Over the past week, there have been multiple reports about the future of Cyanogen Inc., the company behind the popular CyanogenMod Android fork. None were good.
Today, founder Steve Kondik addressed the "misinformation" and seems to suggest that Cyanogen is doing just fine:
I wanted to quickly address the circus of misinformation which has sprung up recently, particularly for everyone ... [ read the full article ]
Please read the original article before posting your comments.
Sounds strongly like an APN issue. I had the same problem, using CM on a CDMA Galaxy S3, when using Ting (a Sprint MVNO), and fixed it with an APN change.
If you're willing to mess with a bit, simply go to your (currently working) phone's "data" menu via the dialer (dial ##3282#; some phones make you press the "call" button afterward), go to the APN menu, and copy ALL the APN info (or simply google it). Then root (if you haven't already), make a full NANDroid backup so you can un-bork it easily if there's an issue, and install CM. You can then make a manual APN setting with the very same data within CM's settings.
If you're not running stock but still have a non-AOSP ROM, the EPST dialer code (##3282#) should still work fine. AOSP ROMs usually break EPST, sadly; if you are using an AOSP ROM already or your current ROM doesn't suport EPST codes for some other reason, "True Phone Dialer"should allow proper EPST code entry.
You can also do this with a simple .zip file install via recovery ? that's how the fix for my S3 was handled ? but that's beyond my ken ^^' .
Feel free to get back to me here or via PM, if you'd like more detailed/additional assistance.
Edit -> Rot, that app will NOT suffice any more (at least on my LG G2). Ah well; you should be able to read your APN data from your phone's settings, but if not, looks like a search for the proper ones is the only way to go.
