Database Develop

Android System issue.

I'm getting unusually high Android System usage. Sometimes it outnumbers screen usage. If I start using the phone at the end of the day(10% battery life), my max SOT will be something like 2hrs with 20-30% Android System use. It happens on every single kernel and rom (SM-N920C). So here are the things I tried:
Stock russian based image with deepsleep fix/stock kernel (CF 2.66) N920CXXU2AOK6_N920COXE2AOJ5_N920CXXU2AOK5_HOME.tar.md5
Stock AUE based image with deepsleep fix/stock kernel (CF 2.66) N920CXXU2AOK6_N920COJP2AOJ5_N920CXXU2AOK5_HOME.tar.md5
Stock based image with arter97 v11 kernel and philz recovery.
Stock based image with SkyHigh v3.5 kernel with philz/twrp recovery.
Dr. Ketan rom with arter97/skyhigh kernel
Venom rom with arter97/skyhigh kernel
The problem is not in deepsleep, because the device does deepsleep when checking through betterbatterystats.
Tried disabling location/location history, android device manager, most of the samsung bloat through titanium backup. Also ejected the sim to make sure its not a network issue. Wifi is connected but when I check from betterbatterystats everything seems ok. No unusual wakelocks or anything. I literally tried everything.
Please help me.

Octa_core said:
I'm getting unusually high Android System usage. Sometimes it outnumbers screen usage. If I start using the phone at the end of the day(10% battery life), my max SOT will be something like 2hrs with 20-30% Android System use. It happens on every single kernel and rom (SM-N920C). So here are the things I tried:
Stock russian based image with deepsleep fix/stock kernel (CF 2.66) N920CXXU2AOK6_N920COXE2AOJ5_N920CXXU2AOK5_HOME.tar.md5
Stock AUE based image with deepsleep fix/stock kernel (CF 2.66) N920CXXU2AOK6_N920COJP2AOJ5_N920CXXU2AOK5_HOME.tar.md5
Stock based image with arter97 v11 kernel and philz recovery.
Stock based image with SkyHigh v3.5 kernel with philz/twrp recovery.
Dr. Ketan rom with arter97/skyhigh kernel
Venom rom with arter97/skyhigh kernel
The problem is not in deepsleep, because the device does deepsleep when checking through betterbatterystats.
Tried disabling location/location history, android device manager, most of the samsung bloat through titanium backup. Also ejected the sim to make sure its not a network issue. Wifi is connected but when I check from betterbatterystats everything seems ok. No unusual wakelocks or anything. I literally tried everything.
Please help me.
Click to expand...
Click to collapse
Let the phone settle down after flashing. I guess it so happens because it keeps system wakeclocks to check your usage patterns and then try to save battery accordingly from 2nd or 3rd charge cycle.
I'd recommend to wait after flashing a firmware.
Assuming you have a N920C (single sim), flash the OK7 version ROM (or even the iOiO custom ROM) with SkyHigh v3.5 kernel and allow it be stable after 1 or 2 days and then check. (You'll be surprised with good battery life)
Sounds good?

anmolkakkar said:
Let the phone settle down after flashing. I guess it so happens because it keeps system wakeclocks to check your usage patterns and then try to save battery accordingly from 2nd or 3rd charge cycle.
I'd recommend to wait after flashing a firmware.
Assuming you have a N920C (single sim), flash the OK7 version ROM (or even the iOiO custom ROM) with SkyHigh v3.5 kernel and allow it be stable after 1 or 2 days and then check. (You'll be surprised with good battery life)
Sounds good?
Click to expand...
Click to collapse
I wish it worked as great as it sounded. I have done that. It came to the point where the system started asking about optimizing apps (after couple of days) and I agreed. Nothing changed. It most likely is not a wakelock. Standby drain is normal but once I turn the screen on it starts going down really fast, like I can see it going down in front of my eyes.

Octa_core said:
I wish it worked as great as it sounded. I have done that. It came to the point where the system started asking about optimizing apps (after couple of days) and I agreed. Nothing changed. It most likely is not a wakelock. Standby drain is normal but once I turn the screen on it starts going down really fast, like I can see it going down in front of my eyes.
Click to expand...
Click to collapse
It may sound odd, but did you try a wipe data/factory reset?
Sometimes it can help!?

anmolkakkar said:
It may sound odd, but did you try a wipe data/factory reset?
Sometimes it can help!?
Click to expand...
Click to collapse
Like I said, I have been doing full stock installs, meaning everything is wiped off and I always set everything up from scratch, no backups.

Has Anybody Experienced or Seen This Screen Phenomenon?

I've posted this in one of Mirek's threads and it's been lost in conversation. Hopefully someone has some ideas.
http://forum.xda-developers.com/showpost.php?p=64996639&postcount=685
My guess is its Mirek's ROM, but I can't conclusively confirm. I've tried flashing his 4.4, but touch doesn't work and his fix doesn't either. What I DO know is that no such thing occurs when I'm in Windows. In Android, the screen/reboot issue happens randomly. Sometimes it can go hours without an incident, sometimes every 10-15 minutes. So it can't necessarily be a hardware problem, right? Then again, it might be that Windows is using the GPU properly, while this version of Android is messing with it.
All said, this is getting rather annoying.
Thanks in advance!

same problem here, whenever I'm playing wordfeud. I got mirek rom 7.Extremely annoying, has anyone a fix for this?

After testing nearly the whole versions of Mirek's roms including lollipop and kitkat , I found that the best stable and performing rom is the stock kitkat rom and you can root it to remove the bloatware out of it and you'll have battery free bug and the other related complications .

melmarghaney said:
After testing nearly the whole versions of Mirek's roms including lollipop and kitkat , I found that the best stable and performing rom is the stock kitkat rom and you can root it to remove the bloatware out of it and you'll have battery free bug and the other related complications .
Click to expand...
Click to collapse
Stock Kitkat, as in from Teclast?

[SOLVED] How to fix the TW Oreo battery calibration issue.

so for some reason upgrading to oreo really messes up the battery calibration for me. at first, everything will be fine, but after a few reboots and using the phone, the battery percentage is everywhere. I'll plug my phone to charge and the percentage will rise as if it were seconds. I love oreo to bits, and I prefer it over nougat obviously. I used Odin to flash a stock rom, and still it's happening. anyone know what we can do to fix this? I know others here have the same problem.
EDIT (09/03/2019):
some people have mentioned ways to try and fix the problem, so I decided to make this a thread to try and find a solution to the calibration issue.
How can I participate?
You can participate by (briefly):
*submitting a solution you have found
*submitting an idea that may potentially work
*testing the fixes or ideas submitted
What else?
*solutions that are submitted are to be tested and confirmed if they work or not.
*ideas can also be tested, but at your own risk. make sure to make a backup of your current rom and storage if you don't want to lose anything.
*also submit what model you have (unless this applies only to the G610F model - we cant tell).
we can do this. I am tired of android nougat (android N doesn't have this issue).
EDIT (14/04/2019)
so, now that our phone actually recieved OneUi, theres no point for this thread android Pie doesn't have this problem, which is fantastic. thanks for those who contributed!
ill keep this thread around in case there are some bois out there who still prefer oreo for whatever odd reason.
but honestly tho, oneui is perfect.
PEACE!!
EDIT 13/05/2019
SOLVED!! (FINALLY)
right now im running oreosama rom, with no issues, no problems at all - i have (accidentally) found the solution to this battery problem!
the solution is very simple - download a stock oreo rom from sammobile or updato, and then flash its bootloader with odin. the battery calibration issue occurs cause the bootloader is still based on nougat. that issue goes away once you upgrade.
there you go folks - happy oreo flashing!!

lor3tz said:
so for some reason upgrading to oreo really messes up the battery calibration for me. at first, everything will be fine, but after a few reboots and using the phone, the battery percentage is everywhere. I'll plug my phone to charge and the percentage will rise as if it were seconds. I love oreo to bits, and I prefer it over nougat obviously. I used Odin to flash a stock rom, and still it's happening. anyone know what we can do to fix this? I know others here have the same problem.
Click to expand...
Click to collapse
I have the same problem after an OTA update.

officially from samsung?

Try to use Battery Calibration app on CHPlay of SuperThomasLab, read instruction and follow that, i am in TW Oreo and my battery is OK although it stills rarely mess up

I have this problem and I don't know why. I have Android 8.1 official

I had the same problem but .. its gone after flashing oreosama rom and in other TW roms that supports USSD CODES (including the stock) I used *#0228# and it worked everything was ok

Can you give more details?
AhmedKhamis67 said:
I had the same problem but .. its gone after flashing oreosama rom and in other TW roms that supports USSD CODES (including the stock) I used *#0228# and it worked everything was ok
Click to expand...
Click to collapse
i could give this a try. im desperate to get my phone fixed lol.

AhmedKhamis67 said:
I had the same problem but .. its gone after flashing oreosama rom and in other TW roms that supports USSD CODES (including the stock) I used *#0228# and it worked everything was ok
Click to expand...
Click to collapse
so I updated the post. anyways, I tried your idea. I downloaded oreosama and used the ussd code. I thought everything was fixed, then suddenly it gave the usual problems. so your solution did not really work. is there any way we could like port the nougat battery files over to oreo?

If you try to delete battery.bin?
Maybe it would help you.

Drain to 0% and charge your phone to 100%. While plugged in, dial *#0228# and press 'Quick Start'. It would be better if you are on stock ROM. Do it 1 or 2 times and you are good to go. Works like charm for me.

do i dial the ussd code once the phone has reached 100%? how do i know if theres a battery calibration issue?

Beytullah61 said:
If you try to delete battery.bin?
Maybe it would help you.
Click to expand...
Click to collapse
somebody test this

lor3tz said:
somebody test this
Click to expand...
Click to collapse
It worked on my phone.

I think you need to replace the battery with new one

Before doing make sure battery is at 100%
1. Go to root/data/system.
2. Delete all the files which have a name that starts with battery.
3. Delete the Dropbox folder.
4. Reboot to TWRP.
5. Go to Wipe -> Advanced Wipe. Choose dalvik and cache partitions and then wipe them.
6. Reboot and check.
For TWRP and root users ..

op post edit~

guys, ive finally fixed the problem. check the OP to see how!

Help, all of your methods are not work on my phone. My phone is charged too quickly to 100% and after restart the battery is draining to 10%.

did you upgrade the bootloader to Oreo?

lor3tz said:
did you upgrade the bootloader to Oreo?
Click to expand...
Click to collapse
Yeah.

Battery drain over the night?

Recently I switched back from PE to stock using MiFlash and manually installed all updates. (It's my decision to do this because of some kind of security issue with my banking app.) However, I noticed that comparing to previous stock and previous PE ROM, it's currently using a lot (~20%) of battery over the night with the same settings. Plus, some WiFi doesn't work anymore. So I am wondering if flashing through MiFlash has restored the firmware or kernel to the official version? If so, what's causing the problem?

By the way, I did check some tech info and it seems that my CPU isn't stuck at maximum.

Note8 Random Restarts when Idle

I have searched all over the place for anything that works with no luck, so asking sharper minds.
My Note8 phone started restarting randomly if left idle. The deets:
Have tried settings, updates, safe mode, cache wipes, factory resets etc multiple times. Not better even without loading backed up data and apps.
A reboot is usually every 3-10 minutes
Reboots in full; functions properly when not restarting
Can stay on as long as there is battery unless lock screen is dismissed
Stays on connected to the laptop/charger.
I concluded this may be a faulty battery as I let it run dry a few times since upgrading to a newer Note.
BUT
If I let Audible (ebook reader) or YouTube run in the background. It is a continuous operation and the phone does not restart until the app is closed. (Phone restarts with or without Audible installed so the app does not seem to be the problem).
Does it seem like the battery to anyone else, with the apps functioning?
Or should I reflash Samsung stock ROM. Those seem like the only options to me. Anything?
Thanks for taking the time.

Tried flashing the official Samsung ROM again to see if it helped.
Odin: 3.14.1
ROM: Official N950FXXSCDTF1 (Australian)
As long as the phone was downloading updates after the flash, there were no resets. As soon as it went idle it rebooted within a couple of minutes.

Hi, have you solved the problem? Have you tried to change the battery?

ok.

Install wakelock v3 from play store.
My galaxy note 8 had the same problem and it got fixed after installing it.

AVMY said:
Install wakelock v3 from play store.
My galaxy note 8 had the same problem and it got fixed after installing it.
Click to expand...
Click to collapse
Can you show settings of this app?

Plbeat said:
Can you show settings of this app?
Click to expand...
Click to collapse
USE 4th option: Processor: known to fix Galaxy note 4 issues.

AVMY said:
USE 4th option: Processor: known to fix Galaxy note 4 issues.View attachment 5765945
Click to expand...
Click to collapse
This works!!! Thanks alot!

The OP is since 2 years inactive, therefore I don't quote his message.
But according to my understanding, this is an issue with deep-sleep and should be properly fixed in kernel via an OTA update from Samsung or by trying to flash latest stock ROM from sammobile.com with ODIN or alternatively (recommended) you can try to flash a custom kernel. I've made one for Note8 and so far nobody reported such a deep-sleep issue to me.
I don't recommend at all to use that wakelock app, since it's only a workaround and will prevent your Note8 to enter in deep-sleep mode. That means higher battery usage without working deep-sleep.

ace2nutzer said:
The OP is since 2 years inactive, therefore I don't quote his message.
But according to my understanding, this is an issue with deep-sleep and should be properly fixed in kernel via an OTA update from Samsung or by trying to flash latest stock ROM from sammobile.com with ODIN or alternatively (recommended) you can try to flash a custom kernel. I've made one for Note8 and so far nobody reported such a deep-sleep issue to me.
I don't recommend at all to use that wakelock app, since it's only a workaround and will prevent your Note8 to enter in deep-sleep mode. That means higher battery usage without working deep-sleep.
Click to expand...
Click to collapse
Thank you for the advice Sir. I did flash stock rom via Odin but no luck. Wakelock v3 is the only app that worked for me. As you said it drains 2 to 3 percent battery per hour.

Plbeat said:
This works!!! Thanks alot!
Click to expand...
Click to collapse
Sir, the app drains 2 to 3 percent battery per hour even when the screen is off.

@AVMY
Yup, because phone stays awake. Honestly I can't believe that even on latest Samsung kernel it's not fixed. Strange, unfortunately I don't have an Note8 for testing. I've only S8 phone but the hardware is almost the same and there is no deep-sleep issue, no matter if I use latest stock kernel from Samsung or if I use my custom kernel.
Try with A2N kernel, if it'll still reboot, just post last_kmsg (see post #3 how-to provide last_kmsg) in the Note8 thread, then I'll check what's wrong. But as I said, so far nobody reported this.