FORUMS
Remove All Ads from XDA

[PX5][Android 8.0+][MD725] Fix for MD725 Type 2 Bluetooth on Oreo

28 posts
Thanks Meter: 9
 
Post Reply Email Thread
17th November 2018, 01:32 PM |#11  
switchboy's Avatar
Junior Member
Thanks Meter: 14
 
More
The sdsdk executable is currently not working because of text relocations which aren't allowed in Android in userland anymore. So we either need to find a way to run sdsdk outside userland or find an sdsdk executable without text relocations. A version from android 7 might work.

See attached logcat
Attached Thumbnails
Click image for larger version

Name:	Screenshot_20181117-003315_Log Viewer.jpg
Views:	598
Size:	258.0 KB
ID:	4645046  
The Following 2 Users Say Thank You to switchboy For This Useful Post: [ View ] Gift switchboy Ad-Free
 
 
17th November 2018, 06:26 PM |#12  
Quote:
Originally Posted by switchboy

The sdsdk executable is currently not working because of text relocations which aren't allowed in Android in userland anymore. So we either need to find a way to run sdsdk outside userland or find an sdsdk executable without text relocations. A version from android 7 might work.

See attached logcat

Great detailed summary and investigation into the issue.
Thanks for taking the time and sharing with the forums.

Until these blobs are updated or other software solution is found, we may have found a supplier for genuine GOC-MD-725.
19th November 2018, 02:23 PM |#13  
switchboy's Avatar
Junior Member
Thanks Meter: 14
 
More
Update
Not deterred, I managed to find a version of sdsdk without text relocations. I actually just took it out of the Android 7 rom for PX3, figuring that support for text relocations in userland was dropped by then. It turns out, I was right. ‘readelf –d sdsdk’ did not show the dreaded ‘0x00000016 (TEXTREL) 0x0’ anymore.

Hooray!

Therefore, after checking the shared library list and not seeing any new libraries I went ahead and overwrote my old version of sdsdk with this one. I rebooted the device and… nothing.

After reviewing, the logcat to find out what went wrong the following error messages repeats a couple of times:

Code:
libc    ( 1008): CANNOT LINK EXECUTABLE "/system/bin/sdsdk": cannot locate symbol "_ZN7android10AudioTrackC1E19audio_stream_type_tj14audio_format_tjj20audio_output_flags_tPFviPvS4_ES4_i15audio_session_tNS0_13transfer_typeEPK20audio_offload_info_tiiPK18audio_attributes_tbf" referenced by "/system/bin/sdsdk"...
11-19 14:46:00.787 F/libc    ( 1008): Fatal signal 6 (SIGABRT), code -6 in tid 1008 (sdsdk)
11-19 14:46:00.829 F/DEBUG   ( 1013): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-19 14:46:00.829 F/DEBUG   ( 1013): Build fingerprint: 'Android/px5/px5:8.0.0/OPR5.170623.007/hct08091121:userdebug/test-keys'
11-19 14:46:00.829 F/DEBUG   ( 1013): Revision: '0'
11-19 14:46:00.829 F/DEBUG   ( 1013): ABI: 'arm'
11-19 14:46:00.829 F/DEBUG   ( 1013): pid: 1008, tid: 1008, name: sdsdk  >>> /system/bin/sdsdk <<<
11-19 14:46:00.829 F/DEBUG   ( 1013): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
11-19 14:46:00.830 F/DEBUG   ( 1013): Abort message: 'CANNOT LINK EXECUTABLE "/system/bin/sdsdk": cannot locate symbol "_ZN7android10AudioTrackC1E19audio_stream_type_tj14audio_format_tjj20audio_output_flags_tPFviPvS4_ES4_i15audio_session_tNS0_13transfer_typeEPK20audio_offload_info_tiiPK18audio_attributes_tbf" referenced by "/system/bin/sdsdk"...'
11-19 14:46:00.830 F/DEBUG   ( 1013):     r0 00000000  r1 000003f0  r2 00000006  r3 00000008
11-19 14:46:00.830 F/DEBUG   ( 1013):     r4 000003f0  r5 000003f0  r6 ffe4d100  r7 0000010c
11-19 14:46:00.830 F/DEBUG   ( 1013):     r8 f70b0010  r9 ffe4d3a8  sl f70fcd90  fp ffe4e3b4
11-19 14:46:00.830 F/DEBUG   ( 1013):     ip 00000000  sp ffe4d0f0  lr f7164bc7  pc f716ede8  cpsr 200f0010
11-19 14:46:00.839 F/DEBUG   ( 1013): 
11-19 14:46:00.839 F/DEBUG   ( 1013): backtrace:
11-19 14:46:00.839 F/DEBUG   ( 1013):     #00 pc 00066de8  /system/bin/linker (__dl_tgkill+12)
11-19 14:46:00.839 F/DEBUG   ( 1013):     #01 pc 0005cbc3  /system/bin/linker (__dl_abort+54)
11-19 14:46:00.839 F/DEBUG   ( 1013):     #02 pc 00018641  /system/bin/linker (__dl___libc_fatal+24)
11-19 14:46:00.839 F/DEBUG   ( 1013):     #03 pc 0000fcb5  /system/bin/linker (__dl___linker_init+1956)
11-19 14:46:00.839 F/DEBUG   ( 1013):     #04 pc 00014d50  /system/bin/linker (_start+4)
11-19 14:46:00.858 W/NativeCrashListener(  499): Couldn't find ProcessRecord for pid 1008
Therefore, I assume that one of the libs sdsdk is depended on were updated and now is not quite compatible anymore. I am a bit hesitant to start altering system audio libraries willy-nilly because then I might start to break the audio subsystem of the rom. So unless I can find a version of sdsdk that is compatible with the audio subsystem of android 8 we are stuck at the moment.

Since the MD725 type 2 is a chip used in a lot of BT dongles as well there must be a device out there currently running android Oreo. I cant think of any reason why an sdsdk ripped from such firmware would not work on our Oreo installment. We just have to find it.
The Following 3 Users Say Thank You to switchboy For This Useful Post: [ View ] Gift switchboy Ad-Free
19th November 2018, 09:20 PM |#14  
Member
Boston, MA
Thanks Meter: 71
 
More
I love your persistence!

Did you also copy over the associated libraries? Typically, one can copy over the entire web of libraries required by a specific binary, and use those only for such binary, while leaving the rest of the system libraries alone. However, such solution may make things work, but may break integrations that Android may have had.

If only we had the source code ........

Seems like https://source.android.com/reference...taudio__policy may references audio_offload_info_t.... I'll take a look. I might as well just scrape all the symbols to get a layout of what's calling what
19th November 2018, 09:56 PM |#15  
switchboy's Avatar
Junior Member
Thanks Meter: 14
 
More
If only we had the sourcecode of sdsdk I could debug it against current libraries rewrite it a bit and then compile a working version.
The Following 2 Users Say Thank You to switchboy For This Useful Post: [ View ] Gift switchboy Ad-Free
21st November 2018, 03:54 PM |#16  
OP Junior Member
Flag Perth
Thanks Meter: 9
 
More
@switchboy I am really impressed with the level of debugging and research you went into! Thank you!!

It makes it more confusing that my BlueTooth works for around 30 minutes or so (or until I end a call) before my phone disconnects (but the HU still thinks it is connected).
21st November 2018, 03:57 PM |#17  
OP Junior Member
Flag Perth
Thanks Meter: 9
 
More
Quote:
Originally Posted by marchnz

Great detailed summary and investigation into the issue.
Until these blobs are updated or other software solution is found, we may have found a supplier for genuine GOC-MD-725.

I am very interested in this supplier!
21st November 2018, 08:59 PM |#18  
switchboy's Avatar
Junior Member
Thanks Meter: 14
 
More
Quote:
Originally Posted by jimimatthews

@switchboy I am really impressed with the level of debugging and research you went into! Thank you!!

It makes it more confusing that my BlueTooth works for around 30 minutes or so (or until I end a call) before my phone disconnects (but the HU still thinks it is connected).

Could you by any chance upload the sdsdk which is in your bin folder on the hu? To double check if it is the same one from the OP.
22nd November 2018, 02:11 PM |#19  
Member
Boston, MA
Thanks Meter: 71
 
More
Quote:
Originally Posted by jimimatthews

I am very interested in this supplier!

Check the md725 module 1 and 2 swap thread
14th December 2018, 05:18 PM |#20  
Junior Member
Thanks Meter: 0
 
More
I'm getting a similar issue with my Bluetooth.

A2DP, Call History and Contact Sync all work
but Calling does not work properly. People can hear me, but I cannot hear them through my speakers.

I'm using an AVIN PX5
MCU version: MTCE_GS_V2.94_3 Sep 13 2018 11:26:51

I'm wondering if any MCU updates are available to resolve this issue?
2nd January 2019, 12:27 PM |#21  
Junior Member
Thanks Meter: 1
 
More
Any update to fix this problem ??!
Post Reply Subscribe to Thread

Tags
android 8.0 oreo, bluetooth, headunit, md725, mtcd

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes