yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] zdiamant:
Yes I am getting to boot animation.. It just hangs there.. I have tried wiping cache and dalvik and taking battery out about 3-4 times and still freezes at boot animation. I will gladly try several more times if you think that will help. Interestingly, the boot animation starts in color and then transform into only white.

Thanks for all the work you and others like you do, as I know how to use your work, but no way could I ever originate it.

[recent edit] OK.. I'm perplexed now.. I tried again, clearing battery stats and cache. It booted up fine, however as soon as I touched the screen it froze and I had to pull out battery to reboot. After battery pull, it froze again at animation boot screen. Removed battery once again and this time it didn't even get to animation screen. Pulled battery again and this time froze at animation screen. Do I have to reset battery stats and cache everytime I reboot? Any other suggestions as I really want to try this kernel.
[Nexus One Android Development] fitsnugly:
psyq_2.6.33-2.diet_kernel_AVS_OC flashed fine here, no reboots!
[Nexus One Android Development] christiankk:
My advice (and I've been using these kernel since the beginning) is to keep trying, eventually it will work. Can't promise of course, but patience is the key here. (in my experience). I've seen the behavior you describe, many times - and I am yet to give up on an AVS kernel 8-)

For instance I've just installed the latest of intersects kernels. I had about 5 lock-ups, and maybe 20 reboots plus 4 launcher FCs before it started working for me.

I hope it will work for you.

BTW: I only wipe once.
[Nexus One Android Development] zdiamant:
Thanks for the reply.. I have been trying for almost an hour here with about 10 reboots. At this time, I have to have a working phone so I am reverting to non-AVS kernel.. I may try again tonight.
[Nexus One Android Development] fitsnugly:
and then bootloop out of no where :rolleyes:
[Nexus One Android Development] christiankk:
I've seen that too.

Somehow you can only say an AVS kernel is stable when it has been running for a while (an hour or so) :confused:
[Nexus One Android Development] die-hard:
Hi Ivan,

10x for your work.

I installed your latest avs kernel on latest cyano mod and work very good.

I have only one problem, when i install desire camera i lose your kernel futures and camera not work.

Now i have one question. Who can help me to come back to original camera app present in cyano mot 5.0.6?

Thanks in advance
[Nexus One Android Development] antoniouslj:
I've been using the AVS+OC and it has performed way above my expectations. I don't know what other optimizations you have put in place, but it seems kmobs has some catching up to do.

The kernel is extremely stable for me. I haven't had any lockups or force reboots and have been running it for the past couple days. It's by far the fastest feeling kernel I've flashed to my nexus. I'm also running CM 5.0.6, which could have something to do with the speed...

Keep up the good work!
[Nexus One Android Development] u3819013:
Re: Diet Kernel for Nexus One (CM 5.0.5.6), incl. undervolting+OC + TEST AVS SUPPORT!

8hrs on 3G Cyan 5.0.5.6-t2 with latest AVS not OV.

browsing and gaming.

it's work smooth no reboot.

thanks for great kernel.

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] Pochemuchka1977:
Is there any reason why dmesg does not work on latest AVS kernel ?

>adb shell dmesg

klogctl: Function not implemented
[Nexus One Android Development] floridasrt:
Been running latest avs-oc kernel for about 2 hours now. I flashed cyan's test2 ROM and then this kernel and its been running like a dream. Not a single bootloop, reboot, or hiccup yet. Keeping my fingers crossed and going to test out battery life. Awesome job you guys!!
[Nexus One Android Development] Ivan Dimkovic:
I have disabled debugging options from my kernels (for maximum speed / minimal size)

But I think I will at least produce versions with debug outputs starting from next release - so people could use them also for kernel debugging.

@persiansown,

To be honest, I have not experimented with manual undervolting since AVS - latest voltages I used are in my github.

But, I think that it would be a good idea to create one forum thread with posted and shared CPU freq/voltage table / tables, so we do not redo the same work all the time. Those tables could contain lowest voltages found to be stable for most people.
[Nexus One Android Development] christiankk:
.925 avs works for me.:cool:
[Nexus One Android Development] Ivan Dimkovic:
Looks like 0.85v is also stable for me.

I will do some more tests and maybe release a "download table" with multiple voltage ranges, so people could figure out what is the lowest stable voltage for them and use that one.
[Nexus One Android Development] floridasrt:
I'm using the AVS-OC kernel. Just took phone off charger so I can do some battery testing. After about a 30min of web browsing I checked to see whats been using the battery up the most.

Display - 67%

browser - 13%

SetCpu - 12%

Followed by cell standby and other things

So how come SetCpu is eating up so much battery? I have it set to max 998mhz min 245mhz. I have profile set up for sleep 245/245. Charging 998/245. CPU governor - on demand. I have option for "set on boot" marked and that's it. Anybody know why it would be using up so much juice?
[Nexus One Android Development] bobdude5:
does your latest kernel implement 8mb xtra ram hack?
[Nexus One Android Development] Ivan Dimkovic:
Actually - no, I forgot to add it.

I am putting it in now, and will release it along with more changes tomorrow.

Ivan
[Nexus One Android Development] decayed.cell:
1.06 OC AVS won't boot with HTC Desire ROM, rolled back to 1.05
[Nexus One Android Development] solidmac:
if i install this kernel will it be compatible with 5.0.5.3CM ?
[Nexus One Android Development] seanowns:
Yes, this is compatible with all of the CM mods.

Make sure to push the BCM4329 file to get wifi working.
[Nexus One Android Development] Ivan Dimkovic:
V1.07 is out :)

0.85v and 0.925v AVS flavors are available + 8 MB extra RAM and some other tweaks.
[Nexus One Android Development] pzumk:
the kernel without avs was "last modified 09.04.2010"

??
[Nexus One Android Development] Ivan Dimkovic:
Hmm

Maybe I did make some mistake...

I will remove the downloads and recompile all again.

@edit - done. Everything should be up-to-date now.
[Nexus One Android Development] xspeed9190:
how to we know the current cpu voltage. i am trying a few UV kernels and am trying to discern the diffirence. AVS/non AVS. Do you have to actively lower the voltage on the non AVS one. and is there a terminal command that i can use to check cpu voltage. my battery is terrible and need to see wich is best
[Nexus One Android Development] Ivan Dimkovic:
That's not going to be easy as there is no "standard" how to report on what each kernel is doing when it comes to voltage.

The only reliable way I can think of is to look at the voltage table for SVS (non-AVS) kernels directly in source.

My voltage table is on my github:

http://github.com/psyq321/nexus_one_kernel_additions/blob/master/acpuclock-scorpion.c

Check the clkctl_acpu_speed acpu_freq_tbl structure - and you will see voltages used for every frequency. You can do the same for other kernels by checking the same file (acpuclock-scorpion.c) in their respective sources.

For example:

{ [b]460800[/b], CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x0C, 0, [b]1000[/b] }
{ [b]998400[/b], CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x1A, 0, [b]1250[/b] },

This means that the kernel is using 1.000v for 460.8 MHz and 1.250v for 998 MHz

Etc...
[Nexus One Android Development] pzumk:
did you upload the right kernels now?
[Nexus One Android Development] Ivan Dimkovic:
Yep - everything should be online now.
[Nexus One Android Development] xspeed9190:
Re: [Kernel - 33.2][DIET] CM 5.0.6 based, 8 MB Extra, Undervolting, 1.1 GHz OC, AVS

ok so I'm looking for that file on.the phone and I can open it. cool. now I saw u recommend avs stock speeds for batt. does that still apply or should I use non avs uv. I have horrible reception at my house and my battery lasts about 16 hours while my employee has the same phone gets full service at home and his phone lasts 36 hours

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] Ivan Dimkovic:
No no, the file is not on your phone - it is in the developer's github. You need to look at the source code.

For example, this is the pershoot's acpuclock_scorpion.c (dunno if it is up-to-date) :

http://github.com/pershoot/nexus-kernel/blob/master/acpuclock-scorpion.c

This is mine:

http://github.com/psyq321/nexus_one_kernel_additions/blob/master/acpuclock-scorpion.c

Etc... To locate the source, check on the respective kernel thread / developer's webpage.

As for the AVS - AVS can undervolt the CPU much more than non-AVS. However, AVS is still not fully stable and can cause sequence of reboots. For some people it gets fully stable after few minutes of reboots.

Well, for this case I am afraid that undervolting of the CPU will not help much. Source of your battery drain is not the CPU, but the GSM radio, which has to boost the power to compensate for the poor reception. This cannot be "undervolted".
[Nexus One Android Development] www1:
IN my Nexus seem impossible to install avs kernel.

Reboot, frezee ecc... ecc.... I try all version by you and reven but no luck.

I try to wipe cache and battery stat but no luck.

I try also to wipe davilk cache with same result.

Any suggestion for have AVS kernel working on my N1?

I use cyanogen 5.0.6 test2 I use prevoius kernel on cyano 5.0.5.3 with no problem.
[Nexus One Android Development] xspeed9190:
Re: [Kernel - 33.2][DIET] CM 5.0.6 based, 8 MB Extra, Undervolting, 1.1 GHz OC, AVS

thanks Ivan I appreciate it help I knew it was a big waste with my reception but I was hoping UV could help a little

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] Ivan Dimkovic:
Unfortunately, there is no guide for AVS at the moment.

It either works, or it doesn't work :( We still haven't figured out what exactly is causing it to force reboots on some phones.

There are few possibilities:

- N1 bootloader is doing voltage changes which should be prohibited in case AVS is used... if that is going on we can't really do much until Google improves the bootloader and make it AVS-capable

or

- There are further changes necessary in the kernel code to make AVS work. Clock control code in the Code Aurora repository is quite different than in the Android eclair branch - maybe there are some things that we missed

or

- CPU revisions built in N1 are just not AVS compatible - but I find that quite unlikely
[Nexus One Android Development] www1:
:o

Thanks you

But I don't know if one previous release (I don't remember the number) work very well with cyabo 5.0.5.3 after I upgrade and reflash It doesn't work.

If I try other release doesen't work.

When I have time I try to downgrade to cyano 5.0.5.3 and retest all previous avs kernel to investigate.

:)
[Nexus One Android Development] dirwdirw:
850mv is not able to work for me. sequence of reboots on boot.

though i did not wipe anything

925mv seems ok.

245 460 1075 1136 is stable in "stress test" @ SetCPU

it seems 925mv does not include 8MB xtra ram.
[Nexus One Android Development] Ivan Dimkovic:
Yep, this is a known possibility for some CPUs. Some CPUs just can't handle such low voltage.

Please try 0.925v AVS version.

On the other hand, I am not really sure why is this happening - the purpose of the AVS is to probe for the lowest stable voltage. According to the spec, AVS should stop undervolting at the lowest voltage point just before stability is compromised.

So, if it would work as advertised - the lowest #defined voltage should not matter as AVS should automatically stop at the lowest stable voltage for each CPU.

But... this obviously does not work. Not yet, at least.
[Nexus One Android Development] seanowns:
Re: [Kernel - 33.2][DIET] CM 5.0.6 based, 8 MB Extra, Undervolting, 1.1 GHz OC, AVS

Got 850 working very well here. Not a single reboot or freeze yet
[Nexus One Android Development] dirwdirw:
wow, what a cpu you have
[Nexus One Android Development] u3819013:
mine too. :p
[Nexus One Android Development] dirwdirw:
did you do a wipe? or just flashed the zimage?
[Nexus One Android Development] jblazea50:
i have the 850 working as well...first i used adb to push the bcm4329 file, then went into bootloader and flashed the zImage...afterwards, i went into recovery and wiped the cache and that was it and it seems to be working fine so far
[Nexus One Android Development] serialtoon:
****ing epic. I was going to get that machine also but could not justify the price.
[Nexus One Android Development] Ivan Dimkovic:
Well, VPC-Z11 is indeed very expensive - but pretty unique in what it contains in a 13" package (Core i7 on 2.66 GHz, 512 MB Quad-SSD, 8 GB RAM, Full HD screen...) - but the price is really.... tough to swallow indeed. But it is very useful in compiling those N1 kernels - even during kernel recompile in Ubuntu VM, my CPU load is ~20-25% which is very nice :)

Back on topic - I just discovered even more ways to optimize the kernel and reduce its size slightly. I will be testing it tonight and release it tomorrow if it turns out to be stable.
[Nexus One Android Development] seanowns:
Re: [Kernel - 33.2][DIET] CM 5.0.6 based, 8 MB Extra, Undervolting, 1.1 GHz OC, AVS

pushed wifi then flashed kernel which I find more efficient. I Did not bother wiping cache.
[Nexus One Android Development] JHPadu:
psyq_2.6.33-2.diet_kernel_AVS_850mv_OC seem to be working fine on my phone too so far.^^

Only had a quite long boot cycle/bootloop where the "blue part" of Cyanogens bootanimation kept rebooting for a while (it did not reboot from the start).

After that I've had no freeze or reboot.
[Nexus One Android Development] MaxiJavi:
850 good for me too

Hi,

I am using the 850 OC, got a reboot right after flashing, but all good since.

I was running it at 1.1, but I am 960 ...

intersectRaven's 800 didn't work for at all.

I like the extra frequency steps in this kernel VS intersectRaven's Kernel.

Thank you !!
[Nexus One Android Development] gaxx:
how do you install it?

i get an error message when i try to install it from AmonRA Recovery boot saying there is no signature in the zip
[Nexus One Android Development] Clarkster:
Is this the reason for the string of reboots people get before it is stable? AVS tries something too low, the CPU halts and reboots, it tries another less lower one, crashes reboots, etc. etc. until it gets to a stable one?
[Nexus One Android Development] mohsin125:
I flashed diet_kernel_avs_oc_850mv and phone is running perfectly. didnt wipe any cache or anything, reboots perfectly :D...i ran the setcpu stress test at 1.1GHZ and it ran perfectly without errors. does that mean that 0.85v is running perfect on my phone?
[Nexus One Android Development] Docmjldds:
Same here. Pushed WiFi FIRST. Then flashed zImage followed by wipe of cache. Only concern was initially a longer boot time, but so far no hiccups at all, including running my Meridian music app and working out with a CardioTrainer app that had issues with other kernels here. Cardiotrainer uses GPS for logging my workout, which adds to stressing how this is working here. Using the 850mv_oc, setCPU setup with ondemand, set on boot. Profiles currently set charging and sleep 500max/245min and Power at max CPU 1113MHz. 268MB Free MEM with 18 processes running :D

Also, battery charging now with temp showing 31.7 degrees which is much cooler than my usual stock 34-36 degrees charging. Last but not least, gallery with 85 jpgs opens smoothly with no lagging. Have not seen this so smooth to date. Using CM 5.0.6-N1-test1....before I forget to add.
[Nexus One Android Development] Budske:
this will wipe the device?

im a lil worried
[Nexus One Android Development] St.Jimmy!:
It won't wipe your data.
[Nexus One Android Development] Budske:
sorry for all the asking, but im a noob

how stable is the avs one 925mv with oc?? i have the EPE54B nexus one (AT&T)
[Nexus One Android Development] Ivan Dimkovic:
Stability really depends on individual CPU.

Some people are able to run even 0.8v AVS kernels without problems, while some other people can't get any AVS kernels to be stable.

So, the only way to be sure is to try it.
[Nexus One Android Development] charnsingh_online:
i cant find the overclocked versions
[Nexus One Android Development] Ivan Dimkovic:
They are in AVS zip files - you can recognize them by directory name, containing "_oc" in the name.
[Nexus One Android Development] jlevy73:
Does the include the audio hack?
[Nexus One Android Development] Markdental:
+1

Also wondering if this includes the capacitive button fix...
[Nexus One Android Development] andythefan:
When I type: adb remount, it returns with "Invalid Argument"

What do?
[Nexus One Android Development] jlevy73:
Did you make sure to place the .ko file into the same folder where the adb.exe file resides?

Also, are you still in fastboot as it won't work while in fastboot.
[Nexus One Android Development] jlevy73:
I could be wrong Mark but I don't think the capacitive fix is related to the kernel (I think). I am running CM 5.0.6 test2 and capacitive buttons work fine no matter what kernel I use. I could be wrong of course just going by recent experience.
[Nexus One Android Development] Ivan Dimkovic:
- Audio hack is in, as it is part of CM 5.0.6 kernel

- Capacitative button fix - I also don't think that's part of the kernel

Expect some more goodies tomorrow - DMA speedup (from latest CM 5.0.6 repository), further unnecessary things thrown out, some kernel features configured for uniprocessor system instead of SMP thus saving on memory (and probably speeding things up) etc..
[Nexus One Android Development] jlevy73:
Thanks for the clarification.
[Nexus One Android Development] Archimago:
Thank you!

Just to add to the "thank you's" for all your work!

Running the 850 version with O/C. Pushed wifi after zimage flash, no wipe cache. Stress test stable at 1.1Ghz on one of the AT&T/Rogers N1's.

Looking forward to even more optimizations!
[Nexus One Android Development] jblazea50:
so with tomorrow's new versions of kernel, will it also include the 850mv
[Nexus One Android Development] Ivan Dimkovic:
Yes of course. I intend to keep 0.85v and 0.925v versions for now.

I don't know if 0.8v makes too much sense as it looks like it is unstable for most of the people.
[Nexus One Android Development] Ivan Dimkovic:
Could someone test this kernel?

It is non-AVS kernel with 1.1 GHz enabled, but it has lowered voltages for low frequencies down to 0.925v

If you want to test it, please report if you are seeing any problems.

Just ignore the kernel name (it has "avs" - but it is not)
[Nexus One Android Development] SimFox3:
I can confirm this too. What governor are you guys using?
[Nexus One Android Development] jlevy73:
For the governer setting for the AVS/OC 925 kernel what do you recommend?
[Nexus One Android Development] intersectRaven:
Thats basically what the ondemand governor is. It will ramp to maximum immediately then clock down afterwards if the application has finished. The conservative governor ramps up speed slowly. :)
[Nexus One Android Development] jlevy73:
This is a nice kernel. However, I find that it lags a lot more then say pershoots when pushed on 3D games like Asphalt.
[Nexus One Android Development] dirwdirw:
i push the .ko file firest, wipe cache, then flash 850mv.

still got a string of reboot on boot.
[Nexus One Android Development] dirwdirw:
i got A issue. 925mv is stable for night. but when i reboot the phone manually, it become unstable, got a string of reboot.

after several reboot. it get to destop, but Handcent get a FC .
[Nexus One Android Development] happyandy93:
tested the "psyq_2.6.33-2.diet_kernel_AVS_850mv_OC " version works 100% just wipe the battery and cache with the recovery after you flash the zImage and you'll be good to go, some may need to make 2 restarts or you phone may freeze a couple times on the "X" intro, dun worry just remove battery and turn er back on. :cool:
[Nexus One Android Development] 2000impreza:
I've been testing this kernel for the last few hours. Works great with no issues at all. It would be great is you incorporated the 0.925v into the non-avs version of the kernel. I'll probably run the kernel over the next few days and see if I run into any issues.

Just for comparison, I've run avs kernels and always seem to have issues during a reboot. Once it is booted up, they run great. However when it comes time for a reboot, its hit and miss.
[Nexus One Android Development] dirwdirw:
Re: [Kernel - 33.2][DIET] CM 5.0.6 based, 8 MB Extra, Undervolting, 1.1 GHz OC, AVS

+1

i met the same issue
[Nexus One Android Development] dandyd449:
Very nice, I would like to try out the 800 version sometime. How about uploading it?
[Nexus One Android Development] bobdude5:
850 is working beauitfully on mine..my phone is always nice and cold :) is the sound hack in this kernel?
[Nexus One Android Development] jlevy73:
Yes sound hack is included but I found it to be not as robust as pershoot's kernel. Just my two cents. The OP did a great job on this.
[Nexus One Android Development] r34p3rex:
Will definitely be trying this tomorrow :D Can't afford to have an unstable alarm clock for tomorrow morning :(
[Nexus One Android Development] big_adventure:
Hi Ivan,

I've run a few of your kernels - I've been running your 1.03 AVS OC kernel for a few days (maybe a week?), and it has been rock-solid, except for issue one, below.

I'm coming up with two repetitive issues, though issues that are difficult to log and send to you.

Here are the basics - I'm running CM 5.0.5.3 (though I noticed the same under 5.0.5.1). I'm running the latest radio.

In my office I get good signal, but in the bathroom or at the coffee machine, there is a dead zone that blocks service to any phone (iPhone 3G, BB Bold9K, Moto Milestone, Nexus One).

1. Sometimes, when I go into the afformentioned "dead zone" and come back to my office, the phone will lock itself into "no service" mode with 4 blank bars and an "X", and it will only come back if I reboot or go into and out of airplane mode. This happened with my iPhone, my BB, my Milestone and my Nexus (least with the BB, most with the Nexus). Unfortunately, with all of your kernels (1.0, 1.01, 1.03, 1.05 so far), when the service is dead like that, and then I go into and out of airplane mode, the phone reboots if it is not connected to a computer and in debug mode. It WON'T do this if it is plugged into the computer with ADB running or not, meaning logcat of the phenomenon is tough. This does not happen with a few other kernels I've tried, including CM's, IntersectRaven's and Pershoot's. I wish I could give you better feedback and a logcat. I'll keep trying to get something on this.

2. 850 crashes a lot on me, though I've only been running it for 45 minutes. Specifically, it doesn't like running out of radio range. I went into a "dead" zone and fired up my RSS reader. The phone rebooted 4 times in 10 minutes doing that, and then once again coming back to my desk while it was in my pocket. Unfortunately, I could not easily recreate the problem while connected and on-network - I let logcat run for 15 minutes, then stopped it, and two minutes later the phone rebooted itself while it was still plugged in.

I'd like to troubleshoot that further, but I'm supposed to be working and need to have a reliable phone, so I've installed the 925 version and will watch that (yeah, yeah, the irony of needing a reliable phone and therefore installing an experimental kernel is palpable - I get that).