If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Long start time of Firefox and start page on HTC Desire Z especially with activated Sync

NEW
Unassigned

Status

()

Firefox for Android
General
5 years ago
a year ago

People

(Reporter: Thomas Schwecherl, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
I'm using Firefox for Android and Firefox Beta for Android on my HTC Desire Z smartphone with 512MB RAM. I'm waiting several seconds at the start of Firefox (both versions) till the address bar and the awesome screen are usable. The start time extends extremely if Sync is activated. Firefox more or less is not usable on this device for quick web surfing activities and this status hasn't improved in the last year.

I know the device is not the newest, but I thought Firefox (and Firefox OS) should be usable on a broad range of devices and not only the upper class phones with 1GB and quad core.

How can I log something to help you to understand why Firefox is so slow on HTC Desire Z? If you are interested I will try my best to give you more information.
> How can I log something to help you to understand why Firefox is so slow on HTC Desire Z?

Unfortunately, I don't think there's really much that captured log output would reveal in this case. If online available specification information is correct, the Desire Z, with adequate available RAM is constrained at the mercy of its MSM7230 800 MHz CPU.

I have a Nexus One with roughly equivalent hardware specifications, QSD8250 @ 1GHz and it's a noticeable difference.

> I'm waiting several seconds at the start of Firefox (both versions) till the address bar and the awesome screen are usable.

Might be worth checking out a CPU monitoring application to see if org.mozilla.fennec is spiking, or you can try out the Android developer options CPU usage option.

CC'ing :kbrosnan to comment if his Desire Z yields similar performance.
You need to log in before you can comment on or make changes to this bug.