Finally the Fold we’ve been waiting for? Samsung Galaxy Z Fold8 review
https://www.notebookcheck.net/Shooting-to-the-top-with-a-new-form-factor-Samsung-Galaxy-Z-Fold8-review.1394389.0.html
https://redd.it/1wbwg8p
@reddit_android
https://www.notebookcheck.net/Shooting-to-the-top-with-a-new-form-factor-Samsung-Galaxy-Z-Fold8-review.1394389.0.html
https://redd.it/1wbwg8p
@reddit_android
Notebookcheck
Shooting to the top with a new form factor? - Samsung Galaxy Z Fold8 review
Samsung Galaxy Z Fold8 review: How does Samsung’s new foldable smartphone perform in everyday life? We evaluate the display, performance, camera, battery, and usability, and reveal exactly who the Fold8 is for—as well as where this foldable flagship still…
CXMT Pioneers Mass-Production of LPDDR6
https://www.cxmt.com/en/news/info_21.html
https://redd.it/1wbpbbi
@reddit_android
https://www.cxmt.com/en/news/info_21.html
https://redd.it/1wbpbbi
@reddit_android
Cxmt
CXMT Pioneers Mass-Production of LPDDR6 - Newsroom - CXMT
desc
Honor Magic9 series to debut on September 28, design revealed
https://gsmarena.com/honor_magic9_series_to_debut_on_september_28_design_revealed-news-74526.php
https://redd.it/1wbqdn4
@reddit_android
https://gsmarena.com/honor_magic9_series_to_debut_on_september_28_design_revealed-news-74526.php
https://redd.it/1wbqdn4
@reddit_android
GSMArena.com
Honor Magic9 series to debut on September 28, design revealed
The series is also available for pre-order in China. Honor has announced the launch date for its upcoming Magic9 flagship series. Alongside, it has...
SemiAnalysis: Here's an exclusive first look at Samsung's upcoming Exynos 2700 smartphone SoC on their SF2P process! Samsung doubles the prime core count to two with this generation, following others in the industry. We look forward to taking a closer look at this chip when it arrives in 2027!
https://xcancel.com/SemiAnalysis_/status/2095135407163801708
https://redd.it/1wbrgnk
@reddit_android
https://xcancel.com/SemiAnalysis_/status/2095135407163801708
https://redd.it/1wbrgnk
@reddit_android
Google Pixel Tablet has been discontinued, out of stock everywhere
https://9to5google.com/2026/09/09/google-pixel-tablet-discontinued/
https://redd.it/1wcc6pt
@reddit_android
https://9to5google.com/2026/09/09/google-pixel-tablet-discontinued/
https://redd.it/1wcc6pt
@reddit_android
9to5Google
Google Pixel Tablet has been discontinued, out of stock everywhere
Google Pixel Tablet has been quietly discontinued, with sales have ended not only from Google, but everyone else too.
Google Pixel 11 early review (2 days): Switching to Android after nearly staying with iOS for nearly one decade!!!
Hey y'all,
So awhile back I made a post where I announced that I'm switching to android after spending a near decade on iOS (my previous phone was iPhone 14). So, here is my point wise early 2 days review for Google Pixel 11, as some of the guys challenged me that I won’t last 2-3 days with this phone. (This will be a long one)
1. In Hand Feel: The inhand feel of this device uncannily reminds me of an iPhone 16/17, especially from the sides and the slightly curved back. Its like that Google deliberately made this to attract iPhone users, but hey I aint complaining, it feels really sturdy, rock solid and very premium to hold this device. To some extent like Google's own take on iPhone.
2. Operating Software: So, i know this topic is hot cake of a debate on its own. But I'm going to say this without giving a damn about how the user reading this might feel....Android is the undefeated King of the Operating Software and I regret not trying android earlier. The OS on this thing is super duper majesticly customisable. Oh my gawdddddddd, the things I can do with the customisation including the level of depthness of each thing which you can change under the settings (i know that this is all surface level stuff, but hey its been only 2 days since I made the switch, so pls bear with me). This is so freaking good. Now prior to using this device I had a conception for android that "They are slow and bloated to hell", but man I was so wrong. Changing a phone is a big decision and that too while trying a brand which has its own very niche audience is equivalent to making a risky investment in a small cap stocks, either you win big or lose a lifetime. And I'm so glad that I did my research before I made the switch, I'm so glad to say this that I did not make a mistake when I went with Android.
PS - After reading the comments I did my further research and decided to go with stock android (i know that Pixel UI is not stock android, but hey its closest to being one).
3. Camera: This is one area where I have mixed feeling, the camera on this device are super great, but coming from the iPhone they somehow feel a bit different, like something that I'm not so accustomed to see. In any regard, I aint saying that they arent equally good as an iPhone, but one place where I can see the difference has to be the video. This takes utmost honesty to say this......iPhones have the upper hand when it comes down to the video department.
4. Battery: This is the most grey area when it comes to owning Pixel, while most of the users said that the Pixel have a terrible battery.......however, in my personal use case scenario........I did not face the issue. So, my answer needs a bit of context:
My day starts at 5 in the morning, so my pixel is charged at 100% at 5'o clock in the morning. I hit the gym, listen to some music, track workouts on lyfta app. I listen to music for like 3-4hrs per day...yuppp I'm an audiophile in that regards. Then i do some pretty basic stuff which most of us do, phone calls, whatsapp, text messages, draft some mails and then few vc's here and there, then do some general stuff with gemini, and no I do not play games on my mobile device. My daily life does not involve hardware intensive task. So, after unplugging from the charger at 5'o clock and ending my day around 11'o clock.....I'm still left with 25% battery. So, I'll let you be the judge on that!!!!
PS - Unlike other users, my device did not throttle a single bit, and also not to mention the very common complaint from Pixel owners, "the device throttles when you use it on mobile data".....well I can say this that my device did not even get warm when using on mobile data, Google did a fabulous job when it switched to Mediatek modems for the Pixel 11 series.
5. Gaming: As mentioned above I do not play games, so I cannot comment on this aspect of the device.
Ending Note: I suggest that if you are one of those guys who
Hey y'all,
So awhile back I made a post where I announced that I'm switching to android after spending a near decade on iOS (my previous phone was iPhone 14). So, here is my point wise early 2 days review for Google Pixel 11, as some of the guys challenged me that I won’t last 2-3 days with this phone. (This will be a long one)
1. In Hand Feel: The inhand feel of this device uncannily reminds me of an iPhone 16/17, especially from the sides and the slightly curved back. Its like that Google deliberately made this to attract iPhone users, but hey I aint complaining, it feels really sturdy, rock solid and very premium to hold this device. To some extent like Google's own take on iPhone.
2. Operating Software: So, i know this topic is hot cake of a debate on its own. But I'm going to say this without giving a damn about how the user reading this might feel....Android is the undefeated King of the Operating Software and I regret not trying android earlier. The OS on this thing is super duper majesticly customisable. Oh my gawdddddddd, the things I can do with the customisation including the level of depthness of each thing which you can change under the settings (i know that this is all surface level stuff, but hey its been only 2 days since I made the switch, so pls bear with me). This is so freaking good. Now prior to using this device I had a conception for android that "They are slow and bloated to hell", but man I was so wrong. Changing a phone is a big decision and that too while trying a brand which has its own very niche audience is equivalent to making a risky investment in a small cap stocks, either you win big or lose a lifetime. And I'm so glad that I did my research before I made the switch, I'm so glad to say this that I did not make a mistake when I went with Android.
PS - After reading the comments I did my further research and decided to go with stock android (i know that Pixel UI is not stock android, but hey its closest to being one).
3. Camera: This is one area where I have mixed feeling, the camera on this device are super great, but coming from the iPhone they somehow feel a bit different, like something that I'm not so accustomed to see. In any regard, I aint saying that they arent equally good as an iPhone, but one place where I can see the difference has to be the video. This takes utmost honesty to say this......iPhones have the upper hand when it comes down to the video department.
4. Battery: This is the most grey area when it comes to owning Pixel, while most of the users said that the Pixel have a terrible battery.......however, in my personal use case scenario........I did not face the issue. So, my answer needs a bit of context:
My day starts at 5 in the morning, so my pixel is charged at 100% at 5'o clock in the morning. I hit the gym, listen to some music, track workouts on lyfta app. I listen to music for like 3-4hrs per day...yuppp I'm an audiophile in that regards. Then i do some pretty basic stuff which most of us do, phone calls, whatsapp, text messages, draft some mails and then few vc's here and there, then do some general stuff with gemini, and no I do not play games on my mobile device. My daily life does not involve hardware intensive task. So, after unplugging from the charger at 5'o clock and ending my day around 11'o clock.....I'm still left with 25% battery. So, I'll let you be the judge on that!!!!
PS - Unlike other users, my device did not throttle a single bit, and also not to mention the very common complaint from Pixel owners, "the device throttles when you use it on mobile data".....well I can say this that my device did not even get warm when using on mobile data, Google did a fabulous job when it switched to Mediatek modems for the Pixel 11 series.
5. Gaming: As mentioned above I do not play games, so I cannot comment on this aspect of the device.
Ending Note: I suggest that if you are one of those guys who
do not have hardware intensive tasks and you are someone who just want the ultimate stock android feel, then please whole heartedly go for the Pixel, you wont regret it. At the conclusion, I just want to say this............I wish I had done it sooner. I'm never ever going back to iOS again in my life. Pixel is my way to go!!!!!!
https://redd.it/1wbsd6z
@reddit_android
https://redd.it/1wbsd6z
@reddit_android
Reddit
From the Android community on Reddit
Explore this post and more from the Android community
More ways to enjoy your Xperia! Introducing Android™ 17
https://www.sony.co.uk/electronics/support/articles/00409051
https://redd.it/1wbqcvn
@reddit_android
https://www.sony.co.uk/electronics/support/articles/00409051
https://redd.it/1wbqcvn
@reddit_android
Switching password managers is easy and safe on Android
https://blog.google/products-and-platforms/platforms/android/switch-password-managers/
https://redd.it/1wcnin1
@reddit_android
https://blog.google/products-and-platforms/platforms/android/switch-password-managers/
https://redd.it/1wcnin1
@reddit_android
Google
Switching password managers is easy and safe on Android
A new Android feature lets you securely transfer passwords and passkeys between password managers.
Google Play's Early Access program may be exploited by potentially deceptive apps
https://www.bitdefender.com/en-us/blog/hotforsecurity/google-play-early-access-exploit-deceptive-apps
https://redd.it/1wcvq5e
@reddit_android
https://www.bitdefender.com/en-us/blog/hotforsecurity/google-play-early-access-exploit-deceptive-apps
https://redd.it/1wcvq5e
@reddit_android
Bitdefender
Google Play's Early Access program may be exploited by potentially deceptive apps
Google Play Early Access can hide public ratings and reviews, making it easier for misleading apps to avoid scrutiny before release.
Exclusive: Galaxy Buds On Design and Features Revealed
https://sammyguru.com/exclusive-galaxy-buds-on-design-and-features-revealed/?utm_source=twitter&utm_medium=social&utm_campaign=2026-09-10&utm_content=exclusive-galaxy-buds-on-design-and-features-revealed
https://redd.it/1wcvf2d
@reddit_android
https://sammyguru.com/exclusive-galaxy-buds-on-design-and-features-revealed/?utm_source=twitter&utm_medium=social&utm_campaign=2026-09-10&utm_content=exclusive-galaxy-buds-on-design-and-features-revealed
https://redd.it/1wcvf2d
@reddit_android
SammyGuru
Exclusive: Galaxy Buds On Design and Features Revealed
Exclusive: our first real look at the Galaxy Buds On, aka Galaxy Buds Able. Two rounded bulbs on a curved arm, plus Auto Volume, Volume Boost and no ANC.
Wide Motorola razr foldable teaser [at 0:05]
https://xcancel.com/Moto/status/2097746209247244714
https://redd.it/1wd1lkb
@reddit_android
https://xcancel.com/Moto/status/2097746209247244714
https://redd.it/1wd1lkb
@reddit_android
Nitter
motorola (@Moto)
That feeling when you hang up, and your razr says everything you didn’t. 😏
Some are just discovering it. We’ve been making it even better.
Just wait for our next move. 👀
#Razr
Some are just discovering it. We’ve been making it even better.
Just wait for our next move. 👀
#Razr
Vivaldi 8.2 for mobile: Your browser. Your rules. Your extensions.
https://vivaldi.com/blog/vivaldi-on-mobile-8-2/
https://redd.it/1wcj209
@reddit_android
https://vivaldi.com/blog/vivaldi-on-mobile-8-2/
https://redd.it/1wcj209
@reddit_android
Vivaldi Browser
Vivaldi 8.2 for mobile: Your browser. Your rules. Your extensions. | Vivaldi Browser
Vivaldi hands you every tool you need to browse on your own terms. With our latest update, Vivaldi 8.2, we give you more. Or rather everything, with full extension support on Android, so you can shape…
Swiftkey Copies Pixel 11's Awesome Rambler Feature
https://www.droid-life.com/2026/09/11/swiftkey-copies-pixel-11s-awesome-rambler-feature/
https://redd.it/1wdl6ip
@reddit_android
https://www.droid-life.com/2026/09/11/swiftkey-copies-pixel-11s-awesome-rambler-feature/
https://redd.it/1wdl6ip
@reddit_android
Droid Life
Swiftkey Copies Pixel 11’s Awesome Rambler Feature
With the arrival of the Pixel 11 series, it’s clear now that the star of the launch is the new Rambler voice-to-text feature. We’ve talked about it a number of times now, but other new Pixel 11 owners are talking about it just as much. Unfortunately, this…
Poco X8 Power with a 10,000mAh battery goes on sale in India
https://www.gsmarena.com/poco_x8_power_with_a_10000mah_battery_goes_on_sale_in_india-news-74578.php
https://redd.it/1wdj6g4
@reddit_android
https://www.gsmarena.com/poco_x8_power_with_a_10000mah_battery_goes_on_sale_in_india-news-74578.php
https://redd.it/1wdj6g4
@reddit_android
GSMArena.com
Poco X8 Power with a 10,000mAh battery goes on sale in India
It’s powered by the Snapdragon 6 Gen 5 chipset. The Poco X8 was unveiled globally earlier this month, followed by its India launch alongside the X8 Power...
This stylish smartphone is practically indestructible and almost never lets you down—Honor X80 Pro Max Smartphone Review
https://www.notebookcheck.net/This-stylish-smartphone-is-practically-indestructible-and-almost-never-lets-you-down-Honor-X80-Pro-Max-Smartphone-Review.1396849.0.html
https://redd.it/1wdr50h
@reddit_android
https://www.notebookcheck.net/This-stylish-smartphone-is-practically-indestructible-and-almost-never-lets-you-down-Honor-X80-Pro-Max-Smartphone-Review.1396849.0.html
https://redd.it/1wdr50h
@reddit_android
Notebookcheck
This stylish smartphone is practically indestructible and almost never lets you down—Honor X80 Pro Max Smartphone Review
The Honor X80 Pro Max is drop-resistant, can be submerged up to 10 meters, is suitable for use in dusty environments, and can last through even a demanding day thanks to its 11,000-mAh battery. A phone for every situation? We took a closer look at this rugged…
Exclusive: Here’s Your First Look at the Galaxy SmartTag 3
https://sammyguru.com/exclusive-samsung-galaxy-smarttag-3-design/
https://redd.it/1wdtmu5
@reddit_android
https://sammyguru.com/exclusive-samsung-galaxy-smarttag-3-design/
https://redd.it/1wdtmu5
@reddit_android
SammyGuru
Exclusive: Here's Your First Look at the Galaxy SmartTag 3
Exclusive first look at Samsung's upcoming Galaxy SmartTag 3 reveals its new squircle design and two color options. Take a look.
Introducing ROMVERSE — an Android ROM engineering platform I’m building at RadForge Labs
Currently In Alpha Stage
Hey everyone! I’m Steve, and I’d like to introduce RadForge Labs, my independent Australian software studio, and the project I’ve been putting my time into: ROMVERSE.
The idea is to make working with Android devices and firmware more understandable without taking useful technical control away from experienced modders and developers.
What is ROMVERSE?
ROMVERSE is being developed as a desktop workspace that brings together device information, firmware inspection, ROM customisation, build preparation, diagnostics and recovery preparation. The longer-term goal is a connected workflow from understanding your device and preparing a project through to verified, carefully controlled device operations.
A major focus is making that experience work for different skill levels:
Guided mode: Plain-language explanations of what’s happening, why it matters and what to do next. You shouldn’t need to understand every technical term just to follow the process.
Expert mode: Detailed logs, technical information and deeper controls for people who want to inspect what’s happening underneath.
Both modes should retain the same safety checks. Choosing Expert shouldn’t mean losing protection against the wrong device, mismatched files or misleading results.
Where is it up to?
ROMVERSE is currently in Internal Alpha. My immediate focus is testing and polishing the Fedora/Linux desktop experience—first-time setup, project workflows, navigation, error handling, saving, reopening and continuing where you left off. Windows and an Android Companion remain part of the wider project.
There are working development components, but there is also substantial integration and testing still to do. I’m not claiming universal device compatibility, risk-free flashing or a completed end-to-end build-to-flash experience.
When something hasn’t been verified, I want ROMVERSE to explain that clearly rather than guess or show a reassuring green tick it hasn’t earned.
Why share it now?
I’d like to bring people along for the journey, not just appear one day with a launch announcement.
I’ll be sharing weekly updates: actual development footage, animated explainers, progress, bugs, fixes and the problems I’m still working through. Concept visuals and simulations will be labelled clearly so they aren’t mistaken for finished features or real-device tests.
For transparency, the long-term plan is a subscription-supported product, with free beta testing before commercial release. This post isn’t a public download announcement or a request to pay for unfinished software.
No pretending everything works. Just building it, testing it and making it better.
Whether you’re an experienced ROM developer, a weekend tinkerer or someone who finds the whole process intimidating, I’d genuinely appreciate your perspective:
What’s the one thing you wish Android ROM tools explained or handled better?
https://redd.it/1wddi4b
@reddit_android
Currently In Alpha Stage
Hey everyone! I’m Steve, and I’d like to introduce RadForge Labs, my independent Australian software studio, and the project I’ve been putting my time into: ROMVERSE.
The idea is to make working with Android devices and firmware more understandable without taking useful technical control away from experienced modders and developers.
What is ROMVERSE?
ROMVERSE is being developed as a desktop workspace that brings together device information, firmware inspection, ROM customisation, build preparation, diagnostics and recovery preparation. The longer-term goal is a connected workflow from understanding your device and preparing a project through to verified, carefully controlled device operations.
A major focus is making that experience work for different skill levels:
Guided mode: Plain-language explanations of what’s happening, why it matters and what to do next. You shouldn’t need to understand every technical term just to follow the process.
Expert mode: Detailed logs, technical information and deeper controls for people who want to inspect what’s happening underneath.
Both modes should retain the same safety checks. Choosing Expert shouldn’t mean losing protection against the wrong device, mismatched files or misleading results.
Where is it up to?
ROMVERSE is currently in Internal Alpha. My immediate focus is testing and polishing the Fedora/Linux desktop experience—first-time setup, project workflows, navigation, error handling, saving, reopening and continuing where you left off. Windows and an Android Companion remain part of the wider project.
There are working development components, but there is also substantial integration and testing still to do. I’m not claiming universal device compatibility, risk-free flashing or a completed end-to-end build-to-flash experience.
When something hasn’t been verified, I want ROMVERSE to explain that clearly rather than guess or show a reassuring green tick it hasn’t earned.
Why share it now?
I’d like to bring people along for the journey, not just appear one day with a launch announcement.
I’ll be sharing weekly updates: actual development footage, animated explainers, progress, bugs, fixes and the problems I’m still working through. Concept visuals and simulations will be labelled clearly so they aren’t mistaken for finished features or real-device tests.
For transparency, the long-term plan is a subscription-supported product, with free beta testing before commercial release. This post isn’t a public download announcement or a request to pay for unfinished software.
No pretending everything works. Just building it, testing it and making it better.
Whether you’re an experienced ROM developer, a weekend tinkerer or someone who finds the whole process intimidating, I’d genuinely appreciate your perspective:
What’s the one thing you wish Android ROM tools explained or handled better?
https://redd.it/1wddi4b
@reddit_android
ben's gadget reviews - Huawei Mate XT2 Hands-On
https://www.youtube.com/watch?v=FRrS54oHqlw
https://redd.it/1wefklv
@reddit_android
https://www.youtube.com/watch?v=FRrS54oHqlw
https://redd.it/1wefklv
@reddit_android
YouTube
Huawei Mate XT2 Hands-On
The Huawei Mate XT2 is Huawei's new $3,000 trifold. I got my hands on it for an afternoon and checked out the cameras and software. The Mate XT2 features a 6.5-inch outer panel and a 10.2-inch inner panel with a new "privacy screen" feature. The phone's powered…
Vote and Comment to get JPEG XL Support added to Android
https://issuetracker.google.com/issues/259900694
https://redd.it/1wehskp
@reddit_android
https://issuetracker.google.com/issues/259900694
https://redd.it/1wehskp
@reddit_android
Severe Battery Drain & Overheating on One UI 9 (Galaxy S25 FE). Root Cause Found: Infinite Loop in SystemJobService (WhatsApp SyncManager)
PSA: I am posting this root cause analysis to document a severe logic flaw in WhatsApp's handling of Android's WorkManager and SystemJobService background tasks. While I am open to advanced ADB workarounds, I am primarily sharing these JobScheduler dumps and battery metrics for community awareness and developer visibility, as standard tier-1 tech support (clearing cache, reinstalling) cannot fix this persisted loop.
Device: Samsung S25 FE
OneUI 8.5 - August Security Patch
There is a severe logic bug in WhatsApp's background task handling on the current One UI build. Leaving background data enabled triggers an infinite retry loop inside androidx.work.impl.background.systemjob.SystemJobService, locking the CPU and causing massive battery drain and thermal throttling. The device overheats while completely idle.
Using Device Care and Battery Historian, WhatsApp consistently shows absurd metrics for a single morning of idle time: over 14h 26m of background execution time, 3h 22m of Wakelocks, 2h 6m of active CPU time, and 200,907 mobile data packets transferred in the background.
By analyzing the Android JobScheduler dump via ADB (adb shell dumpsys jobscheduler com.whatsapp), I was able to pinpoint the cause: the system is trying to execute a persisted periodic contact sync job, failing internally, and immediately retrying.
The following job parameters and constraints repeat constantly in the dumpsys output:
JobInfo:
Service: android/com.android.server.content.SyncJobService
PERIODIC: interval=+1h0m0s0ms flex=+5m0s0ms
PERSISTED
Priority: 300 [DEFAULT\]
...
Required constraints: STORAGE_NOT_LOW TIMING_DELAY DEADLINE CONNECTIVITY FLEXIBILITY UID_NOT_RESTRICTED [0xd0300008\]
...
Unsatisfied constraints: TIMING_DELAY DEADLINE [0xc0000000\]
After digging deeper into how Android's WorkManager and SyncJobService handle this (@SyncManager@com.android.contacts/com.whatsapp:android), it is clear this is an issue rooted in how WhatsApp handles internal exceptions during background syncs.
Because the job is flagged as PERSISTED, it writes itself to the androidx.work.workdb SQLite database. This means the corrupted job queue survives device reboots and app force-closes.
The fatal flaw is in the higher-level exception handling between WhatsApp and Android's WorkManager. When the sync job fails internally, WhatsApp returns a Result.retry(). Because the OS detects that the CONNECTIVITY constraint is technically met, it fails to apply standard exponential backoff policies. Instead of delaying the retry, it immediately fires the job again in an unconditional infinite loop, waking the CPU up hundreds of times and keeping the modem active (thus the 200k+ data packets).
https://redd.it/1weib1p
@reddit_android
PSA: I am posting this root cause analysis to document a severe logic flaw in WhatsApp's handling of Android's WorkManager and SystemJobService background tasks. While I am open to advanced ADB workarounds, I am primarily sharing these JobScheduler dumps and battery metrics for community awareness and developer visibility, as standard tier-1 tech support (clearing cache, reinstalling) cannot fix this persisted loop.
Device: Samsung S25 FE
OneUI 8.5 - August Security Patch
There is a severe logic bug in WhatsApp's background task handling on the current One UI build. Leaving background data enabled triggers an infinite retry loop inside androidx.work.impl.background.systemjob.SystemJobService, locking the CPU and causing massive battery drain and thermal throttling. The device overheats while completely idle.
Using Device Care and Battery Historian, WhatsApp consistently shows absurd metrics for a single morning of idle time: over 14h 26m of background execution time, 3h 22m of Wakelocks, 2h 6m of active CPU time, and 200,907 mobile data packets transferred in the background.
By analyzing the Android JobScheduler dump via ADB (adb shell dumpsys jobscheduler com.whatsapp), I was able to pinpoint the cause: the system is trying to execute a persisted periodic contact sync job, failing internally, and immediately retrying.
The following job parameters and constraints repeat constantly in the dumpsys output:
JobInfo:
Service: android/com.android.server.content.SyncJobService
PERIODIC: interval=+1h0m0s0ms flex=+5m0s0ms
PERSISTED
Priority: 300 [DEFAULT\]
...
Required constraints: STORAGE_NOT_LOW TIMING_DELAY DEADLINE CONNECTIVITY FLEXIBILITY UID_NOT_RESTRICTED [0xd0300008\]
...
Unsatisfied constraints: TIMING_DELAY DEADLINE [0xc0000000\]
After digging deeper into how Android's WorkManager and SyncJobService handle this (@SyncManager@com.android.contacts/com.whatsapp:android), it is clear this is an issue rooted in how WhatsApp handles internal exceptions during background syncs.
Because the job is flagged as PERSISTED, it writes itself to the androidx.work.workdb SQLite database. This means the corrupted job queue survives device reboots and app force-closes.
The fatal flaw is in the higher-level exception handling between WhatsApp and Android's WorkManager. When the sync job fails internally, WhatsApp returns a Result.retry(). Because the OS detects that the CONNECTIVITY constraint is technically met, it fails to apply standard exponential backoff policies. Instead of delaying the retry, it immediately fires the job again in an unconditional infinite loop, waking the CPU up hundreds of times and keeping the modem active (thus the 200k+ data packets).
https://redd.it/1weib1p
@reddit_android
Reddit
From the Android community on Reddit
Explore this post and more from the Android community