[G Pad 8.3 Android Development] N00b-un-2:
Okay, so from here forward I'm going to basically be using this dev thread as my brain dump on this project so I can go back and review my "notes" and any of you who have insights into what I'm doing can possibly help.

Here is where it stands: we have/had a working ROM based on the V500.

I have tried starting over from scratch and ran into a ton of problems, most of which were already fixed in the existing CM11 ROM.

I wiped out my CM11 source tree and rebuilt if from the ground up

NOTES for myself

source build/envsetup.sh and not ./build/envsetup.sh (facepalm)

I need to officially fork the original repos and start my own on github.

The issue with 4G seems to be a matter of the kernel not being compiled with all the drivers. I'm assuming this is because the kernel config that was being used to compile is the one from the V500 (which obviously doesn't have the drivers, seems pretty logical).

So the issue at this point is to be able to generate a bootable working kernel which includes the 4G driver. The way that the official kernel is built from source is nonspecific as to how the kernel is configd . it calls "altev-perf_defconfig" as the kernel config definition by the script "make_defconfig.sh". I think that if I were to merge the VK810 kernel source into the CM11 source tree (again... I wiped out my build environment, mind you), do a simple

grep -rl "altev" ./kernel/ | xargs sed -i "s/altev/vk810/g"

should replace all instances of altev with vk810, and then I save altev-perf_defconfig as "kernel.config" in the kernel/lge/vk810/ because if I'm seeing things right, the build is using "make_awifi070u_defconfig.sh". The naming conventions don't appear to be completely consistent across devices. But this is going to be the golden ticket, figuring out how to make the compile job build the kernel against the altev_perf-defconfig instead of the one it is using. I need to look at the code more, but it looks like LG uses the same kernel source for many devices and builds the kernels for the individual devices using individual defconfig files (kernel configs).

looking here http://wiki.cyanogenmod.org/w/Doc:_integrated_kernel_building it looks like I can manually specify the kernel config in BoardConfig.mk

eg;

TARGET_KERNEL_CONFIG = kernel/lge/arch/arm/configs/altev_perf-defconfig

TARGET_KERNEL_CONFIG = altev_perf-defconfig

target kernel config already points to kernel/device/arch/arm/configs and usually uses cyanogenmod_device-defconfig

After looking at the file 'cyanogenmod_vk810-defconfig' it turns out the file was automatically generated and does not contain all the variables defined by the official LGE kernel, (but does have a few hundred unused ones).

With any luck, I'll be able to take the new build when it's done and then just build the boot image incorporating the changes, eg; mka bootimage.

Now we are getting somewhere...

Trying to compile CM11 against the static zImage binary kernel that results from compiling using the LGE method results in a non-booting system, so it seems the kernel absolutely needs to be built against the CM11 source at compile time.

I'm in the middle of a compile so I can't change anything until its done, but I'll look at it when I get home this evening. Try not to get your hopes up prematurely, but I think I've had a break through. Unfortunately I have to wait until after the current compile is done (making sure that I can in fact build this from source without errors... you never know! sometimes git commits break stuff).