[ROM][WIP][4.4.2] CyanogenMod 11 KitKat for Optimus S/V

I did put it in the build, and the other VM .prop stuff too.
It does show the right network name and device cause of the .props but no mobile network. nothing in dmesg, logcat just says it's being enabled/disabled.
no soup for me. yet, anyway.

Try the apn-conf.xml from the ics roms. The newer ones have a lot of LTE apns. The framework-base config overlay may be different for cdma, check how other sprint phones on cm11 are working.
 
My build used the apns-conf.xml from CyanogenMod/android_vendor_cm which is 1537 lines and didn't work. The apns-conf.xml from TheJBC/android_vendor_lge is 1335 lines. Try using the one from TheJBC.
 
this looks interesting
https://github.com/CyanogenMod/android_device_lge_ls970-common
it's lte capable but is cdma at least. there's a cdma overlay folder.

My build used the apns-conf.xml from CyanogenMod/android_vendor_cm which is 1537 lines and didn't work. The apns-conf.xml from TheJBC/android_vendor_lge is 1335 lines. Try using the one from TheJBC.
I have, no dice. PAC as well. I am building with the Quattrimus one right now.
 
I made a mini-gapps package that installs to cache like the one from _MarcoMarinho_ but for kitkat. It flashed okay and showed the apps being prepared on startup but once I was booted up the play store was nowhere to be seen. I looked in cache using androxplorer and es file explorer and it showed the cache and data directories as empty, but when I checked them out with adb shell it showed that cache and data were mounted and I could view the contents of the directories. I'm not sure if this is related to not having play store installing correctly or if this is related to selinux. Although settings shows selinux as disabled it's possible it may be preventing access to those directories. cache has owner system and group cache and data has owner system and group system. The other directories which are viewable in file explorer have owner and group root. I asked in the p500 thread if someone would test the gapps package. It seems like we have to install gapps to cache, I don't really know how to trim the system directory down enough to fit it on there.
 
I'm working on patching the boot image to aufs mount mmcblk0p2 and mmcblk0p3 on top of /data and /system respectively.
it has to be done before init or the dalvik doesn't see the extra system apps and they never get recognized even if the partition is aufs mounted after boot. except that'll cause a soft reboot before long that just goes to the bootanimation instead of lg symbol. it does seem to work after boot, just getting the preinit busybox script right is picky so far. I put a 200MB build into the /system-ext partition and adb could see everything in lib and app and app-priv that was oversized when mounted late.
 
p500 has selinux set to enforcing. I'm looking over the flags for the p500 kernel config and they're a little different than the ones I've been using. Going to try a build using those.
Edit: nope, still disabled.
 
Last edited:
Got to extensively play with the alpha. Wifi shows "connected" but data doesn't flow (browser or play)
In terms of Gapps, SlimBean Gapps 2 from thekraven actually worked nicely (but without wifi it was a moot point.
Occasional reboot when mounted USB on computer, could be memory overload.

I am getting cellphone signal, haven't attempted an actual call. Touchpal keyboard works nicely (an old apk that was manually installed).
It's getting really exciting! I think once the radio and wifi are ironed out, everything else will fall into place. KitKat seems like it can take a beating and keep on trucking. Nice work Skinbark!
 
Hmm you say SlimBean gapps work? I'll have to try that since wifi is connecting and working for me

Sent from my LG-VM670 using Tapatalk
 
p500 has selinux set to enforcing. I'm looking over the flags for the p500 kernel config and they're a little different than the ones I've been using. Going to try a build using those.
Edit: nope, still disabled.
according to aosp:
Code:
 Android's SELinux implementation is in enforcing mode - rather than the non-functional disabled mode or the notification-only permissive mode - to act as a reference and facilitate testing and development. Although enforcing mode is set globally, please remember this can be overridden on a per-domain basis as is in the case of the application domain.

SELinux for Android is accompanied by everything you need to enable SELinux now. You merely need to integrate the latest Android kernel and then incorporate the files found in the ~platform/external/sepolicy directory (where examples can also be found):
https://android.googlesource.com/kernel/common/
https://android.googlesource.com/platform/external/sepolicy/

Those files when compiled comprise the SELinux kernel security policy and cover the upstream Android operating system. Place those files within the /device/manufacturer/device-name/sepolicy directory.
Then just update your BoardConfig.mk makefile - located in the directory containing the sepolicy subdirectory - to reference the sepolicy subdirectory once created, like so:

BOARD_SEPOLICY_DIRS := \
        <root>/device/manufacturer/device-name/sepolicy

BOARD_SEPOLICY_UNION := \
        genfs_contexts \ 
        file_contexts \ 
        sepolicy.te 

After rebuilding your device, it is enabled with SELinux. You can now either customize your SELinux policies to accommodate your own additions to the Android operating system as described in the Customization section or verify your existing setup as covered in the Validation section.
"you merely need to integrate the latest Android kernel..."
pah. like they support anything armv6. and it took quite a while to port the 3.0 over... might work better now that I've done it once already, but I can't afford that kind of time investment.
 
androidarmv6 has it working with the 3.0.x kernel, so we should be able to enable it too. I added some of their recent commits (Aug. 5) to ours but it's still showing as disabled. I just think there's something I'm overlooking.
 
I'm glad the 3.0 kernel is still working for the others.
do you have
BOARD_SEPOLICY_DIRS := \
<root>/device/lge/thunderc/sepolicy

BOARD_SEPOLICY_UNION := \
genfs_contexts \
file_contexts \
sepolicy.te
in the BoardConfig.mk and the android.googlesource.com/platform/external/sepolicy/ files installed in the build like it says in that quote?
I'm personally not interested in enhacing security... for my purposes it tends to interfere. things like chroot linux and preinit on boot seem to trigger security issues and I'm going to have to build more things than I want in to get them cooperating I suspect. Still want the latest and greatest android on my old phone, though, so I'm adding my efforts to the learning process.
 
I did try setting it up like they said on that page but it didn't cause it to be enabled. I think if you leave it as is without configuring it'll just generate a 'default' config but I could be wrong.
The settings in BoardConfig.mk override the settings in exernal/sepolicy so you can have a custom security config without messing with that package. But after fooling with it a little bit I think it's something else I'm missing - selinux should be enabled 'out of the box'. Unless the p500 builder is doing some pre-build tweaking my setup really isn't very different from theirs now - device/lge/thunderc, vendor/lge, and device/qcom/msm7x27 are from TheJBC, everything else is the same. As far as having selinux interfere with kernel development there's that option to disable se on the kernel command line that may be useful.
 
I did try setting it up like they said on that page but it didn't cause it to be enabled. I think if you leave it as is without configuring it'll just generate a 'default' config but I could be wrong.
The settings in BoardConfig.mk override the settings in exernal/sepolicy so you can have a custom security config without messing with that package. But after fooling with it a little bit I think it's something else I'm missing - selinux should be enabled 'out of the box'. Unless the p500 builder is doing some pre-build tweaking my setup really isn't very different from theirs now - device/lge/thunderc, vendor/lge, and device/qcom/msm7x27 are from TheJBC, everything else is the same. As far as having selinux interfere with kernel development there's that option to disable se on the kernel command line that may be useful.
actually, kernel development is only a bit of what I like to play around with. boot-from-sd is nice... the overlay idea is a way to try to get a minimal install in nand so it'll survive the card being removed while running. messing with the boot messes with the security the way I've been trying. flashing a duplicate copy of init.qcom.rc prevents the nand from mounting. it probably needs a new updater-script and update-binary to set security permissions.
I have yet to build in my changes but that is the logical next step. then they're security-signed before install and it won't freak over a percieved 'exploit.'
 
After trimming the rom a little by removing Bluetooth.apk, Term.apk and a few libvideoeditor files I was able to get Play Store going by installing this gapps:
Dev-Host - Slim_4.4.X_gapps_Nbsss_v2.zip - The Ultimate Free File Hosting / File Sharing Service
It uses only ~15 mb space on system.
Can anyone recommend a small keyboard that works with this rom?
try this one? I'm having build/crash issues right now and can't test easily.
Downloads - hackerskeyboard - Hacker's Keyboard, a 5-row keyboard using full PC key layout for Android tablets or phones - Google Project Hosting
 
actually, I'm showing 75 mb used for ROM, 100 Mb free after install. The Gapps works, I think it may be what was breaking the wifi though. I did a fresh install and wifi worked without gapps, did not work with gapps. Trying elsewhere for apps pack.
 

Trending Posts

Forum statistics

Threads
956,902
Messages
6,970,525
Members
3,163,646
Latest member
Chris34728