Linux - MobileThis forum is for the discussion of all topics relating to Mobile Linux. This includes Android, Tizen, Sailfish OS, Replicant, Ubuntu Touch, webOS, and other similar projects and products.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm trying to use GRUB2 to boot Android-x86. The following menu entry works fine on a ThinkPad 20FR but not 20UB (which just boots to Android command-line).
Code:
menuentry "Android" --class android-x86 {
savedefault
set root='(hd0,msdos5)'
linux /android-9.0-r2/kernel quiet root=/dev/ram0
initrd /android-9.0-r2/initrd.img
}
I would use the UUID of the partition rather than relying on BIOS generated names.
I'm only guessing, but i'd say that android probably couldn't find it's root partition during the boot process on the 20UB.
Screenshots (even off your phone) are very helpful for diagnostics.
I would use the UUID of the partition rather than relying on BIOS generated names.
I didn't use a BIOS generated name; I used the name of the partition I installed Android on, which has identical configuration/partitioning scheme to the similar/variant device (ThinkPad 20FR) Android works on.
Quote:
I'm only guessing, but i'd say that android probably couldn't find it's root partition during the boot process on the 20UB.
Screenshots (even off your phone) are very helpful for diagnostics.
You didn't really read, did you? It already boots to this partition on the ThinkPad 20UB laptop (what I said it is) but just boots to Android command-line/shell (it's not a rescue shell but bash or something).
Well without screenshots or error messages, your post leaves a lot of room for interpretation.
Perhaps you could post some more useful information rather than attacking the person trying to help?
I wasn't attacking, just pointing out you missed a couple things including that it's a laptop. I don't know of a way to take a screenshot in Android shell and there is no error message. It just says the following.
Code:
Detecting Android-x86... found at /dev/nvme0n1p5
console:/ #
The command ls shows files/directories/folders with 'android' in them and I can also su, so as originally said, Android does actually boot, just doesn't start GUI. Where would I get an error message about that?
As in the Stack Overflow answer, I added 'nomodeset xforcevesa' after linux in /etc/grub.d/40_custom, and regenerated /boot/grub/grub.cfg but this didn't change anything... that was for Android 8.1 but I have 9.0 (latest on Android-x86.org last time I checked).
I couldn't create a log because Android-x86 started read-only, and I couldn't find out how to mount a USB flash drive to write to instead (dmesg, /dev, lsusb being different, and there's no lsscsi).
Here's the Android-x86 log though I'm not expecting anyone to look through much of this because it's almost half a megabyte, so unless you know exactly what things to search for, I don't want to waste a lot of people's time. I still have the older ThinkPad I can use if I really want to use Android. I wish I could report this to Lenovo but they'd probably just say they don't 'support' Android...
I can see from the log that patchoat is failing to load, this is what brings up your ART (android runtime).
it seems to be attempting to load an address that is not available on the newer machine.
have you tried a fresh install on the newer machine? IIRC android can be a bit funny about changing hardware since it's designed for phones & tablets
On a deeper reading of the log, your android install is referring to it's internal config files to locate hardware that was configured at install time.
This is not being found since it's booting on fundamentally different hardware.
I think without significant re-writing of configuration files, you'll have a lot of trouble running the same installation on multiple devices.
I suggest having individual installations per hardware configuration.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.