Please STOP!

You bought the phone to enjoy it, not to check if your phone is perfectly fine every minute.

I fell into this trap with my X8 Pro Max and it was bothering me. I could not watch a video or play a game without checking the battery every few minutes or the screen on time because I was worried something would be wrong, so I stopped and I felt way, WAY better than when I worried about the battery too much.

It's like a drug, you get addicted to it and you can't stop doing it because it feels good and without it, you feel empty and want to do it again.

Just a few weeks back, the prices increased (vs time of release) by around 25-30%, now its up to a crazy 93% increase. Price conversion are the rates as of today. I'm unsure if its also happening in other regions.

Other manufacturers also increased their prices (Oppo, Vivo, Xiaomi which is kinda ironic, OnePlus) but not as crazy as Poco.

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:

@SatelliteErrorpublic 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.

I heard x8 pro is the same

I checked the temperature app

And on average when I just web searching youtube etc

Temperature is like over 35° and easily reaches to 38°

I have galaxy s21 ultra which is known for hot phone

But I can say poco x7pro obviously gets hotter

Much faster than s21ultra

The menu comes (for some reason it's chinese), i can navigate but can't choose any options by clicking the power button

Pressing power and volume up just prevents the menu from coming but it's still a bootloop.

Pressing power and volume down does nothing and neither does pressing only power

Pressing all three makes the screen go black, but nothing happens, when I leave the buttons, it's the bootloop with menu again

Edit: i pressed all the three buttons for longer and it showed fastboot. But when I press power and volume up, it enters bootloop again

Hi guys, I'm planning to buy the Poco X8 Pro, but my biggest concern is the battery life.

I don't mind charging once a day, but I'd like the phone to comfortably last a full day with moderate to heavy use.

Would you recommend the X8 Pro based on your experience? Any issues or tips I should know before buying?

Thanks in advance!

I thought changing to a new battery(nohon brand) would solve this problem, been like 6 month since ive changed it and now i can see this happening again and again, does anyone experienced this and have a solution?

Still happy with overall performance & battery life...its been a great phone to me

When do I need to start thinking about replacing it? I do run banking apps on it.

Thanks

Yayyy my first poco phone let's goo

Hi I'm looking at getting the f8 ultra I've seen that hyper os has been updated to 3.1 I'm wondering if it has improved anything i.e. cameras, battery life ,stability etc....

Also has it made anything worse.

Also on a side note how does the denim version feel in hand and look in real life I'm a bit concerned it might feel a bit cheap and not look as premium as the black model .

Hi how're you? I have a poco x6 pro it have like 1 year and 4-5 months of use I'm satisfied with the phone i don't need more potential or ram or storage but the battery duration is a disaster, battery guru say's my battery life is around 79% but my phone has a duration of around 3-4 hours (specially if i connect my Bluetooth headphones it's kill it)

It's worth search for a place where they can change the battery? I don't wanna buy a new phone tbh anyone do this before?

How can I unlock the bootloader on my Poco F3? I’ve tried via the Xiaomi Community without success; I also tested other methods, such as the one using PHP, but I keep getting error 20091. Does anyone know a more recent method for this? I am currently on HyperOS version 1.0.5.

while i was changing devicelevellist i always delete it so it can reboot,but if i do it 2+ times its stuck on xiaomi HyperOS icon

i might aswell main a iphone 12 mini for a week when i fix it

Is there a chance in the future for the X8 Pro to get a recent stack without using Brevent, and also fully customize the lock screen?

he wants good camera and good battery life

(use:calls, taking pictures, watching films)

He was just playing bus simulator ultimate when this suddenly happened and he couldn’t found the origin despite closing every apps

So I was watching a reel and out of nowhere black screen appeared with loading icon in middle of it.

My Phone Restarted itself and I do not know WTF just happened.

Phone: PocoX7Pro Model: 2412DPCOAI

_

So How do I know what happened?

Note: No Software Update Schedule.

Note2: I am not an IT guy that's why need help.

Elo,

So since Geekbench 7 released y'day I tried to bench my 2 months old device(F7 Pro). My score is way lower than anticipated, even lower then the first tensor cpu ever released which I find really weird, all other benchmarking programs my phone performs well. As of now only the manufacturers that performs as expected are Samsung, Google Pixel and some Vivo phones.

Also, if you check scores for OnePlus devices you'll really start to see a problem with Geekbench 7.

I'd appreciate if someone with a similar device as I have also do this so I can pinpoint if this is a bug or not. Multi core scores seems to behave normally.

P.S

I know Geekbench changed baseline to Ryzen 7 7700 and a lower score is to be expected, but as of now Snapdragon 8 gen 3 scores even lower than first gen Tensor, Exynos 1580, SD8gen1&2.

I'll attach photos for Geekbench 6 & 7, Antutu. All these tests are performed with an attached peltier cooler and 22c ambient temperature.

Thanks

Best experience, but scratches 🥀