yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] dumfuq:
for cm-5.0.8-test2

oc825-cm-2.6.34-mt-v7-signed.zip(remember...will not boot without setting freq)

also included v7 of the multitasking patch.
[G1 Android Development] legend221:
Pershoot and dumfuq many thanks for your kernels they have definitely come in handy.

I have noticed a more faster and stable Super E with this involved and have already directed them to your last 2 releases of the kernel.

Can I ask what exactly the latest version includes other than this and what other advantages it carries?

Contains:

- Offset the reclaimable memory a bit if using swap, by dumfuq and farmatito

- Update Compcache to 0.62

- some more cgroup options

- namespaces support (excluding network)

- deadline i/o scheduler

- v4 block device and data integrity support

- errata 411920 applied

--->> http://droidbasement.com/db-blog/?p=532
[G1 Android Development] Jurai:
forgive me, but is there a stable UV'd kernel which has the ramhack patched in as well?

thanks to all for their hard work
[G1 Android Development] PorchSong:
Pershoot,

Does this kernel still have the the "dirty" sd dismount issue?
[G1 Android Development] pershoot:
if your speaking of usb unmount, that has been fixed.
[G1 Android Development] PorchSong:
Yes I was, and thank you. Also, is Cyanogen using your kernel? I noticed in 5.0.8 test 1 (have not loaded test 2) that you can take phone up to 576.
[G1 Android Development] pershoot:
i believe he has integrated the relevant in-source mods in to his kernel (aside from bzo's turb_mode patch). i have not looked at the relevant sources though.
[G1 Android Development] PorchSong:
Test 2 dropped the higher clock -- back to stock for cyanogen. Anyway, thank you for your fine, fine kernels.
[G1 Android Development] goofyog:
Is there a way to use settings from oc' ed WM devices To get stable 768 mhz like nueROM? http://www.nuerom.com/BlogEngine/post/2009/09/06/Touch-Pro-running-at-800MHZ.aspx

thous processors are the same as g1/mt3g but have stable 768mhz
[G1 Android Development] pershoot:
new dream/sapphire kernel images posted - http://droidbasement.com/db-blog/?p=538
[G1 Android Development] dumfuq:
here's my update for 5.0.8-t3

oc825-cm-2.6.34-8t3-signed.zip (remember to set frequency in order to boot)
[G1 Android Development] anomalous3:
ahh finally more oc goodness for those of us without swap :)
[G1 Android Development] tnpapadakos:
awhile back you mentioned that the mt portion of your kernel won't work unless swap is enabled, and cyanogen has now implemented it in 5.0.8 test3

cyanogen has said that he's only using compcache and that cm doesn't do anything with swap by default only a bit of the built-in compcache

so should one use swap with 5.0.8 test 3? or compcache? or both?

i tried compcache by itself- i don't like it...i noticed some lag when scrolling call log, moving between screens on launcher

i tried both together, same thing

i tried neither, same thing

i tried just swap, dont notice the lag

any comments or guidance here?
[G1 Android Development] Pfeffernuss:
Using only Swap works by far the best for me as well, whatever other people might say. Without this kernel multitasking is simply impossible. Everything will be reloaded once you leave an app only temporarily. CC doesn't solve this fully, Swap however does.

There is a chance that once in a while you do have an unresponsive phone due to heavy Swap thrashing, but this has only happened once for me, in about a week. Swap FTW! :rolleyes:
[G1 Android Development] dumfuq:
Really I think its all personal preference. It shouldn't really matter which one you choose. It seems my phone will lag occasionally no matter which method, including no swap or compcache at all. I myself use compcache w/ 64mb backing swap partition.

Here's my current userinit for reference:

#!/system/bin/sh

# set cpu to min/max
echo 245760 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 614400 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
#echo 528000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

#set governor to conservative
echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

#echo 76 > sys/devices/system/cpu/cpu0/cpufreq/conservative/up_threshold
#echo 12 > sys/devices/system/cpu/cpu0/cpufreq/conservative/down_threshold
#echo 8 > sys/devices/system/cpu/cpu0/cpufreq/conservative/freq_step
#echo 500000 > sys/devices/system/cpu/cpu0/cpufreq/conservative/sampling_rate

# start up compcache
modprobe ramzswap
rzscontrol /dev/block/ramzswap0 --memlimit_kb=32768 --backing_swap=/dev/block/mmcblk0p3 --init

echo 56 > /proc/sys/vm/swappiness;
swapon /dev/block/ramzswap0;

# link /system/sd/bin /usr/bin
mount -o remount,rw /dev/rootfs /
mkdir /usr
chown root.root /usr
chmod 755 /usr
ln -s /sd-ext/bin /usr/bin
mount -o remount,ro /dev/rootfs /

# set bash to default
busybox mount --bind /usr/bin/bash /system/bin/sh
[G1 Android Development] tnpapadakos:
thanx Pfeffernuss
[G1 Android Development] rps13:
While looking through the android section of the htc touch CDMA, I found this thread about GPU overclocking: http://xdaforums.com/showpost.php?p=6734112&postcount=1

For devs source code is here: http://git.linuxtogo.org/?p=groups/...2;hb=23ff83048726252bc785699fc749a3e364a3bdb0. Is it possible to compile a kernel just by putting this file in the kernel for a G1 or Magic? Or is modification required? (I think it should work since the MSM7500 is very similar to the MSM720xA, I think it may even have the same ARM9 core for graphics, but am not sure)
[G1 Android Development] fl3xo:
Someone knows how to add conservative governor to pershoot oc kernel without compiling it from source? actually, i can access to a netbook only with win98 for a couple of days, so no way to compile it. I've tried dumfuq kernel, but is not stable for me at any cpu freqs; anyway, conservative governor decrease my battery drain of about 20% for me under usual use.
[G1 Android Development] ownjoouk:
pershoots kernel with swap has actually made 2.1 useable for me now. I was fed up with the constant dumping from memory but now it's reasonably smooth and so far hasn't dumped my launcher from the memory!!
[G1 Android Development] animefans:
I could be wrong, but I think governor must be compiled in
[G1 Android Development] fl3xo:
I found something for the milestone:

http://android.doshaska.net/conservative

but , as expected, it doesnt work fo my magic.
[G1 Android Development] animefans:
The link provided a .ko file (think that's a module in linux world)

The ko file is still compiled from linux kernel (or android kernel source, in this case), but compilation none the less

If my guess is correct, kernel source and module source must be from the same tree

If someone choose to compile their kernel, along with conservative governor as a module, s/he can then upload this module for you to use, but this someone better use the same version of kernel as you

ie if you are on 2.6.34 kernel (like 5.0.8 test series), this someone has to use 2.6.34 kernel source to compile, and not 2.6.33 (aka 5.0.7 series I think)
[G1 Android Development] fl3xo:
thanks for interest, tomorrow i'll return home and compile my own
[G1 Android Development] pershoot:
JIT for CM508 - DS - http://droidbasement.com/db-blog/?p=620
[G1 Android Development] joseangel.alv:
I think you can have one or more governors available... it depends on your kernel.

You can show which ones are available with:

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

The current used one:

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

and, if there are more than one, you can change it (to conservative, for instance) using:

echo "conservative" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

The governors available in pershoot kernels are ondemand and performance.

Regards. :)
[G1 Android Development] pershoot:
ondemand and performance.
[G1 Android Development] joseangel.alv:
True, sorry... an error derived of my also erroneous instructions... it must be:

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

to show the available governors
[G1 Android Development] tnpapadakos:
no boot for me after flashing it
[G1 Android Development] pershoot:
Re: ToAsTcfh Overclock Kernel Patch :: Downloadable Kernels For G1/32B/32A

It works (one report of success (32a user)) thus far. Take note of the Note: (of it being unstable).
[G1 Android Development] rps13:
JIT works fine for me as well, though when flashing it with dumfuq's kernel for 32A I would get a boot loop...
[G1 Android Development] dumfuq:
Working fine for me on my G1.
[G1 Android Development] smuvman:
jit

might as well ask. did it make any difference?
[G1 Android Development] dumfuq:
Jit

Honestly I'm not a fan and I never keep it around, but for some reason I still try ;)
[G1 Android Development] tnpapadakos:
i'm waiting for cm 6 (froyo) because its built in, should be out in a week or so
[G1 Android Development] bugmenever:
hi, has there been any update on that ?:confused:
[G1 Android Development] lefeudedieu:
Please oc 825 for Froyo :(
[G1 Android Development] zimphishmonger:
Check out the dumfuq's "Kernel Corner" thread for it
[G1 Android Development] bernZ:
I suggest the above post be copied verbatim or referred to in the OP.
[G1 Android Development] aaraya1516:
It boots on my MT3G with CM 4.2.15.1, but I got two FC's and a reboot. Linpack did go up. Touch response went down a bit. No JIT either.
[G1 Android Development] farmatito:
I'm testing it right now seems to be stable. Compiling 0x21 now ;-)
[G1 Android Development] aaraya1516:
not sure what to say, I was able to compile my first kernel today, how would I include this patch into the kernel?
[G1 Android Development] farmatito:
Attached you'll find a boot image and modules for cm 4.2.15.1 @ 633 Mhz

Overclocking: 19.2 x 33 = 633,6 (0x21)

This boots on my G1 but seems to be a bit unstable and causes segmentation

faults under heavy load (web browsing).
[G1 Android Development] farmatito:
copy patch to kernel source dir

cd kernel_source_dir

test it:

patch -p1 -E --dry-run < name_of_patch.file

apply it:

patch -p1 -E < name_of_patch.file
[G1 Android Development] xaueious:
I'll just reference it.

May I ask why there's a new modules.sqf? Typically it isn't necessarily for kernels.
[G1 Android Development] farmatito:
To be sure that the modules could be loaded as I don't know if the previous are compatible.
[G1 Android Development] xaueious:
Should be fine without modules.sqf I think, but needs confirmation.

Here's the 614MHz overclock kernel in update.zip for G1/32B on 2.X or 1.X Radio. All I did was repack the files and modified a line in build.prop for convenience.

Just flash from recovery.
[G1 Android Development] farmatito:
Attached you'll find a boot image and modules for cm 4.2.15.1 @ 652 Mhz

Overclocking: 19.2 x 34 = 652,8 (0x22)

This boots on my G1 but seems to cause some segfaults under heavy load.
[G1 Android Development] xaueious:
Does your phone crash when you plug in USB with everything enabled?

I had my phone boot to 711 MHz, but it was freezing up. Is compiling modules.sqf going to help that?
[G1 Android Development] viettho:
It booted up to home screen and then froze while loading widgets & icons.
[G1 Android Development] farmatito:
I've tried max 652,8 (0x20) so far and it works with usb plugged in

from the start as I use fastboot to test it. Can't say what plugging

and unplugging does. Will compile a few more kernels (up to 700mhz)

tomorrow if there is some interest.
[G1 Android Development] xaueious:
Try unplugging your usb. Also clear dalvik-cache.

The kernel is unstable and your widgets might be crashing the phone.

I actually did boot with my usb in. It froze after loading some stuff. It was a no wipe install though. Only cleared dalvik-cache.

I think there's some variability with our phones. I'm interested to know if modules.sqf makes a difference with stability.

If there's more interest we might get this in some roms.

For everyone new to the thread, this isn't ready for primetime, but we need would like people to try this methodically to see if this is feasible.
[G1 Android Development] sd2649:
Would re-flashing the CMupdate zip file un-do this? if not, how would I go back to stock speeds after this is flashed?
[G1 Android Development] protomanez:
Yeah it would, as you're replacing the kernel :|
[G1 Android Development] jcarrz1:
I would shove this into a ROM !IF! I didn't think it would cause long-term (or even short-term) DAMAGE to my handset. Period.

Temps anyone? a low result could TEMPt me... (pun intended :))
[G1 Android Development] damien667:
I made it myself!

So... I made a stable 614.4Mhz Kernel for the G1... and I even used it all day today... I got 4 MFlop from linpack and 7.8 sec on BenchmarkPi (you can find me on their results site as "dag, tx" here http://androidbenchmark.com/alls.php [takes a min to load]).

I did more than just add the 0x20 OC patch to it (19.2 x 32(0x20 in hex) = 614.4) , I also added 614400 to the list of available clockspeeds in all the data structs in that same file, and changed my .config to set 614400 as the max clock in the Power Management settings... this allowed for /proc/cpuinfo to show correct bogomips.

It was definitely more stable than ya'lls experience... also, I have a G1 from one of the very first batches (got it through t-mo presale)... my serial number is like 00000058 or something like that... :-p... so I might have a SoC/Mem combo that can handle those speeds....

Next I will mess with the memory speed multiplier (which according to the guys for this patch is based on the CPU clock)... to lower it back down to as close to 132.3Mhz as I can (cuz that's the normal clock if I remember right)... every time you change the clock of the CPU, the memory clock is affected too and if the memory isn't spec'ed for that speed, you get intermittent crashes like we all have been getting.

Oh yeah... on my kernel, I was able to make a call... however... in the middle of the call, dalvik crashed and I lost my UI... but since the call was already placed and it was being handled by the ARM9 radio... the call didn't drop!!!... but... the phone got SUPER hot and the battery died in like 2 minutes from 75% charge...

If anyone wants the patch I did and my .config just PM me.

edit: LOL... I guess it's not as "stable" as I started this message with... but still... I think I'm on the right track... anyone?
[G1 Android Development] infinitybiff:
after flashing it i get about 2.6 MLFOPS... i was getting 2.4 on csdi... so a bit better... can't get overclock widget to reflect me being at 614mhz tho... any idea how to verify my clock speed?
[G1 Android Development] erlern:
Oh man... just woke up to find so many things done :) Hahaha... okay, time to flash stuff and test it.
[G1 Android Development] erlern:
Would be interested if you can provide a zip for us to flash :) Sounds great!
[G1 Android Development] xaueious:
The zip is available and linked on the first post. But if you don't even know how to adb push you should not be flashing this.

You can try to enable JIT yourself if you are a keener, but I don't think JIT is stable enough to use as is, so combining JIT with this kernel will only lead to more stability issues. I think that's a waste of time unless you are trying to shoot for benchmarks.

Adding the frequency is pointless and is just a hassle, and there are no benefits at all except for the kernel reporting that it is now running at a higher frequency.

We need people to focus on stability so the community can use it.

I'm not sure about changing the memory line. I think it is running at stock levels even with the patch. I'm not actually sure. Ask the patch creators.
[G1 Android Development] erlern:
Okay, I flashed the zip file and here are my results. I am using JIT (just applied yesterday). Basically this concurs with damien667's performance above.

Benchmark Pi

Before OC Average: 9370ms

After OC Average: 7900ms

Basically a 15.6% which is as expected (within the range)

Linpack MFLOPS

Before OC Average: 3.30

After OC Average: 3.9 (from a low of 3.3 to 4.2)

A bit off since it is 18.2% (but not by much from what is expected)

Initial Findings:

I think it is quite conclusive that it is doing something. Browsing the Net has definitely improved... loading pages are faster (significantly), especially on intensive sites like Engadget and Planetandroid.

But it seems erratic. Swiping between the home screens proved no difference, and has occasional stutters at the start. When I press "call" button, the call log comes out exactly 1 second. In the past, it takes 1-2 seconds to load. Scrolling through the launcher is now not that smooth as before. Scrolling with only JIT was super smooth, now it stutters a bit.

Using yxflash proved interesting. Even when using JIT, there would be at least 1 slight pause/jerkiness every 2 minutes. Now, having played the same video file (xvid), it was surprisingly smooth with no pause/jerkiness for 3 minutes!

Overall I am happy with the performance, but as noted, it seems better for performance intensive usage, but not for the small mundane operations (based on my usage). No crashes (yet). Will update this if there is any.

Btw, no issues with the USB cable. Worked perfectly. Any other tests, please let me know. :)

Updates:

- Added percentage increases

- Found that multitouch experience in browser is quite disappointing. It is not as responsive as before. It takes multiple touches of pinching to get into the text.
[G1 Android Development] damien667:
I looked at their patch, they don't change the memory line... which means you're overclocking the memory too and why there is instability... I know what I'm doing dude.

And your ASSERTION that not reporting the correct speed in the kernel does not affect anything is highly questionable. Unless you know the linux kernel 2.6.29 intimately that runs on our MSM7k G1's, I wouldn't ASSERT, I would ASK.

However, changing the memory line didn't really help... there's other math somewhere that has to be done.. and I don't know MSM7k well enough to know where to look.

It's up to someone else to find out how to stabilize this issue.
[G1 Android Development] damien667:
It comes with the warning that my phone seriously got REALLY hot!!! I'm not responsible for it killing your phone and you having to get a new one... if that's ok with you, I'll send you a boot.img (compiled from current code from cyanogen's 2.6.29 donut kernel git and the .config taken from my phone running 4.2.15.1).

Like I said, i think the memory is overclocked too... and it will cause intermittent crashes.
[G1 Android Development] xaueious:
I'm not a dev. Anything I say regarding source code is never an assertion and more like a guess :p

I'm leaving this thread as it is until someone bothers to figure out the details.

My instability issues could have had different causes.
[G1 Android Development] erlern:
Okay, maybe not... since I only have one HTC Dream! But yeah, let's hope one of the devs would come in and polish it once for all :) But am seriously glad that in many areas, the OC actually is quite good :)
[G1 Android Development] erlern:
Have you tried the higher frequencies that farmatito posted? :)
[G1 Android Development] damien667:
Here's my patch

Attached is the diff against cyanogen's git located here:

git://github.com/cyanogen/cm-kernel.git

on branch:

remotes/origin/android-2.6.29-donut

# On branch remotes/origin/android-2.6.29-donut

# Changed but not updated:

# (use "git add <file>..." to update what will be committed)

# (use "git checkout -- <file>..." to discard changes in working directory)

#

#	modified: arch/arm/mach-msm/acpuclock.c

#

rebuild instructions from section "Prepare Kernel From Source" ONLY:

http://wiki.cyanogenmod.com/index.php/Building_from_source#Prepare_Kernel_From_Source

This assumes you know how to do all this and that you have the Android source and SDK and toolchains and cross compilers... if you don't know what any of that is, then this is not for you :p
[G1 Android Development] damien667:
Here's all I know

I did... 614.4 was the highest I could go and actually boot into Android...

I tried all hex values from 0x25 to 0x20 in the patch.

0x25 = 37 in decimal... and in the math for the multiplier you do 19.2Mhz(the clock source) x multiplier (37) = 710.4Mhz

0x24 = 36 = 691.2

0x23 = 35 = 672

0x22 = 34 = 652.8

0x21 = 33 = 633.6

0x20 = 32 = 614.4

According to the people that did the patch... the memory clock is = CPU clock/(divider+1)

at 528.8(normal clock) the memory should be at 132.2 (in the code, the memory divider is set to 3)...

yes, I've tried increasing the divider number... to no avail... I think it needs more logic and math than this crazy hack to edit the memory register directly...
[G1 Android Development] erlern:
Thanks! I really appreciate your work and am reaping the fruit of it :)

- Playing National Geographic (704*384 reso) with no stuttering :) Yeah!
[G1 Android Development] lefeudedieu:
hello

I put the file in my wlan.ko SuperEclair 2.1 and I lose the wifi, can not enable someone would help me?

Thank you :)
[G1 Android Development] sd2649:
having success

I have cyanogens latest and flashed the update.zip on the first page. I verified the OC through a 2.6 mflop (vs old 2.2). I have no stability issues so far at 614mhz. I have been running it since yesterday around 4 and I have seen noticible increases in speed. Thankyou so much for this! I will report back in a few to talk about battery life, but I have an extended battery, so I am not too concerned. GREAT JOB!!!
[G1 Android Development] infinitybiff:
I'd be quite interested to see what would happen if you put this in a hero rom... however I have NO idea how to go about doing that.
[G1 Android Development] Jefmeister:
Been running almost 2 full days now with 614mhz kernel + 10mb hack + JIT enabled + Linuxswap and no CC on cyanogen 4.2.15.1. Only 1 reboot and no complaints otherwise.

Getting over 4 MFlops now so im a happy man :D
[G1 Android Development] ivanmmj:
Mind making nandroid and uploading the system.img and boot.img somewhere?

I want to try it out. (Assuming you don't have a Roger's Dream.)
[G1 Android Development] smuvman:
superd

tried the zip on the new superd and got stuck at bootscreen. guess ill wait some more.
[G1 Android Development] macacomachec:
Runs Great on Cyanogen's!!!!

By the way how do you enabled Jit,i tried the update.

zip method but i can't pass vodafone bootscreen
[G1 Android Development] Daneshm90:
Hey guys, im very interested to try it out. Heres my boot.img im running amonra's 32a 1.6 ion rom. Is it possible for someone to make a compatible boot.img for me to try this ? it would be appreciated thanks
[G1 Android Development] zerocoolriddler:
Great Work!

Hello everybody.

Tried the EBI0-Flash(update.zip) and it works great on Super D 1.10.3!

Without JIT 2,6MFlops on Linpack. Original 2,2MFlops.

With enabled JIT i´m getting about 4,1MFlops on Linpack. Before 3,6MFlops.

I´ll test for another couple of Days to see how about Stability and Batterylife.

Really great work.:)
[G1 Android Development] erlern:
I think it is conclusive that it does work. The only problem is in its stability. Like I mentioned before, it is not all smooth. I am not sure how the load is handled under this new clock speed. Does it scale up as and when needed? On mundane things, there has been some stuttering (homescreen swiping). Occasionally, when you multitask a bit too many apps, it reboots. I am not sure how much of this is the fault of the new clock speed and how much the fault of JIT.

We really need someone to clean and polish the kernel patch :) That's IMO.
[G1 Android Development] gadget421:
running fasttest 2.9 with ramhack and jit and 614. getting 4.1 mflops. internet speed is improves, a little slow going back to home screen. battery is lasting a little shorter. one time it reboot itself. mytouch32b
[G1 Android Development] Jedipottsy:
how did you apply this to fasttest? How can i add this to SuperD 1.10.3?