Moritz Warning

Please share you changes. Maybe it is enough to expose the vp8 and h264 setting. Then I could add those as settings.

Nice. Have you tried to just disable VP8? https://github.com/meshenger-app/meshenger-android/blob/master/app/src/main/kotlin/d/d/meshenger/call/RTCCall.kt#L531 (with enabled hardware accelaration)

Thank you. I will give it a try.

@CWTakiku can you try a fresh install of https://github.com/meshenger-app/meshenger-android/commit/48756d0e44fe56c6c797202c1dd13005b7859197 on both phones? Btw., the video codec limit to h264 makes by phone unable to connect. I am still investigating.

@CWTakiku thank you, I will give it a try. I did not commit my custom factory, since it broke the call feature for me.

I tried the code with only isSupportedH264 returning true (like in your screenshot), but now the phones cannot establish a connection. Aside from that, the picture quality with the current...

hm, I had the same software on both devices. Here is the source code: https://github.com/meshenger-app/meshenger-android/tree/h264

I will do an intermediate release with enabled hardware decoding by default (it wasn't working right before). Then let's do more testing.

Let's close this issue. It seem to be resolved. But the CPU overuse detection might still ruin the day. But it can be disabled in the setting on the users...

The problem is that the TLD that is intercepted is configurable. So when it is set for the kadnode binary, it would also need to be changed in the /etc/resolv.conf....