Can someone else confirm that the physical keyboard keys get disabled when making flash games go full screen? I was just trying to play a few that I knew had wasd controls and as soon as I would maximize the game to full screen, the keyboard wouldn't work in game anymore. If I left it minimized in the browser, it worked fine...
Anyone else notice this?
i played kitten cannon the other day on addictinggames and i was able to use the space bar just fine to launch the cat even in full screen mode
hmm, it may have been the games I was playing then. I'll try some at addicting games instead and see if I still have issues.
Thanks!
The FPSE forum seems to be moving at a pretty slow pace so I'm hopeful that I may be able to find some assistance here more quickly.
For a while I've had the FPSE Playstation emulator on my Samsung Epic 4G Touch and it has worked pretty well for me thus far. I have recently decided to try getting Final Fantasy VII to work and the game will start up as normal bringing me to the opening credits video. This is where my problem becomes apparent. Any key input doesn't get registered. If anything messing around with the settings has only made it worse as originally the screen would still vibrate when pressed, but now it doesn't even do that. (For other games the vibration seems to be missing now regardless of the feedback setting, though key input is still registered.) As a result I'm left unable to reach the screen where you start a new game as the opening video will continue to loop until any key input is registered. Essentially the game is unplayable while this issue persists. Any help would be greatly appreciated.
Ive played that game not to long ago but stopped because when tifa gets her "break" skill the game goes like 1 fps so i gave up afterwards. But from what ur experiencing maybe its fpse update ? I havent tried it since ive stopped but i know fpse has been updating.
Sent from my SPH-D710 using xda app-developers app
Sorry friend, this sounds more like a App problem so you probably aren't going to be able to get much help here. Have you tried emailing the developer?
I'm experiencing this strange glitch with at least the left and right buttons of the D-pad. They don't respond at all, then they respond, then they don't again annoyingly, by which time I've crashed or died or whatever.
This is only in FPSE and N64oid, I've not experienced it in an Android game, and it's often at similar points in the level I'm playing, which made me think it was a software issue rather than a hardware fault I'd have to send it in to Sony for.
I first experienced it about 3-4 weeks ago. It seemed to be related to .58 enhanced firmware v1, because it went away after I made a fresh flash of .42. It was fine for all of those three weeks, in which I went back to .62, ran ICS, GBXPlay, NXT 1.3 Light, all on different LuPuS kernels, but now it's started happening again, and is still happening whatever nandroid of any of those I restore.
Anyway, has anyone else had this or got an idea what it might be...? I'll hold off reflashing the firmware and starting all over just in case anyone knows what this is...
edit: Hmm. It's happening still on DoomLord's Advanced Stock Kernel for GB .42/.58/.62.
I'm at a total loss now. :crying:
I thought it might be a soft keyboard service interfering with inputs from the D-pad so tried freezing those, no joy... The D-pad freezes up within seconds of playing an actual game on FPSE or N64oid.
Did a complete reflash of 2.3.4 .42 generic firmware with Flashtool, installed FPSE even without rooting or doing anything and the D-pad is still locking up.
The problem is I don't see how sending it in would get it fixed, because it just seems to be a problem with emulators. It works fine on every Android game and would no doubt work fine in the service menu too... they'd just send it back to me.
Gamepad is OK: GTA 3, Blazing Star, Asphalt 7, Super Crate Box.
Gamepad is weird: FPSE, N64oid, Tiger Arcade.
OK I think I've fixed it: it's physical. I took the battery cover off and replaced it and touch wood the problem seems to have gone away.
I had problems before pressing the power button because of the cover.
I went into the service menu (*#*#7378423#*#*) and tried the Keyboard test. I found if I pressed menu or possibly one of the D-pad keys once it would register repeatedly.
Kind of interesting why it only affected emulators. They may not use the same API as Android games for the gamepad, and read them as generic key presses or something, like the service menu, but if it's a purely physical problem with the battery cover, then I don't understand why that would come into it. Fingers crossed I've fixed it. :cyclops:
Perhaps reflashing only seemed to fix it last time because I might have had a problem that required a battery pull...
I got d pad freez too on fpse, emulator bug
Sent from my R800i using xda app-developers app
in external gamepad select icontrolpad
From time to time I will try and play a game on the OUYA and my controller will look in the menus on both the system and in the game but I can not start a game.
Hard to explain but for an example lets say I want to play the game Ice Rage, well I select the game and it loads But in the game I can only go through the menus. When I select single play or multiplayer I can not actually start the game. I can press back to the previous menu screen and scroll through them but I can not play the game.
This happen s randomly and in multiple games. Ive noticed that once this happens no games will work. I thought maybe I got a bad unit so I went back to the store and exchanged it and it is still happening on this one. Both the OUYA controller and xbox controller has this issue which leads me belive it is not an actuall controller problem but maybe a operating or firmware issue.
Has this been a common problem and is it an easy fix?
So I installed Game Killer recently onto my rooted Nexus 7 and I decided I would try to give myself a bottomless clip on MC4. Now, despite the fact the app was working just fine before the root, it immediately minimizes when I start up now. I click the app and a black screen opens for a couple of milliseconds before the game minimizes back down. I can still see it in the running apps menu but if I try to open it from there it just does the same thing again and again. I've already tried the basic solutions like reinstalling and rebooting my device but that's pretty much all my options.
I know that it's not a crash, seeing as the app is still running. It just doesn't maximize correctly and I can't actually view the game. With that, I've exhausted all my options because I'm not getting any feedback about the error and I can't look at a crash report because it hasn't crashed. I can't find anyone else with this problem either.