yashsingh1/xdaforums huggingface dataset:
[Sony Smartwatch 3] RJASSI21:
Its like google think were made of money though. Like we all know our watch has the capability to run aw2.0. Just compare its specs to tge Huawei watch, identical if I dont say. Only difference is Bluetooth 4.1 vs 4.0 on the sw3. Google have a record for killing off capable devices and ours is one of them. I mean they said they were going to release aw2.0 start of this year. In the UK still no aw2.0 for Huawei watch and that had Dev preview.

Our watch should still have this officially it even has nfc that other aw2.0 watches dont. Im pleased to know this thread exists and that people are trying their best to port it, its a hard task to do and its real great that we can prove Google wrong if all goes to plan, it just frustrates me when I know something can have something officially but doeant because, money.

Thanks for the work on the port anyway. Regardless of aw2.0, sw3 is still a great device.
[Sony Smartwatch 3] drakonizer:
No, it's not the same thing. Android Wear is not Android, and it does not have the complete framework of AOSP. Whatever is derived from Android, it has been open sourced under the GPL. However, this is not enough. As someone already pointed out, the source release is missing the newer framework (it downloads the older one). Which means a lot of device specific compiled code must be ported to our device. And this will be really hard, considering ours is the only device with a crappy Broadcom chip.

Gapps will have to be ported too, but that's relatively simple, and must be done only after a ROM built from source finally boots, which I don't foresee happening soon.
[Sony Smartwatch 3] matejdro:
It IS Android. All the additions are eventually added to the Android (for example Android 4.4W was for Wear-exclusive for some time, but then all its framework additions also appeared in Lollipop).
[Sony Smartwatch 3] drakonizer:
It is Android when you think about the way it runs apps and uses the ART. But, it's not AOSP with some random wear google apps. It's a forked version of Android (some crude examples are Remix OS and MIUI) which is based on Android, but is not open source. It is not possible to build and run the system from source (because there is no source).
[Sony Smartwatch 3] matejdro:
Are there any examples of framework features on Wear that did not actually get into mainstream Android eventually?

For example, swipe to dismiss activity, feature that is only used on Android Wear devices AFAIK, is fully present in the Android source: http://grepcode.com/file/repository...id/internal/policy/impl/PhoneWindow.java#3622. It automatically gets enabled on any device that requests this functionality.
[Sony Smartwatch 3] drakonizer:
I'm not talking about framework features. Android Wear does not use the entire AOSP framework, is what I'm saying. I don't know how your link is relevant.

Android Wear, like Android Auto and Android TV, is NOT part of AOSP and cannot be compiled and run from source. Despite what you say, you can't just "install gapps like phones" and get Android Wear running on your watch, like Google releases. The Android Wear tags on AOSP are like the O preview tags: only the GPL licensed parts are present, which is not enough to get it up and running on a watch. If you don't believe me, I guess the best way to prove me wrong would be to either build AW from source and run it on your watch, or refer me to someone who's done this.

However, if someone DOES build full AOSP 7.0/7.1 from source, we *could* run the AW apps from other watches and pretend like it's AW2.0. BUT, no one really knows if AW has any framework changes that are not present in AOSP.
[Sony Smartwatch 3] matejdro:
You seem to have more experience with this, so I will trust you on this one.

I only wanted to make a point that from what I have seen, Google does not seem to have two separate branches of Android. Instead they add all features to the main branch and just turn off unneeded ones on specific form factors.
[Sony Smartwatch 3] Scorchgid:
If android wear is a closed sourced system could you explain to me what this is? https://android.googlesource.com/platform/build/+/android-wear-7.1.1_r1
[Sony Smartwatch 3] fonix232:
Android is not GPL, but MIT covered. That's why manufacturers don't have to release their source modifications. Google is totally in their right to not release the source and control the platform (i.e. prevent fragmentation, which they completely ****ed up anyway).

However, the project is NOT impossible. If you build a ROM with the proper branch, and copy over the closed source bits, you could have a mostly working ROM.

That's the baseline for Android Wear in AOSP. Google marked it so it is easier for them to work, and pushed it to the public, so the public parts can be recompiled.

Android Wear = AOSP - unnecessary framework bits + Wear-specific closed source stuff

Hope that equation explains it.
[Sony Smartwatch 3] drakonizer:
Essentially, you are restating what I said. Android Wear is a closed platform.

From your equation, the modified framework (after removing the unnecessary parts) is needed to build Android Wear. Unfortunately, this is not open sourced by Google. How do you propose to build Wear 2.0 and add the closed source stuff?

You'd essentially need to port the framework from a compiled release of Android Wear, which makes the project near impossible, if not impossible.
[Sony Smartwatch 3] fonix232:
Since the framework changes would be neigh inseparable from "regular AOSP" framework, I'm pretty sure Google used framework extensions (i.e. separate jar libraries) for the Wear framework itself. Those bits are pretty much drag'n'drop once compiled (unless they depend on a VERY specific framework version, which should be the one marked with the proper tag and branch), so it is perfectly possible to port.

Worst case scenario, we grab one of the official ROMs for a rectangular Wear2.0 device, and replace first the HAL and kernel with ours, add tetra bits and pieces required to boot, and continue from there.
[Sony Smartwatch 3] Menomis:
Project closed? impossibile to port?
[Sony Smartwatch 3] lekofraggle:
The way I understand it is that Google does not make the closed source stuff, Sony and ti and others do. And, Sony has released the source for those pieces (which is how we have the builds for AW 1.x).

Of course, that is all conjecture.
[Sony Smartwatch 3] matejdro:
Sony did not release any sources, only the kernel which they are required by law.
[Sony Smartwatch 3] drakonizer:
The builds for AW1.x are not built from source.

OEMs have little role to play in the software of Wear devices. Google releases and handles the updates, which is why the kernel sources of tetra are hosted on Google's git and not Sony's developer portal, like every other Sony device.

The only source code released by Sony is the code for the u-boot bootloader used on the tetra. Yes, we have an open source bootloader.
[Sony Smartwatch 3] Menomis:
I don't understand if the porting is having issues or going good. Do we have good chances to get AW 2.0 on our sony smartwatch? Please answer in plain english, I don't even understand what you guys are talking about.

Many thanks.
[Sony Smartwatch 3] Charmandrigo:
There exist another rom project based on Android wear called fitwear OS, which is also in progress to be available on SW3. Could it be possible to use parts of it for the development?

http://fitwear.lianluo.com/about.html
[Sony Smartwatch 3] xpatze85x:
looks interesting :) but is this one based on aw 2.0 or still on 1.x?
[Sony Smartwatch 3] Charmandrigo:
1.5 apparently, but extremely customized
[Sony Smartwatch 3] Riccorbypro:
Hi [MENTION=6126659]PDesire[/MENTION].

I've tried contacting you via Telegram (username doesn't exist) and in PM and I've had no response since i tried almost a month ago, so I'm now going to openly offer help. I will happily make an attempt to help you with this project. I am not inexperienced with Linux or programming, but I'm not the most proficient when it comes to Android development. I would like to contribute where I can though, and hopefully we will be able to make this work.

Please contact me on Telegram via t.me/Riccorbypro so that we can talk.

I look forward to the possibility of us working together...

Richard
[Sony Smartwatch 3] benmelling:
Just a thought...

Hey! Do you reckon that it would be possible to run the Android Wear 2.0 ROM from the Asus ZenWatch 2? I know that the ZW2 is getting the update and that it has very similar specs to the SW3. :)
[Sony Smartwatch 3] xpatze85x:
it's really strange that [MENTION=6126659]PDesire[/MENTION] is posting in other threads but not responding to questios or giving updates here on on of the sw2 threats since weeeeeeeks
[Sony Smartwatch 3] PDesire:
Well, progress is kinda stucked a bit, because of some problems i had last weeks with phone, exams and so on

Please don't ask for progress, if there is something to tell you i will

Your PDesire

---------- Post added at 17:52 ---------- Previous post was at 17:50 ----------

My username is now PDesire_Yandere

so that means https://t.me/PDesire_Yandere

Your PDesire

---------- Post added at 17:56 ---------- Previous post was at 17:52 ----------

And guys: please take patience, i am extremely busy the last times and right now too and i really try my best, honestly i bricked my SW3 for this project like 20 times or more?

I hope for understanding, I know the annoucement ive done is some months old but: What is better for you:

A Working System

or

Some bunch of **** which doesnt work properly

Thanks for understanding

Your PDesire

P.S. I am responding to other Threads though too because this project is not my only one
[Sony Smartwatch 3] fusinef:
thank you so much, for all the work you put into this, PDesire! :)
[Sony Smartwatch 3] PopsicleMud:
Thanks for working on this, PDesire.

I think that sometimes people forget that you're volunteering your time, and the frustration with Sony for abandoning us tends to spill over.
[Sony Smartwatch 3] Charmandrigo:
As how other posters said, this project was too pushed so, it's really too early to make a AW 2.0 custom rom. If something we can do is just waiting.
[Sony Smartwatch 3] Scorchgid:
So it seems to again come down to the following:

We make a version using http://fitwear.lianluo.com/about.html However it will have to be translate it to English, however from a dev perspective the code is in english and translate seems to make enough sense..

By some miracle someone is able to use one of the existing watches out there with 2.0 and reverse engineer it.

We give up. / pray google eventually give us the tools to do it

Note while I am a technical person, I think my second point is likely utter rubbish and is not possible.
[Sony Smartwatch 3] Bradypodion:
Take all the time you need, sir. And thanks for the initiative.

All the best!
[Sony Smartwatch 3] Mikegrmn:
Well, after waiting for a month, I had the time to read more about AW2 update, and after contemplating about it, it almost looks as if AW1.5 could be even better. Not quite sure anymore what advantage AW2 would have over what AW1.5 brings to the table (at least for me).

Sure, it can operate LTE watches, it can have apps directly on the watch (but hey, I just read that now you need to install Gmaps on the watch instead of just relaying the information from the phone --> what amount of memory does this take?!? , you cannot easily sideload music on the watch, if I remember correctly, you can access watch faces more easily --> but yet, I mostly use only one, etc.).

Maybe I just root my SW3 just for the fun of it.

The reviews of AW2 are not really mind blowing imho, neither are the reviews of the newish watches. Let alone the "many" advantages of apps running on the watch.

Maybe this comes from my 2 years using a pebble (the steel first and the time steel a year later). All I need is telling time, notifications, some interaction with my phone and more battery life.

Most of AW2 features are not really necessary for me.

I was craving to buy another watch with AW2, but now I´m not sure any more if this is what I want. Guess I´d loved to have the 2 buttons and crown (I loved the buttons on the Pebble). I think it makes for a more intuitive watch operation.

So what´s everyone else´s opinion? I mean we were all waiting for a port for so long, that most of us must have thought about the OS, or buying a different watch....

Sorry, just trying to break the "good luck with the port" postings here and getting a real discussion started. Maybe it clears everyone´s sight. I mean after AW2 has been a month or two in the press, I think it doesn´t look as shiny as it did pre-release.
[Sony Smartwatch 3] zagonas:
I am also not too impressed by the AW2. Among the main "new" features we have standalone apps. However the SW3 runs already several standalone apps with nearly full functionality. For example, in addition to the basic smartwatch functions I like to use my SW3 as a sports watch. There are many standalone apps for this, I use mostly Endomondo and Swim.com. These two have been working standalone for a while now.

Do I get this right? What further standalone functionality would the AW2 bring? Of course Endomondo needs the phone to upload the workouts and a new smartwatch with LTE might be able to do that all by itself. The SW3 however has no hardware to access the mobile phone network and therefore I do not see any benefit there.

Of course it is nice to run the latest software and of course the AW2 will have better support regarding security updates. But what are the main new features people are looking for? Ages ago Google introduced ART and I was really eager to update my phone to Kitkat in order to be able to enable it. That was really a major improvment. Is there anything like that in the AW2?
[Sony Smartwatch 3] Mikegrmn:
I think the biggest thing about AW2 is the always connected mode with LTE or 3G, depending on the watch you buy. I can see this if you go running, which I don´t. I couldn´t care less about standalone apps on my watch.

I would still be interested in a quicker way to access airplane mode and display settings, or even better, have these two according to a schedule. I have amazing battery life with SW3 if I turn off always on display and airplane mode for the night. I just don´t get it that one cannot just automate this. My times I need this are pretty consistent.

As for the safety, I couldn´t care less for a watch. After all, if it´s only connected to my phone and shows notifications, I don´t know which threats there should be. I would wish the alarm function were better, especially selecting different vibration patterns. For this I have to go to a 3rd party app which works, but the UI is really clunky.
[Sony Smartwatch 3] dersie:
After update my LG-R to AW2 the watch is now unusable, slow and laggy.

I'm very happy to keep my SW3 without AW2, thank you very much Sony to help me to continue to wear an AW watch :)
[Sony Smartwatch 3] Mikegrmn:
It seems we would have a first hand report here on what you probably like/dislike about AW2. Like explaining, why it is now unusable. If it still works, what makes it unusable for you? I´d really be interested in a first hand report.
[Sony Smartwatch 3] dersie:
Just read the LG section. Almost all review about Wear 2 on the LG update this week are the same on unusability. Very slow, lag, drain battery..... Lost feature like 2 clic for theater mode and 3 clic for max brightness, no undo when you remove a card by mistake....

There are also tuto for downgrade from Wear 2 to Wear 1.5 and a lot of users want to downgrade.
[Sony Smartwatch 3] RJASSI21:
I only wanted AW2 for the keyboard feature and the play store on the watch. That was the main feature I saw of it.
[Sony Smartwatch 3] sirrelevant:
Well, this is interesting. Guy's got 2.0 going on zen 2

https://xdaforums.com/zenwatch-2/development/wear-2-development-sparrow-t3581617

I imagine having the same SoC to work with goes a long way to making a port easier.
[Sony Smartwatch 3] darren1:
Apparently Gboard for AW2 can be sideloaded onto AW1.5 via ADB. The apk is available on APkmirror here

https://www.apkmirror.com/apk/googl...d-google-keyboard-1-0-1-android-apk-download/

I haven't tried this myself yet.
[Sony Smartwatch 3] RJASSI21:
Yeah but I have to use adb and if I need to factory reset the watch I lose sideloaded stuff
[Sony Smartwatch 3] :
I installed it, and thank you for the info, but do you know how can I use the keyboard? There is no option when I tap "answer" on notifies
[Sony Smartwatch 3] darren1:
Sorry I don't know as I haven't installed it on my watch yet.
[Sony Smartwatch 3] :
Thanks for your answer anyway!
[Sony Smartwatch 3] sirrelevant:
Works great! Appfour apps work with it. Not sure what else works, but this is nice.
[Sony Smartwatch 3] Menomis:
Can anyone tell me if the porting of AW2.0 is currently on track? or is the project failing/being closed?

I would really appreciate any information about this thread, thanks in advance.
[Sony Smartwatch 3] RJASSI21:
PDesire hasnt said anything about the port being closed he did say that he was busy with other things. I dont think the port has been closed but more so put on hold for some time. I believe this is due to aw2.0 taking so long to release on other watches, also because of how open source android wear is. Apparently its not very open source so its abit more difficult to develop for. Google are also being very annoying as they are mostly responsible for the delay and us not getting AW2.0 anyway. Im sure well still get a port at some point. Since the Asus Zenwatch has had a port im sure this will help alot with the port. I dont know too much about it but im surr what ive said should help tell you that the port will most likely still happen. Just over a very long period of time as aw2.0 was supposed to be released at the start of the year, and shouldve been release on most watches by now.
[Sony Smartwatch 3] :
So I can't use google keyboard without a 3rd party app?
[Sony Smartwatch 3] sirrelevant:
The problem is that when you want to enter text, google apps don't open a text field to trigger a keyboard.
[Sony Smartwatch 3] Z-Prime:
Hey there. Good to see a fellow old Pebbler on here too :D Also good to see you made the same decision as I did after Pebble closed its doors (thanks for nothing Fitbit) last year. Was tricky deciding what to do and what to go with, in finding anything near the Pebble Time that I was so used to. Smartwatch 3 was the closest all rounder by far for sure. I guess, given the way the market is at the moment, there is nothing like my old trusty Pebble Time. The thing became indispensable. That is why i decided to risk a Sony Smartwatch 3

In the end, with the way the Sony Smartwatch 3 announcement went down however in Feb, I can't say I was not disappointed. After places online saying Sony was supporting it, as nothing else was slated, I was shattered when I heard they decided to pull Android 2.0 support (of course the week I got my SW3).

As it is, the SW3 has been sitting in a cupboard since Feb...waiting for a watch strap adapter to be 3d printed by my bro lol.

But I would say that seeing some promise for the future of the SW3 with projects like this by PDesire gives me a little ray of hope. His and the work of others (such as those on Asteroid OS and Fitwear) are appreciated, if on different roads moving forward as to what could be ahead for a smartwatch 3 user..

My biggest question is (aside from the obligatory and to be fair, question of whether we can get a custom/clone 2.0 firmware working in the first place- which trust me, I am NOT asking here lol), is if Sony felt that Android 2.0 caused issues with usability, will independent coders and the active community be able to identify problems, and rectify or eliminate those feature causing issues? I have no idea how all this breaks down, coming from a different field of coding, and have no knowledge as to the structure of Android as a whole, but yeah. I would be happy to live without some of the more complicated and demanding features of wear 2.0 to see a usable system moving forward till a company releases something that finally achieves a decent smartwatch successor, worthy of the name on the market.

It seems that with companies like Motorola pulling out, Huawai's top people thinking that they are pointless, and Google's, shall we say bizarre way Android 2.0 has been released (and subsequently killed 3/4 of their apparent market, with bricked/useless upgraded watches looking at feedback on Playstore and everywhere else), it makes me wonder how long smartwatches will be produced, or if it will be a prolonged hiatus period before tech improves to give people smartwatches they are more readily wanting to buy.
[Sony Smartwatch 3] Mikegrmn:
I think the smartwatch market isn't dead, but in my opinion has been niche from the start.

A lot of people rely on their smartphone for checking time and most do the same for notifications. After all, if you receive some kind of message, for most it seems they need to answer or comment no matter how useless (thinking about my whatsapp group at work).

The real niche would have been the Pebble. A watch first and some added useful tidbits.

I use my watch for deciding on pulling out my phone, multiple different alarms throughout the week and such. With the Pebble I used the media controls a lot in the car as I personally favor buttons over touchscreens while driving. Since switching to the sw3, I run pure nexus Rom because it has music control by long pressing the volume buttons.

I still wonder why so many companies jumped on the bandwagon. It hurt the small niche startups (they are all gone now) and now they kinda halfass the products. Even with its faults (like my time steel almost burning my arm and Pebble not taking my feedback seriously, which is the reason I switched watches) Pebble has been the best smartwatch so far. At least until they thought that fitness tracking would be the most important thing to customers.
[Sony Smartwatch 3] NotTayyeb:
Still in progress?

Just curious whats happening with the AW2.0 port.... I know its a douchey thing to do to ask for an ETA, but there doesnt seem to be any activity recently..... wondering if the devs are still working at it - i know PDesire has exams and stuff but yah....... Is the port still in the works, or have devs scrapped it?

Thanks
[Sony Smartwatch 3] RJASSI21:
I answered something like this before as far as were aware the project is ongoing. I think PDesires just put it on hold nobody has confirmed cancelation so as far as im aware I still believe its ongoing just very slow, not being looked into too much but its still should be a thing unless [MENTION=6126659]PDesire[/MENTION] says otherwise
[Sony Smartwatch 3] barri100:
Hi

I would like to try participate in this proyect, the smartwatch for me is so important like a lot of diabetic person. I am developer but never I cooked a ROM, but I am reading a lot for do a ROM, If i can help in anything about to do the rom, tell me please.

I am trying to send a telegram but the said me that the count is not exist.

Thanks for all!

Regards!!
[Sony Smartwatch 3] gbru2505:
I got this watch thinking that Wear might be good and if I got an unlikely upgrade to 2.0, all the better. I have to say, the device is really slow. Many of the core apps are barely responsive imo. I have a tightly timetabled day and the calendar reminders are useful. Apart from that and telling the time, the watch does nothing better, quicker, or more conveniently than my Nexus 5x does. It's just too slow. Maybe 2.0 will make a difference. But it was only £85, so I won't be too bothered if I just replace it in a year or so. Would I buy a Wear 2.0 watch? I think I'd need to try one first to see if it was significantly more responsive and faster. Then maybe.
[Sony Smartwatch 3] :
Have you tried with custom rom and kernel? Performance and battery are really good to me, I'm keeping 2 cores unactive because performance are good
[Sony Smartwatch 3] Charmandrigo:
Update it to the latest official release, for me it's good.