Once this problem is solved, my own approach to further FW upgrades is to wait and see. Probably for a good long while, given how long it has taken for this current nause-up to emerge.
No. I’m on a Pixel 8a with Android 15. I have these issues as well.
1 Like
Everyone needs to email naim support. Please.
1 Like
Happy to, but… it’s working for me.
Is everyone who has this issue using Android 15?
14 for me.
So far no options have been pushed from Samsung for 15.
I am on Android 15
FW 7.4.
I mailed Naim.
I recognize all the discribed issues.
Hopefully a solution will follow.
I think I am having these issues more than 2 weeks now.
2 weeks. Same time as me. I expect that coincides with the release of 7.4 naim software
I’m on Android 15 and no problems with the app or Qobuz. (Famous last words).
Android 14 for me and the those problems arrived approximatively 2 weeks ago
The app will not show also what radio channel is Playing nor ( at times) find my nas ( asset). Both are clearly visable on the ipad.
It will play the radio if they are presets or favourites, but select radio from the buttons at the top, and the app crashes.
If i didnt have an ipad, my ndx2/555 would be pretty near useless. And naim appear very quiet about this issue?
I have received the following answer on my email to Naim after I provided additional details:
Many thanks for providing the details.
Our software team are investigating. It appears to only affect a small number of Android devices, and it also appears to be a change at Qobuz’ end, rather than a bug in the app. As soon as I have some news, I will either return to you or an update will be released.
We appreciate your patience.
So they are investigating the issue and it seems to Naim it is caused by a change at Qobuz. I am not very much at home in coding and API calls. So I don’t know if that it’s possible that something at Qobuz is causing issues on the output side in the Naim app as well. Personally I find it difficult to believe, as to me it would be logical in that case that that would cause problems with a lot more users.
So I am curious: Could those experiencing issues with the Android Naim App also see which version of Qobuz they are using?
I’ll start. My version is :
- qconnect-beta07
How do you know what version of qobuz your naim app is using?
My samsung/android naim app is FUBAR. Totally unusable. If i didnt have an old ipad it would be useless.
I don’t but I am in a beta group at Qobuz so maybe that could cause it. And that could become clear if others are also beta users. So, like I said. Just curious.
Ok. Naim or Qobuz beta group?
Qobuz
It was posted by Richard Dane that one of the advantages of the Focal&naim tie up was a significant investment in software development.
Might be worth seeking comment on how that’s translating into increased user satisfaction with the Android app
naim support don’t read the forum bug threads so email your dissatisfaction to support@naimaudio.com
I had the same email.
1 Like
I have no issues, and while I’m using the beta version of the client Qobuz app, I’m not in the Qobuz Connect beta that I assume you are in.
S24, Android 14, latest Focal/Naim and Qobuz client apps version. MuSo2 on my case, should it make any difference.
Is is a backend API change, I agree anyone using the same should have the same problems.
1 Like