#grapheneOS #android #movetoearn #soundhsa
One quick note on the technology we are using on reading the pedometer on Android:
In the past reading sensor data was only possible while the app was open. With the latest API (hardware <-> OS) it is possible to close the app and when coming back still have the step count in place.
Differences between iOS and Android:
- for iOS users: they can access step counts even before date of app installation
- Android users can only track their steps after they installed the app and gave permission to read activity data
- Android users must NOT uninstall the app (specially not during a challenge) because they loose access to the sensor data and will start from zero
- on both OS you are "allowed" to fully close the app and reopen it and not loose your step count (only iOS users may uninstall the app and re-install)
Known bugs:
August 2025:
- when coming back to the app the progress on a challenge may show 0. This is typically solved by walking a few steps with the phone or switching tabs in the app front and back.
- some users report having trouble that their move-to-earn tab stopped counting while they still have the steps inside the health tab. This can only be a UI glitch since the access to the step count is the same on both ends. Please reopen the app or switch tabs.
If any serious bugs kept you from participating in a challenge, please repost to us SOUNDHSA (nprofile…5v08)
There will be a next challenge.
We will definitely investigate GrapheneOS a little more as there seems to be some issues lately.
MaxGy
npub1mf…aw6vx
2025-08-28 08:11:45 UTC
Author Public Key
npub1mfkv66vztz2fr47swxhxjt7phhac5vqzl54x7ghhdrjxmjzlu8vqpaw6vxPublished at
2025-08-28 08:11:45 UTCEvent JSON
{
"id": "69982998dbc33d4d8a16d167fbc4c44dac37c3bcf7e9c3014fddf8b1b4abf266",
"pubkey": "da6ccd6982589491d7d071ae692fc1bdfb8a3002fd2a6f22f768e46dc85fe1d8",
"created_at": 1756368705,
"kind": 1,
"tags": [
[
"t",
"grapheneOS"
],
[
"t",
"android"
],
[
"t",
"movetoearn"
],
[
"t",
"soundhsa"
],
[
"p",
"f59d2b10c265f715e51aa30b47f70ef7287a76a4d76c74a566af0b86e242f4f1",
"ws://192.99.46.112:4848",
"mention"
]
],
"content": "#grapheneOS #android #movetoearn #soundhsa\n\n\nOne quick note on the technology we are using on reading the pedometer on Android:\n\nIn the past reading sensor data was only possible while the app was open. With the latest API (hardware \u003c-\u003e OS) it is possible to close the app and when coming back still have the step count in place.\n\nDifferences between iOS and Android:\n\n- for iOS users: they can access step counts even before date of app installation\n- Android users can only track their steps after they installed the app and gave permission to read activity data\n- Android users must NOT uninstall the app (specially not during a challenge) because they loose access to the sensor data and will start from zero\n- on both OS you are \"allowed\" to fully close the app and reopen it and not loose your step count (only iOS users may uninstall the app and re-install)\n\nKnown bugs:\n\nAugust 2025:\n- when coming back to the app the progress on a challenge may show 0. This is typically solved by walking a few steps with the phone or switching tabs in the app front and back.\n\n- some users report having trouble that their move-to-earn tab stopped counting while they still have the steps inside the health tab. This can only be a UI glitch since the access to the step count is the same on both ends. Please reopen the app or switch tabs.\n\nIf any serious bugs kept you from participating in a challenge, please repost to us nostr:nprofile1qythwue69uhnzwfj9cunjt35xchrzvfj8g6rsdpcqywhwumn8ghj7er9wchxummnw3e8qmrp09nhymm4dejzucm0d5qzpava9vgvye0hzhj34gctglmsaaeg0fm2f4mvwjjkdtctsm3y9a83ym5v08 \nThere will be a next challenge.\n\nWe will definitely investigate GrapheneOS a little more as there seems to be some issues lately.\n\n",
"sig": "569e9ad4bc42248bd3afe8896060256621ad6a0bbc5b9fdaab1f1b1f46c0661179f07b35b7bf0b855aa219a94f4fcea51a842c613072afe988c8393254abc78e"
}