Have you had any issue with applying wallpapers to lockscreen from the settings app by chance in the latest update?
HyperOS 1.0 HyperOS 1.0 STABLE RELEASE
- Thread starter ingbrzy
- Start date
Have you had any issue with applying wallpapers to lockscreen from the settings app by chance in the latest update?
Updated Marble to 1.0.12 yesterday and noticed that long press on navigation buttons no longer functions. (Was working on 1.0.9)
Only tested them due to receiving a message in the Google app to inform that circle to search was finally available.
Is this a likely issue with the launcher we use, or a wider issue with Xiaomi devices?
Only tested them due to receiving a message in the Google app to inform that circle to search was finally available.
Is this a likely issue with the launcher we use, or a wider issue with Xiaomi devices?
using this rom on device marble.
I want to use lsposed. Can you guys revert to stock hyper os art? instead of ur own??
and what are the advantages xiaomieu rom dev and user gets from using their own art implementation ?
I want to use lsposed. Can you guys revert to stock hyper os art? instead of ur own??
and what are the advantages xiaomieu rom dev and user gets from using their own art implementation ?
1.0.14.0.UNRCNXM
Yes, there is a problem with applying wallpapers and the miui.systemui.plugin component in Themes.
Good evening, will the Xiaomi 11T Pro continue to be supported by the devs here in the future, or is it heading towards EOL?
MeiGuddet
Members
- 29 Apr 2016
- 1,576
- 297
if xiaomi.eu wanted to can they still build a newer rom for a eol device?
It would be a completely a different ROM and project. Currently they are modding official ROMs, you are talking about porting another ROM that was not intended to work on the device, with all the issues that come with it.
My question follows on from this: Can Xiaomi.eu keep the ROM alive after the EOL?
- 6 Oct 2016
- 9,979
- 322
1. There's zero incentive to be dealing with ports. We have plenty of devices to maintain support for.
2. Even if we wanted to make ports, that requires owning every single device for which we'd make ports for testing. No one is going to waste money for no incentive.
Short answer is no, if the device goes EOL, it's game over.
Can't enable suspend execution for cached apps in developer options ever since upgraded from miui 14 by xiaomi.eu
device: Marble
device: Marble
- 6 Oct 2016
- 9,979
- 322
@Igor Eisberg
Poco F6
What means a bug? Is it a real WiFi drain or just some wrong display of battery stats?
And whatever it is, is there some fix for it. Some people say that for example on India stock rom, there is not such a problem.
Since the beginning I was on xiaomi.eu rom and since that time I have this wifi drain.
Last edited:
Hi all,
I have a problem after upgrading to xiaomi.eu_GARNET_OS1.0.14.0.UNRCNXM_c713bc8cad_14.zip (from 1.0.13.0).
When "Files" is invoked (i.e. to select a file to load to gmail or to another app), it automatically crashes. I tried everything I could think of:
• clear data
• toy with permissions
• revoke permissions
• disable/enable mi cloud inside "Files".
• reflash (upgrade only, because I don't want to reinstall everything).
Nothing.
In another garnet device, "Files" works as intended (also upgraded to 1.0.14.0), so I am perplexed.
Do you have any ideas?
Is running "windows_install_upgrade.bat" (of 1.0.13.0 package) to downgrade to 1.0.13.0, then doing it again (after rebooting) of 1.0.14.0 package to go again to 1.0.14.0 safe? I have seen a thread that someone did it and worked.
I have a problem after upgrading to xiaomi.eu_GARNET_OS1.0.14.0.UNRCNXM_c713bc8cad_14.zip (from 1.0.13.0).
When "Files" is invoked (i.e. to select a file to load to gmail or to another app), it automatically crashes. I tried everything I could think of:
• clear data
• toy with permissions
• revoke permissions
• disable/enable mi cloud inside "Files".
• reflash (upgrade only, because I don't want to reinstall everything).
Nothing.
In another garnet device, "Files" works as intended (also upgraded to 1.0.14.0), so I am perplexed.
Do you have any ideas?
Is running "windows_install_upgrade.bat" (of 1.0.13.0 package) to downgrade to 1.0.13.0, then doing it again (after rebooting) of 1.0.14.0 package to go again to 1.0.14.0 safe? I have seen a thread that someone did it and worked.
- 6 Oct 2016
- 9,979
- 322
Unfortunately, I had to do a clean format and reinstallation of xiaomi.eu_GARNET_OS1.0.14.0.UNRCNXM_c713bc8cad_14.zip.
When I click "restore" (on the built-in backup/restore MIUI settings) while "SMS, contactns and call history" is selected, it does nothing. If I unselect it, then the rest ("Other system app data" and "Third party apps and app data") can be restored (when I click "Restore", they are restored).
Also, If I want to backup, then "SMS, contacts, and call history" is greyed out.
What is the cause of that? Before I had to clean reinstall, the auto-backup feature did in fact capture SMS, contacts and call history, so it baffles me. I have those MIUI backup files (last backuped last saturday). How can i restore them?
When I click "restore" (on the built-in backup/restore MIUI settings) while "SMS, contactns and call history" is selected, it does nothing. If I unselect it, then the rest ("Other system app data" and "Third party apps and app data") can be restored (when I click "Restore", they are restored).
Also, If I want to backup, then "SMS, contacts, and call history" is greyed out.
What is the cause of that? Before I had to clean reinstall, the auto-backup feature did in fact capture SMS, contacts and call history, so it baffles me. I have those MIUI backup files (last backuped last saturday). How can i restore them?
PervizMikail
Members
- 18 Nov 2023
- 365
- 67
Yes, to no avail. No backup is possible also. Which means there is a problem indeed.
Fixed it. Despite being a full format+installation, system app "Backup" was automatically denied access to Call Logs and Messages. When I manually enabled access via the settings, the backup option was activated and the restore function was able to proceed. So everything went ok in the end.
