A lot of people have complained about stuttering in between App switching and gaming. This guide helps you disable Dynamic refresh rate through MagiskHide Prop Config, which is easier than setting it manually and safer to disable if it doesn't work.
Disclaimer: Disabling Dfps (Dynamic refresh rate) will degrade battery life with prolonged use. According to my personal testing, battery life (SOT) decreased by 10-18% on average. Only use for short periods of time.
Click to expand...
Click to collapse
Requirements:
- Unlocked and rooted with Magisk v21.0.
- busybox-ndk.
- MagiskHide Prop Config installed (used often to pass safetynet CTS but can be used to set custom Props).
Instructions:
1- Run SU in your terminal of choosing.
2- Run props.
3- choose option 5 "Add/edit custom props".
4- choose n "New custom prop".
5- type in:
Code:
ro.vendor.dfps.enable
6- Default value should be true, type in false to disable.
7- choose 2 "post-fs-data".
8- choose n, don't reboot yet.
9- choose n again to set another prop.
10- type in:
Code:
ro.vendor.smart_dfps.enable
11- Default value should be true, type in false to disable.
12- choose 2 "post-fs-data".
13- Reboot.
Only tested on stock MIUI. Try at your own risk!
It works on MIUI eu 12.0.3.0.
No stuttering anymore !
Thanks man !
Do this affect to battery performance?
Segamalaga said:
Do this affect to battery performance?
Click to expand...
Click to collapse
Yes. For me i get 1 hour less of SOT. That means if i get 7-9 hours on average, with this mod i get 6-8 hours instead.
Doesn't this mess with L1 ? Damn , I need to back up my persist img
Joakin2k said:
Doesn't this mess with L1 ? Damn , I need to back up my persist img
Click to expand...
Click to collapse
NOPE. It doesn't mess with L1 certification or any for that matter. This is a systemless "vendor" modification not "persist", and as such very easily uninstallable. See attached screenshots.
Also the payoff/difference is huge if you're a power user. Try consistent 120Hz vs. stuttering 120Hz (sometimes drops to 30Hz) and you will notice immediately.
Slim K said:
NOPE. It doesn't mess with L1 certification or any for that matter. This is a systemless "vendor" modification not "persist", and as such very easily uninstallable. See attached screenshots.
Also the payoff/difference is huge if you're a power user. Try consistent 120Hz vs. stuttering 120Hz (sometimes drops to 30Hz) and you will notice immediately.
Click to expand...
Click to collapse
Excellent explanation ! , I don't care for battery (if is not something out of control) I charge my phone always twice a day, I read that even Xiaomi EU and MIUI MIX has this issue ...
Going back to stock or EU for performance, aosp based are very green in performance...
Any Rom recommendation ?
Is there a way to set the refresh rate to 90hz and disable the dynamic refresh rate after that?
Joakin2k said:
Any Rom recommendation ?
Click to expand...
Click to collapse
I've tried all the custom ROMs available for our device and recommend stock for now. Since all of them are based on stock kernel anyway, they're all MIUI ROMs in my opinion, but you can't blame devs for choosing to patch Stock MIUI when we don't even have Device sources released. TWRP for the same reason, Dynamic partitions are scary.
Skeuomorphic said:
Is there a way to set the refresh rate to 90hz and disable the dynamic refresh rate after that?
Click to expand...
Click to collapse
As far as i know, refresh rate is handeled by an Activity:
Code:
com.xiaomi.misettings/.display.RefreshRate.RefreshRateActivity
which handels Dfps. In turn Dfps handels the frequencies in between 30Hz-120Hz depending on the process(Activity) on the forground.
I can't use my pc for a week atleast (broken from tinkering too much) to find a workaround, but good news! Theoretically, this guide should also work in custom roms with 90Hz option in settings app. Try it on a custom ROM and share your experience with us. [at your own risk ofc]
Thanks for taking your time to answer sir
Will this still work if i set the display to 60hz?
I'm having problems hiding magisk manager(no magisk hide), I already turn off dynamic hz thx to you , changed device fingerprint for pixel 4(want certification)... But when I want to hide magidk manager (a Bank app can see it -already marked in hide-) it says some error , I don't know if it's the Miui security app , this never happened on AOSP, I'm on stock poco X3 , root + props hide config + vanced ... Any tip ?
olujnap316 said:
Will this still work if i set the display to 60hz?
Click to expand...
Click to collapse
Yes. Setting 60Hz in the Settings app will set it to a constant 60Hz, conversely setting it to 120Hz will set it to a constant 120Hz as well.
Joakin2k said:
I'm having problems hiding magisk manager(no magisk hide), I already turn off dynamic hz thx to you , changed device fingerprint for pixel 4(want certification)... But when I want to hide magidk manager (a Bank app can see it -already marked in hide-) it says some error , I don't know if it's the Miui security app , this never happened on AOSP, I'm on stock poco X3 , root + props hide config + vanced ... Any tip ?
Click to expand...
Click to collapse
This is a fairly famous problem with Magisk Manger hiding and SELinux enforcing, but easily solvable. Do the following:
1- Go to Play store and turnoff Play Protect scanning (interferes with magisk manager repackiging itself aka Hiding).
2- Force stop Manager.
3- Open Manager again and choose another name and apply.
4- Profit.
If this still doesn't work, try this:
5- Go back to step 2 and then open terminal.
6- Type SU.
7- then set SELinux to permissive by inputting:
Code:
setenforce 0
8- continue with step 3
9- then set SELinux back to enforcing by inputting in terminal:
Code:
setenforce 1
10- Done
Man... Worked Flawlessly... Never had that issue on AOSP roms.
Thanks ! no need to turn on/off selinux enforcement.
But , really, thanks for your attention and detail , I'm impressed Sr
To make things easier and more risk free, i have attached a config file to automate this process. New steps are even easier! Do the following:
1- Install the aforementioned modules.
2- unzip the attached .zip file to the root of internal storage.
3- Reboot.
New settings should've been applied successfully after reboot and the config file will delete itself.
Slim K said:
To make things easier and more risk free, i have attached a config file to automate this process. New steps are even easier! Do the following:
1- Install the aforementioned modules.
2- unzip the attached .zip file to the root of internal storage.
3- Reboot.
New settings should've been applied successfully after reboot and the config file will delete itself.
Click to expand...
Click to collapse
Does this mean that the manual method enables back the dynamic refresh rate after every reboot? Which this conf will solve by placing the conf file at the root of internal storage before rebooting the phone?
Skeuomorphic said:
Does this mean that the manual method enables back the dynamic refresh rate after every reboot? Which this conf will solve by placing the conf file at the root of internal storage before rebooting the phone?
Click to expand...
Click to collapse
The Manual method as well as this method both persist through reboots. Only difference is the complexity of the initial setup, but that's it.
Great tutorial.any good guide to debloat safely without root
Doesn't seem to work there, checked with the power monitor, and it still switch between 120/90/60/30/1 fps depending on the app/menu I'm in
CaPicote said:
Doesn't seem to work there, checked with the power monitor, and it still switch between 120/90/60/30/1 fps depending on the app/menu I'm in
Click to expand...
Click to collapse
Can you provide me the following?:
1- MIUI vers. (i.e 12.0.3.0 QJGEUXM)
2- Go to terminal a run su and then:
Code:
getprop ro.vendor.smart_dfps.enable
-Output should be false, if it's true, then you didn't set it right.
I think a lot of people mix up framerate and refresh rate. Just an FYI, the thing that should be of interest is the refresh mode in power monitor. Check these screenshots, the circled value should stay at 120Hz consistently. Another screenshot I provided below without this mod shows 60Hz encircled when device not touched(which we don't want). The value on the right side of it (also in screenshots) is the framerate provided from the app (process) and indicates the actual frames displayed on the screen, if the screen isn't changing or moving, then there is nothing to display 120 frames about and will drop to 1 fps, which is completely normal.
Related
For those that don't know, here's how to enable Power saver mode on the vzw model.
You need:
Root
Root browser/ root explorer/ etc.
Navigate to system/ customize/ CID/ Default.xml. scroll about 1/3 of the way down until you find "def_hide_ui_powersaver" >1</item<item> and change value to "0".
Reboot device, then go to home screen, long press to add widget, select shortcuts, then down to power saver. This will put a shortcut to the power saver menu that is hidden from us.
Note that you must mount R/W or the edit will not work. This will not enable the quick setting or for it to show up in the regular power options menu but this will work for now.
Good luck
Thanks to aer0zer0 for pointing me in the right direction.
I can verify that this can also be enabled on unrooted devices as well. Credit goes to user l7777 in this post: http://forum.xda-developers.com/verizon-htc-10/help/verizon-version-missing-options-t3376634.
For the powersaver mode, try this from a computer with working ADB
Code:
Code:
adb shell "settings list secure | grep power"
If it returns something that looks like this
Code:
Code:
hide_ui_user_powersaver=1
Then try
Code:
Code:
adb shell "settings put secure hide_ui_user_powersaver 0"
This does not require root if done from a computer. It will require root if done from a terminal on the device. This is what works on an M9 running Marshmallow. It may or may not work on the 10. You can also try
Code:
Code:
adb shell "settings list secure"
To get a list of all the settings.
Click to expand...
Click to collapse
I had to restart my phone after making the change in ADB. The only thing that doesn't seem to work correctly is when I click on the Battery Saver Mode to edit the settings, I will receive an error message. The Battery Saver Mode will turn on and off with no issue.
Must have missed that one. I went through that post a couple days ago. Guess this will work for those that can't or don't know how to setup and use adb
Sent from my HTC6545LVW using Tapatalk
Evocm7 said:
For those that don't know, here's how to enable Power saver mode on the vzw model.
You need:
Root
Root browser/ root explorer/ etc.
Navigate to system/ customize/ CID/ Default.xml. scroll about 1/3 of the way down until you find "def_hide_ui_powersaver" >1</item<item> and change value to "0".
Reboot device, then go to home screen, long press to add widget, select shortcuts, then down to power saver. This will put a shortcut to the power saver menu that is hidden from us.
Note that you must mount R/W or the edit will not work. This will not enable the quick setting or for it to show up in the regular power options menu but this will work for now.
Good luck
Thanks to aer0zer0 for pointing me in the right direction.
Click to expand...
Click to collapse
If it is like the M9 on marshmallow, after making that edit, if you factory reset it, the menu option should appear in the standard menu. its alot easier to either put it in as a shortcut, or use xtended settings, and add it to the power menu, or gravity box, and add custom quicksetting tiles (1 of which being battery, it will also show battery temp and mAh remaining).
Once we get a deodexed based, or even a stock odex flash, we can make those edits prior to flash and it will be in the menu as normal
edit, i also believe if you edit the next line (120) def_hide_ui_user_powersaver and set it to 0, this is what will enable the menu on factory reset
Note that this survives reboot and/or power recycle. Using the adb approach for unrooted handsets, got it working on both my own and a test device.
UPDATE: So far as I can tell, the latest OTA to 1.19.605.22 breaks this ability.
hgoldner said:
Note that this survives reboot and/or power recycle. Using the adb approach for unrooted handsets, got it working on both my own and a test device.
UPDATE: So far as I can tell, the latest OTA to 1.19.605.22 breaks this ability.
Click to expand...
Click to collapse
Can confirm that the latest update definitely does break this ability (no root). =(
im_high_tech said:
Can confirm that the latest update definitely does break this ability (no root). =(
Click to expand...
Click to collapse
I think the only way to do this is to write to \system; so for those who don't want to flash a custom ROM or write to \system, it's out of reach for now.
And especially galling because the 10's on all the other carriers have the feature. Verizon kills it.
@andybones has it in the stock deodex base, but if you are working off of the odex base, the easiest way is probably gravitybox, and using the QS tile to toggle it (still requires root). Just make sure you are using systemless xposed to not touch the system partition as @hgoldner pointed out, if you need it.
by stock base, i mean OTA to 1.19.605.22
Battery Saver Mode Settings
You can change the power saver mode settings if you install the apk from apk mirror http://www.apkmirror.com/apk/htc-corporation/power/
klarthur said:
I can verify that this can also be enabled on unrooted devices as well. Credit goes to user l7777 in this post: http://forum.xda-developers.com/verizon-htc-10/help/verizon-version-missing-options-t3376634.
I had to restart my phone after making the change in ADB. The only thing that doesn't seem to work correctly is when I click on the Battery Saver Mode to edit the settings, I will receive an error message. The Battery Saver Mode will turn on and off with no issue.
Click to expand...
Click to collapse
This modification can be done using Magisk, without editing /system. You need to cache-mount the edited default.xml using Magisk, and Magisk mount the patched SystemUI.apk and HtcPowerManager.apk from @andybones' deodexed stock ROM. HUUUGE thanks to @Captain_Throwback for helping me figure this out and tolerating all-too-frequent stupid mistakes getting to this point, and, of course, none of this would be possible without the amazing efforts of @topjohnwu in creating Magisk in the first place.
I will post detailed instructions if someone is interested.
jackebuehner said:
You can change the power saver mode settings if you install the apk from apk mirror http://www.apkmirror.com/apk/htc-corporation/power/
Click to expand...
Click to collapse
I just tried installing this on my stock, non-rooted Verizon HTC 10 and it didn't give me any new options for power saver mode. I installed the most recent version from apk mirror and then rebooted. Everything looks the same. I'm on version 3.057.92923
Sent from my HTC6545LVW using Tapatalk
Chewieez said:
I just tried installing this on my stock, non-rooted Verizon HTC 10 and it didn't give me any new options for power saver mode. I installed the most recent version from apk mirror and then rebooted. Everything looks the same. I'm on version 3.057.92923
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
You have to follow the steps in post #2 before installing the APK does anything. The APK just makes it so that power saver mode settings doesn't crash.
jackebuehner said:
You have to follow the steps in post #2 before installing the APK does anything. The APK just makes it so that power saver mode settings doesn't crash.
Click to expand...
Click to collapse
I believe he is referencing the fact that not all of the available settings are shown. From screenshots of the book on the HTC one there should be settings for what power saver does.
CPU
Display
Vibration
Data connection
Useful settings. I would like to be able to turn down the processor without turning off data.
mrbacks said:
I believe he is referencing the fact that not all of the available settings are shown. From screenshots of the book on the HTC one there should be settings for what power saver does.
CPU
Display
Vibration
Data connection
Useful settings. I would like to be able to turn down the processor without turning off data.
Click to expand...
Click to collapse
You'll likely need a custom kernel for that, which means root access and either unlocked bootloader or S-OFF. Once you're in that boat, you'll need Magisk to clear Safety.net. It's not otherwise doable on pure unrooted stock. FWIW, if you are rooted, you can use @flar2's ElementalX kernel which is quite good, especially when used with the helper app allowing you to tweak all settings.
This Guide helps on configuring the A.R.I.S.E. (Auditory Research in Sound Enhancement) Sound System, including Viper4ARISE, in your Axon 7. This fixes the low volume problem for the EU version of AXON 7 2017G and increases the quality in all the models. Among other features it reconstruct the signal for streaming audio, increasing the spectrum and bringing more detail to the sound. It is also compatible with Dolby ATMOS. The official thread is complicated since it offers a lot of different options. Here I try to provide an easy and straightforward guide for beginners. After a while you will be able to get into the universe of profiles, settings and extras explained in the official thread.
REQUIREMENTS:
- Since this package modifies your system partition, it requires unlocked bootloader and root.
- Another requirement is to have the Busybox patch. If your root method is not including it, just grab one of the many free Busybox Apps from Play Store.
WARNINGS:
- Since this module is not systemless, in case of an OTA upgrade you will need to reflash the stock system before performing an OTA upgrade, apply the upgrade and then reinstall the Sound System.
- Unfortunately there is no uninstaller so keep a backup of your system partition before proceeding with the installation.
DOWNLOADS:
For a safe installation begin using ARISE Deuteronomy 2.2.3 Patched. Some people likes better the sound athmosphere provide by this version. The latest stable release ARISE Deuteronomy 2.3.3 and other versions can be found in the official thread. However 2.2.3 patched has proven to be very stable and fully compatible with our device. Later on you can test upgrading to the current or another release.
Since ARISE Sound Systems rewrites the audio configuration depending on your settings, you may need the Dolby ATMOS add-on too to recover this feature.
You'll have to flash it using TWRP recovery 3.0.3 or Flashfire app.
INSTALLATION:
STEP 0: Ensure you have a backup of your system partition and you have downloaded the ARISE Sound System to the internal or external storage of your phone.
STEP 1: Disable Dolby ATMOS.
STEP 2: Flash ARISE Sound System version 2.2.3 patched either using TWRP or Flashfire.
STEP 3: Reboot, play some music, open Viper4ARISE, activate the master switch for your headset and enjoy. Save your current configuration in the hamburger menu before testing new settings. You can also tune the phone speakers, bluetooth and external USB DAC settings.
STEP 4 (Optional): If Dolby ATMOS is not working after applying the patch, Flash the Dolby ATMOS add-on.
TROUBLESHOOTING:
- If ask for driver installation then Open your favorite file explorer and go to: /vendor/etc and rename audio_effects.conf to audio_effects.conf.bak, reboot and follow step 3 again.
- Ensure you have unlocked the system partition by typing reboot disemmcwp in the system or TWRP terminal or ADB shell. and repeat from step 1.
MY SETTINGS:
My recommendation is to leave Dolby ATMOS disabled unless you are watching a movie or concert. You do not have to disable Viper4ARISE when using Dolby ATMOS, however do never mix surround or spatial processing in both, it will be a mess. I share my general settings as an starting point, however you can experiment with all the parameters to find the sweet spot for your gear. Do not forget to save your current configuration in the hamburger menu before testing new settings, it is hard to remember the detailed configuration afterwards:
Check that the Headset HiFi setting in your Phone settings is set to Super. and for Viper4Arise set:
Master Power ON
Spectrum Extension ON (only for low quality streaming)
- Strength: 0.2
Dynamic System ON (Headset Only)
- Listening Device: Common Earphone v2
- Dynamic Bass: 18% for acoustic music and high dynamic range sources, up to 29% when listening dance/electronic
ViPER Bass OFF (only activate it if your headphones require extra Bass. In my case I have it disabled).
- Bass Mode: Natural
- Bass Frequency: 40hz
- Bass Boost: 13dB
VIPER Clarity ON (It can bring up pretty good detail to the sound).
- Clarity Mode: Natural
- Clarity: 6dB
Master Gate (Limiter)
- Channel Pan:0%
- Output Gain: 2.3dB (set more if you want more output volume without making quantization noise audible)
- Limit Threshold: 0dB
After setting it, just toggle the master switch several times to hear the difference. You will realize how much quality can be extracted from this excellent Axon 7 hardware.
How was your experience?
I love this mod, but every once in a while (like at least once or twice a day) I have to disable/ re-enable V4a or restart my phone because something goes wrong with it and it turns off (but shows it's on), like the driver unloads? So, I came back to the stock Dolby Atmos.
Hello, I'm having issues having viper to download drivers, for some reason, I am unable to rename audio_effects.conf with either es file explorer or root explorer despite es file explorer saying renamed successfully but it wouldn't change or show after reboot. I made sure they both have root permission. I have also checked if I have busybox installed but it came with systemless root. Root Switch shows selinux is set to permissive. So i'm scratching my head trying to figure out what the issue is.
PS. forgot to mention my bootloader is also unlocked.
vyurdin said:
Hello, I'm having issues having viper to download drivers, for some reason, I am unable to rename audio_effects.conf with either es file explorer or root explorer despite es file explorer saying renamed successfully but it wouldn't change or show after reboot. I made sure they both have root permission. I have also checked if I have busybox installed but it came with systemless root. Root Switch shows selinux is set to permissive. So i'm scratching my head trying to figure out what the issue is.
PS. forgot to mention my bootloader is also unlocked.
Click to expand...
Click to collapse
Did you ever do a "reboot disemmcwp"?
If not, turn on usb debugging, connect the phone to your computer and do a "adb reboot disemmcwp".
This disables the write protection on /system.
Loader009 said:
Did you ever do a "reboot disemmcwp"?
If not, turn on usb debugging, connect the phone to your computer and do a "adb reboot disemmcwp".
This disables the write protection on /system.
Click to expand...
Click to collapse
It works now, thanks! luckily I didn't have to edit that file.
Did anyone get it to work on Cm13? For me the driver fails to load with status abnormal, both with stable and alpha of Deuteronomy
nupi said:
Did anyone get it to work on Cm13? For me the driver fails to load with status abnormal, both with stable and alpha of Deuteronomy
Click to expand...
Click to collapse
Change the Selinux to Permissive on boot.
reV17 said:
Change the Selinux to Permissive on boot.
Click to expand...
Click to collapse
I shall try that. Can I put it back to enforcing after boot? I really dislike running devices on permissive...
nupi said:
I shall try that. Can I put it back to enforcing after boot? I really dislike running devices on permissive...
Click to expand...
Click to collapse
Unfortunately I don't believe it'll work if you put it back to enforcing.
tele_jas said:
I love this mod, but every once in a while (like at least once or twice a day) I have to disable/ re-enable V4a or restart my phone because something goes wrong with it and it turns off (but shows it's on), like the driver unloads? So, I came back to the stock Dolby Atmos.
Click to expand...
Click to collapse
Dolby ATMOS is meant for movies or concerts. Music sounds horrible with Dolby ATMOS.
I have been using this mod for about a week now in this device without any issue. I have tested the three proposed versions, and I have: the bootloader unlocked, F2FS filesystem, root, Xposed (all 9 modules working) and SafetyNet below this sound system.
What ROM are you using? Have you unlocked your system partition by doing a reboot disemmcwp in the terminal or adb shell? What version of ARISE Sound Systems are you using? How did you root your phone? Perhaps we could help you on this.
nupi said:
I shall try that. Can I put it back to enforcing after boot? I really dislike running devices on permissive...
Click to expand...
Click to collapse
You can try setting up V4A in enforcing mode using this guide.
for me it doesn't work, it ask for install drivers every time i reboot, and for no reason selinux don't stay to permissive after reboot (with selinuxmodechangerv3.2).
so i have abnormal statuts in viper4arise.
i try with stock b06, stock b08 and stock b09, it never work for me (maybe is because of b09 bootstack).
i also cannot use xposed framework anymore with b09, i can install it but if i activate any mod and reboot my phone bootloop.
Killerdog said:
i also cannot use xposed framework anymore with b09, i can install it but if i activate any mod and reboot my phone bootloop.
Click to expand...
Click to collapse
Did you try xposed 87? November security patches broke the earlier versions
nupi said:
Did you try xposed 87? November security patches broke the earlier versions
Click to expand...
Click to collapse
i try updating xposed inside the app. update is ok, but if i activate any module it bootloop at next reboot.
Oki said:
Dolby ATMOS is meant for movies or concerts. Music sounds horrible with Dolby ATMOS.
I have been using this mod for about a week now in this device without any issue. I have tested the three proposed versions, and I have, the bootloader unlocked, F2FS filesystem, root, Xposed and SafetyNet below this sound system.
What ROM are you using? Have you unlocked your system partition by doing a reboot disemmcwp in the terminal or adb shell? What version of ARISE Sound Systems are you using? How did you root your phone? Perhaps we could help you on this.
Click to expand...
Click to collapse
> I used the latest 2.3.3, flashed it twice in the past month (also tried an older one, but not sure which one)? Also flashed just V4a, with the same issue
> I'm running Z.A.D. Mix7 (V.3) ROM
> Xposed is installed for status bar changes only, and re-orientated volume
> I did do the disemmcwp (had to do this for my font and emoji changes to stick)
> I was one of the few that have the actual ZTE unlocked bootloader, then I followed DrakenFX thread on how to root.
But... the reason I went to ARISE, was because I wanted to use my favorite music player, n7 music player..... Which isn't compatible with Dolby Atmos. So, the issue may have been with n7? I'm currently trying to decide between XenoAmp and Double Twist Cloud Player as my player of choice. I also used PowerAmp for about 4 years, even ran the beta (build 703) up until about 3 months ago, but am tired of the same Gingerbread style UI it's had for the past 3 or 4 years.
So, that's where I'm at.... I may try it again without n7?
Killerdog said:
for me it doesn't work, it ask for install drivers every time i reboot, and for no reason selinux don't stay to permissive after reboot (with selinuxmodechangerv3.2).
so i have abnormal statuts in viper4arise.
i try with stock b06, stock b08 and stock b09, it never work for me (maybe is because of b09 bootstack).
i also cannot use xposed framework anymore with b09, i can install it but if i activate any mod and reboot my phone bootloop.
Click to expand...
Click to collapse
Try rooting your device using this method. The root includes Xposed (I have 8 modules up and running) and everything should be working. Probably using HelsAx7 as the base ROM could solve your problem.
tele_jas said:
> I used the latest 2.3.3, flashed it twice in the past month (also tried an older one, but not sure which one)? Also flashed just V4a, with the same issue
> I'm running Z.A.D. Mix7 (V.3) ROM
> Xposed is installed for status bar changes only, and re-orientated volume
> I did do the disemmcwp (had to do this for my font and emoji changes to stick)
> I was one of the few that have the actual ZTE unlocked bootloader, then I followed DrakenFX thread on how to root.
But... the reason I went to ARISE, was because I wanted to use my favorite music player, n7 music player..... Which isn't compatible with Dolby Atmos. So, the issue may have been with n7? I'm currently trying to decide between XenoAmp and Double Twist Cloud Player as my player of choice. I also used PowerAmp for about 4 years, even ran the beta (build 703) up until about 3 months ago, but am tired of the same Gingerbread style UI it's had for the past 3 or 4 years.
So, that's where I'm at.... I may try it again without n7?
Click to expand...
Click to collapse
PowerAmp and Player PRO are the best in sound quality, the second is even better. And both seem to be working fine with Viper4ARISE. What kind of source are you playing (bandwidth and bitdepth)?
This makes my music sound sweet! I don't know if anyone experienced this but my phone has 0% sleep and is always 100% awake and heats up like an oven after flashing this I restored my backup and it's okay now
Teet1 said:
This makes my music sound sweet! I don't know if anyone experienced this but my phone has 0% sleep and is always 100% awake and heats up like an oven after flashing this I restored my backup and it's okay now
Click to expand...
Click to collapse
You can use wake lock detector to check what's wrong. The package is pretty stable. Could you please provide some more info (device, ROM, root method, media player, ARISE version, Viper4A configuration...)?
Oki said:
Dolby ATMOS is meant for movies or concerts. Music sounds horrible with Dolby ATMOS.
I have been using this mod for about a week now in this device without any issue. I have tested the three proposed versions, and I have, the bootloader unlocked, F2FS filesystem, root, Xposed and SafetyNet below this sound system.
What ROM are you using? Have you unlocked your system partition by doing a reboot disemmcwp in the terminal or adb shell? What version of ARISE Sound Systems are you using? How did you root your phone? Perhaps we could help you on this.
Click to expand...
Click to collapse
I'm wondering if you can help me with another issue I'm experiencing since I last posted here. My battery started draining really fast since I flashed the audio patch, I'm aware that's normal for viper but this is abnormal since the battery drains when the phone is not in use and it tends to stay warm. I have never had this issue when I had viper on my note 4.
The steps I have done for my phone:
Root method by jcadduono’s official thread in your safety net guide with success.
Done all steps with safetynet steps from above with success.
And I did the audio upgrade from this thread with success by using your preferred one.
And that's when my phone started draining more than it usually does for viper and being slight warm when not in use. I have already done a wipe before I did all these methods.
EDIT: Someone already mentioned the issue I'm having and I did not see that on mobile. I'm running all of those on A2017U stock rom running on b29 for additional info. I used stock music player, usb audio player pro (eXtream Software Development) for external dac and Equalizer + (DJiT) which i rarely use. I'll install wakelock detecter and ill report back what I find.
Summary && Detail:
1, you can convert the application to VR mode to watch and operate.
2, support the Bluetooth handle.
3, VR mode to support the up and down volume keys to control the screen size.
4, support touch screen operation, touch screen area from the upper left corner of the physical screen to start mapping
5, there may be some BUG, disable module can be restored
ScreenShot && Download:
http://repo.xposed.info/module/com.app360.app360
YOUTUBE:
https://www.youtube.com/watch?v=qyROy_zLaQA
Major update!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
detail:
Support global VR mode in landscape for all of android apps.
This function is tested on Android 5.1 and Android 6, Android5.0 has not yet tested.
This function is strong enough for having no friends
using:
open settings app,find Accessibility,switch on Magnification gestrues.when play apps in landscape,triple tapping the screen,then you will in VR mode.
notice:
miui should allow system alert window
if not work,please check auto run and record screen permission
any suggesting can email to [email protected]
app2vr said:
Summary && Detail:
1, you can convert the application to VR mode to watch and operate.
2, support the Bluetooth handle.
3, VR mode to support the up and down volume keys to control the screen size.
4, support touch screen operation, touch screen area from the upper left corner of the physical screen to start mapping
5, there may be some BUG, restart the phone can be restored
ScreenShot && Download:
repo.xposed.info/module/com.app360.app360
Click to expand...
Click to collapse
Wow is this real ?! I always wanted to do that
I'm testing it on a nexus 6. I'll report bug with logs if needed
thank you !!!!
BUG
Well it's not working on nexus 6 for me. It shows a dark screen when launching an app through app2vr interface.
Logs attached
also why so many files comes on /sdcard after instalation?? It looks like malicious app...
Dead-neM said:
Wow is this real ?! I always wanted to do that
I'm testing it on a nexus 6. I'll report bug with logs if needed
thank you !!!!
BUG
Well it's not working on nexus 6 for me. It shows a dark screen when launching an app through app2vr interface.
Logs attached
also why so many files comes on /sdcard after instalation?? It looks like malicious app...
Click to expand...
Click to collapse
Hi,thank you very much,because my application supports xposed mode and normal root mode, so i need to release the GoogleDoor and Lib files in sdcard for injection into the system_server process to complete the functional patch, the program does not contain malicious code, you can decompile to confirm, according to your feedback Log, I modified the program, the current xposed mode does not need to click to install, activate the module can be used after the restart, this is the beta version, does not support all types of app to be converted into vr mode,the current upgrade to the 19 version,this version had repaired your feedback.
app is really available
app is really available, but in the early stages of development, I will be the fastest speed to solve the problem.
Zenfone2 ze331ml lollipop 5.0.1 here.
Installed, allowed root to modify system partition, tried to start 920 text editor and just got a black screen.
Phone did not react to nothing, home button, power button, nothing. seems dead.
After a while adb via usb started working, and i issued a reboot from there.
Next, i've got a bootloop; i disabled xposed and the bootloop did not went away!
Fortunately i've had a complete twrp backup...
I tried to understand what it did to my system app, but the source on github is not available.
app2vr said:
Hi,thank you very much,because my application supports xposed mode and normal root mode, so i need to release the GoogleDoor and Lib files in sdcard for injection into the system_server process to complete the functional patch, the program does not contain malicious code, you can decompile to confirm, according to your feedback Log, I modified the program, the current xposed mode does not need to click to install, activate the module can be used after the restart, this is the beta version, does not support all types of app to be converted into vr mode,the current upgrade to the 19 version,this version had repaired your feedback.
Click to expand...
Click to collapse
Hi, thanks for the app
U mentioned about root mode. Any case this works with nougat in root mod I'm just asking
app2vr said:
Hi,thank you very much,because my application supports xposed mode and normal root mode, so i need to release the GoogleDoor and Lib files in sdcard for injection into the system_server process to complete the functional patch, the program does not contain malicious code, you can decompile to confirm, according to your feedback Log, I modified the program, the current xposed mode does not need to click to install, activate the module can be used after the restart, this is the beta version, does not support all types of app to be converted into vr mode,the current upgrade to the 19 version,this version had repaired your feedback.
Click to expand...
Click to collapse
Awesome I'll try again and report back. Thank you for being super fast.
Just one question what is the demo.apk on /sdcard?
When I try opening an application, a black screen just shows any way I can fix this? I am on a Redmi Note 3.
Dead-neM said:
Awesome I'll try again and report back. Thank you for being super fast.
Just one question what is the demo.apk on /sdcard?
Click to expand...
Click to collapse
DemoInject2.apk contains the function code,processing function logic in native layer is very complicated ,processing in java layer by using dexclassloader can enhance the stability.thanks
kokoko3k said:
Zenfone2 ze331ml lollipop 5.0.1 here.
Installed, allowed root to modify system partition, tried to start 920 text editor and just got a black screen.
Phone did not react to nothing, home button, power button, nothing. seems dead.
After a while adb via usb started working, and i issued a reboot from there.
Next, i've got a bootloop; i disabled xposed and the bootloop did not went away!
Fortunately i've had a complete twrp backup...
I tried to understand what it did to my system app, but the source on github is not available.
Click to expand...
Click to collapse
Very sorry,its my fault, I am tested on Android 5.1, Android6.0 machine, can you provide some log information? MainXposed.java is not confused, because the visual processing part of the code is not my work,so its hard to opensource.
reversegear said:
Hi, thanks for the app
U mentioned about root mode. Any case this works with nougat in root mod I'm just asking
Click to expand...
Click to collapse
Today, I experimented with Android N, I found that when I injected into the system_server, android :: AndroidRuntime :: getJavaVM () often return null ,so i can not load the function code in DemonInject.apk with jni_env , i am looking for solution..
APP2VR now can run on nougat when selinux disabled.
Gtxinsane said:
When I try opening an application, a black screen just shows any way I can fix this? I am on a Redmi Note 3.
Click to expand...
Click to collapse
can you provider me some log? I will resolve your problem as quickly as possible!
On v20 it's still not working on a nexus6. Problem looks the same. Video and Logs below.
https://drive.google.com/folderview?id=0BwCC2VJYgCavdzUyODhjejAtZXM
waiting for stable build
Dead-neM said:
On v20 it's still not working on a nexus6. Problem looks the same. Video and Logs below.
https://drive.google.com/folderview?id=0BwCC2VJYgCavdzUyODhjejAtZXM
Click to expand...
Click to collapse
From the Log analysis, APP2VR Xposed Module is not enabled, I Hooked startActivity but no log output, you can uninstall and reinstall V21 version.
app2vr said:
From the Log analysis, APP2VR Xposed Module is not enabled, I Hooked startActivity but no log output, you can uninstall and reinstall V21 version.
Click to expand...
Click to collapse
Why no suports phone root
After “put your device into cardboard“ just a black screen with the settings symbol, but not clickable + difficulties exiting the app.
InFocus M808 modded Stock 6.0
Could you include two key options.
1. To disable gyroscope, or to show in static frame.
2. To adjust FOV.
Sent from my Lenovo X3a40 using XDA Labs
BUGS
In Cardboard mode: It only shows main activity, app can not be controlled by the headset, Moga gamepad doesnt work (moga universal driver) and probably other controllers, and yoi have to look towards fixed direction
In Global mode: Not all the screen is visible through the vr glass (bigger than it should be)
please support locked mode screen
Hello everyone!
I'm happy to announce that I successfully installed android 12 on nairo, this guide comes with post install tweaks (that to me are the most important part)! I used a XT2075-3 Dual sim.
Warning: I don't take any responsibility if you brick your phone. This is just how I achieved this result. Read the guide in its entirety first! Back up everything with TWRP on an external drive.
I've tried 2 times and the first time it worked properly except for some things that we (thanks also to @wesleyvanneck12345678 ) have found a fix for:
THINGS NOT WORKING AND THINGS TO FIX ON POST-INSTALLNot working (READ CAREFULLY)
TWRP doesn't work, at least the one by vache, THEREFORE INSTALL MAGISK ON ANDROID 11! Thanks (and sorry) to @Zainullahk1234 for signaling this problem on the guide
Post-install fixes
The clock and notification are behind the double hole punch, we'll need to fix the statusbar padding on post-install.
Audio routing needs some tweaks, we have to fix some things in developer options and phh's patches (thanks to @wesleyvanneck12345678 audio was a deal breaker for me and they helped me fix it)
AT THE TIME OF WRITING BLUETOOTH HEADSET DOESN'T WORK, if you can help on that let's discuss it on the comments[ SOLVED ] yay!
GSI INSTALLATION (install magisk while on android 11)Ok let's start, actually before that i recommend backing up all partitions on a hard drive via twrp, it literally saved me from bricking my phone the first time so you should do it too.
First of all you should obviously unlock your bootloader, google is your friend on that.
I SUGGEST INSTALLING MAGISK WHILE YOU ARE ON ANDROID 11 WITH TWRP!
Install Pixel Experience Alpha, I've used the arm64 vndklite version i'm not sure if it's the correct one but it worked. I followed this guide on how to install a gsi rom on a super partiton phone.
After installing the rom should work properly by itself, the audio works only through the speakers and the clock and notifications are under the double cutout cameras, let's see how to fix both.
POST-INSTALLAUDIO FIX
Open Developer Options in settings
Find Disable Bluetooth Hardware Offload and turn on the setting
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reboot
Go in settings and find Phh Treble Settings
Open Misc features
Enable Use alternate way to detect headsets
Scroll down and find Force-disable A2DP offload and turn it on
That's it, reboot and both aux and bluetooth headset should work!
STATUSBAR PADDING FIX (portrait mode)
After installing Magisk we can fix the statusbar. Install this module in magisk manager by downloading the zip from XDA and selecting it from your download folder.
The installation of this module is unusual, when installing it will ask you to install some presets on the phone, use the volume buttons to choose the CUSTOM option (last one, not the pixel 5), this will create 5 text files in the storage of your phone.
Reboot if you want (idk if it's necessary but I did it anyway)
Use a file manager like total commander to navigate in your storage/emulated/0/com.logmd.n3o/ there will be 5 files.
Open the custom1left.txt, delete the number you see and write 240, save and close. 240 is the pixel distance from the left side of the screen, this size doesn't give me problems.
OPTIONAL: open the custom2left.txt and a different number like 260 if you want the clock more distant from the cutouts. Save and exit.
Open magisk manager and run the installation of the module again
Select the custom option another time, this time it will check the folder with the files we edited for new instructions.
Reboot
CRUCIAL if you are clumsy: connect the phone (with usb debug enabled) to a pc and with ADB run the command "adb devices" and tell the prompt on your phone to always grant permissions from that pc. This will help if you mess up the next steps by selecting a wrong option.
Once booted go to developer option in settings and find Display Cutout under Design settings.
!!!BE VERY CAREFUL NOT TO SELECT ANYTHING ELSE THAN N3O OPTIONS!!! Stock overlay display cutouts are bugged on android 12 and if you select one you will have to disable it via adb.
Select the option you we created earlier it will be called "N3O CST left custom1 (240px)"
That's it, check if it stays after reboot but there should be no problems.
As you can see it works in the Notification panel too!
Ta-Da! (I guess) Let's have a conversation on this and find a fix for bt maybe lol. [SOLVED]
THANKS TO:
PIXEL EXP TEAM:@jhenrique09@phhusson@AndyYan@eremitein@poncesSTATUSBAR FIX:@LOGMDAUDIO FIX RESEARCHER :@wesleyvanneck12345678
Tommy0000 said:
Hello everyone!
I'm happy to announce that I successfully installed android 12 on nairo, this "guide" comes with post install tweaks (that to me are the most important part)! I used a XT2075-3 Dual sim.
Warning: I don't take any responsibility if you brick your phone. This is just how I achieved this result. Read the guide in its entirety first!
I've tried 2 times and the first time it worked properly except for some things that we (thanks also to @wesleyvanneck12345678 ) have found a fix for:
THINGS NOT WORKING AND THINGS TO FIX ON POST-INSTALL
TWRP didn't work, at least the one by vache, this still doesn't work but i personally don't care much because this rom comes with magisk preinstalled.
The clock and notification are behind the double hole punch, we'll need to fix the statusbar padding on post-install.
The aux output didn't work the first time, we have to tweak some things in developer options and phh's patches (thanks to @wesleyvanneck12345678 audio was a deal breaker for me and they helped me fix it)
AT THE TIME OF WRITING BLUETOOTH HEADSET DOESN'T WORK, if you can help on that let's discuss it on the comments
GSI INSTALLATIONOk let's start, actually before that i recommend backing up all partitions on a hard drive via twrp, it literally saved me from bricking my phone the first time so you should do it too.
First of all you should obviously unlock your bootloader, google is your friend on that.
Install Pixel Experience Alpha, I've used the arm64 vndklite version i'm not sure if it's the correct one but it worked. I followed this guide on how to install a gsi rom on a super partiton phone.
After installing the rom should work properly by itself, the audio works only through the speakers and the clock and notifications are under the double cutout cameras, let's see how to fix both.
POST-INSTALLAUDIO FIX (this needs a better solution)PREMISE: This works only if you don't need Bluetooth headsets because we are going to disable it I think (I'm not an expert)
Open Developer Options in settings.
Find Disable Bluetooth Hardware Offload and enable it
Reboot
Go in settings and find Phh Treble Settings
Open Misc features
Enable Force headset switch (Huawei defaul...
Enable Use alternate way to detect headsets
That's it, reboot for safety measure.
If you know how to do this in a better way please help us below! I don't need bluetooth that much but it's better to have it than not.
STATUSBAR PADDING FIX (portrait mode)View attachment 5464363
After installing Magisk we can fix the statusbar. Install this module in magisk manager by downloading the zip from XDA and selecting it from your download folder.
The installation of this module is unusual, when installing it will ask you to install some presets on the phone, use the volume buttons to choose the CUSTOM option (last one, not the pixel 5), this will create 5 text files in the storage of your phone.
Reboot if you want (idk if it's necessary but I did it anyway)
Use a file manager like total commander to navigate in your storage/emulated/0/com.logmd.n3o/ there will be 5 files.
Open the custom1left.txt, delete the number you see and write 240, save and close. 240 is the pixel distance from the left side of the screen, this size doesn't give me problems.
OPTIONAL: open the custom2left.txt and a different number like 260 if you want the clock more distant from the cutouts. Save and exit.
Open magisk manager and run the installation of the module again
Select the custom option another time, this time it will check the folder with the files we edited for new instructions.
Reboot
CRUCIAL if you are clumsy: connect the phone (with usb debug enabled) to a pc and with ADB run the command "adb devices" and tell the prompt on your phone to always grant permissions from that pc. This will help if you mess up the next steps by selecting a wrong option.
Once booted go to developer option in settings and find Display Cutout under Design settings.
!!!BE VERY CAREFUL NOT TO SELECT ANYTHING ELSE THAN N3O OPTIONS!!! Stock overlay display cutouts are bugged on android 12 and if you select one you will have to disable it via adb.
Select the option you we created earlier it will be called "N3O CST left custom1 (240px)"
That's it, check if it stays after reboot but there should be no problems.
View attachment 5464365
As you can see it works in the Notification panel too!
Ta-Da! (I guess) Let's have a conversation on this and find a fix for bt maybe lol.
THANKS TO:
PIXEL EXP TEAM:@jhenrique09@phhusson@AndyYan@eremitein@poncesSTATUSBAR FIX:@LOGMDAUDIO FIX RESEARCHER :@wesleyvanneck12345678
Click to expand...
Click to collapse
bluetooth headset can fixed by going in develpers setting and turning on disable bluetooth a2dp hardware offload and that looks like this:
wesleyvanneck12345678 said:
bluetooth headset can fixed by going in develpers setting and turning on disable bluetooth a2dp hardware offload
Click to expand...
Click to collapse
Ye but that way aux/jack stops working for me
Tommy0000 said:
Ye but that way aux/jack stops working for me
Click to expand...
Click to collapse
heh i got both enbled and it works for me
wesleyvanneck12345678 said:
heh i got both enbled and it works for me
Click to expand...
Click to collapse
Ok! I'll try!
Wich one have you enabled?
disable Bluetooth offload in dev options
force switch in phh patches
alternate switch in phh patches
Maybe it's a coded not supported by my headset
Tommy0000 said:
Ye but that way aux/jack stops working for me
Click to expand...
Click to collapse
foudn the fix go to phh treble settings > misc features and enable use alternate way to detect headsets
Can you tell me, just to be sure what is enabled and what not? @wesleyvanneck12345678
Tommy0000 said:
Ok! I'll try!
Wich one have you enabled?
disable Bluetooth offload in dev options
force switch in phh patches
alternate switch in phh patches
Maybe it's a coded not supported by my headset
Click to expand...
Click to collapse
Tommy0000 said:
Can you tell me, just to be sure what is enabled and what not? @wesleyvanneck12345678
Click to expand...
Click to collapse
1 and 3 and also dont forget to enable disable Bluetooth offload in phh treble settings > misc features
wesleyvanneck12345678 said:
1 and 3 and also dont forget to enable disable Bluetooth offload in phh treble settings > misc features
Click to expand...
Click to collapse
Thanks, i'm going to update the guide!
It works for me too!
Tommy0000 said:
Thanks, i'm going to update the guide!
It works for me too!
Click to expand...
Click to collapse
btw you sayed bluetooth audio doesnt work it does work with same settings
wesleyvanneck12345678 said:
btw you sayed bluetooth audio doesnt work it does work with same settings
Click to expand...
Click to collapse
I hadn't enable offload fix in phh's patches menu, maybe it was that, maybe I forgot to turn on something else when I tried
wesleyvanneck12345678 said:
btw you sayed bluetooth audio doesnt work it does work with same set
wesleyvanneck12345678 said:
btw you sayed bluetooth audio doesnt work it does work with same settings
Click to expand...
Click to collapse
Click to expand...
Click to collapse
you have to enable this to for bluetooth audio phh treble settings > misc and then features force-disable A2DP offload
so that in develpers settings and treble settings has to be anbled for bluetooth audio for aux force switch in phh patches
Tommy0000 said:
Hello everyone!
I'm happy to announce that I successfully installed android 12 on nairo, this guide comes with post install tweaks (that to me are the most important part)! I used a XT2075-3 Dual sim.
Warning: I don't take any responsibility if you brick your phone. This is just how I achieved this result. Read the guide in its entirety first! Back up everything with TWRP on an external drive.
I've tried 2 times and the first time it worked properly except for some things that we (thanks also to @wesleyvanneck12345678 ) have found a fix for:
THINGS NOT WORKING AND THINGS TO FIX ON POST-INSTALLNot working
TWRP didn't work, at least the one by vache, this still doesn't work but i personally don't care much because this rom comes with magisk preinstalled.
Post-install fixes
The clock and notification are behind the double hole punch, we'll need to fix the statusbar padding on post-install.
Audio routing needs some tweaks, we have to fix some things in developer options and phh's patches (thanks to @wesleyvanneck12345678 audio was a deal breaker for me and they helped me fix it)
AT THE TIME OF WRITING BLUETOOTH HEADSET DOESN'T WORK, if you can help on that let's discuss it on the comments[ SOLVED ] yay!
GSI INSTALLATIONOk let's start, actually before that i recommend backing up all partitions on a hard drive via twrp, it literally saved me from bricking my phone the first time so you should do it too.
First of all you should obviously unlock your bootloader, google is your friend on that.
Install Pixel Experience Alpha, I've used the arm64 vndklite version i'm not sure if it's the correct one but it worked. I followed this guide on how to install a gsi rom on a super partiton phone.
After installing the rom should work properly by itself, the audio works only through the speakers and the clock and notifications are under the double cutout cameras, let's see how to fix both.
POST-INSTALLAUDIO FIX
Open Developer Options in settings
Find Disable Bluetooth Hardware Offload and turn on the setting
View attachment 5464431
Reboot
Go in settings and find Phh Treble Settings
Open Misc features
Enable Use alternate way to detect headsets
Scroll down and find Force-disable A2DP offload and turn it on
That's it, reboot and both aux and bluetooth headset should work!
STATUSBAR PADDING FIX (portrait mode)View attachment 5464363
After installing Magisk we can fix the statusbar. Install this module in magisk manager by downloading the zip from XDA and selecting it from your download folder.
The installation of this module is unusual, when installing it will ask you to install some presets on the phone, use the volume buttons to choose the CUSTOM option (last one, not the pixel 5), this will create 5 text files in the storage of your phone.
Reboot if you want (idk if it's necessary but I did it anyway)
Use a file manager like total commander to navigate in your storage/emulated/0/com.logmd.n3o/ there will be 5 files.
Open the custom1left.txt, delete the number you see and write 240, save and close. 240 is the pixel distance from the left side of the screen, this size doesn't give me problems.
OPTIONAL: open the custom2left.txt and a different number like 260 if you want the clock more distant from the cutouts. Save and exit.
Open magisk manager and run the installation of the module again
Select the custom option another time, this time it will check the folder with the files we edited for new instructions.
Reboot
CRUCIAL if you are clumsy: connect the phone (with usb debug enabled) to a pc and with ADB run the command "adb devices" and tell the prompt on your phone to always grant permissions from that pc. This will help if you mess up the next steps by selecting a wrong option.
Once booted go to developer option in settings and find Display Cutout under Design settings.
!!!BE VERY CAREFUL NOT TO SELECT ANYTHING ELSE THAN N3O OPTIONS!!! Stock overlay display cutouts are bugged on android 12 and if you select one you will have to disable it via adb.
Select the option you we created earlier it will be called "N3O CST left custom1 (240px)"
That's it, check if it stays after reboot but there should be no problems.
View attachment 5464365
As you can see it works in the Notification panel too!
Ta-Da! (I guess) Let's have a conversation on this and find a fix for bt maybe lol. [SOLVED]
THANKS TO:
PIXEL EXP TEAM:@jhenrique09@phhusson@AndyYan@eremitein@poncesSTATUSBAR FIX:@LOGMDAUDIO FIX RESEARCHER :@wesleyvanneck12345678
Click to expand...
Click to collapse
Holy crap thank you sooo much.. I love this pixel gsi 12 ROM running on moto g stylus 5g 2021..
Bluetooth and 2g only for calls and text were my only bugs...
Now Bluetooth works flawslesy with this guide...
Any fix for volte..
I tried to flash the Qualcomm zip fix but twrp error"arcititure unknown"'
Anyone???
Awesome ROM guys... keep up the great work .
jhjhjhjhjhjh said:
Holy crap thank you sooo much.. I love this pixel gsi 12 ROM running on moto g stylus 5g 2021..
Bluetooth and 2g only for calls and text were my only bugs...
Now Bluetooth works flawslesy with this guide...
Any fix for volte..
I tried to flash the Qualcomm zip fix but twrp error"arcititure unknown"'
Anyone???
Awesome ROM guys... keep up the great work .
Click to expand...
Click to collapse
With Bluetooth you mean Bluetooth headsets? You should try with patches for audio that i included in the guide, idk much about it tho :/
Tommy0000 said:
With Bluetooth you mean Bluetooth headsets? You should try with patches for audio that i included in the guide, idk much about it tho :/
Click to expand...
Click to collapse
Yes my Bluetooth before I found this guide my audio was choppy and distorted...now it's just like my stock ROM...I'm so happy now...thanks..
Viper and Dolby both working on with Bluetooth as well...loving it!!!!
Again I just need a volte fix...I have to turn off volte and the data turns to "E" then calls and text work fine...but on LTE/5g no calls or MMS.. I use a free text app for now as a work around...
jhjhjhjhjhjh said:
Yes my Bluetooth before I found this guide my audio was choppy and distorted...now it's just like my stock ROM...I'm so happy now...thanks..
Viper and Dolby both working on with Bluetooth as well...loving it!!!!
Again I just need a volte fix...I have to turn off volte and the data turns to "E" then calls and text work fine...but on LTE/5g no calls or MMS.. I use a free text app for now as a work around...
Click to expand...
Click to collapse
There is a volte fix in patches too i think, also to me the preferred data connection was 3g maybe try to change it
3g setting puts my phone in "E' Wich is 2g speeds basically..I get calls and MMS but slow data...I have a 5 g phone that supposed to have MMS and calls over LTE/NR....
Tommy0000 said:
There is a volte fix in patches too i think, also to me the preferred data connection was 3g maybe try to change it
Click to expand...
Click to collapse
jhjhjhjhjhjh said:
3g setting puts my phone in "E' Wich is 2g speeds basically..I get calls and MMS but slow data...I have a 5 g phone that supposed to have MMS and calls over LTE/NR....
Click to expand...
Click to collapse
Yes this doesn't work do some roms do give you 5g do its android 11
t
Tommy0000 said:
Hello everyone!
I'm happy to announce that I successfully installed android 12 on nairo, this guide comes with post install tweaks (that to me are the most important part)! I used a XT2075-3 Dual sim.
Warning: I don't take any responsibility if you brick your phone. This is just how I achieved this result. Read the guide in its entirety first! Back up everything with TWRP on an external drive.
I've tried 2 times and the first time it worked properly except for some things that we (thanks also to @wesleyvanneck12345678 ) have found a fix for:
THINGS NOT WORKING AND THINGS TO FIX ON POST-INSTALLNot working
TWRP didn't work, at least the one by vache, this still doesn't work but i personally don't care much because this rom comes with magisk preinstalled.
Post-install fixes
The clock and notification are behind the double hole punch, we'll need to fix the statusbar padding on post-install.
Audio routing needs some tweaks, we have to fix some things in developer options and phh's patches (thanks to @wesleyvanneck12345678 audio was a deal breaker for me and they helped me fix it)
AT THE TIME OF WRITING BLUETOOTH HEADSET DOESN'T WORK, if you can help on that let's discuss it on the comments[ SOLVED ] yay!
GSI INSTALLATIONOk let's start, actually before that i recommend backing up all partitions on a hard drive via twrp, it literally saved me from bricking my phone the first time so you should do it too.
First of all you should obviously unlock your bootloader, google is your friend on that.
Install Pixel Experience Alpha, I've used the arm64 vndklite version i'm not sure if it's the correct one but it worked. I followed this guide on how to install a gsi rom on a super partiton phone.
After installing the rom should work properly by itself, the audio works only through the speakers and the clock and notifications are under the double cutout cameras, let's see how to fix both.
POST-INSTALLAUDIO FIX
Open Developer Options in settings
Find Disable Bluetooth Hardware Offload and turn on the setting
View attachment 5464431
Reboot
Go in settings and find Phh Treble Settings
Open Misc features
Enable Use alternate way to detect headsets
Scroll down and find Force-disable A2DP offload and turn it on
That's it, reboot and both aux and bluetooth headset should work!
STATUSBAR PADDING FIX (portrait mode)View attachment 5464363
After installing Magisk we can fix the statusbar. Install this module in magisk manager by downloading the zip from XDA and selecting it from your download folder.
The installation of this module is unusual, when installing it will ask you to install some presets on the phone, use the volume buttons to choose the CUSTOM option (last one, not the pixel 5), this will create 5 text files in the storage of your phone.
Reboot if you want (idk if it's necessary but I did it anyway)
Use a file manager like total commander to navigate in your storage/emulated/0/com.logmd.n3o/ there will be 5 files.
Open the custom1left.txt, delete the number you see and write 240, save and close. 240 is the pixel distance from the left side of the screen, this size doesn't give me problems.
OPTIONAL: open the custom2left.txt and a different number like 260 if you want the clock more distant from the cutouts. Save and exit.
Open magisk manager and run the installation of the module again
Select the custom option another time, this time it will check the folder with the files we edited for new instructions.
Reboot
CRUCIAL if you are clumsy: connect the phone (with usb debug enabled) to a pc and with ADB run the command "adb devices" and tell the prompt on your phone to always grant permissions from that pc. This will help if you mess up the next steps by selecting a wrong option.
Once booted go to developer option in settings and find Display Cutout under Design settings.
!!!BE VERY CAREFUL NOT TO SELECT ANYTHING ELSE THAN N3O OPTIONS!!! Stock overlay display cutouts are bugged on android 12 and if you select one you will have to disable it via adb.
Select the option you we created earlier it will be called "N3O CST left custom1 (240px)"
That's it, check if it stays after reboot but there should be no problems.
View attachment 5464365
As you can see it works in the Notification panel too!
Ta-Da! (I guess) Let's have a conversation on this and find a fix for bt maybe lol. [SOLVED]
THANKS TO:
PIXEL EXP TEAM:@jhenrique09@phhusson@AndyYan@eremitein@poncesSTATUSBAR FIX:@LOGMDAUDIO FIX RESEARCHER :@wesleyvanneck12345678
Click to expand...
Click to collapse
when i installed it it didnt come with magisk?
im on arm64 ab
Zainullahk1234 said:
t
when i installed it it didnt come with magisk?
im on arm64 ab
Click to expand...
Click to collapse
Ohhh very weird, it happened to me once, try reinstalling system without wiping user data and using another date build, maybe they forgot to put it in :/
Kirisakura-Kernel for the Sony Xperia 1 IV
Hello everyone,
To keep it short: Here is Kirisakura- GKI - Kernel for the Sony Xperia 1 IV aka Nagara. Nagara is the internal codename for this years development platform of Sony Mark IV devices.
I would appreciate if everybody that flashes the kernel, reads at least once through this opening post and the following ones.
Kirisakura - Kernel is designed to bring a handful of beneficial features to the device, while ensuring excellent performance and smoothness to get you safely through the day!
If you expect a custom kernel to magically improve your devices battery life manifold and this is your only priority then this might not be the right place for you.
There´s also a cpu-battery saver mode that cuts back the CPU max- freqs, but without the disadvantages like delayed notifications from built into the system user-space power-saving modes.
If that got your curious, I welcome you to continue reading if you´re still interested!
Now lets continue with a list of features in the next paragraph!
Main Features:
- Based on kernel/common 5.10.149
- compiled with Clang 12.0.5
- CPU-Battery saver to be able to restrict max cpufreqs on the fly, without enabling powersaving modes that might cause missed notifications (see second post)
- SSG IO scheduler for reduced overhead and less CPU cycles (more lightweight and android optimized)
- Power saving workingqueues enabled by default
- Change various drivers to use power efficient workingqueues. This compliments EAS in general
- implement LRNG (thanks @arter97, see arter kernel OP for more info )
- Enable support for TTL spoofing
- wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
- please read [URL="https://arstechnica.com/gadgets/2018/08/p-is-for-power-how-google-tests-tracks-and-improves-android-battery-life/"]this for further info
- f2fs improvments for better efficiency
- scheduler improvements
- psi fixes
- Flashing the kernel will keep root!
- Flashable via EXKM, FKM or TWRP (if available) on a rooted system!
Flashing Guide, Download and Changelog
Requirements:
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- magisk root
- a backup of stock boot.img or your magisk patched boot.img in case you want to go back to stock.
How to flash the Kernel:
1. Download the latest kernel.zip and make sure you have properly updated to the latest matching Firmware (check the feature list for the current firmware the source is based on). When there´s an OTA update for the Sony Xperia 1 IV it takes Sony a while to release the source code for the new OS and me a while to build a new kernel. If you don´t want to face any issues, wait until I either release an updated kernel or give green light because there were no kernel changes.
If you want to be sure there are no issues, always make sure to run the firmware the kernel is built for!
If you feel adventurous and try in advance, make sure you have a backup ready!
2. Flash the kernel.zip via latest TWRP (if available), EXKM or FKM app and do a full reboot.
3. Reboot and profit.
DOWNLOAD:
Download is located always in this folder, or attached to the release posts in case AFH is wonky.
https://www.androidfilehost.com/?w=files&flid=335705
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 12
1.0.0 Initial Release
Android 13
1.0.0 https://forum.xda-developers.com/t/...-xperia-1-iv-aka-nagara.4480653/post-87711541
1.0.1 https://forum.xda-developers.com/t/...-xperia-1-iv-aka-nagara.4480653/post-87945391
1.0.3 https://forum.xda-developers.com/t/...-xperia-1-iv-aka-nagara.4480653/post-88241223
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee/tea
If you like my work: http://paypal.me/freak07
Credits:
Sony for the development device, giving me the opportunity to create this project!
@osm0sis for all his work, including the ak3 installer!
@tbalden for being the best HTC, Pixel, OnePlus and now Asus wingman!
@LeeDroid and @mwilky for their awesome roms and work I used on multiple devices!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@arter97 for giving me advice
@kdrag0n for his help and advices!
@topjohnwu for magisk!
Source Code: https://github.com/freak07/Kirisakura_GKI_Nagara
F.A.Q:
Question: Is root preserved when flashing this kernel?
Answer: Yes, the AnyKernel.zip will detect root and keep it.
Question: Safetynet does not pass on my phone since I unlocked the phone, why is this so?
Answer: Google introduced hardware backed attestation recently. Unfortunately the old kernel tricks to still get safetynet passing won´t work. Instead you will have to rely on some magisk modules. Short guide in post #4 below.
Question: How do I return back to stock or another kernel.
Answer: Extract boot.img from the matching firmware you are on (you can do so by using this tool or similar ones found on XDA and when googling around) and flash via fastboot. If you want to keep root flash back the magisk_patched_boot.img. Or dirty flash your rom and re-root.
Question: Why is having Magisk installed mandatory for this kernel?
Answer: The kernel uses a ramdisk overlay to apply some settings after boot. If you are not rooted these settings will not get applied and you miss some of the optimizations.
Question: How to report bugs properly?
Answer: Have a look at post #3 in the linked thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re running on a stock configuration. That´s means you´re not using any mods, tweaks in kernel managers or other root tweaks , magisk modules, scripts or other modifications that alter various functions like sound mods, data traffic, sleeping behaviour, scheduler, magical battery tweaks etc.
Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.
Is the issue reproducible? Does it happen frequently?
Provide logs, otherwise debugging is a lot harder. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.
Feature Documentation:
Here´s a brief documentation about some of the features included in the kernel that can be changed as the user desires.
They can be accessed via either terminal, scripts or for example EXKM manager ( tools -> user settings).
CPU-Frequency Limiting:
Another option is CPU-Freq Limiting. You can now limit the CPU frequency to a few different levels with a sysfs interface. Original implementation is from @tbalden, I only changed it to be accessible via traditional root methods.
Main Switch:
sys/module/cpufreq/parameters/batterysaver
Set this option to "1" to enable the feature
Max-Frequency Selection (Input boosts, such as scrolling boost or app launching boosts will still apply, if touch boost restriction is not set to 1)
sys/module/cpufreq/parameters/batterysaver_level
Set this to "1" to restrict the max CPU-Freqs to 1,6GHZ/1,9GHZ/2,22GHZ (Little Cluster/Big Cluster/Prime Core)
Set this to "2" to restrict the max CPU-Freqs to 1,4GHZ/1,6GHZ/1,8GHZ (Little Cluster/Big Cluster/Prime Core)
Set this to "3" to restrict the max CPU-Freqs to 1,1GHZ/1,1GHZ/1,1GHZ (Little Cluster/Big Cluster/Prime Core)
Touch-Boost Restriction
sys/module/cpufreq/parameters/batterysaver_touch limiting
Set this to "1" to restrict the powerhal from boosting over the limit defined in batterysaver_level
Set this to "0" to allow the powerhal to boost above the values defined in batterysaver_level, but only during interaction with the Phone!
Screenshots:
View attachment 5309899View attachment 5309901View attachment 5309903
This is for example very useful during gaming to prevent additional heat, if not the highest performance from the CPU is required. Check if the game is running fine on level 1 or 2, and you´ll notice much less heat. Powerdraw will be reduced as well.
Another very useful trick while doing video calls or long extended navigation sessions with google maps to preserve battery or keep the phone from heating. Especially during summer if the ambient temperatures are high.
This is a very easy way to preserve battery or reduce heat without toggling the battery save mode in settings as that restricts background data usage, which can lead to delayed notifications.
How to pass Safetynet after unlocking the bootloader
With the introduction of hardware backed safetynet attestation, passing safetynet has become a lot more complicated.
Some probably remember a while ago, flashing a kernel that forced some flags was enough to pass it. However these days are gone.
Below is a short guide how to pass safetynet on phones that are flagged to use HW attestation (such as the ROG 5).
1. Make sure you´re running latest magisk canary.
2. In Magisk Manager enable both zygisk and deny list.
4. Download the latest Universal Safety Net Fix from @kdrag0n ´s github for zygisk cand flash it in Magisk Manager. Reboot.
5. Profit
Oh, my God! thank you so much for making the IV kernel
am I right to assume that CPU frequency limiting can help the phone not overheat when taking photos?
You are Awesome
tomatoketchup said:
am I right to assume that CPU frequency limiting can help the phone not overheat when taking photos?
Click to expand...
Click to collapse
yes. it should at least slow down the heat buildup. that´s the main goal behind it.
please note that 4k 120fps recording or other demanding tasks might not work without stutters if CPU gets restricted too much.
Apart from app loading times, if the usage is not super demanding level 3 works without major stutters in the UI on 120fps refresh rate.
htcmage said:
Oh, my God! thank you so much for making the IV kernel
Click to expand...
Click to collapse
Thaiban said:
You are Awesome
Click to expand...
Click to collapse
Freak07 said:
yes. it should at least slow down the heat buildup. that´s the main goal behind it.
please note that 4k 120fps recording or other demanding tasks might not work without stutters if CPU gets restricted too much.
Apart from app loading times, if the usage is not super demanding level 3 works without major stutters in the UI on 120fps refresh rate.
Click to expand...
Click to collapse
excellent <3, I don't need 4K 120fps recording I actually only do 1080p 24 because I like stabilization. so going to flash 64.0.A.8.25 and this kernel after that. million thanks!
It's a small amount, but I donated it, thank you always
htcmage said:
It's a small amount, but I donated it, thank you always
Click to expand...
Click to collapse
Thank you very much! I greatly appreciate it.
Hahaha... Hello my good friend @Freak07. Didn't know you were into Sony as well.
@Freak07 can you port it to xperia pro i ?
Developer, I have a question
If I use my work profile (shelter or island apk) I can't get into the settings menu I get a popup stating that the system UI is shutting down, maybe it's kernel related?
Should I uninstall Uperf before flashing?
Also thanks for this excellent work.
great work!Thx
to those who flashed, how is battery live ?
ist compüatible with latest sony update?
Would be interested to know, if it supports the old android kernels feature to emulate CD and DVD. Its a feature that DriveDroid needs to emulate a bootable DVD drive from an *.ISO hosted from an android device over USB. it was present in my older devices until XZ1 Compact and i was able to boot my pc off from a iso file hosted on my android device. It was much convinient than using silly PXE boot over eth0
No more update ?
Mrxyzl said:
No more update ?
Click to expand...
Click to collapse
OP will update when new Kernel sources are released and he has time. Mentioned in the first post.