Database Info

Substratum beta not working in fresh install of PIE

Tried using substratum beta 999 but I get a message saying it can't fall back to rooted mode. I'm using magisk 16. Any ideas?
Sent from my [device_name] using XDA-Developers Legacy app

gvsukids said:
Tried using substratum beta 999 but I get a message saying it can't fall back to rooted mode. I'm using magisk 16. Any ideas?
Click to expand...
Click to collapse
Go back to 998 and it'll work

Also, for good measure, update to Magisk 16.7 Beta.

Any themes that work?
Sent from my [device_name] using XDA-Developers Legacy app

gvsukids said:
Any themes that work?
Click to expand...
Click to collapse
I was using flux on my essential phone without any issues on the dp's

crixley said:
I was using flux on my essential phone without any issues on the dp's
Click to expand...
Click to collapse
Which flux? The one by ginnias didn't work
Sent from my [device_name] using XDA-Developers Legacy app

Sorry if it's the wrong place to ask, but:
Does substratum work without root on Android P?
Also, can someone point me to the beta apk, I tried 998 from apkmirror and it didn't work? Thanks

harisyks said:
Sorry if it's the wrong place to ask, but:
Does substratum work without root on Android P?
Also, can someone point me to the beta apk, I tried 998 from apkmirror and it didn't work? Thanks
Click to expand...
Click to collapse
No it doesn't work without root. 998 refers to the beta substratum not the previous version from the play store. A weird situation happened in which beta is currently a version number behind play store version. Anyways you'll need that apk from telegram.

I'm new to using Substratum and i got the 998 version on the web, I'v tried a few different them but none of them have worked, i found Ethereal theme which is updated to work with Pie, but i still get the same results. After selecting all the options in Substratum and clicking build and install, all goes good and shows it was compiled but nothing in the phone changing. I go to manager and it said no overlays installed. Can anyone help please.
Thanks in advance.

FilthyFord said:
I'm new to using Substratum and i got the 998 version on the web, I'v tried a few different them but none of them have worked, i found Ethereal theme which is updated to work with Pie, but i still get the same results. After selecting all the options in Substratum and clicking build and install, all goes good and shows it was compiled but nothing in the phone changing. I go to manager and it said no overlays installed. Can anyone help please.
Thanks in advance.
Click to expand...
Click to collapse
Reboot, then go back to manager in Substratum to Enable.

lightningdude said:
Reboot, then go back to manager in Substratum to Enable.
Click to expand...
Click to collapse
Am i supposed to have this installed and enabled. Or anything from Majisk? When i go back to manager in Substratum there is nothing there. It tells me to compile a theme to use the manager.

FilthyFord said:
Am i supposed to have this installed and enabled. Or anything from Majisk? When i go back to manager in Substratum there is nothing there. It tells me to compile a theme to use the manager.
Click to expand...
Click to collapse
If you're rooted with Magisk, and are using Substratum version 998, compile your theme as normal, tapping build and enable when you've selected your overlays. When your phone finishes that process, reboot your phone. Go back into Substratum, and if your theme is compatible with Pie, you'll have overlays in the Manager tab.
For example, I use Sai's Oreo Theme, which doesn't advertise being compatible, but it is. Just don't install the navbar overlay. I also use Stasusbar Clock Tweaks for P, from these forums.

lightningdude said:
If you're rooted with Magisk, and are using Substratum version 998, compile your theme as normal, tapping build and enable when you've selected your overlays. When your phone finishes that process, reboot your phone. Go back into Substratum, and if your theme is compatible with Pie, you'll have overlays in the Manager tab.
For example, I use Sai's Oreo Theme, which doesn't advertise being compatible, but it is. Just don't install the navbar overlay. I also use Stasusbar Clock Tweaks for P, from these forums.
Click to expand...
Click to collapse
Still a no go for me. I tried Sai's theme that you mentioned and unchecked the navigation so that it don't need with it. Built and enabled, once done the system UI restarted, i then restarted the phone and go back into substratum too the manager and it still says to compile a theme to use the manager. Right now I'm using substratum 998, I've tried with Majisk 16.0, 16.4 and 16.7. not sure what's going on with mine. Thanks for the help though.
---------- Post added at 01:03 PM ---------- Previous post was at 12:55 PM ----------
Unless it's because i didn't clean flash Pie. I removed the -w and flashed that way. But everything else send to be working properly. I might redo the flash today and try it on a clean install.

For everyone having the issue of no overlays being installed after reboot... You are using the wrong substratum APK. You NEED the 998 BETA version from TELEGRAM. You will ONLY be able to get it from TELEGRAM. Searching on Google will only get you an older play store version of the same number.
Now, any questions?

k.s.deviate said:
For everyone having the issue of no overlays being installed after reboot... You are using the wrong substratum APK. You NEED the 998 BETA version from TELEGRAM. You will ONLY be able to get it from TELEGRAM. Searching on Google will only get you an older play store version of the same number.
Now, any questions?
Click to expand...
Click to collapse
How do i get on the telegram conversation to get the apk

I have similar problems.
Got substratum to work with 'dark grey' overlay.
This was using 998 from apk-mirror.
Now I have this, and only this one overlay in the 'manager'-tab in substratum.
I can freely activate and deactivate it.
However, I can NOT delete it.
I can not compile other overlays, and I can not compile it again with different settings/colors.
Deinstalling and reinstall of substratum did not help, reboot in between did not help.
Finally I got 998 from the telegram beta channel, downloaded and tried 3 different builds, nothing changed.
I am still semi-happy -- at least I can apply the compiled dark grey overlays, which is better than nothing.
Oh yes, and I also flashed Android PIE again before problems started, using the "-w" method, as I got stuck in a bootloop after applying a font.

hardcoremildred said:
I have similar problems.
Got substratum to work with 'dark grey' overlay.
This was using 998 from apk-mirror.
Now I have this, and only this one overlay in the 'manager'-tab in substratum.
I can freely activate and deactivate it.
However, I can NOT delete it.
I can not compile other overlays, and I can not compile it again with different settings/colors.
Deinstalling and reinstall of substratum did not help, reboot in between did not help.
Finally I got 998 from the telegram beta channel, downloaded and tried 3 different builds, nothing changed.
I am still semi-happy -- at least I can apply the compiled dark grey overlays, which is better than nothing.
Oh yes, and I also flashed Android PIE again before problems started, using the "-w" method, as I got stuck in a bootloop after applying a font.
Click to expand...
Click to collapse
Can you send me a link to the telegram group please

FilthyFord said:
Can you send me a link to the telegram group please
Click to expand...
Click to collapse
I connected to this telegram channel:
https://t.me/substratumci
which is announced as beta-channel in the official substratum telegram group link list.

Something like Xposed-RootCloak for Pie

Anyone know of a way to have the phone report it is not rooted like you could with Xposed/Rootcloak?

toy4x4 said:
Anyone know of a way to have the phone report it is not rooted like you could with Xposed/Rootcloak?
Click to expand...
Click to collapse
Have you tried magisk hide?
Sent from my [device_name] using XDA-Developers Legacy app

Yes. It still seems to have issues app wise. Maybe the app is installing some module I don't know of? I grab the app off of the play store, mark it in MagiskHide and then install Outlook on top of that and mark it in MagiskHide. It still reports root.

toy4x4 said:
Yes. It still seems to have issues app wise. Maybe the app is installing some module I don't know of? I grab the app off of the play store, mark it in MagiskHide and then install Outlook on top of that and mark it in MagiskHide. It still reports root.
Click to expand...
Click to collapse
Does magisk show that your phone passes the safety net check?

Have you used the feature to hide the Magisk manager app? It renames the package so other apps don't know it is installed. Apps don't need special permissions to retrieve installed package names, Pokemon go won't work unless you do that. Also, it tended to not work if you had a folder by the name of Magisk even though it didn't have storage permissions it would get a different error if the file was there vs not there.

Philips Sonicare 4.5 Bluetooth toothbrush app

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?

Can't successfully hide root with magisk 18.1 for square reader app

I've been rooting my Android phones since about 2012, but today I got a point of sale card reader for my business and I'm not having any luck hiding root from the app (square reader app). The app wont work at all so I tried a number of options in magisk manager (magisk hide the app, hide magisk manager, enable core mode only) rebooting between each try and clearing the square reader app data and setting it up fresh each time, but still no luck
I tried to uninstall magisk but the app still didn't work. So I eventually flashed back to stock and got rid of magisk all together, now the app works but I don't have root...
I tried installing magisk again after I got the app to work and hiding root from the app before I opened it up again, but it still somehow knew the device was rooted
Can anyone suggest anything I haven't tried? Or is there an alternative to rooting the OnePlus 6 (other than magisk) and hiding root? I had a bit of a look around but didn't find anything.
Thanks

I had to go back to 18.0, heard 18.2 works as well.

qbanlinxx said:
I had to go back to 18.0, heard 18.2 works as well.
Click to expand...
Click to collapse
Thanks for your reply. I tried with 18.0, damn, it still doesn't work, it still picks up that the phone is rooted
I tried the 18.2 canary build as well (18.2-e72c6685) no luck either
This app must be looking somewhere out of the ordinary for evidence of root in the phone

I have a bank application and facing the same problem. Hope someone can help us to make applications run by hiding the root
I think recent applications are looking for if knox security is tripped !! so in this case Magisk will not help

Ooohhh had to subscribe to this as I face the exact same issue!! Been trying to get my Square reader to work for a while with root and could never figure out how they are detecting root. Using Pixel XL here

Google changed something in Safety Net in play services, it passes, yet for me, google pay fails. That COULD be the issue, though I read 18.2 fixes that. Another option I helped a friend with is if it's detecting magisk itself via the files, culprit here was pokemon go.
Try opening your Magisk settings, the tick "hide magisk manager" clear the repo cache, and rename or delete the MagiskManager folder on the root of your storage. Reboot, clear data from the square app, and try again. Keep in mind, you have to unhide magisk to update it.

Skreelink said:
Google changed something in Safety Net in play services, it passes, yet for me, google pay fails. That COULD be the issue, though I read 18.2 fixes that. Another option I helped a friend with is if it's detecting magisk itself via the files, culprit here was pokemon go.
Try opening your Magisk settings, the tick "hide magisk manager" clear the repo cache, and rename or delete the MagiskManager folder on the root of your storage. Reboot, clear data from the square app, and try again. Keep in mind, you have to unhide magisk to update it.
Click to expand...
Click to collapse
In my case, I dont think its detecting the files. The reason i say that is because I play Pokemon Go just fine with no issues. So whatever Square is doing, its something different then what PoGo is doing.

Idledev said:
In my case, I dont think its detecting the files. The reason i say that is because I play Pokemon Go just fine with no issues. So whatever Square is doing, its something different then what PoGo is doing.
Click to expand...
Click to collapse
I agree, I have no problem hiding magisk and root from other apps, the square reader app must be somehow different. I've even gone through my storage and deleted any files or folders that might suggest the phone is rooted, but still no luck...
I also went into battery optimization settings to stop magisk from being put to sleep (which might stop magisk hide from working..?), that didn't work either.
I've found a temporary workaround to my problem anyway, I realized that I can share my internet (wifi hotspot) with my ipod touch, this way square reader works as the ipod touch isn't jailbroken or modified. It just means I have to carry around my ipod touch with me, which is a better trade off for me than having a stock, non root phone

Managed to get it working today! Upgraded my Pixel XL to the Android Q beta. By doing this, I had to run Magisk canary build. Installed square, enabled Magisk hide, rebooted and it worked fine! Not sure if the Android Q beta has anything to do with it,but give the canary builds of Magisk a try

Idledev said:
Managed to get it working today! Upgraded my Pixel XL to the Android Q beta. By doing this, I had to run Magisk canary build. Installed square, enabled Magisk hide, rebooted and it worked fine! Not sure if the Android Q beta has anything to do with it,but give the canary builds of Magisk a try
Click to expand...
Click to collapse
That's awesome! What canary build did you use?
I tried the latest build a few weeks ago and it didn't work for me

Build 18120

Idledev said:
Build 18120
Click to expand...
Click to collapse
No luck for me...
I updated to the latest canary build, cleared all data from square reader app, selected magisk hide, rebooted the device. After it booted up I tried to run it and it still detected root. I have a feeling that the OnePlus OS does something that doesn't totally allow me to hide root from the square reader app. It's annoying because for other apps root can be hidden
Maybe there's something in the Android Q build that lets you hide root better

Something that seems reliable right now on 18.1, Pixel Experience and OOS :
Combine Magisk Hide with Magisk "Core Mode". This seems to do the trick for now, Google Pay is triggered with normal mode, but works in Core Mode. Same for Snapchat and banking apps like N26.
But within this, you can't use any module.
kage00 said:
I also went into battery optimization settings to stop magisk from being put to sleep (which might stop magisk hide from working..?), that didn't work either.
Click to expand...
Click to collapse
This is always a good idea, on OOS at least, Magisk being optimized sometimes prevents the granting of root rights to apps, it never reacts to kernel applications requesting root on startup for example.

There's an issue with Googlypay services apparently. You need to downgrade it (remove factory updates) so it's down to version 14.something and then it should work.
You need to disable admin rights and background data to try to prevent autoupdates as well. This thread may be useful?
https://forum.xda-developers.com/ap...e-pay-magisk-discussion-t3906703/post79155616

DaveW1972 said:
There's an issue with Googlypay services apparently. You need to downgrade it (remove factory updates) so it's down to version 14.something and then it should work.
You need to disable admin rights and background data to try to prevent autoupdates as well. This thread may be useful?
https://forum.xda-developers.com/ap...e-pay-magisk-discussion-t3906703/post79155616
Click to expand...
Click to collapse
Hmm, I'm running the magisk xXx ROM and google pay is completely debloated/removed. when I get a spare half hour I might try removing the xXx module and flashing back to stock and following the advice in that thread. I'll let you know how it goes

kage00 said:
Hmm, I'm running the magisk xXx ROM and google pay is completely debloated/removed. when I get a spare half hour I might try removing the xXx module and flashing back to stock and following the advice in that thread. I'll let you know how it goes
Click to expand...
Click to collapse
Ummm yeah.. then the problem doesn't lie within Google pay it lies within the modifications that you are using.
I have to say I have never had any issues with Google pay or Android pay or any banking app using magisk. I don't even have to hide anyting. Of course I'm also not using any modified ROMs or kernels either

Hi guys,
I have this issue for a couple years now and I just cannot find a solution!
Google Pay, and 4 banking app from two different countries work fine with my 1+6 (stock ROM OOS 9.0.9 with magisk 19.4 - 7.3.4) but Square does not.
Did anyone find a solution?
Magisk config:
Magisk hide
Two modules OOS phone record and youtube
No core mode
All banking app and Square hidden

Nope.

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!