As per phonearena.com Mate 9 is starting to get update to Oreo
https://www.phonearena.com/news/Unlocked-Huawei-Mate-9-receiving-Android-8.0-Oreo-in-the-US_id102104
Wait is over
Android Central is reporting it too. Anyone get it?
I have checked mine several times and nothing yet
it's approved for update in Firmware Finder
Edit: nevermind, jumped the gun...only approved if you check without the imei.
As someone who has been on the beta test for this for the past 2 months, it's pretty disappointing that they're releasing this. It has issues that they haven't fixed. If .360 is the final version, I'll have to see if I can get rolled back to Nougat.
dscline said:
As someone who has been on the beta test for this for the past 2 months, it's pretty disappointing that they're releasing this. It has issues that they haven't fixed. If .360 is the final version, I'll have to see if I can get rolled back to Nougat.
Click to expand...
Click to collapse
What issues are you having?
audioman42 said:
What issues are you having?
Click to expand...
Click to collapse
I stream Google Play Music via Bluetooth in my car. Until Oreo, when I turn off my car, or switch to another audio source, streaming from the phone is paused. Next time I start up the car, it resumes. Now, I have about a 50% chance of it resuming Google Play Music. It will randomly decide to instead use the built in music app to play something stored on the phone (one of the demo songs that came with the phone, or the one track I have saved on the SD card). I’m constantly having to go to Google Play Music & re-start whatever I was playing.
I’m also having unreliable visual notifications, particularly text messages (I use Textra). I do at least sometimes get the audio ding, but more often than not, no flashing light, and no badge on the shortcut. So if I’m not within earshot of the phone when I get a txt, I don’t know I received one (I can’t say for certain audio notifications always work, but I know at least sometimes I’ve heard the ding, but visually the phone doesn’t indicate it).
The above two issues are new since the Oreo update. Another issue I have that also existed in Nougat: the phone has difficulty managing multiple simultaneous Bluetooth connections. My car requires two connections: one for phone calls, and another to a 3rd party streaming adapter. If I have my Huawei Watch on/already connected to the phone when I get in the car, the two car connections won’t connect, at least not both of them. I have to toggle Bluetooth off/on on the phone to get all three connected at the same time. If I don’t have my watch on, there’s a better chance that both will connect, but at least one will. I didn’t seem to have these issues with my previous Note 3, but the Mate 9 seems to have a hard time reconnecting Bluetooth when there are multiple simultaneous connections involved. This issue is the one that caused me to join the beta, hoping to ensure it was fixed in the new software. Instead, it persists, and I gained a couple new ones.
dscline said:
I stream Google Play Music via Bluetooth in my car. Until Oreo, when I turn off my car, or switch to another audio source, streaming from the phone is paused. Next time I start up the car, it resumes. Now, I have about a 50% chance of it resuming Google Play Music. It will randomly decide to instead use the built in music app to play something stored on the phone (one of the demo songs that came with the phone, or the one track I have saved on the SD card). I’m constantly having to go to Google Play Music & re-start whatever I was playing.
I’m also having unreliable visual notifications, particularly text messages (I use Textra). I do at least sometimes get the audio ding, but more often than not, no flashing light, and no badge on the shortcut. So if I’m not within earshot of the phone when I get a txt, I don’t know I received one (I can’t say for certain audio notifications always work, but I know at least sometimes I’ve heard the ding, but visually the phone doesn’t indicate it).
The above two issues are new since the Oreo update. Another issue I have that also existed in Nougat: the phone has difficulty managing multiple simultaneous Bluetooth connections. My car requires two connections: one for phone calls, and another to a 3rd party streaming adapter. If I have my Huawei Watch on/already connected to the phone when I get in the car, the two car connections won’t connect, at least not both of them. I have to toggle Bluetooth off/on on the phone to get all three connected at the same time. If I don’t have my watch on, there’s a better chance that both will connect, but at least one will. I didn’t seem to have these issues with my previous Note 3, but the Mate 9 seems to have a hard time reconnecting Bluetooth when there are multiple simultaneous connections involved. This issue is the one that caused me to join the beta, hoping to ensure it was fixed in the new software. Instead, it persists, and I gained a couple new ones.
Click to expand...
Click to collapse
Same here with bluetooth inconsistencies when connected to my car. I have resynched several times and sometimes it helps for a short while and other times no improvement. Sometimes I can control songs and other times not. Sometimes it shows songs and other times it shows connecting. Sometimes it shows the correct name of song and other times it freezes on a song title that is long gone. Even when deleting and resynching my phone, an old song title is displayed and not the same as being played. Total bummer as I use bluetooth music every time I get into my car. On recent update (360) which appears to be the same one they are releasing as OTA.
hmmm, this must be a states model thing, my huawei mate 9 works perfectly on oreo...i dont use textra, use normal default...anyway is one of the reason i dont buy or use states systems on no phone...i always buy the international phones(orignal phone) the company put out...they better and receive the update in a timely manner...sorry, but state phones suck! i havent bought one in over at least 10 years....
Still waiting. To be honest though, it's not even Oreo I want, I just want the dang security updates. April 2017 is wayyy too old.
dscline said:
I stream Google Play Music via Bluetooth in my car. Until Oreo, when I turn off my car, or switch to another audio source, streaming from the phone is paused. Next time I start up the car, it resumes. Now, I have about a 50% chance of it resuming Google Play Music. It will randomly decide to instead use the built in music app to play something stored on the phone (one of the demo songs that came with the phone, or the one track I have saved on the SD card). I’m constantly having to go to Google Play Music & re-start whatever I was playing.
I’m also having unreliable visual notifications, particularly text messages (I use Textra). I do at least sometimes get the audio ding, but more often than not, no flashing light, and no badge on the shortcut. So if I’m not within earshot of the phone when I get a txt, I don’t know I received one (I can’t say for certain audio notifications always work, but I know at least sometimes I’ve heard the ding, but visually the phone doesn’t indicate it).
The above two issues are new since the Oreo update. Another issue I have that also existed in Nougat: the phone has difficulty managing multiple simultaneous Bluetooth connections. My car requires two connections: one for phone calls, and another to a 3rd party streaming adapter. If I have my Huawei Watch on/already connected to the phone when I get in the car, the two car connections won’t connect, at least not both of them. I have to toggle Bluetooth off/on on the phone to get all three connected at the same time. If I don’t have my watch on, there’s a better chance that both will connect, but at least one will. I didn’t seem to have these issues with my previous Note 3, but the Mate 9 seems to have a hard time reconnecting Bluetooth when there are multiple simultaneous connections involved. This issue is the one that caused me to join the beta, hoping to ensure it was fixed in the new software. Instead, it persists, and I gained a couple new ones.
Click to expand...
Click to collapse
I've noticed similar Bluetooth problems. I stream in my car pretty often and through headphones at work, and at times I won't be able to skip songs via the receiver/headset. Since a reboot always fixes it, I've been doing preemptive reboots as I walk to my car in the morning to circumvent the issue.
I've had zero issues with Textra. If anything, it's working even better now than it did before - all of my MMS sending issues are gone. Apparently, though, this was less of a Huawei problem and more of a Nougat problem.
cross1989 said:
hmmm, this must be a states model thing, my huawei mate 9 works perfectly on oreo...i dont use textra, use normal default...anyway is one of the reason i dont buy or use states systems on no phone...i always buy the international phones(orignal phone) the company put out...they better and receive the update in a timely manner...sorry, but state phones suck! i havent bought one in over at least 10 years....
Click to expand...
Click to collapse
Which region did you rebrand to? I was on 432 running a custom ROM for a while, but went back to 567 thinking that would solve my MMS sending issues. I want to rebrand, but I've heard that rebranded phones don't receive OTA updates because the IMEI doesn't match the region.
Thanks
I did not rebrand any thing, as I stated I don't buy state side phones, I buy original unlock phones directly from company (Amazon).. I have international version, MHA-L29C185... Now on oreo from Ota... Yea you loose Ota on those rebranding systems most of those require to unlock bootloader and twrp... That alter the system... If you want a good Huawei phone, buy international or China version off Amazon, yes both work in the states.
Just got my ota update today
Can someone who got Ota update check to see if any of the files on the FF app are giving an imei approval?
Mine still isn't and I didn't get Ota yet, so if it does for you and u got the Ota it may shed some light on whether the server shown on FF is directly linked to Ota files...
I just got the OTA update...downloading it now
kullum79 said:
I just got the OTA update...downloading it now
Click to expand...
Click to collapse
Where are you located??
shae23 said:
Where are you located??
Click to expand...
Click to collapse
I am in Chicago Central Standard Time... playing with the camera as we speak....
kullum79 said:
I am in Chicago Central Standard Time... playing with the camera as we speak....
Click to expand...
Click to collapse
Lool same location, no update, man Huawei is funny, oh well, guess it'll get here in its own time
It doesn't matter about the area it's being done in Bach's by imei .
---------- Post added at 09:11 AM ---------- Previous post was at 09:02 AM ----------
U can download it in ff but when it finishes download and install it won't verify because the it's has the imei in the download bricked one phone so I will wait for the ota I called huwaei to c about unbricking and the told me the date and time of the forced update voided the warranty
I got my Oreo update just a few hours ago, bought off Amazon, in KY, on T-Mobile
Oreo Update
I got my OTA update late yesterday. Haven't had it long enough to see if the battery life is better.
Related
I've got a Kenwood BT-200 bluetooth handsfree car kit and have found the following issues with it;
1. Everytime a call is completed, the phone book downloads all over again and takes over 10 minutes, preventing making follow on calls till complete.
2. The received and dialed calls list doesn't work
3. Cannot initiate a call from the head unit unless the phone screen is on (was working perfectly on previous HTC Touch Cruise).
4. Unable to initiate voice dialing on Phone using Microsoft Voice Command whereas with previous HF kits it was as simple as pressing and holding the call button.
Anyone else use the same Touch Pro - BT200 combination? Or experience similar problems with other HF kits?
I have Pioneer BT unit. I can not connect, but I installed Hands-Free Config from JETware Mobile Software and it solved all my problems. There are many setting options which should help you...
Hi Pritman,
I just went through the same thing after upgrading to the Touch Pro from the Dopod 838Pro (Hermes).
There's a firmware update available for the KCA-BT200 which may well fix your issues (certainly did mine).
I created a post about this earlier today (didn't see your post here).
http://forum.xda-developers.com/showthread.php?t=440494
The firmware flash is very easy to do. You will just need a laptop with a bluetooth adaptor.
Codenix.
Kenwood have released another update.
See my other post at http://forum.xda-developers.com/showthread.php?t=440494 for details.
Codenix.
Wow, never thought I would fine anyone else with the combination of Kenwood DNX-7100, KCA-BT200 AND the touch pro. I am having similar issues.
DNX-7100 with BT100 worked fine with touch pro.
"upgraded" to BT200, and I have nothing but headaches.
I have tried two different BT200, and both have been flaky.
I have tried BT200 firmware 1.60 and 1.70, and both have been flaky.
My problem is similar to the ones you folks have been experiencing, mainly it is constantly downloading, and the interface is super sluggish when downloading. I can retrieve a name and phone number from the BT200's memory, but when I call out it will say downloading and do nothing. Sometimes it won't "pair" with the phone automatically unless I manually select my phone from the DNX-7100, and sometimes it will just drop the connection. I used the BT100 for about a year, and it was solid 95% of the time. I am running stock Telus rom, btw. I have also played around with the dip switch on the BT-200. From the shipped manual, DNX-7100 belongs in group F, which is off, off, on for dip switch 1, 2, 3. But when I searched online, some of Kenwood's info listed the DNX-7100 under group G, which has dip switch off, on, off, just to add to the confusion. I have also tried removing the "wireless stereo" profile as well as the "serial port" profile, but that fixed nothing. Lastly, just to kick me when I'm down, when it list the numbers, sometimes it list them as first name, then last name, but sometimes it list it as last name then first. This is super irritating as you can't be sure where anyone is listed ..... so far my experience with the BT200 has been nothing but horrible. I am on the verge of flashing my touch pro to a cooked ROM just to see if it is due to the stock Telus rom's bluetooth (I went back to stock as the juggalo rom I used became corrupt after a few weeks).
So, did you guys finally find a solution that worked 100% of the time?
Idea
Hi Guys, I'm glad there are more people out there with my combination.
Upgrading the BT 200 to 1.70 has improved things significantly but not as good as it would be with another handset like a Nokia N95. The download delay and sluggishness still exist.
I recall when I paired the TP, a notice came up on the TP that the BT 200 is requesting access to the phonebook or contacts and prompted me to allow or deny. I'm wondering what would happen if I deny? I do know that when I first paired the N95 with the older firmware, it wouldn't syncronise the contacts and I had to manually send the contacts to the BT 200. If this can be done with the TP, it may eliminate the constant downloading, perhaps.
Anyone else willing to try this. I may not be able to do this till later this weekend so if any of you do manage to test this before me, please post the results.
Good luck!
If you don't give it access to the phonebook, I suspect it can't download your phonebook automatically, and you would have to manually push the phonebook over, which defeats the purpose of the BT-200, effectively making it a BT-100. After trying a 2nd BT-200 for 3 days, I have given up and chalked up the BT-200 as extremely flaky, and is easily the worst purchase I have ever made as:
1) Half the time it won't pair with the phone automatically
2) The other half when it does pair, you can't dial out as half time time again when you want to make it call, it decides to do a download from your phone instead (never mind that it already "downloaded" when it paired already. Half x half = quarter.
3) Half the time when it does manage to make it call, it magically drops the bluetooth pairing and drops the call.
If you're keeping track, we are at half x half x half, which is 0.125, or this damn thing only works 12.5% of the time. This is not a time saver, nor a gadget of convenience/safety. It is the ultimate source of anxiety, danger (as you're trying to get the damn thing to work), and a big disappointment. Kenwood, shame on you for putting out such flaky products, and especially for not fixing it (look at the first post, it is from Oct 08).
I am going to return both of my BT-200 to Clutchfield, and am going back to my 99% stable BT-100. BT-100 actually is not as horrible with the TP as TP runs WinMo 6.1, which lets you push multiple phone book contacts at once (not like the older WinMo where you had to push contacts ONE BY ONE!!!). The only caveat with the BT-100 is if you need to delete or modify any contacts, you can't, and you have to delete all the entries for a particular phone and repair and push all contacts again, which takes 1 minute now as oppose to half an hour with pre-WinMo 6.1. When I buy a HU next time, I don't think I will consider Kenwood again due to:
1) Flaky software/interface.
2) Poor documentation.
3) Poor service support. Kenwood Canada actually NEVER REPLIED. I only received the auto-gen email notification indicating they received my email. Clutchfield Canada has been very supportive, and I will pay more to buy from them in the future solely due to their strong customer support.
Hi Johnnysks,
As far as the Touch Pro is concerned, I understand your frustration and totally support your argument.
On the other hand, I have tested the BT-200 with a Nokia 96 & my previous Touch Cruise, works like a dream! I've had good responses from Kenwood UK but whenever I contact HTC, I alway get vague responses, which to me suggests that Kenwood must have been making the effort but keep getting let down by HTC. Ultimately the BT-200 works with majority of the handsets out there.
I will still keep trying for a solution though as I really do like the TP and the BT-200!
I have no doubts the BT-200 works with other phones, and I know my TP works with my BT-100 flawlessly. I also know from prior personal dealings with Kenwood Canada's technical support that:
1) They're rude, have a bad attitude, and unprofessional (as my first inquiry for a different product from a year ago was met with a reply that was condescending, unhelpful, and was not even in proper English). I'll be more than happy to dig up my old email for you if you have any doubts.
2) They're not responsive. It's been over a week, and they never replied to my current inquiry regarding the BT-200 (funny. They used to be rude and unprofessional. Now they're missing in action)
Perhaps Kenwood USA, Kenwood UK, or Kenwood Japan are doing an awesome job. However, I can only go with what I have personally experienced.
Anyone find a fix for this? I have the same problems with my DNX8120. Tried Jetware, no luck, I would try BTRestore, but it won't work with .net 3. My biggest complaint is that even if it is connected via bluetooth, it won't start a call from th eheadset unless the phone is not in standby. Next biggest issue is that it drops the connection after hanging up from a call.
Very f*&%*g annoying!
FYI, worked with 2 different ETEN's
Well I just upgraded to new Oreo and guess what? I can't use my Bluetooth headset anymore (Blue Tiger Elite). The audio gets distorted or breaking up. Failing to connect or disconnect to/from the phone. Was working fine before update. Tinkering Bluetooth settings in developer mode didn't help since they will stay unchanged after you open the menu again.
Have anyone encountered same problem?
When im paired up with the stereo in my work truck i noticed a pop every now and then.
stefilie said:
Well I just upgraded to new Oreo and guess what? I can't use my Bluetooth headset anymore (Blue Tiger Elite). The audio gets distorted or breaking up. Failing to connect or disconnect to/from the phone. Was working fine before update. Tinkering Bluetooth settings in developer mode didn't help since they will stay unchanged after you open the menu again.
Have anyone encountered same problem?
Click to expand...
Click to collapse
Audio streaming on Nougat for me was perfect all the time, now since my Oreo update I've experienced constant stuttering and/or growly distortion for a moment at least every ten seconds. Also 'Settings' keeps closing whenever I'm accessing any of my apps when changing permissions for example. It couldn't even pull up my app list, so I've done a backup and deleted at least 300 of my apps, and only now things are slightly better. I don't understand why everything is lagging so much now when before the update, all was perfect.. Help?
ScottOverly said:
Audio streaming on Nougat for me was perfect all the time, now since my Oreo update I've experienced constant stuttering and/or growly distortion for a moment at least every ten seconds. Also 'Settings' keeps closing whenever I'm accessing any of my apps when changing permissions for example. It couldn't even pull up my app list, so I've done a backup and deleted at least 300 of my apps, and only now things are slightly better. I don't understand why everything is lagging so much now when before the update, all was perfect.. Help?
Click to expand...
Click to collapse
Try factory reset, it worked for me. Good luck!
Yes, I'm having the same issue with bluetooth connection and the same Blue Tiger Elite. Just got off the phone with Verizon tech person he is thinking my headset is old enough technology that it won't stay connected.
Steve Phillips
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
MJFox78 said:
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
Click to expand...
Click to collapse
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
nabbed said:
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
Click to expand...
Click to collapse
if Google's code is garbage, I suggest you stop using android and start making your own good code!
nabbed said:
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
Click to expand...
Click to collapse
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
kewlest22 said:
if Google's code is garbage, I suggest you stop using android and start making your own good code!
Click to expand...
Click to collapse
I had a Pixel XL for over a year. Only kept it for Project FI. Bug ridden POS.
Sold it for half going price just so I could feel clean again.
Even if Samsung *used* to have sluggish Touchwiz in the past, at least it didn't have deal breaking bugs.
Don't even have to make my own code - some XDA roms had fixed this bug, as opposed to Google.
MJFox78 said:
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
Click to expand...
Click to collapse
I am almost positive that if you had a somewhat similar problem on a Note 8, it's probably Google's fault.
I don't really use the 2 BT phone functionality for more than 30 min on average, but I've never had any problems on Note 7, GS6 or GS9, or even on a Pixel pre 7.0.2 android, when this bug was first introduced.
After 7.0.2, bluetooth stuff just broke everywhere. This bug, constant disconnects and reconnects, for some people music skips, for some doesn't even work, BT UI in Settings just crashing etc.
It's like Google replaced their BT programmer with a monkey at that point, or even a monkey's nephew.
So just because you cannot use 2 Bluetooth devices simultaneously to make phone calls, it's a deal breaker??? Lmao please please please go back to Samsung so we don't have to hear the whining anymore. Good luck with those bootloaders
hi i love my op6 but there is one annoying thing Bluetooth auto connect ..my phone is connected to my tic watch pro with no problems but when i get in my car that has a alpine halo 9 i have to connect it manually ,also my company car is continually searching for my phone..i have never had this problem with any of the phones i have had [i have had every flagship phone that has come out .IOS or android.] any body shed some light on this for me thanks
nobody got the same problem then
Relax, someone will come eventually... And no, I don't have.
westentertainer said:
hi i love my op6 but there is one annoying thing Bluetooth auto connect ..my phone is connected to my tic watch pro with no problems but when i get in my car that has a alpine halo 9 i have to connect it manually ,also my company car is continually searching for my phone..i have never had this problem with any of the phones i have had [i have had every flagship phone that has come out .IOS or android.] any body shed some light on this for me thanks
Click to expand...
Click to collapse
Everyone who has a smart watch that can make BT phone calls has this problem.
The car kit connects as "Connected (no phone)."
This bug was introduced by Google with Pixel XL after 7.0.2 update, and they never fixed it.
Individual manufacturers fix this in their own Android skins except Google, Xaiomi and now Oneplus.
BTW, the bug was not present in 5.1.5. OOS, and was introduced in 5.1.6 or 5.1.7 (I skipped the 5.1.6 update.) So, it's likely that OP simply and lazily copied Google code at that point.
If you want to get rid of this annoyance, one possible way is to disable Phone Audio option in the watch BT properties on the phone.
Of course, you could also flash 5.1.5.
nabbed said:
Everyone who has a smart watch that can make BT phone calls has this problem.
The car kit connects as "Connected (no phone)."
This bug was introduced by Google with Pixel XL after 7.0.2 update, and they never fixed it.
Individual manufacturers fix this in their own Android skins except Google, Xaiomi and now Oneplus.
BTW, the bug was not present in 5.1.5. OOS, and was introduced in 5.1.6 or 5.1.7 (I skipped the 5.1.6 update.) So, it's likely that OP simply and lazily copied Google code at that point.
If you want to get rid of this annoyance, one possible way is to disable Phone Audio option in the watch BT properties on the phone.
Of course, you could also flash 5.1.5.
Click to expand...
Click to collapse
Thank you. What would I loose disabling phone audio on watch ?
westentertainer said:
Thank you. What would I loose disabling phone audio on watch ?
Click to expand...
Click to collapse
Then you couldn't talk and listen to phone calls on the watch. You could initiate and receive the phone calls on the watch, but the audio would automatically go to the phone instead.
nabbed said:
Then you couldn't talk and listen to phone calls on the watch. You could initiate and receive the phone calls on the watch, but the audio would automatically go to the phone instead.
Click to expand...
Click to collapse
Thank you
Back a couple of hours, I had a chat and a call with the support Huawei stuff. Among other things about the update process of the Huawei Watch 2 (BT).
What the support staff told me, that there is no way to manually update (trigger an update by the enduser). "The system" of Huawei decides, when a serial number will get the updates. And it can take up to 8 weeks, until all "the system" has enrolled all the updates to the watch. When the watch will be factory resetted, all this will happen again.
In all my experience as a software developer, architect and as a normal enduser, this "process" was completely unknown by me. I would tend to say, that it is the worst user experience ever.
Today, I got the update to Wear OS 1.7 (from 1.6). As of supports statement, there are several updates in the line until Wear OS 2.0.
My question relates to this: What are your experiences (from recent buyers)? How long does it took for you to finally get a working watch?
PS: "working watch"... I also report an issue, that the Bluetooth internet tethering does not work as the watch did not define this scope in the Bluetooth handshake. From the phones view, the watch just cannot do tethering at all. Support staff told me, that is be fixed with Wear OS 2.0. So I will nearly have useless watch for up to 8 weeks until I get the 2.0 update. Yay I am not a couch potato, I do perform activities outside my WiFi network
I didnt quite get what your actual question is but as far as i know if you want internet connection and your watch is bt variant you can either connect through wifi or your phone's internet through bluetooth
And i geuss thats the case with every other smartwatch and OSs
Same issue here
Just got my watch this morning and it's stuck at wear os 1.7. When I search for updates on the watch it tells me there's no updates.
I've also updated all apps in the play store
Could anyone else shed light on this or is it just a matter of time?
Thanks in advance
Kianush said:
I didnt quite get what your actual question is...
Click to expand...
Click to collapse
How long did it took for you until you watch was usable (the 2.0 update)?
Outside WiFi zone, I cannot use my watch because I have to stick with 1.7 for as long as Huawei's system won't give me the update. So no internet over Bluetooth until I finally get the 2.0 update.
I have connection with bluetooth.
burnersk said:
How long did it took for you until you watch was usable (the 2.0 update)?
Outside WiFi zone, I cannot use my watch because I have to stick with 1.7 for as long as Huawei's system won't give me the update. So no internet over Bluetooth until I finally get the 2.0 update.
Click to expand...
Click to collapse
I do have connection via Bluetooth, my only qualm is the fact its not updating despiste the fact it should.
Weird it doesn't even find updates for the watch.
M3th0s said:
I do have connection via Bluetooth, my only qualm is the fact its not updating despiste the fact it should.
Weird it doesn't even find updates for the watch.
Click to expand...
Click to collapse
You have a Bluetooth internet connection or just a Bluetooth connection?
For example, if you explicitly turn off you watches WiFi, will Google Maps or Google Music (streaming, not downloaded files) work?
What is you Wear OS version?
burnersk said:
You have a Bluetooth internet connection or just a Bluetooth connection?
For example, if you explicitly turn off you watches WiFi, will Google Maps or Google Music (streaming, not downloaded files) work?
What is you Wear OS version?
Click to expand...
Click to collapse
Now i undrestand your issue.
I will give u a clear answer here
Huawei watch 2 hasnt recieved the wear os 2.0 update yet, and its 1.7 right now
Also from the day one i got this watch (one year ago which was many updates ago) this watch had no problem connecting to internet through bluetooth (as i mentioned in my first post here)
You just need to connect the watch to your phone and then turn on you phone's data connection which then the watch will use it and u will have internet connection (google maps/play store/ system update etc)
And also if u turn on vpn on your phone it will be also effected on the watch.
burnersk said:
You have a Bluetooth internet connection or just a Bluetooth connection?
For example, if you explicitly turn off you watches WiFi, will Google Maps or Google Music (streaming, not downloaded files) work?
What is you Wear OS version?
Click to expand...
Click to collapse
Yup, no issues whatsoever accessing data outside a wifi network
---------- Post added at 10:05 PM ---------- Previous post was at 10:05 PM ----------
Kianush said:
Now i undrestand your issue.
I will give u a clear answer here
Huawei watch 2 hasnt recieved the wear os 2.0 update yet, and its 1.7 right now
Also from the day one i got this watch (one year ago which was many updates ago) this watch had no problem connecting to internet through bluetooth (as i mentioned in my first post here)
You just need to connect the watch to your phone and then turn on you phone's data connection which then the watch will use it and u will have internet connection (google maps/play store/ system update etc)
And also if u turn on vpn on your phone it will be also effected on the watch.
Click to expand...
Click to collapse
Thanks for the clear explanation. Do we know when we can expect 2.0?
M3th0s said:
Thanks for the clear explanation. Do we know when we can expect 2.0?
Click to expand...
Click to collapse
No we dont, there is another topic regarding this matter titled "Wear os update"
So it seems to me that the Huawei Support ist knowingly lying to potential buyers.
The told me that the 2.0 update was already released and 2.1 is in planning (as announced by Google). And that there are several updates between 1.7 and 2.0 that my watch will pick up (become pushed) within the next 8 weeks.
What I see from your responses is that there were no updates in the past after 1.7..
And Huawei's update server decides, when to roll out (pushes) updates to the watch. Manual searches for updates will always be "already on newest release" because Huawei's update server don't work that way. At least this is what the support told me.
So to sum up... It seems that particular my watch have a Bluetooth issue since it does not announce tethering capabilities with the handshake. That is why, I cannot use my watch. Support stated, that this issue is known and already fixed with 2.0..
I get really angry with Huawei's support. You guys have pointed out so many points, that the support didn't told the truth. I had 3 contacts with different support staff. So this is not the accident of one individual.
burnersk said:
So it seems to me that the Huawei Support ist knowingly lying to potential buyers.
The told me that the 2.0 update was already released and 2.1 is in planning (as announced by Google). And that there are several updates between 1.7 and 2.0 that my watch will pick up (become pushed) within the next 8 weeks.
What I see from your responses is that there were no updates in the past after 1.7..
And Huawei's update server decides, when to roll out (pushes) updates to the watch. Manual searches for updates will always be "already on newest release" because Huawei's update server don't work that way. At least this is what the support told me.
So to sum up... It seems that particular my watch have a Bluetooth issue since it does not announce tethering capabilities with the handshake. That is why, I cannot use my watch. Support stated, that this issue is known and already fixed with 2.0..
I get really angry with Huawei's support. You guys have pointed out so many points, that the support didn't told the truth. I had 3 contacts with different support staff. So this is not the accident of one individual.
Click to expand...
Click to collapse
Yeah it's sad.
I was hoping wear os was going to be a different story than android and updates would be pretty consistent across watches.
I am now considering going back to my gear s3 frontier tyzen watch until such a time as Google decides to release a watch (if they ever do).
Say what you want from apple but at least they're consistent (I know they only have to cater for their devices) and watch os looks damn good and seems like the better watch experience you can have atm.
i agree, the updates for the watch are like they are for their phones, - non-existent - as usual they make good hardware but it's backed up by poor support and updates from them.
I just wish Google would hurry and release a smartwatch so can swap over.
burnersk said:
So it seems to me that the Huawei Support ist knowingly lying to potential buyers.
The told me that the 2.0 update was already released and 2.1 is in planning (as announced by Google). And that there are several updates between 1.7 and 2.0 that my watch will pick up (become pushed) within the next 8 weeks.
Click to expand...
Click to collapse
Watch 2 Sport LTE. Had 1.6, Did factory reset sunday morning. Received 2.1 today.
Yup update seems to have rolled out today
Got my update in Germany for BT a few minutes ago
Watch 2 BT with 2.1 update also for me ? watch is finally working ?
LTE version in Spain received now 2.1