Hi all. I've tried using USB joysticks and gamepads with my G5+, but without success. They are detected (i.e. by looking at logcat/dmesg), and they power off (lights go on), but I can't actually use them in any way. I've tested by using a Joystick test app, and a couple of games. In all cases there is no joystick detected.
I tried this with stock unrooted before, and again now under Lineage 14.1. Has anyone had any luck with this? Could another kernel enable joysticks? Other USB peripherals work fine, e.g. keyboard/mice/USB sticks.
Also, has anyone tried bluetooth joysticks/gamepads? If I'm out of luck with USB joysticks, might consider just getting a bluetooth one if I know they work.
Here's an example of the output from dmesg:
[ 126.407593,3] usb 1-1: new low-speed USB device number 3 using xhci-hcd
[ 126.557281,3] usb 1-1: New USB device found, idVendor=046d, idProduct=c20a
[ 126.557328,3] usb 1-1: New USB device strings: Mfr=4, Product=32, SerialNumber=0
[ 126.557347,3] usb 1-1: Product: WingMan RumblePad
[ 126.557364,3] usb 1-1: Manufacturer: Logitech Inc.
[ 126.558716,3] usb 1-1: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 126.558778,3] usb 1-1: ep 0x1 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 126.868193,2] QSEECOM: qseecom_load_app: App (cppf) does'nt exist, loading apps for first time
[ 126.871609,2] QSEECOM: qseecom_load_app: App with id 19 (cppf) now loaded
Well I've used all sorts of peripherials on stock, including a universal gamepad. It works flawlessly and gets detected, though I do have to add a keylayout file for it to work with games in its native mode. When switching to xbox input mode it's supported natively on Android.
Mine uses a 2.4GHz usb dongle which uses very little power, maybe it's a power draw related thing?
I had considered of it was a power drain issue as well. I tried hooking up the same gamepad to an old Samsung galaxy s3, and it worked fine. Not sure that that tells us much.
In any case I decided to purchase a cheap Bluetooth gamepad to test, and I can use it with my laptop if it doesn't work with my g5+. So when it arrives, hopefully I can get it working.
Related
As there is a USB host-mod port in A500, Is there any way to get a USB to serial converter working with it?
From time to time, I need to access to some Cisco devices' serial consoles. I used to use the laptop (which has neither a serial port) with a USB to serial converter for this. If the converter can also works in A500, it would be very nice that I don't need to bring the heavy laptop.
jackycxh said:
As there is a USB host-mod port in A500, Is there any way to get a USB to serial converter working with it?
From time to time, I need to access to some Cisco devices' serial consoles. I used to use the laptop (which has neither a serial port) with a USB to serial converter for this. If the converter can also works in A500, it would be very nice that I don't need to bring the heavy laptop.
Click to expand...
Click to collapse
I also need this, and I think the original acer 3.0 rom already support pl2303(usb to serial ), because I test my gps in the terminal emulator and it can get the data. But m-dj's roms don't support.
are the stock rom support it ?
sanaell said:
are the stock rom support it ?
Click to expand...
Click to collapse
Yes! I have tested my usb gps(pl2303) and it got the data. I think it just recognize this device but maybe you need some app to deal with it. I search the web and find some information. they said linux supports pl2303 and so android might support also and really stock rom support this chip pl2303 but m-dj's mod rom not.
Not sure if mine is pl2303. I will check it out.
but it does not recognized when I plug it in A500.
I got below information from dmesg.
<6>[ 387.721955] usb 1-1: new full speed USB device using tegra-ehci and addres
s 2
<6>[ 389.787681] usb 1-1: New USB device found, idVendor=0403, idProduct=6001
<6>[ 389.788352] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumbe
r=3
<6>[ 389.788998] usb 1-1: Product: usb serial converter
<6>[ 389.789346] usb 1-1: Manufacturer: ftdi
<6>[ 389.790054] usb 1-1: SerialNumber: ftEFW35C
jackycxh said:
Not sure if mine is pl2303. I will check it out.
but it does not recognized when I plug it in A500.
I got below information from dmesg.
<6>[ 387.721955] usb 1-1: new full speed USB device using tegra-ehci and addres
s 2
<6>[ 389.787681] usb 1-1: New USB device found, idVendor=0403, idProduct=6001
<6>[ 389.788352] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumbe
r=3
<6>[ 389.788998] usb 1-1: Product: usb serial converter
<6>[ 389.789346] usb 1-1: Manufacturer: ftdi
<6>[ 389.790054] usb 1-1: SerialNumber: ftEFW35C
Click to expand...
Click to collapse
I think your device is not used pl2303. Because the manufacturer is not prolific.
Hmm, I tried when I was on 3.0.1 and could not get it to work. Just got the 3.1 update yesterday and plugged in my prolific today and yep /dev/ttyUSB0 shows up. Now I don't have to rely on bt for gps.
GonzoCSU said:
Hmm, I tried when I was on 3.0.1 and could not get it to work. Just got the 3.1 update yesterday and plugged in my prolific today and yep /dev/ttyUSB0 shows up. Now I don't have to rely on bt for gps.
Click to expand...
Click to collapse
You mean you can use use usb gps? How? With or without any addtional apk?
It should be pretty easy to write your own app to read /dev/ttyUSB0 or modify an app like BlueGPS4Droid (which receives serial NMEA over Bluetooth and feeds a mock location listener). I am not sure if the standard Java libraries for serial connections are supported under Android or not. I will be looking more into this in the next few days and I will post back here when I figure out more.
GonzoCSU said:
It should be pretty easy to write your own app to read /dev/ttyUSB0 or modify an app like BlueGPS4Droid (which receives serial NMEA over Bluetooth and feeds a mock location listener). I am not sure if the standard Java libraries for serial connections are supported under Android or not. I will be looking more into this in the next few days and I will post back here when I figure out more.
Click to expand...
Click to collapse
It is nice! And I think it will be successful. And I use the terminla emulator and gps can get data and even it fixed the location (led of my gps flash and meant it got the postion). However I need the tab support my gps because I am not using the stock rom, I am using galaxy 1.05
And I see the kernal resource on the web and see it really support and the code is here
https://github.com/roggin/iconia-a500-kernel/tree/iconia_kernel_11.2.9/drivers/usb/serial.
Not only the pl2303 also other usb2serial. And can anyone make this to my galay rom and let it supported?
Hi Guys!
I have a self powered: FTDI(FT232R) - micro USB-A (Nokia OTG CA-157) - Archos 70
with custom kernel. It works like a charm BUT
The driver picks the FT232R only if I connect it in the following sequence:
1. First connect the micro USB-A dongle (FT232 not attached)
2. As second connect FT232R to the USB dongle
Then I got the following dmesg:
1.
Code:
Code:
usb_switch_print_state: 3 ATTACHED_HOST
usb_switch_print_state: 3 ATTACHED_HOST
twl4030_usb twl4030_usb: regulator_enable twl4030_usb-usb1v5 enabled 0
twl4030_usb twl4030_usb: regulator_enable twl4030_usb-usb1v8 enabled 0
twl4030_usb twl4030_usb: regulator_enable twl4030_usb-usb3v1 enabled 0
musb_hdrc: version 6.0, musb-dma, peripheral, debug=0
twl4030_usb twl4030_usb: regulator_enable twl4030_usb-usb3v1 enabled 1
twl4030_usb twl4030_usb: regulator_enable twl4030_usb-usb1v8 enabled 1
twl4030_usb twl4030_usb: regulator_enable twl4030_usb-usb1v5 enabled 1
musb_hdrc: USB Host mode controller at fa0ab000 using DMA, IRQ 92
musb_hdrc musb_hdrc: MUSB HDRC host driver
/home/archos/kernel/gen8/gen8-gpl-froyo/linux/drivers/usb/core/inode.c: creating file '002'
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
usb usb2: default language 0x0409
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.29-omap1 musb-hcd
usb usb2: SerialNumber: musb_hdrc
usb usb2: uevent
usb usb2: usb_probe_device
usb usb2: configuration #1 chosen from 1 choice
usb usb2: adding 2-0:1.0 (config #1, interface 0)
usb 2-0:1.0: uevent
hub 2-0:1.0: usb_probe_interface
hub 2-0:1.0: usb_probe_interface - got id
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
hub 2-0:1.0: standalone hub
hub 2-0:1.0: individual port power switching
hub 2-0:1.0: no over-current protection
hub 2-0:1.0: power on to power good time: 10ms
hub 2-0:1.0: 100mA bus power budget for each child
hub 2-0:1.0: local power source is good
hub 2-0:1.0: enabling power on all ports
/home/archos/kernel/gen8/gen8-gpl-froyo/linux/drivers/usb/core/inode.c: creating file '001'
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0000
hub 2-0:1.0: hub_suspend
usb usb2: bus auto-suspend
2.
Code:
Code:
usb usb2: usb resume
hub 2-0:1.0: hub_resume
hub 2-0:1.0: port 1: status 0101 change 0001
hub 2-0:1.0: state 7 ports 1 chg 0002 evt 0000
hub 2-0:1.0: port 1, status 0101, change 0000, 12 Mb/s
usb 2-1: new full speed USB device using musb_hdrc and address 2
usb 2-1: ep0 maxpacket = 8
usb 2-1: default language 0x0409
usb 2-1: New USB device found, idVendor=0403, idProduct=6001
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1: Product: RFID_EM
usb 2-1: Manufacturer: FTDI
usb 2-1: SerialNumber: A9UMG98I
usb 2-1: uevent
usb 2-1: usb_probe_device
usb 2-1: configuration #1 chosen from 1 choice
usb 2-1: adding 2-1:1.0 (config #1, interface 0)
usb 2-1:1.0: uevent
usbserial_generic 2-1:1.0: usb_probe_interface
usbserial_generic 2-1:1.0: usb_probe_interface - got id
ftdi_sio 2-1:1.0: usb_probe_interface
ftdi_sio 2-1:1.0: usb_probe_interface - got id
ftdi_sio 2-1:1.0: FTDI USB Serial Device converter detected
usb 2-1: Detected FT232RL
usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0
/home/archos/kernel/gen8/gen8-gpl-froyo/linux/drivers/usb/core/inode.c: creating file '002'
hub 2-0:1.0: 100mA power budget left
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1 enable change, status 00000103
This is a very verbose fine dmesg showing ttyUSB0 is created.
My problem is that if I connect the micro-A dongle with FT232R already connected, then just the 1st sequence runs (till bus suspend) the second not. The same thing is with soft reboot, it is not working I need to manually disconnect then connect dongle first then FT232R.
I tried to tune msusb_hdrc config but with no sucess. What is the problem, what causes to stuck at suspend when it is not attached in 2 step??????
I have a pic from the hw look but yet I can't post it (till 8 posts) if needed I can in private.
UPDATE is that I tried to disable auto suspend and it is still not working. The general thing is that the musb_hdrc host driver recognizes the OTG as a hub with one port and if the peripherial (FT232R in this case) is already attached it is not enumarated and picked by the FTDI driver. Furthermore the state switching is not done properly. If the periph. is not attached it goes to a_idle but if yes it stays in b_idle mode (sys/devices/platform/musb_hdrc/mode).
Thanks, cheers
sodjas
As the title states, I have installed 4.0.4 Tegraowners ICS ROM v170 and see that i have a 3g signal bar, however no connection. I am not sure how to check and see if my 3g dongle is even being seen correctly other than the green lights on the device it self.
**edit**
O.K. a little more information:
Qualcomm 3g device
dmesg log shows device seen, connected, and drivers loaded: See below
Code:
[ 3982.060685] usb 1-1.2: new full speed USB device number 8 using tegra-ehci
[ 3982.092684] usb 1-1.2: New USB device found, idVendor=1199, idProduct=0301
[ 3982.092791] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=4
[ 3982.092968] usb 1-1.2: Product: Sierra Wireless Device
[ 3982.093067] usb 1-1.2: Manufacturer: Sierra Wireless, Incorporated
[ 3982.093246] usb 1-1.2: SerialNumber: 4Vx«Íïÿÿÿÿ
[ 3982.096237] sierra 1-1.2:1.0: Sierra USB modem converter detected
[ 3982.097713] usb 1-1.2: Sierra USB modem converter now attached to ttyUSB0
[ 3982.098625] usb 1-1.2: Sierra USB modem converter now attached to ttyUSB1
[ 3982.101019] usb 1-1.2: Sierra USB modem converter now attached to ttyUSB2
[ 3982.102181] usb 1-1.2: Sierra USB modem converter now attached to ttyUSB3
[ 3983.590674] usb 1-1.1: new high speed USB device number 9 using tegra-ehci
[ 3983.622387] usb 1-1.1: New USB device found, idVendor=198f, idProduct=0220
[ 3983.622694] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3983.623193] usb 1-1.1: Product: Mobile WiMax SS
[ 3983.623471] usb 1-1.1: Manufacturer: Beceem Communications Inc.
Now I have tried adding sprint APN in via the GUI but nothing stays. I guess i need to figure out how to add it to the APN file and upload it that way to my device.
O.K. maybe i am missing something.
Do I need to add an app, or turn something else on to have the ROM use the 3g dongle for connectivity? I am on an A500 so I do not think i need to make this change "a501 3g modem(comment ro.carrier=wifi-only in /system/build.prop)" as stated i have the 3g bars with an x through them even when the dongle is plugged in. Anyone familiar with this willing to try and help me figure this out.
I am not a noob to android just a noob to modding my tablet.
Still any help would be appreciated, even if its to tell me i need some kind of app to enable the modem.:silly:
For support on tegraowners Rom, you need to go to their site.
Thank you for the reply ....
The same post has been on the tegraowners support forum for about a week. Almost 100 views, and only my 1 reply to my self with the extra information. Was hoping someone over here could help me out.
Alas, the TO ROM is kinda persona non-grata around here, due to the lack of GPL compliance. We're really not generally meant to discuss it all that much as it usually devolves into a slanging match.
TO is the best place to go to get support.
FloatingFatMan said:
Alas, the TO ROM is kinda persona non-grata around here, due to the lack of GPL compliance. We're really not generally meant to discuss it all that much as it usually devolves into a slanging match.
TO is the best place to go to get support.
Click to expand...
Click to collapse
Gotcha, and thanks for the info. I will keep trying over there, unless someone can point to another a500 rom supports the 3g dongle.
If u have an android phone get foxfi app from market and use ur phone as modem. I who needs a Dingle.
Hello all,
I finally received my usb otg hub so I can start fiddling with my old mce usb ir receiver. I was hoping it would just be plug and play, but alas for some reason google didn't include the necessary kernel drivers for this old receiver lol. The stock kernel didn't support loading modules so I had to build my own. After an hour of pulling sources and digging through the make menuconfig options I think I setup the proper build. Now when I plug in the usb receiver it actually spits out some good dmesg info. I'm just not sure where to go from here. Here is my dmesg for the NP.
Code:
<6>[ 495.285263] usb 2-1.4: new full-speed USB device number 5 using dwc3-host
<6>[ 495.322972] usb 2-1.4: New USB device found, idVendor=045e, idProduct=006d
<6>[ 495.322992] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 495.323004] usb 2-1.4: Product: Microsoft IR Transceiver
<6>[ 495.323014] usb 2-1.4: Manufacturer: Microsoft
<6>[ 495.323024] usb 2-1.4: SerialNumber: MS1PG7GQ
<6>[ 495.331082] Registered IR keymap rc-rc6-mce
<6>[ 495.331553] input: Media Center Ed. eHome Infrared Remote Transceiver (045e:006d) as /devices/pci0000:00/0000:00:11.0/dwc3-host.2/usb2/2-1/2-1.4/2-1.4:1.0/rc/rc2/input10
<6>[ 495.331633] keychord: using input dev Media Center Ed. eHome Infrared Remote Transceiver (045e:006d) for fevent
<6>[ 495.331642] rc2: Media Center Ed. eHome Infrared Remote Transceiver (045e:006d) as /devices/pci0000:00/0000:00:11.0/dwc3-host.2/usb2/2-1/2-1.4/2-1.4:1.0/rc/rc2
<6>[ 495.332199] input: MCE IR Keyboard/Mouse (mceusb) as /devices/virtual/input/input11
<6>[ 495.332364] keychord: using input dev MCE IR Keyboard/Mouse (mceusb) for fevent
<6>[ 495.332449] rc rc2: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
<6>[ 495.492417] mceusb 2-1.4:1.0: Registered Microsoft Microsoft IR Transceiver with mce emulator interface version 1
<6>[ 495.492430] mceusb 2-1.4:1.0: 2 tx ports (0x0 cabled) and 2 rx sensors (0x0 active)
I grabbed some lirc binaries from this thread
http://www.freaktab.com/showthread.php?10233-Adding-support-of-quot-third-party-quot-IR-remotes
Code:
[email protected]:/system/usr/lirc # ./ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event0) with:
Driver rc-loopback, table rc-empty
Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC RC-5-SZ other
Enabled protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC RC-5-SZ other
Name: rc-core loopback device
bus: 6, vendor/product: 0000:0000, version: 0x0001
Repeat delay = 0 ms, repeat period = 0 ms
Found /sys/class/rc/rc1/ (/dev/input/event4) with:
Driver mceusb, table rc-rc6-mce
Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC RC-5-SZ other
Enabled protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC RC-5-SZ other
Name: Media Center Ed. eHome Infrared
bus: 3, vendor/product: 045e:006d, version: 0x0200
Repeat delay = 0 ms, repeat period = 0 ms
Unfortunately ./ir-keytable -t doesn't shows any key presses. Also the rest of the utilities, irw, lircd etc don't run, SELinux hell.
Does anyone else have any insight that I may be missing.
I've attached my kernel, it has /proc/config.gz enabled to help
I am planning on using a Flirc IR receiver. Will this kernel be useful to me adding new remotes? Do you know?
QUEDRO said:
I am planning on using a Flirc IR receiver. Will this kernel be useful to me adding new remotes? Do you know?
Click to expand...
Click to collapse
Flirc IR reciever doesn't need a custom kernel. Should just be plug and play
Was any progress made with this? I'd love to be able to use my MCE remote!
If your remote is an IR remote, it should work fine. However, not all MCE remotes are so it would depend on which remote you have...
Sent from my A0001 using Tapatalk
xaudiblex said:
If your remote is an IR remote, it should work fine. However, not all MCE remotes are so it would depend on which remote you have...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Unfortunately that isn't correct... I'm using an HP IR MCE receiver with my Logitech Harmony... No dice.
hawkxcore said:
Unfortunately that isn't correct... I'm using an HP IR MCE receiver with my Logitech Harmony... No dice.
Click to expand...
Click to collapse
I should have been more specific. There was some discussion about using Flirc in conjunction with their MCE remote (not the receiver). What I should have stated was that If they were to use an IR MCE remote in conjunction with FLIRC USB receiver/adapter, than it should work.
Flashed the latest Pure Nexus last night and sideloaded Hangouts today. Both working great, except!
the AOSP base for Pure Nexus says it supports webcams for hangouts. I get no mic or video. If i try to take a picture in the hangouts app and get a "couldn't launch camera" message. a test video call got no audio or video.
I'm using a Logitech Webcam Pro 9000, i ran dmseg with it unplugged and plugged-in and ran diff on the output files and got
> [ 5140.962790] usb 2-1.4: new high-speed USB device number 13 using dwc3-host
> [ 5141.109753] usb 2-1.4: New USB device found, idVendor=046d, idProduct=0990
> [ 5141.109809] usb 2-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=2
> [ 5141.109842] usb 2-1.4: SerialNumber: BC054521
> [ 5141.133395] uvcvideo: Found UVC 1.00 device <unnamed> (046d:0990)
> [ 5141.165663] input: UVC Camera (046d:0990) as /devices/pci0000:00/0000:00:11.0/dwc3-host.2/usb2/2-1/2-1.4/2-1.4:1.0/input/input32
> [ 5141.585485] usb_audio: Warning! Unlikely big volume range (=3072), cval->res is probably wrong.
> [ 5141.585529] usb_audio: [5] FU [Mic Capture Volume] ch = 1, val = 4608/7680/1<6>[ 5152.100119] atvr_remove: hdev->name = Nexus Remote removed, num 1->0
Click to expand...
Click to collapse
So I know it's seeing the camera. Tried a couple camera apps but nothing comes up.
ideas?
I saw in a different thread that you need to change the camera defaults it uses... now if I could find that thread.
Found: http://forum.xda-developers.com/showpost.php?p=63229199&postcount=2
To fix the webcam in hangouts
edit the build.prop and change:
ro.camera.number=2
ro.camera.0.devname=/dev/video0
ro.camera.0.facing=back
ro.camera.0.orientation=0
ro.camera.1.devname=/dev/video0
ro.camera.1.facing=front
ro.camera.1.orientation=0
in -------------------->
ro.camera.number=1
ro.camera.0.devname=/dev/video0
ro.camera.0.facing=back
ro.camera.0.orientation=0
Is implied that you must start the device with the camera connected to have the webcam working
Asitaka said:
I saw in a different thread that you need to change the camera defaults it uses... now if I could find that thread.
Found: http://forum.xda-developers.com/showpost.php?p=63229199&postcount=2
To fix the webcam in hangouts
edit the build.prop and change:
ro.camera.number=2
ro.camera.0.devname=/dev/video0
ro.camera.0.facing=back
ro.camera.0.orientation=0
ro.camera.1.devname=/dev/video0
ro.camera.1.facing=front
ro.camera.1.orientation=0
in -------------------->
ro.camera.number=1
ro.camera.0.devname=/dev/video0
ro.camera.0.facing=back
ro.camera.0.orientation=0
Is implied that you must start the device with the camera connected to have the webcam working
Click to expand...
Click to collapse
I tried that. no luck. thanks!
Mic works fine, just no video.
skunkfifty said:
I tried that. no luck. thanks!
Mic works fine, just no video.
Click to expand...
Click to collapse
Any progress on this? I'm trying to see if I can get a webcam working on this ROM. So far no luck.
petermg said:
Any progress on this? I'm trying to see if I can get a webcam working on this ROM. So far no luck.
Click to expand...
Click to collapse
Nothing. I haven't had time to poke at it since my last post.
I can get audio but no video. I was able to get low quality video using a webcam app before I started messing with anything but that's it.
skunkfifty said:
Nothing. I haven't had time to poke at it since my last post.
I can get audio but no video. I was able to get low quality video using a webcam app before I started messing with anything but that's it.
Click to expand...
Click to collapse
ro.camera.0.facing=back
Change this line from "back" to "front". Make sure the camera is connected. Reboot.
shdware said:
ro.camera.0.facing=back
Change this line from "back" to "front". Make sure the camera is connected. Reboot.
Click to expand...
Click to collapse
I will try this later today and post back.
petermg said:
I will try this later today and post back.
Click to expand...
Click to collapse
If you're not too attached to this custom rom, you can try the roms developed by Zulu99. His lollipop and marshmallow based roms both support hangouts and skype, with some tweaks in build prop like above and separate camera and mic like you have. But this roms are far from the guidelines imposed by google in android tv
pisicuta said:
If you're not too attached to this custom rom, you can try the roms developed by Zulu99. His lollipop and marshmallow based roms both support hangouts and skype, with some tweaks in build prop like above and separate camera and mic like you have. But this roms are far from the guidelines imposed by google in android tv
Click to expand...
Click to collapse
Yeah I tried his ROM only thing is that the mic on the remote doesn't work so I went to Pure ROM. Getting a webcam to work isn't a high priority to me. It's more important to me for the mic in the remote to work. Thanks for your suggestion though.
---------- Post added at 02:45 AM ---------- Previous post was at 02:44 AM ----------
shdware said:
ro.camera.0.facing=back
Change this line from "back" to "front". Make sure the camera is connected. Reboot.
Click to expand...
Click to collapse
I still got nuthin'. This doesn't do anything for me. Thanks though.
---------- Post added at 02:48 AM ---------- Previous post was at 02:45 AM ----------
Here is the dmesg output for my cameras
Code:
dmesg |grep cam
[ 0.708100] info[ 6]: name = camera_full, gpio = -1
[ 0.708108] info[ 7]: name = camera_half, gpio = -1
[ 0.708133] info[10]: name = cam_capture, gpio = -1
[ 0.708141] info[11]: name = cam_focus, gpio = -1
[ 0.708199] info[18]: name = camera0_sb1, gpio = -1
[ 0.708207] info[19]: name = camera0_sb2, gpio = -1
[ 2.360149] usb 2-1.3: Product: HP Webcam 3110
[ 2.440263] uvcvideo: Found UVC 1.00 device HP Webcam 3110 (03f0:8d07)
[ 2.445466] input: HP Webcam 3110 as /devices/pci0000:00/0000:00:11.0/dwc3-host.2/usb2/2-1/2-1.3/2-1.3:1.0/input/input2
[ 8.170892] usb 2-1.4: Product: HD Pro Webcam C920
[ 8.201974] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d)
[ 8.203654] input: HD Pro Webcam C920 as /devices/pci0000:00/0000:00:11.0/dwc3-host.2/usb2/2-1/2-1.4/2-1.4:1.0/input/input3
Code:
dmesg |grep video
[ 0.112578] Linux video capture interface: v2.00
[ 0.388324] usbcore: registered new interface driver uvcvideo
[ 2.440263] uvcvideo: Found UVC 1.00 device HP Webcam 3110 (03f0:8d07)
[ 8.201974] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d)
Code:
dmesg |grep usb
[ 0.112235] usbcore: registered new interface driver usbfs
[ 0.112274] usbcore: registered new interface driver hub
[ 0.112415] usbcore: registered new device driver usb
[ 0.347779] usbcore: registered new interface driver kaweth
[ 0.347825] usbcore: registered new interface driver pegasus
[ 0.347859] usbcore: registered new interface driver rtl8150
[ 0.347894] usbcore: registered new interface driver r8152
[ 0.347934] usbcore: registered new interface driver asix
[ 0.347970] usbcore: registered new interface driver ax88179_178a
[ 0.348005] usbcore: registered new interface driver cdc_ether
[ 0.348040] usbcore: registered new interface driver cdc_eem
[ 0.348075] usbcore: registered new interface driver smsc75xx
[ 0.348110] usbcore: registered new interface driver smsc95xx
[ 0.348148] usbcore: registered new interface driver plusb
[ 0.362532] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.362546] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.362556] usb usb1: Product: EHCI Host Controller
[ 0.362566] usb usb1: Manufacturer: Linux 3.10.20-gc298bbc ehci_hcd
[ 0.362576] usb usb1: SerialNumber: 0000:00:10.0
[ 0.386650] usbcore: registered new interface driver usb-storage
[ 0.386756] usbcore: registered new interface driver usbserial
[ 0.386791] usbcore: registered new interface driver ftdi_sio
[ 0.386827] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 0.386886] usbcore: registered new interface driver pl2303
[ 0.386924] usbserial: USB Serial support registered for pl2303
[ 0.386967] usbcore: registered new interface driver usb_tm
[ 0.387312] usbcore: registered new interface driver xpad
[ 0.388324] usbcore: registered new interface driver uvcvideo
[ 0.388384] usbcore: registered new interface driver cx231xx
[ 0.551962] usbcore: registered new interface driver usbhid
[ 0.551971] usbhid: USB HID core driver
[ 0.702251] usbcore: registered new interface driver snd-usb-audio
[ 1.375803] android_usb gadget: Mass Storage Function, version: 2009/09/11
[ 1.375821] android_usb gadget: Number of LUNs=1
[ 1.376411] android_usb gadget: android_usb ready
[ 1.669083] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.669108] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.669129] usb usb2: Product: xHCI Host Controller
[ 1.669148] usb usb2: Manufacturer: Linux 3.10.20-gc298bbc dwc-xhci
[ 1.669167] usb usb2: SerialNumber: dwc3-host.2
[ 1.670908] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
[ 1.670934] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.670955] usb usb3: Product: xHCI Host Controller
[ 1.670974] usb usb3: Manufacturer: Linux 3.10.20-gc298bbc dwc-xhci
[ 1.670993] usb usb3: SerialNumber: dwc3-host.2
[ 2.032714] usb 2-1: new full-speed USB device number 2 using dwc3-host
[ 2.050257] usb 2-1: New USB device found, idVendor=05e3, idProduct=0606
[ 2.050292] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.050313] usb 2-1: Product: USB Hub 2.0
[ 2.050332] usb 2-1: Manufacturer: ALCOR
[ 2.050796] usb 2-1: ep 0x81 - rounding interval to 1024 microframes, ep desc says 2040 microframes
[ 2.243090] init: (Parsing /init.usb.rc took 0.00s.)
[ 2.243487] init: (Parsing init.fugu.usb.rc took 0.00s.)
[ 2.243842] init: (Parsing /init.usb.configfs.rc took 0.00s.)
[ 2.328442] usb 2-1.3: new full-speed USB device number 3 using dwc3-host
[ 2.345416] usb 2-1.3: not running at top speed; connect to a high speed hub
[ 2.360131] usb 2-1.3: New USB device found, idVendor=03f0, idProduct=8d07
[ 2.360143] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.360149] usb 2-1.3: Product: HP Webcam 3110
[ 2.360154] usb 2-1.3: Manufacturer: HP
[ 2.445466] input: HP Webcam 3110 as /devices/pci0000:00/0000:00:11.0/dwc3-host.2/usb2/2-1/2-1.3/2-1.3:1.0/input/input2
[ 8.076253] usb_audio: Warning! Unlikely big volume range (=7680), cval->res is probably wrong.
[ 8.076266] usb_audio: [5] FU [Mic Capture Volume] ch = 1, val = 512/8192/1<6>[ 8.146364] usb 2-1.4: new full-speed USB device number 4 using dwc3-host
[ 8.162618] usb 2-1.4: not running at top speed; connect to a high speed hub
[ 8.170872] usb 2-1.4: New USB device found, idVendor=046d, idProduct=082d
[ 8.170885] usb 2-1.4: New USB device strings: Mfr=0, Product=2, SerialNumber=1
[ 8.170892] usb 2-1.4: Product: HD Pro Webcam C920
[ 8.170897] usb 2-1.4: SerialNumber: D98ED55F
[ 8.203654] input: HD Pro Webcam C920 as /devices/pci0000:00/0000:00:11.0/dwc3-host.2/usb2/2-1/2-1.4/2-1.4:1.0/input/input3