Related
HELP,
yesterday, I was using my nexus 7 for normal use, wasn't playing game, just browsing with chrome. the battery was 8 percent when I last saw it. I then proceed to charge it, but the thing suddenly just shut down itself. I thought I misread the battery percentage, so I charge it anyway. about an hour later, i checked on my nexus 7, turn it on, got to the boot screen, got to the home screen, use it for about 15 minutes, and suddenly, the screen black out, it was flickering like crazy, and making some white noise ish sound. I panicked so I hold down the power button and turn it off. I turn it on again, and after about 30 seconds, the same thing happened again. I was using motley's kernel with 520 GPU, and I thought, maybe my nexus 7 cant handle the GPU OC. So I went to recovery, tried playing with recovery for about a minute or so, but the screen didn't flicker at all on the recovery. So I flashed the 484 GPU version of motley's kernel. When I reboot to system, the same thing happened again. So I thought, maybe if I restore to my old backup, it would not be like this any more. so I wipe the data, dalvik, and cache, and I restore my old backup. But the same thing happened again, only this time, after I turn it off, it make a high pitched sound.
I waited for about 6 hours, and now when I turn my nexus 7 on again, it works normally.
So, what has happened to my nexus 7?
bump
I'd say it is the overclock. Graphic cards do some weird stuff when overclocked. You can burn up your GPU doing that and cause it to forever freak out. I always shied away from GPU overclocks.
Sent from my Nexus 7 using xda premium
would that cause any permanent damage?
keni.mardira said:
would that cause any permanent damage?
Click to expand...
Click to collapse
It should be ok if you reflash back to stock rom to make all the hardware back to reset mode. A warning always given when we try to flash rom with oc created.
i also experienced this one, also received a battery warning and then suddenly screen went blank. then same weird thing happened as the one above. I'm on paranoid android rom and i'm quite sure it's not overclocked or something. Was only able to get back to normal by holding the power button for around 15-20 seconds...
Happens to me
This will happen to me a lot when my nexus 7s battery dies, I plug the tablet in and then immediately try to start it up. It will work for around 30 seconds then look like an old TV without a signal. I am on stock everything, no rooting or custom Roms (yet). I always thought it had something to do with battery calibration being off and the tablet not having enough power to run, because it always works fine when I charge it before attempting to boot.
I have also noticed that every once in a while the screen will have a vertical line of pixels flicker.
Same thing happened to me yesterday...
I got the "low battery" warning and after some time the screen started flickering in many colors and there was a weird static noise.
I pushed the on/off button, but it wouldn't turn on again. After a few minutes of charging, I could turn it on again.
This isn't normal behaviour, is it? Shouldn't the N7 perform a regular shut-down when the battery has no juice left?
I'm on the rooted stock rom btw.
androidswagz said:
This will happen to me a lot when my nexus 7s battery dies, I plug the tablet in and then immediately try to start it up. It will work for around 30 seconds then look like an old TV without a signal. I am on stock everything, no rooting or custom Roms (yet). I always thought it had something to do with battery calibration being off and the tablet not having enough power to run, because it always works fine when I charge it before attempting to boot.
I have also noticed that every once in a while the screen will have a vertical line of pixels flicker.
Click to expand...
Click to collapse
+1 bro. I am having the same problem. what do we need to do ? it is same with all nexus 7's . should we claim the warranty or just neglect it ? wat say ?
Aditya88 said:
+1 bro. I am having the same problem. what do we need to do ? it is same with all nexus 7's . should we claim the warranty or just neglect it ? wat say ?
Click to expand...
Click to collapse
I faced the same problem. I dont know when the battery might have drained out, but on starting the tab on low battery, it suddenly started showing black screen with little grains and suddenly stopped with a noise. I charged, started the tab again while charging, and the battery reading stuck at 21% even after charging for 20 mins. Within 5 mins, it happened again. Now after 35 mins of charging, I start it again, it boots normal, and now its reading the battery percentage in an incremental value (started with 22%) and now its again stuck at 23%
Is this a HW related issue? Or do you think it is more of SW related issue? If it is more towards the HW side, we better have it replaced. Mine is C70 model.
bump
just happened to me... it may have run out of juice... didn't turn on when I tried, so I guess it did... then I put it on the charger, tried booting it, went away for a sec and when I came back I also got this black screen with some flicker and a static noise...
will now try to charge it over night before trying again...
Nexus 7/Google problems
I received my Nexus 7 on Aug 21 after hearing the rave reviews. It didn't come with app for a camera, so I downloaded one.
The camera didn't work. I re-booted it & it worked this time. Downloaded Skype - whole reason for getting the tablet - to stay in touch with family that is far away. Tried to Skype - camera wouldn't work. Rebooted - worked this time again (getting tired of having to reboot for something I want to use to work). On Sept 2, sent message to Google inquiring about camera & app I downloaded. Only response - "thank you for contacting...blah, blah, blah - check out Q&A." All along, the tablet would shut itself down & reboot randomly (battery fully charged sometimes). On Sept 13, I shut it down & charged it. After a full charge, I tried to power it back on. Tried again several times that night & then the next morning. Called Google (who I bought it from). Told them I didn't want a piece of junk that wouldn't work. He told me it was past my remorse period. (The only remorse I have is buying their piece of crap instead of a reputable one.) I finally did get it to come back on, but camera hasn’t work since even after a complete factory reset. Any way – in order to get this one fixed, I have to “buy” a new one, then send back the old one & be reimbursed. Is this a legitimate business practice?
hi,
since today i have the same issue. did nothing special, just swichting from g currents to chrome. stock rom, no modifications, not rooted, everything original
n7 suddenly had a black screen(battery was at 28%). nothing worked, no powerswitch(10-30 secs). when connected to original power supply and cable, it boots up.. google logo .. glowing X.. lockscreen. then, approx. 30 sec later it turns off again(screen black). usb cable still connected. after some time it comes up again.. and repeats the procedure. after some cycles it stops, and when i reconnect the usb calbe it starts over again. sometimes, before it turns black, it shows a flickering screen and sometimes fizzling sound.
any suggestions?
I had this same issue right after the 4.2 ota update, after leaving it on charge overnight it seems fine now after a couple of discharge / charge cycles
Its like after the update it was over estimating the battery level
Sent from my Nexus 7 using xda premium
Same thing!
I have a completely stock Nexus 7, and the EXACT same problems are happening to me too! The first couple of times it happened my tablet would reboot normaly. But now, my tablet won't boot up at all. Any suggestions on what I should do? Also, remember, I have no mods installed.
Happening to me too.My N7 shut itself down because of low battery a couple hours ago and I haven't been able to get it to boot since. When I plug it into the charger it shows a flickering screen like a tv with no signal but with less white flickers. I've tried multiple chargers and cables but I could only get it to boot up a couple times and both times it did not show that it was charging even though it was plugged in and the battery was at 0% so as soon as it boots up it shuts itself down again because of low battery.
So now I've got it on the charger, screen all a'flicker, waiting for it to get a charge but I've got a feeling its not even charging because, like I said, the few times it has booted it showed the battery at 0% and not charging.
I guess I'll try to leave it alone for a while and see if it will start up after being plugged in for a bit.
EDIT: I let it sit there and charge for about an hour or so (with the screen flickering) and I was finally able to get it booted. It said it only had 3% battery but now it seems to be charging as fast as usual.
devhen said:
EDIT: I let it sit there and charge for about an hour or so (with the screen flickering) and I was finally able to get it booted. It said it only had 3% battery but now it seems to be charging as fast as usual.
Click to expand...
Click to collapse
Yup... I've let mine sit there turned off and charging over night... helped!
Just had a problem with the Nexus 7 not charging when battery was likely fully depleted. Putting a charge cable in was automatically booting the Nexus 7 up and wouldn't charge shutting down right after. Loops going on and off. What I did was plug a charge cable in and hold power+both volumes and now I believe I am charging at the bootloader screen. It stays on so I will leave it like this and if it doesn't resolve the issue I will try recovery once it is charged.
I've just started having the same issue. Has happened twice when battery gets to 8%, suddenly jumps to 0, shuts down, then after a few seconds restarts itself. Gets to home screen for a few seconds, battery showing 8, then jumps to zero, switches off and has flickering blocks on screen with static noise. This keeps repeating, only way I have found to solve it is to load into bootloader, then select power off. Device charges normally then and once charged works fine. I am unlocked and rooted but running stock 4.2.1, think I'll just have to return it for a warranty claim.
Based on what you experienced, the lesson here is your device can't handle the GPU over clock of more than 446mhz or it will do some crazy stuff.
Sent from my Nexus 7 using xda app-developers app
For the purposes of documenting EVERYTHING, here we go:
- I charged my phone last night after a long night of Ingress. I kept it mostly charged with my battery pack last night anyway, so I probably came home with ~50%.
- Woke up with 100% charge this morning
- Saw the new nightly for CM 10.1 and flashed it because it has GPS fix. Flashed Franco r70 also because he released that.
- Took a couple of work calls this morning while plugged in at my bed due to emergencies.
- Dropped phone once in garage while running back and forth, but I have a TPU case on. Phone seemed fine. No cracks no scratches.
- Decided it's lunch time so I wanted to go play Ingress while grabbing lunch.
- Plugged phone in to car charger and drove to nearest portal.
- As I did a uturn my phone slipped from my lap into the cup holder next to me. Like a 6 inch drop. Phone started BEEPING and showed WHITE SCREEN OF DEATH.
- It was LOUD. I did a Volume Down + Power and it rebooted. Saw the Google splash screen and CM10.1 bootup animation.
- Looked away for a few seconds and it seems the phone never booted.
Now I cannot power on the phone at all. I held down every combo of keys possible. I saw the LEDs flashing RED if I held power for like 10+ seconds or something. It flashes 12 times and then I think it stops and then the flashing cycle restarts.
I had 100% battery but from quick reading it seems sometimes the battery resets itself. I have my Nexus 4 plugged into to a 2A charger, my Nexus 10 charger right now hoping it will recover.
I wanted to list all the facts, but I know people will start blaming things: "You dropped the phone" "You flashed CM10.1" "You flashed Franco Kernel." Well I used my phone for an hour or two surfing today and calling already, and it was fine. Maybe the slip into the cupholder screwed everything up. But until we see mass failures due to Franco or CM10.1 0209 nightly I think we can rule that out for now, or at least keep it as a not likely to have caused my phone to blow up.
Maybe the drop tripped some circuitry inside, who knows? But it was fine.
But what I'm interested in is:
1) Anyone have their phone WSOD before and have the speaker/earpiece just BUZZ/beep (continuously)?
2) Any thing I should try?
Rant:
- Ugh. I've dropped my SGS2, Nexus S dozens of times. They always have cases, but damn. This is ONE fragile phone. Oh I also have an iPhone 5 for work that I've dropped a few times too. Sad
- Thanks to the no SD card policy, no removable battery, I can't do anything. I learned my lesson with my SGS2 when it once wiped internal memory. I keep everything on the SD card like weekly titanium backups, nandroid backups. At least I could pull data if I had an SD card. Now I'm screwed.
On the bright side:
- There's another Nexus 4 that just got delivered to my house this past Thursday....
Hey everyone!
I recently left Samsung and decided to try out Nexus 4. I actually planned to test it out so I kept the plastics on the charger and everything, and left everything in the box because I want to sell it for the Nexus 5. Anyways, I've used it for exactly a week now and it's been working just fine, but last night was the second time I left it charging overnight. Since I kept all of its stuff in the box, I use the charger from my Nexus 7 to charge it. It's been working fine so far, but today I woke up from my alarm, took my phone off charge and it worked perfectly. I went back to sleep with the phone beside me and when I woke up, it wouldn't turn on. Anyways, I got really worried and eventually it safe booted when I pressed power + vol. down. I pressed "Start" and now it's up and running but when it powered back on, it showed 85% battery instead of 100% considering it was on charge for about 8 hours. I know this isn't because of battery hibernation because I put it on charge while it was at about 4% I believe. I've looked around everywhere online and I can find people with similar problems but all of them have something like the phone going into hibernation or such. But Mine did not do anything like that. Can anyone please explain why this happened? The phone still has warranty but I really can't afford to go without a phone for 3 weeks if I send it in. Thanks so much!!!
P.S. It's running the latest KitKat, I've never rooted it, flashed it or anything like that. I am running the Google Experience Launcher.
Edit: I read that Nexus 7 chargers use 0.8 more current that the Nexus 4 chargers. Can that be the case? Thanks again guys!
tashad said:
Hey everyone!
I recently left Samsung and decided to try out Nexus 4. I actually planned to test it out so I kept the plastics on the charger and everything, and left everything in the box because I want to sell it for the Nexus 5. Anyways, I've used it for exactly a week now and it's been working just fine, but last night was the second time I left it charging overnight. Since I kept all of its stuff in the box, I use the charger from my Nexus 7 to charge it. It's been working fine so far, but today I woke up from my alarm, took my phone off charge and it worked perfectly. I went back to sleep with the phone beside me and when I woke up, it wouldn't turn on. Anyways, I got really worried and eventually it safe booted when I pressed power + vol. down. I pressed "Start" and now it's up and running but when it powered back on, it showed 85% battery instead of 100% considering it was on charge for about 8 hours. I know this isn't because of battery hibernation because I put it on charge while it was at about 4% I believe. I've looked around everywhere online and I can find people with similar problems but all of them have something like the phone going into hibernation or such. But Mine did not do anything like that. Can anyone please explain why this happened? The phone still has warranty but I really can't afford to go without a phone for 3 weeks if I send it in. Thanks so much!!!
P.S. It's running the latest KitKat, I've never rooted it, flashed it or anything like that. I am running the Google Experience Launcher.
Edit: I read that Nexus 7 chargers use 0.8 more current that the Nexus 4 chargers. Can that be the case? Thanks again guys!
Click to expand...
Click to collapse
Charger could be one problem. It's better to use the stock one.
What you had there was a BSOD ( black screen of death). Basically, the cpu gets stuck when trying to sleep. Software issue. Battery consumption is higher. Plus a reboot may have taken some more battery.
abaaaabbbb63 said:
Charger could be one problem. It's better to use the stock one.
What you had there was a BSOD ( black screen of death). Basically, the cpu gets stuck when trying to sleep. Software issue. Battery consumption is higher. Plus a reboot may have taken some more battery.
Click to expand...
Click to collapse
Phew! Thanks!! I was so worried that this was a hardware issue! I am a developer so I was testing out a tetris app yesterday, that can be probably cause I guess. Or maybe that just happens to the CPU sometimes. I've never done anything to overload it or anything but maybe it was working too hard to control all that extra power it was getting from that Nexus 7 charger. But that makes alot more sense! I was really worried because I baby all of my electronics and I would hate to have to send my phone into Google or for anything to be wrong with it. Software issues can all be fixed with a factory reset right? Thank you so much! I was extremely paranoid! Thanks!
tashad said:
Phew! Thanks!! I was so worried that this was a hardware issue! I am a developer so I was testing out a tetris app yesterday, that can be probably cause I guess. Or maybe that just happens to the CPU sometimes. I've never done anything to overload it or anything but maybe it was working too hard to control all that extra power it was getting from that Nexus 7 charger. But that makes alot more sense! I was really worried because I baby all of my electronics and I would hate to have to send my phone into Google or for anything to be wrong with it. Software issues can all be fixed with a factory reset right? Thank you so much! I was extremely paranoid! Thanks!
Click to expand...
Click to collapse
Hi i can buy lg nexus 4 8gb, problem with phone is is itself reboot even in hboot recovery etc.
seller say:
"Phone stopped working after updating to the latest software, its gone into sleep mode does not switch on. Recovery mode turns it on but on most occasions turns of after a minute."
Is software issue or hardware ??
Regards
Everyone, please help me. I don't know what else to do. I am desperate here!!!
So, I've had my Galaxy Note 4 since the day they came out (October 24th, 2014), and I baby my phone.
Anyway, I've never dropped it, got it wet - nothing.
Last week, out of nowhere (I don't recall downloading anything out of the ordinary), my phone started getting extremely sluggish. I wiped the cache partition, but that didn't solve my issues.
Then, the phone was shutting down (abruptly, not powering down) out of nowhere. So, I pulled the battery, and did so many other recommended things.
Now, I cannot turn on my phone without first pulling the battery. Every so often, the phone shuts down (abruptly) and I have to pull the battery to start it up again.
I've changed batteries to back to my original battery, but that didn't help.
Then, every so often a screen comes on with the Android character saying, "Downloading. Do Not Turn Off Target !!"
Please help me!!! What can I do? What should I do?
I love this phone and it's gonna be a long time before the Galaxy Note 8 comes out!
Dankees said:
Everyone, please help me. I don't know what else to do. I am desperate here!!!
So, I've had my Galaxy Note 4 since the day they came out (October 24th, 2014), and I baby my phone.
Anyway, I've never dropped it, got it wet - nothing.
Last week, out of nowhere (I don't recall downloading anything out of the ordinary), my phone started getting extremely sluggish. I wiped the cache partition, but that didn't solve my issues.
Then, the phone was shutting down (abruptly, not powering down) out of nowhere. So, I pulled the battery, and did so many other recommended things.
Now, I cannot turn on my phone without first pulling the battery. Every so often, the phone shuts down (abruptly) and I have to pull the battery to start it up again.
I've changed batteries to back to my original battery, but that didn't help.
Then, every so often a screen comes on with the Android character saying, "Downloading. Do Not Turn Off Target !!"
Please help me!!! What can I do? What should I do?
I love this phone and it's gonna be a long time before the Galaxy Note 8 comes out!
Click to expand...
Click to collapse
Could be a faulty battery because the symptoms sounds similar to mine.
What happened to me was :
Phone would shut down randomly and would only switch on when plugged and charging.
Phone would shut down randomly and would only switch on after pulling out the battery.
Phone would randomly reboot.
Phone would discharge at a very quick pace. 20% for 5-20 minutes of usage.
Phone would only switch on when plugged into a power source but would bootloop when unplugged, even at 100%.
I managed to remedy the situation by buying a new battery. Although you did mentioned that you replaced it with the original battery, I suspect that there might be some sort of batch issue or something when it comes to the Note 4 battery. This current battery that I'm using is the third battery I bought for my Note 4 (because Samsung did not honour their warranty) and the only one that did not came from a Samsung authorised dealer and so far the issues seems to be gone. My phone stopped shutting down randomly and now I'm able to get 4 hour SOT with 12 hours of battery. Not that I'm suggesting you to get a fake battery but it's worth a try to see that it's not a motherboard issue.
My first two battery that came from Samsung and an authorised dealer both had issues within one year respectively and if you bring it to Samsung they will claim it's a motherboard issue and will charge you a few hundreds for a replacement so a new battery is worth a try.
So, I replaced my OEM battery with an Anker battery over a year ago. When this issue started, I put the OEM battery back in. The same issues occurred and the battery drained faster, so I put the Anker one back in.
Did adding a new battery fix your issues? It seems like you might have had the same issues as me.
Did that boot screen with the big Android guy come up on your phone as well?
Did you do a factory reset upon loading the new battery in?
I really love this phone, as you do, and I really want it to work and last!
Dankees said:
So, I replaced my OEM battery with an Anker battery over a year ago. When this issue started, I put the OEM battery back in. The same issues occurred and the battery drained faster, so I put the Anker one back in.
Did adding a new battery fix your issues? It seems like you might have had the same issues as me.
Did that boot screen with the big Android guy come up on your phone as well?
Did you do a factory reset upon loading the new battery in?
I really love this phone, as you do, and I really want it to work and last!
Click to expand...
Click to collapse
Hi there,
I had exact the same problems. I think it is your flashmemory that is causing the problem. When the phone suddenly reboots into downloadmode you normally will see an error message in red saying "emmc read failure". This is your flashmemory. I ordered a new motherboard via alieexpress and replaced it myself, which is not difficult. You can find tutorial on youtube.
My phone is working perfect now.
Dankees said:
Everyone, please help me. I don't know what else to do. I am desperate here!!!
So, I've had my Galaxy Note 4 since the day they came out (October 24th, 2014), and I baby my phone.
Anyway, I've never dropped it, got it wet - nothing.
Last week, out of nowhere (I don't recall downloading anything out of the ordinary), my phone started getting extremely sluggish. I wiped the cache partition, but that didn't solve my issues.
Then, the phone was shutting down (abruptly, not powering down) out of nowhere. So, I pulled the battery, and did so many other recommended things.
Now, I cannot turn on my phone without first pulling the battery. Every so often, the phone shuts down (abruptly) and I have to pull the battery to start it up again.
I've changed batteries to back to my original battery, but that didn't help.
Then, every so often a screen comes on with the Android character saying, "Downloading. Do Not Turn Off Target !!"
Please help me!!! What can I do? What should I do?
I love this phone and it's gonna be a long time before the Galaxy Note 8 comes out!
Click to expand...
Click to collapse
Same issue here, started over a week ago, I have tried so many things, no results, you can't do anything, just gotta change the motherboard.
Same issues for me also. I replaced the battery,with no positive effect. The only thing to help is installing the app wake lock. Phone now works, but this does not solve the poor ram handling.
2018 may be late in the game to become a new owner of a OnePlus 2 phone. But here I am. My main phone at present remains a Samsung Note 4, and I'm trying to get a feel for how this old (but not as old as the Note 4) phone can be repaired. My issues are a mix of battery, possible circuit board, and other problems / eccentricities.
The phone was given to me non-working. I have a minor-league reputation for rescuing phones, so thought I'd try this one.
First, I had to get it up and going. Nothing worked initially. I wasn't delighted to find out the battery is only accessible after removing two covers and about 30 microscopic screws. I reset it by pulling the small "plug" at top center-right and the phone decided to allow me to boot. I immediately (per instructions I found elsewhere here) went to fastboot and wiped the cache.
I did manage to install TWRP and the latest (as of a few days back) version of Lineage 8.1. But then the problems began again. The phone would suddenly, after charging for a while (and reporting a battery that was nearly charged), shut down. No charging icon showed on the screen.
Fast foward. Today, I got a cheap knock-off battery in the mail. It intially worked and I got it nearly charged. But after more spontaneous reboots I noticed something odd; in TWRP, the battery said only 50% charged while in Lineage it said 97% charged. So once again I wiped the cache and this time the ART/Dalvik cache as well (pointless, but ya never know).
This did get the two percentage reports matching up. And initially it got the phone working again. But alas, once again, the phone started the shutting down.
Currently, I'm leaving it overnight to charge - if in fact it is charging (how does one tell)? If that doesn't work, I'm thinking about using Odin to totally reflash the original version of the operating system.
Any other ideas or input - including laughing at me for bothering with this - is permitted.
I will say that the engineering of this phone compared to the older Note 4 leaves the Note easily the winner; to take its battery out is a matter of 20 seconds. Really not impressed with my OnePlus experience so far...
Thought I'd update things. After spending a day on sites (here and on the official OnePlus community boards) I tried any number of fixes. I'm reasonably convinced the only way to somewhat consistently start my particular OnePlus 2 phone is to:
1. Open it up, thus voiding the warranty (hehehe.... by now that's void anyway).
2. Unplug the battery's small plug at upper right-center of battery (a fingernail works fine, but do make sure the phone isn't plugged in!)
3. *Leave the back off* or at best gingerly snap it on but without attaching the screws. (Every time I did so, even after extensively using the phone while it lay on my sofa's arm and rebooting it numerous successful times previous to replacing the screws, the phone refused to reboot.)
4. I also cleaned the usb c socket with a wood toothpick and was a little surprised at how dirty it was; I did the same in a minimal way to the battery contacts.
5. I found no real use to having the actual OnePlus charger; I used it a bit but my best results came from the Samsung charger and a new (though cheap) usb c cable I nabbed via ebay.
Today I did get the phone going and intentionally wiped Lineage and installed the latest (2017) version of the OnePlus2 official os. It went on fine. I rooted it, installed apps, and (as mentioned) repeatedly shut down and restarted the phone, which promptly restarted with only a 3 second lag. I did this 5 times because one thread I found suggested this was an official OnePlus suggestion. (I rolled my eyes but did it anyway.) Played with the phone a bit, then shut it down again and screwed the back on. As noted, the phone suddenly wouldn't turn on again.
In summary, I'm not sure if this phone can be meaningfully resurrected. If I knew where what may be a short in it was, I could possibly replace that part. But I have little idea and am not quite the geek enough to sort that out. I am guessing at a short because without the lid or screws, it wants to work. It wants to be a good phone for me and I'll keep toying with it for a while longer.
Any suggestions appreciated.
Third post is a question for others:
Has anyone else experienced their OnePlus 2 working fine *without* the back cover screwed on, but as soon as it was screwed on the phone stopped working and wouldn't start again? And, if so, did they ever sort out why?
I'm going to make this a separate discussion.
Hey. I experienced the same symptoms with a "official" replacement battery I found online. Random reboots over and over again until I couldn't even turn it one anymore.
TWRP was always showing different battery percentages than OS.once I put back in my old but original battery that came with the phone it turned on again and it works flawlessly again.
maikl91 said:
Hey. I experienced the same symptoms with a "official" replacement battery I found online. Random reboots over and over again until I couldn't even turn it one anymore.
TWRP was always showing different battery percentages than OS.once I put back in my old but original battery that came with the phone it turned on again and it works flawlessly again.
Click to expand...
Click to collapse
This is something I've read, and may well do. It also, however, raises another thorny set of issues re battery calibration. I understand that sometimes new batteries have to be "calibrated" by being charged, discharged completely, charged again, discharged completely, and charged yet again and discharged. After that, things are supposedly going to run right. Trouble is in my case, the phone doesn't want the battery; it keeps stopping completely and not restarting. Either the battery stats are wholly inaccurate (says around 57% charged during those brief times I've had it up) or I need to go with your idea. Trouble is there the original battery from this phone is dated 2015; I hope it has anything at all left to give.
shonkin said:
This is something I've read, and may well do. It also, however, raises another thorny set of issues re battery calibration. I understand that sometimes new batteries have to be "calibrated" by being charged, discharged completely, charged again, discharged completely, and charged yet again and discharged. After that, things are supposedly going to run right. Trouble is in my case, the phone doesn't want the battery; it keeps stopping completely and not restarting. Either the battery stats are wholly inaccurate (says around 57% charged during those brief times I've had it up) or I need to go with your idea. Trouble is there the original battery from this phone is dated 2015; I hope it has anything at all left to give.
Click to expand...
Click to collapse
Mine is dated 2015 as well and I'm getting through the day with closely 3 hours of SOT.
maikl91 said:
Mine is dated 2015 as well and I'm getting through the day with closely 3 hours of SOT.
Click to expand...
Click to collapse
I'm trying this in desperation. The phone has gone completely unresponsive at this point, and I'm looking at having a technological paper weight. Hope I can resurrect it but the odds are not good.
Some progress, some regress.
Here's what I'm seeing. I can get the phone up and running again after extensive recharging. As long as I leave the back of the phone off - that is, both the inner and outer backs - it seems willing to keep running. As soon as I snap the inner back into place, not even with the screws yet, the phone locks up. Soon after, around 10 to 20 seconds, it shuts off. Sometimes it will restart and other times it won't for a long time, even after unplugging and replugging battery.
Has anyone else run into shorting or grounding issues associated with the back (inner, the one w/ 18 screws) case?
I am now back to a dead phone. A new (3rd party) battery is my current hope... charging it for over a day now has not yet led to the phone showing any sign of life.
One other question: I know both this cable and charger work, but as they are not the "original" OnePlus charger / cable combo, could that be the difference? I'd appreciate it if there is any clear evidence regarding this question.
The below article raises a disturbing possibility, based on the reality that OnePlus cables and chargers are - by OnePlus' own admission - non-standard and possibly could harm other electronics. But on top of that, and not well explored in the article, is whether or not OnePlus' charger/cable combo might even be damaging to the OnePlus 2 (and other OnePlus phones). They "assure us" this is not the case. Hmm.
https://www.androidauthority.com/oneplus-responds-to-bad-usb-type-c-cables-658048/
I thought I'd update this thread with what may be the final installment.
I invested $70 in a highly bent but somehow still working second OnePlus 2 phone off ebay. (The guy had a great fall on a log story as to how the phone got bent.) Long story short... I gambled and won. That is, I gambled that the innards of the second phone would go into my first phone and that the first phone's screen would work. YES. And so, after playing amateur phone repairman, I have myself a OnePlus 2.
So many questions. Going to peruse this board now...