a-frame runs poorly on high-end android devices

[ngokevin]

Description: Slow, laggy for A-Frame. Pure three.js (circa. r70) is fine.

• A-Frame Version: 0.1.3
• Platform/Device: Android mobile (S6, Note 4, Note 5)

[ghost]

I'm experiencing the same issue on iPhone 5.

[ngokevin]

Bad performance on iPhone 5 is expected as it runs nearly 4-year old hardware. We haven't come up with an official list of supported devices yet, but iPhone 5 is too old to become on that list (especially since the screen would be too small for VR).

[ghost]

@ngokevin, fair enough.

[bryik]

How slow is "laggy"? <30 FPS?

[dmarcos]

What demo exaclty? content with video? Scenes with lots of geometry? Lots of different textures? This issue is not actionable.

[ngokevin]

Every demo. Like 15 FPS. Is that actionable?

Try Anime UI which runs perfectly smooth in iPhone.

[ngokevin]

I will get more information later, but it's pretty widespread and easily noticable.

[bryik]

@ngokevin hmm, I get >30 FPS with Anime UI on my HTC One M8 using Chrome. However, I did notice instability (browser crashes) and stuttering with Firefox.

edit: tested the same demo on a Nexus 4 and it ran even smoother in Chrome (lower res.) and slower in Firefox (~10 FPS).

Here's a copy of Anime UI (with stats turned on) for others to try

[ngokevin]

@bryik thanks for testing, glad to know it's not on all Android. Don't think this is actionable, @dmarcos pointed out Android accelerometer hardware might not provide data very quickly.