yashsingh1/xdaforums huggingface dataset:
[XPERIA X10 Android Development] TheRuan:
[how to test uv freq by freq]

Well the need for testing freq by freq is that you have to make sure that the freq. you are undervolting is perfectly working and that if you get any WLOD or FCs(i just got one FCs during the testing any error ended on WLOD) the error is on the freq. you are testing and none of the freq. higher or lower is affecting it.

Governor:

POINT: The only governor should be used in the initial testing procedure is the performance governor.

REASON: Because it will only use the freq. you testing, nothing lower and nothing higher.

PS: You have to always set the max freq. to the one you are testing.

1) Find the freq. you want to test(Let's say 128MHz)

2) Go to setcpu or CPU Master and set min AND MAX to 128MHz (i know the rom will be very slow on this point, don't complain about it) and set governor to performance mode(it won't make a difference, but just you get used to it).

3)Go to IncrediControl and set 128MHz voltage to 1000mV if it is already working lower it to 950mV it should work( DO NOT CHECK "SET ON BOOT" )

4)Go to Linpack and keep running test, at least 5 times, if you get wlod make the voltage higher and repeat this step, else go to next step.

5) Go to Quadrant and do at least to runs, if you get a wlod it will be most likely right on the start of 2D scenes, if you get wlod raise the voltage and repeat this step, else go next.

6) If you didn't get any WLODs during these tests, lower the voltage.

7) you can do this from the first to the last voltage, all freq should work from 128MHz to 1228MHz.

PS: Setting the screen to always ON may be needed as some rooms will change you governor to interactive if the screen goes OFF.

PS2: testing above 998MHz should not be done for more than 30min for security(not breaking the phone) reasons.

Advises:

Always take a note in a table of everything that happened, wlods, FCs, noting the freq, it happen and how much battery you had when that happened.

Run this tests with the battery lower than 50% with everything ON(bluetooth, wifi, data(will not be used if wifi is on), gps,... everything you can think of, is better, because it will reduce variation due to higher or lower battery % or battery consumption that could affect the tests.

Applications used in the tests:

IncrediControl

AND

Linpack

AND

Quadrant

AND

CPU Master (Free)

OR

CPU Master for Root Users

OR

SetCPU for Root Users
[XPERIA X10 Android Development] TheRuan:
FAQ

Q? :Should these voltages work on any x10 phone?

A! :NO, every phone is nearly the same but always different, everything is always different.

Q? : Why did you post if this shouldn't work in the same way for others?

A! : Because the voltages may work or not, but the test procedure for sure will work, and also this voltages can be used as the base for testers given the start point.

Q? : Will this work on any Kernel?

A!: This should work on any kernel/rom that can support UV.

Q? : I got stuck on loading the OS, right after the OS starts, it locks giving wlod or rebooting right away, what did I do wrong or what should I do now?

A! : I told you not to set in on boot before really testing the voltages, i will try to get a way to prep a guide in case this happen, but normally incredicontrol will recognize the wlod and set the voltages to default.

Q? : Do you have any? Let me know.

A? : I will give any answers as soon as possible.
[XPERIA X10 Android Development] TheRuan:
This last one should be enough.
[XPERIA X10 Android Development] n4naveen:
undervolting gives me worse results , device heats up more quickly than stock voltages and Stock voltages gives me better battery life than undervolted voltages , there's something wrong in this concept , esp for our X10 . I tested them.
[XPERIA X10 Android Development] TheRuan:
Are you using an addon module for WB rom? or something like that? or a custom kernel?

I had a similar issue using the addon modules before the kernels were released, nothing similar to it anymore.

For me the only times that i get battery draining is if for some reason i get wlod, than it will drain like 1% of the battery.

Getting less battery on UV is actually impossible, it only means that your UV or the rom you are using is having some sort of errors.
[XPERIA X10 Android Development] indhimaga:
so many developers popping up, I hope to be able to feel the best results that they have created, and I pray you will be a developer with great skills, keep up the good work... because people like you who make our novices into smart :D sorry for bad language...!!!
[XPERIA X10 Android Development] 10assaye:
A very good guide...This is exactly what I do but I never thought to write it down...just thought all testers knew what they were doing, but now I read your post I realise that some "testers" just download, flash and complain within the space of 10 mins and dont really do the testing....

:) Well done...
[XPERIA X10 Android Development] DooMLoRD:
once u have arrived on stable voltages, min/max CPU freq, governor, i/o scheduler combo (phew thats a lot of tweaking ;)) for ur device u can simply use init.d startup scripts to set those values... no need to use multiple apps :D

here is something that should be helpful:

http://xdaforums.com/showthread.php?t=1236446
[XPERIA X10 Android Development] TheRuan:
Next month i will start learning Java Introduction classes and then right next I will be going to an Android development class, so be prepared, because for now I'm just a novice, but some day i'm going to join the great guys here. :D:D

Yeah most people download everything from the post, not read anything in the FAQ and neither on the how to, and start commenting errors that sometimes even exist before using what they downloaded.

This only causes confusion for Devs delaying even more the good stuff.
[XPERIA X10 Android Development] TheRuan:
Don't know yet how to set that on the init.d dir, though it should be very simple, will try to search for this tonight.

Good addiction to this guide.

Thanks!
[XPERIA X10 Android Development] indhimaga:
yeah looks like a hardwork... BTW the tutorial like Overclock in my AMD Phenom, but different methode... :D Reserved...!!!
[XPERIA X10 Android Development] iridaki:
Here is a startup script for init.d, which sets the VDD levels at boot.

It's the one I use but you can edit/add/remove any values you want.

Get it from [. . .]!

You're welcome! :)
[XPERIA X10 Android Development] robertberma:
Very nice but a waste of time to show this because every phone handles different settings differently. If these settings works for you it do not mean it works for someone else.
[XPERIA X10 Android Development] robertberma:
the way u test is a good way but the voltage do not work for everone.
[XPERIA X10 Android Development] TheRuan:
I never meant to tell that this will work for everyone, though i believe that a very similar configuration will work for mostly everyone.

The intention on this is to show how you can get the basis for a test.

Because, just because you could set a voltage without getting the phone WLODing for you right after that will not mean that the voltage you set really will work, it only means that you have still to stress it to test.

By the way, this configuration will work for most people, most people can use the 128MHz but just doesn't know the correct voltage for that.

The thing is, if you can set the voltage for 128MHz at 800 without it rebooting right after that, stress a bit the processor, if it doesn't reboot try for some time, using on demand mode, so you will get it jumping a lot of times between lower freq. and higher freq.

Most people do the following:

Set 128MHz for (let say 900mV), 900mV and leave the next freq at 1000mV or more, this will cause problems and most likely WLOD, I have tested this and almost always a big variation generates WLOD, so it must be gradual or won't work, for this reason i created this so everyone can calculate the best basis for their phones based on their freq, not in mine.

The only thing I really believe will work for everyone is the math, rate 0,58 per 1MHz, this have worked, as far as i can see.
[XPERIA X10 Android Development] Mayazcherquoi:
That's merely app development.
[XPERIA X10 Android Development] Skumtomten:
which can be used for developing apps for tweaking the x10's voltage ;)
[XPERIA X10 Android Development] Haldi4803:
Had a lot of time yesterday. So here are my Voltages (no overclock though)

128Mhz | 825mV

192Mhz | 825mV

245Mhz | 850mV

384Mhz | 850mV

460Mhz | 925mV

576Mhz | 950mV

614Mhz | 975mV

652Mhz | 1000mV

691Mhz | 1025mV

729Mhz | 1075mV

768Mhz | 1075mV

806Mhz | 1125mV

844Mhz | 1150mV

921Mhz | 1200mV

998Mhz | 1250mV

Currently capped at 768mhz to try out battery life ;)

Haven't found any negative points till now.
[XPERIA X10 Android Development] dragoxt:
Insanity uv

So i been trying to under-volt mi phone, i have stumbled upon something really weird:

so i have been making test and lowering mi v on each frequency this is what i got so far 2+ hours tested no wlod or crash only up to 768 (cap) interactive.

5 runs on each frequency on linpack and 2-3 on quadrant.

first tested on IncrediControl then patch-it with my uv modified script, to make sure it was getting set to 750.

'128000 750'

'192000 750'

'245760 750'

'384000 750'

'460800 750'

'576000 750'

'614400 750'

'652800 750'

'691200 750'

'729600 750'

'768000 750'

IncrediControl reports 750 on all those freq.

reinstall this script init.d-autorunner-v01.zip

everything is still working correctly .... so ... anyway to test this is real and not just mi imagination ?. because i don't believe this myself...

Phone x10a

Firmware wolfbreak 4.0.4c

Kernel Doomkernel v04x

patch with vdd-doomkernel-v04-init.d-script-X-v02

then further modified using "TheRuan" guide "thanks by the way"

Also check on data\local\tmp\ and i get confirmation init.d is working.
[XPERIA X10 Android Development] DooMLoRD:
check the output of the following command:

cat /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels

also do this: (in SetCPU)

set governor to performance

then move min frequency slider to extreme left (LOW freq) then move max freq slider to extreme left, then keep moving the slider one notch at a time towards right (HIGH freq)...

if ur device doesnt freeze/crash then those voltages are indeed working...
[XPERIA X10 Android Development] dragoxt:
OK verified output using free terminal emulator:

from 128000: 750

to 768000: 750

All the other freq untouch.

and SetCpu went as you explained one by one even went ahead and did a CPU bench test short and long bench on each freq.

So confirm it is working at 750.. i haven't touch the the other freq cause i felt i was doing it wrong,, ill see how far i can go with the other and get back to ya...

is this a good thing ?, I kinda feel proud of mi x10 right now
[XPERIA X10 Android Development] xachiel:
nice its working!

my uv table is this

128Mhz | 750mV

192Mhz | 750mV

245Mhz | 750mV

384Mhz | 750mV

460Mhz | 750mV

576Mhz | 750mV

614Mhz | 750mV

652Mhz | 750mV

691Mhz | 750mV

729Mhz | 750mV

768Mhz | 750mV

806Mhz | 1100mV

844Mhz | 1125mV

921Mhz | 1175mV

998Mhz | 1225mV

1036Mhz | 1250m

1075Mhz | 1300mV

1113Mhz | 1325mV

1152Mhz | 1325mV

1190Mhz | 1350mV

1228Mhz | 1375mV

no WLOD.
[XPERIA X10 Android Development] DooMLoRD:
did u try 750mV for >800Mhz? i want to know if the device freezes at such low voltages for high freq...
[XPERIA X10 Android Development] xachiel:
yes but only in 1050 and it freezes
[XPERIA X10 Android Development] DooMLoRD:
so basically very low voltages dont work for those frequencies right?
[XPERIA X10 Android Development] xachiel:
right! even minus 25mv from 806mhz to 844mhz will give wlod on linpack.
[XPERIA X10 Android Development] dragoxt:
So i might have made a discovery or at least found something up, when testing don't go far from the mv between freq.

Example if i have 729000@750mv the next frequency should work close enough to its mv ex.768000@800 mainly be more or less then > 100 mv so it doesn't jump on the voltage.

Also i did get some wlod first time i tried changing the mv on most of the upper frequency only once when i went from high mv ex.1050 to very low mv 900-800mv but when i do it from a 50 to 50 ex.1050-1000-950 without testing until i go to a very low ex.800 it works very well.

i successfully went ahead and got this working without wlods :

new*

806400@750

844800@750

921600@750

998000@750

ill try playing some games and see if i get a error or a wlod.

so word of advice test the next freq at the last mv you used, if you get a wlod restart and add +25mv

im starting to believe going below 850mv is not being correctly added to the cpu. you know the 2 good to be truth situation.
[XPERIA X10 Android Development] DooMLoRD:
hi can u do some checks like the ones outlined below:
[XPERIA X10 Android Development] xachiel:
thats impossible i manage to set 806mhz to 844mhz 1050mv only and gets wlod. hmm. maybe its not compatible for my x10.

see
[XPERIA X10 Android Development] dragoxt:
well i did plenty of times linpack, quadrantand also i get the same result on the cat inside Terminal Emulator even played dead space for some minutes.

128000@750 all the way to 998400@750 no wlod everything higher normal mv.

note: i did get some wlods trying to get to the lowest mv. but after that nothing is as stable as normal.

if i get to the overclock freq and managed to down them this much ... ill cal this BS and something will be wrong for the applied voltage.
[XPERIA X10 Android Development] xachiel:
did you try this doom? ive tried that 2 times set in 750 all the way too 998mhz.

still wlod.

EDIT: at 1000mv still WLOD 806-998mhz
[XPERIA X10 Android Development] DooMLoRD:
my x10 crashed when i tried to put all voltages (128mhz to 998mhz) to 850 ;)

doing testing using latest Linpack

i used interactive governor... just set the voltages (via shell script) and device froze :D
[XPERIA X10 Android Development] xachiel:
yeah me too i set only to 1000mv and WLOD
[XPERIA X10 Android Development] DooMLoRD:
same here

i did this test...

using setcpu adjust min/max freq to 768/998

then select governor to interactive

set voltages of those frequencies to 1000mV

the device responds for few seconds when i try to run linpack but the device freezes

used the following code:

#!/system/bin/sh
#
# setting test VDD values
# for X10 (DooMKernel)
#
echo 'setting voltages to: 1000'
echo '768000 1000' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '806400 1000' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '844800 1000' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '921600 1000' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '998400 1000' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo 'DONE! CPU voltages set'

save the above code as a simple file and change permissions to 777 and execute it to change voltages...
[XPERIA X10 Android Development] xachiel:
yeah! like i said its impossible to set 998 to 750mv. only a magician can do that :)
[XPERIA X10 Android Development] dragoxt:
That is why i am saying there must be something wrong i have verified every-way i can if the mv are applying correctly but cant find anything wrong and all points to working correctly.

any test i could do to verify mi settings @DooMLoRd? or @xachiel. :confused:

apart from the already done before.

maybe ill make a video XD on youtube later on. ill need another cam.
[XPERIA X10 Android Development] TheRuan:
My dad is Noel!

Last attempts the best i could get further was 825@128 and @192 but as it was a bit unstable I'm trying to firegure out which is the freq that is not working as the wlod are extremely ramdom, like once a day, sometimes with screen on and sometimes not and also one wlod.

Lower than 800@128 causes many random reboots no worth the tries even.

Well, not sure, i think not even a magician could, it goes against the math i did for the head start, at 998 the minium that maybe and only maybe could work in my opinion is near 1100 to 1150, anything below 1100 would be impossible, because if this worked you would end up using 900 or - @652.

First time I read, i thought it was a joke @dragoxt , but if you are talking serious, don't waste your time 1000mV won't work.
[XPERIA X10 Android Development] dragoxt:
Your exactly right TheRuan that's why i said there was something very weird about getting 750 on almost all the freq, just re-flashed newer version of doomlord kernel, and reset the mV to default, started up again and old mi old values did not work, i am guessing there was just something wrong with mi kernel/installation or init.

maybe there something wrong when going from 750 to 825 on kernel (new settings on DooMKerneL as of V04 ).

ill try going as low as i can one more time and see what i get.
[XPERIA X10 Android Development] Zocker Tko:
hi all, you see my rom and current kernel in my sig

since yesterday i had time and played a little bit with the values

1)128mhz-768mhz@750mv is stable for me using since hours, settings 192min and 768max, interactive with "no frills cpu control"

2)when i change the the other mv values (-25/-50mv) for the other frequences the phone get unstable/wlods or wont boot up

1)+2) mv setting via script (90-vdd_levels)

3) without script and changing the mv values with "incredicontrol" my phone was able to run 998mhz@950/1050mv, but here again not stable

so for me its stable 128mhz-768mhz@750mv and the other values i let untouched in the "90-vdd_levels" script
[XPERIA X10 Android Development] TheRuan:
You can't use too low mV on freq above 500MHz it won't work because everytime the phone changes the freq from one to another it will change the voltage, if the voltage variation is too high it will cause wlod.

To verify this i did test freq by freq, and i got it to go even lower than the ones i posted one first page, but the problem is the individually they will work, but when jumping from the lower freq to higher one like from 128 to 750+ it will wlod because the variation is huge, for me at least the maximun jumps with no big deal was about a max jump of 150mV +/-.
[XPERIA X10 Android Development] Haldi4803:
mhmm, my phone won't go lover than 850mv with 128mhz! But there are some who handle 750mV without any problem.

What do you think? Might there be a chance that the Sony Ericsson Xperia X10i HD not only got another Display but also a newer SoC's from another production series ? Better production process would mean needs less Voltage and might be able to clock higher.

Is there any way to find out Production Date of the Smartphone ?
[General Questions and Answers] Georgi Damceski:
I got my new HTC Desire S before 2 mounts. I`v installed some stupid app and all software crash.... When i start my phone he stuck on Green Logo at start up. What should i do? I tried with vol down + power button and again stuck on any functions.

Pls give some instructions to fix this stupid phone. :(
[General Questions and Answers] congchuaxuchauphi:
i am having a problem which is same to you! have you dealt with it yet?! give me some suggestion... :(
[General Questions and Answers] DroidFreek:
New so call for replacement this can be a hardware issue.
[Atrix 4G General] Gaúcho comedor:
I've been researching extensively how to improve my battery life on my Android phones and I believe I've found an amazing setup for the Atrix. My phone has been disconnected for 3:15 and I'm at 91% right now with moderate use. It used to burn about 5% an hour before with NO use. Yesterday, it lasted 14 hours and I still had 20% left when I went to bed.

Aura 1.1.3 Debloat #7 ROM

This ROM seems to be the lightest one I've tested. It's only 150 MB and very fast.

SetCPU

I set up a profile to underclock the processor all the way to 216 MHz when the screen is off. The processor is running at 1.1 GHz max. I haven't tested underclocking it to 1 GHz or 900 MHz. I'm sure that would improve the battery life even further and not have a huge impact on performance.

Battery mode (Android settings)

Obviously, it's on maximum battery saver.

General settings

I set the screen timeout to 30 seconds. Maybe 15 seconds is too short for you as it is for me, but that would save some more juice.

Every other battery-killing feature is on, like wifi, GPS and sync. I don't use task killers anymore and found out that my battery life actually improved a lot after I ditched Advanced Task Killer.

I just wanted to share this with the community. I hope it helps you. Any suggestions to improve it even further are very welcome. :)
[Atrix 4G General] JaronBang:
Yeah task killers are pretty much useless, watchdog is a wonderful alternative.
[Atrix 4G General] Rayan:
Interesting and thanks for sharing, but...

I can get almost the same results by using any other ROM without SetCPU and just using Max Battery Savings but I'm not interested on that setup because I need to have PUSH email all day.

Maximum Battery Savings makes push emails useless, and for a device that's supposed to be "connected" push mail is a must (at least for me).

Unfortunately, push mail is what kills batteries, specially on 3G/4G.

Cheers!

Rayan
[Atrix 4G General] pukemon:
My phone was maximum battery savings one time for some reason. I didn't do it. But for some reason, it was seriously draininng my battery bad. I think i was on 2.2/froyo before i unlocked so i don't know if that had anything to do with it. I do know, i haven't had reason to try it intentionally since my battery is great overall. It does help since atnt turned up the juice on the 3g and called it 4g reception has been very satisfactory lately helping power consumption by not having to look for a signal as often.

I voided my warranty.
[Atrix 4G General] Rayan:
Exactly! When the phone switches back and forth 2G and 3G/4G it drains a lot of power. So it too depends on the zone we are in at the moment and that's one of the reason we see a lot of different results among users. Of course, phone and app/game/internet usage style also counts.

Cheers!
[Atrix 4G General] pukemon:
I think a lot of people don't realize that terrible reception can account for terrible battery. Often we don't get that feedback when people are whining about battery. Also, lots of the people whining about battery play lots of games, and some of those games that put the gpu through it paces suck up juice faster, but the user is not realistic about that either and expects battery life of a phone that is used lightly.

I voided my warranty.
[Atrix 4G General] iRobby:
Yay for undervolting
[Atrix 4G General] aaron.a:
not "killing" aka "ending" or possibly more familiar "closing" your running apps.. that's like, like if you log into your windows box and you don't have the "X" buttons on the window caption bar.. you just leave everything that you run running until you shutdown..

before you even try to retort, obviously there are exceptions. in windows explorer.exe runs endlessly until you shutdown. on your android device that's the equivalent of your preferred launcher.

what else.. msn? the equivalent of your favorite sms app. facebook and notifications? similar to that browser you keep open with 5 or 6 tabs swiftly consuming your precious processor.

i'm not sure an argument even exists. "task killers" has "killers" in the name which naturally has negative connotations. call it a task manager. windows has a task manager.

other than that nice tips ;)
[Atrix 4G General] andrewxu:
I am stock everything.. even launcher

3hrs 14min screen on time

~12ish hours off the charger

still says 50% battery. which means 50%-59% on motoblur

pretty darn good eh?