• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

what do i do with adb_usb.ini under Linux?

lectraplayer

Well-Known Member
I'm trying to get at least one of my phones to work with the SDK to olkit, locted /opt/Android-SDK/. Debugging is always used and I can always find my device n the USB buss. Als can use te SD card as disk. Still, adb devices shows an empty list. I have seen the file listed as /android/adb_usb.ini. would it go inn the root folder of my SDK kit (/opt/Android-SDK) or would it go in my ./tools folder with the adb executeable, or where?
 
I don't know. :( But there are a couple of things we can try! :)

One, if you post the specific device you're working with, we can move this thread over to that device's 'all things root' board.

Two, there's no reason [that I know of] not to place copies of adb_usb.ini in multiple locations (such as /android and ./tools), and see if doing so solves the problem.
 
iirc, *.ini files are Windows only. specifically drivers. Linux does not use *.ini if i am correct, sounds like you have tried using Windows software on Linux. the usual method of using adb tools in Linux involves downloading the tools from the repos, usually via apt.
 
I too also thought that .ini files were Windows only but they call for it on Mac, which is an Unix base, as is Linux. I am using two unrrooted, unmodified phones from two seperate manufacturers but one carrier-T*mobile. One is a Sidekick (basically a moified Samsung Galaxy S) and an LG MyTouch Q. Even trying my oldHTC Magic (T*Mobile's first MyTouch) leads to the same result-debugging icon shows, device can be found on USB buss, files can be browsed, but ADB has no clue the phone is preset. How would I fix this?
 
i've never seen any use for *.ini files in Linux. Mac OS X is vastly different from Linux, it is more like pure UNIX mixed with Darwin. two entirely different kernel and driver sets. in many cases if not all, UNIX software won't run in Linux. if it did, i would be able to use that 3-D file browser that was seen in Jurassic Park. alas, unless i run whatever UNIX was in the SGI hardware, and have the same hardware myself, it's not possible no matter how much source code i compile.
 
i've never seen any use for *.ini files in Linux.

The extensions may differ but "ini style":

Code:
[section1]
item1=value1
item2=value2
,etc.

configuration files do exist on Linux. The php configuration file on Linux actually is called php.ini.
 
if it did, i would be able to use that 3-D file browser that was seen in Jurassic Park. alas, unless i run whatever UNIX was in the SGI hardware, and have the same hardware myself, it's not possible no matter how much source code i compile.


As a side note, no you wouldn't either. Fsn (pronounced "fusion") was featured in Jurassic Park, but never became a functional software program. I hear most programs compiled for Linux run in Unix and vice versa with little modificatins since both are in C. I know KDE will, and can find many Iinux programs that are tested suitable for MacOS-X. Heck. Android is a bona-fide Linux itself. ...now, if I can get Vector and Android to play together.
 
I thought FSN was actually 'File System Navigator', and if i am not too mistaken, actually did exist on SGI hardware. whether or not it was intuitive or user-friendly is another discussion. Irix, also featured in that movie, also won't run in Linux, it's SGI only. there is, however, a decent replica of it though available on many platforms, including Linux.
 
The extensions may differ but "ini style":

Code:
[section1]
item1=value1
item2=value2
,etc.

configuration files do exist on Linux. The php configuration file on Linux actually is called php.ini.

...in fact, Linux uses that style far, far more than Windows. It is so pervasive in Linux that it is effectively universal. I can't remember ever seeing a config file in Linux that was in binary gobbledygook, except maybe in a cross-compiled program originally written for another type of system (such as a MIcrosoft OS).

That said, if you see a file named foobar.ini, you can safely assume it's not for use in Linux. It's not unknown but examples are the exception, not the rule, in my experience.

As a side note, no you wouldn't either. Fsn (pronounced "fusion") was featured in Jurassic Park, but never became a functional software program. I hear most programs compiled for Linux run in Unix and vice versa with little modificatins since both are in C. I know KDE will, and can find many Iinux programs that are tested suitable for MacOS-X. Heck. Android is a bona-fide Linux itself. ...now, if I can get Vector and Android to play together.

A program compiled for Linux would most likely need to be recompiled for another unix-like system, you wouldn't just be able to run it straight away.

Irix, also featured in that movie, also won't run in Linux, it's SGI only.

Irix is an OS, you wouldn't expect it to run in Linux any more than you expect HP-UX, AIX, Xenix, CP/M, NetBSD, or Windows to run in Linux (except virtualized, of course).

So that movie was full of that kind of stuff? Never seen it, but I know I'd get more pop culture references from the past 20 years if I did. When it came out it was way too popular for me to want to see it and I've never gotten around to it since. :p

...but we digress, let us return to talking about adb. I don't think the .ini file is used in Linux. I think you do the same thing with udev rules. As an example, the Nook Simple Touch doesn't work with a regular adb platform-tools installation, you have to modify adb_usb.ini in Windows, and you do the same thing with udev in LInux:
ADB Over USB (Nook Classic) - nookDevs
 
I'm pretty sure you can use the apt-get command to get the tool, just depends on the flavor you are using.

Sent from my C525c using Tapatalk 2
 
My only problem with apt-get is that my devlopment computer does not have an internet connection.i've found a place to download all things Android Development via a web browser but can't remember where. Would like to find that site again.
 
So that movie was full of that kind of stuff? Never seen it, but I know I'd get more pop culture references from the past 20 years if I did. When it came out it was way too popular for me to want to see it and I've never gotten around to it since. :p
You should see it. Jurassic Park (the original) was amazing; its sequels were so-so. :rolleyes:

My favorite line from the original was "It's a UNIX system...I know this!" I love it so much I've carried an old WAV file of it with me for over 20 years. :D
 
I guess my question is how to get Android SDK to work with my various phones under the Vector Linux environment. I keep digging up adb_usb.ini under Windows and MacOS, but no help under Linux.
 
I guess my question is how to get Android SDK to work with my various phones under the Vector Linux environment. I keep digging up adb_usb.ini under Windows and MacOS, but no help under Linux.

My Virgin Mobile Venture and LG Optimus Slider didn't need any configuration changes to connect ADB in linux (Debian 6), I just needed the ADB platform-tools.

Did you try messing with udev rules as mentioned here?:

I don't think the .ini file is used in Linux. I think you do the same thing with udev rules. As an example, the Nook Simple Touch doesn't work with a regular adb platform-tools installation, you have to modify adb_usb.ini in Windows, and you do the same thing with udev in LInux:
ADB Over USB (Nook Classic) - nookDevs

Have you tried on a Windows box to see if it works there, just in case the problem is your device or cable?
 
If it was the device or cable, would I be unable to browse my files on the phone? I manage my phone's files often from my Linux machine. I rarely, if ever use Windows because it normally gives me problems with simple tasks. Also I have not tampered with udev yet and would not suspect it when I am finding each of my phones under VASM. What would I need to mess with? Where is a good guide for udev?
 
I did not find good documentation for udev.

Not familiar with vasm but seeing your phone listed there may only mean that it was detected for USB mass storage or some other functions, not necessarily for adb.

Even though windows can be a pain, testing on another type of system that is more popular and has more people posting their experiences can help you figure out what you need to do in Linux. For example, if it works on windows without having to mess with that .ini file then you probably won't need to mess with udev.
 
Next question: is there a torrent I can download the Android SDK from? I am trying Android.com but none of the files they have can be downloaded. They all fail instantly. Is thers an alternative download location for Android SDK?
 
Back
Top Bottom