Okay,
Some of you may have had the issue of losing activation when running a CM12 based rom and noticed that the newest builds of most of them are missing the CDMA subscription type option in Mobile Networks. This has lead to needing to keep a nand backup of an old build with the option, and a backup of a sense rom, and finally,a backup of the newest build so you can restore the old cm12 build, change RUIM/SIM to NV, and back, turn on roaming, switch to global, walk backwards in a circle 4 times, bark like a dog, etc.
So I want to test a theory.
Grab a build.prop editor
Change the line ril.subscription.types=NV,RUIM to ril.subscription.types=SIM and go into settings->Mobile Networks and make sure preferred network is set to global. Reboot, then change it back to ril.subscription.types=NV,RUIM and reboot again. Try making a call or sending a text. If it works, great! Stop here and let me know. If it still requires a sense rom to activate, but overall works by eliminating the extra step of keeping an older cm12 build backup around, or if it doesn't work at all let me know.
I think I'll test this. Sick of sense but hate losing service randomly. I'll report back.
Related
Alright.... I dont have enough posts to put this in the development thread. I took the omni rom ota update and like a few people my phone rebooted to the invalid software please take this phone to a verizon store..... I odined back to stock and eventually got things back to normal or so I thought. Now it seems that anytime I am on an aosp based rom my signal is borked. When I am on a touchwiz rom everything seems fine. It does seem to want to go to global under mobile networks and my singal strength seems way lower than normal also the connection seems much slower. So i odined back to stock again and backed up the apns went back to liquid and restored apns. That didn't work. I can receive and make calls no problem. I can receive sms and mms. If i go into mobile settings and change it from global to LTE then turn on and airplane mode it will send messages for maybe a minute then it cuts back out. I am assuming my next step is to get a new sim card. If anyone has any ideas I would appreciate some input. I have been searching this and other sites since the 24th when I took the ota and have had no luck. I have been on this site and fiddling with my androids since the original droid. I didn't think I was a total noob but this has me stumped.
I am on MDK and my IMEI seems fine I actually Just noticed my IMEISV says "00". So help please!
You're having problems with SMS?
Try going from TW to the GPE rom and see if if keeps working on that, then if it does go from that to whatever rom you want.
Oishikatta said:
You're having problems with SMS?
Try going from TW to the GPE rom and see if if keeps working on that, then if it does go from that to whatever rom you want.
Click to expand...
Click to collapse
never thought of the gpe rom. seems to have worked. thank you very much for the help.
OK, so allow me to give the situation:
I have a stock build that I flashed.
However, after normal activation - you know how it should switch to Sprint boot and shutdown animations? Didn't happen.
Sprint Zone also doesn't show correctly, says it's still configuring. Network shows LG. Wifi calling, *2 and Connections Optimizer okay.
Other bloatware doesn't seem to have installed.
I'm pretty sure that the CSC/carrier data is missing but does anyone have any ideas on how to resolve this - other than use a different build?
garwynn said:
OK, so allow me to give the situation:
I have a stock build that I flashed.
However, after normal activation - you know how it should switch to Sprint boot and shutdown animations? Didn't happen.
Sprint Zone also doesn't show correctly, says it's still configuring. Network shows LG. Wifi calling, *2 and Connections Optimizer okay.
Other bloatware doesn't seem to have installed.
I'm pretty sure that the CSC/carrier data is missing but does anyone have any ideas on how to resolve this - other than use a different build?
Click to expand...
Click to collapse
I'm not quite sure what you're taking about but...
if it's stock based, ##RTN# should help with activation. But...
If you're showing LG as the network, that's something that happens with a build.prop edit. I think it was OPEN and Global that caused that to happen.
Activates fine, just not applying the correct CSC for the apps. Functionally everything seems A-OK.
I'll just chalk it up to this particular build.
I did the build number Darklord N5 (looking at settings), Kernal 3.4.0 Kernal now I only have data for a few min then it say's no data connection? It's a Sprint Note 3 and still using Sprint. But the model number no longer says SM-900P and now says SM-9020C. The file I used was DarkLordN5.RC2.1.SamsungViet.vn Sorry I'm a little new to this but I do tend to follow directions well.
It's like Sprint lets me have data and then see's something it doesn't like about the mod and shuts off my data. It always works at first then goes away within 5 min and says no data connection and roaming is turned off. And if I get data again will I still have LTE? So far I just saw 3G when it was working.
Other than that I love the update but I can't do without mobile data! Please help. I've looked everywhere I could think of on here and it's been almost two weeks without data.
Thanks!
Jim
Bump??? Please help???
Bump??? Please help???
That rom is kinda old and has bugs. If you want to use the latest note 5 port, I recommend http://forum.xda-developers.com/gal...-base-n9200zcu2apa1-stablefast-31-01-t3308842
It's based off the last version of darklord's rom and tweaked/fixed it's issues like youtube lag...
It's tricky to get data from it. I use Ringplus so it might work without tinkering with sprint natively.
Just install rom normally, with SPR csc, and see if you get data like that.
If it doesn't here's what I did:
I had to install it with the XAS csc (the SPR csc won't let me change apn's but you're free to try). I then switch radio to cdma or anything else until the apn settings show up AND can be edited in Mobile Networks settings(LTE radio won't me edit). Then I delete all apn's because it won't use the custom ringplus apn i put in by default(yes, I choose it and it still won't use it). Once i'm all done, i set radio back to "cdma/gsm/lte" to get back lte/cdma data (for some reason the "cdma/lte" setting won't work for me). I used app's to get me to the radio and apn settings. There's a few out just take your pick.
Might take some trial and error to get the apn's to show up but in the end i have zero issues with data. good luck.
Thank you very much for your detailed reply. I was wondering if it was old. But being pretty new to this I'm going to have to do some research to try to digest all you said! Although yesterday I did successfully replace the screen/chassis of my old Note 3 which required switching over many components. Now just waiting on a new power on switch. So I'll be back.....
I wanted to post this for people who want to try out MM on the LS990 and have fully working 3G and 4G/LTE data on a Sprint network. I'll explain the exact conditions that I personally went through to get it working.
I CANNOT GUARANTEE THAT THESE STEPS WILL WORK FOR YOU. YOU MAY EXPERIENCE PROBLEMS AS MENTIONED BELOW.
The flashing and setup:
What I personally did was flash BareCee v2 and then updated the PRL and Profile. Afterwards, I dirty flashed BlackSoulxxx's v30b MM port (see: http://forum.xda-developers.com/lg-g3/development/rom-lge-d855-android-marshmallow-ported-t3285025). I rooted the port with SuperSU 2.52 BETA via TWRP. Once I got to the home screen, I was greeted by a notification that stated that I need to update Google Play services. I updated it. Then I confirmed my appropriate APN settings. I'm on RingPlus, so this was important for me to even get mobile data at all.
The fix:
Once I went through all that, I edited /system/build.prop using Solid Explorer with the following lines:
ro.product.model=LGLS990
ro.build.target_country=US
ro.product.locale.language=en
ro.product.locale.region=US
ro.cdma.home.operator.alpha=Chameleon
ro.cdma.home.operator.numeric=310120
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
Click to expand...
Click to collapse
The following two lines might be disabled in your build.prop. If they are active, ensure it's set properly as listed below. It was disabled on mine, so I did NOT touch them or re-enable them:
ro.telephony.default_network=10
telephony.lteOnCdmaDevice=1
Click to expand...
Click to collapse
If you don't care for having your phone unlocked for Global/GSM use, you can edit the following lines to get the Sprint 3G/LTE, airplane mode, etc. status bar icons and branding (as well as disable the Global/GSM network option):
ro.build.target_operator=SPR
ro.carrier=Sprint
Click to expand...
Click to collapse
After you have edited the build.prop, give it a reboot and toggle data/airplane mode in the quick toggle/notification pull-down menu until you get data to finally turn on. Once it switches on, it'll work until your next reboot, I believe. You will need to fiddle with the toggle again once you reboot. This is a bug due to the ports. There's no known fix for this besides dirty flashing over BareCee v2, but I can't really say for certain if everybody will have this fixed just by dirty flashing. Dirty flashing also allows the settings switch and data settings panel to work correctly (sometimes).
From what I can tell, ro.cdma.home.operator.numeric is the key factor for getting 3G data to work properly.
Negative repercussions:
You may have issues with Messaging.app and weather.app NOT working/crashing after launch IF YOU DIRTY FLASH. I'm not sure how to fix this issue other than with a CLEAN FLASH.
Others have expressed issues with google play services not working or force crashing and causing the OS to be unstable. Clean flashing fixes this problem, usually.
Fulmics 3.1 and xpirt was the source of this fix and it was stated that this will be included in the next version of Fulmics 3.X. I personally cannot use Fulmics because it's highly unstable for me. It overheats my phone and there's heavy lag with poor battery life.
Other Notes:
I would like to see somebody clean flash BlackSoulxxx's port or Fulmics 3.1 and try this out. I'm too busy to keep flashing/testing and everything I need is working (I don't bother with the stock Messaging app and weather app works fine for me). Please report back if you do this and let us know what happens. I suspect this is the best possible outcome for avoiding force crashes, but it also may mean that the data may not work properly, even after this fix.
Hope this helps somebody. It took me weeks to resolve this issue.
Thanks to:
blacksoulxxx
xpirt
6th_hokage
jglm4u
This should get its own post: The MM port is unlocked for GSM by default, I believe. Fulmics 3.1 is the same.
No luck for me..
Whenever I make all these changes on a clean flash of fulmics 3.1, I get constant FC's of com.android.phone
spanky34 said:
No luck for me..
Whenever I make all these changes on a clean flash of fulmics 3.1, I get constant FC's of com.android.phone
Click to expand...
Click to collapse
Not sure why you're getting phone FCs, but I'm like 99% sure it may be a fulmics issue. I'm using the blacksoulxxx port right now.
Also, confirmed bug:
ro.build.target_operator=SPR
ro.carrier=Sprint
These two lines cause media services to crash for a media player stuff. Facebook messenger videos and Google hangouts voicemail audio crashed when it searches for sprint-specific players. Strange as hell.
Couldn't you just make a flashable zip to fix the build.prop?
I recently left the stock rom to install custom firmware on my Galaxy S5 (SM-G900T). I am noticing some strange behavior with LTE, and was wondering if anyone else was experiencing a similar issue. With LineageOS 14.1 (klte) currently, upon rebooting the device, it remains on HSPA+ for at least 10 minutes or so before connecting to LTE. If the device is kept running, and is not turned off or rebooted LTE will persist just fine, even if I change the radio selector to 3G or 2G, it will always go back to functioning LTE. On the Stock rom, I never experienced this issue. I previously ran Android 6.0.1, before upgrading to LineageOS. I have also tried with Cyanogenmod 13 to compare, and experienced the exact behavior. I have tried using the dialer menu on LineageOS (*#*#4636#*#*) to see if changing the radio settings makes any difference, sometimes it will make the device connect to LTE faster, after a reboot. If anyone has any insight on how to correct this that would be great. Thanks.
Which firmware version are you on?
invisiblewave said:
Which firmware version are you on?
Click to expand...
Click to collapse
My current firmware is G900TUVU1GPE1. I am also currently running cyanogenmod 13. I flashed back to stock today to take a look at some settings in the service menu. I tried setting LTE Band preference to 17, and it made no difference upon returning to cm 13.
My current "workaround" in cyanogenmod, after a reboot or poweroff, is to go to the dialer menu (*#*#4636#*#*), change radio to LTE/GSM/CDMA, turn off the radio, select LTE/GSM, turn on the radio, then immediately reboot. After a reboot, I can go to Cellular network settings, toggle 3G, then toggle LTE as preferred. I now have LTE, until the next reboot or poweroff.
I'm wondering if there is something in the stock service mode that has to be set, that cyanogenmod somehow does not have access to?
Thanks
I don't recall anyone else with the same issue. I'd try the latest modem, GPK3.
invisiblewave said:
I don't recall anyone else with the same issue. I'd try the latest modem, GPK3.
Click to expand...
Click to collapse
I just tried out the latest modem (GPK3), and I am still experiencing the same problem unfortunately. I don't believe I mentioned this earlier, but the device is unlocked and I am currently using an AT&T SIM. However, I have had no issue with the LTE persisting on reboot with the stock rom though. I'm curious if an alternate rom might be beneficial, perhaps resurrection remix. Have you ever tried your device with an AT&T SIM? Thanks again.
Partially solved. I discovered now that if I toggle 3G under Cellular Networks before rebooting or turning off the device, I am able to select LTE after a reboot or power off and connect instantly. Perhaps this is somehow related to using an AT&T SIM. This is a little better than before, at least.
I had this issue on CM13, since the CM forums are now gone, it's hard to find the old threads troubleshooting these problems. Here is my solution:
Yes!
Thank you for posting this, my last post was 3 months ago on this issue and I was documenting everything I troubleshooted and getting 0 responses..
There must be something glitched with the APNs on this phone, by default I was only seeing Straight Talk with GID set as the MVNO type, after disabling this I could see more APNs and add more, but could not discard them.
/system/etc/apns_conf.xml - Delete this (you can backup just incase)
Go back to APN Settings and Reset to default, then add your APN.
Once I saw HSPA+ I restarted my phone and got LTE and the radio seems less laggy now, only have been testing for a few minutes now.
Only issue is I restarted with LTE and LTE wouldn't come back, I toggled airplane mode and immediately got LTE (unlike before where the radio would take forever just to get HSPA+)
Click to expand...
Click to collapse
You can use archive.org to view the old Cyanogenmod forums, the buttons don't usually work, so you will need to open them in new tabs.
https://web-beta.archive.org/web/20...org/topic/120995-cm13-lte-doesnt-work/?page=6
Also, if you have problems deleting that file (or simply renaming) try:
Try to use one of the following ways:
mount -o rw,remount -t rootfs /system
or
mount -o rw,remount -t rootfs rootfs /system
You also can use it for any folder that you need even root (/)
Click to expand...
Click to collapse
http://stackoverflow.com/questions/18918456/android-2-3-read-only-file-system-stuck
I'm having the exact problem you're having. But it's not just my S5 on LOS 14.1, it's also my roommate with S4 on LOS14.1 and other roommate with S3 on CM13. We're all on Ting, we all started having the same problems at the same time, exactly like you describe.
I called Ting and they told me the towers were being "modernized", and that NONE of these phones had the optimal frequencies to use their new LTE. I got a long email from them about frequency compatibility but my initial research leaves me skeptical. All these phones have the frequencies tmobile says it uses, according to wikipedia.
So, they're sending us new sim cards, which I bet is just another BS fix, just like the 100 times they had me reset my APN settings and pull my battery : p
I installed the latest LineageOS on my S5. I am now seeing network issues. I get drops after calls, and wifi enable/disable. I see a "x" on the bars in the status menu.
If I cycle data on off it seems to reconnect - on but not on full LTE .
After a google search I found what could be the cause, the Verizion radio variant was added to the KLTE builds. You can see it on that forum at reddit.com/r/LineageOS/comments/605y43/please_dont_add_verizon_variant_into_klte/
I didn't actually try the "fix" they offer there because I don't quite understand it.
I gave it a shot and installed the force_g900f_ril_blobs.zip using TWRP and can report SUCCESS. Its a fix of sorts if you are on T-Mobile using another variant like me, in this case a G900V (S5 Verizon).