Firstly, I do realize that the SetCPU profiles over ride the profiles that I set up in OC Daemon. What I'm curious about is if the absence of a profile in SetCPU (I've turned off my SetCPU profiles) trumps the presence of a profile in OC Daemon? i.e. SetCPU isn't running a screen off profile so it doesn't let OC Daemon run it's screen off profile?
Reason for asking; I haven't frozen/uninstalled SetCPU because I want to use it to monitor time in state, at least for the time being as I've installed OC Daemon.
If the above is not effective are there any other apps that I can use to monitor time in state?
Thanks,
Noob.
EDIT: for the meantime I've frozen SetCPU to avoid any conflicts.
Just found cpuspy; time in state all good.
Installing any voltage control apps like SetCpu will completely disable OC Daemon. Absence of profiles in SetCpu won't trigger/activate OC daemon profiles. Like you, reason why many people prefer OC daemon more is because it is more responsive since it's not an app.
If you want to change frequencies without deactivating OC daemon, use this Daemon Controller Tool
http://forum.xda-developers.com/showpost.php?p=16015003&postcount=43194
And yes! Cpu Spy is the best app to monitor time states because it monitors deep sleep too.
Thanks, I failed to mention that I do have the controller as well.
I was hoping to add this to a version of the ROM I'm on that did not come with it. I took the files from a different version of the ROM that is identical in every way with the exception of the OC Daemon functionality.
I placed these files in the following locations:
-virtuous_oc folder to system/etc
-74-OCDaemon to system/etc/init.d
-virtuous_oc file to system/xbin (I notice this file references the sh file in system/bin)
I'm able to change the processor values via the controller and they're recorded in the max/min files in the virtuous_oc folder. They're not being applied however; my time in state is indicating that only stock values are being applied. 1200 max 200 min regardless of what values I set in the controller.
That said, I'll do some more searching to see what my issue might be, and not stress about it too much since a new version of the ROM will be released shortly. Regardless, I know a little bit more now than I did yesterday, so it's not a complete failure
When you installed SetCpu, obviously your daemon was deactivated. I'm not sure if it gets re-activated on uninstallation of setcpu.
Have you checked sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
What are the max and min frequencies there?
Is there anyway to incorporate undervolting with OC daemon..also what is the difference between the two governers OC daemon using..
Thank you
droidphile said:
When you installed SetCpu, obviously your daemon was deactivated. I'm not sure if it gets re-activated on uninstallation of setcpu.
Have you checked sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
What are the max and min frequencies there?
Click to expand...
Click to collapse
Here are those values:
1600mhz: 1400 mV
1400mhz: 1300 mV
1200mhz: 1250 mV
1000mhz: 1175 mV
800mhz: 1050 mV
500mhz: 950 mV
200mhz: 950 mV
100mhz: 950 mV
I had SetCPU uninstalled during my latest trial and with OCD Im still limited to stock values (uninstalled SetCPU reboot, install the OCD files/folders, reboot). No issue with OC or UC when I run SetCPU profiles however. Seems like permissions are missing somewhere in the mix (?).
Sent from my MicroTAC 9800X using speech to fax modem
kba712 said:
Is there anyway to incorporate undervolting with OC daemon..also what is the difference between the two governers OC daemon using..
Thank you
Click to expand...
Click to collapse
mudferret said:
Here are those values:
1600mhz: 1400 mV
1400mhz: 1300 mV
1200mhz: 1250 mV
1000mhz: 1175 mV
800mhz: 1050 mV
500mhz: 950 mV
200mhz: 950 mV
100mhz: 950 mV
I had SetCPU uninstalled during my latest trial and with OCD Im still limited to stock values. No issue with OC or UC when I run SetCPU profiles however. Seems like permissions are missing somewhere in the mix (?).
Click to expand...
Click to collapse
Guys, I have a good news for you :
Stop tearing your hair out !!!
Time to leaving SetCPU to try another apps.
IMO, the best combo is : Voltage Control (UV/OC) + O/C Daemon
Runs like a F1. It's worthy to give a try !
^that's exactly what I was trying to do, my issue is that OCD is not working for me, even with SetCPU uninstalled. I'm missing some key part of it; unsure what, as I mentioned earlier in this thread I hold my n00biness close to my heart
I still use SetCpu because i'm lazy
No governor that has inbuilt profiles (especially screen off) like smartassv2,ondemandx guarantees that the cpu doesn't jump to a higher frequency when phone is idle. So, i'm a setcpu profile freak!
Btw, virtuous_oc folder default permissions (i think) are
xxx
x0x
x0x
Funny you should mention that. Turned off my screen off profile last night and got my least drain ever.
Sent from my MicroTAC 9800X using speech to fax modem
Related
Using this kernel is at your own risk. Before flashing make backups!!!
Hey guys, remember this thread?
http://forum.xda-developers.com/showthread.php?t=952365
well, we can not do it for Ecliar, but OK for Froyo, any body want to taste this?http://sugwacee.dyndns.org/
there are two files for this:
NC_stock_1.2_update_sqlite.so.zip is the updated sqlite.so(no sync version), performance boost, cos sync write in high frequency is not needed. with this version sqlite will only sync write when needed. if no system crash, no data lose,just take it easy.
NC_stock_1.2_restore_sqlite.so.zip is the stock sqlite.so(for recovery, just in case).
Use CWM to flash. enjoy it.
reserve for feedbacks
Have you noticed a performance increase?
likearaptor said:
Have you noticed a performance increase?
Click to expand...
Click to collapse
unlike OC kernel, the perf increase is showed at sqlite sync period, not every moment.
1. performance increase when app install/remove, and when large num of data need to sync into database.
2. save disk(TF) i/o irq, good for system i/o wait delay, and good for TF card too(less write)--only when it is sqlite related.
3. quadrant scores, if you like it.
Flashed the zip, ran quadrant and I got 1264. I wasn't sure what it was before, but it seems fast with apps using the database. Thanks for this find
installed.
Linpack score has dropped from 12's to 10's
Quadrant has bumped up a little from 1630'ish - 1680'ish
Hmm, interesting...
I'm not totally convinced that this device is I/O bound.... But for argument's sake, how does this differ from say...changing the caching strategy in the kernel (for overall I/O performance, not just sqlite?)
Also, this only affects writes correct?
HamNCheese said:
Hmm, interesting...
I'm not totally convinced that this device is I/O bound.... But for argument's sake, how does this differ from say...changing the caching strategy in the kernel (for overall I/O performance, not just sqlite?)
Also, this only affects writes correct?
Click to expand...
Click to collapse
emm... maybe you are right, cache does turn high freq i/o cmd down(sync to ram immediately,and sync to disk when idle).
as i know, only effects write action.
actually i got this .so from moto milestone bbs(same kernel version and system env), then tested and modify it into CWM zip to fit NC.
Just got my gtab the other day. After some XDA upgrades and flashing cm7, I'm not showing any governor selection under cpu settings? I also use Temp+Cpu app to monitor my clock speed and its showing -1mhz constantly with no changes. Everything runs ok, boots no problem, but I'm pretty sure this shouldn't be showing like this.
These are exactly the steps I took-
out of the box booted up, Installed the OTA, checked my info was TNT 1.1 3588, Rooted via z4root, installed clockwork v08, wiped data/factory, cache and dalvik cache, installed cm7n86, booted up.
I'm not new to android but obviously new to the gtab. I'm assuming I did something wrong but not sure what I skipped over if any steps? Any suggestions before nvflashing? Thanks!
If you're running CyanogenMod 7.0.x, then you have pershoot's kernel, which has the correct cpu governor -- ondemand -- already pre-configured. You don't need another governor.
Simply change the MIN and MAX CPU frequencies as needed. The kernel will take care of everything else.
Thanks, but I guess I should have specified more. Not having the governors was a concern as far as them not showing but not for wanting to use the others. I use ondemand for all my devices so that is good to know that it is using that.
For me it's more that it is not showing me what the current cpu frequency / clock speed is. That was one of my ways of telling when an app or something was not acting right. i.e. When I'm sitting on my home screen not doing anything and my cpu is maxed out, then I know something is running when it shouldn't. I still have the cpu % so I can live without the frequency, just not used to seeing my cpu speeds in the negative lol.
btw, is this normal for the gtab/cm7?
The negative CPU frequency is most likely an application bug. Report it to the app author.
Check the correct CPU speed (in kHz) by getting it directly from the kernel:
Code:
$ cat /sys/devices/system/cpu/cpu?/cpufreq/cpuinfo_cur_freq
216000 [I]# system's idle, so the second CPU's been offlined[/I].
[I]
Load the CPU; then,[/I]
$ cat /sys/devices/system/cpu/cpu?/cpufreq/cpuinfo_cur_freq
1000000
1000000 [I]# Both CPUs now operating at 1 GHz[/I].
Instead of the command line, you can also use Michael Huang's SetCPU from Market to check (and set) CPU speed.
Edited
Figured out the answer
When using a kernel that has cpu1 enabled, the cpu1 scaling_governor will be reset to userspace at random intervals. I haven't been able to figure out a pattern for it, but has anyone else noticed this behavior, or have an idea of how to prevent it?
On a related note, the permissions for cpu1/cpufreq on startup are really weird too (440 for scaling_max_freq and scaling_governor), but I can manually fix those after a reboot...
hboot: 1.40
root: revolutionary
ROM: stock 2.08.651.2
kernel: freeza 4a or bcblend 0.03
If any other info would help please let me know. Thanks in advance.
penguinicus said:
When using a kernel that has cpu1 enabled, the cpu1 scaling_governor will be reset to userspace at random intervals. I haven't been able to figure out a pattern for it, but has anyone else noticed this behavior, or have an idea of how to prevent it?
On a related note, the permissions for cpu1/cpufreq on startup are really weird too (440 for scaling_max_freq and scaling_governor), but I can manually fix those after a reboot...
hboot: 1.40
root: revolutionary
ROM: stock 2.08.651.2
kernel: freeza 4a or bcblend 0.03
If any other info would help please let me know. Thanks in advance.
Click to expand...
Click to collapse
very interesting issue...
cpu1 scaling governor reset to userspace at random intervals .. the first guess i'd have would be some 3rd party android app following a predefined profile. of course, this app should need root access to echo out to the sysfs file and if you have superuser installed the app would have had to prompt at least once for permission.
if you don't have any 3rd party app installed echo'n values then the only other common tool i've seen is the settings in CM7, but you stated you're on a stock ROM.
if you're on a rooted stock ROM with custom kernel, sometimes the devs setup support for startup scripts and might be making some type of tweak in a startup script which could also be set to loop and apply some predefined setting.
my guess would be the perms on sysfs files are setup in the kernel config files when its compiled. would be something the kernel dev should be able to change easily. 440 could be intentional as they're trying to limit access .. don't want any random app/binary messing around with the settings
hope some of those thoughts are helpful!
joeykrim said:
very interesting issue...
cpu1 scaling governor reset to userspace at random intervals .. the first guess i'd have would be some 3rd party android app following a predefined profile. of course, this app should need root access to echo out to the sysfs file and if you have superuser installed the app would have had to prompt at least once for permission.
Click to expand...
Click to collapse
Here are the programs with superuser permission:
BusyBox installer
ConnectBot
Kernel Manager Lite
Quick Boot
ROM Manager
Superuser
Titanium Backup
All of these are pretty common, and I doubt any of them would be poking around the governor, but that's why I'm asking after all.
joeykrim said:
if you're on a rooted stock ROM with custom kernel, sometimes the devs setup support for startup scripts and might be making some type of tweak in a startup script which could also be set to loop and apply some predefined setting.
Click to expand...
Click to collapse
Do you know how I could check this? I don't think the kernel has init.d support.
joeykrim said:
my guess would be the perms on sysfs files are setup in the kernel config files when its compiled. would be something the kernel dev should be able to change easily. 440 could be intentional as they're trying to limit access .. don't want any random app/binary messing around with the settings
Click to expand...
Click to collapse
Yeah, definitely makes sense. It was just odd to me that the CPUs were mismatched (cpu0 had 640 permissions for all of those).
joeykrim said:
hope some of those thoughts are helpful!
Click to expand...
Click to collapse
Definitely, thank you.
I've worked around it for now by modifying Virtuous OC to set the perms to 640 before doing its thing, then resetting them to 440 when done. I've also written a daemon that will report when it's changed to userspace in hopes that I can track down some sort of pattern.
penguinicus said:
Here are the programs with superuser permission:
BusyBox installer
ConnectBot
Kernel Manager Lite
Quick Boot
ROM Manager
Superuser
Titanium Backup
All of these are pretty common, and I doubt any of them would be poking around the governor, but that's why I'm asking after all.
Do you know how I could check this? I don't think the kernel has init.d support.
Yeah, definitely makes sense. It was just odd to me that the CPUs were mismatched (cpu0 had 640 permissions for all of those).
Definitely, thank you.
I've worked around it for now by modifying Virtuous OC to set the perms to 640 before doing its thing, then resetting them to 440 when done. I've also written a daemon that will report when it's changed to userspace in hopes that I can track down some sort of pattern.
Click to expand...
Click to collapse
Okay, well given some of your responses I'm going to assume you're a bit more of a technical/advanced user.
All the Android applications you posted with superuser access are very common as you stated. An easy way to check might be, rename /system/bin/su to something else so no scripts or apps can gain superuser access and see if your sysfs cpu1 files are still changed?
If I were you, I'd want to get to the bottom of the perms on the cpu1 sysfs files. Especially since you're saying cpu0 and cpu1 have diff perms set on the sysfs files. Since Linux kernel code is GPL, the kernel dev should have a public link to their kernel files. I'd go look thru their source to find where they're implementing cpu1 sysfs files and check the perms they're setting up sysfs files with. I want to say, the cpu1 sysfs files are something added/modified by the kernel devs so there is definitely potential somebody missed a proper setting.
I'd rather take this approach than have to patch over some poor coding by using another app to adjust the perms on the file.
Can you post the log produced by your daemon on the changes to the sysfs cpu1 file?
Hope that helps!
EDIT: noticed I missed a question, how to check for init.d type support in the kernel. Generally, they're going to have to make a change to the init.rc file in order to add in anything to the start up sequence. I'd grab the stock init.rc file and diff against the currently loaded init.rc file in the kernel being used.
As an FYI, init.rc is stored in the ramdisk part of the boot.img.
Whew, ok. After a lot of observation, I noticed that the reset to userspace corresponded with me putting the device to sleep.
I then tried disconnecting my device from USB and the daemon started crashing, being unable to read the sysfs files for cpu1, which never happened while connected over USB. I switched adb to TCP mode and found that the files were indeed gone, because cpu1 was offline. Apparently being connected over USB kept cpu1 online more often than it would be otherwise. This was causing some weird permission resets too, as the permissions would reset when the core was brought offline and back online.
When cpu1 is automatically taken offline then back online, it seems to be randomly restored with the userspace governor instead of whatever governor it had when it was taken offline. It sometimes gets stuck online, too, even when the phone has been asleep for a long period of time. I still can't get either to happen consistently, however, and I don't know if nobody else is experiencing it, or if it's just gone unnoticed by others.
Enabling and disabling SetCPU seemed to have no effect on the consistency or frequency of the weirdness either. I may mess with my daemon to have it duplicate cpu0's governor to cpu1 when cpu1 comes online but doesn't match, but I have to assume this is just weirdness due to the whole "async cores are new" thing.
Thanks very much for your help, and if anyone else observes anything similar please let me know! D:
penguinicus said:
Whew, ok. After a lot of observation, I noticed that the reset to userspace corresponded with me putting the device to sleep.
I then tried disconnecting my device from USB and the daemon started crashing, being unable to read the sysfs files for cpu1, which never happened while connected over USB. I switched adb to TCP mode and found that the files were indeed gone, because cpu1 was offline. Apparently being connected over USB kept cpu1 online more often than it would be otherwise. This was causing some weird permission resets too, as the permissions would reset when the core was brought offline and back online.
When cpu1 is automatically taken offline then back online, it seems to be randomly restored with the userspace governor instead of whatever governor it had when it was taken offline. It sometimes gets stuck online, too, even when the phone has been asleep for a long period of time. I still can't get either to happen consistently, however, and I don't know if nobody else is experiencing it, or if it's just gone unnoticed by others.
Enabling and disabling SetCPU seemed to have no effect on the consistency or frequency of the weirdness either. I may mess with my daemon to have it duplicate cpu0's governor to cpu1 when cpu1 comes online but doesn't match, but I have to assume this is just weirdness due to the whole "async cores are new" thing.
Thanks very much for your help, and if anyone else observes anything similar please let me know! D:
Click to expand...
Click to collapse
I've noticed the exact same thing on my E3D. I'm running a "clean" custom ROM (CleanROM DE) with a famous third-party kernel (Tiamat Sense 1.1.0). I've also noticed that there is a lot of work in the Sensation forum trying to get the "Dual-Core" mode "unlocked" and that some ROMs have managed to pull it off. I think having a talk with any of these developers (or anyone who boasts "Dual Core" or "dual core patch") would help you get to the bottom of this.
It's extremely frustrating. Even using apps like System Tuner Pro, which have a special option to "force all CPUs active", does not seem to correct the sporadic governor switching back to userspace on the second core.
---------- Post added at 04:33 PM ---------- Previous post was at 04:12 PM ----------
curiousGeorge said:
I've noticed the exact same thing on my E3D. I'm running a "clean" custom ROM (CleanROM DE) with a famous third-party kernel (Tiamat Sense 1.1.0). I've also noticed that there is a lot of work in the Sensation forum trying to get the "Dual-Core" mode "unlocked" and that some ROMs have managed to pull it off. I think having a talk with any of these developers (or anyone who boasts "Dual Core" or "dual core patch") would help you get to the bottom of this.
It's extremely frustrating. Even using apps like System Tuner Pro, which have a special option to "force all CPUs active", does not seem to correct the sporadic governor switching back to userspace on the second core.
Click to expand...
Click to collapse
Oh. HTC's doing. My bad.
http://forum.xda-developers.com/showpost.php?p=17456447&postcount=7630
Of course, flashing this sucker could cause you to wind up with a bricked phone. Beggers can't be choosers. Now I'm off to flash Synergy. *sigh*
WOW, thanks for this info. That makes a lot of sense actually, I notice blazing performance for the most part on tiamat 1.1.0, and then out of nowhere it's slow as balls. Reboot *seems* to fix. I guess it's stock for me with a modified ramdisk, no OC, but that's cool. The shooter is pretty damn quick.
If any of you folks come up with something that corrects the userspace gov issue and perms, please post, I would like to use it. Thanks again.
Was having the same issue, looked all over and found a solution
http://forum.xda-developers.com/showpost.php?p=17456447&postcount=7630
Keep in mind these are flashable solutions as long as you stick with the same scaling_governor. Its been said to have both cpu's running same one.
Set CPU for some reason is no longer working for me. My settings wont stay set on boot. I'm looking for another overclock option, I'd like to also have profile management for off screen and temp, etc... thanks
If you want profiles, I know of no other voltage programs for the Galaxy S that have them besides SetCPU. For voltage control, we have Pimp My CPU and Voltage Control apps. Both were built with the Galaxy S series in mind.
You may want to simply uninstall/reinstall SetCPU first to see if that fixes your problem. Also, what ROM are you on? If memory serves, I had a similar issue back when I used Project V.
I've tried uninstalling and reinstalling several times. Reflashing the kernel wiping data, cache etc.. I'm on bi winning v3. The problem started when i tried tegrak overclock. Just wanted to give it a whirl, didn't like it and when i put set CPU back on the settings wouldn't stick.
maybe try romtoolbox. it allows you to designate max and min clock speeds as well as the governor. unfortunately no profiles are supported but the app is in the market and has a lot of helpful features with anyone with root access that is on a custom ROM.
Hello for all! :good:
Sorry my english...:cyclops:
Well, i have a low cost tablet, less of 100 bucks, AOC MID 7y2241. It have Amlogic (mason 6) Dual Processor set in 1.2Ghz and 1 GB RAM, GPU Dual Mali 400, running Jelly Bean 4.1.1 :highfive:
It can run all games in excellet performance if... dont sleep. Take easy, i can explain:
Yeah, i dont know why, but, when tablet turns on, he play everything very well. But, if the screen lock and sleep for 5 min or more, the tablet shows me so much lag and low performance after wake up. Just way to back to good playing is restarting device.
I think the problem is the power saving or a seriuos bug, but i not sure. This tablet is set up in conservative mode, and i cant change it. Really, i cant change nothing relative of CPU. I already rooted device with kongo, it works really good! But any apps of overclock dont works in this device. Give root permission, you set, but nothing happen.
I try change manually sys directory (cpufreq), with adb shell, but is same. I give permissions to rw, but the device return me ALWAYS operation denied.
Well, i like to know if is possible write in sys directory. I try for adb and rooted file explorer, but always is operation failled or denied. If this low performance after sleep is a bug, how to fix or if change the governor can help me in this case?
I cant wait for updates... maybe this tablet never see other android version. I cant change image files and rom, cause i cant do backup in this device. Need a solution for compiled kernel.
Seens it is not a particularity of my device. All AOC MID 7y2241 shows this same problem (but only me realized.). Everyone thinks this tablet is slow, but it can run heavy apps and games easily (before first sleep).
Pls, a really need some help (more than 5 days searching and nothing...)
*********************************************************
News: When device restart, 2 cores are working. After 5 min sleeping (lock screen), just one core work. Nothing do the second core wake up. Just shows stopped in CPU-Z. I think this is the problem. How i can fix?
For god, nobody????
Cmon guys, just 5 min of a genius can libert me of my insanity!!!
7y2241 said:
Hello for all! :good:
Sorry my english...:cyclops:
Well, i have a low cost tablet, less of 100 bucks, AOC MID 7y2241. It have Amlogic (mason 6) Dual Processor set in 1.2Ghz and 1 GB RAM, GPU Dual Mali 400, running Jelly Bean 4.1.1 :highfive:
It can run all games in excellet performance if... dont sleep. Take easy, i can explain:
Yeah, i dont know why, but, when tablet turns on, he play everything very well. But, if the screen lock and sleep for 5 min or more, the tablet shows me so much lag and low performance after wake up. Just way to back to good playing is restarting device.
I think the problem is the power saving or a seriuos bug, but i not sure. This tablet is set up in conservative mode, and i cant change it. Really, i cant change nothing relative of CPU. I already rooted device with kongo, it works really good! But any apps of overclock dont works in this device. Give root permission, you set, but nothing happen.
I try change manually sys directory (cpufreq), with adb shell, but is same. I give permissions to rw, but the device return me ALWAYS operation denied.
Well, i like to know if is possible write in sys directory. I try for adb and rooted file explorer, but always is operation failled or denied. If this low performance after sleep is a bug, how to fix or if change the governor can help me in this case?
I cant wait for updates... maybe this tablet never see other android version. I cant change image files and rom, cause i cant do backup in this device. Need a solution for compiled kernel.
Seens it is not a particularity of my device. All AOC MID 7y2241 shows this same problem (but only me realized.). Everyone thinks this tablet is slow, but it can run heavy apps and games easily (before first sleep).
Pls, a really need some help (more than 5 days searching and nothing...)
*********************************************************
News: When device restart, 2 cores are working. After 5 min sleeping (lock screen), just one core work. Nothing do the second core wake up. Just shows stopped in CPU-Z. I think this is the problem. How i can fix?
Click to expand...
Click to collapse
uninstall apps you wont use and also
try clearing cache you can do so by finding at play store :angel:
Thanks so much for coop!
Hell_X said:
uninstall apps you wont use and also
try clearing cache you can do so by finding at play store :angel:
Click to expand...
Click to collapse
**********************************************************************************************
Man, i really really apreciatte your iniciative. Thank you so much! I dont give up yet...
I already do a factory reset, cleanning cache, using Power + Up Button. And not work... Maybe you want said other thing, maybe?
I pass last days broken head in this S.O, and seens a bugged kernel. The tablet boot, and 2 cores working. When 5 min pass by (standby), the cpu 1 is setted off line, and dont wake up again until restart. In I9100, the core wake up frequently, according to demand. But in this case, it dont wake anymore...
When the tablet boot, In "cpu1" folder (in sys/devices/system/cpu/), there is a shortcut of folder "cpufreq" contained in "cpu0" folder. When pass 5 min in standby, the cpu1 is setted like offline, and this shortcut (cpufreq folder in cpu0) is deleted, together with folder "topology". When force wakeup cpu1, just folder "topology" backs. In short, the shortcut of "cpufreq" folder in "cpu1" folder no back anymore.
I think that cpu1 stays without freq control, cause system tuner apps shows the cpu1 like online (just when force wake up), but without freq, just shows n/a.
I really really apreciate a solution for this problem. No one apps can do anything usefull.
For hour, this table have a 4000mah battery, so, i dont matter if i can disable hotplug cpu function. I prefer let 2 cores working that let it cpu1 in offline.
All apps that give tweak "all core enable" in boot dont work (rooted). I need a way that prevent the cpu1 to be setted offline permanently when in standby (lock screen), to avoid first offline set in cpu1.
Something to do with your cpu governor not scaling properly on wake up. Download No-frills CPU Control from playstore. You can read about this app in here.
Try setting the cpu governor to interactive (if none, ondemand) and i/o scheduler to sio (if none, noop or deadline). You can also adjust the min/max frequencies of the stock values.
Yet trying!
Hello!!!
Thanks god, somebody reply me! :victory:
So, how i said, noone apps in google play works (rooted) in this tablet. The No Frills was the first that i try. I click apply, but the config dont change (rooted!).
Is a total root. No this problem. I think that cpu Amlogic have some limitations. Maybe the energy controller is very limited, cause i cant change freqs, governors and I/O (any apps). Just have "conservative" (default, i cant change) and "performance2" (i cant set) governors. Exists "performance", but not have config options (is like no exists).
Or, maybe, the kernel of this android version no able this changes (in this case, i have hope).
I think I/O dont go work here (disk scheduler). What i want is prevent cpu1 set offline, maybe disabling hotplug control?
I discover that this cpu set auto offline cpu1 after 40 ~ 50 min playing heavy games (for sure, high temps...). Certainly, the power manager of cpu Amlogic meson6 is very useless.
If somebody know how disable it in kernel options (maybe uninstalling drivers?), it would be amazing :highfive:
Reviving topic...
Reviving topic...
Reviving topico again...
Reviving topic again... :crying:
7y2241 said:
Reviving topic again... :crying:
Click to expand...
Click to collapse
Claim warranty!
It is s SW Problem ... Iam developing a custom kernel for a Ventos 7 HD ( has the same CPU) it has the the same problems. I fixed it by comparing many meson6 kernel sources. You will need a custom kernel.The Original Amlogic Kernel is very buggy .The CPU can reach 1.5ghz without problems but it is not active in most kernels for Amlogic.Also the CPU1 down is a known Problem , this happens often after a suspend.
Try to find the kernelsource for the device.Maybe i can help you then.
Sent from my LG-P990 using XDA Free mobile app