Related
Does anyone use the micro usb port? I have yet to find a use for it. I can't transfer files with it, charge with it nor are there any peripherals (that I know of) that can use it. I searched around but couldn't find much useful stuff on the port. All I found was this useless video:
**Ok I can't post the video because of more stupid forum rules but just go to youtube.com and append this after the url: /watch?v=1xBVu-IatDQ **
Anyway, if someone has ideas on how this port can be used I'm all ears... Thanks.
dq
It is a file transfer port. you plug a cable into it and into your PCs usb port. works like the ones on your phone.
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
What OS are you using on your computer, and have you installed the drivers for it?
don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
Computer OS? i just plugged it into my Win7 system and it was there instantly. 3.0 shows up as a media device, which allows both the tablet and the computer to talk to the sdcard at the same time. So you won't see a mount prompt on the tablet. BTW my Incredible2 is running 2.3 and also lets me access the SD card on it and the computer at the same time.
I'm still using an old tiny xp and it worked fine for me just plugged it in and there it was
I tried Gentoo Linux and XP and neither worked. What drivers do I need to install?
I also have access to a Win7 system so I'll try that.
dq
Drivers from acer website.
I have adb installed should this not be enough?
You need none installed. ADB if its running in some form might be interfering. its just a basic driver in windows it uses.
I only run adb-server when I need it and not all the time. I thought that any needed drivers would have been installed when I installed adb.
For my Gentoo machine what should I do? It's not detected at all if I plug it in. My x10 mini and Nexus One are detected no problem and I can mount them and everything so what's up? Is there a kernel module that I need to build?
Thanks.
dq
I had to download these drivers for my xp netbook ,,
http://global-download.acer.com/GDF...A Tab&Step3=A500&OS=a05&LC=en&BC=Acer&SC=PA_6
I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium
Yes, well I only really use adb in the same capacity as what you describe-- to root a device. After that busybox can be installed and I can either ssh into the device (which I prefer) or use the terminal on the device itself.
But my problem is the detection of the device once it is plugged into my Linux box. I'm not sure if I need a special driver for that and I'd rather not aimlessly search through the kernel config in order to build one (I've done that before and it's painful!). It's good to know that one can mount it on an external device and still use it simultaneously though. That will save me time in trying to fiddle around with settings in the tablet itself...
dq
don quixada said:
I have adb installed should this not be enough?
Click to expand...
Click to collapse
If you are not able to transfer files Try enabling usb debugging before connecting to pc.
If the tab is not in the usb devices list and it doesn't show up as an unknown device, you might want to try another usb cable. Or another port if you have the Windows and Linux on the same machine and you are trying to connect on the same port.
Sent from my A500 using XDA Premium App
gradyzero said:
I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Not nearly what I was saying. Not even close enough that a bomb would touch it.
Simple answer is my vista and win7 systems accessed the iconia as a media player device requiring no drivers as they are a common system driver. My only comment about ADB was that it might be interfering if it somehow was left running in the background.
I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.
sandiegoan said:
I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.
Click to expand...
Click to collapse
Sometimes mine gets a bit wonky as well. Every now and then, I'll plug it in, get the windows dialogue box asking me what I want to do. I open it up and the box is blank, no drives, nothing. Unplug it, wait a few seconds, pop it back in, and everything is OK. No rhyme or reason, and it doesn't happen all the time.
Quick trick for win7 .
Plug in the device.go into device manager delete its entry and the USB controller it resides on.unplug device.install driver from acer web site.then try the device again.
This works on several USB type issues
Good luck if you don't understand don't try
Hi all,
Of late i have been facing this issue of transferring media files from PC to my nexus 10. On connection, MyComputer just crawls and whenever it connects the file transfer bar shows virtually no progress. Even if the file is just a few MB. I also have 2 users on this tablet and on the other user the same thing happens. I have to do multiple restarts to fix this and multiple file transfers is not possible as the whole PC hangs and Windows Explorer crashes.
Any help will be appriciated.
PS. Windows 7 OS and stock N10 with 4.4.2
Hi,
While I can't help you with the Windows issue I can offer you a temporary solution! Which is using adb push.
To do as such please go to the Manta Help Thread and check how to set up adb and enable USB Debugging. From there you will now open a terminal in the folder you want to copy the files and type:
Code:
adb push *filename* /sdcard/
Now the file is in your Nexus 10, if you want to push many files, I suggest creating one folder with the files and pushing the folder itself.
Code:
adb push *foldername*/ /sdcard/
Hope this helps a little . I use it a lot since my Fedora can't recognise MTP hahaha .
~Lord
"All I ever needed was a little piece of hope" - World of Fantasy (Helloween)
Sent from my Xperia Z1
Have you looked at the wifi file transfer apps? - I've never tried them because I'm rooted and use Sambadroid.
Re the transfer speed problem I've a vague recollection that a USB 1 device, like a keyboard will pull other usb 2 devices on the same hub down to usb1 speeds. Have you tried other usb sockets? Other things you can try are disabling USB Legacy Support and enabling AHCI in your BIOS.
If you decide to pursue the USB problem then you may find these progs helpful
There's a microsoft program usbview.exe that you can get from MS here http://msdn.microsoft.com/en-us/library/windows/hardware/ff551063(v=vs.85).aspx It's also here http://www.ftdichip.com/Support/Utilities/usbview.zip . My copy is copyright 1996-98 and it runs under W8.1
http://www.nirsoft.net/utils/usb_devices_view.html
XxLordxX said:
Hi,
While I can't help you with the Windows issue I can offer you a temporary solution! Which is using adb push.
To do as such please go to the Manta Help Thread and check how to set up adb and enable USB Debugging. From there you will now open a terminal in the folder you want to copy the files and type:
Code:
adb push *filename* /sdcard/
Now the file is in your Nexus 10, if you want to push many files, I suggest creating one folder with the files and pushing the folder itself.
Code:
adb push *foldername*/ /sdcard/
Hope this helps a little . I use it a lot since my Fedora can't recognise MTP hahaha .
~Lord
"All I ever needed was a little piece of hope" - World of Fantasy (Helloween)
Sent from my Xperia Z1
Click to expand...
Click to collapse
Will try.
peterk-1 said:
Have you looked at the wifi file transfer apps? - I've never tried them because I'm rooted and use Sambadroid.
Re the transfer speed problem I've a vague recollection that a USB 1 device, like a keyboard will pull other usb 2 devices on the same hub down to usb1 speeds. Have you tried other usb sockets? Other things you can try are disabling USB Legacy Support and enabling AHCI in your BIOS.
If you decide to pursue the USB problem then you may find these progs helpful
There's a microsoft program usbview.exe that you can get from MS here http://msdn.microsoft.com/en-us/library/windows/hardware/ff551063(v=vs.85).aspx It's also here http://www.ftdichip.com/Support/Utilities/usbview.zip . My copy is copyright 1996-98 and it runs under W8.1
http://www.nirsoft.net/utils/usb_devices_view.html
Click to expand...
Click to collapse
Thanks
You've had a few tangential suggestions, the ADB push being the fastest with the hardware and software you have currently.
I don't actually store files on my "PC" really as my source, I store them on a NAS and then pull them either to my PC or my other devices. This makes all my devices "stateless" as I find individual devices I'm moving around with ultimately break more often so I prefer the NAS route. My NAS is a Raspberry Pi running Rasbian with a 1TB USB hardd drive and a 64GB OTG flashdrive.
You can add to the other ideas:
Airdroid which runs a small web server on your Android device and you access the Android device from browser on PC and push files, at Wifi speeds.
run web server on your "PC" and then in Android just get them in a download app. My "PC" is Linux and its running Apache and I either SSH from the PC to the Android and then wget the file or use of the file download methods inside Android.
USB OTG stick which also serves to augment capacity, I get about 22MB/s from USB to inside N10
One other indirect thing, is when you do a full Android flash wipe it seems to reformat and speed up the filesystem better than if you've done an upgrade, although I never benchmarked it to know, just an impression.
Hello! I just got an unlocked LG G2 few days ago. I've gotten as far as enabling Tether, to work, and paritally got to mount it on my PC.
But I keep reading that libMTP is pretty much unstable on Linux. And I've only gotten to see it on banshee last night, but the moment I closed it, I never got to see it again.
I read a topic post that allows a user to mount about any android device on any unix based OS (Or at least) via SSHFS, currently I'm trying to do so. (But it keeps failing for some reason).
So in short, I'm currently unable to connect my phone to my Linux (Mint Xfce 17) PC without any major errors (MTP keeps giving me Function Not Implemented or a Input/Output Error, while I need a wifi (specifically a wifi access point, tether didn't seem to work) to connect via SSHFS), and am currently looking for a way to do so.
Anyone had any success?
Bump.......
Welp. I found a solution. After 3 days of searching (Days prior to the topic posting counted) I found out a way to do it.
Documentation (For anyone who might have the same issue)
You need a blank pendrive, and sshfs, a ssh server for android (I used SSHelper, if you're tethering, uncheck "Enable Wifi While Running", and the SSH IP address is the Device, though it'll say 0.0.0.0.)
1) Plug in your pendrive and if you want, mount it ( I did)
2) Go to terminal and write. You might need to allow allow_others in /etc/fuse.conf (Just remove the comment)
Code:
sshfs -o allow_other -o idmap=user [email protected]:/storage/emulated/0 -p PORT /media/$USER/PendriveName
3) Open Banshee, Ignore MTP Device (if it appears, in my case it did), and proceed to Sync Music To the new "Device"
IF The Pendrive/USB Stick doesn't appear you might need an .is_audio_player file.
Code:
name="LG G2 Drive"
audio_folders=Music/
audio_folder=Music/
Hope this helps
Hello everyone! I'm looking some advice from the wise about bypassing the region restrictions for the Soli Radar (Motion Sense) in my Pixel 4. I am pretty new at running ADB (Android Debug Bridge) from my Windows PC. That said, I'm sure I overlooked something very simple. I can't get the commands to work at all. I followed the XDA YouTube video step by step on how to install and setup the SDK Platform tools on my PC. As well as how to prepare my device to receive commands from my PC. But it fails every time. I'm pretty sure that I'm just running the ADB incorrectly, but I don't know. I have only been able to find instructions on how to install and setup the SDK package. But no clear instructions on how exactly to utilize it. Again, I've never done this before. I am running the latest version on Android 10 on my phone and my PC is running Windows 10. And before running any commands, I verified that the device is in fact attached to the PC by running "adb devices" first. I wish there was an option to attach a screenshot of failure message I'm getting. But it says:
setprop: failed to set property 'pixel.oslo.allowed_override' to 'true'
I get this same failure when I run the alternative command line as well. And I have tried both command prompt and Power Shell and receive the same failure message. Anything advice that can be shot my way would be greatly appreciated. Thanks!
First check the windows 10 device manager to confirm that your device and computer are successfully connected.
Then try to replace with a new data cable, a USB 2.0 cable may be better.
Is the phone bootloader unlocked or have you rooted it yet? Honestly I am not sure if either of those are required for the changes, but I suspect they are. If you haven't rooted the phone yet, then I bet you don't have the correct privileges to make those kind of changes to the phone.
What fun! Windows 10 and the NST
I find that I cannot negotiate ADB access via USB any longer. I don't know when that started, but it looks like maybe sometime in June. These events are displayed in the Device Manager when accessing "Portable Devices":
Driver Management has concluded the process to add Service WUDFWpdFs for Device Instance ID SWD\WPDBUSENUM\_??_USBSTOR#DISK&VEN_B&N&PROD_NOOK_SIMPLETOUCH&REV_0100#7&22272E47&0&3012440020143004&0#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B} with the following status: 0.
Device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_B&N&Prod_NOOK_SimpleTouch&Rev_0100#7&22272e47&0&3012440020143004&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} was not migrated due to partial or ambiguous match.
Last Device Instance Id: SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_B&N&Prod_NOOK_SimpleTouch&Rev_0100#3014760074133009&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
Class Guid: {eec5ad98-8080-425f-922a-dabf3de3f69a}
Location Path:
Migration Rank: 0xF000FFFF0000F102
Present: false
Status: 0xC0000719
Device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_B&N&Prod_NOOK_SimpleTouch&Rev_0100#7&22272e47&0&3012440020143004&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} requires further installation.
It's not beyond belief that the spate of major updates to Windows 10 recently trashed my ability to access the device via ADB/USB. The question is: how to fix it?
On the NST I have the following:
service.adb.tcp.port -1
persist.adb.tcp.port 0
All that stuff indicates that the NST is presenting as UMS.
Have you used UsbView.exe to see what interfaces are being presented?
Have you looked at sys.usb.config, sys.usb.config?
That stuff with adb.tcp is only for ADB over TCP (WiFi).
Renate said:
Have you used UsbView.exe to see what interfaces are being presented?
Click to expand...
Click to collapse
Mmm....is that in your signature (NOT)?
Renate said:
Have you looked at sys.usb.config, sys.usb.config?
Click to expand...
Click to collapse
And this is where?
I should have added that none of my three NST/G devices is connecting properly now (other than as USB file transfer devices) whereas all were formerly able to negotiate USB debugging and ADB.
UsbView.exe is the venerable Microsoft utility, to be found here: https://ftdichip.com/wp-content/uploads/2020/07/usbview.zip
You can also look in Windows Device Manager (devmgmt.msc), especially in "View > Devices by Connection"
Either OmapLink.exe or ImxLink.exe (in sig) will show you if ADB is showing (err, conditional upon the driver being loaded?)
Renate said:
UsbView.exe is the venerable Microsoft utility, to be found here: https://ftdichip.com/wp-content/uploads/2020/07/usbview.zip
You can also look in Windows Device Manager (devmgmt.msc), especially in "View > Devices by Connection"
Either OmapLink.exe or ImxLink.exe (in sig) will show you if ADB is showing (err, conditional upon the driver being loaded?)
Click to expand...
Click to collapse
This is the result from omaplink (green dot for ADB, black for UMS):
Code:
Waiting for bootloader or Fastboot or ADB...
ADB version: 01000000, payload: 4096, type: device
uid=0(root) gid=0(root)
In DeviceManager/Devices by Connection, the Nook shows up as a USB composite device.
And I've attached a screencap from usbview.
Well, OmapLink/ImxLink found your rooted device.
You do have only one Android plugged in?
What part of ADB is not working?
What version adb.exe are you using?
If the version is stone age it goes by VID/PID and it doesn't know about B&N.
Code:
C:\>adb version
Android Debug Bridge version 1.0.41
C:\>adb devices
12345678
Version is not that critical, but should at least be in the high 30's.
(For UsbView you want to click on the device so that you see interesting things in the right panel. But we're past that step.)
Wait, are you talking about UMS not working, not ADB?
Oh, don't tell me that you use UMS?
The NST presents two drives but there may not be anything mounted.
Run Disk Manager (diskmgmt.msc) and see if there are drive letters but nothing inside them.
Renate said:
UsbView.exe is the venerable Microsoft utility, to be found here: https://ftdichip.com/wp-content/uploads/2020/07/usbview.zip
You can also look in Windows Device Manager (devmgmt.msc), especially in "View > Devices by Connection"
Either OmapLink.exe or ImxLink.exe (in sig) will show you if ADB is showing (err, conditional upon the driver being loaded?)
Click to expand...
Click to collapse
This is the result from omaplink (green dot for ADB, black for UMS):
Code:
Waiting for bootloader or Fastboot or ADB...
ADB version: 01000000, payload: 4096, type: device
uid=0(root) gid=0(root)
In DeviceManager/Devices by Connection, the Nook shows up as a USB composite device.
And I've attached a screencap from usbview.
Renate said:
Wait, are you talking about UMS not working, not ADB?
Oh, don't tell me that you use UMS?
The NST presents two drives but there may not be anything mounted.
Run Disk Manager (diskmgmt.msc) and see if there are drive letters but nothing inside them.
Click to expand...
Click to collapse
Unless I am transferring a library book with ADE I like to keep UMS turned off since it locks you out of interacting with the screen while debugging...which now isn't happening for some unknown reason.
I try to do most file transfers wirelessly to save wear and tear on the USB jack.
So, yes, I am talking about ADB. "Device not found" is all I get now. I'll check on the version later today but I don't see why a version which was working just fine before should suddenly stop. Unless its Windows' fault.
nmyshkin said:
"Device not found" is all I get now.
Click to expand...
Click to collapse
Ah, ok.
It's definitely a problem with your adb.exe
OmapLink/ImxLink can find your device, connect and even do shell commands (id).
Those programs, unlike AdbSync, do not go through the ADB port 5037 of adb.exe like a normal ADB client does.
If you actually have adb.exe connected OmapLink/ImxLink won't be able to connect to the already connected device.
So this all means tht your WIndows drivers are fine.
You might have had a few copies of adb.exe and one of them got deleted or the PATH changed or a backup restored the wrong one or...
Also, there was that old C:\Users\Person\.android\usb_adb.ini file which was used by old versions of adb.exe
But you don't want/need that anymore, so forget that I mentioned it!
Renate said:
Ah, ok.
It's definitely a problem with your adb.exe
OmapLink/ImxLink can find your device, connect and even do shell commands (id).
Those programs, unlike AdbSync, do not go through the ADB port 5037 of adb.exe like a normal ADB client does.
If you actually have adb.exe connected OmapLink/ImxLink won't be able to connect to the already connected device.
So this all means tht your WIndows drivers are fine.
You might have had a few copies of adb.exe and one of them got deleted or the PATH changed or a backup restored the wrong one or...
Also, there was that old C:\Users\Person\.android\usb_adb.ini file which was used by old versions of adb.exe
But you don't want/need that anymore, so forget that I mentioned it!
Click to expand...
Click to collapse
ADB version is 1.0.31 (Minimal ADB and Fastboot)
Just to see, I connected up my regular non-Nook tablet and ADB saw the device right away. So the issue is definitely with the NST or the interface of the NST with Windows.
I actually do have that usb_adb.ini file, but again, why work with everything else and "suddenly" stop working with the NST?
When UMS is turned off, I do see the two "empty" drives (internal and sdcard) in Windows when I connect via USB.
Marshmallow came out in October 2, 2015.
That had ADB version 1.0.32
That was the first public release that eliminated vendor white-listing that was changed in November 21, 2014.
I could tell you how to fix the adb_usb.ini, but you really should just update a half decade or so.
Renate said:
Marshmallow came out in October 2, 2015.
That had ADB version 1.0.32
That was the first public release that eliminated vendor white-listing that was changed in November 21, 2014.
I could tell you how to fix the adb_usb.ini, but you really should just update a half decade or so.
Click to expand...
Click to collapse
Huh.
So I updated Minimal ADB and Fastboot to v.1.43 which is ADB version 1.0.39. And it worked right away. I still don't see why the previous version just stopped working with the NST. Like so much else in life, it makes no sense.
Anyway now I have another issue, for this version came with a genuine Windows installer and my previous version was a "dump into the folder of your choice and set up the paths". I'm wondering if it's safe to just delete that entire folder now (probably have to clean up the path statement too...). Ugh.
Once upon a time, adb.exe and fastboot.exe were completely standalone.
Now they require AdbWinApi.dll, AdbWinUsbApi.dll
They also require:
Code:
api-ms-win-crt-private-l1-1-0.dll
api-ms-win-crt-runtime-l1-1-0.dll
api-ms-win-crt-stdio-l1-1-0.dll
api-ms-win-crt-convert-l1-1-0.dll
api-ms-win-crt-string-l1-1-0.dll
api-ms-win-crt-environment-l1-1-0.dll
api-ms-win-crt-filesystem-l1-1-0.dll
api-ms-win-crt-time-l1-1-0.dll
api-ms-win-crt-utility-l1-1-0.dll
api-ms-win-crt-heap-l1-1-0.dll
api-ms-win-crt-locale-l1-1-0.dll
api-ms-win-crt-math-l1-1-0.dll
api-ms-win-crt-multibyte-l1-1-0.dll
But these should already be found in the Windows "downlevel" directories.
There's no need to be adding to PATH for every little thing.
If you are invoking adb/fastboot from the command line, you might consider using doskey:
Regedit HKCU\Software\Microsoft\Command Processor AutoRun=\wherever\my-autorun.bat
Code:
doskey /macrofile=\wherever\my-aliases.txt
Code:
adb=C:\some-sort-of-path\adb.exe $*
fastboot=C:\some-sort-of-path\fastboot.exe $*
Edit: I forgot the arguments ($*).
If you are invoking adb/fastboot from a bat or makefile just put the full path in some define.