yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] fcisco13:
could it be that this kernel is for a nexus one???

it can also be that you are not flashing it trough recovery???
[Nexus One Android Development] maxisma:
This is an old thread. Also this is a Nexus One kernel.

Your bootloader is not unlocked.
[Nexus One Android Development] seanowns:
Are you charging this via a computer? I noticed this with all newer kernels on a windows vista computer I use at work that obviously does not have android SDK installed. I had to purchase a wall charger for work... Same issue though where it shows a charge light, but does not really charge. The computer also has trouble even seeing the phone and only works maybe 1/10 tries.

My phone is charging absolutely fine via wall/car charger with this kernel.
[Nexus One Android Development] Ivan Dimkovic:
Yes, there is overclocking support.

This is a "development" effort - trying to get most out of the compiler optimizations and kernel configuration.

In the few days, if everything works OK I will also publish the compiler switches as well, so other developers could integrate them in their kernels.

The goal, of course, is to have our phones running as fast as they can :)

By the way - I just released v1.02 with yesterday's tweaks - seems to be working fine here :)
[Nexus One Android Development] hotweiss:
Just tried 1.0.2. It is working perfectly. Are you still going to make that super optimized version?
[Nexus One Android Development] Ivan Dimkovic:
Yes I will - at least I will try, but I just wanted to release yesterday's work which has been tested :)

I think it is not a good idea to break USB tethering, or - at least, there should be a separate version if Ethernet drivers are really taking too much space (which I doubt)
[Nexus One Android Development] hotweiss:
Can we follow you on Twitter?
[Nexus One Android Development] spyz88:
I second that question. This kernel is EXCELLENT.
[Nexus One Android Development] spyz88:
Ivan, is the xtra kernel the one that was super optimized for your particular phone? I'm getting the greatest battery life with that one. I just want to know which one to keep an eye on. Thanks
[Nexus One Android Development] pzumk:
(the xtra is the one which is more undervolted)

Getting great battery life with the xtra kernel too :)
[Nexus One Android Development] bouyark:
Excellent kernel

Same here with excellent battery life with the xtra kernel without sacrificing stability and speed. Ivan, thank you.
[Nexus One Android Development] zarskee seven nine:
i'm having the same problem with my phone not charging
[Nexus One Android Development] aonavy:
i tried the UV kernel and things seem to run fine. Im using CM 5.3. In setcpu i see 1.113ghz but when i run cpu benchmark the most it reads is 738mhz.

this has happen with all OC kernels.

Any help?

looks like this..

http://i289.photobucket.com/albums/ll204/SubyWill/d2eea0aa.jpg
[Nexus One Android Development] hotweiss:
That happens with all oc'd kernels. Just slide the max speed level around.
[Nexus One Android Development] aonavy:
i did. setcpu read 1.113.

cpu benchamrk read 738
[Nexus One Android Development] www1:
It's Normal that in "psyq_2.6.33.1_oc_uv_normal.zip" in N1 I see psyq_uv_xtratest@ubuntu#27?

Can have a kernel with stock speed?
[Nexus One Android Development] DebauchedSloth:
Dropped this in on top of one of the other uv kernels, saw immediately better battery life - the slope of my JuicePlotter curve got a lot less steep. Impressive!
[Nexus One Android Development] Ivan Dimkovic:
Uhh... I am not exactly a big twitter fan but I'll think of that :)

I am studying the adaptive voltage scaling in ChromeOS kernel right now...
[Nexus One Android Development] aonavy:
:o anyhelp
[Nexus One Android Development] Ivan Dimkovic:
I'll check it out !
[Nexus One Android Development] fitsnugly:
I think I read somewhere it was a bug in the cpu benchmark app, don't quote me tho...
[Nexus One Android Development] Ivan Dimkovic:
I am trying to build-in the AVS support...

I think I did what is needed, but it looks pretty unstable ATM unfortunately - maybe I am doing something wrong.

I am going to re-enable debug print options so this could be traced
[Nexus One Android Development] aonavy:
i read that too..you think im at 1.113ghz still?
[Nexus One Android Development] Nauren:
SetCPU tells me I'm still at 1.113 after redetect.
[Nexus One Android Development] Ivan Dimkovic:
Added Experimental AVS (Adaptive Voltage Scaling) Support based on latest Qualcomm code!!

AVS should automatically undervolt CPU as much as possible.

This is >very experimental< -and it will need lots of testing

This kernel is available separately and this one has debugging options enabled. Also, I had to kick-out loop unrolling from AVS kernel, as there was no space for it
[Nexus One Android Development] aonavy:
what does that?

what does cpu benchmark tell you?
[Nexus One Android Development] Ivan Dimkovic:
Added source code with AVS patches, so other kernel developers could use it if they wish.

Note, this is still early code with one ugly hack...
[Nexus One Android Development] Ivan Dimkovic:
Ouch... looks like zImage is too big for your phone! That is the problem I am talking about - there is a limit for zImage + initrd.gz (I believe 3 MB total?)

Which ROM are you using?

@edit - ah, it was a wrong cmdline :) That's better...
[Nexus One Android Development] Nauren:
CPU Benchmark says 738mhz
[Nexus One Android Development] :
SetCPU is on a constant 1113 for me. Never goes down :confused:

Using the ondemand Governor.

What Governor are we meant to be using with this kernel ?
[Nexus One Android Development] Ivan Dimkovic:
Ondemand definitely... that's what I am using and I have no problems...

Are you sure CPU load is low? Also, make sure that additional "Up Threshold" is 95% (Advanced options of SetCPU)
[Nexus One Android Development] hotweiss:
I am testing your AVS kernel now. What is the advantage of having AVS selected when you already have had the voltage set at the lowest possible point?
[Nexus One Android Development] Ivan Dimkovic:
In theory, AVS should choose lowest stable voltage for each frequency step.

I have to put some traces inside the code to see what voltages it sets at the end - in the best case, it could go even below the undervolted voltages, depending on the CPU. In the worst case, it could go up - because the CPU complains it needs more power.

The whole point of AVS would be that the CPU gets to work on lower voltage than usual, if the load/temperature/etc... is OK. However, it is not clear yet if manual undervolting can get better but still stable results.

Interesting, though, AVS complains about voltage being too low for 1.1 GHz (1.275v) - it looks that 1.1 GHz needs more - even though systems are stable for everyday use...
[Nexus One Android Development] hotweiss:
I see, thanks. Looking forward to more of your work...
[Nexus One Android Development] jblazea50:
man, too many kernels to choose from; there are so many good kernels being developed, i haven't been on one single kernel for more than couple of days

keep up the good work developers
[Nexus One Android Development] rcxquake:
Both wall charger and USB charger do not work. I'll try the latest version and see if the problem is fixed for my phone.
[Nexus One Android Development] MoogooGai:
Same here aonavy, but on my Desire ROM it reads perfect. It just dose not read perfect in my CM Rom... -.- what's the big deal. SetCPU says 1113mhz Benchmark reads 738mhz.
[Nexus One Android Development] evidenc3:
Getting a ton of dropped calls today after i flashed 1.02. Hopefully just the tower I was on, anyone else seen similar? I'm on the stock rom running at stock speeds.
[Nexus One Android Development] aonavy:
I guess 738 is okay then
[Nexus One Android Development] aonavy:
as long as I knowing at 1.113 and not underclcked at 738.

I'm sorta new to all this but know computers.
[Nexus One Android Development] jdoo:
1.1ghz+avs is crashtastic for me :(

Seems good at 1ghz though.
[Nexus One Android Development] xzr3b0rnzx:
i am using ur xtra v1.02 it's wonderful:)
[Nexus One Android Development] Ivan Dimkovic:
Yes, AVS does not mix well with overclocking as it seems (although it does work well on my Nexus, I guess I am just lucky I got a very good CPU)

Tonight I will release AVS update, which is not going to be overclocked. If AVS works well, this could be "Ultra Diet" kernel :)
[Nexus One Android Development] gregnotcraig:
thanks for this (i have the pre-"test avs" installed. you updated while I was @ work! :p)

I noticed a definite improvement in battery life.

i know people like specifics/percentages, but I'm too tired to do that right now.

I will say that i'm a heavy twitterer, web and sms user,etc

Full charge at 1130 am.

at 10pm it was at 75%

usually by that time, it's between 30-40% & I'm looking for an outlet to charge for an hour, so it would at least last me through a 1.5 hour bus ride home.
[Nexus One Android Development] rossy_k:
I have been running AVS @ 1.1GHz for a while now and no crashes so far.... :)
[Nexus One Android Development] bobdude5:
lol i got a reboot with the avs after exit setcpu then held the home button to get back to it

edit: after that its running perfectly..Asphalt 5 plays with very little lag now!
[Nexus One Android Development] aonavy:
Oops wrong thead
[Nexus One Android Development] aonavy:
if I flashed this right...what would it say in setting under kernel vers?
[Nexus One Android Development] jdoo:
2.6.33.1-psyq_uv_xtra

test@ubuntu #36
[Nexus One Android Development] aonavy:
okay..got it.....
[Nexus One Android Development] aonavy:
are there any other setting i setcpu i need to do?

just drag the max scale to max?

reboot after after this?

anything else?
[Nexus One Android Development] pzumk:
use the profiles..

standby 245/245 on demand

charging 245/600 on demand
[Nexus One Android Development] aonavy:
Do I click set on boot or anything like that?
[Nexus One Android Development] pzumk:
yes, set on boot and yes, when you open setCPU you got the 2 bars and put max to 1113 and min to 245. and on demand governor
[Nexus One Android Development] aonavy:
okay

set those profile you listed above

set on boot

cpu gov set to on demand

reboot

sound right?
[Nexus One Android Development] coolbho3000:
CPU Benchmark reads BogoMIPS which is never equal to actual clock speed on the Nexus One.
[Nexus One Android Development] pzumk:
yes but a reboot isnt needed i think. I never did a reboot
[Nexus One Android Development] DebauchedSloth:
Any chance of an update w/o debugging info?
[Nexus One Android Development] Ivan Dimkovic:
Yes I will update everything - it is just that I got a new laptop (new Sony Z) so I have to install everything again.... but I'll definitely be releasing tomorrow.
[Nexus One Android Development] hotweiss:
Bug report:

With 1.03 I have had a few phone conversations disconnected at random times... There's no way that I can prove that it's the kernel's fault. Could be the network, could be the ROM...
[Nexus One Android Development] hotweiss:
Most likely the kernel, as my internet tethering went haywire for the first time ever.
[Nexus One Android Development] evidenc3:
Probably the kernel.. I saw the same yesterday even in different locations ^

Running back on persians UV'd again and things are good.
[Nexus One Android Development] big_adventure:
I noticed that yesterday, when I lost signal in a place at work that kills al cell phones, the phone wouldn't pick signal back up when I went back to my desk. OK, I've seen this with my old iPhone, BlackBerry and Milestone, as well as my Nexus, so I went to airplane mode and back to reset the radio. The radio reset all right, and about 15 seconds later, the phone rebooted.

One time thing? Unfortunately not, I repeated the process 3 more times.

Here, I'll do it now and take a logcat:

...and, naturally, with logcat humming, there is no reboot, even on 3 straight plane / no-plane changes.

I'll have to retry this at work when I go back to the office next week...

Has anyone else seen the same thing? I don't recal seeing the same thing with other kernels.
[Nexus One Android Development] h11g:
Same for me bro. After my phone lost signal, I couldn't call out and receive calls. Sms won't work as well. But the problem is solved if you reboot the phone.
[Nexus One Android Development] Merdon:
Sry for this noob question:)

I flashed my N1 with the uv_extra.

My kernel-version is now 2.6.33-cyanogenmod kmobs@ubuntu #1

Is this the right?, (forgot to check what it was before)
[Nexus One Android Development] rossy_k:
I have some results to report...

Flashing between the AVS kernel posted in this thread, and using persiansown's OC & UV kernel, both running at 1113MHz:

Keeping my phone in standby leaving all background apps/services running I am getting a 1.4% drop per 15mins with persiansown's kernel, and with the AVS kernel am getting about 1.1% drop per 15mins.

^^ The above tests were conducted over 6 hours with each kernel with the same processes running, with the phone remaining in the same postion (in order to negate varying signal strength having an effect) and using JuicePlotter to view the battery voltage vs. time trend.

Two slight glitches I have noticed with the AVS kernel:

1) Answering a call can take some time from me sliding the slider across, to when the phone actually picks up the call

2) When the phone rings, it can (sometimes) take up to three seconds for the screen to light up [the phone is audibly ringing at this point though]

Cheers,

Ross
[Nexus One Android Development] jblazea50:
I also noticed that when the phone rings, the trackball will repeatedly blink, but it takes like 2-3 rings before the screen turns ok and I have they option to pick up the call. I'm on the avs kernel
[Nexus One Android Development] chaimd:
Thank you for your great work, Ivan.

I have a report of AVS kernel.

The kernel is very stable with my Nexus One

in low temperatureof APPLICATION CORE, maybe.

But I executed Xtremelabs Speed Test with WiFi several times, sequential,

then it rebooted with errors of some applications.

I needed cooling down my Nexus One to correct booting.

I check this process in three times with "ondemand" governor.

heating CORE->reboot with error->cooling down->reboot without error.

I hope my report will be a little help for your great work.
[Nexus One Android Development] intersectRaven:
While porting AVS to my .32 kernel, I ran into something in your code that seems off from the official sources. In this portion:

#ifdef CONFIG_MSM_CPU_AVS

/* Notify avs before changing frequency */

if (avs_adjust_freq(freq_index, 1)) {

printk(KERN_ERR

"acpuclock: Unable to increase ACPU "

"vdd.\n");

}

#endif

You need to perform a:

mutex_unlock(&drv_state.lock);

return ***insert error return from function***;

since there is mutex_lock issued right before it. :)
[Nexus One Android Development] Ivan Dimkovic:
Oops... mutex errors are not good :)

Thanks for the tip - I will check it out tonight when I'm back from work.

I hope this is actually the reason causing instability, as AVS seems to be very nice on the battery.

Question for the guys that are getting call drops - what kernel are you using? Normal / Extra / AVS ?
[Nexus One Android Development] aonavy:
does this work with desir rom? (r21)
[Nexus One Android Development] hotweiss:
I am using the AVS kernel, and I have had calls dropped and internet data disconnected.
[Nexus One Android Development] intersectRaven:
I think that's a huge reason for the instability. With my .32 kernel I couldn't even last for more than 10 minutes without my N1 not responding and I had to do a battery pull everytime. With this, I reached about an hour before I decided to recompile from scratch. (I'm obsessed with running my kernel at the #1 iteration without cheating by editing the .version file...besides, I like staring at the compilation display... :p)
[Nexus One Android Development] jblazea50:
Ivan, i'm using the AVS kernel and whenever i receive phone calls, the screen doesn't come up until after couple of rings

normally, it's supposed to show up on the screen rightaway; not sure if it is the kernel, but never had the issue with other kernels
[Nexus One Android Development] Ivan Dimkovic:
AVS code is fixed - and in my github

I will publish new kernels in ~1-2 hours
[Nexus One Android Development] evidenc3:
I was having issues on the normal 1.02, havent tried 1.03/avs yet.
[Nexus One Android Development] Ivan Dimkovic:
V1.04 is out

- I removed the _normal kernel, "_xtra" now default

- Added kernel with AVS but without OC, for maximum battery life

- Fixed AVS bugs (code is in my github)

- Few more small tweaks in kernel configuration (removed unnecessary stuff)
[Nexus One Android Development] pzumk:
thanks will try the new one
[Nexus One Android Development] jblazea50:
thought you removed the OC for AVS, but i still see a zip file with AVS and OC?

anyway, about to try it out
[Nexus One Android Development] Ivan Dimkovic:
Note:

AVS kernels might reboot phone few times after flashing. I am still investigating why is this happening. It could be due to overclocked bootup frequency that is used in most kernels now... I will see if decreasing it helps
[Nexus One Android Development] jblazea50:
this kernel isn't acting right at all; too many reboots and force closures (AVS without OC)
[Nexus One Android Development] christiankk:
Works fine after one million reboots. Avs no oc.
[Nexus One Android Development] hotweiss:
Disconnect bug is still present in 1.04, as I just had my internet connections freeze. It's a shame, as this kernel does seem faster. I am now going to try to get a logcat for you.
[Nexus One Android Development] niner81:
So far so good for me... not even an initial reboot.

Forgot to mention im running avs without oc.
[Nexus One Android Development] jblazea50:
AVS no OC just kept freezing and certain process was force closing; hopefully it will get fixed as the previous version (1.03) was working well for me without any issues
[Nexus One Android Development] Ivan Dimkovic:
If you used AVS in previous version - that was with OC.

You might want to try V1.04 with OC

AVS support is definitely not fully stable yet - and results vary. Some people have no problems with it (myself included) and some people cannot get it to work. It could be CPU dependent.

The only thing I could advise at this point is to try wiping battery stats after flashing the kernel.
[Nexus One Android Development] niner81:
Dont know if this would help, but I wiped the cache after flashing the new kernel and haven't seen any problems yet.
[Nexus One Android Development] jblazea50:
will try AVS no OC once again and wipe cache and battery stats

EDIT: ok, pushed the bcm4329.ko file and flashed the zimage; then wiped cache and battery stats in recovery; rebooted; it went through couple of bootloops; once it started, had to reboot (battery pull b/c screen froze) couple of times; had one force close of launcher; now it seems to be working

One thing weird that i noticed is that prior to flashing this kernel, my batter was near 93% and now it is reading at 100%;

Ivan, under settings/about phone/kernel version, it says psyq_uv_avs_oc test@ubuntu #43 but i put the zImage from the no OC? is that a mistake
[Nexus One Android Development] hotweiss:
The best way to calbirate your battery is to charge your phone up, turn it off, wait for the orange light to go green, and then wipe the battery stats...
[Nexus One Android Development] hotweiss:
OK, I've tried to make it crash again, but as Murphy's law states - I can't. The crashes usually occur when the phone is being used for an extensive amount of time with the screen off. So I am assuming that the problem lies with the downvolting at low speeds, which occurs when simply talking or tethering. Mind you, my last data crash was when using Google Earth. I had to reboot my phone to get my data back.
[Nexus One Android Development] Ivan Dimkovic:
Yes, it is a mistake - currently all kernel images have the same signature. I will fix that in the next revision.

AVS behavior is really interesting - it appears that people usually have initial few reboots and then everything starts working.

I am wondering what is going wrong... Maybe our silicon does not have proper support for AVS, or there is something else needed, maybe CPU has to be initialized in a different way.

For that, careful analysis of the Qualcomm kernel modules is required. I'll see what I can do.
[Nexus One Android Development] chaimd:
I tried V1.04 AVS_OC kernel, and tested in some heavy loaded situation.

It's very stable! No reboot! Quite differnt from V1.03!

Awsome!
[Nexus One Android Development] hotweiss:
I don't think I have yet used this kernel after a reboot. I always uninstalled it, after the first crash. I will let you know how it functions after the first reboot.
[Nexus One Android Development] jblazea50:
i calibrated the battery this morning when i charged it; i charged till it said charged, powered to recovery and wiped battery stats, then powered off until green light came on; then powered on

now, when i flashed this kernel, my battery is reading 100% for some reason; it's been couple of hours since flashing and i've browsed and played homerun3d game for a while, and it's still at 100%

so, i think once i get home, i will plug it to my wall charger, wait till it goes to green, power off until green light comes one, then wipe battery stats again and hopefully it will be working right then

i doubt it's right the way it is since it's been about 2 hours without a loss of a single percent
[Nexus One Android Development] intersectRaven:
Noticed this as well with my build. After a few reboots it just goes fine. Btw, did you also modify the idle-v7.S file in your build? I modified mine since it seems to be low level commands for the CPU registers. :)
[Nexus One Android Development] hotweiss:
Ok, I now have had two crashes in a row when using the Barcode Scanner app. I will try your non-AVS version to see if it is indeed the AVS.
[Nexus One Android Development] bobdude5:
My phone has been unplugged for 19 hours and I'm at 36 percent. .wow this Avs kernel is amazing. .I've been using the phone for everything..music browsing games calls email texts in fact I'm using it to leave this comment. .I can't wait till the final version is release oh and no crashes
[Nexus One Android Development] intersectRaven:
Wrong thread to post... :p
[Nexus One Android Development] christiankk:
anybody else experiencing that the other party can't hear you when you call them?

edit: my phone is now stuck in an infinite reboot loop. sometimes getting stuck, so only pulling the batt. helps.

phone has room temp.

i will have to let this one go :(
[Nexus One Android Development] mgear356:
same here..

happens to me in 1.04 avs

1.03 avs was fine..
[Nexus One Android Development] Ivan Dimkovic:
V1.05 is out

It affects only AVS kernels! I added missing state saving, etc... in the idle-v7.S (thx intersectRaven!)
[Nexus One Android Development] christiankk:
can people hear you when you call them on the new kernel?
[Nexus One Android Development] Ivan Dimkovic:
Definitely... I am using AVS+OC for days now, and yes... I am using my phone for... phoning others :-)

Try the V1.05 - if it does not fix the issue then I am afraid it is definitely CPU-bound... some people are just lucky to have it work.

But you can always use non-AVS kernel. It might have just slightly worse battery life but at least it has no instability issues caused by AVS.
[Nexus One Android Development] charnsingh_online:
Was running ur kernel since days now the avs kernel, suddenly reboots started today when i tried to call listening tmusic, then when it booted i tried to get to call log a reboot n then while using browser a reboot, worked without reboots for many days but now gives problem
[Nexus One Android Development] christiankk:
i'll give it a shot.

cheers :)
[Nexus One Android Development] christiankk:
kinda same thing happened to me - i had to do a nandroid restore to get out of the boot loop. i'll give the new one a shot.