Project

General

Profile

Actions

Emulator Issues #11944

closed

Android TV Crash on Launch

Added by webgeek1234 over 4 years ago. Updated about 4 years ago.

Status:
Fixed
Priority:
High
Assignee:
-
% Done:

0%

Operating system:
Android
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:
5.0-11827

Description

Game Name?

N/A

Game ID? (right click the game in the game list, Properties, Info tab)

N/A

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

N/A

What's the problem? Describe what went wrong.

Dolphin crashes immediately after launch

What steps will reproduce the problem?

Run dolphin on an Android TV device.

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

5.0-11422

Is the issue present in the latest stable version?

No, as Dolphin does not have a stable Android version. However, the latest Play Store release (5.0-11333) also has the issue.

If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)

Unknown

If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer

N/A

What are your PC specifications? (CPU, GPU, Operating System, more)

Nvidia Tegra devices running Lineage Android OS ATV.

  • foster_e_hdd (SHIELD Android TV Pro 2015) on Lineage 16.0 (Android P)
  • quill (Jetson TX2) on Lineage 17.1 (Android Q)

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

This was tested on atv builds of Lineage 16.0 where it did not run, and on tablet builds where it ran as expected. Also tested on Lineage 15.1 (Android O) atv and it also runs as expected. I don't not have an satv capable of running Dolphin running the stock os atm, but this should also be reproducible on the latest SHIELD Experience 8.x.x updates as they are Android P. I presume something in the leanback requirements changed to where this appcompat theme is now required.

Logcat entry of crash:

01-04 04:56:53.422 5883 5883 E AndroidRuntime: FATAL EXCEPTION: main
01-04 04:56:53.422 5883 5883 E AndroidRuntime: Process: org.dolphinemu.dolphinemu, PID: 5883
01-04 04:56:53.422 5883 5883 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{org.dolphinemu.dolphinemu/org.dolphinemu.dolphinemu.ui.main.TvMainActivity}: java.lang.IllegalStateException: You need to use a Theme.AppCompat theme (or descendant) with this activity.
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3270)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3409)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:83)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2016)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7356)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: Caused by: java.lang.IllegalStateException: You need to use a Theme.AppCompat theme (or descendant) with this activity.
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at androidx.appcompat.app.AppCompatDelegateImpl.createSubDecor(AppCompatDelegateImpl.java:696)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at androidx.appcompat.app.AppCompatDelegateImpl.ensureSubDecor(AppCompatDelegateImpl.java:659)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at androidx.appcompat.app.AppCompatDelegateImpl.setContentView(AppCompatDelegateImpl.java:552)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at androidx.appcompat.app.AppCompatDialog.setContentView(AppCompatDialog.java:95)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at androidx.appcompat.app.AlertController.installContent(AlertController.java:232)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at androidx.appcompat.app.AlertDialog.onCreate(AlertDialog.java:279)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at android.app.Dialog.dispatchOnCreate(Dialog.java:421)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at android.app.Dialog.show(Dialog.java:315)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at org.dolphinemu.dolphinemu.utils.Analytics.showMessage(Analytics.java:63)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at org.dolphinemu.dolphinemu.utils.Analytics.lambda$checkAnalyticsInit$0(Analytics.java:36)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at org.dolphinemu.dolphinemu.utils.-$$Lambda$Analytics$La-3fJkz4ZBITxYMCPMZYq8DAm0.run(Unknown Source:4)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at org.dolphinemu.dolphinemu.utils.AfterDirectoryInitializationRunner.run(AfterDirectoryInitializationRunner.java:48)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at org.dolphinemu.dolphinemu.utils.Analytics.checkAnalyticsInit(Analytics.java:35)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at org.dolphinemu.dolphinemu.utils.StartupHandler.HandleInit(StartupHandler.java:28)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at org.dolphinemu.dolphinemu.ui.main.TvMainActivity.onCreate(TvMainActivity.java:60)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:7824)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:7813)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1306)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3245)
01-04 04:56:53.422 5883 5883 E AndroidRuntime: ... 11 more

Actions #1

Updated by JosJuice over 4 years ago

  • Priority changed from Normal to High
  • Operating system Android added
  • Operating system deleted (N/A)

Thanks for the stack trace and details. I've seen reports of this a few times but wasn't sure what the cause was.

Actions #2

Updated by webgeek1234 about 4 years ago

Issue still present in 11824. I'd like to test dolphin on my Lineage 16.0 builds for the shield devices, mainly the desktop gl support. But still cannot run the software at all.

Actions #3

Updated by JosJuice about 4 years ago

Unfortunately, we don't exactly have many Android developers right now, and the only Android device that I have only goes up to Android O, so I can't reproduce the issue myself. I'm afraid it probably will take some time for this to get fixed.

Actions #4

Updated by JosJuice about 4 years ago

  • Status changed from New to Fixed
  • Fixed in set to 5.0-11827
Actions

Also available in: Atom PDF