Has anyone using mobify.js seen talkback not work, especially on Android 2.3? We know it's not the device as other non-mobify sites work fine. Newer versions of android work fine, just 2.3.
I suspect it's how mobify work that is cause the problem, just i can't confirm.
Cheers.
M
According to this FAQ the default web browser is not accessible in anything below Android 4.0. Unless you can confirm that 2.2 works with Talkback this is the problem.
Related
I'm confused on why UsbManager.ACTION_USB_ACCESSORY_DETACHED from USB Accessory doesn't triggered in Marshmallow and Nougat versions but when using pre marshmallow versions I can trigger the broadcast.
My codes are based on the documentation in USB Accessory link above so no need to paste my code, the only thing is it doesn't trigger when using Marshmallow and up versions of android.
Thanks in advance
As i search the issues in reports bugs in Google i was able to find this issue on android firmware so basically it's more like on android OS problem that UsbManager.ACTION_USB_ACCESSORY_DETACHED was not triggered.Kindly visit on this issue.
Our Phonegap app using inappbrowser works really well on every device tested except one using Android version 4.3 where the CSS seems unresponsive and the onscreen keyboard doesn't pop up when you tap in text fields. I can't seem to find any documentation on minimum versions of Android for supporting the various Phonegap plugins.
From my experience, I've used phonegap a far as Android 2.1 . The problem you could have on such older versions is the phonegap version.
You should provide further information such as phonegap version.
But I can assure you that Android 4.3 has a very broad support for all Phonegap/Cordova 5+ plugins.
If I were you I wolud try updating phonegap version according to your desire of minimum Android version you want your app to be executed on.
For example, until Android 2.3 on inappbrowser apps it wasn't able to use overflow scroll, so you had to use an external plugin to get that effect, which was really annoying.
Hope this helps.
Without any code it's hard to diagnose, but it might be a browser issue: Android 4.3 does not necessarily ship with Chrome, so it might be still running the old "Android Browser", which does not support all (CSS-)features Chrome supports. Caniuse helps to find out if a browser supports a certain feature.
If it's indeed a browser issue and you have to support older browsers like the Android Browser, you might want to check out Crosswalk. It provides a recent version of Chrome as a WebView and as InAppBrowser with consistent behaviour on all Android 4.x devices. Downside: Your app's size will increase...
If it's not the browser you might need to show us some of your code.
I've got a new Samsung Note that has a lot of touch points accessible via the hardware...but I can't seem to get 2 simultaneous touch events registered in the browser, tried quite some demo apps I've found online. (there's a bunch of them listed in this presentation)
I also tried various browsers: Firefox (beta), the default browser, and Dolphin HD... but neither seems to be able to get it right.
Anybody else got this working perhaps, or knows why it doesn't?
Thanks a lot in advance,
Jochen
Opera Mobile 11 supports multitouch.
It's possible that Samsung has customized WebKit on the Note and broke multi-touch handling. Good luck getting definitive answers on that either way.
But, does this page help?
According to http://www.html5rocks.com/en/mobile/touch.html
Android 2.3.3 (which should be very close to the one Galaxy Note uses, 2.3.6) does not support multitouch in the browser.
You may want to try Firefox for Android (I haven't tried that).
Have a go at this MultiTouch Polyfill. It enables you to create a multitouch enabled WebView - which most android 2.x devices (such as the Samsung Note) don't have by default despite the device registering more.
Haven't tested it with the mentioned demo apps from the presentation, but i can say it works for the scripty2 Touchspector as well as pinch zooming OpenLayers and Google Maps.
If this will be helpful, i'd be happy to bundle it up as browser application and put it on the market so you have something to test touch applications with on a 2.x device.
Chrome beta works too! Perhaps even better than Opera Mobile...but slower.
How many browsers support
-webkit-overflow-scrolling:touch
iOS5 does, what about the rest of them, and android etc..
As of this writing, -webkit-overflow-scrolling was exclusive to Mobile Safari on iOS 5 and later.
As of mid-2012, the latest Android version (4.1 Jelly Bean) does not support it, but it IS supported in Chrome for Android, which can be downloaded from Google Play (and only supports Android 4.0+). Android 3.0+ supports overflow: scroll, but it's not very snappy.
Just iOS5 right now. The only other major mobile browser that would use this would be Chrome as others have their own extensions.
Since this post is now 2 years old, just thought I'd share some helpful updates I dug up:
Chrome Browser for Android no longer supports -webkit-overflow-scrolling? Is there an alternative?
http://cantina.co/2012/03/06/ios-5-native-scrolling-grins-and-gothcas/
Please note that the Android 4.1.2 Stock Browser that comes with the Galaxy S2 official firmware reports that it supports webkit-overflow-scrolling, but when you poll the value, it's always an empty string.
Which can lead to nasty bugs like this one: https://github.com/lazd/iNoBounce/issues/8
MY jquery mobile app m.dosomething.org works fine on Iphone but on Android and Motorola keeps popping up keyboard on the form. It works fine with Android on my HTC. I tried with different Jquery mobile versions but does not seem to work for now. Also with out the android SDK , its kind of tough to test. Is this a common issue for Androids on Motorola ? Is there a way to resolve this?
I upgraded my Jquery mobile version to beta and Jquery version to 1.6. That seemed to have taken care of that issue for now.
Thanks for the help