ARCHIVED: [rom] 2.2.2 weekend project 7/2/2011

[bornagainpenguin]

I didn't put this on the delete list. One thing is I gotta redo the entire rom to fix the browser issues yep.

Awesome news!

I guess I haven't encountered any of the browser issues since I tend to use Opera Mobile on my phone. So far so good, everything I've tried has worked for me. I wonder if it helps that my phone was originally Android 2.2.2?

--bornagainpenguin

 

[bigsupersquid]

the only difference there would be for reception is if the ril libraries from the 2.2.1 roms don't get along well with the newer pv5 radio image built into the 2.2.2 phones.

 

[bornagainpenguin]

the only difference there would be for reception is if the ril libraries from the 2.2.1 roms don't get along well with the newer pv5 radio image built into the 2.2.2 phones.

Makes sense to me, how can I test it so we can know for sure?

--bornagainpenguin

 

[bigsupersquid]

maybe copy all the ril files from the 2.2.2 rom to the 2.2.1 and see if it improves.
there's a list in the iho device_lge_thunderc device makefile.

 

[asadullah]

What I'm doing right now is rebuilding this but with the 2.2.1 base rom with the boot.img bigsupersquid had in the basic stock rom so that all can use but without some errors and wifi tethering working. As everything is working good I'll add different things and hopefully completely finish this rom soon. Something should be out tonight.


EDIT Just reread what you guys were talking about originally this rom was based off 2.2.2 so issues weren't from the ril files it was an issue with not using the correct mem settings in apk manager. and doing things I shouldn't in browser.apk

 

[bornagainpenguin]

What I'm doing right now is rebuilding this but with the 2.2.1 base rom with the boot.img bigsupersquid had in the basic stock rom so that all can use but without some errors and wifi tethering working. As everything is working good I'll add different things and hopefully completely finish this rom soon. Something should be out tonight.

That's good news indeed, since I've just started running into issues. After using my phone all day to download my purchased apps and podcasts via listen suddenly Opera gave me a network error. Then after I went into airplane mode and back, I installed youtube and have been completely unable to get it to work. So hopefully fixing whatever the browser issue was will fix that too.

EDIT Just reread what you guys were talking about originally this rom was based off 2.2.2 so issues weren't from the ril files it was an issue with not using the correct mem settings in apk manager. and doing things I shouldn't in browser.apk

No, no, no...those issues I and bigsupersquid were talking about were the reasons why I wanted to stick with a 2.2.2 rom if at all possible. In other roms I keep on having less signal than I did on my old 2.2.1 phone. I can only assume that Virgin Mobile's version of 2.2.2 changed the radio firmware as well as the OS software, making things not work as well when I try to run Froyo roms (most of which are 2.2.1).

--bornagainpenguin

 

[bigsupersquid]

That's good news indeed, since I've just started running into issues. After using my phone all day to download my purchased apps and podcasts via listen suddenly Opera gave me a network error. Then after I went into airplane mode and back, I installed youtube and have been completely unable to get it to work. So hopefully fixing whatever the browser issue was will fix that too.



No, no, no...those issues I and bigsupersquid were talking about were the reasons why I wanted to stick with a 2.2.2 rom if at all possible. In other roms I keep on having less signal than I did on my old 2.2.1 phone. I can only assume that Virgin Mobile's version of 2.2.2 changed the radio firmware as well as the OS software, making things not work as well when I try to run Froyo roms (most of which are 2.2.1).

--bornagainpenguin

i don't think the firmware comes attached to any rom except in the cab files from lg.
the ril libraries for 2.2.2 may be different to match the pv5 radio though. the 2.2.1 v's had pv4 firmware I'm pretty sure.

 

[asadullah]

Here's what I've got done so far if your running 2.2.2 give it a go to make sure it works

forgot the link don't expect much version here

 

[bornagainpenguin]

Thanks for the weekday update!

Okay, here's what I've done so far, I will keep you appraised as I go along:

1) booted into recovery (Xionia CWMA v1.2518.6) and wiped out the current installation with the Bumblebee Wiper (update_wiper_1.3).

2) copied back my original 2.2.2 stock backed up from nandroid.

3) Tried to flash the weekday update. Got the signature error! Toggled the signature verification option and tried again, this time success!

4) rebooted the phone, watched stock Virgin Mobile animation come up and then from there the Android flashing text boot animation. Boot animation goes for a bit, then stutters as the screen goes black and a single cursor line appears at the top of the screen. Boot animation of Android text resumes and continues for about ten seconds before stuttering again. Is this the famous boot loop?

5) Open back cover, remove battery. Do three key combo to return to recovery...

a) Try boot loop fix in recovery. Watch Virgin Mobile animation and Android animation compete with each other for screen time, Android text overlaying red background, screen stutters black and resumes with only Android flashing text and the symptoms described above.

b) Try flashing the anykernel (pica07remix.zip) and has same effect as a) nearly identical!

6) Return to recovery and restore nandroid of other rom was testing before bed.

Its a no go, can't even seem to get into the system! Is there a md5 I can use to make sure I got a good download, or something obvious I did wrong from my descriptions?

--bornagainpenguin

 

[bigsupersquid]

i'd say try wiping, skip the restore, and flash the new version clean.

 

[bornagainpenguin]

Hmmm... Okay that worked. Wonder why there was even an issue?

Now to look around and see what's different...

--bornagainpenguin

UPDATED: Hmmm...funny looks more like a stock 2.2.1 than it does 2.2.2 and that's what it is reporting itself as. Difference seems to be in the kernel and in the phone connectivity to the towers. My phone looks to be averaging all but one bar right now, a very strong signal!

I'm going to let the default gapps and etc update themselves and test them before rolling back my stock nandroid to see what the reported kernel version is.

Market just complained about Streetview having a bad signature, it wants me to uninstall the current version before it will allow me to update it. Going to dig out my copy of rootexplorer and try uninstalling...

Uhoh! Superuser is complaining about legacy su and refusing to update...is this rom rooted?

Personal note weekday rom kernel is: 2.6.32.9 lge@android-build #4

Hmm...kernel was the same in the stock 2.2.2 as the one used here.

 

[asadullah]

Not much just making sure that it works i was having some problems with my laptop wasn't sure that everything was being built correctly

 

[bornagainpenguin]

Well like I said above, there seem to be some issues with SU and Superuser not wanting to update and making me question whether or not the rom was rooted. And the Streetview app complained about signatures not being correct, suggesting that I try uninstalling the one included with the rom before trying to update. Of course since I am having root issues...

--bornagainpenguin

PS: I won't be able to do much more testing today, I have to be ready to head out the door soon and want my phone to be in sorta ready to go status.

 

[bigsupersquid]

the kernel build info in about phone didn't change between the 2.2.1 and 2.2.2 releases, even though they are definitely different.
I checked when I got a new OV with the hitachi screen.
probably a md5sum would show a difference.