Horrible Android browser performance?

Question

css

There is such a problem - in the standard Android browser on the Galaxy Tab 10.1 , the performance of everything related to changing html is simply terrible. Moreover, even in the most simple examples.
Canvas , changing css on timeout and even newfangled css3 - everything is broken by the ruthless brakes of the flagship tablet. And pay attention - this is the most primitive of actions - on an empty page, moving a black square 50 * 50 in size. I didn't even use any frameworks to eliminate the overhead. For some reason, I have a suspicion that everything depends on the too rare dom-repaint.

Have you solved performance problems on Android devices and, if so, how?

Answer 1

Same stuff.
Did you install other browsers? As I understand it, it's just not optimized for ARM, but stupidly assembled for the platform. Sometimes it crashes if there are a lot of dynamic divs, such as transition to a comment, and there are a lot of comments.

Answer 2

SHW-M380S
Android 3.2, Overcome ROM 2.2.0
Dolphin Browser for Pad 1.0beta and "native" browsers:
I don't see "creepy" brakes - some uneven movement is visible.
I assume that the matter is in your private device.

Answer 3

Have you tried moving objects not through left/margin-left changes, but through CSS translate? In iPhones, it seems that iron acceleration is used in this case. It is necessary to experiment with different properties and methods, since one thing can work slower, and another one can work faster. It’s bad, of course, that for each browser you eventually have to write your own way, but what can you do.
For example, I came across the fact that in chrome under Windows, CSS animation (through transition) worked slower and more jerky than javascript through requestAnimationFrame.
In general, a good site can be made without animation. You have some strange problem.
And in general, maybe you just installed Trojans on your tablet and they slow it down?

Answer 4

Galaxy Tab 10.1 is the worst browser ever. Even the taba of the seven is better.
css3 unfortunately refuse - it brakes. Unfortunately, the test cannot be done especially (no one will tell you how ???) - so we can’t say what exactly slows down there. Rejection of css3 helped us.