yashsingh1/xdaforums huggingface dataset:
[Sony Smartwatch 3] ProtoDeVNan0:
I've seen like 3 websites that already confirmed that SW3 will get AW2.0. Also couple of mail screenshots from sony where they say that it will get the update. In the meantime I tried porting AW2.0 but no luck. Managed to brick my watch really really badly. But eventually after 30 minutes of trying to recover it, it finally worked. Might need a newer bootloader to work. We could reverse engineer the bootloader and see what's going on inside. But I don't think it will help a lot cause our devices have Broadcom CPU which ruins everything. We could eventually make a hybrid rom. But that probably won't satisfy most of us.

But yeah.. Sony supposedly confirmed it. So we just have to wait to 9th feb and see what happens. I've also heard that it might come to our devices between march and april but those are just rumours.

Be calm guys! 5 days left. I check google everyday for more news too. But we just have to be patient :).
[Sony Smartwatch 3] gurningchimp:
I'd be prepared to wait a little longer to be honest. There's a flurry of new devices launching and confirmed upgrades etc, it stands to reason that the SW3 may take a bit longer to get some upgrade love. As pointed out already in this thread, the watch will still work regardless :)
[Sony Smartwatch 3] hateus:
[IMG="this was my reply from sony today"]https://www.dropbox.com/s/vpn4kc6prq4iv08/20170208_124551.png?dl=0[/IMG]
[Sony Smartwatch 3] Chinfuk:
Is it only me who can't see this?
[Sony Smartwatch 3] ProtoDeVNan0:
Can't see it either lol. Well tomorrow everything will become clear. Even though it's quite confirmed but who knows.

https://www.google.co.uk/amp/www.po...the-major-software-update-for-watches.amphtml

Another confirmation. Thanks to the guy from reddit.
[Sony Smartwatch 3] alex6600:
And we must wait 1-2 month after release (as always) for update...
[Sony Smartwatch 3] ProtoDeVNan0:
Sony..

Same thing happened with my Xperia tablet. They promised to update it and then it took 2-3 months for them to release the update. Now when I recently bought Xperia XA Ultra that they promised to update to Nougat before 2017, it's february and still no signs of Nougat..

But it still is better to wait and get the update instead of not getting it at all :).
[Sony Smartwatch 3] dafiduck:
me too
[Sony Smartwatch 3] matonka007:
I found this:

If you count both Michael Kors lines, that is a total of twenty watches that will be receiving the update. Watches absent from the list include the original ASUS ZenWatch, LG G Watch, Samsung Gear Live, Moto 360 (Gen. 1), and Sony's Smartwatch 3, none of which should be particularly surprising to anyone at this point.
[Sony Smartwatch 3] cyleo:
Source: http://www.androidpolice.com/2017/0...list-of-every-watch-getting-android-wear-2-0/

I hope they are wrong
[Sony Smartwatch 3] jerses:
Dont get your hopes on the upgrade to AW2.0. Sony has always been open to upcoming updates. Its the only company that has put under the rug all the wereable tecnology from show and websites. They dont want to announce that they wont release an update because they always play the long wait game where the device is too old for consumers to care about. I have yet to see news where they confirm someone at sony (someone with the knowledge) saying it will be even possible only vague emails from reps that are trained to say everything will happen just stop asking. Im guessing SW3 is in the list because every news outlet go to XDA for answers saw the emails and post them as proof then someone else look at that news and post it as fact.
[Sony Smartwatch 3] crunchybutternut:
Yeah, just see a broken image link.

Seems we are not getting the update officially though :(

Hopefully the source will be released...
[Sony Smartwatch 3] milliv4nilli:
What a big disappointment, was really hoping for an update.

Haven't found any credible sources at all regarding an actual update, only speculations.

Well, this is it I guess.
[Sony Smartwatch 3] Chinfuk:
Surely it's not time to sell our watches just yet :) I'm sure someone will be able to get it working somehow? We will just have to wait and see
[Sony Smartwatch 3] jerses:
Not sure about that, android wear is a closed platform right? i have been looking at a friend chinese android watch with android 5.1.1 and its awesome. Its better than android wear 2.0 , it also helps that the watch has a speaker that make it great. You can hear notifications, answer calls, read and answer messages via keyboard. Maybe someone needs to look at that instead lol.
[Sony Smartwatch 3] nexus_ctOS:
fkn google and their support
[Sony Smartwatch 3] matonka007:
Ok, officialy no Android Wear 2.0 for us. Here is official press news from Google:

https://blog.google/products/android-wear/android-wear-20-make-most-every-minute/

"Current watches getting Android Wear 2.0 include: ASUS ZenWatch 2 & 3, Casio Smart Outdoor Watch, Casio PRO TREK Smart, Fossil Q Founder, Fossil Q Marshal, Fossil Q Wander, Huawei Watch, LG Watch R, LG Watch Urbane & 2nd Edition LTE, Michael Kors Access Smartwatches, Moto 360 2nd Gen, Moto 360 for Women, Moto 360 Sport, New Balance RunIQ, Nixon Mission, Polar M600 and TAG Heuer Connected. "
[Sony Smartwatch 3] Oletros:
Why blame Google when the guilty one is Sony?
[Sony Smartwatch 3] nexus_ctOS:
well, who decides to update the watch or not? Sony said that they will, but google didn't
[Sony Smartwatch 3] Oletros:
The one that decides to update is the manufacturer, not Google. And Sony has never officially said that they will update it
[Sony Smartwatch 3] geogaddi47:
This is bull****. The SW3 is more than capable of running AW2 and it's still Sony's latest Android Wear device!
[Sony Smartwatch 3] ironjon01:
And no SW4 at the horizont it's crazy ?

Enviado desde mi Nexus 6P
[Sony Smartwatch 3] ProtoDeVNan0:
Anyone's willing to help me with porting AW2.0? Is there anything like LineageOS Wear? Do we need newest bootloader to boot AW2.0? I ported couple of roms to S7 Edge, so if anyone would want to try then contact me on telegram [MENTION=5203734]ProtoDeVNan0[/MENTION] . The more devs we have the bigger chance we have of porting it! :).

In the meantime we can spam Sony with mails about AW2.0. Like 200-300 people did that when we needed kernel sources from Samsung. They released them even before OTAs lol.
[Sony Smartwatch 3] drakonizer:
Nope. Google handles Android Wear updates, not Sony. That's why Google has the kernel source code on their repositories, and not Sony. I'm pretty sure Google decided to ditch the SW3 because they think it's probably not worth the effort to initiate the bring-up on BCM sources just for one device, which is exactly the kind of bs they accuse smartphone manufacturers of doing. The hypocrisy is real.
[Sony Smartwatch 3] Oletros:
Are you really saying that an smartwatch manufacturer can't start development of a watch until Google decides to develop the kernel code for the SOC?

The one using Mediatek SOC only develop it because Google decided that some would use that SOC, isn't?

You could not be more wrong.

By the way, there is a pretty git repository, and Sony or Fossil can't use it, can they?
[Sony Smartwatch 3] drakonizer:
I like how my point floated over your head like it didn't exist. GOOGLE handles updates. NOT Sony. GOOGLE updates all the smartwatches, irrespective of the brand because it is a CLOSED platform, which means it's not open source like Android. That is why the GPL sources are on their git repos and not Sony's. Updates for phones are handled by the OEM. That is why the kernel sources of Sony phones are hosted on their GitHub account.

If a manufacturer decides to use a MediaTek SoC for their watch, and they want Android Wear on it, they would have to pay the licensing fees to Google, and Google would do the software bring up for the watch. That is how closed platforms work. The MediaTek watches probably got an update because they're relatively newer and it would be extremely unethical to ditch support for them.
[Sony Smartwatch 3] Oletros:
I like how you show that you don't know what closed or open source is. GPL license is the most open source license and not even Google can decieddto forbide that someone forks it

And more bull****, what Google controls is the distribution of the updates and what they forbids is the modification of the core and ui experiences to be certified as Android Wear. The only closed source are the Google Services, as always

And by the way, I suppose that you're saying that Google explicttly lies when they say:
[Sony Smartwatch 3] drakonizer:
1) Android Wear is not licensed under the GPL. Please do some research.

The source code for Android Wear is NOT available. If you go to android.googlesource.com, you'd see that there are only tags in the AW repository, with an incomplete source. This is why no AW watch has ever gotten an Android Wear version that was built from source by the community.

(OT: Since I have obviously been here longer than you have and have actually done development and contributed to the site instead of just downloading ROMs and sharing ridiculous opinions and half-truths, I think I know what "closed and open source is".)

2) Google closes only their services for Android. But the whole of Android Wear is closed source. Only Google can push out updates because only they have the source. NUMEROUS websites have already said this, and it would do you well to Google it before your next reply.
[Sony Smartwatch 3] alex6600:
I'm in.

When update will be for square watch, like Asus- we must try something.

I think that existing kernel with firmware and drivers must work on AW2. Only ramdisk well be differ, imho.
[Sony Smartwatch 3] andrewia:
Although it is extremely difficult, it is theoretically possible to port Android Wear from other devices to the Smartwatch 3. [MENTION=803006]biktor_gj[/MENTION] successfully ported Wear to the Galaxy Gear 2 and Gear S (using various watches, especially the Huawei Watch) despite the fact that they use completely different hardware and even different versions of the Linux kernel (made for Tizen, not Android). It would be relatively easier to port Wear 2.0 to the Smartwatch 3 because it already works with Android Wear 1.X, but we would have to work from a watch with NFC - maybe the LG Urbane 2nd edition would be good since it should be upgraded from Wear 1.X to 2.0 soon, and that update should enable its NFC functionality. That way we can compare how its kernel, libraries, etc. were changed and attempt to bring the Smartwatch 3 up.
[Sony Smartwatch 3] ProtoDeVNan0:
Yes! :D I was looking for Your telegram but couldn't find it.. can You message me there?

I'd go like [MENTION=949860]alex6600[/MENTION] said with a square watch.

So far I got the Android wear 2 preview source and now trying to make device tree for it with a help of one dev who is extremely experienced with porting/building(aosp) impossible stuff. We can also make a hybrid. But it wouldn't be as pretty as full AW2.0.

Anyone who's interested in helping me message me at [MENTION=5203734]ProtoDeVNan0[/MENTION] on telegram!
[Sony Smartwatch 3] andrewia:
I am also going to have to disagree with [MENTION=5258151]drakonizer[/MENTION] about the Wear update process. It's ludicrous to think that Google would handle all the updates because every watch is so different. How would Google be able to handle all the minutely different designs in every watch's hardware? Why would every watch have a different bootloader, all of which need to be updated along with major Wear updates, which requires even more work? Why would the Smartwatch 3 have completely different components (mostly sourced from Broadcom) whose binaries need hundreds of man-hours to integrate and retest, when if there was a single "Google Wear development team" it would make much more sense to source the hardware and binaries from another vendor they are already integrating?

Remember that unlike Windows, drivers can't carry over to new OS versions - they must be rewritten by the vendor for every major update and then reintegrated. Also keep in mind updating a device officially is much more difficult than updating a ROM because shortcuts like shims for binaries won't work. (Again, the vendor must supply new binaries with every major OS update.)

In short, it's ridiculous to think Google would shoulder the responsibility of updating dozens of different models of Wear watches, all of which have unique bootloaders, hardware configurations, and other quirks that need to be accounted for. It would also be much more obvious, and development would be much more similar (see Android One), if that were the case.
[Sony Smartwatch 3] alex6600:
I use Skype/Viber/Hangouts...
[Sony Smartwatch 3] andrewia:
I disagree with this. Unless there's part of the Wear stack I'm missing, almost all of Android Wear's software is designed to work with both circular and square screens. Even if it wasn't, switching around userland apps is relatively trivial compared to developing the underlying OS/kernel stack. The kernel will probably be very broken considering the leap to a new OS version, so we want the best kernel to work with to add support for features like NFC. Since the Urbane 2nd Edition will add NFC and will be upgraded from Wear 1.X to 2.0, it would be the best watch to base development off of. As an example, [MENTION=803006]biktor_gj[/MENTION] did a lot of port work from the Huawei Watch, despite the fact that it has a round screen compared to a square and rectangular screen. I think we should all read his posts at https://xdaforums.com/gear-2/development/please-help-kernel-compiling-android-t2992953 and https://xdaforums.com/gear-s/development/dev-gear-s-android-port-t3177740 as a reference for porting Android Wear with less-than-complete source code and different hardware.
[Sony Smartwatch 3] drakonizer:
Because they want to keep Android Wear closed? Despite what you may think, Google is not a fan of open source software. This is evident if you take a look at the Android Open Source Project. The apps in there have been abandoned since API9 and Google has switched over to closed source alternatives. More and more parts of the Android API are being integrated into Google Play Services, as opposed to the open source project.

Android wear is not like traditional Android. Despite what others say, the source code is NOT available. I myself have tried building MM6.0.1 with the already available kernel and platform source from Google, but only to realize that the source is incomplete. Most of the ports you see around are not built from source, but use precompiled apps and libs from another watch, with a self-compiled kernel with enough tweaks to get it to boot.

I can guarantee you bootloader updates are almost never pushed to Android Wear. The bootloader is a one time set up. Almost all Android Wear watches have a snapdragon 400 which simplifies the update process for Android wear. If I remember correctly, I believe Google has a unified kernel for that. The userspace drivers come from QCom (the vendor as you said) and Google does not have to develop them. I do not know what "hardware configurations" you are talking about, but most differences in hardware (like screen size and resolution) are handled by the software and are independent of the drivers. As long as the underlying SoC is the same, the update process is not the hassle you make it to be.

And yes, Google WOULD shoulder this responsibility. Why? Because they don't want a repeat of Android's fragmentation for Android Wear (ironic now). And this was mentioned in the original Android Wear keynote.
[Sony Smartwatch 3] ProtoDeVNan0:
Can You PM me on XDA Your viber or skype? I already have basic device tree.

Edit: seems like I can't build it. Would need linux to do that and on mac it has some weird issues with java.

Well. Porting it in a hybrid way then.

Interesting. If he only made a guide how he did that..
[Sony Smartwatch 3] andrewia:
The Smartwatch 3 bootloader has been updated at least 3 times since launch: I have found updates in the OTAs LWX48P, LCA43, and MEC24H.

I also want to argue there is a third option between "source not disclosed outside of Google" and "open source". Google can share Android source to manufacturers under NDA to let them develop updates ahead of time, and in my theory, let manufacturers develop OTA updates for Android Wear watches. This happens every year after Google announces a new version of Android but does not release the source: manufacturers such as HTC and Samsung can begin bringing up their devices before the update is released on any phone. This also happens in rare cases of public beta release, such as Sony's Nougat preview for the Z3. That was released without source because Google gave Sony their Nougat DP source under restriction.
[Sony Smartwatch 3] drakonizer:
Except every source on the internet states that Google updates watches, not the OEM. That is why GOOGLE'S blog post had the information about which watch would get updated. That is why the GPL kernel sources of every watch is hosted on Google's git servers (which otherwise host only Nexus and Pixel kernel sources). That is why whenever an OTA is released, the link redirects to GOOGLE's servers. That is why, if you'd take a look at some of the threads in the Sony support forums regarding AW, they'd say they're not responsible, Google is. That is why almost all of the Smartwatches were listed in the Google Play store at some point.
[Sony Smartwatch 3] DrJ76:
Here we can vote to make some presure on Sony to do something:

https://www.change.org/p/sony-andro...utm_source=share_petition&utm_medium=copylink

Best regards..
[Sony Smartwatch 3] Omibus:
A big German online shop lists the SWR50 with Android Wear 2.0 in the Title:

https://www.otto.de/p/sony-3-swr50-...serdicht-449154145/#variationId=449156333-M24
[Sony Smartwatch 3] andrewia:
I downloaded the latest Smartwatch source from Sony Mobile's site and it seems we are both half-right. Sony Mobile itself only releases the u-Boot source and says, "All other copy-left code can be fetched through the AOSP servers which can be found [at googlesource.com]". The Smartwatch source at Google has commits from many developers (understandable considering it's forked from an Android kernel which is forked from the Linux kernel), but all hardware-specific commits [i.e. commits that are unique to the Smartwatch's repo] are authored by Sony Mobile developers then committed by a mix of Sony Mobile and Google developers. So Sony updates the bootloader itself and brings up the kernel to support Google's new release, with Google ultimately in charge of signing off on the update and then building and releasing it.
[Sony Smartwatch 3] blast1987:
Can't we make an aosp version of aw2 for our smartwatch ? I don't understand, is AW2 a closed source platform or not?
[Sony Smartwatch 3] drakonizer:
It makes sense. Sony does the initial hardware bring up and other hardware improvements if needed to the kernel. And this way, Google manages to keep Android Wear itself a closed platform. Thanks for the info.
[Sony Smartwatch 3] nawashi:
SWR50 Not getting update

as per the fine print on the store page (too few posts, cant paste link to store page here)

imgur. com/0MAZLbF
[Sony Smartwatch 3] fjordstrom:
Here's a screenshot of what [MENTION=6983266]nawashi[/MENTION] is talking about:

[IMG="https://pbs.twimg.com/media/C4Y6IjgWAAEm3F-.png"]https://pbs.twimg.com/media/C4Y6IjgWAAEm3F-.png[/IMG]

So Sony is confirming it... in fineprint -_-
[Sony Smartwatch 3] PDesire:
There's a hope for us to get AW 2.0, the Source of AW 2.0 Preview 2 is there and device trees exist already for our devices so when I come back (in a Month maybe) I will try my best to make AW 2.0 possible for our devices as I've paid 170€ for it and won't let it die so easily

Let's see who's better Google ;)

This is the device tree, thanks Protodevan0 for that:

https://github.com/PDesire/device_tree_sony_tetra

Missing are blobs, that's it, and Gapps I will use from Huawei Watch with same FW.

The blobs we can extract from Asteroid OS and self dump

Your PDesire
[Sony Smartwatch 3] jek20:
I bought it 141€ a week ago because I knew it will get AW 2.0 when it comes...
[Sony Smartwatch 3] dverbame:
hope you can, and even i think a custom aw2 for us :D with much much more tools

can't wait .. please make it faster
[Sony Smartwatch 3] last_nexus:
Maybe not yet supported
[Sony Smartwatch 3] Mikegrmn:
I bought mine about 2 weeks ago, already kinda knowing it won´t get official support. But then, there´s still the community and it´s working well with 1.5 also. And, imho, it´s still the best android wear minus pulse reading. All the new watches are feature laden, have low power chips and still don´t make it through a full day in terms of battery.

I get full 48 hrs and even up to 72 hrs if I turn on air plane mode and turn off display during the night.
[Sony Smartwatch 3] drakonizer:
Maybe we can base the device tree also from AsteroidOS? Seems like your one is missing some bt related files. https://github.com/FlorentRevest/android_device_sony_tetra

Also, Asteroid OS is lollipop based, and uses blobs from the 5.1.1 release. We should dump the blobs from the latest MM build to ensure maximum compatibility.
[Sony Smartwatch 3] Skyjumper_GR:
AW 2.0 not supportet!"

https://www.sonymobile.com/global-en/en/products/smart-products/
[Sony Smartwatch 3] mikrokernel:
Nooo

SmartWatch 3 SWR50 supports up to Android Wear 1.5. Android Wear 2.0 and onwards are not supported.

Inviato dal mio HUAWEI NXT-L29 utilizzando Tapatalk
[Sony Smartwatch 3] dverbame:
bro when do you start it ? and when do you think it will come out ?
[Sony Smartwatch 3] gbru2505:
Delete

---------- Post added at 10:57 AM ---------- Previous post was at 10:53 AM ----------

That sounds a little pricey. It's been available in the UK for £80 for months. I bought it at that price but suspected no official upgrade would be forthcoming because I the tiny profit at that rate wouldn't pay for development. Hopefully the community will come up with something. Isn't that what has driven Android forward and costs down all along?
[Sony Smartwatch 3] pawces:
the thing about being a first adapter of anything is, you accept that you are the test bed for something better, and that the manufacturer was happy for your help but not enough to give you the fruits of their experiments to which you signed up for voluntarily. Let's protest. Isn't that the millennial thing to do? lol
[Sony Smartwatch 3] mikrokernel:
then it is sure that you will not make aw2.0?

Inviato dal mio HUAWEI NXT-L29 utilizzando Tapatalk
[Sony Smartwatch 3] RJASSI21:
At least you didnt buy it at launch for £180. Thats what I paid from Amazon UK and to see it not gonna support aw2.0 is a real shame. Just one thing though... I did get a notification on the watch only to complete a survey which asked me if I was happy with the watch. I asked my brother if he got the same thing on his Huawei watch but nothing. I thought maybe it was related to aw2.0 and Google considering it. To which if most people answered extremely happy they would make aw2 0 or if people said extremely awful to not consider it. Im unsure about that but I am ashamed.
[Sony Smartwatch 3] alex6600:
I, and some other peoples with SW3 received such notification a few months ago.
[Sony Smartwatch 3] RJASSI21:
Hmm interesting... I live in the UK so that might be why I only had it yesterday. I havent herd of any other watches getting it yet.
[Sony Smartwatch 3] McNeillR:
I only got mine a few weeks ago so can return it (though did pay £15 to cover it).

I'm only really after a few things:

GPS Tracking

Offline (i.e don't have my phone with me) music streaming

[Spotify controls if possible - Smartkey or similar is fine though to change track/volume]

I'm assuming for £80 I can find something comparitive from China even if it doesn't support AW2?
[Sony Smartwatch 3] zbiecik:
http://m.gsmarena.com/its_official_sony_smartwatch_3_will_not_receive_android_wear_20-news-23428.php

Wysłane z mojego EVA-L09 przy użyciu Tapatalka