Related
Hi!
I'm soooooo damn tired facing thousands of radio issues day in and day out
I'm using radio rom 1.15 and i find it extremely buggy . I looked through the forums and noone seems to be complaining, so i wonder if i'm the jinx here :/
The problems i face are -
1. All of a sudden i cant make calls. It throws a notification popup saying "The call has failed". Thanks! The only way out....restarting the radio. And yea, thats a nightmare too....going to comm manager, switching of phone, and switching it back on....the damn thing doesnt work right AT ALL! I switch it off....and push the button again to turn it back on, nothing happens....i push it again and again and again a million times....it gets too painful. So what do i do instead? soft reset
2. My gprs connectivity goes for a toss every now and then. again, the same ordeal....it never connects until i soft reset or restart the radio.
3. The worst part, when the phone module has taken a crap....i.e....reached a state where no calls go thru (refer problem 1.), i cant even receive incoming calls! The person calling me gets a ringing tone, but my phone's a dead corpse here. All messages sent to me are "apparently delivered" but nothing shows up here....
Is it just me?
Is there a better radio rom?
I restart my phone roughly 5 times a day, once in the morning when i wake up WITHOUT FAIL....and all this is getting to me really bad :-/
San
Well i see you are from Banglore,im from Hyderabad,i have been using the 1.15 radio for ome time now with the pdav latest rom(.09) sometimes my phone acts a little strangely like when receiving a call sometimes the incoming call icon stays there for about 10sec before the screen comes on the call status one.I switched over to radio 1.09 which i found the most stable on my O2 exec,but in my experience radio roms also behave differently depending on location,and also the os system try to use 1.09 as i found it the best for me in India.
Radio versions works differently depending on your location.
Try other radio versions.
Or better yet, just use the radio version that came with your device.
Do not upgrade your radio unless your having problems with it.
Like our friend here at xda-developers said, "If it's not broken, don't fix it."
arvind09 said:
Well i see you are from Banglore,im from Hyderabad,i have been using the 1.15 radio for ome time now with the pdav latest rom(.09) sometimes my phone acts a little strangely like when receiving a call sometimes the incoming call icon stays there for about 10sec before the screen comes on the call status one.I switched over to radio 1.09 which i found the most stable on my O2 exec,but in my experience radio roms also behave differently depending on location,and also the os system try to use 1.09 as i found it the best for me in India.
Click to expand...
Click to collapse
well, i've reverted back to 1.09, lets see if its any better!
i feel sooo sick sometimes, i think of buying another normal phone! But hell, i love my universal so much that i cant do it....i'd rather put up with all the $hit it throws at me... !
cheers, and thanks for ur help everyone! i'll post back and let u knw if its still coughing up!
San
Radio Rom?
If you are still having issues, also post back your OS Rom that you are running, this may also have some bearing on the underlying issues.
Cheers,
Beast
Using radio 1.15:
With Ivan's base it causes my device to experience problems with the phone and GPRS\3G
With Midget's base everything seems to work fine
(btw I have an O2 Exec - Just suggesting that it may be the differences in hardware...)
dreamtheater39:
Same problem here.... Since I (sim) unlocked my MDA-Pro I'm experiencing EXACTLY the same problems as you have.
I posted several items on this forum, no success till now.
I'm thinking of reassembeling my old MDA-Pro, which is sim locked but screen broken. replacing the screen with my new (sim) unlocked MDA-Pro and see if the radio problem is still there. Just to exclude if the problem can be (sim) unlocking the phone...
But it is VERY anoying, I must agree...
regards
arjan
Also,.. I've tried almoast every Radio rom!! still no success.. even te Original T-Mobile rom (ROm and radio) give me problems...
So can it be the Sim unlocking (V1 by Buzzdev)?
A.
adonker said:
Also,.. I've tried almoast every Radio rom!! still no success.. even te Original T-Mobile rom (ROm and radio) give me problems...
So can it be the Sim unlocking (V1 by Buzzdev)?
A.
Click to expand...
Click to collapse
Hi,
I doubt it is the SIm unlock.
I used Buzz's too, originally many Rom flashes past that.
I have Exec with Radio 15 and customised Rom with Midgets as base and no issues at all.
I would advise finding out what the latest Radio Ver offered by Manufac for your model and try that one for a bit.
Perhaps we should start a poll as to what each user is using and record Radio and OS Rom info with a comments section for any issues noted. It would at least help stablise WM6 builds.
Regards,
Beast
That damn radio issue!
I think it is time to stop discussing whether there is an issue and start looking for a fix!
First off: basically all HTC-phones have had a similar probblem, going back to the MDA 2. The key problem has been, that the data connection does not properly switch between mobile cells when you are on the move.
My device loses data connection every time I go into the parking garage, where there is no reception. Also, when I'm sitting in an area with very poor UMTS-coverage, the MDA-PRO loses connection after a few successful switches to GPRS. BTW: You can see you have a problem when Active Sync on the MDA says "Waiting for Network".
This wasn't such an issue as long as we didn't have the data connection constantly on. But, latest with the MS-Pushmail this has changed - the data connection is always on.
HTC and the operators have seemingly been working on this issue for quite some time. The only ROM on the MDA-PRO that was quite stable on this was actually the last T-Mobile WM-5 ROM.
With WM6 we are back to the issue. I no longer believe it is a problem with the Radio-ROM. Most likely is that there are differences in the driver dll. THis might explain why Midget's ROM seems to be better than IVAN's.
So, guys start troubleshooting!
Yes dreamtheater, are you running WM6? It is WM6 that seems to display these problems, regardless of the Radio. If I roll back to the official T-Mobile Rom (WM5) or Orange Rom (WM5) my problems disappear
HA!
Finally some usefull information. But very strange, buying a very expensive devise, but not being able to make a proper phonecall with it....
a.
YIPPEEEEEEEEEEEEEEEE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I installed Radio 1.09 and so far sooooooooooo good!!!! None of the issues i mentioned, it works like a charm!!!
The only noticable issue i've found a couple times is, the gprs automatically disconnects once in a while, but i can ask it to reconnect and it does so without a fuss! Wowwwweeee!!!!
A BIGGG thanks to Arvind09 for this!!!!
So guys, i guess you got to try all radio roms and find which one works best for you, no other go as i see it
Cheers!
San
OH CRAP!!!!!!!!! I SPOKE TOOOOO SOON
Woke up early morning and the damn things crapped again :-/
The sobbing continues
If you tried different Radio Version and still does not work, it is time you change a service provider, provided you are sure that your hardware never had problems before.
Bangalore is a big city, coverage should be good, could it be the part of area you are in has bad coverage, try asking you friends about service provider other than your current one in that particular area.
If changing provider still does not work, make a complaint to the providers, it nothing improves, its time you need to move somewhere else.
I have the same issue when I keep the Radio Band in Auto mode (GSM/3G) I change my phone to GSM and it is better.
Ye, I did the same too. only switch manually to 3G when needed. I almost forgot about this point.
Furthermore, GSM mode makes the battery last more days than 3G mode.
encountered the same probs, 4 me radio 1.12 is the most stable one (I believe it's an exotic/not commonly used version)
I have been struggeling with this since the first WM6 Pre-release ROM came out on this forum. Tried all the radio ROMs available, without succes. As said, the only ROM that does not suffer from this, is the latest WM5 ROM.
dreamtheater39 said:
OH CRAP!!!!!!!!! I SPOKE TOOOOO SOON
Woke up early morning and the damn things crapped again :-/
The sobbing continues
Click to expand...
Click to collapse
Ok could you tell me which provider are subscribed to? I use Airtel and hutch on both my pocket pc(universal and orbit)Ive noticed that airtel tends to loose its signal whereas hutch has never given me a problem.for this reason i use hutch on the Uni,though i cannot say that im very happy with their service,they are any day much better tha Airtel and Idea both.Also try to change the rom and see if the problem still persists.
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.
Hello all!
I am a noob on here so if this has been asked or brought up before please forgive me. I couldn't find any info on this issue. After installing 2.3.4 on my sensation (I am running stock out of the box) I notice when I connect the phone to wifi and use wifi calling that when I use the speaker phone on my phone, the person on the other end can no longer hear me. The person just says hello over and over and totally cuts off the mic on my phone. When I enter it back to the regular headset, it continues to be cut off. When I try troubleshooting the issue I connected to the t mobile network it works just fine. Only when I use the wifi calling feature does this happen. Does this happen to anyone else? Is this a known bug? I did a battery pull and this did not fix the problem. Any suggestion or feed back would be much appreciated. Thank you everyone!
Not one person is having this issue? Can anyone help out there? At least let me know if it is a known issue. I know the speaker phone is terrible but I'm only trying to find out if there is a fix for this.
Thanks!
HTC Sensation Speakerphone does not work on WIFI
I am having the same issue. Speakerphone does not work over Wifi. Person on the other end cannot hear me and I often cannot hear them. When I am not using Wifi, speakerphone works fine. Version 2.3.4 seemed to improve speakerphone volume, but it still does not work over Wifi. I contacted HTC tech support and they said while they were unaware of the problem, but it is possible that it exists. They said they would investigate. We will see. Not sure whether the HTC Amaze has the same problem.
I had the same issue till I S-offed and flashed a new ROM. I think it's something with TMO's factory ROM they have the speaker function turned way down and my first Sensation would do just what urs is.
Rec: Unlock (S-off) and flash a new ROM (I personally am running CoreDroid 2.4)
I'm on ARHD 3.6.2 and non speaker phone works ok, but on speaker I've been told its hard to hear.
I am also having a same issue. I've opened up a ticket with t-mobile. T-mobile techs are looking into this issue. Yesterday I went to the store from which I purchased my sensations and showed them the issue. We tested the issue with other HTC android devices but only sensation is having this Issue.
I noticed this problem a couple months ago, and am surprised there hasn't been a software update to fix it. In the meantime, I just shut off wifi if I expect to make a phone call using the speaker phone, which is somewhat annoying.
I have a HTC sensation (non branded european version) for about 5 months now, and lately its been crashing constantly, it just goes black and is completely turned off.
Most of the time this happens when its in my pocket.
I'm running the original rom, its not rooted, and i did a factory reset last week.
The problem was gone for a couple of days, but its back again.
I assume its an app that's causing it to crash, but i can't figure out what app.
I'm not sure because it seems that everytime it crashes and i restart it, a program that uses the internet has an update. For example whatsapp, twitter, wordfeud etc.
I tried disabeling wifi, that didn't help. I disabled the mobile network now to see if its internet related, but its not an option to keep that disabled ofcourse.
I removed a couple of apps, but that didn't solve the problem.
Hope someone can help.
If a phone reboots...its typically software related
If it shuts all the way off...its usually battery related.
Call HTC about them sending a replacement battery. Tell them Tmobile told you to call them and you need it for troubleshooting testing.
Sent from my HTC Sensation Z710e using xda premium
I can't help, however can report that I have similar issues.
Though I get crashes as well during normal operation such as:
- getting a phone call
- opening up Google Maps (or any GPS app)
- receiving SMS messages
- starting the camera
And all with stock software.
I have a same problem. I cant figure it out. When i turn on my phone battery is around %6 . but normally its around %70. When i restart again it turns normal %70. is it same on your device ?
thnx for the replies! I indeed have weird and incorrect readouts from the battery after restarting, and it doesn´t crash when on the charger.
I realy hope its the battery, i´l call HTC right away to see if they can send me a replacement battery.
Having similar issue
MrSkyline said:
thnx for the replies! I indeed have weird and incorrect readouts from the battery after restarting, and it doesn´t crash when on the charger.
I realy hope its the battery, i´l call HTC right away to see if they can send me a replacement battery.
Click to expand...
Click to collapse
Hey... I am facing exactly the same issue. Replacing the battery fixed it or not?
Same here. I also noticed that if I changed my wallpaper, it reverts back to the default phase beam wallpaper on the next boot.
Updating to this firmware
DOWNLOAD 3.32.531.14 710RD (TMO ONLY [THX GROGG88]): http://goo.gl/JCWEO
MD5: 79EDF95337826DF73083E227DB8DE7C3 from http://forum.xda-developers.com/showthread.php?t=1459767 seemed to fix it for me.
It probably shouldn't have, because the firmware is supposed to be the same as previous except for the radio.
Maybe it'll work for you guys.
Had the same problem, it shutsdown when receiving phone calls.... Like the previous post said it must be battery problem.. i did this fix and my phone has not shut down randomly.. this fix will tighten the battery contact with the terminals...try it first, Its a simple fix
http://forum.xda-developers.com/showthread.php?t=1622683
Sent from my HTC Sensation using Tapatalk
Had this same problem on stock sensation . Once I rooted and installed custom rom the problem went Away! Never to return.
I truly believe and its been proven that custom Roms are MORE stable than stock. After installation of the custom rom , the issue of restarting NEVER RETURNED! Not a problem anymore . It's a software issue. It can be fixed with different software . It's a known issue.
Sent from my HTC Sensation 4G using xda premium
realsis said:
Had this same problem on stock sensation . Once I rooted and installed custom rom the problem went Away! Never to return.
I truly believe and its been proven that custom Roms are MORE stable than stock. After installation of the custom rom , the issue of restarting NEVER RETURNED! Not a problem anymore . It's a software issue. It can be fixed with different software . It's a known issue.
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
I rooted since warrenty is over, I had the problem on stock rom, hungarian t mobile one, and now the problem starts to come back on a custom rom also, but not form the first day, it must be something related to software... i have two batteries and it did not fix the issue, i dont think the battery is the problem, one is original the other (i mostly use) is an anker battery... quite cool since longer standby...
how can i debug and read logs or dumps about the error?
scenarios when my phone shuts off:
- receiving a call after ringing once or twice (not always)
- during talking on the phone
- when i call someone after ringing once or twice (not always)
- starting camera and using it to make a picture in the moment of flash
- sometimes just when its in my pocket, later i pick it out and wonder its again turned off: D´OH!
most stable workaround which lasts usually half a day (remove battery)
have you any ideas how I can read dumps or logs?
thanks
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....