01-11-2020, 12:45 PM
There still seems to be a misunderstanding.
This Chromebook is running the very latest release of ChromeOS. Unless you have confirmation from other ChromeOS users that everything is fine with *their* model, I think you must assume that moode currently works with _none_ of them.
Is there a way we could get current moode users that happen to have a Chromebook to test this out somehow? Call for testing?
Also, you mention that this might cause a regression, but I see no way this can happen at all. Please have a look at src/io.c in bluez-alsa where there's this check exactly 3x:
#if ENABLE_PAYLOADCHECK
if (rtp_header->paytype < 96) {
warn("Unsupported RTP payload type: %u", rtp_header->paytype);
continue;
}
#endif
How could not having this check regress anything? When removed, the quantity of accepted inputs is strictly higher than with the check.
Regards
Opi
This Chromebook is running the very latest release of ChromeOS. Unless you have confirmation from other ChromeOS users that everything is fine with *their* model, I think you must assume that moode currently works with _none_ of them.
Is there a way we could get current moode users that happen to have a Chromebook to test this out somehow? Call for testing?
Also, you mention that this might cause a regression, but I see no way this can happen at all. Please have a look at src/io.c in bluez-alsa where there's this check exactly 3x:
#if ENABLE_PAYLOADCHECK
if (rtp_header->paytype < 96) {
warn("Unsupported RTP payload type: %u", rtp_header->paytype);
continue;
}
#endif
How could not having this check regress anything? When removed, the quantity of accepted inputs is strictly higher than with the check.
Regards
Opi