Ok, this may turn into a long question but here it goes. I the a TMO Samsung Galaxy S4, been running fine now for over 1 year, 3 weeks ago, I flashed one of Dan's 12/12 builds of GPE 5.0. Around the 20th of December, I woke up with my phone underneath me and I must have fallen asleep with it while it. (Problem isn't associated with ROM, just giving you guys everything leading to issue) I went to turn on phone and battery was pretty much dead. Ok, so I go to plug on charger and but the battery icon just keeps recycling. I decide to to pull the battery inspect everything and all is good. I cannot get the device to charge or boot! I figure it's a dead battery, bad charging cable or USB port on phone is broken.... So I take my wife's battery (she has same phone) BOOM phone boots up, I put my battery in her phone and it charges normally.
So I connect everything to the computer because I originally thought, maybe something is either wrong with the recovery, ROM or firmware. Well... USB works perfectly fine for connecting data, I'm able to transfer files to SD card without a problem. So I tried to download the newest build at them time which was 12/24. I downloaded the GPE 5.0 12/24 build then installed with success. I rebooted and literally the second it hit the homescreen setup, the phone said "powering down - shutting down" I couldn't get past that screen. I tried this a few times, same results. I thought it was a bad download, tried alternate mirrors, same result. As a last ditch resort, I downloaded the Newest firmware that was out (yes I understand it has knox, but at this point I didn't care) installed a factory IMG and rebooted into ROM. Ok.... It let me in, BUT!!!! Almost immediately I get a message saying, "device/battery overheating - closing all 2 applications......." literally could only use phone and that was it!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
At this point, I'm pretty stumped on what is going on, I think ok.... Battery is good, works perfectly fine in my wife's phone, it's not the battery. So I try charing again, the red light is blinking, error states there's a problem charging your device and the battery icon is also blinking. At this point, I'm not positive it's the USB board here's why. I cannot install any newer ROM without getting an overheating message that pops up. I also tried downloading the 12/25 build of Dan's GPE 5.0 ROM and I had the same results as the 12/24 build. The phone will boot and immediately shut down.
Here's the weird part... I can install and boot the 8/30 GPE build which is last kitkat built from Dan, I can't charge it, I get the same blinking light, but it works. My question is.... 1. Does anyone know what my issue is? 2. Are there any further troubleshooting steps I can take? 3. I would love to install one of the newer builds, but I can't what's different from 8/30 GPE to the newer 12/25 build that shuts the phone down. I'm guessing it is a safety measure because it says the phone is getting to hot.
Sounds like hardware issue. The reason it shuts down is probably as you guess it, safety measure of the kernel. Probably different than what you used or was baked with the older build. Does the phone get hot even when you don't use it?
serio22 said:
Sounds like hardware issue. The reason it shuts down is probably as you guess it, safety measure of the kernel. Probably different than what you used or was baked with the older build. Does the phone get hot even when you don't use it?
Click to expand...
Click to collapse
Yeah that's what I'm guessing. As far as the phone getting hot, negative. Phone is cool to touch if it's idle. Even when I turn it on I don't understand how it could be "overheating" The kernel is intersting.... I wonder if I was to flash the newest GPE ROM then flash say KT kernel isntead of the Googey kernel if that would have any affect. I'll give it a shot later. Thanks for the reply.
RBalber said:
Yeah that's what I'm guessing. As far as the phone getting hot, negative. Phone is cool to touch if it's idle. Even when I turn it on I don't understand how it could be "overheating" The kernel is intersting.... I wonder if I was to flash the newest GPE ROM then flash say KT kernel isntead of the Googey kernel if that would have any affect. I'll give it a shot later. Thanks for the reply.
Click to expand...
Click to collapse
That really is odd. Does the battery drain unexplainably?
serio22 said:
That really is odd. Does the battery drain unexplainably?
Click to expand...
Click to collapse
Negative. Battery has regular drain in stand by or sleep mode.
RBalber said:
Negative. Battery has regular drain in stand by or sleep mode.
Click to expand...
Click to collapse
Then it must be getting a false reading somehow
Related
I have been rooted for a while and successfully flashed a few Roms/Kerenels using rom manager. I was flashing the newest version of Myn and one of the "warm" kernels that it offered with it. Everything was going normally the rom loaded fashed the rom and kerenel the phone was reseting then out of nowhere i got the image of the white box and android guy with an arrw as if to say "android taken out of box" I left it like that for about 5 min then took the batt out and tried to reset it. I got the same image then i tried vol. up & power it vibrated 3x and did nothing. My buddy had the same problem yesterday and he got it workin. I called him and he said all he did was pull batt/restart over and over till it booted normally. I tried that about 10x then it would not turn on again. Plugged it in, no response no led light up.
Am I bricked past the point of no return, and if not what can I do to get back in business
Try volume down + power..
also if you have a spare battery on hand try that
Ive tried all button combos ect. nothing I have tried has gotten me ANY sort of response from the phone
dnicholsokp said:
Ive tried all button combos ect. nothing I have tried has gotten me ANY sort of response from the phone
Click to expand...
Click to collapse
can u get it to turn on to splash screen?
at the risk of sounding ignorant what is that/ how would i get it up because I cannot get it to do ANYTHING but sit here off with no display no led light not led when charging its almost as if it wasnt recieving power or something
can you turn it on at all?
Can you get into the phones boot loader?
Take the battery out and plug the phone into the charger let it sit for like 1 min then put the battery back in while on the charger still. Wait for the led and then
Vol down + power
Go into wipe section and wipe everything
Do you already have updated radios?
Sent from my PC36100 using XDA App
following the steps mentioned above the LED never came on I still have not gotten it to do ANYTHING... do you think that if i brought it to a tech center they would swap it out because there is no way to get it on and if they cant get it on there is no way they could tell that it was routed.. right? also in regaurds to the antennas i believe it did i think myn made me do that as part of the kernel change/rom flash
dnicholsokp said:
following the steps mentioned above the LED never came on I still have not gotten it to do ANYTHING... do you think that if i brought it to a tech center they would swap it out because there is no way to get it on and if they cant get it on there is no way they could tell that it was routed.. right? also in regaurds to the antennas i believe it did i think myn made me do that as part of the kernel change/rom flash
Click to expand...
Click to collapse
First yeah they should just exchange it at a sprint corporate store.
Second myn didn't make you do anything, he made a suggestion.
Third now I know what you did wrong, which was obviously pulled the battery while the radio was updating.
Fourth, you have no choice but to turn it into sprint as there are several documented occasions where ppl have done the exact same thing and had to exchange their phone..
Fifth get a good nights rest and head to sprint first thing in the morning!
Sent from my PC36100 using XDA App
I agree with craig... sleep on it.
Sent from my PC36100 using Tapatalk
that is the reason Why I don't flash roms.
Yea dude being that I just went through 4 evo's before I finally got it right ik the pain but you gotta just suck it up and bring the poor thing back to sprint
Sent from my PC36100 using XDA App
you pulled the battery while it was updating the radio, didnt you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just smash the phone on the floor,tell Sprint you droped it. Pay the $100.00 insurance and walla! New EVO!
Possible Fix
Last night I decided to flash Calkulin's Radio, WiMAX, PRI & NV combo..something I have done several times. Only this time I was discharging my battery and I forgot that the low battery warning had come on. So, long story short, I ended up with the little box and the android guy. I did a search and came to this thread. Anyway, out of desperation to do something, I connected my phone to fastboot commander and since I couldn't put my phone into fastboot mode the phone was not recognized. So I switched it to the system settings. No sooner than I connected it than the the progress bar started initializing under the android guy. The screen dimmed and came back on and then went to the splash sceen and booted up. I don't know if this is a fluke or what, but I'm pretty damn happy with myself for solving my own problem. Maybe this will help someone.
UPDATE: I tried to flash Calkulin's Radio, WiMAX, PRI & NV combo again to make sure everything flashed properly and the same thing happened. I connected my phone to fastboot commander and it worked again.
Trial and Error brotha Trial and MuthaF'n Error
dkdude36 said:
you pulled the battery while it was updating the radio, didnt you.
Click to expand...
Click to collapse
Yup only thing I could think of
!!!!PLEASE ASSIST!!!!
So e4gt root running aokp with my own flairs, cwm recovery, stock kernel.... its been rooted about 6months (my second one, smashed old)
so ive never had a problem until today when i was charging it via comp usb and suddenly m computer blue screened (overclocking fun) and of coarse comp shuts off and stops charging... comp comes back on line and now all i get is the blue light of death. finally got it booted into recovery from a homemade battery charger i made did a full wipe restore to factory and still getting the blue light. by now my battery dead. finally charged up again got it into odin and computer wont even acknowledge the phones existence not even in recovery mounted storage. all drivers are fine and ive tried multiple ports and multiple cables as well as 2 different computers.... the real kicker is when the phone is off and plugged in the blue light will flash for about 15min then the phone boots up and then shuts right down "battery low, connect charger". sorry about the length and the slight confusion. ive been working at this for about 3 hours..... p.s JTAG did not do anything... just covering my bases
Flashing blue light means that the battery has failed. In this case, it could be another component in the phone that is failing too. Try getting a new battery. If that doesn't work, I am afraid that you are hosed...
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
i do have an extra battery from the first e4gt i had and it was still no good... i just wasnt sure if there was something internally i could mod/tweak...
thanks tho id always prefer a second opinion
Dmiles053 said:
i do have an extra battery from the first e4gt i had and it was still no good... i just wasnt sure if there was something internally i could mod/tweak...
thanks tho id always prefer a second opinion
Click to expand...
Click to collapse
Pretty sure you're screwed bro... Sucks. But graydiggy is right, unless you're gonna try to fix it yourself.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bilgerryan said:
Pretty sure you're screwed bro... Sucks. But graydiggy is right, unless you're gonna try to fix it yourself.
Click to expand...
Click to collapse
thanks for the insight lol i need an upgrade anyway :crying:
Dmiles053 said:
!!!!PLEASE ASSIST!!!!
So e4gt root running aokp with my own flairs, cwm recovery, stock kernel.... its been rooted about 6months (my second one, smashed old)
so ive never had a problem until today when i was charging it via comp usb and suddenly m computer blue screened (overclocking fun) and of coarse comp shuts off and stops charging... comp comes back on line and now all i get is the blue light of death. finally got it booted into recovery from a homemade battery charger i made did a full wipe restore to factory and still getting the blue light. by now my battery dead. finally charged up again got it into odin and computer wont even acknowledge the phones existence not even in recovery mounted storage. all drivers are fine and ive tried multiple ports and multiple cables as well as 2 different computers.... the real kicker is when the phone is off and plugged in the blue light will flash for about 15min then the phone boots up and then shuts right down "battery low, connect charger". sorry about the length and the slight confusion. ive been working at this for about 3 hours..... p.s JTAG did not do anything... just covering my bases
Click to expand...
Click to collapse
Not sure if this will apply... but I had my phone go crazy where it would charge but as soon as I took it off the charger it would give me that ( battery low, connect charger ) and shut off. But in my case it would boot when plugged in. I went into recovery and wiped the battery stat stuff and it fixed it... probably different situation then what you're looking at but thought I'd throw it out there..
I am wondering if someone here can help me.
I have an unrooted SGIII from Sprint and have had the phone since 2012.
In the last update, to kitkat at least I have noticed some serious battery drain...in particular when I take pictures, the pictures get very grainy and then boom, the phone shuts down. Not cool.
do i need a new battery? I have read all the information about saving battery infact I can hardly see my screen my brightness is so low.
Any help would be appreciated.
Thanks
Try a factory reset after backup what you want.
If that doesn't help, try Odining the stock ND8 tar from a PC, in the development (non-original) section.
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
I can't tell you that a new battery will fix your problems. But, I replaced my battery after 9 months of use and I was amazed at the difference. Try borrowing someone's battery and see if it makes a difference? If you buy a new battery and that doesn't solve the problem, you've ruled out the battery and now have 2 batteries to switch between
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
I have this exact same problem. Any time the battery is below 40-50%, the camera could cause the phone to shut down at any time. Really, anything will cause it to shut down, but it seems like the camera will do it every single time. The phone will not stay on after that point unless you plug it in for even 5 minutes, at which point it tells you your battery is 60-70%.
This is the reason I rooted and then flashed the Odin stock ND8 the other day (http://forum.xda-developers.com/gal...rint-galaxy-s3-complete-boot-process-t2829181). I then flashed to Wicked X v7.3. It has only been two days, but the same symptoms persist. My wife has the same phone and experiences the same problems, which all started upon the update to 4.4.2.
If anybody has any ideas, I'm all ears.
huntley said:
I have this exact same problem. Any time the battery is below 40-50%, the camera could cause the phone to shut down at any time. Really, anything will cause it to shut down, but it seems like the camera will do it every single time. The phone will not stay on after that point unless you plug it in for even 5 minutes, at which point it tells you your battery is 60-70%.
This is the reason I rooted and then flashed the Odin stock ND8 the other day (http://forum.xda-developers.com/gal...rint-galaxy-s3-complete-boot-process-t2829181). I then flashed to Wicked X v7.3. It has only been two days, but the same symptoms persist. My wife has the same phone and experiences the same problems, which all started upon the update to 4.4.2.
If anybody has any ideas, I'm all ears.
Click to expand...
Click to collapse
how long have you guys had your phone any water damage? hard falls things like that?
6th_Hokage said:
how long have you guys had your phone any water damage? hard falls things like that?
Click to expand...
Click to collapse
Got the phone in December 2012, as did my wife. No hard falls that I can remember. Up until recently I had it in an Otter Box Commuter case. I took it out after I updated and started pulling the battery to try to get things to reset (never worked and like the smaller profile so I didn't put the case back on).
Tonight I installed the Xposed critical battery shutdown module and also Battery Calibration recommended in these posts http://forum.xda-developers.com/showthread.php?t=2781926 and (can't find the thread recommending Battery Calibration by Nema, but whatever). After I installed the module (and I think activated it), I ran the battery down until the phone shut off. Will charge to 100% tonight and start calibration in the morning.
The module does not appear to be working,as the phone shut down at 28% with no prior warnings that it prevented shutdown. That's unfortunate. To activate the module, do I just click the check mark and reboot?
from what I've seen water damage and hard falls can have a heavy impact on the OS(not like crack screen or digitizer but just a hard fall and phone survives) well except on water proof/shock proof phones.....but for the most part if a factory reset/Odin/Heimdall/what ever method back to stock you use doesn't fix the problem its a hardware issue
All's better after new battery
I just wanted to post a followup to my issue. After the shutdown mod and battery calibration didn't help, I bought an Anker replacement battery from Amazon. Since my wife had the same problem, I bought a two pack for $28. I charged the battery overnight and then in the morning hit the battery calibration button.
I noticed a difference right away - I was only down 7% after a few hours at work. My goal was to let the battery run down until the phone shut off, which happened at about the 30 hour mark with my playing HD youtube videos for the last hour so it would die. The battery life indicator actually counted all the way down to 1% before shutting off, which is a stark contrast to the 30% that had been occurring with the old battery.
With the new battery, I've also used the camera when it was under 30% with no problems.
My recommendation for anyone that has similar problems is to get a new battery. They are a hell of a lot cheaper than a new phone, so it's worth a shot.
Hey guys Ive been having severe battery and charging issues, tried new cables/ 2.1 charger warts etc but my battery life was still crappy. I went out and bought an extended battery and its been good exept my phone will not reach 100%. It reaches 20% overnight. I can still use it and eventually its starts going from 20% down so im pretty sure its taking charge just not displaying it properly. Any suggestions?
How long has this been going on? How many overnight charges of the extended battery?
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
ricanjoe said:
Hey guys Ive been having severe battery and charging issues, tried new cables/ 2.1 charger warts etc but my battery life was still crappy. I went out and bought an extended battery and its been good exept my phone will not reach 100%. It reaches 20% overnight. I can still use it and eventually its starts going from 20% down so im pretty sure its taking charge just not displaying it properly. Any suggestions?
Click to expand...
Click to collapse
What kernel you using? I flashed one a couple weeks ago that caused those issues.. Went away as soon as I flashed a different one. Also, when it happens, restart your phone, unplug it and then plug it back in. It tends to make it charge correctly again. Until the next time it happens.. Over night I only got to 33% before
ReapersDeath said:
What kernel you using? I flashed one a couple weeks ago that caused those issues.. Went away as soon as I flashed a different one. Also, when it happens, restart your phone, unplug it and then plug it back in. It tends to make it charge correctly again. Until the next time it happens.. Over night I only got to 33% before
Click to expand...
Click to collapse
I have the stock kernel from the moar rom. which kernel do you recommend? Sometimes I unplug the charger and it shows up as if its still plugged in and vice versa as well.
roirraW "edor" ehT said:
How long has this been going on? How many overnight charges of the extended battery?
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Click to expand...
Click to collapse
Ever since I got it, 4 days ago. And the original samsung battery does the same. Sometimes the phone will think its still plugged in even after I unplugged it for 10 minutes.
Sounds like a possible hardware issue? Especially since you just got it. If it wasn't completely stock when you got it, I would take it back to stock?
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Update today, did a factory reset through my twrp menu and I left it overnight and it reached 100% finally. This morning I recovered my nandroid backup to get all my stuff back and it has been running okay. Charging is still kind of crazy. My battery status app will show "Connected" But still discharging at -1200ma. I might just have to buy a even bigger battery so I that I dont have to worry about charging only at night. That could be a solution untill I upgrade.
ricanjoe said:
Update today, did a factory reset through my twrp menu and I left it overnight and it reached 100% finally. This morning I recovered my nandroid backup to get all my stuff back and it has been running okay. Charging is still kind of crazy. My battery status app will show "Connected" But still discharging at -1200ma. I might just have to buy a even bigger battery so I that I dont have to worry about charging only at night. That could be a solution untill I upgrade.
Click to expand...
Click to collapse
so after the factory reset your battery inside your phone reached 100% or the extended battery?
6th_Hokage said:
so after the factory reset your battery inside your phone reached 100% or the extended battery?
Click to expand...
Click to collapse
Yes the extended battery was the one that reacheD 100%. I bought this battery because I thought the original battery was going bad but that must have not been the case. It seems like the issue is somewhere else.
These newer phones seem to be lasting less and less. They are rushing too fast to make the next one LOL.
ricanjoe said:
These newer phones seem to be lasting less and less. They are rushing too fast to make the next one LOL.
Click to expand...
Click to collapse
mines bran new and its lasting 2 days on a charge with the internal battery so it could be something with your exact phone and if your phone is Sprint try using Odin to go back to stock ND8 to see if the issues disappear cause that seams to cure 90% of problems
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just wanted to post a short topic letting other users know that there may be a charging issue with WW-5.17.44.68. A couple of days after updating to the most recent firmware I suddenly began having charging issues with my Zenfone 3 Deluxe special edition. Shortly after hooking up the factory charger I would receive this error message accompanied by the same alert sound that Amber Alerts use. The only way I was able to get the phone to charge at all was to roll back to my pre WW-5.17.44.68 nandroid. Trying different chargers with different cables made zero difference. The error is dead on as pulling out the USB cord you can clearly feel it is quite hot. Ignoring or missing this error will most likely guarantee a fried charge port (minimal)! Immediately after installing my backup all issues went away. I am currently charging with the factory charger and cable now without heat/error.
Sandman45654 said:
View attachment 4409791
I just wanted to post a short topic letting other users know that there may be a charging issue with WW-5.17.44.68. A couple of days after updating to the most recent firmware I suddenly began having charging issues with my Zenfone 3 Deluxe special edition. Shortly after hooking up the factory charger I would receive this error message accompanied by the same alert sound that Amber Alerts use. The only way I was able to get the phone to charge at all was to roll back to my pre WW-5.17.44.68 nandroid. Trying different chargers with different cables made zero difference. The error is dead on as pulling out the USB cord you can clearly feel it is quite hot. Ignoring or missing this error will most likely guarantee a fried charge port (minimal)! Immediately after installing my backup all issues went away. I am currently charging with the factory charger and cable now without heat/error.
Click to expand...
Click to collapse
That's rough. I haven't bothered with the update because it's too much of a hassle right now to go to stock recovery and update. I think your best bet would be to stay on your backed up firmware and wait out the Oreo update (which should be soon as well.)
Thanks for the heads up. Hopefully it isn't a widespread issue.
asianflipboy said:
That's rough. I haven't bothered with the update because it's too much of a hassle right now to go to stock recovery and update. I think your best bet would be to stay on your backed up firmware and wait out the Oreo update (which should be soon as well.)
Thanks for the heads up. Hopefully it isn't a widespread issue.
Click to expand...
Click to collapse
After feeling how hot the USB port/plug got I am in no hurry to try it again! I could even smell the charge board heating up. That is quite a gut-wrenching smell when it comes to a phone costing as much as this one. I too hope that it isn't a widespread issue.
I completed a full wipe before installing the firmware and tried multiple USB cords and chargers after. The only thing that fixed the issue was downgrading. That leaves the firmware as the main suspect which is why I decided to post my findings.
If anyone is considering updating PLEASE have a recent nandroid FIRST.
Thanks for the warning, indeed they did add battery improvement to the changelog....
I did update to the newest firmware and I am charging using Zenfone 2 chargers, I just checked it out and it doesn't seem too hot.... maybe it applies only to QuickCharge chargers....
though I do have an issue that when my phone is locked (aka screen is turned off, phone is running... sleep mode) I have some screen flickering... the whole screen flashes white for just one second before turning off again... kinda annoying as it also wastes a lot of battery
Chaosruler said:
Thanks for the warning, indeed they did add battery improvement to the changelog....
I did update to the newest firmware and I am charging using Zenfone 2 chargers, I just checked it out and it doesn't seem too hot.... maybe it applies only to QuickCharge chargers....
though I do have an issue that when my phone is locked (aka screen is turned off, phone is running... sleep mode) I have some screen flickering... the whole screen flashes white for just one second before turning off again... kinda annoying as it also wastes a lot of battery
Click to expand...
Click to collapse
If I recall correctly the Zenfone 2 charger supports the same range of voltages. 5-9-12 volts with varying amperage.
Your screen issues could quite possibly be caused by a rogue app. I've noticed using the "Always On" feature my phone will flash white from time to time. Not the entire screen mind you, just the clock being shown with full brightness for one cycle. If you have TWRP installed it would be worth a backup/wipe to see if it is indeed software. Good luck with your issue
Good news time for everyone except me! After charging the phone twice the error message has shown its ugly face once again. So it seems that my phone is actually to blame :'-( I've cleaned the USB-C port with some contact cleaner sprayed onto a small piece of folded paper. So far it seems to have done the trick. USB-C is great for ease of use but not so great for keeping debris out.
I have found the actual cause of my issues. It's an unusual one so I thought I should share. It turns out that an old florescent table lamp I recently started using again basically turned itself into an EMP device. All of the electromagnetic interference feeding back through the surge protector has caused both my phone charger and my 6 bay 18650 (vaporizer) battery charger to malfunction. After unplugging the lamp the overheating issue has stopped. The phone charger no longer quick charges but I'll take that over a dead phone any day! The issue with my 6 bay charger, if you were curious is that I have to power cycle it each time i want to establish a bluetooth connection now. Its crazy some of the curveballs life can throw your way!
asianflipboy said:
That's rough. I haven't bothered with the update because it's too much of a hassle right now to go to stock recovery and update. I think your best bet would be to stay on your backed up firmware and wait out the Oreo update (which should be soon as well.)
Thanks for the heads up. Hopefully it isn't a widespread issue.
Click to expand...
Click to collapse
It should be soon but unfortunately it won't be...