AOSP Android 2.2 FroYo! 1/22/11 New Build Posted

Good news! I think I ALMOST have AOSP working! I got a TON of drivers to load now (according to dmesg), but the phone keeps bootlooping. I think once I can get it past the bootloop, we should have a fully working AOSP 2.2 :)

Woot

Sent from my LS670 using Tapatalk
 
Good news! I think I ALMOST have AOSP working! I got a TON of drivers to load now (according to dmesg), but the phone keeps bootlooping. I think once I can get it past the bootloop, we should have a fully working AOSP 2.2 :)

Great news!
 
Can you get it to boot without loading the other drivers?

Sent from my LS670 using Tapatalk
 
Can you get it to boot without loading the other drivers?

Sent from my LS670 using Tapatalk

Yes, but Android runs very poorly (laggy as heck) without the drivers, and isn't reall functional. You can download the AOSP ROM I uploaded in the first post if you want to at least try AOSP out.
 
Yes, but Android runs very poorly (laggy as heck) without the drivers, and isn't reall functional. You can download the AOSP ROM I uploaded in the first post if you want to at least try AOSP out.

Give us an update! :D What the deal???
 
If you can get it to boot without the native drivers, you have a place to start from.

How many divers are we taking about? Could try adding a driver at a time to see where it freaks out at. Time intensive, but you can rule things out.

(just trying to give some ideas about how to get past this.)

The reality is that since the phone comes natively with 2.2 on it, switching to asop shouldn't be too painful... The kernel drivers are the most painful part... Getting the boot image happy can be a pita... Having the wrong drivers sucks!

Sent from my LS670 using Tapatalk
 
If you can get it to boot without the native drivers, you have a place to start from.

How many divers are we taking about? Could try adding a driver at a time to see where it freaks out at. Time intensive, but you can rule things out.

(just trying to give some ideas about how to get past this.)

The reality is that since the phone comes natively with 2.2 on it, switching to asop shouldn't be too painful... The kernel drivers are the most painful part... Getting the boot image happy can be a pita... Having the wrong drivers sucks!

Sent from my LS670 using Tapatalk

The drivers that don't work are pretty much everything specific to our board in our phone (MSM-7227). I am in the process of playing around with the libs right now to see what I can take out and what I need to leave for the drivers to load properly.
 
Its one of those "should be easier than it is" situations...

Not sure I know enough to help...

Sent from my LS670 using Tapatalk
 
I'm now going to try to compile AOSP for "user" instead of "engineer" to see if it makes a difference. If this doesn't work, I'm going to stop using LG's instructions and follow some for the Nexus One (making necessary edits along the way). I have no idea why LG made it so difficult to do this... It's still 2.2, so it shouldn't be this difficult.
 
Dumb question: what's between the aosp and the stock rom that came with the optimus? The only thing I could think of is the bloatware.

Good job btw. :)

Sent from my LS670 using Tapatalk
 
Dumb question: what's between the aosp and the stock rom that came with the optimus? The only thing I could think of is the bloatware.

Good job btw. :)

Sent from my LS670 using Tapatalk

AOSP will be significantly faster, we'll have the ability to use more mods, and it's a stepping stone to getting CyanogenMod working on our phone :)
 
AOSP will be significantly faster, we'll have the ability to use more mods, and it's a stepping stone to getting CyanogenMod working on our phone :)

Thanks for the answer, i'll be willing test if you need testers. :)

I miss cm6 :'(

Sent from my LS670 using Tapatalk
 
Have to say... Adb was interesting to get working under ubuntu... ;)

Sent from my LS670 using Tapatalk
 

Trending Posts

Forum statistics

Threads
956,900
Messages
6,970,509
Members
3,163,643
Latest member
stonefruit