08-05-2016, 08:50 AM
(This post was last modified: 08-05-2016, 08:53 AM by MarkHaysHarris777.)
hi Montero65,
On the gnu+linux images that we control we are doing precisely as you suggest, now. In fact the gnu+linux images must be expanded in order to take full advantage of the space available on the full SD card.
The problem arises with the images that we do not control.
I will pass this on to the developers in our own think tank, and see what we can do to influence the people who are building the proprietary images for Android &c. If I controlled it this would be fixed this afternoon. If TL Lim controlled it, it would have been fixed weeks ago.
The most important thing to do is to make sure that your SD card really has the capacity that it is supposed to have. There are several on-line tests for this purpose. If you have a bad or fraudulent card (maybe even a fake) there is no amount of programming that will fix that.
Another thing we can do is have a builld and test group of volunteers who will verify that each image will actually work with X number of SD card vendors and size. This is not fully in place, and we are going to have to discuss it some more. In the mean time, the best i can suggest atm is to purchase quality cards which are having the capacity they advertise.
NOTE: The 'K' problem is universal. Please don't shoot the messenger. developers *all* use K=1024... SD card vendors all ALL use K=1000. This is clearly an error, but none of use who are developers are going to start using K=1000 !! (NOT GOING TO HAPPEN) The reason of course is that K is about binary, not about decimal; and the even binary number closest to 1000 is 1024.... so, what's the 16Gb equivalent of this idea... ?
17,179,869,184
Do you see the problem ? By the place value that we are talking about billions of bytes (16 Billion bytes) is actually well over seventeen billion bytes !!
The manufacture of these cards is in the hands of engineers who have NDAs and contracts with multiple Corporations... and our hands are tied. Its not so simple as tell someone to make the image smaller... we get the image the way its given to us... this problem can be pushed back a bit... but it is going to take some time, politics, understanding, and patience.
On the gnu+linux images that we control we are doing precisely as you suggest, now. In fact the gnu+linux images must be expanded in order to take full advantage of the space available on the full SD card.
The problem arises with the images that we do not control.
I will pass this on to the developers in our own think tank, and see what we can do to influence the people who are building the proprietary images for Android &c. If I controlled it this would be fixed this afternoon. If TL Lim controlled it, it would have been fixed weeks ago.
The most important thing to do is to make sure that your SD card really has the capacity that it is supposed to have. There are several on-line tests for this purpose. If you have a bad or fraudulent card (maybe even a fake) there is no amount of programming that will fix that.
Another thing we can do is have a builld and test group of volunteers who will verify that each image will actually work with X number of SD card vendors and size. This is not fully in place, and we are going to have to discuss it some more. In the mean time, the best i can suggest atm is to purchase quality cards which are having the capacity they advertise.
NOTE: The 'K' problem is universal. Please don't shoot the messenger. developers *all* use K=1024... SD card vendors all ALL use K=1000. This is clearly an error, but none of use who are developers are going to start using K=1000 !! (NOT GOING TO HAPPEN) The reason of course is that K is about binary, not about decimal; and the even binary number closest to 1000 is 1024.... so, what's the 16Gb equivalent of this idea... ?
17,179,869,184
Do you see the problem ? By the place value that we are talking about billions of bytes (16 Billion bytes) is actually well over seventeen billion bytes !!
The manufacture of these cards is in the hands of engineers who have NDAs and contracts with multiple Corporations... and our hands are tied. Its not so simple as tell someone to make the image smaller... we get the image the way its given to us... this problem can be pushed back a bit... but it is going to take some time, politics, understanding, and patience.
marcushh777 
please join us for a chat @ irc.pine64.xyz:6667 or ssl irc.pine64.xyz:6697
( I regret that I am not able to respond to personal messages; let's meet on irc! )
please join us for a chat @ irc.pine64.xyz:6667 or ssl irc.pine64.xyz:6697
( I regret that I am not able to respond to personal messages; let's meet on irc! )