Apples own iPhone apps never rotate "upside down" in portrait mode, so you can use a landscape view on your side with no trouble. 3rd party apps should follow this convention.
IPhone Developers: We use our iPhones in bed, allow us to disable landscape
51–55 of 55 posts
Re: IPhone Developers: We use our iPhones in bed, allow us to disable landscape
#52This is an excellent point. It annoys me daily.
Re: IPhone Developers: We use our iPhones in bed, allow us to disable landscape
#531. Jailbreak.
2. SBSettings.
3. RotationInhibitor.
4. There is no step four.
Seriously, why more people don't just jailbreak their devices and make it work the way they want it to work baffles me. Jailbreaking my 3GS (running 3.0 originally) took a total of 3 minutes using the purplera1n method. The redsn0w takes a bit longer and has more downloading involved, but still...
Re: IPhone Developers: We use our iPhones in bed, allow us to disable landscape
#541. Jailbreak. 2. SBSettings. 3. RotationInhibitor. 4. There is no step four. Seriously, why more people don't just jailbreak their devices and make it work the way they want it to work baffles me. Jailbreaking my 3GS (running 3.0 originally) took a total of 3 minutes using the purplera1n method. The redsn0w takes a bit longer and has more downloading involved, but still...
9 out of 10 support requests for my app come from jailbroken users. About 1/3 are actual cracked copies; I can tell, because they register with our API server and the app sends along little bits of goodies. I ignore those, other than a "Buy a legitimate copy and I'll be more than happy to help you."
The other 2/3's are crashes from jailbroken devices. Directly caused by SBSettings. In fact, having the users go in and turn everything off in SBSettings usually fixes it.
So that's why jailbroken devices suck. It's not about "making it work the way they want", it's about having a stable environment for your applications to run in.
Re: IPhone Developers: We use our iPhones in bed, allow us to disable landscape
#551. Jailbreak. 2. SBSettings. 3. RotationInhibitor. 4. There is no step four. Seriously, why more people don't just jailbreak their devices and make it work the way they want it to work baffles me. Jailbreaking my 3GS (running 3.0 originally) took a total of 3 minutes using the purplera1n method. The redsn0w takes a bit longer and has more downloading involved, but still...
9 out of 10 support requests for my app come from jailbroken users. About 1/3 are actual cracked copies; I can tell, because they register with our API server and the app sends along little bits of goodies. I ignore those, other than a "Buy a legitimate copy and I'll be more than happy to help you." The other 2/3's are crashes from jailbroken devices. Directly caused by SBSettings. In fact, having the users go in and…
Fair enough, but I'd point out that I've had a jailbroken phone for quite a while, installed and played with thousands of apps, and never experienced one "crash". What's the difference? Simple, I only installed tried and tested apps, even from Cydia.
Jailbreaking the phone is simply not inherently more unstable. It's like anything else, if you install unstable stuff, you get unstable results. SBSettings is perfectly stable and works well, as do most of the simpler addons for it, RotationInhibitor being one of these. But quality of JB apps varies, and there certainly are a lot of unstable ones out there.
So before you go blaming jailbreaking itself, I'd investigate to see what specific apps are interfering with your app, and see what the issue is. Because a jailbroken phone is certainly not inherently more unstable. It's the unstable addons are the problem, but people are stupid and will install any old thing, no matter how crap quality it might be.