Closed
Bug 792151
(moreapks)
Opened 12 years ago
Closed 2 years ago
Build and deploy multiple APKs tailored for different screen sizes and device capabilities
Categories
(Firefox Build System :: Android Studio and Gradle Integration, enhancement, P5)
Firefox Build System
Android Studio and Gradle Integration
All
Android
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: kats, Unassigned)
References
Details
ARMv6 devices generally are lower-end devices with smaller screens. It may be possible to exclude big-screen UI assets from the ARMv6 .apk file entirely. It should also to have smaller/lower-resolution UI assets for the low-memory devices, which should reduce the memory requirement on the Java side.
Comment 2•12 years ago
|
||
Removing the tablet UI stuff seems an easy win.
Comment 3•12 years ago
|
||
What are all resolutions are supported by armv6 devices?
I believe shipping ldpi (needs to be created) and mdpi seems to be a safe bet. MDPI can stand up to HDPI (with pixellation), but won't crash the app.
Reporter | ||
Comment 4•12 years ago
|
||
(In reply to Kevin Brosnan [:kbrosnan] from comment #2)
> Removing the tablet UI stuff seems an easy win.
I don't know if we can do this across the board for the ARMv6 APK. There is at least one ARMv6 tablet out there: http://www.tinydeal.com/android-233-7-multi-touch-wifi-tablet-armv6512mb-hd-p-52309.html (with a screen resolution of 800x480)
Otherwise most ARMv6 phones I've seen are 320x480 or smaller.
Comment 5•12 years ago
|
||
If the tablet is not running honeycomb+, we don't need tablet resources, as we dont support tablet interface for anything that's not running honeycomb+.
Updated•12 years ago
|
Whiteboard: [ARMv6]
Comment 6•12 years ago
|
||
Wont-fix?
Reporter | ||
Comment 7•12 years ago
|
||
I'd like to leave this open for now. It's still a viable method for reducing resource usage.
Comment 8•11 years ago
|
||
I'd like to resurrect this bug. Can we get a mentor on it? Maybe we should just start with *not* bundling XHDPI and XXHDPI assets?
Updated•11 years ago
|
Summary: [ARMv6] Reduce UI assets for small-screen devices and/or low-memory devices → Reduce UI assets for small-screen devices and/or low-memory devices
Whiteboard: [ARMv6]
Comment 10•11 years ago
|
||
Comment 11•11 years ago
|
||
And more context:
http://developer.android.com/google/play/publishing/multiple-apks.html
Strictly speaking it's possible to publish different APKs for different screen sizes, as well as different architectures.
I don't think this is something we should plan on doing, but if we decide to get really aggressive with this -- e.g., if we start supplying large images for a new feature -- we could explore supplying multiple APKs with tailored resource sets.
Comment 12•10 years ago
|
||
We no longer support ARMv6. Bug 1039789 will split our APK between API9 (resource constrained) and "everything else".
Morphing this bug to be the evolution of that.
Component: General → Build Config & IDE Support
Summary: Reduce UI assets for small-screen devices and/or low-memory devices → Support multiple APKs tailored for different screen sizes and device capabilities
Comment 13•10 years ago
|
||
This is an extension of the work done in Bug 1039789. We should investigate what we get by building screen size dependent APKs.
Two broad thoughts:
1) I think the technical path to get here should be to push building with Gradle across the line (Bug 1119520); there's no sense rolling this support ourselves.
2) There are finnicky version code issues all over this. See Bug 1137586 and the discussion at http://tools.android.com/tech-docs/new-build-system/user-guide/apk-splits.
Alias: moreapks
Summary: Support multiple APKs tailored for different screen sizes and device capabilities → Build and deploy multiple APKs tailored for different screen sizes and device capabilities
Comment 14•10 years ago
|
||
Nick: perhaps file a new bug for this? The first ten comments are kinda misleading.
Comment 16•6 years ago
|
||
Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195
Needinfo :susheel if you think this bug should be re-triaged.
Priority: -- → P5
Updated•5 years ago
|
Product: Firefox for Android → Firefox Build System
Updated•2 years ago
|
Severity: normal → S3
Comment 17•2 years ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 3 duplicates.
:nalexander, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Flags: needinfo?(nalexander)
Updated•2 years ago
|
Severity: S3 → --
Type: defect → enhancement
Flags: needinfo?(nalexander)
Comment 18•2 years ago
|
||
We can close this: we don't produce APKs at all for GeckoView; any changes here would be over in Fenix-land.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•