I have been having a very annoying issue since the early builds and continuing until now. The phone app will on occasion stop working completely. I will try to place a call and I can hit the call button or the contact as many times as I want, but the call won't get placed. If I wait 5 minutes or so, then they all get placed simultaneously, which results in lots of calls being put on hold. So basically, sometimes, I can't call anyone. It's extremely annoying because it happens with regularity. Does anyone else have this issue?
CyanogenMod 9 ICS for Captivate Q&A(Unofficial)
- Thread starter kangi26
- Start date
Just want to start of with: Awesome ROM, completely revived by Cappy, was looking for a new phone, not any more.
Quick question, for anyone using their phone to play music in the car via bluetooth, the time elapsed for each song displayed on the headunit does not work properly. Not sure if it's the headunit or the phone, but the time just keeps counting 0...1...2...0....1...0...1...2...3..0..1 etc etc...
Does this happen to anyone else (if not, must be my headunit), or possibly a bug in CM9?
Quick question, for anyone using their phone to play music in the car via bluetooth, the time elapsed for each song displayed on the headunit does not work properly. Not sure if it's the headunit or the phone, but the time just keeps counting 0...1...2...0....1...0...1...2...3..0..1 etc etc...
Does this happen to anyone else (if not, must be my headunit), or possibly a bug in CM9?
I upgraded to the galaxy s ii recently and I actually miss all the settings that come with CM9 
At least I finally got ICS on my S II
I'm back to using my captivate in my car as a GPS since i have the car dock for it, but can't connect to my S II via wifi, but my laptop does work.
Is anyone else having issues connecting their captivate via a wifi connection?
My captivate is running CM9 build 17.
At least I finally got ICS on my S II
I'm back to using my captivate in my car as a GPS since i have the car dock for it, but can't connect to my S II via wifi, but my laptop does work.
Is anyone else having issues connecting their captivate via a wifi connection?
My captivate is running CM9 build 17.
Last edited:
I have to say [knock on wood] i've had great success with this rom, and many of the nightlys. I had an issues with gmail and sync [i guess that was it] a week or more ago, i wiped, wiped, and re-wiped, and cleared all kinds of cache, and flashed and re-flashed. and sync is working again.
I've had issues with 'low memory or space' and i guess i need 80 or more percent free space on my internal memory? I spent some time moving almost every thing i could to the ext SD [which is now 80 to 90 percent full] and everything seems to working like a dream, i've only had to flash the last several nightlys and all is well
---------- Post added at 01:04 PM ---------- Previous post was at 01:02 PM ----------
I upgraded to the galaxy s ii recently and I actually miss all the settings that come with CM9
At least I finally got ICS on my S II
I'm back to using my captivate in my car as a GPS since i have the car dock for it, but can't connect to my S II via wifi, but my laptop does work.
Is anyone else having issues connecting their captivate via a wifi connection?
My captivate is running CM9 build 17.
Do you mean just a regular home wifi connection, I've had great success with that. I also love using my cappy as my regular daily GPS i love it!
ouch
RIGHT after bragging about how i love the ics and no issues BAM!
the [apparently known ] Encryption Unsuccessful 'event' ugh
after much angst, and research, i found and followed cgugino's instructions and got it back up again, limping of sorts, NO internal memory at all fully off the real external sd
[unable to reply to that thread due to the randomness of 10 'helpful posts']
seems like that thread should be a sticky as a warning
RIGHT after bragging about how i love the ics and no issues BAM!
the [apparently known ] Encryption Unsuccessful 'event' ugh
after much angst, and research, i found and followed cgugino's instructions and got it back up again, limping of sorts, NO internal memory at all fully off the real external sd
[unable to reply to that thread due to the randomness of 10 'helpful posts']
seems like that thread should be a sticky as a warning
Did you do a factory reset after you got it? That should be the first thing you try
sorry if this has been asked before but im new to the cappy and im rooted with the newest cm9 nightly and i have to say top notch work !
anyways what the best settings for setcpu ? im looking for battery life mainly OC not really a much please and thank you
anyways what the best settings for setcpu ? im looking for battery life mainly OC not really a much please and thank you
Can't really oc with stock cm9 kernel. You can use glitch or semaphore, but the stock kernel is pretty quick.
Sent from my SGH-I897 using xda premium
Hi peepz:
I'm looking for the easiest way to have my cake and eat too. I have CM9 nightlies installed and working well. I keep a nandroid backup of the previous and current release. This is a repost from the ROM furum.
I would also like to have GINGERBREAD nandroid backup configured so I can restore whichever on the fly via ROM mgr or str8 CWM.
While I'm not new to flashing, I have a few questions:
2- Both ROMS will use the same bootloader (the ATT GB one), so switching roms should be nothing more than just a restoring the backup?
3- creating the GB backup will probably take ODIN/Heimdall back to stock with the att GB boatloader or can i just flash CM7 twice (refering to the OP note)?
4- issues others have ran into previously would be nice.
The end result, is to have ICS as my daily but be able to easlily swicth to GB to be able to use the TV Out function with apps like Nteflix & Hulu.
If you considered this clutter please PM but thought this could spawn a good discussion. Thx for thinking.
I'm looking for the easiest way to have my cake and eat too. I have CM9 nightlies installed and working well. I keep a nandroid backup of the previous and current release. This is a repost from the ROM furum.
I would also like to have GINGERBREAD nandroid backup configured so I can restore whichever on the fly via ROM mgr or str8 CWM.
While I'm not new to flashing, I have a few questions:
1 - How does this statement effect having a backup of CM7 & 9 and switching between the two?
2- Both ROMS will use the same bootloader (the ATT GB one), so switching roms should be nothing more than just a restoring the backup?
3- creating the GB backup will probably take ODIN/Heimdall back to stock with the att GB boatloader or can i just flash CM7 twice (refering to the OP note)?
4- issues others have ran into previously would be nice.
The end result, is to have ICS as my daily but be able to easlily swicth to GB to be able to use the TV Out function with apps like Nteflix & Hulu.
If you considered this clutter please PM but thought this could spawn a good discussion. Thx for thinking.
Having some trouble using ES file explorer to browse the external SD card.
Internal SD card seems to be /mt/sdcard and external SD card seems to be /mnt? ES doesnt seem to find it.
Internal SD card seems to be /mt/sdcard and external SD card seems to be /mnt? ES doesnt seem to find it.
Go to settings-->system-->status bar-->battery status style
Sent from my SGH-I897 using xda premium
Ok I can see the emmc folder using root explorer but not in in ES. Isn't there supposed to be some kind of shortcut like external_sd folder?
Maybe press refresh? The only places you can find emmc is the shortcut at /emmc and /mnt/emmc
Is there a way to turn on charge complete notifications? I know I'm probably one in a million who actually wants it on but I hate not knowing when my phone it done. This is CM9 there has to be an option I'm missing.
Sent from my SGH-I897 using xda premium
Sent from my SGH-I897 using xda premium
Issue With Nightlies
I have been running Build 17 for about a month now and I love it, but figured I would upgrade the latest nightly. I downloaded the 4/22 nightly and the latest Google Apps zip. When I flashed them via recovery, the installation would abort saying there was an error with the zip file. The only thing I did that wasn't mentioned in the instructions was wipe data and cache. I tried again with the 4/19 nightly and got the same error.
To make matters worse, when I tried to flash my Build 17 backup, it just stayed on the opening screen (not ATT, the one with all the colors) for over 90 minutes. I finally pulled the battery and tried again and the second time it worked, but none of my Google Apps would worke. They would all force close.
Thankfully, I can easily flash back to my CM7 backup, but now that I'm used to ICS, I don't care for CM7. I'm working to flash back to ICS, but is there something I need to do differently to get the nightlies to work?
I have been running Build 17 for about a month now and I love it, but figured I would upgrade the latest nightly. I downloaded the 4/22 nightly and the latest Google Apps zip. When I flashed them via recovery, the installation would abort saying there was an error with the zip file. The only thing I did that wasn't mentioned in the instructions was wipe data and cache. I tried again with the 4/19 nightly and got the same error.
To make matters worse, when I tried to flash my Build 17 backup, it just stayed on the opening screen (not ATT, the one with all the colors) for over 90 minutes. I finally pulled the battery and tried again and the second time it worked, but none of my Google Apps would worke. They would all force close.
Thankfully, I can easily flash back to my CM7 backup, but now that I'm used to ICS, I don't care for CM7. I'm working to flash back to ICS, but is there something I need to do differently to get the nightlies to work?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
4This 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
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 CM72
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
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
New posts
-
Development Project Matrixx v10.3.0 - UNOFFICIAL | Android 14 | (rosemary)- Latest: SinhoGamerOfc
-
-
