it is true that pegasusq is more aggressive in this version.
and it doesn't like to be watched.
What did you mean with "doesn't like to be watched" ?
Hmmm, i found some other problem with pegasusq: i set it as governor (in setcpu and extweaks), and i did watch But first second core stays off, even if benchmarking or somewhat. If i set 2ndcore app to all cpu on, core goes online and stays online. After a reboot, it seems that phone starts more slowly than normal, i looked and second core is off...
Thats not really more agressive
---------- Post added at 12:34 PM ---------- Previous post was at 12:32 PM ----------
Quote:
Originally Posted by nihilista
What did you mean with "doesn't like to be watched" ?
Hmmm, i found some other problem with pegasusq: i set it as governor (in setcpu and extweaks), and i did watch But first second core stays off, even if benchmarking or somewhat. If i set 2ndcore app to all cpu on, core goes online and stays online. After a reboot, it seems that phone starts more slowly than normal, i looked and second core is off...
Thats not really more agressive
I'm imagining that "doesn't like to be watched" means that if you're running an app to view on the screen the state of the CPU, that app will itself require more CPU resources and make the 2nd core kick in (or keep online).
Perhaps leaving the device idle (even with the screen on, on the homescreen) might allow the 2nd core to go idle as it's no longer updating status bars every second.
---------- Post added at 12:34 PM ---------- Previous post was at 12:32 PM ----------
I'm imagining that "doesn't like to be watched" means that if you're running an app to view on the screen the state of the CPU, that app will itself require more CPU resources and make the 2nd core kick in (or keep online).
Perhaps leaving the device idle (even with the screen on, on the homescreen) might allow the 2nd core to go idle as it's no longer updating status bars every second.
OK, but this behavior is only seen with pegasusq, and - tested it another time - after reboot only one core and slow phone....
If you have no problems with v4.0 you don't have to download and install v4.0.1.
Even though I say this I am sure most of you will download and install anyway
the only change is the init binary and one-line change in init.rc
What did you mean with "doesn't like to be watched" ?
Hmmm, i found some other problem with pegasusq: i set it as governor (in setcpu and extweaks), and i did watch But first second core stays off, even if benchmarking or somewhat. If i set 2ndcore app to all cpu on, core goes online and stays online. After a reboot, it seems that phone starts more slowly than normal, i looked and second core is off...
Thats not really more agressive
So you use setCPU, 2ndcore app and ex tweaks?
3 apps that basically all do the same and you wonder about hiccups? :screwy:
I can not download anything after installing this kernel to Codeworkx's latest 4.1.1 JB. e g. Can not download new update of this kernel from OP link. Same was with 3.5.2 but at that time i thought i messed up something.
Any way to fix this out i am the only one with this problem?
Sent from my GT-I9100 using xda app-developers app
I can not download anything after installing this kernel to Codeworkx's latest 4.1.1 JB. e g. Can not download new update of this kernel from OP link. Same was with 3.5.2 but at that time i thought i messed up something.
Any way to fix this out i am the only one with this problem?
Sent from my GT-I9100 using xda app-developers app
if you have latest JB zip file on your phone you just need to reflash it & google apps package to get back to stock JB state without losing anything.
Not too long ago, we talked about how Sony was continuing its AOSP efforts on … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?