Hi, this is a simple fix to make the camera working in gsi like Resurrection Remix. I have this problem only with this gsi.
In phone with a root explorer go to:
- /system
-open build prop, scroll down and mod this line like this:
-if you don't have add: persist.camera.HAL3.enabled=1
Boot to twrp, and flash this:
-Permissiver v2
If using Gcam, don't use Hdr+ Advanced
Profit. :good:
Related
Guys I know that many of you have been having trouble with installing exposed on your One x+. This is what I did to get it working:
Before we begin I must note that you MUST start clean. No Data, No ROM and Wipe Dalvik.
1. In the recovery find the cm rom on your sd card and install it.
2. Then find the Paranoid Android Gapps and install the as well.
3. Then Wipe cache and reboot into boot loader.
4. Flash the kernel and reboot into your ROM.
5. After the setup process get the Xposed.apk file and install.
6. Go into the app, Install the Framework, BUT DON'T REBOOT!!
7. Exit the app.
8. Change SELinux to Permissive. ( I used SELinuxModeChanger from the play store to change it)
9. After you changed it go into Terminal Emulator and type in these commands
a. su
b. mount -o remount,rw /
c. mount -o remount,rw /system
d. restorecon /system/bin/app_process
10. Now you can reboot!
11. Done and have fun modding your device!
Dalvik still alive: cm-11-20160612-NIGHTLY-enrc2b.zip
Battery friendly
If some are interested, you can build latest nightly 20160612 cm11 +3originals:
- mar-V-in fake signature for nogapp (github .com/microg/android_packages_apps_GmsCore/blob/master/patches/android_frameworks_base-KK-LP.patch;
- inverted broken xposed & SELinuxModeChanger from d8130142.diff (cm 20151109 review.cyanogenmod .org/#/c/118800/);
- wakelockblocker cherry-picked from crdoid 4.4 (github .com/crdroidandroid/).
Your build will, keep same CVE as the official one and, stay untouched apart +3 above.
For xposed only correction; get 2 files from ORIGINAL cm-11-20151108-NIGHTLY-... or any unofficial CMbased,before 20151109, for your device; then xposed(+1reboot?) AND SELinuxModeChanger.apk will both work back:
system/bin/app_process
system/lib/libandroid_runtime.so.
Wakelock Blocker for Official 2016, Nightly CM11 (and many more...wip)
I will be glad, if some could report a checked OK with BetterBatteryStats_2.1.0.0 or Wakekock Detector /device, in my thread.
Thanks in advance, and re-joy your battery & privacy.
Although the device is protected but it is an android ( The best open-source OS ) and here are the simplest steps :-
1- Rooting the device by Vroot
2- Install terminal
3- Install BusyBox
4- Install xposed
5- Write those commands in the terminal : su
mount -o rw,remount /system
chattr -R -i /system
6- Open any file manger and search for a file named set_immutable.list
7- Rename it into set_immutable.list.old
8- Go to INSTALLATION MODE in exposed frameword and tick on disable resource hooks
9- Tab on Install/Update DO NOT ACCEPT THE REBOOT
10- Go back to the file manger and rename the file " set_immutable.list.old " back to " set_immutable.list " ( you will get boot-loops if you skipped this step )
# Now you can also edit the build.prop
# As soon as you reboot the system permission will be back to the main original permission
# You also can edit host file my the same steps ( no need to say without re-installing exposed...... -_-)
# Now you can reboot
Tested my self, Written by me, Found the info on a French development website
What I tested with exposed :-
1- Android Apps Theme Engine pro >> Not Working
2- Android L Navigation Bar >> Not Working
3- Android L Theme >> Not Working
4- Android Theme Engine >> Not Working
5- Battery Home Icon >> Working
6- Burnt Toast >>Not Working
7- GravityBox [KK ]>> Not Working, but I
8- MaxLock >> Working
9- Network Speed Indicator >> Not Working
10- Physical Button Music Control >> Working
11- Statusbar download progress >> Working
12- VolumeStep+ >> Working
13- PinNotif >> Working
14- XHalo Floating Window >> Working
15- Xinstaller >> Working
= Everyone say what he test
Thanks. On my rooted x1 (7d-501u, 4.4.2 EMUI 3.0 400dpi), I simply install xposed 2.5.1.
I installed appsetting 1.8, try changing dpi but no effect, no error report. Any recommendation?
Sent from my X1 7.0 using Tapatalk
If Gravitybox doesn't work, not much point for Xposed.
I am on R002C209B008 Malaysia, and although I did the system r/w commands and got Xposed installed, nothing works. After a reboot, Xposed says it's not working.
I tried 2.4.1 which installed, but none of the newer mods work. I then tried 2.5.1, which shows the framework in red color. 2.7 experimental 1 installed with green text, but again nothing works after a reboot.
The trick that used to be edit build.prop for the hwtheme=0 no longer works.
Huawei also needs to release their kernel and ROM sources.
bthoven said:
Thanks. On my rooted x1 (7d-501u, 4.4.2 EMUI 3.0 400dpi), I simply install xposed 2.5.1.
I installed appsetting 1.8, try changing dpi but no effect, no error report. Any recommendation?
Sent from my X1 7.0 using Tapatalk
Click to expand...
Click to collapse
I didn't notice any change too
joytest said:
If Gravitybox doesn't work, not much point for Xposed.
I am on R002C209B008 Malaysia, and although I did the system r/w commands and got Xposed installed, nothing works. After a reboot, Xposed says it's not working.
I tried 2.4.1 which installed, but none of the newer mods work. I then tried 2.5.1, which shows the framework in red color. 2.7 experimental 1 installed with green text, but again nothing works after a reboot.
The trick that used to be edit build.prop for the hwtheme=0 no longer works.
Huawei also needs to release their kernel and ROM sources.
Click to expand...
Click to collapse
Have you tried those steps carefully ?, i have tested them on my 7D-501u on Rom emui 2.3, emui 3.0 B002 & B005
Which version of xposed did you use?
not working
i followed your steps but it did not work well with my b010 emui 2.3 K.K 4.4.2 and besides exposed will be nothing without the gravity box
its a hell of a good app to tweak your device i wish someone find a way for this big problem we need gravity box
Ok, I admit I missed NOT renaming set_immutable.list.old back to its original name.
After this, Xposed 2.7.1 experimental works, and AppSettings works.
However, Dimensions and Gravitybox still do not work.
Damn you and your stupid theming engine Huawei.
joytest said:
Ok, I admit I missed NOT renaming set_immutable.list.old back to its original name.
After this, Xposed 2.7.1 experimental works, and AppSettings works.
However, Dimensions and Gravitybox still do not work.
Damn you and your stupid theming engine Huawei.
Click to expand...
Click to collapse
I can confirm Xposed 2.5.1 framework and App Settings 1.8 module works on EMUI 3.0 B008 (for 503L).
I installed an older version of Xposed, upgrade it to 2.5.1 within Xposed, then installed the App Settings 1.8 module and I can now change DPI for apps that I want to work like they will on tablets.
The only caveat - Huawei's theme engine will break with the above arrangement (this is the same when on 2.3 B010) - u wont get any error or FC but u 'cannot' change theme; no matter which theme u choose, the icons will remain as default.
I m ok as I use Action Launcher and dont mind this cosmetic setback, against the freedom to be able to choose the DPI of each app!
I did not do any hacks nor install busybox to the X1 prior to installing Xposed, only flashed the KangVIP mod to get clean root.
YMMV
---------- Post added at 05:36 AM ---------- Previous post was at 05:29 AM ----------
bthoven said:
Thanks. On my rooted x1 (7d-501u, 4.4.2 EMUI 3.0 400dpi), I simply install xposed 2.5.1.
I installed appsetting 1.8, try changing dpi but no effect, no error report. Any recommendation?
Sent from my X1 7.0 using Tapatalk
Click to expand...
Click to collapse
if you are sure u got Xposed 2.5.1 and App Settings 1.8 properly installed and activated (did u activate the App Settings 1.8 module within Xposed?), the only thing missing may be what the KangVIP mod did to the system, you nay want to try flashing that (your X1's bootloader must be unlocked).
if u can download from china servers, the link is as below, else i will try to upload to mediafire for u (author is quite particular abt rehosting his files)
URL: pan.baidu.com/s/1jGLzK4u
Codeļ¼ 7c6s
if you cannot download from china servers, then use the link below
http://www.mediafire.com/download/04izc31qkkl4d2q/X1-EMUI3.0-B008_img.rar
good luck!
(i find wifi on 3.0 B008 not as good as when on 2.3 B010, but all other new features are pretty sweet)
daser4ever96 said:
Although the device is protected but it is an android ( The best open-source OS ) and here are the simplest steps :-
1- Rooting the device by Vroot
2- Install terminal
3- Install BusyBox
4- Install xposed
5- Write those commands in the terminal : su
mount -o rw,remount /system
chattr -R -i /system
6- Open any file manger and search for a file named set_immutable.list
7- Rename it into set_immutable.list.old
8- Go to INSTALLATION MODE in exposed frameword and tick on disable resource hooks
9- Tab on Install/Update DO NOT ACCEPT THE REBOOT
10- Go back to the file manger and rename the file " set_immutable.list.old " back to " set_immutable.list " ( you will get boot-loops if you skipped this step )
# Now you can also edit the build.prop
# As soon as you reboot the system permission will be back to the main original permission
# You also can edit host file my the same steps ( no need to say without re-installing exposed...... -_-)
# Now you can reboot
Tested my self, Written by me, Found the info on a French development website
What I tested with exposed :-
1- Android Apps Theme Engine pro >> Not Working
2- Android L Navigation Bar >> Not Working
3- Android L Theme >> Not Working
4- Android Theme Engine >> Not Working
5- Battery Home Icon >> Working
6- Burnt Toast >>Not Working
7- GravityBox [KK ]>> Not Working, but I
8- MaxLock >> Working
9- Network Speed Indicator >> Not Working
10- Physical Button Music Control >> Working
11- Statusbar download progress >> Working
12- VolumeStep+ >> Working
13- PinNotif >> Working
14- XHalo Floating Window >> Working
15- Xinstaller >> Working
= Everyone say what he test
Click to expand...
Click to collapse
when i enter 'mount -o rw,remount /system' on terminal it says 'mount: Invalid Argument'
what i need to do??
What is this?
This mod removes the persistent "Device is HD capable" Notification that appears on many custom roms
Applicability?
This mod is meant for Yu Yureka Plus running Resurrection Remix Rom 5.8.0 Official Build. For other devices, keep reading...
How does it do it?
The culprit package that causes this notification to appear in the status bar is ims.apk - located at /system/vendor/app/ims
This mod replaces that file with a modded one. More on that below...
Instruction of use
1) Download file - NR_yurekaRR580o.zip
2) Reboot phone into TRWP recovery
3) Mount > System partition
4) Install > NR_yurekaRR580o.zip file
5) Reboot
Downloads
1) Notification remover - NR_yurekaRR580o.zip
2) To re-enable this notification again, flash this file - NEN_yurekaRR580o.zip
-------------------
FOR OTHER DEVICES
This mod was made using the ims.apk file extracted out of Resurrection remix rom 5.8.0 official build meant for the yureka plus phone. So whether this mod will work on other phones cannot be answered. But if you want to create this mod for your phone, here are some quick lessons:
1) Find ims.apk file in your phone and extract it to PC
Try looking for it in /system/vendor/app/ims
2) Use apktool and do these edits in ims.apk
Decompile ims.apk
In ims.apk>res>values>bools.xml
Change value of config_update_service_status to True
In ims.apk>res>values>strings.xml
Delete value of device_is_hd_capable
In ims.apk>res>values-mcc** (inside dozen or so folders) > bools.xml
Change all values of config_update_service_status to False
Re-compile ims.apk and give necessary signs. And use it any flashable zip
Credits:
This mod is based on KabirKalsi's similar mod found here that he made for the redmi 3. All credits to him.
Will this works in RR Official March build??
Sent from my YU5510 using Tapatalk
Thanks for help. That notification was irritating me since I flashed voLTE firmware. Followed modification steps mentioned above.
PFA, apk file which worked for me on Yu Yureka RR v5.8.2.
Device Model: Yu Yureka AO5510
OS: RR-N-v5.8.2-20170307-tomato-unofficial
Flashed: voLTE firmware.
Android 7.1.1 (Resurrection Remix Nougat 7.1.1_r25 - NOF27B)
Steps to install:
make an adb connection to pc.
1. adb reboot recovery
2. adb push ims.apk /system/vendor/app/ims/
-- expected output -> [100%] /system/vendor/app/ims/ims.apk
3. adb reboot.
Done.
Download link. (remove the spaces)
http :// s000.tinyupload.com /index.php ? file_id = 37766304712524729237
Credits
@broadways
Worked perfectly fine on Moto G4 plus running Ressurection Remix.
If it remove hd sign...then is it add the volte icon??
Sent from my YU5510 using Tapatalk
Worked like a charm
Thanks man! It was really helpful and I used APK Editor to edit the values. Thanks a lot again. Cheers!
thanks for your help,I moved HD capable by this artcle.
How to enable HDR+ in Lenovo K6 / K6 power / K33 / Karate device?
1. You need custom ROM based on 64 bit
2. Need root. & Yoy must not have Google camera installed as system app. If it's installed as system app first remove it.
3. Open X-plore file manager. Give root permission. Go to system/build.prop & open it as text file.
( X-plore file manager download link:
https://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore )
4. Enable Hal3 by editing this line from 0 to 1
Before:
persist.camera.HAL3.enabled=0
After
persist.camera.HAL3.enabled=1
5. Save & then reboot.
6. Go to this link & download following modified Google camera. & Install it as simple apk.
Download link of modified Google camera:
https://androidfilehost.com/?fid=962021903579481168
OR
Download link of Google camera with more features link RAW:
https://androidfilehost.com/?fid=817906626617934890
7. Open Google camera & Enjoy HDR+
( Note:
Modified Google camera links have been posted from following:
https://www.xda-developers.com/google-camera-hdr-customization-raw-support/ )
Herein the screenshot below is the line that to be edited.
U gave the same link twice
m.atif said:
U gave the same link twice
Click to expand...
Click to collapse
Corrected
Thank you .Bro please give credits to Dev who made this magical mod.
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.