Anthropic is catching up with OpenAI

https://fixvx.com/luckeyfaraday/status/2107445352622415935?s=46

Samsung is deliberately crippling Linux/AVF support on its phones, and I’m honestly tired of it

I’m genuinely frustrated with Samsung’s approach to Android’s Android Virtualization Framework (AVF) and the new Linux Terminal. I recently bought a Galaxy F56 (Exynos 1480, One UI 8.5 / Android 16) specifically expecting that Android 16’s Linux/virtualization capabilities would be something I could actually use. Instead, after checking the device through ADB, it appears that Samsung simply hasn’t included the necessary components on this phone. I checked:
```
adb shell pm list packages | grep -E 'virtualization|microdroid|avf'
```

Nothing.
```
adb shell pm list features | grep -i virt
```

Nothing.
```
adb shell ls -l /dev/kvm
```

Result:
```
/dev/kvm: No such file or directory
```

And:
```
adb shell cmd virtualizationservice help
```

returns: Can't find service: virtualizationservice

The Samsung Linux Terminal package itself is also completely absent: Unknown package: com.android.virtualization.terminal So this isn't simply a case of Samsung hiding an app or forgetting to add a launcher shortcut. The underlying virtualization infrastructure doesn't appear to be present on my phone's stock firmware either. And that's what annoys me. Android itself has been moving toward proper virtualization with AVF, Microdroid, protected VMs, etc. Android 16 makes the Linux Terminal increasingly useful. Some Galaxy devices get the functionality, while other Samsung phones running essentially the same Android generation and One UI version don't. Why? If the hardware and Android platform are capable of supporting virtualization, why should Samsung decide that a particular phone simply doesn't get it?

I'm not asking Samsung to give a ₹20,000 phone every feature of a flagship. I'm asking for software capabilities that are already part of the Android platform to not be arbitrarily crippled or omitted. Samsung already has a huge history of limiting software features by device and region, but virtualization is particularly frustrating because it has enormous potential for:

* Linux development

* Running isolated

* Linux environments

* Developer/testing workloads

* Security research

* Container/VM experimentation

* Android development

* Education

* General power-user use

And Android's Linux Terminal could have turned a modern Samsung phone into a genuinely useful portable Linux development machine. Instead, on my F56, I'm apparently back to Termux + proot if I want Linux userspace. That's useful, but it isn't equivalent to having a proper VM backed by hardware virtualization. What makes this even more frustrating is that Samsung's own ecosystem is increasingly marketed toward developers and power users, while capabilities like this are being selectively withheld. Samsung: if AVF isn't supported because of a genuine hardware limitation, explain it. If there is a technical limitation, explain it. But if the hardware is capable and you're simply choosing not to ship the necessary components, please stop pretending that One UI's Android 16 features are universally available. At minimum, Samsung should publish a clear list of which Galaxy devices support AVF/Linux Terminal and why others don't. I bought an Android phone, not a phone where Samsung decides which parts of Android I'm allowed to use. Has anyone else checked their Galaxy device with ADB to see whether /dev/kvm, virtualizationservice, and the AVF packages are actually present?

https://redd.it/1wxb4tf
@reddit_android

Nothing is using Google Forms for account deletion requests 😭

Follow @NothingFuckups

Turns out, he is now past 23,000+ level in Candy Crush Saga after creating that record in August end 😭

Smart Launcher and Kustom Industries are joining forces. introducing Wild Pixels
https://www.smartlauncher.net/blog/smart-launcher-and-kustom-industries-are-joining-forces-introducing-wild-pixels

https://redd.it/1wzxpst
@reddit_android

Open up windows powershell and copy and paste this code:

[Console]::Beep(658, 125);
[Console]::Beep(1320, 500);
[Console]::Beep(990, 250);
[Console]::Beep(1056, 250);
[Console]::Beep(1188, 250);
[Console]::Beep(1320, 125);
[Console]::Beep(1188, 125);
[Console]::Beep(1056, 250);
[Console]::Beep(990, 250);
[Console]::Beep(880, 500);
[Console]::Beep(880, 250);
[Console]::Beep(1056, 250);
[Console]::Beep(1320, 500);
[Console]::Beep(1188, 250);
[Console]::Beep(1056, 250);
[Console]::Beep(990, 750);
[Console]::Beep(1056, 250);
[Console]::Beep(1188, 500);
[Console]::Beep(1320, 500);
[Console]::Beep(1056, 500);
[Console]::Beep(880, 500);
[Console]::Beep(880, 500);
sleep -m 250;
[Console]::Beep(1188, 500);
[Console]::Beep(1408, 250);
[Console]::Beep(1760, 500);
[Console]::Beep(1584, 250);
[Console]::Beep(1408, 250);
[Console]::Beep(1320, 750);
[Console]::Beep(1056, 250);
[Console]::Beep(1320, 500);
[Console]::Beep(1188, 250);
[Console]::Beep(1056, 250);
[Console]::Beep(990, 500);
[Console]::Beep(990, 250);
[Console]::Beep(1056, 250);
[Console]::Beep(1188, 500);
[Console]::Beep(1320, 500);
[Console]::Beep(1056, 500);
[Console]::Beep(880, 500);
[Console]::Beep(880, 500);
sleep -m 500;
[Console]::Beep(1320, 500);
[Console]::Beep(990, 250);
[Console]::Beep(1056, 250);
[Console]::Beep(1188, 250);
[Console]::Beep(1320, 125);
[Console]::Beep(1188, 125);
[Console]::Beep(1056, 250);
[Console]::Beep(990, 250);
[Console]::Beep(880, 500);
[Console]::Beep(880, 250);
[Console]::Beep(1056, 250);
[Console]::Beep(1320, 500);
[Console]::Beep(1188, 250);
[Console]::Beep(1056, 250);
[Console]::Beep(990, 750);
[Console]::Beep(1056, 250);
[Console]::Beep(1188, 500);
[Console]::Beep(1320, 500);
[Console]::Beep(1056, 500);
[Console]::Beep(880, 500);
[Console]::Beep(880, 500);
sleep -m 250;
[Console]::Beep(1188, 500);
[Console]::Beep(1408, 250);
[Console]::Beep(1760, 500);
[Console]::Beep(1584, 250);
[Console]::Beep(1408, 250);
[Console]::Beep(1320, 750);
[Console]::Beep(1056, 250);
[Console]::Beep(1320, 500);
[Console]::Beep(1188, 250);
[Console]::Beep(1056, 250);
[Console]::Beep(990, 500);
[Console]::Beep(990, 250);
[Console]::Beep(1056, 250);
[Console]::Beep(1188, 500);
[Console]::Beep(1320, 500);
[Console]::Beep(1056, 500);
[Console]::Beep(880, 500);
[Console]::Beep(880, 500);
sleep -m 500;
[Console]::Beep(660, 1000);
[Console]::Beep(528, 1000);
[Console]::Beep(594, 1000);
[Console]::Beep(495, 1000);
[Console]::Beep(528, 1000);
[Console]::Beep(440, 1000);
[Console]::Beep(419, 1000);
[Console]::Beep(495, 1000);
[Console]::Beep(660, 1000);
[Console]::Beep(528, 1000);
[Console]::Beep(594, 1000);
[Console]::Beep(495, 1000);
[Console]::Beep(528, 500);
[Console]::Beep(660, 500);
[Console]::Beep(880, 1000);
[Console]::Beep(838, 2000);
[Console]::Beep(660, 1000);
[Console]::Beep(528, 1000);
[Console]::Beep(594, 1000);
[Console]::Beep(495, 1000);
[Console]::Beep(528, 1000);
[Console]::Beep(440, 1000);
[Console]::Beep(419, 1000);
[Console]::Beep(495, 1000);
[Console]::Beep(660, 1000);
[Console]::Beep(528, 1000);
[Console]::Beep(594, 1000);
[Console]::Beep(495, 1000);
[Console]::Beep(528, 500);
[Console]::Beep(660, 500);
[Console]::Beep(880, 1000);
[Console]::Beep(838, 2000);

Apple's smart home device images have been leaked, they will be sold by LG

Designs and features of smart deadbolt door lock, thermostat and temperature sensor have leaked which are being developed by LG in collaboration with Apple.

https://www.notebookcheck.net/Apple-is-reportedly-helping-LG-build-smart-home-devices-and-the-designs-have-leaked.1418298.0.html

Apple smart home devices will debut on 13th October Globally

Interactive web messages right in the chat

The TGBetaLeak channel discovered a large experimental subsystem called HTMLBubbles in version 12.10.283300 of Telegram for macOS.

According to the description, the messaging app is testing interactive messages built with HTML, CSS, and JavaScript right in the chat, without the need to launch a separate Web Mini App window.

@tginfo editors have confirmed the module’s presence in the code of that version based on a preliminary review, but the described behavior and how it works have not yet been independently verified.

The idea is to turn ordinary messages into widgets: product cards with selectable options, interactive boarding passes, or live charts.

According to the source, rendering is handled by the compact litehtml engine, while scripts run in a heavily restricted sandbox with CPU limits, network requests blocked, and external media prohibited. You can read all the technical details about these restrictions in the source post.

Editors’ concerns

Despite the extensive list of restrictions, @tginfo editors have serious security concerns about this kind of feature. Integrating web engines that support JavaScript execution — even in a heavily restricted form — directly into the chat interface poses a huge risk.

Experience shows that no matter how thoroughly developers isolate an environment, vulnerabilities are regularly found in rendering systems. The risk of malicious code running simply by viewing a chat raises serious questions about whether these widgets are worth it.

For now, HTMLBubbles is an early experimental concept being tested within the Telegram team. The feature could change substantially during development or be canceled entirely.

#macOS #beta

This video showcases the new search animations. Many find it cool, but not me. What I see in the video are lags and distraction. You?