SMS "Pending" Problem - Thunderbolt General

Hey everyone, just wanted to say that even though I have very little posts here, I have been following this forum for a long time now and I have gotten a lot of great info from everyone on XDA. Finally started to contribute now that I am getting more and more knowledge of the devices.
I couldn't seem to find a post on this so I thought I would post it...
I use Handcent for text messages, and since the majority of my friends use Verizon, I have "delivery reports" enabled so I can see if they do get delivered. Recently, starting last night and today whenever I sent a text it would stay in the pending phase for a very very long time and sometimes took a reboot or another text message sent to have them go through. Odd thing is, I can make phone calls or do anything else that requires data service. Past 2 hours or so it has been fine but since then I have flashed to a different radio. I am using the leaked radio, but the New CDMA/Old LTE combo.
Here are some things that may be useful:
ROM: Vanilla Bean 1.2
Baseband Radio: 1.16.00.0402w_1 (New CDMA/Old LTE - Radio Posted in Vanilla Bean Thread)
Kernal: 2.6.32.21_bamf_4.3a
Software: 1.13.605.7
Has anyone else experienced something like this? I tried the leaked radio with new CDMA and LTE but since I don't get 4G in my area yet, it caused more issues of signal going in and out constantly.

Related

Radio problems

I have been experiencing some pretty severe radio issues. I have been missing calls without the phone ringing and people have to call me multiple times to get through even when I have great signal. My radio switches to 1x for long periods of time and loses all signal randomly (or it goes back and forth between EvDo and and 1x rapidly). This has just started happening over the last week or two and I live in a large city that normally has really great sprint 3g coverage. Today, I got an error that said something about "insufficient radio resources" so I figure that could be related to the problem. I am running Fresh 2.0d and using the 2.42.00.03.10 radio. I think the problems may have started after I tried to update my PRL, but it seemed to update fine and is currently 60664. Has anyone else had this kind of problem and/or know any fixes? Thanks.
This has nothing to do with "Hero CDMA Android Development". I would reload your backup.
.........................
This used to be the area to ask for help when you have problems on the phone running a modded rom/radio. If that has changed I didn't realize it. I have tried going to backups but the problem persists. If you don't want to offer help then don't, but you could be less of a ****.
If this is the wrong forum could a mod plz delete the thread and I'm going to repost in the General forums (although the general forum doesn't seem like the place for Rom/radio problem either)
Maybe flash another radio and see how that works
http://forum.xda-developers.com/showthread.php?t=659762

[Q] Anyone else having this problem?

I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
sliderocket22 said:
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
Click to expand...
Click to collapse
Yep, happens to me all the time. Internet doesn't always work either. I "fixed" the problem by setting it to GSM only mode. Now I only have EDGE internet.
brandon827 said:
Yep, happens to me all the time. Internet doesn't always work either. I "fixed" the problem by setting it to GSM only mode. Now I only have EDGE internet.
Click to expand...
Click to collapse
Are you on the same rooted stock rom, or something different? I don't seem to remember having this problem when I was just on pure stock AT&T with no root. Somewhat annoying, as I'll have to place a call 3 or 4 times to get it to go through, but what's really annoying is that it is so sporadic I can't gauge when it'll happen!
sliderocket22 said:
Are you on the same rooted stock rom, or something different? I don't seem to remember having this problem when I was just on pure stock AT&T with no root. Somewhat annoying, as I'll have to place a call 3 or 4 times to get it to go through, but what's really annoying is that it is so sporadic I can't gauge when it'll happen!
Click to expand...
Click to collapse
I've noticed this at multiple times, but haven't been able to narrow down what's causing it. I was running Revolution 1.15, and I think it started when I applied the .16 performance patch. It got so bad last night I couldn't make/receive calls for hours. I did a full wipe an reinstalled 1.15 and all has been well the last 24 hours. I just flashed the 2.1 patch but we'll see what happens. Note: Not only can you not make calls when this is happening you won't be able to receive calls either. It does appear to most often happen when bouncing between networks (HSDPA, UMTS, Edge, etc)
homeslice976 said:
I've noticed this at multiple times, but haven't been able to narrow down what's causing it. I was running Revolution 1.15, and I think it started when I applied the .16 performance patch. It got so bad last night I couldn't make/receive calls for hours. I did a full wipe an reinstalled 1.15 and all has been well the last 24 hours. I just flashed the 2.1 patch but we'll see what happens. Note: Not only can you not make calls when this is happening you won't be able to receive calls either. It does appear to most often happen when bouncing between networks (HSDPA, UMTS, Edge, etc)
Click to expand...
Click to collapse
Man, I'm glad I'm not the only one having this problem. I thought my phone was defective at first, and now I don't feel so crazy anymore. My sister was furious with me, I had to pick her and her boyfriend up from DIA yesterday to take her to Copper Mountain to snowboard with my girlfriend and myself, and she called me 4 times and I didn't receive a single one. I wonder if it has anything to do with HSUPA being enabled on the phones, but at this point I'm just ready to give up root and go back to stock. I don't make tons of calls, but I'd like to be able to when I need to, and for my phone to not hang up on me in the middle of one. I have noticed though it's particularly bad for me when I'm on bluetooth.
I was also having those problems
I am using Revolution 4G 2.1. I'm in the process of trying to get the problem figured out. Stock rooted rom had problems for me because you couldn't set it to GSM only, and that's the only way I've found to make the phone reliably work as a phone.
If anyone can figure it out, I'd love to know what causes it. I've been poking around myself, but haven't come up with anything worthwhile. I suppose I'll flash a different rom and try that.
Sent from my Desire HD using XDA App
Anyone found any clue as to why this happens? I've searched the dev forums but nobody seems to mention this, which makes me wonder if most people have this problem.
Sent from my Desire HD using XDA App
I have never had this problem. Running a rooted stocker.
Sent from my Desire HD using XDA App
It happened to me again last night. Still had data but lost the ability to make/receive calls. I switched network to GSM only, the data switched to EDGE, and i was able to make/recieve calls. Turned back to GSM/WCDMA, no calls. Rebooted, no calls. Turned back to GSM only, calling functionality returned. I did another full wipe, installed AR 2.1, sound fix, apache 1.6 kernel, and calling is restored when connected to HSDPA/WCDMA. Has been working fine for the last 12 hours. I'll keep you updated. I don't know why it's doing this, and it doesn't make sense as to why a wipe would fix it. The first time this happened I was runing the stock radio. Last night when it happened i was running the recommended radio in the AR thread (M2). I've now switched back to stock this time...let's see what happens
Edit: I am also glad to know I'm not the only one having these issues...maybe someone a LOT smarter than I am can figure it out. It's annoying to have to have a slow data connection to have a reliable voice connection. The last Android I had (LG GW620 Eve), also did this from time to time, but I just blamed it on the fact that it was a POS. My voicemail actually went like this "This is Greg. I probably have no idea you called me just now, so please leave a message and I'll get back to you"
Edit: mike1986 (android revolution developer) just chimed in in his thread and stated these issues should be fixed in version 3.0 set to be released soon. Is anyone else that's having these problems NOT running Revolution?
sliderocket22 said:
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
Click to expand...
Click to collapse
I had this problem when I first rooted (running Inspire 4G Stock Rom w/Root, HSUPA, and Sideloading from the development section) I installed Android Revolution 2.1 and it went away.
I know from my captivate days that sometimes a ROM just hiccups and a fresh flash can fix the issues. I don't know if this is the same with HTC, but it's all android so It's plausible.

Data blinks in and out on AOSP only since getting new SIM

5/19/2013 Update: The bug might be dead! Like for real this time. See this post, post number 14 in this thread with an explanation of what to do.
10/25/2012 Update: TRY THE LATEST BUILDS OF BRUCE'S CM10 STARTING WITH THE 10/25 VERSION!
Bruce has made a change that helps differentiate between the regular data stream and the MMS data stream in an attempt to see if that was what was causing the instability issue. This is only on Bruce's CM10 Kang as of 10/25. If you are only another CM ROM, flash Bruce's (even if just for a minute or two) and see if the data bug goes away. Please report back if it did!
If this does cure it, I'm sure Bruce will share the sollution to all other devs and your favorite other AOSP ROm will have the cure shortly.
Updated 10/24/2012
This is a detailed description of the 6 million or so things that various people have attempted to do in order to rectify the blinking data connection problem plaguing T Mobile USA users on AOSP ROMs for the Sensation. This issue is non existant in Sense based ROMs.
The problem has something to do with how the Sensation authenticates itself with the T Mobile Data Network. It's not based on the cell towers as voice calling is unaffected. The theory is that the AOSP framework lacks the proper authentication certificates for part of the data network and when the phone is routed to that part of the network, it gets kicked off teh network, then continually retries to connect.
This was and issue on the Sense Gingerbread Stock ROM in 2011 but T Mobile and HTC patched it. All Sense ROMs are free from this bug. But no one knows what exactly the patch was so AOSP ROM's have not been able to be cured yet.
Short version....
Problem started for me on Bruce's CM10 rom. But it's reported on all CM10 variants and most CM9 ROM's as well.
One day I noticed that data wasn't connecting well. It would blink on and off. Sometimes it would stay on, but if I turn it off then right back on, it might go back to blinking.
The problem exists on all AOSP roms (AOKP, CM9, all versions of CM10) even after full wipes and restores of known working nandroids.
Cell signal for voice calls works perfectly. No problems whatsoever. So the phone is connecting to T Mobile. It just won't get data.
Long version....
To fix this I've tried the following...and how each does or doesn't work.
Switch to 2G networks only and switch back. Problem remains, and still blinks E on the EDGE networks rather than being solid on them.
Updated the radio. Problem remains.
Updated the entire firmware package. Problem remains.
Superwipe and flashed Sense, verify data works well. Then regular wipe and flash a fresh install of CM10. Problem remains.
Flashed clean version of CM10 and fixed permissions. Problem remains.
Made calls from the phone. Some people have reported that this helps temporarily.
Sent myself a text message. Some people have reported that this helps temporaliy.
Turn on airplane mode for a minute then go back to normal. Some people have reported that this helps temporarily.
It's not related to Wifi at all because I've created the error on fresh installs of CM10 before ever turning Wifi on.
Formatted SD card. Problem remains (and just to be sure I got the error while the blank formatted SD was removed from the device)
Checked the APN's 100 times. They are correct.
Spent an hour on the phone with T Mobile. Their tech said everything looked good on their end. He cleared the SIM and reactivated it. Problem remained.
Other people have gotten new SIM cards and found that while they helped right away, the problem eventually came back.
The only things that have shown any help to multiple users are in bold above. There are various reports of 100 other 'fixes' that people swear fixed the problem for them. But all of them involved the phone disconnecting from the network and reconnecting. That appears to be the key to get data working again temporarily. Making calls and sending yourself text messages also forces authentication on the T Mobile network without breaking the original connection.
If you want more details or want to review the logs to see if you can figure it out, logcats of the problem are located in this post! Click here for logcatty goodness!
Here is the real kicker....
Everyone once in a while...it connects. And once it's connected it'll stay connected until I turn the connection off or reboot the phone. Then it'll go back to blinking in and out when I try to turn it back on.
Just another note, the data is finicky on my old LG G2x also on TMobile with AOSP based ROMs, talk works, but cell data won't come back after going into airplane mode and out, until a reboot. It works fine on official TMobile ROMs. I suspect there may be some proprietary cell data negotiation between handset and Tmobile towers that AOSP code doesn't have.
Whyzor said:
Just another note, the data is finicky on my old LG G2x also on TMobile with AOSP based ROMs, talk works, but cell data won't come back after going into airplane mode and out, until a reboot. It works fine on official TMobile ROMs. I suspect there may be some proprietary cell data negotiation between handset and Tmobile towers that AOSP code doesn't have.
Click to expand...
Click to collapse
Okay here's an update on this for anyone who finds this thread through a search or Google or something....I'll try to describe this using the simplest terms possible so those of us who aren't cell tower engineers can understand it. (And I assume that's most of us, including me!)
The latest running theory is that the issue occurs due to the way the phone is handed off from 1 tower to another.
As you move your phone is handed off from one tower to the next. You get unregistered with tower 1 and reregistered with tower 2. That's normal.
However if you are within range of 2 towers you can't be on both. You have to be registered with 1, and that's supposed to be the stronger one. But AOSP ROMs lack a T Mobile certificate that authenticates which tower is supposed to have priority. So when the data is blinking you are getting bounced between 2 towers because the phone is trying to register with both.
The latest version of Bruce's CM10 ROM (Dated 10/10/12 and with TMOUS DATA in the rom name on the download page) supposedly includes patches that fix how this authentication works. And I only say 'supposedly' because the patches have only been up for about 12 hours so the jury is still out on how well it works. Personally I've been on it all day today and haven't had the data issue yet. But it can be days in between seeing it. So it'll take a while to know for sure that it's fixed.
If this turns out not to be the exact cause of the problem, it's something similar and a final sollution should be found soon.
Update: This have never been substantiated, and several users with the bug have reported knowing for a fact that they experience the problem when in range of only 1 tower.
Hi,
I have noticed with JB ROMS that you get 7 or 8 APN's,most of which do not apply to me.
Have you tried (making a note of your one first) and deleting all the APN's
Reboot,and just install yours.
malybru said:
Hi,
I have noticed with JB ROMS that you get 7 or 8 APN's,most of which do not apply to me.
Have you tried (making a note of your one first) and deleting all the APN's
Reboot,and just install yours.
Click to expand...
Click to collapse
That's one of the 1000 things that's been tried, to no effect. If he APN is set to the correct one the extra APN's are ignored.
Nothing that you do within the phone can cure the problem. At most, forcing the phone to re-register with the tower is the only thing that can help, and that will be temporary if it works at all.
The best bet now is to hope that Bruce fixed it with his latest additions to CM10 now that we understand what the actual problem is (or at least that we think we do)
Update....
T Mobile data is still broken. It has not been fixed yet. The latest theory may just be one more in a long line of theories that turned out to be wrong.
There are days when I really hate this phone.
Thanks for the update. I've been monitoring that thread occasionally, but it has way too much traffic for me to keep up. I was close to switching to it, but I need good battery life and reliable cell service over any smoothness benefits of JB, which is why I'm sticking with HyperNonSense ICS for now.
been experiencing this issue for a couple months myself. currently stuck in a no data bout as we speak. i'm wondering if it has anything to do with the amount of data we've used. i noticed this last bout started right around the time i passed 5gb. should also be noted i'm on the unlimited 4g plan and tether like crazy. i guess i'll know if the problem persists until my next billing cycle. for now i'm stuck with a sense nandroid and crack flashing aosp daily to see if it's fixed.
cpittman said:
been experiencing this issue for a couple months myself. currently stuck in a no data bout as we speak. i'm wondering if it has anything to do with the amount of data we've used. i noticed this last bout started right around the time i passed 5gb. should also be noted i'm on the unlimited 4g plan and tether like crazy. i guess i'll know if the problem persists until my next billing cycle. for now i'm stuck with a sense nandroid and crack flashing aosp daily to see if it's fixed.
Click to expand...
Click to collapse
I have tried the SIM swap fix. And that has apparently worked. I've been using in good for about the last 6ish hours without any problems. :good:
So i'd give that a shot if your willing.
I've been using CM10 KANG since it was available for HTC sensation. Never had the data blink issue. Recently, my phone started to have this issue. Data would simply not connect with CM10 or CM10.1 with any radio/firmware combination. I also noticed that when I travel to work, i get data say after 10 miles away from my home and it continues to work after coming back home. However, after restarting the phone, i hit the blink problem again. Wondering if its because of some cell tower maintenance/upgrade near my area.
So I was on bruce's ROM until a week ago and this never happened while on his ROM. Just upgraded to albinoman's ROM and this started happening. I have to send myself a MMS picture to get it back again. Hope this helps
Fix
Ive had this problem on and the only thing that seems to help is flashing a new ROM but then a few weeks later it returns... I realized that this only happens when I try to send an MMS message or attempt to receive them. I don't know how to stop receiving an MMS but just delete the picture message you're trying to send and your data should stop blinking on and off. Can't guarantee it'll work for you but it worked for me! GL!!
It appears as though this stupid annoying silly obnoxious bug has finally been squished, sprayed with 3 cans of Raid, and its' mangled corpse then burned to a crisp...I hope.
3 weeks ago W1ldFl0wer brought this fix to Albinoman's attention...
In the build.prop under phone>system was the following line....
ro.telephony.ril.v3=datacallapn,signalstrength
This line appeared like this on all AOSP roms for the sensation.
The fix was to add skipbrokendatacall to the line so it looked like this....
ro.telephony.ril.v3=datacallapn,signalstrength,skipbrokendatacall
Save the file, reboot, and data should spine right up and work fine. So far the peopl ewho have run into the data bug have implimented this change and BOOM, data fixed.
So if you use any AOSP ROM 4.0, 4.1, or 4.2 other than Albino's CM10.1 Kang just add skipbrokendatacall to that line and see if it fixes it. Only do this if you on in the US on T Mobile's network. If you are in parts of Europre making this change will screw up your data.
If you are using Albinoman's CM10.1 Kang ROM, he has already included this line in the build.prop for you. You just have to activate it. About 30 lines into the build.prop is the new line that reads...
#ro.telephony.ril.v3=datacallapn,signalstrength,skipbrokendatacall
Just delete the # in front of that line. (The # makes the ROM skip the line when loading everything, but lets it stay in the file so you can read it. Deleting the # means that the phone will read that line when it reboots.) Then go up to the line that says the same thing without skipbrokendatacall and delete that line entirely. Save the file and reboot. If you don't delete the original line without skipbrokendatacall, your phone will go haywire, data might not work at all, and you might inadvertantly trigger Z Day. So if you're not ready to fight in the zombie apocolypse, only leave one of those lines in the build.prop.
Hope this cures it for everyone! Again, don't make this change if you live outside the USA or are not on T Mobile's network! Doing so on other networks in other parts of the world could make things worse for your phone!
Here is the link to the post where W1ldFl0wer informed Albinoman of this fix.
http://forum.xda-developers.com/showpost.php?p=40755845&postcount=9003
I don't think W1ldFl0wer invented the fix, but he certainly is the one who made it public to Sensation users so go to that post and thank him/her bcause I might finally be able to stop obsessing over this stupid bug because of this user!!! :good:

Text Messages arriving hours late

Since December 6th, I've had occasional difficulty receiving text messages in a timely manner. Believing it to be caused by an outdated CM10 nightly, I downloaded the latest (at the time December 10) and did a factory reset. Since then, the issue has been largely non-existant. However, today, I experience it.
I decided to do a little digging. Using an XML backup of my SMS messages, I decided to see how many messages have been delivered over an hour after they were sent. In the six months of SMS history, there've been only 30 messages delivered over an hour after they were sent, all after December 6th. On average, these messages are arriving 3.7 hours late, and only after I send a message first. (For example, I pick up my phone, send a message, and suddenly receive several messages.)
I've run my current build of CM10 for almost a week, and have only had noticeable issues today. (Keep in mind this issue doesn't seem to occur if I send texts on a regular basis.)
Anyone have an idea why this might be happening? Could this be caused by my ROM, and if so, should I try switching to another?
Have you tried a different radio?
dstaley said:
Since December 6th, I've had occasional difficulty receiving text messages in a timely manner. Believing it to be caused by an outdated CM10 nightly, I downloaded the latest (at the time December 10) and did a factory reset. Since then, the issue has been largely non-existant. However, today, I experience it.
I decided to do a little digging. Using an XML backup of my SMS messages, I decided to see how many messages have been delivered over an hour after they were sent. In the six months of SMS history, there've been only 30 messages delivered over an hour after they were sent, all after December 6th. On average, these messages are arriving 3.7 hours late, and only after I send a message first. (For example, I pick up my phone, send a message, and suddenly receive several messages.)
I've run my current build of CM10 for almost a week, and have only had noticeable issues today. (Keep in mind this issue doesn't seem to occur if I send texts on a regular basis.)
Anyone have an idea why this might be happening? Could this be caused by my ROM, and if so, should I try switching to another?
Click to expand...
Click to collapse
I'm stock rooted but you're not the only one having this issue. I was actually locked too when this was happening as well. The messages take a long time to arrive and when they do, they come in droves.
However, it doesn't happen to every person I know texting me. On Att as well.
Sent from my HTC One X using xda app-developers app
Genetic517 said:
Have you tried a different radio?
Click to expand...
Click to collapse
CM10 bundles the radios into the .zip, thus making it more difficult to flash radios. I'm running the only AT&T radio, but I might try flashing one of the few CM10 compatible radios tomorrow and see how much luck I get with it.
ToxicWaste said:
I'm stock rooted but you're not the only one having this issue. I was actually locked too when this was happening as well. The messages take a long time to arrive and when they do, they come in droves.
However, it doesn't happen to every person I know texting me. On Att as well.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I've been able to determine that, after an indeterminate amount of inactivity, the phone won't receive *any* text messages sent to it until you send one out. Today, happened after just thirty minutes in my pocket. Pulled it out, sent one, and then received five. Is your phone receiving them on its own, or are you only getting them after you've sent a message?
dstaley said:
CM10 bundles the radios into the .zip, thus making it more difficult to flash radios. I'm running the only AT&T radio, but I might try flashing one of the few CM10 compatible radios tomorrow and see how much luck I get with it.
I've been able to determine that, after an indeterminate amount of inactivity, the phone won't receive *any* text messages sent to it until you send one out. Today, happened after just thirty minutes in my pocket. Pulled it out, sent one, and then received five. Is your phone receiving them on its own, or are you only getting them after you've sent a message?
Click to expand...
Click to collapse
Now that you mention it, if I send a text, then I get everyone else's late and in bundles. However, I've had it be jus a couple people but mostly from just one person. That person also has a completely stock HOX. Mins was doing it too when it was completely stock.
from my HTC One X using xda app-developers app
Your post came through without any text from you btw
I've noticed the exact same prob on my phone as well. I'm running Nocturnal's Dirty Rom 2.3c hmmm interesting issue luckily it hasn't been a huge prob to me, yet.
WeWearFedoras said:
I've noticed the exact same prob on my phone as well. I'm running Nocturnal's Dirty Rom 2.3c hmmm interesting issue luckily it hasn't been a huge prob to me, yet.
Click to expand...
Click to collapse
What radio and carrier are you on?
It doesnt seem like this has been solved yet and I have been getting this issue,too! has anybody been able to fix this issue?
dstaley said:
CM10 bundles the radios into the .zip, thus making it more difficult to flash radios.
Click to expand...
Click to collapse
This I'm afraid is incorrect, if ROMs contained radio images then there would be quite a few more bricks.
They don't include them for this reason
The reason why you can't flash certain radios because the ones in the dev section include the ril. And because the sense ril is much different from a aosp one it causes issues when you flash a radio. Hense why there are separate versions for those who are running a aosp ROM
Sent from my One X using Tapatalk 2
superchilpil said:
This I'm afraid is incorrect, if ROMs contained radio images then there would be quite a few more bricks.
They don't include them for this reason
The reason why you can't flash certain radios because the ones in the dev section include the ril. And because the sense ril is much different from a aosp one it causes issues when you flash a radio. Hense why there are separate versions for those who are running a aosp ROM
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
h8rift said:
Yes, radio firmware currently is being set to 1.85 on boot.
Now, for those who are upset, and want 2.20.....note that I am right now working on updating our prop libs so it will be 'updated' to 2.20 att release radio. On boot, the radio firmware is updated to what the ROM has in it, for those curious about why it seems the flashable radios are not 'taking effect'. This will help reduce radio firmware outliers and keep the rom all together on the same versions of software.
Click to expand...
Click to collapse
CM10 bundles the radio into the .zip so that everyone is using the same, as there are like 17 variants of radios for the Evita. It loads it on boot from a location (/system/etc/firmware) different than the normal radio.img flashes, which is why even when you flash them, the ROM uses the bundled one.
This has been happening to me as well since about Dec 6 as mentioned in OP. I am rooted various roms, Original and Sense ICS or JB. Now I think this is an ATT issue. My other line on my account also a HTC OneX Virgin (Stock, NOT rooted, 2.20) used by a friend has the same problems. Sometimes its 20min late up to hours late. We both have issues where texts when they do finally come through like one other mentioned you get all at once. Time Received will show something like 8:00pm, sent 6:00pm...
jatipton said:
This has been happening to me as well since about Dec 6 as mentioned in OP. I am rooted various roms, Original and Sense ICS or JB. Now I think this is an ATT issue. My other line on my account also a HTC OneX Virgin (Stock, NOT rooted, 2.20) used by a friend has the same problems. Sometimes its 20min late up to hours late. We both have issues where texts when they do finally come through like one other mentioned you get all at once. Time Received will show something like 8:00pm, sent 6:00pm...
Click to expand...
Click to collapse
I agree with you 100%. I was posting here weeks ago when the OP created the thread. I was bone stock then and it was happening. Happening rooted with different Roms too. It has been happening to my brother and his wife with S3s and my fiance and I on HOXs. We are all on ATT.
I think ATT is putzing with something but unrelated to phones on Roms. Been happening for a while now. In fact, has anyone else just had LTE implemented? Went up here just over a month ago and seems ever since my texts aren't getting to people fast enough and vice versa.
ATT HOX Premium App--Stock is fine but modded is Creative
I find this happens on mine at times when I'm in a poor lte signal area.
I send a message to myself once a day to flush system an I see it at these times, if I turn lte off and go hspa they come through fast.
I don't think lte is culprit I believe its in the carriers hand off between lte hspa imo.
WR
Sent from my HTC One XL using xda app-developers app
IV had this issue and I have a temporary fix for it. I say temporary because if u turn your phone off you'll have to do it again. I had this issue for the longest with my one x I hope this works for you type this in your dialer *#*#4636#*#*. Once done goto phone information. Then scroll till u see something above turn off radio. It should say something like lte wdcma prl gsm... What u have to do is change it I use the PRL one... I hope this works
Sent from my HTC One XL using xda app-developers app
This often happens to me when I switch from a aosp rom to a sense rom. I often just wipe cache and than toggle airplane mode and all my messages catch up with everything.
Sent from my HTC One XL

Weird Issue Call Drop using custom ROMS In the Middle of Conversation

I have the strangest issue. I get disconnected from calls in the middle of conversation if I'm using any of these main custom ROMs.
Blaz3r
CyanogenMod 10
Blaze Tweaked ICS 2.2
But If I'm using a stock ICS ROM or "Android ICS 4.0.4 UVLH5 (Posted by tthaz777)" everything is very stable and no disconnects.
I have full bar with all the ROMs and get perfect data speed and everything else works fine. I'm using the same exact apps on the ROMs as I do on the stock, so I don't think it's related to a particular app. It seems as if TMobile scans the sessions at their network level and disconnects the call because my connection is not providing some information/call data they need. The disconnect can happen as fast as a few seconds or after a 10 minutes or so, just random.
Is anyone else experiencing this ?
I'm currently running below and everything is stable with no drop calls. Just can't figure out why this happens when install any other ROM. and Yes I always to do a full wipe before install.
Android ICS 4.0.4 UVLH5 (Posted by tthaz777) with merwin's scorched-kernel-t769-ics v1.0.29
Well the 4.0.4 thazz build should be pretty stable as its essentially stock. That being said my wife (who is INCREDIBLY picky on how her phone functions... I've yet to get her to try something not TW-based) has been using Tweaked since before it was even posted and uses her phone as a phone constantly (... lot's of out-of-state sisters that she's always yapping with) and has yet to report an issue. I am unclear why you would be having these issues with the particular specificity you are experiencing... especially if kernels are remaining consistent across TW-based builds anyway. Without me being able to recreate it on my end or a logcat taken during the premature disconnect on your end I'm at a loss. If nothing else, at least you found something that works for you, so I suppose it a could be worse.
Sorry for the troubles.
Not all stock apps or play store apps work with 4.1, I had the same problem when I let my battery app manage my data. It would wait to connect sometimes up to 20-30 secs later after waking to make a call. Check all your apps your using for compatibility, and when you wake your phone give it a sec before calling out. If your in a bad area the alternating of edge/3g/HSDPA+ doesn't help either. I stopped allowing my battery app data control and that solved 90% of my issues, sometimes it still does it but only when I'm in the boonies.
techclan said:
I have the strangest issue. I get disconnected from calls in the middle of conversation if I'm using any of these main custom ROMs.
Blaz3r
CyanogenMod 10
Blaze Tweaked ICS 2.2
But If I'm using a stock ICS ROM or "Android ICS 4.0.4 UVLH5 (Posted by tthaz777)" everything is very stable and no disconnects.
I have full bar with all the ROMs and get perfect data speed and everything else works fine. I'm using the same exact apps on the ROMs as I do on the stock, so I don't think it's related to a particular app. It seems as if TMobile scans the sessions at their network level and disconnects the call because my connection is not providing some information/call data they need. The disconnect can happen as fast as a few seconds or after a 10 minutes or so, just random.
Is anyone else experiencing this ?
I'm currently running below and everything is stable with no drop calls. Just can't figure out why this happens when install any other ROM. and Yes I always to do a full wipe before install.
Android ICS 4.0.4 UVLH5 (Posted by tthaz777) with merwin's scorched-kernel-t769-ics v1.0.29
Click to expand...
Click to collapse
LOL I am using T-Mobile service with this device, so if that's the case for you I would expect a few drops from time to time
On a serious note, drops can happen with full bars for a variety of reasons. Tower is overloaded (signal shows strong but can't connect/gets dropped), person you have called drops you (calling someone in NY that has AT&T? ), bad/faulty sim card (free to get checked and replaced), etc. No cell phone/ROM is drop call immune, even stock (and yes even those people using Verizon). FWIW, I haven't dropped a single call in over a month using Thomas' PA and Tweaked. That's pretty good considering that's including the holidays and I didn't go home this year.
Thanks for the replies guys. What drives me crazy is that I have absolutely no dropped calls when using the stock ICS ROM, but as soon as I load any of the ICS ROMs mentioned the voice call gets disconnected periodically. Same Location, Same Apps, Same Calling Number, nothing changes except the ROM.
I'm fairly technical and good at troubleshooting but not an expert in reading the Android Logcat and don't know what to look for in the log. I have loaded the UVLH5 radio after flashing the the custom ROMs to see if that might be the cause but same thing.... I wondering if I need to try an older Radio...
Like I said all is running great with Android ICS 4.0.4 UVLH5 (by tthaz777) + merwin's scorched-kernel-t769-ics v1.0.29 OC to 1728 but not knowing what's causing the drops is just driving me crazy....
To test I just load the ROM and then call one of the free news numbers (ABC News etc 650-293-9114) and put the phone on speakerphone, and yes I have tried varies other numbers... JUST WEIRD
Try finding an app of the app store to make logging easier like logcat or something. Then run the app and make a call. If it doesnt disconnect, restart the log. When it does disconnect, end the log and copy+paste it here. That is the only real way to find out whats up.
So the problem started again this AM and it's been fine since I flashed Android ICS 4.0.4 UVLH5 (by tthaz777). I hear the hang up tone and calls would just disconnect in the middle of conversation with perfect signal strength. Nothing new was added to the phone, so only way to fix it was to reflash it again from a nan backup.
This is driving me crazy. Attached is a short logcat from right before the call dropped, could one of you experts check it out and tell me if you see anything strange going on....
Thanks
techclan said:
So the problem started again this AM and it's been fine since I flashed Android ICS 4.0.4 UVLH5 (by tthaz777). I hear the hang up tone and calls would just disconnect in the middle of conversation with perfect signal strength. Nothing new was added to the phone, so only way to fix it was to reflash it again from a nan backup.
This is driving me crazy. Attached is a short logcat from right before the call dropped, could one of you experts check it out and tell me if you see anything strange going on....
Thanks
Click to expand...
Click to collapse
any chance you can put that on pastebin instead of a pdf? just post a link to it. It could be helpful to a dev as I see that some info is spread out to different pages and is cut off.
Also did you use an existing sim from a previous phone when getting this phone or did you get a brand new sim? I know various issues arise when using an old sim with this phone. My old sim had issues and wouldn't connect to wifi calling and it was only 10 months old.
anactoraaron said:
any chance you can put that on pastebin instead of a pdf? just post a link to it. It could be helpful to a dev as I see that some info is spread out to different pages and is cut off.
Also did you use an existing sim from a previous phone when getting this phone or did you get a brand new sim? I know various issues arise when using an old sim with this phone. My old sim had issues and wouldn't connect to wifi calling and it was only 10 months old.
Click to expand...
Click to collapse
Here's the pastebin link. Thanks
http://pastebin.com/SCBx2jNS
When I initially had the issue I ordered a new sim hoping it would resolved it and that didn't help, so I flashed ICS 4.0.4 UVLH5 (by tthaz777) which is pretty much the stock with bloatware removed and that resolved the problem and not a single dropped call for a month and it just started again. It's so weird as if Mobile is looking for something in the connection/session and forces a disconnect.
techclan said:
Here's the pastebin link. Thanks
http://pastebin.com/SCBx2jNS
When I initially had the issue I ordered a new sim hoping it would resolved it and that didn't help, so I flashed ICS 4.0.4 UVLH5 (by tthaz777) which is pretty much the stock with bloatware removed and that resolved the problem and not a single dropped call for a month and it just started again. It's so weird as if Mobile is looking for something in the connection/session and forces a disconnect.
Click to expand...
Click to collapse
Ordering a new sim doesn't mean getting a compatible sim. Have you taken the phone to a Tmo store and had someone check it out? They could've sent you another partially compatible sim for it. If I knew more about reading the logs I would love to help you out....

Categories

Resources