yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] fruitsalt:
just an update on kernel usage:

still am on the previous version of the 800mV Bfs kernel(6/23)

battery life is amazing

stats:

almost 36 hours before the phone died

talk time 2 hours 13 mins

some 80 odd messages ( includes some 5-6 MMS)

5 emails account checked every hour + GMAIL push ( replied to some 10-15 emails)

browsing time : 1 hour 40 mins ( includes some time using flash)

google talk, google voice and Nimbuzz on since 100 % charge ( over 2 hours of IM'ng)

and all the stats i listed before in the previous post also apply(http://xdaforums.com/showpost.php?p=6952823&postcount=379)

so i expect to get atleast 2 days on this kernel by taking out the flashing that i did during this charge.

Note: i keep the screen brightness at minimum and adjust manually as needed, as i dont like how auto brightness adjusts

im switching to kango-rama(FRF83), will test the battery life out on that and report back

thanks again for all the hard work you put into making this amazing kernel.
[Nexus One Android Development] mtw4991:
Wildmonks, here is the pastebin link: http://pastebin.com/yGP5FLdr under "OS Monitor fail to open"

fyi, I can't read these but they just look like avs settings to me, lol. Maybe you, IR or Pershoot have a clue?
[Nexus One Android Development] wildmonks:
Wow, that's weird. AVS is totally not working correctly for you. How are you flashing the kernel to your phone? Flashing directly with the zip or pushing the zImage & bcm4329.ko via your computer? Also which rom are you using? the stock or one of the cooked froyo roms?
[Nexus One Android Development] mtw4991:
I flashed Paul's rom, not the OTA, using Amon_Ra 1.0.7 recovery:

•FRF83 stock rooted + insecure + ChainsDD's Superuser app + deodexed update zip - DOWNLOAD (MediaFire Pro) / MIRROR (ROMraid / CoBlitz) - MD5: fa3c9757320b9d08fbce619a5c421509

I wiped cache, dalvik, battery stats, flashed rom, rebooted, powered off, booted into recovery, flashed your 925 BFS (the one that said 800mV)
[Nexus One Android Development] wildmonks:
Ok, I'm compiling a rom for you that might fix the problem. It will take some time (15 mins or so). In the mean time, try setting your max to 1075MHz, reboot your phone, and after its done loading, try opening up OS Monitor.
[Nexus One Android Development] wildmonks:
Here's a test kernel for you to try out. I changed the way AVS is activated in this one and it has the all the debugging code turned on so you will see lots of lines related to the AVS.

2.6.34_AVS-925mV_BFS_1113Mhz_DEBUG_062610_v1.zip

Because you have the SDK, you can monitor the kernel message in realtime by using the command:

adb shell cat /proc/kmsg

What I'm hoping you'll see is a line that says

Using SVS Regulator (Bypassed HAVS)

Pastebin your results after opening OSMonitor.
[Nexus One Android Development] mtw4991:
Ok, give me a couple of minutes....
[Nexus One Android Development] mtw4991:
I did try setting max to 1075, but didn't reboot afterwards....I'll set to 1075, load the new debug kernel and test
[Nexus One Android Development] wildmonks:
Okay, this tells me its a problem with SVS and HAVS for you. 1075 setting should work on this debug kernel too. Go ahead and try 1113 and see if it works. Hopefully the edit I made will have SVS and HAVS properly working for you.
[Nexus One Android Development] mtw4991:
http://pastebin.com/yLVgv0cM for the debug version
[Nexus One Android Development] wildmonks:
Okay looking good. How about using 1113MHz max?
[Nexus One Android Development] mtw4991:
test ran at 1075: linpack 41-42, quadrant 2nd run at 1647

test ran at 1113: linpack 41-43, quadrant 2nd run at 1727

OS Monitor still won't open :confused:
[Nexus One Android Development] wildmonks:
Pastebin your results right after your OSMonitor refuses to open.

(Yah, your benchmark shows your CPU can handle 1113 without a problem)
[Nexus One Android Development] mtw4991:
ummm....I was doing it right after. What I'd do is hit OS Monitor with my right hand and Enter with my left hand like 1/2 second later and that's what I got. Should I use a different command other than dmesg in shell? Not a programmer here, just a tester;)
[Nexus One Android Development] wildmonks:
Oh ooops.. I might have miss understood you.. sorry -_-;

So OS Monitor has never worked for you on this debug kernel? Even if you use 1075 max?

BTW: I'm really sorry making you become a tester, aka lab rat...
[Nexus One Android Development] mtw4991:
nope, started giving me opening issues shortly after putting on a kernel other than Froyo stock. I would have to tap it several time to get it to stay open, then it wouldn't open at all. Weird.
[Nexus One Android Development] mtw4991:
Wildmonks, I just set SetCPU to 245/1075 ondemand and was running realtime monitoring in cat /proc/kmsg and I saw the Using SVS line you were looking for...not sure what it means but its there, lol.
[Nexus One Android Development] wildmonks:
Wow, strange.... Okay, so that problem is unrelated to SVS+HAVS. I'm trying to rack my brain to figure out what it could be...
[Nexus One Android Development] mtw4991:
fyi, in monitoring kmsg, with min245/max1075, it is regulating itself around 925-950mV
[Nexus One Android Development] wildmonks:
Is that before or after launching OSMonitor?
[Nexus One Android Development] mtw4991:
Also, two other curiositys:

The market doesn't always show all of my apps after changing kernels. Easy fix is to uninstall Tmo MyAccount, then re-install and bam, there they are?

Second is with Pauls Froyo, when I plug in USB and check debugging, "sometimes" the SD card gets mounted also....:eek:
[Nexus One Android Development] mtw4991:
after, I can try to launch it while monitoring???

Wow, just turned off debugging and the little android guy mounted my sd card a minute later, lol.
[Nexus One Android Development] wildmonks:
That's awesome, then SVS and HAVS is working together nicely again.

Oh, kinda weird. I'll be on the lookout for that (I'm using the exact same rom)

Nevermind what I said.. dunno what I was thinking. That's actually a good thing about AVS regulating itself around 925-950mV. That means the CPU is comfortable for the moment with 925 or 950mV power. Your saving battery power at that very moment. I've seen it stay at 925mv but its running at 998MHz, which means greater battery savings.
[Nexus One Android Development] wildmonks:
I really don't know what is causing OSMonitor to not open for you. Maybe its a conflict with another program... (wild guess, most likely not). At this moment, I suggest uninstalling it and avoid using it. You do have a much better monitoring program "SystemPanel" and you can always monitor the kernel message using adb.
[Nexus One Android Development] mtw4991:
doesn't say anything now other than "Using HAVS regualtor
[Nexus One Android Development] wildmonks:
It will only say Using SVS Regulator (Bypassed HAVS) when it reaches 1113MHz. If you set your min and max to 1113MHz you will see it.

What "Using SVS Regulator (Bypassed HAVS)" means is its no longer using the energy saving HAVS and instead its using SVS (that's used in the stock kernel) to keep its stability. Unfortunatly your not saving battery power when SVS is used (your eating up as much energy as the stock kernel)
[Nexus One Android Development] mtw4991:
yeah, I got that part. what I meant was, it is no longer showing the 925-950mV setting in the log, just the "using HAVS regulator" statement. didn't know if that meant anything or not
[Nexus One Android Development] wildmonks:
Ah, It won't display "AVS setting V to XXX mV @XXXX MHz" unless it has to change the voltage.

I use the debug code "Using HAVS regualtor" as a place marker in my code to help me figure out where I am in the code when I see it in the kernel message (uh.. if that makes any sense)..

Uh, in other words, this is all normal behavior.

After today, your really going to know the in and outs of what the kernel is doing in terms of voltage regulation :)
[Nexus One Android Development] mtw4991:
lol, yep,,,thx for the education:p
[Nexus One Android Development] dictionary:
This has turned into an interesting chat, lol.
[Nexus One Android Development] mtw4991:
yeah, really helped me with a problem I didn't even know I had, lol. Plus I found a couple of others like the mount sd card issue.
[Nexus One Android Development] wildmonks:
@mtw4991

Do you want to continue using the debug kernel or would you like me to make you a kernel right now without all those debug messages?
[Nexus One Android Development] mtw4991:
sure, that sounds good as long as it works the same ;):D
[Nexus One Android Development] wildmonks:
Yah and strangely fun being asked all these questions :rolleyes:

Yes sir, give me 15 or so minutes to compile it. For the next release, I'll see if its safe to apply the changes I did to the other CFS kernels.
[Nexus One Android Development] mtw4991:
Yes sir, give me 15 or so minutes to compile it. For the next release, I'll see if its safe to apply the changes I did to the other CFS kernels.[/QUOTE]

cool, thx
[Nexus One Android Development] wildmonks:
@mtw4991

Here yah go.

2.6.34_AVS-925mV_BFS_1113Mhz_062610_v2.zip
[Nexus One Android Development] mtw4991:
Thanks man, you've been a big help. Dropbox here we come, lol.
[Nexus One Android Development] LordPhong:
n00b question: I have stock everything with FRF83 for the exception of it being rooted without unlocking the bootloader. Can I just send the bcm4329.ko and zImage from the zip found in the first post? I am liking what I read about this kernel.
[Nexus One Android Development] wildmonks:
Yes you can. The bcm4329.ko and zImage are the two files you must push to the phone to get it to work. The other files are minor optional stuff.

If you do decide to try it out, I hope you like it :)
[Nexus One Android Development] LordPhong:
i put down the bcm4329.ko (in /system/lib/modules) and zImage from 2.6.34_AVS-925mV_CFS_1113Mhz_NoAudBoost_061710.zip but setCPU only sees the max as 998Mhz. Am I missing something?

PS: wifi is nonfunctional.

FRF83 stock.
[Nexus One Android Development] wildmonks:
In setcpu, hit the menu button, select device detection, thenauto detect speeds.
[Nexus One Android Development] knightnz:
Any CPU speed on mine 921Mhz or higher gives me lots of "AVS setting V to 1225 mV @[Mhz]" messages, is this correct behaviour?

Using the current 062610 925mV CFS kernel.

Even if SetCPU is configured from, The "Misc" tab in OSMonitor should show the full valid freq. range (245-1136Mhz). Not much use if OSM isn't starting of course.

I'm using a baked MCR19 FroYo ROM and all is well.
[Nexus One Android Development] wildmonks:
Yes, its normal. It means more voltage is being feed to keep the cpu operational at that MHz.
[Nexus One Android Development] knightnz:
If you haven't flashed the FroYo radio you might get problems.

Well done getting it rooted without the unlock, looks like an awkward process.
[Nexus One Android Development] wildmonks:
Double check the kernel version to see if zImage was properly flashed.
[Nexus One Android Development] wildmonks:
Ditto :)
[Nexus One Android Development] LordPhong:
I did do that. i don't know if it's a placebo effect but it does seem faster even though the benchmarks (linpack, An3DBench, NeoCore, and Quadrant) show no difference.
[Nexus One Android Development] LordPhong:
this is the problem. I'm getting:

C:\sdk\tools>fastboot flash zImage zImage

sending 'zImage' (2158 KB)... OKAY [ 0.319s]

writing 'zImage'... INFOsignature checking...

FAILED (remote: signature verify fail)

finished. total time: 0.708s

any ideas?
[Nexus One Android Development] knightnz:
Write zimage with a lowercase I and see if that works. Maybe rename the local file "zimage.img" or something so you can easily differentiate it.

Some phones also have slightly less space in their kernel partition than others, so it's possible that this image is too big for your phone to handle.
[Nexus One Android Development] wildmonks:
Phew... sorry.. finally in front of a computer....

Its case sensitive and changing the file name will break the signature check (I think). Type exactly:

fastboot flash zimage zImage
[Nexus One Android Development] LordPhong:
thanks guys but that's not the problem according to this post:

http://www.mail-archive.com/android-kernel@googlegroups.com/msg01628.html

that looks awfully complicated.
[Nexus One Android Development] knightnz:
You might want to try anyway:

zImage:

Davros:Applications steve$ fastboot flash zImage zImage
sending 'zImage' (2178 KB)... OKAY
writing 'zImage'... INFOsignature checking...
FAILED (remote: signature verify fail)

zimage:

Davros:Applications steve$ fastboot flash zimage zImage
sending 'zimage' (2178 KB)... OKAY
writing 'zimage'... OKAY
[Nexus One Android Development] wildmonks:
Have you tried what I suggested? I know its case sensitive because I cut and pasted what you wrote and got the same error. But using what I wrote flashes normally.
[Nexus One Android Development] wildmonks:
Oh.. you beat me knightnz... haha
[Nexus One Android Development] LordPhong:
sorry, I should've replied with my result:

C:\sdk\tools>fastboot flash zimage zImage

sending 'zimage' (2158 KB)... OKAY [ 0.319s]

writing 'zimage'... INFOsignature checking...

FAILED (remote: signature verify fail)

finished. total time: 0.708s
[Nexus One Android Development] LordPhong:
@knightnz

I noticed that yours doesn't do an INFOsignature check. perhaps your fastboot is different from mine. Mine is the latest SDK from google.
[Nexus One Android Development] LordPhong:
please ignore last post.
[Nexus One Android Development] wildmonks:
Maybe that zImage is currupt :confused:

Try this one:
[Nexus One Android Development] LordPhong:
no go. sorry. I was looking at your kernel directory in the zip file and it looks like there's a script in there that recreates the boot.img with the new zImage. This seems to be how your zImage is getting in there with the update.
[Nexus One Android Development] wildmonks:
Could it be not having a unlocked bootloader, you can't use the flashboot zimage command? :confused:

I use this method all the time to flash my kernels to my phone because its much faster then navigating true the custom recovery menu. Hmmm.. I'll need to investigate this.
[Nexus One Android Development] LordPhong:
i think you're right but not the bootloader. I would bet that it would work if I replaced the recovery image (RA Recovery).

If anyone else knows, please post.

thanks.
[Nexus One Android Development] wildmonks:
Yah.. if you have RA Recovery, then you can use the the posted zip straight. Forgive my ignorance about locked bootloaders :(

This lesson cost you your wi-fi.... I can try and get a stock bcm4329.ko from FRF83 for you to push.
[Nexus One Android Development] wildmonks:
After reading this I see now that indeed you need an unlocked bootloader to use fastboot...

http://android-dls.com/wiki/index.php?title=Fastboot
[Nexus One Android Development] LordPhong:
I took the plunge and put in RA Recovery. I know the zip file is the easier route. My bad habit is trying something new. BTW, my bootloader is still unlocked and everything is working the way it should (1113/245MHz).

I want to thank everyone for helping me out. The quick response was definitely appreciated.
[Nexus One Android Development] wildmonks:
Oh, I see. Well I did learn something from you doing this, so I thank you very much for that :D
[Nexus One Android Development] mtw4991:
Wildmonks...14.6 hours and 53% still left at 1075 with

moderate to heavy use! Excellent job sir
[Nexus One Android Development] wildmonks:
Awesome, definitely looks like AVS is working correctly for yah :)
[Nexus One Android Development] zizoty:
What's the best app to track your battery usage? I'm not getting battery with your current 800 bfs compared to pershoot.
[Nexus One Android Development] wildmonks:
I don't use an app to track my battery drain. Instead I use this method because it allows me to see the battery drain every other minute so I don't have to wait for the whole battery to drain to get results.

But I have read elsewhere that JuicePlotter is a good app to use.

Maybe other can chime in on what other apps are good as well.

BTW: For comparison I've had avg as low as (-9 avg) which usually results in ~1%/hr drain.
[Nexus One Android Development] rodigezstyle:
@monk

I´m just here to say I LOVE YOUR NEW 34. BFS 800mV Kernel

- OC/UV/RAM

- Best Battery Life

- Very Good Performance

- No 3g errors

- Right Working BFS on FroYo

The Perfect Kernel for me... you and Ivan does a great Job ;)
[Nexus One Android Development] wildmonks:
Thank you very much for your compliment and feedback! I will keep trying my very best on these kernels :)
[Nexus One Android Development] zizoty:
Hey monk, what's your experience with the four kernels offered. Do you keep a statistics of the each kernel and with one you personally use?
[Nexus One Android Development] wildmonks:
In terms of download numbers from mediafire, it currently stands at:

2.6.34_AVS-800mV_CFS_1113Mhz_062610.zip

Downloads: 55

2.6.34_AVS-925mV_CFS_1113Mhz_062610.zip

Downloads: 83

2.6.34_AVS-800mV_BFS_1113Mhz_062610.zip

Downloads: 394

2.6.34_AVS-925mV_BFS_1113Mhz_062610.zip

Downloads: 51

2.6.34_AVS-925mV_CFS_1113Mhz_NoAudBoost_062610.zip

Downloads: 24

The 800mV_BFS is bit skewed since its being direct linked (which I'm humbly honored by :)). In past releases the 925mV_CFS has been the most downloaded which is the one I use, even before I started publicly releasing kernels. I would like to use the 800mV version but my cellular radio acts up sometimes with it (EDGE and 3G would switch back and forth, resulting in a increase in battery drain when it occurs).

Its been my observations on these forums that a small number of people who use 800mV kernels encounter weird behavior on their phones, probably as a result of too little power being feed into the hardware. Guess I'm one of the unlucky few...

In terms of my past usage experience with CFS and BFS. BFS sure is more smoother and quick when manipulating the interface (homescreen, scrolling, typing) but CFS handles multitasking better for me which I do a lot on my lunch break at work (download and listen to podcasts while browsing the web).
[Nexus One Android Development] zizoty:
I wonder if the network play a role for people using 800. I'm on tmobile and 800 isn't as good as 925.
[Nexus One Android Development] rodigezstyle:
Fixed I´m share the Link to this Thread Now..
[Nexus One Android Development] wildmonks:
Maybe not.. I'm on AT&T... :(

Oh, I don't mind direct linking at all ;)

The download stats means nothing to me :o
[Nexus One Android Development] damanrico:
First of all I want to thank you for an amazing kernel, wildmonks. Been using it for a few days now, and it's running great (925mV CFS no audio boost).

Just wanted to ask a quick question about wifi. Does this kernel use a different wifi module, or can we use different wifi modules?

My wifi seems to have a lot of problems lately, with and without your kernel. The same problem (wifi being connected, but acting like it's not having internet access, thus not loading anything) on different routers.

So I was wondering if pushing a different wifi module could solve this problem for me.

Sorry if this question is a bit off topic, but I read quite a lot about wifi modules + kernels in every kernel thread, so I hope you can help me out.

Thanks in advance.
[Nexus One Android Development] agentkalaw:
excellent kernel wildmonks!

i'm using kang-o-rama and the kernel on that rom wasn't surpasing the stock 2.2 speeds during quadrant benchmarking so i switched to yours (925 CFS). and my speeds were faster and battery life seemed better. I then went to the 925 BFS and that was a tad faster. I was scared to switch to the 800 for radio problems but i'm on it now and couldn't be happier...can't wait for your next update. Works flawlessly with the KOR rom!
[Nexus One Android Development] samir5421:
Hi wildmonks can you add kmobs's UV to your kernel? His UV settings have really good battery life, sometimes even better than these kernels. If you could do that, it would be awesome. Thanks.

http://github.com/kmobs/UVkernel
[Nexus One Android Development] athost:
"The best is the enemy of the good" ;)

Wildmonks, your kernels are almost perfect.
[Nexus One Android Development] THATTON:
If this is possible this would be the greatest kernel of all time!!! Kmobs(Persionsown) UV kernel has some sick battery life but isn't overclocked and isn't an AVS kernel either. If you do this, that would be frakin awesome!!!!!!!!!!!
[Nexus One Android Development] wildmonks:
There's a good chance that it will not work. The wifi modules are specifically compiled based on the kernel code used and there should be good amount of difference between IR's source (which is what I use) and pershoot's source. When I get home tonight, I'll investigate this more. It could be that pervious kernel flashes are leaving behind misc modules that may interfere with the current kernel that's being used. If that's the case, I can make a quick update.zip that will delete the previous modules.

Actually I'm using his voltage settings :) He maybe using more unpublish tweaks to improve battery life.
[Nexus One Android Development] samir5421:
Ok. Hmmmm if there were a way to find out if kmobs' kernel is completely open sourced ;)
[Nexus One Android Development] zizoty:
How about a 950v version? That's the voltage that knobs used I think
[Nexus One Android Development] wildmonks:
Here's the update.zip file that I mentioned that will delete all the modules in the modules folder including the wifi module. After you apply this zip (via Amon_Ra's custom recovery) you will have to reflash the kernel so you'll get back the proper wifi module.

I kinda have my doubts this will fix your problem, but at the moment this is all I can come up with, sorry....

Delete_Modules.zip

Oh, interesting. Sure, I can wip up a batch of kernels with the minimum voltage setting to 950mV for you to test. Give me an hour or so to compile the kernels.
[Nexus One Android Development] THATTON:
I will test them out as well.
[Nexus One Android Development] wildmonks:
OK, here it is:

2.6.34_AVS-950mV_CFS_1113Mhz_TEST_062810.zip

2.6.34_AVS-950mV_BFS_1113Mhz_TEST_062810.zip

2.6.34_AVS-950mV_CFS_1113Mhz_NoAudBoost_TEST_062810.zip

I too will test out this kernel (950mV_CFS) overnight tonight and throughout the day tomorrow. Will report my findings.
[Nexus One Android Development] THATTON:
Thanks. I flashed it already and will do the same.
[Nexus One Android Development] SimFox3:
Thanks. I'm trying out the 950mv (NO audio boost) to compare my results too.
[Nexus One Android Development] damanrico:
Wow thanks a lot for the quick help. I really appericiate it.

Flashed the zip and kernel, will see if it helps.
[Nexus One Android Development] wildmonks:
Here's my report after using the 950mV kernel:

7 hours since unplugged (overnight drain) = 95% battery remaining

16 hours since unplugged = 69% battery remaining

Breakdown of phone usage:

Voice calls = 32%

Display = 27%

Cell standby = 20%

Phone idle =18%

Android System = 3%

What I did with the phone:

Not much, made 8 short phone calls, totaling ~15 minutes and downloaded a 21MB podcast and listed to it via bluetooth A2DP.

In comparison to the 925mV CFS kernel, this is about the same amount of battery drain for me.
[Nexus One Android Development] knightnz:
I'm looking into trying to do some C# development for Android, which requires running Mono in an android environment, as it turns out it looks like a Unioning filesystem (such as the recently added AUFS) is a useful thing to have when doing this semi cross-platform development (between Debian/Android). So it looks like it may be quite beneficial.

Saurik has a bunch of into on this at http://www.saurik.com/id/10

At any rate, it looks like getting a workable C# environment is gonna be a real headache, but it's the language my work is paying me to learn, so it seems silly not to try and use it.
[Nexus One Android Development] wildmonks:
Ah, very interesting read and very informative. I imagine it would take a great mind (that's definitely not me..) to combine the two environments together.