yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Lekz:
I have an SIII now, but I can't help but wonder what the heck happened to CM9 RC1 for my cappy...
[Captivate Android Development] ThreeofNine:
Maybe they stopped working on cm9-rc1 for the Captivate since they knew that JB (cm10) would be released and they preferred to work on it? Just hoping......;)
[Captivate Android Development] :
Someone posted a while back that the build just wouldn't compile, so they skipped it, but the new builds are more updated than RC1 anyways.
[Captivate Android Development] Silencer96:
Here's to hoping that CM10 comes out pronto! I can't wait to see Jelly Bean running on my Cappy :D
[Captivate Android Development] cas0404:
Hi, I'm just install this CM9 ICS Rom and I’m so happy everything work fine but I’m noticing something on my wallpaper, when i scroll through the different pages i see some glitch on the screen, the image gets distorted for a second, why this happen? Maybe because of the GPU Driver that doesn’t render well the image on ICS? is there a fix? .....

thx
[Captivate Android Development] ap1618:
7/9 build charges slow??! 2% increase in like 20 minutes...
[Captivate Android Development] bmaa:
Hi. This is my first clean install of CM9 coming from GB 2.3.5. Wiped data/cache. Installed latest CM9 nightly 20120710. But now i have a "Safe Mode" watermark in the left bottom of the screen. How can get rid of it? what did I do or did not do? Thanks for your help.
[Captivate Android Development] ap1618:
you did factory reset?

did you also wipe cache partition?
[Captivate Android Development] bmaa:
I was running stock GB 2.3.5.

This is what I did today:

Rooted with ODin and re-installed Stock-Kernel.

Installed CWM using ODin and Corn-Kernel UCKK4-7.05.

Booted into recovery mode.

Wiped data. Wiped Cache.

Installed the CM9 nightly and then installed GAPPS.

Do I need to restart again? did I miss sometheing? Thanks for your quick response.

---------- Post added at 07:31 PM ---------- Previous post was at 07:24 PM ----------

Wiped Data/factory reset in the same step. I repeated now again with wipe data/factory reset, wipe cache, wipe Dalvik (missed first time around) then install cm9 + gapps. Safe mode watermark still there,.
[Captivate Android Development] cas0404:
I'm realizing that the glitch on the screen is everywhere, it also appear in recent apps, i know that gpu drivers are out a long time ago, but the screen still flickering.

Is It Just Me?

thx
[Captivate Android Development] Gromlakh:
All the wipes/resets and whatnot while you are on stock are not needed and will not help to do them again. When you flash the CM9 installer, the installer will completely format the entire partition table and rewrite everything. There will be no data/cache/dalvik/anything else left from stock. All you need to do is have CWM and just flash.

Sent via Captivate (powered by CyanogenMOD)
[Captivate Android Development] whipps:
Is this an AOSP rom?
[Captivate Android Development] sa1yan:
Yep! Probably one of the best.

EDIT: Like ever.
[Captivate Android Development] ninjuh:
LOVE latest nightly. Smooth as butter. Where's everyone getting the green ics theme though?
[Captivate Android Development] ap1618:
Is it only mine that is not butter smooth?

and my battery life sucks. OS consuming the most.
[Captivate Android Development] nkrick:
"Butter" will come as part of CM10 (Jelly Bean).
[Captivate Android Development] :
..."smooth as butter" is a common expression :laugh:
[Captivate Android Development] CptTwinkie:
The copyright lawsuit is pending lol

Sent from my Galaxy S3 [d2att][root]
[Captivate Android Development] :
Wait, they patented that too! *que sitcom intro*
[Captivate Android Development] ninjuh:
Oh **** my bad..Google if u can read this plz don't be sue-happy like apple. I really didn't mean to use the bu**er word :'(
[Captivate Android Development] axl81:
Seriously though, this nightly is so smooth, I can't believe it's not butter...
[Captivate Android Development] johnnyrichter:
Just got done installing CM9 ROM and Glitch kernel from Corn 7.0a kernal and Legend5 ROM. Had a little hiccup on the ROM install but all I had to do was just install it again via CWM and the second time worked.

Some questions...

-Is there a list of working themes for this ROM?

-Which launchers are confirmed 100% working? I need one that lets me apply a single-screen sized wallpaper rather than only letting me select a certain part of the wallpaper or zooming in on the wallpaper like Holo does.

-Does the launcher change the power button menu or is that the ROM? Reason I ask is because I miss having "reboot to recovery" and "reboot to download" in my power button menu.

-Is it better to OC from Glitch or from the ROM? It looks like I can do it from the ROM settings but maybe I misunderstood what I was looking at in the settings menu.
[Captivate Android Development] bmaa:
Tried again. Went back to CM7 (it was not easy going from CM9 to CM7). Followed the steps from first post and flashed CM9. The "Safe Mode" watermark still there. Anyone else seeing that problem? thanks.
[Captivate Android Development] shane87:
1. To find themes, search the market for cm9 themes. Most will tell what they do and don't theme, and list any issues along with any special instructions to ensure the best application.

2. All launchers should work. Personally, I use Go Launcher EX. With go launcher, I have my background set to scroll as I flick through screens, but you can have the background stationary, in which case it will show all of the image, assuming that the image is properly sized. Remember, these screens have a fixed size, so certain picture sizes, such as a landscape (i.e. wider than it is tall) image, will not work so well.

3. The power menu is rom-controlled. This rom does have the option for "reboot recovery." Press power, then press reboot, and it will give the option to specify reboot or reboot to recovery. Cm9 does not have a "reboot to download" option. To the best of my knowledge, the only ways to trigger download is to power off, hold vol up & vol down, then insert usb, or use a download-mode jig.

4. Oc is not an "official" feature, and relies on an after-market kernel, such as glitch. Therefore, questions about oc, or any other non-stock kernel features/issues, should be directed to the forum for your kernel.

Hope this helps!
[Captivate Android Development] johnnyrichter:
1. Thanks, I'll try that out.

2. Downloading and instaling GO Launcher EX right now. I've heard so much about it, and my beloved TW 4.0 can be a bit buggy, so I figured I'll try this one out. ETA: GO Launcher EX is pretty sweet!

3. Those two options were really nifty on Legend 5, but it's good to know that rebooting in to recovery is an option on this ROM. An option for rebooting to download isn't too big of a deal since I really only use that for restoration purposes.

4. Will do.
[Captivate Android Development] shane87:
Glad I could help! I wish this rom did have an option to reboot to download. It would help people like me, who's power button is fried.
[Captivate Android Development] dardragon:
Is your down volume key broken? You will go into safe mode if you hold the down key while booting up
[Captivate Android Development] :
That's for i9000 bootloaders. Captivate ones require both volume keys and insertion of a usb cable. When my power button broke, I used a jig.
[Captivate Android Development] johnnyrichter:
Icy Glitch + today's nightly build of CM9 = amazing. This combo runs smoother and faster than anything I've tried so far, and the battery drain seems to be the least I've seen so far. All my apps seem to be working fine, and there's definitely no lack of customizations with this ROM. I am extremely happy with this software and GO Launcher EX made it even more enjoyable.

I have a few more questions...

I looked on the market and I'm noticing two types of themes so far. Those with no restrictions listed(such as CM9 Green, CM9 Red, etc) and those that do have restrictions like "This theme is for xHDPI and HDPI phones only!" What are xHDPI and HDPI phones? I'm also noticing some themes having AOKP in their title or description, what's that about? Figured I'd ask before I go installing a theme that won't work or may screw up my phone.

Could anyone tell me why I don't get the same dialogue/popup from the menu key in Titanium Backup that I did on Corn+Legend5? When I hit menu now it just brings up a long list of options, no more little popup with settings/batch/about/etc. I can't seem to figure out how to do batch backup/restore now or why it wouldn't be showing up with this ROM. Batch operation keeps me from having to manually restore/backup all 140+ items.

I understand OCing is a kernel related deal but my question is about something built in to CM9. The ROM's OC menu, is that "safe" enough to use or should I be OCing via CWM or Voltage Control? I like the simplicity of it so unless there's a reason I shouldn't use it, I'd like to stay out of the CWM and avoid downloading even more apps.

If I want to stay up-to-date with the nightly build versions, what is the most recommended way to do so? The first page says to do a nandroid backup, install the ROM normally, and install the google addon. I have no idea what a nandroid backup is. I already installed the google addon, so do I need to do it again since there doesn't appear to be any need for a wipe? Will I have to back anything up on the older version or will all my apps/settings/etc carry over?
[Captivate Android Development] shane87:
The themes with restrictions refer to the pixel density of the phone. The captivate is an hdpi, or high-density pixel interface, phone. The aokp tag means that it also works on the aokp roms. Aokp is a different aosp sourced rom.

The change in titanium backup is due to ics's use of the "application bar." To launch batch jobs, look at the top of the tibu screen, and press the icon that is on the far right. It has a box with a check mark in it.

The oc options included in the rom do essentially the same thing as voltage control. And you will notice that, even when oc'ing is included in the stock kernel, it is not recommended by the devs, since you will get a popup warning you to be careful with the settings, and not to report any problems you may experience while oc is enabled.

To stay up-to-date, make a nandroid backup of your current setup. To do that, boot to recovery, choose backup/restore, then choose backup. Then simply flash the latest nightly, followed by the gapps package. All of your settings and installed apps will remain. However, you will have to reflash gapps after EVERY flash of a cm9 update, since gapps reside in /system/app, and /system is wiped when you install an update.

[EDIT] The nandroid backup is so that, if you experience problems with the new update, you can restore back to an older version.[/EDIT]

[EDIT 2]If you are using an after-market kernel, such as glitch, you will need to reinstall glitch after an update to a new cm9 nightly, since it will install the stock kernel.[/EDIT 2]

Hope this helps!
[Captivate Android Development] nkrick:
You no longer have to reflash gapps when installing a new nightly. This was fixed quite a while ago, but for some reason it was not mentioned by the devs. I believe the problem was in CM9, not in THS's Galaxy S specific code, so perhaps one of the core CM developers mentioned it was fixed and the word never trickled down to everyone.
[Captivate Android Development] johnnyrichter:
Ah ok, so the CM9 HDPI themes will work on my phone. Good to know, will check some of those themes out and see what catches my eye.

Got Titanium backing up everything now. Thanks for the tip on that application bar. I would have never found it on my own. :o

I understand them not recommending overclocking as I'm an overclocker when it comes to PC, so I'm definitely familiar with the risks. I'm running a very conservative OC on the phone, but just wanted to be sure the ROM's OC interface was OK to use instead of VC or CWM.

The update steps sound easy enough so I don't foresee any issues there. I'll go ahead and leave the gapps and Icy Glitch packages on the phone.

Thanks for all the help!
[Captivate Android Development] azunino:
If you want themes for CM9 take a look at this: http://xdaforums.com/showthread.php?t=1673456
[Captivate Android Development] johnnyrichter:
It seems that my phone turns itself off if it's locked/idle for about an hour or more. I've had to turn it back on about 3 times today so far. Anyone else having this issue?
[Captivate Android Development] azunino:
which kernel?
[Captivate Android Development] johnnyrichter:
Icy Glitch, linked in my sig.
[Captivate Android Development] bmaa:
That was it !!. I just realized my volume down button was not working (i fixed my power button last week, so maybe some dirt went into volume button). I cleaned with some alcohol and re-installed CM9. No more Safe mode watermark. Thank you for your help.
[Captivate Android Development] ap1618:
there was no 7/11 nightly...
[Captivate Android Development] johnnyrichter:
Just had it turn off after about 10 minutes. It's not the battery as it has almost a full charge. No idea why it's doing this. :confused:

ETA: My brother has the same exact phone with the same exact software(I did it all for him) and his phone isn't shutting off like mine. We're both running a 200/1200 OC in the ROM OC menu which rules that out as the cause, although I did set mine back to default settings just in case. The only difference between his setup and mine is I have different apps...teamspeak, titanium backup, astro, opera, sceenshot, aim, grooveIP. I believe he only has the base apps plus maybe pandora.
[Captivate Android Development] ShadrachCA:
I had the same problem with battery life after flashing the last couple nightlies. Worse than I have ever seen - we're talking dropping 25% an hour while my phone sat untouched on my desk at work and it was getting very warm. Battery stats showed OS consuming almost all. I reflashed and wiped all data/caches (I typically just wipe caches) and it seems to have done the trick.
[Captivate Android Development] azunino:
Use the default kernel included with CM9. It is super stable.
[Captivate Android Development] johnnyrichter:
Good call, I'll take that step next if my current "fix" didn't work. I uninstalled steam since I never use it and I also undid my ROM-menu overclock, even though my brother is running the same OC and his phone doesn't shut off, figured I might as well rule that out mostly for the sake of getting support if the problem persists.

I've checked the phone once every 10-15 minutes or so, no shut down yet. I'll let it sit for an hour or so and if it shuts down I'll switch to the default kernel. Is there a .zip for that kernel or do I need to install the latest nightly again? If the latter, I guess I'll have to do a titanium + nandroid backup from what someone said earlier.
[Captivate Android Development] CheesyNutz:
nope all good here
[Captivate Android Development] nkrick:
Just flash the latest nightly to get back the the THS kernel. In the meantime, the developers have requested on several occasions that you not post any problems on this thread unless you are running the included THS kernel. You should be posting your problems in the glitch kernel thread.
[Captivate Android Development] shane87:
You don't have to back anything up for flashing a nightly install package. It is a good idea to make a nandroid backup before flashing, in case you have any issues with the latest nightly. However, flashing a nightly package does NOT wipe data, so all of your apps/settings will not be lost.
[Captivate Android Development] johnnyrichter:
I did a nandroid backup, wiped both caches(although I doubt this was necessary), then installed the latest nightly. Everything went smooth and my phone has yet to shut off so I guess it was Glitch causing it.

It's a shame that I can't OC past 1000MHz with this kernel, though. Would there happen to be a feature list posted anywhere for this kernel they package with the ROM? Or is it more of a basic kernel?
[Captivate Android Development] ninjuh:
So I experienced a bug today everyone should keep an eye out for..or an "ear" rather...

I was on the phone with a support rep for PayPal trying to get some info on my account sorted out(headache), when suddenly the call went silent, looked at my phone & I was on my home screen as if I ended the call. So I set my phone down & start *****ing to my girlfriend about how stupid the rep was on the phone, 2 seconds later, I hear the rep yelling through my phone...looked at my phone and it showed zero evidence of being connected to a call, but I could hear the lady talking.... I felt like such an ass. Yanked my battery out in a panic lmao.

So yeah, be careful guys

I'm running 7/10 nightly stock kernel w/ clean flash. Going to flash newest nightly so hopefully it doesn't happen again.
[Captivate Android Development] account4me2:
These are called sleep deaths, and I've been getting them on all of the CM9 nightlies that I've tried (maybe 10 of them) over the last 3-4 months. I've tried all the kernels (obviously including the THS one that comes with CM9), I've tried different bootloaders, and I've increased the min clock speed to 200mHz from 100mHz. No good.

I'm pretty sure I get them less on Glitch than on any of the other kernels, though. I didn't used to get them in the alpha builds, but I can't be bothered going back or switching ROMs. On Glitch right now I only get it 1 time every 1-2 days, usually, so it's alright.
[Captivate Android Development] billyjed:
Try to overvolt by about 50 with nstools. Such setcpu if you have been using it. Set the minimum cpu to 200 with the overvolting.
[Captivate Android Development] johnnyrichter:
Switched back to the included kernel and it's still shutting off during idle, times vary.
[Captivate Android Development] shawn122:
I posted about the idle issue in the Devil kernel thread. Someone there told me it was a function of the ROM and not the Kernel
[Captivate Android Development] johnnyrichter:
This turning off after X idle time has persisted between both the backed in and glitch kernels, so it definitely looks to be ROM related. I'm using all the same apps I had on KK4 and Legend5, so I doubt they're to blame.

The problem doesn't always occur which is the most confusing part. Sometimes the phone will shut off after a few minutes of idle, or an hour, or not at all. It definitely shuts off during the night while I'm asleep but I don't know when. All that's ever running @ idle is the wifi, GrooveIP, DSPmanager, Gmail, AIM. Network is off since I only use this as a home/emergency phone, main one is a tracfone.
[Captivate Android Development] Primus76:
Anyone else getting "low on space" error in notification bar after the latest nightly?

Stock cm9 and kernel.

Storage looks fine in setting. Is it referencing system?
[Captivate Android Development] shane87:
The "low storage space" is actually in reference to the datadata partition. This is where all of your apps, including system apps, store their settings and any lib files. This partition is located on the small but fastest flash chip to increase app load speed. To determine what app(s) are taking up the most room, download disk usage from the market. I have to regularly clear my history/cache from chrome beta, as the cache and history grows and can take up quite a bit of room.

Another option is a "data fix script" which will move everything except for libs out of the datadata partition, saving a lot of room. However, the last time I used a "data fix" script was around the same time my mms stopped working. I have no proof that it was related, but I am suspicious.
[Captivate Android Development] shane87:
[EDIT]Just as an example, I cleared the cache and cookies from chrome beta and cleared 7+mb of room on datadata. That was without clearing history or saved passwords/autofill data.[/EDIT]
[Captivate Android Development] dardragon:
I used the data fix from here http://xdaforums.com/showthread.php?t=1541942

I haven't noticed any problems but I also don't use mms
[Captivate Android Development] azunino:
no problems here. Updated without wiping
[Captivate Android Development] shane87:
That's the same one I used. It may be completely coincidental. I just know that my mms stopped working in early march, so I went back to earlier builds, and it was still broken, even though it had worked before. Around the same time that mms stopped, I had installed the data fix script, which makes changes in data and datadata, so it doesn't get wiped after a flash. After going to kk4 and coming back to cm9, mms started working again, and I haven't used the data fix since. I may do some testing tomorrow and see if the data fix does break mms. If I find anything, I'll post back with details.
[Captivate Android Development] Primus76:
Thanks for the info. Was using disc space but wrong partition. My data data as down to 16 meg. Cleared browser history and freed up 6 more. Error gone.

Thanks again all.
[Captivate Android Development] shane87:
Ok, so, I can confirm that the data fix script does NOT break mms. I tested like this:

1. Wipe cache/dalvik (I always wipe caches before a flash)

2. Install 0714 nightly and gapps

3. After reboot, I sent an mms message, just to be sure mms wasn't broken in the 0714 nightly

4. Reboot recovery, wipe cache, wipe dalvik, flash data fix script.

5. After reboot, send mms again.

I know I didn't exhaustively test it, and certainly not under worst case scenarios, such as flashing a new nightly over a setup with data fix already applied. All I tested was that the data fix script, BY ITSELF, does not break mms. To anyone with mms problems, I would suggest a wipe data/factory reset followed by flashing the latest nightly, or a heimdall/odin one click to kk4 if the wipe data/factory reset does not work.
[Captivate Android Development] johnnyrichter:
So is there a fix for random turn-offs? 7-13 nightly and stock kernel.
[Captivate Android Development] azunino:
Maybe some of your apps? I've been using cm9 since april and I've never had a reboot
[Captivate Android Development] johnnyrichter:
AIM, Gmail, Youtube, GrooveIP, Titanium Backup, Astro, screenshot, Opera Mobile, Pandora, TapFish, Drag Racing, Pool Master, Drag Racing Bike Edition.

Gmail and FB are usually the only ones running constantly.
[Captivate Android Development] azunino:
default kernel? are you overclocking? any battery "optimizer" tweak? some leftovers from a previous rom? Did you restore settings with titanium backup (it is know for causing problems)?
[Captivate Android Development] johnnyrichter:
Stock CM9 kernel, no OC, didn't do a restore this time around with Titanium Backup. Fresh install that was done after a wipe/reset via CWM.

Even when I had Icy Glitch, and an OC, it still had the same problem.

ETA: Also using GO Launcher EX + GO task manager, and Black Exodus theme.
[Captivate Android Development] azunino:
Well, nothing seems wrong with your apps. Do you have the most recent google apps: http://goo.im/gapps/? I had problems with the inverted gapps once. Maybe you should try using the stock cm9 theme just to narrow down the number of possible causes (btw, I have >10 themes installed so I don't think that's the problem...). Besides, try not to kill apps with go task manager.
[Captivate Android Development] johnnyrichter:
I do kill apps quite often with that, keeping my FB/GMail/GrooveIP locked. I uninstalled some games, aim, titanium. Also using the most recent gapps for CM9 that was on the cyano install wiki.
[Captivate Android Development] azunino:
well, then that's the next thing to try. Remove the go app killer and let the android low memory task killer do its job. In fact, task killers are not necessary, and cause more harm than good.