LG Viper roms?

[brandonabandon]

Re: lg viper roms?

oops. found this in cm-10.1 and aokp 4.2.2 frameworks av media libstagefright --->

ifeq ($(BOARD_USES_PROPRIETARY_OMX),SAMSUNG)
LOCAL_CFLAGS += -DSAMSUNG_OMX
endif

on it.

 

[thenameisnigel]

Re: lg viper roms?

oops. found this in cm-10.1 and aokp 4.2.2 frameworks av media libstagefright --->

ifeq ($(BOARD_USES_PROPRIETARY_OMX),SAMSUNG)
LOCAL_CFLAGS += -DSAMSUNG_OMX
endif

on it.

If that's from my GitHub or ProjectOpenCannibal's can you submit a pull request with it removed? I know I still have a lot of stuff I borrowed from Samsung in there.

Edit:
NIGEL's BACK lol.

 

[brandonabandon]

Re: lg viper roms?

long time no see. i just synced cm10.1 source for 214523rd time lol. i hope uncommenting the samsung omx flag resolves the omx errors i posted. im compiling a "frankenrom" i know aosp 4.2 will compile, but not flash, so ive included the aosp files aokp wouldnt compile into a aokp build, which compile compatibly so far. i have also included p.o.c. recovery. if the build is successful, the aokp kernel could possibly function the aosp rom as well. btw ^=libstagefright/omx/android.mk (cm10.1)

 

[brandonabandon]

Re: lg viper roms?

status: the aosp/aokp merged built compiled but would'nt build the .zip. replacing cm/build for aokp/build and modding it (adding cm10.1 kernel/device also) compiled the rom successfully. it wont boot, hangs at logo unlike the aosp rom which fades to nothing immediatley after logo. cm10.1 now. any suggestions?

 

[thenameisnigel]

Re: lg viper roms?

status: the aosp/aokp merged built compiled but would'nt build the .zip. replacing cm/build for aokp/build and modding it (adding cm10.1 kernel/device also) compiled the rom successfully. it wont boot, hangs at logo unlike the aosp rom which fades to nothing immediatley after logo. cm10.1 now. any suggestions?

I'm putting together a ROM distro OpenROM which will be as close to AOSP as human-ly possible, so try that.

I'll give you a step by step so we can make sure it's not a simple mistake causing it.

• First make the working directory by doing: mkdir -p ~/orv1
• cd ~/orv1
• repo init -u https://github.com/nenterprises/android.git -b orv1
• repo sync -j4
• Let that finish out
• . build/envsetup.sh
• lunch cm_ls840-userdebug (assuming you already have the dependencies)
• make -j4 otapackage

That SHOULD get you a working build. If not, try building for another device and tell me how it works, so do:

• . build/envsetup.sh
• lunch cm_d2spr-userdebug
• make -j4 otapackage

If that builds, then the problem lies in the Viper's device tree. BUT, link me the .zip if it builds so we can actually know if it works or if it's like the Viper with a blank screen.

 

[brandonabandon]

Re: lg viper roms?

from jump, the device tree does have problems. to get a build, fork d710 recovery_keys.c, no element found @ overlay/res/.xmls, some sources allow the build without/some dont. fork d710 sirfgps.config, and the recovery_ui.c reads just re...? also patches for the charger.

 

[brandonabandon]

Re: lg viper roms?

i was able to compile ics aokp and cm9 with same booting results as jb. aokp boots logo/blank screen, cm9 boots logo hangs. flashing this method: system wipe, factory reset, flash rom/gapps, dalvik wipe. recovery log ->log - Pastebin.com. pg says the gpu drivers are possibly outdated. i swapped the updater-scripts and bootimg's between roms, same results. i will start your build nigel...any suggestions?

 

[brandonabandon]

Re: lg viper roms?

status: i cant compile poc recovery under any source. always issues. with 4.3 nandroid/mkyaffs2 not agreeing. i tried to compile aosp jb/ics, aokp "..", cm9,10,10.1, and now 10.2. cm 10.2 recovery so far compiles with your source nigel. your source has the omx error equivelant to the error i was experiencing while compiling cm10.1 (LOG TAG, enum ion heap ids, blah) swapped qcom to -CAF, build in progress. looking into and comparing iproj's gpu drivers, only difference between your kernel tree adreno_a3xx_snapshot.c and adreno_a3xx_trace under drivers/gpu/msm. funtime. how to incoporate these drivers?

 

[brandonabandon]

Re: lg viper roms?

im replacing all the gpu drivers. this will be quite the process.lol

 

[thenameisnigel]

Re: lg viper roms?

status: i cant compile poc recovery under any source. always issues. with 4.3 nandroid/mkyaffs2 not agreeing. i tried to compile aosp jb/ics, aokp "..", cm9,10,10.1, and now 10.2. cm 10.2 recovery so far compiles with your source nigel. your source has the omx error equivelant to the error i was experiencing while compiling cm10.1 (LOG TAG, enum ion heap ids, blah) swapped qcom to -CAF, build in progress. looking into and comparing iproj's gpu drivers, only difference between your kernel tree adreno_a3xx_snapshot.c and adreno_a3xx_trace under drivers/gpu/msm. funtime. how to incoporate these drivers?

OMX errors under ORv1 is actually good.

I say that because OMX errors are usually driver issues on Samsung devices. That's why omx is short for sec_omx which is Samsung Electronics Corp OMX. It's an issue in the device tree, because the device tree references some Samsung proprietary drivers (which is totally unneeded and just creates a lot of errors).

Comment out any line in the Android.mk, etc, etc that references non-LG blobs.

 

[brandonabandon]

Re: lg viper roms?

libmedia.so - Pastebin.com i got around this in cm10.1 by swapping frameworks and hardware aosp 4.2.2. i might have patched the system some with 4.2.2 as well. the same error, after patching to CAF, and patching CAF. any suggestions?

 

[thenameisnigel]

Re: lg viper roms?

libmedia.so - Pastebin.com i got around this in cm10.1 by swapping frameworks and hardware aosp 4.2.2. i might have patched the system some with 4.2.2 as well. the same error, after patching to CAF, and patching CAF. any suggestions?

nano /home/cannibal/orv1/out/target/product/ls840/obj/SHARED_LIBRARIES/libmedia_intermediates/LINKED/libmedia.so so it'll create a blank file.

Posted via Android Central App

 

[brandonabandon]

Re: lg viper roms?

yeah. were gonna need libmedia.so. anyhow, i dev'd/patched the gpu drivers and added 10.2 support. currently mid-build. im working on the 10.2 tree. i will add aosp 4.3 sources to your tree, (which successfully built 10.1(4.2)) i will know tomorrow.

 

[thenameisnigel]

Re: lg viper roms?

yeah. were gonna need libmedia.so. anyhow, i dev'd/patched the gpu drivers and added 10.2 support. currently mid-build. im working on the 10.2 tree. i will add aosp 4.3 sources to your tree, (which successfully built 10.1(4.2)) i will know tomorrow.

I'm pretty sure Qualcomm offers a download of the GPU drivers on their website that you could've used. Just use the Linux Kernel 3.2+ drivers.

 

[thenameisnigel]

Re: lg viper roms?

need fastboot.

There's no current possible way to use fastboot on the LG Viper.

 

[brandonabandon]

Re: lg viper roms?

zvi has fastboot. but locked.

 

[brandonabandon]

Re: lg viper roms?

I'm pretty sure Qualcomm offers a download of the GPU drivers on their website that you could've used. Just use the Linux Kernel 3.2+ drivers.

yeah. i nabbed iproj kernel's gpus'. i wanted to integrate into the build. i got a successful build with it on my cm10.1 tree. its missing some apps, i think i might have used aokp frameworks/hardware rather than aosp on my previous builds' because i had to remove 10 or so apps/providers due to java errors. i will replace if the rom boots. i will also try to get your repo buildable.

 

[brandonabandon]

Re: lg viper roms?

the build with the ipoj's gpu driver's was successful, same results though (no boot). i will investigate further.

 

[thenameisnigel]

Re: lg viper roms?

zvi has fastboot. but locked.

No, it's bootloader is similar in a way to Samsung's GS3. You are unable to use fastboot.

 

[brandonabandon]

Re: lg viper roms?

gotcha, its accessible but useless.