This is useful for identifying phones on the local networks by looking at DHCP lease tables in the routers. It doesn't make your phone appear on Windows networks, since the phone needs to broadcast NetBIOS name for that. If you want your phone to show up on Windows networks (and share files) - you need Samba server, and JimmyChingala is working on one.
ROM developers can insert the option to customize hostname using the way described below in their Spare Parts options. Feel free to do so.
[SOLUTION]
The following shell command does the job of changing WiFi hostname:
echo YOURHOSTNAME > /proc/sys/kernel/hostname
Click to expand...
Click to collapse
For the change to stay, it should be executed on each boot. And here the things start being more problematic.
For custom ROMs:
Most, if not all, custom ROMs include some user init shell script that will be executed on boot, making the solution easy.
Enter the following line in the Terminal / ADB shell:
echo "echo YOURHOSTNAME > /proc/sys/kernel/hostname" >> the_path_and_name_of_userinit_script.sh
chmod 777 the_path_and_name_of_userinit_script.sh
Click to expand...
Click to collapse
Several examples of custom ROMs and their userinit scripts:
Suggested - will work for most ROMs (creates another file in directory of autoexecuted scripts): /etc/init.d/88hostnameinit
Additional possibility for Enomther's ROM: /data/local/userinit.sh
Additional possibility for CyanogenMOD: /sd-ext/userinit.sh
For stock ROMs:
There is no autorun script for stock ROMs, so they have to be added through modifying boot.img. It's a complicated procedure, and even though guides exist for it - I suggest not to mess with it only because of the hostname. The easiest solution would be to create a script file with the line above using Gscript or other scripting solutions, and execute it after each reboot. If anyone really wishes to modify boot.img - I assume that he/she knows enough about Linux/Android since it can be relatively easily done only on Linux, can find the necessary guides with some googling (like I did), and in this case the modification is easiest to do directly in init.rc - changing "hostname localhost" to "hostname name_of_your_choice".
[ORIGINAL POST]
Hi people,
I'm not much of a dev, but I can find my way around with a bit of Google search And sorry about the links that don't link, new user's permissions don't allow me to...
Anyway, after messing with my router today I've noticed that Nexus transmits "localhost" as its host name to DHCP server, causing my DD-WRT to show it as "*". I went to Google and to my surprise, discovered that there isn't such an option in any Nexus ROM yet.
Found this: LINK_www_laslow_net_?p=501
To change your hostname on Cyanogen 5.x, add the following line to the bottom of /system/etc/init.d/01sysctl -- and make sure you make a backup of 01sysctl before editing it!
echo NEWHOSTNAME > /proc/sys/kernel/hostname
Click to expand...
Click to collapse
I tested it, and it didn't work. After booting, the file still read "localhost" in it, and the hostname on DHCP server reflected it.
But, I didn't get frustrated, connected with ADB, manually executed the command:
echo MyHostName > /proc/sys/kernel/hostname
checked that the file was overwritten, disabled WiFi, deleted DHCP lease, enabled WiFi back - and voila, I have a new hostname!
Then I went to search for hostname setting, which got me to /init.rc:
on boot
# basic network init
ifup lo
hostname localhost
domainname localdomain
Click to expand...
Click to collapse
Well, I guess that's the place. A tiny problem, though - it's in the boot image, which can't be easily modified. Thanks to the latest thread on update.zip creation I can probably do it myself, but I wanted to share the findings and ask for the correct way to implement.
There's a "dirty but functional" way of "disable WiFi - override /proc/sys/kernel/hostname - enable WiFi", and it's probably not a problem to stick it somewhere in the boot sequence, or even write an app that writes those changes to one of the boot scripts and allows configuration of host and domain names. But it's not the best way - DHCP might already give out a lease, and the new host name might not register.
And there's a correct (?) way of doing it, introducing it into init.rc. Since it's "on boot", I suppose that it runs after mounting the partitions - which means that the partitions are already accessible.
In this case, the best way would be executing a small shell script that would check for existence of, say, "/system/etc/settinghostdomainnames.rc" and create a default one if it's not there, then use "import /system/etc/settinghostdomainnames.rc" and set a manual trigger, like the guy is trying to do here:
LINK_groups.google.co.jp_group_android-developers_browse_thread_thread_e2f432707b735ff0
"trigger someeventtobringupnetworkinterface"
That would allow to use a custom setting for host and domain names that can be changed by SW, and adding that as another option into ROM Settings app or external app.
But the guy in question didn't succeed. What did he miss? Would it be better to do something like "on fakesystemproperty=something" and instead of manual trigger, doing "setprop fakesystemproperty something"?
I can probably test it and find out myself, but it would take loads of time compared to one of the kernel devs, and I don't even have the environment set up for modifying boot images. I was kinda hoping that one of the kernel devs would test it. I can write and post the modifications to init.rc and the custom script, they're very simple.
So, who can help me with answering the questions in the thread, and/or testing the modification?
Thanks! It's back.
Oh well, I'll keep preparing Ubuntu VM anyway
OK, first test fired - updated /init.rc in my own boot.img, checked the values. It's working, hostname is indeed modified.
Now I'll try to rewrite /init.rc in such way as to load the hostname setting from elsewhere, while not screwing the security. Will post results soon.
Setting it to the same value as the BT value would be ideal. I'm not sure how you could do that though, because the init scripts run before the frameworks load
Looking forward for a fix to this problem.
Update, but only partially on topic:
God, I hate SH scripting. Couldn't even google a normal tutorial that would explain where I went wrong. A script of 10 lines, and I can't make it work.
Let's see, I need something like this:
#!/system/bin/sh
echo "on service-exited-network_prepare" > /system/etc/net_init.rc
echo " ifup lo" >> /system/etc/net_init.rc
if [ -e "/system/etc/net_init.domain" ];
then
echo "hostname `cat /system/etc/net_init.host`" >> /system/etc/net_init.rc
else
echo "hostname localhost" >> /system/etc/net_init.rc
fi
if [ -e "/system/etc/net_init.domain" ];
then
echo "domainname `cat /system/etc/net_init.domain`" >> /system/etc/net_init.rc
else
echo "domainname localdomain" >> /system/etc/net_init.rc
fi
echo >> /system/etc/net_init.rc
Of course, this thing fails miserably with -
Syntax error: end of file unexpected (expecting "then")
What the hell am I doing wrong? Never used SH before, mostly tcsh and perl.
Thanks.
Oh well, I guess I got the problem.. Unix vs Windows file format. Sorry for bothering.
its always bothered me that you cant change the device name for wifi networks, and ive always looked for a way to change it.
kudos to you for the ambition and diligence to do it!
dont give up, if you can get it smoothed out enough im sure cyanogen will implement it in his next mod. ive always wished there was an option in wifi settings to change device name. itd be very useful for lan ip configuring and when your connected to a random hotspot lol
Ok, after fighting for a day, I still didn't manage to import another .RC file and run on service exit (I don't even see the trace of the process I'm trying to start - the first thing it does is attempting to write log, and there is no log, no matter where I put the start command), but at least for a "quick-and-dirty way" there's a very simple solution, given SD-EXT partition (I believe everyone creates it):
open terminal application, type the following command:
echo "echo YOURHOSTNAME > /proc/sys/kernel/hostname" > /sd-ext/userinit.sh
That would override the hostname of the system before boot completion.
After some reading, I believe there's nothing bad in setting the hostname twice - once default localhost in init.rc, and then overriding it using /proc/sys directory, Linux is designed to cope with that and hopefully so does Android.
So, as to pershoot's request, it's possible to write a small application to read Bluetooth device name value and write it as WiFi hostname, and include it in boot process right before 20userinit.
Now this is a task I'm not suitable for, I have no knowledge of frameworks whatsoever. Anybody up to the task?
Jack_R1 said:
After some reading, I believe there's nothing bad in setting the hostname twice - once default localhost in init.rc, and then overriding it using /proc/sys directory, Linux is designed to cope with that and hopefully so does Android.
So, as to pershoot's request, it's possible to write a small application to read Bluetooth device name value and write it as WiFi hostname, and include it in boot process right before 20userinit.
Now this is a task I'm not suitable for, I have no knowledge of frameworks whatsoever. Anybody up to the task?
Click to expand...
Click to collapse
I requested it and I'm not pershoot
Oops Sorry, my bad. Fever and lots of time in front of the computer don't do me good...
Kudos to you Jack_R1. Watching this.
Let me know if you need any help with shell scripting.
Gonna watch this and try it out later, the solution so far.
is this a stable fix?
is this confirmed to work?
Sorted out, updated with the most current info and several examples of custom ROMs.
Jack_R1 said:
Sorted out, updated with the most current info and several examples of custom ROMs.
Click to expand...
Click to collapse
I am running CM6 with a2sd and somehow the /sd-ext/userinit.rc is not executed. Even if I change permissions of the file to 777, it's not executed.
I also haven't found in init.d the script which executes userinit.rc, might be because I am running custom kernel? (wildmonks).
The only way for me to do it was to put the script in /etc/init.d/88userinit file and change it's permissions to 777
It's /scripts/userinit.sh, not userinit.rc
The execution of /sd-ext/userinit.rc used to be in /init.rc, in boot.img.
But the preferred way for most of the ROMs is to use /etc/init.d/ scripts anyway, since a lot of ROMs use them.
Changed the 1st post to reflect it.
Hi, i have a folio 100 rooted with SuperOneClick, but when i try to connect me to a proxy with Transparent Proxy it says:
failed to start redirect.sh
permission denied
i find a solution and now i have root access with the app, but when I try to turn the proxy on, I get this error:
"Failed to start redirect.sh (FIX ME! implement
getprotobyname() bionic/libc/bionic/stubs.c:378
iptabels v1.3.7: can't initialize iptables table 'nat':iptables
who? (do you need to insmod?)
Perhaps iptables or your kernel need to be upgraded"
the message repeats.
Nobody has a solution?
gilms said:
Nobody has a solution?
Click to expand...
Click to collapse
I don't have a 'solution' but you can diagnose the problem more easily if you have the file /proc/config.gz on your device... copy it off and unzip, open and look for:
Code:
#
# IP: Netfilter Configuration
#
These are the ones that probably matter?
Code:
CONFIG_NF_CONNTRACK_IPV4=y
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REDIRECT=y
I have a lot more set to =y on my device (Atrix)
You probably also need to have the 'iptables' binary in /sbin
You'd probably do best to start from a newer kernel that some dev modded for your device, and already enabled netfilter... then all you need is iptables
Hello Everybody,
I have flashed my phone with gestures script TouchGesturesSample-v1.1-s3-CWM.zip as described in this thread
http://forum.xda-developers.com/showthread.php?t=1831254&page=4
Of course i have the latest Siyah kernel on my Samsung S3 i9300/ ROM: XXDLJ4/ no mods, other scripts installed/ I have Tasker installed but i'm not usuing any gestures there
The instalation was successfull - no issues, but the gestures are not working - nothing happens
So I have tried to execute it manually. This is what I get
[email protected]:/system/etc/init.d # ls -l
-rwxr-xr-x root shell 5663 2008-08-01 14:00 S50GestureActions
127|[email protected]:/system/etc/init.d #
S50GestureActions
sh: S50GestureActions: not found
127|[email protected]:/system/etc/init.d #
./S50GestureActions
./S50GestureActions: line 52: can't create /sys/devices/virtual/misc/touch_gestures/gesture_patterns: nonexistent directory
There is a problem with the line 52:
" > /sys/devices/virtual/misc/touch_gestures/gesture_patterns
I have tried to make this directory manually, but it is not permitted, even with root.
Can anyone help? How to move forward? Pls help! I want to have this great feature on my phone.
Guys,
Pls help. I don't how to move forward
running Lenovo IdeaTab a2107a-f
android version: 4.0.3
I'm having issues with the renice command, which i have via toolbox(i believe).
I can issue a renice command and change the user priorities(-20 - 19), but i can't change realtime priorities at all.
Usage: renice [[-r] priority pids ....] -g pid
so i type this using random PID as example.
renice -r 99 1475
i use this command on my zte n9510, and it works great, but when i type the command on my lenovo i get the following error.
sched_set_scheduler: Operation not permitted
WTH??
I've tried every variation of the command.
if i use chrt i get the following error.
chrt -pr 99 1475
pid 1475's current scheduling policy: SCHED_OTHER
pid 1475's current scheduling priority: 0
chrt: can't set pid 1475's policy: Operation not permitted
anyone got any clues?? i can't even figure this out from a linux perspective let alone specifically android. I'm stumped. 8(
I did it!!!!
I can't tell you how long i've been trying to figure this one out. i even crashed my tablet at one point trying to crack it. well not entirely, but i did lose root which is just as bad so i had to restore.
so here's what i did to gain full control of nice and all priorities using the root account.
on my a2107a-f i went to /system/etc/permissions/platform.xml
i then added these 2 lines to the section about the shell permissions. you can add them to the last part of <!-------------Standard permissions granted to the shell-------------> or wherever you want i guess.
<assign-permission name="android.permission.CAP_SYS_NICE" uid="shell" />
<assign-permission name="android.permission.sched_set_scheduler" uid="shell" />
Then i rebooted, and logged back into root, and behold i had the powers i need. strangely enough though....you won't be able to just shell in with adb and use the renice command. you need to su after you do this edit, or you won't be able to renice the realtime priorities or anything.
i been trying to figure this out for weeks i think. i originaly went looking in etc/security, but it wasn't there. they moved it all to /system/etc/permissions/ and there appears to be lots of stuff to tweak in here.
now if i could just stop some daemons from respawning.
setting firefox to renice -r 99 <firefox's PID> and renice -20 <firefox's PID> really makes it fly on this slow browser after some other serious firefox tweaks. which i may just make a post here later. i'm pretty hardcore when it comes to waxing firefox on PC, and was glad to see my tricks worked on adroid too.
now that i got all hardware acceleration turned on, the OS stripped down, and my browser waxed to the extreme, this tablet's come a long way. it's comperable to some of the dual cores out there. i feel like i got a new tablet. 8D
Update!!!!
Something is weird with my fix. 8(
i rebooted by killing zygote and now i can't repeat the command anymore. i checked the platform.xml, and it looks like my changes stuck, but it also appears that maybe my changes weren't exactly what was creating the effect.
I had busybox installed on both machines, but as i mentioned earlier i had lost root when my permissions accidently got toasted. i was in a dir and typed the all powerful chmod -R 777 * -but come to find out i did it in the wrong directory and executed the command in /. LOL. so yeah, i lost root.
anyways i think maybe some ownerships got screwed up. so i checked the owner ship on my n9510 and renice linked to toolbox needs to be owner: root group: root, and toolbox needs to be user: root group: shell.
the lenovo has those permissions backwards, and so the renice command wasn't fully functional. once i switched em back to the aforementioned, i was able to renice -r 99 <pid> again.
now the question is, did my changes in platform.xml make any difference?? i can't remember, because i seem to remember playing with the permissions first and not getting the results i wanted, and then made changes to platform.xml, and then crosschecked ownership with the zte n9510, and set them accordingly, so i actually did 2 things at once, and thought it was my modified platform.xml that was providing the changes that i wanted.
so next step is to undo my platform.xml and see if that has an effect on being able to renice.
wth happened?? all i did was kill zygote or something and it changed my ownerships back around, but before that i had done a warm reboot from terminal with the reboot command, and it still worked, and retained my ownership. what a mess android is on the backend i tell ya.
anyone know how to make ownship changes stick /system/bin/??