Google Pixel 10 series

[limmk]

 

[TopGun]

This update includes a new graphics driver. Any tangible change so far?

 

[limmk]

 

[limmk]

 

[kEvinErd]

Samsung’s new S26 series come with Call Screening now.

Meanwhile, idiotic Google is still geo-blocking Call Screening on Pixel phones which it first introduced not one, not two, not three, not four, not five, not six, not seven, but freaking eight years ago.

 

[Jurong640]

@limmk

 

[limmk]

@limmk

Pixel still wizard with software, but nowadays other brands hardware power too strong already. hard to ignore

 

[Jurong640]

Pixel still wizard with software, but nowadays other brands hardware power too strong already. hard to ignore

come join us

 

[limmk]

come join us

Waiting for the ultra

 

[Jurong640]

Waiting for the ultra

google pixel ultra series?

 

[limmk]

google pixel ultra series?

Vivo x300 ultra lah

 

[Jurong640]

Vivo x300 ultra lah

Ok. i quote first haha

 

[limmk]

 

[limmk]

TL;DR

• Google is introducing a new optimization trick to make the core of Android run faster by studying how phones are actually used.
• The new system analyzes real-world app usage and then reorganizes Android’s code so the most frequently used parts run more efficiently.
• This could result in faster app launches, smoother performance, and better battery life on Android devices over time.

Google is introducing a new optimization trick for the Android kernel, the very core of Android, that could help make phones faster and more efficient.

The company’s Android LLVM toolchain has announced it is bringing Automatic Feedback-Directed Optimization (AutoFDO) to the kernel, implementing lessons learned from real-world smartphone usage into how Android is built. Let’s try and break down what this really means.

The Android kernel is one of the most important parts of the operating system. It sits at the core of Android and manages communication between the CPU, apps, and hardware. According to Google, the kernel accounts for roughly 40% of CPU time on Android devices, so even small improvements here can have a noticeable impact on real-world performance.

When software is compiled, a tool called the compiler prepares the code so your phone can run it. It essentially turns code written by a developer into instructions your phone’s processor can understand. During this process, it also decides how to arrange and optimize that code so it runs as efficiently as possible. However, these decisions are based on general rules and educated guesses rather than on how people actually use their phones.

AutoFDO changes that by letting the compiler learn from real-world usage. To collect this data, Google ran tests in a controlled lab environment using Pixel phones. The tests simulated usage by launching and interacting with the top 100 most popular Android apps, while profiling tools tracked which parts of the kernel were used most often. The system then identifies which parts of the code are “hot” (frequently used) and optimizes the kernel around them.

When the kernel is rebuilt with this data, the compiler can make smarter decisions about how the code is organized. This allows frequently used parts of the system to run more efficiently.

Google says the improvements can translate into faster app launches, smoother performance, quicker app switching, and potentially better battery life.

“We have seen impressive improvements across key Android metrics,” the team noted.
Google is currently deploying kernel AutoFDO in the android16-6.12 and android15-6.6 branches — the versions used by recent Android versions — with plans to expand it to future kernel versions.

Over time, Google wants to apply these optimizations to more parts of the kernel, including extra system components and the hardware drivers that phone makers add for things like cameras and modems.

 

[limmk]

TL;DR

• Pixel phones’ optional 80% charging limit works differently than it used to.
• As of the March update, phones with the setting enabled charge to about 77% at a normal rate, then slow charging drastically from that point to 80%.
• Some users don’t like the new charging behavior, complaining that it makes bypass charging more difficult to achieve.

Like many other modern gadgets, Google’s Pixel phones offer a setting to limit battery charging to 80 percent of maximum capacity to protect long-term battery health. Over the past few days, users have been reporting that with this setting enabled, getting to that 80 percent mark is taking a lot longer than it used to.

A bunch of Pixel users have taken to Reddit (via Android Police) to speak up about this new behavior. It seems like the change is affecting multiple Pixel models and started with the March Pixel Drop that started rolling out earlier this month. As it turns out, though, the new behavior doesn’t seem to be a bug, but rather a conscious change on Google’s part.

Following the March update, with the 80% charging optimization feature enabled, Pixel phones are reaching a charge percentage in the high 70s at a normal rate, but once the phone reaches 77 or 78%, charging slows significantly. One Pixel 10a user on Reddit says their phone is taking “about an hour” to get from 77 to 80%.

Another user shared a screen recording showing that with the 80% limit imposed, their Pixel starts pulling less than one watt at a 77% charge, versus 12 to 14 watts at the same charge level with the setting turned off.

Despite some users’ displeasure with the new behavior, a Google IssueTracker entry about the behavior has been marked as fixed, with a Googler sharing that the new charging pattern is intentional “to manage battery health.”

While the difference in usable battery life unplugging at 77% rather than 80% is down to a few minutes of screen time, plenty of users are calling on Google to roll back the change, or at least make it optional. A common complaint is that the new behavior makes so-called bypass charging — where the phone operates on power from the charger without actively charging the battery — harder to achieve. As the battery sips power at a very low rate near the 80% ceiling, it might never reach a full charge if the phone is in use while charging.

Have you noticed this new charging optimization limitation on your own Pixel? Do you care one way or the other? Let us know in the comments.

 

[limmk]

TL;DR

• Google is introducing a new optimization trick to make the core of Android run faster by studying how phones are actually used.
• The new system analyzes real-world app usage and then reorganizes Android’s code so the most frequently used parts run more efficiently.
• This could result in faster app launches, smoother performance, and better battery life on Android devices over time.

Google is introducing a new optimization trick for the Android kernel, the very core of Android, that could help make phones faster and more efficient.

The company’s Android LLVM toolchain has announced it is bringing Automatic Feedback-Directed Optimization (AutoFDO) to the kernel, implementing lessons learned from real-world smartphone usage into how Android is built. Let’s try and break down what this really means.

The Android kernel is one of the most important parts of the operating system. It sits at the core of Android and manages communication between the CPU, apps, and hardware. According to Google, the kernel accounts for roughly 40% of CPU time on Android devices, so even small improvements here can have a noticeable impact on real-world performance.

When software is compiled, a tool called the compiler prepares the code so your phone can run it. It essentially turns code written by a developer into instructions your phone’s processor can understand. During this process, it also decides how to arrange and optimize that code so it runs as efficiently as possible. However, these decisions are based on general rules and educated guesses rather than on how people actually use their phones.

AutoFDO changes that by letting the compiler learn from real-world usage. To collect this data, Google ran tests in a controlled lab environment using Pixel phones. The tests simulated usage by launching and interacting with the top 100 most popular Android apps, while profiling tools tracked which parts of the kernel were used most often. The system then identifies which parts of the code are “hot” (frequently used) and optimizes the kernel around them.

When the kernel is rebuilt with this data, the compiler can make smarter decisions about how the code is organized. This allows frequently used parts of the system to run more efficiently.

Google says the improvements can translate into faster app launches, smoother performance, quicker app switching, and potentially better battery life.

“We have seen impressive improvements across key Android metrics,” the team noted.
Google is currently deploying kernel AutoFDO in the android16-6.12 and android15-6.6 branches — the versions used by recent Android versions — with plans to expand it to future kernel versions.

Over time, Google wants to apply these optimizations to more parts of the kernel, including extra system components and the hardware drivers that phone makers add for things like cameras and modems.

 

[leon0079]

anyone has issue with singpass face scanning?

Reset the app and managed to complete the singpass but kept failing during my maribank login.

Error showing screen brightness too low and keeps failing. So frustrating as I'm trying to login my Maribank account and had to switch my singpass account to another phone to get the bank verification completed.

Done then I switched back my singpass account to my fold. darn troublesome

 

[TakKiu]

Stand at a well lit area, turn your phone to max brightness.

 

[halocast]

anyone has issue with singpass face scanning?

Reset the app and managed to complete the singpass but kept failing during my maribank login.

Error showing screen brightness too low and keeps failing. So frustrating as I'm trying to login my Maribank account and had to switch my singpass account to another phone to get the bank verification completed.

Done then I switched back my singpass account to my fold. darn troublesome

Needs to be in a well lit but not too bright until face overexposed

 

[ahboon83]

anyone has issue with singpass face scanning?
Reset the app and managed to complete the singpass but kept failing during my maribank login.
Error showing screen brightness too low and keeps failing. So frustrating as I'm trying to login my Maribank account and had to switch my singpass account to another phone to get the bank verification completed.
Done then I switched back my singpass account to my fold. darn troublesome

I also have this issue on my Pixel 10 pro

I solved it by looking at the screen instead of the front camera, I failed more than 20 times when looking at the front camera



Read HWZ Forum Rules!