• 1 Post
  • 89 Comments
Joined 3 years ago
cake
Cake day: June 22nd, 2023

help-circle




  • Osmand~ and CoMaps (fork of Organic Maps) use the same map data, but different rendering/routing engines.

    Osmand~ is everything and the kitchen sink. Any feature you can think of, it probably has

    CoMaps is just the basics for 85% of people. It’s much simpler, its map drawing is much faster (no lag while waiting for tiles/branches/labels like Osmand), and much faster on-device routing than Osmand.







  • Because they’re objectively better on a desktop.

    Your compositor should control the window - if the poorly implemented client hangs, you can just click the server-side close button a couple times and get the “shall I force close this?” popup

    The only reason for CSD is touch interfaces on small screens. In that case, you still need some other interface to handle misbehaving applications, but they tend to be harder to use, e.g. the removal of home/back buttons on Android

    Edit: If you’re trying to improve on SSD, you could consider some model where the client can register some actions it would like to have displayed to the compositor, and the compositor can relay clicks back to the client. In this scheme, the compositor still owns the title bar, but the client can request special decorations







  • The fucking gas lighting in this response

    Google provides more assistance to open source software projects than almost any other organization, and these debates are more likely to drive away potential sponsors than to attract them

    “We ran AI that may or may not have found a legitimate issue, and you’re not looking into it for us fast enough. That’s going to drive away new volunteers that we need”



  • Maybe easier to another suggestion, you’re probably using a systemd based distros -

    journalctl -b -1 will show you the logs from the previous boot, so you could check that after resetting to see if anything was logged

    For some other ideas to narrow down where the issue is…

    If you’re stuck in the frozen state, you can Ctrl+alt+delete 7+ times quickly to tell systemd to try to restart the system. If this works, it means init was still able to process messages

    If that doesn’t work, you could enable Magic Sysrq Key (if disabled in your distro), and then use the key sequence REISUB to try to see if the kernel is still responding and can reset the system