dennisguse - Network

#OpenTracks is now available via #fdroid as reproducible build! 🚀 https://f-droid.org/packages/de.dennisguse.opentracks.playstoreThanks...

#OpenTracks is now available via #fdroid as reproducible build! 🚀

https://f-droid.org/packages/de.dennisguse.opentracks.playstore

Thanks to @storchp making his apps reproducible and then nudging me to take a look again (after quite some years).

Also https://gitlab.com/licaon-kter for enduring 5x OpenTracks releases before getting everything right!

For historians: https://github.com/OpenTracksApp/OpenTracks/issues/418

#38C3 if somebody wants to playaround with some Bluetooth sensors. I brought some fancy ones:* Flybeeper pressure sensor (barometer)* Polar...

#38C3 if somebody wants to playaround with some Bluetooth sensors. I brought some fancy ones:
* Flybeeper pressure sensor (barometer)
* Polar running sensors (distance and cadence)
* Polar OH1 (heart rate)
* Xioami Temperature and Humidity Monitor 2

In February, #OpenTracks got a new amazing sticker design Design was done by: https://github.com/ch3thanhsIf you want, you can order these...

In February, #OpenTracks got a new amazing sticker design

Design was done by: https://github.com/ch3thanhs

If you want, you can order these stickers for yourself: https://stickerapp.de/customer/reorder/3047172/992ce4e3e5f925

Version v4.12.3 released that contains a fix for this issue.https://github.com/OpenTracksApp/OpenTracks/releases/tag/v4.12.3Nightly will...

Version v4.12.3 released that contains a fix for this issue.

https://github.com/OpenTracksApp/OpenTracks/releases/tag/v4.12.3

Nightly will available in the next minutes.
Playstore release is pending review (likely Monday).
F-Droid may take longer.

#PSA#OpenTracks has a critical issue (aka data recorded is incorrect). Affected version: likely v4.12.XRecommendation: remain on prior...

#PSA

#OpenTracks has a critical issue (aka data recorded is incorrect).
Affected version: likely v4.12.X

Recommendation: remain on prior versions (or downgrade).

Current status: gathering evidence to figure out what the problem is.

More Infos: https://github.com/OpenTracksApp/OpenTracks/issues/1898

🚀🚀🚀🚀🚀🚀🚀 As we all know, the most complicated task in IT is naming things, right?I am building a (tiny) Android app that...

🚀🚀🚀🚀🚀🚀🚀

As we all know, the most complicated task in IT is naming things, right?

I am building a (tiny) Android app that will expose the device's sensor data via Bluetooth LE using standardized BLE protocols. So, GPS would be exposed via "location and navigation profile" and the barometer using "environmental sensing service".

What is a useful name for this app?

PS/ proof of concept is implemented (X-Mas 24) and real implementation is almost done - I juuusstt need a name.

😜

#Boost

#OSMDashboard just received a big update: it is now way faster - scrolling is now even fun on my good old Nexus 5. This is now working as...

#OSMDashboard just received a big update: it is now way faster - scrolling is now even fun on my good old Nexus 5.

This is now working as
@storchp migrated from Mapsforge to Mapsforge VTM: https://github.com/mapsforge/vtm

@storchp it was fun helping you

#OpenTracks

@storchp The #OpenTracks and the #OSMDashboard logo have made it :)https://icondb.co/icons/opentracks/No clue how uploaded it....

@storchp The #OpenTracks and the #OSMDashboard logo have made it :)

https://icondb.co/icons/opentracks/

No clue how uploaded it....

#OpenTracks v4.9.0 was just released.Please note: it contains a BREAKING CHANGE.Namingly: how not moving aka idle is determined.Now an idle...

#OpenTracks v4.9.0 was just released.

Please note: it contains a BREAKING CHANGE.

Namingly: how not moving aka idle is determined.
Now an idle duration is used rather than "reported speed is too low".

More infos here: https://github.com/OpenTracksApp/OpenTracks/releases/tag/v4.9.0

Somebody interested in checking #OpenTracks UI revamp (aka migration to MaterialDesign 3)?Then you shall not be disappointed:...

Somebody interested in checking #OpenTracks UI revamp (aka migration to MaterialDesign 3)?

Then you shall not be disappointed: https://github.com/OpenTracksApp/OpenTracks/pull/1597

Feedback welcome

Recently, we got some weird pull requests for #OpenTracks.Those contain quite a number of commits (>100) and pretend to fix technical...

Recently, we got some weird pull requests for #OpenTracks.
Those contain quite a number of commits (>100) and pretend to fix technical debt.
However, in quite some cases this will break things.
And there are more than five GitHub accounts doing this.

Has anybody any idea what might be going on?
Is this some kind of SPAM or what are people doing?

Here is one example: https://github.com/OpenTracksApp/OpenTracks/pull/1467

#OpenTracks could use a new sticker?Back in 2019, I created the current logo (with some help from a fellow designer).Is anybody interested...

#OpenTracks could use a new sticker?
Back in 2019, I created the current logo (with some help from a fellow designer).

Is anybody interested to create a new design?

#Boost

https://github.com/OpenTracksApp/OpenTracks/issues/1444

@storchp welcome back ;)

@storchp welcome back ;)

@lbenedix welcome back ;)

@lbenedix welcome back ;)

6. Crashs are reported from different devices and Android versionsHypothesis: could it be that devices with PlayStore present who installed...

6. Crashs are reported from different devices and Android versions

Hypothesis: could it be that devices with PlayStore present who installed #OpenTracks via #Fdroid are responsible for these crash reports?

If this is true, it is likely that these users never installed this appId.

AppId is de.dennisguse.opentracks (Old Play store and F-Droid) and de.dennisguse.opentracks.playstore.

PS signing key for PlayStore de.dennisguse.opentracks was destroyed purposefully in August 2019.

So, some more insights.1. There are crashs reported for newer versions of OpenTracks to the appId2. There are also older versions reporting...

So, some more insights.

1. There are crashs reported for newer versions of OpenTracks to the appId
2. There are also older versions reporting to this appId (still have a BootReceiver)
3. Data is only shown in PlayStore app provided by Google (not on play.google.com/publish)
4. Crash reports started about 4 weeks ago
5. There was always at least 1 active installation for this appId (not me)

Info: F-Droid and this old PlayStore app use the same appId

Back in 2019, I released #OpenTracks via the PlayStore (just playing around). Some days later I needed to recreate the application for the...

Back in 2019, I released #OpenTracks via the PlayStore (just playing around). Some days later I needed to recreate the application for the PlayStore.

This first application still has one user.
And it is used: got some crash reports.
Technically it is OpenTracks 3.0.0 and the packageId is the same as on Fdroid.

Don't know what this person is doing and I am pretty sure it isn't me ;)

I got some feedback andddddd it is working 🥳 Will be in tomorrows nightly.

I got some feedback andddddd it is working 🥳
Will be in tomorrows nightly.

PS I actually never tested the code so far as I don't have access to the necessary hardware. So, it might be working or not.Let's...

PS I actually never tested the code so far as I don't have access to the necessary hardware. So, it might be working or not.
Let's see.

Testers for #OpenTracks needed.I have a first draft to fetch cadence from powermeter (cycling). So, if you have powermeter that is attached...

Testers for #OpenTracks needed.

I have a first draft to fetch cadence from powermeter (cycling). So, if you have powermeter that is attached to the crank, it would be awesome if you could test if this pull request works for you: https://github.com/OpenTracksApp/OpenTracks/pull/1372

What should work:
* Settings->Sensors->Cycling cadence: the powermeter should be listed here (independent if it can provide cadence)
* Settings->Sensors->Cycling power: as well
* When recording a track, cadence and power should be shown.