yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] ashwinds:
The script runs if i manually execute it. Just doesn't launch on boot. All I have is this:

#!/system/bin/sh

echo "25 50 50 50 50 50" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
[Galaxy S I9000 Android Development] raspdeep:
can u do a ls -l /etc/init.d?

anyway, attached a working one so push to /etc/init.d and chmod 755 after pushing
[Galaxy S I9000 Android Development] ashwinds:
That does not work either raspdeep - thanks. The permissions are good - I did a chmod and chown root.root.

Dont bother if init support is working, I must have broken something else - I will look into it later tonight.
[Galaxy S I9000 Android Development] raspdeep:
here is the code in sztupy's post-init.sh

# init.d support
cd /sbin/init.d
echo $(date) USER EARLY INIT START
if cd /system/etc/init.d >/dev/null 2>&1 ; then
for file in E* ; do
if ! cat "$file" >/dev/null 2>&1 ; then continue ; fi
echo "START '$file'"
/system/bin/sh "$file"
echo "EXIT '$file' ($?)"
done
fi
echo $(date) USER EARLY INIT DONE
echo $(date) USER INIT START
if cd /system/etc/init.d >/dev/null 2>&1 ; then
for file in S* ; do
if ! ls "$file" >/dev/null 2>&1 ; then continue ; fi
echo "START '$file'"
/system/bin/sh "$file"
echo "EXIT '$file' ($?)"
done
fi
echo $(date) USER INIT DONE

filenames should start with E or S (E files will start earlier than the S files)
[Galaxy S I9000 Android Development] loco-:
Hey rasp, im just wondering if it'd be better to use a JPO kernel for JPO Firmware, rather than your (or any) JPM/JP6 kernel.
[Galaxy S I9000 Android Development] android53:
There is no source released
[Galaxy S I9000 Android Development] loco-:
I know, but i mean for example z4patched JPO kernel or is it impossible to patch?

EDIT: btw, i don't use this kernel because of oc but uv, built in cwm, more ram, etc.

what are the disadvantages compared to jpo kernel?
[Galaxy S I9000 Android Development] ashwinds:
Yes! it was indeed filename - I had gone with 30S*..... now it works. around 1% per hour idle battery drain overnight over 8 hours (with OC limited to 1.1 Ghz). Everything stable as of now!

Update: apparently it was NOT on 1.1 Ghz... system froze just now. Will 1.1 value work for OC? Anyway - retrying...
[Galaxy S I9000 Android Development] xan:
No such performance level. Its either 100, 200, 400, 800, 1000 or 1200 mhz...
[Galaxy S I9000 Android Development] raspdeep:
you should be able to use it for jpo, the kernel source is definitely 2.6.32 but they may or may not update source code and the initramfs may have subtle differences.
[Galaxy S I9000 Android Development] raspdeep:
i thought your 1.1ghz was a typo.. look at the first post, it states the frequencies supported. you cannot just plug in a number and expect it to work. the script that i posted on previous page limits max scaling to 1ghz if you do not want OC
[Galaxy S I9000 Android Development] ashwinds:
Yeah well... guilty as charged :D

Anyway - it all works now... still not much joy with OC @ 1.2 - maybe i need to tone down the UV to all 25 to keep it stable... will try.
[Galaxy S I9000 Android Development] raspdeep:
if 1.2ghz is not stable when UV, just leave that at zero and UV the rest.. 0 25 50 50 100 100
[Galaxy S I9000 Android Development] ashwinds:
Thats what i have right now (except it was 50 50 all the way...) - will try it for a few hours and let you know how it works.
[Galaxy S I9000 Android Development] xan:
New version of Voltage Control posted.
[Galaxy S I9000 Android Development] ashwinds:
Came back to report that those settings work fine for normal use. It does appear that 1.2 + UV doesn't work too well on my phone. Will try more agressive UV values for the other freq. now leaving 1.2 untouched.
[Galaxy S I9000 Android Development] raspdeep:
Most of the time, you phone will be spent sleeping anyway, so try target UV for low frequencies. I can leave my phone sleeping for 8-9 hrs for only about 2% drop. The trick is to turn off APN/data connections which draws a lot of power.
[Galaxy S I9000 Android Development] xan:
When do you plan releasing 2.1 patch, so we can have one and only UV scheme? :)
[Galaxy S I9000 Android Development] dereknas:
Is there any other ways other than use scripts to set the preset settings rather than manually set after each reboot?
[Galaxy S I9000 Android Development] xan:
Whats wrong with the scripts way?

I cant see any other way than some auto-start application/hardcode values into kernel.
[Galaxy S I9000 Android Development] Razer(x):
Is it possible to have no-oc and undervolting?
[Galaxy S I9000 Android Development] xan:
Yes. Simplest way is to use Voltage Control + check no overclocking tickbox.
[Galaxy S I9000 Android Development] dereknas:
xan, thanks for the reply...well, errm, i'm kinda noob so i'm not so 'literate' in creating my own scripts....do u hv any samples of any generic script for this purpose?

btw, rasdeep, do you think you could integrate hardcore's work into your kernel?
[Galaxy S I9000 Android Development] xan:
Thats no problem - use Voltage Control to set values, apply, then [set on boot] and script will be automatically created.

Be sure to get correct version for the kernel.
[Galaxy S I9000 Android Development] ashwinds:
+1. I know raspdeep said he'd not be incorporating tweaks but would leave it to other kernel devs to incorporate his UV/OC code - but hardcore's work makes the kernel pretty smooth. And not to forget the sharpness fix.

PS: raspdeep posted a sample script with pretty conservative values (and no OC - you have to change 1000000 to 1200000 in the 2nd echo if you want to enable it. Its on this post.
[Galaxy S I9000 Android Development] ragin:
If this is stable mention it on the Title
[Galaxy S I9000 Android Development] raspdeep:
source released!
[Galaxy S I9000 Android Development] RetoGaeumann:
it always freezes..... :/

what am i doing wrong?? i flashed the 2.1 tar file with odin...
[Galaxy S I9000 Android Development] Arise:
hi there, thanks for making the sources public. Hope to see those changes soon integrated in other kernels.

Tried to test your kernel.

-25mV for the 1200MHz made my phone freeze as soon as I launched quadrant.

-25mV for the 1000MHz made my phone freeze during the last graphical test in quadrant.

Kinda bad?

Running at stock voltage seems to be fine, at least it completes the quadrant.
[Galaxy S I9000 Android Development] xan:
Nothing, OC makes ur CPU unstable.
[Galaxy S I9000 Android Development] miragebg:
How many of you, guys, have unstable OC speed on stock voltage?
[Galaxy S I9000 Android Development] raspdeep:
i will slowly include tweaks that i run when i find it stable enough.

did you UV or it hang even without UV'ing? you can try reducing the UV or disabling UV by setting it to zero. Alot of it is by trial and error and understand what your phone likes or dislikes. if your phone cannot OC properly, you can disable OC by using xan's app and check limit clock frequency to 1ghz (no overclocking) option

not all phones can do UV at 1.2ghz. if it hangs, set to zero at 1.2ghz and leave 25mV for 1ghz.

during benchmark, 99% of the time your phone will be at the highest frequencies (depending if you oc or not), if it hangs, you should look at changing the UV at that highest frequency. If it runs unstable with UV, disable it by setting zero at that.
[Galaxy S I9000 Android Development] raspdeep:
updated post #1 with OC/UV 101 and FAQs
[Galaxy S I9000 Android Development] glitterballs:
edit - I just need to refresh the page in xda app so im not replying to a question answered hours ago.

Sent from from my brain using Thumbs 2.0.
[Galaxy S I9000 Android Development] raspdeep:
what was your question?
[Galaxy S I9000 Android Development] ashwinds:
Fair enough. I think the changes are pretty stable (especially miss the sharpness fix) except for the pre-empt and the recent 300Hz switch. Anyway - trust your judgement on that :)
[Galaxy S I9000 Android Development] glitterballs:
I was answering a question xan had already answered several posts back that I somehow didn't notice when I was browsing with the XDA app.

I do have a couple questions though - What do the changes to the q202240.c (or whatever the name is) do? I can more or less follow what you're doing everywhere else, I don't get that one though. Also, I saw a post where you talked about turning off data or putting the phone into airlplane mode at night...have you noticed any change in battery use? I used to do this all the time, and get, as you mentioned, 1-2% drop over the night, but last night (first time I tried the new code) it was over 10% drop with the same conditions. But I wasn't sure if maybe I was trying to undervolt the low frequencies too aggressively, and perhaps the CPU was spending more time at higher frequencies (and voltages) as a result.

As an aside, I pieced together a kernel on my own and (finally) got it compiled and working. Thanks again for putting your code out there.
[Galaxy S I9000 Android Development] Arise:
Hello raspdeep!

You said that forcing the CPU using SetCPU to the same min-max frequency is not "forcing" things really tight.

So what about making 6 (six) kernels each one for every single stepping? Would that work better for testing/benchmark/stressing?

thx. :D
[Galaxy S I9000 Android Development] xan:
Thank you for updated OP!

Its not the case with Overclock Widget.
[Galaxy S I9000 Android Development] raspdeep:
if you have a 10% drop, something must be running in the background drawing cpu. you can check the "time in state" or process monitor to find the culprit.
[Galaxy S I9000 Android Development] raspdeep:
haha, but i dont think that is necessary. after some playing with it, you should get a hold of how your phone react to the UV settings.
[Galaxy S I9000 Android Development] raspdeep:
i dont see how overclock widget is different, what it does is still setting max_scaling_frequency in sysfs?

anyhow, i use setcpu because it provides a lot of other information that is useful
[Galaxy S I9000 Android Development] xan:
Well, I dont use SetCPU, but wit Overclock Widget I can actually limit clocks for testing purposes. (eg. on 100Mhz device is choppy as (u name it))

BTW Voltage Control updated ;]
[Galaxy S I9000 Android Development] raspdeep:
ya but that doesnt mean it did not jump above the frequency that you have set. you can check "time in state" and see the time difference it spent on each frequencies to determine if it went over
[Galaxy S I9000 Android Development] ashwinds:
I dont know how practical/feasible this is. But here goes anyway :)

Is there some way you can detect when the phone is going to hang and trigger off a reboot? My problem is not that its not stable, but that it freezes - instead if there was a way to detect that the "freeze threshold" is approaching to trigger a reboot, maybe with a stock/safe set of values, it'd be much better.
[Galaxy S I9000 Android Development] jeebspawnshop:
From what little I know of programming (admittedly nothing about Android/Linux...), an FC is the Windows equivalent of a program crashing and returning you to desktop.

A freeze is like the BSOD. It's when an app or the OS does something that was totally unexpected, and therefor could not be handled properly and it freezes the whole system.

What you're asking here is that you want them to expect the unexpected...

I don't think you'll get your wish ;)
[Galaxy S I9000 Android Development] ashwinds:
I realized that - but what i was hoping for is that each freeze would be on account of some value (or composite value) falling below a threshold. The threshold may well be different for each phone, but it could be derived out of logs. I do understand that some reboots maybe false, i.e. pre-emptive - but I for one dont mind the occasional false reboot as against suddenly realizing your phone hasn't been running for the last 10 minutes :)
[Galaxy S I9000 Android Development] android53:
Its impossible on a single core device
[Galaxy S I9000 Android Development] ashwinds:
Is the "freeze" a kernel panic? Or is it some other state?
[Galaxy S I9000 Android Development] xan:
Nope. If kernel is in panic it knows that smthing gone wrong but it doenst know what.

Freeze is a hardware fault, interrupted basic operation. The hardware just refuses to work, it has no "sanity" to realize that something failed.

Some more technical explanation would be nice :)
[Galaxy S I9000 Android Development] glitterballs:
Ok, so I guess a question I have is this - (xan this isn't something I'm asking you, just asking in general)

Let's say I have the 100MHz step UVed by X mV, and I use the phone so the processor has to crunch some amount of data. If I UV it too aggressively, is the processor going to jump to the next available frequency in order to crunch the data in a certain amount of time? Or is there just going to be a hardware fault? How does the kernel 'choose' what frequency it should be at? And, maybe this is a stupid question, but does lowering the CONFIG_HZ value pre-compilation affect any on this? It doesn't, right? I know the theory is that UVing gives you the same amount of performance at a given level of undervolting, I just want to make sure there isn't a caveat to the theory that I don't know about that might be causing my phone to jump to higher frequences (and use more battery that would be used at lower frequences less aggressively undervolted).

Perhaps using the 100MHz step as an example is a poor choice since according to raspdeep's OP they use the same voltage, but I hope what I'm asking about is clear.
[Galaxy S I9000 Android Development] xan:
I dont think so. UV has nothing to the frequency chosen. Eg. if governor sets CPU to 200Mhz, it doesnt check its voltage, its just: "I will (given the load in past few microseconds) run @200Mhz to satisfy the user". This would be some (u-name-it) explanation: (not sure its needed here, but will post for anyone interested :) )

Voltage 'given' to the processor shouldnt be confused with fuel. Its just the matter of 'blood flow', processor has to have electricity (blood) flowing to make it add, subtract and such. Its the same with human body, heart needs to pump a lot of blood when body works out, but when body consumes goodies from blood faster than heart could pump - you can faint.

As mentioned earlier, depending on the load from previous sampling period. Hardware faults could be named as "faints".

This is interesting, but we need someone better-informed.

Well, I've checked "Time in State" in SetCPU after setting 100-100Mhz and 200-200Mhz and from my observation clock doesnt "jump" It always stays @desired frequency.

It might be the kernel though, mine is: "SO_zImage_opt_ext_root_JPM-JP6_V3_9_OC.zip" from this thread: Super Optimized JPM-JP6 Kernel (3_9 STABLE) (2010-09-11)
[Galaxy S I9000 Android Development] raspdeep:
you are getting a little confused about UV and frequency scaling. they are not related.

1200000 - 1300 (<-added)

1000000 - 1275

800000 - 1200

400000 - 1050

200000 - 950

100000 - 950

Looking at stock voltage info above, each frequency runs at a certain voltage so UV is just reducing the voltage it runs at the particular frequency compared to stock. UV does not make the frequency jump. For instance at 100mhz, when does it decide to jump to 200 or higher? This jump (or frequency scaling) is determine by load and thresholds.

Let say a particular task it needs to run starts off at 100mhz, but since it need more CPU, it reaches a threshold of say 80% (of 100mhz) and it jumps to 200mhz and if it still reach say another 80% (of 200mhz), it jumps again and this process goes on until it reaches max frequency (if the task is still not completed). This up and down thresholds determine how the frequency jumps up or down..

there are some tweaks that i can do and is in my to-do list
[Galaxy S I9000 Android Development] raspdeep:
that is interesting, i may have to check it out.

so to double check, you set using SetCPU, conservative governor, max and min scaling to 100-100 or 200-200 and it doesnt jump even when you try to put more "load" like move your finger on the screen up and down real quick..
[Galaxy S I9000 Android Development] xan:
Yes m8, Im positive, not a one us on higher clocks even with benchmarks/rockplayer. Btw i have only slight uv, but kinda max my cpu is capable of :-)

flashing to it is straigtforward..
[Galaxy S I9000 Android Development] raspdeep:
i just checked v3_9, it still does what i said it does... run setcpu, set 100-100 or 200-200.. go to info table.. look at Time in state while you move your finger up and down the screen, see the time in state that it adds more time slice to higher frequency
[Galaxy S I9000 Android Development] xan:
ok this is TOTALLY strange, because im 100% positive it doesnt for me... i can post a vid if you dont believe me!
[Galaxy S I9000 Android Development] raspdeep:
hmm, weird, you sure not on performance governor or something? cos i know performance governor "fixed" the frequency but conservative doesnt and it has been like that since eclair
[Galaxy S I9000 Android Development] xan:
yes, conservative governor. tried different schedulers... same result. As far I remember it always fixed freq for me. Vid first thing in the morning.
[Galaxy S I9000 Android Development] Arise:
After testing all frequencies, I realized that I've missed to test the most important one. The 1.2GHz option.

So the bad news for me is that this freq. just won't be stable for me. As soon as I start a movie in RockPlayer the screen freeze.

I've tried with 0 (default) but after freezing, I decided to push things further, using adb, beyond 1300. So, I've issued the next commands (one per test, not both of them one after another):

echo "-25 0 0 0 0 0" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
echo "-50 0 0 0 0 0" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

Even for -50 ( that means 1350mV right? ) my CPU is not stable and it freeze.

I have a slight feeling that -25 is a little better, cause the movie even started playing a few frames, but is just a feeling.

So, I understand that specs said it should be max 1.31v (equivalent of 1310, right?) but I just can't accept it won't work for -50. IMO I was damn generous with the voltage juice.
[Galaxy S I9000 Android Development] raspdeep:
Are you running in software or hardware mode?

A few pages back, we were discussing about rockplayer and there is version optimized for arm_v7.

Also, if you can run any other programs at 1.2ghz without crashing except rockplayer. It is still unfair to say 1.2ghz is unstable for you.

As long as you know the risks that you can damage the CPU by running above the max voltage suggested and still willing the take the risk, more power to you!
[Galaxy S I9000 Android Development] Arise:
It does have a system mode and a normal mode.

I choose normal mode, I guess system mode is something where GPU acceleration is involved, right?
[Galaxy S I9000 Android Development] xan:
Mine says Hardware and Software mode. Hardware -> using hardware decoders, software -> pure CPU (ALU?) calculation.

Arise, I have similar situation, tried OV +25 and still 1200Mhz unstable. It seems we are just out of luck. (Like I always am with overclockable thingies)
[Galaxy S I9000 Android Development] Arise:
I have RockPlayer 1.0.31_v7 and 1.1.47 for armv7. Both of them shows me System mode and Normal Mode. There is not such an option like Hardware/Software.

Don't know what to say much about this, but is kinda hard to accept that even for some extra juice I can't make it stable. And I don't feel like going over 1350mV.

The max UV I can do for the 1000MHz is 25mV, and the max UV I can do for 800MHz is 50mV, that is keeping the Rock Player stable.

But my CPU freq is jumping, setting it in SetCPU to the same min/max value will give me short jumps when I move from tab to tab and I switch back.

I agree that most of the time, the frequency is somewhat locked because my quadrant scores goes lower and lower with the frequency.
[Galaxy S I9000 Android Development] xan:
I got this: (see screenshots)

"RockPlayer Universal" from market.

//edit: Just got another version and its like yours.

It doesn't actually matter, both are unstable @1.2Ghz for me.
[Galaxy S I9000 Android Development] raspdeep:
just checked rockplayer,

system = hardware

normal = software
[Galaxy S I9000 Android Development] raspdeep:
new version for testing
[Galaxy S I9000 Android Development] dupel:
- fast scaling speed jump

- tweak for faster response

Can you clarify a bit on this?
[Galaxy S I9000 Android Development] wurzelsepp3:
After I flashed the new kernel my phone was stuck before the bootanimation.

Flashed 2 times with the same result, so I reverted back to uv-2.1 debug and everything works fine again.

Edit:

Sorry my bad, the file was somehow only downloaded 99.9% (stupid opera),

redownloaded and flashed again. Now everything works.
[Galaxy S I9000 Android Development] Arise:
Still not solving my OC problems. :(
[Galaxy S I9000 Android Development] ashwinds:
Well... it does appear snappier. As for battery since you asked that we keep our eyes open - over 6% in 2.5 hrs of mostly idle usage... it appears a bit steep. But will check more and revert to you.
[Galaxy S I9000 Android Development] raspdeep:
sorry bro, i cant do anything if your hardware cannot handle :(
[Galaxy S I9000 Android Development] dahuzi:
I will not try OC as concerning of battery drainage. But OP did a good experiment. Keep it up.
[Galaxy S I9000 Android Development] zenkinz:
considering that the tweak is extending the range of clock freq, rather than over clocking consistently at 1200mhz, I think the battery drainage is going to be marginal.

the biggest battery killer in my observation has to be the google pushmail. turned it off my phone battery level consumption is about 1% an hour. but it's quite silly do so because once i turn off google account sync, I am turning all the other mail sync as well.
[Galaxy S I9000 Android Development] xan:
Ok, I confirm - NO JFS support. Takin recovery steps ATM.

It seems to be possible to recover from this, just changed config from JFS to EXT4, and now I'm recovering data from backup made prior to flashing.
[Galaxy S I9000 Android Development] raspdeep:
yes, using sztupy ramfs but jfs not in yet.

thanks, will take a closer look

if you are concern about battery life, wait for the UV version and use setcpu to limit max frequency to 1ghz

try turn off APN :)
[Galaxy S I9000 Android Development] zenkinz:
I could do that (in fact, just turn off data connection), but it defeats the purpose of me carrying a smartphone :D
[Galaxy S I9000 Android Development] DocRambone:
Add your gmailaccount to the email app. Skip google sync, and let the email app sync the gmail
[Galaxy S I9000 Android Development] zenkinz:
galaxy email app is slow to open as compared to gmail. or is there a light weight email app you would recommend?

looks like this is the only way out for me. but i assume disable google sync, it'll not affect market access?
[Galaxy S I9000 Android Development] xan:
Using EXT4 config:

Linpack: ~16.500 Mflops

Quadrant: 1750-1850 pts.

And unfortunately the same freezes with Asphalt and generally 3d graphics like on ur previous Eclair versions.
[Galaxy S I9000 Android Development] DocRambone:
http://xdaforums.com/showpost.php?p=8789398&postcount=4

I use the aosp email and it rocks, the CM version may even be better.

No problem with market without google sync

Sorry for the offtopic :)
[Galaxy S I9000 Android Development] xan:
How to try ext2? Does JFS option stand for ext2 for now?
[Galaxy S I9000 Android Development] ragin:
+10 for this... been waiting for a long time.
[Galaxy S I9000 Android Development] eRajesh:
Welcome back Rasdeep!:)
[Galaxy S I9000 Android Development] Ibanez33:
I know they don't count for anything... but look at the pretty numbers!!! 2025 quadrant

Tayutama Edition Lite v1.0.0
[Galaxy S I9000 Android Development] EarlZ:
We are making progress here 1.2Ghz on our device but the other Galaxy S device already has an alpha 1.6Ghz xD