I had a Huawei Mate 9 before, and there was an icon at the bottom-center of the screen, so that when I tap it, it shows all apps on the phone. (It is running the latest Android it can, which I think is Android 9 and EMUI 9.1) However, I just got a Xiaomi Redmi 9 , and there seems to be no such icon (it is running Android 10 and MIMU 11). I can only slide the desktop left and right. Is the standard Android interface actually to show all apps by default on the desktop (and is slide-able, like on an iPhone), and so there is no need to have that bottom-center icon, and we actually can see all apps on the phone just by sliding the desktop left and right?

I used the dload method to upgrade my dual-SIM Huawei P20 Lite (ANE-LX3 C605) with bootloader locked from EMUI 8.1 to 9.1. It is actually the first time I ever do something to this phone, so I am not completely sure how this works. I think my phone was rebranded to C432 because the name of the firmware I downloaded is Huawei P20 Lite ANE-LX1 ANE-L01 ANE-L21 hw eu Anne-L01 Anne-L21 9.1.0.132(C432E5R1P7T8) Firmware 9.0.0 r3 EMUI9.1.0 05014YWN 05014YXX.zip. EMUI 9.1 works like a charm, but I want to downgrade to EMUI 8 in order to have an earlier version of Google Play services. I have download a few different firmware from androidhost.ru: 1. Huawei P20 Lite ANE-LX3 ANE-L23 claro la Anne-L23 8.0.0.152(C605) Firmware 8.0.0 r1 EMUI8.0 05015ATQ 2. Huawei P20 Lite ANE-LX1 ANE-L21 hw eu Anne-L21 8.0.0.150(C432) Firmware 8.0.0 r1 EMUI8.0 05014YWN 3. Huawei P20 Lite ANE-LX1 ANE-L21 hw eu HLRCF Anne-L21 8.0.0.180(C432) Firmware 8.0.0 r1 EMUI8.0 05014YXX With 1. and 3. it says "Software install failed! Get help from www.emui.com" With 2. it says that the software package is not compatible with the current version . I have attached a couple of screenshots with info on the version and build number as seen currently. Any help with this matter would be much appreciated, thanks in advance.

I messed around with my phone (Huawei P10 VTR-L29) and unfortunately bricked it. what happened ------------- To give you the whole story, I tried to root it, but during the root process I found out that the device is encrypted so I had to "rollback". That worked fine and my phone was working ok with one issue - I wasn't able to update firmware via regular system updates. I saw the update, but wasn't able to download and install - it always ended up with some error. That made me decide to reinstall the firmware from scratch. I followed general steps but yeah, I messed up. current status -------------- The only thing I can see now is When I click on download latest version and recovery But after a while it fails: And I am stuck :( I can't get any further .. I tried to connect via ADB (but since I cannot get in the phone to enable USB Debugging (which might be the problem) I am unable to connect (nor ADB neither FASTBOOT can see the device). I tried to create this file: /etc/udev/rules.d/51-android.rules But when I run sudo adb kill-server sudo adb start-server adb devices It's still empty ... I can't even get to the "FACTORY RESET" by pressing and holding POWER + VOL:DOWN for some time; it always brings me back to the Huawei eRecovery Do you guys have any idea how to fix this?
Or is that phone dead for good? I don't care about the data inside.. I would only love to make it work again EDIT ==== with the help of alecxs I made it to the fastboot&rescue mode however this sudo fastboot boot [img] ends up with downloading 'boot.img'... OKAY [ 1.052s] booting... FAILED (remote: Command not allowed) finished. total time: 1.056s similar for sudo fastboot flash recovery [img] ends up with target reported max download size of 471859200 bytes sending 'recovery' (32040 KB)... OKAY [ 0.995s] writing 'recovery'... FAILED (remote: Command not allowed) finished. total time: 1.001s EDIT2: ------ I asked as well one of my friends and we moved on a bit more ... I tried to unlock the bootloader sudo fastboot oem unlock [unlock_code] Then I got this screen: I went with the option (2) and that brought me to the first screen mentioned in this article "Huawei eRecovery" but when I repeated the VOL:DOWN + USB:CABLE:PLUG trick :) I got this I tried a different TWRP (for P10 specifically) from this link: XDA Devs - P10 TWRP Flashing worked fine: sudo fastboot flash recovery_ramdisk twrp_p10_0.1.img I got: target reported max download size of 471859200 bytes sending 'recovery_ramdisk' (24954 KB)... OKAY [ 0.771s] writing 'recovery_ramdisk'... OKAY [ 0.232s] finished. total time: 1.003s after sudo fastboot reboot right after this command, I need to unplug the USB cable and hold VOLUME:UP to be able to get to TWRP (swipe.d to allow modifications) ... am there already now I am looking for any ROM for my P10 to flash it. I want to try this one: TheUpgradeGuide.com - Pixel Experience I downloaded the gApps and ROM ... uploaded it to the "Internal Storage" of the phone (there was a folder TWRP so I put it next to it) . .. /TWRP rom.7z gapps.zip Went on wiping -> WIPE -> ADVANCED -> checked these - Dalvik Cache - System - Cache - Data swiped to wipe (uplugged USB) .. but got this error: Updating partition details ... Failed to mount '/odm' (Invalid argument) ...done Failed to unmount '/system' (Device or resource busy) Full SELinux support is present MTP Enabled Failed to unmount '/system' (Device or resource busy) Wiping Dalvik Cache Directories... --Dalvik Cache Directories Wipe Complete! Formatting Cache using make-ext4fs... Wiping data without wiping /data/media ... Done. Failed to unmount '/system' (Device or resource busy) Unable to wipe /system. Updating partition details... Failed to mount '/odm' (Invalid argument) ...done EDIT 3 ------ in the adb shell ~ # mount rootfs on / type rootfs (rw,seclabel,size=1457112k,nr_inodes=364278) tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755) devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600) proc on /proc type proc (rw,relatime,gid=3009,hidepid=2) sysfs on /sys type sysfs (rw,seclabel,relatime) selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime) none on /acct type cgroup (rw,relatime,cpuacct) tmpfs on /mnt type tmpfs (rw,seclabel,relatime,mode=755,gid=1000) none on /config type configfs (rw,relatime) /dev/block/bootdevice/by-name/secure_storage on /sec_storage type ext4 (rw,context=u:object_r:teecd_data_file:s0,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered) adb on /dev/usb-ffs/adb type functionfs (rw,relatime) hdb on /dev/usb-ffs/hdb type functionfs (rw,relatime) /dev/block/bootdevice/by-name/system on /system type ext4 (ro,seclabel,relatime,data=ordered) /dev/block/bootdevice/by-name/vendor on /vendor type ext4 (ro,seclabel,relatime,data=ordered) tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=755,gid=1000) /dev/block/sdd46 on /data type f2fs (rw,seclabel,relatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,verify_encrypt,active_logs=6) /dev/block/sdd46 on /sdcard type f2fs (rw,seclabel,relatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,verify_encrypt,active_logs=6) /dev/block/sdd13 on /cache type ext4 (rw,seclabel,relatime,data=ordered) plus the ls output ~ # ls -ld $(find /dev/block -name by-name)/* drwxr-xr-x 2 root root 1020 Jan 4 18:02 /dev/block/bootdevice/by-name lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/boot_a -> /dev/block/sdd32 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/bootfail_info -> /dev/block/sdd14 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/cache -> /dev/block/sdd13 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/cust_a -> /dev/block/sdd43 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/dfx -> /dev/block/sdd19 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/dts_a -> /dev/block/sdd34 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/fastboot_a -> /dev/block/sdd24 lrwxrwxrwx 1 root root 15 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/frp -> /dev/block/sdc1 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/fw_hifi_a -> /dev/block/sdd28 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/fw_lpm3_a -> /dev/block/sdd21 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/hisee_fs -> /dev/block/sdd18 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/hisee_img_a -> /dev/block/sdd23 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/isp_boot_a -> /dev/block/sdd26 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/isp_firmware_a -> /dev/block/sdd27 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/misc -> /dev/block/sdd15 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/modem_fw_a -> /dev/block/sdd36 lrwxrwxrwx 1 root root 15 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/modem_om -> /dev/block/sdd7 lrwxrwxrwx 1 root root 15 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/modem_secure -> /dev/block/sdd3 lrwxrwxrwx 1 root root 15 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/modemnvm_backup -> /dev/block/sdd9 lrwxrwxrwx 1 root root 15 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/modemnvm_factory -> /dev/block/sdd8 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/modemnvm_img -> /dev/block/sdd10 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/modemnvm_system -> /dev/block/sdd11 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/modemnvm_update_a -> /dev/block/sdd38 lrwxrwxrwx 1 root root 15 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/nvme -> /dev/block/sdd4 lrwxrwxrwx 1 root root 15 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/oeminfo -> /dev/block/sdd5 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/patch_a -> /dev/block/sdd39 lrwxrwxrwx 1 root root 15 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/persist -> /dev/block/sdc2 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/product_a -> /dev/block/sdd42 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/recovery2_a -> /dev/block/sdd30 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/recovery_a -> /dev/block/sdd33 lrwxrwxrwx 1 root root 15 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/reserved1 -> /dev/block/sdc3 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/reserved10 -> /dev/block/sdd17 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/reserved2 -> /dev/block/sdd16 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/reserved3_a -> /dev/block/sdd22 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/reserved4_a -> /dev/block/sdd37 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/reserved5 -> /dev/block/sdd45 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/rrecord -> /dev/block/sdd20 lrwxrwxrwx 1 root root 15 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/secure_storage -> /dev/block/sdd6 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/sensorhub_a -> /dev/block/sdd31 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/splash2 -> /dev/block/sdd12 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/system_a -> /dev/block/sdd44 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/teeos_a -> /dev/block/sdd29 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/trustfirmware_a -> /dev/block/sdd35 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/userdata -> /dev/block/sdd46 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/vector_a -> /dev/block/sdd25 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/vendor_a -> /dev/block/sdd41 lrwxrwxrwx 1 root root 16 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/version_a -> /dev/block/sdd40 lrwxrwxrwx 1 root root 15 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/vrl -> /dev/block/sdd1 lrwxrwxrwx 1 root root 15 Jan 4 18:02 /dev/block/platform/ff3b0000.ufs/by-name/vrl_backup -> /dev/block/sdd2 Ok, with the help of alecxs I managed to get a bit further (see the chat) but it seems like the TWRP is faulty (the one from the link above -> XDA).. nonetheless, any other TWRP is not working at all and I am landing on this screen instead :( EDIT 4: ------- output of fastboot getvar all is here: getvar:all FAILED (remote: Command not allowed) EDIT 5: ------- see the output of the fastboot commands requested in the chat #sudo fastboot oem get-bootinfo ... (bootloader) unlocked OKAY [ 0.006s] finished. total time: 0.006s $ sudo fastboot getvar vendorcountry vendorcountry: hw/eu finished. total time: 0.007s $ sudo fastboot oem get-build-number ... (bootloader) :VTR-L29C432B151 OKAY [ 0.007s] finished. total time: 0.007s $ sudo fastboot oem oeminforead-SYSTEM_VERSION ... (bootloader) :VTR-L29C432B151 OKAY [ 0.008s] finished. total time: 0.008s SOLVED ====== Finally, I made it and the phone is up and running :) I downloaded Huru Updated (v0.3) and these files https://huaweidl.com/download/huawei-p10/vtr-l29/b151/ Followed these steps: https://www.getdroidtips.com/hurupdater-tool/ and yaaaay, it works :) after months of playing around ... big thx to alecxs for his immense help !!! this guys is a genius !!! the only question now is to get from Android 7 (the stock I flashed) to 9.1 (the most updated one provided to p10) ... bec the native system update does not offer me an update :D but that's minor .. EDIT: ok, following this manual xda-developers - Jannomag I was able to upgrade to 8.0 (with a little hiccup - just had to manually restart it multiple times) and then to 9.0 (no problem at all this time) and right after 9.0 it offered me (via system update) automatically the newest 9.1.0.263

For couple of weeks I'm experiencing weird behaviour on my P30 Pro. Randomly, from time to time, for a split second blank activity window is sliding from the right and back making usage of the phone problematic. Especially while recording a video what leads the process to stop. Nothing shows up on the recent apps view, AVG doesn't show any threats. Do you have any idea how can I hunt down responsible app? Android 10, EMUI 11

I have a Chinese phone and I don't know what to do with that. I have Huawei 7 Plus (Android 7, EMUI 5.1.1 B223). How to install core GMS packages on it?

Yesterday, I used the Xiaomi Mi 9 SE [Updater](https://adimorahblog.com/wp-content/uploads/2021/06/Mi-9-update.jpg) app to update my EMUI version. After downloading the update zip file (2.8GB), the app warned me that it would "install the update, start in recovery mode and will ask for my password as the file system was encrypted" (I don't remember the message exactly). The phone rebooted and got stuck on the Fastboot screen for more than a hour. After that I rebooted multiple times with different ways (hold power button, hold power button + volume down, and hold power button + volume up and down) but just after the reboot it gets stuck on the Fastboot screen again. I tried using the Android platform tools to try to reboot it but the result is the same, always stuck on the Fastboot screen.

$ sudo ./fastboot devices
f6da2608	fastboot

$ sudo ./fastboot reboot
Rebooting                                          OKAY [  0.000s]
Finished. Total time: 0.351s

$ sudo ./fastboot reboot recovery
Rebooting into recovery                            OKAY [  0.000s]
Finished. Total time: 0.352s

Do you have any solution to fix ? If not, is it possible to do a factory reset ? I have backups for my data so no problem for me.

I have been using my Huawei Honor 8 for about 2 years now. I live in the US. And I have been using Google Play Store and other apps without any issues. Last night my phone ran out of charge and died. When I plugged it in and turned it on, I received tens of notifications stating: "Get Google Play Services. [App name] won't run without Google Play Services which are missing from your device". I Double checked it, and Google Play Services are still installed. However, whenever I attempt opening any Google-related app, I get an error message saying: "Core GMS packages. Install core GMS packages to use [App name]". Has anyone encountered this problem before? What could cause it? And how could it be resolved? Model Number: FRD-L04 Build Number: FRD-L04C567B398 EMUI version: 5.0.4 Android Version: 7.0

Yesterday I installed a suggested update on my Huawei nova3i, to EMUI version 9.1.0 There is one change which I don't like. Many apps installed from the app store used to have round icons, but now they have square icons. See in this before and after, how the 'Calm', 'MeeWee' and 'Vimeo' icons have changed shape: (We can also see that the icons grew a little bit larger, which I don't really find appealing either.) **Is it possible to restore the old look, with smaller round icons for apps from the App Store?** (I am willing to install a theme if I have to, but I don't really want the default icons, wallpapers and text to change!)

I have Huawei Honor View 10 phone I got it bootloader unlocked and rooted with magisk while bootloader unlock option was available on Huawei website. After sometime I upgraded to Android 10 update (EMUI) from Huawei which caused me to lose root. If I rollback to previous version... 1. Do I get bootloader unlocked as earlier 2. Will it be rooted or require me to root it again looking to hear from someone who has been there done that.

Please read [this question](https://android.stackexchange.com/questions/241078/bootloop-after-rebooting-the-system-android-7) first!!! I've disabled dm-verify and then it says the data partition is corrupted! I did a low-level factory reset, but it is still showing that annoying message when I try to boot it up. How to fix this?

I run EMUI 9.1, which completely supports Google Play Services (bought it before the ban). However, I used to update Chrome normally, but starting with version 91.xxx, it just updates fine, but the app icon is removed from the launcher, and can't start it. Any solution? or I have to quit Chrome?

The navigation bar at the bottom of my screen adapts with the app I'm using at any given time. This would be nice if it actually worked, but for some apps even while using dark theme the bar would turn into a bright white, which just looks distracting. I'd prefer to have it be all black at any given time, but I couldn't find any system settings for it. Is there a way to accomplish this using ADB or something? I've got a Huawei Mate 20 X with EMUI 11. Also here's an example screenshot of an otherwise dark app having a white navigation bar:

I would like to replace my desktop computer with an android phone. I only do word processing (in google docs) and internet browsing (chrome), so I figured the processing power of a new phone should be enough for that. However, I like to write on one screen, while I read pdfs or research websites on another screen. I have two HDMI monitors. Can I use Samsung DeX or android desktop mode for this? What should I look out for, when buying a phone or a suitable docking station? (I haven't seen ones with two HDMIs yet)

I am having an issue with my brand new phone Huawei Mate 9 EMUI 5.0 from China. Somehow, when I want to install WhatsApp on it, I get the following message > Install core GMS packages to use Google Play Store Here is the screenshot What can I do to solve this? I just got the phone and I am lost.

I downloaded the latest version of EMUI 8 for my Huawei Nova 2i (RNE-L22), the file size is 3GB. Before installing the update, I'm planning to do a factory reset but that means I will need to re-download the update. The problem is I have a very limited internet connection, so I wanted to move the file into my SD-Card and flash it later. I couldn't find where the file is located, anyone knows where it is? Anyway, I downloaded the update by navigating into the Settings > About Phone > System Update.

I have deleted 47G worth of photos and no space has freed up. I have a Huawei Honor 9 (STF-AL10) EMUI 9.1.0 phone that I bought in China. What do I need to do in order to claim back that space that is still for someone reason occupied by my deleted photos? Thank you.

I have this Huawei Nova 3i , I forgot the PIN but there's no "forgot password" or "forgot PIN" option. I noticed that my Huawei Nova 2i doesn't have that option too, and I'm stuck on "Try again after 24 hours". Normally, when I forgot my password or pin, I just click on the "Forgot Password" option, input the Google Account Password that is bound to the device, and viola, password or pin successfully reset. Is there a workaround here to use that option?

I'd like to have my bootloader unlocked for my Huawei P8 Lite 2017 (PRA-LX1(C02)), but I don't wanna spend money on DC-Unlocker. My phone runs Android 8.0 EMUI 8.0 but I can downgrade it to Android 7.0 if needed. If you need IMEI, Serial Numbers things like that ask me and I'll provide those. Thanks in Advance!

I have tablet (Huawei MediaPad M6) with EMUI 10.1 (based on Android 10). My tablet regularly requests to the following domains: pushtrs9.push.hicloud.com grs.dbankcloud.com grs.dbankcloud.cn grs.dbankcloud.eu grs.dbankcloud.asia Also sometimes makes requests to the following domains: query.hicloud.com configserver.platform.hicloud.com I blocked all these requests with Blokada app. Also I uninstalled about 60% of all system apps via adb. This helped to get rid of some of the requests. But the above requests are still ongoing. How to terminate all these requests? Everywhere in the license I refused to collect data and statistics. Should I uninstall more any system apps? Or disable something in the settings?

So, I'm in my 3rd month of ownership of my first (**and last**) Huawei smartphone and I have discovered yet another strange family of issues. I have a 20GB monthly data limit from work so I rarely check my data usage. But I had a few extra charges on my last bill so I decided to check it out. (First time on this phone) The first shock was that there was no Sum of the usage, just a graph with the daily peaks and that's it. So if it was say the 30th, then you would have to add-up 30 days worth of data to find out how much you have left. What a joke: Anyway, so I figure that I should add a data limit and maybe that will Sum-up my usage. So I tap on the gear icon on the top right, then on Monthly Data Limit and enter **18GB**. Voila, my total appeared: From here on, the story gets even stranger. I tapped on the pencil icon and for some strange, inexplicable reason, you can actually edit your usage. What exactly is the point of that??? So I enter a number and tap on OK to see what happens, and now the Used total becomes whatever amount I entered: So I decided to revert to the ACTUAL total usage and I was confronted with yet another trademarked Huawei irritation. You cannot clear your own usage, you have to enter something in that box, otherwise Save stays disabled: So as a last resort I thought that I should clear my data limit and be done with all this mess. Sadly I discovered that there is no way of doing that. It seems that once you enable the data limit, you're stuck with one. You can only change the number of MBs or GBs and again like above, you **have** to enter something in that box otherwise OK is disabled: I tried Network settings reset but all that does is **delete** your stored Wi-Fi networks (thanks Huawei) and Bluetooth devices (thanks again !) Any ideas?