AtmosphericIgnition

Results 32 comments of AtmosphericIgnition

I have asked in the GrapheneOS Matrix, and searched their git repository, and I could not find any place where they changed the stock AOSP power management system.

I'm running the latest RC, and just had the bug occur again. I know that my phone definitely had a GNSS fix while NeoStumbler was not recording because of this...

I have experienced crashes during the day related to #237, I have experienced this well before I ever had issues like #237 describes.

Couldn't reproduce on the latest version.

1. I'll let you know if the chart gets any more broken when I add more days. 2. I was going to suggest this, but didn't want to over complicate...

This is what the tab looks like after another week: ![Screenshot_20240729-172337](https://github.com/user-attachments/assets/3985b48d-b9c1-46c6-99ec-683c3aebf3b6)

I would just like to say that if this gets implemented, I would really like if the accurate timestamps were still recorded to NeoStumbler's database, as I find the data...

I asked about how this would affect BeaconDB in the Matrix room, this is the response from the BeaconDB lead dev: "Nope, in the future the server might make use...

If BeaconDB no longer depends on accurate timestamps (and no other services I know of accepting submissions in the Ichnaea format), would it make sense to just have the one...