Closed Bug 1207404 Opened 10 years ago Closed 10 years ago

Firstrun sync image is too small

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(firefox43 affected, firefox44 fixed)

RESOLVED FIXED
Firefox 44
Tracking Status
firefox43 --- affected
firefox44 --- fixed

People

(Reporter: liuche, Assigned: liuche)

References

Details

Attachments

(5 files)

The sync image is too small - either the files are in the wrong dimen resource folders, or the images need to be bigger.
I wonder if there is something weird with the image? I can't figure out why the images would be different sizes, even though they look like the same size when I open them locally. Antlam, any ideas on what could be different? I do notice that the devices/sync image is bigger in bytes than the coffee one in XXHDPI. This only affects tablets.
Oh, because the obvious answer is that we have some extra images for the import panel on tablets, specifically drawable-large-xxhdpi. We either need to add another image for large-xxhdpi, or be okay with smaller images for tablets. The actual solution is probably to ship a single very-large image and just scale the height per device type. "import" resources: http://mxr.mozilla.org/mozilla-central/find?string=coffee&tree=mozilla-central&hint= "sync" resources: http://mxr.mozilla.org/mozilla-central/find?string=_devices.png&tree=mozilla-central&hint=
try this
Flags: needinfo?(liuche)
Bug 1207404 - First run image is too small. r=sebastian
Attachment #8675979 - Flags: review?(s.kaspari)
I removed a bunch of images in the meantime, which cuts the apk size by some hundreds of KB. I tested this on a N7 (tablet), N5, Nexus S, and a Asus Transformer and everything worked fine. However, the Galaxy Nexus did not seem to be able to downscale from the xxhdpi resource I moved into drawable/ and didn't show the image at all until I reverted the hdpi files. I'll investigate more tomorrow, but the error was: 10-20 02:00:26.749 11774-11794/org.mozilla.fennec_liuche E/libEGL﹕ validate_display:257 error 3008 (EGL_BAD_DISPLAY)
Flags: needinfo?(liuche)
Attachment #8675979 - Flags: review?(s.kaspari) → review+
Comment on attachment 8675979 [details] MozReview Request: Bug 1207404 - First run image is too small. r=sebastian https://reviewboard.mozilla.org/r/22537/#review20075
(In reply to Chenxia Liu [:liuche] from comment #5) > I removed a bunch of images in the meantime, which cuts the apk size by some > hundreds of KB. \o/ > However, the Galaxy Nexus did not seem to be able to downscale from the > xxhdpi resource I moved into drawable/ and didn't show the image at all > until I reverted the hdpi files. What version of Android is the Galaxy Nexus running? Maybe back then the xxhdpi bucket wasn't added yet?
I actually missed the relevant error, which popped up when I turned logging to verbose. The file in the drawable/ directory was getting scaled up too much to be used on the Galaxy Nexus, so it was complaining “Bitmap too large to be uploaded into a texture”. "Android assumes drawables without a density qualifier are mdpi and scales them up or down for other densities, in this case scaled up 2x for xhdpi." [1] So when the image was already an xxhdpi image, scaling it up by 2x or 3x caused OpenGL to run out of memory and abort. Fixed this by putting the resources into drawable-nodpi, which means Android will not scale them. I wonder if this means we run into other memory problems where we scale images from drawable/ up? [1] http://stackoverflow.com/a/14877627/582004
Comment on attachment 8675979 [details] MozReview Request: Bug 1207404 - First run image is too small. r=sebastian Bug 1207404 - First run image is too small. r=sebastian
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 44
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: