deleted all those files, does not restart after swiping out.
interesting did your logcat ever mention duraspeed probably has to do with the rom im using versus yours
Actually, all you need is this:
# Disable accessibility
settings put secure enabled_accessibility_services ""
# Re-enable accessibility service
settings put secure enabled_accessibility_services com.oss.egate/com.oss.egate.MyAccessibilityService
His rom is pretty much 1.1.1
i dont know?? im gonna try another device
F21 pro?
ya
its still working - battery life seem normal - i getting hopefull
1 Like
So I figured out something interesting.
Foolproof way to turn accessibility on programmatically on the f21 after closing from recents, is to turn it off and on TWICE.
@FlipAdmin does this help you at all?
Magisk module that does exactly this on boot and every time egate is closed (for testing):
egate_watchdog.zip (834 Bytes)
#!/system/bin/sh
PKG="com.oss.egate"
COMP="com.oss.egate/com.oss.egate.MyAccessibilityService"
# Bind accessibility service (twice)
settings put secure enabled_accessibility_services ""
settings put secure enabled_accessibility_services "$COMP"
settings put secure enabled_accessibility_services ""
settings put secure enabled_accessibility_services "$COMP"
# Watchdog loop to detect crash and rebind
while true; do
if dumpsys accessibility | grep -q "Crashed services:.*$COMP"; then
settings put secure enabled_accessibility_services ""
settings put secure enabled_accessibility_services "$COMP"
settings put secure enabled_accessibility_services ""
settings put secure enabled_accessibility_services "$COMP"
fi
sleep 1
done
Also, logcat for egate accessibility shows running and crashed at the same time, when accessibility menu says there is an issue.
Also, dunno if this will help anyone brainstorm… But there is a difference (on boot) in the FIRST launch and close of a given app and any subsequent open/close actions.
The first one is a more powerful shutdown somehow.
The first one is the reason why I had to do twice. One time disable/enable accessibility worked for subsequent open/close, but not the first.
Why am I not recommending shutting down/deleting duraspeed?
First of all, it didn’t work for me. I believe the answer is in services.jar
Second, I have no idea what will break or be affected.
There is someone on this forum who figured this whole thing out (@youknowwhoyouare 
) but is keeping it to himself. No complaints, just sayin 
Technically can just make a ROM with all mdms restart accessability functionality, just feels cheap…
5 Likes
Technically can make a module, or boot script in a ROM, that checks all crashed accessibility services, and turns them on and off twice.
This trancends yeshivish.
Would work though.
1 Like
Any interest in this?
I’d just flash 1.1.1, gapps, pull super and make my additions.
Wouldn’t spend time making it kosher, unless it was tripleumdm only, that I already figured out how to auto start configuration on first boot.
Kosher would be talk and text only, can’t deal with iabs.
Nonkosher + make your own kosher ROM makes more sense, but I can’t post that here.
Video showing it working for all accesibility apps.
Gave it to someone to test, and it didn’t work for them.
Turns out I had duraspeed disabled. The script only works with it gone.
And no, just removing duraspeed did not stop the app killing.
Going to make an exceptions config file.
Something like this might work:
# /data/system/duraspeed.xml
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<duraspeed>
<pkg name="com.oss.egate" enabled="true"/>
</duraspeed>
I’ll have to try
1 Like
Just curious if this issue is a bug on Qin’s side or they wanted it like this.
Wow, they really messed up on this one.
Duraspeed does not honor it’s own config file.
1 Like
had the wrong format seems to be working now
Update
Solved!
Works perfectly, will be using a rooted boot image, because I can’t get a normal rc to work. Open to changing that if someone provides me some help.
For kosher roms, rooted boot image doesn’t matter, magisk stub can be hidden and no user access.
Need a list of common accessibility apps, mdm apps, and music apps package names.
The rest is up to you, need that list.
2 Likes
okay sorry im not folowing - whats the new solution
did you reboot after removing duraspeed