Database Develop

The Boot Loop of Death (BLOD)

Hey Guys,
Ever since I first experienced this bug, it seems more and more people are coming forward explaining the same symptoms.
Connection drops, OS becomes unresponsive, freezes, and then you are greeted by the 'X' animation. After the phone reboots, it freezes once again and returns you to the 'X' animation and the process repeats until you pull the battery.
There seems to be no direct trigger as it can occur when on a call, when browsing or even when the phone is idle.
I've read through various threads on different forums in an attempt to reveal some kind of pattern, yet reports are coming from users on different ROMs with different kernels and different apps. I've created this thread in the hope that if people contribute their experiences, we can draw some kind of reasoning behind the development of the bug and offer some hope for resolving the issue in then future.
So guys, what are your experiences of the BLOD? What ROM were you running? What kernel were you running? Do you overclock, underclock or remain at stock? Anything you think may contribute to this annoying bug.
Thanks in advance.....

Reserved for future use

My experience began after updating to Kang-o-Rama 0.6 final (CM 5.0.6) after using Kings Desire Port aswell as using Paul's Desire ROM and Cyanogenmod previously. Originally it happened to me in the gym. While listening to music I recieved an SMS and the phone suddenly crashed and went into the BLOD. I had to pull my battery for it to stop. Since that occasion, I began to suffer the BLOD 3-5 times a day, sometimes when on a call and other times when the phone was idle. I tried wiping and reinstalling countless times, flashed stock Cyanogen and the later versions of K-o-R which would give my phone a slight reprieve ,however eventually the BLOD would hunt me down and return.
Eventually I believed it was a Cyanogenmod specific bug, especially after reading this thread,
http://forum.cyanogenmod.com/index.php?/topic/43-odd-crash/
Since I thought it was CM specific I went away and flashed Enom's ROM which again gave me a reprieve but only until I charged the phone at night. I awoke in the early house to find my phone rebooting away as I slept. This pattern continued for 3 nights until last night which was my first BLOD free night.
Now i'm not 100% sure as to what cured my looping last night but I flashed a new kernel yesterday (IR .33.5) and also on the advice of this thread,
http://www.google.co.uk/support/forum/p/android/thread?tid=2711ea74ef3d9aee&hl=en
I wondered whether the fact that I'd started using the stock alarm clock app could have triggered this so called 'notification bug'. I returned to using Gentle Alarm from the market and cancelled my stock Androdid alarm.
Right now i'm waiting to see how long I go without a BLOD before investigating if it was specifically the new kernel or changing the alarm which got me through the night. Will report back if anything changes.

I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done

wesbalmer said:
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
Click to expand...
Click to collapse
Cyanogen posted something regarding it being a system_server crash in the CM thread and that we needed logs of the event occuring before he could draw any conclusions. I managed to dump and adb logcat of the event while it was happening, although it was just a panic loop of which a segment was posted on the Cyanogenmod forum I posted above. Has anyone managed to capture a log of the BLOD as it starts? That would be a great help.

I got my N1 about 4 weeks ago and it worked OK until I flashed the Froyo radio. from that point on I could not get any rom to run in a stable way - my reboots happened 3 - 4 times a day and got to the point where I would get stuck in the boot loop. Pulling the battery did not always solve the problem although I found that if I kept the battery out for several minutes my chances of getting the phone to boot into either the ROM or recovery would be better.
I noticed at the same time that once the boot loop started I could not get into recovery until my phone had at least booted into the ROM successfully once.
Flashing back to the 4.04 radio reduced the random reboots to about once a day - usually at night after I had just plugged my phone in to charge. I was using the stock alarm app as a bedside clock.
After many days of frustration and the help from several people here at XDA, I finally came to conclusion that the problem must be hardware related and am returning my current device to HTC and am getting a new one.

I don't have a boot loop but I definitely experience the initial stages of this problem on a stock (unrooted, locked) N1 (at&t).
50% of the time when the N1 loses the connection (e.g. due to going into a garage) it will not re-acquire the signal. Searching for networks will hang, putting the phone in flight mode and then disabling flight mode will still result in no signal.
The only way to get a cell signal back is rebooting the phone.
Usually, searching for a network and/or enabling and disabling flight mode will result in the phone turning black and then rebooting.

I have the problem, too.
Just a few notes:
didn't have it on stock rom and Cyanogen 5.0.6, nor an Enomther's 1.8.1, started with Enomther's 1.9.2
This is not really a reboot, because a real reboot always helps. Other than a reboot, it starts directly at the X animation, not with the unmoving X before.
Seems to be a kernel panic.
I currently suspect that the panic happens when the RAM is full, especially if there is one single process that uses up massive amounts of RAM (could be in the background, of course).
I yesterday found that Sytrant (periodically sets time using internet time server) has a memory leak, and on closer inspection today found that it queries an ad server every few seconds and thus switches from sleeping to running state every few seconds. Also, it spawns root processes when setting time, which might lead to the system not wanting to kill it.
So, here's my current suspection (I'm not at all sure if that's true!):
The reboot loop only happens when the system runs out of memory.
In this case, Android should normally kick out other programs: First apps that are not running anymore, but are still in memory, second background jobs, and third services.
I guess there's some error in the killing logic in newer Cyanogen kernels and others that use Cyanogen parts (or maybe even in the orginal code from Google).
This somehow leads to a state where the kernel has no memory left and can't kill a process, too. -> Kernel panic
Maybe this is more probable if there is one big memory hog the kernel doesn't want to kill (because it's a service, or maybe because it has children running as root).
So, everyone who has this problem, please get a process monitor or task manager where you can see how much memory an app uses. OSMonitor is a very good one, and it can also sort the processes by memory usage. Start it periodically to find out if a process is constantly growing.
If you found such a process: Is it one that requires root? Does it run as a service? (Unfortunately, OSMonitor can't tell you if a process runs as service, or at least I didn't find it if it can. ES Task Manager can show that information, though, for example.)
Personally, I threw Sytrant off my phone now and will watch if that helps. I had reboot loops every two or three days, so I can't tell yet if it really will make a difference. I really hope so …
Edit: Of course, this theory does not really explain why the network drops before the boot loop starts. It could be, though, that the kernel tries to kill just anything to gain meomry, which might also be a system process that it responsible for the network. As the networks always seems to drop before the loop starts, maybe killing that process is what leads to the panic in the end.
Maybe, could … well, yes, this is just a theory. But at least it sounds good, doesn't it? ;-)

The more I read about this problem here and in other threads, the more I am convinced that my problem is probably not hardware related. My replacement phone arrives today but now I am wondering if I should return my original or not. Argg!
Is there a way we can all band together to try and get to the bottom of this problem? I am more than willing to do whatever testing those that know what to look for tells me to do.
Would one of the Guru's here be willing to guide us through a coordinated troubleshooting excersize?
Maybe we can start by trying to find out what we all have in common?
I have an AT&T/Rogers version of the N1.
I typically have the Facebook, Calendar Widgets on home screen.
Power Widget on 2nd screen
Use gmail but via the standard email client, not the gmail client.
Use the native alarm clock app in the dock at night
16GB ADATA MicroSD card.
I also install:
- ChompSMS (with icon widget on home screen)
- NewsRob (with Widget on home screen)
Did not get the reboots initially running the stock rom but they started the moment I installed paul's version of Froyo. I tried several of the other roms and had the same instability and BLOD's until I reverted back to stock and things stabalized again although I was still getting random reboots once a day or so.

While a hardware issue (especially RAM failure) could cause this issue, I don't think that it is the cause in most of the cases here. The fact that some don't experience it anymore after trying one or another software-related measure makes a hardware failure highly improbable, at least in their cases.
I won't rule that out, but until I tried everything else I can't conclude it must be a hardware faliure.
Please get OSMonitor and watch your processes. If after some days you still can't find a process using more than, say, 65 M, and still get the issue, you can be pretty sure that a memory leak isn't the problem for you.
The memory leak + killing bug guess is a good one and is quite probable. So let's check that first.

I think my FroYo rom problems are the same problems you guys are having. I think it's something with an app or an element of the OS or something.
http://forum.xda-developers.com/showthread.php?t=703508
I get the exact same issue on a handful of roms. Everything starts to force close, then it goes into boot loop, but, as someone said, doesn't really fully reboot, it just starts at the boot screen.
I've also noticed when things get funky, plugging in the USB cable makes it immediately go into a boot loop.

I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.

cmarti said:
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
Click to expand...
Click to collapse
I deleted quadrant, signed into market and all so it knew i uninstalled it, flashed a baked modaco R17, and it still boot looped on first reboot.

I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.

DvTonder said:
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
Click to expand...
Click to collapse
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.

MSigler said:
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
Click to expand...
Click to collapse
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?

DvTonder said:
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
Click to expand...
Click to collapse
The only roms that screw up for me are modded froyo roms. LeoFroyo works fine for some reason, as does the stock FRF50. I'll screenshot my apps in a minute and post them.

I have this on stock 2.1u1 EPE54B

I was getting some pretty random boot loops when running CM 5.0.7.1 and 4.04 radio. Noticed two things could (almost) cause it every time:
1) Not so much a cause, but Google Listen was running almost every time I went into a BLoD.
2) Something that WAS causing it.. I keep my phone on airplane mode at work with WiFi on, since I don't get a reception in the building. Reboot + turn off airplane mode when the phone is to that point = BLoD.
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.

tjsimmons said:
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
Click to expand...
Click to collapse
Did you flash the Froyo version with SP3?

[Q] Some remaining probs with doc 7.6.2

I am trying to get a solution for these 3 problems I am facing with Doc´s 7.6.2.
Maybe it is not a big deal to make it a perfect ROM but these 3 topics are annoying:
I wrote the same message already in Doc´s threat but no answer at all. in 5 min 10 new messages so nobody really takes care for a new question
Hi Guys,
Some problems I do have with the 7.6.2 and for sure I am not alone with these errors.
1 From time to time high energy consumption but sometimes not - this is crazy. One thing I realized when alarm is switched on for all weekdays then it sucks almost 20% in 5h - just in standby mode. Whats wrong here?
2 GPS signal is bad. When you using this tracking tools eg. cardio trainer it looses half time the GPS signal. Was definitely not with older ROMs.
Is that the modem version?
Is this part of the kernel?
3 Bluetooth works but whenever activating and deactivating getting a stupid message about an opp bla bla.
What is wrong?
Who can help?
Thanks
boris03

quite alot galaxy s users have reported issues with the gps reception i used to think its just a driver issue but upon reading into it would seem its related to the antenna. The wifi also suffers from this problem for me it does anyway. you can try out gps booster lite from market it does help outdoors to get a faster fix as for battery issues well im not so sure you would prob better asking in that thread if your still not heard try sending a pm that should work. good luck

boris03 said:
I am trying to get a solution for these 3 problems I am facing with Doc´s 7.6.2.
Maybe it is not a big deal to make it a perfect ROM but these 3 topics are annoying:
I wrote the same message already in Doc´s threat but no answer at all. in 5 min 10 new messages so nobody really takes care for a new question
Hi Guys,
Some problems I do have with the 7.6.2 and for sure I am not alone with these errors.
1 From time to time high energy consumption but sometimes not - this is crazy. One thing I realized when alarm is switched on for all weekdays then it sucks almost 20% in 5h - just in standby mode. Whats wrong here?
2 GPS signal is bad. When you using this tracking tools eg. cardio trainer it looses half time the GPS signal. Was definitely not with older ROMs.
Is that the modem version?
Is this part of the kernel?
3 Bluetooth works but whenever activating and deactivating getting a stupid message about an opp bla bla.
What is wrong?
Who can help?
Thanks
boris03
Click to expand...
Click to collapse
1.) Turn off your lagfix, run stock RFS see if you still get the issue.
Do a fresh install dont add ANY apps other than stock, observe for 1-2 days of battery usage.
2.) GPS is a hit or miss, hardware is broken.
3.) Never had issues with BT, I use it on a day to day basis to pass around files at the office.

Are you using one of those OC kernels? Or any of the suggested kernels for the matter? I was using Super Optimized Kernel for a while and the battery drain was outstanding even on the non-OC versions. Switched to SpeedMod 300hz. Haven't monitored the battery though but it seems better with normal usage. Also, what lagfix are you using? For a time I was using the Ext-4 Overkill lagfix from the ULF and I noticed considerably less battery life.
As Earlz suggested, try disabling lagfixes and tweaks and monitor..then if it is better than before perhaps using a different lagfix would be a solution. Try switching up kernels (remembering to disable lagfixes prior). Try running different launchers too. I'm no expert on how these things work and affect battery life, but this is all based from personal experience.
My GPS never worked from the start no matter what firmware/ROM I'm on so it seems to really be a hardware issue as EarlZ mentioned. If the problem came about after flashing 7.6.2 then try reflashing to stock firmware with repartition and installing 7.6.2 again after clearing cache and factory reset. Somehow that (having a super clean install) usually fixes random problems I get with any ROM. I'm not certain if it will have any affect on GPS performance but it's worth a try.
Bluetooth is still working fine for me. Perhaps the aforementioned clean install advice I gave could remedy this.

Hi there, i rescently installed DJP5 v8.0.1 . And have some problems with it. When i'm making call i hear the other side perfect, but they dont hear me well. Is it some issue with the ROM or ? Have someone else experienced similar problems?

darkfire_bg said:
Hi there, i rescently installed DJP5 v8.0.1 . And have some problems with it. When i'm making call i hear the other side perfect, but they dont hear me well. Is it some issue with the ROM or ? Have someone else experienced similar problems?
Click to expand...
Click to collapse
There is investigation on that one...
For now, it seems to be a modem issue from the stock modem of ADJP5
Flash another modem seems to fix this issue

darkfire_bg said:
Hi there, i rescently installed DJP5 v8.0.1 . And have some problems with it. When i'm making call i hear the other side perfect, but they dont hear me well. Is it some issue with the ROM or ? Have someone else experienced similar problems?
Click to expand...
Click to collapse
Sigh....Thats covered in the main thread for this rom, try a different modem.
Sent from my GT-I9000 using XDA App

[Q] Touch buttons dont work after call

Hi everyone
A issue I have noticed on mine and brothers phone
Basically, after a phone call, the touch bottoms (menu and back buttons) dont work sometimes, they just freeze and dont work.
It doesnt happen all the time, maybe 1 or 2 times a day. It requires a restart of the phone by taking the battery out
Just wandering if anyone has experienced this problem on there note and whether it is a software or hardware problem. Buttons work fine at all other times, but sometimes after a call they just freeze.
Thanks

coola71 said:
Hi everyone
A issue I have noticed on mine and brothers phone
Basically, after a phone call, the touch bottoms (menu and back buttons) dont work sometimes, they just freeze and dont work.
It doesnt happen all the time, maybe 1 or 2 times a day. It requires a restart of the phone by taking the battery out
Just wandering if anyone has experienced this problem on there note and whether it is a software or hardware problem. Buttons work fine at all other times, but sometimes after a call they just freeze.
Thanks
Click to expand...
Click to collapse
Same problem here! I don't need to take out battery, just reboot device
Any idea? Root? What ROM?

This thing has too many troubles for users. Just got mine but haven't used it yet. Samsung hasn't made a good phone so far. Problems left to right. Note could be my last Samsung phone.

i have noticed the same thing too, but i am running Sheep Rom, it seems intermittent. what rom are you running?

coola71 said:
Hi everyone
Basically, after a phone call, the touch bottoms (menu and back buttons) dont work sometimes, they just freeze and dont work.
Click to expand...
Click to collapse
I used to have issues with my prior android phone if I got dirt or whatever over the proximity sensor.
Android phones disable the touchscreen/buttons during a phone call so your cheek doesn't hang up the phone.
If your phone is dirty, however, it gets confused, and keeps things disabled after the call.
This happened to me fairly often when I had a case/screen collector that tended to collect pocket lint.
- Frank
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
CyberGhos said:
This thing has too many troubles for users. Just got mine but haven't used it yet. Samsung hasn't made a good phone so far. Problems left to right. Note could be my last Samsung phone.
Click to expand...
Click to collapse
You can't be bleeding edge without some bleeding.
The GNote ain't perfect and it's a bit rough on the edges, but there's no way I would trade it for any other phone.
- Frank

ChodTheWacko said:
I used to have issues with my prior android phone if I got dirt or whatever over the proximity sensor.
Android phones disable the touchscreen/buttons during a phone call so your cheek doesn't hang up the phone.
If your phone is dirty, however, it gets confused, and keeps things disabled after the call.
This happened to me fairly often when I had a case/screen collector that tended to collect pocket lint.
- Frank
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
You can't be bleeding edge without some bleeding.
The GNote ain't perfect and it's a bit rough on the edges, but there's no way I would trade it for any other phone.
- Frank
Click to expand...
Click to collapse
This. You shouldn't go Samsung or Android if you don't want to do some finetuning. If you want an out of the box solution take buy an iPhone. Then you can wait for Apple to release updates instead of being able to fix it yourself the same day.

i agree, its not even a hardware problem, its a software problem. i can accept small glitches as long as i can fix them, unfortunately you cant fix a hardware malfunction with software, unless of course the patch your applying is going directly over the antenna like a certain iGadget4

coola71 said:
Hi everyone
A issue I have noticed on mine and brothers phone
Basically, after a phone call, the touch bottoms (menu and back buttons) dont work sometimes, they just freeze and dont work.
It doesnt happen all the time, maybe 1 or 2 times a day. It requires a restart of the phone by taking the battery out
Just wandering if anyone has experienced this problem on there note and whether it is a software or hardware problem. Buttons work fine at all other times, but sometimes after a call they just freeze.
Thanks
Click to expand...
Click to collapse
Hi
Even i am facing the same issue n need to know what is the sol. If it is a hardware issue should i get my phone replaced. I bought it only yesterday.
For me too it happens occassionally and requires restart of the phone.
Please help someone.
Just a guess - if all users r not facing it is it a hardware issue

I had this happen once after about 4weeks of using sgn. I don't know if i had made a call prior or what, just before it happened. A reboot made the problem go away for an hour or so. It came back.
I had installed an app a few hours earlier (dell store mobile app). I removed it - not really expecting to fix it. . . It didn't.
After some futzing, I rebooted into cwm recovery: flushed dalvic cache and fix permissions and rebooted. .. it has been working ever since.
This has happened only once, a few days ago. I'd wager it is a software issue.
Sent from my GT-N7000 using xda premium

Even I am also facing the same issue on Sheep ROM
Is this a ROM specific issue or Kernel ?

Same problem here !
I have been using the SGN for the past 4 days. I had this problem in the Stock ROM and it remains even after rooting the phone.
This phone/tablet seems to be a premature release with loads of small problems here and there. I guess they plan to remove these errors directly in ICS.

I believe the problem is on the kernel, try to get some that is stable.
If you are on original stick with it, if you have it rooted try to get the newest kernel.
What happen is that the proximity sensor closes the phone screen, and lower the speed of the cpu, in some times the cpu have some collapses and forget, what you need is to control the cpu or turn off the proximitor sensor, something like that.
I dont have that problem, with both official rom and rooted phone with abyssnote.
I hope this help.

It happened with me too, 2-3 times. Few hours ago I was checking a pdf document and I received a call and the other party couldnt hear me well. While he was calling me again everything froze. Neither touch buttons nor the screen was working. I had to take the battery out, since I couldnt turn it off because of the unresponsive screen. This is really bugging me off.

I've had this occur to me twice, first time I was fidgeting with some app I can't even remember which, second time just a while ago (and that's why I went in here searching), right after making a call.
Using the S-Pen to swype-gesture back and menu they work though, it's just the buttons themselves that are dead.
Wouldn't think the proximity has anything to do with it (nice idea anyway) because then the whole screen should be unresponsive to touchm, wouldn't it?
BTW I am using xlite rom now, and maybe I could go for the cache wiping.
EDIT: I had cleared cache partition and dalvik cache this morning, ths afternoon the note has been sitting idle on the desk, 2mA drain according to battery monitor widget estimates, and without any calls the buttons stopped working again...

xinato91 said:
I believe the problem is on the kernel, try to get some that is stable.
If you are on original stick with it, if you have it rooted try to get the newest kernel.
What happen is that the proximity sensor closes the phone screen, and lower the speed of the cpu, in some times the cpu have some collapses and forget, what you need is to control the cpu or turn off the proximitor sensor, something like that.
I dont have that problem, with both official rom and rooted phone with abyssnote.
I hope this help.
Click to expand...
Click to collapse
+1 I'm using Abyssnote kernel too - no problems with soft buttons yet.

anyone find a fix for this yet? i have to reboot my phone after pretty much every call to get the buttons working again. starting to get really annoying
forgot to mention im on stock rom unrooted

Reset and Root - CFKernel and AbyssNote worked for me
n0thingr3mains said:
anyone find a fix for this yet? i have to reboot my phone after pretty much every call to get the buttons working again. starting to get really annoying
forgot to mention im on stock rom unrooted
Click to expand...
Click to collapse
I had rooted and applied CF Kernel to my rom and had faced a few problems. But after wiping and applying CFRoot (latest) again I did not face any problems.
I have had no problems in the past 24 hours.
You can use the guide by Chainfire to root and apply CF Kernel (the best guide ever) and test for a day or two. then try moving to AbyssNote1.4 (I moved because I wanted to test OC)
Before you root and flash kernel, I will recommend factory resetting(since you are unrooted at the moment) and do not install any apps - because that is what actually worked for me.
UPDATE :
I havr started facing button issue on 1.4 AbyssNote as well.

Same problem here not woking :-( :-( :-(
---------- Post added at 06:17 PM ---------- Previous post was at 06:16 PM ----------
How to fix this bug???

So, some news. I've been fighting with a nasty battery drain due to the phone being unable to keep the deep sleep status. In the process I've tried flashing AbyssNote kernel 1.2 (people were saying 1.4 suffered from high drains, and I haven't seen this problem since then... but it's been just a few, so it may be too soon.

ephestione said:
So, some news. I've been fighting with a nasty battery drain due to the phone being unable to keep the deep sleep status. In the process I've tried flashing AbyssNote kernel 1.2 (people were saying 1.4 suffered from high drains, and I haven't seen this problem since then... but it's been just a few, so it may be too soon.
Click to expand...
Click to collapse
I can confirm high battery drains with Abyss 1.4 (revert back to 1.2). But it is the only kernel which don´t suffer "touch buttons bug"

Rooting my phone has turned into a nightmare, can you help me?

Ok firstly I'd like to say I just rooted my phone last week, this was my first time doing it. I decided to do it to get rid of various problems (I was led to believe rooting fixes everything). Some of them went away, some of them stayed, and new ones came up with the rooting.
I was coming a stock LG Optimus 2X P990 with Android 2.3.4 (had been updated because the phone was originally older 2.2.2 I think.. I'm not sure), and rooted to Nova HD Rom (ICS 4.0.4) using this thread : http://forum.xda-developers.com/show....php?t=1508492. Oh also, I'm using SPB Shell launcher.
Problem #1 : Signal interuption. This one is probably the worst problem I have. I rely on my phone a lot as I don't have a ground line I need it to catch all my calls. About 2-3times a day I'll check my phone and I'll have no network. Sometimes the signal bars are frozen, they don't flutuate as I move to different areas. Sometimes there's an X on the signal logo. Either way, where I go inside/outside.. my phone can't get network. At first I tried to activate/de-activate 2G, turning on/off airplane mode to somehow reset the damn thing, but it just won't pickup. Then I tried a reboot, after the reboot.. still stuck at no signal. Then I finnally found how to fix it.. a full power OFF, and back ON. That's right each time I peak at my phone and it seems to be doing this, I need to make a complete shut down to wake his ass off.
Problem #2 : Battery drain. Well after days of reading on the subject apparently rooting my G2X was gonna improve it's battery life. Result is : no difference. I've bought a bunch of apps to try and keep track on what's wrong (BetterBatteryStats, Battery Monitor Pro). Just this morning I unplug my fully charged phone at 7:00:AM, and by 1PM (6hours later) it was done. There was about 1½hours of awake time, and about 50mins of screen on (perhaps half of this was using my 3G internet with various apps), no SMS or Calls. Usually if the phone is kept sleeping it can last about 24hours, do you guys think this is normal battery drain?
Problem #3 : Phone Clock off? Last week I was woken up by my alarm in the morning to find out I was about 40minutes late. Only happened once so far. I checked to see if I had set my alarm incorrectly.. nope, then I saw my phone time.. It was was OFF by 40mins... WTF? I went in the options and everything was fine... "Automatic date & Time" checked. I unchecked/checked it, and it didn't fix it, I had to reboot the phone for the time to come back to normal. Now hopefully that was only a one time problem, only now I have to live with the stress every morning my phones time might be wrong and I'll be late for work.
Problem #4 : Seriously where the hell is my FM radio. I use to listen a lot of FM radio before I rooted my phone , this is a feature I enjoyed. After rooting the FM radio application was gone, I said what the hell I'll just get another app from google play. NOPE, not a single FM radio app (that works). I tried a bunch of stuff, read on the forums and searched google for like 3hours and couldn't believe how much work I had put into such a simple thing.. this is so infuriating. The next day I kept looking but was never able to get anything working.. Oh and every where I look people say "lol why use FM radio when you can stream 1gazillion radio with given apps or whatnot". DAMMMMMMNN CAUSE MAYBE I DON'T HAVE INFINITE DATA PLAN? (In fact I have only 500megs/month). Seriously I'm so mad about this.
Problem #5 : Can't copy MKV files?! . I swear to got now that I rooted my phone each time I try to do something, something ****S UP. I just wanted to plug in my phone and copy some episodes of a serie I watch. Each time I tried copying the files : BAM "Windows Explorer has stopped working". So after another 2hours or so of trials and errors I figured the damn thing out . If I try to copy anything, it works. If I try to copy a *.MKV file, explorer crash. A solution I found is renaming my files to *.****YOU and then copy it and rename it back to MKV after it's done copying. Then I wondered, what if I rename a txt file to mkv, will it crash when being copied? Nope won't crash. So it's not just the extension? But why does it work if I remove the mkv extension.. oh good god how the hell am I supposed to understand anything.
Problem #6 : Can't play that MKV file?. Hey I finnally copied my file, the next day at work during my break I open my phone to watch it and.... well I realised there wasn't any video player included in my ROM, so luckly this time I found apps on the market that could play it. I used MX Player. Oh alright time to watch it? NOPE The video is all laggy and skipping frames like hell. Also audio is off and about each 10sec it mutes as if it was re-syncing the sound. Later the next evening I wasted another couple hours figuring this one out. What comes out often : they say use Dice Player instend! LOL Funny! The damn app won't even open my file!.
Playing with my phone I opened an APP I've pushased : System tuner pro. Looking at the CPU stats I noticed the first CPU was at 1.01Ghz, and the second one was at 216mhz? What the hell? I thought isn't that suposed to be 2x1ghz dual core?. So I cranked up the thing up to 1.01Ghz just like the other CPU, opened MX Player and already my video was almost watchable (a definitive improvement). I went back in System tuner pro, and overclocked the damn thing (even tough I had no idea if it was safe to do so) to 1.4ghz on both cores. Another significant improvement, this time when set this way I could watch my video! And the app onlyl reports a 5Celcius increase so I guess it's fine.
My only problem/question about that is why does each time I reboot my phone does the damn thing turns back to 216mhz? In fact why was it set to 216mhz in the first place? Considering all the problems I have and that I reboot my phone about 10times a day, I can't just go in system tuner the re-set my CPU settings each time?
Hopefully you guys can help me.. I'm exhausted I''ve been searching this forum and the web for the last couple days, I have like 1000tabs open in chrome. Btw this forum is a goldmine for information but damn it's a lot of reading.
Thanks in advance for your help

First, I'd like to say that I admire your keenness to detail in writing all of your issues down. Thing is, most of the problems you have are mainly because you flashed a modified ICS ROM. ICS roms by themselves are in beta stage, meaning there are some things that people compromise in flashing them (such as the missing FM radio), and you flashed a modified one, which might be the reason for certain power saving features such as your 2nd core down stepping to 216MHz.
Thing is, most of those were discussed in the NOVA ICS thread.
I would recommend flashing the more stable ROMs. Temasek's CM7, DjangoManouche by Carburano, Nostalgia by Topogigi (Froyo ROM) are the ones that pop-up in mind.
For a panic button, you can do a smartflash and it will restore all partitions to stock LG (wiping all user data of course).
Anyway, read the threads carefully. The opening posts and the last 5 pages at least. In order to get a feel of user experiences with the ROM.
Goodluck and happy flashing!
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
I also noticed that you mentioned you have a G2X? But you also mention having a P990. If you're on a G2X, you have a different forum section my friend. This forum section is specifically for the O2X.
Flashing an O2X ROM on a G2X may result in softbricks.
(Please disregard my advise about ROM choices if you're have an LG P999 G2X, those are all intended for the LG P990 O2X.)

yea my mistake when I typed G2x.. I meant O2X.
Thanks for the advice.
If I change my ROM will it wype all my user data again? (sorry im a newb at this)

The ROM itself might not. But I highly recommend you wipe your device since you're moving from 1 version of android (ICS) to another (Froyo or GB).

I'd recommend you CM7 (not CM9) based ROMs but since you need the FM radio, they have none AFAIK.. but you can try stock based ROMs that are still in active developments by the dev. Usually they worked just fine and will fix most of your problems.. again, don't use CM9 based..
Now for the network that is constantly disconnecting in background, this bug is actually introduced (at least for me) after the GB update (i assumed because of the changes LG has made to the baseband). There's no surefire fix for this problem.. try different combinations of basebands and RILs.. stick to whatever works for you
For battery, if you're in constant mobile network, 24 hours standby time is incredible IMO.. our battery is just too low in capacity to make it last any longer than that.. my only advice is minimize the number of apps in your device, because some of them always stay in RAM doing god knows what..
Good luck
Sent from my Optimus 2X using XDA

Patbach said:
yea my mistake when I typed G2x.. I meant O2X.
Thanks for the advice.
If I change my ROM will it wype all my user data again? (sorry im a newb at this)
Click to expand...
Click to collapse
Yes it will wipe them.. for baseband changes too.. so if you have apps that you'd like to preserve, back them up before flashing anything.. Titanium backup will do the trick, but some instability issues might appear if you choose to just backup and then restore everything up.. so choose all your important apps and leave the rest.. this way if something is wrong with the rom after restore, you can at least pinpoint which app is causing it
Sent from my Optimus 2X using XDA

amateru said:
I'd recommend you CM7 (not CM9) based ROMs but since you need the FM radio, they have none AFAIK.. but you can try stock based ROMs that are still in active developments by the dev. Usually they worked just fine and will fix most of your problems.. again, don't use CM9 based..
Now for the network that is constantly disconnecting in background, this bug is actually introduced (at least for me) after the GB update (i assumed because of the changes LG has made to the baseband). There's no surefire fix for this problem.. try different combinations of basebands and RILs.. stick to whatever works for you
For battery, if you're in constant mobile network, 24 hours standby time is incredible IMO.. our battery is just too low in capacity to make it last any longer than that.. my only advice is minimize the number of apps in your device, because some of them always stay in RAM doing god knows what..
Good luck
Sent from my Optimus 2X using XDA
Click to expand...
Click to collapse
CM7 has a working FM radio since late last year.
Just an FYI.
----------
Sent from my Optimus 2X

salisbury_steak said:
CM7 has a working FM radio since late last year.
Just an FYI.
Oh great.. that means you wouldn't mind using CM7.. i just don't bother checking for working FM radio app since long ago
why not try Temasek's kang build? I believe it is still the best stability wise..
Sent from my Optimus 2X using XDA
Click to expand...
Click to collapse

is there ICS Roms which are CM7 Based? I figure might as well have the latest version of android...

Patbach said:
is there ICS Roms which are CM7 Based? I figure might as well have the latest version of android...
Click to expand...
Click to collapse
CM 7 is Gingerbread
CM 9 is ICS
The numbers indicate Android's different iterations, so no, you can't
Sent from my Optimus 2X using XDA

CM 7 is a fantastic phone, but it has 2 big problems:
-huge battery drain, specially when you enable Wifi!
-sporadic BSODs...specially when the phone is on charging...
Sadly i had to remove CM7 because i use a lot Wifi...i flashed Topogigi's nostalgia now..good rom
Inviato dal mio LG-P990 con Tapatalk 2

markop90 said:
CM 7 is a fantastic phone, but it has 2 big problems:
-huge battery drain, specially when you enable Wifi!
-sporadic BSODs...specially when the phone is on charging...
Sadly i had to remove CM7 because i use a lot Wifi...i flashed Topogigi's nostalgia now..good rom
Inviato dal mio LG-P990 con Tapatalk 2
Click to expand...
Click to collapse
Which both are solved to about 95% by using etana kernel.
In short CM7 is the most feature complete ROM without sacrificing performance on our phones.
Skickat från min Optimus 2X via Tapatalk 2

Just to give an update I have changed my ROM to a CM7 based rom like u guys said. Temasek's kang build
Problem 1. Signal interuption : problem is definitly solved.
Problem 2. Battery drain : definite improvement, battery now last at least twice longer
Problem #3 : Phone Clock off? : Didn't get the problem again, so solved.
Problem #4 : Seriously where the hell is my FM radio. : Well I got an FM radio app, but I can't make it work. It doesn't pick up the stations..
Problem #5 : Can't copy MKV files?! : Well this is solved yes and no. If I manage to make my computer detect the damn phone, I can copy whatever I want to. Thing is for some reason I can't seem to be able to plug my phone into Mass Storage mode anymore. It worked a couple of times and all of sudden even tough I didn't change any drivers, my computer just doesn't see the phone anymore. I get a "USB Composite Device" with a yellow "!" mark in my device manager.
I tried a bunch of stuff in the options, rebooting the phone and/or computer, nothing worked. I decided to try reinstalling the rom, and boom right after I pluged it in, the USB Mass storage mode worked. Once again after a couple of times it started doing the same thing (yellow "!" mark in my device manager), and no new drive being detected. This time I'm completly clueless on what's going on, and I have no idea what I can do about it.
I'm currently copying files using Samba Filesharing over Wi-Fi, but sometimes I'd prefer using my USB cable, and I just can't...
New problem!!! : I had my phone at work yesterday and pluged in my headphones to listen to music, start my music and the sound was playing in both my heatphone and phone speakers. I tried unplugging/replugging the headphone, now the sound only worked on the phone speaker. Looked up every phone option possible regarding sound or headphones.. couldn't find nothing. I did a reboot on the device, and bam fixed everything. Couple hours later I re-open my phone for music, same problem occured. Had to reboot the device for the sound to be back in the headphones.
Most problems are fixed, I Guess I'm satisfied, but damn can't everything just work...

JuiceDefender Premium will make it that your device loses 1% every 10 hours if screen is off.

Stock 20Q from LG is free of bugs and full of functions.

Might be a stupid advice,
but you do know that you need your headphones plugged in for FM radio? (they are the actual antenna)
In the settings you can also set your region (e.g. North America or Europe), since the frequencies differ a bit (e.g. Europe uses 0.1MHz 'jumps' and some regions 0.2MHz).

Zorkman said:
Might be a stupid advice,
but you do know that you need your headphones plugged in for FM radio? (they are the actual antenna)
In the settings you can also set your region (e.g. North America or Europe), since the frequencies differ a bit (e.g. Europe uses 0.1MHz 'jumps' and some regions 0.2MHz).
Click to expand...
Click to collapse
yea I know all of that don't worry.
The FM radio app is pretty buggy, today I made it worked. Once the app was started with the station selected, I hit the home button then I pulled down the tray and click on the FM app from there. All of sudden I started hearing sound.. it had worked.
Turns out the app is also the source of what is messing my headphones up. When I close and re-open the app, the sound will come out from the phone speaker, and that messes up every sound from the phone then on.

Patbach said:
yea I know all of that don't worry.
The FM radio app is pretty buggy, today I made it worked. Once the app was started with the station selected, I hit the home button then I pulled down the tray and click on the FM app from there. All of sudden I started hearing sound.. it had worked.
Turns out the app is also the source of what is messing my headphones up. When I close and re-open the app, the sound will come out from the phone speaker, and that messes up every sound from the phone then on.
Click to expand...
Click to collapse
That FM radio thing is a bug that I haven't heard of actually. When you have the opportunity (or maybe on the next build #94, I'd suggest a full wipe then reflash).

Sleep of Death, FIXED?

Hi guys,
I'm pretty new to the forum, but I've been playing with this phone over the last 2 years. I tried everything to fix the sleep of death, but the only solution I found was to use Captivate Keep Alive. That app drained way too much battery in a short period of time so I was close to giving up until all I did was update my phone, problem solved.
I rooted my phone with SuperOneClick, then installed Cyanogenmod 10 (Nightly) with Devil3 Kernel along with the necessary gapps. Then, I downloaded the app SuperSu, installed it. Lastly, I disabled SuperUser and just kept SuperSu working. Interestingly enough, my phone hasn't turned off in three straight days. Not sure how this fixed my almost 2 year problem, but it worked. Hope it helps everyone else!
Just to add: My phone was updated with a new rom everytime a new release came out. Sleep of Death occured about every hour or so, worst SOD case I've ever seen on a captivate. Just sharing how serious my SOD on my phone was. So happy it lasted three days without a shut down!

ryunbaik said:
Hi guys,
I'm pretty new to the forum, but I've been playing with this phone over the last 2 years. I tried everything to fix the sleep of death, but the only solution I found was to use Captivate Keep Alive. That app drained way too much battery in a short period of time so I was close to giving up until all I did was update my phone, problem solved.
I rooted my phone with SuperOneClick, then installed Cyanogenmod 10 (Nightly) with Devil3 Kernel along with the necessary gapps. Then, I downloaded the app SuperSu, installed it. Lastly, I disabled SuperUser and just kept SuperSu working. Interestingly enough, my phone hasn't turned off in three straight days. Not sure how this fixed my almost 2 year problem, but it worked. Hope it helps everyone else!
Just to add: My phone was updated with a new rom everytime a new release came out. Sleep of Death occured about every hour or so, worst SOD case I've ever seen on a captivate. Just sharing how serious my SOD on my phone was. So happy it lasted three days without a shut down!
Click to expand...
Click to collapse
Hi
So you want to say SuperSu fixed your SOD?
What are the other settings of Devil kernel? Could you please share them
thx!

Yes more info would be nice. Right now I am fighting with my phone SOD about 5-8 times per day. Sucks.

as for me I keep "Captivate Keep Alive" till 70% of battery
then it turns off ..
My battery last about a working day - so it is somehow could be called "fine"...however I would prefer to NOT use wakelock progs....
I'm using Devil kernel too and Lanight ROM.
So please tell us more details: ROM version, kernel version, kernel settings ....etc...

Sorry for late response!
Sorry for the late response guys.
I thought it was the rooting to cm10 and SuperSu that did the trick, but apparently after rooting the phone, I started downloading all the Apps that I wanted to make my phone look cool. As silly as it sounds I installed World Weather app for clock and weather... oddly enough this thing keeps my phone from going to sleep. I realized this because after uninstalling it, going for a different look, I downloaded Rings Digital Weather and my phone started to turn off every 30 minutes again. Let me know if it works for you guys... cuz seriously this was the last thing I would've turned to to fix my phone