Hey all,
I've had mixed results when trying to get an APN that works. I'm running LiquidSmooth RC2 (4.2.2) and have had issues with sending MMS. I've tried both APN files that I have found on XDA for Sprint.
Thread number 1 (post #2):
File name: apns-20120808101544.xml
APN's included: 16 (only Sprint APNs)
Didn't work for me.
Thread number 2:
File name: sprint-mms-fixed-apns.xml
APN's included: 4 (only Sprint APNs)
Didn't work for me.
Neither of these two APN xml files worked for me.
When scouring my SDcard, I found an APN backup file that I had created (from the original filename, I had created it Feb 11th, 2013). I don't remember creating it or ever flashing it before, but I decided to try it out.
File name: Topherk's Fixed APN - 2013-02-11.xml
APN's included: 83 (A whole slew of carriers APNs)
Worked for me.
Now, when I started to look more carefully into the differences between these APNs, I started to get confused (as anyone who is first looking at APN files should!).
When comparing the apns-20120808101544.xml file with my "working file," the Sprint-related APNs were identical. Since I can send MMS on the working file and not the apns-20120808101544.xml file, it leads me to believe that I'm actually sending files through one of the other carrier's APNs. I don't even know if this is possible.
So I guess my "Fix" is working, but I don't really know why. You can try it if you like. Just follow the instructions in the first thread I linked.
Also, last thing, I haven't been able to find this 83-strong APN file anywhere on XDA. If someone has posted it before me, please let me know and I'll give them a proper link (I'm not trying to steal anyone's thunder).
I'm glad this worked for you and I'm not trying to debunk your method entirely I'm just saying this fix along with the other two did not work for me. The only thing that ended up fixing my problem was changing LTE/CDMA/EvDo to CDMA/Evdo auto I ended up restoring my original APN just for safety
sevenpioverthree said:
I'm glad this worked for you and I'm not trying to debunk your method entirely I'm just saying this fix along with the other two did not work for me. The only thing that ended up fixing my problem was changing LTE/CDMA/EvDo to CDMA/Evdo auto I ended up restoring my original APN just for safety
Click to expand...
Click to collapse
No worries. The MMS issue with 4.2.2 is really finicky and different fixes work for different people/phones (that's why I had the ? in the title). I'm glad you got your phone working. Thanks for adding what worked for you, it really helps when people are searching for solutions (hopefully people do searches!).
I'd also like to add that I followed advice in another thread that said to do a clean flash of LiquidSmooth (It was on the LiquidSmooth ROM thread, so I can't say it'll work for your ROM) and it actually worked! MMS is sending just fine and I restored all my data with TIBU, however I skipped the file with the name "Phone/Messaging Sto...25 (SMS/MMS/APN)". So I restored everything with TIBU except that file on the list of applications (it has a green name).
sevenpioverthree said:
I'm glad this worked for you and I'm not trying to debunk your method entirely I'm just saying this fix along with the other two did not work for me. The only thing that ended up fixing my problem was changing LTE/CDMA/EvDo to CDMA/Evdo auto I ended up restoring my original APN just for safety
Click to expand...
Click to collapse
Had just the opposite for a customer's phone. Changed their's from CDMA auto to LTE/GSM/CDMA auto and MMS started working. Thanks for the tip about changing modes.
Whenever I flash cm 10.2 cm 11 any rom at all I face the problem of no internet. So I go back to stock. I have my baseband, build # important stuff like that. I always have to take out my assert lines. So when I flash any rom the fine line will say;
;Mount
or something like that I delete all the assert lines and I was told to keep assert lines but just change them to my baseband and stuff. Any help would be appreciated. & btw the problem is it says Mobile State: Disconnected. But I'm in service too.
I have the same problem. Been searching for a while and trying different fixes, but doesn't seem to be working. I'm on ATT galaxy S3, tho. If someone's got a working ATT S3 and let me know exactly what ROM, gapp, modem, etc they used, would much appreciate it.
Keyonwise said:
Whenever I flash cm 10.2 cm 11 any rom at all I face the problem of no internet. So I go back to stock. I have my baseband, build # important stuff like that. I always have to take out my assert lines. So when I flash any rom the fine line will say;
;Mount
or something like that I delete all the assert lines and I was told to keep assert lines but just change them to my baseband and stuff. Any help would be appreciated. & btw the problem is it says Mobile State: Disconnected. But I'm in service too.
Click to expand...
Click to collapse
More info is needed, such as carrier. I'm guessing either Virgin Mobile or Boost if you need to remove asserts on any of the pre-unified builds (this would hold true for any ROM that has switched to d2lte from d2spr). If that is the case, then you don't have the correct APN's configured. Also, it usually doesn't hurt to be running the most current modem (MK3 for Sprint, MK5 for VM/Boost). Again, the more info the better, then people don't have to play Twenty Questions in order to get to the heart of the matter.
This may work...
So, after trying countless options that i found on this site, and after dozens of flashing roms, modems, kernels, booloaders, restores, etc... turns out that i was doing everything right and there was nothing wrong with the install or the phone itself. After contacting my carrier (PTEL Mobile) for the third time, (first time they told me they had an outage, second time they told me to set the APN setting correctly - neither of which was incorrect on my end or the cause), they said they will try RESETting the DATA on their end. And guess what - that worked.
If you think you did everything correctly but still not getting data, i suggest you make your provider to do the same, or at least pry them as much as you can about your problem and what they can do about it. I wasted to much time and effort (my poor phone) on this and the solution was simple, and not my fault. Hope this helps others.
Mr. Struck said:
More info is needed, such as carrier. I'm guessing either Virgin Mobile or Boost if you need to remove asserts on any of the pre-unified builds (this would hold true for any ROM that has switched to d2lte from d2spr). If that is the case, then you don't have the correct APN's configured. Also, it usually doesn't hurt to be running the most current modem (MK3 for Sprint, MK5 for VM/Boost). Again, the more info the better, then people don't have to play Twenty Questions in order to get to the heart of the matter.
Click to expand...
Click to collapse
Hiya, I'm currently having the same problem as the OP. Mobile state disconnected but it says I am in service. Using latest version of Philz recovery and I flashed the most recent nightly of the Cyanogenmod 11 -4.4.2 KitKat (April 5th, 2014).Carrier is Virgin Mobile, using Samsung Galaxy SIII SPH-L710. PRL is most recent one 33030 and modem is MK5. I did however, flash the rom without deleting the assert lines, since I did not know I had to delete some assert lines. Any help with this? Thanks.
S0lstice said:
Hiya, I'm currently having the same problem as the OP. Mobile state disconnected but it says I am in service. Using latest version of Philz recovery and I flashed the most recent nightly of the Cyanogenmod 11 -4.4.2 KitKat (April 5th, 2014).Carrier is Virgin Mobile, using Samsung Galaxy SIII SPH-L710. PRL is most recent one 33030 and modem is MK5. I did however, flash the rom without deleting the assert lines, since I did not know I had to delete some assert lines. Any help with this? Thanks.
Click to expand...
Click to collapse
Deleting asserts is only for d2spr specific builds, that doesn't apply to d2lte builds (hence the reference to "pre-unified builds" in my first post). Your issue is most likely also related to APN's. However, there are also known data issues on a lot of the latest CM nightlies, and also on the ROM's that rely heavily on CM as a code source. I would strongly recommend reading the last several pages of the thread for any ROM that falls into this category in order to see what other users are reporting along these lines.
CM11 No Mobile Network
Hey guys,
Noob here. I'm running CM11-20140428-NIGHTLY-jflte on a Galaxy S4 GT-i9507(international, optus) but bootscreen now says 9505(not sure if that's important).
I've had Mobile Network State: Disconnected for the last three nightlies. On CM11 M3 it was working all good, but now no luck.
So I've tried a few things and I've come to the point where I'm going to try the factory reset then reflash CM11 and fingers crossed it will work.
Can anyone talk me through the proper procedure for this? I've made a full backup on my external SD using CWM 6.0.4.7 and transferred it to
computer just in case. So would anyone be awesome enough to take me through it step by step.
Cheers,
hhmmm
Use Rom Manager app and Fix Perrmisson
I install a bunch of roms on my dadz s3 and had 2 DirtyFlash it
And then used Wifi 2 get the app itselfz and it fix'd 88 permission
Idk jus tryn 2 help
Had sumthing 2 do w Gapps causing my issue
CM11 No Mobile Network
Ickyz said:
Use Rom Manager app and Fix Perrmisson
I install a bunch of roms on my dadz s3 and had 2 DirtyFlash it
And then used Wifi 2 get the app itselfz and it fix'd 88 permission
Idk jus tryn 2 help
Had sumthing 2 do w Gapps causing my issue
Click to expand...
Click to collapse
Just Fixed Permissions using Rom Manager, still no good.
Stock no APN settings at all
I have looked everywhere and found nothing for the last 3 weeks. I have a stock, sprint S3 on straight talk (my son's phone) it will not get 4g lte data what so ever. My phone is the exact same phone, and it does get 4g lte data. I tried all the basics ##72786# data on off check airplane mode...nothing. Mobile network state is "disconnected". So I opened data ##3282# to compare apn settings with my phone. I made sure everything matched, and when I get to "LTE APN Settings" I open it up, and nothing is there except APNs nothing, blank. Also missing is "Dial Up Networking" that option does not exist on my son's phone. He updated to kitkat (uggh) but the problem was present before that. Checked the phone, and it is not rooted. Funny thing is the phone updates with 4g lte running after dialing ##72786#, but that goes away after it completes. Texting works, but no mms (pictures etc.) and if I set it to cdma only it gets 3g, otherwise no data at all. Anybody?
I've recently moved to Washington, D.C. for a summer internship as of last Friday. Ever since getting into the area, I have not been able to receive phone calls on my AT&T HTC One M9. I was curious to know if anyone else has had this issue? I am able to make phone calls, use the cellular internet (usually I have LTE service), send text messages, and anything else using the phone service, but the only time I know I get an incoming call is when my phone notifies me that I have a new voicemail message. It also doesn't matter if the phone is "awake" or not. I have had people call me when the phone screen is off and on, with the same result. I commute from Arlington, VA every day, and this issue happens regardless of where I am along my commute.
To further complicate things, if I am in phone conversation and someone calls me, Call Waiting shows up with the incoming call. So I am "able" to receive phone calls, but I do not receive them when I am not in a phone conversation.
Has anyone had a similar problem like this? I'm currently running Android Revolution 5.1 since the latest version has an issue for me where the phone restarts if I try to turn on the screen. Even then, that is not the issue because 8.1 has the same calling issue. I've talked with AT&T tech support and did everything they suggested, when I get home from work I plan on getting a new SIM card to see if that fixes things.
My gut tells me there is either something wrong with the SIM, or for some reason my out-of-state phone number (I have a central Ohio area code) has issues with the towers in the area.
I would reccommend that you try performing a manual roam, go to settings>mobile data>Network operators, let it scan for networks, select a network that is NOT your carrier then once it fails to register select your own carrier, this should update the Mobile HLR and hopefully allow you to receive calls again.
Hope this helps
shark0807 said:
I've recently moved to Washington, D.C. for a summer internship as of last Friday. Ever since getting into the area, I have not been able to receive phone calls on my AT&T HTC One M9. I was curious to know if anyone else has had this issue? I am able to make phone calls, use the cellular internet (usually I have LTE service), send text messages, and anything else using the phone service, but the only time I know I get an incoming call is when my phone notifies me that I have a new voicemail message. It also doesn't matter if the phone is "awake" or not. I have had people call me when the phone screen is off and on, with the same result. I commute from Arlington, VA every day, and this issue happens regardless of where I am along my commute.
To further complicate things, if I am in phone conversation and someone calls me, Call Waiting shows up with the incoming call. So I am "able" to receive phone calls, but I do not receive them when I am not in a phone conversation.
Has anyone had a similar problem like this? I'm currently running Android Revolution 5.1 since the latest version has an issue for me where the phone restarts if I try to turn on the screen. Even then, that is not the issue because 8.1 has the same calling issue. I've talked with AT&T tech support and did everything they suggested, when I get home from work I plan on getting a new SIM card to see if that fixes things.
My gut tells me there is either something wrong with the SIM, or for some reason my out-of-state phone number (I have a central Ohio area code) has issues with the towers in the area.
Click to expand...
Click to collapse
I had this issue last week as well. It came on out of the blue and did all the usual AT&T troubleshooting and technical support. As of Monday, though, I think I have the issue fixed. I don't know if AT&T made a network modification that spurred the issue or if I changed something on my phone. Anyway, I'm not sure exactly what step along the way actually fixed my issue, but here's what I did.
1) Go into mobile data settings and see if turning off "Enhanced 4G LTE services" helps
2) I'm not sure if ARHD has this option, but if you can set your phone disable 4g in mobile data settings, turn 4g off and see if you can receive calls...I bet you can (so that's a temporary solution)
3) Alternatively, you can dial *#*#4636#*#* which will bring you into phone settings. Go into phone information, scroll down and on preferred network type, change that from GSM/WCDMA/LTE auto to GSM or GSM Auto (again this is just a temp fix because basically you're disabling LTE which is not desirable)
If any of those work, then check this file:
system\customize\ACC\default.xml
Scroll to the "Phone" app section
Look for a line "<item type="boolean" name="voLteEnabled">false</item>"
Change that to "true"
(If ARHD is compatible with AT&T, then it's probably already set to true)
If it was set to false, reboot and see if that works (to test, you'll have to undo any changes made in steps 1,2 or 3).
I did a lot of stuff before I did any of the above and Insert Coin (the custom ROM I use) already had the voLte setting set to true so the stuff below might actually be what fixed my issue. The next steps are just not as quick to accomplish as I ran the AT&T Ruu a few times and also flashed the developer ROM.
here's everything that i did...
Ran ATT 1.32.502.31 RUU to confirm that I can receive calls on 100% stock.
Flashed stock developer RUU and I could no longer receive calls.
Flashed custom rom (Insert Coin) and I could still not receive calls.
Ran ATT RUU again and calls suddenly worked again.
Re-flashed developer RUU.
Rooted it
installed root explorer (ES Files Explorer)
navigated to system\customize\ACC\default.xml and made the change explained above
rebooted the phone and I was again able to receive calls on the developer edition
Restored Insert Coin from a backup and i was STILL able to receive calls.
After restoring IC, i checked the default.xml file and noticed that not only was voLte set to true, ALL of the voLte options (there are like 5 of them) were set to true. Then I checked the IC zip file and opened the default.xml from what i was flashing and they were all set to true in the zip file. So I think they were all set to true when I began having problems. So I'm really not sure what fixed this for me. But, like I said, that's everything I did and it's working again.
If you go 100% stock by flashing the AT&T RUU (or if you're able to restore to stock using an untouched system image from TWRP) and still can't receive calls, then get on with AT&T support and have them verify your provisioning.
Sorry if this is not very well organized, but I started having this issue like last Friday and worked on it all weekend and Monday and finally got it resolved Monday night...so needless to say...I tried a lot of different things, but what I've written above is what I believe fixed the issue.
I think the problem is that your area supports voLte but maybe the ROM doesn't. Notice when you make a call that your 4G/LTE icon changes to 4G only. Well, the same is supposed to happen when you receive a call, but for some reason, something isn't allowing the phone to switch to 4g only.
jollywhitefoot said:
I had this issue last week as well. It came on out of the blue and did all the usual AT&T troubleshooting and technical support. As of Monday, though, I think I have the issue fixed. I don't know if AT&T made a network modification that spurred the issue or if I changed something on my phone. Anyway, I'm not sure exactly what step along the way actually fixed my issue, but here's what I did.
1) Go into mobile data settings and see if turning off "Enhanced 4G LTE services" helps
2) I'm not sure if ARHD has this option, but if you can set your phone disable 4g in mobile data settings, turn 4g off and see if you can receive calls...I bet you can (so that's a temporary solution)
3) Alternatively, you can dial *#*#4636#*#* which will bring you into phone settings. Go into phone information, scroll down and on preferred network type, change that from GSM/WCDMA/LTE auto to GSM or GSM Auto (again this is just a temp fix because basically you're disabling LTE which is not desirable)
If any of those work, then check this file:
system\customize\ACC\default.xml
Scroll to the "Phone" app section
Look for a line "<item type="boolean" name="voLteEnabled">false</item>"
Change that to "true"
(If ARHD is compatible with AT&T, then it's probably already set to true)
If it was set to false, reboot and see if that works (to test, you'll have to undo any changes made in steps 1,2 or 3).
I did a lot of stuff before I did any of the above and Insert Coin (the custom ROM I use) already had the voLte setting set to true so the stuff below might actually be what fixed my issue. The next steps are just not as quick to accomplish as I ran the AT&T Ruu a few times and also flashed the developer ROM.
here's everything that i did...
Ran ATT 1.32.502.31 RUU to confirm that I can receive calls on 100% stock.
Flashed stock developer RUU and I could no longer receive calls.
Flashed custom rom (Insert Coin) and I could still not receive calls.
Ran ATT RUU again and calls suddenly worked again.
Re-flashed developer RUU.
Rooted it
installed root explorer (ES Files Explorer)
navigated to system\customize\ACC\default.xml and made the change explained above
rebooted the phone and I was again able to receive calls on the developer edition
Restored Insert Coin from a backup and i was STILL able to receive calls.
After restoring IC, i checked the default.xml file and noticed that not only was voLte set to true, ALL of the voLte options (there are like 5 of them) were set to true. Then I checked the IC zip file and opened the default.xml from what i was flashing and they were all set to true in the zip file. So I think they were all set to true when I began having problems. So I'm really not sure what fixed this for me. But, like I said, that's everything I did and it's working again.
If you go 100% stock by flashing the AT&T RUU (or if you're able to restore to stock using an untouched system image from TWRP) and still can't receive calls, then get on with AT&T support and have them verify your provisioning.
Sorry if this is not very well organized, but I started having this issue like last Friday and worked on it all weekend and Monday and finally got it resolved Monday night...so needless to say...I tried a lot of different things, but what I've written above is what I believe fixed the issue.
I think the problem is that your area supports voLte but maybe the ROM doesn't. Notice when you make a call that your 4G/LTE icon changes to 4G only. Well, the same is supposed to happen when you receive a call, but for some reason, something isn't allowing the phone to switch to 4g only.
Click to expand...
Click to collapse
Friend, you win the internet, turning off 4G and turning it back on did the trick. Thank you!
shark0807 said:
Friend, you win the internet, turning off 4G and turning it back on did the trick.
Click to expand...
Click to collapse
Nice. Glad to hear it. Where did you turn 4G off? In mobile data settings?
shark0807 said:
Thank you!
Click to expand...
Click to collapse
There's a button for that
jollywhitefoot said:
Nice. Glad to hear it. Where did you turn 4G off? In mobile data settings?
There's a button for that
Click to expand...
Click to collapse
Yes, once off of 4G I was able to receive calls again. Now That I'm home I'm trying the .xml edit to see what happens.
EDIT: Tried the .xml edit, didn't work, I will flash the RUU tonight and see what happens.
shark0807 said:
Yes, once off of 4G I was able to receive calls again. Now That I'm home I'm trying the .xml edit to see what happens.
EDIT: Tried the .xml edit, didn't work, I will flash the RUU tonight and see what happens.
Click to expand...
Click to collapse
This happened to me with my M7 on T-Mobile after they added VoLTE and I was forced to toggle off LTE whenever I wanted to use the phone and I could never make it work properly again. Fortunately for you, the M9 supports it so it could be something like tower upgrades thus toggling it off then on made it grab on to different towers...possibly. I was running ViperROM then so it was a quick toggle however it would get frustrating to have to go into settings regularly. Hope you are all fixed for good
shark0807 said:
Yes, once off of 4G I was able to receive calls again. Now That I'm home I'm trying the .xml edit to see what happens.
EDIT: Tried the .xml edit, didn't work, I will flash the RUU tonight and see what happens.
Click to expand...
Click to collapse
Was the XML switch set to false? You could try changing all of the volte switches to true. Also maybe a different custom rom...maybe arhd doesn't support volte at all.
It was, and I did as you suggested, still nothing doing. I've now been trying to use the AT&T RUU to restore everything, but I'm running into problems with that as well. I haven't seen anyone discuss it on this forum, but fastboot and htc_fastboot crash while trying to flash the RUU. First I tried with the .exe of the RUU, which doesn't give me much information except that it crashes. If I do it through command prompt (and a RUU in .zip format), the RUU sends a "pre-update", crashes with an error code FAIL90, tries to do it again, then fastboot and htc_fastboot crash on the computer.
From previous HTC phone forums, it seems like this error happens on Windows 8 and 8.1 computers, but I'm not entirely convinced why my OS in this case would be the problem.
Fastboot error on computer:
Code:
Problem signature:
Problem Event Name: APPCRASH
Application Name: fastboot.exe
Application Version: 0.0.0.0
Application Timestamp: 54bfb0a1
Fault Module Name: ntdll.dll
Fault Module Version: 6.3.9600.17736
Fault Module Timestamp: 550f42c2
Exception Code: c0000005
Exception Offset: 0004248d
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 5861
Additional Information 2: 5861822e1919d7c014bbb064c64908b2
Additional Information 3: a10f
Additional Information 4: a10ff7d2bb2516fdc753f9c34fc3b069
And for htc_fastboot:
Code:
Problem signature:
Problem Event Name: APPCRASH
Application Name: htc_fastboot.exe
Application Version: 0.0.0.0
Application Timestamp: 546e94d2
Fault Module Name: StackHash_79f3
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: PCH_27_FROM_htc_fastboot+0x00001215
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 79f3
Additional Information 2: 79f3f37ca9651ef9bd47b0bfb55904f8
Additional Information 3: 86de
Additional Information 4: 86de0d14c4489f5d62365f6244178ece
shark0807 said:
It was, and I did as you suggested, still nothing doing. I've now been trying to use the AT&T RUU to restore everything, but I'm running into problems with that as well. I haven't seen anyone discuss it on this forum, but fastboot and htc_fastboot crash while trying to flash the RUU. First I tried with the .exe of the RUU, which doesn't give me much information except that it crashes. If I do it through command prompt (and a RUU in .zip format), the RUU sends a "pre-update", crashes with an error code FAIL90, tries to do it again, then fastboot and htc_fastboot crash on the computer.
From previous HTC phone forums, it seems like this error happens on Windows 8 and 8.1 computers, but I'm not entirely convinced why my OS in this case would be the problem.
Fastboot error on computer:
Code:
Problem signature:
Problem Event Name: APPCRASH
Application Name: fastboot.exe
Application Version: 0.0.0.0
Application Timestamp: 54bfb0a1
Fault Module Name: ntdll.dll
Fault Module Version: 6.3.9600.17736
Fault Module Timestamp: 550f42c2
Exception Code: c0000005
Exception Offset: 0004248d
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 5861
Additional Information 2: 5861822e1919d7c014bbb064c64908b2
Additional Information 3: a10f
Additional Information 4: a10ff7d2bb2516fdc753f9c34fc3b069
And for htc_fastboot:
Code:
Problem signature:
Problem Event Name: APPCRASH
Application Name: htc_fastboot.exe
Application Version: 0.0.0.0
Application Timestamp: 546e94d2
Fault Module Name: StackHash_79f3
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: PCH_27_FROM_htc_fastboot+0x00001215
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 79f3
Additional Information 2: 79f3f37ca9651ef9bd47b0bfb55904f8
Additional Information 3: 86de
Additional Information 4: 86de0d14c4489f5d62365f6244178ece
Click to expand...
Click to collapse
I'm on Windows 7, so I don't know about the Win 8/8.1 issues, but I've read a lot of people that have trouble using those operating systems with drivers.
Maybe try insert coin or another custom rom...I know IC supports AT&T, even thought that's the rom i was using when I started having problems.
Unfortunately I have very slow internet so it takes hours to download a ROM to test. I installed ViperROM, which I have been very happy with when I had my M7, and I can confirm that receiving calls works again. But I have the same problem I had with ARHD, that being that when the screen turns off, the phone turns off. So, the solution is "fixed" kind of, I just need to figure out why my phone is doing this standby issue, and fix that.
shark0807 said:
Unfortunately I have very slow internet so it takes hours to download a ROM to test. I installed ViperROM, which I have been very happy with when I had my M7, and I can confirm that receiving calls works again. But I have the same problem I had with ARHD, that being that when the screen turns off, the phone turns off. So, the solution is "fixed" kind of, I just need to figure out why my phone is doing this standby issue, and fix that.
Click to expand...
Click to collapse
That's because the version of Viper you're using is on the 1.40 base and you're on 1.32 firmware. Either upgrade firmware to 1.40 (requires s-off), flash a 1.32 version of Viper (if one is available...i'm sure one is), or you can try only flashing a 1.32 kernel (either the kernel found in the 1.32 viper rom, or you could try flashing Flar2's 0.3 version kernel in the Original Develpment section). I can confirm with insert coin that I'm able to run a 1.40 base rom on 1.32 base firmware by flashing a 1.32 base kernel...I can't guarantee the same will work with Viper, but it probably will. The easiest thing will be to just flash Flar's 0.3 version kernel because it's a small download. If that doesn't work, you probably should just download the entire 1.32 viper rom (or get s-off and flash the 1.40 firmware).
Actually, I forgot there's an option in Viper's aroma to install the old base kernel. Read here: http://venomroms.com/htc-one-m9/ (see the firmware requirements section)
@shark0807 your ADB and fastboot crash because they are not suitable for the M9 and buggy probably. I had such versions at the beginning of the M9 lifecycle. HTC has by now released their own version of fastboot which a.) doesn't crash anymore and b.) is capable of flashing RUU's larger than 2GB.
You can get my "Batch Tool" which includes the ARUWizard (the "RUU") from HTC as well as the updated htc_fastboot.exe and adb.exe (which I believe is just the generic Google adb.exe).
The Batch Tool comes as self-extracting rar archive and extracts to C:\Android - if you don't want to use it anymore, just delete that folder and its gone.
Batch Tool is here: http://forum.xda-developers.com/showpost.php?p=59783535&postcount=4
A procedure to have your stuff working on Windows 8/8.1:
1.) Go into Control Panel and remove everything that is or might be connected to HTC. First and foremost, HTC Sync Manager. Also every type of ADB/Fastboot drivers you see there.
2.) Download HTC Sync Manager from HERE and install it. Then remove it again (Sync Manager likes interfering with RUU flashes by blocking Fastboot and ADB for its own stupid purposes - better not have it run in the background. The drivers it installs will remain on your system anyway).
3.) Download my Batch Tool and use the "htc_fastboot.exe" instead of the generic Google fastboot.exe!
That should get you up and running. My Batch Tool additionally installs vcredist_x86_2008_SP1.exe - which is vital for a RUU to run properly. It is usually also installed by HTC Sync Manager but I have seen plenty of cases where that did not happen, so I included it into my Batch Tool setup.
Furthermore, DotNet in some version is required but usually already on most windows PC's - I haven't seen the necessity to separately install it. Just FYI.
I ended up having this problem, just tried what was said and its working so far hopefully it stays working! never had this problem before I think the volte stuff was disabled from when I tried a different rom, im staying stock rooted at&t now
jollywhitefoot said:
I think the problem is that your area supports voLte but maybe the ROM doesn't. Notice when you make a call that your 4G/LTE icon changes to 4G only. Well, the same is supposed to happen when you receive a call, but for some reason, something isn't allowing the phone to switch to 4g only.
Click to expand...
Click to collapse
I think that's the case , for now what has work for me is using GSM auto prl, drains the battery faster , don't know why .
I have call att, I have them going nuts , they don't know what it is , I also enable all of the values, for volte, in the default.XML file, but didn't work .
I'm going to try changing roms, I'm thinking maximum HD
To point out, I haven't change firmwares , the phone still has the at&t one , I've kept in order to avoid this situations , I'll try another ROM
@ZeRo2o9
Where can I get the at&t ROM rooted ??
People I had the same issue , I've call at&t and told them I can only receive call on GSM mode , while on LTE , the phone wouldn't ring at all .
So the lady explain that LTE voice is not supported on all towers , that is the reason , so she opt me out , while it becomes available. Then unchecking the option under setting and reseting the phone the calls where working again .
Thanks for this forum for the help .
Anyone else having problems sending or receiving with MMS on the nightly builds for CM 12.1? My SMS works just fine.
I have Ting, which may be part of my problem. I am using the same APN settings that use to work for MMS in CyanogenMod 11.
Yep. I've been fighting this for 3 days now. I must have tried every CM 12.1 variant out there with the same result. The APN list shows Ting... but you cannot select it, modify it, or save it. Reset to Default APN doesn't work... Rebooting 18 times doesn't work... flashing the various APN "fixes" like for FreedomPop, MVNO_CDMA, etc doesn't work. But like you... SMS, Phone, and Data (on WiFi) work fine. However, MMS and data (on 3G/4G) don't work.
What has worked... backing off to either a Stock ROM or CM 11. So something in these recent CM 12.1 builds is just broken. The only reason I was trying to upgrade from CM 11 to CM 12.1 was because of that StageFright vulnerability. So I may just go with the Stock ROM until I see the CM 12.1 APN issue for Ting has been resolved.
I've been using the clear google messaging app from the TBO updater app and just installed their latest hangouts to try. They both have been handling mms better than any other messaging apps and sometimes the stock mms will work by just having the gmessenger app installed. I've been rom hopping lately and it seems pretty much the same for me across most CM12.1 based ROMs. Also, you could try editing the actual apns-conf.xml file under /system/etc/ back it up first tho and for permissions 644. from my Virgin Mobile Tri-Band model S3
zentsang said:
Yep. I've been fighting this for 3 days now. I must have tried every CM 12.1 variant out there with the same result. The APN list shows Ting... but you cannot select it, modify it, or save it. Reset to Default APN doesn't work... Rebooting 18 times doesn't work... flashing the various APN "fixes" like for FreedomPop, MVNO_CDMA, etc doesn't work. But like you... SMS, Phone, and Data (on WiFi) work fine. However, MMS and data (on 3G/4G) don't work.
What has worked... backing off to either a Stock ROM or CM 11. So something in these recent CM 12.1 builds is just broken. The only reason I was trying to upgrade from CM 11 to CM 12.1 was because of that StageFright vulnerability. So I may just go with the Stock ROM until I see the CM 12.1 APN issue for Ting has been resolved.
Click to expand...
Click to collapse
You should be able to modify Ting by touching the name, even when the button for selecting it is absent. You may need to add "default" to the type once you have it open. I have Ting and I have had to deal with this somewhat as well. I believe I saw some recent Ting APN updates get pushed through as well. Have you tried Exodus?
There is also another thread in here about lollipop and 5.1 which has information that may help.
monsterpenguin5 said:
You should be able to modify Ting by touching the name, even when the button for selecting it is absent. You may need to add "default" to the type once you have it open. I have Ting and I have had to deal with this somewhat as well. I believe I saw some recent Ting APN updates get pushed through as well. Have you tried Exodus?
There is also another thread in here about lollipop and 5.1 which has information that may help.
Click to expand...
Click to collapse
Exodus? Nope... but I'll be checking it out now!
If you don't mind me asking more about the APN. How many are actually needed in there? If I were to delete all the APNs and just manually setup the 1 needed... is it just the LTE version pointing to http://mms.plspictures.com ... or ... http://mms.sprintpcs.com and making sure the "type" has "default" in it? It's the one thing that I can't understand. Out of every forum I've read... not 1 mentions just blowing all the APNs away and just simply adding a single APN for Ting. I don't think I really need all 8-16 APNs (depending on the ROM you flash).
And this question is open to anyone. Is there any reason you have to have all those APNs for other networks like Boost, FreedomPop, Boost Mobile, etc? What should the APN contents be for just Ting? Inquiring minds want to know.
zentsang said:
Exodus? Nope... but I'll be checking it out now!
If you don't mind me asking more about the APN. How many are actually needed in there? If I were to delete all the APNs and just manually setup the 1 needed... is it just the LTE version pointing to http://mms.plspictures.com ... or ... http://mms.sprintpcs.com and making sure the "type" has "default" in it? It's the one thing that I can't understand. Out of every forum I've read... not 1 mentions just blowing all the APNs away and just simply adding a single APN for Ting. I don't think I really need all 8-16 APNs (depending on the ROM you flash).
Click to expand...
Click to collapse
I actually tried that myself but didn't have any luck with it sticking past reboot or even holding the data signal right. It's possible it might work. I don't know enough about APN's to say for sure. Did you try adding "default" to the beginning of the Ting APN type and then save it?