CyanogenMod 9 ICS for Captivate Q&A(Unofficial)

Search This thread

pqee

Senior Member
Sep 13, 2010
418
147
Ottawa
Does anyone else use the option Settings-->Developer options-->Kill app back button?

I use this pretty frequently but found it also kills my launcher. Even with my launcher set as the default it's killing it if I'm not careful how long I press the back button or how often. This causes an annoying delay waiting for it to reload.

Is this intentional behavior? I would think it wouldn't touch the launcher.
 

RootTheMachine

Senior Member
Oct 4, 2011
2,088
533
Does anyone else use the option Settings-->Developer options-->Kill app back button?

I use this pretty frequently but found it also kills my launcher. Even with my launcher set as the default it's killing it if I'm not careful how long I press the back button or how often. This causes an annoying delay waiting for it to reload.

Is this intentional behavior? I would think it wouldn't touch the launcher.

It kills whatever process is in the foreground, there are no rules to what it kills


Sent from my CM9 ICS i897 Captivate
 

pqee

Senior Member
Sep 13, 2010
418
147
Ottawa
It kills whatever process is in the foreground, there are no rules to what it kills


Sent from my CM9 ICS i897 Captivate

I might be wrong but I'm almost certain that CM7 didn't behave this way. If you had no default launcher defined then it would kill anything. If a default launcher was defined, it would kill anything other than the launcher. Holding back while on your launcher did nothing.

I posted in the CM7 Q&A forum to find out so I don't have to reflash. I'm lazy that way.

Edit: Turns out I was wrong. Damn. The option would be so much more useful if it didn't touch the launcher. :)
 
Last edited:

Razzman

Senior Member
Jan 3, 2011
362
16
I might be wrong but I'm almost certain that CM7 didn't behave this way. If you had no default launcher defined then it would kill anything. If a default launcher was defined, it would kill anything other than the launcher. Holding back while on your launcher did nothing.

I posted in the CM7 Q&A forum to find out so I don't have to reflash. I'm lazy that way.

Edit: Turns out I was wrong. Damn. The option would be so much more useful if it didn't touch the launcher. :)

I use it to and yes it kills the launcher about 50% of the time. Not a big deal as it comes right back, the benefits far out weigh that little inconvenience IMO.

Sent from my SGH-I897 using XDA App
 

6speedg35

Member
Mar 21, 2011
6
0
I'm sorry if this a noob question, but I've only ever flashed this phone once before. I was on CM7 and I installed build 16 of this ROM. I did wipe data and cache before installing. I then installed the google apps and rebooted. The welcome to SGH-I897, touch the android to begin screen came up but when I clicked it it says "Unfortunately, setup wizard has stopped". So I rebooted into recovery and installed the google apps fixer and rebooted and the same thing happened. I can't even get past it, and I don't know what to do.
 

RockRatt

Senior Member
Aug 1, 2010
4,101
3,711
I'm sorry if this a noob question, but I've only ever flashed this phone once before. I was on CM7 and I installed build 16 of this ROM. I did wipe data and cache before installing. I then installed the google apps and rebooted. The welcome to SGH-I897, touch the android to begin screen came up but when I clicked it it says "Unfortunately, setup wizard has stopped". So I rebooted into recovery and installed the google apps fixer and rebooted and the same thing happened. I can't even get past it, and I don't know what to do.

Try going to recovery and flashing the complete rom again, then before rebooting flash the gapps package also. Then reboot. Sometime it takes two flashes to get everything working as it should.

Sent From My KickAss ATT SGS2 SPORTING CM7
 
  • Like
Reactions: 6speedg35

6speedg35

Member
Mar 21, 2011
6
0
Try going to recovery and flashing the complete rom again, then before rebooting flash the gapps package also. Then reboot. Sometime it takes two flashes to get everything working as it should.

Sent From My KickAss ATT SGS2 SPORTING CM7

i'll try that, does it matter that i'm installing all of these from the "sd card" and not the "internal SD card"? Also, does it matter if my SIM is in the phone? I just took it out and put it in my backup iphone because i'm waiting for a call.
I tried it a few times installing the ROM then Gapps then rebooting and I even tried installing the ROM,Gapps and Gapps fix all before reboot and I get the same thing. I have a pic of my screen right before I reboot, but I can't post it up.

img13.imageshack.us/img13/943/photogoe.jpg
 
Last edited:

RockRatt

Senior Member
Aug 1, 2010
4,101
3,711
i'll try that, does it matter that i'm installing all of these from the "sd card" and not the "internal SD card"? Also, does it matter if my SIM is in the phone? I just took it out and put it in my backup iphone because i'm waiting for a call.

When you say sdcard, are you saying it as the removable sdcard (emmc) or are you saying sdcard as in the 16Gb (11Gb usable usually)? I would put them kn your sdcard (NOT the removable one) to be safe. I have flashed things from my removable sdcard but normally dont try it that way. One less thing to go wrong.
As far as sim card i bavent ever removed it while flashing cm7 ever, since my cappy days and now my SGS2.

Sent From My KickAss ATT SGS2 SPORTING CM7
 
  • Like
Reactions: 6speedg35

6speedg35

Member
Mar 21, 2011
6
0
When you say sdcard, are you saying it as the removable sdcard (emmc) or are you saying sdcard as in the 16Gb (11Gb usable usually)? I would put them kn your sdcard (NOT the removable one) to be safe. I have flashed things from my removable sdcard but normally dont try it that way. One less thing to go wrong.
As far as sim card i bavent ever removed it while flashing cm7 ever, since my cappy days and now my SGS2.

Sent From My KickAss ATT SGS2 SPORTING CM7

Well I've now tried it from both places and am still getting the same thing. I even got into settings from the notification pull down and tried to set up my google account but it fails, saying Gapp something or another has closed.
 

RockRatt

Senior Member
Aug 1, 2010
4,101
3,711
Well I've now tried it from both places and am still getting the same thing. I even got into settings from the notification pull down and tried to set up my google account but it fails, saying Gapp something or another has closed.

Ok next question, wbat version of gapps are you trying to use? There is a NEW gapps from february 15th for ics. Maybe try that one. You can download it via rom manager, then go into cwm and go to clockworkmod and keep following it until you see where the newest gapps was downloaded to, then flash that one. Also what I would do is this, go to cwm after the newest gapps has downloaded, then wipe data/factory reset, flash the ics build, then flash the newest gapps before rebooting. Make sure you have backed up all your apps via titanium backup so you can restore USER APPS ONLY. Once you get everything up and running correctly you can then use titanium backup to restore anh NEEDED USER DATA associated with the apps. No system apps for sure. This is what I would try at least. Hope you get it figured out.

Sent From My KickAss ATT SGS2 SPORTING CM7
 
  • Like
Reactions: 6speedg35

6speedg35

Member
Mar 21, 2011
6
0
Is there anywhere online I can download it from? I can't get past that welcome screen. Also I have all the free versions of everything so I don't think I get updates in my rom manager. I'm also a bit confused, I thought cwm stood for clockworkmod? The gapps that was in my rom manager is "gapps-gb-20110828-signed.zip" for android 2.3.5.
 

kangi26

Retired Forum Moderator
Nov 8, 2006
6,360
3,138
Seattle
Is there anywhere online I can download it from? I can't get past that welcome screen. Also I have all the free versions of everything so I don't think I get updates in my rom manager. I'm also a bit confused, I thought cwm stood for clockworkmod? The gapps that was in my rom manager is "gapps-gb-20110828-signed.zip" for android 2.3.5.

If you take a look in the OP, I have DL link to gaaps 20120207
 
  • Like
Reactions: 6speedg35

6speedg35

Member
Mar 21, 2011
6
0
Thanks everyone, I think it's working now :) I got the gapps-ics-20120215-signed.zip and installed that. I was able to setup google sync and everything seems to be working. Now I'm going to try downloading titanium backup and see how that go's for restoring my apps.
 

RockRatt

Senior Member
Aug 1, 2010
4,101
3,711
Thanks everyone, I think it's working now :) I got the gapps-ics-20120215-signed.zip and installed that. I was able to setup google sync and everything seems to be working. Now I'm going to try downloading titanium backup and see how that go's for restoring my apps.

Glad you got it working, the gapps you were trying to use was for gingerbread/CM7 Gapps. Also even with rom manager free you should be able to download gapps. The only things that you cannot do is things like CM7 with the free version of rom manager. Just looked and there are four roms that are in premium and gapps and alot of other roms/items are in the free section so you can always grab them from there.

Sent From My KickAss ATT SGS2 SPORTING CM7
 
  • Like
Reactions: 6speedg35

singlebeam

Senior Member
Oct 15, 2010
288
33
State of Jefferson
I've been using CM9 from build 1 and have never seen a CM bootanimation. Some have inferred that they see it but I always get a second At&t logo. I just wanted to make sure something fishy isn't going on with my /boot partition....is everyone else getting the second ATT logo as well?
 

kangi26

Retired Forum Moderator
Nov 8, 2006
6,360
3,138
Seattle
I've been using CM9 from build 1 and have never seen a CM bootanimation. Some have inferred that they see it but I always get a second At&t logo. I just wanted to make sure something fishy isn't going on with my /boot partition....is everyone else getting the second ATT logo as well?


What I get is a AT&T logo, a quick flash, and then it comes again.
If everything if working well for you, I wouldn't worry about it

Sent from a autonomous device
 

ClownTrigger

New member
Jun 24, 2011
4
0
On build 15 and 16, my phone won't charge while in car mode in the car dock. It goes into car mode just fine, audio reroutes fine, just won't charge. If I plug the charger directly into the phone, it charges. The dock is fine because it used to work before I switched from stock GB. If you look at a micro USB plug closely, the power pins come into contact with their mating pins in the phone before the data/ID pins do (by design) and interestingly, if I engage the plug on the car dock slowly enough, so that the power pins engage but not the data/ID pins, it will charge, and if I continue to engage the connector, it will continue charging but never go into car mode. Anybody else have this issue?

---------- Post added at 11:32 AM ---------- Previous post was at 11:11 AM ----------

Also, my audio out clips when playing back some songs. It's most apparrent with Pandora, but also happens with Google music, and Spotify. Adjusting the preamp level in voodoo controls or turning down the system volume have no effect. It's like the audio is clipped before it even makes it to the DAC. It happens on both the headphone jack and the USB port in car dock mode, regardless of what's plugged in.
 

JonnehXD

Senior Member
Nov 7, 2011
75
5
Baltimore, MD
Alright, so I forgot the pattern for my lock screen and my data / wifi are both turned off, so it won't let me sign in via a google account.

I'm locked out of my phone right now. Is there anything I can do? I have a backup made from before I turned on the pattern lock, should I just flash back to that?
 

brianray14

Senior Member
Jan 29, 2011
960
179
Bradenton
Alright, so I forgot the pattern for my lock screen and my data / wifi are both turned off, so it won't let me sign in via a google account.

I'm locked out of my phone right now. Is there anything I can do? I have a backup made from before I turned on the pattern lock, should I just flash back to that?

Sounds like your only option is to reflash to me

Sent from my SGH-I897 using xda premium
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    This thread is for the support of CM9 ICS release by CyanogenMod

    This is NOT an official CyanogenMod thread, and isn't officially supported by CyanogenMod or Teamhacksung.

    This thread is designed to help keep the dev thread clean and clear for the dev's to do their magic. So please feel free to ask any questions about the ROM, but flaming will not give great results and will be reported

    The main CyanogenMod CM9 ROM thread is HERE

    The Nightlies can be found here

    GAAPS can be found here
    Look for 'gaaps-ics-********-signed.zip'

    Modems for ICS:
    http://soggycashew.weebly.com/cm7miui--ics-modems.html
    Modem Coverage Map:
    http://soggycashew.weebly.com/modem-location-map.html
    ONLY USE THE MODEMS MADE FOR CM7/Miui/ICS.



    Give the ROM thread and this one a good read before you post, you may find the answer is already available. Keep in mind that each device may behave slightly different, so YMMV

    People have found different ways to successfully install, and it works for them, but their method may not work for everyone. So it is highly suggested to follow the method recommended by the developers.



    This is copied directly from the dev OP:

    "-First time flashing ICS to your Captivate (or coming from another ROM)?

    1. Root your device and install ClockworkMod Recovery.
    2. Reboot into Recovery using 3-button-combo
    3. Do a Nandroid backup!
    4. WIPE (wipe data/factory reset + wipe cache partition)
    5. Install the ROM from internal sdcard using ClockworkMod Recovery
    6. Optionally install the Google Addon
    7. WIPE again or Calendar Sync will not work

    -Upgrading from CM7?
    1. Do a Nandroid Backup!
    2. WIPE (wipe data/factory reset + wipe cache partition)
    3. Install the ROM from internal sdcard using ClockworkMod Recovery
    4. Optionally install the Google Addon

    -Upgrading from another CM9 (or teamhacksung) Build?
    1. Do a Nandroid Backup!
    2. Install the ROM from internal sdcard using ClockworkMod Recovery
    3. Optionally install the Google Addon

    Note: The upgrade process from CM7 to ICS is automatic, but downgrading from ICS to CM7 (or restoring Nandroid) requires flashing twice. Once from ICS and again from CM7's recovery."


    FAQ

    The FAQ is available on Teamhacksung's Wiki. Please read before asking any questions and please feel free to edit it.

    http://teamhacksung.org/wiki/index.php/Experimental:GT-I9000:Frequently_Asked_Questions


    Known Issues

    Please check the list of known issues before reporting bugs.

    http://teamhacksung.org/wiki/index.php/Experimental:GT-I9000:Known_issues

    Reporting Bugs

    You are allowed to report bugs ONLY in the Development thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
    Grab a logcat right after the problem has occurred.
    If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow.


    Thanks to the entire CyanogenMod Team for creating their magic for our aging Captivates!
    2
    Ok, so before flashing Build 15 I decided to check out the other ICS rom out here (rc4) just for funzies. Turns out not a great idea. Flashed the rom and it su decides to deny every permission required app. Its up to date too, whatever I didnt want to deal with it and decided to flash back b15 (yes I followed instructions from OP) but I get an error:
    getprop("ro.product.board") == captivate
    ...
    E:Error in /sdcard/update.zip
    (Status 7)
    Installation Aborted.

    According to google, some say status 7 is an out-dated CWM Recovery I think. Well, I thot I dont mind going back to stock and then working my back to ICS but the new ClockWorkMod app is weird. It says it doesnt support Captivate (MTD) and to use the already installed recovery which I wouldnt have if I go back to stock, right?

    A little confused, hopefully somebody can throw some advice my way. Oh btw, I can still flash the RC4 file thru recovery without error.

    Just flash this kernel reverter/kernel cleaner, then BEFORE you reboot flash the THS CM9 and it will NOT give you tje get prop error.
    The error bappens because once you flashed the other ics it makes you phone read as a i9000. NO NEED TO FLASH STOCK. http://db.tt/o1IOmK4d

    EDIT: Just noticed you got it working. Just keep tjis kernel reverter handy and it will get you past those get prop issues kn the future for cm9.

    Sent From My KickAss ATT SGS2 SPORTING CM7
    2
    I have been running ICS port from Teamhacksung since beta three and have had no issues with it at all, guess I am one of the lucky ones. When flashed b13 all was great and then I got Sleep of Death the next morning. I flashed Glitch Kernel and all was solved. But Glitch is Glitchy. LOL. Well I am on b14 now testing it and this morning was Sleep Of Death. I dont want to flash Glitch because the stock Kernal is pretty sweet. Does anybody have an Idea why it is doing this and if there is a cure? This only takes place when plugged into a A/C adapter not to my PC.
    Thanks for the help.

    The charge death problem could be due to a hot battery. Is the phone warm/hot to the touch when it first dies? The wall charger charges the phone faster by supplying a higher voltage. This can cause the battery to get hotter than charging at a lower voltage. The battery in our Captivates is designed to stop charging if it gets too warm. Based on recent evidence, it appears that at least on the teamhacksung ICS ROM, it may also be causing the phone to "die." The battery shut down feature is to protect the phone and you from the battery starting a fire (such as has happened with some iPhone's recently).

    If your battery is overheating, there are two potential causes. The first is that your charger/cable may have issues and need to be replaced. I have read of at least one person solving the charge death problem by replacing their charger. The other cause could be the battery itself. As the battery ages, it becomes less efficient and it is possible that it is getting hotter when charging now than it did when it was new. If this is the case, a new battery could solve the problem.

    edit: To clarify, you mention that your problem only happens when charging on the A/C charger. This means you have a charge death, not a sleep death. People who have sleep death have their phone die when not using it (and not charging it). Sleep death is a completely different problem that is frequently fixed by changing the lowest clock setting to a higher speed (200 - 400 Mhz) or increasing the minimum voltage at the lowest clock speeds.

    The sleep death is a recognized problem by AT&T and Samsung which caused them to replace phones that have the issue in Nov/Dec 2010. A update was released around that time that provided a software "fix" for the sleep death. It is theorized that the software fix was an increase in speed or voltage (or both) to prevent sleep death.
    2
    Was wondering if anyone was having any wireless download speed problems? I am currently getting 200kbps down and 4.5mb upload (huge difference, obviously).

    Running stock everything on build 15 with no kind of wireless fixing applications installed.

    Thanks in advance for any help provided.

    Take a look at a new modem. You can find one here
    Also, take a look here There is a map that can give you some ideas as to which modem works (according to other users) in your area
    2
    On build 12, Gapps v7.1: I'm getting ""App x" could not be downloaded due to an error. (-101)". I've tried clearing the market's data, but no change. Any ideas to fix this?

    Thought I'd share what fixed my issue, in case it helps someone else...

    - removed my Google account from accounts menu
    - re-added my account
    - reboot
    - issue solved, and no need to flash the fixer

    Sent from my SGH-I897 using xda premium