Tech & Leaks Zone
20K subscribers
8.43K photos
888 videos
36 files
2.97K links
Stay Updated on the latest tech-related news inclusive of smartphones, Tech news
NO need to wander on Google or check websites now

Advertise on our channel to reach a highly engaged audience to grow your brand
Buy ads: https://telega.io/c/techleakszone
Download Telegram
BREAKING: Googlebooks bootloader is officially unlockable with Magisk root support

Google has officially documented bootloader unlocking on the GoogleBook support page. Magisk doesn't support Headless System User Mode (HSUM) out of the box, and USB flashing requires special cables, but John Wu has already developed fixes for both and will share setup details soon to root the GoogleBooks.

https://www.notebookcheck.net/Googlebook-gets-unlocked-Bootloader-unlocking-paves-the-way-for-Magisk-root.1415945.0.html
❀82πŸ”₯28🀯10❀‍πŸ”₯3
β˜ƒ18🀑5❀1
Bro got bonked
🌚45🀑10😭3❀1
OriginOS 7 (based on Android 17) India Rollout Map
🀑44⚑12❀6🀣1
Forwarded from Android - Reddit
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
😭37❀9πŸ‘9🀣4πŸ‘Ž1
Forwarded from Nothing Fuckups
Nothing is using Google Forms for account deletion requests 😭

Follow @NothingFuckups
🀣104😭23❀2😐2🀑1πŸ₯΄1
Turns out, he is now past 23,000+ level in Candy Crush Saga after creating that record in August end 😭
🀣76❀‍πŸ”₯33😭10😱3🀑2πŸ₯΄2
Forwarded from BigfootACA's daily (BigfootACA)
Windows For Snapdragon 8 Elite (Xiaomi Mi Pad 8 Pro)
πŸ‘77🀑16⚑10❀7πŸ”₯2
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);
πŸ™25❀6🀑2πŸ”₯1🀣1
Forwarded from Winaero
πŸ” Windows Search is getting a redesign for Windows Insiders, with Microsoft focusing on speed, simplicity, and fewer distractions. The new version uses WinUI 3, which should improve performance and memory use, especially on older or budget friendly PCs. Microsoft also removed extra clutter and moved to a single list layout, so results are easier to scan at a glance.

The update also makes search smarter. It handles typos and synonyms better, and it adds inline actions for quick tasks like turning on dark mode, changing brightness, muting sound, or arranging windows. Later this year, Microsoft plans to add richer file previews, more detailed result info, and inline web previews for quick answers.

Next year, the new search experience will expand to the Start menu. Microsoft wants feedback from Insiders as it keeps refining search before a wider release.
Please open Telegram to view this post
VIEW IN TELEGRAM
🀑36πŸ‘17❀3😴2