S Startup Active Member Licensed User Longtime User Jan 24, 2016 #1 I make #StartAtBoot: True and StartActivity("Main") in the Starter service module and Activity.LoadLayout("Main") in the Main module which just loads a panel. When I run the App the panel loads OK but when I close the App and reboot the device the App runs but does not display the panel. What am I missing? Here's the simple zip file. Attachments AutoStartTest.zip AutoStartTest.zip 7.4 KB · Views: 307
I make #StartAtBoot: True and StartActivity("Main") in the Starter service module and Activity.LoadLayout("Main") in the Main module which just loads a panel. When I run the App the panel loads OK but when I close the App and reboot the device the App runs but does not display the panel. What am I missing? Here's the simple zip file.
Erel B4X founder Staff member Licensed User Longtime User Jan 24, 2016 #2 1. Are you testing it in release mode? 2. Make sure not to kill the app as it will prevent it from starting (don't swipe it from the recent apps list). 3. Try to use CallSubPlus to show the activity after a few seconds. https://www.b4x.com/android/forum/threads/60877/#content Upvote 0
1. Are you testing it in release mode? 2. Make sure not to kill the app as it will prevent it from starting (don't swipe it from the recent apps list). 3. Try to use CallSubPlus to show the activity after a few seconds. https://www.b4x.com/android/forum/threads/60877/#content
S Startup Active Member Licensed User Longtime User Jan 24, 2016 #3 Erel said: 1. Are you testing it in release mode? 2. Make sure not to kill the app as it will prevent it from starting (don't swipe it from the recent apps list). 3. Try to use CallSubPlus to show the activity after a few seconds. https://www.b4x.com/android/forum/threads/60877/#content Click to expand... Thanks Erel. 1. I am running in release mode. 2. I close (in the list of running Apps) the App before restarting the device. 3. While reviewing CallSubPlus approach I came across NJDude's post which works perfectly for me. For me, this is, I think a simpler approach? Upvote 0
Erel said: 1. Are you testing it in release mode? 2. Make sure not to kill the app as it will prevent it from starting (don't swipe it from the recent apps list). 3. Try to use CallSubPlus to show the activity after a few seconds. https://www.b4x.com/android/forum/threads/60877/#content Click to expand... Thanks Erel. 1. I am running in release mode. 2. I close (in the list of running Apps) the App before restarting the device. 3. While reviewing CallSubPlus approach I came across NJDude's post which works perfectly for me. For me, this is, I think a simpler approach?
Erel B4X founder Staff member Licensed User Longtime User Jan 25, 2016 #4 Step 2 is the problem. Upvote 0
S Startup Active Member Licensed User Longtime User Jan 25, 2016 #5 Erel said: Step 2 is the problem. Click to expand... Thanks Erel. But, the App now starts up OK at boot even when I close (in the list of running Apps) the App before restarting the device using NJDude's post approach. Upvote 0
Erel said: Step 2 is the problem. Click to expand... Thanks Erel. But, the App now starts up OK at boot even when I close (in the list of running Apps) the App before restarting the device using NJDude's post approach.
