Database Users

[Q] Can a wear image be built/flashed to a watch?

I have experience modifying the Lollipop AOSP source and building images and flashing them onto devices but I want to modify and build for a wearable.
There is an android-wear-5.0.0_r1 tag and I've downloaded that source code but there's in it which is specific to a wearable - for example there's no new wearable source code, and the lunch menu contains android device lunch items not wearable device lunch items (i.e. the lunch menu doesn't contain dory, sprat, minnow build options) so there's no way of building it for a wearable.
Does anybody know if its possible to build an image for a wearable?

mungbeans said:
I have experience modifying the Lollipop AOSP source and building images and flashing them onto devices but I want to modify and build for a wearable.
There is an android-wear-5.0.0_r1 tag and I've downloaded that source code but there's in it which is specific to a wearable - for example there's no new wearable source code, and the lunch menu contains android device lunch items not wearable device lunch items (i.e. the lunch menu doesn't contain dory, sprat, minnow build options) so there's no way of building it for a wearable.
Does anybody know if its possible to build an image for a wearable?
Click to expand...
Click to collapse
Were you able to accomplish anything? We are also working with a custom ROM but we don't see any way how we can merge and build the branch Android W 5.0.0_r1. I don't think is the full source for Android Wear

[CALLING DEVELOPERS] Jolla's Sailfish OS port continuity (GNU/Linux)

Hey fellows!
A screenshot of another older phone for attention: https://twitter.com/sledgeSim/status/625235917486338048
yuga's Sailfish OS port was shaping up during past months, by @oleid, but he got carried away by his studies. Now that Sailfish OS UX 2.0 is on the doorstep, is a good time to restart a port! If you're completely new: https://sailfishos.org/hadk
We also just provided LED notification support for Xperia Z, but this needs testing: https://github.com/nemomobile/mce-plugin-libhybris/pull/16
Original porter left all documentation here: https://wiki.merproject.org/wiki/Adaptations/libhybris/Install_SailfishOS_for_yuga (including link to automated script) and modem hurdles: http://piratepad.net/hadk-yuga
Pop by to #sailfishos-porters and we'll guide you through if you want to make a build a new Sailfish OS version for your beloved phone, and also make those phonecalls work
Cheers!

[ROM][XT16xx][7.1.0][CyanMod 14.1 [MotoG4 / G4 Plus] - Where are the BSP files?

Hello again,
Again I post here because I am denied posting in the correct spot. I suppose this silly denial will end, eventually.
I have a question for @Silesh.Nair :
In the dev thread, you tell somebody that he can build CM14.1 from source himself, using that guide:
http://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
In a further post, you seem to indicate that the Moto G4 Plus build is obtained direct from the CM source repo.
I found that github repo for CM on the moto G4: https://github.com/CyanogenMod/android_device_motorola_athene
Unfortunately, the latest tag is marked CM 13 ... and there is nowhere to find the BSP files for CM 14.1.
Now, since it seems quite evident to you, but not at all for me, could you please kindly tell us where we can obtain the BSP files (device tree, vendor, kernel) for CM14.1 - Athene?
Thank you for your understanding my confusion.

You cannot post on a dev forum till you get to 10 posts.
You obviously cannot build cm14.1 using the device tree in cm github.
You have to sync the sources and add your device, vendor and kernel repos from here in your local manifest file.

Thank you
Silesh.Nair said:
You cannot post on a dev forum till you get to 10 posts.
You obviously cannot build cm14.1 using the device tree in cm github.
You have to sync the sources and add your device, vendor and kernel repos from here in your local manifest file.
Click to expand...
Click to collapse
Thank you for this snippet of information. I will look further into it.
In the world of embedded systems, when you have a generic operating system that can be used with many different hardware targets, a Board Support Package ("BSP") is the set of files that are required to build the generic OS on a specific target. For example here the BSP is all the files that are specific for the Moto G4/Plus (e.g. device tree, vendor, kernel), once you have a generic CM 14.1 distribution to start with. "BSP" refers to all the target-specific files that would not be the same on another target (i.e. a different phone).
I think this nomenclature is quite appropriate for the subject at hand.

Suggestions for smartwatches with active open source rom support

Hello all,
I have found some watches with open source Roms here at xda-devs but I am not sure about how active the developers are and if a Rom from months back have the required security kernel patches (for example).
It would be nice if this thread gathered all (or most) of the information about smartwatches that have good open source Rom support.

Clang error when attempting to build Halium systemimage for Amazon Fire HD 8 (2018)

Hello! This is my first post so please forgive me if I did not write this concisely enough ?
I am attempting to port Ubuntu Touch aka Halium-7.0 for the Amazon Fire HD 8 (2018 16gb model, Codename: karnak). I have adapted the device, common, kernel and vendor trees from Kaijones's repository here. I am keeping track of all the changes I made over on my own github in the following repositories:
Device Tree
Common Tree
Kernel Tree
Vendor Tree
The error: https://del.dog/lofudanaco.txt
What I've tried to do so far: I've come across this article that claims the issue is with the C compiler itself, providing some code to potentially fix the bug, however, I have doubts as to the actual nature of the problem and whether this solution is relevant to my issue or not. Any help is appreciated. TIA!