• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Virgin Mobile] [BETA] [4.4.4] Cyanogenmod 11 Unofficial

daemon32, when you tested the ril files from the f6 cm11 rom, did you adjust the build.prop to reflect the changes?

Especially:
ro.telephony.ril_class=SamsungQualcommRIL
 
daemon32, when you tested the ril files from the f6 cm11 rom, did you adjust the build.prop to reflect the changes?

Especially:
ro.telephony.ril_class=SamsungQualcommRIL

:oops: WOW, stupid me assumes that all samsung rils are like the one that the replicant team found...
Calls back and forth work with that on GSM, yes...
 
Beautiful, I achieved LTE. Strange, i'm in a non LTE area. I need to do some testing. It both sends and receives phone calls and the sound is great. I'll upload what I have later for others to test. :)

daemon32, I pulled the files from the f6 cm11 rom and changed the build.prop line posted above.

# Radio from Samsung Serrano LTEXX
https://github.com/hroark13/lge_f6mt_aosp/blob/master/device/lge/f6mt/f6mt-vendor-blobs.mk

Oh, I don't know about those... I just used the ones from the LS KK ROM all day (on AT&T HSDPA/3G) and it was fine.

I'm assuming you already made the changes to test. Are you having service issues like i'm having?
I haven't tried LTE for very long, but my 3G and EDGE work fine.

I've got a speedtest now: http://i.imgur.com/xFvwQms.png

There might actually be an open source RIL available... https://gitorious.org/replicant/har...urce/73cde24d9690e2b9d4fb588fa8cc54fa50ef0b3e:
 
Last edited:
I was looking into that recently, all I saw was people saying it shouldn't make a difference. On a side note, I noticed ueventd.fx3s.rc isn't on the ramdisk, and it has some permission settings related to bluetooth and the radio, might help with some of the issues in those areas
 
I was looking into that recently, all I saw was people saying it shouldn't make a difference. On a side note, I noticed ueventd.fx3s.rc isn't on the ramdisk, and it has some permission settings related to bluetooth and the radio, might help with some of the issues in those areas
Thanks, I'll look into it. And the reason I asked about the hardware rng, is that I plan to use encryption on my phone when I leave the country and I was wondering if anyone else would benefit by me fixing it.
 
Oh, and I get this:
Code:
E/Cryptfs (  189): Orig filesystem overlaps crypto footer region.  Cannot encrypt in place.

I know how to fix it by hand, but what should I do to the ramdisk/rom/recovery to make the data partition smaller by default?

EDIT: Or maybe point it to /dev/block/platform/msm_sdcc.1/by-name/encrypt ?

EDIT2: fstab.qcom: encryptable=footer,length=-16384 -> encryptable=/dev/block/platform/msm_sdcc.1/by-name/encrypt

EDIT3: It works! And with qcrypto + qrngd, the encryption/decryption speed of /data is almost like native!
 
Last edited:
Adding the vibrator/tspdrv.c and BOARD_HAS_VIBRATOR_IMPLEMENTATION := ../../device/lge/fx3/vibrator/tspdrv.c in BoardConfig.mk makes the vibrator work instantly (I expected to have to work for that!)

EDIT: Trying to add widgets or apps to the homescreen causes surfaceflinger to hang (with the vibrator going full speed), but resume normally after a minute or two (without crashing), logcat isn't really showing anything interesting, so I wonder if it's a kernel issue with /dev/tspdrv

The current workaround is to disable vibrate on touch to add apps/widgets to the homescreen, as that works fine.
 
Last edited:
Adding the vibrator/tspdrv.c and BOARD_HAS_VIBRATOR_IMPLEMENTATION := ../../device/lge/fx3/vibrator/tspdrv.c in BoardConfig.mk makes the vibrator work instantly (I expected to have to work for that!)

EDIT: Trying to add widgets or apps to the homescreen causes surfaceflinger to hang (with the vibrator going full speed), but resume normally after a minute or two (without crashing), logcat isn't really showing anything interesting, so I wonder if it's a kernel issue with /dev/tspdrv

The current workaround is to disable vibrate on touch to add apps/widgets to the homescreen, as that works fine.

Cool on the vibration, that sucks its screwy though.
 
I replaced all stagefright files with the ones from the ls-kk rom and switched to the f6 kernel from compile. The f6 prebult kernel boots but doesn't work right.

I've had steady lte for about 10 minutes now and sms works in the default app.

hum, as i'm typing this, it dropped the network for a few seconds and then picked it back up. Looks like it's still unstable but it's more stable than what it was. I'll keep poking around.
 
I replaced all stagefright files with the ones from the ls-kk rom and switched to the f6 kernel from compile. The f6 prebult kernel boots but doesn't work right.

I've had steady lte for about 10 minutes now and sms works in the default app.

hum, as i'm typing this, it dropped the network for a few seconds and then picked it back up. Looks like it's still unstable but it's more stable than what it was. I'll keep poking around.
What is it that you're doing with the kernel?
 
Um.. khakis
slinyl47qxj9lkdgwguq.jpg


lol, using it. :p

No, seriously, I swapped our config file with theirs.
Meaning that i'm using their config file, I just renamed it to ours.
 
Last edited:
http://androidforums.com/threads/vi...rgin-mobile-apn-fix-wip-cm-aosp-4-4-x.840298/

Check this out, I was having issues receiving MMS messages until I flashed this, they come through now no problems. Might be able to incorporate these changes into the ROM. There's another one that adds visual voicemail and a modded Messenger, that might actually be what made it work, I'm not sure, I flashed both: http://forum.xda-developers.com/showthread.php?t=2199489

I had planned to bake that in with the next upload. I've been using it for a while now. As for the visual voicemail, I have used that in the past as well. That won't be included. But I did have planned to provide a link to it though. It's got issues.
 
Back
Top Bottom