Develop Bugs

[Q] Phone won't turn on without removing battery first

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.

Reboots on all 5.1 ROMs...

Like the title says, on every 5.1 ROM I keep getting random reboots. They happen indiscriminately, with no clear reason at all. Other people report no issues at all. On 5.0.2 I have no issues at all. I have no idea what causes it could be or no knowledge on how to diagnose it...I want to use 5.1, but if this keeps happening I don't think I can ?.

I've not had any issues with random reboots, been running euphoria rom (updating with each new build) and glitch kernel for weeks with no issues.
Assuming you're doing clean flashes, with no extra mods, and not restoring system data, yes? Its even possible that restoring app data from backups can cause weird things to occur at times. If you haven't yet, wipe everything and clean flash, restore apps only from play store, and see if it still happens.
Otherwise, maybe a specific app is causing problems? You could try and grab some logs to narrow down the cause, but I know that's very tough to do if the issue is intermittent and seemingly random. Still it is the only way to tell for sure what's happening.
Here's a guide on how to grab the different logs if that helps at all: http://forum.xda-developers.com/showthread.php?t=1520508 .

LucentBirch said:
Like the title says, on every 5.1 ROM I keep getting random reboots. They happen indiscriminately, with no clear reason at all. Other people report no issues at all. On 5.0.2 I have no issues at all. I have no idea what causes it could be or no knowledge on how to diagnose it...I want to use 5.1, but if this keeps happening I don't think I can ?.
Click to expand...
Click to collapse
The random reboots are caused by outdated 5.0.2 binaries, if you update to 5.1 it should mend it random reboots. Also if your ROM developer might or will update the ROM to 5.1 with the updated binaries!

Killah1994 said:
The random reboots are caused by outdated 5.0.2 binaries, if you update to 5.1 it should mend it random reboots. Also if your ROM developer might or will update the ROM to 5.1 with the updated binaries!
Click to expand...
Click to collapse
Well I know for a while that some 5.1 roms were using the 5. 0. 2 binaries because the 5.1 weren't released yet... And they never really said whether or not they updated the binaries or if they were even released...I updated my tablet to a 5.1 R_5 this morning and it hasn't rebooted all day...so maybe they have?

LucentBirch said:
Well I know for a while that some 5.1 roms were using the 5. 0. 2 binaries because the 5.1 weren't released yet... And they never really said whether or not they updated the binaries or if they were even released...I updated my tablet to a 5.1 R_5 this morning and it hasn't rebooted all day...so maybe they have?
Click to expand...
Click to collapse
5.1 binaries and factory image for this device were just rolled out today. This may indeed resolve your issues, but give the custom rom devs some time to catch up, they'll need to grab the latest source and post new builds for the latest binaries to be included.

Same thing here
I excitedly loaded up the 5.1 build on my 2013 wireless today. SAME ISSUE. I can't do anything .
I didn't wipe the device when I upgraded. I was rooted - unrooted / flashed / rooted using the Nexus Root Tooklit as I have since Jelly Bean. I used the option to use NO WIPE MODE to try and keep my apps intact.
Any help appreciated.

mrdrumsc said:
I excitedly loaded up the 5.1 build on my 2013 wireless today. SAME ISSUE. I can't do anything .
I didn't wipe the device when I upgraded. I was rooted - unrooted / flashed / rooted using the Nexus Root Tooklit as I have since Jelly Bean. I used the option to use NO WIPE MODE to try and keep my apps intact.
Any help appreciated.
Click to expand...
Click to collapse
in that case you should try wiping then flash the 5.1 factory image and see if it works.

PrizmaticSmoke said:
5.1 binaries and factory image for this device were just rolled out today. This may indeed resolve your issues, but give the custom rom devs some time to catch up, they'll need to grab the latest source and post new builds for the latest binaries to be included.
Click to expand...
Click to collapse
cm12.1. rebooted once today while using chrome.

Reboots better!
I concur with the messages I've been seeing. After several app updates over the weekend, culminating in some Chrome updates, the tablet seems stable. I haven't re-rooted it yet.
I wonder if something has to do with the "notification crash" error listed in the changelog for 5.1.1.
Either way, looking forward to 5.1.1!

Cyanogenmod 13 not charging!

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

LG G Pro E988 Cyanogenmod Reboot Problem

Hi. Im using LG G Pro E988 variant. I'm trying to flash cyanogenmod 12.1 nightly version. Everything went well and all but i got a problem where the phone likes to reboot itself. So i try to clean everything with the usual stuff (wipe data, even wipe system, cache, etc) and re-flash the same. The issue still persists so i thought maybe it's the problem lies within the cm12.1 itself so i move a step back. I flashed the latest Cyanogenmod 11.2 Snapshot version that was available from their site. The issue still happened and i got no clue what's going on. On my stock kitkat ROM, this issue never happened.
Anybody got the same problem? Thank you before

Oyongx said:
Hi. Im using LG G Pro E988 variant. I'm trying to flash cyanogenmod 12.1 nightly version. Everything went well and all but i got a problem where the phone likes to reboot itself. So i try to clean everything with the usual stuff (wipe data, even wipe system, cache, etc) and re-flash the same. The issue still persists so i thought maybe it's the problem lies within the cm12.1 itself so i move a step back. I flashed the latest Cyanogenmod 11.2 Snapshot version that was available from their site. The issue still happened and i got no clue what's going on. On my stock kitkat ROM, this issue never happened.
Anybody got the same problem? Thank you before
Click to expand...
Click to collapse
I'd try using the latest wild kernel.

g0at1 said:
I'd try using the latest wild kernel.
Click to expand...
Click to collapse
well i think i did try wild kernel with cm12.1 latest nightlies. The issue gotten worse. More random reboot occured.
Currently on slimLP with his zerkernel v1.7. I thought this one is perfect, but then out of nowhere the random reboot occured again. It's not as frequent as before but still happen.

Right now I'm using Mokee with wild kernel and everything is going well.

Oyongx said:
Hi. Im using LG G Pro E988 variant. I'm trying to flash cyanogenmod 12.1 nightly version. Everything went well and all but i got a problem where the phone likes to reboot itself. So i try to clean everything with the usual stuff (wipe data, even wipe system, cache, etc) and re-flash the same. The issue still persists so i thought maybe it's the problem lies within the cm12.1 itself so i move a step back. I flashed the latest Cyanogenmod 11.2 Snapshot version that was available from their site. The issue still happened and i got no clue what's going on. On my stock kitkat ROM, this issue never happened.
Anybody got the same problem? Thank you before
Click to expand...
Click to collapse
Random rebooting is a common issue with all the cm 12.1 based ROM for lg ogp. The cm12. 1 in my opinion was never fully stabilized even by the time the devs were starting to switched to the newer hardwares. If you keep the number of apps you unstated to minimum, you may be able to keep random rebooting down, but this just my observation. I thought the latest bliss pop 4.03 had the rebooting issues sloved, but it rather just had the occurrence down to where it's less. But there are other issues such as the device getting extremely hot, which in turn causes shutdown. To the point where I give up on using LP once again on this device, and move back to kk. The kk may be an older rom, but at least it's stable. With the LP, I think issues with it unable to find the sim card, GPU issues that cause screen to flicker and blackout, all are never fully fixed. Rather, those issues were patched and rigged to make the rom run, but not smooth enough where you see issues such as rebooting and overheating.
Sent from my LG-E980 using XDA-Developers mobile app

hawkwind212 said:
Random rebooting is a common issue with all the cm 12.1 based ROM for lg ogp. The cm12. 1 in my opinion was never fully stabilized even by the time the devs were starting to switched to the newer hardwares. If you keep the number of apps you unstated to minimum, you may be able to keep random rebooting down, but this just my observation. I thought the latest bliss pop 4.03 had the rebooting issues sloved, but it rather just had the occurrence down to where it's less. But there are other issues such as the device getting extremely hot, which in turn causes shutdown. To the point where I give up on using LP once again on this device, and move back to kk. The kk may be an older rom, but at least it's stable. With the LP, I think issues with it unable to find the sim card, GPU issues that cause screen to flicker and blackout, all are never fully fixed. Rather, those issues were patched and rigged to make the rom run, but not smooth enough where you see issues such as rebooting and overheating.
Sent from my LG-E980 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah, i think the issue are only on cyanogen based ROM. When i use the lolipop such as Super Mini V6.5 by henrypham91 and lgviet team, it's all good. Deep sleep normaly, no sound delay when game on 2D graphics, and all. But then again, it's noticeably slower if you compare against CM head to head. I really love CM or AOSP based rom because they are so fast.
g0at1 said:
Right now I'm using Mokee with wild kernel and everything is going well.
Click to expand...
Click to collapse
Never heard about Mokee. I'll look maybe and try that. Thanks Edit: it is an AOSP based rom! Might try that. Hopefully my phone survive lol

Oyongx said:
Never heard about Mokee. I'll look maybe and try that. Thanks Edit: it is an AOSP based rom! Might try that. Hopefully my phone survive lol
Click to expand...
Click to collapse
Mokee is a Chinese CM based rom.

g0at1 said:
Mokee is a Chinese CM based rom.
Click to expand...
Click to collapse
The download link seems invalid. I don't understand chinese but on the downlaod the url there's an error 404 written. :silly:

Oyongx said:
The download link seems invalid. I don't understand chinese but on the downlaod the url there's an error 404 written. :silly:
Click to expand...
Click to collapse
Their website has an English version. There should be a British flag on the upper right side. Then download their history zip which is a kind of final release.

Flashing CM 12.1 hangs on patching system image

I am trying to flash CM 12.1 on a GT6810P. I followed instructions from the 1st post of the thread and everything works fine up to the point of flashing the zipfile of CM12.1. It progresses to "Patching system image unconditionally" and then nothing happens anymore. I tried both CMWR 6.0.5.1 as the latest TWRP. In CMWR the wire frame keeps rotating, but the process never finishes. I let it run for 1 hour and 45 minutes, but still no end.
Does anybody have any clue what is wrong or what I am doing wrong?

I discovered that above problem is only with the most recent release of the 8th of June '16. I was able to flash the second last release of the 18th of januari '16 without a problem. Pretty strange. Did anybody had the same problem as me?

I had the same problem with cm-12.1-20160608-UNOFFICIAL-nevisp and after reading through the forums, I discovered that others did too.
I'm also using cm-12.1-20160118-UNOFFICIAL-nevisp, but I can't seem to use WhatsApp without the phone crashing every few hours.
CM11 had trouble playing videos in WhatsApp, so I moved to CM12. I still have not found a stable build that can do just Youtube, Whatsapp, and basic calls without crashing or poor performance. Have you tried the CM13 release by faizauthar12?
eximiusnl said:
I discovered that above problem is only with the most recent release of the 8th of June '16. I was able to flash the second last release of the 18th of januari '16 without a problem. Pretty strange. Did anybody had the same problem as me?
Click to expand...
Click to collapse

orangematter said:
Have you tried the CM13 release by faizauthar12?
Click to expand...
Click to collapse
Yes, I tried that one after I could not get cm-12.1-20160608-UNOFFICIAL-nevisp to work. But CM 13 is so slow that it is not usable and hangs on the Google login, so Play store does not work.
cm-12.1-20160118-UNOFFICIAL-nevisp seems to complain about the SIM and seems to expect a dual SIM phone. The last posts in the CM12.1 thread are related to this issue.