• 0 Posts
  • 13 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle
  • randy@lemmy.catoLinux@lemmy.mlAsteroidOS 2.0 Released
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    2 months ago

    AsteroidOS mostly supports watches that come stock with Wear OS, which is a modified version of Android, which, guess what, runs a Linux kernel. These watches are on the more powerful end of the computing spectrum. As you say, there are a lot of smart watches that use pretty lean MCUs, but those aren’t running AsteroidOS or Wear OS, as noted in this FAQ entry.



  • Follow the link and go down to the third point:

    Isn’t this just ReactOS?

    ReactOS tries to reimplement the Windows NT kernel, and that has always been its Achilles heel, holding it back from a hardware compatibility and stability standpoint. The loss32 concept is to achieve a similar-feeling end result to ReactOS, but built on a more usable foundation, using components known to work well (the Linux kernel, WINE, everything that glues those together, and a sprinkling of ReactOS userland niceties). As a bonus, the OS would still technically be a Linux distro, so it would be possible to run Linux software when necessary, something ReactOS can’t do.


  • Follow the link and go down to the third point:

    Isn’t this just ReactOS?

    ReactOS tries to reimplement the Windows NT kernel, and that has always been its Achilles heel, holding it back from a hardware compatibility and stability standpoint. The loss32 concept is to achieve a similar-feeling end result to ReactOS, but built on a more usable foundation, using components known to work well (the Linux kernel, WINE, everything that glues those together, and a sprinkling of ReactOS userland niceties). As a bonus, the OS would still technically be a Linux distro, so it would be possible to run Linux software when necessary, something ReactOS can’t do.


  • Actually, it’s more the opposite. Sorry, I don’t think I explained too well. The watch works just fine on its own without a smartphone. For functions that require phone and watch working together, Gadgetbridge lets them communicate (e.g. when you receive a text message on your phone, Gadgetbridge will let you read the text on your watch).

    The apps on the watch will work with or without a smartphone. However, installing apps from the Bangle app loader requires the watch have a Bluetooth connection to a phone or computer. After apps are installed, they will run even without the Bluetooth connection.

    Finally, note that the Bangle does not have an internet connection on its own; it has no cellular or wi-fi radios on board. So any apps that require a network connection (e.g. weather) will only work when paired to a phone with Gadgetbridge. I think there are other watches with wi-fi, but I’m not familiar with them.




  • That sounds like an issue with the underlying OpenStreetMap data that is used by Organic Maps (and CoMaps, and OsmAnd, and others). Map quality depends on where you are in the world and who is contributing to the maps there. If data is incomplete around you, you could contribute to it (but easier said than done, I know).

    I can’t say why the route would be hours longer than Google maps, but I’ve noticed OsmAnd~ tends to overestimate drive time for me (I think it overestimates delay from traffic lights). Or it could just be that calculating routes on your phone doesn’t always give results as good as calculating routes on Google’s servers.