Skip to content
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

Replacing switching move mode with Easer to Automation / Problem with both #1996

Open
vsatmydynipnet opened this issue Mar 7, 2025 · 0 comments

Comments

@vsatmydynipnet
Copy link

For a long time I was running Owntracks on LineageOS/rooted switching move mode with Easer as written here

#1096

I switched to monitoring 2 when leaving the home wifi and to 0 if connected to home wifi.

Now I am working on a Pixel 8a running GrapheneOS (Android 15) and Easer stopped to work using the commands below. The commands

am start-service -a org.owntracks.android.CHANGE_MONITORING --ei monitoring 2

works on TermUX without the device beeing routed. The Easer setup does nothing. So I tried to install

https://f-droid.org/de/packages/com.jens.automation2/

and add a perAction startService but also this does not change the move mode. Is there any known problem on Adroid15/GrapheneOS with automating switching the move mode? Unsure I enter stuff there correct.

Thank you for any hint.

Start

am start -n org.owntracks.android/.ui.map.MapActivity

Stop

am force-stop org.owntracks.android

Change Mode

am start-service -a org.owntracks.android.CHANGE_MONITORING --ei monitoring 2

Links

https://owntracks.org/booklet/features/android/

Modes

Quiet monitoring:-1
Manual monitoring:0
Significant Changes monitoring:1
Move monitoring:2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant