yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] houzuoguo:
I'd like to say that I can now confirm that battery drains faster at 1Ghz when I undervolt to 1175mV.

It seems that undervolt too much doesn't always bring benefit.

I wish one day there'll be a kind of battery that runs out every week or longer, then I won't need to worry about battery life anymore :rolleyes:
[Nexus One Android Development] paulk_:
Amen!

And I wouldn't have to make my N1 huge and heavy with the Seidio extended battery any more!
[Nexus One Android Development] intersectRaven:
Try using the CAVS version and set your voltages manually since the default minimum voltages of AVS doesn't seem to work for you. :)
[Nexus One Android Development] intersectRaven:
New HAVS and CAVS Kernel released!

- updated AVS with CodeAurora changes

- merged latest CM kernel commits
[Nexus One Android Development] Basil 123:
@ch33kybutt

I tried flashing your last script, from recovery and it appeared to install, but the N1 was stuck at the bootscreen. Any advice?

Thanks

Basil
[Nexus One Android Development] k3vink3vin:
phone sleeps after flashing 2.6.37_AVS-CM7_CFS_20110218_1344.zip :D
[Nexus One Android Development] intersectRaven:
Again, use CAVS and adjust manually. :)
[Nexus One Android Development] k3vink3vin:
I don't want to fiddle with the voltage table myself though!

btw the phone seems to be sleeping and waking up fine with your newest AVS kernel so it's all good for me again :)
[Nexus One Android Development] ch33kybutt:
Which of IR's kernel's are you using? I have the same problem with his BFS kernels, always gets stuck at X logo, with or without my script.

In any case, might be you're having problems with boot-up tweaks in the script, so here's a recovery zip which has SS4N1 script disabled after 1st install. You'll have to run "sscfg" in adb or terminal emulator to enable it.
[Nexus One Android Development] Basil 123:
Sweet! Runs a treat.
[Nexus One Android Development] intersectRaven:
By-the-way, the latest kernels have the new compcache built-in so you just need to enable compcache in the CM performance settings section to enable it. Also, you need to have build 47 or higher of CM. :)
[Nexus One Android Development] hotweiss:
So is compcache is set to 18% by default, what do you recommend setting it to?

Edit: disabling Compcache makes my N1 a lot snappier
[Nexus One Android Development] dirwdirw:
:eek:

Really ??? !!!
[Nexus One Android Development] intersectRaven:
No surprises there. That earlier post was just to announce added features for those who really want to use compcache for whatever reason and not an outright endorsement. ;)
[Nexus One Android Development] hotweiss:
Thanks, that did the trick for me. The other one froze at the boot screen.
[Nexus One Android Development] discostu1:
I've been having problems with iR's kernels for the last few weeks on my rooted N1.

Up until CM 6.0.0 and the concurrent iR kernel of that time, I had absolutely no problems whatsoever.

Then a couple weeks ago I updated to CM 6.1.1 and got a new iR kernel, and my usb stopped connecting to my pc. After doing some testing, I figured out that it was the iR kernel that was the problem. If I installed CM 6.1.1 with no iR kernel, my usb worked fine. So I left it, knowing that a CM7 release candidate was near.

Then I got the CM7 RC1 that just came out a couple days ago. I got that and the new CM7 customizeable AVS iR kernel. I ran my phone with just CM7 for a couple days, the usb was working properly. Then I flashed the iR kernel, and my usb didn't stop working... Yay, right? That is, until I went to transfer some files to my sdcard. My usb is now slow as balls, transferring at ~150-175 KB/s opposed to the usual 1.5ish MB/s. Sigh.

I searched this thread and the only slow usb problems were from months ago, so maybe it's my phone? I've now done a complete wipe and reinstall of everything (because I forgot to NANDroid before flashing Gapps and it bugged on me :\ ) and I'm still seeing the same problems. Any ideas?

Here's a link to my original help thread in the N1 Q&A forum.

http://xdaforums.com/showthread.php?t=947236
[Nexus One Android Development] houzuoguo:
I remember the same issue happened with Wildmonk's kernel (101206 version if I remembered correctly), Wildmonk and his users solved it by flashing the kernel, reboot, then flash the kernel again.
[Nexus One Android Development] viper2g1:
With all this talk of cm7 will these kernels still work good with enoms rom? Or should I stick with his kernel?
[Nexus One Android Development] phewizzo:
I havent got the touchscreen bug since installing ur 2/17 and 2/18 kernel, let me not jinx myself though lol.
[Nexus One Android Development] intersectRaven:
If you're fine with having no USB mount notification and video recording, use mine, otherwise... :)

I'll jinx it for you...you will experience the touchscreen bug soon... :p

What release are you using by-the-way? If you're on CAVS, then it's because AVS isn't "active" unless you manually edited the voltages with the script a few posts back. :)
[Nexus One Android Development] paulk_:
You don't get the touchscreen bug if you don't use AVS? o.o
[Nexus One Android Development] phewizzo:
Im using the AVS and not CAVS, I always got touchscreen problems with AVS or NON-AVS kernels but since your 2/17 release theres a noticable speed increase which I guess makes the phone more smoother for faster typing, I used to always get touchscreen bug fix every 10 minutes or so cuz im a big texter, but I havent got it since your 2/17 kernel and now im on 2/18 and still the same. LOL.
[Nexus One Android Development] k3vink3vin:
Just now I rebooted my phone and once it's completed the reboot I unlocked it, pulled down notifications and attempted to read some unread emails and then the device froze right there. It just got stuck there and won't do anything. There is haptic feedbacks from the touch capacitive buttons, and power button switches on/off the screen, but it's stuck at the same screen no matter what I do.

CM7 #47, 2.6.37_AVS-CM7_CFS_20110218_1344.zip

logcat: http://pastebin.com/ej6BgnNL
[Nexus One Android Development] miguelm75:
had the same problem as Basil 123, but ch33kybutt's advice didn't work for me. i was using this kernel: 2.6.37_AVS-CM7_CFS_20110218_1344.zip
[Nexus One Android Development] intersectRaven:
That's not CAVS so ch33kybutt's advice really won't work. Try the ones with CAVS on them. :)
[Nexus One Android Development] intersectRaven:
New AVS and CAVS Kernels uploaded! synced with CM's kernel updates and removed mutex locks from the imported regulator code... :)
[Nexus One Android Development] phewizzo:
I will try this IR, i havent had the touchscreen bug in 3 days :-)
[Nexus One Android Development] navahoo:
Just installed the latest avs cfs on my n1 with cm7 and all running nice and easy so far!

And as my gf got a cm7 on her Htc Desire and those devices are quite simliar im wondering if this kernel will run there too?

Thx and sorry for noobing... ;)
[Nexus One Android Development] miguelm75:
i'm sorry, i didn't read properly :-) thank for your tip. will test soon.

BTW: maybe in first/second post any describing of WIFIFAST and NOBOOST?
[Nexus One Android Development] ch33kybutt:
@IR, thanks a bunch for your work on CAVS kernels, giving me great balance between performance/economy when I use it with my SS4N1 script.

Just one thing though, when updating voltages for all freqs (128 to 1136 MHz), debug messages on /proc/kmsg only up to 1075 MHz ...

<4>[ 2968.120000] Manual adjustment begin for 1036Mhz
<4>[ 2968.120000] Manual adjustment success for 1036Mhz
<4>[ 2968.120000] Minimum: 1175mV
<4>[ 2968.120000] Maximum: 1275mV
<4>[ 2968.220000] Manual adjustment begin for 1075Mhz
<4>[ 2968.220000] Manual adjustment success for 1075Mhz
<4>[ 2968.220000] Minimum: 1175mV
<4>[ 2968.220000] Maximum: 1275mV

Debug messages for 1136 MHz not shown.
[Nexus One Android Development] intersectRaven:
I don't really overclock so maybe something in the AVS code is preventing it from setting or something. If it was just AVS, maybe your CPU is signalling that it won't adjust voltage for those frequencies so AVS doesn't bother. :)
[Nexus One Android Development] paulk_:
It's not just when overclocking, houzuoguo and I have the same problems when underclocking or running at 998 - at 998 the max frequency it will scale up to 960, same for any underclocked frequency.

Have yet to check whether this also occurs on other kernels (I flash your kernel immediately after flashing my rom lol).

[EDIT] Just to mention, it doesn't matter whether I set the voltages as AVS or CAVS, it still doesn't hit the max voltage specified.
[Nexus One Android Development] ch33kybutt:
Not exactly true. If CPU frequency scaling is viewed via SetCPU, OS Monitor or just monitoring /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq every second, it does go up to specified maximum, (e.g. 998MHz). But if you check debug messages on /proc/kmsg, AVS settings only performed for freqs up to 1-step lower than specified max freq (e.g. 960MHz), see below as example...

<4>[ 6083.870000] AVS setting V to 850 mV @128 MHz
<4>[ 6083.890000] AVS setting V to 950 mV @499 MHz
<4>[ 6083.990000] AVS setting V to 850 mV @128 MHz
<4>[ 6084.530000] AVS setting V to 925 mV @460 MHz
<4>[ 6084.550000] AVS setting V to 1275 mV @960 MHz
<4>[ 6084.650000] AVS setting V to 850 mV @128 MHz
<4>[ 6084.960000] AVS setting V to 1075 mV @537 MHz
<4>[ 6085.060000] AVS setting V to 850 mV @128 MHz
<4>[ 6085.560000] AVS setting V to 1075 mV @768 MHz
<4>[ 6085.580000] AVS setting V to 1275 mV @960 MHz
<4>[ 6085.680000] AVS setting V to 850 mV @128 MHz
<4>[ 6086.310000] AVS setting V to 1075 mV @537 MHz
<4>[ 6086.330000] AVS setting V to 1100 mV @614 MHz
<4>[ 6086.350000] AVS setting V to 1275 mV @960 MHz

So CPU frequencies do scale correctly between specified min & max, and I'm just guessing that there is probably simply some issue at how AVS setting for each freq is detected and debugged.
[Nexus One Android Development] paulk_:
I see! I've never checked anything other than /proc/kmsg, and I don't even have setcpu installed anymore lol.
[Nexus One Android Development] intersectRaven:
I think I found the issue. I'll fix this in a later release. :o
[Nexus One Android Development] k3vink3vin:
2.6.37_AVS-CM7_CFS_20110220_2112.zip = insomnia on my N1

2.6.37_CAVS-CM7_CFS_20110220_2124.zip = sleeps no problem :)
[Nexus One Android Development] miguelm75:
tried several CAVS kernels with SS4N1, but still freeze at "X" bootscreen. don't know, what's going on...
[Nexus One Android Development] hotweiss:
Try this version:

http://xdaforums.com/showpost.php?p=11446892&postcount=5022
[Nexus One Android Development] miguelm75:
i already did, but still no luck :]
[Nexus One Android Development] ch33kybutt:
I see you're using CWM recovery. I've only tested the update.zip on RA recovery. So that may be the reason. Let me load up CWM and test ...

Nope. Works fine with CWM 2.5.1.4. So problem lies elsewhere. Although you may actually consider changing your recovery to RA 2.2.1, which totally pwns CWM 2.5.1.4 IMHO.
[Nexus One Android Development] miguelm75:
using Amon RA 2.2.1, kernel 2.6.37_CAVS-CM7_CFS_20110220_2124.zip and SS4N1, but still freeze at "X" screen. nevermind, will stay at kernel and not using SS4N1. thanks anyway :)
[Nexus One Android Development] intersectRaven:
Have you edited the SS4N1 script's config to use more conservative values? Maybe the values are too much for your device. :confused:
[Nexus One Android Development] myplague:
my device will not boot if SS4N1 is enabled. So what I have been doing is disable the script before I shut off my phone.
[Nexus One Android Development] ch33kybutt:
Might be one of the tweaks is not working well for you. You can try to disable all the tweaks (maxphone, dewonkifier, noatime, storage/io, ui/homescreen, network) and turn back on one-by-one to find which particular one is causing your boot-up problem.
[Nexus One Android Development] intersectRaven:
I found the cause of the HAVS 998Mhz not setting thing and it's bad. It may actually be the cause as to why HAVS isn't stable for some people. Anyways, I'm gonna work on it now so hold tight. :o
[Nexus One Android Development] intersectRaven:
Fixed kernels are up. :)
[Nexus One Android Development] ch33kybutt:
New kernel works great, thanks! Full range of frequencies (128-1136MHz) now shown in /proc/kmsg. I was wondering why 256MHz was in your CAVS table but didn't show up in /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies.
[Nexus One Android Development] intersectRaven:
Yeah. That was a major oversight on my part. That actually made all frequency limits be the one for the previous frequency instead of the proper ones which may be the cause for some of the problems with AVS. :o
[Nexus One Android Development] jameztcc:
Hi iR,

Got a couple of auto reboots after a while with the CAVS, just remembered manually echo voltages to avs_adjust for 800mhz.

e.g.

[ 643.880000] Manual adjustment success for 128Mhz

[ 643.880000]	Minimum: 825mV

[ 643.880000]	Maximum: 875mV

http://pastebin.com/HpeHMBT8

thanks,

James Tan
[Nexus One Android Development] intersectRaven:
That just means that your CPU can't handle those voltages. Try increasing them.
[Nexus One Android Development] ch33kybutt:
Kernel-panics are par for the course. Keep experimenting until you find a min/max voltage combination for each frequency that's stable for your phone's CPU.
[Nexus One Android Development] jameztcc:
Thanks, guess besides finding the stable min/max, there's also the consumption of power due to undervolting.
[Nexus One Android Development] intersectRaven:
Yeah. Although the study has been done by kmobs already and the consensus is that anything below 925 is hurtful due to signal/power trade-offs. :)
[Nexus One Android Development] miguelm75:
i was using "moderate battery savings", so i don't think, that values are problem. it's interesting, that reboot and stuck at "X" screen was after using Quadrant benchmark. is there a need to wait for new version of SS4N1 or may i try one more time with new kernels?
[Nexus One Android Development] intersectRaven:
Try with the newer kernels since they have the correct limits set to the frequencies so that may have an effect on stability. :)
[Nexus One Android Development] ch33kybutt:
Just to point out that the presets in SS4N1 are under the assumption that you use the phone in relatively good radio-strength locations. If you set too low min/max voltages, and you are in a weak radio-strength location, then what will most likely happen is that the under-powered radio hardware will struggle to maintain an adequate signal, and will most likely end up drawing even more power from the battery. So best to check number of bars and dB strength wherever you are, and adjust accordingly.
[Nexus One Android Development] britoso:
2.6.37_CAVS-CM7-NOBOOST_CFS_20110220_2124 is working well for me on CM-7 build 3

First time I'm on a CFS scheduler :)

USB transfer via adb seems fast.
[Nexus One Android Development] ch33kybutt:
Fixed a typo in the presets (Awake mode max freq was 9984000 ... one zero too many :o). Probably the reason why you couldn't boot. So here's fixed version of SS4N1...

As before, it's DISABLED by default after 1st installing, so you'll have to run adb shell or terminal emulator and run "sscfg" and ENABLE it ...

# sscfg

**************************************************
SSCFG: Home Screen
**************************************************
This utility configures the SS4N1 script
[/etc/init.d/98ss4n1] which auto-switches
settings based on phone-state (AWAKE/SLEEP).

Please choose an option below and press Enter.
[1] Enable SS4N1
[2] Display settings
[3] Load PRESET profiles
[4] Customize settings
[5] Save/View/Load settings on sdcard
[6] *** Apply changes and exit ***
[Enter] Exit without applying changes
[Nexus One Android Development] theloginwithnoname:
IR, top job - good, low "per hour" battery drain and good performance. Nice one!
[Nexus One Android Development] miguelm75:
still no progress there... maybe my phone is just "special"? ;-)

anyway thank you very much for your effort. i will install any AVS kernel. BTW: any change in "settings"/"Cyanogen settings"/"Performance"/"CPU settings" will affect IR kernel settings? sorry, if my question is n00bish.
[Nexus One Android Development] jameztcc:
Thanks for CAVS kernel. Managed to get good battery e.g 3% loss per hr screen off though phone failed to sleep for whatever reason (cm7 nightly #3). If using stock / avs only kernel, the loss is > 10%. Thanks!
[Nexus One Android Development] kieranc:
If I could make a suggestion, under 'Customize settings', '[1] Enable/Disable ALL features' could be changed to '[1] Enable/Disable features'

I keep thinking it's going to switch everything off....
[Nexus One Android Development] ch33kybutt:
Good point. Will be changed next version.
[Nexus One Android Development] k3vink3vin:
What is the average battery consumption (current draw) for you guys when the device is in sleep state with the screen switched off?

My average is about 9mA, lowest is 5mA, according to "Battery Monitor Widget".

http://pastebin.com/Es6gfL39

Running AVS kernel.
[Nexus One Android Development] ultraviolet74:
I'm using 2.6.37_CAVS-CM6_BFS_20110222_1155.zip

but USB as storage doesn't work, only to charge... (doesn't appear to enable usb)

I have Cyanogen 6.1.1 installed.
[Nexus One Android Development] intersectRaven:
2.6.37.1 AVS Kernels are up! :)
[Nexus One Android Development] jameztcc:
Thanks! Using the CAVS now.
[Nexus One Android Development] rickh925:
Long Boot Time at X Screen

I've been wanting to get back to IR kernels, wififast in particular, but have been having problems being stuck at the X screen after flash. Well, apparently I was being too impatient. I decided to let the phone sit at the X for a max of 15 minutes just to be sure. In the past after about 30 seconds I would start the battery pull option.

Presto, it took exactly 26 seconds to go from the X screen to the CM7 boot video. While I'm glad that it works now (T-Mobile WiFi Calling), it only takes about 7 seconds to go from the X screen to CM7 boot video running the stock kernel.

Is there something going on with the boot with IR? Anyway, looking forward to playing the voltage/freq game in my "free" time!

Rick
[Nexus One Android Development] kieranc:
Protip: if you UV too much and it wont boot, don't nandroid, just reflash ss4n1 to restore default settings :-)
[Nexus One Android Development] bimasakti85:
Just be patience. It can took up to 5 minute to boot up after flashing IR's kernel.
[Nexus One Android Development] rickh925:
Yes. I am much more patient now. I did have to pull the battery again tonight after trying to flash a theme. Didn't have time to look into it so I just restored.
[Nexus One Android Development] kieranc:
I don't think it should take 5 minutes if it's working right. Flashing a ROM can result in a slow boot as it rebuilds dalvik-cache etc, flashing a kernel should have no such effects, unless something is broken/borderline.
[Nexus One Android Development] cloversis:
What's the difference between wififast and noboost as well as not mentioned?

Thz.
[Nexus One Android Development] ellesshoo:
Wifi fast= modified wifi performance / policy for T-Mobile wifi calling issues. May use more battery.

No boost = no audio volume boost. Some think the stock (Google) audio is good (me) and some feel its not loud enough. With the regular kernels people around me can hear the person I'm talking to from a few feet away even with volume lowered. I like no boost.
[Nexus One Android Development] mezmer1ze:
I have to quote you, got the same problem with SS4N1 on my N1, applied moderate battery savings and it gets stuck on X whenever I reboot. My phone CPU is definitely very good as I was running 800 mV SVS kernels before without any problems and signal strength is full in the terms of displayed bars.
[Nexus One Android Development] ch33kybutt:
Try DEFAULT preset (no UV) and then reboot ...
[Nexus One Android Development] houzuoguo:
Hi IR :rolleyes:

Not sure whether this is a CM nightly issue or kernel's issue, I upgraded from CM7 nightly #6 to #7 together I upgraded from your 0223 kernel to 0224 kernel, the system isn't stable as I got 2 random reboots..

I didn't change my voltage table but I'll try a bit higher voltage to see if it caused the problem
[Nexus One Android Development] mezmer1ze:
Strange, default preset hangs on X too :confused:

edit: When I change the settings, apply them, disable SS4N1, it restarts just fine.
[Nexus One Android Development] ch33kybutt:
Might be one of the tweaks. Try disabling all of them.
[Nexus One Android Development] mezmer1ze:
Ok so it must be one of the features, because with all of them disabled it works fine.

I'll try to turn them on one by one and post results later.
[Nexus One Android Development] pengu1n:
which build include the vpn fix which introduced in the drsire forum asop kernel thread? thanks
[Nexus One Android Development] intersectRaven:
What VPN fix? :confused:
[Nexus One Android Development] pengu1n:
In the Desire dev sub forum, a thread tagged as [asop] xx kernel says he has some fix for vpn issue for cm7.

cm7 can't connect to vpn server since it has been published.

sorry i can't provided url for the link, have laptop or pc now
[Nexus One Android Development] mezmer1ze:
Ok I have narrowed it down to these 2 features:

Dialer optimization (0)

Autoswitch between sleep and awake (6)

With any of these 2 enabled the phone doesn't start and stays at X...
[Nexus One Android Development] mindfrost82:
Will the CM7 versions work with a rooted OTA Gingerbread install?

I'm one that needs the audio boost :)
[Nexus One Android Development] intersectRaven:
The video recording may not since there were modifications for 720p. :)
[Nexus One Android Development] ch33kybutt:
Funny that. If Autoswitch is disabled, then you're not getting the CAVS regulation.

If you just want the CAVS features, I'd suggest the following configuration ...

**************************************************
SSCFG: Enable/Disable features
**************************************************
[0] Enable Dialer optimization
[1] Enable Dewonkifier (a1026 mic)
[2] Enable Remount with noatime
[3] Enable Storage/IO tuning
[4] Enable UI/Homescreen optimization
[5] Enable Network performance tuning
[6] Disable Autoswitch between AWAKE/SLEEP modes
[7] Disable Autoswitch for CAVS
[8] Enable Autoswitch for CPU scheduler
[9] Enable Autoswitch for CPU frequency governor
[a] Enable Autoswitch for Virtual Memory
[?] HELP-INFO for all of the above features
[Enter] Return to previous screen

i.e. enable only [6] and [7]
[Nexus One Android Development] steve.garon:
Just a quick question. I'm running latest intersect kernel and getting a load of IO error. Has anyone had the same issues with with the kernel or could that be related Cyanogenmod??
[Nexus One Android Development] McFroger3:
Yea I'm getting some weird stuff happing too, like when I reboot it wont load anything until I unlock the screen. Ill get a phone call, it will freeze and I can't unlock the screen or I can unlock it and I cant get to the phone call, I'll click the notification in the bar, open the phone app, nothing, then the trackball will blink like I'm getting a phone call constantly, only way to stop it is to hard reboot. This is on the newest CM nightly #7.