Related
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.
I know this is probably something that can't be fixed without working with T-Mobile, but they can't seem to figure out what the problem is and I'm getting desperate
Whenever someone sends me a text I get duplicates of it over and over until I turn on WiFi calling, which seems to work fine. I have had this problem with two different G2x (I sent the first one back thinking it was a hardware issue). This also does not happen on my Nexus One (I moved the SIM card back over and the issue disappears).
I am thinking it has to be something to do with the communication between the G2x and my T-Mobile cell network. Any information anyone has about this that could help me help T-Mobile find the issue would be great.
Thanks.
You don't have another messaging app installed, do you?
First thing I did when I got the replacement was sync Google contacts and tell someone to text me and it started happening. I factory reset the original one I had 3 times and the problem persisted.
Are you running juicedefender? I get duplicates of some messages because juicedefender shuts off mobile data, so the network doesn't receive the notification that the MMS was received. It will try and resend every 5 minutes for a specified number of times until the message is received.
Nope, had no apps installed. Plus I get the duplicates sometimes less than 1 minute apart.
Thanks for the responses so far. This problem is really starting to get irritating.
I was getting a lot of duplicates. Seems to have spied for now. No clue what was doing it
Its really irritating because I love the phone, but I can't use it if I am constantly getting spammed by duplicate text messages.
yea i got 55 texts from 12 am to 11 a m from the same person 2 different texts and it kept going for a couple hours after too idk why i just got a new one today though but it's got a bad bleed so im just returning it and going to wait a week or two hope they solve it by then already sent lg a pic so
If your problems anything like mine a replacement won't fix the problem, unless I somehow got stupendously unlucky.
Anyone figure this out. I have the same problem. It is not every text message and not every person. It is pretty random. The same person can send me 4 texts 2 are normal, one repeated twice and one 24 times over a period of time, usually a couple hours.
Check any of the apps/widgets that have anything to do with calls/texts, even just showing a number of unread texts. If there are any that have the permission "Your Messages: Send SMS-received broadcast" uninstall it and see if the problem persists. I think I may have had an app called Organizer Widget that was blocking my phone from sending that broadcast.
I had your problem.
I was running on stock G2X, and I was receiving text after text after text.
I spent time on the phone with the T-Mo reps, and he concluded that:
"it's a server problem. You see, our messaging database isn't reading that your phone got the text, and thus it re-sends it in hopes that it receives it."
Basically, he is saying that the messaging server is tripping. But, this is not exactly true, because if it was the messaging server, then it would be universal. It is simply a G2X stock-rom problem.
I think it actually might have something to do with the baseband, but I am not sure if CyanogenMod updates it or fixes it when flashing.
I have a fix.
After I flashed myself some CyanogenMod, the problem was instantly fixed.
So, I think its a problem with the stock rom. Definitely. The CM rom works perfectly, no repeating messages. Also, the current nightlies are mighty stable.
I have this issue as well. It doesn't happen often but when it does it sends 10 or more duplicates.
I have handcrafted sms and launcher products which displays the number of texts on the dock. Running rooted stock.
It hasn't happened in a while, so I doubt it is related to the Apps.
Sent from my T3 Motion GT3 (look it up)
I've had this issue on ALLLL my android phones I've owned . Even non Android phones and my unlocked iPhone. I have tried different similar cards as well.
I have noticed it happens the most when I receive messages from a Verizon user; followed by AT&T users. I never (not that I've noticed) had duplicates from Sprint or other T-Mobile users. Only Verizon and AT&T.
My point being I think it's a T-Mobile issue. Or a communication issue between providers.
Sent from my LG-P999 using XDA Premium App
JRudnik said:
I had your problem.
I was running on stock G2X, and I was receiving text after text after text.
I spent time on the phone with the T-Mo reps, and he concluded that:
"it's a server problem. You see, our messaging database isn't reading that your phone got the text, and thus it re-sends it in hopes that it receives it."
Basically, he is saying that the messaging server is tripping. But, this is not exactly true, because if it was the messaging server, then it would be universal. It is simply a G2X stock-rom problem.
I think it actually might have something to do with the baseband, but I am not sure if CyanogenMod updates it or fixes it when flashing.
I have a fix.
After I flashed myself some CyanogenMod, the problem was instantly fixed.
So, I think its a problem with the stock rom. Definitely. The CM rom works perfectly, no repeating messages. Also, the current nightlies are mighty stable.
Click to expand...
Click to collapse
I'm actually having this problem running CM7 Nightly 63, it's irritating as hell.
Dont know, but I'd like to know the problem too. I have chompsms installed but it shows duplicate in the stock messaging app too.
I really don't think it has anything to do with the phone...
Like I said earlier, all my phones have done it. Even my crappy clamshell Samsung back in the day. Or my unlocked iPhone.
Server makes the best sense.
Sent from my LG-P999 using XDA Premium App
I have the issue as well...although it seems to be only with certain contacts, however across every carrier. Averages 3-4 duplicates. Never had this problem before with any phone. SIM card went straight from my N1 to my G2X. Kind of an old SIM. Maybe I'll try a re-provision on a new SIM to see if that makes any difference.
Thank you @shaneledford, uninstalling organizer widget solved my problem... everything's back to normal
Sent from my LG-P999 using XDA Premium App
I've also had this problem with previous phones, though it tends to happen much more often when one of them is an Android phone. Only started happening with my phone before this one, though, but that was a Nokia non Android, so it's a fairly recent thing but not Android specific.
Sent from my LG-P999 using XDA App
I rooted and have been running CM7 for months never had a problem. Earlier today I started having trouble sending texts so I updated from Nightly 71 to nightly 75 thinking I stumbled into a nightly bug (which happens often) and this did not fix the problem. So I went to an old nandorid backup from 7-18-2011 and restored because that particular backup has always worked perfect for me. Still this did not fix my problem.
Then I got my big boy shoes on and downloaded Heimdall and a stock image of Froyo 2.2 for my Captivate. I followed the directions and downloads from here.
This did not fix my problem. I am currently running a 100% stock version of the phone now so I cant possibly think of any other way to fix this problem other than taking it up to AT&T and asking them if there is any way to have it sent out or to receive a new phone. As I think there might be a problem with the radio inside the phone.
I can still send texts on and off but I can not use data. My mother has an SGS Captivate running stock Eclair 2.1 (never been rooted or flashed) and she has FULL bars while I alternate between 1 and none. What gives??
Have you tried a different sim card?
UPDATE: All the sudden my mothers phone and my friends phone (AT&T Iphone) are reporting the same type of service issues. Maybe it was a service outtage in my area and my phone just saw it first? This is getting stranger.
Seems like AT&T issue, just wait 1 or 2 days and see if everything goes fine.
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
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....