~mil

http://milesalan.com

I'm Miles, also see: http://milesalan.com

My nick is mla on IRC.

Trackers

~mil/sxmo-tickets

Last active 4 days ago

~mil/mepo-tickets

Last active a month ago

~mil/mobroute-tickets

Last active 3 months ago

~mil/tlml-tickets

Last active 6 months ago

~mil/framebufferphone-tickets

Last active 1 year, 4 months ago

#53 libpng error: IDAT: insufficient memory crash a month ago

Comment by ~mil on ~mil/mepo-tickets

Unable to replicate.

REPORTED RESOLVED CLOSED

#72 Document How to Configure Accurate Location Gathering Support/GPS a month ago

docs added by ~mil on ~mil/mepo-tickets

#71 Crashed on start on Mobian (mobian-sm7225-phosh-20230806) on Fairphone 4 a month ago

Comment by ~mil on ~mil/mepo-tickets

I wonder if this is a permission error related to how Flatpak is setup globally on Mobian (e.g. do other Flatpak's have internet access?). I haven't had time to test (besides testing Flatpak locally / e.g. not directly on Mobian) but what your describing with showing 'queueing' and alternating is essentially how mepo acts when the application doesn't have internet connection or very slow connection (e.g. hitting timeout limit for tile downloads, failing and restarting).

Also - I don't think this would necessarily change things but I did publish a new Flatpak for the 1.2.0 release a few days ago so you may want to give that a shot as well.

Regarding offline usage - you can download tiles via mepo itself (caveat: #62) and don't necessarily need a tileserver (although local tileserver will work too if you want to go that route); see userguide for downloading tiles for later offline usage via mepo: http://mepo.milesalan.com/userguide.html#offline-usage

#72 Document How to Configure Accurate Location Gathering Support/GPS a month ago

Comment by ~mil on ~mil/mepo-tickets

So as mentioned in #73 you should just use geoclue; if gpsd is properly configured, geoclue will use gpsd implicitly (and I want to remove gpsd altogether from mepo's codebase).

As far as configuring GPS / gpsd, that's a per-device concern and out-of-scope for mepo itself; but I do agree mepo's documentation could use some work and be more helpful in pointing users to guide(s) on how to properly configure gpsd for their device on the postmarketOS wiki etc.

#73 Deprecate coordsviagpsd in favor of geoclue a month ago

refactoring added by ~mil on ~mil/mepo-tickets

#73 Deprecate coordsviagpsd in favor of geoclue a month ago

Ticket created by ~mil on ~mil/mepo-tickets

Raised in #72 in reality we should just deprecate / remove all coordsviagpsd functionality as geoclue will use gpsd in anycase. The gpsd CLI logic (and extra adhoc configuration) just adds extra complexity and confusion for end-users.

If GPSD is properly configured, geoclue will use it properly either way and pass this through for mepo.

#70 Make it more obvious to user how to set ENV variables a month ago

Comment by ~mil on ~mil/mepo-tickets

Let's pickup discussion on GPS on https://todo.sr.ht/~mil/mepo-tickets/72 as this ticket was more about setting ENV vars.

REPORTED RESOLVED CLOSED

#72 Document How to Configure Accurate Location Gathering Support/GPS a month ago

Comment by ~mil on ~mil/mepo-tickets

I think pointing to the postmarketOS wiki or a similar guide on how to configure GPS would be the best course of action here.

Currently the main documentation on mepo userguide is: http://mepo.milesalan.com/userguide.html#repositioning-the-map

#72 Document How to Configure Accurate Location Gathering Support/GPS a month ago

user-feedback added by ~mil on ~mil/mepo-tickets

#43 Automatically detect if hardware rendering not available and use software rendering a month ago

Comment by ~mil on ~mil/mepo-tickets

Fixed in 1.2.0 release.

REPORTED RESOLVED FIXED