Android 4 list is performing worse in ST2 then ST1 (slow scroll)

[cchilds]

Thanks for the thorough explanation. I was going to go to my boss this morning and tell him we could no longer continue with ST because of this issue. I'm glad I saw this and I can't wait for the new releases. Thanks for all you guys' hard work!

[Jamie Avins]

Just a quick note, that the new Samsung III is seems to get around the issue by just throwing hardware at the problem. It preforms well even in the current state.

[sven]

Just a quick note, that the new Samsung III is seems to get around the issue by just throwing hardware at the problem. It preforms well even in the current state.

I can confirm this. The S3 performs very well

[hotdp]

Just a quick note, that the new Samsung III is seems to get around the issue by just throwing hardware at the problem. It preforms well even in the current state.

Yes, the lag is minimum on this device (S3).
But try to scroll slowly on Disclosure list etc. by holding your finger on the list and moving up and down:
http://dev.sencha.com/deploy/touch/e...ink/#demo/list

As you can see it lags, also on the S3.

Also sadly, there are more and more older devices that are getting 4.0.x and they don't have the hardware power.

The slow scroll issue seems like a huge and strage "bug"?

Please keep this thread updated Jamie and let us know if you find anything.

[dsac]

getting a dealbreaker for us too

ST is nearly unusable on early 4.0.x devices

[gubarez]

Good news from Google, guys!

Here is part of the changes in Jelly Bean! (read full at http://developer.android.com/about/v...elly-bean.html)
Android Browser and WebView

---

In Android 4.1, the Android Browser and WebViews include these enhancements:

• Better HTML5 video user experience, including touch-to-play/pause and smooth transition from inline to full screen mode.
• Improved rendering speed and reduced memory usage for better scrolling and zooming performance.
• Improved HTML5/CSS3/Canvas animation performance.
• Improved text input.
• Updated JavaScript Engine (V8) for better JavaScript performance.
• Support for the updated HTML5 Media Capture specification (the "capture" attribute on input type=file elements).

Now we just wait... along with ST2.1!

[hotdp]

Hi Jamie Avins,

It's been over three weeks since I reported this bug.
Can you give me an update on the timeframe for a bug fix?
As more and more people get 4.0.x the problem is getting bigger by the day.



@gubarez

Yes, 4.1 seems better (On the paper I have not tested the native browser in 4.1 yet) but sadly it does not fix the problem with all the people who still have 4.0.x


As many others I hope that one day all Android phones will use a good version of Chrome, but until then we have to get this fixed.

[SunboX]

Yes, 4.1 seems better (On the paper I have not tested the native browser in 4.1 yet) but sadly it does not fix the problem with all the people who still have 4.0.x

As many others I hope that one day all Android phones will use a good version of Chrome, but until then we have to get this fixed.

As I read yesterday, the new Chrome Engine works NOT in any UIWebView on Android 4.1. UIWebView still uses the "old" Android Browser Engine. So no pseudo native App will participate from the new Chrome Browser. That´s really bad news.

However, for web views –such as pseudo browser or native apps- the old engine is still there, so there is no Chrome engine from web views yet.

Source: http://www.mobilexweb.com/blog/chrom...lly-bean-html5

[hotdp]

Can I get any kind of official update on this?
1.1xx views show the interest in this.

[dsac]

they're going to replace the old webview with a stable cromium release in the near future, i think