I'm developing a PhoneGap App with jQuery "collapsible content" elements. Now I'm testing the app under Android 4.2.2 on a Nexus 7 device and I have a problem with the expand/collapse event. The element expand and collapse immediately after the touch event. If I tap and hold the element for a second the collapse or expand event works.
It's very strange because it works under iOS (iPhone 5, iPad) and on Android 2.3.5 (HTC Desire HD)
Please help.
You might be seeing the same double-click bug as this. Phonegap 2.4.0 with Android 4.2 - strange double click behaviour
You can try the solution proposed in the link.
Related
I'm using dojo performTransition to switch between views and it is working fine all the devices except Samsung devices with Os version higher than 4.1.x
Transition is working but all the previous and next view are visible and I'm able to see all the screens that I navigate from on the screen by swapping the screen
Please look at the following dojo defect:
Transition issue on some Android 4.1.x devices:
https://bugs.dojotoolkit.org/ticket/17164
As well as this previous post that may help you based on Ken's and Idan's suggestions:
IBM Worklight 6.0 - Dojo application doesn't work on Samsung Galaxy S3
manually hiding and showing screens using css display 'block' and 'none' after transition is finished worked for me.
My problem is described in the following.
I recently developed a Phonegap app (Android and Ios are the target platforms) and deployed it on the markets. My app mainly consists in an event list.
The list is obviously scrollable. The purpose is to give a native feeling experience to the users or at least something close to it. Actually, I would like to enable inertia for most users (everyone would be awesome!).
The app can’t be downloaded by android < 3.0 phones, so it doesn’t matter if the solution excludes android 2.X users. In addition, for the moment the app is not design for tablets so I don’t mind if the solution doesn’t works with android < 4.0.
I use the following CSS property on the scrollable div:
overflow: scroll;
-webkit-overflow-scrolling: touch;
On Ios, there is absolutely no problem. It is fast and inertial scrolling is enabled.
With Android, I'm still having problems with some phones. Here are my tests:
Nexus 5 (Android 4.4) : inertia Ok
Sony Ericsson (Android 4.0.4) : inertia Ok
Samsung galaxy Trend (android 4.0.4) : inertia Ok
Samsung Galaxy Note 3 - SM-N9005 (Android 4.3): No inertia
Samsung Galaxy S4 (Android 4.3): No inertia
I don’t’ use any JavaScript library for scrolling (for example Iscroll ect…) and I don't want to do so except if it is a really lightweight librairy. In fact, I have tried Iscroll and the result is unusable because it is too slow and jerky. By the way, the event list contains gradient, images, text, shadow ect…
I have done a lot of research on the internet. And now, I feel lost!
I even don’t know if the problem is related to:
The manufacturer layer
The Android version
The default browser on the phone (I think not because it appears
that Phonegap doesn’t use it)
The embedded PhoneGap webKit rendering engine
Deprecated CSS properties : see this article
Something else?
It is a bit weird because it works on 4.0.4 and 4.4 but not on 4.3… I start to think this is related to manufacturer…
Any help, solution or information about the above would be really appreciated.
Not sure if you have solved your problem yet, but I just came across this issue.
I was using Hammer.js to detect drags for the sidebar, within doing so, I called preventDefault() which affected scrolling inertia in the android default browser, but not chrome. Removing that call fixed the issue.
I had the same problem. I looked into it for quite some time and the only solution I know is using a scrolling library. The best one I found is Overthrow: http://filamentgroup.github.io/Overthrow/
Cool thing is that it uses native scrolling whenever it can and only reverts to javascript when needed. Even works for me on old Adroid devices, while keeping that native scrolling feeling on iOS.
I'm developing a phonegap application for both iOs and Android platform.
I'm using AppFramework by Intel (ex. jqMobi) and it works like a charm in iOs, it works good also on android, the only thing is that the scrolling is not working in Android 2.3.6 and I can't figure out why. I don't know if it works in most recent version of Android on real device, it's not working there too in the emulator.
Thanks in advance for any suggestion...
On Android 2.3.5 & 2.3.6, JQM's header and footer scroll with document and then reposition (back to top and bottom) after scrolling has stopped. This happens when header and footer are set to data-position="fixed".
It appears that these versions of android have buggy CSS implementations of {position:fixed;} and therefore JQM's behavior appears erratic when compared to other adjacent Android versions.
I have made HTML5 application which is using vmoss platform, similar to phonegap. The application was running smoothly on samsung galaxy 10.1 tab with android version 4.0.4. After the client updated the device to android 4.1.2 now he is complaining of following issues.
Calendar control not working in new version
Text box controls having focus issues
Application GUI Issues because response is very slow
The page where issue of slowness comes is the page where child pages are loaded inside one of its div.
Can someone tell me, is it android os update issue or what?
i think it's because of the platform not updated to work/cope well with version 4.1.2
this one is vmoss platform issue.
Better try to run simple Html page with all these control without using the VMOSS at backend and see if there will be any issue.
Some time the version of Jquery doesn't fully support by the browser.
I created an application in html and JavaScript but it has the same bug is that with Android 2.3.6 with iPhone 5.0, while the Android version 4.0.4 the bug is not there.
To make it easier to explain my problem I put a link to the recording of my monitor.
The video on the iPhone, but on Android is the same. This application is for my thesis.
You can listen for showkeyboard/hidekeyboard events and resize your UI as appropriate.