Friday, September 2, 2016

Galaxy S5 (Sprint). Straight talk. CM13 (k1tespr). Data problem.

Ok, so typically my Google-fu is on point but I'm at a loss for finding relevant posts for my particular issue.

The issue is getting cellular data to work on the Galaxy S5 (Sprint edition), whilst using the Straight Talk carrier, while also on CM13 (snapshot). The phone was originally on Sprint, my wife just got the new Note 7 (lol - at time of the post is the day after the major announcement they'd be recalling all Note 7's), it was paid in full and as far as I can tell it is unlocked. I promptly put a new recovery on it and finished it off with CM.

I'm gonna take a moment to say something irrelevant. Oh. My. God. has rooting/custom ROM/bootloading improved over the years. Maybe it's the fact I finally have a device that was popular enough to have a real big community that worked on it, or what, but everything went SO much smoother than any experiences I've had putting custom roms on devices (then again, the fact that my other devices were always Verizon phones or Chinese tablets probably has something to do with it too). The only hiccup was recompiling an updated executable through a *nix shell. Anyways, back to the point.

I have LTE data working on stock ROM (backed it up before flashing to CM). When I switch to CM, I get working voice/text, but without all the data stuffs. What I suspect the issue may be is that the CM release that works with my phone (k1tespr) is trying to find the Sprint data network and use it. Everything works the way it should on Stock, and I've reinstalled CM multiple times now after verifying that LTE/Voice/Text works on stock, but still running into this wall when I go to use CM.

Hopefully because of the popularity of this device, and the popularity of Straight Talk BYOP's, someone figured this out!

Side Note: In the CM Cell data settings, when I go to "Select Carrier" at the bottom, it errors out, briefly rebooting the cell data settings. The error is "com.android.phone has stopped working". Looks/feels like a CM bug.


from xda-developers http://ift.tt/2c8Y866
via IFTTT

No comments:

Post a Comment