Hacker News Reader

Comment by konraditurbe | Hacker News Reader

You loose waterproofing, and Moto 360 has a TI chip which makes it difficult to port Asteroid OS to it.

Thanks for mentioning it, I don't care about waterproofing but I intended to attempt a port (I get a librem5 as soon as they're out so my android wear will be basically useless by then), so the chip thing may be a problem.

Do you know if anyone documented a previous attempt somewhere? Or do you have any other knowledge that makes you say this will be a problem?

https://asteroidos.org/wiki/porting-guide/

You can try, the sony sw3 has a bcom chip and has still some bugs.

Yes, that's what I read before deciding to try it :)

But my question was more about what you were saying about the TI chip, what makes you say it will be a problem? (eg different architecture, known limitations, etc)

Well, since it uses Libhybris for interfacing with Android it should not be a problem to port it, but, the advantage of the snapdragon chips is that most watches use the same chip so the code was reusable (eg: g watch > g watch r), so you might encounter some issues that are not present on the existing ported watches. Fortunately the source code for the kernel on the omap3 is available for download: http://processors.wiki.ti.com/index.php/OMAP3_GIT_Linux_Kern...

Awesome, thanks for the info!

thanks to google/motorola build quality (which was during the phase moto360 and motoX came out) the back of both those devices are 100% guaranteed to be cracked already and any waterproofing claims gone.

but you are rigth on the TI chip. not even wearOS was updated past the release version there.

Reply on news.ycombinator.com