[Shanling]

2nd question is when I connect the phone using USB c to c cable to up5, it just display 96k. (is this phone limitations?)

Thanks.

This depends on the app and phone capabilities.
Running something like UAPP or HiBy app, you should get the Android to play correctly the original sample rate.

What am I doing wrong in trying to update to the newest firmware? Followed the directions, computer recognized UP5, go to the upgrade.bat file and this is what shows up. Any thoughts or ideas?

From the message in the software it seems there was some issue with the other files? Maybe the zip didn't open fully or you moved some of the files? Not sure.

I don't know if it is a problem of UAPP app or of the update but MQA does not work anymore with this app. Works perfectly with TIDAL.

We test MQA just for use with Tidal. UAPP might need to adjust something for UP5?

 

[littlenezt]

That's awesome wish that would have happened with mine. I got it resolved with the help of all you awesome folks, but for whatever reason, it kept telling me FAIL! haha, But, all is well now as far as firmware goes. Is the beep gone? I haven't gotten that far yet. Thanks again everyone

still cant confirm about the low battery beep yet, my up5 still around 80% of battery

 

[YanaMJ]

This depends on the app and phone capabilities.
Running something like UAPP or HiBy app, you should get the Android to play correctly the original sample rate.



From the message in the software it seems there was some issue with the other files? Maybe the zip didn't open fully or you moved some of the files? Not sure.



We test MQA just for use with Tidal. UAPP might need to adjust something for UP5?

I don't know if UAPP might need to adjust something but it worked fine before the new firmware...

 

[littlenezt]

still cant confirm about the low battery beep yet, my up5 still around 80% of battery

my UP5 finally beep just once when the battery percentage drops from 40% to 20%, seems to be no longer beeping for every 30seconds.

also i noticed some strange behavior, the battery indicator seems to be kinda inconsistent? when my up5 beep once, the battery indicated low (20%), while the UP5 still ON, i restart my phone, when my phone reconnects the UP5 battery goes back to 40% and 5 minutes later it drops again to 20% and beep once more.

i guess the battery need full cycle after firmware flashing?

well atleast the up5 no longer beeping like crazy for every 30s i guess

edit:
now lets see how much longer before the device turn itself off from 20%, previously my UP5 can last for 2 more hours while beeping for every 30s before the device turn off by itself.

another edit:
my up5 from 20% to finally shutting itself off only last for around 20minutes

 

[Sixgun1]

Great info littlenezt, thank you for the heads up

 

[YanaMJ]

Now my UP5 that was working well with UAPP does not work well anymore with UAPP and with tidal sound stops after few seconds of few minutes and as I said previously MQA does not work anymore with UAPP... Really sad... Never used Tidal before as UAPP was great.

 

[rlw6534]

Now my UP5 that was working well with UAPP does not work well anymore with UAPP and with tidal sound stops after few seconds of few minutes and as I said previously MQA does not work anymore with UAPP... Really sad... Never used Tidal before as UAPP was great.

Same issue here with USB and UAPP (no MQA/OFS).

 

[YanaMJ]

Same issue here with USB and UAPP (no MQA/OFS).

I've found the problem. Look at you parameters of quality. It was changed and not on MQA anymore.

Now it works again.

 

[rlw6534]

I've found the problem. Look at you parameters of quality. It was changed and not on MQA anymore.

Now it works again.

In UAPP? Where?

 

[YanaMJ]

In UAPP? Where?

Yes in UAPP

 

[rlw6534]

Yes in UAPP

Mine was a different problem, but I figured it out. I needed to turn up the device volume (not UP5) to 100% before MQA would work. I don't recall having to do that before.

 

[YanaMJ]

Mine was a different problem, but I figured it out. I needed to turn up the device volume (not UP5) to 100% before MQA would work. I don't recall having to do that before.

If you read the previous pages of this thread you'll see we have to do that even with the 1st versions of the firmware. Lots of people thought MQA didn't work because of this.

 

[rlw6534]

If you read the previous pages of this thread you'll see we have to do that even with the 1st versions of the firmware. Lots of people thought MQA didn't work because of this.

Yeah, I missed that. I don't usually use UAPP with the UP5 (USB) but after your initial report I tried it to see what would happen for me. Rookie mistake...

Is this something specific to the UP5? I really don't remember having to do this with my Zen DAC. Maybe I'm confusing with iPhone/iPad.

 

[Shanling]

Yeah, I missed that. I don't usually use UAPP with the UP5 (USB) but after your initial report I tried it to see what would happen for me. Rookie mistake...

Is this something specific to the UP5? I really don't remember having to do this with my Zen DAC. Maybe I'm confusing with iPhone/iPad.

Yes, it's bit unique for UP5. You always have to have system volume at 100% to get MQA playback. Both on smartphones and Windows.

 

[504246]

Latest firmware installed.
I still encounter volume issues with abnormal variations, as if I were switching from low gain to high gain when, for example, I take the device out of standby.
It happened to me yesterday in bluetooth mode with my OnePlus Nord CE, which works perfectly with my other wireless devices (TWS, Q1).
I contacted my local dealer support.