Database Users

HP Mini Note 2133 Netbook - HTC Android Phones

UPDATE - HP has given me 48 hours to provide other users with this issue, as no one has reported it directly to them besides me. If anyone has an HP mini 2133 and has the issue described below, please PM or email me ASAP with your serial number [email protected]
I am creating this thread to collect data to present to HP/HTC.
Issue:
T-Mobile G1 connected over USB to HP Mini Note 2133 (Via Chipset)
When you select Mass Storage on the G1 the computer freezes
Collecting Information:
Anyone who has an HP mini note 2133 and any HTC android phone (Dream/Magic/Ion) please PM me with your setup and results.
I have been submitting information to HPs engineering team regarding this issue there is an open ticket.
The more information we present the more likely we are to obtain a fix for the issue.
Thanks all!

just to throw it out there, I have a HP mini 1000 and everything works fine for me
What OS are you running? I can connect with XP and ubuntu 9.x on mine. What usb drivers are you using? are you sure your using 32bit/64bit where appropriate?
Try and do a thumbdrive ubuntu boot and connect through that, I bet it will work.

ggolemg said:
just to throw it out there, I have a HP mini 1000 and everything works fine for me
What OS are you running? I can connect with XP and ubuntu 9.x on mine. What usb drivers are you using? are you sure your using 32bit/64bit where appropriate?
Try and do a thumbdrive ubuntu boot and connect through that, I bet it will work.
Click to expand...
Click to collapse
I checked the specs on the 2133 and its using VIA chipset. Mini 1000 uses Intel chipset. Most likely that's the culprit (VIA chipset not playing nice).
I would hope HP's tech support suggested u install the latest drivers from their site. If not and you have not done this yourself then:
http://tinyurl.com/mjywny
Interesting situation nonetheless. Hope u get it sorted out; that would irritate the funk outta me!

the chipset is the problem - the hp mini 1000 is indeed intel, thus you have no problems. I have been working with HP Engineering to resolve - after all of my testing (different G1s - sd cards) what i really need is for someone with a magic/ion and an HP mini to try mounting to see if it occurrs with that phone - windows mobile hTC phones do not connect as mass storage so i cannot confirm that the problem is with HTC phones in general.

maubig said:
I checked the specs on the 2133 and its using VIA chipset. Mini 1000 uses Intel chipset. Most likely that's the culprit (VIA chipset not playing nice).
I would hope HP's tech support suggested u install the latest drivers from their site. If not and you have not done this yourself then:
http://tinyurl.com/mjywny
Interesting situation nonetheless. Hope u get it sorted out; that would irritate the funk outta me!
Click to expand...
Click to collapse
its not a drivers issue, the problem occurs in UBUNTU or Windows - its a firmware issue

Sorry to hear... That really sux. Well at least u can remove the TF/SD card and use a card reader (hopefully at the least the VIA chipset supports a USB card reader). Is it also affecting your ability to use adb and fastboot or just mass storage access?

yeah very crappy - the 2133 has a built in sd reader and its fine, adb and fastboot are fine as long as i dont try to access the sd card (even from shell) waiting on a callback from HP on Monday.

I have the same problem with my G1 and HP 2133. Any news about this?

Anyone? Really need to have this fixed

Actually the symptoms of it freezing happened to me many times before, until I changed the USB data cable to one that is shorter. Somehow, when I use certain cheapo USB cables, it will always either hang midway (upon transferring files) or cause a total freeze on the computer. I thought it was a driver problem, but after reading much complaints (not specific to Mini Note 2133) deduce that a change of USB cable solves the problem (apparently it has to do with some chipsets not compatible with all USB cables). Sorry, writing this after months of solving the problem (middle of last year).
Hope this helps.

I HAVE THE SAME DANG PROBLEM!!!!!!!!!!!!!!! was pickin my brain for like 3 hours trying to figure out what the hell was going on.... this explains soooo much.

erlern said:
Actually the symptoms of it freezing happened to me many times before, until I changed the USB data cable to one that is shorter. Somehow, when I use certain cheapo USB cables, it will always either hang midway (upon transferring files) or cause a total freeze on the computer. I thought it was a driver problem, but after reading much complaints (not specific to Mini Note 2133) deduce that a change of USB cable solves the problem (apparently it has to do with some chipsets not compatible with all USB cables). Sorry, writing this after months of solving the problem (middle of last year).
Hope this helps.
Click to expand...
Click to collapse
Tried different cables but no effect. Thanks anyway.

I have an Hp 2133 running Ubuntu 9.10 and it freezes if I attempt to use my HTC Desire as a modem. The phone is recognised by the OS as a wireless modem and I get 5-15 minutes of connection before the machine freezes. Nothing will bring it back after that and I have to cycle the power to get the machine back.

phlebas said:
I have an Hp 2133 running Ubuntu 9.10 and it freezes if I attempt to use my HTC Desire as a modem. The phone is recognised by the OS as a wireless modem and I get 5-15 minutes of connection before the machine freezes. Nothing will bring it back after that and I have to cycle the power to get the machine back.
Click to expand...
Click to collapse
Hi peeps,
I have the same setup and problem. I've had the desire a week. First time I connected as a modem, surfed for 15 mins, then froze. I am lucky to get 5 mins now before freeze.
It doesn't freeze when using as a drive, only modem.
I am on Telstra in Australia and haven't rooted the phone or stuffed around with it in any big way.
FRUSTRATING
Its the only drama that the 2133 has given me in over 2 years.

I have the same problem. My setup : HP2133 with Debian squeeze, HTC Dream (G1) as USB drive. Today I could catch a stack trace, that I am giving below just in case it could help solve the issue (I tried to send it to kerneloops.org but the website is down).
Kernel failure message 1:
BUG: unable to handle kernel paging request at 2f327473
IP: [<2f327473>] 0x2f327473
*pde = 00000000
Oops: 0000 [#1] SMP
last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
Modules linked in: usb_storage acpi_cpufreq cpufreq_conservative cpufreq_stats cpufreq_powersave cpufreq_userspace parport_pc ppdev lp parport bluetooth binfmt_misc uinput fuse via_chrome9 drm snd_pcm_oss snd_mixer_oss loop snd_hda_codec_analog arc4 snd_hda_intel snd_hda_codec snd_hwdep ecb snd_pcm snd_seq b43 rng_core uvcvideo snd_timer videodev snd_seq_device joydev mac80211 snd soundcore i2c_viapro v4l1_compat shpchp cfg80211 psmouse video pcspkr output serio_raw evdev snd_page_alloc wmi i2c_core battery button pci_hotplug rfkill processor ac ext3 jbd mbcache usbhid hid sd_mod crc_t10dif ata_generic ssb sata_via mmc_core tg3 libata uhci_hcd pcmcia libphy ehci_hcd scsi_mod usbcore pcmcia_core thermal thermal_sys [last unloaded: scsi_wait_scan]
Pid: 2144, comm: udisks-daemon Not tainted (2.6.32 #1) HP 2133
EIP: 0060:[<2f327473>] EFLAGS: 00010002 CPU: 0
EIP is at 0x2f327473
EAX: e712c578 EBX: e98daeb0 ECX: 2f327473 EDX: e712c578
ESI: e712c578 EDI: 0109ac40 EBP: efdc3e1e ESP: efdc3d8c
DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Process udisks-daemon (pid: 2144, ti=efdc2000 task=f5a82200 task.ti=efdc2000)
Stack:
c111c28a c1122fbc e98daeb0 00000246 e712c578 c1123463 e712c578 00070000
<0> e712c600 f7d570c6 efeedd20 efdc3e1e f5c71c00 e7109010 f7d57190 00000000
<0> 00000000 efeedd20 00001d4c 00000005 00000000 00000000 00000003 04000000
Call Trace:
[<c111c28a>] ? elv_put_request+0x10/0x11
[<c1122fbc>] ? __blk_put_request+0x60/0x8e
[<c1123463>] ? blk_put_request+0x1e/0x2e
[<f7d570c6>] ? scsi_execute+0x115/0x11c [scsi_mod]
[<f7d57190>] ? scsi_execute_req+0x58/0x83 [scsi_mod]
[<f7d5744b>] ? scsi_test_unit_ready+0x50/0xca [scsi_mod]
[<f7f34713>] ? sd_media_changed+0xde/0x17c [sd_mod]
[<c10cd7f7>] ? check_disk_change+0x16/0x3e
[<f7f324d8>] ? sd_open+0xc2/0x153 [sd_mod]
[<c10ce091>] ? __blkdev_get+0xae/0x2c0
[<c10ce306>] ? blkdev_open+0x5c/0x87
[<c10adf39>] ? __dentry_open+0x156/0x235
[<c10ae0ae>] ? nameidata_to_filp+0x2a/0x3b
[<c10ce2aa>] ? blkdev_open+0x0/0x87
[<c10b8819>] ? do_filp_open+0x443/0x7e3
[<f7d52779>] ? T.807+0x48/0x123 [scsi_mod]
[<f7d51119>] ? scsi_device_put+0x21/0x2e [scsi_mod]
[<f7f31b09>] ? scsi_disk_put+0x20/0x2c [sd_mod]
[<c10bfacd>] ? alloc_fd+0x4f/0xb1
[<c10adcf0>] ? do_sys_open+0x49/0xdd
[<c1135732>] ? copy_to_user+0x2c/0x100
[<c10addc8>] ? sys_open+0x1e/0x23
[<c100305b>] ? sysenter_do_call+0x12/0x28
Code: Bad EIP value.
EIP: [<2f327473>] 0x2f327473 SS:ESP 0068:efdc3d8c
CR2: 000000002f327473
---[ end trace 75f7276db9ecf1ff ]---

[Q] Aaaaarrrrgh. USB drivers not working under Windows 7/64

OK, I've now officially burned 4 hours trying to get my Epic to work properly with Windows 7 (64 bit) for anything besides mounting it as a USB drive.
I tried the (32-bit?, and only?) driver Samsung seems to officially have for the Epic 4G.
I tried the 64-bit driver(s) apparently intended for Kies.
I've installed, uninstalled, shutdown-after-uninstall-instead-of-reboot, and sacrificed 3 chickens to the appropriate gods.
I temporarily made TouchWiz the homescreen instead of LauncherPro.
I made sure the phone was in "PDA" mode and NOT "modem" mode (##8778##, I think).
I've updated everything Windows Update will touch, then installed the Asus P5N-D motherboard chipset drivers straight from Asus' international site, just for good measure.
I've attempted to upgrade the Google USB driver through tools (the app that gets launched when you just type "android" from a command prompt).
Oh, I also made sure that USB Debugging was NOT enabled when I connected the phone for the first time after supposedly installing the Samsung USB drivers. Two of the drivers installed correctly. Then I enabled USB debugging, reconnected USB, and ended up (for the Nth time):
SAMSUNG Android USB Composite Device: v/ Ready to use
CDC Abstract Control Model (ACM) O Installing driver software... (for 20+ minutes)
S3C6410 Android ADB O Installing Driver Software (for 20+ minutes)
USB Mass Storage Device v/ Ready to use
For the record, I have a core2quad 9600 running at ~2.6GHz with SSD, so it seems almost inconceivable that it could legitimately take 20+ minutes to install ANYTHING.
In Device Manager, I have at least one "Other Devices" entry that just refuses to die -- Universal Serial Bus (USB) Controller. I've tried deleting it, uninstalling it, uninstalling it and shutting down (vs restarting windows), the works. NOTHING will kill it, or at least it won't stay dead when I try. Worse, when I try reinstalling the Samsung drivers, I usually get a message along the way that installation of the drivers for the Universal Serial Bus (USB) Controller failed, even though it's not even connected.
This is driving me insane. It worked fine under Vista/32, but I've never been able to get it to work properly since I got the SSD and Win7/64. Specifically, I've never been able to get ADB to work, and the USB driver situation appears to be completely fsck'ed.
Is there some secret strategy I'm forgetting for making Windows forget everything it thinks it knows about a corrupted USB driver installation and making it start over from a clean slate? I think the problem is that I have a driver that's latched onto something, refuses to be deleted, and won't allow itself to be overwritten.
Before I waste any more time on this, can anybody recommend any specific things to try? I have to get this working tonight

bitbang3r said:
OK, I've now officially burned 4 hours trying to get my Epic to work properly with Windows 7 (64 bit) for anything besides mounting it as a USB drive.
I tried the (32-bit?, and only?) driver Samsung seems to officially have for the Epic 4G.
I tried the 64-bit driver(s) apparently intended for Kies.
I've installed, uninstalled, shutdown-after-uninstall-instead-of-reboot, and sacrificed 3 chickens to the appropriate gods.
I temporarily made TouchWiz the homescreen instead of LauncherPro.
I made sure the phone was in "PDA" mode and NOT "modem" mode (##8778##, I think).
I've updated everything Windows Update will touch, then installed the Asus P5N-D motherboard chipset drivers straight from Asus' international site, just for good measure.
I've attempted to upgrade the Google USB driver through tools (the app that gets launched when you just type "android" from a command prompt).
Oh, I also made sure that USB Debugging was NOT enabled when I connected the phone for the first time after supposedly installing the Samsung USB drivers. Two of the drivers installed correctly. Then I enabled USB debugging, reconnected USB, and ended up (for the Nth time):
SAMSUNG Android USB Composite Device: v/ Ready to use
CDC Abstract Control Model (ACM) O Installing driver software... (for 20+ minutes)
S3C6410 Android ADB O Installing Driver Software (for 20+ minutes)
USB Mass Storage Device v/ Ready to use
For the record, I have a core2quad 9600 running at ~2.6GHz with SSD, so it seems almost inconceivable that it could legitimately take 20+ minutes to install ANYTHING.
In Device Manager, I have at least one "Other Devices" entry that just refuses to die -- Universal Serial Bus (USB) Controller. I've tried deleting it, uninstalling it, uninstalling it and shutting down (vs restarting windows), the works. NOTHING will kill it, or at least it won't stay dead when I try. Worse, when I try reinstalling the Samsung drivers, I usually get a message along the way that installation of the drivers for the Universal Serial Bus (USB) Controller failed, even though it's not even connected.
This is driving me insane. It worked fine under Vista/32, but I've never been able to get it to work properly since I got the SSD and Win7/64. Specifically, I've never been able to get ADB to work, and the USB driver situation appears to be completely fsck'ed.
Is there some secret strategy I'm forgetting for making Windows forget everything it thinks it knows about a corrupted USB driver installation and making it start over from a clean slate? I think the problem is that I have a driver that's latched onto something, refuses to be deleted, and won't allow itself to be overwritten.
Before I waste any more time on this, can anybody recommend any specific things to try? I have to get this working tonight
Click to expand...
Click to collapse
I had the same problem, but found out that its all b/c of my cheap 99cent usb cable. When I use the official usb cable that came with the phone it works fine.

Argh. It appears I've forgotten rule #27,326 of Android -- don't believe the error messages. Half the time they're wrong, and the other half of the time something is lying to you. Despite having the USB driver that I can't get rid of or fix and the error messages announcing that installation failed, it seems to work. At least, adb logcat works, and I was able to deploy an app from Eclipse to the phone right now.
(goes to bash head against wall in frustration)
Oh, I'm using the cable that came with the phone ;-)

Which particular driver did you end up with? I tried using the Samsung Moment drivers (saw a vid on Youtube using these as a substitute for the Intercept handset), and though I got similar errors as you - and supposed fixes - my Eclipse was never able to connect to the handset to debug an app, grab screen shots, or anything. Would love to figure out how to get my Intercept to work with my Win 7 64-bit setup.

First of all, a large number of people (myself included) agree that the stock USB-microUSB cable sucks balls. I ran into the same problems you're having, and then they magically went away when I replaced my cable. You can find super-cheap cables on Amazon.com, or if you're a "gotta have it now!" type I know the Radio Shack cable works great, I have it.
Secondly, I know the drivers on http://forum.xda-developers.com/showpost.php?p=7933592&postcount=1 work, they're what I'm using.
I would imagine you just need to replace that stock cable. Sometimes certain things will work, but I had almost exactly the same problems as you and they all went away when I changed my cables.
Also, try to use a USB socket that's directly attached to your motherboard, i.e., a USB port on the back of your PC, as apposed to front- or top-mounted USB ports, since those add extra hardware and connections that could decrease reliability.
Good luck!

For what it's worth, I am using the drivers from Samsungs website on all of my windows 7 x64 computers. Haven't had any problems.
Sent from my SPH-D700 using XDA Premium App

Use this to remove any residual drivers from your computer before installing your new drivers. It is a very useful tool when you have driver conflicts that may be happening.
http://www.multiupload.com/3PC2BBAFSO
Then use these drivers, they've worked on my many machines with Win 7 64 bit:
http://www.multiupload.com/LLOCCAMUT4
Wow just realized how old this thread is. LOL

heathmcabee said:
Wow just realized how old this thread is. LOL
Click to expand...
Click to collapse
Hmmm, I hadn't realized that! Why the Hell did CirrusFlyer resurrect this thread?

I had the same problem and the problem ended up being my new dell xps core i7 tower. Use a powered usb hub such as your monitor with the usb hub ( if you have one) and it will solve your headaches. I am willing to bet money this will work, everyone I know that has had the same problem has solved it this way.
Sent from my SPH-D700 using XDA Premium App

The usb socket directly attached to my motherboard was the problem a powered usb hub for some weird reason made it driver up every damn time and still works today.
Sent from my SPH-D700 using XDA Premium App

Cpagent is 100% correct on the powered usb port causing issues. And that goes for multiple devices for an assortment of usb drivers... I have to deal with it all the time with my customers (that's assuming I've already exhausted every other software possibility... for this reason I only work on customers phones on an older xp 32 pc with proper hardware) it really ticks me off how little software developers.care about adapting basic drivers to be compatible with the machines most commonly used by the people who actually have to use said software/hardware ...
Lol.... /rant
Sent from my DROIDX using XDA App

Still nothing. CDC serial is not installed.

sly21 said:
Still nothing. CDC serial is not installed.
Click to expand...
Click to collapse
That one is a Pain in the ass. Took 35 minutes on my laptop!
Sent from my SPH-D700 using XDA App

Trying to diagnose my USB modem on android, tips?

So i have a CA-FI 7008000 android powered car stereo, it is a freescale based android 2.2 device with a USB host port dedicated for usb modems. Currently I am attempting to use the Sierra wireless 313u (att momentum 4g ) with it. When plugged in, it powers on and status lights begin blinking indicating it does see a network, but does not connect (light should go solid). Currently it isplugged into the correct port and is in Modem only mode. I have verified the device works on windows and a mac.
I've done a fair amount of hacking in android, but I'm beyond lost with this.
under dmesg in terminal im getting **** like this:
<6>usb 1-1: new high speed USB device using fsl-ehci and address 5
<4>usb 1-1: config 1 has an invalid interface number: 7 but max is 3
<4>usb 1-1: config 1 has no interface number 2
any ideas?

It sounds like either the USB descriptors in the device are a bit flakey or else your Linux is.
You can use usbview.exe under Windows (although it's ancient).
http://www.ftdichip.com/Support/Utilities.htm
Copy out the right hand pane for your modem.

[Q] USB device not recognized

I can't connect my phone to laptop it always shows it as unknown device .I have uninstalled it couple of in device manager and plugged it still same even its in USB debugging enabled .keep rebooting my laptop and keep trying still the same
Turn my off plug it to laptop them turn on still Its window 7. Tell me what to do ????? I think! It was rooted then I got OTA update (I was new I didn't know that I shouldn't install that I was happy to install on my rooted phone ) that's from where problem started I think.now I want to root my phone but it's not connecting .HELPPP

binsalamat said:
I can't connect my phone to laptop it always shows it as unknown device .I have uninstalled it couple of in device manager and plugged it still same even its in USB debugging enabled .keep rebooting my laptop and keep trying still the same
Turn my off plug it to laptop them turn on still Its window 7. Tell me what to do ????? I think! It was rooted then I got OTA update (I was new I didn't know that I shouldn't install that I was happy to install on my rooted phone ) that's from where problem started I think.now I want to root my phone but it's not connecting .HELPPP
Click to expand...
Click to collapse
Try reinstalling the drivers and/or use a different usb cable or different jack.

Believe me I have done all that different cable and PC reset my phone reset my PC .just because I have rooted my phone I can't send it for replacement and I can't unroot it without connect to PC and that is the problem .I'm here because this is my last hope .
Sent from my Nexus 4 using xda app-developers app

any updates on this?
i'm having the same problem. my n4 is not recognized - i've tried three different computers and i can't even get it to show up so i can move files in/out of the phone.
i bought this n4 used from kijiji. i just want to get it back to complete stock form with locked bootloader.
i've tried three different machines all windows 7 x64 - might try an xp machine but i think it's the phone
factory reset the phone
tried with and without usb debugging
tried 4 different cables
phone has unlocked bootloader
cannot get into recovery, i get an triangle with robot lying down
phone shows up as unrecognized usb device

binsalamat said:
Believe me I have done all that different cable and PC reset my phone reset my PC .just because I have rooted my phone I can't send it for replacement and I can't unroot it without connect to PC and that is the problem .I'm here because this is my last hope .
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
If you have an unlocked bootloader use this tool to lock it: https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
To unroot use the permanent unroot feature in SuperSU.
Order is important since the Bootloader tool requires root.
Sent from my Nexus 4 using xda app-developers app

binsalamat said:
I can't connect my phone to laptop it always shows it as unknown device .I have uninstalled it couple of in device manager and plugged it still same even its in USB debugging enabled .keep rebooting my laptop and keep trying still the same
Turn my off plug it to laptop them turn on still Its window 7. Tell me what to do ????? I think! It was rooted then I got OTA update (I was new I didn't know that I shouldn't install that I was happy to install on my rooted phone ) that's from where problem started I think.now I want to root my phone but it's not connecting .HELPPP
Click to expand...
Click to collapse
SeraldoBabalu said:
any updates on this?
i'm having the same problem. my n4 is not recognized - i've tried three different computers and i can't even get it to show up so i can move files in/out of the phone.
i bought this n4 used from kijiji. i just want to get it back to complete stock form with locked bootloader.
i've tried three different machines all windows 7 x64 - might try an xp machine but i think it's the phone
factory reset the phone
tried with and without usb debugging
tried 4 different cables
phone has unlocked bootloader
cannot get into recovery, i get an triangle with robot lying down
phone shows up as unrecognized usb device
Click to expand...
Click to collapse
Try following these directions to properly install the Google drivers.
http://forum.xda-developers.com/showthread.php?t=1830108

Thanks for your response!
Do still have that problem ?
How did slove it?
Sent from my Nexus 4 using xda app-developers app

thanks. i installed the android sdk and java jdk but still have the problem. i believe the problem is with the phone 100%
my nexus always shows that it's charging on AC whenever plugged in. doesn't matter if it even is to AC or USB. the phone shows up as unrecognized device with a bang in the USB section of the device manager. on some computers it doesn't even show up.
i tried on my macbook pro and it doesn't even show up there but in every case, the phone charges.
wondering if there's a switch or toggle somewhere that will turn it on and get it working
i'm going to install a windows xp VM as a last ditch resort and see if it at least shows up there.

SeraldoBabalu said:
thanks. i installed the android sdk and java jdk but still have the problem. i believe the problem is with the phone 100%
my nexus always shows that it's charging on AC whenever plugged in. doesn't matter if it even is to AC or USB. the phone shows up as unrecognized device with a bang in the USB section of the device manager. on some computers it doesn't even show up.
i tried on my macbook pro and it doesn't even show up there but in every case, the phone charges.
wondering if there's a switch or toggle somewhere that will turn it on and get it working
i'm going to install a windows xp VM as a last ditch resort and see if it at least shows up there.
Click to expand...
Click to collapse
Make sure your device is on MTP and try an other data cable which has no missing/broken data wires inside.
Sent from my Nexus 4 using xda app-developers app

yep it tried on mtp and ptp with 4 different cables. two original nexus 4 cables, one nexus 7 cable and a blackberry cable. they all work with my other nexus 4... just not this one.
the windows VM didn't work unfortunately.

SeraldoBabalu said:
yep it tried on mtp and ptp with 4 different cables. two original nexus 4 cables, one nexus 7 cable and a blackberry cable. they all work with my other nexus 4... just not this one.
the windows VM didn't work unfortunately.
Click to expand...
Click to collapse
That is strange, it should work with the Windows Virtual Machine.
Maybe it is to do with the standalone machine using it in the same time.
Sent from my Nexus 4 using xda app-developers app

Same problem here. USB is not recognized using my Nexus 4 ( it used to be recognized on two PCs, but no longer), but another Nexus 4 connects perfectly. I can only charge a USB rate on chargers that used to charge at ac rate. I've tried everything, and more than mentioned in this thread.
LG-E960, Tapatalk b4

I've ordered a replacement USB port via Amazon for $23. Once I install it, I'll update this thread.
LG-E960, Tapatalk b4

Hi guys,
Seems that I've got the same trouble. Got my N4 (stock ROM, 4.2.2) a couple of weeks ago and everything was ok - connection as MTP, connection for debug and so on. But yesterday I connected it to my PC and found that the device indicates charging but not USB connexion. So I've tried to reboot PC and N4, tried other cables and 2 other PCs (my with Win8, and those with Win7 and Linux Mint if matters). Other devices are ok (Huawei Honor, N7, Milestone2).
The phone just doesn't detect USB connection - in both MTP and PTP. Then I tried to plug in wall charger and connect back again to USB. AND IT WORKED! The phone detected the connection so I was able to mount it and detect with adb. I thought that the problem was solved but when I connected it next time - same ****. This time nothing helps (most likely that there wasn't any casual relationship between wall charger connection and temporary fix...)
What options I've got now? Try to root the device and look into syslog to detect if it's a software issue or disassemble the device and try to find any defects on USB port?
Thank you,
Alex

allookin said:
Hi guys,
Seems that I've got the same trouble. Got my N4 (stock ROM, 4.2.2) a couple of weeks ago and everything was ok - connection as MTP, connection for debug and so on. But yesterday I connected it to my PC and found that the device indicates charging but not USB connexion. So I've tried to reboot PC and N4, tried other cables and 2 other PCs (my with Win8, and those with Win7 and Linux Mint if matters). Other devices are ok (Huawei Honor, N7, Milestone2).
The phone just doesn't detect USB connection - in both MTP and PTP. Then I tried to plug in wall charger and connect back again to USB. AND IT WORKED! The phone detected the connection so I was able to mount it and detect with adb. I thought that the problem was solved but when I connected it next time - same ****. This time nothing helps (most likely that there wasn't any casual relationship between wall charger connection and temporary fix...)
What options I've got now? Try to root the device and look into syslog to detect if it's a software issue or disassemble the device and try to find any defects on USB port?
Thank you,
Alex
Click to expand...
Click to collapse
I got mine to work by using a 2 into 1 usb plug. The kind that comes with portable CD writers. Once I got it working I reflashed stock 422 and the problem is gone. Turns out it was a bad flash from the previous owner.
Sent from my Nexus 4 using Tapatalk 2

SeraldoBabalu said:
I got mine to work by using a 2 into 1 usb plug. The kind that comes with portable CD writers. Once I got it working I reflashed stock 422 and the problem is gone. Turns out it was a bad flash from the previous owner.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for advice. During this day it worked properly twice - the phone just started detecting connection. No obvious reasons for that... I got a new device with stock 422 from amazon and haven't flashed or event rooted it. How do you think, should I try to flash it with official 4.2.2? Now I can say that it's most likely a software issue.

allookin said:
Thanks for advice. During this day it worked properly twice - the phone just started detecting connection. No obvious reasons for that... I got a new device with stock 422 from amazon and haven't flashed or event rooted it. How do you think, should I try to flash it with official 4.2.2? Now I can say that it's most likely a software issue.
Click to expand...
Click to collapse
I'd say try a factory reset first and see how that works.
Sent from my Nexus 4 using Tapatalk 2

SeraldoBabalu said:
I'd say try a factory reset first and see how that works.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Tried it out - the result is the same. Now I can not even unlock the bootloader to reflash 422... Btw I didn't managed to find a 2into1 cable but checked if the same trick would work with USB hub with external power - it works really better. The device can detect the connection almost all the times and I can see it listed in adb devices and as a mounted storage. Though in fastboot mode this doesn't help. Device remains unrecognized.

allookin said:
Tried it out - the result is the same. Now I can not even unlock the bootloader to reflash 422... Btw I didn't managed to find a 2into1 cable but checked if the same trick would work with USB hub with external power - it works really better. The device can detect the connection almost all the times and I can see it listed in adb devices and as a mounted storage. Though in fastboot mode this doesn't help. Device remains unrecognized.
Click to expand...
Click to collapse
well if you're getting a connection to the computer but not in fastboot, your drivers might just need removal/reinstallation.
once you get it going, reflash the stock 4.2.2 from google and see how it goes.
if that doesn't work and you can get it going, get it replaced by Google.
if you can, try it on a mac.. they don't need the drivers installed. just run it all from terminal.

Okay, I've managed to track down the issue...
Once I got it available for fastboot I've unlocked bootloader and then flashed with Cyanogen. The problem remained but I could get dmesg output for plug-in event. I've managed to get logs for problematic case (doesn't detect USB data connexion) and for correct behavior case (when Android detects USB data connection).
No sense to put the whole log pieces here just a brief quotes.
For correct case:
Code:
Avail curr from USB = 500
For incorrect case:
Code:
Avail curr from USB = 1500
USB module firmware tells the system that it has detected data-connection and enabled low-power mode (500mA). In this case Android initiates mtp and adb:
Code:
<6>[62539.001178] adb_open
<6>[62539.001269] mtp_bind_config
<6>[62539.001422] adb_bind_config
And in problematic case USB module firmware incorrectly indicates for the OS that there are only power-connection (5V/ground). I cant say exactly where the issue is but there are only two options - bug in USB module firmware or physical fault of connection (pins, bus or whatever else). Anyway I've to replace USB module or just go with it and use adb over network (the matter is that sending the device back to Amazon seller from my country would cost me 1/3 of the purchase total so I consider that just unreasonable).
Thanks to LG - for my money I got not only a box with device but also whole lotta fun =)

Nook Simple Touch USB Mode Almost Working

Hello, I am trying to hack my Nook Simple Touch 1.2.1 to work with a keyboard or mouse. In order to do this, I followed the instructions here: https://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/USB_host_mode. The instructions basically worked, except I had to make one small modification. On step 3 (https://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Replacing_boot_files), I had to do the command:
cd /data/local/tmp
in between lines 2 and 3 of the terminal method. (As suggested on my previous forum post here: https://forum.xda-developers.com/nook-touch/general/boot-partition-trying-to-install-usb-t3753107)
This appears to have worked in the sense that I have a USB mode utility app now, but I'm encountering problems when actually trying to connect the keyboard/mouse. I bought 2 different USB to microusb adapters, one of which also accepts external power through another female microusb port. Here they are: https://www.amazon.com/gp/product/B00M7X6XNG/ref=oh_aui_search_detailpage?ie=UTF8&psc=1
https://www.amazon.com/UGREEN-Adapt...ords=usb female to micro usb male otg adapter
I open the USB mode utility app, hit the off button on the current limit section. It tells me that Superuser permissions are now enabled. I then hit Host several times, and then I plug in the keyboard or mouse.
With the non-externally powered cable, nothing happens. With the externally powered cable, power switches from battery to usb, and input switches from Key:3 to Key:4. In the latter case, if I then click on view usb, it correctly lists the device information of the keyboard or mouse that is plugged in. For example, for the mouse, it displays:
1d6b:0002:01 MUSB HDRC host driver
1038:1361:00 Steel Series
However, in any app I then try, the keyboard and mouse don't do anything. For example, I can't get the keyboard to input text into text boxes. Basically, except for the view usb output, it's as if the device isn't plugged in.
So I have 2 questions:
1. How do I get the nook to actually recognize the input from these devices?
2. Is it possible to do this without external power? If so, why isn't it working with the non-externally powered cable?
Thanks

Either of those adapter should be fine.
When the tree is showing a keyboard do you see #0 - 03:01:01 HID (boot) and #1 - 03:00:00 HID?
There should (probably) be two interfaces and two check marks.
When you go back to the main screen of UsbMode can you twiddle the keyboard keys and see scan & key codes?
Do you have a /system/usr/keylayout/qwerty.kl?
What does dmesg say?
Code:
# dmesg
Start with a USB OTG adapter and a powered hub until you get the problems ironed out.
You can get a mouse to work, but the behavior is a bit strange.

When I hit usb, if the device is plugged in, its info shows up after the second (indented) 1 in a box. For the mouse, it doesn't have anything under it. But for the keyboard, it has: #0 3:01:01 HID boot (checkmark). No #1 3:00:00 though.
With the keyboard, I went back to the main USB mode screen, and mashed the keys/pressed every key on the keyboard. Nothing on the nook changed, including the scan and key codes. They remained blank. I did notice that the num lock key lighted up the keyboard num lock indicator though, so I guess it's at least getting adequate power. Although this is only after restarting a plugging in and out a bunch of times because the cable/connection is a bit janky.
I do have /system/usr/keylayout/qwerty.kl, other files in that folder include: AVRCP.kl, TWL5030_Keypad.kl,gpio-keys.kl, and omap_tw14030keypad.kl
dmesg (from this location, if that matters) outputs more than a hundred lines, so I would prefer not to copy them word by word. What are you looking for specifically? Notable lines include:
[random #.random #] zforce-ts 2-0050 invalid_frame: 255
[random #.random #]usb 1-1: new full speed USB device using musb_hdrc and address 5
[random #.random #]usb 1-1: device v1038 p1361 is not supported
[random #.random #]usb 1-1: rejected 1 configuration due insufficient bus power
[random #.random #]usb 1-1: new low speed USB device usir
[random #.random #] regulator regulator, 5: enabling charge: USB HID v1.10 keyboard...
[random #.random #] usb 1-1: device not accpeting addresss 15: error -110
[random #.random #] usb 1-1: device descriptor read/64, error -110
[random #.random #] hub 1-0: 1,0 unable to enumerate device on port 1
Looks like it fails for various different reasons, seemingly dependent on the power source, restarting, and how carefully I plug it in.
Thanks again for all your help!

-110 is timeout on the USB, it seems to be flailing.
Did you try using a powered hub?
A "SteelSeries ApS Ideazon Sensei" keyboard?
How about trying a crappy $3 keyboard?
I'd like to know what the configuration descriptor is quoting for bus power, I've not seen that "rejected 1 configuration due insufficient bus power" before.
If you use Windows (or Linux), try UsbView.exe on it from the good folks at FTDI: http://www.ftdichip.com/Support/Utilities.htm
Here's a typical device:
Code:
Configuration Descriptor:
wTotalLength: 0x0029
bNumInterfaces: 0x01
bConfigurationValue: 0x01
iConfiguration: 0x04
0x0409: "Default"
bmAttributes: 0x80 (Bus Powered )
MaxPower: 0x32 (100 Ma)

I tried the standard dell keyboard with a powered hub. It didn't even appear to recognize it unless I used the adapter cable again with external power (which makes much less sense now, because the hub is definitely powered--the num lock key was lighting up before attaching the hub to the adapter). When I did plug it in with the powered adapter (so I had dell keyboard-->powered usb hub-->usb to microusb with a separate microusb power input from the wall-->nook), it was recognized, but performed essentially the same (showed up under viewusb, but didn't register any inputs). I'm attaching a picture of what the viewusb came up with.
Additionally, I tried a really crappy old apple keyboard, which again was recognized, but didn't register input. Looking at dmesg, this error came up (I think) every time:
usb 1-1: new low speed usb device using musb_hdrc and address 7
usb 1-1: device v413c p2005 is not supported
So possibly I just have to use yet another keyboard? I don't have a steelseries keyboard--the steel series thing was the mouse I was plugging in.
I am additionally attaching the outputs from usbview on the dell keyboard and the crappy apple keyboard.

Oops , looks like the usbview.exe output files didn't get attached. Here they are!

Mmm, something goofy is going on
Code:
<7>[ 387.083526] usb 1-1: default language 0x0409
<3>[ 387.093414] usb 1-1: device v04d9 p1503 is not supported
<6>[ 387.098968] usb 1-1: New USB device found, idVendor=04d9, idProduct=1503
Even though I copied qwerty.kl over:
Code:
-rw-r--r-- root root 3123 2012-04-15 10:20 qwerty.kl
-rw-r--r-- root root 3123 2018-04-04 20:23 Vendor_04d9_Product_1503.kl
Maybe the NST didn't use that system, G2 & G3 did.
In any case, my NST still works fine without a specifically matching kl.
Android supposedly looks in eight places for a match: https://source.android.com/devices/input/key-layout-files
If it fails it should fall back to qwerty.kl

One notable thing is that when following the initial install instructions, I accidentally installed usbmode.apk before changing the boot files like you're suppposed to. The nook started giving me an "install failed" lock screen when it idled for long enough. I then realized the problem, switched the boot files, then reinstalled usbmode. Do you think that could be causing the problem? I could try factory resetting and starting over, although I'm not sure if it would help.

There shouldn't be any problem when you installed UsbMode.apk, it's only an app.
The NST's Eclair doesn't use /system/usr/idc like the later Android.
I renamed /system/usr/keychars and system/usr/keylayout to garbage.
When a keyboard is attached and twiddled it all acts as a home key.
Does the cap locks cause the cap lock light on the keyboard to go on and off?

When connected correctly (which is getting harder and harder over time), the caps lock and num lock lights are both toggled by the corresponding keys. But the keyboard still doesn't seem to register at all on the nook--no key codes, no home button functionality, etc.

Does the soft keyboard work correctly?
It's a little bit more difficult to debug when you have the choice of either ADB or keyboard.
If you had a hardware console, a rooted terminal app or ADB over WiFi it might be easier.
This will dump out info as long as the keyboard was inserted and working once:
Code:
# cat /proc/bus/input/devices
...
I: Bus=0003 Vendor=04d9 Product=1503 Version=0110
N: Name="USB Keyboard"
P: Phys=usb-musb_hdrc-1/input0
S: Sysfs=/devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/input/input23
U: Uniq=
H: Handlers=kbd event3
B: EV=120013
B: KEY=10000 7 ff800000 7ff febeffdf f3cfffff ffffffff fffffffe
B: MSC=10
B: LED=7
...
There could be two interfaces.

Yes, the on screen touch keyboard on the nook works fine. I actually do have an ADB Konnect app, and I think it works. I start it on the nook, type in adb connect 192.whatever on my computer, and it says it's connected. Just not sure what to type then; if I enter commands just like into the terminal app on the nook it looks for files and folders on my computer, not on the nook. Getting this to work seems like a good idea though; it would certainly be a lot easier than retyping all the really tiny hard to read output from the nook terminal app.
In the terminal app, cat /proc/bus/... produces the following output:
I: Bus=0019 Vendor=0001 Product=0001 Version=0003
N: Name="TWL 4030 Keyboard"
P: Phys=twl4030_keyboard/input0
S: Sysfs=/devices/platform/i2c_omap.1/i2c-adapter/i2c-1/1-004a/tw14030_keypad/input/input0
U: Uniq=
H: Handlers=kbd event0
B: EV=3
B: KEY=similar long #s
then same paragraph except replace twl keyboard with gpio-keys, and the various numbers change slightly
then same paragraph except replace gpio-keys with zForce Touchscreen
Notably, there is no line after the "B KEY=number" line in the first two paragraphs, but for the third one (the touchscreen),
there is the line: ABS=600000 3. Not sure if that's important.

You're not seeing the USB keyboard at all.
The TWL4030 is the 4 side buttons on the Nook (which are scanned directly by hardware).
The gpio-keys is the power and home button (which are handled by software).
The B:KEY is a bitmap of allowed scancodes.
My button box has 4 scancodes, 1-4 and B:KEY = 1e = 11110
If you got that while the keyboard was connected (and you can get the LEDs to toggle) then there's the problem.
After adb connect 192.XX.XX.XX you should type "adb shell".

The adb part worked great! I can now debug from the computer, so I should be able to copy the full output of long logs for you from now on.
I didn't realize that you wanted me to connect the keyboard while running that command (I thought you meant if it had been connected before it would be ok). I will try it again with the keyboard connected.

Ok, here's the output of the cat line from wireless adb, after successfully connecting the keyboard with the powered adapter. I checked that num and caps lock keys were lighting up the indicators immediately before inputting the line.
Code:
I: Bus=0019 Vendor=0001 Product=0001 Version=0003
N: Name="TWL4030 Keypad"
P: Phys=twl4030_keypad/input0
S: Sysfs=/devices/platform/i2c_omap.1/i2c-adapter/i2c-1/1-004a/twl4030_keypad/in
put/input0
U: Uniq=
H: Handlers=kbd event0
B: EV=3
B: KEY=10800000 0 0 0 0 0 0 0 40000800 0 0 0 1
I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="gpio-keys"
P: Phys=gpio-keys/input0
S: Sysfs=/devices/platform/gpio-keys/input/input1
U: Uniq=
H: Handlers=kbd event1 as3676
B: EV=3
B: KEY=100040 0 0 0
I: Bus=0018 Vendor=0000 Product=0000 Version=0000
N: Name="zForce Touchscreen"
P: Phys=
S: Sysfs=/devices/virtual/input/input2
U: Uniq=
H: Handlers=event2
B: EV=b
B: KEY=400 0 0 0 0 0 0 0 0 0 0
B: ABS=600000 3
I: Bus=0003 Vendor=413c Product=2005 Version=0110
N: Name="DELL DELL USB Keyboard"
P: Phys=usb-musb_hdrc-1/input0
S: Sysfs=/devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/input/input3
U: Uniq=
H: Handlers=kbd event3 as3676
B: EV=120013
B: KEY=10000 7 ff9f207a c14057ff febeffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

also, attatched is the (almost) complete output from dmesg. the command prompt stopped letting me scroll up (might have gotten overloaded by the amount of text), so it's cut off at the top, I don't know how much.

Your dmesg is a train wreck!
You should not be having crashes.
Put the Dell keyboard aside. It's quoting 100 mA which may be the problem.
Use the Apple or another keyboard or even a mouse.
Use a powered hub until you get things working.
Your next experiment: If you find your keyboard in /proc/bus/input/devices, look for the event#.
Then:
Code:
cat /dev/input/event# [color=red]<- whichever number it is, event2 or something[/color]
Then twiddle keys, you should get a burst of garbage with each key.
Does your OTG adapter work on other things, your phone?

OK, I attatched a newer keyboard (logitech K120), through a powered hub. I tried the cat line with the event number, and pressing keys produced garbage output, just like you said! However, the keyboard still doesn't seem to provide any input to the nook. Also I retested the non-externally-powered otg adapter (because it seems like it should have enough power now that I'm using the usb hub), but it still doesn't do anything.
I'm not sure what you mean about using the otg cable with other things. Like I wouldn't expect my phone to know what to do when I plug a keyboard into it through the adapter. I tried this (with the externally powered one), and the phone did start to charge. But it didn't do anything else.

mysteriousmonkey29 said:
The nook started giving me an "install failed" lock screen when it idled for long enough.
Click to expand...
Click to collapse
Did you figure out the "install failed" when it sleeps issue? i have two NST that I cloned i thought way back, i can't remember even how I rooted them it's been so long. But one of them does this, and it's super annoying. It's about to sleep but instead it reboots then tries to install something and fails. Requires reboot.

No, never fixed this. I bet I could fix it by wiping the nook, re-rooting, and re-installing usbmode, etc. (in the correct order this time), but that's a pain, so I would prefer not to unless necessary.
Although maybe we are headed in that direction.