# \[UNOFFICIAL BUILDS\] Samsung Galaxy S23 / S23+ / S23 Ultra

**URL:** <https://community.iode.tech/t/unofficial-builds-samsung-galaxy-s23-s23-s23-ultra/5444>\
**Category:** Community Builds & GSI\
**Created:** [12 February 2025 19:44 UTC](https://community.iode.tech/t/unofficial-builds-samsung-galaxy-s23-s23-s23-ultra/5444 "2025-02-12T19:44:17Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![PalmerC](https://community.iode.tech/letter_avatar_proxy/v4/letter/p/7ab992/32.png) [@PalmerC](https://community.iode.tech/u/PalmerC)\
**Post date:** [18 June 2026 12:51 UTC](https://community.iode.tech/t/unofficial-builds-samsung-galaxy-s23-s23-s23-ultra/5444/22 "2026-06-18T12:51:12Z")

</div>

Additional note.  
The problem does NOT appears when a Whatsapp call comes in.  
A Whatsapp incoing call rings normally

---

<div class="post-metadata">

**Author:** ![PalmerC](https://community.iode.tech/letter_avatar_proxy/v4/letter/p/7ab992/32.png) [@PalmerC](https://community.iode.tech/u/PalmerC)\
**Post date:** [18 June 2026 16:33 UTC](https://community.iode.tech/t/unofficial-builds-samsung-galaxy-s23-s23-s23-ultra/5444/23 "2026-06-18T16:33:35Z")

</div>

Maybe I have simply to wait for an angel who likes “coffee” to make the 7.6 available so I can upgrade rather than downgrade 😀 –Update -  
@ronnz98 , Hi Ronald my young son has start fiddling with Android and he pulled this report out of the phone with adb. It is from the bluethooth log. I do not know if this might help clarifying the issue.

==================================================================================

1. 
# START OF THE CALL & BLUETOOTH HANDSHAKE TIMELINE

06-18 19:20:43.279 2239 3386 I Telecom : InCallController: Calling onAvailableCallEndpointsChanged  
06-18 19:20:43.279 2239 3386 I Telecom : InCallController: Calling onCallEndpointChanged  
06-18 19:20:43.279 2239 3386 I Telecom : CallAudioRouteController: UPDATE\_SYSTEM\_AUDIO\_ROUTE  
06-18 19:20:43.279 2239 3386 I Telecom : AudioState isMuted: false, route: BLUETOOTH, activeBluetoothDevice: [XX:XX:XX:XX:65:20]  
06-18 19:20:49.256 3277 3742 I BluetoothActiveDeviceManager: setActiveDevice: null, setHeadset=true, setA2dp=false  
06-18 19:20:49.256 3277 3742 I BluetoothActiveDeviceManager: Setting active Headset (OpenRun by Shokz)

# ==================================================================================

1. THE AUDIO PROBLEM (FATAL ROUTING CRASH LOOP)

[EXPLANATION]: The Bluetooth stack enters a loop where it tries to initialize a normal  
media stream (A2DP), but the OS rejects it repeatedly because it cannot resolve how  
to run media and an active phone call concurrently over the Snapdragon audio HAL.

06-18 19:20:50.985 3277 3742 E bluetooth-a2dp: unable to start stream: call is active  
06-18 19:20:50.986 1355 7863 I BTAudioProviderStub: streamStarted - SessionType=A2DP\_SOFTWARE\_ENCODING\_DATAPATH, status=FAILURE  
06-18 19:20:50.987 1355 7863 I BTAudioSessionAidl: ReportControlStatus - status=FAILURE  
06-18 19:20:51.828 3277 3742 E bluetooth-a2dp: unable to start stream: call is active  
06-18 19:20:51.829 1355 7863 I BTAudioHalDeviceProxyAIDL: control\_result\_cb: session\_type=A2DP\_SOFTWARE\_ENCODING\_DATAPATH, status=FAILURE  
06-18 19:20:52.850 1355 7863 E BTAudioHalDeviceProxyAIDL: Start: session\_type=A2DP\_SOFTWARE\_ENCODING\_DATAPATH failure  
06-18 19:20:52.850 1355 7863 E BTAudioHalStream: out\_write: state=STANDBY failed to resume  
06-18 19:20:53.668 1355 7863 W BTAudioHalDeviceProxyAIDL: control\_result\_cb: status=FAILURE failure for session\_type=A2DP\_SOFTWARE\_ENCODING\_DATAPATH  
06-18 19:20:54.095 3277 3742 E bluetooth-a2dp: unable to start stream: call is active  
06-18 19:20:54.096 1355 7863 E BTAudioHalDeviceProxyAIDL: Start: session\_type=A2DP\_SOFTWARE\_ENCODING\_DATAPATH failure

# ==================================================================================

1. END OF THE CALL TIMELINE & ROUTING TEARDOWN

06-18 19:20:49.629 2239 7798 I Telecom : CallAudioRouteController: onCommunicationDeviceChanged: previous device (AudioDeviceInfo: type: bt\_sco id: 38), current device (AudioDeviceInfo: type: earpiece id: 2)  
06-18 19:20:49.629 2239 7798 I Telecom : CallAudioRouteController: handleBtConnectionStateChanged: SCO connected(false) for address C0:86:B3:3A:65:20  
06-18 19:20:49.629 2239 7798 I Telecom : CallAudioRouteController: Evaluating BT disconnect: isScoConnected=false, isOriginDisconnected=true  
06-18 19:20:49.629 2239 7798 I Telecom : CallAudioRouteController: Enter pending route, orig=AudioRouteType=TYPE\_BLUETOOTH\_SCO, dest=AudioRouteType=TYPE\_EARPIECE  
06-18 19:20:49.629 2239 3386 I Telecom : CallAudioRouteController: Message received: EXIT\_PENDING\_ROUTE  
06-18 19:20:49.629 1489 3296 D AudioFlinger: moveEffectChain\_ll: successful move of session from Bluetooth to EarPiece thread  
06-18 19:20:49.629 2239 3386 I Telecom : Event: RecordEntry TC@1: AUDIO\_ROUTE, Entering audio route: AudioRoute[Type=TYPE\_EARPIECE]  
06-18 19:20:49.630 2239 3386 I Telecom : CallAudioRouteController: updateCallAudioState: updating call audio state to [AudioState isMuted: false, route: EARPIECE]  
06-18 19:20:49.630 2239 3386 I Telecom : InCallController: Calling onAudioStateChanged, audioState: route: EARPIECE, activeBluetoothDevice: [null]  
06-18 19:21:28.448 1357 3490 D vendor.qti.bluetooth@1.1-wake\_lock: Release wakelock is released  
06-18 19:21:35.255 1357 1357 D vendor.qti.bluetooth@1.1-ibs\_handler: SerialClockVote: vote for UART CLK OFF

---

<div class="post-metadata">

**Author:** ![ronnz98](https://community.iode.tech/user_avatar/community.iode.tech/ronnz98/32/2811_2.png) [@ronnz98](https://community.iode.tech/u/ronnz98)\
**Post date:** [19 June 2026 11:31 UTC](https://community.iode.tech/t/unofficial-builds-samsung-galaxy-s23-s23-s23-ultra/5444/24 "2026-06-19T11:31:51Z")

</div>

Try latest build please:  
[iode-7.6-20260619-dm1q.zip](https://sourceforge.net/projects/eosbuildsronnz98/files/OtherCustomROMS/iode/iode-7.6-20260619-dm1q.zip/download)

Source and install instructions for S23:

> **[Info about dm1q | LineageOS Wiki](https://wiki.lineageos.org/devices/dm1q/)**

[iode-7.6-20260622-dm2q.zip](https://sourceforge.net/projects/eosbuildsronnz98/files/OtherCustomROMS/iode/iode-7.6-20260622-dm2q.zip/download)

[iode-7.6-20260622-dm3q.zip](https://sourceforge.net/projects/eosbuildsronnz98/files/OtherCustomROMS/iode/iode-7.6-20260622-dm3q.zip/download)

Source and install instructions for S23+ and S23 Ultra:  
[https://xdaforums.com/t/rom-official-16-0-evolution-x-11-for-galaxy-s23-plus.4782988/](https://xdaforums.com/t/rom-official-16-0-evolution-x-11-for-galaxy-s23-plus.4782988/)

---

<div class="post-metadata">

**Author:** ![PalmerC](https://community.iode.tech/letter_avatar_proxy/v4/letter/p/7ab992/32.png) [@PalmerC](https://community.iode.tech/u/PalmerC)\
**Post date:** [19 June 2026 14:03 UTC](https://community.iode.tech/t/unofficial-builds-samsung-galaxy-s23-s23-s23-ultra/5444/25 "2026-06-19T14:03:28Z")

</div>

Hi Ronald, my phone is the dm2q (S23+)

---

<div class="post-metadata">

**Author:** ![ronnz98](https://community.iode.tech/user_avatar/community.iode.tech/ronnz98/32/2811_2.png) [@ronnz98](https://community.iode.tech/u/ronnz98)\
**Post date:** [22 June 2026 15:13 UTC](https://community.iode.tech/t/unofficial-builds-samsung-galaxy-s23-s23-s23-ultra/5444/26 "2026-06-22T15:13:56Z")

</div>

I updated also S23+ ROM now

---

<div class="post-metadata">

**Author:** ![PalmerC](https://community.iode.tech/letter_avatar_proxy/v4/letter/p/7ab992/32.png) [@PalmerC](https://community.iode.tech/u/PalmerC)\
**Post date:** [23 June 2026 19:36 UTC](https://community.iode.tech/t/unofficial-builds-samsung-galaxy-s23-s23-s23-ultra/5444/27 "2026-06-23T19:36:32Z")

</div>

Hi Ron,  
No joy with 7.6 either.

Here below the error logged.:  
The last 3 lines in it puzzels me. Why HFP keeps on flipping ?  
Bon, I do not know enough. Again , Whatsapp calls ring just fine.

# ====================================================================

BUG REPORT SUMMARY: BLUETOOTH SYSTEM SERVER CRASH (SIGABRT)

[SYSTEM INFO]  
OS: iodéOS (Android 14/15 Base)  
Process: com.android.bluetooth  
Thread: gd\_stack\_thread (Gabeldorsche Bluetooth Stack)

* * *

[1. THE SMOKING GUN: FATAL CRASH]  
The Bluetooth system server terminates unexpectedly due to a fatal abort (Signal 6) originating from the modern Android Bluetooth stack (Gabeldorsche JNI library).

Timestamp: 06-22 22:33:12.032  
PID: 3944 | TID: 4118

Log Snippet:  
F libc : Fatal signal 6 (SIGABRT), code -1 (SI\_QUEUE) in tid 4118 (gd\_stack\_thread), pid 3944 (droid.bluetooth)  
F DEBUG : Cmdline: com.android.bluetooth  
F DEBUG : pid: 3944, tid: 4118, name: gd\_stack\_thread \>\>\> com.android.bluetooth \<\<\<

* * *

[2. DEVS: CRITICAL STACK TRACE]  
The crash occurs instantly during the `on_connection_complete` lifecycle hook, specifically failing inside the internal logging utility (`vlog`). This points to a malformed log string format, an unallocated memory read, or a null pointer exception during connection event logging.

#00 pc 00000000000b03b0 /apex/com.android.runtime/lib64/bionic/libc.so (tgkill+16)  
#01 pc 00000000000539c8 /apex/com.android.runtime/lib64/bionic/libc.so (abort+140)  
#02 pc 00000000006734d4 /apex/com.android.btservices/lib64/libbluetooth\_jni.so (/\* error handling/abort code \*/)  
#03 pc 000000000030eb9c /apex/com.android.btservices/lib64/libbluetooth\_jni.so (bluetooth::log\_internal::vlog(…) + …)  
#04 pc 0000000000632a90 /apex/com.android.btservices/lib64/libbluetooth\_jni.so (on\_connection\_complete(…) + …)

* * *

[3. SYSTEM CONSEQUENCE: AUDIO ROUTING LOOP]  
Post-crash, the Bluetooth daemon attempts to recover, resulting in a cascading loop with the paired device (MAC: 3C:B0:ED:EE:89:37). The audio system gets stuck in a continuous loop trying to re-initialize profiles and resetting volume indices to 0.

Key Symptoms in Log:

- HFP (Hands-Free Profile) constantly flipping states:  
State 3 (Connecting) → State 0 (Disconnected) → State 2 (Connected) → Repeat.
- AudioVolumeChangeHandler flooding:  
“onVolumeGroupChanged: group: 5, volumeIndex: 0” repeating indefinitely.
- Result: Media audio cuts out entirely or aggressively oscillates between device and phone speakers.

====================================================================

[Previous page](https://community.iode.tech/t/unofficial-builds-samsung-galaxy-s23-s23-s23-ultra/5444.md?page=1)