OK I used dsixda kitchen to port mrinehart93 rom to community rom, those are the logcats I posted above.
I then used dsixda kitchen to port community rom to mrineharts rom, this booted and EVERYTHING works! The kernel is mrinehart93's, 2.6.32.9 mike@mike-desktop #2. There is still a WiFi error, but sms and phone works, 3G works, it did port over some sprint crap but that can be taken out. I am uploading rom now, please tell me that it is AOSP with some sprint crap that we can remove! If nothing less maybe the libs from this can be what is needed for mrinehart93 aosp rom he posted!!!
Camera FC's and Gallery doesnt seem to load pics, but SD card appears to be mounted...
ROOT is working!
./arch/arm/mach-msm/dma_test.ko
./arch/arm/mach-msm/reset_modem.ko
./drivers/misc/pmem_kernel_test.ko
./drivers/net/wireless/bcm4325/wireless.ko
./drivers/net/wireless/libra/librasdioif.ko
./drivers/net/tun.ko
OK I used dsixda kitchen to port mrinehart93 rom to community rom, those are the logcats I posted above.
I then used dsixda kitchen to port community rom to mrineharts rom, this booted and EVERYTHING works! The kernel is mrinehart93's, 2.6.32.9 mike@mike-desktop #2. There is still a WiFi error, but sms and phone works, 3G works, it did port over some sprint crap but that can be taken out. I am uploading rom now, please tell me that it is AOSP with some sprint crap that we can remove! If nothing less maybe the libs from this can be what is needed for mrinehart93 aosp rom he posted!!!
Camera FC's and Gallery doesnt seem to load pics, but SD card appears to be mounted...
ROOT is working! Titanium BackUp is working! Starting to wonder if this didnt work like I think/hope it worked, the porting/merging of aosp and community rom...
So...
When I look at the kernel configuration... Most of the drivers are built in, but there are a few that are modules...
I've normally just seen tun.ko and wireless.ko in the /system/lib/modules folder on the boot image... however, when I search for ".ko" files in my compiled kernel directory, I see a few more than are referenced... I'm unsure if these are important or not...
Code:./arch/arm/mach-msm/dma_test.ko ./arch/arm/mach-msm/reset_modem.ko ./drivers/misc/pmem_kernel_test.ko ./drivers/net/wireless/bcm4325/wireless.ko ./drivers/net/wireless/libra/librasdioif.ko ./drivers/net/tun.ko
Go look in the /system/framework folder. If there is no lge-res.apk, then you've done itAlso, in the Google search widget, if there is a magnifying glass, then it's AOSP that is running. If it is a Google icon, then it is the community ROM. Could you post a link to download it?
Here are a couple logcats, take a look and if either one of them has potential I will upload the rom... I think they look promising as the unable to get control ERROR is gone![]()
From the first logcat, it looks like you got the phone to recognize that it's on a CDMA network! Good job
Ported2.zip is definitely not AOSP. It has .odex files, which aren't present in AOSP builds. I'll test Ported.zip right (it is AOSP).
OK, since Ported3.zip has the mounted SD and working sound I am trying to merge a few things from Ported.zip. Ported.zip recognizes phone as CDMA, what I need to know is once I add/swap libs, and or bins, do I need to recompile boot image? I add a few thing and reflash but dont see much change in my logcats, unless I swap a file. If I add what looks to be a missing file it is as if android skips it, almost as if the file wasnt there.
Thanks
OH, one other thing. Boost Mobile/Virgin is releasing a Optimus V, will this basically be a unbranded version, aosp? If so this may be all we need to make this happen!
The Optimus V will have the Virgin Mobile "special sauce" in it that will let the user monitor minutes.
It will also ahve the custom LG stuff, such as the LGE-res.apk that makes theming a PITA.
What about when I add libs/bins to the Ported3.zip rom, should I make a new boot image and updater script?