@Christoast
Please provide the ROSE ID from Device Settings > System Information so we can check.
Rose ID: OD3111 for Early Access 5.12
@Christoast
Is it correct that your deviceās Rose ID is 0D3111, starting with a number ā0ā instead of a letter āOā?
If you click āUse Official Versionā and download it, version 5.9 should be downloaded. However, is it correct that version 5.11 was downloaded even though you downloaded the Official version?
Thatās right, I went from the official version 5.9 to Early Access version 5.12.
Then, when I switched back to the official version, version 5.11 was updated.
Currently, Iām back on Early Access 5.12; itās the only version that allows me to access Tidal.
Hallo
i have a RS520 and I canāt sea the firmware update.
My early Version itās 5.10.
Can somebody help me?
Greats from Switzerland
Remo
Hi Remo,
Before you update ā Iād hold off for now if I were you. I have an RS520 too, and after updating to the latest [Early Access] v5.12.04, I ran into a serious problem: the device kept asking to update the MCU, and every time I confirmed, it rebooted and asked again ā an endless loop. I had to roll back to the stable firmware (5.9.0.9).
One more important thing: if you update and run into problems, you most likely wonāt be able to roll back to your current Early Access 5.10 ā as far as I understand, you can only go back to the official stable version, not to a previous EA build. So youād lose your current version either way.
Iāve reported the issue to Rose and theyāre looking into it, but thereās no fix yet. So unless you specifically need something from the new version, Iād recommend staying where you are until Rose confirms itās resolved.
You can follow my report here: RS520: MCU update loop after [Early Access] v5.12.04
@Geka4epist
Many thanks for the help, I also reported it to Rose and the answer is.
We apologize for any confusion this may have caused.
Following the release of the Early Access (E/A) version, an issue was reported where the Rose ID was not visible for certain users. Since there is a possibility that this issue could affect other users as well, we have temporarily suspended the update while we analyze the root cause.
We plan to redeploy the update around tomorrow and will provide another announcement as soon as it is released.
Thank you for your patience.
@Christoast
Thank you for your help. Thanks to you, I think weāve found the root cause. A new EA version is expected to be released this week, and I believe this version wonāt have any issues.
Glad I could help!
Unfortunately, I havenāt received any updates from the Rose team regarding my specific issue yet. But from what I can see, it looks like weāre all dealing with the same root problem here ā the bug with the incorrect Rose ID in the new firmware. And as I understand it, thatās also what causes the MCU update issue.
Hopefully the new EA version they mentioned will fix all of this. Fingers crossed!
Hi Rose_love,
Iād like to request a small but important addition to the upcoming EA release: please add the Israel time zone (Jerusalem / Tel Aviv, IST UTC+2 / IDT UTC+3 with daylight saving) to the firmware.
Currently there is no option to select Israelās time zone in the device settings, which means the clock(and the weather) cannot be set correctly for users in Israel. As a workaround I currently have to select a different city in the same offset - Athens in my case, but this doesnāt handle our daylight saving transitions properly.
This should be a simple addition, and it would be much appreciated by Rose owners in Israel. Thank you!
Thank you for your suggestion.
The request has already been forwarded to our software development team for review. From our initial assessment, this appears to be something that could potentially be addressed through a software update.
We will continue to monitor the progress internally, and as soon as we receive any updates or confirmation that the requested feature has been implemented, we will be happy to let you know.
Thank you for your valuable feedback and for helping us improve HiFi ROSE.