yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] intersectRaven:
I'll post it after I clean-up the code. I'm still not finished tracing everything and making it "clean". :)

Battery life depends on a variety of factors. This kernel just addresses the kernel part. If you don't experience any improvements, the other factors (use, apps, etc.) are what is causing most of your battery drain. :)

Nope. :p

Too many factors to say why some can go 800 and some can't. :p

Nope again. :p (I really have a very bad experience with overclocking) Besides, that's what Ivan's kernel is for! (well, atleast when I finish the changes and upload to my github or if he traces from hugonz' post whichever happens first I guess) This kernel's objective is to get maximum powersavings at stock. :D
[Nexus One Android Development] hugonz:
My name is hugonz, not honz :-)
[Nexus One Android Development] intersectRaven:
Sorry about that! My brain likes to shorten things to make it fit in one sector of my memory file system. :p
[Nexus One Android Development] www1:
Insert can U give more volume for audio (ringtone)?

Iin many case I can hear my N1.

:)
[Nexus One Android Development] intersectRaven:
I think that's still a work-in-progress by rotohammer. :)
[Nexus One Android Development] pzumk:
Oh well, since there are so many custom kernels now I don't know which to use :D

Just flashed the "experimental!!! 850mv_avs_oc" by PsyQ and someone gave me a heads up that there's a kernel with 800mV.. just flashed your latest one and will give it a try.

Edit // What about overclocking it? ;) (didnt read the 100 sites, sry if its been answered before, maybe you put it in the first post)

Edit // Has been answered just a site ago :D Okay
[Nexus One Android Development] Docmjldds:
As much as I would also like OC, I had been using Ivan's Kernel till a couple of days ago. Stability in the beginning slowly decayed to several random reboots, or freezes/day. Enough to go looking here ;)

So far so good. And no rebooting/freezes to date. THanks for the great work/effort here.....
[Nexus One Android Development] wildmonks:
Awesome! Thanks Raven :)
[Nexus One Android Development] d.cortez:
i always like to try the kernel before flashing. so instead of flashing it, i use the "fastboot boot zimage zImage" command which boots the phone with the new kernel but doesn't permanently flash it to my device. this way if i have a problem i just reboot my phone using the stored boot.img.

wanted to report that i tried the 4.18 release on Desire ROM A19 and my phone will not boot (e.g., go past the 4-colored X logo). this includes wiping the cache and the battery stats. now, i suspect it could be due to kernel size??? previous sizes were in the 2-2.2 MB range while the latest version is about 3.9 MB in size. i tried 3 times but it didn't work. no worries though, as i mentioned above, i rebooted (e.g., removed the battery) and my phone started without issue using the 4.09 Non-AVS version that's permanently flashed to my device.
[Nexus One Android Development] intersectRaven:
Uhm...3.9 MB?!?! There is something wrong with that file if that's what you're flashing. The latest kernel is only 1.9MB in size. :)
[Nexus One Android Development] Markdental:
Raven, over in Pershoot's thread he did the following:

switched from NEON to VFPv3 optimisation flag

And it seems to have made the phone a bit snappier plus there is no lag at all while playing Asphalt. Would you consider making this version of your AVS kernel?
[Nexus One Android Development] pzumk:
Crazy. Your kernel work great for 4 hours. 5 mins ago I started WiFi and some seconds ago it just restarted and I got a bootloop. Im getting to the lockscreen and its restarting again. Lockscreen, restart, lockscreen, restart.

I'm in fastboot now. Should I flash the 825?
[Nexus One Android Development] intersectRaven:
I think you're having problems with the WiFi module. It is a known problem for some. I still don't know why this is the case.

To All:

I uploaded a new version of the hybrid AVS kernel with the cleaned-up code. I'm a bit hesitant about it though since it might reintroduce the bugginess of AVS. If you want to help me test its stability, here is the link:

20100419_0009:

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

I need testers for this since my phone likes the previous unstable AVS too much so I can't expect any reboots even if this reintroduces the bug. :)
[Nexus One Android Development] pzumk:
I used pershoots, persiansowns and psyqs kernels and never experienced wifi problems :\
[Nexus One Android Development] jblazea50:
this latest one (20100419_0009) is no good for me; phone stays on the "X" screen and keeps rebooting to just the "X" screen

btw, can you get your kernel to work with Manup's Goodies5 for Cyan 5.0.6? i flashed the goodies and the camera doesn't work (maybe Manup will fix it)
[Nexus One Android Development] intersectRaven:
:(

Anyways, just flash back for now to the previous version. I'll have to study the code more but can't do it tomorrow since I have a M$ seminar to attend for work. ;)
[Nexus One Android Development] pzumk:
I managed to get into airplane mode before wifi automatically starts and thats how I avoid another reboot.

and as im writing this the phone is rebooting again.. -.- damnit. worked for 2 minutes!

after the reboot im pushing the .ko file again, maybe its working now..

Edit // to be more clear: I flashed your new kernel and I dont get stuck at the X like jblazea but I get random reboots. Right now another one, repushing the .ko didnt work

Edit // are there any differences between your wifi module and psyqs?

Edit // Yes, yours is 207kb and psyqs is just 196, will push his .ko to try it..
[Nexus One Android Development] hah2110:
Re: [Kernel - .33.2]intersectRaven's Kernel (new Hybrid AVS *STABLE*) 04/18/2010 0

I'm getting numerous force closes on the newest one on enom

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] wildmonks:
I get the exact same problem which I talked about how I got around it on post #244. (In summery, erase all wi-fi profiles before pushing kernel+ko files, and avoid using "Add Wi-Fi network" option in the wi-fi menu)

It was this problem that lead me to learn how to compile android kernels for myself so I really have to thank you raven, I'm having a blast learning how to compile/program for android :D
[Nexus One Android Development] pzumk:
Okay thanks.

I pushed PsyQ's .ko file and it doesn't reboot anymore but WiFi isn't working either.
[Nexus One Android Development] MaxiJavi:
Happy chappy

Hi intersectRaven,

I am using the 17_1756 since you released it ... Thank you so much.

It is both responsive and super good with my battery :-)

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] pzumk:
I reflashed CM 5.0.6 and reflashed PsyQ's AVS 850mV Kernel.

Will try yours again when it's more stable.

Why is your .ko file bigger than Pershoots or PsyQs?
[Nexus One Android Development] prscott1:
I flashed the 2.6.33-AVS-800mv on my modaca alpha2.1 desire custom rom and it works great! I'm not sure if it is a placebo effect but my bluetooth connection in my car is working more stable with this rom/kernel combo.

Thank you!! :D
[Nexus One Android Development] die-hard:
latest kernel reintroduce AVS bug. My N1 stay on X boot :(
[Nexus One Android Development] hah2110:
this is weird. any time I'm in maps and try to do a voice search, it goes into the boot animation. it isn't a full reboot, just the animation and then it comes back. anyone else?

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] jblazea50:
thanks, just pushed the new kernel through, charged battery fully and wiped battery stats

hopefully this is a keeper; although i will probably push the .33 kernel tomorrow

thanks again
[Nexus One Android Development] hotweiss:
Unfortunately the USB tethering and WiFi tethering does not work with your latest kernel.
[Nexus One Android Development] intersectRaven:
Hmmm...maybe I neglected to turn on a kernel option in my compile. I'll look at it tomorrow. ;)
[Nexus One Android Development] gettingtired:
thanks for the great work.

but the new kernel reboots after bootscreen on my device...

maybe it's too hot because it was on the charger :confused:
[Nexus One Android Development] christiankk:
mine is also out of whack :(

edit: it seems better after a few random reboots and fc's :/
[Nexus One Android Development] fabioccoelho:
Maybe u needed wipe battery status :)

For me works with method :p

Cheers ;)
[Nexus One Android Development] RieGo:
(Back with new name...)

I'm gonna try it, thanks.

edit: omg, my nexus was going crazy... i did wipe battery stats, but there was one freeze after another and display did flash up on boot. I'll let my hands off this for now :)
[Nexus One Android Development] christiankk:
Been using this one for a few hours now. Rock stable and very nice on the battery. Fncking nice! :cool:
[Nexus One Android Development] fabioccoelho:
Same for me :cool:
[Nexus One Android Development] jazzor:
Just a quick question: Why did you go back to SLAB? I thought SLAB was the worst of the three...
[Nexus One Android Development] intersectRaven:
I reverted all of my previous build settings to see if one of them was causing the instability. I'll revert it back after testing this further. :)

Updated with tethering support!
[Nexus One Android Development] britoso:
I'm on the 4/1 version now. .33. works fine.
[Nexus One Android Development] wildmonks:
I can confirm that the USB tethering is working just fine on both .32 and .33 versions of 20100402_0921 but it doesn't work with the wifi/bluetooth tethering app. I get an error saying "No netfilter" and refers to a FAQ page stating: the "kernel on your device does not have the features (CONFIG_NETFILTER, CONFIG_IP_NF_IPTABLES and CONFIG_NETFILTER_XT_MATCH_MAC) required for tethering. If the feature "CONFIG_NETFILTER_XT_MATCH_MAC" is missing the "access control"-feature will not work correctly"

Otherwise, this kernel is excellent! Stable and smooth (even when set to conservative). Keep up the good work!
[Nexus One Android Development] intersectRaven:
Thanks for pointing that out! I disabled that option in my .32 kernel to save space since I thought nothing was using it based on its description. I'll try to integrate it in the next release. ;)
[Nexus One Android Development] intersectRaven:
Minor edit to my first post to point to my github repository. (contains my AVS modifications to both .32 and .33 kernels...) ;)
[Nexus One Android Development] RieGo:
with the new kernel i still get a lot of freezes. can't get it running for more than 2 minutes...
[Nexus One Android Development] intersectRaven:
Have you cleared your battery stats and tried it for a couple of reboots? It usually clears up after one or two reboots on a new flash if you were from the non-AVS kernel before. :(
[Nexus One Android Development] jblazea50:
IntersectRaven, not sure if you mentioned this earlier or not, but did you put back "ondemand" option for SetCPU?
[Nexus One Android Development] RieGo:
Yes, i charged completely and wiped battery stats and cache. I did about 10 reboots and after landing on homescreen it did everytime either freeze or force a reboot.

Maybe my CPU is too lazy ;)

I'm now back on the latest non-AVS, which works nice.
[Nexus One Android Development] intersectRaven:
Yeah. Its set as default now but if you want to go to other CPU governors, I included all of them so you can select what works best for you. :)

Btw, to all who are having problems with AVS, you can help me pinpoint the problem by doing the ff:

1.) Do not remove your N1 from the USB after rebooting.

2.) Wait for 'adb devices' to recognize your device and type 'adb shell'.

3.) Enter 'cat /proc/kmsg' and press enter. Tell me if you're seeing lines starting with AVS and what the message is.

I'm guessing the instability is being caused by some processors who can't handle even the maximum voltage of this kernel, 1250, and needs the default of 1275 to function properly.
[Nexus One Android Development] britoso:
Updated to 2.6.33_AVS_20100418_0816.

No problems with 800mV now :)

nice bugfix.

cat /proc/kmsg |grep AVS
<6>[ 528.462432] AVS setting V to 800 mV @20
<6>[ 528.652709] AVS setting V to 1225 mV @20
<6>[ 535.299194] AVS setting V to 800 mV @20
<6>[ 535.399291] AVS setting V to 1225 mV @20
<6>[ 539.323089] AVS setting V to 800 mV @20
<6>[ 543.777587] AVS setting V to 1225 mV @20
<6>[ 545.939575] AVS setting V to 800 mV @20
<6>[ 548.472076] AVS setting V to 1225 mV @20
<6>[ 566.409545] AVS setting V to 800 mV @20
<6>[ 575.388275] AVS setting V to 1225 mV @20
<6>[ 577.800659] AVS setting V to 800 mV @20
[Nexus One Android Development] vegetaleb:
If someone can try BT Desire Rom with this kernel to confirm I will come back to Desire R19 or KingDesire :D
[Nexus One Android Development] rjhay22:
Yo blaze, kernel works if you flash it over cyan and goodies. But will give you error if you flash goodies over it.
[Nexus One Android Development] jblazea50:
oh yeah, i know the kernel works; sorry i may have not typed that correctly

i'm using his 800mV kernel from yesterday and it's great

the issue i'm having actually isn't related to the kernel; just that once i flashed manup's theme and goodies, the desire camera doesn't work, i get forced closes all the time; so i pushed the camera apk from cyan's rom, but that max out a 3MP and not 5MP; so i guess the only thing to do now is wait for Manup to create his goodies without the desire camera and just the stock camera

sorry for the confusion
[Nexus One Android Development] rjhay22:
NP man, so wait you say the stock cam from cyan is 3MP Max? Or the desire cam ? coz I know, when using the fullscreen version of the desire cam its only 3mp, but don't think the stock is. Let manup know bro he usually fixes stuff quick.
[Nexus One Android Development] hah2110:
This actually happens on ANY voice search. WEIRD. Any help? Also - has anyone used these kernels on MCR?
[Nexus One Android Development] jblazea50:
Manup's Goodies5 include the desire camera, which I suppose is 5MP (4MP if using widescreen), but the desire camera force closes on me everytime. So I just extracted the camera apk from cyan's 5.0.6 and pushed it to /system/app and now the stock camera max is at 3MP

yeah, a few others are waiting on Manup to post a Goodies5 version with stock camera
[Nexus One Android Development] Docmjldds:
Just tested voice search with maps opened and no problems. Absolutely the best stability to date. But I also am using older CM ROM so I can have a good stable desire camera, till a newer kitchen comes out with 5.0.6 and desire camera in the oven, although I did have it working with no problems on the test 3 version. Was an Alpha desire user till R21 and too many bugs had me coming back to non Desire Roms. Diet setup decided to go south for no reason, especially after waking up phone from long standby/sleep.
[Nexus One Android Development] Enndr:
I've been on the new kernel all day with no issues at all... Looks like a winner! :D
[Nexus One Android Development] lore2486:
love the new kernel but i think theres something wrong with the avs messages on the debug, it never shows 800@2 mine always goes down to 800 but @14 and set cpu shows the cpu at 245mhz shouldent that be @2?? im using conservative if it matters
[Nexus One Android Development] intersectRaven:
That means AVS already set the mV for @2 as stable and hasn't been updating it. It should be fine.

To All:

Thanks to those who tested the "cleaned" kernel. I'm disappointed that it brought back the random reboot AVS bug. Anyways, please just use the stable version posted on the front page. :)

*By the way, I need help in locating this function in the code aurora repository for AVS. Here's the function name:

tps65023_set_dcdc1_level

I just need to see what it actually does but can't seem to find it anywhere. :confused:
[Nexus One Android Development] hugonz:
I guess you already know this, but the TPS65023 is a voltage regulator IC that contains several voltage regulators (DC-DC converters). DC-DC1 provides voltage for the Scorpion applications processor core.

I would imagine this function:

static int tps65023_dcdc_set_voltage(struct regulator_dev *dev,

int min_uV, int max_uV)

in aosp/android-msm-2.6.32 does the same thing...

The Chromium kernel seems to have diverged considerably from the Android kernel, and appears to be being worked on by different teams at Code Aurora/Qualcomm.

What specifically do you need to know about it?
[Nexus One Android Development] intersectRaven:
I need to know how they diverged so I need to see it in the code aurora version. It's the piece that is causing the reboots for AVS in the N1 version. Although I believe it is safe to take it out, I don't like getting rid of code without knowing anything about it. :)

*Edit: It's not exactly that code. Just the equivalent in our N1 version. :p
[Nexus One Android Development] jazzor:
it is interesting I was looking for the same thing. If you look at include/mfd/tps65023.h you will see that its actually defined only if CONFIG_TPS65023 or something is defined. If you search for CONFIG_TPS65023 you will see that its doesnt exist anywhere, so in the chromium kernel case, i think its just -ENODEV or something very wierd...
[Nexus One Android Development] D_Toma:
is there a way to see what voltage the phone is actually running?????

also what should show up as the code for this kernal?? i have the 800mv one my phone is showing 2.6.33.1-psyq_uv_avs_oc test @ubuntu #44 is that right
[Nexus One Android Development] b1337:
just flashed the latest mine says...2.6.33.2-intersectRaven root@raven-lx

#1
[Nexus One Android Development] rjhay22:
You can get OSmonitor from market or use adb

adb shell cat /proc/kmsg

Seems to me like you flashed Ivan's kernel and not raven's.
[Nexus One Android Development] Enndr:
Im showing as 4133mV right now. Im not running anything but OSmonitor.
[Nexus One Android Development] Wysie:
I'm not too sure if it's CM5.0.6 or this kernel, but I have gotten 2 random reboots so far :(. Thanks intersectRaven!
[Nexus One Android Development] lore2486:
thats your battery voltage not your avs cpu votl, look in the last tab thats where it says the volts it should say something like AVS 800mv@4
[Nexus One Android Development] lore2486:
what does this mean

- all mV steps have now been dropped in favor of 800mV which is now stable

- SLUB block allocation
[Nexus One Android Development] vegetaleb:
Anybody can confirm the latest version make BT stable on Desire Roms???
[Nexus One Android Development] lore2486:
my BT dosent work on modaco r21 then again it has never worked
[Nexus One Android Development] hugonz:
Is this what you're after:

https://www.codeaurora.org/gitweb/q...3c825011199a7bf1e;hb=refs/heads/msm-2.6.31.12

(line 37)

I'm not sure what you mean by "I believe it is safe to take it out"... if you take out the calls to that function, the voltage never actually gets changed by the voltage regulator and the AVS does nothing :-)
[Nexus One Android Development] vegetaleb:
How can I see what the actual voltage of my N1?
[Nexus One Android Development] die-hard:
in prompt digit adb shell cat /proc/kmsg

or

use osmonitor
[Nexus One Android Development] daedelus82:
after installing this kernel I am unable to open the 'messages' tab in osmonitor. It works fine under cyanogen's kernel, just not this one.. Has been that way since intersectRaven's very first kernels.. Anybody else had similar?

Other than that this kernel is rock solid. I love it.

edit: just tried osmonitor seems it's working for me again. lol. weird.
[Nexus One Android Development] Homotechual:
Anyone? help ?!
[Nexus One Android Development] FastMhz:
To be honest. I dont know if this Kernel is for your ROM. If so, ADB mode is when your phone has completely rebooted into the ROM.
[Nexus One Android Development] intersectRaven:
Hmmm...it seems I was sleepy when editing. :p
[Nexus One Android Development] intersectRaven:
I'm so disappointed with myself! The supposedly stable kernel was just the result of an incorrect editing of the AVS systems! This was why the "cleaned" version was unstable!!! I'm very sorry everyone!!! :(
[Nexus One Android Development] die-hard:
Really?

Pls real release stable version :)
[Nexus One Android Development] intersectRaven:
I'm working on it now. I replaced the voltage setting system to be more in-line with Code Aurora's kernel repository. Hopefully, the N1 implementation was the one causing the bugs. If not, well, we'll have another long wait for a stable AVS kernel. :(
[Nexus One Android Development] Wysie:
No worries man, you have been doing an awesome job :)! It's not like you fried a couple of CPUs anyway :P. Keep going!
[Nexus One Android Development] hugonz:
What?? Really? The Chromium kernel has ugly hacked voltage regulator drivers that don't use the kernel regulator framework; our kernel uses the proper approach. Don't break that!
[Nexus One Android Development] intersectRaven:
It's only for a test kernel. Anyways, we just need to pinpoint what is causing the instability with the current way of setting it versus the "ugly hacked voltage regulator driver" from code aurora if ever it proves stable. :p

Here is the "ugly hacked voltage regulator driver" AVS kernel for testing of stability:

http://www.mediafire.com/?myzgnzitont
[Nexus One Android Development] u3819013:
I'll test it.
[Nexus One Android Development] u3819013:
Re: [Kernel - .33.2]intersectRaven's Kernel (new Hybrid AVS) 04/18/2010 08:18am

wow! it kept on lowest votage 800-825mV. flashed for 5 mins.
[Nexus One Android Development] Royan:
No worries :-)

But what does this mean for people using the stable, "uncleaned" version (2.6.33_AVS-800mV_20100417_1756.zip)?

Is it svs?

Should we change to a different kernel?

brgds

Royan
[Nexus One Android Development] jblazea50:
no worries about you goofing on the last kernel, not a big deal; will try the test version now and hopefully it will work

did you see the latest from Hugonz about another battery saving tip for the camera? it's https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git;a=commit;h=8a68421a300878d729991c1db609a541910d2c70 and he says that it is more uptodate and may be easier to merge
[Nexus One Android Development] intersectRaven:
Yeah. It was SVS which was why it was so very stable. :(

Yeah I saw that. I'm just more focused on AVS for now especially with what happened with the supposedly stable release. I really should just concentrate on one thing at a time... :o
[Nexus One Android Development] hah2110:
You are doing good development at no cost to everyone, I think you have nothing to apologize for. Is a test version up that corrects this?
[Nexus One Android Development] Markdental:
But the SVS version you made was stable at 800mv, still pretty impressive.
[Nexus One Android Development] intersectRaven:
Yeah. Here it is:

http://www.mediafire.com/?myzgnzitont
[Nexus One Android Development] intersectRaven:
That was actually false. AVS received no complaints from the CPU since the static voltages were being applied so it kept lowering the voltages being displayed. :(
[Nexus One Android Development] Royan:
Hehe..

This might explain why my log is going bananas with avs entries.

Avs requests new voltages at least every second, but it's not getting it...:)

Still, lower frequencies at 800 is really stable.

Higher frequencies keep getting "set" to higher voltages...:)

I guess I'll try the "hack" when I get home tonight...

brgds

Royan
[Nexus One Android Development] hah2110:
Flashing now. Will report in.
[Nexus One Android Development] intersectRaven:
Upon further inspection of what hugonz previously noted, Ivan's observation and reading the code and comparing between the official N1 and Code Aurora's, I'm already getting a hunch on what is going wrong with the voltage setup. Anyways, if this "hack" works, it's one step to confirming my hunch. :)