Expert Remote App - not on Android 14 (S24's...)

[Delija]

Could -> this <- be something to try?
I would try it myself, but don't want to lose the app.
My S23 was running Android 13 when i got it, but has been upgraded to Android 14.

You are not reading carefully

I already wrote it's not working. I've tried on Pixel 8 and S24 Ultra.

I used this on my S22 running A14. It took quite a few attempts, but I got it to work. I also used some of the tricks in the link above, especially when I got the message that my device was unauthorized.
https://youtu.be/tsVJniGSVXE

S22 is an old phone - it wasn't natively A14. It also works on A33.
Try this on S24. If you manage to make it run - it would be great!

[ada]

Updating the thread about my first findings:

Good news:
- I was able to get the latest Android app code fully decompiled and I am able to recompile and run it 100% fully functional for any 32bit Android platform.


Bad news:
- There is a native .so lib which is complied for x86 and armV7 but not for armV8 (which is 64bit and required for Android 14), I will try to decompile this lib too but as of my knowledge even if I decompile it to be readable my researches shows that it will be nearly impossible to recompile it back which leaves us which only the option of this .so lib code to be shared by Devialet with us and then I can debug and fix the architecture problems in the code and then have a 64bit version of it.

While I will keep trying, unfortunately I am not seeing a feasible option to get this project done as .so file architecturally is the blocker here. If someone is interested in with the fully functional Android code I am happy to share, if there is anyone that has C decompile and recompile skills, I am also happy to partner with them but for the time being we are again depending on Devialet.

[sergii85]

Updating the thread about my first findings:

Good news:
- I was able to get the latest Android app code fully decompiled and I am able to recompile and run it 100% fully functional for any 32bit Android platform.


Bad news:
- There is a native .so lib which is complied for x86 and armV7 but not for armV8 (which is 64bit and required for Android 14), I will try to decompile this lib too but as of my knowledge even if I decompile it to be readable my researches shows that it will be nearly impossible to recompile it back which leaves us which only the option of this .so lib code to be shared by Devialet with us and then I can debug and fix the architecture problems in the code and then have a 64bit version of it.

While I will keep trying, unfortunately I am not seeing a feasible option to get this project done as .so file architecturally is the blocker here. If someone is interested in with the fully functional Android code I am happy to share, if there is anyone that has C decompile and recompile skills, I am also happy to partner with them but for the time being we are again depending on Devialet.

So, as I understand correct, there is no way we can use an expert remote app on new devices?

[ada]

Not until Devialet agrees to share the code of the .so lib that we can recompile. I think this is a dead end as they are not responding Expert platform to become open source as it is EOL product. We may need to seriously increase the pressure on them with the petition that I prepared in here: https://devialetchat.com/Thread-Petition-for-Devialet

[sergii85]

Not until Devialet agrees to share the code of the .so lib that we can recompile. I think this is a dead end as they are not responding Expert platform to become open source as it is EOL product. We may need to seriously increase the pressure on them with the petition that I prepared in here: https://devialetchat.com/Thread-Petition-for-Devialet

Totally agree and support. All the users have to make a pressure at least to give us a source code for the future development. 
I would pay to somebody for a good working app or any other improvements and additional features.

[Cylob]

I gave it another shot (since Devialet seems to be listening when there's new products released)
and asked for an update on the Expert remote app::::

answer1:::::
I was informed that the Expert remote app will no longer provide the update.
===
follow up question::::
'' Why not add support for the Expert in the current app that features all your products? ''
===
answer [from another customer & support agent] ::::
Thanks for your voice!
I've forwarded the above to the team.
Thank you very much again for your support of Devialet's products.
====

Well, my fingers are crossed. I won't hold my breath though...

[fraserhadden]

II thought that I should bring this thread back to life as we must now all fear the moment when faulty remotes can no longer be repaired and we will be forced to the app.

The technique demonstrated in the YouTube video (https://www.youtube.com/watch?v=tsVJniGSVXE) does work and is much more straightforward than it appears on first viewing.

Two things:

1. Turn off the 'music'. You will need to concentrate!
2. There are two errors @ 2:37 - (a) An obvious typing error in the first command; (b) Do not type "DRAG THE FILES HERE" after the command ending in sdk-block. Type the full path to the apk instead. Thus the command will be adb install --bypass-low-target-sdk-block c:\adb\platform-tools\DevialetExpert.apk

Note that there should be no spaces in the .apk filename. You can see that I renamed mine to DevialetExpert.apk

Joy is pretty much unconfined

[Stian_Gel]

Tried this on my Sony Xperia 1 VI phone with no luck.
Got various error messages.
Had 3 different .apk files. Same error on all of them.
Looked promising in the start though.

[fraserhadden]

Sorry to hear of your travails.

If all the .apks you tried failed, the problem is probably not with the .apks themselves.

The .apk I used was Devialet Expert Remote_1.1.2_APKPure.apk, downloaded from https://apkcombo.app/devialet-expert-rem...et.remote/, and shortened by me to DevialetExpert.apk as installation failed when its original name was used. Knocking out the spaces was critical.

From what I could divine from the command line, the process should be wholly independent of the phone itself as it is simply bypassing the Android check for 'insecure' apps.

[Stian_Gel]

That was one of the apk's i tested.
Probably a phone issue then.
Sony might have a more agressive software.