Hi all,
I searched quite a lot, but seems to me not nearly enough. I've been using adb on my Windows 7 machine for a while now, but would like to have adb at work on my Ubuntu 11.04 machine where I am going to start some boring development.
I have installed the sdk and eclipse and and and (if it is important WHAT I installed more than this, I will elaborate)
lsusb returns
Code:
Bus 002 Device 009: ID 04e8:689e Samsung Electronics Co., Ltd
so I have set my
/etc/udev/rules.d/51-android.rules
to reflect like this:
Code:
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",ATTRS{idProduct}=="689e",SYMLINK+="android_adb",MODE="0666
I'm kinda hoping this is wrong and there is an easy fix that I can laugh about.
When I have the emulator running and my phone plugged in
Code:
$sudo adb devices
returns a blank line and something about an emulator, only emulator running yields no blank line and only phone plugged in yields a nice and quiet blank line.
I had this on Windows as well when I struggled with drivers, but the CD sorted it out. I read that the necessary drivers comes with the SDK, but I might be wrong.
I have tried different tutorials and different values for the idProduct and idVendor as some tutorials claim they should be kept constant and not vary per phone... I restarted adb each time I made a change with
Code:
$sudo adb kill-server; sudo adb start-server; sudo adb devices
I'm currently running FirstUA v1.2 if that changes anything.
If you need more info, don't hesitate to ask, I know it's easier to solve problems with the right info (coming from an IT helpdesk).
Digi.Gram said:
Hi all,
I searched quite a lot, but seems to me not nearly enough. I've been using adb on my Windows 7 machine for a while now, but would like to have adb at work on my Ubuntu 11.04 machine where I am going to start some boring development.
I have installed the sdk and eclipse and and and (if it is important WHAT I installed more than this, I will elaborate)
lsusb returns
Code:
Bus 002 Device 009: ID 04e8:689e Samsung Electronics Co., Ltd
so I have set my
/etc/udev/rules.d/51-android.rules
to reflect like this:
Code:
SUBSYSTEM=="usb",ATTRS{idVendor}=="04e8",ATTRS{idProduct}=="689e",SYMLINK+="android_adb",MODE="0666
I'm kinda hoping this is wrong and there is an easy fix that I can laugh about.
When I have the emulator running and my phone plugged in
Code:
$sudo adb devices
returns a blank line and something about an emulator, only emulator running yields no blank line and only phone plugged in yields a nice and quiet blank line.
I had this on Windows as well when I struggled with drivers, but the CD sorted it out. I read that the necessary drivers comes with the SDK, but I might be wrong.
I have tried different tutorials and different values for the idProduct and idVendor as some tutorials claim they should be kept constant and not vary per phone... I restarted adb each time I made a change with
Code:
$sudo adb kill-server; sudo adb start-server; sudo adb devices
I'm currently running FirstUA v1.2 if that changes anything.
If you need more info, don't hesitate to ask, I know it's easier to solve problems with the right info (coming from an IT helpdesk).
Click to expand...
Click to collapse
The SDK Drivers are not for Galaxy Ace , Google for the drivers , they should be easy to find
Sent from my Ultma Weapon using XDA App
It seems that my problem begins with our Proxy server.... As the SDK manager and I had a quarrel about authentication, I downloaded some of the packages directly and forced the manger to use them instead of those on Google. With this, I accidentally downloaded an outdated adb, which had problems specifically with the Galaxy line of phones.... Downloading the correct package now, will see if it works better
Maybe I must just stop before I think of continuing I installed the newer r06 version, and my device is picked up, but now adb shell gives me this:
Code:
:~$ adb devices
List of devices attached
S58300c017faf device
:~$ adb shell
sh: applet not found
Any ideas where to look for the applet? Maybe I must continue tomorrow, new day new ideas.
Do you have Debugging turned on? And is the device rooted with Busybox? I assume yes since you're running a custom ROM but double checking.
If you're having trouble, I'd either: a) run a VM with XP SP3; b) head to the Android Q&A board here.
mmm, I never though of looking at that, since I figured they do say busybox is installed on this ROM, but thanx for nudging me into that direction, I found this post from ketut.kumajaya so I'm looking into that. Had some issues with not abling to get rw access, but my only problem there was a spelling error in the terminal.
I still get the error with the sh: applet not found, even after I tried the advice on that link. I tried installing all 3 versions shipped with BusyBox Installer on all 3 locations, still nothing. Just had an idea I'll try, if you invoke sh in linux you get a new shell, when I invoke sh I get the applet not found error. Maybe I should upgrade my sh or something. Worth a try
I am running a VM for the VB programming I do at work, but that doesn't have USB support (to much trouble to reinstall Virtual Box now just for USB support). Last night I tested on Windows 7 (first time since I started using this ROM) and it failed with the same error. I'm sure it's the sh that's broken or something. Will test on my wife's phone tonight (running the same ROM).
Thanx for your ideas so far. That's what I love about an online community, even if you don't exactly know what's wrong, people sling ideas around that nudge you in the right direction. One error message at a time
Solved thanx to Ketut
Thanx for all your help guys.
hey all, i got ubuntu on my galaxy tab and everything is working with terminal emulator and vnc so i don't have to use a computer with adb to do it, what i want to ask is that when i go into ubuntu with the lxde desktop environment, everything works perfect and a lot faster than i though except for the terminal. i can load the terminal but i don't get a command prompt, the cursor just blinks but nothing happens. what can i do about that? i even tried to download different terminals, (guake terminal, the terminal that comes with gdm, etc) nothing works. thanks in advance for the help!
Hi I can't connect to the Wlan Network at our university, which is using wpa2 enterprise.
When I click on the network nothing happens. On askubuntu I found something, but I don't know in which file on my phone I have to put the text in.
http://askubuntu.com/questions/586300/creating-a-wpa2-enterprise-connection-on-ubuntu-touch
Yes, WPA2 Enterprise isn't supported by the GUI yet.
The file you need to save that to needs to be called
Code:
/etc/NetworkManager/system-connections/<your network's id>
Replace <your network's id> (including the brackets) with the ID of your Wifi network. In the example it would be "eduroam".
(Please note that you need to save the file as root, i.e. using sudo.)
I tried it yesterday with the file, but it didn't worked. But I am not sure if the file is correct for our network.
I followed this guide http://www.danbishop.org/2015/02/21...ther-802-1x-wireless-network-to-ubuntu-phone/ and now I get a connection. Only username and password have to be changed.
Sent from my awesome Ubuntu Touch device using the Forum Browser app
Sorry if this is a semi-hijack, but this seems the most relevant place for my question. I can't get access to my uni's wi-fi either (aquaris ubuntu edition phone), and I was wondering if anyone knows if the functionality for wpa2 is going to be added in the near future? I don't have ubuntu on a desktop atm and I don't want to have to install it just to tinker with my phone, which also seems a little bit daunting to me, worried I will explode my phone or something.
I don't know when they bring wpa2 enterprise support via gui, but I think it is a must have feature. You don't need ubuntu to get it working. I can upload the file I used, you just have to change 2 lines. You can use putty to put the file in the right location.
jonny-boy said:
I don't know when they bring wpa2 enterprise support via gui, but I think it is a must have feature. You don't need ubuntu to get it working. I can upload the file I used, you just have to change 2 lines. You can use putty to put the file in the right location.
Click to expand...
Click to collapse
That'd be great, although I've no idea what I'm doing with this sort of thing, would it be possible for you to explain it to me in idiot terms? I'm not familiar with putty or this kind of exercise
1. Activate Developer Mode on your phone
You can activated the Mode under Device info, developer mode
(But you have to set a password for your phone before, if I am not mistaken)
2. Connect your Phone via usb to your computer
3. Download adb for windows: http://forum.xda-developers.com/showthread.php?p=48915118
The installer asks some questions, I answered all questions with yes.
4. I attached a File. Just change username and password.
Then remove the file extension (remove the .txt)
You have to activate show file extensions in the windows explorer, to remove the file extension
5. Move the File on your phone e.g. in the download directory via usb
6. Run the windows command line tool (I use Super+R and then just run "cmd")
7. Run "adb shell" in the cmd
(When it says: "error: closed", you have to unlock your phone)
It should say something like "[email protected]" now.
8. Move the file from the Download-Folder to the Network-Manager-Folder:
"sudo cp Downloads/eduroam /etc/NetworkManager/system-connections/"
Password should be your phone unlock password
9. Now go into the Networkmanager directory:
cd /etc/NetworkManager/system-connections/
10. Run the following commands to set the right permissions for the file:
"sudo chown root eduroam"
"sudo chgrp root eduroam"
"sudo chmod 600 eduroam"
11. Reboot your Phone
For me this worked. My English is not that good, so just ask, if you have questions.
jonny-boy said:
1. Activate Developer Mode on your phone
You can activated the Mode under Device info, developer mode
(But you have to set a password for your phone before, if I am not mistaken)
2. Connect your Phone via usb to your computer
3. Download adb for windows: http://forum.xda-developers.com/showthread.php?p=48915118
The installer asks some questions, I answered all questions with yes.
4. I attached a File. Just change username and password.
Then remove the file extension (remove the .txt)
You have to activate show file extensions in the windows explorer, to remove the file extension
5. Move the File on your phone e.g. in the download directory via usb
6. Run the windows command line tool (I use Super+R and then just run "cmd")
7. Run "adb shell" in the cmd
(When it says: "error: closed", you have to unlock your phone)
It should say something like "[email protected]" now.
8. Move the file from the Download-Folder to the Network-Manager-Folder:
"sudo cp Downloads/eduroam /etc/NetworkManager/system-connections/"
Password should be your phone unlock password
9. Now go into the Networkmanager directory:
cd /etc/NetworkManager/system-connections/
10. Run the following commands to set the right permissions for the file:
"sudo chown root eduroam"
"sudo chgrp root eduroam"
"sudo chmod 600 eduroam"
11. Reboot your Phone
For me this worked. My English is not that good, so just ask, if you have questions.
Click to expand...
Click to collapse
So far I can't get the adb shell to recognise the phone is there, it just keeps saying "error: device not found" so I'm kinda stumped right now
I got this error the first time, too. I just reinstalled adb, while the phone was plugged to my computer and unlocked and answered the driver question with yes, then some driver were installed.
jonny-boy said:
I got this error the first time, too. I just reinstalled adb, while the phone was plugged to my computer and unlocked and answered the driver question with yes, then some driver were installed.
Click to expand...
Click to collapse
Did that, still says Error: device not found =/
Garatolla said:
Did that, still says Error: device not found =/
Click to expand...
Click to collapse
Tried it on my friend's linux pc as well and it still says error device not found, guess I'm just going to have to wait for them to officially add in wpa2 functionality. Welp, back to my old phone for a while then, thanks for the help jonny-boy
@garatola Do you have the phone unlocked and the screen turned on when trying to connect? That's one requirement on Ubuntu.
Sent from my awesome Ubuntu Touch device using the Forum Browser app
nikwen said:
@garatola Do you have the phone unlocked and the screen turned on when trying to connect? That's one requirement on Ubuntu.
Sent from my awesome Ubuntu Touch device using the Forum Browser app
Click to expand...
Click to collapse
Yup, I managed to find out about that before I first started trying to figure out how to fix this unfortunate situation
Does anyone know if or when there will be wpa2 functionality on this os? Or where I might ask? I need it for accessing my uni wifi stuff, and if it's going to be a while, I'll just shelf the phone and forget about it as a phone without internet access is pretty much just a paperweight for me. Thanks again for the help given so far everyone
Garatolla said:
Does anyone know if or when there will be wpa2 functionality on this os? Or where I might ask? I need it for accessing my uni wifi stuff, and if it's going to be a while, I'll just shelf the phone and forget about it as a phone without internet access is pretty much just a paperweight for me. Thanks again for the help given so far everyone
Click to expand...
Click to collapse
According to the corresponding launchpad issue, a fix has just been made available. However, it will probably take a month until it is in the stable builds.
If adb still doesn't work for you and the issue is that important to you, you can always also try following the guide using the terminal app on the device itself. Will take some time to type the commands in but it should work.
nikwen said:
According to the corresponding launchpad issue, a fix has just been made available. However, it will probably take a month until it is in the stable builds.
If adb still doesn't work for you and the issue is that important to you, you can always also try following the guide using the terminal app on the device itself. Will take some time to type the commands in but it should work.
Click to expand...
Click to collapse
I don't have access to a linux pc, and for some reason ubuntu wouldn't install for a dual boot when I tried that either. I also didn't see an app that would let me use the terminal on my phone - I've not had much luck with this lol. However, for some reason the adb stuff randomly started working on my friends linux pc and he friend managed to fix something up for me today, so all is well, for now at least :s (I also noticed the terminal app on the ubuntu store once I finally did get the net working.)
In the end, my friend used this http://www.danbishop.org/2015/02/21...ther-802-1x-wireless-network-to-ubuntu-phone/ to get it working, although the first time he tried adb wouldn't recognise my phone, and we don't know how it was righted, so sorry I can't pass on more info to people who might have the same problem =/
Thanks for all the replies again
Garatolla said:
I don't have access to a linux pc, and for some reason ubuntu wouldn't install for a dual boot when I tried that either. I also didn't see an app that would let me use the terminal on my phone - I've not had much luck with this lol. However, for some reason the adb stuff randomly started working on my friends linux pc and he friend managed to fix something up for me today, so all is well, for now at least :s (I also noticed the terminal app on the ubuntu store once I finally did get the net working.)
In the end, my friend used this http://www.danbishop.org/2015/02/21...ther-802-1x-wireless-network-to-ubuntu-phone/ to get it working, although the first time he tried adb wouldn't recognise my phone, and we don't know how it was righted, so sorry I can't pass on more info to people who might have the same problem =/
Thanks for all the replies again
Click to expand...
Click to collapse
Great that it finally worked.
I recently installed ConnectBot and ran it. When the app opened, I typed 'ls', but was told 'permission denied'; however, I was able to successfully execute 'ls /sdcard' .
My phone is a rooted Pixel 7 running Android 13. What can I do, if anything, to see the / directory? Thanks.
groston said:
I recently installed ConnectBot and ran it. When the app opened, I typed 'ls', but was told 'permission denied'; however, I was able to successfully execute 'ls /sdcard' .
My phone is a rooted Pixel 7 running Android 13. What can I do, if anything, to see the / directory? Thanks.
Click to expand...
Click to collapse
I don't understand what you are writing about. ConnectBot is an ssh client. First you need to establish a connection. You can only execute commands after logging in.
ze7zez said:
I don't understand what you are writing about. ConnectBot is an ssh client. First you need to establish a connection. You can only execute commands after logging in.
Click to expand...
Click to collapse
I don't understand your reply. I set the program to localhost and when I entered 'ls /sdcard', it did exactly as expected. However, when I simply entered 'ls', I got an error.
So ConnectBot works great, but you write something completely different in the title of the thread (ConnectBot not working as expected).
.