Okay so first thing is first let this be known that this was not created by me. I'm just sharing along since I found a fix. All you have to do is Google up "universal boost mobile APN fix for d2lte" its a mod created by mopedryder. All credit goes to him. I haven't thanked cause I'm not on the thread. But here you go. This will fix the APN. Receive and send MMS and also fix "roaming indicator" to "Boost Mobile". Hope this works for everyone else like me.
Currently tried with C-Rom. Try it out and share your findings
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE! FLASH AT YOUR OWN RISK
All Thanks go to MOPEDRYDER
How to:
1) Flash rom of choice
2) Let Rom update and finish.
3) Reboot to recovery, MAKE BACKUP, Flash fix
(wipe dalvik/cache if you want)
4) Reboot and change settings in Hangouts.
5) Test it
Since the fix is meant for the LTE network from Hangouts APN's select "Sprint CdmaNai" There are two of them so select the one that works best. I usually use the first one.
So far what i have tried it on.
*CM11 - Working with fix and using hangouts.
*Paranoid Android - Working with fix and using Hangouts
*C-Rom - Working with fix and using Hangouts As of C-Rom v7 data won't work on xt1031 so MMS will not send. And no you can't do it over WiFi might as well send it through regular Hangouts.
*Slim Rom - Not working. Just hangs at (Sending)
*Lego Rom - Not working. Hangs at (sending)
*Gummy Rom - Working with fix. Using hangouts.
*AOSB (ProBAM) - Not working. Hangs at (sending)
*Omni Rom - Working with fix. Using hangouts.
ALTERNATE FIX
After flashing APN fix and that didn't work try this:
1) Download 8sms from the playstore: https://play.google.com/store/apps/details?id=com.thinkleft.eightyeightsms.mms
2) Go to settings in 8sms-> MMS settings-> add the following
MMSC: http://mm.myboostmobile.com
MMS Proxy: 68.28.31.7
MMS Port: 80
3) Test it. Should work just fine.
Try this fix before and after flashing the APN fix with ROM. This won't work on ProBAM ROM for some reason but feel free to prove me wrong.
Mopedryder actually replied and gave his own input and this is what he had to follow with that ks go to him one more time and also junkie2100
Haha! The things you find when one googles your profile. Small world indeed.
If you want a link to the folder I keep the fixes in use this: (copy to OP if wanted)
Boost LTE fix
R2 is basically a install binary update.
Here is some backstory / info on the 'fix':
The primary goal I set out to do was to get lte working on our phones with CM / AOSP ROMs(I have a G3 Virgin Mobile phone). Secondary, if able was to get MMS to work. MMS is still a challenge to say the least. In order to get LTE / MMS to work on Sprints network you need to identify yourself as Boost / Virgin on the Sprint network...with correct settings and at times credentials. The APN settings I made actually is a combo of both Sprint and Virgin/Boost settings.
Beyond the APN settings I made a simple bash script to 'find and replace', or if not found input the settings required. It also adds a eri.xml for the phone to identify itself as Boost / Virgin.
Getting MMS to work on LTE made me pull my hair out. Virgin mobile(Boost) working on Sprint networks when it comes to MMS messages is an over complicated issue caused the providers. When attempting to receive MMS on LTE networks with stock MMS or some 3rd party MMS apps it returns with a "HTTP error: Authorization Required". When trying it on 3G its no problem. Seems they required "Authorization" for MMS on LTE but not 3G - go figure. Hangouts basically works for all because the app itself doesn't use the phones APN settings. It tries (and does) to attain what carrier you are on and use its settings. In our case it will identify you are on the Sprint network and use those APN settings. Why don't we set our phones to the Sprint settings?...no LTE then.
For Samsung phones (My S3) TW ROMs use a system called chameleon to attain both LTE and SMS/MMS ability. The chameleon system will not work in AOSP / CM ROMs. The system "shows" itself as Virgin Mobile for phone/network but Sprint for MMS.
I have also found this fix doesn't seem to work on MIUI ROMs either. Haven't figured out why. For some reason every S3 sprint MIUI ROM wont even boot on my phone.
For my fix - if anyone wants to use / edit / repost it I say go for it. Open source at its finest. Best way to learn IMO is to reverse engineer something....just be careful :fingers-crossed:
As for the code if anyone wants to see it without unzipping:
The reason this is capable of flashing on multiple phones is partition specific blocks are not used.
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
Click to expand...
Click to collapse
Is used and not something like:
mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system");
Click to expand...
Click to collapse
Script I made for the build.prop edits:
#!/sbin/sh
#For APNs fix D2LTE Build ROMs
#Written by Moped_Ryder
#Update to handle universal lte builds
busybox mount -o remount,rw /system
cp /system/build.prop /system/build.prop-bak
if grep -q "ro.cdma.home.operator" "/system/build.prop"; then
sed -i 's/ro.cdma.home.operator.numeric.*$/ro.cdma.home.operator.numeric=311870/' /system/build.prop
sed -i 's/ro.cdma.home.operator.alpha.*$/ro.cdma.home.operator.alpha=Boost Mobile/' /system/build.prop
sed -i 's/ro.product.locale.region=.*$/ro.product.locale.region=US/' /system/build.prop
sed -i 's/gsm.sim.operator.alpha.*$/gsm.sim.operator.alpha=Boost Mobile/' /system/build.prop
sed -i 's/gsm.sim.operator.numeric.*$/gsm.sim.operator.numeric=311870/' /system/build.prop
sed -i 's/gsm.operator.alpha.*$/gsm.operator.alpha=Boost Mobile/' /system/build.prop
sed -i 's/gsm.operator.numeric.*$/gsm.operator.numeric=311870/' /system/build.prop
sed -i 's/gsm.sim.operator.iso-country=.*$/gsm.sim.operator.iso-country =US/' /system/build.prop
sed -i 's/gsm.operator.iso-country=.*$/gsm.operator.iso-country=US/' /system/build.prop
sed -i 's/ro.telephony.default_network=.*$/ro.telephony.default_network=8/' /system/build.prop
else
echo "####Adding the Boost Mobile APN fixes####" >> /system/build.prop
echo "ro.cdma.home.operator.numeric=311870" >> /system/build.prop
echo "ro.cdma.home.operator.alpha=Boost Mobile" >> /system/build.prop
echo "ro.telephony.default_network=8" >> /system/build.prop
echo "telephony.slteOnCdmaDevice=1" >> /system/build.prop
sed -i 's/ro.product.locale.region=.*$/ro.product.locale.region=US/' /system/build.prop
sed -i 's/gsm.sim.operator.iso-country=.*$/gsm.sim.operator.iso-country =US/' /system/build.prop
sed -i 's/gsm.operator.iso-country=.*$/gsm.operator.iso-country=US/' /system/build.prop
fi
if grep -q "moped_ryder" "/system/build.prop"; then
echo "its there"
else
echo "#moped_ryder carrier edit completed" >> /system/build.prop
fi
Click to expand...
Click to collapse
Like I said nothing too complicated
The APN Settings used are:
Credit where due > My work may not have been possible without junkie2100 from android forums. You ever see him - give him a like / thanks please :good:
...as said in the OP flash at won risk. Sorry so long
Thanks for sharing. I'm gonna give it a shot tonight after backing everything up.
Sent from my XT1031 using Tapatalk
So I did flash the fix and my phone shows up as Boost Mobile for my network, but it still won't send MMS. Which APN did you select since there's like 10 of em?
Sent from my Moto G using Tapatalk
vitokes said:
Okay so first thing is first let this be known that this was not created by me. I'm just sharing along since I found a fix. All you have to do is Google up "universal boost mobile APN fix for d2lte" its a mod created by mopedryder. All credit goes to him. I haven't thanked cause I'm not on the thread. But here you go. This will fix the APN. Receive and send MMS and also fix "roaming indicator" to "Boost Mobile". Hour this works for everyone else like me.
Currently tried with C-Rom. Try it out and share your findings.
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
Just tried this with Lego ROM...did you have to clean install for it to work? I still can't access my APN settings. It says Boost for the service now instead of the Roaming Indicator message but still no MMS support. I know you gave the link for a different thread with the methods for the fix but can you give detail on the exact steps that you did for it to work on the Moto G please? It would be greatly appreciated, MMS is the last thing I'm missing, I'm loving everything else about my current ROM and really don't wanna go back to stock.
ricola1989 said:
So I did flash the fix and my phone shows up as Boost Mobile for my network, but it still won't send MMS. Which APN did you select since there's like 10 of em?
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
Alright so I've been going from ROM to ROM to see which one plays nice. My first was c-rom and that worked. Then I tried pa and that also worked. Anyways the apn's only go to hangouts since that's what it's meant for. Now I'm using Lego ROM and got some reason it won't send the pictures through it. The APN I pick from hangouts is SprintCdmanai.
Sent from my Moto G using Tapatalk
hhill13 said:
Just tried this with Lego ROM...did you have to clean install for it to work? I still can't access my APN settings. It says Boost for the service now instead of the Roaming Indicator message but still no MMS support. I know you gave the link for a different thread with the methods for the fix but can you give detail on the exact steps that you did for it to work on the Moto G please? It would be greatly appreciated, MMS is the last thing I'm missing, I'm loving everything else about my current ROM and really don't wanna go back to stock.
Click to expand...
Click to collapse
I was currently testing this with Lego ROM. And I can't seam to get it to send MMS either. It works with the previous ROMs I've tried.
1. Flash whatever ROM you are going to use.
2. Complete your setup. Let everything update.
3. Flash APN fix, boot when done.
The APN settings only show up in hangouts.
Sent from my Moto G using Tapatalk
So I was on Lego ROM and it wouldn't work. I don't know why. I did notice on Lego ROM you can't access the APN settings in settings>mobile network>APN settings. It's just greyed out. So I switched back to latest pa and you can access APN settings through mobile network. And I'm now sending and receiving
Sent from my Moto G using Tapatalk
vitokes said:
So I was on Lego ROM and it wouldn't work. I don't know why. I did notice on Lego ROM you can't access the APN settings in settings>mobile network>APN settings. It's just greyed out. So I switched back to latest pa and you can access APN settings through mobile network. And I'm now sending and receiving
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
Good to know, I will jump back over to the Lego thread and see if the OP has any input on the issue.
Sent from my Moto G using XDA Free mobile app
I started out with a clean install of Lego ROM when I flashed this fix. I, too, an not able to send/receive MMS or pictures. I'm going to check the Lego thread and see what the OP SARS @vitokes- have you tried this fix on Slim, that's what Lego is mainly based on....
I do think that access to the APN settings in the actual Settings menu has something to do with it. Also, it took me a bit to get the ROM to give 3g since it won't stick if you select Preferred Network in the menu. You actually have to go into the Phone hidden menu info from the dialer (*#*#4636#*#*).
@ricola1989 I haven't had a chance to test on slim. I will after work though.
Sent from my Moto G using Tapatalk
trying on slim now, give me a few....
Andromendous said:
trying on slim now, give me a few....
Click to expand...
Click to collapse
Just tried on slim and it only hangs. It must be something to do with the ROM. Anyways I updated the thread wit how to's and also what ROM works and doesn't.
IF you want me to test more just let me know and I'll check them out if you would like.
vitokes said:
Just tried on slim and it only hangs. It must be something to do with the ROM. Anyways I updated the thread wit how to's and also what ROM works and doesn't.
IF you want me to test more just let me know and I'll check them out if you would like.
Click to expand...
Click to collapse
what do you mean it "hangs", it says boost mobile now. but when i tryed an mms it said "insert sim to send mms". i tryed a couple different apns, but just the default and the one mentioned a few posts back
Andromendous said:
what do you mean it "hangs", it says boost mobile now. but when i tryed an mms it said "insert sim to send mms". i tryed a couple different apns, but just the default and the one mentioned a few posts back
Click to expand...
Click to collapse
By "hangs"
I mean it hangs at just sending. Doesn't send an MMS. Or receive. And then once left for a minute or 2 it says it can't be sent. Touch to retry. I think the problem is slim ROM in general..
Edit: also the only APN's you can use from the list are the bottom 2. They are meant for CDMA network.
Sent from my Moto G using Tapatalk
Having the hanging problem I'm c-rom tried both cdma
Sent from my Moto G using Tapatalk
You are using hangouts I assume? Try "reset to default" and then change to the other apns.
Sent from my Moto G using Tapatalk
Bstrong9211 said:
Having the hanging problem I'm c-rom tried both cdma
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
Also try to add your own APN settings just like the picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Moto G using Tapatalk
That seems to have done the trick. Thanks a lot!
Sent from my Moto G using Tapatalk
Bstrong9211 said:
That seems to have done the trick. Thanks a lot!
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
Glad I could help! Just give me a simple thanks and all credit goes to mopedryder.
Sent from my Moto G using Tapatalk
I'm surprised this isn't more popular. It should be added to the roll up thread.
Sent from my Moto G using Tapatalk
Related
MMS Fix for Epics on Alternative Carriers
Works for ICS only, will not work on earlier versions of android.
Installation instructions
Please locate your carrier and ROM from the list below.
Download the fix
Copy to your sd card
Flash from recovery - this can and should be flashed over an existing installation.
Thanks!
Don't forget to say thanks to the devs and testers.
Alias8818: This wonderful fix is brought to you by his tireless efforts.
mucus_android, brian117: Guinea Pigs
Downloads
Further preconfigured fixes will be added as they become available. If you do not see your fix listed, please read the guide below.
AOKP ROMs
Virgin Mobile - AOKP build 34 | mirror
MMSfix.zip only provided by Alias8818
How-To Guide
Guide on how to get MMS working an ALL carriers.
Step 1:
Install MMSfix
DL mmsfix.zip
Load onto SD card
Flash via recovery
Boot to system
Code:
Important notes
This will add several APN lines to your device, and the different APNs will become active as you change your build.prop
This deletes the telephony.db, allowing the system to rebuild it based on the new APNs
Step 2:
Edit build.prop
Use a root file explorer (I use ES File Explorer)
Make sure to mount system as writable, and that the File Browser is capable of root access.
Navigate to /system/build.prop
Open it with any onboard text editor (I used ES's text editor)
There will be two lines you have to edit and two new lines you should add
Find the following lines, they should be right next to one another
Code:
ro.cdma.home.operator.numeric=310120
ro.cdma.home.operator.alpha=Sprint
Edit them to read
Code:
ro.cdma.home.operator.numeric=Your Carrier's Numeric Identifier* please see attached for list of numeric values
ro.cdma.home.operator.alpha=Your Carrier's Name* please see attached list for list of names
Add the following two lines
Code:
gsm.operator.alpha=Your Carrier's Name* please see attached list for list of names
gsm.operator.numeric=Your Carrier's Numeric Identifier* please see attached for list of numeric values
Save the changes and reboot your phone.
Step 3:
Test mms
Make sure mms is working, if it is - You're done!
If mms is not working, there is most likely an error in the entries to the build.prop
Numeric and Alpha values
Boost
Code:
ro.cdma.home.operator.numeric=50502
ro.cdma.home.operator.alpha=Boost MMS
gsm.operator.alpha=Boost MMS
gsm.operator.numeric=50502
Cricket
Code:
ro.cdma.home.operator.numeric=31016
ro.cdma.home.operator.alpha=Cricket
gsm.operator.alpha=Cricket
gsm.operator.numeric=31016
Metro PCS
Code:
ro.cdma.home.operator.numeric=310027
ro.cdma.home.operator.alpha=Cricket
gsm.operator.alpha=Cricket
gsm.operator.numeric=310027
Sprint (do you really need this?)
Code:
ro.cdma.home.operator.numeric=310120
ro.cdma.home.operator.alpha=Sprint
gsm.operator.alpha=Sprint
gsm.operator.numeric=310120
Verizon
Code:
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
gsm.operator.alpha=Verizon
gsm.operator.numeric=310004
Virgin Mobile US
Code:
ro.cdma.home.operator.numeric=311490
ro.cdma.home.operator.alpha=Virgin Mobile US
gsm.operator.alpha=Virgin Mobile US
gsm.operator.numeric=311490
Thank you for reading this guide.
Further reading
brooksyx's thread on MMS fix for virgin mobile.
He address the issue differently, and it did not completely work for me.
The issue is likely related to the APNs.
But please read his thread and check out the zip file he includes, he goes about the setup differently
http://forum.xda-developers.com/showthread.php?t=1491189
Pics!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That was so worth it.
Thanks for your patience too, mucus.
Does MMSfix.zip work for all roms, or is it ics-only? I don't mind editing my build.prop but i'm not clear on what the MMSfix zip does. I am running the lastest CM7 rc1 update1
antipasta said:
Does MMSfix.zip work for all roms, or is it ics-only? I don't mind editing my build.prop but i'm not clear on what the MMSfix zip does. I am running the lastest CM7 rc1 update1
Click to expand...
Click to collapse
Quote from OP regarding mmsfix
Important notes
This will add several APN lines to your device, and the different APNs will become active as you change your build.prop
This deletes the telephony.db, allowing the system to rebuild it based on the new APNs
Click to expand...
Click to collapse
This will not work on cm7
I tested this on CM9 Cricket Build, And it works. Thanks for the useful information.
AnDrOpErZ said:
I tested this on CM9 Cricket Build, And it works. Thanks for the useful information.
Click to expand...
Click to collapse
Thank you for the information!
I am glad that it works for you!
Works on cricket for receiving, can't send though oddly enough.
explosivequack said:
Works on cricket for receiving, can't send though oddly enough.
Click to expand...
Click to collapse
are you sure you entered your information correctly? and are you using stock mms.apk?
mucus_android said:
are you sure you entered your information correctly? and are you using stock mms.apk?
Click to expand...
Click to collapse
I'm pretty sure I entered it correctly and I'm using a themed mms.apk its the b34 one but I'll go back to stock one now see if that changes it
Edit: same thing although I sent a picture to my gf and she got part of it but it never actually said it sent. But receiving is more than I've ever got from any mms fix so thanks
1 more edit: redownloaded and installed and it works now
explosivequack said:
I'm pretty sure I entered it correctly and I'm using a themed mms.apk its the b34 one but I'll go back to stock one now see if that changes it
Edit: same thing although I sent a picture to my gf and she got part of it but it never actually said it sent. But receiving is more than I've ever got from any mms fix so thanks
1 more edit: redownloaded and installed and it works now
Click to expand...
Click to collapse
I knew you could do it!
Step 2:
Edit build.prop
Use a root file explorer (I use ES File Explorer)
Make sure to mount system as writable, and that the File Browser is capable of root access.
Navigate to /system/build.prop
Open it with any onboard text editor (I used ES's text editor)
There will be two lines you have to edit and two new lines you should add
Find the following lines, they should be right next to one another
Code:
ro.cdma.home.operator.numeric=310120
ro.cdma.home.operator.alpha=Sprint
Edit them to read
Code:
ro.cdma.home.operator.numeric=Your Carrier's Numeric Identifier* please see attached for list of numeric values
ro.cdma.home.operator.alpha=Your Carrier's Name* please see attached list for list of names
Add the following two lines
Code:
gsm.operator.alpha=Your Carrier's Numeric Identifier* please see attached for list of numeric values
gsm.operator.numeric=Your Carrier's Name* please see attached list for list of names
Save the changes and reboot your phone.
I think the OP made a mistake here. He put that the gms.operator.alpha= carrier's numeric identifier, but it's suppose to be the carrier's name and vice versa!
Glad this is working for other roms as well. My main focus was getting MMS working for CM9 on the OG epic and then the E4GT (my current phone) on virgin mobile. Since I first found the fix the correct mms cdmasmsdispatcher has been added to the both the CM9 and AOKP upstreams so the the only necessary changes are to the build.prop so that the correct apn values are used. The only other things needed to do is delete the telephony.db and the telephony.db-journal in data so that the correct apn settings are written on the next reboot.
brooksyx said:
Glad this is working for other roms as well. My main focus was getting MMS working for CM9 on the OG epic and then the E4GT (my current phone) on virgin mobile. Since I first found the fix the correct mms cdmasmsdispatcher has been added to the both the CM9 and AOKP upstreams so the the only necessary changes are to the build.prop so that the correct apn values are used. The only other things needed to do is delete the telephony.db and the telephony.db-journal in data so that the correct apn settings are written on the next reboot.
Click to expand...
Click to collapse
You are absolutely right. Thanks for pointing that out!
I should mention though, the zip file itself takes care of that.
So what's happening is the mmsfix.zip is writing new apn settings and deleting the .db files.
If you check your apn settings after flashing the zip you'll notice it appears blank.
This is fixed after writing the the changes to the build.prop
lokoz89 said:
I think the OP made a mistake here. He put that the gms.operator.alpha= carrier's numeric identifier, but it's suppose to be the carrier's name and vice versa!
Click to expand...
Click to collapse
>_< oh yeah.... you seem to be right, thanks for pointing it out!
mucus_android said:
You are absolutely right. Thanks for pointing that out!
I should mention though, the zip file itself takes care of that.
So what's happening is the mmsfix.zip is writing new apn settings and deleting the .db files.
If you check your apn settings after flashing the zip you'll notice it appears blank.
This is fixed after writing the the changes to the build.prop
Click to expand...
Click to collapse
That's what my flasherzip does as well except my flasherzip uses a special Linux script to get the job done. If you open the script you should see what I mean. I can guarantee that my fix works for cm9 on the epic and e4gt, and aokp for the e4gt. I assume it works for aokp on the og epic but I can't test that. As for the apns-conf.xml you shouldn't have to make any changes to it. The correct values are already in there, editing the build.prop to the correct values and delete the telephony.db will set the correct values to data after a reboot.
Sent from my SPH-D710 using XDA
Specifically with my builds, up until now, I've only been including Sprint's APN.
I suppose he could specifically specify ROM's and the builds that would require it from AOKP... But the ease of making sure its in there, that step is required.
I do like the script that was implemented, warren had shown that to me.
It will honestly ease updates for the ROMs.
Just figured I'd chime in since I've been building AOKP for the OG Epic.
Alias8818 said:
Specifically with my builds, up until now, I've only been including Sprint's APN.
I suppose he could specifically specify ROM's and the builds that would require it from AOKP... But the ease of making sure its in there, that step is required.
I do like the script that was implemented, warren had shown that to me.
It will honestly ease updates for the ROMs.
Just figured I'd chime in since I've been building AOKP for the OG Epic.
Click to expand...
Click to collapse
Okay. I know the apns-conf.xml file in CM9 and aokp for the epic touch work for virgin mobile. I can't comment on boost mobile or others but I did see those values in there as well. Maybe you could nab one of those files.
I have my own special apns-conf.xml file I use for virgin mobile but I alwas scrub down a rom and add my own tweaks in before I flash it to my phone.
Hello folks,
I followed the steps -- flashed the MMSfix.zip and rebooted; then updated the build.prop in /system/ with the required cricket information (since I'm on Cricket). It's not working.
Do I need to be using a different SMS/MMS application aside from the default Messaging one that is included with my install of Android? Will not download message sent from my sister about 4 days ago. Trying to send now, but doubting that will work. Do I need to actually update the APN's inside my phone to contain my login information, etc?
I am currently on CM9 Beta 2...
Thoughts?
Thanks!
where can i get those build.prop values ? cause my carrier isn't listed
on the other hand, can i add my own carrier in the apns-conf.xml ?
my carrier is indonesian smart-telecom
terinfire said:
Hello folks,
I followed the steps -- flashed the MMSfix.zip and rebooted; then updated the build.prop in /system/ with the required cricket information (since I'm on Cricket). It's not working.
Do I need to be using a different SMS/MMS application aside from the default Messaging one that is included with my install of Android? Will not download message sent from my sister about 4 days ago. Trying to send now, but doubting that will work. Do I need to actually update the APN's inside my phone to contain my login information, etc?
I am currently on CM9 Beta 2...
Thoughts?
Thanks!
Click to expand...
Click to collapse
If you search around this dev section I think there was a thread on getting mms to run on cricket. No offense to the op but his post seems pretty incomplete with what he stated in the thread title.
Sent from my SPH-D710 using XDA
These builds are unofficial, unsupported by the LiquidSmooth team. Do not file bug reports to the Liquidsmooth devs -- instead please post them in this thread.
What is LiquidSmooth? Find more information here: Official LiquidSmooth G+ Community
Installation instructions:
Backup what is precious to you
Wipe system, data and cache
Flash ROM (link below)
Flash gapps (link below)
Reboot and wait for welcome screen
Downloads:
Liquid-JB-v2.37-UNOFFICIAL-20131106-ovation.zip - 105.01 MB
Standard Gapps: Goo.im - gapps-jb-20130813-signed.zip
Slim Gapps (compatible with "Dark Liquid" switch): Slim Gapps download page
Banks's basic Gapps (absolute minimal gapps install): XDA thread
Known issues/bugs
Text strings in the UI are a bit wonky, especially those for Wi-Fi and Bluetooth (i.e. "deny" instead of "connect" when adding a new Wi-Fi network)
Bluetooth tethering does not work. Fixed in 2013-11-06
Potentially there can be some rotation bugs. LMK if you identify any
There is not Tablet UI available, and auto-patcher does not support LiquidSmooth at this point
Generic screenshot showing LS features
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Interesting...
Sent from my Nook HD+ using xda app-developers app
It looks nice is trim disabled?
Sent from my PC36100 using xda app-developers app
jpisini said:
It looks nice is trim disabled?
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
+1.... would like to try if it's disabled (I have the chip that can be potentially bricked by trim).
320flyboy320 said:
+1.... would like to try if it's disabled (I have the chip that can be potentially bricked by trim).
Click to expand...
Click to collapse
Trim is disabled.
TY!! but wifi doesn't work for me
------------------------------------------------------------
oh, it woks after fixing permission @twrp. TY again!
Looks good. I will try to flash this this weekend.
Sent from my LG-LS855 using Tapatalk 2
Just noticed on the settings screen, and if you tap on BATTERY, settings crashes. Other than that, it's working good so far...:good:
320flyboy320 said:
Just noticed on the settings screen, and if you tap on BATTERY, settings crashes. Other than that, it's working good so far...:good:
Click to expand...
Click to collapse
flyboy,
As the other poster mentioned, I too can't get WiFi to work. How did you get past the initial start up settings procedure? Setup won't let me skip logging into a network so I'm stuck.
smithmal
Edit - figured it out. When setting up tablet on the "Wifi Select" screen, for some reason when adding a network, network settings cannot be saved (seeing this when manually adding a SSID as I have mine hidden). Click "Skip" and then click "Cancel" and then setup will finish.
Still cannot manually add my hidden SSID though so I can't connect to my WiFi network.
Ya WiFi is for sure screwed up. I did manage to add my hidden SSID after trying a few times. Although as with the APPS in SETTINGS the button names seem to be messed up. If I try to uninstall an app, I only get the option to either INSTALL or SDCARD...bit weird...:silly:
Could you please in the next release, switch the release flag here to false, this makes it so the build is Unofficial.
I really like the boot animation on the ROM!
Sent from my LG-LS855 using Tapatalk 2
320flyboy320 said:
Ya WiFi is for sure screwed up. I did manage to add my hidden SSID after trying a few times. Although as with the APPS in SETTINGS the button names seem to be messed up. If I try to uninstall an app, I only get the option to either INSTALL or SDCARD...bit weird...:silly:
Click to expand...
Click to collapse
I'll have a look at these issues (starting with Wi-Fi) and try to fix them next week.
deadman96385 said:
Could you please in the next release, switch the release flag here to false, this makes it so the build is Unofficial.
Click to expand...
Click to collapse
Will do.
jisoo said:
I'll have a look at these issues (starting with Wi-Fi) and try to fix them next week.
Will do.
Click to expand...
Click to collapse
I. Noticed something odd with the WiFi this weekend. I flashed the ROM on Friday,, and then yesterday I messed something up while restoring some stuff so I did another clean flash. This time I used the "minimal gapps" and when I tried setting up, it would not even show any of the 4or 5 access points nearby. And nothing I tried would produce any results.
So,, I went back and flashed the AIO gapps and then all the AP's showed up and I was able to log on to it.
Just thought I'd share. I think it's kinda odd that the gapps would make a difference in being able to see wifi.
Sent from my Nook HD+ with unofficial LiquidSmooth on emmc using Tapatalk 4
bpaulien said:
I. Noticed something odd with the WiFi this weekend. I flashed the ROM on Friday,, and then yesterday I messed something up while restoring some stuff so I did another clean flash. This time I used the "minimal gapps" and when I tried setting up, it would not even show any of the 4or 5 access points nearby. And nothing I tried would produce any results.
So,, I went back and flashed the AIO gapps and then all the AP's showed up and I was able to log on to it.
Just thought I'd share. I think it's kinda odd that the gapps would make a difference in being able to see wifi.
Sent from my Nook HD+ with unofficial LiquidSmooth on emmc using Tapatalk 4
Click to expand...
Click to collapse
Interesting. Are you refering to the AIO gapps listed for Slimbean (see here) or full CM listed 4.3 gapps (08/13/2013 gapps). I've tried this with the Slimbean AIO gapps and it didn't work (re-flashed it a couple time to make sure). I wonder if going from minimal gapps to AIO gapps is the trick?
Also, after getting all your APs to show up is LiquidSmooth supporting BT? As I recalled BT worked, I just couldn't connect to my AP.
Edit: Tried installing with minimal first and then re-flash AIO and I can't save password for my AP. Once password is entered I only have two options: "Failed to save network" and "Deny"
smithmal
Guys,
Sorry about the WiFi problems. I tested this build with no gapps and it worked ok for me, so I didn't know about the issues.
I'm a bit busy at work right now, but I will get back to this at the end of the week and try to put up a better working build.
I have no issues with WiFi
Sent from my BN NookHD+ using XDA Premium 4 mobile app
smithmal said:
Interesting. Are you refering to the AIO gapps listed for Slimbean (see here) or full CM listed 4.3 gapps (08/13/2013 gapps). I've tried this with the Slimbean AIO gapps and it didn't work (re-flashed it a couple time to make sure). I wonder if going from minimal gapps to AIO gapps is the trick?
Also, after getting all your APs to show up is LiquidSmooth supporting BT? As I recalled BT worked, I just couldn't connect to my AP.
Edit: Tried installing with minimal first and then re-flash AIO and I can't save password for my AP. Once password is entered I only have two options: "Failed to save network" and "Deny"
smithmal
Click to expand...
Click to collapse
I was referring to the SlimBean AIO.
The very first time I flashed it, I used the one (can't remember its name) that pulls up the interface where you can pick and choose the gapps you want to install. That worked for me.
Then when I re-flashed (clean) I just wanted to get going, and didn't really care what was on it, so did the minimal gapps. That's when I couldn't see any WiFi Access Points. But since I knew I had gotten access to WiFi the first time, I figured there had to be something different between my 2 flashes. But not wanting to go through and select things again, I just flashed the AIO gapps over everything. That time WiFi worked.
I can't answer about BT. I'm not using any BT connections with my Nook at this time.
And as to your edit, I think I got some kind of error message too, but when I got to the next part, where you log into your google account, it had access and everything worked. So despite the error message regarding WiFi, I was able to continue, and haven't really had any WiFi issues with it.
So I've uploaded a new build for v2.37.
I tested Wi-Fi, and although the text strings in the UI are wrong (for instance it says "deny" where it should say "connect"), Wi-Fi and BT tethering now work as far as I can test.
I also merged all of the bug fixes and cleanups the LiquidSmooth team has added since the last build, but these are quite minor. There does not seem to be any new features coming into the 4.3/JB3 branch. This is the case for more or less all ROMs, as everyone is busy rebasing and merging functionality into the 4.4 branches.
The new build is also properly marked as unofficial, as requested by the LiquidSmooth devs.
jisoo,
Thanks for this ROM, your work porting this to the HD+ is much appreciated. I loaded this up and took it for a spin earlier today. WiFi connection is still a bit dicey. It took me three or four times before it would connect (using WPA2 security on my network), but the tablet did finally connect. It seemed my signal strength was a bit lower than other ROMs, but I don't have any hard data to support that.
The ROM seemed snappy enough (coming from the Slimbean ROM which is very responsive). BT turned on when selecting it, but I haven't gotten a chance to test it yet so that's on my list.
I will do some more tests on DL speeds/UL speeds/WiFi strength later tonight and let you know.
smithmal
I made an updated flashable VM fix from V.R2 of Mopedryder's version of the fix http://androidforums.com/threads/vi...rgin-mobile-apn-fix-wip-cm-aosp-4-4-x.840298/. I wrote a new updater-script to accommodate our new apns-conf. This also deletes telephony databases and updates the build.prop somewhat accordingly,carrier brand is also correctly set as VM also. I recommended using this on a clean flash of your ROM or after a factory reset, let me know if you get LTE,text and calls working and which ROM and kernel you are using and we can add or change stuff. This should work with CM 12 & 13
Take a backup first via twrp before using this. I am not responsible for any damage you cause on your end!
How to install:
Download to Ext SD Card
Reboot into recovery
Either Clean Flash with ROM &Gapps
Or
Flash and then
Factory Reset (Dalvik,Cache,Data)
Reboot
LTE should immediately turn on
texts and MMS should now work, textra helps if you get problems sending pics.
https://drive.google.com/file/d/0Bz99NuhE3XwmRnRTWW9SejY2MlE/view?usp=docslist_api
Sent from my Virgin Mobile Moto E via CM 13
Thanks man, I was actually working on this, used the other thread to manually get everything working, once I saw it worked I was working on a script to do it via flash like this, I just got the device to have a decent phone while my Nexus 6 is getting rma'd, must say I'm super surprised at this little $40 phone
Sent from my XT1526 using Tapatalk
soupysoup said:
Thanks man, I was actually working on this, used the other thread to manually get everything working, once I saw it worked I was working on a script to do it via flash like this, I just got the device to have a decent phone while my Nexus 6 is getting rma'd, must say I'm super surprised at this little $40 phone
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
This is my favorite phone I've had so far, I broke the screen on my old one and bought another one because I wanted to see LTE work on the custom ROMs so badly. @Starklyraving and @hydroman202 have been so awesome working all along to get this fixed. Cheers guys!
Sent from my Virgin Mobile Moto E via CM 13
Thanks
I spent some time this afternoon throwing together an Aroma flashable zip to activate LTE on Boost, FreedomPop, Sprint, Ting, and Virgin Mobile. It's a really simple setup, but I've hit a hangup getting build.prop to edit in recovery mode.
Is your zip actually patching build.prop or is it just acting like it does?
Mind you, I've had LTE running fine with no changes whatsoever to build.prop so I may just cut those patches out.
I double checked the prop.sh file and I made a few edits to fix mms but I'm not finished yet,I'll upload that tomorrow but to answer you the zip also clears the correct databases and replaces the eri and apns_conf file and changes the numeric in build.prop and carrier branding
Sent from my Virgin Mobile Moto E via CM 13
Sands207 said:
I double checked the prop.sh file and I made a few edits to fix mms but I'm not finished yet,I'll upload that tomorrow but to answer you the zip also clears the correct databases and replaces the eri and apns_conf file and changes the numeric in build.prop and carrier branding
Sent from my Virgin Mobile Moto E via CM 13
Click to expand...
Click to collapse
I don't really understand what is the difference with https://github.com/Motorola-Cyanoge...mmit/8a6f577c866c3979d758bbe48d3bb0565fd94a1d
unless at that time the values that were provided were wrong, in the apns-conf.xml and eri.xml were wrong, this patch used to do the same thing. (I actually didn't make the diff for now)
Update the getprop values, copy apns and eri to the right place.
I some of you guys want to send me the fix for all the providers. I'll make it by default in the "CAF" build.
CM13 will most probably won't get the fix.
Sands207 said:
This is my favorite phone I've had so far, I broke the screen on my old one and bought another one because I wanted to see LTE work on the custom ROMs so badly. @Starklyraving and @hydroman202 have been so awesome working all along to get this fixed. Cheers guys!
Sent from my Virgin Mobile Moto E via CM 13
Click to expand...
Click to collapse
I will say I'm super impressed with moto for this device, I mean come on, I paid $40 for this thing, it performs almost as well as my Nexus 5, I just wish it had a little bit bigger screen and some more storage, but I mean for $40 really, I had very low expectations for this phone, it was just something to get me by until me N6 comes back from RMA, but after using it for a week I'm impressed, I'm actually working on 6.0 for it too, bcuz I know it can run it and I think it will improve on an already amazing device, good stuff moto, after my Nexus 6 I wasn't a fan of moto, but this restored my trust in them a great deal....
Sent from my XT1526 using Tapatalk
scritch007 said:
I don't really understand what is the difference with https://github.com/Motorola-Cyanoge...mmit/8a6f577c866c3979d758bbe48d3bb0565fd94a1d
unless at that time the values that were provided were wrong, in the apns-conf.xml and eri.xml were wrong, this patch used to do the same thing. (I actually didn't make the diff for now)
Update the getprop values, copy apns and eri to the right place.
I some of you guys want to send me the fix for all the providers. I'll make it by default in the "CAF" build.
CM13 will most probably won't get the fix.
Click to expand...
Click to collapse
The main difference is in apns-conf.xml. eri.xml is purely cosmetic and LTE works perfectly without patching build.prop. I'm currently pulling the build.prop patching from my zip and updating the various apns-conf.xml files with the most current information. I'll upload in a bit.
scritch007 said:
I don't really understand what is the difference with https://github.com/Motorola-Cyanoge...mmit/8a6f577c866c3979d758bbe48d3bb0565fd94a1d
unless at that time the values that were provided were wrong, in the apns-conf.xml and eri.xml were wrong, this patch used to do the same thing. (I actually didn't make the diff for now)
Update the getprop values, copy apns and eri to the right place.
I some of you guys want to send me the fix for all the providers. I'll make it by default in the "CAF" build.
CM13 will most probably won't get the fix.
Click to expand...
Click to collapse
@scritch007 Thanks, if you could include it that would great. The difference is on lines 23 + 24 of prebuilt/system/etc/cdma/virgin/apns-conf.xml the value for LTE for Virgin Mobile at least in the US I believe is n.ij.ispsn instead of v.vmu.ispsn which is used for 3g data that is there now. I am guessing with the introduction of spark network the value was changed. The prop fix just sets our carrier branding correctly as Virgin Mobile in settings>sim info and in quick settings because by default without the fix we are listed as using Boost Mobile as our carrier and in quick settings it will just read "roaming indicator off" and can only use 3g. I am using the fix in CM 13 right now. The only difference between flashing the fix with CM 12.1 and 13 and probably CAF too is that APN's can be viewed,added,edited etc in CM 12.1 and in CM 13 APN's are not visable but the fix still works by replacing the correct files and prop edits.
The carrier information in SIM status is taken from eri.xml. I get no difference in functionality between patched and unpatched build.prop files. It may have once been necessary, but I think whatever problems those build.prop patches solved have been resolved.
deega said:
The carrier information in SIM status is taken from eri.xml. I get no difference in functionality between patched and unpatched build.prop files. It may have once been necessary, but I think whatever problems those build.prop patches solved have been resolved.
Click to expand...
Click to collapse
OK great
Sent from my Virgin Mobile Moto E via CM 13
scritch007 said:
I don't really understand what is the difference with https://github.com/Motorola-Cyanoge...mmit/8a6f577c866c3979d758bbe48d3bb0565fd94a1d
unless at that time the values that were provided were wrong, in the apns-conf.xml and eri.xml were wrong, this patch used to do the same thing. (I actually didn't make the diff for now)
Update the getprop values, copy apns and eri to the right place.
I some of you guys want to send me the fix for all the providers. I'll make it by default in the "CAF" build.
CM13 will most probably won't get the fix.
Click to expand...
Click to collapse
I just looked a bit deeper into the code you linked. (specifically init_surnia.c) It's setting the CDMA values based on the value of ro.boot.fsg-id, expecting virgin or sprint else it's boost. A getprop ro.boot.fsg-id returns nothing on my CAF 0.10 surnia. getprop ro.cdma.home.operator.numeric returns 311870 (boost). Expected behavior would return the following in my case:
ro.boot.fsg-id=virgin
ro.cdma.home.operator.numeric=311490
If I understand the structure of APN entries correctly, getting this resolved would make it possible to include the APNs in the default apns-conf.xml.
I'm not sure how ro.boot.fsg-id is derived, but adding ro.boot.fsg-id=virgin to build.prop doesn't alter the above behavior.
deega said:
I just looked a bit deeper into the code you linked. (specifically init_surnia.c) It's setting the CDMA values based on the value of ro.boot.fsg-id, expecting virgin or sprint else it's boost. A getprop ro.boot.fsg-id returns nothing on my CAF 0.10 surnia. getprop ro.cdma.home.operator.numeric returns 311870 (boost). Expected behavior would return the following in my case:
ro.boot.fsg-id=virgin
ro.cdma.home.operator.numeric=311490
If I understand the structure of APN entries correctly, getting this resolved would make it possible to include the APNs in the default apns-conf.xml.
I'm not sure how ro.boot.fsg-id is derived, but adding ro.boot.fsg-id=virgin to build.prop doesn't alter the above behavior.
Click to expand...
Click to collapse
Yes this is taken from the CDMA test build I made. I had asked people to set the fsg-id to the correct value. This can be done thanks to fastboot:
Code:
fastboot oem config fsg-id virgin
This wasn't added into CM.
Something like that would certainly help! If the CDMA properties were set based on a user-selectable carrier then it would solve a lot of headache with the apns-conf.xml files. We know the appropriate APNs for Boost, Sprint, and Virgin. It would be nice to have them folded into the default apns-conf.xml.
deega said:
Something like that would certainly help! If the CDMA properties were set based on a user-selectable carrier then it would solve a lot of headache with the apns-conf.xml files. We know the appropriate APNs for Boost, Sprint, and Virgin. It would be nice to have them folded into the default apns-conf.xml.
Click to expand...
Click to collapse
It definitely would. I don't understand why this isn't already fixed in CM 12.1, it also should be listed as an issue in the wiki but it isn't.
I just tried placing the values from the code @scritch007 linked into build.prop like so:
Code:
ro.cdma.home.operator.numeric=311490
ro.cdma.home.operator.alpha=Virgin Mobile US
gsm.sim.operator.numeric=311490
gsm.sim.operator.alpha=Virgin Mobile US
gsm.operator.numeric=311490
gsm.operator.alpha=Virgin Mobile US
Then I tried appropriately tagging the VM APNs with numeric="311490" mcc="311" mnc="490" while including them in a default, huge apns-conf.xml file.
Even with the proper numeric codes set in build.prop, the phone populates its APN database with Sprint (310120) APNs. Getprop yields the following results:
ro.cdma.home.operator.numeric=311490
gsm.sim.operator.numeric=31000
gsm.operator.numeric=310120
I sure hope hardcoding these values into init works better than defining them in build.prop. It's clear that the value of gsm.operator.numeric is pretty important. It's also clear that patching build.prop doesn't help us.
Pardon me if this is all old news, but I'm pretty new here.
When flashing the Motorola Moto G 2015 with any custom ROM (Cyanogenmod, Resurrection Remix, Lineage), the PRL information sticks until a reboot from custom ROM.
When rebooting, the phone has internet access (including Hotspot), however no text messages, inbound/outbound phone calls do not work. The fix has been flashing Virgin Mobile stock ROM in TWRP recovery, programming the phone (##72786#) and then restoring a backup from custom ROM via TWRP recovery. Then the phone will again be able to send/receive text messages and phone calls - until the next reboot.
Would like to know if there is a fix to bypass reflashing stock ROM if phone needs rebooting from custom ROM. This process takes about 15 - 20 minutes. Big nuisance.
Any assistance would be appreciated.
------------
NetSpeedZ said:
Any assistance would be appreciated.
Click to expand...
Click to collapse
Copy this APN (see the attachments), to system/etc and set permissions to 0644 or rw-r--r-- with a root explorer. Reboot. Go to settings>more>cellular networks, select LTE in Preferred network type, and RUIM/SIM in system select. Tap the "carrier settings" option at the very bottom. All the radios will reset and come back on in a few seconds, and everything should work after that. Let me know if you need any more assistance, I'll be happy to help. I've had to deal with this issue since day one.
Edit; You will only have to do this after flashing a ROM, and this includes updates too. It can also be done through TWRP's file manager immediately after flashing before you even boot it the first time, and without root.
Spaceminer said:
Copy this APN (see the attachments), to system/etc and set permissions to 0644 or rw-r--r-- with a root explorer. Reboot. Go to settings>more>cellular networks, select LTE in Preferred network type, and RUIM/SIM in system select. Tap the "carrier settings" option at the very bottom. All the radios will reset and come back on in a few seconds, and everything should work after that. Let me know if you need any more assistance, I'll be happy to help. I've had to deal with this issue since day one.
Edit; You will only have to do this after flashing a ROM, and this includes updates too. It can also be done through TWRP's file manager immediately after flashing before you even boot it the first time, and without root.
Click to expand...
Click to collapse
Cyanogenmod 12.1 does not have the menu - settings>more>cellular networks. Is this done via stock ROM?
Also, don't have RUIM/SIM in system select. Only 'Home Only' and 'Automatic'.
------------
NetSpeedZ said:
Cyanogenmod 12.1 does not have the menu...
Click to expand...
Click to collapse
Try rebooting the ROM without your sim card in. Then put it back and reboot once more. It should reset. I didn't realize you were still using cm12. Those settings are only found in 6.0.1 and up. The apn settings not being visible has something to do with us being CDMA. I think it's the sim cards virgin uses.
You also need to add these lines to the end of your build.prop too. (Not needed on MM+)
ro.cdma.home.operator.numeric=311490
ro.cdma.home.operator.alpha=Virgin Mobile US
ro.telephony.default_network=8
telephony.slteOnCdmaDevice=1
Spaceminer said:
Try rebooting the ROM without your sim card in. Then put it back and reboot once more. It should reset. I didn't realize you were still using cm12. Those settings are only found in 6.0.1 and up. The apn settings not being visible has something to do with us being CDMA. I think it's the sim cards virgin uses.
You also need to add these lines to the end of your build.prop too. (Not needed on MM+)
ro.cdma.home.operator.numeric=311490
ro.cdma.home.operator.alpha=Virgin Mobile US
ro.telephony.default_network=8
telephony.slteOnCdmaDevice=1
Click to expand...
Click to collapse
While waiting for your reply, I copied the APNS-Conf.xml file attached to your original reply to the system/etc folder on phone and rebooted. Inbound/outbound phone calls and text messages seem to be working now. Even performed a backup in TWRP and then rebooted again. All seems to be operating properly.
I did not add the build-prop text you gave in previous reply. What exactly does this build-prop text do? I'm hesitant in adding it as everything is operational - the old saying 'don't fix what isn't broken'.
I was using Cyanogenmod 13, however, I did not like some of the Cyanogenmod 13 apps, i.e., text messaging app. The Cyanogenmod 12.1 texting app has many features that CM 13 doesn't. Also, CM 12.1 seemed to run smoother on the Motorola Moto G 2015 phone I'm currently using.
Also would be interested in knowing where the apns-conf.xml file was pulled from and what all this file did to make everything work again.
FYI, as standard procedure I always mount system and then flash the Virgin Mobile APNFix (which I've attached for anyone running across this thread in need of this file) in TWRP after flashing a new ROM and associated GAPPS , however, it seems that the apns-conf.xml file became corrupt/unusable somewhere along the line.
Your efforts in helping me solve this issue are appreciated.
------------
NetSpeedZ said:
I did not add the build-prop text you gave in previous reply. What exactly does this build-prop text do? I'm hesitant in adding it as everything is operational - the old saying 'don't fix what isn't broken'. ....
Also would be interested in knowing where the apns-conf.xml file was pulled from and what all this file did to make everything work again.
Click to expand...
Click to collapse
If everything is working properly, then don't worry about adding those lines. I had to add those and the apn to get LTE working on the older test builds of cm12. As far as I know, it just locks you to virgin. It was likely fixed in later builds of cm12.
The APN I pulled from an older build of cm13. When flashing the older ones, the install process would locate and copy virgin's current apn to /system/etc and rename Motorola's default APN to .bak. (The giant 500kb+ APN with all the carriers found in stock.) It would also add a US Cellular APN. I discovered at some point from poking around enough, that deleting the .bak and US Cellular APNs got LTE working if I reset the radio afterwards.
Spaceminer said:
If everything is working properly, then don't worry about adding those lines. I had to add those and the apn to get LTE working on the older test builds of cm12. As far as I know, it just locks you to virgin. It was likely fixed in later builds of cm12.
Click to expand...
Click to collapse
This is a nice and informative thread for anyone that has the same issues that you and I have had with Virgin Mobile APN's. Hopefully it will be added to Google searches soon.
Appreciate all the help.
------------
If You're Like Me And Have Sprint, But Having
Issues With 4g/LTE Data On Lineage Based Roms
(Including GSI), Then Here's The Fix. I've Done This
Multiple Times, And It's Worked Great. Everything
You Need Is In The Zip As Well.
=====================================
Once The Rom Is Fully Installed And Booted,
Go To Settings, Network & Internet, Mobile Network,
Advanced, And Access Point Names. You'll Be Adding
A NEW APN, Exactly As Below. Screenshots Attached
As Well.
=====================================
Name : Sprint
APN : x.ispsn
Proxy : Not Set
Port : Not Set
Username : Not Set
Password : Not Set
Server : Not Set
MMSC : http://mms.sprintpcs.com/servlets/mms/
MMS Proxy : Not Set
MMS Port : Not Set
MCC : 310 ***
MNC : 120 ***
Authentication Type : Not Set
APN Type : default,mms,supl,hipri,fota,ims,cbs
APN Protocol : IPv4/IPv6
APN Roaming Protocol : IPv4/IPv6
Bearer : Unspecified
MNVO Type : None
=====================================
Once The APN Has Been Added, Push The 3 Dots
Up Top, And Click Save. Then Make Sure The NEW
APN Is Selected.
=====================================
https://cp.sync.com/dl/f6482b210/ab97w3j2-uevmigxz-2fpjeehn-i64ig32i
Download And Unzip The Zip Provided (sprintfix.zip). Reboot Your
Phone Into Bootloader Mode. Once In Bootloader Mode, Open A
Command Prompt / Powershell In The Zip Folder By Holding Down
Shift, Right Clicking, And Then Selecting The Option For
"Open Command Prompt / Powershell Here"
=====================================
Directions For Command Prompt:
Type In The Following Command Without Quotes "mfastboot flash modem non-hlos.bin"
Once That Finishes, Type In The Next Command, Without Quotes "mfastboot erase carrier".
Then Finally, "mfastboot reboot".
Directions For Powershell:
Same As Command Prompt, EXCEPT: change "mfastboot" to ".\mfastboot".
=====================================
If You Mess With The APN Settings, Or Change It Around, You'll Have To Do
These Steps Again.
Showing 4g On Sprint
Pictures
good news for Sprint users
What's the point of SprintDM and Carrier Provisioning Service if 4G relies on a Modem & APN? The world may never know.
Thanks for this, now Fi users can also get full Sprint access (if they need it).
murrty said:
What's the point of SprintDM and Carrier Provisioning Service if 4G relies on a Modem & APN? The world may never know.
Thanks for this, now Fi users can also get full Sprint access (if they need it).
Click to expand...
Click to collapse
The verdict is out on whether this works for FI at the moment. Currently it's a guide for straight sprint. If someone gets this working with FI, please post
This doesn't work on Project FI because APN settings are disabled by the Project FI app.
michael28056 said:
This doesn't work on Project FI because APN settings are disabled by the Project FI app.
Click to expand...
Click to collapse
I have an idea for fi, give me a few and I'll post my suggestion. On the road at a red light lol
EDIT: Working on my idea now
If someone with FI, on a lineage base (or GSI) having issues with FI days could PM me, I have an idea I'd like tried before I post it.
Message sent I'm interested in being guinea pig.
Sorry, been sick the past couple days. I got a fi sim, and tried it out. Didn't work
I switched to project fi, this fix does work.
Tried this fix for the GSI 9.0 ROM, using Project FI. Everything else seems to work just fine. Keep getting the message about SprintDM stopping anytime I try to connect to Sprint. Either through Fi Activation or using dialer codes. Anyone else have the same issue?
Nick1801 said:
Tried this fix for the GSI 9.0 ROM, using Project FI. Everything else seems to work just fine. Keep getting the message about SprintDM stopping anytime I try to connect to Sprint. Either through Fi Activation or using dialer codes. Anyone else have the same issue?
Click to expand...
Click to collapse
Yes, Sprint will only connect to 3G as well, logcat said something about missing a Java file ( or class), the file is there so I'm going to open Java file and see if I can figure anything out, don't expect much from me though.
QWZR II said:
Yes, Sprint will only connect to 3G as well, logcat said something about missing a Java file ( or class), the file is there so I'm going to open Java file and see if I can figure anything out, don't expect much from me though.
Click to expand...
Click to collapse
Sprint doesn't even connect on 3g for me, as soon as it tries to connect with Sprint, I get the SprintDM.apk has closed error. Then it switches over to Tmo. I wouldn't even really mind if Tmo worked at all in my area. Hate to go back to stock just for Sprint lol. I was going to attempt to maybe replace the SprintDM.apk in the system files. I noticed the one in there has a build date from 1969.
Not sure if that even matter, might trip up some kind of security. Like when the date on Windows is set incorrectly? Just guessing. Going to stick with the Wi-Fi/Tmo service as long as I can, don't want to end the Pie love affair yet.
Nick1801 said:
Sprint doesn't even connect on 3g for me, as soon as it tries to connect with Sprint, I get the SprintDM.apk has closed error. Then it switches over to Tmo. I wouldn't even really mind if Tmo worked at all in my area. Hate to go back to stock just for Sprint lol. I was going to attempt to maybe replace the SprintDM.apk in the system files. I noticed the one in there has a build date from 1969.
Not sure if that even matter, might trip up some kind of security. Like when the date on Windows is set incorrectly? Just guessing. Going to stick with the Wi-Fi/Tmo service as long as I can, don't want to end the Pie love affair yet.
Click to expand...
Click to collapse
I was trying that, it won't install because it's a system app and the uid (not sure on the actual error) is mismatched. Looking it up online suggested either editing manifest xml or clearing odex file from priv app, which I couldn't find a way to do successfully.
QWZR II said:
I was trying that, it won't install because it's a system app and the uid (not sure on the actual error) is mismatched. Looking it up online suggested either editing manifest xml or clearing odex file from priv app, which I couldn't find a way to do that didn't involve "lucky patcher" which won't work if you've already removed using terminal debloater.
Click to expand...
Click to collapse
I'm just sticking with T-Mobile and Wifi for now. Don't want to go back to 8.1 after using 9. Maybe someone will have a fix eventually, I'm sure that's more likely than Moto actually releasing Pie this year.
Anymore information on if this works with Project Fi? I am on Project Fi and would like to run Lineage but went back to stock for the fact that my data for Sprint and US Cellular were not working. I had to leave my phone on T-Mobile all the time which is not optimal where I drive and live. I need my phone to be able to get data in remote locations through the different carriers. I ran LOS 15.1 Unofficial, Official and LOS 16 Unofficial. None of them had mobile data on Sprint or US Cellular. Only T-Mobile. I tried installing SprintDM in system to no avail.
A thought, I have had Fi since beginning. Now with US Cellular added, it's a must for my area of coverage. I live in a remote (cell wise) area and only US Cellular works. So my Moto X4 is stock until Pie updates for all above reasons. On my Nexus 5X I could not use any Lineage based roms because of the Sprint/Fi problem. From What I have found Lineage went from complete ASOP to some else after 14.X for certain system based files for carriers. Especially Sprint APN's. My knowledge is limited on how or why. Even with my returned Pixel 2 and now Pixel (unlocked Verizon) I have to stay with Google based app+apk's roms to have ALL Fi Carriers switching with out problems. I still can't use Lineage based roms + apks to get Carrier switching to work on my Pixel. So can somebody figure out how to still use original Moto X4 Fi App packages? That may fix it.
I have all 3 networks working with 4G on my phone on the latest version of LOS 16. I had to add in some files I pulled from the latest Pixel 3 Rom. I'm not sure if all the files I grabbed are needed since I'm not an expert by any means but what I added seemed to get all three networks working.
I haven't had much chance to test auto switching because I'm generally always on T-Mo.
I also flashed the NON-HLOS.bin from the latest stock rom as well following the instructions in OP's post. I didn't bother creating the apn.
After rebooting I cleared the data for the project-fi app and let the service re-activate.
Not sure if it matters but I also have the stock gapps package installed.
I'll attach the files I used showing the paths where I copied the files to. I just overwrote whichever files were already there. I would make a twrp zip to install these files but I'm not sure how to do that if someone else wants to take a crack at it feel free.
https://ln.sync.com/dl/b36c27e30/qvzjf7v2-jwmzmqy7-uxua4x76-cjy3brq2
slaytanic said:
If You're Like Me And Have Sprint, But Having
Issues With 4g/LTE Data On Lineage Based Roms
(Including GSI), Then Here's The Fix. I've Done This
Multiple Times, And It's Worked Great. Everything
You Need Is In The Zip As Well.
=====================================
Once The Rom Is Fully Installed And Booted,
Go To Settings, Network & Internet, Mobile Network,
Advanced, And Access Point Names. You'll Be Adding
A NEW APN, Exactly As Below. Screenshots Attached
As Well.
=====================================
Name : Sprint
APN : x.ispsn
Proxy : Not Set
Port : Not Set
Username : Not Set
Password : Not Set
Server : Not Set
MMSC : http://mms.sprintpcs.com/servlets/mms/
MMS Proxy : Not Set
MMS Port : Not Set
MCC : 310 ***
MNC : 120 ***
Authentication Type : Not Set
APN Type : default,mms,supl,hipri,fota,ims,cbs
APN Protocol : IPv4/IPv6
APN Roaming Protocol : IPv4/IPv6
Bearer : Unspecified
MNVO Type : None
=====================================
Once The APN Has Been Added, Push The 3 Dots
Up Top, And Click Save. Then Make Sure The NEW
APN Is Selected.
=====================================
https://ln.sync.com/dl/f6482b210/ab97w3j2-uevmigxz-2fpjeehn-i64ig32i
Download And Unzip The Zip Provided (sprintfix.zip). Reboot Your
Phone Into Bootloader Mode. Once In Bootloader Mode, Open A
Command Prompt / Powershell In The Zip Folder By Holding Down
Shift, Right Clicking, And Then Selecting The Option For
"Open Command Prompt / Powershell Here"
=====================================
Directions For Command Prompt:
Type In The Following Command Without Quotes "mfastboot flash modem non-hlos.bin"
Once That Finishes, Type In The Next Command, Without Quotes "mfastboot erase carrier".
Then Finally, "mfastboot reboot".
Directions For Powershell:
Same As Command Prompt, EXCEPT: change "mfastboot" to ".\mfastboot".
=====================================
If You Mess With The APN Settings, Or Change It Around, You'll Have To Do
These Steps Again.
Click to expand...
Click to collapse
The sprint-fix link is broken. Do you have a copy of it?