End screen glitch skip

Toturial:

You have to play in version 1.24, first exit the game and then enter again, after you reach the door touch the red laser and then go to the main menu then press continue and wait a few seconds until the end screen appears

Video tutorial:
https://youtu.be/eOcZR6xTED4

Level Layouts

## Level 1:
https://i.imgur.com/7g69HZr.png


## Level 2:
https://i.imgur.com/Hbvp6bW.png


## Level 3:
https://i.imgur.com/NOwSAjg.png


## Level 4:
https://i.imgur.com/lWIM9qB.png


## Level 5:
https://i.imgur.com/wFH54Of.png


## Level 6:
https://i.imgur.com/VxJT5Gh.png


## Level 7:
https://i.imgur.com/4HKJn4u.png


## Level 8:
https://i.imgur.com/yve2TBg.png


## Level 9:
https://i.imgur.com/AxiuDCI.png


## Level 10:
https://i.imgur.com/Qzt9Uo7.png


## Level 11:
https://i.imgur.com/Fqq58SP.png

Play Bounce using WSA on Windows 11

1.) Install WSA from [here](https://apps.microsoft.com/store/detail/windows-subsystem-for-android%E2%84%A2-with-amazon-appstore)

2.) Open WSA and go to "Developer". Enable Developer Mode. Copy the IP address.

3.) Download Platform Tools - [here](https://developer.android.com/studio/releases/platform-tools)

4.) Extract the zip file and open the platform-tools folder. Right click and select "Open in Windows Terminal.

5.) Enter the following command: `.\adb connect <ip address`, here `<ip address>` is to be replaced with the one you copied from step 2.

6.) Download J2ME Loader APK - [here](https://github.com/nikita36078/J2ME-Loader/releases/download/1.7.5/J2ME_Loader-1.7.5-open-release.apk)

7.) Place it in the platform-tools folder

8.) Run this in Terminal - ` .\adb install J2ME_Loader-1.7.5-open-release.apk `

9.) Now you should be able to open J2ME loader as a native app in Windows 11.

10.) Download bounce.jar and put it in platform tools folder.

11.) Run this in Terminal - `  .\adb push bounce.jar `/storage/emulated/0/Download/  `

12.) Now you can find it in the downloads folder when you open J2ME loader.

For any queries, DM me - `G M P#0177` on Discord.

Note, all commands to run without the ` ` quotes.

Timing ILs taken from full runs

# PS: Bounce runners and viewers please ignore this, I am using this page a sandbox for another game will delete it shortly.

## What is the timer bug?

Timer bug is a logical error in the game's code due to which there are only 719 elapsed frames per minute as opposed to the expected 720. Because of this, the timer essentially jumps from [**X**]**:59.916** to [**X+1**]:**00.083** on every minute transition.

## What is the impact?

Full runs are unaffected by this because the points at which this occurs is consistent. In case of the Individual level runs, it is a bit trickier. For example, let's say a level is 1 minute and 30 seconds long. If the level starts at **1:10:00.000** it will go through one minute transition (**1:59.916**->**2:00.083**). But if the level starts at **1:40:00.000** it will go through two minute transitions (**1:59.916**->**2:00.083** and **2:59.916**->**3:00.083**). This means for the same gameplay the level will be one frame longer in the way the game measures time.

## What is the solution?

In the above example, for the second case, one frame will be subtracted to ensure fairness. All the old runs have been either been retimed manually to reflect the change. All the new IL attempts done using the updated autosplitter will have this issue fixed internally. As for full run segments that are submitted as ILs, the following webpage can be used to calculate the correct time of the IL run:
https://gmpranav.github.io/pop1-il-calculator/

Name	Author
End screen glitch skip	do_ob 2 years ago
Level Layouts	GMP 4 years ago
Play Bounce using WSA on Windows 11	GMP 2 years ago
Timing ILs taken from full runs	GMP 1 year ago