yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] houzuoguo:
thanks :D

at uni I'm learning C++ at moment, I personally prefer C over C++.

Although the unit is called "Application with C++", it emphasis on unix socket programming and multithread using pthread, so it's not much about C++..

Later I'll try to compile your kernel myself see what will happen :D I've never done that before, I'll search for some instructions first..
[Nexus One Android Development] redstar3894:
Check cyanogen's wiki for an EXCELLENT guide on how to build kernels for the n1.... I've gone back to that many times during my experimentation with compiling kernels myself...

IR would be able to give better advice here of course, because it is his kernel after all... ;)

Also, IR, I've been trying to track down the newer 0xlab toolchain you've been using recently, it wasn't in the same place I found the earlier 4.4.1 toolchain you were using.... is there something really obvious I'm just not finding or did you compile it yourself from their source?

Sent from my Nexus One
[Nexus One Android Development] eViL D::
How's the lightsensor port going? :p
[Nexus One Android Development] intersectRaven:
I'll get on that after AXI. This version of AVS seems finished in my N1. Haven't encountered a single wake-up problem overnight. Quite promising. :)
[Nexus One Android Development] eViL D::
Awesome! Not sure if you've tried the HD rom yet, but wifi is really flaky on it. Somebody had posted a kernel from pershoot from late May that had a working wifi module. Seeing how pershoot didn't release his full source until a little while ago, do you think grabbing the bcm files from MSM will work (from May or so)?
[Nexus One Android Development] intersectRaven:
I don't really know but maybe it will. Most of the odd connection changing stuff happened then so maybe it will work. :confused:
[Nexus One Android Development] mescieux:
I've got the wake issue for the first time on 2.6.35.6_AVS-CM-950mV_CFS_20101003_1336 after using it for a couple of days. I realize that you said you might've found the true problem and have a newer version uploaded but I'll add the last_kmsg just in case you want to take a look to see if it's the same problem.

edit: Woops. Got another one on 2.6.35.6_AVS-CM-950mV_CFS_20101004_0839. Another last_kmsg(2) attached.
[Nexus One Android Development] jeffokada81:
Confirmed wake issue. I have to pull battery to reset.
[Nexus One Android Development] clustered:
I have to do the same, tried to call my number... its ringing but the phone didnt wake up...
[Nexus One Android Development] Pochemuchka1977:
Same here with 2.6.35.6_AVS-CM-950mV_CFS_20101004_0839 version, will try 20101006
[Nexus One Android Development] intersectRaven:
Hopefully, the 1006 version solves everything for you. I've been running on a previously compiled kernel for 48 hours now with no problems. :)
[Nexus One Android Development] houzuoguo:
Hi IR, I've been running your 1004 kernel for 1 day and no any problem :)

But sometimes I notice a sudden increase (very huge increase) in battery discharging current during sleep (screen turns off) according to my Current Widget.

I'll try 1006 now...

Thanks for your great work!
[Nexus One Android Development] intersectRaven:
Turn off your WiFi if you're not going to use it for a while. The suspend function of the current driver is wonky. :p
[Nexus One Android Development] houzuoguo:
aha i see, thanks
[Nexus One Android Development] RellikZephyr:
Unfortunately I got no wake issue only hours after flashing 20101006 kernel

Rellikzephyr
[Nexus One Android Development] houzuoguo:
Using 1006 Kernal seems it has solved the sudden battery massive drain problem :) you're awesome IR
[Nexus One Android Development] intersectRaven:
I'll just have to conclude that AVS isn't for your N1 then. Maybe a faulty sensor. :(

*Another possibility is your CPU is just too sensitive and crashes immediately upon lowering voltages without even giving AVS a chance to increase mVs.
[Nexus One Android Development] ZeGM:
Hi,

I've just try last 1006 builds on my N1 with modaco R24 mod, and wifi isn't working with these builds... When I try to activate wifi, it tells me that there is an error.

Is there any solution to make it works ?

Thanks.

DD.

PS: Ok, solution found, I've pushed bcm4329.ko and wifi now works.
[Nexus One Android Development] eViL D::
Ahh, you sneaky guy! Snuck in a little OC, eh? :cool:

New source is looking pretty good. Gonna test a couple more days to make sure it's stable though.
[Nexus One Android Development] houzuoguo:
Hi Iven

this morning I thuoght I got no-wake-up issue...running latest CM nightly and your 1006 kernel for CM

actually not :D battery had drained completely, thus it didn't wake up~

I had 20% left last night, normally it drains 8% overnight.

so I tried to get latest kernel messages but.... again last_kmsg was not there?!

my current widget recorded for me some strange data.

After I fell asleep, battery started draining at more than 150mA per hour, the current varied from 110mA to 220mA, but never gone below 100mA.

And the record stopped when battery had 15% left (real no-wake-up?)

Normally for me , android shuts down when battery has 7% left.

by the way, does Nexus One CPU naturally support AVS? (though some support well and some don't?)
[Nexus One Android Development] intersectRaven:
Did you turn off WiFi before you slept? That could account for the drain as its suspend function is wonky. The Scorpion CPUs have the sensors to implement AVS. Whether they're calibrated for it or if the CPU has a tolerance for low voltages without throwing errors IMMEDIATELY is unknown. :)
[Nexus One Android Development] houzuoguo:
Thanks. I forgot to turn off wifi :)
[Nexus One Android Development] intersectRaven:
New source doesn't have the patch for the delay so it may still cause lockups for some (although the chances are extremely diminished by the AVS change I committed which is already there). :)
[Nexus One Android Development] houzuoguo:
you're reaching your 1000th post Iven :P

Temporarily I'm using WM's 925mV AVS kernel (I know its AVS is based on yours) without overclocking, for some reason, it works always very well on my phone..
[Nexus One Android Development] dlunch:
no commits?
[Nexus One Android Development] RellikZephyr:
Since first no wake error, 20101006 has been stable. Please teach me how to make last msg. Incase it fails again

Thanks

Rellikzephyr
[Nexus One Android Development] Pochemuchka1977:
Read the thread ... http://xdaforums.com/showpost.php?p=8447297&postcount=4329
[Nexus One Android Development] RellikZephyr:
That's too easy thanks

Rellikzephyr
[Nexus One Android Development] loverhime:
I tried 2.6.35.6_AVS-CM-950mV_CFS_20101006_0848 and quiet smooth, but not stable.It was issused no wake error.

I am using CM6 Nightly#183=]
[Nexus One Android Development] intersectRaven:
I think that should be addressed in my latest edit which I've committed to my GitHub. Don't have time to compile right now though. :(
[Nexus One Android Development] mafiaboy01:
Hi, I just installed this kernel over my nightly build of CM and everything is running great!

The only thing is that I don;t know what app to use to get the FM Radio working?

Any help would be apreaciated.
[Nexus One Android Development] intersectRaven:
W00T! 1000th personal post! Nicely coincides with HAVS update release! :D

*Also my 600th tweet. :p
[Nexus One Android Development] ~~Tito~~:
I am about to try it now! :)
[Nexus One Android Development] eViL D::
Lol, uhh... congrats? Updated to the latest source. Using wm's older wifi driver and things are running smooth on the HD & Z ports.
[Nexus One Android Development] intersectRaven:
Nice to hear. What driver version worked?
[Nexus One Android Development] eViL D::
I believe monks said it was 4.218.246
[Nexus One Android Development] houzuoguo:
Hi Iven,

thanks for your great work!

How is wifi driver in the latest release?
[Nexus One Android Development] eViL D::
This isn't Ivan's thread, it's IntersectRaven's. You may be confusing the AVS part. Those are 2 different people.
[Nexus One Android Development] intersectRaven:
I think he just compressed my name since he spelled it as Iv-E-n and not Ivan...still, better to be safe. Ivan and I are two different people. There, that's the official release. :p
[Nexus One Android Development] eViL D::
Lol, straight from the man!
[Nexus One Android Development] eViL D::
here's from kmsg regarding wifi.

Firmware version = wl0: May 28 2010 14:32:04 version 4.218.207.0
[Nexus One Android Development] intersectRaven:
Woah! That's old... :p
[Nexus One Android Development] houzuoguo:
hehe~ I know Ivan, the another guy doing AVS kernel, i remember i once used his/her kernel together with cyanogen mod long long ago..

all right so this is.. intersectRaven ..
[Nexus One Android Development] myakove:
Run on CM nightly and the phone very slow. (using BFS kernel)

from kmsg:

<3>[ 866.780700] acpuclock: Unable to increase ACPU vdd: 1113600.

<6>[ 866.815063] -21568mV too high for 1.

<6>[ 866.815368] AVS setting V to -21568 mV @0 MHz

<3>[ 866.820861] acpuclock: Unable to increase ACPU vdd: 1075200.

<6>[ 866.895202] AVS setting V to 0 mV @0 MHz

<3>[ 866.900482] acpuclock: Unable to increase ACPU vdd: 1036800.

<6>[ 870.889038] 17172mV too high for -1073527996.

<6>[ 870.889373] AVS setting V to 17172 mV @3221439 MHz

<3>[ 870.894836] acpuclock: Unable to increase ACPU vdd: 1113600.

<6>[ 870.979187] AVS setting V to 1050 mV @537 MHz

<6>[ 871.101318] AVS setting V to 975 mV @245 MHz

<6>[ 875.883911] 17172mV too high for -1073527996.

<6>[ 875.884246] AVS setting V to 17172 mV @3221439 MHz

<3>[ 875.889709] acpuclock: Unable to increase ACPU vdd: 1113600.

<6>[ 879.507568] 17172mV too high for -1073527996.

<6>[ 879.508117] AVS setting V to 17172 mV @3221439 MHz

<3>[ 879.513397] acpuclock: Unable to increase ACPU vdd: 1113600.
[Nexus One Android Development] intersectRaven:
Don't overclock. The new code for ensuring voltages are set are causing intentional delays whenever the voltage can't be set. The problem is AVS doesn't have the proper voltages to set to so it delays the change everytime. :)
[Nexus One Android Development] mafiaboy01:
Hi, been using this kernel for a little while and it works great, the only thing is that I don't know where to find a radio app of it.
[Nexus One Android Development] MaxiJavi:
They are from different days ... Different builds ...

2.6.33_AVS-850mV_20100412_1010.zip is going to be an untested build from today, I assume.
[Nexus One Android Development] hah2110:
But why does one say UV and one doesn't?
[Nexus One Android Development] intersectRaven:
Haven't gotten around to running my auto build script yet. Too busy at work. :p

The UV one is the older build which was compiled manually. The mV is the newer build compiled using my automation script. No significant changes are there so you can use the older one. :)
[Nexus One Android Development] hah2110:
Ok and what is standard AVS vs. something like 850UV?
[Nexus One Android Development] intersectRaven:
The standard AVS is the 1000mV one since that is the default minimum that is specified in the AVS files. :)
[Nexus One Android Development] hah2110:
For the record... You are the most responsive dev I have ever seen... so KUDOS! How much battery life would someone realize moving from standard AVS -> 850??

EDIT - In your experience, what ROM has the best battery?
[Nexus One Android Development] intersectRaven:
Thanks! The secret to that is having almost no social life whatsoever. (Uhm...not really sure I should be proud about that though... :p ) The battery life depends on too many factors to accurately quantify. Suffice it to say that the battery life would be better the lower the minimum voltage. Just be aware that the risk for instability increases as the minimum voltage is lowered. :)

* I don't really go around trying different ROMs. I stick with cyanogen's stable. :)
[Nexus One Android Development] myplague:
If your phone can handle the 850mV then go for it!

I used it all day yesterday and had 42% left after 18 hours with heavy usage for most of the day.
[Nexus One Android Development] exelinguy:
Not able to go below 1075 @ 14 on Modaco Desire ROM...
[Nexus One Android Development] intersectRaven:
Updated!

20100412_2234:

Non-AVS:

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

AVS (800mV):

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

AVS (825mV):

http://www.mediafire.com/?2k3iijnmynz

AVS (850mV):

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

AVS (875mV):

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

AVS (900mV):

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

AVS (925mV):

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

AVS (default - 1000mV)

http://www.mediafire.com/?nt2jglimjz2
[Nexus One Android Development] intersectRaven:
The Desire's UI required the additional processing power which is why it won't go down in CPU frequency. I think you can use SetCPU to force the idle clock speed to 245 for you to gain power when your display goes on suspend. :)
[Nexus One Android Development] exelinguy:
With SetCPU it's going down to 850mV @ 2. Time to save some battery!:D

Will try 800mV now. Is it working for you Raven?
[Nexus One Android Development] intersectRaven:
Yes. I'm stable at 800mV. You'll be one of the lucky ones if your N1 is stable at that minimum voltage. :D
[Nexus One Android Development] christiankk:
875 mV works for me :cool:

Thanks intersect! :)

edit: thats about 6% lower than 925! woot!
[Nexus One Android Development] exelinguy:
I seem to be quite stable at 800mV! Thankyou very much!
[Nexus One Android Development] Gimpeh:
Has anyone had any issues with wifi tethering with this kernel?
[Nexus One Android Development] intersectRaven:
Are you having issues? As far as I know, I already solved the tethering issues a few changes ago. :confused:
[Nexus One Android Development] RieGo:
800mV working for me after the usual reboots. only problem is rebooting the phone...

so let's go for the 600! :D (just kidding)
[Nexus One Android Development] maximus0206:
800mV

Well, the 800 mV setting was working great for about an hour, then a reboot occurred while it was sitting in the dock idle, trying the 825mV kernel now.

Keep up the great work!
[Nexus One Android Development] hah2110:
What do you mean problem is rebooting? Anyone noticing performance issues with these? I'm not, just curious.
[Nexus One Android Development] yuripave:
intersectRaven, I am wondering if you can make the kernel havs again so people willing to oc will use svs. Since there are 2 ppl asking the same question, i think you should either limit your kernel @998 and explain it on first post, or use svs when ppl do want to oc. So ppl won't be confused. I know you are not a big fan of OC but i dont think you want to answer the same question over and over again =)
[Nexus One Android Development] mik101:
x2... but I'm having lockups with the latest CFS kernel at stock speeds anyhow. Latest CM6 nightly. No lockups with stock CM6 kernel at the same speeds.
[Nexus One Android Development] himynameisbunny:
Cool, so that's why it was lagging so bad. Running like lightening now :)

Are you planning on fixing the AVS code to operate with overclock?
[Nexus One Android Development] intersectRaven:
AVS isn't for you if it still locks up now. :(

I'm thinking about it. :p
[Nexus One Android Development] himynameisbunny:
Brotip: Cm nightlies are experimental - I'd try running it on cm6 stable first to see if that fixes the issue.
[Nexus One Android Development] intersectRaven:
Update posted!

Those who want to use the OC frequencies can now use it without experiencing the delay issue. Please be advised though that AVS will not be adjusted to support this if the current voltages prove to be insufficient. ;)
[Nexus One Android Development] dessanct:
After flashing the newest kernel you've posted my SD card seems to repeatedly disconnect then connect... no idea if it's the kernel's fault but I didn't have this problem before I flashed it..

EDIT: I restarted my phone and now when I try to boot my phone it just says "System not responding" Force Close / Wait but it locks up on either one..

EDIT 2: I got it to boot again by pulling out battery and it seems to be running okay again.. will get the kmsg if it happens again.
[Nexus One Android Development] houzuoguo:
Hi Raven, how is the wifi driver in the latest kernel.. does it have bug with sleeping?

thanks~
[Nexus One Android Development] intersectRaven:
I think I'll have to restore the MMC driver to its previous incarnation. I don't have this error but I have seen it before when I wasn't basing my kernel from Cyanogen's. :)
[Nexus One Android Development] dessanct:
My phone just randomly rebooted too.. I have the kmsg, but I don't know which part of it would help so here is the whole thing :P

http://www.mediafire.com/?06qtk73z4n7e7a1
[Nexus One Android Development] intersectRaven:
You're using OC frequency so I cannot guarantee stability. :)
[Nexus One Android Development] Pochemuchka1977:
High power consumption of the new 20101011 kernel

IntersectR,

It looks like the power consumption of the new version (CFS-CM) is very high

<6>[ 3986.662078] batt: 99%, 4114 mV, -44 mA (-36 avg), 26.2 C, 1344 mAh

<6>[ 4036.804687] batt: 99%, 4118 mV, -39 mA (-36 avg), 26.1 C, 1344 mAh

<6>[ 4086.912017] batt: 99%, 4118 mV, -35 mA (-37 avg), 26.1 C, 1342 mAh

<6>[ 4137.029235] batt: 99%, 4118 mV, -38 mA (-36 avg), 26.1 C, 1342 mAh

<6>[ 4197.117950] batt: 99%, 4118 mV, -39 mA (-65 avg), 26.1 C, 1342 mAh

<6>[ 4262.286376] batt: 99%, 4114 mV, -36 mA (-85 avg), 26.1 C, 1340 mAh

<6>[ 4327.431671] batt: 99%, 4114 mV, -37 mA (-35 avg), 26.0 C, 1340 mAh

<6>[ 4377.555816] batt: 99%, 4114 mV, -34 mA (-36 avg), 25.8 C, 1337 mAh

<6>[ 4427.711425] batt: 99%, 4114 mV, -36 mA (-39 avg), 25.8 C, 1337 mAh

<6>[ 4477.832794] batt: 99%, 4114 mV, -35 mA (-36 avg), 25.8 C, 1337 mAh

<6>[ 4532.873046] batt: 99%, 4114 mV, -36 mA (-35 avg), 25.8 C, 1337 mAh

<6>[ 4593.004455] batt: 99%, 4109 mV, -43 mA (-37 avg), 25.8 C, 1336 mAh

<6>[ 4658.111267] batt: 99%, 4109 mV, -35 mA (-37 avg), 25.8 C, 1336 mAh

<6>[ 4723.231781] batt: 99%, 4114 mV, -35 mA (-38 avg), 25.8 C, 1334 mAh

<6>[ 4788.398162] batt: 99%, 4114 mV, -35 mA (-37 avg), 25.8 C, 1334 mAh

<6>[ 4853.533843] batt: 99%, 4109 mV, -34 mA (-37 avg), 25.8 C, 1332 mAh

<6>[ 4918.649353] batt: 99%, 4109 mV, -36 mA (-35 avg), 25.8 C, 1332 mAh

<6>[ 4983.797882] batt: 99%, 4109 mV, -36 mA (-36 avg), 25.8 C, 1332 mAh

<6>[ 5048.893890] batt: 99%, 4109 mV, -35 mA (-35 avg), 25.7 C, 1331 mAh

<6>[ 5114.036193] batt: 98%, 4109 mV, -34 mA (-35 avg), 25.7 C, 1331 mAh

<6>[ 5179.160217] batt: 98%, 4109 mV, -37 mA (-35 avg), 25.6 C, 1331 mAh

<6>[ 5244.288085] batt: 98%, 4109 mV, -34 mA (-36 avg), 25.6 C, 1329 mAh

<6>[ 5309.437713] batt: 98%, 4104 mV, -36 mA (-36 avg), 25.6 C, 1328 mAh

<6>[ 5374.563964] batt: 98%, 4109 mV, -37 mA (-38 avg), 25.8 C, 1328 mAh

<6>[ 5439.719543] batt: 98%, 4104 mV, -37 mA (-43 avg), 26.1 C, 1328 mAh

<6>[ 5504.854614] batt: 98%, 4104 mV, -44 mA (-39 avg), 26.3 C, 1328 mAh

In previous versions the drop was about -5 -7mA when the phone was idle ...
[Nexus One Android Development] intersectRaven:
Noticed that. It seems the MMC modifications caused the phone to become unable to sleep properly. I'll be reverting in the next release. :o
[Nexus One Android Development] pakalrtb:
Just flashed the latest kernel over a previous IR one and Titaniun Backup seems to FC everytime.

p_
[Nexus One Android Development] ~~Tito~~:
Will this work on emonthers? I will try the next release it was really unstable on Paul's v24 desire ROM.
[Nexus One Android Development] intersectRaven:
I'm uploading a fixed version right now. This should fix the MMC issues. Google just fixed it when I woke up. :)
[Nexus One Android Development] pgwipeout:
Love you man! Had a bluetooth issue but once I re-paired with my computer it started working again.
[Nexus One Android Development] intersectRaven:
Will be releasing a -CM update which should enable the MIUI app to work when flashed on a ROM with the MIUI framework modifications. :)
[Nexus One Android Development] intersectRaven:
Update posted to -CM release!

Now supports the MIUI FM app IF used with a ROM with the MIUI framework modifications. :)
[Nexus One Android Development] ~~Tito~~:
Where to get? LOL
[Nexus One Android Development] yuripave:
Just got a no wake on 1012 CFS CM, going back to 1009, 1009 seems stable to me.

Edit: I don't have a last_kmsg because I go straight to recovery to flash 1009 after I pull the battery.
[Nexus One Android Development] Werewolf123:
Dear intersectRaven!

Could you make version without "audio boost modification"?

Very high volume level of speaker after unplugging BT headset makes me crazy!
[Nexus One Android Development] m3nster:
FM Radio

It works flawless! Perfect reception! Great!
[Nexus One Android Development] operron:
I'm still facing the issue where the Wifi can't connect to my hidden SSID (wpa2 encryption, wifi N).

The only kernel around here that do work is actually the latest wildmonks kernel (27th Aug).

I know you've reverted the broadcom driver back to version 4.218.246 but there must be something else (maybe a further patch to the bcm driver?) that prevent connections to hidden SSID.

What can I do to help you fix this nasty issue ?
[Nexus One Android Development] r8zer:
thats happens on cyans rom aswell, and even before that on stock i could never connect to hidden ssid
[Nexus One Android Development] daveid:
I would be willing to pay for any kernel that has no audio boost, since WM's are now outdated and don't have the latest features and fixes.
[Nexus One Android Development] intersectRaven:
Here you both go!

CFS HAVS-CM-NOBOOST:

http://www.mediafire.com/?483sol9oqqwjikf

BFS HAVS-CM-NOBOOST:

http://www.mediafire.com/?61iuukh3yjcwsgb
[Nexus One Android Development] daveid:
Thanks a million, going to flash it now... Donation will be forthcoming, pay day is Friday.
[Nexus One Android Development] Werewolf123:
Thank You! You are the Best! In future, can we see the new versions without boost?
[Nexus One Android Development] intersectRaven:
I'll think about it. Depends on how busy I am. It's easy to compile my usual releases since they're supported by my auto build script but audio boost currently isn't. :cool:
[Nexus One Android Development] houzuoguo:
Raven :P

this morning when I woke up, screen wouldn't turn on but trackball was flashing, that was first time I had that occasion on 8/27 AVS WM kernel :D

now I'm using your second latest kernel(the one without FM code from MIUI) since this morning, it works very well, and wifi sleeping works fine.

Thank you!
[Nexus One Android Development] operron:
I've rebuild IR's kernel after replacing current bcm4329 files with the ones used by wildmonks. The kernel starts to boot and then hangs somewhere in the middle of the boot process (just after the charging led is being switched on).

Any idea how I could get some logs of the failing boot process ? Is there any way to get a console ?
[Nexus One Android Development] intersectRaven:
You need to revert the changes made by these commits:

ff9d876e8892557e61ed7aedfa04c5ceaafb4662

7607ec95d771aac75cc0f46acbf800a329bacda4

Good luck! :)
[Nexus One Android Development] operron:
Thanks IR, the kernel boots now but FM app hangs while enabling BT...
[Nexus One Android Development] operron:
It's maybe worth adding that I was able to add FM support to wildmonks kernel by merging commit 1208591ceeef388d7478 (Merge "support FM Radio in kernel" into android-msm-2.6.35) from cm-kernel.

With this modified wildmonks kernel, FM radio and wifi do both work as expected.

So i need to digg a bit more the 2 source trees...
[Nexus One Android Development] zitseng:
I'm trying to build the IR kernel myself. I install it in a CM6. The phone works except for one little thing. I can enable bluetooth the first time, then disable it. But subsequently, bluetooth cannot be enabled anymore.

The downloaded IR kernel works perfectly.

Any pointers on what might be wrong or where I should look?
[Nexus One Android Development] intersectRaven:
You should revert the modifications I made to enable FM in desire. :)