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 have a Moto G 4G LTE XT-1040 with the latest (11/08/2016) CM13 nightly ROM.
I got an app that need the storage permision enabled. How ever when i come to enable it, a message pop up telling i need to disable Screen Overlay to change the permission.
I did disable for all apps (except the system ones that it didn't allow me to disable) on settings but still no use.
I did reboot the phone on safe mode to try to change there and had the same issue.
What could it be?
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
OK guys I hope this hasn't already been covered but here goes anyway. I have found this fix for notifications not arriving when doze is enabled. Iff you go into the particular app e.g what's app then into data usage you must select the following settings see pic below. then all the notifications will arrive straight away regardless of doze state.
sam00561 said:
OK guys I hope this hasn't already been covered but here goes anyway. I have found this fix for notifications not arriving when doze is enabled. Iff you go into the particular app e.g what's app then into data usage you must select the following settings see pic below. then all the notifications will arrive straight away regardless of doze state.
Click to expand...
Click to collapse
Yes that seems to be the problem. I had made a post months ago. It's very hidden feature by Lenovo and I think it's wrong to pre-restrict all background data. User should decide what to do.
I think they lenovo did it to block unnecessary data usage but i agree it is not needed and people are thinking their is something wrong with their phones.
Thanks for the tip
Thanks Sam, I saw this on the JJ review of Nougat. Is this for Nougat as my MM P2 settings don't look like the screenshot.
Sent from my Lenovo P2a42 using Tapatalk
Hi yes it is for Nougat the comment posted on JJs review regarding this fix was posted by me also.
Confusing settings these as the first one makes it look like enabling the "Restrict background data" option will disable background data, when in fact it does the opposite. You need to have both of these options enabled so the sliders are green, then you need to open Settings > Power Manager > Battery Optimization
Then you need to search for the apps that you need to fix notifications and change the option so it says "Don't optimize". Then the phone won't 'helpfully' close the app when the phone has been unused for a long time. This is why notifications are stopping.
precisely i agree quite confusing it took me a while i had to get a friend to send me whats app messages continuously untill i figured all this out but im glad i finally did.
If you make the changes to fix the notifications, shut down and power the phone back on rather than do a reboot. The settings don't seem to work until the phone has properly rebooted.
Is it worth noting that elsewhere it's stated that turning off doze altogether (using ADB) might be a saner option? Consensus seems to indicate it's basically a curse with little value, and that would certainly hold water in light of the battery capacity of the P2.
https://forum.xda-developers.com/lenovo-p2/help/regretting-purchase-t3611968
I think the following helps. Credit goes to JasonMR and manototh (Taken from oneplus.net forum)
JasonMR
KitKat
JasonMR, Nov 2, 2016 :
Guys, to avoid having to run the ADB command after each reboot follow these instructions (please note, the files should be downloaded to a PC and then transferred to your phone via USB otherwise they mess up sometimes):
You need to enable USB debugging mode in Developer options first
Download and install this apk and transfer it to your phones storage - https://drive.google.com/file/d/0BxD...w?usp=drivesdk
Then connect phone to PC and allow the drivers to install
Download and install ADB here - https://drive.google.com/file/d/0B0M...ljU2NPR0k/view
Go into the ADB folder, hold shift, right click and select "Open command prompt here"
Type the command: adb devices (now hit enter)
It should return your phones serial number is connected correctly
Run this command in ADB: adb -d shell pm grant com.adamioan.scriptrunner android.permission.DUMP (now hit enter)
Download this file and transfer it to your phones storage - https://drive.google.com/open?id=0Bx...VA4YmxGTS1OX3c
Open the SH Script runner app and tap the three dots in the top right corner, select "Load" and locate the file from teh previous step
Click the Circle button with the play sign at the top of the screen
You should see the message "Idle mode disabled" which means that Doze has now been disabled.
Whenever you reboot your phone, open the SH Script runner and the command will still be there, just click the play button to run the script again.
And that is it, two clicks to disable Doze after each reboot.
Full credit to manototh for putting this together originally.
Doze does not need disabling iff you follow my advice in the initial post i have tried and tested this and can confirm it works fully.
This is really frustrating. No matter what settings I use I still don't get notifications after a while. I don't want to go modifying my phone, can someone post a step by step if they have it working properly?
Spacedog79 said:
This is really frustrating. No matter what settings I use I still don't get notifications after a while. I don't want to go modifying my phone, can someone post a step by step if they have it working properly?
Click to expand...
Click to collapse
Follow my ordinal post and also go into battery optimisation and disable optimization for things like sms eggs what's app Facebook etc all the things you need notifications for should be disabled from sleep mode under battery optimization.
Like this
sam00561 said:
Like this
Click to expand...
Click to collapse
Yes thats exactly how I've done it. I've also tried every combination of settings under Apps for Unrestricted data usage.
And also the setting here
sam00561 said:
And also the setting here
Click to expand...
Click to collapse
Yep doesn't work either.
Perhaps your only option left is to try the disable doze app which has worked for many people but it's a paid app.
Just to update it does seem to be working properly now. I'm not 100% sure but I think turning the phone all the way off and on again instead of rebooting with the settings correct had the desired effect.
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!