Hi everybody
I have searched all over the internet for a working mkyaffs.exe I found one (attached below) but it's not working with me, it does create the output it should create, but:
1. it's 14MB larger than the one CWM Created.
2. unyaffs returns error when trying to unyaffs the file I created via mkyaffs
The error that is produced is:
Code:
0 [main] unyaffs 768 exception::handle: Exception: STATUS_ACCESS_VIOLATION
624 [main] unyaffs 768 open_stackdumpfile: Dumping stack trace to unyaffs.ex
e.stackdump
The stackdump is:
Code:
Exception: STATUS_ACCESS_VIOLATION at eip=6112A143
eax=00000000 ebx=00000004 ecx=00002400 edx=00000000 esi=20028390 edi=00000000
ebp=0028ABE8 esp=0028ABE4 program=C:\Users\Omar\Desktop\New folder (2)\unyaffs.exe, pid 768, thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args
0028ABE8 6112A143 (00000000, 0040DC70, 00000200, 00000000)
0028AC28 004010BF (0028ACA9, 00000000, 20028280, 00401333)
0028AC58 004013AF (00000002, 0028AC80, 20028280, 0028ACA0)
0028AD08 61007535 (00000000, 0028CD88, 61006B20, 00000000)
End of stack trace
Thanks in advance
hi all:
i download aosp kitkat4.4 source codes from google website. i compiled the code. i got the ROM.but when i flash the ROM to my device nexus 7(deb). it cannot boot.
from the log. i found that following error log. the sentence "couldn't find an OpenGL ES implementation" maybe cause the fatal question.
any advices is welcomed !
thank
brian
02-10 08:37:07.375: E/QCOMKeyMaster(17633): failed to load qseecom library
02-10 08:37:07.375: E/keystore(17633): could not open keymaster device in keystore (Operation not permitted)
02-10 08:37:07.375: E/keystore(17633): keystore keymaster could not be initialized; exiting
02-10 08:37:07.405: A/libEGL(17630): couldn't find an OpenGL ES implementation
02-10 08:37:07.405: A/libc(17630): Fatal signal 6 (SIGABRT) at 0x000044de (code=-6), thread 17630 (surfaceflinger)
02-10 08:37:07.575: E/msm8960_platform(17632): platform_init: DLOPEN failed for libacdbloader.so
02-10 08:37:07.575: E/msm8960_platform(17632): platform_init: DLOPEN failed for libcsd-client.so
02-10 08:37:07.575: E/MonoPipe(17632): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
[msm8939][meizu][camera]dlopen failed: could not load library "libcam.meiyan.so" need
Hello,
Could you please help me?
Platform:meizu m1note msm8939
I ported from flyme to miui.
The camera has problem.
I got the error:
dlopen failed: could not load library "libcam.meiyan.so" needed by "camera.msm8916.so";
caused by cannot locate symbol "_ZN11CBeautyShot18SetSkinBrightLevelEl" referenced by "libcam.meiyan.so"...
About symbol "_ZN11CBeautyShot18SetSkinBrightLevelEl",
I found it at:
m463c/rom/update/system $ g CBeautyShot
Binary file ./lib/libarcsoft_beauty_shot.so matches
Binary file ./lib/libcam.meiyan.so matches
And I push them to my phone.
But I still get the error.
Who can help me? Thank you very much.
I have been debugging for several days.
01-02 08:17:52.901 I/libmdmdetect( 351): Found internal modem: modem
01-02 08:17:52.901 E/QC-QMI ( 272): qmi_client [272]: unable to connect to server, errno=[2:No such file or directory], attempt=1
01-02 08:17:52.901 E/QC-QMI ( 351): qmi_client [351]: unable to connect to server, errno=[2:No such file or directory], attempt=1
01-02 08:17:52.901 I/ThermalEngine( 288): Sensor:tsens_tz_sensor3:80000 mC
01-02 08:17:52.941 E/HAL ( 276): load: module=/system/lib/hw/camera.msm8916.so
01-02 08:17:52.941 E/HAL ( 276): dlopen failed: could not load library "libcam.meiyan.so" needed by "camera.msm8916.so"; caused by cannot locate symbol "_ZN11CBeautyShot18SetSkinBrightLevelEl" referenced by "libcam.meiyan.so"...
01-02 08:17:52.941 E/CameraService( 276): Could not load camera HAL module
01-02 08:17:52.941 I/mediaserver( 276): ListenService instantiated
01-02 08:17:52.941 V/ListenService( 276): instantiate entered
01-02 08:17:52.941 V/ListenService( 276): getInstance entered, mNumInstances currently 0
Eismog
my-mail:[email protected]
Is there anyone who can help me?
I'm making a CM12.1 ROM port. Every time after compilation, I'm just stuck on the boot screen. My logcat logs always look like this:
Code:
D/gps_ril_BRCM( 1390): ril thread received 0 events
D/gps_ril_BRCM( 1390): ril_state_thread, fd < 0, calling timeout_action_add
I/DEBUG ( 1389): tid 15467 does not exist in pid 15467. ignoring debug request
I/ServiceManager( 1385): service 'media.audio_flinger' died
I/ServiceManager( 1385): service 'media.player' died
I/ServiceManager( 1385): service 'media.camera' died
I/ServiceManager( 1385): service 'media.audio_policy' died
D/gps_ril_BRCM( 1390): ril thread received 0 events
D/gps_ril_BRCM( 1390): ril_state_thread, fd < 0, calling timeout_action_add
I/mediaserver(15513): ServiceManager: 0x2a00b448
I/AudioFlinger(15513): Using default 3000 mSec as standby time.
E/MediaPlayerFactory(15513): calling dlopen on FACTORY_LIB
E/MediaPlayerFactory(15513): calling dlsym on pFactoryLib for FACTORY_CREATE_FN
E/MediaPlayerFactory(15513): registering DASH Player factory...
I/CameraService(15513): CameraService started (pid=15513)
I/CameraService(15513): Loaded "BCM21553 Camera HAL" camera module
D/BcmCamera(15513): HAL_get_number_of_cameras: numCameras:1
I/AudioPolicyManagerBase(15513): loadAudioPolicyConfig() loaded /system/etc/audio_policy.conf
I/AudioFlinger(15513): loadHwModule() Loaded primary audio interface from Samsung BCM21553 audio HW HAL (audio) handle 1
I/AudioFlinger(15513): HAL output buffer size 1024 frames, normal mix buffer size 1024 frames
I/AudioMixer(15513): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
I/AudioFlinger(15513): Using module 1 has the primary audio interface
D/AudioPolicyManagerBase(15513): setOutputDevice() changing device from (2) to (2) force (1) delayMs (0) on Output (2)
I/AudioFlinger(15513): AudioFlinger's thread 0x40f53008 ready to run
W/AudioFlinger(15513): Thread AudioOut_2 cannot connect to the power manager service
D/audio_hw_primary(15513): call=n, earpiece=n hp=n speaker=y sco=n a2dp=n out_device=2
W/AudioFlinger(15513): Thread AudioOut_2 cannot connect to the power manager service
I/audio_a2dp_hw(15513): adev_open: adev_open in A2dp_hw module
I/AudioFlinger(15513): loadHwModule() Loaded a2dp audio interface from A2DP Audio HW HAL (audio) handle 3
I/AudioFlinger(15513): loadHwModule() Loaded usb audio interface from USB audio HW HAL (audio) handle 4
W/AudioFlinger(15513): Thread AudioOut_2 cannot connect to the power manager service
E/AudioFlinger(15513): no wake lock to update!
I/r_submix(15513): adev_open(name=audio_hw_if)
I/r_submix(15513): adev_init_check()
I/AudioFlinger(15513): loadHwModule() Loaded r_submix audio interface from Wifi Display audio HAL (audio) handle 5
I/AudioPolicyService(15513): Loaded audio policy from LEGACY Audio Policy HAL (audio_policy)
D/gps_ril_BRCM( 1390): ril thread received 0 events
D/gps_ril_BRCM( 1390): ril_state_thread, fd < 0, calling timeout_action_add
D/AndroidRuntime(15512):
D/AndroidRuntime(15512): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime(15512): CheckJNI is OFF
D/dalvikvm(15512): Unable to stat classpath element '/system/framework/core.jar'
D/dalvikvm(15512): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm(15512): ODEX file is stale or bad; removing and retrying (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm(15512): DexOpt: --- BEGIN 'conscrypt.jar' (bootstrap=1) ---
E/dalvikvm(15640): Fatal error: java/lang/Object
E/dalvikvm(15640): VM aborting
F/libc (15640): Fatal signal 6 (SIGABRT) at 0x00003d18 (code=-6), thread 15640 (dexopt)
I/DEBUG ( 1389): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1389): Build fingerprint: 'Samsung/cm_totoro/totoro:5.1.1/KTU84Q/20150211:userdebug/release-keys'
I/DEBUG ( 1389): Revision: '0'
I/DEBUG ( 1389): pid: 15640, tid: 15640, name: dexopt >>> /system/bin/dexopt <<<
[A bunch of seemingly random (at least for such a noob like me) numbers]
W/dalvikvm(15512): DexOpt: --- END 'conscrypt.jar' --- status=0x0006, process failed
E/dalvikvm(15512): Unable to extract+optimize DEX from '/system/framework/conscrypt.jar'
D/dalvikvm(15512): Unable to process classpath element '/system/framework/conscrypt.jar'
D/dalvikvm(15512): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm(15512): ODEX file is stale or bad; removing and retrying (/data/dalvik-cache/[email protected]@[email protected])
D/gps_ril_BRCM( 1390): ril thread received 0 events
D/gps_ril_BRCM( 1390): ril_state_thread, fd < 0, calling timeout_action_add
D/dalvikvm(15512): DexOpt: --- BEGIN 'okhttp.jar' (bootstrap=1) ---
E/dalvikvm(15692): Fatal error: java/lang/Object
E/dalvikvm(15692): VM aborting
F/libc (15692): Fatal signal 6 (SIGABRT) at 0x00003d4c (code=-6), thread 15692 (dexopt)
I/DEBUG ( 1389): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1389): Build fingerprint: 'Samsung/cm_totoro/totoro:5.1.1/KTU84Q/20150211:userdebug/release-keys'
And so on, and so on, until it fails to load everything and starts all over again.
And yes, if you look at the logs, I am porting a ROM to an obsolete device and no, I don't really care that it's "not gonna work". I just want to fix that dex problem.
What I tried so far:
- cleaning up the rom (did nothing)
- changing up a few libraries that had something to do with "dex" (did nothing, but I might have missed something)
- re-unpacked the frameworks (did nothing)
- re-downloaded the rom then re-unpacked the frameworks (also did nothing)
- downloaded another rom and re-unpacked the frameworks (did nothing, what a waste of bandwidth)
- cleared Dalvik cache (did not do anything, I do that every build alongside with a factory wipe in CWM)
- changed the kernel TWICE (did nothing except for making logcat work (it wasn't working for a few builds))
Anyone got any ideas?
knuxfanwin8 said:
I'm making a CM12.1 ROM port. Every time after compilation, I'm just stuck on the boot screen. My logcat logs always look like this:
And so on, and so on, until it fails to load everything and starts all over again.
And yes, if you look at the logs, I am porting a ROM to an obsolete device and no, I don't really care that it's "not gonna work". I just want to fix that dex problem.
What I tried so far:
- cleaning up the rom (did nothing)
- changing up a few libraries that had something to do with "dex" (did nothing, but I might have missed something)
- re-unpacked the frameworks (did nothing)
- re-downloaded the rom then re-unpacked the frameworks (also did nothing)
- downloaded another rom and re-unpacked the frameworks (did nothing, what a waste of bandwidth)
- cleared Dalvik cache (did not do anything, I do that every build alongside with a factory wipe in CWM)
- changed the kernel TWICE (did nothing except for making logcat work (it wasn't working for a few builds))
Anyone got any ideas?
Click to expand...
Click to collapse
Yeah. You need to Deodex both ROM BASE and PORT BEFORE you build. That is the reason you keep getting dex errors. Use ASSAYYED Kitchen or @superR's Kitchen or similar to accomplish this ?
Hi everyone.
As people are aware, upgrading to Android 8.0 Oreo broke the functionality of Bluetooth for users with the MD725 Type 2 Bluetooth module. I have now found the driver file that will likely repair all lost Bluetooth functionality - the sdsdk file. This should also fix any external USB WiFi/Bluetooth devices that use the MD725 Type 2 module.
I have tested this on my MTCD HA unit running Hal9k's Oreo ROM and can confirm that the following features now work:
- A2DP
- Calling
- Call History
- Contact sync
Note: This fix requires root access.
Installation Instructions:
1. Download the attached sdsdk.zip file.
2. From the sdsdk.zip file, extract the "sdsdk" file.
4. Copy the sdsdk file to a USB drive or SD Card to be plugged into your headunit
5. Install a Root file explorer.
6. Copy the sdsdk file from your external storage device to the location:
Code:
/system/bin
7. Reboot your headunit.
The working sdsdk file is from the MTCD_HA_20170726 ROM provided by @f1x in their "Solution for the bluetooth echo v2":
https://forum.xda-developers.com/an...neral/px5-solution-bluetooth-echo-v2-t3661284
I hope that this fix works for you!
@Malaysk perhaps you can try to incorporate this fix in your rom if tested to work OK?
Sent from my G8141 using Tapatalk
The command "ps | grep sdsdk" just returns the line(s) containing sdsdk (grep command) from the running processes list (ps command). So I think that that step is not necessary.
Also where did you find a working sdsdk for android 8, substituting the one from android 6 was tried before and did not work.
Regardless I will try to flash my android 6 HU to HALK's Oreo to comfirm this working on a MTCD KGL (v2.83)
switchboy said:
The command "ps | grep sdsdk" just returns the line(s) containing sdsdk (grep command) from the running processes list (ps command). So I think that that step is not necessary.
Also where did you find a working sdsdk for android 8, substituting the one from android 6 was tried before and did not work.
Regardless I will try to flash my android 6 HU to HALK's Oreo to comfirm this working on a MTCD KGL (v2.83)
Click to expand...
Click to collapse
Okay, I've removed that part of the step. I had a feeling it wasn't necessary but left it in.
The working sdsdk is from the MTCD_HA_20170726 ROM, which was collected by @f1x for the "Bluetooth echo solution".
Thanks! Please reply with your results!
I am afraid it did not work for me. Added the files to 'system/bin/'
Gave the the file 777 permission just to be sure (read write execute)
Did a reboot, no luck
As you can see sdsdk is not running when I search for it with 'ps | grep sdsdk'
I added photographs of the situation.
This is a fresh upgrade to HALK's Oreo rom from Android 6.0 do i need to select the MD725 as my BT adapter somewhere? Because that might be causing my issues? I will check the factory setting later (although they should not have been touched and BT was working on android 6)
It will have to be another time though. It's getting cold now that it is dark and I don't want to burn petrol while waiting on the HU. Already used a bit too much battery power while waiting on the update process.
Edit:
OP, did you also install the libraries (.lib files) provided by f1x? That might be the reason why it did not work and sdsdk doesn't run on my system right now.
hello . i have mtcd px5 , MX , Bluetooth MD725 type 2 , i am now at malaysk rom 6 v7 , want to ask if this fix will work with me ? till now i didn't try android 8 because of Bluetooth problem ?
Have been playing around with this idea some more. First off I checked if for some reason the Bluetooth adapter in the factory settings was changed. So I double checked and it was still set to MD725. So that was not the reason why sdsdk is not running. Secondly I thought maybe sdsdk is missing other files it depends on to run so I went ahead and made sure I copied the .lib files and the .ini file from f1x to the right folders and made sure all of them were executable. After that I did a reboot of my device and nothing. The Bluetooth name and pin are not populated in the settings menu and the process sdsdk is still not in the running processes list. This could either mean:
- The process sdsdk isn't started by the system on boot and we need a way to start it manually
- The process sdsdk is started but crashes soon after being started because it is still missing dependencies
- The implementation of sdsdk is not compatible with android 8 anymore (which would mean the end of the line for this approach)
After these tests I was a bit disappointed and had ran out of time for today. I need some way to check if sdsdk is doing anything and if so what it is actually doing. So on a PC my next logical step will be to try and run the program manually from the command line and see if it spits out an error. If it does I might be able to solve the problem.
Because of digging work by f1x we know that the init.hct.rc script does contain the commands to start sdsdk: (so this makes the first scenario unlikely)
Code:
on property:bt.md725.type=1
start gocsdk
service gocsdk /system/bin/gocsdk
class main
user root
group root
disabled
seclabel u:r:shell:s0
on property:bt.md725.type=2
start sdsdk
service sdsdk /system/bin/sdsdk
class main
user root
group root
disabled
seclabel u:r:shell:s0
I think the second scenario is the most likely scenario and sdsdk is missing the right (versions) of other files the program depends on. So we need to figure out what those files are. Furtermore I think the simple terminal command '/system/bin/sdsdk' probably wont start the service in a way that is useful for the OS, however I am hoping it wil output a usefull error code. So that will be the fist thing I will try next time I got some spare time to play with the HU.
Unfortunately I am a bit of a Windows guy and hobby developer (with limited C++, PHP and Java knowledge) so my Linux knowledge is limited. I would love to be able to decompile sdsdk to see what it actually does that might make fixing this software mess a bit easier. At this point I am not expecting a manufacturer to do it for us. As for now I just making guesses why it doesn't work and I don't like that.
switchboy said:
- The process sdsdk is started but crashes soon after being started because it is still missing dependencies
Click to expand...
Click to collapse
You can test this by, first, running '/system/bin/sdsdk' in a terminal. Even if this step works, I would see the missing libraries by running 'ldd /system/bin/sdsdk'. The assumption in the 'ldd' step is that the binary gets libraries dynamically attached to it when it runs, as opposed to coming packaged with the binary.
Feel free to paste the output and I can help interpret it. I would do this myself, but at the rate at which I'm going, I won't get to it until next year
P.S. you may need to find a binary for ldd on Android. Termux has an ability to get such, just type in the command, and if it knows it can download a binary for a missing program, then it will tell you how to do it
I dont have acces to my headunit at the moment. The wife has taken the car for a drive. So I did the next best thing and used readelf on a ubuntu vm to try and find dependencies of the sdsdk binairy. Here is the raw output:
Code:
@Butterfly:~/Desktop$ readelf -And sdsdk
Dynamic section at offset 0xbe65c contains 33 entries:
Tag Type Name/Value
0x00000003 (PLTGOT) 0xbfd84
0x00000002 (PLTRELSZ) 1248 (bytes)
0x00000017 (JMPREL) 0x9bc0
0x00000014 (PLTREL) REL
0x00000011 (REL) 0x2cb0
0x00000012 (RELSZ) 28432 (bytes)
0x00000013 (RELENT) 8 (bytes)
0x6ffffffa (RELCOUNT) 3551
0x00000015 (DEBUG) 0x0
0x00000006 (SYMTAB) 0x148
0x0000000b (SYMENT) 16 (bytes)
0x00000005 (STRTAB) 0x1258
0x0000000a (STRSZ) 4590 (bytes)
0x00000004 (HASH) 0x2448
0x00000001 (NEEDED) Shared library: [libtinyalsa.so]
0x00000001 (NEEDED) Shared library: [libmedia.so]
0x00000001 (NEEDED) Shared library: [libutils.so]
0x00000001 (NEEDED) Shared library: [libbinder.so]
0x00000001 (NEEDED) Shared library: [liblog.so]
0x00000001 (NEEDED) Shared library: [libstdc++.so]
0x00000001 (NEEDED) Shared library: [libm.so]
0x00000001 (NEEDED) Shared library: [libc.so]
0x00000001 (NEEDED) Shared library: [libdl.so]
0x0000001a (FINI_ARRAY) 0xbc3b8
0x0000001c (FINI_ARRAYSZ) 8 (bytes)
0x00000019 (INIT_ARRAY) 0xbc3c0
0x0000001b (INIT_ARRAYSZ) 36 (bytes)
0x00000020 (PREINIT_ARRAY) 0xbc3e4
0x00000021 (PREINIT_ARRAYSZ) 0x8
0x00000016 (TEXTREL) 0x0
0x0000001e (FLAGS) TEXTREL BIND_NOW
0x6ffffffb (FLAGS_1) Flags: NOW
0x00000000 (NULL) 0x0
Displaying notes found in: .note.gnu.gold-version
Owner Data size Description
GNU 0x00000009 NT_GNU_GOLD_VERSION (gold version)
Version: gold 1.11
Attribute Section: aeabi
File Attributes
Tag_CPU_name: "ARM v7"
Tag_CPU_arch: v7
Tag_CPU_arch_profile: Application
Tag_ARM_ISA_use: Yes
Tag_THUMB_ISA_use: Thumb-2
Tag_FP_arch: VFPv3
Tag_Advanced_SIMD_arch: NEONv1
Tag_ABI_PCS_GOT_use: GOT-indirect
Tag_ABI_PCS_wchar_t: 4
Tag_ABI_FP_denormal: Needed
Tag_ABI_FP_exceptions: Needed
Tag_ABI_FP_number_model: IEEE 754
Tag_ABI_align_needed: 8-byte
Tag_ABI_enum_size: int
Tag_ABI_HardFP_use: Deprecated
Tag_ABI_optimization_goals: Aggressive Speed
Tag_CPU_unaligned_access: v6
Tag_ABI_FP_16bit_format: IEEE 754
Tag_DIV_use: Not allowed
Tag_Virtualization_use: TrustZone
It would seem that the only libs this file depends on are the following:
Code:
0x00000001 (NEEDED) Shared library: [libtinyalsa.so]
0x00000001 (NEEDED) Shared library: [libmedia.so]
0x00000001 (NEEDED) Shared library: [libutils.so]
0x00000001 (NEEDED) Shared library: [libbinder.so]
0x00000001 (NEEDED) Shared library: [liblog.so]
0x00000001 (NEEDED) Shared library: [libstdc++.so]
0x00000001 (NEEDED) Shared library: [libm.so]
0x00000001 (NEEDED) Shared library: [libc.so]
0x00000001 (NEEDED) Shared library: [libdl.so]
So now we need the right version of these in /system/lib/ and it might work.
EDIT:
I also ran this command on gocsdk:
Code:
0x00000001 (NEEDED) Shared library: [libbinder.so]
0x00000001 (NEEDED) Shared library: [libmedia.so]
0x00000001 (NEEDED) Shared library: [libutils.so]
0x00000001 (NEEDED) Shared library: [liblog.so]
0x00000001 (NEEDED) Shared library: [libstdc++.so]
0x00000001 (NEEDED) Shared library: [libm.so]
0x00000001 (NEEDED) Shared library: [libc.so]
0x00000001 (NEEDED) Shared library: [libdl.so]
So it seems that libtinyalsa.so might be our missing file!
sdsdk needs it and gocsdk doesn't.
Edit 2:
Okay I've extracted the missing files from a recent android 6 ROM which had working BT on my unit. I've created an archive with all the files that I think are missing in android 8 in their respective folders. Copy and paste to the right folders on your unit and set permissions to 777 for each file (you'll need a root browser for this). I've hadn't had time to test it for myself but this will hopefully fix this mess.
Edit 3:
Well it seems that the missing files I gathered up aren't complete yet. I can comfirm that 'sdsdk' is indeed crashing because it is missing dependencies. Executing the file from terminal is generating this error message.
"CANNOT LINK EXECUTABLE 'sdsdk' has text relocations"
Sadly I am currently at a loss getting the name and paths out of 'sdsdk' with readelf.
Edit 4:
After more reading it would seem that google disabled text relocations for applications running in userland. So this error seems logical since I was running the terminal in userland .
Hello Switchboy, i did put the files in the locations as showed in youre zip file.
It does not work on my HU.
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
switchboy said:
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
Click to expand...
Click to collapse
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.
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.
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/hal/structaudio__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
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.
@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).
marchnz said:
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.
Click to expand...
Click to collapse
I am very interested in this supplier!
jimimatthews said:
@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).
Click to expand...
Click to collapse
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.
jimimatthews said:
I am very interested in this supplier!
Click to expand...
Click to collapse
Check the md725 module 1 and 2 swap thread
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?