I'm about to get my first hearing aids. Four years after cancer diagnosis my hearing loss is moderately severe, thanks to ototoxic Cisplatin chemo.
Modern hearing aids link to devices via Bluetooth Low Energy (BTle) protocol adopted by hearing aid manufacturers. Apple developed and patented a BTle protocol they call MFI (Made for iPhone.) Almost all hearing aids support it.
Android does not have that Apple licensed protocol, so Android users need third device that links to the phone and links to the hearing aids and passes phone calls or music streaming to the HAs. Most third party devices have batteries that last 4-6 hours, and cost $3-$600 in addition to the $4-6K for hearing aids. Getting an iPhone is the solution, seems most HA users have iPhones (I found an HA forum with good users and info on the web.)
There is information that Android P will support direct connection to hearing aids.
https://www.xda-developers.com/google-pixel-2-bluetooth-hearing-aids-android-p/
Reading the DP Program Timeline, DP4 should be a Release Candidate with final APIs in place for testing. https://developer.android.com/preview/overview
Looking forward to an answer regarding this. I would love to update the article to confirm it works.
I also buyed an iPhone in order to test the connectivity to my aids but I'm a bit dissapointed of iOS.
Looking forward to get some information about the new hearing aid connectivity features in Android P - can somebody report if they are already integrated the the developer preview builds?
Hope that not only Pixel devices will support them, because I'm actually very happy with the OnePlus devices. Maybe there would be a way to enable them on non-Pixel devices.
Regards,
dachserl
So is the belief that Android P will allow non-A2DP hearing aids to stream audio/music? My dad has non-A2DP hearings aids (has to use a separate transmitter between the hearing aids and the phone to be able to stream music) and I have DP4 installed, so I can probably test this but I'd like to confirm first if my understanding is correct.
Hi,
yes, streaming audio, making phone calls like with Made for iPhone (MFI) aids.
See this article: https://www.xda-developers.com/android-getting-support-for-bluetooth-hearing-aids/amp/
Would bei very nice if you and your dad could test and report if it is already part of the DP4 version.
renndachserl said:
Would bei very nice if you and your dad could test and report if it is already part of the DP4 version.
Click to expand...
Click to collapse
It is not visible or useable in DP4.
Do you know any date for the final release?
renndachserl said:
Do you know any date for the final release?
Click to expand...
Click to collapse
I use Oticon OPN HA's and am on DP4 using a Pixel XL. I don't see anything in the menu that suggests HA support is now available. I don't know when the final release of P will be.
I got my hearing aids 2 years ago and had to buy an iphone because only apple had the low power bluetooth which the OPN's use. My understanding is that this tech is proprietary to apple. Two developments since then. One is Oticon released a version of it's Oticon ON software for android. It doesn't allow streaming but will allow you to change programs and volume on the HA's. This spring Oticon released its "ConnectClip" device, about the size of a match book, which connects regular bluetooth to the low power bluetooth used by the HA's. You can pair your pixel to the connect clip and it will act as an interface and stream and manage phone calls. The other advantage with the connect clip is that it will work with any bluetooth device, i.e. laptop, tablet, etc. I paid $150 for it.
Hope this helps.
renndachserl said:
Do you know any date for the final release?
Click to expand...
Click to collapse
Did you read my first post?
Hint - second link -> click it and read <-
STraver said:
I use Oticon OPN HA's and am on DP4 using a Pixel XL. I don't see anything in the menu that suggests HA support is now available.
Click to expand...
Click to collapse
Did you see the first link in my first post? It has proof that P shows HA support, but it is hidden code for now.
Pkt_Lnt said:
Did you see the first link in my first post? It has proof that P shows HA support, but it is hidden code for now.
Click to expand...
Click to collapse
No I didn't but I'll check it out. My Dr. always said Android would offer support at some point.
Pkt_Lnt said:
I'm about to get my first hearing aids. Four years after cancer diagnosis my hearing loss is moderately severe, thanks to ototoxic Cisplatin chemo.
Modern hearing aids link to devices via Bluetooth Low Energy (BTle) protocol adopted by hearing aid manufacturers. Apple developed and patented a BTle protocol they call MFI (Made for iPhone.) Almost all hearing aids support it.
Android does not have that Apple licensed protocol, so Android users need third device that links to the phone and links to the hearing aids and passes phone calls or music streaming to the HAs. Most third party devices have batteries that last 4-6 hours, and cost $3-$600 in addition to the $4-6K for hearing aids. Getting an iPhone is the solution, seems most HA users have iPhones (I found an HA forum with good users and info on the web.)
There is information that Android P will support direct connection to hearing aids.
https://www.xda-developers.com/google-pixel-2-bluetooth-hearing-aids-android-p/
Reading the DP Program Timeline, DP4 should be a Release Candidate with final APIs in place for testing. https://developer.android.com/preview/overview
Click to expand...
Click to collapse
I would wait till DP 5 which should come out in first week of August. I also wear a hearing aid that works well with Iphone and have a dongle for the android. Its a pita!
I have the ReSound Hearing Aid.
I've got my dad installing DP4 now. I'll let you know probably either tonight or tomorrow whether HA streaming support works or not.
Update: DP4 installed on Pixel 2. Phonak HAs were already paired but saw no additional option for music streaming (still only Phone and Contacts options). Tried YouTube any way but audio still came through the phone instead of HA. Went to Developer Options and didn't see anything related in there. Unpaired/forgot the HAs, re-paired but still to no avail.
Thoughts? Do you think they just haven't implemented it in DP4 and maybe it'll be in the final?
Just throwing this out there for consideration, when Google enables HA support in DP5 or full version of P, wouldn't we be waiting on the HA manufactures for firmware updates to the HA's themselves. My thought is that the HA's that have a made for iphone designation or even just a generic bluetooth ability, it's the HA firmware that enables the features.
I just received my first set of HA's, Oticon OPN 2 miniRITE, and I'm looking at getting the Oticon ConnectClip to give me the ability to stream. Oticon could take years to implement the android features into their firmware.
What are your thoughts? Firmware updates needed??
I sure hope Google helps us out with Android P. I have used an iphone with my widex hearing aids for about a year now... sucks. Soooo ready to get back to Android.
---------- Post added at 10:37 PM ---------- Previous post was at 10:28 PM ----------
Meandering Wanderer said:
Just throwing this out there for consideration, when Google enables HA support in DP5 or full version of P, wouldn't we be waiting on the HA manufactures for firmware updates to the HA's themselves. My thought is that the HA's that have a made for iphone designation or even just a generic bluetooth ability, it's the HA firmware that enables the features.
I just received my first set of HA's, Oticon OPN 2 miniRITE, and I'm looking at getting the Oticon ConnectClip to give me the ability to stream. Oticon could take years to implement the android features into their firmware.
What are your thoughts? Firmware updates needed??
Click to expand...
Click to collapse
I think the Manufactures would race to get that streaming technology to their hearing aids if Android comes through.
No change with DP5 either. No option in Bluetooth settings for media/audio/streaming.
s1dest3pnate said:
No change with DP5 either. No option in Bluetooth settings for media/audio/streaming.
Click to expand...
Click to collapse
Accessibility Settings? That is where I would expect them. Not that it matters really, but MFI support is in accessibility settings, as most HA users and Audiologists look for them on fitting setup.
Pkt_Lnt said:
Accessibility Settings? That is where I would expect them. Not that it matters really, but MFI support is in accessibility settings, as most HA users and Audiologists look for them on fitting setup.
Click to expand...
Click to collapse
There is nothing in accessibility settings. I tried to connect with the HA but it doesn't pickup the hearing aid. I sometimes get GN to pop up but doesn't connect
With P being out now, we need to check this again. My dad is out of town but I'll have him check when he gets back. Can anyone else check in the meantime?
s1dest3pnate said:
With P being out now, we need to check this again. My dad is out of town but I'll have him check when he gets back. Can anyone else check in the meantime?
Click to expand...
Click to collapse
I just tried with the resound gn. When trying to add the HA the GN shows up and able to connect but I can't hear any music in Spotify. Still missing code I believe.
Related
It sounds like Android Wear should be updated "soon" and we "should" have the speaker support all of us Huawei Watch owners have been longing for.
The next version of Android Wear is being tested on the Huawei Watch from the sounds of it. I would bet (hope) the Huawei Watch sees the update first! Here is a link to the article by Android Police:
http://www.androidpolice.com/2015/1...i-watch-and-it-finally-activates-the-speaker/
Anyone have any idea how to become a member of this testing group?
timdoggg said:
Anyone have any idea how to become a member of this testing group?
Click to expand...
Click to collapse
I'm looking into this now. Hopefully someone will upload the build for others to flash.
It would be nice to test the updated build, but I haven't seen any details about how to enroll in their beta program.
Rektifying said:
I'm looking into this now. Hopefully someone will upload the build for others to flash.
Click to expand...
Click to collapse
so just ask the guy and tell him how its done.
Does anyone know if your phone's android system needs to be at version 6 (Marshmallow) in order to use the new features on the watch, once android wear is updated¿
Sent from my SM-G928T using Tapatalk
wease said:
Does anyone know if your phone's android system needs to be at version 6 (Marshmallow) in order to use the new features on the watch, once android wear is updated¿
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
it doesnt.
I was just coming over to post the same article. This may make my regret of leaving the Gear S go away!
This is why I bought this watch, for speakerphone support on Wear 1.4 update.
The ZenWatch 2 also has a speaker and should also receive an update. No other Wear watches have a speaker.
I hope that this is not fake.
Sent from my SM-N920C using XDA Free mobile app
https://youtu.be/nvS4iPynkuM
XperiaLover said:
I hope that this is not fake.
Sent from my SM-N920C using XDA Free mobile app
Click to expand...
Click to collapse
https://youtu.be/nvS4iPynkuM
Yea this is not fake.
The LG Urbane 2 LTE came with this version and had the speaker enabled. The Urbane was supposed to release with it but was recalled due to some "hardware" issues.
I specifically bought the Huawei watch for this specific reason. Watch calls from inside my pool this summer, yes!
I WISH they would include an option for a keyboard. Yes it is not ideal or reasonable for normal use, but there are some times when it would be awesome. Options are always good, even if they are disabled by default. Even a T9 style old school input would be awesome.
player911 said:
Yea this is not fake.
The LG Urbane 2 LTE came with this version and had the speaker enabled. The Urbane was supposed to release with it but was recalled due to some "hardware" issues.
I specifically bought the Huawei watch for this specific reason. Watch calls from inside my pool this summer, yes!
I WISH they would include an option for a keyboard. Yes it is not ideal or reasonable for normal use, but there are some times when it would be awesome. Options are always good, even if they are disabled by default. Even a T9 style old school input would be awesome.
Click to expand...
Click to collapse
you should try quick for wear. its fantastic
The urbane 2 uses a new hexagon battery, wich caused problems.
Watch keyboard
Motawa88 said:
you should try quick for wear. its fantastic
The urbane 2 uses a new hexagon battery, wich caused problems.
Click to expand...
Click to collapse
What about Touch One keyboard for wear?
Rektifying said:
I'm looking into this now. H.
Click to expand...
Click to collapse
found anything?
player911 said:
Yea this is not fake.
The LG Urbane 2 LTE came with this version and had the speaker enabled. The Urbane was supposed to release with it but was recalled due to some "hardware" issues.
I specifically bought the Huawei watch for this specific reason. Watch calls from inside my pool this summer, yes!
I WISH they would include an option for a keyboard. Yes it is not ideal or reasonable for normal use, but there are some times when it would be awesome. Options are always good, even if they are disabled by default. Even a T9 style old school input would be awesome.
Click to expand...
Click to collapse
I use these two apps:
Mail for Android Wear
And
Messages for Android Wear
They are both replacement apps and are by the same Dev and have tiny keyboards that can be gotten used to!
They also have a web browser that works... well... It works...
I hope this is real. I'd love to have audio notifications on my H Watch.
Just waiting for someone to leak the firmware and confirm its true.
The guy who recieved the update didn't make a system dump before installing the update. This can only be done BEFORE installing. So there is no hope, we will get the update from him. Unless there is another user that copies the update.zip before installing.
On the other hand he won't be the only one to recieve this test build.
sputnik99 said:
The guy who recieved the update didn't make a system dump before installing the update. This can only be done BEFORE installing. So there is no hope, we will get the update from him. Unless there is another user that copies the update.zip before installing.
On the other hand he won't be the only one to recieve this test build.
Click to expand...
Click to collapse
This device has an unlocked bootloader and a redily available copy of twrp.
ANY ONE who got that update could distribute it with in just a few minutes...
1. Receive update.
2. Let it apply
3. Unlock bootloader
4. Flash TWRP
5. Back up entire system
6. Post to internet.
But to what you are saying... Yes, it is correct that you can only get the update.zip before install. However see my point about getting the entire deal.
Then anyone could restore his TWRP back up and have whatever it is he has...
Perhaps newer builds of the firmware will be more widely tested soon, and more likely to leak out.....
The thing that's bothering me is that perhaps we might not get this firmware at all, and that it might be for testing features in a new 2016 watch from Huawei.
figures crossed we WILL get a download of this soon
Good, forgive the English if it is bad, this translated with google. I do not know who the author is, but they have created this request at change.org for people to sign and send it to Sony. They are supposed to pressure and end up updating, as we believe meets the characteristics for it. I leave the link below in case someone wants to sign, I already sign, at least for trying not to be.
Put the www in front since being a new user does not let me put links.
change.org/p/sony-android-wear-2-on-sony-smartwatch-3?recruiter=679511093&utm_source=share_petition&utm_medium=twitter&utm_campaign=share_twitter_responsive
Done - Hopefully it helps!
https://www.change.org/p/sony-android-wear-2-on-sony-smartwatch-3
Hey, I created my own petition because i noticed you didn't have a letter attached just to let you know.
If mine doesn't start picking up too much steam, would you mind copying and pasting my letter into yours considering you don't have one? I think it makes a pretty compelling argument.
crunchybutternut said:
https://www.change.org/p/sony-android-wear-2-on-sony-smartwatch-3
Click to expand...
Click to collapse
I kinda doubt that Sony will listen, but I signed anyways. Still the only watch that lasts 2-3 days having features that are still up to date if someone would actually make the software to use the features properly. Still hoping on community development though, because also on the phones side, community developed software usually rocks more than anything stock.
Mikegrmn said:
I kinda doubt that Sony will listen, but I signed anyways. Still the only watch that lasts 2-3 days having features that are still up to date if someone would actually make the software to use the features properly. Still hoping on community development though, because also on the phones side, community developed software usually rocks more than anything stock.
Click to expand...
Click to collapse
agree :highfive:
me too.... think no hope from sony ...
sony always do the same thing
just in this case i can't understand ... sony always drop support from older devices to make people go and buy new ones...
but for sw3 there is no newer... and no why ??
I'm using Sony devices since December 2010 and every time the support was about to get dropped (we still don't know if it's confirmed the Smartwatch 3 WON'T get the update...) for any Sony device, there were always some heroes who tried to change the future with these petitions... and it never worked. Ever.
Just sayin'...
romcio47 said:
I'm using Sony devices since December 2010 and every time the support was about to get dropped (we still don't know if it's confirmed the Smartwatch 3 WON'T get the update...) for any Sony device, there were always some heroes who tried to change the future with these petitions... and it never worked. Ever.
Just sayin'...
Click to expand...
Click to collapse
Sony SmartWatch 3 is not compatible with 2.0.
It's said on the webpage of the watch.
alvid98 said:
Sony SmartWatch 3 is not compatible with 2.0.
It's said on the webpage of the watch.
Click to expand...
Click to collapse
It's a lie. Sony just did not want to update them.
Good news guys Looks like Google is giving us treats for the holiday season.
https://www.gsmarena.com/android_wear_devices_to_get_oreo_update_starting_today-news-28614.php
I'm guessing that every watch that is supported by AW2.0 will also be getting Oreo update. Yes, original Huawei watch is already beyond the 2 year support period but i don't think that the same rules goes for watches like it's usually the case with phones. Do you think original HW will be getting Oreo? I mean, we got new security update some days ago so it's still supported
I hope so,waiting for the update in a month.
In comments on articles about this, people have been reporting even the original Moto 360 is already getting this. I'm not sure the relationship between android version and android wear code but maybe it's pretty easy to merge the Oreo updates with the manufacturer's code now that they are on AW 2.0.
jdock said:
In comments on articles about this, people have been reporting even the original Moto 360 is already getting this. I'm not sure the relationship between android version and android wear code but maybe it's pretty easy to merge the Oreo updates with the manufacturer's code now that they are on AW 2.0.
Click to expand...
Click to collapse
The original moto 360 never even made it to android wear 2.0, so I highly doubt it is getting this update.
---------- Post added at 04:06 PM ---------- Previous post was at 04:03 PM ----------
Carmanen said:
Good news guys Looks like Google is giving us treats for the holiday season.
https://www.gsmarena.com/android_wear_devices_to_get_oreo_update_starting_today-news-28614.php
I'm guessing that every watch that is supported by AW2.0 will also be getting Oreo update. Yes, original Huawei watch is already beyond the 2 year support period but i don't think that the same rules goes for watches like it's usually the case with phones. Do you think original HW will be getting Oreo? I mean, we got new security update some days ago so it's still supported
Click to expand...
Click to collapse
The fact that we got a security update doesn't mean much. There were some pretty high profile vulnerabilities that needed patching (KRACK, etc.).
TheSt33v said:
The original moto 360 never even made it to android wear 2.0, so I highly doubt it is getting this update.
Click to expand...
Click to collapse
Oh sheesh... so that particular comment was meant as a joke that went right over my head!
How can i return to the stock rom and unroot the device? Or just to return to the stock with the ota updates. Thanks im on the negalite now...
vuoshino said:
How can i return to the stock rom and unroot the device? Or just to return to the stock with the ota updates. Thanks im on the negalite now...
Click to expand...
Click to collapse
Follow this video: https://youtu.be/qVrBEmi35-E
Files are on his server.
I accidentally installed AW 1.4 but received updates to update so now I'm on AW 2.6 A7.1.1 october patch
Don't expect it for this device.
Just read on an Android Wear g+ community that it is only coming for the Huawei watch 2.
Sent from my Pixel 2 XL
Yep we're screwed... Here's the official list
jeston said:
Yep we're screwed... Here's the official list
Click to expand...
Click to collapse
That sucks :/ I kinda knew this would happen eventhough i was optimistic and hopeful that Huawei Watch still gets it. So, it's finally the end of software support for our beloved original HW **** you, you ugly ass HW2!
Can someone explain this End Of Life situation though...? The Huawei Watch is STILL on sale via Huawei's direct website! Surely they shouldn't be selling a watch without providing the software support seriously!? I thought the deal was 2 years after the device goes on sale or 18 months after it stops being on sale (whichever is longer).
I think this statement needs to be reiterated to Huawei and Google.
Also I bought the watch thinking the support life would be alot longer than a phone... People don't buy +£200 watches for only 2 years usage.
This "policy" may have just made me decide that I'm not interested in Android Wear anymore... Even my Pixel 2 will have a longer shelf life!
EOL is not here yet, just no Oreo. This is near the bottom of the article.
Some of the watches dropped from support include the ASUS ZenWatch 2 and 3, the original Fossil Q Founder, the LG G Watch R/Urbane/Urbane LTE, the second-gen Moto 360 and 360 Sport, and the original Huawei Watch. Those watches will continue to get Android Wear updates (like the recent v2.6 update) through the Play Store, but the underlying Android version will be stuck on Nougat.
Click to expand...
Click to collapse
http://www.androidpolice.com/2017/12/09/google-announces-android-wear-watches-will-get-oreo-update/
Surely there will be a way to install as a custom Rom?
tboy2000 said:
Surely there will be a way to install as a custom Rom?
Click to expand...
Click to collapse
The only one for the HW1 is discontinued. The dev's watch died and Huawei gave him a watch 2. If another dev steps up, yes, but since there was only one and that dev does not plan to continue.
The thing is I only love the look of HV1 watch. Most stylish. There is no other V2 watch out there that comes close.
I have a Huawei Mate 10 running Oreo so it's a shame my watch won't match my phone.
Custom ROMs are our only hope now!
Voterx said:
Custom ROMs are our only hope now!
Click to expand...
Click to collapse
Well actually, just staying on wear 2 isn't a bad option, it still works wonderfully.
I agree. The more that Huawei Watch (1) is still officially on sale and is more expensive in stores than Huawei Watch 2.
I've made a post on their Swedish FB-site, here in Sweden it is still actively sold by two of Huawei's recommended resellers advertised at Huawei's site.
Can we figure out if the 18 months after sale claim is valid for Wear as well as regular Android? And was this formulated before or after the launch of the Watch?
I spoke to Huawei Technical Service. They do not have anywhere indicated that they provide support for 18 months from purchase / production. They claim that it depends on Google - not from them. They do not guarantee anything
It's a pity, because I have their P9 Plus smartphone and Watch 1 smartwatch and I think it makes the highest-class flagship.
Just checking to see if anyone with the One UI Beta has been able to test to see if Android Auto Wireless is working? If not this needs to be submitted to Samsung to get added.
We're on beta 4 and a couple of people have reported that it has been working since beta 2.
That's great news! Thanks for the info.
Can anyone confirm this? I check after every update on the S9+ with my AVH-W4400NEX and it hasn't worked yet.
where can i find this beta version and instructions? thanks
c-stam said:
Can anyone confirm this? I check after every update on the S9+ with my AVH-W4400NEX and it hasn't worked yet.
Click to expand...
Click to collapse
Nope. I'm on beta 4, have a kenwood with AA wireless and it's not working yet.
that green guy was dreaming or drinked......
Just got stable pie on my unlocked S9+. Notta.
It's frustrating, I bought the JVC head unit in July because it supposedly supported AA wireless with Oreo. I dug and found out AA wireless requires pie, so I waited it out.:
I have the stable Pie update on my US Unlocked Galaxy S9 and wireless android auto still doesn't work with my JVC KW-M845BW. Come on Google!
Could somebody explain the purpose of this?
As my head unit will screen mirror or i can install the app on the head-unit itself.
Think i maybe missing the point??
derekmski said:
I have the stable Pie update on my US Unlocked Galaxy S9 and wireless android auto still doesn't work with my JVC KW-M845BW. Come on Google!
Click to expand...
Click to collapse
Doesn't work for me either. Kenwood DNX995S. Works fine with Pixel 3 of course. I thought for sure Samsung would get it straightened out in the final pie. Grrrrrr. I don't understand. If the S10 doesn't have it it will be going back within the return period
Someone from Google on Google forums said they're working on enabling AA Wireless with non Google Pie phones. It sounds like Google has this intentionally disabled on the backend for non Google phones.
derekmski said:
Someone from Google on Google forums said they're working on enabling AA Wireless with non Google Pie phones. It sounds like Google has this intentionally disabled on the backend for non Google phones.
Click to expand...
Click to collapse
I wonder if it will be enabled through a Pie update, or simply an Android Auto update in the Google Play Store???
JethroJax said:
I wonder if it will be enabled through a Pie update, or simply an Android Auto update in the Google Play Store???
Click to expand...
Click to collapse
Through a quick update like they did before just for a day while apparently testing it. A user reported having wireless AA briefly working on beta UI
Anybody??????????
This is frustrating.
https://www-xda--developers-com.cdn....com/wireless-android-auto-any-android-phone/
This worked! They must be rolling it out to the masses soon
c-stam said:
https://www-xda--developers-com.cdn....com/wireless-android-auto-any-android-phone/
This worked! They must be rolling it out to the masses soon
Click to expand...
Click to collapse
what worked? i was using wired android auto for a couple years and i was very happy with it, but never got a deck or car that had wireless android auto. I have been heavily involved in the car audio scene for a while (not just bass in case you were wondering LoL) and i havent seen anyone having any issues with wireless AA not working on anything outside of a pixel phone :/
youdoofus said:
what worked? i was using wired android auto for a couple years and i was very happy with it, but never got a deck or car that had wireless android auto. I have been heavily involved in the car audio scene for a while (not just bass in case you were wondering LoL) and i havent seen anyone having any issues with wireless AA not working on anything outside of a pixel phone :/
Click to expand...
Click to collapse
Wireless Android Auto has never worked for non-Pixel or Nexus phones until now. There have been some hacks but nothing directly from Google to allow Samsung, LG, Motorola, OnePlus, HTC, etc phones to work wirelessly with Android Auto until this beta.
c-stam said:
Wireless Android Auto has never worked for non-Pixel or Nexus phones until now. There have been some hacks but nothing directly from Google to allow Samsung, LG, Motorola, OnePlus, HTC, etc phones to work wirelessly with Android Auto until this beta.
Click to expand...
Click to collapse
weirdness... wireless AA has been out for a long time now, thats kinda shocking that it took this long for it to work across multiple devices outside of the range mentioned. Oh well, at least i, myself, wasnt impacted, because... you know.... thats the most important thing here
---------- Post added at 01:06 PM ---------- Previous post was at 01:01 PM ----------
ohhhh, was it just the stock car systems that had that issue? i was referring to the aftermarket like Pioneer, Alpine, Kenwood (which is now owned by JVC), JVC, Sony etc etc.
Affected Aftermarket too. It did not work on my Pioneer W4400NEX with my S10+, but does with the new Google play services beta and the developer option in Android Auto app.
NOTE: Either it has been a f***ing big time coincidence, or it was triggered on Samsung servers somehow (?) by trying to download the firmware to my notebook using SAMFIRM (it was identified, R805FXXU1ESI1, but failed to download), or Samsung reacted real quick to this post, but anyway in a matter of hours after posting this I'm getting the September update through the official channel (Galaxy Wearable app). The updates below were posted before this very note. Just installed. Loving the new look and all features and corrections I mentioned are there! At the time of this writing the online documentation (https://doc.samsungmobile.com/SM-R805F/ZTA/doc.html) still points to the February update (R805FXXU1DSB3, posted in May). EDIT: the update introduced a known bug, one that makes the watch disconnect while updating bundled apps and the update stalls. I guess this may be why Samsung was holding back the updates. OMG. A patch that solves a problem but introduces another. Like Microsoft with "Windwoes" 10.
UPDATE: now it doesn't even serve as a watch. It entered Daylight Savings Time, which has been abolished in the country, and the time settings option is grayed out. Well done, "Sam-Jong"!
UPDATE 2: it looks like there are builds for all regions up to September, but Sam-Jong is lazy enough not to publish them. Just change the region code (ZTA) in the link below and check it.
http://fota-cloud-dn.ospserver.net/firmware/ZTA/SM-R805F/version.test.xml
UPDATE 3: there is even an October update for region TGY:
http://fota-cloud-dn.ospserver.net/firmware/TGY/SM-R805F/version.test.xml
Samsung is holding off these releases for some obscure reason. One of them could be sabotaging Galaxy Watch to favor the Active lineup, like they did to the Note 9 to favor the Note 10.
***
I have an expensive Galaxy Watch LTE, a high-end product, bought at Claro/Brazil this week, national/legal, model SM-R805F.
I've read that it received an update that allows it to monitor outdoor swim training (at the sea), so I bought the model.
The problem is that, even after the firmware update, it does not offer this function, nor several others that have been announced. The lag in step count in walks goes uncorrected.
I did some research and found out that this same model (SM-R805F) received an update abroad in May, which is already outdated, but here there's no update since February, even more outdated.
What's the reason behind this disrespect towards Brazil, and especially towards the LTE variant, top of the line? The BT variant (model SM-R800, without LTE) was updated here in September. So LTE here is at least 7 months behind BT.
LTE for me is a requirement.
Here follows Samsung's own update documentation.
Germany (DBT Region, carrier-free):
https://doc.samsungmobile.com/SM-R805F/DBT/doc.html (May firmware)
Brazil (ZTA [Claro] and ZVV [Vivo]):
https://doc.samsungmobile.com/SM-R805F/ZTA/doc.html (February firmware)
https://doc.samsungmobile.com/SM-R805F/ZVV/doc.html (February firmware)
The ZTO region (Brazil, carrie-free) does not exist for this model, the following page does not exist:
https://doc.samsungmobile.com/SM-R805F/ZTO/doc.html
although the model is reported on sale by the Samsung Brazil page. It never existed, was never available for sale. Samsung says on its page that it is available in its own stores, but that has not left the papers. I went to several stores and the answer is always the same: "only available at the carriers".
The ZTO region only exists for the BT variant:
https://doc.samsungmobile.com/SM-R800/ZTO/doc.html (September firmware).
I've tried all the way to contact Samsung, chat, Samsung Members app and etc, I tried the number 0800-942-9060, a number that a store dealer gave me, but when I call during office hours a recorded voice informs you that at the moment they cannot answer, and at other times it informs you to call during office hours. A real booby trap.
All the answers I received by the other means were "we can do nothing". They don't even give a justification for what is happening.
I have a laptop, a TV, wired and wireless chargers, a dock, a tablet and a Note, all recent, all Samsung tops, but apparently the king has laid in splendid cradle and thinks he can abandon the user that bets in the company's products.
I am responsible for IT in a growing business, I recently recommended buying more than a dozen Samsung Expert X30 laptops for employees, but I am reviewing this recommendation.
As I said in the note topping the post, the watch finally got a firmware update. But it introduced a known bug, one that makes the watch disconnect while updating bundled apps and the update stalls. I guess this may be why Samsung was holding back the updates. OMG. A patch that solves a problem but introduces another. Like Microsoft with "Windwoes" 10.
Whammamoosha said:
As I said in the note topping the post, the watch finally got a firmware update. But it introduced a known bug, one that makes the watch disconnect while updating bundled apps and the update stalls. I guess this may be why Samsung was holding back the updates. OMG. A patch that solves a problem but introduces another. Like Microsoft with "Windwoes" 10.
Click to expand...
Click to collapse
I'm facing the same problem!
Whammamoosha said:
As I said in the note topping the post, the watch finally got a firmware update. But it introduced a known bug, one that makes the watch disconnect while updating bundled apps and the update stalls. I guess this may be why Samsung was holding back the updates. OMG. A patch that solves a problem but introduces another. Like Microsoft with "Windwoes" 10.
Click to expand...
Click to collapse
I guess I'm one of the lucky ones, Northeastern USA, Verizon 4G, watch (LTE) is SM-805U. Tizen 4.0.0.4, no issue, runs like a top....
Sent from my SM-N976V using Tapatalk
lcvleo said:
I'm facing the same problem!
Click to expand...
Click to collapse
So do I.
Did any of you report the problem to Samsung? If yes, what is the best channel? Samsung Members?
KruseLudsMobile said:
I guess I'm one of the lucky ones, Northeastern USA, Verizon 4G, watch (LTE) is SM-805U. Tizen 4.0.0.4, no issue, runs like a top....
Click to expand...
Click to collapse
The problem is localized. Brazil this time. It surfaced on other countries previously and was corrected.
But it seems Samsung didn't resist keeping its bad reputation with this watch and included the bug on the September update released this early November (2 months late). Gosh.
It's been 20 days since the cursed update and still no word from Samsung other than covering up for all the holes I depicted in this post.
A device that can't update its most meaningful app is something between lameness and insult.
Whammamoosha said:
It's been 20 days since the cursed update and still no word from Samsung other than covering up for all the holes I depicted in this post.
A device that can't update its most meaningful app is something between lameness and insult.
Click to expand...
Click to collapse
welcome to the club. except on my 805w, the app update issue has been going on since june or july's update or something.
also posting and expecting any resolution on xda will not yeild any support on the issue. samsung members and forums would be the most productive way of going about this.
Mine hasnt even pulled the update from earlier in the year. I always said I would never buy Samsung again.
Whammamoosha said:
It's been 20 days since the cursed update and still no word from Samsung other than covering up for all the holes I depicted in this post.
A device that can't update its most meaningful app is something between lameness and insult.
Click to expand...
Click to collapse
Raise a problem via Samsung members, with logs/ screenshot.
As far as I know, Gear side is still working on Tizen 3/4 on R8x5, so it maybe a problem from localization.
---------- Post added at 07:37 AM ---------- Previous post was at 07:25 AM ----------
Whammamoosha said:
It's been 20 days since the cursed update and still no word from Samsung other than covering up for all the holes I depicted in this post.
A device that can't update its most meaningful app is something between lameness and insult.
Click to expand...
Click to collapse
Raise a problem via Samsung members, with logs/ screenshot.
As far as I know, Gear side is still working on Tizen 3/4 on R8x5, so it maybe a problem from localization.
tinhduong said:
Raise a problem via Samsung members, with logs/ screenshot.
As far as I know, Gear side is still working on Tizen 3/4 on R8x5, so it maybe a problem from localization.
---------- Post added at 07:37 AM ---------- Previous post was at 07:25 AM ----------
Raise a problem via Samsung members, with logs/ screenshot.
As far as I know, Gear side is still working on Tizen 3/4 on R8x5, so it maybe a problem from localization.
Click to expand...
Click to collapse
Thanks for trying to help, but I've already raised the whole problem via Samsung Members, XDA, Reddit, the whole lot.
Since it's a long-dwelling, well-known and widespread bug, with thousand of complaints worldwide since it started appearing (and being corrected region-wise/variant-wise for a few random regions/variants), I wasn't supposed to *need* to report anything.
But in this post I reported the DNA of the bug *and* of the lack of support for the LTE variant, and also denounced an evident, just-in-time cover-up by Samsung for the latter.
So there's a plethora of detail here *and* from thousands of baffled users, so what's the point in posting pictures/logs? Had Samsung just picked a SM-R805FZSAZTA unit (in my case), upgraded the OS, factory reset it and tried to update the apps, and *fail* at that, it would have a *live* case to work on, with much more detail than a user could ever provide.
BTW Samsung's standard procedure through Samsung Members in publicly well-known cases is more psychological than technical: ask for pictures and logs to make the user believe the matter is being dealt with when it's actually just buying time. Samsung Members in most cases is *useless*. But Samsung just can't say "Sorry, it's a well-know problem, but due to the lack of standardization and centralization in dealing with our products' issues we're lost and haven't done much since the problem appeared. Some random, lucky regions/variants of the product have been contemplated with a solution, but because it's a mess here we've just introduced the bug again, this time in your region/variant, and it will take some awful time until your product's region/variant catches up".
Some issues can only be resolved when a few big heads roll.