Database Info

[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.

[Q] Nexus S changes to speaker phone on recieving call

So I just got a Nexus S 4g on Monday and my dad and I already rooted the phone and have been trying different roms. He actually rooted it and swapped out the stock rom before I even knew I was getting it.
So with both of the roms I have tried, whenever i recieve an incoming call the speakerphone automatically activates and I have to manually turn it off.
We already tried reflashing the rom and we have also tried replacing a lib***.so file (forget which one) and neither fixed the problem. I cant find any sort of setting for this.
Anyone else having this problem? Is there a fix available that someone can guide me? Very new to Android so I'm still learning the tricks of flashing etc.

Just curious...did you test the phone before it was rooted.
Sent from my PC36100 using XDA Premium App

I received the phone on monday evening and my dad had the phone all day and routed it etc.
I never handled the phone with the stock rom. Its not too big a deal since I don't use it for much calling but a fix would be greatly appreciated.
Sent from my Nexus S 4G using XDA App

webhead1994 said:
I received the phone on monday evening and my dad had the phone all day and routed it etc.
I never handled the phone with the stock rom. Its not too big a deal since I don't use it for much calling but a fix would be greatly appreciated.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Well it seems like you don't know if this problem has always existed or if it is a result of flashing a custom rom. Best bet would be go back to completely stock and see if you still have the problem.
Sent from my PC36100 using XDA Premium App

Just flashed the new miui rom and it fixed the problem. Now I just have to redo my launcher lol.
Sent from my Nexus S 4G using XDA App

I'm having the same problem running a stock version of Android.

I started to have the same problem few days ago and my phone is all original stock, ,,

my wife just started experiencing this today. completely stock nexus s. we may try uninstalling the last few apps that had updates and see if we can trace it to one of those.
edit: are any of u using go sms (specifically version 3.66)? other users are complaining that recent update is causing this issue. im sending my wife a backed up version i have of 3.65 to see if its resolved
edit 2: rolling back to 3.65 did not resolve the issue, but rolling back to 3.64 did. good thing i have appmonster pro.....

I just started to have this problem today too. I did try to activate GoogleVoice yesterday but the calling issue did not begin until today. Running MATR1X v.6 and CM7 nightly #83. Didn't have this problem during stock.

Go sms's latest update is the culprit. The August 29 th update is responsible. Just uninstall that and put some other sms app.
Should solve it, It fixed my phone.

it happened to me twice yesterday, I answer the phone the screen went black and the sound routed to the speaker..can't go back to turn it off during the call as the screen has nothing. (stock rooted)...will uninstall GoSMSPro and see how it goes

If anyone needs/wants the 3.64 version of GO SMS, dm me you're email addy. (i'm assuming this would be ok on XDA since the app is FREE in the market?)

They (GoSMS) just released an update 3.66 to fix the problem

vennstrom said:
They (GoSMS) just released an update 3.66 to fix the problem
Click to expand...
Click to collapse
Its still exists on 3.66. My wife was using this version and it had the problem. We had to roll back to 3.64 before it went away.

u were right, Go SMS was the issue, they released an update today and solved the problem!
cheers everyone!

Glad I saw this thread... my G2 started doing this after not changing the ROM in months, at least now I know what caused it. I got my Nexus S yesterday and haven't answered any calls without the headset yet, lol, so I thought it was just my G2.

[Q] Connectivity problem, all roms?

Been using custom roms on my Inspire 4g since about March with no serious issues till this week. Sometime around wednesday, my connection to my google account, the connection to talk, market, gmail, etc. Seems to be dropping out and locking up my 4g connection for a minute or two. This is really annoying. I have tried numerous different radio and rom combinations as well as going to the store and getting a new phone. The only thing that keeps it up and running is if I roll back to stock. Any help would be greatly appreciated.
Have recently tested Absolution, CM7, Android Revolution, and TalonRom with recommended radios per developer instruction to no avail. But am up and running fine with roll back to att gingerbread update via hack kit...
Any suggestions?

I was experiencing loss of background data on both my inspire and my atrix with stock gingerbread, until just recently. The only conclusion I came to was that ATT had a problem, at least in my area, with background data staying connected on 4G phones running gingerbread, except on wifi. About a week and a half ago, I noticed that the problem had mysteriously resolved itself, and I was having no more issues with push to email and other apps. I can only assume it was something they fixed with a network solution. Perhaps this fix has caused a problem with the roms you're using. I know that numerous calls to customer service failed to produce an answer for my issues, it seemed either no one could figure it out, or it was a known issue that they weren't acknowledging.
Sent from my Desire HD using XDA App

Yes, similar to me. Thanks for the reply. I'll give a Rom a try over the weekend and see if the problem has rectified itself.
Sent from my Desire HD using xda premium

[Q] Cannot send MMS when connected to WiFi

I switched to this Motorola RAZR HD from my GS3 about 2 months ago. I love the phone. Battery life is awesome, and the phone is lightning fast.
However, in the past week or two, I found that I cannot send MMS messages when connected to WiFi. When I turn off WiFi manually, I can then send MMS no problem.
I do recall doing an OTA update about 10 days ago, which is right around the time my problem started, but I'm not 100% sure that this started exactly after the OTA update. I've also been noticing since the OTA update my phone has been a bit laggy. My phone used to be lightning fast, but now its acting like my GS3 that I had. Again, not sure if this is at all related to any of the other things.
So whats the wifi fix? Is there a known problem with the latest OTA update?
I'm on 4.1.2.
Build #9.8.1Q-62_VQW_MR-2.
System version 9.16.6.XT926.Verizon.en.US
Thanks guys?

MMS needs the carrier's internet to work..not WIFI...at least that's how it is on my network (Bell).
Sent from my XT925 using xda premium

slickfing said:
MMS needs the carrier's internet to work..not WIFI...at least that's how it is on my network (Bell).
Sent from my XT925 using xda premium
Click to expand...
Click to collapse
I am aware of that. It is my understanding that the phone disables WiFi to send an MMS and then enables it after the message is sent. It used to work just fine. I don't know what could be causing my problem. I have not changed any settings.

Just wanted to update that I'm still having these problems. 50% of the time the phone will send MMS. The other 50% of the time it will just hang there and keep trying to send and I manually have to turn off wifi to get the MMS to send. Phone still lags, probably worse than ever.
This is also not the same phone as when I first posted. I had a replacement from Verizon a few months ago. The problems carried over with the new phone.
I have been using an app called Clean Master to clean my cache and unwanted files. Seemed to work well at first, but now it doesn't feel like it does anything.

Can't send MMS current cyanogenmod 10 nightly

Hello,
I upgraded my wife's Galaxy S Blaze to CM 10 because her phone didn't get the ICS upgrade over the air and I saw a lot of reports of it having memory issues. (On nightly 20130707 right now)
Anyway, everything on it is great except for one thing that is VERY important to her: MMS messaging.
Whenever she tried to send one, it says "Sending..." for a long time, then eventually fails.
T-mobile is the carrier.
Any ideas?
EDIT: I just noticed while filling this out another thread called "Can't send MMS unless WiFi is off (CM 10.1)". Even though we're on 10, not 10.1 I tried turning off WiFi and it worked!
Is that any clue to a possible fix? I can leave WiFi off for now, but it is going to continue to frustrate her until it is fixed.
Thanks!
--mobrien118

I have never had any issues with MMS on the nightlies. I normally run with WiFi and data on (just tested a pic and working fine, sending and receiving).
FYI, there is a 7/14 nightly out.

CM10.1 is in really really early alpha stages. Like Romman said use CM10's latest nightly. Also, ICS was not an OTA update. You needed to connect your phone to Lies to update.
Sent from my Blaze/HTC One using Tapatalk 4 Beta(using both )