Pages:
#1 Re: MFi Controllers » Gamevice for iPhone (2nd gen) impressions » Feb 03 11:47 AM
Hi! I'm an iOS developer and have a developer license, and I also contribute to and maintain various emulators on iOS.
I don't jailbreak my device, and the way I install emulators is that I either:
- Use my developer license to "code-sign" an existing emulator that's already been built (an IPA file), and transfer the IPA file to my iPhone via iTunes or Xcode
- Build the emulator in Xcode and run on my device. Most emulators are open source and have Xcode projects you can open and run.
The easiest way by far is to register as an Apple developer for $99/year. You can build and run emulators on your iOS device using Xcode without being a developer but the profile is only good for 7 days (as opposed to 1 year if you are a developer), and you'd have to reinstall the emulator every 7 days or so. There are services that you can pay for that will add your iOS device under an enterprise license so that your profile is good for 1 year, but this seems a little bit shady.
I can post more detailed instructions later if you're interested. I maintain the MAME port for iOS and have some instructions on how to build it if you're not a developer:
#2 MFi Controllers » Gamevice for iPhone (2nd gen) impressions » Feb 01 4:45 PM
- harakari
- Replies: 5
I'm the original owner of a Gamevice for iPhone, and recently upgraded to the 2nd gen Gamevice for iPhone controller. I got an iPhone 7 Plus last fall, and found that the controller wasn't quite compatible with the bigger 7 Plus. The folks at Gamevice were very nice and receptive when I contacted them, and I got an email asking if I'd like to upgrade to the 2nd gen version for a fair and very generous price of $50. I said yes, and promptly got a FedEx package a few days later.
The biggest improvement, as Kevin mentioned, is the analog sticks. They still could use improvement, as they're not quite up to the level of an Xbox 360 analog, but are miles ahead of the 1st gen flimsy sticks that were near unusable. I played some GTA: San Andreas, Modern Combat 5, Metal Gear Solid: Peacewalker (on the PPSSPP emulator) and Star Fox 64 (on RetroArch) on my iPhone 7 Plus and the difference was quite noticeable.
The unit is a little bit lighter, thanks to the absence of a battery - and it does feel a little more comfortable. And having a Lightning port instead is a godsend, as you no longer have to carry around a micro USB cable for charging.
One issue I found was that sound through the headphone port is very very low - even after turning up the volume to max on the iPhone. It could be because there's no longer enough external power to amplify the sound. It sounds like you'd need to use bluetooth headphones for audio with the controller.
That being said, I feel the Gamevice for iPhone is probably the best portable choice for an mfi controller. Although the experience is slightly awkward, like playing on a ridiculously elongated PSP (on an iPhone 7 Plus), it's better than lugging around an Xbox 360-like controller with a clip attached.
Big props and thanks to the support team at Gamevice for being responsive and allowing me to upgrade to the latest generation.
#3 Re: MFi Controllers » Mfi dropping after ios10 update. Anyone else? » Nov 01 12:04 PM
Issue still exists on 10.1.1 (iPhone 7 Plus, Mad Catz CTRLi).
Testing on 10.2 beta 1 (iPhone 6 Plus) now..
(Update)
10.2 beta 1: Mad Catz CTRLi did not disconnect after ~1 hour. Will test some more later.
(Update 2)
10.2 beta 1: Mad Catz CTRLi did not disconnect after ~3 hours.
I'm going to cautiously declare that it looks like it's fixed in 10.2 😊
#4 Re: MFi Controllers » Mfi dropping after ios10 update. Anyone else? » Oct 25 12:50 PM
iPhone 7 Plus, iOS 10.1 with MadCatz CTRLi here - controller disconnects and becomes unresponsive after about 20-30 mins. Removing the battery and replacing it, and then re-pairing seems to make it work again.
So it looks like 10.1 works better with some controllers (SteelSeries, PXN) but not with MadCatz maybe?
Also have a Gamevice for iPhone which works fine as expected (it's Lightning, not Bluetooth).
Pages: