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.
Related
Wifi Calling working on ROMs that don't have it included.
It looks the files needed as compared to other WifiCalling packages for other phones are:
/system/lib
libganril.so
libhtc_ril.so
libhtc_ril_switch.so
libkineto.so
librilswitch.so
/system/app
com.android.kineto.apk
Then in the build.prop append this line of text to the very end
Code:
rild.libpath=/system/lib/librilswitch.so
THE ZIP IS NOT FLASHABLE
Its only for testing purpose to make sure we get Wifi Calling working properly so we can make a flashable zip later when we start getting AOSP roms and custom kernels
I am going to work on a installable script from the terminal that will copy over the needed files to the correct directories then append the needed line of text do the build.prop
10Char, working on script
In one of the roms they had the t-mob wifi in a zip they didn't test it but I could look there
Updated with some more information that I gathered for testing
There is a kernel and a flashable zip that will put wifi calling back onto your phone. Check the insert coin rom thread for info on it.
silentsnow31802 said:
There is a kernel and a flashable zip that will put wifi calling back onto your phone. Check the insert coin rom thread for info on it.
Click to expand...
Click to collapse
yes but if you also check it, it will also put all the other tmobile crap on your phone, plus he couldn't test it since he is not on tmobile, so have you tried it and verified that it worked?
update posted. I currently have Wifi Calling while using Revolution HD
BrokenWall said:
update posted. I currently have Wifi Calling while using Revolution HD
Click to expand...
Click to collapse
have you check mic volume level? I have many people said they have trouble hearing me. I did a test call to my skype and the mic volume is indeed very low. I had to revert to stock rom to get volume back to normal.
sovereignty68 said:
have you check mic volume level? I have many people said they have trouble hearing me. I did a test call to my skype and the mic volume is indeed very low. I had to revert to stock rom to get volume back to normal.
Click to expand...
Click to collapse
I have always had low mic call volume running the stock ROM. This has been the case with both Sensations I have owned. Never had an issue with Skype, volume is always perfect.
Just tested this myself with the insertcoin build.prop (from the TMOUS Patch) and its working, using the libs and apk provided here.
BrokenWall said:
yes but if you also check it, it will also put all the other tmobile crap on your phone, plus he couldn't test it since he is not on tmobile, so have you tried it and verified that it worked?
Click to expand...
Click to collapse
Yes I have tried it. I was actually the one that tested the flashable kernel. It does install all the other tmobile crap but titanium backup made short work of that.
silentsnow31802 said:
Yes I have tried it. I was actually the one that tested the flashable kernel. It does install all the other tmobile crap but titanium backup made short work of that.
Click to expand...
Click to collapse
give me some time to sort through the differences in the build.props to see what is triggering the difference in wifi calling working or not then we will see if we can get something made.
So after looking at a build.prop from Revolution HD and then comparing it to the one from Virtuous, Stock, and InsertCoin TmoUS mod.
I think I have traced down the issues, looking into it a built more. After I find the needed values I will see if we can make an install script that will mod the build.prop lines and add the libs and apk and restart the phone.
Update for complete working Wifi Calling. I have tested it a few times and it works fine with only these files at minimum, no need to add alot of extra text or HTC/Tmobile crap.
Works for me thanks. Took me a bit to figure out that you still need to install after copying the apk to /system/app.
Thanks again.
Sent from my HTC Sensation Z710e using XDA Premium App
I forgot where I got this (sorry ) but it works on any ROMs I've tried. Flash it on top of the ROM. Currently using it with LeeDroid without any problems.
It doesn't have t-mobile bloatware.
http://www.mediafire.com/?fdsqwfo28lat0qx
tengtengvn said:
I forgot where I got this (sorry ) but it works on any ROMs I've tried. Flash it on top of the ROM. Currently using it with LeeDroid without any problems.
It doesn't have t-mobile bloatware.
http://www.mediafire.com/?fdsqwfo28lat0qx
Click to expand...
Click to collapse
This is not a problem, the only issue I have with this is that you loose any custom tweaks or settings the developer made to his/her ROM because your flashing a basic stock build.prop
I will make a script here shortly that will copy files to the needed directories and then append the needed information to the end of the current build.prop, and all you will need to do is run the script from a terminal or from ADB off the SDCard after each update.
When I start the wifi app, it connects to my network, but it gets stuck on "enabling....". Any suggestions?
Edit: NVM. After I restarted my phone it worked. Thanks.
Wifi calling working for me but have a small issue. The outgoing mic volume is really low on my end. People on the other end of the line can hardly hear me. Any chance you could bump up the mic gain values a bit?
I am having a few issues:
1. When I turn off wifi calling, the app automatically restarts and re-enables it. This occurs even when I select cellular as connection preferences.
2. When I select cellular for connection preferences, with wifi calling ON, it still uses wifi. Why won't it use the cellular signal?
Thanks.
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
Q&A for CyanogenMod 12.0 for Photon Q
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for CyanogenMod 12.0 for Photon Q. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
So far so good for CM12, everything runs really smooth. Only issues are the default text app send button is grayed out and won't let you send but using Google messenger app it works fine. Is there any reason to why the send button wouldn't work?
LTE seems to work well but visually every now and then it seems to disconnect/reconnect but functions fine. And just a quick/dumb question which CDMA subscription should we use, RUIM/SIM or NV as I found info on RUIM/SIM but couldn't really find much on the definition of NV.
I really wanted to know that everybody has no problem at all in logging in Google+ with the latest version of its client.
I'm having trouble the most recent one that I can download from Play Store, : v5.1.0
I had to restore the backed up version of v5.0
I recently got the multimedia dock for this phone and I've noticed that some things don't work. None of the USB ports on the dock seem to interface with the OS, but any peripheral connected by a USB OTG cable (while not in the dock, of course) works just fine. Also, the device doesn't seem to detect that it is in a dock at all; I have it set to daydream when it's docked, but nothing happens.
Does anybody else have these issues? Is there a known or planned solution?
Thanks!
Hei just another quicky:
I had problems with twrp unable to mount /data on encrypted phone. I was never asked for passphrase also it did not detect data was formated as f2fs and assumed ext4.
After factory reset I reformated data and cache to f2fs again (as I think the performance gain is real) and cleanflashed latest cm12 nightly + gapps.
After setting up my phone it became slugish fast again, also battery did drain fast (also the phone did get real hot)
My circumvention so far is limiting Background processes to 2 within Dev options. Since then phone stays much cooler, everything works as expected normal cpu usage shows 2.5/3.2/3.5.
Before that phone was sometimes at 12/9/8 or so and thus bekame unresponsive/sluggish.
Does anyone know the standard count of background processes? Form Q?
Since i did not discover any strange behavior/lags since i switched to only 2 backgroundprocesses anyone knows what kind of usage could result in problems with lower backgroundprocesses?
Thanks in advance!
CM 12.0 nightlies I/O and issues
So I switched over to CM12 because of the ability to switch the filesystems to f2fs. And so far I have seen a pretty decent improvement in the response, speed, and general performance with CM12.
A few issues have come up though:
CM nightly 03232015
-the cLock widget just randomly stopped functioning. Worked for a day or two, then stopped working. I wasn't able to set the alarm and clicking on the time on the home screen does nothing. Disabled cLock and am using the default Deskclock instead (I need to be able to set alarms).
-the messaging app was not working correctly... I was able to receive texts but the send button was greyed out and would not let me click on it. This is both over Wi-Fi and 3G and 4G LTE. Had to revert to 8sms that I was using on CM10...
-the themes are applied inconsistently... not all apps or system dialogs are themed when I use ThemeDIY to create/apply my own theme.
-equalizer doesn't seem to make a big difference...
-doesn't seem to remember wifi logins... keep getting the "sign in to wireless network" notification (I've already signed in)... the sign in page does not open in Chrome, but rather a separate browser or system page that won't offer to save my password (though it does autofill the username)...
-weird issues using adb... even though I've authorized the computer, and have root access on the phone and am running adb root, it won't let me write to certain parts of the file system (I couldn't adb push bootanimation.zip /system/media/bootanimation.zip error was "read-only filesystem")
I know it's a nightly, just wanted to see if anyone else has these same issues and to make sure the developers are seeing this. For the record, I did a wipe and format (since I was going to change the file system,) and this is a clean install of both TWRP and CM12.
Thanks!
---------- Post added at 06:15 PM ---------- Previous post was at 05:58 PM ----------
breakerwaves said:
So far so good for CM12, everything runs really smooth. Only issues are the default text app send button is grayed out and won't let you send but using Google messenger app it works fine. Is there any reason to why the send button wouldn't work?
LTE seems to work well but visually every now and then it seems to disconnect/reconnect but functions fine. And just a quick/dumb question which CDMA subscription should we use, RUIM/SIM or NV as I found info on RUIM/SIM but couldn't really find much on the definition of NV.
Click to expand...
Click to collapse
I didn't know what to use either so I left it on NV. Haven't noticed a difference in signal or call quality or anything. I am guessing since we're on Sprint and there is no SIM card that RUIM/SIM won't work?
Im am currently running on NV too, but with german sim.
To the other problems you have, I don"t have those. Sms works. CLock works, alarms work... I am running without any themes just switched the stock trebuchet launcher to apex. I am also on f2fs.
I also would like to know the difference between NV and RUI/SIM, and which one should be preffered with simcard mod.
kecksk0enig said:
Im am currently running on NV too, but with german sim.
To the other problems you have, I don"t have those. Sms works. CLock works, alarms work... I am running without any themes just switched the stock trebuchet launcher to apex. I am also on f2fs.
I also would like to know the difference between NV and RUI/SIM, and which one should be preffered with simcard mod.
Click to expand...
Click to collapse
I can't speak to the RUI/SIM issue but I don't know how to switch themes off. As far as my SMS and cLocks idk it is possible that I disabled the wrong app I don't like to run more then the bare minimum. As for the theme I ended up downloading a dark theme from the app store which is wonderful looking!! It is called Nicholas' Dark Material. In case you're looking for dark like me.
Do you have issues with the gallery or camera? I think I saw somewhere on the xt897 forum a link to motorola's camera and gallery apps... are you able to change the save location for pictures or no?
I also had an issue where the navigation bar does not render right when I watch full screen video in landscape mode. May have to do with me forcing GPU render under developer options. I'd take it off but I can't remember how I got there lol
---------- Post added at 11:27 PM ---------- Previous post was at 11:21 PM ----------
I cannot set the custom color for notifications in CM12... but there is a post that says the colors were retained on an upgrade from CM11. Well I wiped and did a clean install rather than an upgrade so is there an .xml file or a settings I can edit? I'm comfortable with file manager and editor and adb and shell...
CM 12 update
I have a simple question so if I am not asking it in the right place, I apologize.
If I do one of the CM12 updates (the nightlies) through the Update in the Settings Menu on my phone, does it wipe the phone? Or does it only update relevant system files and keep my apps and data??
nasch007 said:
I have a simple question so if I am not asking it in the right place, I apologize.
If I do one of the CM12 updates (the nightlies) through the Update in the Settings Menu on my phone, does it wipe the phone? Or does it only update relevant system files and keep my apps and data??
Click to expand...
Click to collapse
If you only apply the update, it will not wipe the device. You would have to wipe it manually in recovery. It will apply a so-called "dirty flash" as you are not wiping any partitions.
CM12-->CM12, should be fine. Of course before you report any issues try a clean flash (or if it's a single app FC'ing, try clearing data on that single app).
I'm having tons of trouble using this with Sprint.
When I lock it to CDMA and/or EVDO mode, Logcat shows that it's trying to connect using a C Spire APN. If I lock it in LTE-only mode and select Sprint APN, it gets a good data connection. The APN menu is foolishly disabled for CDMA/EVDO so I cannot correct the issue. Why is it trying C Spire? How can I fix 3g and MMS settings to work?
CM11 worked great in all conditions, and MMS worked out of the box.
I'm trying to flash CM12 on a FreedomPop device and I'm getting the message "This package is for device: xt987,asanti_c; this device is asanti". I was able to flash CM11 from the nightlies page but no luck with CM12 nightlies nor with the CM12.1 that was posted here on XDA.
Any help to flash CM12 on this device? :good:
Alien987 said:
I'm trying to flash CM12 on a FreedomPop device and I'm getting the message "This package is for device: xt987,asanti_c; this device is asanti". I was able to flash CM11 from the nightlies page but no luck with CM12 nightlies nor with the CM12.1 that was posted here on XDA.
Any help to flash CM12 on this device? :good:
Click to expand...
Click to collapse
In the short term you can change the meta-inf file in the update.zip and change the assert line to allow asanti.
In the future, the CM maintainer probably needs to update the source to allow your device... odd that it worked in CM11 but not 12 tho.
Are you going from CM11 to CM12? Even if you clean flashed.
arrrghhh said:
In the short term you can change the meta-inf file in the update.zip and change the assert line to allow asanti.
In the future, the CM maintainer probably needs to update the source to allow your device... odd that it worked in CM11 but not 12 tho.
Are you going from CM11 to CM12? Even if you clean flashed.
Click to expand...
Click to collapse
Thanks for the tip!
First I tried to flash CM12 directly but got the error. Then decided to try with CM11 and it worked so I hoped it would work to update to CM12 but got the same error again.
Just to double check I'm not doing it wrong, this is what I tried to flash:
CM12 (Failed): http://download.cyanogenmod.com/get/jenkins/107228/cm-12-20150417-NIGHTLY-xt897.zip
CM11 (Success): http://download.cyanogenmod.com/get/jenkins/100850/cm-11-20150216-NIGHTLY-moto_msm8960_jbbl.zip
What I understood by reading around is that for CM12 I should use the xt897 file even though it's differently named than the CM11 one (moto_msm_8960_jbbl).
Can you please confirm that I'm using the correct CM12 one?
Thanks
Alien987 said:
Thanks for the tip!
First I tried to flash CM12 directly but got the error. Then decided to try with CM11 and it worked so I hoped it would work to update to CM12 but got the same error again.
Just to double check I'm not doing it wrong, this is what I tried to flash:
CM12 (Failed): http://download.cyanogenmod.com/get/jenkins/107228/cm-12-20150417-NIGHTLY-xt897.zip
CM11 (Success): http://download.cyanogenmod.com/get/jenkins/100850/cm-11-20150216-NIGHTLY-moto_msm8960_jbbl.zip
What I understood by reading around is that for CM12 I should use the xt897 file even though it's differently named than the CM11 one (moto_msm_8960_jbbl).
Can you please confirm that I'm using the correct CM12 one?
Thanks
Click to expand...
Click to collapse
Yes, that's the correct one.
The CM maintainer clearly states the reasoning in the CM12 thread:
kabaldan said:
Please note:
In CM12, the Motorola 2012 msm8960 device line has been de-unified again, so moto_msm8960/moto_msm8960_jbbl builds are dead from now on.
Please check the xt897 device link for new Photon Q builds.
Click to expand...
Click to collapse
arrrghhh said:
In the short term you can change the meta-inf file in the update.zip and change the assert line to allow asanti.
In the future, the CM maintainer probably needs to update the source to allow your device... odd that it worked in CM11 but not 12 tho.
Are you going from CM11 to CM12? Even if you clean flashed.
Click to expand...
Click to collapse
Adjusting the meta-inf to check for "asanti" instead of "asanti_c" worked perfectly. Thanks for your help!
Now I have to find out why after I flash gapps I start to get multiple crashes related to Google Services and Google Apps.
Edit: Well, just in case someone face the same problem in the future. I updated to the latest TWRP recovery directly from their webpage (initially I used Rashr app) and that solved all my problems, including the initial error when flashing CM12 nightly.
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.
------------
Has anybody gotten visible Wireless to work correctly on custom roms? I got it up and running no problem on oxygen OS, but for some reason I just can't get it going on customs.
It's literally driving me insane.
I'm bumping this thread... been trying out some custom roms (Havoc and trying Bliss now) but haven't been able to get any Visible Wireless (by Verizon) signal on my phone.
Does anyone know if ANY custom ROM works? Particularly interested in ASOP ROMs, not ones based on OOS.
dizM0nkey said:
I'm bumping this thread... been trying out some custom roms (Havoc and trying Bliss now) but haven't been able to get any Visible Wireless (by Verizon) signal on my phone.
Does anyone know if ANY custom ROM works? Particularly interested in ASOP ROMs, not ones based on OOS.
Click to expand...
Click to collapse
Yes, you can get visible wireless to work on all custom roms now. Used to not be able to because custom roms wouldn't detect Verizon Sims, but that's been fixed for a couple months now. Only thing that needs to be done is updating the apn config. The instructions to replace the apn config file are located here. The only difference is on Android 10, it's located in /system/product/etc/ instead of /system/etc/ that is lit used to be on Android 9. I've uploaded the new apn config file that you need to use.
jeffsga88 said:
Yes, you can get visible wireless to work on all custom roms now. Used to not be able to because custom roms wouldn't detect Verizon Sims, but that's been fixed for a couple months now. Only thing that needs to be done is updating the apn config. The instructions to replace the apn config file are located here. The only difference is on Android 10, it's located in /system/product/etc/ instead of /system/etc/ that is lit used to be on Android 9. I've uploaded the new apn config file that you need to use.
Click to expand...
Click to collapse
Awesome... I opened in Notepad++ and searched for "VSBL" ... four entries were found. I was able to combine most of the entries into 'apn carrier="Visible Internet"'
<apn carrier="Visible Internet"
mcc="311"
mnc="480"
apn="VSBLINTERNET"
type="default,dun,supl,fota,ims,mms,ia,cbs"
mmsc="http://mms.vtext.com/servlets/mms"
protocol="IPV4V6"
roaming_protocol="IPV4V6"
profile_id="0"
modem_cognitive="true"
max_conns="20"
max_conns_time="300"
wait_time="0"
read_only="false"
mvno_type="GID"
mvno_match_data="BAE1000000000000"
/>
Data, MMS, etc all working great. Thanks for sharing!
it works
Wow. I just got a H830 unlocked lg g5 running lineage 17.1 working with visible LTE. I merely switched the apn.xml file as you said and switched my preferred network mode to LTE. THANK YOU!!
---------- Post added at 01:33 AM ---------- Previous post was at 01:26 AM ----------
Burt Squirtz said:
Has anybody gotten visible Wireless to work correctly on custom roms? I got it up and running no problem on oxygen OS, but for some reason I just can't get it going on customs.
It's literally driving me insane.
Click to expand...
Click to collapse
Yes!!! I finally did! Lineage 17.1 on a lg g5 h830 and on lineage 17.1 galaxy s9. Both working. WOOHOO! Merely swap apn.xml, chmod, reboot, reset settings, then click visible internet, then set network mode to "LTE"
I have a OP8 Pro that I've been trying to get work with Visible and custom roms (Resurrection Remix and/or crDroid specifically), but have hit a dead end.
crDroid doesn't let me edit any of the "Network Settings," the option is grayed out entirely with the Visible SIM inserted (but the lock screen shows "No SIM inserted - Visible," giving the impression that the phone sees the SIM in one slot, knows it is Visible, but won't connect or register it to allow changing settings).
Resurrection Remix will recognize the SIM, and I can get into Network Settings. I've tried to add all 4 APNs manually after flash and can't get it to get a signal at all, leading me to believe that there's further, "deeper" integration that I don't have access to after flashing is complete and system partitions are locked as read-only.
TWRP 3.40-14 by mauronofrio works with Resurrection Remix flashed, but System, Vendor, Product, etc. are all locked as read-only, so editing the apn-conf.xml file can't be edited. And, sadly, that's where I'm at. A bit frustrating that OOS stock recognizes everything instantly upon initial boot, but custom roms won't. If there's any information I can provide to help get universal support for this carrier, I would be more than happy to help contribute.
lee_d said:
I have a OP8 Pro that I've been trying to get work with Visible and custom roms (Resurrection Remix and/or crDroid specifically), but have hit a dead end.
crDroid doesn't let me edit any of the "Network Settings," the option is grayed out entirely with the Visible SIM inserted (but the lock screen shows "No SIM inserted - Visible," giving the impression that the phone sees the SIM in one slot, knows it is Visible, but won't connect or register it to allow changing settings).
Resurrection Remix will recognize the SIM, and I can get into Network Settings. I've tried to add all 4 APNs manually after flash and can't get it to get a signal at all, leading me to believe that there's further, "deeper" integration that I don't have access to after flashing is complete and system partitions are locked as read-only.
TWRP 3.40-14 by mauronofrio works with Resurrection Remix flashed, but System, Vendor, Product, etc. are all locked as read-only, so editing the apn-conf.xml file can't be edited. And, sadly, that's where I'm at. A bit frustrating that OOS stock recognizes everything instantly upon initial boot, but custom roms won't. If there's any information I can provide to help get universal support for this carrier, I would be more than happy to help contribute.
Click to expand...
Click to collapse
I have a Pixel 4a and none of the custom ROMs except 1, which naturally was the last one I tried, worked. The ROM that worked had this dir /product/etc/CarrierSettings/ with a config for each carrier, Visible's config filename being visible_us.pb, and this dir was missing from the ROMs that Visible did not work on. Note the stock firmware had the same dir and Visible config as well. I also have /product/etc/apns-conf.xml in my ROM that works on Visible but the Visible APNs are NOT in that config so it's pulling it from the visible_us.pb.
It's clearly a firmware issue on some level. I suspect it's simply a matter of getting the system to use the proper APNs. It seems to me that the only way to do that is by building the ROM with the Visible APNs baked in the /product/etc/CarrierSettings/visible_us.pb, or /product/etc/apns-conf.xml, depending on where your implementation gets these default values from — or maybe it's the implementation that makes the difference, I'm not sure.
What doesn't make sense to me is why adding the APNs in settings manually had zero effect. I got the same default APNs to select from when I insert the SIM with ROM that did not work as you, StraightTalk, Verizon, and Xfinity. I also noticed that intermittently it would automatically load the VSBLINTERNET APN from the SIM but nothing would work.
I think the next step is to try to get the devs to include the Visible APNs to apns-conf.xml in the next build. I suspect that will cure this. Too bad Android make the system RO or it would be trivial.
Links that may be of interest..
This is my ROM for Pixel 4a that does work on Visible forked from ASOP.
https://forum.xda-developers.com/t/official-superioros-xcalibur-android-11.4181587/
https://github.com/daradib/carriersettings-extractor
https://www.reddit.com/r/oneplus/comments/g36mxn
https://github.com/GrapheneOS/os_issue_tracker/issues/153
guru6969 said:
I have a Pixel 4a and none of the custom ROMs except 1, which naturally was the last one I tried, worked. The ROM that worked had this dir /product/etc/CarrierSettings/ with a config for each carrier, Visible's config filename being visible_us.pb, and this dir was missing from the ROMs that Visible did not work on. Note the stock firmware had the same dir and Visible config as well. I also have /product/etc/apns-conf.xml in my ROM that works on Visible but the Visible APNs are NOT in that config so it's pulling it from the visible_us.pb.
It's clearly a firmware issue on some level. I suspect it's simply a matter of getting the system to use the proper APNs. It seems to me that the only way to do that is by building the ROM with the Visible APNs baked in the /product/etc/CarrierSettings/visible_us.pb, or /product/etc/apns-conf.xml, depending on where your implementation gets these default values from — or maybe it's the implementation that makes the difference, I'm not sure.
What doesn't make sense to me is why adding the APNs in settings manually had zero effect. I got the same default APNs to select from when I insert the SIM with ROM that did not work as you, StraightTalk, Verizon, and Xfinity. I also noticed that intermittently it would automatically load the VSBLINTERNET APN from the SIM but nothing would work.
I think the next step is to try to get the devs to include the Visible APNs to apns-conf.xml in the next build. I suspect that will cure this. Too bad Android make the system RO or it would be trivial.
Links that may be of interest..
This is my ROM for Pixel 4a that does work on Visible forked from ASOP.
https://forum.xda-developers.com/t/official-superioros-xcalibur-android-11.4181587/
https://github.com/daradib/carriersettings-extractor
https://www.reddit.com/r/oneplus/comments/g36mxn
https://github.com/GrapheneOS/os_issue_tracker/issues/153
Click to expand...
Click to collapse
This was extremely informative! Hopefully this will be helpful to somebody else seeking the info and scouring the web for answers.
I'm on stock OOS right now on an unlocked OP8 Pro. There is no CarrierSettings on this rom, so maybe it's just the APN file? I couldn't find a visible_us.pb file either. But I've also had a dev whip up a Magisk module that supposedly added the APN settings in, to no avail. Perhaps "baking in" is different than trying to overwrite via Magisk.
Of course, I say all of this pleading ignorance to what may be obvious to actual contributors. I have virtually no idea what I'm doing and am probably talking out my ass.
lee_d said:
This was extremely informative! Hopefully this will be helpful to somebody else seeking the info and scouring the web for answers.
I'm on stock OOS right now on an unlocked OP8 Pro. There is no CarrierSettings on this rom, so maybe it's just the APN file? I couldn't find a visible_us.pb file either. But I've also had a dev whip up a Magisk module that supposedly added the APN settings in, to no avail. Perhaps "baking in" is different than trying to overwrite via Magisk.
Of course, I say all of this pleading ignorance to what may be obvious to actual contributors. I have virtually no idea what I'm doing and am probably talking out my ass.
Click to expand...
Click to collapse
Old thread but I am just discovering (via Oxygen Updater) that the IN2015 I purchased from eBay thinking it was a US Open model, not a Visible Frankenstein's monster, will not update from 10.5.4 IN68CE via Oxygen Updater in April 2021.
I just canceled eBay return (128GB was listed as 256GB) but kept based on like new condition and assuming I could easily bootloader unlock, root, flash International Oxygen 11 and use dual SIM tray (eBay order).
Wondering if anyone has successfully updated (via fastboot flashing) a OP8 Visible version to a true carrier free model.
KnowNadda said:
Old thread but I am just discovering (via Oxygen Updater) that the IN2015 I purchased from eBay thinking it was a US Open model, not a Visible Frankenstein's monster, will not update from 10.5.4 IN68CE via Oxygen Updater in April 2021.
I just canceled eBay return (128GB was listed as 256GB) but kept based on like new condition and assuming I could easily bootloader unlock, root, flash International Oxygen 11 and use dual SIM tray (eBay order).
Wondering if anyone has successfully updated (via fastboot flashing) a OP8 Visible version to a true carrier free model.
Click to expand...
Click to collapse
I sold mine and went for the 8 pro, so I'm not aware of anything. I couldn't get it to do anything but run the visible software, unfortunately.
Bummer! Before I follow up my recent eBay return of the blacklisted OP7 Pro I received with a return of this, I guess I'll get familiar with MSM Tool and try to flash different versions of Android 10 and see if I can get something running that I can upgrade. I need non carrier restricted OOS so it will recognize two SIMs. Question is if I can even utilize 2 SIMs with a single IMEI device.
Looking like another eBay return is in my future.