Hi. I just updated the nightly build. After that, phone start to reboot randomly but i didnt think it is a big problem. But now, my battery is %5 and its not charging. I connect the cable, there is the lightning on the battery icon but when i go battery settings it says "%5 not charging". What should i do? How can flash stock rom with that battery level? Please help.
Sent from my iPad using Tapatalk
Same problem here. Revert back to the old CM13, it'll work. As for the 5%, just keep charging it while you downgrade it to the old CM, it won't charge the battery, but it will also stay at 5%.
filbertmang said:
Same problem here. Revert back to the old CM13, it'll work. As for the 5%, just keep charging it while you downgrade it to the old CM, it won't charge the battery, but it will also stay at 5%.
Click to expand...
Click to collapse
What version of CM13 u install to get it back to work? I try to install RR ROM but still don't charge. But when I turn off my phone (I don't know why) then my phone is charging. Any idea?
I had the same problem, it didn't charge more than %18, but i guess it was because of dirty flash, after wiping everything and flasging the new one, problem was solved
I had this problems. You can turn off your phone and it will charge.
If you want to keep CM 13 install 777 kernel that the charging bug will be fixed. At least it worked for me and some other users.
☝ yes, a different kernel fixed the issue, as it is a kernel issue from the new cm kernel that was recently implemented.
777 kernel is great!
Thank you all, I couldn't answer earlier.
filbertmang said:
Same problem here. Revert back to the old CM13, it'll work. As for the 5%, just keep charging it while you downgrade it to the old CM, it won't charge the battery, but it will also stay at 5%.
Click to expand...
Click to collapse
Your method has worked, thanks. As you say it remained same while flashing.
Ryudo0 said:
I had this problems. You can turn off your phone and it will charge.
If you want to keep CM 13 install 777 kernel that the charging bug will be fixed. At least it worked for me and some other users.
Click to expand...
Click to collapse
It wasn't also charging when it's turned off. But thanks for answer.
Sent from my LG-D855 using Tapatalk
Yes i had the same problem and 777 kernel fixed the issue
The kernel wasn't stable at the beginning i had some lags but after clearing cache and dalvik everything is working great now.
BTW Did anyone fixed the issue of "Invalid number" after ending calls???
M_ashmawii said:
Yes i had the same problem and 777 kernel fixed the issue
The kernel wasn't stable at the beginning i had some lags but after clearing cache and dalvik everything is working great now.
BTW Did anyone fixed the issue of "Invalid number" after ending calls???
Click to expand...
Click to collapse
I think this bug come with update CM13 to Android 6.0.1 and they don't know how to fix it or they just don't want to fix it. This bug is on all softwere with number 6.0.1 (on 6.0 never had this) - i think so.
xVeenix said:
I think this bug come with update CM13 to Android 6.0.1 and they don't know how to fix it or they just don't want to fix it. This bug is on all softwere with number 6.0.1 (on 6.0 never had this) - i think so.
Click to expand...
Click to collapse
Do you know what's the last cm 13 update with android 6.0?
I had this problem few times, restart always helped.
Cancled..
Nightly Released 12/22/2015 Fixed Charging Issue
xVeenix said:
What version of CM13 u install to get it back to work? I try to install RR ROM but still don't charge. But when I turn off my phone (I don't know why) then my phone is charging. Any idea?
Click to expand...
Click to collapse
I walked my d855 (LG G3) back through the nightly releases until I found the latest one that did not have the charging issues for me. I ended up with the 12/22/2015 Nightly Build that doesn't seem to have any of the charging issues. I was not able to download the 12/23/2015 Nightly for some reason, I think I just got a 404 error when trying to download the file.
I saw some people talking about the 777 kernel being a solution to this issue and I downloaded the zip file for that kernel but I wanted to see if one of the nightly releases fixed the issue before I started messing around with the kernel. I may end up installing that one if one of the Nightlies doesn't fix this issue sometime in the near future.
For the record, my phone would charge for a short while and then would stop charging the battery. The percentage at which it stopped seemed to be random, it was not the same percentage every time. Every once in a while I could get it to charge up to 100% again but not usually. Most of the time it would stop charging within a couple of minutes of plugging it in or setting it on the wireless charger. It did seem to take a charge if it was turned off. I could only test that with the wired charger since the wireless charger boots the phone up before starting to charge the phone again. Whenever it stopped charging, my 3c toolbox battery manager would say that it was plugged in (or on the wireless) but that it was either at 0mA coming in or sometimes it would actually drop into the negative (discharging).
Around the same time that I started having the charging issues I also ran into a problem where the phone would shut itself off whenever I had Google Play Music running through my Bluetooth headphones for a few minutes. It didn't just shut down all of the sudden with no warning, it would throw up the message box that it was shutting down, just like if I had told it to shut down myself.
I will keep an eye on the 12/22/2015 Nightly release and see if all of the issues I was having with the more recent Nightlies have stayed away. I will post again if I do run into these problems again.
*** EDIT ***
I went ahead and installed the 777 kernel and then updated to the most recent nightly release. I still ran into the same battery issue the first time I tried to plug the phone in. So, in my case at least, the 777 kernel did not do anything to help out the charging problems related to the nightly updates past the 12/22/2015 nightly release.
I am currently restoring my image to the 12/22/2015 nightly release with the updated 777 kernel so that I can charge my phone again. I will continue to check out the 777 kernel but I am going to have to hold off on the nightly releases/updates until they fix this problem. I can't leave my phone off every time it needs to charge. I did order two more batteries with an A/C charger so that I can swap out batteries for full ones if I need to. I originally ordered those when I first came upon the charging problem, mistakenly thinking my battery was going bad.
At any rate, hopefully someone will figure out something for this charging issue soon. I hope I maybe saved someone a little time with this post anyway....
I have the same issue with LG G3 Rogers/Bell (852). Reverted to Dec 22 nightly and battery is now charging OK. Anything past Dec 22 seems to have this battery charging issue for me.
Can confirm that flashing an alternate kernel does in fact fix the charging bug!
AssasinPenguins said:
Can confirm that flashing an alternate kernel does in fact fix the charging bug!
Click to expand...
Click to collapse
tried flashing 777kernel and phone was stuck on boot screen, have any idea why??
svismobo_66 said:
tried flashing 777kernel and phone was stuck on boot screen, have any idea why??
Click to expand...
Click to collapse
Hello
I'm using the latest update CM13 (30-12-2015) and the problem of charge apparently has solved. I have managed to charge my cell phone to 100%. In the only previous version it loaded up to 50%.
someone more that has tested?
Updated to latest nightly Dec 30 2015 and confirm that charging is working again for me. Thanks.
I also updated to December 30 and it is now fixed.
Sent from my LG-D852 using Tapatalk
I still have this issue, tried the 777 kernel and got stuck on boot.
Been trying to systematically update ever since...
Related
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.
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.
hello,
since the 10th jan 2014 i have some strange problems with the CM11 nightlies. Actually im testing at the moment if cm10.2 solves the issue.
The issue is:
huge battery drain. I think its related to the google framework, since there was some update recently.
What i already did, and which did not work, is that i updated the recovery to 6.0.4.5 and my modem to latest version.
This worked fine, but the issue did persist.
So: has anyone of you a idea what i can do?
s0ftcorn said:
hello,
since the 10th jan 2014 i have some strange problems with the CM11 nightlies. Actually im testing at the moment if cm10.2 solves the issue.
The issue is:
huge battery drain. I think its related to the google framework, since there was some update recently.
What i already did, and which did not work, is that i updated the recovery to 6.0.4.5 and my modem to latest version.
This worked fine, but the issue did persist.
So: has anyone of you a idea what i can do?
Click to expand...
Click to collapse
About which model exactly you are talking about?
SandeepEmekar said:
About which model exactly you are talking about?
Click to expand...
Click to collapse
The european LTE model, namely GT-I9595. And yes i installed the correct modem as well as recovery.
And by the way: when my battery drains so fast (and the device also heats up, i think because my CPU is permanently at max clock and with 100% load. Also the device starts to lag and has problems waking up from being locked), the Wi-Fi has also some strange behaviour. For example i cant deactivate it without crashing the settings app.
Oh and: Yes i am on a clean install not using any backups.
UPDATE:
The problem is gone with cm 10.2 stable.
But i want cm11... so nobody with a idea?
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.
Hi guys,
I updated my op3 to latest beta 28 but I got random reboots when I'm not using it;
in fact, usually it reboots when charging or when it's in standby, and other moments like that.. I really don't know why!
I checked the MD5 of the zip, I flashed with the latest bluspark 8.54 and I did a full wipe;
I also reflashed with a dirty flash the ROM(and other ROMs based on Oxy).
Nothing changed.. it appears 2-3 times per day.
Anyone of you got the same error? which could be a solution?
I had exactly the same problem, but flash rom via adb fixed that.
not experiencing any.. stock non rooted...
Kshysiek said:
I had exactly the same problem, but flash rom via adb fixed that.
Click to expand...
Click to collapse
Sounds interesting.. will try! Thx in advance
Morning! You're not the onlyone having troubles with OB28, I'm facing similar issues aswell. Decided to wipe all and perform another clean install (not via adb as suggested above) yesterday afternoon and no issues so far. Will keep you updated
Running ExperienceOS by Jamal btw, which is based on stock OB28
I have had this as well. Just keeps rebooting randomly.
Dirty flashing the rom ob28 helps and keeps it stable. But then it reappears after some time randomly. It could be after a few hours or a day or two as well. Yesterday it just started rebooting while it was lying on the desk.
I suspect it could be because of a custom kernel. I have moved from custom to stock (rooted) for now. Lets see
Having same with ob28 also with 5.0. Sometimes it starts rebooting when charging, sometimes while just laying on the desk. 2 times I had it rebooted to recovery. I have even missed an alarm. I found a phone rebooted to recovery in the morning.
Yesterday clean installed 5.0. Rebooted 10 minutes ago. Dirty flashed ob28, retooting also.
Sent from my ONEPLUS A3003 using Tapatalk
In another thread, someone suggested rooting with SuperSU instead of Magisk. Tried that and now stable of over 2 days. You might give it a try
It has something to do with magisk or bluspark twrp in combination with something. Tried installing Supersu. Rebooting stopped, but dm-verity message appeared when booting. Decided to format everything. Flashed original recovery, but it could not decrypt file system. Tapped on forgot my password and it wiped everything. Sideloaded OOS 5.0, rebooted, then flashed twrp via fastboot. Flashed magisk 14.5. Stable for 2 days.
Sent from my ONEPLUS A3003 using Tapatalk
I have 2 oneplus 3 (one for me and my wife). I installed on both the latest beta Hydrogen OS (basically the same version as OB28).
On both devices, magisk 14.5 is installed.
And yes, I received random reboots maybe 1-2 days one time. And once rebooted, sometimes it will reboot again few seconds after that for few times.
Usually to stop that, after the reboot done, I will reboot the phone manually as fast as possible. And it will be okay for another 1-2 days.
So far I can live with this. But I might downgrade my wife's phone to something else stable
creezalird said:
I have 2 oneplus 3 (one for me and my wife). I installed on both the latest beta Hydrogen OS (basically the same version as OB28).
On both devices, magisk 14.5 is installed.
And yes, I received random reboots maybe 1-2 days one time. And once rebooted, sometimes it will reboot again few seconds after that for few times.
Usually to stop that, after the reboot done, I will reboot the phone manually as fast as possible. And it will be okay for another 1-2 days.
So far I can live with this. But I might downgrade my wife's phone to something else stable
Click to expand...
Click to collapse
Same behaviour here on OxygenOS 5.0 with Magisk 14.5 and Boeffla kernel. I usually wipe cache and dalvik in TWRP 3.2 and then it's fine for a couple of hours (or days, if I'm lucky).
Quick update from my side. It's been 6 days since I replaced Magisk and rooted with SuperSU and it definitely solved my issues. No reboots or whatsoever.
basvanasperdt said:
Quick update from my side. It's been 6 days since I replaced Magisk and rooted with SuperSU and it definitely solved my issues. No reboots or whatsoever.
Click to expand...
Click to collapse
Same here
Been in SuperSU for 3 days. No issues so far
Op3 ob28
I had random reboots on Freedom OS 3.1 after about two weeks of use with stock kernel and Magisk 14 (no issues before that). Flashed Blu Spark 207, didn't help. Flashed FOS 3.2: neither. Somebody suggested aggressive dose to be the culprit. It wasn't as I didn't had it enabled for starters. I Flashed official OB28 + magisk and stock kernel... And after one day, reboot. Flashed Blu Spark 208, reboot. But after a couple more reboots last week, they seem to have gone by themselves:
$ uptime
02:00:49 up 4 days, 6:48, load average: 2.98, 2.01, 2.24
*I had not tried using super su instead.
What can we do to debug this issue? Seems like everybody is trying to guess in the dark...
---------- Post added at 09:31 AM ---------- Previous post was at 09:10 AM ----------
If I may suggest, there seems to be a sort of "environmental" origin for this... I've noticed some "correlated incidence of reboots" between unrelated devices, regardless of specific OB variant (OB, FOS, EOS), kernel (stock, Blu), and root method, based on number of complaints and reports of generically unsuccessful attempts to solve the issue in the respective ROM threads, and here too.
Besides, I've not been able to identify any usage related trigger: this has happened to me while phone is idle, while browsing this thread, while driving thru unknown and dangerous streets guided by Waze, while commuting on the subway and only listening music...
Some more rigurous analysis of the prevalence of these reboots as a function of time might prove useful...
Also, there seems to be a growing incidence between users. There seems to be also a "incubation time" for most of us (but not for everybody). Are we sure we are not talking about some disease?
Just had another reboot. No Magisk log created...
But on every reboot I seem to lose some settings (in the settings app). Which setting is lost, seems completely random: battery optimization setting, LED notification setting, configured sounds,...
Aaand..... Two reboots lastima friday, and about 5 today...
This Is turning into a real deal breaker...
Experiencing back to back reboots form morning on stable Oreo op3. Imma switch back to 7.1 til the time its solved
I also have problems with reboots, but they have given way. Now I have a problem with the phone's sudden heating and battery drain this.
simpele said:
Just had another reboot. No Magisk log created...
But on every reboot I seem to lose some settings (in the settings app). Which setting is lost, seems completely random: battery optimization setting, LED notification setting, configured sounds,...
Click to expand...
Click to collapse
strange1712 said:
Aaand..... Two reboots lastima friday, and about 5 today...
This Is turning into a real deal breaker...
Click to expand...
Click to collapse
abhibnl said:
Experiencing back to back reboots form morning on stable Oreo op3. Imma switch back to 7.1 til the time its solved
Click to expand...
Click to collapse
Kshysiek said:
I also have problems with reboots, but they have given way. Now I have a problem with the phone's sudden heating and battery drain this.
Click to expand...
Click to collapse
Those experiencing reboots .. pls specify if it's with or without magisk. And if it's with, which version. And if it's without, what other modding have you done.
Will be helpful to establish the common thing in the setup causing the reboots
candiesdoodle said:
Those experiencing reboots .. pls specify if it's with or without magisk. And if it's with, which version. And if it's without, what other modding have you done.
Will be helpful to establish the common thing in the setup causing the reboots
Click to expand...
Click to collapse
With magisk 14.0 and later magisk 14.5. Now I'm testing without root at all, as it seems to be magisk related, it is also reported on the magisk thread.