LG Optimus S: 4.4 KitKat?

Re: 4.4 KitKat?

I've crunched through more of the art thumb2 errors by attempting to translate the errored commands to thumb1 where I haven't found existing armv6 fixes (like atomic.cc and some other files are fixed already out there.)
hopefully I still have half a clue, the instruction sets have grown a lot. thumb1 is still a lot more complex than the 8/16 bit chips I've worked with even though they call it a 'risc' processor.
certainly not done yet. currently on the 5th or 6th file with thumb2 crud in it. And it's not proper patching, it's not checking for armv6 or 7 and dropping the appropriate code, just overwriting the v7 stuff. kind of like the first pass at the kernel, and some of that lame coding is still in there too.
 
Re: 4.4 KitKat?

here's some really nice tidbits.
Running Android with low RAM | Android Developers
the other 'porting' sections nearby have lots of good system variables and such listed as well.

hah, look at this nasty little thing from the build system. near the end, building the boot image.
selinux_fc = (str) /tmp/targetfiles-il3eWy/BOOT/RAMDISK/file_contexts
which looks like, if the ramdisk is modified from the stock build, selinux sez ptooey. so no ramdisk patching zip files probably.
 
Last edited:
Re: 4.4 KitKat?

I still haven't figured out how to enable selinux in my builds.

from what I was messing with in the kernel early on, you probably don't want to...
I think several kernel CONFIG_ variables are flat out missing and would need their associated code backported before it'd work right.
ashmem also wants backported, it was causing that bootloop issue until androidarmv6 disabled the thing that wanted to use the newer ashmem in dalvik. A memory dump variable of some kind I think.
here's data anyway...
Validating Security-Enhanced Linux in Android | Android Developers
it points out the needed kernel mods among other things. google has really updated their developer docs since ICS.
 
Re: 4.4 KitKat?

I'm not sure anymore since we're getting working builds without it, but I'm pretty sure I've read selinux was going to be nessasary for something. Maybe not....

Sent from my LG-LS670 using Tapatalk
 
Re: 4.4 KitKat?

I'm not sure anymore since we're getting working builds without it, but I'm pretty sure I've read selinux was going to be nessasary for something. Maybe not....

Sent from my LG-LS670 using Tapatalk
That's what I thought too. I need to look at the p500 stuff more closely, I think they have it enabled. I set all the flags I could find to enable it but it still shows up as disabled.
 
Re: 4.4 KitKat?

I took the tmobile theme manager packages out of my build and it seems to run a little quicker.
 
Re: 4.4 KitKat?

I took the tmobile theme manager packages out of my build and it seems to run a little quicker.

It would crash when i went to the themes section anyway. Running your build now by the way

Sent from my LG-LS670 using Tapatalk
 
Re: 4.4 KitKat?

dang it, androidarmv6 been pushing new stuff all day.
no wonder all my builds've been broken. teach me not to have a backup repo that I can revert to if a fresh sync bites the big one.
maybe next time I'll check theirs and cyanogenmod's githubs to see if they've been idle long enough to not be broken.
 
Re: 4.4 KitKat?

dang it, androidarmv6 been pushing new stuff all day.
no wonder all my builds've been broken. teach me not to have a backup repo that I can revert to if a fresh sync bites the big one.
maybe next time I'll check theirs and cyanogenmod's githubs to see if they've been idle long enough to not be broken.

I can't tell if they are on the 4.4.0 booting manifest or in sync with cm now.
 
Re: 4.4 KitKat?

I picked up a couple glitches myself but I managed to get a good sync after a try or two. They're on 4.4.2 now. They've got things working to the point where I'm only using device/thunderc and squidkernel plus dropping the thunderc folder into their vendor/lge. Everything's coming together nicely. Use the latest cwm to get rid of sd-ext errors.
 
Re: 4.4 KitKat?

Give these a try for data. If any of this helps, i'll point you to the changes. Other tips would be to say "open apns" in voice dialer and try to manually enter the apns.

rcm11 - build.prop tweak from Sprint Toro. framework overlays from toro Goo.im Downloads - Downloading rcm-11-20131231-thunderc-thekraven.zip
scm11 - no build.prop tweak. apn-conf.xml from CAI, framework overlays from CAI Goo.im Downloads - Downloading scm-11-20131231-thunderc-thekraven.zip
tcm11 - build.prop tweak from Sprint Toro, apn-conf.xml from CAI, framework overlays from CAI Goo.im Downloads - Downloading tcm-11-20131231-thunderc-thekraven.zip
 
Re: 4.4 KitKat?

Give these a try for data. If any of this helps, i'll point you to the changes...
rcm11 - build.prop tweak from Sprint Toro. framework overlays from toro Goo.im Downloads - Downloading rcm-11-20131231-thunderc-thekraven.zip
scm11 - no build.prop tweak. apn-conf.xml from CAI, framework overlays from CAI Goo.im Downloads - Downloading scm-11-20131231-thunderc-thekraven.zip
tcm11 - build.prop tweak from Sprint Toro, apn-conf.xml from CAI, framework overlays from CAI Goo.im Downloads - Downloading tcm-11-20131231-thunderc-thekraven.zip

the rcm build kinda enhanced my theory that enabling/disabling data is pointing at an audio device.
Code:
<6>[  307.191811] [audpp.c:audpp_dsp_event] DISABLE
<6>[  307.192008] [audpp.c:audpp_disable] Received CFG_MSG_DISABLE from ADSP
<6>[  307.192106] [adsp.c:msm_adsp_disable] disable 'AUDPPTASK'
<6>[  307.193246] [adsp.c:msm_adsp_put] closing module AUDPPTASK
<6>[  307.193383] [audmgr.c:audmgr_disable] session 0xc07da4c8
<6>[  307.194473] [audmgr.c:audmgr_rpc_thread] rpc_reply status 0
<3>[  307.205131] [audmgr.c:process_audmgr_callback] DISABLED
<6>[  308.792708] [audmgr.c:audmgr_enable] session 0xc07da4c8
<6>[  308.793598] [audmgr.c:process_audmgr_callback] rpc READY handle=0x00000000
<6>[  308.793973] [audmgr.c:audmgr_rpc_thread] rpc_reply status 0
<6>[  308.799638] [audmgr.c:process_audmgr_callback] rpc CODEC_CONFIG volume=0x00000000
<6>[  308.799731] [adsp.c:msm_adsp_get] opening module AUDPPTASK
<6>[  308.800836] [adsp.c:msm_adsp_enable] enable 'AUDPPTASK'state[0] id[17227122]
<6>[  308.801853] [adsp.c:handle_adsp_rtos_mtoa_app] module AUDPPTASK: READY
<6>[  308.803068] [audpp.c:audpp_dsp_event] ENABLE
<6>[  312.782751] [audpp.c:audpp_dsp_event] DISABLE
<6>[  312.782953] [audpp.c:audpp_disable] Received CFG_MSG_DISABLE from ADSP
<6>[  312.783049] [adsp.c:msm_adsp_disable] disable 'AUDPPTASK'
<6>[  312.784046] [adsp.c:msm_adsp_put] closing module AUDPPTASK
<6>[  312.784181] [audmgr.c:audmgr_disable] session 0xc07da4c8
<6>[  312.786659] [audmgr.c:audmgr_rpc_thread] rpc_reply status 0
<3>[  312.796243] [audmgr.c:process_audmgr_callback] DISABLED
dmesg from enabling data toggle.
edit:// skinbark pointed out that it's the 'click' noise from leaving the system sounds on. duh...
//edit: same results from all three roms. no data for me.
Other tips would be to say "open apns" in voice dialer and try to manually enter the apns.
now that looks interesting. I forgot to do that in those test roms.
In my build, I get
Virgin Mobile US
0
pressing it,
it has the name, but everthing else is 0 or not set, until the MMS settings, which are correct.
but, dang, it exactly matches a working data setup with PAC.
 
Last edited:
Re: 4.4 KitKat?

Excellent work guys!! This is why this device was so awesome. True community unity and support. The device is far out dated but that doesn't stop you guys. Bravo!!

Sent from my Galaxy S4
 
Re: 4.4 KitKat?

awesome work. Thanks!
this build runs well off of the card too! gotta mod fstab.thunderc and init.qcom.rc in the boot.img, and copy the /system directory over to mmcblk0p3, but then it's smooth as butter.
I am working on a kernel bug, temperature readout wrong and causes powerdown at lo temps. Fix is pushed to cm-11.0 branch.
Look like someone donated you a phone? or are those tester screenshots?

by the way, your 'android' repo has a space missing before "revision" on line (83?) if I remember right.
View attachment 99448View attachment 99449View attachment 99450

I got data working. i'll push my changes tomorrow. Somewhere the androidarmv6 commits broke camcorder. I'll have to see what changes they made.

Rom
cm-11-20140103-thunderc-thekraven.zip | by thekraven for Optimus S
Philz non touch recovery for kitkat or can use Skinbark's cwm.
philz_6.0.4.6-thunderc-thekraven.zip | by thekraven for Optimus S
 
Re: 4.4 KitKat?

More like borrowed. Haha. The no data thing was bugging me. I think the fix was the jbc 10.1 overlays and inits. There's build.prop lines to test. Try switching on different ro.telephony.ril.v3 lines

Also thanks to skinbark for pointing to the team hydra github. I used their frameworks opt telephony . so I'm not sure if it works with the cm fork

Sent from my SM-T217S using AC Forums mobile app
 
Re: 4.4 KitKat?

Awesome job thekraven! What a relief to have that fixed! FYI to flashers the Virgin fix from my link will break data with this rom. Removing.
 
Re: 4.4 KitKat?

More like borrowed. Haha. The no data thing was bugging me. I think the fix was the jbc 10.1 overlays and inits. There's build.prop lines to test. Try switching on different ro.telephony.ril.v3 lines

Also thanks to skinbark for pointing to the team hydra github. I used their frameworks opt telephony . so I'm not sure if it works with the cm fork

Sent from my SM-T217S using AC Forums mobile app
I saw those overlays in your vendor/lge and was wondering cuz they're not in androidarmv6's, but didn't get around to adding them. It's a surprisingly mysterious subject trying to get this stuff going!
 

Forum statistics

Threads
955,737
Messages
6,965,660
Members
3,163,379
Latest member
Mike D