Hi,
I recently installed viperROM v2.1.1 Redline with Tiamat v1.1 Sense on my HTC EVO3D. So far I love it! It runs super smooth and I love many of the included features. I have set maximum overclock through vipercontrol to 1.56GHz. I have just a few questions:
1.) I have occasionally had my alarm not go off. One time I caught it come on the screen, but no sound even. Sometimes the screen didn't wake up at all. This hasn't happened in about a week, so hopefully it fixed itself. I've done a few cache and dalvik cache wipes. Has anyone else experienced this issue, or may know what caused it?
2.) I have occasionally had a black screen on some incoming calls. This also has not happened in about a week so hopefully it fixed itself.
3.) How do I know how far I can overclock on this ROM and still maintain stability? This is my first experience with this on Android phones. I am very familiar with overclocking computers though and I know there are programs to test the stability of your overclock. There seems to be no such thing with phones.
4.) I know everyone says Quadrant scores don't mean squat, but why are they so low on this ROM? It certainly feels faster.
5.) What does everyone think of this ROM compared to other EVO 3D Sense ROMs? Are there any others I should look at? I'm only really interested in Sense based ROMs, I know they are heavy, but I really love the GUI and the phone seems to handle it quite nicely.
Thank you everyone for your time, and to all the developers thank you for all your hard work!!
I also forgot to ask, how is TWRP 2.0? Is it worth flashing? I'm still using the old clockworkmod recovery because that's what I've been used to.
Get TWRP 2.0. Its nice.
Do you have any screen off profiles? If so set it to 192-486mhz or 384-486mhz so the screen can wake with no problems. Also, flash an Anthrax kernel and see if you get black screen errors while waking up the phone. I dont know if the tiamat kernel is built into the Rom but it may be outdated if you picked it from the Dev Section.
The quadrant score may have to deal with the mods and tweaks in the Rom. They dont always reflect the truth.
You may be able to overclock to 1782mhz. Most of our phones can do this. Try a program like setcpu and see if you can raise it higher but "uncheck" the boot option. If you clock high and the phone automatically freezes, it means the clock speed is too high so try again with a lower speed until good.
My Blog: knowledgexswag.tumblr.com
Twitter: @knowledge561
knowledge561 said:
Get TWRP 2.0. Its nice.
Do you have any screen off profiles? If so set it to 192-486mhz or 384-486mhz so the screen can wake with no problems. Also, flash an Anthrax kernel and see if you get black screen errors while waking up the phone. I dont know if the tiamat kernel is built into the Rom but it may be outdated if you picked it from the Dev Section.
The quadrant score may have to deal with the mods and tweaks in the Rom. They dont always reflect the truth.
You may be able to overclock to 1782mhz. Most of our phones can do this. Try a program like setcpu and see if you can raise it higher but "uncheck" the boot option. If you clock high and the phone automatically freezes, it means the clock speed is too high so try again with a lower speed until good.
My Blog: knowledgexswag.tumblr.com
Twitter: @knowledge561
Click to expand...
Click to collapse
I'll give TWRP 2.0 a try then.
I'm using vipercontrol to set the min and max freq. Right now it has it set at 192MHz for min freq. I actually tried the Anthrax kernel before and had constant screen wake issues even setting the min freq up to 486MHz. I then decided to use Tiamat kernel, which so far has been much more stable for me. I only had the screen wake issue a couple times on Tiamat. Anthrax would do it every 5 minutes no matter what I tried.
I might try 1782MHz tonight. Will having it overclocked too much cause the battery to drain significantly faster? Or since most the time the phone is sleeping and not running at full speed it won't matter much?
Thanks for all your help!
Decided to try 1782MHz now, seems to be working great!
Graphics on my N64oid games seem to be smoother now.
Overclocking will drain it a bit quicker. Ive decided not to set any custom clock speeds or profiles at all. I kept a stock kernel and did nothing to it.
My Blog: knowledgexswag.tumblr.com
Twitter: @knowledge561
knowledge561 said:
Get TWRP 2.0. Its nice.
Do you have any screen off profiles? If so set it to 192-486mhz or 384-486mhz so the screen can wake with no problems. Also, flash an Anthrax kernel and see if you get black screen errors while waking up the phone. I dont know if the tiamat kernel is built into the Rom but it may be outdated if you picked it from the Dev Section.
The quadrant score may have to deal with the mods and tweaks in the Rom. They dont always reflect the truth.
You may be able to overclock to 1782mhz. Most of our phones can do this. Try a program like setcpu and see if you can raise it higher but "uncheck" the boot option. If you clock high and the phone automatically freezes, it means the clock speed is too high so try again with a lower speed until good.
My Blog: knowledgexswag.tumblr.com
Twitter: @knowledge561
Click to expand...
Click to collapse
First of all, not picking at you, just the first post I read and don’t have a lot of time here
The black screen errors are an issue within the kernel. Last time I used tiamat this was still a common bug in the kernel. You can fix it by downloading and installing and setting up a call recording app by the dev “voix” or something like that… don’t use the one on the market because it will do nothing for you. You need to download the one specific to 3D. it is found on the dev’s website.
Quadrant scores should be taken with a grain of salt. Depends on the ROM. I will state however that quadrant’s database read and write tests are accurate with real performance in that function of your ROM. I have personally tested this theory. Also, your database read/write tests contribute to a lot of the scoring in your overall performance summary with the free version. Just keep that in mind.
Don’t use set CPU, it is a good program, but designed for single core applications. Use system tuner pro, CPU master pro, or No Frills cpu. All of those are WAY more in depth and offer other adjustable variables that are critical for performance like setting the I/O scheduler.
Also, you need to manually adjust cpu1’s operating parameters, because when that CPU turns on and off constantly, it slows down your phone, causes lag, all this bull****. I cant figure out why it was programmed from the factory the way it was. It makes no sense whatsoever to have the two cores running two separate scaling governors. Set it to demand in root explorer by adding this line to init.d or init.post_boot.sh…
chmod 666 /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo “ondemand” > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
also, in init.d or init.post_boot.sh, adjust your ondemand parameters to match your settings in CPU master, system tuner pro, etc…
you will see a line like this (for “cpu0” and “cpu1”)…
echo “60000” > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate
change that value to 10000.
You will also see one similar for the up threshold… the end of it will read “…ondemand/up_threshold” with a value at the beginning probably of 95 or 90…
Change that value to 70
Basically, you should set both cores to ondemand, and tune that governor for performance by adjusting it’s operating parameters. Very responsive, good balance of performance and battery with a little more weight on the performance side of the scale.
---------- Post added at 03:34 PM ---------- Previous post was at 03:29 PM ----------
EDIT*** also, the two lines i gave you to add, put them in before any lines with "system chown" in them.
honestly man, if you want i can just email you a copy of my init.post_boot.sh, and init.d files, and you can just delete yours and add mine. lol.
i have them saved on my sd card so every time i flash a rom i remove the dev's tuning parameters and add my own, lol
the kernel is reason your phone is having wake issues another reason viper suggests using a minimum 384 on sleep helps prevent the wake issues.
Sent from my HTC Evo 3D using xda premium
Bradfordv said:
the kernel is reason your phone is having wake issues another reason viper suggests using a minimum 384 on sleep helps prevent the wake issues.
Sent from my HTC Evo 3D using xda premium
Click to expand...
Click to collapse
Is there something wrong with Tiamat kernel? I thought it was supposed to be one of the better kernel's for our phone?
Related
Title says a helluva lot ;-)
READ THIS WHOLE POST AND THE WHOLE POST AFTER IT!
Features:
All steps undervolted about 25%. Should be stable still
The table is currently 300, 600, 950mhz until I can make it scale more than 3 steps.
The voltage for 950Mhz is less than at stock for 800Mhz, so you should see better battery life even though we're overclocked.
Display flicker fixed (or at least toned down, it can't be completely eliminated with the LED backlighting)
Scheduler tweaks backported from later kernel versions
Some governor tweaks of my own for responsiveness
To install this, just flash the zip in ClockworkMod. This shouldn't harm your device, but I make no promises. I trust it enough to run it on my device, if that means anything to y'all. I also attached a zip to flash back to the stock kernel (..but why would you break my heart by doing so..? ;P).
Next Up:
I REALLY want to get 1Ghz+ working, and my code is sound (I'm sure of that) but it won't boot on my device. I think I just need to find the right voltage, or I could have a bad die for OC'ing. This is the first thing I will work on.
Maybe the interactive CPU governor
Look into the 2-point touch limitation
Source:
Source is available on my GitHub at https://github.com/geniusdog254/Quickie
I will not flat out ask for donations, however I do appreciate them. So if you're feeling generous or appreciate my work then it would help me out a lot if you could donate. I have my game Reflex-A-Tron on the Market for $1 if you'd like to donate like that, or there is a link under my name on the left side to donate, and one in my signature. The one on the left and in my signature is to donate via PayPal. Any amount is appreciated, but please don't feel obligated.
You can contact me here via PM, on Twitter @geniusdog254, or email me at [email protected]. Email or Twitter is the preferred method, because I really despise the XDA PM system.
Disclaimer:
If this breaks your Nook, kills your family/pets, or starts global thermonuclear war, do not blame me. You have been warned. If you break your device and blame me, I will point at you and laugh.
Changelog:
1-11-11 - Screamer:
Overclock to 950Mhz. Still chokes at 1Ghz, which tells me it's probably my device. 950 is stable.
Temp sensor drivers. Thanks to the Nookie FroYo guys!
Updated to 2.6.29.6.
Scheduling tweaks from 2.6.31.
Code idle time from 2.6.34.
Scaling fixed. Now scales properly between all 3 CPU levels. Adding more than 3 makes it choke for some reason. I'll look into it.
Test version set at 1Ghz added. Just because it doesn't work for me doesn't mean it won't work for you. Don't get your hopes up though, I've tried making it work every way from Sunday
Notes:
Screen WILL be unresponsive immediately after a boot. Just lock the device for several seconds, unlock it, and all will be fine until another reboot. I blame B&N, it happens with all custom kernels.
Yes, I know there are more versions of this kernel than there are Windows Vista. The middle one is the recommended one. If your Nook can't run at 950Mhz (crashing often, or just won't boot) try the one with the 900mhz tag. If you wanna try and push it higher, try the 1Ghz one. Be warned: very little success is reported with the 1Ghz kernel. The top level of these chips seems to be right around ~925-975Mhz. Very few devices will be able to hit 1Ghz.
You should probably wipe your cache partition after flashing this. You won't lose anything, and many people are reporting that it makes things more stable at the higher freqs for them.
MD5 Sums:
stock-1.0.1-kernel.zip — 78ccf8ab0cd35b988cc9a81bd8bbc310
quickie-1ghz-test.zip — 7076a88cae2229910478e698c0e19435
quickie-screamer.zip — 22e8c2cc21e42cca1d18377a92b49540
quickie-900mhz.zip — 40362515da86cb4baea37b0bc6358feb
Wow thanks so much for this. Gotta try it out!
wow very nice! going to have to give this a shot!
Awesome! But is it compatible with nookie froyo (2.2) or the stock BN (2.1)?
Update: It boots Nookie Froyo but powers off immediately after booting. I am looking forward to the release of the 2.6.32 version of your work. Keep up the good work!
Sent from Nook Color (Nookie Froyo microSd optional)
runhopskipjump said:
Awesome! But is it compatible with nookie froyo (2.2) or the stock BN (2.1)?
Sent from Nook Color (Nookie Froyo on emmc)
Click to expand...
Click to collapse
Just stock 2.1.
With the Nookie FroYo, it wouldn't flash the kernel to the SD for boot, plus (at least on th Epic) a 2.6.29 kernel won't boot on FroYo, it needs 2.6.32 or higher
Glad to have you part of the nook color family. You did awesome work on the Epic4G.
Looking forward to more great stuff from you.
Thanks
Sent from my LogicPD Zoom2 using Tapatalk
Loss of touch sensitivity
I loaded up the new kernel via Clockwork and all went smoothly with the install. I noticed immediately that my touch sensitivity has decreased. I now have to press and hold just about as long as you would press and hold to bring up a context menu or something. If I don't do that, my touch is ignored and not registered.
Interestingly enough, when I type an email on the keyboard, it recognizes my typing very quickly. No apparent loss of sensitivity when I'm using the keyboard. I wonder why and how that is???
I guess I need to recalibrate the screen again to regain sensitivity.
I did notice that Castle Crashers frame-rate has improved a good bit with the overclock. It's a noticeable and welcome difference.
Angry birds was a bit annoying to play with the loss of screen sensitivity.
Edit: I alleviated the loss of touch sensitivity by installing the LCDDensity app from the Android Marketplace and selecting a density of 200.
Tried to install via clockwork and I keep getting errors unable to install. an I missing something?
sent from my nookcolor using the xda app
Got it working with clockwork update... thanks!
Flashed. Am loving it, seems much snappier, and the keyboard response at 900mhzz is much improved. Keep up the good work!
NC overcklock
Hi,
Last month I made some tests with overcloking /undervolting. I was able to push the NC at 1.15GHz, with a little voltage tweaking. 1Ghz was achieved without voltage tuning. The smartreflex technology adjusts automaticaly the OPP voltages to minimize the power consumption. Maybe the L3 speed can be increased to 200 Mhz by setting DPLL at 400MHz (in u-boot).
Occip (working for 2.6.32 NC kernel)
deitiphobia said:
I loaded up the new kernel via Clockwork and all went smoothly with the install. I noticed immediately that my touch sensitivity has decreased. I now have to press and hold just about as long as you would press and hold to bring up a context menu or something. If I don't do that, my touch is ignored and not registered.
Interestingly enough, when I type an email on the keyboard, it recognizes my typing very quickly. No apparent loss of sensitivity when I'm using the keyboard. I wonder why and how that is???
I guess I need to recalibrate the screen again to regain sensitivity.
I did notice that Castle Crashers frame-rate has improved a good bit with the overclock. It's a noticeable and welcome difference.
Angry birds was a bit annoying to play with the loss of screen sensitivity.
Edit: I alleviated the loss of touch sensitivity by installing the LCDDensity app from the Android Marketplace and selecting a density of 200.
Click to expand...
Click to collapse
me too, seems touch for a while(XXms) take effect, less then that screen acts like nothing touch it. this drived me mad when using Gellery, switch pictures give terrible feeling.
i think this relay to the clock scaling, i will check this out using SetCPU.
thanks for your work!
Amazing work with the kernal. I flashed and changed density to 200 in Root Explorer /system/build.prop and it works great.
Also in Spare parts I change both animations to Fast instead of defaults.
occip said:
Hi,
Last month I made some tests with overcloking /undervolting. I was able to push the NC at 1.15GHz, with a little voltage tweaking. 1Ghz was achieved without voltage tuning. The smartreflex technology adjusts automaticaly the OPP voltages to minimize the power consumption. Maybe the L3 speed can be increased to 200 Mhz by setting DPLL at 400MHz (in u-boot).
Occip (working for 2.6.32 NC kernel)
Click to expand...
Click to collapse
Can you add me in GTalk? [email protected]
I have some stuff I'd like to ask about. How did you do the OC? Did you change the actual clock in u-boot so everything scales up? Or did you add more VDD_OPP* steps. I used some of the code I saw before for the Droid's 3430 chipset, using the OPP steps. The stock kernel has steps built in for up to 1.2Ghz, but if I enable them I can't make it boot, at least on my device.
I can't figure out the voltages either, probably because I fail at hex. If I understood that, it would help me a lot.
sugwacee said:
me too, seems touch for a while(XXms) take effect, less then that screen acts like nothing touch it. this drived me mad when using Gellery, switch pictures give terrible feeling.
i think this relay to the clock scaling, i will check this out using SetCPU.
thanks for your work!
Click to expand...
Click to collapse
Hrrm. It sounds like the CPU scaling is staying low, because I see absolutely no change in the touch sensitivity, and I didn't touch any of the code related to it. Try setting the CPU Governor to OnDemand or Performance in SetCPU if it isn't set there already.
Geniusdog254 said:
Can you add me in GTalk? [email protected]
I have some stuff I'd like to ask about. How did you do the OC? Did you change the actual clock in u-boot so everything scales up? Or did you add more VDD_OPP* steps. I used some of the code I saw before for the Droid's 3430 chipset, using the OPP steps. The stock kernel has steps built in for up to 1.2Ghz, but if I enable them I can't make it boot, at least on my device.
I can't figure out the voltages either, probably because I fail at hex. If I understood that, it would help me a lot.
Click to expand...
Click to collapse
diff is available http://nookdevs.com/NookColor:_Nookie_Froyo_Tips#Overclock_.5B100.25_untested_on_this_system.5D
occip said:
diff is available http://nookdevs.com/NookColor:_Nookie_Froyo_Tips#Overclock_.5B100.25_untested_on_this_system.5D
Click to expand...
Click to collapse
Odd. That's exactly what I've done (with a couple diff voltages) but it won't boot on my Nook. I guess I just got a bad die. Can you explain the voltage values? I know how to increase/decrease the hex number, but how does it correlate to the actual voltage? Like how is 0x38 = 1.35V in a stock kernel?
Definitely going to try this out. Thanks for the work. I'll report back with comments/questions/concerns.
nrune said:
Tried to install via clockwork and I keep getting errors unable to install. an I missing something?
sent from my nookcolor using the xda app
Click to expand...
Click to collapse
+1 I am getting the same. It installs half way then stops with a big exclamation mark, asks me to shut down and restart. I would love to try this. Any ideas?
EDIT: OK got it. CWM updated to 3005 and now it can go into recovery was on 3002 which did not.
This is very much appreciated.
Be expecting some monies so you can buy some candy in the near future.
keep up the good work.
Thanks!
Samsung Fascinate CDMA
Rooted MIUI 1.9.16
Did a brief search here looking to understand how to operate overclocking kernals, but find it/me relatively limited.
I have installed and ran Glitch v11 and v12, played around with HL to LL, and made adjustments to undervoltage utilizing Pimp My CPU and Voltage Control. I have also ran Tweak (though not really a kernal).
My question is this,
am I overclocking when I reduce voltage on Mhz's above 1,000?
If not, could someone point me to, or explain how to achieve overclocking on our phones, and
which kernel and governor do you prefer for overclocking?
As an ammended note, I've installed Tegrak Overclock, but am still looking for a user guide...
Thank you for your time.
If you're the running the glitch kernel...use voltage control, not tegrak overclock...over clocking is when you turn the CPU speed above its normal speed..anything over 1GHz.
under volting is when you turn down the voltage frequency to achieve better battery life...
Any one clock speed may perform more or less stable with different under volting unfortunately all of our phones will vary in performance so one setting that works for one may not be the best for another so experimentation is really the best option...this applies for schedulers and governors as well.
I personally overclock as high as I can until it freezes or crashes..then I go 1 setting down...I then try undervolting different steps observing the stability of my phone...when I find what I like,I run it for a few days, then if its still nice and stable I will apply on boot.
The different leakage values are affected by the hardware quality of the chips in our phones which also vary..I start with high and see how high I can overclock..note the setting, then try medium..see how high I can overclock and so on...just as a reference..high leakage creates the most heat and is the least efficient, but works for most phones, while low leakage is the most efficient and generates the least heat and will work with not as many phones
Sent from my SCH-I500 using XDA App
efan450 said:
If you're the running the glitch kernel...use voltage control, not tegrak overclock...over clocking is when you turn the CPU speed above its normal speed..anything over 1GHz.
under volting is when you turn down the voltage frequency to achieve better battery life...
Any one clock speed may perform more or less stable with different under volting unfortunately all of our phones will vary in performance so one setting that works for one may not be the best for another so experimentation is really the best option...this applies for schedulers and governors as well.
I personally overclock as high as I can until it freezes or crashes..then I go 1 setting down...I then try undervolting different steps observing the stability of my phone...when I find what I like,I run it for a few days, then if its still nice and stable I will apply on boot.
The different leakage values are affected by the hardware quality of the chips in our phones which also vary..I start with high and see how high I can overclock..note the setting, then try medium..see how high I can overclock and so on...just as a reference..high leakage creates the most heat and is the least efficient, but works for most phones, while low leakage is the most efficient and generates the least heat and will work with not as many phones
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Efan450,
Thanks.
How do you over-clock using Glitch and Voltage Control? I see that Voltage Control goes up to 1,300Mhz, but it's at 0 above 1,000Mhz and can be dropped down to -200mV. Is overclocking just the process of decreasing that voltage on Mhz's above 1,000Mhz's
FJRSport said:
Efan450,
Thanks.
How do you over-clock using Glitch and Voltage Control? I see that Voltage Control goes up to 1,300Mhz, but it's at 0 above 1,000Mhz and can be dropped down to -200mV. Is overclocking just the process of decreasing that voltage on Mhz's above 1,000Mhz's
Click to expand...
Click to collapse
come on man.. Clock speed (mhz) and undervolting are 2 completely different things.. Forget the voltage.. No changing the voltage is NOT overclocking.. You overclock by changing your maximum clock above 1000mhz which is stock for this phone.. Try long pressing 1200mhz and selecting set as max.. Now your overclocked to 1200mhz..
Sent from the fascinate that holds the record benchmark on antutu
No decreasing the voltage is simply undervolting whether it's over 1000 or under. The idea behind undervolting is increasing battery life, but you can't necessarily go and set each level to the maximum undervolt (200) you half to see what works. Increasing the processor speed is overclocking, stock speed is 1000 so anything over that is over clocked. As far as how far as how far you can over clock depends mostly on 2 things, 1. the kernel your using, ( for example if it shows 1300 in the list that means thats all that specific kernel supports) 2. It varys greatly between phones. For example with glitch you can overclock to 1700 but very few phones can run that high for longer than a few minutes!
Hope that helps.
Sent from my SCH-I500 using xda premium
Yes.. And the fact you say your running glitch and your max oc is only 1300 my guess is you broke your kernel with tegrak overclocks module.. Delete tegrak and stop downloading overclock apps. or any other root app unless you know fully the consequences first.. If after deleting tegrak, and rebooting, if your voltage control don't show a maximum clock of 1700 mhz, then you will need to reflash your glitch kernel
Sent from the fascinate that holds the record benchmark on antutu
Neh4pres,
Yeah, I kind of feel like a heel. For some reason, I had a brain fart when looking in the 'General' section of Voltage Control. I see now how to overclock.
Regarding ost #6:
When I flashed MIUI 1.9.16, I did not install any kernel; so it was kind of a half truth in that while running 1.9.9 I did have Glitch installd. Nevertheless, I still have Voltage Control installed.
mkropf,
I see that now, and thought as such earlier, but needed some clarification.
Having so many issues with Glitch and 1.9.9, I'm hesitant to install Glitch, but interested to see if it runs better on the newer MIUI...
Thank you two for answering my newbie questions.
FJRSport said:
Neh4pres,
Yeah, I kind of feel like a heel. For some reason, I had a brain fart when looking in the 'General' section of Voltage Control. I see now how to overclock.
Regarding ost #6:
When I flashed MIUI 1.9.16, I did not install any kernel; so it was kind of a half truth in that while running 1.9.9 I did have Glitch installd. Nevertheless, I still have Voltage Control installed.
mkropf,
I see that now, and thought as such earlier, but needed some clarification.
Having so many issues with Glitch and 1.9.9, I'm hesitant to install Glitch, but interested to see if it runs better on the newer MIUI...
Thank you two for answering my newbie questions.
Click to expand...
Click to collapse
There are no issues with glitch.. It is what I run.. Very smooth.. Just have to give your phone time to adjust and build cache
Sent from the fascinate that holds the record benchmark on antutu
Landscape
Re-installed Glitch v12 ML last night and have it overclocked @ 1,200 with no under-voltage...yet. Want to see any adverse effects.
I started at 1,300 and it locked up then rebooted within 5 minutes.
A concern I have is that now my phone will not Auto Rotate to Landscape even though I have Auto-Rotate 'on' in Settings.
I've scoured Sixstrings Glitch thread to no avail. Though it's not needed anymore, I also flashed the cleaning script just to see if it would make a difference.
Is there a work around or fix for this?
Make sure you're on the latest 9/15 version of the kernel. Anything before that will kill all of your phone's sensors.
http://forum.xda-developers.com/showthread.php?t=1252871
sageDieu said:
Make sure you're on the latest 9/15 version of the kernel. Anything before that will kill all of your phone's sensors.
http://forum.xda-developers.com/showthread.php?t=1252871
Click to expand...
Click to collapse
That was it. I had re-installed the older Glitch v12 that was already on my PC. Deleted them and downloaded the newer Glitch kernels to experiment with.
Thanks!
FJRSport said:
Re-installed Glitch v12 ML last night and have it overclocked @ 1,200 with no under-voltage...yet. Want to see any adverse effects.
I started at 1,300 and it locked up then rebooted within 5 minutes.
A concern I have is that now my phone will not Auto Rotate to Landscape even though I have Auto-Rotate 'on' in Settings.
I've scoured Sixstrings Glitch thread to no avail. Though it's not needed anymore, I also flashed the cleaning script just to see if it would make a difference.
Is there a work around or fix for this?
Click to expand...
Click to collapse
under volting helps stability.. I use -50 for everything above 1ghz.. Your phone may vary
Sent from the fascinate that holds the record benchmark on antutu
OC & UV settings
neh4pres said:
under volting helps stability.. I use -50 for everything above 1ghz.. Your phone may vary
Sent from the fascinate that holds the record benchmark on antutu
Click to expand...
Click to collapse
Yeah, locking and rebooting was while using the older version of Glitch v12. With the 9/15 dated Glitch I'm at 1300 now with the following settings:
Deadline / ondemand
200 - 1300
1300 -25
1200 -25
1000 -50
800 -50
400 -75
200 -75
1.2GHz is the best I say if you want good battery with a higher frequency. 1.4GHz is the best for anyone who uses their phone alot. Samsung did add 1.2GHz overclock in their source.
Sent from my SCH-I500 using XDA App
Back to running MIUI without Glitch.
Things that make you go, Hmmm?
For some reason, every time I accessed the keyboard for Google+, it hung, then froze, and 3 of the four times rebooted. The fourth time I needed to remove the battery to reboot. So I re-flashed MIUI 1.9.16 (effectively removing Glitch) and have 0 problems.
Bummer, I like Glitch too.
I'm in the same boat, however they redone the latest glitch merge and posted it last night so I'm thinking we'll be back in good times
Sent from the most custom, custom rom Miui 1.9.16 and currently the best kernel Jt
mkropf said:
I'm in the same boat, however they redone the latest glitch merge and posted it last night so I'm thinking we'll be back in good times
Sent from the most custom, custom rom Miui 1.9.16 and currently the best kernel Jt
Click to expand...
Click to collapse
are you using JT's 9/12 kernel?
if so...did you overclock it?
i'm on jt's 9/12 with miui 1.9.16 and wondering if I can / should overclock and undervolt it. I'm just trying to maximize battery life at this point.
Try the new glitch posted last night, it is fantastic.
Sent from my MIUI SCH-i500
sageDieu said:
Try the new glitch posted last night, it is fantastic.
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
what voltages are you running?
also for anyone..
is there any way to directly compare two kernels? like a test or something?
I can't decide between JT's 9/12 and the new glitch..
worshipNtribute said:
what voltages are you running?
also for anyone..
is there any way to directly compare two kernels? like a test or something?
I can't decide between JT's 9/12 and the new glitch..
Click to expand...
Click to collapse
You wouldn't want to use my voltages, I put everything way lower than anybody else does or recommends and am just lucky that it is stable for me but it causes the sleep of death for anyone else.
For comparison, just run JT's kernel for a bit and then flash glitch and try it... once you play with OC/UV and voodoo color you won't be able to go back. (you'll be able to but you'd have to be insane.)
So I'm interested in undervolting using the stock CPU freq's, and I'm going to be using setCPU (obvi).
So, first question: Even if I want to use the stock frequencies, do I have to be using the OC kernel (0.2.1/1.45ghz at the time)? And then adjust the max to 1000mhz?
Second, I started up SetCPU and whenever I go to the voltage tab it forcecloses. This happens with both the stock enhanced & OC kernel, and I've tried fixing permissions to no avail.
All I really understand so far is that the end result is a table of CPU frequencies and linked voltages. I've OCed the hell out of desktops, but I'm lost here.
I'd just like to know how to get from starting up setcpu to ultimately popping out that new voltage/freq table.
I do apologize if this seems kinda stupid, I'm just trying to exercise caution lest I demolish my phone's innards. I've done it with many an intel.
If you just want stock frequencies, then there's no need for a custom kernel. I guess in that case, you could just use SetCPU for undervolting & profiles.
However, if you want overclock, you'll need a custom kernel.
If you're going to be using a overclocked kernel (i.e. the new Faux 1.45 GHz), then you will need to set the max to 1.45 GHz, and make sure SetCPU is set to start on boot; other wise it will stay at the stock clock speed of 1 GHz... So i guess if you only wanted the OC at certain times, you could set the max speed manually, only when you want to, and not select to start on boot.
I haven't really had any success with undervolting yet... always crashes on me & reboots. The best thing to do is make sure "set to boot" is not selected, when testing your undervolting, other wise you could get stuck in a loop, with the phone crashing every time it boots and tries to apply you undervolting values. I'd start at -25 for each and work from there... stress testing each choice with a benchmark app to make sure you wont reboot... if it reboots, then you know your undervolt was to much. Also remember that you can not undervolt more than -100 between each frequency, otherwise the undervolting will not make any difference.
I really like the profile options in SetCPU... you can set the screen off frequencies to the lowest two, that way for whatever reason your phone isn't running at full strength while your not using it. Also, you can set frequency speeds at custom defined battery levels.
Hope this helps somewhat.
It's unclear to me why it force closes. This may be a rom incompatibility or a SuperUser issue? I assume you've tried uninstalling it and reinstalling it? Updating your SU app? Try flashing to the latest Aura rom?
A few quick words about SetCPU:
1. When you first get started, do not set to "Set on Boot" in case you've undervolted too much and it crashes when applied. You can always check it later once you know the voltages are stable.
2. Between each frequency step there is a maximum of 100mV step off. Anything greater than that it defaults to native voltage. I think this is a Tegra2 issue.
With that said, undervolting is simple: simply slide the little slider on SetCPU to negative values. How much you can under-volt largely depends on your particular hardware and it is inconsistent across all Atrix's. My voltage table is as belows:
1000mhz: -50
912: -50
750: -50
608: -75
456: -75
312: -100
216: -100
I, however, did not test the limits of my phone. Many people will slowly increment the voltage lower until they start to get resets, and then they'll move it back to find the lowest stable point.
It has, however, been well established that minor undervolting improves battery life and diminishes heat generation. Excessive undervolting may actually hurt battery life. You can look around on this forum regarding the data. However, reasonable undervolting will improve battery life.
Thanks fellas, this helps A LOT.
I was so afraid I'd get 17 responses of "You're such a noob. Stop cluttering the forums" etc etc
At this point, I think that the problem is, for whatever reason, the FC when I tap the voltages tab.
I'm on the newest Aura (1.2.2.1) newest enhanced stock kernel from Faux123 (0.2.1) and the newest SetCPU (2.4). I'll try updating my SU (though I believe I did that right after I flashed.
I'll reintall SetCPU and report back.
Until then, THANKS BUCKETS fellas. I really appreciate the info and advice.
UPDATE: May have found the problem. When it first boots up it prompts to autodetect freq's or choose them manually (or something like that). I was afraid this would actually alter my CPU clocks right then and there and so I hit manual detect, saw something that said Tegra2 etc and clicked it. I just now hit 'menu' and set it to autodetect, tried the voltages tab, and no FC, so I think that's solved.
Thanks again for all the info guys! I'll start experimenting and let you know HOW LOW I CAN GO (ha).
You guys get force closes due to kernel problems. You have to ask your developments. There might be something wrong with some of your cpu voltage drivers. So yeah that's why just a tip. Only overclock when you're playing some high end game. If not stick to normal. If not your phone might get overheated and damaged
Accidentally sent from my Ultra-speedy SG3 using Tapatalk
AdiNova said:
You guys get force closes due to kernel problems. You have to ask your developments. There might be something wrong with some of your cpu voltage drivers. So yeah that's why just a tip. Only overclock when you're playing some high end game. If not stick to normal. If not your phone might get overheated and damaged
Accidentally sent from my Ultra-speedy SG3 using Tapatalk
Click to expand...
Click to collapse
It's cool bro the problem was totally a user goof by me. I kind of agree with your OC philosophy though, primarily because 1ghz with this proc an RAM seems ample and I don't do much gaming.
Real quick:
When undervolting, should I do it one freq step at a time? Or can I do ALL of them at say -25, stress test, then adjust? Also, what's a good stress test that'll force the proc to hit all the different freqs instead of just the max clock and then the minimum when it's idling/the screen is off?
xyrovice said:
It's cool bro the problem was totally a user goof by me. I kind of agree with your OC philosophy though, primarily because 1ghz with this proc an RAM seems ample and I don't do much gaming.
Real quick:
When undervolting, should I do it one freq step at a time? Or can I do ALL of them at say -25, stress test, then adjust? Also, what's a good stress test that'll force the proc to hit all the different freqs instead of just the max clock and then the minimum when it's idling/the screen is off?
Click to expand...
Click to collapse
Id start at -25 for all. Setcpu has a built in stress test under info, I think. Could also try a benchmark to test it. As general rule if thumb, then lower frequencies can be undervolted more, while the higher ones take some tweaking... I can't even do -25 on my 1000, b/c ill eventually get a reboot, maybe not right away, but eventually. Every device is unique when it comes to undervolting.... just remember to not set the undervolt part to auto on boot, until you get it somewhat stable.
Sent from my MB860 using xda premium
Swiftks said:
Id start at -25 for all. Setcpu has a built in stress test under info, I think. Could also try a benchmark to test it. As general rule if thumb, then lower frequencies can be undervolted more, while the higher ones take some tweaking... I can't even do -25 on my 1000, b/c ill eventually get a reboot, maybe not right away, but eventually. Every device is unique when it comes to undervolting.... just remember to not set the undervolt part to auto on boot, until you get it somewhat stable.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Got it. I figure that 'set on boot' checkbox is basically a wedding ring ha. Thanks for the advice and insight my friend.
Also (as I run my first stress test with -25 across the board) if I get reboots early on, should I assume it's the higher voltages and that I should back off on the fast end of the clocks?
xyrovice said:
Got it. I figure that 'set on boot' checkbox is basically a wedding ring ha. Thanks for the advice and insight my friend.
Also (as I run my first stress test with -25 across the board) if I get reboots early on, should I assume it's the higher voltages and that I should back off on the fast end of the clocks?
Click to expand...
Click to collapse
When testing each frequency just set your min/max mHz to the level your testing i.e. min/max=1000. UV and stress test at that frequency and if it's stable, move to min/max=912 and so on.
FYI, my MHz might be different than yours, I'm on the stock enhanced.
ghost_og said:
When testing each frequency just set your min/max mHz to the level your testing i.e. min/max=1000. UV and stress test at that frequency and if it's stable, move to min/max=912 and so on.
FYI, my MHz might be different than yours, I'm on the stock enhanced.
Click to expand...
Click to collapse
That makes perfect sense- limiting the max during the stress test. Thanks for the tip bro I really appreciate it.
Okay, I looked at what ziggy and cron247 did over on XDA and tried to make it better.
This kernel is unsecured, meaning adb connects with root.
It OverClock's up to 1.836MHz.
It has the SmartAss V2 governor.
It uses my ramdisk, not the one you have. I cannot forsee this being an issue. If it becomes one, let me know.
Updates:
Version 1.1.3 changes the version of lagfree, the old one was having issues. Also removes forcing the second CPU to be online which was causing choppiness.
Version 1.1.2 adds increased read ahead, writeback tweaks, decreased dirty ratio settings, simple I/O scheduler, and the lagfree governor.
Version 1.0.5 adds mpdecision fix by Mr X, thank you whoever you are, if you removed mpdecision, put it back. Also added voltage control for you UV lovers.
The only control program I have tested to work is AnTuTu CPU Master (Free), I have had issues with SetCPU and a few others. This one does speed, governor, and voltage all very well.
Get it here: AnTuTu CPU Master (Free)
The following problems seem to be fixed at this point: governor and speed settings not sticking, smartass staying at top speed, random reboots or bootloops overnight.
READ THE INSTRUCTIONS, THIS IS A SINGLE FILE
To install this kernel:
Copy the file to the root of your SDcard.
Reboot into recovery (CWR or AmonRa).
Flash the file from the SDcard.
At the end of the flash the phone will reboot to fastboot.
Once fastboot loads, tap PWR to get to HBOOT.
HBOOT will find the update and ask you to install.
Tap Vol Up to begin the install.
When it finishes it will say tap PWR to reboot. Do it.
After the phone boots remove the PH98IMG.zip file from your SDcard.
Use AnTuTu CPU Master (Free) to set min/max/gov/voltage.
Enjoy!
Thanks to ziggy and con247 for getting us started and having stuff out there for me to get ideas from.
Download:
Link: dsb9938 Kernel 1.1.3
MD5: a2558e70f9af572f43e258c9aedb4b40
Source on GitHub.
My favorite Rezound kernel so far. Haven't had one crash, even at max OC. Thanks so much guys at BAMF!
This kernel has been good to me too.
I just wish I could get a handle on thie weird issue. Any of these other than stock kernels seem to have the minimum cpu speed jump up to the max cpu speed, then back down constantly, and I cant figure out the deal.
I can check on mine periodically and my min says 192, than a couple seconds later it says its the same as my max. Ugh.
dccoh said:
This kernel has been good to me too.
I just wish I could get a handle on thie weird issue. Any of these other than stock kernels seem to have the minimum cpu speed jump up to the max cpu speed, then back down constantly, and I cant figure out the deal.
I can check on mine periodically and my min says 192, than a couple seconds later it says its the same as my max. Ugh.
Click to expand...
Click to collapse
I noticed that as well
I also had a problem yesterday morning where my phone locked up when my alarm clock went off - forcing me to pull the battery to turn the sound off - not sure if that's kernel or ROM related (running CleanROM 1.5)
Argent36 said:
I noticed that as well
I also had a problem yesterday morning where my phone locked up when my alarm clock went off - forcing me to pull the battery to turn the sound off - not sure if that's kernel or ROM related (running CleanROM 1.5)
Click to expand...
Click to collapse
It's kernel related; I'm running rezrom and had the same exact issue with my alarm running this kernel.
Do you think ziggys is more stable?.. or do I just need to find the right overclock/underclock settings?
I seem to recall seeing them have that problem on ziggy's - but I never had that problem on earlier versions of dsb's - so maybe it's just something that is fixable for the next release
*wanders off to test it again*
This is no doubt me doing things wrong that led to this, but I downloaded the kernel through the phone browser, then flashed it from the download directory on the internal SD. When I flashed Incredikernel from there it copied the PH98 to the sdcard, but no dice on this kernel until I copied it to the sdcard then flashed it.
I probably should have copied it to the sd card myself first anyway, but I figured I would let you know!
Well this morning - my alarm clock went off - I was able to snooze it - and then a few minutes later the phone went in to boot loops - had been running stable all weekend - once I pulled the battery the phone booted back up just fine.
we'll see if it repeats this behavior tomorrow morning or not...
Call recording support in the kernel?
timp123 said:
Call recording support in the kernel?
Click to expand...
Click to collapse
Nope, only Ziggy's kernel currently supports this.
I only set one alarm at a time usually, but I have one set to go off every morning at 7:30 & it has worked perfectly everyday for a few weeks now.
~John
Curious to see what settings people are using (min/max) as well as voltage control to get best battery life. Downloaded the CPU Master Free and wanted to set it up. Thanks
sandman_nyc_316 said:
Curious to see what settings people are using (min/max) as well as voltage control to get best battery life. Downloaded the CPU Master Free and wanted to set it up. Thanks
Click to expand...
Click to collapse
My default setting is 384 - 1512. I have a charging profile that OC's slightly to 1620. I also have profiles for a hot battery (which I have never had) and power under 20% which UC to 1296 and 1060 respectively. I use sio for scheduler (although that tends not to stick). My minimum UC is 384, nothing lower (I've read of bootloop issues with lower frequencies on the Incredible).
I undervolt everything from 384 to 1404 by -50; and 1512 by 25. Everything else is default.
I have never had a crash or reboot with this kernel on stock ROM.
hgoldner said:
My default setting is 384 - 1512. I have a charging profile that OC's slightly to 1620. I also have profiles for a hot battery (which I have never had) and power under 20% which UC to 1296 and 1060 respectively. I use sio for scheduler (although that tends not to stick). My minimum UC is 384, nothing lower (I've read of bootloop issues with lower frequencies on the Incredible).
I undervolt everything from 384 to 1404 by -50; and 1512 by 25. Everything else is default.
I have never had a crash or reboot with this kernel on stock ROM.
Click to expand...
Click to collapse
Thanks! How's your battery life been with those settings?
sandman_nyc_316 said:
Thanks! How's your battery life been with those settings?
Click to expand...
Click to collapse
Decent. I can get 10 solid hours or more of moderate use when I cannot be near a charger. I can stretch it further by turning off LTE and background data. Heavy data use tends to be the biggest killer. I keep my display at 30%, too, and use smartass v.2 as default.
hgoldner said:
Decent. I can get 10 solid hours or more of moderate use when I cannot be near a charger. I can stretch it further by turning off LTE and background data. Heavy data use tends to be the biggest killer. I keep my display at 30%, too, and use smartass v.2 as default.
Click to expand...
Click to collapse
Appreciate it. Gonna see what happens. Will update with my results. Thanks again!
I wonder what is causing all these boot loops for us all. Do you guys think it's the voltage? Perhaps the software?
zetsumeikuro said:
I wonder what is causing all these boot loops for us all. Do you guys think it's the voltage? Perhaps the software?
Click to expand...
Click to collapse
Good question. I haven't had a single bootloop since flashing this kernel after coming from Ziggy's. Been running this 192min/183max and UV'd -75 across the board and running great.
Hopefully I don't jinx myself.
Guys with bootloops/lockups...are you running any profiles?
Make sure you do a dalvik cache wipe....
Ziggy's would always lock up on me (multiple times per day) so I gave up on it. The only problem I have with this on (and this was a problem with Ziggy's too) is the min jumping to max.
My frequencies bounce on this kernel. It spends about equal time between the highest setting, and lowest setting. It works great other than that. My question is this bad for my CPU? I get great battery life, and performance, just scared the bouncing could be bad for the processor. Any help would be great.....
Sent from my ADR6425LVW using Tapatalk
Disclaimer: I realize overclocking and tweaking is very much device specific and what works for one person won't necessarily work for another. That said, I've done a fair amount of reading on the subject but need some clarification on the finer points, along with some opinions on what's working for other people. Most of my questions pertain to the Devil kernel, as most of the settings aren't very well explained. I'm running AOKP M6 with Devil kernel and I've set a modest overclock with 200 minimum and 1200 max, which seems to be pretty smooth and stable. I haven't really felt the need to push it yet
1) What governor do you prefer? From what I read in this thread, SmartassV2 sounds the best and so far it seems to be working okay for me. Also, do the profiles matter (smooth, normal, powersave)?
2) Is it wise to mess with the memory settings in the Devil kernel (zRAM, etc) or should I just leave it alone? What about swap files? Worth the hassle or not?
3) What's the difference between using Live OC and the ROM settings to OC? I've left Live OC alone, and just used the AOKP overclocker to set my values.
4) I know that I've read Deep Idle doesn't work for our phones, but what's the Devil idle setting do?
5) Right now the Screen Off- Min/Max Freq setting is off, but should I set the values for that or does the SmartassV2 governor automatically handle it?
6) Any thoughts on I/O Schedulers? From what I was reading, SIO seems to be the best choice, but then again it seems to be all a matter of opinion.
Thanks for any input you might have on the subject
Alright well I think I'm getting a better handle on this since I've had a few days to mess around, and I'll post some of my thoughts in hopes it might help someone else who's trying to mess with OCing. Problem is that AOKP ICS is already so buttery smooth that overclocking really isn't that noticeable of a gain (at least for me).
As far as clock speeds I've been sticking with 200MHz min 1.2GHz max but might just drop back down to 1.0GHz to save some battery life (I don't really run cpu intense apps that often so I don't really see a huge need). I'm not really going to mess with Live OC now that I understand that it overclocks the bus too... I've screwed around enough with PC overclocking to know that it's going to seriously compromise stability which is a risk I'm not willing to take right now (not to mention it'll probably drain the battery a lot more than 'standard' OCing). I've also found that screen off 400MHz min and 800MHz max works well for me, because although 200MHz min will work too, it lags far too much coming back from standby for my liking.
2 things I still haven't messed with are the RAM settings and devil idle (which I assume doesn't work anyway). As far as the RAM I've never once ran into a low memory issue so I don't really think it's worth the trouble (due to reading this forum post I found).
I changed to SIO for the I/O scheduler but really can't notice any difference from just the default, but I'll keep it set there for good measure I guess.
Well that's it for now, if I notice anything else that might be helpful I'll post again, and if anyone wants to jump in with their experience or settings feel free.
Thanks