I'm trying to enable Accessibility features (e.g. the Universal Switch). However, I can't enable any of the features, as I can't for whatever reason press the "OK" button when the dialog asking for permissions pops up; I've tried it for different Accessibility features, pressing "OK" does nothing ("CANCEL" takes me out of the dialog, as expected). For reference, a screenshot of the dialog I'm referring to is located at imgur with the URL identifier "Lwg0seF" (I'm a new user, forgive me for not being able to directly post the screenshot here :/ )
I have no idea how to circumvent this. Does anyone have any idea how to solve this?
Please help, I can't use my phone properly unless I get this working. Thanks in advance.
EDIT: I don't know how this happened, but I've just tried it again (haven't made any changes), the permission granting works now. It seems the problem solved itself somehow.
did you installed a rom that was debloated of samsung software ?
because i´ve had this problem before and it turned out the rom i was using needed the samsund TTS and voice software for me to use the accessibility option i needed
not sure if this is your case, hope it helps
Related
Searched around alittle to see if anyone had found any means of doing this, but didn't find anything.
Anyone know if it's possible to assing the "settings" function to the browser key?
Thanks
siggehandf said:
Searched around alittle to see if anyone had found any means of doing this, but didn't find anything.
Anyone know if it's possible to assing the "settings" function to the browser key?
Thanks
Click to expand...
Click to collapse
Look here. It has a lot of information on it. You should be able to do with relative ease.
Cheers.
Sweet!, Worked like a charm with root explorer.
Just stumbled on this thread and thought id give it a shot on my K1. Everything went fine, files were same name and in same location, mounted the dir. Rw then changed my hardware button (the one thats Home/Back/Menu), saved the file with a backup but no changes were made. I even changed the buttons in the other file showing only hardware buttons and then rebooted but still nothing...
Im thinking that since this mod was for the TPT and Im on a K1, theres something Im missing. Any K1 owners had any success with re-mapping the hardware buttons?
Sent From My K1
may need to set permissions on file
You may need to set permissions on the file before you can save. Using "File Manager HD" I had to enable root explorer and mount systems folders under the settings and then add write permissions to Group and Others in the permissions dialog, probably don't need Others but I am lazy. Don't forget to change the permissions back after you save your changes. Incorrect permissions settings can sometimes really bork things.
Also seems that the settings might be a little different under ICS, I am getting "Touchscreen Toggled" instead of the menu after setting 150 to MENU.
-j
On the Lenovo boards, it has been comfirmed in the released chineese manual, that pen only mode is avaible. SoSweet!
Menu's not allowed in ICS
Well, here is why remapping the browser button to MENU does not work in ICS, looks like we are no longer allowed to have a menu.
http://android-developers.blogspot.com/2012/01/say-goodbye-to-menu-button.html
Still playing with it but it appears that no matter what I put on the line after key 150 I just get touch-screen toggled, which is useful but not what I want.
-j
BTW doin' this on a Thinkpad Tablet
Hi there,
after quite a bit of searching both on google and on this forum, I cannot find anything about this, although I am sure I am not the first one wanting this tweak...
My Samsung sgs2 will open a confirmation dialog when I try to enable the airplane mode by selecting the apropriate "phone option" by long-clicking the side button.
Does anyone know what do I need to modify to disable the confirmation dialog? I mean: I already long-clicked a physical button to get into the menu... what are the chances that I did that unintentionally??
Thank you!
Hello
It occurs in ICS (4.0.3 for me).
This may also concern other confirmation popups. If it is doable only in a ROM, just tell us, but do not leave us in ignorance.
If someone has not the confirm dialog, could he give us his config (ROM, kernel, ..) so we can try to investigate what enables that.
Many thanks to testers & analyzers there.
Regards
I just got this phone last week and I love it...except for this one annoying issue:
It appears for certain apps, when there's a popup window/dialog, I have trouble making the dialog responding to my taps.
For example, I have privateinternetaccess app, when I hit connect, a popup comes up asking if I trust this app, and I cannot tap to check "I trust this application" checkbox.
Another example: when sideloading an apk, the screen shows a list of permissions the app requires and asks me to accept it, but I cannot tap "Install"...
A third example: SuperSU prompt me when an app requests for root, and I cannot make the popup respond to any taps. However, today I discovered that in SuperSU there's a setting to disable tapjacking prevention and when I checked it, it worked! I'm wondering if the other two issues are related.
Anyone else experience this issue? I did search the forum first and so far only http://forum.xda-developers.com/showthread.php?t=1189703 thread sounds like something that's remotely related to my issue and it got 0 replies...
kevinjqiu said:
I just got this phone last week and I love it...except for this one annoying issue:
It appears for certain apps, when there's a popup window/dialog, I have trouble making the dialog responding to my taps.
For example, I have privateinternetaccess app, when I hit connect, a popup comes up asking if I trust this app, and I cannot tap to check "I trust this application" checkbox.
Another example: when sideloading an apk, the screen shows a list of permissions the app requires and asks me to accept it, but I cannot tap "Install"...
A third example: SuperSU prompt me when an app requests for root, and I cannot make the popup respond to any taps. However, today I discovered that in SuperSU there's a setting to disable tapjacking prevention and when I checked it, it worked! I'm wondering if the other two issues are related.
Anyone else experience this issue? I did search the forum first and so far only http://forum.xda-developers.com/showthread.php?t=1189703 thread sounds like something that's remotely related to my issue and it got 0 replies...
Click to expand...
Click to collapse
Are you using lux? There is a known issue with that and the tap jacking feature in su
My God....this was driving me crazy. I installed a different ROM/kernel combo trying to figure it out! In my case, I was only experiencing the issue with the SuperSU popup dialogue. I flashed back to stock and it seems to have fixed it for now. I am using Lux BTW.
I play with my food
zelendel said:
Are you using lux? There is a known issue with that and the tap jacking feature in su
Click to expand...
Click to collapse
That's it! I'm not using lux but I use a similar app twilight. I stopped it and popups are responsive again! It's a pity - I like that app.
Hi all
I'm having problems with the accessibility options in the CM12.1 port for my SM-P900. You can set which applications have access to other applications on your device e.g. letting Lastpass have access to other applications so that it can fill forms and passwords for you.
The option to enable this is in the 'Accessibility' section of the settings. I open this section, I toggle the option to 'On', which then opens a confirmation dialogue to confirm that you do want to turn it on. The problem I then have it that I cannot press the 'OK' option no matter what I do! The 'Cancel' button work perfectly but the confirmation will not work no matter what!
I've read other threads that this may be an overlay issue to stop tapjacking exploits (say, for example, if you have Twilight installed). I have turned off all overlays, yet I'm still not able to proceed.
Does anyone have any ideas or insight?
Ta
Found that it was related to Lux app for me...
If, by chance, you have Lux or Lux Dash installed I discovered it necessary to disable Lux and only then I was able to turn on Accessibility for LastPass. System would not allow me to do so prior to disable Lux.
Once turned on for LastPass I re-enabled Lux and all is working as expected. I do hope this helps as it is was very frustrating for me and was only one post which pointed to Lux as the root cause. They uninstalled but that was not necessary for me, disable / re-enable works the trick!
http://forums.androidcentral.com/as...-why-can-t-i-turn-services-accessibility.html
Mine was related to "copy bubble float" when I turned that off I was able to enable last pass and then turn copy bubble back on.
Hello,
I'm curious I can get some help. I have an android box that hooks up to my TV. I have an app I use called "Key Mapper" that allows me to remap my keyboard keys so I can create shortcuts. One of the issues I find with the app is that sometimes I have to exit out of it and reopen it and re-enable accessibility within the App.
In Android Settings I already have accessibility enabled so it should be good, but when I reboot the device it seems to always stop working until I close out of the process and re-open it up.
My theory is that maybe I need to delay the auto boot of the application. It starts up with Android automatically but if I can have it delayed start that may resolve the issue. Is there an app or some way I can adjust the auto boo setting to delay it say 10 seconds after Android loads up?
m0d hipp¥ said:
Hello,
I'm curious I can get some help. I have an android box that hooks up to my TV. I have an app I use called "Key Mapper" that allows me to remap my keyboard keys so I can create shortcuts. One of the issues I find with the app is that sometimes I have to exit out of it and reopen it and re-enable accessibility within the App.
In Android Settings I already have accessibility enabled so it should be good, but when I reboot the device it seems to always stop working until I close out of the process and re-open it up.
My theory is that maybe I need to delay the auto boot of the application. It starts up with Android automatically but if I can have it delayed start that may resolve the issue. Is there an app or some way I can adjust the auto boo setting to delay it say 10 seconds after Android loads up?
Click to expand...
Click to collapse
After your OS finishes booting and loads the full OS stack, a system-wide message called Broadcast Intent will be sent to all apps, notifying them that your device has completed booting (this intent is called BOOT_COMPLETED). Then it's up to the individual app to use that broadcasted intent to pre-load in memory whatever they want (or simply not react at all).
The thing is you want to delay auto boot for that specific application, so there are 2 options for that:
you turn off auto boot in the App itself (if it provides such an option).
you block the app from receiving the intent broadcasted.
The second option is also achieved either by using a task killer to force kill the app (which defeats your point IMO) or it manipulate the app from receiving the intent entirely. Both of these options require root access.
If you have root I suggest The App: SD maid (pro version). Under app control you can modify which system Broadcasts that Keymapper recieves (among them could be boot_completed). See attached screenshot from my device for example.
Hope I helped somehow
Thank you for your response. That was super helpful! The device I am playing around with is a Mekotronics R58x, and it had some sort of modified root that was conflicting with Magisk. I read somewhere on these forums that someone suggested renaming the su file if it exists in /system/xbin/su; which it did. I renamed it and rebooted and after that everything worked wonderfully. Keymapper was still autobooting like previously, but this time all the services loaded right up and I didn't have to restart the app it just worked.
Basically I think the issue was this custom su file that was conflicting with Magisk and causing a headache with the keymapper. I'm glad I stumbled across the fix, but either way your post was also very helpful! Thank you!