I did some testing with wpa_supplicant to try and get wifi roaming to working
i added the bgscan code to my wpa_supplicant.conf, and it did work, but whenever i restarted the wifi the wpa_supplicant.conf would be recreated without the bgscan code
can anyone point me in the right direction, or has any information on how i would get android to add the bgscan line to the wpa_supplicant.conf
i originally found this post, and used it for testing
http://forum.xda-developers.com/showpost.php?p=46134045&postcount=15357
Maybe you could make the file read-only.
Otherwise you will have to use a script.
Related
I ran into the "Unable to scan network" and Wifi turning itself off the 2nd time today.
I remembered last time googling about this problem and found out 2 way
1. Do a factory setting, which I did the first time
2. Delete wpa_supplicant.conf and restart, which I tried this time, but apparently this doesn't work. Or maybe my memory served me wrong .
Anyway... now I don't have a wpa_supplicant.conf file in /system/etc/wifi/ anymore. I did a factory setting AND the hard reset (volume up + home + power) but the file is still missing. Now I can't turn on my wifi anymore.
I tried google for a default file to download but had no luck, if anyone can please upload the wpa_supplicant.conf file locate in (/system/etc/wifi/) that'd be greatly appreciated.
I don't really know much about these stuff so I wonder if it has to be the default factory setting file or not? But I think it may include some password in there so please blank it first...
I'm using Galaxy S, Android 2.1 and rooted.
Update:
I've search some more and found out some example and so I created the wpa_supplicant.conf file, content below:
#-------------
ctrl_interface=tiwlan0
update_config=1
network={
ssid="tenda"
key_mgmt=NONE
priority=11
}
#------------
and put it in /system/etc/wifi/, restarted... but it have the error "Unable to scan networks" again.
Please help
I don't know if this is possible but it would be nice to have APN settings in the startup file. Have to re-set it everytime I try another build.
you can always add your APN settings in the apns-conf.xml located in system/etc/ then when you change builds, just copy it and put in int the new build in root/system/etc and it will be copied automatically to the specified location.
Thanks. I open the existing file but don't see all info there. Do you have an example?
I'm interested in this also. I find myself using a lot of Android builds and I always have to make some modification to the APN settings. What are you using to access that location? Droid Explorer?
Sorry, I've been lazy with learning how to modify the system files using ADB or Droid Explorer... I'll get up to speed soon enough.
So I had the Ad-hoc patch working on my 3.1 4.010.11 using the Xoom's Wpa_supplicant file. I changed back to the stock wpa_supplicant file and then did a OTA upgrade to 4.010.13. rerooted and used es file explorer to copy back the xoom's wpa_supplicant and nothing in fact the wifi would not even turn on. Yes no wifi access at all. till i put back the stock wpa-supplicant. Any Ideas on a new patch?
Make sure the permissions on the supplicant file are correct. Just match the other files in the directory.
I had the same issue going from 3.0 to 3.1.
Thanks, that was it. Could not figure out what I was missing.
No problem. I spent about an hour trying to figure it out before I had the "Doh!" moment.
entropyiv said:
Make sure the permissions on the supplicant file are correct. Just match the other files in the directory.
I had the same issue going from 3.0 to 3.1.
Click to expand...
Click to collapse
Thanks entropyiv for posting this.
So I'm a novice here... I had the ad-hoc patch running for quite a while and got the update that zrhodes posted about. I tried the same things and also couldn't get ad-hoc mode running. I tried changing the permissions in the wpa_supplicant file to match the other files in the system/bin folder, rebooted and it's still not working (A500 is rooted). Am I doing this correctly? Thanks in advance.
PS. The current permissions are rwxr-xr-x
Stormyfour20 said:
Thanks entropyiv for posting this.
So I'm a novice here... I had the ad-hoc patch running for quite a while and got the update that zrhodes posted about. I tried the same things and also couldn't get ad-hoc mode running. I tried changing the permissions in the wpa_supplicant file to match the other files in the system/bin folder, rebooted and it's still not working (A500 is rooted). Am I doing this correctly? Thanks in advance.
PS. The current permissions are rwxr-xr-x
Click to expand...
Click to collapse
It is possible the file got corrupted during transfer. Did you try downloading the supplicant file again? Other than the permissions, I can't think of what could be causing the issue.
Maybe this dhcp issue i have seen floating around?
http://forum.xda-developers.com/showthread.php?t=1184646
Well this is curious. My GF and I both have HTC Touch Pro 2's and am using the wi-fi router application. It works using her phone, but not with mine. However, when I go to connect with the laptop to the phone, the "wifi router" shows up in the available network list. I try to connect using the tablet and it get's stuck in the obtaining IP loop. Well, didn't that frost me! So I had several version's of wi-fi router on my phone's sd card, tried installing another, and it works fine now. The wi-fi router application worked with my phone yesterday, before I updated to 4.010.13 GEN 2. Go figure...
One other thing to try is use Root Explorer to verify the owner and group of the file; long-press on wpa_supplicant file to bring up menu and select Change Owner. Make sure Owner is 0 - root and Group is 2000- shell. Copying the file into the folder using a file manager, or even simply extracting the file from a zip delivery, can change the file owner and/or group.
To avoid the permissions and groups issues w/ the wpa_supplicant file each update, I keep both the stock and ad-hoc files in the folder (/system/bin) and rename the files prior to installing any updates - the ad-hoc version gets renamed to wpa_supplicant.adhoc before updates and the stock version gets renamed to wpa_supplicant.stock after the update.
Carrier is just showing numbers on a AOSP rom I installed. I understand this is completely stripped but I was wondering how to setup the carrier name properly instead. I read that spn-conf.xml in /system/etc/ is what I should edit but there was no file so I created one and pushed it to the device with adb rebooted the device but no luck. Anyone know how to set this up? Thanks
maybe you lost the imei?
No phone works fine.. I know there is suppose to be a file that will read the numbers then display the carrier name. Before it use to be spn-conf.xml and you would setup the file as follows;
<spnOverride
numeric="302320" spn="Mobilicity"/>
</spnOverrides>
then push it to /system/etc and it would overwrite the file however in the new 2.3.5 this file is not present and was wondering if anyone with knowledge knows this. I would post in development but that is for projects and not for troubleshooting or chatting.
Thanks
Did you find a fix for this? I just installed CyanogenMOD 7.1 and am seeing these numbers as well (using Mobilicity on my Vibrant).
I am trying to change Sprint GS4 L720T 3g data indicator to a 4G data indicator, so whenever I connect to HSPA, I get the 4G icon instead of the 3G icon. I have identified the icon inside the SystemUI.apk file: it's called "stat_sys_data_connected_3g_spr.png." My idea is to change that icon with another one like "stat_sys_data_connected_4g_att.png" or "stat_sys_data_connected_4g_tmo.png".
Method 1: I used 7-zip to inter-change the name of the files within the apk and then moved back to modified file to /system/priv-app/
Method 2: I used apktool to rename the file name and the moved the re-compiled apk back to /system/priv-app/
The problem: With both method the device seems to detect the changes I made thru signature detection or some other method and the modified SystemUI.apk does'n't work.
I have even tried a de-odexed ROM and tried both previous method and the device keeps failing to recognize the apk.
Does anyone has any idea on how can I change SystemUI.apk without triggering the signature change?
PS: I was able to do this but only on a device that had a 15 digit EMEI instead of the 14 digit MEID. I cannot reproduce the problem again because I don't have any other device with a 14 digit MEID.
Can anyone at least lead me in the right direction?
Extract the pngs you want to use, rename them to the ones you want to replace, put back into apk
Profit
Or decompile/recompile properly
Or disable signature check
BTW, this isn't really relevant to the developer section