M0 Pro is using 5-pin TRRRS output, which we configured to be both compatible with single-ended and balanced headphones.
You can use M0 Pro in balanced mode with the 4.4mm adapter we sell, you can make your own adapter or you can re-wire your headphones using the 5-pin TRRRS 3.5mm connector.
It's not designed for the old 4-pin TRRS balanced 3.5mm.
I wouldn't call the adapter proprietary, the 5-pin 3.5mm TRRRS jacks are normally available on Aliexpress, so anybody who wants to can make one.
So, do you have any iea why it is not working with the Fiio M5 but work with androids... I really really really need you or somebody at the company to test out ANY b&w headphones through their c2c cable... that should not be impossible... but what is impossible is to buy this product blindly. B&W is a fairly big headphone company... is there not anybody that knows this ?
I bought M0 Pro with firmware 1.4. I downloaded 1.5 from the official website, unpacked it according to the instructions and placed the update.bin file into the root of the memory card, selected update through the menu, and now I got constantly reboot with the message Update Failed(((
I looked at the memory card and found the firmware_v0.tar archive had appeared. This archive contains a 'recovery-update' folder, and it already contains 'nand' folder with a bunch of archives. I pulled these archive files out to the root of the memory card, and the firmware update has been done.
after some time with my M0 pro, i am pleased. it seems good build quality, and functions without problems.
Its small size was the reason i wanted it, and it's really nice to have around my office for example when working or relaxing.
If I buy another DAP, i will take a look at shanling again! really happy with this one.
As we told you before on June 13th, please contact your seller for warranty. Hardware defects can happen on the units, that's why there is warranty. There is nothing we can do about that with a software update.
I'm not sure what do you mean? We told you back in June that you should go for warranty on this issue, we accept there might be a hardware issue on your unit.
According to your posts, you got the unit in March this year, so well within its standard warranty period.
Since I am not the only one with the same issue I doubt it's my unit that's to blame. I was hoping you'd asked a couple tech's to look into it and they'd found the flaw and had added a fix into the next firmware update. That's what most western companies do. That way buyers might never know there was a problem.
Since I am not the only one with the same issue I doubt it's my unit that's to blame. I was hoping you'd asked a couple tech's to look into it and they'd found the flaw and had added a fix into the next firmware update. That's what most western companies do. That way buyers might never know there was a problem.
Some potentiometers can be less accurate or even faulty. It's a simple hardware question. And as much as we focus on it in our QC, these situations can happen.
Which is why we offer a warranty on our devices and it covers this problem.
Have any question about our players? Just PM me or send me email.
Stay updated on Shanling at their sponsor profile on Head-Fi.
Some potentiometers can be less accurate or even faulty. It's a simple hardware question. And as much as we focus on it in our QC, these situations can happen.
Which is why we offer a warranty on our devices and it covers this problem
Mmm then why does it only happen in the Hiby music app all other music player apps are fine no issue. Surely if it was hardware it would happen in them too
If I use the M0 Pro as a source (via USB) for something like a BTR7, do the functions where you can double press the BTR7's volume buttons to play previous or next track work, or is that for bluetooth only?
Just picked an m0 pro up for fitness use with LDAC earbuds. Got the clip but would love a watch strap band or case with band mounts. Anyone seen one of these for this model?
Today the button stopped reacting to one short click (turn screen on/off) but it's working fine with a long hold (power on/off). I'll just RMA it, but I'm wondering how is it possible that short click doesn't work but long hold does if this was a HW problem?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.