yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] dictionary:
mine does, lol.

There is no way to have consistent life from one phone to the next, because we all have different usage, different radios, live in different areas, have different settings, have different signal strength, live in warmer or colder environments, etc.

Now if you take two N1's, side by side, same network, same mods, etc, I'm sure there would be a consistent drain between the two, if nobody called or texted either, yada yada.
[Nexus One Android Development] MaxiJavi:
Actually my N1 isn't that consistent from one day to the next :-)

As I try different kernels and background programs the battery life changes ...

However, I do consistently get well over a days full use of the phone with some pretty thorough usage. And from reading the forum it seems as if everyone should be able to do this, and if not, they should first check they don't have a bad battery, and then check they don't have a bad phone.

These kernels are great, and if you follow the instructions and advice on this forum you CAN get the great battery life ...

The constant moaning helps no-one.
[Nexus One Android Development] hah2110:
I'm not looking to moan. I am a very technical guy and don't like the QA issues with this device, albeit I love the phone. I have put two N1s STOCK (besides unlocked bootloader) next to each other and closed all apps and they drain slightly differently. I get about 16 hours of moderate usage with these new kernels. Right now I'm on 2.6.33.2-cyanogenmod kmobs@ubuntu #3.
[Nexus One Android Development] MaxiJavi:
OK ... Sorry, but I now have to agree with everyone else ... As for the "very technical", all the evidence is to the contrary.

Of course they are going to drain slightly differently, first of all not every battery is the same, secondly not every bit of silicon is the same, and thirdly there are several hardware revisions out there (and that is with me trying to buy your story 100%).

If there is a large divergence between the two phones of the same hardware revision and with equivalent batteries conditioned in a similar way, then you'd have a point. But we know there are plenty of bad batteries out there, and it would appear that there is some bad hardware too (although much less that I have seen for equivalent hardware - iPhones and the like - Do your homework on the whole QA thing).

So no, you are still moaning and driving us all nuts ...

This is my last post as I for one have had enough.

Back on topic ... Thanks Ivan, I look forward to your new kernel (!) :-) :-)
[Nexus One Android Development] BlueScreenJunky:
Re: [Kernel - 33.2][DIET] CM 5.0.6 based, 8 MB Extra, Undervolting, 1.1 GHz OC, AVS

glad to hear you're still working in this kernel ti make it even better :-)

also, as far as battery life is concerned I think saying "I have x% after y time of z usage" is pointless because the percentage is neither accurate nor linear. So IMO the only really useful info is how much time it lasts with a full charge before it turns of and you can't use it anymore.
[Nexus One Android Development] adam18488:
Re: [Kernel - 33.2][DIET] CM 5.0.6 based, 8 MB Extra, Undervolting, 1.1 GHz OC, AVS

flashed this kernel last night...been using heavily since ...I only seem to get random reboots when using the browser. will this eventually become stable? oh its the 800mv or whatever it is..
[Nexus One Android Development] jtn7040:
what is the avg battery life change after flashing this kernel now?
[Nexus One Android Development] joeavery2:
Just giving some feedback, I'm running the Avs, .850v kernel. Cm 5.0.6 with setcpu. Most of the time it is stable but I have had a few times where it would not wake up and a few where it just crashed and rebooted, sorry no logs. I watched one time as it broke the threshhold for setcpu (50%) and it just crashed. I don't know if this is an indicator as I watched it break another threshold later without failure. I may switch to the 925 mv. Just to see if it is an issue with the voltage or setcpu.

Also as a rough guess I would say I'm doing 10% better battery. My phone doesn't get warm as it did before. I notice more variation due to how I set the screen brightness and if I use it for websurfing or just siting in my pocket as a phone.

If I don't really use it except phone calls and text, I can have as much as 70% battery at the ends of a 12 hour day. Obviously there is know way of quantitizing in real world use so take it for what it is worth, I would say it did make an improvement in battery life and I am happy to use it, so thank you for the work.
[Nexus One Android Development] Ivan Dimkovic:
Finally... V1.09 is out

Now, it is using Hybrid AVS with implemented fixes done by IntesectRaven for stability.

No need for non-AVS version anymore. Going down to 0.8v

There is also AVS+OC (which goes down to 0.925v ATM, but this will be fixed soon)
[Nexus One Android Development] Breece:
Installed like a charm :) Thanks!
[Nexus One Android Development] yiannit:
is there anyway to see the voltage?
[Nexus One Android Development] Ivan Dimkovic:
Unfortunately no as the debug info is completely disabled.

I have to think how to enable partial debugging output just for the voltage stuff...

By the way, I just updated the OC version - now this one also scales down to 0.8v
[Nexus One Android Development] jblazea50:
pushed the ov version; no issues at all; everything is working as it should so far

quick question, is all the voltages undervolted, even the maximum voltage? i know for pershoot's OC/UV kernel, everything is undervolted except for the 113mhz, so wanted to know if this kernel is also similar in that regard
[Nexus One Android Development] Ivan Dimkovic:
This is how it works:

For frequencies up to (and including) 998 MHz:

- Voltage goes down to 0.8v, there are also upper limits for each frequency

For frequencies above 998 MHz (overclocked):

- Voltage goes down to 0.925v, upper limits are also per frequency

How low it will go is purely CPU dependent and I guess the kernel will behave exactly the same as intersectRaven's as the algorithm is the same.

There is only one limitation for frequencies above 998 MHz, and that is that AVS will not even try to go below 0.925v. I had to do it as I encountered some weird slowdowns which are sign of instability
[Nexus One Android Development] jlevy73:
That makes sense as I notice when I push your AVS OC kernel on CPU intensive games and apps, there is a noticeable lag. This kernel excels in battery life no doubt, but performance wise still has some issues IMO. What's strange though is benchmark scores for this kernel are higher than other OC kernels :confused:
[Nexus One Android Development] jblazea50:
great, thanks for cleraing that up for me
[Nexus One Android Development] dirwdirw:
this version works well for me.

i reboot the phone and no issue!

i set setcpu with min128-max1113 now.
[Nexus One Android Development] jblazea50:
Ivan, i had a question regarding the minimum scale. I noticed that the minimum it 128mhz, now if i set the minimum to 128mhz for all the profiles in setcpu, will there be any issues?

thanks
[Nexus One Android Development] intersectRaven:
Finally! I can now point people who're looking for OC to your kernel! :D
[Nexus One Android Development] dirwdirw:
Re: [Kernel-.33.2][DIET][04/25] CM 5.0.6, Stable Hybrid AVS, Optional OC

i have no issue so far .
[Nexus One Android Development] Wysie:
Ivan: Are you still using NEON? According to pershoot and based on the feedback I saw in his thread, VFP is recommended instead. :)
[Nexus One Android Development] fitsnugly:
OC AVS 800 not stable for me, the 925 one you posted early was, any way to have a choice?
[Nexus One Android Development] redraiderj:
Hi Ivan, can you please offer the download link for 1.08 psyq_2.6.33-2.diet_kernel again? I've tried to use intersect's hybrid avs kernel but there's something wrong with the phone's network, so I turned to your 1.08 kernel. Today, I noticed that you update it to 1.09, but I haven't noticed that you apply intersect's avs, so I flashed it, and encountered the network problem again... I saw the log in terminal, it seems that something went wrong with the "registering phone to network". I'm not sure the root cause but I just want to flash back to 1.08, thx a lot. Here's my post in intersect's thread.
[Nexus One Android Development] Ivan Dimkovic:
Okay, so things to do tonight:

- Re-release the SVS kernel for people that can't use AVS

- Re-release the AVS with low voltage cap @925v for people that have issues with 0.8v

- Check NEON vs. VFP performance and use the fastest
[Nexus One Android Development] maximus0206:
Unstable

Coming over from IntersectRaven's stable 800mv hybrid AVS...which was completely stable for me, absolutely no reboots at all (used his kernel for a couple of weeks now, always with AVS), so I know my CPU can handle 800mv, but I've already had a couple of reboots from your kernel when running at 1.113 Ghz, so maybe the 925mv for speeds above 998 isn't enough?

Might try 950mv?
[Nexus One Android Development] jlevy73:
According to his github @ 998 he is using 1.25V. At 1.113ghz he is using 1.275V which is stock voltage and more than sufficient for that clock speed.

Try wiping Dalvik cache then reinstall the kernel and see if that helps.
[Nexus One Android Development] Wysie:
Ivan: Reading pershoot's thread it's not just about VFP being faster. Apparently NEON causes some problems too.. Not too sure of the details but thought I'd let you know.
[Nexus One Android Development] jlevy73:
VFP is just much smoother than NEON is. I didn't really notice a speed difference as much as I did a seamless experience.
[Nexus One Android Development] Ivan Dimkovic:
Hmm

That is strange because I don't think too much of kernel code is using floating point anyway...
[Nexus One Android Development] Ivan Dimkovic:
Yes and that's the maximum voltage (1.275v)

Lowest voltage is determined by the AVS scaling algorithm.

Note that 1.275v is actually not really enough for 1.1 GHz, but it happens to work on nearly all CPUs. AVS >will< complain that 1.275v is not high enough for that frequency, and I guess their hardware is probably right :)

What I did to make OC version work is also to apply minimum voltage per each frequency (for everything below 1 GHz it is 0.8v and for everything above 1 GHz it is 0.925v) - this solved the "slowdown issue" at least on few phones I tested this on.

However, it looks like some people will need low threshold of 0.925v so I'll build that, too.

Ivan
[Nexus One Android Development] Buck Shot:
someone said flash in recovery... it failed everytime. I really want this kernel, but i am totally lost on how to do this. Esp where u have to type all of these commands. I dont even know where to do that. Yes im rooted and all that w/ morphs so im sure i can do this. Any noob guide or video. lol I need images...
[Nexus One Android Development] fitsnugly:
From the FIRST POST:

[power off your phone and boot into fastboot]
fastboot flash zimage zImage
[reboot]
adb remount
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
[Nexus One Android Development] jlevy73:
Cool, thanks for explanation :)
[Nexus One Android Development] bskim23:
flashed the rom last night before going to bed and have been running it with no problems since 7:30 AM. it is now 11 am and with some browsing, texting, emailing, and just plain messing around with the phone, im at 90%. on intersect's kernel i get slightly better battery drainage probably because this one is OC and requires more juice. still much better than stock where with the same use, i would lose more than 10%/hr using the phone for the same things
[Nexus One Android Development] Buck Shot:
if i knew how to do this i wouldnt be asking. How do I fastboot? Hold down power and trackball hit bootloader?

fastboot flash zimage zImage --- where do i do this

adb remount

adb push bcm4329.ko /system/lib/modules/bcm4329.ko -- what the???? lol
[Nexus One Android Development] Ivan Dimkovic:
V1.10 is out

- Floating point mode is now VFP

- AVS is now offered in two options

Option 1 - minimum voltage goes down to 800mv

Option 2 - minimum voltage goes down to 925mv

Each option has normal and overclocked versions.

For people that asked for a non-AVS version, could you try the AVS 0.925v kernel? It should behave very similar to the old SVS with 0.925v limit.
[Nexus One Android Development] b1337:
two words: search function
[Nexus One Android Development] Buck Shot:
typical dickhead xda move.
[Nexus One Android Development] Enndr:
Not really dude. If you cant be self sufficient with this stuff you'll brick your phone eventually and complain about it...

"Oh no one helped me"

"Oh screw Google/HTC for not giving me a free new one"

You're a vet, so am I. Do you want someone to give one of your privates an M4 or M249 without making him or her know the fundamentals and how it operates?

Crawl, Walk, Run.... Search, Read up and be semi-self sufficient man. You should know whats thats about. Unless you were a POG maybe. :rolleyes:

(At least I think you're a vet from your avatar)

Edit: Oh yeah and the same two words as above "Search Function," Private. :)
[Nexus One Android Development] Buck Shot:
def not a POG... 11B. I have searched and tried to figure out how to fastboot but i cant find it. I wouldnt of gotten this far with the rooting and morphs if I havent. Its not hard to point someone in the right direction. Ive read the noobies guide on adb/fastboot. Doesnt tell u how to do it tho. I read "How to update Kernel" doest tell me how to fastboot and type commands....
[Nexus One Android Development] jblazea50:
Ivan, the kernel is working great (using 800mV OC). Haven't noticed any lag or anything unusual.

Quick question: In the OC kernel, i noticed that the minimun scale is set to 128mhz, while the normal kernel, the minimum is 245mhz. Now, any reason for the difference? Also, if i were to set the minimum to 128mhz to all my profiles in SetCPU, will it make any difference?

Also, any possiblity of incorporating this kernel with Termana's .34rc3 kernel?
[Nexus One Android Development] Ivan Dimkovic:
Ouch I think I know where is 128 MHz coming from...

It is actually a bug, not really a feature. Will be fixed asap :)
[Nexus One Android Development] jblazea50:
oh i see, glad i posted it and it'll be fixed

btw, any chance of incorporating all your features in your kernel to termana's .34rc3?

thanks and looking forward to the fix
[Nexus One Android Development] Ivan Dimkovic:
I can definitely give it a try :)
[Nexus One Android Development] Markdental:
+1 to termana's kernel. I have heard nothing but good things.

Would love to have an AVS/UV/OC version of this.
[Nexus One Android Development] MaxiJavi:
128 ?

But what will happen ?

I am using it for my sleep profile, and it seems to work (?)

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] bskim23:
+1

I have also set it to 128-245 for sleep/standby. By a bug do you mean it will not be running at 128?
[Nexus One Android Development] jmotyka:
:D:D

I just left kmobs kernel for this 925mv anything below 900mv i noticed isnt juicing the radio enough and dropping my 3g down to edge way to often. So with that being said i think that the problems people were having with loosing 3g back when the nexus first started shipping was that the power to the radio was to low. Now im on this kernel and love it.
[Nexus One Android Development] stuff:
I agree. I also was getting random unstable reboots with the previous OC version, leading me to believe the processor is not getting enough power, forcing it to crash. Hopefully I don't get any unstable problems this time. :)
[Nexus One Android Development] bskim23:
is this why when im using my phone for a while or downloading from the market my connection seems to drop from 3g to edge?

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] jlevy73:
No, the kernel has no effect on the radio.
[Nexus One Android Development] bskim23:
is there a reason why my text msgs arent working after flashing the new 800 ockernel?

EDIT: nevermind there's something wrong with tmo network in my area -_- i have service and can use the internet but i cant make calls or send texts!

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] schahr01:
Ivan, What was reason to ditch NEON for VFP? I don't claim to be an expert on floating point hardware extensions :-) but the articles I have read seem to indicate that NEON is a pro not a con.

"We would therefore strongly advise the Android team at Google to update the NDK to a new version of GCC so Neon floating-point code can be written to take full advantage of the CPU in the Driod & Nexus."

Quoted from:

distinctivegame.wordpress.com/2010/02/09/dd-tech-talk-1-nexus-versus-iphone-3gs/
[Nexus One Android Development] Wysie:
schahr01: Something with CM5.0.6 causes NEON to be weird (not too sure of the specifics, cyanogen and pershoot had a mini-discussion gg on on Twitter). Anyway, from this page onwards: http://xdaforums.com/showthread.php?t=633238&highlight=NEON&page=156 There's a bit of info scattered here and there.
[Nexus One Android Development] MaxiJavi:
Ummm ... I have had two reboots running OC over a 12 hour period :-(

Lets try with the stock speeds.
[Nexus One Android Development] Ivan Dimkovic:
@MaxiJavi,

Are you using 0.8v OC or 0.925v OC? You might want to try the higher one firt.

As for the 128 MHz clock... well, apparantly it does seem to work, BUT it is using a different clock source (AXI)

I don't have the snapdragon datasheet, so I am not really sure if this is recommended.

But it does look it is working...
[Nexus One Android Development] B1ny:
Re: [Kernel-.33.2][DIET][04/26] CM 5.0.6, 8 MB+ RAM, Hybrid AVS **STABLE**

I have been running for over 4 hours with 128 mhz as the lowest setting for all profiles on the 800 oc kernel. Everything is perfect :)
[Nexus One Android Development] dixxa:
Any chances of you using that universal update.zip like intersect raven or koush?

Many people now use the xda app and we don't always have a computer nearby ;)
[Nexus One Android Development] xzr3b0rnzx:
i have a problem with the 800mv avs kernel..when i flash zimage i failed .. cmd prompt said "remote: not allowed"

*it's ok now working fine .. tried flashing with my desktop.. was using laptop just now
[Nexus One Android Development] jblazea50:
Ivan, i'm not sure if this is true, but someone stated that Kmobs said that at low voltages (his 850mV), the battery life is shorter compared to his 925mV becasue at such a low voltage, the radio draws too much power.

Can you look into that? thanks
[Nexus One Android Development] MaxiJavi:
@ Stock speeds I was OK ...

Going to try the 925 one at OC now :-)
[Nexus One Android Development] MaxiJavi:
The source of that info is :

http://twitter.com/kmobs

Hope it helps ...
[Nexus One Android Development] jblazea50:
thanks.....
[Nexus One Android Development] The_Serious:
Very interested in that too )

Please, could you also release your Kernels in form of Update.zip so that we could flash it through Recovery. Dont have PC allways at hand, and i flash things on the go usualy. It gives a realtime chance to compare different things and lure out bug sources for example. Thanks!
[Nexus One Android Development] Cal-El:
+1 :)10 Chars
[Nexus One Android Development] bskim23:
oops wrong kernel
[Nexus One Android Development] jlevy73:
Ivan do you plan on updating this to the .33.3 kernel?
[Nexus One Android Development] schahr01:
Perhaps just write this off as someone new to the android forums "not getting it yet" :-) but Ivan puts a lot of work into this kernel but a lot is also derived from the work intersectRaven and others have contributed as well. Why not merge the work and offer less kernels? I believe GIT (github) makes this easy. The pool of kernel testers are more concentrated with less kernels.

Or is this an application of evolution theory and the best kernel will eventually emerge (survival of the fittest?)?
[Nexus One Android Development] St.Jimmy!:
I've been waiting for this! Thanks definitely trying tomorrow!
[Nexus One Android Development] intersectRaven:
I disagree with this. Each kernel produced is a product of a developer with a specific goal in mind. I for one don't like OC so I don't produce or support it. Other developers are then encouraged to produce their own versions in order to satisfy their own needs or the needs of others. :)
[Nexus One Android Development] B1ny:
Re: [Kernel-.33.2][DIET][04/26] CM 5.0.6, 8 MB+ RAM, Hybrid AVS **STABLE**

Flashed the 925mv oc 128mhz yesterday. And today was the first time I have managed to get through the 9 hours at work, without having to connect the charger, I even have 16% juice left :)

I didn't have any calls but usage was pretty much average. This is my first AVS, and 128 mhz kernel, and this is a major improvement for me. It seems the biggest savings comes from when the phone is asleep.
[Nexus One Android Development] mikechw:
Re:

i tried both raven's kernel n this oc kernel both for a few days. dont know why raven's kernel feels smoother.
[Nexus One Android Development] Daswolven:
Been awhile since I played with these. :) Back off of stock now that I have my replacement phone in, and will see how the 800 OC works for me. I like the concept of AVS, but have always been a little buggy on it. :P

Edit: Just noticed in SetCPU that autodetect now shows a min of 128? Not sure if this should be the case, but going to read some posts up and see.

Edit: Edit: NVM. :)

Edit: Edit: stability was an illusion. Small assortment if miscellaneous freakiness.
[Nexus One Android Development] SeriousX:
What do u mena by smoother? Desktop switching is smoother?
[Nexus One Android Development] mikechw:
I tried both kernels...

Ivan's kernel should be faster, since it is OCd and dieted. But sometimes I feel there are slowdowns when I am switching applications. I feel that Raven's kernel is more responsive... don't know why.

:confused:
[Nexus One Android Development] Nighthound:
[Kernel-.33.2][DIET][04/26] CM 5.0.6, 8 MB+ RAM, Hybrid AVS **STABLE**, Optional OC

I think it's fine as it is currently. Basically there are 4 kernel variants now: oc/non-oc, avs/non-avs. The other stuff like vfp, audio fix, etc are already largely shared between the kernels. The variants give users the option to choose what they want to use.
[Nexus One Android Development] BlueScreenJunky:
I don't what what I'm talking about either, but I think Ivan's kernel is a also very stripped down version of the standard kernel, lacking among other things many debug features in order to make room for optimisations.

While it makes no difference to people like me, I guess other people (developpers ?) actually need these features and use other kernels.
[Nexus One Android Development] Ivan Dimkovic:
Yes - the purpose of "my" kernels is to strip them down so they are as light and fast as it gets. Also, there is an OC available for AVS for people that feel that they need those extra 100 MHz but still wish to have AVS as well. Not everyone needs that exact feature set, and hence the need for more choice.

Lack of debugging features makes these kernels not suitable for developers (or even some advanced users that want to be able to see what is going on on the kernel side) - when I need to debug I am also switching to debug info as well.

Now, that said - this weekend I am planning to upgrade to .33.3 and also test .34-rc5 and see how it goes - if it is sufficiently stable I will release it as well

I wish I can do this faster but the regular work is really preventing me from doing it... maybe I'll take a vacation to do more android development :)
[Nexus One Android Development] jlevy73:
Like all things Android things evolve. .33.3 is now a stable update to .33.2 and the changelog has plenty of optimizations that could benefit what Ivan is doing as well all those using this kernel.

I agree that most of the items are shared between kernels as these are based on Cyanogen's github. What makes this kernel and Intersects unique is the AVS.

My point about .33.3 is, if there is a better base out there why not use it.