28 Jul Fr19: MoDaCo Custom ROM for the LG Optimus 2X with Online Kitchen (new: custom kernel)

[Guest 719rock]

For those with battery 'issues', could you confirm you've tested a simple fix such as charging to 100%, rebooting in recovery, deleting battery stats (adb shell mount /data && adb shell rm /data/system/batterystats.bin) and restarting?

I suspect this WILL help (it seemed to make the battery meter more reliable after a cycle here)... if this is confirmed, I can add the battery stats wipe to the install process...

Still toying with the G2X Gingerbread, but don't have the RIL working as yet. :unsure:

P

Please, first dealing with battery problems.

This battery showed abnormal when I uaed first time it's a full power, but the power display just have 92%, and 95% in three minutes later.

However everyone still looking for the Gingerbread operation at FR.

Edited May 10, 2011 by 719rock

[Guest masi0]

read my prev post on last page - did a full wipe before i installed fr15 (multiple times)

and why should i disable my accounts? i do not want to fool

myself thinkin ouh, battery life is not that bad - bullshit!

i wqnt to test the battery in a real life scenario!

i suppose first you must exclude all issues that might cause the problem then conclude

[Guest aaww]

So this battery issue (sorry to keep going on about it) - Since the guy in cyanogenmod noticed the driver is crap, does that mean when cyanogen comes out of nightly into stable for o2x it means it will have a better battery driver? or is this something only LG can sort?

I got my o2x a few days ago, its got two really big problems, I just want to know if you guys have the same, and its a software glitch or should I return it to the store.

its completely stock

problems are: Wifi will not work after a few hours of the phone being switched on. The phone will just freeze for a few seconds then it will say "error". A reboot fixes this for another few hours.

Battery: when charging (or even discharging sometimes) the meter doesnt update. for example, I run it down to 18%, plug it in overnight and in the morning it says 18%. then after a reboot it says 100% as it should, then i use it throughout the day it still says 100% until I reboot it again and the correct level is shown. annoying!

apologies if this is the wrong place to post. if Pauls rom does fix either of these two issues I would be interested to try it...

Cheers

Cris didn't say they will fix it in CM, he said that it will be solved "if someone wants to rewrite the battery driver from the ground up, then yes."

[Guest aaww]

For those with battery 'issues', could you confirm you've tested a simple fix such as charging to 100%, rebooting in recovery, deleting battery stats (adb shell mount /data && adb shell rm /data/system/batterystats.bin) and restarting?

I suspect this WILL help (it seemed to make the battery meter more reliable after a cycle here)... if this is confirmed, I can add the battery stats wipe to the install process...

Still toying with the G2X Gingerbread, but don't have the RIL working as yet. :unsure:

P

tried it on my Fr15 I can confirm that there is an improvement in battery performance.

[Guest aaww]

how do you reboot into recovery mode on one of these?? or can it just be done from the ADB shell in normal mode?

if you have Paul's CW turn off your phone, then press power + vol key untill it say android on the screen, then release they keys and you are in.

[Guest Paul]

I also don't see people with battery issues confirming they have tried a wipe / base install...

P

[Guest masi0]

I also don't see people with battery issues confirming they have tried a wipe / base install...

P

maestro - do you have battery issue yourself?

had some battery stats and seems like lg.carhome is eating the sensors. also i think that weather widget is doing this as well.

we all should all be happy with 2x anyway, go and check Xperia Arc forums - people are complaining way way more than on all 2x forums :unsure:

[Guest inza]

I also don't see people with battery issues confirming they have tried a wipe / base install...

P

I wiped everything that you can wipe in CWM before I flashed this. The Battery time is getting a bit better after a few charge cycles but I still have the issue with the Dialer using partial wake a lot.

[Guest withoutwings]

For those with battery 'issues', could you confirm you've tested a simple fix such as charging to 100%, rebooting in recovery, deleting battery stats (adb shell mount /data && adb shell rm /data/system/batterystats.bin) and restarting?

I suspect this WILL help (it seemed to make the battery meter more reliable after a cycle here)... if this is confirmed, I can add the battery stats wipe to the install process...

Still toying with the G2X Gingerbread, but don't have the RIL working as yet. :unsure:

P

Paul, there are two clear issues that are not battery stats related which do drain the battery:

• Dialer partial wake is up to 50% of the "time since last unplugged". It doesn't seem to matter that you haven't used the phone.
  
• Alarm/Clock sometimes "latches" the sensor use on 100% of the time. Happens for me almost every time when my alarm goes off with the phone plugged in to charge, I hit snooze once or twice, then stop the alarm and unplug the phone.
  

Obviously wiping battery stats will help slightly thanks to LG's crappy battery driver, but the above two issues are clearly adding to battery drain and I would wager that one or both of them happen to every single person who is complaining of poor battery performance (including me). Would you mind taking a look into those problems for the next FR release?

Edited May 10, 2011 by withoutwings

[Guest gin0v4]

I also don't see people with battery issues confirming they have tried a wipe / base install...

P

then u do not read my posts -.-

are all of u ignoring me????

i did everything u guys told me, even before u told me (cuz i aint stupid :unsure:)

[Guest johnnydj]

Cris didn't say they will fix it in CM, he said that it will be solved "if someone wants to rewrite the battery driver from the ground up, then yes."

I'm using CM builds for a a week now, and I must say that the battery life is visibly better than any of Paul's ROM's.

8 hours of standby with wifi on I lost only 3% battery which I could never achieve with Paul's ROM.

It might be that Gingerbread is better in managing things.

[Guest masi0]

I'm using CM builds for a a week now, and I must say that the battery life is visibly better than any of Paul's ROM's.

8 hours of standby with wifi on I lost only 3% battery which I could never achieve with Paul's ROM.

It might be that Gingerbread is better in managing things.

Ok - is it stable? :unsure: i dont thin so , is everything working flawless? :) is radio working? 8mpix camera? video? bt?

[Guest Trym Hansen]

Ok - is it stable? :) i dont thin so , is everything working flawless? :) is radio working? 8mpix camera? video? bt?

No, CM7 is far from stable, and should at this time only be considered a preview. Lots of basic stuff isn't working yet.

::Trym

[Guest destesi]

I also don't see people with battery issues confirming they have tried a wipe / base install...

P

Hi Paul, it's my first post so first of all let me thank you for your great work on this device.

In reply of your request I can describe my experience: I tried Fr12 and Fr14 with normal behaviour when it comes to battery.

Then I tried Fr15:

* restore factory default from recovery

* wiped cache and dalvik cache

* installed FR15

* recovered all the application with Titanium backup

First day of use I've found no lag after app install (as in Fr12-14) but the battery lasted 1/3 less than the previous installation.

Then I tried to wipe the battery stats as suggested from someone and made two cycle of recharge from 20% to 100%. But the battery lasted nearly the same amount of time.

My setup is 3G active from 8.30 A.M. to 18.00 A.M. then Wifi when at home (using tasker). At 18.30 Fr15 battery was nearly depleted. An Fr12 was beetween 30% to 40%. With 3g/Wifi disabled even Fr15 lasts forever.

Tonight I'll try to bake a new FR15 without LG stuff, only AOSP and see if if make any difference in the next days. If there is a preferred way to install/test it other than what reported above then all advice/hints are welcome.

[Guest masi0]

Hi Paul, it's my first post so first of all let me thank you for your great work on this device.

In reply of your request I can describe my experience: I tried Fr12 and Fr14 with normal behaviour when it comes to battery.

Then I tried Fr15:

* restore factory default from recovery

* wiped cache and dalvik cache

* installed FR15

* recovered all the application with Titanium backup

First day of use I've found no lag after app install (as in Fr12-14) but the battery lasted 1/3 less than the previous installation.

Then I tried to wipe the battery stats as suggested from someone and made two cycle of recharge from 20% to 100%. But the battery lasted nearly the same amount of time.

My setup is 3G active from 8.30 A.M. to 18.00 A.M. then Wifi when at home (using tasker). At 18.30 Fr15 battery was nearly depleted. An Fr12 was beetween 30% to 40%. With 3g/Wifi disabled even Fr15 lasts forever.

Tonight I'll try to bake a new FR15 without LG stuff, only AOSP and see if if make any difference in the next days. If there is a preferred way to install/test it other than what reported above then all advice/hints are welcome.

are you using any 3rd party apps as juice defender etc? :unsure:

[Guest d-droid]

Paul, there are two clear issues that are not battery stats related which do drain the battery:

• Dialer partial wake is up to 50% of the "time since last unplugged". It doesn't seem to matter that you haven't used the phone.
  
• Alarm/Clock sometimes "latches" the sensor use on 100% of the time. Happens for me almost every time when my alarm goes off with the phone plugged in to charge, I hit snooze once or twice, then stop the alarm and unplug the phone.
  

Obviously wiping battery stats will help slightly thanks to LG's crappy battery driver, but the above two issues are clearly adding to battery drain and I would wager that one or both of them happen to every single person who is complaining of poor battery performance (including me). Would you mind taking a look into those problems for the next FR release?

Tried this?

http://android.modaco.com/content/zte-blad...e-dialer-issue/

I'm having the same problem but the above was already unchecked for me. (It's in gestures settings and not sound for the o2x).

[Guest PAQman]

I also don't see people with battery issues confirming they have tried a wipe / base install...

Hi Paul,

I also had battery issues after updating to FR15. I've deleted the batterystats, did a full wipe... everything! Nothing helped. So I switched back to FR13 and everything seems ok. The installed Software is always the same. At the moment I'm very happy with the battery.

Much more annoying is the lack of GPS. I've tested all the thing posted in differnent threads, but I can't manage to get a GPS-Lock. My N1 got a lock in 2-3 seconds. My 2X isn't able to get a lock after 15 Minutes. GPS Status (the app from Market) is showing 5-8 satellites. But they stay grey and the 2X won't get a lock. I also tested it with a fresh install (wipe), but that won't help...

This evening I will return to stock to test if my device is broken. But I'm sure it is not.

[Guest johnnydj]

Ok - is it stable? :unsure: i dont thin so , is everything working flawless? :) is radio working? 8mpix camera? video? bt?

- radio is working without any problems for me

- video sometimes crashes

- pictures are fine

- bluetooth is working

- games are working

- sometimes browser crashes and things.

it's not stable, but my battery lasts 3-4 times longer at least and if you know how to use it, it won't crash until a stable version will come out.

I'm just pointing out the options and that the battery drain IS/NEVER WAS present in any CM7 build.

[Guest destesi]

are you using any 3rd party apps as juice defender etc? :unsure:

No, with Galaxy S I used to have Green Power manage my data connection but had problem using it correctly with G2x and Stock/Fr12. So removed it for good before Fr13.

I'm pretty sure there is no apps killing my battery but will try next Fr15 bake as is for at least two or three days.

[Guest djpalmis]

reading only the voltage is not enough to measure the state of charge of a battery, in general its a good indication but as you can read from the datasheet there is another more interesting register where the MAX1740 saves the result of all the hidden (and magical) math to calculate the real SOC (State of Charge) of the battery.

I agree with you that this driver shouldn't be so much complex, reading the correct register should give us what we need.

Hi Federico, :unsure:

You are right.. But I not agree with you. But let's talk about!

First of all, as you can see here: http://tomoyo.sourceforge.jp/cgi-bin/lxr/s...17040_battery.c

124 static void max17040_get_soc(struct i2c_client *client)

125 {

126		 struct max17040_chip *chip = i2c_get_clientdata(client);

127		 u8 msb;

128		 u8 lsb;

129 

130		 msb = max17040_read_reg(client, MAX17040_SOC_MSB);

131		 lsb = max17040_read_reg(client, MAX17040_SOC_LSB);

132 

133		 chip->soc = msb;

134 }

135

So, as you can see SAMSUNG DEVELOPERS (So, please, stop blaming LG :) have done a very good work: they reads the right register.

I don't know (please, help me if anybody have a little time) if kernel calls max17040_get_soc!!!

And anyway.. I have to say a word about battery stats (that i really don't know how android handles..)

Quoting datasheet:

The MAX17040/MAX17041 use a sophisticated Li+ battery-

modeling scheme, called ModelGauge™ to track

the battery’s relative state-of-charge (SOC) continuously

over a widely varying charge/discharge profile. Unlike

traditional fuel gauges, the ModelGauge algorithm eliminates

the need for battery relearn cycles and an external

current-sense resistor.

So: It is a placebo that "charging and discharging"/deleting stats things get better!

And after all I repeat: It is not a matter of battery %!!!

It is a simple problem:

On FR12 battery is under voltage after X hours.

OnStock battery is under voltage after Y hours.

On FR15 battery is under voltage after Z hours.

Where X>=Y>>Z.

STOP!

So, it is not important how system computes %s.. It is important that after X hours Battery voltages is under treashold (3200mV? You know: battery LOW)!

Edited May 10, 2011 by djpalmis

[Guest d-droid]

Hi Federico, :unsure:

You are right.. But I not agree with you. But let's talk about!

First of all, as you can see here: http://tomoyo.sourceforge.jp/cgi-bin/lxr/s...17040_battery.c

124 static void max17040_get_soc(struct i2c_client *client)

125 {

126		 struct max17040_chip *chip = i2c_get_clientdata(client);

127		 u8 msb;

128		 u8 lsb;

129 

130		 msb = max17040_read_reg(client, MAX17040_SOC_MSB);

131		 lsb = max17040_read_reg(client, MAX17040_SOC_LSB);

132 

133		 chip->soc = msb;

134 }

135

So, as you can see SAMSUNG DEVELOPERS (So, please, stop blaming LG :) have done a very good work: they reads the right register.

I don't know (please, help me if anybody have a little time) if kernel calls max17040_get_soc!!!

And anyway.. I have to say a word about battery stats (that i really don't know how android handles..)

Quoting datasheet:

So: It is a placebo that "charging and discharging"/deleting stats things get better!

And after all I repeat: It is not a matter of battery %!!!

It is a simple problem:

On FR12 battery is under voltage after X hours.

OnStock battery is under voltage after Y hours.

On FR15 battery is under voltage after Z hours.

Where X>=Y>>Z.

STOP!

So, it is not important how system computes %s.. It is important that after X hours Battery voltages is under treashold (3200mV? You know: battery LOW)!

Thanks for a great tech-explanation! :P

[Guest gin0v4]

thinking about installin fr12 again till fr16 is or any gb release is out - battery still suckZ after i did all things u guys recommended :unsure:

Edited May 10, 2011 by gin0v4

[Guest Frank Sem-Jacobsen]

Tried this?

http://android.modaco.com/content/zte-blad...e-dialer-issue/

I'm having the same problem but the above was already unchecked for me. (It's in gestures settings and not sound for the o2x).

It is unchecked for me as well. As an experiment I have unchecked every other gesture as well since in my experience they do not work anyway. Maybe it has some impact...?

[Guest defectivereject]

Yes.

Fully wiped reset the lot

Its defo an issue with the dialer.

[Guest djmcnz]

Re: Battery

Message is clear, needs to be looked at.

Further discussion here: http://android.modaco.com/content/lg-optim...iscussion-here/

Please