Tech & Leaks Zone

Windows For Snapdragon 8 Elite (Xiaomi Mi Pad 8 Pro)

Now he is already past 23,000 levels in Candy Crush Saga 😭

Nothing is using Google Forms for account deletion requests 😭 Follow @NothingFuckups

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

Anthropic is catching with OpenAI https://fixvx.com/luckeyfaraday/status/2107445352622415935?s=46

OriginOS 7 India Rollout Map

Bro got bonked

BREAKING: Googlebook bootloader is officially unlockable, Magisk root confirmed by John Wu Google has officially documented bootloader unlocking on the GoogleBook support page. Meanwhile, John Wu announced on X that the GoogleBook will be rootable as well. Magisk doesn't support Headless System User Mode (HSUM) out of the box, and USB flashing requires special cables, but he has already developed fixes for both and will share setup details soon. https://www.notebookcheck.net/Googlebook-gets-unlocked-Bootloader-unlocking-paves-the-way-for-Magisk-root.1415945.0.html

GoogleBook is such a good name ...

https://github.com/Maikyxd/val-protocol Source of truth.

And, time to kill marketplace created by those gsm tools dev. Due to licensing issues from original developer, it will not become into a feature of lmnflash (which is MIT licensed), but a separated program.

Here's how YouTube looks on the iPhone Duo

AEmulator - Android emulator that simulates older android firmware https://aemulator.gt.tc/ https://redd.it/1wu4a9b @reddit_android