[Shanling]

At this time we do not have any info about new firmware from software team.

We do not recommend connecting multiple headsets to UP5 at the same time, it can damage the audio circuit.

 

[Jeff Graw]

At this time we do not have any info about new firmware from software team.

Words cannot express how lame it is that every version of the firmware has major issues, the latest firmware has a huge issue with charging, and you have no plans to fix it. Unless you guys are struggling to remain afloat and literally don't have the resources, this comes across as very anti-consumer and immoral. I will attempt to cancel my order.

 

[Shanling]

For the charging issue, it's glitch showing on very small amount of units and seems our engineering team wasn't able to replicate it properly. Their only recommendation at this time, if you encounter this issue, is to turn on/off charging few times, it should be able to reset the charging circuit and get it working properly.

 

[Jeff Graw]

For the charging issue, it's glitch showing on very small amount of units and seems our engineering team wasn't able to replicate it properly. Their only recommendation at this time, if you encounter this issue, is to turn on/off charging few times, it should be able to reset the charging circuit and get it working properly.

OK. Leaves a bit of a funny taste given the number of people who have came forward with the issue, but is a much better explanation. So we're on the same page, if you do get reproduction steps the software team will fix it and release a new firmware? Development is paused for the moment due to lack of reproducible issues, but isn't EOL?

 

[HiFiLVL]

I support. Your policy leads to the fact that we do not want to buy your products. You make interesting devices, but as a result they seem unfinished and when we are waiting for the firmware, you say that the firmware is not planned and you have no information. Will not work. If you don't meet customer needs, you don't grow. But your competitors are evolving. Therefore, it is in your interest to listen to complaints and make the necessary corrections to the product.

 

[rlw6534]

I'm pretty sure Shanling would release new firmware if there is something to fix that can be identified and it isn't a hardware issue. Perhaps this is simply a communication breakdown.

 

[Jeff Graw]

Assuming the UP5 software support isn't EOL, and the software team just doesn't feel they have any remaining tasks for the UP5 or continuing to hunt down charging bug, there are still two huge usability issues they can work on: MQA only working when the volume is maxed, and not being able to shut off BT while connected through USB.

Speaking as a developer myself, I'm incredibly skeptical that either issue is a hardware limitation. Regarding connecting BT while USB is off, it makes perfect sense that the UP5 is built in such a way that the QCC5120 cannot be bypassed. However, the idea that the QCC5120 chip does not have some mode that disables pairing or transmission is baffling and strikes me as incredibly unlikely.

The MQA max volume requirement just comes across as weird. When I heard of that my first thought was "this must be something someone haphazardly hacked together instead of implementing a proper solution that would require actual refactoring."

The overall impression is that the code is a mess of spaghetti and that the software team is either very lackluster, or just as likely, they are struggling with an extremely difficult legacy codebase and management refuses to sign off on necessary refactoring and/or rewrites, pushing developers to bolt on features, implement band-aid fixes, and accumulate technical debt.

In either case, I would bet my life savings that there are serious software issues at play, far and above the usual problems developers face (perfectly good code doesn't really exist, but there are different degrees of evil).

 

[Andrew_WOT]

With such prejudiced negativity, why even bother getting one, you know you will regret it.

 

[rlw6534]

The MQA max volume requirement just comes across as weird. When I heard of that my first thought was "this must be something someone haphazardly hacked together instead of implementing a proper solution that would require actual refactoring."

The reason the source volume has to be set at the maximum is because digital volume control reduces bit-depth when lowering volume and the stream is no longer bit-perfect. MQA needs all of the original bits to function and decode. This is not an UP5 specific problem.

 

[ClieOS]

I am one of the earliest UP5 owner. The original firmware did left a lot to be desired, but I am happy to say that most of the issues were fixed on subsequent firmware update and I have no problem with it since then.

 

[Jeff Graw]

The reason the source volume has to be set at the maximum is because digital volume control reduces bit-depth when lowering volume and the stream is no longer bit-perfect. MQA needs all of the original bits to function and decode. This is not an UP5 specific problem.

I stand corrected.

EDIT: Well, I can see it going either way. It's an order of operations issue whether you unfold MQA prior to volume correction or after. Question is where the volume correction and unfolding is being done. If it's in the same hardware, then there's a good chance it's a software issue, and my hopefully safe assumption is that both operations happen on the DAC. Going forward with that assumption, if the DAC chip is inflexible to the point that MQA must happen after volume correction, then MQA was "bolted on haphazardly" at a hardware level. Otherwise, the same is true at the software level. Later seems more likely given that you don't often see intentional hardware design flaws.

 

[Nealz]

Hello guys, so I just got a brand new Shanling UP5. While using the balanced 4.4 mm port with my Tri i3 Pro I am getting only 3 hours worth of battery life from a single charge. My Up5 already came with the latest firmware out of the box. Is this normal? Cause I have read most reviewers are getting 8 to 9 hours worth of battery life from the balanced port. I even used to get 7 hours of battery life using the balanced port on my old BTR 5.

 

[rlw6534]

I stand corrected.

EDIT: Well, I can see it going either way. It's an order of operations issue whether you unfold MQA prior to volume correction or after. Question is where the volume correction and unfolding is being done. If it's in the same hardware, then there's a good chance it's a software issue, and my hopefully safe assumption is that both operations happen on the DAC. Going forward with that assumption, if the DAC chip is inflexible to the point that MQA must happen after volume correction, then MQA was "bolted on haphazardly" at a hardware level. Otherwise, the same is true at the software level. Later seems more likely given that you don't often see intentional hardware design flaws.

I agree with you that it would be nice to fix this, if possible. I was simply trying to explain the "why". There are a few variables (UAC mode, exclusive USB access) that may also play in to this from a technical perspective. It seems to be problem with devices that have separate volume controls (and don't use UAC volume control).

 

[Shanling]

Hello guys, so I just got a brand new Shanling UP5. While using the balanced 4.4 mm port with my Tri i3 Pro I am getting only 3 hours worth of battery life from a single charge. My Up5 already came with the latest firmware out of the box. Is this normal? Cause I have read most reviewers are getting 8 to 9 hours worth of battery life from the balanced port. I even used to get 7 hours of battery life using the balanced port on my old BTR 5.

3 hours from full charge to device completely turning off? Did you please test it on single-ended output?

I agree with you that it would be nice to fix this, if possible. I was simply trying to explain the "why". There are a few variables (UAC mode, exclusive USB access) that may also play in to this from a technical perspective. It seems to be problem with devices that have separate volume controls (and don't use UAC volume control).

MQA implementation on UP5 is bit different from our other devices, UP5 works in closer cooperation with the unfolding capabilities of the Tidal app to reach the MQA 16x. Current setup is confirmed by the MQA and we will not be adjusting it.

 

[caboodle19]

excessive battery drain on my AP80 in usb dac mode. No issue in blue tooth mode and usb mode in my hip dac. Any fix with future firmware?