Related
Hi folks,
can i change the device name of my HTC Hero anyhow, so that in my router's overview it shows the name of it, like it does with laptops / PCs?
I know its possible with bluetooth, but i havent found any option for doing that concerning WLAN.
I didnt root my device, otherwise i would have probably tried the commands which i would use for my Ubuntu laptop:
sudo echo "newname" > /etc/hostname
sudo hostname -F /etc/hostname
and edit /etc/hosts accordingly.
Anyone knows a solution for me?
Best regards,
kapen
Please, anyone?
Or could anyone, who has a rooted Hero, go and take a look whether the files /etc/hostname, /etc/hosts and the command "hostname" exist? Or perhaps even write something in these files, i mean it wont do any harm as you are just writing sth to an ordinary text file.
If i'd have root, i'd do it myself, but for now there are no benefits for me which would push me to root and i don't want to lose my warranty for nothing.
Help is very much appreciated!
most routers let you do this on the router....
I know when i hook up to my thompson router and set a static IP address, it lets me name the device... Hardly worth hacking the device for really.
Bump
I'd like to be able to do this as well, without having to use a static IP. This can be done with symbian, winmobile, java and other types of phone not to mention internet tablets, laptops etc. Why not an Android phone?
rhedgehog said:
most routers let you do this on the router....
Click to expand...
Click to collapse
True. But most routers isnt my router, its not able to do that. And neither do i want to set a static IP on my Hero, because i'm using it with several other WLANs.
fair enough.
I just thought as there is no way that anyone seems to know of on the device, that it may be an alternative.
Ya your right.
I just thought anyone knew a solution for me. I mean its a system running on linux and i ought to be able change that kind of stuff... just don't know how :\
Heureka! It worked just the way i suggested
If you have a rooted device with busybox!, get that handy adb file and do:
Code:
1. adb root
2. adb remount
3. adb shell
3.1 cd /etc
3.2 echo "Hero" >> hostname
3.3 echo "127.0.0.1 Hero localhost.localdomain localhost" > hosts
3.4 echo "127.0.1.1 Hero" >> hosts
3.5 hostname -F /etc/hostname
Voila. Though, you'll get an error when you do "hostname" now, because something in busybox is wrongly linked against a library which doesnt allow resolving hostname by IP, but other devices (such as my router) will now display "Hero" as device name.
Side note: my only intend for doing this was, that my router WAG54G2 (Linksys by Cisco) didnt work correctly with my Hero, meaning i got a lot of connection aborts in WLAN and often could not reconnect afterwards. That seems to be solved now!
Edit:
With the method above, you''ll lose your Wlan name after reboot. You need to add a line to the init startup scripts to perform a "hostname -F /etc/hostname" on every boot. This can be done in the file /init.rc or, if you have the MoDaCo Rom, in /data/init.sh
Hey guys.
Just a heads up, the Xoom can run ADB natively. Full ADB. Haven't tested it over USB Host, but it works with ADBwireless.
Doesn't seem to be documented anywhere, but it does work. Try ADB devices from a terminal on your xoom.
Meaning that the Xoom can run ADB, just like your computer. Pull APKs, ringtones, media, whatever over wifi.
EDIT: These commands should make it work without the apk.
To trigger adb wifi on your phone/non-Xoom:
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
To stop adb wifi and return to USB listening:
Code:
setprop service.adb.tcp.port -1
stop adbd
start adbd
To connect:
Code:
adb connect [IPAddress]:[port]
For example, adb connect 192.168.1.4:5555
Or from USB on your comp:
Code:
adb tcpip 5555
adb connect 192.168.0.101:5555
To get back to USB mode:
Code:
adb usb
thats awesome thanks!
good to know thanks
you could also use adbwireless from the market to do the same thing
it's a lot easier, I think.
Yes, but some of us don't feel like paying...or just prefer command line. :]
smaskell said:
you could also use adbwireless from the market to do the same thing
it's a lot easier, I think.
Click to expand...
Click to collapse
What is included in the sdk on the xoom? I know that you can build apps from the command line on windows and linux. I think that this function would really be what I need to buy a tablet (again). Or you might be able to borrow things from the linux sdk.
Someone should take these commands and put them together into one easy to use app and launch it on the market. Many would benefit from one click type methods to natively run adb commands from the Xoom. If someone would be willing to do that of course. I'm just sayin'.
yep, weve been using the functionality for a while now!
you should also look into moto utils, which come preinstalled on the xoom and can do all sorts of funky stuff!
diablo2224 said:
Someone should take these commands and put them together into one easy to use app and launch it on the market. Many would benefit from one click type methods to natively run adb commands from the Xoom. If someone would be willing to do that of course. I'm just sayin'.
Click to expand...
Click to collapse
search "adb wireless"，you can get this awesome free app, it has a widget built-in.
and born at a bit long ago.
ftgg99 said:
yep, weve been using the functionality for a while now!
you should also look into moto utils, which come preinstalled on the xoom and can do all sorts of funky stuff!
Click to expand...
Click to collapse
So I checked out the field utils...
Apparently the Xoom has a WCDMA component? That's HSPA+ if I'm right...further supported in the iFixIt teardown.
Turned off the GSM functionality (on by default), hoping it'll save battery...not that I can complain. Battery life on this thing kicks ass.
Here's my question: Does it have an IMEI? As in can I put an AT&T SIM in there and it'll work? I'll try testing it out later. Might be time to pull out the ole' faraday cage...
schould get the commands into scripts, executable from a homescreen/the app drawer
@oshigeru YES it has an IMEI. If the AT&T Sim is on CDMA, you should have no problem to use it on the xoom, cuz i can see no restriction/branding/something on it
RinTinTigger said:
schould get the commands into scripts, executable from a homescreen/the app drawer
@oshigeru YES it has an IMEI. If the AT&T Sim is on CDMA, you should have no problem to use it on the xoom, cuz i can see no restriction/branding/something on it
Click to expand...
Click to collapse
Gscript should be able to do it.
AT&T on cdma? Lolwut?
It has an MEID that looks one hell of a lot like an imei, but I can't see an imei anywhere in the tablet. I don't know if the sim slot is active or not. (3g version.)
Sent from my Xoom using Tapatalk
I know this is an older thread but I need some direction in how to get adb in xoom to recognize my NS4G device when plugged in via usbOTG. Is it possible?
Daniel Smith1953
Jewremy said:
Hey guys.
Just a heads up, the Xoom can run ADB natively. Full ADB. Haven't tested it over USB Host, but it works with ADBwireless.
Doesn't seem to be documented anywhere, but it does work. Try ADB devices from a terminal on your xoom.
Meaning that the Xoom can run ADB, just like your computer. Pull APKs, ringtones, media, whatever over wifi.
EDIT: These commands should make it work without the apk.
To trigger adb wifi on your phone/non-Xoom:
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
To stop adb wifi and return to USB listening:
Code:
setprop service.adb.tcp.port -1
stop adbd
start adbd
To connect:
Code:
adb connect [IPAddress]:[port]
For example, adb connect 192.168.1.4:5555
Or from USB on your comp:
Code:
adb tcpip 5555
adb connect 192.168.0.101:5555
To get back to USB mode:
Code:
adb usb
Click to expand...
Click to collapse
thanks for the info but, I can't get adb on my pc! says it doesn't exist! No idea of where to go for that. Any suggestions?
Dan [email protected]
Thank you for these commands.
I am still having same issue with adb and linux not recognizing my epic I have posted in regards to this and had no responses there all so many devs that work with epic and yet not one has commented to offer a fix i have tried adding 99-samsung.rules with proper edits and changed the 51 rules to match i have reloaded those rules I have added the edited adb i have restarded linux i have changed cables phones usb ports and it picks up my friend og droid no prob but neither me nor my fiances epic will be recognized. any help please.
mikeew83 said:
I am still having same issue with adb and linux not recognizing my epic I have posted in regards to this and had no responses there all so many devs that work with epic and yet not one has commented to offer a fix i have tried adding 99-samsung.rules with proper edits and changed the 51 rules to match i have reloaded those rules I have added the edited adb i have restarded linux i have changed cables phones usb ports and it picks up my friend og droid no prob but neither me nor my fiances epic will be recognized. any help please.
Click to expand...
Click to collapse
This is the way its done. Sorry up front for quoting myself but I have responded to this issue in the past:
Download the file from this post
http://forum.xda-developers.com/showpost.php?p=8752645&postcount=5
Follow the steps with this post
http://forum.xda-developers.com/showpost.php?p=14199959&postcount=11
Profit!
Holy run on sentence Batman.
Sounds like a drivers issue, or that you don't have USB debugging enabled on the phone.
Open the Dalvik Debugging Monitor Service (DDMS) that came with the Android SDK.
Does it recognize the phone at all in DDMS?
If yes, then does it say "online"? If yes, then you have something blocking adb from talking to your phone from your computer. (firewall?)
If no, then you have a driver or USB connectivity issue. (bad driver installation, usb debugging not enabled on phone, bad usb cable, plugged usb cable into a port not directly on the motherboard)
EDIT: Looks like the post above me could understand the run on sentence more than I could.
You can also run the command lsusb and it should tell you if your system is seeing the device.
What Linux distro your running?
Sent from an Epic with 4G
ok to recap
I have followed your prior threads does not work. I have usb debugging on as explaiend i have tried everything means I have searched for hours on end and come with nothing. I have replaced the ADB and created 99-android.rules and edited that as well as editing the 15-android.rules files I have run lsusb and it does show samsung device.
tried your directions again
I have tried them again and they do not work.
Try the usb cable for the droid x. Its a really good one.
if that were an option
I have an incredible cord i can try that is about the only one but i dont see how it has anything to do with the usb cable when lsusb recognizes the device plugged in just adb will not list it on devices so that i dont think is the answer but thank you for the suggestion.
mikeew83 said:
I have followed your prior threads does not work. I have usb debugging on as explaiend i have tried everything means I have searched for hours on end and come with nothing. I have replaced the ADB and created 99-android.rules and edited that as well as editing the 15-android.rules files I have run lsusb and it does show samsung device.
Click to expand...
Click to collapse
You should only have 1 rules file, my suggestion, delete the 15 one and keep the 99.
Make sure the permissions are configured correctly, the biggest issue to run this type of operations in linux is the permissions and the ownership on the config files
Sent from an Epic with 4G
thanks
could you possibly explain this a bit more in detail as im still very new to this im a quick learner and great at researching.
mikeew83 said:
could you possibly explain this a bit more in detail as im still very new to this im a quick learner and great at researching.
Click to expand...
Click to collapse
Let me go over what to do:
After downloading the rules file on the above post, for example I have the SDK (adb) installed on my PC on the following path: ~/android/tools/, so go to your SDK folder (where adb is located) and run the chmod a+rwx adb command.
After this, take the rules file you downloaded from the above post and moved it to the /etc/udev/rules.d/ folder (logged as root, NOT SUDO). After doing this, run the following commands:
make sure that 51-android.rules file has the following permissions -rw-r--r (read and write for owner, group + others read only)
su [then placed the password] (Once again DO NOT USE SUDO)
chown root:root 51-android.rules
Once done, restart the PC and it should be working 100%. Before connecting the phone, make sure USB Debugging is active, and restart your phone.
Connect your phone via USB and run the lsusb command to confirm the connection of the device and then run ./adb devices and check for the positive return!
Note: if you have never had a password on su, run the following command: sudo passwd and change the password and try running the series of command above.
Note2: add your user to the plugdev group on your computer
Note3: sometimes while performing the ./adb devices command will return a response stating that a device by the name ?????????????? is connected, this is OK, you can connect via ./adb shell and you will see your device file structure, if you request SU permissions you will have to authorize it on the phone via the SUPERUSER app that gets installed when rooting the device.
IMPORTANT: The password for ROOT (su) user is not the same as the password you enter for the SUDO command (your user) unless you make them the same!
I'm not sure what exact problem you are having, but I was having a similar problem until this morning (of ADB not recognizing the phone) until I did this:
A) Open the phone dialer.
B) Enter "##8778#".
C) Set both options to "PDA".
D) Make sure sure "USB Debugging" is enabled under "Settings", "Applications", "Development".
I have no idea if this fully applies to your issue, but if it helps, great. If not, no harm done.
SweetBearCub said:
I'm not sure what exact problem you are having, but I was having a similar problem until this morning (of ADB not recognizing the phone) until I did this:
A) Open the phone dialer.
B) Enter "##8778#".
C) Set both options to "PDA".
D) Make sure sure "USB Debugging" is enabled under "Settings", "Applications", "Development".
I have no idea if this fully applies to your issue, but if it helps, great. If not, no harm done.
Click to expand...
Click to collapse
Though this is good info (thanks for pointing it out), I would highly suggest to leave UART as Modem, and just change USB to PDA.
Sometimes you may have issues with Tethering if you set the UART to PDA.
I have been a bit busy I appreciate the run down and will try it here tomorrow or its 2am so later today I also checked the 8778 and my usb is already set to what was specified.
Sent from my SPH-D700 using Tapatalk
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?
Morning all,
So here is the deal. Buddy of mine broke his phone last night, I gave him one of my spares and he is keeping that. I took his broken S4.
The screen si dead and the digitizer does not work
Had CWM flashed on it but stock rom when I gave him the S4 initially
I tried every possible way to get usb debugging working without the screen. edited the build.prop and default.prop
change the settings.db no luck
using adb in recovery i was able to flash cyanogenmod 10 as i read it had usb debugging enabled by default
well after the flash and booting the device (using an MHL) i still cant access an adb shell. I'm guessing i have to go through the setup process of cy mod before it kicks on maybe.
so i'm stuck here. now what I was hoping, and I know its a long shot. Could someone maybe make a nandroid of a stock rom, any rom that is rooted. but with vnc or other remote software installed and setup so I can flash and access this device.
I was also going to try to find a TV with CEC support as I heard the MHL will pass them through
If I can convince someone to upload a nandroid for me (I'll provide hosting) anyone have any ideas on controlling this thing remotely. I just need to be able to install arliberator, pair it with my cars deck via Bluetooth and i'll be good to go.
-pete
More thoughts. Having usb debugging enabled is clutch. Just realized, it wont be on my wifi so vnc wont work to well. I know droid vnc and do usb using adb. so maybe thats my best bet
making some progress
Copied the wifi settings from wpa+supplicant.conf from my brothers phone
so the S4 witht he broken screen now connects to my wifi
I installed the droid vnc apk using recovery
also installed it on another phone, setup the way I want
copied the settings folder from the /data/data frolder and copied it to the S4
chmod the folder and files to 777 and set 776 on "androidvncserver" file not sure about that step
cant get vnc to connect. but making progress
made a bit more progress
downloaded fastdroid vnc
pushed it to /data/ in recovery using adb
set 777 as i didt feel like dealing with permissions
made a super simple script to load it and placed in /data/local called userinit.sh or something like that
so it started and I was able to make a vnc connection, but it was all black and didnt accept mouse or key inputs.
i assume this is because it is no longer maintained and is many years aold
tried to do the same with droid vnc server and starting the androidvncserver file.
unfortunatly it never accepted a connection and i'm not even sure if the file starts
need more work
anyone willing to save me all the trouble and get me a nandroid with usb debugging enabled? pretty please! :crying:
Final update. Working
so I ended up placing androidvncserver in /data/
chmod 777 /data/androidvncserver
placed my wpa_supplicant.conf in /data/misc/wifi
chown system.wifi wpa_supplicant.conf
made a userinit.sh and pushed to /data/local/userinit.sh
chmod 777 /data/local/userinit.sh
reboot
connected to wifi, accepted the vnc connection and mouse movement. still a black screen but with the MHL and the mouse. I was able to get ARliberator installed and connected to my appradio2 and configured everything there
done