Originally Posted by ipgoogle
Thanks for reply, and you have type 2 from MD725 BT ?? And whats MCU type you have ??
It must be a type 1.
However, I just did new tests and realized that type 1/2 does not make sense anymore. We should call a driver compatible/incompatible module.
Here is my story. I have a MTCD PX3 radio which used to run Android 5.1.1/7.1.2 and bluetooth worked well. I upgraded coreboard to PX5 with Android 8 and BT was not working anymore. BT module was not detected and BT name/code were empty. Downgraded to Android 6 and BT worked again. Using getprop bt.md725.type I saw "2", indicating it is a type md725 type 2 module. I always want to come back Android 8, so I am constantly monitoring new versions of Oreo firmware. Yesterday I upgraded to Hal9K's Oreo version 3.1.1 with mcu HA 2.99, and noticed some changes. BT name/code were showing up and my phone was able to see CarKit BT. Unfortunately they cannot pair, so BT is still not working. Then I typed "getprop bt.md725.type" and I saw "1" this time. My module became type "1" !
In short md725 BT driver is getting better in new Oreo firmware, but is still incompatible with our old modules. Hope the driver will be improved and our module will be running in future.