yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] paulk_:
Kernels work on CM 5.0.6 test 2 and test 3 (these are what I've tried, didn't try it on test 1).

If it's a bootloop, it should be due to the AVS version you're trying. Try a higher one. I don't think that the phone should be checking for wifi immediately after booting, or anytime before it actually enters the OS. (correct me if I'm wrong)
[Nexus One Android Development] S_Dot:
intresting, tried it without pushing wifi still cuaght in boot loop!
[Nexus One Android Development] intersectRaven:
Try a higher voltage one if that will work. With AVS it's either a hit or a miss. :(

Yes it will. I'm actually running on the 5.0.6 now. :)
[Nexus One Android Development] S_Dot:
Also when I'm in fastboot and i type the adb command it says device not found
[Nexus One Android Development] S_Dot:
I thought it always worked, but it would be laggy when it starts up due to low voltage
[Nexus One Android Development] lore2486:
when in fastboot the comand is fastboot flash zimage zImage not ADB, also if you get into a bootloop try the next voltage i cant boot on 800 but 825 is bootable (stable for only 3 hrs) and 850 is the one i use. not all procesors are the same
[Nexus One Android Development] rcxquake:
That is because fastboot doesn't support adb. type "fastboot devices"
[Nexus One Android Development] S_Dot:
Still not working im all the way up at 875mV whats going on, anyone? im on enomther 181
[Nexus One Android Development] intersectRaven:
As I said, just test until the 925. If it still doesn't work, then AVS isn't for your N1. Some processors just don't like it for some reason. :(
[Nexus One Android Development] S_Dot:
finally got it working on 900mV :(
[Nexus One Android Development] S_Dot:
Turned out I was wrong still unstable.. even up to 975mv and when it starts it asks me to touch the android like a brand new phone and all these FCs appear...

too bad my phone doesnt like this kernel, i give up :(
[Nexus One Android Development] lore2486:
anyone running this kernel on cm 5.0.6 the actual stable release?
[Nexus One Android Development] jblazea50:
yeah, it is working fine so far
[Nexus One Android Development] lore2486:
so we stay with all the new neon optimizations and new things from 5.0.6 or does flashing this new kernel take all those away?
[Nexus One Android Development] intersectRaven:
As I understand it, the NEON optimizations are mainly located in the bionic part which is not in the kernel so it should still be there. :)
[Nexus One Android Development] lore2486:
thanks thats what i wanted to know, im new to the whole android platform, but so far im happy i switched from Iphone to nexus :D
[Nexus One Android Development] intersectRaven:
Welcome to freedom then! :p
[Nexus One Android Development] dahui9:
Hey IntersectRaven,

I'm running your 800 AVS kernel right now just flashed, I'm going to run this for a couple of days or more and see if I have any problems, if not I would like to talk with you about possibly teaching me where to undervolt the kernel a little more. (AS ALWAYS YOU ARE NOT RESPONSIBLE FOR ME ****ING UP MY PHONE) :p

I can be the guinea pig.

-Charlie
[Nexus One Android Development] paulk_:
Ooh I'd love to have this kernel undervolted to the same values as UV@Stockspeeds
[Nexus One Android Development] intersectRaven:
The hybrids are already undervolted at stock speeds. :)
[Nexus One Android Development] rcxquake:
I think he is referring to the kernel Undervolted @ Stock Speeds
[Nexus One Android Development] paulk_:
Umm yeah I was referring to that one. Should be more undervolted than kmobs values, though I've never seen the table for that one
[Nexus One Android Development] intersectRaven:
I see. I'll try asking persiansown for his values then. :D
[Nexus One Android Development] paulk_:
Sweet! More battery life ftw lol
[Nexus One Android Development] rjhay22:
Yo raven, is OP updated already? did you release your hybrid version yet? I musta missed you posting the links.
[Nexus One Android Development] dahui9:
yes I was reffering to UV at stock speeds, sorry I didn't clarify, I don't play to many games just surf the net, navigate, text and call mostly. Thats why I said I can guinea pig.

-Charlie
[Nexus One Android Development] intersectRaven:
I haven't announced them yet and also I'm trying to clean them up first since the coding was messy since I just coded it while the SVS kernel was being made as an afterthought. :D
[Nexus One Android Development] rjhay22:
Oh ok, I thought I was missing something here. Cool thanks, goodnight bro.
[Nexus One Android Development] Wysie:
The latest version caused my phone to hang at 800 again.
[Nexus One Android Development] vegetaleb:
Did you noticed a difference with battery when using screen @100% brightness?

I mean my battery can last perhaps 3 days if the screen is not lit but will drain 100x faster if I use the screen
[Nexus One Android Development] hah2110:
What is the consensus? What is getting the best battery life?
[Nexus One Android Development] nDrg:
Unlike other roms the wifi works perfectly on this. However I get regular reboots every 5-10 minutes using the 800mV version, should i try another?
[Nexus One Android Development] intersectRaven:
Try a higher one. :)
[Nexus One Android Development] hah2110:
Anyone using the new stable 5.0.6 with any of these?
[Nexus One Android Development] u3819013:
stable for a half day with latest 5.0.5.6-N1+825mV Hybrid
[Nexus One Android Development] christiankk:
hybrids running like a charm here.
[Nexus One Android Development] paulk_:
Yeah I am. For some reason battery life is still draining really fast even when I'm not doing much.
[Nexus One Android Development] hah2110:
Is this cause of CM or the Kernel you think?
[Nexus One Android Development] nDrg:
900mV works much better, cheers :)
[Nexus One Android Development] intersectRaven:
Updated!

20100416_2237:

Hybrid AVS:

800mV:

http://www.mediafire.com/?mnjmzmjvmyd

825mV:

http://www.mediafire.com/?4ndb4hghynz

850mV:

http://www.mediafire.com/?ko205md2mzn

875mV:

http://www.mediafire.com/?mmdmjzz3zm5

900mV:

http://www.mediafire.com/?ljm3rrzd2dm

925mV:

http://www.mediafire.com/?4mmjzvz1jmz
[Nexus One Android Development] nDrg:
I reckon this could be due to a kernel problem as I've had poor battery problems using the stock kernel on several CM versions. Now that I've flashed this it seems to have stopped, as my battery has remained constant over the past 30 minutes whereas I'd have lost around 5% previously.
[Nexus One Android Development] hah2110:
What did this update do?
[Nexus One Android Development] Daswolven:
Stable CM 5.0.6 running well on the 800mV. Tried the hybrid and got caught in boot loops. (Yes, followed instructions, and works fine with the non-hybrid.) I'll try the next hybrid update again, but in the meanwhile will be enjoying this.

Thanks for your efforts. :)
[Nexus One Android Development] paulk_:
No idea, haven't tested either for that long.
[Nexus One Android Development] intersectRaven:
This is the formal release of the hybrid kernel and cleaned up the hybrid code.

Have you tried a higher level?
[Nexus One Android Development] paulk_:
Are the bcm4329.ko files the same across all the versions? Going to try different levels and wanna know if I need to push it again

[EDIT] Interesting, the AVS 825 before the undervolting would give me a boot loop, but now I'm in the OS and it seems to be running fine. Great!
[Nexus One Android Development] Cheesebaron:
My phone keeps rebooting/freezing after a couple of days, is there anything I can do to help debugging this? Point me in the right direction and I can see what I can do.

I have tried the 1000mV and lower kernels and the problems persists.
[Nexus One Android Development] intersectRaven:
Unfortunately, AVS really is not that stable for some CPUs. Please try Ivan's or an SVS kernel for the meantime. :(

Yes they are the same for all versions. :)
[Nexus One Android Development] paulk_:
Wonder who's kernels are more undervolted between pershoot and persiansown
[Nexus One Android Development] paulk_:
Great, saves me a teeny bit of time :P
[Nexus One Android Development] Markdental:
any way to make a 950 volt version? When pershoot made a 925 there was some lag but now with the 950 it is completely stable.
[Nexus One Android Development] paulk_:
Ugh guess 825 isn't stable on my phone, getting reboots now
[Nexus One Android Development] DebauchedSloth:
875/AVS used to work for me. 875/Hybrid boot loops. :(
[Nexus One Android Development] acantril:
mmm did you disable voltage logging ? im catting /proc/kmsg and its now showing the voltage changes ?
[Nexus One Android Development] acantril:
ignore me... im being a retard :)
[Nexus One Android Development] intersectRaven:
No I did not. Your voltage must be holding steady if there is no AVS messages. Have you tried looking near the top for AVS messages? There should be at least some at the beginning of the bootup process. :)
[Nexus One Android Development] acantril:
So ive installed CM 5.0.6 and your latest kernel and im noticing something odd. While asleep i have the CPU set to 256/256 with setCPU and before the Voltage would stay at 800mV with the 800 kernel.

Now its flapping

<6>[ 1080.821502] AVS setting V to 800 mV @2

<6>[ 1085.766052] AVS setting V to 1225 mV @20

<6>[ 1085.806213] AVS setting V to 1200 mV @17

<6>[ 1085.826171] AVS setting V to 800 mV @2

<6>[ 1087.137664] AVS setting V to 1225 mV @20

<6>[ 1087.157684] AVS setting V to 800 mV @2

this is pretty constant....
[Nexus One Android Development] intersectRaven:
That's odd. It shouldn't fluctuate if you've set it on SetCPU to be constant. Maybe the sleep settings are different? I believe SetCPU has category settings which can differentiate between different states of the phone. :confused:
[Nexus One Android Development] acantril:
Theres deffo something in CM6.0.5 thats using CPU every second or so the CPU usage spikes when its awake.

If i set min cpu on 256 and max on 998 its constantly

256, 998, 256,998 etc etc

Trying it in sleep.
[Nexus One Android Development] intersectRaven:
Updated!

20100417_0039:

Hybrid AVS:

800mV:

http://www.mediafire.com/?yhzd0ktnniw

825mV:

http://www.mediafire.com/?niujzgglomy

850mV:

http://www.mediafire.com/?yn5zekzyczm

875mV:

http://www.mediafire.com/?owldymlkmmz

900mV:

http://www.mediafire.com/?jqcmimkakio

925mV:

http://www.mediafire.com/?24hzmcgxmyz

*I used a different compiler with the last version. I forgot to restore the default android compiler when I triggered the automaker script. Only found out while looking at the SetCPU information. Sorry!!! :o
[Nexus One Android Development] intersectRaven:
I noticed that as well when I tried replicating your problem. Odd. Anyways, just keep the governor on powersave when you're not going to use it heavily. :)
[Nexus One Android Development] hah2110:
Will these fix 5.0.6 spiking issueS?
[Nexus One Android Development] intersectRaven:
No. This has nothing to do with the spiking issues. That is something running in the background which is triggering every second or so. :(
[Nexus One Android Development] paulk_:
Hmm.. Set my speeds to 245/245 in setcpu for normal use (no profiles) but I still see it going up to 20

[EDIT] Oh wait that is super stupid of me. Setting for normal use doesn't work because I have a charging profile. duh.
[Nexus One Android Development] rjhay22:
Yo Raven, so this hybrid kernel is both AVS and SVS correct?
[Nexus One Android Development] dictionary:
Changelog:

20100417_0039:

- new experimental AVS/SVS hybrid kernel which combines the powersaving capabilities of both AVS and SVS kernels by capping the maximum voltage for each frequency (SVS) while allowing dynamic undervolting as well (AVS)
[Nexus One Android Development] rjhay22:
Thank you, *smacks my forehead* woulda been easier if I just read the OP. lol.
[Nexus One Android Development] sir*mez:
Hybrid Kernel, sexy as hell!!
[Nexus One Android Development] rjhay22:
Coming from the 850mV reg to the 850mV Hybrid I notice a few things:

Device seems stable, no random reboots so far, but battery seems to be warmer thus draining the battery quicker than the previous kernel and gives out a few errors.

binder: release proc 2874, transaction 175246, not freed.

binder: 187: binder_alloc_buf, no vma

msm_pm_wait_state(2,0,0,0) failed 11001

msm_i2c msm_i2c.0: error, status 43c8

msm_i2c msmi2c.0: Error during data xfer (-5)

AVS: Voltage cannot get high enough.
[Nexus One Android Development] jlevy73:
Off topic, what helix launcher are you using for Enom's Rom?
[Nexus One Android Development] rjhay22:
Using NexTheme goodies5 over Enoms so whatever launcher he has. Forcecloses quiet a bit though. Have you tried it?
[Nexus One Android Development] dyndragon:
AVS & SVS seems to have fixed my problems with this kernel and my phone! Previously, not even the 1000mV kernel would stay booted for more than a few minutes on my phone, but now I can actually launch and stay running for more than 3 minutes!
[Nexus One Android Development] r8zer:
so, is this hybrid, better for people, in terms of temps, and battery life, im on previous and my temps range from 20 to 25*c. and battery is near to 2 days light use.

FANTASTIC!!

any input from the new hybrid kernel is very much welcomed.
[Nexus One Android Development] rjhay22:
It seem to give me the opposite, when I ran Enom and the regular AVS my batt temp went all the way down to 19-22C, when I ran Cyan and the regular AVS it was around 25-28C.

Now, Enom = 24-28C / Cyan = 30-32C.

My device probably just cant handle the pure awesomeness! lol.
[Nexus One Android Development] dictionary:
Enom disappeared though, lol. I'm loving CyanogenMod though. Beautiful. I'm on a different kernel, and running steady at 30.2
[Nexus One Android Development] r8zer:
lol, im on cm5.0.6 test 3 and i only reach 25+ when browsing heavy or gaming, is there big differences in the hybrid compared to the avs, in terms of the batt and temps,

also, just wish my damm phone would accept the 800mV avs, these xtra 50mV's are killing me.
[Nexus One Android Development] intersectRaven:
But you still suffer from reboots right? AVS might not be for you if so. :(

There is a major difference compared to regular AVS. Although whether or not that applies to you varies. :)
[Nexus One Android Development] r8zer:
just tried your hybrid 850 and just would reboot, but your avs on 850 works perfect for me.

3>[ 199.284088] msm_pm_wait_state(2, 0, 0, 0) failed 11001

<6>[ 199.284088] msm_sleep(): msm_pm_wait_state failed, 11001

<6>[ 200.176208] AVS setting V to 975 mV @11

<6>[ 200.464324] do_imprecise_ext: ADFSR = 0x00000004

<6>[ 200.464447] do_imprecise_ext: DFSR = 0x00000436

<6>[ 200.464691] do_imprecise_ext: ACTLR = 0x000c0037

<6>[ 200.464813] do_imprecise_ext: EFSR = 0x00000004

<6>[ 200.465026] do_imprecise_ext: L2SR = 0x00010000

<6>[ 200.465148] do_imprecise_ext: L2CR0 = 0xc0050f0f

<6>[ 200.465301] do_imprecise_ext: L2CPUESR = 0x00000020

<6>[ 200.465515] do_imprecise_ext: L2CPUCR = 0x000000e0

<6>[ 200.465637] do_imprecise_ext: SPESR = 0x00000000

<6>[ 200.465881] do_imprecise_ext: SPCR = 0x0000000f

<6>[ 200.466003] do_imprecise_ext: DMACHSR = 0x00000001

<6>[ 200.466125] do_imprecise_ext: DMACHESR = 0x00000000

<6>[ 200.466735] do_imprecise_ext: DMACHCR = 0x0000000f

<6>[ 200.466857] do_imprecise_ext: TCSR_SPARE2 = 0x0000a037

<1>[ 200.467102] Unhandled fault: imprecise external abort (0x436) at 0x4814b00

what does this mean, this is from the AVS 850 kernel.

now it wont give same error.
[Nexus One Android Development] Gimpeh:
Same thing happend here. Had to up it to 900.

Edit: Nevermind, it just froze on 900 as well.

Edit 2: It's freezing on all of the new kernels. Weird as the test hybrids worked fine.
[Nexus One Android Development] Daswolven:
Back on 2.6.33_AVS-800mV_20100417_0039 which runs great on my N1. Lower Hybrids worked without problems when i could get running, but got sick of fighting boot loops to get there every time. :)
[Nexus One Android Development] intersectRaven:
That's odd. No code changes were introduced with the newest kernel 20100417_0039. I'll just have to credit AVS for the instability then. :confused:
[Nexus One Android Development] sir*mez:
I don't know but I'm liking the new hybrid. I haven't had a problem yet. Ill update with more info later tonight or tomorrow. Testing to see how long I get.
[Nexus One Android Development] intersectRaven:
I'm recompiling a new kernel now which has more debugging features so you can report more if ever. :)
[Nexus One Android Development] intersectRaven:
Updated!

*Please tell me if the kernel size is too big for your device.

20100417_1112:

Hybrid AVS:

800mV:

http://www.mediafire.com/?mion2fyjdry

825mV:

http://www.mediafire.com/?utrqnyj5znt

850mV:

http://www.mediafire.com/?dqnghwgonmz

875mV:

http://www.mediafire.com/?imdhmym0zgd

900mV:

http://www.mediafire.com/?mlywwyjmnxj

925mV:

http://www.mediafire.com/?dg2q5ngm2dq
[Nexus One Android Development] hah2110:
What did this update do? In your opinion, what is my best bet for battery life on CM 5.0.6?
[Nexus One Android Development] hah2110:
What kind of battery temps is everyone seeing? How are people getting like 22c? On pershoot I was around 30, on the newest 850mv (just updated), I'm at 25/26c.
[Nexus One Android Development] hotweiss:
Will try it, what were your last omptimizations? Selected? Is your kernel just as undervolted as Ivan's?
[Nexus One Android Development] intersectRaven:
I still use kmobs values...as for the optimizations, they're selected and not the full O3 level since I can't make a properly functional kernel with it that still has the desired features...:)
[Nexus One Android Development] intersectRaven:
I'll see if it's interesting enough... :p
[Nexus One Android Development] hotweiss:
Maybe this can help you:

http://xdaforums.com/showpost.php?p=6024383&postcount=45
[Nexus One Android Development] www1:
When I try to push latest versione I have this error

sending 'zimage' (2313 KB) OKAY

writing 'zimage' FAILED (remote: unknow fail)
[Nexus One Android Development] britoso:
Removing EXT4 filesystem support would be dangerous as CM 5.0.5 includes it. I dont recommend it as I use apps2SD :)
[Nexus One Android Development] hotweiss:
What OS are you using?
[Nexus One Android Development] www1:
Win seven 64.

I have change about 25 kernel and no problem.

Now when I try to repush any kernel I have the same error :confused:

I think this kernel have made a error.

I can't also use adb in windows (after yes).

It's a kernel bug.

I reflash my N1 with cyanogen and I return to use Adb on W764, now I reflash with another kernel and it works.
[Nexus One Android Development] big_adventure:
Hi,

I ran this Kernel (.33) version for a couple of days. It was rock solid and stable. I had no problems with the Desire Cam, trackball wake, setcpu, etc. I'm running CM 5.0.5.1 (love me some V8) with the 4.04.00.03_2 radio.

I got rid of it, though, as I think that the consevative power manager introduces just a hint too much hesitation. Flinging between screens in the launcher (I do have a stack of widgets running), going in an out of apps, etc., is just a little less than instant. I also had a strange problem where touch buttons would highlight in orange on the screen, but not actually select until the second touch.

The kernel sequence I've used:

CM 5.0.4.1

Kmobs UV kernel

CM 5.0.5

CM 5.0.5.1

Pershoots OC/UV

Desire (modded CM5.0.5.3)

IntersectRaven .33

Now I'm on Ivan's Diet kernel.

IntersectRaven's was perfectly clean, just a bit too slow for me.
[Nexus One Android Development] intersectRaven:
that's also what I thought which is why it's still in the kernel...

I think this is a bad block issue in some N1s which causes kernels which are bigger than usual to fail writing...you'll have to wait for when I can get this smaller since I've pretty much hit a brick wall already in terms of what I can remove from the kernel...must read more... :confused:
[Nexus One Android Development] intersectRaven:
that's fine...the conservative governor can be laggy when CPU needs to be heavily utilized... ;)
[Nexus One Android Development] big_adventure:
Yep, that's why I moved on yet again. I'm going to have to build the toolchains and roll my own I think. Thanks for all the effort!

To anyone reading my previous commentaries, please don't take what I wrote as an attack on intesectRaven or his kernel - it does EXACTLY what he advertises, and seems to do it perfectly, it just wasn't for me.
[Nexus One Android Development] intersectRaven:
I'm thinking of redoing this to actually have ondemand defaulted and just include ALL the power governors so users can actually choose which governor they want using either SetCPU or the terminal method. Anyways, I'm currently busy analyzing which option I can remove from the kernel to minimize its size to work even on those N1s whose boot partition are smaller due to "bad" areas. ;)
[Nexus One Android Development] daedelus82:
If you could add the other governors that would be great!

I love your kernel but don't really like the conservative governor all that much.
[Nexus One Android Development] gettingtired:
That's a great idea! :)

looking forward to it
[Nexus One Android Development] intersectRaven:
Studying AVS now. I'm interested in more power savings! Good thing there seems to be a lack of updates in Cyan's and Android's kernel repositories. ;)

Will be releasing a .32 kernel with AVS soon. Just recompiling from scratch now without my debugging extensions for AVS testing. Test seem to indicate it's working (just put a ton of pr_info so I can see if its going inside the AVS codes necessary for voltage tuning...) so I'll see what the community feedback will be. :p
[Nexus One Android Development] britoso:
What does AVS, SLAB, O2 stand for? and any luck turning the book animation off?

having all governors available will be sweet!
[Nexus One Android Development] intersectRaven:
Updated! Will work on .33 version tomorrow! :)
[Nexus One Android Development] intersectRaven:
AVS stands for Adaptive Voltage Scaling which is a method to lower or increase your CPU's voltage based on several factors in order to get the maximum power savings for the frequency without sacrificing overall stability. SLAB is a memory management technique for allocating memory. O2 stands for the optimization level used while compiling the kernel. I can't get into details but if you want to know more, just google "O2 optimization" or "SLAB allocation". :D
[Nexus One Android Development] hotweiss:
Thanks, I will try it. There's no better way to start a day, than with a fresh new kernel.
[Nexus One Android Development] intersectRaven:
More debugging options were left in the kernel to provide more information. Also, I changed some other things. Please see the front page for more info. :)
[Nexus One Android Development] intersectRaven:
They might be in airconditioned rooms or somewhere comparatively low temperature environment. In comparison, when I'm at work I usually have 21.3 temps while left idle but at home, I get 30 - 35 or even 37! :)
[Nexus One Android Development] hah2110:
I haven't been able to keep up with every post on here. Which kernel seems to be yielding the best battery life? Is it true some are seeing better battery life WITHOUT AVS? Any experience on MCRs ROM?
[Nexus One Android Development] paulk_:
I usually get 25 degrees in an airconditioned room when my phone's been idle for quite a while. Not sure how other people manage to see such low temperatures!

On another note, installed the latest kernel by adb pushing, rebooting in bootloader, flashing then using fastboot reboot and my phone rebooted itself after the Cyanogen 'X' animation the first time. After that it was ok. This is the first time it's ever happened to me while using raven's kernel.
[Nexus One Android Development] paulk_:
Haven't tried a Sense rom before, but battery life should be better with AVS for raven's current kernel, as it caps the voltage at non-AVS levels, but after that the AVS allows it to scale down to even lower levels if the processor allows it.

Previously there was no cap (or only a slight cap) on voltage for AVS kernels, so that might have led to worse performance than non-AVS if you use your phone a lot (don't allow it to be in standby much).