[ROM][MOD][4.4.2][EXPERIMENTAL] KitKat OS2SD

bigsupersquid, there is a bug in your qualcom settings for the camera service, I just commented out the ifdef in the service and it built, just made an os2sd rom for a clean build to test before I tweak it. Also dual boot solution: finally a use for all my old microsd cards!
[will update once dalvik builds]
cool. I just inherited the bug. the rom builds ok on my system (?)
another bug, fixed now, is sysinit called from init.qcom.rc
should be in init.rc only. wasn't there yet when I caused the bug way back when before cm incorporated it again. it runs twice unless corrected.
 
Last edited:
cool. I just inherited the bug. the rom builds ok on my system (?)
another bug, fixed now, is sysinit called from init.qcom.rc
should be in init.rc only. wasn't there yet when I caused the bug way back when before cm incorporated it again. it runs twice unless corrected.

Yeah luckily that doesn't prevent it from booting at least. My sdcard now boots properly, so I'll be moving this from my test card to my main card. I did notice the time lag in upper right, of course lockscreen time is right. Location now works properly for widgets. I made a permissions fixer package as well, eventually we should add fix permissions back to the recovery. after I move this to my primary card I'll patch the apn (afaik the apn conf is no longer the standard implementation) make a new lunch option for os2sd, and see what else to patch and add to a repo.

Also your repo lacks the external storage provider work around apk.
 
Last edited:
Yeah luckily that doesn't prevent it from booting at least. My sdcard now boots properly, so I'll be moving this from my test card to my main card. I did notice the time lag in upper right, of course lockscreen time is right. Location now works properly for widgets. I made a permissions fixer package as well, eventually we should add fix permissions back to the recovery. after I move this to my primary card I'll patch the apn (afaik the apn conf is no longer the standard implementation) make a new lunch option for os2sd, and see what else to patch and add to a repo.

Also your repo lacks the external storage provider work around apk.

so I've been testing some of my initial patches, and have coded a few core changes to tweak some mms and storage related issues. I also added the os2sd code to my local repo. Haven't gotten around to cleaning up the recovery yet (I'm actually tempted to port twrp) about to build with my fixes and make sure I patched everything correctly. Then I'll start hosting my builds (probably weekly unless I run out of bugs that irritate me)

Haven't looked much into video in snapchat yet, but its glitchy, probably has to do with the camera resolution not being grabbed properly.
 
so I've been testing some of my initial patches, and have coded a few core changes to tweak some mms and storage related issues. I also added the os2sd code to my local repo. Haven't gotten around to cleaning up the recovery yet (I'm actually tempted to port twrp) about to build with my fixes and make sure I patched everything correctly. Then I'll start hosting my builds (probably weekly unless I run out of bugs that irritate me)

Haven't looked much into video in snapchat yet, but its glitchy, probably has to do with the camera resolution not being grabbed properly.
I would enjoy seeing your changes, especially for mms.
 
I would enjoy seeing your changes, especially for mms.

Well now we must wait as my buildserver goes about its work. Was the half finished twrp settings from a previous rom? I didn't really pay much attention to whether it was ported to the 670. When I move on to recovery, there will be one recovery that can do both internal or external installs as well as wipe battery stats and fix permissions.
 
Well now we must wait as my buildserver goes about its work. Was the half finished twrp settings from a previous rom? I didn't really pay much attention to whether it was ported to the 670. When I move on to recovery, there will be one recovery that can do both internal or external installs as well as wipe battery stats and fix permissions.

everything I have repo'd but the kernel was either grabbed from skinbark's repo or thekraven's. I did port the kernel from p500 source. I have implemented a few changes in the device folder, but most of the stuff on my manifest is inherited; I'm still learning about the build system, repo, and git.
mostly my repo is public so other people can fix and borrow from it like I do with everybody else's stuff. plus since I posted binaries, need source up for GPL (kernel...) and it's polite to post source for the built ROM for others to kang.
the twrp stuff in there built but won't quite work right. it does start up. check github.com/skinbark and look for the twrp fork.
 
Hi, Skinbark. I have the optimus v zv9. I hear that if I use touch recovery, I will be bricked. Can you update to support zv9?
 
hey squid, I'm still having trouble with mms debugging you mentioned you can get send/receive to work after modifying the apn in the settings stub, which of the 4 or so variations of the virgin mobile apn settings worked for you?

For me it seems the issue is that TransactionSettings is failing to properly receive the settings, i'm hardcoding if statements to set the values if they return null as a test.
 
Last edited:
hey squid, I'm still having trouble with mms debugging you mentioned you can get send/receive to work after modifying the apn in the settings stub, which of the 4 or so variations of the virgin mobile apn settings worked for you?

For me it seems the issue is that TransactionSettings is failing to properly receive the settings, i'm hardcoding if statements to set the values if they return null as a test.
TeamHydra finally incorporated the fix I posted a link to for DcTracker, so that helps a little.
I tried hardcoding the cdma stub in DcTracker to the Virgin Mobile APN as it gets set in the radio log when it's working and it STILL won't send or recieve until the APN is saved or activated in the APNs editor stub in settings, even though the log shows that apn everywhere it's usually stubbed out with blanks.
Now DcTracker works out of the box to pick up the APN once triggered, but it won't use it until then.
I can use all sorts of varations on the APN and still get MMS once it's triggered. Most of the settings don't affect it and none of them seem to trigger it being picked up on boot.
The simplest is this:
Code:
<apn carrier="Virgin_Mobile" mcc="311" mnc="490" apn="0" mmsproxy="205.239.233.136" mmsport="81" mmsc="http://mmsc.vmobl.com:8088/mms?" type="mms" />
make it type="default,mms" and it picks up the radio button in the editor, but once it's checked it stays checked. add another apn with the same mcc/mnc and default,mms set, and you can pick between the two radio buttons.
The long version I tried sets every variable the same as it shows up in the log when it's working. bearer=7 or 8, authype=-1, protocol and roaming_protocol=IP, carrier_enabled=1, no (port proxy user password). It still works when triggered and won't pick up on boot.
I've also fruitlessly tried the Sprint APN settings for user , password, and authtype (*,*,3) in there too. ApnSetting doesn't include server in the list of variables.
oh, and it doesn't seem to matter what the carrier and apn fields hold as long as they're not null.
 
Last edited:
When do you guys think you can fix MMS, bluetooth, and sd ext app install? These features are important to me.
 
Last edited:
When do you guys think you can fix MMS, bluetooth, and sd ext app install? These features are improtant to me.
with this rom all apps are automatically on sd.
if you want an alternative, with virgin mobile mms,
http://forums.androidcentral.com/op...kernel-cm-11-0-4-4-2-ov-kitkat-jbc-based.html
non-os2sd (regular internal memory)
you have to prod the mms once every reboot, and use something other than apps2sd (like mounts2sd) but everything works.
you can also install the latest release kernel over this rom and get bluetooth I think. no mms though.
http://forums.androidcentral.com/op...android_kernel_lge_msm7x27-3-0-x-3-0-8-a.html
 
Last edited:
with this rom all apps are automatically on sd.
if you want an alternative, with virgin mobile mms,
http://forums.androidcentral.com/op...kernel-cm-11-0-4-4-2-ov-kitkat-jbc-based.html
non-os2sd (regular internal memory)
you have to prod the mms once every reboot, and use something other than apps2sd (like mounts2sd) but everything works.
you can also install the latest release kernel over this rom and get bluetooth I think. no mms though.
http://forums.androidcentral.com/op...android_kernel_lge_msm7x27-3-0-x-3-0-8-a.html

Hey my bluetooth works flawlessly using your source, I'm about to work on my website and add a nightly section for my builds, but mind you, I will only build for os2sd, with a focus on virgin mobile.

So far I've been tweaking the power profiles, and the usb mount, and mms code.
Bluetooth works with hid, audio, smart watches, etc.
Wifi also works
Last I checked tethering works
Data seems to run a bit slower, but the browser probably needs tweaks.
 
Hey my bluetooth works flawlessly using your source, I'm about to work on my website and add a nightly section for my builds, but mind you, I will only build for os2sd, with a focus on virgin mobile.

Can you link to your site. I am excited about os2sd roms
 
Can you link to your site. I am excited about os2sd roms

Just updated my sig, I usually dev on androidtablets.net, and a bit on xda, but androidcentral seems to be the main place for the device. Remember that my builds are nightlys/weeklys and things may break, and since I haven't finished a proper recovery yet, you have few options for recovery. Warnings aside, I'm cleaning up my site now and linking in the build server.