yashsingh1/xdaforums huggingface dataset:
[HTC Aria Android Development] cHarley04:
I guess I'll just sit tight for a while on n74 and drowning's 7-5 kernel. My battery life has never been better.

:)
[HTC Aria Android Development] joachim123:
what theme is that? i noticed the black on white. looked pretty clean thats all. :P
[HTC Aria Android Development] retired_mnbooze:
From n75's changlog, I would assume n74+drowingkernel 7-5 and n75+drowingkernel 7-5 would be the same. My performance would suggest this too.

Sent from my CM7 Aria.
[HTC Aria Android Development] cHarley04:
Unless it has something to do with the WiFi changes???

n75 Changelog: "Update prebuilt kernel & wifi module (usb tether fix) "
[HTC Aria Android Development] uacvax:
Can you guys post numbers for your screen on time? That by far is the largest battery drainer so would be important to know for correlations I would think. Thanks.
[HTC Aria Android Development] CallMeAria:
Nightly 76 seems to be great. Haven't messed with any kernels on this build yet, the built in kernel seems pretty solid. No wifi issues, battery is good. USB tethering is also working fine again. Running 245/768 interactive and its very responsive.

Sent from my cm7 Aria.
[HTC Aria Android Development] kabell4:
Is it me or is the GPS and compass off by 90 degrees?
[HTC Aria Android Development] CallMeAria:
I can't vouch for GPS right now but both maps and my compass are orientated correctly. Maybe you need to calibrate your compass?

Sent from my cm7 Aria.
[HTC Aria Android Development] DanGeorges:
I have this problem as well -

I'm tempted to unroot to original and see if this is a hardware (magnetometer) issue or software misinterpreting the readings...
[HTC Aria Android Development] kabell4:
I guess it was nothing a reboot and calibration couldn't fix. : )
[HTC Aria Android Development] kabell4:
Why "interactive" and not "on demand" or one of the other ones? I tried to search for how each controlled the phone, but couldn't find anything.
[HTC Aria Android Development] DanGeorges:
cpu governers

Good question.

I found this on various android forums:

Interactive governor favors higher frequencies more often.

Ondemand is the most common AFAIK. It scales up according to the CPU load. Performance is more aggressive, and more likely to be in the upper end of your max/min.

From the SetCPU author:

- The ondemand governor is the default option used by Android. It scales the CPU speed between the minimum and maximum speeds depending on CPU load. If the system needs more speed, the kernel will rapidly scale up the CPU speed.

- The conservative sets the CPU speed in a similar way to the ondemand governor, but scales the CPU up much less rapidly. This would theoretically save battery power, but may lead to less responsiveness.

- The userspace governor is currently useless. It's another way for applications to set the CPU speed that SetCPU does not use.

- The powersave governor always keeps the CPU at the minimum set frequency.

- The performance governor always keeps the CPU at the maximum set frequency.

Except for "userspace," no matter which governor you set, the CPU will always stay within the bounds of the maximum and minimum speeds you set in SetCPU.

Smartass automatically limits the screen on frequency to >= 518Mhz to ensure responsiveness, and screen off frequency to <= 352Mhz to keep standby battery life under control. Much like HTC's perfllock, it does this at the kernel level so it is much better than app level screen off profiles.

I hope this is all correct. I found it on the internet, so it must be correct!
[HTC Aria Android Development] cHarley04:
Interactive does do a bit better job than On Demand when it comes to eliminating "lag" during Screen On activities. However, it does come at a bit of a price in terms of the CPU spending more time at higher clock speeds, and as a result, not quite the battery performance as On Demand can provide, depending on how you are using the phone.

I'm currently in the middle of benchmarking the different governors with different clock settings, and comparing them to battery consumption. In the mean time, I strongly suggest that people that a look at This Thread and give it a try. It has made more of a difference in terms of eliminating "lag", than any governor tweaks I've played with.

;)
[HTC Aria Android Development] Darius_bd:
Wow, you're saving me quite some work, thanks ! ;D
[HTC Aria Android Development] uacvax:
Charley,

Could you also keep tabs on screen on times in your benchmarks? Whether or not you are able to maintain a consistent and good HSDPA or EDGE connection seems to have a huge impact on battery life too. Thanks!

P.S. Does anyone know what the different colors on that phone signal graph indicates? Like green, beige? Thanks.
[HTC Aria Android Development] cHarley04:
Sorry, but given the number of different governors & speed range combinations, and the time required to test each for a duration long enough to determine battery consumption, I just don't have that kind of spare time, and with Data On, the variable amounts of background data has too much potential to distort my battery usage numbers.

The benchmarks I'm running all involve gauging CPU usage and battery consumption during, Screen Off, No Data, streaming music via Bluetooth to a headset, coupled with the phone having enough in reserve to respond to an incoming phone call without noticeable lag.

I can tell you already though, that the Smartass governor fails horribly in this application. :o
[HTC Aria Android Development] uacvax:
I figured. Thanks though. Eager to see your results.
[HTC Aria Android Development] kabell4:
Awesome posts everyone. Glad I asked the questions.
[HTC Aria Android Development] retired_mnbooze:
drowningkernel 7-7 just got released at the end of its thread.

Sent from my CM7 Aria.
[HTC Aria Android Development] cHarley04:
Thanks, but based on his comment;

"it is indeed the smartass (

at least for the latest kernel it would never scale back when sleeping

, my mistke one extra zero i had in the settings) "

that's not going to fix the inherent fact that during Screen Off mode, Smartass will eventually put the phone into "Deep Sleep" mode, despite the fact that a background task has the CPU running at 30-50% of max clock. The result in this case is usually hung and/or crashed tasks.

While the Smartass gov works very well in most Screen On situations, it's inability to adapt to what's happening in the background during the Screen Off mode, leaves me wanting to rename it the DUMBASS governor.

.
[HTC Aria Android Development] drowningchild:
so pretty much scrap smartass?

it was just experimentation on my part

i do not know enough to fix problems such as this, i just looked at commits and tried to cherry pifck them into our kernel

and the kernel i was referring to was 7-6 as i changed sleep max to 2457600 instead of 245760 so it would never sleep
[HTC Aria Android Development] lilhaiti:
I wouldn't say scrap Smartass...just suggest people that have a problem with deep sleeping to use another governor.

For me Smartass gives me the best performance for what I use the phone for.
[HTC Aria Android Development] tommyguns818:
Smartass works great with 7sio on rc4. Been monitoring off screen mode and runs along 3% usage or even lower. When screens off, streaming music works great with no kick ups. Thanks
[HTC Aria Android Development] Darius_bd:
But it's a inherent error with the Smartass governor itself or just kernel-specific?

So, in the end, Interactive would be the better governor?

And my ticks says the phone it's been 73% of the time in deep sleep but I still heard the email notifications from time to time. Yes, not always, sometimes it went into a really-deep sleep (so to say) so it's not like something totally reproducible...
[HTC Aria Android Development] dandrumheller:
I for one would prefer you keep the smartass governor in your kernels. When not running cpu intensive tasks with screen off, it seems to provide the best balance of performance and battery life.

Like cHarley, I run into problems with it when running media in the background - typically for me this involves streaming pandora in my car - it will start to stutter the music, or kill pandora all together. My simple solution is to switch to ondemand when doing this. I haven't had time to investigate, but I think tasker may be able to automate this swap, or at least allow me to create a widget to toggle between the two governors. Anyone tried this??

At any rate, I have been running CM7.0.3 with your 7-5 kernel for quite a few days now. Up until today I had been seeing about 6-7% battery drain per hour with a mix of wifi/3g with background data on all the time. Today, however, I've had the phone on for 9.5 hours, and am still at 67% battery, so this is giving me roughly a 3.5% burn per hour. The only other time i have gotten this good a battery life is on the first few CM7 nightlies. I don't know if this is just a random case, or the battery stats are settling in, or what. I will continue to monitor, but loving it right now.

So count me as one vote for keeping smartass! what does it hurt to have it in there - doesn't stop anyone from using ondemand or interactive or whatever...

DD
[HTC Aria Android Development] :
I agree keep smartass in the kernel, I have been using n66 with drowning 7.5 for almost a week now and have had the best battery life since owning the phone. I have an active sync account set to push and the Gmail app and I can't recall ever missing an email alert in fact most of the time when sitting at my desk the email hits my phone before my PC. I say if you don't like it don't use it to each his own.
[HTC Aria Android Development] drowningchild:
i dont have any issues with smartass either except my latest(been experimenting with smartass with the last 2 revisons)

i'll revert to how it was :)
[HTC Aria Android Development] cHarley04:
Let's no give up too quick, in all fairness, I haven't tried 7-6 yet. Smartass shines during Screen On use. It also shines in conserving battery during Screen Off times (in most cases).

It's downfall, is it's inability to recognize and adapt to CPU load when in the Screen Off mode. It just seems to assume that if the screen is off, nothing is going on, so it's OK to go to sleep.

My situation may be different than most people in that I spend 2 or 3 days a week using the phone (screen off) all day long, streaming music to a BT headset and the phone in "standby" awaiting a (potential) incoming phone call, nothing more.

I'm busy riding a motorcycle during these times, and if it's not for the fact that the Aria's screen is next to impossible to read in direct sunlight, I'm too busy avoiding the idiots that are texting while driving, too have any use for data services. ;)

So, here's my current (workaround) solution to Smartass' limitations.

1 - I'm running Smartass 245-806 as default.

2 - I'm using Tasker.apk to monitor my Bluetooth status, and when active, overriding the governor to - On Demand 245-768.

(BT is always on when I'm using the phone Screen Off and easy to monitor.)

This is working out OK for me now, but it leaves me wondering, for example, how many people use their Aria unplugged (screen off) as an alarm clock, and how many of them have been late for work because the Smartass Deep Sleep mode stopped the alarm clock from activating? That's just one of the potential problems I foresee when the phone enters Deep Sleep and is unable to respond to upcoming CPU demand.
[HTC Aria Android Development] CallMeAria:
You brought up some interesting points that I hadn't thought about before. Two things I would like to point out is that I was using smartass for quite some time and during that time I would plug my phone into the auxiliary Jack of my car stereo and listen to music. It worked great with the exception that once in a while there would be a delay when trying to skip a track using the volume buttons after the phones been off for a while. Not as intensive as streaming through Bluetooth though. I never had a problem with my alarm going off though. I'd imagine since the phone isn't actually doing anything while I'm sleeping there is nothing to keep the underclocked CPU from waking for the alarm.

I think a fix for the music Bluetooth issue, and all screen off issues, would be to raise the minimum frequency that smartass uses while screenoff. I think raising it to 245 as opposed to 120 with screen off would fix the issue. And I suppose the easiest way to do that would be to remove all the frequencies below 245 from the kernel altogether. A 245/320 screen off and 400 min screen on would still be very nice.

Sent from my cm7 Aria.
[HTC Aria Android Development] cHarley04:
It's certainly worth a try.

Just so you have some food for thought though;

Here's what I'm seeing for CPU usage during Screen Off while streaming via BT.

.
[HTC Aria Android Development] dandrumheller:
A little away from the current topic of conversation here, but are any of you guys still having issues with lack of notifications from the gmail app? I think I recall seeing a post or 2 on it a while ago, but haven't seen anything in a while?

Edit: Wow, apparently working night shifts is mangling my brain. After a quick google search (1st hit, 2nd post) indicated a clear data / toggle mail sync in the settings menu might fix the problem, I went and checked my account settings - sure enough, mail sync was turned off. checked the box, and like magic I now have push mail again. I know I didn't turn it off, so it must have been set off by default in one of the builds I flashed or something. Anyway, hopefully this might help some other poor soul who runs into the same thing....
[HTC Aria Android Development] cHarley04:
As follow up, I show the following as the 5 lower end speed steps, according to the CPU Spy app:

245 - 200 - 122 - 120 - Deep Sleep

Maybe the answer isn't raising the min to 245, but not allowing it to enter Deep Sleep?

And, based on my chart above, a 320 max during Screen Off, probably won't cut it in this case.

EDIT: a quick test at 245min - 320max while streaming via BT

CPU at 245 - 1% of time & 320 - 99% of time. Phone controls extremely sluggish to unresponsive.
[HTC Aria Android Development] CallMeAria:
2 questions:

1. Do the other governors allow the phone to go into deep sleep with bt running? Or is it just smartass. If the other governors allow deep sleep then I don't think that would be the problem.

2. When you say you set it 245/320 and the controls are sluggish is that with screen on or off?

Yet another observation: maybe it'd just the fact that the smartass wont let the phone go over 320 screen off that's causing the problem. Maybe its not the minimum?

Try this with tasked or set CPU:

Scenario 1:

Interactive governor.

245/400 screen off.

400/600+ screen on.

(Maybe try 120/400 screen off too).

See if that fixes your issues and it would atleast give us some more insight.

EDIT: what music player are you using?

Sent from my cm7 Aria.
[HTC Aria Android Development] CallMeAria:
I don't use the actual Gmail app, but no issues with my Gmail pushing to the android email app.

Sent from my cm7 Aria.
[HTC Aria Android Development] dandrumheller:
I have never used the android email app - just Gmail (my one other account gets polled by gmail so I don't have to have an email app polling from the device). Will the android mail app accept gmail pushes with polling turned off?

Edit: answer appears to be no.

Edit 2: issue resolved, see post one page back for details
[HTC Aria Android Development] drowningchild:
http://www.mediafire.com/file/hopnqdix2q85i26/cpufreq_smartass.c

thats the actual kernel part for smartass just open it up in a text editor have a look at it :)
[HTC Aria Android Development] Moh_Jay:
Ooooor you guys can get setcpu and have a screen off profile :D

Signatures are fancy.
[HTC Aria Android Development] Darius_bd:
.

Smartass bypasses screen off profiles, afaik.
[HTC Aria Android Development] Moh_Jay:
Oo oh well screen off works fine for me

Signatures are fancy.
[HTC Aria Android Development] cHarley04:
This only occurs with Smartass. The other governors seem to obey the Min/Max clock settings, while Smartass ignores them when the screen is off.

Both Screen On & Off

That seems doubtful from what I've seen, but to test that would require a custom Smartass kernel with a Screen Off max of at least 400. Smartss does work for several (~5) minutes before crashing, during my testing. Repeatedly testing and closely watching CPUSpy at 30 second intervals, leads me to believe that Smartass allows several minutes to pass after Screen Off, before dropping into Deep Sleep, or at least slowing to a clock rate that's too slow to cope with the CPU load. Streaming music works during the initial few minutes (sluggishly) before either Deep Sleep kicks in or the clock slows to a rate too slow to keep up with the task demand.

I have already tested this using Tasker to set Interactive at both 245-320 and then 245-400 when streaming via BT. The phone does not enter Deep Sleep, and the 245-400 setting is not near as sluggish when pressing phone controls. Using data gathered (see my chart in above post), setting the CPU min to anything less than a 245 min would seem pointless, as demand on the CPU will keep it from running any slower, with the exception of Smartass screen off mode which seems to have it's own problem if there are any background, CPU intensive, tasks running.

Both the stock Music app and my favorite, MortPlayer.

I'm not saying that Smartass won't work well for many people, but it appears to me, that anyone running CPU intensive, screen off, background tasks, are sooner or later going to experience problems.

I guess I'm just not convinced, that "Screen Off" is the best State to use as a status flag for determining when you can safely chop the CPU clock rate.

What I would like to be able to test, is a Smartass kernel with 120-400 Screen Off and no Deep Sleep step.
[HTC Aria Android Development] cHarley04:
Thanks.

First, I'm not much of a programmer and I haven't had but about 20 minutes to study the file, but here's what I see.

Using Notepad++

The obvious:

line 98 - #define DEFAULT_SLEEP_MAX_FREQ 320000

change to raise the max sleep freq. to say 400000

The interesting:

comments in lines 663-665 (below), seem to explain why smartass works for a brief period in Screen Off, but after that time expires, Smartass doesn't give a Ratsass how busy (loaded) the CPU is, it's going to start stepping down the clock.

Note comment, "even at full load the timer will lower the freqeuncy"

Maybe I'm just not bright enough to figure out how slowing down a CPU that's running at say =>50% load, is going to result in anything other than trouble. :confused:

IMO, ignoring CPU load during Screen Off, is just flat wrong and a crash waiting to happen.
[HTC Aria Android Development] bkmo:
I know this might be slightly off topic but has battery drain been fixed since nightly 75? :)
[HTC Aria Android Development] hungmung:
Actually your one of the first people on topic I've seen in here in a while.

Sent from my Liberty
[HTC Aria Android Development] gdeadfan:
Just installed CM7 build 6, and it is working surprisingly great. I really don't have any complaints about the build quality, wifi and gps and everything work perfectly. I just have a couple questions though..

How can I get my picture to show up for my outgoing text messages? I have a contact for myself with a picture attached, but the messaging app will not show it.

Is there any way to get a different gallery? This 3d gallery crap is so slow and low res, it drives me insane. I loved the HTC Sense one because it was quick and simple.

Is there any way to show message previews on the lock screen like HTC Sense did?

Is there a way to decrease the amount of home screens? I have dug and dug through these menus and I can't seem to find the option, I think it may have been left out.

I think those are all the questions I have for now! Thanks for all your help devs!
[HTC Aria Android Development] tedkunich:
This was a clean install with no backup restores - installed, booted, installed maps and ran the test.

Unfortunately I do not have that logcat anymore as I restored my 6.1.1 install. I'll repeat it again tonight (again with a clean CM7 install) and post the entire logcat as requested.

To answer your other questions, the phone was in a bay window (inside) with a view of the southern sky - CM6.1.1 will lock onto 3 sats from that location. For this test I had just opened the Maps application and clicked on "zoom to my location" carrat, which normally zeros into my exact location. WiFi was off since it somehow can use my wifi/lan location to zero onto my house without gps enabled at all - having wifi off, it would put my location a few blocks away without a gps lock.

I have tried using the GPS status app based on an older post of your, and was never able to get a gps lock with CM7, even after an hour (phone set not to sleep). I repeat this again and capture a logcat of that as well.

Thanks,

T

Ted
[HTC Aria Android Development] lunerceli:
I know this may seem weird, but I couldn't get GPS to lock on at all. I even did everything over and over again with no luck. So I did what any debugger would do and started playing around withstand apps. I finally got GPS working by going into maps and then I searched for directions, still no GPS, and then when it came up with the directions I switched over to navigation. Now that I have done that, my GPS locks on within 3 seconds and is accurate within 50 meters. Everything works like it should now. Maybe everyone that is having GPS problems could try this. If u do and it works then there is the temp solution until RC1 is pushed out the door.
[HTC Aria Android Development] attn1:
E/vending ( 1376): [15] 1.run(): Error while trying to retrieve provisioning: java.net.SocketException:

this tells me you are having connectivity issues of some sort - which can be why agps data is not retreived and why gps fails.

make sure the rom has settled after install before initializing GPS. with pacman going after a clean install, data sync going on and so on, contention for data connections gets a bit tedious. Also make sure you have a good network connection (market is working).

I just flashed the 07 nightly, and GPS locks on 8 sats using GPS Status very quickly here.
[HTC Aria Android Development] jznomoney:
people with issues try using the gps test by mike lockwood on the market and post what happens.
[HTC Aria Android Development] attn1:
Doesn't look complete - i dont see anything before you started gps.
[HTC Aria Android Development] attn1:
This worked for me at one time early on. I haven't had any need to try it again - even after factory resets and reflashes. It sure can't hurt anything.
[HTC Aria Android Development] Darius_bd:
This one should be complete http://pastebin.com/XPLjs09z
[HTC Aria Android Development] jdwhite87:
http://pastebin.com/97NckV00

How is this
[HTC Aria Android Development] pigman46:
I always set my home to three screens by pressing Menu->Edit on the home screen. Then you can scroll to the screen you want to remove and press the red (X) to remove it. The yellow pin at the top is to define which screen is the default home screen.