- 0 Posts
- 21 Comments
Also, Google is no longer releasing the Pixel-specific source code, meaning you can no longer just build AOSP for new Pixels and have all the hardware just work - this makes it harder for custom ROM developers and might eventually lead to some hardware being simply unsupported unless you use the stock ROM.
Just to be clear, the applets were stuck while the laptop was plugged in? If so, then it might just be the threshold - connected, not charging, not discharging (because the laptop is running off the AC adapter).
For example on my IdeaPad laptop, when I enable the charge limiting feature it will get “stuck” at 59 or 60% while plugged in. It doesn’t have a configurable threshold. Although your laptop might provide a more fine-grained control given that you were able to fully discharge it while plugged in.
I agree, the fact that Meta considers 13 year olds being able to have romantic chats with chatbots to be perfectly fine is disturbing and IMHO the main newsworthy thing here.
However there is no mention of “200 pages of romantic interactions with minors” in the article - that is the whole chatbot guidelines document. Still, it including such things shows how shitty Meta is as a company.
OK, so the whole LLM chatbot arranging dates with people thing is obviously problematic, but this person simply tripped and fell, and the headline vaguely implies that the chatbot is responsible for his death. That seems a bit clickbaity - if it was a real person and they were actually waiting to meet at the agreed upon address, the outcome would be the same.
I don’t understand how having a notification is what’s keeping an app alive.
Do you remember notifications that couldn’t be swiped away in older Android versions? Their point was to keep their app alive. They still exist and still work the same way, keeping their app alive until it cancels the notification, except they can now be dismissed like any other notification (which doesn’t really have any effect other than hiding it from you - it will still keep the app alive even when hidden).
It’s possible that it’s broken in AOSP for some reason, but developer documentation says it should work like this and it does indeed work like this on stock Google ROMs on Pixels.
why would swiping away an app not kill it? why would you do that? leave it be until it’s done wtf
Because if an app has a permanent notification, it cannot get killed. Before Android 15 or 14, you couldn’t even swipe such notifications away - the idea was that the app was forced to tell the user it’s running.
Then Android added a list of apps running in the background and allowed users to dismiss the permanent notifications, but the behavior is still the same - an app can keep itself alive until it removes the notification on its own or gets force killed either by doze or from the settings.
So swiping away a browser after you initiate a download is a perfectly valid use case that is intended to work without any problems. If it doesn’t, then it’s a bug either in LineageOS or in the browser.
Also, I can confirm this works perfectly fine on stock Android 16 ROM on a Pixel with Vivaldi browser - the download finished, and then Vivaldi got killed, because nothing was keeping it alive after it cancelled its download notification.
Idk, it surprises me it took so long for TP-Link to get into trouble with how they tend to support every HW revision of their routers for about a year and then stop releasing any security updates for them. That’s awful for a device intended to sit at the edge of your network, possibly having a public IP address.
Like sure, you can look for any reasons you want, but not giving a fuck about security in a device that’s always connected to the internet and also routes all user traffic is bound to get companies in trouble when someone with the power to do something about it notices.
Apparently not according to the other comments here, but I absolutely love Material You now that a lot of apps support it. Not having every app have its own color scheme just feels comfortable and IMHO makes a lot of sense together with the system-wide dark mode.
Also, the app drawer always has unthemed icons, the themed ones are only for the home screen where I like to keep the few apps that I use often, so not having a colorful mess for a home screen is a bigger plus for me than losing the ability to recognize them at a glance, because I know exactly where on the home screen they are anyway.
Nah, the kernel isn’t that important for apps - you can replace the kernel and update the massive Android framework to work with the new one relatively easily (you will need some Linux compatibility for native code that does syscalls on its own, but that’s pretty much it - even WSL1 could do that).
It’s all the APIs and system apps provided by Google that have no reasonable alternative in AOSP that are the problem for compatibility. Look how incomplete projects like MicroG (an open-source implementation of Google Play Services) are, and their only goal is to provide Android compatibility for unofficial ROMs without installing the proper Google services.
Sure, but I don’t see how any of that disproves the current “M$ supremacy” for “normies” - the fact is that people who couldn’t care less about how their computers work will have a much easier time using Windows (and probably macOS) than any Linux distro. You don’t have to worry that some software won’t be available to you because of your choice of the OS, and if you ever have a problem it’s easy to find help.
I haven’t used Windows in a decade on my personal computers, but as long as these two things hold true, it will always be my recommended OS for people who simply don’t care - I’m not going to spend my time doing free IT support for everyone I know and then get blamed everytime something doesn’t work.
Right, but the commenter above me seems to suggest that GrapheneOS removed the battery management in order to bring the charging limit back, which is why I asked.