Hi
Had the kaiser 3 months now..had the initial prob with the speaker phone...where people just couldnt hear me..now this..
I know its the phone has tried my chip in my old phone and no problems.
everytime I make a call the other people say that my voice is cutting out and coming back in..sometimes the phone call just cuts off and i have to call back..
anybody here having the same probs with Kaiser/wario III etc.??????
Rish
This could be a hardware, software issue. Without checking we cannot tell. Hopefully it's either software or the "banswitching" issue. If it is a new thing that has just started then a hard reset may solve the problem.
Many folks with newer phones in areas where different available phone bands are present, report dropped calls as the phone seeks to change to the strongest signal.
See this thread (one of many) that mentions the problem) also note the Bandswitch application that lets you fix the phone to one band to avoid the problem:
http://forum.xda-developers.com/showthread.php?t=320942
Mike
RIISHI said:
Hi
Had the kaiser 3 months now..had the initial prob with the speaker phone...where people just couldnt hear me..now this..
Click to expand...
Click to collapse
I presume you've tried turning off Microphone AGC (Automatic Gain Control) if it was enabled and you're using the speakerphone?
This is not a thread that im complaining but I need to know if im the only one experiencing these bugs and issues . I love the Tmobile g1 but im also fed up with a lot of problems . I think the biggest issue is on the network, I dont think its a OS problem anymore Im pretty sure Im not the only one with the problems because I see these issues posted on google, xda, and other forums, but its appears lately no one is saying anything about these issues and bugs so I want to make sure that im not the only one experiencing these problems.
-Dropped Calls
-Sometimes no internet service
-Sometimes not even being able to call out or send text messages [message not sent]
(usually fixed by restarting my phone)
-I use to not receive notifications (email and texts) but ive fixed that by installing dgAlert.
I called tmobile reguarding these issues and they had me replace my sim card but im still getting problems. I received excellent service, they are calling me back on tuesday to help me out more (they re-registered me on the network but that didnt help either).
*Yes, my g1 is rooted but I highly doubt that is the issue.
The G1 is truely a good release but before they go making another phone (HTC Magic) why havent they took the times to prefect the g1.
Thanks for reading and you sharing your issues or recomendations would be greatly appreciated.
I located this one post also http://forum.xda-developers.com/showthread.php?t=501146
-Dropped Calls: I used to have this problem quite a bit. I switched to 2G only which seemed to correct the issue. I had a flurry of problems where the 3G network was out sporadically for 2 days and since then I have not had a dropped call with 3G active. I am hoping this was an update to the network and the dropped calls a thing of the past. Not betting on it though.
Edit: submitted by accident
Sometimes No Internet: Except the outage noted above none that I know of.
No notifications: no
Can not make calls: no
Hi I am using the ATT HTC VIVID from Nov 2011.
I bought this phone last Nov 11, and I stated noticing my phone was not receiving any calls if I stay at home(jersey city). If anyone calls to my number it will not connect at the same time it will not sent to voicemail also. It will say "call couldn't be completed".
After 2 months fight with ATT, they tried
1. they did a factory reset on my phone - it didn't help
2. changed the sim card - it didn't help
3. finally they replaced a another HTC vivid
even that didn't help
finally they said there was issue in near to my home and they fixed it.
now i a started receiving calls but now the new issue is, if I call to my number it will not connect first time it will go to voicemail, and second time if i try then it will ring. (First time also my phone is idle) This is happening randomly and ATT is not helping on this situation. As per them I am not able to replicate when they were testing on my phone.
Because of this issue I am missing calls which is making me really frustrated. After three week of research I found this is happening in not only near to my home its happening at my work place (NYC) and if I go around also its happening.
Can someone please give some advice to fix the issue that would be really great
Is there anyone else in or around your home with AT&T service? If so, do they experience the same problem as you? Can you receive calls everywhere else besides home and work? Do text messages get through? How about internet service? MMS?
Thanks for your response
The issue is not around my place
The issue is, if any one calls first time it will go to voice mail, if they call again it will connect to my phone. This behavior is happening randomly.
It is happening in my work place(NYC) and also if i go some where in new jersey also. I can't tell when its happening and how. In a day it may happen one or two time. I can't check constantly on a day when and where.
Sometime i feel I am not getting call, if i try from land line it may work or it may go to voice mail, after the second try then it will be fine for that day.
this issue look little weird. but because of that I am missing calls.
forgot to mention, that time my internet will work fine, how I am sure is one time i was browsing and trying to call my phone from land line it didn't connect. as usual second time if i try it did connected
Also the signal bar in my home and my work place its full
First of all, I want to say that I found people with the same issue using Android everywhere and with a lot of different phones, so it's probably an Android bug rather then Moto X itself, but I wanted to leave my report.
I came from an S3, which suffered from the same problem when using Cyanogenmod. When using official Samsung ROM everything worked as it should. Now, I'm getting the same issue on my brand new Moto X.
When I try to call someone, sometimes it just doesn't call, after I press the dial button, it just hangs (without ringing) and finished the call with a "Cal ended" message. It happens randomly, and sometimes I can't call anybody for like 2/3 hours.
The simcard has been changed from the S3 (micro) to the Moto X (nano), so it's probably not it. Also, with the Samsung ROM it didn't happen.
I can still receive calls and messages, and the signal strength is fine most of the time. I just can't call.
Today I faced this problem and then I tried calling from my girlfriend smartphone (samsung ace IIx) at the same time, which is from the same carrier, calling to the same number, and it just worked fine. Mine still didn't work though.
Here is a thread on people on xda facing the same problem, but with a different phone: http://forum.xda-developers.com/showthread.php?t=2351227
Don't know what to do.
i've had the call not go through as you've described, but have never had a phone not let me place "any call" afterwards. i always chalked it up to poor performance (limited RAM, too many processes, etc). My DROID3 would do it and often times when it finally did make a call, there was zero sound and I would have to reboot the phone.
640k said:
i've had the call not go through as you've described, but have never had a phone not let me place "any call" afterwards. i always chalked it up to poor performance (limited RAM, too many processes, etc). My DROID3 would do it and often times when it finally did make a call, there was zero sound and I would have to reboot the phone.
Click to expand...
Click to collapse
Hmm, it doesn't seems like poor performance. I ended up every task and it still happened.
However, I noticed that when I check the "2G ONLY" option it comes back to work. Maybe it's something with the HSPA/HSPA+ connection.
it could be completely carrier dependent then. my experience has been with vzw.
Moto X "Call Ended"
I have experienced this same problem in Houston on the T-Mobile network after switching over to Android. My T-Mobile rep told me they have had towers vandalized for copper which has impacted service for them, I believe he said it was about 15 towers and 10K a pop to get things corrected. What gets me is I was on a Bold 9900 and while I had signal problems in the affected areas of town I didn't not experience the "call ended" issue. I can also call other T-Mobile phones from those same areas but not land lines so to me this seems like a possible network routing issue which I have seen before between specific carriers.
If the problem does continue I may have to switch carriers. T-Mobiles service was previously outstanding in Houston but recently had not been great after the 4G LTE upgrades. I support multiple hospitals and need service to work correctly and will work with the T-Mobile Engineers to see if I can make headway on that front. I noticed another MotoX user reporting he only had the issue when flying in to Houston for work and that everything worked for him outside of Houston. His solution was to operate in 2G mode which for me is really not an option. I have to handle a lot of tasks over the network while on calls.
Anyways I would appreciate it if others could post if they are experiencing these issues and give as many details as possible so we can try to isolate the root cause of this problem and if found to be a carrier issue we can escalate with them. Thanks
dicarli said:
First of all, I want to say that I found people with the same issue using Android everywhere and with a lot of different phones, so it's probably an Android bug rather then Moto X itself, but I wanted to leave my report.
I came from an S3, which suffered from the same problem when using Cyanogenmod. When using official Samsung ROM everything worked as it should. Now, I'm getting the same issue on my brand new Moto X.
When I try to call someone, sometimes it just doesn't call, after I press the dial button, it just hangs (without ringing) and finished the call with a "Cal ended" message. It happens randomly, and sometimes I can't call anybody for like 2/3 hours.
The simcard has been changed from the S3 (micro) to the Moto X (nano), so it's probably not it. Also, with the Samsung ROM it didn't happen.
I can still receive calls and messages, and the signal strength is fine most of the time. I just can't call.
Today I faced this problem and then I tried calling from my girlfriend smartphone (samsung ace IIx) at the same time, which is from the same carrier, calling to the same number, and it just worked fine. Mine still didn't work though.
Here is a thread on people on xda facing the same problem, but with a different phone: http://forum.xda-developers.com/showthread.php?t=2351227
Don't know what to do.
Click to expand...
Click to collapse
Call Ended Issue Resolved
Hi All,
I see this Call Ended Issue in many brands. So I assume the error is a combination of the Network along with the SimSlot.
I tried various combinations for my Moto-E mobile.
Before i post the solution i found, Let me provide a brief about the problem.
I use Vodafone network on sim1 slot and Uninor network on Sim2 slot. I started facing the call ended issue on my sim 1 vodafone network.
I inter changed the sim's and found the network working absolutely fine. This makes me to understand that the sim1 slot with the vodafone carrier has some network issue where that IMEI code has some problem.
i tried to place the vodafone sim again on the sim 1 slot and found the problem persists. So i came to that conclusion.
Hope this might help you and provide a instantaneous and temporary resolution.
Thanks,
Praveen.
Call Ended problem still going...
Hey,
I just rooted my Moto X (XT 1053), like 5 min ago, in the hope to fix this same problem. I`m no programer/developer and have nothing against rooting, I just don`t think I`m that kind of user. Anyway, about a week ago my phone started to drop my calls right after dialing. I restored factory settings, updated it and nothing worked. I took it for service and they offered to charge me 150 bucks to restore factory settings and update the software. So I was kinda forced to root and try to fix it this way. The problem is that I probably don`t understand half of what you guys say, so if there are any kind souls out there, please help me out.
To sum it up:
- No Sim Card error
- I get carrier services and can use mobile internet (3G because 4G is still too explensive here in Brazil)
- Directly drops my calls
- Won't receive calls
- Won't send or receive text messages via carrier (just over 3G or wifi)
I`ve tried another carrier's Sim Card, no go.
I`ve tried my Sim Card on another phone and it worked just dandy, so I really don`t think it`s carrier related.
I`m running Android 4.4.3, as the other updates weren`t available for my phone via Motorola. I thought maybe updating to a newer version of Android might do the trick. I just have no clue on how to do that on a rooted phone... or on a non rooted phone for that matter.
Can anyone give me any tips/pointers/etc... ?
Thanks!
I have the same issue with my moto x on Verizon. Have you been able to figure it out?
Be aware: just calling 112 or 911 for testing purpose can be a criminal offence in your country
At the moment I am running the latest version of Resurrection Remix on my international M7 .
A while ago I needed to call the emergency services (112 in my country) but my phone immediately rebooted as soon as I press "call"
Now this is something only a very few of us will check but I'm curious if this could be an underlying problem of custom Roms in general because; who the hell will test this after installation of a custom ROM?
Proofing my above point is the fact that a Google search ("phone reboots when calling emergency number") doesn't give a lot of answers.
what I tried:
calling any other 3 figure number will work. In my country Portugal there's a number for forest fires 117, it worked.
I tried a few other dialers and also tried changing the default settings for the dialer (phone app).
I also tried to call 112 after start up, when the pin screen tells you "only emergency calls". It had the same result: reboot.
Perhaps some readers are willing to test this on their phones and report back? If your phone doesn't immediately reboot: cut off the call and all should be good (I guess)
I read in another device's forum about people testing emergency numbers routinely. They said they explained to the operator that they were making the call to test software and that they didn't get in any trouble.
Your mileage may vary, of course.
Well, I test it as well but I'm quite sure that many countries around the planet made it even a criminal offence (ie the Netherlands)
@ Floborg: could you tell me which fora you read about testing? Some devs might give me hints why my phone reboots every time I try 112 or 911.
It was in the Samsung Galaxy Exhibit 4G forum on XDA (the Cyanogenmod thread comes to mind). Some of the old devs and testers are probably still active in XDA somewhere, but probably not in that old device's forum.