Database Users

[Q] Consistent reboot problem with tattoo

Hello there everyone!
So, first if of all allow me to say I'm a programmer/network administrator so I know things around *nix systems and Java, and right now I'm having a quite boring problem with my Tattoo.
Here's the history:
Got a Tattoo one year ago, v1.6, all going well, suddenly it started rebooting, some months ago, dropping calls and would sometimes loose network. In the meanwhile I used another phone and left the Tattoo alone.
Now I decided to pick it up again and sort things out.
Problems:
Phone sometimes reboots randomly
Phone reboots specially during phone calls
If I select the use 2G Networks Only, the phone restarts some seconds later
What I have tried:
- Changing SIM card
- Flashed latest version from: http://forum.xda-developers.com/showthread.php?t=939122
- Full wipe as well
- Formatted SD
- Factory Reset
- Cleared Dalvik Cache
Clearing Dalvik Cache allowed me to keep a phone call for more than 30 minutes though.
The weirdest situation is that *every* time I select the Use 2G Only option the phone reboost, some 5 seconds later. Every time.
Any suggestions? Completely lost here.

Shameless bump...

Late, but, I had have same problem when the battery is not calibrated.
I seems to happen when the Tattoo appears to have enough battery, but it not true.
Charging (up to 75%) and calibrating battery works for me.

enriquettoo said:
Late, but, I had have same problem when the battery is not calibrated.
I seems to happen when the Tattoo appears to have enough battery, but it not true.
Charging (up to 75%) and calibrating battery works for me.
Click to expand...
Click to collapse
It's never too late
Can you elaborate? I still have it so I'm willing to give it a go in the next hours and post results...

jpoa said:
It's never too late
Can you elaborate? I still have it so I'm willing to give it a go in the next hours and post results...
Click to expand...
Click to collapse
Charge your battery to 100%, go to your recovery, advanced, wipe battery stats. Then discharge fully and charge 100% again

Great, thanks!!

Random shutdowns?

Has anybody experienced random shutdowns on their N4? It's happened twice now for me in the last few days. I'll go to turn on the screen and find that the phone is completely shut down and needs powered back up, without me having shut the phone down.
One strange thing associated with this is that it completely wipes my battery stats.

Please provide more information.
Stock? Unlocked? Rooted? Custom rom? Custome kernel? Undervolted?

spitefulcheerio said:
Please provide more information.
Stock? Unlocked? Rooted? Custom rom? Custome kernel? Undervolted?
Click to expand...
Click to collapse
Sorry, stock rooted. Both times happened when there was plenty of juice left in the battery, this morning when it happened I was still at 95%.

hfuizo said:
Sorry, stock rooted. Both times happened when there was plenty of juice left in the battery, this morning when it happened I was still at 95%.
Click to expand...
Click to collapse
Are you sure it's actually shutting down?
The reason I ask is that there's an issue where the screen won't wake up, but the phone is still functional (can still hear notifications and feel vibrations etc.). It looks like it's shut down, but it actually isn't.
If so then I believe it's a known issue, even on the stock (unrooted) rom. It happens to me every now and then, and as far as I know it needs a hard reboot to fix (hold down the power button for 10 seconds).
Don't know what you mean by wiping your battery stats? A reboot would do that anyway, wouldn't it?

hfuizo said:
Sorry, stock rooted. Both times happened when there was plenty of juice left in the battery, this morning when it happened I was still at 95%.
Click to expand...
Click to collapse
There's a video on youtube showing how this phone just shuts down after running a benchmark for long enough (that was about 10 minutes at normal room temperature..)
Could it be that your phone was doing something in the background, and because of the overheating issues that it has, it just shut down to prevent damage?

jb91 said:
There's a video on youtube showing how this phone just shuts down after running a benchmark for long enough (that was about 10 minutes at normal room temperature..)
Could it be that your phone was doing something in the background, and because of the overheating issues that it has, it just shut down to prevent damage?
Click to expand...
Click to collapse
I wasn't doing anything significant right before hand. The last things I did were: checked Facebook, modified a Tasker profile, and swiped away a couple apps from the recent apps screen. Phone was cool to the touch. I was in the basement with no cell coverage (wifi connected), then moved upstairs and next time I tried to turn on the screen the phone was powered off.

Shodney said:
Are you sure it's actually shutting down?
The reason I ask is that there's an issue where the screen won't wake up, but the phone is still functional (can still hear notifications and feel vibrations etc.). It looks like it's shut down, but it actually isn't.
If so then I believe it's a known issue, even on the stock (unrooted) rom. It happens to me every now and then, and as far as I know it needs a hard reboot to fix (hold down the power button for 10 seconds).
Don't know what you mean by wiping your battery stats? A reboot would do that anyway, wouldn't it?
Click to expand...
Click to collapse
No it was shut down, had to hold down the power button for 2 seconds to boot it, felt the boot vibration and saw the boot animation. This happened after being off charger for about 2 hours, but upon booting the battery screen showed on battery for 1 minute. Usually when I reboot the "on battery" time is preserved.

Shodney said:
Are you sure it's actually shutting down?
The reason I ask is that there's an issue where the screen won't wake up, but the phone is still functional (can still hear notifications and feel vibrations etc.). It looks like it's shut down, but it actually isn't.
If so then I believe it's a known issue, even on the stock (unrooted) rom. It happens to me every now and then, and as far as I know it needs a hard reboot to fix (hold down the power button for 10 seconds).
Don't know what you mean by wiping your battery stats? A reboot would do that anyway, wouldn't it?
Click to expand...
Click to collapse
Is there a fix for the screen not waking? I'm still on 4.2(stock and rooted), does 4.2.1 fix it? I can't seem to update to 4.2.1, if it does fix it. But that's another issue...

Ya know I'm starting to think it may be my belt holster that's somehow shutting down the phone. This is the first day of my new holster and now the phone has shut itself down 3 times, each time I've noticed it after pulling it from the holster.

hfuizo said:
Has anybody experienced random shutdowns on their N4? It's happened twice now for me in the last few days. I'll go to turn on the screen and find that the phone is completely shut down and needs powered back up, without me having shut the phone down.
One strange thing associated with this is that it completely wipes my battery stats.
Click to expand...
Click to collapse
I only had N$ for 3 days.
Yesterday when I was taking a picture, camera app was running, while I was putting kids together phone screen went black. Only way to bring it back was to hold power button and it went through full boot up cycle, so I would say it did shut down on me.
Stock, no root, updated to the 4.2.1. Battery was between 50 and 75% and it did not wipe it's stats.

stud_muffler said:
I only had N$ for 3 days.
Yesterday when I was taking a picture, camera app was running, while I was putting kids together phone screen went black. Only way to bring it back was to hold power button and it went through full boot up cycle, so I would say it did shut down on me.
Stock, no root, updated to the 4.2.1. Battery was between 50 and 75% and it did not wipe it's stats.
Click to expand...
Click to collapse
Oh man that's gotta suck. Worst moment possible. Mine has shut down as well several times.

I find that my phone likes to randomly reboot when using bluetooth. May be a coincidence or not. At times the widget toggle for bluetooth stops working too, so there's something going on with bluetooth. My bluetooth problems documented here:
http://forum.xda-developers.com/showthread.php?t=2040796

hfuizo said:
Ya know I'm starting to think it may be my belt holster that's somehow shutting down the phone. This is the first day of my new holster and now the phone has shut itself down 3 times, each time I've noticed it after pulling it from the holster.
Click to expand...
Click to collapse
Does anybody know a sequence of button pushes that will shut down the device? I know holding power for 10 seconds causes a reset, but is there a combination of button pushes that initiates shutdown?

hfuizo said:
Does anybody know a sequence of button pushes that will shut down the device? I know holding power for 10 seconds causes a reset, but is there a combination of button pushes that initiates shutdown?
Click to expand...
Click to collapse
If you hold just power button it should bring a popup with Power Off option, which is a standard for most Android phones.

hfuizo said:
Has anybody experienced random shutdowns on their N4? It's happened twice now for me in the last few days. I'll go to turn on the screen and find that the phone is completely shut down and needs powered back up, without me having shut the phone down.
One strange thing associated with this is that it completely wipes my battery stats.
Click to expand...
Click to collapse
I have the same issue recently. I've used nexus 4 for 1 month, this issue just occurred recently. it shutdown without any notice. I've drop my phone once, cracking its glass back, but it doesn't seem to relate to that issue. I guess maybe this is some software problem.

Bootloop Related To Battery Percentage?!

It's my brother's phone. out of nowhere, it started boot-looping. I tried everything I know to fix it, I was pretty sure it's a hardware issue once i saw it. It keeps trying to boot, some times it passes the google logo to the colored dots but with a very slow-motioned animation, then it boot-loops again. sometimes it boots though but once I try to put the google account and stuff it boot-loops again.
I started by clearing cache and data. I tried then installing the last factory image, when it didn't work I tried also last month's image and MM image, nothing worked. I went on and tried PureNexus, LineageOs, and a punch of kernels.
I left the phone boot-looping over night and when I woke up it was booted. The battery was 5% so I connected the charger and started putting my account and fingerprint. Suddenly it boot looped again at 12% battery. I unplugged the charger and left the phone. It kept boot-looping for a while the booted up with 10% battery. I didn't try to charge it again and everything went smoothly. I started trying the stock roms again, even the beta 7.1.2, I'm now sure that it only boot-loops above 10% battery, lower that 10% it works like a charm even with games and heat.
I know it's a long A$$ post but I'm not sorry ?. What do you guys think of that issue? anyone else had the same problem?

Hrmmm... Try disabling battery saver all together. A similar situation I had with my Pixel XL. Good luck. I miss my 6P!...:crying:

nagoo1 said:
It's my brother's phone. out if nowhere, it started bootlooping.
Click to expand...
Click to collapse
Fastboot format userdata, system and cache then install NOF27B full image using flash-all.bat.

v12xke said:
Fastboot format userdata, system and cache then install NOF27B full image using flash-all.bat.
Click to expand...
Click to collapse
Isn't NOF27B a PIXEL rom? ... If yuo mean N4F26T for nexus 6p, then I sadly tried that. I did it with twrp recovery though.

nagoo1 said:
Isn't NOF27B a PIXEL rom? ... If yuo mean N4F26T for nexus 6p, then I sadly tried that. I did it with twrp recovery though.
Click to expand...
Click to collapse
Yes, sorry N4F26T. You cannot install a full image with TWRP. You need to fastboot format your cache, userdata and system partitions (not wipe with TWRP) and then fastboot flash the full Google image (not the OTA) using flash-all. bat.

v12xke said:
Yes, sorry N4F26T. You cannot install a full image with TWRP. You need to fastboot format your cache, userdata and system partitions (not wipe with TWRP) and then fastboot flash the full Google image (not the OTA) using flash-all. bat.
Click to expand...
Click to collapse
I meant that I wiped everything with twrp then flashed factory image with Flash-all. I don't know if formatting with fastboot will make a difference but I will try it, hope it works.
Thanks man

nagoo1 said:
I meant that I wiped everything with twrp then flashed factory image with Flash-all. I don't know if formatting with fastboot will make a difference but I will try it, hope it works.
Thanks man
Click to expand...
Click to collapse
Yes, formatting is different than wipe. Note any errors during the formatting. Cap your screen if you get any. Good luck.

v12xke said:
Yes, formatting is different than wipe. Note any errors during the formatting. Cap your screen if you get any. Good luck.
Click to expand...
Click to collapse
I tried formatting, got no errors, and the same freakin boot-loop. The thing is we bought this phone from USA and the warranty expired 3 weeks ago :s .. anyways, if you have any other ideas plz suggest
Thanks

@nagoo1
Your case is different from (almost) all others. People with the BLOD have no recovery mode and you are using TWRP with no issues. A few have recovery but cannot format userdata or cache and get terminal errors attempting to format. You say the phone works normally under 10% but not above. Maybe there is something wrong with the battery? Try running an app called Accubattery. Once installed, charge the phone from below 10% until the APP tells you the phone is full. Don't go by what the phone says. Don't take it off the charger until Accubattery tells you it is full. After doing this check under the "Health" tab for the estimated battery capacity.

v12xke said:
@nagoo1
Your case is different from (almost) all others. People with the BLOD have no recovery mode and you are using TWRP with no issues. A few have recovery but cannot format userdata or cache and get terminal errors attempting to format. You say the phone works normally under 10% but not above. Maybe there is something wrong with the battery? Try running an app called Accubattery. Once installed, charge the phone from below 10% until the APP tells you the phone is full. Don't go by what the phone says. Don't take it off the charger until Accubattery tells you it is full. After doing this check under the "Health" tab for the estimated battery capacity.
Click to expand...
Click to collapse
Thanks for replying. I'd like to try your method but I don't think it's gonna work for me as the phone starts bootlooping after the 10% mark and the app wouldn't stop it from doing that. I also think that battery health is OK because if I keep charging it up to a 100% while off then try to boot it, it keeps bootlooping for about 5 hours until it reaches 10% then boots normally.
I don't know if I said this before, sometimes it boots up at a higher percentage but as soon as I start using it (open any thing or even swipe left and right), it bootloops again till it reaches 10%
I tend to believe that it's a ram issue as I've seen this before in other phones, PCs and Laptops, but what does any thing have to do with this 10% battery??????

nagoo1 said:
I don't know if I said this before, sometimes it boots up at a higher percentage but as soon as I start using it (open any thing or even swipe left and right), it bootloops again till it reaches 10%
Click to expand...
Click to collapse
Did you watch the kernel logs? dmesg and after reboot /proc/last_kmsg (which will be empty unfortunately if RAM stops being powered)

rchtk said:
Did you watch the kernel logs? dmesg and after reboot /proc/last_kmsg (which will be empty unfortunately if RAM stops being powered)
Click to expand...
Click to collapse
Never done this before, I'll look it up and try to get it. I think I saw an option in twrp to copy logs.

nagoo1 said:
It's my brother's phone. out of nowhere, it started boot-looping. I tried everything I know to fix it, I was pretty sure it's a hardware issue once i saw it. It keeps trying to boot, some times it passes the google logo to the colored dots but with a very slow-motioned animation, then it boot-loops again. sometimes it boots though but once I try to put the google account and stuff it boot-loops again.
I started by clearing cache and data. I tried then installing the last factory image, when it didn't work I tried also last month's image and MM image, nothing worked. I went on and tried PureNexus, LineageOs, and a punch of kernels.
I left the phone boot-looping over night and when I woke up it was booted. The battery was 5% so I connected the charger and started putting my account and fingerprint. Suddenly it boot looped again at 12% battery. I unplugged the charger and left the phone. It kept boot-looping for a while the booted up with 10% battery. I didn't try to charge it again and everything went smoothly. I started trying the stock roms again, even the beta 7.1.2, I'm now sure that it only boot-loops above 10% battery, lower that 10% it works like a charm even with games and heat.
I know it's a long A$$ post but I'm not sorry . What do you guys think of that issue? anyone else had the same problem?
Click to expand...
Click to collapse
happened to me just now, been bootlooping since morning, phone was being charged alternately with my wall charger and usb connected to my charger, in the middle of me trying to find a solution, so the phone was adequately charged. finally getting tired of the whole trial and error i forgot to charge and was busy restoring my old recoveries when an oct 2016 backup suddenly started booting with the running colored dots and when the security screen came in and the phone died because of low battery. I had tried the same backup before but it didnt boot. can this be true ? that the bootloops are battery related..
My bootloader shows Battery as OK and i can access TWRP recovery.

anikadam said:
happened to me just now, been bootlooping since morning, phone was being charged alternately with my wall charger and usb connected to my charger, in the middle of me trying to find a solution, so the phone was adequately charged. finally getting tired of the whole trial and error i forgot to charge and was busy restoring my old recoveries when an oct 2016 backup suddenly started booting with the running colored dots and when the security screen came in and the phone died because of low battery. I had tried the same backup before but it didnt boot. can this be true ? that the bootloops are battery related..
My bootloader shows Battery as OK and i can access TWRP recovery.
Click to expand...
Click to collapse
Seems to be the same issue. I hope we both can find a solution for this.
Here are two dmesg.log I got from TWRP, I got one below 10% and one above 10% (bootlooping). I really don't know what to do with these, so we'll need some experience here
Edit: too much characters for the post, I'll attach them instead

I hope this is actually what you guys are looking for.
View attachment 4089615
View attachment 4089616

It actually sounds like you might have a hardware issue where if the phone gets too hot from running or charging the phone bootloops. This could be because of damaged memory, a damaged CPU or damaged connections to the motherboard. The phone might work at 10% or less because the phone is running cooler when the battery is close to running out since the phone is trying to preserve what is left of the charge. I seriously doubt that there is anything you can do software wise to fix that phone. You could bring it into a repair shop. Frequently they give free estimates on a repair. Good luck.

jhs39 said:
It actually sounds like you might have a hardware issue where if the phone gets too hot from running or charging the phone bootloops. This could be because of damaged memory, a damaged CPU or damaged connections to the motherboard. The phone might work at 10% or less because the phone is running cooler when the battery is close to running out since the phone is trying to preserve what is left of the charge. I seriously doubt that there is anything you can do software wise to fix that phone. You could bring it into a repair shop. Frequently they give free estimates on a repair. Good luck.
Click to expand...
Click to collapse
Yeah I think it's a HW failure too, but what makes it work without any issues under 10%? keep in mind that sometimes I leave it bootloop for hours before it reaches 10% and boots-up, which means the device is hot. Also, if i leave it to cool down with airplane mode for a while, it keeps working. I even tried playing asphalt till the phone reached 0% and shut down. It has nothing to do with heat i think, which means its not connection issue like we used to see in graphics cards before.
I just wanna know what gets triggered under 10% that makes the phone work normally? it's not battery saving mode cause i've tried it, but I'm pretty sure something changes at exactly 10% that makes it work.
I don't have a service center that I can trust over here, I called them and they told me they will try flashing the SW (not free of-course) and that if ti's not SW then they will change the main board for almost the same price as a new phone :laugh:

I could be wrong but I think the battery saver feature basically turns off your radios and reduces brightness so you can still make calls for as long as possible. But I think even with that off your phone likely consumes less energy when the battery is down to 10% because the cpu cores will no longer operate at full strength. You might be able to use the phone somewhat if you install Francos kernel and use the most battery restraining governor settings possible to keep the phone cooler and processor use at the minemum but even if that worked you would basically be turning the 6P into the equivalent of a hundred dollar phone usability wise so it's kind of pointless. I asked a repair shop here what it would cost to replace the motherboard and they said it was essentially replacing the whole phone and wouldn't make sense cost wise. I don't think any of these 6Ps will be around in a few years. It doesn't seem like they were built to last.

I knew it wouldn't work, but I had to try
I found a thread over here that fixes bootloop for a certain situation, i knew it wouldn't work but i tried it anyways.
https://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938
Following the guide I have to Restore a backup through TWRP, It further proved that It's a HW issue when it kept freezing and rebooting when trying to restore. I left the battery drain till it reached 10% then tried to restore again and it worked and booted up, but again when I tried to charge beyond 10% it bootlooped :crying:

jhs39 said:
I could be wrong but I think the battery saver feature basically turns off your radios and reduces brightness so you can still make calls for as long as possible. But I think even with that off your phone likely consumes less energy when the battery is down to 10% because the cpu cores will no longer operate at full strength. You might be able to use the phone somewhat if you install Francos kernel and use the most battery restraining governor settings possible to keep the phone cooler and processor use at the minemum but even if that worked you would basically be turning the 6P into the equivalent of a hundred dollar phone usability wise so it's kind of pointless. I asked a repair shop here what it would cost to replace the motherboard and they said it was essentially replacing the whole phone and wouldn't make sense cost wise. I don't think any of these 6Ps will be around in a few years. It doesn't seem like they were built to last.
Click to expand...
Click to collapse
Nice Idea, but I don't know which kernel manager to use with franco & what settings would be best for limiting cpu. if there's a topic about that please point it to me or give me ur thoughts

A7 horrible standby time, unusual RF signal drain, battery% drop 4% overnight(8hours)

I understand that bad signal will drain more battery but when I'm at home with perfect signal and wifi I still get pretty bad drain. I disabled wifi and set data to 2G over night and I left with 4% drain after 8 hours. I have no issue with wakelock, no Facebook, don't use snapchat often, super light user. Overall, very disappointed with the A7. I just can not stand the standby time, and I have no idea how to fix it. When I'm in school with bad signal, the battery drain even faster .Come from Iphone 5s which is almost a 3 years old phone(still work like charm, and my moms using it) with literally no battery drain overnight, and it out performance the A7 in battery life by far(with outstanding standby time). Just kindly ask you guys, do you have this kind of issue or is it just me? And any suggestion on fixing this issue?
here is the link for the battery screenshot, I'm a new user so I deleted the http
imgur.com/a/kcRDO

Did you disable the WiFi scanning? This is commonly a major factor in battery drain in Android phone.
Also, try to wipe the cache and dalvik

ttkian said:
Did you disable the WiFi scanning? This is commonly a major factor in battery drain in Android phone.
Also, try to wipe the cache and dalvik
Click to expand...
Click to collapse
No, sir wifi scannings on, is it the major battery hog? I know how to wipe cache but how do you wipe dalvik? Also do I have to disable location?

Badman™ said:
No, sir wifi scannings on, is it the major battery hog? I know how to wipe cache but how do you wipe dalvik? Also do I have to disable location?
Click to expand...
Click to collapse
In my experience, the WiFi scanning should be disable to help battery drain. Go to location, click the three dot on the top right hand side corner, click scanning, then turn off the WiFi scanning and bluetooth scanning.
You have to boot to recovery to wipe cache and dalvik. Turn off the phone. After it's off, press the volume up and hold it while you press the power button. Once the phone vibrates and ZTE logo is showing, release the power button but hold the volume up. You will be presented with recovery option. Choose wipe cache and dalvik, then reboot. Be very careful with this, don't click the wrong choice. I am not responsible if your phone is bricked because you did something wrong here. If you are not familiar with it, DON'T do it.
For location, I don't disable it, but I put it under "battery saving" mode. When I use navigation, I will change it to high accuracy.
Try the first one and the third ones and see what happens after a few days. If you are still not satisfied, wipe the cache and dalvik (DON'T do this if you are not familiar with it)
My personal experience with this phone, I can have 5 to 7 hours SOT depending on what I do.

ttkian said:
In my experience, the WiFi scanning should be disable to help battery drain. Go to location, click the three dot on the top right hand side corner, click scanning, then turn off the WiFi scanning and bluetooth scanning.
You have to boot to recovery to wipe cache and dalvik. Turn off the phone. After it's off, press the volume up and hold it while you press the power button. Once the phone vibrates and ZTE logo is showing, release the power button but hold the volume up. You will be presented with recovery option. Choose wipe cache and dalvik, then reboot. Be very careful with this, don't click the wrong choice. I am not responsible if your phone is bricked because you did something wrong here. If you are not familiar with it, DON'T do it.
For location, I don't disable it, but I put it under "battery saving" mode. When I use navigation, I will change it to high accuracy.
Try the first one and the third ones and see what happens after a few days. If you are still not satisfied, wipe the cache and dalvik (DON'T do this if you are not familiar with it)
My personal experience with this phone, I can have 5 to 7 hours SOT depending on what I do.
Click to expand...
Click to collapse
Good advices bro.
What firmware are you running?

nfsmw_gr said:
Good advices bro.
What firmware are you running?
Click to expand...
Click to collapse
I am running Bad Boyz 7.1.1 v1. 0 with Beast kernel v31.

ttkian said:
In my experience, the WiFi scanning should be disable to help battery drain. Go to location, click the three dot on the top right hand side corner, click scanning, then turn off the WiFi scanning and bluetooth scanning.
You have to boot to recovery to wipe cache and dalvik. Turn off the phone. After it's off, press the volume up and hold it while you press the power button. Once the phone vibrates and ZTE logo is showing, release the power button but hold the volume up. You will be presented with recovery option. Choose wipe cache and dalvik, then reboot. Be very careful with this, don't click the wrong choice. I am not responsible if your phone is bricked because you did something wrong here. If you are not familiar with it, DON'T do it.
For location, I don't disable it, but I put it under "battery saving" mode. When I use navigation, I will change it to high accuracy.
Try the first one and the third ones and see what happens after a few days. If you are still not satisfied, wipe the cache and dalvik (DON'T do this if you are not familiar with it)
My personal experience with this phone, I can have 5 to 7 hours SOT depending on what I do.
Click to expand...
Click to collapse
Thank you good sir, appreciate your advice! I'll try this and see what will happen

ttkian said:
In my experience, the WiFi scanning should be disable to help battery drain. Go to location, click the three dot on the top right hand side corner, click scanning, then turn off the WiFi scanning and bluetooth scanning.
You have to boot to recovery to wipe cache and dalvik. Turn off the phone. After it's off, press the volume up and hold it while you press the power button. Once the phone vibrates and ZTE logo is showing, release the power button but hold the volume up. You will be presented with recovery option. Choose wipe cache and dalvik, then reboot. Be very careful with this, don't click the wrong choice. I am not responsible if your phone is bricked because you did something wrong here. If you are not familiar with it, DON'T do it.
For location, I don't disable it, but I put it under "battery saving" mode. When I use navigation, I will change it to high accuracy.
Try the first one and the third ones and see what happens after a few days. If you are still not satisfied, wipe the cache and dalvik (DON'T do this if you are not familiar with it)
My personal experience with this phone, I can have 5 to 7 hours SOT depending on what I do.
Click to expand...
Click to collapse
The main issue is the RF signal and standby time drain huge percent of battery. Disabling wifi scanning will reduce the drain but only on wifi portion. there is the link of my screenshot I took after disabling wifi scanning and location. Did not fix battery drain on idle issue.
http://imgur.com/a/wRb4G

Badman™ said:
The main issue is the RF signal and standby time drain huge percent of battery. Disabling wifi scanning will reduce the drain but only on wifi portion. there is the link of my screenshot I took after disabling wifi scanning and location. Did not fix battery drain on idle issue.
http://imgur.com/a/wRb4G
Click to expand...
Click to collapse
If I look at the attachment, you use the phone for 13.5 hours since you charged it and you still have 78% of battery left. If that's the case, I don't see a problem with that.
The 41% of RF signal usage is out of your hardware battery usage (75%). So, in reality, it's 30% of usage which represents 6.6% of overall usage (30% x (100-78)%). It seems to me that you had the phone connected to wireless data during this time, not your WiFi? If so, that's normal.

I get 3% battery drain overnight at most.
Don't see any problem with that.
That SoT is with streaming movies etc. YouTube a little gameplay and Facebook.

chaki- said:
I get 3% battery drain overnight at most.
Don't see any problem with that.
That SoT is with streaming movies etc. YouTube a little gameplay and Facebook.
Click to expand...
Click to collapse
That's pretty good. I'm not getting that. I average 5 hours. Will see what the latest 7.1.1 gives me.
I mostly just surf the net and check emails so I should be getting more.

Hi, guys have any of you been able to solve this issue? I'm currently using stock 8.0 and I have just replaced my battery for a new one and still RF signal and Standy are killing my battery (even using airplane mode).
I don't know what to do. I have tried going back to android 7.1.1. and 6.0 with no luck. I have tried several factory resets, I have wiped cache, I just don't know what else to do. My phone's battery is simply dying for no apparent reason.
I will post some Gsam screenshots before my battery dies.

I will post the screenshots later on today. But I can say now there is a major problem with the standby of the phone. So I fully charged the device this morning and battery has dropped by 15% in 4 hours simply from standby (I haven't used the phone).
---------- Post added at 01:15 PM ---------- Previous post was at 12:52 PM ----------
My problems keep getting worse. Now I'm stuck in FTM mode and I can't get out. I have tried every single combination of buttons for way over 10 seconds with no luck.I guess I will have to wait until the baterry dies and hope for the best.

Something went finally the right way! After several attemps I have been able to reboot the phone via the "adb reboot" command while stuck in FTM mode.
Back to figuring out what to do to improve the phone's battery. While stuck in FTM mode the battery went from 80% to 60% (screen was on obviously in FTM mode) - 4 hours aprox.

S5 Battery Problems.

Problem Fixed
The Problem:
Even when the phone is booted up and i charge it up to 100%. It quickly drops down 98/97% in few seconds. Is that normal?
Also when i do restart the phone the charge will be at whatever % but even when unpluged it will go up by few %s and then quickly go down in few seconds.[/I]

Charging with phone closed and you unplug it before opening, when opening, that fase will suck up a few % of battery juice in a little wile because a lot of apps are loading and also some of them will go in wifi or data connection for play store, email searching, flipboard or news loading ecc, ecc. Infact, you can also see that your phone will get hot for a few minutes and that means that cpu is working for this.
Try charging after 5 minutes that your phone is opened and the % of battery is droped and reach 100% .
Stay a couple of minutes charging once reached 100% and then unplug.
Now battery % should drop normally.
Remember that every time you reboot, that will happen again so apps will suck % of battery quickly in this fase.
What you can also do is to make a wipe cache in recovery mode first opening your phone.

joedellosso69 said:
Charging with phone closed and you unplug it, when opening, that fase will suck up a few % of battery juice in a little wile because a lot of apps are loading and also some of them will go in wifi or data connection for play store, email searching, flipboard or news loading ecc, ecc.
Try charging after 5 minutes that your phone is opened and the % of battery is droped and reach 100% .
Stay a couple of minutes charging once reached 100% and then unplug.
Now battery % should drop normally.
Remember that every time you reboot, that will happen again so apps will suck % of battery quickly in this fase.
What you can also do is to make a wipe cache in recovery mode first opening your phone.
Click to expand...
Click to collapse
Even when the phone is booted up and i charge it up to 100%. It quickly drops down 98/97% in few seconds. Is that normal?
Also when i do restart the phone the charge will be at whatever % but even when unpluged it will go up by few %s and then quickly go down in few seconds.

DroidFlow said:
Even when the phone is booted up and i charge it up to 100%. It quickly drops down 98/97% in few seconds. Is that normal?
Also when i do restart the phone the charge will be at whatever % but even when unpluged it will go up by few %s and then quickly go down in few seconds.
Click to expand...
Click to collapse
this is not normal..try wipe cache in recovory mode, reboot and recharge and see what happens.

joedellosso69 said:
this is not normal..try wipe cache in recovory mode, reboot and recharge and see what happens.
Click to expand...
Click to collapse
yeah i will try that. I did do a factory reset. But will try it again. If it does not work, should i just buy a new battery?
i will try to get a video of it happening if it does again.

DroidFlow said:
Even when the phone is booted up and i charge it up to 100%. It quickly drops down 98/97% in few seconds. Is that normal?
Also when i do restart the phone the charge will be at whatever % but even when unpluged it will go up by few %s and then quickly go down in few seconds.
Click to expand...
Click to collapse
this is not normal..try wipe cache in recovery mode then reboot and see what happens.
if doesn't work try a battery calibration doing this:
*#0228# in phone dialer
- that will pop on battery calibration screen
- charge battery at 100% and unplug
- once unpluged wait a couple of minutes and then press quik start botton
- wait that screen returns and you will see that % of battery will be less
- richarge at 100% and then unplug
that should fix

joedellosso69 said:
this is not normal..try wipe cache in recovery mode then reboot and see what happens.
if doesn't work try a battery calibration doing this:
*#0228# in phone dialer
- that will pop on battery calibration screen
- charge battery at 100% and unplug
- once unpluged wait a couple of minutes and then press quik start botton
- wait that screen returns and you will see that % of battery will be less
- richarge at 100%
that should fix
Click to expand...
Click to collapse
Thanks, i will try to do that. But heres the problem, as soon as i unplug in few seconds it drops to 98%
Here is the video and phone in action: https://www.youtube.com/watch?v=UXe5ivnsyIo

DroidFlow said:
yeah i will try that. I did do a factory reset. But will try it again. If it does not work, should i just buy a new battery?
i will try to get a video of it happening if it does again.
Click to expand...
Click to collapse
before bying a new battery, try battery calibration and then if you can try going in samsung assistence for a quik battery test that will tell you if battery is to be replaced.
I recommend the original battery and not cheap chines ones...there Life is longer.

joedellosso69 said:
before bying a new battery, try battery calibration and then if you can try going in samsung assistence for a quik battery test that will tell you if battery is to be replaced.
I recommend the original battery and not cheap chines ones...there Life is longer.
Click to expand...
Click to collapse
Oh. I did the calibration. after the screen returned. It went from 96% to 86%. Charging it to 100% again. Hopefully it works. Thanks for your help. Where do you recommend buying batteries from?

DroidFlow said:
Oh. I did the calibration. after the screen returned. It went from 96% to 86%. Charging it to 100% again. Hopefully it works. Thanks for your help. Where do you recommend buying batteries from?
Click to expand...
Click to collapse
Samsung assistence store, stores having original battery, even in internet like amazon or others like this...

joedellosso69 said:
Samsung assistence store, stores having original battery, even in internet like amazon or others like this...
Click to expand...
Click to collapse
ok. it looks like it didnt work. its doing the same problem again. Im starting to get the feeling the its the battery.
Such saw my phone jump from 95% to 100%. wtf