yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] wildmonks:
Yah, it should, thanks to a bit of code change by pershoot. This was commited in on the 110710 kernels but was broken when I first added the RogerPodactor's and loginwithnoname's battery code for direct access to the battery's EEPROM chip (kernel ver. 111110). Its all been fixed now in the 111110b kernels :)
[Nexus One Android Development] wildmonks:
Awesome! Glad it working out good for y'all :)
[Nexus One Android Development] criscan:
Hy friends, i have a doubt:

I flash kernels using Fastboot(.img) or Recovery(.zip)!

I would like to flash 35.8 but how can i backup my current kernel?

Sorry, its a simple question but i didn't found answer on my search.:confused:

Thanks.
[Nexus One Android Development] fcisco13:
Do a nandroid before flashing kernel then ,flash .zip in recovery
[Nexus One Android Development] criscan:
Ok, but this is a backup of the Rom (boot, system, data...) not only kernel!!!;)
[Nexus One Android Development] mtw4991:
Using Amon_Ra recovery, boot into recovery and backup/restore..nandroid IS the backup.
[Nexus One Android Development] Vlad83:
He isn't looking to back up the entire ROM, just the kernel.

There isn't an easy way of doing that, maybe through ADB that I am not aware of. If you are constantly flashing kernels why not just save the last installed kernel instead of backing it up? Sounds like more work for nothing...
[Nexus One Android Development] criscan:
Ok, perfect, now you answer my question!

Then, it's time to make an app (like OCLF by RyanZA (SGS)) that backups your current Kernel before flash a new....:D....Just a suggestion

And as we see it's not a simple question.

Thank you all!
[Nexus One Android Development] mrdemo007:
I acctually have had quite a few crashes related to viewing images in the built in android photogallery app. the crashes have been both when oc:ing and not.

using latest 2.6.35.8_AVS-950mV_BFS_AXI_No720p_1152MHz_111110b kernel.

I am using Geo411´s stock deodexed rom if that could matter.
[Nexus One Android Development] Treatcon:
I use the CFS version and have been browsing the web, using bluetooth, market, Angry Birds, taking pictures and videos, viewing my gallery and using Flikie with not a single restart or FC at all. Battery is also holding up very well!

Latest benchmark, just hit 1838.

This image has been resized, click here to see the fullsize original.
[Nexus One Android Development] mrdemo007:
just flashed the CFS version too, i experienced a few crashes with BFS and it drained my battery unusually fast...
[Nexus One Android Development] cyberchuck9000:
Just keep the last kernel you flashed on your SD card or computer? Am I missing something?
[Nexus One Android Development] temasek:
I am starting to love this kernel. Flashed this kernel, did a battery learning successfully, changed battery age back to 100%. I'm loving it. :)
[Nexus One Android Development] wildmonks:
Did you experience the same problem using the pervious No_720p 111010 kernels?

I wonder if stock froyo doesn't like the RCU changes, battery driver, or both. :confused:
[Nexus One Android Development] mrdemo007:
nope i dont think so atleast, i think i will try SVS later on as i am seeing alot of crashes in different applications too, earlier i thought it only was in picture viewer but today i got a reboot while writing an sms...

I need to evaluate the battery on the CFS kernel a little bit more though :), but i am sure BFS drained my battery in around 12h with little to none usage.

ive also stopped using setcpu completely, so that there should be no interference from oc or governor settings :)

(maybe a stupid question but is there any way to get a hold of the dmesg output after a crash, if that could lead us any closer to solve issues)
[Nexus One Android Development] wildmonks:
From my conversations on twitter, it seems the 720p kernels may also have this crashing problem (especially when multitasking). This to me sounds like the RCU change I did is to blame. I did a quick reverted the RCU config back to the way it was and uploaded it here for the folks that are helping me beta test it.

http://wildmonks.whoisthedrizzle.com/kernel/test/111410/

As for the dmsg log you can use this command after a crash.

adb pull /proc/last_kmsg

If the problem persist, I can just go back to 35.7 and work from there to isolate the issue. (I really only made 2 major changes from 35.7 so it should be easy to figure out).
[Nexus One Android Development] simms22:
i tried the beta and had the same issues. actually even a worse issue, browse freeze. this site and this thread froze :rolleyes:
[Nexus One Android Development] wildmonks:
Bleh.. ok, reverting battery changes and if that doesn't fix it, then its back to use 35.7 source :rolleyes:
[Nexus One Android Development] BakaPhoenix:
I don't know if is a problem of the kernel but after installing the 111110b all the apps that i tried to install says that i haven't got enought space (i'm using dark tremor's a2sd)
[Nexus One Android Development] simms22:
im using DT also, have used many of these kernels and have never had that issue. how mych space do you have in internal, because app data still goes in there.
[Nexus One Android Development] BakaPhoenix:
i still have about 40 mb, i've also tried to unistall and reainstall the same apps

but i have the same problem :(

Edit: i rolled back to the 111010 and i have the same issue, so i think that the problem is an other ^^' sorry for the bother XD
[Nexus One Android Development] wildmonks:
Ok, so far it looks like its the battery driver as it now seems to be stable (at the moment) when I revert it back. Damn shame because I really liked it. :( If it continue to go well, I'll do a full release.
[Nexus One Android Development] temasek:
I am using svs cfs kernel and had a total of ZERO issues. In fact it had impressed me over my last days usage after I had did the battery learning and resetted the battery age back to 100. Very smooth and fast.

I check out your beta2 and quickly reverted back to the older kernel.
[Nexus One Android Development] EnhancerFIN:
I'm using the bfs-avs with cm6 nightly build 245 + setcpu to control and I've had zero problems!

Battery life has been at least double better as with kernel included with nightly build.

My screen on -profile in setcpu is 1152min-1152max and screen off -profile us 384min-652max ondemand. I did get issues with screen off 128min, really slow after turning the screen on, but nothing after bringing the min a bit up.

Normally my battery has been round 25% at midnight, now 53%.
[Nexus One Android Development] redstar3894:
It could have possibly been a change to CFS task accounting and scheduling that would break BFS that was fixed by this commit from IR

Not sure if you committed that, but the BFS kernel I compiled without that fix had some major issues... this mostly fixed it, but there still seemed to be some minor hiccups... :rolleyes:

Also, the PREEMPT-TINY-RCU changes are great, but also I'm not sure how well it gets along with BFS... personally I always used BFS but when I found that addition, it made CFS kernels so silky smooth that I ended up switching... :D

That being said, I agree that it might have some regressions which break BFS support and BFS kernels might be better suited to using something like the Classic RCU or Classic Preempt RCU...

Just my 2 cents... :p

BTW: glad to see you're back, if only intermittently, it was you and IR who first inspired me to start building kernels... :D Keep up the good work dude! ;)
[Nexus One Android Development] wildmonks:
I compiled a beta2 kernel for you to see if it helps at all with your crashes (this kernel without battery changes).

http://wildmonks.whoisthedrizzle.com/kernel/test/111410/beta2/

It helped with 2 other users so maybe it will for you too.

I haven't yet commit in those changes from IR and from the looks of it, i guess i shouldn't :rolleyes:.

Ah, thanks for your insight on the preempt rcu. After all this investigating it looks like it's ok to leave that in.

I'm kinda confused now if the battery driver was really the cause.:confused: Maybe it only affects some users. I'll wait for mrdemo007 to try out beta2 before making any final decisions.
[Nexus One Android Development] temasek:
The battery driver is the viagra to my aging battery. Pls let me have it. :)
[Nexus One Android Development] redstar3894:
It was that commit I referred to and this one as well...

It really seemed to help with the "jittery" nature of CFS and definitely helped smooth things out... I would definitely recommend using it, but I could also understand if you were a little reticent about merging it in just yet... :p

With the tiny preempt rcu, this provides a nice little boost to CFS as it helps the scheduler keep better track of tasks, specifically IO and DMA activity, and schedule accordingly... but since I'm not sure where cyanogen originally got this commit from, I don't know if it was ever merged into the mainline kernel, which would potentially explain why it doesn't get along with BFS without IR's fix... and the tiny preempt rcu was only recently included in the mainline 2.6.37-rc1, so that could also account for some of the "issues" people might have with BFS... :confused:

The battery driver only seemed to cause problems for me when I wiped the battery stats, otherwise the only major changes they've made involved read/write to the registers in the ds2784 EEPROM chip in the battery... otherwise it's been fine, no real issues have popped up either in use or in the dmesg or logcat outputs... :rolleyes:
[Nexus One Android Development] wildmonks:
Yah, those read/write codes in the battery driver is what I removed and compiled in the beta2. Honestly I don't know how that piece of code could be the problem. Maybe its something else I'm overlooking...
[Nexus One Android Development] shuka325:
Been running CM 6.1 with this kernel, 2.6.35.8_AVS950mV_BFS_AXI_720p_1152MHz_111110b for a while and have had NO issues. Loving it and i do see a little bit of money for your OJ fund on the way. My Nexus honestly has never run smoother. Keep up the great work.
[Nexus One Android Development] wildmonks:
I love this comment. A very fitting analogy :D

Don't worry, one of my beta tester still crashed when I removed it so its probably not the battery. It must be something I inadvertently introduced when moving from 35.7 to 35.8 (35.7 works perfectly for him). I decided to re-base back to 35.7 and slowly add back in the commits.

Coolzors ;)
[Nexus One Android Development] simms22:
ive got to say, i really do like that 35.8 beta2. even with it panicing while using pandora. otherwise its very smooth. and i should say that im getting abnormally wonderful battery life. thats always a plus, much more important than pandora :)
[Nexus One Android Development] medi88:
Hi,

Managed to solve the problem... Apparently, after flashing to your latest kernel, my Laptop diesn't recognise my device so i had to update the USB driver..

All is well now...Thanks
[Nexus One Android Development] wildmonks:
Ah, Thx for the update. Glad to know it's working again for yah. :)
[Nexus One Android Development] mrdemo007:
i just flashed 2.6.35.8_AVS-950mV_CFS_AXI_No720p_1152MHz_111410_beta3, i will report any findings later today :)

thanks for all your work wm :)
[Nexus One Android Development] badantii:
Thanks for this awsomeness :). Trying out the No720p/NoAB on CM6 RC1! Seems to work well :).
[Nexus One Android Development] Treatcon:
Ditto but I use the 2.6.35.8_SVS-950mV_CFS_AXI_720p_1152MHz_111110b version. Not a single problem at all, silky smooth and wonderful battery!! :D
[Nexus One Android Development] YoMarK:
Thanks wildmonk, using the latest kernel with MIUIMOD. Works fantastic and very fast with the performance CPU governor. 22+ in Nenamark. :D
[Nexus One Android Development] jameztcc:
Hi,

Am running the following kernel, been fast and stable ondemand with setcpu sleep 128/128.

$ uname -ai

Linux localhost 2.6.35.8-wildmonks #168 PREEMPT Fri Nov 12 15:40:58 PST 2010 armv7l GNU/Linux
[Nexus One Android Development] kyota:
Hello ..

Can you make these two specification of files for me ?

I really need them .. Thank you very much .

2.6.35.8_SVS-950mV_CFS_AXI_720p_1228MHz

2.6.35.8_SVS-950mV_BFS_AXI_720p_1228MHz
[Nexus One Android Development] byrdman164:
Hey..been running your 2.6.35.8_AVS-950mV_CFS_AXI_720p_1152MHz_111110b since last night and it's great...But I have a question. I'm using launcher pro, and it seems when I run over 1075mhz, the home screen keeps reloading itself over and over, and it's real difficult to click the setcpu widget to slow it down and 'correct' it. It doesn't happen with adw, so could it be a problem with launcher pro? Or something with the kernel? Never noticed an issue until I went higher with the cpu. Anything I can provide as far as information?
[Nexus One Android Development] daveid:
Same here, my serial number which is the representation of the specific device to the PC was changed with a recent kernel update. It had to reinstall the device on my PC, which is how I noticed (I connect multiple Android devices and need to specify which I am connecting to) that the serial number for my Nexus was now (and continues to be) wrong.
[Nexus One Android Development] pwig:
My phone is running nightly 247 and it gets real hot and current widget is saying about 550ma is being drawn. I tried all four beta kernels. When I flashed the nightly back over it, my battery use went back to normal. Did I miss something? I just flashed the kernel in recovery.
[Nexus One Android Development] sl8125:
@WM: How are your test kernels released on 111410 different from 111110?

You don't need it. You just WANT one. Cuz i WANT one too. But 1152mhz is fine by me. What will i do with additional 5% more of my cpu. Nothing. But I wouldn't mind it.
[Nexus One Android Development] sl8125:
Does anybody have any issues with connecting ADB with the new kernels. I am currently using 2.6.35.8_SVS-950mV_BFS_AXI_720p_1152MHz_111110. with this kernel everytime i connect my n1 to my cpu, usb connect automatically and having to turn it off when i connect to tether. before, it was an option to turn on to connect to cpu. i wonder if usb mode is on as default. @WM, can you confirm? I can't seem to connect. I am having to use the terminal emulator.
[Nexus One Android Development] fitsnugly:
USB is acting fine here... usually if it's auto-mounting the USB drive, it's an app doing it like Winamp or DoubleTwist
[Nexus One Android Development] wildmonks:
Running fine here with nightly 247 and the AVS BFS beta 3. Do you experience the same problem running a 2.6.35.7 111010 kernel?

Beta 3 kernels is a re-base back to 111010 with only a few cherry pick commits from 2.6.35.8 and preempt rcu without rcu boost + RogerPodactor's and loginwithnoname's ds2784 battery driver. Its an attempt to solve the crashing problem mrdemo007 and simms22 was experiencing with 111110b.

And nope, I will not make anything higher then 1152mhz kernels. They're way more trouble then its worth.
[Nexus One Android Development] wildmonks:
I experienced the same thing too a couple weeks back. Turns out it was Winamp auto-mounting my phone.

As for the ADB related issue, it maybe similar or related to medi88's problem. He fixed it by updating his android usb drivers. http://xdaforums.com/showpost.php?p=9218757&postcount=2231
[Nexus One Android Development] mrdemo007:
No crashes so far with beta3, and feels really responsive, will try to use setcpu too see if it likes to oc.

Seems to be back to normal with battery drain too!
[Nexus One Android Development] wildmonks:
Nice, hope it stays that way. :)

Oh right, dang.. totally forgot to mention this. In the updated battery driver there a command you can send that affects the battery percent meter.

As quoted directly by RP.

Set charge back to <40mA:

echo 0x65 0c > setreg

if you even wanna go <20mA:

echo 0x65 06 > setreg

Back to stock value of <80mA:

echo 0x65 18 > setreg

In the 111010 kernels, it was automatically using <40mA but now you have a choice by using the above commands. For more info on this command go to:

http://xdaforums.com/showthread.php?p=9195120&highlight=echo+0x65#post9195120

Might explain the perceived battery drain difference after flashing a kernel with the new battery driver.
[Nexus One Android Development] simms22:
maybe someone else can reproduce my crashes with any of the 35.8 kernels. i use pandora. after about 5-15 minutes of streaming pandora and generally using the phone at the same time(browser, gtalk, tweetcaster, etc.) i get a freeze. the phone freezes but whatever im listenung to on pandora keeps playing. sometimes its with screen on, sometimes off. but usually, i have to pull the battery. besides for that, the kernel is silky smooth and has great battery life. beta 3 took a little longer to crash, but crashed nevertheless :(
[Nexus One Android Development] sl8125:
Mang. Thanks for quick reply. Everything solved. Got rid of Winamp and reinstated driver fixed all issues with adb. Thanx.
[Nexus One Android Development] fitsnugly:
have you pulled last_kmsg once you're booted up right after the crash?
[Nexus One Android Development] simms22:
just got a crash on 35.7 using the stock music app. sent you a log by email.
[Nexus One Android Development] simms22:
ive gotten a few freezes to wake, then got a log.
[Nexus One Android Development] mtw4991:
been using svs-cfs-111110b on CM245/246 for a couple of days and have not had one issue at all, no reboots, fc's, nothing. using RP setage=100% and setreg=<20mAh and getting awesome battery life. 245/1075 ondemand, fwiw.
[Nexus One Android Development] temasek:
Same.................
[Nexus One Android Development] dark79:
You didn't have to uninstall Winamp. You can disable automount in the settings...

Sorry if I'm repeating something in the last 200 pages or so, but searching in thread isn't working for me:

Anyway, SetCPU with this kernel (or pershoots 2.6.35.8 kernel) gets stuck at whatever the max setting is. There's no throttling at all. It just stays at 1152 and never throttles down. This happens whether I set it at Ondemand or Interactive. I've already tried a full wipe and it didn't matter.

The other odd thing is that it profiles are affected, too. For example, I have it set to 998/245 when charging so that it doesn't get too hot and as I explained above it stays stuck at 998 and never throttles down. But when I unplug the charger it should switch back to the 1152/245 profile (and get stuck at 1152), but it doesn't. It stays at 998.

Just to be sure it really was doing this I added a screen off profile of 345/245 and when the screen turns off it would drop to 345 (no idea if it ever throttled to 245), but when I turned the screen back on, it was again stuck at 345 even though it was back on the 1152/245 profile.

I know it's changing the profiles appropriately because SetCPU app and widget both change the max and min per profile appropriately. But the current speed shown doesn't match the profile and stays at a constant speed depending what profile it was at previously.

Quadrant runs verify that the current speed shown is displayed correctly (e.g. it really was stuck at 345 after screen turned back on).

I haven't tried installing a 2.6.35.7 kernel yet, but I'll try that next.

Anyone have any suggestions? I'm running CM6 247 nightly, but I've had this issue since 242.
[Nexus One Android Development] criscan:
Blunden's answer:

"The kernel is a part of the boot.img and is backed up by nandroid, yes. You could just fastboot flash boot boot.img from your nandroid if you don't feel like restoring the entire backup..."

Thank you, Blunden
[Nexus One Android Development] nitrox1:
Hello, @Wildmonks,

I am relatively new, having only had my nexus one for a week.

Already I am running cm6-n1-rc1, with your BFS-1152Mhz-AVS-950mV kernel (2.6.35.8_AVS-950mV_BFS_AXI_720p_1152MHz_111110b). I defiantly noticed alot of "better" differences, between your kernel and stock (even touch screen, but could be my imagination), and even prefer yours to Ir.

I run your kernel between 245-1113Mhz ondemand (deciding if I need screen off 245-384Mhz powersave, and think 128Mhz is a little unstable, these could be old phone habits))

But I have owned an HTC Desire for about 8 months prior to me bricking it, in flashing a corrupt HBOOT file (Because I didn't check my Md5).

But I was using a kernel and ROM for the desire, that enabled me exceptionable battery life. 10% battery loss compared with 30% most of the time, over a 5 hour period, and 1825 Quadrant scores in performance gov..

Now I might need a quick lesson between the Desire and the N1, but to me they are too similar.

Anyway, the kernel ran HAVS-BFS-245-1113Mhz but with 875mV, even had "smartass governor" (which did nothing for me)? Is this possible on the N1?

I have included his github: https://github.com/richardtrip/cm-kernel/tree/bravoc/kernel/

Thanks for any info.
[Nexus One Android Development] samarium:
+1

N1 with CM 6.1 Nightly 245 and WM 111110b kernel, and overall a good experience.

While /proc/cmdline continues to have androidboot.serialno=correct, when I attach the device to my windows box & query with ADB devices, I get 0123456789ABCDEF as the serialno.

Looking in devmgmt.msc, it seems that the WM kernel is returning USB VID=18D1 PID=4E12\0123456789ABCDEF rather than than PID=4E12\correct-serial-number.

I've been using either stock CM 6.1 nightly kernels or IR kernels before that, so this seems to be a regression.
[Nexus One Android Development] jameztcc:
Same thing, on Linux btw:

~$ adb devices

* daemon not running. starting it now *

* daemon started successfully *

List of devices attached

0123456789ABCDEF device
[Nexus One Android Development] skorpioneMM:
For curiosity... are you using interactive cpu governor?

I ever have problems with this cpu governor... all works fine but when im starts a few apps at the same time (multi-tasking) after a few time, my phone ever freezes.
[Nexus One Android Development] simms22:
im using interactive, performance, and ondemand.
[Nexus One Android Development] wildmonks:
Nice catch! I'll have to fix this in the next release, maybe tomorrow or the day after, time permitting.
[Nexus One Android Development] Pochemuchka1977:
Same here in Win7 64, running 11110b kernel
[Nexus One Android Development] daveid:
Just to double confirm this is what I mentioned in my previous post, when flashed with IR's latest kernel my serial number is represented properly.
[Nexus One Android Development] simms22:
my problem with the freeze during pandaro streaming is solved! woohoo! wildmonk had me try out some different variations with the kernel(35.7 & 35.8) and we got a winner. thanks again wildmomk :)
[Nexus One Android Development] fitsnugly:
what was the problem?
[Nexus One Android Development] jlevy73:
Simms forgot to take SetCPU out of "drunk mode" :p
[Nexus One Android Development] simms22:
hahaha... my phone doesnt believe in drunk mode! i believe it was just a little more voltage, maybe something else too. wildmonk could explain better :)
[Nexus One Android Development] waylo:
Was this on wifi, 3g, or both?
[Nexus One Android Development] simms22:
it was on 3g. i rarely use wifi. my 3g speeds are much better than wifi at the places im usually at.
[Nexus One Android Development] mtw4991:
LMFAO...too funny
[Nexus One Android Development] solidmac:
Same here when ever I use astro or gallery it will pause then reboot. I'm not sure what could be the cause of this problem I hope there would be a fix for it soon so I can take advantage of the wifi calling
[Nexus One Android Development] criscan:
SVS-CFS is running nice for me. Best battery life time kernell...congratulations
[Nexus One Android Development] mik101:
Anyone else trying out his test kernel from yesterday? (15th)

Im using test 3. My phone needs the 975mv for max stability (I get weird errors with most 925/950mv kernels). So far so good. :)
[Nexus One Android Development] simms22:
im running test 3 from yesterday too(2.6.35.8_SVS-975mV_CFS_AXI_720p_1152MHz_111510_beta3.zip). it runs absolutely perfectly for me. i was getting a freeze on all the others. this one doesnt even slow down after a bunch of multitasking going on at the same time