yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] myplague:
can someone please help me with the auto script?

I have this in my file

#!/system/bin/sh
if [ $1 == "on" ]
then

echo "128000,850,875" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "245000,850,875" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "256000,975,900" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "384000,875,925" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "256000,975,900" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "422400,900,950" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "460800,900,950" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "499200,900,950" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "537600,925,950" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "576000,925,950" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "614400,950,1000" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "652800,950,1025" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "691200,975,1050" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "729600,1000,1075" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "768000,1025,1075" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "806400,1050,1125" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "844800,1075,1125" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "883200,1075,1150" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "921600,1100,1150" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "960000,1100,1175" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "998400,1100,1175" > /sys/module/avs/parameters/avs_adjust

fi

I copied the previous instruction on this thread and I tried to piece together the instruction from the tasker thread. I only get one message that AVS started and then nothing else

Thanks
[Nexus One Android Development] houzuoguo:
paste the following into a file <filename>:

echo "128000,850,875" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "245000,850,875" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "256000,975,900" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "384000,875,925" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "256000,975,900" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "422400,900,950" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "460800,900,950" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "499200,900,950" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "537600,925,950" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "576000,925,950" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "614400,950,1000" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "652800,950,1025" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "691200,975,1050" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "729600,1000,1075" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "768000,1025,1075" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "806400,1050,1125" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "844800,1075,1125" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "883200,1075,1150" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "921600,1100,1150" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "960000,1100,1175" > /sys/module/avs/parameters/avs_adjust
for a in $(seq 0 1 10000)
do
done
echo "998400,1100,1175" > /sys/module/avs/parameters/avs_adjust

then run:

sh <filename>

By the way IR, to use avs_adjust, shall I choose "CAVS" kernel?
[Nexus One Android Development] intersectRaven:
Yeah you should use the CAVS. The non-CAVS have a fixed AVS setting for novice users. :)

*I'm thinking of actually setting aside my hate for Java and programming a UI for this...can someone else maybe do it? :p
[Nexus One Android Development] houzuoguo:
I too hate Java, it's too cumbersome for me :rolleyes:

I wish for a mobile operating system that runs on Python :p
[Nexus One Android Development] intersectRaven:
Read back a few pages. :p
[Nexus One Android Development] seanowns:
825v seems rock solid for me.
[Nexus One Android Development] apacheo:
Completely missed that, even though I've been following the thread.. it moves quickly sometimes :)

I spoke too quickly about the 800mv kernel though... a bit unstable on my N1. Reverted to the 900mv kernel for now and we'll see how the savings go there :)

Need stability, as its kind of hard to flash different kernels without a laptop handy :)

EDIT: Given that I'm home all day today I might play with the 825 and 850 and see whether they are stable.
[Nexus One Android Development] intersectRaven:
I know. Just last night 2 pages were added to the thread while I was sleeping. :p
[Nexus One Android Development] r34p3rex:
Yea i know, but I meant, is there anyway to limit the voltage when the CPU is at 998? :D Instead of having it at 1.25, would it be possible to limit it to say, 1100 or maybe even 1000?
[Nexus One Android Development] Wysie:
I've flashed without wiping the battery stats or cache for 850 and it's working well. Just flashed 800 and seems to be fine so far too. Will report back if it's working well. I've the same HBOOT as you, intersectRaven (if it makes any diff).
[Nexus One Android Development] intersectRaven:
Uhmm...no? Well, there is but that wouldn't be wise since AVS tries to follow the inner whining of the CPU as to how much juice it wants. If you lower the maximum voltage to that (fyi, current maximum is 1275mV) I'm pretty sure your processor will throw a really bad tantrum. :p

Good for you! I don't think there are people with different HBOOT as ours though since I think that's the standard release version and it isn't flashable (I think...). :D
[Nexus One Android Development] exelinguy:
I am running stable on 800 but realized that every now and then my phone was rebooting when I used power governor. Perhaps the Desire UI requires more power when it sleeps. The phone is perfectly stable when awake.

I will try the 850 kernel to see if it still keeps rebooting while power governor is on.
[Nexus One Android Development] britoso:
I started with 800, then 825...only the 850 one booted.
[Nexus One Android Development] TFJ4:
800 is ROCK SOLID for me, might you pm me (or post if you don't care) a 775 version?
[Nexus One Android Development] LunatikBunnie:
Hrng, I stand corrected, after using 925mV for 2 hours, my N1 did a backflip and flopped into a reboot. Not I'm not sure if i'll ever want to play with AVS anymore
[Nexus One Android Development] britoso:
had a reboot with the 850, on 875 now... hope its stable :)
[Nexus One Android Development] veescript:
i'm running the 800mV AVS fine for now, i'll update if I'll have some problems...

i have the stable cyanogen mod rom

Edit 1: the wifi works after doing the trick

Edit 2: Done a Short Bench on SetCPU --> 280ms average

Edit 3: Doing now a stress test to see if the 800mV kernel is good or not... i will tell you later

Edit 4: The stress test was successfull! NO ERRORS...now i will stress it my self :P
[Nexus One Android Development] intersectRaven:
Good luck! Post again if you're one of the lucky ones! :D

I think 800mV is the lowest that the regulator supports if I'm not mistaken. :)
[Nexus One Android Development] veescript:
I had just now the first reboot....hope it will be the first and the last one..

hmmm...second reboot....the nexus reboot itself when it's locked OMG!
[Nexus One Android Development] intersectRaven:
Guess 800mV isn't for you then... :(
[Nexus One Android Development] veescript:
it is normal that reboots only when it is locked ? because it has not rebooted when i was using it....then i'm now trying the 825mV
[Nexus One Android Development] intersectRaven:
It's not normal. You should be stable even while locked. :)
[Nexus One Android Development] veescript:
mmh...now it's not rebooting still with 800mV
[Nexus One Android Development] intersectRaven:
Try it for a few more reboots. They say that a few spontaneous reboots are needed for AVS to calm down. :)
[Nexus One Android Development] ellesshoo:
Please UI. That would be on a whole new level.
[Nexus One Android Development] myplague:
not working for me:( Weird I was able to edit the values one by one
[Nexus One Android Development] redstar3894:
You might want to take a look at the battery calibration app, since they're using a similar method (through sysfs) as you are here... that's actually what I had in mind when you first mentioned you were looking into this... that an app would be a good idea here... :p

I am a registered developer if anyone comes up with something and wants it on the market... ;)

I agree... been trying to teach myself various forms of coding and while everyone tells me I should learn Java to start, I've been going through Google's Python class in my spare time and I have to say, I think I'm beginning to see why houzuoguo is in love with Python... it does work pretty well... :p

Maybe once I get up to speed we can start working on rewriting android in Python... :p
[Nexus One Android Development] ch33kybutt:
Instead of

for a in $(seq 0 1 10000)
do
done

we can just use

usleep 100000

to sleep for 100000 microseconds (or 0.1 second)

Not good in Java, so I just wrote a simple bash startup script which automatically changes UV levels based on screenstate. Will post it here if results are good.

Basically, it runs at startup from /etc/init.d, loads user settings from /sdcard/cavs.conf and then runs a while loop which checks screenstate from /sys/power/wait_for_fb_wake and /sys/power/wait_for_fb_sleep.
[Nexus One Android Development] yang901:
Great! looking forward to your results. It's interesting to tune these value to save power, mine N1 is too sensitive to the low setting on voltage though.
[Nexus One Android Development] houzuoguo:
Here's my latest voltage table:

cd /sys/module/avs/parameters
echo 128000,875,875 > avs_adjust
sleep 1
echo 245000,875,900 > avs_adjust
sleep 1
echo 256000,875,900 > avs_adjust
sleep 1
echo 384000,900,925 > avs_adjust
sleep 1
echo 422400,900,925 > avs_adjust
sleep 1
echo 460800,925,950 > avs_adjust
sleep 1
echo 499200,925,950 > avs_adjust
sleep 1
echo 537600,950,1000 > avs_adjust
sleep 1
echo 576000,975,1025 > avs_adjust
sleep 1
echo 614400,1000,1050 > avs_adjust
sleep 1
echo 652800,1025,1075 > avs_adjust
sleep 1
echo 691200,1025,1075 > avs_adjust
sleep 1
echo 729600,1050,1100 > avs_adjust
sleep 1
echo 768000,1050,1100 > avs_adjust
sleep 1
echo 806400,1075,1125 > avs_adjust
sleep 1
echo 844800,1075,1125 > avs_adjust
sleep 1
echo 883200,1100,1150 > avs_adjust
sleep 1
echo 921600,1100,1150 > avs_adjust
sleep 1
echo 960000,1125,1175 > avs_adjust
sleep 1
echo 998400,1125,1175 > avs_adjust

been running it for more than 24 hours, very stable for me :rolleyes:

By the way I notice that when I play a game, if CPU is running at 950mV 500Mhz, battery is drained about 40mAh faster than running at 1175mV 1Ghz, could anyone please give a hint on what caused it?
[Nexus One Android Development] paulk_:
I'd say it's most likely something to do with a processor that's capped at a lower speed having more stress placed upon it when playing the game, since it's struggling to process the graphics, logic and commands, but when running at 1GHz, it isn't being pushed as much.
[Nexus One Android Development] ch33kybutt:
Thanks to IR, for helping me make such productive use of my otherwise mundane life for the past few hours ;). Found out the hard way that any UV for OC freqs (above 998400) results in almost automatic bootloops for me (on CM7 latest nightly). So I had to limit min/max freq to 128000/998400, with a screen-off profile of 128000/384000, and so far so good.

I've written a simple script (based mostly on collin_ph's battery saver, since I too, share IR's hatred for Java) which let's you specify voltages on the fly and automatically changes voltage values whenever screen is on or off.

It's split into 3 main files...

/system/etc/init.d/98cavs - Startup script which checks phone-state (AWAKE/SLEEP) and sets UV accordingly

/system/etc/cavs.conf - Initialization file for /etc/init.d/98cavs

/system/bin/cavs - Configuration script for /etc/init.d/98cavs
​

To configure the CAVS script, run ADB on yer PC or terminal emulator on yer phone...

$ su
# cavs

and you'll get the following options

[1] Disable CAVS script
[2] Display current settings
[3] Load PRESET UV profiles
[4] Customize Undervolt settings
[5] Save/View/Load settings on sdcard
[6] *** Apply changes and exit ***
[Enter] Exit without applying changes

Instructions are provided inline, but somewhat sparingly, since most of it is self explanatory. But instead of specifying a specific min/max voltage for each frequency, you specify a delta value which will be subtracted from the default voltage for each frequency. Much simpler to script that way.

e.g.

If you set AWAKE_MIN_UV=100 & AWAKE_MAX_UV=50

>> [ frequency, min voltage, max voltage ]

>> [ 245000, (950-100), (1000-50) ]

>> [ 245000, 850, 950 ]

These are the default settings in /system/etc/cavs.conf (without any undervolting)...

AWAKE_MIN_UV=0
AWAKE_MAX_UV=0
SLEEP_MIN_UV=0
SLEEP_MAX_UV=0

And these settings work pretty well for me...

AWAKE_MIN_UV = 75
AWAKE_MAX_UV = 25
SLEEP_MIN_UV = 200
SLEEP_MAX_UV = 100

Note that the above is WITHOUT OVERCLOCKING. Anytime I try to increase max freq above 1GHz with any undervolting, reboots-on-panic galore ...

Anyway, it's time to hit the hay, so here's the recovery zip (provided as-is, use at your own risk, won't be held responsible, blah blah blah, etcetera etcetera ...)
[Nexus One Android Development] myplague:
I can not get my n1 to boot with this!
[Nexus One Android Development] ch33kybutt:
Not all CPUs will be able to undervolt off the bat, so I've updated my previous post with updated recovery.zip which has default settings with no undervolting. Up to you then to slowly scale up the UV levels ...
[Nexus One Android Development] myplague:
Thanks

That's weird my CPU has always been able to handle extreme undervolting

EDIT: Still not booting!
[Nexus One Android Development] ch33kybutt:
From your earlier posts, I see that you had issues with getting manual scripts to work via adb. Were you able to succeed with that? If not, then this method probably won't work for you.
[Nexus One Android Development] myplague:
Yep any previous scripts did not work for me but I am able to use the terminal and root explorer to input manually.

Thanks for your help
[Nexus One Android Development] houzuoguo:
CM7 has hit RC-1 today

I notice there were few commits regarding kernel of CM7 on @cmsrc :rolleyes:

Would IntersectRaven please release an updated kernel? Much appreciated!
[Nexus One Android Development] myplague:
I feel like an idiot rite now lol

Script works fine on my phone it was just that I was using an older IR kernel. I downloaded the last one that had CAVS in the title which apparently was not the lastest!
[Nexus One Android Development] ch33kybutt:
No worries, dude. We've all had our off-days, some even off-weeks/months/years. But I digress .... I'm still not able to successfully UV+OC without getting reboots, so hope it works out better for you.
[Nexus One Android Development] intersectRaven:
Just set the sort of my MediaFire folder to date descending and find the ones with CAVS in the title to get the latest. :)
[Nexus One Android Development] myplague:
no overclocking for me, I do not care about the extra speed:D
[Nexus One Android Development] ch33kybutt:
1. SetCPU doesn't like OverClocking+UnderVolting

2. My phone doesn't like SetCPU

At least one of the above is true (probably both). OC+UV only works if I modify the script to also handle dynamic CPU freq scaling. Doing OC+UV with SetCPU is a 100% guarantee of panic-reboots for me. Thus I've done away with SetCPU. The new settings below work quite well for me using IR's most excellent CAVS kernels...

AWAKE_MIN_UV=100

AWAKE_MAX_UV=0

AWAKE_GOVERNOR=interactive

AWAKE_MIN_FREQ=128000

AWAKE_MAX_FREQ=1113600

SLEEP_GOVERNOR=conservative

SLEEP_MIN_FREQ=128000

SLEEP_MAX_FREQ=245000

SLEEP_UP_THRESHOLD=99

SLEEP_MIN_UV=250

SLEEP_MAX_UV=100

Makes my phone behave the way I want it to: responsive when I'm using it and economical on battery when I'm not. Need to clean up the script (added other stuff such as optimizations for IO scheduler, TCP connections, CPU scheduler, Virtual Memory and dialer process) so will post an update later ...

Btw, the freq/volt table posted earlier was for the 2.6.35 kernel. Here's the actual freq/volt table for 2.6.37...

{ 19200, 950, 975 },

{ 128000, 950, 975 },

{ 245000, 950, 1000 },

{ 256000, 950, 1000 },

{ 384000, 950, 1025 },

{ 422400, 950, 1050 },

{ 460800, 975, 1050 },

{ 499200, 1000, 1075 },

{ 537600, 1000, 1075 },

{ 576000, 1025, 1100 },

{ 614400, 1050, 1100 },

{ 652800, 1075, 1125 },

{ 691200, 1100, 1150 },

{ 729600, 1125, 1175 },

{ 768000, 1150, 1200 },

{ 806400, 1175, 1225 },

{ 844800, 1200, 1250 },

{ 883200, 1200, 1275 },

{ 921600, 1225, 1275 },

{ 960000, 1225, 1275 },

{ 998400, 1225, 1275 },

{ 1036800, 1275, 1275 },

{ 1075200, 1275, 1275 },

{ 1113600, 1275, 1275 },

{ 0 },
[Nexus One Android Development] ch33kybutt:
Done with cleaning up the script. In addition to auto-switching CPU voltage-levels based on phone-state (AWAKE/SLEEP), it also auto-switches settings for CPUsched, CPU governor and Virtual Memory. Since it's controlling more than just voltages for IR's CAVS kernel, I've renamed it to SS4N1 (ScreenState for N1).

So if you are using earlier N1CAVS script, please undo it before you install SS4N1.

How to configure SS4N1...

- from PC, use adb shell

- from phone, use terminal emulator

$sscfg

**************************************************
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] Disable SS4N1
[2] Display current 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

Just follow on-screen prompts from there onwards. All tweaks can be disabled if you don't want to use them...

**************************************************
SS4N1: Enable/Disable features
**************************************************
[0] Disable Dialer optimization
[1] Disable remount with noatime
[2] Disable storage/IO tuning
[3] Disable UI/homescreen optimization
[4] Disable network perf tuning
[5] Disable autoswitch for ALL settings
[6] Disable autoswitch for Undervolt settings
[7] Disable autoswitch for CPUsched settings
[8] Disable autoswitch for CPUFREQ settings
[9] Disable autoswitch for VM settings
[Enter] Return to previous screen

And also provided PRESET profiles for those who don't want to go through so many options.

**************************************************
SS4N1: PRESET profiles
**************************************************
Select to view & load preset
[1] DEFAULT settings
[2] High Battery Savings
[3] Moderate Battery Savings
[4] Moderate Performance
[5] High Performance
[6] Maximum Overclock Undervolt (UNSTABLE?)
[7] UNDO changes
[ENTER] Load preset and continue

Just remember to always select [6] *** Apply changes and exit *** or your changes won't be applied.

And same disclaimers again ...

(provided as-is, use at your own risk, won't be held responsible, blah blah blah, etcetera etcetera ...)

@intersectRaven: Apologies for hijacking your thread, but not sure if this would be well-received by many users, so hope you don't mind :) In any case, it does work really well for me with your CAVS kernels. Much better than SetCPU which reboots with any OC+UV setting.
[Nexus One Android Development] intersectRaven:
Stop hijacking my thread!!! ;p

Seriously, it's fine. It's for CAVS anyway so it's still on topic. I've also been busy these past few days so I had no time to code. Keep it up since what you're doing is why this forum exists! :p
[Nexus One Android Development] jolinnard:
I want to test your last update, but I can not boot... Can I apply last "patch" to the new version?
[Nexus One Android Development] houzuoguo:
The latest kernel compiled by gcc4.4.6 runs smoothly :)

Sent from my Nexus One
[Nexus One Android Development] redstar3894:
Yay! Someone noticed the upgrade!!! :D

Sent from my Nexus One
[Nexus One Android Development] phewizzo:
The new kernel is running SUPER FAST, good job guys.
[Nexus One Android Development] theloginwithnoname:
AND battery life seems great under CM7 RC1 too! bravo.
[Nexus One Android Development] houzuoguo:
:rolleyes:

Does Current Widget always give correct reading? (Despite the delay)

I get usually lower Amps reading (about 30% lower) when using my voltage table, but I don't notice overall battery life increment at all! I wonder why :rolleyes:

By the way, my latest voltage table is

cd /sys/module/avs/parameters
echo 128000,875,875 > avs_adjust
usleep 100000
echo 245000,875,900 > avs_adjust
usleep 100000
echo 256000,875,900 > avs_adjust
usleep 100000
echo 384000,900,925 > avs_adjust
usleep 100000
echo 422400,900,925 > avs_adjust
usleep 100000
echo 460800,900,950 > avs_adjust
usleep 100000
echo 499200,925,950 > avs_adjust
usleep 100000
echo 537600,925,950 > avs_adjust
usleep 100000
echo 576000,925,950 > avs_adjust
usleep 100000

echo 614400,950,975 > avs_adjust
usleep 100000
echo 652800,975,1000 > avs_adjust
usleep 100000
echo 691200,1000,1025 > avs_adjust
usleep 100000
echo 729600,1025,1050 > avs_adjust
usleep 100000
echo 768000,1050,1075 > avs_adjust
usleep 100000
echo 806400,1075,1100 > avs_adjust
usleep 100000
echo 844800,1100,1125 > avs_adjust
usleep 100000
echo 883200,1125,1150 > avs_adjust
usleep 100000
echo 921600,1125,1150 > avs_adjust
usleep 100000
echo 960000,1150,1175 > avs_adjust
usleep 100000
echo 998400,1150,1175 > avs_adjust

I use consecutive governor, 128mHz-998mHz (ondemand reboots for me :D i guess it's due to that voltage increases too slow in my table).

Getting generally 160-240mAh battery drain when screen is at lowest brightness, around 360mAh when it's at maximum.
[Nexus One Android Development] paulk_:
I have no idea whether it works, but immediately after I wake my phone up the draw is 5mAh. Played around it bit (scrolling through screens, opening closing apps and it went up to 83mAh on default auto brightness (not too bright, in the office under florescent lights).

I'm using static voltages, generally using the max voltages you have, except for

128000 - 850

245000 - 850

256000 - 875

960000 - 1225 (any lower and my phone soft reboots after a while)

Using the CM CPU settings, max 998 (so kernel will only go up to 960000, still no idea why). No setcpu installed.

Seen the current go up to 400mAh when I go back to my homescreen from Whatsapp, and a lot higher when I go back to my homescreen from the camera app.
[Nexus One Android Development] k3vink3vin:
feels VERY smooth and responsive after flashing cm_passion_full-47.zip and 2.6.37_AVS-CM7_CFS_20110217_2143.zip!

edited:

phone wouldn't enter sleep state after flashing both of the above. been rebooting and wiping dalvik cache, didn't help. anyone else suffering from this?