Since Nougat update I can't catch Pokemon anymore

LeoLe · November 17, 2018, 11:58am

Dear Fairphhone community,
I know it’s a minor problem compared to other topics, but I wanted to share it anyways. Perhaps someone else got the same problem.

Since the update to Android Nougat Pokemon Go crashes everytime I attempt to catch a Pokemon. I already deinstalled the game twice and tested it in every kind of situation (like with WIFI on or while charging) - nothing solved the matter. As soon as I tap on one of those cute monsters the game shuts down. I also checked the authorization I of the app, It got every authorization it needs.

So I started to believe it has to do with the Android 7 update. But it is weird - I didn’t any other problem with the new update. It’s quiet the opposite - I feel like most apps are operating better now.

If anyone has got a hint what I could do to solve the problem - I’d appreciate it.

Best
Leo

oli.sax · November 17, 2018, 1:21pm

I don’t have this issue (running PkmnGo on Lineage15), but here are some hints:
Try to desactivate AR or to enable camera permission for this app

LeoLe · November 17, 2018, 4:52pm

Thanks for the answer oli.sax.
I didn’t expect to find a fellow PkmnGo Player so fast
And thanks for the shared links to those reddit support pages, I tried them out.

I checked the camera permissions again, they were on. Now I tried some variations with turning permissions off and on and deinstalling it and deleting the cache. Sadly the problem consists.

I don’t know if it’s the AR modes fault that the game crashes. It always shuts down before the catching screen appears, so I can’t see if the AR setting is on. And the AR+ setting doesn’t exist for Android 7 on FP2, so I can’t turn that off.

Perhaps I should install Lineage15 and try it on that OS.

StefanReimers · November 17, 2018, 11:27pm

Same problem here. Also googled the problem, but the old solutions don’t help.
Just that it is not only a minor problem for me…

JeroenH · November 18, 2018, 4:12pm

That’s a feature, not a bug

In all seriousness, have you tried to delete the program’s cache at App Info?

LeoLe · November 18, 2018, 4:45pm

Thanks for the hint.

I deleted the programm’s cache, sadly it didn’t help.
But after deinstalling it several times - I would have been surprised if it would have helped.

flowsn · November 18, 2018, 6:32pm

Hi there,
I have the same problem, tried everything already described above. Re-installed it a couple of times, played around with the camera options and authorizations, even did a hard reset - nothing helped. It’s pretty annoying and I actually don’t want to install Lineage15 (but if some confirms pogo will work again with that, I might consider it). I hope there will be a fix soon (before my ex-raid on Thursday would be great). So if anyone comes up with a solution, I’d be happy to read about that over here
Cheers!

FPuser1 · November 18, 2018, 7:06pm

I am having the exact same issue here since updating to Nougat. I also tried enabling/disabling permissions and reinstalling the software, but the problem persists.

Stryker · November 19, 2018, 8:17am

I have the same problem. And already done everything, cache deleted, uninstalled and reinstalled, but has brought nothing.

oli.sax · November 19, 2018, 8:21am

I have a simple idea to test if this problem is camera-related or not: could you try adding a new friend with the QR-code camera reading? Me for example

Otherwise, what we can do is look in the log (activate adb in the developper settings, connect to computer and type ‘adb logcat’ in a terminal) to search a specific message explaining the crash…

StefanReimers · November 19, 2018, 8:42am

I just used my camera to scan your QR code. This worked (and you should now have a new friend request on Pokemon GO).
Trying to catch a pokemon still causes the app to crash.

I’m very willing to work with you to research the matter. I’m not very familiar with developer settings though, could you guide me through?

LeoLe · November 19, 2018, 8:52am

Good Idea oli.sax, I added you as a friend too now.
So I guess it is not camera related.

How do I activate ADB in the developper settings?
I can’t find it (probably because my phones language is German).

oli.sax · November 19, 2018, 8:53am

There is a wiki here : ✏ How to gather logs

In a summary:

[on FP2] you need to go to settings -> developer settings and enable USB debugging. (If you can’t see the menu for developer settings, you need to go to settings -> about phone and tap a few times on the build number.)
[on your computer] Install the drivers and Android Debug Bridge. For windows follow this tutorial, for linux sudo apt install android-tools-adb
[once your FP2 is connected to your computer] Check that the computer detect the device: adb devices; then open the log: adb logcat

StefanReimers · November 19, 2018, 9:03am

That is some hefty installation…
Not sure I’m up to scratch. Are you working on it, LeoLe?

LeoLe · November 19, 2018, 9:23am

I am a beginner too

I activated the USB debugging.
Installed Android File Transfer (because my mac didn’t connect to my phone)
and Homebrew because I’ve found this tutorial: installing-adb-on-macos

But now I don’t know how to go on. if I type in " adb devices" into the terminal I get the message “command not found”

StefanReimers · November 19, 2018, 9:35am

Well, I might wait to get back to Germany and have someone read out the phone there rather than ruining my computer…
Anyway, I also opened a ticket with the support, the replied but no solution yet: “Your request 267903 about “Pokemon GO not working properly on Fairphone 2 after Android update” has been updated.” The link in the mail returns a “page does not exist”, though…

oli.sax · November 19, 2018, 10:21am

Strange, if adb is installed it should find the adb command… Have you tried rebooting?

LeoLe · November 19, 2018, 11:24am

My fault, I skipped one step in the tutorial.
Now adb is sucessfully installed. And I tried “adb devices”.

I get this response and I don’t know what to do next:

List of devices attached
8cccf626 device

do I have to start " logcat" now? can I post a part of the logs (that I think that is relevant) here?

oli.sax · November 19, 2018, 1:06pm

That’s the perfect behaviour, it is installed perfectly
Now just type “adb logcat”, it’ll display all the log in the terminal, or “adb logcat > logFP2.txt” to export it in a text file.
Copy and paste just the lines corresponding to the time pokemon go has crashed…

LeoLe · November 19, 2018, 1:30pm

I identified the crash, but I don’t know how much of the log is relevant:

11-19 13:03:53.389 1815 3473 W GnssLocationProvider: Invalid size of GpsSvStatus found: 0.
11-19 13:03:53.650 29560 29576 E libEGL : call to OpenGL ES API with no current context (logged once per thread)
11-19 13:03:53.654 29560 29576 E CRASH : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
11-19 13:03:53.654 29560 29576 E CRASH : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-19 13:03:53.655 29560 29576 E CRASH : Build fingerprint: ‘Fairphone/FP2/FP2:7.1.2/18.09.2/gms-4a5ca353:user/release-keys’
11-19 13:03:53.655 29560 29576 E CRASH : Revision: ‘0’
11-19 13:03:53.772 1815 4514 D GnssStatusListenerHelper: Remote Listener died: android.location.IGnssStatusListener$Stub$Proxy@c21cf2d
11-19 13:03:53.772 1815 9749 I WindowManager: WIN DEATH: Window{1531c62 u0 SurfaceView - com.nianticlabs.pokemongo/com.nianticproject.holoholo.libholoholo.unity.UnityMainActivity}
11-19 13:03:53.776 1815 4524 I ActivityManager: Process com.nianticlabs.pokemongo (pid 29560) has died
11-19 13:03:53.776 1815 3073 W InputDispatcher: channel ‘8f2c27e com.nianticlabs.pokemongo/com.nianticproject.holoholo.libholoholo.unity.UnityMainActivity (server)’ ~ Consumer closed input channel or an error occurred. events=0x9
11-19 13:03:53.776 1815 4524 D ActivityManager: cleanUpApplicationRecord – 29560
11-19 13:03:53.776 1815 3073 E InputDispatcher: channel ‘8f2c27e com.nianticlabs.pokemongo/com.nianticproject.holoholo.libholoholo.unity.UnityMainActivity (server)’ ~ Channel is unrecoverably broken and will be disposed!
11-19 13:03:53.776 1815 3293 I GnssLocationProvider: WakeLock acquired by sendMessage(3, 0, com.android.server.location.GnssLocationProvider$GpsRequest@8d521f3)
11-19 13:03:53.780 1815 1831 I GnssLocationProvider: WakeLock released by handleMessage(3, 0, com.android.server.location.GnssLocationProvider$GpsRequest@8d521f3)
11-19 13:03:53.780 29187 29187 D BackgroundService: stopping notification
11-19 13:03:53.783 1815 4524 W ActivityManager: Scheduling restart of crashed service com.nianticlabs.pokemongo/com.upsight.android.analytics.internal.DispatcherService in 1000ms
11-19 13:03:53.784 1815 4524 W ActivityManager: Force removing ActivityRecord{dbc3782 u0 com.nianticlabs.pokemongo/com.nianticproject.holoholo.libholoholo.unity.UnityMainActivity t285}: app died, no saved state
11-19 13:03:53.804 273 273 W SurfaceFlinger: couldn’t log to binary event log: overflow.
11-19 13:03:53.805 1815 22863 I WindowManager: WIN DEATH: Window{8f2c27e u0 com.nianticlabs.pokemongo/com.nianticproject.holoholo.libholoholo.unity.UnityMainActivity}
11-19 13:03:53.806 1815 22863 W InputDispatcher: Attempted to unregister already unregistered input channel ‘8f2c27e com.nianticlabs.pokemongo/com.nianticproject.holoholo.libholoholo.unity.UnityMainActivity (server)’
11-19 13:03:53.815 273 273 W SurfaceFlinger: couldn’t log to binary event log: overflow.
11-19 13:03:53.816 1815 4524 D ActivityTrigger: activityResumeTrigger: The activity in ApplicationInfo{ed5f821 com.fairphone.fplauncher3} is now in focus and seems to be in full-screen mode
11-19 13:03:53.816 1815 4524 E ActivityTrigger: activityResumeTrigger: not whiteListedcom.fairphone.fplauncher3/com.fairphone.fplauncher3.FairphoneLauncher/10005
11-19 13:03:53.820 284 284 I Zygote : Process 29560 exited due to signal (11)
11-19 13:03:53.828 29187 29187 D BackgroundService: BackgroundService onDestroy PROCESS_LOCAL_VALUE = 9899031
11-19 13:03:53.828 1815 22865 I GnssLocationProvider: WakeLock acquired by sendMessage(3, 0, com.android.server.location.GnssLocationProvider$GpsRequest@809aeb0)
11-19 13:03:53.889 1815 1831 I GnssLocationProvider: WakeLock released by handleMessage(3, 0, com.android.server.location.GnssLocationProvider$GpsRequest@809aeb0)

shortly after that crash I tried it again - so it would be easier to identify in the logs

11-19 13:03:13.169 28749 28765 E libEGL : call to OpenGL ES API with no current context (logged once per thread)
11-19 13:03:13.188 28749 28765 E CRASH : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
11-19 13:03:13.188 28749 28765 E CRASH : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-19 13:03:13.188 28749 28765 E CRASH : Build fingerprint: ‘Fairphone/FP2/FP2:7.1.2/18.09.2/gms-4a5ca353:user/release-keys’
11-19 13:03:13.188 28749 28765 E CRASH : Revision: ‘0’