Develop Bugs

Battery Problems (After Bricking??)

Alright so I've been doing research online this week and haven't been able to fix it so I'm coming to you guys. I'll give you a little background to hopefully help speed up this process.
So about 3 weeks ago I rooted my Sprint LG Optimus G after having it for almost a year to get some better performance and battery life out of it. After getting it all setup, I noticed a huge difference and was even able to watch the movie Flight and two episodes of Family Guy off Netflix and my battery still lasted 9 hours that day.
Well last weekend after uninstalling some Google apps I soft bricked my phone. Thanks to the help of sawdey21 on the IRC I was able to get it back up and running with LGNPST. After getting it running, I switched launchers (from Holo to Nova) and also unlocked mine phone via FreeGee with TWRP. Since then, my battery life has been terrible. To give you a reference it took my phone 8 hours to fully charge last night while it was off (although since I unlocked it I have a new charging animation and after a few seconds of the animation, instead of shutting the screen off like it use to it now just goes to a black screen but is still on as you can see the brightness. It never shuts off). After unplugging it, an hourly later I was down almost 15% after just listening to music and after 4.5 hrs its at 30% and I just plugged it in. Today I have done nothing but listen to music and just period check/browse my phone.
Is it possible that the bricking messed up my battery? Or the unlock? I switched back to the previous Holo launcher I was using before and it made no difference. I've also unistalled several apps I downloaded since the bricking I thought could be causing it.
Has anyone ran into this or could help? My next step is to boot back into Download Mode and try LGNPST again. I would post pics of Battery Settings, WakeLocker and BetterBatteryStats but I can't since I'm a new comer.
Thanks!

Different roms use a different amount of power...
Sent from my GT-P3100 using xda app-developers app

xSTUDDSx said:
Alright so I've been doing research online this week and haven't been able to fix it so I'm coming to you guys. I'll give you a little background to hopefully help speed up this process.
So about 3 weeks ago I rooted my Sprint LG Optimus G after having it for almost a year to get some better performance and battery life out of it. After getting it all setup, I noticed a huge difference and was even able to watch the movie Flight and two episodes of Family Guy off Netflix and my battery still lasted 9 hours that day.
Well last weekend after uninstalling some Google apps I soft bricked my phone. Thanks to the help of sawdey21 on the IRC I was able to get it back up and running with LGNPST. After getting it running, I switched launchers (from Holo to Nova) and also unlocked mine phone via FreeGee with TWRP. Since then, my battery life has been terrible. To give you a reference it took my phone 8 hours to fully charge last night while it was off (although since I unlocked it I have a new charging animation and after a few seconds of the animation, instead of shutting the screen off like it use to it now just goes to a black screen but is still on as you can see the brightness. It never shuts off). After unplugging it, an hourly later I was down almost 15% after just listening to music and after 4.5 hrs its at 30% and I just plugged it in. Today I have done nothing but listen to music and just period check/browse my phone.
Is it possible that the bricking messed up my battery? Or the unlock? I switched back to the previous Holo launcher I was using before and it made no difference. I've also unistalled several apps I downloaded since the bricking I thought could be causing it.
Has anyone ran into this or could help? My next step is to boot back into Download Mode and try LGNPST again. I would post pics of Battery Settings, WakeLocker and BetterBatteryStats but I can't since I'm a new comer.
Thanks!
Click to expand...
Click to collapse
I'm not 100% sure but it is possible the bricking messed with the battery. LGNPSTing back to stock could have affected it, anytime you flash a new rom it takes a couple of days to "settle in" but you said last weekend so it should be settled by now.
But from your info, it may be the way you are charging it. There is a common misconception that every so often you are supposed to let your battery drain fully and then charge to 100%. This is only true for nickel based batteries, ours is lithium so this is in fact quite detrimental. Lithium batteries are built to be charged often and you should never let it dip too far into the red. Doing so decreases the life and performance of your battery significantly. 5% is as low as I'll let my battery dip before charging and even that is pushing it imo. There is an app in the play store called battery calibration that actually tells you to do this, but like I said, it's only useful for nickel based rechargeable batteries. Also this same app's function is deleting the batterystats.bin file in order to "recalibrate" the battery. This is also completely false as that file has nothing to do with how well your battery performs.
I wouldn't turn the phone off to charge, just charge it while it's still on so the screen actually shuts off. Checking your wakelocks and using greenify on power hungry apps will go a long way. I also turn my capacitive buttons off because I don't need to see them to know left, right, center and what they do. And if I'm not using it, it is always off, sync, gps, brightness when inside, etc. But as I said, it may have been the way you were charging it, it might not affect the battery for months, then all of a sudden your battery doesn't perform as well because it's dying due to improper charging techniques. And when you LGNPSTed back to stock, your system tries to start fresh which is why it may have happened immediately afterwards.
I hope some of this helps you - if using greenify doesnt show improvement you may want to buy a bigger capacity battery and start fresh. Installing the new battery is tricky however, there are youtube videos on how to do it, but it may not be for everyone.
Good luck and I'm sorry if I assumed too much or misread your info!
EDIT: You may also want to try flashing a different stock kernel(I use Viper1.1, my signature has a link to the thread) and using trickstermod to undervolt the cpu. The improvement is minimal but every little bit helps. On average I get a full 24 hours in between charges and usually charge once it hits 10-15%. And it only takes about 60-120 minutes to fully charge.
However the lgog is also very fickle, what works for one may not work on another, even if it's the exact same model. Many people have reported the same security bootloop soft brick after deleting google apps for instance, but I deleted(not frozen or disabled) google apps just fine. The only ones I have on my phone are play store and google search and I'm still on stock zvc.

HPTesta,
Appreciate the response and all the info. To clarify a little more, I've never installed a custom ROM. Just been doing launchers from the Play Store besides having to do the LGNPST. As far as Apps I've been using greenify since I rooted 3 weeks ago as well as CPU Tuner which had both been doing great for me before this.
As far as charging goes, I generally never run my phone compleley dead. I usually charge when its getting low but last night I ran it complete lay dead to use Wake locker (read in the app store to drain bat, recharge full, and use after a couple hrs.
One thing I did find weird is that I don't remember how much battery I had when I bricked it but after doing the LGNPST I had 0 (Don't know if that's normal).
Also, never used the Battery Calibration app.

And based off what your saying would you not recommend doing LGNPOST again?

xSTUDDSx said:
HPTesta,
Appreciate the response and all the info. To clarify a little more, I've never installed a custom ROM. Just been doing launchers from the Play Store besides having to do the LGNPST. As far as Apps I've been using greenify since I rooted 3 weeks ago as well as CPU Tuner which had both been doing great for me before this.
As far as charging goes, I generally never run my phone compleley dead. I usually charge when its getting low but last night I ran it complete lay dead to use Wake locker (read in the app store to drain bat, recharge full, and use after a couple hrs.
One thing I did find weird is that I don't remember how much battery I had when I bricked it but after doing the LGNPST I had 0 (Don't know if that's normal).
Also, never used the Battery Calibration app.
Click to expand...
Click to collapse
Ok well it seems like you follow good battery techniques. Maybe try LGNPSTing back to a full stock zvc(or zvb and then updating to zvc) and charge it to 100%(let it sit at 100% while still charging for 15 mintues or so) before rerooting and unlocking. I would probably also copy your internal to your pc and wipe everything in recovery before doing LGNPST just to make sure it is a completely clean slate. I added an edit in my post above as well.
I had a strange issue a few weeks back where I tried overclocking my cpu with AK kernel - my battery was at 99%. My phone shut off and wouldn't come back on, just had a red blinking light. I later found out it was an issue with AK. I charged it for a few minutes and luckily was able to get into TWRP. The strange part was that when I did get into TWRP my battery read 0%, I did a full wipe and restored my backup, then my battery read 99% in TWRP. It's a different issue from yours but makes me think that it's possible that your softbrick and LGNPSTing affected it somehow.
---------- Post added at 03:52 PM ---------- Previous post was at 03:49 PM ----------
xSTUDDSx said:
And based off what your saying would you not recommend doing LGNPOST again?
Click to expand...
Click to collapse
I honestly have not had or heard of any issues with LGNPST and battery performance. Anytime Ive had to use LGNPST with a full stock .bin, it essentially set my phone back to factory condition, battery performance included. However since this all happened when you did this, maybe try flashing another rom first, even a stock based one and leave LGNPST as a last resort. Just make sure you read the instructions for whatever rom you decide to test and always do a full wipe(data, cache, dalvik and system) before flashing.
EDIT: Sorry if it seems like I gave you conflicting info, if it was me I would probably be weary of using LGNPST again, personally. But if I tried flashing other things, different recoveries, roms and still had the same issue, maybe it was just a slightly messed up LGNPST flash and would try it again as a last resort.

Forgive my ignorance but I've never actually booted into twrp recovery. Its volume up and power but where do you go from their to wipe?

xSTUDDSx said:
Forgive my ignorance but I've never actually booted into twrp recovery. Its volume up and power but where do you go from their to wipe?
Click to expand...
Click to collapse
After holding volume up + power, you then will hit volume down twice and power again. Once in TWRP it is very easy, there is an install button, wipe button, etc. Hit the backup button, pick all available options and then do a backup and reboot into your OS. From there, download a rom(optimus DE is a great stock rom) to your internal and you will probably need gapps as well(depends on rom but almost all of them need gapps or you wont even have the play store - just read the install instructions of the rom). Go back into recovery, This is under the advanced wipe button in the wipe menu - wipe everything except internal storage(if you wipe internal you will lose your backup, pictures, music, etc) and then go to install, pick the rom.zip and flash that, then pick the gapps zip and flash that as well.
Also keep in mind that if you flash an AOSP or CM based rom, the file system will be different. Our internal storage is /data/media but for AOSP based it is /data/media/0. So say for instance you make a backup in TWRP of your stock then flash an AOSP rom, it will look as if your internal is gone as well as your backup. You will just have to use a root file explorer to copy the /data/media/TWRP folder to /data/media/0/TWRP and then you will be able to restore your backup from TWRP.
If you are just going to try LGNPST again then when you get into TWRP pick everything including internal and turn the phone off and put the phone into dl mode(you know what you are doing from there).
One final note, if you are using current FreeGee to unlock then you are most likely using the updated TWRP. Some people have had SEVERE issues with it, for others it works just fine. You need it to install any rom based on Android 4.4 but I personally use TWRP 2.5.0.0 which will flash stock to Android 4.3 roms just fine and it is rock solid stable. So unless you are planning on installing a kit kat rom, I would first download the TWRP 2.5.0.0 zip found here to your internal, go into twrp, pick the install button, find the .zip file and install that, then go to reboot in TWRP's main menu and choose recovery instead of system. TWRP should now read 2.5.0.0.
Sorry for the books I'm writing here but I think it's always best to be thorough!! And I haven't slept in about 30 hours so I am a bit scatter brained.

Phone shutting off while data enabled

My friend is owning Xperia SL for a long time, it is rooted and has custom rom. Everything was going fine for about an year.
But since 3-4 days, the phone is shutting down whenever "mobile data (internet)" is enabled. It stays for few seconds, or minutes then the phone goes off. It doesn't even show the "Power Off" message, the screen simply fades away and the phone is off. And the battery percentage drops to 1%.
It is 100% sure the phone would shutdown if data is enabled. After much research, I also found that phone SOMETIMES shuts off if CPU usage is high (meaning you run some high-end apps or gaming). I have already reset the device, formatted system, cache, dalvik cache. Even I switched between JellyBean/Kitkat roms, but the problem still exists.
My friend is very desperate. What can I do to fix that phone (I am his expert )? I tried to fetch a logcat with "Catlog" when the phone goes off. It's attached.

Try to Recalibrate the battery
1) Drain Battery Completely, make sure it doesn't even have the ability to give any indication that it is running
2) Wait 24 Hours
3) Recharge to 100%
-----------------------------
If worst case scenario and above does not work, instead of relying on cwm or twrp, use flashtool to completely reflash the firmware of your choice from scratch. This will remove any possibility of it being a software related issue.

424aca said:
Try to Recalibrate the battery
1) Drain Battery Completely, make sure it doesn't even have the ability to give any indication that it is running
2) Wait 24 Hours
3) Recharge to 100%
-----------------------------
If worst case scenario and above does not work, instead of relying on cwm or twrp, use flashtool to completely reflash the firmware of your choice from scratch. This will remove any possibility of it being a software related issue.
Click to expand...
Click to collapse
Okay, I will try. Though I am not sure if that would work. The second one may help, I am going to reflash the STOCK rom/kernel with FlashTool soon.

Overheating issues with fulmics 5.3: phone reboots

I have been using fulmics for a long time now. I live somewhere where the temperature is always something around 17-25 degrees on summer and never had an overheating problem. Now, I'm on holiday somewhere hotter (canary islands) and the 30-ish temperatures are causing my phone to reboot if i take a couple of pictures or if I open apps like pokemon go. I think this has something g to do with heat because back at the hotel, I don't have these issues at all. Even when i perform the same tasks at night, the phone does not reboot.
Now, I can't remember if I chose the stock or the the thermal throttle values upon installation but I'd like to ask, which would be the best option to avoid this issue and also, any other advice you could give in order to mitigate this issue. I asked on the fulmics thread over at xda but the mods locked it because some asshole didn't stop asking the dev for Etas. Screw that guy.
Any help would be welcome! Thanks!

Hi, there will probably be an update to fulmics 6.0 which should solve overheating problems. I'd recommend for you to move to Cloudy G3 2.5 or XenonHD with aCC kernel just for now.

I also have problems with heating. When the phone is at direct sunlight for some time it become irresponsible. I mean it don't reboot but message pop up "system ui stopped ....." and screen lock. I wonder if fulmics ROM is the reason for that. As far as I remember upon installation I choose stock settings, kernel.

Update! : This morning, I went out and the phone got literally unusable. Constant bootloops. Sometimes getting to see the wallpaper but after a couple of seconds, before the whole system boots, rebooting again. The temperature today is quite lower than the previous days and the phone sure didn't feel that hot on the back (power button is my thermometer). Back at the hotel, I tried to backup in order to wipe data and see if it's a data corruption issue. I had to try a couple of times to backup because the phone would reboot half way. I finally made it to the point where I reinstall the rom, before wiping, and the phone would reboot while fulmics was getting installed. I then remembered reading somewhere about the possibility of being a fubar battery, so I plugged the thing to the wall: instant fix. No more reboots. I even restored the backup without any reboots. Booted the rom perfectly. Let it load. Open pokemon go, see it works. Unplug from the wall and in less than twenty seconds: reboot.
Now, I'm on twrp without performing any task and saw my phone lose 30% of the battery in 45 minutes just sitting still. So yes, my bet is on a broken battery.
Whaddayathink?

My G2 acted like this when the battery died. Its a sure sign
GFXi0N said:
Update! : This morning, I went out and the phone got literally unusable. Constant bootloops. Sometimes getting to see the wallpaper but after a couple of seconds, before the whole system boots, rebooting again. The temperature today is quite lower than the previous days and the phone sure didn't feel that hot on the back (power button is my thermometer). Back at the hotel, I tried to backup in order to wipe data and see if it's a data corruption issue. I had to try a couple of times to backup because the phone would reboot half way. I finally made it to the point where I reinstall the rom, before wiping, and the phone would reboot while fulmics was getting installed. I then remembered reading somewhere about the possibility of being a fubar battery, so I plugged the thing to the wall: instant fix. No more reboots. I even restored the backup without any reboots. Booted the rom perfectly. Let it load. Open pokemon go, see it works. Unplug from the wall and in less than twenty seconds: reboot.
Now, I'm on twrp without performing any task and saw my phone lose 30% of the battery in 45 minutes just sitting still. So yes, my bet is on a broken battery.
Whaddayathink?
Click to expand...
Click to collapse

Battery problems with MM? Look here.

After taking the OTA to PD1 and then PF3, battery life was horrible and much worse than LP, despite doing factory resets, clearing cache and turning off Google backup.
However, after dirty flashing PF3 full firmware from here
http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
There's a noticeable improvement and all seems to be working well. I recommend trying this.

Did you notice any wakelocks beforehand? For me Android OS is keeping my GN4 awake just over 50% of the time, and I just bought a new battery and I can only squeeze 2 hours SOT out of it thanks to the wakelock. Sounds like a somewhat similar problem to mine. I've also factory reset several times, cleared cache and turned off backup.
What do you mean exactly by a dirty flash though? Just run the firmware through Kies/Odin and let it "install" on my phone?

Protocol114 said:
Did you notice any wakelocks beforehand? For me Android OS is keeping my GN4 awake just over 50% of the time, and I just bought a new battery and I can only squeeze 2 hours SOT out of it thanks to the wakelock. Sounds like a somewhat similar problem to mine. I've also factory reset several times, cleared cache and turned off backup.
What do you mean exactly by a dirty flash though? Just run the firmware through Kies/Odin and let it "install" on my phone?
Click to expand...
Click to collapse
Not sure how to detect wakelocks, but one of the reasons I updated to MM in the first place was Doze. I noticed that overnight the phone was not sleeping by looking at the bars in the battery screen. Now, after dirtyflashing, it seems to be sleeping much better. By dirty flash, I mean using Odin to flash the full firmware PF3 over my existing install. As I mentioned I had done a factory reset during my previous install.

Here, I don't know if you can see attachments but this is what I'm looking at (after dirty flashing with Odin as well.)
Notice how steep the graph is, and how it was pretty much awake through it all. And also notice how Android OS has a huge 4 hour "stay awake" timer. I keep turning more and more apps off and I can't figure this out, it's driving me up a wall. :crying:
So now I can tick "flash firmware with Odin" off of my list of things I've tried.

Protocol114 said:
Here, I don't know if you can see attachments but this is what I'm looking at (after dirty flashing with Odin as well.)
Notice how steep the graph is, and how it was pretty much awake through it all. And also notice how Android OS has a huge 4 hour "stay awake" timer. I keep turning more and more apps off and I can't figure this out, it's driving me up a wall. :crying:
So now I can tick "flash firmware with Odin" off of my list of things I've tried.
Click to expand...
Click to collapse
Yeah yours is even worse than what I had, including OS keeping it awake. This is what I would do. If you've previously done factory reset, then I don't think you need to do it again. Turn off backup. Another suggestion I've seen is to reset network preferences (wifi passwords, etc). Then dirty flash CP3. Clear cache through Settings and thru Recovery. After that I'm losing only about 2%/hour when not using it much (turning it on a couple times and hour to check messages but nothing intense, not leaving alone enough to go into Doze either).
The other option I would have taken if this hadn't worked, was to downgrade to 5.1.1.

Battery Drain following Oreo Update, even after update to Oxygen OS Open Beta 5

I have a Oneplus 3 and I have been quite happy with it .. up until got notified for an update to Oreo a few daya ago.
Since the update, the battery drain on the phone has been pretty bad and even when I am not using the phone, the battery is draining much faster than it should or was.
Yesterday I tried searching on Oneplus forum to see how to fix it, and saw some post suggesting to update to Open Beta 31. I downloaded the update the manually updated the phone, and the battery drain still seems to be same.
Fyi, my phone is not rooted.
Please see the image below for battery drain graph..
What I can see is that even when the screen is off, and the wifi is inactive .. the phone is still awake and not seemingly going into deep sleep mode..!!
Can anybody please help how to solve this issue?
Thanks

you could try better battery stats although it is a root app to find what is keeping the phone awake, i think you can use adb to grant the permissions for it to work without root or you could factory reset that should sort it out

myself01 said:
I have a Oneplus 3 and I have been quite happy with it .. up until got notified for an update to Oreo a few daya ago.
Since the update, the battery drain on the phone has been pretty bad and even when I am not using the phone, the battery is draining much faster than it should or was.
Yesterday I tried searching on Oneplus forum to see how to fix it, and saw some post suggesting to update to Open Beta 31. I downloaded the update the manually updated the phone, and the battery drain still seems to be same.
Fyi, my phone is not rooted.
Please see the image below for battery drain graph..
What I can see is that even when the screen is off, and the wifi is inactive .. the phone is still awake and not seemingly going into deep sleep mode..!!
Can anybody please help how to solve this issue?
Thanks
Click to expand...
Click to collapse
From the screenshot, I am able to see that you have a very patchy mobile signal which is one of the reasons for the drain .

Well, the signals have been same even before the update. The battery drain was not like this before.
In the last 8 hours, with little use the phone went to about 36%..
Now I can do a factory reset but it's an annoyance because all my data would get lost, or I'll have to backup and restore using some means.

myself01 said:
Well, the signals have been same even before the update. The battery drain was not like this before.
In the last 8 hours, with little use the phone went to about 36%..
Now I can do a factory reset but it's an annoyance because all my data would get lost, or I'll have to backup and restore using some means.
Click to expand...
Click to collapse
I have noticed that with an incremental update, things get sour on OP3. The best bet without losing data would be to clean flash the full ROM after wiping system, data (excluding internal storage), Dalvik and cache. I am sure your issue would be gone.
I always clean flash and have no such issues.

100% App related. I am getting great battery life on Oreo 5.0.1 by using Greenify. Maybe 3-4% overnight.

myself01 said:
Well, the signals have been same even before the update. The battery drain was not like this before.
In the last 8 hours, with little use the phone went to about 36%..
Now I can do a factory reset but it's an annoyance because all my data would get lost, or I'll have to backup and restore using some means.
Click to expand...
Click to collapse
Just because it worked before doesnt mean it will work the same after an update. Mainly with this OEM.

Hi,
I've tried clearing the cache and also deleting everything except personal data and reinstalled the update 31 multiple times. Still the same problem.
The battery is draining at about 10% every hour regardless.
Can anyone advise what else can i try?
My only doubt now is if the update 31 file is the right one to install. I'm assuming that because the file is approximately 1.5GB it is a full update rather than a incremental update.
If that's not the case, can anyone tell me which file to install as the full update?
Another problem I have noted since the update is that the Camera does not work. Not sure why though.
If nothing else works, I'd be forced to try and downgrade to android 7 though I'd prefer to have android 8 - if it works and does not drain the battery this much.

myself01 said:
Hi,
I've tried clearing the cache and also deleting everything except personal data and reinstalled the update 31 multiple times. Still the same problem.
The battery is draining at about 10% every hour regardless.
Can anyone advise what else can i try?
My only doubt now is if the update 31 file is the right one to install. I'm assuming that because the file is approximately 1.5GB it is a full update rather than a incremental update.
If that's not the case, can anyone tell me which file to install as the full update?
Another problem I have noted since the update is that the Camera does not work. Not sure why though.
If nothing else works, I'd be forced to try and downgrade to android 7 though I'd prefer to have android 8 - if it works and does not drain the battery this much.
Click to expand...
Click to collapse
You say that you have the OP3 but the heading of this thread refers to Open Beta 5 and then you say that you clean flashed Open Beta 31. Which is correct, OP3 or OP3T, OB5 or OB31? No wonder you are facing issues.

Hi
The phone is Oneplus 3
It prompted for auto update to Oreo, which I did.
Then started battery drain issues.
After reading forums, I updated to Open Beta 31.
The battery drain is still there and I have reinstalled Open Beta 31 couple of times which includes deleting everything from the phone excluding personal data, music etc.
I have cleared cache as well.

myself01 said:
Hi
The phone is Oneplus 3
It prompted for auto update to Oreo, which I did.
Then started battery drain issues.
After reading forums, I updated to Open Beta 31.
The battery drain is still there and I have reinstalled Open Beta 31 couple of times which includes deleting everything from the phone excluding personal data, music etc.
I have cleared cache as well.
Click to expand...
Click to collapse
I repeat, your mobile signal is one, if not the only, heavy drainer.
Install BBS, grant permissions through adb, run it and take an idle dump (as described in its thread) and attach it in the BBS thread. Someone there will study it and identify the culprit/s.

I've installed Bbs and here's what it shows:

It shows something named video2 is keeping the phone awake most of the time. I also found that the phone cpu is awake most of the time rather than being in deep sleep.
Looking on the internet, I can't find what video2 is!!
Any ideas?

Also just found that the YouTube app is also not working. I google'd and found many people have reported the same problem, and have been suggested to do a factory reset. So I've just done that as well and it has still not helped.

Here's another screenshot of betterbatterystat showing the same issue :

This shows that the phone is not going into deep sleep most of the time, as video2 is keeping it awake. Hence the battery drain.
Any ideas of what I can do to solve this please?

myself01 said:
Here's another screenshot of betterbatterystat showing the same issue :
Click to expand...
Click to collapse
myself01 said:
This shows that the phone is not going into deep sleep most of the time, as video2 is keeping it awake. Hence the battery drain.
Any ideas of what I can do to solve this please?
Click to expand...
Click to collapse
Tried a reboot? Don't use any force dozing apps or block wakelocks.

Yes, rebooted the phone and I am not using any app to restrict wakelocks or force dozing any apps - apart from what's inbuilt in the Oreo os.

myself01 said:
Yes, rebooted the phone and I am not using any app to restrict wakelocks or force dozing any apps - apart from what's inbuilt in the Oreo os.
Click to expand...
Click to collapse
It's known that Mobile Data can be a really big drainer. I easily go from 0.6% per hour on WiFi to +2% on mobile data, especially poor signal as you have shown can drain even more. You could try using Greenify with Shallow Hibernation, it doesn't kill apps it only restricts them from doing too much in the background, you could try blocking the wakelock with Bluspark's build in wakelock blocker. But I am highly against blocking things that you don't know (Can cause more wakelocks, random reboots etc).

If Video2 is similar to Video3 is then most likely camera related.
Maybe some app is using your camera and doesn't even let your device sleep. Which could make sense since even being awake all the time 10%/h drain is way to high with the screen off, so probably other hardware is being used.
Check your apps, you might even have malware installed. See what permissions was each app.
I'd recommend to backup your data, do a factory reset or even wipe system partition (although you need TWRP for that
Since you mention that YT is not working another possible option is that is some playback video related.
Same thing, backup and factory reset. Install each app with Playstore and don't restore backups.
Maybe when you backup your data into your PC run some kind of Virus Scan over all the file just to be safe.