Related
I found those sudden reboots happening on my device, XT1033 with ART unrooted running the single sim firmware. Everything was fine for a long time, but the last weeks its been happening. It simply freezes, no matter doing what going into a point that when I press the power/lock, the screen won't even turn itself back on, forcing myself to force-reboot in order to work again. I also notice that when it happens, the device has a downfall in the battery graph even tho not much was consumed and even losing a couple minutes on the screentime. I will embed a photo.
Maybe switching back to Dalvik fixes it? Or something else is the issue? I got no "weird" apps installed. Suggestions?
Nobody?
Before to think if it's a battery problem you have tried to switch to dalvik and see what happens on long time?
denzel09 said:
Before to think if it's a battery problem you have tried to switch to dalvik and see what happens on long time?
Click to expand...
Click to collapse
Not exactly, mainly because it never happened before. I am using ART since it updated to KK, started recently only.
rogeriorp said:
Not exactly, mainly because it never happened before. I am using ART since it updated to KK, started recently only.
Click to expand...
Click to collapse
Can you grab logcat log? Maybe it can say something when it happens.
The best way to do this is by Eclipse -> CatLog viewer. You won`t loose log messages when device will be rebooted.
Did you try wiping cache / dalvik ? System will rebuild everything so you won`t loose your data and it can fix your problem.
Cheers,
fabus said:
Can you grab logcat log? Maybe it can say something when it happens.
The best way to do this is by Eclipse -> CatLog viewer. You won`t loose log messages when device will be rebooted.
Did you try wiping cache / dalvik ? System will rebuild everything so you won`t loose your data and it can fix your problem.
Cheers,
Click to expand...
Click to collapse
I did only wipe cache partition before, never the dalvik. I might give it a try the next time it happens.
Also, to catch a logcat requires root? If so I can't grab one.
rogeriorp said:
I did only wipe cache partition before, never the dalvik. I might give it a try the next time it happens.
Also, to catch a logcat requires root? If so I can't grab one.
Click to expand...
Click to collapse
Try catlog, i don't remember if need root honestly
Alright, got the guidances. Thank you both for the help, will leave some feedback later on.
An update: it happened twice in a row just now. Switched back to Dalvik just in case. Will keep this one post updated to not spam.
rogeriorp said:
I found those sudden reboots happening on my device, XT1033 with ART unrooted running the single sim firmware. Everything was fine for a long time, but the last weeks its been happening. It simply freezes, no matter doing what going into a point that when I press the power/lock, the screen won't even turn itself back on, forcing myself to force-reboot in order to work again. I also notice that when it happens, the device has a downfall in the battery graph even tho not much was consumed and even losing a couple minutes on the screentime. I will embed a photo.
Maybe switching back to Dalvik fixes it? Or something else is the issue? I got no "weird" apps installed. Suggestions?
Click to expand...
Click to collapse
I just unlocked, rooted, flashed recovery and custom ROM on a refurb unit. I had kinda the same issue with this phone out the box stock. Mine will work perfect as long as its plugged in to either PC or wall charger. Once unplugged, pushing power to wake causes screen to shutoff after a few seconds or freeze, then reboot. Doesn't seem to be software related, as a clean install of pacman did nothing different. Touchscreen gets very unresponsive, also causing reboots.
sent from my Gs3
rogeriorp said:
An update: it happened twice in a row just now. Switched back to Dalvik just in case. Will keep this one post updated to not spam.
Click to expand...
Click to collapse
- LogCat requires root to see system messages, otherwise you will see only high layer user messages.
- I tryied ART and didn`t have such issue, just came back to Dalvik because I noticed that ART uses more cache (which impacts overall virtual SD capacity) and didn`t see any improvement in performance.
@joeyhdownsouth - could you give us logcat / dmesg log on some share? It seems you have some issues while charging. It can be causes either by wrong charger (too high/low current, but moto should control it) or maybe some app causes this when you unplugs usb cable.
Anyway - without log we cannot say anything.
Cheers,
I have this phone for 4 months already, its weird it happens out of no where tbh. Switched back to Dalvik yesterday and no issue yet, switching runtimes compile them all over again right?
rogeriorp said:
I have this phone for 4 months already, its weird it happens out of no where tbh. Switched back to Dalvik yesterday and no issue yet, switching runtimes compile them all over again right?
Click to expand...
Click to collapse
yes, you should see "Updating Android" with application number every time you switch DALVIK<->ART.
Cheers,
fabus said:
- LogCat requires root to see system messages, otherwise you will see only high layer user messages.
- I tryied ART and didn`t have such issue, just came back to Dalvik because I noticed that ART uses more cache (which impacts overall virtual SD capacity) and didn`t see any improvement in performance.
@joeyhdownsouth - could you give us logcat / dmesg log on some share? It seems you have some issues while charging. It can be causes either by wrong charger (too high/low current, but moto should control it) or maybe some app causes this when you unplugs usb cable.
Anyway - without log we cannot say anything.
Cheers,
Click to expand...
Click to collapse
Waiting on Motorola charger to come in, then if no change, I'll pull a logcat.
sent from my Gs3
I also experienced the last 3 days complete freezes. No idea what was going on...
Unfortunately I couldn't pull any log messages from the phone by that time. Half an hour later it just responded normally... Didn't see if it rebooted in between or what exactly happened
Just a heads up: going back to Dalvik got me rid off those freezes. Something on ART was messed up.
rogeriorp said:
Just a heads up: going back to Dalvik got me rid off those freezes. Something on ART was messed up.
Click to expand...
Click to collapse
I never even checked to see which one it was using when I first got it.
sent from my Gs3
joeyhdownsouth said:
I never even checked to see which one it was using when I first got it.
sent from my Gs3
Click to expand...
Click to collapse
By deault it is Dalvik. If you have new phone so it will be Dalvik.
Did you said two posts before that you were using some 3rd party charger (not Motorola cable)?
Funny, but yesterday I had similar issues with freezes and random reboots. I was using some cable taken from Friend (not Motorola) and weird things started to happening:
- It was indicated on a screen that phone is charging (probably discovered usb cable plugged it), but it was discharging faster and started rebooting (because it reached below 1% battery state) and after some reboots battery was so discharged that phone couldn`t come up.
This usb cable was attached all the time to my phone and a computer.
- Next I connected phone to my reglar charger for night (from Zte Tablet, but really good and charges fast, never had issues with it) and it was fully charged.
On the morning I played music for 15 minutes by loudspeaker and then put phone into my pocket for 10 minutes (walk to take a bus).
When I took my phone back into my hand battery was dropped to 1%! (from over 95% to 1% in 10 minutes), but phone didn`t shut down.
This 1% remain for couple of hours (something like 2-3) without shutting phone down.
I took another charger and connected to it again - phone was charged to 100% in less than 30 min (usually takes up to 3hrs) and now works like before (no huge and weird battery drain).
Btw. I`m on faux kernel 007m.
Weird... looks like moto g doesn't like be connected to a PC by other cable than Motorola
Hi All, a few hours ago something really weird happened, I stopped using my phone with 60%+ of battery, one hour later when I tried to use it again it was off and would not turn on. I thought that something ate my battery so I placed it in my car's charger with no signs of life, so I thought that maybe the battery was fully discharged and it needed a few minutes before I could turn it on, but nothing. Once I got home, I plugged it in the original charger with the original cable and left it a few minutes and then unplugged it (trying to move the charger to another plug) and it suddenly booted up by itself with me not even pushing the on button, and once it booted the phone had 60%+ battery so it was never the battery.
Has anyone experienced something like that? what could cause my phone to shutdown and not respond until plugging and unplugging it? I'm attaching my last_kmsg
I'm running rooted stock 38R with Franco Kernel r27
i also experienced the same thing, randon deaths with more than 40%, have to put the phone to charger, it would say low battery but battery,would say 40% after it started up. please help!!!
boomsheklau said:
i also experienced the same thing, randon deaths with more than 40%, have to put the phone to charger, it would say low battery but battery,would say 40% after it started up. please help!!!
Click to expand...
Click to collapse
Me too! Rooted on fk r28. Still have not find out a solution.
potpit said:
Me too! Rooted on fk r28. Still have not find out a solution.
Click to expand...
Click to collapse
Google the following and you will find the instruction: How to fix One Plus One sudden death bug resulting in boot loops
but I don't know how to! Can anyone walk us through it? what is TWRP and how do I run a command??
boomsheklau said:
Google the following and you will find the instruction: How to fix One Plus One sudden death bug resulting in boot loops
but I don't know how to! Can anyone walk us through it? what is TWRP and how do I run a command??
Click to expand...
Click to collapse
My OPO did not go into boot loops. It died not reaching 0% of battery life, which is weird & able to boot up when I plug in the charger.
But, for those facing the same problem I faced, download 'Battery Calibration' app from play store (free). Your OPO need to be rooted. Today, my OPO worked normally. My batt is at 17% whilst writing this & it's still alive. Will continue to monitor these few days.
What is TWRP & how to run a command, see here: http://forum.xda-developers.com/showthread.php?t=2788632
boomsheklau said:
Google the following and you will find the instruction: How to fix One Plus One sudden death bug resulting in boot loops
but I don't know how to! Can anyone walk us through it? what is TWRP and how do I run a command??
Click to expand...
Click to collapse
I Had the boot loop today(out of the blue, didn't know why it rebooted in the first place), i thought was just a random boot loop because i had so many xposed modules installed but later i got to know it was because of the "persist" partition getting corrupted during the reboot. if you have this problem just do the following and you will be ok.
adb shell
make_ext4fs /dev/block/mmcblk0p15
Click to expand...
Click to collapse
source:http://www.androidpolice.com/2014/10/13/heres-easy-fix-oneplus-one-sudden-death-bug-results-neverending-boot-loops/
I've had exactly the same problem, twice now. The phone dies after being WiFi hotspot for some time; it isn't hot, it won't turn back on, it won't show charging.... both times I have managed to get it going again with persistence pressing the power button vol up or down with the power plugged in.
Given the age of the phone, perhaps the problem really is the battery; pity it isn't user replaceable (easily). Such a pity as it is a good phone, still, it seems to be abandoned now as I only have 6.0.1 with old security updates in Sept. 2016.
affinityvision said:
Such a pity as it is a good phone, still, it seems to be abandoned now as I only have 6.0.1 with old security updates in Sept. 2016.
Click to expand...
Click to collapse
Our OPO is far than being abandoned. Even if it will receive no more official CyanogenOS or OxygenOS updates, here at XDA you will find several Android 7.1.1 ROM alternatives.
I personally use TugaPowerN (based on Lineage OS 14.1).
Latest N25 build features Feb. 2017 Android security updates.
fastleo63 said:
Our OPO is far than being abandoned. Even if it will receive no more official CyanogenOS or OxygenOS updates, here at XDA you will find several Android 7.1.1 ROM alternatives.
I personally use TugaPowerN (based on Lineage OS 14.1).
Latest N25 build features Feb. 2017 Android security updates.
Click to expand...
Click to collapse
Well, that would be good, but it then matters how much work it will take to keep it up to date; and that would be a problem if the device itself continues to have occurrences of random shutdown. I'm doing a battery calibration, hope that helps, if it does, then I'll consider changing ROM from stock.
TugaPower ROMs are often and constantly updated. Not only Nougats, but even Marshmallow version.
IMHO even if discontinued, the above ROMs will be more secure than the latest original stock Cyanogen OS (13.1.2).
First stop using unofficial kernel. Return to stock.
First, sorry if this has already been discussed somewhere, but I couldn't find a topic with a case exactly like mine.
I have a 4G Slide. From the beginning, as I don't like Android 2.3 (or whatever it was, 2.X anyway) I upgraded to 4.0 by installing Cyanogenmod 9.10 (stable release for Doubleshot). So I don't really know how it was before CM 9, but here's the issue.
First, this phone takes forever to charge it, even leaving it overnight isn't enough sometimes. However, it can reach 100%, it's just really slow. And here's the strange part. If you look at the charge graph in Battery menu, you can see the straight line going up, and at a certain moment you can notice what looks like a very slight break in it - not a gap, I mean that it's going up at a certain angle, and you see it suddenly change a bit, like the charging speed slowed down or something. So I found out that when you see this line break, you can just reboot the phone. And it shows 100% charge, the light is green! Otherwise you'll have to wait for hours until it shows 100%.
Also, changes in charge displayed on the screen are almost unpredictable. Sometimes it shows you it's holding charge well for a relatively long time, and suddenly, there's a sharp fall in the graph, and the phone shuts off. It's especially annoying during the night, as I use it as an alarm cloclk to wake up, and once I almost was late for work because the stupid thing died in the night, luckily I woke up by myself.
So my question is whether this can be fixed as I'm fed up. What I tried: changed the battery, tried different chargers, tried to clean the micro USB on the phone (the charging port), installed an updated version of CM 9 from this site. Nothing seems to help. So I'll be grateful if someone can tell me what it is, maybe you've seen this happen. Does it mean my phone has a bad charging controller? I also heard that flashing a different kernel sometimes helps, but there aren't any available for my phone.
Thank you.
RomanKasp said:
First, sorry if this has already been discussed somewhere, but I couldn't find a topic with a case exactly like mine.
I have a 4G Slide. From the beginning, as I don't like Android 2.3 (or whatever it was, 2.X anyway) I upgraded to 4.0 by installing Cyanogenmod 9.10 (stable release for Doubleshot). So I don't really know how it was before CM 9, but here's the issue.
First, this phone takes forever to charge it, even leaving it overnight isn't enough sometimes. However, it can reach 100%, it's just really slow. And here's the strange part. If you look at the charge graph in Battery menu, you can see the straight line going up, and at a certain moment you can notice what looks like a very slight break in it - not a gap, I mean that it's going up at a certain angle, and you see it suddenly change a bit, like the charging speed slowed down or something. So I found out that when you see this line break, you can just reboot the phone. And it shows 100% charge, the light is green! Otherwise you'll have to wait for hours until it shows 100%.
Also, changes in charge displayed on the screen are almost unpredictable. Sometimes it shows you it's holding charge well for a relatively long time, and suddenly, there's a sharp fall in the graph, and the phone shuts off. It's especially annoying during the night, as I use it as an alarm cloclk to wake up, and once I almost was late for work because the stupid thing died in the night, luckily I woke up by myself.
So my question is whether this can be fixed as I'm fed up. What I tried: changed the battery, tried different chargers, tried to clean the micro USB on the phone (the charging port), installed an updated version of CM 9 from this site. Nothing seems to help. So I'll be grateful if someone can tell me what it is, maybe you've seen this happen. Does it mean my phone has a bad charging controller? I also heard that flashing a different kernel sometimes helps, but there aren't any available for my phone.
Thank you.
Click to expand...
Click to collapse
ICS may just have battery stats that don't work for your batteries. Try calibrating the battery:
http://www.androidpit.com/how-to-calibrate-the-battery-on-your-android-device
https://play.google.com/store/apps/details?id=com.nema.batterycalibration&hl=en
If I remember the instructions properly, install the app, charge to full (or half hour past full), open the app to press the button, run it dry, and charge it fully with it turned off (note the LED on mine turns green at the 90% mark, so leave it plugged in and off for about an hour past the time it turns green).
I found with the app, it takes forever to get that last 1% after using it, and it takes a while before dipping below it again, but it seems to be more accurate than CM thinking I had the stock battery installed (I have a couple Ankers now). Hope this helps.
Thank you but doesn't work
Nothing helps. It's surely not related to incorrectly calibrated battery. I did 8-1-1 charge which DID help when I bought a Chinese copy of Samsung Galaxy S3 Mini (my wife is using it now, and it's working fine, battery life is very good). But my stupid phone doesn't react. Just 5 minutes ago, when I was talking to my friend, it still showed about 30% left, then it suddenly died and I even couldn't turn it on, even while it was charging, the red light was blinking. Then it turned on and showed 2%! But the most interesting thing is that now there's something else going on, which I've NEVER seen! Because when I looked at it after approximately 10 minutes, it showed 98%!!! It never did that before. What the hell is happening?????? Then I rebooted it, and now it shows 39%! How's that? I've no idea how to make it work, maybe it's the CM9 which doesn't work corectly with the battery controller, but I think that it's much more likely that the battery controller itself is faulty. Sometimes this happens, and this is a physical fault. Unfortunately, it's too expensive to fix, so I'll just probably have to get a new phone...
RomanKasp said:
Nothing helps. It's surely not related to incorrectly calibrated battery. I did 8-1-1 charge which DID help when I bought a Chinese copy of Samsung Galaxy S3 Mini (my wife is using it now, and it's working fine, battery life is very good). But my stupid phone doesn't react. Just 5 minutes ago, when I was talking to my friend, it still showed about 30% left, then it suddenly died and I even couldn't turn it on, even while it was charging, the red light was blinking. Then it turned on and showed 2%! But the most interesting thing is that now there's something else going on, which I've NEVER seen! Because when I looked at it after approximately 10 minutes, it showed 98%!!! It never did that before. What the hell is happening?????? Then I rebooted it, and now it shows 39%! How's that? I've no idea how to make it work, maybe it's the CM9 which doesn't work corectly with the battery controller, but I think that it's much more likely that the battery controller itself is faulty. Sometimes this happens, and this is a physical fault. Unfortunately, it's too expensive to fix, so I'll just probably have to get a new phone...
Click to expand...
Click to collapse
Well, I am suspecting a hardware issue, but only one way to find out ... go back to stock.
Doesn't have to be true stock, if you no longer have a nandroid of the original OS. MikTouch would work just as well, as the kernels are interchangeable. If you need a download for it, I can help out with that.
joel.maxuel said:
Well, I am suspecting a hardware issue, but only one way to find out ... go back to stock.
Doesn't have to be true stock, if you no longer have a nandroid of the original OS. MikTouch would work just as well, as the kernels are interchangeable. If you need a download for it, I can help out with that.
Click to expand...
Click to collapse
By the way, I wanted to install an upgrade - a different version of CM found here (the thread says it's stable enough) to see if a newer system can solve the problem. I found this "[ROM][Official]MyTouch4G Slide CyanogenMod 10.1 [P-21] | 2013-06-16" - but unfortunately, it doesn't work on my phone. It's getting installed, and then it says something like "Updating Android" and then "Starting applications" and just freezes. If you reboot it, it just stops at the CM10 logo. I had this before with CM 9 and wiped Dalvik cache (I think), then the problem went away. Here, no such luck. Doesn't help at all. Will go back (as I did a backup) to what I had. But it's a pity.
RomanKasp said:
By the way, I wanted to install an upgrade - a different version of CM found here (the thread says it's stable enough) to see if a newer system can solve the problem. I found this "[ROM][Official]MyTouch4G Slide CyanogenMod 10.1 [P-21] | 2013-06-16" - but unfortunately, it doesn't work on my phone. It's getting installed, and then it says something like "Updating Android" and then "Starting applications" and just freezes. If you reboot it, it just stops at the CM10 logo. I had this before with CM 9 and wiped Dalvik cache (I think), then the problem went away. Here, no such luck. Doesn't help at all. Will go back (as I did a backup) to what I had. But it's a pity.
Click to expand...
Click to collapse
Did you dirty flash, that is not wipe data before installing CM10.1? If so, that would be the cause.
If not, that's new for me. I used TBalden's CM10.1 for a year, never had a problem like that.
joel.maxuel said:
Did you dirty flash, that is not wipe data before installing CM10.1? If so, that would be the cause.
If not, that's new for me. I used TBalden's CM10.1 for a year, never had a problem like that.
Click to expand...
Click to collapse
I tried everything, including wiping data/cache/Dalvik cache, then installing the file, I even tried to install the GApps too. Nothing seems to happen. It just gets stuck in the bootloop. When you first turn it on, it stops at "Starting apps", then if you reboot it, it stops working at CM logo (bootloop). I waited for 10 minutes or more, no result. Luckily, I did a full backup so I went back to CM 9. Seems like my phone is simply incompatible with this mod. No luck for me here .
Hi everyone, i know the title seems like it's just a trival matter, but trust me it's not.
The phone was bought new in August of last year (2015).
The story so far: I've been using sultanxda ROM for over 6 months without any issues, but i decided to test a different ROM, so i downloaded Darkobas rom and GAPPS, the ROM and Gapps installed fine but when i started the device and i was doing the initial configuration the phone rebooted by itself. It happened about 3/4 times and after that the phone had entered a bootloop. I tried to reflash the ROM and gapps, but the phone was restarting during the flash in TWRP. I decided to go stock Cyanogen OS, so i did a clean fastboot install of cyanogen OS. Everything went well the phone was working fine, but a few hours after installation the phone was randomly rebooting again, i decided i'll live with it and wait and see if it goes away by itself.
The phone was rebooting 2/3 times a day, during different acitivities so it was hard to pinpoint what might the issue be (even when locked in my pocket with all apps killed). After a few days of usage it just went straight to bootloop, after that i had issues to even install a rom (even via fastboot), because it would install everything fine and then it wouldn't start properly and would be in a bootloop (straight after installation).
I also tried the Bacon Root Toolkit installation as well as formatting everything and wiping everything. But even with the usage of Bacon Root Toolkit the random reboots happened.
So i installed an older TWRP recovery, i wiped everything re-formatted the phone to F2FS (was EXT 4 b4) and installed a F2FS compatible ROM (can't remember which one), after that installation everything seemed to work fine, but after a day or so the random reboots came back to haunt me again. So i reformatted the phone to EXT-4 again, installed stock cyanogenmod via fastboot (the 4.4.2 version), and updated it to 6.0.1 via OTA (during the course of a day or so, but even when the phone was on 4.4.2 i had a random reboot once), and the reboots returned ( i tried many different solutions, even the command line in TWRP "make_ext4fs /dev/block/mmcblk0p15"). I had NO IDEA what might be causing them but i thought that maybe the processor is ****ed and it's overheating, i returned to sultanxda rom (with the underclock to 1957 mHz).
After returning the phone booted correctly after a clean install via TWRP, but now it's rebooting again, and sometimes it happens 4/5 times in a ROW, sometimes it doesnt even reboot, but goes to black screen and I have to push the power button for 6 + seconds for it to reboot.
I've tried the stability test, or running antutu a few times in a row to verify if maybe it's the processor's/RAM's fault, but the phone didn't care, it rebooted randomly (sometimes 6/7 antutu runs in a row and nothing happened, sometimes rebooting in my pocket with all apps shut down). I've tried different launchers/messing with WiFi options/turning off the proximity check/turning off the trust agents nothing seems to make a difference. At this point I'm at a loss of what to do so i came here to ask for any advice. Is there any way to check if the phones internal memory is corrupted in some way ? I've tried searching for some apps but nothing turned out.
oski131 said:
Hi everyone, i know the title seems like it's just a trival matter, but trust me it's not.
The phone was bought new in August of last year (2015).
Click to expand...
Click to collapse
flash this solved my problem http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Flashed the persist.img the problem still occurs. 15 minutes after the flash the phone shutdown, black screen.
Your phone battery is dying...replace your phone battery and all the problem will go away....random reboot a couple of times and then goes straight to bootloop is a sign of a dying battery....trust me i know this cause it happen to me before and i'm sure you have the same problems....
this problems will get worst when you can only boot into your rom while your phone is connected to the charger and goes straight to bootloop when you disconnect the charger....
iPusak Gaoq� said:
Your phone battery is dying...replace your phone battery and all the problem will go away....random reboot a couple of times and then goes straight to bootloop is a sign of a dying battery....trust me i know this cause it happen to me before and i'm sure you have the same problems....
this problems will get worst when you can only boot into your rom while your phone is connected to the charger and goes straight to bootloop when you disconnect the charger....
Click to expand...
Click to collapse
Shouldn't the battery meter go crazy after reboots or something ? Well i guess i'll try this, the battery is not a costly component. Are there perhaps any bigger batteries than the original one with bigger backs ?
oski131 said:
Shouldn't the battery meter go crazy after reboots or something ? Well i guess i'll try this, the battery is not a costly component. Are there perhaps any bigger batteries than the original one with bigger backs ?
Click to expand...
Click to collapse
Nope...the battery remains like normal but random reboot will happen more regularly until bootloop....
Not sure if there is a bigger battery but there is one thread here that show one battery with 3600mAh and don't buy OP2 battery as it is not compatible with OPO...
Sent from my A0001 using Tapatalk
Ok thanks for the help, will report back with new battery.
Switched the battery, the random reboots still happen, decided to do a clean flash, after wiping the phone in TWRP during the flash of GAPPS the phone rebooted itself and is in a boot loop currently.
Ok so the reboots stopped, it was a battery issue, but now i have a problem with battery indicator it's stuck at 50 % all the time and the phone does not show when it's charging (no information, no LED color), but the battery is being charged because when i shut it down and connect the charge and battery level (which shows when the phone is off) increases.
I've tried to use it untill it shuts down then i charged it while it was off for 6 hours, but after turning it on it still showed 50 %. I've also deleted the batterystats.bin using TWRP but it still did not help. Any ideas how to make it show the correct % ?
oski131 said:
Ok so the reboots stopped, it was a battery issue, but now i have a problem with battery indicator it's stuck at 50 % all the time and the phone does not show when it's charging (no information, no LED color), but the battery is being charged because when i shut it down and connect the charge and battery level (which shows when the phone is off) increases.
I've tried to use it untill it shuts down then i charged it while it was off for 6 hours, but after turning it on it still showed 50 %. I've also deleted the batterystats.bin using TWRP but it still did not help. Any ideas how to make it show the correct % ?
Click to expand...
Click to collapse
told you it was a battery issues but look like you have another battery issues here...try disconnect the battery from the motherboard for 1 minutes before connect it again and do offline charge for atleast 30 minutes....after 30 minutes reboot the phone and look at the battery percentages...if its goes above 50% then you have solved your problems....if it doesn't then you might bought a bad battery....you need to contact the seller that sell you the battery and asked for replacement....
Well unfortunately after changing the battery for a second one (the random reboots started again on the new one) the issue still prevails, so i'm currently writing a ticket to oneplus in hopes of some help.
Thank you iPusak Gaoq™
iPusak Gaoq™ said:
Your phone battery is dying...replace your phone battery and all the problem will go away....random reboot a couple of times and then goes straight to bootloop is a sign of a dying battery....trust me i know this cause it happen to me before and i'm sure you have the same problems....
this problems will get worst when you can only boot into your rom while your phone is connected to the charger and goes straight to bootloop when you disconnect the charger....
Click to expand...
Click to collapse
You Sir iPusak Gaoq™ are amazing. I 've searched for 2 whole weeks and no one was able to zero in on the issue.
After reading your post, I changed my battery. 3 days back. Till now my phone is as good as new.
I cannot thank you enough. I tried everything from recovery to rom to stock.
Thank you Thank you thank you.
What peace of mind now !!!!!!!
You can try this it solved my problem without changing battery :-
https://forum.xda-developers.com/k5-plus/how-to/solving-random-reboots-problem-t3682037
Hello, everyone.
I'm using an OPO since october 2014 and I had no intention of buying a new phone in the near future. But now I'm worried about it.
Abouth three weeks ago, my phone started to freeze and reboot. At the time I was using sultan's latest ROM. I thought the problem was the latest updates and, as I wanted to test Nougat, I decided to download Lineage.
To my surprise, I kept having random freezes and reboots.
While reflashing ROMs and changing kernels, I had some reboots. Yes, self rebooting while on recovery.
So I decided to get it totally back to stock and re-start fresh.
Phone froze and restarted on COS initial config. And, after that, rebooted again when updating Gmail apps.
During these three weeks, it kept on with no reboots for, at max, around 40 hours.
Is there any way I can test my phone to determine if it's a hardware issue? It all makes me think it is. :/
Any clue is welcome.
Thanx.
Cappelletti said:
Hello, everyone.
I'm using an OPO since october 2014 and I had no intention of buying a new phone in the near future. But now I'm worried about it.
Abouth three weeks ago, my phone started to freeze and reboot. At the time I was using sultan's latest ROM. I thought the problem was the latest updates and, as I wanted to test Nougat, I decided to download Lineage.
To my surprise, I kept having random freezes and reboots.
While reflashing ROMs and changing kernels, I had some reboots. Yes, self rebooting while on recovery.
So I decided to get it totally back to stock and re-start fresh.
Phone froze and restarted on COS initial config. And, after that, rebooted again when updating Gmail apps.
During these three weeks, it kept on with no reboots for, at max, around 40 hours.
Is there any way I can test my phone to determine if it's a hardware issue? It all makes me think it is. :/
Any clue is welcome.
Thanx.
Click to expand...
Click to collapse
Get your device checked at a local shop. Looks to me like a battery or logic board issue.If it's battery then you can get a replacement but if its logic board then yes,you should consider buying new device.
Mr.Ak said:
Get your device checked at a local shop. Looks to me like a battery or logic board issue.If it's battery then you can get a replacement but if its logic board then yes,you should consider buying new device.
Click to expand...
Click to collapse
I'm fairly sure that there is no local shop that could check it.
Right now, before checking this thread, I let the battery completely drain and now it's on the wall recharging. I'll enter recovery when it's 100% charged and do a factory reset. Then install everything back and use it for a few hours.
Let's see it that helps.
Thanx for the reply.
- phone battery completely drained
- phone battery completely charged
- booted to recovery and factory reseted
- initial COS configuration done without any freeze and/or reboot
- updating Google Apps
So far, so good.
And it rebooted twice, during apps update.
Although it updated main Google apps, it was not supposed to reboot.
:/
Hmmm...if random reboot but able to boot normally afterwards then you need to tweak the kernel a little bit but if is random reboot and then stuck at 1+ logo or bootanimation then your battery is dying....
to check whether the battery is dying just wait until next reboot...if it stuck on 1+ logo or bootanimation, turn off the phone completely then plug in the charger...it it charge for 5 minutes in offline mode then turn it on while the charger still connected...if its boot normal then it is confirmed that the battery is dying...replace a new battery as quick as possible...
I've been living with random freeze+ automatic reboot since COS13 it's a PITA but doesn't cost me anything to wait 1min until full reboot, only problem are lucky patch on boot which take longer but nothing that bad. I was never able to troubleshot the issue, usually happens to me when I receive some notification I see the LED and try to unlock but the phone stays blacked out (even though it's clearly on since notifications are shown on the LED) until I force reboot.
Over the years I tried insane amount of ROMs and kernels, nothing changed, adding to that the fact that 10% of the times when i put it in charge (original charger+cable) says 7h or 6h until full charge (and I actually have to wait all that time), I just have to unplug and try again until it fixes. It's not the charger because I tried it with other phones, so I started to assume my problems are the small board with the charging board + battery. But I never had the willing to change it. I'm "fine" with how it works.
iPusak Gaoq™ said:
Hmmm...if random reboot but able to boot normally afterwards then you need to tweak the kernel a little bit but if is random reboot and then stuck at 1+ logo or bootanimation then your battery is dying....
to check whether the battery is dying just wait until next reboot...if it stuck on 1+ logo or bootanimation, turn off the phone completely then plug in the charger...it it charge for 5 minutes in offline mode then turn it on while the charger still connected...if its boot normal then it is confirmed that the battery is dying...replace a new battery as quick as possible...
Click to expand...
Click to collapse
It does not get stuck. At times, it reboots during boot. Some times (rarely) it does that for two or three times and then turns off. But most of the time it freezes, reboots and I can use it normally for hours and hours.
seanwlk said:
I've been living with random freeze+ automatic reboot since COS13 it's a PITA but doesn't cost me anything to wait 1min until full reboot, only problem are lucky patch on boot which take longer but nothing that bad. I was never able to troubleshot the issue, usually happens to me when I receive some notification I see the LED and try to unlock but the phone stays blacked out (even though it's clearly on since notifications are shown on the LED) until I force reboot.
Over the years I tried insane amount of ROMs and kernels, nothing changed, adding to that the fact that 10% of the times when i put it in charge (original charger+cable) says 7h or 6h until full charge (and I actually have to wait all that time), I just have to unplug and try again until it fixes. It's not the charger because I tried it with other phones, so I started to assume my problems are the small board with the charging board + battery. But I never had the willing to change it. I'm "fine" with how it works.
Click to expand...
Click to collapse
I'm "almost" fine with the way it works for me. As most of the time it's fully operational.
I found a OPO with damage screen for sale here. He guy didn't want too much $ for it. I bought it and will receive next week. Will try to swap logic boards.
Let's see what happens.
Was able to have logcat running when the device froze (during game) and rebooted.
Is anyone able to see any error on the log that could make the device freeze and reboot?
Got the broken screen OPO two days ago. Yesterday my phone was impossible to be used. Rebooting like hell.
I swapped logic boards and all is fine. No freezes and reboots (of course, it's pratically another phone). I kept only my screen, housing and battery.
My logic board had a 2.5 sticker on it. The one I got now has a 2.1 sticker. Does anyone know what's that about?