[Bada Software and Hacking General] hunktb:
[MENTION=1030585]adfree[/MENTION]

Tools versions: QXDM Professional 03.12.714 (Production Build) and QPST 2.7 Build 323

Do you have a link to I download HWTP and PSAS tools?

audio/microphone: I think Rebellos answer about that was clear enough http://xdaforums.com/showpost.php?p=41284946&postcount=117

I have been investigating bluetooth in S8530 as it seemed to me something related with configuration/firmware versus S8500 and I thought it didn't need coding, but to dig into audio/microphone needs a lot of coding and it is far for my current capabilities. I could just try to investigate, for example, look to QXDM logs when starting / ending a record with bada sound recorder, but these logs say nothing to me :) And this is simple: audio/mic in calls deals with codecs... reverse engineering all that from logs has to be a hell. It is incredible to me how Rebellos has managed to do everything already done.

MSG [00000/03] Legacy/Error 03:28:07.391 QMochaSound.c 00899 qMochaSndIPC : eventId = [2], bufSize = [56]
MSG [00000/03] Legacy/Error 03:28:07.391 QMochaSound.c 00619 qMochaSetMute:devType = [1]
MSG [00000/03] Legacy/Error 03:28:07.391 QMochaSound.c 00620 qMochaSetMute:inDevMute = [0]
MSG [00000/03] Legacy/Error 03:28:07.391 QMochaSound.c 00621 qMochaSetMute:outDevMute = [1]
MSG [00000/03] Legacy/Error 03:28:07.391 QMochaSound.c 00622 qMochaSetMute:sndType = [16]
MSG [00000/03] Legacy/Error 03:28:07.391 QMochaSound.c 00863 qMochaSetVolume : sndType = [16]
MSG [00000/03] Legacy/Error 03:28:07.391 QMochaSound.c 00864 qMochaSetVolume : Volume = [7]
MSG [00000/03] Legacy/Error 03:28:07.391 QMochaSound.c 00259 qMochaAgcOff : QDSP CLK OFF, do nothing
MSG [00000/03] Legacy/Error 03:28:07.392 QMochaSound.c 00899 qMochaSndIPC : eventId = [1], bufSize = [56]
MSG [00000/03] Legacy/Error 03:28:07.392 QMochaSound.c 00619 qMochaSetMute:devType = [1]
MSG [00000/03] Legacy/Error 03:28:07.392 QMochaSound.c 00620 qMochaSetMute:inDevMute = [0]
MSG [00000/03] Legacy/Error 03:28:07.392 QMochaSound.c 00621 qMochaSetMute:outDevMute = [1]
MSG [00000/03] Legacy/Error 03:28:07.392 QMochaSound.c 00622 qMochaSetMute:sndType = [16]
...

For example this line seems something more simple and unrelated to others, maybe reading temperature to avoid overheating while charging (95 maybe 95 º F = 35 ºC ?), as far as I know a function not yet implemented in badadroid.... but to deal with that will need coding and to understand current badadroid implementation in code, again out of my reach.

MSG [00000/03] Legacy/Error 03:28:04.291 charging.c 00145 temp_state: 0, pre_state= 0, charging temperature = 95

[MENTION=1767826]Rebellos[/MENTION]: thanks, I have located file manager in badadroid source and I understand badadroid uses that

https://github.com/KB-JetDroid/bada-modemril/blob/master/libmocha-ipc/mocha-ipc/fm.c

But my question is if the same filesystem can be accessed in other way with other tools:

QPST EFS Explorer screenshots in this thread, posts 15, 17, 18

shows similar filesystem structure/info as "Stune" utility does (I include screenshots; it is a S8500 with TurkoCFW and Stune says S8530)

Maybe these tools are implementing the same badadroid does to show this filesystem...

And maybe with these tools we can search for another .hcd or .hex file bada uses for bluetooth.

Just to share, as I see adfree is a windows user and most of the info is "windows based", I include lsusb on S8500 (first lines) from my ubuntu 13:04. It is funny to see it says "GT-I9100 Phone [Galaxy S II], GT-P7500 [Galaxy Tab 10.1]" :)

AP USB Mode Enabled (AP = Application Processor?)

lsusb -v -s 002:007

Bus 002 Device 007: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II], GT-P7500 [Galaxy Tab 10.1]
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize0 64
idVendor 0x04e8 Samsung Electronics Co., Ltd
idProduct 0x6860 GT-I9100 Phone [Galaxy S II], GT-P7500 [Galaxy Tab 10.1]
bcdDevice 4.00
iManufacturer 1 Samsung Electronics
iProduct 2 Samsung Wave(GT-S8500)
iSerial 0
bNumConfigurations 1
...

CP USB Mode Enabled (CP = Call / Cellular Processor?)

lsusb -v -s 005:004

Bus 005 Device 004: ID 05c6:9002 Qualcomm, Inc. Gobi Wireless Modem
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x05c6 Qualcomm, Inc.
idProduct 0x9002 Gobi Wireless Modem
bcdDevice 0.00
iManufacturer 3
iProduct 2
iSerial 0
bNumConfigurations 1
...

Edit 1: include lsusb from badadroid... it says Nexus S :)

lsusb -v -s 002:005

Bus 002 Device 005: ID 18d1:4e22 Google Inc. Nexus S (debug)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x18d1 Google Inc.
idProduct 0x4e22 Nexus S (debug)
bcdDevice 2.31
iManufacturer 2 samsung
iProduct 3 GT-S8500
iSerial 4 0000045600000123
bNumConfigurations 1
...