Jump to content

CM7 Nightlies Topic [Nightly 28- 21/03/2011]


Guest Victor von Zeppelin

Recommended Posts

Hmm, I've seem to have a weird problem with the sensors of the phone. If I call someone and the phone blanks out and comes back, the sensor seems to keep itself activated even after the call (while on or sleeping doesn't matter) this happens with games/apps that use the sensor too (Gallery 3D for an example).

If I use the Gallery for a moment and tilt the phone a bit then close the application and sleep the phone, the sensor usage from Gallery in spare parts gets bigger and bigger when I check it from time to time. If I charge the phone to 100% and unplug + sleep it and leave it for 10 minutes then checking the battery usage, the app that used the sensor or android system will be on top of battery usage. Even more weird is that killing the app is not helping either and it's just a reboot of the phone that solves the sensor usage.

Is there anyone else who has this problem or is my phone retarded?

Link to comment
Share on other sites

Guest Hurders
To answer one part of that, ROM manager does some Google Analytics stuff. It has been guessed that it doesn't stop trying to phone home when wireless is off. So, the courses of action are to either remove it, or to disable analytics in the settings. Seems fairly founded in good ideas.

Well I can definitely report that removing the ROM manager apk from the zip had absolutely no effect reducing battery drain for me on a fresh RC2 install. Rom manager is definitely not on my phone so I know its definitely not been installed with the RC2 rom. As I previously reported. Phone still dropped 17% battery overnight on standby over 7 hours from 100% to 83%. So in my experience ROM manager is definitely not the problem, or at least its not a significant contributor to the battery drain.

Link to comment
Share on other sites

Guest reluctant_traveller
leaving the phone pointing East overnight resulted in zero battery drain with GPS, Wifi & 2-minute checks on 10 POP email accounts all on

My gods.. yes.. YES.. this is it! the compass is constantly trying to point north, so it tries to swing counter-clockwise, inducing a reverse electro-magnetic current that counteracts the current drain from the battery! GENIUS!

Link to comment
Share on other sites

Guest Zythus

Uninstalled ROM Manager by Titanium Backup, on RC with boot.img from 2nd post

Waiting to 100% charge and let's see!

Btw guys, on nightly 14 today, from 9:10 am to 9:30 I was tryin to connect to wi-fi in my school, and it was dropping and connectin, cause there was bad signal.

In 20 minutes battery dropped from 79% to 65%! :(

And after some playing, on 2 pm it was on 35% :(

So it was dropping like crazy... hope this rom will make it better

Link to comment
Share on other sites

Guest walkies2000

tried replacing the sensors default and goldfish, made no difference to my RC 2 install at all, not to say it doesnt work but no different here, back to nightly 8 for me

Link to comment
Share on other sites

Guest targetbsp

I disabled google analytics on day 1. And also (thanks to autostarts) don't have rom manager even running until its needed. And my battery life sucks. :( So it's not that.

Link to comment
Share on other sites

Guest Grain
Hmm, I've seem to have a weird problem with the sensors of the phone. If I call someone and the phone blanks out and comes back, the sensor seems to keep itself activated even after the call (while on or sleeping doesn't matter) this happens with games/apps that use the sensor too (Gallery 3D for an example).

Check /proc/wakelocks via adb or some app. If you see a "taos" wakelock that is active, this might be related to this hack that basically should keep the phone from sleeping as long as any application uses the proximity sensor.

Edited by Grain
Link to comment
Share on other sites

Guest DonJamal
tried replacing the sensors default and goldfish, made no difference to my RC 2 install at all, not to say it doesnt work but no different here, back to nightly 8 for me

i use it n15

Link to comment
Share on other sites

Guest DonJamal
Check /proc/wakelogs via adb or some app. If you see a "taos" wakelock that is active, this might be related to this hack that basically should keep the phone from sleeping as long as any application uses the proximity sensor.

with notepad2

name count expire_count wake_count active_since total_time sleep_time max_time last_change

"mmc_delayed_work" 1380 3 0 0 3033243331 719453326 813993341 2757490110530

"KeyEvents" 20312 0 0 0 4381581738 209073332 101888336 2757452188862

"event0-175" 19934 0 0 0 2967396580 0 10308334 2757452122195

"PowerManagerService" 940 0 0 0 341025177038 25567338360 71147996655 2756855467198

"qcril" 687 0 0 0 898081674 41688332 33071667 2756846025531

"rpc_reply" 411 0 0 0 391501675 35690003 23848334 2756845598865

"rpc_read" 724 0 0 0 920756664 841210004 628675004 2756845217198

"rpcrouter_smd_xprt" 6865 0 21 0 1418723341 118111685 74973340 2756845178865

"rpc_server" 1451 0 0 0 835528340 392170009 90670002 2755844952201

"rpc_reply" 1451 0 0 0 806215035 391155017 90650001 2755844947201

"rpc_read" 1451 0 0 0 119529984 5943332 7388333 2755844860535

"event1-175" 342 0 0 0 169471677 434999 4581668 2745867853860

"gpio_kp" 172 0 0 0 34099990399 15936666 942214999 2745867603860

"rpc_read" 365 0 0 0 34938335 608333 4463334 2743552750542

"alarm" 76 0 0 0 1549231702 907491685 649940005 2733792995537

"power-supply" 37 0 0 0 33526669 1396666 20805000 2716622465511

"event4-175" 35 0 0 0 6751748433 6606596763 640476673 2675295213867

"rpc_read" 131 0 0 0 5373335 3588331 1460000 2675279630534

"rpc_read" 94 0 0 0 43308340 1270004 41768333 2674811022200

"alarm_rtc" 9 3 0 0 4172538402 4146388404 1002136683 2674286257196

"GPS" 2 0 0 0 1894528333 4991667 1889535000 2673489170519

"rpc-interface" 4 0 0 0 56845001 1106666 55570001 2673484942186

"rpc_reply" 2 0 0 0 56525002 1045000 55480002 2673484902186

"rpc_read" 4 0 0 0 525250005 515113339 515113339 2673483860520

"msm_camera" 2 0 0 0 29986901654 0 21531174993 2400801567164

"msm_camera_wake" 2 0 0 0 29986903321 0 21531174993 2400801565498

"adsp" 11 0 0 0 57312831716 1101751668 17230363324 2400781243831

"mt9t11x" 2 0 0 0 28898889988 0 20901618329 2400767813831

"rpc_reply" 30 0 0 0 271053338 20065000 30381668 2396637973840

"audio_pcm_idle" 10 0 0 0 40296566752 0 6705003330 2396637923840

"audio_pcm" 10 0 0 0 40296585084 1424438334 6705008330 2396637922173

"rpc_read" 48 0 0 0 73903331 7798332 22051667 2396635920507

"rpc_reply" 16 0 0 0 145298335 14398334 37758334 2393549473840

"rpc_read" 16 0 0 0 851666 465000 465000 2393542132174

"ApmCommandThread" 44 0 0 0 4217475001 0 2000308333 2392460083839

"rpc_read" 39 0 0 0 2665001 0 971667 2392458840505

"rpc_read" 1 0 0 0 16667 0 16667 343389071764

"rpc_reply" 0 0 0 0 0 0 0 0

"rpc_reply" 267 0 0 0 147343330 0 5286667 239482786755

"rpc_read" 529 0 0 0 70830002 0 7123333 239482550088

"rpc_reply" 19 0 0 0 10335000 0 3246668 232231565092

"rpc_read" 38 0 0 0 3846666 0 486666 232231228425

"rpc_read" 33 0 0 0 3758329 0 1118333 126393050061

"rpc_reply" 6 0 0 0 3081668 0 1480000 126377141727

"rpc_reply" 9 0 0 0 6548334 0 3435000 120566380063

"rpc_read" 17 0 0 0 1175000 0 166666 120566046730

"rpc_reply" 5 0 0 0 6611666 0 4628334 116689893411

"rpc_read" 10 0 0 0 729998 0 120000 116689476744

"rpc_read" 6 0 0 0 490001 0 120000 46743903390

"rpc_reply" 0 0 0 0 0 0 0 0

"rpc_read" 0 0 0 0 0 0 0 0

"rpc_reply" 0 0 0 0 0 0 0 0

"rpc_reply" 0 0 0 0 0 0 0 0

"rpc_reply" 0 0 0 0 0 0 0 0

"usb_mass_storage" 0 0 0 0 0 0 0 0

"rpc_reply" 0 0 0 0 0 0 0 0

"rpc_read" 0 0 0 0 0 0 0 0

"rpc_read" 4 0 0 0 65001 0 25000 5181391724

"rpc_reply" 2 0 0 0 28423332 0 19171666 5180050057

"rpc_reply" 0 0 0 0 0 0 0 0

"rpc_read" 0 0 0 0 0 0 0 0

"rpc_reply" 0 0 0 0 0 0 0 0

"power-supply" 1 0 0 0 1495000 0 1495000 3951971715

"power-supply" 1 0 0 0 1536667 0 1536667 3951915048

"rpc_reply" 0 0 0 0 0 0 0 0

"rpc_read" 0 0 0 0 0 0 0 0

"rpc_reply" 0 0 0 0 0 0 0 0

"usb_mass_storage" 0 0 0 0 0 0 0 0

"rpc_read" 3 0 0 0 40000 0 13334 3040516700

"rpc_read" 3 0 0 0 61667 0 23334 3030831700

"usb_bus_active" 0 0 0 0 0 0 0 0

"rpc_reply" 0 0 0 0 0 0 0 0

"rpc_reply" 0 0 0 0 0 0 0 0

"DATA7" 0 0 0 0 0 0 0 0

"DATA6" 0 0 0 0 0 0 0 0

"DATA5" 0 0 0 0 0 0 0 0

"msm_serial_hs_dma" 0 0 0 0 0 0 0 0

"msm_serial_hs_rx" 0 0 0 0 0 0 0 0

"rpc_reply" 0 0 0 0 0 0 0 0

"rpc_read" 0 0 0 0 0 0 0 0

"rpc_reply" 0 0 0 0 0 0 0 0

"rpc_read" 0 0 0 0 0 0 0 0

"rpc_reply" 0 0 0 0 0 0 0 0

"rpc_read" 0 0 0 0 0 0 0 0

"rpc_reply" 0 0 0 0 0 0 0 0

"rpc_read" 0 0 0 0 0 0 0 0

"rpc_reply" 0 0 0 0 0 0 0 0

"rpc_read" 0 0 0 0 0 0 0 0

"rpc_reply" 0 0 0 0 0 0 0 0

"rpc_read" 0 0 0 0 0 0 0 0

"rpc_reply" 0 0 0 0 0 0 0 0

"rpc_read" 0 0 0 0 0 0 0 0

"qmi2" 0 0 0 0 0 0 0 0

"qmi1" 0 0 0 0 0 0 0 0

"qmi0" 0 0 0 0 0 0 0 0

"unknown_wakeups" 0 0 0 0 0 0 0 0

"deleted_wake_locks" 80 0 0 0 19974958594 8287430132 2513678352 0

"radio-interface" 87 0 0 751866666 93669525148 2169293352 3174198324 2756813937198

"main" 16 0 0 82258114997 2708856175231 0 536617893365 2675307698867

dont find taos

Link to comment
Share on other sites

Guest pellonet
My gods.. yes.. YES.. this is it! the compass is constantly trying to point north, so it tries to swing counter-clockwise, inducing a reverse electro-magnetic current that counteracts the current drain from the battery! GENIUS!

What, no 'tongue-in-cheek' smiley', that leaves you sounding as if you are trying sarcasm?

:( :(

Edited by pellonet
Link to comment
Share on other sites

Guest pellonet
To answer one part of that, ROM manager does some Google Analytics stuff. It has been guessed that it doesn't stop trying to phone home when wireless is off. So, the courses of action are to either remove it, or to disable analytics in the settings. Seems fairly founded in good ideas.

Yep, that makes sense, but total removal seems drastic when, as you say, you can just disable the Google Analytics in settings.

Link to comment
Share on other sites

Guest Kokainkatt
where to find ansewer call animation? :(

My bad. It was the "lockscreen" option in CM settings. When i changed that from "rotary" and used the first option in the list, it also changed the way you answer a call, from the rotary thingy to the stock froyo slide thingy.

I know this sounds all F*up, but my settings are in a different language and Im far to tired to even try to translate things properly.

But I think you get the picture. Try changing the lockscreen setting and se if the proximity issu lasts. Mine did not.

Link to comment
Share on other sites

Guest DonJamal
My bad. It was the "lockscreen" option in CM settings. When i changed that from "rotary" and used the first option in the list, it also changed the way you answer a call, from the rotary thingy to the stock froyo slide thingy.

I know this sounds all F*up, but my settings are in a different language and Im far to tired to even try to translate things properly.

But I think you get the picture. Try changing the lockscreen setting and se if the proximity issu lasts. Mine did not.

i changed it to the first sliding tab.. im hungarian but doesnt work for me

Edited by DonJamal
Link to comment
Share on other sites

Guest jayhix

was looking at my battery usage, have a look at the drain when i turn off wifi in a 3g area... i dont get this sort of drain with 2g.

post-791616-1299692551_thumb.jpg

Edited by jayhix
Link to comment
Share on other sites

Guest JimJam707
I saw that too. Perhaps it did it. Who knows :(

But that's only new enough to be in the RC....soooo

ANYONE NOT ALREADY USING RC2, GET YOUR ASSES ON IT RIGHT AWAY

Thank you.

Calm down, just flashing it nao :(

Link to comment
Share on other sites

Guest Maz2011

My lockscreen setting has always been on "slide" as I dont like the rotary one. For me it has no effect at all on the proximity sensor problem.

Battery life also continues to be very poor (astoundingly poor actually: you can almost watch the % drop).

The touchscreen no longer freezes. :(

No other obvious problems.

Link to comment
Share on other sites

Guest Xaphod
https://github.com/CyanogenMod/android_fram...86b50b4f8f1dffa

found this commit interesting, any idea what it was trying to do

If you look at the rest of the routine, you'll see that the variable 'x' is not used anywhere, so there's no point in subtracting 'dw' from it. Like the committer says, it's dead code. His comment about "consuming battery life" is facetious as even if the compiler left that code in, the effect would be entirely negligible.

Link to comment
Share on other sites

Guest chall32

Re taos, it's logged to kmsg:

<2>[03-09 17:44:09.358391] [4: events/0]TAOS: prox_interrupt =18431, distance=1

<2>[03-09 17:44:10.438391] [4: events/0]TAOS: prox_interrupt =2374, distance=5

<2>[03-09 17:44:11.918391] [4: events/0]TAOS: prox_interrupt =18431, distance=1

<2>[03-09 17:44:13.128395] [4: events/0]TAOS: prox_interrupt =2165, distance=5

<2>[03-09 17:44:14.478393] [4: events/0]TAOS: prox_interrupt =18431, distance=1

<2>[03-09 17:44:20.138393] [4: events/0]TAOS: prox_interrupt =2064, distance=5

Is what I see during a blackscreen call when covering and uncovering proximity sensor....

Link to comment
Share on other sites

Guest hc_1540

Sorry, bit of a noob and would really like to help out with all this. One question though, If I move to the latest updates will I lose my finely tweaked homescreens etc.? I've got them exactly as I want.

However, sometimes sacrifices need to be made...

Link to comment
Share on other sites

Guest Victor von Zeppelin
Calm down, just flashing it nao :(

Sorta what I hope for when the RC2 topic is up. I think we've just about got people out of N8, so lets bring it up to RC2

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.