yashsingh1/xdaforums huggingface dataset:
[Magisk] fOmey:
I'm curious to know if this is happening to users who are not rooted... I've only been aware of this issue for 5 minutes so excuse my ignorance..

EDIT: Look's like it is happening to users who are not rooted... So why exactly do we chalk this down to being a issue with magisk ?

I think were not passing safety net intermittently because of the lag introduced by the crashes ?

EDIT 2: Just updated via the playstore (0.95.3), cleared data & cache and I don't seem to be crashing anymore ?

EDIT 3: No crashes, device incompatible popped up completely randomly tho... hmm I was GPS spoofing & using calcy IV at the time tho.

EDIT 4: Had another session, begun crashing once again. Seems like clearing data & cache prevented any crashes for that initial session, may just be a coincidence tho.
[Magisk] nguyen4514:
I think the problem could be linked to magisk.

On most of my spoofing devices, I don't have magisk installed. I used TWRP to either convert a joystick into a system app or install smali patcher. These devices have the new 0.95.3 APK installed and no crashes or compatibility errors when playing the game.

On my magisk device, the game constantly crashes. Doesn't matter if I have spoofing apps installed. After repeated attempts to open the game, I get lucky and the game loads. During gameplay I will get a random compatibility error. Again, this problem is not present on my devices that do not have magisk installed.
[Magisk] shoey63:
Not just Magisk. SuperSU + old SUHide + systemless xposed + rootswitch as well.

Edit: Actually, that configuration seems to work lol.

Edit 2: Nope. Gets incompatible device message with latest Pogo update.
[Magisk] EViollet:
It isn't surprising actually because suhide uses the same per-process mechanism to hide SU as Magisk.

But it does give some indication as to what Pogo does in the background, which is really only focused on SU detection, and not Magisk itself. Which is quite good news after all.

So we're back to needing a MagiskHide global button to override the per-process detection.

Just hope that topjohnwu gets back before Niantic forces the new udate on us....

:fingers-crossed:
[Magisk] armeliiito:
I think Magisk and root are the issue. To bad that after uninstall root and Magisk, your Patcher stop working. Can we have an option to patch services.jar even if Magisk is not installed?
[Magisk] nguyen4514:
Yes. You can extract the services.jar file from the zip file generated by smali patcher. After extracting the services.jar file, you can paste it into the /system/framework folder. You can do all of this by using the file manager in TWRP.
[Magisk] HeNaFi:
Yes. I have 2 old devices with Suhide.55 and systemless xposed-v86.2 ND rootswitch 1.3.3.2. That work for more than a year until this update. On my daily driver I have magisk 16 and the same problem as everybody here.
[Magisk] osm0sis:
Does suhide-lite work still?
[Magisk] HeNaFi:
No idea. Bro. I tried that for the daily driver, it never worked so I got stuck with using magisk
[Magisk] SebaS-DG:
Is not magisk, ppl with out it is having the same problems.

Toons of ppl reported this, stop saying it is, or go and read.
[Magisk] Nataku90:
For all people getting "Incompatible Device" in lastest pokemongo versions - THIS IS NOT MAGISK - the new pogo versions are buggy as hell and as soon as it crashes the incompatible screen can appear - also on unrooted devices with stock android! It is niantic (pogo developers) fault so no need to eather blame magisk nor to ask for solutions. All you can do is to doqngrade to an older pogo version of 0.92.x wich doesnt have this bugs or wait for a newer version of pogo where they hopefully fixed this errors.
[Magisk] fOmey:
I'll test this theory, I'll uninstall magisk and see if I still crash / incompatible device.

EDIT: Nope, can't seem to uninstall magisk without bootlooping.. flashing the stock boot.img in the rom I'm using doesnt seem to solve the boot loop either.

No idea why it's boot looping, really can't be bothered with it either (at work).

If someone is keen: try uninstalling magisk. If your using a modified services.jar place that in /system/framework (delete the odex files also if your running a odexed rom)... see if you crash, or get spammed with device unsupported messages on the latest pokemon go update.
[Magisk] pileot:
I have four phones that were rooted with Magisk. Three of which were OnePlus 3's with ONLY POKEMON GO installed, and the few required apps (play store, for instance). All other non manditory apps (even Contacts, phone, clock, etc.) were disabled or uninstalled. Basically, next to nothing on these phones.

Download the 0.95.3 APK, get the error with magisk / root.

Delete the Magisk app, still getting errors / incompatable.

Reinstall magisk, remove root. No errors.

I used to get errors at least once an hour at best. I was playing ALL DAY LONG (8 hours today, 0.95.3 APK) with MULTIPLE relogs / restarts / account switching and NO ERRORS after removing Magisk.

My daily driver still has Magisk. It worked fine for maybe 45 minutes, then "device incompatible".

To those saying its not root - If you are getting errors with Magisk are you still getting errors WITHOUT magisk after removing root?

Its possible those claiming errors and not rooted either A) are unaware their phones are rooted / using a rooted rom, or B) are trying to hide that they use a rooted phone, for some reason.

I have done a LOT of personal testing. I've copied the TWRP backup to my three "Pokemon Go" phones so they are identical in every way, on one phone I remove root, no problems, on my other phones (running IDENTICAL INSTALLS) they get device incompatible messages. As soon as I remove root I no longer get those errors. Note I still have custom recovery, I still have USB debugging turned ON.

OP3 running OOS 5.0.1, Kernel 3.18.66-blu_spark-OOS-Oreo

I am 100% convinced that Pokemon Go is somehow detecting either Magisk or systemless Root. I dont know how but that is the only logical conclusion I can come up with after my own extensive testing.
[Magisk] iamelton:
a friend of mine is using Nexus 6 on Pure Nexus, rooted with Magisk 16.. and he has NOT experienced any error using latest 0.95.3..

i have read through this thread and related threads in reddit.. it seems like there is an exception to every possible theory..

thus im convinced that it might be a combination of hardware/software setups that caused the issue..
[Magisk] crhistianwolf:
la nueva actualización de Pokemon go . con magisk instalado no funciona . he desinstalado magisk y no ha funcionado. solo he logrado que el juego funcione instalando la rom stock limpia y desde 0.. ///

the new update of Pokemon go. with magisk installed does not work. I have uninstalled magisk and it has not worked. I have only managed to make the game work by installing the clean stock rom and from 0 ..
[Magisk] pileot:
How long has he played? My rooted phone worked for a solid 45 minutes at least. The erroring seems somewhat random, as far as I've seen nobodys pinned down whats triggering it.

What kernel / rom / process did he use to root his phone, and is it repeatable? Its possible he did something we havnt that is preventing him erroring, or its possible he has just been really lucky not getting errors and they are coming.
[Magisk] iamelton:
he played daily for a few hours.. the test started since yesterday and so far no error resulted..

the setup is Nexus 6 with Pure Nexus (latest version that he just downloaded, with stock rom kernel), and he flashed rom & magisk with latest twrp..

(be assured that he is a seasoned root user, so the likelihood of him doing something wrong during the process is very low.. and since this is his old phone used solely for this test, he installed the rom & magisk, and did not install any unnecessary apps..)
[Magisk] oTeMpLo:
Yes he played 91.2 wit magisk last version that works :)
[Magisk] pileot:
91.2 is not the problem

The problem is 0.95.3, which is going to be a forced update when the community event comes this weekend since it contains the new moveset for bulbasaur. Unless something dramatic comes before then, this is only a small wave of complaints compared to the tsunami once the update is forced in a couple days.

Its well known you can downgrade to 0.91.2 in order to continue using root but that "workaround" is not going to last very much longer.
[Magisk] justj0sh:
I spent a good 5 mins ticking every single option available under magisk hide but something seems to still be leaking root detection. I'll probably have to remove magisk because I don't want to risk missing the ex-raids in case they force the update early. As per earlier testers, I can confirm that a non-rooted device works with 0.95.3 easily.
[Magisk] Telperion:
Pokémon Go is accessing java.sun.misc.Unsafe.java for unknown purposes, any way to leverage that to have more robust root detection?
[Magisk] osm0sis:
I just did some tests with suhide-lite, and even with Pokemon GO itself specifically added to suhide-lite's hide list (SafetyNet is already on there by default) the game behaves in exactly the same ways as with MagiskHide: crashing at first-start, crashing before/after SafetyNet check, failing SafetyNet check and periodically passing.

The periodic passing continues to suggest it's a timing issue, and could be resolved by the root hiders by speeding up the hiding process, since other SafetyNet tests in other apps, including Android Pay, still pass with flying colors.
[Magisk] Telperion:
I had PoGo sitting open with a logcat running on the process. With device sitting there, it went to the not compatible screen. This is what was logged:

03-22 12:24:08.375 12107 12123 I Upsight-UnityPush: registration succeeded
03-22 12:24:21.231 12107 12123 I Unity : HandleAuthEvents: DeviceIncompatible
03-22 12:24:21.231 12107 12123 I Unity : UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[])
03-22 12:24:21.231 12107 12123 I Unity : UnityEngine.Logger:Log(LogType, Object)
03-22 12:24:21.231 12107 12123 I Unity : Niantic.Auth.AuthenticationService:HandleAuthEvents(AuthEvent)
03-22 12:24:21.231 12107 12123 I Unity : Niantic.Platform.Ditto.Auth.AuthManager:HandleEvent(InternalStateEvents)
03-22 12:24:21.231 12107 12123 I Unity : Niantic.Platform.Ditto.Auth.<ChannelAuthEventHandler>c__AnonStorey0:<>m__0()
03-22 12:24:21.231 12107 12123 I Unity : Niantic.Platform.Ditto.Tasks.AsyncTaskQueueImpl:ProcessOnMain(Double)
03-22 12:24:21.231 12107 12123 I Unity : Niantic.Platform.Ditto.Tasks.AsyncTaskQueue:Process(Int64)
03-22 12:24:21.231 12107 12123 I Unity : Niantic.Platform.Ditto.Plugin.DittoPlugin:Update()
03-22 12:24:21.231 12107 12123 I Unity :
03-22 12:24:21.231 12107 12123 I Unity : (Filename: ./artifacts/generated/Android/runtime/DebugBindings.gen.cpp Line: 51)
03-22 12:24:21.231 12107 12123 I Unity :
[Magisk] Haxorleet:
Talking about forced update...

Talking about forced update...

I just came back home after three hours farming outside, and I got a pop up message to upgrade my game from 0.92.x to the latest version...

---------- Post added at 07:24 PM ---------- Previous post was at 06:53 PM ----------

I play fair 95% of my time.

The last 5% is to snipe IV 100 Pokemon that I already have in my Pokedex and I don't even put them in gyms.

I don't even fly Gyms because I live a few meters away from one and only one gym is needed to get 50 Pokedollars.

I just collection Pokemon, change their movesets, put little stars on them when they are perfectly set up and let them be in my storage.

And I only play with the same 6 Pokemon team all the time.

I am level 40, i didn't finish my Pokedex yet because I take my time to enjoy the game with my friends outside.

Nothing makes me more happy than adding a new Pokemon by walking around.

Plus the only main reason I root my phone is to get rid of bloatwares.

I hate the fact of not fully controlling of what's installed on my phone.

Peace
[Magisk] 4thfloorcaveman:
Hiding the launcher and backgroundrunning apps (facebook, huawei services, google maps etc.) seemed to do the trick.

Much fewer crashes and I have yet to see an "unsupported" message.

Have to agree on the dirty temp though :laugh:
[Magisk] Telperion:
So far I've not had any 'not compatible' messages with this setup.
[Magisk] jan.skurski:
Care to explain what is in that screenshot / how can one recreate your setting?
[Magisk] Telperion:
Well immediately after posting that I got the message. :laugh: It's an app called Disable Service, I disabled Niantic's analytics services. It can't hurt.

In any event, get the game working, then run a backup in Titanium Backup. When you get the compatibility message, swipe Pogo closed, then restore data from TB. When you launch Pogo again you'll be able to play again. It's not a fix, but it works.
[Magisk] InTiime:
Solved, ty
[Magisk] pileot:
There are several "Service Disabler" apps that come up, which one do you use? Mind posting a screenshot of its icon, who makes it, or better yet a play store link? Thanks!
[Magisk] Telperion:
I've been using this one for years, hasn't been updated in ages but it doesn't need to be when it gets the job done.

https://play.google.com/store/apps/details?id=cn.wq.disableservice

Use it in conjunction with adding potential leaks to MagiskHide. Things like SystemUI, FusedLocation, etc. On one instance, pulling down the notification shade caused an instant 'not compatible message'.

The general idea is to add possible sources of leaks like app transitions, etc to your hide list, and block all the Pogo services you can while still having a working app. I make no guarantees that this won't trigger an anti-cheat mechanism, since I simply don't know what all they're looking at. Pogo communicates with the Play Store to validate IAP ability, so that's another possible leak.

logcat -b all | grep -e "niantic"

See what all else the app interacts with, and add those to MagiskHide also.
[Magisk] Flying Scotsman:
I haven't had much time to actually properly look into this, but would something like this module help lower the chances of that annoying "Device not compatible" message from appearing?

I realise Niantic probably won't be sniffing out prop files to check, and that these errors are just from a bad build (a very bad one in fact....) but it may at least extend the time before that stupid message pops up.
[Magisk] justj0sh:
What is this?
[Magisk] Kermit223:
After you transfer the services.jar or do you need to set any file permissions? Have you tried this? Is pogo still crashing?
[Magisk] hamonmaru:
Any far explain about this?
[Magisk] nguyen4514:
Didn't have to change permissions. Backup your original services.jar file before you replace it with the modified version.

None of my devices crashed with the newest 0.95.3 update. All of my devices use custom ROMs. I only used TWRP to convert joysticks into system apps or install smali patcher. Running well on KitKat, lollipop, marshmallow, nougat, and Oreo.

I started using magisk again because my group members were reporting crashes with magisk. Noticed that my devices also crashed with magisk.
[Magisk] justj0sh:
Does removing magisk make the crashing go away? I'm about to hit the button to remove magisk
[Magisk] Kermit223:
Yes after removing magisk everything works perfect. I'm going to try using small patcher now and copy the patchedservices.jar over using twrp and see if that works.
[Magisk] the00guy:
It appears so, I uninstalled it and had the game load no problem just now. Will report back if this ceases to be the case. Luckily via the zips it's so easy to reinstall magisk, I don't mind doing that as a stop gap solution for the time being.
[Magisk] nguyen4514:
There are plenty of people in this forum that don't think magisk is the problem.

Based on what I've seen from my group members and my own devices, I do think magisk may be the issue. As I said in my last post, my devices all run custom ROMs. Magisk was not installed on them. I only installed magisk to test what my group members are talking about. The moment I installed magisk, I saw the crashes they were talking about.
[Magisk] justj0sh:
I've gathered enough info from the users in this forum and my own testing to believe that magisk is the problem. Or rather magisk is leaking the root detection somehow through one of the background services. My question was more about does removing magisk truly remove all traces because I'd totally do that for the time being. Can't give up the ex raids coming up soon.

Also, I'm thinking niantic isn't crashing the game on purpose but probably calls a bad function when magisk is detected and that's crashing the java thread.
[Magisk] hamonmaru:
After uninstalled magisk all thing about pogo with last update seem going back to normal.

Before with magisk the game always crashes.

But now all magisk moduls are gone though all the modules I installed are very much needed.

Maybe magisk dev would give their time to fix this issue soon.

:)
[Magisk] MoHuToP:
N910f - my daily driver. RR 5.8.5, latest beta Magisk. All problem persist, BUT when I've not used recent apps switch, the game is stable at 100%

G900f - test device. Latest stable Magisk. Latest beta Lineage 14.1. Impossible to play with this device.

The interesting part....

Nokia 3 - test device, stock firmware, rooted with latest beta. NO problems with crashes. Few times I've got incompatible version during the startup of the game. After all, is stable for playing. My wife device, she plays alot.

Lenovo a1000, - test device, custom ROM, tweaked custom kernel, Android 5.0 rooted with latest beta. Hardcore sniping. NO problems during the play time. Stable as rock.

i9195 - cm 13, rooted with latest beta Magisk, custom kernel, hardcore spoofing, NO problems at all. Stable.

And the funny part - i9300, my work daily driver,, slimrom, boeffla latest beta, overclocked, overvoltage, latest beta Magisk, hard tweaked kernel, NO problems at all.

Lenovo P1 - test device - latest stable Magisk, no crashes and errors.

HTC M7, slimroms,, rooted with 15,3 beta Magisk - today I'll test and report.
[Magisk] teddy0209:
No problem playing here with latest magisk... It's probably setup dependent...

MHide on, Manager hidden, some props, xposed off...
[Magisk] Didgeridoohan:
Very unlikely...

The idea by [MENTION=3694505]Telperion[/MENTION] to disable specific services for the app is absolutely brilliant though! Give that a go.
[Magisk] justj0sh:
I have reservations about this. I have followed the RE community since the start and they have not been able to figure out how Niantic is detecting the reversed API. You have no idea if disabling some of the processes will flag you as using the reversed API because some information doesn't get sent back.
[Magisk] pileot:
My issue with disabling services is it prevents the gotcha / plus to connect. I also suspect that Naintec can detect at least some disabled services and that has been the cause of some bans / warnings in the past.
[Magisk] Nataku90:
Pokemongo can read installed packagenames thats how they lockout people with spoofingapps unless those apps got repacked with a random packagename.

Magisk runs under the packagename "com.topjohnwu.magisk" and niantic uses androids inbuilt feature to readout installed packagenames. Maybe they simply added the packagename of magiskmanager to their blacklist like alot spoofingapps are? :)
[Magisk] pileot:
You can repackage Magisk with a random name, it does not fix the problem.
[Magisk] Nataku90:
Ah i had no time to try that yet but thanks! Too bad would have been and easy and fast fix ^___^
[Magisk] fOmey:
Curiosity got the best of me, I decided to uninstall magisk... used my smalipatcher to generate a patched jar to allow mock locations and manually installed it.

Started spoofing my location and using calcyIV... played for about 10 minutes no crashes or any "device not compatible" pop up's... pretty safe to say they are detecting it's related to magisk..
[Magisk] Haxorleet:
My game worked all night long.

Hi back,

Last night, I decided to try something with my game after updating it with the forced update.

I kept my game running starting at 9 pm (rooted Galaxy S6 with magisk 16).

I wanted to see how long the game would last until I get the "unsupported device" message or any crash.

I woke up at 8.30 am this morning and the game was still running + a 10k egg hatched.

I don't get it... it looks like its random.
[Magisk] Kermit223:
Can you let me know how you added your services.jar without magisk? I patched my servicess.jar and copyed it over using TWRP file manager but when I opened my GPS joystick app but it was still asking me to set mock locations then pokemon go was saying can not find location.
[Magisk] oTeMpLo:
No.. its timing issue with magiskhide.. switching tasks

So with no interaction i am not with resoult..
[Magisk] InsaneNutter:
I've had this issue since the 16th now, however have only just found this thread.

After a lot of trial and error this is what i've been doing for the last week to successfully keep playing with the latest 0.95.3 version of Pokemon Go.

Initial Setup:

Force Pokemon Go to stop, then clear the apps data / cache.

Go to Settings > Apps > Pokemon Go and manually grant the app permissions for everything it wants. On my OnePlus One Pokemon Go seems to crash every time it requests a permission for the first time, such as the camera for example.

Now you have a clean copy of Pokemon Go, sign in and you should be able get in game without any crashes.

Once Pokemon Go had signed in, swipe the app to close it.

Immediately make a backup of the app + data with Titanium Backup.

You now have a working backup of Pokemon Go where you are signed in, with all the app permissions granted.

Each time you want to play Pokemon Go:

Restore the working backup with Titanium Backup, then Pokemon Go will load and sign in first time without issue.

Have fun.

My Experience:

I've found by restoring my working backup I can play for as long as I want, with no crashes, providing i dont do anything else on my phone.

When playing you can't switch out of Pokemon Go to another app such as Whatsapp or take a phone call for example. Pokemon Go has to be the running app in the foreground at all times. You can't turn the screen off or anything, the phone need to remain on with Pokemon Go running in the foreground as the active app.

If you switch to any other app Pokemon Go will either crash when you switch back to it, or tell you that you are using an unsupported device.

I have found I can quick reply to WhatsApp messages from the notification try as Pokemon Go is still the running app in the foreground when doing that.

Yesterday I restored my backup, loaded the game and played for an hour with no issue. That is the most i've played as i'm more of a casual player. However I will be playing for the 3 hour community event this Sunday.

I do think it's a real shame Niantic try to punish people for taking security more seriously and using custom roms with the latest security patches / later versions of Android. Pokemon Go is far stricter than any banking app in my experience. Without a custom rom i'd be on Android 6.0.1 with the September 2016 security patches...

Phone: OnePlus One

Android: 7.1.2 (Linage OS 14.1)

Security Patches: February 2018

Rom: Sultanxda's Unofficial LineageOS 14.1 with 3.4.0 kernel

Something else I have noticed is if you load Magisk Manager then Pokemon Go the game will also usually load up and sign in ok too.
[Magisk] justj0sh:
The problem only happens when you switch tasks and root detection leaks through. I'm very interested to know if a faster phone actually fixes this issue
[Magisk] oTeMpLo:
It makes it worse... It
[Magisk] justj0sh:
What makes it worse is being unable to remove Magisk :D
[Magisk] hamonmaru:
Agree.

Once switch tasks opened and move to other tasks then back to pogo it will be crashed all the time.

Playing pogo and gps app simultaneously and alternately.

Make me have to uninstall magisk but no modules anymore.

Like have very2 standard phone.