I need help. 2 days ago that I have a problem with the buttons of Shield
They work parcially
Nvidia Button: Rather than launching Shield Hub, it makes Shield sleep (but i can shut down and reboot)
Home button doesn't works (No multitask, no Google Now)
Back button: Sometimes works, sometimes doesn't
Pause button: Only for Game Mapper
Luckly, A,B,X,Y, joysticks, d-pad, bumpers and triggers, work perfectly
I tried to do a wipe but when I enter recovery mode, i get a message that says "Any command". Anyway, i did a hard reset by the System configurations (and not be solved)
Someone more it has happened this? How i can solve it?
Sorry for my bad English, i'm using my poor knowledge of English and a translator
Thanks!
Related
I have tried a number of different jblend and jbed versions to launch java games on my touch dual. Almost all of them either produced errors, didnt launch or install the java files. I finally found one that worked which was a version of jbed called JRebeiro Esmertec Jbed which has a build ID: 20071119.3.1. This one launched all the java files perfectly.....
However, the only problem now is that I can't use the soft keys! I can use the D-pad and the keypad (numbers) to navigate through the menus, but the left/right soft keys don't work. For example, if I run Need for speed pro street, the first option is whether or not to enable sound. The 'yes' and 'no' icons show, but I cant select either soft key so I cant continue!!
I tried searching the forum and read through the whole 'midlet bible' thing but didnt find anything conclusive!
Does anyone know a solution? or even a midlet manager that has the soft keys working?
fl4r3 said:
I have tried a number of different jblend and jbed versions to launch java games on my touch dual. Almost all of them either produced errors, didnt launch or install the java files. I finally found one that worked which was a version of jbed called JRebeiro Esmertec Jbed which has a build ID: 20071119.3.1. This one launched all the java files perfectly.....
However, the only problem now is that I can't use the soft keys! I can use the D-pad and the keypad (numbers) to navigate through the menus, but the left/right soft keys don't work. For example, if I run Need for speed pro street, the first option is whether or not to enable sound. The 'yes' and 'no' icons show, but I cant select either soft key so I cant continue!!
I tried searching the forum and read through the whole 'midlet bible' thing but didnt find anything conclusive!
Does anyone know a solution? or even a midlet manager that has the soft keys working?
Click to expand...
Click to collapse
Strange, in my 3.1 copy (did you use the same as me? http://www.winmobiletech.com/092007MidletBible/JRebeiro_EsmertecJbed_20071119.3.1.zip ) works just great on my (several) Pocket PC's.
If it doesn't work at all, get Cloudyfa's 2.1: http://www.winmobiletech.com/092007MidletBible/Jbed.zip
First of all, thanks for the reply.
I had the same versions as you just showed and I had also previously tried Cloudyfa's version too. I tried out the ones you posted anyway just to be safe but I had the same problem on both...no soft keys. (BTW, The soft key buttons on screen work in the Jbed main screen, its just when I launch a java game that I cant select or use the soft keys).
What buttons do you use as the soft keys?
The only buttons left on my touch dual apart from the number pad is the start and end call buttons, the navigation/D pad, the volume up and down keys and the camera button. Only the navigation/d-pad buttons seem to when I launch a game in Jbed, but the other keys function as normal (if i press the call button, the phone dialer appears, or if i press the camera button, it launches the camera).
So are the soft key buttons on the touchscreen (icons shown on the touchscreen) meant to work? Or is the touch dual lacking the necessary buttons?
fl4r3 said:
First of all, thanks for the reply.
I had the same versions as you just showed and I had also previously tried Cloudyfa's version too. I tried out the ones you posted anyway just to be safe but I had the same problem on both...no soft keys. (BTW, The soft key buttons on screen work in the Jbed main screen, its just when I launch a java game that I cant select or use the soft keys).
What buttons do you use as the soft keys?
The only buttons left on my touch dual apart from the number pad is the start and end call buttons, the navigation/D pad, the volume up and down keys and the camera button. Only the navigation/d-pad buttons seem to when I launch a game in Jbed, but the other keys function as normal (if i press the call button, the phone dialer appears, or if i press the camera button, it launches the camera).
So are the soft key buttons on the touchscreen (icons shown on the touchscreen) meant to work? Or is the touch dual lacking the necessary buttons?
Click to expand...
Click to collapse
oic. I've always used hardware buttons; no wonder in-game softkeys don't work (they aren't supposed to).
use a button redefiner; for example, AEBPlus, to map left/right softkey functionality to the existing buttons (for example, Camera)
Thanks for that. I finally solved it!
I went and got AEBplus like you said and I noticed it showed the left and right soft keys eventhough there arent any on the touch dual. Then I went to check the actual buttons option in the windows setting tab and found that I can map some of the shortcut buttons as left/right soft keys! Everything works perfectly now. Just got to find the right buttons to map the left/right soft keys.
Finally solved that problem! I'm surprised no one mentioned this anywhere else.....probably because its a touch dual specific problem.
other jbed issue
i haven't had any problems with softkeys but i am having an issue with sound. if i dont disable sound the program crashes. i've tried several versions of jbed. im using moto q. any suggestions or fixes?
goodst0ry said:
i haven't had any problems with softkeys but i am having an issue with sound. if i dont disable sound the program crashes. i've tried several versions of jbed. im using moto q. any suggestions or fixes?
Click to expand...
Click to collapse
must be a moto q-specific issue - i haven't encountered anything like this on my Smartphones
Vibration Jbed Dont work
How to assign numpad values to play java games?
some games like gangster and prince of persia needs the nampad values 0 and 1 etc., how can it played in jbed in ppc wm5(dopod 818 pro 195mhz omap processor full touch and no qwerty keyboard)
please help me ... adavance thanks...
I've been pretty happy with this phone, especially since I got WM6 on it but I'd like to be able to use Morphgear as an emulator. When I do, I like to use it in "west" orientation with my left thumb on the control pad and my two main buttons as Button 1 (the "mail" button) and Button 5 (the "comm manager" button) so I can press them at the same time with my thumb on 1 and my index finger on 5. When I try to map the buttons that way in Morphgear, it calls Button 5 Button 6 instead and it doesn't work in game. I thought it might be a Morphgear issue but I've tried it with other emulators and it doesn't work in them either. Why is that? Is there any way to correct it? Another annoying issue is that whenever I accidentally press the center of the control pad and Button 1 at the same time it wants to align the screen.
Any help?
evilwise said:
...Another annoying issue is that whenever I accidentally press the center of the control pad and Button 1 at the same time it wants to align the screen.
Any help?
Click to expand...
Click to collapse
that combination is probably a built in feature to pull up the align screen program for your device, and i am pretty sure can be removed by tweaking the reg. settings that correspond to the short cut.
You should post your issue under the tnt rom thread to avoid creating redundant threads.
cheers
try vjcalibrula .
it may turn calibration combo off... it works on wizard, at last..
So I've got PocketGBA installed, and it runs much smoother than Morphgear. The problem is, that when you set it to run in landscape, which is known as "vertical" mode for some reason, the screen is upside down. So you'd have the keyboard out, but the games run upside down.
Is there anyway to fix this, or a program to set screen orientation temporarily or whatever?
Thanks
I actually just play it that way, leaving the keyboard slid out on the top and assigning the keys.
Assigning keys this way is wierd, because with the keyboard open the onscreen buttons are off. So what I do, is with the keyboard closed... select your first key to assign, then slide the keyboard open and press a button.
You should see the button press take. To continue, close the phone then select another onscreen button to assign, open keyboard and press the selected physical button to map it.
Do this for all the required button assignments, opening and closing the keyboard each time. Once your done you shouldn't have to do it anymore.
Then just play with the keyboard open, with the screen facing you.
A fix would be nice though, but I don't know if the author of PocketGBA is still around or is the source is even available any more. It seems that there isn't an interest in working emulators for PocketPCs anymore. The ones we have are YEARS old and are bug prone. Finding the right Emulator is finding one that has bugs you can live with.
http://forum.xda-developers.com/showthread.php?t=427805
I don't think that will work. It is the PocketGBA software that rotates the screen. Even if you forced the screen to display the orientation correctly, I think the program will have all the touchscreen interface offset (just like what happens when you open the keyboard). I will try it though.
Hi I was just wondering if anybody has had this problem before on a huawei u8350 or other android on froyo 2.2.2 or other. The phone is rooted When I press a key, any key including menu, home, back and all the letters numbers etc I get the same input as that key on any other key pressed after it. I think it was mainly/only 1 repeat but sometimes maybe more. So if i pressed A then B it would enter AA then AAB if B was pressed again. This also applied to the thumb controller. I have recently used some non market app's VGBA ( a gameboy advanced emulator packaged with lucky patch), FPSE ( PSONE emulator) I don't know if that has anything to do with the problem. I ran an avast virus scan, nothing detected and I don't think it could be a hardware problem as I have tried using various input options and the problem remained until I rebooted the phone. Seems fine now but I was just curious as to what might have caused this???? Thanks in advance
Is there any way to force a menu button entry? Many older programs such as Scumm Vm do not have on-screen menus of any kind of rely on the button.
How can I play Full Throttle now!?!?!?! Good god the calamity.
bonapartist said:
Is there any way to force a menu button entry? Many older programs such as Scumm Vm do not have on-screen menus of any kind of rely on the button.
How can I play Full Throttle now!?!?!?! Good god the calamity.
Click to expand...
Click to collapse
'Y' should be acting as a menu button. Unless ScummVM maps it to something else, it should bring the menu up.
Gnurou said:
'Y' should be acting as a menu button. Unless ScummVM maps it to something else, it should bring the menu up.
Click to expand...
Click to collapse
AFAIK ScummVM is a derelict project - fully functioning and fully featured but no longer updated. It will likely never have anyone tailoring Shield support for it. So I have no way whatsoever to access the menu once in game, and hence no way to save or load, making most games essentially fruitless to play given their nature as long graphic adventures. I think the exclusion of a menu button is a bummer and a deficiency. They could of coded so a double press of the Nvidia button registers as a menu press, or something akin to that; knowing how cool Nvidia is, I imagine they'll either add this in, or their openness about the Shield will allow a custom rom to force it in... Still, it's a bummer right now that ScummVM is essentially "broken" on the Shield. 15+ years of superb graphic adventures.. Nuts.
I know the menu button is no longer a requirement on Android devices, but I for one am very sorry to see it go, even outside of implications for old Android applications that do not get freqeuent updates such as ScummVM.
Also the lack of a menu button means I can't bring up the keyboard at will in apps such as Dosbox! That's a huge problem! Being able to bring up the keyboard whenever you want was useful in many, many applications, I don't know why they would ever eliminate that.
I've yet to try SCUMM on the shield but there isn't a way to bring it up by swiping the screen?
On Dosbox, the keyboard can be brought up by swiping down from the top of the screen. Maybe it can be done somehow with ScUMM.
saiyan23 said:
I've yet to try SCUMM on the shield but there isn't a way to bring it up by swiping the screen?
On Dosbox, the keyboard can be brought up by swiping down from the top of the screen. Maybe it can be done somehow with ScUMM.
Click to expand...
Click to collapse
Is there an App like Button savior which has a menu button?? I use that app on my nook tablet which only has one button but I don't recall there being a menu button
If you're rooted you can use tincore keymapper and make whatever button you want into the menu button. Just run it when you run the emulator.
"Home 2 shortcut" could also work. Like someone above said it could assign menu to double tap of the home button. I've not tried it on the shield though. Though I'm not sure it can be used like this...It might only work to launch apps.
My FIrsthand Solution
bonapartist said:
Is there any way to force a menu button entry? Many older programs such as Scumm Vm do not have on-screen menus of any kind of rely on the button.
How can I play Full Throttle now!?!?!?! Good god the calamity.
Click to expand...
Click to collapse
I know this is an old post, but it came up on google when I was trying to resolve this problem myself. I decided to sign up and post the solution I found incase someone else searches the web trying to fix this problem.
I'm using the Nvidia Shield, but i believe this Build of ScummVM resolves problems for a lot of Android Devices:
google: ScummVm svn55436 1-1-0-7 (I Can't post links as a new user)
This is a stand-alone version of ScummVm, it offers an onscreen keyboard, as well as the ability to map buttons--resolving the issue of accessing a menu to save/load your game progress
Here is what I did using Nvidia Shield:
1. unistalled any Scumm apps I had
2. Using the chrome browser I went to: H TTP anddev.at.ua/load/scummvm_svn55436/1-1-0-7 (OR) google: ScummVM svn55436 1-1-0-7 (Again, I Can't post links as a new user)
the download link is at the top of the post
3. I went to settings>security> Check "Unknown Sources" UnCheck "Verify apps"
(This prevents Android from blocking installation switch these settings back after step 4.)
4. I then went to apps>downloads> and clicked "7_scummvm-sdl-1.7.apk" to install it
5. once installed I opened the program, I spent sometime configuring things in a trial by error fashion
Here's my configuration settings to my best recollection:
1. Video Settings> Check--Keep 4:3 screen aspect ratio
2. Mouse Emulation> Calibrate Touchscreen
3.Remap Physical Keys> (I pressed the "left shoulder" button on my gamepad)> Select Action> (scroll down) Show all Keycodes> then select "F5" <<<<This Lets you access the menu so you can SAVE/LOAD!!!!!
Were you able to use the analog stick to control the cursor? Mine acts very erratic. I followed your instructions and scumm works fine but I just that issue.
saiyan23 said:
Were you able to use the analog stick to control the cursor? Mine acts very erratic. I followed your instructions and scumm works fine but I just that issue.
Click to expand...
Click to collapse
I've been able to get by just fine using the touchscreen. The joystick is a little funky on me too, any movement tends to send the cursor drifting offscreen.
The guy who did this build, I believe, designed it for android devices in general and not specifically for the Shield, so if you want the analog joystick working you might be s-o-l.
I have to say though, the touchscreen is working pretty good for me--I'd give it shot and try to get used to it.