Hello All,
Not sure if this is the right forum to raise this issue we observed. If not please redirect me to the right place.
Problem observed::
With Juno release we have the option for creating a media device from the juno.img.bz2 or from the 3 tar balls provided for the android image.
When I try to create the image from juno.img.bz2 and try to install a 'huge' benchmark apk like GFXBench3.0 (100+MB size apk and uses larger space on disk while execution too) it fails with disk space not sufficient error.
Even if I use a 16GB usb device I hit this problem.
Some interesting details::
Please see the attached screen shots. The first one is where I have the got the 16GB media formatted.
When I use linaro-android-media-create then can see sdcard partition extending the remaining of the space on the disk.
But if you look at the dd'ing 2.1GB juno image I can see 14GB shown as 'Unallocated.
Please note that if I use linaro-android-media-create I never hit this problem of lack of space when GFXBench3.0
Any clue?
Is this a bug?
Is there a way juno.img can be made to 'have larger space'?
Thanks Basil Eljuse...
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
Hi all,
I would like to add that even with linaro-android-media-create, even though the partitions are set up differently, the free 14GB is still not visible to Android. The system shows ~500MB of internal memory.
Thanks,
Varun
From: Basil Eljuse Sent: 08 August 2014 13:47 To: Linaro Validation Cc: Jon Medhurst (Tixy); ryan.harkin@linaro.org; Manik Bajpai; Dean Arnold; Varun Sarwal Subject: Observed diff between how dd'ing juno.img and using linaro-android-media-create...
Hello All,
Not sure if this is the right forum to raise this issue we observed. If not please redirect me to the right place.
Problem observed::
With Juno release we have the option for creating a media device from the juno.img.bz2 or from the 3 tar balls provided for the android image.
When I try to create the image from juno.img.bz2 and try to install a 'huge' benchmark apk like GFXBench3.0 (100+MB size apk and uses larger space on disk while execution too) it fails with disk space not sufficient error.
Even if I use a 16GB usb device I hit this problem.
Some interesting details::
Please see the attached screen shots. The first one is where I have the got the 16GB media formatted.
When I use linaro-android-media-create then can see sdcard partition extending the remaining of the space on the disk.
But if you look at the dd'ing 2.1GB juno image I can see 14GB shown as 'Unallocated.
Please note that if I use linaro-android-media-create I never hit this problem of lack of space when GFXBench3.0
Any clue?
Is this a bug?
Is there a way juno.img can be made to 'have larger space'?
Thanks
Basil Eljuse...
On Fri, 2014-08-08 at 13:47 +0100, Basil Eljuse wrote:
Hello All,
Not sure if this is the right forum to raise this issue we observed. If not please redirect me to the right place.
Problem observed::
With Juno release we have the option for creating a media device from the juno.img.bz2 or from the 3 tar balls provided for the android image.
When I try to create the image from juno.img.bz2 and try to install a 'huge' benchmark apk like GFXBench3.0 (100+MB size apk and uses larger space on disk while execution too) it fails with disk space not sufficient error.
Even if I use a 16GB usb device I hit this problem.
Some interesting details::
Please see the attached screen shots. The first one is where I have the got the 16GB media formatted.
When I use linaro-android-media-create then can see sdcard partition extending the remaining of the space on the disk.
But if you look at the dd'ing 2.1GB juno image I can see 14GB shown as 'Unallocated.
Please note that if I use linaro-android-media-create I never hit this problem of lack of space when GFXBench3.0
Any clue?
The pre-built image is a raw disk image and so includes a partition table for a particular size of disk, in this case 2GB. If we created an image for say a 16GB disk, then it wouldn't work on any media smaller than that. Note, the current 2GB disk size for vexpress family images is so they work on FVPs which have a 2GB limit for things like sdcard emulation. (And also means people using models don't end up with lots of wasted disk space on their PC's taken up by mostly empty disk images).
Is this a bug?
No :-)
Is there a way juno.img can be made to 'have larger space'?
I guess so for Juno Android images, they don't currently work on models and so could be bigger. For ARMv8 OpenEmbedded and all 32-bit images, the same filesystems also works on models, so that would be a consideration in not increasing the size. (And in future you could imagine Juno Android images also becoming a generic vexpress image that worked on FVP Base models).
But basically, if you want bigger partitions, I would just say use linaro-android-media-create (l-a-m-c), and if you specifically want a raw disk image to test, use l-a-m-c to create one (using the --image-file --image-size options instead of '--mmc /dev/sdX').
linaro-validation@lists.linaro.org
-
Basil Eljuse -
Jon Medhurst (Tixy) -
Varun Sarwal