Hi,
I have an issue with wifi hotspot configuration on my SGS2 running Darky XXKI3.
For some reason I can't change the setting for my hotspot.
No matter what I configure (another SSID, PSK or open) it always revert back to AndroidAP with a random generated password.
I know this is a not a ROM issue since I had this also with default stock ROM after flashing an update from CWM.
If I flash from odin everything works fine
Any suggestions hot to troubleshoot this?
I've been having the same problem after upgrading to XXKI8 running 2.3.5
hello, i had the same problem. had a look in logcat, it shows:
E/WifiService( 2677): Error writing hotspot configurationjava.io.FileNotFoundException: /data/misc/wifi/softap.conf (Permission denied)
so, to fix bring up a console (eg connectBot, or adb shell), and run:
busybox chown wifi:system /data/misc/wifi
chmod 770 /data/misc/wifi
and then it'll be working again.
Your script did the job!
I've had this bug since ki3, and i believe its common for ki* firmwares.
But now its OK. 10x
omniwolf said:
hello, i had the same problem. had a look in logcat, it shows:
E/WifiService( 2677): Error writing hotspot configurationjava.io.FileNotFoundException: /data/misc/wifi/softap.conf (Permission denied)
so, to fix bring up a console (eg connectBot, or adb shell), and run:
busybox chown wifi:system /data/misc/wifi
chmod 770 /data/misc/wifi
and then it'll be working again.
Click to expand...
Click to collapse
I tried your solution via adb shell, but I received:
chown: /data/misc/wifi: Operation not permitted
EDIT: I fixed this by simply giving write permissions to this wifi folder for group in Root Explorer.
omniwolf said:
hello, i had the same problem. had a look in logcat, it shows:
E/WifiService( 2677): Error writing hotspot configurationjava.io.FileNotFoundException: /data/misc/wifi/softap.conf (Permission denied)
so, to fix bring up a console (eg connectBot, or adb shell), and run:
busybox chown wifi:system /data/misc/wifi
chmod 770 /data/misc/wifi
and then it'll be working again.
Click to expand...
Click to collapse
Awesome that fixed it...thanks heaps for that omniwolf!!!!
omniwolf said:
hello, i had the same problem. had a look in logcat, it shows:
E/WifiService( 2677): Error writing hotspot configurationjava.io.FileNotFoundException: /data/misc/wifi/softap.conf (Permission denied)
so, to fix bring up a console (eg connectBot, or adb shell), and run:
busybox chown wifi:system /data/misc/wifi
chmod 770 /data/misc/wifi
and then it'll be working again.
Click to expand...
Click to collapse
Awesome. Fixed the problem a treat. Many thanks.
Hi, I've been having problem getting your script to work. I have root access on my Galaxy S2, got adb shell installed & started but after that I'm stumped. I tried to type:
busybox chown wifi:system /data/misc/wifi
but I'm given this as a reply:
chown: unknown user/group wifi:system
Am I missing something obvious? I am quite new on this...
Thank you!
The syntax of chown can sometimes vary slightly.
Try wifi.system instead of wifi:system
Note that your initramfs will clobber permissions on boot most likely - however once the file is created, it may be rewritable even after the initramfs hoses the parent directory's perms.
MadRoman said:
Hi,
I have an issue with wifi hotspot configuration on my SGS2 running Darky XXKI3.
For some reason I can't change the setting for my hotspot.
No matter what I configure (another SSID, PSK or open) it always revert back to AndroidAP with a random generated password.
I know this is a not a ROM issue since I had this also with default stock ROM after flashing an update from CWM.
If I flash from odin everything works fine
Any suggestions hot to troubleshoot this?
Click to expand...
Click to collapse
hello my s2 isnt rooted can i still perform this?? thanks
pinkysegun said:
hello my s2 isnt rooted can i still perform this?? thanks
Click to expand...
Click to collapse
No. You need root to change ownership and permissions.
guess i ve to keep changing the ssid then thanks
pinkysegun said:
guess i ve to keep changing the ssid then thanks
Click to expand...
Click to collapse
You could also update to 2.3.6; I believe it is fixed in that version.
EDIT: at least, I think it is fixed in newer versions of 2.3.6. That said, this thread (starting with post 12) suggests some possible fixes. I've not tried them, as I offer my own fix in that same thread, but that fix requires root...
i'm back
e4gleeye said:
Hi, I've been having problem getting your script to work. I have root access on my Galaxy S2, got adb shell installed & started but after that I'm stumped. I tried to type:
busybox chown wifi:system /data/misc/wifi
but I'm given this as a reply:
chown: unknown user/group wifi:system
Am I missing something obvious? I am quite new on this...
Thank you!
Click to expand...
Click to collapse
somehow i had another (different) wifi issue, was googling, and came across this thread again. weird.
anyway, i was having the same problem as the user above - unknown user/group system:wifi
for my problem, wifi wouldn't turn on at all until i chmoded /data/misc/wifi/wpa_supplicant.conf to 666. everytime i rebooted, it would change back to 660, and not work. argh1!!
eventually i worked out the owner was wrong, but everytime i tried to change it
chown system:wifi /data/misc/wifi/wpa_supplicant.conf
i would get the above error about unknown user/group
eventually i worked it out. if you go ls -al in the folder, you'll get something like this:
Code:
[email protected]:/data/misc/wifi # ls -al
ls -al
drwxrwx--- 3 1010 1010 4096 Apr 1 02:18 .
drwxrwx--t 11 1000 9998 4096 Apr 1 08:14 ..
-rw-rw---- 1 1000 1010 21 Apr 2 13:18 entropy.bin
drwxrwx--- 2 1010 1010 4096 Apr 2 13:18 sockets
-rw------- 1 1000 1000 24 Apr 1 01:46 softap.conf
-rw-rw---- 1 0 0 891 Apr 2 13:18 wpa_supplicant.conf
[email protected]:/data/misc/wifi #
do you see on the . and sockets folder the owner is 1010:1010 ? and on the wpa_supplicant.conf file the owner is 0:0 ?
well, that's the prob. i had copied in my own wpa_supplicant.conf file because titanium backup couldn't restore my wifi access points for some lame reason, and the owner was wrong. miror the . folder owner for this file:
chown 1010:1010 /data/misc/wifi/wpa_supplicant.conf
and you don't need 666 perms on the file, 660 is enough!
Thanks a lot !
omniwolf said:
hello, i had the same problem. had a look in logcat, it shows:
E/WifiService( 2677): Error writing hotspot configurationjava.io.FileNotFoundException: /data/misc/wifi/softap.conf (Permission denied)
so, to fix bring up a console (eg connectBot, or adb shell), and run:
busybox chown wifi:system /data/misc/wifi
chmod 770 /data/misc/wifi
and then it'll be working again.
Click to expand...
Click to collapse
omniwolf,
Thanks for the trick, it solved my problem which arose just after I reset the phone.
Instead of using a console, I took a different way to change the permissions.
I used the file manager "ES File Explorer" with root access to chmod the directory from 750 to 770.
I didn't issue the chown command and although the file softap.conf has been created, I've noticed that the permissions have been reverted to 750.
And I can still change the configuration (SSID or key) since the file already exists with 600 permission.
How those two points can be explained ?
Thanks for your answer.
Quick start for Wi-Fi configuration*After spend some days on CM11 Wi-Fi I want share with the community my new knowledge in order to simplify the life to who develop after me
For make it (very) simple, Wi-Fi envirorment in CM11 is structured in driver (make hardware exploitable) + Android system + wpa_supplicant (used by Android for communicate with driver).
In order to configure drivers is necessary modify BoardConfig.mk. It set the drivers and some related flag userfull for build CM system and wpa_supplicant. WARNING: Usually is not necessay specify any flags (e.g. XXXXX := true) because wpa_supplicant's Android.mk load all the correct configurations from android.config.
Before explain how to configure wpa_supplicant is needed introduce some concepts. For communicate wpa_supplicant and CM use sockets (is not importat that you know precisly what they are, you can image them as files). There are 2 kind of sockets in Andoid: Unix socket and Android private socket. At function level they are equivalent but your configuration must be coerent and use only one type.
In order to configure wpa_supplicant is necessary modify 2 files:
- init.xxxxx.rc: this file create the directory needed by wpa_supplicant and lunch it.
#Common socket dirs
mkdir /system/etc/wifi 0770 wifi wifi
chmod 0770 /system/etc/wifi
chmod 0660 /system/etc/wifi/wpa_supplicant.conf
chown wifi wifi /system/etc/wifi/wpa_supplicant.conf
#Android socket dirs
mkdir /data/misc/wifi 0770 wifi wifi
mkdir /data/misc/wifi/sockets 0770 wifi wifi
chmod 0770 /data/misc/wifi
chmod 0660 /data/misc/wifi/wpa_supplicant.conf
chown wifi wifi /data/misc/wifi
chown wifi wifi /data/misc/wifi/wpa_supplicant.conf
#Unix socket dirs
mkdir /data/system/wpa_supplicant 0771 wifi wifi
chmod 0771 /data/system/wpa_supplicant
chown wifi wifi /data/system/wpa_supplicant And then wpa_supplicant must be lunched like this:
#Android socket
service wpa_supplicant /system/bin/wpa_supplicant \
-iwlan0 -Dnl80211 -c/data/misc/wifi/wpa_supplicant.conf \
-e/data/misc/wifi/entropy.bin -ddd
class main
socket wpa_wlan0 dgram 660 wifi wifi #<- With this line you specify that is an Android socket, note the keyword "socket"
disabled
oneshot
#Unix socket
service wpa_supplicant /system/bin/wpa_supplicant \
-iwlan0 -Dnl80211 -c/data/misc/wifi/wpa_supplicant.conf \
disabled
oneshot
- wpa_supplicant.conf: this file give to wpa_supplicant the correct settings for run.
#(Minimum) Configuration for Android socket
ctrl_interface=wlan0 #<- With this line you specify that is an Android socket, note the relative path
update_config=1
#(Minimum) Configuration for Unix socket
ctrl_interface=DIR=/data/system/wpa_supplicant GROUP=wifi
update_config=1
That is all. As usual if something not work use adb shell, adb logcat, google and your brain :good:.
*It is litte more than a copy/past of my thread here.
Reference:
- http://blog.linuxconsulting.ro/2010/04/porting-wifi-drivers-to-android.html
- http://processors.wiki.ti.com/index.php/TI-Android-JB-PortingGuide
Dear Users,
I have a tablet - Acer Iconia A1-B71, which works fine but I dont have root permission what is very annoying when I want to do something with Files Manager or Total Commander. I readed this thread:
http://forum.xda-developers.com/showthread.php?t=2240029
But for my bad I get errors. Below is a log file from CMD:
http://pastebin.com/EEiihY01
The most important part is this (I think):
Enter a selection:
system.img.gz found in folder 'system_image'.
/data/local/tmp/busybox telnet 127.0.0.1 1234
chmod 777 /cache
chmod 777 /cache/system.img.gz
[email protected]:/ $ /data/local/tmp/busybox telnet 127.0.0.1 1234
telnet: can't connect to remote host (127.0.0.1): Connection refused
1|[email protected]:/ $ chmod 777 /cache
Unable to chmod /cache: Operation not permitted
10|[email protected]:/ $ chmod 777 /cache/system.img.gz
Unable to chmod /cache/system.img.gz: Permission denied
10|[email protected]:/ $ exit
failed to copy 'system_image\system.img.gz' to '/cache/system.img.gz': Permissio
n denied
opendir failed, Permission denied
Failed to copy system.img.gz. Make sure the folder 'system_image' of this toolki
t contains a system.img.gz suiting to your installed firmware.
Press Enter to leave Application...
Click to expand...
Click to collapse
If you can tell me - Am I doing something wrong? Is there any solution?
Thank you for the smallest help.
Kind Regards,
Raintek
Hi guys
The VidOn XBMC player allows for pass through of HD audio streams (DD TrueHD & DTS-HD MA) through HDMI (and probably SPDIF). However it requires some simple changes to the ROM source. Unfortunately I can't get access to Amlogic's Android 4.4 SDK since I am a personal Android developer. So much for open source
I was hoping one of you guys would build a new ROM from sources and implement the changes according to VidOn's guidelines. Like I said they are very simple and should not require much time
Required changes according to the VidOn support for XBMC:
Amlogic SDK Configuration - S802 S805 S812
1. Permission:
Please change the permissions in the two files below.
device/amlogic/common/init/mbx/init.amlogic.rc
device/amlogic/common/init/mbx/ueventd.amlogic.rc
chmod 666 /dev/amvideo
chmod 666 /dev/amstream*
chmod 666 /sys/class/video/axis
chmod 666 /sys/class/video/screen_mode
chmod 666 /sys/class/video/disable_video
chmod 666 /sys/class/tsync/pts_pcrscr
chmod 666 /sys/class/audiodsp/digital_raw
chmod 666 /sys/class/ppmgr/ppmgr_3d_mode
chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 666 /sys/class/video/blackout_policy
chmod 666 /dev/snd/controlC0
chmod 666 /dev/snd/pcmC0D0c
chmod 666 /dev/snd/pcmC0D0p
chmod 666 /dev/snd/pcmC0D1c
chmod 666 /dev/snd/pcmC0D1p
chmod 666 /dev/snd/timer
chmod 666 /sys/class/audiodsp/digital_codec
chmod 666 /sys/devices/platform/spdif-dit.0/spdif_mute
chmod 666 /sys/class/amhdmitx/amhdmitx0/config
2. Change:
frameworks/base/services/java/com/android/server/wm/WindowStateAnimator.java
Change this piece of code
boolean isNeedOpaque = attrs.getTitle().toString().contains("xbmc.Main") ? false : true;
to
boolean isNeedOpaque = true;
String attrsTitle = attrs.getTitle().toString();
if (attrsTitle.contains("xbmc.Main") || attrsTitle.contains("xbmc.kodi") || attrsTitle.contains("org.vidonme"))
isNeedOpaque = false;
I really hope someone will take the time to implement the changes according to the above links. Or maybe someone could help me get access to the Amlogic SDK. Like I mentioned I sent my public RSA key to Amlogic but they declined to allow me access to their SDK.
Thx in advance
So I'm trying to test a script, test.sh which I saved in /cache. Chmod + x test.sh returns bad mode, Chmod 777 and others, 700, 666, etc. does nothing to change the file's permissions and no errors are given. Just for giggles ./test.sh returns not found. Rooted with Magisk, issued su beforehand, terminal app has root (Terminal Emulator). What gives?
Even more interesting....
ls -la shows no changes, however Power File Browser shows the script is 770 and is able to change permissions and shows the permissions changing. It also shows that the script now simply named test is also getting it's permissions changed with chmod, so perhaps there is an issue with ls -la in Stricson's Busybox? But why can't I ./ ?
Ok. Doing a which ls and which chmod shows /bin, but busybox is in /xbin, however calling busybox directly busybox ls -la and gives the same result doesn't show the +x but busybox chmod +x does work, so the chmod in the stock ROM doesn't support using +.
Busybox ./test does nothing either.
Found the issue with the file not running ./ and not found had #!/bin/sh and it requires #!/system/bin/sh at the top of the script.
In conclusion the ls -la command does not work correctly.