2017-01-28 16:52 GMT+08:00 Terence Wu <
jiaye...@gmail.com>:
>
> Thank you for your reply. But I would like to point out 2 problems.
>
> First, some tablets from several manufacturers can only boot from USB
> devices with winboot files, that means any non-Windows-based installation
> USB stick will not boot in those devices (my Lenovo MIIX310 is,
> unfortunately this kind of device). So the only way to install Android X86
> seems to use a Win32 Installer, which cannot recognize ext2/3/4 partitions
> due to Windows limitations (even with newer Windows 10 builds with Linux
> support). So in these cases, installing on FAT32/NTFS partitions is
> inevitable, and data.img is still very useful.
That's right.
On FAT32/NTFS partition you should use data.img.
(I've said that in another post)
> Second, previous builds like 6.0 r1 and CM13 rc1 have already supported BOTH
> data.img and "data" subdirectory. With the same grub.cfg using
> "DATA=/AndroidOS", if a data.img file exists in C:\AndroidOS, it will use
> the img directly; otherwise it will create a "data" subdirectory instead.
> That means subdirectory is already supported. I see no necessity to design
> the "new feature" (what I took as a bug lol) for the old one is good enough,
> and, better.
"DATA=/AndroidOS" is a wrong syntax (and no effect) before (include) 6.0-r1.
In 6.0-r2, it means the data subdirectory is "AndroidOS".
The feature allows the users to specify the data subdirectory if they want.
If you want to use data.img as before, you have to remove "DATA=/AndroidOS"
from your cmdline as I have explained.
> Based on my consideration in the First point, and the fact that many people
> don't want to mess up with their partitions or file systems, I suggest the
> old way to deal with data maybe better - or if I misunderstood something
> here- or is there a method to use data.img again - or if you would like to
> introduce another way to install in such devices (mostly cherry-trail
> devices), please let me know.
The "old way" is always supported, of course.
Indeed I think you misunderstood (misuse) the meaning of DATA=.
If you want to say "my android-x86 installation dir is /AndroidOS",
it should be "SRC=/AndroidOS" instead of "DATA=/AndroidOS".
> I can offer assistance if you want further testing on this kind of devices.
>
> BTW, now only 6.0r1 and RemixOS 3.0(touch support has dropped?) works on
> MIIX310 (r2 cannot), with rotation wrong, battery un-detected and WLAN
> unusable. I assumed that a newer kernel for Cherry-trail support is needed?
Please open another thread for such a question.
List what versions you have tested and what peripherals work or not,
with dmesg and lsmod attached.
Usually a newer kernel is better.
But sometimes you may encounter some regressions.
(something works in an older kernel but breaks in a newer kernel)
In this case you should report it carefully with details as possible.