FORUMS
Remove All Ads from XDA

Android Wear 2.0 for SmartWatch 3 port progress Thread & Creation of OSS project

1,550 posts
Thanks Meter: 5,941
 
Thread Closed Email Thread
Hello,


As some people heard, i really try to get Android Wear 2.0 for our beloved SmartWatch 3.

And it's possible, sources, device trees, all exist to build a working own compiled Android Wear 2.0.


So this thread tells about the current process of the port


PROGRESS
Code:
Repo synced 
First build finished (not buildable yet due no blobs included 
GAPPS Porting in progress 
Fixed to 99% the device tree
Updating Blobs to M1D64T in progress 
Using own Device tree

SOURCES
Device Tree for tetra:
https://github.com/Sony-SmartWatch-3...eng_prerelease

Device Kernel for tetra (unmodified):
https://android.googlesource.com/ker...ar-6.0.1_r0.99
(we can use MM kernel on Nougat too, maybe some patches needed but that's okay)

Prebuilts/Blobs for tetra:
https://github.com/Sony-SmartWatch-3...rebuilts_tetra

For Discussions go to this thread please: https://forum.xda-developers.com/sma...r-2-0-t3565693


If you want to help me on this project, write to me via telegram: https://t.me/PDesire
The Following 127 Users Say Thank You to PDesire For This Useful Post: [ View ]
 
 
23rd February 2017, 09:50 PM |#2  
Junior Member
Thanks Meter: 1
 
More
I need that so much any ETA ?
By the way keep up the good work !
23rd February 2017, 11:51 PM |#3  
zippy01's Avatar
Senior Member
Thanks Meter: 359
 
More
Nice to see someone is working on this

Sent from my Sony Xperia Z5 using XDA Labs
24th February 2017, 03:20 AM |#4  
Junior Member
Thanks Meter: 3
 
More
Thanks for your job.

Enviado desde mi Redmi Note 3 mediante Tapatalk
24th February 2017, 03:33 AM |#5  
felipeacydc's Avatar
Member
Flag santiago
Thanks Meter: 21
 
More
great!!! thanks
24th February 2017, 06:01 AM |#6  
Member
Thanks Meter: 3
 
More
Dear PDesire,,

My support can be only moral.....

And I hoping good news soon from you

Thx again for your great hard work
24th February 2017, 08:49 AM |#7  
HEKER510's Avatar
Senior Member
Thanks Meter: 183
 
More
thankx you great hard work and good luck my friend
24th February 2017, 08:53 AM |#8  
drakonizer's Avatar
Forum Moderator
Flag Death Star
Thanks Meter: 2,367
 
Donate to Me
More
I checked out your device tree. It looks like it's based off an Open Devices tree. I don't think we need the following lines
Code:
include device/sony/common-headers/KernelHeaders.mk
-include device/sony/common-kernel/KernelConfig.mk
in BoardConfig.mk.
Also, what about the HALs? Asteroid OS used the system.img from a stock build, but we will need to build from source. I do not think it is open source, as it is not available on google git servers.

EDIT: I do not think building from source will work. This is what I found the Google Android building group:
Quote:

Certain components of Android (and therefore Wear) come from third parties and have licenses which require the source code to be made available (e.g. the Linux kernel). The components made available via the AOSP repositories for releases like Wear are, afaik, the components which have that type of license.

Wear is a release which has taken the same path as Honeycomb. I can understand that for open source fans and people looking to tinker with a working system it’s somewhat disappointing to see, but those are the choices Google has made.

Looks like the only way to go forward is to port it from a pre-compiled version for another watch, like they did for the Galaxy Gear devices.

EDIT 2: Refer:
https://groups.google.com/forum/#!se...g/-KexIWTCDwAJ
https://groups.google.com/forum/#!se...s/USxAUaKVAwAJ

These sources are incomplete and only include GPL licensed projects. It is not the complete source, just like google releases preview sources for AOSP preview builds (M, N etc). I suggest you not waste your quota in downloading the source.
The Following User Says Thank You to drakonizer For This Useful Post: [ View ] Gift drakonizer Ad-Free
24th February 2017, 11:53 AM |#9  
PDesire's Avatar
OP Recognized Developer / Recognized Contributor
Flag Frankfurt am Main
Thanks Meter: 5,941
 
Donate to Me
More
Quote:
Originally Posted by drakonizer

I checked out your device tree. It looks like it's based off an Open Devices tree. I don't think we need the following lines

Code:
include device/sony/common-headers/KernelHeaders.mk
-include device/sony/common-kernel/KernelConfig.mk
in BoardConfig.mk.
Also, what about the HALs? Asteroid OS used the system.img from a stock build, but we will need to build from source. I do not think it is open source, as it is not available on google git servers.

Yeah I've seen these, and already fixed. Patch comes soon.
Things for WLAN and BT for example are on google repo too and if a library or something is missing we can use it from M1D64T

Quote:


EDIT: I do not think building from source will work. This is what I found the Google Android building group:

Looks like the only way to go forward is to port it from a pre-compiled version for another watch, like they did for the Galaxy Gear devices.

EDIT 2: Refer:
https://groups.google.com/forum/#!se...g/-KexIWTCDwAJ
https://groups.google.com/forum/#!se...s/USxAUaKVAwAJ

These sources are incomplete and only include GPL licensed projects. It is not the complete source, just like google releases preview sources for AOSP preview builds (M, N etc). I suggest you not waste your quota in downloading the source.

Lel then I can't understand why the build is working xD at least I am building in time and already 14% finished

I know some libs we have to grab from the Marshmallow FW but that shouldn't be a big deal


At least we also need some things from Preview 2 so we can get our AW 2.0 Preview 2 working


So I try my best to grab much from source and if required also from FW, but all in all its possible for our SmartWatch 3 to get Android Wear 2.0


Your PDesire
The Following 16 Users Say Thank You to PDesire For This Useful Post: [ View ]
24th February 2017, 02:42 PM |#10  
Member
Thanks Meter: 20
 
More
but there's one thing i don't understand ... why r u using preview 2 instead of a feature complete newer version or the final version?
The Following 3 Users Say Thank You to xpatze85x For This Useful Post: [ View ] Gift xpatze85x Ad-Free
24th February 2017, 03:17 PM |#11  
Junior Member
Thanks Meter: 12
 
More
Quote:
Originally Posted by xpatze85x

but there's one thing i don't understand ... why r u using preview 2 instead of a feature complete newer version or the final version?

Because there aren't any sources of the final version.
Thread Closed Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes