Related
This post is to address how to fix two major issues on the G2X without rooting or flashing . . .
A. How to fix the APN issue which causes the default APN to jump back to T-Mobile . . . after setting up a custom APN such as Simple Mobile . . .
B. How to get the DNS to work on WiFi so that you do not need to restart the phone or switch airplane mode on and off to get it to work.
For the brief time that I had the T-Mobile G2X I notices a couple of issues that were annoying as heck. Loved the phone, but hated that LG was too slow to fix these issues, so I came up with my own fixes / workarounds. I hope that this helps out the community.
A. To fix the APN issue:
Note: Make sure you follow all of the steps exactly / correctly or else it will not work.
1. Simply download APN Manager from the Market.
2. Make a backup of your configuration using APN manager
3. Delete all of the APNs on your phone using APN manager including the T-Mobile APN. (If you ever need it again you can restore it from your backup. You did make a backup right?)
4. Configure your new one and only SimpleMobile APN and set it as the
default
5. Enjoy your Fixed G2X phone
B. To fix the WiFi DNS Issue:
Note: Make sure you follow all of the steps exactly / correctly or else it will not work.
1. Simply Download DNS Setting by Daingo from the Market
2. Run the app
3. Enter the following settings:
I.P. Address: 0.0.0.0
Subnet Mask: 0.0.0.0
Gateway I.P: 0.0.0.0
Primary DNS server: 8.8.8.8
Secondary DNS Server: 8.8.4.4
4. Save and exit
5. Enjoy your Fixed G2X phone
Notes: 8.8.8.8 and 8.8.4.4 are the I.P. Addresses for Google DNS servers, I am told that these DNS servers are blocked by T-Mobile / SimpleMobile, but they will work over WiFi with no problems and the DNS Setting app will only apply it to your WiFi settings, but if you decide to use a different app then keep that in mind.
Also, you may need to set your gateway address to your WiFi routers address, but generally if you set an address as 0.0.0.0 it will default to DHCP (or automatically assign)
This worked for me, and I certainly hope it works for you. I hope I saved many people many headaches.
Now if someone could only figure out how to calibrate the accelerometer.
The infamous developers project is up at http://www.infamousdevelopers.com
Sent from my SGH-T989 using Tapatalk 2
wifi not working
ny time i flash an ICS or JB rom on my g2x the wifi stop working but resumes and work fine when i flash GB. My baseband is March 2012. Any help guys?
mariowinax said:
ny time i flash an ICS or JB rom on my g2x the wifi stop working but resumes and work fine when i flash GB. My baseband is March 2012. Any help guys?
Click to expand...
Click to collapse
I haven't seen this issue, but typically if it won't connect a hard reboot (vol+ and power simultaneously until the set reboots) fixes it.
-- The noob says:
A bootloop is android trying to rationalize pi.
Just did that,but no positive. Its displays ( TURNING ON WIFI........eventually when it ON) it doesnt find any available wifi connections respective to yet available wifi spots......
mariowinax said:
Just did that,but no positive. Its displays ( TURNING ON WIFI........eventually when it ON) it doesnt find any available wifi connections respective to yet available wifi spots......
Click to expand...
Click to collapse
The only other thing I can suggest is to use cleanup batch or nullifier and reinstall. Can't guarantee that it would fix the issue though.
-- The noob says:
A bootloop is android trying to rationalize pi.
Think G2x Scrubber as the same as the batch and e nullifier. Because I always used g2x scrubber to wipe my phone before even installing a custom rom so I don't believe is a problem emanating from there. Anyway thanks for ur consistent aid u giving me,just it doesn't solve ma problem fella.
mariowinax said:
Think G2x Scrubber as the same as the batch and e nullifier. Because I always used g2x scrubber to wipe my phone before even installing a custom rom so I don't believe is a problem emanating from there. Anyway thanks for ur consistent aid u giving me,just it doesn't solve ma problem fella.
Click to expand...
Click to collapse
Scrubber is not the same as batch, which is not the same as nullifier. Batch is my favorite because it removes and reconstructs all partitions.
-- The noob says:
A bootloop is android trying to rationalize pi.
Ok let me try my hands on,can u help me with the link of the nullifier u talking about?
mariowinax said:
Ok let me try my hands on,can u help me with the link of the nullifier u talking about?
Click to expand...
Click to collapse
[email protected] http://forum.xda-developers.com/showthread.php?t=1854850
Cleanup [email protected] http://forum.xda-developers.com/showthread.php?t=1590523
-- The noob says:
A bootloop is android trying to rationalize pi.
Did all with the aid of the soft from the above links. But the wifi still not working. Am using ics Hellfire v1.9, am asking is there any ics good kernel I can flash to aid it working that you are familiar with?
mariowinax said:
Did all with the aid of the soft from the above links. But the wifi still not working. Am using ics Hellfire v1.9, am asking is there any ics good kernel I can flash to aid it working that you are familiar with?
Click to expand...
Click to collapse
Faux 0.14 beta AFAIK. But look in the kernel threads.
Edit: did you do fresh install after the wipe tools or restore from nandroid?
-- The noob says:
Everyone searches, but few have mastered the art of search. Google makes money because of the people of the first kind!
Yes I did, after it I restore from nandroid. But no solution, with the kernel can u give a link to e thread?
Dude...mansa has been babying you this entire thread. Showering you in helpful information while providing links that could be easily found with a quick search. Look through the stickies and find the thread with all the roms and kernels for our device and stop begging for links. Its annoying.
/rant.
-custom sig.
mariowinax said:
Yes I did, after it I restore from nandroid. But no solution, with the kernel can u give a link to e thread?
Click to expand...
Click to collapse
Your restore from nandroid is likely restoring your problem. Try a fresh install. Most folks here seem to like CM7.
Sent from my LG-P999 using xda app-developers app
As most users already know, there is a bug in the dual-SIM ICS FTF if you flash it on Xperia E, not being able to manually save APNs. Infact, not being able to create them at all.
Well, I had this and fixed this problem on xmoose's XBoosT ROM , but since its based on the stock ICS firmware, it'll work for it too.
Here's what you want to do to fix it :
METHOD 1:
Disable 'Data Transfer" : Go to Settings > (under Wireless and Networks) More.... > Mobile Networks > UNTICK 'Data Enabled'
Go Back, and turn ON Airplane Mode
Wait till its completely turned on
As soon as its turned on, turn it back OFF
Now go set up your APNs!!
Hit the THANKS !!
P.S : I believe the bug was because the ROM could not detect the MCC and MNC port numbers of your respective carrier. But this fixes it. Weird.
UPDATE: Looks like this bug exists in the Dual SIM variant too. To fix it on DS phones, follow these: OK, it seems the bug isn't device-specific. Just try either method (if Method 1 doesn't work, try Method 2)
METHOD 2:
NOTE: You'll need a working Wi-Fi network with for this!
Connect to any Wi-Fi network
Go to Settings > Dual SIM card > Untick SIM 1, and then tick it back again
Go to Settings > Xperia (TM) > Internet settings
The APNs should get downloaded and be working!
(Thanks to @TheRealSS for Method 2)
Will try this,if you are sure it works,let @UltraGamerHD note this in his Official thread under "How To"
NeoTrix said:
Will try this,if you are sure it works,let @UltraGamerHD note this in his Official thread under "How To"
Click to expand...
Click to collapse
Will Do!
KDB223 said:
As most users already know, there is a bug in the dual-SIM ICS FTF if you flash it on Xperia E SS, not being able to manually save APNs. Infact, not being able to create them at all.
Well, I had this and fixed this problem on xmoose's XBoosT ROM , but since its based on the stock ICS firmware, it'll work for it too.
Here's what you want to do to fix it :
Disable 'Data Transfer" : Go to Settings > (under Wireless and Networks) More.... > Mobile Networks > UNTICK 'Data Enabled'
Go Back, and turn ON Airplane Mode
Wait till its completely turned on
As soon as its turned on, turn it back OFF
Now go set up your APNs!!
Hit the THANKS !!
P.S : I believe the bug was because the ROM could not detect the MCC and MNC port numbers of your respective carrier. But this fixes it. Weird.
UPDATE: Looks like this bug exists in the Dual SIM variant too. To fix it on DS phones, follow these:
NOTE: You'll need a working Wi-Fi network with for this!
Connect to any Wi-Fi network
Go to Settings > Dual SIM card > Untick SIM 1, and then tick it bak again
Go to Settings > Xperia (TM) > Internet settings
The APNs should get downloaded and be working!
(Thanks to @TheRealSS for the fix for DS)
Click to expand...
Click to collapse
thank you. it works.
KDB223 said:
As most users already know, there is a bug in the dual-SIM ICS FTF if you flash it on Xperia E, not being able to manually save APNs. Infact, not being able to create them at all.
Well, I had this and fixed this problem on xmoose's XBoosT ROM , but since its based on the stock ICS firmware, it'll work for it too.
Here's what you want to do to fix it :
METHOD 1:
Disable 'Data Transfer" : Go to Settings > (under Wireless and Networks) More.... > Mobile Networks > UNTICK 'Data Enabled'
Go Back, and turn ON Airplane Mode
Wait till its completely turned on
As soon as its turned on, turn it back OFF
Now go set up your APNs!!
Hit the THANKS !!
P.S : I believe the bug was because the ROM could not detect the MCC and MNC port numbers of your respective carrier. But this fixes it. Weird.
UPDATE: Looks like this bug exists in the Dual SIM variant too. To fix it on DS phones, follow these: OK, it seems the bug isn't device-specific. Just try either method (if Method 1 doesn't work, try Method 2)
METHOD 2:
NOTE: You'll need a working Wi-Fi network with for this!
Connect to any Wi-Fi network
Go to Settings > Dual SIM card > Untick SIM 1, and then tick it back again
Go to Settings > Xperia (TM) > Internet settings
The APNs should get downloaded and be working!
(Thanks to @TheRealSS for Method 2)
Click to expand...
Click to collapse
dude i followed each and every step and it would work for the time being but after just one reboot the prob comes again all my apn accounts r gone but able to revive by following this procedure again and again. cant there be any permanent fix for this problem.
aahanable said:
dude i followed each and every step and it would work for the time being but after just one reboot the prob comes again all my apn accounts r gone but able to revive by following this procedure again and again. cant there be any permanent fix for this problem.
Click to expand...
Click to collapse
ya.. even for me after first reboot the apn disappeared but still I could connect to the internet. after some reboots (didn't count) the apn reappeared all by itself !
EDIT : now my phone saves the apn's sent as a msg from my operater. this wasn't working before ¿¿
smz2014 said:
ya.. even for me after first reboot the apn disappeared but still I could connect to the internet. after some reboots (didn't count) the apn reappeared all by itself !
EDIT : now my phone saves the apn's sent as a msg from my operater. this wasn't working before ¿¿
Click to expand...
Click to collapse
Well, atleast its working now...wasn't that the whole point?
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.
Hi!
Can anybody explain me why mobile data only works with original stock ROM?
I have tried ambasadii and king rom.
With both ROMs I was able to activate my SIM card.
With both ROMS I was able to make and receive phone calls and sms.
With both ROMs I was able to access wifi.
With both ROMS I had mobile data turned ON from settings.
With both ROMS I had correct APN data (verified from my ISP homepage)
small hint (may be unrelated): When I uninstalled too much of bloatware (probably something I shouldnt) I ended up in the same situation. I had mobile data on, and correct APN data entered.
In all cases described above:
1) web browser showed me that I am offline.
2) ping google.com told that google.com was unknown host.
3) ping 8.8.8.8 told me that it cant reach that network is unreachable
In all cases I tried to:
1) Restart phone
2) Move to location with better signal (although I tried in places where it worked with original rom)
Nothing helped. So I installed back stock ROM. Now mobile data works out of box again. With stock ROM I did not touch APN settings. It just worked.
Can anyone explain me what is happening and how this could be fixed?
It works on custom ROMs too.. depends what u didn't install from aroma installer from the custom rom..or maybe a CSC related problem but I don't think so. I'm on a s8 port ..and I tryied all the exynos ROMs out here and the mobile data worked on every one of them
^^That's correct. You are doing something wrong. I can confirm Mobile Data works fine on every single Custom ROM I have tried.
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.
------------