Related
Hi all,
Had my Nexus 6 for a while and love it, but its starting to get a little sluggish and I've been having a look at a few ROMs available but I've not quite found one thats took my fancy. I was wondering if someone could recommend a ROM that's minimal providing good performance and possibly something that allows a CPU and GPU overclock? If I'm not mistaken its the kernel that provides the overclocking facility and not the ROM. I have seen a ROM (must include a kernel) that states CPU and GPU overclocks but in the description its actually downclocked for battery life.
Just throwing it out there in case someone reading this could answer as well, I've heard GTA San Andreas is an intense game to play on High settings, how does (stock) perform or as a bonus do you know how it performs with an overclock? I was surprised to see quite a few phone on benchmarks beat the Nexus 6
Thanks for any help/recommendations
first off, questions go into the q&a/help section, not into general. secondly, roms do not provide oc, or performance enhancing. thirdly, you want to try different kernels, as they provide oc and performance enhancements. i use elementalx kernel, which allows me to oc to 3033mhz.
and which phones beat the n6 in benchmarks? i get 58500 on antutu with my n6.
simms22 said:
first off, questions go into the q&a/help section, not into general. secondly, roms do not provide oc, or performance enhancing. thirdly, you want to try different kernels, as they provide oc and performance enhancements. i use elementalx kernel, which allows me to oc to 3033mhz.
and which phones beat the n6 in benchmarks? i get 58500 on antutu with my n6.
Click to expand...
Click to collapse
Hi,
Yes as I did say I did pick up that kernels provided over clocking and I will try elementalx and see how that goes. As for the benchmarks for graphics I come across this website and filtered out Desktop and over 7" devices and that's where I discovered the Nexus 6 quite low down the score board.
http://gfxbench.com/result.jsp
Well definitely got some stuff to do now, I shall hopefully remove forced encryption and get elementalx on the go and see how it goes.
simms22 said:
first off, questions go into the q&a/help section, not into general. secondly, roms do not provide oc, or performance enhancing. thirdly, you want to try different kernels, as they provide oc and performance enhancements. i use elementalx kernel, which allows me to oc to 3033mhz.
and which phones beat the n6 in benchmarks? i get 58500 on antutu with my n6.
Click to expand...
Click to collapse
Hi Again,
Took absolutely ages to install ROM and kernel because I deleted everything I'm twrp (advanced options) but Chroma ROM and Elementalx kernel are installed but I have some questions if you can help. First you have a massive 3033 over clock which if I recall was an option available when installing through recovery, however I've paid for the Elementalx app and highest over clock available is: 2649. Any reason for this? Also can I re install Elementalx through recovery without loosing anything?
Also there's only a 600mhz clock available for graphics is it possible to get higher ?
Last but not least I was really looking forward to having no encryption but it seems Elementalx installs with encryption.. Anyway around this? I've heard of read and write increases of up to three times faster.
mrsweet1991 said:
Hi Again,
Took absolutely ages to install ROM and kernel because I deleted everything I'm twrp (advanced options) but Chroma ROM and Elementalx kernel are installed but I have some questions if you can help. First you have a massive 3033 over clock which if I recall was an option available when installing through recovery, however I've paid for the Elementalx app and highest over clock available is: 2649. Any reason for this? Also can I re install Elementalx through recovery without loosing anything?
Also there's only a 600mhz clock available for graphics is it possible to get higher ?
Last but not least I was really looking forward to having no encryption but it seems Elementalx installs with encryption.. Anyway around this? I've heard of read and write increases of up to three times faster.
Click to expand...
Click to collapse
if you intall the kernel through tbe app, youll get less options. install it tbrough the recovery, amd go ghrough thd setup and choose 3032mhz.
for the gpu, yes, 600 is the max. no way around that.
the kernel supports decryption, but you have to decrypt first, its not automatic. to decrypt, you have to reformat your storage, then boot up with the kernel.
simms22 said:
if you intall the kernel through tbe app, youll get less options. install it tbrough the recovery, amd go ghrough thd setup and choose 3032mhz.
for the gpu, yes, 600 is the max. no way around that.
the kernel supports decryption, but you have to decrypt first, its not automatic. to decrypt, you have to reformat your storage, then boot up with the kernel.
Click to expand...
Click to collapse
Hi again,
I originally did everything through recovery but didn't choose the highest over clock I just assumed it could be changed in settings or something.
Anyway to decrypt.. If I go into TWRP and perform a wipe (the three things that it selects as default) shall I install just the kernal first (no rom, su or gapps) to get the option to decrypt? Then install the ROM , Gapps and su afterwards?
Sorry for the newbness
mrsweet1991 said:
Hi again,
I originally did everything through recovery but didn't choose the highest over clock I just assumed it could be changed in settings or something.
Anyway to decrypt.. If I go into TWRP and perform a wipe (the three things that it selects as default) shall I install just the kernal first (no rom, su or gapps) to get the option to decrypt? Then install the ROM , Gapps and su afterwards?
Sorry for the newbness
Click to expand...
Click to collapse
lol, thats alright, we were all newbs once.
no, thats not how things work. a rom has to be installed, then the kermel. then you reformat your storage, then you just reboot and youre unencrypted
btw, im still encrypted. besides the read/write speeds, it all is the same.
Read the disable forced encryption thread in development. Take your time before you mess things up.
simms22 said:
lol, thats alright, we were all newbs once.
no, thats not how things work. a rom has to be installed, then the kermel. then you reformat your storage, then you just reboot and youre unencrypted
btw, im still encrypted. besides the read/write speeds, it all is the same.
Click to expand...
Click to collapse
ok, I wiped the phone in TWRP installed Chroma then Elementalx, gApps then supersu then I selected to wipe data and I had to type yes. Afterwards Chroma would be stuck in a boot loop. It said Android is starting.. starting apps but then immediately restart. So I tried again but after installing everything I just performed a factory reset and this time it worked, but I have an odd problem.. it;s installing apps but saying I'm running out of storage space?.. I went into storage and it shows 25.98GB available.. any ideas? and also thanks for your help I do now have it decrypted and I think im running an overclock that you had.. I'll have to wait for the app to install to verify
mrsweet1991 said:
ok, I wiped the phone in TWRP installed Chroma then Elementalx, gApps then supersu then I selected to wipe data and I had to type yes. Afterwards Chroma would be stuck in a boot loop. It said Android is starting.. starting apps but then immediately restart. So I tried again but after installing everything I just performed a factory reset and this time it worked, but I have an odd problem.. it;s installing apps but saying I'm running out of storage space?.. I went into storage and it shows 25.98GB available.. any ideas? and also thanks for your help I do now have it decrypted and I think im running an overclock that you had.. I'll have to wait for the app to install to verify
Click to expand...
Click to collapse
just reboot. thst happened to me twice, not enough space, and i rebooted. fixed it for me. i believe it said i was running out of space in the /system/. oh well.
simms22 said:
just reboot. thst happened to me twice, not enough space, and i rebooted. fixed it for me. i believe it said i was running out of space in the /system/. oh well.
Click to expand...
Click to collapse
Hi,
before you replied I went ahead and tried flashing again this time not performing the wipe after I installed everything. But now I can't get rid of the boot loop, everytime Chroma starts for the first time a window appears saying "apps are starting.. starting apps" but once finished it reboots... I've tried flashing everything and performing a wipe, flashing and performing a cache and delvik wipe and also flashing and performing nothing just booting into system... however im still stuck in that boot loop.. seems I've gone a step backwards somewhere lol.. any ideas? I'll continue flashing in the meantime until I get a reply thanks for your help again
This time I wiped user data as well as factory reset so there was nothing at all on the phone. restarted into TWRP which mounted the file system so I could transfer all the files over from my PC. installed everything as per usual and once installed I didn't wipe delvik cache I just selected to boot into system but same again it just says starting apps and once finished just reboots.
mrsweet1991 said:
This time I wiped user data as well as factory reset so there was nothing at all on the phone. restarted into TWRP which mounted the file system so I could transfer all the files over from my PC. installed everything as per usual and once installed I didn't wipe delvik cache I just selected to boot into system but same again it just says starting apps and once finished just reboots.
Click to expand...
Click to collapse
After restarting around 3 times its finally booted.. how odd
mrsweet1991 said:
After restarting around 3 times its finally booted.. how odd
Click to expand...
Click to collapse
ok, I keep getting optimising apps on every boot so not too sure why that is, but storage space running out is gone and encryption is also disabled. One thing however is Elelemntalx app shows the default overclock being used and not exceeding 2265,, however if I go into CPU settings I see 3033 as on option but when selected it won't change the overclock above the default max
mrsweet1991 said:
ok, I keep getting optimising apps on every boot so not too sure why that is, but storage space running out is gone and encryption is also disabled. One thing however is Elelemntalx app shows the default overclock being used and not exceeding 2265,, however if I go into CPU settings I see 3033 as on option but when selected it won't change the overclock above the default max
Click to expand...
Click to collapse
its because youre at 40% battery or less. on 5.1, the cpu automatically drops to 2265. at 20%, it drops even more. nothing you can do about it at this point
simms22 said:
its because youre at 40% battery or less. on 5.1, the cpu automatically drops to 2265. at 20%, it drops even more. nothing you can do about it at this point
Click to expand...
Click to collapse
Sweeet waiting for it to get another 20 odd percent then see if it gets 3033
Vindicator kernel supports 2.9ghz CPU OC and 700mhz GPU. Optipop or benzo ROM are both pretty optimized.
I've been seeing constant complaints around the OnePlus 3's development section of the forums regarding an unusual high CPU usage and massive battery drain on different ROMs. These reports are posted in the custom kernels thread.
flar2's ElementalX kernel thread (now locked unlocked):
[link removed]
eng.stk's blu_spark kernel thread:
[link removed]
The reports mostly state that "(insert kernel name) gives high CPU usage, battery drain, etc." flar2 and eng.stk both say it's not the kernel, yet every custom ROM seems to have issues with this strange "bug". Even stranger, it only affects some users.
So what gives?
To preface, I'll be as verbose as I can about my experience with this: I had this exact issue with the CPU nearly maxing out and massive battery drains on LOS/AOSP-based ROMs. I clean-flashed Resurrection Remix, DU, Citrus, and CypherOS, and I even tried flar2's EX kernel, blu*spark, and stock kernel that ships with the ROMs; every one of them had this problem. On average, I use my phone daily, but not really heavily (I don't play games, but I either web browse, Youtube, or calling/text), so I found it odd that my phone's battery drops from 100% to 72% every time I get up in the morning and down to 15% after only 2 hours of using my phone. I thought this was strange since I never had this problem before. I checked my phone's battery stats (Settings -> Battery) and didn't find anything strange. I blamed CM/LOS and switched to AOSP, same issue. From there was a full day and half of switching ROMs, swearing, and confusion. What I should've done from the start was check the logcat because the solution was literally written all over the logcat.
Something related to the modem was silently crashing in the background.
It would restart again and again, crashing every 5-10 seconds or so. It would comment something about com.phone.android - I forgot to save a screenshot of the message
but nevertheless this error was 5-6 lines long and was scattered all over the logcat. Again, silent crash: no (processes) has stopped, unfortunately, (processes) has stopped, etc). This would explain why my device never entered deep sleep and sky-rocketed the CPU frequency.
To conclude, I firmly believe the high battery drain and CPU usage is actually caused by Oxygen OS's 4.0.x firmware, NOT THE KERNEL. When I switched to 3.2.8 firmware or 3.5.5CE my issue was completely fixed - 10 hours of SOT and very good performance using the EX kernel +AKT combo. I think the reason why some people have this problem and others don't is because they're on different firmwares. Through testing, 4.0.x has these problems whereas 3.5.5CE and 3.2.8 does not.
I want to note that I did not test stock Oxygen OS. The firmware downgrade solution may also not work for you - hence why the thread's title name is "a potential fix". Some users on FreedomOS, Experience, or other custom Oxygen-based ROMs have reported two approaches to fix battery and CPU usage:
The modem/phone errors on firmware 4.0.x could be limited to custom AOSP/LOS ROMs. Using an older firmware may cause Oxygen OS Nougat to not boot anymore, so backup everything and make sure you have a restore point before trying my fix.
TL;DR: This is NOT a kernel issue. Don't blame flar2, eng.stk, or anyone but OnePlus. I believe this is a bug in OnePlus' Nougat firmware. Until OnePlus fix this, I urge everyone to flash either 3.2.8 or 3.5.5 firmware and see if the High CPU usage and battery drains are gone on custom AOSP/LOS ROMs. You can try downgrading firmware on Oxygen OS - but please backup and make a restore point if the ROM does not boot (I did not test stock Oxygen OS). If you're on Oxygen OS, I suggest you try using phhh's root and changing SELinux Policy to permissive first (though SELinux should be enforced) before downgrading firmwares. OnePlus needs to fix their unstable firmwares (and release Camera blobs, etc)!
STEPS:
0. If you're on Oxygen OS, try phhh root and changing SELinux policy to permissive first. If that doesn't work, or if you're not on Oxygen OS, go to the next step.
1. Go to jamal's firmware/modem collection: (link removed)
2. Click the Android 6.x button.
3. Click link to download Firmware + Modem zip 3.2.8 OR 3.5.5CE (I recommend 3.2.8).
4. Flash in TWRP recovery (any recovery version works).
5. Reboot and enjoy better battery life and no high CPU usage
5a. If you set a lockscreen with PIN, chances are that you won't be able to get pass the lockscreen; in that case, reboot back to TWRP recovery, mount /system, use the built-in filemanager to navigate to /data/system, and delete the 5 gatekeeper/lockscreen files.
5b. If your ROM kernel panics after flashing firmwares (screen suddenly goes black, reboots), delete the init.d folder.
UPDATE:
I've been doing some testing with the OOS 4.0.x firmware and I think I found out the issue!
I kept getting the same battery drain on LOS/AOSP-based ROMs. Reading the thread, it seems hardly anybody has this issue on newer firmwares. At first, I thought it was an F2FS issue. I started from scratch by wiping everything (including the internal storage), changed the /data partition to ext4, and upgrading TWRP. When I booted the ROM afterwards and let my phone sit for a few hours, I still had that strange error with the CPU behaving abnormally and battery drain. So I took to the logcat and started searching.
The error that generated heat and battery drain from OOS 4.0.x's firmware is the following:
Code:
Sending non-protected broadcast com.android.imsconnection.DISCONNECTED from system 2019: com.android.phone
com.android.phone? That's familiar....remember how I said in the OP it was a modem issue? But just above the error has this message:
Code:
ImsSenderRxr : Response data: [12, 13, -1, ...
That's Enhanced 4G LTE Mode! All I needed to do was flip the switch OFF and viola! All errors gone, CPU stable and minimal battery drain. Oxygen OS does not error out like this, so I'm certain this "issue" is exclusive to just LOS/AOSP.
Looking at the OP I realize how silly this thread is. I could've just attached the logcat into the Q/A thread and asked for help, done deal. My apologies everyone. If you downgraded the firmware to try this "fix", upgrade back!
For people running Oxygen/Freedom/Experience OS: if you have drain, this fix still applies to you:
Use phh's superuser instead of SuperSU
Using the command:
Code:
su
setenforce 0
or using init.d scripts to change SELinux's policy to permissive
If /data is F2FS, try changing it to EXT4
I'm open to discussion - did this solution work for you? Anyone try this on Oxygen OS? Or perhaps you have a different solution? Comment below, or use the poll! That will help me when I create future OP threads
Instead of complaining appreciate the efforts of eng.stk and flar2. Some are spoonfeed they don't want to search. Thank you for posting this!
madsponge26 said:
Instead of complaining appreciate the efforts of eng.stk and flar2.
Click to expand...
Click to collapse
To the contrary. I really appreciate their work for the OnePlus 3. They're extremely talented developers that I definitely look up to. I just blame OnePlus for the bugs
madsponge26 said:
Some are spoonfeed they don't want to search.
Click to expand...
Click to collapse
I completely agree with this, and it's sad, really. I remember when new XDA members were collaborating with developers and innovating (sorry, Apple). Now it seems like too many members are treating XDA like a technical support site.
madsponge26 said:
Thank you for posting this!
Click to expand...
Click to collapse
You're welcome
I've had this issue as well. I went from Experience Rom to Stock 4.0.2 since when I used Xceed the CPU load didn't go below 60%. But this is not a kernal issue.
I have flashed the 3.2.8 firmware+modem over OB11 and did not experience any bootloops. We'll see how battery fares.
The issue is in 99℅ of the cases the one described by @NevaX1 here, do his solution and all will be perfect my CPU finally dropped to 300mhz.
Edit link: https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348/page546
TLR: run in terminal
Su
Setenforce 0
peshellas said:
The issue is in 99℅ of the cases the one described by @NevaX1 here, do his solution and all will be perfect my CPU finally dropped to 300mhz.
Edit link: https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348/page546
TLR: run in terminal
Su
Setenforce 0
Click to expand...
Click to collapse
Well I tried this fix and it doesn't seem to work.. I'm currently on Oos 4.0.2 rooted and bluspark r32 kernel and I still have the hand warmer.. Heat is just reeks from all parts of phone :/
That's just a workaround and for example flar2 didn't recommended to run SELinux in that mode.
@kentexcitebot, did you tested stock ROM provided by OP? I might try it because I don't see in OP foruns people complaining about this battery drain and I'm curious how this relates to custom ROMs only, when in the end they are based on stock.
sarus_b said:
Well I tried this fix and it doesn't seem to work.. I'm currently on Oos 4.0.2 rooted and bluspark r32 kernel and I still have the hand warmer.. Heat is just reeks from all parts of phone :/
Click to expand...
Click to collapse
When you send the su command did it ask you, and you gave root permissions? Also if you use ARISE you must go to titanium backup and freeze an app called something like arkansysaudio, my spelling might be little off. I clean flashed Experience 10.1 then bluespark r32, then magisk and then phh root for magisk(latest) all was perfect but there was heat etc, after the nevax1 solution that was also gone. Phone is now perfect and passes safetynet security (snapchap, pay, etc)
Edit: In order to use magisk and phh root, you must completely remove supersu(it has an option in the app). So best way should be
0.flash the twrp 3.0.4
1.Flash rom
2.Flash bluspark r32
3.Reboot
4.Extract stock boot.img feom the rom you flash(open it via file Manager, its the first file you see)
5.Go to SuperSU app settings and completely remove it, and say no when it asks to restore boot.img
6.reboot to recovery
7.select install and change to image install, choose the boot.img you extracted and flash it in boot partition when it asks.
8. Flash kernel
9. Flash latest magisk(10.2 at the moment)
10. Flash latest "phh for magisk"
11.reboot
12. Install phh app from play store
13.open magisk and it should ask for root via phh Interface and then show you that magisk a d root are functional (you can test safetynet security on there too with one button)
14. Open terminal and run "su"( it will ask permission), and after that run "setenforce 0"
15. Profit, all should be perfect and you can enjoy it even safetynet free
Optional: download AKT PROFILES 1.2 app(not zip) and install. Run it give it root, and restart it. After that run it choose ballanced or battery saving profile of your choice for even greater battery and smoothness.
peshellas said:
When you send the su command did it ask you, and you gave root permissions? Also if you use ARISE you must go to titanium backup and freeze an app called something like arkansysaudio, my spelling might be little off. I clean flashed Experience 10.1 then bluespark r32, then magisk and then pph for magisk(latest) all was perfect but there was heat etc, after the nevax1 solution that was also gone. Phone is now perfect and passes safetynet security (snapchap, pay, etc)
Click to expand...
Click to collapse
Yes there was a prompt, obviously I won't be using kernel without being rooted..
Anyway I don't use any mods you mentioned yet the problem is still there... It has just decreased now.. Now it depends on my phones mood when to start heating up..
Same here, after the workaround I can't feel that much the heat but the drain is clearly there. Android System was taking 45% of the drain. Using FreedomOS with blu_spark kernel and no mods except Adaway.
peshellas said:
The issue is in 99℅ of the cases the one described by @NevaX1 here, do his solution and all will be perfect my CPU finally dropped to 300mhz.
Edit link: https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348/page546
TLR: run in terminal
Su
Setenforce 0
Click to expand...
Click to collapse
Yup, I have that in the OP.
lxxs said:
That's just a workaround and for example flar2 didn't recommended to run SELinux in that mode.
@kentexcitebot, did you tested stock ROM provided by OP? I might try it because I don't see in OP foruns people complaining about this battery drain and I'm curious how this relates to custom ROMs only, when in the end they are based on stock.
Click to expand...
Click to collapse
Like I wrote in the OP, I do not recommend changing the SELinux policy. I also mentioned in the OP that I did not test Oxygen OS, reason being that OOS 4.x seems like a rushed product (so I put no time investing to flash OOS). Since I haven't flashed OOS, I wrote on the bottom of the OP if anyone has modem errors popping up in the logcat. My "fix" is to simply downgrade to a stable firmware (3.2.8 preferably).
Looking at the comments so far, I think Oxygen OS may not be affected by the modem bug. I'll wait and see what people write in the comments and will edit the OP if necessary. Maybe try flashing the firmware, then clean flash the ROM?
EDIT: I just edited the OP so the phhh root workaround is more visible!
lxxs said:
That's just a workaround and for example flar2 didn't recommended to run SELinux in that mode.
@kentexcitebot, did you tested stock ROM provided by OP? I might try it because I don't see in OP foruns people complaining about this battery drain and I'm curious how this relates to custom ROMs only, when in the end they are based on stock.
Click to expand...
Click to collapse
Yes he doesn't recommend it for safety reasons, but it is far worse to run the phone in a max cores overheating state, it will at some point damage the motherboard and other components. So either this for now or downgrade to another version. Also people with stock op rom have it too, not all though, same with custom roms guys, not all face the issue. And im also suspecting it cam be related yo the kernels not managing selinux properly, but again, some people with custom kernels said ot worked out of the box.
---------- Post added at 10:54 AM ---------- Previous post was at 10:52 AM ----------
sarus_b said:
Yes there was a prompt, obviously I won't be using kernel without being rooted..
Anyway I don't use any mods you mentioned yet the problem is still there... It has just decreased now.. Now it depends on my phones mood when to start heating up..
Click to expand...
Click to collapse
Try all steps, they are not mods, its alternative root. I just did all those as mentioned exactly and problem is gone, I spent hours to come down to this. :fingers-crossed:
After writing:
su
setenroce 0
shall i get any feedback message? or just a new line to write a command?
Hello OP, thanks for getting this point out. I never liked blaming on things which we use for free , plus the devs put a lot of effort.
I have few questions. I'm kind of novice.
I'm on Experience ROM v9.6 with SuperSu 2.78 and modified twrp.
Can I flash the 3.5CE modem over it? I'm kind of scared with Op3.
I don't have anything beside it.
Thanks
AvivEliyahu said:
After writing:
su
setenroce 0
shall i get any feedback message? or just a new line to write a command?
Click to expand...
Click to collapse
There won't be any feedback, but if you go into Settings and to About Phone, then scroll to the bottom, you'll see that SELinux policy changed from "enforcing" to "permissive".
shubhaemk said:
I'm on Experience ROM v9.6 with SuperSu 2.78 and modified twrp.
Can I flash the 3.5CE modem over it? I'm kind of scared with Op3.
Click to expand...
Click to collapse
Try using phh root and changing SELinux first before downgrading the firmware. Don't worry about hard-bricking your OnePlus 3 - I've done bad things like flashing a OnePlus 3t version of custom ROMs (not unified) and I got out of it
Instead of updating old firmware and all, try the following to fix the issue permanently. Will persist across reboots as well -
Extract ElementalX / blu_spark kernel zip
append the following to cmdline parms
Code:
androidboot.selinux=permissive
Repackage and flash from TWRP
File is present at following location in the either zips -
ElementalX - boot/cmdline.sh
blu_spark - kernel/blu_spark_tweaks.sh
Before
Code:
androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x237
After
Code:
androidboot.hardware=qcom user_debug=31 androidboot.selinux=permissive msm_rtb.filter=0x237
Its possible swith this with seLinuxModeChanger
Sent from my ONEPLUS A3003 using XDA-Developers Legacy app
Hey @kentexcitebot.
U really saved up many ppl's life with this...
After applying Ur fix my overnight drain is 1-2%, unlike b4 when it was >15%.
It really works , I really appreciate Your work.
Currently my device running Freedom Os 2.2, no kernal, only magisk+phh super su.
and battery is awesome .
Thanks,
Cheers!!!!!!!!!!!!!!!!!
I am using RR build 20170116 and firmware 4.0.2. Never had this problem. It occasionally does not go to deep sleep after screen off. Clear data of Google Play service or reboot always fix the problem.
How can I explain it if there's a problem with firmware 4.0.x?
Hi, I have got my N910F rooted phone with stock firmware build
MMB29M.N910FXXS1DPH1
and E-motion kernel.
These days I've installed L Speed to get a faster phone but I'm noticing many lags..unfortunately..
I notice the kswapd0 and Android system often suck my cpu.
I found on the web that if you want fox the kswapd0 issue you need to use Semaphore kernel but I installed E-motion kernel because I'm using a Zerolemon large battery and this kernel can read the battery in a correct way.
Therefore I'm thinking to change the Rom for example but I don't know them..
I thought about Emotion Revolution that you can match with the Zerolemon kernel.
In my phone I have installed about 650 apps (Titanium finds 660apps).
What do you think? Can I solve my lags issues?
Thanks!!
Sent from Note 4 device - Rome - Italy
umby75 said:
Hi, I have got my N910F rooted phone with stock firmware build
MMB29M.N910FXXS1DPH1
and E-motion kernel.
These days I've installed L Speed to get a faster phone but I'm noticing many lags..unfortunately..
I notice the kswapd0 and Android system often suck my cpu.
I found on the web that if you want fox the kswapd0 issue you need to use Semaphore kernel but I installed E-motion kernel because I'm using a Zerolemon large battery and this kernel can read the battery in a correct way.
Therefore I'm thinking to change the Rom for example but I don't know them..
I thought about Emotion Revolution that you can match with the Zerolemon kernel.
In my phone I have installed about 650 apps (Titanium finds 660apps).
What do you think? Can I solve my lags issues?
Thanks!!
Sent from Note 4 device - Rome - Italy
Click to expand...
Click to collapse
Sounds like you are suffering from the same symptoms I have. After over a years worth of usage and a couple "dirty" flashes to improve speed / stability my device was suffering from random reboots, slowdowns and lag spikes. In the end the only real solution is a factory reset
I've tried wiping cache, re flashing roms / kernels, trying different kernels (even though I need the zerolemon fix) all without any meaningful success
I'm unsure of the exact cause of the lag though. Even completely stock devices will experience lags / slowdowns after several years and the recommended fix from the manufactures themselves is a factory reset. This is only exasperated by flashing custom roms, kernels and patches which may introduce memory leaks, data leaks or other instability.
Personally I went back to a stock (debloated) Samsung based rom with Emotion's Zerolemon kernel, restored most of my apps and re-setup everything system related. It's now running like-new again.
Sadly there is no "quick fix" for this issue and, like me, your attempts to solve issues regarding speed / reliability by flashing various patches and fixes have come back to bite you.
So:
Backup userapps in Titanium (Do not backup / restore systemdata)
Perform a Nandroid Backup
Flash the rom of your choice (Do not flash the kernel yet)
Factory reset (Wipe system, Cache, Dalvik Cache in recovery)
Boot into android and perform the initial set-up
Flash the kernel in recovery (No need to wipe anything)
Boot back into android and begin restoring user apps and setting everything back up the way you like it.
I know "factory reset" probably isn't the answer you were hoping for but it's the only option I have found which fixes these issues for longer than a couple days..
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.
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.