| Age | Commit message (Collapse) | Author |
|
25% of the screen isn't necessarily wide enough on phones,
especially not in portrait mode.
|
|
|
|
Removing the menu for a split second before showing the transition
back to the main activity looks janky.
|
|
Android TV devices aren't the only devices without touchscreens.
Regarding MotionAlertDialog, I could've replaced the leanback
check with a touchscreen check instead of just removing it,
but I thought there was no reason to prevent people with
touchscreens from doing a long back press if they want to.
|
|
https://bugs.dolphin-emu.org/issues/12029
We currently have one way of opening the menu on touch screen
devices (swiping down from the top of the screen to bring up the
action bar and selecting the menu in the action bar), and another
way of opening the menu on Android TV (pressing Back). However,
some devices that claim to support touch (or don't support
leanback? Dolphin currently conflates the two) don't actually let
you swipe down from the top of the screen in the way that Dolphin
expects, notably Chromebooks. There are also some phones where you
can swipe down from the top of the screen but this for some reason
doesn't lead to the action bar becoming visible, though we are
getting less reports about this nowadays than in the past.
This change makes us use the Back method on all devices,
since it should work on all devices with no significant drawbacks.
Unfortunately, we not only have two different ways of triggering
the menu but actually two entirely different menus, with the
non-touch menu not implementing options that only are revelant
when using a touch screen. A later commit will add the missing
features to the menu that we now use on all devices.
|
|
Android: Optimize imports
|
|
|
|
|
|
|
|
|
|
Android: Optional AfterDirectoryInitializationRunner failure message
|
|
Android: Make FilePicker act like a normal setting
|
|
Android: Fix saving Horizonal Wii Remote overlay A/B/1/2 positions
|
|
The reason why the finish() call was added no longer exists.
(Also, there was never a duplicate SettingsActivity as far as
I can tell, only a duplicate SettingsFragment.)
|
|
classes
This way we don't have to hardcode any keys inside the classes.
|
|
Fixes https://bugs.dolphin-emu.org/issues/12096.
|
|
Replaces the inflexible INI functions in NativeLibrary.
|
|
This centralizes the code for showing the write_permission_needed
and external_storage_not_mounted toasts.
|
|
Android: Minor cleanup
|
|
Android: Better GCAdapter scanning thread management
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Android: Fix defaults for WiimoteContinuousScanning/EnableSpeaker
|
|
|
|
The default values need to match the default values defined in C++.
|
|
Long sequences of JNI calls are both hard to read and slow.
|
|
Android: Fix SettingsActivity lifecycle management
|
|
Android: Remove some static variables from SettingsAdapter
|
|
Fixes the behavior where the settings activity would go back to
the top-level menu after switching to a different app and back.
|
|
Just for maintainability. This is a shorter and more standard
solution compared to our current one where the Fragment
persists the Settings and passes it to the Activity.
|
|
All of these have non-static equivalents (mView and mClickedItem).
|
|
Fixes https://bugs.dolphin-emu.org/issues/10815
|
|
Android: Clear game profiles and GameSettings
|
|
Android: Settings and Emulation activities skip (Tv)MainActivity library rescan
|
|
Android: Add Log Configuration to UI
|
|
Android: Add Pause / Unpause Emulation Toggle
|
|
|
|
That a device doesn't have a touchscreen doesn't necessarily mean
that it doesn't support rumble (though it is usually the case).
setPhoneVibrator already contains a check for whether the device
supports rumble, so we can simply remove the touchscreen check.
|
|
When using the combination of Android 11 and HDMI 2.1,
this will send a signal to the TV suggesting it to switch to
a low latency mode ("game mode").
|
|
|
|
|
|
|
|
|
|
|
|
Android: Use correct encoding when converting strings
|
|
Android: Increase targetSdkVersion to 29
|