Database Users

Device name in WLAN

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

HOWTO: Ubuntu USB reverse tethering

def:"Reverse tethering" : sharing your PC's internet connection with your Android phone.
This is suppose to work with any rooted Android device with the latest of Busybox. I own an Atrix and I use Ubuntu, and it works. If you own X and use Y, I don't care . It is also suppose to work with any USB tether-able Android device (like in proper, not the kind where you need to download an app for your PC to set up a SOCKS proxy of some kind).
I also use the Gingerbread ROM leaked for AT&T. This was done on Ubuntu 11.04 Natty, but the principles stay the same.
Let's get on with, shall we:
INSTRUCTIONS
Install Firestarter and DHCP server
sudo apt-get install firestarter dhcp3-server
Connect to the internet
Like you normally would. If you connected via WiFi, your connected device would probably be wlan0, if via ethernet - eth0, if via dialup - ppp0. If you are unsure, click on the Network Manager icon and click on Connection information. Otherwise, run ifconfig to see which device has got what IP address (to give you a hint as to what network device your PC is using).
Start USB tethering on your Atrix
Plug in the USB cable in your Atrix.
Under Settings -> Wireless -> Tethering & Mobile Hotspot -> USB Tethering checked.
Your Network Manager will try to get an IP address (and will probably succeed). Click on the Network Manager icon (probably the icon has changed to an ethernet port to signify that you are connected via USB) and click on "Edit Connections".
Under the "Wired" tab double-click on USB0 to edit it
Under the "IPV4" settings click on the "Routes" button
Check the "Use this connection only for resources on its network"
OK, Save
You'll see the Network Manager icon will change back to its previous icon.
Configure Firestarter
Run firestarter
If it is your first time to start firestarter, it will prompt you with the First Run Wizard. Otherwise, click on Firewall -> Run Wizard
Click Forward to get past the intro screen.
In the drop down box, select the device you are connected to the internet with.
Click forward
Check the "Enable internet sharing" option
On the checkbox, select the "Unknown Device (usb0)" as your Local Area Network device
Check the "Enable DHCP for local network" option
On the DHCP server details, select the "Create new DHCP configuration:" option
Click forward
Uncheck the "Start Firewall now"
Click save.
Great, so Firestarter is set up. But, it saves the dhcpd.conf file (Natty specific? I don't know) in the wrong directory (/etc/dhcpd.conf instead of /etc/dhcp/dchpd.conf).
sudo mv /etc/dhcpd.conf /etc/dhcp/dhcpd.conf
Start the Firestarter firewall (in Firestarter, press CTRL-S)
Configure the Atrix
2 Options:
1) While the device is connected via USB (and Applications -> Development -> USB debugging is enabled)
sudo adb shell
su bash
netcfg usb1 dhcp
2) Run in your terminal on your phone:
su bash
netcfg usb1 dhcp
If nothing failed, then everything worked. The principle is this : IP Chains between USB0 and <internet connecting device> (set up by Firestarter) with DHCP server running. This may not be the most über geek way of doing things but is sure point-and-clicky-easy-ish.
Et voilà, sweet reverse tethered nettubes...

No Enable DHCP checkbox
while i try everything .... i m stuck at the part where the 'Enable DHCP for local network' checkbox is inactive due to 'Chromium cannot be run as root'....
i dont know why this error kindly help me with this....

How is Chromium even related to DHCP and/or firewall settings?

failed
Code:
action 'dhcp' failed (Bad file number)
I'm using LightJB 1.2 Rom with CoCore-CWM 6.2

Unfortunately my Network Manager hasn't succeed when I turned USB Tethering checked on Android since I've upgrade ubuntu from 14.04 to 16.04.

adb unable to connect...

I was to B&N today, read few books in store (on nook)
Came home, tried to connect:
adb unable to connect...
run dropbear - unable to ssh
rebooted nook via terminal
adb unable to connect...
Scratched head…
rebooted nook again via terminal
adb unable to connect...
Did basic adb troubleshooting:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
adb unable to connect...
stop adbd
adbd &
adb unable to connect...
netstat
showed listening (with adbd running)
127.0.0.1:5037
0.0.0.0:5555
rebooted nook via terminal
rebooted PC…
adb unable to connect...
put noogie SD, reboot, check uRamdisk – same size & timestamp
removed noogie, off/on - connected right away!
I’m puzzled…
I saw few times, after 2-3 days of reading adb is unable to connect, but reboot fixed it always.
What was different this time?
“Cold reboot”?
I spend like 30min and feel like an idiot right now…

I was unable to connect over the usb port as well. Without too long investigation I've used adbwireless app on NT and was able to connect.
You might want to refresh server
adb kill-server
adb start-server
then connect using your NT ip address:5555 and you should be done.
In my case, I think, there are too many conflicting drivers installed and NT is not being recognized when connected.
Good luck

Adapt0r said:
I was unable to connect over the usb port as well. Without too long investigation I've used adbwireless app on NT and was able to connect.
You might want to refresh server
adb kill-server
adb start-server
then connect using your NT ip address:5555 and you should be done.
In my case, I think, there are too many conflicting drivers installed and NT is not being recognized when connected.
Good luck
Click to expand...
Click to collapse
I did it as well before every adb connect, thought it not worth to mention.
Naturally, "rebooting PC" should reboot adb server too, right?
But it didn't help either...

If you see this issue again, just try toggling ADB Wireless On/Off and it should reset anything on the devices side. Also I've noticed that sometimes and completely random from what I can tell "USB Debugging" will get unchecked, which will mess with ADB access via USB.

Disabling/Enabling ADBwireless sometimes may help.
Maybe a stupid question: Do you have a firewall running on your pc?

digiflash said:
Disabling/Enabling ADBwireless sometimes may help.
Click to expand...
Click to collapse
won't it be the same as below or it does more?
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
digiflash said:
Maybe a stupid question: Do you have a firewall running on your pc?
Click to expand...
Click to collapse
Always
I did check it too. It was nothing worth to mention.
abd attempted to connect - got nothing back (timeout)
on NST adbd was listening, I was able to access gmail.
I can ssh neither, and dropbear was listening too.
Looks, in fact, like firewall on NST was blocking all incoming connection.
That's why I wrote "Scratched head…" - which means I checked pretty much everything.
Could somebody explain, what is the major difference for NST between:
reboot (hot reboot) & shutdown/start (cold reboot)
Or more precisely for the latter:
insert noogie SD/reboot/remove noogie SD/turn off/turn on

ApokrifX said:
insert noogie SD/reboot/remove noogie SD/turn off/turn on
Click to expand...
Click to collapse
Cannot connect today at all. Cold reboot doesn’t help anymore...
Did some more tests (including ADBwireless):
I cannot ping [nook IP] from my computer
I can ping [nook IP] from router.
From PC
>telnet [nook IP] 5555
Connecting To [nook IP]...Could not open connection to the host, on port 5555: Connect failed
From router:
telnet [nook IP] 5555
Connection didn’t timeout (i.e. it does connect!)
Again, looks like something on Nook blocking connections from all IP, except from default gateway (i.e. router)
Question: Does rooting process unblock connections from other IPs?
About Disabling/Enabling ADBwireless:
Before running ADBwireless
netstat
127.0.0.1:5037
0.0.0.0:5555
netstat -tapn doesn’t work
stop adbd
both above disappear from netstat
start adbd
both show up
run ADBwireless
get message: ADBwireless is off
pushed button, message changed to: adb connect [nook IP]:5555
(adb connct didn’t work)
Switch to terminal,
netstat
127.0.0.1:5037
I.e. no more: 0.0.0.0:5555
Subsequent "stop adbd"/"start adbd" changes nothing:
netstat
127.0.0.1:5037
I was wondering what ADBwireless supposed to do then?
Could somebody check from his nook what netstat shows, please?
Nook can connect to internet (gmail, market) + netstat shows all outgoing connections…
What else can I try?
I guess, I can switch to adb usb…

It might be helpful if you tell what OS you are running on your PC and what did you do with NT. If we can reproduce your case then we can troubleshoot it otherwise you will hear useless guesses and speculations.
I like NT as a reader and nothing else. Web and games are looking awful on it.

Adapt0r said:
It might be helpful if you tell what OS you are running on your PC and what did you do with NT. If we can reproduce your case then we can troubleshoot it otherwise you will hear useless guesses and speculations.
I like NT as a reader and nothing else. Web and games are looking awful on it.
Click to expand...
Click to collapse
One box is XP with Outpost firewall (abd set to full trust).
Another win7 (FW policy – allow outgoing connections + few exceptions).
I’m Win developer/admin and Linux(CentOs) admin.
I’m complete noob when it comes to Linux non-shell related programming.
Router runs DD-WRT.
As of now I switched to uRamdisk_1_1_rooted_usb.
When I run dropbear, I see it listening on 22, but cannot ssh still.
That’s all I guess…
Could you do one test for me please?
If your NST runs uRamdisk_1_1_rooted_wifi:
Could you ping you NST from you box
If not - could you do same from your router/AP?

1. I don't have uRamdisk_1_1_rooted_wifi on my NT and can't test it.
2. adbWireless works on my Win 7 and Mac the same way. Both comps have firewalls running and both are on the same network. I can connect and ping NT.
Just for clarification I will describe how it works on my setup:
- I start adbWireless on NT,
- it asks for root permission if it for the first time and I grant it
- then shows fat button on the screen and says adbWireless is off
- I push the button
- it says adbWireless is on, from your computer run
adb connect 192.168.15.112:5555
At this point I can ping IP address and run adb shell.
I've rooted NT for purposes of software testing and customization. I did it twice with older and newer Nooter and did not find any noticeable differences.
Let me know if you want some other tests or info.

Adapt0r said:
I can connect and ping NT.
…
At this point I can ping IP address and run adb shell.
Click to expand...
Click to collapse
To clarify (trying to get a setup as simple as possible):
We connected NST to our home wireless network and it gets IP.
We didn’t touch adbWireless yet!
Now do two tests, please:
1. From NST we ping gateway or "another device on same network", (providing it let us).
2. From "another device on same network", ping NST.
What do you get?
I thought, adbWireless just configure adbd for IP connection (as opposite for USB one) and starts it - nothing else.
If #1 works, but not #2,
and #2 starts working after you “hit adbWireless button”, than adbWireless does more then I wrote above…

Sorry, I didn't have time to do your test at home. I'll try today.
I think you are correct, adbWireless does configuration of connection by executing something like this:
Turning On:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
Turning Off wifi and start listening on usb
setprop service.adb.tcp.port -1
stop adbd
start adbd
Cheers!
Edit:
Ping NST_ip_address from PC works fine.
Since I don't have terminal installed I could not test reverse pinging.

Ouch…
Just figured out:
1: I press “big red button” in adbWireless.
2: I push back button
And it pushed adbWireless into background.
If it’s the same as turning it (adbWireless) off,
it’s possible, that adbWireless reset adbd service to use USB.
Thus there is nothing listening on 5555 when I run netstat in terminal on NST.
Who’s with me?
Should be east to test:
press “big red button” in adbWireless.
I push back button
try to connect

ApokrifX said:
Ouch…
Click to expand...
Click to collapse
Updated router firmware - I can ping nook and ADB over wireless works too.
Not sure thought, if it was wireless channel problem.
I've read somewhere, some NST firmwares doesn't work on high channels or certain combined modes - like works on A+B, but not A+G
Apparently, NST firmware 1.1.2 was targeted to solve some of these issues.

PROBLEM SOLVED.
I didn't have the proper folder for the adb.exe.
-----
I have a similar problem: I recently rooted my nook simple touch with touchnooter 2.1.31, and all seems well but I can't connect to the adb wireless. IP is 192.168.0.6:5555 according to adb; I can ping from my Win XP computer if I use 192.168.0.6, but not if I add the 5555, but I just can't connect to the ereader. Wireless connections seem fine otherwise. I've tried shutting off and one the wireless adb.
I'm a complete beginner in this. On the reader, the screen has this:
"from your computer run: adb connect 192.168.0.6:5555"
This suggests that I can't simply use a firefox browser to connect? I tried using the windows cmd box, but windows indicates it doesn't know what 'adb' is. Then I found a website about adbwireless: http://theunlockr.com/2011/04/12/how-to-connect-to-your-android-device-through-adb-wirelessly/
and installed Adroid SDK Tools as indicated. When I use the cmd window, go to the proper sdk tools subfolder, and type 'adb connect 192.168.0.6:5555', windows still insists it doesn't recognize 'adb'
Please help!

try adb.exe

Meter 13,
Thanks for the reply. I added a pre-script to my op. I had created a bat file to move to the proper folder but had realized that the adb.exe had been moved to the platform-tools subfolder from its old location in the tools folder. Once I realized this, all worked well - connected to my nook, and used adb to install an apk file.
Bob

Just a note:
Ping isn't the usual TCP/UDP stuff, so there are no (port) numbers on the end.
ping 192.168.1.27
ADB uses TCP and a port number but it usually defaults to 5555
adb connect 192.168.1.27
adb connect 192.168.1.27:5555
You can also telnet to check if you can connect to the nook via TCP and port 5555
telnet 192.168.1.27 5555
(Note: If this works it will tell you that you are connected, but you can't do anything because ADB is a binary protocol.)

I had the same problem, turns out the correct drivers weren't installed. Ive downloaded HTC sync from HTC.com. I installed it and removed HTC sync afterwards. The drivers should stay there. Now reconnect your phone and try "adb devices" Before ADB wouldn't recognize my device but now it does. Tried to "adb backup -all" again, and it worked instantly.
Maybe this solves the problem?

You could try going back to a stock /boot partition.
I run my nstg rooted with the addition of about 8 files (su, xbin, busybox in system, adb wireless in /data plus a launcher) when I first root.
with the nstg, at least, I don't actually need the modified kernels - adb connects from my computers to the nstg, I simply don't have a root shell when I first connect.
This is fixed by doing an
su
once I'm in
Might be worth trying a restore of just partion 1 from your backup?

[Q] How to modify MAC address without reboot?

I have rooted my Nexus 7. Currently, the only way to change my MAC address is the following:
Code:
$ echo -n <MAC> > /persist/wifi/.macaddr
Using busybox ifconfig seems to work because new HWaddr is shown but in fact it doesn't - Settings->About tablet->Status shows old Wi-Fi Mac address. Additionally I cannot connect to AP any more. OpenWRT says:
deauthenticated due to local deauth request
Click to expand...
Click to collapse
I can write a script to automatically write new MAC to /persist/wifi/.macaddr and reboot, no problem, but I would prefer to avoid rebooting.
Kernel version 3.4.0-g03485a6, Android 4.4.4, Nexus 7 2013 Wi-Fi only.

Is this possible?

Has anyone ever got this to work? I'm searching on a way to have my MAC address changed upon booting the device and keeping it that way. Using ifconfig/busybox just allows you to change the MAC on that "boot session" and reverts back when you disconnect from an AP. I want to change my "stock MAC" from the get-go so that if I disconnect from an AP, it wont go back to the actual one. There is no /persist/wifi dir on my Nexus 7. Anyone who has done this before who can tell me how to do it?

Set manual network configuration (hidden SSID, static IP, gateway, etc.) on Android W

Dear xdadevelopers,
I have a Huawei Watch running Android Wear 1.3.0.2176821
Now I would like to write my manual network settings on the device in order to persist and make other settings unavailable.
I am able to login using adb shell but now I am a bit overwhelmed how/where to apply my settings?
On Ubuntu, I am setting my custom configuration in
Code:
/etc/network/interfaces
and
Code:
/etc/wpa_supplicant/wpa_supplicant.conf
which works perfect.
1. How can I login into the Watch as root to work there?
2. Where can I modify my network settings?
If root access does not work:
1. Which other possebilities do I have (maybe a start script, flashing with another Android Wear image, applying network settings in an app which is being installed on the device, etc.)?
Thank you an best,
Marcel

Mobile network

You can root your watch, you know? And it isn't like the Android os where oems usually lock the user form doing that. So it's quite easy, then just run adb shell and then su and badabam

Connect via App
Do you know an option without having to root the device? There is an app out there which makes it possible to connect to WiFi networks directly called "Wear WiFi"
RAZERZDAHACKER said:
You can root your watch, you know? And it isn't like the Android os where oems usually lock the user form doing that. So it's quite easy, then just run adb shell and then su and badabam
Click to expand...
Click to collapse

tur-ing said:
Do you know an option without having to root the device? There is an app out there which makes it possible to connect to WiFi networks directly called "Wear WiFi"
Click to expand...
Click to collapse
I have it, and I love it. But I'm not sure it can set IP addresses etc.