Android - Reddit
1.29K subscribers
16 photos
1 video
34.7K links
Stay up-to-date with everything Android!
Content directly fetched from the subreddit just for you.

Powered by : @r_channels
Download Telegram
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
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
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
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
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
UI/UX devs reactions to the IPhone Duo has been such a wake up call to how shit the app support is for android.

Don’t get me wrong. I’ve always known developers generally don’t give a fuck when it comes to porting for android. They’ll do the bare minimum and have the app look like it was made in 2005 while on IOS they’ll go out of their way to use apples own design language.

But what was an awake up call for me is seeing hit tweets with 100 thousand likes of tweets like “if you want your app to look nice on this phone, you’re gonna have to adapt to all these layouts” as if these layouts haven’t existed for the past 6 years. It’s so weird to see on the outside but I feel like if you’re an app developer, you would have already considered those layouts but they really just don’t care. Google and Samsung have to resort to having the phone do the work for them and hope it doesn’t look like crap.

Anyways the very least, we should just have better support now that they give a shit I guess so we just reap those rewards.

https://redd.it/1wdmbwk
@reddit_android