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?
first i bought a sim-free kaiser - had problems getting bluetooth to work when wifi was connected - got so pissed off with it i sent the unit back - now ive got another unit (a vario 3 this time) and i am having the exact same bloody problem - what the hell is going on? cant this device do bluetooth and wifi at the same time? i want to stream music over wifi to my BT stereo headset FGS
Any equipment wether it is a phone, laptop or PC will have somewhere in its manual that recommends WiFi and Bluetooth are not used together. Both systems run on very close frequencies and cause interference to each other.
The problem is enhanced by the proximity of the Tx and Rx of each system within such a small unit as a phone or PDA.
I wanted to do the same as you and found BT falling off due to the high rate of packet retries on each so reverted to wired headphones.
Add a cellphone TX and Rx to this also and you have one NOISEY set of close by systems.
i have heard reports of people using both together in harmony on the kaiser - and a lot of people who own other devices (ie htc universal, sony ericson, p990i etc) do not seem to have this problem
i appreciate that bluetooth and wifi share the same frequency bandwidth and this will inevitably cause packet loss - but not nuke it all together! afaik bluetooth hops 1600 times a second (or smt like that) all over the spectrum, where as wifi tends to stay within a certain band?
Lately, I've had a little trouble with using WiFi with A2DP on my Jabra BT8010. Periodically, I get dropouts on the sound, which seem to be associated with WiFi disconnects -- I lose the WiFi momentarily, then as it tries to re-connect to the AP, I lose sound. Not a range issue -- this happens even when I'm right on top of the AP.
I haven't had any problems with WiFi & BT in handsfree or HID modes, just A2DP.
guess im just really unlucky :/
3waygeek said:
I haven't had any problems with WiFi & BT in handsfree or HID modes, just A2DP.
Click to expand...
Click to collapse
A2DP uses 200-400 kbps, while handsfree / HID only a fraction of it.
fusi said:
guess im just really unlucky :/
Click to expand...
Click to collapse
You're not alone. There are 5 reports of this in the HTC Wiki, and I've run into it myself. If I'm using wifi and I answer a call with my bluetooth headset, WiFi simply stops working. Likewise, if I'm using the headset and I try to switch on WiFi, the device can see the network, but can't connect and will eventually drop the network configuration and prompt me for the WPA passphrase.
Edit: I tried upgrading to the 1.27.12.17 radio ROM, but no joy.
I'm having the same problem, but I'm using the ROM that the Kaiser came with. Has anyone tried using Dutty's ROM or something?
Maxim726X said:
I'm having the same problem, but I'm using the ROM that the Kaiser came with. Has anyone tried using Dutty's ROM or something?
Click to expand...
Click to collapse
Do us all a favor and give HTC a call and report the problem. I have nothing against the cooked ROMs, but just like the video drivers, it would be nice if there was something official from HTC:
+1 866 449 8358
Just wanted to say that I too have the same Bluetooth + Wifi problem. When I have Wifi on, it's nearly impossible for me to connect to my PC with a Bluetooth connection. I have only had some luck when I established the bluetooth connection and then turn on Wifi.
HTC says they're trying to reproduce the issue and will get back to me in the next day or two. Again, I strongly encourage you to give them a call.
sinanju said:
Do us all a favor and give HTC a call and report the problem. I have nothing against the cooked ROMs, but just like the video drivers, it would be nice if there was something official from HTC:
+1 866 449 8358
Click to expand...
Click to collapse
Just called them, and the woman on the phone basically told me not to expect any updates within the next few months, if ever. What the hell is that about? To that I responded 'so basically you're saying that you don't support the device'... She kind of dodged the question, but it seems to be that way. We're kinda on our own... Which is unfair, but this verification removes any remorse I would have about hacking the **** out of my phone. So now that it is verified that we're being hung out to dry, do any of the ROMs address this issue?
As will all other customer service organizations, if you don't like the answer, call back.
Getting them to reproduce and recognize the issue is the first battle.
Smart Answer mate. I have an SDA and haven't noticed that problem so far, I'll try to see if its been happening un noticed. Anyone know where i can find A2DP profile for the SDAII ?
Maxim726X said:
I'm having the same problem, but I'm using the ROM that the Kaiser came with. Has anyone tried using Dutty's ROM or something?
Click to expand...
Click to collapse
Im using Dutty's ROM and have the same problem.
Has this issue been resolved with the new Firmware, to anyone's knowledge?
The recently released AT&T ROM does not fix the issue. Support told me they have sent a report back to engineering. I'm going to give them 'til the end of the week before I call them back.
Any Updates or fix regarding Wifi and Bluetooth interference on the HTC?
Let me add to my own finding...
I have 3 laptops and 1 PC that is on the WiFi. If my HTC Kaiser craps out using the Wifi with bluetooth. It takes the WHOLE entire Wifi network down( for about 30sec to 1min). I can see all my laptops and PC dropping Wifi and trying to reconnect.
Hello All,
I am running Dutty's Dual Touch v1.1 Rom with radio 1.27.12.17 on my ATT Tilt. The device is brand new, 6 days old now. Whenever I make a phone call, I can hear the other person perfectly. However I have consistently heard complaints from the person on the other end of the line. They complain that they can't hear me, saying I sound muffled or far away. In some cases they can't hear me at all, and I would have to call the other person back. Sometimes they can hear me perfectly, and sometimes they cant. I'd say its 50/50, good and bad. What could be the problem?
Thanks,
thehin
I have similar problem. Sometimes people just can't hear me well, but I always can hear everyone perfectly. During the normal call it happens not very often, but the loudspeaker is almost unusable, in most cases none can here what I speak.
I have a good GSM coverage in my area, my old Nokia 6680 produced a good call quality.
I have standard ROM 1.56.405.5 (08/28/07), Radio: 1.27.12.11
I think, it is probably something in the Kaiser's hardware, because I’ve heard about similar problems from different people with totally different ROMs and radios.
Big Problem
This is a huge problem for me, it's somewhat embarrassing when people can't hear you, and you are forced to call back or call from another phone. I have full service, and have no problems with data connections. Could it be due to a constant connection????
Is your data connection active when you're on the phone? If so, try turning them off and then making calls. I think I read somewhere (or made up in my head) that the 3G connection messes with your call connection.
I expiernece the problem in both scenarios. I turned off 3G through comm manager, and it still happens. I even disabled data all together and it still happened. :-(!!!
met3ora said:
Is your data connection active when you're on the phone? If so, try turning them off and then making calls. I think I read somewhere (or made up in my head) that the 3G connection messes with your call connection.
Click to expand...
Click to collapse
I think it is nothing to do with the data connection, mine is mostly off, but the problem remains. Theres some cases the sound just floating, according to recipients and they just cant hear what I am saying.
If anyone DOES NOT experience the same problems, can you please be kind enough to share your ROM version, and radio version?
Thanks
Has nothing to do with ROM type. The Mic on the HTC8925 / Tilt / kaiser is located at bottom right-hand edge of the device. Although your voice sound travels through all of the bottom parts of the device, the most sensitive spot is the small hole next to the mini USB plug in. If you are holding the phone and covering the bottom part of the phone with your palm, then the person on the other side of the call will not hear you well.
To test, start HTC recorder or Resco Recorder program and while tapping on various areas of the phone surface observe the behavior of the decibel meter on the Recording program. You will then discover the most sound sensitive spot of your device.
I will give that a try. However the other night when I was talking to someone, they claimed they couldn't hear me at all, and I was coming in and out. I checked my reception, full service. No data connection, no bluetooth, no wifi, no 3G, no GPS, no apps running. I then held the phone out and talked directly into the mic, he still could not hear me. I held the phone a little farther away, still no go. One person said I sounded like i was whispering off a mountain peak.
ARGGHH :-( I love this phone, but this is pretty annoying.
thehin said:
If anyone DOES NOT experience the same problems, can you please be kind enough to share your ROM version, and radio version?
Thanks
Click to expand...
Click to collapse
You mentioned you were running Dutty's Dual Touch v1.1 Rom with radio 1.27.12.17 on my ATT Tilt. Have you tried to flashed back to the original Rom to see if you still have the same problem?
thehin said:
I will give that a try. However the other night when I was talking to someone, they claimed they couldn't hear me at all, and I was coming in and out. I checked my reception, full service. No data connection, no bluetooth, no wifi, no 3G, no GPS, no apps running. I then held the phone out and talked directly into the mic, he still could not hear me. I held the phone a little farther away, still no go. One person said I sounded like i was whispering off a mountain peak.
ARGGHH :-( I love this phone, but this is pretty annoying.
Click to expand...
Click to collapse
LOL thats exactly how the Titan sounds through bluetooth, only it so happens to sound that way. on our side of the call.
Finally!
I'm so glad to find other people suffering the same problem.
I'm battling with Handtec & HTC to try and resolve this issue, it's driving me *and callers* mad.
I've been waiting 3 months for this to be resolved and Handtec have finally agreed to replace it... but if this is a common problem, a replacement isn't likely to resolve it. £440 is a lot of money for something you can only use 50% of the time.
I also has the same problem. People sometimes just told me that they hear nothing frommy side suddently for a few seconds.
The only way to "contain" it is using Bluetooth, this way so far I never found problem any more.
ROM: 1.56.708.3
Radio: 1.27.12.11
Well my At&t Tilt is stock, i mean i havent change any radio roms or what ever, and I have the same problem, sometimes people complaint they cant hearme, I know its very anoying, but on my case its not like a 50/50, its more 75/25 (25 they cant hear) this happend on the 2 o 3 first days I had the phone, After that or the people I call can hear me, or the problem persist and they dont tell me.
I see the microphone its on the bottom of the phone, I think its because of that, when people complain I simply put it on speaker and talk directly to the microphone (but I dont know if this works ) hehe
Good morning and Happy New Year
I have had the same problem but after upgrading to Dutty's Dual Touch v2 Rom and radio 1.27.12.32 the sound is excellent, tested it yesterday and both on speaker and off speaker is very clear. My advice if you do not want to move to Dutty's v2 then at least flash the Radio to .32
Good luck
I don't have the problem. I'm using a TyTN II version with stock ROM. Got it when it came out so a few months ago.
I have the same problem, and mine is stock standard. Also tried it with and woth out 3G, blue tooth ect ect ect ect same problem.
Any Advice Anyone.
On another site, the issue was discussed and some one suggested the issue was caused by a .dll file conflict that routs or attempts to rout calls to HTC recorder program. It was also suggested to remove any recording software from the device or disable its call recording in the settings and see what happens.
I have been trying to look for a solution for that problem, Finally I decided to let go and stop using the loudspeaker option
I am trying to research this on other related forums and will get back to you if I am lucky.....
I got the same problem, but the person on the other end of the line can't hear me, with or without the loudspeaker option!!
Has anybody found a fix for this?
So i got a diamond for about a month now, and im pretty happy with it except for one problem which absolutly drives me crazy, and pretty much makes it suck as a mobile phone.
Tried searching the forum but can't see anything about this, my only guess is it might have something todo with 3G weak reception.
i still don't know when exactly this happens, under what conditions exactly.
but basically this happens a few times a day.
The problem:
I will get/make a call while having signal.
I click accept
as it is trying to connect the call suddenly all reception is lost and i lose my signal.
basically it fails to connect the call
a second later i will have reception again.
if now i get called again, it will usually give me the same problem.
I have absolutly no idea how to fix this.
tried reflashing the official rom, but it didn't work.
i really hope this is an easy fix, as i really like this phone so far, but seems my wizard worked better as phone.
aRnonymous said:
So i got a diamond for about a month now, and im pretty happy with it except for one problem which absolutly drives me crazy, and pretty much makes it suck as a mobile phone.
Tried searching the forum but can't see anything about this, my only guess is it might have something todo with 3G weak reception.
i still don't know when exactly this happens, under what conditions exactly.
but basically this happens a few times a day.
The problem:
I will get/make a call while having signal.
I click accept
as it is trying to connect the call suddenly all reception is lost and i lose my signal.
basically it fails to connect the call
a second later i will have reception again.
if now i get called again, it will usually give me the same problem.
I have absolutly no idea how to fix this.
tried reflashing the official rom, but it didn't work.
i really hope this is an easy fix, as i really like this phone so far, but seems my wizard worked better as phone.
Click to expand...
Click to collapse
try to flash latest radio
if no improvement ... looks like a hardware problem -> service center
MEDBEDb said:
try to flash latest radio
if no improvement ... looks like a hardware problem -> service center
Click to expand...
Click to collapse
Well i flashed the official rom from HTC website, i assume it has the newest radio rom.
its got radio version 1.00.25.05.
although i see there is 1.00.25.06, but .05 is recommended in the thread
aRnonymous said:
Well i flashed the official rom from HTC website, i assume it has the newest radio rom.
its got radio version 1.00.25.05.
although i see there is 1.00.25.06, but .05 is recommended in the thread
Click to expand...
Click to collapse
Hey aRnonymous,
It seems your radio is (1.00.25.05) quite outdated.....try this Thread:
http://forum.xda-developers.com/showthread.php?t=432770
You will find many radios which you can use. Than you can see if your problem will be solved...probably a bad flash from your current radio is causing the problem you prescribed....
Good luck fella en let us know about your progress....
also...look @ my signature...this radio is working great (at least, in my opinion, you have to try many radios)
Regards
Jeroen
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.