Related
This is an (hopefully) updated collection of all roms (not android based, but other linux OS, like ubuntu, archlinux, fedora...) for nexus 7 (grouper and tilapia) available using the MultiROM system.
MultiROM is an amazing hack (I want to thank again its author, Tasssadar) that permits to boot different OS (multiboot) and different android roms. It starts between kernel and rom init, showing a sort of bootloader dialog to choose which system to boot.
It supports installing (and booting, of course) roms to USB drives.
To use MultiROM you need multirom installation zip , a modified TWRP recovery and kernels with kexec support. Relax, is not hard or long to do this.
More information and installation (of MultiROM, recovery and kernels) --> [ MULTIROM ]
PS: I need to specify I coded nothing, my only work was helping with issues, repacking roms, make them work. I want to say thank you to all devs are developing for Nexus 7, I'm doing this because I appreciate their work and I want MultiROM to rise. It deserves to.
HOW TO INSTALL A ROM.
Tasssadar provided also a zip template (see the [ WIKI ] for more info) that is incredibly easy to use.
To install a linux os to sdcard, you just need to download the zip and flash it like a normal update.zip.
It won't replace your internal rom, because it is going to install in /sdcard, not in /system or /data. And it WON'T wipe anything.
Remember that flashing ubuntu or android rom is DIFFERENT from flashing those zips. To flash ubuntu or another android rom you need to use MultiROM menu under ADVANCED voice in recovery (again, see wiki or multirom thread if you need more information).
ROM PACKS.
In the next post I'll share links for rom zips. If you have other zips or if you have built other zips, please share them. They will be (hopefully) added to the list. If not, please pm me. I can't read all posts.
If you want to share a zip, please try it first. I don't know if I'll be able to test everything real-time, and I don't want anyone to see his sdcard erased or strange things like this. MultiROM has a percent of risk, but nobody has lost his data till now. So please share zips consciously.
ROM LIST (DOWNLOADS)
* [NEW] PLASMA ACTIVE 4.0 (20140121)
mirror: http://d-h.st/Khh
old version: https://docs.google.com/file/d/0B9ZvdqAbuJi2blQ0TDgweFFKTlU/edit
description: KDE for embedded devices. Very cool and interesting. 4.0 version is more stable, video codec is working as well. Little slow booting.
* BODHI LINUX 20130109
old version: INITIAL RELEASE
notes: old version passwd for root and armhf user is trustno1 (sorry for that, is my fault. In new release it is again bodhilinux)
description: Ubuntu with E17 (Enlightenment) with mobile GUI. Pretty stable and... veeery fast.
*ArchLinux 20130113-2
old version: -
description: ArchLinux. Simply. Not designed for basic users. Really powerfull, with already packed KDE, Gnome-shell, LXDE, XFCE, Enlightenment environments (and many others probably). Needs testing, and some love, as it's initial release.
*WebOS ALPHA
old version: http://www.mediafire.com/?3m58uuvysxiwypw
description: still in alpha stage, unstable. Interesting project. Needs love.
* [MANUAL INSTALL] Ubuntu Touch Tablet DEVELOPER PREVIEW
old version: -
description: developer preview, android-based, with the new Ubuntu Touch UI.
[NEW] Use MultiROM app to install the latest version in the easiest way
ROMS TO BE PACKED/MADE WORKING:
fedora4nexus7?
PAY ATTENTION: NEW MULTIROM CHANGED THE ROM ZIP STRUCTURE!
NEW STRUCTURE HERE.
I GUESS YOU CAN USE OLD ZIPS, BUT I CAN'T TRY AND IT'S BETTER TO USE NEW METHOD (REPACK NEEDED)
STEPS TO CREATE A NEW ROM ZIP (EASY-WAY):
* first, download the template (reworked by me)
* then, unzip the template, put the root.tar.gz and rom_info.txt inside rom folder (if you don't know what I'm talking about, read again the wiki - link above)
* edit rom name inside of scripts/extract.sh script (it's the only thing you have to edit, unless you want it to do something else, but be careful in that case)
* select the 3 folders (META-INF, rom, scripts) and zip them in a zip called <DISTRONAME>-MultiROM-Installer-<VERSION>.zip (I think it's a good standard, if you don't like simply name it another way, but I reckon that using a standard would be a very good thing)
*when the zip is finished, upload your zip somewhere (I use google drive now, but I hope I'll have my storage sometime in the future) and share the link here. I will add it to the list.
If I don't, pm me.
[EDIT] new packing method for webos available https://github.com/Tasssadar/webos_multirom_packer [/EDIT]
MORE INFORMATION.
PLASMA ACTIVE.
known bugs: https://wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7/PA_Known_Issues
username/password : mer/mer, root/mer
Interesting features : Plays 720p movies full screen with sound and 1080p full screen down scaled with sound.
BODHI LINUX.
known bugs: http://forums.bodhilinux.com/index.php?/forum/40-nexus-7/
username/password: armhf/bodhilinux
useful page (customization, add software, guides): http://wiki.bodhilinux.com/doku.php
ARCHLINUX.
armv7h images: http://os.archlinuxarm.org/os/ (see tegra directory)
username/password: arch/arch, root/root
useful link (bible): https://wiki.archlinux.org/
infos: needs an OTG keyboard or to use "sudo screen /dev/ttyACM0 115200" to connect via usb.
While you are connected you need to configure wifi. I use a script that simply uses iwconfig, wpa_supplicant.conf and dhcpcd to get a wifi connection.
The rest is up to you.
Enlightenment is preinstalled in build 20130113-2.
UBUNTU TOUCH.
infos: use MultiROM Manager app to install it.
GENERAL.
lintz said:
Recomended "fixes" after first install (Mer, Plasma ndr) :
Install custom keyboard (write this comands in terminal start with su and after the password for root by default mer)
1. zypper ar -G http://repo.pub.meego.com/home:/won...wonko:branches:Project:KDE:Trunk:Testing.repo
2. zypper up maliit-active libmaliit-quick
3. killall -9 maliit-server
Update the system (use su and root password first)
zypper ref && zypper up
Install GUI package manager (same here su and root password)
zypper in apper
Click to expand...
Click to collapse
Thanks to lintz for the suggestions.
LATEST HOT NEWS.
-updated with latest Plasma version.
-updated with Ubuntu Touch
-updated with latest Plasma & WEBOS version (repacked for new MultiROM structure)
-updated with Ubuntu Touch Dev Preview
-updated OP with arch infos.
-Making zip for new BodhiLinux version, that now has correct passwd
Code:
bodhilinux
as it should be.
xela92 said:
Making zip for new BodhiLinux version, that now has correct passwd
Code:
bodhilinux
as it should be.
Click to expand...
Click to collapse
thx xela, I'm still having trouble creating a zip with the template. perhaps you could post the steps you took to create the new bodhi release
bonzer2u said:
thx xela, I'm still having trouble creating a zip with the template. perhaps you could post the steps you took to create the new bodhi release
Click to expand...
Click to collapse
Steps how-to done
Later (when upload ends) I'll share Bodhi new version installer link
Nice thread. Can't wait to try some other distro's.
xela92 said:
ROM LIST (DOWNLOADS)
* PLASMA ACTIVE 20130109
old version: -
description: KDE for embedded devices. Very cool and interesting, but still an alpha.
* BODHI LINUX (uploading new version)
old version: INITIAL RELEASE
notes: old version passwd for root and armhf user is trustno1 (sorry for that, is my fault. In new release it is again bodhilinux)
description: Ubuntu with E17 (Enlightenment) with mobile GUI. Pretty stable and... veeery fast.
Click to expand...
Click to collapse
Needs more info.
Add following kategories
Plasma Active
Bugs : https://wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7/PA_Known_Issues
Username passwords : mer/mer, root/mer
Recomended "fixes" after first install :
Install custom keyboard (write this comands in terminal start with su and after the password for root by default mer)
1. zypper ar -G http://repo.pub.meego.com/home:/won...wonko:branches:Project:KDE:Trunk:Testing.repo
2. zypper up maliit-active libmaliit-quick
3. killall -9 maliit-server
Update the system (use su and root password first)
zypper ref && zypper up
Install GUI package manager (same here su and root password)
zypper in apper
Features : Plays 720p movies full screen with sound and 1080p full screen down scaled with sound.
Same thing for Bodhi. But I dont know the detales about it since I don't use it.
PS as it is now this thread feels as a start to a redundant thread to what is written in Tassadars first 3 posts in the MultiRom thread. Better if you focus on the current distros that don't have any "real" maintener here on xda.
I will add those categories later
lintz said:
Needs more info.
Add following kategories
Plasma Active
Bugs : https://wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7/PA_Known_Issues
Username passwords : mer/mer, root/mer
Recomended "fixes" after first install :
Install custom keyboard (write this comands in terminal start with su and after the password for root by default mer)
1. zypper ar -G http://repo.pub.meego.com/home:/won...wonko:branches:Project:KDE:Trunk:Testing.repo
2. zypper up maliit-active libmaliit-quick
3. killall -9 maliit-server
Update the system (use su and root password first)
zypper ref && zypper up
Install GUI package manager (same here su and root password)
zypper in apper
Features : Plays 720p movies full screen with sound and 1080p full screen down scaled with sound.
Same thing for Bodhi. But I dont know the detales about it since I don't use it.
PS as it is now this thread feels as a start to a redundant thread to what is written in Tassadars first 3 posts in the MultiRom thread. Better if you focus on the current distros that don't have any "real" maintener here on xda.
Click to expand...
Click to collapse
thanks
this solved my onscreen keyboard problem (not working over browser) ... now only gui glitches was left (multitasking bar )
xela92 said:
STEPS TO CREATE A NEW ROM ZIP (EASY-WAY):
* first, download the template (reworked by me)
* then, unzip the template, put the root.tar.gz and rom_info.txt inside rom folder (if you don't know what I'm talking about, read again the wiki - link above)
* edit rom name inside of scripts/extract.sh script (it's the only thing you have to edit, unless you want it to do something else, but be careful in that case)
* select the 3 folders (META-INF, rom, scripts) and zip them in a zip called <DISTRONAME>-MultiROM-Installer-<VERSION>.zip (I think it's a good standard, if you don't like simply name it another way, but I reckon that using a standard would be a very good thing)
*when the zip is finished, upload your zip somewhere (I use google drive now, but I hope I'll have my storage sometime in the future) and share the link here. I will add it to the list.
If I don't, pm me.
Click to expand...
Click to collapse
Hi xela,
I understand the process except for creating the 'root.tar.gz' file from a compressed image (.img or .raw) file. Do you need to extract the image file to the /root folder and then recompress with a command similar to:
sudo tar --numeric-owner -zpcf root.tar.gz ./*
Nice Topic, i've tried your first Bodhi Zip and it seems very fast and stable to me. A few bugs, but nothing major.
I'm waiting for the new Version to finish uploading
bonzer2u said:
Hi xela,
I understand the process except for creating the 'root.tar.gz' file from a compressed image (.img or .raw) file. Do you need to extract the image file to the /root folder and then recompress with a command similar to:
sudo tar --numeric-owner -zpcf root.tar.gz ./*
Click to expand...
Click to collapse
I couldn't find out how to mount those IMG files. I thought they were ext4 fs but they aren't. I tried to use dd to flash them on a drive but failure again. So to extract rootfs I install them with standard procedure (Ubuntu) and the repack roofs to tar.gz. It could be useful to find out how to directly extract rootfs, because it's the same method used by Ubuntu. With the difference that Ubuntu uses zsync to permit fast upgrade...!
xela92 said:
I couldn't find out how to mount those IMG files. I thought they were ext4 fs but they aren't. I tried to use dd to flash them on a drive but failure again. So to extract rootfs I install them with standard procedure (Ubuntu) and the repack roofs to tar.gz. It could be useful to find out how to directly extract rootfs, because it's the same method used by Ubuntu. With the difference that Ubuntu uses zsync to permit fast upgrade...!
Click to expand...
Click to collapse
I could never get it mounted as well.... Is this why your having a delay in uploading the new bodhi release?
bonzer2u said:
Hi xela,
I understand the process except for creating the 'root.tar.gz' file from a compressed image (.img or .raw) file. Do you need to extract the image file to the /root folder and then recompress with a command similar to:
sudo tar --numeric-owner -zpcf root.tar.gz ./*
Click to expand...
Click to collapse
If you can get the files from the .img files, you really dont need the zip to install it, just creat a dir with the name for the OS, then inside create a dir called root, then inside extract the .img
For the rom_info.txt file, just make the changes needed and put them on the same dir that ../root is and restart and you should be able to boot form it.
Rafase282 said:
If you can get the files from the .img files, you really dont need the zip to install it, just creat a dir with the name for the OS, then inside create a dir called root, then inside extract the .img
For the rom_info.txt file, just make the changes needed and put them on the same dir that ../root is and restart and you should be able to boot form it.
Click to expand...
Click to collapse
Unfortunately we have been unable to mount/extract anything from the image although it appears it may install via the multirom/ubuntu method
bonzer2u said:
I could never get it mounted as well.... Is this why your having a delay in uploading the new bodhi release?
Click to expand...
Click to collapse
I'm not at home right know, but in 30 minutes I'll post it
shared the latest bodhi linux version get the link in OP
bonzer2u said:
Unfortunately we have been unable to mount/extract anything from the image although it appears it may install via the multirom/ubuntu method
Click to expand...
Click to collapse
I think zip solution is the best and most "standard". When I make a zip I know it will work, because it's the final, multiROM surely compatible, version. And I can test it immediately, fix it, reflash, and try without messing the world up. I think update zips are the most user-friendly way too. But that's only MHO.
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
SailfishOS (SFOS) is a GNU+Linux system using libhybris to leverage Android drivers from LineageOS.
About everything should work (except NFC, no userspace support for now).
You're root and you've SSH, set password in developer-mode settings. Use devel-su like you'd use sudo !
To use/flash SFOS (no wipe needed), you should already be using LineageOS 14.1 20181031 build or newer,
and have booted it at least once (otherwise WLAN problems).
See latest release post for OTA update instructions, or flash ZIP download link.
Warning : flashing zip over previous SFOS install erases it ! So use OTA to avoid that, or use integrated backup app...
Note : SFOS only flashes boot partition and install itself in /data/.stowaways/sailfishos/ so :
you can go back to LineageOS only by flashing the LOS boot image
you can reclaim diskspace used SFOS by removing /data/.stowaways/sailfishos/
Reference Wiki page on merproject.org
Kernel | Device | Vendor source trees
Feeling adventurous ?
This is a SailfishOS community port for the 6045 idol3.
This is not Android (just re-using the lower layers), Android apps can't run on it and there's no support for official-ports-AlienDalvik-emulator.
So please don't ask.
During installation, you'll be asked to create a Jolla account, to have access to basic apps (notes, mediaplayer, documents, etc.).
This is not mandatory (though prefered for the full experience) : should you choose not to register (and even if you do),
you still can install an alternative store using OpenRepos client Storeman
Reserved
Hello, installed version 3, everything works fine, data transfer, wifi, all sensors (including case), location, mtp, calls and SMS. There were only problems with the store, some applications are not installed the first time, you have to install again, and so great work is another alternative for the smartphone, thank you.
andrejchern said:
Hello, installed version 3, everything works fine, data transfer, wifi, all sensors (including case), location, mtp, calls and SMS. There were only problems with the store, some applications are not installed the first time, you have to install again, and so great work is another alternative for the smartphone, thank you.
Click to expand...
Click to collapse
I have installated seilfish os some time ago in my moto g2 and the battery life and boot speed its superior then any version of android ... ?
A very fast, fluid, and consistent UI in this ROM. An interesting one to play with. (However, for my needs, I need the PlayStore apps.)
I now understand how your work on Lineage was a foundation for this one.
I am curious Vknecht, what is your interest in this one?
tess1 said:
A very fast, fluid, and consistent UI in this ROM. An interesting one to play with. (However, for my needs, I need the PlayStore apps.)
I now understand how your work on Lineage was a foundation for this one.
I am curious Vknecht, what is your interest in this one?
Click to expand...
Click to collapse
It's all politics, also it's the system I use daily
some sort of hommage to a french industry of old (1898), rough-rided by financialization (see, can't build idol3 themselves)
fighting planned obsolescence
taking the power back on a device
powering it with an OS independent from GAFAM
having closer to classical GNU+Linux distro, though not totally open in the case of SFOS
Since 2010 I've been a Nokia N900 then N9 user (which ran with Maemo, resp. Meego, predecessors to SailfishOS) until summer 2017 when I got a Xperia X for the SailfishX release. Only ever used Android for a month, until the build-SFOS-for-X documentation was released and dived in the OS-building fun...
At the beginning of 2018 I looked for a cheap and decent french-branded-androphone (2Gb RAM, HD display) with a working LineageOS port and found the idol3 to begin a new SFOS port. It's been a long 8 months journey, where rebuilding LineageOS if only for the patch-level was not much, then also wanted to "upstream" some fixes or upgrades (eg. kernel) I wanted in SFOS...
I started using my idol3 again and I love Sailfish OS as soon as I figure out android apps im gonna use it alot more
Everything work fine, but the double tap to wake up the telephone.
Hi vknecht, great job, how can I contribute (donation) to your work? I've installed everything except Anbox, but I think I'll do it anyway, most of my contacts use Wzap ... Everything works fine except for the double tap to wake up the phone, do you know what it can depend on? Is it a function of hardware or software? With Lineage it worked, with Sailfish no. It's not dramatic, but definitely inconvenient to have to use the power switch every time. Thank you.
Best regard.
Antonio from Italy.
vknecht said:
Feeling adventurous ?
This is a SailfishOS community port for the 6045 idol3.
This is not Android (just re-using the lower layers), Android apps can't run on it* and there's no support for official-ports-AlienDalvik-emulator.
So please don't ask.
It's a systemd-based GNU/Linux with 32bits-userspace system, and about every basis function should work.
You're root, set password in developer-mode settings. Use devel-su like you'd use sudo !
To use/flash SFOS (no wipe needed), you should already be using LineageOS 14.1 20181031 build, and have booted it at least once (otherwise WLAN problems).
During installation, you'll be asked to create a Jolla account, to have access to basic apps (notes, mediaplayer, documents, etc.). This is not mandatory (though prefered for the full experience, for now) : should you choose not to register (and even if you do), you still can install an alternative store using OpenRepos client Storeman
*basic Anbox support was added, but don't count on it for now (plz contribute if you can), it may be broken.
If you really want to try it : (don't just copy/paste, fix the URLs !)
Code:
### As root (devel-su), on the phone via SSH :
# Add mal's Anbox for SFOS repository
ssu ar home_mal_anbox [url]http://repo.merproject.org/obs/home:/mal:/anbox/sailfish_latest_armv7hl/[/url]
pkcon refresh
pkcon install anbox-sailfishos anbox-sailfishos-image-mixed-32-64-bit
rm -f /var/lib/anbox/overlay/system/lib64/libGLESv*
cp /vendor/lib/egl/libEGL_adreno.so /var/lib/anbox/overlay/vendor/lib/egl/
# Install a keyboard APK, eg [url]https://f-droid.org/fr/packages/rkr.simplekeyboard.inputmethod/[/url]
mkdir -p /var/lib/anbox/data/app
cp *apk /var/lib/anbox/data/app
### Networking is broken at the moment... ###
### Comment anbox-bridge.sh lines (ExecStartPre and ExecStopPost) ###
### in /lib/systemd/system/anbox-container-manager.service ###
# Restart Anbox
systemctl restart anbox-container-manager
# There's no "back" button for now
# Run Anbox from app screen again to go back to Anbox app launcher
This is a simultaneous release of SFOS 2.2.1.18 and 3.0.0.8, if you have problem with one version, try the other
SFOS 2.2.1.18
SFOS 3.0.0.8
Sorry no screenshot or video for now, you can find for other devices, looks should be the same.
SailfishOS fir idol3 Wiki page
Kernel | Device | Vendor source trees
Click to expand...
Click to collapse
Any chance of seeing it on the Idol 3 4.7 ? It would give me a good reason to use it again. It's okay if not it's just sad that there's no updated ROM for this version... I could beta test it if you ever do that
zorro_tj said:
Hi vknecht, great job, how can I contribute (donation) to your work? I've installed everything except Anbox, but I think I'll do it anyway, most of my contacts use Wzap ... Everything works fine except for the double tap to wake up the phone, do you know what it can depend on? Is it a function of hardware or software? With Lineage it worked, with Sailfish no. It's not dramatic, but definitely inconvenient to have to use the power switch every time. Thank you.
Click to expand...
Click to collapse
Hello, and thank you for the heads up on dt2w... so I had a look, and found how to enable it
(make sure developer mode is enabled and you've set or checked the password)
Code:
host $ ssh [email protected]
,---
| Sailfish OS 3.0.1.11 (Sipoonkorpi)
'---
[[email protected] ~]$ devel-su
Password:
[[email protected] nemo]# echo 1 > /sys/class/tp_gesture/tp_device/tp_gesture_id
[[email protected] nemo]# printf "[EVDEV]\nKEY_APP_SWITCH=KEY_POWER\n" > /etc/mce/99-doubletap-idol3.ini ; systemctl restart mce
The echo command has to be issued when the screen is on, and each time you reboot, for now (don't know why it's not already set to 1 like in LOS)
The printf and systemctl are only needed once to create the configuration file and restart the service.
Hopefuly you'll see no battery drain, so it can be enabled by default in the future...
For donations, maybe it will be possible later.
h3cat3 said:
Any chance of seeing it on the Idol 3 4.7 ? It would give me a good reason to use it again. It's okay if not it's just sad that there's no updated ROM for this version... I could beta test it if you ever do that
Click to expand...
Click to collapse
One thing I could do is try building LOS 14.1 with idol347 defconfig, but afaik it's not really working.
Otherwise one could follow the SailfishOS HADK using a working CyanogenMod base and I'd be glad to help, but don't have time to start it myself at the moment.
Thanks!
vknecht said:
Hello, and thank you for the heads up on dt2w... so I had a look, and found how to enable it
(make sure developer mode is enabled and you've set or checked the password)
Code:
host $ ssh [email protected]
,---
| Sailfish OS 3.0.1.11 (Sipoonkorpi)
'---
[[email protected] ~]$ devel-su
Password:
[[email protected] nemo]# echo 1 > /sys/class/tp_gesture/tp_device/tp_gesture_id
[[email protected] nemo]# printf "[EVDEV]\nKEY_APP_SWITCH=KEY_POWER\n" > /etc/mce/99-doubletap-idol3.ini ; systemctl restart mce
The echo command has to be issued when the screen is on, and each time you reboot, for now (don't know why it's not already set to 1 like in LOS)
The printf and systemctl are only needed once to create the configuration file and restart the service.
Hopefuly you'll see no battery drain, so it can be enabled by default in the future...
Thanks a lot, it worked! I will pay attention to the the battery drain and will informe you. Just another question: i see your OS version is 3.0.1.11, mine is 3.0.0.8 (Lemmenjoki) is it convenient for me to update it? if yes, in what way? The device is a Idol 3 6045K dual-sim, no external sdcard on board.
Thanks again, greet from Italy.
Click to expand...
Click to collapse
zorro_tj said:
Thanks a lot, it worked! I will pay attention to the the battery drain and will informe you.
Just another question: i see your OS version is 3.0.1.11, mine is 3.0.0.8 (Lemmenjoki) is it convenient for me to update it?
if yes, in what way? The device is a Idol 3 6045K dual-sim, no external sdcard on board.
Thanks again, greet from Italy.
Click to expand...
Click to collapse
You're welcome For now I don't see any drain, let's hope it stays like this.
I found out that the ini file is not necessary if one sets tp_gesture_id to 2, but still have to set this value on boot
and/or find why it's not the same as in LineageOS by default.
3.0.1.11 release for idol3 is still in devel phase, once it's ready (~ one week or so) it will be published in testing phase and then you'll be able to do
OTA through commandline.
One can flash a devel-image, but then can't rely on OTA : will have to re-flash a testing-image or do risky/unsupported repository-switch.
Those are generally built using SailfishOS porters' Gitlab-CI group, latest being the 20190227 devel image
SailfishOS 3.0.1.11 beta3
Backup...
Update using OTA : the integrated graphical updater doesn't work for community ports
Easiest is to install sfos-upgrade either through Storeman or direct RPM dowload.
Flash image : (erases previously installed SailfishOS)
sailfishos-idol3-release-3.0.1.11-20190321-beta3.zip
Changes :
SailfishOS 3.0.1.11 release notes (points specific to officially supported devices don't apply)
Kernel : enabled Yama security module
Enabled doubletap to wake
Sorry, Anbox confirmed to NOT work, have to check required overlayfs support, maybe broken with the kernel updates.
SailfishOS 3.0.1.11 beta3 beta2 Constant reboots, hangs and reboots.
andrejchern said:
SailfishOS 3.0.1.11 beta3 beta2 Constant reboots, hangs and reboots.
Click to expand...
Click to collapse
Sorry to hear that... does it happen regularly/systematically and quite early after boot, or after (somehow) extensive usage, especially browser ?
I supposed you tried with flashing as well as OTA ?
A known cause for reboot is fixed in this build (and beta2 iirc) by an updated connman package ("rpm -qi connman" shows ip6tfix in version).
Maybe it's related to Yama security, will make a build without it...
Arbitrary reboots, after the introduction of the account and login starts hanging and rebooting, I immediately rolled back to the backup and did not understand why this is happening.
andrejchern said:
Arbitrary reboots, after the introduction of the account and login starts hanging and rebooting, I immediately rolled back to the backup and did not understand why this is happening.
Click to expand...
Click to collapse
Could you try flashing the ZIP inside the artifact from this devel build ?
It uses the same kernel as 3.0.0.8, ie. without yama, pstore and iirc RTC write support...
This build works fine, no reboots. Thanks.
SailfishOS 3.0.1.11 beta4
Update from any previous betas using OTA :
has to be done from commandline (on device or through SSH, USB prefered) since the graphical client in settings doesn't support community ports.
Code:
# Install sfos-upgrade package like this, or through Storeman
curl -O https://openrepos.net/sites/default/files/packages/5928/sfos-upgrade-2.4-1.noarch.rpm
devel-su
pkcon install-local sfos-upgrade-2.4-1.noarch.rpm
sfos-upgrade 3.0.1.11
reboot
# Patience, it takes an additional reboot to flash boot partition
# Go to commandline again and run :
devel-su post_sfos-upgrade
or install by flashing sailfishos-idol3-release-3.0.1.11-20190329-beta4.zip
(this replaces previously installed SailfishOS and SailfishOS-data, backup if needed)
Changes
Fall back to previous kernel
Hey mate, great job! Everything worked fine with sfos-upgrade from command line! Thanks a lot!!!
Just a question... I haven't prediction text, it's normal? Thanks again.
Antonio from Italy.
░▒▄█▀▄░ █▀▄ █▀▀▄ █▀▀ █▄░█ ▄▀▄ █░░ ▀ █▄░█ █▀▀░░▒▐█▀▀▄ ▄▀▄ █▄░▄█
▒▐█▄▄▐█ █░█ █▐█▀ █▀▀ █░▀█ █▀█ █░▄ █ █░▀█ █▀▀░░▒▐█▒▐█ █░█ █░█░█
▒▐█░▒▐█ ▀▀░ ▀░▀▀ ▀▀▀ ▀░░▀ ▀░▀ ▀▀▀ ▀ ▀░░▀ ▀▀▀░░▒▐█▀▄▄ ░▀░ ▀░░░▀
Key Features
Based on @foobar66 GoogleWiz ROM
NX Kernel
Samsung SoundAlive Dolby Atmos
Shell Script Advanced Features (SSAF) *See post #2
Updates will come in small service packs instead of a complete ROM update unless necessary
Samsung Gear might work out of the box
Removed some tweaks that I deemed useless.
Removed a few Google apps (Drive, Map, YouTube, etc) from the ROM, you can install them from Play Store instead
Emergency Launcher, UltraPowerSavingMode, SmartCapture, SmartSwitch, LiveWallpaper
Removed GoogleWiz's customizing script
Installation
Backup is always recommended
You should be able to dirty flash from stock/GoogleWiz ROM
You might not be able to boot, which is why 1. is important
Install any patch or cumulative update zip.
Adrenaline Experience
Some apps that I personally use and recommend:
SolidExplorer
SwiftBlack
Fluid Navigation Gestures
Download
*Feel free to mirror, however, monetizing the download link in any way is strictly prohibited.
Google Drive
Patches & Cumulative Update
Bootloader
Source
GITHUB: Shell Script Advanced Features
Credit
@foobar66
@SoLdieR9312
@Noxxxious
@xpirt
amirzaidi for Pixel Launcher
Shell Script Advanced Features
Everything that can be done in shell script shall be done in shell script.
You will need to install a terminal emulator from PlayStore to use this function.
Current functions:
Remap Bixby Key
Change Device Name
Max Volume Warning Toggle
Enable Stereo Speaker
Navigation Bar Toggle
Immersive Mode
Set DNS
Powercfg by yc9559 @ CoolApk [EXY8895]
Host File Based Adblock
Service Disabler
Set big Cluster Max Freq
Set LITTLE Cluster Max Freq
Script OTA Self Update
Reboot Device
Reboot into Recovery
To use, type the following in a terminal emulator
Code:
su
cfg
Code
Issues
TODO/Progress
Wiki
Credits
Changelog
v1.0 - The Late Santa [26 Dec 2018]
Initial Release.
v2.0 - WorstJet [13 Jan 2019]
Reverted Samsung Camera to stock
Samsung Gallery is back to the party
Added quite a lot of files that are related to VOLTE/VOWIFI (credit), you will need to flash CSC installer to install your CSC files
NX Kernel R19
Magisk v18.0
Almost up-to-date SSAF
Flashable Update Zip
[Patch] - Smaller fix, you need to install all patches according to the number, you do not need to reboot in between patches. (Flash 1.0 first, then 2.0, 3.0 ...)
[Cumulative Update] - Bigger update containing all the previous small patches.
WorstJet
-Nothing available as of now
Previous Version(s)
The Late Santa
[Patch 1.0] 26122018
Enabled navigation bar
Added Project WIPE by yc9559 @ CoolApk, default setting is set to [Balance]
Changed config to cfg for easier access
[Patch 2.0] 27122018
Added GearManagerStub.apk
Added Launcher from amirzaidi
[Patch 3.0] 27122018.2
Updated custom menu to include adblock and service disabler
[Patch 4.0] 30122018
Fixed permissions
Minor update to SSAF
Service disabler in SSAF will now run in complete silence
Enabled UHQ tile in csc
[Patch 5.0] 31122018
SSAF now able to set DNS properly
SSAF now able to change big cluster max freq
[Patch 6.0] 03012019
SSAF now able to grab dependencies from GitHub if any is missing
SSAF now able to change LITTLE cluster max freq
Minor fixes to powercfg
[Patch 7.0] 05012019
SSAF now able to enable stereo speaker
Thanks! Haven't been able to download the ROM you're basing yours as it always hangs for me with megaupload, will try yours as I have better luck with gdrive. Slds.
well stuck on android is starting
Android is starting and no navbar,even going for settings and reenable it
pbls said:
Android is starting and no navbar,even going for settings and reenable it
Click to expand...
Click to collapse
I left the navigation bar disabled in build.prop accidentally
Edit the last line in build.prop:
Code:
qemu.hw.mainkeys=1
to
Code:
qemu.hw.mainkeys=0
and reboot.
or use the custom menu to re-enable it then reboot
or edit the build.prop and reflash ROM
EDIT:
or flash the attached flashable patch zip
how do i install the rom?
well the navbar is back and still stuck at android is starting
ps: this rom doesnt have a launcher thats why i keep stuck at android is running
Is Volte vorking? Foos original rom hasn't.
Good job ! I will test the rom i i will give u a feedback !
You will planning to add some more mods ?
Thanks.
the ROM doesn't have a launcher,you must go to the Google play to install one
pbls said:
the ROM doesn't have a launcher,you must go to the Google play to install one
Click to expand...
Click to collapse
Ah.. now I know why it doesn't boot.
navaskp said:
Is Volte vorking? Foos original rom hasn't.
Click to expand...
Click to collapse
It isn't working either
xtmzone said:
Good job ! I will test the rom i i will give u a feedback !
You will planning to add some more mods ?
Thanks.
Click to expand...
Click to collapse
I'd refrain from adding 'mod' myself that requires to be redone every security update as it wastes time.
Feature will be added to the custom menu instead as that is portable, work across updates and even devices.
Everything that's doable in shell script shall be done in shell script.
ImbaWind said:
AdrenalineROM Custom Menu
You will need to install a terminal emulator from PlayStore to use this function.
Current functions:
Remap Bixby Key
Change Device Name
Max Volume Warning Toggle
Navigation Bar Toggle
Immersive Mode
Set DNS
Powercfg by yc9559 @ CoolApk [EXY8895]
Host File Based Adblock
Service Disabler
Reboot Device
Reboot into Recovery
To use, type the following in a terminal emulator
Code:
su
cfg
Click to expand...
Click to collapse
I always get the result "permission denied"
Su rights granted to terminal emulator. Used the commands su "enter" cfg "enter". What am I doing wrong?
xxxPLETTIxxx said:
I always get the result "permission denied"
Su rights granted to terminal emulator. Used the commands su "enter" cfg "enter". What am I doing wrong?
Click to expand...
Click to collapse
Sounds like you are doing everything right, but I'm not sure why.
Can you attach a screenshot?
keyboard is not working for me
ImbaWind said:
Sounds like you are doing everything right, but I'm not sure why.
Can you attach a screenshot?
Click to expand...
Click to collapse
Sure. Hope you can help.
ImbaWind said:
Sounds like you are doing everything right, but I'm not sure why.
Can you attach a screenshot?
Click to expand...
Click to collapse
Same here,but loving the ROM nonetheless and I've installed so many
xxxPLETTIxxx said:
Sure. Hope you can help.
Click to expand...
Click to collapse
pbls said:
Same here,but loving the ROM nonetheless and I've installed so many
Click to expand...
Click to collapse
Code:
su
mount -o rw,remount /system
chmod 777 /system/bin/cfg
cfg
This should help
Tested with:
Code:
ArrowOS Version: arrow-11.0
ArrowOS Build Type: OFFICIAL
ArrowOS Build Variant: VANILLA
Device Name: POCO X3 NFC (surya)
This modification makes use of the addon.d survival mechanism found in almost all (if not all) custom ROMs, which is leading back to CyanogenMod, and allows the installation of @janhammer504's YouTube HDR & Chrome Yellow Tint - Real Fix with automatic reinstatement after a manual or OTA system update.
Create the folder /sdcard/Android/addon.d/hdrfix, download and unpack YouTube HDR & Chrome Display Fix (v2) - Final.zip to that location.
Place the following script with the name 52-hdrfix.sh into /system/addon.d and make it executable (755), which can either be done from a root shell or through recovery after mounting /system with read-write access:
Code:
#!/sbin/sh
#
# ADDOND_VERSION=2
#
###################
# Restore HDR Fix #
###################
case "$1" in
post-restore)
AD="/sdcard/Android/addon.d"
DD="/product/vendor_overlay/29/etc"
mount /dev/block/mapper/product /product 2> $AD/mount_error.log
[ -d $DD ] && cp $AD/hdrfix/* $DD 2> $AD/hdrfix_error.log
umount /product
;;
esac
That's it, either reinstall the current version of the used custom ROM through recovery or make an OTA update.
Now the catch with this was, that for some unknown reasons, addon.d scripts see the device mapping different than from a running system or recovery, please see this issue for details.
ArrowOS 11 has the two XML files in /product/vendor_overlay/29/etc, but this may be different in other ROMs. In that case, simply have a look and change the destination folder ($DD) in the script accordingly.
The script is safe to use as nothing gets modified if the given destination folder is not found.
To uninstall this modification, simply remove the file /system/addon.d/52-hdrfix.sh.
You can also temporarily disable this modification by removing/renaming the two XLM files from/in /sdcard/Android/addon.d/hdrfix and everything gets back to default with the next system update.
Hint: You may want to watch the changelog for the used ROM and remove that modification once the ROM developers have implemented that fix by themselves.
Although working as supposed to, my approach for applying this fix is more of a proof of concept to me, as I wanted to find out how to make use of the addon.d survival mechanism.
For anyone else looking for an easier way to apply that fix (till your ROM developer has taken care of this), @janhammer504 has already provided the according Magisk Module.
FYI This fix will be implemented in the next build of ArrowOS, so this modification is no longer needed if using that custom ROM.
Is there any magisk module for fix? I'm noob Now using Havoc os 4.3 and don't want to flash arrow os and format data and install everything again Thanks in advance.
Master One said:
FYI This fix will be implemented in the next build of ArrowOS, so this modification is no longer needed if using that custom ROM.
Click to expand...
Click to collapse
I have the latest arrow os 12 on my F3 and HDR does not work.
AndreiR32 said:
I have the latest arrow os 12 on my F3 and HDR does not work.
Click to expand...
Click to collapse
Better ask at the new ArrowOS 12 thread then, because I'm still on 11.