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.

How to start app in full screen, no splash screen

Other Parts Discussed in Thread: AM3517

Hi everyone,

I am developing an android device that need to boot directly in an application, without loading screen. My device doesn't have a touch screen, only some GPIOs.

Does anyone know how to modify the filesystem/boot script to do this?

Best regards,

Jerome

  • Quick data;

    Adding a "am" command to start the application in init.rc or init.<platform>.rc, you can use ./adb am or am alone for runtime help, or check next link,

    http://omapedia.org/wiki/Android_How-tos#Run_Android_Application_from_Command_Line

    ./mydroid/packages/experimental/ExampleImsFramework

    About splash screen you are talking about the boot animation or a splash screen in your application, I found next command for emulator -no-boot-anim the link is

    http://developer.android.com/tools/help/emulator.html

    and to avoid the initial lock screen check (add proper permission to disable keyguard)

    http://developer.android.com/tools/testing/activity_testing.html#UnlockDevice

    -no-boot-anim

  • Hi Manuel,

    Thanks for your tips. Ill try those as soon as I have my development board.

    I have another question. In my product, I don't need the Android environment. I mean I don't need to have access to dashboard, I don't need to configure time or open a browser. So I would not like to boot in "Android mode". I would like to launch only my android application. Do you know if it's something that can be done?

    I don't know if I explained it well, but I could make a parallel with a Linux example. It's like if I wanted to boot linux, launch X11 server and start a graphic application from command line, without loading KDE or Gnome.

    Best regards,

    Jerome

  • I have been thinking about this possible question since yesterday, and I cannot find the answer that you are requesting, from my point of view it is important to have Toast Notifications or Status Bar Notifications because they are part of the System's notifications and they are used to interact with the user, for mentioning one example. I have not heard of this type of change you are asking.

    My suggestion is to use a non-telephony configuration that is going to reduce used memory and free some resources, changes like the ones explained in next post and link,

    Android 2.3.4 on AM3517 - non Phone device (http://e2e.ti.com/support/embedded/android/f/509/t/213419.aspx)

    Or in next link from previous post,

    http://processors.wiki.ti.com/index.php/Android_gingerbread_memory_analysis_for_non-phone_device