Hi All,
Something weird happened yesterday, my tytn II stopped working normaly.
I cannot make calls anymore and people calling me get my voicemail, although it shows full reception (t-mobile). The only call works, is calling my voicemail. I didnt change anything in the phone prior to this problem.
Also the battery is dropping down very fast. Like 50% in 5 hours without using anything...
I putted my sim in another phone, it works fine, so the problem lies within the phone. I hardresetted the phone but the problem remains...
Anybody had the same problems and/or knows how to fix this???
I have an original HTC tytn II on tmobile network.
THanks!!
Jelle
found comparing problem here, probably same problem:
http://forum.xda-developers.com/showthread.php?t=335074
Any help is welcome, also for the other users with the same problem!
Thanks!
same problem
Hi,
I also have the same problem you write about. It also happened for no apparant reason. I notice that I can make calls to other mobiles that are close to my phone in proximity... odd?!
I've sent an email to HTC ... waiting on a response.
I have started getting the same sort of problem. When I try and make calls - it just won't connect. Sometimes a soft reset works - but not always. People cannot call me and I get messages about missed calls and voicemail messages.
It's starting to make my Orange TyTnII virtually unusable.
Suggestions?
Had my O2 Steller (rebranded kaiser) with the original ROM for about a month and I cant believe it but i think its turned into a brick.
The problem I have is even though it gets a full signal I cannot send or recieve calls, texts or transmit any data. When the fault happens during a call I have the phone looking like it is connecting with the dialler but immediately ends the call.
I had initially thought it was maybe a bit of software causing the prob so removed any software I had installed , (HTC home Skype and google maps) this had no effect. Tried another sim card in case mine was faulty, still no effect.
Spoke to a mate who suggested that I try a hard reset and this seemed to give me a solution with it working for a day but today it started to go faulty again.
Anyone else had any similar issues similar?
Really peaved as O2 cannot get me a new Kaiser for some time as they initially said they were no longer available, then said they were out of stock but had no idea when they would get stock back in. Tried to palm me off with lower spec phones.
Main concern is getting my kaiser working again, so any help with this would be great.
id try a hard reset once more.. if that fails, call your service provider. they might be the cause of the problem
not techinally a brick since you can turn it off and on and see some functions... I might recommend completely flashing the rom... that might solve the problem if it is indeed a software problem
Hey guys,
I have had my Nexus One for a couple of months now but one nagging issue has been the call quality. I bought the AT&T version and I sometimes get blips of static or white noise during my calls. On rare occasions I don't have this problem. The phone is not rooted or modified in any way and I even tried exchanging the phone 2 times and both times I had the same issue. Could this just be an AT&T issue or maybe it is my location (Connecticut/Massachusetts). Is there anything AT&T could do? I did get a new SIM with no change. I talked to HTC tech support but there wasn't much they could offer except wait for the next update (Froyo?) and see if that improves the quality a bit. Is that even possible it would and how? I like this phone a lot but I was hoping I would have resolved this by now. Anybody experience this or have some insight on it? Thanks!
Jay
Must be an ATT issue over there. I have the exact phone as you, ran vanilla/unrooted for months and never had any issues.
I have the rogers version (att&t) and I have no issues like that here in Canada.
I have the same version in DC with none of those problems
Dear users,
So 2 months ago I returned to Europe from USA. I bought an AT&T Captivate over there and since it could not be used over here, I unlocked it. But after unlocking the phone I noticed an very frustrating problem :
When someone calls me there are absolutely no problems no mater how many times they call.
When I call someone the first time everything is also ok.
But when I try to call someone after I already called once, there is no sound. I can't hear absolutely nothing and neither can the person that is beeing called. Not a sound, not even the "beep...beep" sound (sorry, i don't know how it's called in English) when you are making a phone call.
So basicly I have to restart my phone after every time I call someone to be able to make a call and actualy speak to them, and then restart again.
I hope I described clearly what the problem is. Is there some way I can fix this because it is extreamly frustrating ?
P.S. i'm using Froyo OS.
The Froyo build is Beta - so it could be your problem. Also, the Captivate is still an AT&T phone, so even though it is unlocked, it may not like the network you are using.
You could try the following:
1. Different SIM - different provider
2. Roll back to 2.1
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?