Att service, but never had this many Droped calls. 6 years and this the only phone i've had this many Droped calls., now the question is, is it a device problem or user error. And is anyone else having issues? I've basically tried everything I belive, full wipes, different roms, and radios and rils... Any thoughts would bee much appreciated. Sand sorry if there's a thread at Work didn't have time to search.
Sent from my Inspire 4G
I had the same problem but when I switched radios it was fine. Might be a hardware problem.
Sent from my Inspire 4G using XDA App
I had some problems when I was running coredroid v8.1 with the recommended radio, switched to the most up to date radio, 4.21 and matching RIL and have been fine since. I by no means saying CD v8.1 was the cause, just that radio wasn't working in my area. Since then I've been using the same radio with BinDroid and it has been amazing in terms of data speed, GPS, and phone calls. When switching radios/rils, give it time for everything to settle..I know when I made the switch to the new radio, it took about 18 hours or so and then all of sudden calls were fine.
Edit: No scientifically proven that 18 hours was the exact time, but its about that time frame...changed radios..made some calls, phone dropped I think like 2 of the 6 calls I made...got mad, went to bed..woke up and made some calls and everything was working nicely..no dropped calls!
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.
Hi guys,
Right, so I've noticed that when making calls with the Sensation, if they are reaching the 10 minute mark, for absolutely no reason whatsoever the line will just go silent, before the call is dropped. The signal bar doesn't even change.
Has anyone else had this issue?
Cheers,
James
My phone also has dropped calls randomly but on random times I'm sure. Today it did it as well. I don't know why though. I hope to God its not a fault in the phone that can't be fixed with an update. I'd hate switching to s-on and stock recovery.
Sent from my HTC Sensation 4G using XDA App
random call dropping
Hi,
A complete n00b when it comes to Android and first post on this forum. Kindly excuse any inadvertant mistakes.
Thanks to the wonderful forum we have here, I managed to root and get the IC 2.5.3 ROM on my Sensation. And its working like a dream except for one small problem. Big problem really.
Calls keeps dropping, and there have been occassions where I was getting disconnected every 10 seconds. Patterns I noticed :-
1. Voice suddently drops. The call is still on and in about 3-5 seconds call gets disconnected.
2. This happens only in a wi-fi zone (mostly at home). When I am in a wi-fi off zone, this has never happened.
3. This was happening even BEFORE I flashed the custom ROM, (was hoping that the problem would be resolved), but no luck)
4. I suspect its because of an incompatible radio image in my country (India), but what do I know. Could a 4G enabled handset encounter such problems on a 3G network?
5. How can I get to know the best/most compatible radio image for my ROM . ( I searched, but nothing conclusive so far anywhere. I am not able to post in the developer thread because I am newbie )
Please help.
HTC Sensation
Insertcoin rom 2.5.3
Bricked kernel 1.5ghz
Anyone have any idea what the issue is or when the crashing after every call and general instability will be fixed? SMS works beautifully but calling is spotty at best, even from ROMa like ARHD that claim to have working WiFi calling.
I fugure we will have to wait until an ICS TMOUS phone is released or the sensation is updated to ICSvon TMOUS.
I made a thread about this a few weeks ago and never got an answer. basically it's tmobile and the app itself that needs to be fixed, and there isn't a single ICS rom that it works on, I don't care what the rom chef says. For me I just turn it off immediately when I flash a new rom as it has never once worked for me during a call.
You have to wait until T-Mobile releases their ics update for the sensation.
Sent from my HTC Sensation Z710e using Tapatalk
I could be wrong but I have a feeling that the problem is caused by one of two reasons. One being that the app it self is really not fully compatible with ICS yet. Or, and I feel this is the more likely the reason, the kernel has been changed for ICS causing the WiFi calling app to not be able to function properly, meaning the kernel has to be reworked. I feel like this and maybe a couple of other kernel issues is why TMOUS has not started pushing out the OTA yet.
I am running arhd and wifi calling works like a charm. So its hit or miss.
Sent from my HTC Sensation 4G using XDA App
Skipjacks said:
I am running arhd and wifi calling works like a charm. So its hit or miss.
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
+1, arhd, and my WiFi calling works. I rarely use it though .
Sent from my HTC Sensation 4G using Tapatalk
I am on ARHD as well with no joy. I mean, occasionally I can get a call out on my Bluetooth, and my phone always rings, but usually won't go any further... multiple WiFi access points tested at various places. SMS and MMS are flawless, so I have been tolerating it.
In any case, I find it hard to believe it is working 100% for anyone yet.
Question for those who say it is working... after you end a call does the WiFi calling icon disappear for 20 seconds or so, then come back? Or after making a call the second one will hang with a green icon, then disappear and reappear again? If so, those are signs that the application is crashing and being restarted.
And if those aren't happening and WiFi calling is truly working, please post what WiFi router and internet provider you are using...
WiFi calling has multiple ways of getting out to the internet, some of which are kind of clever... to the point where it will work on most Aruba WiFi systems that use a captive portal...
At the college I work at, the Aruba technician doing an upgrade on our devices had to spend a good 30 minutes figuring out how it was bypassing the captive portal so he could block it.
Good luck finding somebody who will answer you with this, I tried in my own thread and never got a satisfactory answer. There are a few people as you see in this thread who claim it works great but I've never seen anybody explain exactly what their specific setup is. I'd like to know if it has anything to do with the router and/or type of wifi network you are on, the rom, the kernel....so many different variables. I'm like you, I just don't see how it could work 100% for somebody if so many others do NOT have working wifi calling.
kingston73 said:
I just don't see how it could work 100% for somebody if so many others do NOT have working wifi calling.
Click to expand...
Click to collapse
Because annoying things like that happen. Gps is funky for me on all cyanogen builds, but works perfectly for everyone else, for example. Only works once per boot up. Freaky...but im the only one.
The fact is the updated version of the apk isnt out yet for wifi calling. So you have to be patient. Those of us who have it working might just be lucky. It happens.
Sent from my HTC Sensation 4G using XDA App
Works for text and mms
Calls fail and app drops out for me
in us running ptd local ISP and a linksys wrt54g router
Has anyone found a ics build with sense that works with wifi calling?
The major issue is kineto_gan.ko a module in /system/lib/module
It is one of the main files needed to run WiFi Calling. The problem is it is Gingerbread base and kind of like when you port items from one sense to another it doesn't play so well.
The secondary issue is there isn't anything on TMO with ICS yet until the One S comes out and with a lot of more recent phones TMOUS patches in the WiFi calling at a later time so we can't really extract it from there either (yet).
Then brings in the issue of WiFi encryption, setups, and so on that mess with the way the call is carried through the network to properly register to TMO.
So it is like others have said. Some people will have good luck some wont. At home mine gets texts just fine but calls I can't rely on it and won't until Tmobile gets us a version we can use.
Yeah I think even when the one s comes out even though won't be helpful either. That will probably have the newer IMS wifi calling like the amaze does and not be compatible because that is more reliant on hardware supposedly and if nothing else needs a newer sim.
May need to wait till there is a offical rom update relased from T-Mobile.
I haven't had reliable wifi calling in any ROM in at least the last 6 months. Would work fine and then crash, requiring a reboot to fix only to repeat the process. Sometimes that crash took 2 minutes and sometimes 30.
With the ICS builds I've been trying it's always closer to 2 minutes but text works fine. It's been rough since I rely on the wifi calling because of the weak signal when I'm at home. I'm expecting it will be much more reliable when T-Mobile releases the official Sensation build which they sent back to HTC,... because of the wifi problem from what I've heard.
Lucky I found this thread (thank you Google), I thought i was having a bad time with calls dying after 5 minutes or so, but from what I hear from you guys, guess I've got it good (just gotta make sure I'm not on wifi calling during an important call). Although, i really wished it worked well for voice calls as I'm always within different buildings and no guarantee of signal in there (same for my apartment). SMS & MMS work fine though
I'm running latest ARHD (ICS) btw. Although some of this problem might be due to the devices themselves different config, etc.
I'm using Virtuous Inquisition v4.0.1 and WiFi calling works perfectly fine with fast connection. It didn't work so well for me on ARHD
It's hit or miss. Not much in between. Stick with gb if you want WiFi calling to work. That's what I have to do. People on here act like you're crazy to want WiFi callinh to work.
Hi. I was using my Sensation last night, went to bed and woke up the next day only to find that my 4G connection wasn't working! The signal bars were white and the icon (currently an H) is flashing. What does this mean? How can I fix it? I can only use Wifi at the moment, and I DO NOT pay an extra $10/mo to deal with this! How can I fix this? I've checked my data settings, rebooted my phone, scanned fir viruses, but can't figure it out!
Sent from my HTC Sensation using XDA
611
I don't follow you.
ClipTy said:
I don't follow you.
Click to expand...
Click to collapse
They are referring to the number you call for T-Mobile US costumer service.
At my house edge goes is and out..flashing E.. tmo must either know or are working on it
mulletcutter said:
At my house edge goes is and out..flashing E.. tmo must either know or are working on it
Click to expand...
Click to collapse
this happened to me the other day, even in 3G/4G mode my data would never connect and E would just keep flashing over and over again (in like 10 sec. intervals) thought it was a ROM problem so I restored a backup and sure enough, the problem was still happening. I could still make calls and send texts fine tho. its not happening to me anymore, but I found it weird. could it possibly be T-Mobile messing with their towers or something in preparation for LTE?
Well, I'm not sure what caused this very same issue for me a couple days ago. I can say that it ONLY effected my AOSP (CM9) rom, but my Sense rom was unphased. It seems to be a common recent complaint in the OpenSensation thread...
I've since then done a fresh install of CM9 RC1 with the addition of Tamcore's kernel. Although I'm not experiencing the described symptom any longer, I can say that my data speeds are far from exceptional. I'm not sure what is going on, but it does seem to be carrier related.
I experienced the same 1 day after flashing CM9 RC1. I re-flashed the Virtuous Inq. ROM I was using previously and the problem went away
My phone went back to normal later on. I think you were right mulletcutter, they might have been servicing it.
Sent from my HTC Sensation using xda app-developers app
Same data connectivity issue
I have two sensations, both shows similar data connectivity issue on TMobile. Data signal jump to connected and not connected for couple hours, and eventually problem will go away. I have both phones rooted running either CM9 or Kang. So far I have tried couple following things but no solutions. I believe its HTC Sensation hardware issue:
1. Flickering so far seen usually after night long charge in the morning. It will last couple hours, some time days.
2. Changing/reflashing ROMs did not help at all and saw same issue continued.
3. One of my friend has Sensation and he also has seen same issue.
4. Some time going into Phone application(Dialer) and then Settings/Advance settings and come back without doing anything helps but not always.
Please post here is you have temporary/permanent solution or even know the root cause of this data connectivity issue.
Also thinking to call Tmobile to get some kind of help but not expecting much as I bought phones more than year ago but less than 2 years. I don't want to give any more commitment/agreement with Tmobile as planning to move to value plans to save some money. If Tmobile does not help, thinking to try American Express to conver it under extentended warranty as I paid by AMEX credit card.
Thanks
Have you tried the application get ril? I was having some issues myself, I'm also T-Mobile. I tried get ril and found out my radio and ril we're not matching. The application suggested a ril for download and once I did that I went from one bar of connection to five bars of connection on H. It made a big difference for me. Perhaps it could also help you? You can download get ril from the market. It sure won't hurt to try. Best of luck.
Sent from my HTC Sensation using xda premium
Its a defect in the basic aosp framework. There is nothing you can do to fix it. There is also nothing your usage did to start it.
The good news is that it should disappear on its on after a few hours.
Check my threads started history. You will find a thread near the top of that list showing almost all there is to know about this issue. I think my thread might be linked in the first 2 posts of the cm10 faq thread too.
Sent from my HTC Sensation using xda app-developers app
Hi, I'm a noob with half an idea of what I'm doing. Please excuse any stupidity (I was born with it and am learning to develop it everyday)
I have a problem that I think is probably for [RADIO][LATEST: 26.16.04.09] The HTC Desire HD Radio Thread----- but because I'm new, I can't post there.
I'll try and give you what I think is the the most relevant information
I have a 2 year old HTC Desire HD still running on the UK Orange network.
I have successfully flashed probably more than 10 roms over that period (to try out different features).
About 7 weeks ago (stupidly) flashed a new radio.
It seemed to go well and my phone is correctly reporting the new
"Baseband Version 12.69a.60.29U_26.17.14.11_M"
I'm currently running Android 4.2.2
Kernel 3.0.78_JellyTime_42_R9-g35b611d
which I like but ...
ever since I flashed my radio my reception has been awful
I hardly ever use data when I'm out (I tend to be in places where I can use wifi)
so usually my data is turned off.
I just want to receive calls or texts but most of the time my phone shows no signal bars and callers can't get through (no texts either).
My texts seem to come through if I switch to airplane mode then switch back to normal.
Unfortunately its not totally consistent but most of the time, through the day, my phone (which I was probably successfully using earlier) just decides to lose any signal and then not "reconnect" to a mast unless I force it (through airplane off then on).
I have subsequently tried a few different Roms (without re-flashing the Radio) but the problem is the same whichever Rom I use.
I've read lots and lots and the Radio I'm using seems to be well liked but I'm guessing that for some reason it doesn't like my phone. I'm thinking I need to go back to a different radio but I don' t know which one and before someone tells me to go back to the previous one (before my problem) I've tried so many different things I can't remember what Radio and Rom I last had that worked successfully (I told you I was stupid).
The battery now drains very quickly, only lasts a quarter as long as it did 2 months ago. I believe (but could be wrong) that is because my phone is constantly trying to register with a mast but is getting no signal.
I want my phone to be reliable, I don't need the latest "bells & whistles" ie I don't want to be trying out someone's newest "nightly" with a whole lot of features not yet working.
I appreciate you guys have put in so much effort and know so much more than me.
I hope I haven't bored you but that I've included enough info to help your diagnosis.
Last bit of info, I notice that on a lot of roms, the camera seems to be one of the features that regularly "doesn't work yet". The camera is one of the features I use the most (it's important to me).
What should I do?
All help gratefully received... Thanks in anticipation
Hey, I flashed my stock HTC Desire HD with CM 10.1 eventually - had to spend lots of time figuring out how to get S-OFF and I'm sure in that process the radio image got reflashed with another which causes the same symptoms you describe - excessive battery use, phone hot at the radio module, not getting constant signal, etc. Now I'm also rather concerned because I wouldn't want to brick the device by flashing a bad radio image...
If you've figured anything out, let me know, I'll be stuck reading...