[Dobrescu George]

   
we are really doing a lot of FiiO's work for them - please don't get me wrong, the community (including FiiO) appreciates your work. But it should be FiiO who should be tracking this and we in turn provide feedback on the firmware bugs.
 
I'm quite frustrated by these events and can't help but give my observations...but i'm going to stop for now and see what FiiO says.

 
As I see it - we're doing the good thing! 
 
A company usually collects this data via numerous crash reports - like MPC-HC and Xiaomi and Samsung and other companies do. Fiio will eventually implement a bug tracker with crash reports too - it's mostly a matter of time. 
 
We should offer support, those DAPs exist for one thing - sound. They still do it well in folder browsing from my understanding, and as long as EQ works, that's all I will ask for now. Because that is my usage pattern - well, this and DAC function. 
 
People are really alarmed, but the old FW was working well - new FW won't make it another device. 
 
This is the same as doing overclock. It's an endless race where we forget to do what we should - enjoy the thing. (I has recently given up on overclocking and has a good peace of mind, don't be aggressive - overclocking is some serious problem after a point) 

 

[karloil]

 
As I see it - we're doing the good thing!
 
We should offer support, those DAPs exist for one thing - sound.

 
IMO, SQ and UI should both go together. We are (Beta testers) offering support to FiiO - first by purchasing the product and now in OS bug feedback.

 

[headwhacker]

   
As I see it - we're doing the good thing! 
 
A company usually collects this data via numerous crash reports - like MPC-HC and Xiaomi and Samsung and other companies do. Fiio will eventually implement a bug tracker with crash reports too - it's mostly a matter of time. 
 
We should offer support, those DAPs exist for one thing - sound. They still do it well in folder browsing from my understanding, and as long as EQ works, that's all I will ask for now. Because that is my usage pattern - well, this and DAC function. 
 
People are really alarmed, but the old FW was working well - new FW won't make it another device. 
 
This is the same as doing overclock. It's an endless race where we forget to do what we should - enjoy the thing. (I has recently given up on overclocking and has a good peace of mind, don't be aggressive - overclocking is some serious problem after a point) 

 
Software allows you to enjoy the sound. If the software fails the SQ will not matter.

 

[JaviAl]

My FW 3.0.4 Beta report:
 
1. Scanning media library for the first time in my 1 TB. Kingston HyperX pendrive, tooks about 40 minutes and only scans 600 songs aprox. FW 2.0 tooks 5 minutes to scan more than 8.000 songs.
 
2. Scanning media library for the second time in my 1 TB. Kingston HyperX pendrive, tooks about 1 hour and only scans 3.000 songs aprox. FW 2.0 tooks 5 minutes to scan more than 8.000 songs.
 
3. Scanning media library for the third time in my 1 TB. Kingston HyperX pendrive, tooks about 1 hour and only scans about 6.500 songs aprox. FW 2.0 tooks 5 minutes to scan more than 8.000 songs.
 
4. Some DSD64 files with no DST encoding, reproduces but no sound output.
 
5. Swiftkey keyboard or any other different keyboard than the Android default not work on Pure Music Mode.
 
6. Imposible to see long names and dark gray subtitles, some icons and others texts dificult to read:


 
7. Changing the default icons orders on Fiio music main screen, return to default order when exits Fiio Music or restart the device. This also occurs in FW 2.0:

 
8. Allow multiple genres, artists tag separated by semicolon.
 
9. Interesting to see the number of track when searching by albums or artists.
 
Returning to FW 2.0 again.  

 

[headwhacker]

Wow this is beginning to feel like DX50 again. lol

 

[JamesFiiO]

seems it is a wrong decision to release the beta firmware to public.  I think the best way is just open to some users so they can help us and other users, and them people can wait for a stable firmware. 

 

[JamesFiiO]

   
IMO, SQ and UI should both go together. We are (Beta testers) offering support to FiiO - first by purchasing the product and now in OS bug feedback.

 
sorry for the trouble, but we are not asking anyone to update to the beta firmware.  people in head-fi should known our style that we are following our customers. I can see quite a lot people complaned the beta version so plz understant that we may not 
 
open the beta firmwar to the public in the future. 

 

[citraian]

seems it is a wrong decision to release the beta firmware to public.  I think the best way is just open to some users so they can help us and other users, and them people can wait for a stable firmware. 

not really a bad decision. some people should understand what a beta means

 

[JamesFiiO]

   
Thanks for confirming!
 
@JamesFiiO
 
I hope this is included in your list of "to address" in the firmware or maybe in your IT back end. Or if you can't get the OTA to work, then a simple link will do for us users to download. Hopefully your future reveals will bear fruit and not leave us users hanging. 
 
 
Totally understand! thanks!

 
 
sorry it take time to translate the content and lots of time to upload the firmware to the server outside China. 

 

[JamesFiiO]

not really a bad decision. some people should understand what a beta means

 
yes, some understand, so we should just open to them but not for others. 

 

[JHutchins]

yes, some understand, so we should just open to them but not for others. 

James,
It is not that people do not understand the concept of beta software, the problem is the lack of a change log. The frustration is caused by not knowing what issues the latest FW has addressed and therefore where we are looking for improvements. For example, my main concern is the down-sampling of output through the digital Coax output which FiiO has confirmed is an issue back in 3.02, it was the same in 3.03 but I have no idea if there has been an attempt to fix the problem. Is the problem still the same in 3.04, I've no idea and I'm not inclined to load the latest Beta to find that it's not fixed and thus I have to revert to 2.0 yet again.

 

[karloil]

sorry for the trouble, but we are not asking anyone to update to the beta firmware.  people in head-fi should known our style that we are following our customers. I can see quite a lot people complaned the beta version so plz understant that we may not 

Yes, I totally understand that you're not asking everyone to update to Beta but opening this to the public gives your users the opportunity to "try and give feedback" - and I believe a lot are doing that. Few might be complaining but the general is definitely helping out in identifying issues for you to resolve.

My main concern and feedback is the manner this Beta testing has been done:
- multiple threads which causes confusion
- issues tracking identified bugs, it's a mess! no centralized way of showing your users that this bug has been identified and is being addressed - so you get multiple reports for the same issue and it also wastes your Reps time in answering the same item over and over again! This came to the point that your user has already volunteered to do this job for you, which in my opinion should be your job and let the user just enjoy his music.

sorry it take time to translate the content and lots of time to upload the firmware to the server outside China. 

But shouldn't this be already prepared and completely uploaded (including to servers outside of China - as you know that head-fi is worldwide) and tested before you even made the announcement?

 

[KC33]

@JamesFiiO ,I would suggest offering everyone the most stable FW for the X7 (as you perceive it to be) and not release anything until you have a fully functional upgrade that works properly. A lot of people apparently don't know what Beta means so releasing these updates just adds more confusion and frustration. 

 

[harpo1]

I agree there is like four or five threads that involve firmware now and none of them list issues with the exception of the one started by a head-fi user.  Beta testing should be done in one thread where the firmware is posted, known issues listed and updated when fixed.  @JamesFiiO a changelog is crucial when beta testing otherwise we have no idea what to test.  This would make the experience better for all involved.  

 

[Paulo Abreu]

Guys, a little help concerning this latest FW for who already upgraded...

Some people reported problems reading tracks from 200Gb card, is this confirmed? I want to install FW 3.0.4 but if this is a new problem, I'll wait.
I don't want flash again a previous FW, I am at 3.0.3

TIA
Regards