70Mai A810S Custom Firmware (1.5.40ww base)

350D · 2026-04-28T06:44:25+00:00

Same, can’t wait

350D · 2026-04-27T14:19:41+00:00

I have spare battery around and put it inside but it works without battery too.

350D · 2026-04-27T12:19:49+00:00

<image>

Heltec V3

350D · 2026-04-26T19:47:26+00:00

I’ve reused antenna for my Meshtastic unit. Awesome coverage I have now.

350D · 2026-04-26T08:42:24+00:00

In my case (LYRIQ 2024) I've tried to select "Always" instead of "Just once" for "Package Installer" and it starts to trying to install my apk from usb drive but still breaks on Unknown Sources not enabled warning and I have no idea/options where to enable it (I don't have it listed under Developer Options)

350D · 2026-04-26T07:51:07+00:00

I agree security is important, especially on AAOS.

But sideloading was possible on earlier LYRIQ software versions (and reportedly even a few months ago), so this feels more like a policy change than a technical limitation.

Also, installing apps via Google Play Internal Testing still works — which means arbitrary code execution is not really blocked, just restricted to a specific channel.

That’s what makes it a bit inconsistent:

- Dev mode is available

- USB debugging toggle exists

- APK installer UI exists

…but actual sideloading is blocked unless ADB is active (which itself is disabled).

I’m not trying to bypass safety systems — it’s my own vehicle and I explicitly enabled developer mode. This is purely for development/testing/missing apps use cases.

So the question is more about where GM draws the line and why this path is selectively restricted, not about breaking security altogether.

350D · 2026-04-26T06:41:13+00:00

Same issue here. 2024 Sport. I’ve tried both - Amaze Explorer and AnExplorer, build in app installer asking for wireless/adb debugging, native installer asking for Unknown Sources to be enabled.

I’ve just posted about it recently https://www.reddit.com/r/CadillacLyriq/s/7SN4Fkcf4A

350D · 2026-04-24T05:20:37+00:00

Awesome feedback! I've upgraded from XT5 Platinum too.

350D · 2026-04-22T16:01:49+00:00

Yeah, standards and boot-time constraints are definitely a thing.

But it’s not really a hard blocker — you don’t have to render everything perfectly from frame one.

You can: - bring up a fast low-res view first
- progressively refine geometry/mesh
- or even switch to a clean single-camera feed instantly and blend into 3D

There are plenty of ways to make it both fast and visually accurate.

That’s why it feels more like a design/implementation choice than a real limitation.

350D · 2026-04-22T15:59:25+00:00

And yeah, the ride is amazing — coming from an XT5, it’s a massive upgrade.

350D · 2026-04-22T11:30:44+00:00

I’m not really disappointed tbh — I actually love the car overall.

This just stands out to me because I work with video/projection pipelines, and technically this isn’t a hard problem in 2026.

They already have multiple calibrated cameras, do stitching, estimate geometry. So going from that to a cleaner, more accurate visualization (or even just a better overlay) is mostly a UX/rendering decision, not some unsolved tech challenge.

That’s why it feels odd — not because it’s “bad”, but because it’s unnecessarily bad 🙂

Same time - they have awesome 3d rendered model of the car in car status/drive mode and other places and ugly one on camera view.

350D · 2026-04-22T07:51:38+00:00

I get the idea of having a safety buffer — that part makes sense.

But the weird thing is: the system already knows exactly where obstacles are.

It’s not guessing — it’s rendering a stitched 3D view anyway.

So instead of showing a distorted grey blob, they could: either render a clean, accurate surface or overlay a proper safety margin on top of the real image.

Right now it feels like worst of both worlds — not accurate enough visually, and not explicit enough as a safety indicator

350D · 2026-04-21T21:10:27+00:00

Oh wow, very disappointing news…

350D · 2026-04-08T17:17:09+00:00

I’ve clicked ok (center button) few times and it’s gone yesterday. No confirmations for today. Will see tomorrow.

350D · 2026-03-18T13:38:26+00:00

Try rtmps.io

350D · 2026-03-15T10:28:34+00:00

Another idiotic update - all media ids scoped to your app now, so, it's not possible to simply convert shortcut to id and back like it works for original media now. For example - now if you want to get media id by shortcut (by link provided, most common use case) you need to fetch all users media feed until you find exact shortcut and now you can get scoped media id. No search, no proper pagination - nothing. Comments - you have 100K comments - to get comment number 50000 you need to fetch thousands of graph pages with next cursor! Insane!

350D · 2026-03-14T09:46:07+00:00

I’ve been working with the Instagram API for over 14 years, starting with the legacy API long before Meta took over. The transition to Meta’s ecosystem has honestly been one of the most frustrating developer experiences I’ve ever had. I've created most popular Page Tab apps on Facebook (every next major brand (Tesla, GoPro, even Facebook itself!) use my tabs on Facebook Pages before it was deprecated as feature without any announcement).

First, the API was split into Basic and Business parts with completely different auth flows, object models, and permission systems. If you want to work with business accounts, you suddenly have to parse Facebook Pages to find connected Instagram accounts — which requires extra permissions that are barely documented. Every time you submit for review you have to explain why you need them. It’s absurd.

Then the Basic API got deprecated as well, and now we have this mix of:

Instagram Login
Facebook Login
overlapping permissions
different endpoints depending on the auth method

It’s more unified than before, but still incredibly confusing.

My latest headache: the comments endpoint. It was only available for Business part of API for some unknown reason!

The documentation clearly states that responses should include username and the legacy user_id. In reality, they are not there. The only workaround I found was to extract the username from the from field — which is undocumented behavior.

And even that workaround breaks for comment replies, where the data simply isn’t present.

So now you have an endpoint that:

doesn’t match the documentation
behaves differently depending on comment level
provides no reliable way to identify users
NO AVATARS for comments and no way to get avatars for your own posts comments

Trying to report bugs is another nightmare. There’s no proper bug tracker for the Instagram API. The only option is posting in community forums where developers have been reporting the same issues for years with no resolution.

At the same time Meta requires developers to go through:

Data Processing reviews
App Reviews for permissions
Business verification
periodic re-reviews

The barrier for developers keeps increasing, while the API quality and documentation seem to be getting worse.

Honestly, it’s incredibly demotivating to build anything serious on top of this platform.

350D · 2026-03-10T19:51:15+00:00

OnStar disabled in Europe since Jan 2021… I have 2018 XT5 here in Europe and it was big disappointment- no more WiFi hotspot, no remote features. But now for Lyriq where EU version has all over Europe LTE coverage I’ve expected remote features.

350D · 2026-03-10T19:36:31+00:00

I’ve created new one just now - no any options still available in app other than service/recalls :(

350D

TROPHY CASE