ROM(eMMc) Issue on Xiaomi Mi A2 [118036531]

Infeasible

Bug

[AOSP] assigned

Status Update

No update yet.

Description

ro...@gmail.com

created issue #1

Oct 21, 2018 07:12PM

The memory read and write speed on Xiaomi Mi A2 is not stable, so there are some lags and freezing when it's on the use and using on big files. or clearing memory like clearing Chrome cache.

For example: when u are trying to clear about 50MB of chrome's cache, the device gets unstable and unusable for few minutes.
Or when u trying to take a benchmark with a huge file like 3GB, device freezing.

So there are always lags and instability on using the phone.

This problem is just for 4 GB ram and 64GB rom version.

Comments

ke...@gmail.com <ke...@gmail.com> #2Oct 21, 2018 09:55PM

agreed, i have 4/64 version and i have this shit bug.

nh...@gmail.com <nh...@gmail.com> #3Oct 21, 2018 10:48PM

4/64 same here...

ra...@gmail.com <ra...@gmail.com> #4Oct 21, 2018 10:51PM

+1

4/64 global version - black

ba...@gmail.com <ba...@gmail.com> #5Oct 21, 2018 11:12PM

4/64 same it's abysmal

an...@gmail.com <an...@gmail.com> #6Oct 22, 2018 12:09AM

Same in Mi A2 4/64 with Emmc Micron

gi...@gmail.com <gi...@gmail.com> #7Oct 22, 2018 05:45AM

4/64 same here...

s....@gmail.com <s....@gmail.com> #8Oct 22, 2018 10:15AM

I have mtp slow speed very slow like 700kb per sec
Im very sad about buying xiaomi a2

al...@gmail.com <al...@gmail.com> #9Oct 22, 2018 10:36AM

4/64 micron vendor. Slow write speed and can't transfer a'a movie into my mi a2 because it would take 30/40 minutes!

lo...@gmail.com <lo...@gmail.com> #10Oct 22, 2018 10:48AM

Same issue here with two Xiaomi Mi A2 4/64 black and gold. Can't clear Chrome cache unless I want an unresponsive system for 5 minutes or so. Also with AndroBench and 512 MB file size I get frezees and low write speeds (60-70 MB/s) while I can get faster writes (220-230 MB/s) with small 64 MB file size.
The issue went away right after a factory reset of the phone and appeared again after the night.

30...@gmail.com <30...@gmail.com> #11Oct 22, 2018 11:31AM

Confirm that!

em...@gmail.com <em...@gmail.com> #12Oct 22, 2018 12:00PM

Chrome crashes and reboots phone everytime I clear the large cache. Hope a fix soon!

yo...@gmail.com <yo...@gmail.com> #13Oct 22, 2018 12:15PM

Fingerprint sensor and smart-lock problem, I have only since the October update, previously worked the A2 (6/128) absolutely easily. I have temporarily disabled both Smart Lock and Lock Screen. Result: The device behaves as before the two October updates.

me...@gmail.com <me...@gmail.com> #14Oct 22, 2018 12:28PM

Fingerprint FPC issue Is not solved. The Little CPU stucks at 1401 MHz after a couple of times using the FPC sensor to unlock the device. You have to restart the device to back the min frequency to 633 MHz.
.
Many users report this issue.
.
Pls solve this issue. It's very annoying.

br...@gmail.com <br...@gmail.com> #15Oct 22, 2018 01:31PM

4/64GB

I flashed MIUI and this bug wasn't present there so it's obviously a software issue.

si...@gmail.com <si...@gmail.com> #16Oct 22, 2018 04:17PM

Same here

te...@gmail.com <te...@gmail.com> #17Oct 22, 2018 05:17PM

Yes I flashed miui i can confirm there is no reading / writing issue is there ... this is completely software issue

to...@gmail.com <to...@gmail.com> #18Oct 22, 2018 05:56PM

Same here, I'm afraid this won't get fixed if it doesn't make the headlines on android news sites like the CPU bug did.

And I doubt this tracker is the right place to report issues like this. The CPU bug at least got confirmed on Xiaomi forums by their employe.

ro...@gmail.com <ro...@gmail.com> #19Oct 22, 2018 05:59PM

We will try and we will find the right way. It's better than nothing. For CPU bug they started Issue tracker like this, then they made that to headlines

[Deleted User] <[Deleted User]> #20Oct 22, 2018 07:50PM

I have this issue

mi...@gmail.com <mi...@gmail.com> #21Oct 22, 2018 07:50PM

I have shitty benchmark results as well, but when clearing cache the phone just freezes for a few secs and then everything goes back to normal.

va...@gmail.com <va...@gmail.com> #22Oct 22, 2018 08:39PM

Same issue, once I clean cache and device is even not responding for unlock button. I tried to unlock and then I see bootscreen, but without prompting the PIN. Idk what it was, but some ROM operations make a huge impact to the system stability and almost always freeze the phone.

ko...@gmail.com <ko...@gmail.com> #23Oct 22, 2018 08:47PM

Agreed! Please fix it

pe...@gmail.com <pe...@gmail.com> #24Oct 22, 2018 08:54PM

4/64gb model. Having problems with large files and clearing chrome cache makes my device unresponsive.
I bought this phone because of Android one, but now it seems, that miui is better.

ad...@google.com <ad...@google.com> #25Oct 23, 2018 06:11AM

Assigned to ad...@google.com.

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.

Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.

Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)

NOTE: Please upload the files to Google Drive and share the folder to android-bugreport@google.com, then share the link here.

r3...@gmail.com <r3...@gmail.com> #26Oct 23, 2018 07:00AM

Agreed. 4/64 gold. Fix it.

ro...@gmail.com <ro...@gmail.com> #27Oct 23, 2018 07:50AM

Thanks for the response.

This one is with running speed test app:

https://drive.google.com/file/d/1LfiEJrSQTLdB-bNw6ft4kWc3wHoylRTf/view?usp=drive_web (bugreport-jasmine-OPM1.171019.011-2018-10-23-10-48-16.zip)

This one is without running any app:

https://drive.google.com/file/d/11_YBAjM_S28UQhGtvB4qB3fnwlPTFWXc/view?usp=drive_web (bugreport-jasmine-OPM1.171019.011-2018-10-23-11-01-58.zip)

And about frequently, it happens all the time (100%). I can say that there is no problem when we do a Factory reset. But after few hours or one or two days, the bug appears again and eMMc writing and reading getting unstable. even without installing any application.

When we are trying to clear Chromes cache, the device starts to clearing cache. For 50 MB it takes about 30 sec time and device loses its response.

Because of this bug, the device always has some lags and touch problem. Cause internal memory has a low speed and more important than that, has an unstable speed, because its start benchmark with a good speed after few secs getting stuck, start again, the stuck! so when the device wants to read or write some bug files or too many files, the devices lose response on touch and sometimes getting a soft reboot automatically.

P.S: If you want I can send u more Bug report files in various conditions.

ro...@gmail.com <ro...@gmail.com> #28Oct 23, 2018 07:51AM

Link of Drive folder:

https://drive.google.com/open?id=1gGuRKW4YGRxVrclAVfkMFINBr3wrWJ1m

ad...@gmail.com <ad...@gmail.com> #29Oct 23, 2018 08:20AM

I am also constantly facing this issue super slow write speed when file is big
when i tried to clear chrome cache device freezed and i have to long press power button to force reboot
please look into it as soon as possible

ke...@gmail.com <ke...@gmail.com> #30Oct 23, 2018 09:27AM

I also have this

issue 4

/64 black model. .write read speed is not stable pls fix this asap

gi...@gmail.com <gi...@gmail.com> #31Oct 23, 2018 10:16AM

I concur with the people above...

to...@gmail.com <to...@gmail.com> #32Oct 23, 2018 10:49AM

4/32 gold - same

ke...@gtempaccount.com <ke...@gtempaccount.com> #33Oct 23, 2018 12:15PM

Not only are not 64GB, there are users using the device with 128GB that face the same problems. My 64's suffer from the same.

[Deleted User] <[Deleted User]> #34Oct 23, 2018 01:11PM

I'm also having this issue. 4/64 black

mi...@gmail.com <mi...@gmail.com> #35Oct 23, 2018 01:16PM

Facing the same issue, but on 4/32gb black variant.

sa...@googlemail.com <sa...@googlemail.com> #36Oct 23, 2018 01:32PM

Same issue on 4/64. V9.6.15.0

Write 41 MB/s, Read 282 MB/s

da...@gmail.com <da...@gmail.com> #37Oct 23, 2018 04:02PM

I hve the same problem 4/64 black global edition, help please!

pi...@gmail.com <pi...@gmail.com> #38Oct 23, 2018 04:10PM

STOP MAKING SPAM, WE ALL KNOW THAT THERE IS A PROBLEM, GOOGLE DON'T CARE WHAT COLOR OF THE PHONE YOU HAVE, IF YOU WANT TO HELP, SEND LOGS,

el...@gmail.com <el...@gmail.com> #39Oct 23, 2018 11:45PM

Same issue also after update to October update

s....@gmail.com <s....@gmail.com> #40Oct 24, 2018 06:52AM

Yes, the same problem with my device 4/64 black

ad...@google.com <ad...@google.com> #41Oct 24, 2018 12:16PM

We have passed this to the development team and will update this issue with more information as it becomes available.

md...@gmail.com <md...@gmail.com> #42Oct 25, 2018 02:10AM

MI A2 is a great smartphone but due to this problems people don't like it...
And nobody is taking care of it....
PLZZ do the needful

a....@gmail.com <a....@gmail.com> #43Oct 25, 2018 08:48AM

Samee 4/64

el...@gmail.com <el...@gmail.com> #44Oct 26, 2018 02:15AM

same issue as well. freezing especially when playing games. so annoying. please make necessary fix. thanks

el...@gmail.com <el...@gmail.com> #45Oct 26, 2018 02:20AM

https://drive.google.com/file/d/1GZ2m0_vc8PShubc4IvdAv5rfoz4sQBsH/view?usp=drivesdk
bug report

e....@gmail.com <e....@gmail.com> #46Oct 26, 2018 10:32AM

4/64 same here...

wu...@gmail.com <wu...@gmail.com> #47Oct 26, 2018 12:00PM

Same 4/64

wi...@gmail.com <wi...@gmail.com> #48Oct 26, 2018 12:21PM

The same

issue 4

/64.

on...@gmail.com <on...@gmail.com> #49Oct 26, 2018 12:42PM

I can confirm this issue. I sometimes download lot of files on my phone from my google drive and when I select all and delete them it takes good amount of time just to delete, i have compared it with Mi A1 and Mi A1 deletes files faster. Also while playing games there is noticeable freeze when the game is trying to save the game data during that time the phone is unresponsive. With google Chrome if I exit out of the browser with a page loaded in the background and when I open browser again there is also serious glitching of the view of page for a 2 solid seconds.

se...@gmail.com <se...@gmail.com> #50Oct 26, 2018 02:17PM

4/64 same problems

va...@gmail.com <va...@gmail.com> #51Oct 26, 2018 04:04PM

4/64 problem

ri...@gmail.com <ri...@gmail.com> #52Oct 26, 2018 05:17PM

4/64 Same problems. Freezes sometimes on instagram too and when i'm clearing chromes history, that takes ages..

ro...@gmail.com <ro...@gmail.com> #53Oct 27, 2018 11:22AM

There is another Bug report on my drive:

Folder:

https://drive.google.com/open?id=1k6W-492E_2ZZF1JbDPCvu-41lLYu8ukE

File:

https://drive.google.com/open?id=1z9C9CoJ_KNMbCl7jcHM9fvIjneQ_b2-1

I took this one when I tried to clearing Chrome's cache. It took about 5 min to take the Report.

So I think this one can help too

P.S: Folder sharde with: android-bugreport@google.com

jo...@stcharles.fr <jo...@stcharles.fr> #54Oct 29, 2018 12:48PM

Same problem on 4/64 mi a2
Freeze on games and big applications

fr...@gmail.com <fr...@gmail.com> #55Oct 29, 2018 10:32PM

Same issue here

lr...@gmail.com <lr...@gmail.com> #56Oct 30, 2018 05:29AM

same issue here. while clearing app cache phone goes blank (System UI stops responding) and even sometimes turns on the wifi and location service.

pe...@gmail.com <pe...@gmail.com> #57Oct 30, 2018 10:01AM

Same here, Mi A2 4/64, clearing Chrome's cache (>500Mb) resulted in a shutdown. Waiting for solution...

ma...@gmail.com <ma...@gmail.com> #58Oct 30, 2018 10:18AM

Same problem with my Mi A2 4/64...

ma...@gmail.com <ma...@gmail.com> #59Oct 30, 2018 12:25PM

same issue on my A2 4/64 GB

m....@gmail.com <m....@gmail.com> #60Oct 30, 2018 05:19PM

I also have this problem, phone just freezes or even panics and does a reboot when moving/deleting big files

ic...@gmail.com <ic...@gmail.com> #61Oct 30, 2018 11:09PM

Same forme

sa...@gmail.com <sa...@gmail.com> #62Oct 31, 2018 11:06AM

In windows MTP is really slow, but in ubuntu 18.04 speed is ok!

no...@gmail.com <no...@gmail.com> #63Oct 31, 2018 01:35PM

The same problem with my device A2 4/64

jc...@gmail.com <jc...@gmail.com> #64Oct 31, 2018 03:35PM

same bug on my A2 4/64 GB

jo...@gmail.com <jo...@gmail.com> #65Oct 31, 2018 08:05PM

google any news about this bug? i buy my phone mi a2 4/64 gb 2 days ago i have install latest update and its very annoying that phone freeze when i clean browser cache. I have 2 weeks to return phone to shop so i wait one week for any news but I hope that I will not be disappointed in andoroid one project and you will fix this bug before i return phone

jc...@gmail.com <jc...@gmail.com> #66Nov 1, 2018 03:58PM

in the same way it happens, when I clean the cache of some applications (more than 100bm of cache) it gets frizzed :/ please correct the flaw

gi...@gmail.com <gi...@gmail.com> #67Nov 1, 2018 05:46PM

I have the same problem with my a2 4/64

da...@gmail.com <da...@gmail.com> #68Nov 1, 2018 11:00PM

Save problem here with Mi A2 4/64

ro...@gmail.com <ro...@gmail.com> #69Nov 5, 2018 04:38PM

Got november update and issue still is in there:

Bug report of november:

File:

https://drive.google.com/file/d/1ChLfE1oH9tTlUOmyFDTxiDY0PmTYZevz/view?usp=sharing

https://drive.google.com/file/d/1ChLfE1oH9tTlUOmyFDTxiDY0PmTYZevz/view?usp=drive_web (bugreport-jasmine-OPM1.171019.011-2018-11-05-18-02-04.zip)

Folder:

https://drive.google.com/drive/folders/18C7YEfmtFGUgKHGkGye9NbtoJ41yCV7v?usp=sharing

Shared with: android-bugreport@google.com

ed...@googlemail.com <ed...@googlemail.com> #70Nov 7, 2018 08:42PM

Same issue here
Device is very slow

cy...@gmail.com <cy...@gmail.com> #71Nov 10, 2018 07:38AM

same problem here 4/64 international version

jc...@gmail.com <jc...@gmail.com> #72Nov 12, 2018 02:18PM

4/64 same here Global Version...

ha...@gmail.com <ha...@gmail.com> #73Nov 14, 2018 01:45AM

same here
4/64

ju...@gmail.com <ju...@gmail.com> #74Nov 16, 2018 08:31AM

Same unstable behavior when using or deleting files, 4/64 version

br...@gmail.com <br...@gmail.com> #75Nov 18, 2018 02:38AM

Android Pie stable is out and the memory problem still persists.

an...@gmail.com <an...@gmail.com> #76Nov 19, 2018 01:32PM

Can confirm. The Issue persists on Android Pie as well.

ng...@gmail.com <ng...@gmail.com> #77Nov 19, 2018 03:52PM

4/64 global version and on Pie. Same problem

mu...@gmail.com <mu...@gmail.com> #78Nov 19, 2018 06:29PM

sirr volte no work can't call my wife 4/64 curry
btw i delete account if no fix!!

oc...@gmail.com <oc...@gmail.com> #79Nov 19, 2018 08:06PM

I also experienced freezing when I tried to clean cache of chrome. My phone became unresponsive and unusable. It was working again after a reboot.

ar...@gmail.com <ar...@gmail.com> #80Nov 19, 2018 09:11PM

4/64 same here Global Version :(

tu...@gmail.com <tu...@gmail.com> #81Nov 19, 2018 10:13PM

251/62 jesus.

aa...@gmail.com <aa...@gmail.com> #82Nov 20, 2018 01:45PM

As said in #10, even I have an issue clearing my 500 MB cache size on Chrome on Mi A2 4/64 variant. The same thing also happens to me on Nokia 7+ 4/64 Android One variant TA-1046. Is it something in general about Android One devices with SD660 or is it these 2 phones going through it?

bb...@gmail.com <bb...@gmail.com> #83Nov 20, 2018 03:19PM

4/32 MiA2 global market. same issue

al...@gmail.com <al...@gmail.com> #84Nov 20, 2018 03:20PM

Same issue here

On Tue, Nov 20, 2018, 5:19 PM <buganizer-system@google.com wrote:

- Show quoted text -

ja...@gmail.com <ja...@gmail.com> #85Nov 20, 2018 04:36PM

Issue exist in my 4gb 64gb variant too. My 2 year old Redmi note 3 clears 400+MB of Google Chrome cache in the time my Mi A2 takes to clear 20MB of cache. I don't think this is the problem of eMMc chips as various users have eMMcs from various vendors.
But if it's software why isn't there a fix already, it has existed ever since I bought the phone which was over 2 months ago. If this issue is not fixable and is rather hardware issue then Xiaomi is responsible and should replace the devices or refund the money we paid by accepting their faulty phones back.

re...@gmail.com <re...@gmail.com> #86Nov 20, 2018 04:59PM

Same issue to clean clear cache for Mi a2 4/64 Black

de...@gmail.com <de...@gmail.com> #87Nov 20, 2018 06:43PM

EMMC chip is bad and no software update will solve this

mr...@gmail.com <mr...@gmail.com> #88Nov 20, 2018 06:45PM

I have this too. Phone lags and at one point became irresponsive and restarted itself when trying to clear chrome cache.

sh...@gmail.com <sh...@gmail.com> #89Nov 20, 2018 08:24PM

I have the same issue

al...@gmail.com <al...@gmail.com> #90Nov 20, 2018 09:59PM

Noted.

On Tue, Nov 20, 2018, 10:24 PM <buganizer-system@google.com wrote:

- Show quoted text -

mc...@gmail.com <mc...@gmail.com> #91Nov 20, 2018 10:01PM

Same here

hr...@gmail.com <hr...@gmail.com> #92Nov 21, 2018 01:03AM

Same problem in LATAM, on Android O, fix It soon please

ju...@gmail.com <ju...@gmail.com> #93Nov 21, 2018 02:08AM

Same problem in LATAM, on Android P, slow memory reading

ja...@gmail.com <ja...@gmail.com> #94Nov 21, 2018 02:58AM

https://drive.google.com/file/d/1m3MI4tpqdog-zzJcy-2DGjVNVHq8i819/view?usp=drivesdk

Developers from Xiaomi are said to deny this issue saying benchmark apps cannot be trusted.
While enquiring about anything there is no response. One thing you find on internet is it's an Android One device, software is provided by Google directly. Then why is there delay in providing updates.
Set that all aside. Please atleast from here any developer acknowledge this issue exists. Tell us if it's the hardware issue or software issue and that can it be fixed. If it can't be fixed tell us that. We deserve to know to truth, after a year or so confirming this is a hardware issue won't do any good to us customers. Company will put their hands down telling the device is year old. If it's indeed a hardware issue and cannot be fixed, then the company is liable to replace the device or refund the money. It'll only happen if this issue is confirmed and acknowledged by the company. Since they're not doing this. I'm afraid it might indeed be a hardware issue. They're stalling us by not acknowledging this issue because the might not be a fix. I will wait for some more time. If there no official confirmation or any promise of fix, I'll file a lawsuit against the company. That was hard-earned money I spend on buying this device.

ma...@gmail.com <ma...@gmail.com> #95Nov 21, 2018 04:17AM

Same in Mi A2 4/64 with Emmc Micron

dd...@gmail.com <dd...@gmail.com> #96Nov 21, 2018 04:35AM

Dame here with Mi A2 4/64 with Hynix

ru...@gmail.com <ru...@gmail.com> #97Nov 21, 2018 05:05AM

Samee here 4/64

io...@gmail.com <io...@gmail.com> #98Nov 21, 2018 08:15AM

4/64 same here.. and with pie on

jj...@gmail.com <jj...@gmail.com> #99Nov 21, 2018 02:33PM

agreed, i have 4/64 version and i have this shit bug.

[Deleted User] <[Deleted User]> #100Nov 21, 2018 03:14PM

Same here 4/64 MICRON

ni...@gmail.com <ni...@gmail.com> #101Nov 21, 2018 06:31PM

Realmente desepcionante

ar...@gmail.com <ar...@gmail.com> #102Nov 22, 2018 01:44AM

Same prble here 4/64 micron

lu...@gmail.com <lu...@gmail.com> #103Nov 22, 2018 02:57PM

Esperamos una solución por favor. Same problem 4/64 MICROM

mi...@gmail.com <mi...@gmail.com> #104Nov 22, 2018 05:48PM

Same here :(, 4/64

ja...@gmail.com <ja...@gmail.com> #105Nov 22, 2018 11:11PM

Bug still on Android Pie
Bug report

https://drive.google.com/file/d/109TeBohGxNTXoSy2RUwHowLZYKr9bTvw/view?usp=drivesdk

ko...@gmail.com <ko...@gmail.com> #106Nov 23, 2018 12:03AM

please is it a software or hardware issue?

ra...@gmail.com <ra...@gmail.com> #107Nov 23, 2018 07:29AM

Is this problem on "lite" version too?

fr...@gmail.com <fr...@gmail.com> #108Nov 23, 2018 02:46PM

Same 4/64

ju...@gmail.com <ju...@gmail.com> #109Nov 23, 2018 03:07PM

Same 4/64

lu...@gmail.com <lu...@gmail.com> #110Nov 24, 2018 09:59PM

Esperamos una solución por favor. Same problem 4/64 ICROM

jo...@gmail.com <jo...@gmail.com> #111Nov 25, 2018 03:39PM

similarly, the same problem 4/64

ma...@gmail.com <ma...@gmail.com> #112Nov 26, 2018 12:26PM

Yes i have too....

ia...@gmail.com <ia...@gmail.com> #113Nov 26, 2018 09:34PM

I have the same issue. My phone's screen usually goes black and it stops work and after some time comes back to life. (Blue 4/64)

ma...@gmail.com <ma...@gmail.com> #114Nov 28, 2018 01:07AM

Same here 4 64

ty...@gmail.com <ty...@gmail.com> #115Nov 28, 2018 06:36AM

I solved this issue already. It is a software bug.

https://github.com/MiCode/Xiaomi_Ker...rce/issues/977

gi...@gmail.com <gi...@gmail.com> #116Nov 28, 2018 06:54AM

I solved this issue already. It is a software bug.

https://github.com/MiCode/Xiaomi_Ker...rce/issues/977

The link is dead...

sc...@gmail.com <sc...@gmail.com> #117Nov 28, 2018 12:59PM

some searching give me this link (not shortened)

https://github.com/MiCode/Xiaomi_Kernel_OpenSource/issues/977

to...@gmail.com <to...@gmail.com> #118Nov 28, 2018 07:50PM

4/64 black A2, problem still exists on Nov. 5. Security patch, android 8.1

al...@gmail.com <al...@gmail.com> #119Nov 30, 2018 12:48PM

Noted.

On Wed, Nov 28, 2018, 9:50 PM <buganizer-system@google.com wrote:

- Show quoted text -

em...@gmail.com <em...@gmail.com> #120Dec 1, 2018 11:39AM

4/64 android 9.0 and the problem still exists

ha...@gmail.com <ha...@gmail.com> #121Dec 2, 2018 01:23PM

Same for me, 4/64

co...@gmail.com <co...@gmail.com> #122Dec 2, 2018 10:32PM

Confirm That!!! 4/64 gb

ms...@gmail.com <ms...@gmail.com> #123Dec 4, 2018 11:13AM

I can confirm that it affects me too. Black, 4/64 global

va...@gmail.com <va...@gmail.com> #124Dec 4, 2018 11:46PM

unfortunately mine as well Mi A2 global black 4/64 xiaomi/jasmine/jasmine_sprout:8.1.0/OPM1.171019.011/V9.6.17.0.ODIMIFE, work well until i write large file

ju...@gmail.com <ju...@gmail.com> #125Dec 7, 2018 12:33PM

Same here, 4/64 blue. when im updating apps or move files the phone frezzess totaly, in some cases even reboot by itselft

an...@gmail.com <an...@gmail.com> #126Dec 13, 2018 12:54PM

Can someone from google provide an update on the issue? This issue has been opened since 2 months now

al...@gmail.com <al...@gmail.com> #127Dec 14, 2018 08:35AM

Same for me too, 4/64

ha...@gmail.com <ha...@gmail.com> #128Dec 14, 2018 11:20AM

same after pie update

jl...@gmail.com <jl...@gmail.com> #129Dec 14, 2018 11:35PM

I´m tired, i´m going to sell the phone. This is a completely joke!

da...@gmail.com <da...@gmail.com> #130Dec 15, 2018 04:31AM

Same, fix this

st...@gmail.com <st...@gmail.com> #131Dec 15, 2018 09:13AM

Conformità that! 4/64 with android pie

ja...@gmail.com <ja...@gmail.com> #132Dec 16, 2018 04:16PM

agree

y....@gmail.com <y....@gmail.com> #133Dec 16, 2018 05:15PM

Face unlock (smart-lock) not working on Android 9 V10.0.2.0.

oc...@gmail.com <oc...@gmail.com> #134Dec 17, 2018 08:12AM

Same issue, clearing chrome cache hangs the phone.

gi...@gmail.com <gi...@gmail.com> #135Dec 17, 2018 08:14AM

Is there any progress at all with this issue? Can someone inform us, please? This is getting really frustrating...

ib...@gmail.com <ib...@gmail.com> #136Dec 17, 2018 12:25PM

Having the same issue, hope it gets fixed soon.

ib...@gmail.com <ib...@gmail.com> #137Dec 18, 2018 04:35AM

Fixed

an...@gmail.com <an...@gmail.com> #138Dec 18, 2018 07:21AM

to #137 : there is no change in the status. Who fixed it ?

gi...@gmail.com <gi...@gmail.com> #139Dec 18, 2018 07:24AM

to #137: What do you mean and how is it fixed?

na...@gmail.com <na...@gmail.com> #140Dec 18, 2018 09:14AM

Same with December update Android Pie

ib...@gmail.com <ib...@gmail.com> #141Dec 18, 2018 01:51PM

#137 It's definitelly not fixed at all.

in...@gmail.com <in...@gmail.com> #142Dec 18, 2018 06:32PM

Same problem with android pie and december patch

ia...@gmail.com <ia...@gmail.com> #143Dec 19, 2018 04:04PM

that software bug was fixed 28 days ago by removing 3 lines of code (scroll above to see GitHub link to the fix) from drivers/mmc/card/queue.c but Xiaomi didn't push that fix to users, at least not yet. It's very frustrating.

<insert am i joke to you meme> here>

to...@gmail.com <to...@gmail.com> #144Dec 19, 2018 06:33PM

I would guess those 3 lines were there for a reason not just to make our
phones hang with large files. Issues that look simple usually aren't if you
don't know real reason behind them.

sre., 19. dec. 2018 17:04 je oseba <buganizer-system@google.com> napisala:

- Show quoted text -

su...@gmail.com <su...@gmail.com> #145Dec 20, 2018 06:02PM

Same here with my 4/64. Trying to clear chrome cache of 300+ MB completely hangs the phone, eventually leading to a restart.

do...@gmail.com <do...@gmail.com> #146Dec 21, 2018 10:43AM

same its December 2018 still the bug hadn't been rectified by android one developers. issuebis only with my 4gb /64gb variant. kindly fix the issue fast.

sa...@gmail.com <sa...@gmail.com> #147Dec 24, 2018 08:10AM

Yes the memory read/write speed is really not stable and is very slow causing freezes and lags. Also the cpu frequency sometimes gets stuck at 1401MHZ (Min) instead of 633MHz and is temporarily fixed only after reboot.

ab...@gmail.com <ab...@gmail.com> #148Dec 30, 2018 08:44AM

After December Patch is still there, What the Xiaomi is Doing and how the Os is distributed with such unstable code.
Totally frustrating the scenario is.

Kindly fix the issues.

se...@gmail.com <se...@gmail.com> #149Jan 1, 2019 03:46PM

i have the same problem

dw...@gmail.com <dw...@gmail.com> #150Jan 1, 2019 08:26PM

I have the issue, but notice that it ONLY happens when I have 2.4Ghz wifi active. Using 5Ghz wifi or disabling wifi altogether, the 512MB Seq Write eMMC tests perfectly in Androbench. I can do this over and over and will only have the issue when 2.4Ghz wifi is active.

Little history. I never had the issue, but at the time I only connected to my 5Ghz wifi. I was looking for a better wifi signal when I was in my backyard and jumped on 2.4Ghz. I then started seeing hickups and freezes with large files, games etc. Went to delete a large app and it took a minute or two to delete. I then ran the test with Androbench and saw my Seq Write test tank. Rebooting etc did nothing. Then I notice while running the test, wifi was overly active. I then disabled wife, cell data and bluetooth and ran the test again and it ran perfectly. Then turned back on wifi and the test tanked again. Tried 5Ghz, and the test was perfect again. Turned on 2.4Ghz....test tanked.

Hopefully someone else will see this and test it.

Testing with Androbench, 512MB test file.

sa...@gmail.com <sa...@gmail.com> #151Jan 2, 2019 01:29PM

mine too, Xiaomi Mi A2 4gb / 64gb, black. The phone works great but with unusual lag an freezes where it shouldn't be, for example when uninstalling an app, or minor but annoying like when typing.

an...@gmail.com <an...@gmail.com> #152Jan 7, 2019 01:39PM

As users who have opted into the android one program through Mi A2, i think we deserve atleast a response from Google after almost 2 and half months of this defect being open.

ri...@gmail.com <ri...@gmail.com> #153Jan 11, 2019 08:52AM

Agreed... also 4/64... i have also noticed when taking burst shots sometimes one or 2 photos came totally out of order... like it was saved later... is it related?
Also app uninstalling is a pain...
I see there is a private access issue blocking this one... does anyone has any info?

jl...@gmail.com <jl...@gmail.com> #154Jan 12, 2019 10:48AM

I have the solution. IT´s a HARDWARE BUG. So if your Mi A2 freezes constantly or takes a lot of minutes to clear an app cache and then restarted......ask for a replacement.

I have returned the phone and get a new one and now i´m happy. The new phone is not freezing.

pr...@gmail.com <pr...@gmail.com> #155Jan 12, 2019 04:00PM

I believe the priority should be upgraded to P2 from P3 since the device functionality is affected by this issue when triggered

I got the Mi A2 4/64 with Micron eMMC and DDR. The device is running on PIE V10.0.2.0.PDIMIFJ with December security update

Please find below Android bug report after reproducing the issue. File is also shared with android-bugreport@google.com

https://drive.google.com/file/d/1APRxqJ54P-tIQLJvbeTUNZ-o00V3f24H/view?usp=sharing

To reproduced the issue:
1. browse the web with chrome till cache is over 100MB, Instagram can also be used to reproduced the issue. So this is not a bug with chrome.
2. perform clear cache on chrome. The higher the cache size the longer the freeze. The phone is completely unusable while its clearing the cache.

Frequency
100% of the time when deleting a lot of files or cache with over 100MB

al...@gmail.com <al...@gmail.com> #156Jan 16, 2019 04:26PM

Any update in this problem? Its unbelievable not to be able to clear cache on a 250€ Android One phone! Mine is 4/64gb. Please we need a fix ASAP, it happens EVERYTIME so troubleshooting is easy!

co...@gmail.com <co...@gmail.com> #157Jan 16, 2019 10:37PM

same here. pity. micron emmc , 4/64 model

sa...@gmail.com <sa...@gmail.com> #158Jan 17, 2019 12:09AM

Wow, I've never tried clearing Chrome's cache, but when I did (it had up to 502mb), the phone froze, went completely unresponsive, most components in the UI went black, and finally the phone powered off... Please don't tell me it's a hardware issue... Xiaomi has like 0 official representation here in Argentina.

ms...@gmail.com <ms...@gmail.com> #159Jan 17, 2019 03:23AM

Even I have the same issue.kindly fix this ASAP

al...@gmail.com <al...@gmail.com> #160Jan 17, 2019 02:07PM

I'll write here everyday to ask for a fix. This is unbelievable.

ar...@gmail.com <ar...@gmail.com> #161Jan 17, 2019 02:12PM

You can write here everyday but you're only going to disappoint yourself. No developer in Google is watching this thread every day and feels like "oh no this guy is doing his daily online comment, i should change my strategy and fix it today". Most likely they are either already looking into it or they don't. And the same guy posting daily won't have any effect. Multiple new individuals that report do have a slight change of creating an effect

na...@gmail.com <na...@gmail.com> #162Jan 18, 2019 04:37PM

Same here in my Mi A2 4/64. It is a real pain. I had accumulated around 400 MB of chrome cache and tried to clear it. The phone froze for 5 minutes and then restarted. Also, it took a lot longer than usual for the phone to startup. It seems it recovered from a major problem. Hope I donot need to clear the cache again or download or use a big file.

we...@gmail.com <we...@gmail.com> #163Jan 22, 2019 08:46AM

Having the same issue here with my Xiaomi Mi A2 4/64.

al...@gmail.com <al...@gmail.com> #164Jan 22, 2019 03:20PM

Still no fix..

ro...@gmail.com <ro...@gmail.com> #165Jan 23, 2019 02:58PM

Same here.

jr...@googlemail.com <jr...@googlemail.com> #166Jan 23, 2019 09:37PM

same here, realy disapointed

[Deleted User] <[Deleted User]> #167Jan 31, 2019 07:47AM

Nota fix whit android pie :/ problema slow reading Andrés write.

[Deleted User] <[Deleted User]> #168Jan 31, 2019 07:49AM

Not fix whit android pie :/ problem slow reading And write.

al...@gmail.com <al...@gmail.com> #169Feb 1, 2019 01:48PM

And still no fix...

to...@gmail.com <to...@gmail.com> #170Feb 2, 2019 02:42AM

Hola no va a ver solución?

st...@gmail.com <st...@gmail.com> #171Feb 5, 2019 09:38PM

Having the same issue here.
Xiaomi=shit

an...@gmail.com <an...@gmail.com> #172Feb 8, 2019 05:35PM

Same here

pm...@gmail.com <pm...@gmail.com> #173Feb 8, 2019 05:51PM

Same problem A2 4/64

ma...@gmail.com <ma...@gmail.com> #174Feb 10, 2019 06:37PM

Deleting cache or any app with more than 50MB cause the phone freeze entirely (eventually will unlock after several minutes). No changes after the january update. Problem persist since I got this phone. Mi A2 Black, 64+4.

al...@gmail.com <al...@gmail.com> #175Feb 12, 2019 06:36PM

..and still no fix..

je...@gmail.com <je...@gmail.com> #176Feb 18, 2019 12:31AM

Hi, I have the same issue, my eMMc is MICRON brand, mi model is 64gb/4 RAM with Android 8.1 november 2018 patch.
When I tried to clear the Chrome's cache (600MB) the screen turn black and after a few minuted the phone just restarted by itself.

https://drive.google.com/drive/folders/1S6jKQiDg-k3X7zxL7MRGfD8K5ozdJJyo?usp=sharing

al...@gmail.com <al...@gmail.com> #177Feb 18, 2019 08:18PM

android pie and the problem is here :(

ju...@gmail.com <ju...@gmail.com> #178Feb 19, 2019 07:03AM

the problem continues, confirmed in my Xiaomi Mi A2 4GB Ram 64GB Rom

un...@gmail.com <un...@gmail.com> #179Feb 20, 2019 01:01AM

Same problem 4/64

gp...@hotmail.com <gp...@hotmail.com> #180Feb 20, 2019 10:51AM

Same here, 4/64 and MICRON chip.

ir...@gmail.com <ir...@gmail.com> #181Feb 21, 2019 04:46PM

the problem continues, confirmed in my Xiaomi Mi A2 4GB Ram 64GB Rom - Android Pie

ga...@gmail.com <ga...@gmail.com> #182Feb 22, 2019 02:41AM

Remove all this

al...@gmail.com <al...@gmail.com> #183Feb 23, 2019 12:04AM

...still no fix...

os...@gmail.com <os...@gmail.com> #184Feb 26, 2019 12:09PM

Hi,

The problem persists with the February update, we need a solution.

Best Regards

ko...@gmail.com <ko...@gmail.com> #185Feb 27, 2019 12:49AM

sorry but this is a bad bad bad support what a shame

ze...@gmail.com <ze...@gmail.com> #186Feb 27, 2019 01:38PM

i can confirm the problem still is here with the February update and i have occasional stutters when typing a SMS or using whatsapp but mostly when typing a SMS in the default messaging app, its a shame poor support from google besides part of the android one program....

ze...@gmail.com <ze...@gmail.com> #187Feb 27, 2019 01:52PM

here is the bug report

https://drive.google.com/file/d/1dgPJ849X-TwcmxL5TPazYCBnrdZ3u9kM/view?usp=drive_web (bugreport-jasmine-PKQ1.180904.001-2019-02-27-18-36-09.zip)

and i believe all phones having micron as a manufacturer of emmc are affected

deleted

Restricted

0 B

ad...@google.com <ad...@google.com> #188Feb 28, 2019 05:51AM

Re:

comment #187

can you please share the Google Drive link with android-bugreport@google.com

ze...@gmail.com <ze...@gmail.com> #189Feb 28, 2019 06:11PM

done

ad...@google.com <ad...@google.com> #190Mar 1, 2019 09:58AM

Thanks.

ja...@gmail.com <ja...@gmail.com> #191Mar 1, 2019 11:35AM

It's not just micron, i have a hynix eMMC. I have issue. So far with the information I got, mainly people who bought the device in early time around launch have this issue. My friends who bought the device in December and January don't have this issue. I really think it's some kind of manufacturing defect with eMMC. Why else they can't fix it yet ? This issue tracker thread was created in October 22 . It's been too long. But how come eMMC from different manufactures have this issue then. Neither Xiaomi or Google is giving clarification on this matter.

as...@gmail.com <as...@gmail.com> #192Mar 1, 2019 04:56PM

I have this issue too.. now i feel like miui devices perform way better than.the so called stock android device.. hate it when it lags...

Any solution??

jo...@gmail.com <jo...@gmail.com> #193Mar 3, 2019 04:43PM

Is there a solution or its a hardware problem?

al...@gmail.com <al...@gmail.com> #194Mar 5, 2019 11:46PM

Still no fix....

je...@gmail.com <je...@gmail.com> #195Mar 6, 2019 06:17AM

GOOGLE, PLEASE TAKE A LOOK AT THIS:

https://github.com/MiCode/Xiaomi_Kernel_OpenSource/issues/977

an...@gmail.com <an...@gmail.com> #196Mar 6, 2019 10:15AM

Not sure why would Google not even take a look at the fix being suggested?
Can some one from Google work on this on priority? It affects all the A2 phones with 4/64 config.
After all its an android one device.

jo...@gmail.com <jo...@gmail.com> #197Mar 6, 2019 04:08PM

Is there any rom with the problem fixed?

ry...@gmail.com <ry...@gmail.com> #198Mar 7, 2019 06:18AM

This is affecting my device as well and is very easy to replicate. Fix this shameful bug and get some pride in your work already!

an...@gmail.com <an...@gmail.com> #199Mar 7, 2019 08:47PM

Freeze bug here 🖐️

ha...@gmail.com <ha...@gmail.com> #200Mar 7, 2019 09:29PM

Same here, its a shame that a system using sto k android works like this :(

pu...@gmail.com <pu...@gmail.com> #201Mar 7, 2019 09:45PM

Same here, i tried yesterday to empty Chrome cache and phone just froze and then rebooted.

sa...@gmail.com <sa...@gmail.com> #202Mar 7, 2019 10:04PM

Worst case scenarios (like clearing 600mb of Chrome's cache) results in Settings, Chrome and Quickstep app (Default launcher on Mi A2) not responding. Sometimes System UI too, and finally a quick reboot of the phone unexpectedly.

nt...@gmail.com <nt...@gmail.com> #203Mar 7, 2019 10:08PM

Easily to reproduce and happens 100% of the time.

st...@gmail.com <st...@gmail.com> #204Mar 7, 2019 10:10PM

Plz fix this so we can use the device

ha...@gmail.com <ha...@gmail.com> #205Mar 7, 2019 10:14PM

no one cares. about this issue 😑 because our mi a2 is low budget , otherwise they will fix issues and take this issue seriously

ar...@gmail.com <ar...@gmail.com> #206Mar 8, 2019 12:04AM

Same here for me. Have the 4GB RAM and 64GB Internal Storage variant and face these freeze of 2-3 seconds while normal device usage.

jo...@gmail.com <jo...@gmail.com> #207Mar 8, 2019 01:42AM

I have this issue too, it happens every time I try to clean cache.

ho...@gmail.com <ho...@gmail.com> #208Mar 8, 2019 01:49AM

This seems to be a hardware issue:
The changes referenced in

https://github.com/MiCode/Xiaomi_Kernel_OpenSource/issues/977 are included in the custom hex kernel (

https://forum.xda-developers.com/mi-a2/development/kernel-hex-t3855773) . Unfortunately also using this kernel the slow write speed issue remains.
So it's very likely nothing will happen: Google will not push vendors to fix hardware issues and Xiaomi has most likely silently fixed this in latest shipping versions of the A2.

ma...@gmail.com <ma...@gmail.com> #209Mar 8, 2019 01:58AM

Same here

ti...@gmail.com <ti...@gmail.com> #210Mar 8, 2019 05:24AM

issue affected my MI A2 as well. device tend to freeze whenever clearing cache which are more than 50MB.
Been using the 4GB 64GB variant.

sa...@gmail.com <sa...@gmail.com> #211Mar 8, 2019 07:03AM

Had the same issue ever since I bought the device last September. Mine is the 4/64GB variant. Yesterday I had the worst experience of clearing my cache and storage. It got stuck to a black screen and when I tried to restart the phone, it got stuck to the restarting logo for a few solid minutes. I thought the phone was gonna get bricked that moment. For an Android One phone, I am totally NOT impressed by this.

al...@gmail.com <al...@gmail.com> #212Mar 8, 2019 07:22AM

Ok

Em sex, 8 de mar de 2019 04:04, <buganizer-system@google.com> escreveu:

- Show quoted text -

br...@gmail.com <br...@gmail.com> #213Mar 8, 2019 08:01AM

4/64 and a lagging phone.

s....@gmail.com <s....@gmail.com> #214Mar 8, 2019 08:12AM

4/32 and it is too annoying everytime this happens

to...@gmail.com <to...@gmail.com> #215Mar 8, 2019 08:17AM

Fingerprint sensor bug only got solved when it was reported by few online news sources. I doubt anything will happen with this bug unless it gets some news coverage. Even then, if it's really HW bug, I doubt we'll get any solution.

an...@gmail.com <an...@gmail.com> #216Mar 8, 2019 08:42AM

@215. Even if its a hardware bug, Xiaomi needs to provide us a hardware fix. Replace the defective memory chip with a good one. They should not escape by selling a defective hardware to us.

to...@gmail.com <to...@gmail.com> #217Mar 8, 2019 08:56AM

We all know what they should do, but what are our options, Xiaomi being Chinese company, if they don't provide a solution?

lo...@gmail.com <lo...@gmail.com> #218Mar 8, 2019 09:05AM

@216
That's not feasible. What they should do is officially acknowledge the problem and tell us if it can be fixed (sw issue) or can't be fixed (hw issue).
If it's hw they should at least mitigate the problem, a slower phone is better than a crashing phone.
A company with morals and respect for its customers would then offer some sort of compensation, but history teaches us that even the big players like Apple don't cope well with their own fuckups (remember the antennagate?).
What I hate of this situation is the lack of communication, after every software update I check to see if the issue is fixed and not only the phone crashes, but after the reboot other things begin to misbehave! What they change remains a mistery.

an...@gmail.com <an...@gmail.com> #219Mar 8, 2019 09:10AM

@218. So true. Their changelogs have always been a joke. And regarding the compensation, you are right. Companies in this industry are not known to accept their mistake except very few.
At this point of time all we can do is pester this issue to Xiaomi and Google and not leave it at that.

es...@gmail.com <es...@gmail.com> #220Mar 8, 2019 09:20AM

Did someone try to bring the phone under warranty with this issue to repair center? I know it's country specific / repair center specific, but it would be interesting to know if they solve it with a hw replace with another eMMC.

os...@gmail.com <os...@gmail.com> #221Mar 8, 2019 09:48AM

same happening with me

ar...@gmail.com <ar...@gmail.com> #222Mar 8, 2019 12:47PM

My Mi A1 completely died while flashing an update, so i think its EMMC is dead too. Xiaomi is just destroying android ones name now. It was the 4/64 version.

lo...@gmail.com <lo...@gmail.com> #223Mar 8, 2019 04:21PM

I've the 4/64 version and that's mess. Sometimes it gets slower than my old LG G2. It's a phone from 2013. That was one of my worst experiences on a smartphone, I miss so much my old OnePlus phones.

le...@gmail.com <le...@gmail.com> #224Mar 10, 2019 06:05AM

I bought this phone last week and have same problem, 280 read and 50write

da...@gmail.com <da...@gmail.com> #225Mar 10, 2019 06:49AM

https://drive.google.com/file/d/0ByVaUcvngB4Tc3RhcnRlcl9maWxl/view?usp=drive_web

be...@gmail.com <be...@gmail.com> #226Mar 10, 2019 01:43PM

Notice that periodical freezes while in chrome and google apps

le...@gmail.com <le...@gmail.com> #227Mar 10, 2019 10:30PM

I tested with wifi off and my speeds are back to normal, 220write and 280 read. Strange but I'm satisfied to my phone not have an hardware problem with emmc.

an...@gmail.com <an...@gmail.com> #228Mar 14, 2019 08:43AM

The cache clearing issue exists even after march update. At this point of time I have lost hope.

sh...@gmail.com <sh...@gmail.com> #229Mar 14, 2019 01:32PM

Me to, please fix the bug network settings only 2G 3G

ri...@gmail.com <ri...@gmail.com> #230Mar 14, 2019 03:09PM

I also agree with the wifi on/off...
Sometimes some app freezes while getting something from the memory (like loading a photo)... but when i turn off the wifi... it loads instantly...

yk...@gmail.com <yk...@gmail.com> #231Mar 15, 2019 11:32AM

Seriously Android one by Xiaomi is a joke. They didn't even fixed this issue till now.

al...@gmail.com <al...@gmail.com> #232Mar 16, 2019 07:19AM

...and still no fix...

an...@gmail.com <an...@gmail.com> #233Mar 16, 2019 01:23PM

Can we have an update on the status of this issue? Can google give a valid reason and close if it is not their purview to fix it. Add Can google or Xiaomi anyone let us know if this is a hardware or software bug ?

le...@gmail.com <le...@gmail.com> #234Mar 16, 2019 03:39PM

Here is my bug report. Mi A2 4/64gb Blue version, manufactured in november/2018 and micron memory. I have slow emmc too.

deleted

Restricted

0 B

deleted

Restricted

0 B

deleted

Restricted

0 B

deleted

Restricted

0 B

an...@gmail.com <an...@gmail.com> #235Mar 16, 2019 03:53PM

Attaching the log where I cleared cache of 2 to 3 apps.

deleted

Restricted

0 B

ri...@gmail.com <ri...@gmail.com> #236Mar 16, 2019 04:12PM

Does anyone have any info about the issue blocking this one?

nt...@gmail.com <nt...@gmail.com> #237Mar 16, 2019 11:44PM

https://www.mysmartprice.com/gear/redditors-report-issue-emmc-storage-xiaomi-mi-a2-files-take-longer-time-delete/

https://www.bgr.in/news/xiaomi-mi-a2-internal-storage-file-transfer-issue-reported-by-reddit-users/

More posts like these will help

an...@gmail.com <an...@gmail.com> #238Mar 18, 2019 07:01AM

these articles itself are 4 months old and there has been no progress since. I would suggest if Google or Xiaomi does not respond to issues here, we should all be taking our devices to the services centres.

ke...@kfngou.info <ke...@kfngou.info> #239Mar 20, 2019 04:54AM

You are not going to fix it. Right? No more Android One phones anymore for me.

ca...@gmail.com <ca...@gmail.com> #240Mar 20, 2019 08:33PM

I have two Mi A2s.
I got slow write speed with 4/64 gold on Mikron memory (56mbps)
No problem with 4/64 black on Samsung memory(190 mbps).

gi...@gmail.com <gi...@gmail.com> #241Mar 20, 2019 09:22PM

Same here!! 4/64. Global version.

ti...@gmail.com <ti...@gmail.com> #242Mar 20, 2019 10:46PM

Same problem here, Global version 4/64 micron memory. Very slow clearing cache, also uninstalling apps. It can also cause the system ui to hang and become unresponsive for up to a few minutes, sometimes resulting in the phone rebooting.

an...@gmail.com <an...@gmail.com> #243Mar 21, 2019 07:36AM

I have Hynix memory. Does not have the slow write speed, but have the cache clearing issue. Phone gets stuck when clearing cache more than 200MB

zo...@gmail.com <zo...@gmail.com> #244Mar 21, 2019 09:18AM

Issue still here. Using 4/64 version, black. And I don"t know if this is a separate problem, but I get every half an hour black screen on a tab in chrome. I can't go back or refresh the page, it stays black. Only thing to do is close the tab and reopen the page in a new tab.

Thought this was a great phone, but I'm starting to get frustrated over this.

pl...@gmail.com <pl...@gmail.com> #245Mar 21, 2019 01:46PM

Same problem with my 4/64 Black Global

ra...@gmail.com <ra...@gmail.com> #246Mar 22, 2019 12:25PM

Until WHEN? 4/64 Black Global here.

ni...@gmail.com <ni...@gmail.com> #247Mar 23, 2019 02:14AM

Dear Google Please Solve this serious issue

an...@gmail.com <an...@gmail.com> #248Mar 25, 2019 07:44AM

any update on this Google ?

al...@gmail.com <al...@gmail.com> #249Mar 26, 2019 01:20PM

And still no fix..

mi...@gmail.com <mi...@gmail.com> #250Mar 26, 2019 10:22PM

Same here 4/64

kf...@gmail.com <kf...@gmail.com> #251Mar 27, 2019 05:03AM

Fix it with XiaoMi ASAP. Android One program is going to be ruined by XiaoMi.

ja...@gmail.com <ja...@gmail.com> #252Mar 27, 2019 02:51PM

Guys , I got my device replaced under warranty . I'm from India. If you have warranty take it to service center and ask for replacement .And yes I don't have issue anymore. Got a new 4/64 Black unit. Software /Hardware issue ,I don't think xiaomi or Google intend to fix it . Heavens they haven't acknowledged this issue given its been here for months .I found a thread on issue tracker for Nokia 7 plus which have the same issue , it hasn't been solved and it's been over a year. But I only sighted that one unit of Nokia unlike A2 users who faces this issue in large numbers.

an...@gmail.com <an...@gmail.com> #253Mar 27, 2019 03:00PM

@252. Wow. I reside in India as well. Going to do it ASAP. By the by how did you prove the issue to them? Did they easily agree to replace to it ? What was the reaction of the service centre guys ?

ja...@gmail.com <ja...@gmail.com> #254Mar 27, 2019 03:14PM

I had previously gone twice there. So they understood the issue when I demonstrated it to them. I compared clearing cache on both my old Redmi note 3 and A2 at once. Note 3 cleared 500+ MB instantly and A2 took quite a long to clear just 283MB or so and froze and restart while trying to switch back from home screen. Time actually took for them to convince xiaomi about the issue. After that it took about 4 days for device to arrive at the service center. I'm in Kerala. I had submitted my device there on 15th of March. So it took about 12 days. Device arrived yesterday evening I guess. But they only called me today morning. And service center guys were supportive. They had to record and send video of issue to prove the issue to xiaomi . They did all they could . But they had told me they only do repairs. And even if it's a hardware issue they would probably replace motherboard. But instead I got a call last Thursday evening from them saying a new handset replacement have been approved.

an...@gmail.com <an...@gmail.com> #255Mar 27, 2019 03:20PM

Thank you. I will try my luck lets see what happens. I do have chrome setup right now even thought generally I do not use it.

al...@gmail.com <al...@gmail.com> #256Mar 28, 2019 11:26AM

I won't stop asking a software fix. Where is it?

sa...@gmail.com <sa...@gmail.com> #257Apr 1, 2019 05:48PM

Yes im also facing this issue try to fix it

ge...@gmail.com <ge...@gmail.com> #258Apr 5, 2019 08:00PM

I've been using this phone almost three months now and it gets harder every day to clear the cache of any program. It takes about a minute to clear it and blocks everything in my phone along the way. This issue is not persisted on any custom rom, other developers seem to have it fixed, now is the time Google to do it also.

It's a shame that such a good hardware to perform so badly.

zo...@gmail.com <zo...@gmail.com> #259Apr 5, 2019 08:03PM

Received the March update yesterday, but the problem still exists. Fix this please!

na...@gmail.com <na...@gmail.com> #260Apr 6, 2019 08:03PM

Same problem here, starts yesterday. 4/64 Black Global. Last update in March 25th.

ag...@gmail.com <ag...@gmail.com> #261Apr 9, 2019 07:10AM

Freaking bugs

mi...@gmail.com <mi...@gmail.com> #262Apr 9, 2019 03:25PM

Same issue here idk what to do anymore my keyboard even freezes when i try to type fast

ma...@gmail.com <ma...@gmail.com> #263Apr 9, 2019 07:24PM

I have the same problem, keyboard freezes, freezes after clearing cache in chrome history....We need the explanation and possible fix

ri...@gmail.com <ri...@gmail.com> #264Apr 9, 2019 07:32PM

It's basically impossible to clean the cache after it reaches a few hundred MB. Phone is becoming slower now to save stuff or uninstall app.
I don't care about the reason anymore, just fix it.

an...@gmail.com <an...@gmail.com> #265Apr 10, 2019 05:51AM

Ok, so I have an update on this. Recently i took my phone to mi service center and showed them the issue. First they clean flashed the phone to check if its not software.
They took the bug report and sent it to their technical team to see if they approve a motherboard change or phone replacement. When i called the service center again they told me that the tech team has analysed the bug report and are working on a software fix. The service center said, they will let me know more info this thursday.

ri...@gmail.com <ri...@gmail.com> #266Apr 10, 2019 10:52AM

But did they confirm that it is a sw issue? Or are they working on a "workaround"?

I'll give u an example... A oem that have a issue with a memory, in order to fix the issue, it needs a new firmware, but the update is not possible. So instead of fixing the issue, they make a workaround on android (like not allow the ui to freeze when clean cache is pressed, but the slow memory rw speeds is still low, making it hang in other ops)

an...@gmail.com <an...@gmail.com> #267Apr 10, 2019 11:09AM

@266. I think the there are 2 different issues here.
1. emmc slow write speeds.
2. Cache clear issue.

My phone does have constant write speed of around 200. So looks like i do not have

issue 1

.
The 2nd issue seems to have affected every 4/64.

The service center guy could not give much details into this since he might not be aware of the technical intricacies.
All he told me was they are working on a fix and they will roll it out.
Like i said i will try to extract more info tomorrow.
But i suggest everyone who has access to mi official service, should visit it and push it.
If it is a hardware issue, they should be able to replace the motherboard or phone.
But one thing is for sure, service center cannot reject this issue since it so obvious.

ak...@gmail.com <ak...@gmail.com> #268Apr 10, 2019 11:10AM

This issue is a software issue and has already been fixed in custom ROMs.

On Wed, Apr 10, 2019, 4:39 PM <buganizer-system@google.com> wrote:

- Show quoted text -

ar...@gmail.com <ar...@gmail.com> #269Apr 10, 2019 11:17AM

Good thing you are trying to push it in a service center. But i guess many of us are unfortunate of not having a Xiaomi servive center around. All i can do is contact a chinese reseller... I had to import this phone because our telecom blocks this good price/quality brand. They rather push expensive Samsungs and Apples into our hands...

an...@gmail.com <an...@gmail.com> #270Apr 12, 2019 06:34AM

@269. I think you should wait if you do not have access to official service center. If it turns out to be a software issue, its a hassle for you.
I will not let this leave till it reaches an official conclusion.
I would suggest everyone who has access to mi service center should bring this to their notice and let them take a call.
I think 6 months is enough time we gave them.

ri...@gmail.com <ri...@gmail.com> #271Apr 12, 2019 11:45AM

But man... i'm still pretty sure we have only one issue... at least seeing the "symptoms" and by having worked on an OEM...
I still think that a SW can make a workaround... but i totally agree with going to service center. This increase their "worries" on each country, when a country surpass a certain level, they start asking the developers to find a fix.
When a service center work for a certain OEM, their expenses are passed to the OEM. Like "bought a mi a2, but the guy had a problem within 10 days and asked for a new device" etc.

So if you have service center, the best is to have numbers right now, so xiaomi start working on it.

Just one thing that i always notice but never asked. This thread, on the right side, has some info about the issue. "In Prod" is OFF, anyone knows why? and why the priority and severity is so low?

In Prod, i'm pretty sure means that it is detected in production units. Not sure if it actually means "detected in production line", but i'm pretty sure is the former one. Anyone has any info about this?

wh...@gmail.com <wh...@gmail.com> #272Apr 12, 2019 01:47PM

It's a hardware issue. Bring it down to the service center and get it fixed asap.
A software workaround to a hardware problem may or may not materialize.
It'll probably drag on forever till the warranty if any expires.
If you are still waiting for a software workaround, good luck.

lo...@gmail.com <lo...@gmail.com> #273Apr 12, 2019 02:39PM

Are you sure it is a hardware issue? I've seen people reporting that issue was fixed after flashing the MIUI 10.

my...@gmail.com <my...@gmail.com> #274Apr 12, 2019 03:00PM

Are you sure it's a software issue? I have never seen anyone reporting that the issue has been fixed after 9 months of software updates.

[Deleted User] <[Deleted User]> #275Apr 12, 2019 04:53PM

This is getting worst!
I should have known about it...
I bought Mi A2 12 days ago online!!! And it has started signs of lags in 3-4 days
I'm a gamer and needs speed... I'm depressed
I love GOOGLE,But about this nah not?
(The big thing is it lagged while typing here too)

ri...@gmail.com <ri...@gmail.com> #276Apr 12, 2019 04:57PM

@274
Actually i have seen some saying that different kernels had this fixed...
I can't say for sure if this is actually fixed or just "fixed".

But read/write in emmc can usually lead to a firmware upgrade (of the emmc) which usually the OEM won't release because it needs lots of tests and performance check etc. If this problem is related to Micron, then yeah.. even if it can be considered possible to be solved, it won't....

[Deleted User] <[Deleted User]> #277Apr 12, 2019 05:01PM

@276
Should I consider that it will be fixed in the April/May or the next Q version update....or should I plan to get a new phone (Honor play either)

ri...@gmail.com <ri...@gmail.com> #278Apr 12, 2019 05:08PM

Imho... Memory issues are usually really bad. Not that it's not fixable, but i saw the devs try any workaround instead of actually acknowledge the issue and fix it. So any type of known issue (like nexus 6 processor dying, samsung s6 sudden brick etc) is better to consider that the phone might be usable and might have a sw to fix it, but the sooner you go to a better phone, the best...
But that's my opinion... Because i understand that oem cares only to sell it... They won't receive anything after the sales... So upgrades are costly and it's preferred to release a new phone, instead of wasting good devs making updates.

[Deleted User] <[Deleted User]> #279Apr 12, 2019 05:15PM

@278
Will rooting help to fix it?
Installing other ROMs. I'm a tech geek and I'll do it somehow
(16 year old actually). Should I wait for the update or I upgrade to a new one.....it really looks odd when you're changing your phone 2 times under 1 month in a middle-high class family.
I've had a lag even writing this. The phone rebooted. (I even have a REDMI NOTE 3, should I switch to it or should I face these bugs and wait the next update?(also when the April security patch is coming,do these patches fix all these,and will it fix it,maybe Google is paying attention and is not telling us)

ri...@gmail.com <ri...@gmail.com> #280Apr 12, 2019 05:25PM

Well... Depends on where this issue really is located....
Android basically has a top java layer (app) that is the settings... When you press the clean cache it will call inner layers (c c++), deciding that it will clean the cache, it will ask for a more deeper layer, which is the memory chip code itself (I'm over simplifying...).
If the emmc firmware is not working, nothing we can do. If we can make a workaround, it would be in kernel layer, maybe setup some look ahead parameters etc, just guessing... If this is an android system issue, then it's google issue (but then, other phones from different oems should be showing this same behaviour, but can be hard dependent, like very hard to reproduce if you have more memory or faster cpu...). If it's system... A different OS like paranoid, could fix this, but doesn't seem to be... Since many ppl are saying that hex kernel fixed this issue... It might be possible to mitigate it, but again, can't confirm if this really fix it. We would need internal information from xiaomi devs to understand what's going on...

ja...@gmail.com <ja...@gmail.com> #281Apr 12, 2019 05:55PM

I don't think xiaomi hasn't been updating kernel of A2. They for sure have been updating it there by downgrading the performance. From my replacement unit i took androbench test before every update , what I found is i got 85MB/s in November security patch oreo and after pie update with november security patch itself got about 48-54MB/s and then I got straight 1GB update to february patch there i got 28MB/s after march update I gets around 13-17MB/s . I'm talking about Random Write speed and they have been seriously downgrading it , sequential write is always over 250MB/s for me . Sequential read and write as always over 200-250MB/s on my old AW too. Now it takes about 10-12 seconds to clear 500MB cache while it only took 1-2 seconds in November patch where random write speed was higher but device doesn't freeze or hang. In my old A2 it would take more than 1 minute to clear 300+MB cache and device used to freeze and becomes unusable for some time. So clearly low random write speed can account to slower cache clearing . That issue came to being in my new device as well after updating but it only takes 12 seconds compared to minutes in old one and device don't hang. So phone freezing while cache clearing might indeed be a hardware issue and slow clearing only problem a software one. I'm no expert but experts have banana down their throats and have nothing to speak up despite these manju people reporting the issue. So I think if you only have slower cache clearing and your device don't freeze then it might be a software problem . If it's freezing try to get it replaced before warranty goes void. Also one another thing I noticed was SQLite operations in oreo /november build had about 800-900 range of iops value while latest updates have 1500-2500 iops . I think they improved SQLite operations but Random write speed was compromised.

ri...@gmail.com <ri...@gmail.com> #282Apr 12, 2019 05:56PM

@279
Do you wanna know how i am pretty sure that xiaomi won't fix it soon?
The priority and severity... it's just too low... Usually P0 = show stopper...

What usually occurs is the following:
OEM allocate some devs to a project (phone model). This team is the tier engineers, there will be design, hardware, sw and each divide into other teams (UI, kernel, sensors, touch... etc). After the release of the phone, this team is allocated to other phone model (that's why we have phones every 6 months basically), and usually some variants are done by different teams (like a p30 and p30 pro, s10, s10e), and usually they only exchange a few info, so some issues might be fixed on one but not on the other...
When a security patch from google comes, it's basically integration, so the teams just apply the patches and release a test sw... no big deal.
But a new android usually needs more work, so they need a few devs to reapply patches, fix some new bugs, but i doubt (seriously doubt) that xiaomi reallocate the same devs and tests, basically because the phone is already sold on the market and won't make more money of it. So this new integration lacks tests and details. That's why, usually, the first sw that comes with the phone is the most stable. They will, obviously fix the issues every new update, but there won't be that "big team" that was allocated when the phone is released.
So can we expect this issue to be fixed in the next patch? I hardly doubt. Can it be fixed in Android Q? Maybe... with different kernel...

The best thing we can do... go to service center and describe the SAME issue.
Service center labels the issues from each OEM, so if a phone has "freeze" and the other says "clean cache not working" and the other says "slow", this might be considered 3 different issues, counting overall 1 issue each, instead of 3 issues of the same subject.

The more issues the service center has from an OEM, the higher the bill for that OEM, basically...
So we need to make people start moving to service center, which will make (i hope...) this issue priority higher.

[Deleted User] <[Deleted User]> #283Apr 13, 2019 03:49AM

@282
If you're sure that Xiaomi won't fix it soon...
What your probability when they will fix it(approximately?)

wh...@gmail.com <wh...@gmail.com> #284Apr 13, 2019 03:50AM

Just bring it back to the service center be it hardware or software.
If they cant fix it, ask for a refund.
If they refuse, contact a consumer organisation or regulatory authority.
We shouldn't have to live with a defective product.

For example

https://ec.europa.eu/info/live-work-travel-eu/consumers/resolve-your-consumer-complaint/european-consumer-centres-network_en

wh...@gmail.com <wh...@gmail.com> #285Apr 13, 2019 03:55AM

The problem has been known since oreo and has persisted all the way. The probability of them releasing a software workaround for the defective hardware decreases exponentially with time. It has been 9 months, their warranty obligation is 12 months. Go figure.

ri...@gmail.com <ri...@gmail.com> #286Apr 13, 2019 06:27AM

@283
I'm not sure if they will or won't fix it...
What i believe is... If there is a slight possibility to be fixed in kernel... And with this p3... In android Q (with very small probability). Unless the phone becomes unusable and people start to complain, i would say that this won't be fixed ever

an...@gmail.com <an...@gmail.com> #287Apr 13, 2019 09:43AM

Service center has again told me that this issue will be fixed in April patch which will be released in 2 3 days as beta.

my...@gmail.com <my...@gmail.com> #288Apr 13, 2019 09:53AM

I would rather get a refund. They had 9 months to fix and it it wasn't fix. What's the chance that it'll be fixed in the next 2-3 days? A Big Fat Zero.

ri...@gmail.com <ri...@gmail.com> #289Apr 13, 2019 10:49AM

Well... Can't buy another and i enjoy android one a lot... So I'm just hoping that they fix it... I had a mi a1 and it was a nice phone... Issues occurs... they are basically forced to release new phones constantly, it is very hard to make all of them without any failures... Besides this issue, i see no other problem with this phone... And for this price....

wh...@gmail.com <wh...@gmail.com> #290Apr 13, 2019 05:14PM

If you are fine with the faulty hardware then i guess that's not an issue. Each to their own i guess. Good luck waiting for the fix.

ri...@gmail.com <ri...@gmail.com> #291Apr 13, 2019 05:44PM

@290 well, imho, I don't know why someone who is sure that this is a hw issue be replying on an issue tracker..

But you are right that waiting for a solution that likely won't be released is a waste of time. If i had the money i would totally go for a different phone, but not everybody can just get a new one that easily. And without any xiaomi service center in here... I guess i will just wait to get money to get a better one...

al...@gmail.com <al...@gmail.com> #292Apr 14, 2019 08:14AM

...and still no fix...

wh...@gmail.com <wh...@gmail.com> #293Apr 15, 2019 01:01AM

Well, I was waiting for a software fix too, that's why i'm on the issue tracker. But it is a hardware fault. What you are waiting for is a software workaround. Insisting that it's a software bug doesn't change the fact that the hardware is faulty. All you are doing is misleading others to think that there's nothing wrong with the hardware and preventing them from getting their phone fixed.

ri...@gmail.com <ri...@gmail.com> #294Apr 15, 2019 10:58AM

@293
I think you are not understanding my point.
Again, we, who have no real information where this issue can be located, cannot say "it is a hardware issue" or "it is a software issue". Unless you have xiaomi stating "micron emmc batch was faulty" or anything near that, you cannot confirm that this is a hardware issue. Actually, you stating that this is a hardware issue is more than misleading, as you are just as clueless as any of us really are.

Another point, i am not waiting for a workaround, read the thread, that's what it is here for. If there is a hardware issue, xiaomi can only "fix it" with a workaround via software, as they won't say "hey users, we found this issue so we will repair your phone for free". What i am saying is, think as the OEM, do you think they will want to lose money in a mid range phone that is likely not being used by any "major content share" like mkbhd and others, that can really make any impact on sales?
If this is a SW issue, xiaomi MIGHT fix it, but again, it is not likely, because the priority level and severity.

And again, read the thread, I have mentioned a way to make people getting their phones fixed:

"The best thing we can do... go to service center and describe the SAME issue.
Service center labels the issues from each OEM, so if a phone has "freeze" and the other says "clean cache not working" and the other says "slow", this might be considered 3 different issues, counting overall 1 issue each, instead of 3 issues of the same subject.

The more issues the service center has from an OEM, the higher the bill for that OEM, basically...
So we need to make people start moving to service center, which will make (i hope...) this issue priority higher."

If you have information that this is a hardware issue, we will all be happy if you bring it here, so anyone can actually force their phone to be exchanged by xiaomi. If you have that information and you are not providing, you are the one preventing people to get their phone fixed.
If you don't have the information, then don't come here saying trash, we are all expecting a fix or a position from xiaomi. If this is a SW issue but xiaomi won't make any fixes until android Q, i am ok with that. But if they say that they won't make any fix at all, i would start considering using a custom rom.

ri...@gmail.com <ri...@gmail.com> #295Apr 15, 2019 11:12AM

Actually, you want to help?

Make people vote here for the issue:

http://en.miui.com/forum.php?mod=viewthread&tid=5370182&highlight=mi%2Ba2

and just an obs. (as i had forgotten about this one too):
"Not just micron, i have hynix emmc. I also face this issue."

Again, let's not rush conclusions. Confirm that your issue occurs THERE. We need xiaomi devs to start checking, not google.

ja...@gmail.com <ja...@gmail.com> #296Apr 15, 2019 01:13PM

The slow cache clearing is indeed a software issue , as I said even my replaced unit have slow cache issue . It gradually went slower in each pie update. In Oreo it was really quick. Now new phone have Samsung emmc ,lot of people said Samsung is fine. But it takes a few seconds to clear large cache on my phone. Only difference is phone doesn't freeze and restart. I haven't had a single force restart on my new phone. So slow cache issue can be categorised as software issue. I had requested fellow users in a Mi A2 WhatsApp group to share their androbench scores. And what I noticed is people only facing slow cache issue have Random write speed more than 12MB/s on March security patch. And those who had both slow cache and phone freezing got around 5-8MB/s . And I had Hynix emmc on old A2 , I used to get 6.93 MB/s on it. So there's likely 2 type of issues . 1 software issue and 1 hardware issue . May be both are software issue. How long are you willing to wait for finding out ? But I suggest those who also face freezing get your phone replaced if you have warranty and service center accessible to you. Most of the people who face this issue have bought device early at time of launch and soon their warranty will expire , finding out it was a hardware issue all along will not be a good news to hear after warranty is expired.

ri...@gmail.com <ri...@gmail.com> #297Apr 15, 2019 01:35PM

Imo i don't think that these issues are different. Cache is located in data/data meaning emmc. From what I have checked source code, settings will only call clean cache low layers and wait for response. Sending the command directly to package manager also froze the device when cleaning cache (adb shell pm clear package). After cleaning the big caches, my phone did not force a reboot but slowed down considerably.
The reason why i believe is located in lower layers and that is the same issue, imagine that all the threads/process running on kernel/android layers... sandboxed and being able to be killed by android if there is no UI response. Well... the problema is that... i don't see the UI trying to kill anything while cleaning cache, unless you try to move to another app and settings doesn't respond... so i believe that it is bottlenecked in memory (specially because of the benchmark ppl ran... and checked the read write speed... not that it can be used as a absolute parameter, but we can have some "traces" of where the issue could be).
Also let's consider that, although we are saying "cleaning cache", emmc won't delete (write) stuff from memory as writing will degrade the memory lifespan... so i think (if anyone works on memory team/emmcs etc, please confirm the procedure) that the memory will only allocate the blocks as "unused" but i don't think that they will literally clean those blocks, unless you actually use it. But this is my guess from previous issues i have seen before.

But i agree with you... if your warranty is not expired, take it to a service center. There is a high chance that this issue could be fixed (although it could be located in emmc) but i would not guarantee that this will be fixed at all... but again, xiaomi seems to work differently from other OEMs i know... so they might actually try to fix it... at least this is my feeling after seeing how xiaomi work with updates (very different rules/process that i was used to...)

Also, depending how much it affects users, they could be forced to do something, for example:

https://www.androidcentral.com/nexus-6p-owners-eligible-400-huawei-and-google-class-action-settlement

ja...@gmail.com <ja...@gmail.com> #298Apr 15, 2019 02:08PM

I don't know bro , but my new phone doesn't have freezing issue anymore . I can continue to use my phone while clearing the cache . In old device if I try to do that it's guranteed to restart( yes if I leave the phone after pressing clear cache and leave it be ,it won't restart , it only force restarted only if I try to switch to another app. But if I try to every single time it force restarted . New phone doesn't . It might very well be a software issue . But I disagree with the fact xiaomi may try to fix it . If they would've , it would've been fixed long back. I have been reporting this issue to xiaomi via feedback app long before this issue tracker thread was created. At the time when I searched Mi A2 on Google I found blogs and websites reporting this emmc issue , I was glad to know I want the only one facing it . 2 days after when I searched Google Mi A2 what I found was Mi 2 getting a price cut. All the headlines were regarding the price cut . They buried the emmc issue from public. Even now if we Google Mi A2 only headlines we can find are about the never ending price cuts of A2 . I really wish I had bought Nokia devices. They gives proper explanation and details regarding bug fixes and update schedules to their users even acknowledges the bugs on devices and offer info on when they will fix it. They even gave camera 2 API to users after request . Now they take better photos even though A2 has better camera . They gave face id on their Android one devices while xiaomeme keeps telling Android one doesn't get it. Nokia update camera features across all their devices. Mi A1 is stuck with the camera app it was launched with . Yeah nearly 2 years in and it still have the same camera UI as MIUI 8. Don't get me wrong Mi A2 is still the perfect device for me , perfect form factor ,perfect cameras sleek design . But software experience and bugs ruin it and I will never buy another xiaomi device ever again .

wh...@gmail.com <wh...@gmail.com> #299Apr 15, 2019 02:37PM

If it looks like a duck, swims like a duck, quacks like a duck, it's probably a duck.
I'm calling it a duck but of course each to their own.
You might be right, it might actually be a mutated swan, but it's probably a duck.

ri...@gmail.com <ri...@gmail.com> #300Apr 15, 2019 02:42PM

Nah... is not the time... really...
I will give you an example... let's say that a batch of micron memory had an issue... and were used in production for mi a2. Until the issue was discovered, the units were sold... then they discovered that the memory had that issue and needs to fix it... but the fix is in emmc firmware.
Well the thing is... how does this work inside the OEM... (i believe that this is also for xiaomi...) the OEM does not have the source code, they need to request to micron to fix this asap, but xiaomi won't stop selling those (specially if they are not a exploding unit like samsung note). So now the issue was passed to micron... what micron can do? well... if the issue is hardware only... they will make a new batch and we will never see a fix. If the issue is in their firmware, we might take some time and see a fix... but remember that... when the oem develops the phone, it is not ... a phone yet... it's more like a circuit board with a panel etc... the bsp team (board support package) will start to work checking each park and make stuff work... they will run months of tests to check performance. So change a firmware could lead to new tests (aka more money), so it must worth the fix...
Let's say the issue can be fixed in kernel... same thing but this is xiaomi responsibility, they can fix on their own, which means it should be released a fix fast... if we don't have a fix yet, probably the issue is not here. If this issue is caused by google, xiaomi would need to open an issue in google and wait for a patch... but i'm not seeing other phones having this issue...
So let's say that the issue is hardware... xiaomi cannot do anything... well to fix it... and they won't say "hey we have a hardware issue recall". So what can they do? Probably change kernel parameters to mitigate the problem. This won't fix, but it could make the read write faster... like "caching" more... example:

https://developer.ridgerun.com/wiki/index.php/Linux_Performance_and_Tuning_Tricks

https://cromwell-intl.com/open-source/performance-tuning/disks.html

again... it is not a fix, but more like... improvements to make it less shitty... imo... it is very hard to do this after the phone is produced and tested... specially because you need to check performance and other issues that can occur... but, as i said before, xiaomi works differently with update team, so i cannot say how they work internally with other teams also.

About nokia device... camera 2 api unlocks some features, yes xiaomi could have managed to do this and test... i don't know why they didn't release it with the camera 2 enabled. But now... changing to camera 2 api will demand tests... because the android can check for those properties and run different codes, enabling it would be done on the first releases. Next updates would need to be tested to see if it would not affect other functionalities... (remember that one thing that is xiaomi, even being android one... is the camera). So if xiaomi releases camera 2 api enabled, it is totally because the users requested and not because their camera actually needs the features.

The faceid, imo, is not important, since it is not secure. it is more gimmicky, but maybe because of the faceid is that they needed to enable camera 2 api. Who knows...

True... i was also expecting updates in camera app... specially with the low light sensor... it has "white pixel noise" when dark... they could do a better algorithm for noise reduction and many other features... but yeah... that's the camera team...

But the reason i bought xiaomi is because of its price:

https://www.amazon.com/Nokia-7-1-Unlocked-Smartphone-T-Mobile/dp/B07HD2X91Q/ref=sr_1_7?keywords=android+one&qid=1555339217&s=gateway&sr=8-7

https://www.amazon.com/Xiaomi-64GB-Camera-AndroidOne-Smartphone/dp/B07FMPVBQR/ref=sr_1_13?keywords=android+one&qid=1555339217&s=gateway&sr=8-13

But yeah... nokia seems to be better than mi a2...

ri...@gmail.com <ri...@gmail.com> #301Apr 15, 2019 02:48PM

@299
I totally agree with you man... i would also bet that this is hw... but...

wh...@gmail.com <wh...@gmail.com> #302Apr 15, 2019 02:57PM

#294 is bad advice, just report what issues you have. #296 is actually pretty close to what i think is the actual issue. The slow cache clearing is a side effect of codes that they introduced to workaround a batch of faulty hardware. If you have issues exactly as described by the OP. You probably have a duck.

ja...@gmail.com <ja...@gmail.com> #303Apr 18, 2019 08:35AM

#300 1. It wasn't just micron , i had hynix memory. So issue may not be readily with emmc chip but it's interfacing with the mi a2 main board. almost all devices bought around launch to September or even October faces freezing issue along with slow cache clearing. that can't be a coincidence . I mean on my old unit i had both slow cache and freezing in both oreo and pie the same . according to some xda forums slow cache clearing is a result of xiaomi trying something to make internal memory faster. xiaomi has added some lines of codes, that causes the slow cache issue and low random write speeds and by removing them from kernel, issue is solved and random write speeds are back to normal. as i said earlier its over pie updates i started facing slow cache issues and that too isn't severe and hasn't , so it can be fixed by xiaomi if they intend to fix it .I also asked around with people recently bought the device and the ones who got replacement , they all have same experience as me as in slow cache issue comes after updating to pie . and if it indeed is a hardware issue then they should be able to publicly anounce their certain batch of devices are faulty and are to be recalled , because customers actually paid for those devices , we didn't get those for free. and mi a2 isn't a really cheap device , it is now but when i bought it ,it was arounf rs.17499(about $250) now its rs.11999
(about $170) . they always speak highly of their commitment to customers . is this the kind of commitment they were talking about, release a phone without proper testing and not fix any issues . talk about poco f1 screen bleeding issues , they didn't respond to that issue until mainstream bloggers and medias started reporting it. they responded they're aware of issues and is offering screen replacement to affected users at service centers only after it became a news and they were aware of it and only chose to acknowledge it after news broke out. it happened only because poco has been sold in more numbers . i have seen various oems recalling or offering fixes for their faulty devices. at least they have the bones to admit when their devices have some issue if it is as widespread like this emmc bug in A2. nokia recently admitted about device activation data being sent to some china servers from certain batch of Nokia 7 plus and quickly rolled out a fix. It is shameful to xiaomi that e new company such as hmd is giving better customer support for their products.

2. i said about face id because it was added by request from users as well as the camera 2 api . it shows how much they listen to their customers. and i don't understand why enabling camera 2 api demand tests as it is something that's part of android os since lollipop . they have disabled something that was already there it by removing codes that accesses the API. i mean adding 3-4 lines of code in build prop enables this , that 3-4 codes is not the camera 2 api, these api are already available in our roms , they just have disabled the codes that accesses these api . people who have rooted and enabled camera 2 api are using it effortlessly and doesn't have adverse effect on system, yes i was also under the thought they might be working on a way to enabling camera 2 api without affecting the working of stock camera ,but people are using gcam and stock cam together without any issues at all . in their miui system disabling camera 2 api can be justified as , with or without it they will get latest camera features through miui upgrade. but in the case of android one users as mi a1 and a2 we are stuck with what we got at launch and is forbidden to use other 3rd party apps which offer better features by disabling the api those apps demand. that is just outrageous on any perspective.

Again i'm telling you if it's just slow cache clearing wait for a fix or live with it. if there is also the freezing issue ,better get the replacement from xiaomi before it's too late.

je...@gmail.com <je...@gmail.com> #304Apr 18, 2019 04:25PM

Guys, please report this on the "Feedback" app of XIAOMI, let's make noise, I already send my bug report, You have to keep them aware of the problem.

wh...@gmail.com <wh...@gmail.com> #305Apr 18, 2019 04:49PM

Isn't it like super duper obvious that they already know about the problem but can't be bothered to fix it?

ri...@gmail.com <ri...@gmail.com> #306Apr 18, 2019 04:57PM

Actually 304 is right... Although they know about the problem, this is not prioritized... The only way they can give a higher priority is by having more field issues reported. Obviously the dev team already know about the issue and also it was probably already discussed internally... The devs will only discuss about this issue again if things start getting hot (users reports). I am pretty sure that mi a2 inside xiaomi is a "legacy project" already... Specially because of mi a3 that is likely to be released. Mi a2 will only have more focus when the android Q update start to be developed inside xiaomi... Again, this is what i know from internal process inside an OEM... Doesn't mean xiaomi follow this but I'm pretty sure it's the same...

g....@gmail.com <g....@gmail.com> #307Apr 18, 2019 05:50PM

Hi I sent the feedback as it was suggested by users above. I also linked this page into the description and I think it could be useful if anyone does the same.

an...@gmail.com <an...@gmail.com> #308Apr 19, 2019 04:05AM

Well after april issue , the cache issue still persists. Not sure on what basis the service center told me that it will fixed on next update. Heading to service center again.

sr...@gmail.com <sr...@gmail.com> #309Apr 22, 2019 08:03PM

I have the same

issue 4

/64 version. Please for God sake release an bug fix soon.

gp...@hotmail.com <gp...@hotmail.com> #310Apr 22, 2019 11:01PM

@308 Please, do keep us informed.

wh...@gmail.com <wh...@gmail.com> #311Apr 23, 2019 12:38PM

Moral of the story is Xiaomi is not worth buying at all.

No Double Tap to Wake
No Camera Api 2
No HDCP for Netflix
No Warranty
No Support
No Aftersales

wh...@gmail.com <wh...@gmail.com> #312Apr 23, 2019 03:07PM

Not to mention shitloads of problems.
Random freezing, apps not responding
Slow cache take a few minutes to clear cache
Cpu getting stuck at certain state while the phone is idling. Huge battery drain.

or...@gmail.com <or...@gmail.com> #313Apr 24, 2019 07:44AM

I have 2 of these Mi A2 crappy phones. Before this I had 2 of the Mi A1 which worked brilliantly. Gave the A1s to my kids. Now I encounter lots of freezes and waits. BTW: I am updated to the latest updates.

Actually just posting so I can follow any developments.

wh...@gmail.com <wh...@gmail.com> #314Apr 24, 2019 08:11AM

sadly there is no development to speak of. Nil, zero, zilch

al...@gmail.com <al...@gmail.com> #315Apr 25, 2019 12:03PM

...and still no fix....

ri...@gmail.com <ri...@gmail.com> #316Apr 25, 2019 12:32PM

@311

No Double Tap to Wake - the chipset allows this but they are just not willing to implement... i guess they are right... double tap was good when fingerprint was not available all around... but now... even mid tier has fingerprint scanner...

No Camera Api 2 - this is probably a choice of tier... since they are not providing a great camera... they probably think it is not useful to allow things that are probably unusable or that might demand implementation (even if it's just a return 0 case)... i believe that this will start being released in mid tiers phone when the camera quality start to become cheaper (like it has been recently... allowing mid tiers camera with 13MP 1.8f etc... which were a high/premmy tier 2 or 3 years back...) So this will likely make them improve software and probably starting to release more manual controls (since AI is being such a great deal for cameras)

No HDCP for Netflix - this is xiaomi being cheap... even in poco they had issues by not having widevine implemented or provisioned... i don't know why they don't implement... but yeah... that's entirely their fault, but i see that they are already updating for some phones like poco...

No Warranty
No Aftersales - this 2 i agree... it's not that they don't have any... is just that they focus on selling more... providing customer support demands money... and phone makers doesn't want this kind of trouble... once it's sold... they don't care at all (not only xiaomi)... for example... first SW were developed by the main team (like mi a2 devs... that were focused on mi a2 project)... after it was released, probably there is a legacy model team that probably works with mi a1 mi a2 and mi a2 lite... and they just forward the issues to the dev team... the dev then releases a patch which will be on the next update... since urgent security patches cannot have bug fix.. they will release as an usual update... this means that they need to run some few tests after applying all the bug fix and the security patches.. this usually takes a few weeks so that is why we receive the updates at the end of the month usually... but if anything goes wrong... they will keep in this cycle (implement - test - fix again - re test) until the project team approves the update... but this is different for a OS upgrade... since the dev team is not allocated anymore to the mi a2... i believe that they forward the updates to third parties companies... which is more like a patch apply and bug fix... any complex implementation will be forward to the original dev team... So that's why we have low attention... we are banging our heads in a google issue tracker... but this is not a google issue (afaik).
There is probably a link to the internal bug system tracker inside xiaomi but they are not likely to be seeing any changes on this bug... so all the comments are likely being ignored (check that the assignee is not xiaomi internal but google)...

But again i think this could be fixed in the next OS... could... not that it will...

No Support - i partially agree... xiaomi has been very active on their forums... even being able to contact the dev team there... if you compare to samsung... lg... etc... they don't have anyway to be contacted... so i would say that xiaomi cares a little bit more about users opinion... (just a little bit)... but regarding customer support... again... they are not spending money on after sales... once is sold... they won't have any other income... so they just focus on releasing another phone...
Imho... this will only change if people change... instead of buying newer phones, people start recycling them... upgrading the phone... etc... if people start to focus on keeping a phone longer, the income for newer models would not be that high... so they would need to change the strategy to "customer support and repair"...

Anyway is there any other info about the customer supports that you guys were going? Can they inform a way to reach the mi a2 dev team more efficiently?

al...@gmail.com <al...@gmail.com> #317Apr 26, 2019 12:13PM

They changed the miui forum too merging the

en.miui.com to the Chinese one I guess...the thread wich I wrote my feedback in has been put in "read only" and cannot accept replies anymore. If anyone has an idea on how to talk directly with devs.. Please tell us

ja...@gmail.com <ja...@gmail.com> #318Apr 26, 2019 01:54PM

#316 for a serious and severe problem such as this , they are not in a position to make any excuses for this problem being not fixed for over six months ,especially when they charged a hefty price point for a device with such specs. Only Snapdragon 660 device globally available that is expensive than A2 is Nokia 7 Plus and it does have a premium build , Zeis Cameras to make up for it. All other devices with 660 offer better value for money. So the least these AHoles could do is provide good support for these devices . You talk about other OEMs not being able to contact as simple as Xiaomi , there is no particular need to . They don't have much of an issues , even if there are they fix it , they don't give frequent updates for all their phones but the updates it get they fix the bugs unlike Mi A2 here getting updates worth 1GB and not fix a damn thing and introducing more issues . What's the point ? driving the user mad ?? Or decreasing the phone memory ?? In the case of Samsung they do have issues but most of them are hardware related . No other OEM would have ever taken this much time to fix an issue that's widespread as this. It's to be noted this still hasn't been fixed nor they have even acknowledged it. I have seen multiple times Nokia admitting some bugs in their phones and telling when they will fix it and they do. And you thinking they are aware about this issue and not aware it is widespread is a complete folly . They are aware of it this issue is not only discussed in this issuetracker. It is severely discussed in Mi community , xiaomis own platform . And I have been reporting this issue via feedback app since October and a lot of other people that I know of . And the fact that you said not enabling camera 2 API can be justified since they didn't provide great cameras makes me wonder are you stupid or are you Xiaomi insider trying to defend the company(no offense). IMX486 sensor with f1.7 lens isn't good for you ?? The secondary 20MP sensor with pixel binning is said to have 2 micron super pixel also coupled with f1.75 lens . There is no other phones out there that has 2 micron pixel size coupled with a fast f1.75 lens . This phone has the best camera setup in this price range and some devices above its price range. Camera 2 API is must for A2 since the improvement it makes is drastic both day and night. You can google "Mr Phone Google camera comparison A2,OnePlus 6 and Poco F1" to notice the difference. And the important thing to notice here is Camera 2 API is a built in API that's part of android. Xiaomi just has it disabled. Only thing Xiaomi doing is being arrogant , there is a reason for them, that the phone wasn't as successful as they hoped for multiple reasons like high price , no SD card slot , no 3.5 mm Jack and 3000mah battery which is low for today's standard. They made those decision while they designed the phone and fault is theirs only if they didn't make a profit. That didn't give them a right to make customers who out their trust in their brand and bought their phones to suffer like this . Their support is only good if the device was successful I know this from using Redmi note 3 since 2016 and got a great deal of support and I haven't faced major issues .A2 being not successful is not our concern , they have an obligation to customers. They have to keep it no matter what.

ri...@gmail.com <ri...@gmail.com> #319Apr 26, 2019 02:33PM

@318
Nah man... all the OEM has many phones with horrible issues... trust me... i know...

I know that xiaomi should have fixed this issue earlier... but the process that works inside the corp is not as "logical" as it should be. Specially considering user reported issues.

When the user reports an issue in a service center, it just add another number... like X battery fail, Y camera fail, Z cache fail, etc...
The service center has the directive from the OEM to do the procedures for certain issues like... "if battery is bad, change battery and return the same phone... if the phone was purchased less than a month (an example) give a new phone to the user".

Then the local OEM office (usually is customer relation and customer service... merchandise... etc) will gather this numbers and inform to the HQ... then the HQ will inform the devs IF the issues gets problematic... like let's say most of the devices showing a problem occurs during the one month, making the customer services give a new phone. Let's say it's a carrier phone like... hmm AT&T... so AT&T will report this to the OEM, meaning less profit.

So the OEM will only start to move when this case occurs... let's say the issue occurs but there is no repair involved... just maybe a small factory reset... this will count too but less than giving a new phone. So if the number of reports is too low (or should i say... as expected...) the OEM will also not move.

But let's say that the OEM know about an issue that can be fixed in SW side... but this change might be too risky and probably will need tests... what do they do? Well... they will check how severe is the issue... does it affect the overall performance or it only affects a few users that do a certain action (like cleaning the cache of an app)... Depending the severity... this issue is likely to not be fixed at all... and will be closed as "improvement" and "will be fixed in next release" (which can be android or any other release)...

My point is... it doesn't matter how much you pay for the phone or which OEM... they don't work for after sales... (and i'm not guessing this...) Their focus is always to sell more phones... it doesn't matter that you say "xiaomi never again"... people nowadays has no memory... want an example? samsung note 7 explosion... samsung s3 sudden death... nexus 6 sudden death... LG G4 sudden death... Apple iphone 4 antenna design issue...

The only way to attract focus to this issue is more people going to authorised service center... report the same issue and make number...

And no... i'm not stupid neither xiaomi insider... i just know how it works... so you can complain as much as you want here to me... but again... everyone here has a mi A2 and is suffering from the same issue as you...

Regarding the camera... you described the hw... but you have to remember that it doesn't matter the hw if the sw is not well implemented... HW team and SW teams are separated one (usually camera is a whole team from HW to SW including app)... But for an example... Pixel cameras with same sensors as other phones has better SW treatment, meaning better photos... Another example GCAM port in mi devices can get sharper and less noise images... so just spitting the HW specs like it would make a difference will not change the fact that a lower tier phone model will have less attention than higher tiers... EVEN if the HW ALLOWS...

So instead of trying to argue against another user... understand that i am only describing how it works and how we can reach xiaomi more efficiently... if you don't accept how it works that is your problem, but it won't change the fact how it is. We all know how it sucks to have paid for a phone that has an issue and that they should be fixing... but again... arguing what it should be and what it is won't make our phone fixed... so like me... try to reach the xiaomi mi a2 dev team... send them emails... ask for info how to reach them...

ja...@gmail.com <ja...@gmail.com> #320Apr 27, 2019 04:06AM

#318 did you read what you typed ?? You literally said they might think camera 2 API isn't really necessary because you think they're not providing great camera . Now you're saying what I said in my comment. You said A2 didn't had good camera and it might not be worth effort to enable camera 2 API first and now you're saying this . I don't know what to think now. You sound ridiculous really, how is that any different from what I said about the may. Only you still sound like A2 don't deserve what it rightfully should've had always CAMERA 2 API and A2 is not lower tier one. It's actually upper mid tier phone.

I agree I don't know much about their internal working and all . I know I got better support for my Redmi note 3 which had their own MIUI and provided changelogs with every update and what's fixed and what's broken . And I have been trying all accessible ways to contact dev team like emails , live chat support ,Mi community ,feedback everything even Xiaomi official pages and official personels Instagram handles ,all options I've tried and keeps doing the same. May be more than anyone . Smartphones are supposed to make lives easier . I have never been stressed out by a phone as much as with this one. I didn't had Camera 2 API on Redmi note 3 but at that time it pretty much provided was manual control and some ported MIUI camera app worked just fine. Today time is didn't camera 2 API is really significant feature now . And I'm a person who use web browsing a lot . My Chrome browser gets filled with over/under 500 MB in a days usage and it's a great deal for me to able to clear the cache fast . That's not so much to ask . Even 50 dollar phones clear cache 800MB+ in less than 2 seconds. Slow cache issue is fixed with custom roms why can't a company large as Xiaomi fix this issue. All those issues you mentioned are hardware fault and most of them were acknowledged by the companies. A2 motherboard dies that's a problem genuinely can happen for multiple reasons . While a problem of this magnitude and scale isn't . I can confidently say more than 50 % of A2 users are facing this issue across the world. It also affects whole stability of the device too . I'm glad I got the replacement and I no longer facing freezing issue. There are others who haven't got their issue fixed. I keep saying the importance of this issue to be fixed ASAP and you keep saying they probably should and it's also justified why they aren't doing it. Maybe you got the device for cheap or you have another phone with good specs . So you don't care if it gets fixed or not . There are other people here who gets annoyed by this issue and wants an immediate fix, people who saved up money to buy it . Only word for what's Xiaomi doing now about this issue is FRAUD.

ri...@gmail.com <ri...@gmail.com> #321Apr 27, 2019 12:29PM

@320 dude i know how you feel... I bought mi a1 and paid for it during a whole year... I had to give it to my parents cause their mobile was shitty and then i decided to pay another year for this mi a2... Again... We are here because we are suffering the same issues that you have...

About the camera... I will tell what happens (probably in xiaomi too)... Camera team is usually separated from the rest of the teams (hw bsp app) because that's one of the main concern for a future device and camera is what i could say "the cherry on top of everything"... The camera team focus basically on developing a better camera for future models and also make it more affordable for cheaper devices... So instead of creating newer solutions... They basically copy from a better one and make it cheaper... That's why we have legacy camera api while newer ones are being released with camera 2 enabled... If there is a big request from customers, they can enable it IF the properties doesn't affect the sw stability in general. Again it has nothing to do with hw... They just won't touch anything that is already working... But imo as a dev... Improvements should be made if requested and if it could reach better performance... So understand that there is a difference between developers pov and business pov... As a dev we can ask for changes and inform the benefits, but money will say if anyone should be or not allocated for these stuff... This is how any OEM and corp works...

Mi a2 is mid low dude.. you usually can tell by the price is being offered... That's not my opinion about the phone... Is just how mirroring with the one's i know... Fits the price range... This also means less tests and cheaper components... But it doesn't mean it will or won't fail... Check premium tier devices that had issues like note 7...

About fraud... It's not fraud but they are hurting the customer... What i can say is that most OEM knows about an issue but won't do anything to fix until it starts to hurt their own pocket... As a dev i totally disagree with this... But this is how it works... If they already sold the device and they don't need to exchange it... Then nothing to be done... Again... I disagree but i understand the way they work... So that's why i am saying that we should go to customer support as much as we can....

tr...@gmail.com <tr...@gmail.com> #322Apr 27, 2019 04:26PM

My phone keeps freezing. And when transferring files from my computer it just crashes!

ph...@gmail.com <ph...@gmail.com> #323Apr 28, 2019 05:22PM

my phone freezing while delete Google chrome cache

sa...@gmail.com <sa...@gmail.com> #324Apr 28, 2019 05:28PM

My Xiaomi Mi A2 with Android 9 (V10.0.8.0.PDIMIXM) freezes or runs slowly when you clear apps cache or when moving a file of more than 300mb

fo...@gmail.com <fo...@gmail.com> #325Apr 28, 2019 06:16PM

Even with the newest April update the phone still freezes when removing the Chrome cache.

This is a software bug with the Micron emmc chip.

If i put the Miui 10 software of the Mi6Pro on it,the problem is fixed.
No lags or freezes.
So it is a driver of configuration bug in the Android One build.

Please fix this very annoying bug in this great ohone

an...@gmail.com <an...@gmail.com> #326Apr 29, 2019 11:23AM

So the service center came back to me saying that, their technical team from Mi have analysed the logs of the issue and they say that it is common that clearing cache would take some time and is expected.
I have reverted to them asking, how come a 3 year old phone(redmi note 3) performs better in this aspect than the newest and how come the 6/128 does not have this with the same firmware?
The service center have said they will revert back with an answer in 2 days.

ri...@gmail.com <ri...@gmail.com> #327Apr 29, 2019 12:34PM

@325
i don't think it's the android one.... when you change to miui10 you change the boot partition? if so.. you are possibly changing the kernel img (zImage) which means if this is a custom kernel there could be different approaches to reading and writing... but if you feel that there is no more bug... the solution could be in kernel really... so that would give us a little bit more hope... "it can be fixed"

@326
When you say tech team analysed the logs you mean xiaomi devs? As far as i know service center does not have people who can analyse the log (i'm not saying they are dumb... but you can only understand what it is being called and what is the normal flow if you have the SOURCE CODE)... So just because they read that android is waiting for the task to finish doesn't mean that it is ok... the approach BSP/HW team would have in these kind of issues is "ok... is this an issue? since when? compare with a model with the same specs and check the time" (since this is an easy issue to reproduce.. they can perform this many times to compare...).
Also the cache cleaning CAN be slow... but it shouldn't hold/freeze the UI... this is a noticeable bottleneck... and since even deleting apks are slow... (but not as much as deleting the cache) it can be something being done during the cache cleaning or during the memory read/write...
But way to go man... we appreciate your efforts for bringing us info.

ja...@gmail.com <ja...@gmail.com> #328Apr 29, 2019 05:39PM

#327 cleaning cache can be slow is only valid for may be phones from last decade or unless you're using Mi A2 4GB/64GB, also only other device ever to have reported having this same issue is Nokia 7 Plus . So clearly it has something to do with Android One. Also I only saw one user reporting it in some forum and no others have backed that user and the issue was listed in Google issue tracker too. But that seemed to be an isolated issue. Three affected Nokia 7 plus was also of 4GB/64GB config. Also my friend have this Micromax canvas A1 a phone that was released in 2014 costed less than $100 , the first of android one smartphones with a very low end spec like 1Gigs of RAM and 4Gigs of internal ,it can clear 300+ MB cache in over/under 1 second. So basically no , clearing cache cannot be slow ,not in this era . Also there's a YouTube video showing Mi A2 clearing cache on stock and then on converted Mi A2- 6X, 6x clears cache instantly when clear cache is pressed .And yes service centre guys can collect the device logs , everytime our device encounters a bug or crashing ,it's logs are by default created and stored. It can be accessed from service centers. Just they send it to technical team and it's them who analyses the issue. My device also went through same procedure as #326. It took about 12 days for getting the replacement after I submitted my phone in service centre.
You all will be disappointed after finding out what happened to Nokia 7 Plus emmc bug issue tracker thread. Check it out below

https://issuetracker.google.com/issues/119763086

ri...@gmail.com <ri...@gmail.com> #329Apr 29, 2019 06:17PM

@328
Yeah i agree that cache clean should be fast... even for GB of cache... but it can hang for a couple of ms depending the size... but not like on mi A2...

So about the 2 points you raised... yes customer service is actually instructed to collect logs if the issue is occurring... they submit those logs to a bug tracker (inside OEM). It depends on what the service center was instructed... For example... issues on android apps and other general bugs, they will collect the logcat... devs can also request small details depending the issue (for example... if a unit has a screen flicker, it can be instructed to exchange with a model with an ok screen and check if the issue is actually the screen or motherboard... this helps to focus the issue better and label it correctly), but for logs... mostly logcat, tombstones, crash reports, screenshots are sent to dev team. The dev team can be either the original model team or just bug fix around the world... (usually will be india or china for most OEMs).

About the Nokia... not really disappointed... but more like "expected"... Google release the AOSP and for every model it will need a porting.
So for mi a2 for example... there will be a part that it's entirely xiaomi and a part that is like xiaomi + google and a part that's only google...
Xiaomi part will be basically related to pre kernel, kernel and specific device hardware, like camera, drivers etc... google only has from boot to android framework itself + google specific apps.

If people are saying that miui10 does not have this issue... then it's pretty likely that we would have the same reply from google...
What we would need to separate is... is this android or kernel or hardware? If the service says "xiaomi will make a fix" it's possibly located on kernel... (even if it's a hardware issue... they would try to make a workaround)... if this is a hardware issue and starts to affect too much (like in a few years or months phones starts to sudden death)... then xiaomi will instruct service center to exchange for a new device (possibly... if they acknowledge the issue)... if this is android... xiaomi will not fix it... but it would be fixed on the next android...

But then.. with this issue that you brought... i am more convinced that we should take find a better place to report the bug... xiaomi community just merged miui's one... and i don't know where there is a "bug" section...

wh...@gmail.com <wh...@gmail.com> #330Apr 30, 2019 07:02PM

Stop trying to defend the mi a2. Sounds like total bullshit to my ears.

wh...@gmail.com <wh...@gmail.com> #331Apr 30, 2019 07:06PM

You are insulting the intelligence of every single one here

ri...@gmail.com <ri...@gmail.com> #332Apr 30, 2019 07:07PM

I am not actually defending xiaomi, just stating information...

But i guess ignorance is a blessing...

ko...@gmail.com <ko...@gmail.com> #333Apr 30, 2019 07:27PM

I don't wanna get into your couple fight, but I will just drop a comment.
#331
No bro, you are dumb. That guy is actually right about the developing process, you can see an old version of this here:

https://www.phonearena.com/news/HTC-makes-an-infographic-to-detail-the-Android-update-process_id50719#image-103758

#332
Even if I agree with the process, I still think Xiaomi is to blame here. They made this shitty hardware or, at least, has the same "footprints" as a hardware issue.
I believe that people who has the device should go to customer service to exchange for a new one. I don't see where Xiaomi could actually fix this shit.

ri...@gmail.com <ri...@gmail.com> #334Apr 30, 2019 07:38PM

@333
I agree with you... if you can contact a customer service and it still has and warranty... go for it... waiting for xiaomi to fix is very likely to happen...

About that process that HTC release... on step 6,7,10... that's exactly where the problems occurs (at least for us). The issue was not considered a critical (even here, you can check the priority/severity)... So xiaomi just didn't actually worry about it... and will not worry unless the issue start to get considered critical...

wh...@gmail.com <wh...@gmail.com> #335May 1, 2019 01:18PM

#333 why are you calling names?

my...@gmail.com <my...@gmail.com> #336May 1, 2019 01:29PM

Actually everyone knows that no one is working on any fix.
I guess he feels smarter by calling names.

py...@gmail.com <py...@gmail.com> #337May 1, 2019 01:35PM

Sorry to Hijack this thread, but there some some knowledgeable people in here from what I've been reading over the last few weeks I was subscribed.

I have the Mi A2 6/128 version and after the latest April update, I'm getting high CPU usage measured by CPU Z which is badly affecting my battery life. Battery life and SOT dropped to half if not less. I tried disabling fingerprint sensor but didn't work. Restarted and shut off too, didn't work. This only happened once or twice before but fixed itself. I have the FPS or FPR fingerprint sensor, not the other one that is known for that bug. Although I read that both can have it.

Any solution please? Suggestions? Thanks and again, apologies for hijacking the thread.

wh...@gmail.com <wh...@gmail.com> #338May 1, 2019 01:47PM

It's one of the many bugs that's been plaguing Mi A2 since launch. From launch till now, no known software fix. You can restart and pray that it doesn't come back so soon. But eventually it'll be back.

py...@gmail.com <py...@gmail.com> #339May 1, 2019 01:50PM

That's what I've been doing. Lots or restarting minus the praying side, which I'll add.

Do you think a factory reset would solve it? Or don't bother?

wh...@gmail.com <wh...@gmail.com> #340May 1, 2019 02:02PM

I've tried resetting before. it'll come back. If you can send it to a service center. Their service center are mostly a joke thou. The one that took my phone in just reset the phone and pretend it's fixed.

py...@gmail.com <py...@gmail.com> #341May 1, 2019 02:05PM

No service center in the US. I took a risk I was willing to take when I dumped the iPhone brand and jumped to Android. All I wanted was a phone with stock Android and good battery life. And while Mi A2 isn't known for it's superior battery life, it's been more than enough for me with 30-36 hours with 5 hours screen time (no gaming though)

wh...@gmail.com <wh...@gmail.com> #342May 1, 2019 02:07PM

Probably a class action suit would get it fixed.

ri...@gmail.com <ri...@gmail.com> #343May 1, 2019 02:08PM

From what i have seen back then... This issue was already fixed for some but there were others still reporting a high freq.
Make sure that what's holding your CPU... also check for apps wakelock... (I think there's an app to check if anyone is holding ur phone)...
Factory reset could work if you have anything that could affect the CPU usage... But as far as i remember... CPU usage will be set according to internal parameters and possible "tweaks" that xiaomi would make to "trick" the end user to believe that it has a high rate on benchmarks... If they implemented poorly, there could be some issues there... I will check the forums for more info about how they have checked this issue

wh...@gmail.com <wh...@gmail.com> #344May 1, 2019 02:11PM

No more xiaomi phone for me personally. This is a nightmare which i didn't sign up for.

py...@gmail.com <py...@gmail.com> #345May 1, 2019 02:12PM

#343 thank you. Well I know it's not just numbers because my battery is suffering badly. That's when I checked the CPU actually just to confirm it. Which forums do you recommend?

#342 I would love a class action suit even if I'm not affected by the cache issue. I remember when NVIDIA sold me the GTX 970 marketed as 4 gb while it was 3.5 gb plus 500 mb of slow ram. Got their asses sued and received $30 after a year or two, lol. But they got pinched for it.

ri...@gmail.com <ri...@gmail.com> #346May 1, 2019 02:14PM

Don't worry... I will be checking here and report to you in a few minutes
(maybe hours...)

On Wed, May 1, 2019, 11:12 <buganizer-system@google.com> wrote:

- Show quoted text -

ri...@gmail.com <ri...@gmail.com> #347May 1, 2019 02:16PM

Oh just one question thou... By high cpu usage you mean they are stuck in the max freq both the small cores and big cores?

my...@gmail.com <my...@gmail.com> #348May 1, 2019 02:16PM

#345 don't follow him on his wild goose chase. It a rabbit hole.

py...@gmail.com <py...@gmail.com> #349May 1, 2019 02:21PM

#347 They're not stuck, but they all fluctuate at high frequencies. the last 4 are usually higher (2200 or 1800) the first 4 are 1400-1700, with a split second 633 every now and then. but when the phone was fine, I would get 633 for the first 4 constant, and 1100 for the last 4 constant with some ups to 1400 for split second, ALL that while idle of course

ri...@gmail.com <ri...@gmail.com> #350May 1, 2019 02:29PM

I'm pretty sure the fingerprint issue maxed the core freq. Try one thing... Turn on airplane mode, reboot the phone, keep the airplane mode on and check the cpu.. from what you have said this would still keep the cpu freq high right? Could you check that?

my...@gmail.com <my...@gmail.com> #351May 1, 2019 02:36PM

They do not always max the frequency. And i don't think anyone can confirm it's actually the fingerprint sensor. What happens on mine is it doesn't return to base frequency, my small core gets stuck at 1401. Some people get max frequency. All kind of bugs but the end result is the already short battery life getting even shorter.

py...@gmail.com <py...@gmail.com> #352May 1, 2019 02:43PM

@ #350 I powered off AND restarted the phone while it's on airplane mode. First 4 cores are stuck on 1800, second 4 fluctuate between 1100 and 2200

wh...@gmail.com <wh...@gmail.com> #353May 1, 2019 02:45PM

Basically it's a freakshow of what can go wrong with a phone.

py...@gmail.com <py...@gmail.com> #354May 1, 2019 03:14PM

@ #350 again,
My bad, I kept it for a while and now the cpu is back to normal (in airplane mode). first 4 cores are 633 with splitsecond spikes and 2nd 4 cores are 1100 with splitsecond spikes.

ri...@gmail.com <ri...@gmail.com> #355May 1, 2019 03:30PM

@353
True story...

@352 @351
Some are really having issues with only the single cores:

http://en.miui.com/thread-3625494-1-1.html

I think it might not be related to fingerprint anymore... but like that guy on the tread said:

"We have reproduced the issue and reported to Qualcomm. Qualcomm is working on it."

This is bad... there are 2 possibilities:
- xiaomi devs are being lazy and just reporting to QCT for the fix, when they could have done it by changing parameters
- the issue is located inside QCT part... which means... xiaomi cannot see the source code for further analysis

Usually it takes weeks/months until a fix is released... actually the fix is released fast by QCT and they say "ok we have a fix on this kernel version... but the release on the official build will take X time... if this is a critical issue, you should consider using this fix and applying on your code"

Then mi A2 team will decide... update kernel or just apply some patches... usually OEM would only apply because updating the whole kernel is very risky... I think maybe getting the logs from the boot until around 15 minutes of the single core stuck might be useful for them... but again... many ppl are also having this issue...

I agree with @348... even if you are able to point out the issue location like:

"Details of this issue:Requeriments:
Have a Goodix fingerprint sensor (You can use phone *#*#6484#*#* to see what sensor you have)
Use fingerprint to unlock smartform (If you turn on screen with power button and then use FP to unlock, issue not occurs; but if you with black screen use FP to turn on screen and unlock, then issue ocurrs). Obviously, if you don't use FP, you haven't issue.

Consequences:
Modify value of files: /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq, ...., /sys/devices/system/cpu/cpu7/cpufreq/scaling_min_freq
In theses files, the value is put to max
Then frequency of all cpus run at max
Then battery drain

Xiaomi, need you more details?"

This will still demand an update from xiaomi... but the thread is still running... so maybe xiaomi will make another fix (for the small cores now)

ri...@gmail.com <ri...@gmail.com> #356May 1, 2019 04:12PM

@354
Yeah man... Not sure if this is good or bad... The modem can be triggering the max CPU or it can be an app... I saw ppl saying that without simcard was not giving them the issue, but again... If there's no app draining the battery by doing some bizarre processing... Then it's likely that this will be a recurrent bug...

ol...@gmail.com <ol...@gmail.com> #357May 2, 2019 06:25AM

4/64 same here

an...@gmail.com <an...@gmail.com> #358May 2, 2019 07:33AM

so the service center gave me another update. They conveyed that, their technical team has said that there is 'No issue' with hardware or the software and that my phone is fine.
However they are ready to replace my motherboard. The service center guy definitely agrees that there is an issue but the technical team at Mi do not.
Since they are ready to replace the motherboard, I am thinking of giving it a go ahead and see what happens.

py...@gmail.com <py...@gmail.com> #359May 2, 2019 12:17PM

@356
Removing the sim is almost like airplane mode, in my understanding which did temporarily fix the issue. It's one of their first, if not the first Android One phones. Many people will just not buy Xiaomi anymore because of the lack of the support. I really like the phone if it wasn't for this issue. Then of course comes the issue you guys are having.

ri...@gmail.com <ri...@gmail.com> #360May 2, 2019 01:12PM

@358
man... if they are allowed to replace the motherboard we have a hardware issue... unless xiaomi wants to analyse... but usually the OEM just won't allow hw exchanges just like that easy...
This might be really bad news...
Check if you get a samsung memory... if so... maybe there won't be the issue...

@359
Actually there's a lot of difference regarding the sim not present and airplane mode. Having a simcard inserted can start some customization process (usually from OEM), get some MCC and MNC from the simcard... bla bla... Obviously that both will not trigger any data exchange (if we consider to disable wifi, bt, etc)... but we cannot be so sure that the issue is under modem/processor (QCT) or xiaomi made something stupid here... or even some application... (maybe a factory reset would be good to figure it out if it was any third party app installed, but imo... not worth trying, since others are also having this issue, but it's up to you really).
The first was mi A1, which i had before, and it was pretty good... didn't have all the bugs that mi A2 has... but yeah... mid low tier phones are always prone to defects easily because of the lack of testing (which is nothing compared to high premium tiers)

py...@gmail.com <py...@gmail.com> #361May 2, 2019 04:25PM

UPDATE:
I checked the apps using the battery during night time when I wasnt using the phone (asleep), and I found "Cricket Wireless" using the majority of what has been consumed of the battery life. I remember I ran this application few days back, maybe when the issue started? not sure, but I DEFINITELY closed it when I was done. Apparently the app was running in the background even if it was closed, not only running but consuming a lot of power. I still dont think this is the app's fault, it's the system handling the way an app opens and closes. Dunno if this makes sense to the guys who know more about how all of this works.

TLDR; forced an app to stop, cpu usage back to normal, restarted, still ok, but fingerprint still off. I doubt it was related. I will soon enable it and update here

ri...@gmail.com <ri...@gmail.com> #362May 2, 2019 04:50PM

@361

Closing an app doesn't really mean much... the dev can process stuff in background, like "reach the server and update the info" etc... Usually is not a good app design, but it is not impossible.
In theory, the best way for an app to update itself (update its contents) would be, hit the server the first time, get all the content needed (if network is detected - wifi or data) and store it internally. Then only update it when the user re-open the app, but some apps can constantly check the data and update itself in background. Some apps that need this kind of stuff are like... gmail, instagram, facebook etc. Which will get constant info and messages, even if you are not using it (you can check for process running with an app).

Imo, if this app has most of the battery usage, it probably kept the phone awake (the processor kept running), which would be the reason why the device didn't sleep (acquired wakelock bla bla)...

Android has a way to keep/kill process if it needs memory. For example, if you have an app opened, then change to another... it will keep the first app alive, even if it's not visible. If you open a third app and the system feels that it needs memory, it will basically "close" the first app to make room for the third. That's why, specially in mobile reviews when they do a "open app speed test" (imo terrible way to compare anything) when you see the app re-opening the app (and not continuing where it was left) it means Android had to kill it to allow other apps to open.
Obviously this is not decided by Android only... the app developer can make the app running in background (for example, apps that request to leave a notification on). But more easy to explain... imagine a very important app that needs to be running in the background (like a message app) android cannot kill its process and make you stop receiving the messages... (it has to hit the server and fetch the messages from time to time)... therefore Android has some priorities when "cleaning" the stuff...

I would consider testing the phone more and keep checking the if there are any other apps that might be consuming battery (specially facebook and social media apps...) also consider checking the display brightness, as it kills a lot of battery too... oh and one more item... mobile data signal... when the phone is in a hmm "bad region", far from mobile antennas, the signal drops a lot, which means the phone needs to intensify the signal to keep connected... (or if it disconnects, it will keep trying to reconnect...). When the mobile first try to connect to a network, you have a peak of signal (meaning more power)... so staying in a low signal place is very very bad for your battery.

wh...@gmail.com <wh...@gmail.com> #363May 3, 2019 03:37PM

Any lawyers?

wh...@gmail.com <wh...@gmail.com> #364May 3, 2019 03:41PM

The lawsuit alleged that Google, which contracted the design and manufacturing of its early Android smartphones to third-party companies, and Huawei, one of the chosen companies, breached the device warranty since the companies were aware of the issue, but did not respond to the bug. The plaintiffs also said the companies continued selling the faulty devices while failing to acknowledge the issue. If the court approves the settlement at the next hearing on May 9th, Nexus 6P users in the US who purchased the device on or after September 25th, 2015 would be eligible to claim reimbursement.

wh...@gmail.com <wh...@gmail.com> #365May 3, 2019 03:41PM

https://www.theverge.com/2019/4/11/18306552/google-huawei-nexus-6p-class-action-lawsuit-settlement-agreement-compensate

sq...@gmail.com <sq...@gmail.com> #366May 6, 2019 06:04PM

Tried clearing Chrome cache and it worked fine. Not sure what changed. Curious if anyone else has an updates or if they've attempted again?

wh...@gmail.com <wh...@gmail.com> #367May 7, 2019 03:31AM

what's your phone model? how big was the chrome cache? What's your build number? How long did it take to clear the cache?

sq...@gmail.com <sq...@gmail.com> #368May 7, 2019 02:05PM

In reference to #367.

Phone Model: Mi A2
Chrome cache was 500mb
Build number: PKQ1.180904.001.v10.0.8.PDIMIXM
Only took a 30-45 seconds

However, I did spam the clear cache button and the phone eventually restarted itself. I didn't need to spam it, it was clearing cache in the background. So it's still a bit buggy.

wh...@gmail.com <wh...@gmail.com> #369May 7, 2019 04:09PM

Is your phone 64 or 128 gb? i think the main issue is the phone is also unstable. After you use it for some time it'll keep crash frequently.

wh...@gmail.com <wh...@gmail.com> #370May 7, 2019 04:10PM

the slow cache clearing is mostly an annoyance, unless it crashes the phone. which happens like most of the time

wh...@gmail.com <wh...@gmail.com> #371May 7, 2019 04:13PM

try testing your phone emmc. i think if your random write is below 10 you'll probably have a lot of problems down the road. It'll manifest itself as micro stutters and all kinds of crap.

ri...@gmail.com <ri...@gmail.com> #372May 8, 2019 08:33AM

4/64 global same problem

mi...@gmail.com <mi...@gmail.com> #373May 8, 2019 08:23PM

4/64 global version

Got this phone in December and since day one I'm facing a lot of problems with it.

I'm really disappointed on Xiaomi - this device performs poorly compared to other midrangers I have at home (namely the Galaxy A8 2018 and LG G5 SE).

I'm experiencing random lagging/stuttering/freezing/rebooting on the UI and specific apps, such as Chrome, WhatsApp and Gboard.

Sometimes I feel like the whole system is throttling down and the phone pretty much becomes unusable till I restart it.

Androbench (aproximate) scores are:

- 64MB file size:

Sequential Read ~250-280MB/s

Sequential Write ~100-120MB/s *

Random Read 34-39MB/s

Random Write 8-11MB/s

* it may be only a coincidence, but before disabling Chrome and uninstalling Oulook, Sequential Write would score anywhere between 30-70MB/s.

- 512MB/s file size:

Sequential Read 256MB/s**

Sequential Write 29MB/s**

Random Read 35MB/s**

Random Write 7MB/s**

** My phone will crash/reboot during test probably 4 out of 5 times I run it.

deleted

Restricted

0 B

wh...@gmail.com <wh...@gmail.com> #374May 9, 2019 01:32AM

I got mine is September 2018 same problems. I wonder if this is batch dependent. Anyone here got the phone say last 3 months and facing the same issues?

wh...@gmail.com <wh...@gmail.com> #375May 9, 2019 01:38AM

#373 btw your what's your % of storage used?

wh...@gmail.com <wh...@gmail.com> #376May 9, 2019 01:39AM

it actually performs worst than my older phone with SD625. My old phone actually feels much smoother and more fluid.

ri...@gmail.com <ri...@gmail.com> #377May 9, 2019 10:54AM

I've got mine in Oct 2018... it can be batch related, but i think it's very unlikely, because even people with other memory are having issues (although I saw once a phone that was using 2 manufactures and both had an issue... different issues thou...)

Performance is very difficult to measure... although using the device should "worn out"... the best way would be making a factory reset on both... without any apps, mobile signal/wifi, etc.
But yeah, mi a2 shows some hiccups that should not occur... likely because of the emmc...

Imo we should try to move all this thread (or at least future discussions) to:

http://c.mi.com/forum-1227-1.html

ma...@gmail.com <ma...@gmail.com> #378May 9, 2019 02:52PM

My pixel 3a just arrived, so I'm going to unsubscribe i this moment. I feel sorry for the owners of the affected batch and hope those cretins will be held responsible somehow in the near future for their negligence.

mi...@gmail.com <mi...@gmail.com> #379May 9, 2019 10:44PM

#375

85%

But I've face reboots after a fresh factory reset with only a few apps installed...

wh...@gmail.com <wh...@gmail.com> #380May 10, 2019 01:04AM

pixel 3a is a nice phone, just saw it yesterday. the only downside is there's only one sim slot, the other is esim. Anyway in general there's are way too many nice and decently priced phones from other companies for us to put up with this shit from xiaomi.

wh...@gmail.com <wh...@gmail.com> #381May 10, 2019 01:37AM

#379 was just wondering coz your sequential write looks painfully slow. Mi a2 is really a crap phone.

ri...@gmail.com <ri...@gmail.com> #382May 10, 2019 11:02AM

@379
does this occur after any work with the memory? like cleaning the cache, installing/uninstalling apps, rebooting... etc?

ad...@gmail.com <ad...@gmail.com> #383May 10, 2019 11:22AM

4/64 here also

Easiest way to replicate it is the following: start copying a very large file to the phone via cable (I have used a 4-5 GB file) after 10-15 seconds into copying, phone UI starts to become unresponsive and eventually crash or freeze.

a few seconds after copying finishes, the phone will be back to normal.

after a full factory restore, above method gives the same results.

ri...@gmail.com <ri...@gmail.com> #384May 10, 2019 11:40AM

Does anyone know why cache cleaning is considered a different issue of the slow emmc?

mi...@gmail.com <mi...@gmail.com> #385May 10, 2019 02:51PM

#382

Nope. It's totally random...

Actually, I didn't even know, before reading the thread that brought me here, it was a chrome / cache cleaning related issue.

Like I said in my first post here, from day one I'm experiencing poor performance on this device.

Not smooth at all. Honestly, from what I remember, it performs the same way my original Moto G did after the first OS update (from kitkat to lollipop, if I'm not mistaken, which pretty much killed that device for me).

My backup LG G5 SE destroys the A2 performance-wise, even with LG's heavy UI customizations...

wh...@gmail.com <wh...@gmail.com> #386May 11, 2019 05:31AM

The mi a2 is just a stuttering mess and the best part is xiaomi thinks it's fine. So good luck waiting for any fix.

ce...@gmail.com <ce...@gmail.com> #387May 14, 2019 02:52AM

119210591, 118658586, 37048434, 132651311, 132651310, 113346931, 37130791, 124412355, 132609062, 132600809, 132612065, 132603291, 132603290, 132408114, 132621725, 37047566, 132144330, 132502609, 132274780, 36978378, 130306189, 122786936, 132562196, 131447183, 121304970, 112716912, 130636137, 69060926, 130892338, 126882641, 129163552, 132575652, 131060135, 132523057, 131775013, 132453139, 132455284, 132455282, 132481545, 132473211, 132502599, 132473216, 132528217, 132515778, 132502611, 132495833, 132515784, 132565620, 132546832, 132515787, 132546835, 132489115, 132587852, 132569408, 132569411, 132569412, 132587715, 132401143, 130085813, 125432843, 123653007, 124102557, 123979452, 128908792, 128973402, 130061837, 130042034, 131449902, 110911269, 112714505, 112926159, 112927340, 37018589, 117988573, 117266730, 109923682, 132435767, 37101826, 37002883, 36984056, 37576886, 117486314, 120630908, 132434254, 131381060, 112586994, 112517042, 132455277, 132475240, 132476180, 132434253, 132439808, 132434096, 132455272, 132434083, 132401649, 118036531, 122066787, 132402267, 132402784, 132408112, 132401659, 132402795, 132402797, 132402799, 132408120, 132402282, 132402802, 132402284, 132408124, 132435759, 132434240, 132434082, 132435764, 128697355, 132312906, 123461156, 37324649, 78842401, 129672929, 119182671, 117811333, 129588076, 130214962, 110692932, 130102815, 130786158, 129864757, 118182902, 132188446, 132188442, 131354561, 63132100, 74469013, 37053235, 119582512, 37919136, 117855263, 113348894, 37132168, 110762648, 112754914, 132274762, 132029565, 117201274, 120951626, 131206256, 112412166, 125437350, 112294488, 77549479, 112688535, 112604037, 132274553, 132280278, 132285676, 132274978, 132313042, 132274654, 132316438, 132323218, 132323235, 132312908, 132337599, 132333141, 132368533, 132365112, 132365597, 132365599, 78318912, 128898647, 131980598, 131947381, 131851828, 131733663, 132105394, 132191989, 132105393, 132144323, 132135609, 132102213, 132144324, 132102215, 132161205, 132144342, 132105408, 132105405, 132191990, 132188438, 132149392, 132196465, 132188441, 132197394, 132196471, 132192004, 132219843, 132197411, 132192006, 132249307, 132234926, 132226613, 132179822, 132274637, 132249308, 129926365, 119886485, 129726526, 37018931, 113070145, 78087306, 112815303, 129226384, 129250415, 129234661, 129261442, 129261438, 129275240, 129275239, 129288063, 129270276, 129362584, 129324474, 129365350, 129362483, 129396360, 129387032, 129425701, 129396363, 129457716, 129449590, 129457734, 129492777, 129497683, 129493709, 129583168, 129535295, 129583173, 129594933, 129620326, 129586748, 129629200, 129478248, 129702530, 129629202, 129700750, 129728443, 129728454, 129735594, 129726284, 129738221

an...@gmail.com <an...@gmail.com> #388May 16, 2019 06:45AM

So I have an update. Xiaomi replaced my phones motherboard with a newest manufactured one and guess what the phone still crashes on clearing the chrome cache. I tried to clear a 400mb cache and the phone rebooted. This time the emmc I have is MICRON and the write speeds are really bad. This is now really really bad.

ri...@gmail.com <ri...@gmail.com> #389May 16, 2019 11:31AM

@388
You are the guy who took the phone to the service right? (who said that for him... it was an issue)

This might be very bad... or very good...

very bad if they don't know or doesn't care that it could be a HW issue... therefore they are still selling it even if they know that there is a bug...
Usually manufactures will avoid using components with issue, because it could affect greatly their income because of the costs of the service and repair... basically a person would be getting 2 phones instead of one... so this means 2x components (not only the memory - which btw is basically attached to the processor... changing the memory is very hard, even for experienced people...)

very good if they see this as a SW issue and not HW... it doesn't mean that they will fix it... but there's a better chance of being fixable (even with custom kernels + rom)

But one thing is very very bad... even if there is a fixable SW issue... if you are saying that it got worse with the MICRON memory... then... micron might have another issue related to the speed... and cleaning cache will also be more affected... that would explain better why people consider this as 2 issues... although is memory related... one can be caused by xiaomi kernel code... and one can be caused by micron firmware...

Are you taking it again to the service?

ad...@gmail.com <ad...@gmail.com> #390May 16, 2019 11:51AM

Mine is also in service now, let's see what do they come up with, will keep you posted

ri...@gmail.com <ri...@gmail.com> #391May 16, 2019 11:53AM

@390

Cool thanks
Good to see that you are all taking it to service...

an...@gmail.com <an...@gmail.com> #392May 16, 2019 12:06PM

@389. I called the Mi India customer care to raise a complaint and they said suggested to take it to service center again and share the Job id this time, so that they can escalate the issue.
Lets see what happens. I talked to service center guys about a possible replacement and they do not do replacements at any cost and its upto the company to decide.

And yes, this time i got a Micron chip, and the phone rebooted when trying to clear a cache of 400MB. Earlier with Hynix My phone never rebooted but took 2 or more minutes to recover.
I will drop it in the service center again, lets they what they can come up this time.

ri...@gmail.com <ri...@gmail.com> #393May 16, 2019 12:18PM

@392
the problem is that they only raise the issue to the dev team if there is enough number of complaints... most of the issues are filtered by the local customer service team... but I always recommend that people keep trying and make number...

yeah about replacements is very hard for them to make decisions... usually because the factory doesn't keep spare parts... so when they actually need some spare boards, they need to ask the main factory which is likely to be in china... or india where the mi a2 would be producing (not sure if you have any xiaomi factory there). And usually they will ask the main head corp. what will be done in this case of replacement... if they decide that replacements can be done, they will have to guarantee that for everybody... and i don't think xiaomi wants to have that kind of less profit...

shi*... hynix always have issues... really... well not all but specially low tier memory... hynix takes just tooooo long to fix it... the experience i had with hynix was very bad some issues because of random bitflips... not sure if they fixed or if the memory was exchanged by another...

but yeah... people who can get in touch with service... should definitely take it there...

ch...@gmail.com <ch...@gmail.com> #394May 21, 2019 04:50PM

Same problem for me

ma...@gmail.com <ma...@gmail.com> #395May 21, 2019 10:58PM

Same here. Please help us.

ri...@gmail.com <ri...@gmail.com> #396May 21, 2019 11:16PM

Make stuff move here:

https://c.mi.com/thread-2162085-1-0.html

This thread at google issue tracker won't make xiaomi do anything

ja...@gmail.com <ja...@gmail.com> #397May 22, 2019 01:44AM

http://in.c.mi.com/thread-1819974-1-0.html

http://in.c.mi.com/thread-1669994-1-0.html

#396 mi community and both this google issue tracker thread won't make xiaomi do any thing. Above given links are threads created by me explaining every possible bit i know about the issue in detail. What's gonna happen there is one MFin moderator will ask you explain your problem in detail , seriously ?? After the long thread itself I've to explain it more. I explained , but then no reply. When I checked the bastard put and 'answered' stamp on my thread. Another one got reply, will forward issue to technical team. And then stamp. No course of action is going to be taken.

#392 how many more people have to raise the complaint for xiaomi to think it's enough to forward to the dev team. Trust me they are aware of the situation and scope of this issue. They just aren't taking action. They're making fun of consumers. No xiaomi phone ever have had this much complaint. Yes that's correct. No other MFing phone from xiaomi have had an issue like this for this many people . In every more than dozen email and feedbacks, i add links to this thread and mi community thread for them to checkout. If they've checked out atleast one if then they'd know the magnitude and scene of this issue. What's done is done we all made a mistake buying a device from xiaomi by putting trust in it . And what's xiaomi doing about these issues are putting a nail on every month on that trust with more problems rather than a fix in the name of updates. What can we do ? Move on and forget we bought this device and never ever purchase a device from xiaomi. And for the sake of f***in god , don't defend this greedy as* company on any level , not anymore please. Because they don't deserve it. If the issue was an isolated one with only a handful people affected by the issue, then everything you said makes perfect sense. But haven't you listened to anything I said earlier. They have silenced every article that came initially about this issue , so they're aware of the issue from the beginning and ,it shows they're just being unreasonable and staying g adamant not to fix the issue. I don't know why would an OEM do that. Xiaomi would do that if they want world to think their MIUi is better than stock android. Because that's where their profit lies. If you can't accept or take a grip of what I'm saying , then you're delusional or like I said earlier , you're paid off to speak good about xiaomi.

#and yes my old redmi note 3 have hynix emmc and other than being slower over nair 3 years of usage ,it is still able to clear cache over 1 GB in 2-3 seconds. My old A2 had hynix emmc and it used to get hang and restart. Now that it's samsung ,cache clearing is still slower but not like before and had not a single time force restarted. I don't know what to make of this because for #392 hynix didn't restarted the device only made it slow, for me hynix restarted the device. Fitr some people micron doesn't cause issue. But one thing that's consistent is that majority of users face this issue ,one way or other.

ri...@gmail.com <ri...@gmail.com> #398May 22, 2019 02:16AM

Well haven't seen your post when i searched back then...

I'm not defending them... Again that's just not how it works... There is literally no one reading forums... At least no one from dev team... That's just how it is man...
As a ex OEM developer... Being part of bsp team and also giving support for customer service... The dev team is the last team to be reached... Everything is filtered by the local customer service team... They will only raise an issue for the main devs if the issue start to affect sales... And the dev team is usually on another project already... So after the initial release the project is basically sent to small devs... In case of xiaomi i bet the main team is in China and the support teams are located in India... These local teams can do basic porting like patch applying and maybe some more basic issue solving... Also os upgrade are usually their responsibility...

The same goes for market share and sales... They don't give literally a f... About OS... Sales até not measured by that but whether it's carrier related or unlocked... The only os comparison is android x apple.... So don't rush into conclusions if you still don't get it how it works inside...

The rules of the games are pretty simple... Sell the phone... If it's sold then nobody cares about support... If it doesn't sell focus on the next one.... If anything raises a flag it's a problem... If not.... No harm done...
Do you know XGH? That's how it is... Literally.. And that is probably valid for all oem including xiaomi...

ja...@gmail.com <ja...@gmail.com> #399May 22, 2019 03:18AM

I don't know what's xgh . I agree that you might've worked for other OEMs but you haven't for xiaomi. Why do you think xiaomi has made such huge impact on tech world in really short time. Even samsung had to try little hard to dethrone nokia even with android . Xiaomi dethroned samsung with such ease(. I'm taking about india.) , It's because they don't work line other OEMs .So just because you've worked in an OEM Diane mean you can assume it's the same going on in other OEMs . Xiaomi works differently from other OEMs , i know that much because I was active in mi community and miui forum when redmi note 3 was my primary device.

And as for the sales stuff you said. Why do you think xiaomi has drastically reduced the price of mi a2 in India. It was launched for INR.16,999 online and INR.17,499 offline. Now it retails at INR.10,999. First perude cut was the next day emmc bug issue made way to internet through various online media. When I bought My redmi note 3 in august 2016 the device was manufactured and packed in 2016 august itself. When I bought my first A2 it was packed in August 2018 while I bought it in 2018 september. The replacement device i got in March was packed in 2018 december. And 3 of my friends bought device in march-april , their device was also manufactured and packed in 2018 december. Clearly the sales have seriously declined and that is due to the negative word of mouth the device have regarding these issue. So instead of fixing issues the solution they find is to keep reducing the price. At this point they're trying to clear the stock.

All those stuff you said might be valid for other OEMs , but not xiaomi. India is a difficult market. And things work differently here. And xiaomi knows that . If xiaomi is doing all these by knowing the outcome of torturing it's users like this, it's for the purpose of over glorifying MIUI,most A2 users who were disappointed with the phone were saying they should've home for Redmi note 5 pro/Note 6 pro , that's what xiaomi want. There was reports that eventually got buried about xiaomi was surprised that mi a1 overtook redmi note 4 sales and wasn't particularly happy with the development. After all xiaomi emerged into market with MIUI , not smartphones. If you still cannot understand what I'm saying , i don't know what to say.

ri...@gmail.com <ri...@gmail.com> #400May 22, 2019 03:44AM

Wait... You think you know how stuff works because you were an active user in a forum? India is a tough market? Oh my...
#shrug

I guess you really have no idea about oem after all... Just let it be dude...

Anyway for anyone having the emmc issue and cache issue... Forward your focus to this thread...

http://in.c.mi.com/thread-1669994-1-0.html&sa=D&usg=AFQjCNFk6htW8JkQ0bbUgg900bUekhLQVg

ja...@gmail.com <ja...@gmail.com> #401May 22, 2019 04:23AM

#400 good luck with that focusing ... And what the jack do you know about india than a citizen and consumer of india. And actively participating in a forum specifically beta development participation and discussions with actual moderators who directly communicates with dev team gives a more clear idea about how a particular OEM works than on working for another OEM. You work for another OEM , what part of all OEMs don't work the same you didn't understand ? I was registered for redmi note 3 beta development since miui8 . And was active tiil sometime after the release of miui9. And people communicate and bug reports were taken seriously and used to address most of them and updates were with a detailed change log. Some of these details (like dev team knows about the issue and is working on a fix like things)were available to people who haven't registered to beta team like me now. In the case of Mi A2, community is weirdly inactive.
And for the people who have emmc issue don't listen to #400 just go to service center and demand a replacement of the device as I'm almost certain Mi A2 production has stopped and replacement of the devices will only possible as long as the stock is available with the company. Xiaomi is aware of the issue and is not fixing it , so most probably it won't be fixed in the future either. Listening to #400 and focusing the issues in a useless place will only stall you guys until replacement will not be an option anymore. I got replacement from xiaomi , even after they first insisted they only repair the devices and not replace. I'm saying this from my experience with this device while somebody here is talking with his experience from another OEM. I have got a solution and I'm only pissed they're not enabling camera 2 api. I'm still replying to this thread to help others facing the issue.

And #388 there's possibility that the motherboard replaced might not be new. It might be from returned or refurbished phones. Now that replacing motherboard didn't fix the issue. You can confidently ask for the entire phone replacement. That's how a fellow guy from mi community got his device replaced , first they tried replacing the motherboard but didn't fix the issue so they replaced the entire phone. It was with that info I approached the service center , initially they said they won't replace the device but since I said I won't accept the device back until issue is fixed, so they tried communicating with xiaomi and send bug reports ,logs and video proof of device hanging and restarting. Finally xiaomi approved the replacement. They'll have to . And as far as with the information I have devices manufactured from november doesn't have the force restart issue, slow cache clearing might be present (but won't be minute long) . Most of the users who gets the force restart issue , they probably have the manufactured month august,september or October. I don't know for sure , but these are the info I got from asking around users .

ja...@gmail.com <ja...@gmail.com> #402May 22, 2019 04:25AM

And #400 the thread you mentioned in #400 is created by me.

wh...@gmail.com <wh...@gmail.com> #403May 27, 2019 01:18AM

Just sell the phone away. Problem solved. End of story. No more xiaomi. No more problems.

an...@gmail.com <an...@gmail.com> #404May 28, 2019 11:58AM

So here is an update. Mi replaced my phone with a brand new one and guess what , this phone also has the same issue. At this point I do not know what to do. I have contacted the service center again.

ri...@gmail.com <ri...@gmail.com> #405May 28, 2019 12:24PM

@404 same memory brand?

an...@gmail.com <an...@gmail.com> #406May 28, 2019 12:30PM

yes its MICRON. But they told me its 2019 manufactured.

ri...@gmail.com <ri...@gmail.com> #407May 28, 2019 12:47PM

@406
Ok so this is good...

If this info is true and it is really 2019 manufactured...
What happens is that... if there is a hardware issue and the memory/chip makers has a problem... usually they fix it in a couple of months and new devices rarely face the issue (is not 100% guaranteed because they always have a small portion of components already in the warehouse...) unless they didn't fix anything or wasn't aware of this issue... not likely because micron memory is probably in another devices too...

So this could indicate a SW issue... which means it is not hardware... so even if xiaomi won't fix... custom roms could fix this... (if this is really a sw issue)... Also it could have a fix for the next OS... (doubt)

IMO... if you are still facing the issue... take again to the official service and request a refund... usually the refund was done when a user took the phone to the service... and on the second return, if there was the same issue, they would accept a refund...
What i believe is that... there is no reason for you to expect anything fixed at this moment... (maybe with another memory would mitigate the issue... but doesn't seem like samsung memory has this issue fixed...)

Unless you want to keep trying... which i believe it's not worth it at this moment... as xiaomi will have more focus trying to increase their sales while huawei is facing some serious trust matters from users...
I mean... all the OEM right now will try to improve their sales right now... so all the focus on SW teams are likely to be in newer devices like K series for xiaomi... meaning that, although there is a team giving small support to mi a2... all the concerns will be towards devices that will increase sales at this moment (and not sold before)...

Samsung already is making this move...

http://www.techgrits.com/samsung-launches-campaign-to-exchange-huawei-for-galaxy-s10/

Xiaomi might take the older and lower tiers... like honor users and P10... or lite versions... so they could probably move towards an mi9... or even the brand new k20... or even mi a3...
so i believe that mi a2 right now (and for quite some time now...) will be backstage...

an...@gmail.com <an...@gmail.com> #408May 28, 2019 01:03PM

@407. I have informed the service center again of the issue on the new phone. The manager there has asked for a couple of days to revert with an update.
Lets see what do they say. Man this is getting on my nerves now since its been 2 months I have been following up with them and I really like the phone.
Its really sleek and very well made.
Is it worth it to push them to get me a 6/128 version. Are we sure this does not exist in that version ?

ri...@gmail.com <ri...@gmail.com> #409May 28, 2019 01:16PM

I heard one person having this issue in a 6-128...

IMO... if you have a chance to go to other device/brand... go...
If you cannot change... only upgrade to 128... then upgrade... but if you have the chance of paying more to get a better one... get a better one...

Usually this kind of projects (google)... there is a small team focused... it's really something separated... for example:

https://www.xda-developers.com/google-completes-acquisition-htc-engineers-google-pixel-2/

So with this kind of variant (memory... only...) usually the team is the same and only the build will change... meaning... it has the same tests procedures, same treatment and same devs and company politics...

Don't think it worth your patience...

an...@gmail.com <an...@gmail.com> #410May 28, 2019 04:15PM

This phone will have absolutely no value even if I try to exchange it. So I will wait for xiaomi to provide me a solution. Lets see what have to say now.

ra...@gmail.com <ra...@gmail.com> #411May 31, 2019 09:17AM

i have been waiting for 4 months as this bug was not fixed by xioami. i think so it is an emmc issue they used very bad emmc in this variant. great specs for lower price with worst hardware. very disappointed with xiaomi not be responding after many users reporting this bug for months. here after i won buy xiaomi mobiles and won't recommend to others

ri...@gmail.com <ri...@gmail.com> #412May 31, 2019 10:24AM

@411... man... we have been waiting almost since the release and it's gonna be like 1 year...
emmc is bad because of the phone price... but really... it doesn't justify the bugs...
i would love to say i won't but another xiaomi, but here the price is actually unbeatable...
so i would buy... but if the price and hardware specs really worth it...

ra...@gmail.com <ra...@gmail.com> #413May 31, 2019 11:11AM

please fix the bug as soon as possible i have been reporting this slow emmc
bug for last 4 months in mi feedback application nothing done by developers
initially i have faced microphone issue for 3 moths which is unacceptable
for the smartphone of this price and laggy phone which almost 300$ price
phone even 100$ smartphone is not lagging at present day.shame on xiaomi
for their lazy developers. please fix this bug as early as possible it is
very frustrating with laggy phone.thank you

On Fri, 31 May, 2019, 3:55 PM , <buganizer-system@google.com> wrote:

- Show quoted text -

wh...@gmail.com <wh...@gmail.com> #414Jun 2, 2019 08:03AM

i disagree that the price is unbeatable. There are many alternatives. You have to be a real sucker to keep thinking it's worth it..

an...@gmail.com <an...@gmail.com> #415Jun 11, 2019 10:36AM

Same problem, global version 4/64gb.
Freezes phone sometimes.. :(

Please, fix It.

aj...@gmail.com <aj...@gmail.com> #416Jun 13, 2019 11:09AM

Same problem.

ro...@gmail.com <ro...@gmail.com> #417Jun 13, 2019 03:25PM

Same problem,
Phone still Freeze. Any workaround?

pls.

st...@gmail.com <st...@gmail.com> #418Jun 16, 2019 07:03AM

I will probably change to Iphone 6 or 7. Could not find android phone without bugs.

wh...@gmail.com <wh...@gmail.com> #419Jun 17, 2019 01:09PM

well, i sent the phone for repair and the motherboard was replaced. I have not had a single freezing issue yet vs multiple freezing per day. Maybe i spoke too early but hopefully it stays that way. Some will insist that it's a software issue. Maybe, so good luck waiting for your software fix.

ri...@gmail.com <ri...@gmail.com> #420Jun 17, 2019 01:18PM

@419
Did it change the emmc manufacturer?

How about cache cleaning? Working?

wh...@gmail.com <wh...@gmail.com> #421Jun 17, 2019 03:50PM

My first Mi A2 one was one of the early batches. Then it got replaced. Based on imei, probably another early batch phone. But it went into bootloop after update and i wasn't able to test. The third replacement is probably a later batch again based on imei. Cant remember the previous emmc but the current one is hynix. Cache clearing still takes a long time and still can crash the phone. But at least it's not crashing randomly left right center multiple times per day. Everything and anything used to crash. Any apps, settings, really anything, ridiculously annoying and micro stutters, total nightmare, piece of shit..

ad...@google.com <ad...@google.com> #422Jun 18, 2019 09:29AM

Status: Won't Fix (Infeasible)

Unfortunately, this issue is not reproducible with our version of the AOSP source code for Pixel devices. Please file a bug with the respective OEM (Xiaomi in this case). This bug will be marked as closed.

ja...@gmail.com <ja...@gmail.com> #423Jun 18, 2019 05:02PM

# I don't know how all this works. But how the hell are you trying to reproduce a problem in Mi A2 devices with source code for pixel devices ? You've waited 8 months for replying there won't be a fix. We've tried mailing and sending feedbacks to Xiaomi several times and moderator response is software side is handled by Google and they're just pushing the update with some tweaks. If you guys are not going to fix , atleast show the humility to explain how software development and update policy works for Android one devices in detail. This information is nowhere to be found. All information that's available about it is speculations by bloggers.

[Deleted User] <[Deleted User]> #424Jun 18, 2019 06:57PM

My phone shut down after trying to clear cache for chrome , I think android one program Is worst , and I must have bought red mi note 7 series instead .

mi...@gmail.com <mi...@gmail.com> #425Jun 19, 2019 02:46AM

LOL

st...@gmail.com <st...@gmail.com> #426Jun 19, 2019 03:25AM

My phone still have warranty. Do you think I can get my money back?

st...@gmail.com <st...@gmail.com> #427Jun 19, 2019 11:57AM

I just updated my device with june patch and cleaned my cache of facebook and instagram and it did not freeze or reatart, but I made test with androbench and my writing speed is still around 50MB. Atleast I hope they fixed the freeze.

hu...@gmail.com <hu...@gmail.com> #428Jun 20, 2019 01:36PM

The June patch update no more results in freezing or slowdowns when clearing cache for me, tried it with Google Play Store and while uninstalling an app

kk...@gmail.com <kk...@gmail.com> #429Jun 20, 2019 01:48PM

i'm still using A1 with no issue.
so disappointed with A2.
updating June patch now to try.

ri...@gmail.com <ri...@gmail.com> #430Jun 20, 2019 02:06PM

Updated to june... True facts... Cache clearing don't hang the phone anymore... But the cache isn't cleared immediately... As i mentioned before... This seems like a workaround to not hold the ui thread... But it also means xiaomi is aware of this issue as it made a specific"fix" for the cache issue... If you leave the clear data page and return, you will see the cache slowly going down every time you enter... Well they might consider as fixed and the emmc issue might be set as won't fix and maybe they will wait for the next android version... I still see both emmc speeds and the cache issue the same... The cache issue was likely a bad implementation of the ui...which would be affected because of the emmc speed... That's why they made a workaround... But for now... I see no problems living with this implementation since i have not suffered any general hangs...

he...@gmail.com <he...@gmail.com> #431Jun 20, 2019 02:11PM

It's still much faster to clear the cache. Before, when clearing a ~600mb cache my phone hanged for 2~3 minutes. Now, I cleared a 900mb cache in ~20 seconds without freezing the phone.

fo...@gmail.com <fo...@gmail.com> #432Jun 20, 2019 07:57PM

On June update, cache clearing no more freezingh phone.. Initial reports.. Cannot say if true or not, will run R/W tests tomorrow morning..

ab...@gmail.com <ab...@gmail.com> #433Jun 21, 2019 09:37AM

After the June 2019 update cache or file clearing has improved significantly but random read/write and sequential read/writes are still not up to the mark especially random writes are abominable coming at less than 10MB/s which is unacceptable but frequent lags or freezes are almost gone unless you are using any ram hungry app. Overall performance has improved significantly I recommend everyone to update to this June build and turn off auto install of future updates until this issue is resolved for good. Don't update to July or any future update until Android Q update comes along. Xiaomi needs to install the new firmware if the firmware will be updated it will have the size of about 2 gigs which I don't think they are going to release that even if they have it ready. It is likely that they will use the opportunity of android Q update to do that too only if they have the fix.

Until then just update to June update it solves the cache clearing and frequent hangs and freezes. just don't update it further until android Q. You can turn off auto install of updates in developer options(see the attached pic).

deleted

Restricted

0 B

ma...@globant.com <ma...@globant.com> #434Jul 12, 2019 10:36PM

yes, that's true

lo...@gmail.com <lo...@gmail.com> #435Jul 12, 2019 10:50PM

Have anyone tried flashing another ROM? I'm guessing if I should flash Pixel Experience. Even after the June update my Mi A2 is laging like hell.

ab...@gmail.com <ab...@gmail.com> #436Jul 13, 2019 02:13AM

#435 What is the latest update installed on your phone? If its July update I don't know maybe the bug came back. I know for sure June update has fixed the bug. Try resetting the device it might solve the problem. I too reset the phone then it was behaving smooth although lagging stopped before reset after the update. Try resetting your phone.

lo...@gmail.com <lo...@gmail.com> #437Jul 13, 2019 03:50AM

#436 It has the June update installed. Just checked and the July update isn't even available yet to download. By reseting you mean restore to the factory standard?

ri...@gmail.com <ri...@gmail.com> #438Jul 13, 2019 01:13PM

@435

IMHO... xiaomi didn't fix anything... again, like i mentioned before, for me, both read/write emmc speeds and cache clearing/lags are the same issue.

At least this is how it would be first treated in a OEM...
Mostly because of android layers, i would understand the following:

Android apps
------------------
Android Framework
------------------
Kernel
------------------
HW

That's over simplified but it explains the concept... Imagine that i push a button in an app (like cache clean in settings app)...
It will call the inner layers of android (framework and kernel) until it actually sends to the emmc "clean this portion of memory".

Now imagine that there is an issue at kernel/HW levels. Hardware is not "updatable" unless they make a recall or you exchange the main board. From what i have seen, many changed the emmc but the issue has randomly persisted (some said it fixed). For every hw there is a driver or firmware that will control the hardware. Android (actually the kernel) makes a layer to "accept" all the HW making a common interface (again not like this but explains the concept), so all the above framework can call "clean cache" the same way, without knowing which HW is (like samsung, hynix etc)
So the low layers implementation is responsibility of the own manufacturer (not the OEM).

Now let's say that the clean cache expects that this task is super fast, so there is no code treating a slow memory response... what does it happen? Yeah... the lag while cleaning cache.
Imagine that this slow memory response is because of a bad implementation on the lower levels or even HW... What do you think Xiaomi would do to solve this?

"fix the issue of course"

Well... that's the problem... when we go deeper into the inner layers of android, the responsibility changes, because the ownership of the source code changes. When a wifi issue is detected inside a chipset, the chipset manufacturer makes the fix and sends a binary (blob) or image (like modem.img). When a wifi issue is detected because of Android, google provides a fix...

Now imagine a huge tree... being the main branch the google android, then forking for each OEM, each hardware, each carrier, etc.
Then google sends a patch saying "hey i fixed this issue, everybody update"... So imagine that you have a notebook, all written... then your teacher says "oops, i've made a mistake yesterday and the drawing is not a circle... change it to a square and change all the references to circle to square now"
You would have to go all the way back, change the information and check the places where it was also affected. That's the same for a source code (well almost)...

With all the changes done after months of development, many OEM doesn't apply "risky changes" if it could make the SW not stable. Depending how serious is the issue, they will balance the benefits and the possible re-testing.

Ok, so what does all that means...

When you clean cache, android still respond to user interactions, but if you go back to the cache cleaning size, you will see that the cache isn't cleared fast, it will slowly decrease the size. So what I believe it was done here, xiaomi made a patch that will only make workarounds to avoid you to notice that there is any lags. People who has bought this phone now, or haven't noticed the lag from clear cache, won't be able to notice anymore.

"you keep saying cache cleaning, but i have lags... not cache issue"

Yeah... that's why i think the issues might be related... you see... xiaomi needs to sell phones. If there is any issues with a memory slowly dying, and could be noticeable, what would you do?
Well... if you are a good guy, exchange everyone's phone. Honestly... i don't think they would...
I believe that cache cleaning was only one of the perceptible issues around all the issue with the memory... and the easiest one to hide.
Now imagine how they would hide lag, or benchmarks, or transfer files from the pc... it becomes a bit harder right?

What i think xiaomi will do (if they don't actually fix the issue)

1 - slow emmc read write in benchmarks will be ignored (won't fix)
2 - animation/system lags possibly the will reduce animation factor, while leaving as seeing normal (or will be ignored saying that this could be occuring because of 3rd part apps)
3 - transfer files from pc, possibly a buffer, but since this buffer would be located at the emmc, they will probably ignore this too and say that it is not reproduced with their equipments

Possibly an update for android Q might fix this, because of the kernel update... but who knows...

Anyway, this is my opinion about the issue and how it would possibly be treated internally

wh...@gmail.com <wh...@gmail.com> #439Jul 17, 2019 12:30PM

it really doesn't matter what you know or dunno about the process.
It's their internal process it's really something that we shouldn't need to concern ourselves with.
Just get rid of the phone and make sure your next phone is not mi a3 or any phone from xiaomi.
Save yourself the headache.

ri...@gmail.com <ri...@gmail.com> #440Jul 17, 2019 12:41PM

@439
true... avoiding xiaomi for a while now...

py...@gmail.com <py...@gmail.com> #441Jul 17, 2019 03:43PM

@439 don't worry xiaomi made sure we won't want to get the Mi A3. 720p screen after Mi A1 was 1080. No thank you it's called upgrading a phone not downgrading

lo...@gmail.com <lo...@gmail.com> #442Jul 17, 2019 04:30PM

@441 I'm sure i'm not going to buy the Mi A3. Xiaomi should have put a 1080p screen instead of this fucking triple camera setup. Really, it's a cheap phone, there's no reason to put a feature of flagship phones on it instead of a essential feature.

ab...@gmail.com <ab...@gmail.com> #443Jul 17, 2019 04:36PM

@441 Exactly, they made sure that no one buys their android one program phones now. Google should have strict control over the min specs of a phone having android one program. They[xiaomi] just want to show the world that their MIUI phones are better than android one program. "If you still buys that you better be ready to make significant compromises on the performance". I also don't blame them completely because literally not just xiaomi all oems are not in favour in making android one phones because apparently they can't collect telemetry only google collects telemetry and usage data of users. They loose control over the "what this user or how this user uses his phone lets see" part. This is also happening because there is literally no android one phone with SD660 or better which is android one and not made my xiaomi except pixel devices. there is no phone in the segment of 15k to 40k for android one even if there is they either skimp on processor or they sell it for about 20% higher margin just cause it is android one although I don't have problem paying for Mi A3(4+64) around 20k if it is android one I would take it for clean aesthetics but not providing full hd display in a android one phone is WTF! moment. Android one is perceived as premium segment I get it if i have to pay 3-4k more for same specs but compromising on screen would be the lamest decision ever. I guess I would just buy a MIUI phone with good specs and install custom rom like Lineage OS to get the stock experience or wait for Motorola's One lineup next release. It was a good run while it lasted with Xiaomi's android one lineup RIP!

I do have one other opinion about the android one program. There is very little chance but may be google is telling manufacturers to do this kind of nonsense because they want to make their pixel devices look good when it comes to stock android experience. I know it is very hard to believe but can't trust them too much, they do have history of abusing their monopoly in the past.

Well I have Mi A2 experience was cumbersome but all good or i can safely say decent after the june update at least it is not laggy or choppy in animations so feels smooth. I bought Mi A2 because it did not have ugly notch like all the other phones did, android one, looks (very classy one of the best looking phone out there having 7.3mm slim body), 18:9 screen resolution instead of nonsense like 19:9 or 19.5:9 so that youtube experience is very good without weird black bars. I also did made compromises on some aspects like 3.5mm jack(I still hate the fact It doesn't have it), no expandable storage camera quality is good so storage fills up quite fast on this phone. I regularly clear the storage and old photos from device to make room for new stuff. But despite the cons i still bought because for most of the time it is still a good phone. But looks like xiaomi lost on all pros with Mi A3. Don't recommend this phone to anyone. Get Redmi device and flash custom rom that is way better than buying a deliberately outdated hardware.

ri...@gmail.com <ri...@gmail.com> #444Jul 17, 2019 04:37PM

sorta agree with you...
in glass fingerprint + triple camera...
with an oled screen... people are already having ghost touch and image retention on many other xiaomi devices... getting a phone with oled display from xiaomi is just suicide...
price going for around 280 USD... nah... pixel 3a FTW...

ab...@gmail.com <ab...@gmail.com> #445Jul 17, 2019 04:43PM

@442 triple camera is just for show unlike A2. third camera is measly 2MP WTF why even give it and waste money on that and not give a full hd screen on an android one device. Seriously! Especially when you demand a premium on android one phones. I gonna keep my Mi A2 until it dies or get lost. I will only update it when I get android one with no notch on the head of the phone.

ri...@gmail.com <ri...@gmail.com> #446Jul 17, 2019 04:51PM

BTW... hey guys... I just read after the comment above... but the status of this issue is set as

Status
Won't Fix (Infeasible)

I am pretty sure it was set as assigned way back...

So i believe that the issue is totally xiaomi's fault and nothing that google source did not predict... meaning... the "fix" for not hanging the UI is likely to be really just a workaround...

Well... i guess we won't see a fix for android Q after all... let's just expect that this is not slowly killing the emmc life span...

wh...@gmail.com <wh...@gmail.com> #447Jul 23, 2019 04:36AM

There's is no way i'll ever use miui again. It's a huge mess. I get so pissed using miui i always ended up installing custom rom. So android one based mi a1, mi a2 were the only acceptable phones. If they want to push me away, i'll have no choice but to consider nokia, realme, oppo, huawei, samsung, pixel, meizu, asus, one plus... Say no to xiaomi, say no to miui.

st...@gmail.com <st...@gmail.com> #448Jul 23, 2019 05:03AM

It is not in the context but I type it here anyway. I was happy using
MI A2 but I find it hard to use on direct sunlight and this bug with the memory made me think about buying new phone. Which one do you think is better for everyday usage: pixel 3 , galaxy s9 or razer phone 2 which is on sale rightnow for 400 usd?

ri...@gmail.com <ri...@gmail.com> #449Jul 23, 2019 10:27AM

@448
go with the pixel... always...

i got a 2 xl recently because it was sorta cheap... although i'm not a big fan of amoled displays (because of burn in, thou i never had issues with that), pixels are just straight forward... I mean... constant updates, great camera, great performance, clean android experience...

Although i would rather get a pixel 3 because of phone size... so definitely pixel 3...

hu...@gmail.com <hu...@gmail.com> #450Jul 27, 2019 12:53PM

got the july update. tap 2 wake is gone, but animation of rotation is borked.. UGH

lo...@gmail.com <lo...@gmail.com> #451Jul 27, 2019 03:25PM

Just want to share what happened to my Mi A2.
After the latest I got enough of it's stuttering and lagging and got convinced Xiaomi won't fix it. My phone had the July update, then I followed the steps described on Xda to unlock the bootloader so I could flash a custom rom to see if I could have a better performance. After I finished the steps all my data got wiped. Now I noticed the performance for much better. Seems it have been fixed may in the June update. So if you still having some lags after the recent updates try to return your phone to the factory standards.

wh...@gmail.com <wh...@gmail.com> #452Aug 6, 2019 04:07AM

The fact that xiaomi can make a decent phone hardware perform worse than a shit phone tells you a lot about xiaomi. They make shit phones.

ri...@gmail.com <ri...@gmail.com> #453Aug 11, 2019 09:22PM

The device keeps lagging and freezing while downloading apps, completely freezes while installing or while moving files.
I ran Androbench and the speeds were extremely slow, even slower than the previous gen Mi A1.

deleted

Restricted

0 B

ri...@gmail.com <ri...@gmail.com> #454Aug 11, 2019 09:25PM

And not just a bit slower, literally 4-5 times slower and this isn't happening on custom ROMs, this is proof that only the stock ROM has this bug.
Google promises one of the best Android experience with Android ones, that is just a joke, a widely reported issue has not been fixed even after months.

ri...@gmail.com <ri...@gmail.com> #455Aug 11, 2019 09:29PM

If it is unfeasible to fix them Google and Xiaomi should do a recall or replace the defective hardware. A $300 Android One device has storage speeds slower than 5 year old budget phones, disgusting and pathetic.

ri...@gmail.com <ri...@gmail.com> #456Aug 12, 2019 02:51PM

@455

But if you mentioned that this only occurs for you with stock ROM, i don't see why you are complaining about defective hardware.

And also, if you are mentioning that it is slower than mi A1, it is not an Android One issue. This is solely xiaomi fault.

Considering what you are stating... custom ROMS doesn't present this failure, also i don't see any other manufactures complaining about this issue... so it's not top layers. And if custom ROMS runs ok, it is not lower layers...

I can only guess that it's not android system and not hardware firmware... so it has to be something wrong with mi a2 kernel...

ab...@gmail.com <ab...@gmail.com> #457Aug 13, 2019 09:22AM

@456

Yes. It is the kernel problem and have been solved recently by Xiaomi in June update. because it turns out that the solution was only workaround so that your read speed improved significalty hence better cache clearing performance. but write speeds are abysmal in this device. hence the problem doing multitasking. what's the point of having a SD660 if the phone starts lagging as soon as you start doing 2-3 things at the same time.

To those whose phones are still lagging and stuttering in animations. I strongly recommend reset to factory state it would solve the problem of lagging and stuttering. else don't expect much from Xiaomi they just want to sell MIUI devices and from now on I will gladly buy it and flash lineage os or pixel experience and be done with it. seems like that way is lot better to buy android one phones from xiaomi.

Those who are disappointed with the release of Mi A3 recently can check out Motorola One Vision it is a very good phone and it has everything. Hole punch display and headphone jack unlike Mi A2. It is currenly selling for about little higher than Mi A3 but it is much better.

ri...@gmail.com <ri...@gmail.com> #458Aug 13, 2019 01:34PM

@457

Yeah but they likely made a change to the system itself to fix the cache clearing right? I mean... probably creating a separated thread for the clearing process instead of waiting for a response from lower layers... but the kernel itself is very unlikely to change... i remember that SW eng didn't want to update the kernel neither make enhancements because the tests were too complex for a product that was already release (this is a problem that occurred with a different OEM but almost the same kind of issue)...

I remember that improving read ahead would mitigate the issues with lags and memory issues, but even when improvements were noticeable by testers, the dev team would not make the change...

But i agree... xiaomi with the release of A3 won't even make any efforts to improve this issue...

pa...@gmail.com <pa...@gmail.com> #459Sep 3, 2019 06:38PM

When camera api 2 enable in mi a2

ra...@gmail.com <ra...@gmail.com> #460Sep 21, 2019 10:47PM

4/64 same problem, i buy my phone from Romania

po...@gmail.com <po...@gmail.com> #461Sep 28, 2019 05:21AM

4/32 Same problem.
Great thing for my first Xiaomi phone...

fm...@gmail.com <fm...@gmail.com> #462Nov 19, 2019 01:29PM

Hi, same problem here, and the memory is fine,
HW 4/64
Version 9
Patch 05/11/2019
Kernel 4.4.153-perf+

ma...@gmail.com <ma...@gmail.com> #463Dec 31, 2019 07:06PM

4/64 same problem - Got my phone in Canada

fl...@student.uni-pr.edu <fl...@student.uni-pr.edu> #464Apr 6, 2020 08:56PM

Same problem here , i hoped to be fix with security patche but nope the problem still persist , sometime the phone freezes and when it gone its difficult to write on keyboard to many touch lags when typing

ab...@gmail.com <ab...@gmail.com> #465Apr 7, 2020 05:03AM

to all those who are still having multitasking problems and stutters here and there. Flash Pixel Experience. I'm using PE Fan Edition maintained by Dev Aryan Gupta(former official Maintainer).This Fan Edition supports Encryption+Play Store Certification so no problem of rooting devices, OTA Support so no need to flash again and again, Google Play system updates work fine, Fan Edition customizations like changing the status bar, three finger screenshots, clock in the center of the status bar, basic animations in the quick toggles of the notification bar, etc. It will work exactly as stock rom only better in performance(about 30% better). You can even change the Device fingerprint to get the new Assistant 2.0(changing the device fingerprint requires root)
Here's the telegram group.

https://t.me/pixeljasmine

JOIN and ask any query you guys have. Leave the stock rom. Stock Android 11 is even more unstable from Xiaomi.

ju...@gmail.com <ju...@gmail.com> #466Apr 18, 2020 05:05PM

4/64 - i'm so tired of this problem

d....@gmail.com <d....@gmail.com> #467May 12, 2020 01:40PM

Xiaomi....never more...

yu...@gmail.com <yu...@gmail.com> #468May 29, 2020 07:26PM

same problem here for 4/64 GB, just a trash can

yu...@gmail.com <yu...@gmail.com> #469May 29, 2020 07:29PM

the reason that push me to iphone xr

lo...@gmail.com <lo...@gmail.com> #470May 29, 2020 07:42PM

guys I trying to flash a custom ROM to see if can fix this problem but my USB port is broken. How can I root my Mi A2 without using the USB port?

pc...@gmail.com <pc...@gmail.com> #471Jun 10, 2020 09:08PM

Still freezing many times per day, very annoying.

[Deleted User] <[Deleted User]> #472Jun 22, 2020 05:58PM

Same for me 4/64 user

ll...@gmail.com <ll...@gmail.com> #473Jul 6, 2020 06:36AM

Same here, on 4/64. On that state, the phone cannot be consider as a working one.

aa...@gmail.com <aa...@gmail.com> #474Oct 1, 2020 01:39PM

SAME SAME SAME here, its seems useless to have such a great phone

pa...@gmail.com <pa...@gmail.com> #475Jan 21, 2021 04:42PM

Having 660 AI chipset it freezes like hell in just doing I/O, I need to wait like "click on clear cache, do your dinner and come back to see its still freezed and still clearing cache"...

ma...@gmail.com <ma...@gmail.com> #476Jun 7, 2021 05:51AM

Same here! Please fix!

lo...@gmail.com <lo...@gmail.com> #477Mar 1, 2022 04:19PM

4/64 facing exactly same problem

Issue 118036531

Description

Issue summary

Comments

ke...@gmail.com <ke...@gmail.com> #2Oct 21, 2018 09:55PM

nh...@gmail.com <nh...@gmail.com> #3Oct 21, 2018 10:48PM

ra...@gmail.com <ra...@gmail.com> #4Oct 21, 2018 10:51PM

ba...@gmail.com <ba...@gmail.com> #5Oct 21, 2018 11:12PM

an...@gmail.com <an...@gmail.com> #6Oct 22, 2018 12:09AM

gi...@gmail.com <gi...@gmail.com> #7Oct 22, 2018 05:45AM

s....@gmail.com <s....@gmail.com> #8Oct 22, 2018 10:15AM

al...@gmail.com <al...@gmail.com> #9Oct 22, 2018 10:36AM

lo...@gmail.com <lo...@gmail.com> #10Oct 22, 2018 10:48AM

30...@gmail.com <30...@gmail.com> #11Oct 22, 2018 11:31AM

em...@gmail.com <em...@gmail.com> #12Oct 22, 2018 12:00PM

yo...@gmail.com <yo...@gmail.com> #13Oct 22, 2018 12:15PM

me...@gmail.com <me...@gmail.com> #14Oct 22, 2018 12:28PM

br...@gmail.com <br...@gmail.com> #15Oct 22, 2018 01:31PM

si...@gmail.com <si...@gmail.com> #16Oct 22, 2018 04:17PM

te...@gmail.com <te...@gmail.com> #17Oct 22, 2018 05:17PM

to...@gmail.com <to...@gmail.com> #18Oct 22, 2018 05:56PM

ro...@gmail.com <ro...@gmail.com> #19Oct 22, 2018 05:59PM

[Deleted User] <[Deleted User]> #20Oct 22, 2018 07:50PM

mi...@gmail.com <mi...@gmail.com> #21Oct 22, 2018 07:50PM

va...@gmail.com <va...@gmail.com> #22Oct 22, 2018 08:39PM

ko...@gmail.com <ko...@gmail.com> #23Oct 22, 2018 08:47PM

pe...@gmail.com <pe...@gmail.com> #24Oct 22, 2018 08:54PM

ad...@google.com <ad...@google.com> #25Oct 23, 2018 06:11AM

r3...@gmail.com <r3...@gmail.com> #26Oct 23, 2018 07:00AM

ro...@gmail.com <ro...@gmail.com> #27Oct 23, 2018 07:50AM

ro...@gmail.com <ro...@gmail.com> #28Oct 23, 2018 07:51AM

ad...@gmail.com <ad...@gmail.com> #29Oct 23, 2018 08:20AM

ke...@gmail.com <ke...@gmail.com> #30Oct 23, 2018 09:27AM

gi...@gmail.com <gi...@gmail.com> #31Oct 23, 2018 10:16AM

to...@gmail.com <to...@gmail.com> #32Oct 23, 2018 10:49AM

ke...@gtempaccount.com <ke...@gtempaccount.com> #33Oct 23, 2018 12:15PM

[Deleted User] <[Deleted User]> #34Oct 23, 2018 01:11PM

mi...@gmail.com <mi...@gmail.com> #35Oct 23, 2018 01:16PM

sa...@googlemail.com <sa...@googlemail.com> #36Oct 23, 2018 01:32PM

da...@gmail.com <da...@gmail.com> #37Oct 23, 2018 04:02PM

pi...@gmail.com <pi...@gmail.com> #38Oct 23, 2018 04:10PM

el...@gmail.com <el...@gmail.com> #39Oct 23, 2018 11:45PM

s....@gmail.com <s....@gmail.com> #40Oct 24, 2018 06:52AM

ad...@google.com <ad...@google.com> #41Oct 24, 2018 12:16PM

md...@gmail.com <md...@gmail.com> #42Oct 25, 2018 02:10AM

a....@gmail.com <a....@gmail.com> #43Oct 25, 2018 08:48AM

el...@gmail.com <el...@gmail.com> #44Oct 26, 2018 02:15AM

el...@gmail.com <el...@gmail.com> #45Oct 26, 2018 02:20AM

e....@gmail.com <e....@gmail.com> #46Oct 26, 2018 10:32AM

wu...@gmail.com <wu...@gmail.com> #47Oct 26, 2018 12:00PM

wi...@gmail.com <wi...@gmail.com> #48Oct 26, 2018 12:21PM

on...@gmail.com <on...@gmail.com> #49Oct 26, 2018 12:42PM

se...@gmail.com <se...@gmail.com> #50Oct 26, 2018 02:17PM

va...@gmail.com <va...@gmail.com> #51Oct 26, 2018 04:04PM

ri...@gmail.com <ri...@gmail.com> #52Oct 26, 2018 05:17PM

ro...@gmail.com <ro...@gmail.com> #53Oct 27, 2018 11:22AM

jo...@stcharles.fr <jo...@stcharles.fr> #54Oct 29, 2018 12:48PM

fr...@gmail.com <fr...@gmail.com> #55Oct 29, 2018 10:32PM

lr...@gmail.com <lr...@gmail.com> #56Oct 30, 2018 05:29AM

pe...@gmail.com <pe...@gmail.com> #57Oct 30, 2018 10:01AM

ma...@gmail.com <ma...@gmail.com> #58Oct 30, 2018 10:18AM

ma...@gmail.com <ma...@gmail.com> #59Oct 30, 2018 12:25PM

m....@gmail.com <m....@gmail.com> #60Oct 30, 2018 05:19PM

ic...@gmail.com <ic...@gmail.com> #61Oct 30, 2018 11:09PM

sa...@gmail.com <sa...@gmail.com> #62Oct 31, 2018 11:06AM

no...@gmail.com <no...@gmail.com> #63Oct 31, 2018 01:35PM

jc...@gmail.com <jc...@gmail.com> #64Oct 31, 2018 03:35PM

jo...@gmail.com <jo...@gmail.com> #65Oct 31, 2018 08:05PM

jc...@gmail.com <jc...@gmail.com> #66Nov 1, 2018 03:58PM

gi...@gmail.com <gi...@gmail.com> #67Nov 1, 2018 05:46PM

da...@gmail.com <da...@gmail.com> #68Nov 1, 2018 11:00PM

ro...@gmail.com <ro...@gmail.com> #69Nov 5, 2018 04:38PM

ed...@googlemail.com <ed...@googlemail.com> #70Nov 7, 2018 08:42PM

cy...@gmail.com <cy...@gmail.com> #71Nov 10, 2018 07:38AM

jc...@gmail.com <jc...@gmail.com> #72Nov 12, 2018 02:18PM

ha...@gmail.com <ha...@gmail.com> #73Nov 14, 2018 01:45AM

ju...@gmail.com <ju...@gmail.com> #74Nov 16, 2018 08:31AM

br...@gmail.com <br...@gmail.com> #75Nov 18, 2018 02:38AM

an...@gmail.com <an...@gmail.com> #76Nov 19, 2018 01:32PM

ng...@gmail.com <ng...@gmail.com> #77Nov 19, 2018 03:52PM