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
Related
I followed directions to wipe everything as suggested in this post:
http://forum.xda-developers.com/showpost.php?p=20485148&postcount=146
Was using Alfa 13 just fine, but on Alfa 17 I can not get cellular data to work. Confirmed my WAP settings are correct for my carrier.
My baseband it says its a i9020xxkf1 and everything else on the phone works. I can access the market, wifi works, account sync if i have wifi on. I have doubled checked every possible setting. But it will not bring up a data connection over the cellular radio. It even takes calls over the radio. Just no data connectivity.
Any suggestions or reasons why this is occurring? I can easily swap back to an older nandroid image of alfa 13, but I would really like to get on a new version etc.
(Also, I would have made this post in the right dev section, but i lack 10 posts to gain access to it.)
Have you tried removing and replacing your SIM card ?
Also, check if your data counter has a limit set on
You could also manually configure your APN settings with your carrier's settings
Unfortunatly I have done all of those things. It doesn't even attempt to connect to data. I sit at 4 or 5 bars of signal and it never even connects to EDGE/3g at all. Yet if I flip back over to my older image it works flawlessly.
i have also problem with version 17, but i can't post it to developer forum (newbie here)
problem is that i can't hook on any network, no calls no messegas, i'm using croatian tele2/t-mobile....sometimes it connects but still nothing, no calss etc.
also problem (not so much a problem but a solution) when i installed ROM it went to bootloop, all you have to do is remove battery and power up again, and voila, it works, same problem happened when i installed gapps (same solution worked, everything installed from CWM latest version)
there were also posts regarding cwm not stiking after installing cynogen, i had no problem with it, i have latest cwm 5.0.2.3 (think so), sticks like hell tried couple of roms, still sticking
cheers
I have the same problem here... ICS 4.0.3 and my 3G stopped to work.
also tried new 18 version, still no luck, i'm staying on cynogenmod 7 (GB), only ICS version that worked was MUI but i don't like it very much....
http://forum.xda-developers.com/showthread.php?t=1398691
It has been messed around with a fair bit. Various methods have worked for different people. YMMV. I myself had such an issue with the stock FW (of all FWs...).
First off, yes it's a Sprint problem. Yes, you aren't obligated to care.
I was happily running a myriad of 5.1 ROMs that I was just dirty flashing for awhile. Decided to move up to the latest Chroma and did a clean flash and...no data. I get a signal and an exclamation mark. Well, I've certainly seen this before. I tried flashing the Sprint fixes floating around and with no luck. As soon as I disconnected from wi-fi I'd lose data.
I flashed the factory image and was up and going in no time. Did a profile and prl update (since those have never worked on AOSP roms) and tried another clean flash of SlimLP, CM12.1, and Chroma. No data on any of them. For the meantime I'm back to using a debloated factory image and Code Blue.
I'd really like to go back to using RRO on a custom ROM. Are any other Sprint users having this issue? Any workarounds? I know we had this issue during the early stage of CM12, after which a fix was identified and committed upstream.
Also having this issue... Without the exclamation mark though. One thing to attempt is the dialer *#*#4636#*#* option and switch between variations of the LTE/GSM/CDMA combination... Occasionally I can get my connection to data back, but it's not reliable... A more reliable fix would be appreciated
It seems I have managed to solve it by myself. I have loaded factory image of 44S, preformed OTA upgrades and it seems the issue is gone.
The thread can be closed.
Hi, Last week I had my phone connected to power bank over night with "Sleep as Android" turned on. In the morning I got my wake up alert but I was unable to wake up my screen to turn it off... so I had to keep the power button down and shutdown the phone.
After that I have faced boot loop (phone worked fine previous evening).
I have tried rebooting phone couple of times but nothing worked so I have restored backup of last CM11s from TWRP (I was running on CM12 nightly during the crash). Phone booted up poperly and I thought everything is fine however after couple of hours I noticed my phone is asking me for my PIN so it has apparently rebooted. It appeared that it is rebooting every couple of hours and after every call (like 5 sec after call ended)...
I have tried restoring other backup but I was facing the same issue. I have done clean install of current CM12 nightly and got the same...
Facing that I decided to clean my phone completely... I have backed up all my data and did wipe and format of everything of everything I could from TWRP. Then via fastboot I have been tring loading YNG1TAS17L 64GB (from here) by flash-all.bat file. After loading bootloader I have received message <waiting for device> and my phone got hardbricked...
I managed to recover it using this guide.
Then I loaded TWRP again and installed COS 12.
On that point my phone started working stable but after a while I noticed that is started losing cell signal. Sometimes it was just for couple of seconds and sometimes it lost it for good (while tring to hardcode cell operator I was getting "error while searching for networks" and I was able to restore connectivity after couple of reboots).
I decided it could be radio/modem related so I have applied full firmware. No go. Loaded CM12 nightly - the same, loaded that modem from oxygen again - no go.
I have tried installing latest BlissPop, Mahdi ROMs and Oxygen and still facing the same issue.
Tested SIM card on other phone and it works fine, tested other SIM card on my OPO and still the same issue so it is phone related.
Getting the following in logcat during time phone is unable to connect to cell signal:
Code:
05-31 11:57:36.265 D/GsmDCT ( 2457): [0]isDataAllowed: not allowed due to - SIM not loaded and not NV subscription
05-31 11:57:36.265 D/GsmDCT ( 2457): [ApnContext:mms] getApnSetting: apnSetting=null
05-31 11:57:36.268 D/GsmDCT ( 2457): [0]isDataAllowed getRecordsLoaded=false
Anyone has any idea what could be a reason of this issue and how to fix it? At this moment everything is working fine except phone calls and Internet over network operator (Wifi works fine). Thanks in advance.
UP
Anyone has any idea? I believe I have narrowed the problem down a bit. It seems 2G/3G is affected only. As long as I'm in LTE range the connection is stable (that explains why I noticed the problem after few hours when I left home).
I have played a bit with hardcoding band and noticed that LTE is running stable (with GSM Signal Monitoring app). When switching to 3G it is dropping every couple of seconds. The strange thing is that 2G is sometimes affected and sometimes not... When switching LTE->2G it seems to be running pretty stable but when switching from 3G->2G it is acting the same way as 3G.
were you able to fix it?
I went through same experience except that I can barely connect to 4g, 3g 50% of time. Tried many radios but none worked.
spx2000 said:
were you able to fix it?
I went through same experience except that I can barely connect to 4g, 3g 50% of time. Tried many radios but none worked.
Click to expand...
Click to collapse
OP updated the post with how it was fixed. Sorry to bump the thread, but thought I'd inform spx that there was an update. Glad it worked out for you OP, I've saved this in case it ever happens to me, and good luck to spx. Hopefully someone puts this info in a sticky so others can try that if they are stuck too.
I fixed it by reflash raido of xnph52q found here. The zip contains more than the radio firmware.
http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph52q-t3025399
I flashed it before but it didn't work. The only difference is I used TWRP 2.8.6. I remember reading somewhere online that 2.8.7 has issue with OPO
artiwal said:
It seems I have managed to solve it by myself. I have loaded factory image of 44S, preformed OTA upgrades and it seems the issue is gone.
The thread can be closed.
Click to expand...
Click to collapse
Where is the 44S that OP used? I have something similar happening with my phone. I revived my phone from a hard brick and now it's not connecting to the cell network. Wifi works, IMEI shows when SIM is inserted, no EFS partition backup (I didn't know that was a thing to do until it was too late).
FWIW, my current build is KTU84Q and I'm running CM-11-20141008-SNAPSHOT-M11-bacon
Hi,
I have serious connectivity issues with my Nexus 5.
Most of the time I am only picking up 2G signal, sometimes the connection drops compeltely. However, I had a very unstable 3G/H/LTE connection for a few minutes sometimes in the last days.
This started after changing the battery and upgrading from Cyanogenmod 12 to 12.1. Unfortunately I did both changes at the same time, so I am not sure what caused this problem.
The following things I could rule out/test:
- Another phone (Nexus 4) picks up H+ with my sim
- My phone doesn't pick up 3G/H/LTE with another (working) sim
- I have checked the connections of the both cables running alongside the battery, I also checked the cables itself.
- I fiddled with the apn settings, also I never touched them before and everything worked fine.
- I have updated the radio image.
The one thing I couldn't try is flashing an older cyanogenmod 12, because I have no backup and couldn't find one online.
Does any of you have any ideas what I can do?
I would be really thankful for any kind of help.
Who is your carrier :/
I probably should have added that in the first place.
My carrier is T-Mobile in germany.
I have the same problem. Also i'm tryed flash Android 5.0 and Android M, in stock i have Android 5.1.1. Who khow how to fix this ?
I have no solution yet. The next thing I want to try is to roll back to Cyanogenmod 12, but I guess I am going to build it myself because it seems to have vanished from the internet.
I do occasionally get LTE, but it is very unstable and doesn't work most of the time.
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.