• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Virgin Mobile/Sprint] [Dev] Porting Stuff.

phenomx4 said:
Anything I can do to help you guys?
Click to expand...

I would love your help. Any bit I can get would be great. :)

Here's my device tree for the Optimus F3:
https://github.com/xclusive36/android_device_lge_fx3

The current setup (if you compile from git as it stands currently) loads the logo animation then goes black. Looks like it fails to load the external sd. it also runs out of memory.
Here's the logcat for that setup: Here

To get the boot animation, more files from the stock lib folder need to be copied onto the zip. Then I would need to copy the stock bin folder as well.
Here's the logcat for that setup:
http://dl.litestep.com/logcat3.txt

It looks like I missed some of the needed files from the lib folder. I'm currently separating them out. From what I understand, I shouldn't need anything from the bin folder (although I do to get to the boot animation).

The important thing is that it's now loading the correct hardware files now. I also wanted to mention that although we're using loki to bypass the bootloader, I'm using 2nd-init in this rom to do the same thing. I haven't had luck with the ramdisk yet. I was hoping I could get this up and running first and then focus on that and building the kernel with it later. (I'm using stock prebuilt)

I can upload the stock ramdisk if you wanted to look at them. LG threw in allot. ex. init.qcom.rc, init.fx3.rc, init.fx3s.rc, etc..

I pulled the info from the init.fx3.rc to specify the external sd location and threw it into the 2nd-init init.fx3.rc

Thank you for showing interest. It means the world to me. :) I'm sure to the rest of us as well.
 
robaho said:
You should not be copying blobs that are not low level - and usually proprietary - hardware drivers. Things like the dalvik jvm should be built from the source.

You can probably take the code aurora aosp builds for the same chipset and get fairly close.

I would think think the only tough devices are the camera and the NFC chip. All of the other devices are fairly standard.
Click to expand...

It is compiling the dalvik jvm from source. I'm attempting to sort out the need files currently. It's when I over-write them with the stock files I get the rev error. Unfortunately it doesn't boot as far if I don't copy them over.

It's slow going. I make a few changes, copy them over to the phone, wipe and flash. Take note, wipe again, and then restore from backup. Then repeat. My usb is beginning to become worn out.

I get what your saying though. I thought you are supposed to copy over hardware files that are not being compiled from source. Proprietary hardware files that are needed to get things like the camera, nfc chip, and modem working.
 
Alright, i've updated the device tree once more to add the missing lib files. The bin folder is no longer needed. If compiled, it should boot up to the boot animation.

Here's the logcat

There maybe a few files in there I don't need. I noticed allot of the files I needed were files that should of compiled.

Like libstagefrighthw.so, and it's dependencies. Especially the ones in the lib/hw folder like audio_policy.msm8960.so, copybit.msm8960.so, gestures.msm8960.so, etc..

It's compiling default files like audio_policy.default, gralloc.default.so, etc.. I see I need to mess with the BoardConfig.mk file a bit more.

Also, I see that it's calling /system/framework/framework2.jar. There is no framework2.jar in the rom. It is however in the stock rom.
 
this is both off and on subject, but is there an easy way to crack open boot.lok to mess with the ramdisk at all? thanks for any input, im looking but loki stuff is new to me

edit: nevermind, android image kitchen with the loki addon worked, thanks to all anyway
 
xclusive36 said:
Alright, i've updated the device tree once more to add the missing lib files. The bin folder is no longer needed. If compiled, it should boot up to the boot animation.

Here's the logcat

There maybe a few files in there I don't need. I noticed allot of the files I needed were files that should of compiled.

Like libstagefrighthw.so, and it's dependencies. Especially the ones in the lib/hw folder like audio_policy.msm8960.so, copybit.msm8960.so, gestures.msm8960.so, etc..

It's compiling default files like audio_policy.default, gralloc.default.so, etc.. I see I need to mess with the BoardConfig.mk file a bit more.

Also, I see that it's calling /system/framework/framework2.jar. There is no framework2.jar in the rom. It is however in the stock rom.
Click to expand...
I decompiled framework2.jar and from what I've found it handles all things call/sms/mms. My ability to read smali isn't the greatest, lol.
 
gherkaul said:
I decompiled framework2.jar and from what I've found it handles all things call/sms/mms. My ability to read smali isn't the greatest, lol.
Click to expand...

I think thats all inside the framework.jar for cm. framework2.jar shouldn't be needed for cm as far as i know.

Grrr. If i set 'BOARD_USES_QCOM_HARDWARE := true' i keep getting 'was not declared in this scope' errors.
'BOARD_USES_LEGACY_QCOM := true' works but isn't creating the needed lib files stated above.
 
True, it's in the cm framework but any thing in the system that normally would call for the framework2.jar library would now need to be changed to call the framework.jar. Know what I mean?
 
xclusive36 said:
I think thats all inside the framework.jar for cm. framework2.jar shouldn't be needed for cm as far as i know.

Grrr. If i set 'BOARD_USES_QCOM_HARDWARE := true' i keep getting 'was not declared in this scope' errors.
'BOARD_USES_LEGACY_QCOM := true' works but isn't creating the needed lib files stated above.
Click to expand...
You need "BOARD_USES_QCOM_HARDWARE" to be true as it uses a Qualcomm chipset. Post the compilation errors you get with that enabled on pastebin. Also what version of android is the stock rom?
 
phenomx4 said:
You need "BOARD_USES_QCOM_HARDWARE" to be true as it uses a Qualcomm chipset. Post the compilation errors you get with that enabled on pastebin. Also what version of android is the stock rom?
Click to expand...

That's pretty much what i figured. I'll post the compilation error the next time it pops up. The Cyanogen git doesn't include the hardware/qcom/msm8960 contents for cm-10.1. I was using aosp. I'm thinking thats where my problem is. I just changed it to cm-10.2 msm8960.

The stock version is 4.1.2.
 
gherkaul said:
LMAO, yea something like that link. Can you give me a link to the cm framework apk and jar you have. I'd like to take a look at them if you don't mind. I'm not much help with building a rom from source but modifing the framework is more up my alley. I want to see what differences there might be with cm verses stock.
Click to expand...

I sent you a pm
 
I'm going to switch gears and jump back to cm-10 after testing the Optimus f7 rom. I've pulled the device tree off of that and am going to use that as a base to port. Thanks cesarasm for posting that to the forum.

I'm going to use this as a learning experience.
 
Ok, I've switched back to the cm-10.1 build. With that said, I've made progress on the error I was getting with the 'BOARD_USES_QCOM_HARDWARE := true' switch. I now have the requirements to use that switch. I only needed a modifed hardware/qcom/audio-caf from https://github.com/hroark13/hardware_qcom_audio-caf.

I'm currently compiling cm-10.1 for the lg motion as i'm using that to test for compile errors. When it completes with no errors i'll jump back to ours using it as a template to get past the errors i was getting.
 
xclusive36 said:
phenomx4, here's the latest logcat. This is for CM 10, and not CM 10.1. It's almost booting but stuck on the boot animation. Any thought on what the issue is?

http://dl.litestep.com/logcat13.txt

It's having issues with the camera
Click to expand...

A few issues I found Via this logcat for CM10:

1. No input was found - Touch screen issue?
2. No sound devices - Speakers or Handset?

These specific issues repeat through out the logcat output.

The touch screen seems like that might be an issue for booting but I am not sure.
 
sandix said:
A few issues I found Via this logcat for CM10:

1. No input was found - Touch screen issue?
2. No sound devices - Speakers or Handset?

These specific issues repeat through out the logcat output.

The touch screen seems like that might be an issue for booting but I am not sure.
Click to expand...

I did not notice that. I would not know how to fix those errors. Im focused on cn10.1 now. Would you know how to fix those issues?
 
xclusive36 said:
I did not notice that. I would not know how to fix those errors. Im focused on cn10.1 now. Would you know how to fix those issues?
Click to expand...

No I do not, but I do have a flashable CM10.1 for LG FX3 that I am uploading right now. Again I cannot test it as I am at work, but maybe you can test and see? Also, I had to heavily edit the updater-script file so I am not sure if it will actually flash, I'll PM you the link in a minute.
 
Im trying a few different kernels (V5/6/7) and still cannot get CM10 booted....

The reason I am trying different kernels is because I believe at this point it might be a kernel issue.
 
You must log in or register to reply here.
Back
Top Bottom