search

bailuk / AAT

Another Activity Tracker for Android
https://bailu.ch/aat
GNU General Public License v3.0
150 stars 41 forks source link

V1.25 and 1.25.2 have EPERM error on S23 device #162

Open petherfile opened 1 month ago

petherfile commented 1 month ago

After installing V1.25 + on my device I'm getting EPERM errors and tracking will not start.

Screenshot:

image

Basically nothing I try in the application works and you just see that error all the time.

back to V1.24 and the issue disappears.

It appears the OS is refusing to pick up on required permission in V1.25+ any mention of file permissions or anything similar disappear from the list of permissions that can be allowed.

Screenshot of V1.25.2 permissions on my device. This is a complete list of available permissions:

Screenshot_20240528_114057_Permission controllerV1 25 2

Screenshot of V1.24 permissions on same device. This list is not complete (too long), but shows the file permissions:

Screenshot_20240528_114428_Permission controllerV1 24

Not sure if this could be something extra Samsung have done? (knox thing?) Running android V14.

mats1729 commented 1 month ago

I have the same problem on a Xiaomi phone (Android 14, Xiaomi HyperOS), so it is not about Samsung. The app can read old files, but not write new ones.

bailuk commented 4 weeks ago

The reason for this change is that v1.24 had targetSdk = 29 and v1.25 moved to targetSdk = 33.

Google added some privacy features in Android 11 (API level 30) which are documented here: https://developer.android.com/about/versions/11/privacy

Overview of SDK/API changes here: https://developer.android.com/tools/releases/platforms

Heres what you can try:

  1. Use SAF to access your aat_data folder:
    pick_saf
  2. ... or copy tracks to app folder where you have permission. And select internal folder (first or second entry in screenshot)
  3. ... or see if there are some extra permission (this is also needed to enable GPS tracking in background #120):
    all-permission-select