I used to be able to override a flag in Chrome to hide the default share screen, thus giving direct/one-tap access to all the apps on my phone, but the option appears to be done now with Android 10.
I guess it could be sharing from any app on my phone, not just Chrome.
Any other way to do this?
Thanks.
I've got a sticky situation. I'm developing a kiosk-style tablet application on JellyBean, and we're stuck with JellyBean.
We don't install a standard launcher on our Android tablets, and instead supply our own Home Screen/Launcher app, so that our application starts on system startup.
We were using a WebView for our GUI app. The WebView that comes with JellyBean is buggy and deficient in many ways, so our app doesn't work correctly in the WebView.
However, Chrome runs our app perfectly, so we want to switch to using Chrome, which we would launch from our own Home Screen application on startup.
We need to start it in full-screen mode, just like Launchers do when they launch any app/URL via a link that was placed on the Desktop.
I can't for the life of me find out how launchers pull this off.
I've tried adding --app="xxx", and/or --start-fullscreen to the /data/local/chrome-command-line file, but all to no avail. The additions options show up on the "chrome://version" screen in Chrome, but they have no effect.
Does anyone have any clue how they manage to launch Chrome in full-screen mode?
These tablets are all rooted tablets, completely under our own control, so no solution is out of bounds.
Thanks for any help!
Is there a basic example showing how to disable the default Android browser on a Samsung Galaxy S6, MDM or otherwise, without root permissions? I’ve already tried the basic profile example; however, it does not encompass what I need.
If you go to
settings>apps>(all tab)>Browser>Click "Disable"
you won't have to ever answer if you want a link or anything to open in Browser or Chrome. It will act like Browser isn't on your phone and default to Chrome.
I am developing an Cordova application and am working on making it accessible. In iOS, VoiceOver works fine and as you would expect with a native application. For Android, TalkBack briefly works on the first screen of the application. After the first screen, TalkBack stops responding (globally, not just in the application) and will not allow the user to swipe to the next element, or select any elements.
The content is build using all the right ARIA tags and following the specs, Android and TalkBack just doesn't seem to be playing nicely with HTML content and WebView.
The application is targeting Android 4.3 and Android 4.4.
Can anyone point to a Cordova / PhoneGap application that works properly with TalkBack on Android?
I have an enterprise Flex web application, served up over https, that runs fine on Flash player 10.0 and beyond on a desktop computer/browser.
However, when I run it from my HTC Incredible with Android 2.2 the app loads fine, but there is no on-screen keyboard and so I cannot log in. I can see the blinking cursor inside the username and password text fields. I can switch between them. I can even hit the login button and see an authentication error!
According to Adobe this should Just Work. Any ideas? I wanna show off our spanking new app to strangers at the bus stop!
Seems the problem is different implementations of the keyboard in the browser. See the comment from Adobe here as they shut the bug as unfixable: https://bugs.adobe.com/jira/browse/FP-5704
I have the same problems on a Galaxy S2 - though manually forcing the keyboard up here isn't an option as the address bar automatically gains focus.
Mobile Text Input
Flash Player 10.1 provides support for use of native device virtual keyboards with TextField support if no physical keyboard is detected. A virtual keyboard is automatically raised and lowered in response to focus changes on text fields when editing text on mobile devices supporting a virtual keyboard to enable unobstructed and intuitive text editing. The focused text field is centered in the visible region of the page and appropriately zoomed/scrolled to ensure it is not obscured by the virtual keyboard. Upon screen rotation, incoming calls, or other system events, any already existing text input is retained. The virtual keyboard works with TextField but does not currently work with the Text Layout Framework or other Flash Text Engine text.
The spark components in Flex 4 are not currently optimized for mobile. The next release of Flex codenamed "Hero" will provide mobile optimized skins for the spark TextInput/TextArea components. These skins are based on TextField and they are also optimized for performance with ActionScript skins and a more appropriate default size. Text support in the current Hero preview release is minimal, but the final release will be more robust, for example supporting scrolling in a TextArea. Check out the spec for more information: http://opensource.adobe.com/wiki/display/flexsdk/Mobile+Text+Components
It's probably worthwhile to note that the mobile features in Hero are designed with standalone mobile applications in mind, not browser-based applications. That said you might be able to grab those mobile skins and try using them in a browser-based Flex application compiled with Hero.
have you tried republishing your work strictly for 10.1? i believe that any applications which support versions of Flash prior to 10.1 are seen as Flash Lite on mobile devices, which may (or may not) be the problem.
it's worth a try.
Not a programming solution, but long press on the menu button brings up the keyboard if it doesn't pop up by itself (at least on my HTC Desire, 2.2 android).
Device: Kindle Fire
I had the same problem. My mathlab uses flash for homework assignments, and I could not access my keyboard for input. Until I found this.
Download and Install "Keyboardflash_1.0.0.apk" on your Android device.
go to the flash program in your browser
run the "Game Keyboard" app and click "Tap here to call out keyboard after exit"
return to your browser
You will notice I did not perform the direction the app gives you because the kindle fire is not compatible with those steps. Maybe it is with your device.
You may have trouble getting this to work with a browser app like "Dolphin"
Your Welcome :)
and respect the developer
Gamepad is also on the android market.