Related
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)
Hi,
I ordered an expensive toothbrush by Philips, it has an app that keeps track of your brushing habits.
Even tracks of certain areas you don't cover too well.
If it works that would be great.
But I haven't even received my package yet, and I just try to install the app on my phone, I get a message that It won't work because I have a rooted phone.... Well it does not really say this, it said I have a jailbroken phone. See attachment.
Now before ordering I did try to see if it would work on a rooted phone, (on my wife's oukitell) no, but with magisk hide, it worked fine...
On my Xperia xz1, with Android 9 rooted also with magisk, magisk hide does not seem to work for this app.. Not even magisk repackaging.
I looked in the play store and see that there are a few others that bump into this problem.
I found on apkmirror that version 4.2.2 does work though if anyone needs this info.
At least on a repackaged magisk, and magisk hide.. I did not yet try it if it works without those.
I wish app makers would not do this... Many banking apps and other important apps I never have a problem with.
For anyone that is interested, with magisk version 18 and magiskhide activated for the sonicare app you can use it, even after the app detected root 'jailbreak' (as Philips puts it), and you turn on magiskhide in magisk 18 for sonicare the app will work again.
Using Sonicare apk 4.8.0 & Magisk 18.1 and turn on magiskhide on almost every app (incl system apps)
but still get the detect 'jailbreak' message.
Any idea how to fix this?
Ancientsthe said:
Using Sonicare apk 4.8.0 & Magisk 18.1 and turn on magiskhide on almost every app (incl system apps)
but still get the detect 'jailbreak' message.
Any idea how to fix this?
Click to expand...
Click to collapse
The app checks following things:
Code:
String str = Build.TAGS;
if (str != null && str.contains("test-keys")) {
return "true";
}
for (String file : new String[]{"/system/app/Superuser.apk", "/sbin/su", "/system/bin/su", "/system/xbin/su", "/data/local/xbin/su", "/data/local/bin/su", "/system/sd/xbin/su", "/system/bin/failsafe/su", "/data/local/su", "/su/bin/su"}) {
if (new File(file).exists()) {
return "true";
}
}
also tests output for /system/xbin/which su and /system/bin/which su
and check for emulator
public static boolean isEmulator() {
return Build.FINGERPRINT.startsWith("generic") || Build.FINGERPRINT.startsWith(EnvironmentCompat.MEDIA_UNKNOWN) || Build.MODEL.contains("google_sdk") || Build.MODEL.contains("Emulator") || Build.MODEL.contains("Android SDK built for x86") || Build.MANUFACTURER.contains("Genymotion") || (Build.BRAND.startsWith("generic") && Build.DEVICE.startsWith("generic")) || "google_sdk".equals(Build.PRODUCT);
}
You can find application without the check here https://drive.google.com/open?id=1VRqHwyN9OoHioX2-nppkJRwyQOUPAqSh .
Sadly due to paranoid developers you have to modify the app.
elektro255 said:
The app checks following things:
You can find application without the check here https://drive.google.com/open?id=1VRqHwyN9OoHioX2-nppkJRwyQOUPAqSh .
Sadly due to paranoid developers you have to modify the app.
Click to expand...
Click to collapse
Thanks a ton! I've been using the app for a while, but now it came up with that blocked message. Nothing I do seems to get rid of it anymore, even Magisk Hide. I didn't update the app, either. It's really weird.
Can you tell me which class the checks are in so I can do this myself? I'd really appreciate it.
Also, can this be removed through just .smali modifications? Or does it require a full .java decompile and recompile?
(Edit: I was able to find all of the code you pointed out and change these myself - I successfully modded version 6.4.1 of the app)
And since you seem knowledgeable, another thing I'd like to do is completely disable the need to log in before using the app. I've been able to use the app for a while, and it works fine if you totally block it from the internet. If I could just disable the account check and skip straight to the main activity and make the app think I'm logged in, that would be awesome.
I'm not super skilled with modifying decompiled apps, but I'm going to try and rip out the need to log in with an account just to use the app. I'm hoping I can attach this to a debugger and see which functions I will need to change. If anyone could point me in the right direction with this, that would be awesome!
ubergeek77 said:
Thanks a ton! I've been using the app for a while, but now it came up with that blocked message. Nothing I do seems to get rid of it anymore, even Magisk Hide. I didn't update the app, either. It's really weird.
Can you tell me which class the checks are in so I can do this myself? I'd really appreciate it.
Also, can this be removed through just .smali modifications? Or does it require a full .java decompile and recompile?
(Edit: I was able to find all of the code you pointed out and change these myself - I successfully modded version 6.4.1 of the app)
And since you seem knowledgeable, another thing I'd like to do is completely disable the need to log in before using the app. I've been able to use the app for a while, and it works fine if you totally block it from the internet. If I could just disable the account check and skip straight to the main activity and make the app think I'm logged in, that would be awesome.
I'm not super skilled with modifying decompiled apps, but I'm going to try and rip out the need to log in with an account just to use the app. I'm hoping I can attach this to a debugger and see which functions I will need to change. If anyone could point me in the right direction with this, that would be awesome!
Click to expand...
Click to collapse
Hi!
I have the same problem with Sonicare for Kids 1.8.6 even when I uninstalled Magisk.
Can you tell me where did you find the checks please? I'm searching for it with APK Multi Tool but find nothing after a long time and multi files opening.
Thanks for your help.
Hi
try to install the sonicare kids app on my samsung tab 3 with lieneago OS 14.1.
same problem, i try magisk hide, hide the app, hide magis, all no solution Can any help or modify the app for me? After modify i can update the app? Big Thanks
I ran into same problem.
I downloaded APK, modified methods for verifying root a tampered package, recompile, resign and it's working.
If anyone interested I can upload it somewhere, not sure if it can be uploaded on XDA directly.
DasioX said:
I ran into same problem.
I downloaded APK, modified methods for verifying root a tampered package, recompile, resign and it's working.
If anyone interested I can upload it somewhere, not sure if it can be uploaded on XDA directly.
Click to expand...
Click to collapse
If you are talking about the sonicare kids app, then yes, please My daughter has been needling me mercilessly to get it working again on her tablet.
uberhund said:
If you are talking about the sonicare kids app, then yes, please My daughter has been needling me mercilessly to get it working again on her tablet.
Click to expand...
Click to collapse
No i'm not talking about kids app
I know, it is an old thread, but it is the closest thing I found to get the sonicare apps running.
A good source on how and what to patch is here: https://resources.infosecinstitute.com/topic/android-root-detection-bypass-reverse-engineering-apk/
The patched apps can be found here:
patched sonicare app (10.6.0): https://gofile.io/d/6riPuK
patched kids app (4.0.1): https://gofile.io/d/2OcFKB
moto-assa said:
I know, it is an old thread, but it is the closest thing I found to get the sonicare apps running.
A good source on how and what to patch is here: https://resources.infosecinstitute.com/topic/android-root-detection-bypass-reverse-engineering-apk/
The patched apps can be found here:
patched sonicare app (10.6.0): https://gofile.io/d/6riPuK
patched kids app (4.0.1): https://gofile.io/d/2OcFKB
Click to expand...
Click to collapse
Could you re-upload patch kids app? Unfortunately "This file does not exist."
Would love this patched app as well, but link no longer works.
Me too
No patched app is needed.
1. Open Magisk app*.
2. Go to "Settings".
3. Enable "Enforce DenyList".
4. Tab on "Configure DenyList".
5. Search for Sonicare app and tab on it.
6. Enable all displayed sliders. (two for me)
7. That's it.
Have fun to use Sonicare app with your rooted device.
* latest Magisk app 25.2 (25200)(33)
resi83 said:
No patched app is needed.
1. Open Magisk app*.
2. Go to "Settings".
3. Enable "Enforce DenyList".
4. Tab on "Configure DenyList".
5. Search for Sonicare app and tab on it.
6. Enable all displayed sliders. (two for me)
7. That's it.
Have fun to use Sonicare app with your rooted device.
* latest Magisk app 25.2 (25200)(33)
Click to expand...
Click to collapse
Thanks resi83.
I did that.
Unfortunately on my device (Galaxy Tab S2, LineageOS 17.1) I still get the jailbreak message.
joehensley said:
Thanks resi83.
I did that.
Unfortunately on my device (Galaxy Tab S2, LineageOS 17.1) I still get the jailbreak message.
Click to expand...
Click to collapse
Sorry to hear that, joehensley!
Described way works fine for me on two different systems without the jailbreak message or other issues:
- Galaxy S10+ (G975F) with stock firmware (one ui 4.1 aka Android 12) + rooted via Magisk
- Galaxy A5 (A520F) with LineageOS 18.1 + rooted via Magisk
I'm sorry! :-/
Maybe someone else has also tested it and can give us feedback!? (@All)
DasioX said:
I ran into same problem.
I downloaded APK, modified methods for verifying root a tampered package, recompile, resign and it's working.
If anyone interested I can upload it somewhere, not sure if it can be uploaded on XDA directly.
Click to expand...
Click to collapse
Can you give me a download link ? Which version did you patch?
Nope.
^Preemptively answering all PMs.
This sounds amazing, May i ask for a very wanted feature? Android 10(Q) battery! If you make this possible ill love you to the ends of the world and donate a bottle of something good lol ?
Thanks for this. Can you tell me if the transcripts for screened calls are available with this?
mikkis2k said:
This sounds amazing, May i ask for a very wanted feature? Android 10(Q) battery! If you make this possible ill love you to the ends of the world and donate a bottle of something good lol
Click to expand...
Click to collapse
What are you asking for?
lollyjay said:
Thanks for this. Can you tell me if the transcripts for screened calls are available with this?
Click to expand...
Click to collapse
I'm not sure if call screen saves the transcript, but I've interacted with live transcriptions with multiple responses. You can see my screenshots in the other call screen thread.
TotallyAnxious said:
What are you asking for?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/themes/magisk-aod-lockscreen-weather-mods-oos-t3847008
"v1.7 (23/04/2019)
- Add Android Q battery icon style"
This, if its possible tho, its weird that the oneplus 6 thats on pie can and we cant, you think its possible? ?
mikkis2k said:
https://forum.xda-developers.com/oneplus-6/themes/magisk-aod-lockscreen-weather-mods-oos-t3847008
"v1.7 (23/04/2019)
- Add Android Q battery icon style"
This, if its possible tho, its weird that the oneplus 6 thats on pie can and we cant, you think its possible? ?
Click to expand...
Click to collapse
No idea. I'll maybe look into it. But it's not something that immediately hits me as "hey I can do that". I'm incredibly lazy and stoned a lot (stage 3 colon cancer survivor). So keep that in mind lol
Well dang, I still can't get call screening even with this. That's the only feature I truly missed when I left pixel 2 xl for a op7pro. I just have the worst luck trying to get it back.
Also I had a super nice stable device on 9.5.13 with root and a lot of nice things and the only reason I even went to 10 was the other thread said it was working on 10 and xxx said it worked on 10 and now I've been on 10.0.1 for 3 days and it's the buggiest thing I've used ever
Sent from my OnePlus7Pro using XDA Labs
spart0n said:
Well dang, I still can't get call screening even with this. That's the only feature I truly missed when I left pixel 2 xl for a op7pro. I just have the worst luck trying to get it back.
Also I had a super nice stable device on 9.5.13 with root and a lot of nice things and the only reason I even went to 10 was the other thread said it was working on 10 and xxx said it worked on 10 and now I've been on 10.0.1 for 3 days and it's the buggiest thing I've used ever
Click to expand...
Click to collapse
It's incompatible with your set up or you didn't follow the directions. (I'm not angry). But I've posted screenshots proving it works
So try eliminating variables till it works.
https://forum.xda-developers.com/on...bling-google-pixel-call-t3946535/post80596215
TotallyAnxious said:
It's incompatible with your set up or you didn't follow the directions. (I'm not angry). But I've posted screenshots proving it works
So try eliminating variables till it works.
https://forum.xda-developers.com/on...bling-google-pixel-call-t3946535/post80596215
Click to expand...
Click to collapse
Well I am on the T-Mobile version converted to international so mine is the gm1915 which you already said might not work. I completely clearer out every magisk module I had, rebooted to a stock rooted phone and things were fine, installed your first module, rebooted things were fine, installed the companion module and get a bootloop. Thankfully I have twrp and uninstalled the companion module and now it boots. I just have a gut feeling it's not going to work on here and I REALLY hate wiping my data so I'm just going to wait and see if someone else makes a breakthrough on the gm1915 model
Sent from my OnePlus7Pro using XDA Labs
spart0n said:
Well I am on the T-Mobile version converted to international so mine is the gm1915 which you already said might not work. I completely clearer out every magisk module I had, rebooted to a stock rooted phone and things were fine, installed your first module, rebooted things were fine, installed the companion module and get a bootloop. Thankfully I have twrp and uninstalled the companion module and now it boots. I just have a gut feeling it's not going to work on here and I REALLY hate wiping my data so I'm just going to wait and see if someone else makes a breakthrough on the gm1915 model
Click to expand...
Click to collapse
Well you didn't follow the instructions. You didn't install Google phone. Please reread.
If you don't install Google phone before flashing the companion. It won't boot.
I provided clear instructions. Follow them and you'll get call screen.
How to install (Magisk Manager or TWRP):
0. Uninstall kirisakura kernel companion, it's included.
1. Install "Anxious7Pro_v*.zip".
2. Reboot.
3. Install google phone apk from apkmirror or just use the apk in the companion module.
4. Set up google phone, i.e. grant all permissions (including "Draw over other apps" and "Modify system settings"), set as default phone app, open app and set up available features.
5. Install "Anxious7ProCompanion_v*.zip".
6. Reboot.
7. Profit.
Also you should pretty much always have BusyBox installed if you're rooted.
TotallyAnxious said:
Well you didn't follow the instructions. You didn't install Google phone. Please reread.
If you don't install Google phone before flashing the companion. It won't boot.
I provided clear instructions. Follow them and you'll get call screen.
How to install (Magisk Manager or TWRP):
0. Uninstall kirisakura kernel companion, it's included.
1. Install "Anxious7Pro_v*.zip".
2. Reboot.
3. Install google phone apk from apkmirror or just use the apk in the companion module.
4. Set up google phone, i.e. grant all permissions (including "Draw over other apps" and "Modify system settings"), set as default phone app, open app and set up available features.
5. Install "Anxious7ProCompanion_v*.zip".
6. Reboot.
7. Profit.
Also you should pretty much always have BusyBox installed if you're rooted.
Click to expand...
Click to collapse
I have no idea what kirisakura kernel companion is, but is compatible with Smurf kernel? Could that be my problem?
I also had Google phone installed before I did this, I preferred it over oos dialer from the start
Sent from my OnePlus7Pro using XDA Labs
spart0n said:
I have no idea what kirisakura kernel companion is, but is compatible with Smurf kernel? Could that be my problem?
I also had Google phone installed before I did this, I preferred it over oos dialer from the start
Click to expand...
Click to collapse
You should follow the instructions. If it says install Google phone, you should do that. If it's already installed that means you should uninstall to install. And it's just a handful of shell script commands. It is NOT the issue.
I'm not trying to be difficult. But you've twice not followed the instructions. If you don't follow them. It won't work.
The instructions were set up specifically for this. The non-boot that is caused by Google phone being installed as a system app prior to being a user app. I have no idea why in hell that would cause a non-boot. But it does. As I said I am very lazy. I did everything I could to make this a one and done module. So I wouldn't have to provide much support.
Kirisakira companion is listed as feature but I actually rewrote it and that will probably be put into the original mod from freak07. It's just to emphasize not needing to install both.
I think it's ridiculous it requires instructions but it's the only consistent way I've found to get all the listed features working. Please please please ? ?? read them carefully and follow them. Meaning the below paragraph is the ridiculous part btw.
It makes no sense Google phone causes a non-boot when installed as system app first. Even in a module by itself. It causes that.
I spent a week figuring out the easiest way to do this. And I got it down to under 10 steps. Please follow them.
I even spent time leanring how the unity module template works ecause the companion module is unity. And I'm really lazy.
Simplified instructions
How to install (Magisk Manager or TWRP):
0. Uninstall Kirisakura kernel companion and Google Phone, if both/either are installed. Reboot if you uninstalled.
1. Install "Anxious7Pro_v*.zip".
2. Reboot.
3. Install google phone apk from apkmirror or just use the apk inside the companion module.
4. Set up google phone, i.e. grant all permissions (including "Draw over other apps" and "Modify system settings"), set as default phone app, open app and set up available features.
5. Install "Anxious7ProCompanion_v*.zip".
6. Reboot.
7. Profit.
If you don't follow the instructions, you'll probably end up in a non-boot/bootloop.
@TotallyAnxious I will post here. I will be doing clean install of Beta 4 in a couple of hours, and post feedback here. One question though... I am a beta tester for Google Phone. Should I not use it, and instead install the nodpi version of latest .APK that you linked?
Sent from my JiaYu S3 using XDA Labs
lollyjay said:
@TotallyAnxious I will post here. I will be doing clean install of Beta 4 in a couple of hours, and post feedback here. One question though... I am a beta tester for Google Phone. Should I not use it, and instead install the nodpi version of latest .APK that you linked?
Click to expand...
Click to collapse
Didn't you just confirm it works with that screenshot? And I use beta too. But I have stable in the companion module and you can use any verison. I just don't want to provide a non stable starting point. I get less issues reported that way haha you'll learn overtime I consider how to minimize the effort I need to put into support beyond the OP. I'm incredibly lazy.
TotallyAnxious said:
Didn't you just confirm it works with that screenshot? And I use beta too. But I have stable in the companion module and you can use any verison. I just don't want to provide a non stable starting point. I get less issues reported that way haha you'll learn overtime I consider how to minimize the effort I need to put into support beyond the OP. I'm incredibly lazy.
Click to expand...
Click to collapse
lol same here (lazy). But I think that testing your modules with clean beta 4 install is worth the time and effort.
Sent from my JiaYu S3 using XDA Labs
lollyjay said:
lol same here (lazy). But I think that testing your modules with clean beta 4 install is worth the time and effort.
Click to expand...
Click to collapse
I don't think it is but I haven't tried beta OnePlus software yet. But I doubt it's gonna be that different with a clean install. Can you post the screenshot here so people see it works? Until it's posted here, people can click the link to see it.
https://forum.xda-developers.com/on...-nolimits-7-0-speed-ram-t3933927/post80645203
TotallyAnxious said:
I don't think it is but I haven't tried beta OnePlus software yet. But I doubt it's gonna be that different with a clean install. Can you post the screenshot here so people see it works?
Click to expand...
Click to collapse
Sure, np
Sent from my JiaYu S3 using XDA Labs
Hi, Ive just followed the instructions and got this working.. but i previously had the google phone installed as system app so went to my uninstaller and uninstalled 3 things, phone, phone .com and android.phone i think it was and now i have no mobile data.
Any idea what i install again to get this back? Thanks!
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.
I'm not able to open the Android camera app anymore. WIth Edxposed disabled it works. So I'm wondering if anyone on Android 11 Nov update with Edxposed has camera working. If so, could you kindly tell me your setup (ie. Edxposed version, etc.)?
Edit: It looks like the Camera update from Nov 17 is what broke this. After uninstalling the update it works.
I have the same problem - how did you uninstall the update?
EDIT: Nevermind I figured it out ?
Uninstalling the update down to 7.3.021 is an okay fix... but is there any way to update it to something more recent without installing 8.1.011 from the Play Store which is definitely broken with EdXposed?
I tried the APK Mirror installer with a split APK, but get a "verification did not succeed" error. This is with USB/ADB verification disabled.
I tried an old 7.6 APK with MiXplorer trying to install with root and it also didn't work.
I don't think I use the camera enough to even know the difference between 7.x and 8.x... I guess I'm just curious.
Anyone found a solution for this? Only stock version is working.
Apparently if you clear the cache/data of Google Play Services, the APK Mirror Installer will have better luck installing other versions.
jljtgr said:
Uninstalling the update down to 7.3.021 is an okay fix... but is there any way to update it to something more recent without installing 8.1.011 from the Play Store which is definitely broken with EdXposed?
I tried the APK Mirror installer with a split APK, but get a "verification did not succeed" error. This is with USB/ADB verification disabled.
I tried an old 7.6 APK with MiXplorer trying to install with root and it also didn't work.
I don't think I use the camera enough to even know the difference between 7.x and 8.x... I guess I'm just curious.
Click to expand...
Click to collapse
For pass the dread "verification did not succeed" message, clear your Google Play framework data. You will need to resetting some personalization settings (you will know when it happens) but install of 8.x camera app will work.
I had the same issue with edxposed and google camera 8.1, but all of a sudden it started working today. Not really sure what I did that made it work.
I was playing around with edxposed back and forth. Originally had Riru v21.2 installed (where camera 8.1 didn't work), so I installed Riru v23 over it. Rebooted but camera still didn't work. Went back to v21.2 or v21.3 and then went back to v23. I may have done a few more uninstaling/reinstalling and now camera 8.1 opens without crashing.
With camera 8.1 working, I have the following installed: magisk manager 21101, riru v23, riru-edxposed v0.5.0.6 (sandhook), edxposed manager 4.5.7. But the odd thing is that I've had the same apps/modules installed when camera was not working.
What I noticed different this time is that Edxposed manager says "Edxposed Framework is not installed" whereas before it would say something like, "installed but not active." That made we think that edxposed wasn't installed or active, so i tested with 2 xposed modules (fingerface and disableflagsecure) and they both work... so I'm pretty sure edxposed is active.
I also cleared the cache and storage on the camera app but I don't think that did anything.
I have the same problem
neo_lithic3K said:
I had the same issue with edxposed and google camera 8.1, but all of a sudden it started working today. Not really sure what I did that made it work.
I was playing around with edxposed back and forth. Originally had Riru v21.2 installed (where camera 8.1 didn't work), so I installed Riru v23 over it. Rebooted but camera still didn't work. Went back to v21.2 or v21.3 and then went back to v23. I may have done a few more uninstaling/reinstalling and now camera 8.1 opens without crashing.
With camera 8.1 working, I have the following installed: magisk manager 21101, riru v23, riru-edxposed v0.5.0.6 (sandhook), edxposed manager 4.5.7. But the odd thing is that I've had the same apps/modules installed when camera was not working.
What I noticed different this time is that Edxposed manager says "Edxposed Framework is not installed" whereas before it would say something like, "installed but not active." That made we think that edxposed wasn't installed or active, so i tested with 2 xposed modules (fingerface and disableflagsecure) and they both work... so I'm pretty sure edxposed is active.
I also cleared the cache and storage on the camera app but I don't think that did anything.
Click to expand...
Click to collapse
I tried it but it didn't work, it only works with v 21.3 but the modules stopped working. Hopefully a solution comes out.
Add gcam to black list and reboot. Just tried and it works
peter_dk01 said:
Add gcam to black list and reboot. Just tried and it works
Click to expand...
Click to collapse
I tried updating Google Camera to 8.1, immediately didn't work as expected.
Added to Exposed blacklist, rebooted... still didn't work.
Added to Exposed Compat list, rebooted... still didn't work.
Downgraded to 7.1, works again.
Before installing 8.1, I added Camera to Exposed blacklist. Just for safe measure also added to magisk hide. Rebooted, installed 8.1 and it worked.
Don't know if all steps are necessary but not gonna tweak anything since I don't know how sensitive it is.
Added to Magisk Hide, Xposed Blacklist, Xposed Compat list, rebooted; installed 8.1.101.x... force closes immediately.
thx, it worked for me. I did it after I already installed 8.1
dortok said:
Before installing 8.1, I added Camera to Exposed blacklist. Just for safe measure also added to magisk hide. Rebooted, installed 8.1 and it worked.
Don't know if all steps are necessary but not gonna tweak anything since I don't know how sensitive it is.
Click to expand...
Click to collapse
dortok said:
Before installing 8.1, I added Camera to Exposed blacklist. Just for safe measure also added to magisk hide. Rebooted, installed 8.1 and it worked.
Don't know if all steps are necessary but not gonna tweak anything since I don't know how sensitive it is.
Click to expand...
Click to collapse
I did this except add to magiskhide and it worked.. uninstalled updates. Compatibility list camera app, rebooted then open it. After update back to 8.1. and opened camera..works great again
What fixed the problem for me was downloading the latest canary YAHFA build in exposed manager. And flashing it in Magisk. I already had configured the compatibility settings for the camera module.
peter_dk01 said:
Add gcam to black list and reboot. Just tried and it works
Click to expand...
Click to collapse
This is all I had to do on my Pixel 4a 5G also. Thanks!
For anyone wondering, in EdExposed, if I go to XHide and hide camera it works. Hope this helps!
Hide camera in black list.
Latest version of exposed, riru, and riruedxposed June 21 update stock rooted. Working flawlessly
LSPosed is a better choice
EdXposed has not been updated for too long
Anyone found a solution? I can't get it to work hiding gcam on xposed blacklist and magiskhide