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] Is my Galaxy S more laggy than everyone elses?

I've had a 16gb Samsung Galaxy S on Three in the UK since they launched last year, and it's the only Android phone I've used.
It's pretty laggy, but since I'd read a lot about Galaxy lag online, I assumed this was to be expected.
However, I had to help a colleague with a problem on their HTC Wildfire today (a lower spec phone, as far as I know), and was amazed how much more responsive than my Galaxy S.
It didn't seem to show any of the laggy, hanging-ey behaviour I experience. I have more apps installed than the Wildfire, but I'm quite careful not to install anything that's going to run at startup or cause problems (mostlly just games, no widgets, etc.)
As an example, if I turn the phone on clean, wait for everything to be loaded and ready (media scanning to finish, etc.) then poke the "Market" button, it takes 28 seconds for it to be loaded and responsive. Close that, poke the Facebook button, over 20 seconds until I'm shown the news feed. Sometimes when the phone rings on my desk, I literally won't be able to get it to respond enough to answer the call before the caller hangs up. If I try to switch from program to program, I end up getting quite a lot of frustrating 20-30s hangs and pauses. This is all on a decent wifi connection, so the problem isn't data related.
The question is - how laggy should a Galaxy S be? Would it work better if I added an SD card (with the 16gb phone memory, I didn't see the need)? Is it worth installing a lagfix under Froyo (I tried one back on 2.1, but didn't notice a huge amount of difference)?
Any help would be greatly appreciated!

I think its sometimes very busy rebuilding it's wifi connection. Or some other process.
Am not sure.
Sent from my GT-I9000 using XDA App

I didn't see any speed difference with SD card IN/OUT so i don't think you will have faster phone by inserting it (SD card).

Why don't you try a reset and see if that works? Also are you on eclair or froyo because that would make a world of difference if you upgraded

I just got my sgs from bell Canada last Tuesday. It has all stock with launcherpro and a few Widgets. So far (knock wood) its been a big step up over my HTC dream. I experience maybe 10 seconds of startup lag and then for the rest of the day its awesome. My firmware version is the newest one bell offers (jl2 Frito). What android version are you running?
Sent from my GT-I9000M using XDA App

monkeyhat said:
Any help would be greatly appreciated!
Click to expand...
Click to collapse
That's exactly my experience. The only way to solve it is with a good lagfix and/or flashing JPY firmware
This will get almost instant loading of apps and only minor lags when switching apps. It's still slow when scrolling icons and such... my previous phone, iphoe 3g, is still faster than this crap-phone
Cheers,
Soulbrighter

My Galaxy S was laggy as hell brand new out of the box. Sometimes it would hang for what seemed like 10 seconds. I didn't like the Samsung launcher anyway, so I did my homework, made sure I could get into 3-button download mode, and then rooted, wiped and flashed a custom Froyo ROM. I've tried a few ROMs since then and have landed on Insanity with EXT4 lagfix.
Now my Galaxy S is _awesome_ ... I don't even bother overclocking it, everything is smooth.

try a task killer and set it up to auto kill when screens goes off done a few tests with it ,one with no killer and one with and the one with was faster and had no lag fix running too go to the market and get quadrant standard try it for yourself and see

What's the current firmware you're using ? I suggest flashing to JPY and testing it out.

Update to JPY!
If not possible, install a lagfix on your current ROM/kernel.
The amount of lag you describe is terrible, I have never seen it that bad...

I don't think the lag should be that bad, I did experience some occassional lag back on eclair, but never exceeded 5-10 seconds. Usually after loading whatever that app was once, it'd be okay on the next open too.
Since I've upgraded to JPY i see 1-2 second lag extremely rarely.
Maybe you can get a task manager and see if anything is hogging memory?

Thanks for all the responses. The firmware is FROYO.XXJPO, so I'll definitely try flashing to JPY and will report back! Thanks so much for the tip!

[Q][i9000] Custom Firmware?

I have the 16GB Vodafone UK Galaxy S. Today I was in a city trying to use satnav and it was rank rotten. So I thought I'd see if an upgrade would do it. I was using the very first Froyo that Vodafone came out with - I upgraded to that and hadn't upgraded since. I did have it rooted and 1 click lag fix was on it.
I upgraded to Gingerbread just there, sadly I had to do a factory reset, however it's all working.
I have realised that if I am going to put a custom firmware on it then now is just the right time to do it.
Is there one out there that's stable, and an improvement over the Gingerbread I'm using? Particularly I'd like it to fix the lag (if that still needs fixed) and even better would be fixing GPS/Satnav.

Pinpong blockbuster rom - ticks all your boxes. Get faster fix from market.
Your gps will never be 100% satisfactory in the city, in fact it will probably always be poor - no matter what custom rom you use.

Halkus said:
I have the 16GB Vodafone UK Galaxy S. Today I was in a city trying to use satnav and it was rank rotten. So I thought I'd see if an upgrade would do it. I was using the very first Froyo that Vodafone came out with - I upgraded to that and hadn't upgraded since. I did have it rooted and 1 click lag fix was on it.
I upgraded to Gingerbread just there, sadly I had to do a factory reset, however it's all working.
I have realised that if I am going to put a custom firmware on it then now is just the right time to do it.
Is there one out there that's stable, and an improvement over the Gingerbread I'm using? Particularly I'd like it to fix the lag (if that still needs fixed) and even better would be fixing GPS/Satnav.
Click to expand...
Click to collapse
Have you think about CM7? Great Rom, works well on my phone, and add many new things.

Hi Mate, I tried many custom roms and finally settled for
(ROM)GingerCriskeloV77-9LS-CamHack- SIP + NoIncRing I9000/T/M JVP 2.3.4
Cheers

Well, I managed to get it on. Booting up is weird though, it looks for a long time as if the screen is broken, but eventually ti comes on to the Blockbuster lock screen and then everything is fine. It does seem faster - but I'll only really know when I get to one of those situations where I feel the phone is frustratingly slow.
Thanks very much Woolf!
Time allowing I'll give the other roms a shot, although this Blockbuster one does seem to be good enough for me.

Sadly my phone now reboots constantly. it seems to do it when the screen locks

Halkus said:
Sadly my phone now reboots constantly. it seems to do it when the screen locks
Click to expand...
Click to collapse
Check you got the installation right for that rom, maybe you had to flash a jvp stock first or some similar omission?
Sent from my GT-I9000 using XDA Premium App

Sorry to hear you're having issues. Try flashing to a totally stock JVQ first (with repartition) once you've backed up, then if you don't like that, try a custom ROM. I don't think many JVQ custom ROMs are worth trying if you want a taste of custom ROMs. Better to try CM7 or MIUI for something fast and different.
As a side note, the best tip I've seen for fixing the dreadful GPS we have with the i9000 is to buy a Nexus S or just ANY other phone! Yes, some radios appear better than others, but nobody can prove anything and it's almost all subjective feedback. A drop in the ocean of improvement needed for satisfactory function. If you must use it, a bluetooth GPS receiver and 3rd party navigation app seem the best way to deal with it.

I've now stepped away from Blockbuster. Even doing the a perfect install it crashed often and repeatedly. I did try upgrading to the very latest and that crashed several times in the past hour. Part of the problem was the rom starts with a lockscreen that has a messaging unlock on it, but it isn't set to an app that comes with the rom, so it reboots every time. Sadly that wasn't the only problem, as I was still getting loads of reboots.
So that's out of the way.
I'm now a lot more comfortable using Odin so I'll be able to try other options. I'll try the other two suggested in this thread first of all.
Next to test is CM7.
Thanks for the help folks!
CM7 aborted. Instructions are incorrect, the file they say to download doesn't actually match the instructions so that's out. Plus it clearly states it's not suitable for day to day use... so I don't thnk the time in working out how to fix it is justified since it looks like it wouldn't be useful.
I'm going back to the original question in the thread, to say that I'm looking for something stable. I now think that a custom rom is not the way to go. However some modifications may well be.
Can anyone suggest some kind of lagfix/speedup that isn't a complete overhaul like CM7, Blockbuster etc, that is very stable and that'll make my phone faster?
Edit : Part of what I was doing to install Blockbuster was install Speedmod kernel. So I've gone and put that on, and used the clockwork mod to root it, and also convert to ext4. I think things are looking pretty fast so far. I'm not sure if there's a lagfix for this, but I'm quite comfortable just now footering around - unlike the complete rom I don't feel out of my depth. So I think I'll be ok for now.

Weird "soft restart" / force close???

I am using JVQ Sensation Rom with the JVQ semaphore kernel atm.
I sometimes get some weird "soft restart" / force closes.. no idea how to better name this issue.. let me describe:
The Phone screen turns black, phone vibrates one time shortly, then it comes back to life - media scanner is running, my connection bars show a "stop sign" like they do before or when you don't enter your pin at start.. but shortly afterwards the normal connection bars are shown and I do not have to enter my pin.
If I listen to MP3 or had some other app open at the time of these "soft reboots" they are no longer open and the mp3 playback stops when this reboot occurs.
---
Does anyone have a clue what this could be? I dumped logcat into a file and looked through it myself, but couldn't really find anything on my own.
I cannot really reproduce this error, but it usually happens when I do had a few apps running or had recently used the phone it seems.
I am thinking maybe it could be the garbage collector / memory free thingy that then kills the launcher or something - could that be it?
Or is this known problem or smth? I don't really know what to search for in the search function - I'm sure anyone had this before, but no idea how to find a thread about this error.

Bump this. I was on a vibrant rom (revolution) I have a captivate. I used darkcore kernel and jk4 modem. Worked fine for a while...but did that a couple times a day while I was listening to Pandora on my bt headset.
Sent from my SGH-I897 using XDA Premium App

It's a problem, started from 2.3.3
This problem,affecting all 2.3.3 releases!!
There is also a thread in Q & A section but not many people paid attention to it.
Every 'now and then' phone slows down for moments, till the point that, it reboots itself or give force close or freezes so you have to turn it off.After reboot, it good to go again for ~3-4 days and then again same thing happens.
I read in some threads that darky rom also has this problem but I don't think its darky rom problem but stock Gingerbread itself has something wrong.
If it does not reboot and you don't power it off then you have to wait ~1-2 minutes before its comes back respond.
1. SD card formatting, already ruled out in thread in Q & A. I formatted the card but it simply happens again.
2. Less RAM can also be ruled out as I tried to open as many apps possible without closing them but Gingerbread was doing memory management very well and no freezes.
Expert please give your opinion, how can we get it fixed.

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).