[Wiped89]

I am having the same issue. Were you able to solve it?

Yes I actually was. I just switched off equalizer entirely and went with MSEB only. Put MSEB (in the excessive setting) to +20 bright, +32 bass depth and +32 bass punch and it sounds great now

Ocassionally I put Equaliser back on but only a touch of extra bass and treble and keep pre amp at -2

 

[Joe Bloggs]

Thats what I mean. There is seemingly no change before and after the update. So what is point 3 of the brief on the update? It makes me wonder whether the update is just a placebo.

I hope some real changes and improvements are included. Can we have more info?

It's a top level menu item in settings right under Display. If anyone is having trouble finding it I have to wonder if their firmware update actually took, or if it failed as some reported.

 

[Joe Bloggs]

The latest update keeps disconnecting bluetooth, then reconnecting, then disconnecting on an endless cycle.

The error message "com.android.bluetooth keeps stopping" giving you the options to "open app again" or "close" app. Clicking either does nothing to stop this endless cycle.

@Joe Bloggs please advise how to solve this issue. Thanks!

Can you try the following:
1. Tap on Settings->System->About Device->Build number several times until a toast comes up saying "you're now a developer!"
2. Go up to ->System and into the new "Developer options" menu
3. Scroll down and turn on "Disable absolute volume"
4. Tap on Bluetooth Audio Codec and choose "SBC".

If these steps solve the bluetooth crash problem, you may try re-enabling the two features one by one (absolute volume and ability to switch between high level bluetooth codecs) to see if they now work.

 

[Joe Bloggs]

The issue with TIDAL and Qobuz not playing in native frequencies actually stems from the fact that a whitelist for DTA-enabled apps has been added in this version (and in the R6 pro RTM firmware), which however did not include TIDAL and Qobuz because the testing team were not aware of the latest developments in the apps which enabled native frequency output at various frequencies recently.

The whitelist itself was enacted because it was found that apps depending on DTA (whether the app is actually capable of output at multiple sample frequencies or not) were prone to problems in bluetooth and usb audio output. Thus the purpose of the whitelist is to list out apps that can actually output at multiple sample rates under DTA.

I pointed out that that would not solve said bluetooth and usb output problems for those whitelisted apps for those who do actually use those devices, but is on the other hand unnecessary for those who do not. My alternative proposal is a simple DTA master switch in settings (which may take a restart to take effect).

What are your thoughts on the matter?

 

[powersfineart]

The issue with TIDAL and Qobuz not playing in native frequencies actually stems from the fact that a whitelist for DTA-enabled apps has been added in this version (and in the R6 pro RTM firmware), which however did not include TIDAL and Qobuz because the testing team were not aware of the latest developments in the apps which enabled native frequency output at various frequencies recently.

The whitelist itself was enacted because it was found that apps depending on DTA (whether the app is actually capable of output at multiple sample frequencies or not) were prone to problems in bluetooth and usb audio output. Thus the purpose of the whitelist is to list out apps that can actually output at multiple sample rates under DTA.

I pointed out that that would not solve said bluetooth and usb output problems for those whitelisted apps for those who do actually use those devices, but is on the other hand unnecessary for those who do not. My alternative proposal is a simple DTA master switch in settings (which may take a restart to take effect).

What are your thoughts on the matter?

The DTA master switch idea is way better than trying to maintain a whitelist of possible apps that would use it. The master switch would cover more use-case scenarios as well.

At the present time (after the current 8.1 OTA update), Hiby can’t really market the R6 as playing native resolutions from Tidal and Qobuz if it doesn’t actually do it which negates the whole DTA benefit and essentially makes it the same as every other Android based audio player that supports streaming.

The DTA master switch is a great idea!

 

[Double C]

The issue with TIDAL and Qobuz not playing in native frequencies actually stems from the fact that a whitelist for DTA-enabled apps has been added in this version (and in the R6 pro RTM firmware), which however did not include TIDAL and Qobuz because the testing team were not aware of the latest developments in the apps which enabled native frequency output at various frequencies recently.

The whitelist itself was enacted because it was found that apps depending on DTA (whether the app is actually capable of output at multiple sample frequencies or not) were prone to problems in bluetooth and usb audio output. Thus the purpose of the whitelist is to list out apps that can actually output at multiple sample rates under DTA.

I pointed out that that would not solve said bluetooth and usb output problems for those whitelisted apps for those who do actually use those devices, but is on the other hand unnecessary for those who do not. My alternative proposal is a simple DTA master switch in settings (which may take a restart to take effect).

What are your thoughts on the matter?

My thoughts is that this is all so confusing....jajajajaj!

 

[KKFA]

It's a top level menu item in settings right under Display. If anyone is having trouble finding it I have to wonder if their firmware update actually took, or if it failed as some reported.

I had this before the update. If I remember correctly even when it was running 6.0. Thats why I am saying it looks the same. So at least for me the recent 1.1G update item 3 does not apply?

 

[Jujoe]

Can you try the following:
1. Tap on Settings->System->About Device->Build number several times until a toast comes up saying "you're now a developer!"
2. Go up to ->System and into the new "Developer options" menu
3. Scroll down and turn on "Disable absolute volume"
4. Tap on Bluetooth Audio Codec and choose "SBC".

If these steps solve the bluetooth crash problem, you may try re-enabling the two features one by one (absolute volume and ability to switch between high level bluetooth codecs) to see if they now work.

this does nothing

 

[Joe Bloggs]

this does nothing

I've asked them what to do next, hopefully they'll reply before holiday starts tomorrow. If not please try reverting by flashing the original r6 android 6 to 8 offline upgrade and let me know if you have any problems with the process...

 

[Joe Bloggs]

https://www.facebook.com/groups/HiByUsers/permalink/370269247100895/

Users are hereby cautioned to check the firmware's characteristics against their usage requirements before considering whether to take the OTA update...

 

[rjoudrey]

I've asked them what to do next, hopefully they'll reply before holiday starts tomorrow. If not please try reverting by flashing the original r6 android 6 to 8 offline upgrade and let me know if you have any problems with the process...

This will erase all user modification to software. Is there a way to back up data before flashing?

 

[Joe Bloggs]

This will erase all user modification to software. Is there a way to back up data before flashing?

Depends. What data would you like to back up?

 

[Jujoe]

I've asked them what to do next, hopefully they'll reply before holiday starts tomorrow. If not please try reverting by flashing the original r6 android 6 to 8 offline upgrade and let me know if you have any problems with the process...

I did the flash to 8 with no issues at all but still no bluetooth.

 

[Joe Bloggs]

I did the flash to 8 with no issues at all but still no bluetooth.

Excuse me?

 

[Jujoe]

I reset my r6 and then reflashed the fireware to oreo and still have the endless bluetooth cycle of android.bluetooth has stoped. I need the bluetooth for in car unfortunatly.