Installation strange display problem

359 views
Skip to first unread message

Lucio Tamburini

unread,
Apr 17, 2019, 2:48:14 PM4/17/19
to Android-x86
Hi all, I'm trying to install Android X-86 on my notebook but I have some trouble.

GRUB menù (all ok):

grub.jpg



x-86 live version (shell unreadable, Android Environment OK):

android.jpg



x-86 installation, stuck in the installation process (everythings is unreadable, vertical orientation, everything seems to be multiplicated and splitted):

stuck.jpg



Android X86 version 8.1-r1
Notebook/Tablet (detachable keyboard + touchscreen) Lenovo model 80SG
Screen native resolution 1280x800


Some help? How to start the installation in some "safe creen mode" so I can perform it?
(I have already search in the FAQ of android-x86.org and in google... nothing, you are my last chanche)
Thank in advance... :-)

Chih-Wei Huang

unread,
Apr 17, 2019, 11:34:07 PM4/17/19
to Android-x86
In the boot menu, try "Advanced options" -> "No Hardware Acceleration".
But it's strange why it works in live mode...


Lucio Tamburini <lucio.t...@gmail.com> 於 2019年4月18日 週四 上午2:48寫道:
>
> Hi all, I'm trying to install Android X-86 on my notebook but I have some trouble.
>
> GRUB menù (all ok):
>
>
>
> x-86 live version (shell unreadable, Android Environment OK):
>
>
>
> x-86 installation, stuck in the installation process (everythings is unreadable, vertical orientation, everything seems to be multiplicated and splitted):
>
>
>
> Android X86 version 8.1-r1
> Notebook/Tablet (detachable keyboard + touchscreen) Lenovo model 80SG
> Screen native resolution 1280x800
>
>
> Some help? How to start the installation in some "safe creen mode" so I can perform it?
> (I have already search in the FAQ of android-x86.org and in google... nothing, you are my last chanche)
> Thank in advance... :-)




--
Chih-Wei
Android-x86 project
http://www.android-x86.org

Lucio Tamburini

unread,
Apr 18, 2019, 6:44:56 AM4/18/19
to Android-x86
Tryed the "no hardware acceleration" but non solution:

(shell ambient)

1.jpg




(Android OS environment. Note the rectangular box -I have pushed the power button-)

2.jpg




So:
- "live": shell unreadable / AndroidOS no problem
- "no hardware acceleration": shell unreadable / androidOS unreadable
- "installation" and "automatic installation to hard disk": shell unreadable (unable to choose option and continue)

If the logic is correct, the problem must be in the hardware acceleration of my device. The androidOS use it and have no problem, the shell *do not use it* and the screen is unreadable.
There is any solution to force the hardware acceleration also in the shell part?

Thanks...

Chih-Wei Huang

unread,
Apr 18, 2019, 6:52:01 AM4/18/19
to Android-x86
Not understand what you meant the "shell".

You should collect dmesg & logcat for both
normal (live) and abnormal cases for analysis.

Lucio Tamburini <lucio.t...@gmail.com> 於 2019年4月18日 週四 下午6:45寫道:
>
> Tryed the "no hardware acceleration" but non solution:
>
> (shell ambient)
>
> (Android OS environment. Note the rectangular box -I have pushed the power button-)
>
> So:
> - "live": shell unreadable / AndroidOS no problem
> - "no hardware acceleration": shell unreadable / androidOS unreadable
> - "installation" and "automatic installation to hard disk": shell unreadable (unable to choose option and continue)
>
> If the logic is correct, the problem must be in the hardware acceleration of my device. The androidOS use it and have no problem, the shell *do not use it* and the screen is unreadable.
> There is any solution to force the hardware acceleration also in the shell part?
>
> Thanks...
>
>
>

Lucio Tamburini

unread,
Apr 18, 2019, 6:58:59 AM4/18/19
to Android-x86
Sorry, I mean the first part when the OS is loading, before the "graphic part".
The "command prompt", "black background + white text"... what's the correct name?

Can you explain me how to collect dmesg & logcat? Need to edit the option in GRUB?

4TechGuns

unread,
Apr 19, 2019, 5:58:31 AM4/19/19
to Android-x86
Press Alt+F1/2/3 to get to the shell and type dmesg/logcat. It has to be booted in order to run these commands.
Reply all
Reply to author
Forward
0 new messages