Guys i need help. I have branded Huawei P8 Lite, and there is 4 cores locked. I found out (on my last phone, Alcatel One Touch Mini S 2) that this utility can unlock rest of cores, and improve performance on phone. I was doin that with Kernel Auditor app before, but on my P8Lite app just freezes when i'm selecting CPU settings. I tried other apps but problem was the same, or apps was not free (i'm broke). I've rooted phone, installed busybox and superuser, permissions works normal. Do you have any ideas how to unlock 8 cores in that phone?
btw, i was trying performance mode on cpu developer, works as 4 cores with maximum speed, not 8 cores, and i can turn off cores (of course only this 4 cores that are available)
If you help me i'll be very, very happy, i just hate limits on branded phones.
The cause of the problem is Huawei's Power Manager software, and this "core-locking" function cannot be removed, or disabled at this point of time. I'm almost sure, apart from the Power Manager, the kernel itself has such "core-locking" thing too.
I don't know know why Huawei did this, and why they didn't include an option to use all 8 cores with manual settings.
However, tests show that the last 4 core will activate under heavy load, meaning you should not need to manually unlock them.
Personally, I don't have any performance issues with the phone, all apps running smoothly, fast, and responsively, without any major lag.
I think without these regulations, the stand-by time would be much much lover than the current stand-by time, which is a solid 1 day for me, with WiFi/LTE always on, 10-15 calls, a few YouTube vids, and almost 5-6 hrs of Spotify music a day.
On the other hand, a few guys are already working on bringin AOSP and CM to our phone, with custom kernels, maybe after the new kernels, you will be to able to use all 8 cores, but as I said before, right now, there is no option to forcefully turn on all the cores.
Thanks for reply so fast, for me that utility is important cause it greatly improved battery life for Alcatel (like 2-3x time). But if it's locked directly from Huawei i guess on this time it's not worth to risk hardbrick. Anyway, thank You for clearing it for me
Good info on that:
http://forum.xda-developers.com/p8lite/general/octacore-4-cores-t3223533/page2
Conclusion: 8 cores work ONLY WHEN REALLY NECESSARY in Intelligent mode. CPU stats app seems to see all cores working nevertheless. CPUZ and CPUX don't see them working normally, in Intelligent mode at least.
Related
Uhh, I cannot post this in development as I am still a newby :-(
However:
Hello,
I came from Symbian (Nokia C7-00) and liked the phone very much. Everything worked the way it should. (I was especially interested in office functionality.)
Now I bought a Galaxy Note and I really love the hardware.
But I discovered that it uses much energy and it doesn't like to sleep as often as it could. (I already returned to Android GB, which gives a better experience, but there still is room for improvement.)
1. Sometimes even though the phone simply lies around and does nothing, the last app that I forgot to close is hindering the CPU from sleeping. Why? The is no need.
2. At night I am used to turn the phone into flight mode. However I found out that this isn't the best thing for Android. In the morning, when the email app goes to push phase, the phone leaves sleep mode and seems to excitedly wait for the flight mode to get switched off. This uses *quite* a bit of battery!
These things seem strange to me. My impression is that Android is not really optimised for cell phones. If the screen is off, there is no need for CPU time, doesn't it? There is nothing urgent to do; everything could be done slowly; no hurry.
I guess the battery could last *much* longer if this would be improved.
Greetings,
corcov
corcovo said:
Uhh, I cannot post this in development as I am still a newby :-(
However:
Click to expand...
Click to collapse
Which is handy, because this thread has nothing to do with development and thus saved you from some abuse!
Regards,
Dave
Sent from my GT-N7000 using Tapatalk 2
But I already know how to click the "thanks" button
corcovo said:
But I already know how to click the "thanks" button
Click to expand...
Click to collapse
Doesn't matter.
Development, if you did not create IT, then it does not belong in development. Remember that. Otherwise you will get flamed.
Android is a mobile OS, so of course it is optimised for smart phones - not ordinary cell phones. Android acts like a computer and, if you keep a computer running Crysis 2 for example, it would burn more power than a computer just playing some music off of iTunes.
In terms of improving your battery, check your brightness. You can download widgets to adjust the brightness right from the home screens. I use these to set my brightness to its lowest whilst at home (perfectly adequate for night and indoor use away from sunlight) and turn it onto automatic when I go outside. This has saved my a bunch of battery.
If you are running a stock Samsung ROM, turn on power saving mode. I always leave it on and, frankly, I have no idea as to what it actually does. I haven't noticed a performance drop in the slightest, but if it saves a bit of battery it is worth it. Also, you could try Juice Defender or some other battery saving apps which work for some people - others not.
Finally, ensure you haven't left GPS, Bluetooth or WiFi on when not needed. Try downloading CPU Spy to check your phone deep sleeps, yet mine even without it ever deep sleeping gets around 16 hours of battery life which is still the best I have ever gotten on a smart phone. Bettery Battery Stats can show you wake-locks (apps that are keeping your phone active) also.
Brad387 said:
Android is a mobile OS, so of course it is optimised for smart phones - not ordinary cell phones.
Click to expand...
Click to collapse
I see. Well it might be a nice feature if one could add an "now be a cell phone"-option for energy enhancement, which means: if screen if off, sleep.
c.
corcovo said:
1. Sometimes even though the phone simply lies around and does nothing, the last app that I forgot to close is hindering the CPU from sleeping. Why? The is no need.
Click to expand...
Click to collapse
There are some legitimate needs for keeping the CPU from sleeping for a short period of time - such as finishing a sync operation (otherwise, the radio power spent beginning the sync is wasted). Unfortunately, some poorly written applications (Facebook for example) abuse the wakelock mechanisms and hold wakelocks when it is not justified.
2. At night I am used to turn the phone into flight mode. However I found out that this isn't the best thing for Android. In the morning, when the email app goes to push phase, the phone leaves sleep mode and seems to excitedly wait for the flight mode to get switched off. This uses *quite* a bit of battery!
Click to expand...
Click to collapse
This is not something I have ever encountered myself. "push" relies on the server to trigger something - in airplane mode, this trigger can't happen.
These things seem strange to me. My impression is that Android is not really optimised for cell phones. If the screen is off, there is no need for CPU time, doesn't it? There is nothing urgent to do; everything could be done slowly; no hurry.
I guess the battery could last *much* longer if this would be improved.
Greetings,
corcov
Click to expand...
Click to collapse
Android is well optimized for cell phones - However, it assumes that third-party applications follow Google's recommendations for power management. Unfortunately, many of them do not. The number of IM applications which choose to use their own proprietary and poorly optimized network protocols (such as Skype, it's atrocious) as opposed to Google C2DM (optimized and efficient) is astonishing.
An interesting note was that I believe much of the focus at Google I/O was on reminding app developers that they need to play nice with the system and other apps.
There are some cases where there are device-specific nonoptimalities. Compared to most Nexus devices, Exynos devices have an absurdly long time to resume from wake (1000 milliseconds), and during that resume cycle CPU frequency is locked to 800 MHz and cpuidle is disabled. This is one of the #1 causes of power drain on our device. This is also exclusively a Samsung kernel/hardware architecture problem that does not affect the Nexus S (similar CPU, but completely different modem interface) or the Galaxy Nexus (different CPU/modem interface).
In the case of our device, the modem is hung off of the CPU on a USB bus - this makes for very long resume times.
Here are obvious reasons the CPU should occasionally turn on when the screen is off:
1) MP3 playback in the background
2) Handling of background syncs - e.g. when an email or Google Talk IM comes in, wake the CPU, handle it, and pop a notification sound, then go back to sleep. Normally, this means the CPU sleeps while waiting for an interrupt from the WLAN chipset or the cellular radio. Unfortunately, some apps drive incoming data to the device far too frequently. (See my above rant about Skype's network protocols being crap compared to Google's C2DM protocol.)
3) Handling of scheduled wakeups (alarms, calendar events, etc) - these are rare and almost never consume power
Most power drain is from item 2, with third-party apps frequently behaving extremely poorly compared to Google's own application suite and sync protocols.
Now this an extensive answer which is very informative and helpful for me since insights are always soothing. Love it. Thanks!
not much to add after Entropy, but if you feel the need to get some control over battery usage you could try betterbatterystats app (and the thread) to identify battery eaters, besides that, there are few apps to check what is going on with your system when it sleeps:
- CPU Spy to show cpu states time
- Autorun Manager or Autostarts to disable triggers causing apps like FB to run without reason (those which you will find with betterbatterystats)
- Battery Monitor Widget, to check battery current consumption (mA) - this app is generally not recommended, because Note's hardware does not report the actual current, so the readings are highly estimated and because when poorly configured it can drain your battery faster, BUT otoh with refresh rate set at 5 minutes or more, it can give you some approximate orientation on how much battery you lose (better than counting %/hour by yourself) at negligible battery usage
- also, if you feel the need to disable net and sync during night, you could automate it using "lama", which is free, and in my experience does not eat much battery by itself
- and last but not least, avoid taskillers, those apps may have adverse effect, i.e. self restarting apps (by the triggers mentioned above), will get killed then restarted and so on and so on, leading to much higher battery drain
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?
Hi, so I've had my G2 D800 model for a while (about a year or two), and for the most part, it's been an excellent phone despite being 3 years old now. Never had any slowdown problems, and it's always performed well in games and in general.
But just recently, about a week ago, it just started lagging out and being very, very slow.
For example, if I'm watching a YT video through the app, if I rotate the screen, it takes maybe 5-8 seconds to actually rotate. Also, in a lot of circumstances where the keyboard has to pop up, it just freezes the app until the keyboard pops up maybe 10 seconds later.
It's also just laggier in general in most apps, scrolling through FB or Twitter freezes nearly every second when I'm scrolling. It's generally unresponsive and sometimes just freezes outright. It also acts this way on the homescreen, and in most everything else.
The most annoying part, however, is that sometimes the devices just doesn't turn on for sometimes up to 15 seconds after pushing the power button (and it usually just refuses to turn on when using my knock code).
The odd part, however, is that once it's actually in something like a game, it performs perfectly fine.
I've played a number of Cardboard games, as well as games like Nova 3, and it performs perfectly.
I've also ran multiple benchmarks (Geekbench, 3DMark, etc), and it scores around where it should.
Info about the device:
LG G2 D800
Stock Lollipop 5.0.2
Software Ver. D80030f
Kernel Ver. 3.4.0
Rooted
TWRP Recovery installed
XPosed Lollipop installed
G3 Tweaks installed, a number of tweaks applied
Everything else is stock (homescreen, etc)
What I've tried/checked:
Checked memory usage during "lag sessions", rarely dips below 300mb free
Changing minfree values through Rom Toolbox (tried every preset, as well as setting everything to the max to free as much as possible)
Rebooting (affects nothing)
Checked CPU speed with Rom Toolbox (is at max, and does achieve the max speed of 2265 MHz. Setting it to performance mode/setting the min speed to be 2265 MHz has no effect, but reduces battery time)
Changed default cache sizr (tried every preset from 128kb to 4096kb. With multiple benchmarks, the optimal value for r/w bounced between 512kb and 4096kb, currently on 4096)
Things I have not tried (that I am aware would possibly have an affect):
Changing anything in the kernel tweaks/build.prop
Completely wiping, reformatting, and reinstalling (I really would rather avoid this if possible, as it would take a while to get everything back to what it is now, and it was a pain to upgrade to Lollipop in the first place)
I am unaware of anything else I could try to fix it, which is why I'm here
So, does anyone know of any other solutions or things to try? This has made my phone very unreliable, even for phone calls and messages, which is a problem.
Thank you for your time and help!
Jtpetch said:
Hi, so I've had my G2 D800 model for a while (about a year or two), and for the most part, it's been an excellent phone despite being 3 years old now. Never had any slowdown problems, and it's always performed well in games and in general.
Click to expand...
Click to collapse
Hi,
First thing i need you to try out is this custom kernel : http://forum.xda-developers.com/lg-g2/development/lp-5-0-2-kernel-3-4-107-dorimanx-1-0-lg-t3102512
Then install greenify, and hibernate all the unnecessary apps.
This should solve the issue.
iubjaved said:
Hi,
First thing i need you to try out is this custom kernel : http://forum.xda-developers.com/lg-g2/development/lp-5-0-2-kernel-3-4-107-dorimanx-1-0-lg-t3102512
Then install greenify, and hibernate all the unnecessary apps.
This should solve the issue.
Click to expand...
Click to collapse
Thanks for the quick reply!
I'll try out greenify, though there aren't many unnecessary apps running (i uninstalled all the bloatware first thing, when I rooted).
And about the custom kernel, it's something I've never tried, so I have a couple questions.
Will it wipe my device, or break TWRP, root, or Xposed? (Sorry, didn't see the answer on that forum)
Will a TWRP backup I make be able to fully restore my device to it's current condition?
Is everything that is supported on my device be supported with that kernel? (Apps, etc. Don't know a whole lot about how kernels work, so I don't know)
Thank you!
Jtpetch said:
Thanks for the quick reply!
I'll try out greenify, though there aren't many unnecessary apps running (i uninstalled all the bloatware first thing, when I rooted).
And about the custom kernel, it's something I've never tried, so I have a couple questions.
Will it wipe my device, or break TWRP, root, or Xposed? (Sorry, didn't see the answer on that forum)
Will a TWRP backup I make be able to fully restore my device to it's current condition?
Is everything that is supported on my device be supported with that kernel? (Apps, etc. Don't know a whole lot about how kernels work, so I don't know)
Thank you!
Click to expand...
Click to collapse
Hi,
Even you uninstalled bloatware, the apps you use daily could be running in background and taking all those rams. So whenever you play a game or dont use a certain app, just go to greenify and hibernate. Since you have xposed installed, you can do more than that such as u can stop sync , etc.
About the kernel, it has a ram management settings and cron task.
Ram management dont need to be altered. It has some preset profile so if you seek performance, just choose performance or if u need battery , select battery profile etc.
Cron task is useful because it will do alot of things automatically. For example, it will release ram at certain amount of time from the apps , it will restart google play service since that could be an issue , etc.
All you need to do is take a nandroid backup just to be safe. Then download Dorimanx Ota from playstore and it will detect ur device and show u which version of kernel is available. Then download that, go to recovery, flash it, and you will see three app installed : Synapse -- will give you all the details of ur setup including cpu speed, temp etc for monitoring purposes
Dorimanx settings - this is the main settings of the kernel. You will see a P icon on top, tap it and choose your desired profile.
Color management : It is as the title says, just leave it be.
Then use your device, check your ram and report back. Hopefully it will resolve your issue.
Wow. Dorimanx did a lot more than I was expecting.
Downloaded the app, downloaded the kernel, flashed it no problem, went through and checked out synapse.
Went into the Dorimanx settings, and set it to the "Performance" profile.
Immediate improvement.
The whole phone seems a lot more snappy, and I switched back and forth between a 1080p60 YT video, facebook, and twitter with absolutely no problem.
Free memory when idle (no apps open) stays around 1gb; it used to be about 500mb before.
Tested a few games for the heck of it, and it actually seems to have improved game performance somehow. (It seems to have overclocked my CPU to 2.5ghz, though, so that makes sense.)
Temps stayed at around 58-60c while running a few Cardboard apps, so it seems fine.
Thanks for the help iubjaved! This has fixed my issue and then some! Ah, the wonders of the Android dev community.
Jtpetch said:
Wow. Dorimanx did a lot more than I was expecting.
Downloaded the app, downloaded the kernel, flashed it no problem, went through and checked out synapse.
Went into the Dorimanx settings, and set it to the "Performance" profile.
Immediate improvement.
The whole phone seems a lot more snappy, and I switched back and forth between a 1080p60 YT video, facebook, and twitter with absolutely no problem.
Free memory when idle (no apps open) stays around 1gb; it used to be about 500mb before.
Tested a few games for the heck of it, and it actually seems to have improved game performance somehow. (It seems to have overclocked my CPU to 2.5ghz, though, so that makes sense.)
Temps stayed at around 58-60c while running a few Cardboard apps, so it seems fine.
Thanks for the help iubjaved! This has fixed my issue and then some! Ah, the wonders of the Android dev community.
Click to expand...
Click to collapse
No worries, happy to help. I gave you advice based upon my experience using all those .
Feel free to post in XDA if you need any sort of help, you will find many that will give you insights and stuff to solve your issue.
GL :good:
So, as the title says, there may be a way to prevent your device from freezing due to unlocked bootloader. Here are 2 things I've discovered:
1) Most of you may already know of this: If you switch off cores 3 and 4 of your CPU in the app Kernel Adiutor you can prevent the freezing issue. However, you lose half your CPU power, and if you leave it that way for long you can't switch those cores back on for some reason, and you'll have to reboot your device(else your battery will drain out if left as is, from my experience), so it's quite a cumbersome task.
2) If you play games that require little more than average ram and CPU power(even games like hill climb) your phone won't freeze while playing. I play this game called Vainglory, and after having played for over 10 hours, I can say for sure it didn't freeze even once.
From these two things I can draw up a vague conclusion that the phone freezes when the CPU isn't doing anything much. When we switch off 2 cores, the workload increases on the CPU, this making it busy(which also leads to quick drain). Same goes for gaming.
So how do we work on that? I'm not sure. Anyone have any ideas? Maybe someone can create a kernel compatible with RR and other cm13 roms which has what's needed. Or maybe try a different CPU governor? Well, just wanted to put it out there.
I tried all what you're trying to do and I understand that. The thing is that it will freeze no matter what.
Of course you can try but don't expect too much.
Goodluck!
I am facing this same issue suddenly
there is no connection between ifwi and cpu core
paktepu said:
there is no connection between ifwi and cpu core
Click to expand...
Click to collapse
Who said there is?
Another thing I found:
When you use kernel adiutor to switch off cores 3 and 4, and use your phone normally, the instant when your phone would have frozen if it weren't for the app, is when your phone gets much slower suddenly. At this point, you'll no longer be able to switch those cores back on, and only a reboot will resolve that.
I've mentioned this so-called "method" of preventing Z5 freeze long ago. I can confirm that switching off cores 3 and 4 somehow halts the phone's urge to freeze. I could've lived with limiting my "power use" as I'm not really a fan of entrusting your phone with large tasks. However, what turned me off was that disabling either one of cores 3 and 4 also disables the camera somehow (Ring a bell, Z5 users who lose their cameras whenever their bootloaders are unlocked?)
No one really replied with certainty back then and up to now, that thread is still collecting cobwebs.
Question: is battery drain a characteristic of disabling cores? I disabled only core 4. Cores 1, 2, and 3 are up and my ROM (Lineage 14.1) runs perfectly without freezing.
I may have discovered a way to make Shield Tablet very smooth and stable very consistently. I don't have the technical backing for it - im just a regular user doing trial and error. I hope it helps the others who want to keep this awesome Device live up to its potential...longer.
So here's my Device setup:
- Shield Tablet US-LTE
- using stock 5.4 debloated for K1 by Sh0X31 for K1 (yes, it works well with my us-lte as long as you don't care about system updates and stylus app)
- rooted via magisk
- Xposed framework
- Nova launcher
Using the ROM as it is significantly improved the performance of the device compared to stock 5.4 for US or RoW LTE. But the sluggish experience Everytime the device wakes up from deep slumber, or connects to WIFI for the first time, is still there. Using Antutu system monitor on the notification panel, I could correlate the sluggish performance with the CPU hitting above 94%. That happens 99% of the time so I suspected that most of the persistent sluggish performance is a CPU issue rather than a RAM issue. So I looked for a way to pinpoint which apps are hogging CPU operations, and hopefully discover what triggers it.
I tried enabling CPU usage in Developer's Options but alas, it could only show com.android.systemui so nothing much can be done from there. I understand this is a bug in Android 7 and it was supposed to be fixed on 7.1 but we all know Shield Tablet is stuck at 7.0 for now.
Next I tried checking out Running Services, still in Developer's Option. So I saw a lot of apps there that seem to be hogging CPU - Malwarebytes, ShareIt, Antutu, Google Services, etc. I uninstalled Malwarebytes and ShareIt but the CPU was still operating at 94% and it takes the device a few seconds to respond to my inputs.
Finally, I noticed these Nvidia-specific processes - these few KBs of operations particularly the ones for OTA upgrade and Media as well as Nvidia -customize (something like that). I forced them to stop and voila! My device CPU suddenly calmed somewhere between 30-50% and as expected, it's operating smoothly and snappily.
When I rebooted, those Nvidia processes naturally became active. I suspect that it's probably part of the device startup process. And as expected as well, whenever they're present the device is expected to go sluggish at some point before its CPU can calm down again.
So now, it's been 2 days and my CPU operates between 18-54% on normal operation, sometimes hitting 80% when I transfer files or play games. But it has NEVER gone sluggish, not even once (waking from deep slumber, connecting to WIFI, etc). I'm very satisfied and back to enjoying my Shield Tablet.
DISCLAIMER: I don't have proof that this is indeed the solution. I can't explain it technically as well. Hoping someone with more knowledge on system process can enlighten us. One thing I'm convinced though is that the sluggishness we all experience comes from NVIDIA-specific processes. I make this inference from my observation that having AOSP ROMs make the device smooth consistently. But I don't like any other custom ROMs coz I need the controller support for the tablet. I hope I make sense and hopefully this could help some Shield Tablet Fans. Sorry for the long write up.
Thanks for the post! If you want to try and dig deeper into this, consider using Tasker, I believe it can be used to make those force stops automatic on start up. Good luck!
fpozar said:
Thanks for the post! If you want to try and dig deeper into this, consider using Tasker, I believe it can be used to make those force stops automatic on start up. Good luck!
Click to expand...
Click to collapse
Thanks for the TIP. I've checked it out in Google Play, the paid version listed what it can do. Need to study if it can disable those mentioned process at startup.
I really wished Nvidia would finally make it's firmware documentation open to the public.