Response title
This is preview!
Move this topic
Replies(32)
Hi,
same issue, ICS 4.0.3 at my Nexus S, pages loading blazing slow or doesn't even load.
Browser incompatibility?
Leave a comment on karolyi's reply
One of my friends has Galaxy Nexus with Android 4.0. With his phone, the page is loaded properly.
It may be a problem with Nexus S. But I need to test more with different Android 4.0 devices.
YW
Leave a comment on ahn.yongwoon's reply
Seeing the same problem with my nexus S. The application is dead slow.
Leave a comment on aditya.rustgi's reply
Does someone has a response for it. If it is supported or not ? and if a fix is coming ?
Leave a comment on xavier.ameslon's reply
On my Nexus S 4.0.3 it looks like the click event have a delay...
Leave a comment on michal.klima_jquery's reply
Same problem here..my site totally breaks with ICS on a Nexus S.
http://fmk.mobi
I've attached a screen shot of what it should look like vs. ICS.
Do we have to wait for an ICS update before this will work?
http://fmk.mobi
I've attached a screen shot of what it should look like vs. ICS.
Do we have to wait for an ICS update before this will work?
Attachments
- Screenshot_2012-01-11-22-49-03.pngSize : 91.29 KB Download : 1162
- workingimage.PNGSize : 146.24 KB Download : 1074
Leave a comment on alykhan's reply
Same problem here, page transitions are REALLY slow and shocky. Buttons seem not to respond, then suddenly kick into action.
Leave a comment on freshbase's reply
I have a rooted HTC Sensation running Android Revolution 5.0.1 rom (Android 4.0.1). I've been using JQM 1.0 and Phonegap 1.2 to work on a simple application. I would just like to report that so far, besides the fact that ICS seems to be scaling things very differently (my application looks much smaller), everything seems to be working fine.
My phone settings say it uses WebKit/534.30 under Settings / About Phone / Software information / More / Brower version, if it matters.
My application consists of a single page that does a search using getJSON and then populates a listview on call back. A click on a listitem triggers a new ajax call to a webservice and displays the results on callback. I haven't done any heavy traversing yet besides using .each on getJSON callback to populate my listview.
Leave a comment on sebotron's reply
I read about big changes to the Android 4.0 browser. switching to tile-based rendering for example.
My Galaxy Nexus is showing no transitions at all, and other frameworks like Sencha Touch are showing flickering screens and broken transitions.
If you set up a global div style to set rotateZ:0 (aka enable hardware acceleration) things don't exactly improve but do change.
I did some testing with the animate.css demo page and everything ran fine so maybe there is hope. (Then again check out his blog for the bit about Android fibbing about what kinds of CSS3 transitions it really supports pre-4.0).
Leave a comment on richardleggett's reply
Hi all -
..............................................
Todd Parker
jQuery Mobile & UI design lead
Partner, Filament Group Inc.
todd@filamentgroup.com
Thanks for chiming in with test results. We still don't have a ICS device in our test lab so we're relying on emulators and team member Ghislain to test. Anyone know how we can get our hands on a device?
Anyway, we've been tracking this as well as we can and it seems like ICS is pretty horrible with any sort of transition which is worse than Honeycomb and that was worse than Gingerbread so things are going downhill in Android instead of better.
We're working intensely on trying to find a sweet spot for transitions that are at least blink-free and show some animation frames on Android which is tough given how terrible the platform is. At the moment, we have a bunch of branches in active development, each very unfinished as we try different approaches.
If anyone wants to give these a test and tell us how things are looking in ICS (keep in mind these can be pretty busted), please do.
The "fade-in-out-transition" branch is probably the most polished and it switches to a simple fade out, then we scroll to the top before fading in the new page. This uses a new minimal loader style and focuses on making transitions as fast and clean as possible.
The "slide-transition-experimental" branch makes some tricky tweaks to the slide transition to make it more repliable in various versions of Android. There are also "new-transitions" and -b, -c, and -d versions where we're playing with how and when the loader appears which impacts smoothness.
Anyway, this is a top priority and we're making good progress but Android is really challenging. Ideas, feedback and test results are appreciated.
We're tracking our transition work on this ticket:
..............................................
Todd Parker
jQuery Mobile & UI design lead
Partner, Filament Group Inc.
todd@filamentgroup.com
I use a Nexus S + ICS 4.0.3. Scroll is smooth but transitions … OMG. I tap a button, nothing happens durint 3 seconds, then it turns blue (:hover state I guess) for another 2 seconds, then the screen is white during one more second. Finally, I can see the other pageHere is the latest version, be interested to hear how it's working. We're close to landing this on master and can refine a bit from there.
I see the same as tbasseto on nexus s + ics.
If I disable OpenGL rendering in the browser I see the animations and the ui is more responsive.
to turn off OpenGL rendering:
1. Open your browser
2. Enter "about:debug" into the URL bar
3. The browser is now in debug mode, press menu button and go to "Settings"
4 go to "Debug" (visible when in debug mode)
5. disable OpenGL rendering
Browser rendering is more responsive for me on the Nexus S with ICS when this is disabled.
Leave a comment on toddparker's reply
Give the " fade-out-in-transition" branch a try to see the new default fade transition that should be smooth, even on ICS. Note: other transitions are wonky in this branch, only the default fade is working.
Demo page here: bit.ly/sa6Z4B
See issue above for updates...
..............................................
Todd Parker
jQuery Mobile & UI design lead
Partner, Filament Group Inc.
todd@filamentgroup.com
..............................................
Todd Parker
jQuery Mobile & UI design lead
Partner, Filament Group Inc.
todd@filamentgroup.com
This demo looks horrible on my Nexus S with ICS... :(
It hardly seems to respond to my clicking on the links in the overview list. then the next page flickers into view.. tile by tile..
It's working a lot better on a Samsung Galaxy I have with Gingerbread.
Leave a comment on toddparker's reply
I also updated my Nexus S to ICS. after that the browser is weird. Rendering sometimes hardly works at all. pages stop rendering. Pages are loaded in tiles and sometimes not all of them render correctly. Text is blurry.
jquerymobile does not work properly
jqtouch does not work properly
sencha touch does not work properly
anyone here have a galaxy nexus device and can see how these things are performing in ICS on that device?
Leave a comment on bjossi's reply
I think it's pretty clear from reports that ICS needs a bit more time in the freezer ;)
I'm hearing that the Nexus S upgraded devices are pretty unusable in general but the Galaxy is quite a bit better. Both still sound worse than 2.x and even 3.0 (which is a blinky mess). Let's hope Google has an update to set their browser because we really can't fix their broken rendering on our end.
Keep updating this thread and the issue above with info, we appreciate the testing help.
..............................................
Todd Parker
jQuery Mobile & UI design lead
Partner, Filament Group Inc.
todd@filamentgroup.com
..............................................
Todd Parker
jQuery Mobile & UI design lead
Partner, Filament Group Inc.
todd@filamentgroup.com
Leave a comment on toddparker's reply
hi
my new gallaxy nexus with ICS shows my jQuery mobile site a whole lot better than my old gallaxy s 1 with gingerbread.
I don't see any problems.
Alex
Leave a comment on barbalex's reply
My Galaxy Nexus with ICS works fine with the bit.ly location above. While on the topic of ICS, I am seeing an issue with my app in the webview when we make a selection in a nested list.
If your finger touches the center of a list element that element gets selected. But if your touch near the edge of the element, then the element seems to get selected but then it jumps to the next element, which ultimately gets selected. This is not happening with Gingerbread phones.
Any clues on why this is happening? I have a feeling it has something to do with the high resolution of the phone but not able to put a finger on it. I have tried various <meta> commands but they don't work.
Tried the following <meta> tags:
<meta name="viewport" content="target-densitydpi=device-dpi" />
<meta name="viewport" content="target-densitydpi=high-dpi" />
<meta name="viewport" content="width=device-width, initial-scale=1">
Thanks in advance,
Vish
Leave a comment on vishyr's reply
Hi, could anyone try on Honeycomb?
Even on emulator I have the bottom screen chop off, I think it was because WXGA is wide screen and the portrait in WXGA is actually reverse. Rotating screen mess up the screen/viewport.
Leave a comment on joven.chiew's reply
Is the only fix for this an update to ICS? Any chance of a work around or maybe someone could identify things that don't work.
I posted some screenshots on my previous post and the output is pretty awful on ICS.
A.
I posted some screenshots on my previous post and the output is pretty awful on ICS.
A.
Leave a comment on alykhan's reply
Hi all -
Here is the latest version, be interested to hear how it's working. We're close to landing this on master and can refine a bit from there.
- We have a new test to exclude non- 3D transform browsers like Android 2.x from the advanced transitions so we fall back to fade for all to improve smoothness.
- Honeycomb (3.0) passes the 3D test and generally crashes and burns, hoping a lot of these devices will get a 4.0 upgrade because 3.0 is a complete mess
- Android 4.0 seems to work fairly well if it ships on the device (Galaxy Nexus) but if horrible if you upgrade (Nexus S) which explains why Samsung announced that a 4.0 upgrade will not happen. Sounds like ICS requires a fast processor to run smoothly so if you upgraded early or have a bootleg upgrade, expect poor performance, not sure what we can do to fix Google's mess here.
Looking forward to hearing reports from the field on this.
..............................................
Todd Parker
jQuery Mobile & UI design lead
Partner, Filament Group Inc.
todd@filamentgroup.com
Looking forward to hearing reports from the field on this.
..............................................
Todd Parker
jQuery Mobile & UI design lead
Partner, Filament Group Inc.
todd@filamentgroup.com
I take it you mean no upgrade for the Samsung Galaxy S? As an upgrade to 4.0 has been announced for the Tab (not 7.0), Galaxy S II and the Note if I remember correctly. I wonder what this means for performance in combination with JQM on these devices....which explains why Samsung announced that a 4.0 upgrade will not happen
Leave a comment on toddparker's reply
Yes, I meant this:
http://www.theverge.com/2011/12/23/2657132/samsung-no-ics-upgrade-for-galaxy-s-and-galaxy-tab
..............................................
Todd Parker
jQuery Mobile & UI design lead
Partner, Filament Group Inc.
todd@filamentgroup.com
..............................................
Todd Parker
jQuery Mobile & UI design lead
Partner, Filament Group Inc.
todd@filamentgroup.com
Leave a comment on toddparker's reply
After turning off OpenGL, the JQM page is usable but very slow to render the page on my Nexus S with ICS.
Yong woon Ahn
Leave a comment on ahn.yongwoon's reply
Hi All,
Same issue for us on ICS 4.0.3 on a Nexus S.
This presented with the bug "slow to display date and time pickers with jQM-DateBox components"
With some testing it appear the display of any dialogue display is incredibly slow.
The "fade" dialog on this page http://jquerymobile.com/branches/out-in-transition/docs/pages/page-transitions.html took 13.6 seconds to display after the button was clicked.
Also, everything works fine on our HTC Desice 2.2 device.
I'm not sure of our customer base usage specs, but it looks like we wont be supporting ICS for now.
I feel a bit better to see that it is not isolated to us.
Thanks,
Mark
Leave a comment on markyk's reply
I have the same problem with my Nexus S, on Android 4.0.3 using jquery.mobile-1.0.min.js
Leave a comment on willem.vermeer's reply
I've a Galaxy S unofficially upgraded to Android 4.0.3 (compiled from AOSP).
Transitions are smooth compared to Android 2.3.4 but, as mentioned, are *extremely* laggy (transition can take several seconds to load after the touch).
I have checked the CPU usage from adb shell:
top -m 40 -s cpu -t -d 1
and thread WebViewCoreThread of the process com.google.android.browser takes the whole CPU for the time (>5 seconds) between the touch and the transition.
Disabling hardware acceleration it works very similar to Android 2.3.4 (e.g. flip works badly but without any lag).
Other 3d test works, someone good and someone slow, but not laggy.
http://www.webkit.org/blog-files/3d-transforms/morphing-cubes.html
http://www.kevs3d.co.uk/dev/html5logo/
http://www.kevs3d.co.uk/dev/canvask3d/ultralight.html
http://www.kevs3d.co.uk/dev/eglogo/
CSS3 transition/translation is laggy also in this test page:
http://css3.bradshawenterprises.com/sliding/
Transitions are smooth compared to Android 2.3.4 but, as mentioned, are *extremely* laggy (transition can take several seconds to load after the touch).
I have checked the CPU usage from adb shell:
top -m 40 -s cpu -t -d 1
and thread WebViewCoreThread of the process com.google.android.browser takes the whole CPU for the time (>5 seconds) between the touch and the transition.
Disabling hardware acceleration it works very similar to Android 2.3.4 (e.g. flip works badly but without any lag).
Other 3d test works, someone good and someone slow, but not laggy.
http://www.webkit.org/blog-files/3d-transforms/morphing-cubes.html
http://www.kevs3d.co.uk/dev/html5logo/
http://www.kevs3d.co.uk/dev/canvask3d/ultralight.html
http://www.kevs3d.co.uk/dev/eglogo/
CSS3 transition/translation is laggy also in this test page:
http://css3.bradshawenterprises.com/sliding/
Leave a comment on michele.redolfi's reply
sorry for posting here, but I'm having similar problems in android 2.2 for smartphones after upgrading to 1.1.0 rc2. http://forum.jquery.com/topic/problem-with-links-in-android
after upgrading, the transition event for dialogs (at least) is broken too: all transition types acts as fade (in my notebook/google-chrome (18.0.1025.151) too). you can see in www.rssprocer.com/laarena/12345/aa/2.2 this behaviour. is there some workaround I can use to fix this? thanks
Leave a comment on shamank's reply
I just got an update for my Nexus S - Android 4.0.4. - browser seems to be fixed up a whole lot.
Jquery mobile and jqtouch working a whole lot better than with 4.0.3
Leave a comment on bjossi's reply
I also checked it. a stock browser in Nexus S with Android 4.0.4 works well with jQuery mobile.
Leave a comment on ahn.yongwoon's reply
Hi, we are still seeing some pretty bad slide transitions on both 1.0 (in production) and 1.1 (in our internal development environment).
I've been testing it on my Galaxy Nexus running ICS 4.0.2. Viewing our site through the stock Android browser shows broken transitions -
http://politix.topix.com/ . When viewing in the Chrome beta browser, the slide transitions occur, but are very very laggy (you only get a few frames of animation).
Our current planned workaround it to switch to the fade transitions that are being done for 1.x and 2.x devices, but we are surprised that jQuery Mobile 1.1 still shows issues on a Galaxy Nexus running ICS since that combination is specifically listed as being supported.
Is anyone else having issues with jQuery Mobile 1.1 witha 4.0.2 Galaxy Nexus (Verizon)?
Leave a comment on alpaca's reply
One more reason to get an iPhone :)
Leave a comment on bradycolton's reply
Change topic type
Link this topic
Provide the permalink of a topic that is related to this topic
Reply to ahn.yongwoon's problem
{"z8464483":[14737000003026365],"z8202887":[14737000002939041],"z2170053":[14737000002943513,14737000002976575],"z8435968":[14737000003013513],"z8346532":[14737000002977099],"z2421461":[14737000002934916],"z8476092":[14737000003264175],"z18842346":[14737000003262749],"z524188":[14737000003013135,14737000002962037,14737000002962035,14737000003253717],"z2254118":[14737000002934270,14737000002934880,14737000003013141,14737000003253819],"z600308":[14737000002957993,14737000002959537,14737000002962043,14737000002978073,14737000002978079],"z7087176":[14737000002965465],"z8253680":[14737000002957923],"z5569951":[14737000002967131],"z8459722":[14737000003252561],"z314273":[14737000003011133],"z8191238":[14737000002934379],"z7077514":[14737000002943083],"z8423875":[14737000003013193],"z1020703":[14737000002946453],"z8247686":[14737000002957361],"z5569958":[14737000002955563]}
Statistics
- 32 Replies
- 6608 Views
- 14 Followers
