Hello,
I tested with three different REDMI 3 devices and three different rom versions and have the following problem:
initially everything with connecting an external usb camera was ok. My usb camera app received events asking for permissions for using usb camera. But after 3 or 4 full charges the app stopped receiving permissions. I checked with couple other apps but again no permission. If my battery drops under 60% suddenly everything is ok again and the app detects the camera. It is stranger, that before full detect of the camera the app starts some kind of permission loop. I click allow and after 2 seconds the permission dialog shows again and so on... I checked the source code and appears my USBManager returns empty device list. For me it looks like some kind of battery optimizer or usb state optimizer doing it. I will be more than happy if someone can help me with this issue. Additionally I checked with all other stock rom version. It is all the same.
Here is some log from dmsg.
Code:
<6>[12449.627983] msm_otg 78d9000.usb: USB exited from low power mode
<6>[12449.647323] psy->name:usb
<6>[12449.652992] XXX::smb358_get_prop_batt_status:reg=0x0
<12>[12449.653558] healthd: battery l=94 v=4240 t=22.3 h=2 st=4 c=382 chg=
<6>[12449.744320] msm_hsusb_host msm_hsusb_host: EHCI Host Controller
<6>[12449.744844] msm_hsusb_host msm_hsusb_host: new USB bus registered, assigned bus number 1
<6>[12449.751356] msm_hsusb_host msm_hsusb_host: irq 166, io mem 0x078d9000
<6>[12449.769480] msm_hsusb_host msm_hsusb_host: USB 2.0 started, EHCI 1.00
<6>[12449.769624] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[12449.769636] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[12449.769646] usb usb1: Product: EHCI Host Controller
<6>[12449.769656] usb usb1: Manufacturer: Linux 3.10.49-perf-g48b885e ehci_hcd
<6>[12449.769665] usb usb1: SerialNumber: msm_hsusb_host
<6>[12449.772688] hub 1-0:1.0: USB hub found
<6>[12449.772729] hub 1-0:1.0: 1 port detected
<6>[12449.876761] msm_otg 78d9000.usb: USB in low power mode
<6>[12450.296922] msm_otg 78d9000.usb: USB exited from low power mode
<6>[12450.519306] usb 1-1: new high-speed USB device number 2 using msm_hsusb_host
<6>[12450.949089] usb 1-1: new high-speed USB device number 3 using msm_hsusb_host
<6>[12451.619450] usb 1-1: new high-speed USB device number 5 using msm_hsusb_host
<11>[12452.316729] init: Warning! Service eyecare needs a SELinux domain defined; please fix!
<11>[12453.339456] init: Warning! Service coloradjust needs a SELinux domain defined; please fix!
<6>[12453.759449] usb 1-1: new high-speed USB device number 13 using msm_hsusb_host
<6>[12455.879543] usb 1-1: new high-speed USB device number 21 using msm_hsusb_host
<6>[12456.212015] XXX::smb358_get_prop_batt_status:reg=0x0
<6>[12456.216663] psy->name:rk-bat
<6>[12456.216678] status=3, percent=94
<6>[12456.216684] status=3, percent=94
<6>[12456.222182] XXX::smb358_get_prop_batt_status:reg=0x0
<12>[12456.222723] healthd: battery l=94 v=4248 t=22.4 h=2 st=4 c=401 chg=
<6>[12456.319281] usb 1-1: new high-speed USB device number 22 using msm_hsusb_host
<11>[12457.382047] init: Warning! Service eyecare needs a SELinux domain defined; please fix!
<6>[12457.499222] usb 1-1: new high-speed USB device number 26 using msm_hsusb_host
<11>[12458.407239] init: Warning! Service coloradjust needs a SELinux domain defined; please fix!
<6>[12458.899381] usb 1-1: new high-speed USB device number 31 using msm_hsusb_host
<6>[12459.339269] usb 1-1: new high-speed USB device number 32 using msm_hsusb_host
Im now at tampered rom (the rom says miui global 7.1 | 7.1.1.0.0 stable) it not real global rom! gold colour. but i dont have any problem with otg or battery drops. All working fine. Except a few settings turns back to default if i reset the device. But its doesnt bothered me much.
Related
Hi Folks!
I'm a happy owner of a Galaxy Tab 10.1, and an EE engineer who frequently uses a small USB microscope while assembling boards.
I would be really happy to be able to use my Galaxy Tab as a lightweight portable screen for this microscope. This would be much more handy than having a bulky laptop stand in there.
So I've seen that the Galaxy Tab 10.1 has USB host capabilities. And after a quick verification, I've noted that the stock kernel has the uvcvideo driver builtin (the microscope is UVC compatible, actually it's a Logitech C310 hardware with added optics).
Seems like everything is in place to make it work. However when I plug the device in, I get an unrecognized USB device message popping up.
Here's the output from dmesg:
Code:
<6>[11734.027241] Board P4 : tegra_otg_en = 1<6>[11734.037361] tegra-otg tegra-otg: SUSPEND --> HOST
<6>[11734.037391] tegra-otg tegra-otg: tegra_start_host+
<4>[11734.038884] tegra_usb_phy_open() called instance :0
<6>[11734.038966] Board P4 : tegra_usb_ldo_en=1 instance=0 present regulator=1
<4>[11734.039001] utmi_phy_power_on() called. instance : 0
<6>[11734.040244] tegra-otg tegra-otg: Acc power on detect
<6>[11734.057205] Board P4 : tegra_acc_power token : (1,1) on
<4>[11734.057234] utmi_phy_clk_enable() called. instance : 0
<6>[11734.058757] tegra-ehci tegra-ehci.0: Tegra EHCI Host Controller
<6>[11734.059016] tegra-ehci tegra-ehci.0: new USB bus registered, assigned bus number 1
<6>[11734.067158] [ CONNECTOR_DRIVER (acc_notified,387) ] ACCESSORY=OTG : STATE=online
<6>[11734.087920] tegra-ehci tegra-ehci.0: irq 52, io mem 0xc5000000
<6>[11734.107159] tegra-ehci tegra-ehci.0: USB 2.0 started, EHCI 1.00
<6>[11734.107282] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[11734.107306] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[11734.107326] usb usb1: Product: Tegra EHCI Host Controller
<6>[11734.107343] usb usb1: Manufacturer: Linux 2.6.36.3 ehci_hcd
<6>[11734.107359] usb usb1: SerialNumber: tegra-ehci.0
<6>[11734.111805] hub 1-0:1.0: 1 port detected
<6>[11734.113078] tegra-otg tegra-otg: tegra_start_host-
<6>[11734.113101] host_notify: ndev name=usb_otg: from state=2 -> to state=1
<6>[11734.327059] usb 1-1: new high speed USB device using tegra-ehci and address 2
<3>[11734.592745] usb 1-1: device v046d p081b is not supported
<6>[11734.618692] host_notify: ndev name=tegra-ehci.0: from state=0 -> to state=5
<3>[11734.620877] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11734.787068] usb 1-1: new high speed USB device using tegra-ehci and address 3
<3>[11735.040504] usb 1-1: device v046d p081b is not supported
<6>[11735.076960] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11735.077029] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11735.237112] usb 1-1: new high speed USB device using tegra-ehci and address 4
<3>[11735.505766] usb 1-1: device v046d p081b is not supported
<6>[11735.528455] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11735.528541] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11735.687712] usb 1-1: new high speed USB device using tegra-ehci and address 5
<3>[11735.950203] usb 1-1: device v046d p081b is not supported
<6>[11735.978040] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11735.978125] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11736.137097] usb 1-1: new high speed USB device using tegra-ehci and address 6
<3>[11736.393178] usb 1-1: device v046d p081b is not supported
<6>[11736.417207] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11736.419203] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11736.580821] usb 1-1: new high speed USB device using tegra-ehci and address 7
<3>[11736.840702] usb 1-1: device v046d p081b is not supported
<6>[11736.866992] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11736.867057] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11737.027074] usb 1-1: new high speed USB device using tegra-ehci and address 8
<3>[11737.279441] usb 1-1: device v046d p081b is not supported
<6>[11737.306990] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11737.307086] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11737.467126] usb 1-1: new high speed USB device using tegra-ehci and address 9
<3>[11737.736913] usb 1-1: device v046d p081b is not supported
<6>[11737.758513] host_notify: ndev name=tegra-ehci.0: from state=5 -> to state=5
<3>[11737.758578] hub 1-0:1.0: unable to enumerate USB device on port 1
<6>[11737.916947] usb 1-1: new high speed USB device using tegra-ehci and address 10
[email protected]:/ $ dmesg
Then it goes on and on with the 'new device [...] unable to enumerate' messages until I unplug it.
The device is found, and early init seems to go through (VID/PID are correct) but it doesn't seem to make it to the uvcvideo driver (or the driver is rejecting it, I don't know).
I am not very savvy as regards to linux's USB stack (though I know my way around linux, having cross compiled it, and tweaked it several times for boards I design), so I'm a bit lost as to what I could further investigate to pinpoint the issue.
I am certain that uvcvideo is present (dmesg shows 'usbcore: registered new interface driver uvcvideo' after boot).
Things works fine when I plug in a USB flash drive.
Things works fine too when I plug the microscope to my linux desktop (through uvcvideo).
Any idea or advices would be greatly appreciated!
Thanks,
Theo
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Hi tbeauchant,
I am also looking for same , till now i didn't get any success but after going through with the code , i have seen that samsung have disable the feature of detecting a few device , in my case it says , unkown usb device and
dmesg says :: device ######(product id) ######(vendor id) not supported ,
did you get any success or any approch which you will follow.
I have noticed this morning that while my Xperia S is connected via USB cable to the PC it does not charge, ie. it indicates charging but battery level goes down rather than up. Also I've noticed that my OS (Fedora 16) stopped mounting Xperia's internal memory. Dmesg output is just that:
Code:
[34723.804074] usb 2-1.2: new full-speed USB device number 61 using ehci_hcd
[34723.877051] usb 2-1.2: device descriptor read/64, error -32
[34724.050920] usb 2-1.2: device descriptor read/64, error -32
[34724.224867] usb 2-1.2: new full-speed USB device number 62 using ehci_hcd
[34724.287808] usb 2-1.2: device descriptor read/64, error -32
[34724.461715] usb 2-1.2: device descriptor read/64, error -32
[34724.635655] usb 2-1.2: new full-speed USB device number 63 using ehci_hcd
[34725.037264] usb 2-1.2: device not accepting address 63, error -32
[34725.110414] usb 2-1.2: new full-speed USB device number 64 using ehci_hcd
[34725.512050] usb 2-1.2: device not accepting address 64, error -32
[34725.512180] hub 2-1:1.0: unable to enumerate USB device on port 2
Did a bit of research around the interwebs, found advice to clear data of the MtpApp app (settings -> applications -> all -> MtpApp), which I did but that didn't solve the problem, yet dmesg output changed a bit:
Code:
[34734.683275] usb 3-1: new full-speed USB device number 67 using xhci_hcd
[34734.686432] usb 3-1: Device not responding to set address.
[34734.890333] usb 3-1: Device not responding to set address.
[34735.091046] usb 3-1: device not accepting address 67, error -71
[34735.243993] usb 3-1: new full-speed USB device number 68 using xhci_hcd
[34735.247164] usb 3-1: Device not responding to set address.
[34735.451046] usb 3-1: Device not responding to set address.
[34735.651757] usb 3-1: device not accepting address 68, error -71
[34735.804727] usb 3-1: new full-speed USB device number 69 using xhci_hcd
[34735.807836] usb 3-1: Device not responding to set address.
[34736.011768] usb 3-1: Device not responding to set address.
[34736.212469] usb 3-1: device not accepting address 69, error -71
[34736.365416] usb 3-1: new full-speed USB device number 70 using xhci_hcd
[34736.368521] usb 3-1: Device not responding to set address.
[34736.572448] usb 3-1: Device not responding to set address.
[34736.773180] usb 3-1: device not accepting address 70, error -71
[34736.773208] hub 3-0:1.0: unable to enumerate USB device on port 1
Seems to also depend on the USB port I use in my laptop, ie. in one port it says "Device not responding", while on the other "device descriptor read/64, error -32". UPDATE: On double check it seems like USB 3.0 ports saying "not responding", while USB 2.0 port returns "descriptor error".
I obviously tried rebooting (including hard-reboot with volume-up key held), tried different cables, different PCs, including Windows one which just popped a balloon saying something about "unrecognized device". Nothing seems to rectify the issue. Needless to say it was working perfectly up until today.
Thankfully, it seems that's a software-related issue rather than physically borked USB port as I successfully managed to put device into flashmode (volume-up + usb plug). UPDATE: Unfortunately, even if physical plug to the port is recognized and green or blue light comes up, dmesg still returns "descriptor errors" and device is turning itself into charging-only mode (I initially thought just seeing blue/green light means either of modes is entered).
Running out of ideas what else I could do to get USB work again, apart from hard reset. Any suggestions more than welcome.
UPDATE: Out of the sudden, after 1525th reboot cycle somehow charging via USB cable works fine again, however internal storage is still not mounted to the PC. Doh! I guess I'll end up with warranty repair/replacement.
FINAL UPDATE: USB port died completely, plugging USB cable to the PC doesn't trigger any dmesg activity at all and handset after a while of doubt recognises connection as a standard wall charger. Sorting out warranty replacement as we speak.
Have you tried cleaning of the USB port/connector (of your phone)?
cognosco said:
Have you tried cleaning of the USB port/connector (of your phone)?
Click to expand...
Click to collapse
No, I haven't, but I doubt that's the case, as it wouldn't enter flashmode either.
I have a Huawei u8160 running Psyke83's Cyanogenmod 7.2 14/8/2012.
I've recently been testing things on my recently activated OTG I've tried to connect a USB Portable HDD, However when I connect the HDD the LED flashes like it's reading/writing , dmesg notices it :
Code:
[INDENT]
<6>[12, khubd] [10776.834610] usb 1-1.4: new full speed USB device using msm_hsusb_host and address 40
<6>[12, khubd] [10777.015514] usb 1-1.4: not running at top speed;
connect to a high speed hub
<7>[12, khubd] [10777.018517] usb 1-1.4: default language 0x0409
<7>[12, khubd] [10777.021505] usb 1-1.4: udev 40, busnum 1, minor = 39
<6>[12, khubd] [10777.021544] usb 1-1.4: New USB device found,
idVendor=174c, idProduct=5106
<6>[12, khubd] [10777.021567] usb 1-1.4: New USB device strings:
Mfr=2, Product=3, SerialNumber=1
<6>[12, khubd] [10777.021589] usb 1-1.4: Product: StoreJet Transcend
<6>[12, khubd] [10777.021607] usb 1-1.4: Manufacturer: StoreJet
Transcend
<6>[12, khubd] [10777.021624] usb 1-1.4: SerialNumber:
WD-WXF1E32VNMN1
<7>[12, khubd] [10777.022149] usb 1-1.4: uevent
done.[/INDENT]
that is what dmesg says directly after connecting.
and when I write lsusb on terminal emulator it returns :
Code:
[INDENT] Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 041: ID 058f:9254
Bus 001 Device 042: ID 174c:5106[/INDENT]
one of them is always there,and another one is the USB Hub ,and another is the USB HDD
I already successfully mounted an NTFS Flash Drive (Fromatted using Minitool partition wizard,mounted using Paragon NTFS&HFS+) then the problem isn't the File System,when connecting the HDD Paragon NTFS&HFS+ doesn't even notice it
Does your hdd have an external power supply? I am assuming no. The n7 does not output enough power to spin up an external hdd. It can see it, but thats about it. Any hdd's that have power sources external from the phone will work fine. I use an external case that is externally powered with my 1Tb sata hdd. Works great. Its all about the power.
Skyrocket on AOKP by R4ins
yes it uses external power not from my phone
Sent from my U8160 using xda app-developers app
Nexus 7 on AOKP by R4ins
rebel1699 said:
Nexus 7 on AOKP by R4ins
Click to expand...
Click to collapse
What's that supposed to mean?
ASUS TF201 / 64 gb. – No access to specific blob files.
I think I have APX mode after I run the below commands in Ubuntu
lsusb...
Bus 002 Device 085: ID 0955:7330 NVidia Corp.
and when I run
dmesg |tail
[15614.715848] usb 2-1.2: new high-speed USB device number 84 using ehci-pci
[15615.539331] usb 2-1.2: device not accepting address 84, error -71
[15615.539592] hub 2-1:1.0: unable to enumerate USB device on port 2
[15616.495015] usb 2-1.2: new high-speed USB device number 85 using ehci-pci
[15616.588212] usb 2-1.2: New USB device found, idVendor=0955, idProduct=7330
[15616.588224] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[15616.588230] usb 2-1.2: Product: APX
[15616.588236] usb 2-1.2: Manufacturer: NVIDIA Corp.
[16007.391552] systemd-hostnamed[7142]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[16008.688244] perf samples too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
I have tried Windows before Ubuntu, I was able to identify as APX in device manager but I could not understand and get any results, and decide to move to Ubuntu.
I appreciate if I can get straight answer that I can’t seem to find:
Since it’s visible as APX in ubuntu and Windows what are % chances to be recoverable?
I’m newbie and I have tried to learn as much as I can…but after a week of frustration I’m very down on energy, and lost …in commands that don’t seem to work as specified on forum.
I appreciate any help and direction on where should I start.
I'm having problems with a Chinese tablet that I believe to be a Mediatek TAB910 with a MTK6592 processor.
It started by having problems with the SIM slots which I put down to a faulty SIM card. I obtained another from the telco but that didn't solve the problem. I concluded that the problem was with the SIM slots or with the software so I did a factory reset.
That appears to have gone well EXCEPT that I cannot get past the "Enter Privacy Protection password" screen (PPP). Let me say at this stage that I have never used PINs on my SIM cards; in fact, if I put a SIM card in which has a PIN then the screen asks for and accepts the SIM PIN but still presents the PPP screen.
I have tried to connect to the tablet by USB in order to try SP FLASH, but that tool doesn't see the tablet at all.
I then tried sudo dmesg|grep usb to see if there was any recognition of the USB and got the following results:
[237820.461318] usb 1-2: new high-speed USB device number 22 using xhci_hcd
[237820.611762] usb 1-2: New USB device found, idVendor=0e8d, idProduct=2000, bcdDevice= 1.00
[237820.611773] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[237820.611779] usb 1-2: Product: MT65xx Preloader
[237820.611783] usb 1-2: Manufacturer: MediaTek
[237823.266112] usb 1-2: USB disconnect, device number 22
[237830.885144] usb 1-2: new high-speed USB device number 23 using xhci_hcd
[237831.034440] usb 1-2: New USB device found, idVendor=0e8d, idProduct=2002, bcdDevice=ff.ff
[237831.034451] usb 1-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[237831.034456] usb 1-2: Product: TAB910
[237831.034461] usb 1-2: Manufacturer: MediaTek
[237831.034465] usb 1-2: SerialNumber: 0123456789ABCDEF
[237831.038098] usb-storage 1-2:1.0: USB Mass Storage device detected
[237831.045186] scsi host2: usb-storage 1-2:1.0
[237831.471860] usb 1-2: USB disconnect, device number 23
Click to expand...
Click to collapse
It appears that the tablet is identifying itself, but immediately disconnecting again, hence no response from SP FLASH.
I can get the tablet to drop into two factory setting levels, one with English language instructions, the other with Chinese language instructions. Both of these appear to work as expected when I run through the menu items including, in the Chinese menu, "Eliminate eMMC".
I have also modified the udev files, but seemingly to no avail.
~$ cat /etc/udev/rules.d/80-persistent-usb.rules
SUBSYSTEM==”usb”, ACTION==”add”, ATTR{idVendor}==”0e8d”, ATTR{idProduct}==”2000“
SUBSYSTEM==”usb”, ACTION==”add”, ATTR{idVendor}==”0e8d”, ATTR{idProduct}==”2002“
~$ sudo service udev restart
Click to expand...
Click to collapse
My question is: Where do I go from here before I decide to bin this chablet.
TIA
For your reference.
https://visihow.com/Bypass_Privacy_Protection_Password_on_Android
James_Watson said:
For your reference.
https://visihow.com/Bypass_Privacy_Protection_Password_on_Android
Click to expand...
Click to collapse
Thanks for that but I have already been down that rabbit hole without success. My big problem is that the USB comes up but promptly disconnects again
Usually MTk preloader comport will disconnect if correct bootloader is not detected. So check you've got MTK6592 supported sp flashtool version and original firmware loaded. For privacy protection removal you need to format whole flash except bootloader and flash origin firmware then need to repair imei.
For some models you need to press and hold VOL+ or VOL- or both to get in to flash mode.