Related
Hey All,
So, I'm having a weird issue with my T-989. I get intermittent audio loss upon making and receiving calls. Refer to the following examples:
Call comes in; I swipe to answer..."Hello...Hello...Hello....-__-" I can not hear the person on the other end of the call and they are un able to hear me. I've asked countless people that call me on a daily basis on their experience when this happens. They say the call connects but no audio; they then get confused and hang up if I don't end the call my self. Normally I'm the one that ends the call now and I'll call back....sometimes I hear ringing and I know that it'll work ok.
Sometimes, the call log counter starts....but I hear no ringing, HOWEVER the person I'm calling is actually being called and tries to answer the phone...but because I don't hear the ringing...I don't even realize that the phone has established a connection.
Sometimes....everything works fine. I'll answer the phone and it'll work like a charm or I'll make a call and it'll work like a charm. Two hours later...same weird issue.
I wanted to know if people had similar problems.
It's getting increasingly annoying at this point. At first I thought maybe it was my service. Then I thought it was my ROM / Radio. Honestly, I know people who have the same service and plan as me.
Phone is running P.A.C 22.0.1
This issue happened on older versions of which I completed wiped and re installed newer versions of P.A.C; it happened on AOKP; happened on Paranoid Android.....
I'm guessing the only thing I haven't tried changing is the Radio that comes with each ROM.
I am on the T-Mobile Pre Paid Unlimited Talk / Text w/ 500mb Data plan. [I work in data centers, unlimited INTERWEBS!]
Anyone else have similar symptoms? I'll be getting the S4 soon, but I wanted to resolve this issue before hand because I'll be giving it to a friend.
Thanks in advance for any help! :victory::highfive:
I have been living that same issue for months, between several ROMs and kernels and radios. Ive learned to use this process......answer call, wait 3 seconds, then saying "hello". I know, its silly.
I have noticed its seems worse when answering calls from others running aosp (cm10)roms.
I've have not tried any touchwiz ROMs
Sent from my cm_tenderloin using xda premium
Waiting 3 seconds and then saying hello works? For me the issue happens when placing calls as well. I installed the newest P.A.C last night when I posted the OP, so far no problems. I'll update again if I have any issues moving forward.
What radio are you using?
Now - UVMC6
As I said, as of yet, I haven't had any issues. Let's see over the next couple of days....
Good Afternoon!
I recently upgraded my Optimus S to an Optimus G and loving it but after rooting I'm not able to send text messages nor when i do get a reply its usually after a couple days or after a reboot. I've gone through and updated the PRL,Profile, and firmware and ive updated all the permissions as someone else recommended with no avail. Sprint of course states that i should drive the hour and a half to the closest sprint repair center to fix it. So i guess i am stumped on what else i could do on my own to fix it, and if i cant how would i Un-root the phone so they dont get all weird since the phone was rooted?
Update: After deleting the SD>Data>Datacom.android.providers.telephony>databases>telephony.db i was able to send and receive texts messages for about an hour...then for some reason it wouldn't work again am i just missing something?
Update 2: Completely started fresh and now back to a stock rom, this issue was fixed in the process besides almost bricking meh phone, worked for a little while then stopped again
Update 3: So after countless hours of help from the great people on the IRC channel and breaking down and talking to sprint i found out it was from the Airave that was messing with the internals of the system and once i reset that it worked fine
Fixed
robert98374 said:
Good Afternoon!
I recently upgraded my Optimus S to an Optimus G and loving it but after rooting I'm not able to send text messages nor when i do get a reply its usually after a couple days or after a reboot. I've gone through and updated the PRL,Profile, and firmware and ive updated all the permissions as someone else recommended with no avail. Sprint of course states that i should drive the hour and a half to the closest sprint repair center to fix it. So i guess i am stumped on what else i could do on my own to fix it, and if i cant how would i Un-root the phone so they dont get all weird since the phone was rooted?
Update: After deleting the SD>Data>Datacom.android.providers.telephony>databases>telephony.db i was able to send and receive texts messages for about an hour...then for some reason it wouldn't work again am i just missing something?
Click to expand...
Click to collapse
After a huge debacle it was all fixed thanks to Artlan on the IRC channel
Intro:
I have the Samsung Epic 4G. Great phone, running into problems. I originally started out rooted and modded with the CyanogenMOD 10 Nightly. Everything was going great and I love the mod but I started getting MMS problems where I couldn't see the pictures being sent or the ones I was sending. There was an easily located temporary fix found online to delete the telephony file and restart the phone. No biggie I can deal. Then bigger problems started arising as I was no longer getting all of my text messages. Sometimes none. I contacted Sprint and they ran through the whole ordeal of giving me some codes to input which of corse wouldn't work on the MOD and I couldn't update the profile so they said they'd check the tower where I was located and turned out nothing was wrong with it.... My wife and I are having a baby so being unable to contact her without calling constantly is a no go.
Main:
I flashed the stock for the SPH-D700 and all of my problems were fixed. This is a no bueno for me because it's full of bloatware and the phone without modification dies before my workday is out practically, even without heavy usage (and forget heavy usage because that was like shooting the battery into the sun and who the hell wants a smart phone that works for only like an hour?). After looking around I located the stock FC09 Deodexed MTD which comes with ShadowKernel (aweeeesome!) and flashed that. Didn't have any issues and all my texts were coming and going through. This was tested at work using a series of seperate sequential alphanumeric texts and all was good. I installed the usual suspects, Voltage Control, Juice Defender, SD Maid, ES Explorer, the WiFi hack, etc... Not being a fan of the stock messaging app I also downloaded the standard Chomp SMS app (which is def a step up and ad free) as well. I knocked the voltages down reasonably and tested them using Voltage control to do that and control the CPU (no overclocking). I got rid of all of the apps that the XDA Wiki said I could and backed everything up. All was well until yesterday. I charged the phone the previous night and went to work doing the normal kinda day act. I sent my wife some messages but figured she was busy when she didn't respond. Hours later I realized that she probably had responded because she never goes that long without doing so. I asked a few friends to text me and I texted myself as well and now I wasn't getting ANY texts. I did the phone dance with Sprint to no avail and they told me to take the phone to my local store. This would be the second Epic 4G that they would be replacing. The first one had this problem too but fixed itself when I flashed the stock rom. Then there was some water damage which thankfully insurance covered and I got my replacement earlier this week when I worked on modifying my phone to something I found acceptable. I think this rules out a hardware issue. On a whim I restored to a backup that I had made after getting my phone neat and tidy and some odd things happened. I started getting texts, but not the ones that I had already missed, and I was getting some later ones first before getting the first ones sent, I.E. i'd send 1, 2, 3, 4, 5 and get back 5, 2, 3, 4, 1 but they would arrange themselves in the correct order onces they came. It was also taking them forever to come in as I would send them and have to wait five to ten minutes for them to come.
Conclusion:
Tired, frustrated, and somewhat perturbed I reflashed the stock rom and the problem again has fixed itself. My question is has anyone else run into this? I've looked everywhere and can't find a similar case. Am I just not seeing something that's directly in front of me? Ideally i'd really like to put Cyanogen back on but I can't afford not to be in contact with my pregnant wife. I'd also reaaaally like the WiFi cabailities that were advertised with the phone but then neglected to mention that I would have to pay 30$ extra a month for. Is this a similar issue to the MMS telephony file issue that can be resolved with perhaps a nightly deletion of a file? Is there anything I can do NOT to be on the stock rom with the worthless battery life and bloatware that chokes?????
Sincerely,
Ignored Thoughts
ignoredthoughts said:
Intro:
I have the Samsung Epic 4G. Great phone, running into problems. I originally started out rooted and modded with the CyanogenMOD 10 Nightly. Everything was going great and I love the mod but I started getting MMS problems where I couldn't see the pictures being sent or the ones I was sending. There was an easily located temporary fix found online to delete the telephony file and restart the phone. No biggie I can deal. Then bigger problems started arising as I was no longer getting all of my text messages. Sometimes none. I contacted Sprint and they ran through the whole ordeal of giving me some codes to input which of corse wouldn't work on the MOD and I couldn't update the profile so they said they'd check the tower where I was located and turned out nothing was wrong with it.... My wife and I are having a baby so being unable to contact her without calling constantly is a no go.
Main:
I flashed the stock for the SPH-D700 and all of my problems were fixed. This is a no bueno for me because it's full of bloatware and the phone without modification dies before my workday is out practically, even without heavy usage (and forget heavy usage because that was like shooting the battery into the sun and who the hell wants a smart phone that works for only like an hour?). After looking around I located the stock FC09 Deodexed MTD which comes with ShadowKernel (aweeeesome!) and flashed that. Didn't have any issues and all my texts were coming and going through. This was tested at work using a series of seperate sequential alphanumeric texts and all was good. I installed the usual suspects, Voltage Control, Juice Defender, SD Maid, ES Explorer, the WiFi hack, etc... Not being a fan of the stock messaging app I also downloaded the standard Chomp SMS app (which is def a step up and ad free) as well. I knocked the voltages down reasonably and tested them using Voltage control to do that and control the CPU (no overclocking). I got rid of all of the apps that the XDA Wiki said I could and backed everything up. All was well until yesterday. I charged the phone the previous night and went to work doing the normal kinda day act. I sent my wife some messages but figured she was busy when she didn't respond. Hours later I realized that she probably had responded because she never goes that long without doing so. I asked a few friends to text me and I texted myself as well and now I wasn't getting ANY texts. I did the phone dance with Sprint to no avail and they told me to take the phone to my local store. This would be the second Epic 4G that they would be replacing. The first one had this problem too but fixed itself when I flashed the stock rom. Then there was some water damage which thankfully insurance covered and I got my replacement earlier this week when I worked on modifying my phone to something I found acceptable. I think this rules out a hardware issue. On a whim I restored to a backup that I had made after getting my phone neat and tidy and some odd things happened. I started getting texts, but not the ones that I had already missed, and I was getting some later ones first before getting the first ones sent, I.E. i'd send 1, 2, 3, 4, 5 and get back 5, 2, 3, 4, 1 but they would arrange themselves in the correct order onces they came. It was also taking them forever to come in as I would send them and have to wait five to ten minutes for them to come.
Conclusion:
Tired, frustrated, and somewhat perturbed I reflashed the stock rom and the problem again has fixed itself. My question is has anyone else run into this? I've looked everywhere and can't find a similar case. Am I just not seeing something that's directly in front of me? Ideally i'd really like to put Cyanogen back on but I can't afford not to be in contact with my pregnant wife. I'd also reaaaally like the WiFi cabailities that were advertised with the phone but then neglected to mention that I would have to pay 30$ extra a month for. Is this a similar issue to the MMS telephony file issue that can be resolved with perhaps a nightly deletion of a file? Is there anything I can do NOT to be on the stock rom with the worthless battery life and bloatware that chokes?????
Sincerely,
Ignored Thoughts
Click to expand...
Click to collapse
So that's a big wall-o-text. I didn't read it, and just skipped down to your conclusion. You can flash another CM based 4.2.2 rom to test SMS/MMS. It all works fine for me on Slim. If you want TouchWiz, then flash The People's ROM. This rom has no bloat and better battery life than stock. All of these roms have the Wifi access point built in.
nikon120 said:
So that's a big wall-o-text. I didn't read it, and just skipped down to your conclusion. You can flash another CM based 4.2.2 rom to test SMS/MMS. It all works fine for me on Slim. If you want TouchWiz, then flash The People's ROM. This rom has no bloat and better battery life than stock. All of these roms have the Wifi access point built in.
Click to expand...
Click to collapse
I'm dloading the latest CM 10.1 RC4 to give it another shot. I'm not confident that this won't happen again either immediately or within a few days. Thank you for your input.
IT
I guess my concern is that this happened across both roms, FC09Deodexed and CM10.
Ok so no luck. Flashed CM10 and no bueno. Not getting all of the messages I send to myself. Massive delay between send and receive.
Then you're left to using Odin to get back on stock. Check auto-reboot, repartition, and f. reset time. After you are back on stock FC09, you may as well update PRL, but be sure to update profile. Test on 100% stock again.
If things work like they should on stock, then Odin in CWM without auto-reboot checked. Battery pull, then reinsert. From there boot into recovery and flash a rom of choice. Test again on newly flashed rom.
If things are not working properly on stock rom, then bring it into a Sprint store for service.
Sorry to say but all of that's been done and put in the original post (which you only speed read through the last part). I appreciate your help though. This is the second Epic 4G to do this to me on everything but the stock rom which makes me think it's not hardware but if it's not happened to anyone else then not much else I can do.
ignoredthoughts said:
Sorry to say but all of that's been done and put in the original post (which you only speed read through the last part). I appreciate your help though. This is the second Epic 4G to do this to me on everything but the stock rom which makes me think it's not hardware but if it's not happened to anyone else then not much else I can do.
Click to expand...
Click to collapse
Haha, yea well it was a big wall of text.
I've burned through my ideas, lol. Good luck to ya.
Np, I really appreciate the advice. So far i've rerooted, reflashed the FC09DeodexedMTD and did a straight sprint (no lollygagging with install and uninstall of apps) to a barebones what I want system, apps include then backed up via CWM. So far it's still working great though i'll keep my fingers crossed. Should anything happen I have a backup from the getgo that should put things back to the way they were, ie. working. Stupid problem, of corse it has to only be me with it.
Ciao
IT
Howdy Folks!
I recently got a SGH-I927 that is locked to AT&T.
I have read what I believe is all the relevant data about how to do the things I want, and I think I have it down, but I want to make sure I have everything exactly correct. I still have 6 days left with Virgin Mobile before I have to have all this done.
What I want to do...
Root
Back up my EFS
Update from 2.3.6 to 4.0.4
Carrier Unlock from AT&T so I can use a T-Mobile MVNO.
So my question is- is this the best order to do things in? I know I have to root before I can Unlock the phone or Backup my EFS, but I notice that there are two different methods for Rooting. I can root before I update to ICS or after. Does it make a difference? Which method is easier, which one is more reliable/safer? I also noticed that Unlocking the phone after updating to ICS requires an extra step, so that would be another factor.
Kies seems to be working, and when I plugged my phone in, it offered to update me from 2.3.6 (Baseband Ver I927UCKL1) to 4.04 (Baseband Ver I927UCLJ3), so it doesn't seem like updating will be a problem.
Are there any major issues with version two of the ICS update? I have read a lot of people that had issues with the first version of ICS that got released, and I know AT&T pulled it as an OTR update, but haven't heard a lot about version two. The people who have it are you satisfied with it? Did anyone prefer Gingerbread?
Thanks in advance for any help, and sorry if these questions have been answered already, I really did read through a LOT of information before posting here, and haven't seen these answered.
You don't need to root to unlock the phone. You just need to insert a code you buy from a seller on the internet.
I'm running the ULCHJ version of ICS and it works fine. I experienced the same GPS issue i had in GB, but the same fix worked it out and it I'm totally happy with it.
I can say, hope i won't regret, that there's nothing i should fix so far. Some minor issues were fixed as soon as i went through, I'm quite satisfied with this ROM now.
DarkBlaidd said:
Howdy Folks!
I recently got a SGH-I927 that is locked to AT&T.
I have read what I believe is all the relevant data about how to do the things I want, and I think I have it down, but I want to make sure I have everything exactly correct. I still have 6 days left with Virgin Mobile before I have to have all this done.
What I want to do...
Root
Back up my EFS
Update from 2.3.6 to 4.0.4
Carrier Unlock from AT&T so I can use a T-Mobile MVNO.
So my question is- is this the best order to do things in? I know I have to root before I can Unlock the phone or Backup my EFS, but I notice that there are two different methods for Rooting. I can root before I update to ICS or after. Does it make a difference? Which method is easier, which one is more reliable/safer? I also noticed that Unlocking the phone after updating to ICS requires an extra step, so that would be another factor.
Kies seems to be working, and when I plugged my phone in, it offered to update me from 2.3.6 (Baseband Ver I927UCKL1) to 4.04 (Baseband Ver I927UCLJ3), so it doesn't seem like updating will be a problem.
Are there any major issues with version two of the ICS update? I have read a lot of people that had issues with the first version of ICS that got released, and I know AT&T pulled it as an OTR update, but haven't heard a lot about version two. The people who have it are you satisfied with it? Did anyone prefer Gingerbread?
Thanks in advance for any help, and sorry if these questions have been answered already, I really did read through a LOT of information before posting here, and haven't seen these answered.
Click to expand...
Click to collapse
hi dark blaidd, welcome to glide!
if i were to do it over again i would backup my efs via adb on my computer before rooting or anything.
i used fastgsm to unlock my phone which is a codeless way to unlock and i suspect its how i lost my imei
certainly get a code and use dmans uclj3 deodexed rooted as the stable rom.. then you can use es explorer to modify sirgps.conf and gps.conf to get your gps working. before i switched to cm10.1 JB I was running it with no issues and instant GPS lock in all apps.
I will likely switch back as I have a new hands free stereo for my car that I would like to legally take advantage of
let us know if you run into issues you will need to do a few searches.
sbiricuda said:
You don't need to root to unlock the phone. You just need to insert a code you buy from a seller on the internet.
Click to expand...
Click to collapse
I'm a poor boy, so I am probably going to try and save a few bucks by using this method, which requires root.
I'm running the ULCHJ version of ICS and it works fine. I experienced the same GPS issue i had in GB, but the same fix worked it out and it I'm totally happy with it.
Click to expand...
Click to collapse
What was the GPS issue? Can you link to the fix please?
I can say, hope i won't regret, that there's nothing i should fix so far. Some minor issues were fixed as soon as i went through, I'm quite satisfied with this ROM now.
Click to expand...
Click to collapse
Cool, thanks for giving your opinion. How good is your battery life?
yohan4ws said:
hi dark blaidd, welcome to glide!
if i were to do it over again i would backup my efs via adb on my computer before rooting or anything.
Click to expand...
Click to collapse
Sounds like a good idea, I will do that.
i used fastgsm to unlock my phone which is a codeless way to unlock and i suspect its how i lost my imei
Click to expand...
Click to collapse
Noted, I will stay away from fastgsm. I think I am going to do this or GalaxSim Unlock.
certainly get a code and use dmans uclj3 deodexed rooted as the stable rom.. then you can use es explorer to modify sirgps.conf and gps.conf to get your gps working. before i switched to cm10.1 JB I was running it with no issues and instant GPS lock in all apps.
Click to expand...
Click to collapse
I can't believe I am about to say this, I have spent the last two years on custom ROMs, but I think I am fine with stock for now. The ROMs for the Glide look promising, but I MUST have Camera and Bluetooth, so I will probably wait until those issues get ironed out. There is also a chance that Samsung will update us to Jellybean, they just released an update for the Galaxy S2, so it's possible.
let us know if you run into issues you will need to do a few searches.
Click to expand...
Click to collapse
Thanks! I believe I have done enough research to do what I want, so hopefully I won't make any dumb mistakes.
DarkBlaidd said:
Update from 2.3.6 to 4.0.4
Click to expand...
Click to collapse
Don't bother with ICS, the official ROM has issues and we never did much dev at that level. Go to CM10.1 once you have the ICS bootloader.
Carrier Unlock from AT&T so I can use a T-Mobile MVNO.
Click to expand...
Click to collapse
About that... AT&T phones, even once unlocked, cannot use UMTS or HSPA+ on T-Mobile's network. It's a physical limitation of the radio. ONLY do this if you already KNOW you will be happy with EDGE.
DarkBlaidd said:
I can't believe I am about to say this, I have spent the last two years on custom ROMs, but I think I am fine with stock for now. The ROMs for the Glide look promising, but I MUST have Camera and Bluetooth, so I will probably wait until those issues get ironed out.
Click to expand...
Click to collapse
I'm in same boat here I guess. Just ordered a Glide, looking forward to having a physical keyboard again since my TP2 days. I was checking out the ROM options, found the link for "Stock UCLJ3 Rom" and it looks like that is the way go, other than maybe just staying stock... I need Bluetooth, Camera, GPS, and Tethering to work, so I guess I won't be messing around with anything fancy.
So don't do any OTA upgrade at all when I first get it out of the box? Just back it up, then root, and install UCLJ3 via CWM? Is this the best choice?
roothorick said:
Don't bother with ICS, the official ROM has issues and we never did much dev at that level. Go to CM10.1 once you have the ICS bootloader.
Click to expand...
Click to collapse
Doesn't CM10.1 still have issues, like with bluetooth, GPS, and camera?
idenlover said:
Doesn't CM10.1 still have issues, like with bluetooth, GPS, and camera?
Click to expand...
Click to collapse
There is not and never has been GPS problems that actually affect normal use. I don't know where people are getting that from. There's some anomalies in the data returned, but nothing that's actually used by the location API.
Bluetooth itself works, but there are some audio layer problems that interfere with headsets/earpieces and the like. (TBH our whole audio layer is a mess right now.) Stuff like OBEX and tethering should work fine.
Speaking of audio layer issues... there's still a longstanding bug where if userspace (i.e. an app; normal cell network phonecalls are fine) opens the microphone, audio output is corrupted. The biggest problem caused by this is the other person is basically unintelligible when calling in Skype. That and Bluetooth audio routing are really the only big problems we still have.
The camera was fixed months and months and months ago. I discovered the original fix even. There was a problem with audio in the video recorder that has now been solved recently.
roothorick said:
There is not and never has been GPS problems that actually affect normal use. I don't know where people are getting that from. There's some anomalies in the data returned, but nothing that's actually used by the location API.
Bluetooth itself works, but there are some audio layer problems that interfere with headsets/earpieces and the like. (TBH our whole audio layer is a mess right now.) Stuff like OBEX and tethering should work fine.
Speaking of audio layer issues... there's still a longstanding bug where if userspace (i.e. an app; normal cell network phonecalls are fine) opens the microphone, audio output is corrupted. The biggest problem caused by this is the other person is basically unintelligible when calling in Skype. That and Bluetooth audio routing are really the only big problems we still have.
The camera was fixed months and months and months ago. I discovered the original fix even. There was a problem with audio in the video recorder that has now been solved recently.
Click to expand...
Click to collapse
OK, so then just the random app microphone and bluetooth issues still remain... So you still say it's worth it? I'm leaning towards the debloated rooted stock as I'm just lazy and want everything to work.
idenlover said:
OK, so then just the random app microphone and bluetooth issues still remain... So you still say it's worth it? I'm leaning towards the debloated rooted stock as I'm just lazy and want everything to work.
Click to expand...
Click to collapse
Official ICS was something of a ****storm, as Samsung never did get it to work quite right. There was a myriad of weird keyboard issues, intermittent radio problems, and come to think of it, I think I know where the GPS thing came from... official ROMs have lethargic GPS if you're not on AT&T. I'd say 99% of power users with a Glide are on one build/variant or the other of CM10.1 because it's the most problem-free ROM that's not, ugh, Gingerbread.
The primary value of official ICS to us was the kernel sources and RIL blobs -- the last few critical bits and pieces we needed to make our own ROMs and properly connect them to all the phone hardware.
I'd say, once you have everything backed up:
Flash official ICS UCLJ3 (for the bootloader and baseband)
Flash CWM over the top of it
Use CWM to flash the current CM10.1 build and gapps. Call it good.
roothorick said:
Official ICS was something of a ****storm, as Samsung never did get it to work quite right. There was a myriad of weird keyboard issues, intermittent radio problems, and come to think of it, I think I know where the GPS thing came from... official ROMs have lethargic GPS if you're not on AT&T. I'd say 99% of power users with a Glide are on one build/variant or the other of CM10.1 because it's the most problem-free ROM that's not, ugh, Gingerbread.
The primary value of official ICS to us was the kernel sources and RIL blobs -- the last few critical bits and pieces we needed to make our own ROMs and properly connect them to all the phone hardware.
I'd say, once you have everything backed up:
Flash official ICS UCLJ3 (for the bootloader and baseband)
Flash CWM over the top of it
Use CWM to flash the current CM10.1 build and gapps. Call it good.
Click to expand...
Click to collapse
Ok great, thanks for the explanation/breakdown So if there is an OTA update that pops up right out of the box, do I do it or skip it? And I'll have to root before flashing the UCLJ3, right?
idenlover said:
Ok great, thanks for the explanation/breakdown So if there is an OTA update that pops up right out of the box, do I do it or skip it? And I'll have to root before flashing the UCLJ3, right?
Click to expand...
Click to collapse
Might as well, as if it happens to be UCLJ3, well, it just did Step 1 for you, and if not, well, it doesn't matter either way.
You don't really need root for any of this since our bootloader is unlocked OOB.
roothorick said:
Might as well, as if it happens to be UCLJ3, well, it just did Step 1 for you, and if not, well, it doesn't matter either way.
You don't really need root for any of this since our bootloader is unlocked OOB.
Click to expand...
Click to collapse
Awesome, thanks for the help!:good:
roothorick said:
About that... AT&T phones, even once unlocked, cannot use UMTS or HSPA+ on T-Mobile's network. It's a physical limitation of the radio. ONLY do this if you already KNOW you will be happy with EDGE.
Click to expand...
Click to collapse
Damn it, that really sucks. Thank you so much for letting me know that, you saved me some headaches.
Edit: I did some digging around to get a technical explanation of this issue and stumbled across some unexpectedly good news, I can use HSPA+ on T-MO, well halfway at least, I'm going to make a new post as a public service.
Hey guys,
I think I've reached the point where it's time to call in the cavalry and see if anyone around here is having the same issue; there appears to be a plague going around on the Verizon network, specifically in the Pennsylvania area, preventing people from sending SMS, but still receiving fine (and 4G works fine too, for the record). MMS still sends / receives fine, but I'm unable to send SMS. There are tricks to allowing a single SMS message to go through which involves toggling Airplane mode on / off every. Single. Time. People have also had success with turning 4G off completely, using the CDMA band after a reboot at which point they can send *several*, but still end up with the same issue.
The only solution I've read about that FIXED it is by reverting back to complete stock from VZW. Performing factory resets, using other ROMs, etc etc...doesn't work. I'd REALLY rather not do this and, frankly, would rather use 3G / toggle Airplane mode for texts than use Sense and get off of my ROM (http://forum.xda-developers.com/showthread.php?t=2560831).
People from other device forums on XDA are having the same problem; the ones I've seen that are active discussions are the Samsung Galaxy S III & IV. They're mostly CM ROMs *as well as* AOSP ROMs in general.
http://forum.xda-developers.com/showthread.php?t=2532414
http://forum.xda-developers.com/showthread.php?t=2658572
SIM card replacements are a no-go, and the recorded instances seem to be in the 717 / 570 area codes, mostly. Now I DO know that VZW released an OTA update for the One recently, and I'm relatively confident that would fix the issue, but I've no idea why. I'm thinking perhaps they dispatched new radios? I looked around a bit and couldn't find any flashable zips of radios extracted from the latest OTA, that's the next step I'll be trying once that download finishes.
So is anyone else having this issue? Any word on fixes?
The newest firmware from the latest OTA can be found in the 2nd post in this thread: http://forum.xda-developers.com/showthread.php?t=2485319
If you've already flashed the latest firmware then I'm not sure what to tell you... maybe ask your favorite rom developer to take a look at the latest OTA in regards to this issue?
If it has the stock rom and OTA update why not take it to the store and let them look at it. Something might be wrong with your account.
movieman999 said:
Hey guys,
I think I've reached the point where it's time to call in the cavalry and see if anyone around here is having the same issue; there appears to be a plague going around on the Verizon network, specifically in the Pennsylvania area, preventing people from sending SMS, but still receiving fine (and 4G works fine too, for the record). MMS still sends / receives fine, but I'm unable to send SMS. There are tricks to allowing a single SMS message to go through which involves toggling Airplane mode on / off every. Single. Time. People have also had success with turning 4G off completely, using the CDMA band after a reboot at which point they can send *several*, but still end up with the same issue.
The only solution I've read about that FIXED it is by reverting back to complete stock from VZW. Performing factory resets, using other ROMs, etc etc...doesn't work. I'd REALLY rather not do this and, frankly, would rather use 3G / toggle Airplane mode for texts than use Sense and get off of my ROM (http://forum.xda-developers.com/showthread.php?t=2560831).
People from other device forums on XDA are having the same problem; the ones I've seen that are active discussions are the Samsung Galaxy S III & IV. They're mostly CM ROMs *as well as* AOSP ROMs in general.
http://forum.xda-developers.com/showthread.php?t=2532414
http://forum.xda-developers.com/showthread.php?t=2658572
SIM card replacements are a no-go, and the recorded instances seem to be in the 717 / 570 area codes, mostly. Now I DO know that VZW released an OTA update for the One recently, and I'm relatively confident that would fix the issue, but I've no idea why. I'm thinking perhaps they dispatched new radios? I looked around a bit and couldn't find any flashable zips of radios extracted from the latest OTA, that's the next step I'll be trying once that download finishes.
So is anyone else having this issue? Any word on fixes?
Click to expand...
Click to collapse
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
DreamFX said:
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
Click to expand...
Click to collapse
Thanks DreamFX; I've been following this thread (http://forum.xda-developers.com/showthread.php?t=2658572&page=6) lately as they seem to be the most on top of it. I can't believe Verizon has let this issue go on for so long, but given that it seems to only be relevant to those of us with AOSP ROM's, I guess it makes sense. At least I'm still able to send texts, if not only through a silly process of toggling airplane mode on / off. Hopefully it gets resolved soon...
DreamFX said:
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
Click to expand...
Click to collapse
movieman999 said:
Thanks DreamFX; I've been following this thread (http://forum.xda-developers.com/showthread.php?t=2658572&page=6) lately as they seem to be the most on top of it. I can't believe Verizon has let this issue go on for so long, but given that it seems to only be relevant to those of us with AOSP ROM's, I guess it makes sense. At least I'm still able to send texts, if not only through a silly process of toggling airplane mode on / off. Hopefully it gets resolved soon...
Click to expand...
Click to collapse
I'm getting this too, just started for me today from what I can tell. Driving me bonkers but, Airplane mode toggle totally works for me. :cyclops:
VZW SGS4 running AOSPA with 804 area code operating in Oregon.
dickenam said:
I'm getting this too, just started for me today from what I can tell. Driving me bonkers but, Airplane mode toggle totally works for me. :cyclops:
VZW SGS4 running AOSPA with 804 area code operating in Oregon.
Click to expand...
Click to collapse
Whoa, that's weird. I really thought it was isolated to the 717 area code. It's getting pretty crazy...I've been dealing with this for a few weeks now and my patience is running thin. Unfortunately it's not like we can just report this to VZW because all anyone would tell us to do is "restore to factory", which simply isn't a solution.
movieman999 said:
Whoa, that's weird. I really thought it was isolated to the 717 area code. It's getting pretty crazy...I've been dealing with this for a few weeks now and my patience is running thin. Unfortunately it's not like we can just report this to VZW because all anyone would tell us to do is "restore to factory", which simply isn't a solution.
Click to expand...
Click to collapse
Yup, I thought so too. Just cropped up between 10a and 11a PDT. Like you said MMS is fine, simply affects SMS. And yes, restoring stock is simply not an option. Going to TMobile, however, is totally an option that I'm considering more and more often......
EDIT: AND SMS began sending properly (without workaround) for me around 8p PDT last night, just tested and still ok. RESOLVED!
EDIT EDIT: Issue now persists....sadface =[
Sent from my SCH-I545 using Tapatalk
dickenam said:
Yup, I thought so too. Just cropped up between 10a and 11a PDT. Like you said MMS is fine, simply affects SMS. And yes, restoring stock is simply not an option. Going to TMobile, however, is totally an option that I'm considering more and more often......
EDIT: AND SMS began sending properly (without workaround) for me around 8p PDT last night, just tested and still ok. RESOLVED!
EDIT EDIT: Issue now persists....sadface =[
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
IM getting it now. but not exactly the same. phone freezes without warning and I have to toggle airplane mode and restart to get it to unfreeze. this happened after the last OTA update. I am going to a custom ROM until I don't read anything about this for a while