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

[Guest djpalmis]

But seriously the battery doesn't work any better on Stock.

I'm sorry but that is not my opinion.

Maybe it is a placebo but FR12, in my opinion, was way better than FR15 and a little better (if not equal) to Stock.

And it is not a matter of "%".. I talk about battery that reaches the lowest voltage.

I'm not a developer too: I'm an electronic eng that works on embedded since 2009.

My impression is that some service drains battery: But I trust in Paul, and I have nothing to teach him.

Maybe is something related to phone service (like many people say).

Or maybe something that only someone that knows android can solve..

In the meantime I'm re-testing stok ROM 10b..

But I miss FR12 was very-very power friendly.. I changed it because it was some time so slow (like in App management).

[Guest gin0v4]

But seriously the battery doesn't work any better on Stock.

the gage is less jumpy but other than that it is the same for me on stock and on Fr15.

nope, if u would've read my post on the prev page u would now that this is not true:

lost about 30% while i was asleep past 8h... 4 mail accounts set up - one syncs every 2h the other 3 every 8h, fb and twitter (using the lg sns widget) are syncin every 4h and whatsapp was on.

my friend has the exactly same setup but she uses stock rom and lost 5% during the night.

on both phones: wlan and gps and bt switched off, no live wallpaper, we went to bed at the same time and woke up 2gether...

i think that proves that there is sth wrong with the rom (did a full wipe before install and did a battery calibration, already charged it a couple of times after calibration).

[Guest ascito]

I don't know if it can help but I installed a fr15 based ROM (TK Vanilla ones) and I flashed it with battery fully charged and performing a BattStat wipe with CWR. I must say that battery performs a way better, but it's still not good. I just checked and the Standby mode is still eating my battery. I also know that by downgrading baseband to the very first one with .10a stock ROM, gives excelent battery performance.

Edited May 9, 2011 by ascito

[Guest conceptics]

Since FR15 (previously FR12), GPS fix does not work or only when standing right under clear sky and waiting for about 5 minutes. I've tried this on multiple apps (Speedview) and I know this wasn't the case in FR12 (maximum wait 20 seconds!). I see Paul (in the changelog) has said there's a GPS fix conf file now included in FR15.

I'm based in Switzerland. Other than changing the NTP server to my localised one, I can't see anything else I could do to solve the problem?!

Is there any concrete solution to this problem?

[Guest djpalmis]

Since FR15 (previously FR12), GPS fix does not work or only when standing right under clear sky and waiting for about 5 minutes.

Same problem.. That is the second problem that there is not on FR12 (best ROM in my opinion).

[Guest aaww]

Same problem.. That is the second problem that there is not on FR12 (best ROM in my opinion).

I have to agree with you.

[Guest Marco_CH]

Same problem.. That is the second problem that there is not on FR12 (best ROM in my opinion).

I agree, FR12 was "best". Im about to install that again.

I tried them all and even all CM7. But Im giving up, I put my phone on sell. Either Ill sell it (for 2/3 of what it cost me) or Ill update to gingerbread when it eventually comes out.

Also it doesnt get any love from Paul, he is now fixed on SGSII, not that I could blame him :-)

[Guest aaww]

Can you give me some links?

Because I can't understand what does "broken battery driver" means.

There is a MAX17040 that sends battery data via 2-wire interface.

You can monitor battery voltages and you can see that battery voltage goes down.. And that's not an "opininion".

So, Can you explain me what is "boken"...?

Are you still sure about that?

Just had a short twitter chat with Chris Soyars.

He said that the only way to fix the driver issue is to "to rewrite the battery driver from the ground up"

When i asked for specifics he said "braindead math is braindead".

Well we have the source code. hope some one can take a look...

[Guest djpalmis]

When i asked for specifics he said "braindead math is braindead".

Well we have the source code. hope some one can take a look...

Thank you for your help.

Well: I'm Italian.. I am not sure to understand "braindead math is braindead". May you explayn that sentence?

Anyway.

As I said, it is an easy, silly two-wire protocol.

I can assure you that i2c is the easiest protocol in the world!

It doesn't need "special math".

Even if you did not ever code a driver you can easily understand how it works on pag. 7 in Datasheet.

02h–03h VCELL Reports 12-bit A/D measurement of battery voltage. R —

04h–05h SOC Reports 16-bit SOC result calculated by ModelGauge algorithm. R —

06h–07h MODE Sends special commands to the IC. W —

08h–09h VERSION Returns IC version. R —

0Ch–0Dh RCOMP

Battery compensation. Adjusts IC performance based on

application conditions.

R/W 9700h

FEh–FFh COMMAND Sends special commands to the IC. W —

The "broken" driver has to read on address 0x2 via I2C.. that's the easyest way. And as you can see it reads battery voltages! You can see battery voltages with an app such as "battery calibrator": Voltages are correctly read! There are some "special" commands like RCOMP.. I don't have time to study them but I assure that there is nothing wrong: what we need is a battery voltage measurament: and it measures! Sorry If I spealt something wrong. EDIT: I downloaded source code. As you can see in kernel there is this file max17040_battery.c: And this are the defines:

#define MAX17040_VCELL_MSB	0x02

#define MAX17040_VCELL_LSB	0x03

#define MAX17040_SOC_MSB	0x04

#define MAX17040_SOC_LSB	0x05

#define MAX17040_MODE_MSB	0x06

#define MAX17040_MODE_LSB	0x07

#define MAX17040_VER_MSB	0x08

#define MAX17040_VER_LSB	0x09

#define MAX17040_RCOMP_MSB	0x0C

#define MAX17040_RCOMP_LSB	0x0D

#define MAX17040_CMD_MSB	0xFE

#define MAX17040_CMD_LSB	0xFF

As you can see (max17040) memory maps is correct.

It is very clear to understand even if you are not an eng!

So: In my opinion it is a shame to call that driver "Broken".......

Are you agree with me?!

PS: As you can see they don't use "special math".. Only a simple read ov A/D converter..

@Marco_CH: Tomorrow I will come back to FR12.. Stock is too.. STOCK! :unsure:

Edited May 9, 2011 by djpalmis

[Guest Marco_CH]

someone here posted an answer from LG Support Russia stating that there is a battery drain issue in the rom. this suggests that it is not just bad reading of data. its just consuming way too much power.

e.g. with stock or the FR roms I have up to 50% battery drain on standby. with CM7 that was around 20%. so whatever is being adjusted, it will not fix the problem. that most likely needs a complete new rom (CM7) or a fix from LG directly (Gingerbread, they wont spend time on this mess here)

some people state that they dont have a battery problem at all. if thats the case, then it might be affecting some production units only. on this forum you mostly find those who have a problem, not those who dont.

just finished configuring FR12, nearly like the phone again :unsure:

[Guest Luik]

Since FR15 (previously FR12), GPS fix does not work or only when standing right under clear sky and waiting for about 5 minutes. I've tried this on multiple apps (Speedview) and I know this wasn't the case in FR12 (maximum wait 20 seconds!). I see Paul (in the changelog) has said there's a GPS fix conf file now included in FR15.

I'm based in Switzerland. Other than changing the NTP server to my localised one, I can't see anything else I could do to solve the problem?!

Is there any concrete solution to this problem?

There is a problem at the moment with the google a-gps server. Try using supl.nokia.com instead.

http://www.google.com/support/forum/p/maps...9ae5d&hl=en

[Guest gin0v4]

pls paul, just one more version for the 2x, then u can play with your galaxy s2 :unsure:

(gb release would be appreciated :))

[Guest federicoc]

[...]

PS: As you can see they don't use "special math".. Only a simple read ov A/D converter..

Hi 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.

Regards

F.

[Guest conceptics]

I agree, FR12 was "best". Im about to install that again.

I tried them all and even all CM7. But Im giving up, I put my phone on sell. Either Ill sell it (for 2/3 of what it cost me) or Ill update to gingerbread when it eventually comes out.

Also it doesnt get any love from Paul, he is now fixed on SGSII, not that I could blame him :-)

Is there a way to access the kitchen of an older build? I still have FR12, but I since have added/changed a few apps that are important and don't really want to download the pre-baked one.

Also, is Modaco a one man show? I'm hoping not - I've been really liking the improvements with each upgrade and it would be a shame to see development stalled, especially once things start to improve from LG and new upgrades come out. There are also some bugs that still aren't solved and have not received any answer to yet - MMS sending bug.

[Guest mankian]

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

[Guest 719rock]

hi pual, can FR with CM7 on FR16 test?

Cm7 Working so nice on phone.

hope u can update plz!!! :unsure:

[Guest maedox]

Is there a way to access the kitchen of an older build? I still have FR12, but I since have added/changed a few apps that are important and don't really want to download the pre-baked one.

Also, is Modaco a one man show? I'm hoping not - I've been really liking the improvements with each upgrade and it would be a shame to see development stalled, especially once things start to improve from LG and new upgrades come out. There are also some bugs that still aren't solved and have not received any answer to yet - MMS sending bug.

Yes, MoDaCo is a one-man show I'm afraid. If you only want to add some apps you can just push them afterwards via ADB or add them to the right directory in the zip file you already have. Just make a backup first and you'll be fine. Let us know what you want to add and we and most importantly Paul can comment on if it's plug 'n' play or not.

[Guest conceptics]

There is a problem at the moment with the google a-gps server. Try using supl.nokia.com instead.

http://www.google.com/support/forum/p/maps...9ae5d&hl=en

Excellent catch, thanks a lot. Is this something that will solve itsself (when google updates the certificate) or will there have to be an update on our end as well? If not, then I may as well wait, as I'm not too concerned about GPS not working properly now. Also, where do you change that address?

[Guest conceptics]

Yes, MoDaCo is a one-man show I'm afraid. If you only want to add some apps you can just push them afterwards via ADB or add them to the right directory in the zip file you already have. Just make a backup first and you'll be fine. Let us know what you want to add and we and most importantly Paul can comment on if it's plug 'n' play or not.

Thanks for the info. About the FR12 build - I actually wanted an 'as empty' build as possible. My personal builds consist of only the LG Keyboard, fonts, google-desk-clock, no-calenders at all, lg-dialer, lg-sms/mms, lg-memo app, stock theme, full-battery pop up block, no-music buttons in slider (but keep the other on-off switches) . IMO light, is right. :unsure:

Having the kitchen of the older version would be great, as I can just do it from there. Seeing as GPS would have been the only reason to revert back to FR12 for me (and that may be down to the expired SSL certificate), I may not need it after all.

[Guest Paul]

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

[Guest ascito]

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

I did this test and I can confirm that there is an improvment in battery life. I tried it with TK Vanilla version of MCR FR15.

[Guest mankian]

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

[Guest gin0v4]

i did that yesterday evening paul and my battery is at 26% right now.

will use. read my prev post pls-this night i only lost 21% in 8h which is still way too much!

i did the calibration via cwm while charger was plugged in and phone at 100%.....

will use the phone till it is completly dead and then charge it for a few h whrn its off...

calibrating through an app did not helped at all...

[Guest masi0]

i did that yesterday evening paul and my battery is at 26% right now.

will use. read my prev post pls-this night i only lost 21% in 8h which is still way too much!

i did the calibration via cwm while charger was plugged in and phone at 100%.....

will use the phone till it is completly dead and then charge it for a few h whrn its off...

calibrating through an app did not helped at all...

Do the full wipe/factory reset, do not setup any accounts/install any software just see the battery behaviour then

[Guest gin0v4]

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!

Edited May 10, 2011 by gin0v4