The toggle could have a third state (grayed out) to indicate that a startup or shutdown process is in progress. To be honest, also the two startup/shutdown buttons in Android App support settings could be replaced by the same toggle.
You can already put a shortcut on the top menu that takes you directly to the android support page in the settings app. Not as neat, but its what I use several times a day when I have to stop/start Android to get internet connectivity back when it screws itself.
Or a little Android robot icon next to the toggle could rotate in little circles until the on-off or off-on state change has completed!
And if the state change didn’t complete successfully the little robot would stop rotating, but land on its head instead of upright when it did work …
Its’getting complex for a switch…I can see why the current design was chosen, but I like your idea! :
I’ve been using aliendalvik button for this. It worked quite well on Xperia X, on the X10 II it leaves a bit to be desired, but is still ok to stop android support. Starting isn’t that reliable, but can also be achieved by starting an android app.
@PeperJohnny thank you for the idea! I was missing this icon too, I took it from my XperiaX as one more setting, the orientation bar which you can select between dynamic-portrait-landscape and I prefer it from the “lock orientation button”. Unfortunately on the tries I copied the file “/usr/share/jolla-settings/pages/android-runtime/android.qml” from my XperiaX to X 10 ii . Could you send it to me please? Thank you in advance
Hi @PeperJohnny, where do I have to place the files? I am quite new to Sailfish and the Qt universe. Thanks in advance
If I understand the spec correctly you need to copy the .qml files to /usr/share/jolla-settings/pages/aliendalvik/
and the .json file to /usr/share/jolla-settings/entries/
You could also try to build the package yourself with the SDK tool Building packages - advanced techniques | Sailfish OS Documentation
Well, yes and no. We know starting AD takes time. Couldn’t this switch just show a waiting sign before the start of AD is being completed and then only turn to a started state?
Another thing that makes me wonder (and tear my hair) why it’s not implemented after all these years…
If you are still interesting on it and you are using patchmanager, you can try “Android Support button” patch from Catalog Web
Didn’t work that well on my X10III. It gave me one more torch button instead of a android button.
Edit:
Reboot made it happen the right way. Looks like it’s working fine now. Thanks!
Thank you for the offer but I don’t use PatchManager and won’t in the near future as my phone is my main device and I can’t take the risk of adding fiddle software.
Why on earth is a dev. capable of puling it off and Jolla can’t. Is it just time?
Nicely done @carmenfdezb - I don’t use patchmanager any more, to many problems for me personally. So instead, i added the files you provide for your patch and now I have a working stop-start button for Android runtime
It’s not a priority for what little resources Jolla apparently has.
Doing it together…we make it, jolla may follow, or…may not.
It’s weird, I don’t understand why you get torch button, but it’s nice to hear that it’s working for you, thank you for the feedback.
In my case (I installed it in my devices: XA2 and 10 II) it worked fine and I didn’t reboot them.
I understand you and I hope Jolla implement this feature soon, but I agree with @Edz, Jolla is a small company with limit resources and there are a lot of bugs to fix.
Could you share the steps needed to add these files and make it work without PatchManager? That would surely help some users and I would definitely mark this feature request as Solved.
Before I give details to @Maximilian1st - can someone here confirm for me that stop-start-runtime.json
is an ORIGINAL file found in /usr/share/jolla-settings/entries
Sounds daft, but often i do things on automatic pilot and don’t always recall what or how I did it.