Jolla phone 2026 AppSupport bluetoth passthrought

REPRODUCIBILITY: Always
OS VERSION: 5.2.016,5.2.0.17
HARDWARE: Jolla J2 2026
UI LANGUAGE: English
REGRESSION: Connected devices settings ( and Network and Internet) are not accessible in AppSuport as by selecting them settings window freezes and shortly after crashes and closes completely.

DESCRIPTION:

Connected devices settings ( and Network and Internet) are not accessible in AppSuport as by selecting them settings window freezes and shortly after crashes and closes completely.
The same behavior is observer if:
After resetting phone you install AppSupport on the first boot (with or without Appsuport bluetooth)
After resetting phone you do not install AppSupport, but install it from Jolla store (with or without Appsuport bluetooth)

PRECONDITIONS:

N/A

STEPS TO REPRODUCE:

  1. Go to AppSupport Android settings

  2. touch with finger “Connected devices” or “Network and Internet”

EXPECTED RESULT:

“Connected devices” settings open where I can pair or see nearby Bluetooth actual devices

ACTUAL RESULT:

AppSupport Android settings window briefly froze and immediately exits/closes

MODIFICATIONS:

None

ADDITIONAL INFORMATION:

Here is relevant part of the log and anr file (which is from todays identical crash - as original one is gone by reseting phone)

anr.targz (79.5 KB)

:
08-25 12:33:15.972 1396 1401 W ndroid.settings: Cleared Reference was only reachable from finalizer (only reported once)
08-25 12:33:15.983 1396 1403 W ndroid.settings: ApkAssets: Deleting an ApkAssets object ’ and /system/app/webview/webview.apk’ with 1 weak references
08-25 12:33:20.649 1396 1396 D ActivityEmbeddingUtils: isSettingsSplitSupported = false
08-25 12:33:20.649 1396 1396 W ElapsedTimeUtils: getElapsedTime: sSuwFinishedTimeStamp is null
08-25 12:33:20.654 257 886 W OptProp : Cannot read opt property android.window.PROPERTY_COMPAT_ALLOW_ORIENTATION_OVERRIDE
08-25 12:33:20.656 257 886 D APPSUPPORT: Not informing SurfaceFlinger of launch of 163 as they are the same task
08-25 12:33:20.656 257 886 E CellBroadcastUtils: getDefaultCellBroadcastReceiverPackageName: no package found
08-25 12:33:20.658 257 886 W OptProp : Cannot read opt property android.window.PROPERTY_COMPAT_ALLOW_MIN_ASPECT_RATIO_OVERRIDE
08-25 12:33:20.663 257 886 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cmp=com.android.settings/.SubSettings (has extras)} with LAUNCH_MULTIPLE from uid 1000 (BAL_ALLOW_VISIBLE_WINDOW) result code=0
08-25 12:33:20.668 1396 1396 W ElapsedTimeUtils: getElapsedTime: sSuwFinishedTimeStamp is null
08-25 12:33:20.674 257 336 W OptProp : Cannot read opt property android.window.PROPERTY_COMPAT_ALLOW_RESIZEABLE_ACTIVITY_OVERRIDES
08-25 12:33:20.684 136 136 I BpBinder: onLastStrongRef automatically unlinking death recipients:
08-25 12:33:20.690 1396 1396 D ActivityEmbeddingUtils: isSettingsSplitSupported = false
08-25 12:33:20.700 1396 1396 D SettingsActivity: Starting onCreate
08-25 12:33:20.710 1396 1396 D SettingsActivity: Starting to set activity title
08-25 12:33:20.710 1396 1396 D SettingsActivity: Done setting title
08-25 12:33:20.710 1396 1396 D SettingsActivity: Switching to fragment com.android.settings.connecteddevice.ConnectedDeviceDashboardFragment
08-25 12:33:20.710 1396 1396 D SubSettings: Launching fragment com.android.settings.connecteddevice.ConnectedDeviceDashboardFragment
08-25 12:33:20.712 1396 1396 D PrefCtrlListHelper: Could not find Context-only controller for pref: com.android.settings.slices.SlicePreferenceController
08-25 12:33:20.714 1396 1396 D LocalBluetoothProfileManager: LocalBluetoothProfileManager construction complete
08-25 12:33:20.715 1396 1396 D LocalBluetoothProfileManager: Adding local Hearing Aid profile
08-25 12:33:20.718 1396 1396 D PrefCtrlListHelper: Could not find Context-only controller for pref: com.android.settings.connecteddevice.AddDevicePreferenceController
08-25 12:33:20.718 1396 1396 D PrefCtrlListHelper: Could not find Context-only controller for pref: com.android.settings.connecteddevice.PreviouslyConnectedDevicePreferenceController
08-25 12:33:20.719 1396 1396 D PrefCtrlListHelper: Could not find Context-only controller for pref: com.android.settings.connecteddevice.fastpair.FastPairDevicePreferenceController
08-25 12:33:20.720 1396 1396 D PrefCtrlListHelper: Could not find Context-only controller for pref: com.android.settings.connecteddevice.AdvancedConnectedDeviceController
08-25 12:33:20.720 1396 1396 D PrefCtrlListHelper: Could not find Context-only controller for pref: com.android.settings.connecteddevice.DiscoverableFooterPreferenceController
08-25 12:33:20.725 1396 1396 I TetheringManager: registerTetheringEventCallback:com.android.settings
08-25 12:33:23.673 257 855 E TaskPersister: File error accessing recents directory (directory doesn’t exist?).
08-25 12:33:25.699 257 374 W InputDispatcher: Window a2a4604 com.android.settings/com.android.settings.Settings (server) is unresponsive: a2a4604 com.android.settings/com.android.settings.Settings (server) is not responding. Waited 5002ms for FocusEvent(hasFocus=false)
08-25 12:33:25.699 257 374 W InputDispatcher: Canceling events for a2a4604 com.android.settings/com.android.settings.Settings (server) because it is unresponsive
08-25 12:33:25.700 257 374 I WindowManager: ANR in Window{a2a4604 u0 com.android.settings/com.android.settings.Settings}. Reason:Input dispatching timed out (a2a4604 com.android.settings/com.android.settings.Settings (server) is not responding. Waited 5002ms for FocusEvent(hasFocus=false)).
08-25 12:33:25.703 257 1441 D ActivityManager: created ANR temporary file:/data/anr/temp_anr_7994889609945456720.txt
08-25 12:33:25.703 257 1441 I ActivityManager: Collecting stacks for pid 1396 into temporary file temp_anr_7994889609945456720.txt
08-25 12:33:25.704 257 1441 E system_server: Could not open /dev/binderfs/binder_logs/transactions. Likely a permissions issue. errno: 13
08-25 12:33:25.704 257 1441 E android.os.Debug: Failed to get binder state info for pid: 1396 status: -13: Permission denied
08-25 12:33:25.706 257 1441 I system_server: libdebuggerd_client: started dumping process 1396
08-25 12:33:25.707 38 38 I tombstoned: registered intercept for pid 1396 and type kDebuggerdJavaBacktrace
08-25 12:33:25.708 1396 1398 I ndroid.settings: Thread[2,tid=1398,WaitingInMainSignalCatcherLoop,Thread*=0xb400007297c0df50,peer=0x14003b98,“Signal Catcher”]: reacting to signal 3
08-25 12:33:25.708 1396 1398 I ndroid.settings:
08-25 12:33:25.729 257 1442 I ActivityManager: dumpStackTraces pids={635=true, 719=true, 765=true, 836=true, 874=true, 887=true, 909=true, 911=true, 954=true, 983=true, 999=true, 1001=true, 1033=true, 1047=true, 1059=true, 1071=true, 1087=true, 1101=true, 1123=true, 1136=true, 1150=true}
08-25 12:33:25.731 257 1442 I ActivityManager: Dumping to /data/anr/anr_2026-08-25-12-33-25-729
08-25 12:33:25.795 38 38 I tombstoned: received crash request for pid 1396
08-25 12:33:25.795 38 38 I tombstoned: found intercept fd 512 for pid 1396 and type kDebuggerdJavaBacktrace
08-25 12:33:25.796 1396 1398 I ndroid.settings: Wrote stack traces to tombstoned
08-25 12:33:25.796 38 38 W tombstoned: skipping tombstone file creation due to intercept
08-25 12:33:25.796 257 1441 I system_server: libdebuggerd_client: done dumping process 1396

Just FYI, you shouldn’t ever need to go for those android settings. You handle all bluetooth connections in native settings app →Bluetooth. There you determine whether connection is to be made for native side or for AAS side. So this discovery of your might be actually feature to protect you, not a bug. Same as you should handle all WLAN stuff on native side.

2 Likes

Thanks for insight ;);):wink: and good logic. But why then on xperia 10II, I can access these settings (I know it is 5.1 version of AppSupport ) and I can pair my smart swimming goggles with xperia whlie with J2 - not ;);):). If other users will report that they can not access these settings on J2 - then it is afeatture - not a bug and I will close this ticket and keep digging why pairing is not working on J2 :wink:

With J2 you probably can’t get the connection to work because of this bug: Jolla Phone (2026) Bluetooth crashes randomly - #43 by filip.k . IIRC in last community meeting Jolla said that there is at least some improvements expected to be in next update. There definitely is differences and changes made for J2 bluetooth system compared to Xperia 5.1 lineup, which is still in work in progress. I also have bluetooth issues that aren’t present in 10 III, but have to wait for general fix first