Fixing accessibility problem on Qin F21 Pro

somone confirm this!!! i was able to swipe out of egate and it still worked

the qin has a bug that affect all acsseibilty apps so i was testing solutions using the FNG once i found a solution i tried it on egate and it worked

Write exactly what you did and I’ll try to recreate it

i posted it above nothing different eGate - Android MDM - Version 1.33 + - #63 by ars18

but maybe it only works on the xda rom

did you watch the screen record

Yes

okay i rebooted and it stopped working when i swipe out of egate -

Yep lol

If you have the head for it, explore the services.jar in the f21 pro ROM.

smali smali smali I hate it

now i cant even get accseisibilty to work on egate even if i dont swipe out of egate

i feel like it has saomething to do with egate because the FNG was working accross reboots and when i swiped out of it and egate was messing not only with its own accseibilty but also FNG

i deleted all duraspeed related files and egate is back to working when i swipe out of it and it still works accross reboots. i saw in accseibiltiy setting that when you swipe out of egate it says “Not Working. Tap for info“ and then after a few second it goes back to “on“

and FNG is working - can somone try this out and tell me - any other tests i should try out

Write exactly what you did

i deleted these files

/system/etc/init/duraspeed.rc

/system/framework/duraspeed.jar

/system/framework/oat/arm/duraspeed.odex

/system/framework/oat/arm/duraspeed.vdex

/system/framework/oat/arm64/duraspeed.odex

/system/framework/oat/arm64/duraspeed.vdex

i think the other things i changed (the ones i posted earlier lo maala vlo morid)

I’ll try it out.

This seems to work as well, without modifying system files.

Running after exiting from recents

# Kill the app if running
am force-stop com.oss.egate
sleep 1

# Launch the app
am start -n com.oss.egate/.MainActivity
sleep 0.5

# Disable accessibility
settings put secure enabled_accessibility_services ""
settings put secure accessibility_enabled 0
sleep 1

# Re-enable accessibility service
settings put secure enabled_accessibility_services com.oss.egate/com.oss.egate.MyAccessibilityService
settings put secure accessibility_enabled 1

input keyevent 4

im confused how does that help - also that would only work for egate what i did seems to work for all accseibilty services now i just have to see how not having duraspeed affects me

yeah thats what I’m afraid of

everything seems fine for now ill keep you posted - i backed up all the files just in case

1 Like

anyone try it out??