WAI
Status Update
No update yet.
Comments
zy...@google.com
zy...@google.com
We use build flavours heavily with a lot of common code. The refactoring support in AS is really good but it continually catches us out when it doesn't work across all flavours in a project. It's a big gap for serious product development.
sc...@gmail.com
We at my company need this same feature. We have a lot of white labels and need refactor the same class across flavours. :(
zy...@google.com
I need this feature too...
zy...@google.com
+1, I need this very badly
sc...@gmail.com
+1 My company also need this feature.
zy...@google.com
Can we atleast know the status of the issue please? Will it be fixed or is it in low priority. It's been 4 years.
sc...@gmail.com
We are currently investigating possibly solutions.
zy...@google.com
+1 This will exclude a lot of unnecessary work. In my work I have 25 flavours. :(
we...@gmail.com
+1 .. we need it as well...
we...@gmail.com
Any update on this?
Description
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 26.1.2
HAXM / KVM Version: unknown
Android SDK Tools: 26.0.2
Host Operating System: Ubuntu 16.04
CPU Manufacturer: [Intel / AMD / Other] Intel
When using emulator 26.1.2, it seems to use the wrong "disk.dataPartition.size" value of 512m rather than the value specified in the avd's config.ini: 1024MB.
When the emulator starts, it outputs:
Content of hardware configuration file:
[...]
disk.dataPartition.size = 512m
whereas the config.ini specifies
disk.dataPartition.size=1024M
The full emulator stdout is attached (emu.out-26.1.2), as well as the full config.ini file.
I've also attached the emulator stdout from an older emulator version (25.1.7) using the same avd, where it uses the correct data partition size value: "disk.dataPartition.size = 1g" - see emu.out-25.1.7
The logs here are from an API 17 x86 avd, using system image revision 2 (yes, I know it's old, but we use old/stable AVDs for running automated regression testing against old systems), but this same data-partition-size behavior also occurs with a newly created API 26 Google Apis avd.
Note: when testing with the API 26 emulator, the userdata.img file created by AS is 550M. If I run `resize2fs userdata.img 1G` before launching that emulator, it correctly determines "disk.dataPartition.size = 1g" when booting and `df` reports the /data partition is the correct size. However, this workaround doesn't work for the older API 17 userdata.img file (it's only ~4MB and attempting resize2fs on it fails).