Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NtSpeed appears off screen if device is rotated Landscape when SpringBoard loads #13

Open
badger200 opened this issue Apr 27, 2019 · 4 comments

Comments

@badger200
Copy link

Upon jailbreaking, NtSpeed is only visible if I rotate my iPad to Landscape with a home button on the left. Any other orientation, I can see the NtSpeed box fly away to a position off screen.

However, after restarting SpringBoard a second time, then NtSpeed always appears in correct position in all 4 orientations.

Also, the location settings adjustments are extremely erratic and make it very difficult to position the bar correctly. It took me a week to finally achieve the perfect location:

Width: 40
Height 35
Location X: 5
Location Y: 49

These next two aren't as crucial but nevertheless:
Radius: 6
Alpha background: 0.50

Absolutely spectacular tweak BTW, I can't live without it!

@badger200
Copy link
Author

I noticed if I rotate upside down (iPad home button at top), NtSpeed appears visible with correct x axis near the right edge of screen, but the y axis is about 2" lower than it should be.

@BzowK
Copy link

BzowK commented May 24, 2019

Hey Guys - Just my 2 cents about similar issues -

Below are the issue I encountered on my iPad Pro (landscape) with details following...

  1. Any (even tiny) adjustment to settings for ntSpeed result in the speed box being replaced with a small shape with no text (purposeful?)
  2. Any (even tiny) adjustment to settings for ntSpeed result in the speed box jumping off-screen
  3. In line with 2 above, a respring restores the seemingly correct and working speed box in a different area than what was previewed

When I initially installed ntSpeed, I thought it didn't work only to discover that it was off-screen due to my iPad being in landscape mode (which is how I use it 99% of the time). I played with the X + Y settings which didn't show the standard speed indicator, but a small odd shape. Regardless, once I got it in the desired position and respringed, it was still off-screen. I was finally able to get it to work, but only by following the below steps about 20 times until it was close to where I wanted it...

  • Visit Settings / ntSpeed
  • Adjust X + Y settings (Preview appeared offscreen)
  • Repring

After each respring, the speed box seemed to display correctly. It is only after changing any setting for ntSpeed that it would immediately go offscreen and in a different location. I tried moving to portrait mode to see if it appeared properly, but it was all out of whack so disregarded. Only had installed for an hour so will update if anything else new discovered.

To note, separating upload / download or at least having an option to within the same speed box would be fantastic.

I have ntSpeed beta6a installed on 12.1.1 on my iPad Pro (A12) and am looking forward to a potential fix soon -

Thanks for your time on this!

@badger200 badger200 changed the title NtSpeed appears off screen until 2nd SpringBoard restart NtSpeed appears off screen if device is rotated Landscape when SpringBoard loads Sep 13, 2019
@badger200
Copy link
Author

@BzowK I finally discovered what is happening. NtSpeed works perfectly as long as I hold the device in Portrait with home button at bottom, when SpringBoard loads. If I have my iPad in landscape during SB load/reload, it throws everything off in NtSpeed.

So your tests adjusting the NtSpeed positioning are invalid if they were not all performed with device in Portrait position.

I looked at the code and I believe there’s just a small typo in one of the 4 rotation sections where it swaps X and Y with the screen.height and screen.width but I don’t have access to Xcode at the moment unfortunately.

@badger200
Copy link
Author

This bug is now over a year old and I’ve posted the fix 4 months ago, any chance it can be implemented?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants