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

[skinbark]

ok I'm rebuilding and testing with what you gave me, may try other config later. I'm looking at getting around an apparent permission problem with cache.
Edit: well it didn't break anything, logging into google now.
Edit: Partition info shows correct /data partition size
Edit: cache is working. I'd call that a success

 

[bigsupersquid]

I think the fstab bit from hammerhead may be important, its sets all kind of flags on mount for the main directories. my earlier guesses, were really just that. guesses, at how it might work.

 

[skinbark]

I agree this is nicer than link2sd scripts. Loading up apps from the play store now

 

[skinbark]

thekraven uploaded 3 roms to test for data function. I'm planning on activating a phone this weekend or next week but I can't do anything until then.
http://forums.androidcentral.com/lg...s-hacks/331332-4-4-kitkat-14.html#post3362910

 

[skinbark]

Local manifests (full and barebones)

 

[skinbark]

After using this setup for a while, I'd say it seems to be working great, although it's slower than normal with my class 4 card. I ordered the latest UHS-1 card that's supposed to be super fast so hopefully that should remedy the speed issue. Many many thanks bigsupersquid! This makes all the difference.

 

[brotherswing]

So I haven't tried it yet, I'm still on TWRP 2.2.2.1. I'm reluctant to switch to CWM because, well, I'm lazy and really like the touch recovery. I looked (a little bit) for a newer TWRP build for thunderc but no dice. Does anyone here happen to know where a link would be? Failing that I might compile it myself, but as I stated...lazy.

Explore! Rescue! Protect!

 

[skinbark]

So I haven't tried it yet, I'm still on TWRP 2.2.2.1. I'm reluctant to switch to CWM because, well, I'm lazy and really like the touch recovery. I looked (a little bit) for a newer TWRP build for thunderc but no dice. Does anyone here happen to know where a link would be? Failing that I might compile it myself, but as I stated...lazy.

Explore! Rescue! Protect!

I like TWRP too and I'll probably try and make a build soon, I just haven't gotten around to it. Lazy too

 

[bigsupersquid]

I for some reason have 2/3 functional bluetooth.
it turns on and sees devices but won't complete pairing.
fresh androidarmv6 sync if it matters, and common_full_phone.mk instead of mini.mk in cm.mk

 

[thewraith420]

I'm getting really anxious to see what the next build you guys release is going to be like!

Sent from my XT907 using Tapatalk

 

[Anino4]

I'm getting really anxious to see what the next build you guys release is going to be like!

Sent from my XT907 using Tapatalk

Same here, can't wait to see a fully functional kitkat rom !

Posted via Android Central App

 

[bigsupersquid]

galaxy s3 is virgin mobile, has cm11 nightlies and working data...
lte, but maybe bits can be extracted.
interesting, the apns-conf.xml from this:

<?xml version="1.0" encoding="utf-8"?>
<apns version="8">
<!-- Sprint/Virgin Mobile -->
	<!-- Modify APN for Sprint LTE support -->
	<apn carrier="LTE - SPRINT test ISP" mcc="001" mnc="01" apn="n.ispsn" type="default,mms" mmsc="http://mms.sprintpcs.com" mmsproxy="68.28.31.7" mmsport="80" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
	<apn carrier="LTE - SPRINT test OTA" mcc="001" mnc="01" apn="otasn" type="fota" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
	<apn carrier="LTE - SPRINT test PAM" mcc="001" mnc="01" apn="pamsn" type="dun" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
	<apn carrier="LTE - SPRINT test ISP" mcc="001" mnc="010" apn="n.ispsn" type="default,mms" mmsc="http://mms.sprintpcs.com" mmsproxy="68.28.31.7" mmsport="80" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
	<apn carrier="LTE - SPRINT test OTA" mcc="001" mnc="010" apn="otasn" type="fota" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
	<apn carrier="LTE - SPRINT test PAM" mcc="001" mnc="010" apn="pamsn" type="dun" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
	<!-- END APN database for Sprint LTE support -->

	<!-- APN database for Sprint EHRPD support -->
	<apn carrier="EHRPD - SPRINT test ISP" mcc="001" mnc="01" apn="n.ispsn" type="default,mms" mmsc="http://mms.sprintpcs.com" mmsproxy="68.28.31.7" mmsport="80" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
	<apn carrier="EHRPD - SPRINT test OTA" mcc="001" mnc="01" apn="otasn" type="fota" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
	<apn carrier="EHRPD - SPRINT test PAM" mcc="001" mnc="01" apn="pamsn" type="dun" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
	<apn carrier="EHRPD - SPRINT test ISP" mcc="001" mnc="010" apn="n.ispsn" type="default,mms" mmsc="http://mms.sprintpcs.com" mmsproxy="68.28.31.7" mmsport="80" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
	<apn carrier="EHRPD - SPRINT test OTA" mcc="001" mnc="010" apn="otasn" type="fota" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
	<apn carrier="EHRPD - SPRINT test PAM" mcc="001" mnc="010" apn="pamsn" type="dun" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
	<!-- END APN database for Sprint EHRPD support -->
	
	<!-- VIRGIN MOBILE CUSTOM APNS -->
	<apn carrier="APN1 Virgin Internet LTE" numeric="310120" mcc="310" mnc="120" apn="n.vmu.ispsn" user="Sprint" server="" password="*" proxy="null" port="null" mmsproxy="68.28.31.7" mmsport="80" mmsprotocol="null" mmsc="http://mmsc.vmobl.com:8088/mms?" type="default,supl,mms,fota,dun" bearer="14" /> 
	<apn carrier="APN2 Virgin Internet EHRPD" numeric="310120" mcc="310" mnc="120" apn="n.vmu.ispsn" user="Sprint" server="" password="*" proxy="null" port="null" mmsproxy="68.28.31.7" mmsport="80" mmsprotocol="null" mmsc="http://mmsc.vmobl.com:8088/mms?" type="default,supl,mms,fota,dun" bearer="13" /> 
	<!-- END VIRGIN MOBILE CUSTOM APNS-->	
<!-- END Sprint/Virgin Mobile-->
</apns>

dang it, I swear the data toggle is trying to turn on qdsp5 audio instead of the rmnet interface.

 

[brotherswing]

I love Unix based operating systems! Where else can you cobble together the bits of code and compile something that works!

Explore! Rescue! Protect!

 

[bigsupersquid]

this is new. I read about it for JB but never saw it.

adb shell
error: device unauthorized. Please check the confirmation dialog on your device.

and a toast pops up with the host rsa key.
cool.

 

[skinbark]

this is new. I read about it for JB but never saw it.

and a toast pops up with the host rsa key.
cool.

I just saw that too after doing the full phone build.
Evo V 4G is another Virgin phone I was looking at. 3G + Wimax. There's a kitkat build with working 3g on xda. github.org/TeamHydra. shooter is sprint and shootervm is virgin.

 

[skinbark]

I for some reason have 2/3 functional bluetooth.
it turns on and sees devices but won't complete pairing.
fresh androidarmv6 sync if it matters, and common_full_phone.mk instead of mini.mk in cm.mk

I was able to pair the phone with my linux system, and initiate a file transfer from the pc to the phone. The phone recognized the incoming file and began to download it but the transfer failed with the message 'Request can't be handled correctly.' The phone also detected an attempt to 'Browse files' from the pc which is a kind of ftp connection. It probably just needs to be configured.

 

[thekraven]

One big thing i see missing is:

https://github.com/TheJBC/android_d...mmit/62bf340df4c7d7d5ed5712ae8e16e9c715f96019

The patch is in my builds, but no feedback on data.

 

[bigsupersquid]

the 3 builds on the generic kitkat thread, no data for me.
and every cm11 build i try gives that weird dmesg toggling audio instead of radio.

One big thing i see missing is:

https://github.com/TheJBC/android_d...mmit/62bf340df4c7d7d5ed5712ae8e16e9c715f96019

The patch is in my builds, but no feedback on data.

 

[skinbark]

the 3 builds on the generic kitkat thread, no data for me.
and every cm11 build i try gives that weird dmesg toggling audio instead of radio.

I think the audio messages are related to the hissing sound you hear through headphones when you do something and the audio gets turned on for a couple seconds, you hear a soft hissing sound. I notice that a lot on various roms.

 

[bigsupersquid]

I think the audio messages are related to the hissing sound you hear through headphones when you do something and the audio gets turned on for a couple seconds, you hear a soft hissing sound. I notice that a lot on various roms.

I dunno, I didn't see it in JB watching cat /proc/kmsg (realtime) but in kitkat every time you click the data toggle it spits something about enable then disable module AUDPPTASK. I can push a hardkey and it says gpio blahblah, then toggle data and get the audpp message, every time.
here, logcat with thekraven's just-mentioned patch inserted. toggle on, then off.

D/ConnectivityService( 500): setMobileDataEnabled(true)
D/MobileDataStateTracker( 500): default: setUserDataEnable: E enabled=true
I/AudioHardwareMSM72XX( 110): set device to SND_DEVICE_SPEAKER device_id=0
I/AudioHardwareMSM72XX( 110): Enabling post proc features with mask 0x0000
I/AudioHardwareMSM72XX( 110): set device to SND_DEVICE_SPEAKER device_id=0
I/AudioHardwareMSM72XX( 110): disabling post proc features with mask 0x0000
D/ConnectivityService( 500): setMobileDataEnabled(false)
D/MobileDataStateTracker( 500): default: setUserDataEnable: E enabled=false
I/AudioHardwareMSM72XX( 110): set device to SND_DEVICE_SPEAKER device_id=0
I/AudioHardwareMSM72XX( 110): Enabling post proc features with mask 0x0000
I/AudioHardwareMSM72XX( 110): set device to SND_DEVICE_SPEAKER device_id=0
I/AudioHardwareMSM72XX( 110): disabling post proc features with mask 0x0000