Remember in 2019 when Google announced that it was giving up on tablets? And then teased the Pixel Tablet in 2022 before ultimately releasing it in 2023? Well, it looks like And now it turns out that the Pixel Tablet will also be joining that list again, though not before getting one more iteration.
There is currently only the first generation Pixel Tablet available on the market. Insiders from Google claim that — though a Pixel Tablet 2 is under the works — there will be no third tablet.Multiple industry sources close to the project have confirmed that the device, internally known as “Kiyomi,” will not be moving forward.
According to sources familiar with the matter, Google made this decision last week, with internal communications and meetings taking place to inform the teams involved. The personnel previously assigned to the Pixel Tablet 3 project are being redirected to other initiatives within the company.
Pixel Tablet 2 is presumably too far into development to quit cold turkey which is why it will allegedly come out next year. However, there’s no saying how long support for it will last if Google has given up on the entire thing.
What does this mean for Google’s tablet?
The Pixel Tablet — something that sounds so appealing on paper — didn’t turn out to be the high-end Android experience we hoped for. Google’s newest tablet, while not bad per se, was nothing special either. The 60 Hz display in particular made it feel very outdated, a problem that is also present on the iPhone 16.
However, instead of working towards improving it and making it the Android contender we need, Google simply abandoning it.As it stands The Pixel Tablet was marketed as some “premium” tablet from Google, when in reality, it looked a lot like a cheap tablet from Five Below. It was pretty cheap compared to other premium tablets like the iPad Air and iPad Pro, as well as Samsung’s Galaxy Tab S series.And Google really can’t charge Apple prices because Android, unlike iOS, isn’t exclusive to Pixel.
This effectively means that the Pixel Tablet 2, when it launches next year, will be a lame duck tablet.
The Digital Wellbeing app is getting a new feature to help you spend less time in distracting apps.Instead of blocking users from using the app, it gently reminds them when they’ve spent too much time on it.
This feature was first spotted in a teardown of the Digital Wellbeing app last month. It has now started showing up for some users.Google has made some changes to the feature since the previous report. It’s now called Screen time reminders instead of Mindful Nudge.
The feature brings up a pill-shaped notification at the top of the screen after you’ve used one of the selected apps for a long time. The notification will show the amount of time you’ve spent on the app, prompting you to close the app and make better use of your time.
You can enable the feature on your phone by navigating to the new Screen time reminders option in the Digital Wellbeing & parental controls settings. Enable the Use reminders option on the following page and select the apps you want to see reminders for to set things up. The feature will then automatically show you a reminder when you spend too much time on one of the selected apps.
This new feature is a welcome addition to the Digital Wellbeing app. It can help users become more aware of how much time they are spending on their phones. This can help them make better choices about how they spend their time and which apps are the ones that tend to be the time-wasters. Although Digital Wellbeing apps in general already do this, the fact that this doesn’t completely lock you out of using the apps, but instead gently nudges you, it’s a different implementation.
Gemini officially landed as a standalone app on Android back in February. Now, only a few days after a stray report about a dedicated Gemini app landing on iOS did the rounds, the Mountain View, California-based tech giant has officially confirmed its launch.
The new app allows iPhone users to interact with Google’s AI through text or voice queries and includes support for Gemini Extensions. A key feature is Gemini Live, which wasn’t available in the previous Google app implementation. When engaged in a conversation, Gemini Live appears in both the Dynamic Island and Lock Screen, letting you control your AI interactions without returning to the main app.You can continue talking to the AI assistant even with your iPhone locked.
The app also aids with learning by allowing users to ask questions on any topic, receive personalized study plans, and access custom, step-by-step guidance tailored to their learning style. Additionally, Gemini can assess knowledge with quizzes, including those based on complex diagrams.
Furthermore, the Gemini iPhone app seamlessly connects with other Google apps through Extensions. This integration enables Gemini to access and display relevant information from apps such as YouTube, Google Maps, Gmail, and Calendar within a single conversation.
The app is free to download, and Google offers premium features through Gemini Advanced subscriptions available as in-app purchases. Gemini Advanced is part of a Google One AI premium plan costing $18.99 per month. Apart from Gemini in Mail, Docs, and more, it includes access to Google’s next-generation model, 1.5 Pro, priority access to new features, and a one million token context window. Users need to sign in with a Google account to access the service.
It’s worth noting that the app is only available for users running iOS 16 and above. Also worth noting is that even though the standalone app is rolling out worldwide, users would only be able to make use of Gemini Live in the following languages:
Android 15 now supports the Wi-Fi Ranging feature for precise indoor tracking and navigation of less than one meter (about forty inches), but that doesn’t mean you can use it today.
Also known as the IEEE 802.11az protocol, Wi-Fi Ranging has the potential to replace indoor GPS tracking, which uses satellites orbiting the Earth to pinpoint our location. But the problem with GPS tracking is that it doesn’t work reliably in places that obstruct the signal, like malls.
Android actually added support for Wi-Fi RTT with the release of Android 9 in 2018, and many mobile devices today have Wi-Fi chips that support the positioning technology. Google even created a demo app to showcase Wi-Fi RTT with FTM, though because there aren’t many AP deployments that support it, you’ll have trouble finding a place to actually try it out in.
While Wi-Fi RTT with FTM is already fairly accurate, the IEEE SA was able to improve upon it even further with the 802.11az standard, also known as Wi-Fi Ranging.
The IEEE SA published the 802.11az standard in March 2023, making it too late to support in 2023’s Android 14 release. However, Google was able to add hardware abstraction layer (HAL) support for the standard in the second quarterly platform release of Android 14. The HAL APIs for Wi-Fi Ranging can be implemented by devices running Android 15 or later, as mentioned by Google in its documentation for Wi-Fi RTT.
You might be wondering why you should care about Wi-Fi Ranging when UWB already exists and Bluetooth 6.0 with Channel Sounding is almost here. Wi-Fi-based positioning offers a superior link budget, has lots of available spectrum to meet growing demand, is compatible with previous generations of Wi-Fi, is scalable to a large number of clients, is adaptive to traffic conditions, is robust to multipath through MIMO, is secure, and is cost effective. Sure compared with UWB and Bluetooth 6’s Channel Sounding, the Wi-Fi Ranging feature is slightly less accurate. On the upside, it has a longer range than either UWB or Bluetooth 6.
Most Android phones don’t have hardware support for Wi-Fi Ranging just yet, but that’s set to change within a couple of years. Qualcomm’s new FastConnect 7900 connectivity chip supports Wi-Fi Ranging, for example, so any upcoming phones that use that chip will be ready. However, many Wi-Fi APs that support Wi-Fi 6 or later will need to receive a firmware update to support 802.11az, so even if your phone were to support it today, you’d need to wait to use it.
Google fixed two actively exploited Android zero-day flaws as part of its November security updates, addressing a total of 51 vulnerabilities: CVE-2024-43047, a flaw affecting Qualcomm chipsets, and CVE-2024-43093, a vulnerability in the Google Play framework.
“There are indications that the following may be under limited, targeted exploitation,” says Google’s advisory.
Qualcomm patched CVE-2024-43047 – a use-after-free vulnerability in the Digital Signal Processor (DSP) service that could be exploited to escalate privileges on targeted devices – in October 2024, and urged original equipment manufacturers (OEMs) to deploy the patches as soon as possible.
CVE-2024-43093 is also a high-severity elevation of privilege flaw,that allows privilege escalation and has been fixed by restricting access to “Android/data,” “Android/obb,” and “Android/sandbox” directories and their sub-directories. This time impacting the Android Framework component and Google Play system updates, specifically in the Documents UI.
While Google did not share any details on how the vulnerabilities were exploited, as researchers at Amnesty International discovered CVE-2024-43047, it could indicate that the flaw was used in targeted spyware attacks.
Propagating fixes in the Android ecosystem
Google issues two patch levels each month, in this case, November 1 (2024-11-01 Patch Level) and November 5 (2024-11-05 Patch Level).
The first level addresses core Android vulnerabilities, with 17 issues this time, while the second patch level encompasses those plus vendor-specific fixes (Qualcomm, MediaTek, etc.), counting an additional 34 fixes this month.
To apply the latest update, head toSettings>System>Software updates>System update.Alternatively, go toSettings>Security & privacy>System & updates>Security update. A restart will be required to apply the update.
Android 11and olderare no longer supported but may receive security updates to critical issues for actively exploited flaws through Google Play system updates, though that’s not guaranteed.
The best course of action for devices still running those older releases should be either to replace them with newer models or use a third-party Android distribution that incorporates the latest security fixes.
Given up on trying to get Google Assistant to dim the lights or pull your drapes? If you’re an Android user, now’s your chance to give Gemini a spin with your smart home.
Google has just released an extension for the Gemini app that allows Google’s LLM to take charge of a wide range of smart gadgets, from smart lights and thermostats to smart shades and TVs.
For now, you’ll need the Android version of the Gemini app, and you’ll also need to be enrolled in Google’s Public Preview program.
Once you’ve enabled the Google Home extension on the Gemini app (this Google support page has all the details), you’ll be able to give smart home commands to Gemini that had previously been executed by Google Assistant.
Google explains that telling Gemini the phrase “the sun is too bright in the living room” will result in the AI assistant closing the smart window blinds in your home. The company also gives an example of using “help me clean up the kitchen” to start a robot vacuum.
There are a few limitations to note, though. It’s only available on Android phones and is restricted to English prompts.For now, only the following categories are supported (according to Google):
Lights & power, like lights, outlets, and switches
Climate control, like air conditioning units, thermostats, heaters, and fans
Window coverings, like curtains, blinds, and shutters
Media devices, like TVs and speakers
Other smart devices, like washers, coffee makers, and vacuums
Google warns that Gemini’s smart-home control abilities are (for the moment, anyway) “for convenience only, not safety- or security-critical purposes.” On devices that don’t have Gemini, you’ll still be using Google Assistant.
Specifically, Gemini can’t do anything with a security device that requires a PIN, stream video feeds from security cams, or perform “some” actions on gates, locks, doors, garage doors, and other security-related devices.
You can try the Google Home extension in the Gemini app now if you’re enrolled in the early preview, and a wider release is likely to follow in the future.
In a major shift of its release cycle, Google has revealed that Android 16 will be released in Q2 of 2025. Google typically pushes out a new major release of Android in Q3 or Q4, but the company has decided to move next year’s major release up by a few months so more devices will get the update sooner.
Google’s updates kicked off by highlighting the future of its Android SDK. In a blog post, the company states it will bring “more frequent” SDK releases, beginning in 2025. Google states it will have a “major” release in Q2 that contains “behavior changes” for apps. This seems to be Android 16 as Google states developers should keep their eyes out for more information regarding its first preview. The company states app developers can prepare for the major Q2 2025 release by conducting the “annual compatibility testing” a few months sooner.
The minor SDK release in Q4 2025 will contain feature updates, optimizations, and bug fixes to clean up any issues with the intended major Q2 launch.
Q1 and Q3 2025 will be minor, offering “feature only” updates to developers, per Google’s set timeline.
Gemini in Android Studio Updates
Following the debut of “Gemini in Android Studio” in April,the company is pushing the boundaries of its AI by boosting its coding capabilities, allowing it to edit your work by “implementing common design patterns.” Several of Gemini’s new code editing features include the ability to “modify and refractor” code based on custom prompts.
A commit message generation feature lets the AI analyze your changes and propose its own set of alterations. “Rethink and rename” lets Gemini generate names for your coding classes, methods, and variables. “Prompt Library” enables the AI to “automatically” save and manage a user’s most frequently used prompts for easy recall. Users can also generate documentation for a select chunk of code by right-clicking.
In the Android Studio, Gemini can now auto-generate “composable” previews and simplify the visualization process for your intended UI. Moreover, “coming soon,” Google says Gemini in Android Studio will support image attachments.
As Gemini in Android Studio picks up a Ladybug feature drop, developers can weed out bugs quicker and (hopefully) see fewer crashes. Additional features include test scenarios using local code context, build/sync error insights, and app quality insights for suggested crash fixes.
Play Store Updates
In a separate blog post, the company states it’s changing how apps are displayed on its store. These new formats include a full-screen mode for portrait videos in an app store listing. Google states a more “prominent” install button should now be visible to users.
Google highlights the Play Store’s “personalized” query recommendations. According to the post, users can find these recommended search queries via the “Search Home.” This is available for English with support for additional languages set to arrive “soon this year.”
Google’s “interest picker” arrived to help the Play Store understand where your interests are for accurate recommendations. The company rolled out a similar tool for games in July.
The post adds that the Play Store delivers a more robust security system when purchasing content. The company says users can now choose “on-device biometrics” when purchasing an app. This includes deciding between using your fingerprint or face to authenticate a purchase instead of inputting your account’s password.
The final two updates for the Play Store involve boosting revenue for developers and their apps alongside Play Integrity API upgrades. Concerning the former, Google states that it has “proactively” encouraged users to assign a payment method on the Play Store and within the Android OS. This has reportedly “doubled the number of purchases” in 2024 and provided a nearly 3% increase in conversion rate.
Payment options have continued to expand as users find options like Paypal, Cash App, direct carrier billing, and more. Additionally, Google highlights its Play Store algorithm for pushing what content users might buy as additional content for their favorite apps.
Google also highlighted its “gentle nudge,” an alert that reminds users of an item they’ve forgotten in their cart.
Google states, “in the coming months,” developers can opt into improved Play Integrity API verdicts to bolster their app’s defenses. What’s more, Google’s “app access risk” feature has exited beta. Developers can now “detect and respond” to apps that capture a user’s screen or control their device to avoid security disasters.
After debuting on the Fitbit Ace LTE, Google Wallet with tap-to-pay will be available next year for kids using Family Link-managed Android devices. The news comes after Google first added the feature to its kid-focused Fitbit Ace LTE fitness tracker in August.
Google tells us today that supervised kids in Family Link will be able to download the Google Wallet app on their Android phones. This will allow them to make tap-to-pay transactions in stores. They won’t, however, be able to use cards saved in Google Wallet for online payments.
Parents can supervise children’s accounts via the Google Family Link app that lets parents set restrictions for content and screen time, and added the ability to see when kids leave school and arrive home in 2022. Meanwhile, their Family Link app will let them view recent transaction history and remotely remove a card, as well as block passes.
Kids will be able to make tap-to-pay purchases using standard authentication options, including fingerprint, facial recognition, PIN, or passwords. They can also use Google Wallet to store gift cards and event tickets, but they can’t make online purchases or save health or identification cards.
Google already built a lot of this infrastructure out for its Wear OS-powered kids smartwatch earlier this year, noting the “the positive response of tap-to-pay on Fitbit Ace LTE.” The company emphasizes how this “new experience is built with safety in mind.”
Google’s kids’ payments feature will start rolling out to Google Wallet users in the US and several other countries next year.With the move, Google is catching up with Apple, whose Apple Cash Family service already lets children use Apple Pay for purchases in stores. It also lets kids buy things online as well as send and receive money through messages.
Google introduced Application-Bound (App-Bound) encryption in July (Chrome 127) as a new protection mechanism that encrypts cookies using a Windows service that runs with SYSTEM privileges.
The goal was to protect sensitive information from infostealer malware, which runs with the permissions of the logged user, making it impossible for it to decrypt stolen cookies without first gaining SYSTEM privileges and potentially raising alarms in security software.
“Because the App-Bound service is running with system privileges, attackers need to do more than just coax a user into running a malicious app,” explained Google in July.
“Now, the malware has to gain system privileges, or inject code into Chrome, something that legitimate software shouldn’t be doing.”
However, by September, multiple information stealers had found ways to bypass the new security feature and provide their cybercriminal customers the ability to once again steal and decrypt sensitive information from Google Chrome.
Google responded by saying that it was expected, and added that it was happy the changed forced a shift in attacker behavior.
“This matches the new behavior we have seen. We continue to work with OS and AV vendors to try and more reliably detect these new types of attacks, as well as continuing to iterate on hardening defenses to improve protection against infostealers for our users.”
Now, security researcher Alexander Hagenah built and shared a tool on GitHub he called ‘Chrome-App-Bound-Encryption-Decryption’ which does the same as these infostealers, BleepingComputer reports.
“This tool decrypts App-Bound encrypted keys stored in Chrome’s Local State file, using Chrome’s internal COM-based IElevator service,” the project page reads. “The tool provides a way to retrieve and decrypt these keys, which Chrome protects via App-Bound Encryption (ABE) to prevent unauthorized access to secure data like cookies (and potentially passwords and payment information in the future).”
Commenting on all of the above, Google essentially said it was satisfied, since crooks now need higher privileges to pull off the attacks:
“This code [xaitax’s] requires admin privileges, which shows that we’ve successfully elevated the amount of access required to successfully pull off this type of attack,” Google said.
Google’s Pixel Watch 5 might get a custom Tensor chip, giving up on Qualcomm as a supplier. This makes sense since Google is also using Tensor chips for its Pixel smartphones, but interestingly the switch will only happen in 2026, so the Pixel Watch 4 will presumably still use a Qualcomm SoC.
That said, the roadmap document that this leak is based on is itself from early 2023, which means a lot could have changed from then and up until now, keep that in mind.
The rumor comes courtesy of Android Authority, which cites leaked documents from Google’s gChips division. According to the leaked plans, the wearable Tensor chip, codenamed NPT, sports a core configuration of an ARM Cortex A78 and two Arm Cortex A55s. These are older CPU cores, but that’s a fairly typical move with wearable processors. Other than that, details are scant and it’s currently unknown which process node technology the planned wearable Tensor chip might have.
Chips aren’t usually as heavy a focus for smartwatches as they are for smartphones. So long as performance is snappy, smartwatch makers tend to focus on ways to prolong battery life without sacrificing smart features. But this is a potentially interesting development given that chip stagnation has historically been a huge obstacle for Android smartwatches.
Both Samsung and Qualcomm use older cores in their smartwatch chips – the Snapdragon W5 Gen 1 has Cortex-A53 cores (which launched in 2012), while the Exynos W1000 has one Cortex-A78 and four Cortex-A55, thus being the most similar to Google’s intended design. That makes us think this wearable Tensor might just be a tweaked Samsung chip – in the same way as all of the smartphone Tensor chips so far have been.
What isn’t known is what process technology this new Tensor chip will use, but it could be 3nm. Another unknown is the modem that will be used.We’ll have to see how things shake out, hopefully this is a sign that it can keep it going.
