Related
For those Audiophiles like me if you wanna get Viper4Android to work with RemixOS here is the noob friendly guide;
1) MAKE SURE WHAT'S YOUR BOOT INSTALL : LEGACY OR UEFI (32 AND 64-bit) ; As for mine I have Legacy boot. So it's the guide of as such system. BTW for 64-bit system please see this awesome guide made by @electrikjesus
http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
2) For Legacy boot of RemixOS boot installs (32 & 64 bit) using MBR from Jide's Installer (NON-UEFI)
You will want to make sure you can view hidden and system files in Explorer options, Once you do that, travel to C:\RemixOS (or where yo installed it) and using Notepad++ or your code editor of choice, find and open the menu.lst file. Then add a second entry containing the REMOUNT_RW=1 entry like you see below:
Code:
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 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
title Resident mode - RW enabled
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1 initrd /RemixOS/initrd.img
boot
3) Once you are done, you can reboot, and choose the entry you added. It will then extract the system.sfs file to a system_dev.img, and mount it as RW for you. Once booted, go to /system partition (myself use Root explorer, it's personal choice) and you can toggle Mount R/W to R/O and lets see Supersu enabled you to make change any file in /system. If succeeded then nobody can stop you lol!
4) Now turn to Viper things , I personally use ARISE Viper4Android (it has a good reputation and large fan based forum, just see it) sound systems http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
download stable Exodus or Leviticus 1.3 or Numbers.
5) Now extratct the (say Numbers) zip file and see there is a Numbers folder (in case of Exodus or Leviticus it's pretty straight forward, you will see system folder) inside. Now copy system folder directly into /system while Make sure it's Mounted as R/O.
In case of Numbers only, If copy is succeeded then go to the customize folder and extract app and vendor folder. Rename the app folder as ViPER4Android_FX_A4.x and put it to /system/priv-app.
6) (*It's an optional step for Numbers only*) Now put the vendor to /system and merge it. When everything is installed there'll be /vendor in root, alongside /system, but it will be a symlink to /system/vendor.
** A symlink is symbolic link, it's basically a way for the file system to protect files or in this case be universally compatible because some phones have a dedicated vendor partition that would normally conflict with ARISE vendor if it wasn't symlinked, since it is it just knows the contents are within the linked directory and can display them as if they were, often with different permissions etc. **
7) Last but not the least, finally tap the ViPER4Android_FX_A4.x.apk inside priv-app folder and install it to sdcard. Open it and let's see if it requires driver update, Bang! you are done. V4A is in your system, now all you need is to reboot and see V4A is processing like shown in the picture.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Play your favorite music player and load a profile of your choice (from the extra folder in) in V4A to see what's the difference in SQ. Check it by enabling Master Power on/off. Make sure UI setting as Expert.
Finally to @Ventricle and @ephexxis , I owe to you guys and thanks to @guitardedhero and his ARISE team for this awesome mode and to @electrikjesus for his REMOUNT_RW=1 method to achieve R/W & true root in RemixOS.
Fly with ARISE!
ranaxda200 said:
For those Audiophiles like me if you wanna get Viper4Android to work with RemixOS here is the noob friendly guide;
1) MAKE SURE WHAT'S YOUR BOOT INSTALL : LEGACY OR UEFI (32 AND 64-bit) ; As for mine I have Legacy boot. So it's the guide of as such system. BTW for 64-bit system please see this awesome guide made by @electrikjesus
http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
2) For Legacy boot of RemixOS boot installs (32 & 64 bit) using MBR from Jide's Installer (NON-UEFI)
You will want to make sure you can view hidden and system files in Explorer options, Once you do that, travel to C:\RemixOS (or where yo installed it) and using Notepad++ or your code editor of choice, find and open the menu.lst file. Then add a second entry containing the REMOUNT_RW=1 entry like you see below:
3) Once you are done, you can reboot, and choose the entry you added. It will then extract the system.sfs file to a system_dev.img, and mount it as RW for you. Once booted, go to /system partition (myself use Root explorer, it's personal choice) and you can toggle Mount R/W to R/O and lets see Supersu enabled you to make change any file in /system. If succeeded then nobody can stop you lol!
4) Now turn to Viper things , I personally use ARISE Viper4Android (it has a good reputation and large fan based forum, just see it) sound systems http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
download stable Exodus or Leviticus 1.3 and if you are an adventerous audiophile like Me, then use Latest Testing Sound Systems (like Numbers now).
5) Now extratct the (say Numbers) zip file and see there is a Numbers folder inside. Now copy all the contents directly into /system while make sure it's Mounted as R/O. If copy succeeded then go to the customize folder and extract app and vendor folder. Rename the app folder as ViPER4Android_FX_A4.x and put it to /system/priv-app and put the vendor to /system and merge it. When everything is installed there'll be /vendor in root, alongside /system, but it will be a symlink to /system/vendor. This is so that for those with an actual vendor partition so it's importatnt.
6) Last but not the least, finally tap the ViPER4Android_FX_A4.x.apk and install it to sdcard. Open it and let's see if it requires driver update, Bang! you are done. V4A is in your system, now all you need is to reboot and see V4A is processing like shown in the picture.
Play your favorite music player and load a profile of your choice (from the extra folder in) in V4A to see what's the difference in SQ. Check it by enabling Master Power on/off. Make sure UI setting as Expert.
Finally to @Ventricle and @ephexxis , I owe to you guys and thanks to @guitardedhero and his ARISE team for this awesome mode and to @electrikjesus for his REMOUNT_RW=1 method to achieve R/W & true root in RemixOS.
Fly with ARISE!
Click to expand...
Click to collapse
In extracted files I see only extras, leviticus and META-INF folders. I don't see a customize folder
There are a priv-app and vendor inside the (in my case) leviticus folder
lollyjay said:
In extracted files I see only extras, leviticus and META-INF folders. I don't see a customize folder
Click to expand...
Click to collapse
You downloaded leviticus 1.3 guess. It has no customize folder. It's in new Testing Numbers edition. I would suggest Numbers 0.9.8.7 zip. It's fine
Is it possible to make it systemless?
Sent from my Moto G using XDA Labs
OK QUESTIONS ARE ENCLOSED BY <<<>>>
4) Now turn to Viper things , I personally use ARISE Viper4Android (it has a good reputation and large fan based forum, just see it) sound systems http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
download stable Exodus or Leviticus 1.3 and if you are an adventerous audiophile like Me, then use Latest Testing Sound Systems (like Numbers now). <<<SINCE YOU BASE YOUR DIRECTIONS ON NUMBERS THEN ONLY SUGGEST NUMBERS OTHERS DO NOT HAVE THE SAME SUBFOLDERS>>>
5) Now extratct the (say Numbers) zip file and see there is a Numbers folder inside. Now copy all the contents<<<COPY THE CONTENTS, OR THE FOLDER? >>>directly into /system while make sure it's Mounted as R/O. If copy succeeded then go to the customize folder and extract app and vendor folder. Rename the app folder as ViPER4Android_FX_A4.x and put it to /system/priv-app and put the vendor to /system and merge it<<<WHAT DO YOU MEAN BY MERGE?>>>. When everything is installed there'll be /vendor in root, alongside /system, but it will be a symlink to /system/vendor.<<<MOST OF US DON'T KNOW WHAT YOU MEAN>>>This is so that for those with an actual vendor partition so it's importatnt.
6) Last but not the least, finally tap the ViPER4Android_FX_A4.x.apk<<<DO YOU MEAN THE ONE IN THE /SYSTEM/PRIV-APP/? >>>and install it to sdcard. Open it and let's see if it requires driver update, Bang! you are done. V4A is in your system, now all you need is to reboot and see V4A is processing like shown in the picture.
lollyjay said:
OK QUESTIONS ARE ENCLOSED BY <<<>>>
4) Now turn to Viper things , I personally use ARISE Viper4Android (it has a good reputation and large fan based forum, just see it) sound systems http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
download stable Exodus or Leviticus 1.3 and if you are an adventerous audiophile like Me, then use Latest Testing Sound Systems (like Numbers now). <<<SINCE YOU BASE YOUR DIRECTIONS ON NUMBERS THEN ONLY SUGGEST NUMBERS OTHERS DO NOT HAVE THE SAME SUBFOLDERS>>>
5) Now extratct the (say Numbers) zip file and see there is a Numbers folder inside. Now copy all the contents<<<COPY THE CONTENTS, OR THE FOLDER? >>>directly into /system while make sure it's Mounted as R/O. If copy succeeded then go to the customize folder and extract app and vendor folder. Rename the app folder as ViPER4Android_FX_A4.x and put it to /system/priv-app and put the vendor to /system and merge it<<<WHAT DO YOU MEAN BY MERGE?>>>. When everything is installed there'll be /vendor in root, alongside /system, but it will be a symlink to /system/vendor.<<<MOST OF US DON'T KNOW WHAT YOU MEAN>>>This is so that for those with an actual vendor partition so it's importatnt.
6) Last but not the least, finally tap the ViPER4Android_FX_A4.x.apk<<<DO YOU MEAN THE ONE IN THE /SYSTEM/PRIV-APP/? >>>and install it to sdcard. Open it and let's see if it requires driver update, Bang! you are done. V4A is in your system, now all you need is to reboot and see V4A is processing like shown in the picture.
Click to expand...
Click to collapse
OK ANSWERS ARE ENCLOSED BY **
*4)Good point. I'll re-edit in the OP, Leviticus and exodus has 'system' folders that needs to be extracted to /system patition, then no need to extract 'app' from customize as there's already priv-app in that folder. But since Numbers has been officially initial released from today I would rather suggest to try it.*
*5)copy the contents is right, means everything including ARISE version info.text to be copied to /system. It's current version info helpful for future update. Merging means merge the contents of /vendor with the existing system contents. Vendor in /customize is so that /customize/vendor will go to /system/vendor or /vendor depending on the device. As far I know symlink to /system/vendor was written to mitigate the TWRP 7 error but as this is RemixOS I'll take it as optional. :good:*
*6) As I told in exodus and leviticus there's already priv-app in the /system folder. *
Just let me know if everything goes well or not. Enjoy.
Aguys said:
Is it possible to make it systemless?
Click to expand...
Click to collapse
No idea about system less v4a right now. BTW the main difference between system less and system, besides partition, is that thise sound system files will be symlinked (symbolic link) to /system, those are files that don't exist in /system. The only exception being audio_effect.conf, which will be moved to data/media/0 so that the sound system's audio_effect.conf will be symlinked.
BTW IMO /system installation is rather better to enjoy the fuller sound quality.
OP is updated. Symlink and other regular stuffs are clearly explained
I will try this ASAP!
This gives a life to my horrible sound driver on Linux
??
modaifallah said:
I will try this ASAP!
This gives a life to my horrible sound driver on Linux
??
Click to expand...
Click to collapse
Make sure you Remount system RW to RO using step by step jide's guide( link in OP) for Linux and download following ARISE NUMBERS (official stable release from Today). Enjoy :good:
https://www.androidfilehost.com/?w=files&flid=97426
it's possible using viper without set selinux permission?
ulum.misbahul said:
it's possible using viper without set selinux permission?
Click to expand...
Click to collapse
Selinux is disabled for this ROM mate. U may check
Code#
su
#getenforce
ranaxda200 said:
For those Audiophiles like me if you wanna get Viper4Android to work with RemixOS here is the noob friendly guide;
1) MAKE SURE WHAT'S YOUR BOOT INSTALL : LEGACY OR UEFI (32 AND 64-bit) ; As for mine I have Legacy boot. So it's the guide of as such system. BTW for 64-bit system please see this awesome guide made by @electrikjesus
http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
2) For Legacy boot of RemixOS boot installs (32 & 64 bit) using MBR from Jide's Installer (NON-UEFI)
You will want to make sure you can view hidden and system files in Explorer options, Once you do that, travel to C:\RemixOS (or where yo installed it) and using Notepad++ or your code editor of choice, find and open the menu.lst file. Then add a second entry containing the REMOUNT_RW=1 entry like you see below:
Code:
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 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
title Resident mode - RW enabled
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1 initrd /RemixOS/initrd.img
boot
3) Once you are done, you can reboot, and choose the entry you added. It will then extract the system.sfs file to a system_dev.img, and mount it as RW for you. Once booted, go to /system partition (myself use Root explorer, it's personal choice) and you can toggle Mount R/W to R/O and lets see Supersu enabled you to make change any file in /system. If succeeded then nobody can stop you lol!
4) Now turn to Viper things , I personally use ARISE Viper4Android (it has a good reputation and large fan based forum, just see it) sound systems http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
download stable Exodus or Leviticus 1.3 or Numbers.
5) Now extratct the (say Numbers) zip file and see there is a Numbers folder (in case of Exodus or Leviticus it's pretty straight forward, you will see system folder) inside. Now copy system folder directly into /system while Make sure it's Mounted as R/O.
In case of Numbers only, If copy is succeeded then go to the customize folder and extract app and vendor folder. Rename the app folder as ViPER4Android_FX_A4.x and put it to /system/priv-app.
6) (*It's an optional step for Numbers only*) Now put the vendor to /system and merge it. When everything is installed there'll be /vendor in root, alongside /system, but it will be a symlink to /system/vendor.
** A symlink is symbolic link, it's basically a way for the file system to protect files or in this case be universally compatible because some phones have a dedicated vendor partition that would normally conflict with ARISE vendor if it wasn't symlinked, since it is it just knows the contents are within the linked directory and can display them as if they were, often with different permissions etc. **
7) Last but not the least, finally tap the ViPER4Android_FX_A4.x.apk inside priv-app folder and install it to sdcard. Open it and let's see if it requires driver update, Bang! you are done. V4A is in your system, now all you need is to reboot and see V4A is processing like shown in the picture.
View attachment 3846678
Play your favorite music player and load a profile of your choice (from the extra folder in) in V4A to see what's the difference in SQ. Check it by enabling Master Power on/off. Make sure UI setting as Expert.
Finally to @Ventricle and @ephexxis , I owe to you guys and thanks to @guitardedhero and his ARISE team for this awesome mode and to @electrikjesus for his REMOUNT_RW=1 method to achieve R/W & true root in RemixOS.
Fly with ARISE!
Click to expand...
Click to collapse
in the screenshot you posted..
the neon status is not enabled then how you are saying its working
ajaikumarnadar said:
For those Audiophiles like me if you wanna get Viper4Android to work with RemixOS here is the noob friendly guide;
1) MAKE SURE WHAT'S YOUR BOOT INSTALL : LEGACY OR UEFI (32 AND 64-bit) ; As for mine I have Legacy boot. So it's the guide of as such system. BTW for 64-bit system please see this awesome guide made by @electrikjesus
http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
2) For Legacy boot of RemixOS boot installs (32 & 64 bit) using MBR from Jide's Installer (NON-UEFI)
You will want to make sure you can view hidden and system files in Explorer options, Once you do that, travel to C:\RemixOS (or where yo installed it) and using Notepad++ or your code editor of choice, find and open the menu.lst file. Then add a second entry containing the REMOUNT_RW=1 entry like you see below:
in the screenshot you posted..
the neon status is not enabled then how you are saying its working
Click to expand...
Click to collapse
Neon is a ARM instruction for more efficient processing. It's for x86 architecture so it's not needed.
ranaxda200 said:
For those Audiophiles like me if you wanna get Viper4Android to work with RemixOS here is the noob friendly guide;
1) MAKE SURE WHAT'S YOUR BOOT INSTALL : LEGACY OR UEFI (32 AND 64-bit) ; As for mine I have Legacy boot. So it's the guide of as such system. BTW for 64-bit system please see this awesome guide made by @electrikjesus
http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
2) For Legacy boot of RemixOS boot installs (32 & 64 bit) using MBR from Jide's Installer (NON-UEFI)
You will want to make sure you can view hidden and system files in Explorer options, Once you do that, travel to C:\RemixOS (or where yo installed it) and using Notepad++ or your code editor of choice, find and open the menu.lst file. Then add a second entry containing the REMOUNT_RW=1 entry like you see below:
Code:
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 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
title Resident mode - RW enabled
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1 initrd /RemixOS/initrd.img
boot
3) Once you are done, you can reboot, and choose the entry you added. It will then extract the system.sfs file to a system_dev.img, and mount it as RW for you. Once booted, go to /system partition (myself use Root explorer, it's personal choice) and you can toggle Mount R/W to R/O and lets see Supersu enabled you to make change any file in /system. If succeeded then nobody can stop you lol!
4) Now turn to Viper things , I personally use ARISE Viper4Android (it has a good reputation and large fan based forum, just see it) sound systems http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
download stable Exodus or Leviticus 1.3 or Numbers.
5) Now extratct the (say Numbers) zip file and see there is a Numbers folder (in case of Exodus or Leviticus it's pretty straight forward, you will see system folder) inside. Now copy system folder directly into /system while Make sure it's Mounted as R/O.
In case of Numbers only, If copy is succeeded then go to the customize folder and extract app and vendor folder. Rename the app folder as ViPER4Android_FX_A4.x and put it to /system/priv-app.
6) (*It's an optional step for Numbers only*) Now put the vendor to /system and merge it. When everything is installed there'll be /vendor in root, alongside /system, but it will be a symlink to /system/vendor.
** A symlink is symbolic link, it's basically a way for the file system to protect files or in this case be universally compatible because some phones have a dedicated vendor partition that would normally conflict with ARISE vendor if it wasn't symlinked, since it is it just knows the contents are within the linked directory and can display them as if they were, often with different permissions etc. **
7) Last but not the least, finally tap the ViPER4Android_FX_A4.x.apk inside priv-app folder and install it to sdcard. Open it and let's see if it requires driver update, Bang! you are done. V4A is in your system, now all you need is to reboot and see V4A is processing like shown in the picture.
View attachment 3846678
Play your favorite music player and load a profile of your choice (from the extra folder in) in V4A to see what's the difference in SQ. Check it by enabling Master Power on/off. Make sure UI setting as Expert.
Finally to @Ventricle and @ephexxis , I owe to you guys and thanks to @guitardedhero and his ARISE team for this awesome mode and to @electrikjesus for his REMOUNT_RW=1 method to achieve R/W & true root in RemixOS.
Fly with ARISE!
Click to expand...
Click to collapse
what about dolby atmos or dolby digital for remix os ? any possibilities ?
good work bro.. for bringing viper installation tutorial for remix os..
i just install it, and it sounds not too good. There is no low tons(bass) only high, even if i boost bass to max i hear only small change. I tryed exodus and numbers 3,5 and imhave same problem.
Second thing. Installing this mods corrupting my MBR and i can't boot to windows, only remix os
any ideas how to fix
hello
I have 4 operating system on my machine, and 3 of them read bios clock as UTC, while remix read it as localtime.
my question is, can I tweak something on remix -instead of the other 3- to make it read bios clock as UTC?
rheezid said:
hello
I have 4 operating system on my machine, and 3 of them read bios clock as UTC, while remix read it as localtime.
my question is, can I tweak something on remix -instead of the other 3- to make it read bios clock as UTC?
Click to expand...
Click to collapse
i am in the same boat none of my other use localtime
open console alt-f1 and type
Code:
setprop persist.rtc_local_time 0
Maromi said:
open console alt-f1 and type
Code:
setprop persist.rtc_local_time 0
Click to expand...
Click to collapse
it works, but not as what I expected
what I got after running the code: remix time is always UTC upon reboot, but will change to network time when connected to the internet. This change doesn't change the bios time, so it's not a big deal as it won't conflict with my other OS then.
but what I expect is, for remix to read bios time as UTC and then naturally adjust it's clock to my localtime, just like other OS.
but I guess this solved the conflict
don't work for me
z750leovince said:
don't work for me
Click to expand...
Click to collapse
Did you reset the clock back to utc?
its ok...when shut down and restart my computer, has work
thanks
Read the title.
Flashfire can't seem to work.
Hope you can help me.
vinnce143 said:
Read the title.
Flashfire can't seem to work.
Hope you can help me.
Click to expand...
Click to collapse
Obviously you can't use flashfire as RemixOS doesn't have and can't exactly use a recovery.img
What would you need Magisk for? I did try a while ago to install it manually but that didn't work... I might try again as I know slight more about how it works; but can't really see the benefit of it on Remix.
benefit of magisk on Remix OS:
be rooted but able to quickly and easily unmount root for apps that use safetynet, such as pokemon go.
trevorcobb said:
benefit of magisk on Remix OS:
be rooted but able to quickly and easily unmount root for apps that use safetynet, such as pokemon go.
Click to expand...
Click to collapse
I'll take another look but I don't think RemixOS would pass safety net, regardless of magisk.
And I'm not sure why anyone would want to play Pokemon GO on a PC/tablet
HypoTurtle said:
I'll take another look but I don't think RemixOS would pass safety net, regardless of magisk.
And I'm not sure why anyone would want to play Pokemon GO on a PC/tablet
Click to expand...
Click to collapse
you make a good point about passing safetynet even with magisk installed and functional.
people play Pokemon Go on a PC/Tablet by using a GPS location spoofer, which is usually accompanied by an Xposed module that hides that mock location is turned on, so they don't get banned by Niantic. this enables people to "walk" around with a little on-screen GPS. my interest is because I have Nougat on my N6P and there is no Xposed for Nougat yet.
trevorcobb said:
you make a good point about passing safetynet even with magisk installed and functional.
people play Pokemon Go on a PC/Tablet by using a GPS location spoofer, which is usually accompanied by an Xposed module that hides that mock location is turned on, so they don't get banned by Niantic. this enables people to "walk" around with a little on-screen GPS. my interest is because I have Nougat on my N6P and there is no Xposed for Nougat yet.
Click to expand...
Click to collapse
I have just now made a ramdisk/magisk.img for magisk with 64bit 3.0.205.
Only done the magisk part (no magisk SU or xposed yet)
Screenshot attached - using stock ro system (system.sfs). Essentially that would be the limit of ro system; I could add a magisk SU and have the magisk app claim proper root installed but all disabling root would do is revert back to the stock com.android.setting su
To use it properly I'd say you would need to unroot system:
boot with REMOUNT_RW=1
Install SuperSU and let it replace com.android.settings su
Unroot with SuperSU
Then probably optionally to convert system_dev.img to system.sfs to make it ro again
@trevorcobb the selinux might be an issue with SafetyNet - see if you can boot without that added to grub {gonna check on mine but doubt it'll boot}
My point about Pokemon Go is that there more/better apps than that if you don't play it properly with GPS; but I guess that's just the orienteer in me...
I'll post a build of magisk with SU and Xposed added {it'll be up at least tomorrow}. Install will be the similar to Systemless SU/xposed [a modified ramdisk and a /data/magisk.img file]
UPDATE phh superuser added to magisk which has turned root off {blocks com.android.settings} - but can't seem to install phh's supersu apk; so stuck unrooted {ALT&F1 still has su but it uses phh's su now}. Will need to recheck with the x86 version.
UPDATE2 not going to get anywhere with phh due to the the superuser baked into settings; going with SuperSU should be fine - it just means another .img is needed.
UPDATE3 Having a bit more trouble with this. Tried Magisk; Magisk superSU [essentially just Systemless-SU] and Magisk xposed but can't get xposed to activate. Will try with Magisk, SuperSU and Systemless xposed - but don't know if there is actually any benefit here [would need an updated x86_64 xposed version for suhide to work]
HypoTurtle said:
I have just now made a ramdisk/magisk.img for magisk with 64bit 3.0.205.
Only done the magisk part (no magisk SU or xposed yet)
...
I'll post a build of magisk with SU and Xposed added {it'll be up at least tomorrow}. Install will be the similar to Systemless SU/xposed [a modified ramdisk and a /data/magisk.img file]
Click to expand...
Click to collapse
holy chit! thanks so much!!
I am jumping in to follow along.....for the record I am using this solely to play Pokemon Go with my son.
I modify initrd.img，use /mnt/$SRC/su folder，and mount su/sbin、su/init.rc，needn't modify ramdisk.img ，I edit more su/sbin/launch_daemonsu.sh ，delete mount img .
about “magisk”，I just edit su/init.rc，symlink su /magisk，I edit more /su/sbin/magic_mask.sh ，delete mount img .
youling257 said:
I modify initrd.img，use /mnt/$SRC/su folder，and mount su/sbin、su/init.rc，needn't modify ramdisk.img ，I edit more su/sbin/launch_daemonsu.sh ，delete mount img .
about “magisk”，I just edit su/init.rc，symlink su /magisk，I edit more /su/sbin/magic_mask.sh ，delete mount img .
Click to expand...
Click to collapse
@youling257 Just to clear up anyone elses confusion... you are running on a ext4 partition, right?
The issue is more with the xposed version. For this to be of any benefit over systemless, you`d need suhide to work, which needs v86.2 and we don`t have a version for x86_64, there is one for x86 so I`ll try and get around to making a x86 magisk.img I already have modified the installer script for it.
HypoTurtle said:
@youling257 Just to clear up anyone elses confusion... you are running on a ext4 partition, right?
Click to expand...
Click to collapse
please see this screenshot，i use f2fs partition
trevorcobb said:
holy chit! thanks so much!!
Click to expand...
Click to collapse
youling257 said:
I modify initrd.img，use /mnt/$SRC/su folder，and mount su/sbin、su/init.rc，needn't modify ramdisk.img ，I edit more su/sbin/launch_daemonsu.sh ，delete mount img .
about “magisk”，I just edit su/init.rc，symlink su /magisk，I edit more /su/sbin/magic_mask.sh ，delete mount img .
Click to expand...
Click to collapse
Mind doing a walk through for the less genisus in the group.
laserspeeddemon said:
Mind doing a walk through for the less genisus in the group.
Click to expand...
Click to collapse
I am sorry if this is annoying, and please don't hold any ill towards me for this, however genius in plural is genii (I had also thought that it is geniuses before I had learned this a few years ago).
moriel5 said:
I am sorry if this is annoying, and please don't hold any ill towards me for this, however genius in plural is genii (I had also thought that it is geniuses before I had learned this a few years ago).
Click to expand...
Click to collapse
In this usage it is actually geniuses, if it was the original Latin use [to refer to a genie/jinn] the plural would be genii but the meaning of intellect is old English, so the plural is geniuses...
Any way what @youling257 did was take the changed files from the ramdisk that would be made to run magisk and add them to another folder in his RemixOS folder along with what would be the contents of magisk.img and had the initrd.img mount them where they would originally be. This can be done using a folder instead of an .img as youling257 is using a linux partition [ext4/f2fs] with fat/ntfs you can't do this with a folder but could with a .img
HypoTurtle said:
This can be done using a folder instead of an .img as youling257 is using a linux partition [ext4/f2fs] with fat/ntfs you can't do this with a folder but could with a .img
Click to expand...
Click to collapse
of course . ext4/f2fs , mount /mnt/$SRC/su folder on /android/su , /android/magisk link to /android/su ; ntfs/fat , mount /mnt/$SRC/su.img on /android/su , /android/magisk link to /android/su .
needn't /android/data/su.img and magisk.img .
moriel5 said:
I am sorry if this is annoying, and please don't hold any ill towards me for this, however genius in plural is genii (I had also thought that it is geniuses before I had learned this a few years ago).
Click to expand...
Click to collapse
HypoTurtle said:
In this usage it is actually geniuses, if it was the original Latin use [to refer to a genie/jinn] the plural would be genii but the meaning of intellect is old English, so the plural is geniuses...
Any way what @youling257 did was take the changed files from the ramdisk that would be made to run magisk and add them to another folder in his RemixOS folder along with what would be the contents of magisk.img and had the initrd.img mount them where they would originally be. This can be done using a folder instead of an .img as youling257 is using a linux partition [ext4/f2fs] with fat/ntfs you can't do this with a folder but could with a .img
Click to expand...
Click to collapse
First, I'm not annoyed, I was tickled.
Second you're both are wrong as I simply typo'ed "genius." When I said "less than genius" this was an adjective referring to a group of people using a noun. When applying a adjective-noun to a noun, the adjective-noun is singular.
youling257 said:
of course . ext4/f2fs , mount /mnt/$SRC/su folder on /android/su , /android/magisk link to /android/su ; ntfs/fat , mount /mnt/$SRC/su.img on /android/su , /android/magisk link to /android/su .
needn't /android/data/su.img and magisk.img .
Click to expand...
Click to collapse
I was going to do exactly that a few months ago after I got the systemless SU setup done. Does the SU toggle on/off properly for you with Magisk?
Are you running this on CM13 or N? If CM13 have you tried adding xposed to it - I haven't gotten magisk xposed working on x86_64 - I probably could just use the systemless-SU files though.
@laserspeeddemon, I know you typo'd, that's why I didn't quote your post
HypoTurtle said:
I was going to do exactly that a few months ago after I got the systemless SU setup done. Does the SU toggle on/off properly for you with Magisk?
Are you running this on CM13 or N? If CM13 have you tried adding xposed to it - I haven't gotten magisk xposed working on x86_64 - I probably could just use the systemless-SU files though.
@laserspeeddemon, I know you typo'd, that's why I didn't quote your post
Click to expand...
Click to collapse
I modified initrd.img and use su folder ，two month ago，July 22nd ；I first tried magisk link to su ，magisk v2，the first ten days of August .
these two month，I used Chainfire supersu and my system less idea on 6.0 and 7.0 ; the first ten days of August ，your idea /su/xpo，I modifed rovo89 xposed x86 v86 app_process ； the x86_64 xposed，we only has MIUI x86_64 v85 June，we still use /su/xpo . I didn't know magisk too much，I didn't try magisk in September .
about xposed system less，why we need topjohnwu magisk method ? why we use his ?
youling257 said:
I modified initrd.img and use su folder ，two month ago，July 22nd ；I first tried magisk link to su ，magisk v2，the first ten days of August .
these two month，I used Chainfire supersu and my system less idea on 6.0 and 7.0 ; the first ten days of August ，your idea /su/xpo，I modifed rovo89 xposed x86 v86 app_process ； the x86_64 xposed，we only has MIUI x86_64 v85 June，we still use /su/xpo . I didn't know magisk too much，I didn't try magisk in September .
about xposed system less，why we need topjohnwu magisk method ? why we use his ?
Click to expand...
Click to collapse
The only reason for magisk xposed here would be for PokemonGo to bypass the SafetyNet check that they added. I couldn`t get phh to work with Magisk as there is already a superuser added to Remix via Settings. Which means 86.2 is needed for suhide which is needed if using superSU.
The benefit of magisk over systemless would be probably with allowing adding files to ro system and modifying ro. entries in build.prop (although that wasn`t working on Remix last I checked).
I`ll try and get around to a simple patcher for this. Had planned on a initrd auto-patcher for sometime as well - for continued ota support.
HypoTurtle said:
The only reason for magisk xposed here would be for PokemonGo to bypass the SafetyNet check that they added. I couldn`t get phh to work with Magisk as there is already a superuser added to Remix via Settings. Which means 86.2 is needed for suhide which is needed if using superSU.
The benefit of magisk over systemless would be probably with allowing adding files to ro system and modifying ro. entries in build.prop (although that wasn`t working on Remix last I checked).
I`ll try and get around to a simple patcher for this. Had planned on a initrd auto-patcher for sometime as well - for continued ota support.
Click to expand...
Click to collapse
menuentry "6.0.1 (DEBUG mode)" {
set DIR=/6.0.1
search --set=root --file /32/kernel
linuxefi /32/kernel root=/dev/ram0 androidboot.hardware=android_x86 DIR=$DIR SRC=$DIR intel_idle.max_cstate=0 i915.enable_psr=0 DEBUG=2
initrdefi /initrd.img
}
menuentry "remixos 64" {
set DIR=/remixos
search --set=root --file /64/kernel
linuxefi /64/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 DIR=$DIR SRC=$DIR intel_idle.max_cstate=0
initrdefi /initrd.img
}
menuentry "cm13 (DEBUG mode)" {
set DIR=/cm13
search --set=root --file /64/kernel
linuxefi /64/kernel root=/dev/ram0 androidboot.hardware=android_x86_64 DIR=$DIR SRC=$DIR intel_idle.max_cstate=0 DEBUG=2
initrdefi /initrd.img
}
I use the same kernel、modules、initrd.img with 6.0、cm13、remixos ; kernel 、initrd.img on fat32/esp partition .
auto mount f2fs partition on /mnt , auto mount /mnt/modules ; /mnt/6.0.1 , /mnt/cm13 , /mnt/remixos， if ota，just update /mnt/remixos files
In this thread, you can let me and the Remix Team know what issues you are having with your Nvidia-based systems!
Before you report any bugs, check this thread by my friend @Vioner : http://forum.xda-developers.com/remix/remix-os/solution-problems-booting-remix-os-dual-t3466027
Also, don't forget to send full bug reports here too, here! Made by Jide!
Notebook Dell XPS 15 Touch (9530)
Notebook Dell XPS 15 Touch (9530)
INTEL HD + NVIDIA GPUs (Nvidia GeForce GT 750M graphics card)
Remix OS for PC 3.0.205
Do not boot with option
nouveau.modeset=0
nomodeset
boot only with
androidboot.swrast=1 --> drawbacks - low performance.
I was able to boot with no additional option on release Remix OS for PC 3.0.202.
Hope you can fix soon.
I have a Dell m3800 and am seeing a similar issue. My computer has the Intel HD + Nvidia (Quadro 1100m). The performance is horrible. I cant even play a youtube video because both the audio and video are studdering so badly...
maxiclo said:
Notebook Dell XPS 15 Touch (9530)
INTEL HD + NVIDIA GPUs (Nvidia GeForce GT 750M graphics card)
Remix OS for PC 3.0.205
Do not boot with option
nouveau.modeset=0
nomodeset
boot only with
androidboot.swrast=1 --> drawbacks - low performance.
I was able to boot with no additional option on release Remix OS for PC 3.0.202.
Hope you can fix soon.
Click to expand...
Click to collapse
Try with:
nouveau.modeset=0 i915.modeset=1
HypoTurtle said:
Try with:
nouveau.modeset=0 i915.modeset=1
Click to expand...
Click to collapse
I
I did try this and the results were pretty strange. During boot, it wound up stuck on the command line. I did an lsmod and noticed that both i915 and nouveau were loaded. I then issued an "rmmod nouveau" from the command line and remix os then continued to boot into the OS. So why would the nouveau module still be loaded even with nouveau.modeset=0 explicitly set?
When inside Remix OS I swithed to the congsole ( using ATL + F1 ) and verified using lsmod that i915 was loaded and nouveau was not. However, I still could not play a video off of youtbe without both the video and the audio being choppy [and unusable at all].
Gtx 980. Works in guest mode. Stay stuck at logo in resident mode .
tailslol said:
Gtx 980. Works in guest mode. Stay stuck at logo in resident mode .
Click to expand...
Click to collapse
How long does it get stuck for? Report back with results from adding "DEBUG=1" to the kernel line.
moman2000 said:
How long does it get stuck for? Report back with results from adding "DEBUG=1" to the kernel line.
Click to expand...
Click to collapse
Stay stuck forever.
Kernel line?
tailslol said:
Stay stuck forever.
Kernel line?
Click to expand...
Click to collapse
Open menu.lst with your favourite text editor (I used Notepad++)
Add this: "DEBUG=1" after "CREATE_DATA_IMG=1"
Make sure the red code is added like this:
Example:
Code:
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 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ DATA= CREATE_DATA_IMG=1[B][COLOR="Red"] DEBUG=1[/COLOR][/B]
initrd /RemixOS/initrd.img
boot
Save and reboot to Remix OS, and report back with any errors you see, you could send an image taken with a phone!
I've tried pretty much all of the combinations that I can think of. I can boot fine either with the software rendering flag set or with the nvidia card disabled (usually via a "rmmod mouveau" before remix completes boot.) However, nothing that I do enables youtube or any other video app to play smothly. This is driving me nuts as otherwise Remix seems really aweomse and I want to use it
As a related question, is there a way to gain root access in the command line so that we can do things like edit /system/etc/modules.blacklist ?
For reference, this system runs linux normally so I know that the hardware does work fine when blacklisting the nouveau (and nvidia) drivers. [Although I use Bumblebee for normal operation, which again is typically only using the Intel HD video card]
@HypoTurtle @Adaptive13 I've talked to @masaykh about these nomodeset and .modeset=0 problems - it appears that in Marshmallow they moved driver modules from initrd to system and because of that parameters like nomodeset or nouveau.modeset are not working. I'm not a 100% sure of that, but it seems a quite legit theory since trying all kinds of modeset combinations doesn't disable the driver modules. I've already talked about this with Remix product manager and they're working on it.
Vioner said:
@HypoTurtle @Adaptive13 I've talked to @masaykh about these nomodeset and .modeset=0 problems - it appears that in Marshmallow they moved driver modules from initrd to system and because of that parameters like nomodeset or nouveau.modeset are not working. I'm not a 100% sure of that, but it seems a quite legit theory since trying all kinds of modeset combinations doesn't disable the driver modules. I've already talked about this with Remix product manager and they're working on it.
Click to expand...
Click to collapse
@Vioner Thanks for following up on this. Please keep us posted on when a workaround will be available.
My Nvidia works well but has wrong thermal configurations making the display flash. I fix it by "echo 125000 > /sys/class/hwmon/hwmon1/temp1_max, temp1_crit, temp1_emergency" but this has to been done from the root terminal after every boot manually. I can automate it by adding the command to init.sh but this breaks OTA updating.
Card: Nvidia GeForce 8200 mg.
Vioner said:
@HypoTurtle @Adaptive13 I've talked to @masaykh about these nomodeset and .modeset=0 problems - it appears that in Marshmallow they moved driver modules from initrd to system and because of that parameters like nomodeset or nouveau.modeset are not working. I'm not a 100% sure of that, but it seems a quite legit theory since trying all kinds of modeset combinations doesn't disable the driver modules. I've already talked about this with Remix product manager and they're working on it.
Click to expand...
Click to collapse
Don't think drivers have ever been in initrd/ramdisk with Ax86 - there's too many drivers [100-150MB] for them to be added; AndroidIA (and some arm ROMS) have drivers in ramdisk as the Android build is device specific. There was a change though with MM-r1 (or whatever it was called) that 203 was rebased on; with modprobe being run differently, loading modules in a different order than before - I guess this could be ignoring grub $cmdline and module blacklisting.
modaifallah said:
My Nvidia works well but has wrong thermal configurations making the display flash. I fix it by "echo 125000 > /sys/class/hwmon/hwmon1/temp1_max, temp1_crit, temp1_emergency" but this has to been done from the root terminal after every boot manually. I can automate it by adding the command to init.sh but this breaks OTA updating.
Card: Nvidia GeForce 8200 mg.
Click to expand...
Click to collapse
You could try systemless to write to a loop-mounted init.sh or use a su.d script. That's what I have to do for my touchscreen & I can OTA by replacing 1 file (ramdisk.img).
Also back on topic you could I suppose loop-mount an empty file over the unwanted module (.ko) so that it doesn't load. I've tried blacklisting modules in newer Ax86 builds and that doesn't seem to work either (via grub and etc/blacklist) - not sure if the loop would be made before the module is loaded so likely be better to physically delete the .ko with a rw system.
Asus N76V: Intel i7-3630QM 2.4Ghz, Intel HD Graphics 4000 + Nvidia Geforce GT 650M.
can only make it works with "nomodeset", otherwise, it's stuck at terminal screen.
@HypoTurtle correct, they weren't in initrd, but the driver modules handling changed. @Adaptive13 we already have a workaround ready. I've updated my dual gpu booting guide, check HERE
Netbook ASUS 1215N
Intel ATOMD525 (Intel HD) + NVIDIA ION2 (Nvidia GT218)
Remix OS for PC 3.0.205
O.S Boot fine without change anything.
O.S it's super smooth but there something wrong with 2D and 3D applications.
1) Youtube HD is working, a bit choppy but it's working.
2) 99% of the games run with VERY slow framerate everything from very simple 2D games to complex 3D games like GTA. (some 2D games runs worse than GTA)
Just to make some examples... Angry Birds run @ 3-4 FPS while GTA SA runs 7-8FPS...
clash of clans is super smooth
tomb raider 1 (i tested lara's house level only) working good at the initial locations, but as soon as you reach the hall it drop from 30 stable FPS to 3-4FPS.
@Vioner As your other guide mentions adding EXTMOD=i915 works! And man does it work great! HD Youtube + audio upscaled to my 4k touchscreen display beautifully! I'm running off of a USB drive but the performance is incredible now. I am very impressed! Thanks!!!!!!!!!!!!!!!!!!! (For others reading this, I have DPI=300 also added to the boot parameters to make things look nice on the high res monitor.
@AuRoN89 that might indicate that you are running the system with software graphics renderer (graphics handled by the CPU). You can try my guide with "nomodeset" or "EXTMOD=i915". It should help.
Like all variables:
XT1650_xx
Short Answer : Yes