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?
Being a sprint user myself upon the camera development this morning (still needs work but something is better than nothing)
i have come to realize that Eclair and Android on The Sprint HTC Touch
is very close to complete.
only things left that i know of are:
bluetooth audio (music playback)
video recording
Video playback
but i want to see if anybody else has found anything.
thoughtlesskyle said:
Being a sprint user myself upon the camera development this morning (still needs work but something is better than nothing)
i have come to realize that Eclair and Android on The Sprint HTC Touch
is very close to complete.
only things left that i know of are:
bluetooth audio
and video recording
but i want to see if anybody else has found anything.
Click to expand...
Click to collapse
bt audio works for calls.
Yea I know it is but not for audio routing so you can't listen to music through it
Video playback is also still not working.
I'm running the super eclair from incubus
Well the camera on mine still isn't working after the update. It loads but when i take a picture it crashes.
I'm very new to this so I'm trying to learn as I go.
but also I'm not receiving text for some reason, everything else seems to be working fairly well.
diabolicalnyc said:
I'm running the super eclair from incubus
Well the camera on mine still isn't working after the update. It loads but when i take a picture it crashes.
I'm very new to this so I'm trying to learn as I go.
but also I'm not receiving text for some reason, everything else seems to be working fairly well.
Click to expand...
Click to collapse
Text messaging is a known issue with super eclair. It works on other builds.
cool now that the camera is working does everyone have MMS setup to send?
acegolfer said:
Text messaging is a known issue with super eclair. It works on other builds.
Click to expand...
Click to collapse
He mentioned it was.
maybe i'll try another one. I really like his version but text is pretty important.
My phone specifies that its a Tmobile my touch now after upgrading it to Myn’s Warm Donut Android 1.6 with Prodical Sun Theme. Also I get a MMI code issue. What should I do to fix this.
Tsvallette said:
My phone specifies that its a Tmobile my touch now after upgrading it to Myn’s Warm Donut Android 1.6 with Prodical Sun Theme. Also I get a MMI code issue. What should I do to fix this.
Click to expand...
Click to collapse
its always going to say my touch 3G, thats just what he has the build set to recognize the phone as, it shouldn't cause any problems
i have no clue what an MMI code is so im not sure
This is day two of going back to this phone and I dont have any data connection. In two more days according to Sprint I should have 100 percent access to whats on my account. I hope I have data connection soon. If I dont have it back by then I will be posting it here. I miss my data connection!
Tsvallette said:
This is day two of going back to this phone and I dont have any data connection. In two more days according to Sprint I should have 100 percent access to whats on my account. I hope I have data connection soon. If I dont have it back by then I will be posting it here. I miss my data connection!
Click to expand...
Click to collapse
what happened there, was your Data working before you flashed to android?
I have the Vogue and the Titan. I switched from my Vogue to the Titan due to some minor issues and now my Titan is doing the same thing. Before switching back to my Vogue I flashed the rom with the Android, liked it alot and then called up sprint and did a switch back to my newly improved Vogue. According to the sprint rep it will take upto 4 days for all provisioning to be complete. As of right now I have it all working except for the data. My phone doesnt even show a data connection and when it tries to access something via internet it says "You don't have a network connection. Ths could be a temporary problem or your SIM card may not be provisioned for data services. Please try again when you are connected. If it continues, call Customer Care."
Ohh yah, *2 and *4 doesnt work. I was going to call them today to see if they could speed things up but cant call them this way.
Tsvallette said:
I have the Vogue and the Titan. I switched from my Vogue to the Titan due to some minor issues and now my Titan is doing the same thing. Before switching back to my Vogue I flashed the rom with the Android, liked it alot and then called up sprint and did a switch back to my newly improved Vogue. According to the sprint rep it will take upto 4 days for all provisioning to be complete. As of right now I have it all working except for the data. My phone doesnt even show a data connection and when it tries to access something via internet it says "You don't have a network connection. Ths could be a temporary problem or your SIM card may not be provisioned for data services. Please try again when you are connected. If it continues, call Customer Care."
Ohh yah, *2 and *4 doesnt work. I was going to call them today to see if they could speed things up but cant call them this way.
Click to expand...
Click to collapse
yea so i have an easy fix to your problem, flash back to windows mobile once its back an loaded access the internet, it should do some sort of dialing #777 thing then flash back to android after IE loads any sort of web page.
you should be perfectly provisioned right now the max it usually takes is like 24 hours, although i do still have nightmares from my days as a service tech provisioning those sprint Direct Connect phones
but yea so if you were in android before you activated the phone thats why you dont have data
Thank you. I relized that I would probable needed to do this but I didnt want to if there was a easier way to resolve this issue. I recall that I needed to do this when I went for stock rom to nfs 6.5 and had no internet as well. I then needed to load the 6.3 rom and then back to 6.5. This time I reverted to the 6.3 nfs rom and straight to this one.
okay so I am super new to this...i have a sprint vogue and i am running the zen-hero files from my sd card...I cannot get my caller id to work to save my life...it shows just numbers when someone calls me please help...
Hi! I hope to write in the right area, but if not I ask someone to move my post in the right one.
Now I have a HTC Diamond device, but I've to change it for a GalaxyS or an iPhone4.
I would like to buy a GalaxyS device, but I read many posts about bugs, lags, gps problems, so I wonder if it is a great choice this GalaxyS.
I like android and all the development opportunities around it (thanks to XDA), but it seems to be not so stable yet...
I flashed many ROMS on my Diamond in the past, so it's not a problem to do the same for my GalaxyS, but problems are fixed? The GPS works fine? Maybe not...
Maybe with Froyo 2.2?
iPhone4 is not so open as an Android device, but it's a very stable device!
What do you think about?
coming from a winmo background you're gonna love the galaxy s! its miles ahead in terms of refinements, polish and brilliant integration. The GPS problems are nothing so critical...its more of a sw fix im guessing. I live in India, and i have ZERO problems on my GPS....i feel the bug is something country/carrier specific.
there are many things to love and obsess with the galaxy s....go get yourself one, you sure wont regret it
While I'd love to echo what dreamtheater39 has said, I can't. It's a brilliant phone, but after having mine for just under a month, it's starting to lag like crazy, and in the last two days I've had a ton of dropped calls and the phone has switched itself off/crashed three times in the last few hours resulting in data loss because the power button doesn't respond (forcing me to hard-reset the phone).
All I can say is that, if you do get one, have an open mind. And make sure you don't get locked into a lengthy contract in case things do go awry.
same here GPS working great since day 1
http://forum.xda-developers.com/showthread.php?t=775450
Maybe I got a lemon
Maybe I got a lemon but I can not stand the i9000. I have 4 bugs that drive me crazy.
1. Market Place hangs at starting download. I have to do a factory reset to download an update an app.
2. GPS just stops working or it puts you on a different street when you are using navigation. The worst part is then it has to recalculate the directions twice, once for the wrong location and then again for the correct location, which is a real pain in the pocketbook when you are rooming.
3. Receives invalided cert from a hotspot connects the 1st time then never again. So I cannot use my hotspot at work, my old iphone connects no problem.
4. Does not always switch between wifi and mobile network. Have to go to airplane mode and back to get 3G network. (I tried changing the wifi sleep settings)
Mmmm...so maybe it's a good device, but I understand that who had an iPhone before it seems to be a step backward...is it?
Is anyone else having issues using the app HeyTell? The only ROM i can get it to work properly on is the stock AT&T 2.1, it doesn't even work on the stock 2.2 update. Basically on stock 2.1 I can send and receive messages perfectly without missing a message or having to close the app. If I update to 2.2 or flash a custom ROM, I can send about 2 messages and then it stops sending or receiving, I have to close the app and then try to send the message again. Once I open the app again, whatever the person sent to me is lost and they have to send it again.
Just putting this out there, I have emailed the developer and they are stating that they have no issues. I don't know what else to try, I have cleared the app's cache, uninstalled and reinstalled, I am out of ideas.
I've never even heard of this app before... I'll install it now and tell you how it goes.
EDIT: Okay, I obviously have no friends on this at the moment... But I've been clicking around the app and it seems fine? I'm using Paragon RC6 right now. The GPS/Map component seems to be working fine anyway... I can't really send a voice clip or message through it (no-one to send it to).
EDIT2: Okay, I somehow sent a voiceclip/message to myself and I've recorded it, sent it, and then received it fine. I'll keep playing around with this a little bit further in the morning.
I really appreciate it, it will work at first, and then just stop sending and receving, the little sending icon just spins and spins...then you have to force close it and then start it again, then it works for a few messages and then stops again.
I'm having the same problem with the HeyTell app. It's pretty much hit or miss for me, sometimes it works good for a while, sometimes it sends blank messages. I have a ton of friends using this app on iPhones or other Android devices and they aren't having problems at all.
I have emailed the developer and he states that it works perfectly for him on his phone, whether or not that is true, I am not sure.
Not trying to thread jack but for some reason my hey tell doesn't get messages on time. I'll be next to a buddy and I'll get a message that he sent hours ago. Does anyone else have this issue? I just have the 2.2 froyo update, no custom roms.
I thought for sure HeyTell would work on Official 2.2 as well but I have the same issue your stating. Like I said though, the developer states he has no issues...I am not sure what is going to happen.
HeyTell Support
Are you sure you contacted HeyTell support? I don't have any record of sending a "works for me" answer on a report like this...drop me another email to refresh my memory at [email protected] if you can - thanks in advance!
So! We're aware of an issue on the Galaxy S series phones (Fascinate, Epic, Captivate, Vibrant) introduced by 2.2 firmware (Samsung only, 2.2 makes HeyTell better on other phones). Symptoms appear to be spotty network reporting, media player issues (inconsistent record behavior), and the OS killing HeyTell during screen dims.
We're currently working hard to find a workaround for affected users (and trying to get more info from Samsung), but in the meantime, if you could do us a favor and email us your firmware revision number and any logs you have related to the behavior, we'd greatly appreciate it!
Since I had the issue with Stock 2.2 and not with Stock 2.1 I am running Stock 2.1 until there is a fix. If your asking me for logs I cannot help you there unless I put 2.2 on my phone. i am currently running HeyTell version 181, I am willing to load 2.2 and work with you and get you information, just let me know. I love this app, but my phone is kinda laggy and slow running 2.1 and I want to be running 2.2.
I"m also using HeyTell on 2.2 and having quite a bit of troubles. I'd be happy to send you logs if you could explain to me how to do so. Thanks!
Just a little update, I finally got tired of stock 2.1 last night and decided to try out MIUI. I was pleased to find that after sending more than 10 messages back and forth, HeyTell has not failed yet.... I will be testing all day at work today, I am not sure if they updated the app or if something in MIUI allows it to work. I just thought I would update those few of you that have had the same problem as me.
Everything is still working fine with HeyTell, I am running MIUI Beta 6 and HeyTell is working perfectly. I did notice an update to from the market, I am hoping that could be a fix for other cutom Roms and Stock 2.2.
As MIUI has no samsung crap in it, it should work fine, since it seems to be a samsung issue. Runs fine on CM7 as well.
We put a workaround into builds 1.1.3 -- that fixed it for stock, but didn't catch all of the custom ROMs, so we spun 1.1.4 - give that a whirl and it should work. If anyone runs into this issue again, shoot us an email with your model number (Menu > Profile > Email Support sends this to us, so that may be the fastest method, but also don't forget to include a description of the issue you hit).
Oh sweet so HeyTell should be working fine now with stock 2.2? I will test it now, thanks alot!
Ever since I downloaded the update the app works great! Thanks!
Hey Tell Message Queue Issues
I've been having a problem for a while now where message don't come in automatically, as if they're caught up in the queue somehow. I have to exit HeyTell multiple times, manually click on the message, hit the stop and play buttons, or multiple combinations of all of these just to get a single message to play sometimes. I'm using a Samsung SGS3 with Synergy. Any way to fix this issue? Thanks much!
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.