Related
Anyone have tried reducing DPI on our device? Any disadvantages of this operation? Like screwed up icons or something?
Sent from my HTC One SV powered by Saturn III.
Have you tried xposed & appsettings?
I've just noticed the thread about it (XDA App haven't shown it to me or may I missed it). Will do a try, I only hope I won't make a mistake anywhere.
Bazdir said:
I've just noticed the thread about it (XDA App haven't shown it to me or may I missed it). Will do a try, I only hope I won't make a mistake anywhere.
Click to expand...
Click to collapse
I use xposed an appsettings without any problem.
With the other solution (to change dpi in build.prop) you will have the problem that several apps seem to be incompatible and Play Store won't update these "incompatible" apps any longer.
Sylvia said:
I use xposed an appsettings without any problem.
With the other solution (to change dpi in build.prop) you will have the problem that several apps seem to be incompatible and Play Store won't update these "incompatible" apps any longer.
Click to expand...
Click to collapse
So... Setting 217 DPI will cause problems with updating apps such as jakdojade.pl or something like that? God damn it, I hoped, I would have a bit smaller interface like One S has.
And thanks for the feedback.
Bazdir said:
So... Setting 217 DPI will cause problems with updating apps such as jakdojade.pl or something like that? God damn it, I hoped, I would have a bit smaller interface like One S has.
And thanks for the feedback.
Click to expand...
Click to collapse
Personally, I had no update issues in reducing the dpi to 217 in build.prop
The only problem is that some apps will look glitchy (sense interface, torch), for them you'll need to set dpi back to 240, using something like appsettings for xposed framework
madpausa said:
Personally, I had no update issues in reducing the dpi to 217 in build.prop
The only problem is that some apps will look glitchy (sense interface, torch), for them you'll need to set dpi back to 240, using something like appsettings for xposed framework
Click to expand...
Click to collapse
Good. I've tried installing Xposed Framework to get Appsettings module, but then I've been spammed with illegal information. Do I have to install busybox? Or may I just forgot to set system rw in ES File Explorer... I just realised that might be the solution.
EDIT: Well... That haven't worked either. Only app_process have been patched. If I will push xposedbridge by myself, then it should work?
EDIT2: Okay, that haven't changed anything.. Any idea?
Sent from my HTC One SV powered by Saturn III.
Bazdir said:
Good. I've tried installing Xposed Framework to get Appsettings module, but then I've been spammed with illegal information. Do I have to install busybox? Or may I just forgot to set system rw in ES File Explorer... I just realised that might be the solution.
EDIT: Well... That haven't worked either. Only app_process have been patched. If I will push xposedbridge by myself, then it should work?
EDIT2: Okay, that haven't changed anything.. Any idea?
Sent from my HTC One SV powered by Saturn III.
Click to expand...
Click to collapse
Flash back stock boot.img with fastboot, install xposed, flash back the kernel/boot.img you used before.
old.splatterhand said:
Flash back stock boot.img with fastboot, install xposed, flash back the kernel/boot.img you used before.
Click to expand...
Click to collapse
I was wondering, if it wasn't caused by non-stock kernel. Then you picked up the idea here in this thread. And it worked. Thanks!
Bazdir said:
I was wondering, if it wasn't caused by non-stock kernel. Then you picked up the idea here in this thread. And it worked. Thanks!
Click to expand...
Click to collapse
I had the same problem
I'm bumping up this thread again, because I tried to take a DPI one step lower, so it means - 216 DPI. I have to tell, that the interface looks much better than it was on 217. The notification icons are sharper and all the icons and texts are sharper too. I really recommend to try it.
(I didn't want to make a new thread, so I posted it here.)
I find 216 still too large for my liking. I've been running 200 for a while without any issues. It's a good balance.
I am also using the multi-dpi version of google play so no probs there either.
The ONLY minor issue is that it cuts off the bottom of the 'Recent Apps' (the part showing the app name) which isn't a big deal for me at all as I can see what the app is anyway.
Hey guys,
since i got my Oneplus 6, i couldnt get viper to work quite right. Most of the time its just shows "Processing: No" till i restart it and after like a hour or device switch it turns off.
I tried:
Copying the Audioeffects.conf from system/etc to vendor/etc
Using Magisk Audio Compability Module
Using Alternate Magisk V4A Module
Using a Magisk Rom with Build-In V4a (currently xXx 2.8)
Disabling Dirac and Services
but nothing worked
thanks for your help
i had the same but then i tried to use the other viper release from magisk and it worked. there is this one called hifi and fx
Try exiting the viper app with the 3 dots top right hand corner. That is what worked for me
dgunn said:
Try exiting the viper app with the 3 dots top right hand corner. That is what worked for me
Click to expand...
Click to collapse
that works for like 10 mins and then it gets killed
byReqz said:
that works for like 10 mins and then it gets killed
Click to expand...
Click to collapse
Sounds to me like you need to disable the battery optimizations for Viper. It's almost as if your phone is detecting High battery drain and shuts down the app
dgunn said:
Sounds to me like you need to disable the battery optimizations for Viper. It's almost as if your phone is detecting High battery drain and shuts down the app
Click to expand...
Click to collapse
yeah thats what i thought too, i zried whitelisting it and installing it as system app (+ magisk module) but it didnt seem to work.
I removed the one from my rom and tried the magisk repo version again and somehow its working till now
byReqz said:
yeah thats what i thought too, i zried whitelisting it and installing it as system app (+ magisk module) but it didnt seem to work.
I removed the one from my rom and tried the magisk repo version again and somehow its working till now
Click to expand...
Click to collapse
I was unaware that you were using the magisk module. I could not get that one to work either
dgunn said:
I was unaware that you were using the magisk module. I could not get that one to work either
Click to expand...
Click to collapse
the normal one doesnt work with viper doewsnt it?
Try just exiting the viper app then reopening it. I had this problem before and it just randomly went away.
TheNetwork said:
Try just exiting the viper app then reopening it. I had this problem before and it just randomly went away.
Click to expand...
Click to collapse
it only works for a few mins that way
I'm using the Android p beta and i don't have the problems with viper as i did with oxygen os 5. it's always processing for my headphones, either plugged in or Bluetooth. the only exception is sometimes after receiving a call while listening to music, after the call is over and my music resumes, viper is no longer processing. not every time though. i used the latest magisk and the viper module in the screenshot.
i also didn't make any changes to conf files, just installed through magisk download. rebooted, opened viper fx, gave it storage permissions and turned it on.
Had the same problem, but was able to resolve it by choosing the legacy (non-material) interface when installing the Magisk module. I still flashed the full module and selected the latest version, just not the material interface. It may have been something else, but I've updated my ROM (HavocOS) several times and even done a couple full fastboot stock resets and the issue is yet to resurface.
TuxRuffian said:
Had the same problem, but was able to resolve it by choosing the legacy (non-material) interface when installing the Magisk module. I still flashed the full module and selected the latest version, just not the material interface. It may have been something else, but I've updated my ROM (HavocOS) several times and even done a couple full fastboot stock resets and the issue is yet to resurface.
Click to expand...
Click to collapse
as i said, idk why but its working now.and im on material now
byReqz said:
Hey guys,
since i got my Oneplus 6, i couldnt get viper to work quite right. Most of the time its just shows "Processing: No" till i restart it and after like a hour or device switch it turns off.
I tried:
Copying the Audioeffects.conf from system/etc to vendor/etc
Using Magisk Audio Compability Module
Using Alternate Magisk V4A Module
Using a Magisk Rom with Build-In V4a (currently xXx 2.8)
Disabling Dirac and Services
but nothing worked
thanks for your help
Click to expand...
Click to collapse
I've had this problem on an Samsung S7 Edge, S8 Plus, and now, a Oneplus 6.
Everything appears to look good on Driver Status, except "Processing:No" and it's audibly not on.
What's worked for me in this specific situation is replacing the configuration file "audio_effects.conf" in /system/vendor/etc with another configuration file that I found in another XDA thread. So here's the concrete steps:
1. Install the viper4android FX module from Magisk manager that has four devs (v1.7 as i write this) and reboot. I don't know if this method will work with other v4a modules. Note that Processing will work temporarily, but likely won't survive a reboot.
2. Download this file (files_for_v4a.zip) from here:
https://forum.xda-developers.com/ga...laxy-s8-s8-t3596933/post72049061#post72049061
3. Unzip files_for_v4a.zip and make note where it extracted. (You'll need one of its contents, audio_effects.conf, later)
4. Using a file explorer with root capability, go to the following directory:
/system/vendor/etc
5. Copy the existing "audio_effects.conf" to another directory, for example /download, to use as a backup in case this goes badly
6. Copy the file "audio_effects.conf" that you unzipped earlier to /system/vendor/etc, overwriting the existing file.
7. Reboot and test v4a.
Good luck!
Note: The Pulse feature of a custom NavBar in custom ROMS based on LOS 15.1 will not work if you do the above.
Although I'm just a hack, I modded an "audio_effects.conf" file using commits from the above to work with Pulse. I've tested it on my device (despite my lack of know-how, it seems to work for me and others!), so be aware of this if you download the following file and use it (by renaming it audio_effects.conf and placing it in /system/vendor/etc):
reaper000 said:
I've had this problem on an Samsung S7 Edge, S8 Plus, and now, a Oneplus 6.
Everything appears to look good on Driver Status, except "Processing:No" and it's audibly not on.
What's worked for me in this specific situation is replacing the configuration file "audio_effects.conf" in /system/vendor/etc with another configuration file that I found in another XDA thread. So here's the concrete steps:
1. Install the viper4android FX module from Magisk manager that has four devs (v1.7 as i write this) and reboot. I don't know if this method will work with other v4a modules. Note that Processing will work temporarily, but likely won't survive a reboot.
2. Download this file (files_for_v4a.zip) from here:
https://forum.xda-developers.com/ga...laxy-s8-s8-t3596933/post72049061#post72049061
3. Unzip files_for_v4a.zip and make note where it extracted. (You'll need one of its contents, audio_effects.conf, later)
4. Using a file explorer with root capability, go to the following directory:
/system/vendor/etc
5. Copy the existing "audio_effects.conf" to another directory, for example /download, to use as a backup in case this goes badly
6. Copy the file "audio_effects.conf" that you unzipped earlier to /system/vendor/etc, overwriting the existing file.
7. Reboot and test v4a.
Good luck!
Note: The Pulse feature of a custom NavBar in custom ROMS based on LOS 15.1 will not work if you do the above.
Although I'm just a hack, I modded an "audio_effects.conf" file using commits from the above to work with Pulse. I've tested it on my device (despite my lack of know-how, it seems to work for me and others!), so be aware of this if you download the following file and use it (by renaming it audio_effects.conf and placing it in /system/vendor/etc):
Click to expand...
Click to collapse
Thanks for your long answer, will be trying the files if this module fails again.
Also im not on a LOS Based Rom, im on OOS and GravityBox
byReqz said:
Thanks for your long answer, will be trying the files if this module fails again.
Also im not on a LOS Based Rom, im on OOS and GravityBox
Click to expand...
Click to collapse
Just seeing if I can help! And I did the same sequence of steps on OOS as well ... But I haven't run gravity box in awhile. Hope it works out for you.
reaper000 said:
Just seeing if I can help! And I did the same sequence of steps on OOS as well ... But I haven't run gravity box in awhile. Hope it works out for you.
Click to expand...
Click to collapse
I tried everything but it still needs a restart to be working sometimes, do you know if i have to disable dirac or something?
byReqz said:
I tried everything but it still needs a restart to be working sometimes, do you know if i have to disable dirac or something?
Click to expand...
Click to collapse
I haven't messed with dirac at all, and v4a still works for me.
Some clarification, please:
Did you uninstall the v4a magisk module that came with xXx and reboot?
Then go to magisk manager and install v4a fx materialized1.7 and follow the rest of the steps outlined in my post?
reaper000 said:
I haven't messed with dirac at all, and v4a still works for me.
Some clarification, please:
Did you uninstall the v4a magisk module that came with xXx and reboot?
Then go to magisk manager and install v4a fx materialized1.7 and follow the rest of the steps outlined in my post?
Click to expand...
Click to collapse
yeah, its 1.7 from magisk repo, disabling dirac seems to help a bit but not everytime
byReqz said:
yeah, its 1.7 from magisk repo, disabling dirac seems to help a bit but not everytime
Click to expand...
Click to collapse
And you replaced the audio_effects.conf file in /system/vendor/etc with the one from the downloaded zip?
(Sorry to belabor the point, but it's not clear to me you tried all that)
I saw someone made a post on one way to remove the distortion from V4A, but that method breaks Bluetooth audio. This is how you fix it without breaking Bluetooth:
1. Reboot to recovery, mount Vendor
2. go to 'Advanced' -> 'File manager'
3. Go to "/Vendor/lib64/audiofx/" and rename/remove libvolumelistener.so
4. Go to "/Vendor/lib/audiofx/" and rename/remove libvolumelistener.so
5. Reboot to system, install V4A
And that's it
Edit:
You can also just use one of the older versions of V4A without needing a fix of any kind.
Couldn't you get the same result on a file manager with root permission without having to go through TWRP and reboot?
stewykam said:
Couldn't you get the same result on a file manager with root permission without having to go through TWRP and reboot?
Click to expand...
Click to collapse
I believe at least one of those is read only while the system is on. I remember trying that before and it wouldn't let me.
TiklMiPickles said:
I believe at least one of those is read only while the system is on. I remember trying that before and it wouldn't let me.
Click to expand...
Click to collapse
Ahh... Just wondering. Thanks for the info though ?
Anyone who tried it out and could confirm on this?
Edit: Tried to poke around in my phone but there's no "audiofx" instead there's "soundfx" which still houses the (lib)volumelistener.so
TiklMiPickles said:
I saw someone made a post on one way to remove the distortion from V4A, but that method breaks Bluetooth audio. This is how you fix it without breaking Bluetooth:
1. Reboot to recovery, mount System and Vendor
2. go to 'Advanced' -> 'File manager'
3. Go to "/System/lib64/audiofx/" and rename/remove volumelistener.so
4. Go to "/Vendor/lib/audiofx/" and rename/remove libvolumelistener.so
5. Reboot to system, install V4A
And that's it
Click to expand...
Click to collapse
Notification helper do this job systemless
However, I have a problem always with whatsapp voice notes crackling an stuttering sound if its mininized or force screen off
Dude, you are telling the same thing that I have posted (I'm sure you're talking about my post). You are asking users to manually edit volumelistener.so and I suggested users to flash the notification helper magisk module which does the exact same job automatically and most important, systemlessly. Is it really needed to create the same post with different heading and tagline? I'm sure you don't even know what I was talking about or didn't even try the module. Or else you would have realized you are not giving anyone any different solution. And if the method I told users breaks Bluetooth audio, then your method will do the exact same thing. Guess why. Because you are telling people to do the same thing, but manually. But I'm sure you didn't even bother to check the github of the particular magisk module I was talking about or didn't even try contacting the dev to see how exactly it works. Now the main question, what different solution did you give the users here?
---------- Post added at 08:53 PM ---------- Previous post was at 08:46 PM ----------
Dna10 said:
Anyone who tried it out and could confirm on this?
Edit: Tried to poke around in my phone but there's no "audiofx" instead there's "soundfx" which still houses the (lib)volumelistener.so
Click to expand...
Click to collapse
This is what happens when someone decides to make a post without having complete knowledge about what he is saying.
Dna10 said:
Anyone who tried it out and could confirm on this?
Edit: Tried to poke around in my phone but there's no "audiofx" instead there's "soundfx" which still houses the (lib)volumelistener.so
Click to expand...
Click to collapse
You have to mount those partitions in recovery. If you didn't manually mount them, a lot of files/folders won't show
Rowdyy Ronnie said:
Dude, you are telling the same thing that I have posted (I'm sure you're talking about my post). You are asking users to manually edit volumelistener.so and I suggested users to flash the notification helper magisk module which does the exact same job automatically and most important, systemlessly. Is it really needed to create the same post with different heading and tagline? I'm sure you don't even know what I was talking about or didn't even try the module. Or else you would have realized you are not giving anyone any different solution. And if the method I told users breaks Bluetooth audio, then your method will do the exact same thing. Guess why. Because you are telling people to do the same thing, but manually. But I'm sure you didn't even bother to check the github of the particular magisk module I was talking about or didn't even try contacting the dev to see how exactly it works. Now the main question, what different solution did you give the users here?
---------- Post added at 08:53 PM ---------- Previous post was at 08:46 PM ----------
This is what happens when someone decides to make a post without having complete knowledge about what he is saying.
Click to expand...
Click to collapse
No, you said to full on remove the audiofx folder rather than fix the specific files that cause the problem. The magisk also removes more files than necessary, which breaks Bluetooth audio.
It's funny you say I should know what I'm talking about when you are the one spreading false information. Before you go around throwing shade, you should have checked to see if I was right.
slimshouki said:
Notification helper do this job systemless
However, I have a problem always with whatsapp voice notes crackling an stuttering sound if its mininized or force screen off
Click to expand...
Click to collapse
The magisk module is definitely easier and let's you have the fix systemlessly, but I use Bluetooth audio all the time, and this is the only way I've found to have working notifications, Bluetooth and V4A.
Is the WhatsApp issue with the magisk module or fix I listed?
TiklMiPickles said:
The magisk module is definitely easier and let's you have the fix systemlessly, but I use Bluetooth audio all the time, and this is the only way I've found to have working notifications, Bluetooth and V4A.
Is the WhatsApp issue with the magisk module or fix I listed?
Click to expand...
Click to collapse
Both make same behaviour
Btw, Magisk module do not break BT audio
slimshouki said:
Both make same behaviour
Btw, Magisk module do not break BT audio
Click to expand...
Click to collapse
That's strange, I just double checked and it breaks it for me on Havoc-OS, it also did on Siberia and AEX when I used those. Maybe it has to do with the rom or vendor/firmware? I'm using Havoc and 8.12.20
TiklMiPickles said:
No, you said to full on remove the audiofx folder rather than fix the specific files that cause the problem. The magisk also removes more files than necessary, which breaks Bluetooth audio.
It's funny you say I should know what I'm talking about when you are the one spreading false information. Before you go around throwing shade, you should have checked to see if I was right.
Click to expand...
Click to collapse
Its funny how you accuse me of spreading false information without even digging into the module or atleast check the github. This is what happens when a randon user decides to show up once in a blue moon. Here is the github link of the module: https://github.com/Magisk-Modules-Repo/nhr
If you still don't understand how it works and what it does, then I feel sad for your noobness. And can you please list out what the module removes more than volumelistener.so? Don't just go on make claims, prove it first. And also, I have attached a screenshot of my post. Please show me where did I suggest people to remove audiofx folder (which is again wrong. There is no audiofx folder on vendor partition. Its called soundfx). And next time, if you decides to challenge someone who is more active on XDA than you, first upgrade your profile. I didn't get those thanks count just like that. It's the appreciation that I got from others upon helping them. So don't teach me what I am suggesting other users. First raise your profile standard.
slimshouki said:
Both make same behaviour
Btw, Magisk module do not break BT audio
Click to expand...
Click to collapse
Yeah because that magisk module does nothing other than removing volumelistener.so systemlessly when you choose volume down (that's why I have suggested users to choose volume down when prompted) . And if you choose volume up, it removes notification_helper from audio_effect cfgs.
And Viper will only break BT audio if you don't know how to make BT work with Viper.
Rowdyy Ronnie said:
Yeah because that magisk module does nothing but removes volumelistener.so systemlessly when you choose volume down. And if you choose volume up, it removes notification_helper from audio_effect cfgs.
And Viper will only break BT audio if you don't know how to make it work with Viper.
Click to expand...
Click to collapse
Do you have any idea about whatsapp voice notes issue?
slimshouki said:
Do you have any idea about whatsapp voice notes issue?
Click to expand...
Click to collapse
I have sent a message to Zack regarding the issue. Let see if he can address the issue. By the way, can you do one test. Remove the module and flash it again. This time when asked to choose between volume up and down, select up to remove notification helper and see if it fixes your problem.
Rowdyy Ronnie said:
I have sent a message to Zack regarding the issue. Let see if he can address the issue. By the way, can you do one test. Remove the module and flash it again. This time when asked to choose between volume up and down, select up to remove notification helper and see if it fixes your problem.
Click to expand...
Click to collapse
I did that as well.and same issue
Rowdyy Ronnie said:
Yeah because that magisk module does nothing other than removing volumelistener.so systemlessly when you choose volume down (that's why I have suggested users to choose volume down when prompted) . And if you choose volume up, it removes notification_helper from audio_effect cfgs.
And Viper will only break BT audio if you don't know how to make BT work with Viper.
Click to expand...
Click to collapse
After doing some testing, it seems to be rom specific. AEX and Havoc-OS, it breaks Bluetooth audio, but I tested on Resurrection Remix and Syberia and it doesn't.
Rowdyy Ronnie said:
Yeah because that magisk module does nothing other than removing volumelistener.so systemlessly when you choose volume down (that's why I have suggested users to choose volume down when prompted) . And if you choose volume up, it removes notification_helper from audio_effect cfgs.
And Viper will only break BT audio if you don't know how to make BT work with Viper.
Click to expand...
Click to collapse
I've managed to track down the issue. It isn't the notification remover module that is causing the issue, it's the Audio Modification Library, which the notification remover tells you to install if you have V4A installed. I have found this to be the case with AEX, Havoc-OS and MSM Xtended. Removing the AML module fixes the issue.
Not work viper and Dolby...havoc rom
Hi, first of all, sorry for my bad english.
I just updated my 7Pro and rooted it, and installed the last AdAway release from XDA. The problem is, they didn't block any of the ads from Chrome or any other app like 9gag.
Has anyone tried to use any adblocker for this version of OOS?
Thanks!
yes here is a magisk module of the app i made so if you don't like it just uninstall module
download
u need to make sure you force close chrome and reboot after you updated adaway
Bradl79 said:
yes here is a magisk module of the app i made so if you don't like it just uninstall module
download
u need to make sure you force close chrome and reboot after you updated adaway
Click to expand...
Click to collapse
Thanks for the quick replay, but I finally found a solution. I had to enable the "Systemless host" in Magisk options.
Thanks for you help anyway
Bradl79 said:
yes here is a magisk module of the app i made so if you don't like it just uninstall module
download
u need to make sure you force close chrome and reboot after you updated adaway
Click to expand...
Click to collapse
Dang, you have a Magisk module for everything. You should start a thread with them all listed. I'm sure people would appreciate it.
Garapablo said:
Thanks for the quick replay, but I finally found a solution. I had to enable the "Systemless host" in Magisk options.
Thanks for you help anyway
Click to expand...
Click to collapse
U helped me too, BC I forgot to enable systemless host in Magisk, thank you lol
---------- Post added at 10:45 PM ---------- Previous post was at 10:44 PM ----------
bp328i said:
Dang, you have a Magisk module for everything. You should start a thread with them all listed. I'm sure people would appreciate it.
Click to expand...
Click to collapse
Lol I do, I make one for almost all the apps I use the most
Here is a link if u want to check it out
My modules
I rooted OnePlus 7 Pro and wanted to make OTA update. But as a newbie I didn't turn off fingerprint lock before reboot. OP 7 Pro just froze after reboot on PIN screen and turned off to stock recovery. I could only make a hard reset. After that my OP 7 Pro turned on. I make one more time root process - fastboot boot twrp.img > in TWRP Install Recovery Ramdisk from twrp.img > Flash Magisk.zip. But now Adaway doesn't work and I tried everything - granted root access, permission to write in memory, in adaway systemless option turn on same in Magisk. Can you please help me? Uninstall and install adaway didn't help me. Everything looks good but advertises are still display.
Hi,
with pleasure I share the module for center/right clock in the status bar, the module is created by @Tulsadiver, tested by me on Oneplus 7 Pro with firmware version as specified file name.
ESSENTIAL PREREQUISITE: BEFORE INSTALLING THE MOD, IT IS NECESSARY TO INSTALL, IF NOT PRESENT, THE "OVERLAY MOUNT FIX" MODULE BY @Zackptg5 DOWNLOADABLE FROM MAGISK MANAGER, WITHOUT THIS THE CLOCK MODULE WILL NOT WORK!
It is a magisk module and I want to repeat that it can only be used on Oneplus 7 Pro.
The module can only be used with the firmware release indicated in the file name, it will be my commitment to update the thread with the release of future updates.
I'm trying it and it doesn't seem to show any problems but I still recommend making a backup before trying it.
To remove the mod, simply uninstall the module using magisk manager or, if this is not usable, from recovery twrp, using the file manager deleting the module "OP7_VrThemer_OPSystemUI" that you find at the following path:
/data/adb/modules
Update: How to remove the module in case of failure (procedure valid for any magisk module):
Turn off the phone by pressing and holding the power button for a few seconds.
Turn the phone back on.
After the "Bootloader Unlocked" warning appears, press and hold down the "Volume up" and "Volume down" keys at the same time, until the startup animation appears.
The phone will boot correctly but will be operating in "Safe mode".
Now restart your phone normally.
The phone will boot in standard operating mode but with all magisk modules disabled.
Remove the magisk module that caused the problem and enable your other modules and reboot one last time.
The phone operating as if nothing had happened
My biggest, massive, THANKS go to @Tulsadiver, for sending me his xml file with the modifications necessary to obtain the movement of the clock and for passing me Its VRThemer module, without your help I could not have avoided the bootloop ... I can say that the mod is all from @Tulsadiver, the mod is all the result of his work and his expertise, I have only been a tester and shared his fantastic work with you.
Thanks also to @dladz, for giving me his support and advice!
Attention each module you find in this post is specific to the firmware indicated in the file name, with each new firmware it will be my concern to release the new updated module.
Flashing always at your own risk!!!
To be installed only with Magisk Manager, if installed by TWRP it does not work.
Please read all indications before proceeding with the installation, module has been tested and is working on the OxygenOS 10 and OxygenOS 11 based firmware, NOT tested with other firmware and non-OxygenOS based roms.
P.S. To complete the information, I have not had the opportunity to try the same module with other firmware versions, it could work but I have no way of knowing, if you decide to try remember that it should only be used on Oneplus 7 Pro with firmware OxygenOS 10 and OxygenOS 11 and that you do at your own risk. I test the module with the firmware specified in the file name before publishing it, if it is here for you it means that it has not given me any problems.
Flashing always at your own risk!!!
This sounds awesome. Thank you very much. I know it's a lot to ask, but would you be able to make a version that moves the clock to the right? That would be truly amazing if at all possible
a63548 said:
This sounds awesome. Thank you very much. I know it's a lot to ask, but would you be able to make a version that moves the clock to the right? That would be truly amazing if at all possible
Click to expand...
Click to collapse
Check your pm
You should post the right clock as well
Just a humble request, can you create a telegram group to support and test your module, it will be faster
a63548 said:
This sounds awesome. Thank you very much. I know it's a lot to ask, but would you be able to make a version that moves the clock to the right? That would be truly amazing if at all possible
Click to expand...
Click to collapse
mholloway said:
You should post the right clock as well
Click to expand...
Click to collapse
work in progress...stay tuned
Added to the first post mod for right clock and updated the module for center clock (if you want to update remove the old release, restart and install the new one).
I await your feedback.
Thanks to @Tulsadiver for his patience in supporting me and for his great availability!
New update of the "center clock" module, fixed clock displayed in the lockscreen defect, I recommend removing those installed up to now and replace with the latter released
Thanks for the mod. I tried the right clock mod but it did not work. Just to be fair, I tried on stable OS 10.3.5 and NOT on beta OS. Mod installed w/o any errors and I can see this mod installed in the Magisk Manager but clock is still on the left side. Rebooted twice, still no go. May be the beta 18 OS is the only OS that support this module. Keep up the good work. Thanks.
Gr8man001 said:
Thanks for the mod. I tried the right clock mod but it did not work. Just to be fair, I tried on stable OS 10.3.5 and NOT on beta OS. Mod installed w/o any errors and I can see this mod installed in the Magisk Manager but clock is still on the left side. Rebooted twice, still no go. May be the beta 18 OS is the only OS that support this module. Keep up the good work. Thanks.
Click to expand...
Click to collapse
Sorry my mistake, try like this:
Remove the right clock module
Restart
Install "Overlay mount fix" module by @Zackptg5 from magisk manager
Restart
Reinstall the clock module
The overlay mount fix module is necessary for the mod to work and I forgot to write it, sorry.
I await feedback
Installed right clock on beta 18,not working.
Magisk 20.04
Magisk manager 8.0.2
mholloway said:
Installed right clock on beta 18,not working.
Magisk 20.04
Magisk manager 8.0.2
Click to expand...
Click to collapse
Try like this:
Remove the right clock module
Restart
Install "Overlay mount fix" module by @Zackptg5 from magisk manager
Restart
Reinstall the clock module
I await feedback
dianoandr said:
Try like this:
Remove the right clock module
Restart
Install "Overlay mount fix" module by @Zackptg5 from magisk manager
Restart
Reinstall the clock module
Click to expand...
Click to collapse
That worked
mholloway said:
That worked
Click to expand...
Click to collapse
My mistake, sorry to you and everyone, I have the "overlay mount fix" module installed by default in my phone and I have not taken into account that it is necessary for the module to work...sorry again
dianoandr said:
Sorry my mistake, try like this:
Remove the right clock module
Restart
Install "Overlay mount fix" module by @Zackptg5 from magisk manager
Restart
Reinstall the clock module
The overlay mount fix module is necessary for the mod to work and I forgot to write it, sorry.
I await feedback
Click to expand...
Click to collapse
I know it worked for someone else but it really messed up my phone. Phone boots fine but screen is dark i.e. no display anymore. I am on OS 10.3.5 and the current Magisk 20.4. I'll use the fast boot zip when I get home to bring the phone back to life. Thanks!
Gr8man001 said:
I know it worked for someone else but it really messed up my phone. Phone boots fine but screen is dark i.e. no display anymore. I am on OS 10.3.5 and the current Magisk 20.4. I'll use the fast boot zip when I get home to bring the phone back to life. Thanks!
Click to expand...
Click to collapse
Go to recovery, with the integrated file manager function, delete the module "OP7_VrThemer_OPSystemUI" that you find at the following path: /data/adb/modules and reboot
dianoandr said:
Go to recovery, with the integrated file manager function, delete the module "OP7_VrThemer_OPSystemUI" that you find at the following path: /data/adb/modules and reboot
Click to expand...
Click to collapse
That did the trick. Thanks for your help. My phone came back to life and working fine
So, is it safe to say that right side clock module only work with OS 18 beta and not the latest stable OS 10.3.5?
Thanks again for your help.
Gr8man001 said:
That did the trick. Thanks for your help. My phone came back to life and working fine
So, is it safe to say that right side clock module only work with OS 18 beta and not the latest stable OS 10.3.5?
Thanks again for your help.
Click to expand...
Click to collapse
Happy it's back to normal, it's a trick to keep in mind for emergency situations.
The change itself is the same for all versions of oxygenos based on android 10, it probably changes something else in the apk and as a consequence the .xml file compiled with the mod, crashes your opsystemui.
I sent you a p.m.
I can confirm that mod works fine on Beta 19 as well? Thanks
Gr8man001 said:
I can confirm that mod works fine on Beta 19 as well Thanks
Click to expand...
Click to collapse
Great news, however as soon as I update my phone, I check that there are no major changes related to the apk and eventually update the modules to avoid instability.