[GCAM]: Mi 8 SE: Buffer fix - Xiaomi Mi 8 SE ROMs, Kernels, Recoveries, & Other

Hey, I've found a man who made buffer fix for Mi 8 SE in a form of TWRP flashable zip, Magisk module and patched lib.
It will fix lagging viewfinder in GCAM
You have three options to install it:
1) Boot into TWRP, flash zip.
2) Flash zip in magisk
3) replace patched lib in vendor/lib/hw
Sources:
https://gist.github.com/HighwayStar/3da60a36395fa992cf4afc9f01449203
Credits:
@highwaystar_ru

But exactly what problem fix?perhaps is the same that I had, when I took photo or vĂ­deo It took too much time to be available in gallery or Google photos, but I solved with this change in settings-enable Google photo(reboot required) and now everything works fine with Gcam.
Thanks and regards

Thread closed
Double post. Please use existing thread here
strongst
Forum Moderator

Related

Enable google lense in google photo

Requirements
1) root
2)Magisk v14 or 14.3 app AND TWRP recovery for flashing
3)latest Google photo app from play store
4)android 7.0 to8.0
5) knowledge of flashing
Download files from This link
1) BY magisk module:
https://forum.xda-developers.com/on...photos-t3694140?_e_pi_=7,PAGE_ID10,7137433206
Installation Instructions
Copy the correct module as per your Magisk version to your phone's internal memory
Open Magisk Manager
Go to the Modules section
Click on the "+" Floating Button and select the module zip
Reboot
OR
2) BY recovery :
U can flash recovery flashable zip from this LINK AND reboot
https://forum.xda-developers.com/oneplus-3/themes/flashable-zip-google-lens-pixel-2-t3693859
Follow the instructions.....
https://youtu.be/omi9QD7ok-8
You have to take photo for which u want information and then go to google photo app and then open that image and use google lense for that....... It's tedious but useful
NOTE: I AM NOT RESPONSIBLE FOR ANY THING KEEP BACKUP

[Treble] Android GSI on Kenzo/Kate. [SnapDragon]

UPDATE - Pixel Experience Official is out for Kenzo. Link attached below. Ongoing support for GSI users though.
https://forum.xda-developers.com/redmi-note-3/development/rom-pixel-experience-t3835648
-------------------------------------------
Disclaimer: I'm not responsible for bricked devices, flash at your own risk. I might be able to help with restoring your device though.
This is a guide to installing Android GSI on Redmi Note 3 (Kenzo)
---------------------------------------------------
What works-
RIL
GPS
Camera
Pretty much everything
What doesn't work-
Bluetooth
Hotspot
VoLTE(I couldn't test)
(NOTE - Bugs vary GSI to GSI)
---------------------------------------------------
Required files -
Grab these files first, and keep them on your SD card
TWRP Treble - https://androidfilehost.com/?fid=5862345805528059847
Android GSI(USE ARM64 A-ONLY) - for this tutorial, I'm using Phhusson's AOSP Pie GSI found here - https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
List of GSI's - https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Pie GApps (If using Pie GSI) - https://forum.xda-developers.com/android/development/gapps-unofficial-opengapps-builds-t3828141
Vendor Image - https://androidfilehost.com/?fid=1322778262903993757
Permissive SELinux Enabler - https://drive.google.com/file/d/1KFdPH2JGtvkXwt2emxPb-k7zdv2pLd-F/view?usp=drivesdk
Magisk 16.7 (minimum 16.7, you can use 17 as well)- https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Latest Firmware - https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361/page176
Optional - Digital Well-being (ONLY FOR PIE)
Digital Well-being apk (Download latest version) - https://www.apkmirror.com/apk/googl...wellbeing-0-2-207862754-android-apk-download/
Digital Well-being Magisk Module - https://drive.google.com/file/d/1AAFMWbAAK-febiP9h4iZMJONEHXopmEU/view?usp=drivesdk
--------------------------------------------
Assuming you have an unlocked bootloader, and know your way in and around Android, let's begin!
How to install -
1. First, flash the Treble enabled TWRP.
2. Reboot to recovery.
3. Mount all partitions, and wipe all partitions.
4. Flash the Vendor Image zip file and immediately flash the Permissive SELinux Enabler.
5. Clear Dalvik/Cache.
6. Mount all partitions, and wipe system.
7. Flash GSI to System partition *only*.
8. Reboot to System.
9. Reboot to recovery.
10. Perform a factory data reset, and flash GApps
11. Reboot to System, and complete setup.
12. After completing setup, reboot to recovery and flash Magisk 16.7
13. Reboot to System
14 Reboot to recovery and flash firmware.
15. Profit!
If you want Digital Well-being (ONLY FOR PIE) -
16. Install Digital Well-being apk
17. Flash Digital Well-being Magisk Module through Magisk Manager
18. Reboot
19. Profit!
-------------------------------------------------------
Tested on Snapdragon version, don't know if it works on MTK.
Screenshots are attached.
Fixes -
If you have the QS toggles moving out of the header like the screenshot attached in #1, do the following steps
1. Enable Developer Settings,
2. Find Smallest Width setting
3. Increase the value by 20. (If it's 360, make it 380)
4. Profit!
------------------------------------------
Google Camera + Face Unlock fix.
If Google Camera/Face Unlock doesn't work for you, do the following -
1. Reboot to recovery
2. Mount system
3. Flash the zip file (download link below)
4. Clear cache
5. Reboot to system
This should make Face Unlock work again, and GCam work as well.
Download patch - https://drive.google.com/file/d/17OUBxhsfeK0625_pYe8aRNr5L6doKdAK/view?usp=drivesdk
------------------------------------------
Can't find Smart Lock in settings?
1. Go to Settings < Security and Location.
2. Scroll down and click Advanced.
3. Click Trust Agents.
4. Switch on Trust Agent for Smart Lock.
You should now have Smart Lock option below Fingerprint.
-------------------++++++++++++++++-----------------------
For Changing accent colours -
Download this file - https://t.me/kenzousersglobal/1169
1. Flash it in recovery
2. Reboot to system
3. Go to Settings - Display - Advanced. Scroll down to find "Colour Theme"
4. Select colour theme and select colour of your choice.
5. Profit!
---------------------------------
Custom kernels that currently work
Radon - https://drive.google.com/file/d/1LYggpHDVph1fvWctIKY4FqQwtRb6Svh0/view
---------------------------------
Review - after extensive testing, I found this to be daily driver material, with the only exception being Bluetooth, Hotspot, and VoLTE(I couldn't test it myself)
Special thanks to - @corkiejp
Is it possible to get an Overlay Patch for Mi 8?
NielsvdS said:
Is it possible to get an Overlay Patch for Mi 8?
Click to expand...
Click to collapse
I honestly have no clue. I have only gathered all the patches and files for Kenzo and made them into one guide.
Thanks for the guide: -
Digital Well-being apk (Download latest version) <<<< Links to the overlay zip and not the apk.
Sourced the beta of apkmirror: - https://www.apkmirror.com/apk/googl...wellbeing-0-2-207862754-android-apk-download/
I used Mind the Gapps found on Telegram, when flashing.
Is it possible to dirty flash open gapps?
Work on kate devices?
Why is it there system.img.xz should I remove .xz rename it
---------- Post added at 04:24 PM ---------- Previous post was at 03:42 PM ----------
1.flashed carlosvendor.zip
2.mounted system vendor cache
3.flshed system.img as system image
After rebooting stuck at fastboot logo
sharan565 said:
Why is it there system.img.xz should I remove .xz rename it
---------- Post added at 04:24 PM ---------- Previous post was at 03:42 PM ----------
1.flashed carlosvendor.zip
2.mounted system vendor cache
3.flshed system.img as system image
After rebooting stuck at fastboot logo
Click to expand...
Click to collapse
You need to extract the image file from that compressed format, use windows are download an app that will extract it.
Suggestion RAR from play: - com.rarlab.rar or alternative app that will do the same.
corkiejp said:
You need to extract the image file from that compressed format, use windows are download an app that will extract it.
Suggestion RAR from play: - com.rarlab.rar or alternative app that will do the same.
Click to expand...
Click to collapse
Thanks man I will try
Hey @Sid127, this is really nicely written tutorial, thank you What bothers me, why we need to mount partitions once again in step 6? Partitions were mounted in step 3 and there wasn't any reboot in meanwhile.
3. Mount all partitions, and wipe all partitions.
4. Flash the Vendor Image zip file.
5. Clear Dalvik/Cache.
6. Mount all partitions, and wipe system.
7. Flash GSI to System partition *only*.
Click to expand...
Click to collapse
Second question, maybe easier... If I have existing TWRP backup for non treble ROM, is it OK to restore such backup using Treble recovery after wiping everything? Or it's recommended to flash previous recovery first?
wxtester said:
Hey @Sid127, this is really nicely written tutorial, thank you What bothers me, why we need to mount partitions once again in step 6? Partitions were mounted in step 3 and there wasn't any reboot in meanwhile.
Second question, maybe easier... If I have existing TWRP backup for non treble ROM, is it OK to restore such backup using Treble recovery after wiping everything? Or it's recommended to flash previous recovery first?
Click to expand...
Click to collapse
1. You just need to make sure that all partitions are mounted.
2. You can restore the backup through Treble TWRP.
Happy flashing!
Hexvessel1992 said:
Work on kate devices?
Click to expand...
Click to collapse
I don't know, I need someone to test it. It should work, since the Vendor for Kenzo and Kate are the same.
corkiejp said:
Thanks for the guide: -
Digital Well-being apk (Download latest version) <<<< Links to the overlay zip and not the apk.
Sourced the beta of apkmirror: - https://www.apkmirror.com/apk/googl...wellbeing-0-2-207862754-android-apk-download/
I used Mind the Gapps found on Telegram, when flashing.
Is it possible to dirty flash open gapps?
Click to expand...
Click to collapse
I'll update the thread with the right link
I think it is possible to dirty flash Open Gapps, but it might give bugs, always go for a clean flash
Everything works for me, only thing was that at the first setup it was stuck on "checking for updates". So I tried the method of tapping all sides of the screen (from top-left clockwise to bottom-left) and it skipped the setup. The flashlight is a little wonky, but that's the only thing that was getting in my way. The audio was a little too quiet, so I installed some app on the playstore to gain it. Thanks for such a comprehensive guide! Android Pie is amazing, but development for it on a 3 year old device is even more so!
srishant said:
Everything works for me, only thing was that at the first setup it was stuck on "checking for updates". So I tried the method of tapping all sides of the screen (from top-left clockwise to bottom-left) and it skipped the setup. The flashlight is a little wonky, but that's the only thing that was getting in my way. The audio was a little too quiet, so I installed some app on the playstore to gain it. Thanks for such a comprehensive guide! Android Pie is amazing, but development for it on a 3 year old device is even more so!
Click to expand...
Click to collapse
I had to forage through 4 complex guides, scourge through XDA and Telegram for all the patches, and hence could make such a simple guide. Apparently, devs on the Telegram channel are working on the Bluetooth and VoLTE fix I'll update once that happens!
Bolte
Test n let me know if it works
https://t.me/kenzoromnews/1445
Modify for treble then flash
amog787 said:
Bolte
Test n let me know if it works
https://t.me/kenzoromnews/1445
Modify for treble then flash
Click to expand...
Click to collapse
I did see that, but when I flashed it, it messed upy system and I had to reinstall the GSI. I don't know how to modify it for Treble, could you do it? I'm happy to test. I believe that fix is for Flashavle ZIPs, not for Treble GSIs.
Possible Gcam and stock working patch!
Posted this in AOSP Pie Rom thread, may also work for the GSI?
corkiejp said:
I found Gcam Pie Fix for another device in this thread.
Link to Gcam Pie Fix: - https://drive.google.com/file/d/1D5qvlA-QbQu6xoWpsLPyWquMkS3hxXi3/view
Gcam that I'm using: - https://androidfilehost.com/?fid=673956719939833577
^^^ From this thread, maybe newer versions available.
I was able to setup face unlock after flashing the above fix, you may also need to enable Smart Lock (Google) as a trusted agent.
It is buggy and the face option may not always trigger, plus you need to hold the phone far from you and swipe when the lock symbol appears (no fast unlock options xposed).
Another benefit of flashing another Camera (V 2.0.002) Started working as well. (Don't know if that is the default AOSP camera or something I restored from backup? Could be Snap Camera from LOS).
Click to expand...
Click to collapse
corkiejp said:
Posted this in AOSP Pie Rom thread, may also work for the GSI?
Click to expand...
Click to collapse
Is there also an uninstaller for this fix? I'll test only if there is an uninstaller for it. Last time I tested a fix I had to format data to revert...
Sid127 said:
Is there also an uninstaller for this fix? I'll test only if there is an uninstaller for it. Last time I tested a fix I had to format data to revert...
Click to expand...
Click to collapse
Not that I'm aware of, but this just places/replaces some Lib and Lib64 in system partition.
If your worried about it, back up your system partition, flash the this patch and wipe caches.
If you experience problems, just restore your system partition.
It was reported working by someone else here.

Here Is How To Get HDR+, Portrait Mode and much more (Only For 64 Bit Oreo)

Caution Only For Oreo 64bit
Hello Guys , This is my First thread . Be Sure To Leave A Reply . All Links Below The Thread.
I Am Using Moto g5 with :-
1. Unlocked Bootloader
2. 64bit Recovery (Thanks To @CodeZero)
3. Aosp Extended Rom (Thanks To @Fedray , You are on Fire)
Steps For HDR+ And Portrait Mode
Note :Currently All Oreo Roms (Not Stock) have patched Camera , so you need to follow as below to enable HAL3 (camera 2 api)
1. Install MagiskManager (latest version) and flash magiskzip (will be available inside magiskmanager)
2.Install MiXplorer and give root access
3.Go to root directory then go to /system/lib/hw
4. Delete or Rename camera.msm8937.so as camera.msm8937.so.bak and rename camera.vender.msm8937.so to camera.msm8937.so
5.Install BuildPropEditor.
6. Add A Line Saying "persist.camera.HAL3.enabled=1"
7.Reboot
8. Install Provided Camera
9. Go To camera Settings - Advanced - Under Front Camera - Manual fixed black level offset- Set To 16 or 12
10.Restart Camera Application.
Boom You Get HDR+ And Portrait Mode .......But I Was Not Able To Record Videos (But Footej Is Working For VIdeos)
If You Want Ar Stickers , then Flash The Zip Below After Following the above tutorial
You May Now Also Install Motion stills apk from the play store.
Magisk Manager - Search Google
MiXplorer - https://forum.xda-developers.com/showthread.php?t=1523691
Camera - https://drive.google.com/file/d/1skMGmQlHOn0pVXh5UD7AS6F6LIQNTF91/view?usp=sharing
Ar Stickers - https://drive.google.com/file/d/1skMGmQlHOn0pVXh5UD7AS6F6LIQNTF91/view?usp=sharing
Pixel Fonts - https://drive.google.com/file/d/1jfHTqLU8bu1FyWelprindMzYpW5wC1OP/view?usp=sharing
BuildProp Editor - https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en_IN
Twrp 64 - https://androidfilehost.com/?w=files&flid=236353
If I Miss To give Credits to Anyone Pls PM me
Any mod for 32bit with Portrait Mode
Fedray used to be on fire but now he doesn't update AEX at all
Exanneon said:
Fedray used to be on fire but now he doesn't update AEX at all
Click to expand...
Click to collapse
Chill man , he is busy.
abhimanyuk said:
Any mod for 32bit with Portrait Mode
Click to expand...
Click to collapse
There is but......you will have to use lensblur
Or else you may use Snapseed for editing and making image blur.. search Google.
Can I run camera files by transferring to android 9?

Viper4android driver status abnormal.

Dear brother's I have facing issue with viper4android fx, I have installed from magisk module and install driver but it show status-abnormal, I have seen many videos on youtube and check XDA thread but still same issue.
Pls help me...
wakram001 said:
Dear brother's I have facing issue with viper4android fx, I have installed from magisk module and install driver but it show status-abnormal, I have seen many videos on youtube and check XDA thread but still same issue.
Pls help me...
Click to expand...
Click to collapse
Use the guide as in that post (the same can be also found in the XDA V4A general thread):
zgfg said:
There is actually an easier way to fix Viper4Android, follow the original post where the fix was described:
[APP][ALL ROOT SOLUTIONS][6.0+]ViPER4Android FX 2.7
ViPER4Android FX By pittvandewitt and MrWhite214 Introduction Many users are enhancing their smartphone audio experience with the popular ViPER4Android software, but some of us have a hard time installing the driver or they don't like the look...
forum.xda-developers.com
In other words, replace (use TWRP or root explorer like MiXplorer)
/data/adb/modules/ViPER4AndroidFX/post-fs-data.sh
with the attached file (download and unzip) and reboot
Still make sure that Legacy mode in V4A Settings is enabled
AML module makes no harm but it's not needed (unless you install additional audio modules like mi9tpbitrate320.zip)
---
In case of installing V4A from scratch:
- install ViPER4Android_FX-v2.7.2.1.zip from Repo (through Magisk) and reboot
- open Viper4Android app and let it install the driver, it will reboot
- replace post-fs-data.sh as above and reboot once again
- open Viper4Android app and enable Legacy mode in its Setrings
- also, don't forget to enable Master limiter for e.g. speaker or headphones
Check the driver status, it must show Status Normal (and Processing Yes when playing nusic)
---
I have Xiaomi.eu A11 beta and I regularly update every week when they release (by dirty flashing their new MIUI zip release, wiping Dalwik and Cache and by flashing the new boot img patched by Magisk)
Up to the two weeks ago I had to re-do the relatively complicated procedure for V4A as was described in this thread upon every Xiaomi.eu update
Since two weeks ago when I replaced the post-fs-data.sh as described above, I just dirty flash Xiaomi.eu, apply root/Magisk, and my V4A continues to work as my all other installed Magisk modules (and root apps), with no needs to fix the V4A driver anymore
PS: This 'new' method with the modified post-fs-data.sh is specifically useful for Magisk Canary 22006 since Magisk 22006 has a known bug with processing the sepolicy.rule files (also in /data/adb/modules/ViPER4AndroidFX), and hence the 'old' method from this thread does not work with Magisk 22006 - but the 'new' method does work (I currently use that Magisk 22006)
Click to expand...
Click to collapse
Can AML fix this issue...
I can't understand which files I replace.
I am a bigner user of magisk.
wakram001 said:
Can AML fix this issue...
I can't understand which files I replace.
I am a bigner user of magisk.
Click to expand...
Click to collapse
In the thread I gave you the link, use of AML was also described. But I'm no more using AML and cannot/won't support you about
In my previous post there is s link to my post with the guide using post-fs-data.sh (sorry, I'm not going to send the link again)
Click on that post and inside you will find post-fs-data.zip.
It was described in details, so once again but only shortly here:
- download the zip, extract post-fs-data.sh
- use your favorite root File Manager (like MiXplorer - google on XDA to find its thread and installation if needed) or use TWRP, Advanced, its File Manager (again, google if needed to learn how to use).
Anyway, those skills and tools will be useful for you in future if you decided to go with Magisk, its modules, etc
- go to /data/adb/modules/Viper4Android FX and rename the existing post-fs-data.sh to post-fs-data.bak (just in case) and paste instead the post-fs-data.sh you extracted from my zip (see screenshot)
-reboot
- open V4A app, go to its settings and enable Legacy mode (again, see the screenshots in my post with the guide)
Dear brother
I have understood what you said, but I can't find zip file from your previous post, one more thing v4a fx working with legacy mode, but when I close legacy mode it cannot support.
Thanks for replying on my post.
zgfg said:
In the thread I gave you the link, use of AML was also described. But I'm no more using AML and cannot/won't support you about
In my previous post there is s link to my post with the guide using post-fs-data.sh (sorry, I'm not going to send the link again)
Click on that post and inside you will find post-fs-data.zip.
It was described in details, so once again but only shortly here:
- download the zip, extract post-fs-data.sh
- use your favorite root File Manager (like MiXplorer - google on XDA to find its thread and installation if needed) or use TWRP, Advanced, its File Manager (again, google if needed to learn how to use).
Anyway, those skills and tools will be useful for you in future if you decided to go with Magisk, its modules, etc
- go to /data/adb/modules/Viper4Android FX and rename the existing post-fs-data.sh to post-fs-data.bak (just in case) and paste instead the post-fs-data.sh you extracted from my zip (see screenshot)
-reboot
- open V4A app, go to its settings and enable Legacy mode (again, see the screenshots in my post with the guide)
Click to expand...
Click to collapse
Dear brother
I have understood what you said, but I can't find zip file from your previous post, one more thing v4a fx working with legacy mode, but when I close legacy mode it cannot support.
Thanks for replying on my post.
wakram001 said:
Dear brother
I have understood what you said, but I can't find zip file from your previous post, one more thing v4a fx working with legacy mode, but when I close legacy mode it cannot support.
Thanks for replying on my post.
Dear brother
I have understood what you said, but I can't find zip file from your previous post, one more thing v4a fx working with legacy mode, but when I close legacy mode it cannot support.
Thanks for replying on my post.
Click to expand...
Click to collapse
Zip attachement was there, you have to go to that post and scroll down through the whole post, it was the last attachement (scrollshot below, click to open and scroll down, it's very long)
Do not read just my post there but study the whole thread and you will see that bobod made it working without Legacy mode on Mi 9T (Pro or not Pro). Google for the general V4A thread on XDA and you will see that most of users/phones can only work with Legacy mode. If you don't like, don't use V4A. Btw, what's wrong with, besides that is called 'legacy'
Dear brother
Still I can't find the zip file, I have goes through whole post and I can't get zip files.
I request you to pls upload once more....
Thanks for guidance...
wakram001 said:
Dear brother
Still I can't find the zip file, I have goes through whole post and I can't get zip files.
I request you to pls upload once more....
Thanks for guidance...
Click to expand...
Click to collapse
Go back to my first answer in this thread (post #2), answer to your original question about V4A.
Click on to the cited post there, to JUMP INTO
When you jumped to that other thread and the post there, scroll down till the end of the long post where ATTACHMENTS begin
CONTINUE SCROLLING through all atrachements, skip three screenshots and CLICK on the ZIP (last attachement) to start downloading
Really so hard?

Viper4androidfx and oos13

Has anyone been able to use v4afx on 13? It keeps asking to install the drivers.
Basically you have to remove everything from V4A first like in Magisk and the app itself. After the reboot you do the installation process again with Magisk but do not open V4A yet.
Put the attached file into /data/adb/modules/ViPER4AndroidFX and overwrite it if necessairy.
Now reboot and it should work with legacy mode on.
To make it work, v4a must "patch" audio_effects.xml file, but there is a problem, because earlier androids up to OOS11 have it stored in /vendor/etc, and it patched it without problem. OOS12 and 13 have that file too in this location, but it's generic file, don't contain Dolby Atmos, Nokia Ozo processing, Dolby VQE (message enhancer), and system don't use it...
From OOS 12, oneplus decided to store and use this file in /odm partition, exactly in /odm/etc.
V4a don't have possibility to patch it, that's why it tries to install "driver" again and again.
One more info.
mount -o bind /vendor/etc/audio_effects.xml /odm/etc/audio_effects.xml from post-fs-data.sh will replace that file in odm, and yes, it will work, but it also will kill your Dolby Atmos, OZO processing, VQE, because this file in /vendor/etc don't contain them.
Thanks for the input. I will give it a shot.
Idk if u have looked thoroughly, but I made a guide to install V4A: https://forum.xda-developers.com/t/...tall-viper4android-for-oneplus-8-pro.4388799/
Instead of using these weird files and workarounds to install V4A...
I would suggest downloading DDC and kernel files which can be found on my XDA thread.
Just download them and extract the .zip file only
Then download, install V4A repackaged, reboot and done
Try installing V4A repackaged: https://github.com/programminghoch10/ViPER4AndroidRepackaged/releases
The weird file you're referring to is from dorimanx himself.
[APP] [FIX] 100% working Viper4Android for Android 10-11-12 devices
If you are someone like me who encountered countless problems while installing Viper4Android on your Android 10 or 11 device and have no idea what to do then you are in the right place. Just download and install the apk from the attachment below...
forum.xda-developers.com

Categories

Resources