I would like to see that, too. But the ride is still very unreliable to Disney standards. A 2 hour queue could easily turn to 4 or more hours with breakdowns. Just when I think they ride is running smooth and more reliable, there is a stretch of days when the ride starts acting wonky. Yesterday there was a 90 minute gap between BGs getting called early in the morning.
2 Likes
For those that practice pre-trip are you usually successful getting to that not so fast (or whatever that message is) screen?
2 Likes
Yes. So far Iāve only missed twice and that was my own dang fault for not doing it right. But when I follow @bebe80ās directions Iāve been 100% for Not So Fast or No Park Reservation Found
1 Like
It seems most people are successful in practice at a pretty high rate. Theoretically, on the real attempt you should have an even better chance if others from your party are also attempting.
Besides post 1, refer also to post 3.
I have practiced twice and not been successful either timeš¬ but both times I think I messed up. I did not log out of my app and log back in. Does that make a difference? Also both times I had something pop up on my phone right at seven which caused a problem. Iām not completely tech savvy so I have to figure out how to do speed checks on my phone?
That can be a problem. Others have suggested to turn off all phone notifications temporarily, especially if you are one to get a lot of them.
I recall someone getting an alert from their Ring doorbell back home, luckily a backup person attempting was able to secure.
2 Likes
One of the two times I missed was 100% because of this.
1 Like
Ha! I have read it all!
I have only tried 3 days but I am only 1 for 3
1 Like
Practice makes perfect 
If only I have not convinced myself I will panic and completely mess it upā¦.
1 Like
Harness that adrenaline 
1 Like
Fixed
4 Likes
My first few practices I was successful about 50-60% of the time, then over the last several weeks, more like 90-100%.
On our actual trip I was successful 3/4 times. We got BG 17 the first time for all 7 people, then 21 for 4 people, then 30something for 4 people. On our 4th (and completely overkill) HS day, I failed. I hit join with the side of my finger/fingernail instead of the pad of my finger and the click didnāt register. That second long delay (at most) cost us a BG that morning. That was also the only day DH was still sleeping and not being a backup attempt.
We did succeed at the 1 pm drop that day.
Overall, practice makes almost perfect. Keep trying until you figure out what works for you, and it will hopefully be good enough. The system is stressful but donāt psych yourself out!
2 Likes
Yes, only when the app is opened, or running in the background. It goes by atomic (world) time and beeps at xx:xx:55, :56, :57, :58, :59, :00.
So, I just open the app at 6:57 or 6:58. Then, back out and get into MDE. Wait for the 5th beep at 6:59:59 and Boom!
2 Likes
I have an Android, so not sure if that matters if you are an iPhone. But it is called Atommic Clock and Watch Accuracy Tool (with NTP Time).
It is a blue icon with an atom looking drawing in the middle.
3 Likes
As seen above, there are multiple versions. See which works best for you.
1 Like
Others have also mentioned to turn on the ābeepingā as the time approaches the top of the minute. When enabled, it will beep at x:xx:55, x:xx:56, x:xx:57, x:xx:58, x:xx:59 and then a longer beep at xx:xx:00.
In the Android version of the app, the switch to turn on the beep is called āPlay Greenwich Time Signal when next minute is approachingā
6 Likes
Just checking you click the first join screen at xx59?