I have an AccessibilityService that will break if the user turns it on and off through the Android system user interface. I only want the user to be able to disable/enable AccessibilityService through my own Activity which will handle shutting it on and off correctly.
I never encountered this feature before until I tested my app on newer devices. On Android 11 devices there is suddenly an option to toggle "Accessibility Shortcut". This will add a button at the bottom corner the navigation buttons OR it will allow the user to toggle the AccessibilityService by holding both volume buttons at the same time. For my app, it say's it will add the toggle near the navigation buttons.
How do I remove this option?
I am running into the exact same problems. Users tend to enable all switch button they see without reading explanation or videos. Since accessibility shortcut interfere in a bad way with the accessibility service, they got a non working experience.
It seems at first sight there is no option for developpers to hide the option for their accesibility services...
Related
Im trying to retrieve typing information such as the on-screen coordinates of where a user presses a key on a keyboard on Android and iOS using flutter similar to how swiftkey does it to generate their heatmaps.
How would I go about doing this? Do I have to create my own custom keyboard
I've tried to implement the suggestion here: How to Calculate the Coordinates of touch in Flutter?
But once the keyboard drawer pops up, the on-screen coordinates do not register.
To do this you would have to show your own keyboard that you build in flutter. The reason for this is that the keyboard which pops up is actually a different android window (or at least activity, but pretty sure window and likely process as well), that is shown over top of the window that flutter is rendering into. By design, the keypresses can't be recorded as that would be a security issue (the active app is one thing, but imagine if another app could record keypresses or even location of taps - they could steal your passwords!).
There may be some android-specific way of doing it that I'm not aware of, but it probably won't work on all devices and all keyboards and is likely not a good route to follow.
I'm part of a team building a mobile web app using AppGyver Steroids (PhoneGap). We are having an issue with the iOS7 keyboard displaying a very faint "Done" button on the keyboard when the user is operating in a text area or an input select. I suspect this is a problem that is actually global in our app, but these are the instances where I have observed them.
I've searched and searched for a solution or how to "customize" the keyboard in order to make this "Done" button more obvious, but I haven't found any solutions yet. Can anyone point me in the direction of how to adjust the "Done" button or any other keyboard/input controls?
Attached are two screenshots showing the issue.
http://i.stack.imgur.com/KeFYM.png
http://i.stack.imgur.com/h11IH.png
Have you seen the issue on github? It's now fixed. They'll be including the option for custom colours in the near future.
Recently, I am trying to fix issues of my app after release of iOS7.
One of the most annoying problem is about the pull-up control panel: since my app has pull up menu, apparently, the pull-up gesture triggers control panel simultaneously.
However, I found some apps are not affecting by this issue cause they need to pull twice to show the control panel, such as Slideshark. When user perform a pull-up gesture, the menu shows up with a "pull up tab" at the bottom of the screen(see red rectangle).
So the user need to pull up again to trigger the control panel.
I do not think pull-up menu is a good idea in iOS7, but this seems temporarily fix the problem. Anyone know how to do this?
Hubert
You'll get this behavior automatically when you hide the status bar in your app.
This question explains ways to hide the status bar on iOS 7: Cannot hide status bar in iOS7
(You can do it on a per view controller basis, or for your entire app at once.)
I am building iOS app for promo. The client asked that people using it should never quit it, so I got an idea.
When people are trying to quit, they would be asked to enter the password, otherwise it's impossible. Is there a solution to this?
I would appreciate any help, thanks!
Here are the steps to easily disable the home button :
Launch the Settings app from the Home screen of your iPhone or iPad Tap on General.
Scroll down towards the bottom of the screen and tap on
Accessibility.
Under the Learning section, tap on Guided Access.
If it's not already, turn the toggle next to Guided Access to the On
position, then choose a passcode.
After having deployed your application on the device, open it and triple tap the home button.
Set your options and then tap on start.
You can leave the guided access mode by triple tapping the home button again, it will ask you for the passcode you set before.
Here is a link for more details (and illustrated with photos)
What you are doing is not possible I guess. See for quitting any app the user can simply press the big quit button on the ipad or iphone and then the app would go into the background nevertheless.
You can't prevent the user from quitting. If you try to prevent it, the OS will terminate the app directly. With iOS 4.0, you can have tasks that are allowed to complete in the background.
Check this out.
For an overview about running tasks.
On this site : mecanomedic.com, the menu template work fine in "normal" desktop browser, but dont slide down on ipad-iphone device. What can be the problem ?
Some tell me it's a css problem, but HOW safari desktop work ?
The problem is that the menu expansion relies on the user hovering with a mouse. On touch devices like iPads & iPhones, the hovering gesture can't be replicated because there's only one input- touch. If I were you, I'd take a look at Twitter's Bootstrap menu setup and perhaps use media queries to serve up a different menu on smaller screen sizes.
Here's an example of a Bootstrap navigation bar in action (you'll have to inspect the code to see how it works).
Add a href to the top-level <a>'s so that they can be focusable:
Produits
Elements that are focusable receive mouse events and hover styles when the user taps on them.
As #Matt stated, the problem is that your menu relies on a hover event and unfortunately that event is unavailable on touch screen devices.
One way to fix this would be to:
Check if the current user's device is an iOS device
If the device is an iOS device, use javascript to trigger a menu item's "show event" when the menu button is CLICKED instead of ROLLED OVER / HOVERED.
This would result in the menu being shown when the user taps a menu button.