Hello everyone.
I recently purchased the lg g pad and I'm very satisfied with it, although I encountered this annoying issue...
yesterday I decided to get a USB OTG adapter so I could play games with my official xbox 360 controller, specially GTA series and emulators. But, for my surprise, it didn't quite work as I expected, with random button pressing and blinking xbox logo button all the time. It was impossible to play :/
I already tested both the cable and my controller on my friends motorola xoom and worked quite well with GTA vice city.
I would like to know if anyone has ever had this issue or if my tablet may be defective and I need to replace it.
By the way, I tried to use the cable to open a pen drive on the g pad and it worked flawlessly. I got official 4.4.2 stock ROM installed via OTA, unrooted and factory locked.
Thanks for your support
Im running mahdi rom and dont have your issue when running my wired 360 or knock off ps3 controller. Does it happen after a fixed time, i never play for more than 10-15 min.
nightanole said:
Im running mahdi rom and dont have your issue when running my wired 360 or knock off ps3 controller. Does it happen after a fixed time, i never play for more than 10-15 min.
Click to expand...
Click to collapse
Thank you for your reply =) No, it happens as soon as I plug in the controller. Have you ever tried playing on the stock ROM?
EDIT: I'll try flashing mahdi rom, depending on result I'll return it to warranty after restock, will report ASAP
JoaoGuiPan said:
Thank you for your reply =) No, it happens as soon as I plug in the controller. Have you ever tried playing on the stock ROM?
EDIT: I'll try flashing mahdi rom, depending on result I'll return it to warranty after restock, will report ASAP
Click to expand...
Click to collapse
http://www.amazon.com/CNE93775-T-Flash-Adapter-GT-i9100-GT-N7000/dp/B005FUNYSA
This it the otg i use. I guess my htc one x is picky on which one, so i just plugged it into my gpad and crossed my fingers. I never used the stock version sorry.
nightanole2661 said:
http://www.amazon.com/CNE93775-T-Flash-Adapter-GT-i9100-GT-N7000/dp/B005FUNYSA
This it the otg i use. I guess my htc one x is picky on which one, so i just plugged it into my gpad and crossed my fingers. I never used the stock version sorry.
Click to expand...
Click to collapse
Nice =] I have another brand, but also generic otg. I hope this is a stock rom driver issue and not a hardware one =/ It's always a pain to deal with warranty stuff
EDIT: I just installed Mahdi ROM, it didn't work I think I'll have to replace my tablet... Damn it :/
Related
Any one else having trouble with HDMI re-booting? Every time I plug in my hdmi cable to my tv the phone freezes and then reboots, tried stock rom and rooted damagecontrol rom both with the same issue...
No real experience here myself, but from what I've read some TVs work better than others, and some have a problem handshaking with the TV. Have you tried it on a different TV/monitor?
CentroniX said:
No real experience here myself, but from what I've read some TVs work better than others, and some have a problem handshaking with the TV. Have you tried it on a different TV/monitor?
Click to expand...
Click to collapse
not yet I only have one with HDMI but I will try and go to a friends house and give it a try, im waiting to try my gf's EVO to see if it does it too, If hers doesnt do it then I know its my phone, I was having trouble with random resets on my phone aswell, i havent noticed it since fully rooting....
Update: I tried my ft's EVO and same problem, haven't got to try a diff. T.V. yet maybe latter today I can.
-------------------------------------
Sent via the XDA Tapatalk App
same issue here, plug in and phone freezes. have to remove the battery to reset.. pretty disheartening
It's the tv, I've went through the same thing, it works fine on my TVs at home but at my mom and my sisters houses it did not work, they both have the same TVs it freezes and reboot the phone.
well that sucks. hoping I wouldn't encounter MORE reasons to return this thing
widjit said:
Any one else having trouble with HDMI re-booting? Every time I plug in my hdmi cable to my tv the phone freezes and then reboots, tried stock rom and rooted damagecontrol rom both with the same issue...
Click to expand...
Click to collapse
Same issue.. Mine starts to reboot but never finishes (I end up having to pull the battery out..) - gets stuck at the white HTC EVO 4G screen
-m
Well its good to know its not just me, I'm going to a friends house to try it on his... or maybe I will just go to best buy and try it up there on multiple TV's think they would mind...
-------------------------------------
Sent via the XDA Tapatalk App
quit buying cheap tvs buy sony bravia i have 4 plus a new sony 3d tv they all work great from my phone.
dogbone414 said:
quit buying cheap tvs buy sony bravia i have 4 plus a new sony 3d tv they all work great from my phone.
Click to expand...
Click to collapse
boy you sure are cool.
Wait so I need to buy a new tv to solve this issue? WTF is this ****!?
chuckhriczko said:
Wait so I need to buy a new tv to solve this issue? WTF is this ****!?
Click to expand...
Click to collapse
Hahaha. Yeah, it's stupid. But to be fair a cheaper TV is a lot more likely to incorrectly implement the HDMI spec. Your Bluray player or Xbox might be able to deal with this, but I just don't think a mobile device has the hardware to compensate.
I first bought the Samsung brand MHL adapter, and the moment i plugged it into the phone, it simply reboot without displaying anything on the TV. I figured it might be the adapter, so I returned it and bought a 3rd party Menotek adapter only to find the same problem.
The power cable is connected to the adapter, and the adapter to the phone and HDMI cable. I even tried a different power cable, and wall charger and same problem occurs.
Is this a problem with anyone else, one that has a fix? If not I might have to exchange my phone, since this is a feature I really wanted.
Could it be perhaps that the Docomo (Japanese) version uses different electric current that it has to convert, but the adapter can't convert?
i have the exact same problem.
at first i thought it was the cable, so i exchanged for another one... it rebooted.
then i thought maybe it's the tv, so i tried a friend's tv... it rebooted as well.
so i figured it must be the phone. but then since everything else was working perfectly on my phone, i couldn't be bothered to go exchange it... i thought i'd hardly use the mhl if at all. guess you should go exchange yours while you still can though.
I'll contact newegg about it, see if I can get a hassle free exchange.
My biggest guess is that is has something to do with the 110v/220v electrical current that it either doesn't receive enough, or too much, causing it to restart.
I am not sure what a good solution is. At least I am not the only one.
hmm i doubt it's got anything to do with electric currents.
it's my understanding that standard usb power is 5v.
anyways japan uses 110v same as US, and i'm in asia 220v and we're having the same problem.
I had same problem as this but the jelly bean update fixed it....
Sinfamy said:
I'll contact newegg about it, see if I can get a hassle free exchange.
My biggest guess is that is has something to do with the 110v/220v electrical current that it either doesn't receive enough, or too much, causing it to restart.
I am not sure what a good solution is. At least I am not the only one.
Click to expand...
Click to collapse
110/220 is AC, which is converted to DC before it even gets to the usb cord, let alone to the phone. Most chargers will support 110 & 220, so there shouldn't be any issue there.
Are you rooted? Have you tried any other ROMs?
live-evil said:
I had same problem as this but the jelly bean update fixed it....
Click to expand...
Click to collapse
i have the same problem and the jelly bean update doesn't fix this problem, any solutions?
I9250 suffers from defect as well
I have problem. Using i9250 original international version. MHL worked once upon a time, jelly bean didn't fix it, started in 4.0.4, last worked in 4.0.2, dont care about downgrading just to examine, but going back to stock 4.0.1 or 4.0.2 might fix it
Please star issue:
http://code.google.com/p/android/issues/detail?id=34048
Ahh forgot about this thread. Using bigxies deodexed rom got it working for me you can find it in the dev forum here.
Hello people, i'm going to tell you something you should know if you are going to buy the Nyko Playpad.
(I'm not trying to discurage you from buying the controller i'm only gonna give you guys some info. Very good info.)
(Also, if i posted this in the wrong place, sorry, i'm new here.)
Anyway, what i was going to tell you is something that happend to me. I bought the controller to use it with my HTC Evo View 4G Tablet.
The controller claims to be compatible with any Android device, as long as it has a version of 3.0 and up, BUT, it won't work on ALL devices. (A guy from Technical Support told me this.)
So my problem is that I am able to pair the control and the tablet, but aren't able to establish a succesfull connection, after pairing the controller, they don't connect like they are suposed to, insted, the light on the controller goes back to flashing slow, I made sure everything was correct, folowed the instructions sevral times, but no luck. Clicking on the device from the list of devices wont work eather, i only get a message saying to press any key on the KEYBOARD to reconnect; pressed the hell out of the buttons sevral times and they still don't connect.
Later on this day today, i call technical support but they wernt much of help, all they told me was that not all devices are compatible, and to try to reset the controller that there is a button to do so and then to try again. I fond the pin hole but theres no botton, so there is no reset botton, nor does it say anywhare how to do so. (the hole doesn't even say "reset" like most holes.
The controller is not defective, i tried it on my friends Galaxy Tab 2 and it worked with no problem at all, it also works perfectly with my iPod 4g.
So what i'm trying to tell you is to do some background research to see if your device will be compatible, and for gods sake, make sure you are on Android 3.0 or above, some people don't even see that. (I forgot to check so myself.)
Here is a list of devices i tried and if they worked or not and a reason:
Verizon Galaxy Tab 7" (Galaxy Tab 1): Not working. Reason: Below Android 3.0
HTC Evo 4G: Not working. Reason: Below Android 3.0
Galaxy Tab 2: Working Perfectly.
iPod 4th Generation (Running IOS 6.1.3 Jailbroken): Works perfectly in iCade mode.
HTC Evo View 4G: Not working: Reason: Pairs but doesn't connect. (Yes I made sure it was running above 3.0, and my tablet is running on 3.1.2)
LG Optimus L9: Not working. Reason: Pairs but doesn't connect. (Didn't check what Android version it was running on, my friend took it away from me befor i could check.)
I also know that it works perfectly on the Galaxy Note II.
Again, im not trying to discurage you from buying it, its one hell of a good controller, only thing is that its kind of small, but you eventually get used to it after the first day.
It would be nice to have a list of comatible devices on their website, or somewhere, in fact, if there is non, we should all make one by saying which device they tried and if it worked or not.
One last thing, if you guys know how to make it work on the HTC Evo View 4G Tablet, please tell me, perferably something not requireing root, I've Googled to death and even made an account here for help and i got no reply... Or at least how to reset the controller.
Hope this was helpful to you people who want to buy the controller, if i made you change your mind about the controller, sorry, but this has to be somewhere to be found and known about. Thanks for taking your time reading this, and if you decide to help on my little connection problem, also thanks.
so if i buy it for an ouya...would it work ?
BadWolff23 said:
so if i buy it for an ouya...would it work ?
Click to expand...
Click to collapse
I don't know, i.don't have an Ouya, but it is Android Powerd if there is a way for them to connect then it might, but honestly, i've never bother to see what the Ouya is cpable of...
I know this thread is kinda old, but I just got one and am having trouble connecting. There is a little pinhole and a button down inside of it. You have to push straight down and you'll be able to feel it.
mrhomg said:
I know this thread is kinda old, but I just got one and am having trouble connecting. There is a little pinhole and a button down inside of it. You have to push straight down and you'll be able to feel it.
Click to expand...
Click to collapse
Whoa sorry for the year late reply, but i actually tried that pinhole thing and didn't fix it, i figured it was just my ex HTC tablet that was not compatible... so i guess just because it was in the 3.0+ or whatever, it doesnt really meen it will work, to this day, i gave the tablet to my little neice, and its still not compatible lol... but i have a Tab 4 7.0 and a Note 2 i use it with cx
My earbuds which i was using for a long time
Then my newly bought usb Cable
Then another earbuds which i had at home
All these 3 items went faulty just in period of one week for me. Earbuds are not working in other devices to but the usb cable could charge any other device but not mine.
I just got my phone back after replacing my faulty touch screen. And then all of this happened. Also i had installed a new rom and kernel after getting my phone.
I find it a little difficult to find that all this accessories gettingg faulty were a coincidence.
Just wanted to know your opinion.
arjun5463 said:
. Also i had installed a new rom and kernel after getting my phone.
Click to expand...
Click to collapse
install stock rom and see what happens,is probably software problem
I am having tons of issues with Android P and the headphone adapters. When I was running dev preview 1 I had a strange issue where they worked with headphones, but not aux cables. I posted here and no one else was having issues so I just dealt with it for a bit. Then the beta came out and I upgraded. Everything started working again after that and I had no issues for a few days. Then it started acting up again. This time with headphones. It would randomly drop the headphones and start playing out of the speakers. Usually a reconnect or reboot would fix it. Then they just quit all together, nothing I did would make them work at all, headphones or aux. So I reflashed back to Oreo. All worked fine, so I upgraded back to the beta. Once again all was good until a few days and everything quit working again. That is where I currently am now. The other thing of note is that it has charging connected device via USB in the notifications. It seems to me that something changes and it starts seeing the adapters as some sort of USB device and not an audio adapter.
I also have 2 adapters and always test both with the same results. Is anyone else having issues? Could this be a hardware issue? I guess the next step is to go back to Oreo for a while and see if it happens there. Maybe it was just a coincidence that it happened when I upgraded.
I only had the issue on the first Dev preview where my aux cable would not play. On the second beta it is still working perfectly and I've been running it since it came out. I don't use headphones, so I have no tested it. I'd say no it is not a hardware issue and is just due to software issues with the beta. If you are worried about hard ware, go back to stock and see if you have the issue. If not, that will tell you it is the software and issues are expected as it is in beta.
I have tried some more steps. I flashed back to stock by opting out of the beta and it still didn't work. So I flashed back to stock with the factory image and that didn't work either. Now the same thing happens no matter what, it just says its supplying power to the device. I contacted support just to see what I could do about it. They are sending a new dongle to test. I do already have two, but it cant hurt to try another first. I suppose if that still doesn't work, the next step will be a new device.
I'd bet bad USB components. Can you connect to your computer? Bet it's not recognized.
Just got my second replacement for bad port. 1st one was smoking.
Second one behaved like yours.... no headphones or PC connection.
thecaptain0220 said:
I have tried some more steps. I flashed back to stock by opting out of the beta and it still didn't work. So I flashed back to stock with the factory image and that didn't work either. Now the same thing happens no matter what, it just says its supplying power to the device. I contacted support just to see what I could do about it. They are sending a new dongle to test. I do already have two, but it cant hurt to try another first. I suppose if that still doesn't work, the next step will be a new device.
Click to expand...
Click to collapse
Im in the same boat as you. It's suspicious that a lot of people had the same problem.. I dunno if its a HW problem..
I started to have this problem last night. Very frustrating.
akenis said:
I'd bet bad USB components. Can you connect to your computer? Bet it's not recognized.
Just got my second replacement for bad port. 1st one was smoking.
Second one behaved like yours.... no headphones or PC connection.
Click to expand...
Click to collapse
Yeah, it seems like that has started to go too. Tested it and windows says device unrecognized. Still seems to be charging for now.
Frustrating
Ever since the last update it stoped working all together.
This is so frustrating.