On Android 4 I could alter the wpa_supplicant.conf file (WiFi configuration file), reboot the wifi and the WiFi driver would adopt the changes in wpa_supplicant.conf. In Android 5, however, it seems that each time I reboot the WiFi, the wpa_supplicant.conf file is restored to the configuration it had before closing down. So all the changes that I make in wpa_supplicant.conf are overwritten by something.
Who is restoring the wpa_supplicant.conf? And how can I disable that?
I browsed through the Android source code and saw indeed backup calls for wpa_supplicant.conf file in IWiFiManager, but I didn't get any wiser than that :s I understand that this could be good for security reasons, but I am testing WiFi connections and I don't have a need for this wpa_supplicant.conf auto backup...
Related
Ok, time for another quick fix for the 4g LTE Tabs out there:
AdHoc WiFi so that you can get your Netflix going without blowing through all of your tiered tablet data!
Again, none of this is stuff I wrote, just stole from other threads and brought here.
Step 1: Root your Tab (See my other walk through if you need it)
Step 2: Download THIS wpa_supplicant file written originally for the Xoom. Doesn't matter where on your tab you download this to.
Step 3: Replace the file on your Tab
1. Turn on Airplane mode so that all of your wireless activities get shut off. Your tab won't let you get rid of the file if you have it still in use by your wifi.
2. Unzip the wpa_supplicant_xoom_wifi_adhoc.zip file that you downloaded above
3. Use Root Explorer (or similar) to navigate to \system\bin and rename your original wpa_supplicant file as something else (BackupWPA or whatever). You will need to "Mount as Read/Write" first.
4. Move the new wpa_supplicant file into \system\bin
5. Long click on the new wpa_supplicant file in Root Explorer and select "Permissions"
6. Click (activate) the check boxes under "Execute" for Owner, Group, and Others so that your system can use the new file (this is the chmod 755 step in adb or terminal emulator)
7. Un-mount as R/W in Root Explorer and Turn Off Airplane mode and you should see your wireless network pop back up (a * for the adhoc ones)
There appears to be a bug that the system will create multiple copies of the adhoc networks whenever you connect, but you can just Long Click to "Forget" the ones not in use.
Hope this helps someone else!
I am trying to sync a rostering app between two devices using dropsync.
The .db files that need syncing are in the /data/data/com.blah.blah/databases directory. Using Root explorer I can change the permissions to give full rw permission to others. The two .db files will then upload to the dropsync server.
The problem is that whenever the app is opened and anything modified, the permissions change back to default and thus dropsync can't access the modified .db
Is there anyway to change this or am I wasting my time? what is the 'sticky' box option in RE?
I'm not sure precisely what "sticky" means, but it's not what you want--it doesn't involve persistence or "sticking".
You could try to make the files not owned by the app but set it so the group is the app. Make sure the group can read/write/execute, or whatever it needs. This way, the app can still use the file but won't be able to change its permissions.
Of course, it could see that it doesn't own the file and refuse to run. I'm not sure what sort of checks the program's authors implemented. This also won't work if the file is deleted and created anew--the new file would be owned by the app.
Yeah thanks for that,
I tried the ownership and group swap earlier, and am pretty sure the app re- writes the db.
Don't think is going to work.
cheers
Well its obvious that the app, when opened sets the permissions to the .db files so that they wont be usable by others. The way you describe the problem is more likely to be a file owner problem and not with the permissions. Try to set the app and the files to the same owner and see if that works. You could always make a script that would change the permissions/ownership of the file.
FYI,
The sticky bit is a special part of the permissions mask for a file or directory. When set on a directory, it tells the system to prevent anyone but a containing file's owner from deleting files in that directory. This is handy if you have a directory that's being used by multiple users on a system as scratch space as it prevents people from wiping out others' files.
For files....the behavior isn't defined.
Hope this helps,
- chris
Hi guys,
I'm currently trying to manipulate the file /data/system/packages.xml in order to make Android start one of my apps with another user id. However, this doesn't work because it seems that Android recreates the file completely when shutting down the system which means the old user id is being written back into the file.
Without rebooting, changing the file's contents (or even deleting it completely) doesn't do anything either, it seems that the contents are being loaded into the memory on boot.
What I need are your ideas on how I can make my app run as another user (or edit the file permanently) I need this because I want to access another app's non-exported service.
Thanks in advance!
edit: Even if I try editing the file and then shutting down the system unexpectedly (One X, holding down power for like 10 seconds without using the software shutdown), the file is being restored after reboot. When I check the file in CWM after a normal shutdown, it's also back to normal. So I guess Android rebuilds it on shutdown AND on boot.. or something?
edit2: I just tried the following: Rebooting into CWM, editing /data/system/packages.xml from there, checking file contents (worked), rebooting system - file contents restored. I'm starting to think that this isn't the file I have to edit. But which one is it?
edit3: Tried editing /data/system/packages.list instead, didn't work either. The file is also being restored to the original state.
- Android 4.1.1, CM10, German
did u managed anything?got same issue
I saved password located in wpa_supplicant.conf from cm13 and now when i try to paste them in wpa_supplicant.conf on lineageos they doesn't work and the wpa_supplicant.conf get restored everytime. Any help?
no one knows how can i solve this?
Hey, I installed a new treble gsi today and wanted to edit the keylayout on my device (S8). I went to system/usr/keylayout and edited the generic.kl file. I then saved and exited. Then I set 755 permissions for the file and rebooted. This is what I've done multiple times before with the same file explorer and it always worked.
This time, after the reboot, everything was reset to how it was before I made any edits. The permissions are not the ones that I set, but that had been there before. The generic.kl file itself doesn't contain my edits anymore as well. I can even delete all the files in system/usr/keylayout and they still show up after a reboot.
Now the question is what is overwriting my edits and/or how can I find out what's causing this behaviour? I asked the devs and other people that have installed the gsi before, but nobody seemed to know.
Me too i have the same problem