03-04-2011 09:26 PM
I'm currently developing a webworks application and it extremely slow on the torch device. But working fine on the simulator.
By slow, I mean the ui takes atleast takes 3 second to respond after the touch gesture, either scrolling or clicking a button. And page transitions lag.
I'm currently using jquery and jquery mobile, could those be causing the problems?
Solved! Go to Solution.
03-20-2011 05:57 PM
I am facing a similar issue, my application loads normally on simulator, but when moved to the device it takes about 3-4 seconds each page to load, eventhough I am testing on local network (through WiFi).
The simulator and the device are the same: 9700 Bold.
n.b. I am using jQuery 1.5.1
03-28-2011 07:38 PM
Same issue here, with the same specs as mchaimech -- 9700 Bold, app uses jQuery 1.5.1. It's only one page, but all actions are a little delayed, and one in particular (which resets some elements and redraws the page) is very slow. Not bad on the simulator, just bad on actual hardware. Very frustrating.
03-29-2011 01:17 AM
The primary item that stands out to me with slow behavior of Web content in this context while running on a live device is processor - you do not have a simulator running on a developer machine powered by a strong processor (while on the Bold 9700 its a 624Mhz chip).
03-29-2011 03:28 AM
As i wrote in the prevous-similar thread before:
it's not fair to compare between simulator and the real device,
because of its difference hardware.
06-08-2011 01:24 AM
Hi, i am facing the same issue i have a web works application but the ui response is delayed 2 to 3 seconds, please if anyone of you has been able to solve this issue or have any tips for me than please help...
06-08-2011 04:53 AM
My guess is that it is because you are using jQuery mobile on your page. jQuery uses extremely LARGE amounts of DOM manipulation on the live DOM and doesn't "yet" use document fragments or remove sections of the DOM to manipulate it.
This is because the next line of code may be gathering measurements from the changes made on the previous line of code.
Here is a post where I explain it more and how you can get orders of magnitude speed increases by manipulating the DOM in a mobile efficient way.
06-10-2011 12:49 AM
Thanks alot man that was really what i was looking for, solved my problem though there was a minor problem that after removing an element from DOM I could not use any document method like document.getElementById(), found an other tutorial for solving the problem blackberry Webworks Performance Issue