Hi all,
Just out of curiosity. I have a 3rd party app on my phone (not available on the Google Play Store, obviously)
I am currently running Android 7.0. When accessing the settings - - > apps--> theApp--> permissions where one can adjust the permissions on demand, I noted that the "Telephone" permission for this specific app cannot be switched off.
When selecting to switch it off there is the usual prompt that the app won't work as intended and I "continue anyway". The slider goes into the off position. Then when clicking back and then opening the permissions, the Telephone permissions switch is back into the on position.
What do you make of this? I have suspected that the app is "spying" somehow for quite some time. Reverse engineering on the apk itself had some very strange permissions logged in the Android Manifest file.
I would really like to hear your opinion....
41 views and zero replies....
Related
I've just installed QuickSpell from MobiSystems on my Nexus. When I go into the Language & input section of Settings, and change which spell checker to use, my selection is not "sticky" - the setting reverts to the Android default.
When I make the selection of QuickSpell, I get a verification dialog box - "Attention! This spell checker may be able to collect all the text you type, including personal data like passwords and credit card numbers. It comes from the app QuickSpelll.Use this spell checker?" (doh! isn't that what I just selected?)
I select "OK", of course, then go on to do whatever I was going to do.
When I power off, then power back on later, this setting reverts to the Android default. It does this even if I disable the Dictionary Provider app, which seems to re-enable itself too when rebooted.
Another similar odfity in the Language & inputs settings is the "voice typing" option. This too is not sticky, even if I have all the voice-related apps even if I have all the voice function apps disabled. I'm not sure if any of these are re-enabled by reboot, but I suspect so since I know I have had to disable something(s) off this sort repeatedly.
The only system-level type modsI have is the Nova launcher. I run Lookout Premium for security, but I know that that is not the source of the problem. They quickly replied to my email about this and said that Lookout does not make changes of any kind to any settings. They merely detect what apps do in re: privacy and report on their behavior, letting the user decide whether to uninstall or continue using apps that can/do access potentially private data, include Lookout itself.
Having to re-enable QuickSpell as my default with each reboot is a pain in the fingers (carpal tunnel, you know, from a zillion years as a now-retired software engineer. A new keyboard app is next, since I really hate this one. I'll take suggestions on that too.)
Becky
INTRO
Hey everyone!
Some of you, like me, loved to use the smart stay feature of Samsung, they disables the dimming of the screen while you are looking at it.
Unfortunately, on the latest builds (CM11 like CM12), this app is broken. What happens is that, when an app is using the camera and another tries to access it, there is a conflict. For example, you are using the camera. If smart stay + tries to see if you are still there, it tries to access the camera which is already in use. And so, the camera app doesn't know what to do and crashes ^^
A way to repair this is to modify directly the app to pause the search when the camera is already in use, but we can't do that, the only one who can is the app dev ^^ Another way is to refuse access to the camera when using the camera app, but not sure how we can do that... The way I did is bypassing this error by killing smart stay + when I use a specific app like the camera
Apps
To do this, you need to install :
Tasker : lets you automate stuff depending of the state of the phone, an app, or even the sensors,
Secure Settings : lets you change the phone settings directly from Tasker,
TaskKill : lets Tasker kill apps using several different methods.
Watch out! Make sure you have the latest version of each, or else bugs may appear!
Lets Start!
So, start by installing as those apps, and install the latest version of Smart Stay + (if you are on CM12, you can't download it from Play Store cause it's incompatible, so you need to use the apk from the Internet). Don't launch Smart Stay +, and don't enable its setting in the accessibility menu on the phone!
First off, we need to give root rights to Secure Settings. Launch the app, then go to the System+ tab and enable it. It will then ask for root rights, accept and we are good to go on.
Kill Switch
Now, launch Tasker and go on the profile tab (if you want to follow everything in english in the app, press the 3 dots in the upper right corner, then Preferences, go all the way down in the UI tab, then change the language). Create a new context using the + icon on the bottom of the app, then chose Application. A list of all your apps will be shown, so you need to chose which app will kill the other one. Here, I want the Camera app to be the "killer", so I chose the apps using the camera (I have Camera Next as well as the stock camera, so I chose both) :
Screenshot 1
To go back, do not press the X button on the upper right corner! It will erase your config Press the button on the upper left corner to go back to the profiles. The app will show you then a menu where you can enter a new task. Chose New Task and name it "Kill". A new screen will be shown :
Screenshot 2
Click +, then go into Plugin, and you will see all the plugins. Click on TaskKill, then press on the Pen logo on the upper right corner to config the plugin. Here, you can choose the method to use to kill, and the app. You need to use the Extrem method, or else Smart Stay will keep rebooting... Choose Smart Stay in the list, then click apply. Set the Timeout to 0, then save it by clicking on the upper left corner, and return to the profiles list.
Here is what we should see :
Screenshot 3
Starting the App
We now need to start smart stay after we finished using the camera, and it's a bit tricky. You can either start the app using Tasker, but it will ask for you to enable the accessibility option of Smart Stay (happens every time), and that is really a bummer... That made me look if we can't directly turn on that setting from Tasker, so that we don't need to open the settings, close the app, etc... And it is! We can change that settings from Tasker using a plugin! Buuuut, the catch is that we need root...
Soooo to enable this setting, you need to long press on the action we just did named "Kill", and add an Exist Task. Next, do a new task named "Start". After, choose the plugin Secure Settings, then press on the Pen logo on the upper right corner to config the plugin. Here, you can choose which action you want. Go to System+ Actions, then press Accessibility Services. A new menu will appear, where you can see the different apps that has an Accessibility Setting. Choose Smartstay+, and make sure the button underneath it is Disabled (so that it disables that setting). Save it, then go back to the profiles list using the button on the upper left corner.
Here is what you should see :
Screenshot 4
Testing
Tada! Done! You can now launch the camera app without having it bug! To test it out, you can go on each action, like "kill" and press the play button on bottom of the screen. You will see that the notification is closed. Go into the "start" action and press play, you will that icon return! Go try it out using the camera app!
Misc / Other Method
You may ask why I didn't use the Secure Settings in the first place, and the reason is that it doesn't work well. The app isn't totally killed, it's just paused, so we don't know if it still has access to the camera, or if it is draining battery... Using TaskKill ensure us that it isn't running in the background, and so not draining any battery.
For Android L users, you may know that with Smart Lock, you can unlock the phone with your face. To do so, Android uses the stock camera app. This means that you won't have any bugs at all using that unlocking method with Smart Stay, thanks to our bypass
Another method that was pointed out by triviums (1+1 forums) is to use Smart Stay EX Pro. It has an option to disable scanning when certain apps are launched. But, after testing this out, it doesn't work as well as my method. There is a missing option in that app which is Smart Timeout. Without this feature, it still scans if the user is there, even though he is typing something or scrolling a page. Smart Stay + has this feature for free )
If this could be implemented (cause on the photos on Google Play, the feature is there for PRO users, but after installing you don't see it...), then it may be better (no need to kill and restart app, which takes some battery). If this doesn't work, then the battery you gain from not killing the app is lost in the use of the camera when it isn't necessary...
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 there,
as written in the title I am trying to figure out why the settings app does not show the apps list to turn off dark mode for sigle applications.
CONTEXT:
MIUI Global 13.0.1 (Android 11), Dark mode enabled.
Some minor (no root/no roms flashing) tinkering has been made on the device, including:
Uninstalled some community-recognized bloatware via adb
Revoked some highly-sensitive intrusive permission for some system/not-system apps from Settings > Privacy Protection > Special Permissions, however no permission has been revoked from the "Settings" app
EXPECTED BEHAVIOUR:
Opening Settings > Display > More dark mode options shows a list of apps (under "Individual apps") for whom you can disable the made-in-miui dimming.
OBTAINED BEHAVIOUR:
The "individual apps" list is empy, as shown in the screenshot linked above.
ALREADY ATTEMPTED (AND DIDN'T SOLVE):
Rebooting the device (disappointed, I expected this to work)
Accessing the dark mode settings from the notification area
Opening the settings in split-screen with another app
Opening the settings after opening as many apps as possible to fill the RAM
Waiting 5+ minutes in the "More dark mode options" screen
Swiping the line just above "Individual apps" up
Accessing the settings page while mobile data and Wi-Fi are turned off
What are the other possible ways to solve this? Is there a particular system app who is responsible for the app list showing in this setting? Or is there a way to completely turn off Individual apps dark mode while keeping dark mode on?
Thank you in advance for the replies and screw Xiaomi for making no option for this and making this "in-app-enforced-darkmode-wannabe" enabled by default for every app.
Hum..., bump?
Unfortunately all I can add is I'm experiencing the same issue and haven't found a solution. I think it must have been introduced with an MIUI update as I know in the past the dark mode app list has been populated.
questioner9 said:
Unfortunately all I can add is I'm experiencing the same issue and haven't found a solution. I think it must have been introduced with an MIUI update as I know in the past the dark mode app list has been populated.
Click to expand...
Click to collapse
Any updates on it?
InternationalSystem said:
Any updates on it?
Click to expand...
Click to collapse
Still not working for me. I did find this thread for a different Xiaomi phone with the same MIUI issue. Seems someone has made a Magisk module if you have a rooted phone: https://forum.xda-developers.com/t/...t-miui-13-redmi-note-10.4404923/post-87160523
However I haven't rooted my phone (in case I had any issues with e.g. banking apps) so haven't tried this myself. I'm just hoping Xiaomi eventually fix it in an update.
questioner9 said:
Still not working for me. I did find this thread for a different Xiaomi phone with the same MIUI issue. Seems someone has made a Magisk module if you have a rooted phone: https://forum.xda-developers.com/t/...t-miui-13-redmi-note-10.4404923/post-87160523
However I haven't rooted my phone (in case I had any issues with e.g. banking apps) so haven't tried this myself. I'm just hoping Xiaomi eventually fix it in an update.
Click to expand...
Click to collapse
That is absolutely crazy, how Xiaomi messed up their own software. It has not been showing the apps for me for long now and it is so annoying to have to switch dark mode off entirely every time an app doesnt display elements correctly, just because Xiaomi forces their weird dark mode adaptation into apps that dont support dark mode natively. I dont get how they thought that feature being on by default for every app was a good idea...
EDIT: Also thank you for the link but I don't want to root my phone either, too many security related concerns.
It is working, the UI just stalls when loading the apps list. when you open the "More dark mode options"
place your finger on the line that says "individual apps" and swipe up. if u did it right it will show the list., just keep swiping up from that line until the list shows
This issue was discussed in the xiaomi forums (c.mi) and this is the only way to access the dark mode page.
zero_ap said:
It is working, the UI just stalls when loading the apps list. when you open the "More dark mode options"
place your finger on the line that says "individual apps" and swipe up. if u did it right it will show the list., just keep swiping up from that line until the list shows
This issue was discussed in the xiaomi forums (c.mi) and this is the only way to access the dark mode page.
Click to expand...
Click to collapse
I tried this several times and in multiple directions (I can actually swipe the interface up), swiping the line app to the top, but it keeps showing no app; there keeps being a problem on loading the list of apps for some reason
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!