HiBy R6 III (Gen 3) Android digital audio player, Dual ES9038Q2M, Class A / AB amplification switch, Snapdragon 665, Open Android 12 OS, DSD512 / PCM768

[dharmasteve]

It's not a bug in the firmware, because as pointed out, if you factory reset it, the issue goes away. A bugged firmware won't do that. It is an issue with the process of updating from one firmware version to the next, that may be "bugged", however, as pointed out, this does not happen to all users, only to some users under specific conditions, specific conditions which unfortunately we have not been able to isolate so far. There are many variables when updating an existing Android installation to a new version.

Pride has nothing to do with this. I am immensely proud of the software on our Android devices, e.g. https://www.facebook.com/hibycom/po...9cJaypQ8CeV1YkJs6m3MAo3xRZpZYvr1V3kejtZA8VLal .

That doesn't mean that we can't be left holding the bag on a bizarre problem between firmware updates. We certainly hope to find an easy fix that can be applied in the next firmware update, but all we know right *now* is that a factory reset will fix the issue, because the new firmware is not bugged, only the code for updating the firmware may be. I mean, imagine how puzzling this is:

1. The previous firmware worked fine.
2. The update also works fine, in the sense that the new firmware has been installed. It has been installed completely, in the sense that if you factory reset your device, everything works.
3. BUT in the meantime something is screwed up, even though everything has been put in place, according to the Android OS.

Anyway--can you try another thing for me? The settings app has application data. Can you try going to settings->apps->settings (the app) and clear data on the settings app?

So followed your advice and did factory reset. Switched off after having done it to use later and, the little turquoise light is on and won't go off and I can't boot. That's what the factory reset has done. What do I do?

 

[anli]

It is 0.5 ohm in SE and 1 ohm in balanced.

Just for record. Have got the player. On SE output with Vout = 460mV, f = 1KHz, Rload = 27 Ohm, AB have got Zout = 0.71 Ohm. Probably, 0,5 Ohm is for class A.

 

[Joe Bloggs]

So followed your advice and did factory reset. Switched off after having done it to use later and, the little turquoise light is on and won't go off and I can't boot. That's what the factory reset has done. What do I do?

Hold next button and then also the power button for 15 seconds to force reboot. If that doesn't help, you may hold previous button and then also the power button to power on the device into recovery mode. When you see the resting android robot figure, hold the power button and then press the previous button to enter the menu. From there you can perform a further factory reset on your device. If the device is still unstable after a factory reset, that should be a hardware fault and you should return the unit to us for repair or exchange, sorry for the inconvenience.

 

[dharmasteve]

Hold next button and then also the power button for 15 seconds to force reboot. If that doesn't help, you may hold previous button and then also the power button to power on the device into recovery mode. When you see the resting android robot figure, hold the power button and then press the previous button to enter the menu. From there you can perform a further factory reset on your device. If the device is still unstable after a factory reset, that should be a hardware fault and you should return the unit to us for repair or exchange, sorry for the inconvenience.

I solved the problem myself. I am a great fan of the HiBy R6 III hardware, as is clear by my comments. The FW needs a kick up the ass. You are deluded if you think it is up to anyone else besides HiBy has to get everything about FW upgrades perfect. I criticised HiBy generically not you....the Ego is your adversary sometimes. Thank you anyway.

 

[ticoss]

The "lost time" problem is present with my device and the last firmware (v1.30). I don't think that I've had it before..
Can you pass the information on to the development teams?
Thanks

​

Firmware v1.31 solve my time problem.
As I had the little problem with the MSEB title, I've done a factory reset. Well.., it takes time (install softwares, rebuild library etc..) but at least, system is completely clean now

 

[Joe Bloggs]

I solved the problem myself. I am a great fan of the HiBy R6 III hardware, as is clear by my comments. The FW needs a kick up the ass. You are deluded if you think it is up to anyone else besides HiBy has to get everything about FW upgrades perfect. I criticised HiBy generically not you....the Ego is your adversary sometimes. Thank you anyway.

Well, everyone thought that it is up to us to fix TIDAL not working on HiBy players (because they screwed up coding for Android 10- when the app purportedly supports them--and any old Android should be able to play FLACs), until TIDAL fixed it in the latest beta. Everyone thinks that the FC6 was buggy with Snapdragon 8 smartphones, not the other way around--still do, because we "fixed" it on our end by downgrading USB audio protocol to discard asyc timing signals which could otherwise be used to reduce jitter over the USB connection, which smartphones with those chipsets don't grok properly.

For another example, I suppose you understand that one would be barking up the wrong tree, if one asked HiBy to make Android firmware updates reversible? Or firmware downgrades possible? (this is actually relevant, as this makes troubleshooting issues with a firmware update process that much more difficult. What you want to do, is get a hold of a device suffering the naming issue, and reverse the update to see what special characteristic the Android install may have had before the update.)

There are many things about the firmware I would like to see work on, this naming issue isn't one that the team has reported being able to work on so far (actually, as far as I know, this issue cropped up *because* they were trying to add / correct names in this version.). Realistically I would instruct them to work on things that they can work on, if that were even my job. Pride or humility or desperation do not make people dream up solutions to a problem.

I'm not putting my foot down on this one because it has not yet been proven that the fault lies outside our responsibility, but, unlike what you think, such things are technically entirely possible. That we would be held accountable for it nevertheless, and would have to find a way to "fix" it, if possibly by no better means than to freeze large swathes of the firmware from future updates indefinitely (especially code related to system settings names, as, as far as I know, this issue cropped up in this update because they were actually trying to change / add names), is a story for another day.

Anyway, how did you solve the problem you mentioned with the device after the factory reset?

 

[dharmasteve]

Well, everyone thought that it is up to us to fix TIDAL not working on HiBy players (because they screwed up coding for Android 10- when the app purportedly supports them--and any old Android should be able to play FLACs), until TIDAL fixed it in the latest beta. Everyone thinks that the FC6 was buggy with Snapdragon 8 smartphones, not the other way around--still do, because we "fixed" it on our end by downgrading USB audio protocol to discard asyc timing signals which could otherwise be used to reduce jitter over the USB connection, which smartphones with those chipsets don't grok properly.

For another example, I suppose you understand that one would be barking up the wrong tree, if one asked HiBy to make Android firmware updates reversible? Or firmware downgrades possible? (this is actually relevant, as this makes troubleshooting issues with a firmware update process that much more difficult. What you want to do, is get a hold of a device suffering the naming issue, and reverse the update to see what special characteristic the Android install may have had before the update.)

There are many things about the firmware I would like to see work on, this naming issue isn't one that the team has reported being able to work on so far (actually, as far as I know, this issue cropped up *because* they were trying to add / correct names in this version.). Realistically I would instruct them to work on things that they can work on, if that were even my job. Pride or humility or desperation do not make people dream up solutions to a problem.

I'm not putting my foot down on this one because it has not yet been proven that the fault lies outside our responsibility, but, unlike what you think, such things are technically entirely possible. That we would be held accountable for it nevertheless, and would have to find a way to "fix" it, if possibly by no better means than to freeze large swathes of the firmware from future updates indefinitely (especially code related to system settings names, as, as far as I know, this issue cropped up in this update because they were actually trying to change / add names), is a story for another day.

Anyway, how did you solve the problem you mentioned with the device after the factory reset?

I did next track, power button. Previous track, power button did not bring the options screen.

As hard as it seems, like any manufacturer, retailer etc, it's their, HiBy, (not you personally) problem to fix issues. We pay the money £500, HiBy solves the issues. That is the ethical, moral side of business. I understand there are glitches, but it's where responsibility to deal with the problems lie. HiBy software issues are for HiBy to sort. I understand it is difficult, but that's the ethical side of business. I bought a Tempotec V6 DAP directly from Tempotec, backing them on Kickstarter, and immediately the 4.4 mm socket would not change to 3.5mm when I put a 3.5mm jack in. After a short dialogue they stopped communication and I have an unsellable DAP. Ethics and morals are all good businesses have.....so we depend on you (the business), but not all businesses' have good ethics.

 

[ongbenghui]

Firmware v1.31 solve my time problem.
As I had the little problem with the MSEB title, I've done a factory reset. Well.., it takes time (install software, rebuild library etc..) but at least, system is completely clean now

Did the factory reset fix the MSEB title problem ?

 

[ticoss]

Did the factory reset fix the MSEB title problem ?

Yes

 

[anli]

@Joe Bloggs , are there some public details about system-wide PEQ? On the go? Month? Months? Years?

 

[Simon Patten]

@Joe Bloggs , are there some public details about system-wide PEQ? On the go? Month? Months? Years?

Yes, I need this too. I love music but have hearing issues, having to set up EQ for each app (Hiby, UAPP, Amazon, etc.) is a real pain.

 

[rahulmunjal]

@Joe Bloggs
Hi Guys, I am facing an unique issue.

After reading all the good reviews, recently purchased the Hiby R6 gen3. Out of the box it was at FW 1.2; updated it immediately and started playing music after transferring mp3/flac files on an external micro SD card and also to internal memory.
I am mostly using Bluetooth speakers/headphones because of the convenience and I understand that while Bluetooth streaming all the internal circuitry is by passed. So what is happening is - while the song is playing, lets say at any XYZ volume, suddenly for a fraction of a second the volume dips to about 10 and then comes back to normal to what it was playing at.
So example I am at any volume 70/60/50 etc. it will dip to about 10 (barely audible, but still can hear music) for half a second and then come back to what it was originally set at. This happens once in 30 minutes, not at fixed intervals but still happens!!!
I am presently at FW 1.31 and have done all the factory reset and all those procedures but still this problem persists.
I have tried various different speakers and headphones, I have tried different SD Cards and also internal memory and also tried spotify/youtube but still this happen.
If I use wired headphones or speakers then this doesnt happen.

Is any one facing similar issue? Have you found a fix? I have also reported this to Faye at HIBY headquarters.

Please let me know of any solutions, if you have any.

Cheers
Rahul

 

[Electrocrytic]

@Joe Bloggs
Hi Guys, I am facing an unique issue.

After reading all the good reviews, recently purchased the Hiby R6 gen3. Out of the box it was at FW 1.2; updated it immediately and started playing music after transferring mp3/flac files on an external micro SD card and also to internal memory.
I am mostly using Bluetooth speakers/headphones because of the convenience and I understand that while Bluetooth streaming all the internal circuitry is by passed. So what is happening is - while the song is playing, lets say at any XYZ volume, suddenly for a fraction of a second the volume dips to about 10 and then comes back to normal to what it was playing at.
So example I am at any volume 70/60/50 etc. it will dip to about 10 (barely audible, but still can hear music) for half a second and then come back to what it was originally set at. This happens once in 30 minutes, not at fixed intervals but still happens!!!
I am presently at FW 1.31 and have done all the factory reset and all those procedures but still this problem persists.
I have tried various different speakers and headphones, I have tried different SD Cards and also internal memory and also tried spotify/youtube but still this happen.
If I use wired headphones or speakers then this doesnt happen.

Is any one facing similar issue? Have you found a fix? I have also reported this to Faye at HIBY headquarters.

Please let me know of any solutions, if you have any.

Cheers
Rahul

Sounds like a notification from another app. Don't know what you have installed or are playing music from but you can disable notifications for specific apps in settings/apps. Some music playback apps have an option not to interupt (lower the volume) with notifications.

 

[rahulmunjal]

@Electrocrytic
No, there are no notification.
It happens when I am offline as well.
I am using Hiby music app and spotify.

 

[Joe Bloggs]

Yes, I need this too. I love music but have hearing issues, having to set up EQ for each app (Hiby, UAPP, Amazon, etc.) is a real pain.

Is your hearing issue different per channel? I think per-channel PEQ would be a ways off, you may be better off putting together a convolver for your use with my help. Pm me