Originally Posted by SirBrettrick

Probably safer to stay off alpha ROMs if you're expecting important calls.

Sent from my Captivate

I didn't think I would have this problem up until now..Hopefully this ril file will fix it cuz i love this ROM.. Murphy's Law... Go figure!

Yeah, I got you. Not trying to be rude, I was just saying maybe you should switch to something more stable until you can use your phone more for "play." But the RIL fix seems to be working for others, so good luck with that.

Sent from my Captivate

Just noticed this... when I'm listening to music I looked at my battery consumption info and it shows music taking up battery but also mediaserver so both those together take up about 70-80% of my battery. Is this a bug? I ask because I'm not positive but in earlier android versions I don't think it had media server to drain more battery.

Anyone having aproblem running chrome? I can't get i tto work..gives me an "unable to parse" error
I am trying to run this version given here http://forum.xda-developers.com/show....php?t=1485440
Also it's been so long since the last update :P just saying...

Unable to flash any version of CM (GB or ICS)

---

So, I was running ICS build 16 and while I was goofing with world of goo, the phone rebooted, showing the boot animation for several minutes and refusing to boot normally.

So I dropped the phone into download mode, flashed it to stock 2.1, Master Cleared (which basically formats the phone and does a factory reset), rooted, installed cwm (which was fun because rom manager is not on the marketplace anymore for 2.1 and below and on stock you cant sideload apps).

Upon picking the following versions of CM to install thru the recovery menu (latest GB stable, latest 'official' GB nightly 181, latest unofficial Kang dated a few days ago, and the latest ICS build 16), the phone simply boot loops (it says 'checking for BNL / Auto, the phone reboots, then a bunch of text scrolls on the screen too fast for me to read and reboots, spams a bunch of text, reboots, etc.). The version of clockwork is the last one made for Eclair / Froyo (somewhere in the mid 2's).

I have already done factory resets between each version I tried to install so I dont understand what is going on here. I assume that somewhere along the lines, CM lost compatibility with installing over older versions of Android? I mean, I cant see anything I am doing wrong - flash to stock 2.1, root, install CWM, reboot into recovery, wipe caches and factory reset, install rom. Its as clean as I can get it.

I should also mention, I tried all versions (using the same procedure) with stock Froyo as well with no luck, it does the exact same thing.

I am unable to get into recovery while it is boot looping so I am forced to put the phone into download mode and flash to stock again.

Oh, and I am using Rom Manager to install the latest recovery (although I did try the suggested method on the CM wiki that involves installing the speedmod kernel w/ recovery built in).

Any ideas what is going on here?

Originally Posted by littlewierdo

So, I was running ICS build 16 and while I was goofing with world of goo, the phone rebooted, showing the boot animation for several minutes and refusing to boot normally.

So I dropped the phone into download mode, flashed it to stock 2.1, Master Cleared (which basically formats the phone and does a factory reset), rooted, installed cwm (which was fun because rom manager is not on the marketplace anymore for 2.1 and below and on stock you cant sideload apps).

Upon picking the following versions of CM to install thru the recovery menu (latest GB stable, latest 'official' GB nightly 181, latest unofficial Kang dated a few days ago, and the latest ICS build 16), the phone simply boot loops (it says 'checking for BNL / Auto, the phone reboots, then a bunch of text scrolls on the screen too fast for me to read and reboots, spams a bunch of text, reboots, etc.). The version of clockwork is the last one made for Eclair / Froyo (somewhere in the mid 2's).

I have already done factory resets between each version I tried to install so I dont understand what is going on here. I assume that somewhere along the lines, CM lost compatibility with installing over older versions of Android? I mean, I cant see anything I am doing wrong - flash to stock 2.1, root, install CWM, reboot into recovery, wipe caches and factory reset, install rom. Its as clean as I can get it.

I should also mention, I tried all versions (using the same procedure) with stock Froyo as well with no luck, it does the exact same thing.

I am unable to get into recovery while it is boot looping so I am forced to put the phone into download mode and flash to stock again.

Oh, and I am using Rom Manager to install the latest recovery (although I did try the suggested method on the CM wiki that involves installing the speedmod kernel w/ recovery built in).

Any ideas what is going on here?

Maybe try going to stock GB instead of froyo? Also try changing bootloaders?


Sent from my SGH-I897 using XDA App

Originally Posted by littlewierdo

So, I was running ICS build 16 and while I was goofing with world of goo, the phone rebooted, showing the boot animation for several minutes and refusing to boot normally.

So I dropped the phone into download mode, flashed it to stock 2.1, Master Cleared (which basically formats the phone and does a factory reset), rooted, installed cwm (which was fun because rom manager is not on the marketplace anymore for 2.1 and below and on stock you cant sideload apps).

Upon picking the following versions of CM to install thru the recovery menu (latest GB stable, latest 'official' GB nightly 181, latest unofficial Kang dated a few days ago, and the latest ICS build 16), the phone simply boot loops (it says 'checking for BNL / Auto, the phone reboots, then a bunch of text scrolls on the screen too fast for me to read and reboots, spams a bunch of text, reboots, etc.). The version of clockwork is the last one made for Eclair / Froyo (somewhere in the mid 2's).

I have already done factory resets between each version I tried to install so I dont understand what is going on here. I assume that somewhere along the lines, CM lost compatibility with installing over older versions of Android? I mean, I cant see anything I am doing wrong - flash to stock 2.1, root, install CWM, reboot into recovery, wipe caches and factory reset, install rom. Its as clean as I can get it.

I should also mention, I tried all versions (using the same procedure) with stock Froyo as well with no luck, it does the exact same thing.

I am unable to get into recovery while it is boot looping so I am forced to put the phone into download mode and flash to stock again.

Oh, and I am using Rom Manager to install the latest recovery (although I did try the suggested method on the CM wiki that involves installing the speedmod kernel w/ recovery built in).

Any ideas what is going on here?

Mine did the same thing coming from i9000 based gb. I pulled battery when it started bootlooping, replaced battery, then used vol up vol down power to get into recovery, reflashed ths ics, and it worked perfectly.

Sent from my SGH-I897 using XDA App

Originally Posted by voldomart13

Just noticed this... when I'm listening to music I looked at my battery consumption info and it shows music taking up battery but also mediaserver so both those together take up about 70-80% of my battery. Is this a bug? I ask because I'm not positive but in earlier android versions I don't think it had media server to drain more battery.

Same thing happening to me. Listening to music severely drains battery. At first I thought it was because I was using Pandora or Google Music. So I moved my music to my sd card hoping that would alleviate the problem.. but no dice. Using the stock music app with music on sd card still causes the drain of media server and music.

Originally Posted by J0ESK0

Same thing happening to me. Listening to music severely drains battery. At first I thought it was because I was using Pandora or Google Music. So I moved my music to my sd card hoping that would alleviate the problem.. but no dice. Using the stock music app with music on sd card still causes the drain of media server and music.

i can confirm this as well

Sent from my SGH-I897 using xda premium

hi battery drain by wifi when not connected to network

---

I noticed yesterday what may be a bug. After performing a factory reset I had forgotten to set the wifi sleep policy. This was causing slightly higher battery drain, but as long as my wifi was connected to a network (which it is 95% of the time) there was no noticeable high battery drain.

Yesterday around 4:30 in the afternoon I had about 85% battery left. I then spent about 2 hours away from work/home and more importantly, no where near any wifi access points. I also did not even touch my phone during that time. During that time, my battery drained down to around 40%. When I noticed the low battery much later, the "culprit" in the battery stats was "Android System." It was only by looking at the graph that I was able to see that the high drain was during the period of time that my wifi was not connected (and not using my phone at all). I then checked and noticed that my wifi sleep policy was set to never sleep (so I fixed it).

I don't think that having wifi enabled but not connected should drain so much battery. It seems like the phone spends the entire time actively searching for wifi networks causing excessive drain.