yashsingh1/xdaforums huggingface dataset:
[Magisk] gentano:
Which rom/device?

I cant get it to work on Lineage/Xiaomi.

What are your settings? Which modules installed?

According to their error page here

Fehler

www.payback.de

"Wir haben festgestellt, dass auf diesem Gerät Software installiert ist, die in der Lage ist, Apps Dritter zu beeinflussen, zu manipulieren bzw. Daten auszulesen. Diese Software kann durch den Nutzer individuell installiert sein oder ist tlw. bereits ab Werk durch den Hersteller installiert, dies kann insbesondere bei Geräten der Hersteller Xiaomi, Huawei oder Honor auftreten."

"Sollten Sie keine dieser Software individuell installiert haben, handelt es sich bei ihrem Gerät um ein Gerät eines unsicheren Herstellers, welches wir leider nicht unterstützen können."

it might be possible that they blacklisted xiaomi, huawei and honor devices.

We need people with these devices to test this. I have only xiaomi devices and its not working on any of them.. tried with Magisk 27.0 and latest APatch.
[Magisk] Spartacus500:
I don't think these devices are blocked, I think it's about custom Roms on these devices.

Download the Securify app, install it, then add it to denylist in Magisk 27.0 and show the result
[Magisk] gentano:
"Device is running a custom ROM."

is the only anomaly.
[Magisk] Spartacus500:
And this is your main problem 🤷
[Magisk] daftndaze:
Nope, that's not all. Xiaomi device here, Magisk 27, blacklisted Payback ... same issue. Can not use app anymore
[Magisk] gentano:
how does this help?

Which ROM? Miui or Lineage or sth else? We need ROM names.
[Magisk] daftndaze:
Oh yeah... forgot to mention this... stock HyperOS 1.0.3.0 UMNEUXM.
[Magisk] gentano:
try this: https://xdaforums.com/t/payback-pay-detecting-root.4153749/post-89358645

and post your result please.. you shouldnt get the custom rom anomaly
[Magisk] Stefan6183:
My Payback app also does not start anymore since the newest update (Payback app version 24.02.0100), despite putting it on the Magisk 27.0 denylist. I have a Samsung Galaxy S22 Ultra with Android 12 stock Samsung ROM. Securify shows Environmental anomaly detected: Debugging mode is enabled. Found suspicious files.
[Magisk] gentano:
easy:

- disable debugging mode in developer options

- look on your internal storage, there should be a TWRP folder - rename it (if you use another recovery like OrangeFox, look for that folder and rename it)

try again Securify and post results
[Magisk] daftndaze:
I had "Found suspicious files". Have renamed TWRP. No anomaly. Payback still not working.

Why should Payback be able to read my root dir? It is not. The question is still there... how do they detect our "unsave" environment.
[Magisk] daftndaze:
TB Checker detects this stuff besides TWRP-dir.

No, sorry. Forget it. I missed to put Checker on deny list. 🙁
[Magisk] oricon:
I have the same probleml with payback.

MIUI 14.0.5.0 Android 12, Magisk alpha newest version, Airfrozen App

View attachment 6072112View attachment 6072113View attachment 6072114
[Magisk] Stefan6183:
I found am solution: Installed Play Integrity Fix Magisk module. I also uninstalled the Payback app before and cleared all data.

Now the Payback app works again.
[Magisk] daftndaze:
Does not work for me.
[Magisk] daftndaze:
@Stefan6183 Some more details? Which versions of Magisk, PIF? Which data cleared? Payback app data? Something else?
[Magisk] Stefan6183:
Magisk 27.0, PIF 15.8, Shamiko 1.0.1, Zygist - LSPosed 1.9.2, Magisk App freezed, cleared Payback App data, Payback App on Magisk deny list.
[Magisk] daftndaze:
Nice. Thank you! Installed and enabled Shamiko... it says it does not work because deny list is enforced... but... payback is working now! Great! Thanks again!
[Magisk] xmasman:
The same on my Phone worked
[Magisk] gentano:
Not working here.

Which ROM are you all using?

Im using Lineage and Im pretty sure Lineage is on blacklist.
[Magisk] Stefan6183:
I am on stock Samsung Android 12
[Magisk] xmasman:
Pixel 7a Stock Rom

Unlocked Bootloader

Rooted with Magisk

Modules in Magisk:

Systemless Hosts, Play Integrity Fix and now Shamiko
[Magisk] gentano:
so its working on stock rom (as expected)... anybody with a solution for Lineage?
[Magisk] meiser:
Works fine here on CrDroid (which is a LineageOS variant). I use KernelSU with PIF module. No Shamiko or whatever.
[Magisk] gentano:
Thats cool, you are the 2nd person confirming that the Payback App is working with a LOS (Variant) using KernelSU. BUT:

I dont know how to install KernelSU on Xiaomi Mi 10T (apollo) on CrDroid 10.2 (Android 14)

I dont know if there is a compatible kernel available etc.

Unfortunately APatch is also not working with the boot.img of CrDroid 10.2 (Android 14), so I cant check that out either.

Anybody can help or any alternative ideas?
[Magisk] sawdoctor:
Have you tried the KSU app to see if there's compatible kernel? If you only need to patch the kernel rather than compile its fairly straightforward if you follow the instructions
[Magisk] gentano:
ofc I did and its not compatible
[Magisk] strec007:
I actually must have built the whole system. Kernel only never worked (broken driver modules, no sound, etc.). I'm actually running LineageOS for microg on Fairphone 4. There is a docker-based builder which I successfully tweaked to include KernelSU. If interested, I can upload my repo to Gitlab.
[Magisk] gentano:
I dont think I have the knowledge to get this installed/built.

which device?

Iam currently on CrDroid on Xiaomi Mi 10t/Apollo and completely removed Magisk / unrooted my phone (bootloader still locked ofc).

Securify 1.1.0 is now saying:

and still the Payback App is not working

My argument is stil:

Payback has blacklisted Xiaomi devices at all, no matter the OS.

If you have working config for xiaomi device, post your complete config (OS, root method, root config, installed modules etc.) please.
[Magisk] dolons:
Xiaomi Mi 9T

Magisk 27 + systemless hosts 1.0 , Universal Safetynet fix v2.4.0

New Shamiko v1.1.1

Now it works again, include the last Paypack playstore update
[Magisk] sawdoctor:
Do you have a link for shamiko 1.1.1 please? Last version I have is 1.0.1
[Magisk] gentano:
Thank You for trying to help. But its not working here with that config (putting Payback App on deny list.

@sawdoctor

That Shamiko 1.1.1 is a typo, he ment 1.0.1 (he posted on another forum that he uses 1.0.1)
[Magisk] pandavova:
Finally fixed my issue using this module: https://github.com/ez-me/ezme-nodebug

I am using a Xperia 5ii with Lineage 20 (A13) and KernelSu.
[Magisk] gentano:
Thank you very much. I was really hopefully on this one as Iam expecting the problem in this direction.

However its not working for me :-( (LineageOS-Version is hidden tho in Settings > About screen, so the module seems to work)

Config:

Redmi Note 11

LOS 20 with Magisk 27002 Alpha

Magisk App hidden

Force deny list

Payback App on deny list including all 4 sub processes

PIF 15.9.7

LSPosed 1.9.2 (7024)

Any more ideas?
[Magisk] pandavova:
Are you using hidemyapplist?

You will also need LSposed for that. You also don't have Shamiko if that is your full config.

Releases · Dr-TSNG/Hide-My-Applist

An Xposed module to intercept applist detections. Contribute to Dr-TSNG/Hide-My-Applist development by creating an account on GitHub.

github.com

Releases · LSPosed/LSPosed

LSPosed Framework. Contribute to LSPosed/LSPosed development by creating an account on GitHub.

github.com

Releases · LSPosed/LSPosed.github.io

Contribute to LSPosed/LSPosed.github.io development by creating an account on GitHub.

github.com
[Magisk] gentano:
LSPosed is installed.

I already tried with HMA and Shamiko, but will try again in combination with the ezme module, thanks.
[Magisk] gentano:
Wow, its working for the first time after months lol - thank you!

What I use and need for my config (LineageOS 20 on Redmi Note 11):

Magisk 27002 Alpha with only two Magisk modules:

Nodebug from ez-me (https://github.com/ez-me/ezme-nodebug/releases/tag/v1)

Shamiko 1.0.1 (300) - You can keep enforce denylist in Magisk, at least in my case

LSPosed 1.9.2, HMA (Hide my Applist) and any PlayIntegrityFixes are not needed for Payback App to work (tested in my config).

@pandavova

Thank You again! There is only one problem now:

Since the OS informations are hided from apps the FPS in games dropped dramatically. I think its because the game doesnt know which OS I use so it doesnt know what driver to use or something like that. You have any idea how to fix that?

Maybe this is related to https://xdaforums.com/t/sm6225_performance_plus.4531933/ and the frequency of the SOC is now limited.
[Magisk] sawdoctor:
I'm having great success with this for hiding root

[MODULE] Zygisk Assistant (FOSS Root Hider)

Zygisk Assistant (FOSS Root Hider) This module is designed to hide root similar to Shamiko. While Shamiko has some other features too, this module is effective in hiding root completely unless something is directly injected into the target...

xdaforums.com
[Magisk] pandavova:
Sorry, I don't know.
[Magisk] gentano:
[MODULE] Zygisk Assistant (FOSS Root Hider)

Zygisk Assistant (FOSS Root Hider) This module is designed to hide root similar to Shamiko. While capabilities may not be the same, it's worth noting that this module is open-source whereas Shamiko is closed-source. One of the advantages of this...

xdaforums.com

means: for up to date apps from Play Store HMA seems obsolete.

@sawdoctor

Thank You, but even the fresh released ZA 2.1.0 is not working with the Payback App, while Shamiko does.
[Magisk] pandavova:
If you really care about that just disable the Lineage module and reboot (and turn it on when you need it again), you surely won't need to play games and use payback at the same time.
[Magisk] veitograf:
@gentano I'm using a pixel 7 with root and shamiko + ez-me and still can't get payback to work :(
[Magisk] gentano:
Which root method? Magisk? Apatch? KernelSU? And which version of the root method?

For Magisk You need Canary (27002 Alpha), it was not working with 27.0 Release Build for me!

You can get Canary here:

Download page: https://github.com/topjohnwu/Magisk

Direct link: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk

Apatch and KernelSU I didnt try.
[Magisk] veitograf:
I'm using magisk and I installed 27002 debug and it's still not working.
[Magisk] gentano:
Which modules in magisk? You followed EXACTLY my post https://xdaforums.com/t/payback-pay-detecting-root.4153749/post-89474307 ? Use ONLY those 2 modules in the exact mentioned version
[Magisk] Paradoxon_:
Using crdroid on Android 11, can confirm that latest play store version of payback works after switching to kitsune mask version of magisk and setting up denylist to all processes of payback. What Modules you use doesnt matter much as long you have enabled denylist on the payback app and installed a play integrity fix module.
[Magisk] snake-4:
If you're using KSU or APatch, check my post here.

Additionally this app checks for KernelSU manager so you might have to uninstall that or try with HMA.

You'll also have to clear the app's data to pass detection.
[Magisk] meiser:
Hi,

I'm running crDroid 9.15 with KernelSU 0.9.4 and Zygisk Assistant 2.1.1. Latest Payback app 24.04.2501 does not start anymore because of unsafe environment. Any idea how to fix it? Thanks!

Regards,

meiser
[Magisk] snake-4:
It's additionally checking for the KernelSU app. It will work if you uninstall that. Maybe HMA will also work but I haven't tried that.

Also, are their devs reading this thread? If so, hello developers!
[Magisk] meiser:
You're right, uninstalling the KernelSU app works. It's strange since it worked in the past to freeze the app instead of uninstalling.
[Magisk] Cydras:
Thank you guys!

After installing Magisk i get Payback working again with your help :)

I have these modules now installed:
[iPAQ rw6828, XDA Atom Software Upgrading] kingofhearts:
Is there any way to revive my ATOM life dead bootloader.

Kind Regards

Haseeb Ali
[Samsung Galaxy Watch 3] hhaghgou62:
When I measure my blood oxygen is successful.

Once 98 indicates once 87 shows . and when i check my Spo2 with my Galaxy s9 it show True

what is the problem ?
[Samsung Galaxy Watch 3] bbwolff:
It's very inaccurate, almost useless. I compared results from professional sp02 monitor, where I scored 98%, and my watch, that showed 92% at the same time.
[Samsung Galaxy Watch 3] hhaghgou62:
No have more problem for this

In where we can check Vo2 max and in where we can find Spo2 ?
[Samsung Galaxy Watch 3] kodiak799:
Actually kind of a record....

Cranked the watch down a little extra tight, and after one or two incomplete readings I got this. Most were pretty quick, a few took 15+ seconds. Sitting normally resting my hand like normally:

96, 94, 93, 94, 94 96, 94, 96, 96, 95, 95, 96, 96, 94

I know from other monitors that <95 is not accurate. So this is understated by at least 2 points. At least I know it can get consistent readings if I tighten the watch to the point of cutting off circulation!
[Samsung Galaxy Watch 3] pigglett:
A new version of Samsung health is been released today maybe is will fix this
[Samsung Galaxy Watch 3] agbva:
Here's what I found to work

no change to the band tightness, just slide the watch up a finger width or so above your wrist

As soon as you start the O2 test, use your other hand to press down on the watch at the top and bottom (where the straps attach)

This gives me consistent readings in the mid-upper 90's which look more normal
[Samsung Galaxy Watch 3] hhaghgou62:
my watch 3 show my spo2 low but when i check my spo2 with my phone sensor my spo2 is very well .
[Samsung Galaxy Watch 3] kodiak799:
There are several ways to "get it to work", none of which are how it's intended to work and none of which are going to work for sleep monitoring. On-demand checking of SPo2 really doesn't serve any practical purpose.

I hope for a software fix, but the fact that it appears to take at least 10 seconds to get a reading (when it works) doesn't give me hope that the sensors are up to the task. To be able to detect potential sleep apnea, as Samsung claims, it needs to be able to measure SPo2 at least every few seconds while you sleep. And it needs to be very consistent/accurate.

Something is going on. No way does Samsung release this feature, much less make the sleep monitoring claims, with this many people having issues. Makes me wonder if the ECG/BPM hack many of us here installed is the actual culprit. But I don't know how or why that would be the case.

On the other hand, maybe Samsung did release a half-baked feature, otherwise you're trying to sell a watch with most of the advanced health features you're promoting disabled! The fact there is currently no SPo2 monitoring during sleep, as far as I can tell, might be an indicator Samsung knows it's still wonky.

---------- Post added at 09:54 PM ---------- Previous post was at 09:43 PM ----------

Reading low doesn't really matter so long as it's consistent. Normal is 95% and above, and it fluctuates. Below 90% is generally considered to be potentially dangerous.

Sleep apnea is a condition where people temporarily stop breathing while they sleep, and this causes blood oxygen levels to drop. Too many drops, large drops and drops below 90% are indicators of a potential problem. So if you know it's reading 2-3 points low, then you're concerned with drops below 87-88%. No big deal. But the readings need to be consistent in order to know if a sudden 4-5 point drop is real. And you can see from the readings I posted earlier that the consistency appears to be a little over +/- 1%, meaning 2-3 point changes are common within the normal variance of the watch.
[Samsung Galaxy Watch 3] agbva:
It wasn't any better before I installed the BP/ECG hack, so I think you may be spot on: Samsung knows this needs work but had to release it quickly, otherwise, their announcement with all the new features would be completely empty
[Samsung Galaxy Watch 3] kodiak799:
Now you got me thinking....It's almost the same message as for BPM - keep your wrist steady at heart rate level. That's obviously not how it's going to work with sleep monitoring, and it's not how any SPo2 detector works (but IS how to properly take a BPM reading). Even that error message is half-baked.

So the watch automatically detects when you're sleeping. That would also mean the SPo2 would be automatically triggered and begin recording for sleep monitoring. Maybe that coding is somehow interfering with on-demand readings.
[Samsung Galaxy Watch 3] agbva:
And one more: when you take a BP or ECG reading, you can see your pulse on the watch and it's even and steady in both modes. With an O2 reading, it's all over the place. I often do all three at once and really notice the difference without ever moving my arm.
[Samsung Galaxy Watch 3] hhaghgou62:
Where is vo2max ? I can't see this option ??
[Samsung Galaxy Watch 3] admir83x:
I'ts not an on-demand feature. You must do the run at least 20 minutes in the HR zone above your 70% of your Max HR and when you finish your workout it will be shown in the stats of your workout (in the watch and Samsung Health as well). It will be calculated every time you spend at least 20 minutes in the mentioned HR zone. For now, VO2Max is only shown in workout stats.

Best regards
[Samsung Galaxy Watch 3] hhaghgou62:
bro i have a question why when i track my spo2 with my watch it is very variable and when i measure Spo2

with my phone it show quite accurately

allways show my spo2 low ( with my watch )
[Samsung Galaxy Watch 3] adfree:
Do you mean you have such tiny Phone like the Watch? :D

Sorry, IMHO Watch is Toy... this is soo f%&ing tiny.

We are far away from Star Trek...

Okay, we come closer to beam me up scotty... :D

Best Regards
[Samsung Galaxy Watch 3] defeat2:
[MENTION=1030585]adfree[/MENTION]

Garmin venu and vivoactive 4/4s has accurate SpO2-sensors. Their red LEDs are very strong and bright though, much brighter than their green HRM-sensors. I don't know how bright Watch 3s red LEDs are, but if they are as weak as Active 2s SpO2-sensor there's no wonder why they're not accurate.
[Samsung Galaxy Watch 3] kodiak799:
I hadn't realized it was a red LED, but now that you mention it other SPo2 sensors I've used had a red LED. But I just checked, and the red LED on the GW3 is blindingly bright when taking a SPo2 reading.

But maybe you're on to something because HR and BPM use the green LED.
[Samsung Galaxy Watch 3] defeat2:
Really? Could you try to do a sensor-test in the service menu to see if they are blindingly bright there as well? Dial *#0*# -> HRM -> EOL

If they are I think we can forget SpO2 on GWA2. Heres a comparison between the green and red light on a GWA2
[Samsung Galaxy Watch 3] defeat2:
Has samsung said anything about SpO2 reading during sleep, are they working on it??
[Samsung Galaxy Watch 3] hhaghgou62:
No bro . i think they must update the frimware . we should submit them about this problem .
[Samsung Galaxy Watch 3] defeat2:
A question to Watch 3 owners. The watch has 8gb of free storage, approximately how much of this is taken up by the tizen 5.5 software and how much is free to use? And if someone could do the HRM EOL test and compare the brightness of the green and red LEDs i would be very grateful!

Thanks in advance
[Samsung Galaxy Watch 3] kodiak799:
I believe it's 4.2gb free. Doubt it would allow you to completely fill that up, so it might be more like 3.4-3.8gb usable. But beats the heck out of my old Huawei watch which had about 2gb free, but was closer to 1.4gb usable.
[Samsung Galaxy Watch 3] defeat2:
Well, then Active 2 owners can forget about tizen 5 and Spo2 since it only has 4gb! I'm returning my watch, thanks for the info! :)
[Xiaomi Mi A1 Questions & Answers] jeffersonx:
I want to use the phone with a lan cable. I have tried a ugreen usb-c rj-49 adapter but it didn't work (apparently it has otg).

Is there an underlying issue with A1 or should I try another adapter?
[Xiaomi Mi A1 Questions & Answers] floridan:
I'm using a tp-link ue330 adapter. Phone recognizes ethernet, and other connected usb devices. For this I need an type-a -type c otg adapter too.

edit: not sure about stock rom, but on los since beginning it was working for me.
[General Questions and Answers] John Mugen:
Hi! Recently I updated to Stock ZUI 11.5.111 ST from this posthttps://xdaforums.com/z5-pro-gt/lenovo-z5-pro-no-gt-qa-guides-development/lenovo-z5s-update-to-zui-11-5-android-10-t4111935 and Works Flawlessly :fingers-crossed: (Except Whatsapp Notifications :eek:)

But i cannot ¨Disable¨ or Change the ZUI Lockscreen by defect :/

I Tried ¨Hi Lock¨ and Works Good but... When I press the Lock Button on the Phone it Still show the Lockscreen by defect (Without password and Fingerprints), and after unlock it (Just Swipe up) it Show the Lock by ¨Hi Lock¨ :eek:

Sometimes Work like it has to be, But Other Times the Lockscreen by defect cames back and it start the same problem again :(

Theres a way to totally disable it? In my Old Phone When I press the lock button it shows the main screen without another screen...
[General Questions and Answers] Peppo420:
Hello!

I hope this is the right sub for stuff like this, i looked but didnt find any better.

When i was talking with a friend about me planning to buy a new phone he told me about CFW and xda.

Now, with all the new possibilities for android that i learned about, old criteria for choosing a phone, like a good interface or nice apps seem redundant.

Is there any stuff i should specifically look for in a new phone if i plan to flash it?

Greetings

Joe
[General Questions and Answers] Droidriven:
If you want to flash the device with a custom recovery and custom ROMs, all you really need to focus on is a device that has an unlocked bootloader or a bootloader that can be unlocked with a known method for that device.

Make sure the device has custom development(root, custom recovery, custom.ROMs, etc..) available for it here and make sure the device is compatible with your network service provider.

If you can make a choice that fits these criteria, you should have no issues.
[Samsung Galaxy Tab A series Questions & Answers] Aguamandan:
Alright, I've been running LineageOS 17.1 on my T510 for a few weeks now. It's been fun and all, but the cons outweigh the pros, so I wanna return my tablet back to as close to stock as possible. Don't care about data or root loss. Can anyone point me to a good guide for the process? Thanks in advance.
[Touch CDMA General] robstak:
ok here's the quick: let sprint custs run (i know). relocked and reflashed original verizon ROM dump. manually replaced epst settings and DMU reset. everything works now cept EVDO because:

my HDR AN AUTH User ID: is hexESN@hcm.sprint.com!!! (wow those custos really f you in the end)

when i go to edit it says "write "HDR AN AUTH User ID" error"

I know no EVDO because of failed auth is a common problem, but i think my problem is a bit unique in that i know it needs to be my#@vzw3g.com, but it just wont let me change it. any ideas???

are you not allowed to edit your own auth? can verizon (called 3 times, all morons)? what about qpst or qxdm or whatever?

thanks ahead of time,

-karl
[Touch CDMA General] robstak:
**bump**

anyone?
[Touch CDMA General] njakobs:
You can use EPST to change your HRD ID etc.

You will need to know what your MSL code is though.

If you just use the view option of EPST it will not show you the security settings.

If you look at this thread http://forum.ppcgeeks.com/showthread.php?t=25226

It has all the info you need to find out your MSL code etc. I am sure that info is elsewhere on this site to. That is just the place I found it all.

Cheers
[Touch CDMA General] robstak:
my msl is 000000 i can get into edit the settings in epst, it just gives me an error when i try to change my hdr an auth! its so weird!

when i access my settings in qpst i get a write error when i try to change it!

i dont get what gives! hellppp!!

:/

-karl