-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement edge-to-edge #80
Comments
Interesting - I have seen this in an emulator running the current beta of Android 16, but thought it would be okay on a physical device. Apparently not. |
The map needs a working internet connection to work, there is no way around that (other than migrating to a Google Maps implementation, but I will stay with OSM) |
A local download of OSM could be added to the app, couldn't it? Before the redesign the app worked fully offline. |
That is rather infeasible as it takes a huge amount of space:
Actually, no. This would not have been possible in any way - and after some testing, I can confirm that the map did not work offline (see screenshot below).
Found out that this is due to the new edge-to-edge layout, which is forced with target SDK 35. One can opt out using |
for now... At some point we need to fix the layout to be future-proof! Related: #80
I will send version 2.1.0 off to FDroid now - should be public in at most a week. |
Description
On my Pixel 8 Pro, there are no buttons to interact with anymore since the 2.0 redesign.

To reproduce
Steps to reproduce the behaviour:
Expected behaviour
There are buttons to set the location etc.
Screenshots
No response
Logcat
No response
Additional context
No response
Device
Pixel 8 Pro
OS
GrapheneOS 2025030300
FakeTraveler version
2.0.0
The text was updated successfully, but these errors were encountered: