yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] Docmjldds:
Ivan....absolute great work here. Looking forward to even more tweaks.

Cold is nice. I went as far as obtaining an RMA on my N1 back in late January for excessive heat, especially during charging. I decided to wait it out, based on the many user reports on the N1 feeling hot during charging etc. Just adding a quick follow up of 100% rock solid stability for last 24 hours, with amazing battery life using the 850avs version. 54% battery time after heavy duty use yesterday including running music app for a solid 3 hours non stop simultaneously with a Cardio function application employing GPS.
[Nexus One Android Development] MaxiJavi:
Other voltages ?

850 seems unstable for me, 925 is rock solid.

Would it be nice to try a 875 or a 900 ...

Thank you very much either way :-)
[Nexus One Android Development] danielherrero:
850 is working perfectly for me. I could make work correctly other AVS kernles, but this works like a charm ¡¡

Thanks
[Nexus One Android Development] r34p3rex:
Flashed the 850mv AVS kernel, 10 minutes stress test passed! :D No reboots at all

Excellent kernel!
[Nexus One Android Development] RieGo:
I'm using this one right now and i like it very much. Maybe you could make also a 850mV version of this? This is the only stable one for me (even on booting) except for the default kernels. I really like you work!
[Nexus One Android Development] Ivan Dimkovic:
V1.08 is out now

- Non AVS kernel is now undervolted down to 0.925v

- Further kernel tweaks

- Some more compiler optimizations
[Nexus One Android Development] jlevy73:
Do these additions apply to the AVS kernels as well or just the non-avs one?
[Nexus One Android Development] Ivan Dimkovic:
Changes apply to all kernels.
[Nexus One Android Development] HackDown:
Whit this kernel (very nice, thanks bro) I lost percentuage for battery meter :(
[Nexus One Android Development] Markdental:
Josh, have you tried the AVS kernel? If you have, how was battery life vs pershoot?

I had major issues with the other AVS kernel, going to try this one soon though.
[Nexus One Android Development] b1337:
avs has better battery savings than non-avs in my experience, also just try each update as they come out dont be such a scaredy ;)
[Nexus One Android Development] Markdental:
lol, well honestly, the other AVS was so unstable, it wouldn't make it past the boot animation.

I really want to try AVS, but I think I need to wait for it to be a bit more stable. It has to have quite a bit better battery life for me to switch.
[Nexus One Android Development] b1337:
i had stability problems with intersectravens and early ivan kernals but the updates and proper wiping of caches and letting it boot a couple times its been smooth sailing with 36-48 hour battery life compared to 12-24 with non avs
[Nexus One Android Development] loganno:
sorry I'm new to flash the kernel I wanted to know:

I try this without AVS, or the one with AVS?
[Nexus One Android Development] Docmjldds:
By chance are you in the Dental world. Retired after 20 years, just outside of Las Vegas. WRT battery, the amount of savings is unbelievable. Been out and about here last 6 hours or so. Several phone calls, texting etc. and listening to music, and I show 87% battery available. Going to update to the latest 1.08 just posted (850avs_oc)
[Nexus One Android Development] danielherrero:
latest 850 mV version was unstable for me. Many reboots so came back to the previous version (8 hours ago). Looking forward next release :)
[Nexus One Android Development] MaxiJavi:
Weird ... This latest version (1.08), actually works for me at 850 ...

Not only that, it absolutely screams along :-)

The difference in speed is noticeable.

I wiped cache/stats before flash.

Thank you !!!!
[Nexus One Android Development] Docmjldds:
No stability issue here. I did NOT wipe cache this time. (Forgot in haste of wild expectation:D) Made no difference. I did follow my first method of pushing the .ko first, then booted to fastboot to flash the zimage. No boot loops. Also, no issues with battery gauge as reported by another user here. All is well after 15min of stress testing.
[Nexus One Android Development] die-hard:
I installed 850mV but Launcher freeze
[Nexus One Android Development] stryker759a:
Is there away to go back to the stock kernel after i installed yours?
[Nexus One Android Development] die-hard:
U can backup your original zImage and .ko modules. In this way u can revert all modify
[Nexus One Android Development] die-hard:
I quote myself ;)

System work fine now with kernel@850mV
[Nexus One Android Development] jblazea50:
Ivan, any chance of putting out one at 800mV and 825mV?
[Nexus One Android Development] stryker759a:
How would i got about doing that? Since i have no originally nandroid back up that works. For some reason my main gmail account wont send any emails it just stays in the outbox. The solution i have found for my other gmail account is to delete it but i dont know how to delete my main account the phone says it has to be wiped or something along thoose lines. Also my nandroid backups are fcked up they fail when i try to do one.
[Nexus One Android Development] loganno:
what is better than no AVS or what to 850mv?

I put that without AVS, and that's fine. But what attracts me with AVS and 850mv! HELP ME!
[Nexus One Android Development] Docmjldds:
Trying to figure out what Gmail accounts have to do with Nandroid backups that aren't up to snuff. If you are trying to revert, why not use a zimage file that did not cause you issues and simply flash from fastboot. Once you have the phone settle down when booted up, then push a .ko file associated with the image, to get wifi back. You shouldn't need any backup to do this. I have to ask, how old are the Nandroid backups, and have you ever simply run a test of restoring one?
[Nexus One Android Development] stryker759a:
They are my backup from rooted and unlocked before i pushed the cyanogen rom. I have restored a back up or two but for some reason my back up of stock rom doesent work i will try the new release of this when i get home.
[Nexus One Android Development] Docmjldds:
Did you wipe all the data, caches, etc BEFORE trying the Nandroid backups. If not, then you should try that. As a rule of thumb, I always peak at my backups prior to trying anything experimental. Then I run a backup again, before I install whatever. Better safe than sorry. I guess I inherited this habit from running perpetual ghost images of my PC setups. (I switch between Acronis and Ghost. Both work pretty foolproof on total image restores, which is almost what we are doing here) I stress almost, BTW.

Best place to start over is from this link which has references to all ROMs :D

http://xdaforums.com/showthread.php?t=654869
[Nexus One Android Development] r34p3rex:
Guess I spoke too soon!

850mv worked for about 3-4 hours (100% stable, stress tests passed, no problems). But soon after, it began freezing and rebooting every 2 minutes. Dropped the 925mv kernel in and everything is working like a charm!
[Nexus One Android Development] stryker759a:
Doc that thread you linked me to just forwards me over to http://www.modaco.com/ it does not link to any thing. My question is when the new cyanogen rom comes out will i be able to just flash the new rom onto my phone since i have this kernel? I currently have the latest cyanogen rom.

Thanks,

Jason
[Nexus One Android Development] stryker759a:
i am running this kernel	psyq_2.6.33-2.diet_kernel.zip but my max cpu speed under set cpu is 998 and you say it wil be 1.1 and that we are suppose to set it to 998mhz. Is there any way on the phone that will show that i have that kernel installed ?
[Nexus One Android Development] paulk_:
You can, flash the new Cyanogen, but you will have to reflash and repush the kernel as flashing a new ROM will overwrite the kernel.

You should be able to move the slider up to 1.1? Not sure though, I haven't tried the non AVS kernel myself, though the folder inside the zip says it's OC.

Don't think there's any hard evidence that you have the kernel installed unless you're using an OC kernel and can set the CPU speed higher than 998, though I could be wrong.
[Nexus One Android Development] jlevy73:
Did you set up SetCPU to autodetect? If you didn't unintall SetCPU, reinstall and choose autodetect and NOT the Snapdragon option. If you installed the OC kernel it will tell you max is 1.1ghz
[Nexus One Android Development] MaxiJavi:
I spoke too soon too ... Same problem ... And solution :-)
[Nexus One Android Development] stryker759a:
Thanks i uninstalled it and reinstalled it and set it to auto it went to 1.1 and I set it to 998 thanks for the help.

Jason
[Nexus One Android Development] paulk_:
Ack completely forgot to ask if you'd set it to auto, sorry. You don't actually need to reinstall, you can simply press the menu button while in the main setcpu screen and use that option to choose the device or auto selection.

Just started trying this kernel last night, the last AVS 850 (stock speeds) was stable all night, installed the latest AVS 850 (OC) this morning and it's been stable for me. 1.09pm my time so that's roughly 5 and a half hours.

[EDIT] Just to mention that I've been using persiansown's UV@Stockspeeds and I don't really see a difference between the 2 (in terms of battery life) so far. Will report back at the end of the day.
[Nexus One Android Development] big_adventure:
Nearly 24 hours now of heavy use on the 925 AVS OC kernel, and all's well. I have not managed to crash it or crash any app even once. This was after bunches of crashes on 850. This is on the 1.07 version on CM 5.0.5.3.
[Nexus One Android Development] danielherrero:
I ve resintalled again latest 850 avs oc and works perfectly. No reboots or freezes. Thanks¡¡¡ :)
[Nexus One Android Development] Docmjldds:
Just logged on and saw your issues well covered by others here. Using the autodetect for setCPU is probably the one "gotcha" most users seem to miss. Kind of counter intuitive to not choose the snapdragon choice. Glad all is well again for you.
[Nexus One Android Development] Docmjldds:
I was using the UV@Stockspeeds and had horrible crashes on my N1. It would work if I would only be using one app at a given moment, but if I tried any multi tasking such as running music concurrently with browsing or any other app, it would freeze up or just go wonkie for lack of better terminology. So far, ever version of 850avs has worked flawlessly for me.
[Nexus One Android Development] zsutomato:
bad luck...

after serval time reboot my N1 succeed boot up and run smooth. But I forgot to put the bcm4329.ko back to it.

Then I push the file back to directory, reboot, after that, my phone continue reboot and reboot, sometime hangup at X, never succeed finish the boot up anymore.

I tried about 30mins still can't make it. Final I flash the kernal w/o AVS, it's ok now.
[Nexus One Android Development] paulk_:
I never had any crashes with UV@Stockspeeds, but I've had 1 crash with avs 850 so far. Other than that it's been stable
[Nexus One Android Development] Docmjldds:
It seems that there is some quality control for lack of better terminology WRT to hardware/CPU etc in these units. There is a variation in part numbers I have seen, but trying to put 2 + 2 together on this to come up with definitive cause and effects is impossible. As of today, I have one small inconsistency that has cropped up. If I turn the phone off and reboot, it freezes when it gets to the desktop. Have to pull the battery to reboot. But then on reboot, all is well. Go figure :confused:
[Nexus One Android Development] big_adventure:
Just to see what was what, I installed Cyanogen 5.0.6 test 2 and the 1.08 AVS/OC kernel. Ooooh, not so good for me - at first, it was great, but once it lost signal once, it had real problems establishing network connections when I went back into a "known good" area (it would show just bars, with no network type or arrows, OR it would think it had a connection, but would just send and send and send, never receiving anything back).

It was OK on Cyan's stock kernel, though not perfect. I then flashed the 1.08 kernel here (925, AVS, OC) and at first it had real network problems, and then it started getting more and more likely to crash (over the span of about an hour and a half of testing). Eventually, I restored back to 5.0.5.3 and then flashed on the 1.08 AVS/925/OC kernel, and everything is happy now. So the problem seems to be in Cyan 5.0.6 for me, and exacerbated (quite seriously) by the something in the AVS kernel.
[Nexus One Android Development] die-hard:
I installed Ivan kernel @850mV. Who work with this kernel + JIT?

IS this stable?
[Nexus One Android Development] pzumk:
just to let you know:

the newest non avs kernel works great
[Nexus One Android Development] Stea1thmode:
out of interest, what ROM are you using?
[Nexus One Android Development] dirwdirw:
i tried 925mv twice.

it had the same issue. it worked great when i first installed the zimage, it was very stable on Stress Test @SetCPU. after i push .ko file and reboot, i had the same problem as you.
[Nexus One Android Development] jblazea50:
i'm using the 850mV kernel with JIT...flashed the kernel last night around 6pm and no reboots yet

usually i get one or two reboots during normal usage, but nothing major
[Nexus One Android Development] kraftwerk2020:
850 wth AVS has been stable for about a 36 hours

Just had my first lockup. Battery life has been very good. I don't know how to pull the logs from the phone, but if it would help and someone can tell me how I can post them.
[Nexus One Android Development] hotweiss:
I am very happy with 1.08 running at 850 MHz. It has only crashed once right after the installation. So far after that it has been stable. I use Cestos (a game) to check the kernel's stability, as it really behaves erratically with AVS kernels. There have been some occasional video anomalies, but nothing too big.

PS-can you please enter the version number in your thread title...
[Nexus One Android Development] seanowns:
Nevermind. Holding off with said statement
[Nexus One Android Development] pzumk:
That means setting the overall thing to 1113/245 governor keeps it at 245? and on demand balances it between 1113 and 245 like I want it (since its set to 1113/245)

Edit // I always set everything to "on demand" btw.

Only my battery profile is 500/245 governor
[Nexus One Android Development] persiansown:
It doesn't seem like a good idea to have kernel debugging stripped out as well an experimental lower overclock. Not all instability manifests itself the same way and you might not be able to detect that the hardware is unstable without the debugging.

Also you said yours was UVed more. Out of curiosity, more than whose?
[Nexus One Android Development] Ivan Dimkovic:
More than pershoot's published settings on his github:

I'll publish my table after I do more tests - I guess it would be helpful to other kernel devs.

I am building new build now - with conservative governor built-in, too - and I am also trying to get last bit of optimizations.

As for the debug settings, unfortunately they had to go in order to enable even more agressive code optimization. Too bad that Nexus One current configuration won't accept 2.5 MB kernel image.
[Nexus One Android Development] pershoot:
if your looking at my source, it is more then just the table of frequencies (and their corresponding VDD) which lends itself to the scale up/down and VDD that has been decided upon, in each step. a function has been re-written to give you the whole freq. table and also to disable those that have been defined as such, etc.

so if your using the stock board file (which says to only give highest freq. at said VDD), then you will need to make adjustments in your own file to attenuate for this. you can certainly look at the table i use as a guide, but things will change with the stock board file.
[Nexus One Android Development] Ivan Dimkovic:
Thanks pershoot,

I just noticed that as well - I will make the necessary change so all the frequencies are used.

Unfortunately, enabling aggressive inlining increases the zImage to 2.8 MB :( This will certainly not fit... so back to default inlining, then.
[Nexus One Android Development] pzumk:
I just notice the newest setCPU uses "powersave" instead of "governor" :P

Using your _xtra Kernel now, could you give us 998 back? :D
[Nexus One Android Development] Ivan Dimkovic:
Ok,

Fixed the table lookup bug - and also added "Conservative" governor for people that want to use it!

Agresive inlining had to go - 2.8 MB zImage will not flash on N1. I'll see if I could get rid of more unnecessary options but this does not seem too likely at this point.
[Nexus One Android Development] hotweiss:
I will pull your config and see what I can suggest to trim the kernel down even more. I trimmed the Magic kernel down to 1.5 mb's. It shouldn't be too much trouble to cut another 300 kb.
[Nexus One Android Development] Ivan Dimkovic:
I'm open for suggestions :)

If you're OK maybe the best would be to discuss them on this forum, so everyone could learn something new...
[Nexus One Android Development] persiansown:
That reminds me.. I need to release my table. Mine is more UVed than his.
[Nexus One Android Development] jlevy73:
Ivan great work however I am seeing a lot of stability with both of the kernels you posted. Had about 5 reboots in the last hour (one was playing Asphalt 5, another google nav, playing music, browser). I know that comes with the jit territory just sharing my observations.

I noticed that it doesn't play nice with K-9. I would get emails but notifications only showed up 50% of the time.
[Nexus One Android Development] Ivan Dimkovic:
I am almost 100% sure that the JIT is the reason for your problems.

I cannot use JIT (using Desire ROM) so that kinda prevented me from using it too much - but I remember the old CM 5 pre-release days when I used it and same things occured.

If you want to be sure - try eliminating JIT first, and see if the problems stay... if yes, I guess you will need to use the "normal" kernel which is just slightly undervolted.
[Nexus One Android Development] jlevy73:
It is definitely JIT but that being said you are definitely on the right track. May not be able to make it perfect but it certainly does show what the N1 is capable of doing. Thanks, I look forward to future revisions to this
[Nexus One Android Development] Gilg@mesh:
can someone make a .zip file so I can flash the bcm4329.ko file please?
[Nexus One Android Development] Ivan Dimkovic:
Hmm, did anyone try LZO compression for the kernel? I don't know if it is supported...

Heck.. I'll give it a try :)
[Nexus One Android Development] hotweiss:
If it's based on 2.6.33.1 source, it should be supported.
[Nexus One Android Development] jlevy73:
Because this release is experimental, I believe the OP wanted a barrier so that not everyone could just install it. But if you read through the OP, there is a very good description on how to install everything.
[Nexus One Android Development] Ivan Dimkovic:
Nah, LZO compression just made it bigger... 2.4 vs. 2.2 MB

Too bad there is no LZMA...
[Nexus One Android Development] jlevy73:
That's too bad.
[Nexus One Android Development] RieGo:
just wanna bring this up again:

I worked with your tweaked non-AVS kernel since it's release (because AVS is very unstable for me, even on 1000mV), and it's just perfect..

But could you please make a second version with 850mV minimum? That would be really great! :)
[Nexus One Android Development] pzumk:
please just open your eyes a bit more :)
[Nexus One Android Development] Stea1thmode:
hey man, I got it the first time round. Some peeps dont update their sigs, thought your were one one them.;)
[Nexus One Android Development] Ivan Dimkovic:
I can try - but this is something that might not work. You see, AVS does dynamic undervolting.

So, imagine that your phone is stable @0.850v at, say, 400 MHz - but only until CPU load is below 30%... this can happen, everyone knows from the PC "stress testing" that overclocks / undervolts show signs of problems when CPU is under load.

AVS can detect this, and safely (heh) raise voltage to 0.875v or even higher.

Now, if we configure SVS (non-AVS) to use 0.850v for 400 MHz, if CPU gets into situation to be @400 MHz with >30% load - you'll get into trouble.

And the problem is - this is all so dynamic, and it depends on the CPU make, current temperature... I think the best solution is to make AVS stable :)

But until then... I'll see what I can do.
[Nexus One Android Development] Docmjldds:
<<So the problem seems to be in Cyan 6.0.6 for me, and exacerbated (quite seriously) by the something in the AVS kernel.>>

Maybe the difference in test1 vs test2. I'm still on #1 and no problems to speak of.
[Nexus One Android Development] RieGo:
oh, I see... thx for the explanation.

AVS is more than I thought it would be :)
[Nexus One Android Development] hugonz:
Actually, my understanding (I'm a professional electrical & electronics engineer) is that AVS changes voltage primarily in response to temperature, which changes performance characteristics of the silicon. Process variations (sample differences between two copies of the same CPU, e.g. from different batches and so on) also have a large effect; the AVS system (in theory, and in other SoCs like the OMAP3430) can correctly handle these variations too, but of course process parameters don't changes anywhere near as dynamically as temperature :-)

Also, people who have experience overclocking or under/overvolting desktop CPUs should know that the low-power silicon process used for these sorts of SoCs is quite different to the high-performance process used for desktop/laptop CPUs and GPUs. Importantly, low-power silicon can be damaged (albeit very slowly, over a process of tens of thousands of hours of operation) by overclocking at stock voltages, through a process of electromigration....

To all the people testing AVS kernels by stressing your phone with games or benchmarks, also stress it by letting it get cold (put it in a ziplock bag in the freezer for example) and see if it's stable during rapid temperature changes (pull it out of the freezer and start running your benchmark/stress tests). Hold the back part below the battery under a hair dryer for a bit or leave it in the sun and see how it handles above-average temperatures.
[Nexus One Android Development] Ivan Dimkovic:
AVS is explained very nice in this patent:

http://www.faqs.org/patents/app/20090031155

It is quite complex and it relies not just on temperature, but also on the load (not just the load factor, but also types of instructions - see 0024 for example)

Back on topic - I managed to kick even more stuff from kernel which is not needed (this never ends :) ) - and I am testing it now. If all goes well, I'm releasing it tomorrow.
[Nexus One Android Development] paulk_:
After using it for a day, I've found that the AVS@850 seems pretty stable for me. Had to pull the battery once, and got a reboot 2 or 3 times. These all seemed to occur when trying to do things fast when coming out of sleep mode (245/245 in sleep mode, 998/245 normal), guessing that the voltage can't ramp up fast enough?

[EDIT] Sorry if this has already been asked, I've read through the whole thread briefly, but how is the AVS max voltage compared to the non-AVS voltage? When the AVS is 850, the minimum voltage is 850 (I believe) and is the maximum voltage the same as the non-AVS version?
[Nexus One Android Development] jsiripra:
also having trouble coming out of sleep (have to pull battery), but otherwise very stable. running AVS 850 OC
[Nexus One Android Development] MaxiJavi:
Re: [Kernel - 33.2][DIET] CM 5.0.6 based, 8 MB Extra, Undervolting, 1.1 GHz OC, AVS

I had to go to the 875 kernel from intersectRaven because the phone would crash randomly while sleeping on the 850.

I got the feeling that 245 under load may have been the culprit. Shame, as this kernel seems faster ... Any chance we can get a 875 build ?

Thanks !!

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] paulk_:
Could be because you have an app running during sleep which requires a lot of CPU power?