I have an iPega 9025. I haven't used it in a while, and wanted to try it with a new phone (LG G7). When I hooked it up last night I got strange behavior. In gamepad mode (Home + X), the buttons work, but the sticks and triggers (that should show up as axes) seem to drop out intermittently. They worked for a bit, then stopped.
I visited https://html5gamepad.com/ and all the regular buttons work but the analog sticks were not showing any movement. I happened to move a stick while scrolling the screen, and it registered. I tested some more and confirmed, all 6 axes (2 sticks plus 2 triggers) registered movement but only when I had a finger on the touchscreen (!).
I've tried forgetting the controller and connecting it again, but I can't get the sticks to show up reliably. Has anybody had an issue like this before? I've read about people flashing new firmware, would that help? I couldn't find any information about firmware on iPega's website.
Found on another post: there's a reset button on the back of the controller. 5 seconds with a paper clip, delete pairing on the phone, pair again, and it works perfectly. No idea what went wrong.
Related
I have no problem connecting to my LG phone which is running Android 4.1.2 but for the life of me I cannot get my Note 10.1 2014 to connect or even see my wedge mouse. Any ideas?
Mickeylittle said:
I have no problem connecting to my LG phone which is running Android 4.1.2 but for the life of me I cannot get my Note 10.1 2014 to connect or even see my wedge mouse. Any ideas?
Click to expand...
Click to collapse
I was able to get mine successfully paired and working. Just got my new Note 10.1 today.
In the bluetooth setting, making sure I check-marked "make device discoverable" I flipped my Wedge over, pressed the power button once until it lit steady blue, then held it down until it went into pairing mode, then I hit 'Scan' on the Note and in seconds it found the Wedge mouse.
Perfect!
dlg_dlg said:
I was able to get mine successfully paired and working. Just got my new Note 10.1 today.
In the bluetooth setting, making sure I check-marked "make device discoverable" I flipped my Wedge over, pressed the power button once until it lit steady blue, then held it down until it went into pairing mode, then I hit 'Scan' on the Note and in seconds it found the Wedge mouse.
Click to expand...
Click to collapse
Perfect.... I should have read the directions! Thanks!!!:victory:
You're welcome. I've missed that little gem of "make device discoverable" myself in the past and learned my lesson from it.
Mickeylittle said:
Perfect.... I should have read the directions! Thanks!!!:victory:
Click to expand...
Click to collapse
Yeah....reading the directions sucks. Lol... it's like asking for directions on the road.
...Sent from my Tablet...Please excuse any typo's...
dlg_dlg said:
You're welcome. I've missed that little gem of "make device discoverable" myself in the past and learned my lesson from it.
Click to expand...
Click to collapse
I made the device discoverable. The problem I had was the 1-2 punch of (1) turning the mouse on & (2) then pressing and holding to get it into pairing mode. I guess I got lucky when I was messing with it on my phone and got it paired.
Mickeylittle said:
I made the device discoverable. The problem I had was the 1-2 punch of (1) turning the mouse on & (2) then pressing and holding to get it into pairing mode. I guess I got lucky when I was messing with it on my phone and got it paired.
Click to expand...
Click to collapse
Ah, you are far better than I. Some products default to discoverable mode, others not. It took me several tries on some devices to realize I had to put it in discoverable mode myself - basically, not paying attention to the screen text - and I found most fam/friends did the same, so I assumed that was the issue. Nonetheless, the connection button actions ... it took me three attempts to figure that one out
But tell me, do you find the cursor movement erratic with the Wedge on the Note 10.1 (2014)? Mine seems to be jerky quite often, sluggish to perform a movement.
dlg_dlg said:
Ah, you are far better than I. Some products default to discoverable mode, others not. It took me several tries on some devices to realize I had to put it in discoverable mode myself - basically, not paying attention to the screen text - and I found most fam/friends did the same, so I assumed that was the issue. Nonetheless, the connection button actions ... it took me three attempts to figure that one out
But tell me, do you find the cursor movement erratic with the Wedge on the Note 10.1 (2014)? Mine seems to be jerky quite often, sluggish to perform a movement.
Click to expand...
Click to collapse
So far it is jerky. I'm not too sure how much I will use it since the sPen does mostly the same thing anyway. Overall I'm very happy with the tablet but maybe when/if we get all 8 cores up and going or once we get our tablets fine tuned just like we want them, things will settle into place.
For those of you that have it working, what does the right-click on your mouse do? I have a note 10 (2012 version) and will probably be upgrading to the 10 or 12. I have one major problem using my note as a work terminal connecting to a citrix session: The right mouse button acts as a 'back' command in anything, including within the citrix session. I have another, older samsung 10" tab and the right click is ignored at the OS level, but within Citrix it works as expected. I believe the OS is applying a default behavior of a 'back' function to any right click on the later device(s) and am wondering if anyone here has any input on it's behavior in the latest devices.
Thanks for any input
Like it says up top, but it's relatively new. Of course I tried new batteries. I had been using the originals from when I bought it in late March. All I was doing was syncing mysql to the stick and I needed a mouse to move some stuff around in ES file explorer (got side tracked actually and installed task manager to clear the cache) so I installed WuKong remote. It was then I noticed some serious lag--takes about 10 seconds or less on fire tv console to clear cache. This took about a minute at least then it just froze in the app, couldn't press home. Tried 3 sets of new batteries but nothing worked.
BTW--this new faster screen timeout on aftv is all the more annoying when you're trying to do something like update a library because if I leave for a couple of minutes I need to reboot since neither Yatse nor wukong were able to wake up the display BUT you can still hear the clicks.
I don't mean to go on but something tells me this is more than just a remote control issue. I thought if anyone had a similar experience they might be of some help. Thanks.
Did you try to pair the remote again? Press the home button for 5-10 seconds after powerup.
Calibaan said:
Did you try to pair the remote again? Press the home button for 5-10 seconds after powerup.
Click to expand...
Click to collapse
Yes. A few times with different batteries, but it just won't pair. I might try a factory reset. If I had to pin point it it would've died when i first started using wukong app. I've used that on other devices with no issues but that's the only thing i did differently last night. I'll probably do a factory reset and if that don't work call amazon.
You could try the Android phone remote app for calling the pairing function from menu. Probably this does the trick.
Calibaan said:
You could try the Android phone remote app for calling the pairing function from menu. Probably this does the trick.
Click to expand...
Click to collapse
And had I caught your post a bit earlier...I may have lol.
I still have no idea the root cause but a factory reset did the trick. The remote responded immediately (actually a lot faster then when i wipe my rooted atvs.) I wonder if the wukong remote somehow highjacked it?) Just remember the reason i installed it was to be able to mouse click "show hidden" on ES file explorer. The stupid part is I now know there's another way to accomplish this without a mouse by going into the app's settings. No big deal. Thanks for the help!
This has happened to me thrice in one week. This on a rooted FTV, not stick. Three times, the remote just died. Changed batteries, but no joy. The first time, a simple reboot fixed it. The second time, I had to use the FTV app on my iPhone to un-pair and re-pair it. The third time, the reboot did the trick. Not sure what happened. Since then (around a month back), no issues. No change in firmware/apps/any sort of configuration on FTV (or any new devices in the house) before the problem or after the problem. The problem came for a week and then simply went away.
I don't have the Wukong app installed. I have one another FTV in my bedroom and made sure that the problem remote did not somehow got paired to it, and it wasn't. I need to read up on BT interference, that seems to be my wild and ignorant guess. Or some hardware within the remote is going bad... But, I am not sure about that reason, the remote is used everyday and works fine since the mishap.
Today while watching a video via my AFTV, the whole thing just locked up on me. Had to remove the power cord to reboot it. After it rebooted I noticed that my controller wasn't doing anything, and the same with my amazon game controller. But my logitech K400 worked. So I go to settings because I know for a fact the batteries aren't bad. Put in some new one on the remote first thing and you can see the led light up on the controller. Anyways, in Settings it said my controllers were paired, but said Battery, like the batterys were dead. So I used my keyboard to unpair my gamepad. Then I had no problem pairing it up and controlling stuff, so I did the same with my remote and boom, now it works.
tl;dr Check settings, if it says just Battery on the controller, unpair it, and then pair it again.
Can some one help my fire stick controller it's working correctly it goes up & down but it won't go on the mouse bit to click on the show box films I want to watch I'm new to all this technology stuff lol
fire sitck dead
I had my firestick for a week and used it, maybe four times. Went to use it again and it would not come on, no LED light, nothing. I changed the batteries, several sets of new ones. Nothing. I am not a tech guru, so if you have some ideas for me, dumb them down.
Oh, and I tried the new batteries in another remote and they work fine.
Had the same problem too... I had to hold down the Home button while being 4inches away from the receiver before it synced
i've had no luck with my firestick remote, i connected the firestick to my tv but the firestick remote won't sync with the firestick so now i'm stuck at the first screen, i've tried changing the batteries for new ones, cleaning the remote's battery contacts, plugging and unplugging the firestick from the tv and the electrical outlet. I've also plugged the firestick to a brand new tv and still can't find the remote. I've remove the batteries for 2 hours and tried again to sync it to the firestick and no luck. rebooted my router several times, put the remote next to the firestick to see it would sync and still no luck, changed hdmi ports and nothing, went to a friend's house and not working there either. called amazon to be sent a replacement firestick and remote, they sent both and still the same problem. I would like to factory reset the firestick but i don't know how since i can't use the phone app or the remote. I'm at the very first screen where it asks you to press the home button so it can find the remote. btw, i've also did the hold 3 button remote reset and didnt work either. i have the firestick with voice first generation, i had kodi installed so i don't know if that means it was rooted or not.... Any suggestions on what else i can do to pair it would be greatly appreciated.
TL;DR firestick with voice remote won't sync no matter what and need help with syncing.
If you are still having this trouble it is because your firestick does not recognize that the tv is on. It's doing that because it is plugged into the wall. If you unplug the USB part of the plug from the wall and plug it into your USB slot on your tv it will solve the problem. Switched mine over and it hasn't happened since.
TommyCallahan said:
If you are still having this trouble it is because your firestick does not recognize that the tv is on. It's doing that because it is plugged into the wall. If you unplug the USB part of the plug from the wall and plug it into your USB slot on your tv it will solve the problem. Switched mine over and it hasn't happened since.
Click to expand...
Click to collapse
That makes absolutely no sense at all.
@nachumama So you have a new FireTV Stick and a new remote and it still doesn't work? Two separate sets of stick+remote and none of them works on your TV or the one at your friend's house? That's not good.
FireStick remote not working properly
My Firesticktv remote was working very slowly. I would hit a button on the remote and nothing would happen for about 30 seconds. I changed the batteries(no change). I fixed it by going to Settings- Network- whatever network it says you are connected to. hit the Forget this network, Then connect to the next network on your router. It was my 2.4GHz channel. For some reason my channel was changed and was on my 5GHz channel, It didn't work on the 5GHz channel. The remote works like new again
my firestick is not working tried very thing that other people has tried what to do next
Fire Tv Stick remote suddenly stopped working issue or Amazon Fire Stick not working issue usualy occured due to Inadequate Power Supply, Damage Fire Stick’s remote batteries, Outdated Software, Corrupted Fire Stick Cache, and Overheating of Fire Stick devices.
However, there is some workaround solutions available on the web 'https://techsmagic.com/how-to-fix-amazon-fire-stick-not-working-after-update-reset' page detailing it. Here is the solution:
Method 1: Restart your Fire Stick
Method 2: Check your Internet Connection
Method 3: Update FireStick Software
Method 4: Clear the Fire Stick Cache
Method 5: Reset your Fire Stick to Factory Settings
If you have some other and better solutions to fix this issue, must share with me. Thanks
Got the new controller for the Shield Pro 2015 edition. Great form factor, much better than the original. However, it cannot be used with the 2015 unit yet. Problem is when you take it out of box and turn it on, it immediately goes into pairing mode, the unit detects it but when you try to push an action key on the controller to accept the new controller on the pairing screen, it will not respond. Then it will finally go back to main screen only to endlessly repeat the pairing screen. There is no light on the power key anymore so there is no way to tell if the thing is on or off. Also, long pressing the gamepads on button will not stop the repeating of the pairing signal. Called Nvidia, they said this is normal but it should work as a normal controller for now, until update/ if plugged into unit via USB. No go there either. There is not indicator other than when you first plug in a power cable and it vibrates to let you know that it's getting power but no indicator light to tell you when it is fully charged. I had to put it back in the box and move into another room far away from shield unit just to be able to stop it from trying to pair every two minutes or so. Anyone else have any success with this. I'm thinking the controller may be a defective one.
Found solution in another blog: I got the new controller for the 2015 shield pro and found out the hard way that it doesn't quite work as it's supposed to yet. However instead of "adding shield accessory" (which continuously found it but failed to pair it) I was able to "add a Bluetooth device" and it paired and works perfectly. For anyone else that may have jumped the gun on the new controller with the older system.
It works fantastic.
I think you need the new 5.0 update, that hopefully coming soon.
I have a Moto z play on Android Oreo. I just ordered a new Moto mod gamepad. I connect it to the back of my device and it recognises it as it pops up with the screen first time and says 100% battery for the gamepad. I go through the Moto gamepad and install and open a compatible game and when it opens it doesn't detected any button inputs.
I have tried this on more than 5 games. I also am unable to move through my icons on the home screen like other people have shown in videos.
I originally got the gamepad on 7.1.1 and it didn't work. Tried factory resetting and still didn't fix so figured it was a defective unit. I am now on Oreo and just received the new one and it does the same thing.
I have tried clear the apps data and cache. Restarting the phone. Charging the gamepad in case it's low and also disconnecting and reconnecting the gamepad.
I am totally lost as to what to do. It's technically possible I received two broken units but more likely I am making a very dumb mistake.
Please help.
stigmatised1 said:
I have a Moto z play on Android Oreo. I just ordered a new Moto mod gamepad. I connect it to the back of my device and it recognises it as it pops up with the screen first time and says 100% battery for the gamepad. I go through the Moto gamepad and install and open a compatible game and when it opens it doesn't detected any button inputs.
I have tried this on more than 5 games. I also am unable to move through my icons on the home screen like other people have shown in videos.
I originally got the gamepad on 7.1.1 and it didn't work. Tried factory resetting and still didn't fix so figured it was a defective unit. I am now on Oreo and just received the new one and it does the same thing.
I have tried clear the apps data and cache. Restarting the phone. Charging the gamepad in case it's low and also disconnecting and reconnecting the gamepad.
I am totally lost as to what to do. It's technically possible I received two broken units but more likely I am making a very dumb mistake.
Please help.
Click to expand...
Click to collapse
Probably it's hardware problem with pinout on your Moto. Do you have friend with phone from Moto Z series? That would be easiest way to check gamepad.
Device is a PX5 fitted for an MB SLK (with extra hardware Buttons, CAN-BUS, etc), Android 9.
I think someone posted something similar before, I'm also in contact with the producer (Witson):
First the tl;dr - Touchscreen didnt work temporarily, then permanently, now not in some areas.
Now the details:
~2 Weeks ago: Touchscreen suddenly didn't respond, I rebooted the device, worked fine again
~1 Week ago: Touchscreen was acting "on its own" sometimes making presses I didnt make, so songs switched etc. maybe was also only dirt, but didn't seem like it, only reboot helped
~2 days ago: Drive to supermarket, everything works fine, come back, screen doesn't react anymore. AT ALL. Tried to reboot, still doesn't work. Tried to boot into recovery, even there the screen doesn't work(tapping gestures, long press).
So I wrote Witson and simultaneously googled for issues like that with Android Head Units, read sth about calibrating the screen or holding reset+power button... last thing didnt work.
Smarta** that I am, I connected a mouse to the device, system was working fine with that, so I could still somehow use everything, so definatley sth with the touchpanel
Then came the answer from Witson, they sent a video on how the recalibrate, so I did:
Go into Factory Settings > Enter 126 > Touch Panel Calibration (or sth like that) .... 2 crosses in the corners of the screen, no reaction .. i think i also tried to use "Reset Touch" but also didn't work.. BUT I didn't reboot afterwards.
Now the fun begins: After work, go to the car, Head Unit starts, I dont even try touching until after 3 minutes and as I try suddenly the screen reacts! But after some time of driving, it stopped working again.
Back home, reboot, touch works for ~1min then stops again.
Boot into recovery, Wipe/Factory reset, Screen reacts PARTLY after that, like around the middle it doesn't seem to react... Factory Settings for Calibration again, want to enter the 126, but that row on the keyboard doesn't react. All the others do (even though sometimes laggy), Mouse again, enter code, go to calibration, touch works this time! Calibrate, apply, reboot. But still sometimes the Settings itself don't react all the time, when I wnat to enter WiFi Password, again, upper row of the keyboard doesn't react, rest of the keyboard does.
WHAT is going on!? Faulty Hardware? Software? "Driver"?
I also have a video of me trying to enter stuff on the keyboard, if someone needs it.
Suggest to send it back or demand warranty replacement for these poor lack of Quality Control knock off head units.
All you will get posting here are guesses.