Some Problems on Remix OS and Android x-86 OS

[Deni Yulianti]

Hi all.

I have a problem using Android OS on VM-ware that is related on internet connection in Android x-86 version 5.1 (Lollipop) and version 4.4 (Kitkat). 

I use android-x86-4.4-r5.iso for Kitkat and android-x86-5.1-rc.iso for Lollipop. 

I use VM-ware version 12.5.

I have internet connectivity and I can use web browser for both android emulators, but I cannot download the APK files. 

The status of the APK files at Download Folder always show Queued status and I waited for so long but there was no any APK file at that folder (Download folder), or there was no any response. 

How should I have to do to have capability downloading android applications on Android x-86?

Besides, when I changed to the guest account, I cannot access the internet, it happens for both Android x-86 OS and Remix OS. 

How should I do in order to connect between a guest account and features that just have by administrator account?

Furthermore, I would like to change my cover photo (background) on Android x-86 version 5.1 (Lollipop) and version 4.4 (Kitkat). 

What should I have to be able to change my cover photo to be a new one?

In addition, in Remix OS I cannot impose the code into the Remix OS. Let says I wanna impose code into /etc/init.sh. 

When I checked my account by typing "whoami", and it resulted that i was a root.

How should I do to get permission to make some codes in Remix OS?

Please help me out. I would appreciate for your suggestions. Thanks in advance.

[Dondre Johnson]

VMware is not recommended for virtual emulation. Try VirturalBox, the official Remix OS player at jide.com/remixos-player, or Remix OS x86 at jide.com/remixos-for-pc

[Evan Langlois]

First, running Remix under an emulator is not supported so you either have the abilities to configure this yourself or you don't.  You don't even say what your host OS is, so we really can't help you there.  Your network problems are between your host OS and your emulator, not Remix.  Second, most of your other issues are with Android-x86 running older versions.  Remix is marshmallow.

You mentioned /etc/init.d.  On Android, you likely mean /system/etc/init.d.  Only some ROMs actually support this.  You need to have the "run-parts" executable set-up in your init.rc and at first glance, it doesn't look like its in there.   Editting ths means changing your root filesystem so you need to be familiar with Linux commands and the way linux systems boot and initialize.  Its not for the faint of heart.   Likewise, /system/etc is in the system.img which is loopback mounted read-only and inside a system.sfs squashfs image.  You have to be very clever to get this mounted read/write as it can't be done inside Android because of how RemixOS is set up.  You need to have it to it on boot-up, which is kinda dangerous.  Also, do not let the updater run on a modified system.img as you will totally screw it up (which is why they make it so hard to do this).

Don't expect init.d support because RemixOS uses binary-diff patching, so changes to system.img just aren't gonna happen.   Currently, I'm adding these to my own image (to support Viper and adblockers, etc), and I'll copy in the original system.sfs (unchanged) when I need to do an update, and then rehack the image after the update.  If something goes wrong, I can fix it.

As for a background picture, I'm using the Android-like launcher with Desktop crap turned off so its more-or-less the standard Android Launcher with widges and all that.  Hold button on background, select Wallpaper button on the bottom.  You can also go into Settings -> Display and set the wallpaper on all Remix versions and all Android versions.  If you can't change your wallpaper, I think you should leave /etc alone!  No offense, but /etc contains stuff that are for admins, not end-users.

[hypot...@gmail.com]

init.d wasn't mentioned init.sh was; but functionally they are the same thing [lots of init.d scripts = 1 init.sh run early in boot]. Booting with system rw is also pretty straight forward; but there's also options to modify a ro system via systemless methods; we just need an updated magisk.img so any system-mods can survive an OTA. 

[nanduvsa...@gmail.com]

My PC is dual booted,when I install remix os it is done without any problems but when I switch between my operating systems it shows some error on disk,when I login to remix os after error it shows files are missing. I installed the remix os on hard disk.my PC is also triple booted windows 10,windows 7,remix os.

[Evan Langlois]

Why are people so afraid to READ THE SCREEN! I work on IT and people always call and tell me some error message popped up. I ask what it says and they say "I dunno". Read it! And then they say, "Oh, nevermind" Yeah, it says the printer is out of paper. Duh!

Don't tell us you have an error message. If you don't tell us what it says, there is no way anyone can help you and you are wasting your time. Read it!

[Evan Langlois]

Magisk is ugly. Some day when I get time (yeah, right) I can add overlayfs to the kernel (just check the box) which allows you to do overlays on the read-only system image. Its fast and clean without the nasty boot delay caused by Magisk's trickery (lots of copying and bind mounts).