The game does not appear to work within the Android N environment on my 5x. I gave it a quick check and am reverting back to M now.
Google released the first ‘stable’ beta of Android N today at Google I/O. As Google has now blessed this preview as solid enough for primary devices, I would expect usage to jump. MPQ crashes on launch on this build of Android.
I just put in a ticket, but figured I would bring it up for visibility on the forums. It looks like MPQ is crashing when launching it on the new Android N Beta (https://www.google.com/android/beta)
Any news on adding support for Android N? The dev preview has been out for a few months, and I expect an uptick in usage as the beta rolls out to people that enroll.
Just FYI to anyone who may install the new Android M. Android M is pretty cool… but MPQ crashes on startup.. it.. very much does not work.. so.. be careful.
I think you mean Android N? I made a post about it here as well: https://forums.505go.com/discussion/44484
Put in a support ticket too. Hopefully after the initial canned response I can make some progress with them!
https://www.reddit.com/r/MarvelPuzzleQu … v_preview/ has commentary from a red name.
I just learned this the hard way.
Hey thanks much for the head’s up → I was gonna check out the beta on my Nexus phone, but now I think I will hold off cause, ya know, I just can’t get enough Crit Boost awarding PVE action…
Today I learned that Android beta users are unable to search for existing threads before starting a new one.
Merged four threads.
I tried to be quick about it and post it prominently.
According to the comments there, it should be supported in R102. However, I would not count on that until a red name says so here, on the official forums.
Until then, it sounds like this is across the board, so don’t install the beta yet!
As always, I am not speaking for D3 or Demiurge.
I’m torn between wiping my phone in order to downgrade and just playing less for the next few weeks on my tablet. I think this is probably what will happen.
Umm, the person that posted that is Demiurge_Kabir so I would count that as a red weighing in.
It’s Reddit, not an official channel, so I figure it’s redpill trolls until proven otherwise.
Android N is coming soon and right now it is in beta. When I upgrade my phone to the preview, MPQ Crashes on launch. This happened last time Android upgraded to Marshmallow too, please fix this before N is launched officially! The preview is available to try now, and here is a stack trace for you guys as well:
06-01 12:43:30.070 935 12842 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.d3p.mpq/.LoadNativeLibrariesActivity (has extras)} from uid 10029 on display 0
06-01 12:43:30.084 4505 4518 W SearchService: Abort, client detached.
06-01 12:43:30.090 935 948 E ActivityManager: applyOptionsLocked: Unknown animationType=0
06-01 12:43:30.106 935 948 I ActivityManager: Start proc 12960:com.d3p.mpq/u0a92 for activity com.d3p.mpq/.LoadNativeLibrariesActivity
06-01 12:43:30.109 935 3882 I ActivityManager: Killing 11517:com.google.android.apps.youtube.gaming:screencast/u0a138 (adj 906): empty #17
06-01 12:43:30.122 935 4165 I ActivityManager: Exiting empty application process com.d3p.mpq (null)
06-01 12:43:30.233 4481 4592 W NotifCollectorService: SecurityException accessing existing notifications, scheduling retry
06-01 12:43:30.249 12960 12977 D FiksuTracking: ForegroundTester thread started, process: 12960
06-01 12:43:30.251 12960 12960 E FiksuTracking: THE FIKSU INSTALL TRACKING CODE ISN'T INSTALLED CORRECTLY!
06-01 12:43:30.251 12960 12960 E FiksuTracking: Unexpected receiver: com.appsflyer.MultipleInstallBroadcastReceiver
06-01 12:43:30.251 12960 12960 W System.err: com.fiksu.asotracking.FiksuIntegrationError: The Fiksu BroadcastReceiver must be installed as the only receiver for the INSTALL_REFERRER Intent in AndroidManifest.xml.
06-01 12:43:30.251 12960 12960 W System.err: at com.fiksu.asotracking.InstallTracking.checkForFiksuReceiver(InstallTracking.java:163)
06-01 12:43:30.251 12960 12960 W System.err: at com.fiksu.asotracking.FiksuTrackingManager.initialize(FiksuTrackingManager.java:24)
06-01 12:43:30.251 12960 12960 W System.err: at com.d3p.mpq.YorkAndroidApplication.onCreate(YorkAndroidApplication.java:144)
06-01 12:43:30.251 12960 12960 W System.err: at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1024)
06-01 12:43:30.251 12960 12960 W System.err: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5254)
06-01 12:43:30.251 12960 12960 W System.err: at android.app.ActivityThread.-wrap2(ActivityThread.java)
06-01 12:43:30.251 12960 12960 W System.err: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1508)
06-01 12:43:30.251 12960 12960 W System.err: at android.os.Handler.dispatchMessage(Handler.java:102)
06-01 12:43:30.251 12960 12960 W System.err: at android.os.Looper.loop(Looper.java:154)
06-01 12:43:30.251 12960 12960 W System.err: at android.app.ActivityThread.main(ActivityThread.java:5969)
06-01 12:43:30.251 12960 12960 W System.err: at java.lang.reflect.Method.invoke(Native Method)
06-01 12:43:30.251 12960 12960 W System.err: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:801)
06-01 12:43:30.251 12960 12960 W System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:691)
06-01 12:43:30.255 12960 12960 I Seoul : Checking requirements...
06-01 12:43:30.261 12960 12960 I Seoul : Google Play Services Ready...
06-01 12:43:30.265 935 1032 I WindowManager: Destroying surface Surface(name=Application Error: com.d3p.mpq) called by com.android.server.wm.WindowStateAnimator.destroySurface:1931 com.android.server.wm.WindowStateAnimator.destroySurfaceLocked:875 com.android.server.wm.WindowState.destroyOrSaveSurface:2015 com.android.server.wm.WindowSurfacePlacer.performSurfacePlacementInner:429 com.android.server.wm.WindowSurfacePlacer.performSurfacePlacementLoop:232 com.android.server.wm.WindowSurfacePlacer.performSurfacePlacement:180 com.android.server.wm.WindowManagerService$H.handleMessage:7978 android.os.Handler.dispatchMessage:102
06-01 12:43:30.266 935 1032 W AppOps : Finishing op nesting under-run: uid 1000 pkg android code 24 time=0 duration=0 nesting=0
06-01 12:43:30.283 12960 12960 W Activity: An activity without a UI must call finish() before onResume() completes
06-01 12:43:30.287 12960 12978 I Seoul : Starting York with: [Ad-ID 73f5d748-64de-49d8-af1d-99d0df8eafa7] [Android-ID 8e41858040a5173e] [Device-ID/IMEI: 867686020627129]
06-01 12:43:30.289 935 9118 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x32200000 cmp=com.d3p.mpq/.YorkAndroid (has extras)} from uid 10092 on display 0
06-01 12:43:30.314 935 4353 I ActivityManager: Start proc 12979:com.d3p.mpq/u0a92 for activity com.d3p.mpq/.YorkAndroid
06-01 12:43:30.431 12979 12995 D FiksuTracking: ForegroundTester thread started, process: 12979
06-01 12:43:30.433 12979 12979 E FiksuTracking: THE FIKSU INSTALL TRACKING CODE ISN'T INSTALLED CORRECTLY!
06-01 12:43:30.433 12979 12979 E FiksuTracking: Unexpected receiver: com.appsflyer.MultipleInstallBroadcastReceiver
06-01 12:43:30.434 12979 12979 W System.err: com.fiksu.asotracking.FiksuIntegrationError: The Fiksu BroadcastReceiver must be installed as the only receiver for the INSTALL_REFERRER Intent in AndroidManifest.xml.
06-01 12:43:30.434 12979 12979 W System.err: at com.fiksu.asotracking.InstallTracking.checkForFiksuReceiver(InstallTracking.java:163)
06-01 12:43:30.434 12979 12979 W System.err: at com.fiksu.asotracking.FiksuTrackingManager.initialize(FiksuTrackingManager.java:24)
06-01 12:43:30.434 12979 12979 W System.err: at com.d3p.mpq.YorkAndroidApplication.onCreate(YorkAndroidApplication.java:144)
06-01 12:43:30.434 12979 12979 W System.err: at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1024)
06-01 12:43:30.434 12979 12979 W System.err: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5254)
06-01 12:43:30.434 12979 12979 W System.err: at android.app.ActivityThread.-wrap2(ActivityThread.java)
06-01 12:43:30.434 12979 12979 W System.err: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1508)
06-01 12:43:30.434 12979 12979 W System.err: at android.os.Handler.dispatchMessage(Handler.java:102)
06-01 12:43:30.434 12979 12979 W System.err: at android.os.Looper.loop(Looper.java:154)
06-01 12:43:30.434 12979 12979 W System.err: at android.app.ActivityThread.main(ActivityThread.java:5969)
06-01 12:43:30.434 12979 12979 W System.err: at java.lang.reflect.Method.invoke(Native Method)
06-01 12:43:30.434 12979 12979 W System.err: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:801)
06-01 12:43:30.434 12979 12979 W System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:691)
06-01 12:43:30.473 12979 12979 D HockeyApp: Writing unhandled exception to: /data/user/0/com.d3p.mpq/files/f5253c36-ca03-4fb8-8b35-70735f38d6a3.faketrace
06-01 12:43:30.488 12979 12979 W PopupManager: You have not specified a View to use as content view for popups. Falling back to the Activity content view. Note that this may not work as expected in multi-screen environments
https://www.reddit.com/r/MarvelPuzzleQu … v_preview/
Should be fixed with next week’s release.
However, it’s not listed in the R102 release notes preview that was posted today: https://forums.505go.com/discussion/45122
I’d recommend holding off on upgrading to N until it is absolutely confirmed that the latest MPQ release supports it.
It’s still coming in R102. See https://www.reddit.com/r/MarvelPuzzleQu … ew/d3shte0
Can confirm that R102 makes MPQ playable on Android N.
Yup confirmed, fixed on Android N. Thanks guys!