Related
I'm getting about 1-2 days battery life after rooting.
I've removed Phone.apk and the other one (can't remember what it's called).
I think the short battery life is because certain apps are trying to download in the background, even when WiFi is disconnected, I can't see what else it could be:
- market
- various rss readers
- widgets
- more?
I think this is happening even when these programs are not shown in a basic task manager (the task manager resulting from the n button long press rework).
I should add, how much battery life do you get after rooting?
About 1 month but I charged it only twice
I read that some had battery drain after a month I'm still waiting to figure it out :-$
NookTouch 1.0 rooted with touchnooter 1.6. 24
Sent from my GT-P1010
What do you have in Nook Color Tools > Settings > Battery use ?
thanks mdall,
it's 48% wifi (not worried about that)
43% phone idle
& 8% display, system 2%
I have 85% for Cell standby, is this normal?
why do I have something like that on a non-phone device?
MOD: I've found a thread about it: http://forum.xda-developers.com/showthread.php?t=1189047
glezmen said:
I have 85% for Cell standby, is this normal?
Click to expand...
Click to collapse
If you keep the NST on for long periods of time without reading, then the answer is yes. Otherwise, I couldn't tell you.
glezmen said:
why do I have something like that on a non-phone device?
Click to expand...
Click to collapse
Well, there might development considerations for not excluding the culprit files (mainly: Phone.apk and TelephonyProvider.apk) but, then again, after rooting they can be removed with no apparent damage to the device so...
Sebastián Armas
Avid reader, Spanish Interactive Fiction Author
Just a note, those files don't actually affect battery life, they only affect the way battery life is displayed in battery statistics.
Disabling phone apps for good: How?
GabrialDestruir said:
Just a note, those files don't actually affect battery life, they only affect the way battery life is displayed in battery statistics.
Click to expand...
Click to collapse
Sweet...
So, how we disable those apps for good, so they wont't suck the battery dry??
Awaiting your kind reply,
Sebástian,
If I understood right what Gabrial said, and it was commented before in nook str forum, those apps won't suck your battery, because there is no phone to get in touch with, and it won't add to wifi download - even though I notice that wifi traffic is heavier that from my phone, but I have much experience with android, so I can't really tell.
Disabling phone apps for good: How?
apeine said:
If I understood right what Gabrial said, and it was commented before in nook str forum, those apps won't suck your battery, because there is no phone to get in touch with
Click to expand...
Click to collapse
My point is, dear sir: if it's running, it's using CPU and/or memory... and certainly battery.
sarmasm said:
My point is, dear sir: if it's running, it's using CPU and/or memory... and certainly battery.
Click to expand...
Click to collapse
And if it isn't there, other parts of the system are wasting CPU cycles trying to find and start it. Been there before, done that, learned that removing things without having good reasons to do it can lead to wasting a lot of time.
Looking at how much the Nook stays on each cpu state, I have found some strange issues.
It seems, that without modifying anything, it stays a whole +1 minute at 800mhz after the last touch to the screen, and then comes back to 300mhz and stays there, this is not desirable at all, even for just reading.
Can someone install any program as cpuspy to check if it is a common issue?
Here is a link to the market, its free:
https://market.android.com/details?id=com.bvalosek.cpuspy&hl=es
Do something, open an app, close it, and w8 3 minutes, if the cpuspy reports +1 or more minutes of 800mhz state, then the issue is there.
If installing Setcpu, and looking into the gobernors, they are not found, all the options are -1.
When I change the max cpu state to 300mhz (so max = min) the cpu comes down to 300mhz but dosnt stay there, it jumps back to 800mhz but inmediatly comes back to 800mhz when not in use.
I need someone to check what I'm saying to look further into this issue.
Setcpu is free for xda members, http://forum.xda-developers.com/showthread.php?t=505419
Allthough if you can buy it, its a grate app, and devs need donations.
eded333 said:
If installing Setcpu, and looking into the gobernors, they are not found, all the options are -1.
When I change the max cpu state to 300mhz (so max = min) the cpu comes down to 300mhz but dosnt stay there, it jumps back to 800mhz but inmediatly comes back to 800mhz when not in use.
Click to expand...
Click to collapse
The NST has its own power management service, so tools like that would most likely not work as expected and could in fact be dangerous to your NST. (overheating)
ros87 said:
The NST has its own power management service, so tools like that would most likely not work as expected and could in fact be dangerous to your NST. (overheating)
Click to expand...
Click to collapse
That makes sense, and is what I thought about the gobernors.
The problem still resides on the time the cpu stays at max state after it has stopped being used.
I'm taking a look at sys/devices/system/cpu/cpu0/cpufreq/ at the moment, strangely under cpuidle I found a folder named conservative..... could that have been introduced by SetCpu, or am I talking bull**** ?
It seems the kernel supports the tipical gobernors: conservative, ondemand, userspace, performance, can't find any trace of the one the extra one that uses the Nook Touch, so it must be somewhere else.....
---------- Post added at 07:13 PM ---------- Previous post was at 06:44 PM ----------
ros87 could you please, if you know, show me where to look for this service, I found strange things under sys/devices/system/cpu/cpu0/ on idle, for example 8 states and a conservative folder, which totally shouldnt be there, and on frequency I found the normall gobernors.
I'd really like to know how the Nook touch administrates its power states .
eded333 said:
ros87 could you please, if you know, show me where to look for this service, I found strange things under sys/devices/system/cpu/cpu0/ on idle, for example 8 states and a conservative folder, which totally shouldnt be there, and on frequency I found the normall gobernors.
I'd really like to know how the Nook touch administrates its power states .
Click to expand...
Click to collapse
Sorry, I don't have any in-depth knowledge about this.
And maybe I misused the term "service", I wasn't really referring to a daemon.
There are some hints in init.rc
Code:
# Enabling sleep in idle path
write /sys/power/sleep_while_idle 1
# Enabling OFF mode
write /sys/power/enable_off_mode 1
# Enabling Voltage OFF in idle path
write /sys/power/voltage_off_while_idle 1
# Enablig DVFS with conservative governor
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor conservative
# Enabling SmartReflex for Zoom3 OMAP3630
write /sys/power/sr_vdd1_autocomp 0
write /sys/power/sr_vdd2_autocomp 0
I guess you have to grep your way trough the sources to find out what B&N modified for this particular platform.
Here's some platform documentation from TI (Gingerbread related, but still)
http://processors.wiki.ti.com/index...t-2.1_PortingGuides#DVFS_-_CPU_Freq_framework
Thanks ros87, I'll look into it.
Thanks - the link to the processor wiki is very helpful for a newbie like me to learn how these things work. I never understood that the userspace governor had to be set before the cpu frequency could be set.
Well, it worked with three other testers, some friends of mine that found the same problem. If you're facing this, try and feedback me. Just want to make sure that I've helped someone.
This guide is for those who have the 0% battery issue, found the fix by Bazoocaze (thanks a lot !!!) and are experiencing some quick battery drain. If you're not, then you can go read something else In two or three weeks of testing, I believe that this does not have something related to the ROM that we're using. The processes on background and the use of CPU is relative, but maybe a process is using too much energy, and if we keep the energy level on a low status, I think this process won't have so much energy to use. And maybe the kernel, or the kernel's governors are affecting something, not sure of this last one. I've also concluded that this don't have anything to do with the Wi-Fi modules, because I've already tried that fix, and it drains pretty quick anyway, some believe that there is a bug affecting the Wi-Fi, and it doesn't turn off, even if we turn it off on the menu.
First of all, if you haven't find the fix, read this: http://forum.xda-developers.com/showthread.php?t=1312398
You can also use the DooMKerneL ICS v4 that DooMLorD developed, and it already has the patch built-in (I recommend for this guide): http://forum.xda-developers.com/showthread.php?t=1520654
1 - Flash the kernel, the one of Bazoocaze or the DooM Kernel
2 - Turn on your phone, normally, make all your configs, and do a little test, BEFORE following this guide. See how many time your battery can hold on. If you feel that it's going out too fast, keep going on the guide.
3 - For this operation, I suggest you buy or download the free version of SETCPU, never forget that name. NoFrills didn't work very well to me..
4 - Overclock, if you want and if you're using DooMKerneL. Keep the MHz min on 364 (will explain later)
5 - Go to the profiles tab and press the ''plus'' button. Change the MHz max to 768 and keep the min at 364. In profile, select Screen Off, and change the governor to powersave or smartass and set priority to 100%
6 - Save it, and press Enable and Notifications on the bottom of the screen.
7 - Now test it for some time. Try not to keep your screen always on, as it ''cancel'' the effect of this guide.
Explanations:
a) The reason to keep the min MHz at 364 is that you won't face stuttering in the screen on/off, because the app will only change the max value, and not the min value, which makes the system still work fine (I believe, if some dev could correct me..). It behave better in AOSP alike roms.
b) NoFrills didn't give me the same results as SetCPU, that's why I'm recommending SetCPU. Make some effort to buy the Pro app.
c) The main trick is to reduce the power usage and capacity when the screen is off, because you don't use your phone 100% of the day, and because the process that may exist (mentioned above) would not use the whole capacity of the energy and the CPU as well. That's why it works. At least worked for me.
d) There is absolutely no hardware of software issue if you try this guide, you can uninstall the SetCPU app and use kernel other than DooM's. It's safe and quick, if it doesn't work, you can always revert everything.
Please, if you want to try this guide, give me the feedback. As I've said, I just want to confirm that theory and make sure that I've helped someone.
Thanks Bazoocaze and DooMLorD for being life savers!!!!!!!!
Bye
Thanks for your help
Sent from my LT18i using xda premium
ok guys first of all ill start by saying that none of this i mine...its all stuff that i understood from different threads.I am a complete noob so there are gonna be many things ill not be able to understand to you!
i am gonna thank these brilliant people first
-gokhanmoral
-pikachu
-droidphile
-andre
and others(who have started undervolt threads) ive missed!
ok now to the main point!
this works only on ics siyah kernels as currently GM is the only one who supports the following commands!
what you need!!
-terminal emulator
-volt tweaking app (set cpu, voltage control),i wont prefer extweak or xxtweak as you cant edit a perticular freq volt with them
-patience
ok now start by selecting the freq on which you wanna work..undervolt it to your desired volt
e.g ive undervolted my 200mhz to 925mv
now open terminal emulator
type:
su
LVL=`cat /proc/kallsyms|grep " level\."|awk '{print $3}'`;kmemhelper -n $LVL -t int 14
and press enter
ok what this command does is that it changes your touch screen freq to the number last in the command line..in this case 14 it is
you can alter these numbers as follow:
0-1600 6-1000 12-400
1-1500 7-900 13-300
2-1400 8-800 14-200
3-1300 9-700 15-100
4-1200 10-600
5-1100 11-500(stock)
so as you can see the above command line sets my touch freq to 200 mhz.
ok so as soon you press enter in the terminal emulator your touch freq is changed to the freq of your liking..(remember use the above states numbers and not the freq itself in the command line) and some how that perticular freq takes load in such a pattern which i could not recreate with any stress stability test or even mxvideo test( you can find about it in various threads) and hence if the undervolt is below the stability threshold your phone will crash,hang,reboot...but you will get to know which volt value on which freq is unstable.
After setting the touch screen freq try(you can use voltage control to confirm if your touch freq has changed or not) use your phone normally...scrolll between pages..browse..play games..and if the perticular freq volt is unstable your phone will indefinitely crash within 5-10 min..!
do this procedure for every freq and ull definitely will get yourself the most stable UV's your device can handle!
you can read much about this and other stuff in droidphiles thread
http://forum.xda-developers.com/showthread.php?t=1572937
thank me if it helped!!
Hmm... do we really need another one of these threads lol
Sent from my 80GB CyanogenMOD 9 + Siyah ICS powered beast. Booya!!
i jus tought of sharing this as it seems to me that this kinda crash which the touchscreen freq produces isnt reproduced by any stability test..hence another way for testing your stability...besides i myself was facing few crashes with my settings lately and this cured it...!
Your CAPS key is broken ...
haha not really...HERE YOU GO...i had words in caps up there aswell...dun knw what went wrong..btw...love your dp!!
Thanks for the info. I've been having a little trouble with some UV values that I believe should be stable. This might be the fix. I'll report back after I've tested it.
I didn't even know you could do that, learn something everyday.
Interesting because in Siyah I've always noticed the max frequency ALWAYS exceeds whats set in SetCPU etc.
If I set it to 500mhz, it will still jump to 800Mhz momentarily when touching the screen, loading apps, scrolling etc. I've noticed on the latest kernel it hits 1200mhz, no matter what my global max frequency is. On Abyss kernel etc, it behaves normally. Is this 'touch frequency' the reason for this?
I watch the CPU frequency using Cool Tools/CPU spy...
Tye:P said:
Thanks for the info. I've been having a little trouble with some UV values that I believe should be stable. This might be the fix. I'll report back after I've tested it.
I didn't even know you could do that, learn something everyday.
Click to expand...
Click to collapse
yeah i myself was having issues with uv's..found this way indirectly with the help of droidphile...would love to see if it helped you!
busky2k said:
Interesting because in Siyah I've always noticed the max frequency ALWAYS exceeds whats set in SetCPU etc.
If I set it to 500mhz, it will still jump to 800Mhz momentarily when touching the screen, loading apps, scrolling etc. I've noticed on the latest kernel it hits 1200mhz, no matter what my global max frequency is. On Abyss kernel etc, it behaves normally. Is this 'touch frequency' the reason for this?
I watch the CPU frequency using Cool Tools/CPU spy...
Click to expand...
Click to collapse
mate your issue can be solved simply by installing extweak and setting the smooth scaling level to your max freq..on default the level is 1200..but this issue was solved in the 3.2.7.X versions of siyah..which version are you using?
i'll try to UV with xxtweak
doesnt matter what uv tool you use...but i should be an app which uv's indivisual freq's and not all at once as then you wont be able to figure out which volt is giving error on which freq!
Hello.
Undervolting your CPU has always been a daunting task - there's so many CPU steps, if you pick say -100mV to all frequency steps and you get a reboot, how do you work out which step (or steps!) is causing the problem? If you undervolt -25mV on one frequency, then wait a couple of days to make sure it's stable, then reduce the same frequency by another 25mV.. you'll still be undervolting a year later.
This thread is my tutorial on how to do a best effort at quickly and safely undervolting your phone CPU.
First of all - is undervolting your CPU worth it?
Initially it was thought not to make much difference, but after some serious testing (thanks AndreiLux), "we" decided that it was a good idea. I also did my own basic testing, and it looks like it's worth it.
What are the advantages of undervolting?
Better battery life
Cooler phone, especially useful if you overclock your CPU
What are the disadvantages of undervolting?
That's the great thing! Really the worst that can happen is your phone freezes or reboots. The steps below should eliminate all of that. Once you have undervolted your CPU to just above its freeze/crash levels, there are no disadvantages!
Note: I have had some minor data loss (eg an app forgets a setting) after an undervolting related crash, but it was rare and I believe has to do with the Perseus kernel "Enable dynamic FSync" setting. I note below how to mitigate against this.
What do you need?
A rooted phone, and a kernel that supports undervolting. Perseus and Siyah will work, but any kernel should be fine that supports SetCPU's undervolting schema
SetCPU or you can use a combination of STweaks and Stability Test (use STweaks for setting the frequency and voltage, and use Stability Test's Classic Test for the stress test)
A paper and a pen - I used Sticky Notes as I was at a computer for most of the process
Some patience
Let’s begin.
Open SetCPU. You’ll be greeted by the Main screen which has the min/max CPU frequencies, the governor options, and the IO scheduler options. Reduce the max CPU frequency to the lowest step. On the SGS3 this will be reducing 1400MHz down to 200MHz, so you now have both the min and the max set at 200MHz. The phone will get pretty slow at this point. Ensure the Set on Boot option is unticked
Set the governor to Performance (note: you have to make sure all cores of your CPU are being used. In a complex kernel such as Perseus, you'll have to go into STweaks and set the CPU hotplug lock to 4 so all 4 cores are used. Also note there appears to be a bug in Perseus at the time of writing: you have to set the hotplug lock BEFORE you change the governor to performance)
Move to the Voltages screen
Ensure the Set on Boot option is unticked, and scroll down to the lowest setting, and change it to something low, like 700mV, and then apply it (click the third icon from the right at the top of the screen, a rectangle with a tick on it) . This first setting is always a bit of guess and check, and to be honest you’re hoping for the phone to freeze or crash on this first one. Has it frozen? If so move on to the next step. If not, reduce it by a further 25mV and apply again, repeat until your phone freezes or reboots.
So, you have undervolted too far. Reboot the phone, and perform steps 1-3 again. At step 4, use the voltage that crashed your phone +25mV (eg if it crashed at 675mV, this time set it to 700mV). Now, you have a very slow phone running a low voltage that doesn’t immediately crash it. Move on to the next step
An easy crash test I found was simply allowing the phone to go into deep sleep, and waking it up again. To do this, unplug your phone if it’s charging, and turn the screen off. At this point I usually wrote the time down on my piece of paper, as well as what frequency and voltage I was testing as I’m prone to forget these things. Wait 5 minutes with the screen off (and make sure no notifications have come in while the screen is off – this wakes the phone up and you’ll have to wait another 5 mins), then turn the phone on. You’ll know it’s gone into deep sleep as there’ll be a slight delay before the screen turns on as compared to no delay when turning it off and immediately back on again. If the phone doesn’t turn on, go to step 5. If your phone comes out of deep sleep OK, move on to the next step.
Now, we stress test. In SetCPU scroll over to the Info screen, and scroll down to the Stress Test option. Start it, and note down the time on your paper/Sticky Notes. Your CPU will now run as hard as it can at the current frequency. Let it run for 15-20 minutes. At the lowest frequency it will be pretty laggy and slow, if you think it has frozen always give it 30 seconds to see if it picks up again. If it gets stuck for over a minute, you probably have a crash. Go to step 5. If after 15-20 minutes it’s still running, you have found your first stable(ish) voltage for that frequency! At this point I saved the voltages in SetCPU by pressing the diskette icon. To ensure the changes are written to disk turn the phone screen off for 5 seconds then turn it back on again.
We are now ready for the next frequency. There’s pretty much no way a frequency will run stably on a lower voltage than a frequency below it, so our first voltage for the next frequency up should be the same stable voltage we found for the previous frequency. For example if we found a stable voltage of 725mV on the 200MHz frequency, our first test voltage for 300MHz should be 725mV. Write this down with the frequency on your paper. In the Main screen of SetCPU, change the max frequency to the next step up. Then, in the Voltages screen, adjust the voltage to be the same as the lower frequency, as discussed above. If your phone immediately freezes or reboots, move to the next step. If not, go to step 10.
So, you have undervolted too far, again! Reboot your phone, open up SetCPU, and in the main screen ensure the max frequency is set to the frequency we’re testing. Give the sliding bar things a jiggle to apply it. Ensure the governor is set to Performance by pressing it on the lower left part of the screen. Move to the Voltages screen, and you’ll either see your previous “saved” voltage values ready to be applied in dark grey under the “current” voltage settings, or you’ll have lost your “saved” voltage settings. If you have lost them, never fear; just restore the latest settings by clicking the first from the right icon at the top (a square with an arrow pointing outwards). Adjust the frequency we’re testing’s value to 25mV more than the value you last used when it crashed, and apply it. If it crashes immediately, repeat this step. If not, move on
We now start the two tests in steps 6 and 7 again, but this time if your phone crashes or freezes, go to step 9. If it completes the deep sleep and stress test tests, go to step 8 for the next frequency test.
Sorry for the complexity here, but it was the easiest way I could write it without repeating myself too much. The TL;DR version goes like this:
Pick the lowest untested frequency, set the max frequency to this and the governor to Performance, and find the lowest voltage that doesn’t immediately crash the phone
Put the phone into deep sleep, and see if it crashes. If it does, increase the voltage for the current frequency we’re testing by 25mV and test again. If not, move on
Run a stress test on the phone for 15-20 minutes. If it crashes, raise the voltage by 25mV and go to step B. If it doesn’t crash the current frequency is now tested. Go to step A
You now have a set of frequencies that shouldn’t immediately crash the phone. Set the min and the max frequencies back to normal, and set the governor back to your usual governor. At this point for me I was able to use the phone for about 2 hours before I had my first crash. How running a stress test on each frequency for 20 minutes didn’t pick up this crash situation I’m not sure, but it didn't.
After screwing around for a while I found the easiest solution was to just raise each frequency step by 25mV and then continue every day usage. That was enough to stabilise my phone. If it still crashes for you, keep raising all the values by 25mV until it settles down. After a day or two of no crashes you can start slowly one by one reducing each step by 25mV again to find out which step caused the crash.
After that, you should be done!
Ps I know there is another thread around here discussing undervolting, but I found it too vague on the details and sometimes wrong, so I thought I’d share my experiences in the hope it might help.
Good work!
Would you pls post your testing results for our reference?
Thanks.
Mod edit: please do not quote the OP.
A table with the running undervolting settings would be a great orientation help. Given that, people don't need to trail and error from scratch.
Sent from my Nexus 4 using xda app-developers app
me_max said:
A table with the running undervolting settings would be a great orientation help. Given that, people don't need to trail and error from scratch.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Under/over volting doesn't work that way. Each chip is unique, and chips are tested only on default voltage and frequencies, so each one's behavior on non-default settings is unpredictable. Some are able to work on 100 mV lower voltage, some can't handle even -25mV... Trial and error is the core of overclocking.
yep, that's one of the reasons i disagreed with the other UV thread - they list absolute voltage levels which are only applicable to the specific grade of chip in their phone (and yes, I posted some corrections in the other thread but they were ignored).
Have a look HERE if you'de like to see all the different possible default voltage settings for the i9300/i9305.
As a rough rough guide of a voltage level for the 200MHz step that will (hopefully) crash your phone, I'd start at 650mV.
i have tested my cpu
for stable values and i finished with these settings:
200Mhz - 0.775V
300Mhz - 0.800V
400Mhz - 0.825V
500Mhz - 0.850V
600Mhz - 0.875V
700Mhz - 0.900V
800Mhz - 0.925V
900Mhz - 0.950V
1000Mhz - 0.975V
1100Mhz - 1.000V
1200Mhz - 1.050V
1300Mhz - 1.100V
1400Mhz - 1.150V
1500Mhz - 1.200V
My exynos is stable for 2 months now, i play a lot of new games like most wanted etc.
In UV more important is leaving phone in idle, deep sleep on and off, or non demanding tasks, if i UV too much games were stable but i had random restarts when phone was in the pocket sleeping. But, as You mentioned, every cpu is different so everyone has to test it...
Thank you OP for this very, very useful guide. I am new to undervolting and even though I have a T999V north-american model with the Qualcomm SoC, this will prove very useful in my experimentation.
Only difference with the Qualcomm is that clock speed can go as low as 96Mhz, but you can't undervolt under 700mV - SetCPU just refuses to apply anything under that.
No probs
That's a kernel limitation, not SetCPU. Check with your kernel dev to see if they can allow further undervolting.
I tried to make the instructions as generic as possible so any stepping config could use them. good luck!
I'm doing my 96Mhz test and running a stress test.
The loading circle is still moving just fine (although a bit sluggishly) but none of my buttons are responding at all so I cant leave the test until I pull the battery. Would this count as a freeze/crash, or do you think this voltage is okay to stick at (or even go lower?!)
That's just the CPU bogging down, it's not a voltage issue.
hi guys. this might sound like a dumb question but i honestly looked everywhere but i cant seem to find the UV in setcpu. i'm i missing something?
Probably the kernel you're using doesn't support UV.
Hey
I find that 200 is stable on 687500
And then when I move to edit 300 it reboots
Then increased the number on both and still reboot.
I don't restart in between. Any idea??????
Sent from my GT-I9300 using xda app-developers app
tony1234567890tony said:
Hey
I find that 200 is stable on 687500
And then when I move to edit 300 it reboots
Then increased the number on both and still reboot.
I don't restart in between. Any idea??????
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
That means that 200 is NOT stable. Try using a higher voltage. 0.6875v is ridiculously low
TP.
What do you mean low he says in the op to reduse to 700
THC for fast answear
Sent from my GT-I9300 using xda app-developers app
tony1234567890tony said:
What do you mean low he says in the op to reduse to 700
THC for fast answear
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Default voltage for 200mhz step is 0.9v (for me on asv2). So 0.7v (which is still higher than what you have set) it a whopping 200mv less than stock which is like I said before, ridiculously low. It may run at this voltage for you for now(depending on your as level), but I can pretty much guarantee you that it will never be 100% stable
I'll take your THC ; ) lol
TP.
Thanks I'll give you feed back
Sent from my GT-I9300 using xda app-developers app
omniwolf said:
Probably the kernel you're using doesn't support UV.
Click to expand...
Click to collapse
i thought the matr1x kernel supports it. UV works fine in trickster mod. i don't even have a heading for 'voltages' in the the app like it's shown in the play store.
tony1234567890tony said:
What do you mean low he says in the op to reduse to 700
THC for fast answear
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
yep, as STAticKY says, if you get a reboot on a step, then it's not stable. raise the voltage on that step and try again.
STAticKY said:
Default voltage for 200mhz step is 0.9v. So 0.7v (which is still higher than what you have set) it a whopping 200mv less than stock which is like I said before, ridiculously low. It may run at this voltage for you for now, but I can pretty much guarantee you that it will never be 100% stable
I'll take your THC ; ) lol
TP.
Click to expand...
Click to collapse
This is only correct for your ASV value. Please edit this post, it contains incorrect information. Your default voltage for 200MHz might be 0.9v, but for other people it's likely different, as they have different quality chips. Read post 3, 4, and 5 in this thread for more info.
genericuser2013 said:
i thought the matr1x kernel supports it. UV works fine in trickster mod. i don't even have a heading for 'voltages' in the the app like it's shown in the play store.
Click to expand...
Click to collapse
possibly the matirx kernel does support UV, but it might not be exposed in the way that SetCPU is expecting. Does the Matrix kernel developer recommend a specific app to adjust the voltages? If so use that, you can still follow my guide.
Can anybody tell me how to determine ASV-level of my chip?
I have a HD2 with an older version of android cooked on. Android version 2.3.7 Kernel version 2.6.32.15_tytung_r12.4-heebf2c Mod version is CyanogenMod-7.1.0 Desire (Typhoon_v3.7.0 Magldr) I think my radio is 2.15.50.14
I really need the wifi calling feature on my phone to work. Do all the roms have this problem on our phones? Would it be easier for me to just install a new rom? Every time I turn on wifi, the phone freezes completely. I read through the post regarding this issue, but there was no specific information given about how to overclock the phone. I downloaded nofrills cpu control and have tried random combinations, but was wondering the ideal oc speed?
resevil83 said:
I have a HD2 with an older version of android cooked on. Android version 2.3.7 Kernel version 2.6.32.15_tytung_r12.4-heebf2c Mod version is CyanogenMod-7.1.0 Desire (Typhoon_v3.7.0 Magldr) I think my radio is 2.15.50.14
I really need the wifi calling feature on my phone to work. Do all the roms have this problem on our phones? Would it be easier for me to just install a new rom? Every time I turn on wifi, the phone freezes completely. I read through the post regarding this issue, but there was no specific information given about how to overclock the phone. I downloaded nofrills cpu control and have tried random combinations, but was wondering the ideal oc speed?
Click to expand...
Click to collapse
I never used Tytung's GB rom but wifi generally works very well. I used it all the time with Typhoon GB, Tytung's ICS and JB.
For overclocking Install Setcpu from the Play Store.
---
With proper diet, rest, and exercise a healthy body will last you a lifetime... (via Tapatalk)
Can you give me an estimated range I should set my cpu to? I can't find the thread, but somewhere along the line I read something about how you should over clock your processor in multiples of something. I'm not describing it well, but maybe it had something to do with a mhz speed and then a frequency or another unit of measurement for power. Like volts. I have no idea, what I'm trying to say is that I read there is some sort of calculation you need to figure out in order to properly adjust your cpu settings.
ny_limited said:
I never used Tytung's GB rom but wifi generally works very well. I used it all the time with Typhoon GB, Tytung's ICS and JB.
For overclocking Install Setcpu from the Play Store.
---
With proper diet, rest, and exercise a healthy body will last you a lifetime... (via Tapatalk)
Click to expand...
Click to collapse
resevil83 said:
Can you give me an estimated range I should set my cpu to? I can't find the thread, but somewhere along the line I read something about how you should over clock your processor in multiples of something. I'm not describing it well, but maybe it had something to do with a mhz speed and then a frequency or another unit of measurement for power. Like volts. I have no idea, what I'm trying to say is that I read there is some sort of calculation you need to figure out in order to properly adjust your cpu settings.
Click to expand...
Click to collapse
I think that all better apps for this already take care of much of what you are looking for. I know SetCPU does - in fact it has profiles for numerous phones, including the HD2. The one disadvantage that I tend to forget is that it isn't free. If you look at the app's description on Google Play you will get a lot of ideas. Likewise, the developer's web site also has some good info.
Briefly, I do not set any profile's low frequency below 245 MHz (potential SODs). The high-end you can experiment - if the HD2 locks up reboot and set it lower.
I have a default profile and change it to faster MHz if plugged in (I don't care about using more power when plugged in) or lower frequencies for sleep or overheating and such. If you do get SetCPU you can plug in the attached profiles (don't forget to unzip it first!) and see if you like any of them. They can all be changed or deleted, of course.