I think it’s a bug, because if you think about it with a beginner’s mind you’d agree that it’s a bug.
Try to think like a beginner
What is the error? You didn’t even show me the video from my second link.
Well, what does the beginner think?
Please Wait Sir 
Here is the official certificate at the Activity Lifecycle.
https://developer.android.com/reference/android/app/Activity?hl=ru#onStart()
If a novice reads it carefully, they will understand that there are many different events on the screen and onCreate is different from onStart and everything else.
You see, it’s the same several times. and the odd thing is why (Screen Open) keep growing in the list
You can see that the [Start] block on screen 2 is executed only 1 time, and [Opens] is executed several times each time screen 2 is displayed. Here’s the second difference.
I still can’t understand the oddities that exist, and why it must be several times for them to change.
is this problem because of block (navigate)
Let’s start with the fact that there is a bug, because on my Android 9 everything works differently than on your video )))
What device and OS version are you using?
- Brand = asus
- Model = ASUS_Z012DB
- Android Version = 8.0.0
- API = 26
- Codename = Oreo
- Release = 8.0
hmm, can you record your project on your phone
I’ll deal with it now and give you an answer))
Thank you very much 
I changed the project for a better understanding of the work, so open it again Thunkable it turns out like this
Why does it work like this? When using the navigation block outside of the navigation components, a new screen is created, so when switching from Screen1 to Screen2, Screen2 is created again and [Starts2] =1 and [Opens2] =1. Back from Screen2, the transition to Screen1 occurs when the system back button is clicked, so an existing Screen1 opens. If switching to Screen 1 points using the navigation block, then a new screen would be created and [Starts 1] =1 and [Open s1] =1
When the navigation block is used inside navigation components, new screens are not created, but a transition occurs between existing screens in navigators. This is why the number [Open 2] increases, and [Starts 2] = 1, because [Starts] for each screen is only executed 1 time always.
Now you have it working the way I have it in the video?
I recommend that you install the Bluestacks 4 emulator on your PC.it Will not be superfluous to test applications in it.
I become confused
I didn’t understand what you were trying to say. You can view additional information in the translation at the link http://droidscript.ru/main/statyi/thunkableios_navigation.php
Navigating between screens is a complex topic and you can easily fall into traps, especially if you mix different navigation methods without understanding how they work. That’s why I gave you a link to more information.
I think my brain should be refreshed for some time
why on your cellphone the listview can add (Screen1.Opens) in screen1, and on my cellphone it can’t.
This is a good question.
-
is there an update to Android 8.1 for your phone?
-
are you using the latest version of Thunkable Live?
-
have you installed bluestacks 4 (it is better to install version 64 if your computer supports the requirements for It)? It uses Android 7 and you can check how it works
The most important question. On your last video on the screen 2 button to Navigate to Screen3. Do you click on it and go to Screen1 or do you use the system back button?
As I said, the problem occurs when mixing different navigation methods. Why is [Open2] increasing and [Opens1] = 1? Because when using the navigation block from Tab Navigator, it creates a new Screen1, and when this new Screen1 goes to screen 2, it does not create Screen2 again, but returns to the one already created.
Recently, the navigation block was changed and now it works like this.
I have noticed this-
when you check it on computer, screen always goes to Open mode and when you check it on device it goes in Screen Starts mode.