Related
I have very strange problem with my euro 3g xoom. When I bought it it recognized my sim card and network (T-Mobile Hungary). Now I flashed Tiamat 2.2.2 Moray. Of course I had a lot of problems with that one so I went for Hammerhead and flashed 3.2.2 stock rooted too. In every case I did a complete wipe / factory reset and a dalvik cache wipe too.
Now the actual nature of the problem is that I LOST PARTS OF MY 3G SETTINGS. This means I cannot define APN any more nor can I select service provider. Menus are missing. 3g device activation fails with infinite attempt to activate device.
As it appears to me Xoom seems not to recognize my 3g modem at all..
Any suggestion / comment is welcome. Right now I am on 3.2.2 stock rooted with of rogue ran a kernel. Oc 1.5 ghz rock solid, excellent performance no FCs at all, ONLY 3g is not working at all.
Thanks for any support in advance.
My hardware is European Xoom 3g, model nr. MZ-601 - Tegra 250.
-p0rt3r-
UPDATE_1
Tried Rogue Recovery 1.3.0 to see if the Solarnz one based on CWM 3.2.0.0-rc1 is responsible not wiping some faulty settings - no success, still missing menus in Mobile Network settings.u
For ppl who might responde to this rthred: I don't really nee a GUI for setip its okay when u guys tell me which file to edit in order to put in my APN which is very genuine: "internet"
Right now my baseband is "unknown" in the about tablet section....
-p0rt3r-
UPDATE_2
Here is what I have in the Mobile network settings:
Data enabled
Data Roaming
System select
Activate device
And no, I cannot scroll down any further etc.
p0rt3r-
UPDATE_3
Went back to Hammerhead where:
Version 2.1
Fixed all the application signatures - Google applications should update fine now.
All of the language packs are now incorporated into this rom
European 3g support should be 100% working now.
Native screenshot is back
now what I see is:
Data enabled
Data roaming
System select (change CDMA roaming mode) - I am on GSM!
Activate device.
Thats it for Mobile network settings menu.
You need to extract the telephoney files after installation. Bear with me and I will try to find the link. Be back soon.
Ok, here is the thread I think you need: http://forum.xda-developers.com/showthread.php?t=1089695
You should have backed up your original Euro 3G with CWM (Clockworkmod Recovery)
These are the files you need:
settings.db settings.db-shm settings.db-wal telephony.db telephony.db-journal from the data.img (From your original backup) You will need unyaffs.exe (use google search to get it)
1) Copy (not move) your original data.img to the same folder as unyaffs.exe.
2) Open cmd prompt and change directory to point to the folder now containing the unyaffs.exe and the data.img
3) type "unyaffs data.img" without quotes and press enter.
4)Copy all databases from /data/data/com.android.providers.settings/databases/ (above mentioned files)
5) Flash the rom you want i.e. Hammerhead etc. (Best clean install)
6) Then reboot
7) Once booted and signed in etc. open a cmd prompt pointing to adb's location
8) adb remount
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
adb push settings.db-wal /data/data/com.android.providers.settings/databases/settings.db-wal
adb push settings.db-shm /data/data/com.android.providers.settings/databases/settings.db-shm
adb push telephony.db /data/data/com.android.providers.telephony/databases/telephony.db
adb push telephony.db-journal /data/data/com.android.providers.telephony/databases/telephony.db-journal
adb reboot
If you have followed the instructions properly then on reboot you should have Euro menu for choosing GSM etc.
Hope this helps. Thanks and credit goes to lowtraxx
Phil
diigibio, thank you
diigibio,
thank you. Would be more than happy if you could provide me with som information how to get Hamerhead or any other native Tiamat rom to work on Euro 3g Xoom.
So far I can confirm that
http://forum.xda-developers.com/showthread.php?t=1183416
lowtraxx's solution is fine, all working now except Google aps updates but I do not really care for that 3g and wifi functionality is the most important, any other thing is addiional gift
waiting for your info.
-p0rt3r-
Problem solved completely?
Phil,
excellent. I cannot say how much this gonna help for me in the future. As for lowtraxx's 3.2, now I hv Hungarian market on Hammerhead I had US market... not sure if I do Hamerhead or any other Tiamat I will have my native market so I will leave this thread open for a while to see if anybody has experience with the solution you just sent me.
I also hv to say great community here, in 2 hrs u solved my problem. Thank you for this.
-Zoltan
Glad I could help. Enjoy. All the best for the New Year from the UK.
Same to u too mate from Hungary
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.
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.
If You're Like Me And Have Sprint, But Having
Issues With 4g/LTE Data On Lineage Based Roms
(Including GSI), Then Here's The Fix. I've Done This
Multiple Times, And It's Worked Great. Everything
You Need Is In The Zip As Well.
=====================================
Once The Rom Is Fully Installed And Booted,
Go To Settings, Network & Internet, Mobile Network,
Advanced, And Access Point Names. You'll Be Adding
A NEW APN, Exactly As Below. Screenshots Attached
As Well.
=====================================
Name : Sprint
APN : x.ispsn
Proxy : Not Set
Port : Not Set
Username : Not Set
Password : Not Set
Server : Not Set
MMSC : http://mms.sprintpcs.com/servlets/mms/
MMS Proxy : Not Set
MMS Port : Not Set
MCC : 310 ***
MNC : 120 ***
Authentication Type : Not Set
APN Type : default,mms,supl,hipri,fota,ims,cbs
APN Protocol : IPv4/IPv6
APN Roaming Protocol : IPv4/IPv6
Bearer : Unspecified
MNVO Type : None
=====================================
Once The APN Has Been Added, Push The 3 Dots
Up Top, And Click Save. Then Make Sure The NEW
APN Is Selected.
=====================================
https://cp.sync.com/dl/f6482b210/ab97w3j2-uevmigxz-2fpjeehn-i64ig32i
Download And Unzip The Zip Provided (sprintfix.zip). Reboot Your
Phone Into Bootloader Mode. Once In Bootloader Mode, Open A
Command Prompt / Powershell In The Zip Folder By Holding Down
Shift, Right Clicking, And Then Selecting The Option For
"Open Command Prompt / Powershell Here"
=====================================
Directions For Command Prompt:
Type In The Following Command Without Quotes "mfastboot flash modem non-hlos.bin"
Once That Finishes, Type In The Next Command, Without Quotes "mfastboot erase carrier".
Then Finally, "mfastboot reboot".
Directions For Powershell:
Same As Command Prompt, EXCEPT: change "mfastboot" to ".\mfastboot".
=====================================
If You Mess With The APN Settings, Or Change It Around, You'll Have To Do
These Steps Again.
Showing 4g On Sprint
Pictures
good news for Sprint users
What's the point of SprintDM and Carrier Provisioning Service if 4G relies on a Modem & APN? The world may never know.
Thanks for this, now Fi users can also get full Sprint access (if they need it).
murrty said:
What's the point of SprintDM and Carrier Provisioning Service if 4G relies on a Modem & APN? The world may never know.
Thanks for this, now Fi users can also get full Sprint access (if they need it).
Click to expand...
Click to collapse
The verdict is out on whether this works for FI at the moment. Currently it's a guide for straight sprint. If someone gets this working with FI, please post
This doesn't work on Project FI because APN settings are disabled by the Project FI app.
michael28056 said:
This doesn't work on Project FI because APN settings are disabled by the Project FI app.
Click to expand...
Click to collapse
I have an idea for fi, give me a few and I'll post my suggestion. On the road at a red light lol
EDIT: Working on my idea now
If someone with FI, on a lineage base (or GSI) having issues with FI days could PM me, I have an idea I'd like tried before I post it.
Message sent I'm interested in being guinea pig.
Sorry, been sick the past couple days. I got a fi sim, and tried it out. Didn't work
I switched to project fi, this fix does work.
Tried this fix for the GSI 9.0 ROM, using Project FI. Everything else seems to work just fine. Keep getting the message about SprintDM stopping anytime I try to connect to Sprint. Either through Fi Activation or using dialer codes. Anyone else have the same issue?
Nick1801 said:
Tried this fix for the GSI 9.0 ROM, using Project FI. Everything else seems to work just fine. Keep getting the message about SprintDM stopping anytime I try to connect to Sprint. Either through Fi Activation or using dialer codes. Anyone else have the same issue?
Click to expand...
Click to collapse
Yes, Sprint will only connect to 3G as well, logcat said something about missing a Java file ( or class), the file is there so I'm going to open Java file and see if I can figure anything out, don't expect much from me though.
QWZR II said:
Yes, Sprint will only connect to 3G as well, logcat said something about missing a Java file ( or class), the file is there so I'm going to open Java file and see if I can figure anything out, don't expect much from me though.
Click to expand...
Click to collapse
Sprint doesn't even connect on 3g for me, as soon as it tries to connect with Sprint, I get the SprintDM.apk has closed error. Then it switches over to Tmo. I wouldn't even really mind if Tmo worked at all in my area. Hate to go back to stock just for Sprint lol. I was going to attempt to maybe replace the SprintDM.apk in the system files. I noticed the one in there has a build date from 1969.
Not sure if that even matter, might trip up some kind of security. Like when the date on Windows is set incorrectly? Just guessing. Going to stick with the Wi-Fi/Tmo service as long as I can, don't want to end the Pie love affair yet.
Nick1801 said:
Sprint doesn't even connect on 3g for me, as soon as it tries to connect with Sprint, I get the SprintDM.apk has closed error. Then it switches over to Tmo. I wouldn't even really mind if Tmo worked at all in my area. Hate to go back to stock just for Sprint lol. I was going to attempt to maybe replace the SprintDM.apk in the system files. I noticed the one in there has a build date from 1969.
Not sure if that even matter, might trip up some kind of security. Like when the date on Windows is set incorrectly? Just guessing. Going to stick with the Wi-Fi/Tmo service as long as I can, don't want to end the Pie love affair yet.
Click to expand...
Click to collapse
I was trying that, it won't install because it's a system app and the uid (not sure on the actual error) is mismatched. Looking it up online suggested either editing manifest xml or clearing odex file from priv app, which I couldn't find a way to do successfully.
QWZR II said:
I was trying that, it won't install because it's a system app and the uid (not sure on the actual error) is mismatched. Looking it up online suggested either editing manifest xml or clearing odex file from priv app, which I couldn't find a way to do that didn't involve "lucky patcher" which won't work if you've already removed using terminal debloater.
Click to expand...
Click to collapse
I'm just sticking with T-Mobile and Wifi for now. Don't want to go back to 8.1 after using 9. Maybe someone will have a fix eventually, I'm sure that's more likely than Moto actually releasing Pie this year.
Anymore information on if this works with Project Fi? I am on Project Fi and would like to run Lineage but went back to stock for the fact that my data for Sprint and US Cellular were not working. I had to leave my phone on T-Mobile all the time which is not optimal where I drive and live. I need my phone to be able to get data in remote locations through the different carriers. I ran LOS 15.1 Unofficial, Official and LOS 16 Unofficial. None of them had mobile data on Sprint or US Cellular. Only T-Mobile. I tried installing SprintDM in system to no avail.
A thought, I have had Fi since beginning. Now with US Cellular added, it's a must for my area of coverage. I live in a remote (cell wise) area and only US Cellular works. So my Moto X4 is stock until Pie updates for all above reasons. On my Nexus 5X I could not use any Lineage based roms because of the Sprint/Fi problem. From What I have found Lineage went from complete ASOP to some else after 14.X for certain system based files for carriers. Especially Sprint APN's. My knowledge is limited on how or why. Even with my returned Pixel 2 and now Pixel (unlocked Verizon) I have to stay with Google based app+apk's roms to have ALL Fi Carriers switching with out problems. I still can't use Lineage based roms + apks to get Carrier switching to work on my Pixel. So can somebody figure out how to still use original Moto X4 Fi App packages? That may fix it.
I have all 3 networks working with 4G on my phone on the latest version of LOS 16. I had to add in some files I pulled from the latest Pixel 3 Rom. I'm not sure if all the files I grabbed are needed since I'm not an expert by any means but what I added seemed to get all three networks working.
I haven't had much chance to test auto switching because I'm generally always on T-Mo.
I also flashed the NON-HLOS.bin from the latest stock rom as well following the instructions in OP's post. I didn't bother creating the apn.
After rebooting I cleared the data for the project-fi app and let the service re-activate.
Not sure if it matters but I also have the stock gapps package installed.
I'll attach the files I used showing the paths where I copied the files to. I just overwrote whichever files were already there. I would make a twrp zip to install these files but I'm not sure how to do that if someone else wants to take a crack at it feel free.
https://ln.sync.com/dl/b36c27e30/qvzjf7v2-jwmzmqy7-uxua4x76-cjy3brq2
slaytanic said:
If You're Like Me And Have Sprint, But Having
Issues With 4g/LTE Data On Lineage Based Roms
(Including GSI), Then Here's The Fix. I've Done This
Multiple Times, And It's Worked Great. Everything
You Need Is In The Zip As Well.
=====================================
Once The Rom Is Fully Installed And Booted,
Go To Settings, Network & Internet, Mobile Network,
Advanced, And Access Point Names. You'll Be Adding
A NEW APN, Exactly As Below. Screenshots Attached
As Well.
=====================================
Name : Sprint
APN : x.ispsn
Proxy : Not Set
Port : Not Set
Username : Not Set
Password : Not Set
Server : Not Set
MMSC : http://mms.sprintpcs.com/servlets/mms/
MMS Proxy : Not Set
MMS Port : Not Set
MCC : 310 ***
MNC : 120 ***
Authentication Type : Not Set
APN Type : default,mms,supl,hipri,fota,ims,cbs
APN Protocol : IPv4/IPv6
APN Roaming Protocol : IPv4/IPv6
Bearer : Unspecified
MNVO Type : None
=====================================
Once The APN Has Been Added, Push The 3 Dots
Up Top, And Click Save. Then Make Sure The NEW
APN Is Selected.
=====================================
https://ln.sync.com/dl/f6482b210/ab97w3j2-uevmigxz-2fpjeehn-i64ig32i
Download And Unzip The Zip Provided (sprintfix.zip). Reboot Your
Phone Into Bootloader Mode. Once In Bootloader Mode, Open A
Command Prompt / Powershell In The Zip Folder By Holding Down
Shift, Right Clicking, And Then Selecting The Option For
"Open Command Prompt / Powershell Here"
=====================================
Directions For Command Prompt:
Type In The Following Command Without Quotes "mfastboot flash modem non-hlos.bin"
Once That Finishes, Type In The Next Command, Without Quotes "mfastboot erase carrier".
Then Finally, "mfastboot reboot".
Directions For Powershell:
Same As Command Prompt, EXCEPT: change "mfastboot" to ".\mfastboot".
=====================================
If You Mess With The APN Settings, Or Change It Around, You'll Have To Do
These Steps Again.
Click to expand...
Click to collapse
The sprint-fix link is broken. Do you have a copy of it?
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.