Without modifying a specific Kernel, if your level 3 application is requiring a specific tag, part of the AgnosDB definitions, but not handle for this scheme, there is a way to retrieve it without modifying the kernel.

You can use an UC_Cx file (Update Conditions changes for Kernel Cx)

see UPDATE CONDITIONS

The goal is to place the file in the same folder than your level 3 application.

For example for testing it, with our level 3 certification, we place the UC_Cx in the assets and copy it in the ca.amadis.top folder, as for example for Discover:

/data/data/ca.amadis.top/UC_C6

By adding some logs for Android in the debug version for the Discover kernel, the logcat provides this:

 2023-11-09 15:08:03.133 403-1098 dpOverload...Conditions ca.amadis.top V Path=/data/data/ca.amadis.top/
2023-11-09 15:08:03.133 403-1098 dpOverload...Conditions ca.amadis.top V fileName= /data/data/ca.amadis.top/UC_C6
2023-11-09 15:08:03.133 403-1098 dpOverload...Conditions ca.amadis.top V size= 28
2023-11-09 15:08:03.133 403-1098 dev ca.amadis.top D dev_file_open() on /data/data/ca.amadis.top/UC_C6
2023-11-09 15:08:03.133 403-1098 dpOverload...Conditions ca.amadis.top V ifp= 1
2023-11-09 15:08:03.133 403-1098 dpOverload...Conditions ca.amadis.top V size= 1
2023-11-09 15:08:03.133 403-1098 dpOverload...Conditions ca.amadis.top V Tag= 9f6e = 09

The corresponding UC_C6 file is joined. changing tthe update conditions for tag 0x9F6E