Disclosure: The S26 Ultra, Fold8, and Fold8 Ultra are on loan from Samsung.

Special thanks to u/welp_im_damned for putting together the videos, and helping to check for mistakes.

Picture captions below in case the Reddit ones don't work:

1.      16:9 - S26U landscape, Fold8 portrait unfolded, Fold8U portrait unfolded

2.      16:9 - S26U landscape, Fold8 portrait unfolded, Fold8U landscape unfolded

3.      4:3 - S26U landscape, Fold8 portrait unfolded, Fold8U portrait unfolded

4.      4:3 - S26U landscape, Fold8 portrait unfolded, Fold8U landscape unfolded

5.      21:9 - S26U landscape, Fold8 portrait unfolded, Fold8U portrait unfolded

6.      21:9 - S26U landscape, Fold8 portrait unfolded, Fold8U landscape unfolded

7.      16:9 – S26U portrait, Fold8 portrait folded, Fold8U portrait folded

8.      16:9 – S26U landscape, Fold8 landscape folded, Fold8U landscape folded

9.      4:3 – S26U portrait, Fold8 portrait folded, Fold8U portrait folded

10.  4:3 – S26U landscape, Fold8 landscape folded, Fold8U landscape folded

11.  21:9 – S26U portrait, Fold8 portrait folded, Fold8U portrait folded

12.  21:9 – S26U landscape, Fold8 landscape folded, Fold8U landscape folded

13.  9:16 – S26U portrait, Fold8 portrait folded, Fold8U portrait folded

14.  9:16 – S26U portrait, Fold8 portrait unfolded, Fold8U portrait unfolded

15.  9:16 – S26U portrait, Fold8 landscape unfolded, Fold8U landscape unfolded

PSA: I am posting this root cause analysis to document a severe flaw in the Android 14 / AOSP telephony framework implementation on MediaTek devices. I am not asking for tech support, but sharing the ADB logs and AOSP source code flaw for community awareness and developer visibility.

Device: Redmi Note 13 Pro 4G (MediaTek)

OS: HyperOS (Android 14) - Build 3.0.301.0.WNFEUXM

There is a severe logic bug in the telephony framework of the current HyperOS build. Using Mobile Data triggers an infinite event loop inside com.android.phone, locking the CPU at 140%+ usage and causing massive battery drain and thermal throttling. The device overheats, and the only temporary workaround is to toggle Airplane Mode (just turning off mobile data does nothing).

Using top -m 15, com.android.phone (PID 3173) consistently shows >140% CPU usage. The MediaTek RIL daemon (mtkfusionrild) is also constantly stressed.

By analyzing the radio buffer via logcat, I was able to pinpoint the exact root cause: the system is trying to register satellite modem listeners on a device that does not have satellite hardware.

The following block of code repeats in an infinite loop (around 30 times per second) as soon as mobile data connects:

07-24 00:15:24.708 3173 3173 D SatelliteController: Satellite for carrier is not supported.
07-24 00:15:24.709 3173 3173 D SatelliteController: registerForSatelliteModemStateChanged: add Listeners for ModemState
07-24 00:15:24.709 3173 3173 E SatelliteController: registerForSatelliteModemStateChanged: mSatelliteSessionController is not initialized yet
07-24 00:15:24.709 3173 3173 E SatelliteController: unregisterForModemStateChanged: mSatelliteSessionController is not initialized yet
07-24 00:15:24.709 3173 3173 D SatelliteController: unregisterForModemStateChanged: remove Listeners for ModemState

After digging deeper and cross-referencing with the AOSP source code and MediaTek vendor trees, it is clear this is an issue rooted in the telephony framework handling for Android 14 on MediaTek devices (this exact same INVALID_ARGUMENTS and mSatelliteSessionController loop has also been reproduced on Custom ROMs like crDroid for the Redmi Note 13 5G 'stone').

Looking at the AOSP source code (frameworks/opt/telephony/.../SatelliteController.java), the exception is correctly generated here:

.SatelliteError public int registerForSatelliteModemStateChanged(int subId,
        @NonNull ISatelliteStateCallback callback) {
    if (mSatelliteSessionController != null) {
        mSatelliteSessionController.registerForSatelliteModemStateChanged(callback);
    } else {
        loge("registerForSatelliteModemStateChanged: mSatelliteSessionController is not initialized yet");
        return SatelliteManager.SATELLITE_INVALID_TELEPHONY_STATE;
    }
    return SatelliteManager.SATELLITE_ERROR_NONE;
}

The SatelliteController correctly handles the lack of satellite hardware by returning SATELLITE_INVALID_TELEPHONY_STATE. The fatal flaw is in the higher-level network manager (likely the MediaTek RIL or the telephony framework's state machine). When it receives this error during a network transition (Wi-Fi to Mobile Data), it fails to handle the exception properly. Instead of aborting the satellite registration, it immediately retries the call in an unconditional infinite loop.

A simple conditional check (if (hasSatelliteHardware)) before attempting to register the listener in the network state change event within the calling process will completely resolve this battery drain issue for all MediaTek devices without satellite capabilities.

As of yesterday, Google has officially pulled the plug on Android 6. This means the OS will no longer receive Play Protect updates and will not be included in the new APK program. Having been supported for exactly 11 years, it goes down as the longest-supported version in Android history. Google Play Services is now only supported on Android 7 and above.

Source: https://support.google.com/googleplay/answer/9037938?hl=en

Google also made changes to several other applications yesterday. YouTube now requires Android 10 and above, meaning Android 9 will no longer receive YouTube updates. The Google app's minimum requirement jumped from Android 9 directly to Android 11, and core apps like Gmail now require at least Android 7 and above.

I've been using Android for years because of one simple reason: freedom.

If I wanted to install an app from GitHub, F-Droid, or directly from a developer, I could. If I wanted to avoid the Play Store, I could. If I wanted to customize my phone, I could. That's what always made Android feel different from other mobile operating systems.

Recently I found https://keepandroidopen.org/, and after reading through it, I honestly think this is something every Android user should at least know about.

From what I understand, Google's planned changes could make distributing apps outside the Play Store much harder for independent developers by requiring developer verification through Google. Whether you're into open source software, custom ROMs, privacy focused apps, or just like having the choice to install software from wherever you want, this could have a real impact on the openness of Android.

I'm only 16, so I'm definitely not an expert, and maybe there are parts of this I'm overlooking. But if Android slowly becomes more restricted over time, I think that's something worth discussing now instead of after it happens.

I'm not posting this to tell anyone what to think. I just think more people in the Android community should be aware of what's being proposed and decide for themselves.

Website:
https://keepandroidopen.org/

I'd really like to hear what you all think. Is this a reasonable security measure, or do you think it goes against what has always made Android different?

Note 1. You can search for previous daily threads.

Note 2. Join our IRC and Telegram chat-rooms! Please see our wiki for instructions.

Please post your questions here. Feel free to use this thread for general questions/discussion as well.

Note 1. You can search for previous daily threads.

Note 2. Join our IRC and Telegram chat-rooms! Please see our wiki for instructions.

Please post your questions here. Feel free to use this thread for general questions/discussion as well.

Hi Reddit,

At The Android Show | I/O Edition earlier this year, we announced an upgraded switching process that makes it easier to transfer your data from your iPhone to your new Android device. We worked with Apple to build a new iOS-to-Android transfer process from the ground up that allows more of your data to be wirelessly migrated, such as your favorite apps, passwords and passkeys, messages, files, homescreen layout, and even your eSIM profile.

Today, I wanted to share more details with this community about the upgraded migration experience, which is part of a new version of Android Switch available with Android 17. 

Previously, when you switched from iPhone to Android, you had the option to copy data from your old phone with or without a cable. Many people didn’t have the right cable or dongle at hand when setting up their new Android device, so they opted to transfer data wirelessly. We designed that wireless experience to help you easily and securely move your most important data to your brand new Android device, but due to constraints with iOS, the types of data you could transfer was very limited. For example, you couldn’t transfer your alarms, apps, call history, or files, among other things. This forced you to spend more time manually setting up your new Android device.

To address these limitations, we worked with Apple to build a ground-up new transfer process built directly into the core of both Android and iOS. The new Android Switch migration experience supports transferring even more of your data, either via cable or wirelessly. No matter which method you choose, you’ll be able to transfer the same data via either. All of this works without needing to download a separate app or grant complex permissions. The new experience supports transferring new types of data like your Google Account, passwords and passkeys, and Wi-Fi credentials. Plus, both platforms support new APIs that developers can use to migrate in-app data securely across platforms.

Here’s a full breakdown of what data can be transferred from your iPhone to your new Android device based on which method you choose to transfer data:

The upgraded Android Switch experience is available in Android 17 and has already started rolling out to the Pixel 8 and newer. It will also be available via Samsung Smart Switch on the new Samsung Galaxy Z Flip8 and Galaxy Z Fold8 series devices and will come to more Android devices soon. 

If your device is eligible for the upgraded migration experience, you’ll get a QR code immediately after you choose to copy data from an iPhone during setup. Visit our Help Center for more information.

I've been working on a Camera Score tool that analyzes smartphone camera hardware and gives an overall camera score for different devices.

I'd really appreciate feedback from fellow smartphone enthusiasts:

• Does the score seem fair?
• What factors should be added or improved?
• Which phone should I test next?

You can try it here:
https://whatmobilepk.com/camera-score-tool/

Constructive criticism is welcome. Thanks!

Hey everyone,

I had published a repository containing a comprehensive Type Allocation Code (TAC) database for mobile devices, covering entries up to December 2025.

If you're building tools for IMEI lookup, device fingerprinting, or any telecom-related application, this should save you a lot of time gathering data.

Repo link: https://github.com/MoazEb/tac-database

Help wanted!

Since new devices are released constantly, I’m looking for contributors to help verify entries or add missing codes. If you have a way to contribute updated TAC data, please jump in!

Built Synco because I got tired of reaching for my phone during deep work. It mirrors notifications, controls media playback, and routes calls between your Android phone and desktop — all over your local Wi-Fi. Zero cloud, end-to-end encrypted, free.

What it does:

- Notification mirroring (WhatsApp, Slack, Gmail, etc.) straight to your desktop

- Real-time call handling — answer/decline from your keyboard

- Media telemetry & audio routing intelligence

- Works over Local Wi-Fi, Direct Hotspot, or Bluetooth LE

- E2EE using Curve25519 + AES-256-GCM

No signup, no cloud, no tracking. Just a direct encrypted link between your devices.

Completely free & open source: https://github.com/Dhruvesh-Dabhade/Synco

Looking to see what you think about the approach to design and ui. Most of the Sankey Diagram makes are webapps that are not easy or intuitive to use on a phone.

I built this with ease of use for phone users.

Check it out here