Ext version tested:
Sencha Touch 2.2
Browser versions tested against:
Chrome on HTC One (Android 4.1.2)
Stock HTC One Browser (Android 4.1.2)
Description:
Sencha Messageboxes and the like won't release focus after clearing them in the stock browser or webviews on an HTC One.
This problem doesn't happen on Chrome or on other Android 4.1.2 phones AFAIK. Tested a Samsung today and all worked as expected.
Steps to reproduce the problem:
Using an HTC One, go to the Sencha Kitchen Sink demo here: http://cdn.sencha.io/touch/sencha-touch-2.2.0/examples/kitchensink/index.html#demo/overlays
Tap on 'Alert', and then 'OK'. Works fine in Chrome. Does not work in either stock browser or in a webview (so no PhoneGap/Cordova either).
Yes, I know, this belongs on a Sencha board. I posted a thread there this weekend, and the post was deleted Monday morning. Google 'sencha default overlays Android 4.1.2 HTC One' to see a dead link. So I'm posting here.
Perhaps my frustration was showing and Sencha didn't like the tone of my post. I really would like to see some kind of workaround from either Sencha, HTC or someone here on SO.
Does anyone know of a software workaround that will allow Sencha Touch 2.X to work on an HTC One? Or are we stuck waiting on HTC and the carriers? Not really Sencha's fault, but this leaves me down on HTML-5 mobile app development.
Answer courtesy of appglu in Sencha forums:
in messagebox.js
set hideAnimation to null instead of:
hideAnimation: { type: 'popOut', duration: 250, easing: 'ease-out' },
This solution works on my new HTC One running my Sencha 2.2.1 app built in Cordova 3.0.
Further discussion here: http://www.sencha.com/forum/showthread.php?262324-Sencha-Messagebox-and-Overlay-Problems-on-HTC-One-Browser
Related
The call is working perfectly fine for the first time.
But after that it freezes just before connecting to WebRTC, this is currently happening only on Samsung Galaxy S5 out of my 5 devices that I test upon.
Other devices are:
Motorola Moto G2
Nexus 5X
Samsung Grand
Samsung S2 (Genymotion emulator)
Please point me to something that can help... Sorry, but I don't have the logs for this error
I am from Crosswalk team. We are maintaining some basic tests for WebRTC on Crosswalk and haven't find similar issues.
If you can share your test page, it could accelerate the problem fixing.
Another way is to file bugs a bug JIRA where we use to track bugs,
https://crosswalk-project.org/jira/secure/Dashboard.jspa
I'm currently working on a Wordpress site and am having an issue specifically with Galaxy S4 and other versions. It seems to work fine on all other mobile devices, on multiple mobile browsers (Chrome, Safari, etc.) After doing some research I've seen a couple of people having the same issue but no real answer to the problem.
The issue even recreates with emulators built into the desktop browsers, so I have tested it on multiple version of Galaxy using Chromes emulator and the same issue occurs as on the hardware device.
Here is the link to the site I am working on: http://beta.iqcando.com/
I'm truly at a loss as to what could be causing this, as it appears to be fully mobile on other devices. Any suggestions or solutions are welcome, thanks in advance!
There is an
overflow-y: hidden!important;
on your html in style.css on line 109.
When you remove that the scroll works fine ;)
If you want to debug your site on mobile, on chrome you can install sdk and then use chrome to inspect the mobile version of your site.
https://developers.google.com/web/tools/chrome-devtools/debug/remote-debugging/remote-debugging
I've installed my app on Samsung S2 GT I9100, but its not working.
The problem I figured out is, deviceready of cordova is not been called.
I read some articles, many people faced this problem. But no solution worked for me.
I tried the same app on other devices also it worked (like Moto, Samsung other devices, Asus etc).
The problem is Cordova doesn't support android versions which goes below 5% distribution according to Cordova-Platform-Guide. So you need atleast 4.1+ to continue to use Cordova in your app. Other wise you can switch back to older version of Cordova.
You can see latest survey of Google's distribution dashboard.
Do I need to install an emulator of some sort? Are there any online services that offer this? I've found little guidance elsewhere on this matter. I'm on Windows 8, just trying to figure out (locally) why my android users are experiencing issues with an MVC app.
The easiest way would be to download and install the Android SDK and use the emulator to try and reproduce the problem. The SDK has emulator images for all versions of Android, and you can create devices with different screens (resolution/dpi/size), so if your site uses responsive design you can test also how it scales across different devices and whether the problem affects one specific or all Android devices.
However, it is possible that the emulator might not be good enough for reproducing and understanding the problem. The Android SDK images come with the browser that is part of the Android Open Source Project (AOSP). While this browser is technically based on WebKit, it is based on a rather old version of it. Most OEMs that have built Android devices have signed the Google Mobile Services (GMS) license ship on their devices the Google suite of apps which includes the latest version of Chrome, which is based on the most recent WebKit version. The difference in the behavior between the two browsers is rather big.
So if the problem turns out to be with Chrome instead of the AOSP Browser, you will have to buy a real device and test on it. Depending on the budget you have and whether you want a phone or a tablet, you can go with a Nexus 5 ($350 w/o contract), Nexus 7 ($230 wifi only), or a Moto G ($175 w/o contract). Of course, you could also buy Samsung Galaxy S4, HTC One X, or a Moto X, but they all will cost you more.
It might be worth also borrowing from someone a Samsung Galaxy Ace 2, or equivalent low end MDPI device.
well, you can install an android emulator and use the browser there (http://developer.android.com/tools/devices/index.html), but it's extremely slow,
so you should, instead, try Genymotion. It's an android virtual machine and it's pretty smooth. (http://www.genymotion.com/)
another option, is the Opera mobile emulator, but that is specifically for the mobile Opera browser. (http://www.opera.com/developer/mobile-emulator)
if you want a chrome specific approach, try this (https://developers.google.com/chrome-developer-tools/docs/mobile-emulation)
http://developer.android.com/sdk/index.html has the emulators.
… but it may be just as cost-effective to just spring the $40 for a cheap Android tablet with WiFi.
I copied a tutorial like the simple Hello World App which I followed and created to try features on in Flex 4.6. It work it the emulator with the Flash Flex 4.6 software but when it cam to using / testing the simple App on a real phone there was a problem.
it installed on the HTC Wildfire S but when it came to running the app, there was a error with the following.
"The application HelloWorld(process air.HelloWorld has stopped unexpectedly. Please try again"
I am new to Flex but this error is making things harder, It seems this is a unknown error the code seem to be all correct I checked it with the tutorial.
The HTC That I tested on has the following os
Android version 2.3.5
Software number 2.13.206.1
Kernel version 2.6.35.10
Do you know any common reason for this error, the firmware is the latest 2.3.5
Thanks
If i could i would just comment this, but anyways...
I have few working Flex mobile apps which i tested on android devices. Yesterday i only had my friends HTC sense 2.3.3 (which i didnt used before) available for testing. None of my working AIR apps did work on that phone. I am always using captive runtime. App size is usually around 10 mb apk, and 20 mb when installed (even small hello world app always have about 20mb when installed with captive runtime). Strange thing is, that apps on HTC sense had only 10 mb after being installed - so there was clearly some problem with deploying captive runtime...
If your hello world works on flash builder simulator, then its probably some problem with device.
You should try another devices.
You should also check, if your app size is around 20mb...