Related
Can someone explain the nature of the reboots that they are experiencing? I had a reboot on Friday but it was much more then just a reboot, after the phone was finishing powering back up I had no ability to call out as if there was no service. I tried numerous battery pulls and even had Verizon do a reset on there end, nothing helped yet I was still able to receive and send data. Finally after about an hour my service was back. Then the same thing happened again yesterday, I went through the same processes with no success yet. I have tried all the different radio choices and nothing is working, does anyone have any suggestions?
Thanks!!!
Also I am rooted and using the stock rom
Bump..........
Did you do any radio flashes? I know mine rebooted on me when I was trying to flash the GB leak from yesterday and there wasn't even a signal bar...just blank space. I reflashed my radio and everything was ok.
Edit: read the last line that I missed before. I am assuming if you are on a stock rom that you didn't flash any radios (otherwise it would have been noted). Thats the only thing that I have run across causing issues. SMH
Yes, I had similar problem
I was running the Stripped Das BAMF with the new radio (same as the one that recently came out OTA) and had this no service problem twice. Since I'm in a 3G only area, I have been using CDMA auto(PRL) and use the Phoneinfo app to change it. I tried to change the network type to something else but couldn't change it. (I presume the network type is for data, but I was trying to see if changing it would affect the service). The other options were there, but I couldn't select anything other than the CDMA auto. A battery pull fixed my problem both times.
Now I'm running BAMF Remix 1.6.3 with the new radio and everything is fine. I don't change the voltages or overclock. Yesterday as I was driving around town the phone rang, but I didn't answer it. When I got home, the phone had powered down and did a reboot.
Just an additional thought. You might try doing a data wipe/factory reset to see if that helps. Of course, you lose your settings that way, so back up first.
Ok, first of all I'm an old veteran at flashing ROMs. Secondly, I know about the SIM card reset, where I restore my phone to factory settings and enter a number in the dialpad (can't remember it, have it written down) to reset your network connection. The thing is, I have a few hours left at work before I'll have time to attempt that, so I wanna explain this issue to the community and see if there's an easier option.
So, to start, I have been running the 01/02 build of Bean Stalk 4.4.2 for a few weeks now with no issue. I'm also on the latest modem, VRUCML1, which I again have been running for a while with no issue.
Today I decided to try out some newer builds, so I made a nandroid and then flashed the new Carbon 4.4 build (01/19). This was when I had my first network issue, where it had me stuck in roaming even though I was in my home. So, thinking the ROM may still have some issues, I switched to a newer build of Bean Stalk (01/17). While I now had mobile data back, I found that my phone was unable to send SMS.
I finally restored my nandroid, yet now I find that this problem is still persisting. I flashed the previous modem, VRBMF1, and the problem still persists.
The weirdest thing, though, is that even though it won't send SMS, my mobile data works fine. I'm able to browse the web at full LTE speeds, but not send SMS.
Edit: After a recent test, it seems phone calls won't work either. So my phone seems to be handling the LTE functions well enough, but is having trouble with the CDMA/EVDO part of the antenna.
Anyone who has any advice, please help. Like I said, I'm inclined to do a SIM reset, but won't be able to until much later tonight.
TenderloinShadow said:
Ok, first of all I'm an old veteran at flashing ROMs. Secondly, I know about the SIM card reset, where I restore my phone to factory settings and enter a number in the dialpad (can't remember it, have it written down) to reset your network connection. The thing is, I have a few hours left at work before I'll have time to attempt that, so I wanna explain this issue to the community and see if there's an easier option.
So, to start, I have been running the 01/02 build of Bean Stalk 4.4.2 for a few weeks now with no issue. I'm also on the latest modem, VRUCML1, which I again have been running for a while with no issue.
Today I decided to try out some newer builds, so I made a nandroid and then flashed the new Carbon 4.4 build (01/19). This was when I had my first network issue, where it had me stuck in roaming even though I was in my home. So, thinking the ROM may still have some issues, I switched to a newer build of Bean Stalk (01/17). While I now had mobile data back, I found that my phone was unable to send SMS.
I finally restored my nandroid, yet now I find that this problem is still persisting. I flashed the previous modem, VRBMF1, and the problem still persists.
The weirdest thing, though, is that even though it won't send SMS, my mobile data works fine. I'm able to browse the web at full LTE speeds, but not send SMS.
Edit: After a recent test, it seems phone calls won't work either. So my phone seems to be handling the LTE functions well enough, but is having trouble with the CDMA/EVDO part of the antenna.
Anyone who has any advice, please help. Like I said, I'm inclined to do a SIM reset, but won't be able to until much later tonight.
Click to expand...
Click to collapse
Go into About Phone -> status check your IMEI and PRL and such are they still there?
buhohitr said:
Go into About Phone -> status check your IMEI and PRL and such are they still there?
Click to expand...
Click to collapse
My IMEI is there, it was the first thing I checked. I did the whole IMEI backup thing way back in the beginning with this phone.
IMEI wouldn't explain the problem anyway. I still have 2-3 bars of LTE at all times, which I wouldn't have if I didn't have my IMEI. For whatever reason regular phone communications (SMS/Calls) won't go through. Since I know that Verizon still routes those communications through the older CDMA/EVDO network, I'm assuming that's the source of my problem.
TenderloinShadow said:
My IMEI is there, it was the first thing I checked. I did the whole IMEI backup thing way back in the beginning with this phone.
IMEI wouldn't explain the problem anyway. I still have 2-3 bars of LTE at all times, which I wouldn't have if I didn't have my IMEI. For whatever reason regular phone communications (SMS/Calls) won't go through. Since I know that Verizon still routes those communications through the older CDMA/EVDO network, I'm assuming that's the source of my problem.
Click to expand...
Click to collapse
Sure just make sure things don't get corrupted, if everything is still in order then you can reset sim, worse case call VZ and they can reset (re-provision) the sim for you. Happened to me twice and VZ solved them in both cases.
The problem i had i couldn't recieved calls. Everything worked fine..
I ended up getting new sim card then the employee dialed *73 then my fone was back in action
buhohitr said:
Sure just make sure things don't get corrupted, if everything is still in order then you can reset sim, worse case call VZ and they can reset (re-provision) the sim for you. Happened to me twice and VZ solved them in both cases.
Click to expand...
Click to collapse
yeah I figured that would have to be the answer from the beginning. Have to Odin back to stock first, won't be able to do that for probably another 3-4 hours because of a work meeting that's about to start, so I figured I'd ask around.
If anyone has any other ideas, I'm open to them. Otherwise I'll reprovision tonight and report back.
The data/sms issue isn't odd... sms and calls are on the 1x protocol, data is on the LTE/CDMA/EvDO, so if you can't send sms, you can still use data.
Have you tried flashing one of the stock-based roms and seeing if the issue remains? I've encountered that before where stock is fine, but CM/AOSP roms have a wonky issue and *some* people report after doing so, they can get data/calls working on the custom roms. Unfortunately, my resolution there was to cab (LG device) back to factory image.
beepea206 said:
The data/sms issue isn't odd... sms and calls are on the 1x protocol, data is on the LTE/CDMA/EvDO, so if you can't send sms, you can still use data.
Have you tried flashing one of the stock-based roms and seeing if the issue remains? I've encountered that before where stock is fine, but CM/AOSP roms have a wonky issue and *some* people report after doing so, they can get data/calls working on the custom roms. Unfortunately, my resolution there was to cab (LG device) back to factory image.
Click to expand...
Click to collapse
+1
Flash back to stock, or a stock based rom with stock messaging. Try to force the message through. My messages stopped sending on aosp messaging and was persistent through rom flashes. I eventually forced it through using touchwiz messaging.
Sent from my SCH-I535 using Tapatalk 2
This happens on every Lollipop ROM I have flashed, no problems on 4.4 ROMS. I do clean installs, do not restore anything from Tibackup. So basically what happens is I will randomly but very frequently lose all data and cell service. Like once every three minutes frequently. It only lasts about 5 seconds at a time. The signal bar triangle will have an exclamation mark in it (see attached example). I delete and re-enter my APN, turn off wifi AND the Scanning Always Available option. I have read some threads about this exact same thing happening on Nexus 5 after Lollipop update but they are old and it seems to have been fixed with an update. Does anyone have any ideas about what is going on? I'm on TMO in the US and like I said, it ONLY happens on Lollipop ROMs it does not happen of Kitkat.
I read this as sort of an explanation as to why but nothing as to how to fix it. It is driving me insane.
I'm in the same boat, I cant make calls with hangouts or with Dialer or it will disconnect. I haven't seen a solution yet. I've tried every ROM I can, but it keeps crashing. drives me up a wall. I want to logcat it, but having issues while at work.
budm said:
I'm in the same boat, I cant make calls with hangouts or with Dialer or it will disconnect. I haven't seen a solution yet. I've tried every ROM I can, but it keeps crashing. drives me up a wall. I want to logcat it, but having issues while at work.
Click to expand...
Click to collapse
Only discussion about this I have seen is in the Nexus 5 forums, nothing in OPO
Any insight to this would be greatly appreciated.
Come on guys, am I really the only one with this issue?
TigerDNA said:
Come on guys, am I really the only one with this issue?
Click to expand...
Click to collapse
You're not alone, I have this as well but I don't get the exclamation mark but instead the triangle appears completely empty, as if I have no signal at all.
anyone know a way to fix this awell? i flashed the new lolipop alpha modem and still same thing if not worse
The only time this has happened to me is when I toggle Wi-Fi. It for this every time, but have no data issues otherwise. Seems to be when switching between ip addresses. Are you possibly between towers or roaming on another network? May be the issue, but I can't say for sure. Running the lollipop rom exodus, no issues at all.
EDIT: also what baseband are you guys on? I thought I saw something similar and someone flashed a test baseband and it fixed whatever issue they were having. Link coming shortly.
EDIT 2: just now noticed the list above mine about the alpha modem and it not working for them. If anyone else needs to try however, link is http://forum.xda-developers.com/sho... work for some and not others.
from the one+
Does anyone know if we can flash the CM11S modem on CM12?
Go to Settings -> More - > Mobile Networks. Make sure all the items are set correctly.
alleykat2561 said:
Go to Settings -> More - > Mobile Networks. Make sure all the items are set correctly.
Click to expand...
Click to collapse
In OP "I delete and re-enter my APN, turn off wifi AND the Scanning Always Available option."
Same issue here. Running SlimSaber using alpha radio.
Same problem on two OPOs here, both running Temasek CM12
Anyone found a solution yet?
I have the same issue on CM12, BlissPop and Validus ROMS.
Strangely I do NOT have the issue on Euphoria.
Think it happened after I flashed the Alpha L modem.
Tried flashing an older CM11S modem, but no luck...
Hi,
Sorry for the noob answer but anybody tried settings>mobile networks>preferred network type and set it to 3G? I flashed a new rom from stock CM and noticed that I was experiencing signal trouble, I checked my status and the signal detected is LTE so I changed my network to 3G and network signal improved. Downside is that you cant use LTE (but thats ok for me since here in our country, LTE signal is still kind of limited)
Zino same for me. Ever find a fix or a rom that doesn't do this?
OP here, it's strange that all of us have this issue, the same issue that came up on the Nexus 5 thread when L was first released but know one else seems to have any knowledge of it. I am almost certain it doesn't have to do with our carriers but rather something software related.
I'm also suffering from this issue, until now the only way I knew how to fix it was to wipe the cache in recovery which takes ages!
got the same problem :<
I have a similar issue. I use t mobile in the USA and LTE works, H+ works, but 3g shows signal and won't load anything. No idea how to fix it.
Flashed from CM13 to CM14 without issues. However, every nightly after 11/16 causes my phone to not send txt messages. Have tried different apps, checked carrier settings, re-flashed, etc. Any help would be appreciated.
I think the Beanstalk thread gives us the best perspective on the issue. Probably early issues that will eventually get fixed.
Which baseband? This behaviour smells a lot like some of the other weirdnesses I've seen when I've had an image installed which was expecting a baseband other than the one I had in play. When I tried CM14 had the latest official O-something or other for the SM-G900P SPR and like a lot of folks, GPS was just not functional at all. So... after wiping the everythings (literally everything except my ejected microSD card) and reinstalling CM13 through TWRP certain operations (like initializing GPS) were still taking a good 30-45 seconds to initialize which wasn't the case previously with the late October nightly I was using. ...another sign that something has gone off the rails with the modem-y parts, and that they might be in a tizzy about being talked to with the wrong API.
So... just to reset everything I wound up reflashing the O-something stock firmware I had, then letting it upgrade itself via the two OTA patches to PK1. (Don't worry, I find the idea of tolerating Sprint's Crazy-Town modifications laughable.) Updated the profile and the PRL for giggles, and then reflashed in TWRP, wiped the everythings again and sideloaded the same CM13 nightly and Gapps.
I've just gotten things squared back away with CM13 and haven't had a chance to circle back around to try CM14 again (because all that other stuff takes a few hours and makes testing conflict with things like, sleeping and eating) with the new baseband, but the pass through stock and it's updates sorted out the strange 30-45s glitches. If anyone's actually tried CM14 with a PK1 baseband it would probably be worth hearing if they've got GPS and cellular traffic working simultaneously.
Update: Sure enough, after upgrading to the PK1 baseband (via a reflash to stock) CM14.1 seems to be able to handle cellular data and voice calls, wifi, bluetooth and GPS. There was a bit of weirdness with Allo making a terrible sound instead of beeping, but all things considered it looks like it's stable enough to be a daily driver for the SM-G900P now.
If I'm understanding correctly none of the current roms work on Sprint's network. Is that correct?
I've tried lineageOS and couldn't hold a signal so if there's one that works please point me in that direction.
Thanks.
I hadn't had any luck with ROMs on Sprint either until today. I decided to restore my TWRP backup of LineageOS 14.1 official, then I re-flashed the bootloader and radio from the most recent stock build (I had been on 4.4.3 to test something). The device was not active on my account at the time, but when it booted up, I got an alert from Signal Check Pro that it had an LTE signal, and the LTE indicator was on. So then I signed on and swapped devices to try to reactivate it, and immediately went into carrier settings and tapped update network settings. I got an alert shortly after saying com.android.phone had stopped, but it appeared to work, and I had a signal and LTE indicator. There was a Lineage update showing (May 17), so I downloaded it (over LTE) and installed it. Everything has been working so far, both before and after the update: voice, LTE (all bands), SMS, MMS, and RCS. So I really didn't do anything different, it's just working now.
Note, I have had SMS problems on every stock build starting with the first 6.0.1 build, and all security releases after it. I haven't had any problems on any older Android version. What happens is it works fine for a while, but at least once a day. SMS stops working until I reboot or update network settings. That's why I installed Lineage, trying to determine if it's a bug in Android or the radio. So far, no problems, but it has only been a few hours.
Sent from my Nexus 5 using Tapatalk
LOL it course the SMS bug struck after about 24 hours.. except this time it took a couple of tries to get data working again, and SMS wouldn't work again.. I knew better.. back to stock again..
Sent from my Nexus 5 using Tapatalk