i dont have egate installed im still setting this phone up but ill probably do it soon
this is what i did in order not sure what did it i thin it was the 3rd one
-
i added these lines to build.prop though didnt seem to do anything
ro.config.accessibility_timeout 30000
persist.vendor.accessibility.enable true
persist.sys.accessibility.persist true -
adb shell dumpsys deviceidle whitelist +com.fb.fluid
-
adb shell settings put global setting.duraspeed.enabled 0
No change for me when disabling duraspeed.
Go into accessibility settings after closing from recents and see if it says it’s working properly.
working properly - says on
what rom are you using
also now it starts up within a second pretty quick
eGate’s external accessibility APK was made specifically for this issue.
If you set it up correctly, it should work.
Didn’t do anything for me dunno
The reason this works is because you never open the app.
i the external wrok for me but i want a way around it
your logcat is difffertn from mine - waht rom are you on - im using 1.1.1 from xda
Aiv 1.1.1
im gonna set up egate now without the external apk whats an easy test to see if it is working
Nothing special, it should work because you don’t open and close the external APK.
Open webview to see if it closes it.
Open external accessibility, and then swipe it from recents.
Open webview again.
confused, im not gonna use the external apk just the regular app to see if it accsibility restarts itself
Oh, I see what you mean.
In that case, enable accessibility, make sure it’s working, then swipe the app from recents and see if it restarts.
okay it didnt work but as soon as i enable egate accsibility it kills the FNG acsibility then i turned FNG back on and it was working but when i swiped up on FNG it would restart so i turned accsibilty off for egate and put FNG back on and now when i swipe up it restarts itself - so maybe egate messes with accseibility
it WORKED video coming
I still don’t underestimateamd the point in fng can someone please explain