Related
This overlay APK is "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .
What it does exactly?
Nothing more than adding AOSP overlay matching our device capabilities and also, inherits Bond power profile.
Do I need it?
Yes.
It will fix Battery stats problems and add compatible features for your BND over GSI.
This will conisderably enhance your experience on every GSI ROM giving better functionality overall.
Why you did that?
Because I'm sick of inheriting stuff that belongs to /vendor, in system.
Project Treble it's all about separating vendor implementation from system.
So why we should keep adding OEM stuff in that doesn't belong no more in /system
I have XYZ device with ZYX firmware can I use it?
As long as you're on a BND-*** device (with a non-EMUI firmware), you're good to go.
Otherwise DO NOT USE IT FOR THE LOVE OF MANKIND.
I don't have BND, but I want it on my Huawei device !
Well, that's fine, join the Telegram group @GSI_HI6250, so that you could help me with stock files grabbing to make an overlay for your device.
Overlay configs (aka "what does dis do, ser tell pl0x"):
Allows all rotations;
Configs autobrightness levels;
Configs autobrightness Lcd values;
Configs BLE;
Sets Doze Component;
Sets Doze After screen off;
Configs autopowermodes (doze related);
Configs power management on:
screen off due to proximity sensor interaction;
decouple on suspend state;
Configs brightness doze value;
Configs Intrusive led;
Configs dual band wifi support (where available);
Configs hotswap (where available);
Configs Color Transform on HWC;
Configs VoLTE available (even tho it needs support on GSI side);
Configs WFC over IMS;
Configs wifi background scanning support.
Installation Instructions
Download the overlay
With root, push the overlay to /vendor/overlay. Create the folder if it doesn't exist.
Run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/dil3mm4-overlay-BND.apk
It's here, it's finally here
Dil3mm4 said:
This overlay APK it's "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .
What it does exactly?
Nothing more than adding AOSP overlay matching our device capabilities and also, inherits Bond power profile.
Do I need it?
Yes.
It will fix Battery stats problems and add compatible features for your BND over GSI.
This will conisderably enhance your experience on every GSI ROM giving better functionality overall.
Why you did that?
Because I'm sick of inheriting stuff that belongs to /vendor, in system.
Project Treble it's all about separating vendor implementation from system.
So why we should keep adding OEM stuff in that doesn't belong no more in /system
I have XYZ device with ZYX firmware can I use it?
As long as you're on a BND-*** device (with a non-EMUI firmware), you're good to go.
Otherwise DO NOT USE IT FOR THE LOVE OF MANKIND.
I don't have BND, but I want it on my Huawei device !
Well, that's fine, join the Telegram group @GSI_HI6250, so that you could help me with stock files grabbing to make an overlay for your device.
Installation Instructions
Download the overlay
With root, push the overlay to /vendor/overlay. Create the folder if it doesn't exist.
Run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/dil3mm4-overlay-BND.apk
Click to expand...
Click to collapse
Im a lil bit confused , i have the honor 7x (BND-AL10) and i just wanna know what this will exactly do
Martobhai said:
Im a lil bit confused , i have the honor 7x (BND-AL10) and i just wanna know what this will exactly do
Click to expand...
Click to collapse
Do you mind not quoting the entire original post? Makes for a very long post and makes your problem hard to read.
This enables battery usage info and some device-specific features.
Dil3mm4 said:
This overlay APK it's "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .:
Click to expand...
Click to collapse
Hi mate. Just a request, can you make also for vicky (huawei p10+)? Thank you in advance
v0ne said:
Hi mate. Just a request, can you make also for vicky (huawei p10+)? Thank you in advance
Click to expand...
Click to collapse
Please join the telegram group in the my signature for that.
I'd need a couple of things from VKY.
Thank you.
UPDATE
-P compatibility
-Improved brightness levels
DOWNLOAD
#freedil3mm4
#freedil3mm4
@Dil3mm4 Hi, could you provide an overlay like this for moto e5? If you need files, I can send them.
Do I need this if I use phu truss on aosp? Thx
Hey man, I'd like to have a better experience on Descendant on my Honor 6X, in fact at the moment i can't see battery stats, per-app usage, ecc. - I'd like to know if you're still providing overlays for specific Huawei devices on Telegram group. Last request here in the thread is dated 2018 by what I can see, so... Thanks in advance and keep on.
optionalmgrr.la said:
Do I need this if I use phu truss on aosp? Thx
Click to expand...
Click to collapse
hi anyone?
This overlay APK it's "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .
What it does exactly?
Nothing more than adding AOSP overlay matching our device capabilities and also, inherits Victoria power profile and it's compatible with P!
Do I need it?
Yes.
It will fix Battery stats problems and add compatible features for your VTR over GSI.
This will conisderably enhance your experience on every GSI ROM giving better functionality overall.
Why you did that?
Because I'm sick of inheriting stuff that belongs to /vendor, in system.
Project Treble it's all about separating vendor implementation from system.
So why we should keep adding OEM stuff in that if it doesn't belong no more in /system?
I have XYZ device with ZYX firmware can I use it?
As long as you're on a VTR-*** device (with a non-EMUI firmware), you're good to go.
Otherwise DO NOT USE IT FOR THE LOVE OF MANKIND.
I don't have VTR, but I want it on my Huawei device !
Well, that's fine, join the Telegram group @GSI_HI6250, so that you could help me with stock files grabbing to make an overlay for your device.
Installation Instructions
Download the overlay [/URL]
With root, push the overlay to /vendor/overlay. Create the folder if it doesn't exist.
Run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/dil3mm4-overlay-VTR.apk
Thank you very much!
It seems like there is already a huawei vtr overlay included in phh's aosp pie. Can you tell if there are any benefits in applying this on top?
Of
Sent from my LDN-LX2 using XDA Labs
nabihaharyono said:
Of
Click to expand...
Click to collapse
same
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.
Android Q hidden settings enablerCreated by @kingbri
Disclaimer: I am not responsible if you flash this and make your phone into a brick, blow it up, create nuclear war, etc. You are flashing this at your own risk (However, it's very likely this won't happen)
This is a simple magisk module that adds a script to your /system/bin directory
What it does: Shows android Q hidden settings for well-known features (example: Dark mode)
Current features:
Android Q dark theme (system-wide and app-forced)
Navigation bar tweaks (Removed back button and new Q quick switching mechanism)
How to use:
ADB
Enter an adb shell
enter the command "qmod"
Follow the instructions
On-phone
open terminal emulator
su
enter the command "qmod"
follow the instructions
You can also use this without root!Just grab the script by running this command:
curl https://raw.githubusercontent.com/bdashore3/q_tweaks/q_master/system/bin/qmod > /sdcard/qmod
and follow the steps
Steps:
Push the file to /sdcard
Enter an adb shell
cd to sdcard
chmod 0777 qmod
type "sh qmod"
follow the script
Downloads: https://github.com/bdashore3/q_tweaks/tree/releases
If you want to ask questions, here's the contact group for my work: t.me/KingDevel
Credits: MishaalRahman (for getting all his journal posts), paphonb (for the debug_pixel launcher), and anyone else who figured out these tweaks/were behind-the-scenes for this stuff.
Please put any hidden android Q features that you find in here (With the code or it won't be accepted) or open an issue on github along with the code necessary to enable that feature.
mine again
Thanks, this is mine
I am confused, is this a Magisk module to Enable hidden features that already exist in Android Q or a module to add Android Q features to Pie?
firesword14 said:
I am confused, is this a Magisk module to Enable hidden features that already exist in Android Q or a module to add Android Q features to Pie?
Click to expand...
Click to collapse
This mod just turns my tutorials into scripts:
Source 1: https://www.xda-developers.com/android-q-navigation-gesture-controls/
Source 2: https://www.xda-developers.com/android-q-toggle-dark-theme/
Good on ya @kingbri does the trick ?.
MishaalRahman said:
This mod just turns my tutorials into scripts:
Source 1: https://www.xda-developers.com/android-q-navigation-gesture-controls/
Source 2: https://www.xda-developers.com/android-q-toggle-dark-theme/
Click to expand...
Click to collapse
** into A script **
Update! (v1.1)
Changelog (In github q_master branch under "Add v1.1 commit"):
-Fix dark theming command
-Add Lockscreen clock styles, Desktop mode, and chat bubbles as options
-Change option input to numerical format
-Make things easier to read
The downloads are located here: https://github.com/bdashore3/q_tweaks/tree/releases
To contact me on Telegram, I am located here: t.me/KingDevel
Update! (v1.3)
Changelog (In github releases branch under "Add v1.3 commit"):
-Add iphone-style gestures
-Fix some missing stuff
-Add more documentation
-Add keycheck and a few options in installer
(Circumvents system not mounting)
For iphone-style gestures: No other nav bar tweaks are allowed!
You need the back button. All documentation on how to enable
is in the script, nav-bar tweaks, option 3.
The downloads are located here: https://github.com/bdashore3/q_tweaks/tree/releases
To contact me on Telegram, I am located here: t.me/KingDevel
Additionally, if anyone sees a new news post before I do about android Q hidden features (there are new ones popping up everywhere), follow the 2nd post in the O.P. If @MishaalRahman can post an article about this, that will be great rather than making seperate magisk modules for everything
Deleted. Duplicate post
Update! (v1.4)
Changelog (In github q_master branch under "Add v1.3 commit"):
-Improve iphone-like gestures documentation
-Update github documentation to use a curl command
(Non-root)The new curl command is in the OP, just run it in a terminal
Please follow the non-root instructions in the OP
To contact me on Telegram, I am located here: t.me/KingDevel
kingbri said:
Update! (v1.4)
Changelog (In github q_master branch under "Add v1.3 commit"):
-Improve iphone-like gestures documentation
-Update github documentation to use a curl command
(Non-root)The new curl command is in the OP, just run it in a terminal
Please follow the non-root instructions in the OP
To contact me on Telegram, I am located here: t.me/KingDevel
Click to expand...
Click to collapse
Will this work on latest Beta 2 patch?
Zehlek said:
Will this work on latest Beta 2 patch?
Click to expand...
Click to collapse
For me it causes issues especially with pixel launcher
With Q beta 2 update, nope. Changes to launcher so dev options limited. Now I did find that using this link instructions I could get file permissions to revert back to Pie. the "sandbox memory, files protection" is turned off. File managers and app can then access just like before. Now I started with a complete wipe, Q beta 2 factory image, adb enabled, run script,. As warned resets phone, I then added my apps, data, pics through device to device transfer.
https://developer.android.com/preview/privacy/scoped-storage#test-behavior-change
adb shell sm set-isolated-storage off
adb shell getprop sys.isolated_storage_snapshot
should return with flag = false
Your mileage may vary, data may be lost..... bla, bla, bla. Lawnchair v2 alpha works great too!
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.