search

Nell17 / openeve

Automatically exported from code.google.com/p/openeve
0 stars 0 forks source link

BATTERY DRAINS ENERGY FAST #117

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.Energy draining
2.My phone said that the "Android OS" needs the most energy

What is the expected output? What do you see instead?

Longer Battery life

What version of the product are you using?
1. the right 0317 thing
2.  system-gb-20110514a-snapshot.zip    
3.  boot-gb234-110509-rndis-236mb.zip   
4. update-gb-camera-110521.zip 

On what operating system?

Do you have logcat or dmesg ?
 (adb logcat -d > logcat.txt, adb shell dmesg > dmesg.txt)

What version of the *Official LG* Firmware were before using Custom
firmware ?
(V20G, V20D, V15x, V16x etc. )
V10E

Please provide any additional information below.

Original issue reported on code.google.com by Katzen...@gmail.com on 22 May 2011 at 5:33

GoogleCodeExporter commented 8 years ago 
Since update-gb-camera-110521.zip !

Original comment by Katzen...@gmail.com on 23 May 2011 at 6:30

GoogleCodeExporter commented 8 years ago 
I reinstalled System.img
then boot.img
then gapps.
without cam patch.
draining again -.-

Original comment by Katzen...@gmail.com on 24 May 2011 at 2:13

GoogleCodeExporter commented 8 years ago 
even the case is same with me. I tried re-installing from fresh and excluded 
the camera patch. The battery drains too fast. 

Also the in-call quality is very poor.

Original comment by yakaaith...@gmail.com on 24 May 2011 at 2:15

GoogleCodeExporter commented 8 years ago 
my call qualitiy is nice. or i don't know how it sounds if its high quality xD

Original comment by Katzen...@gmail.com on 24 May 2011 at 2:45

GoogleCodeExporter commented 8 years ago 
my phone has this issue, after i update the update camera, battery life run out 
faster

Original comment by gravitar...@gmail.com on 24 May 2011 at 3:36

GoogleCodeExporter commented 8 years ago 
and my phone needs longer to reload if its activated.
i think we need to manualy remove all the files this update gave our system. 
with adb remount and an adb command to remove this files. then reinstall of the 
system without patching the camera thing.
or erase the system and boot partition manualy with adb erase boot & adb erase 
system.

Original comment by Katzen...@gmail.com on 24 May 2011 at 8:07

GoogleCodeExporter commented 8 years ago 
Have you tried wiping battery stats in recovery?
In case you didn't know you have to fully charge your battery first...

Original comment by omarbeko...@gmail.com on 25 May 2011 at 7:03

GoogleCodeExporter commented 8 years ago 
i chraged it fully. and the stats get reseted after every reload automatically.
the phone need 3 times longer to reload. and drains the energy 2-3 times faster

Original comment by Katzen...@gmail.com on 25 May 2011 at 1:02

GoogleCodeExporter commented 8 years ago 
My phone don't have any issues like u describe it, try to get a task manager 
like osmonitor and check what process are eating your cpu. Check also your cpu 
speed setting it has to be on interactive with 691mhz max...

Original comment by cmgonza...@gmail.com on 25 May 2011 at 2:45

GoogleCodeExporter commented 8 years ago 
my cpuspeed setting is since this batttery drain set on POWERSAVE.

Original comment by Katzen...@gmail.com on 25 May 2011 at 5:03

GoogleCodeExporter commented 8 years ago 
This bug has high priority.
the batterylife is shorter.
the energy costs hight.
and the battery/phone life is shorter because of the many reloads.

Original comment by Katzen...@gmail.com on 27 May 2011 at 3:12

GoogleCodeExporter commented 8 years ago 
even with powersave it goes disturbingly quick.

Original comment by ReedSolo...@gmail.com on 30 May 2011 at 8:42

GoogleCodeExporter commented 8 years ago 
yeahs. its horrible. since the camera_app/sensor patch.
and sometimes the camera app crash with a KERNEL PANIC!
Sometimes my phone randomly crashes few times.

Original comment by Katzen...@gmail.com on 30 May 2011 at 2:09

GoogleCodeExporter commented 8 years ago 
you mean before camera/sensor fix battery was fine ?

you can attach your screenshot of "settings=>about phone=>battery use"

Original comment by wkp...@gmail.com on 30 May 2011 at 4:59

GoogleCodeExporter commented 8 years ago 
The thing that uses the energy is called "Android OS"
That problem happens in the past in OpenEtna too.
Now its fine. Weird.
But when my phone it not atttached to power source then it will fast consume my 
battery power.
Loading the power needs longer.

after the camerapatch i installed the system.img and boot.img again to revert 
it. but that didn't made it unhappen.

Original comment by Katzen...@gmail.com on 30 May 2011 at 7:33

GoogleCodeExporter commented 8 years ago 
Well I left it on overnight unplugged with powersave option set and I was down 
to 60, with wifi off.  I'm thinking wifi is the biggest battery drain, followed 
by actually using the 3G.  but if it's not actually in use i suppose it can go 
a day before running out.  but there seems to be an excessive power drain in 
terms of actually using the wireless/3g as the numbers start counting down on 
the battery meter very quickly when in use.  otherwise, the RC build is 
reasonaby stable for me for the most part.  If it can get a bit tweaked for 
battery performance it'd be perfect.  I love the ease of the keyboard selection 
screen in settings but that's an aside, anyways.

I did notice with tethering that the internal tethering seems less snappy than 
when I was using a tethering app on the korean rom. granted I'm using WPA here 
and I was using WEP there.

But anyways, my best guess is some inefficiency with regards to wifi/3g 
management is causing most of the battery drain.

Original comment by ReedSolo...@gmail.com on 4 Jun 2011 at 4:59

GoogleCodeExporter commented 8 years ago 
i agree, the phone battery seems extremely poor now, and i think it maybe as 
Katzen said about the camera patch.
I was able to standby on 2G up to 36 hours before, but now its only around 14 
hours max.

Original comment by Vic.Eas...@gmail.com on 8 Jun 2011 at 2:44

GoogleCodeExporter commented 8 years ago 
Yep... since the last patch the battery SUCKS hard, even on 2g! any suggestion 
to fix this?

Original comment by jjcastil...@gmail.com on 9 Jun 2011 at 1:26

GoogleCodeExporter commented 8 years ago 
Don't use 2G don't use Wlan, APN, bluetooth, only have phone in powersave mode 
and idle.
Battery sucks hardly -.-

Original comment by Katzen...@gmail.com on 9 Jun 2011 at 4:14

GoogleCodeExporter commented 8 years ago 
i dont have access to wlan everytime i want... sometimes i need 3g/2g, but 3g 
drains so fast the battery that i need to use 2g

Original comment by jjcastil...@gmail.com on 9 Jun 2011 at 4:48

GoogleCodeExporter commented 8 years ago 
i never use it. don't have internet flatrate

Original comment by Katzen...@gmail.com on 9 Jun 2011 at 5:00

GoogleCodeExporter commented 8 years ago 
are the sensors really being put to stand by mode? or do they continue turned 
on?

Original comment by migaxmoi...@gmail.com on 9 Jun 2011 at 5:53

GoogleCodeExporter commented 8 years ago 
don't know

Original comment by Katzen...@gmail.com on 9 Jun 2011 at 5:54

GoogleCodeExporter commented 8 years ago 
For example, "Android System Info" is telling me that the sensors are draining 
power, even if I have orientation switching off:
? accelerometer - 0.2mA
? magnetometer - 6.8mA
? orientation - 7.0mA
  temperature - 0.5mA
? proximity - 0.5mA

The ones with a ? I don't see a reason for being switched on...
Most of these should work at 3.3V... Meaning a power consumption of:
Current = 0.2 + 6.8 + 7.0 + 0.5 = 14.5mA
Power = 14.5 * 3.3 = 47.85mW just for the sensors that are on and shouldn't :s

Original comment by migaxmoi...@gmail.com on 9 Jun 2011 at 7:10

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
WTF. Thx for this informations. :)

Original comment by Katzen...@gmail.com on 9 Jun 2011 at 7:40

GoogleCodeExporter commented 8 years ago 
If I have it on 3G/2G, it only lasts 1 day.  If I have it set for 2G only, and 
switch off synchronize (no gmail synchronizing), it lasts 4 days or more(about 
1% per hour).  I think my signal is poor in this area, so it is constantly 
switching between E, 3G, and HSPA.  Every time it connects to a different 
network, it gets a new IP address, and then needs to re-login to gmail again 
(to tell the push system where new email should go).  It can do that a few 
times a minute all day. I think the same thing happens if location is turned 
on, and Google Latitude.  Latitude would always show me connected to different 
towers, even when I am staying still. 
By keeping it on 2g only, it stays connected to the same tower.
FYI: I use Rogers in a rural area near the U.S. border.

Original comment by davidjam...@gmail.com on 10 Jun 2011 at 4:19

GoogleCodeExporter commented 8 years ago 
I can confirm this issue.
With the last versions it was ok, but now the battery drains within few hours. 
(I had wifi & gps activated) and the phone was all the time lying around with 
screen off (so in standby).

Original comment by ti08m...@gmail.com on 12 Jun 2011 at 10:07

GoogleCodeExporter commented 8 years ago 
any fix for this? :(

Original comment by jjcastil...@gmail.com on 12 Jun 2011 at 4:41

GoogleCodeExporter commented 8 years ago 
same problem here, somethimes even if the battery is fully charged, it drains 
it like hell and its empty after 6 hours even if i dont do much, on android 1.5 
i dont have this problem...

Original comment by marcusschons@gmail.com on 12 Jun 2011 at 6:28

GoogleCodeExporter commented 8 years ago 
thats right... mine its empty like 6-7 hours after full charge on powersave 
settings :(

Original comment by jjcastil...@gmail.com on 12 Jun 2011 at 9:07

GoogleCodeExporter commented 8 years ago 
After calibrating my phone's battery, I get about 2-4 days of battery life, 
depending on use.

Original comment by kura...@gmail.com on 12 Jun 2011 at 10:51

GoogleCodeExporter commented 8 years ago 
I went back to 2.3.3 , to my surprise the battery is normal again. 

I guess, using the outdated gaaps with 2.3.4 might cause the battery drain.( 
Purely my opinion).

Original comment by yakaaith...@gmail.com on 13 Jun 2011 at 11:01

GoogleCodeExporter commented 8 years ago 
this would mean that only the display about battery status is wrong. but if the 
phone is at 0% battery it turned off.

Original comment by Katzen...@gmail.com on 13 Jun 2011 at 12:54

GoogleCodeExporter commented 8 years ago 
we need a fix for this as soon as possible :( is there anyway wkp could fix 
this?

Original comment by jjcastil...@gmail.com on 13 Jun 2011 at 3:36

GoogleCodeExporter commented 8 years ago 
I made battery calibrating.
batterydrain is heavy even with powersave in IDLE mode.

Original comment by Katzen...@gmail.com on 13 Jun 2011 at 4:07

GoogleCodeExporter commented 8 years ago 
you are right katzen, i keep using powersave, no gps, no music, no vibrate, and 
my battery lasts about 6-7 hours :(

Original comment by jjcastil...@gmail.com on 13 Jun 2011 at 5:47

GoogleCodeExporter commented 8 years ago 
I have mine on interactive and I get about 2-4 days of battery life, I use 
https://market.android.com/details?id=com.nema.batterycalibration&feature=order_
history

Original comment by kura...@gmail.com on 13 Jun 2011 at 9:39

GoogleCodeExporter commented 8 years ago 
Can someone else confirm this finding ??

Original comment by ivolu...@gmail.com on 14 Jun 2011 at 11:29

GoogleCodeExporter commented 8 years ago 
I have no battery problems (although I keep most services disabled most of the 
time, like 3G, GPS, WiFi, Bluetooth) and my CPU gobernor is also set to 
Interactive (that's the default, and I've not changed it although I use SetCPU).

My battery loses 5% overnight at most, so I'm pretty satisfied.

Original comment by oldm...@gmail.com on 14 Jun 2011 at 1:56

GoogleCodeExporter commented 8 years ago 
Oh you used the tool I use to calibrate.

Original comment by Katzen...@gmail.com on 14 Jun 2011 at 8:04

GoogleCodeExporter commented 8 years ago 
2-4 days? hmm for me it only works for like 6-8 hours using edge/wifi

Original comment by jjcastil...@gmail.com on 16 Jun 2011 at 9:49

GoogleCodeExporter commented 8 years ago 
yeah. with interactive, powersave or on demand mode
and i recalibrated my battery

Original comment by Katzen...@gmail.com on 17 Jun 2011 at 1:40

GoogleCodeExporter commented 8 years ago 
By calibrating, I mean letting it charge to 100% then using that app and then 
draining my battery to 0% using setcpu's stability test.

Original comment by kura...@gmail.com on 17 Jun 2011 at 8:19

GoogleCodeExporter commented 8 years ago 
Done the calibration app thingie...
Default settings on CPU...
And it has drained twice in around 16h.
Does somebody know where can I get the sources for the drivers?

Original comment by migaxmoi...@gmail.com on 17 Jun 2011 at 9:14

GoogleCodeExporter commented 8 years ago 
you have more luck than we. :(

Original comment by Katzen...@gmail.com on 17 Jun 2011 at 10:28

GoogleCodeExporter commented 8 years ago 
But I'm not using wifi. Only edge is on.

Original comment by migaxmoi...@gmail.com on 17 Jun 2011 at 10:46

GoogleCodeExporter commented 8 years ago 
edge?
i disabled every thing 2g 3g wifi gps apn
power save mode enabled
phone in idle mode (during school)
massivly powerloss
i think its like http://code.google.com/p/openeve/issues/detail?id=117#c24 told 
us

Original comment by Katzen...@gmail.com on 17 Jun 2011 at 10:49

GoogleCodeExporter commented 8 years ago 
I just installed the lastes version and notice right away that battery was 
draining very fast when using wireless.
Cheking iwconfig (via terminal emulator) showed up that power management is off.
I changed it to on (iwconfig wlan0 power on).Don't know if power management is 
enabled in the driver or not and if this will have some effect but maybe it can 
help.

Original comment by jsea...@gmail.com on 19 Jun 2011 at 3:30

GoogleCodeExporter commented 8 years ago 
One more thing: the command needs to be executed everytime the wireless is 
turned on

Original comment by jsea...@gmail.com on 19 Jun 2011 at 3:37