Related
I've seen this issue come up several times lately. Unfortunately I don't know the cause or have a solution, but I do want to see if we can figure it out together.
I tend to have very good luck with calls and signal holding on the 2.X ROMs. I've dropped a couple calls over the last few months, but that's generally signal related.
One thing I suspect, but have yet to confirm, is that either ActiveSync or other network app is trying to create a data connection and the phone is obliging, knocking down the voice call as a result. It *shouldn't* behave that way, so I'm just guessing based on a few quick observations, but it might be something to look into. I don't know how much control the OS can give to apps when it comes to forcing a data connection at the expense of voice (should probably be none), but maybe there's some badly behaved apps out there.
I'm just throwing ideas out so we can work towards a solution.
EDIT:
I should probably clarify that I'm talking about a problem of dropped calls happening at seemingly regular intervals, not dropped calls due to poor signal strength.
I have to completly agree...my favorite rom was on of the first summy rommy's but as always i kept going to the newer ones as i have no self control. I was getting a ton of dropped calls I thought i was hiitting the end button with my cheek it was so bad. I have been running the new dopod 2.21.13.1 WWE and it has been flawless, it get about 28 mg of program after clean install. I have had just about every damn rom on my phone and this works well. I don't do the extended rom, i just use a autorun i made with all my apps i normally use, maybe give it a try, it could also be dumb luck, but i have yet to have a single dropped call, and i do sales in Las Vegas to the hotels and I get reception in elevators and in basements I never used to. You are the expert, let me know. ****Warning this post is 100% personal experiince, and absolutly no expertise except experience screwing up my device and late nights running stupid benchmarks for hours to see if I can get it a wee bit faster. Stafford out
well i'll say this, everytime it happened, it lokked like it was going into flight mode each time, then going out and back to normal a few seconds or so later. i flashed with the cooked a2dp rom, and left everything stock, it hasn't happened since.
I haven't seen it at all on the stock Qtek AKU2 rom. It seems odd that a re-flashing process seems to correct this since the base rom is the same. You'd think customizations may be the underlying cause but then everybody should be experiencing the issue.
i was having the same issue too, so i was thinking maybe it was the radio rom. i downgraded the radio rom to 1.13 and i've been testing it out so far. The last two days i've been okay with no dropped calls though i have not made any very long calls yet to fully test it out. i will keep u guys posted.
Well Summiter, for what its worth, I have an 8125 and I'm running that Cingular_RUU_WIZARD_217_AKU2_WWE.exe ROM you released. Radio version 2.07.10.
My results have been absolutely phenomenal. Not only is the device rock solid at clock speeds in excess of 270 MHz, but the battery lasts incredibly long and I have had zero dropped calls in over 2 weeks of use within a 50 mile radius.
Even though this ROM doesn't have your A2DP cab I quite frankly don't care, I'm going to have to think long and hard before I use any other ROM version, official or not.
Edit: I should also note that I'm using Direct Push which means I'm on a constant EDGE/GPRS connection. Even though I've been running this for around a week now, it has had no noticeable effects on my ability to receive or make phone calls. My sole issue with Direct Push was a lockup that would occur when I enabled WiFi, but changing the WiFi registry key "ResetOnResume" to 0 has fixed this.
just an update. i downgraded to 1.13 radio rom and direct push and all calls are fine now. I think i will leave it with this radio since everything is working great now.
Happened during Active Sync
Saw it with my own eyes! On the phone with our PM through BT800 this afternoon and was looking at the screen when Active Sync kicked in and the call immediately droped. (But I did get an email for a good price on Viagara!)
Running: MSVC, SPB Pocket Plus & push email from Exchange
For those folks that changed to a 1.X radio version, I'd like to know if your issue has been completely resolved, or if it's only improved to some degree.
I think the AS activity when a call drops may be because it opens a data connection the millisecond the radio has closed voice (when dropped for other reasons). In other words, the appearance of AS or other data activity actually forcing the voice call to drop is misleading.
If I experienced dropped calls on any significant basis I'd test more of this myself...but (un)fortunately I don't drop calls more than once a week, if that. So..I have to depend on you poor saps who can't hold a voice call to attempt to resolve. >: )
i thought it had resolved completely but i had my first dropped call last night with the same problem looking down and seeing that it dropped the call...tried to establish gprs(edge) and then went in and out of flight mode. the 1.3 seemed to have fixed it a little but not completely. with the new radio i was dropping calls within 4 mins of a call. with the new radio rom i have the only one dropped call 45 min into my call. I probably would have dropped 3 or 4 times before. I don't know what else to do to fix it.
What ROM version and radio version are the people with this problem running exactly? I think that's a good start maybe to get a scope for the issue.
I'm using "Cingular_RUU_WIZARD_217_AKU2_WWE_CF2_A2DP-fixed.exe" and have experienced many dropped calls immediately followed by no signal (searching for signal) for about a minute after dropping the call.
ROM Version
I'm using the Cingular_RUU_WIZARD_217_AKU2_WWE_CF2_A2DP.exe ROM
I'll try some tests tonight to duplicate what happened yesterday.
Another bit of information that could be helpful is whether or not you are using handsfree when your calls are dropped. This is especially important if you are using the A2DP hack or a ROM integrated with A2DP.
Clueless
Don’t know what the h*** happened yesterday. (maybe I’m seeing things….or the “flight-mode” hiccupped?)
Called to & from the phone with & w/o hands free while sending myself emails. No failures…why?? Because GPRS is suspended during phone calls. I’m sure there is a reg hack to enable GPRS during a call.
crosbyme said:
I'm using "Cingular_RUU_WIZARD_217_AKU2_WWE_CF2_A2DP-fixed.exe" and have experienced many dropped calls immediately followed by no signal (searching for signal) for about a minute after dropping the call.
Click to expand...
Click to collapse
I should note that this has occurred while on a bluetooth headset (not stereo) and also when not on the headset.
I'm using Cingular 2.26 Aku2.3 w/a2dp FULLY LOADED *BETA* **UPDATED**
I get dropped calls using a bt headset, a wired headset or no hands-free at all.
Appears to go into flight mode and back out when it occurs. I have noticed that activsync runs all on its own (i haven't synched with a pc even once)
I've had the issue on every rom i've tried recently although i don't remember what they were.
I have a question....my handset not only drops the call it soft resets about 5 mins into the call. POOF! IT is CRAZY!
Anyone having that issue?
On edit for more detail and clarity:
It even happened after I did the HTC GPRS workaround. It didn't stop until I disabled data and activesync through the comm manager
I am not having that issue now. I'm on a new rom.
My stock 8125 will do a reset, but it isn't with every call. I think I've only seen this when using hands free. I'm here looking for an updated rom to get rid of this "feature" of dropped calls and resets. Its driving me up the wall.
And yes for the basic dropped call, mine seems to go into flight mode when this happens, and yes, I see ActiveSync then running on my phone when I wasn't connected to a PC at all that day. The dropped calls happen whether I'm hands free (non stereo BT headset), or just using the phone handset itself.
This is my main frustration with this phone right now. Microsoft Voice Command (new 1.6 with BT support) fixed my other complaint in making the phone easier to use as a phone.
mfrazzz said:
My stock 8125 will do a reset, but it isn't with every call. I think I've only seen this when using hands free. I'm here looking for an updated rom to get rid of this "feature" of dropped calls and resets. Its driving me up the wall.
And yes for the basic dropped call, mine seems to go into flight mode when this happens, and yes, I see ActiveSync then running on my phone when I wasn't connected to a PC at all that day. The dropped calls happen whether I'm hands free (non stereo BT headset), or just using the phone handset itself.
This is my main frustration with this phone right now. Microsoft Voice Command (new 1.6 with BT support) fixed my other complaint in making the phone easier to use as a phone.
Click to expand...
Click to collapse
I have noticed that ActiveStink is in my tasks as a running program when I'm not connected to my PC. I think though it is because I have an exchange server. I wonder if connecting to the exchange server is what is causing the call drops?
I have an ATT Tilt with a personalized cooked ROM. I make a call which the dialer says it is dialing but I hear no ring. It then says it is connected but I cannot hear the person I'm calling nor can they hear me. I've confirmed that it does ring through to them and they answer, but we cannot hear each other.
The only way to fix it is to soft reset. Pain when I really need to make a call.
Has anyone had this problem? Better yet, anyone know of a permanent/non-reset remedy?
Thanks!
Alan
Yes indeed, sounds very familiar! My wife's tilt (stock rom) did it for a period, soft reset let it work for a little while. We called ATT support, tried everything to no avail. Received a replacement phone, all is well now.
My phone (stock rom) has done it a couple of times. Seemed to be related to lower signal strength environments like a costco warehouse. May be related to applications I have downloaded. I have a feeling Voice Command could be problematic.
I do have voice command installed as well. It would not surprise me at all if it is the culprit.
Same here on occasion (German TyTNII ROM). No voice command installed, for me not signal strenght dependent.....
same here from time to time. from what i can recall, it only happens when i am using my bt headset.
HTC have a bluetooth fix to download if you're getting problems with calls while using bluetooth.
Same problem here from time to time (no bluetooth active & no voice command though)
Funny, I have had this happen to me a few times, too. It just started about a week ago and has happend on about 2-3% of my calls. Another thing I noticed what during an inbound call, when you answer call waiting, the original party's call is not terminated (if you know what I mean).
Is anyone using Live Search when this happens? The loss of audio has happened whenever I have Live Search open, possibly with gps on, and when a call comes in, theres no audio. Im not sure if this is just a Live Search bug or a general GPS related bug, but its pretty consistent.
TILT Audio problems
I have had similar issues on my stock ROM ATT TILT (Mobile 6.1). Sometimes audio goes away (call connects without audio). I have also noticed 402 errors in browser at times (while using Edge connection). In both cases, hard power off-on fixes the problem. Very annoying issue.
I have Live Search installed, but the problem started prior to that - possibly about the same time as I installed the 6.1 update.
I'm not sure what triggers / influences the problem. I may have noticed Bluetooth device disconnecting (like when I walk away from my car's handsfree) having some influence. As an additinal input, I don't recall this problem occuring if the Bluetooth radio is disabled.
Any thoughts?
having this problem with the TOUCH PRO 2
Having problem with TP2
Hey all,
I'm at my wit's end with my G2 - I'm having an issue with every ROM I've tried (Malladus, XDABBEB, C-RoM, LS, AOKP, CM11...): bluetooth simply refuses to work. I can pair, for instance with my car, but then bluetooth simply shuts off and tries to restart, but then crashes again and won't turn back on unless I reboot. Sometimes I get a com.bluetooth.blah has stopped working message, but for instance on XDABBEB I don't - it just fails silently.
This happens with every ROM. I have reverted to stock 10B and tested it and every other OTA on the way up to official 24A, and all the stock official ROMs work fine. But on 10B, 12B, and 24A bootstacks no ROM will allow me to use bluetooth for more than a couple seconds after pairing.
Possibly unrelated, but I had the classic GPS problem and didn't bother with the hardware fix attempt - updating to 24A fixed it, so I now have GPS working in non-stock ROMs. Bluetooth is the last key.
Please help?
-guidfail
Might have fixed it myself.
I did two things differently when I got it working this morning on C-RoM 20140510 build (it failed first, then I tried the two new things):
Changed the name of my phone away from the default
Selected "No" when asked for permission to read my messages (which I assume is SMS)
I did select to allow access to my contacts and call history. Bluetooth did not crash and I was able to pair and use it just fine.
Please note, this primarily concerned pairing with a car (a BMW with iDrive).
-G
I have flashed the official google images. MRA58K and MRA58R - both have the following issue:
I'll outline it logistically:
* I connect bluetooth to my 2013 Honda Accord
* When I dial a phone number from the nexus device OR using the car's bluetooth menu the bluetooth disconnects
* the phone continues to call the person
* after the person answers the phone and says hello a few times, the phone reconnects to bluetooth
* the phone call goes on as normal. At this point I have a 20% rate of failure where the phone call connects for a few minutes and then the phone just hangs up on the person randomly. The other 80% of the time the phone call goes correctly without hitch after this point.
I've found the following thread here that seems to outline my problem exactly: https://productforums.google.com/forum/#!topic/nexus/SaoZyWfkX94;context-place=forum/nexus
Add me to the list of people whose Bluetooth connectivity has suffered after upgrading from Lollipop to Marshmallow (on my Nexus 5). All was working perfectly in my 2015 Honda Accord, connecting to their HandsFreeLink software to make and receive calls. Now calls do go out, but you cannot hear the phone "ringing", and the radio comes back on again until the call is completed, when you suddenly hear the caller say "hello." Also many instances of poor call connection (unusable screeching sounds or very garbled speech). Did everything except reset to factory settings: wiped cache, reset the phone to the car's bluetooth, etc. Waiting hopefully for the 6.0.1 update to save the day….
Click to expand...
Click to collapse
Is anyone else experiencing this? How can I fix?
Me too
I have the same exact problem with my kia.
It is really annoying, can anyone help?
arsenik13 said:
I have flashed the official google images. MRA58K and MRA58R - both have the following issue:
I'll outline it logistically:
* I connect bluetooth to my 2013 Honda Accord
* When I dial a phone number from the nexus device OR using the car's bluetooth menu the bluetooth disconnects
* the phone continues to call the person
* after the person answers the phone and says hello a few times, the phone reconnects to bluetooth
* the phone call goes on as normal. At this point I have a 20% rate of failure where the phone call connects for a few minutes and then the phone just hangs up on the person randomly. The other 80% of the time the phone call goes correctly without hitch after this point.
I've found the following thread here that seems to outline my problem exactly: https://productforums.google.com/forum/#!topic/nexus/SaoZyWfkX94;context-place=forum/nexus
Is anyone else experiencing this? How can I fix?
Click to expand...
Click to collapse
I am also having almost the exact same issue.
I have yet to find a working solution. In the meantime, all I could do is go back to 5.1.1.
Also, M developer preview 1, 2 and 3 all work fine.
poncespr said:
I am also having almost the exact same issue.
I have yet to find a working solution. In the meantime, all I could do is go back to 5.1.1.
Also, M developer preview 1, 2 and 3 all work fine.
Click to expand...
Click to collapse
This must be a very widespread issue, I wonder why it's not getting any coverage here?
arsenik13 said:
This must be a very widespread issue, I wonder why it's not getting any coverage here?
Click to expand...
Click to collapse
OK. I finally got it working right.
I will tell you what I did in case you want to try it, if you are comfortable flashing a CM13 alpha.
While on 5.1.1 lmy48y, I flashed CM13 Alpha cm-13.0-20151124-UNOFFICIAL found here.
And gapps found here.
I kept the 5.1.1 bootloader and radio, and have not had any issues.
I am using Elemental kernel 3.06.
And I also formatted my device to remove encryption.
So far so good. No more weird behavior on my CRV blue-tooth.
I don't think that the kernel makes a difference, but that is what I am using and have not tried with any others after getting this working combination.
Hope this helps.
6.0.1 Stock fixes bluetooth issues.
Just in case anyone is still having these issues. I just downloaded and installed stock 6.0.1 and everything is now working great.
Cheers.
poncespr said:
Just in case anyone is still having these issues. I just downloaded and installed stock 6.0.1 and everything is now working great.
Cheers.
Click to expand...
Click to collapse
I am running stock 6.0.1 and my bluetooth doesn't work. At all. Annoying.
6.0.1 introduced a slew of other Bluetooth issues. Because it links phone and BT accessory volume levels (before this they were separate,) this causes some headsets to be stuck on max volume no matter what you do. Rendered my LG HBS-730 useless.
Am getting 100% bluesleep / msm_serial_ds wakelocks on various ROMs using a pebble watch. This makes using Bluetooth and my watch unusable due to radically reduced battery. Any ideas?
Sent from my Nexus 6 using Tapatalk
Chahk said:
6.0.1 introduced a slew of other Bluetooth issues. Because it links phone and BT accessory volume levels (before this they were separate,) this causes some headsets to be stuck on max volume no matter what you do. Rendered my LG HBS-730 useless.
Click to expand...
Click to collapse
True. I had not noticed the bluetooth volume bug, but it is there.
They finally fixed it in N Preview. Hopefully this rolls out as part of monthly security updates for 6.0.1 as well.
I am on N, and Since Marshmallow, i have not been able to pair in my Acura TL bluetooth. Same issue with N. Every other phone before or after has or is working well with my Acura TL. So I KNOW it's not the Vehicle, and I know it's not the phone. I can pair my Nexus 6 with a bluetooth speaker, a bluetooth headset, a NON factory bluetooth DIN radio, and a Bluetooth NON factory In vehicle hands free (GROM) without any issues. Somehow, there is a slight change that is affecting CERTAIN devices prior to marshmallow, that is present now.
I have read about activating the GPS, and trying to sync the phone to the Acura Bluetooth... this has made NO difference. Bluetooth will eventually timeout.
Hello everyone,
I'm having major issues with my Nexus 6 over the past 3 weeks or so.
I've had this phone for almost 2 full years now and love it, however, over the past 3 weeks the bluetooth function keeps turning off when I reboot my phone every night.
It NEVER did this in the past 2 years. Only the last 3 weeks. It seems to be some sort of battery saving feature, I would presume.
What drives me nuts, is I always like to have my bluetooth on, since I get in my truck and it auto connects to my GMC IntelliLink (which is also a problem).
So does anyone know why, all of a sudden, after reboot, bluetooth defaults to off and I have to manually turn it on every time? My Nexus 6 has been flawless up until now.
I've looked everywhere for an "auto start" option for bluetooth, but cannot find one. I have ZERO idea how this happened all of a sudden. I've been running the same ROM since last February with no problems (ROM screenshot attached).
As for my bluetooth truck problem, that started today. All of a sudden "phone audio" will not let me select the box, only "Media Audio" and "Contact Sharing" boxes are selected. Thus my Pandora plays over bluetooth, but my phone calls will not.
Also my Bose Quiet Comfort headphones used to connect perfectly with my Nexus 6, now I'm at work and I notice if I turn the headphones off, then come back and turn on, it'll say "connected to Nexus 6", but the sound is playing through the phone instead of the headphones, even though the bluetooth connection has been established.
Again, this is only over the last few weeks.
Any help would be greatly appreciated.
I'm willing to update to a new ROM or do a wipe, I just tend to live by the motto "if it ain't broke, don't fix it"........ except now it is broke and I want to fix it.
Thank you-
Paste a logcat here. A dev could take a look and help you out.
or
Backup your stuff and do a clean install of a new pure nexus or whatever rom, if it's still present after that, maybe it's just your battery starts to dying after 2 years.
Edit: I'm using crdroid as daily driver and have no bt issues
So glad you posted this, I'm having the same issue! After either a restart or just a period of time my Bluetooth turns to disabled. It is especially frustrating as I have it connected to my watch, which allows me to unlock with smart unlock. When the Bluetooth is disabled, I have to punch my pin in.
I am on stock 7.1.1, February update. I am rooted and flashed the Echo Permissions Fix. I was going to flash stock again this morning, but decided to check here first for a solution. I am just happy to know that it's not just me.
That being said, like @MVLJR, I recently flashed PureNexus ROM and that for me is when this began. I flashed back to stock via flashall, but it has not stopped the problem. Could it be a PureNexus thing?
As we have PureNexus somewhat in common, I am doing some searching on that page. I had previously posted there about it, but I don't think I ever got a response. Someone mentions it on Page 3417, I'll keep reading to see if I find a solution.
My post, by the way, is on page 3420.
I had a problem like this on Pure Nexus and flashed back to stock (N6F26R) to see if the problem goes away...
Previously on stock (release before N6F26R) and never had an issue. I use Bluetooth with a watch, fitness band and sometimes my Wife's Ford...
Sent from my Nexus 6 using Tapatalk
@muiriddin, did the problem go away for you? Because I flashed back to stock and the problem persists.
@MVLJR, I suspect that the problem is Android Wear 2.0 on our phones. Do you have a smart watch?
Edit: On the PureNexus forum, people without Android Wear are also experiencing it. So back to the drawing board. I still do not think it is your ROM.
Reading this thread reminded me of something I dealt with a while back, I don't know if this will do it for all of you, but I figured I'd post this. I screenshotted a reddit thread that fixed the problem for me. I can't remember if what I experienced was the same as all of you, and I am not having the problem now. But I hope this helps. Please see the attached screenshot.
I don't have an android watch, but I do have a fitbit and don't have any problems with it.
A little update, I cleared my Bluetooth cache and changed the name of my device, which seems to have helped.
My Bose headphones now autoconnect like before.
However, my Bluetooth still shuts off after reboot. My GMC Intellilink still won't let me select "Phone Audio" either.
I think I'm going to flash a new ROM this week, which sucks because I've grown attached to the Pure Nexus ROM.
Can someone show me how to post a logcat?
Thanks
This (and similar) bluetooth issues have been reported on the nougat product pages. It's not unique to PureNexus or the Nexus 6.
Reports are that 7.1.2 (beta) fixes the issue on devices that have access to it. Hopefully a fix comes down the pipe for the Nexus 6 as well, as I have some of the same issues.
Similar posts can be found on the nexus6 and googlepixel subreddit pages.
My question is, what prompted this?
I've had the same ROM for a year, no OTA updates. Had to be an app update, correct?
No other way to explain how it worked for a year, now problems all over the place
You've been using the same ROM, but updating the version of the ROM, correct?
And the ROM updates are based on updates made to Android by Google.
So if a bug makes it into Nougat, it will (generally) make it into the modified ROM as well.
Incorrect, I've been on the same version of Pure Nexus since last February, screen shot in original post
I take it the fix I posted didn't help? I was really hopeful that it was the same issue and that would fix it up.
I haven't tried it yet, at work right now, I'll give it a shot later.
I'll update my findings.
Thanks
Will keep my fingers crossed. One thing to note, when doing that fix, it *will* wipe your bluetooth auto-pair devices. So don't fret if nothing automatically connects afterwards. You have to repair everything.
It is not a new problem, there are many threads in the Q&A forum if you search. Here is one:
https://forum.xda-developers.com/nexus-6/help/bluetooth-off-reason-pattern-t3435436
(there are more links and suggested workarounds in that thread from me)
That said, installing the AW 2.0 DP 4 totally solved my BT disconnects from my Huawei watch and LG stereo headset.
The changelog on the latest Huawei AW 1.5 mentions BT issues, but I have not tried it.
AW 2.0 official is supposed to start rolling out OTA tomorrow, so we shall see. (finners crossed tite )
I'm on Jan 21 PN 7.1.1, latest AW app. I have no suggestions of those having issues with no Android Wear, but there are threads here with suggested workarounds that solved this for many of us before, you might want to check them.
@Morpherios and @MVLJR
I don't know if it's of any note, but one of the actions I attempted in trying to fix mine was to reset all network settings via the "More" option in Wireless & Networks settings (I backed up wifi settings in advance). That's essentially a nuking of all network settings, including wifi, cell, and bluetooth. It did not resolve my issue.
@Pkt_Lnt seems to be indicating that with updated AW on his watch, the disconnects are not happening. How the software on the watch (as opposed to the AW app on the phone) would be causing bluetooth to crash, I'm not sure. But it's not outside the realm of possibility.
larrysteeze said:
@Pkt_Lnt seems to be indicating that with updated AW on his watch, the disconnects are not happening.
Click to expand...
Click to collapse
My words were / are different than that:
AW 2.0 DP 4 totally solved my BT disconnects
That means they do NOT happen any more, since Dec 11, 2016 when I installed AW OS 2.0 DP4 was released and I installed it on my watch. Not. One. Disconnect. None. Nada. Zero. Zip. Zilch. Nein.. :victory:
BT devices communicate both directions. The watch CAN control the phone, and was turning off BT. It was obvious when it happened, when my headphones prompt "Out of Range, trying to connect" (I came to hate hate that voice prompt )
I would immediately open the AW app on the phone at disconnect and was prompted to turn on BT because it was off.
@Pkt_Lnt I completely agree that it BT communication is two-way...I stated that it's not outside the realm of possibility because there are a number of factors that could do it, including the phone receiving a message it simply doesn't know what to do with and causing a fault. This could explain my bluetooth share crash messages that I received on occasion.
It's encouraging to know that it's fixed with AW 2.0 for you. I hope it carries through to me when I get the update. If the OTA doesn't drop tomorrow, I may have to flash the DP as well.