Last night my battery died. So I recharged it and after fully charged I turned it on. My phone booted up but it was in a force close loop and continuesly placed itself in airplane mode. I had to reflash my phone. What would of caused this?
Using cm7 rc1 w Trinity kernel
Sent from my Nexus S using XDA App
Ok, for an update...the root cause of this is when I place the power widget 2g/3g toggle in the status bar pull down menu. Toggleing this causes a force close loop upon reboot. I reverted back to a saved back up and reproduced the problem again.
Anyone else have this problem?
Yes I have the same problem, cm7 RC4 + jame bond kernel. Also adding settings in power widget to toggle 3g/2g result in force close loop.
that issue have been there for me too... and I think almost for every one, I use widgetsoid to have that toggle... hoping that cm7 final fixes that.
Hallo, I'm a newbie, I use the CM7 and I have the same problem. Has anyone solved the problem during this period?!?
Thanks!
Alberto
Nexus S
NSCollab 1.0.21
It is a known issue and is logged in the CyanogenMod issue tracker.
http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority
If you want to see the issue fixed then click the link and star the issue.
Sent from my Nexus S using XDA App
Same issue on CM7#159, had to do the workaround in post 97-99 in the google issue tracker.
Related
I have searched and found nothing exactly like this so here I am.
My phone was 100% charged prior to going to bed last night, I wake up this morning and the battery icon is red. I unlock the phone, and see that I have (no service.) A few seconds later I see a force close, SORRY! process com.android.phone has stopped unexpectedly, please try again...BLAH BLAH.
It just keeps force closing, and I close it, then it comes back, again and again.
While this is happening, I went to settings and noticed that airplane mode it repeatedly turning on and back off during this whole force closing problem.
I have had this happen before and forgot how I got it to stop. I have wiped everything and tried and still same thing. I know for a fact that last time this happened I DID NOT re flash the rom or anything. Nor do I want to now, im hoping someone knows the simple solution for this.
Thanks.
UPDATE, actually turning airplane mode on will stop the force closing loop, but once I turn it back off, it still has the force close
If you are running cyanogenmod it's a bug due to toggle 3g/2g. To solve your problem you need to flash cm7 again. Then the FC will stop
Sent from my Nexus S using XDA Premium App
I am running cm7, and now that i think of it, yesterday I added the toggle 2g/3g button to the drop down notification bar... it didnt start to force cloe right after that though, it was like 8 hours later.... weird..
Michigan Jason said:
I am running cm7, and now that i think of it, yesterday I added the toggle 2g/3g button to the drop down notification bar... it didnt start to force cloe right after that though, it was like 8 hours later.... weird..
Click to expand...
Click to collapse
Yes, the FC starts right after the first reboot
Sent from my Nexus S using XDA Premium App
Hello,
I finally managed to flash the Cyanogenmod 7 made by mik_os on my LG Optimus One, but I noticed that if my phone is off and I plug the charge cable It automatically powers on and boots up.
I found out that my settings are resetting after each reboot (f.e. the keyboard resets to the default one when before I had set smart keyboard pro as default).
Could you tell me if these are known bugs and if there's a way to fix them? Or do I have to wait for the next releases of the Mod?
Thank you in advance, I apologize for my poor english skills.
Hi, move the keyboard app on the phone, probably you have installed it on the sd card.
bye d.
Hehe, thanks for your advice silsha, It worked. I really can't understand how I could not find it out by myself!
Thank you so much.
Though, I'd like to fix the charge bug aswell, as it was (and still is) the more annoying problem.
and it will remain for some time cause it's a kernel problem
I would like to know how this stuff works. How can the problem be the kernel when the phone is off?
well normaly when u charge your phone (being off) the kernel loads some parts for u to see those icons on screen that is charging
but having those problems kernel just boots up your phone
Ok, so hopefully this will be fixed in the official release of the mod, right?
Sent from my LG-P500 using XDA App
I think this is a non issue. Can be a bug, but also a feature!
The only problem I see here is if the battery is to low to boot the whole system.
In this case to charge it without booting you can do it in the Custom recovery (AmonRa or Clockworkmod).
is there a fix for these now? just installed cm 10.1
There is an option in battery 'wake up the phone when charging',coz it is not working properly it restarts the phone.If it is selected unselect that.Try and see if this works.
Occasionally my data connection will become either stuck on or off and this affects wifi as well.
When this happens I try to reboot my phone and it will begin to turn off then freeze requiring a battery pull (stuck on black screen and power button can turn on and off ctr animation visible). I'm on TMOUS and have had this issue with multiple roms and radios. Anyone the experienced this?
Sdobron said:
Occasionally my data connection will become either stuck on or off and this affects wifi as well.
When this happens I try to reboot my phone and it will begin to turn off then freeze requiring a battery pull (stuck on black screen and power button can turn on and off ctr animation visible). I'm on TMOUS and have had this issue with multiple roms and radios. Anyone the experienced this?
Click to expand...
Click to collapse
I had this happen when using Juice Defender. I also had this when I flashed the old version of CWM before it was fixed (the first night that S-OFF came out). Are you using either of the two? If not, you might want to reset the phone to factory settings. That usually fixes errors for me when I am stock. (No root or mods done).
Matt
Cwm from Koush.. 4.0.1.5 and no juice defender. Might be the OC daemon as well. Didn't experience it at all on IC 2.0.
I have a problem with my MIUI music player.
- The first song plays just fine, however when it goes to the second song, it gets stuck on buffering... Force close does not fix it, the only fix is rebooting the phone..
I only notice this when the screen is off...
I'm running RG2X with Faux kernel..
Also, APN is gone when I put in airplane mode, and it stays gone until I restart.
Never had that problem with music and never put airplane mode on so I don't know.
Sent from my LG-P999 using xda premium
I also never have that problem, sorry.
Just installed this great rom. Definitely much snappier. Only issue I have is that the wifi does not go to sleep. Anyone else having the same issue.
Never mind. It was an app that kept the wifi on.
tj1772 said:
Just installed this great rom. Definitely much snappier. Only issue I have is that the wifi does not go to sleep. Anyone else having the same issue.
Never mind. It was an app that kept the wifi on.
Click to expand...
Click to collapse
my dear friend can you please answer mw which was this program because im having this problem with all the latest nightlies and the 1.0.0.it has a wifi depp sleep issue and after many hous is frozen and i must rebooted with vol up+power button..i asked everybody about this problem but nobody till now told me what is going on..thanks in advance!greetings from greece..
I also have the same problem. Wifi never sleep and no apps or services are running.
This happens to everyone. Battery stats say wifi never sleeps, but it does turn off..although it seems it takes longer than on HC.
Battery life is same/better. It also goes to deep sleep.
I have not had this except when the nightlys got unstable.
did anyone try reverting back to complete factory stock (pushing factory images) and then putting eos on?
I bring this up because I got some crud lock in that factory reset and cach wipes would not clear. afterwards doing the above all was well.
also some live wallpapers and widets can be problematic.
I personally keep a unrooted untouch factory backup around to be able to start from scratch.
the eos 1.0 is rock solid for me except for a few browser crashes. I'm [email protected]