Hello,
I installed Remix OS on my Samsung Tablet PC (Intel Core i5). This tablet is placed on a support and the display is copied on an external display via HDMI. It works well with Windows 10, when I remove the shelf support, I can continue to work in touch mode where I was.
With Remix OS, in beta, it does not work. The screen is copied but low resolution and too little on my 24 "screen.
Do you think it will work with the final version of Remix OS?
I only got my second screen working but it's picture is a bit offset, still haven't got the dual screen thing fixed.
After editing the menu.lst , I can choose to start on the screen of the tablet or on the external display 24 " .
Stegue said:
After editing the menu.lst , I can choose to start on the screen of the tablet or on the external display 24 " .
Click to expand...
Click to collapse
What exactly did you change in the menu.lst
And how did you do it?
With Windows , replace the code with it in menu.lst adapting to his version of Remix OS , 32 or 64 bit.
default 0
timeout 10
title Boot to screen tablet
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64
androidboot.selinux=permissive quiet SRC=RemixOS/ DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
title Boot to External Monitor
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86_64
androidboot.selinux=permissive quiet SRC=RemixOS/ DATA= CREATE_DATA_IMG=1 video=LVDS-1:d
initrd /RemixOS/initrd.img
boot
Click to expand...
Click to collapse
Stegue said:
With Windows , replace the code with it in menu.lst adapting to his version of Remix OS , 32 or 64 bit.
Click to expand...
Click to collapse
So I can just copy and paste this code into the menu.lst file and I'm good to go?
Related
Thanks to @imadlatch for making tool
original Thread Here : http://forum.xda-developers.com/remix/remix-os/rmxtools-remix-os-data-img-t3308158
Root Remix OS Beta Version with Windows
Video Tutorial : https://www.youtube.com/watch?v=8usNNalReOk
Remix OS Root Method with windows For 2.0 or Below Version
Video Tutorial : https://www.youtube.com/watch?v=JV6vZqGQ4sE
For Downloading RMX Tool v1.5 Download Here : Owner Link | External Link | Initrd64 | Initrd32
Remix OS Root Method with windows For 2.0.101 and Above Version
Video tutorial : https://www.youtube.com/watch?v=IFGzmc81ta0
kabeerkhan2016 said:
Thanks to @imadlatch for making tool
original Thread Here : http://forum.xda-developers.com/remix/remix-os/rmxtools-remix-os-data-img-t3308158
Remix OS Root Method with windows For 2.0 or Below Version
Video Tutorial : https://www.youtube.com/watch?v=JV6vZqGQ4sE
For Downloading RMX Tool Visit Here : http://forum.xda-developers.com/remix/remix-os/rmxtools-remix-os-data-img-t3308158
Remix OS Root Method with windows For 2.0.101 and Above Version
Video tutorial : https://www.youtube.com/watch?v=IFGzmc81ta0
Click to expand...
Click to collapse
updated 10-Feb-2016
Good.
kabeerkhan2016 said:
updated 10-Feb-2016
Click to expand...
Click to collapse
What about Remix OS 32 Dualboot. GRUB Code ?
Shanmukarajan said:
What about Remix OS 32 Dualboot. GRUB Code ?
Click to expand...
Click to collapse
I'm not try this code, but i hope it's work. code below :- (Change (hd0,4) 0 with your hard disk number and 4 with your partition number )
Code:
default=0
timeout=6
title Guest Mode
root (hd0,4)
kernel /kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SRC= DATA= DATA_IN_MEM=1
initrd /initrd.img
title Resident Mode
root (hd0,4)
kernel /kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SRC= DATA= CREATE_DATA_IMG=1
initrd /initrd.img
Its working for Remix 32 bit but for android x86
kabeerkhan2016 said:
updated 10-Feb-2016
Click to expand...
Click to collapse
I want to know GRUB code for Android x86 OS for PC dualboot.
and also its not saving any data in PC like RESIDENT MODE in REMIX OS& PHOENIX OS.
Does we want to create data.img file to save the data else is there any tweaks to do..
Waiting for the reply..
Thanks in advance.
kabeerkhan2016 said:
I'm not try this code, but i hope it's work. code below :- (Change (hd0,4) 0 with your hard disk number and 4 with your partition number )
Code:
default=0
timeout=6
title Guest Mode
root (hd0,4)
kernel /kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SRC= DATA= DATA_IN_MEM=1
initrd /initrd.img
title Resident Mode
root (hd0,4)
kernel /kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SRC= DATA= CREATE_DATA_IMG=1
initrd /initrd.img
Click to expand...
Click to collapse
Thanks Kabeerkhan. I already found the GRUB Code for Android X86 from YouTube Video.
https://www.youtube.com/watch?v=P9bjWlf0Rtw
kabeerkhan2016 said:
Thanks to @imadlatch for making tool
original Thread Here : http://forum.xda-developers.com/remix/remix-os/rmxtools-remix-os-data-img-t3308158
Root Remix OS Beta Version with Windows
Video Tutorial : https://www.youtube.com/watch?v=8usNNalReOk
Remix OS Root Method with windows For 2.0 or Below Version
Video Tutorial : https://www.youtube.com/watch?v=JV6vZqGQ4sE
For Downloading RMX Tool v1.5 Download Here : Owner Link | External Link
Remix OS Root Method with windows For 2.0.101 and Above Version
Video tutorial : https://www.youtube.com/watch?v=IFGzmc81ta0
Click to expand...
Click to collapse
Update 6-March-2016
I have partitioned my USB flash once to be a data drive and one with the OS. When I open the Flash in a file manager it only recognises the partition with data not the OS so i am unable to replace the. IMG
Any way I can fix this?
Hi need a guide for Version 3.0.207 please as RMXtools v1.8 Fix look not like anything in your video.
Shan I watched your YouTube video on how to install Android on PC without usb. Gone smoothly until found that all files in the zip are encrypted. I can't understand why you locked those supportive files if you want people to use your method. Still managed to write from video, Android got stuck at
A N D R O I D [email protected]: and after some time it reboots back to windows.
My system info:-
Os windows 8 pro build 9200
Ram 2gb
Architecture x64
Bios mode legacy
Installed on exfat partitipn
Hello,
Whenever I minimize or close an application in Remix OS. The whole OS restarts from the splash screen (RemixOS for PC) and backs to desktop and all application closed?
Any idea to fix this?
Thank You in advance.
mine does this to I am searching for a fix no luck yet if anyone has a solution please post.
Perhaps...give more info
What version number?
32bit or 64bit?
Hardware used?
Debug log perhaps..
Cheers
mitchell4you said:
Perhaps...give more info
What version number?
32bit or 64bit?
Hardware used?
Debug log perhaps..
Cheers
Click to expand...
Click to collapse
i am running 32 bit version with the video card i have it set like this on boot
default 0
timeout 10
title Resident mode - All your data and apps are saved
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 nomodeset vga=318 1024x768x32 DPI=120 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
here are the specs for the pc
CPU
AMD Athlon 64 X2 3800+ 46 °C
Windsor 90nm Technology
RAM
2.00GB Dual-Channel DDR2 (5-5-5-18)
Motherboard
ELITEGROUP MCP61PM-AM (Socket AM2 ) 40 °C
Graphics
W2040 ([email protected])
128MB NVIDIA GeForce 6150SE nForce 430 (Elitegroup)
Storage
149GB Western Digital WDC WD16 00AAJS-00PSA SCSI Disk Device (SATA) 38 °C
give me a little bit of time for the logs if i can get it to stay up long enough i will get the logs, i am trying to get a log right before it crashes but i don't know what to use to get that log.
Hello guys,
I have bought a Lenovo Yoga Tablet 2 10" and installed Remix OS 32-bit through provided tool. Unfortunately, I have Bluetooth keyboard which doesn't work before full system loading, therefore I can't choose Remix OS on boot screen.
Installation of Remix OS also created the second "Windows Bootloader" entry in EFI Boot from menu (which is operable by touch). When I choose the first Win Bootloader, it throws me directly to Windows 10 loading screen without displaying the boot choice between Windows 10 and Remix OS (which is present on second Win Bootloader option).
So I've got an idea to edit the boot file of Remix OS to boot directly without asking me, whether I want to load Remix or Windows. Therefore I will be able to boot Remix without keyboard when choosing second bootloader, and Windows when choosing the first one.
When I used the live version of Remix OS, I edited grub.cfg to load system directly without waiting for confirmation from keyboard:
set timeout=0
set gfxmode=1024x768
terminal_output gfxterm
menuentry 'Guest mode - No data will be saved after each session' --class android-x86 {
search --file --no-floppy --set=root /kernel
linuxefi /kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet DATA= DATA_IN_MEM=1
initrdefi /initrd.img
}
Is this also possible on installed version of Remix OS? I have tried to edit grub.cfg located in D:/RemixOS/efi/boot to match the code above, but after restart I was greeted with choice screen (so it didn't work).
Thank you in advance for any replies!
Cleo1 said:
Hello guys,
I have bought a Lenovo Yoga Tablet 2 10" and installed Remix OS 32-bit through provided tool. Unfortunately, I have Bluetooth keyboard which doesn't work before full system loading, therefore I can't choose Remix OS on boot screen.
Installation of Remix OS also created the second "Windows Bootloader" entry in EFI Boot from menu (which is operable by touch). When I choose the first Win Bootloader, it throws me directly to Windows 10 loading screen without displaying the boot choice between Windows 10 and Remix OS (which is present on second Win Bootloader option).
So I've got an idea to edit the boot file of Remix OS to boot directly without asking me, whether I want to load Remix or Windows. Therefore I will be able to boot Remix without keyboard when choosing second bootloader, and Windows when choosing the first one.
When I used the live version of Remix OS, I edited grub.cfg to load system directly without waiting for confirmation from keyboard:
set timeout=0
set gfxmode=1024x768
terminal_output gfxterm
menuentry 'Guest mode - No data will be saved after each session' --class android-x86 {
search --file --no-floppy --set=root /kernel
linuxefi /kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet DATA= DATA_IN_MEM=1
initrdefi /initrd.img
}
Is this also possible on installed version of Remix OS? I have tried to edit grub.cfg located in D:/RemixOS/efi/boot to match the code above, but after restart I was greeted with choice screen (so it didn't work).
Thank you in advance for any replies!
Click to expand...
Click to collapse
Hi Cleo ....
Did you ever figure out how to do this, ? cause I would like to do the same boot straight into remix without a dual boot option...
First of all , Hi im dew and this is my first post :laugh:
this is from my personal experiance, I reinstall my windows and i got Error 15 file not found remix os & 0x00000f \ubnldr.mbr Problem, Im too lazy to reinstall the remix os, soo yeah , and finally i found out how to fix it (Might Not Work For Everyone but try it!)
ALL YOU NEED IS:
1. Easybcd (i dont have the link, sorry)
Step by step:
1.Open Easybcd
2.click add new entry
3.click neogrub bar
4.and hit instal (if you already did this you can skip this)
5.after that hit configure
6.delete the previous text and copy this text :
PHP:
default 0
timeout 10
title Resident mode - All your data and apps are saved
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet SRC=RemixOS/ DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
title Verbose Mode - Save log files for debugging
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet SRC=RemixOS/ DATA= CREATE_DATA_IMG=1 SAVE_LOGS=1
initrd /RemixOS/initrd.img
boot[/COLOR][/COLOR]
7.hit save on notepad
8.and back to easybcd
9.click edit boot menu
10.and change the name to Remix OS ( if you see another Remix OS name there , you better delete it first)
11.restart
(Might Not Work For Everyone but Worth to try.)
and yeah, Lets be friend after this :v
I am trying to install Android on a Lenovo Yoga 9i with an i7 10th generation processor which dual boots Win 11 and Kubuntu 22.04. I have been able to install PrimeOS, Android-x86 and BlissOS to the kubuntu root using the following isos – PrimeOS-2.1.3-64-bit-20220719-BETA.iso -- android_x86_64-a12.1_r1-03.16.22-01-mesa22-ksu-gapps-libndk-sd.iso and
BlissOS-14.3-x86_64-202106261907_k-android12-5.10.46-ax86_m-21.1.3_r-x86_emugapps_cros-hd.iso manually for linux where I copy the kernel, initrd and system files to the appropriate folder. I create a data folder rather than a data.img file as this is marginally more flexible for my use. I use the following 40_custom grub file to allow me to start the different OS.
menuentry "BlissOS" { set SOURCE_NAME="dev/nvme0n1p8/blissos" search --set=root --file /$SOURCE_NAME/kernel
linux /$SOURCE_NAME/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86_64 androidboot.selinux=permissive set gfxpayload=keep nouveau.modeset=0 i1017.modeset=1 acpi_sleep=s3_bios,s3_mode SDCARD=dev/nvme0n1p6 SRC=/$SOURCE_NAME
initrd /$SOURCE_NAME/initrd.img}
menuentry "Primeos" { set SOURCE_NAME="primeos" search --set=root --file /$SOURCE_NAME/kernel
linux /$SOURCE_NAME/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86_64 SDCARD=dev/nvme0n1p6 androidboot.selinux=permissive set gfxpayload=keep nouveau.modeset=0 i1017.modeset=1 acpi_sleep=s3_bios,s3_mode SRC=/$SOURCE_NAME
initrd /$SOURCE_NAME/initrd.img}
menuentry "Android" { set SOURCE_NAME="android-x86" search --set=root --file /$SOURCE_NAME/kernel
linux /$SOURCE_NAME/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86_64 androidboot.selinux=permissive SDCARD=dev/nvme0n1p6 set gfxpayload=keep nouveau.modeset=0 i1017.modeset=1 acpi_sleep=s3_bios,s3_mode SRC=/$SOURCE_NAME
initrd /$SOURCE_NAME/initrd.img}
I have three issues common to all three Oss which I have cannot solve.
1. I am unable to permanently set a lockscreen password or pin. I can enter a password or pin but the system immediately reverts to none saved.
2. Unlike with earlier versions of Android-x86 (used on a Sony Vaio with touch and a lenovo yoga 3-11) I am unable to set an NTFS data partition as the external SD card. I have tried to find advice as to how I should adapt SDCARD=dev/nvme0n1p6 as it does not seem to work. Strangly PrimeOS mounts the Windows partition unasked.
3. Finally, I would like to run the BlissOS from a separate partition but it fails to find the partition with the kernel. I have tried using the UUID unsuccessfully.
/dev/nvme0n1p8: LABEL="blissos" UUID="69d92f25-8e97-46b8-b0d4-675106fafc60" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="blissos" PARTU
UID="72a75f11-668e-bb48-8c14-6dce6e9ed391"
I have a minor problem with the Android-x86 iso in that it loads an initial screen with bright white lines in the lower part of the screen although I can get past this.
divotee said:
I am trying to install Android on a Lenovo Yoga 9i with an i7 10th generation processor which dual boots Win 11 and Kubuntu 22.04. I have been able to install PrimeOS, Android-x86 and BlissOS to the kubuntu root using the following isos – PrimeOS-2.1.3-64-bit-20220719-BETA.iso -- android_x86_64-a12.1_r1-03.16.22-01-mesa22-ksu-gapps-libndk-sd.iso and
BlissOS-14.3-x86_64-202106261907_k-android12-5.10.46-ax86_m-21.1.3_r-x86_emugapps_cros-hd.iso manually for linux where I copy the kernel, initrd and system files to the appropriate folder. I create a data folder rather than a data.img file as this is marginally more flexible for my use. I use the following 40_custom grub file to allow me to start the different OS.
menuentry "BlissOS" { set SOURCE_NAME="dev/nvme0n1p8/blissos" search --set=root --file /$SOURCE_NAME/kernel
linux /$SOURCE_NAME/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86_64 androidboot.selinux=permissive set gfxpayload=keep nouveau.modeset=0 i1017.modeset=1 acpi_sleep=s3_bios,s3_mode SDCARD=dev/nvme0n1p6 SRC=/$SOURCE_NAME
initrd /$SOURCE_NAME/initrd.img}
menuentry "Primeos" { set SOURCE_NAME="primeos" search --set=root --file /$SOURCE_NAME/kernel
linux /$SOURCE_NAME/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86_64 SDCARD=dev/nvme0n1p6 androidboot.selinux=permissive set gfxpayload=keep nouveau.modeset=0 i1017.modeset=1 acpi_sleep=s3_bios,s3_mode SRC=/$SOURCE_NAME
initrd /$SOURCE_NAME/initrd.img}
menuentry "Android" { set SOURCE_NAME="android-x86" search --set=root --file /$SOURCE_NAME/kernel
linux /$SOURCE_NAME/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86_64 androidboot.selinux=permissive SDCARD=dev/nvme0n1p6 set gfxpayload=keep nouveau.modeset=0 i1017.modeset=1 acpi_sleep=s3_bios,s3_mode SRC=/$SOURCE_NAME
initrd /$SOURCE_NAME/initrd.img}
I have three issues common to all three Oss which I have cannot solve.
Click to expand...
Click to collapse
As I have removed these three ROM and replaced them with the stable Pie based ROM, 11 which I have installed at root, I have happily got rid of 2 of my three problems as follows:-
divotee said:
1. I am unable to permanently set a lockscreen password or pin. I can enter a password or pin but the system immediately reverts to none saved.
Click to expand...
Click to collapse
I can now set a lockscreen
divotee said:
2. Unlike with earlier versions of Android-x86 (used on a Sony Vaio with touch and a lenovo yoga 3-11) I am unable to set an NTFS data partition as the external SD card. I have tried to find advice as to how I should adapt SDCARD=dev/nvme0n1p6 as it does not seem to work.
Click to expand...
Click to collapse
Still a problem . Trying to mount using termux - get 'device not found ' after making a directory as /mnt/newvol.
divotee said:
3. Finally, I would like to run the BlissOS from a separate partition but it fails to find the partition with the kernel. I have tried using the UUID unsuccessfully.
Click to expand...
Click to collapse
Given up trying to do this
divotee said:
/dev/nvme0n1p8: LABEL="blissos" UUID="69d92f25-8e97-46b8-b0d4-675106fafc60" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="blissos" PARTU
UID="72a75f11-668e-bb48-8c14-6dce6e9ed391"
I have a minor problem with the Android-x86 iso in that it loads an initial screen with bright white lines in the lower part of the screen although I can get past this.
Click to expand...
Click to collapse
No longer relevant as I have removed the ROM