Quote:
Originally Posted by Renate
Great! Were you using my edl.exe or the Python one?
|
I did this on a linux machine so I used the Python one.
Quote:
Originally Posted by Renate
Slow listing
Ok, I kind of know what's going on, almost, sort of, possibly.
The Android Chimera (malware detection) running in the background is trying to do something. To keep doing it it's trying to get a Wake Lock. It's not allowed. That causes the System Server to write a error log for DropBox (why?) which it does to the staging area in /data/system/dropbox/ but then the DropBoxService tries to inform the DropBox provider (in KCB) with a broadcast intent (which it's not allowed to do).
This will certainly fix it:
Code:
pm disable com.google.android.gms/.chimera.GmsIntentOperationService
But you'd have to be root to do it.
All this junk is in /system/priv-app/PrebuiltGmsCore/PrebuiltGmsCore.apk
In any case, you can do a quick check that everything works beautifully with Android stopped (but again, you need root for that).
|
Out of curiosity, I just tried this and even with chimera disabled as you said, the time ls takes is the same
Code:
BOOX:/sdcard/Documents $ time ls -Rl tmp/ | wc
14054 112419 852684
2m59.88s real 0m00.72s user 0m03.72s system
BOOX:/sdcard/Documents $ su
BOOX:/storage/emulated/0/Documents # pm disable com.google.android.gms/.chimera.GmsIntentOperationService
Component {com.google.android.gms/com.google.android.gms.chimera.GmsIntentOperationService} new state: disabled
BOOX:/storage/emulated/0/Documents # time ls -Rl tmp/ | wc
14464 115699 877236
3m08.95s real 0m00.54s user 0m03.98s system
(The different file numbers are because it was still syncing, it's a folder with 20000 empty files.)
After stopping android I get an error message:
Code:
BOOX:/storage/emulated/0/Documents # stop
BOOX:/storage/emulated/0/Documents # ls
ls: .: Transport endpoint is not connected