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
Having some issues with my desire hd when playing games that involve movement and i'm unable to find an answer in any previous topics.
when playing a game that involves movement and pressing an action button at the same time the controls become unresponsive. the simple example is playing super mario world and being unable to run. i can walk using one direction button but as soon as you hold the run button or attempt to jump at the same time you have to resort to pressing the direction button over and over to be able to move again.
i've tried restarting the apps, tried various types of apps from 2d platformers to 3d emulators and the same problem applies.
re calibration seemed to help only slightly and re installing apps also does not work.
any insight would be greatly appreciated, so many good games that i'm unable to play with this problem.
[Q] Flickering Problem when running my game
Hello all,
Recently i am developing a game. While testing on my galaxy S3 i noticed that sometimes the home screens and app pages flicker when sliding through pages and even swiping the notification bar down.
The funny thing, it doesnt happen every time i play the game, but it happens some times. To get rid of the problem i have to open my game again or any other app and then exit out of it and the flickering will stop.
Ive tried and tested just about ALL of my code. There doesnt seem to be any major issues or memory problems. I am also cleaning up properly when exiting my game, and destroying objects and even stoping my game engine.
At this point i am beginning to think it is a bug in the Android OS or something. My device is running Android 4.1.1 Jelly Bean. Ive had many others beta test the game on some cheaper and lower end devices and they dont have the problem. And of course not on tablets.
What do you guys think? Has anyone else encountered this issue?
Coder
Hi Everyone,
I recently purchased a 2014 Note 10.1, primarily for gaming. It's still bone stock, updated to the latest US firmware (MK1). I am experiencing an issue with the touchscreen. In games such as Asphalt 7, Riptide & Mini Motor, if I set them for manual acceleration with an on-screen pedal, the pedal works intermittently. For instance, if I start a new game in any of the above titles, the pedal works for maybe the first 10 seconds and even with finger still on it, the on-screen pedal just deactivates at some random point. If you go to press the on-screen pedal again, it may or may not engage immediately - and if it does, it will disengage again at some point. It will do this throughout the game making them impossible to play well. At first I thought it was a problem with Asphalt 7, but the same exact thing happens in Riptide and Mini Motor. So now I'm wondering if my brand new Note has a touchscreen issue or if this is problem that other people can reproduce.
Could anyone please let me know if this exact same behavior happens to you? I really don't want to have to return this tablet if its just a driver issue.
Please let me know, thanks.
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.