Is anyone running the most current snapshot? I installed it and lost reliable mobile data. It looked promising at first but even after a factory reset with a sense ROM I couldn't resolve it.
To start, I'd just like to know if it's possible with this release.
karunamuni said:
Is anyone running the most current snapshot? I installed it and lost reliable mobile data. It looked promising at first but even after a factory reset with a sense ROM I couldn't resolve it.
To start, I'd just like to know if it's possible with this release.
Click to expand...
Click to collapse
Im running that snapshot on a M8 w/ Verizon. I had to go into Mobile Networks -> Access Point Names ->Reset to default; in order for LTE to work. I was only getting 3G.
I continue to experience mobile data issues periodically & have to do the previous steps to get it to work again.
I did a dirty flash from the stock ROM, so I may try wiping everything & flashing to this build again. (or trying the latest CM 13 nightly.)
I hope this helps.
Thanks for confirming my experience. I'm wondering if the CM developers are testing with Verizon. My experience with their most recent builds has been pretty bad- especially with mobile data. It's always a bummer when older versions work better than newer ones.
I am running the CM13 nightly builds based on android 6.0.1 and so far they have been running great. I have specifically flashed the 12-25-15 & 12-26-16 builds. The only issue I have had is that occasionally the WiFi does not want to connect after a reboot, but toggling airplane mode fixes it.
Related
The Problem/Symptoms: I've been running a version of last CM10.2 for the past year. On February 20th, I was able to send a single SMS and then subsequent texts failed. I could still receive SMS, send/receive MMS, send/receive calls and send/receive data. If I toggle airplane mode/reboot I can send another SMS and then subsequent sms are undeliverable.
What wont work: Flashing to CM11 does not change the issue.
Disabling Voice+ does not change the issue
Factory Reset does not change the issue
Workarounds: Toggle Airplane mode
Switching Mobile Network to CDMA only (not permanent)
Change your number to a different area code
Going back to a Touchwiz based ROM
The Solution
net-cat said:
Alright. I think I've refined my process and it results in having a newer radio as well as not having to ODIN things or do dd commands.
NOTE: This isn't fully tested. When I did this, my phone wasn't showing the issue. I did this after doing my original procedure, but the GPS stopped working after I updated the radio from VRALF2 to VRBMB1. You shouldn't need to do the original procedure for this to work, but I haven't tested that. At the very least, the original procedure still works and this one can be used afterward if you need the newer radio. (GSM support...)
Ideally, we'll want to get to a procedure that doesn't use ODIN or dd. Hopefully this is a step in that direction.
Requirements:
A rooted stock ROM of the VRUCML1/4.3 vintage. I used Scott's Stock Rooted Knox Free VRUCML1 - 4.3 - DeOdex - V2. (Thread here.)
VRBMB1 AIO Flash, available here. (Thread here.)
I'm going to assume you know how to boot into and use recovery.
NOTE: Do NOT let the stock ROM install any updates.
Starting with my CM11 M3 install, I did a nandroid backup. (Recovery is CWM Touch 6.0.4.5, but I doubt that matters.)
Flash the VRBMB1 AIO.
Wipe data and cache.
Flash the stock ROM.
Boot into the stock ROM.
The reprovisioning seems to happen as a part of ROM's initial boot up.
Send a few text messages to test. (I sent them to Twitter.)
Launch the Maps application, turn on your GPS and let it get a lock. If you don't, when you boot back into your ROM, you probably won't have working GPS.
This would be a good time to back up your IMEI if you haven't already done so.
Reboot into your recovery, wipe data/cache and restore your nandroid backup.
At this point, you'll be running your preferred ROM with a less archaic radio than my previous post.
DO NOT UPGRADE YOUR RADIO. The moment I upgraded my radio, the problem came back!
CM11 M3 will work just fine with the old radio. I've rebooted several times over the last few hours and it still works fine. (Time will tell if it's a long term fix or not.)
Click to expand...
Click to collapse
buffal0b1ll said:
I put a MB1 aoi zip in my dropbox for you. It's from invisblek.org which isn't working now for some reason https://www.dropbox.com/s/7b1aqspo40fxl00/VRBMB1.aio.zip
Click to expand...
Click to collapse
Notes: There are threads for the S4 with this identical problem. All updated information I have seen is listed above. If anyone knows more please post as I am going to keep this updated. If this does/doesn't work for you please post and let the community know. Feel free to hit the thanks button if it works for you.
This exact thing happened to me. I tried many fixes with no luck. After hours of hacking around in settings, I found a ROM of verizon's 4.3 OTA update and flashed that through ODIN. My texts are working just fine again. Kind of a cheap method of fixing my problem. I wish I could have taken more time to find a fix, but I needed to be able to communicate with people that day.
Stock 4.3 is kind of lame:
-4.3 is killing my battery faster than ever. CM11 had me going for days without charging and now I've needed to charge everyday.
-Stock 4.3 is laggier/slower than CM11. It tends to stutter for me.
-4.3 came with a new boot loader which no developers have exploited to install custom ROMs yet. This leaves you stuck with Verizon bloat. I hate all these damn apps. Going to try to safe root & see if I can't do some cleanup work.
Enough ranting. Just wanted to let you know you are not alone with this problem. Hopefully someone will figure it out. Missing my cyanogen mod already
It seems this problem has happened on other phones also running Cyanogenmod. I found this thread http://forum.xda-developers.com/showthread.php?t=2654822
It looks like the symptoms have all showed up at the same time approximately. (February 19th, 2014). Still looking for a better answer than going back to stock TW...
Edit: And another thread http://forum.xda-developers.com/showthread.php?t=2659280 This one suggests its all AOSP roms. But it seems many people are unaffected... I don't understand why/how.
edit2: and another thread http://forum.xda-developers.com/showthread.php?p=50627899
Just looking for more info
Sent from my SCH-I535 using Tapatalk
Dex954 said:
Just looking for more info
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
SO this is the current status that I know.
The problem happens for everyone with a 570/717 area codes + on verizon + running Cyanogenmod (possibly any AOSP) + while connected to LTE which started on Feb 20th (the day before KitKat came out offically).
Current Workarounds:
Switch to TouchWiz based Roms
Switch your radios to be CDMA only
Call verizon and switch your number to a different area code
I know the workarounds all suck but that all I know for now. Switching SIM cards won't work. If I anyone knows anything more please feel free to let me know.
I'm 717
Sent from my SCH-I535 using Tapatalk
I have still be unable to find a solution for this issue. I think I have to give up on CM and go back to a TW based. If I hear anything new I'll update the post but I don't have the time to be wasting on my phone at the moment. If someone finds or hears of a fix or if it magically goes away as it started, please post it.
And spread the word if there are any other ROMs that this is occurring on. It seems the pool of those affected is just too small.
I have already had to give up. Been running slows tw. I take it Verizon didn't get back to you?
Sent from my SCH-I535 using Tapatalk
Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658
DreamFX said:
Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658
Click to expand...
Click to collapse
Godspeed my friend.
Anyone try aosp to see if fixed yet?
Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.
capt730 said:
Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.
Click to expand...
Click to collapse
I try every other day. 717 for me. Remaining hopeful it's fixed... One day...
What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app
capt730 said:
What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It won't. It isn't software dependent. People who had already flashed builds prior to the 20th magically had issues starting on that date, so it isn't a problem with new builds, and it only happens to those in the 717-570 areas so it isn't a problem with AOSP code. It has to be a Verizon network issue, I just have no idea how.
Sent from my SCH-I535 using XDA Premium 4 mobile app
I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.
capt730 said:
I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.
Click to expand...
Click to collapse
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.
I'm ok with using CR8, Beans or other stock roms. Can't see paying for LTE and not using it lol. Was curious to see how aosp has been coming along and sms was really the only issue I was having.
Obaterista93 said:
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.
Click to expand...
Click to collapse
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,
Whisk_33 said:
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,
Click to expand...
Click to collapse
Basically. I've talked to a few friends who have worked for carriers and stuff, and everyone is stumped as to how something like this can even happen. Luckily I'm pretty much always in WiFi so I can survive on CDMA only.
I love Cyanogenmod, very much so. I downloaded the stable 10.1 build for my phone and it was mostly rock solid. When 10.2.1 come around I was pumped. I downloaded it and immediately encountered force closes out the bum. I switched back and a month later tried again. It was a slightly better experience as I realized I forgot to flash the 4.3 Gapps with my original attempt, but force closes cluttered my screen daily. I want to be able to upgrade, but the ROM just seems completely unstable for my phone. Has anyone experienced these things on their phone? Has anyone fixed these problems? Can anyone recommend the most stable and most up-to-date ROM even though stable and up-to-date rarely go hand in hand.
stjake said:
I love Cyanogenmod, very much so. I downloaded the stable 10.1 build for my phone and it was mostly rock solid. When 10.2.1 come around I was pumped. I downloaded it and immediately encountered force closes out the bum. I switched back and a month later tried again. It was a slightly better experience as I realized I forgot to flash the 4.3 Gapps with my original attempt, but force closes cluttered my screen daily. I want to be able to upgrade, but the ROM just seems completely unstable for my phone. Has anyone experienced these things on their phone? Has anyone fixed these problems? Can anyone recommend the most stable and most up-to-date ROM even though stable and up-to-date rarely go hand in hand.
Click to expand...
Click to collapse
Look in the CM11 thread, the nightlies are pretty stable for the most part and most us using it use it as a daily driver. You MUST perform a full wipe when installing a ROM, even when moving between point releases. If not, you'll encounter problems. GApps must also be flashed after the ROM has been flashed (assuming you want to use Google)
CWGSM3VO said:
Look in the CM11 thread, the nightlies are pretty stable for the most part and most us using it use it as a daily driver. You MUST perform a full wipe when installing a ROM, even when moving between point releases. If not, you'll encounter problems. GApps must also be flashed after the ROM has been flashed (assuming you want to use Google)
Click to expand...
Click to collapse
Yeah I figured that I need to wipe everything and install the proper GApps after my first attempt at 10.2 which to my credit I did do on my second try. Is there a particular nightly release that seems more stable than the rest? To put this in more context, I travel alone from college to various other places often a bit and my college is situated in almost a black hole of service for Verizon so I tend to take reliability over cutting edge even though I very badly want the newest and greatest. I'm on spring break so I'll try the newest nightly and back up my phone. Luckily I have a ton of space on my phone so I can always have a stable back up ready to be flashed on the fly.
stjake said:
Yeah I figured that I need to wipe everything and install the proper GApps after my first attempt at 10.2 which to my credit I did do on my second try. Is there a particular nightly release that seems more stable than the rest? To put this in more context, I travel alone from college to various other places often a bit and my college is situated in almost a black hole of service for Verizon so I tend to take reliability over cutting edge even though I very badly want the newest and greatest. I'm on spring break so I'll try the newest nightly and back up my phone. Luckily I have a ton of space on my phone so I can always have a stable back up ready to be flashed on the fly.
Click to expand...
Click to collapse
By their very nature, Nightlies are not considered stable in the strictest sense of the word. For most of us, they have been. But if you need reliability over cutting-edge, I'd stick with 10.2 or one of the CM11 Milestone builds (however, the RAZR HD only has one that I know of, CM11-M2).
My personal take is that given you're in an area with poor reception, choosing CM11 over CM10.2 (for example) wouldn't give you any better results over the other. Signal is signal.
My suggestion, given your circumstances and criteria, would be to stick with 10.2 but do a FULL backup via Recovery of your stock ROM (or whatever you're using instead of CyanognMod) and then do a FULL wipe of the following (and only these):
- user data
- /system partition
- /cache partition
- dalvik cache (usually found under Advanced in CWM recoveries)
Your phone will be in an unusable state after this. From here, still in Recovery, flash CM10.2 and then the appropriate GApps (make sure you choose the right one; a 4.4.2 GApps isn't suitable for a 4.3 OS) and reboot. If memory serves, CM10.2 is Android 4.3.1
If you're still having problems, you can restore your backup in Recovery or worst case, RSDLite the appropriate SBF for your phone to return to the carrier-stock ROM. But be aware if you chose the RSDLite path, you will lose everything. Basically it'll be like day-1 when you got the phone
Unroot help!!!
Hi I am trying to figure out how to unroot my Droid Razr HD...I bought it used from my buddy who upgraded and before we met up to make the deal I didn't know till after; that he rooted it and won't tell me how to unroot. I have only ever rooted one phone with his help and that was my thunderbolt. This phone is running CM 11-20140218-NIGHTLY-xt926. I want to bring it back to stock rom but have yet to find anyway to do that...it would be awesome if you guys could help me!!
Lanevox said:
Hi I am trying to figure out how to unroot my Droid Razr HD...I bought it used from my buddy who upgraded and before we met up to make the deal I didn't know till after; that he rooted it and won't tell me how to unroot. I have only ever rooted one phone with his help and that was my thunderbolt. This phone is running CM 11-20140218-NIGHTLY-xt926. I want to bring it back to stock rom but have yet to find anyway to do that...it would be awesome if you guys could help me!!
Click to expand...
Click to collapse
Find the FXZ you want to flash and use RSD or House of Moto to flash it.
Can someone please help me out with an issue I am having...?
I can't seem to get Service after installing an AOSP ROM. I have been messing around with this issue for several days now. When I install a 'NON AOSP' ROM such as 'the 'MOAR ROM' it works fine, but then I go to in recovery (Newest TWRP or Newest Philz Touch) and do all of the required 'Wipes' then Install an AOSP ROM like 'Fusion', 'PAC' or the most recent 'CM11 Nightly' and I do not get any Cellular Service (WiFi is fine) and I have been looking for answers for several days and I can't seem to find any.
Can someone please help me out and let me know what I need to do, or point me to the right direction?
Thanks in advance for any help and/or resources that anyone can provide me with. It will be greatly appreciated.
Phone:
Sprint Samsung Galaxy S5 NE5 (Rooted with Knox Tripped :crying
MOAR ROM Installed / Touchwiz Interface.
_________________________________
My Web Design Portfolio
Same was happening to me on philz recovery . so I install trwp for sprint/Verizon . then I installed trwp manager from play store . I install the PAC ROM from in the app and let it wipe it self . and that did the trick at least for me. I have tried many ways like your self. Nothing work that's the only way I got it working. Hope that help.
Sent from my unknown using Tapatalk
I'll give it a shot and see what happens. Thanks for the tip...
Has anyone else had this problem? If so, can you post anything you did to get it working...
My Phone Thanks You...
Im having the same problem on both TW and AOSP. If I mess around with the connection settings I can get a signal but when I reboot its lost.
Ive tried both recoveries and its the same on both. Ive tried flashing modems but that did nothing
EDIT: Seems that any kernel that I flash breaks my phones signal, I need to test further to see what part of the kernel flash is causing this.
Whenever I download klte roms I had that problem. I could receive data and text, but I couldn't send any. I used Google voice until I flash kltespr roms. once I flashed the specific roms for our device it worked. Though I had to install ktoonez's version of twrp to get them to flash. That file can be found on the AICP thread.
Shad Stang said:
Whenever I download klte roms I had that problem. I could receive data and text, but I couldn't send any. I used Google voice until I flash kltespr roms. once I flashed the specific roms for our device it worked. Though I had to install ktoonez's version of twrp to get them to flash. That file can be found on the AICP thread.
Click to expand...
Click to collapse
I think you guys need to flash an APN package with klte roms. Kltespr roms should not have this problem, but if you run into it flashing the APN package shouldn;t hurt there either. Not sure if there is still an APN zip floating around, you may have to manually fix your APN.
It turns out that the custom kernel I was using broke the signal for some reason. Other than that, I had no problems as long as I flashed a kltespr rom. Klte roms worked for data if i used a virgin mobile apn, but there was no texting or calling.
I attached the flashable zip I used to get the virgin mobile apn. I would recommend flashing it right after you flash your rom.
having this same issue also..
i have tried several things.. going back to complete stock and working forward
no matter what i do i get no service on any AOSP rom.. im going to try this apn fix. hopefully it doesnt further break anything lol
Anyone figure this out yet? I've tried about 4 aosp roms and no luck.
PacMan rom with PA Gapps and Ktoonsez kernel worked for me. None of the others did so it must be a ROM issue.
Part of the reason kltespr was de-unified was because of issues like this.
When I'd fix something it would break something else for T-mobile or international.
So I would recommend sticking to kltespr builds for the time being.
Hopefully some work I'll be putting in soon will help get this back in gear.
garwynn said:
Part of the reason kltespr was de-unified was because of issues like this.
When I'd fix something it would break something else for T-mobile or international.
So I would recommend sticking to kltespr builds for the time being.
Hopefully some work I'll be putting in soon will help get this back in gear.
Click to expand...
Click to collapse
I couldn't get data on any kltespr builds except Pac Man and even then I lost data the next day for some reason. The new lollipop build has data working for me even though it's "GSM only" so just hoping it stays that way haha Waiting on fixes for battery drainage and I'll run it daily
Hi,
I am rooted using the TWRP kltespr version. I flashed CM11 4-07 nightly and at first lost the ability to make calls but still had LTE data (go online, get email). After a reboot I lost both completely. Can't make calls and can't get data. I have done a complete wipe and clean installs of a few nightly versions. They all install without errors but I still can't get connected to my network. I have done several factory resets. Under mobile network data is enabled, I have tried "prefered network type" set to LTE, Global and 3G. Still no network.
Any help/suggestions getting my network connection back will be appreciated,
thank you
Search for how to fix your APN. I would say to upgrade your version too, the latest build from October does not have this problem anymore I believe.
Just about every AOSP rom is bssed on CM 11 now if your using offical CM 11 rom. I have flased several official. yhey yo spell out KLTESPR. but I chsnged the updater script no problem
Hi there,
Everything was working just fine, but since I switched to a new carrier I can't get the network back as soon as my OP looses it (subway for example). I have 4G as my favorite internet mode and my APNs are good.
Only a full reboot fixes it, not even a soft one. What can I do?
I use the lastest CM 12.1 S rom (YOG4PAS3JL)
Maybe I should try to flash Oxygen's modem? http://forum.xda-developers.com/one...dio-updated-modem-radio-files-oxygen-t3072516
It seems many users are affected by the problem but I didn't find a real solution, hence my post.
Thank you!
After a long investigation, it seems that the OPO is having trouble switching for and from 4G. I solved it using 3G as my preferred network, but I'd have loved using 4G
reinstall the system... u can google fastboot images for opo... flash them through CMD
I've tried 3 ROMS and at least 4 modems so I think I've tried eveything that's available atm
I have had the same problem for some time now. But no reliable solutions found. Have tried various versions of ROM and Radio. Currently using 44S and CM 12.1 S (YOG4PAS3JL).
Lamner said:
Hi there,
Everything was working just fine, but since I switched to a new carrier I can't get the network back as soon as my OP looses it (subway for example). I have 4G as my favorite internet mode and my APNs are good.
Only a full reboot fixes it, not even a soft one. What can I do?
I use the lastest CM 12.1 S rom (YOG4PAS3JL)
Maybe I should try to flash Oxygen's modem? http://forum.xda-developers.com/one...dio-updated-modem-radio-files-oxygen-t3072516
It seems many users are affected by the problem but I didn't find a real solution, hence my post.
Thank you!
Click to expand...
Click to collapse
kingalpha said:
I have had the same problem for some time now. But no reliable solutions found. Have tried various versions of ROM and Radio. Currently using 44S and CM 12.1 S (YOG4PAS3JL).
Click to expand...
Click to collapse
For how long have you been using that? Did that fix the problem?
This is very annoying!!!!
xupi said:
For how long have you been using that? Did that fix the problem?
This is very annoying!!!!
Click to expand...
Click to collapse
Didn't fix the problem. Finally reverted back to Oxygen OS. Complete reinstall, including bootloader, storage, everything. Got it done at OPO service centre. Much better reception now.