LG Optimus S: 4.4 KitKat?

Re: 4.4 KitKat?

I tried changing ro.telephony.ril.v3 and apns-conf.xml on my build but it didn't fix it so I guess there's more to it than that. Removing skipdatareg on thekraven's build broke data however so I think it is necessary.
 
Re: 4.4 KitKat?

USB tether works on thekraven's build (using now). Wifi tether still broken - says Error.
 
Re: 4.4 KitKat?

Do I need to push anything else? Try manually adding Virgin Mobile in the new eri.xml before compiling. Or grab the eri.xml from the compiled frameworks-res.apk via 7zip and swap out anywhere you see sprint. Then throw it back into the xml folder. I know my manifest isn't updated.

Sent from my SPH-L900 using AC Forums mobile app
 
Re: 4.4 KitKat?

Do I need to push anything else? Try manually adding Virgin Mobile in the new eri.xml before compiling. Or grab the eri.xml from the compiled frameworks-res.apk via 7zip and swap out anywhere you see sprint. Then throw it back into the xml folder. I know my manifest isn't updated.

Sent from my SPH-L900 using AC Forums mobile app
Looks good by eye, but, can't check now, gotta go work soon after a nap. Should have time Monday if I'm lucky or Tuesday if not. Most likely by the time I'm back to it more bugs'll get squished while I wait.
awesome work on the data. I've had it on my phone all day and it's never even rebooted. Play store glitched in the middle of a ridiculous amount of downloading but otherwise it's been silky smooth.
 
Re: 4.4 KitKat?

skinbark runing repo init -u git://github.com/skinbark/android.git -b cm-11.0 then repo sync gives this error

error.GitError: androidarmv6/android_external_chromium_org rev-list (u'^977480fc0090547f6cf5afafd54563df43eedb82', 'HEAD', '--'): fatal: bad object 977480fc0090547f6cf5afafd54563df43eedb82
 
Re: 4.4 KitKat?

skinbark runing repo init -u git://github.com/skinbark/android.git -b cm-11.0 then repo sync gives this error

error.GitError: androidarmv6/android_external_chromium_org rev-list (u'^977480fc0090547f6cf5afafd54563df43eedb82', 'HEAD', '--'): fatal: bad object 977480fc0090547f6cf5afafd54563df43eedb82
Use this instead: repo init -u git://github.com/androidarmv6/android.git -b cm-11.0
 
Re: 4.4 KitKat?

it still returns the same error
Delete the directory you initialized the repo in and run the command in an empty directory. If it still won't download you should create a github account if you haven't already, fork the androidarmv6 'android' project and edit default.xml by commenting out the android_external_chromium_org project with <!-- project --> and initialize your source with
repo init -u git://github.com/your-account-name/android.git -b cm-11.0
You'll be missing that project but you should be able to download it as a zip file and place it in your source tree manually or set the revision to a different version of the package so it'll download. I really don't know what's causing that error but there should be a way to get around it.
Or you could just wait a while and the error will probably go away.
 
Re: 4.4 KitKat?

I think they have the Atheros ath6kl chip. And thunderc use the bcm4325 with the drivers ported from bcm4329 I believe. Maybe look at the driver FM code and try to see if that's a battery drainer. In ICS battery life was better with WPA_SUPPLICANT_VERSION := VER_0_6_X, so you might look at what's needed to port that.
 
Re: 4.4 KitKat?

I think they have the Atheros ath6kl chip. And thunderc use the bcm4325 with the drivers ported from bcm4329 I believe. Maybe look at the driver FM code and try to see if that's a battery drainer. In ICS battery life was better with WPA_SUPPLICANT_VERSION := VER_0_6_X, so you might look at what's needed to port that.

ah, I was looking at this:
BOARD_HAVE_FM_RADIO := true
BOARD_GLOBAL_CFLAGS += -DHAVE_FM_RADIO
BOARD_FM_DEVICE := bcm4325

rather than
WIFI_DRIVER_MODULE_PATH := /system/wifi/ar6000.ko
WIFI_DRIVER_MODULE_NAME := ar6000
in the AndroidBoard.mk
 
Last edited:
Re: 4.4 KitKat?

oh, my, they've really changed stuff up in there. No easy drop-in for me. the sms.blahblah functions aren't there with the same name.
duh, looked in wrong file, needed the cdma folder. CdmaInboundSmsHandler.java looks similar enough I'm trying to build with a patch.
 
Re: 4.4 KitKat?

just as an update, I tried to patch that file and got an mms in the notification bar with no subject. touched it and it vanished like on PAC with 3g turned off.
I looked up the logcat error it was throwing about the mms and found this thread on xda which led to this commit being reviewed at cm.
Building to test again.
I used my PAC install to send myself an mms (text+subject) and pulled the battery after it sent but before it could recieve. Then flashed the previous test build. Logcat shows the mms bouncing every now and again... it's still waiting in the system for me to get it.
//edit: tested.. no go. but I forgot the vm mms overlay in the build with the correct user agent and id url. try again.

nope.
here's the exact error.
Code:
V/TransactionSettings(  990): APN setting: MMSC: http://mmsc.vmobl.com:8088/mms? looked for: current IS NOT NULL
W/TransactionService(  990): Exception occurred while handling message: { when=-83ms what=1 arg1=1 obj=transactionType: 1 uri: content://mms/1 pushData: null mmscUrl: null proxyAddress: null proxyPort: 0 target=com.android.mms.transaction.TransactionService$ServiceHandler }
W/TransactionService(  990): 	at com.android.mms.transaction.TransactionService.beginMmsConnectivity(TransactionService.java:552)
W/TransactionService(  990): 	at com.android.mms.transaction.TransactionService$ServiceHandler.processTransaction(TransactionService.java:890)
W/TransactionService(  990): 	at com.android.mms.transaction.TransactionService$ServiceHandler.handleMessage(TransactionService.java:733)
 
Last edited:
Re: 4.4 KitKat?

I have working MMS :-$
two non-device files patched,
and a modified apns-conf.xml which copies most of the sprint apn as VM (and removes the sprint apns per this post.)
which changes I will post after done babysitting. Well, looks like after work this evening instead since I got done kinda late.
the VM MMS change may be worth trying to submit to cm's gerrit since it's really really close to their cm10.2 patch.
 
Last edited:
Re: 4.4 KitKat?

Looks like androidarmv6 is working on bluetooth and wifi tethering. I think there's a kernel patch too.

Edit: Here's a test build for bluetooth and wifi tethering with patches from androidmeda. I had build errors using their patch and had to add a file;: device/lge/thunderc/bluetooth/vnd_thunderc.txt to get it to build. I just renamed the libbt_lge.txt

http://www.androidfilehost.com/?fid=23329332407567780
This build is twrp 2.3 friendly and should flash with older recoveries. I haven't tried it on cwm6.0.4 or philz recovery.
Try wifi tethering with the included system/etc/wifi/hostapd.conf file and if wifi tethering doesn't work, try deleting that file and reboot
 
Last edited:
Re: 4.4 KitKat?

changes for Virgin Mobile US MMS:
this commit for src/java/com/android/internal/telephony/dataconnection/DcTracker.java pending at cm (patchset 6) absorbed by CM
I added another hacky change to DcTracker.java to force select the APN on startup based on ro.cdma.home.operator.numeric since the code refuses to grab an APN until one is selected or modified externally otherwise. commit (fixes its parent)

The other file, frameworks/opt/telephony/src/java/com/android/internal/telephony/cdma/CdmaSMSDispatcher.java I put on github. first useful commit the cm existing file, next commit is the patched file.
Here's the MMS commit.
I had issues with the Log.d Log.e and TAG parts of the patch and swapped it down to logd and loge with no TAG. If I really knew what I was doing, I'd've fixed that cleaner.
I also changed the eri.xml text to Virgin Mobile and changed all the VM670 instead of LS670 in the device folders everywhere I could grep it (except for the GB build fingerprint bit) before building so it would all get along happy-like. I hoped.
Which actually made no difference. Any operator_alpha/mcc/mnc programmed into the overlay, device makefile, and apns-conf.xml that I tried would send/recieve mms once activated.
The stock cm APN will send/recieve MMS, but it seems to need manual messing in apns from voicedialer. opening the VM APN and saving it without changing anything triggers MMS connection. Once per reboot. Fixed!
 
Last edited:
Re: 4.4 KitKat?

... Here's a test build for bluetooth and wifi tethering with patches from androidmeda. I had build errors using their patch and had to add a file;: device/lge/thunderc/bluetooth/vnd_thunderc.txt to get it to build. I just renamed the libbt_lge.txt ...
hotspot works, no modifications. that is awesome.
bluetooth still won't pair, kind of reboots itself after not pairing for a little while... 'turning on' again, see the keyboard again, says 'pairing'... repeat.
 

Trending Posts

Members online

Forum statistics

Threads
956,978
Messages
6,970,913
Members
3,163,679
Latest member
careerzoneacademy