Stock 20L: 3g disconnects and huge battery drain

[Guest vrowdy]

Note: I posted this also in my GPS/newbie questions topic, but I thought it might go unnoticed there because of the title and it is really big problem for me.

----------------------------------

I have confirmed the following issue on my Optimus 2x with stock 20L. Nothing else, nothing special.

When I leave the phone standby for several hours (eg. during the night), when I get back to it and turn on the screen, the network signal/3G indicators are white - meaning no internet connection.

After around 10 seconds, 3G reconnects itself.

While this is annoying, since you don't get any notifications from programs using the internet (WhatsApp, Facebook etc), it gets worse.

After 3G reconnects itself, the battery drains really fast: about 30 seconds for 1%. So in a few minutes your battery will be completely drained.

This even continues while rebooting.

For example: I come back to my phone and it has 46% left. Then I notice the 3G disconneced and reconnecting and then power starts dropping really fast. I reboot at 43% power left. After the reboot, there's only 18% left but the draining has stopped.

I at least had this happen twice in four days.

Is anyone else noticing this, or does any of the developers out here perhaps has a fix or a custom rom in which it is fixed?

I really like 20L for some new features, but I'm also experiencing issues with GPS and now also this... I'm really thinking of going back to 10D.

Thanks for any help or insights you can give me.

[Guest Basil 123]

I flashed the 'new' BB + RIL over Gr4 and noticed an increase in battery use.

Perhaps we should look at v20L as another 'leak' even though it has been officially released by LG?

I'm going to wait till Paul has released his Gr5 and read all the comments on it - Gr4 is rock solid with the 999switch and HP kernel and the network time disabled.

my 2p

Baz

Edited November 7, 2011 by Basil 123

[Guest Ximo F. Verde]

Note: I posted this also in my GPS/newbie questions topic, but I thought it might go unnoticed there because of the title and it is really big problem for me.

----------------------------------

I have confirmed the following issue on my Optimus 2x with stock 20L. Nothing else, nothing special.

When I leave the phone standby for several hours (eg. during the night), when I get back to it and turn on the screen, the network signal/3G indicators are white - meaning no internet connection.

After around 10 seconds, 3G reconnects itself.

While this is annoying, since you don't get any notifications from programs using the internet (WhatsApp, Facebook etc), it gets worse.

After 3G reconnects itself, the battery drains really fast: about 30 seconds for 1%. So in a few minutes your battery will be completely drained.

This even continues while rebooting.

For example: I come back to my phone and it has 46% left. Then I notice the 3G disconneced and reconnecting and then power starts dropping really fast. I reboot at 43% power left. After the reboot, there's only 18% left but the draining has stopped.

I at least had this happen twice in four days.

Is anyone else noticing this, or does any of the developers out here perhaps has a fix or a custom rom in which it is fixed?

I really like 20L for some new features, but I'm also experiencing issues with GPS and now also this... I'm really thinking of going back to 10D.

Thanks for any help or insights you can give me.

The 3G data issue has been present in more than a few terminals but it seems to have something to do with specific networks in specific countries. 2-3 users here have had this issue (including me) and at least one of them (rasta666) have resolved it by baking a specific custom Gr4. After searching in spanish o2x forums it seems that many more users experience it in Spain than the rest of the world, validating (maybe) the specific networks theory (note that i live in spain but i got my o2x from expansys UK so its unlikely to be a 'bad localized batch').On this page at xda http://forum.xda-developers.com/showthread.php?t=1154127 there's a zip file on OP with the major bugs of o2x. Its believed that bug No.6 on that list is probably our case. My o2x still suffers from it (as well as network drops even though there's a full-bar signal) and im still looking for a solution. Also read posts at and .

[Guest vrowdy]

Thanks for your reply.

I found this in that thread you mentioned:

Make sure to flash the corrosponding 0725 baseband, otherwise you will get Fast Dormancy issues on 3g draining the battery really fast. The 0725 baseband from the v20l release is available on XDA. This probably means not every baseband is the same, even if they have the same name/date.

I flashed the original 20L KDZ file, that includes the baseband.

I do hope in the GR5 it can and will be fixed because this is really annoying (as is the GPS bug, btw).

I can't believe this got through LG's Quality Assurance...

[Guest Ximo F. Verde]

Thanks for your reply.

I found this in that thread you mentioned:

I flashed the original 20L KDZ file, that includes the baseband.

I do hope in the GR5 it can and will be fixed because this is really annoying (as is the GPS bug, btw).

I can't believe this got through LG's Quality Assurance...

Thats true, there are actually 3 different BB all appearing as 725 after flashing. You can rest assured that by flashing the kdz file you have the correct one on your phone.

[Guest HariSeldon85]

Thats true, there are actually 3 different BB all appearing as 725 after flashing. You can rest assured that by flashing the kdz file you have the correct one on your phone.

Same 4 me... absurde battery draining

[Guest vyu]

The disconnection issue is also happened at CM 7.1.0 rel for my phone. I think it is not the 20L problem but the BB / 2.3 problem. I am still finding the solution

[Guest vrowdy]

The disconnection issue is also happened at CM 7.1.0 rel for my phone. I think it is not the 20L problem but the BB / 2.3 problem. I am still finding the solution

Would it be possbile then to flash the 2.2.2 Froyo baseband onto 20L?

Or am I saying something crazy now?

But the way this sounds, it's unlikely this will be fixed in Paul's GR5 release, since that does not include the baseband AFAIK.

So, only options then are to go back to 10D or wait for another baseband update from LG?

Also, any ideas as to what triggers this condition?

Perhaps we then can have a work-aroud, where we prevent this from happening by doing something different? It only seems to happen when I don't use the phone for at least 4 hours or so. Perhaps some program that can activate the screen and press a button or something every xx hours?

Edited November 7, 2011 by vrowdy

[Guest Dzhedaj]

If it was a BB problem, I wouldn't have great data reception with no disconnects while idle with GR4 + V20L baseband + RIL. Battery life is also not different from other V20x releases I've tried.

Maybe you should check which RIL version you have?

[Guest Diskbox]

Just to add my own experience to the mix. I did a complete wipe of everything then flashed the kdz file for 20L then ran getril to make sure I had everything matching. Battery calibration has been done twice also two days apart.

I'm now getting around 54 hours on battery life now with the following configuration.

Airplane mode, 2300-0600

Juice Defender in balance mode

+Fireworks life wallpaper

gmail configured for two separate accounts - not sure how much extra load this has on push/pull data.

This includes G+, facebook, email, a few short calls, three sms messages and news usage.

I'm now getting much more battery life than I did on both GR4 and nightly 18(7/8) even though I've turned on the live wallpaper.

Will try and compare how stock and GR5 differ with regard to battery life.

Diskbox

[Guest vrowdy]

If it was a BB problem, I wouldn't have great data reception with no disconnects while idle with GR4 + V20L baseband + RIL. Battery life is also not different from other V20x releases I've tried.

Maybe you should check which RIL version you have?

I'm sorry, I don't know what a RIL is - well, I just looked it up on Wikipedia of course, but I don't know how this relates to the baseband :)

I'm really new to all this. Could you please help me understand the following?

-------

So, if you could just clear this up for me please, I would be very grateful:

On my phone, there are three partitions: Recovery (which contains stock recovery or CWM), System partition (which contains/includes the OS), Data Partition (which contains all normally installed Apps+data) and the InternalSD (which can also contain Apps if you install them there). There's also the ExternalSD which is the real, physical SD-Card.

You can flash these three partitions all together or seperately.

Then there's also the BaseBand and the RIL, both of which are completely seperate from the 'normal' file systems.

For example: a KDZ file contains and flashes the following: recovery partition, system partition, baseband and RIL. It leaves your data partition, internal SDCard (and external SDCard) untouched. That's why you still have your Apps and Settings after flashing KDZ. It also does remove CWM.

Then there are the CWM-Zip files (updates) you can flash.

In order to do this, you need to have CWM installed in the recovery partition and have root.

Then you copy the ZIP file to your External SD Card and reboot into recovery mode.

There you can select the ZIP file and then the following will be flashed: system partition, data partition(?). BaseBand, RIL and Recovery will be untouched.

Is this correct?

Four questions:

1) There is CWM and there is Rommanager (in Market). Is the latter just some kind of 'helper' GUI for the first? You don't really need Rommanager in order to use CWM?

2) Can I boot into CWM recovery, and then make a full backup of system and data partition into a ZIP file on the External SD Card? (and later restore this in the same manner?) If so, I can safely try GR5 (when it's out) and if it doesn't work, just restore the backup I made and all apps and settings will be back?

3) There also a 'wipe' being mentioned and a 'nandroid backup'. What is meant by these two? Is 'wipe' just an option when booting into CWM? If so, what will it wipe exactly?

4) There's also SmartFlash. This is a Windows tool which can flash all of the above (system, data, recovery, BB, RIL but not InternalSD or ExternalSD). The flash file you give it determines what will be flashed. Do I need CWM installed to use SmartFlash or does it only work with stock recovery? I do understand CWM and SmartFlash are just different tools to the same goal, eg. like Winrar and Winzip.

----------

I really hope you're willing to clarify this for me, because I have the feeling I really need to understand how this all works if I ever want to be able to fix all issues my phone has and use it normally.

And the most important question would be then: how can I check the RIL version I have?

[Guest mparack]

The 3G data issue has been present in more than a few terminals but it seems to have something to do with specific networks in specific countries. 2-3 users here have had this issue (including me) and at least one of them (rasta666) have resolved it by baking a specific custom Gr4.

Agree on the specific country theory based on my experience. I was on t mobile in UK with no issues but when I switched to Reliance in India I started getting regular data drops.

Will find out for sure in a couple of days when I switch back to t mobile

[Guest vrowdy]

Agree on the specific country theory based on my experience. I was on t mobile in UK with no issues but when I switched to Reliance in India I started getting regular data drops.

Will find out for sure in a couple of days when I switch back to t mobile

Just to make my issue more clear: as soon as 3G reconnects automatically (when you turn on the screen), the battery immediately discharges itself fully at about 1% per 30 seconds. So it's one problem, not a problem with 3G and also a problem with the battery, but one big problem.

[Guest MrOtacon]

You are not alone with this problem buddy.

I too experience it.

I do not believe this to be localized to Spain.

My Phone is on Orange in the UK.

I will note - I was a lucky one. I have never had any random FCs or BSODs with my LG before this Rom. Even 10C / D was pretty stable for me.

I was previously running CM7.1

I ran back to ext3 - Then Installed KDZ for 10D european Open. (I realise back to EXT3 may probably not have been required to flash the KDZ for froyo 10d - but Sod it, I was trying to be safe!!)

Rooted with superoneclick

Wiped system, Cache and Dalvik.

Installed Pauls Deox. 20L

Installed Extracted Baseband

Installed Ril (GetRil)

It did work ok for a while, but after about an hour I picked up my phone to check why I hadn't received a pretty important phone call, and low and behold - the white reception icons.

Trying to goto airplane mode causes an error - with a popup "Network is Unavailable". The only way to get it back is to restart the phone. BUT if you restart - the battery displays about 60% less than what it displayed before you restarted (with the crashed radio)

Something is massively draining the battery.

I figured I would then flash the KDZ

Then used the recommended root guide for gingerbread from XDA, worked a treat.

The same problem has occurred since I tried that - multiple times. And the drain is extremely bad. Late for work on Friday due to the alarm pulling my phone out of standby and the battery draining before my snooze (5 mins) has set alarm off again.

I Have tried the four fls Baseband files (I know the KDZ includes the baseband flash, but I wanted to cover everything)

I confirmed my Ril was correct for the baseband I was using with each flash, using GetRIl from MarketPlace.

Was P--sing me off so much, I have rolled back to FR19, with HP Extreme, and switch999, converted to EXT4.

Would love to get gingerbread back - but I can't use it in a state whereby the alarms might not even go off - or I am out and about and people cannot get hold of me. I'm the head of software development and systems administrator at my place of work - I get a crazy amount of phone calls!

One thing to try - is this:

Goto Mobile Network settings in wireless settings

Change your network type to WCDMA Only (3g Only) and make sure use only 2g network isnt ticked.

Im sure when I was trying to debug this, WCDMA was working for me without the error - but I didn't test it for long enough as I still noticed slight battery drain. Probably partly due to always using 3G, also the LG Onscreen Keyboard (VNC Type app) is using a LOT more power in this rom - Previous roms battery stats used to put it near the bottom of the list - but on this Rom its usually a rock solid 3rd of 4th placer at 20-odd percentish!

I can also add this - Touch wood (knock on wood for you americans around here :P) - I didnt have any GPS problems with 20L :D (for what its worth!!)

Edited November 7, 2011 by MrOtacon

[Guest vrowdy]

One thing to try - is this:

Goto Mobile Network settings in wireless settings

Change your network type to WCDMA Only (3g Only) and make sure use only 2g network isnt ticked.

I have changed this setting as you recommended and will see what happens.

If it doesn't work, I hope GR5 or some other custom ROM will be able to fix it. I really like the front cam being accessible with Skype and other programs.

And otherwise I'll give FR19 a try then and hope for ICS some day.

Or perhaps LG will release a 20M that fixes everything.

I still really can't believe this software ever made it through LG's QA... It's just crap and it's all software related.

Sure, I like to tinker with my devices, my AppleTV2, my old X1 with Android... But I bought the O2X expecting a working smartphone. And minor issues I can live with, but these are major problems.

[Guest Ximo F. Verde]

You are not alone with this problem buddy.

I too experience it.

I do not believe this to be localized to Spain.

My Phone is on Orange in the UK.

I will note - I was a lucky one. I have never had any random FCs or BSODs with my LG before this Rom. Even 10C / D was pretty stable for me.

I was previously running CM7.1

I ran back to ext3 - Then Installed KDZ for 10D european Open. (I realise back to EXT3 may probably not have been required to flash the KDZ for froyo 10d - but Sod it, I was trying to be safe!!)

Rooted with superoneclick

Wiped system, Cache and Dalvik.

Installed Pauls Deox. 20L

Installed Extracted Baseband

Installed Ril (GetRil)

It did work ok for a while, but after about an hour I picked up my phone to check why I hadn't received a pretty important phone call, and low and behold - the white reception icons.

Trying to goto airplane mode causes an error - with a popup "Network is Unavailable". The only way to get it back is to restart the phone. BUT if you restart - the battery displays about 60% less than what it displayed before you restarted (with the crashed radio)

Something is massively draining the battery.

I figured I would then flash the KDZ

Then used the recommended root guide for gingerbread from XDA, worked a treat.

The same problem has occurred since I tried that - multiple times. And the drain is extremely bad. Late for work on Friday due to the alarm pulling my phone out of standby and the battery draining before my snooze (5 mins) has set alarm off again.

I Have tried the four fls Baseband files (I know the KDZ includes the baseband flash, but I wanted to cover everything)

I confirmed my Ril was correct for the baseband I was using with each flash, using GetRIl from MarketPlace.

Was P--sing me off so much, I have rolled back to FR19, with HP Extreme, and switch999, converted to EXT4.

Would love to get gingerbread back - but I can't use it in a state whereby the alarms might not even go off - or I am out and about and people cannot get hold of me. I'm the head of software development and systems administrator at my place of work - I get a crazy amount of phone calls!

One thing to try - is this:

Goto Mobile Network settings in wireless settings

Change your network type to WCDMA Only (3g Only) and make sure use only 2g network isnt ticked.

Im sure when I was trying to debug this, WCDMA was working for me without the error - but I didn't test it for long enough as I still noticed slight battery drain. Probably partly due to always using 3G, also the LG Onscreen Keyboard (VNC Type app) is using a LOT more power in this rom - Previous roms battery stats used to put it near the bottom of the list - but on this Rom its usually a rock solid 3rd of 4th placer at 20-odd percentish!

I can also add this - Touch wood (knock on wood for you americans around here :P) - I didnt have any GPS problems with 20L :D (for what its worth!!)

MrOtacon my o2x suffers from exactly the same issues as yours. The dreadful white 3G icon (meaning no data/cell connection), those reboots that devour battery, u name it. I also tried separate v20l/BB/ril as well as kdz, both stock and Paul rooted/deodexed. I sometimes get away w it by airplane mode of/off or switching off/radio from phone settings (dial code), but reboots are needed at times which can cause steep battery drops. Also need to mention that i was also getting this w Gr4 and v20e stock (stock & HP2X kernel). On the 1st post of this http://forum.xda-developers.com/showthread.php?t=1154127 there's a zip file with a list of all the known bugs of the o2x, it is believed that we suffer (partially at least) from the No.6 bug on the list, cannot confirm it though. I think ive given 'WCDMA only' a try, gonna try it again. There are a few o2x users that have the same issues in Spain, no solution in those forums either. As i mentioned b4, i was in Greece briefly while on v10d and cant remember having data/cell problems as such. There's got to be a workaround but my lack of dev knowledge limits my options, Ive tried what i could. Rasta666 seems to have had this bug and resolved it by baking a specific combi of modules of Gr4 as well as a few other mods, kernel etc. You can read a few posts (if u havent already) about this between me and others on the 'Gr4' and 'v20l deodexed-rooted' threads. If no other solution is found im considering a subscription here, just for trying out Rasta's bake. I'll try whatever i might think of, if u (or anybody else) have any news on this, let us know.

[Guest Ximo F. Verde]

..And minor issues I can live with, but these are major problems.

+100

[Guest MrOtacon]

I've actually tried another persons build. Hell_97 from XDA

It seems very stable so far - in regards to network recovery when switching. Have tried numerous times from phone info and from resuming from sleep.

Can't comment on battery yet.

First Link

Im still waiting on GR5, because if it turns out as good as FR19 - then no one will beat them!!

This is just to tied me over :D

Using it with the October Baseband (also in same post)

Edited November 8, 2011 by MrOtacon

[Guest vrowdy]

I've actually tried another persons build. Hell_97 from XDA

It seems very stable so far - in regards to network recovery when switching. Have tried numerous times from phone info and from resuming from sleep.

Can't comment on battery yet.

First Link

Im still waiting on GR5, because if it turns out as good as FR19 - then no one will beat them!!

This is just to tied me over :D

Using it with the October Baseband (also in same post)

Which exact baseband version is that? It appears it can be found through the hidden menu.

[Guest Ximo F. Verde]

I've actually tried another persons build. Hell_97 from XDA

It seems very stable so far - in regards to network recovery when switching. Have tried numerous times from phone info and from resuming from sleep.

Can't comment on battery yet.

First Link

Im still waiting on GR5, because if it turns out as good as FR19 - then no one will beat them!!

This is just to tied me over :D

Using it with the October Baseband (also in same post)

Thats great news MrOtacon, ill probably flash it later on today, keep us updated for any unfortunate incident (related to what we were talking about) - hopefully everything will turn out ok.

[Guest MrOtacon]

Thats great news MrOtacon, ill probably flash it later on today, keep us updated for any unfortunate incident (related to what we were talking about) - hopefully everything will turn out ok.

I will do :D

At the moment, i havent encountered the network issue. Its been stable, and fast.

Cant comment on the battery for another day or so until its been calibrated - but I was on time for work this morning :D

Baseband Version on phone information (version info on hiddenmenu): 1035.21_20110725

AP Version: lgp990-v20l.422c563e

14 Hours so far and am currently at 30% battery, with some youtube playing use, texts and calls, plus a bit of a stint on tweetdeck. etc etc

Battery is not great - but its not a complete calibration cycle yet - so not worried about that for now

I will say this though - there were a few issues with the Build.prop file used in this rom.

Forinstance user.feature.lgdrm and user.feature.lgresource were set to true and then set to false again near the end of the file - which caused the true entry to be disregarded, and stopped customization for ringtones, alarms etc. A quick edit of Build.prop and a reboot fixed this!

Also - wifi.supplicant_scan_interval=180, 180seconds is a crazy amount of time - so i removed the whole line.

Edited November 8, 2011 by MrOtacon

[Guest Ximo F. Verde]

I will do :D

At the moment, i havent encountered the network issue. Its been stable, and fast.

Cant comment on the battery for another day or so until its been calibrated - but I was on time for work this morning :D

Baseband Version on phone information (version info on hiddenmenu): 1035.21_20110725

AP Version: lgp990-v20l.422c563e

14 Hours so far and am currently at 30% battery, with some youtube playing use, texts and calls, plus a bit of a stint on tweetdeck. etc etc

Battery is not great - but its not a complete calibration cycle yet - so not worried about that for now

I will say this though - there were a few issues with the Build.prop file used in this rom.

Forinstance user.feature.lgdrm and user.feature.lgresource were set to true and then set to false again near the end of the file - which caused the true entry to be disregarded, and stopped customization for ringtones, alarms etc. A quick edit of Build.prop and a reboot fixed this!

Also - wifi.supplicant_scan_interval=180, 180seconds is a crazy amount of time - so i removed the whole line.

Great news MrOtacon, getting ready to flash. Ill let u know of any progress.

Laters

[Guest vrowdy]

I will say this though - there were a few issues with the Build.prop file used in this rom.

Forinstance user.feature.lgdrm and user.feature.lgresource were set to true and then set to false again near the end of the file - which caused the true entry to be disregarded, and stopped customization for ringtones, alarms etc. A quick edit of Build.prop and a reboot fixed this!

Also - wifi.supplicant_scan_interval=180, 180seconds is a crazy amount of time - so i removed the whole line.

How can one edit that file?

After flashing on the phone itself? Or via the pc and a special program?

Also, did you report these issues on the orignal thread on xda? Then the creator can fix it.

[Guest MrOtacon]

How can one edit that file?

After flashing on the phone itself? Or via the pc and a special program?

Also, did you report these issues on the orignal thread on xda? Then the creator can fix it.

I did go to report them, but a member named: Craxx already seems to have discovered the problem himself, and has talked about these. He also noticed something I missed, ro.media.dec.jpeg.memcap is set at 20000000 ( ro.media.dec.jpeg.memcap=20000000 ) as well as 8000000 ( ro.media.dec.jpeg.memcap=80000000 ). The first entry ( ro.media.dec.jpeg.memcap=20000000 ) needs removing too!

To edit the build.prop file I used es file explorer from market. Go into settings, and mark the box next to root explorer, then the box next to mount as read / write (directly underneath it). now navigate to /system/ and click on Build.prop. open it in Es File Explorers text editor, and edit away. Have a quick scan for any duplicate lines both myself, and Craxx have missed. save the file once finished. I then recommend that you untick the box next to mount read and write until you need this again.

Restart the phone and it will use your new Build.prop

Edited November 8, 2011 by MrOtacon

[Guest vrowdy]

I did go to report them, but a member named: Craxx already seems to have discovered the problem himself, and has talked about these. He also noticed something I missed, ro.media.dec.jpeg.memcap is set at 20000000 ( ro.media.dec.jpeg.memcap=20000000 ) as well as 8000000 ( ro.media.dec.jpeg.memcap=80000000 ). The first entry ( ro.media.dec.jpeg.memcap=20000000 ) needs removing too!

To edit the build.prop file I used es file explorer from market. Go into settings, and mark the box next to root explorer, then the box next to mount as read / write (directly underneath it). now navigate to /system/ and click on Build.prop. open it in Es File Explorers text editor, and edit away. Have a quick scan for any duplicate lines both myself, and Craxx have missed. save the file once finished. I then recommend that you untick the box next to mount read and write until you need this again.

Restart the phone and it will use your new Build.prop

Thanks a lot! I also read 4.2 is going to be released soon, which includes the new HP kernel from Spica.