yashsingh1/xdaforums huggingface dataset:
[Remix OS for PC] enginbahadir:
I installed this with RemixOs installer tool.

This version is better than original release of RemixOs :) Thanks for your work.

I have only one problem. When i clicked on time from taskbar, i can see what time is it. But in taskbar it shows only "HH:MM Day".

This is not a big problem, maybe because of my screen resolution.

System: Intel Celeron B830 with Intel HD 2000. 4Gb of RAM.

(sorry for bad english)
[Remix OS for PC] pwag:
Installed on my Surface Pro 3, works like a gigantic tablet, pen and touchscreen work well. Only issue I had was my fan ran constantly and the machine seemed warmer than it did when running windows 10
[Remix OS for PC] bg260:
I have spent my free time, for the better part of a week, getting this to triple - boot alongside Xubuntu 16.04 and Win 10. I was trying to do it without any 3rd party applications. In the end I relented and had success with Grub2win. That being said you would think it time for celebration, but no.

I have been rewarded with a horrible user experience. When I click an app, I can leave the room, make a sandwich, eat it, do the dishes and go to the bathroom before it loads. If it loads. 8 out of ten I get a "sorry Chrome or, whatever, is not responding" it will eventually open. After about an hour of going nowhere I get frustrated and exit. I'm pretty sure this is not the norm as my search results bare little fruit. I am also pretty sure that it is me that has screwed this pooch. I'd like to know if there are any ideas.

Running an HP Pavillion 15. 8Gb RAM, 1Tb hdd.

AMD A10-5745M APU w/Radeon HD Graphics

2.10Ghz

I installed Remix to a 64Gb partition, the last on the hard drive.

Not sure what's up. Windows and Xubuntu run great.

I have been really excited about this venture and would like to continue on. Right now the outlook is bleak.

I would greatly appreciate any suggestions.

Thanks

P.S. I have: cleared cache, cleared data, reset sync, installed Play Services via the terminal, signed out of Google and signed back in, signed out of Chrome and signed back in, signed out of Gmail and signed back in. I think I have tried all of the possible fixes described in the thread. Hoping it's not hardware.

Also of note. I mounted the partition in the /media/"username"/uuid# directory. Could this be the problem?
[Remix OS for PC] Vioner:
[MENTION=7185243]bg260[/MENTION] read up on "disable media scanner" - this might help you a lot.

Remix 2.0.205 has retarded media scanning feature which scans all the drived all the time using up CPU and I/O.

Easy way to check if this is the problem is also installing a previous or newer Remix.

Other than that I think you have bad hardware for this. AMD CPU and GPU work worse as they never had any official Android support. (Intel had).

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Remix OS for PC] bg260:
That was what I was worried about. I am going to try to umount /data and see if that helps. (I've only got 300Gb of media in there);) The good news , at least hardware wise. My other laptop is an ASUS with Intel Inside:laugh:. Only 4Gb RAM though. Not sure if I want to triple-boot it or not. Thanks for responding.
[Remix OS for PC] Vioner:
Unmounting will barely help - scanning will go on on Android system and data partitions.

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Remix OS for PC] bg260:
I see. So it's more of a persistent than a quantity. Seems like I should be able to do something through CLI. Yay, more research.

BTW. People are asking questions here because:

1. This

IS

the Edition to have.

2. This thread is #1 after the stickies due to having the most replies. (this indicates actual support). And

3. S**t like this - Discuss Remix OS Bugs Here

I really appreciate you pointing me in the right direction, and your patience.
[Remix OS for PC] Vioner:
[MENTION=7185243]bg260[/MENTION] media scanner used to lag my Asus T100 like hell, but after disabling media scanner the whole OS works blazing fast. Sorry, but right now I can't point you to the exact command you'd have to type in the ALT-F1 console. It's very simple and it won't ruin anything. You don't need media scanner to do anything. It will disable only the persistent scanning, not the whole media storage detectiion.

I'll send in the commands ASAP.

Also you can install PhoenixOS on ur machine - if it doesn't lag then the problem in Remix is definitely the media scanner. Phoenix has media scanner working just fine.

And btw Phoenix is just better.

Edit:

I understand why people may post here but you need to understand one important thing - Jide probably will not look into this thread just because it's name is "hacked". If I were them then I'd think it's a waste of time because they won't support unofficial stuff.

Also, I recommend getting systemless root

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Remix OS for PC] bg260:
[MENTION=4666322]Ventricle[/MENTION] Thanks, I'm looking into all your options. I'm wondering if Root is even necessary anyway. Should be able to make changes to / via Linux CLI or even a live gparted session. Lots to think on.

Edit: New Beta release on, well...today July 5th it what it says. Maybe always has today's date. A lot of bug fixes, nothing about media scanner, ANR's fixed ,did look promising.
[Remix OS for PC] Vioner:
[MENTION=7185243]bg260[/MENTION] latest beta .402 version was released recently, don't know if today.

It says:

Fix: The slowing down of the system when mounting hard disks is fixed.

At first I was naive to think this meant fixing media scanner, but it didn't, so its better to test older version or Phoenix. Anyway, I haven't tested .402 Remix yet.

If you can be satisfied by root use applied only textually, with no GUI, then all Android-x86 versions have root that can be used via alt-f1 console. Alt-f7 or f8 (don't remember) to get back to GUI.

Edit:

I've checked the command for disabling android media scanner. All below commands require root, so use rooted build like this hacked one or just use ALT+F1 console:

pm disable com.android.providers.media/com.android.providers.media.MediaScannerReceiver

or

pm hide com.android.providers.media/com.android.providers.media.MediaScannerReceiver

If this doesn't change anything, then try disabling whole media scanner just to make sure if it causes the lags:

pm hide com.android.providers.media

Remember - the last command is only for testing - you must re-enable the media storage app afterwards or you will experience problems like inability to make screenshots or problems with writing files in some situations.

To re-enable com.android.providers.media (Media Storage app)

pm unhide com.android.providers.media
[Remix OS for PC] bg260:
[MENTION=4666322]Ventricle[/MENTION] Yep, today, it was just posted. I think I beat him to it. v2.0.402. I've got plenty to go on now. Thanks again for the assist. Sometimes we need another pair of eyes in order to see what is right in front of us.

Cheers.

Edit: Saw your edit with command lines. I'll give it a try. Looks like it will work.
[Remix OS for PC] malghani:
Thanks

Thanks man for this awesome OS:good::good:
[Remix OS for PC] bg260:
[MENTION=4666322]Ventricle[/MENTION] Did a full partition wipe, format and reinstall. Entered first code from your post. Media scanner disabled! She's running like a well oiled machine.

Also: Set ro.wifi.channels=11 <------- U.S. / Varies per region. SEE HERE

Thanks for the help. What kind of beer do you like?!?

Edit: Disabling Media Scanner may cause issues with Playstore. Let it update first. I had to manually update it.
[Remix OS for PC] sharmabkhp:
download link for hacked version of remix os not working

kindly post workable link
[Remix OS for PC] Vioner:
[MENTION=7185243]bg260[/MENTION] I'm happy it worked. You've hit the thanks button - virtual beer is here - that's even better because I don't like real beer :D

Enjoy the OS and grats on the WiFi fix.

Also, again, I recommend using PhoenixOS - it has much better UI UX (both stability and feature wise).

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Remix OS for PC] yshalsager:
I tried to update from this version to v2.0.402 using OTA, first it can't check, i removed "Hacked" from version in buildprop then downloaded OTA.

When i rebooted to install it gave me "error 7 Update failed" - After restarting OTA package has been removed

Any solution?
[Remix OS for PC] nkolvek:
Over the last few days I have tried several different ways to do this with 64bit UEFI installs. Stock 2.0.205 installs fine and runs fine, without a hitch actually. Using this image, the packaged installer doesn't work for me, as mentioned by others on this post. I even tried to stock 2.0.205 installer. The packaged installer with this image writes grub but wont load win 10 (no big deal, takes 1 minute to repair and get booting) but this wipes out grub and I haven't actually tried to re-write the cfg yet. Using the installer on page 41, the android-x86 installer, everything seems to install fine but no grub or other OS bootloader than windows. It also writes the OS to a different folder (androidOS) instead of remix but this is not an issue. I'm assuming I can just re-install with the android-x86 installer and then edit efi (safe to assume its just the boot order not writing to the top of the list). Makes me wonder what the TG installer is doing to the bootloader entires if windows is listed in grub but not booting.
[Remix OS for PC] moriel5:
This is a modified build, OTA's won't work here.

Security checks are by blocks, rather than files, so any modification to /system causes the OTA's to fail.

This has existed in Android since version 5.0.
[Remix OS for PC] hdokes:
Greetings,

I use vmware workstation 12 and have already successfully installed the original Remix OS to it's own vm and it works very well. I have also installed the original Remix OS to a flash drive and have used it between my car computer, surface pro 3, and my laptop with various degrees of success. It comes up in all of them but their are quirks such as intermittent wifi (definitely seems to be a dns issue as I can ping any IP address I choose... just can't ping by name but I digress) audio, and bluetooth support.

I also have successfully rooted the original vmware installation of Remix OS so I have a fairly decent handle on what I'm doing. I am excited to install the Remix-Hacked version and have downloaded and upzipped the 64bit iso however when I attempt to install it (pointing to the iso for the cdrom) into a vm it is not recognized as a bootable iso as the original Remix is and therefor does not boot up into the opening install/run screen.

Is this by design or am I overlooking something?
[Remix OS for PC] javierascua:
I can`t update to v2.0.402 usingn OTA, anybody tell me what happened? or i have to wait for remix os hacked edition v2.0.402 to update?
[Remix OS for PC] Vioner:
Man, seriously? The answer is few posts above - post #523

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Remix OS for PC] bg260:
Try booting into a live session of gparted or the distro of your choice. Use the file manager to check all your partitions to see where Remix is installing grub. The installer does not ask you where to install it just yes or know. Alternatively, extract contents of iso. Copy and paste contents to the partition of choice. copy EFI to EFI. Create directory "system" in partition mount system.img and extract contents to "system" directory. Try one or all of these. Or none I suppose.

I ended up having grub installed on my windows recovery partition when i checked BTW.
[Remix OS for PC] nkolvek:
I figured it out just a bit ago. Using this image and the android-x86 installer, just do your options, wait for install to finish, use EasyUEFI and change your boot order. For me it places the android entry at the bottom of the list instead of where it should be. This also explains why I had no grub before with this release. Thanks.
[Remix OS for PC] bg260:
I used grub2win. Same effect. Glad you got it .
[Remix OS for PC] javierascua:
Thxs for your answer, but my question is about to update via OTA to remix os pc hacked v2.0.402 when it realize
[Remix OS for PC] moriel5:
I can understand why you thought that this will be via OTA, it's easy to misunderstand.

However, the hacked versions are just modded versions of the official RemixOS, no more.

As such, they can't be updated via OTA, even to newer hacked versions.

However, I propose a CLI updater, which can be invoked from the terminal to check for a newer hacked version, and if there is, will download the full file, and just patch the system (necessiating a reboot, for obvious reasons).

That way, it will be similar to ArnoldTheBat's ChromiumOS's CLI update method.
[Remix OS for PC] wizmart:
this is how i did: i download ota from jide directly, 32b for me, then i installed with Unetbootin to my hd, rebooted and from the bootmenu first choosed unetbootin then installed to hd, it will install to android-2016-06-30, i did rw install with no grub, then i just move the system folder to my 205remix folder after renaming the 205 system folder, overwrite int,ramdisk and kernel from 06-30.thats it! first boot takes a while cause upgrading , all your apps wiil show as before on 205 just need to grant root again if needed. Enjoy!

(i did went crazy on my second full boot cause i choosed upgrde grub on install and if you don't check "android_x86" on your grub entry it wont boot, putting back to remix_x86 did solve the problem and it runs really good now, a lot of improvements indeed..)
[Remix OS for PC] javierascua:
Thxs, now i understand. And the CLI updater will be nice
[Remix OS for PC] moriel5:
I hope that the OP will add it.

By the way, Wizmart, I think that your procedure could be awesome for the CLI updater, if there will be one.
[Remix OS for PC] HypoTurtle:
Hope I'm not speaking out of turn...

But yea as already stated there's no OTA mechanic to update individual files; rather than patching block files - which would be needed to update this.

Is there anything in particular that you need the hacked version over stock for? Perhaps I can add it to the systemless root [i.e. stock system with custom files mounted over the top] that you could use in the interim.
[Remix OS for PC] wizmart:
well i think its possible to update if you change your buildprop and remove the hacked edition from the remix description, i havent tried yet but it might work if you check your grub entry again before rebooting
[Remix OS for PC] HypoTurtle:
It's not... it's purely a block based patch - and to ensure it applys correctly the .imgs are checked to make sure they match stock.

Procedure: initrd.img runs ==> if /data/media/0/autoupdater/otapackage.zip exists x86updater is run ==> sha1 figures compared between values in zip and the unmounted *.imgs ==> if sha1s match ota is applied - *imgs are patched - ==> otapackage.zip is removed and system is rebooted.

Tl;dr modifying build.prop [and even changing it back] will change the sha1sum of system.img and thus the ota will fail.
[Remix OS for PC] shanx_verma:
Check this out. :)

Hey bro I hope you're feeling awesome and well now .. :) :)

Looks like Jide have released another update officially, total, fully-featured version 2.0.402 on Jul 6th 2016.

So no pressure, none at all, just that I would really love it if you think about updating it. The newer version has the much needed support for my NVIDIA card, but it's just that I don't want to lose your hacked version even for it!! Juz love your work!! :) :)
[Remix OS for PC] moriel5:
Although, why shouldn't we do what CyanogenMod does, and create our own OTAs for the hacked version?

If that even is possible.
[Remix OS for PC] HypoTurtle:
Been a while since I saw a cyanogen ota; but are they actually updates or are they full system ROMs that are flashed?

The issue with replying is that updating a read/write system would need a different method to apply it; as x86update only acts on the *.img (and kernal) as is; i.e. before they're mounted.

I did consider seeing if some sort of file dumper could be used similar to OTA [initrd => mount system => dump files into system => ramdisk runs => systrm starts]; but I can achieve something similar with systemless-root anyway - and it can stock ota update with 1 file change.
[Remix OS for PC] moriel5:
CM updates are full rom updates.

And what do you mean by file dumper?

And what is you Systemless Root method?

This is getting really interesting.
[Remix OS for PC] Supracer:
Delete
[Remix OS for PC] HypoTurtle:
File dumper would be say an ext4 update.img file containing updated files; system.img and update.img get mounted; update.img dumped on top of system.img files then update.img is unmounted and deleted. [But as said - never got round to making it functional]. i.e. Essentially the same as a normal rom install but without the permissions being set during install.

Systemless root from chainfire. Is essentially all the root stuff in a su.img located at /cache or /data with the ramdisk modified to mount su.img and then the su files (via xbin folder) are bind mounted over the system files; leaving the underlying system untouched.

As we don't have a recovery; and the RemixOS is split [kernel/ramdisk.img] I manually created the ramdisk/su.img to be found here

In order to modify more files I added the script:

if [ -e /su/systemfiles.txt ]; then
for line in $(cat /su/systemfiles.txt | grep -v '#'); do filenm=$(echo $line | tail -c +9);
if [ ! -e /su/vendor/$filenm ] && [ -e $line ]; then
mkdir -p /su/vendor/$( dirname $filenm);
cp -p $line /su/vendor/$filenm;
fi;
done;
fi;

for line in $(find /su/vendor/ -type f); do mount -o bind $line /system/$(echo $line | tail -c +12); done

The last line being the most important part [the top is just reading and copying a file from the system to a location you can edit it from]

With this the only think that would error an OTA is the modified ramdisk.img [ota doesn't care about data.img]; so keeping a copy of stock ramdisk.img to switch to will allow the OTA to go through.
[Remix OS for PC] moriel5:
Unless of course we modify the OTA to check for the SHA1SUM of the current hacked version, perhaps also (somehow) get a server for updates, and modify the update URL to said server.

And about the recovery, can't we make something that resembles a recovery?

To the ordinary user, it would seem like a recovery, at least.

While the methods will be different, at least it could the same tasks done (such as flashing .img files and such).
[Remix OS for PC] HypoTurtle:
In short: No on the sha1sum unless the hacked system.img is kept read-only from day0; yes an alternative ramdisk resembling a recovery could be made; we have direct access to the files/locations so 'flashing' becomes pointless
[Remix OS for PC] moriel5:
About the SHA1SUM, that's the whole point, we make our own system.img, and update it accordingly.

About the recovery/ramdisk, you're right about flashing being pointless, however it could be good for updating the systemless root and (when there will be one) the systemless Xposed, as well as disabling something in the event of a bootloop, in a comfortable way.

I personally have no qualms in using the CLI, however for less tech-savvy users who are afraid of getting their fingers dirty, it could be a good idea.

Someone packages the necessary files in a zip or some other format, and they get extracted and run.

For the average user, it would almost be just click-and-run.
[Remix OS for PC] wizmart:
just a little question between, after tweaking with experimental features on the 402 i got stuck on full screen mode for all apps and settings..i cant find a way to get back to windows mode, any solution perhaps?

edit: after clearing data from multiwindowprovider and a soft reboot i got back to windows mode..
[Remix OS for PC] bg260:
This is very good. Are you doing this through the T.E. in Remix

or a Linux shell?

I was considering the copy and over-write method, a dirty flash of sorts. ;)
[Remix OS for PC] bg260:
Try this: Power>Off:laugh:

Worked for me.
[Remix OS for PC] HypoTurtle:
My point being that everyone's sha1sum will likely be different (if they've ever mounted system read-write) - so hijacking the official ota wouldn't be feasible.

i.e. you have system1.img[~2GB] and system2.img[~2GB] and you diff to create system1-to-system2-patches[~100MB]. But if everyone has a different system1.img then they would need their own sys1-to-sys2-patches but they can just replace system1 with system2 instead so why bother creating patches...

Updates for system-less root/xposed would be just an updated ramdisk.img to use [might write an auto-patcher for it].

If your referring to the code [which gets removed in the quote] then this is auto-applied via su.d [system-less root version of init.d] and the files are housed in the su.img only 'limitation' at the moment is existing files are needed to be bind-mounted to and build.prop is read before a custom one can be bind-mounted on top of it.
[Remix OS for PC] moriel5:
Then what do you propose?

Since technically that would be a good idea... for those who don't modify their system partition.
[Remix OS for PC] bg260:
The laborious and tedious process of merging the two manually? Probably easier with a GUI:eek:

This is what was suggested to me.
[Remix OS for PC] moriel5:
I would love that, but so many things could break in the process.

About the GUI, though, I really did not understand what you had meant.
[Remix OS for PC] bg260:
GUI=Graphical User Interface CLI=Command Line Interface

Nemo, as an example, has a GUI and a compare and merge plug-in.

Also, you could clone the Remix partition and restore if anything breaks.
[Remix OS for PC] moriel5:
I know what the letters stand for and their meanings, I just didn't understand what you had meant, since I did not understand the context.
[Remix OS for PC] droseofc:
For those asking about a recovery, couldnt the flashfire app be used in replacement? Its by chainfire, may still be in beta but you can sign up for it somehow through google (cant remember). But it flashes whatever zip, img, firmware/ota/etc with the option to inject su on each flash, preserve recovery and many other things. It goes to its own "systemless" recovery and flashes and then boots back to system (or you could choose a different option). I was just about to try it to flash xposed probably the systemless xposed.....but since others have asked about flashing in recovery now im hesitant.

---------- Post added at 11:37 PM ---------- Previous post was at 11:35 PM ----------

And i just noticed i hadnt tried the hacked version (yet) but did install the beta version and it was already prerooted and i installed busybox and su just havin trouble with updating binary. Gna try hacked version tho before i get too far with settin up the beta. Also been reading other threads, is remix not rooted usually in beta or official? Alls i did was click build number and enable developer, then allow root access and been hacking my network and spoofing my girl from then on with apps that require root.
[Remix OS for PC] bg260:
I apologize for misunderstanding. It was suggest to me to use a utility like Nemo. Slowly and painfully compariing files side by side. Replacing or merging as necessary. My question has been, for Linux user's at least, I root really a necessity? I have

already made changes the build.prop and host files from a Linux terminal. Or maybe with chroot.
[Remix OS for PC] moriel5:
Don't worry, I wasn't offended, I just can't express feelings through text, that's all.

And ordinary users don't absolutely have to have root, though they can have it if they wish to have it, power users are the ones that need it.

By the way, do you use Cinnamon as your DE?

Since you mentioned Nemo.
[Remix OS for PC] bg260:
Linux Mint 'Sarah' currently :). I am proficient enough to be able to entirely break it. If I try.
[Remix OS for PC] HypoTurtle:
Yea it's a good idea for those with identical system.imgs [i.e. sha1sums]; but I'm sure there's not too many users of this version that have identical sha1sums. The alternative being to simply replace the old system.img [and other .imgs] with the new one - do such requiring just a simple copy&paste that anyone can do.