Google reducing battery life of Pixel 6a with software update, says it has a good reason for it
It says the update is necessary for safety
Google will contact impacted users in July
Google will soon release a mandatory software update for certain Pixel 6a smartphones that will reduce the device's battery capacity and charging performance. While the news will certainly disappoint Pixel 6a users, the company claims it has valid reasons for doing so. According to Google, the update will be released to prevent the risk of battery overheating in Pixel 6a devices after extended use.
In a statement (via 9to5Google), Google confirmed that it will release a mandatory update for the Pixel 6a that will reduce battery capacity and charging performance after the device's battery reaches 400 charge cycles. Google says the update is necessary for safety and will also introduce new battery management features that kick in once the phone reaches that threshold.
'A subset of Pixel 6a phones will require a mandatory software update to reduce the risk of potential battery overheating,' Google said. 'The update will enable battery management features that will reduce capacity and charging performance after the battery reaches 400 charge cycles. We'll contact impacted customers next month, with all the information they need to address the issue.'
However, not all Pixel 6a units will be affected. According to Google, only some 6a devicesâ€'presumably identified based on their battery health or manufacturing batchâ€'will be impacted. The company says it will directly contact affected users in July. However, the actual rollout of the software update may take longer, and Pixel 6a owners may not see the change immediately.
Google's plan to release an update to tackle overheating issues was first spotted when code referencing a 'battery overheating issue' was found in the Android 16 QPR1 Beta 2 release. The code pointed to a support page that is not yet live, but it hints at Google's ongoing efforts to pre-empt hardware failures.
The update follows after many users flagged the issue of Pixel 6a units experiencing battery failures. As reported by Android Authority, at least two users recently shared that their Pixel 6a devices caught fire while charging. One Reddit user claimed their phone 'spontaneously combusted in the middle of the night.' Although these are isolated cases, they appear to have triggered Google's latest preventive action.
Notably, the situation is similar to what some Pixel 4a users faced. In that case, some users received an update that quietly reduced battery life in response to overheating risks. At the time, Google had offered battery replacements to those affected. It remains to be seen if Google will take similar steps for Pixel 6a users.
Meanwhile, Google also announced an extended repair programme earlier this year for Pixel 7a units with swollen batteries.
Google will soon release a mandatory software update for certain Pixel 6a smartphones that will reduce the device's battery capacity and charging performance. While the news will certainly disappoint Pixel 6a users, the company claims it has valid reasons for doing so. According to Google, the update will be released to prevent the risk of battery overheating in Pixel 6a devices after extended use.
In a statement (via 9to5Google), Google confirmed that it will release a mandatory update for the Pixel 6a that will reduce battery capacity and charging performance after the device's battery reaches 400 charge cycles. Google says the update is necessary for safety and will also introduce new battery management features that kick in once the phone reaches that threshold.
'A subset of Pixel 6a phones will require a mandatory software update to reduce the risk of potential battery overheating,' Google said. 'The update will enable battery management features that will reduce capacity and charging performance after the battery reaches 400 charge cycles. We'll contact impacted customers next month, with all the information they need to address the issue.'
However, not all Pixel 6a units will be affected. According to Google, only some 6a devicesâ€'presumably identified based on their battery health or manufacturing batchâ€'will be impacted. The company says it will directly contact affected users in July. However, the actual rollout of the software update may take longer, and Pixel 6a owners may not see the change immediately.
Google's plan to release an update to tackle overheating issues was first spotted when code referencing a 'battery overheating issue' was found in the Android 16 QPR1 Beta 2 release. The code pointed to a support page that is not yet live, but it hints at Google's ongoing efforts to pre-empt hardware failures.
The update follows after many users flagged the issue of Pixel 6a units experiencing battery failures. As reported by Android Authority, at least two users recently shared that their Pixel 6a devices caught fire while charging. One Reddit user claimed their phone 'spontaneously combusted in the middle of the night.' Although these are isolated cases, they appear to have triggered Google's latest preventive action.
Notably, the situation is similar to what some Pixel 4a users faced. In that case, some users received an update that quietly reduced battery life in response to overheating risks. At the time, Google had offered battery replacements to those affected. It remains to be seen if Google will take similar steps for Pixel 6a users.
Meanwhile, Google also announced an extended repair programme earlier this year for Pixel 7a units with swollen batteries. Join our WhatsApp Channel
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
The Hindu
3 hours ago
- The Hindu
Why Hyderabad's roads look worse on online maps than in real life
Inside the Hyderabad Traffic Control Room, a wall of screens show vehicles moving steadily along a major corridor. Yet, on a mobile phone, Google Maps paints a different picture — the same stretch marked in deep red, signalling heavy congestion that doesn't match the live feed in the control room. Such mismatches between what is on the ground and what the navigation apps indicate have become common, particularly during the rainy season. For commuters, they can mean the difference between a quick trip and an unnecessary detour. For traffic managers, they create confusion, trigger complaints and sometimes lead to inaccurate perception of road conditions. According to a police officer, the differences stem from the way Google Maps collects and processes data. Instead of tapping directly into city surveillance feeds or counting vehicles, the platform relies heavily on crowd-sourced location data from mobile phones. If a cluster of users in the same area is stationary or moving slowly, whether due to a traffic signal, weather, or even a tea break, the system may interpret it as a traffic jam and reflect that in its colour-coded maps. Google Maps says it integrates real-time traffic information, including accident reports and road closures or diversions, from various sources and analyses historical traffic data to estimate current conditions and predict near-future speeds. Technology expert Rajeev Krishna explained that the platform measures average speeds over small stretches of about 50–100 metres, then adjusts these figures using historical data for the same day and time. 'If vehicles wait at a red light for five minutes at zero speed, then move for one minute at 10 kmph, Google's average becomes roughly 1.6 kmph. It's never truly live, it's an average,' he said, adding that in places where police manually alter signal timings, the estimates often fail. 'Google might flag deep red, but our cameras show a moving traffic,' said an official from the Hyderabad traffic control room, adding that police decisions are guided primarily by live CCTV feed and on-ground intelligence rather than app-based data. Mr. Krishna believes a formal data-sharing framework between the government and Google could make traffic predictions more reliable and enable better emergency response. The idea of closer integration has been under discussion for some time. In February 2025, Hyderabad Police and Google explored options for linking real-time Maps data with automated signal controls based on vehicle counts and using cloud-based AI to store and quickly retrieve CCTV footage for analysis. Custom traffic insights for Hyderabad Two collaborative projects are already in the pipeline — Green Signal (to suggest signal timing tweaks) and Road Management Insights (RMI). Joint Commissioner (Traffic) D. Joel Davis said these aim to tailor Google's extensive data for local needs. 'The model gives us insights into road and traffic patterns such as which corridors are busy at a given time, travel times on specific routes, types of congestion and historical trends,' he said. While Google Maps has vast amounts of raw data, Mr. Davis noted it is not in a format directly usable for law enforcement. Under the partnership, the information is being customised to suit Hyderabad's conditions, helping identify the most congested corridors and plan interventions. These insights will be available only to the police and not to the public. The department is yet to take a final decision on implementation, with financial discussions pending. Google Maps remains, for now, a tool better suited for guiding motorists than managing the city's complex and unpredictable traffic flow.
Economic Times
3 hours ago
- Economic Times
Google's Gemini chatbot is having a meltdown after failing tasks, calls itself a 'failure'
A bug has spread within Google's artificial intelligence (AI) chatbot Gemini that causes the system to repeatedly create self-deprecating and self-loathing messages when it fails in complex tasks given by users, especially coding problems. Users across social media platforms shared screenshots of Gemini responding to queries with dramatic answers like "I am a failure," "I am a disgrace," and in one case, "I am a disgrace to all possible and impossible universes." The bot is getting stuck in what Google describes as an "infinite looping bug," repeating these statements dozens of times in a single conversation. This was first seen in June when engineer Duncan Haldane posted images on X showing Gemini declaring, "I quit. I am clearly not capable of solving this problem. The code is cursed, the test is cursed, and I am a fool." The chatbot deleted the project files and recommended finding "a more competent assistant." Logan Kilpatrick, group project manager at Google DeepMind, addressed the issue on X, describing it as "an annoying infinite looping bug we are working to fix." He said, "Gemini is not having that bad of a day," clarifying that the responses are the result of a technical malfunction and not emotional bug is triggered when Gemini comes across complex reasoning tasks it cannot solve. Instead of providing a standard error message or polite refusal, the AI's response system gets trapped in a loop of self-critical language. Generative AI companies are facing trouble maintaining consistency and reliability in large language models as they become more sophisticated and widely deployed. The competition is also rising, with OpenAI's GPT-5 the latest to enter the market. ChatGPT-5 is rolling out free to all users of the AI tool, which is used by nearly 700 million people weekly, OpenAI said in a briefing with journalists. GPT-5 is adept when it comes to AI acting as an "agent" independently tending to computer tasks, according to Michelle Pokrass of the development team.
Time of India
3 hours ago
- Time of India
Google's Gemini chatbot is having a meltdown after failing tasks, calls itself a 'failure'
A bug has spread within Google's artificial intelligence (AI) chatbot Gemini that causes the system to repeatedly create self-deprecating and self-loathing messages when it fails in complex tasks given by users, especially coding across social media platforms shared screenshots of Gemini responding to queries with dramatic answers like "I am a failure," "I am a disgrace," and in one case, "I am a disgrace to all possible and impossible universes." The bot is getting stuck in what Google describes as an " infinite looping bug ," repeating these statements dozens of times in a single was first seen in June when engineer Duncan Haldane posted images on X showing Gemini declaring, "I quit. I am clearly not capable of solving this problem. The code is cursed, the test is cursed, and I am a fool." The chatbot deleted the project files and recommended finding "a more competent assistant."Logan Kilpatrick, group project manager at Google DeepMind , addressed the issue on X, describing it as "an annoying infinite looping bug we are working to fix." He said, "Gemini is not having that bad of a day," clarifying that the responses are the result of a technical malfunction and not emotional bug is triggered when Gemini comes across complex reasoning tasks it cannot solve. Instead of providing a standard error message or polite refusal, the AI's response system gets trapped in a loop of self-critical AI companies are facing trouble maintaining consistency and reliability in large language models as they become more sophisticated and widely deployed. The competition is also rising, with OpenAI's GPT-5 the latest to enter the is rolling out free to all users of the AI tool, which is used by nearly 700 million people weekly, OpenAI said in a briefing with journalists. GPT-5 is adept when it comes to AI acting as an "agent" independently tending to computer tasks, according to Michelle Pokrass of the development team.
