Related
The styling I love. The way AW works I like. The internals of the watch I'm not happy with. It's screaming Gen 2 with all it should be now. Hate or love my post, it's my opinion.
Would you sell it to me and send it to Spain?
I made a couple of ROMS for the motoactv and I'd like to develop for the moto360 too, but it's going to take some time until it's released in Europe.
Sent from my GT-N7100 using XDA Free mobile app
dproldan said:
Would you sell it to me and send it to Spain?
I made a couple of ROMS for the motoactv and I'd like to develop for the moto360 too, but it's going to take some time until it's released in Europe.
Sent from my GT-N7100 using XDA Free mobile app
Click to expand...
Click to collapse
As long as after it's said and done I have everything I paid for it. I don't need to make money on it, but I also don't want to lose considering I can return for full refund. Let me know.
EVOme said:
As long as after it's said and done I have everything I paid for it. I don't need to make money on it, but I also don't want to lose considering I can return for full refund. Let me know.
Click to expand...
Click to collapse
I sent you a Private message.
dproldan said:
I sent you a Private message.
Click to expand...
Click to collapse
Replied
EVOme said:
The styling I love. The way AW works I like. The internals of the watch I'm not happy with. It's screaming Gen 2 with all it should be now. Hate or love my post, it's my opinion.
Click to expand...
Click to collapse
I may do the same, we'll see
After facing many connectivity issues and slow processor performance I'm on the fence about doing the same. It is sad as I really like the device but it is just too annoying.
I can't post my video on here but I have an awesome relic band I modified to get on my 360
ajamils said:
After facing many connectivity issues and slow processor performance I'm on the fence about doing the same. It is sad as I really like the device but it is just too annoying.
Click to expand...
Click to collapse
I'm on the verge of returning mine because of connectivity issues. I had seven disconnects during a 6 hour span today. Not sure what's causing them, I thought it was Greenify hibernating the Wear app, but I disabled it and the problem persists.
Log of my problems.
My phone is a Nexus 5 with CyanogenMod 11 M9, my 360 is on 4.4W.1 - KGW42N.
Anyone have any suggestions as to figuring out what's causing the disconnects?
Should I logcat both my N5 & 360?
B3RL1N said:
I'm on the verge of returning mine because of connectivity issues. I had seven disconnects during a 6 hour span today. Not sure what's causing them, I thought it was Greenify hibernating the Wear app, but I disabled it and the problem persists.
Log of my problems.
My phone is a Nexus 5 with CyanogenMod 11 M9, my 360 is on 4.4W.1 - KGW42N.
Anyone have any suggestions as to figuring out what's causing the disconnects?
Should I logcat both my N5 & 360?
Click to expand...
Click to collapse
I too get disconnection notifications all the time, but not sure it has actually effected notifications on the watch
slaydog said:
I too get disconnection notifications all the time, but not sure it has actually effected notifications on the watch
Click to expand...
Click to collapse
I'll continue to get event notifications or anything that was previously pushed to my device, but I can't do anything internet related. I normally check by doing an "Okay Google" and asking what my IP is. (It doesn't show it, but it's a simple search)
I'm almost all but certain that this is an AOSP or CyanogenMod problem, not the 360. What ROM are you running?
Over on the N5 CM 11 Nightly thread there's chatter about BT issues. I haven't been involved with the thread other than an initial flash to a Nightly 3 months ago then reversion back to Milestone, but some of the devs seem to be trying to fix the problem.
Artem at Android Police made a rant post about his 360 and specified disconnection issues. I checked his previous posts and it looks like he's running an AOSP ROM. Just Googling, "CyanogenMod Bluetooth issues" and you get a slew of posts about BT problems.
N5 CM just got a fix 16 days ago, so hopefully this is in the next Milestone. I'm tempted to flash the nightly to check, but I don't have any tinkering time right now because of work/school.
I'm going to guinea pig this app and have it reconnect when ever it disconnects (RIP battery life) but I'm not counting on it. I also just uninstall and reinstalled Android Wear on my N5, maybe that will help? - I read through the Artem post a bit more and an N5 user, Jason Bowers, mentioned that after to switching to Faux kernel things were seemingly better, I'm giving it a go.
Edit: Just want to point out that I'm retarded and CM doesn't work with Faux. I just got my N5 3 months ago and normally ran Sense, so was only Sense or AOSP concerned. Not CM others, didn't know it existed, no disclaimer on Faux N5 thread. - I might switch to a Nightly CM or a Faux compatible ROM, mainly because I'd like to experience my 360 before I make the final decision to return it or not. - Might try the BT app as previously mentioned.
I'm really curious if all these bad battery life problems people are having with their Wear devices are because they are on AOSP ROMs?
B3RL1N said:
I'll continue to get event notifications or anything that was previously pushed to my device, but I can't do anything internet related. I normally check by doing an "Okay Google" and asking what my IP is. (It doesn't show it, but it's a simple search)
I'm almost all but certain that this is an AOSP or CyanogenMod problem, not the 360. What ROM are you running?
Over on the N5 CM 11 Nightly thread there's chatter about BT issues. I haven't been involved with the thread other than an initial flash to a Nightly 3 months ago then reversion back to Milestone, but some of the devs seem to be trying to fix the problem.
Artem at Android Police made a rant post about his 360 and specified disconnection issues. I checked his previous posts and it looks like he's running an AOSP ROM. Just Googling, "CyanogenMod Bluetooth issues" and you get a slew of posts about BT problems.
N5 CM just got a fix 16 days ago, so hopefully this is in the next Milestone. I'm tempted to flash the nightly to check, but I don't have any tinkering time right now because of work/school.
I'm going to guinea pig this app and have it reconnect when ever it disconnects (RIP battery life) but I'm not counting on it. I also just uninstall and reinstalled Android Wear on my N5, maybe that will help?
I'm really curious if all these bad battery life problems people are having with their Wear devices are because they are on AOSP ROMs?
Click to expand...
Click to collapse
Interesting, I'm on Liquid Smooth (AOSP), so you could be right.
No other issues with Bluetooth that I've noticed - phone calls and streaming music seem to work fine...
---------- Post added at 02:23 PM ---------- Previous post was at 01:46 PM ----------
I left the Gear 2 not because I didn't like the watch, but because I couldn't stand stock-based ROMs any more - that and because the 360 looked so sweet and I wanted to try Android Wear - so I'm sticking with AOSP anyway, lol
Just got back a lil' while ago from returning mine. Build quality of the watch was a "little" disappointing to me, but the main issue was Android Wear; it just ain't fully baked yet. In addition to it not doing much, bugs with settings/connectivity and sending texts have me feeling it needs time.
After that time, I'll look at the hardware again; guessing it will be more capable as well.
Been struggling with returning mine. I had lost my pebble but then found it after i bought the 360. I have been wearing the pebble while waiting on my 360 screen protector. It providing me the same infomation it just doesnt look as good. I am wondering if the design is enough to keep it. I do have until Friday to decide.
dproldan said:
Would you sell it to me and send it to Spain?
I made a couple of ROMS for the motoactv and I'd like to develop for the moto360 too, but it's going to take some time until it's released in Europe.
Sent from my GT-N7100 using XDA Free mobile app
Click to expand...
Click to collapse
WOOT! I hope you get one dp. I've used your roms on my motoactv. I've got a 360 that I may buy from a coworker (he bought it and is going to return it, he loaned it to me over the weekend)
Hi all. I have a pioneer AVIC-8000NEX and a verizon note 4.
Ever since having my GS4 I could not get the mirror link to work. I have the pioneer cables and the samsung mhl adapter.
I downloaded app radio on my phone but I ca never get it to work.
I tried drive link (Samsung's app) but it constantly crashes upon opening.
Anyone have mirror link working on their note 4?
I am on the same boat. From what I know, the note 4 has some kind of mirror link built-in and the s4 did not, however, pioneer needs to make it compatible with their devices
Sent from my SM-N910V using Tapatalk
I've been trying several things and trying to read up as much as possible. If I'm not mistaken, our devices use mirror link 1.1 and my Pioneer avic 8000 nex is on 1.0. There was a firmware update available but it didn't update the mirror link version. Mainly apply car play. I know Samsung has a Drive Link app, but it crashes whenever I try to open it. Using Pioneer App radio app, it starts to connect but then disconnects. Can't figure this out.
just got off phone with pioneer...
I was having this same issue with my pioneer head unit. Runs mirrorlink v1.0 but note runs v1.1. Spoke to pioneer who tells me the drivers are not backwords compatable. Pioneer is calling it a know defect on Mirrorlink side. They tell me its effecting everyone.
I called mirrorlink which nobody answered..... which is odd.
Also spoke to samsung customer service about it who told me its only used for their tvs to link... after i explained to the customer service person what it really was i did not get a reply.
So 1000.00 on radio, 100.00 on mirrorlink box, and i have a bluetooth connwction still.
Issue is with Pioneer and lack of development
Ok so... spent more time on phone with people at MirrorLink, Samsung and Pioneer.... here is the outcome.
MirrorLink states that the contract any company signs with them simply states they will provide the mirrorlink driver, its is the companies responsability to provide support for the driver and they application.
MirrorLink v1.0 needed a gateway app installed in order for it to talk to your radio however v1.1 has this built in.
Pioneer radios running v1.0 will NOT talk to phones running v1.1 as v1.1 is not backwards compatable due to the gateway app being built in.
I spoke with Pioneer to see how or when a updated flash for the 4600BH will be out there as this is the only reason I got this radio 8 months ago, the rep told me that they have no plans to update any of their current radios with a new flash and v1.1 and if I want MirrorLink to work with my Note4, "go buy a new 2015 model"
So there you go, customer service at its finest.....
I have submitted a BBB complaint that I spent good money for a working product that says it has MirrorLink but yet says nothing about the versions. If I had this radio for 3 years its one thing... but 8 months and there is NO support going foward for it?
Please keep me posted on your complaint with the BBB. You will also most likely need a petition going citing the same issues. I bought my avic 8000nex in April and mirror link was one of the features I was sold on. Is there anything I can do to help spread the word or get some momentum going for the complaint?
Mirrorlink
I have been having the same issue with the Samsung series of phones and the Pioneer AppRadio series. This is an absolute complete fail on Pioneers part. I personally am about to boycot anything from them because of their crappy customer service and their complete disregard to support their own stuff. Complaining to the BBB has done nothing for now, not sure what would. However, if anyone comes up with a fix or a third party flash fix for this head unit, I would be interested until I send this thing back to pioneer in pieces and tell them to kiss my but.
I don't believe this is a pioneer issue. Even if the pioneer uses 1.0 the HTC one m8 is 1.1 and works flawlessly with the pioneer units. I think this is a Samsung issue. I have a galaxy s5 on lollipop with mirrorlink and have the same issue. It connects but phone screen goes black and I have no picture on 4000nex screen. Oh and the s4 mini, note 4 and note edge were removed from the approved devices list on the mirrorlink web site a few days ago. Samsung is the problem here.
I'm in the market to upgrade my minivan's old Tape/CD player to a double-din head unit. I'm glad I found this thread. In fact, I nearly purchased that same head unit, last year.
In regards to MirrorLink 1.1, it looks like it came out sometime between December 2013 - April 2014, more likely AFTER the said head unit in the OP began mass production. I'm wondering if the newer Pioneer units support the same MirrorLink 1.1 technology. I've read that they are due out in March, 2015. I'll be looking at the AVIC-8100NE (or AVIC-8100NEX...it might've been a typo where I first read it), unless I hear of something better.
Can we start a list of known working head units for the Galaxy Note 4?
Honestly, I was going to try and see if there is a way to get it to work but I decided to just sale this head unit. I'm going to wait for an unit with Android Auto... I was looking at the model that Parrot is going to put on the market and I was very impressed, pretty much all that I wanted to do I'd be able to do with that.
Until than, I'm looking a way to use my Nexus 7 LTE as head unitish. Seems like it's possible so I'll start that project tomorrow
Still not working on 2015 model
Hey, tried my s5 with a 4700bs (2015 model with 1.1) on my display today and I still get the same error. "Reset settings" or whatever. This is not a 1.0 vs 1.1 problem. This has something to do with samsungs implementation of mirrorlink. The htc m8 is 1.1 and has always worked. Can't figure this one out. I should have gotten the htc phone.
Does anyone know if as of today pioneer has updated the mirror link firmware to 1.1?
I own Toyota innovative
Same issue . It's having Fujitsu Ten head unit.
I'm wondering if anyone has gotten MirrorLink to work on any Head Units with the Verizon Note 4 model (SM-N910V). Furthermore, if not, I'm wondering what the culprit may be. is root required? What about other Note 4's from other carriers with unlocked bootloaders? Basically anyone except Verizon and AT&T, with the exception of Verizon Developer Edition. Root is available for all those variants, if I'm not mistaken.. Anyone?
Still waiting for Pioneer to update the firmware for avic 8000nex. If they ever will.
Sent from my SM-N910V using Tapatalk
https://9to5google.com/2018/08/29/google-wear-os-redesign-confirmed-all-watches/
This is amazing. For an old ass watch. Thanks Google
Wow great to hear that such an old watch still getting an update.
Anyway, still can't find any new smart watches that I think it's worthy to replace my Huawei Watch 1.
I saw a few videos talking about this update.. excited to see it! and glad its coming to our watch! i was just reading on how a lot of people downgrade from AW2.0 to AW1.5 because of how poor AW2.0 is.. I wonder if this new one will be better than both.
Hold your horses. So far, the only evidence we have that we're getting this update is an uncited and unknown Google rep saying that "all watches with 2.0" will get it. No official Google announcement has confirmed this that I can find. Also, that "list of phones that definitely won't get it" is from a Google post released in 2017 that simply states which phones will not get Android Wear 2.0. Call me a pessimist, but I'm far from convinced that we're getting this.
And if we do get it, I doubt it will be in the form of a firmware update, as some have reported. I suspect it will be just an update to the Wear OS app.
TheSt33v said:
Hold your horses. So far, the only evidence we have that we're getting this update is an uncited and unknown Google rep saying that "all watches with 2.0" will get it. No official Google announcement has confirmed this that I can find. Also, that "list of phones that definitely won't get it" is from a Google post released in 2017 that simply states which phones will not get Android Wear 2.0. Call me a pessimist, but I'm far from convinced that we're getting this.
And if we do get it, I doubt it will be in the form of a firmware update, as some have reported. I suspect it will be just an update to the Wear OS app.
Click to expand...
Click to collapse
Just trying to be optimistic here steev. By the way thanks for your rom NegaSteev. I been using it ever since youve created it. Negamans roms killed my battery on the huawei. Your rom revived my watch. THANKS for all of your work.:good: I guess we play the waiting game. Everyone lookout and update if you find anymore new info.
TheSt33v said:
Hold your horses. So far, the only evidence we have that we're getting this update is an uncited and unknown Google rep saying that "all watches with 2.0" will get it. No official Google announcement has confirmed this that I can find. Also, that "list of phones that definitely won't get it" is from a Google post released in 2017 that simply states which phones will not get Android Wear 2.0. Call me a pessimist, but I'm far from convinced that we're getting this.
And if we do get it, I doubt it will be in the form of a firmware update, as some have reported. I suspect it will be just an update to the Wear OS app.
Click to expand...
Click to collapse
Darn - I knew I was being too optimistic!! Still crossing my fingers, though.
ozzyager said:
Darn - I knew I was being too optimistic!! Still crossing my fingers, though.
Click to expand...
Click to collapse
My WearOS versie = 2.15.0.206732242
Wear os 2.15 is great.
Got released. Anyone got it?
0xPraeT0Rian said:
Got released. Anyone got it?
Click to expand...
Click to collapse
Not yet
Sent from my BTV-DL09 using Tapatalk
Just got an update; frustrated to see it is "android wear 2.16."
Apparently the wear os update is limited to oreo devices, but ours is nougat.
https://m.gsmarena.com/the_redesign...ling_out_to_smartwatches_today-news-33513.php
My guess is that this update is not a firmware update but mearly a wear os launcher redesign/update (supposition made based on the available screenshots) and maybe also of some apps such as google fit. This is why all devices get it (on wear 2.0) as it does not depend directly on wear os base version (Nougat / Oreo).
Edit: although from the gsmarena article the update is called Wear OS 2.1, so who knows. We play the waiting game...
I wish we would have a clear answer, I got a bit excited thinking I would have it and tried forcing an update in various ways.
i'm excited for the new Wear OS (3.0?) .. i'm still on 2.16.. Someone let us know when it arrives!
0xPraeT0Rian said:
Got released. Anyone got it?
Click to expand...
Click to collapse
It's rolling out now. There's a complicated but confirmed working (I did it) method to trigger it that has been described in other threads on this forum. People have also reported triggering it by uninstalling and reinstalling the wear os app from the watch. Either way, you'll probably see it any day now.
As I suspected, it's a wear os app update (must be version 2.16 or later), not a firmware update.
TheSt33v said:
It's rolling out now. There's a complicated but confirmed working (I did it) method to trigger it that has been described in other threads on this forum. People have also reported triggering it by uninstalling and reinstalling the wear os app from the watch. Either way, you'll probably see it any day now.
As I suspected, it's a wear os app update (must be version 2.16 or later), not a firmware update.
Click to expand...
Click to collapse
Yeah, I am following the Reddit subforum of wearos. No official update has been done to hw1 yet, only the ones who forced the update got the new interface.
Thanks for the reply anyway.
TheSt33v said:
It's rolling out now. There's a complicated but confirmed working (I did it) method to trigger it that has been described in other threads on this forum. People have also reported triggering it by uninstalling and reinstalling the wear os app from the watch. Either way, you'll probably see it any day now.
As I suspected, it's a wear os app update (must be version 2.16 or later), not a firmware update.
Click to expand...
Click to collapse
can you explain how did you do it ?
umair shaikh said:
can you explain how did you do it ?
Click to expand...
Click to collapse
https://www.reddit.com/r/WearOS/com...gs_on_my_zw3_heres/?utm_source=reddit-android
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.