FakeTraveler icon indicating copy to clipboard operation
FakeTraveler copied to clipboard

Implement edge-to-edge

Open gitty323 opened this issue 9 months ago • 6 comments

Description

On my Pixel 8 Pro, there are no buttons to interact with anymore since the 2.0 redesign. Image

To reproduce

Steps to reproduce the behaviour:

  1. Update to 2.0
  2. Open the app

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

gitty323 avatar Mar 06 '25 16:03 gitty323

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. Will investigate!

ThexXTURBOXx avatar Mar 06 '25 16:03 ThexXTURBOXx

Mine doesn't even have a map. (Pixel 8 running GrapheneOS. The app has Network permissions disabled)

Image

An-anonymous-coder avatar Mar 06 '25 17:03 An-anonymous-coder

Mine doesn't even have a map. (Pixel 8 running GrapheneOS. The app has Network permissions disabled)

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)

ThexXTURBOXx avatar Mar 06 '25 17:03 ThexXTURBOXx

A local download of OSM could be added to the app, couldn't it?

Before the redesign the app worked fully offline.

An-anonymous-coder avatar Mar 06 '25 17:03 An-anonymous-coder

A local download of OSM could be added to the app, couldn't it?

That is rather infeasible as it takes a huge amount of space:

Image

Before the redesign the app worked fully offline.

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). Obviously, the app itself still works, including all the functions, except for the map. But you can manually set a mock location using geo coordinates.

Image

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.

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 windowOptOutEdgeToEdgeEnforcement, but that would just be a workaround. I will try to properly migrate - but if that fails, I will use the workaround for now...

ThexXTURBOXx avatar Mar 06 '25 18:03 ThexXTURBOXx

I will send version 2.1.0 off to FDroid now - should be public in at most a week. I deployed the workaround for now as it needs a bit more tinkering to fully fix edge-to-edge...

ThexXTURBOXx avatar Mar 06 '25 18:03 ThexXTURBOXx

Having the same problem on my Pixel 9 running GraphineOS (version 2.2.0 from F-Droid)

Screenshot_20250716-044152_1.png

Nrwh1 avatar Jul 16 '25 08:07 Nrwh1

Finally done, will send off to FDroid now

ThexXTURBOXx avatar Jul 16 '25 16:07 ThexXTURBOXx