When kernel Exception, System server exception and other problems occur, the MTK internal mechanism will crawl related exception debugging information, generate the corresponding DB file, and put it under the Aee_exp folder. In different cases, the path to the Aee_exp folder and the number of DB files under the Aee_exp folder will vary.
A. DB path
The path to the DB has only two paths:/data/aee_exp or/sdcard/mtklog/aee_exp. Where/sdcard is generally built-in sdcard. The rules for DB actual storage path are as follows:
(1) ENG version
The ENG version defaults to open Mtklogger, so the DB priority is typically placed in/sdcard/mtklog/aee_exp. But when a KE restarts such an exception, the Mtklogger is not up yet, then Aee_exp is generated in/data/aee_exp.
(2) User version
The user version is turned off by default Mtklogger, so at this point the DB is generated in/data/aee_exp. However, if you open Mtklogger in the user version, Aee_exp is generated in/sdcard/mtklog/aee_exp.
Two. Number of DB under Aee_exp
In cases where the user version is off Mtklogger, only the fatal-level exception is taken to fetch the db (Contains the Ke, exception reboot,system_server je and NE, and software WatchDog). and Aee_exp Save up to 4 db files, name such as db.xx.dbg, where xx is "00", "01", "02", "03", and then the exception occurs in order to overwrite "01", "02", "03", will keep the oldest "00".
In other cases, the exception DB that includes the exception level is crawled, and Aee_exp saves up to 20 db files (db.00.dbg,db.01.dbg,......db.19.dbg), overwriting "01", "02" in the event of an exception. , "03" ... "19", will retain the oldest "00".
Where is the db file generated and what is the number of builds?
