Stock ROM V20I rooted, cleaned up and updated (fast dormancy fixed)

[yuripg1]

I noticed that, on this ROM on News & Weather app, if you uncheck the auto-refresh option it will be checked again on the next boot.

So, I would recommend that you guys set the refresh interval to "1 day". The gain in battery life may be negligible, but I think it's worth the change so you don't have to bother unchecking the auto-refresh option on every boot.

Sent from my LG-P500 using XDA

 

[Ipse_Tase]

I noticed that, on this ROM on News & Weather app, if you uncheck the auto-refresh option it will be checked again on the next boot.

Funny you should mention that...I was just looking at Betterbatterystats numbers and despite me freezing Google Maps and Email, I still get wakelocks...(160 in 24hrs for Maps)...WTF?
Not complaining about battery life, just trying to understand.

BTW...any suggestions re my problem of not getting sd-ext card backups with Clockworkmod? Is it a kernel thing? (I checked my old backups from franco#4 and they don't have my ext2 partition either).

 

[yuripg1]

BTW...any suggestions re my problem of not getting sd-ext card backups with Clockworkmod? Is it a kernel thing? (I checked my old backups from franco#4 and they don't have my ext2 partition either).

Four things occurred to me:

1. I haven't gone too deep on this but as far as I know the recovery has its own kernel (I don't know if it's a complete one or has only the necessary parts for the recovery).
2. CyanogenMod has a different kernel (msm7x27) that, if I'm not mistaken, in the very few first nightlies didn't support ext partitions (they forgot to enable it)
3. The recovery 5.0.2.0 is from the pre-CM era, when all the kernels were based on the stock one from LG (so I suppose recovery's kernel should be similar to those ones)
4. But the recovery 5.0.2.7 was released in January 12, just when we started to have official CM nightlies (so I highly suspect it has the - at the time - brand new kernel of CyanogenMod for P500)

Connecting the dots, I believe ClockworkMod Recovery v5.0.2.7 has problems with ext partitions because it uses the faulty CM kernel we had those days.

P.S.: At that time (January), I used v5.0.2.7 only for a short while, installing back the v.5.0.2.0 and keeping it since then. I simply suppose this is what could be causing the mentioned problem for some people (although I haven't seen anybody clearly state that v.5.0.2.7 doesn't work with ext partitions).

Try using ClockworkMod Recovery v5.0.2.0.

 

[Ipse_Tase]

Try using ClockworkMod Recovery v5.0.2.0.

Thanks, I'm on the same page based on what I read so far.
Now, from ROM Manager I CANNOT flash 5.0.2.0 (I always get an error).
I have a 5.0.2.0.zip posted here in the forums...kinda reluctant to try that and see what gives (bad recovery = better than NO recovery )
Do you have any suggestions? No clue why I fail to flash the older cwm from Rom Mgr.
Can I flash the zip from recovery? (ClockworkMod_5.0.2.0_Recovery_ThunderG_Official.zip Size 4.46 MiB)

/EDIT NVM...found that selecting "old_BB " in ROM Mgr actually flashed 5.0.2.0...now I can't execute cmds...looks like different keys are used...I'm giving up

 

[yuripg1]

Thanks, I'm on the same page based on what I read so far.
Now, from ROM Manager I CANNOT flash 5.0.2.0 (I always get an error).
I have a 5.0.2.0.zip posted here in the forums...kinda reluctant to try that and see what gives (bad recovery = better than NO recovery )
Do you have any suggestions? No clue why I fail to flash the older cwm from Rom Mgr.

Hmmm, it's been a long time since I used ROM Manager to flash Recovery.

I usually put my phone in emergency mode and flash using LGMDP. It takes less than 5 seconds to write the recovery (there's no NV backup and restoration because it's on emergency mode).

Last time I downloaded that Zip but only used its partition table alongside the recovery's .img from ClockworkMod site (the 'oldBB'). Of course I renamed it to 'recovety.img' when putting on the same folder of the partition table.

Sent from my LG-P500 using XDA

 

[Ipse_Tase]

working 5.0.2.0

Guess what: after d!cking around with 5.0.2.0 (and realizing the key have been remapped in 5.0.2.7) I managed to get a full backup (sd-ext included).

I wish someone would have clarified in ROM Mgr that old_BB actually means 5.0.2.0.

BTW: there is a new kernel from Roqu3 (X) which changes the touch screen driver to make it even less CPU intensive while staying responsive.
His kernels are my favorites.

 

[yuripg1]

Guess what: after d!cking around with 5.0.2.0 (and realizing the key have been remapped in 5.0.2.7) I managed to get a full backup (sd-ext included).

I wish someone would have clarified in ROM Mgr that old_BB actually means 5.0.2.0.

BTW: there is a new kernel from Roqu3 (X) which changes the touch screen driver to make it even less CPU intensive while staying responsive.
His kernels are my favorites.

Sorry about the recovery. It's because I had in my mind the ClockworkMod site, that mentions the version.

Sent from my LG-P500 using XDA

 

[klaudyuxxx]

The mobile tv and other links can be easily removed with titanium backup. There's an app which i don't recall exactly its name, but i do know it included "link".

 

[Ipse_Tase]

I had this post in the "Resurrection ROM" thread...it probably should have been here:

Yuripg1...I'm still using your V20i with NO fd wakeups. I did delete ALL the APNs and created my own.
So you might wanna try wiping out those db's instead of copying over. In the end, how many APNs you need? Maybe I'm lucky with just one.
My battery drain is below 0.5%/hr when the phone is not used.


...and I should add that I have only Alarm manager using some CPU. Cannot investigate any further since AM it's a generic way to wake up the CPU by any app...and I don't know how to walk an app thread to see who's calling AM.

 

[yuripg1]

I had this post in the "Resurrection ROM" thread...it probably should have been here:

Yuripg1...I'm still using your V20i with NO fd wakeups. I did delete ALL the APNs and created my own.
So you might wanna try wiping out those db's instead of copying over. In the end, how many APNs you need? Maybe I'm lucky with just one.
My battery drain is below 0.5%/hr when the phone is not used.


...and I should add that I have only Alarm manager using some CPU. Cannot investigate any further since AM it's a generic way to wake up the CPU by any app...and I don't know how to walk an app thread to see who's calling AM.

Once you have the /data set up the first time, deleting the flex.db seems do solve it (and, if I'm not mistaken - it's been a long time - Android starts to read APNs from the apns-conf.xml, so you can replace the file with another from any other ROM). But if you have a clean /data, on the first boot a lot of apps dependent on this file will keep force closing. So, do NOT wipe your data without that file.

1. That's why I didn't release another backup with diferent files. It would fail at the first boot with clean /data.
2. I'm really ashamed that I didn't tell you guys this at that time (probably because I was too frustrated with the item 1). Sorry guys!

By the way, I kept researching a lot on that until two weeks ago, and all this knowledge I passed to dhruv.always when he asked me by PM. I hope he can finally make a APN-generic ROM working from a clean boot.

 

[Ipse_Tase]

[*]I'm really ashamed that I didn't tell you guys this at that time (probably because I was too frustrated with the item 1). Sorry guys!

Either I was lucky or I read somewhere that I should NOT wipe out the dbs completely, because I never ran into problems. I DO believe I set my APN BEFORE making db changes.
At any rate, I'm happy with your modded ROM...and thankful

 

[yuripg1]

Uploaded another backup with up-to-date apps. As of today, there is no app left to update after the installation.

Enjoy!

 

[yuripg1]

One more (and probably the last) thing: I managed to remove the two remaining T-Mobile UK apps that seemed to be links.

Those apps were part of Embedded Link (TmoUrl.apk). Uninstalling it removed Mobile Jukebox and Mobile TV & Video.

And in case it's of anyone's interest, I updated the backup image with this and a few more minor adjustments described in the first post (always sticking to the stock experience, so you can put the kernel, tweaks and scripts that you want).

 

[toxicro]

RingNoFade

Im back

Yuri try this patch and tell me if ringing is better without annoying fade.

 

[yuripg1]

Im back

Yuri try this patch and tell me if ringing is better without annoying fade:

http://forum.xda-developers.com/showpost.php?p=25022994&postcount=115

Thanks!

But I couldn't get the file. It actually seems do download OK, but the file has only 554 bytes.

 

[toxicro]

Thanks!

But I couldn't get the file. It actually seems do download OK, but the file has only 554 bytes.

ups, try now sry

 

[deviler]

Awesome, this is what i'm looking for
Thanks bro

 

[yuripg1]

Added the RingNoFade patch to the first post.

Still wanted to keep the default Phone.apk in the ROM, giving the option to apply the patch.

Also, reorganized the first post to provide better informations about the ROM.

 

[vlt96]

Hey, for changing the stock (android logo) bootanimation go to framework-res.apk, open it with winrar and in /assets/images, replace the images with the attached...
And check if there is any in /system/media (bootanimation.zip, delete it if it is

Oh and keep the name of the 2 images

 

[yuripg1]

Hey, for changing the stock (android logo) bootanimation go to framework-res.apk, open it with winrar and in /assets/images, replace the images with the attached...
And check if there is any in /system/media (bootanimation.zip, delete it if it is

Oh and keep the name of the 2 images

Thanks, but that's not the animation that was replaced.

T-Mobile UK animation shows up (with sound) after the white LG logo and before this "Android" animation.

There is also a similar animation (with no sound) when you power off the phone.