Hi, I've been suffering some random reboots (about 3 per battery cycle) and after every reboot battery goes down drastically. I've changed the ROM and kernel and it still happens. I attach a photo of the battery life (you can see when the 3 reboots happened in the interruptions of the graphic) and a catlog (it's my first catlog so I'm not sure what to do). If you need any more info or the previous part of the log just tell me and I'll provide it.
Mine is a GSM gNEx and now I'm on Rootbox ROM (31/01/13 version) with ak 670.42 dummy kernel but as I said, it also happened in CM 10.1, AOKP, PA and with ak purity, leankernel and franco kernel.
Thanks in advance and sorry for my english.
it could very well be the phone itself. i had something similar happen on my toroplus and havent had the problem since i replaced it.
It could be your chip, but let's look at a couple of things first.
1) Are you dirty flashing by any chance?
2) Have you gone 100% stock and see if it happens there?
Nope, I haven't tried 100% stock, will try tomorrow (after doing my last exam of my degree). Also I've just had a reboot at 82% battery and the first one yesterday was at 82-81%. Is it a coincidence or can it be a hint? Maybe it's the battery...
Also I've been doing a full wipe between ROMS, no dirty flashing except for upgrades on the same ROM (just upgraded rootbox to latest JOP40G)
binlalo said:
Nope, I haven't tried 100% stock, will try tomorrow (after doing my last exam of my degree). Also I've just had a reboot at 82% battery and the first one yesterday was at 82-81%. Is it a coincidence or can it be a hint? Maybe it's the battery...
Also I've been doing a full wipe between ROMS, no dirty flashing except for upgrades on the same ROM (just upgraded rootbox to latest JOP40G)
Click to expand...
Click to collapse
Well I would do 100% stock boot, recovery, ROM etc... and see what it does.
I doubt it's your battery.
My random reboots stopped after I stopped flashing custom kernels. Try a clean install and keep the kernel that came with the ROM and see if you still get them.
Thanks, then tomorrow I'll try going back to stock ROM + kernel and see if it gets solved, if not I'll try with full stock.
Related
Hey all, I have only been flashing custom ROMs onto my G2 for about a month now, so this might be a dumb oversight. Ever since RC4, I have had an issue where every single time I reboot or power off the phone and power it back on, I get the HTC screen for a few seconds and then the CyanogenMod 7 splash screen with the arrow going round and round. And that's it. Even overnight. Now the ROM runs BEAUTIFULLY all the time. No GPS, Google Sych, or Battery Life Issues. Love it, so any help that would allow me to stick with this ROM would be great.
I am running CM 7.0.0
.26 Radio
the base CM7 kernel (2.6.32.28)
Overclocked to 1017Mhz
What should I do to get this issue to stop?
SpeedBlue47 said:
Hey all, I have only been flashing custom ROMs onto my G2 for about a month now, so this might be a dumb oversight. Ever since RC4, I have had an issue where every single time I reboot or power off the phone and power it back on, I get the HTC screen for a few seconds and then the CyanogenMod 7 splash screen with the arrow going round and round. And that's it. Even overnight. Now the ROM runs BEAUTIFULLY all the time. No GPS, Google Sych, or Battery Life Issues. Love it, so any help that would allow me to stick with this ROM would be great.
I am running CM 7.0.0
.26 Radio
the base CM7 kernel (2.6.32.28)
Overclocked to 1017Mhz
What should I do to get this issue to stop?
Click to expand...
Click to collapse
Have you tried a full wipe and then reflash? What rom did you come from? A few details about those things might make it easier for people to help u
dont send me pm's crying about how i hurt your feelings in a thread
I came from the stock post-ota ROM. I did a full wipe when I installed RC4, but I haven't since, just wipe data then re-flash. Should I wipe everything - data, cache, dalvik, etc and then re-flash? Of course Nandroid before...
just cache and dalvik was enough... no data wipe needed (at least.. I haven't needed that before)
But I still need to re-flash the ROM after I clear cache and Dalvik though, right?
Well, apparently, that worked out. Everything is humming along just fine. Thanks a lot for the help everyone.
I having trouble with Aeroevan's CM9 9-05 freezing overnight, completely locking up and requiring a battery pull. I'm coming back to this ROM after using CM10 for a while, then the official CM7.
It's happened several times, last night within a few hours of plugging it in. In one case it must have happened right as I plugged it in because in the morning it had no charge left. The LED is lit (either amber or green) but the phone is completely unresponsive.
I've tried several thing to fix this. At first I just tried different CPU settings and kernels, but it kept freezing. I tried using no kernel (just flashing the ROM an Gapps) but that didn't work. I just tried SuperDuperWipe because I had installed Venom, but that didn't work. I tried fixing permissions but that didn't work either.
Has anybody run into this before? My next step is to flash an earlier CM9 build, then flash over with 9-05. Maybe the 9-05 build is missing something?
I'm S-OFF and running the .320 radio.
roswell_nightlife said:
I having trouble with Aeroevan's CM9 9-05 freezing overnight, completely locking up and requiring a battery pull. I'm coming back to this ROM after using CM10 for a while, then the official CM7.
It's happened several times, last night within a few hours of plugging it in. In one case it must have happened right as I plugged it in because in the morning it had no charge left. The LED is lit (either amber or green) but the phone is completely unresponsive.
I've tried several thing to fix this. At first I just tried different CPU settings and kernels, but it kept freezing. I tried using no kernel (just flashing the ROM an Gapps) but that didn't work. I just tried SuperDuperWipe because I had installed Venom, but that didn't work. I tried fixing permissions but that didn't work either.
Has anybody run into this before? My next step is to flash an earlier CM9 build, then flash over with 9-05. Maybe the 9-05 build is missing something?
I'm S-OFF and running the .320 radio.
Click to expand...
Click to collapse
Ah the infamous lag of death...I had avoided it for a long time, and I never flashed Viperrom. Anyway. I started getting it here and there about two weeks ago and a fresh rom flash usually fixed it. Until yesterday. My phone was absolutely useless and no combination of wipes and rom flashes did anything about it...until I flashed Andybones stock rom. It hurts being on gingerbread, but it is running smooth. I believe other people have done the same and then been able to go back to ICS or JB AOSP roms later successfully. I'm a little hesitant to try myself, but that's the only advice I can offer.
gtdtm said:
Ah the infamous lag of death...I had avoided it for a long time, and I never flashed Viperrom. Anyway. I started getting it here and there about two weeks ago and a fresh rom flash usually fixed it. Until yesterday. My phone was absolutely useless and no combination of wipes and rom flashes did anything about it...until I flashed Andybones stock rom. It hurts being on gingerbread, but it is running smooth. I believe other people have done the same and then been able to go back to ICS or JB AOSP roms later successfully. I'm a little hesitant to try myself, but that's the only advice I can offer.
Click to expand...
Click to collapse
I think SuperDuperWipe got it fixed. I had one lockup and one random reboot since using SDW, and it's been about a week. I consider that stable enough. I had forgotten I used the Viper ROM and needed to "clean the nooks and crannies".
roswell_nightlife said:
I having trouble with Aeroevan's CM9 9-05 freezing overnight, completely locking up and requiring a battery pull. I'm coming back to this ROM after using CM10 for a while, then the official CM7.
Click to expand...
Click to collapse
Try to change the core aeroevan.. I used kernel aeroevan v15 to CM10(Chillybean) with a good result.
Hi,
I bought my Note 2 about 2 weeks ago and kept it to OTA Updates, until recently updated via ODIN and CWM to a few different Original Custom FWs (PA3, RootBox, Carbon, ETC)
Thing is, i like charging my phone overnight, and it just freezes right when i plug it into the charger if the phone is turned off, even if it's on the power block that came with the phone box or via any usb port in my computer.
I've read that it's the kernel, but i've tried many kernels (perseus, limaro, neak, etc) and it always freezes. Also tried different base (official stock roms from sammobile, but i confess i haven't tried charging with stock because i always root it, and cwm it and custom rom it right away, i have no plans on coming back to stock)
I know this is no dealbreaker, but i'd like to be able to do it, since i only like to charge the phone once in a day, and it's when i'm sleeping.
Appreciate any help, thanks in advance.
Bump!
Factory reset.
this is XXXDDDAAA
Try to Charge with any other power adopter. QUOTE=Sojiryu;39628968]Hi,
I bought my Note 2 about 2 weeks ago and kept it to OTA Updates, until recently updated via ODIN and CWM to a few different Original Custom FWs (PA3, RootBox, Carbon, ETC)
Thing is, i like charging my phone overnight, and it just freezes right when i plug it into the charger if the phone is turned off, even if it's on the power block that came with the phone box or via any usb port in my computer.
I've read that it's the kernel, but i've tried many kernels (perseus, limaro, neak, etc) and it always freezes. Also tried different base (official stock roms from sammobile, but i confess i haven't tried charging with stock because i always root it, and cwm it and custom rom it right away, i have no plans on coming back to stock)
I know this is no dealbreaker, but i'd like to be able to do it, since i only like to charge the phone once in a day, and it's when i'm sleeping.
Appreciate any help, thanks in advance.[/QUOTE]
UtkarshGupta said:
Factory reset.
this is XXXDDDAAA
Click to expand...
Click to collapse
I did, CWM Fatory Data/Cache Wipe and didn't work, not sure if it's the same from the rom factory reset option, willing to try (and reinstall everything from scratch) if you or anyone confirms this.
Thanks.
jdomadia said:
Try to Charge with any other power adopter.
Click to expand...
Click to collapse
I did, Doesn't work with the original, or with any other, or USB to PC, just freezes, however it works on stock rom, just not any custom rom.
Thanks.
Try a super wipe and flash back stock rom. We need to cross out custom roms.
Sent from my GT-N7100 using xda premium
UtkarshGupta said:
Try a super wipe and flash back stock rom. We need to cross out custom roms.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
It charges while off on Stock ROM just fine, Just not on ANY CUSTOM 4.1.2/4.2.2 AOSP/AOKP, went to stock and came back to, say Carbon, or Rootbox with no luck, Still unable to charge while off,
Try not to undervolt it...when you try to undervolt too much there will be freezes when you lock the screen.. i had the same problem..
Thats my advice..
Make full wipe and install a custom rom..at the very first boot..try to access to stweak...grant it root pernission...and overvolt every cpu frequency step by+50mV.
Give it a try...i hope i helped you...ifbyes ..plz hit the thanks button..
If you have further question...feel free to pm me..or start a new thread.
Sent from my GT-N7100 using xda premium
It just started happening to me a few days ago on Jedi Master ROM... was working fine for about a month... if the screen stays off for a while or if it's charging for awhile it locks up... have to pull the battery
Have the same problem on slimbean 4.2.2 rom
Wysłane z mojego GT-N7100 za pomocą Tapatalk 4
Similar problem here, whenever screen is off for more than 8 seconds it will not wake up... Any ideas? I am trying stock roms and others, no solution so far...
Same problem with my GT-N7100.
I've tried both CWM & TWRP. It happens after flashing stock ROM to any of 4.3 AOSP based (CM10.2, ReVolt, Carbon, AOKP). When I'm trying to charge in power-off state, empty battery with white circle on center appears and freezes. Device doesn't charge and the only way to boot something (recovery/bootloader/system) is to reinsert the battery.
Changing build-in kernel to N.E.A.K. didn't help either.
I'm out of options. Please help :crying:
Happened here exactly after downgrading from 4.3 custom back to stock Samsung ROM. Of course lost IMEI but I managed to fix it and after applying ARIZA patch all worked well, however I flashed another stock, bit never and freezing started... Out of options so far as well. I will keep trying.
EDIT: Tried suggested in another thread RECOVERY software, however ODIN fails on sboot.bin every time...
My guess - trouble is in AOSP kernel. For example, if you install any AOSP based ROM and then install N.E.A.K. v2.2x SAMSUNG FW kernel (for TouchWiz) - problem goes away. You can't start ROM after that, but that's not the point.
I think we should post our issue in some kernel development discussion, like N.E.A.K. and hope they find solution.
btw 4.2 and 4.3 ROMs both has that issue.
mellax said:
My guess - trouble is in AOSP kernel. For example, if you install any AOSP based ROM and then install N.E.A.K. v2.2x SAMSUNG FW kernel (for TouchWiz) - problem goes away. You can't start ROM after that, but that's not the point.
I think we should post our issue in some kernel development discussion, like N.E.A.K. and hope they find solution.
btw 4.2 and 4.3 ROMs both has that issue.
Click to expand...
Click to collapse
---------------------------------------------------------
Just installed Omnirom 4.4.2 on my Note 10.1 (2012) and am having the same issue. As soon as I dock it / charge it when locked, can't unlock and it appears to crash. I did not have this issue with stock.
Any further progress?
Thanks in advance.
Anybody ever found a solution for this? My note 2, N7100 hangs if charged when switched off.
Only when switched off, I shows the battery with the white circle and that's it.
AOSB KK 1.3.6, 4.4.4, krn 3.0.64-CM, latest modem, TWRP etc.
Brammieman said:
Anybody ever found a solution for this? My note 2, N7100 hangs if charged when switched off.
Only when switched off, I shows the battery with the white circle and that's it.
AOSB KK 1.3.6, 4.4.4, krn 3.0.64-CM, latest modem, TWRP etc.
Click to expand...
Click to collapse
Try Resurrection Remix 4.4.2 KitKat v5.1.5 They fixed it somehow.
plz help
I have note 2 its all fine
but when i turn the screen off for a while the phone freeze and not turning on unless i unplug and replug the battery
this thing happens even in the charger i tried replacing the battery but the same thing
any ideas
I have a used (out of warranty) DINC 2 rooted with Cyanogenmod 7.2 installed (Page Plus). The phone has been working fine for about a month. All of the sudden, the phone will not turn on unless I remove the battery first. If I remove the battery and boot the phone, everything is fine until I turn it off and then it won't come back on. If I do a complete shut-down, then it will turn on. I tried wiping the cache - no help. I tried restoring an old backup that was working at the time - no help. Any ideas? What should I try next to debug this?
Do you have s-off? What version of CM7 are you using (official or custom)? What kernel are you using? Have you tried other ROM's?
brymaster5000 said:
Do you have s-off? What version of CM7 are you using (official or custom)? What kernel are you using? Have you tried other ROM's?
Click to expand...
Click to collapse
Yes, I have S-OFF, it's rooted. Running CM7.2, official, I assume (CyanogenMod-7.2.0-vivow). Kernel version 2.6.35.14-cyanogenmod-g9b2f4dd [email protected]#175. No, I have not tried other ROMs, it was working fine with this one for about 6 weeks and just suddenly this problem started happening.
rh09 said:
Yes, I have S-OFF, it's rooted. Running CM7.2, official, I assume (CyanogenMod-7.2.0-vivow). Kernel version 2.6.35.14-cyanogenmod-g9b2f4dd [email protected]#175. No, I have not tried other ROMs, it was working fine with this one for about 6 weeks and just suddenly this problem started happening.
Click to expand...
Click to collapse
UPDATE: I think I might have figured it out. I borrowed a battery from another phone and it seems to work fine with a different battery. Anyone have recommendations for a good aftermarket battery (not extended) for the DINC2?
UPDATE 2: The "fix" didn't last. The same problem resumed after an hour or so on the other battery. Still open to suggestions.
When I installed CM10 and was experiencing a bootloop the same thing was happened to me. Could not turn on phone unless I pulled battery first. I have since corrected the bootloop issue and have not experienced it since (same ROM).
vforaci said:
When I installed CM10 and was experiencing a bootloop the same thing was happened to me. Could not turn on phone unless I pulled battery first. I have since corrected the bootloop issue and have not experienced it since (same ROM).
Click to expand...
Click to collapse
I don't have any bootlooping - the phone was working great with CM7.2 until this started happening. Can't figure out what caused it. How well is CM10 running on your DINC2 (like, performance-wise)? (Assuming that's the phone you have.)
Performance is better than Viper and yes I have the Dinc2.
What is the turbo engine? I've never used or heard of it. I did have reboot issues with the early builds of cm10. I just flashed psycho's new 4.2.2 build & it seems to be quicker than evervlov. I need to give a couple days though.
D851 here, When ever i switched from cloudy 2.5 to blisspop 4.0 and after wiping everything i flashed a various of radios bootstacks and etc to make it boot after many failed attempts to boot ( it boots up but after 4 or so seconds after the lg logo the screen turns black and doesnt turn back on until after i pull out the battery) it worked after i flashed the rom WITHOUT a custom kernel so naturally i booted up just fine and thought maybe now i set up everything on my phone and tweaks i should go back and flash a custom kernel i used to use (777 r16) but then it gave me the problem i faced before the black screen after the lg logo no kernal would work. THEN another problem arised similar to the freezing on the black screen randomly during a usage thru my day the phones screen would be unresponsive animations but touch wouldnt work and i know its not my screen cause when i flash back to cloudy it works fine the freezing happens at least every 5 mins. someone halp?
i know this thread is kinds old...
but i have this same issue too... I found if I switch batteries the problem isn't as bad... but, then it becomes bad again. Its weird. Before I swapped batteries I couldn't even login with my google account, after a fresh flash. then after I swapped batteries (gf has same phone) I was able to get through to the end and setup the phone. But, then an hour later it started happening again....
OP, did you find a solution?
warrior420 said:
i know this thread is kinds old...
but i have this same issue too... I found if I switch batteries the problem isn't as bad... but, then it becomes bad again. Its weird. Before I swapped batteries I couldn't even login with my google account, after a fresh flash. then after I swapped batteries (gf has same phone) I was able to get through to the end and setup the phone. But, then an hour later it started happening again....
OP, did you find a solution?
Click to expand...
Click to collapse
i actaully did i think one of the problems was maybe flashing over the same kernel? see what happened was after i gave up flashing the kernel i just flashed without it and to my surprise the build actually came with the kernel pre-installed...shocker and so i had no need to flash over the kernel that i wants because the maker of g3 tmo blisspop already had it in his build and it boots up fine( DISCLAIMER: i cant say this about other roms because the only one i actually tested and wanted was blisspop)
thelgog said:
i actaully did i think one of the problems was maybe flashing over the same kernel? see what happened was after i gave up flashing the kernel i just flashed without it and to my surprise the build actually came with the kernel pre-installed...shocker and so i had no need to flash over the kernel that i wants because the maker of g3 tmo blisspop already had it in his build and it boots up fine( DISCLAIMER: i cant say this about other roms because the only one i actually tested and wanted was blisspop)
Click to expand...
Click to collapse
Okay.
Well, when I was flashing I never flashed a kernel.
Ill be getting a brand new Anker Battery in the mail today. Ill report my findings.
I ended up going to a stock based rom and the issue never happened. So I stuck with it. Ill have to do some testing later and ill let you know how the battery works.
It's not the battery
I downgraded my T-Mo G3 since I couldn't root it with LP on it. Went back to 4.4.2., rooted it, TWRP'd it, and installed the latest CM12 Nightly, Gapps, SU, etc.
As long as the sim card was OUT the installation was great on wifi only, As soon as I put it in it shut off right after, or during boot up. Take the sim out and it works. And yes, the only way to get back into recovery was pulling the battery and doing the key press to recovery. Mystified.
If I find out anything, I'll post it here.
I'd say do a complete return to stock, upgrade via LG Mobile Support tool all the way to 20G, see how it works stock for a while. Then root ( http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197 using the first method) and see what happens.