[Xiaomi Mi A2 Lite Questions & Answers] cancam:
Hi!

Many thanks for this.

I have not used ADB in a while so I'll try to find some time to set it up and try it. I guess I'd need logcat running for a while or it just dumps all the logs in a dmesg-like way?

The hardware issue theory is interesting, though in my case it's a brand new phone (Should be less likely and be a manufacturing defect), and I have seen the notification even when flat on table (just double tapping to see if there are notifications, no movement involved). Also I guess that if it was movement dependent we would see the notification also while in use around and this has never happened to me.

I tried to restrict the background access to google photos and it let me, though I didn't see any difference.

Not sure if [MENTION=9995025]trash2009[/MENTION] can add something on this too?

---------- Post added at 03:55 PM ---------- Previous post was at 03:20 PM ----------

I tried it and this is what came out from logcat:

07-22 15:16:54.931 1895 1895 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,97}:
07-22 15:16:54.931 1895 1895 D StorageNotification: type=PUBLIC diskId=disk:179,96 partGuid= mountFlags=VISIBLE mountUserId=0
07-22 15:16:54.931 1895 1895 D StorageNotification: state=EJECTING
07-22 15:16:54.931 1895 1895 D StorageNotification: fsType=vfat fsUuid=8E9F-1EEB fsLabel=
07-22 15:16:54.931 1895 1895 D StorageNotification: path=/storage/8E9F-1EEB internalPath=/mnt/media_rw/8E9F-1EEB
07-22 15:16:56.403 1895 1895 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,97}:
07-22 15:16:56.403 1895 1895 D StorageNotification: type=PUBLIC diskId=disk:179,96 partGuid= mountFlags=VISIBLE mountUserId=0
07-22 15:16:56.403 1895 1895 D StorageNotification: state=UNMOUNTED
07-22 15:16:56.403 1895 1895 D StorageNotification: fsType=vfat fsUuid=8E9F-1EEB fsLabel=
07-22 15:16:56.403 1895 1895 D StorageNotification: path=/storage/8E9F-1EEB internalPath=/mnt/media_rw/8E9F-1EEB
07-22 15:16:56.404 1895 1895 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,97}:
07-22 15:16:56.404 1895 1895 D StorageNotification: type=PUBLIC diskId=disk:179,96 partGuid= mountFlags=VISIBLE mountUserId=0
07-22 15:16:56.404 1895 1895 D StorageNotification: state=BAD_REMOVAL
07-22 15:16:56.404 1895 1895 D StorageNotification: fsType=vfat fsUuid=8E9F-1EEB fsLabel=
07-22 15:16:56.404 1895 1895 D StorageNotification: path=/storage/8E9F-1EEB internalPath=/mnt/media_rw/8E9F-1EEB
07-22 15:21:23.712 1895 1895 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,65}:
07-22 15:21:23.712 1895 1895 D StorageNotification: type=PUBLIC diskId=disk:179,64 partGuid= mountFlags=VISIBLE mountUserId=0
07-22 15:21:23.712 1895 1895 D StorageNotification: state=UNMOUNTED
07-22 15:21:23.712 1895 1895 D StorageNotification: fsType=null fsUuid=null fsLabel=null
07-22 15:21:23.712 1895 1895 D StorageNotification: path=null internalPath=null
07-22 15:21:23.713 1895 1895 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,65}:
07-22 15:21:23.713 1895 1895 D StorageNotification: type=PUBLIC diskId=disk:179,64 partGuid= mountFlags=VISIBLE mountUserId=0
07-22 15:21:23.713 1895 1895 D StorageNotification: state=CHECKING
07-22 15:21:23.713 1895 1895 D StorageNotification: fsType=null fsUuid=null fsLabel=null
07-22 15:21:23.713 1895 1895 D StorageNotification: path=null internalPath=null
07-22 15:21:24.647 1895 1895 D StorageNotification: Notifying about public volume: VolumeInfo{public:179,65}:
07-22 15:21:24.647 1895 1895 D StorageNotification: type=PUBLIC diskId=disk:179,64 partGuid= mountFlags=VISIBLE mountUserId=0
07-22 15:21:24.647 1895 1895 D StorageNotification: state=MOUNTED
07-22 15:21:24.647 1895 1895 D StorageNotification: fsType=vfat fsUuid=8E9F-1EEB fsLabel=
07-22 15:21:24.647 1895 1895 D StorageNotification: path=/storage/8E9F-1EEB internalPath=/mnt/media_rw/8E9F-1EEB

I tried to leave it for a while see if it happened again but it didn't. Will try to get a new log when I see the notification back.

To me it looks like he is actively ejecting the card, unmounting it to then for some reason show the BAD REMOVAL (though he ejected it) and then mounting it normally.

The

No permission grants found for com.google.android.apps.photos

message is also appearing a lot on the logs.