I’m really curious to learn how you get calls in so many different languages. I could definitely see Spanish, English, and maybe Vietnamese all being spoken in a general geographic area, but you listed a lot of diverse languages. Pretty cool if that’s really all within one area!
Look at the build I linked in my issue there. You will see an artifacts page where you can download a working build as a zip. You need to be logged in to GitHub to see the download link.
But like I said, Zygisk is still pretty broken even with that build. You’ll get “further,” but I wouldn’t recommend running it as a daily driver.
No one has any clue when 27 is coming. I just know 26.4 was the last 26.x build.
Are you on GrapheneOS by chance? Either disable Zygisk or try the build I linked here. They kinda rushed the 26 builds out the door without a lot of testing, which is a shame, considering there will be no more releases until v27
https://github.com/topjohnwu/Magisk/issues/7489
However, be warned: my system was very unstable with Zygisk enabled even with this build. Everything would “work,” but apps would randomly crash, be unresponsive, or just display very strange behavior that all went away when Zygisk was disabled. I leave it disabled for now and will try again in v27.
For apps that have root detection, try web versions of those services when possible. Especially banking services.
Hi :)
If you’re already running an instance, you’re not going to have a good time of this on the same server unfortunately. The webserver config I ship assumes a single instance, and all of the handling assumes only one domain. You would have to basically modify my entire script to support something like this.
You can take a look at my advanced configuration page to figure out what files you can edit, but this would be a very manual process for what you want to do.
Apologies, but you would be better off deploying a new server.
CalyxOS (and the supported devices) expose you to a classic “evil maid attack” applied to phones.
As usual if you’re looking to have any security (Verified boot) GrapheneOS + Pixel phone is the only options. I really don’t get it how come people(…) are okay with having a phone with all their personal data and logins without verified boot. Stolen / lost phone and game over.
But CalyxOS focuses on verified boot too?
Not sure what you mean. I’m not trying to use an external monitor, I just want to use AR glasses I already own. There’s no adapter for that, it’s just a USB C cable.
I really hope this will let my AR glasses work. I was bummed they didn’t work with my Pixel 6 Pro, and half the reason I went for an 8 Pro were the initial display out support news from July.
When this workaround was reported to not work, I was pretty bummed, but this seems like a good sign. I’ll be building my own ROM anyway, so I can easily set this property enabled by default with no need for root.
More like guesswork/assumptions than reality
Sorry to be blunt, but you’re not a developer and it shows. Android’s build system was purpose made to be reproducible. Electron was not.
There is so much going on in an Electron build, most of which is out of Signal’s control unless they maintain an entire fork of the Electron build stack. That is an enormous engineering effort for basically zero benefit.
It probably is functionally reproducible, apart from checksums differing due to build dates baked into the artifacts somewhere. It’s not as easy as you think.
If you think it’s as easy as “building it in a Docker container,” then by all means, try.
Keep in mind that Lawnchair is buggy and consistently 2 years behind the latest version of Android. I’m using their 12.1 beta, and it still crashes with null pointer exceptions about twice a week. And, on Android 13 and 14, integration you would expect between the recents screen and Lawnchair does not work. These are the gestures you’re talking about.
And here we are on the launch of Android 14, with no development of Lawnchair for Android 13 in sight.
I should also point out, these gestures you’re mentioning only work on the stock Pixel launcher, the AOSP launcher, and Lawnchair. This is because starting with Android 9, Google baked the recents switcher directly into the launcher app. And, it has to be a system-level app with a special system config that allows the launcher to perform this function.
This is why root is needed for the Quickswitch module. Lawnchair has the code to do this (at least on Android 12), but you have to overwrite a system config to allow Lawnchair’s package name to be capable of serving the recents screen.
Thanks, I didn’t know about this!
But it doesn’t look like it supports text message triggers :(
The person you replied to is being downvoted, and yes, expecting support from Google is a meme, and Google deserves 100% of the negativity they’re receiving in this regard.
But, in their defense, they have always kept their word on keeping Pixels updated, and in some cases, have added on an additional year of support when not originally planned, including an extra full Android update for older devices.
So while they eventually kill every new software product they make, they’ve always kept their word on Pixel updates. I think the Pixel team has a lot more resources than the rest of Google, so I’m inclined to believe them for now, but I’ll be one of the first people grabbing a pitchfork if they don’t keep their word.
There have been a few RCE’s for Android 11 and up impacting both Bluetooth and the Baseband.
Bluetooth:
Baseband:
Of course, Android 11 is still supported as of right now, so if you have been getting security updates when available, then you are good. I just know there are phones running 11 and below that don’t even get security updates, so those are the people that need to watch out. You can check your Security Patch Level in settings to be sure.
If you haven’t been getting security updates, I would definitely consider getting a new phone. Especially if you are not one that stays home a lot. The people who will try to exploit things like Bluetooth will be out and about, not walking up to your home.
deleted by creator
Be careful, there have been some pretty nasty 0-click exploits in the time Android 11 has been around, so I hope you have still been getting security updates.
In about 5 months, Android 11 will be end of life and won’t get security updates anymore, so definitely keep an eye out for anything you may be vulnerable to.
It’s not an assumption. The vanilla Signal app has code in it that disables itself after a certain period without updates. Unless they removed that from this app, then this will do the same thing.
In this case, it sure does sound like abuse. Considering the careful wording, combined with the seemingly kneejerk reaction of requiring authentication, there was likely illegal activity going on:
Earlier this year we saw an increase in the number of reports we received about some people using our service in ways that we cannot tolerate. To be more clear, this was not about some people merely saying things that others disliked.
Over the past several months we tried multiple strategies in order to end the violations of our terms of service. However in the end, we determined that requiring authentication was a necessary step to continue operating meet.jit.si.
It was a free, anonymous service that let people stream video and send messages. Consider for a moment if that “video” was actually non-video data encoded to be streamed through Jitsi and sent to another location. Or, consider if the video was video, but was so egregious and illegal, that Jitsi had to take action. It doesn’t take a lot of thinking to consider the kinds of activities could have been going on.
Why is everyone up in arms about this? The abuse of their free service was rampant. This isn’t a core project change, this is just a measure to keep a version of the project up for free without completely taking it down. They don’t even have a way to monetize this. An alternative was to simply shut it down and only allow you to self host it.
I self host my Jitsi instance, but as a privacy nut, I don’t see a problem with this. Absolute privacy cannot always coexist with free anonymous services. Don’t blame Jitsi, blame the people who ruined it for everyone else.
By blocking unauthorized emulations on PC, studios are able to increase their revenue during the game launch window, which is the most important period for monetization.
Uh huh, yeah, this will definitely just create money out of thin air from people who couldn’t afford it in the first place.
The Nintendo Switch Emulator Protection will ensure that anyone wishing to play the game has to buy a legitimate copy.
To say nothing of Switches running custom firmware. There is absolutely no way for a game to detect this, so it will still be easy to pirate with those. Games will still leak early. Nothing will change.
This is a grift. Studios will probably spend more to license this “technology” than they stand to “save” by preventing emulation. They are taking advantage of clueless game studio execs and they know it.
They’ve been on some kind of emulation crusade then, because it looks like they just killed Ryujinx: