Related
I've just begun overclocking my 8125. starting at 220 and i'll work my way up slowly to a maximum of 265 if possible.
I was wondering if anyone had any horror stories that would make me change my mind about overclocking. Like permanantly damaged devices. I've searched the forums and cant find a single one, which leads me to beleive that it truly is completly safe. But i thought i'd start this thread to make sure.
The worst that I've had happen to me (or heard of happening to someone else) with overdoing the overclock is the device showing the 'white screen of death' which just forces you to soft-reset your device. It's really not anything that bad ^_^
k2snowboards88 said:
I've just begun overclocking my 8125. starting at 220 and i'll work my way up slowly to a maximum of 265 if possible.
I was wondering if anyone had any horror stories that would make me change my mind about overclocking. Like permanantly damaged devices. I've searched the forums and cant find a single one, which leads me to beleive that it truly is completly safe. But i thought i'd start this thread to make sure.
Click to expand...
Click to collapse
i've been overclocking at 242 or 260 for over 2 months now and I haven't had any problems. My sweet spot is 242, it runs GREAT on this speed and it is a tad more stable than 260.
It is possible to brick your device if you try a speed to fast. 240 is perfectly safe, anything above that can be unstable.
I know its possible to fry a chip through overclocking. I remember frying one of my amd k6-2 processers awhile backl. I just find it odd that even though its possible to fry your wizard. and so many people overclock, that i haven't heard one story about a wizard being broken this way.
I know its possible to fry a chip through overclocking. I remember frying one of my amd k6-2 processers awhile backl. I just find it odd that even though its possible to fry your wizard. and so many people overclock, that i haven't heard one story about a wizard being broken this way.
Been running mine @ 240 for a while now and everything seems fine.
My phone is mainly on stand-by during the day, but when I do use it for extended periods (evenings and weekends) I use Wi-Fi a lot and read a lot of ebooks which can be quite power consuming - however, the overclocking seems to have no noticeable affect on the phone other than making it quicker...
afaik
MOST "PORTABLE" CPU'S CAN MUCH FASTER THAN THEY DO BUT AT THE COST OF POWER THE CPU'S ARE "UNDERCLOCKED" TO SAVE POWER
SORRY MY CAPS IS STUCK AND i JUST NOTICED IT...
BHANG
afaik
MOST "PORTABLE" CPU'S CAN MUCH FASTER THAN THEY DO BUT AT THE COST OF POWER THE CPU'S ARE "UNDERCLOCKED" TO SAVE POWER
SORRY MY CAPS IS STUCK AND i JUST NOTICED IT...
BHANG
overclocking after standy freezes for a while!
This query is not related to the thread, but forgive me as I didn't want to start a new one.
I've smarskey with the overclock feature enabled and omapclock.exe running nicely. It hasn't been giving me trouble at all. However, I've one problem..
After the phone goes in standby after a period of inactivity and when I hit the power button again to use the phone, I notice a freeeze in time display. It takes a while before time changes from say 11:30 to 3:30.
I know Smartskey 'wakes' up the overclocking process again and this maybe the reason why my phone somewhat freezes for a very brief period after I disturb the standby mode, but I was wondering if anyone has a solution to this, its kinda annoying.
Thanks
Does not sound that bad, I think your problem is that you can't just take your phone out to have a look at the time :wink: am I right?
Well perhaps that would really be kinda annoying.
But it also sounds like there is no real solution to this. Just try reinstalling the apps, certainly there is a software conflict (if this is not a normal effect).
Perhaps you can also use another possibility than smartskey. I think BatteryStatus and OMAPScaler also have options to overclock at wakeup.
thanks..
maati said:
Does not sound that bad, I think your problem is that you can't just take your phone out to have a look at the time :wink: am I right?
Well perhaps that would really be kinda annoying.
But it also sounds like there is no real solution to this. Just try reinstalling the apps, certainly there is a software conflict (if this is not a normal effect).
Perhaps you can also use another possibility than smartskey. I think BatteryStatus and OMAPScaler also have options to overclock at wakeup.
Click to expand...
Click to collapse
thanks for the advice, i'm thinking about using memaid.
Couldn't really see any discussion on this yet, and personally it's in a location on the forum that I rarely visit but I've found an overclock tool that is slowly becoming very good indeed for our processors. Link to thread is here. I'm soo far up from 528Mhz to 748Mhz (been stable for the past 6 hours no problem). Just make sure to follow the thread (instructions are linked to ensure overclock remains applied through scripts and 3rd party apps). Should take no longer than 30mins for a well versed user to set up. Please don't try this if you haven't got a clue what you are doing as there is soo much scope for error and dead phones! You may also need to customise any scripts to your specific phone/software build. CDMA phones as usual are different from what I've heard. But anyway good luck, I'm gonna keep trying to push the Mhz up (aiming for 850Mhz ).
Not sure its a good idea to go past 700 mhz,our phones run hot as it is under capacity,as with gaming rigs heat is your Enemy,the cooler you keep it the faster.
It's actually remained pretty cool, and when it's in my pocket it's only running at stock clocks anyway. Only when I'm using it does it get to the full 748Mhz. Running wifi router and charger and temps are not noticeably hotter than usual...
um... ive been clocked up to 787 highly stable for the last like 2 weeks. No heat problems, no battery problems, just insane speed.
recommendations: Download v1, not v2. ESP if you dont know what you're doing. Then download the zip im attaching, there's 2 mortscripts in there and a registry addition, THESE MUST BE IN THE STORAGE CARD ROOT. use the regisitry addition FIRST (just associate w/e regedit software you use, then run the .reg file in total commander), then go back to total commander, edit the .mscr "Toggle_boost" and adjust the value boost = "x" to whatever value you want the phone to OC at, eg boost = 41 is 787mhz which is stable for me, test yours out.
THEN, open and install rhodiumkbdcontrol (attached), reboot, go to settings>system>keyboard config> add key
1st pick which key you want to be the OC boost swtich, I have it mapped to my PTT button. click the plus sign, drop down menu, run program, then highlight "run program" in the list then click "..." then type in
Program: \windows\mortscript.exe
Arguments: "\storage card\toggle_boost.mscr"
This time you wanna use the power key.
same general instructions except
Program: \windows\mortscript.exe
Arguments: "\storage card\boost_off.mscr"
then plus sign again, drop down menu, default key action, and click extended emulation. THEN hit update config. should work like a charm, also autoover clocks to 610, the boost button with send you up the w/e the boost = "x" is set to, and then back again, most find 710mhz to be the stable point, and feel free to ask questions
sorry, heres the zips
wouldnt overclocking also gives you a higher chance of frying your CPU chip? cuz ive seen it happened in PCs i just idk about PPCs
I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!
miked79928 said:
I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!
Click to expand...
Click to collapse
Yeah could you hook that up? I think posting it here would be best but pm'ing works just as well
Edit:
I just read threw the above links and guides and was wondering if there is a more automated way of setting this up rather than having to link it to a button press. I'm guessing this has not been figured out yet (or the guides would have mention of it ). Just curious.
dantegl36 said:
Yeah could you hook that up? I think posting it here would be best but pm'ing works just as well
Click to expand...
Click to collapse
Here is the best way I have found to do it. I take absolutely no credit for this:
http://forum.xda-developers.com/showpost.php?p=7354283&postcount=627
Check it!
Outlaw78a said:
Not sure its a good idea to go past 700 mhz,our phones run hot as it is under capacity,as with gaming rigs heat is your Enemy,the cooler you keep it the faster.
Click to expand...
Click to collapse
I have used this, NRG also does. I have NEVER had any problems and mine is as high as 787 as long as I'm running it which is constantly.
XITruthiX said:
um... ive been clocked up to 787 highly stable for the last like 2 weeks. No heat problems, no battery problems, just insane speed.
Click to expand...
Click to collapse
100% agreed. Been running at the highest speeds with NO problems, no batt drain, no heat probs, nothing.
XERO_Racer said:
wouldnt overclocking also gives you a higher chance of frying your CPU chip? cuz ive seen it happened in PCs i just idk about PPCs
Click to expand...
Click to collapse
Not unless you are having excessive heat problems. Since there are basically no people reporting these problems, I wouldn't worry.
miked79928 said:
I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!
Click to expand...
Click to collapse
Once again as stated earlier, 100% agreed.
Do I have to keep plugged in?
miked79928 said:
Here is the best way I have found to do it. I take absolutely no credit for this:
http://forum.xda-developers.com/showpost.php?p=7354283&postcount=627
Click to expand...
Click to collapse
I thank you for this, but I'm not sure how to implement it. I have installed Mortscript, I've copied the code into a file I called overclock.mscr and modified the code reflect the reg values on my Tilt 2. and I've placed the script on the root on my SD card. I've installed MSM7kCpuSpeed on to my SD card. How do I make the script run automatically?
Thank you!
I take no responsibility for w/e happens to your phone with this advice.
Try putting a pointer in your start up to the over clocking script. Its highly unstable and could brick your phone or require a hard reset... thats why I do it with a toggle switch, i dont mind manually applying the OC with a hard key knowing its safe, esp because the situations where I actually NEED 787mhz are less common than needing to just wake the phone to answer a call or make a txt message.
I just want to say that I have been running android on my tilt 2 overclocked at around 750 for a few months now with various builds and i know a lot of other users who have as well with no problems, i am going to try this out, thats what i pay for insurance for hehe
..and after reading more i may have spoken too soon because i missed the posts where i saw that you can brick your phone with OC in WinMo easily enough if you are not careful, so tread with caution
dirtypiratehooker said:
I just want to say that I have been running android on my tilt 2 overclocked at around 750 for a few months now with various builds and i know a lot of other users who have as well with no problems, i am going to try this out, thats what i pay for insurance for hehe
..and after reading more i may have spoken too soon because i missed the posts where i saw that you can brick your phone with OC in WinMo easily enough if you are not careful, so tread with caution
Click to expand...
Click to collapse
Just a note, I'm not sure the insurance would cover burning a custom ROM into the phone, or overclocking the CPU. And if the chip is fried you can't burn the stock ROM back in. But then, they probably couldn't figure out it was updated without in stalling a new CPU. Umm, it would probably work.
Would a .cab for this ever be conceivable?
At this point, we have finally got a script that will work for most Rhodiums, Topaz (Diamond 2), and a few guys with other phones seem to be having good luck.
The device has to have Mortscript installed, and nettrip's MSM7 v2.
It is a single script solution that requires no pre checks in the registry, no key/button assignment, and you can change the speed settings from the script instead of the registry.
It throttles the OC up and down for calls, lock, and sleep, to avoid freezing on wake up and in a call. Some problems that still need to worked out by nettrip in the script. I don't envy him the work as the script(s) were bad enough. Four of us have hit that original script (by jpc) from about page 13.
You copy the script to the SD or the device root, create a shortcut to the file, copy the shortcut to Windows\Startup directory, reset/reboot the device and you are off.
You can use the MSM7 app to read the OC, but you should make sure to exit the app before sleep, lock, or power off, as it will error on reboot if left open.
To be honest, you never have to open the MSM7 app, as the script controls it in the background.
I believe the script is set for a low over clock. 691. My experience has been a 710 average, but a lot get a stable OC at 750+. I am running 748 and I think I will stop there. A 200MHz overclock will just have to do.The phone does not get hot, though with intense use, it does get warmer. Never warmer than when the battery is charging, tho.
I am running the nrg Sense Reference ROM, 23xxx based on Sense 2.5. I added the CHT 1.8x and the editor to save a few MHz, no biggy.
The overclock allows the Sense to work MUCH smoother, actually noticeable as even the weather animation is smooth.
And all the vid players seem to work better.
I have noticed NO extra battery drain than usual.
The script is only a stop gap measure until nettrip finishes his app, but it does work well with little effort. WAAAAY better now than even last week.
However, use the script at your own risk, as you can get too Medieval on the OC. Some guys are running 800+, more nerve than I have.
Anyway, if interested in the script or want to read some more about the app, you can start here
http://forum.xda-developers.com/showthread.php?t=725290&page=89
post #882 has the script.
Plenty of instructions on how to use (and make changes to the settings) in the last 30-40 pages.
Sorry if this is already explained, but can someone tell me in simple details how to keep my overclock at 729mhz even after screen lock or sleep mode? I've tried to follow previous posts but it keeps reverting back to 528mhz after locking and sleep.
Ok so this seems legitamite,everyones checking in with no problems.
other than the increased risk factor that always accompanys speed,
it seems our ppc's cpu was underclocked beforehand ?
i will try this and see if i get a gpu boost as well.
but ivr already experienced my phone overheating to the point
of shutting itself down,and the god-damned orange light is permenantly on...
The main thing I'm concerned about here is the time it takes to charge the phone.
What it seems like is happening is that the phone won't underclock like it did before froyo and it stays up above 500-600 mhz instead of much, much lower in the 200-300 range.
Can anyone tell me if I'm way off on this?
If I'm not, is there a way to test and see at which speed the processor is running, especially in standby?
Then, is there anything that can be done about this, or do we have to wait for the source code to be released and then for custom kernels to be developed that can help the phone be more energy efficient when charging.
Thanks
You could use Set CPU to limit the processor speed while the screen is off or charging.
My only concern with doing that is that when a task needs to be performed it would take alot longer to do it, and erase any positive effect of underclocking that way.
Does anyone know if this is a valid or known issue? Is anyone else seeing the same issue or know why its happening? Just looking for more info on this.
Kind of off topic, but does setCPU work with the latest leak of Froyo?
Sent from my ADR6300 using XDA App
I just have a setCPU profile set to 245/245 while screen off. Doesn't seem to affect anything in a negative way. SetCPU should work as long as your phone is rooted. Select "Autodetect" in device selection. Moving this to General with a redirect expiring in one month.
Keep in mind that underclocking will not work unless you disable the perflock. In setcpu, hit menu to do so. Its only per boot.
adrynalyne said:
Keep in mind that underclocking will not work unless you disable the perflock. In setcpu, hit menu to do so. Its only per boot.
Click to expand...
Click to collapse
thanks for the tip.. so I guess I'll have to disable perflock every time I reboot.. sigh..
Also, what does the "set to boot" check/uncheck option do?
You can set your default speeds with that option on boot. However, it will only work on perflock disabled kernels, and I haven't found a way to disable it in the stock kernel. Easy enough from source, but once its compiled, its a lot tougher, if not impossible.
I guess I don't want to deprive the device of it's full potential by underclocking it especially when I am using it... the processor speed being one of the main reasons why this phone stood out for me back then..
However, I do have the processor speed dip down to 245max/min when screen is off.. I think that should help with battery quite a bit yea? Also with the 245 max/min profile when screen is off.. I guess there is no need for an app killer anymore.
Thats what I am doing as well and the results have been promising. Just wish the perflock disable was permanent
I requested it as a feature in the dev thread, but I don't know if he will add it.
Seems to me he just needs to insmod the module that disables the perflock at the same time speeds are set with the at boot time option.
Not that I know anything about programming.
Ahh yes...forgot about the perflock on your Sense devices.
My understanding was having to do the perflock each time was intentional. Since it has a chance of crashing your phone, if it was permanent it would cause a permanent unrecoverable loop or something to that effect.
But I know nothing about programming either (WAY less than adrynalyne that's for sure), just remember reading that somewhere on the forums.
Didn't really intend for this thread to become a setCPU discussion, but got some good info out of it.
Was mainly trying to figure out WHY group doesn't seem to undertook natively and id there is a possible fix out there or at least looming.
That said. I'll be getting to a charger in a few minutes and anxious to see if this helps me with the charging issue as is seems to have with others.
s197 said:
My understanding was having to do the perflock each time was intentional. Since it has a chance of crashing your phone, if it was permanent it would cause a permanent unrecoverable loop or something to that effect.
But I know nothing about programming either (WAY less than adrynalyne that's for sure), just remember reading that somewhere on the forums.
Click to expand...
Click to collapse
Its true thats why it has been set up that way, and Im sure the dev did that for support reasons too.
Anything is recoverable though
Maybe the dev could add a secret geek code to unlock it for those of us who are stupid and wreckless
Now I love my DZ; it is by far the most capable phone I've ever owned, but it has this nasty habit of failing me whenever I seem to need it the most.
For example, today I was stuck behind a huge accident on the highway with an exit coming up in a few feet. I thought, "hey I'll just see if I can find a detour around it from this exit." Pulled out my phone and quickly launched google maps. right then, it completely stops responding to all touch input; the trackpad and physical buttons work fine, but nothing was registering on the touchscreen or capacitive buttons. I eventually had to pull the battery to fix the issue.
It just seems that these things tend to happen whenever i need to lookup something quickly on the phone (when im just screwing around on it, it works perfectly fine) be it completely not responding to touch input, or something weird happening like getting stuck between 2 homescreens, or the notification panel gets stuck halfway down, or massive input lag (5+ seconds) to the point of it not being usable.
And everything goes back to normal after a reset; but by then, I usually don't need to lookup whatever it was anymore.
The most frustrating part is that I can't seem to figure out whats causing it. I'm running virtuous 2.0.0 without any sense 3 additions, and I generally only have 1 or 2 tasks going on on the phone at once (usually just music player + whatever I'm doing). I originally thought it was just a performance issue, so I've increased the clock up to 1.5ghz (using daemon controller) but it hasn't has of an effect.
Any ideas on what else i can try?
Sounds like simple bad karma, I suggest donating to a charity or going to church
Other than that, I'd have no idea, sorry. Seeing as its not totally regular, there'd be no good way to easily pinpoint the issue. Maybe see if the rom produces a last_kmsg?
-Nipqer
makken85 said:
Now I love my DZ; it is by far the most capable phone I've ever owned, but it has this nasty habit of failing me whenever I seem to need it the most.
For example, today I was stuck behind a huge accident on the highway with an exit coming up in a few feet. I thought, "hey I'll just see if I can find a detour around it from this exit." Pulled out my phone and quickly launched google maps. right then, it completely stops responding to all touch input; the trackpad and physical buttons work fine, but nothing was registering on the touchscreen or capacitive buttons. I eventually had to pull the battery to fix the issue.
It just seems that these things tend to happen whenever i need to lookup something quickly on the phone (when im just screwing around on it, it works perfectly fine) be it completely not responding to touch input, or something weird happening like getting stuck between 2 homescreens, or the notification panel gets stuck halfway down, or massive input lag (5+ seconds) to the point of it not being usable.
And everything goes back to normal after a reset; but by then, I usually don't need to lookup whatever it was anymore.
The most frustrating part is that I can't seem to figure out whats causing it. I'm running virtuous 2.0.0 without any sense 3 additions, and I generally only have 1 or 2 tasks going on on the phone at once (usually just music player + whatever I'm doing). I originally thought it was just a performance issue, so I've increased the clock up to 1.5ghz (using daemon controller) but it hasn't has of an effect.
Any ideas on what else i can try?
Click to expand...
Click to collapse
although people say roms are 'stable' and can recommend these ROMs as "dd" (daily drivers) you cannot say that will be completely reliable. This is because when people say a ROM is 'stable', it's only after using it for 2-3days; unfortunately, roms gather clutter and begin to slow down over time. Not a problem for many flashaholics, but a problem if you're a one-rom kinda guy (or girl). So if you're not one-night-stand rom kind of person, here are some tips:
Reset your phone regularly. Phones start acting funny when they've been on for too long
Try stock ROM with addons flashed on top of it, rather than baked in a new rom
Most reliable roms i've experienced are Stock Gingerbread or CyanogenMod. Try those
If you are flashing a new rom, use SuperWipe, this can help get rid of clutter from old roms
skulk3r said:
although people say roms are 'stable' and can recommend these ROMs as "dd" (daily drivers) you cannot say that will be completely reliable. This is because when people say a ROM is 'stable', it's only after using it for 2-3days; unfortunately, roms gather clutter and begin to slow down over time. Not a problem for many flashaholics, but a problem if you're a one-rom kinda guy (or girl). So if you're not one-night-stand rom kind of person, here are some tips:
Reset your phone regularly. Phones start acting funny when they've been on for too long
Try stock ROM with addons flashed on top of it, rather than baked in a new rom
Most reliable roms i've experienced are Stock Gingerbread or CyanogenMod. Try those
If you are flashing a new rom, use SuperWipe, this can help get rid of clutter from old roms
Click to expand...
Click to collapse
Hmm, so you believe that this is purely a rom issue?
I havent run a stock rom for a while, but from what i remember the experience wasnt that pleasant, there was significant lag almost everywhere in the ui. Although i will admit that was back with froyo; i havent tried a stock gb stock rom yet.
Ill probablygive cm7 a go. Ive just grown so used to some sense features that its going to be hard for me to give them up (mainly recent apps in notifications, news widget, t9 dailer+manually linking contacts, and remote ring and forward on htcsense.com)
Has anyone had similar issues running virtuous sense 2.0.0?
As far as recent apps goes, long pressing the home button is a standard feature of android that brings up the most recent. Stock is the last 8 (I think) cm7 can show 15.
Sent from my HTC Vision using xda premium
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
redpoint73 said:
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
Click to expand...
Click to collapse
I'd agree. I really wouldn't ever go over 1.2ghz for a daily driver personally.
I run my ROMs at 800mhz lol, so I don't see the advantage of a huge overclock unless you're just bragging about benchmark scores.
its funny when u wanna show off your phone and you take it out of your pocket acting all cool and stuff and when u press the power button it wont wake up or you get a blank screen
haha its just bad karma for u like nipqer said
Try the stock pre-rooted gingerbread...I just flashed t last week and it is way faster than my froyo was, and amazing battery life, for me anyways, I do have an extended life battery though lol. Anyways as far as speed it is snappy on 800 mhz
Sent from my T-Mobile G2 using XDA App
redpoint73 said:
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
Click to expand...
Click to collapse
I've noticed the random hangs / glitches @ 800Mhz and 1Ghz, so I'm hesitant to say that the OC is the cause.
What do you use for stability testing? I've been running quadrant nonstop to test new OCs, but I don't think that benchmark stresses the cpu enough.
i am running Virtuous v2.0.0 w/ kernel unity v6 on it on desire z.
i've found bugs like
1/the top black bar ui, top left corner, some times i see the background wallpaper rather than the black bar. but it goes away if i pull down the notifications.
2/ the mail with microsoft exchange active sync, if i delete the mail it will automatically resync and downloads all mail including the on i deleted. but i got around that by using pop/imac instead.
all rather minor as i got ways to go around it.
i did have a similar issue where the touch screen goes unresponsive and i had to force close it, restart phone to get it back alive. but then i readjusted the clock speed and never had it happened again.
the phone is at around 825mhz with governor smart ass on wake time max, unless im watching 720p movies on the phone then i ramp it up at 1.4ghz.
sleep time on 368mhz max with governor at conservative.
i had it on like this since 11/09/11 (as i made a rom backup) and it never occured yet.
swinderz said:
i am running Virtuous v2.0.0 w/ kernel unity v6 on it on desire z.
i've found bugs like
1/the top black bar ui, top left corner, some times i see the background wallpaper rather than the black bar. but it goes away if i pull down the notifications.
2/ the mail with microsoft exchange active sync, if i delete the mail it will automatically resync and downloads all mail including the on i deleted. but i got around that by using pop/imac instead.
all rather minor as i got ways to go around it.
i did have a similar issue where the touch screen goes unresponsive and i had to force close it, restart phone to get it back alive. but then i readjusted the clock speed and never had it happened again.
the phone is at around 825mhz with governor smart ass on wake time max, unless im watching 720p movies on the phone then i ramp it up at 1.4ghz.
sleep time on 368mhz max with governor at conservative.
i had it on like this since 11/09/11 (as i made a rom backup) and it never occured yet.
Click to expand...
Click to collapse
I've been playing with the wake min and wake gov settings the past few days. I have it set at 600Mhz min, performance gov; I haven't noticed much difference in the battery life, but I'll have to do more extensive testing to be sure.
Performance feels slightly better, especially after a fast wake. can anyone give a detailed explanation of the behavior of the different gov settings? I can't seem to find much info on it.
makken85 said:
I've been playing with the wake min and wake gov settings the past few days. I have it set at 600Mhz min, performance gov; I haven't noticed much difference in the battery life, but I'll have to do more extensive testing to be sure.
Performance feels slightly better, especially after a fast wake. can anyone give a detailed explanation of the behavior of the different gov settings? I can't seem to find much info on it.
Click to expand...
Click to collapse
http://www.droidforums.net/forum/droid-hacks/21309-setcpu-1-4-6-what-cpu-governor-options-mean.html
Hey guys,
I've test ICS and came across the need to do a supercharge.
Now I'm back to CM7.1 and I've been wondering what the method is to get it supercharged as well (and 7.2 KANG along the way).
The shell script part is pretty understandable, but I'm unable to understand whether or not I need to replace services.jar in the update zip. If I do need to do so, then which services.jar file do I need to put in there (there's a quite a few and some of them didn't work for me when I jumped and tried to do it myself).
Thanks in advance.
I made a guide for supercharging ICS with the proper services.jar for the nook here:
http://forum.xda-developers.com/showthread.php?t=1508481
Works like a charm, really.
If you want to use the script on any version of CM7, the ROM needs no modification. Leave the services.jar as is. The guide still works, skip to step 5 but just remember to unselect Lock Home in Memory in the device settings.
Look at the second post if you would rather the short and sweet version. The top post attempts to explain exactly what you are doing to your device and why.
Thanks for the quick reply.
It just so happens that I have followed (and bookmarked) your guide when getting my ICS
Unfortunately, I have tried the 3/3 Opengl and it had many lockups.
Any ICS you would recommend? (I know it's a bit off-topic, sorry).
Yeah, I know what you mean. I can't run OpenGL on a daily basis yet either. But the b
Yeah, I know what you mean. I can't run OpenGL on a daily basis yet either. But the builds without OpenGL work great. The threads can be a little hard to follow, what with their length and all the custom zips, I know, but he actual builds themselves are great.
I kept going back to 7.2 after checking in and trying a nightly. But maybe ten days ago, the audio from Nook Tweaks got patched, and know I can listen to movies and music at an acceptable level and I realized it was ready enough for me.
Really, the last thing on my list would be an enabled net filter, to run a firewall. But I am super-impressed with ROM.
Hope that helps. Just all of a sudden, it seemed ready.
Just to clarify, you're satisfied with the 3/3 rom w/o opengl?
Sent from my NookColor using XDA
Yep, I have been testing a bunch of programs on ICS over the last three weeks or so, and while flashing the nightlies over that time, the last couple things that I needed came through the repo. When the patch for the audio boost in Nook tweaks came through, I could use the movie and music players and finally hear them, which was a huge gain for the users. The VPN that I use works, Sync works. Almost every system app has been greatly improved.
Don't get me wrong, there are some big holes to be filled. Flash works only with OpenGL, which I find still to be too buggy and slow for daily use (although some have been reporting fine daily use), and I can't seem to find a firewall that blocks apps from the internet, which is a pet issue of mine. If you want to customize your launcher and overall look and feel, then those features will likely be the last to come around. I don use YouTube and the like hardly ever, but nonHD videos play only.
The progress is brisk, though. I spend maybe fifteen minutes upgrading the nightly as I go to bed at night, the builds seem to add a huge chunk of functionality every day.
One last tip I only recently discovered: people have complained about battery life, but I found it mostly analagous to cm7 with the major exception that deep sleep seemed fitful at best. I just realized that deep sleep doesn't seem to work when I shut the screen off manually. If I let it time out naturally (if it can be said to be natural, then it sleeps with no problem. Now battery life seems totally acceptable.
Just depends what you need to work, I guess, but this is my only real computer when I am away from home for work, and I use it daily now.