Hello,
I have just installed remix os. (dual os though)
Problem is, bottom bar is solid black that means I can not use multitasking. I have to close one app to open another one. I can not also open setting etc.
What is this happening
At the first boot I had this problem too, then system automaticly rebooted and I had that bottom bar now It is again gone. I have really low notebook, has 2gigs of ram and 1.4ghz of cpi even linux freezes time to time. But so far, remix os running like a dream.
Btw, I am using 64bit version if it matters.
thanks in advance
Conixcit said:
Hello,
I have just installed remix os. (dual os though)
Problem is, bottom bar is solid black that means I can not use multitasking. I have to close one app to open another one. I can not also open setting etc.
What is this happening
At the first boot I had this problem too, then system automaticly rebooted and I had that bottom bar now It is again gone. I have really low notebook, has 2gigs of ram and 1.4ghz of cpi even linux freezes time to time. But so far, remix os running like a dream.
Btw, I am using 64bit version if it matters.
thanks in advance
Click to expand...
Click to collapse
Check the autohide settings. Settings ==> Display ==> Autohide (and right click on taskbar if you can)
HypoTurtle said:
Check the autohide settings. Settings ==> Display ==> Autohide (and right click on taskbar if you can)
Click to expand...
Click to collapse
First of all thanks for reply,
And it is not what you say, it isn't hidin problem is
Where running apps and stats should be covered with solid black, (same border)
Conixcit said:
First of all thanks for reply,
And it is not what you say, it isn't hidin problem is
Where running apps and stats should be covered with solid black, (same border)
Click to expand...
Click to collapse
I think I had what you're describing and toggling the autohide fixed it (i think there was a mismatch between the setting value and the right click value).
That being said it might be better to try the 32bit version on your device; it should be easier on resources.
I'll go one farther and say that you should not be running the 64-bit at all on that notebook. You don't have the hardware to properly support it. Upon initial installation you should have seen a pop-up telling you to make sure you are using the 32-bit version based on your hardware.
ZiQn3zZ said:
I'll go one farther and say that you should not be running the 64-bit at all on that notebook. You don't have the hardware to properly support it. Upon initial installation you should have seen a pop-up telling you to make sure you are using the 32-bit version based on your hardware.
Click to expand...
Click to collapse
I totally agree but 64 bit version is the only version that supports EFI ,
Conixcit said:
I totally agree but 64 bit version is the only version that supports EFI ,
Click to expand...
Click to collapse
I'm fairly sure replacing the system.img, kernel, initrd.img and ramdisk.img with the 32bit ones and removing the _64 from the grub.cfg will boot with efi grub... if you want to try
HypoTurtle said:
I'm fairly sure replacing the system.img, kernel, initrd.img and ramdisk.img with the 32bit ones and removing the _64 from the grub.cfg will boot with efi grub... if you want to try
Click to expand...
Click to collapse
What possibly can go wrong anyway?
It's my side OS anyway.
I'll try as soon as I reach home.
Conixcit said:
What possibly can go wrong anyway?
It's my side OS anyway.
I'll try as soon as I reach home.
Click to expand...
Click to collapse
I had the same problem, I fixed it by adding
ro.remixos.no_wallpaper=true
in build.prop where other ro.remixos options are configured
and also remove the 2 ffmpeg lines to remove blinking issue...
If you cannot open any application plug in any usb, es file explorer will appear then enable root explorer option
and navigate to /system to edit build.prop and finally edit it..
updesh94 said:
I had the same problem, I fixed it by adding
ro.remixos.no_wallpaper=true
in build.prop where other ro.remixos options are configured
and also remove the 2 ffmpeg lines to remove blinking issue...
If you cannot open any application plug in any usb, es file explorer will appear then enable root explorer option
and navigate to /system to edit build.prop and finally edit it..
Click to expand...
Click to collapse
where is exactly "build.prob" file.
I'm using Ubuntu
Conixcit said:
where is exactly "build.prob" file.
I'm using Ubuntu
Click to expand...
Click to collapse
It's within the system.img; within RemixOS it's at /system/build.prop.
But I don't think this is a fix per say - yes it seems to work for some people; but this could be due to some data hangover from a previous version with this line present.
What I would try first is simply clearing data from SystemUI (and Settings) app.
HypoTurtle said:
It's within the system.img; within RemixOS it's at /system/build.prop.
But I don't think this is a fix per say - yes it seems to work for some people; but this could be due to some data hangover from a previous version with this line present.
What I would try first is simply clearing data from SystemUI (and Settings) app.
Click to expand...
Click to collapse
Already done that. Not helps
Letme try that file editing thing
HypoTurtle said:
It's within the system.img; within RemixOS it's at /system/build.prop.
But I don't think this is a fix per say - yes it seems to work for some people; but this could be due to some data hangover from a previous version with this line present.
What I would try first is simply clearing data from SystemUI (and Settings) app.
Click to expand...
Click to collapse
Can't find that build.prob file....
Conixcit said:
Can't find that build.prob file....
Click to expand...
Click to collapse
You're dual booting with ubuntu, right?
If so then just mount the system.img and you'll see it righg there.
mkdir rossystem && mount -t ext4 system.img rossystem
or if your using a system folder then it should be just in there.
I had the same problem, I fixed it by adding in build.prop
ro.remixos.no_wallpaper=true
Related
https://i.imgur.com/qfuKKFQ.jpg <- Here's what I get.
I downloaded release_Remix_OS_for_PC_64_B2016020201_Alpha_EFI.zip from the Official Website. Opened the tool inside, and copied the files into my USB 3.0 flash drive using it. Write speeds are higher than 20MB/s. I have a UEFI BIOS. I get the same thing on both Resilient mode and Guest mode. I selected Resilient mode on first launch and the system went through the first launch steps.
When you get to the boot choice of RemixOS remove 'quiet' from the line when TAB and then 'e' for editing it, to show what's going on @ boot time.
most time we solve this by deleting recreating data.img
I hope that helps you
ecksdeeay said:
When you get to the boot choice of RemixOS remove 'quiet' from the line when TAB and then 'e' for editing it, to show what's going on @ boot time.
Click to expand...
Click to collapse
I did that. But this is all I could take a picture of. http://i.imgur.com/7rseNNe.jpg I have no clue what any of it means.
I opened it in guest mode.
imadlatch said:
most time we solve this by deleting recreating data.img
I hope that helps you
Click to expand...
Click to collapse
I dont know how to do that. I cant seem to be able to open the ISO that was in the zip file I downloaded. However, I formatted my flashdrive and used the included tool to reinstall Remix OS. It didnt help.
on the edit line you removed 'quiet' from, put 'DEBUG=1' or just put the '1' on the DEBUG= if it's showing ? I forget if it is but it will go through like before but this time will stop twice where you have to type 'exit' for it to proceed (twice-I repeat!) maybe that'll help? or @imadlatch is more than likely correct?
ecksdeeay said:
on the edit line you removed 'quiet' from, put 'DEBUG=1' or just put the '1' on the DEBUG= if it's showing ? I forget if it is but it will go through like before but this time will stop twice where you have to type 'exit' for it to proceed (twice-I repeat!) maybe that'll help? or @imadlatch is more than likely correct?
Click to expand...
Click to collapse
Here's what I got doing that. http://imgur.com/a/SL1rQ
I never got the second exit prompt. I just got the errors in this https://i.imgur.com/sGo2EQ5.jpg image over and over.
SELinux error. When installing on hardrive the selinux command is passed to the boot line (I'm only guessing here but if you could maybe add this) 'androidboot.selinux=permissive' worth a try?...what are you using as your machine? send feedback from here http://goo.gl/kt1bwC using the Google form https://goo.gl/pcRswT
ecksdeeay said:
SELinux error. When installing on hardrive the selinux command is passed to the boot line (I'm only guessing here but if you could maybe add this) 'androidboot.selinux=permissive' worth a try?...what are you using as your machine? send feedback from here http://goo.gl/kt1bwC using the Google form https://goo.gl/pcRswT
Click to expand...
Click to collapse
androidboot.selinux=permissive is present there by default. Im using a lenovo ideapad y510P with core i7 4700MQ, 8 Gigs of RAM and dual Nvidia GT 755M.
incognitonk said:
Nvidia GT 755M.
Click to expand...
Click to collapse
Nvidia is the problem then. ...
ecksdeeay said:
Nvidia is the problem then. ...
Click to expand...
Click to collapse
Really? Oh well, guess Im gonna be playing the waiting game then.
Thanks for everything up until now.
Search as I think there are work arounds @incognitonk
incognitonk said:
https://i.imgur.com/qfuKKFQ.jpg <- Here's what I get.
I downloaded release_Remix_OS_for_PC_64_B2016020201_Alpha_EFI.zip from the Official Website. Opened the tool inside, and copied the files into my USB 3.0 flash drive using it. Write speeds are higher than 20MB/s. I have a UEFI BIOS. I get the same thing on both Resilient mode and Guest mode. I selected Resilient mode on first launch and the system went through the first launch steps.
Click to expand...
Click to collapse
Its look like its because of your nvdia GPU isssue , don't worry we have solution for this
Select resident mode , don't press enter , press tab you will get into edit mode.
At the end after space write this line - " nomodeset vga = 0x34C "
Without the quote .
Press enter , enjoy remix ☺☺
Hit thanks if it help
mdezazrock said:
Its look like its because of your nvdia GPU isssue , don't worry we have solution for this
Select resident mode , don't press enter , press tab you will get into edit mode.
At the end after space write this line - " nomodeset vga = 0x34C "
Without the quote .
Press enter , enjoy remix ☺☺
Click to expand...
Click to collapse
Thank you, It definitely did help. However the resolution is all wonky now. I have a 1080p screen. The images are all grainy and stretched out. Also, i can see the linux prompt blinking in the background. Anything I type on the keyboard will be entered there. Hence, if i type "reboot" and hit enter, the system will reboot.
I also tried the workarounds in this reddit post: https://www.reddit.com/r/RemixOS/comments/42wylw/any_way_to_run_with_nvidia_gpu/czenutg
But none of them helped either. I get the same issues; the poor resolution and the blinking prompt.
incognitonk said:
Thank you, It definitely did help. However the resolution is all wonky now. I have a 1080p screen. The images are all grainy and stretched out. Also, i can see the linux prompt blinking in the background. Anything I type on the keyboard will be entered there. Hence, if i type "reboot" and hit enter, the system will reboot.
I also tried the workarounds in this reddit post: https://www.reddit.com/r/RemixOS/comments/42wylw/any_way_to_run_with_nvidia_gpu/czenutg
But none of them helped either. I get the same issues; the poor resolution and the blinking prompt.
Click to expand...
Click to collapse
I don't know the blinking error solution , my friend also have that same problem , but there is a easy solution for resolution -
Root remix os , open any rooted browser , go to system folder , then open build.prop , edit the file , just add a line at the end
"ro.sf.lcd_density=150"
Write that line without quote , save build.prop , and change the number between 140 to 210 , see which one looks better on your monitor , have fun exploring remix ☺
Finally got my Alienware X51 to work. It has the GTX 660 gpu.
Combine and try this boot flags and see which one works for you.
1. nomodeset
2. nouveau.modeset=0
3. nouveau.modeset=1
4. video=uvesafb
5. video=simplefb
6. i915.modeset=0
7. i915.modeset=1
My X51 works beautifully with nouveau.modeset=1 i915.modeset=0
Thanks to: winsock2 reddit user
source:
https://www.reddit.com/r/RemixOS/comments/42wylw/any_way_to_run_with_nvidia_gpu/
Click to expand...
Click to collapse
How do i enter this?
# Reboot/Boot and press ESC key to go to main grub menu
# Press E
# Highlight the line that says kernel, press E.
# Enter the above flag/flags right after "androidboot.hardware=remix_x86_64" (Use the arrow keys to go left or right)
# There should be a space between each of the flags
# Optional: go to the end of the line and type DEBUG=1
# Press Enter......Press B to boot.
Okay. I finally got the right boot flags. How do I make it permanent?
# For EFI booters, navigate to X:\RemixOS\efi\boot and edit/add the flags to your grub.cfg
# For Legacy booters, navigate to X:\RemixOS\ and and edit/add the flags to your menu.lst
* Replace X:\ with the drive letter on which you installed your RemixOS
* You can open it in any text editor...but I prefer Notepad++
* Be sure to back up your grub.cfg or menu.lst before making any changes...so that you can always fall back to a working configuration if you mess up.
Happy Remixing!!!
Thanks. This seems to work and the MXPlayer is now playing all file formats.
where do i type this?
kushsingh said:
where do i type this?
Click to expand...
Click to collapse
Check the first post....i added the steps
Is there any way to save the kernel settings so I don't need to write them every time?
skitmos said:
Is there any way to save the kernel settings so I don't need to write them every time?
Click to expand...
Click to collapse
in menu.lst file
You_KS said:
in menu.lst file
Click to expand...
Click to collapse
I'm sorry, I'm new to this. Can you be more specific on where I can find the file, and which part of it to edit, and how?
Ash110 said:
I'm sorry, I'm new to this. Can you be more specific on where I can find the file, and which part of it to edit, and how?
Click to expand...
Click to collapse
It's in C:\RemixOS (assuming C is the drive where you installed) open the file as text and you'll find the kernel line you edit at boot
Isn't this uefi? Legacy is different
Ash110 said:
I'm sorry, I'm new to this. Can you be more specific on where I can find the file, and which part of it to edit, and how?
Click to expand...
Click to collapse
Depends on whether you are using UEFI or BIOS
AmoraRei said:
Isn't this uefi? Legacy is different
Click to expand...
Click to collapse
For LEGACY, edit the file found here: X:\RemixOS\menu.lst
For EFI, edit the file found here: X:\RemixOS\efi\boot\grub.cfg
Note 1: Preferably, use Notepad++ to edit those files
Note 2: Replace X with the drive letter where you installed RemixOS
Can we change the DPI?
AmoraRei said:
Can we change the DPI?
Click to expand...
Click to collapse
Put DPI=xxx (replace with any dpi value)
freelancer81 said:
Put DPI=xxx (replace with any dpi value)
Click to expand...
Click to collapse
And where would that be found?
Fermi may working great. But Maxwell may not. Need Linux kernel 4.6
Sent from my Nexus 6P using Tapatalk
Ash110 said:
And where would that be found?
Click to expand...
Click to collapse
A little googling would have answered your question....
common DPIs are 120, 145, 160, 180, 200, 220, 240....
play around....and see which works best for your monitor/screen.
Houge_Langley said:
Fermi may working great. But Maxwell may not. Need Linux kernel 4.6
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I am not sure bro....
So for now, the only option is to try those boot flags and if it works....Great.
If it does not....we just have to wait for a better fix or upgrades to the 4.6 kernel.
freelancer81 said:
I am not sure bro....
So for now, the only option is to try those boot flags and if it works....Great.
If it does not....we just have to wait for a better fix or upgrades to the 4.6 kernel.
Click to expand...
Click to collapse
Yes, i got this info from Phoronix News
http://phoronix.com/scan.php?page=news_item&px=NVIDIA-Blobs-In-Linux-Firmware
Sent from my Nexus 6P using Tapatalk
freelancer81 said:
A little googling would have answered your question....
common DPIs are 120, 145, 160, 180, 200, 220, 240....
play around....and see which works best for your monitor/screen.
Click to expand...
Click to collapse
Oh no! I know what DPIs are, having played around with them on my phone. Idk where to change DPI in remix OS
Ash110 said:
Oh no! I know what DPIs are, having played around with them on my phone. Idk where to change DPI in remix OS
Click to expand...
Click to collapse
ah well.....your question confused me.
anyways....if you read the previous posts, you would know where or how to put it.
to test it first, go to the grub bootloader and edit the lines to add the DPI=xxx
if you find a dpi that works great on your display, you can permanently set it in your menu.lst or grub.cfg
freelancer81 said:
ah well.....your question confused me.
anyways....if you read the previous posts, you would know where or how to put it.
to test it first, go to the grub bootloader and edit the lines to add the DPI=xxx
if you find a dpi that works great on your display, you can permanently set it in your menu.lst or grub.cfg
Click to expand...
Click to collapse
I checked my menu.lst, but I really couldn't find the dpi thing. Maybe I deleted it or something? Where is it supposed to be?
Hi my friend,
I have just installed the last version of Remix OS PC 64 bit UEFI (build 2.0.205) on my desktop, but after the restart, the taskbar seems like a black rectangle, without any button on it, just all black. I can't use the system without the taskbar, I have just tried to insert the line ro.remixos.no_wallpaper=true in the build.prop file, but it doesn't work as I expected. The taskbar continues to remain black and unusefull.
Have you an idea as I can resolve this problem ?
My sistem specs is:
Motherboard: Asrock QC5000-ITX/WiFi
Disk Drives: Samsung SSD 120GB (dual-boot)
Graphics Card: AMD Radeno HD8300
CPU: AMD A8-4500M APU
BOOT: UEFI
OS: Remix OS Build 2.0.205 (64 bit UEFI)
Thank you in advance for any helps
Best
Francesco
Try change true to false
Or try this Unplug the Keyboard from the PC before you turn on the Computer wait untill Remix oS is started wait a few second plug in your Keyboard
Thank you missing taskbar Resolved!
Thank you,
I have just resolved my problem.
Francesco
kretex said:
Try change true to false
Or try this Unplug the Keyboard from the PC before you turn on the Computer wait untill Remix oS is started wait a few second plug in your Keyboard
Click to expand...
Click to collapse
jonnystorm70 said:
Thank you,
I have just resolved my problem.
Francesco
Click to expand...
Click to collapse
How you resolved it would be very helpful, thanks.
I Just resolved in the following way:
I expanded the system.img file with RMXTool software, the inserted the line
ro.remixos.no_wallpaper=true
in the build.prop file located in \system_\
then rebuilded system.img and copy it in the place of the original system.img file.
After reboot, all the system was ok and taskbar appeared 100% functional.
Let me know if you need some extra help
Best
Francesco
2mecky said:
How you resolved it would be very helpful, thanks.
Click to expand...
Click to collapse
jonnystorm70 said:
I Just resolved in the following way:
I expanded the system.img file with RMXTool software, the inserted the line
ro.remixos.no_wallpaper=true
in the build.prop file located in \system_\
then rebuilded system.img and copy it in the place of the original system.img file.
After reboot, all the system was ok and taskbar appeared 100% functional.
Let me know if you need some extra help
Best
Francesco
Click to expand...
Click to collapse
I'll give it a go thanks. Just one question though, do you need root access to make those mods, for some reason I'm having trouble achieving root, even when following the tutorials closely..??
Hi,
really not, i didn't root the system before resolve my problem. I rooted it after, when my taskbar appeared and work perfectly.
For anything you need don't esitate to ask
Best
Francesco
2mecky said:
I'll give it a go thanks. Just one question though, do you need root access to make those mods, for some reason I'm having trouble achieving root, even when following the tutorials closely..??
Click to expand...
Click to collapse
apparently the time "fix" was switching from UTC to local.
guess what? I don't use windows. So of course my RTC is set to UTC not local.
so every time I boot remix it thinks local time is UTC.
anyone know how to switch it back to use UTC
the solution is not network time or manually change because that will reset my RTC.
update
default.prop contains persist.rtc_local_time=1
*gasp* you...you don't use windows? what *is* there else?
I use Arch, Solus, and Remix OS on my desktop.
And as this a subforum about Remix OS, a desktop-oriented version of Android, which in turn is based upon Linux, I'd say there is a lot beyond Windows.
moriel5 said:
I use Arch, Solus, and Remix OS on my desktop.
And as this a subforum about Remix OS, a desktop-oriented version of Android, which in turn is based upon Linux, I'd say there is a lot beyond Windows.
Click to expand...
Click to collapse
A desktop or laptop will use the time from your motherboard's BIOS before it gets the time from anywhere else. You could boot into ypur BIOS and see what the time is set to there.
I have Remix dual-booting on my laptop and in VirtualBox on my desktop, and Remix gets the time from the BIOS on both computers regardless of OS.
-BoneZ- said:
A desktop or laptop will use the time from your motherboard's BIOS before it gets the time from anywhere else. You could boot into ypur BIOS and see what the time is set to there.
I have Remix dual-booting on my laptop and in VirtualBox on my desktop, and Remix gets the time from the BIOS on both computers regardless of OS.
Click to expand...
Click to collapse
Same here about the BIOS.
-BoneZ- said:
A desktop or laptop will use the time from your motherboard's BIOS before it gets the time from anywhere else. You could boot into ypur BIOS and see what the time is set to there.
I have Remix dual-booting on my laptop and in VirtualBox on my desktop, and Remix gets the time from the BIOS on both computers regardless of OS.
Click to expand...
Click to collapse
I already said in the op it is set to UTC, changing it in the bios/uefi is not a solution because my 2/3 os's are using UTC which sets RTC to UTC. Remix doesn't use UTC it uses local now. Looks like nothing short of modify ramdisk will fix it
Maromi said:
I already said in the op it is set to UTC, changing it in the bios/uefi is not a solution because my 2/3 os's are using UTC which sets RTC to UTC. Remix doesn't use UTC it uses local now. Looks like nothing short of modify ramdisk will fix it
Click to expand...
Click to collapse
Does hwclock do what you need? Perhaps with setprop persist.rtc_local_time 0
HypoTurtle said:
Does hwclock do what you need? Perhaps with setprop persist.rtc_local_time 0
Click to expand...
Click to collapse
Hwclock is the same thing as changing it in bios/uefi menu. Its the system clock using local instead of UTC. Also it's default.prop so can't change it that way. Maybe the latest stable supersu? I noticed with the latest systemless xposed you don't need to modify ramdisk if using 2.76 systemless. Nvm about supersu
Maromi said:
Hwclock is the same thing as changing it in bios/uefi menu. Its the system clock using local instead of UTC. Also it's default.prop so can't change it that way. Maybe the latest stable supersu?
Click to expand...
Click to collapse
It can be changed that way. All persist.* entries - from default.prop/build.prop/local.prop etc. are saved to /data/property/* and they can be changed via setprop [or manually I guess]
HypoTurtle said:
It can be changed that way. All persist.* entries - from default.prop/build.prop/local.prop etc. are saved to /data/property/* and they can be changed via setprop [or manually I guess]
Click to expand...
Click to collapse
I did try it and /data/property value is 0 for it but it didn't change the clock. FYI I am using script to enforce it
Also found this
https://github.com/quanganh2627/and...47-Init-Setting-system-time-back-to-utc.patch
And source forge is down so I can't see the commit for it. I think something was removed
Update:
well i went ahead and changed persist.rtc_local_time=1 to 0 in the ramdisk.
no more rtc resetting when changing the time to local using network time settings now.
something must still be missing so i can change and save the time without network settings.
Also does anyone know how to disable the 4 finger touch minimize? The setting was removed and guess fast screen typing wasn't a concern?
Also screen brightness? Guess being a battery killer wasn't a concern either?
Hey guys,
I recently installed RemixOS 3.0.204 on an Acer Alpha Switch 12, and since I'm running it with Windows 10 but I intend to install some Linux flavor later on, I decided to go ahead and use rEFInd for multibooting (there's also the fact that RemixOS' GRUB wouldn't show up anywhere in my system).
My question at this point regards the default GRUB installed with RemixOS; I can't seem to find the configuration that's running anywhere. I found a couple of grub.cfg files on /EFI/RemixOS/efi/RemixOS (namely grub.cfg, grub32.cfg, grub64.cfg), but editing any or all of these had no impact whatsoever on my GRUB entries. Would anyone be able to help me either remove the GRUB menu altogether or customize it, at least?
Thanks in advance.
EDIT: if anyone's looking for a similar solution, you'll very likely need to mount your computer's EFI partition like I did - the one that would show up is probably the EFI folder on RemixOS installation files. To do that, I had to look into /dev/block and my partitions were listed as sdaX, so chances are you'll find a similar setup for your computer. Good luck!
UEFI boot uses EFI:/boot/grub/grub.cfg file for the menuentry details - edit this one.
Vioner said:
UEFI boot uses EFI:/boot/grub/grub.cfg file for the menuentry details - edit this one.
Click to expand...
Click to collapse
I finally managed to find out what I was doing wrong; I assumed a device listed in /storage was my EFI partition, but it turns out it was probably just the EFI folder from RemixOS original installation. I managed to find my EFI on /dev/block/sda1 and editing grub.cfg was spot on.
Thanks for the help, buddy!
GryphonBR said:
Hey guys,
I recently installed RemixOS 3.0.204 on an Acer Alpha Switch 12, and since I'm running it with Windows 10 but I intend to install some Linux flavor later on, I decided to go ahead and use rEFInd for multibooting (there's also the fact that RemixOS' GRUB wouldn't show up anywhere in my system).
My question at this point regards the default GRUB installed with RemixOS; I can't seem to find the configuration that's running anywhere. I found a couple of grub.cfg files on /EFI/RemixOS/efi/RemixOS (namely grub.cfg, grub32.cfg, grub64.cfg), but editing any or all of these had no impact whatsoever on my GRUB entries. Would anyone be able to help me either remove the GRUB menu altogether or customize it, at least?
Thanks in advance.
EDIT: if anyone's looking for a similar solution, you'll very likely need to mount your computer's EFI partition like I did - the one that would show up is probably the EFI folder on RemixOS installation files. To do that, I had to look into /dev/block and my partitions were listed as sdaX, so chances are you'll find a similar setup for your computer. Good luck!
Click to expand...
Click to collapse
How is Remix running on your switch 12; does everything work properly?
Ludespeed said:
How is Remix running on your switch 12; does everything work properly?
Click to expand...
Click to collapse
Yep, every little thing. The one gripe I've had is when I connect the charger with the computer on standby from Remix OS - not sure what is causing it, but it will reset and I have to do a cold start to get it back to work. But if I take the time to wake it up, connect the charger and then put it back to sleep, no problems.
But other than that, everything is great - sound, WiFi, every port... Oh, one more annoyance - the physical volume keys don't work out of the box. I might be able to get them to, but for now I don't care much about it. And one thing I haven't tried at all is the internal gyroscope, to see if the screen rotates automatically.