Database Users

[Q] CPU @ 681 Mhz max ???

This is my 1st post at the forum (1st android phone too )
i run benchmark with app called "CPU info", screenshot in the attached file
The CPU speed was 681,57 MHz only. Are there probably problems with firmware or power management ?
sry for my bad English...

dtgiang said:
This is my 1st post at the forum (1st android phone too )
i run benchmark with app called "CPU info", screenshot in the attached file
The CPU speed was 681,57 MHz only. Are there probably problems with firmware or power management ?
sry for my bad English...
Click to expand...
Click to collapse
the CPU has power states it probably just read the low power state and reported that
i get a similar thing with my computer when running benchmarks programs report 800mhz because its at idle before it starts so it reads the idle state then when the test starts and places load on the cpu it scales up to the full 3.8ghz
i assume the phone does something similar

noobdeagle said:
the CPU has power states it probably just read the low power state and reported that
i get a similar thing with my computer when running benchmarks programs report 800mhz because its at idle before it starts so it reads the idle state then when the test starts and places load on the cpu it scales up to the full 3.8ghz
i assume the phone does something similar
Click to expand...
Click to collapse
Quite right. There is no need in running at 1 GHz when there is nothing to do. Get an app called Quick System Info - it shows cpu and ram usage in the notification bar.
Sent from my Desire HD using XDA App

Ok, thanks for reply.

Just another list of questions...

Hi all, I know there are threads already created for questions etc but I've an extensive list of them and I don't think its appropriate to spam them in someone else's thread. And I'll update the first post of the answers and replies I've received for the questions I've posted!
My phone's information: will5's MIUI ROM 2.5.25 GB 2.3.7
My list of questions
Android OS
::Hard rebinding hard keys::
Is that possible? My power button recently got damaged and its really tough to press the power button now which is quite a problem, is there any way to rebind the power button to say the camera button? (specifically the 2nd-click of the camera button, not the first click (focus)) MS2Toolbox is able to wake screen with the camera button but thats just soft-sided and I need to hard bind for turning on the phone and using the recovery etc... :crying:
::Allow app to stay active when screen-off and when not in foreground:: http://forum.xda-developers.com/showpost.php?p=29658020&postcount=95
I want to let my app, specifically Opera Mobile, to be constantly active as I run a script (user javascript) on it which repeats its function periodically. Is there a way to keep it active throughout deep-sleep, or when in the background? Currently its working well when I switch the screen off as long the app was in the foreground. The script and Opera Mobile still runs perfectly and I do not experience battery drain (weird). I have been doing so for the past few months and it takes probably only 30% of my battery overnight when I sleep despite the periodic data connection. However, this didn't happen on the MIUIv4 ROM when I tested it. The app is 'frozen' or suspended, it seems, the moment I switch the screen off. Tried apps which disabled deep sleep etc but didn't work. Any ideas?
Overclocking
::What are the default VSELs for the respective frequency for MS2?::
I know there's one here http://forum.xda-developers.com/showpost.php?p=11620994&postcount=1 by santiemanuel, but it gives VSELs WAY above those I'm using or the defaults from MS2Toolbox. Say, for 300MHz, the stock vsel is 33 and 30 is considered unstable. How ever the default in MS2Toolbox for that frequency is 17 if I'm not wrong. I'm using that at the moment and it seems to be running fine (used powersave governor to enforce 300MHz to test it out). Just to confirm, should I really follow that table?
WiFi
::Changing Milestone 2's WiFi MAC address::
Hi guys, I've been trying to look for a way to change my M2's MAC address but have not been able to get it to work.
I've googled up for methods but the common ones do not work.
Tried so far:
- The nvram.txt file
Can't find it in the usual folders stated.
- busybox ifconfig tiwlan0 hw ether <MAC>
- busybox ip link set dev tiwlan0 addr <MAC>
Tried these two commands but didn't work either in terminal emulator. Even did the off-on-immediately spam commands but no luck.
Unsorted
Code:
http://forum.xda-developers.com/showpost.php?p=29675172&postcount=905

::SOLVED::
Overclocking
::How do I check the current VSEL and frequency at any point in time?::
I'm trying to underclock and ultra-undervolt to save as much battery as possible and want to know how's the selected governor working in order to manually optimize the settings to my preferences.
::How do I know its an unstable VSEL?::
Q: Quite vague a question but... as said in the first question, I'm running 300MHz at a VSEL of 17 instead of 33, nearly half of the stock. How would I be able to tell if its unstable? When I'm running in powersave governor, it shows that the 'system' process stopped responding at boot and I've the wait/close option, but after selecting wait the dialog disappears and the phone still works as per usual. However its very sluggish, clearly because of the underclock. Regardless, does the system process being unresponsive at the start shows it is unstable?
A: djlooka via PM
djlooka said:
...My suggestion is: try with that setvsel app for defy (see my answer in the CM9 thread) which comes with a useful mini-stress tester app (you can install it from within the main OC app). It can stress test every single freq step, so you can find its 'sweet-spot-vsel'.
One could also think that there's some advantage in fine tuning the middle steps. IMHO it's wasted time
After some days of tweaking, I realized that our phone will stay in the two the middle steps (combined) for less than 5% of the time. So even if you could save some % of the power by losing 1 or 2 vsel points (let's say 10% of the original vsel), the "on the road" gain would be infinitesimal (10% x 5% = 0.5%).
Anyway it's fine to OCD a bit even about those 2 steps
My final word is: find the lowest possible vsel for both the top and bottom freqs by stress testing. To be extra careful, raise them by one point for rock solid.
E.g.: 300-22 is the best combo for my lowest step -> I put 300-23, and so on.
Click to expand...
Click to collapse
::3 steps shown in the bootloader but 4 shown in MS2Toolbox::
Q: This has been bugging me recently. I've read recently that the M2 has 4 steps for its CPU. So the CPU actually follows the 4 steps shown in MS2Toolbox or the 3 in the bootloader? Note: When I change the values in the bootloader, the values changes respectively in MS2Toolbox for the 2nd,3rd,4th rows (did not tick auto apply in M2T to prevent overlaps with bootloader settings). But the 1st row shows values lower than the one in the 2nd row automatically.
A: djlooka @ http://forum.xda-developers.com/showpost.php?p=29806494&postcount=908
djlooka said:
...Our phone, instead has 4 steps (300, 600, 800, 1000 MHz - the same as the Defy+).
AFAIK, when you set a configuration which allows only 3 steps (in the bootmenu), the hw internally adjusts to have the last 2 steps equal (e.g. 300, 600, 800, 800 MHz).....
Click to expand...
Click to collapse
Applications
MX Player - Does not require codecs. If it requests for ARMv7 NEON codec, get the NEON version of the player instead.

[Q] Full stock n9005 - Hotplugging misbehaving, cores stuck online (2 or 4)

Hi,
Anyone been keeping an eye on hotplugging on the n9005 ?
Mine is still unrooted, so I'm talking 100% vanilla Samsung configuration...
I use Android Tuner's online core notifications to keep an eye on this, there are other apps that can to this as well.
At some point, after a few hours of uptime, sometimes only after quite a many (20h+), I just notice that it will never drop below 2 or 4, never had it lock on 3 minimum, so can't comment on that scenario.
Once this happens, it's impossible to get back to single core even on very low load.
Also when leaving the device doing nothing, freq. drops to 300MHz and still 4 cores remain online.
There is obviously an impact on battery drain as well.
Only way to get back to normal is to reboot...
JP.

I've noticed the opposite issue, two cores just going offline forever until I reboot the device.

So that would point to obvious hotplugging issues, except if you ran into thermal throttling, maybe.
Were you running some heavy stuff when this happened ?
JP.

i tested it out of curiosity using the widget in system monitor app.
i have exactly the same issue as SentinelBorg above. the two cores go offline and never come back online until the next restart.
very wierd.

Well for the very least we can conclude hotplugging is flawed in the current firmware ...
As soon as we get a proper recovery (nandroid restore that don't bootloop) I'll start working on an improved kernel, this is just not acceptable for a top notch 700€ pricetagged device
JP.
Send from my Note 3 (n9005)

Latest case ...
Send from my Note 3 (n9005)

Again ...
Send from my Note 3 (n9005)

You're on full stock. Doesn't that mean you have no options regarding CPU government?

nakedtime said:
You're on full stock. Doesn't that mean you have no options regarding CPU government?
Click to expand...
Click to collapse
Correct, so I cannot do anything about this misbehaving, except reboot.
I want to know whether this is something others observe as well.
The thing is, if you're not looking at it, you won't know it's happening, cause who really keeps an eye on online cores all the time ? I do as I do kernel coding and as such also work on governors, which make me look at stuff like that.
If this happens of yours, you'll just have a hotter Note 3 with less lasting battery without knowing why, or worse without knowing battery easily could last longer if that was fixed.
This clearly is a bug in the current firmware, since as you correctly stated, being full stock unrooted, I can't be influencing this in any other way than applying load to the CPU which is clearly not the case as you can see in the screenshots... and it just happens randomly.
Once I start on a Note 3 kernel that will be in the top list of things to take care of.
JP.
Sent from my SlimBean 4.3 build 1.8 / Yank555.lu CM10.2 kernel v1.6g-beta4 (Linux 3.0.99) powered Galaxy S3 i9300

I would have gone with the N9000 if I knew how to develop a kernel. BIG.little sounds like so much fun to dev on.
PS
Have you found any Info about the thermal throttling? I'd love to be able to manipulate the temps for less heat when over clocking.

I was actually not going to get any more Samsung device because of crappy open source support they (in fact don't) give
I ended up going for the note 3 because of the specs and exactly because it was the Qualcom and not the Exynos version and a one time offer I could not refuse, but I will go nowhere Samsung's own super secret Exynos CPUs ever again unless they change their policies, which I doubt.
I just do hope I won't regret my move...
JP.
Sent from my SlimBean 4.3 build 1.8 / Yank555.lu CM10.2 kernel v1.6g-beta4 (Linux 3.0.99) powered Galaxy S3 i9300

exactly the same here, after a reboot everything is back to normal
Sent from my SM-N9005 using Tapatalk 2

Happened again after ~10h uptime while watching a live video stream...
Cores went to a steady 4 online, load was unchanged over a longer period (~45 mins of video stream over WiFi).
This makes little sense, hotplugging is flawed.
JP.
PS: Still stock unrooted.
Send from my Note 3 (n9005)

This is still happening for me, reboot solves it. Running 4.4.2 and thought this should be solved by now.
Sent from my SM-N9005 using XDA Premium 4 mobile app

Stock kitkat XXUENB3, unrooted. I have a similar problem when all of the sudden all cores are stuck online with core 1 and 2 stuck at 1958 mhz and core 0 and 3 scaling normally just not going offline. A reboot fixes the issue untill it happens again randomly. This is my last Android device and I had gs2,gnex,n4 and now n9005.

I've rooted and when the issue happens, disabling mp decision and enabling it again fixes the issue so this means that hotplug doesn't play well. Maybe a custom kernel will fix this issue.

ciprianruse88 said:
I've rooted and when the issue happens, disabling mp decision and enabling it again fixes the issue so this means that hotplug doesn't play well. Maybe a custom kernel will fix this issue.
Click to expand...
Click to collapse
Yes, long time I've open this thread
Indeed, on TW I used to do just that, "pkill -9 mpdecision", which killed the daemon and it respawned and all was back to usual.
I've since then moved to CM11, and this never happened again ever since, so I expect this to be a TW related issue, since mpdecision had the same MD5 signature in CM11 as on my stock 4.3 TW ROM.
And it looks like if the problem still persists on KK TW...
But it's certainly not a kernel related issue, as I've use my own kernel on JB TW, where this happened as well, once I went CM11, I ported my kernel to CM, and as I mentioned, never happened ever since.
Might be TW messing with DVFS (for benchmark cheating and maybe other things...).
Maybe worth trying to use Wanam's Xposed Module and disable ROM DVFS.
JP.

2 cores always online and the other 2 always offline= Dual Core
Ok guys I have experienced the bug with 2 cores being always offline which basically makes your Note 3 a dual core phone many times in the past untill I found what caused this! Even firing up Antutu the cores are still 2 and not 4 online! So yeah at first a reboot was an easy and effective sollution but that was not enough so I devoted 2 days trying to find out what caused this. Guess what? The problem was inside one of Samsung apps, specifically the bloody S-Finder app! I can reproduce the bug 100% whenever I want so I am very sure about it! Also I have tested this on 2 other Note 3s (n9005) and I noticed the same bug , with 4.3 and unfortunately now on 4.4.2!
Steps to reproduce it:1) Fire up S-finder 2) Search any app and launch it or even without launching just only by typing on the search bar the phone enters into dual core mode(!) after few seconds 3)Now this is the critical step, remember now the phone is already having only 2 cores enabled so if you press the home button then you are stuck with the buggy dual core mode!!! So this is how you end up with only 2 out of 4 cores working!
The sollution is of course to reboot the phone but another more faster and specific sollution is to close the S-Finder with only this (correct) way: while you are on the S-finder app close it by simply pressing the back button untill it exits completely and you are out to the menu. Incase you are not in the S-finder app then you must check if the program is shown in the recently used apps(longs pressing the home button) then tap on it to open it and then close it by hitting the back button." Don't close/kill it from the task manager or from the recently used apps, only close it when you are inside of the app and hitting the back button!"
Synopsis All in all, the culprit at least on my case is the S-finder app in which when it is used it somehow forces the phone to get into dual core mode and it stays like this because you forget to properly close it after the search is done. The sollution is simply closing the S-Finder gently/properly by using the back button from the inside of the app and not with any other way.
I don't know if this is truly a bug of Samsung or just a sneaky way to increase/improve the battery life at the expense of performance but I surely know that many people have this issue without even realising it!
I said too many things so that I can give a detailed review on this bug, I hope I have expressed it clearly and not to confuse you!
I think it is a very serious issue and it should be fixed as well as inform people about it!

SAVVAS. said:
Ok guys I have experienced the bug with 2 cores being always offline which basically makes your Note 3 a dual core phone many times in the past untill I found what caused this! Even firing up Antutu the cores are still 2 and not 4 online! So yeah at first a reboot was an easy and effective sollution but that was not enough so I devoted 2 days trying to find out what caused this. Guess what? The problem was inside one of Samsung apps, specifically the bloody S-Finder app! I can reproduce the bug 100% whenever I want so I am very sure about it! Also I have tested this on 2 other Note 3s (n9005) and I noticed the same bug , with 4.3 and unfortunately now on 4.4.2!
Steps to reproduce it:1) Fire up S-finder 2) Search any app and launch it or even without launching just only by typing on the search bar the phone enters into dual core mode(!) after few seconds 3)Now this is the critical step, remember now the phone is already having only 2 cores enabled so if you press the home button then you are stuck with the buggy dual core mode!!! So this is how you end up with only 2 out of 4 cores working!
The sollution is of course to reboot the phone but another more faster and specific sollution is to close the S-Finder with only this (correct) way: while you are on the S-finder app close it by simply pressing the back button untill it exits completely and you are out to the menu. Incase you are not in the S-finder app then you must check if the program is shown in the recently used apps(longs pressing the home button) then tap on it to open it and then close it by hitting the back button." Don't close/kill it from the task manager or from the recently used apps, only close it when you are inside of the app and hitting the back button!"
Synopsis All in all, the culprit at least on my case is the S-finder app in which when it is used it somehow forces the phone to get into dual core mode and it stays like this because you forget to properly close it after the search is done. The sollution is simply closing the S-Finder gently/properly by using the back button from the inside of the app and not with any other way.
I don't know if this is truly a bug of Samsung or just a sneaky way to increase/improve the battery life at the expense of performance but I surely know that many people have this issue without even realising it!
I said too many things so that I can give a detailed review on this bug, I hope I have expressed it clearly and not to confuse you!
I think it is a very serious issue and it should be fixed as well as inform people about it!
Click to expand...
Click to collapse
Yes. I've did the exact same thing and cpu was dual core but after I've reset mp decision I couldn't reproduce it anymore. Good catch!

Yank555 said:
I use Android Tuner's online core notifications to keep an eye on this, there are other apps that can to this as well.
Click to expand...
Click to collapse
How did you enable the online core notifications in Android Tuner?

[Q] RAM test app for Note 3 / Android?

Hi all,
Is there some kind of RAM test app (like memtest x86 for Windows/DOS) for the Note 3 / Android devices ?
Lately my Note 3 started to reboot out of the blue, many 'xxxx has stopped' errors.
I was still on 4.2 stock (root) so I decided to upgrade to an custom KK ROM.
The usual 5 mins to leave the phone alone was not enough, immediate freezes. It seemed that removing the battery and putting it back in fixes it for a few mins but then I get the same freeze.
Nothing responds and the area around the camera gets hot. So I tried the stock ROM and various other custom ROMS and recovery's. Nothing helped, exactly the same, freeze within minutes.
So I did a cpu stress test, that went fine CPU temperature was also normal, but still it felt hot around the camera. Bootloader was up to date.
So in the store they told me it could be the RAM. They also told me that they saw I tried an custom ROM and I lost my warranty. I reminded them of the non-conformity in Europe and they quickly changed their judgement.
They said 3 weeks at most before I get it back...
Now I've got an nice Nokia 206 Blue
But to get back at my question: Is there is any app to test the RAM? And has anyone else experienced these kind of problems?

stability test from play store may help you. also check check 3c toolbox, it does not have proper memory test, at least I didn't see one, but it has about 60, probably more, different utilities, like system and kernel logs, sd memory speed test, device recorder, cpu temp monitor etc.
if the area around camera is getting hot, maybe that's the problem? if the cores get stock at full speed, they would overheat, start thermal throttling and then errors would start showing up.

same problem
I have the same problem with my note 3 LTE, is there any solution?

tmfares said:
I have the same problem with my note 3 LTE, is there any solution?
Click to expand...
Click to collapse
Read the post above and try .

[Q] Note 4: Performance Issue

Hi Guys,
I am a new Note 4 user, I've had note 2 before. Recently I have used Z3, OneplusOne and S5, which in my opinion other than the S5, the phones were smooth and laggieness was non existence. I have since changed to the Note 4 and immediately I have realised that even in the kitkat (currently running lollipop) that the phone lags when changing between the programs, turning on the camera, or even after a picture has been taken it takes a while to get to respond. Hardwar-wise I believe the Note 4 is very respective and I can only blame this on the software. I have since upgraded to lollipop and I must say the performance is no different than before. Could anyone tell me without rooting and installing a modified rom, is there a way to increase the smoothness of the phone? it is because of the bloatware? how to de-bloat? or is it just how it is?
Thanks
Patrick

the better is a clean installation and after that come back and report any issue's

Thanks vagenrider but this issue was already apparent when I first used the phone right out of the box and noticed the lag.

pplwu said:
Thanks vagenrider but this issue was already apparent when I first used the phone right out of the box and noticed the lag.
Click to expand...
Click to collapse
hi,
I can say this,
that i had my Note4 (N910F rooted, stock Rom.) since October 2014 till now.
Overall i had little or no "lag" of note. (apart from Recent button plus an setting issue.. minor )
Over this period of time, if i found/noticed a bit of "lag" and i found culprit, causing the problem, I would uninstall app,
i also noticed, so far that it has always been a 3rd party (badly coded.. or on lollipop the app was not "playing" nicely.. etc etc)
So overall.... when i was on Android v 4.4.4 or now on Lollipop my device has been working fine.. battery use, been good, very, very smooth
So all i can say, if you have issues it is either you have a faulty device or an app/combination of apps causing lag.or setting issue
I have stated this, in many of my post that i have following devices.. on hand
Note 4, Note 3,Note 8.0 (tab) Note 2 and they all running fine..( 100% satisfaction)
Bottom line
is that i think i am in a good position to state that my Note 4 compares 100%plus, with my Note3(which is a very very, good device, smooth no lag, etc etc)
Above is just my opinion and i hope that you can sort out your device
Good luck

pplwu said:
Hi Guys,
I am a new Note 4 user, I've had note 2 before. Recently I have used Z3, OneplusOne and S5, which in my opinion other than the S5, the phones were smooth and laggieness was non existence. I have since changed to the Note 4 and immediately I have realised that even in the kitkat (currently running lollipop) that the phone lags when changing between the programs, turning on the camera, or even after a picture has been taken it takes a while to get to respond. Hardwar-wise I believe the Note 4 is very respective and I can only blame this on the software. I have since upgraded to lollipop and I must say the performance is no different than before. Could anyone tell me without rooting and installing a modified rom, is there a way to increase the smoothness of the phone? it is because of the bloatware? how to de-bloat? or is it just how it is?
Thanks
Patrick
Click to expand...
Click to collapse
I am having the same issues with my device. I've had it with both lollipop and KK. I've had multiple ROMS (all stock). I've done fresh installs, cleaned cache, disabled apps, and completely run with none of my apps installed. All the same issues, as you've mentioned. I'm thinking of returning my note 4 if they don't fix it by 5.1.1 or August. This device cost way too much for these kinds of issues... :-\

zkyevolved said:
I am having the same issues with my device. I've had it with both lollipop and KK. I've had multiple ROMS (all stock). I've done fresh installs, cleaned cache, disabled apps, and completely run with none of my apps installed. All the same issues, as you've mentioned. I'm thinking of returning my note 4 if they don't fix it by 5.1.1 or August. This device cost way too much for these kinds of issues... :-\
Click to expand...
Click to collapse
pplwu said:
Hi Guys,
I am a new Note 4 user, I've had note 2 before. Recently I have used Z3, OneplusOne and S5, which in my opinion other than the S5, the phones were smooth and laggieness was non existence. I have since changed to the Note 4 and immediately I have realised that even in the kitkat (currently running lollipop) that the phone lags when changing between the programs, turning on the camera, or even after a picture has been taken it takes a while to get to respond. Hardwar-wise I believe the Note 4 is very respective and I can only blame this on the software. I have since upgraded to lollipop and I must say the performance is no different than before. Could anyone tell me without rooting and installing a modified rom, is there a way to increase the smoothness of the phone? it is because of the bloatware? how to de-bloat? or is it just how it is?
Thanks
Patrick
Click to expand...
Click to collapse
About debloating:
Without root you cannot really debloat the rom. You can only try to holding every app you don't need and drag&drop on touch wiz launcher and drag&drop it to "app details". New window with details will be prompted and you can delete or deactivate the app. This is everything you can do on stock to debloat.
About the main problem:
Also here without root and custom rom I could only suggest to try following:
Go to Settings app.
Scroll down to device information.
Tap few times (I think 5 times shoul it be) on build number to activate developer options.
Go back to main screen of settings, scroll down to developer options and open them.
So from here you can try to change following values:
- Force GPU rendering
- Turn off hardware overlays
- lower values for animations (all three) or just set them to zero if you don't need them. That gives really bounce speed (but mainly just for eyes, it doesn't really chages overall performance of device, just little bit maybe)
The nagtive thing of GPU and harware overlay is little bit higher the battery drain then usual.

vbaschen said:
About debloating:
Without root you cannot really debloat the rom. You can only try to holding every app you don't need and drag&drop on touch wiz launcher and drag&drop it to "app details". New window with details will be prompted and you can delete or deactivate the app. This is everything you can do on stock to debloat.
About the main problem:
Also here without root and custom rom I could only suggest to try following:
Go to Settings app.
Scroll down to device information.
Tap few times (I think 5 times shoul it be) on build number to activate developer options.
Go back to main screen of settings, scroll down to developer options and open them.
So from here you can try to change following values:
- Force GPU rendering
- Turn off hardware overlays
- lower values for animations (all three) or just set them to zero if you don't need them. That gives really bounce speed (but mainly just for eyes, it doesn't really chages overall performance of device, just little bit maybe)
The nagtive thing of GPU and harware overlay is little bit higher the battery drain then usual.
Click to expand...
Click to collapse
Thanks for that!! I've just done the above, will use this setting for a while and see how it goes.

Hi Guys, after applying vbaschen's suggestion I believe the phone has improved in terms of window changing and smoothness in operation. Battery discharge hasn't affected me that much given the battery has always lasted an entire day of heavy use and I plug it in everynight. I would recommend this quick mod. Thanks again vbaschen.

vbaschen said:
About debloating:
Without root you cannot really debloat the rom. You can only try to holding every app you don't need and drag&drop on touch wiz launcher and drag&drop it to "app details". New window with details will be prompted and you can delete or deactivate the app. This is everything you can do on stock to debloat.
About the main problem:
Also here without root and custom rom I could only suggest to try following:
Go to Settings app.
Scroll down to device information.
Tap few times (I think 5 times shoul it be) on build number to activate developer options.
Go back to main screen of settings, scroll down to developer options and open them.
So from here you can try to change following values:
- Force GPU rendering
- Turn off hardware overlays
- lower values for animations (all three) or just set them to zero if you don't need them. That gives really bounce speed (but mainly just for eyes, it doesn't really chages overall performance of device, just little bit maybe)
The nagtive thing of GPU and harware overlay is little bit higher the battery drain then usual.
Click to expand...
Click to collapse
Right on. I was going to recommend reducing the animation values as well as that is usually the case. Hope it helped!

Androidious said:
Right on. I was going to recommend reducing the animation values as well as that is usually the case. Hope it helped!
Click to expand...
Click to collapse
I went for a completely different solution: the Note 4's Snapdragon cpu has the bad habit of heating up very quickly. Two or three minutes of heavy usage (gaming/emulation, or worst: piles of file operations, e.g. media scanner) make it shoot up to 85° C. To prevent serious damage, the cpu is then automatically scaled down to extremely low values, which results in abysmal performance. When I first unboxed my N910F and inserted my old sdcard, the media scanner went haywire because my sdcard was faulty (works alright in my old Note 2, but the Note 4 is picky). The phone quickly got too hot to even touch, ran sluggish as hell (AnTuTu scores between 24000 and 29000), then shut itself down. :crying:
After I had replaced the sdcard, things got better, but only when I didn't put too much load on the phone: 52000 AnTuTu points in the morning (first thing to do with the cold phone), but getting worse steadily until I couldn't score more than 43000 points.
Now, after a lot of fiddling and tweaking (Kitkat, Lollipop, Stock, Custom, CM 12.1), I finally settled for (Lollipop) Emotion Revolution R8 ROM along with the Emotion nightly kernel (r17) and (most important) Synapse kernel tweaker. Instead of overclocking the blasted thing even more, I actually downclocked it one step (2572,8 MHz). The result: a rock stable phone that actually runs way better than with the higher (stock) clock rate. The cpu hardly ever scratches 70° C, and usually stays around 65° C even when I run demanding apps like PPSSPP, Dosbox, or Real Racing 3 (don't like that one, but it beats the s**t out of the cpu - 85° with stock cpu clock!). AnTuTu scores reach about 51500 - almost as much as with stock clock rate - but several times in a row now, with no performance hit. So, even though the peak performance may be one or two percent lower, I can run my phone for hours without any performance drops. Oh, and it's good for battery life, of course. :good:
So, if you're rooted, you may want to give it a shot. :fingers-crossed: