Developers, Don't Get EasyTether! - Android Software Development

Developers, do NOT get EasyTether! EasyTether allows your 3G connection to be shared to your computer via the USB Cable.
HOWEVER, when you install the computer-side client of EasyTether, it saves a file that tells the computer to automatically mount the phone as a network spot when it is plugged in. This means adb won't find it (since it's not mounted as a device), and this means DDMS and "Eclipse Run on Device" won't work either. EasyTether is a great app, but developers shouldn't get it if you test apps on your device.
P.S. I learned this the hard way. It involved deleting system files and logging in as root on my Mac, as well as a few terminal commands.

Related

[Q] How to Access the device using Ubuntu?

Does anyone now how I can access the internal storage of my transformer through Ubuntu? I have the transformer connected via USB but it does not auto-mount or appear to be recognised as a storage disk
thanks for any help
I'm using SSHDroid and usb tethering when tablet is connected, find out the tablet ip, then you can use the ubuntu built-in "Connect To Server" via ssh.
readonlycn said:
I'm using SSHDroid and usb tethering when tablet is connected, find out the tablet ip, then you can use the ubuntu built-in "Connect To Server" via ssh.
Click to expand...
Click to collapse
Would you be able to explain the method you use a bit more thoroughly? I too am having frustrating problems getting my transformer mounted under Linux, and am sick of transferring everything via SD card
I tried over SSH, but Android automatically refuses connection. And why do we need to have it tethered via usb to SSH?
The transformer acts as an MTP device. I had some issues with it appearing properly in Ubuntu 10.04, but I believe is because I did something wrong. I have it all working now and mounted as /media/transformer - but I am also running 11.04 now.
This has been asked on the forum before and this answer assisted me in solving it[Full thread].
You also have some links in a different thread here.
poltak11 said:
I tried over SSH, but Android automatically refuses connection. And why do we need to have it tethered via usb to SSH?
Click to expand...
Click to collapse
What's your SSHD application? I recommend sshdroid, you search it in the market.
You needn't tethering if pc and android are in one lan (connected to same wifi for example). Getting android ip is the only purpose of tethering, you can run 'route' command in ubuntu to find out the gateway of usb0, which is the ip of android.
I use a combination of swiftp and droidsshd to access device from ubuntu. Works well. You might need to get the programs from code.google.com, as they are not in the market.
People... they aren't looking for an SSH application, they are looking to MOUNT THE DEVICE OVER USB.
You need to install either libmtp or mtpfs. On Arch Linux, libmtp is in the repos, while mtpfs is in AUR. I use mtpfs.
After getting mtpfs, all you need to do is: sudo mkdir /media/tf && mtpfs -o allow_other /media/tf.
I do it with ADB. adb push and and pull does the job easily, unless you've a ton of different files you want to place in different places.
Using gnomad2 from repo @ Fedora 15 Gnome3
since there is no flashy mtpfs for my distro :/
(to lazy to compile)

[Q] What's the micro usb port for?

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

Not able to ADB my STR

Hello folks,
I had a WinXP computer, and I installed android SDK, and I was able to connect to my nook via ADB. As it was aging and having fan problem, I bought a new Dell (i5, win7, 4Gb RAM, 500 Gb HD). I installed android SDK, but never tried to ADB my nook. Yesterday I tried it, and whenever I try to connect via IP, or use adb devices, nothing shows up. I tried messing with the firewall, but it was not working at all.
Does anybody have any idea to help me? And also on how to get my firewall back (removed Norton, which I believe is a bloating spyware, and installed avast antivirus, but firewall was not released either, and it gives a 0x80070424 error).
Try this
Attach the usb cable to the NST and see if it is visible in device manager. Ideally if no driver is installed, you would just see it there with an exclamation mark.
Then follow ros87's instructions here. If adb_usb.ini doesnt exist create it.
Then from device manager, update device drivers for the unrecognized nook and point it to the i386/amd folder within the android drivers folder.
once that is done, restart adb, run "adb usb", then try "adb devices". If it worked it should show you the device.
ADB wifi was easier. In fact, it was such a long time since I last used it (before 1.1.1), that I forgot to add the adbwireless button to turn it on.
But thanks anyway. I've never dared to use USB due to inner messiness of the process.

[Q] Choosing ADB over USB or WiFi, when Rooting

After reading around, I've learnt that MinimalTouch 1.1beta5 is a reliable way to root my new Nook Simple Touch. Since I intend selecting the package version in the beta5 folder, I must choose between the "START" zips: beta5-2 XUFullTouch-PART-1-START and beta5-2 XWFullTouch-PART-1-START. I gather the first zip is ADB over USB, and the second, ADB over WiFi, but have found little documentation on either, except that ADB is a method to connect your home computer to your Nook.
The above link states that all W zips install ADB wireless Uramdisk, and all U zips install ADB USB Uramdisk + ADB widget to enable wireless adb at need. Am I right that ADB over USB is the best choice because both USB and WiFi are available after rooting? If so, would anyone select the ADB over WiFi option?
Can someone please explain how and why one chooses between the two options when rooting the Nook?
On startup the ADB daemon, adbd looks at the property service.adb.tcp.port
If it is set it uses that value as the port number over TCP (presumably over WiFi) to listen for connections.
If it is not set it tries to connect over USB.
I'm not sure how these applications that switch mode work.
They probably kill the daemon and restart it.
The only difference between the two versions of W and U is the line:
Code:
service.adb.tcp.port=5555
Renate NST said:
The only difference between the two versions of W and U is the line:
Code:
service.adb.tcp.port=5555
Click to expand...
Click to collapse
Thanks for your help. I've taken a while to make sense of your post since all this is new to me - I rarely use a mobile phone.
I've just looked at contents of both the "START" zip files and noticed they're the same, except that the file uRamdisk in the folder boot of the WiFi option is marginally bigger. You have shown me the difference lies in the property service.adb.tcp.port in the Java source code, and that property determines whether the rooted Nook tries to connect by WiFi or USB. In other words, the two zips are identical except for ADB connection.
But my opening post, in ignorance, attempted to ask a more trivial question. I know whenever I wish to access any laptop computer from my desktop computer under Windows XP, I can connect the two using a network cable from the laptop to my wireless router/modem or, more simply, by activating WiFi on the laptop. Similarly, I am assuming I can connect the rooted Nook to my desktop either by cabling the Nook microUSB port to a USB port on my desktop, or by activating WiFi on the Nook. I expect to connect every few days. Since the USB "START" zip of MinimalTouch 1.1beta5 provides an ADB widget to enable wireless adb at need, what is the point - for the end user - of a separate WiFi only "START" zip file?
In other words, in routinely connecting my rooted Nook to the desktop computer every few days, why on earth would I or anyone benefit from having had the two "START" zip options available in MinimalTouch 1.1beta5?

Nexus file transfer tedious.

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.

Categories

Resources