yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] XxKOLOHExX:
I tried flashing this on top of a rom and it locks up, :( While it's booting it won't get past the Mytouch logo
[G1 Android Development] pershoot:
is that the 2708 32b kernel?
[G1 Android Development] roalex:
245-610 /on demand
[G1 Android Development] vermaekansh:
Currently I am on Official AOSP 2.2 test 3 with ezterry's kernel EBI0 (32b) port for 2.22.* radio users and i am afraid to use the above kernel as i am still on 23.02 radio and danger SPL
[G1 Android Development] roalex:
Its only one kernel for the new radio/spl there, the other 2 are for the normal radio, 32b/32a
[G1 Android Development] XxKOLOHExX:
Yeah it is
[G1 Android Development] vermaekansh:
you are tlking about pershoot's kernel or ezterry kernel....
[G1 Android Development] roalex:
Pershoot kernel
[G1 Android Development] vermaekansh:
do u have the link for other 2 for 23.02 radio and danger SPL...
[G1 Android Development] pershoot:
Ill look at the merge.
[G1 Android Development] roalex:
Is it enabled ? I wonder coz the way it worked for me was AFTER flashing the 262 config from terry then your kernel.

This is what ppl state over to CM forums:

hope this made some kind of sense
[G1 Android Development] roalex:
32b

32a

http://droidbasement.com/db-blog/
[G1 Android Development] vermaekansh:
thanks but the baove link is the same from the pershoot for 35.9 kernel m having G1 with test 3 AOSP 2.2 OTA :)
[G1 Android Development] pershoot:
Roalex:

It is enabled in _radio2708 kernel.

Something may have went amiss in the sapphire merge.

Can anyone else confirm that has a mt3g with new radio/spl and the radio2708 kernel causes a no boot?
[G1 Android Development] G1ForFun:
Thank you pershoot. The latest kernel is running beautifully on my G1 on The Official 2.2 AOSP MyTouch 3g release. I noticed a speed boost from the default EZterry kernel and battery life seems good so far.
[G1 Android Development] AndDiSa:
I noticed a strange behavior: I flashed the latest CM nightly and on top directly the pershoot 2.6.35.9 kernel ... it was stuck on the G1 screen. I flashed ezterrys kernel for the 2708 rom and booted without problems. I reflashed the 2.6.35.9 kernel and it booted :confused:

First I thought, it was a bad flash, but I repeated it three times and always the same behaviour. First boot with 2.6.35.9 kernel failed, once booted with a different kernel, the 2.6.36.9 kernel runns smoothly. Somebody has an idea what's going on?
[G1 Android Development] pershoot:
i think anykernel isn't finding the base PHYS_OFFSET properly in this specific case.

ezterry, can you please comment on this?
[G1 Android Development] xaueious:
Anykernel looks for the offset in the existing boot.img

If you flash the boot.img of CM6 stock first, you get the EBI0 offset. 2708 has a different offset and needs to be hardcoded in.
[G1 Android Development] ezterry:
Hrm I always force the --base option on mkbootimg for all my kernels. Since the base is hardcoded in the kernel as well..

The 2708 needs to be at 0x02000000
[G1 Android Development] pershoot:
Thx. Ill force base to 0x2... and refresh the zippies tonight.
[G1 Android Development] sparksco:
Pershoot, I made your newest kernel for DS work on the new radio and spl, here is the updater script. Basicly I just used Ezterry's newest method. Everything is working fine, and my kernel version reads 2.6.35.9-cyanogenmod+root@pershoot-ubuntu #1:

ui_print("Welcome to SparksMod-1.4-1.4.1 No Wipe Update!");
show_progress(1, 15);
package_extract_file("nfo.prop","/tmp/update_nfo.prop");

ui_print(file_getprop("/tmp/update_nfo.prop","nfo.build.title"));
ui_print(file_getprop("/tmp/update_nfo.prop","nfo.build.desc"));
ui_print(file_getprop("/tmp/update_nfo.prop","nfo.build.for"));

mount("MTD", "system", "/system");

assert(getprop("ro.product.device") == "trout" || getprop("ro.build.product") == "trout" || getprop("ro.product.board") == "trout" ||
getprop("ro.product.device") == "sapphire" || getprop("ro.build.product") == "sapphire" || getprop("ro.product.board") == "sapphire");

package_extract_dir("system", "/system");
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));

ui_print("Install Scripts");
package_extract_dir("work","/tmp/work");
set_perm(0,0, 0777, "/tmp/work/delete_files.sh");
set_perm(0,0, 0777, "/tmp/work/install.sh");
set_perm(0,0, 0777, "/tmp/work/mkbootimg");
set_perm(0,0, 0777, "/tmp/work/unpackbootimg");

ui_print("Delete old files");
run_program("/tmp/work/delete_files.sh");

ui_print("Update Kernel");
run_program("/tmp/work/install.sh");

ui_print("Install kernel modules");
package_extract_dir("mod","/system/lib/modules");
unmount("/system");

mount("MTD", "userdata", "/sd-ext");
package_extract_dir("sd-ext","/sd-ext");
ui_print("Installation complete!");
unmount("/sd-ext");
[G1 Android Development] sparksco:
That's why mine works I guess, because I used your method to install it :D
[G1 Android Development] ezterry:
The official koush anykernel and my variant of it (having been designed off of koush's.. and prob the same binaries tho I got them from customMTD) have the same idea:

1) dump current kernel from boot

2) dump the boot image into its parts (kernel, ramdisk, and the two metadata bits, command line, and base address)

3) rebuild with mkbootimg using the new kernel (zImage) with the pre-existing ramdisk and commandline.

4) replace modules,

in the case of myscript i also verify the correct audio profile is installed (but the audio hack in cm ought to be able to do that.. its mostly a legacy of the older ebi1 ports)
[G1 Android Development] sparksco:
I used pershoot binaries, and just renamed zimage to 2708-zimage, and there was one other binary of pershoots that I had to remove, but cant really remember which one now lol. Either way it works great, thank you both :D
[G1 Android Development] havikx:
is there a pershoot 710oc kernal available for my g1's set up? and i can just flash it through recovery while keeping the 14mb ram increase?
[G1 Android Development] Phateless:
I can volunteer for this tonight. Can you link me to the kernel in question so I make sure I flash the right one?
[G1 Android Development] sparksco:
Google Droid basement and select the right one for your phone, radio and spl
[G1 Android Development] havikx:
what is your oc to?
[G1 Android Development] pershoot:
done for 2708 kernel .zip and uploaded (same filename).
[G1 Android Development] MentalDeath:
Are there any 710MHz oc EBI1 kernels?

I tried the 32A kernels but they don't boot up just hang on splash screen and reboot....
[G1 Android Development] pershoot:
nexus/ds/g2 - 2.6.35.9 (nexus/ds); 2.6.32.26 (g2) - http://droidbasement.com/db-blog ; RM updated
[G1 Android Development] vermaekansh:
So finally i flashed this kernel onto my G1 with Official 2.2 test3...hope everything goes well..

good work pershoot
[G1 Android Development] billquinn1:
In your instructions it says:

Is the 28.25 radio also supported? I pre-apologize if already asked and answered.
[G1 Android Development] G1ForFun:
Yes.

(10 char min)
[G1 Android Development] havikx:
I can flash this kernal for my radio and spl on my g1 and get 710 overclock?

edit: i flashed this kernel and it booted just fine but i am still on 614 overclock. i am confused. i thought this was a 710oc kernel.
[G1 Android Development] vermaekansh:
a little bit of badluck for me....with this kernel...though it booted fine and preety fast...

but the problem i faced with the kernel is i got lot of soft reboot what i mean saying this is - once i was downloading a song from opera and it got hanged adn a black screen fone is ON but still m not able to get into it...no display and ringtone while getting a call...for this i had to remove my battery...

i already reported this issue before with one of the kernel..
[G1 Android Development] pershoot:
Pls post logs.
[G1 Android Development] vermaekansh:
those reboots are random...so donnowhen it is going to heppen next sory...i can live with that...and also the battery backup is good..
[G1 Android Development] pershoot:
Post a last_kmsg next time it happens (in /proc)
[G1 Android Development] sparksco:
I haven't had one single soft reboot yet
[G1 Android Development] vermaekansh:
that may be because you are on the new radio/spl combo....i am still on 23.02 and death SPL.
[G1 Android Development] sparksco:
Oh yeah then it won't work, but it's definitely worth the upgrade for 15mb extra ram.
[G1 Android Development] vermaekansh:
any process to check if i am getting extra 15MB ram....
[G1 Android Development] sparksco:
Yes when you have the new hboot you will already have the extra ram
[G1 Android Development] tnpapadakos:
terminal emulator

#free
[G1 Android Development] havikx:
this kernel isnt a 710mhz oc kernel?
[G1 Android Development] Phateless:
I thought the ram came from the new radio and not from the hboot?
[G1 Android Development] sparksco:
You have to have the hboot and radio both, so who cares?
[G1 Android Development] Phateless:
Wasn't it a specific kernel in question or have we all moved on from this? Was just offering to duplicate dude's setup to test to see if it boots.
[G1 Android Development] Phateless:
And what rom am I flashing this over?
[G1 Android Development] sparksco:
Yes, the one that says DS, radio/spl combo
[G1 Android Development] sparksco:
Here's the direct link: http://droidbasement.com/g1/kernels...ds_32b_radio2708-oc-uv-xtra-ram-fp-120110.zip

Basically just use any of the newer cm6 nightlies
[G1 Android Development] vermaekansh:
this is good..and easy

total used free shared buffers

Mem: 98440 95904 2536 0 196

Swap: 0 0 0

Total: 98440 95904 2536 0 196

this is wot i am seeing right Now...
[G1 Android Development] Pfeffernuss:
So it didn't work ;)
[G1 Android Development] vermaekansh:
yeah thats wot i am thinking ...

i need to upgrade it to new radio/spl combo... ;)
[G1 Android Development] dnaroid:
Please make radio2708 patch for Kernel 2.6.33.3 . Thanks.
[G1 Android Development] Phateless:
Ok, I'll get to this in the next day or so. Right now I'm on oem froyo, I assume that wouldn't be close enough for testing purposes?
[G1 Android Development] havikx:
is dumfuqs 710 oc 2708enabled?
[G1 Android Development] Jeffrey.Dahmer:
Is there any mt3g 32b kernels for the latest cyanogen mod nightlies that oc to more than 614?
[G1 Android Development] sparksco:
I'm not really sure buddy, I would assume that it works better on cm6 nighlies or rc1 rom by cyanogenmod. I think pershoot is working with cyanogenmod with his github but maybe I'm wrong
[G1 Android Development] theophile2:
Just flashed it and the answer is no. ;-)
[G1 Android Development] anomalous3:
Issue appears to be fixed!
[G1 Android Development] joseangel.alv:
compcache problem

Hi pershoot

I can't enable compcache with your last (Jun.16, 2010) kernel version (the DS extra one).

I'm commonly using a script to enable it, but the straight cyanogen compcache from spareparts also doesn't work.

I suppose it's something about the "revert update Compcache to 0.62", but I'm not sure how to help you (logcat? kmsg?) to trace it...

Where is the right way/place to send you this info? comments in your blog? here?

This is what I've tried so far...

# find /system/lib/modules/`uname -r` -name ramzswap.ko
/system/lib/modules/2.6.34-cyanogenmod/kernel/drivers/staging/ramzswap/ramzswap.ko

# busybox insmod /system/lib/modules/2.6.34-cyanogenmod/kernel/drivers/staging/ramzswap/ramzswap.ko
insmod: can't insert '/system/lib/modules/2.6.34-cyanogenmod/kernel/drivers/staging/ramzswap/ramzswap.ko': File exists

# busybox swapoff /dev/block/ramzswap0
swapoff: /dev/block/ramzswap0: Invalid argument

# rzscontrol /dev/block/ramzswap0 --reset
reset: Not a typewriter

# rzscontrol /dev/block/ramzswap0 --disksize_kb=12288 --init
init: Not a typewriter

# busybox swapon /dev/block/ramzswap0
swapon: /dev/block/ramzswap0: Invalid argument

A lot of months ago and with other ROM, I've had an issue like this... if I remember it right, it was a problem related to the rzscontrol version that I had installed... but I found this odd, because it was working with all your other kernel versions.

Thank you :)

EDIT:

This is from my last kmsg...

[ 10.387756] ramzswap: module is from the staging directory, the quality is unknown, you have been warned.
[ 10.396911] ramzswap: num_devices not specified. Using default: 1
[ 10.397338] ramzswap: Creating 1 devices ...
[ 10.441497] ramzswap: Disk size set to 12288 kB
[ 10.441925] ramzswap: Invalid ioctl 31236
[ 10.453216] Unable to find swap-space signature
[G1 Android Development] russbvta:
Effect of a kernel on battery life?

Im just wondering how great an impact on battery life kernels make.
[G1 Android Development] pershoot:
ill bundle rzscontrol in the blog post. ill look further in to it tonight..
[G1 Android Development] defconoi:
@pershoot

ever since I flashed your new DS kernel my alarm refused to go off this morning, nothing else changed but your kernel from stock, it was virbrating, just not ringing, even previewing the sound didnt work, had to reboot then it worked
[G1 Android Development] pershoot:
nothing in the kernel would have caused sound to stop working (from what i can see). reflash clean (clear dalvik, flash rom + kern update + gapps. no other addons), and observe. normalized sleeper should be helping things related to sound/music until the framework is updated.

this phantom issue has been around for some time (even for some nexus users). has never happened to me though.
[G1 Android Development] defconoi:
btw I was noticing that the non-xtra kernel of yours seems to be a lil more responsive than xtra
[G1 Android Development] pershoot:
Cool.

One may work better 4 u then the other. I personally prefer xtra.
[G1 Android Development] pershoot:
Ds kernel images refreshed - http://droidbasement.com/db-blog/?p=578
[G1 Android Development] pershoot:
is CC working out ok now?
[G1 Android Development] bkmo:
Yeah, looks to me like it is. I am just running stock Cyanogen from spareparts.
[G1 Android Development] joseangel.alv:
Hi pershoot

Problems in real life... I couldn't post until now...

Yes, compcache is running correctly (cyanogen spareparts one and also the customized script one).

Thank you very much, and sorry for the delay in this reply :o
[G1 Android Development] pershoot:
DS kernel update.zip refreshed - http://droidbasement.com/db-blog/?p=578 - pls read the whole post.
[G1 Android Development] tnpapadakos:
im using dumfuq's oc825 5.0.8 test 4 kernel on 5.0.8 ds final...seems to be working fine
[G1 Android Development] dumfuq:
updated for 5.0.8-final

Dream/Sapphire(32B)

oc825-cm-2.6.34-8final-signed.zip

oc825-cm-2.6.34-8final-boot.img

32A

oc825-32A-2.6.34-8final-signed.zip
[G1 Android Development] pershoot:
DS kernel blog post updated to be clearer - http://droidbasement.com/db-blog/?p=578
[G1 Android Development] tnpapadakos:
thank you, dumfuq
[G1 Android Development] pershoot:
performance seems on par using the latest DS kernel with 508 final.
[G1 Android Development] mark manning:
how should i set; setcpu?

edit:

never mind, figured it out
[G1 Android Development] anomalous3:
hey dumfuq, is there any way to adjust NORMALISED SLEEPER on your kernel? I'm getting music popping, and when I mount the debugfs there's no sched_features.
[G1 Android Development] pershoot:
nexus/ds (2.6.35.9); g2 (2.6.32.26) - http://droidbasement.com/db-blog ; RM updated
[G1 Android Development] sparksco:
Thanks, will try this out :D
[G1 Android Development] havikx:
is there a 710oc working with the new radio/spl combo?
[G1 Android Development] sparksco:
No you don't need it, it's fast enough @614mhz :confused:
[G1 Android Development] ezterry:
The ones building kernels feel it not worth the problems caused by pushing the hardware so fast, thus don't feel like building it.. or if they don't mind building it have been busy with other more tangible android hacks.

The ones asking for faster OC apparently don't know how to build a kernel themselves. 'Cause if you did you just need to add a few lines of code back into arch/arm/mach-msm/acpuclock-arm11.c and build it..

Actually the current CM kernel you just need to enable CONFIG_JESUS_PHONE for speeds up to 710400
[G1 Android Development] sparksco:
Well said buddy
[G1 Android Development] :
Just wondering if the kernel devs might be into trying to improve on the work of carz12 and Feeyo (see links below) to get a fully functioning 2.6.35 kernel for the 32a Magic/Sapphire on the new radio 6.35.16.19 radio that gets regular updates like your other kernels.

The 32a Magic/Sapphire community would be super grateful for the support.

We're struggling without a decent kernel for the new radio.

:(:(:(

http://xdaforums.com/showthread.php?t=692735

https://github.com/Feeyo/cm-kernel-32A-Magic
[G1 Android Development] sparksco:
I haven't had any problems with this kernel at all, but I'm not exactly using the exact same extractor method, other than that it works fine

Edit: Stand by and I'll get you just kernel I'm using...
[G1 Android Development] :
But it looks like you're on a different radio.
[G1 Android Development] Phateless:
When my mt3g was my daily driver I would have been scared to try even 614, but now that I have I've found it perfectly stable for daily use. I would like to give 710 a try. I know that most devices probably won't be stable at that speed, but isn't it possible that some might?
[G1 Android Development] sparksco:
Why are you on a different radio? Talk to crivillani, he has 32A and has already has this kernel working...
[G1 Android Development] :
I believe the hardware is different and the 6.35 radio is the latest version that was recently included in Roger's 2.1 update for the 32a Magic/Sapphire.
[G1 Android Development] sparksco:
Oh I see, well contact crisvillani, he has a 32A port for rom and kernel.
[G1 Android Development] PhilMax:
Which kernel will be the fastest for 32B dream using the 1.33.00.13d spl?

should I use pershoots normal or extra or just stick with ezterrys? I often switch between CM6.1 nightlys and Biffmod 2.1

Thanks :)
[G1 Android Development] roalex:
The performance its better, but i did notice something kinda weird, the battery temp kind of sky rocked, 245-528 with over 40C battery temp / on demand scale gov.
[G1 Android Development] jacobmathias:
mirror

if you'd like to mirror these on a actual server, e-mail me burness.mathias@gmail.com
[G1 Android Development] sparksco:
I second that, I've had this issue as well. For the most part the battery temp stays cooler than other kernels I've used, kinda weird how it does that sometimes.
[G1 Android Development] alexanderlll:
My HTC Magic (32a board) works perfectly at 710 - a lot of games have become playable. It's worth trying - it really gives the phone a new life (or kills it :)).

But the latest 710 OC kernel doesn't work with CM 6.1, so if anyone can excuse my ignorance and tell me how to enable CONFIG_JESUS_PHONE (I searched on Google, found nothing), I'd be very grateful :).
[G1 Android Development] lolmensch:
CONFIG_JESUS_PHONE sound like making fun of sb :P anyway i second that to make users available to overclock to nirvana ^^
[G1 Android Development] pl_laszlo:
you need to compile cm-kernel for d/s with this option enabled. you'll be able to oc to 700 MHz with jesus_phone.

make menuconfig, you will find this option there.

However.. It's unstable and big batery drain.
[G1 Android Development] rps13:
I find it to be unstable even above 614 so IDK
[G1 Android Development] Phateless:
Mine is perfectly stable AT 614, although battery life isn't great. Does anyone have a 2708/28.25 compatible 710 kernel yet?
[G1 Android Development] pershoot:
nexus/ds - 2.6.35.9 - http://droidbasement.com/db-blog ; RM updated
[G1 Android Development] sparksco:
Nice. I know this is the g1 development, but I'm about to install your g2 kernel on a friends phone, and I'll probably have a G2 for myself by the end of the week. He was telling me that we have to install the .ko file manually, just wondering why that is?
[G1 Android Development] xaueious:
For some reason, using 710MHz on Android 1.5 on my 32A with that stock kernel and the modified cpuclock was easy. But with newer versions, cm-kernel in particular, I couldn't achieve the same stability with 710MHz. In fact, I couldn't push it past 633 MHz.

Isn't it recommend to use a .34 series to avoid battery drain though? ezterry's 1106 biff kernel works fine right now on the 32A. I haven't tried it on the 2708 G1, but will give it a shot sometime tomorrow.
[G1 Android Development] rps13:
On the 2.6.34 Cyanogenmod kernel 653 MHz is stable on 32As but 2.6.35 is pretty useless for us
[G1 Android Development] pershoot:
nexus/ds/g2 - 2.6.35.9/2.6.32.26 - http://droidbasement.com/db-blog ; RM updated
[G1 Android Development] pershoot:
nexus/ds/g2 - 2.6.35.9/2.6.32.27 - http://droidbasement.com/db-blog ; RM updated.
[G1 Android Development] sparksco:
Thank you for your awsome kernels, working great on cm6.1.0-DS
[G1 Android Development] pershoot:
nexus/ds/g2 - 2.6.35.10/2.6.32.27 - http://droidbasement.com/db-blog ; RM updated.
[G1 Android Development] Killadude:
Dear Pershoot,

If you dont mind could you please explain at what frequencies how much power the processor uses that would be great. I mean till what frequency is it under-volt and at what frequency do you over-volt it so that it overclocks?

Thanks!
[G1 Android Development] sparksco:
This kernel overclocks really nice and easy, but won't drain the battery unless your using it a lot. I keep mine set with SetCpu and and keep the max @614mhz, and min @245. Set profile to on demand gov. Plus I'm using swap ;)
[G1 Android Development] sparksco:
I was wondering what github repository I connect to for the new radio/spl combo? Or is there one? I see a lot of different ones for DS but not sure which one
[G1 Android Development] Rugga:
I'd like to know too.
[G1 Android Development] ezterry:
Just a FYI of a new build of the CM6.1/CM7 kernel:

http://forum.cyanogenmod.com/topic/...tlies/page__pid__117678__st__5660#entry117678

Includes anykernels for ebi0/ebi1/2708+
[G1 Android Development] sparksco:
Hey thanks a lot!

Edit: Seems this still causes the CM Green tint kernel. Any reason as to why biffmod kernel and pershoot's kernels don't cause the green tint? If we could figure that out then would would be golden. BTW works great on my G1:D
[G1 Android Development] juangil:
thank you, will test on your AOSP 2.2
[G1 Android Development] pershoot:
hey all.

i haven't forgotten about you!

i am working on an update (it would be for froyo).
[G1 Android Development] ezterry:
My previous "biff testing" kernels are 2.6.34.7 based .. cm has been on the 2.6.35.* tree for a while.

I've been trying to make a stable update to the bifftesting kernel to include some of the APIs for gingerbread and battery enhancements without some of the problems we have been having but the resulting merges have not exactly been stable.. I keep running into one or two patches that spider the codebase and seem to change many different things.. but define some API changes so its hard to avoid.

The actual problem to the CM kernel happened between the 2.6.35.7 to 2.6.35.8 upgrade (and stayed with us for .9 and apparently .10)

As I've stated on the cm-nightly forum this seems related to the nt35399 display and not the toshiba one.. but I really do not see any change in the panel code during the kernel version upgrade. My best guess is some property is undefined; that previously wasn't important.. but either in the new kernel version or one of the newly supported devices has become important.

What we need is some dev with the green screen issue to do some analysis I'm running blind as my Dreams have no issue and the one Magic32A currently at my apartment has the toshiba display.

(Edit.. commit 2eaad42be995bde039692415722be1d023d83e59 I think needs an audit)

Curious, besides the usb_mass_storage change, do you know anything in or required by gingerbread than breaks froyo.

To All: Cyanogen removed the backwards compatibility logic for the mass_storage from the most recent so it worked fine on my GB port but failed on CM6.1 until I re-added it. The experimental build I posted re-added the compatibility logic so it would work on today's froyo roms..