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

[zefie]

The problem, scifan, is that Froyo is not cupcake. With cupcake it was fairly easy, however alot of the drivers are half kernel half android framework, therefore without tweaking the framework code, nothing initializes.

 

[scifan]

The problem, scifan, is that Froyo is not cupcake. With cupcake it was fairly easy, however alot of the drivers are half kernel half android framework, therefore without tweaking the framework code, nothing initializes.

Hmm... lost my comments...

I guess I"m unsure how I can help...

Looking at the HTC init files, I decided to look through a working rom to see what files might be different between the AOSP I compiled and ThundeRom...

The one's that jumped out that might include drivers or firmware include:

/system/etc/firmware/yamato_pfp.fw
/system/etc/firmware/yamato_pm4.fw
/system/etc/wl/rtecdc.bin
/system/etc/wl/rtecdc-apsta.bin
/system/etc/wl/rtecdc-mfgtest.bin
/system/etc/MELFAS_FIRM.bin
/system/etc/MELFAS_FIRM_RA10.bin

What do the xml files in the /system/etc/permissions folder do for you?

There are a fairly large number of "lib*.so" files under /system/lib that are missing from the aosp rom...

I think the egl folder includes the graphics accelerator files I saw a config file that seemed to reference the adreno200 as well as a stock video driver...

I see a bluez-plugin folder which I believe relates to bluetooth functions..

haven't got a clue what /system/lib/hw does for you... however I see several files that aren't in the AOSP build...

kernel modules need to go into /system/lib/modules...

In these different files, I have the files that were missing from the AOSP rom...

(No, I didn't copy /system/framework as it's obviously going to be significantly different...)

 

[cordell]

I have swapped all sorts of configurations with the build we have and countless other roms. Right now we have SD Card mounted and sound working. But the launcher suffered and its choppy in the build now. mrinehart93 siad he can take care of the choppiness, I dont doubt him, but still so much more to figure out! Tomorrow I will play with the DeOdex Optimus V template I made Maybe we can get a few other things poppin off here

HERE is AOSP with SD Card mounted and Sound working Add/Edit from this as I have NO idea how the 2 things started working LMAO

 

[cordell]

I have put together a rom from the virgin mobile dump. I am gonna work on stripping it down and make it as bare as possible. This may be the closest to aosp we get. It offers NO ID at boot, is doesnt have near as much stock bloat! I will upload a better version tomorrow, no lag with rom either

edit.....

everything is WORKING!!! I have it OC at 806 stable with Xionia Kernel

quadrant is 609 without stagefright, not bad...

 

[hamagc]

Nice. Can't wait to try it out!

Sent from my LS670 using Tapatalk

 

[RevolutionRed]

everything is WORKING!!! I have it OC at 806 stable with Xionia Kernel

I'd definitely like to try it on my V as well. Right now I'm mixing the VM rom and xionac kernel with a thunderom build.prop. stable at 806, ~1050 in quadrant.

 

[cordell]

I got a error to fix before I upload. Its driving my nuts! lol

"message expired or not available"

Getting that when trying to send a MMS. SMS works just fine though.

EDIT......
Looks like swapping to the sprint mms.apk fixed it!

I dont know if its just me but the screen appears much clearer with this rom

 

[olmos.lalo]

Post the rom cordell! Lol

 

[cordell]

Here is the WIP (work in progress) HERE The rom is not overclocked, Xionia Kernel will work for overclocking. mrinehart93 will be able to add his kernel to the rom later. Also Virgin Mobile users may have trouble with MMS as I had to put sprint MMS.apk in for it to work. Boot animation needs changing as I just noticed the image is a bit to large There are some other little kinks but for the most part it runs pretty good. JIT is on, stagefright is on, I think HW acceleration is on, also tweeked WFI to search at 60 sec rather than 20. Memory tweeks as well. I am pretty sure Build Props that are floating around can be used to turn off what ever you want... ENJOY


depending on what happens when I get with mrinehart93, this rom may be 86'd for a slimmer AOSP rom


to change governor to "interactive", less reboots. enter this in adb shell

echo interactive > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

 

[KSmithInNY]

The virgin mobile ROM is no more AOSP than Sprints. To be honest, both are very VERY close to being AOSP as is. The only things Sprint included which virgin didnt is the whole sprint id thing but on th flip side of the coin, virgin included bloatware sprint didnt like virgin chat and where.

Let me make a suggestion....
1) Start with a deodexed system dump from the Lg Optimus S
2) Remove the launcher2.apk from system/app. Replace it with a froyo launcher2.apk thats had MDPI stripped. This gets rid of id from the launcher.
3) Remove the Sprint ID app. it's called w_installer and can be found in system/app
4) Remove SprintZone.apk from system/app
5) Delete LGSetupwizard from system/app
6) Tell the buildprop to use the AOSP setupwizard by enabling it.
7) Delete protips.apk
8) edit the boot.image and remove sprint boot animation
*-* This is done for sizing purposes*-*
9) Delete aging.mp3 from system/sounds/lgdiag and it's a not an AOSP sound

You do this and you basically have an AOSP build of froyo. although i would mention that .... you also have a very close ROM to LEGO which is basically what's described above then rubbed with special sauce.

 

[cordell]

The virgin mobile ROM is no more AOSP than Sprints. To be honest, both are very VERY close to being AOSP as is. The only things Sprint included which virgin didnt is the whole sprint id thing but on th flip side of the coin, virgin included bloatware sprint didnt like virgin chat and where.

Let me make a suggestion....
1) Start with a deodexed system dump from the Lg Optimus S
2) Remove the launcher2.apk from system/app. Replace it with a froyo launcher2.apk thats had MDPI stripped. This gets rid of id from the launcher.
3) Remove the Sprint ID app. it's called w_installer and can be found in system/app
4) Remove SprintZone.apk from system/app
5) Delete LGSetupwizard from system/app
6) Tell the buildprop to use the AOSP setupwizard by enabling it.
7) Delete protips.apk
8) edit the boot.image and remove sprint boot animation
*-* This is done for sizing purposes*-*
9) Delete aging.mp3 from system/sounds/lgdiag and it's a not an AOSP sound

You do this and you basically have an AOSP build of froyo. although i would mention that .... you also have a very close ROM to LEGO which is basically what's described above then rubbed with special sauce.

Thanks for the input! Thats pretty close to what I have done so far. All the playing around I noticed that there is not much difference between the 2 roms (virgin/sprint). The launcher2 I have not messed with, it is stock one in the VM rom, I use LPP anyway. I looked at LEGO thread, awesome job! Very user friendly, everything is laid right out for the end user, good idea doing that too

I was wondering where to edit the sprint boot (thanks for the tip), I changed the sound to say the Motorola "droid" lol. I still have some work, its more of a hobby than anything. I had a htc hero before and there were so many things to do with that phone, I got hooked on flashing stuff! Though the optimus so beats the hero, even with all its mods.

What I am really looking into is the 30mb of system space not being used. I want to find a way to get that over to data, the cache has another 30 or so mb that can be spared as well

 

[KSmithInNY]

Thanks for the input! Thats pretty close to what I have done so far. All the playing around I noticed that there is not much difference between the 2 roms (virgin/sprint). The launcher2 I have not messed with, it is stock one in the VM rom, I use LPP anyway. I looked at LEGO thread, awesome job! Very user friendly, everything is laid right out for the end user, good idea doing that too Thanks for the tip, I was wondering where to edit the sprint boot, I changed the sound to say the Motorola "droid" lol. I still have some work, its more of a hobby than anything. I had a htc hero before and there were so many things to do with that phone, I got hooked on flashing stuff! Though the optimus so beats the hero, even with all its mods.

I'm a hero guy too (then EVO, now optimus) and wow what a world of difference from the Hero this little phone is. The one thing that nobody can take away from the hero though is that the development community was freaking huge!!!!

 

[cordell]

i'm a hero guy too (then evo, now optimus) and wow what a world of difference from the hero this little phone is. The one thing that nobody can take away from the hero though is that the development community was freaking huge!!!!

amen!

 

[rodcpierce]

Hero guy here also. First was the touch pro, then touch pro 2, then hero, and now the optimus. And yes, I do agree. The Hero dev was gigantic!!

 

[scifan]

Hero Dev was Impressive... however, many seem to be jumping ship to either the EVO or to the optimus...

 

[skeletonbones]

Super pumped about the potential here. My buddy has been running Cyanogen on his Evo, and imagining that on my little Optimus is almost too good to be true. Don't get me wrong though, ThundeROM RULES, and I just started playing around with the nROM, and it's pretty cool so far as well. But Cyanogen...

I'll be downloading your guy here post-nROM meddling. Wish I was better with computers and coding so I could help you out. Good luck friend, will keep following .

 

[gmap516]

What ever happened to this thread? Has anyone made any progress?

 

[Sandman#AC]

So is the AOSP rom for the Optimus S a lost cause?

 

[scifan]

So is the AOSP rom for the Optimus S a lost cause?

Not sure...

I've decided I don't know enough to be really helpful for android dev... (well, color me frustrated and backing off until I'm really ready to try building something again).

The guy who was really driving this appears to have been consumed recently by real world stuff...

So, I'm unsure where this leaves us...

 

[cordell]

Nothing is ever dead, there just hasnt been much advancement. Still only have SD card mounting, and sound, on 2.3 gingerbread/cm7 port. Things take time