hi all,
i postet in the thread of my overclocking tool that i have problems with the StabilityTest tool.
inteks said:
inteks said:
i have a prob with overclocking maybe anyone has an idea ....
when my defy is a long time off the phone cools down to i.e.23°C (stabilitytest shows temperatur) then it crashes with even [email protected]
if i repeat the test and the phone temp raise to 28°C it ist stable with [email protected]
same prob with vsel1&2
is it better to overclock only on a given temp
OR
use higher vsel below a given temp
/inteks
Click to expand...
Click to collapse
after a week of research i found the problem.
jit for 2.1 is not so stable as it looks. i was up to 74vsel for 1100 and i still got crashes sometimes. i revert back to the orginal libs without jit and till now it runs stable with 58vsel for 1100
if some else want to unJit his 2.34CE i attach an update.zip with the orginal Libs
install via recovery
Click to expand...
Click to collapse
so i contactet the autor of this tool because i can unJit the 2.1 FrozenEclair but i have the same problems with CN2.2.
he pointed me to this thread ->
http://code.google.com/p/android/issues/detail?id=10942
and it looks like the Defy (and other devices) are simply not Jit compatible
so if you like it really stable (i do) you disable jit on froyo. or is it fixed on the new UK version ???
/inteks
inteks said:
hi all,
i postet in the thread of my overclocking tool that i have problems with the StabilityTest tool.
so i contactet the autor of this tool because i can unJit the 2.1 FrozenEclair but i have the same problems with CN2.2.
he pointed me to this thread ->
http://code.google.com/p/android/issues/detail?id=10942
and it looks like the Defy (and other devices) are simply not Jit compatible
so if you like it really stable (i do) you disable jit on froyo. or is it fixed on the new UK version ???
/inteks
Click to expand...
Click to collapse
I am running 2.2US and I believe JIT is on by default right? Anyways, running @1100mhz/56Vsel without any problems.
When i have the 2.34 Blurless ROM with 2.34 JIT all work fine no bug .
I don't undersatand why JIT on Android 2.2 is bugger if it is all Android phone with Froyo have a bad issu .
Try a full WIP and try to flash with an other computer, i have a bad issu because my RAM on my computer is corrupt .
@madlive
i have this problems only sometimes with stabilitytest and a few other apps
it runs stable most time with vsel of [email protected] but stabilitytest crashes sometimes even with default values!
@mick711
it has somethings to do how the cache works. so it seems hardware related
inteks said:
@madlive
i have this problems only sometimes with stabilitytest and a few other apps
it runs stable most time with vsel of [email protected] but stabilitytest crashes sometimes even with default values!
@mick711
it has somethings to do how the cache works. so it seems hardware related
Click to expand...
Click to collapse
OK then what does the stability tests say after disabling the JIT on froyo?
chaihg said:
OK then what does the stability tests say after disabling the JIT on froyo?
Click to expand...
Click to collapse
after disabling JIT streetest runs stable or throw a errormessage. but not a FC
I'd sooner blame any instablity on overclocking than on a default feature of a ROM.
Running 2.21 FR rom with frozenEclair and jit enabled and I must raise the vsel to get the phone stable. Before, with no jit, I could run stable with this settings:
900 46
600 32
300 22
With jit the phone reboots sometimes.
Sent from my Defy
I think you are misinterpreting the bug report. The conclusion I draw is not that JIT or the Defy in combination with JIT is to blame.
I feel that users have been altering their phone to such an extent that reliable defaults are no longer reliable.
Overclocking is, by definition, increasing the clock-speed of a device to values higher than factory tested stable defaults, which may cause instability.
*update* Hm. Well, since 2.1 is not, by default JIT-enabled, I do agree that it is possible that it may not be default for a good reason.
However, 2.2 - Froyo - does have it as a default feature, so by that token, if you choose to upgrade, JIT should cause no problems.
naenee said:
I think you are misinterpreting the bug report. The conclusion I draw is not that JIT or the Defy in combination with JIT is to blame.
I feel that users have been altering their phone to such an extent that reliable defaults are no longer reliable.
Overclocking is, by definition, increasing the clock-speed of a device to values higher than factory tested stable defaults, which may cause instability.
*update* Hm. Well, since 2.1 is not, by default JIT-enabled, I do agree that it is possible that it may not be default for a good reason.
However, 2.2 - Froyo - does have it as a default feature, so by that token, if you choose to upgrade, JIT should cause no problems.
Click to expand...
Click to collapse
that is NOT a overclocking problem and NOT a eclair problem. this problem also exist on froyo !!!!
on Froyo the problem is even bigger because till now i found no way to disable JIT !!!
on eclair you can disable jit by adding "dalvik.vm.execution-mode=int:fast" at the end of your build.prop
That's odd. Let me run the tool as well and see if I can reproduce your error.
Well, StabilityTest is killed for some reason, but as the phone itself is not unstable, and no other application segfaults/dies/is killed for me, I tend to suspect there is a problem with StabilityTest itself.
I will try to find another tool to stress-test and see what that says. Afterall, another tool should produce the same problem, providing there is a problem with stability, and not a problem with the application that tests stability.
*update* Ah, I see SetCPU has such a feature.
*update 2* I ran the SetCPU stress test for 797943 milliseconds (13.30 minutes), without any stability issues.
Note: I did not alter the voltage of clockspeed of my Defy in any way.
There is a new StabilityTest version on the market that seems to fix this problem.
Then I think we can safely say that JIT is not causing any instability. Case closed
naenee said:
Then I think we can safely say that JIT is not causing any instability. Case closed
Click to expand...
Click to collapse
this new version just disable jit.....
> http://developer.android.com/sdk/android-2.2.html
do a search for 'vmsavemode'
Sent from my MB525 using Tapatalk
Inteks, so what is the difference when you disable jit now?
Sent from my MB525 using XDA App
It strikes me as a bit odd, that a tool designed to test stability, needs to disable an integral part of a system before it can be stable itself.
To me, it means that this test can not be used for stability testing with any phone that without this test running, uses JIT.
i've see other apps that crashes randomly. most off them use native libs.
you can fix it your self by modding the androidmanifest.xml inside the apk.
add "android:vmSafeMode="true"" to the application tag
naenee said:
It strikes me as a bit odd, that a tool designed to test stability, needs to disable an integral part of a system before it can be stable itself.
To me, it means that this test can not be used for stability testing with any phone that without this test running, uses JIT.
Click to expand...
Click to collapse
yepp. but i want to test the hardware runs stable !!!
that jit isnt stable is a known problem, and the test crashes even at default speed before
Related
Hey everyone,
i just read about the SetCPU app on the front page of xda-developers.com
Does this work for Kaiser too? or would it be safe to use it on the kaiser?
thanks nick
the-nj said:
Hey everyone,
i just read about the SetCPU app on the front page of xda-developers.com
Does this work for Kaiser too? or would it be safe to use it on the kaiser?
thanks nick
Click to expand...
Click to collapse
No. Dont...really dont
I tried a few weeks ago, but instead of running my android freezes... :S
Does this overclock the CPU if so this was bad juju sometime last year was causing funky things to happen when overclocking was added to the default.txt
http://ponack.net/poly/oc/
Script must be run as root. 528 is the fastest stable overclock I can achieve. Sometimes OC lockups will corrupt all your data. I don't recommend OCing at boot/system load unless you're really sure about it. I am not supporting OCing or this file. Every system is different, OC your device at your own risk.
polyrhythmic said:
http://ponack.net/poly/oc/
Script must be run as root. 528 is the fastest stable overclock I can achieve. Sometimes OC lockups will corrupt all your data. I don't recommend OCing at boot/system load unless you're really sure about it. I am not supporting OCing or this file. Every system is different, OC your device at your own risk.
Click to expand...
Click to collapse
I've been running ahb_div=4 & a11=500 all day, and it seems to be alright... The only problems I've had is when it's plugged in, as soon as I unplug it while it's asleep it locks up. A soft reset fixes it just fine, but not sure how alarms/etc. will work while its plugged in. maybe just simply waking it before unplugging will be fine.
NOTE: Everytime I reboot the phone, I need to reapply those settings.
polyrhythmic said:
http://ponack.net/poly/oc/
Script must be run as root. 528 is the fastest stable overclock I can achieve. Sometimes OC lockups will corrupt all your data. I don't recommend OCing at boot/system load unless you're really sure about it. I am not supporting OCing or this file. Every system is different, OC your device at your own risk.
Click to expand...
Click to collapse
How do you run this as root? Do I just need to su, then ./oc.sh?
Pandemic187 said:
How do you run this as root? Do I just need to su, then ./oc.sh?
Click to expand...
Click to collapse
That sounds right. You might have to use chmod to make it executable, too.
Even so, I understand you can brick your device doing all this?
Doesn't sound worth the risk. A little bit more speed in trade for instability and risk of bricking your hard-to-replace Kaiser.
aikeru said:
That sounds right. You might have to use chmod to make it executable, too.
Even so, I understand you can brick your device doing all this?
Doesn't sound worth the risk. A little bit more speed in trade for instability and risk of bricking your hard-to-replace Kaiser.
Click to expand...
Click to collapse
Well, I can't flash to NAND - I'm still using HaRET, so I don't think that would be a problem for me.
If you put the script on your SDcard you don't have to chmod it since FAT partitions don't have permissions, the files are all 777. It'll only corrupt your Android data if it corrupts anything, so backup your Android data first. AFAIK no one has actually permanently damaged the Kaiser using reasonable overclocks.
polyrhythmic said:
If you put the script on your SDcard you don't have to chmod it since FAT partitions don't have permissions, the files are all 777. It'll only corrupt your Android data if it corrupts anything, so backup your Android data first. AFAIK no one has actually permanently damaged the Kaiser using reasonable overclocks.
Click to expand...
Click to collapse
After one lockup, my Android data was corrupted. I probably won't be doing this again.
How to use this script?
I copy it to SDCard and open via "Root Explorer" ("Execute" Command).
I see message "oc.sh executed" but in my opinion overclocking not exist.
DmK75 said:
How to use this script?
I copy it to SDCard and open via "Root Explorer" ("Execute" Command).
I see message "oc.sh executed" but in my opinion overclocking not exist.
Click to expand...
Click to collapse
I have to voice a second opinion on this.
I urge you not to do this if you need your phone as a daily user, Th effects of overclocking are minimal at best anyways, the phone not waking up is one of the reasons 99% of us quit using this a very long time ago. I dont think anyone has permanently bricked their phone YET but its bound to happen. I would think that continually reloading a data backup would get very annoying atleast it did for me. I havent overclocked probly close to a year now and see no reason too even running polymods eclair. If your running myns donut there is absolutley no reason to at all. But if you so desire then go right ahead and hope for the best. And to the one that metioned his phone locking up no your alarms won't work if you overclock your phone don't count on its reliability.
is anything dangerous on overclocking Kaiser?
and whaat is max frequency? 528MHz?
Default is 400MHz
garringm said:
I havent overclocked probly close to a year now and see no reason too even running polymods eclair. If your running myns donut there is absolutley no reason to at all.
Click to expand...
Click to collapse
I already use "polymod 2.1g" and this build need to overclock.
But this script cannot make it.
I seen real overclock only on previous versions mssmison`s eclair: system tools shows 507MHz and device works faster than usual.
The script works, your device needs to sleep and wake before it takes effect. If you want to see the quantitative difference download Linpack or CaffieneMark for Android Every device is different, I can OC and everything works fine (99% of the time) but almost everyone else has trouble. Vogues seem to have it easier -- YMMV.
how i can overclock myn donut?
I'm 90% complete on my Android application that overclocks and changes lcd density within Android. It also works on the Kaiser
Stay tuned.
polyrhythmic said:
AFAIK no one has actually permanently damaged the Kaiser using reasonable overclocks.
Click to expand...
Click to collapse
Once I get my native android device in a few months maybe I'll just have to see how durable the kaiser is. a couple more drops or dings in the touchsreen and itll be pretty much useless anyways
So I noticed a number of references in one of the mega XDAndroid threads to overclocking Rhodium. Sounded pretty simple, just a string of text with the desired frequency in a particular file.
A couple of questions for those who toyed with that:
1) was it stable and what was its fastest stable speed?
2) did it run uncomfortably hot?
3) is it possible to alter it on the fly (so you can run it slow when you're reading, and crank it up for video), or do you have to choose a speed preboot and reset to change it?
4) If it can't at the moment, be altered on the fly, might it be possible for some program to do that in the future?
5) finally, why is it so easy on adroid? It seems like no2chem has hit a bit of a wall in making his winmo project hum, but the references here made it sound like a pretty basic task.
Part of the reason I'm asking is flash 10.1 is due for android in Q1. The last I read of CPU requirements had them over Rhodium's specs by a lot. Mobile hulu access would be fantastic, and I'm planning to start dual booting this summer, once classes are done. It'd be nice if my TP2 could eek out enough performance for that.
Thanks
You could try adding this to your Startup.txt acpuclock.oc_freq_khz=650000, thats the one i use and its prettty nice, i havent notice any heating up at all.
devilcuban said:
You could try adding this to your Startup.txt acpuclock.oc_freq_khz=650000, thats the one i use and its prettty nice, i havent notice any heating up at all.
Click to expand...
Click to collapse
It does not sleep to death for you when you do this devil? I had to take the OC out of my rebuilds, because once the phone sleeps, it will not wake up.
Yep same here. If I add that line, once it goes to sleep in Android, it doesn't want to wake up again...
Reefermattness said:
It does not sleep to death for you when you do this devil? I had to take the OC out of my rebuilds, because once the phone sleeps, it will not wake up.
Click to expand...
Click to collapse
On the Hero one it does , on you build even tho its not really need it i've been using it for a while and it doesn't do it .
So interisting thing, it does go to sleep of death, the reason it didnt do it before for me its because i've been using with htc_battery_smem.fake=1, but as son as i disable that it went to sleep and didn't get up.
devilcuban said:
On the Hero one it does , on you build even tho its not really need it i've been using it for a while and it doesn't do it .
So interisting thing, it does go to sleep of death, the reason it didnt do it before for me its because i've been using with htc_battery_smem.fake=1, but as son as i disable that it went to sleep and didn't get up.
Click to expand...
Click to collapse
I did test and confirm this. I think what happens is with smem.fake=1 the phone actually never goes to sleep.... at least the sleep light never turns on. I will have to ask phh if this is the case.
Tried putting the overclock line in Startup.txt but it did not seem to change anything, at least according to the CPU Benchmark app. The battery line did seem to work though, as it thought it was charging even while not plugged in.
Is there a specific order that these parameters need to be added in? I just added the overclock line at the end and the battery one after that.
Using the latest non-sense 2.1 builds.
I'd love to add Rhodium overclocking support to my RogueTools application.
I think there is still a constraint though with write access to /system. I am hopeful that shortly the Rhodium kernel and rootfs developers will deviate out of the current read only SQSH model and go the way of the Vogue, Kaiser and Polaris hosting the system and data in separate EXT2 partitions on the SD Card. NAND would be the next step.
If someone knows another way to overclock on the fly once the system is up (post boot). PM me. Like I said, I'd love to add support for the Rhodium.
so nothing on the OC for 2.1 yet?
bump
I'm about to test overclocking with the SetCPU app. Worked fine on my rooted G1. I'll report back with my findings.
Edit: Did not work with custom and/or multiple devices selected. Can't push any higher than the stock 528. Blah.
on screen keyboard
when i put both sleep fixes and the overclocking cpu command in my startup text i get the on screen keyboard like in rhobuntu. how do i disable this? its not even usable it just lingers there and its very annoying
O.S.K. byebye command is msmvkeyb_toggle=off
OverClocking M2CW & IME
Data corruption is inevitable without running extensive stress testing to find a safe speed. I have yet to find one for msm7k processors, but surely Qualcomm has one. Benchmarking is not the same as stress testing. Such stress testing apps need to be run for several hours & even days. They can't test all functionality accuracy. Stress testing in themselves can cause hardware damage & even catastrophic failure.
Data corruption is often the "silent killer" and goes undetected by you or system checks ... until you need it most. It may be a config file, a message file, a contact database, an executable, a registry hive, a system file. Any non ROM file is vulnerable. Backup OFTEN & NOT while OC, even though BUed corrupted data is still corrupted. Quote "stable speed" isn't such just because device doesn't randomly lock up or reboot.
Every CPU and memory chip has different limitations. Same phones built on same date may not OC the same.
Don't OC when when building new Android data.img file, downloading update files or apps, extracting or creating archived files, installing apps, encrypting or decrypting.
OC doesn't help Project XDAndroid developers. I suspect many "bugs" they spend valuable time on are OC related.
The msm7k processors supported by Project XDAndroid are a speed scaling processor designed for optimum performance vs. battery runtime, ramping up and down the processor speed based on demand. Average device use doesn't utilize full processor speed.
OC is most noticeable in OS boot times (when OC is initialized prior to), certain multitasking operations, some video playback, CPU intensive games, & to a lesser extent web browsing. Many factors determine the effectiveness of OC especially whether graphics are hardware or software supported.
Your OC device may actually perform worse, noticeably more sluggish, or more jerky than when not OC. Ever notice on some boots into Android it takes forever for your carrier to be detected & displayed on the lock screen and it may creep along as if your processor was hijacked by a random process? Ever notice when you open the app drawer not all your apps are displayed?
OC does use more energy thereby shortening battery run time and producing more heat. Don't complain about battery life if you are OC. Accurate battery charge state & battery run time are not synonymous.
While OC may shorten hardware lifespan it most likely, though possible, will not lead to a catastrophic failure in the typical device lifetime due to the rate of current technological innovations and average length of ownership.
My overall performance satisfaction with Project XDAndroid is best when not OC, especially now that hardware 3D is supported or partially supported as in my rhod500.
OC at your own risk.
Hi,
I've had my Archos G9 80 updated to the latest android official 4.0.5 from and since then i'm expriencing lots of crushes and freezes. I'm getting them randomly with no specific app working.
Also, i have tried to do full formats (Android + Data), and still having same issues.
Does anyone have any idea what else i can try?
Thanks.
I had lots of freezes too (not only with the latest firmware). They seem to be gone since I changed the CPU govenor from "hotplug" to "interactive". I'm not sure yet that it was the reason, but try it and let us know if it helps.
DeeDroid said:
I changed the CPU govenor from "hotplug" to "interactive".
Click to expand...
Click to collapse
how this is done? Ι have the same problem!
africa_twin said:
how this is done? Ι have the same problem!
Click to expand...
Click to collapse
Yes, can this be done from the phone itself? Within the ROM?
You can set this in any tool that is intended for overclocking. I don't overclock, I only changed the Govenor.
I use "SetCPU". ("No-frills CPU Control" should do the same.)
So does this have any other effects on the phone?
RichWPX said:
So does this have any other effects on the phone?
Click to expand...
Click to collapse
Nothing too serious. Your CPU is clocked dynamically so it doesn't run full speed when there is nothing to compute(save energy). To my understanding the govenor is basically a policy to manage how quickly the frequency steps up/down on changing CPU load. So "powersave" is supposed to save energy but make the system a little less reactive than "interactive" Governor for example. I think I read somewhere "hotplug" deactivates the second core on low load situations, I suspect for some strange reason my device might have crashed sometimes on trying to wake up the sleeping second core. Well maybe I'm wrong, that's why I'm interested if it helps others.
I didn't notice any change in battery lifetime, mostly it's the display anyway that drains the battery. Everything is running well, battery lifetime is great too and no crash/freeze at all since i changed that setting and it crashed almost every damn day before, no matter if it was Honeycomb or ICS.
I downgraded the device to 4.0.4 and since then, no crushes.. I guess for some reason 4.0.5 isn't stable on my device.. ill stick with this version unroll they get another one out..
To downgrade, just install official update file of the version you want to upgrade to..
DeeDroid said:
Nothing too serious. Your CPU is clocked dynamically so it doesn't run full speed when there is nothing to compute(save energy). To my understanding the govenor is basically a policy to manage how quickly the frequency steps up/down on changing CPU load. So "powersave" is supposed to save energy but make the system a little less reactive than "interactive" Governor for example. I think I read somewhere "hotplug" deactivates the second core on low load situations, I suspect for some strange reason my device might have crashed sometimes on trying to wake up the sleeping second core. Well maybe I'm wrong, that's why I'm interested if it helps others.
I didn't notice any change in battery lifetime, mostly it's the display anyway that drains the battery. Everything is running well, battery lifetime is great too and no crash/freeze at all since i changed that setting and it crashed almost every damn day before, no matter if it was Honeycomb or ICS.
Click to expand...
Click to collapse
Thanks! And I have notices ICS is not as snappy as GB was... I mean GB flew! Swiping the screen, it feels a little off now.
RichWPX said:
Thanks! And I have notices ICS is not as snappy as GB was... I mean GB flew! Swiping the screen, it feels a little off now.
Click to expand...
Click to collapse
GB? Gingerbread? Guess you mean Honeycomb. Anyway, I experienced ICS to be much better.
DeeDroid said:
I had lots of freezes too (not only with the latest firmware). They seem to be gone since I changed the CPU govenor from "hotplug" to "interactive". I'm not sure yet that it was the reason, but try it and let us know if it helps.
Click to expand...
Click to collapse
changing govenor from "hotplug" to "interactive" seems to help against random freezes. 4 days without problems until now i had freezes with ics, but never with honeycomb.
device: archos 101g9
[ROM] Archos ICS - Firmware 4.0.5(4.0.3) - ROOT & BUSYBOX , Only for SDE (thanks surdu_petru)
DeeDroid said:
I had lots of freezes too (not only with the latest firmware). They seem to be gone since I changed the CPU govenor from "hotplug" to "interactive". I'm not sure yet that it was the reason, but try it and let us know if it helps.
Click to expand...
Click to collapse
That seems to be my problem too. Setcpu requires root. is there a very easy way to do this, just to run this setcpu? There used to be a z4 tool, but can't seem to find it anymore.
Edit I see that I need superoneclick. Will temporary root suffice or will I need permanent root to change the governor setting.and keep it so.
Unfortunately all know temp root variants tend to brake things- im Honeycomb sound, in ICS 3d driver.
The only real option is to enable SDE and use custom firmware.
As for freezes- try reinstalling apps. Direct upgrade from Honeycomb does not work for all
tapatalked from Xperia Arc S
DeeDroid said:
GB? Gingerbread? Guess you mean Honeycomb. Anyway, I experienced ICS to be much better.
Click to expand...
Click to collapse
I have the same experience. Hc was laggy and slow. Ics is much faster and smoother.
Sent from my ARCHOS 80G9 using Tapatalk
gen_scheisskopf said:
Unfortunately all know temp root variants tend to brake things- im Honeycomb sound, in ICS 3d driver.
The only real option is to enable SDE and use custom firmware.
As for freezes- try reinstalling apps. Direct upgrade from Honeycomb does not work for all
tapatalked from Xperia Arc S
Click to expand...
Click to collapse
sorry for the n00b question, but SDE stands for ??? S ? Develeper Edition ?
Will "Superoneclick" not root my device ?
sbtwister said:
sorry for the n00b question, but SDE stands for ??? S ? Develeper Edition ?
Click to expand...
Click to collapse
Special Developer Edition
sbtwister said:
Will "Superoneclick" not root my device ?
Click to expand...
Click to collapse
No, it won't. Gen9 system layout is different than for most other devices
hey, back to topic
5 days without freeze with govenor "interactive". i witched back to "hot plug" this morning and had to reboot my tablet 2 times today. for my case, "interactice" seems to help against random freezes.
mines performance intstead of interactive... experienced some freezing n interactive..
Man I'm really pissed.
Yesterday I had to hard reboot 7 times
Sent from my X8 using xda premium
hmm,
sounds not good. archos stands not for high quality i guess. we get what we pay . i had an archos 101g8, now a 101g9 and trouble with hard-/firmwares since 2010. i think, this was the last one - no furthermore advantures
@IrishStuff09: you did reformat for ics or upgrade from honeycomb? the best way is to start from scratch and skip upgrades.
I'm running Albinoman's JB RC3 ROM, and like it a lot. The only significant problem I have is occasional severe sluggishness. When it happens, I'll open IntelliControl and I notice either of two things going on:
1) I'll see that the max CPU speed has been reset to 664000 or something close to that (it's always the same number, but I don't remember exactly what it is...600-something). Once I crank the max limit back up to 1036800, things are good again. What keeps resetting the CPU limit to such a low level, and how do I stop it from doing that???
2) I'll see that the CPU is maxed out at 1036800, but I can't figure out what's chewing up the CPU. What tool can I use to see what process is consuming all the CPU cycles when that happens?
Thanks for the help...
1. I can't tell you why it happens... but I know it is a common problem on the JB ROMs (on the Dinc). There was quite a lot of discussion about it. I know the devs are aware of the issue and were working on it.
2. I don't know of anything that will graph percentage of cpu cycles, or anything exactly like that. But try hooking the phone up to the PC and run ddms (part of the adb tool set) and see what it is doing (or failing to do). While ddms is running in verbose mode it will give you a running output of everything the phone is doing (along with all the errors and warnings).
MysticCobra said:
I'm running Albinoman's JB RC3 ROM, and like it a lot. The only significant problem I have is occasional severe sluggishness. When it happens, I'll open IntelliControl and I notice either of two things going on:
1) I'll see that the max CPU speed has been reset to 664000 or something close to that (it's always the same number, but I don't remember exactly what it is...600-something). Once I crank the max limit back up to 1036800, things are good again. What keeps resetting the CPU limit to such a low level, and how do I stop it from doing that???
Click to expand...
Click to collapse
That's because he's using an older version of Evervolv's qsd8k-common. It was fixed on Oct 10 with Change I3a0fff83: powerHAL: fix the screen off bug. This is one of the reasons I do nightlys, is to get all the new tweaks. This bug won't be fixed in his ROM till he resyncs his source and recompiles. It's triggered by the screen turning off. There's a workaround with Tasker, but since this bug is no longer in my ROM, I quit looking at it.
MysticCobra said:
2) I'll see that the CPU is maxed out at 1036800, but I can't figure out what's chewing up the CPU. What tool can I use to see what process is consuming all the CPU cycles when that happens?
Click to expand...
Click to collapse
CPUSpy is a pretty good app.
MysticCobra said:
I'm running Albinoman's JB RC3 ROM, and like it a lot. The only significant problem I have is occasional severe sluggishness. When it happens, I'll open IntelliControl and I notice either of two things going on:
1) I'll see that the max CPU speed has been reset to 664000 or something close to that (it's always the same number, but I don't remember exactly what it is...600-something). Once I crank the max limit back up to 1036800, things are good again. What keeps resetting the CPU limit to such a low level, and how do I stop it from doing that???
2) I'll see that the CPU is maxed out at 1036800, but I can't figure out what's chewing up the CPU. What tool can I use to see what process is consuming all the CPU cycles when that happens?
Thanks for the help...
Click to expand...
Click to collapse
For #1, a possible fix could be to use this power.qsd8k.so provided by tiny4579:
http://forum.xda-developers.com/showpost.php?p=32552961&postcount=264
Replacing this file fixed the issue on Pons's ROM, but it may wreak havoc on Albinoman's, I have no way to know. Make sure you have a good nandroid backup before attempting to use it. Or, just wait for Albinoman to release a newer ROM with the problem fixed in the source.
musical_chairs said:
For #1, a possible fix could be to use this power.qsd8k.so provided by tiny4579:
http://forum.xda-developers.com/showpost.php?p=32552961&postcount=264
Replacing this file fixed the issue on Pons's ROM, but it may wreak havoc on Albinoman's, I have no way to know. Make sure you have a good nandroid backup before attempting to use it. Or, just wait for Albinoman to release a newer ROM with the problem fixed in the source.
Click to expand...
Click to collapse
It should work fine on Albinoman's ROM. powerHAL is a generic jellybean feature and should work on all JB ROM's. You won't need the fix however on either of Pon's ROMs whether AOKP or CM10.
I'm finding the same issue on the 11/08 build. I replaced the file with the one you uploaded, yet no change. Still reverts to 614 when the screen is off.
I'm managing it with both Incredicontrol and Juicedefender, so on wake it returns to 1075, and the SAv2 seems much smoother than interactive for me. If there's a fix in the newer builds I may flash one (if I get the time), but for now I'm really impressed by how well this one is running.
Thanks,
...sorry...I was on the phone...
omniatic said:
I'm finding the same issue on the 11/08 build. I replaced the file with the one you uploaded, yet no change. Still reverts to 614 when the screen is off.
I'm managing it with both Incredicontrol and Juicedefender, so on wake it returns to 1075, and the SAv2 seems much smoother than interactive for me. If there's a fix in the newer builds I may flash one (if I get the time), but for now I'm really impressed by how well this one is running.
Thanks,
...sorry...I was on the phone...
Click to expand...
Click to collapse
It's supposed to change to 614 on screen off. The bug was that it would stick at 614 even on screen on.
I don't recommend that lib for cm. It's outdated.
Also I don't use sav2 anymore as it doesn't and won't implement project butter. Also interactive can be more aggressive than sav2 as it can jump frequency on touch via boostpulse which sav2 doesn't have.
Sent from my Galaxy Nexus using Tapatalk 2
Oh, well, then I guess I'll give the interactive another try. Maybe just needs to settle in longer. Got so used to ICS, wasn't sure what to expect from JB. Guess it's time I read back a few pages and see what else I've missed.
...sorry...I was on the phone...
Thanks, guys--appreciate the help!
Maybe its out of topic but since i still cant post on dev sub forum i wanna ask a question here to pons.
Im running your CM10 20121114, whenever i play music with appolo it always reboot my dinc.
Is any other had this problem too?
alph0 said:
Maybe its out of topic but since i still cant post on dev sub forum i wanna ask a question here to pons.
Im running your CM10 20121114, whenever i play music with appolo it always reboot my dinc.
Is any other had this problem too?
Click to expand...
Click to collapse
Yep, just a tad bit off topic.
I haven't had this problem before. Granted, I've never played music off my Inc, but I haven't heard anyone else complain, either. Can you PM a logcat? And it's always preferable to report errors off latest versions (currently 1120).
PonsAsinorem said:
Yep, just a tad bit off topic.
I haven't had this problem before. Granted, I've never played music off my Inc, but I haven't heard anyone else complain, either. Can you PM a logcat? And it's always preferable to report errors off latest versions (currently 1120).
Click to expand...
Click to collapse
Thanks for the reply Pons. Yes i think i will download the latest build sooner and test it again. Hope it (randon reboot with apollo) will not happen again on my dinc. But if it still, i will pm you the logcat.
alph0 said:
Thanks for the reply Pons. Yes i think i will download the latest build sooner and test it again. Hope it (randon reboot with apollo) will not happen again on my dinc. But if it still, i will pm you the logcat.
Click to expand...
Click to collapse
I use Apollo Music regularly on Pons's CM10, it works fine, doesn't reboot.
alph0 said:
Maybe its out of topic but since i still cant post on dev sub forum i wanna ask a question here to pons.
Im running your CM10 20121114, whenever i play music with appolo it always reboot my dinc.
Is any other had this problem too?
Click to expand...
Click to collapse
Try flashing to his newest build. It fixed a few problems for me and is incredibly fast. I had to reflash gapps from goo.im though because play store was force closing. Also, doubletwist is a better music player imo because it has a better interface and has good integration with the lockscreen.
Does this even need an explanation? Lollipop kills apps like it's his hobby.
Even with only a few light (on RAM) user apps running in the background you sometimes find yourself staring at your launcher home screen that, you could've sworn, was just showing a different app a second ago.
Or the times when, after multi-tasking a bit, your phone starts becoming painfully slow. Turns out that some apps are so stubborn that they go on strike (continuously restarting) when LP kills them.
I'm sure many have experienced this. And I have seen some devs address this issue here and there. I though it would be useful to gather the info into one thread, to ease our (or my?) frustration on this issue.
What I wanna know is, what causes it exactly (why didn't it happen on KK?), and is there a solution to this? Or at some way to calm LP down a bit with his killing of innocent apps.
Thanks.
Djalaal said:
Does this even need an explanation? Lollipop kills apps like it's his hobby.
Even with only a few light (on RAM) user apps running in the background you sometimes find yourself staring at your launcher home screen that, you could've sworn, was just showing a different app a second ago.
Or the times when, after multi-tasking a bit, your phone starts becoming painfully slow. Turns out that some apps are so stubborn that they go on strike (continuously restarting) when LP kills them.
I'm sure many have experienced this. And I have seen some devs address this issue here and there. I though it would be useful to gather the info into one thread, to ease our (or my?) frustration on this issue.
What I wanna know is, what causes it exactly (why didn't it happen on KK?), and is there a solution to this? Or at some way to calm LP down a bit with his killing of innocent apps.
Thanks.
Click to expand...
Click to collapse
Im running 1/8 FML with synapse injected R10 kernel on my toro and with ksm and laptop mode enabled in synapse, I haven't had a launcher redraw in days. I don't have anything whitelisted either. However, the trade-off I have at the moment is I cant seem to stream videos on my stock browser. Havent tried a different browser or anything. I just uncheck those two settings and reboot and all is well, but my phone certainly works much better now, and no redraws, with neph settings for LMK
Hope something helps someone!
Thanks
erk1725 said:
Im running 1/8 FML with synapse injected R10 kernel on my toro and with ksm and laptop mode enabled in synapse, I haven't had a launcher redraw in days. I don't have anything whitelisted either. However, the trade-off I have at the moment is I cant seem to stream videos on my stock browser. Havent tried a different browser or anything. I just uncheck those two settings and reboot and all is well, but my phone certainly works much better now, and no redraws, with neph settings for LMK
Hope something helps someone!
Thanks
Click to expand...
Click to collapse
Perhaps you can noobify that a bit, lol. I had to google almost everything you mentioned. As I understand it, this Synapse allows you to tweak the kernel? And this KSM settings can improve this RAM issue? Care to elaborate? And what is laptop mode?
I've read about adjusting the LMK values to calm LP down a little. Any idea though why this was so necessary in LP, but not in KK? Is stock LP 'naturally' more RAM hungry than KK?
Djalaal said:
Perhaps you can noobify that a bit, lol. I had to google almost everything you mentioned. As I understand it, this Synapse allows you to tweak the kernel? And this KSM settings can improve this RAM issue? Care to elaborate? And what is laptop mode?
I've read about adjusting the LMK values to calm LP down a little. Any idea though why this was so necessary in LP, but not in KK? Is stock LP 'naturally' more RAM hungry than KK?
Click to expand...
Click to collapse
I can try to elaborate little bit, as Ive been flashing things and researching xda a lot, but I am still noob in how/why things are the way they are. From what I gather lollipop just handles memory differently then kk did. I think that is some of the reason as to why the "recent apps" persist through reboots now. Remember, our device was not really supposed to run kk and certainly not meant to run lollipop. The developers here are without a doubt amazing in what they know and what they do for us users. A new kernel and driver was necessary to run lollipop on the aging gnex. Now, some of the issues we are experiencing is a google issue and will only seem to get fixed when they get around to it. I know my nexus 7 (old) has some memory issues and lag and redraws from time to time....not as much as I noticed with my gnex before the changes were made I stated in the above post. I recently helped my friend root and upgrade his oneplus one to lollipop and he has the same issues we all have, maybe not as bad, but they are noticeable
A lot of the questions you have, have been discussed recently in bsmitty83 kernel thread, since I asked them. There are links there as to what KSM and laptop mode are and what they do. KSM-kernel same page merging helps with RAM and I believe laptop mode helps to conserve power. A lot of these things are geared at devices with low ram like the aging gnex, but the developers have done a great job at making lollipop a daily driver. Most users I think use trickstermod from playstore to tune kernel settings, and that is ok, however, you must purchase the paid version to tweak low memory settings, which I did. However, synapse, also found on playstore can also be used to tweak kernel settings, but the kernel has to contain UCI support for the synapse app to work. Synapse has more settings available to tweak than trickster does, like KSM and laptop mode, which have helped me very much. The only kernel I'm aware of that has UCI support for synapse is bsmitty83 Full_Auto R10, because osmosis made it work
Hopefully this was rather accurate and helpful and not convoluted! ha.....im sure some more knowledgeable people will come and correct anything I said that may be incorrect, but in the meantime, read through the R10 kernel thread and see what you come up with
What ROM and kernel are you currently using?
Thank you
erk1725 said:
...
The only kernel I'm aware of that has UCI support for synapse is bsmitty83 Full_Auto R10, because osmosis made it work.
...
What ROM and kernel are you currently using?
Click to expand...
Click to collapse
I'm currently using AOSP rom (by freshgimmi) and the Full Auto R10 you mentioned. I'll try injecting the new ramdisk now and see how it goes.
I noticed this issue as well for the first several days . However once I installed the new bootanimation from arter97 the issue doesn't occur anymore. Not sure if it's related but all I did was mount /system as rw and copied into the new lollipop boot animation from here: http://forum.xda-developers.com/android/software/arm-arm64-android-5-0-lollipop-t3032247
Djalaal said:
Does this even need an explanation? Lollipop kills apps like it's his hobby.
Even with only a few light (on RAM) user apps running in the background you sometimes find yourself staring at your launcher home screen that, you could've sworn, was just showing a different app a second ago.
Or the times when, after multi-tasking a bit, your phone starts becoming painfully slow. Turns out that some apps are so stubborn that they go on strike (continuously restarting) when LP kills them.
I'm sure many have experienced this. And I have seen some devs address this issue here and there. I though it would be useful to gather the info into one thread, to ease our (or my?) frustration on this issue.
What I wanna know is, what causes it exactly (why didn't it happen on KK?), and is there a solution to this? Or at some way to calm LP down a bit with his killing of innocent apps.
Thanks.
Click to expand...
Click to collapse
SpideyTheMan said:
I noticed this issue as well for the first several days . However once I installed the new bootanimation from arter97 the issue doesn't occur anymore. Not sure if it's related but all I did was mount /system as rw and copied into the new lollipop boot animation from here: http://forum.xda-developers.com/android/software/arm-arm64-android-5-0-lollipop-t3032247
Click to expand...
Click to collapse
I know about this issue. It is a memory leak during boot. It is a good catch, though all you're changing is the bootanimation.zip. AFAIK, it should not affect your system's performance after boot, once your phone is up and running. My issue is a different thing entirely. I never got bootloops (that is, when not messing around with xposed).
Okay, you're right. As a test last night I switched from FML 5.0.2 to LiquidSmooth's LP ROM and I'm not seeing any aggressive app kills in LiquidSmooth.
Djalaal said:
I know about this issue. It is a memory leak during boot. It is a good catch, though all you're changing is the bootanimation.zip. AFAIK, it should not affect your system's performance after boot, once your phone is up and running. My issue is a different thing entirely. I never got bootloops (that is, when not messing around with xposed).
Click to expand...
Click to collapse
erk1725 said:
Im running 1/8 FML with synapse injected R10 kernel on my toro and with ksm and laptop mode enabled in synapse, I haven't had a launcher redraw in days. I don't have anything whitelisted either. However, the trade-off I have at the moment is I cant seem to stream videos on my stock browser. Havent tried a different browser or anything. I just uncheck those two settings and reboot and all is well, but my phone certainly works much better now, and no redraws, with neph settings for LMK
Hope something helps someone!
Thanks
Click to expand...
Click to collapse
I have got synapse up and running. I AM wondering though, what LMK settings are you using? Cause the neph settings I know of tell me to set empty app to 370, but synapse only allows max 320... If you're following different settings, could you link the post for me?
Djalaal said:
I have got synapse up and running. I AM wondering though, what LMK settings are you using? Cause the neph settings I know of tell me to set empty app to 370, but synapse only allows max 320... If you're following different settings, could you link the post for me?
Click to expand...
Click to collapse
Glad you got everything up and running.....Im using Neph's settings for LMK, and your correct the empty app only goes up to 320 in synapse. There was a post somewhere where Neph said he was still tweaking his LMK values and I believe he mentioned about lower empty app to 330 or something, so I just set it to 320 in synapse and call it a day