Samsung Note 3 version 4.4.4 null pointer in ViewRootImpl.setMultiWindowScale

I have a report from a user with Samsung Note 3 and Android 4.4.4. Here falls out:

SM-N900P 4.4.4 19

    at android.view.ViewRootImpl.setMultiWindowScale(
    at android.view.WindowManagerGlobal.setMultiWindowScale(
    at android.view.View.dispatchAttachedToWindow(
    at android.view.ViewGroup.dispatchAttachedToWindow(
    at android.view.ViewRootImpl.performTraversals(
    at android.view.ViewRootImpl.doTraversal(
    at android.view.ViewRootImpl$
    at android.view.Choreographer$
    at android.view.Choreographer.doCallbacks(
    at android.view.Choreographer.doFrame(
    at android.view.Choreographer$
    at android.os.Handler.handleCallback(
    at android.os.Handler.dispatchMessage(
    at android.os.Looper.loop(
    at java.lang.reflect.Method.invokeNative(Native Method)
    at java.lang.reflect.Method.invoke(
    at dalvik.system.NativeStart.main(Native Method)


It is not in my code and I cannot reproduce it in the emulator as I cannot create an AVD with 4.4.4. With AVD 4.4.2 it works. I tried a physical phone in a store / store with version 4.4.2 and it works. However, I cannot get version 4.4.4.

  • How can I create and AVD with 4.4.4?
  • Why doesn't Google provide 4.4.4 AVD?
  • Does anyone know how to resolve the dump?
  • I can't even find line 7992 and setMultiWindowScale method in AOSP?



source to share

1 answer

How can I create and AVD with 4.4.4?

Genymotion lets you emulate a Samsung Note 3 running 4.4.4.

It has plugin support for Eclipse and Android Studio, follow instructions here to install.

enter image description here

Why doesn't Google provide 4.4.4 AVD?

I don't know why not AVDs, but they provide binaries for 4.4.4 here , if you have access to a Nexus device you can double check / confirm that the problem is only Samsung related.

Does anyone know how to resolve the dump?

The lazy stack trace looks like an exception was thrown after your application was pinned to a multiple window and the view was scaled, or at least scaled if that NPE hadn't been thrown. Check your manifest settings with this walkthrough for multi-window support, check max and min sizes. If the emulator is not working and if you are unable to reproduce the exception, then as a last resort somehow contact that user and report them to reproduce the problem / test your solution and iterate until you fix it. Good luck!

I can't even find line 7992 and setMultiWindowScale method in AOSP?

It looks like this is very similar to Samsung's specific implementation of the android.view.ViewRootImpl class to support multiple windows and other Samsung stuff, I doubt you can find the actual source code if Samsung hasn't posted anything.



All Articles