[NIGHTLY][ROM] CyanogenMod 7 for Samsung Captivate (captivatemtd)
- Thread starter atinm
- Start date
Yes, it contains everything. Just flash the latest update.
Sent from my SGH-I897 using XDA App
If you're not on CM7 yet; Don't you have to flash the inital first... then the update?
You flash the kernel first (the initial flash) to get clockworkmod recovery 3 which is compatible with ext4 so you can install the rom.
If you don't do this I'm pretty sure it won't boot.
Sent from my HTC Glacier using XDA App
Yes, but the way he posed his question made sound like he had flashed the initial, and wasn't sure whether flashing the latest update would bring him up to date.
Sent from my SGH-I897 using XDA App
The question was only about the update...so it should be save to think the person already has CM7 on their phone. But yes if you don't have CM7 installed the initial is what is needed first.
We were talking about the initial package, not the kernel.
Also, you need cwm3 because android 2.3 requires it, not because it's compatible with ext4.
Sent from my SGH-I897 using XDA App
compass/magnetometer has been disabled to prevent issues (phone no longer locks orientation when going into landscape mode using apps like skymap or google navigation). the output in old builds was wildly off as it wasn't being properly offset... Unhelpful is trying to sort the math and proper offsets, but Samsung doesn't use a true driver and seems to speak to the magnetometer through an unusual method that I don't quite understand (even with Unhelpful's explanation!). this seems to be a bigger thing to tackle than he expected though as he's missing some crucial information about the yas529 compass that doesn't seem to be found anywhere.
The one I used was actually in that thread. It was called stock and looks like the samsung themed one without the mic in the screenshot, but it's actually a flashable zip that installs stock swype (the one you'd be getting from installing beta) to system/app. Download is here. From there you can install these.
Last edited:
Yea I'm getting the hotspots error too...just noticed it five minutes ago
Sent from my SGH-I897 using XDA App
Sent from my SGH-I897 using XDA App
I know most people complain about the battery life with CM7 but mine has actually gotten better.
for most of my day I'm in a signal poor region that ate up my battery with Samsung ROMs - it was God awful. I'd lose 15% per hour on standby with no activity. 4 hours gone and you're more than halfway done ...yikes. and yes... this is tested over months... it wasn't just a single bad rom.
Anyways, my phone has more charge at the end of the day.
I suspect CM7 may be better at power saving in poor signal regions.
Sent from my SGH-I897 using XDA Premium App
for most of my day I'm in a signal poor region that ate up my battery with Samsung ROMs - it was God awful. I'd lose 15% per hour on standby with no activity. 4 hours gone and you're more than halfway done ...yikes. and yes... this is tested over months... it wasn't just a single bad rom.
Anyways, my phone has more charge at the end of the day.
I suspect CM7 may be better at power saving in poor signal regions.
Sent from my SGH-I897 using XDA Premium App
You almost certainly can't. It almost certainly depends on the Samsung framework, which is obviously not in CM.
Also, v2.4 of my oc kernel is up, in case any one wants it.
For those of you that are needing droidwall on CM7
the iptables is outdated.
try this one...
not sure where I got it but it works to get droidwall working again.
put it in /system/bin/
in first version of cm7 from 20110304
I also needed to create a modules folder in /system/lib/
and then run
ln -s /system/lib/modules /system/lib/modules/`uname -r`
but with the update 20110310 this is no longer needed.
EDIT: REMOVED .....NOT NEEDED ANYMORE
the iptables is outdated.
try this one...
not sure where I got it but it works to get droidwall working again.
put it in /system/bin/
in first version of cm7 from 20110304
I also needed to create a modules folder in /system/lib/
and then run
ln -s /system/lib/modules /system/lib/modules/`uname -r`
but with the update 20110310 this is no longer needed.
EDIT: REMOVED .....NOT NEEDED ANYMORE
Last edited:
already known and fixed in github. new build will be uploaded once confirmed working by atinm.
the 03.10 build has this iptable in it by default (in fact it's what broke wifi and usb tether) and using this version will most likely kill it for anyone not running 03.10... reverting it is the only way to fix wifi and usb tether (for now?)
Last edited:
For some reason after I updated to 3.10 droidwall still segfaulted.
So I just re-copied this iptables and it works again.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
184This thread is reserved for nightly builds of CyanogenMod Rom for Samsung Captivate.
All Samsung Roms run on top of BML/RFS, CyanogenMod 7 does NOT.
It runs on MTD/yaffs2 (like Nexus One) which means you'll not able to flash just any kernel or run just any other filesystem you want. Use it as it is if possible, otherwise confirm with the kernel developer that you are trying to install whether it would work with CM. We do not support other kernels and know nothing about their capabilities or compatibility. Only the data partition, which is on movinand, is ext4 like on speedmod or voodoo ("lagfix"). No "lagfix" is necessary because this does not use any Samsung proprietary file systems.
CyanogenMod is a free, community built distribution of Android 2.3 (Gingerbread) which greatly extends the capabilities of your phone.
Code:** These CyanogenMod builds are highly experimental and unsupported. ** ** Please refrain from submitting bug reports for any issues ** you may encounter while running one of these builds. ** ** Submitting bug reports on nightly builds is the leading ** cause of male impotence.
What are Nightly builds? Auto compiled build of the latest CyanogenMod source from github. This version changes each night and aren't officially supported.
If you find bugs/issues you can/must discuss here (do not submit nightlies bugs on CyanogenMod issue tracker).
Warning : Not for new users, flash this build only if you know what you are doing !!! Make SURE you can get into Download mode using only buttons (no other method, Download mode from just buttons is essential).
INSTRUCTIONS:
Latest version: http://download.cyanogenmod.com/?device=captivatemtd
Check the md5sum if you want to be sure that the download worked (different OSes have different programs that do md5, on ubuntu it is md5sum that you run against the zip you download and compare to the md5sum number shown on the download website). ROMManager does this automatically for ROMs you download via ROMManager.
- First time flashing CM 7 to your Captivate (or coming from another ROM)?
Easy way:
- Start with a rooted Eclair/Froyo running Eclair/Froyo Bootloaders (do not ask us how to do this).
- Install ROMManager Premium.
- Flash ClockworkMod Recovery. Pick Captivate (MTD) (ignore the warning about not having an official, pick ClockworkMod 2.x).
- Make sure you can reboot into ClockworkMod recovery from ROMManager. Reboot and get back into ROMManager Premium.
- Choose download ROMs.
- Pick the CyanogenMod Nightlies.
- Check the Google Apps addon.
- Check Backup current ROM!
- Check wipe data, cache, dalvik cache.
- Let ROMManager finish the installation.
Harder way:
- Make sure you're running a Eclair/Froyo Firmware (2.1 or 2.2) and Eclair/Froyo Bootloaders!
- Root your device and install ClockworkMod Recovery.
- Do a Nandroid backup!
- WIPE (wipe data/factory reset + wipe cache partition)
- Install the ROM from internal sdcard using ClockworkMod Recovery
- Optionally install the Google Addon (through ROMManager is easiest)
- Upgrading from earlier CM7?
ROM Manager method:
- Install ROMManager Premium.
- Flash ClockworkMod Recovery. Pick Captivate (MTD) (ignore the warning about not having an official, pick ClockworkMod 3.x).
- Choose Download ROMs.
- Pick the CyanogenMod Nightlies.
- Check the Google Apps addon.
- Check Backup current ROM!
- Check wipe cache, dalvik cache.
- Let ROMManager finish the installation.
Clockwork Mod method:
- Download and push the ROM zip file to the sdcard.
- Reboot into recovery.
- Do a Nandroid Backup!
- Install the ROM zip from sdcard (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps. After flashing the rom, don't forget to flash Google Addon package if you want it. ROM Manager will allow you to flash it if you just go into it and after flashing the ClockworkMod recovery for MTD devices, choose Download ROMs, and pick Google Apps.
Additional Information:
Maintainers:
atin - http://twitter.com/atinm
codeworkx - http://twitter.com/codeworkx
coolya - http://twitter.com/dumdidum
guiperpt - http://twitter.com/guiperpt
unhelpful - http://twitter.com/unhelpfulone
Irc:
Host: irc.freenode.net:6667
Channels: #cyanogenmod, #cyanogenmod-dev, #cmsgs
Changelog:
Generic Changelog CMSRC Twitter
Device specific Changelog by igor.tonky
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy![/QUOTE]22
Thanks for sharing.
I'm sure other people are thinking the same things so I'll try to explain where we are.
We're stalled a bit waiting on things that are outside our control right now.
Kernel source code that is essential to solving many of the problems is not available to us from Samsung, and so we're doing what we can without having any documentation of the hardware or source code that actually works with our hardware that is not from Froyo. Regardless of what some idiots who show up now and then say, porting over drivers from the mess that the Froyo kernel drivers are, over to the clean world of Gingerbread from Nexus S is not trivial - especially not when you're twiddling bits that you have no idea what they do to hardware because you lack documentation and are trying to support multiple models of phone while even Samsung seems to segregate their kernel trees by model. Also, many of the drivers were in binary form even on Froyo, and we cannot use that in Gingerbread for the simple reason that binary modules from one kernel do not work in a newer revision of the kernel if enough changes happen between revisions(and enough has changed between linux 2.6.32 on Froyo and linux 2.6.35 on Gingerbread).
Second, comparing SGS to the other manufacturer's devices doesn't really make sense given that this is the first time an SGS has run CyanogenMod while the other phones have a path already because they've been made to work much earlier with previous versions or the other hardware running CM7 have source for the essential pieces that we do not for SGS. Samsung also did things very differently in SGS from Nexus S, let alone from say HTC, and this is an issue that has not been addressed in the CyanogenMod sources and so we have had to make changes that we are waiting on the CyanogenMod team to approve before we can merge with mainline.
It is best to think of the SGS phones are an outlier in the Android world - it is almost as if Samsung was really building it to run another OS and then switched at the last minute to Android. When they switched, they hacked stuff in so that they did not follow the Android model for how the kernel and Android talk to each other. Instead they put in their own custom hacks that are not portable across phones, and break many of the clean interfaces that Android is based on. This is why Samsung Apps from their Gingerbread release will *still* not work on CyanogenMod because CyanogenMod is a clean AOSP build that uses the same code base for all phones, only the underlying hardware interfaces are different. The Nexus S is not a Samsung phone internally in that it has been re-implemented to follow Android guidelines and therefore it was trivial to have CyanogenMod working on it (trivial compared to SGS anyway). We wish we could take more of the drivers from Nexus S given that the hardware is similar, but there are critical pieces that are different and those are exactly the parts that we haven't been able to fix completely.
Hope that clears things up. We're waiting on:
1. Samsung source for Gingerbread for the SGS phones.
2. CyanogenMod team approvals for our submissions for merge to mainline. We have a few critical ones that are pending, after that the merge should be much easier (we hope).
I am working on headset issues for Vibrant, and will be doing some investigation on battery issues after that. The compass is being worked on, and so is the camera. We just haven't had anything to commit, but it isn't for lack of trying (though sometimes it is just that real life constraints give us less time as well).
As far as complaining, or talking about donations that some people do - neither of those things motivate us. I don't ask for donations (except for people to sign up as organ donors, but that isn't directly for me obviously), and anyway, donations are just that - donations. We aren't doing this for the donations, and donating does not give anyone any extra support than not donating. We're doing this because it is a challenge, and is fun, and because we want our own phones to work better. Donations are a nice thank you, but a straight thank you is fine too and means as much. What is appreciated more is taking over some of the support on these threads to give us time to concentrate on coding.
Last I'm saying on this . . .10Just uploaded 06032011 Nightly:
http://sourceforge.net/projects/teamhacksung/files/captivate/
In addition to the changelog on the site linked in the OP, I also added some lower brightness settings from Nexus S that we used to have before. Other than that, if builtbots work tonight, this'll be a repeat. I'll merge the brightness changes soon so builtbots pick them up as well.8Sold my captivate guys. Although I wouldn't had if I couldn't get CM7 on my new device, but that's neither here nor there
Anyway.. just wanted to thank all the users in this thread for helping me out when I needed help or for continuing to make CyanogenMod a positive experience. Thanks again and I wish all you captivators the best and happy CM'ing
