I test app builds for (a little) income. The app I use to test builds is called UserTesting. The app records my screen during while I test builds.
Since rooting my phone, I've been unable to successfully complete a test. I accept a test, start the screen recorder, and then I get a notification: "Your test has been cancelled." I believe this is related to rooting, since I never had this problem before.
I've tried to fix it using:
Magisk Hide
Magisk Hide Props Config > Changing the fingerprint of my phone
By using those solutions, I've been able to run my banking apps. But I still can't get UserTesting working.
Theories:
Even though I've blocked UserTesting from seeing that my phone is rooted, maybe it still manages to do it via the screen recorder? Could that be?
My phone runs Android 10, but the fingerprint I chose was Android 9, because that was the latest available in Props. Could that be causing problems?
Does anyone know why this app isn't working and how I can fix it? Thank you.
My specs:
Sony Xperia XZ1 Compact
Running LineageOS 17.1 Unofficial 1.6
Magisk 20.4 (20400)
Related
I looked through as many threads as I could before post posting. I suddenly have an issue that is vexing me to no end. Certain apps, with no rhyme nor reason that I can discern, have suddenly become greyed out when attempting to install them via traditional means. . .and by that I mean, via the package installer. When using an app such as APK Installer Pro, I have no issue whatsoever. I am not running any apps such as screen dimmers that employ a screen overlay and I took the extra step to disable all screen overlays to test my theory. The only change I tried was playing with the Xposed Framework for Nougat. Upon installing it, I noticed this behavior. So, I deleted Xposed, reflashed my ROM (LineageOS for Shamu) and went back to exactly as I had before. I am really struggling with this. Any thoughts and/or help would be appreciated.
ClubWDW said:
I looked through as many threads as I could before post posting. I suddenly have an issue that is vexing me to no end. Certain apps, with no rhyme nor reason that I can discern, have suddenly become greyed out when attempting to install them via traditional means. . .and by that I mean, via the package installer. When using an app such as APK Installer Pro, I have no issue whatsoever. I am not running any apps such as screen dimmers that employ a screen overlay and I took the extra step to disable all screen overlays to test my theory. The only change I tried was playing with the Xposed Framework for Nougat. Upon installing it, I noticed this behavior. So, I deleted Xposed, reflashed my ROM (LineageOS for Shamu) and went back to exactly as I had before. I am really struggling with this. Any thoughts and/or help would be appreciated.
Click to expand...
Click to collapse
You updated to September security patch?
I believe so. I update the moment LOS releases their update.
ClubWDW said:
I believe so. I update the moment LOS releases their update.
Click to expand...
Click to collapse
I think it's a bug in all ROMs which have october security patch. From the package installer open recents apps and then select the installer again, that fix the problem.
It is a bug in LOS. If you'll minimize installation window, and execute it again from file manager - install button becomes active
The title says it all... does anyone use GrapheneOS? Thoughts? Likes/dislikes?
Are there any phones that are better for it than others? I was looking at the Pixel 3a.
Hi sniper8752,
I know you question is now a few months old (i hope i'm not to late for my answer).
I guess cause there are nearly no xda GrapheneOS threads a question such yours running under the "radar".
I'm on, well let's say, GrapheneOS in examination marks because i don't use the OS on my pixel 4 xl as the dev intented it.
I don't know whether you were on the GrapheneOS website in the past. According to the website you should install GrapheneOS once over fastboot and lock the bootloader again to get the AVB fully working again.
That give you the most security cause you can only boot GrapheneOS and install GrapheneOS Updates over the build-in updater app.
But from my knowledge you can't install EdXposed or Magisk then cause you change partitions and AVB blocks the booting process then.
So i'm using GrapheneOS as normal Custom Rom and unlocked Bootloader to be able to use Root with Magisk.
That why i say i'm having a GrapheneOS in examiniation marks
From user view it's a clean Android 10 ROM without (!) Gapps etc. This won't change cause it a Rom for people which care about privacy and security.
What i really like too are the facts that it explicity apply the full security patches on the supported devices (which are only the pixels) and that it uses a securized kernel and some other under the hood security improvements.
I'm using the rom (stable channel) since a few days now and it's runs totally smooth and i didn't find any bugs
so far.
Atm i'm thinking to offer unofficial builds from the rom with according Magisk pre-patched boot images here on xda. But i'm not completly sure about that.
Edit:
And i forgot still one thing: The support from GrapheneOS for a device ends if google stops the support for it. Again the reason is security: Some parts of your device gets updates through the device oem. GrapheneOS can't cover this so the dev doesn't support the device anymore.
All in all GrapheneOS has another philosophy then most of the custom roms here on xda. It doesn't want to extend the lifetime of devices. It want to gives the user a more privacy and securize-friendly rom during the lifetime of device.
Hey mate - did you manage to get for example Google Photos running if you add MicroG? (in terms of Backup).
I am still not able to ditch that (at least until my full backups from the Pixel seize to exist Jan 2021 I believe...).
Mind you that the Google Photos works just fine on CalyxOS with backup functions operating.
GCam works on both (Graphene with a Services spoofer apk). Still secure.
CalyxOS using the MicroG.
Graphene OS does not allow me to use Google Photos's backup function. I've read that if I backup using Titanium root and then deploy in Graphene (with root) it should work. Using your method + Magisk maybe I can make this work ...
Battery life on Graphene has been epic for me ...
GPS was very slow and sort of inaccurate on both ...
For all else I am perfectly fine with both.
I have recently rooted my S21, and it works perfectly except for apps such as Paypal having issues around the use of fingerprints.
I can unlock the phone with fingerprints, but every app with the ability to read fingerprints fails. Is this happening for anyone else, and does anyone have any tips?
you needed to backup the DRM keys or use hacked kernal .img
i dont know if there is workaround yet for the S21 series
some app can hack this, but its ilegal AFAIK
also netflix and similar apps might not work well or at all for you
I seem to have fixed the issue. I traced it down to being related to the safety-net magisk module I had flashed. It turns out there seem to be known issues with it, and have been resolved in a test release (version 2.0 I believe)
Pisaman2 where did you get ver 2.0 from plz. Also did you have to use magisk props to change fingerprint like before? Or can you just install ver 2.0 and it will work without issues.
[Please let me know if this should be posted elsewhere, somewhere more targeted at rooted phones wherever that might be.]
I have an SM-G998U, bootloader unlocked and rooted with Magisk. (Official ROM still.) I'm experiencing some odd behavior with biometrics; for example...
LastPass reports a "change in biometrics" and is requiring both my master password AND my fingerprint; earlier editions on a different device (LG V20, likewise rooted) would only complain about being installed on a rooted device but would otherwise operate normally (current version on this phone makes no such complaint);
My medical records app refuses to let me use biometrics at all;
My banking app happily lets me use my fingerprint as if nothing is amiss.
I don't know much about how biometrics work on the S21, or how Samsung may have tried to harden them (e.g. via Knox). I don't mind tinkering and I don't mind risking the phone; does anyone have any thoughts (or knowledge) as to what I might try to make the complaining apps work more like nothing is unusual? (Note: MagiskHide and Storage Isolation (arm version) do not seem to help in the examples above.)
dwkindig said:
[Please let me know if this should be posted elsewhere, somewhere more targeted at rooted phones wherever that might be.]
I have an SM-G998U, bootloader unlocked and rooted with Magisk. (Official ROM still.) I'm experiencing some odd behavior with biometrics; for example...
LastPass reports a "change in biometrics" and is requiring both my master password AND my fingerprint; earlier editions on a different device (LG V20, likewise rooted) would only complain about being installed on a rooted device but would otherwise operate normally (current version on this phone makes no such complaint);
My medical records app refuses to let me use biometrics at all;
My banking app happily lets me use my fingerprint as if nothing is amiss.
I don't know much about how biometrics work on the S21, or how Samsung may have tried to harden them (e.g. via Knox). I don't mind tinkering and I don't mind risking the phone; does anyone have any thoughts (or knowledge) as to what I might try to make the complaining apps work more like nothing is unusual? (Note: MagiskHide and Storage Isolation (arm version) do not seem to help in the examples above.)
Click to expand...
Click to collapse
AFAIK rooting (triggering KNOX) or unlocking will not (directly) break biometric features.
Maybe it's just an issue with a few apps that refuse to work properly.
MagiskHide would have been my first try too. Check for Magisk updates. Hopefully the hiding will be optimized ... so that your apps can no longer recognize root.
Backstory: So got my daughter a bluetooth enabled toothbrush named in title, and loaded up the app for it:
Philips Sonicare For Kids - Apps on Google Play
Transform brush time into fun time!
play.google.com
Running on a OnePlus 6, Android 10 stock firmware other than bootloader unlocked, Magisk installed. Start it up, whines it is rooted and refuses to run. Sputter some colorful language, add app to Magisk Hide, restart, poof, works great.
Now daughter likes it, and don't want to give her my phone twice a day... so open the drawer and pull out an older phone, LG G6. Old firmware, prob full of security issues, figure I'll install LineageOS on it. OK, great, get through all that, shiny running system... repeat app install... and ugh... "t3h r00t3d phone!".
This time, Magisk Hide isn't "fixing" the problem, and I am curious what the difference is... same app version on both phones. Safetynet check passes on both phones. The only real differences I can cite are (1) Android 11 OS base and (2) Roar Gapps MiniMe build (vs full Gapp suite on stock OnePlus rom). At this point, there aren't other apps on the device (e.g. SuperSU or similar usual suspect).
Any suggestions on what is different that an app could check and call out a rooted phone?
Answering my own post, in case anyone searches this and finds it helpful...
Turns out this app appears to blacklist Lineage OS.
Reflashed clean, OS only... fail. (No root or safetynet at this point)
Added somewhat normal Gapps, now with working safetynet... fail.
Didn't need to install Magisk at this point.
Lets test the theory... grab another OS image at random, flash it (still no Gapps, Magisk, SN)... success!
Install Magisk, still success!