[10-11-11][ROM] gingerbread-evo-deck [1.3][2.3.7 Stable] #Stablistic

[BrooMann]

In Spare Parts...Battery history...Sensor usage...

GPS Status: 7h 52m 19s
Maps: 2h 45m 40s
Android system: 2h 3m 31s

These seem crazy high...don't they? Or is it just me?

Sent from my Gingerbreaded HTC EVO 4G runnin Deck's 1.1 rom.

[amw1972]

Deck,

How about adding in the option to set long press on the back button to kill app?

just a thought...

[motzvi]

Originally Posted by amw1972

Deck,

How about adding in the option to set long press on the back button to kill app?

just a thought...

go to , settings - applications - development

Sent from my PC36100 using Tapatalk

[SouthernEvo]

Originally Posted by BrooMann

In Spare Parts...Battery history...Sensor usage...

GPS Status: 7h 52m 19s
Maps: 2h 45m 40s
Android system: 2h 3m 31s

These seem crazy high...don't they? Or is it just me?

Sent from my Gingerbreaded HTC EVO 4G runnin Deck's 1.1 rom.

And Let me guess you have an unusually high "Android System" usage showing on your screen . Wait till you make a phone call it will spike even higher the longer the call . Im suspecting there is something not right with the sensors . It seems each newer variation of GB it progressively gets more so . I noticed it early on Salvage Mod's GB as well as R2Droid's OMGB build as well . The later of the two does not give you access to spare parts sensor usage screens . Like previously stated in an earlier post I can make a 45 min phone call and my android system is sitting at 89+% . I was told this is normal , oddly enough I have seen other phones running aosp (Nexus S) that after making a phone call Android system usage does not spike that high . Unfortunatley I checked logcat and was not able to find any errors in the system . But I firmly believe the issue is in the sensors or the drivers for the sensors or how the os manages the sensors .

[getwet]

just installed this and it looks great one question how do i sync with outlook on a pc?

[itouch24]

is the GPS working better on the new versions ... i know with some past versions GPS was spotty for a few ... there was a fix that worked for some but others stated that still wasnt that accurate ... is this still present ...?

[hachiroku]

in regards to many you stating that GPS is using a lot of battery life the same occurs for me. what i have been doing though is killing all apps before i turn off my screen or as i power up my phone. this kills the GPS sensor within a few minute and helps a lot with battery life.

gps like stated above has been better than ever. my gps lock is almost instantaneous and runs great. the gps fix as noted for CM7 works great. as posted by cyanomod, the HTC EVO has an issue with its GPS coding, so we will always tend to be plagued with having to do the GPS fix until custom code can be developed.

i'm on v1.1 with tiamet 3.3.7 sbc
set cpu settings at idle to 128mhz
and using custom proximity/screen brightness settings as i have posted earlier.

i have zero complaints with battery life with this rom. it is the best thing to happen to this phone since its introduction. the standard kernel that is included with the rom does not share the same battery longevity as when using tiamet 3.3.7.

[SouthernEvo]

Originally Posted by hachiroku

in regards to many you stating that GPS is using a lot of battery life the same occurs for me. what i have been doing though is killing all apps before i turn off my screen or as i power up my phone. this kills the GPS sensor within a few minute and helps a lot with battery life.

gps like stated above has been better than ever. my gps lock is almost instantaneous and runs great. the gps fix as noted for CM7 works great. as posted by cyanomod, the HTC EVO has an issue with its GPS coding, so we will always tend to be plagued with having to do the GPS fix until custom code can be developed.

i'm on v1.1 with tiamet 3.3.7 sbc
set cpu settings at idle to 128mhz
and using custom proximity/screen brightness settings as i have posted earlier.

i have zero complaints with battery life with this rom. it is the best thing to happen to this phone since its introduction. the standard kernel that is included with the rom does not share the same battery longevity as when using tiamet 3.3.7.

Im not expierencing any battery life issues . Just unusually large spikes in Android system usage especially after making a phone call . Logic would dictate "Voice calls" should skyrocket not android system when you place or receive a call . But to further backup my arguement was the fact in spare parts sensor usage was the same duration as the phone call . I can only figure that would involve the proximity sensor . I checked your previous posts and was undable to find the custom proximity/screen brightness settings . Unless I over looked it I will look again .

[hachiroku]

Originally Posted by SouthernEvo

Im not expierencing any battery life issues . Just unusually large spikes in Android system usage especially after making a phone call . Logic would dictate "Voice calls" should skyrocket not android system when you place or receive a call . But to further backup my arguement was the fact in spare parts sensor usage was the same duration as the phone call . I can only figure that would involve the proximity sensor . I checked your previous posts and was undable to find the custom proximity/screen brightness settings . Unless I over looked it I will look again .

http://forum.ppcgeeks.com/cdma-htc-e...st2089251.html

i've been contemplating setting the adjustment seconds to be a larger timeframe, but am pretty happy with the settings as of now. there is mild flickering when screen dims or brightens from full low to full high and vise versa. if this bugs you this set the adjustment window's to a larger length.

Sample Interval: 5s
Decrease Hysteresis: 20%


the way our EVO's are designed, the proximity brightness sensor is a bit sunk into the phone's screen. if i were to design this i would have not have the sensor sunk and add a tint to the screen as a filter. that way the light that the sensor actually picks up will be more accurate as the sensor is overly sensitive.

if you have issues of the screen becoming dim when it should not, simply tilt your phone face more towards the sky. the sensor will pickup the lighting and readjust within a few seconds. this mainly occurs when you're indoor with florescent lighting.

[hachiroku]

i dunno if anybody else is having this issue, but the camera focus with v1.1 has gotten worse.

i've downloaded every camera app on the market, and neither provides a better picture than the stock camera app. so i am beginning to think possibly it isnt the app but some core coding? the camera now doesn't even focus appropriately. it completes the action, but seems like it doesn't know what its doing as all pictures are blurry.