Philips pus7303 eth adapter problem - Philips, Sony, TCL Android TV

i have a problem with a philips 65pus7303 tv, i can't get a usb-ethernet adapter (the one that works with many tv, the tp link ue300)
I made the adb access to unlock the rndis function (usb eth) through the command
Code:
adb svc usb setFunction rndis true
the function is partially activated (before as soon as I selected it it came out now it remains selected but when I exit the menu it goes back to reload) but still does not recognize the device
is there any trick you know or try?

I am interested in putting a usb ethernet adapter, if you get it to work please tell me

Related

HTC Desire won't mount as a drive?

Hi guys, I'm obviously new here, but I did have a look and couldn't seem to find this answer anywhere else.
I'm trying to hook my HTC Desire to my PC, but every time I connect it via USB cable it says that device drivers are not found and that Windows cannot rectify the problem.
I've tried installing HTC Sync, but the PC won't even recognise that there's a phone or mass storage device hooked up, so it just stays at "disconnected".
I've selected the phone to appear as a mass storage device when I plug it int the PC (I even select this on the phone's display as I connect it via USB so the phone realises that it's being plugged into a PC).
Does anyone know how to fix this?
Thanks in advance.
I've struggled with a problem like this before (though, a flash drive, not a phone).
There were two solutions that helped mi on two different occasions.
1) Removing all usb devices from the computer. Shut the computer down, take out the power cord and wait for 20-30 min to settle all capacitors. Then turn it on and plug the devices back in.
2) Put the device in the computer as Mass Storage. Go to device manager and see where is the device. Right click on it (should be unknown or stuff), choose update driver. If it doesn't find anything try updating windows with latest patches and try again.
3) I was solving a non-detectable usb webcam, but removing ALL usb devices from the device manager (Under USB choose device, delete, choose device, delete.) Then click Scan for changes on the top to refresh the devices and install the drivers of the usb root hubs, etc. This would probably fix the problem if the above fails.
---- edit ----
Quick note: if your keyboard/mouse are USB, you could hang without keyboard or mouse until you restart your computer, so keep in mind if you can detect them, delete them last
----/edit -----
If you still can't get it to work, please provide results from another computer (if it works there as mass storage), or better if you have some Linux Live CD you could try there if it gets recognised.
Where you try to plug usb cable into PC - front panel or rear? Because a lot of PCs have an issue with front panel usb. Try rear panel
jankos said:
Where you try to plug usb cable into PC - front panel or rear? Because a lot of PCs have an issue with front panel usb. Try rear panel
Click to expand...
Click to collapse
Thanks to both of you for the swift replies
I actually figured I'd check this short fix before trying the more detailed ones and it seems like it was just a matter of plugging it into the rear usb!
I'm definitely putting this solution to my personal FAQ. Thanks, jankos.
HTC EVO won't mount as a drive
verified that issue was with the front USB port. I plugged my EvO in to a usb hub I had plugged into back usb port and it worked like it was supposed to.

OTG

Does Nokia N1 got OTG support? I have Tried to connect my USB Flash through OTG cable but doesn't work for me ....
Doesn't work for me either >_<
I don't have an otg cable myself (yet) but can you try to use USB Host Diagnostics (available in play store) and post the report?
FYI I got an OTG cable myself and it didn't work. I dug a bit deeper and found out that OTG is most likely not implemented because Nokia N1 is using legacy usb controller over usb C - see below:
Converting USB 2.0 OTG SoCs to USB Type-C
While existing Device, Host, and DRD devices can be converted to support the USB Type-C connection with some effort, it is not practical to convert existing OTG SoCs. OTG requires a new state machine using the configuration channel to support USB Type-C. Host Negotiation Protocol is used to swap host and device role for OTG, while Power Delivery communication is used to change roles for USB Type-C. Combined, these challenges preclude simple upgrades of OTC SoCs to USB Type-C. - See more at: https://www.synopsys.com/Company/Pu...esign-type-c-2015q1.aspx#sthash.Ri02Guwe.dpuf
Click to expand...
Click to collapse
The only chance to get otg to work is most likely preparing a kernel patch (are the sources even available?) to manually switch the connector to host mode and power the attached device externally
After a bit of hacking around I was able to enable usb otg on my N1!
I've had a look at kernel sources for device with similar SoC (Nexus Player) and saw an interesting debugfs entry. To my surprise it worked like a charm and immediately detected the attached usb hub with a thumb drive, it even powered the hub so I didn't have to use an external power source!
To enable host mode, the following command has to be enterted in root console:
echo A > /sys/kernel/debug/usb/dwc3_debugfs_root/otg_id
Caveats (will try to find a way to resolve them):
- after enabling host mode N1, won't charge from the usb port - a reboot is required to enable the charging again
- probably same is true for pheripherial mode (connecting n1 to a pc). In theory, changing a to b in the above echo command should bring the tablet back to normal mode but for some reason it won't charge without a reboot so I'm assuming that same is true for non otg usb connectivity. Will have a look at the sources and debug messages to find out what's going on
wodz69 said:
After a bit of hacking around I was able to enable usb otg on my N1!
I've had a look at kernel sources for device with similar SoC (Nexus Player) and saw an interesting debugfs entry. To my surprise it worked like a charm and immediately detected the attached usb hub with a thumb drive, it even powered the hub so I didn't have to use an external power source!
To enable host mode, the following command has to be enterted in root console:
echo A > /sys/kernel/debug/usb/dwc3_debugfs_root/otg_id
Caveats (will try to find a way to resolve them):
- after enabling host mode N1, won't charge from the usb port - a reboot is required to enable the charging again
- probably same is true for pheripherial mode (connecting n1 to a pc). In theory, changing a to b in the above echo command should bring the tablet back to normal mode but for some reason it won't charge without a reboot so I'm assuming that same is true for non otg usb connectivity. Will have a look at the sources and debug messages to find out what's going on
Click to expand...
Click to collapse
Thanks for your hard job.
I have tried on my N1. It is amazing that otg did work. However, the otg can not coexist with charging function as yours. Hope someone could find a solution.
adagiov said:
Thanks for your hard job.
I have tried on my N1. It is amazing that otg did work. However, the otg can not coexist with charging function as yours. Hope someone could find a solution.
Click to expand...
Click to collapse
Hey,
Are you on Android 5.1.1 or 5.0 ?
I've had a look at the code of the usb driver of the a phone with similar chipset (asus zenfone 5) and it seems that the source of the problem is that the tablet fails to detect an appropriate charger type, which could mean either that the otg cable does not support this or the code of the driver does not work properly with usb C. Was wondering if something changed around this after the update?
wodz69 said:
Hey,
Are you on Android 5.1.1 or 5.0 ?
I've had a look at the code of the usb driver of the a phone with similar chipset (asus zenfone 5) and it seems that the source of the problem is that the tablet fails to detect an appropriate charger type, which could mean either that the otg cable does not support this or the code of the driver does not work properly with usb C. Was wondering if something changed around this after the update?
Click to expand...
Click to collapse
Hi, mine N1 is still running the android 5.0.
I am afraid Root is the prerequisite to hack otg. Unfortunately, root is not available on android 5.1.1 till now, so even the android 5.1.1 driver support it, that won't help.
Thanks,dude.
Yeah exactly for that reason I haven't upgraded my tablet yet

[Q] Easycap via USB OTG not working

Hi,
I would like to use lg g3 as a screen for my reverse/backup camera in a car. Before buying the g3 I checked that it supports OTG and latest Android has easycap drivets built in so you do not have to root the phone.
I have got easycap with UTV007 chip which should be supported and I checked that it works on windows laptop. I have got USB OTG cable. If I connect mouse to g3 in otg mode it does work.
However if I connect easycap it does not. I am using one of the reverse camera apps. I ran usb host check program and got the following output:
Android.hardware.usb.host.xml OK
Handheld.core.hardware.xml : usb host not enabled
Tablet.core.hardware.xml : not found
When i tap "fix" i am getting "could not start su process".
To me it sounds like it needs root rights to update some configuration. G3 has factory android 5.0 installed. I have enabled usb debugging but it did not help.
Do you know what the problem is and how can I get easycap working?
I would prefer to not root the device neither to install custom roms because I have no experience (my first week on android)
Thanks in advance!
Forgot to mention: The phone is D855 v20i TWN XX Android 5.0 kernel 3.4.0 if it makes any difference
So I have installed busybox and terminal, no root yet.
I have found handheld.core.hardware.xml and it does not "include" anything to do with usb host- is this a problem?
Furthermore there are numerous files like video0, video1,...video31,video32 in /dev/ - can someone please help explain it?
What is the best thing to check next?
hello. Have you tried using an otg y-cable? It may make no difference, but perhaps a y-cable with power source may help.

Can't connect via adb over bluetooh

While I'm waiting for my USB-C to USB-A cable in the mail, I'm wanting to test some apps on my 5x. I realize you need a cable to start this process over Wi-Fi, so I'm trying to do it with Bluetooth.
So far I've paired the Bluetooth on my 5x with my MacBook. I turned off the Wi-Fi on my MacBook and did Internet tethering via Bluetooth. I can load web pages just fine doing this.
I grabbed the default gateway,
Code:
192.168.48.1.
Then I tried
Code:
adb tcpip 4455
and a
Code:
db connect 192.168.44.1:4455
,
which got me:
Code:
error: device '(null)' not found
and
Code:
unable to connect to 192.168.44.1:4455
I have USB debugging on in the Developer Options. I've seen Bluetooth Debugging mentioned in old posts, but I do not see that option.
Is anybody able to get adb working over Bluetooth or Wi-Fi without a cable??
Thanks in advance.

USB charges but no data

Hi, my phone stopped being able to get a USB data connection. The port is physically intact and does not wiggle. I've tried two different Macs and one PC, different USB-A to -C cables (all verified by Benson Leung). Also toggled USB debug, MTP and PTP modes from Developer Options, rebooted phone and computer. When I plug the phone in, it only goes to Charging mode. Android File Transfer doesn't see it and 'adb devices' comes back empty. There is no notification offering me to select connection type. Did I miss anything or is it time to send it in? Thanks, Tony
What OS are you running on your Windows - checking your Device Manager under Control Panels - are all the Google / N5X drivers installed and working correctly before this ? Try uninstalling, reboot PC and re-install them - and, use different USB port to connect the cable (what kind of connections are you using ??)
Can you run ADB ?
Thanks I'm primarily using a Mac (10.10.5) but the PC was running Vista. It was a borrowed PC so I didn't install the drivers. I don't think it's a driver issue though since nothing shows up in device manager and the phone doesn't offer to switch out of charge-only mode. Also the same Mac worked previously.

Categories

Resources