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
I've used SetCPU in the past and have determined that my max stable clock speed is 113600; I've also read that using SetCPU to control clock speed can create some problems.
How would one go about manually overclocking the phone without using SetCPU? I was looking around in /sys/devices/system/cpu/cpu0/cpufreq and it looks like there are kernel settings there, just want to make sure I don't bork anything in the process
Thanks in advance!
From my understanding is that if you get an overclock kernel it will basically run in the same fashion as your current kernel (as far as governing speed goes) except you'll have a higher max frequency.
Rrrracer said:
I've used SetCPU in the past and have determined that my max stable clock speed is 113600; I've also read that using SetCPU to control clock speed can create some problems.
How would one go about manually overclocking the phone without using SetCPU? I was looking around in /sys/devices/system/cpu/cpu0/cpufreq and it looks like there are kernel settings there, just want to make sure I don't bork anything in the process
Thanks in advance!
Click to expand...
Click to collapse
SetCPU is the GUI to do what you are talking about... Are you looking to go past 1.113? I can only get to 1.113, but if I run Hyrda's OCOV kernel I can get to 1.15.
I would say if you don't know what you are doing, I wouldn't mess with it. Nandroid is handy if you do.
I'm running invisiblek's #16 kernel but max clock speed is showing 998. Not trying to go over 1.13 but thought I read somewhere about being able to manually change it in the system files somewhere without using SetCPU.
IIRC the idea was to use SetCPU to determine your max stable clock speed, then change it manually in a system file somewhere and then not use SetCPU.
Sent from my ADR6300 using XDA App
Try uninstalling/reinstalling setCPU. I've had issues every once in a while when flashing a new ROM, then doing the app only restore from a TI backup cause issues.
Personally I can't say I've ever had any problems using SetCPU, but if there's a way to make it default to 1.13 without having another process running then I am all for it, thus my question. Just don't know where to change it
I can tell you i am 99.9% sure that you were right with the file location in your first post.
If you check chads thread SOMEWHERE in there i think its mentioned... Sorry to say but i have no idea where.
Here's a script that Ziggy wrote, you can edit it to your needs and flash it and fix permissions. Without editing it's set at 1.113GHz Interactive screen on and .384GHz Ondemand screen off if I remember correctly. It also has another tweak (memory management I believe?). But hey, it's a start.
Much appreciated guys, I will check out Chad's thread again and look at that script. I just don't see the need for SetCPU if I can just plug in my known stable values and roll it like that Thanks again!
Fixed lol sorry
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS4.
LOL Blah! :-D
I have tried editing those files and it does not seem to change the clock speed. Anyone who has successfully done it manually could you please list all the specific files. Also im going to examine the script that was linked and see if i can tweak it a bit. Ill post any findings here.
I use the custom kernel #18 and setcpu, clocked to 1.115 easily with cm6.1. works awesome and smokin fast.
trunksta said:
I have tried editing those files and it does not seem to change the clock speed. Anyone who has successfully done it manually could you please list all the specific files. Also im going to examine the script that was linked and see if i can tweak it a bit. Ill post any findings here.
Click to expand...
Click to collapse
I edited Ziggy's script using EditPad lite (free, just Google it) since I'm on Windows so as not to change the format. Flashed from recovery then fixed permission in Root Explorer. Worked like a charm.
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
Does anyone know how to edit Calkulin's processor speed scripts to run at 800MHz all the time instead of using the following preset profiles of 1.2GHz - 100-85%, 1.0GHz - 84-36%, 800MHz - 35-0%?
Simply put, I don't need the faster processor speeds and would rather have the benefits of the longer battery life that running at 800MHz provides. Problem is there are several scripts and I don't know what values to change to accomplish a constant state of 800MHz. If anyone can help me out, I would appreciate it.
FYI I sent Calkulin a message several weeks ago asking this question and presume he is very busy as I have not received a response. I thought I'd try asking the community.
Have you tried to view your screenstate scaling... the profiles are right there you can change where it say 120000 to 80000 similar to battery profile 2 as well as where it says MaxCPu speed.... you can change that to your desired speed.... just use root explorer or notepad+
Its really pretty simple... if you have rom toolbox you can change it there as well which as a whole program is pretty damn useful
Sent from my Xoom using Tapatalk
You can use a third party app, like Setcpu, to established the desired clock. If you want to do it manually without an app, you can open the script file with a text editor and change the values. Look in /system/etc/init.d for the script.
Easiest way is to use Setcpu so you can edited on the fly.
Easy way would be edit the line "MAX_CPU_SPEED_PROFILE_1="1200000"" to show "MAX_CPU_SPEED_PROFILE_1="800000""
Because I suffer some problems in the vision, I bought a Nook Simple Touch to perform some of the functions performed with my asus transformer but with an electronic ink display. I must say I'm quite satisfied with its functionalty, but despite having to severely limit my hours in front of screens, I could not resist to modify the kernel.
The kernel adds frequencies of 1GHz and 1.1GHz, besides being modified to compile using gcc 4.7 from Linaro. I've also changed some compilation options.
The kernel includes the modifications for multitouch.
Attached the patch for the original source code 1.1 and my build.
Don't forget to rename the uImage.img to uImage (renamed it to allow the uploading)
Since version 2, the kernel support the normal and glow versions.
REMOVED temporarily
Very nice to see you Guevor. I am currently still running one of your kernels for the Transformer. Hopefully you can do the same magic over here.
@All, Guevor knows what he is doing and is always willing to help and troubleshoot with you. Above all, if you have bugs, Logcats are best but detailed explanations are almost just as helpful.
whoa! guevor here!!! :good:
Thanks, but a question
Can voltage control be added? The nook would probably benefit hugely from undervolt.
notriddle said:
Can voltage control be added? The nook would probably benefit hugely from undervolt.
Click to expand...
Click to collapse
from everything I've read, undervolting provides only a very minimal gain in battery life (we're talking about max a couple of procent)
The voltage is not fixed for each frequency, so it is modified while working, and the only thing that is fixed is the nominal value.
I have looked very little about this board, but that is what I have seen so far.
I made a compilation reducing the nominal value, but do not think it changes much.
I've also tweaked some latencies and have limited the overclocking to 1Ghz (better relation).
I've done some testing and I can see that using ondemand, the lower rate (300Mhz) is much more used, so consumption should be reduced.
can someone explain how to install this kernel?
pet4a said:
can someone explain how to install this kernel?
Click to expand...
Click to collapse
You first need to rename the uImage.img to uImage
Then you need adb on your computer and be connected on the same net (computer and nook).
After that, you can use these instructions.
http://forum.xda-developers.com/showpost.php?p=24168019&postcount=21
I hope it will be helpful
Thank you for this uImage Hmm...is it really to have USB host support too in this kernel? And support for the NST Glowlight? Thanks.
Filippios said:
Thank you for this uImage Hmm...is it really to have USB host support too in this kernel? And support for the NST Glowlight? Thanks.
Click to expand...
Click to collapse
bump for USB host.
also.. at 1000 MHz system seems to be working noticeably faster (placebo effect?). Thanks for compiling this kernel.
Zorkman said:
from everything I've read, undervolting provides only a very minimal gain in battery life (we're talking about max a couple of procent)
Click to expand...
Click to collapse
This is true on smartphones because most of the battery life is consumed by the display and the cell radio. There is no cell radio on the NST, and the display consumes far less, so a larger percent of the battery consumption is from the CPU and undervolting should be more effective. (let me know if I'm wrong here)
Please clarify re:Glow
Could someone please clarify whether this kernel includes support for the Glow?
I found a mt kernel for the glow from mali100 here: http://forum.xda-developers.com/showthread.php?t=1679036
so i know the nst kernels can be patched for the glow: but I'm unclear whether this kernel, which I'd much rather use for the overclock, has been so patched.
Thanks!
Oh, and my vote is to keep the usb host support in a separate kernel due to battery drain.
-Alley
guevor said:
You first need to rename the uImage.img to uImage
Then you need adb on your computer and be connected on the same net (computer and nook).
After that, you can use these instructions.
http://forum.xda-developers.com/showpost.php?p=24168019&postcount=21
I hope it will be helpful
Click to expand...
Click to collapse
fallowed the instruction but after i reboot the device its freezes on read forever screen
am i missing something?
a7t7d said:
Could someone please clarify whether this kernel includes support for the Glow?
Click to expand...
Click to collapse
I don't think it supports the glowlight, but you can just try it. The worst that could happen, is that the screen light doesn't work as long as this kernel is installed.
I found a mt kernel for the glow from mali100 here: http://forum.xda-developers.com/showthread.php?t=1679036
so i know the nst kernels can be patched for the glow: but I'm unclear whether this kernel, which I'd much rather use for the overclock, has been so patched.
Click to expand...
Click to collapse
That's not a patched nst kernel, it's a glowlight kernel (based on the 1.1.5 nook software). Glowlight kernels work just fine on the old nst.
So what I'm trying to say is:
nst kernel on a glowlight -> works fine, just no support for the screenlight
glowlight kernel on a nst -> works perfect, no issues.
Oh, and my vote is to keep the usb host support in a separate kernel due to battery drain.
Click to expand...
Click to collapse
I second that, usb host is just not stable enough to be a default for everyone, particularly because a lot of people have no use for it.
pet4a said:
fallowed the instruction but after i reboot the device its freezes on read forever screen
am i missing something?
Click to expand...
Click to collapse
Maybe your device does not support the overclocking or may need more voltage.
What version did you use? The original post had a nominal voltage slightly higher.
mali100 said:
I don't think it supports the glowlight, but you can just try it. The worst that could happen, is that the screen light doesn't work as long as this kernel is installed.
That's not a patched nst kernel, it's a glowlight kernel (based on the 1.1.5 nook software). Glowlight kernels work just fine on the old nst.
So what I'm trying to say is:
nst kernel on a glowlight -> works fine, just no support for the screenlight
glowlight kernel on a nst -> works perfect, no issues.
I second that, usb host is just not stable enough to be a default for everyone, particularly because a lot of people have no use for it.
Click to expand...
Click to collapse
Good to know. I'll take a look and if I find no problem, I'll do a single kernel for both.
About the usb host had not even tried, but if you say it is not stable, better to keep two versions.
As a novelty, I have been making tests with the display and I'll upload a new version. I am also uploading a video I have just done to show how it works.
New version with a new fast display mode
I've been testing the epaper's driver, both to see how it work and to testing if I could get something new.
I added a parameter (/ sys/devices/platform/omap3epfb.0/graphics/fb0/fmode) that can enable a new fast mode.
By default starts at 0, so it works very much as always (although I modified some behavior, I have to do more tests), and if we put it to 1 enables a new faster mode.
To not extend much (and avoid being too much in front of the computer screen), I recorded a video showing the new mode, and also put a couple of images to compare the normal mode with the new one.
I have also created a small program that will allow us to switch between the two modes (I use the Reading now button for it)
Hope you are interested.
Thanks for the kernel.
However, I've installed the new version (in the previous post) using clockwork recovery (zipfile) but seems that overclock is inactive. Checked with "Android System Info" app.
EDIT: Reflashed using ADBWireless, now 1 GHz is recognized. And "Fast Mode" is far better than "No Refresh" when browsing web and testing games.
guevor said:
Maybe your device does not support the overclocking or may need more voltage.
What version did you use? The original post had a nominal voltage slightly higher.
works.
Click to expand...
Click to collapse
nook ver 1.1.2 rooted using touchnooter.
i used B&N update to revive my nook.
enrsil1983 said:
Thanks for the kernel.
However, I've installed the new version (in the previous post) using clockwork recovery (zipfile) but seems that overclock is inactive. Checked with "Android System Info" app.
Click to expand...
Click to collapse
"CPU Master Free" shows 1000 MHz in Performance mode.
- Can you add USB HOST support to this Kernel? It would make this one the best kernel available.
Thanks
- from time to time while the wifi is on, Nook freezes.
Hi Guevor,
This is really cool stuff! Thanks!
BTW some people tried to upgrade from Eclair to Froyo but all them got stuck at some point, apparently there are problems with the drivers that are closed source, but I dont see why can't we take the drivers for a similar device that uses Froyo. What is your opinion on this?
I'd be happy to help so you can minimize the amount of time in front of the computer
Gracias!