Calls drop often. Usually within the first minute, and then every time when Im calling back after 10sec. The phone itself does not lose signal. Strange thing is, if I'm getting phone call after first/second drop, phone continues connection without problems... But Only when Im receiving a phone call not when Im trying to re-call someone.
- I tried replacing my sim and the issue persists. No problems with other phones using this Sim (even in the same locations).
These are pretty annoying issues. Anybody else experiencing them? Is there a different radio I can try for the phone? Is there any log I can access showing a reason for the call drop, or any trouble shooting I can do? This seems to be independent of WCDMA Only/Preferred/GSM/WCDMA (Auto) settings. Or if, how to change these settings?
Note: This has nothing to do with the network. I've been with the same company (Orange Europe) for about 2.5 years, and have never had this happen before. This has been consistent since I got my OnePlus (about 1 week ago)
That's true. I'm experiencing this as well for quite some time now. At first I joked and said: Hey, the NSA joined our conversation.....again. But after some time it really annoys me. This has nothing to do with the ROM or kernel as I have tried out various combinations. What I found out is that it got better after I returned to stock CM 11s with stock kernel. But it's not gone completly.
Honestly I neither know how to fix it nor what is causing the problem. Try to reflash the CM11S 25R firmware and see if it gets better. I think something is wrong with the modem software since CM11S 22R,25R and CM11 builds are using the same modem software. Maybe the announced update for the end of this month or early next month will fix this. I really hope so because a phone which is not able to hold a call, can't be considered as a real phone.
Oh im pitty You, If You'll get something just please let me know. Any advices or help will be appreciated. Maybe waiting for new CM relase will solve the problem, I do rly like this OS even with so many bugs... there is always an option. Move to stock 4.4 published by OP on official website.
Anyone else facing the same issue? Was there ever a fix for this issue? I'm on 38R and still encountering this issue
Same here.
See this thread for answers and work around. No solution as of yet.
http://forum.xda-developers.com/oneplus-one/help/dropped-calls-weak-lte-signal-t2916659
Related
The symptoms: SOMETIMES during incoming phonecalls Raphael rings (plays sound) but when I pick up the call, suddenly the phone sort of "mutes itself". I can't hear the person talking, nor can they hear me, even if I hang up and try later. The only thing that helps is a soft reset.
It's difficult to count the occurence, but I'd say like once a day at least.
I have already tried Hard reset, the phone is acting funny with only Advanced Config 3.1 and PHM RegEdit installed and a few tweaks applied (just Boost TFL3D performance tweaks and SMS conversation disabled)
I'm running stock 1.90.401.1 WWE FW, I have flashed a new radio version (1.02.25.31 Cingular) though.
Any advice/suggestion is appreciated.
Unless the new radio is giving you 3G, I'd go back to the stock ROM/radio combination and see if that works. I'm currently using the Cingular ROM/radio as well and I've never run into these problems, but that may be due to different hardware.
Thank you very much for a quick reply.
I'll try flashing the stock radio and will report back...
So, I flashed the original radio and it seemed for a while that the problem was gone.
Sadly, I must report that the problem is persistant as I had to restart my phone right now. When the "sound mute" thing happens I don't hear anything while answering phone calls (even though the phone rings normally!) and also when I try calling any number from my contacts including the operator hotline.
I really don't want to return the phone because I like it very much but having a phone which has problems with phone calls is kind of silly.
I'm at my wit's end.
Will anyone help me please?
I have a small update - today I was so desperate, that I tried flashing a custom ROM (namely DCS-TouchPro-v1.0 Hybrid) and the phone went bonkers right at the first incoming call. However, something IS different - now the phone is not silent but starts "buzzing" - making a long uninterruptible sound that lasts until reset.
Do you think I could have a HW problem?
I HAVE EXACTLY THE SAME PROBLEM!!!
I already posted a message in the "Issues" post of the Raphael Forum, but apparently no one had the same issue so far.
I did many hard resets (and installing gradually less things), it still bugs.
Currently the only tweak installed is the scorpion one to have 4 rows of icons in a menu.
My Raphael is behaving like this since 1 week. The bug occurs once or twice a day as well.
Anybody with some good IT experience has got an idea of what could be wrong with it?
Do you think it is more software related or hardware related?
Today it also crashed badly (grey doted screen and noway to make it work again by turning off. Had to soft reset).
PLEASE DO HELP US, because I'm using the phone for professional reasons and I'll really have to send it back if it keeps on bugging this badely!!!
I just sent a message to HTC Support.
Let's see what they say.
I'll post their response so those who have the same problem will know what to do.
Oh boy, I must say I'm glad not to be the only one with this problem, even though I never wish bad things to anyone.
While googling the problem, I found a few Diamond users with exactly the same symptoms, however most of them solved this by exchanging the device for a new one, so this won't help us much...
Me too, I was wondering if it was because I did something wrong with the phone...
But if I'm not the only it means that there is a problem with the phone itself.
Anyway I'll wait for the official answer from HTC...
I'll post their answer as soon as I receive it.
I'm actually quite curious what their answer will be.
But I wouldn't hold my breath for any miracle, so I'm preparing to send my phone to the service center to have them look at it...
Well.. that makes 3 of us then
at first i thought my symptoms are different, but Flippy confirmed they're identical.
http://forum.xda-developers.com/showthread.php?p=2611523#post2611523
I have to correct myself - I wrote that when the thing happens, the phone still rings, which is not true. It rings just the first time before the problem occurs, but then it's dead silent.
So it seems our symptoms really are exactly the same.
Told ya AntiProxy!
So we are indeed only 3. It is still ok, it means that there is only a very small proportion of of Touch Pro that have this problem.
Now let's only wait HTC's answer...
spoke to HTC support today.
not that i expected them to figure it out or have a solution at hand, but i figured what the heck.. give it a shot.
their solution?
hard reset.. the guy would swear by his daughter that a hard reset will solve it.
i just thanked him and hung up.. *sigh*
don't you just hate it when techsupport's solution to everything is a reboot or reformat.. when you know that's not the solution anyway!
Well, I tried already doing the "Clear Storage" through the settings -> system panel, but it still has got the same problem.
I'll give them a call aswell to see if by any chance I can get on the phone 1 person who will be able to provide us a better technical advice
Hard reset won't help, I've already done it like dozen times and it makes no difference...
I tried flashing the phone to the stock 1.90.405.1 ROM and so far (a day and half) I have NOT encountered the problem. It is too early to start hoping, but I wanted to let you know - if you don't mind flashing your phone, give it a try.
Zillator, can you keep us posted for like 1 week?
If in 1 week the phone doesn't present again that problem I'll flash it as well (I didn't want to flash it because I wasn't sure if it could void the warranty). If during 1 week you don't have the problem again it'll mean that out initial ROM was defective...
Thank you Zillator and please let us know. (by the way when I'll call them tomorrow I'll ask them if flashing the ROM to a newer stock version voids the warranty).
Zillator said:
I tried flashing the phone to the stock 1.90.405.1 ROM and so far (a day and half) I have NOT encountered the problem.
Click to expand...
Click to collapse
only thing is.. my phone is still running the stock ROM as it is!
AntiProxy said:
only thing is.. my phone is still running the stock ROM as it is!
Click to expand...
Click to collapse
AntiProxy, it might be a bug in the ROM we have in our machines. That's why maybe flash it could be the solution. Nevertheless I'll ask about the warranty tomorrow when I call them and let's see how it goes to Zillator.
If his phone doesn't bug for 1 week, there might be a big probability that the problem came indeed from our ROMs.
Guys, don't worry, I WILL keep you updated. I know how much the problem bothers me, so if there's anything I can do to help you, I will definitely do it.
In the end, that's why we are here - to help each other...
AntiProxy: is your stock ROM 1.90.405.1 WWE? Because mine was different (1.90.401.1 WWE) and I had the problem. Maybe Flippy_TK is right and the problem only exists in the 401 ROM.
I'll continue testing and we'll see...
My HTC Droid Incredible has had one problem since the start. The mobile data will drop out, and then reconnect. It happens quite frequently. The reconnect takes about 5-20 seconds.
I've done the *228 option 2 route already, that didn't fix it. Reboots don't fix it. Now I'm wondering if a new baseband, a new kernel, or a new radio would help. This is where I have the question. I have no idea what any of those 3 things are, or what they are responsible for on my phone.
What is a baseband?
What is a radio?
What is a kernel?
Which one would be upgraded/downgraded to get a signal that locks/better signal?
Which version should I get?
I don't want to do anything until I know exactly what these things do, and what to get.
The only thing I know at the moment is that kernels have something to do with power management. Certain kernels work better with certain roms. As to why, I'm not sure. I just do what the developers say.
As I've said, this has happened since I first got my incredible. I'm on my 2nd one (first one went through the washing machine), and the first one had this problem too.
I've tried searching for this problem since June. I keep finding similar problems, but not quite the problem I have. I just want the mobile data to stay connected. Rom changes do not help the problem.
So, can anybody educate me on what those things are/what they do?
Hey everyone,
I have had the infuse roughly since it was released. Never really had any call isuues or anything. Lately however, about 90% of my calls end up dropping. Also, when i try to end a call, the phone kind of freezes and shows that the call has not ended, but it should have. The phone symbol shows up at the top or the status bar stays green... I have no idea what this could be attributed to. I have used different roms and never had an issue. My most recent rom is the Max Q Rom and everyhing was working fine then after a few weeks this calling and ending calls situation started. Tried reflashing the Rom, but problem is still present, dont really think it is Rom related.
Anyone have any input? I cannot seem to figure it out and my phone as a phone has become virtually unusable...
Thanks for any and all help!
Heuser1 said:
Hey everyone,
I have had the infuse roughly since it was released. Never really had any call isuues or anything. Lately however, about 90% of my calls end up dropping. Also, when i try to end a call, the phone kind of freezes and shows that the call has not ended, but it should have. The phone symbol shows up at the top or the status bar stays green... I have no idea what this could be attributed to. I have used different roms and never had an issue. My most recent rom is the Max Q Rom and everyhing was working fine then after a few weeks this calling and ending calls situation started. Tried reflashing the Rom, but problem is still present, dont really think it is Rom related.
Anyone have any input? I cannot seem to figure it out and my phone as a phone has become virtually unusable...
Thanks for any and all help!
Click to expand...
Click to collapse
Have never heard of that.... still have you tried a data and cache wipe in cmw? then install a rom on a fresh device? I know you will have to back up all your stuff but may be the answer.
Also try another modem may help. Im not sure since ive never experienced that but give it a try.
Heuser1 said:
Hey everyone,
I have had the infuse roughly since it was released. Never really had any call isuues or anything. Lately however, about 90% of my calls end up dropping. Also, when i try to end a call, the phone kind of freezes and shows that the call has not ended, but it should have. The phone symbol shows up at the top or the status bar stays green... I have no idea what this could be attributed to. I have used different roms and never had an issue. My most recent rom is the Max Q Rom and everyhing was working fine then after a few weeks this calling and ending calls situation started. Tried reflashing the Rom, but problem is still present, dont really think it is Rom related.
Anyone have any input? I cannot seem to figure it out and my phone as a phone has become virtually unusable...
Thanks for any and all help!
Click to expand...
Click to collapse
I can relate. I had the same exact issue a few days ago. I just flashed and didn't look back.. though I probably will eventually. Try Mitra, very good. I loved it. Experimenting with Caty's rom now. Good luck. Wipe/factory reset, wipe dalvik and fix permissions. Then flash. Let it sit for 10-15 before you start using it. Make sure it settles and gets used to, "it's native infuse guts," as EXPERIMENT put it.
5/19/2013 Update: The bug might be dead! Like for real this time. See this post, post number 14 in this thread with an explanation of what to do.
10/25/2012 Update: TRY THE LATEST BUILDS OF BRUCE'S CM10 STARTING WITH THE 10/25 VERSION!
Bruce has made a change that helps differentiate between the regular data stream and the MMS data stream in an attempt to see if that was what was causing the instability issue. This is only on Bruce's CM10 Kang as of 10/25. If you are only another CM ROM, flash Bruce's (even if just for a minute or two) and see if the data bug goes away. Please report back if it did!
If this does cure it, I'm sure Bruce will share the sollution to all other devs and your favorite other AOSP ROm will have the cure shortly.
Updated 10/24/2012
This is a detailed description of the 6 million or so things that various people have attempted to do in order to rectify the blinking data connection problem plaguing T Mobile USA users on AOSP ROMs for the Sensation. This issue is non existant in Sense based ROMs.
The problem has something to do with how the Sensation authenticates itself with the T Mobile Data Network. It's not based on the cell towers as voice calling is unaffected. The theory is that the AOSP framework lacks the proper authentication certificates for part of the data network and when the phone is routed to that part of the network, it gets kicked off teh network, then continually retries to connect.
This was and issue on the Sense Gingerbread Stock ROM in 2011 but T Mobile and HTC patched it. All Sense ROMs are free from this bug. But no one knows what exactly the patch was so AOSP ROM's have not been able to be cured yet.
Short version....
Problem started for me on Bruce's CM10 rom. But it's reported on all CM10 variants and most CM9 ROM's as well.
One day I noticed that data wasn't connecting well. It would blink on and off. Sometimes it would stay on, but if I turn it off then right back on, it might go back to blinking.
The problem exists on all AOSP roms (AOKP, CM9, all versions of CM10) even after full wipes and restores of known working nandroids.
Cell signal for voice calls works perfectly. No problems whatsoever. So the phone is connecting to T Mobile. It just won't get data.
Long version....
To fix this I've tried the following...and how each does or doesn't work.
Switch to 2G networks only and switch back. Problem remains, and still blinks E on the EDGE networks rather than being solid on them.
Updated the radio. Problem remains.
Updated the entire firmware package. Problem remains.
Superwipe and flashed Sense, verify data works well. Then regular wipe and flash a fresh install of CM10. Problem remains.
Flashed clean version of CM10 and fixed permissions. Problem remains.
Made calls from the phone. Some people have reported that this helps temporarily.
Sent myself a text message. Some people have reported that this helps temporaliy.
Turn on airplane mode for a minute then go back to normal. Some people have reported that this helps temporarily.
It's not related to Wifi at all because I've created the error on fresh installs of CM10 before ever turning Wifi on.
Formatted SD card. Problem remains (and just to be sure I got the error while the blank formatted SD was removed from the device)
Checked the APN's 100 times. They are correct.
Spent an hour on the phone with T Mobile. Their tech said everything looked good on their end. He cleared the SIM and reactivated it. Problem remained.
Other people have gotten new SIM cards and found that while they helped right away, the problem eventually came back.
The only things that have shown any help to multiple users are in bold above. There are various reports of 100 other 'fixes' that people swear fixed the problem for them. But all of them involved the phone disconnecting from the network and reconnecting. That appears to be the key to get data working again temporarily. Making calls and sending yourself text messages also forces authentication on the T Mobile network without breaking the original connection.
If you want more details or want to review the logs to see if you can figure it out, logcats of the problem are located in this post! Click here for logcatty goodness!
Here is the real kicker....
Everyone once in a while...it connects. And once it's connected it'll stay connected until I turn the connection off or reboot the phone. Then it'll go back to blinking in and out when I try to turn it back on.
Just another note, the data is finicky on my old LG G2x also on TMobile with AOSP based ROMs, talk works, but cell data won't come back after going into airplane mode and out, until a reboot. It works fine on official TMobile ROMs. I suspect there may be some proprietary cell data negotiation between handset and Tmobile towers that AOSP code doesn't have.
Whyzor said:
Just another note, the data is finicky on my old LG G2x also on TMobile with AOSP based ROMs, talk works, but cell data won't come back after going into airplane mode and out, until a reboot. It works fine on official TMobile ROMs. I suspect there may be some proprietary cell data negotiation between handset and Tmobile towers that AOSP code doesn't have.
Click to expand...
Click to collapse
Okay here's an update on this for anyone who finds this thread through a search or Google or something....I'll try to describe this using the simplest terms possible so those of us who aren't cell tower engineers can understand it. (And I assume that's most of us, including me!)
The latest running theory is that the issue occurs due to the way the phone is handed off from 1 tower to another.
As you move your phone is handed off from one tower to the next. You get unregistered with tower 1 and reregistered with tower 2. That's normal.
However if you are within range of 2 towers you can't be on both. You have to be registered with 1, and that's supposed to be the stronger one. But AOSP ROMs lack a T Mobile certificate that authenticates which tower is supposed to have priority. So when the data is blinking you are getting bounced between 2 towers because the phone is trying to register with both.
The latest version of Bruce's CM10 ROM (Dated 10/10/12 and with TMOUS DATA in the rom name on the download page) supposedly includes patches that fix how this authentication works. And I only say 'supposedly' because the patches have only been up for about 12 hours so the jury is still out on how well it works. Personally I've been on it all day today and haven't had the data issue yet. But it can be days in between seeing it. So it'll take a while to know for sure that it's fixed.
If this turns out not to be the exact cause of the problem, it's something similar and a final sollution should be found soon.
Update: This have never been substantiated, and several users with the bug have reported knowing for a fact that they experience the problem when in range of only 1 tower.
Hi,
I have noticed with JB ROMS that you get 7 or 8 APN's,most of which do not apply to me.
Have you tried (making a note of your one first) and deleting all the APN's
Reboot,and just install yours.
malybru said:
Hi,
I have noticed with JB ROMS that you get 7 or 8 APN's,most of which do not apply to me.
Have you tried (making a note of your one first) and deleting all the APN's
Reboot,and just install yours.
Click to expand...
Click to collapse
That's one of the 1000 things that's been tried, to no effect. If he APN is set to the correct one the extra APN's are ignored.
Nothing that you do within the phone can cure the problem. At most, forcing the phone to re-register with the tower is the only thing that can help, and that will be temporary if it works at all.
The best bet now is to hope that Bruce fixed it with his latest additions to CM10 now that we understand what the actual problem is (or at least that we think we do)
Update....
T Mobile data is still broken. It has not been fixed yet. The latest theory may just be one more in a long line of theories that turned out to be wrong.
There are days when I really hate this phone.
Thanks for the update. I've been monitoring that thread occasionally, but it has way too much traffic for me to keep up. I was close to switching to it, but I need good battery life and reliable cell service over any smoothness benefits of JB, which is why I'm sticking with HyperNonSense ICS for now.
been experiencing this issue for a couple months myself. currently stuck in a no data bout as we speak. i'm wondering if it has anything to do with the amount of data we've used. i noticed this last bout started right around the time i passed 5gb. should also be noted i'm on the unlimited 4g plan and tether like crazy. i guess i'll know if the problem persists until my next billing cycle. for now i'm stuck with a sense nandroid and crack flashing aosp daily to see if it's fixed.
cpittman said:
been experiencing this issue for a couple months myself. currently stuck in a no data bout as we speak. i'm wondering if it has anything to do with the amount of data we've used. i noticed this last bout started right around the time i passed 5gb. should also be noted i'm on the unlimited 4g plan and tether like crazy. i guess i'll know if the problem persists until my next billing cycle. for now i'm stuck with a sense nandroid and crack flashing aosp daily to see if it's fixed.
Click to expand...
Click to collapse
I have tried the SIM swap fix. And that has apparently worked. I've been using in good for about the last 6ish hours without any problems. :good:
So i'd give that a shot if your willing.
I've been using CM10 KANG since it was available for HTC sensation. Never had the data blink issue. Recently, my phone started to have this issue. Data would simply not connect with CM10 or CM10.1 with any radio/firmware combination. I also noticed that when I travel to work, i get data say after 10 miles away from my home and it continues to work after coming back home. However, after restarting the phone, i hit the blink problem again. Wondering if its because of some cell tower maintenance/upgrade near my area.
So I was on bruce's ROM until a week ago and this never happened while on his ROM. Just upgraded to albinoman's ROM and this started happening. I have to send myself a MMS picture to get it back again. Hope this helps
Fix
Ive had this problem on and the only thing that seems to help is flashing a new ROM but then a few weeks later it returns... I realized that this only happens when I try to send an MMS message or attempt to receive them. I don't know how to stop receiving an MMS but just delete the picture message you're trying to send and your data should stop blinking on and off. Can't guarantee it'll work for you but it worked for me! GL!!
It appears as though this stupid annoying silly obnoxious bug has finally been squished, sprayed with 3 cans of Raid, and its' mangled corpse then burned to a crisp...I hope.
3 weeks ago W1ldFl0wer brought this fix to Albinoman's attention...
In the build.prop under phone>system was the following line....
ro.telephony.ril.v3=datacallapn,signalstrength
This line appeared like this on all AOSP roms for the sensation.
The fix was to add skipbrokendatacall to the line so it looked like this....
ro.telephony.ril.v3=datacallapn,signalstrength,skipbrokendatacall
Save the file, reboot, and data should spine right up and work fine. So far the peopl ewho have run into the data bug have implimented this change and BOOM, data fixed.
So if you use any AOSP ROM 4.0, 4.1, or 4.2 other than Albino's CM10.1 Kang just add skipbrokendatacall to that line and see if it fixes it. Only do this if you on in the US on T Mobile's network. If you are in parts of Europre making this change will screw up your data.
If you are using Albinoman's CM10.1 Kang ROM, he has already included this line in the build.prop for you. You just have to activate it. About 30 lines into the build.prop is the new line that reads...
#ro.telephony.ril.v3=datacallapn,signalstrength,skipbrokendatacall
Just delete the # in front of that line. (The # makes the ROM skip the line when loading everything, but lets it stay in the file so you can read it. Deleting the # means that the phone will read that line when it reboots.) Then go up to the line that says the same thing without skipbrokendatacall and delete that line entirely. Save the file and reboot. If you don't delete the original line without skipbrokendatacall, your phone will go haywire, data might not work at all, and you might inadvertantly trigger Z Day. So if you're not ready to fight in the zombie apocolypse, only leave one of those lines in the build.prop.
Hope this cures it for everyone! Again, don't make this change if you live outside the USA or are not on T Mobile's network! Doing so on other networks in other parts of the world could make things worse for your phone!
Here is the link to the post where W1ldFl0wer informed Albinoman of this fix.
http://forum.xda-developers.com/showpost.php?p=40755845&postcount=9003
I don't think W1ldFl0wer invented the fix, but he certainly is the one who made it public to Sensation users so go to that post and thank him/her bcause I might finally be able to stop obsessing over this stupid bug because of this user!!! :good:
I've had this issue for quite some time now, two months I think, I don't recall it happening before. Sometimes I have my phone on, good LTE signal, everything seems fine. Then when I make a call or send a text, or even without doing it, randomly I get a message from my carrier that someone has called, just as if my phone would be off. Or I get an SMS 5 hours later.
This is really frustrating. It persists on 38R and PA. Haven't tried latest CM nightlies yet. And yes, I've tried reflashing factory images and testing different modems. I'm using Franco kernel, haven't tested much without it but I doubt this might be the issue as no-one has reported anything like this.
Can this be my carrier's problem? Should I contact OnePlus support?
Irseq said:
I've had this issue for quite some time now, two months I think, I don't recall it happening before. Sometimes I have my phone on, good LTE signal, everything seems fine. Then when I make a call or send a text, or even without doing it, randomly I get a message from my carrier that someone has called, just as if my phone would be off. Or I get an SMS 5 hours later.
This is really frustrating. It persists on 38R and PA. Haven't tried latest CM nightlies yet. And yes, I've tried reflashing factory images and testing different modems. I'm using Franco kernel, haven't tested much without it but I doubt this might be the issue as no-one has reported anything like this.
Can this be my carrier's problem? Should I contact OnePlus support?
Click to expand...
Click to collapse
OnePlus support is about as effective as sandpaper toilet paper. I'd suggest getting a replacement (NEW) sim from you carrier if you haven't already.
S M G said:
OnePlus support is about as effective as sandpaper toilet paper. I'd suggest getting a replacement (NEW) sim from you carrier if you haven't already.
Click to expand...
Click to collapse
I thought about doing that, guess I'll have to stop by their store soon.