Hi all,
I've run into something strange with my Nook's battery life. I have a 16Gb tablet that currently is running the 4/20 release of SlimBean with the v13.1 NOF kernel (mentioned for completeness, I don't think this is a ROM or kernel issue). The battery life has gotten so bad as to be virtually unusable. Here's what happens...
The battery indicator shows nearly full -- 75%~85%, then the digitizer gets wonky, and I get a hard shutdown (no warning dialog, just a complete power-down). If I turn the tablet on now, Cyanoboot shows a low battery level (mid-teens, normally), but the tablet proceeds to boot. NOW, the battery indicator reports the same as Cyanoboot. Within a few minutes, I get a normal low-battery warning, and a polite shutdown. If I start the tablet again, both Cyanoboot and the battery indicator show nearly full again, but I get only a few minutes of use before another shutdown.
I say I don't think its a ROM/kernel issue because I've seen this same behavior on my tablet using several different ROMs and kernels - including SlimBean, SG7, and Pac-Man. BetterBatteryStats isn't showing me anything earth-shatteringly strange, but I'm no battery expert.
Any ideas on what's happening here, and what I can do to fix it?
spcagigas said:
Hi all,
I've run into something strange with my Nook's battery life. I have a 16Gb tablet that currently is running the 4/20 release of SlimBean with the v13.1 NOF kernel (mentioned for completeness, I don't think this is a ROM or kernel issue). The battery life has gotten so bad as to be virtually unusable. Here's what happens...
The battery indicator shows nearly full -- 75%~85%, then the digitizer gets wonky, and I get a hard shutdown (no warning dialog, just a complete power-down). If I turn the tablet on now, Cyanoboot shows a low battery level (mid-teens, normally), but the tablet proceeds to boot. NOW, the battery indicator reports the same as Cyanoboot. Within a few minutes, I get a normal low-battery warning, and a polite shutdown. If I start the tablet again, both Cyanoboot and the battery indicator show nearly full again, but I get only a few minutes of use before another shutdown.
I say I don't think its a ROM/kernel issue because I've seen this same behavior on my tablet using several different ROMs and kernels - including SlimBean, SG7, and Pac-Man. BetterBatteryStats isn't showing me anything earth-shatteringly strange, but I'm no battery expert.
Any ideas on what's happening here, and what I can do to fix it?
Click to expand...
Click to collapse
Some ROMs have weird battery issues. Make a SDC card of CM10 and see if the battery is still wonky. You can use this.
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
datallboy said:
Some ROMs have weird battery issues. Make a SDC card of CM10 and see if the battery is still wonky. You can use this.
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Click to expand...
Click to collapse
Thanks. I'll try that this evening and report back. On the upside, the way my battery is acting now, it shouldn't take too long to see if this fixes the problem...
spcagigas said:
Thanks. I'll try that this evening and report back. On the upside, the way my battery is acting now, it shouldn't take too long to see if this fixes the problem...
Click to expand...
Click to collapse
OK... Been running with succulents's CM10 for a few days now, and I'm not seeing this happen as frequently, but it still happens occasionally. I'm going to wipe and reinstall SlimBean tonight and see if the problem returns...
Related
I'm running Cyanogenmod 7 20120703-TEAM-B-acclaim on my 16GB Nook Tablet.
Occasionally I'll charge my device, power it down and put it away for maybe a week or so. When I try to turn it on again the battery will be completely dead. It seems that either the device is never actually shutting down completely and just draining the battery. The screen looks like it's off and there's no signs that it could still be powered on.
Does anyone else have this issue? Seems to only occur right after I charge it up to 100%. Needless to say it's pretty annoying if I expect my Nook to be fully charged, take it out with me somewhere only to find that it's completely dead and I have no charger with me.
chodashi said:
I'm running Cyanogenmod 7 20120703-TEAM-B-acclaim on my 16GB Nook Tablet.
Occasionally I'll charge my device, power it down and put it away for maybe a week or so. When I try to turn it on again the battery will be completely dead. It seems that either the device is never actually shutting down completely and just draining the battery. The screen looks like it's off and there's no signs that it could still be powered on.
Does anyone else have this issue? Seems to only occur right after I charge it up to 100%. Needless to say it's pretty annoying if I expect my Nook to be fully charged, take it out with me somewhere only to find that it's completely dead and I have no charger with me.
Click to expand...
Click to collapse
I have noticed it too.. and sometimes the battery status is not accurate. It shows that it still has 50% but it drains of quickly.
After searching through the bug reporting thread for CM7 it does seem that others are seeing this same issue. Essentially after the device has been charged to 100% if you unplug the charger and then attempt to power off the device it will seem as though it has shut down but if you look at the screen in low light you will notice that it is still on but is all black. This is very bad since its easy to think that the Nook is off when it is actually still on and running down the battery.
I think I will try rebooting the device first before shutting it down after charging to see if I can avoid this issue. Maybe I'll give CM9 a shot.
chodashi said:
... if you look at the screen in low light you will notice that it is still on but is all black.
Click to expand...
Click to collapse
Well...Son of a gun!
I've seen that, too. On my Nook (CM7) and my Droid X (Stock-rooted). I've had the Droid so long, I don't know when it started. I guess I'm just in the habit of unplugging them both, checking for messages, and putting them back to sleep.
Hi all,
recently I flashed Ressurection Remix v3.8 with Siyah kernel 3.0.15
it worked pretty well but from time to time my phone would freeze up, get really warm and reboot (or not, and possibility to turn it on is to take the battery out and turn it back on)
after the phone is switched back on, the battery goes to 1% or 3 % and switches off quite quickly.
when I plug it in to charge it almost immediately goes back to the original battery charge
does anyone recognize this problem?
or if not any ideas whether it is an issue with the rom, kernel, radio or something else?
many thanks
supermooshman said:
Hi all,
recently I flashed Ressurection Remix v3.8 with Siyah kernel 3.0.15
it worked pretty well but from time to time my phone would freeze up, get really warm and reboot (or not, and possibility to turn it on is to take the battery out and turn it back on)
after the phone is switched back on, the battery goes to 1% or 3 % and switches off quite quickly.
when I plug it in to charge it almost immediately goes back to the original battery charge
does anyone recognize this problem?
or if not any ideas whether it is an issue with the rom, kernel, radio or something else?
many thanks
Click to expand...
Click to collapse
What is the real version of your Siyah kernel? because Siyah 3.0.x can never boot RR 3.8!
Jokesy said:
What is the real version of your Siyah kernel? because Siyah 3.0.x can never boot RR 3.8!
Click to expand...
Click to collapse
my bad, it's SiyahKernel S2-v4.1.5
supermooshman said:
my bad, it's SiyahKernel S2-v4.1.5
Click to expand...
Click to collapse
I recognise your problems.
1. "The phone will freeze up" may be caused by some user unstable settings on the kernel, or the general instability of your ROM + the kernel combo, or maybe you are using a conflicting script.
- Next time your phone freeze up, just hold down the power button for about 8-10 seconds instead of removing the battery.
- to solve this problem,
a. Reset all your kernel settings to default
b. remove any other scripts that might be running on your phone.
c. try to track what activity normally trigger this freeze up
d. If the problem persists, you can try another kernel.
2. "after the phone is switched back on, the battery goes to 1% or 3 % and switches off quite quickly". this one may be caused by the fact that your fuel gauge chip is not yet settled.
- to solve this one,
a. charge you phone,
b. Install and run Extweaks, under misc, select Reset Fuel Gauge chip.
c. Exit extweaks and leave your phone untouched for about 1hr to allow it to settle down.
Thanks, I'll give it a try!
Sent from my GT-I9100 using xda app-developers app
Jokesy said:
I recognise your problems.
1. "The phone will freeze up" may be caused by some user unstable settings on the kernel, or the general instability of your ROM + the kernel combo, or maybe you are using a conflicting script.
- Next time your phone freeze up, just hold down the power button for about 8-10 seconds instead of removing the battery.
- to solve this problem,
a. Reset all your kernel settings to default
b. remove any other scripts that might be running on your phone.
c. try to track what activity normally trigger this freeze up
d. If the problem persists, you can try another kernel.
2. "after the phone is switched back on, the battery goes to 1% or 3 % and switches off quite quickly". this one may be caused by the fact that your fuel gauge chip is not yet settled.
- to solve this one,
a. charge you phone,
b. Install and run Extweaks, under misc, select Reset Fuel Gauge chip.
c. Exit extweaks and leave your phone untouched for about 1hr to allow it to settle down.
Click to expand...
Click to collapse
hmmm didn't quite work:
1.
- reset the kernel
- removed all init.d scripts
- no idea how to do that :-s
- going to try this now (any suggestions by any chance?)
2.
- couldn't use extweaks as my phone would switch off before I could open it
fun trivia... my battery level went to -1 when I switched my phone back on... darnit
supermooshman said:
hmmm didn't quite work:
2.
- couldn't use extweaks as my phone would switch off before I could open it
fun trivia... my battery level went to -1 when I switched my phone back on... darnit
Click to expand...
Click to collapse
Did your battery run out of charge?
how many hours/mins can your phone work on battery when idle and when used?
You can try out a friend's battery and test if your problem still persists.
Jokesy said:
Did your battery run out of charge?
how many hours/mins can your phone work on battery when idle and when used?
You can try out a friend's battery and test if your problem still persists.
Click to expand...
Click to collapse
I don't think so as it happens at all different kinds of percentages, and when the phone restarts its mostly between 1% and 3%
on a single full charge when idle, the battery goes about 11 hrs
unfortunately none of my friends have a samsung - the battery of their iphone is not removable (... ok, lets not go there)
I did notice when it does happens, I am almost always using my phone (playing music, surfing, facebook etc), there is not really a particular app that is running when it happens (well maybe in the background)
also, about 5 seconds before it switches off my screen flickers, not sure if that is related (but I'm pretty sure it is)
thanks
My phone has been doing the exact same thing, screen flickers a few seconds then switches off, then the battery level has fallen ridiculously on reboot. Did you ever get to the bottom of this?
Sent from my GT-I9100 using xda app-developers app
I bought a new battery over the weekend, until now, the days and still nothing weird has happened
Maybe as jokesy mentioned, try a battery of a friend or buy a new one (they're not that expensive)
Good luck!
Sent from my GT-I9100 using xda app-developers app
Hi. I have a very frustrating issue I hope someone can help with.
Over the last 3 days or so, my s2 has started to randomly shut itself down. It only appears to happen when I'm using an app, nothing specific, it can happen anytime.
The battery level has been anything from around 75% to 30%.
Sometimes when I turn it back on, the battery shows I am at 1 or 2 %, making me think it might be some kind of calibration problem, but I've tried the suggested method to no avail. I've also completely fresh installed the Rom I was on (neat Rom) and tried another (disaster Rom) but the problem remains.
Can anyone suggest what could be causing the random shut downs?
Thank you
Karf
Are you undervolting/ under clocking this can cause a sod
Hi. Nothing like that, just used neat Rom or disaster Rom as they come.
sent from my Westcrip powered S2
Your phone(battery) has insane gauge chip search for this it answer in your question(it's only for battery)
Happy new year
Paulius
Hi, thanks for the reply. I'm not sure my issue is to do with the guage chip directly, as my phone will switch itself off at any battery level. The issue designed in the other thread its having something like 56% and then having a much lower value after an intended reboot.
Shutdown it's called sleep of death( scary name) but it not death it's just sleeping forever... it problem with your kernel and battery problem is insane gauge chip...
Happy new year
Paulius
I've just charged to full charge, unplugged - and within 2 minutes, the phone froze, could not do anything - so i pressed the power button until it went off, and it booted back up again without me doing anything - when it booted, it showed i had 2% battery. Then it did the same thing, froze, i had to reboot - then it showed 37% battery.........no idea what's going on apart from maybe a faulty battery...
Buy new battery. It was here on the forum a few times.
Yes. When phone hot(sometimes not) it take battery about 50-60%(I don't know exactly) but sometimes it add battery...
If you flash siyah kernel with stweaks(5 version) you can reset it but chip do funny thing even you reset...
Happy new year
Paulius
try Battery caliberation app ...
if it doesnt work buy a new battery
What are you talking about ? It's not battery Fault it's Insane Gauge Chip.... And Battery Calibration not helping...
I decided to go the whole hog and go back to a stock unrooted ICS, after wiping everything, then CFRoot - then reinstalled Neatrom light - currently restoring apps via Titanium - fingers crossed...
I think you don't have anymore BSOD But if you have flash Syiah kernel
Try new kernel and reset fuel gage
Try installing a new kernel like siyah or dorimanx and then reset your battery log this should resolve your problem if not buy a new battery.
karfeef said:
Hi. I have a very frustrating issue I hope someone can help with.
Over the last 3 days or so, my s2 has started to randomly shut itself down. It only appears to happen when I'm using an app, nothing specific, it can happen anytime.
The battery level has been anything from around 75% to 30%.
Sometimes when I turn it back on, the battery shows I am at 1 or 2 %, making me think it might be some kind of calibration problem, but I've tried the suggested method to no avail. I've also completely fresh installed the Rom I was on (neat Rom) and tried another (disaster Rom) but the problem remains.
Can anyone suggest what could be causing the random shut downs?
Thank you
Karf
Click to expand...
Click to collapse
I think I have a very similar issue. The randomly reboots happens several times a day, it does not happen though when charging (never). By now I'm on jb leak and still have the issue. When it shuts down, the sreen dims a bit and then it's gone, the weird thing is that often I have to pull the battery or charge the phone before reboot is possible, the battery shows different values after rebooting, sometimes close to what was before (especially when rebooting on charger), and sometimes way off the values before. I came initially from slimrom with siyah or dorimanx kernel, I really hoped jb leak would help (also tried different kernels), but it didn't. It also seems to me that it happens more often with the sd card (32gb) and without the phone seems more stable, but still it happens from tme to time. Once the screen dim (only one or two steps) and shut down even happend when in CWM recovery, is it maybe hardware related? It's very hard to find the source of the problem, anybody else experience similar issues? By the way the shutdown I have is not a proper shut down, the phone doesn't show the message "is shutting down".
I've completely wiped, used Odin to go back to ics stock, installed cfroot, then installed neatrom light. Had the same issue, so I've installed siyah, and used stweaks to reset the battery fuel gauge. I've only been off charge for 10 mins so far, but normally it would have shut down by now, so here's hoping...
sent from my Westcrip powered S2
Update - battery was at 89%, and the phone shut down, when rebooted, it showed 28%, then when plugging in while it was shut down, the battery icon showed about 50%. Like a previous reply, it never happens on charge, so it does appear that the battery is knackered, time to go shopping I guess :-\
Sent from my GT-I9100
karfeef said:
Update - battery was at 89%, and the phone shut down, when rebooted, it showed 28%, then when plugging in while it was shut down, the battery icon showed about 50%. Like a previous reply, it never happens on charge, so it does appear that the battery is knackered, time to go shopping I guess :-\
Sent from my GT-I9100
Click to expand...
Click to collapse
I had the same problem - SOD several times a day. I change the batery with a fresh new samsung 2000 mA one.
Unfortunatelly SOD came back, but I found a trick: turn off WiFi. Use it only manually.
For the past 3 months I succeded to have 0 SOD's.
I know that manual WiFi is a setback but it works with those experiencing SOD.
Hope it will be usefull.
I am currently running and have been for several weeks the 4.3 Sophisticated ROM. I was on v2.5 when this started but was preparing to update to v3.0 when the problem below arose.
My phone just developed a strange problem but I don't think it's related to this ROM. I just pulled it off the charger to install the 3.0 update and there is a strange behavior with the notification bar. shortly after startup the notification icon starts flickering rapidly regardless of the icon there. After all notifications are cleared the GPS icon is flickering, when I pull it down something tries to show up but disappears before it can even be displayed. The battery is also draining quite fast and the phone is hot. I initially ignored it and proceeded to install the 3.0 update using my usual method of wiping cache/dalvik/system x3. After restarting the issue was still present. I used a task manager the close all apps that could be closed but it changed nothing. When trying to open the battery usage panel to see what is draining the battery it hangs then FCs. Since this first happened when pulling it off the charger, I plugged it back in. Suddenly the issue was resolved. Very very odd, I have never seen this before.
So it does fine while the phone is plugged in and charging or fully charged, but as soon as you take it off the charger the phone starts acting up? First thing I would do is pull the battery to see if there are any indications of the battery swelling or bulging. That is a sure sign of a battery that is failing. Pull it and do a quick visual and report back.
On another note. My sd card wend bad on my note 2 and she'd blow through a battery in a few short hours, plus it would get very hot. You are experiencing something different, but I thought I'd share it with you anyway. I replaced the sdcard and all was well.
Good luck.☻
I had the same problem with the same ROM and I prefered to revert to version 4.1.2 with Odin.
One of my problems it was the high consumption with Multimedia process that show in the battery usage panel.
Awaiting answer to this problem.
Burguitox said:
I had the same problem with the same ROM and I prefered to revert to version 4.1.2 with Odin.
One of my problems it was the high consumption with Multimedia process that show in the battery usage panel.
Awaiting answer to this problem.
Click to expand...
Click to collapse
I was wrong about plugging it back in solving the issue. I had forgotten that I had GPS and Sync toggled off.
I'm not really sure what the cause was but I took the following 2 actions which seems to have resolved the issue
1. Re-flashed 4.3 firmware.
2. I had recently disabled google Wi-Fi location as a reported cause of battery drain (kind of ironic). I re-enabled this because it appeared to GPS causing the problem.
Looking good so far.
Ok I've had the Moto Z for a while and its a great phone. Or it was until a few weeks ago. In the space of a couple of weeks a few official updates were sent to my phone and thinking nothing of it I updated as requested. The last update has seriously messed the phone up.
Problems since the update:-
- Battery drain now has the phone running out in about 10 hours. This problem seems to be intermittent, the majority of the time it happens and drains the phone quickly but not all of the time and usually its Android OS using between 25-50%. Also safe mode has no effect on the problem.
- Phone speaker stops working. Start the phone up and its working, but after a undetermined amount of time (no more than a hour or so) the speaker no longer works. If I get a call I have to turn on speaker phone to be able to hear anyone. Reset the phone and it works normally, only to happen again soon after.
- Phone charging stops working. Again start the phone and plug in the charger and it works fine. But after its charged, again after a undetermined amount of time, charge no longer works. Plug the charger in and the phone indicates its charging with the little light coming on at the top. But nothing else on the phone indicates its charging and the battery continues to drain. Reset the phone and suddenly it chargers normally. Same thing then happens again given time.
What I've tried to do about it:-
- I've tried running in safe mode, which makes no difference
- I've tried a full reset, which makes no difference
- I even unlocked the bootloader and installed a custom OS (Lineage). Thinking that obviously this will wipe out the new update from Lenovo and the phone would have to work properly again. But no, nothing changes, somehow Lenovo have done something beneath the OS that's causing these problems.
The question:-
Does anyone have any idea what could be causing this or have you at least seen these issues before?
I fail to gasp what is the purpose of the topic and I don't see a question.... If you're looking for compassion, I think the internet is the wrong place.
If you're sure that the problems is the updates, downgrade to the latest version that worked well for you. Since you've already unlocked the bootloader, try any of the variety of roms available here to verify you don't have a hardware problem.
apocalypse_bg said:
I fail to gasp what is the purpose of the topic and I don't see a question.... If you're looking for compassion, I think the internet is the wrong place.
Click to expand...
Click to collapse
The point of my post is obvious, I've got a issue with my phone and want to know if anyone has seen this issue with the Moto Z before and if they have any idea what may fix it. The question is right there near the end:
"Does anyone have any idea what could be causing this or have you at least seen these issues before?"
Click to expand...
Click to collapse
apocalypse_bg said:
If you're sure that the problems is the updates, downgrade to the latest version that worked well for you. Since you've already unlocked the bootloader, try any of the variety of roms available here to verify you don't have a hardware problem.
Click to expand...
Click to collapse
I've tried a different ROM:
- I even unlocked the bootloader and installed a custom OS (Lineage).
Click to expand...
Click to collapse
Honestly don't know how my post was unclear at all, but I've gone and tried to make it even more clear with a quick edit, hope that helps.
I have exactly the same problem. For me it occurred after updating to nougat. So fare I tried nearly everything. Disabling nearly everything to the bare minimum, custom ROMs, resetting, trying to flash only parts of the Android 6 firmware (modem, Bluetooth, DSP) since a complete downgrade is not possible, using all kinds of battery tools with a rooted device, using custom kernels... I always ended up with a constant battery drain of 3 to 8 percent per hour no matter what I did. Same in flight modus. Since under Android 6 the device didn't show this behavior I think that the problem must be somewhere in the firmware beneath the OS level. An the cruel thing is that sometimes without a reason for maybe an hour or two my moto z doesn't drain an works fine so that I do not believe in a hardware problem.
Thanks for the post. Yeah it seems like something has been changed underneath the OS. I know that sometimes memory config gets changed with newer Android operating systems (at least I think so?), but could that cause all these problems?
BTW, do you have all three of the problems I mentioned? Battery drain, sound stops working and charging stops working?
Since in this condition the Moto z is not really usable for me I switched back to my old phone and I am not using it that much as a daily device, I cannot really tell about sound or charging problems. So far I did not notice those problems.
DonnieDio said:
Problems since the update:-
- Battery drain now has the phone running out in about 10 hours. This problem seems to be intermittent, the majority of the time it happens and drains the phone quickly but not all of the time and usually its Android OS using between 25-50%. Also safe mode has no effect on the problem.
Click to expand...
Click to collapse
I feel like battery life is a bit worse than with M, but I didn't experience anything as bad as you did. I switched to a custom ROM after updating to 7.0.1
DonnieDio said:
- Phone speaker stops working. Start the phone up and its working, but after a undetermined amount of time (no more than a hour or so) the speaker no longer works. If I get a call I have to turn on speaker phone to be able to hear anyone. Reset the phone and it works normally, only to happen again soon after.
- Phone charging stops working. Again start the phone and plug in the charger and it works fine. But after its charged, again after a undetermined amount of time, charge no longer works. Plug the charger in and the phone indicates its charging with the little light coming on at the top. But nothing else on the phone indicates its charging and the battery continues to drain. Reset the phone and suddenly it chargers normally. Same thing then happens again given time.
Click to expand...
Click to collapse
None of the above ever happended to me
StarStorm said:
I feel like battery life is a bit worse than with M, but I didn't experience anything as bad as you did. I switched to a custom ROM after updating to 7.0.1
None of the above ever happended to me
Click to expand...
Click to collapse
I've never seen anything like it before. Its so random as well. I mean yesterday I rebooted and then charged the phone before I left for Football at 4pm. At about 11pm that night I heard the battery low sound (45% of the battery had be used by Android OS..). First thing I thought of was that usually the phone wouldn't still be making sounds by now. Since as I said earlier usually the speaker stops working along with charging within a hour or so of a reboot and this had been over 7 hours without a reboot. So I tried plugging it in and it started to charge. But then when I woke up this morning again the sound was disabled and it won't charge, it just took longer for the problem to occur this time..
How can we stop asking to update to this patch?
I has already disabled this on the developer preferences but still asking every 10 minutes
Any suggest please
Mine even worst. Battery drain fast and mobile away very warm. It suddenly reboot and shown low battery. Battery drain from 50 to 3 percent in a second! Have you guy come across this?
doug107hk said:
Mine even worst. Battery drain fast and mobile away very warm. It suddenly reboot and shown low battery. Battery drain from 50 to 3 percent in a second! Have you guy come across this?
Click to expand...
Click to collapse
Yep I've also had that as part of my problem, though it had only happened a few times over the course of the month so I forgot about it with all the other problems I mentioned going on.
Basically my phone would be sitting on, say 40%, and after a reboot it would start up in the single digits.
I recently tried changing to a custom kernel to see if maybe that was causing the problem (I'd already tried changing OS). But all the problems are still there using the new kernel. Think my next step should be to try to go back to a 7.0 Android version. Are there any custom Android ROMs using 7.0?
It is said that the Motorola Manager can rescuer lost data even if the data has been covered on phone , is it true ?
Just curious what came of this. My Z, unrooted, has started running crazy hot and the battery life is not good. 6-10 hours. When I connect it to my Anker PowerDrive 2 in the car, the battery actually discharges faster or I get the slow charge warning.
Hi I have exactly the same problems as the op and tried resetting to no avail.Its driving me nuts.
Short update about the massive battery drain problem: like I wrote above, in the past weeks I tried everything from custom kernels to custom roms, resetting, deleting and so on. Nothing helped. So I went back to stock and didn't use the phone the last weeks. Today I read in an other thread about bluetooth problems that a fix for the not working bluetooth was to activate flight mode, restart the phone and deactivate flight mode. So I activated flight mode, pressed the power button for 10 seconds or so until the phone restarted an deactivated flight mode. And now the absolute strangest thing happened: for the last 5 hours the phone lost 0% battery in standby with wifi and lte on. Since I did all the mentioned things above without any effect I do not understand this at all but right now I think that this could be a (temporally) fix also for the battery drain problem.