yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] Ace42:
What's the proper way to add this to the user.sh:

(echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo 122880 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

echo 614400 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq)

^Is that the corr format, I just copy that then done?
[G1 Android Development] Ohsaka:
Just remember if you create a file in windows notepad and then copy it to the phone, you need to run 'dos2unix <file>' from terminal on the phone. I use an editor that preservers UNIX linefeeds but forgot I initially created the file in Windows and it was slowing me down. I also put a semicolon at the end of every line.

For cm5 you call the file 'userinit.sh' and put it in the '/sd-ext/' folder.
[G1 Android Development] Ace42:
Thanks I use Win7, but I pulled the user.sh from the mtslide rom i'm using to add the above lines.
[G1 Android Development] pershoot:
Re: ToAsTcfh Overclock Kernel Patch :: Downloadable Kernels For G1/32B/32A

ohsaka,

That works. You could put some error checking in there (if an invalid value passed, etc.). You could also allow for more then a pair value on cmd line.
[G1 Android Development] Ohsaka:
BTW, I hate unix shell scripting... lol. This is the same reason why I'm not a kernel guy. I'm spoiled by Java programming.

#!/system/bin/sh
#
echo starting change_oc.sh...;

CPUFREQ_DIR="/sys/devices/system/cpu/cpu0/cpufreq";

#make sure even number of args
argsmod=$(( $# % 2 ));
if [ $argsmod -gt 0 ]; then
echo "error, wrong # of args";
exit;
fi;

#loop, grab two args at a time
while [ $# -gt 0 ]
do
SYS_FILE="$1";
echo "echo $2 > $CPUFREQ_DIR/$SYS_FILE";

if [ -e $CPUFREQ_DIR/$SYS_FILE ]; then
echo $2 > $CPUFREQ_DIR/$SYS_FILE;
else
echo ERROR: $CPUFREQ_DIR/$SYS_FILE does not exist;
fi;

shift;
shift;
done

echo finished....;

Obviously you don't want to change the same value twice... but it shows the loop works..

# ./change_oc.sh scaling_min_freq 245760 scaling_min_freq 128000
./change_oc.sh scaling_min_freq 245760 scaling_min_freq 128000
starting change_oc.sh...
echo 245760 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 128000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
finished....
[G1 Android Development] Ohsaka:
This solution isn't as user-friendly as setcpu, but I like having more fine-grained control. Especially when testing overclocking... The scripts all reside on the /sdcard partition and will survive wipes.

Unzip the 'gscript_oc.zip' file into /sdcard/gscript directory. Then when you run the gscript app you can click Menu->Add script and pick any of the scripts you want to run frequently. They all require the "need SU" checkbox. You probably wont need to use all of them, I just included a bunch of them as examples.

Of special note... the 'set_all_oc.sh' script. You can edit it to set all possible values from one script. It will process every pair of name/values you add.

(I also included the Gscript apk file in case anyone needs it.)
[G1 Android Development] Sik-1:
Um instead of creating a gscript y not just use the file that comes with all roms the sysctl.conf, if u check in the /etc/init.d folder u would see that it runs first..o and the sysctl.conf file is also in the /etc folder
[G1 Android Development] Ohsaka:
This is more so you can test out the performance/effect of changing different overclocking related settings quickly and easily. No editing text files or using the terminal every single time you want to change your max frequency...

Sample screen shot of the one-click possibilities...
[G1 Android Development] coolbho3000:
What is the issue with setcpu, autodetect, and the advanced menu? Autodetect sweeps any and all available frequencies, and it detects a new set every time the app starts (if you update your kernel and the new kernel has different freqs, setcpu will change the available frequencies list accordingly). If it's not detected by setcpu, the frequency is not available in the kernel. If setcpu is not doing its job even with autodetection, I will fix it immediately.

In the next version I'm going to do away with my hardcoded frequencies entirely.

Sorry I didn't see your post, but don't use userspace. You need to echo to scaling_setspeed and control the scaling completely from userspace or else it is useless.
[G1 Android Development] treperio:
the patch in the first page work on a g1 with super D 1.11 (ramhack)?
[G1 Android Development] Ace42:
Can I change sd-ext to something else?(dont use cyan)
[G1 Android Development] lefeudedieu:
With my SuperEclair :

at 729000Mhz stable with USB :rolleyes:

http://forums.smartphonefrance.info/viewforum.php?f=42
[G1 Android Development] juangil:
@LFD

thx for sharing your update, downloading now
[G1 Android Development] jad011:
what does the invisible lockscreen look like ?
[G1 Android Development] Ohsaka:
You would have to edit it in the scripts...
[G1 Android Development] Sik-1:
y would u download, cant u read it says with usb, where are u gonna go???? lol
[G1 Android Development] jad011:
boot-cm_2633.4_ds_32a-oc-uv-fp-051210.zip

boot-cm_2633.4_ds_32a-oc-uv-xtra-fp-051210.zip

anyone know what the difference is between those two overclock kernels ?
[G1 Android Development] Sik-1:
xtra has a few more tweaks, tweaks that if ur asking for a difference u wouldnt understand, so just get the xtra and enjoy, its pretty sweet
[G1 Android Development] juangil:
its just translucent (see thru)
[G1 Android Development] tnpapadakos:
anything that says "xtra" must be better

more=better
[G1 Android Development] CharonIDRONES:
So I have to ask as I do not know the answer, but I have read earlier in this forum that these kernels work with Super D 1.11. But I have flashed pershoot's most recent kernel, and using SetCPU 1.53 with auto detect. I put the min and max to 576, and it reports it as such in the info for SetCPU, however it reports 460 when I cat /proc/cpuinfo. I realize that the kernel is more up to date with these 5.0.7 one's, but is there any of pershoot's (with Aanykernel) that behave differently? I have searched and could not locate the answer so any help would be appreciated.
[G1 Android Development] dumfuq:
That's normal with the newer kernels. try...

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
[G1 Android Development] CharonIDRONES:
Re: ToAsTcfh Overclock Kernel Patch :: Downloadable Kernels For G1/32B/32A

Thank you so much dumfuq, again! Reported back at 576000. My LinPack was doing 2.5ish so I had reason to believe that it was working, but just didn't know if it was just scaling up to achieve it. Thank you again.

-------------------------------------

Sent via the XDA Tapatalk App
[G1 Android Development] vincom2:
Hello pershoot,

regarding my previous issue report (the one about opening many things in browser and playing music and having the phone soft reboot on me), I haven't tried flashing the original kernel to test yet, but I haven't been able to reproduce the issue again on your kernel either >.>
[G1 Android Development] coolbho3000:
To add to this, the kHz value in system info reads from scaling_cur_freq, and so does the MHz value in the main interface.

BogoMIPS can give entirely different values but it changes linearly with frequency.
[G1 Android Development] Super Jamie:
I guess my Magic doesn't like overclocking. At 576MHz I get random FCs and strange things like the MMS app just quits back to homescreen. Back to 528MHz and none of that happens. Oh well, sucks to be me.

That would more or less confirm what I said earlier about different individual handsets being able to handle different overclocks. My G1 seems to sit happily at 633MHz, though I haven't used it as a daily phone in a while so maybe further testing would be better with a slower speed.

Also thanks to pershoot for including a bunch of useful modules, namely compcache. Even without the overclock it's nice to have an updated, faster kernel. Dwang v1.17.1 is getting a bit long in the tooth now. I'll be applying this to all my Donut ROMs from now on :)
[G1 Android Development] XxKOLOHExX:
Re: ToAsTcfh Overclock Kernel Patch :: Downloadable Kernels For G1/32B/32A

Can anyone help me when I build my edited kernel with this hack I can't seem to compile I get a sapphire board... missing and 3 errors following it dealing with the sapphire board missing and an error 1 and 2. Thanks for the help in advance. Will add errror once I get home.
[G1 Android Development] samsci:
interesting tidbit

One thing I am finding interesting is that my phone goes through random reboots at 633mhz periodically unless I keep AIM running in the background. Aim is on the notification bar for me to click on and so far, no reboots in 8 hrs. When I turned it off, I had 3 random reboots in 30 minutes.

Running Dumbuq's latest kernel at 633mhz on Cyan 5.07 test 5. Without the kernel patch, no reboots at all or if I move it down to 576mhz no reboot.
[G1 Android Development] pershoot:
new dream/sapphire (32b/a) kernel images posted - http://droidbasement.com/db-blog/?p=404
[G1 Android Development] xaueious:
Maybe if you provided more details some people can help.

I have no experience building 2.6.33.x, but can't you just git pull cm-kernel and then use CM5 as a base config?

Or are you compiling for 32A?
[G1 Android Development] XxKOLOHExX:
Trying to compile for 32B and i will get the error report and post to pastebin :D

http://pastebin.com/DcWRxpUj
[G1 Android Development] ubernicholi:
is there a changelog?

or is it just a compatibility update for cm5.0.7 t5?
[G1 Android Development] dumfuq:
did you just clone the kernel or did you set your local branch to his DS branch?
[G1 Android Development] XxKOLOHExX:
I cloned cm-kernel and then took 2 files from pershoot's github and placed them in the respected spaces and tried to compile.
[G1 Android Development] dumfuq:
if you just did a straight up clone, chances are your on the 2.6.34 branch but not the 2.6.34-DS branch. You need to set up a local branch that follows his DS branch.
[G1 Android Development] XxKOLOHExX:
Oh okay thank you so much :D

Going to see if i can get this fixed :D
[G1 Android Development] stormmonkey:
observations..

I'm currently running SuperD 1.11, 96MB SWAP, and Pershoot's 2.6.33.3 OC Kernel (non-xtra) on a MyTouch3G. The Phone runs amazingly fast, however, battery life has greatly decreased ~15% less power end of day vs my previous setup (cm4.2.15.1, compcache, cm's stock kernel). Additionally, running 2.6.33.3 doesn't prompt to unmount storage for usb transfers to a comp. and 2.6.33.4 seems less stable, force closes / slow performance after the phone's been on for a while.

Is anyone else having similar issues or have any suggestions? Thanks, -Dan

UPDATE:

Battery drain seems to have been a calibration issue. I drained the battery until the phone turned off, then recharged fully. It now seems to report more accurate percentages. As for USB/Stability issues I switched to the other OC Kernel (Universal Overclock...) and things seem to be running more smoothly for me. Thanks for everyone's input and hard work. -Dan
[G1 Android Development] pershoot:
Re: ToAsTcfh Overclock Kernel Patch :: Downloadable Kernels For G1/32B/32A

My kernel set has not been tested on donut nor was it intended to be run on it.

However, with that being said, reflash the rom clean (clearing cache, etc.), and re-setup setcpu as instructed in the blog post. if setcpu causes issues then echo in the values at boottime (search in this thread; there are 3 values to set). No extra settings and no addons, then observe.

If u still face issues, then I would not use my kernel set while on donut.
[G1 Android Development] pershoot:
also your using swap. that is why your getting slowdowns over time.
[G1 Android Development] Super Jamie:
You do realise running your phone faster uses more power, right?

Battery life is directly proportionate to CPU speed. Try underclocking to 245/122 for a day and see how much battery you (don't) use. This is probably why manufacturers release their ROMs with 384MHz max.

I'm running Pershoot's kernel at 528MHz on Donut (setting ondemand and scaling speeds with init script) and I'm not noticing any huge difference from Dwang's original kernel. I don't use A2SD or swap, though I do use 32Mb compcache.
[G1 Android Development] tnpapadakos:
pershoot, dumfuq, where are you?

man i'm jonesing for some oc-uv goodness on cm test6
[G1 Android Development] dumfuq:
here's another boot.img that won't boot ;)

oc825-cm-5.0.7-test6-boot.img
[G1 Android Development] tnpapadakos:
here's an update.zip of test6 with dumfuq's oc825 kernel in it

just flash it like any other update zip; i created it cause of the problem with flash_image in terminal emulator and out of memory errors
[G1 Android Development] G1ForFun:
From the looks of that video and linpack score, it definitely seems real. Just a shame that hardly any of us have a "Robbers aka Rogers" G1.

Everyone pray to the android gods for a dev to come help us 2.x radio G1 users.
[G1 Android Development] Jefmeister:
I'm wondering if the little bit of extra speed would be enough for smooth viewing of xvid's in yxflash. It's only just a little bit laggy now.

Also, this hopefully will smooth out scrolling in menu's and dialer.

On top of that iPhone 3GS = 600 mhz, that would make the g1 just 14 mhz faster :p
[G1 Android Development] G1ForFun:
Lol I was thinking the same thing....bragging rights.
[G1 Android Development] erlern:
But they'll only retaliate by saying that frequencies do not determine CPU performance :P haha
[G1 Android Development] infinitybiff:
bumping in hopes someone compiles a kernel for the g1. Like I said, I'm more excited about this than the "mytouch slide port":D
[G1 Android Development] acejoker25000:
hmmmm putting this in the mytouch slide port!! awesomeness!!
[G1 Android Development] phhusson:
Which is totally true since iPhone has some floating point stuff, while MSM7k has nothing at all.

And I'm not even mentioning the 3D chip or the ADSP stuff.
[G1 Android Development] bernZ:
I'm willing to give this a whirl after my exam at 330 today. I have a Rogers Dream, with 3.xx radio.

Currently sitting on 1.10.2 SuperD. OP, mind getting in touch with me via PM to guide me through? From reading, it appears that this cannot do any permanent damage to my phone. If I take a nand/ext backup and then flash your boot.img and wlan.ko, I can revert to my previous status with nand/ext backup. Is this correct?

This would give me some more confidence in flashing this and testing it out for you guys. Just trying to give back to the community. :)

Edit: Seeing as overclocking is always a crapshoot, is it possible that I will not be able to revert to my old nand backup simply because the phone isn't even stable enough to boot back into recovery?
[G1 Android Development] ivanmmj:
The recovery uses its own kernel. I tested a kernel that I built myself and when it failed, I just did a nand restore and it was fine.
[G1 Android Development] bernZ:
If I understand correctly then, the kernel itself is not touched until the machine actually boots. The recovery is a completely separate package that the phone loads, correct? Under this assumption, it would appear that the kernel is isolated from recovery, so I should be good to flash any random kernel I want without fear of bricking.

Could you confirm this? I'll be testing the patch later tonight and I'd love to offer some feedback for you guys.

Edit: *facepalm. I'll test tonight. I can't read, evidently.
[G1 Android Development] xaueious:
If you have a G1 with the 3.x radio, go ahead and flash the EBI1 update.zip.

To go back you just need to flash the merlos non-ramhack kernel port or beav_35's ramhack kernel port.

When booting the phone, try not plugging in your usb cable at any time after the bootscreen is completed. I was running okay until I plug the cable in, as I said earlier. Maybe that error can be avoided by making the kernel again patched with a lower clock than 614 MHz. If someone has the time to test all that it would be great.

As for battery life concerns, this shouldn't be that much more intensive on the CPU because there's no voltage increase. The phone should also scale no differently than if it didn't have the oc kernel installed.
[G1 Android Development] bernZ:
OK. I said screw it to studying temporarily; took a backup and flashed the new kernel. I kept the USB cable plugged in the entire time and it worked fine. Downloading Linpack now to observe changes.

-- Linpack run, phone scores at 2.6MFlops. Despite this, I don't really feel that the patch does much for the phone at this time; the change isn't noticeable. Successive runs leads to a crash in the phone. I do -not- have the JIT hack.

Further notes: I've also tested rebooting the phone without the cable plugged in initially. Once the phone started to boot, I plugged the cable in. No issues there either.

Final note until new post: Linpack at standard clocks is about 2.1 to 2.2. I don't know whether or not we'd have access to voltage control, but if we do, I say we should increase by a notch and see if this stabilizes the overclock.

If you can offer up a new kernel maybe around 550MHz to 580MHz for stock voltages, I'd be willing to try that as well.
[G1 Android Development] infinitybiff:
You flashed the kernel for the g1? and got it to work?!?!?!?!
[G1 Android Development] bernZ:
I flashed the kernel because I had a Rogers Dream with a 3.xx radio; with this radio, my phone requires a EBI1 kernel.
[G1 Android Development] G1ForFun:
A quick search of his posts reveals

"I have a Rogers Dream, with 3.xx radio."

lol and I am late.

this is the one time I wish I had a Robbers G1...lmfao
[G1 Android Development] infinitybiff:
Forgive me.... I got excited :(
[G1 Android Development] bernZ:
As far as I know, G1s can all run the 3.xx radios. It's just a pain in the rear because you have to have customized Amon_RA recovery (1.x.xR version) and a ROM that supports EBI1 kernel.

I've found my own way to resolve the EBI1 kernel issues by using this tool; I don't know how much it affects the performance of the ROM, but I know that at the very least I can keep up to date with releases.

Said tool is here: http://faruq.yandao.com/magicport/
[G1 Android Development] G1ForFun:
No need to ask for forgiveness.

______________________________

If it can boot on the robbers g1....then it can boot on the other g1's. It's just a matter of somebody taking the time to repack the kernel properly. I wish I was Cyanogen (beholder of all things android) right now so I could have this working in a jiff.
[G1 Android Development] xaueious:
Thanks for flashing it. Interesting that you get different results than me, but this does prove that there is a bit of instability at this clock for the G1.

Linpack did not freeze my phone at all provided that I did not plug the USB cable in by the way. My phone is only 4 months old, for your reference.

We should be stable at a lower clock for the G1, but that would make the oc even less noticeable, but we know it does work. I want someone to try this on a Magic with old radio. Plus if you were running some EBI1 port you were probably coming from wg-kernel, which I think is more responsive than cm-kernel.

Yes ALL G1s can run the 3.x radio. Changing the radio is actually pretty easy, but I don't recommend it at this time since the boot isn't even stable and it would be a pain to switch back and forth.

All the tool does is generate wlan.ko and boot.img, which basically replaces the kernel. To apply this oc kernel you are doing the exact same thing, except I compiled this from source and the tool is an alternate solution using pre-compiled kernels.

It's no so much as a customized recovery than a recovery running a different kernel.
[G1 Android Development] farmatito:
Hi,

attached you'll find a boot image and modules for cm 4.2.15.1 @ 614 Mhz

Overclocking: 19.2 x 32 = 614,4 (0x20)

This boots on my G1.

Unzip and for testing do:

sudo fastboot boot new_boot.img

if it works you can make it permanent:

TAKE A NANDROID OR BART BACKUP!!!!!!!!!!!!!

sudo adb devices
adb remount
adb shell umount /system/modules
adb push wlan.ko /system/lib/modules/
adb push modules.sqf /system/modules/
adb shell mount /system/modules

Then flash the boot image

adb push new_boot.img /sdcard/
adb shell sync
adb shell
flash_image boot /sdcard/new_boot.img

and reboot
[G1 Android Development] pershoot:
tonight/tomorrow morning ill roll up another update to include the oom/lowmemory changes in cy's git. sorry been working on trying to squash another bug elsewhere...
[G1 Android Development] rynosaur:
Could you do the same for your JIT hack as well? I'm a true JIT believer :D
[G1 Android Development] tnpapadakos:
awesome, thanks
[G1 Android Development] qbdx:
I overclocked the phone, had it running at pretty max speed and not long after that the sim card fried in the t-mo g1.

A simple test to check whether you should be overclocking or not is to remove the battery and run your fingers against the back where the battery sits and on the battery it self to see if it is "bumpy//bubbly" which indicates the battery or phone has some internal heat damage.
[G1 Android Development] Boomgawd:
Using the 18th release on test-6

Is it a bad Idea to use your EBI1 kernel (2.33.4) from may 18th on test-6? I am definetly using it now and it seems to works fine..

Looking forward to the latest update.
[G1 Android Development] Gerdal:
setcpu can measure the temperature of the battery and if exceed certain temperature, it can automatically reduce the CPU clock speed.
[G1 Android Development] alongenemylines:
dumfuq, thanks yet again for the updated kernel!

test6 @ 614mhz is soooo smooth

a request though - could you add a speed around 350mhz? i'd like to keep my lower limit higher than 245, but lower than 480
[G1 Android Development] samsci:
I have to second that... I am running at 691mhz now and it is running very smooth. No issues to report at all.
[G1 Android Development] xaueious:
352 MHz is possible with Turbo config.
[G1 Android Development] pershoot:
DS (32b/a) kernel images posted (kernel 2.6.34) - http://droidbasement.com/db-blog/?p=425 - pls take note of the known issues
[G1 Android Development] rynosaur:
Thanks for all your hard work!
[G1 Android Development] pershoot:
Re: ToAsTcfh Overclock Kernel Patch :: Downloadable Kernels For G1/32B/32A

Pls let me know of any issues (aside from the known issues)
[G1 Android Development] borodin1:
I still can't figure out a difference between reg kernel and xtra kernel. Anyone could shed a light on that?
[G1 Android Development] Gerdal:
@pershoot: Can you create a boot.img with frequencies higher than 576 Mhz? Please...
[G1 Android Development] Klyentel:
performance....mostly speed. IMO.
[G1 Android Development] Klyentel:
He will do it when and if he does it, and that's the bottom line...:D
[G1 Android Development] Klyentel:
Noted. i never mount my sdcard anyhow....I use wifi for all my file transfers;)
[G1 Android Development] Klyentel:
Choices of solutions to such a situation:

A. Bigger battery.

B. Better Phone.

C. All the above.

D. Stop overclocking!
[G1 Android Development] tnpapadakos:
is this test7 or test6 compatible
[G1 Android Development] pershoot:
Re: ToAsTcfh Overclock Kernel Patch :: Downloadable Kernels For G1/32B/32A

It works fine with both.
[G1 Android Development] tnpapadakos:
thank you pershoot
[G1 Android Development] pershoot:
im investigating a no boot issue on some 32b devices for .34 kernel.
[G1 Android Development] ceas909:
i had this issue trying to flash over cm test 7... but i wasn't able to get any documentations sorry... but i can confirm it.. was stuck at my touch screen..

p.s. i flashed the xtra boot.img
[G1 Android Development] tnpapadakos:
here's an update.zip of cm5.0.7 test7 with the oc825 by dumfuq already in it

i used the oc825 kernel from dumfuq's test6 version, and it works just fine (so far)
[G1 Android Development] dumfuq:
No need for a test7. No changes in the github since my last release.
[G1 Android Development] pershoot:
Re: ToAsTcfh Overclock Kernel Patch :: Downloadable Kernels For G1/32B/32A

Ceas, can u pls get me full logs?

Thx.