Search results


  1. Igor Eisberg

    Invalid Redmi Note 13 4g - Several bugs and malfunction

    When you don't see similar reports of such a major problem from other users of that device, assume that the problem is on your side.
  2. Igor Eisberg

    HyperOS 2.0 HyperOS 2.0 STABLE RELEASE

    Try this, might be related. https://xiaomi.eu/community/threads/hyperos-2-0-stable-release.74372/post-744208
  3. Igor Eisberg

    Invalid Redmi Note 12 sunstone no haptic feedback (vibration)

    If you don't see the "Touch" tab then your device doesn't support it.
  4. Igor Eisberg

    Gesture

    Then I'm not sure why you're asking questions about stock ROM here, without at least disclosing it. The switch is present on our ROMs, but on stock launcher it's only visible for Japanese KDDI builds.
  5. Igor Eisberg

    Gesture

    Device? ROM version?
  6. Igor Eisberg

    Call recoarding option

    No.
  7. Igor Eisberg

    Gesture

    Home settings -> System navigation -> Google Assistant
  8. Igor Eisberg

    HyperOS 2.0 HyperOS 2.0 STABLE RELEASE

    Android 15 wasn't available a whole year ago.
  9. Igor Eisberg

    HyperOS 2.0 HyperOS 2.0 STABLE RELEASE

    Works fine here. When enabled, a button shows on the left side of the screen when pressing the volume button while audio is played from a certain app or apps.
  10. Igor Eisberg

    HyperOS 2.0 HyperOS 2.0 STABLE RELEASE

    MediaFire (where you uploaded the fix) doesn't expose the date. The modem.img there might be outdated, regardless of region. You should not have included it there at all unless an exact compatible ROM version is specified.
  11. Igor Eisberg

    HyperOS 2.0 HyperOS 2.0 STABLE RELEASE

    Most likely your driver, USB port, or USB cable. Definitely not the ROM.
  12. Igor Eisberg

    Device is not certified to use Google services. (sky/river)

    Can't see how, none of us have this low-end device.
  13. Igor Eisberg

    Device is not certified to use Google services. (sky/river)

    You complained about the same thing a whole year ago. If this was a ROM issue, you'd see plenty of similar reports. No idea what's going on there.
  14. Igor Eisberg

    HyperOS 2.0 HyperOS 2.0 STABLE RELEASE

    All requirements to see this setting are met. You can try to log with this command: adb logcat -s MainlineModuleControl Do that while accessing the "Security status" screen.
  15. Igor Eisberg

    Ricovery average for the Redmi 10 2022 European version with a code called eos

    Seems like it is selene. Try again, in proper English.
  16. Igor Eisberg

    HyperOS 2.0 HyperOS 2.0 STABLE RELEASE

    Don't worry yourself with meaningless details. The way we pack the ROMs doesn't preserve modification date. https://xiaomi.eu/community/threads/hyperos-2-0-stable-release.74372/post-744208
  17. Igor Eisberg

    HyperOS 2.0 HyperOS 2.0 STABLE RELEASE

    Like it said, it's impossible for us to know why you're getting "Waiting for device". It's a specific issue you're having, no one else.
  18. Igor Eisberg

    HyperOS 2.0 HyperOS 2.0 STABLE RELEASE

    It's impossible for us to know what's wrong in your specific case.
  19. Igor Eisberg

    Invalid latest rom for X14, does not connect to XW2

    You do you, man. If you can't handle Global ROM, then go ahead and move to another brand.
  20. Igor Eisberg

    Invalid latest rom for X14, does not connect to XW2

    There are some crazy mental gymnastics in your post. If Global ROM works for your needs, then use Global ROM. Why would you sell the phone and watch just because something doesn't work properly with a custom ROM? Makes no sense.
View older results
Top Bottom
Back