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.
Related
I'm trying to install RemixOS on my old laptop:
Processor: AMD Athlon(tm) X2 Dual-Core QL-60 (2 CPUs), ~1.9GHz
Card name: ATI Radeon HD 3200 Graphics
Memory: 2048MB RAM
Click to expand...
Click to collapse
Booting with NeoGrub
title RemixOS root (hd0,4)
kernel /kernel root=/dev/ram0 DATA= CREATE_DATA_IMG=1 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive
initrd /initrd.img
Click to expand...
Click to collapse
also
root (hd0,4)
kernel /kernel root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive quiet SRC= DATA= DATA_IN_MEM=1
initrd /initrd.img
Click to expand...
Click to collapse
And screen stuck at this : imgur_com/GeOluot (sorry new member can't post link)
Freeing SMP alternatives memory: 24K
Click to expand...
Click to collapse
tungwoodboi said:
I'm trying to install RemixOS on my old laptop:
Booting with NeoGrub
And screen stuck at this : imgur_com/GeOluot (sorry new member can't post link)
Click to expand...
Click to collapse
Your Code is Wrong....
Original Code Link : https://cldup.com/zcR0lBzl_T.txt
Check This image : https://goo.gl/TyvC4T
Also Check Tutorial Dual Boot Remix os & window : https://www.youtube.com/watch?v=aYWY7NadNzU
I tried your code but result is the same.
stuck at "Booting the kernel"
s25.postimg_org/oofaxe4e7/tmp_25421_P_20160114_1049511044007729.jpg
tungwoodboi said:
I tried your code but result is the same.
stuck at "Booting the kernel"
s25.postimg_org/oofaxe4e7/tmp_25421_P_20160114_1049511044007729.jpg
Click to expand...
Click to collapse
watch video : https://www.youtube.com/watch?v=aYWY7NadNzU
and Format Your partition and again mount/extract iso and copy all file to your partition drive.
Then open easybcd click on add new entry > click on neogrub > click on remove, Then again click on install wait few second, click on configure and and paste this code : https://cldup.com/zcR0lBzl_T.txt (note change your partition number) and save the file...
Reboot again.....
I hope your problem solved !
Help material :-
Check Remix OS Partition Number By This Software : BOOTICE : http://bit.ly/1T8aXfb and check this image : https://goo.gl/DtEPL2 and also this https://goo.gl/TyvC4T
Note : Disable secure boot in Bios Setting
repeat exactly steps but no luck..
I think problem is my hardware not compatible with RemixOS
same issue here
Processor: AMD Athlon(tm) X2 Dual-Core QL-65 (2 CPUs), ~2.10 GHz
Card name: ATI Radeon HD 3200 Graphics
Memory: 2048MB RAM
blank screen on emachines e627, seems to be an issue with GPU, because screen goes blank after X starts...
CPU : AMD Athlon TF-20 (1.6GHz * 1)
GPU : ATI Radeon HD 3000
3GB RAM
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,
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?
I'm attempting to use rEFInd and my mac to boot to RemixOS (resident) on a USB. I have a thunderbolt display (Apple Cinema Display), and have managed to get it up and running with kernel parameter nomodeset (as I've had to do in the past with other distros). My Mac Pro has dual AMD GPUs, so I'm assuming RemixOS doesn't have AMD/ATI/Radeon support (drivers, etc). Here are the many options I get when booting. New user, so can't post links. Remove dots: h.t.t.p.s://streamable.c.o.m/wtbc8
My basic REMIXOSSYS/boot/grub/grub.cfg resident kernel boot parameters look normal:
menuentry 'Resident mode - All your data and apps are saved ' --class remixos --class android-x86 --class gnu-linux --class os {
search --file --no-floppy --set=root /kernel
linux /kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive nomodeset androidboot.swrast=1 quiet DATA= USB_DATA_PARTITION=1
initrd /initrd.img
}
This boots fine, doesn't detect my GPU and boots to the desktop environemnt, is very stable, but has a VERY low resolution and dpi, as KMS (kernel mode setting) is disabled. Here's the process for reference. Remove dots: h.t.t.p.s://streamable.c.o.m/dwgss
Here's the interesting part!!
rEFInd also shows a "boot kernel from REMIXOSSYS." Doesn't show a path to the boot file like the other rEFInd entries do. I have no idea if it's booting REMIXOSSYS/kernel directly? maybe getting info from REMIXOSSYS/syslinux.cfg? No idea. reFIND boots with an initrd.img parameter (shows "initrd=\initrd.img." The other 'normal' options boot with no parameters (shows " "). This /kernel boot ends up going through some code, then loads and fixes to my display's full resolution! (where it usually crashes with the other grub boot). I'm guessing it's detecting my GPUs properly here, or getting some sort of info from them, whereas before it wouldn't (without nomodeset), then hang. Anyways, it then gets to an "a n d r o i d [email protected]emix_x86_64" prompt, where it normally would proceed to the remixos logo, then desktop environemnt. It however stays at the prompt (I can browse the filesystem with cd/ls), but no graphical front end/desktop environment appears. I've also let it sit there for a few minutes, to no resolve. Here's the process. Remove dots: h.t.t.p.s://streamable.c.o.m/wlogn
Any advice? I'm being going crazy trying to get this to work for the past week. Finally got it to work with nomodeset, but I'm hung up on the fact that the strange (to me) /kernel boot detects and uses my display's resolution, while my normal grub.cfg does not.
EDIT: Here's a snap of the debug just before it freezes: h.t.t.p://imgur.c.o.m/a/OtScg
So there's a property serial no. failure (normal?).
According to dmesg verbose logs, usb 2-1.4= USB device number 4 using ehci-pci, idVendor=05ac, idProduct=1107, strings: Mfr=1, Product=2, SerialNumber=3, Product: Display Audio. Maybe it's the display audio that's effing things up?
or the ioatdma errors. Some sort of PCI issue? I/OAT DMA by Intel offloads memory form the cpu. Some sort of direct memory access issue? Going to try some iommu parameters.
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