yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] Izord:
Frozen first bootscreen

This kernel worked great on test6, but I have flashed it twice on test7 on a MT3G and both times it broke my phone. I am frozen at the first green boot-screen.

I had to take the battery out a few times to get back into recovery.

I think some changes are needed for test 7
[G1 Android Development] samsci:
I had same issue. Tried twice and on reboots locked up both times. Going to reinstall the rom with the Kernel already built into it to see if that works. Had no issues on Test 6 at all.
[G1 Android Development] samsci:
Interesting. Installing it this way and it is working fine. I was able to adjust it to 691mhz and Test7 is running smooth as silk now. No issues at all. When I installed separately I could not get the kernel to work and rebooting would lock the phone up.
[G1 Android Development] dumfuq:
sry. no changes in the kernel itself but of course in the ramdisk there was ;)

oc825-cm-5.0.7-test7-boot.img
[G1 Android Development] ceas909:
sure thing... reflashed boot.img xtra over cm test7 with same results (stuck at mt3g boot screen)

attached logcat and last_kmsg in a zip
[G1 Android Development] tnpapadakos:
thanx dumfuq
[G1 Android Development] jriv:
that update zip wouldn't flash for me kept saying bad
[G1 Android Development] tnpapadakos:
i know, sorry, try this

(cm 5.0.7 test7 with dumfuq's oc825boot)
[G1 Android Development] Izord:
I tried this one over Test7 with same results dumfuq. Stuck at first greet boot-screen.
[G1 Android Development] Izord:
I tried Pershoot's latest Kernel 2.6.34 – OC-UV-FP – Dream/Sapphire (32B/A)

on top of test 7 and it locked my MT3G at the first boot screen. I am just not having luck with OC kernels on this Test.
[G1 Android Development] Nyr:
I had just flashed oc825-cm-5.0.7-test7-boot.img and have no way to initialize Wi-Fi, not even at 576 MHz ¿is this espected with this kernel, or there is a problem?
[G1 Android Development] roccodaone:
I had the same problem. Reflashed and it works just fine.

Oh, and WIFI works for me as well.
[G1 Android Development] Izord:
Thank you sir.

This one works. No problems noted.
[G1 Android Development] Nyr:
Just flashed the complete update_signed.zip (not only the boot image) and it works like hell, at 614 with Wi-Fi included :)
[G1 Android Development] pershoot:
yes there is an issue with sapphire. i am investigating.
[G1 Android Development] erlern:
Guys, does anyone have any answer for this?

I find that running emulators (Gameboid/SNES) using OC (614Mhz) on CM 4.2.15.1 to be the fastest.

When I run the same games using OC (same frequency) on CM 5.0.7 (all derivative tests), I encounter slower frame rates and lots of stuttering.

What is the problem? I thought Eclair was much better than Donut? I am not using JIT and Ramhack for either cases, so my suspicion is that on the platform itself. Does anyone encounter the same thing? Thanks. Have been very very curious about this discrepancy.
[G1 Android Development] pershoot:
sapphire 32b issue fixed. posting an update shortly.
[G1 Android Development] rynosaur:
Are you using Compcache? IMO, compcache+OC'd kernels = stuttering, delays, etc. Try no compcache with and without linux swap and I think you'll be pleased.
[G1 Android Development] pershoot:
new dream/sapphire (32b/a) kernel images posted: http://droidbasement.com/db-blog/?p=436
[G1 Android Development] ID#:
thanks for your work!

What does xtra mean?

Why don't you enable frequencies higher than 576?

Go for it :)
[G1 Android Development] Sik-1:
still wont boot, stuck on g1 screen for ova a half-hour now, back .33.4 for me
[G1 Android Development] ceas909:
Re: ToAsTcfh Overclock Kernel Patch :: Downloadable Kernels For G1/32B/32A

Thanks worked great for me

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

Sent via the XDA Tapatalk App
[G1 Android Development] pershoot:
which device do you have?

clear cache/dalvik, flash rom + kernel update + gapps, then reboot. no other addons (no JIT, etc.).

make sure you are using the right file for flashing.

pls post full logs (logcat,dmesg,last_kmsg).

thx.
[G1 Android Development] erlern:
I am not using Compcache and yes, the stuttering, delays ... although slight, is evident when compared with 4.2.15.1. I am just as confused why this happens.
[G1 Android Development] rynosaur:
It seems inherent to Dubfuq's hack/overclock kernel and strangely enough, seems to get worse as the clock speed is raised. I think it's the processor/GPU waiting for the memory to catch up, but that's just a guess.
[G1 Android Development] dumfuq:
updated for 5.0.7-ds-final

Once again, this WILL NOT BOOT.

oc825-cm-5.0.7-ds-boot.img
[G1 Android Development] :
I have the same problems with NESoid. OCed to 578, no compcache, no swap, nothing else running - terrible framerates.
[G1 Android Development] tnpapadakos:
cm5.0.7DS final with oc825 by dumfuq and 3D Gallery update.zip

just flash from recovery
[G1 Android Development] erlern:
Thank you! I thought I was the only one. It is really very sad and I hope that Froyo actually will help in this area because I sometimes miss the awesomeness of gaming on 4.2.15.1 :(
[G1 Android Development] Pfeffernuss:
Hmmm, sounded intriguing and so had to try it. Ofcourse, it boots just fine ;)
[G1 Android Development] animefans:
Which app is this?
[G1 Android Development] Pfeffernuss:
That would be SystemPanel, one of the best Android apps ever IMHO :D
[G1 Android Development] animefans:
Thanks!

I will check it out
[G1 Android Development] titsmaster:
Can someone make a flashable version of this ?

(or must I boot it through adb ?)

I've already flashed CM and already have 3D Gallery pushed so I don't want to install the other .zip
[G1 Android Development] rynosaur:
Mit einem Namen wie "Pfeffernuss", habe ich dir glauben!

So is this oc825~.img what's containted in InfinityBiff's UniversalOverclockerv2.01.zip? I like how flashing the images accelerates recovery and booting, but unfortunately it seems to torpedo Sense ROMs with the ol' freeze between boot anim and lock screen :(
[G1 Android Development] samsci:
Works great. Running at 710mhz and it is running flawlessly!
[G1 Android Development] fastludeh22:
as cm's final says includes pershoots cpu clock tweaks, im wondering which on.is it normal kernal? if so im going to flash his xtra over this...
[G1 Android Development] pershoot:
new dream/sapphire (32b/a) kernel images posted (kernel 2.6.34) - http://droidbasement.com/db-blog/?p=457
[G1 Android Development] pershoot:
please let me know of any issues.
[G1 Android Development] Izord:
Hi Pershoot, is this kernel newer than the one in the final release of CM5? I read the changes you listed on Droidbasement, Would you recommend flashing this over CM5 final? Would I see some improvements if I did?

Thank you.
[G1 Android Development] pershoot:
Re: ToAsTcfh Overclock Kernel Patch :: Downloadable Kernels For G1/32B/32A

Any Sapphire 32b users having issues? Pls post full logs if u get a boot loop.

Thx.
[G1 Android Development] devkon:
pershoot you are a kernel fetish!

what are the first impression of this new kernel?? stability?

thanks pershoot
[G1 Android Development] pershoot:
you would have to judge for yourself in your own environment.
[G1 Android Development] pershoot:
this is .34. CM ships with 33.4
[G1 Android Development] rynosaur:
Wow, that's a surprising PC answer, Pershoot ;)

What are the chances of a new JIT build for 2.6.34?
[G1 Android Development] pershoot:
JIT is not so stable, but ill build it against latest CM source when i get a chance this week.
[G1 Android Development] rynosaur:
Thank you. Anyhow, I don't understand the stability "hawks" round here. If I wanted stable, I'd be running OTA DRC83 ;)

Also, if you could give me a few pointers on how to modify your JIT patches for CM5.0.7-based 2.1 Sense ROMs, I'd be ever so grateful.
[G1 Android Development] xaueious:
I just recently noticed the .34 branch on cm-kernel and aosp. Is the new .34 perflock different than HTC's implementation for msm?

Does this impact us a lot?
[G1 Android Development] pershoot:
diff out the source. i have not personally looked at perflock, myself.
[G1 Android Development] Izord:
Flashed on on a MT3G Over CM5. What I noticed. The kernel in CM5 is Kernel Linux version 2.6.33.4-cyanogenmod

gcc version 4.4.0 (GCC) #1

PREEMPT TUE May 25

This is Kernel Linux version 2.6.34-cyanogenmod

gcc version 4.3.3

PREEMPT Thu May 27

Pershoot why did you go backward on your Gnu Compiler Collection?
[G1 Android Development] pershoot:
i have found that 4.3 works best with kernel source vs 4.4, and the flags i am passing to the compiler. im also not using stock arm-eabi toolchain for the DS kernels, but rather an optimised one.
[G1 Android Development] Izord:
Sounds good, and running well on my 32B MT3G. I had a tense moment when I thought it was stuck on the green bootscreen, but it got through that and all is well.

Lemme ask you, why do you limit to 576? My device seems to want to run at 633 all day. I'd rather use your kernel than dumfuqs, because your name is more civilized. ; )

But why not more raw speed?
[G1 Android Development] XxKOLOHExX:
Is it possible to port the JIT compiler from 2.2 to 2.1?
[G1 Android Development] pershoot:
Re: ToAsTcfh Overclock Kernel Patch :: Downloadable Kernels For G1/32B/32A

>576 is not stable for the masses, so this is why I don't go past it.
[G1 Android Development] rynosaur:
kind conspiracy theories

I'm getting that funny deja vu all over again: sometimes the top devs around here (e.g. Cyan, Koush, WG, JF, a few others who don't come to mind, and now Pershoot again) will say something in a certain way or hold a certain line that sounds like they work during the day in the Android R&D department at a certain big company in Mountain View, or at least are saying things one would expect from software engineers. Wouldn't it be delicious (and hilarious) if CM and parts of XDA, etc are just skunk works/a prototype field test for HTC and Google? My evidence is scant and mostly suspicion, and my psychiatrist would probably be concerned about this kind of thought pattern, but still :D

Anyway, Pershoot, you rock, and you're right, upper 600s on a G1= spontaneous reboot, but I never test 614400 for instance, cuz it's seems as stable as 576000 IMX; I am trying to find a ROM I can rely on 100% @ 652800 hehe. Thanks for your good thoughts/work.
[G1 Android Development] Izord:
Oh well, 576 is rock solid stable for my MT3G as is 614 and 633.

I had one reboot at 645 while 3D gallery was running and I took a picture on an earlier build of CM5Test.

Be nice to have the option.

But I'm pretty happy with 576. Maybe after things settle I'll go to try another kernel without limits.

For now this is nice.
[G1 Android Development] Izord:
Awesome if the top paid devs are contributing to the enthusiast community in their after hours!!

:p;):p
[G1 Android Development] Ace42:
I doubt it, you're better off just waiting for the source from google and making a 2.2 rom that would blow away a 2.1 rom. If i'm not too off, Gingerbread should be here this year if all goes well. Wonder what tasty treat is after that?
[G1 Android Development] anomalous3:
I think the whole Google Cease & Desist situation is pretty strong evidence that Cyanogen's not working for the big G. On the other hand, most of the top Devs on this site probably do, or have at some point in their life done, professional software development. This means they have a very different idea of what "stable" means. To you and I, stable means no force closes, freezes, or random reboots until we flash the newest ROM in 2-72 hours. Now that CM5 stable is out I plan on not flashing anything new for some time, but you get the idea. When you're talking about enterprise class software solutions of the type these guys have probably worked on, stable is more like no force closes, freezes, or reboots even if you abuse the software for a month. My phone ran "stable" at 691 Mhz for a couple days but then started freezing randomly. I had to bring it all the way down to 633 before the behavior would stop. I didn't notice it at first simply because I was manually rebooting more often than the error could occur. Now JIT, I think, is almost ready for prime-time, and it never caused anything of that type, but some things like the xda app force close every other time I open it; I'm willing to deal with this for the improved performance. Stable means not having to make those compromises.
[G1 Android Development] rynosaur:
Yes, I really should study up on the exact definitions of development/testing/stable/unstable/backport etc etc around the 'Nix kernels and software packages. Anyhow, you discussion about enterprise and mission-critical stability versus end-user stability w/r/t Android reminds me of the BB Curve I had on T-Mo and how often I had to do a battery pull to resolve a freezing issue. So enterprise-stable . . . not so much :)

I am having severe JIT-envy since I'm running a Slide port. It's going to drive me to figure out how to "backport" (right?) Pershoots JIT/CM kernel to Chief's Slide build. Probably MUCH easier said than done. Strangely, it seems this Slide kernel can tolerate higher overclocking than CM5.0.7 does. Don't ask me why . . . . yet.
[G1 Android Development] anomalous3:
lol I think most enterprise level devs could learn a lot from cyanogen and pershoot and the others on here; I was mostly using it as an example of what they shoot for, but the truth is we're just lucky to have devs that actually know what they're doing. Some companies hire much better devs than others. Also, since they don't have deadlines they actually have time to perfect stuff to their standards.

As far as the JIT goes, I'm assuming that the slide port has been completely deodexed including the framework; if it hasn't that would be why JIT doesn't work. I'll have to check it out. IIRC it's also huge so might it be stashing the dalvik cache in places it doesn't belong?

[edit]looks like it's deodexed but I forgot - it uses sense UI which doesn't play well with JIT. Still, this has piqued my curiosity enough to make me flash a non-cyanogen ROM for the first time in over 2 weeks.
[G1 Android Development] custommsp:
It seems to me that pershoot's latest "xtra" kernal really speeds up CM5 stable. The phone feels a lot more responsive. Can anyone else confirm this?

Thanks to everybody for their amazing work.
[G1 Android Development] fastludeh22:
having issues with the xtra one from here. i installed it at 3pm yesterday. i had 3 reboots by 8 pm. 2 while making a call, and i think 1 was after sending a text. also i went to bed at 12 and the battery was at 100% and i woke up at 6am and it was stone dead, wouldn't even complete a boot up. now i know my bat is on its last legs, but i got 21 hrs out of one of your kernals when not pushing it.

sorry i was nowhere around a comp to get you last_kmsg, ill try today. to make sure would the command be "adb pull /proc/last_kmsg /sdcard/last_kmsg" ?
[G1 Android Development] pershoot:
Sounds like u may not be able to do the upper freqs stable (there has been 1 othe device in this thread which could not do it).

Do this:

Clear cache/dalvik, reflash rom + kern update + gapps, reboot.

Make sure u have setcpu 1.54 installed, autodetect, 122-528, ondemand, onboot, turn off auto refresh. Reboot.

Use it for 12-15 hrs. If no issues, then bump up 1 from 528. Observe for another 12-15. Then bump up again, and so on and so forth until u hit max. You should be able to determine your stable max within a day and a half or so.

Good luck.
[G1 Android Development] pershoot:
also make sure you dont have any apps eating your battery.

my test device has been on with wifi set to never shutoff, and i get 1-1.5% drop an hour at idle.
[G1 Android Development] kristoff123:
Just wondering what the differences are between pershoot's kernel and dumfuq's, besides the obvious higher clock frequencies on dumfuq's. Is pershoot's kernel reckoned to be more stable or responsive?

Dumfuq - that name tickles me every time, lol.
[G1 Android Development] jaychym:
Which one would I download for Mytouch3G v1.2?
[G1 Android Development] pershoot:
i believe you would use 32b.
[G1 Android Development] fastludeh22:
Ill do that for testing purposes for you this weekend, but I'm going to speculate that that is not my problem. I say this because I've been running oc kernals since about page 40-50 of this theard, chiming inhere and there, but mostly quietly watching and using without anyproblems. As a matter of fact when using dumfuqs kernal in past I didn't get fc's till 680-something and didn't get instent reboot till 710. I've been "stable" for a few days at 633. Ivee been running your xtra kernals exclusivly since about page 70, they just seem very smooth. Yesterday was first time I got a reboot on it. Got 1 in my pocket at work today also. I have set cpu 1.54 and been set at 176-576. Ill try your tests though and repot back.

Thanks for the hard work.
[G1 Android Development] pershoot:
it is designed to be run from 122.

you are the first to report this behavior. i myself have been running it non stop (no reboots in between) and have found no issues.

im leaning towards some extraneous factor causing it.

please reflash with clearing and see if that sorts it. pls capture full logs so i can assist you in troubleshooting it.
[G1 Android Development] fastludeh22:
ya i've been running it 122-576 up until about 1-2 weeks ago. not very often, but once in awhile it seemed to have wake up lag so i had tried upping the min to see if it helped, but im thinking it was from the launcher i was running.

ill reflash and set it up the way you outlined and report back, in the mean time i was able to pull last_kmsg 1 min after reboot of sending a few pic messages. i sent you the link in a pm, let me know you got it.

im on a g1 fyi
[G1 Android Development] pershoot:
you should receive no wake up lag. i amended the cpufreq_ondemand values for that to be next to non-existant.

i left my phone idle for 2 days, then woke it back up and clicked browser and it came right up (for example).

if you are, that may be setcpu. uninstall it and echo in your values to cpufreq.
[G1 Android Development] pershoot:
from your log: Internal error: Oops: 817 [#1] PREEMPT

after you clear and reflash clean, if it persists, i will scan this out.
[G1 Android Development] pershoot:
for those that have asked for it:

JIT – CM5.0.7 – Dream/Sapphire - http://droidbasement.com/db-blog/?p=485
[G1 Android Development] rynosaur:
Thank you very much! I am thinking of changing my middle name to "JIT", or possibly getting a cool tattoo of it ;)
[G1 Android Development] anomalous3:
Not yet; the SDK version doesn't have JIT and the nexus version is compiled for ARM7 :(
[G1 Android Development] pershoot:
.34 working ok for everyone?
[G1 Android Development] Ace42:
I've been using it on a sense roms(2.1), havent had any problems at all.
[G1 Android Development] pershoot:
new dream/sapphire kernel images posted (kernel 2.6.34) - http://droidbasement.com/db-blog/?p=496
[G1 Android Development] Ace42:
There's just one thing I noticed, the batt lasts a long time while sleep..But during continuous use I managed to kill it b/t 1-2hrs after a full charge. I think it's linked to me wiping the batt stats.
[G1 Android Development] pershoot:
you will only save power while idle/close to idle. if it is pinned at max, you will get draw.

in 1-2 hours, that's quite quick. try to recalibrate and monitor your actual useage/useage patterns.
[G1 Android Development] PorchSong:
Pershoot,

It's breaking my wifi. I even wiped the phone completely -- even going in manually deleting directories via adb. Did 5.0.7 DS, gapps and wifi worked. Applied your 2710 kernel, and then it will not initiate-- "unable to start."

I am going to wipe it again and see what happens, but I know it is isolated to your kernel at this point on my phone as it breaks immediately after kernel install. The 2310 worked.

Trying the 3010 now. Will let you know.

***Edit***

I cleared the cache and reflashed and nothing, so I wiped the phone completely again, and started from scratch, and. . . .it works now. Thank you, Pershoot. But, what gives with the dirty unmount of sdcard?
[G1 Android Development] pershoot:
Re: ToAsTcfh Overclock Kernel Patch :: Downloadable Kernels For G1/32B/32A

Wifi works fine over here. Reflash clean (clearing cache b4 rom reflash).
[G1 Android Development] dumfuq:
multitasking test

This is NOT an update for my oc-kernel. If you are happy using my kernel there is no need to flash this.

This is a weak hack in order to improve multitasking on this kernel. This is a test, this is ONLY a test. This does appear to work for me (most of the time). I have been able to open a webpage, go to messaging, then to gtalk, then to maps, and return to the webpage without a reload.

This is a WEAK hack. It may introduce other problems. I really don't know, and I really don't care. I was just sick of reloading a webpage just because I wanted to reply to a text.

For those that know the kernel code, here is the change. If you know this will cause problems, please let me know.

diff --git a/drivers/staging/android/lowmemorykiller.c b/drivers/staging/android/lowmemorykiller.c
index 50d5f91..16ccd17 100644
--- a/drivers/staging/android/lowmemorykiller.c
+++ b/drivers/staging/android/lowmemorykiller.c
@@ -90,7 +90,7 @@ static int lowmem_shrink(int nr_to_scan, gfp_t gfp_mask)
int selected_oom_adj;
int array_size = ARRAY_SIZE(lowmem_adj);
int other_free = global_page_state(NR_FREE_PAGES);
- int other_file = global_page_state(NR_ACTIVE_FILE) + global_page_state(NR_INACTIVE_FILE);
+ int other_file = global_page_state(NR_ACTIVE_FILE) + global_page_state(NR_INACTIVE_FILE) + 2048;

As all my kernels, this is overclocked with a default of 825mhz, so tweaking is a must if you want it to boot.

oc825-cm-5.0.7-ds-mt-test-boot.img
[G1 Android Development] XxKOLOHExX:
Thank you :D Going to try :D

I know this is a test only but do you want feedback last_kmg (or w/e) or logcats?
[G1 Android Development] dumfuq:
Yes, feedback would be good.
[G1 Android Development] dumfuq:
with further testing, I have found this to work with comcache w/ backing swap, and just regular linux swap. It does NOT work if no swap at all is enabled. I haven't tried plain compcache however.
[G1 Android Development] dumfuq:
multitasking test2

So with the first multitasking test I recieved a kernel panic "attempting to kill init" :) when trying to background >5 apps and switching between them.

This one I toned down to "+ 1536".

I haven't been able to make it do the kernel panic, however it does force a reload on the webpage when too many apps are backgrounded.

oc-825-cm-5.0.7-ds-mt-test2-boot.img
[G1 Android Development] rynosaur:
This boot.img will disable Pershoot's JIT kernel, correct? Is there a way to OC+Multitask+JIT?
[G1 Android Development] dumfuq:
JIT is not in the kernel. I am using JIT with this.
[G1 Android Development] rynosaur:
Now that I pulled apart Pershoot's last JIT zip file, I see that, thank you.
[G1 Android Development] pershoot:
is the latest .34 working out for everyone (aside from the known issue(s))?
[G1 Android Development] defconoi:
pershoot, works great for me, also im running dumfuq's mutlitask hack, you may want to look into that, it's rockin my g1, its much more usable
[G1 Android Development] sombionix:
Anyone test the OC kernal on 5.0.8 T1 yet?
[G1 Android Development] tnpapadakos:
yes, seems to be working fine
[G1 Android Development] Jigga0o7:
Yup working good. Running 245-633mhz w/ 96mb swap at 60 swapiness & LauncherPro. All to the good.
[G1 Android Development] sombionix:
Thanks guys
[G1 Android Development] pershoot:
new DS kernel images (2.6.34) posted - http://droidbasement.com/db-blog/?p=515
[G1 Android Development] XxKOLOHExX:
By any chance does that have the multitasking ability by dumfuq?
[G1 Android Development] pershoot:
it does not contain the extra NR_FILE value.
[G1 Android Development] XxKOLOHExX:
Alright :D Thanks going to try it now :D
[G1 Android Development] pershoot:
new dream/sapphire kernel (2.6.34) images posted - http://droidbasement.com/db-blog/?p=532