CyanogenMod 7 (CM7) for Captivate

Status
Not open for further replies.

s2h2golf

Well-known member
Aug 2, 2010
228
24
0
Visit site
It's here for all of us Captivate users. If you don't know how to flash a ROM, this is not for you. Please read the thread carefully and then read it again before even thinking about flashing away. There are a lot of steps that have to be followed exactly.

[ROM] CyanogenMod 7 for Captivate (Gingerbread 2.3.x) posted - careful! - xda-developers

Here are my personal findings after running CM7 for 1 week. Because of the poor battery life and the camera not being able to take 5mp pictures, I have gone back to Serendipity for now. Unfortunately, I switched back to Serendipity before TheEscapist was able to get UV working, so I have no battery benchmarks for his OC/UV kernel.
Initial issues (those that I found solutions for):

  • Data cutting in and out. About three hours after initially installing CM7, data cut out completely and I got "No Service" showing on my phone. I was running the JK4 modem. This is the best modem for my area. I thought maybe if I flipped on Airplane mode and then flipped it off that would resolve the issue. Airplane mode stopped working completely. Solution: I have batch number 1007. For me, in order for a modem to work right, I have always had to flash the modem twice. Don't know why, but I always do it after flashing a ROM or switching modems. This resolved the issue.
  • Airplane mode not working. This potentially was a big issue as I have two trips planned this month. It did start working again flawlessly after I reflashed the JK4 modem.
  • GPS taking forever to get a lock. I have been one of the lucky few that have always had a decent working GPS, and with the latest changes made to some of the ROMs, my GPS has been great. However, after flashing CM7, my GPS barely worked. After re-flashing JK4, my GPS now works better than it ever has.
  • Market not updating. Here is one interesting thing that works well - almost too well. Remember that little tidbit of information from Google that popped up when you first entered your account (coming from Froyo update)? The one where it asked you if you wanted to sync your apps with Google. Well, without Samsung and ATT crippling your phone, it actually works. The first time I entered in my account name it asked me if I wanted to restore apps. I decided to do it later after I enabled WiFi. However, it downloaded every app that I had ever used, so I had to uninstall a lot of them. In order to get my data back from the apps, I restored apps from TiBu. It worked fine, but when I went to the Market to check for updates, the only apps showing were the paid ones. Solution: I used Market Doctor from TiBu and then uninstall the updates from the Market. Worked fine after that (using Market Doctor may not have been needed).
Issues that have not been resolved (as far as I know):

There is a list of issues at the XDA post - I am not going to list all of them here. Instead, I am going to list issues that I have seen that, while may be linked to those issues, are not readily identified in that list (confused, just read my list below).

  • External SD card. I am guessing that since the Nexus S does not have an external SD card, that is where the problem lies. The Captivate essentially thinks that it is now a Nexus S. Regardless, this is a problem for programs like Documents to Go where files are saved on the external SD card. Friday I was trying to find a document that I had saved to the external SD card and was starting to get a little upset. I finally had to copy the files to the internal SD card so I could use them. Hopefully someone can fix this problem.
  • Camera. This is directly related to the external SD card issue. There is no way to save a picture to the external SD card. I have to remember to copy them over when I am done taking pictures. Note: Apparently the camera cannot take 5mp pictures either - I do not know what the default setting is, but it is not 5mp. This is the only real deal breaker for me - everything else I can live with.
    [*]Battery life. Battery life for CM7 has been just OK. I've had better battery life on some of the other ROMs. However, the important thing to point out is that the battery monitor never shows more than 95% charged (this is a feature, not a bug, to prevent over-charging). After I unplug and run it for a while, battery life will drop down fast and then stabilize around 60% or so, so it looks like the battery drains faster than normal, but I think the overall battery life is about the same. I decided that I would drain the battery completely down and then charge from a depleted state. I was at 75% battery life and ran Stability Test with maximum brightness. It took about 3 hours to drain down to 0%. That's about how long it took for me when I was using Serendipity to drain the battery.
I am going to conduct a series of battery tests with the stock kernel, the Voodoo kernel and the kernel TheEscapist is working on. I will conduct them in a manner that compares each kernel to previous configurations I had recently (Serendipity 5.12 with Suckerpunch #53 kernel). I will update this with my conclusions for each.

Stock Kernel - after 14 hours of use, I had 32% of the battery left. This included a little more than 1 hour of screen time, flashing 4 different modems, running GPS Test for about 10 minutes, checking email for about 20 minutes, surfing the web for about 20 minutes and making one 10 minute phone call. I did not use WiFi. At idle, the phone lost a little more than 2% an hour. By comparison, I have had similar usage with my Serendipity setup and I would typically be closer to 50-60% battery life. At idle, my battery would lose less than 1% per hour. Before I plugged the phone in this morning to charge, I flashed the Voodoo kernel. The battery meter showed 62% when it rebooted. I am not sure if the stock kernel is inaccurate with its battery monitoring or not.

Voodoo Kernel - I had roughly the same battery life using the Voodoo kernel as I did with the stock kernel. I am now running the battery completely dead and re-charging. I will update this in a couple of days after the battery monitor stabilizes and I get a better idea of how long the battery lasts. I may also buy a new battery and see how that goes. I've noticed over the last couple of months that my battery life is not what it was back in December when I was getting 36+ hours on one charge. Update: Battery life did not improve. I am trying a newer version of the kernel to see if that makes any difference.

TheEscapist's OC Kernel - since the base for his kernel is the same as the stock kernel, I will not run battery tests on it. I am however including benchmarks below that I ran. I set the clock speed to 1.2ghz for these tests.


Performance:

I am using the stock kernel. I am anxiously awaiting the OC kernel to be updated with UV, but for now, performance is good - very good. The only time I see any lag is when I open the app drawer in Launcher Pro, but I see that with just about any kernel I have used (except for SetiroN's kernel, which is no longer supported). Programs open fast, Grocery IQ scrolls fast and I can flip through pages quickly. Here are some of the Benchmarks I ran. I was told that Quadrant had not been optimized yet for Gingerbread. I was seeing frame rate caps at 19fps and 28fps.

The Voodoo kernel from Bilboa1 seems to have a little more lag and is not as smooth. My benchmarks are posted below. After running the Voodoo kernel for a couple of hours, everything stabilized and there is no lag - it seems to perform a little better than the stock kernel.

TheEscapist's kernel is the only one at the moment that has OC enabled. I ran some benchmarks using his kernel clocked at 1.2ghz. My results are below.

I will run tests on each of the three known CM7 kernels at the same time I am running the battery tests and report back.

Stock Kernel:
  • Quadrant - 1699
  • Nenamark - 46.6fps
  • LinPack - 14.25
Voodoo Kernel from Bilboa1
  • Quadrant - 1802
  • Nenamark - 45.6fps
  • LinPack - 14.36
TheEscapist Kernel
  • Quadrant - 1795
  • Nenamark - 42.6fps
  • LinPack - 16.38
GPS:

After re-flashing my JK4 modem, my GPS has been the best it has ever been. I get a good lock and can see 12 sats, where before it normally saw 10-11 sats. Tracking is great. I used My Tracks this morning and where I normally see drifts (2 places that have always been a problem), it locked me right in and turned when I turned.

Appearance:

This should probably be renamed theming. CM7 comes with several themes and you can download more that are Theme Manager compliant from XDA. I installed the Honeybread theme, which looks great. Pic below.

The color issue that was reported on for the Nexus S where everything looks more yellow is present in this build. I was told it was not an issue, but a way of making the colors seem more natural. To me, it looks like an issue - webpages that are normally white have a yellowish tint to them. However, the issue that has always plagued me is the sharpness of the text when reading webpages. While this was resolved with different sharpness fixes, straight stock CM7 has this perfected. Text looks very sharp and clean.

Other Interesting Finds:

  • You can change the notification bar to include different toggles for a whole range of different items. Menu > Settings > CyanogenMod settings > Interface > Notification power widget
  • You can change the battery to show the percentage. Menu > Settings > CyanogenMod settings > Interface > Status bar tweaks
  • The battery usage monitor works even if you reboot the phone. It will keep stats on your battery usage until the battery is fully charged.

I will update this as I run into more issues or find solutions.

attachment.php
attachment.php

attachment.php
attachment.php
 
Last edited:

loraque

Well-known member
Oct 15, 2010
1,130
134
0
Visit site
Got this running. So far it is... ok. I ran into some rotation trouble, and when I tried to re-flash, I learned the hard way that you cannot just flash the ROM again like you can normally, after doing the tweaks to get it going in the first place.

Trying to get the USB audio out to work on my car dock, and have not messed with the camera yet, which seems to contain the worst remaining bugs. Fairly stable for a test release, but not really a daily driver yet IMO. If I can get the USB audio to work, I will probably stick with it for a while and see how the fixes get worked on in the short term.

To get back off CM, you need to use Odin with the repartition box checked... which probably means a stock load. I did do that after I borked it up, and it was flawless, so no big deal getting back.
 

bay_wolf

Member
Feb 14, 2011
20
14
0
Visit site
Got this running. So far it is... ok. I ran into some rotation trouble, and when I tried to re-flash, I learned the hard way that you cannot just flash the ROM again like you can normally, after doing the tweaks to get it going in the first place.

Trying to get the USB audio out to work on my car dock, and have not messed with the camera yet, which seems to contain the worst remaining bugs. Fairly stable for a test release, but not really a daily driver yet IMO. If I can get the USB audio to work, I will probably stick with it for a while and see how the fixes get worked on in the short term.

To get back off CM, you need to use Odin with the repartition box checked... which probably means a stock load. I did do that after I borked it up, and it was flawless, so no big deal getting back.


Auto Rotation has a bug in it that's from using Navigation if you had used that then that would be why.
 

loraque

Well-known member
Oct 15, 2010
1,130
134
0
Visit site
Yeah, stumbled onto that as well while trying to keep up with the post count. I am losing. I was indeed using Nav, so there is that.

It is a no go on the car/desk dock too. So far at least. I read how the kernel had to be manhandled to get to work at all, so it may take some revisiting at a later date to fix/add it.
 

ls377

Well-known member
Aug 6, 2010
1,462
268
0
Visit site
Yeah, stumbled onto that as well while trying to keep up with the post count. I am losing. I was indeed using Nav, so there is that.

It is a no go on the car/desk dock too. So far at least. I read how the kernel had to be manhandled to get to work at all, so it may take some revisiting at a later date to fix/add it.

That's probably a feature put in by Samsung, so you'd have to hack it into the kernel. It isn't a priority for the people working on this, but once this gets more usable, I'm sure someone will make a kernel with this/voodoo sound/ all the other goodies we get with out custom kernels.
 

loraque

Well-known member
Oct 15, 2010
1,130
134
0
Visit site
I think it will be easier than that actually. The kernel code required is a known commodity at this point, just not in the newer version. I doubt it will take long at all to get the relevant pieces added in once more of the kernel devs start taking notice.

There is already a voodoo kernel out for it, so some of the tweaks are already being ported in. Things are progressing nicely.
 

ls377

Well-known member
Aug 6, 2010
1,462
268
0
Visit site
I think it will be easier than that actually. The kernel code required is a known commodity at this point, just not in the newer version. I doubt it will take long at all to get the relevant pieces added in once more of the kernel devs start taking notice.

There is already a voodoo kernel out for it, so some of the tweaks are already being ported in. Things are progressing nicely.

Yeah, I'm sure it will happen rather quickly. I'm willing to bet most devs are waiting on them to finish tweaking the kernel.

I'm really excited about this, but I think I'm going to hold off for a bit. Just seems like it would take awhile to flash it, and I want to be able to change around and go back to my main ROM easily.
 

loraque

Well-known member
Oct 15, 2010
1,130
134
0
Visit site
The wrinkle with it, is that when you want to go back to anything else, you need to use Odin to do so. There are not many Odin ROMs other than stock around, so you end up flashing back to stock first (re-partition box checked) if you want to go back to a Samsung based ROM. After that, it is the same. Extra step coming and going.
 

ls377

Well-known member
Aug 6, 2010
1,462
268
0
Visit site
Yeah, I don't mind doing it once, it's all the going back and forth that would wear on me. I wish it was as easy as using nandroid to go back and forth.
 

loraque

Well-known member
Oct 15, 2010
1,130
134
0
Visit site
It is pretty bad right now. They posted on it, and basically there is a ton of debug code running to assist in development that is chewing through the battery. I have charge options pretty much everywhere I am, so I just keep it plugged in all the time right now.

Apparently if you run the Voodoo kernel, they turn some of the debug off, which might help some.

But yes, it does drain quickly. Worse with Wifi on. For users that often find themselves flirting with a low battery, this is not yet for you.
 

s2h2golf

Well-known member
Aug 2, 2010
228
24
0
Visit site
I updated the OP with my results on battery life. I get about the same as I was getting with other ROMs, it just seems to drain faster initially and then stabilize. I'll do a full test today to see where it stands after I leave work and take it off the charger. Normally, after 17 hours or so of light to moderate use, I end up with about 75% of my battery life. If it is at 70% tomorrow morning, I would consider that about the same.
 
  • Like
Reactions: ls377

ls377

Well-known member
Aug 6, 2010
1,462
268
0
Visit site
It is pretty bad right now. They posted on it, and basically there is a ton of debug code running to assist in development that is chewing through the battery. I have charge options pretty much everywhere I am, so I just keep it plugged in all the time right now.

Apparently if you run the Voodoo kernel, they turn some of the debug off, which might help some.

But yes, it does drain quickly. Worse with Wifi on. For users that often find themselves flirting with a low battery, this is not yet for you.

Makes sense, so it'll get better as they work out other bugs.

@s2h2golf: Thanks for keeping this up to date. It's nice to see the experiences of someone running the ROM, especially here at AC.
 

XANAX

Well-known member
Dec 19, 2010
73
8
0
Visit site
I'm also noticing battery life going quickly until about 60% then tapering off and overall it's about the same as other ROMs. MikeyMike claimed his battery went from 100% to dead in 6-10hrs. Right now I'm at 44% in 17hrs. 50m with fairly light usage, Wifi turned off while I sleep.
 

s2h2golf

Well-known member
Aug 2, 2010
228
24
0
Visit site
Another update to the OP. This time I ran a full battery test being away from a charger for 14 hours. My battery life was not as good as I thought, but it was acceptable. It dropped down to 32% with light to moderate use. Before I plugged it in this morning, I flashed the Voodoo kernel by Bilboa1 and the battery meter showed 62% after it rebooted. Not sure if that is accurate or not, but that may mean that the stock kernel does not monitor the battery usage very accurately. I'll see how the Voodoo kernel works out over the next couple of days.
 

ls377

Well-known member
Aug 6, 2010
1,462
268
0
Visit site
Another update to the OP. This time I ran a full battery test being away from a charger for 14 hours. My battery life was not as good as I thought, but it was acceptable. It dropped down to 32% with light to moderate use. Before I plugged it in this morning, I flashed the Voodoo kernel by Bilboa1 and the battery meter showed 62% after it rebooted. Not sure if that is accurate or not, but that may mean that the stock kernel does not monitor the battery usage very accurately. I'll see how the Voodoo kernel works out over the next couple of days.

How long did you have it plugged in to flash it? (If you did at all). Whenever I use Odin, it always freaks me out when the battery comes back significantly higher than what it was before. I always attributed this to having it plugged in, but 30% seems a little much for that.
 

s2h2golf

Well-known member
Aug 2, 2010
228
24
0
Visit site
How long did you have it plugged in to flash it? (If you did at all). Whenever I use Odin, it always freaks me out when the battery comes back significantly higher than what it was before. I always attributed this to having it plugged in, but 30% seems a little much for that.

I didn't plug it in. The Voodoo kernel was CWM flashable. It did take a while to charge back up after I plugged it in this morning, longer than it would have taken if it was actually at 62%.

I've had Odin do that every now and then too. I've found that physically taking my battery out after flashing a kernel seems to imrpove the battery monitor.
 

godzulu

New member
Oct 17, 2010
3
0
0
Visit site
To get back off CM, you need to use Odin with the repartition box checked... which probably means a stock load. I did do that after I borked it up, and it was flawless, so no big deal getting back.[/QUOTE]

Can you provide instructions or to how to return to stock from cm7? I know how to use odin 1click, used 1.7 to get cm7 but im not sure how to return if necessary. Thx

Sent from my SGH-I897 CM7 using Tapatalk
 
Status
Not open for further replies.

Trending Posts

Forum statistics

Threads
946,028
Messages
6,925,987
Members
3,160,049
Latest member
VersusDizajn