Google Pixel 11 Series RGB Torch feature aka the rumoured Pixel Glow would instead be called as 'HiLight'
The name "Pixel Glowβ first appeared within Android 17 Beta 4. The description says that it uses βsubtle light and color on the back of your device to inform you of important activity when itβs face down.β
Some of its use cases:
β’ Calls from favorites: Subtle lights when your favorite contacts call you
β’ Speaking with Gemini: Hands-free interactions using visual feedback
Via evowizz
Follow @TechLeaksZone
The name "Pixel Glowβ first appeared within Android 17 Beta 4. The description says that it uses βsubtle light and color on the back of your device to inform you of important activity when itβs face down.β
Some of its use cases:
β’ Calls from favorites: Subtle lights when your favorite contacts call you
β’ Speaking with Gemini: Hands-free interactions using visual feedback
Via evowizz
Follow @TechLeaksZone
π€‘58πΏ7β€4β3π1π€1π1π1
Your first look at the Google Pixel Tag
Looks wise, the βPixel Tagβ has an oblong shape similar to the Samsung Galaxy SmartTag. Googleβs tracker also seems to lack any sort of built-in mounting mechanism, likely relying on cases similar to Appleβs tracker.
Follow @TechLeaksZone
Looks wise, the βPixel Tagβ has an oblong shape similar to the Samsung Galaxy SmartTag. Googleβs tracker also seems to lack any sort of built-in mounting mechanism, likely relying on cases similar to Appleβs tracker.
The Google Pixel Tag smart tracker helps you quickly and reliably locate your lost items using the secure βFind My Deviceβ network.
Never waste time searching for your keys, wallet or luggage again. The Google Pixel Tag is a compact, lightweight and durable smart tracker that attaches discreetly to your most important items. Using Googleβs extensive and secure βFind My Deviceβ network, you can always check the exact location of your belongings via your smartphone. The tracker is equipped with a loud speaker for easy nearby search and is designed with your privacy and personal data in mind.
Follow @TechLeaksZone
β€32π€¨15π3π2
BREAKING: Google will restrict 3rd party apps from checking whether ADB over USB and Developer Options are enabled on the device
Google has added a commit which says:
The description of the commit notes:
However, this commit was pushed on 23rd March, 2026. So it's currently unknown when this change goes live. Nevertheless, just enable it through flagflipper once the flag is added.
Follow @TechLeaksZone
Google has added a commit which says:
Add redactedValue for ADB_ENABLED and DEVELOPMENT_SETTINGS_ENABLED
The description of the commit notes:
We update ADB_ENABLED and DEVELOPEMENT_SETTINGS_ENABLED to have a redactedValue of 0, since this information is not important for the third-party apps.This is a big relief because banking apps will no longer be able to check whether Developer Options and ADB are turned on on your smartphone; thus, banking apps will continue to function normally.
However, this commit was pushed on 23rd March, 2026. So it's currently unknown when this change goes live. Nevertheless, just enable it through flagflipper once the flag is added.
Follow @TechLeaksZone
β€βπ₯187β€22π₯8π4β‘3π3π€2π€‘2π―2π1
Forwarded from Tadi Channel
https://arstechnica.com/gadgets/2026/07/google-plans-to-exempt-sanctioned-nations-from-android-developer-verification/
If it's not funny, I don't know what is...
If it's not funny, I don't know what is...
Ars Technica
Google plans to exempt sanctioned nations from Android developer verification
Someone in Cuba or Iran can keep installing APKs with no new restrictions, but devs will suffer.
π€‘63π₯°6β€3π1π₯1
Forwarded from Tadi Channel
https://www.reddit.com/r/GalaxyS24Ultra/comments/1to1lkp/why_is_the_automatic_protection_blocking_random/
Samsung has a feature (enabled by default) that replaces the rendered image outputs when their algorithm considers them malicious. It seemingly broke.
The most major problem with it is data loss. Some apps will only keep an on-device processed (passed through renderer) copy and that may mean an irreversible loss of media that you captured or received. Not a hyperbole.
Samsung has a feature (enabled by default) that replaces the rendered image outputs when their algorithm considers them malicious. It seemingly broke.
The most major problem with it is data loss. Some apps will only keep an on-device processed (passed through renderer) copy and that may mean an irreversible loss of media that you captured or received. Not a hyperbole.
π€23π3
Forwarded from OPlus Fuckups
That was NOT fake
OnePlus support confirmed N6X has eMMC 5.1 πππ
https://fixvx.com/i/status/2083873888103276547
OnePlus support confirmed N6X has eMMC 5.1 πππ
https://fixvx.com/i/status/2083873888103276547
vxTwitter / fixvx
π 308 π 7
π 308 π 7
Beebom (@beebomco)
OnePlus Support has confirmed that the OnePlus N6x does come with eMMC 5.1 onlyπ
π€‘62π€£15β€2
Forwarded from Yekni Tek
Everything started today, I got bored saw my l950 and decided to do something with it. Year ago I couldnβt add ril my self so I thought maybe ai can do something, I mean they release strong models, spend trillions of money into ai. I explained this project to gemini. It told me that Microsoft devices communicate with modem in special ways, unlike android modem driver which lives in the software, these phones drivers live in the modem it self, with android logic is android wants to use modem tells to driver and driver tells modem to do this send this voltage etc. in lumia phones logic is w10m wants to use modem tells to modem, and the microcode in the modem itself decides what to do like powering the 14th pin etc.(In a nutshell) After Gemini explained this told me that this is actually breakable and set modem to understand android way. Asked me if I wanted to proceed I said yes, that it wanted me to dump some information from w10m to get some kind of information. Then I told Gemini that drivers actually exists on Lumia WOAs GitHub. Then Gemini wanted me to give him some files and said I can make modifications to kernel, wanted me to give the kernel so I gave the link to android4lumia GitHubβs spyxinks kernel(I couldnβt typed that sorry). After a while a lot of back and forth it eventually came up with a new kernel told me to build the rom so I did it and after that I got noting so screen nothing told the Gemini that nothing on the screen, so I went to kitchen to drink water and when I came back there were smoke coming from my device, I immediately disconnected the battery waited for phone to cool down. Tried to restore to w10m and surprise surprise windows phone internals or even windows didint even detected it. I opened up the inside carefully gave some power and yeah some chip imediately hated up to 90C which I think is the modem or maybe cpu I have no idea what that thing is, trowed phone to trash deleted my Gemini account Fujk Gemini fujk Microsoft fujk my self for thinking this would work at the beginning.
π€£72π7β€2π₯1π1π1
Tech & Leaks Zone
it eventually came up with a new kernel told me to build the rom so I did it and after that I got noting so screen nothing told the Gemini that nothing on the screen, so I went to kitchen to drink water and when I came back there were smoke coming from my device, I immediately disconnected the battery waited for phone to cool down
TLDR:
- Bro wanted RIL on Android On Lumia950
- asked gemini
- gemini shat out kernel
- phone started smoking
Hahahahahahahahahahahahahaha
- Bro wanted RIL on Android On Lumia950
- asked gemini
- gemini shat out kernel
- phone started smoking
Hahahahahahahahahahahahahaha
π€£82π€‘2π1π1
Anybody with esim broken/failure issues on their Google Pixel 9 series willing to test a fix?
π€‘36π5
Forwarded from GApps Leaks
On bootloader unlocked Google Pixel devices, Google restricts users from using Custom icons feature in the Pixel Launcher.
In a recent update, they have added a clear warning when it can't download app icons - The device doesn't meet security requirements. A warning which many Google Wallet users might have been familiar with on rooted devices.
Google already restricts various other AI features on Pixel devices with unlocked bootloader.
@GappsLeaks
In a recent update, they have added a clear warning when it can't download app icons - The device doesn't meet security requirements. A warning which many Google Wallet users might have been familiar with on rooted devices.
Google already restricts various other AI features on Pixel devices with unlocked bootloader.
@GappsLeaks
π€‘167π€£24π10π₯3β€1π«‘1
Forwarded from PUI The Newsroom π (β±β³β¦β± )
The string name and logo have been unified; the OOS and RUI test versions now all display the Color OS logo.
β€βπ₯30π6π4β€3β‘2π2π€‘1π¨βπ»1π1
Forwarded from Tentacles Channel
Pixel eSIM eUICC Fix Guide
> β οΈ Warning: This process requires root access. Your eID may be regenerated, which can affect existing eSIM profiles. Back up anything important and be prepared to download or reactivate your eSIM afterward.
Requirements
β’ Rooted Pixel device
β’ USB debugging enabled
β’ A computer with ADB configured
Step 1 β Open an ADB shell
Connect the phone to your computer, then run:
Step 2 β Obtain root access
Inside the ADB shell, run:
Grant the root request on the phone if prompted.
Step 3 β Set temporary system properties
Run the following commands one at a time in the same root shell:
Step 4 β Restart framework
Run:
The phone will reboot. Do not close the ADB shell. Once Android has fully booted, unlock the phone and continue using the same shell session.
Step 5 β Open the firmware updater app
Run:
NFC/eSE/eSIM firmware updater application should now open on the phone.
Step 6 β Select the firmware
1. Open the Upgrade Firmware drop-down menu.
2. Select:
3. Tap SE FIRMWARE UPGRADE.
4. Tap CONTINUE to confirm.
Step 7 β Wait for completion
Wait until the process finishes. Do not reboot the phone, disconnect anything, or close the upgrade application while the firmware update is in progress.
Step 8 β Reboot the phone
After the firmware upgrade has completed successfully, reboot the phone normally.
You can restart it from the power menu or run:
Once the phone has booted and eSIM/eUICC functionality is working, the device is fixed and ready for normal use. You can now clean-flash the device or relock the bootloader if needed.
Done.
> β οΈ Your eID may be regenerated after the update. If your existing eSIM profile no longer works, contact your carrier or use its app/website to issue and install a new eSIM profile.
XDA Thread
Full guide and discussion:
XDA: Pixel eSIM / eUICC Fix Guide
Tentacles Channel. Subscribe.
> β οΈ Warning: This process requires root access. Your eID may be regenerated, which can affect existing eSIM profiles. Back up anything important and be prepared to download or reactivate your eSIM afterward.
Requirements
β’ Rooted Pixel device
β’ USB debugging enabled
β’ A computer with ADB configured
Step 1 β Open an ADB shell
Connect the phone to your computer, then run:
adb shell
Step 2 β Obtain root access
Inside the ADB shell, run:
su
Grant the root request on the phone if prompted.
Step 3 β Set temporary system properties
Run the following commands one at a time in the same root shell:
resetprop ro.build.type eng
resetprop ro.build.tags eng
resetprop ro.debuggable 1
setenforce 0
Step 4 β Restart framework
Run:
stop && sleep 2 && start
The phone will reboot. Do not close the ADB shell. Once Android has fully booted, unlock the phone and continue using the same shell session.
Step 5 β Open the firmware updater app
Run:
am start -n com.google.euiccpixel/com.google.euiccpixel.ui.OtaUpdateMenu
NFC/eSE/eSIM firmware updater application should now open on the phone.
Step 6 β Select the firmware
1. Open the Upgrade Firmware drop-down menu.
2. Select:
GGL_P24_ST54L_GSMALIVE_534-1.1_DVT_CC9_v2
3. Tap SE FIRMWARE UPGRADE.
4. Tap CONTINUE to confirm.
Step 7 β Wait for completion
Wait until the process finishes. Do not reboot the phone, disconnect anything, or close the upgrade application while the firmware update is in progress.
Step 8 β Reboot the phone
After the firmware upgrade has completed successfully, reboot the phone normally.
You can restart it from the power menu or run:
reboot
Once the phone has booted and eSIM/eUICC functionality is working, the device is fixed and ready for normal use. You can now clean-flash the device or relock the bootloader if needed.
Done.
> β οΈ Your eID may be regenerated after the update. If your existing eSIM profile no longer works, contact your carrier or use its app/website to issue and install a new eSIM profile.
XDA Thread
Full guide and discussion:
XDA: Pixel eSIM / eUICC Fix Guide
Tentacles Channel. Subscribe.
β€29π€‘3π2β€βπ₯1
Google Pixel 11 Pro will get 120X Zoom. So expect a new telephoto sensor
π«‘61π€‘21β6β€4π3