This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PROCESSOR-SDK-AM62X: APP switch screen delay on am62x-EVM android os

Part Number: PROCESSOR-SDK-AM62X

Hi,

We developed an app and run on the am62x evm.

I  found a problem that there is almost 1 second delay when switch activity(Image).

And the system log always display below log when the activity switched.

How to solve this time out problem?

By the way, does the android sdk default to enable GPU driver?

How can I confirm the GPU function is work?

I also developed an test application ran the app on am62x/ am572x/ Pad to calculate the delay time for creating activity

>>protected void onCreate(Bundle savedInstanceState) {
>> Log.d(TAG, "onClick: onCreate 1: " + System.currentTimeMillis());
>> super.onCreate(savedInstanceState);
>> setContentView(R.layout.activity_main);
>> Log.d(TAG, "onClick: onCreate 2: " + System.currentTimeMillis());
>>}

1. am62x: almost delay about 200 ms 

2. am572x: almost delay about 90~100 ms

3. Pad: almost delay about 40 ms

Attaching the adb/bootup log, delay time file, example code.

MyApplication4.rar

DelayTime.xlsxam62x_boot_log.txtam62x_logcat.txt

Ken

  • Hi TI Champs:

    By looking at the customer logcat, those places listed as the below are using the DMA which might lead the BCDMA errors.

    BR Rio

    Line 801: 09-16 13:19:24.145   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 474
        Line 805: 09-16 13:19:24.229   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 475
        Line 814: 09-16 13:19:24.389   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 533
        Line 946: 09-16 13:19:24.668   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 535
        Line 948: 09-16 13:19:24.672   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 542
        Line 950: 09-16 13:19:24.675   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 866
        Line 952: 09-16 13:19:24.690   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 925
        Line 977: 09-16 13:19:24.775   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1110
        Line 980: 09-16 13:19:24.791   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 979
        Line 982: 09-16 13:19:24.809   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1073
        Line 986: 09-16 13:19:24.822   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 915
        Line 988: 09-16 13:19:24.838   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 906
        Line 991: 09-16 13:19:24.856   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 876
        Line 1197: 09-16 13:19:25.233   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 840
        Line 1218: 09-16 13:19:25.468   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 561
        Line 1887: 09-16 13:19:29.639  1110  1475 I DMABUFHEAPS: Using : Non-legacy ION heaps
        Line 1888: 09-16 13:19:29.639  1110  1475 E DMABUFHEAPS: No ion heap of name ion_system_heap exists
        Line 1889: 09-16 13:19:29.639  1110  1475 E DMABUFHEAPS: No ion heap of name ion_system_heap exists
        Line 2250: 09-16 13:19:33.655   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 925
        Line 2534: 09-16 13:19:47.760   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 979
        Line 2536: 09-16 13:19:47.773   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1213
        Line 2538: 09-16 13:19:47.787   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1073
        Line 2540: 09-16 13:19:52.321   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1554
        Line 2542: 09-16 13:19:53.813   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1376
        Line 2544: 09-16 13:19:53.826   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1580
        Line 2546: 09-16 13:19:53.838   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 915
        Line 2548: 09-16 13:19:53.853   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 906
        Line 2550: 09-16 13:19:53.866   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 876
        Line 2552: 09-16 13:19:53.879   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 840
        Line 2554: 09-16 13:19:53.898   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 561
        Line 2556: 09-16 13:19:55.332   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1644
        Line 2558: 09-16 13:19:55.344   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1619
        Line 2560: 09-16 13:19:56.210   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1279
        Line 2562: 09-16 13:19:57.053   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1435
        Line 2564: 09-16 13:19:57.067   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1705
        Line 2566: 09-16 13:19:57.080   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1416
        Line 2568: 09-16 13:19:57.914   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1763
        Line 2570: 09-16 13:19:57.927   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1736
        Line 2572: 09-16 13:20:10.347   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1213
        Line 2576: 09-16 13:20:15.171   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1675
        Line 2580: 09-16 13:20:15.188   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1793
        Line 2582: 09-16 13:20:15.201   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1376
        Line 2584: 09-16 13:20:15.213   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1580
        Line 2586: 09-16 13:20:15.225   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1554
        Line 2620: 09-16 13:20:19.635   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1435
        Line 2625: 09-16 13:20:19.659   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1763
        Line 2628: 09-16 13:20:19.674   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1736
        Line 2630: 09-16 13:20:19.686   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1705
        Line 2633: 09-16 13:20:19.701   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1619
        Line 2635: 09-16 13:20:19.712   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1416
        Line 2718: 09-16 13:20:25.930  1904  1941 I DMABUFHEAPS: Using : Non-legacy ION heaps
        Line 2719: 09-16 13:20:25.930  1904  1941 E DMABUFHEAPS: No ion heap of name ion_system_heap exists
        Line 2720: 09-16 13:20:25.930  1904  1941 E DMABUFHEAPS: No ion heap of name ion_system_heap exists
        Line 2728: 09-16 13:20:26.376   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1279
        Line 2746: 09-16 13:20:37.141   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1904
        Line 2749: 09-16 13:20:37.208   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1675
        Line 2751: 09-16 13:20:37.229   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1793
        Line 2778: 09-16 13:20:58.305   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1904
        Line 2782: 09-16 13:20:58.366   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 925
        Line 3029: 09-16 13:30:12.637   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 561
        Line 3031: 09-16 13:30:12.663   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1110
        Line 3033: 09-16 13:30:12.680   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 979
        Line 3035: 09-16 13:30:12.692   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 1213
        Line 3037: 09-16 13:30:12.706   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 876
        Line 3039: 09-16 13:30:12.719   417   417 W IMGMemtrackHAL: getMemoryRecords:543 Failed to read dmabuf fd references for pid 840
    Search "uEnv_j721e_vision_apps.txt" (3 hits in 3 files of 116 searched)
      new 9 (1 hit)
        Line 97: cp /opt/ti-processor-sdk-rtos-j721e-evm-08_04_00_06/vision_apps/apps/basic_demos/app_linux_fs_files/uEnv_j721e_vision_apps.txt /media/root/BOOT/
      C:\Rio_Shared_Folder_2014\1_TDA_Stuffs\SDK_From_Luke_Build_Stuffs\TDA4_SDK8.4_With_Onsemi_AR0233_Failed_1.txt (1 hit)
        Line 1021: app_sfm.cfg                run_app_tidl_16bit.sh       uEnv_j721e_vision_apps.txt             vx_app_sfm.out                       vx_app_tutorial.out
      C:\Rio_Shared_Folder_2014\1_TDA_Stuffs\SDK_From_Luke_Build_Stuffs\TDA4_SDK8.4_With_Onsemi_AR0233_Failed_3_With_Performance_Dump.txt (1 hit)
        Line 1022: app_single_cam.cfg         run_app_tidl_16bit.sh          uEnv_j721e_vision_apps.txt             vx_app_sfm.out                       vx_app_tutorial.out
    Sear

  •            Possible root cause:

                   Line 2718: 09-16 13:20:25.930  1904  1941 I DMABUFHEAPS: Using : Non-legacy ION heaps

                   Line 2719: 09-16 13:20:25.930  1904  1941 E DMABUFHEAPS: No ion heap of name ion_system_heap exists

                   Line 2720: 09-16 13:20:25.930  1904  1941 E DMABUFHEAPS: No ion heap of name ion_system_heap exists

  • Hi Ken,

    Log in console was link to an audio issue so perhaps this issue create so delay in all other task , to check this you can disable all audio efect in settings.
    do you use last Release 08.04.00? 

    i will check your app to see if i have reproduce you issue

  • Hi Rio,

    Concerning log link to ION , ion is deprecated so normal to not find it.
    you need to use dmabuf now and you have 3 heap , dma system heap is equal to ion_system_heap .

    Same if you are not on 08.04.00 releaes please move on it.

  • Hi,

    I only followed installation steps from TI web site.

    https://software-dl.ti.com/processor-sdk-android/esd/AM62X/08_03_00/docs/devices/AM62X/android/Overview_Building_the_SDK.html

    It mean that the AOSP version is 08.0.3.00?

    How can I check the AOSP verison or how to upgrade it to 08.04.00?

    Thanks,

    Ken

  • here you can download release prebuilt image :
    https://www.ti.com/tool/PROCESSOR-SDK-AM62X

    and find last documentation, step is the same as previous just change all 08.03.00 to 08.04.00

  • Hi,

    I have run the same test application on asop 08.04 prebuilt image android platform.

    The delay issue still remains.

    Attatching the system log and app logcat log.

    am62x_08_04_logcat.txtam62x_08_04_systemlog.txt

    Ken

  • Hi,

    I got below error when I executed command.

    #git clone -b 08.04.01.005 git://git.ti.com/atf/arm-trusted-firmware.git

    #git clone -b 08.04.01.005 git://git.ti.com/optee/ti-optee-os.git

    Is it the correct link to download bootloader?

    Thanks,

    Ken

  • Hello Ken,

    This will be fixed as soon as possible, you can use the release bootloader images meanwhile. Here is a link to the release image: https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-8cVNlmT7Aa/08.04.00/AM62x_08.04.00_emmc.tgz ( tiboot3.bin, tispl.bin and u-boot.img )

    Thank you,

    Safae

  • Hello Ken,

    The bootloader fetching issue is now resolved.

    Thank you for reporting.

    Safae

  • Hi Safae/G:

    This E2E ticket is aiming for the Android Delay.  (Boot loader is not the main issue.)

    Let's keep talking about this Android 12 delay issue.

    I studied this:

    https://source.android.com/docs/core/graphics/implement-dma-buf-gpu-mem

    Customer  - Ken confirmed the AM57 has no this issue.

    Only the AM62 with Android 12 has this issue.

    May you comment if this is the DMA-Buff matters?

    BR Rio

  • Customer-Ken has tried the method below, the result has no improvement.

    Follow the steps below to disable animations in Android.

     

    • Go to “Settings à About Tablet”
    • Scroll down and click on “Build Number” 7 times (You will see a pop up saying ’you are now a developer’)
    • Now go to “Settings à System à Developer Options”
    • Scroll down to bottom and you will see below 3 options, click on them and choose “Animation Off”
      • Window animation scale
      • Transition animation scale
      • Animator duration scale
    • Now the animations will be off
  • By checking the Android community, the Android is a laggy version:

    https://issuetracker.google.com/issues?q=Android%2012%20laggy

  • Hi

    Do you have any updates for this problem?

    Thanks,

    Ken

  • Hi,

    No specific update except as Rio say by email :
    dalvik.vm.usejit=true instead of false.

    we will do some test next week to know is some other settings can be change to have better performance on this,
    problem to play with this is you can probably create more graphics frame lost.

    i'll keep you inform when i have some news

  • Hi,

    Thanks for your reply.

    Please let me know if you have any further information.

  • Hi Ken,
    I do some stest but for now no better result as you .
    the best perf come with usejit changes so we will add this change in next release.

    i continue to check if some other change can help, if i find something i will reply on this thread