mrjeeves

Our app includes Android Auto, which I think is what causes it for us. Submitted 4 Sept, still in review.

Was only 48-72 hours until this year, where it randomly jumped to 2 weeks or longer like it still is.

It's really frustrating, and makes it very difficult to develop with, let alone reliably release features across platforms.

Coming second half of this year!

Oops. Thanks.

It's tough, but when the people don't respond what do you do?

Do you just sit on the info, hoping noone else sees it and exploits it?

Or do you try and get them to fix it somehow?

The headers are included in every single downlink message after initiating a call, including the downlink SIP Invite message before 100 Trying, 180 Ringing or 183 Session Progress.

If you're quick enough (or automate this with dedicated software, like an attacker might actually do), it won't even need to ring out. It's really not good.

I doubt it. This is likely O2 UK specific.

This one is actually on us. The email contacted was actually @virginmediao2.co.uk, not @virginmedia.co.uk. It's a typo in the article.

I'll update it with a correction.

We know the relevant team within O2 was actually informed, but evidently no action (or insufficient action) was taken.

Yes, you can do the first one. There's a post scrubber on the right hand side of any thread with buttons for top and bottom.

Disclaimer: Flarum core dev

Argh, I'm jealous.

I've been looking for suitable SDRs in the ~£180 range for a few months now, and nowhere has one suitable for 5G NR or 4G LTE available. HackRF seems to be pretty crippled in mobile networking, and Pluto seems to not work at all on srsRAN/srsLTE.

I doubt you'd be willing to let go of your full-size LimeSDR for £180, though, and I don't blame you based on its demand level.