Database Users

[Think Tank] Fixing "Fix Permissions" in Froyo Builds

Ever since the first froyo rom until now (currently running Nero 4.1), Fix Permissions in Rom Manager and ClockworkMod Recovery has been rendered useless. It simply starts for a second then ends right after, and permissions remain unfixed. Is this a problem due to lack of source from samsung or is this a bug that has not been detected by devs, either way if its solvable I think its a minor bug that should have some attention and maybe a fix.
Thank You!

I thought I had read something about having the proper busybox installed, but I have changed mine and can't seem to get it to work ether. I have also uninstalled and reinstalled RM.

No need for a think tank. There is already a solution.
Apparently the script in Clockwork is looking for a file in the wrong place. You can change the script or you can copy and move the file it's looking for. Either one will work. I am unsure if Koush has been contacted about this issue.
Check out this thread. I use the solution in post #3 and it works fine.
Also, if you feel as though someone is being rude, just ignore it and report the post. The mods act quickly as soon as something is brought to their attention.

-thanks for your suggestion...worked great.
Keslynn said:
No need for a think tank. There is already a solution.
Apparently the script in Clockwork is looking for a file in the wrong place. You can change the script or you can copy and move the file it's looking for. Either one will work. I am unsure if Koush has been contacted about this issue.
Check out this thread. I use the solution in post #3 and it works fine.
Also, if you feel as though someone is being rude, just ignore it and report the post. The mods act quickly as soon as something is brought to their attention.
Click to expand...
Click to collapse
--Thanks for keeping this thread on-point. Almost got side-tracked there with all the other posts. Follow Keslynn's attached link. The fix worked for me.

Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant General

I'm trying to follow these directions... but I'm not sure where to get the packages.xml file.
Can someone please show me?
jnagar said:
Thank you--if it helps, I simply copied the packages.xml file into /data/system/ in order to run fix_permissions, and then just deleted the .xml file.
A temporary fix, yes, but I was just trying to fix a specific problem with ending phone calls causing an FC (see http://forum.xda-developers.com/showthread.php?p=9943863#post9943863).
Click to expand...
Click to collapse

rogue sound files
I wonder if permissions will fix the rogue sound files in my player?

Does anyone know if the fix permissions issue is limited to Rom Manager or if all other applications doing the same thing are affected? I tried using the "Root Tools" app to fix permissions, but it looks to be doing the same thing that occurs in rom manager.
- Mat

How to connect to a Mobile HotSpot. 2ways.

Hi guys,
Since the mobile hot spot is an adhoc networks, so tablet cannot recognise it
directly.
So I found a instruction which is called can solve this problem.
We simply replace the original wpa_supplicant with the new one.
And put it in /System/Bin/.
I did the root and copy, but it still cannot find the adhoc hotspot for me.
So anyone have any idea?
Solution 1: solving it with the magic "wpa_supplicant"
Solution 2: changing the configuration of hotspot in my mobile to a normal wifi.
I'm waiting for anyone who can solve this.
Cheers
Winston

Hmm. I have a mytouch 4G and the A500 connects to the hotspot easily. No mods, rooting etc. needing.
Is this in relation to phones that are using less than carrier proposed methods for enabling hotspots?

Hi Neo,
According to what I have had known so far, it seems that google blocks this function,
so someone modified the wap_supplicant to enable the hotspot functionality.

franva said:
Hi guys,
Since the mobile hot spot is an adhoc networks, so tablet cannot recognise it
directly.
So I found a instruction which is called can solve this problem.
We simply replace the original wpa_supplicant with the new one.
And put it in /System/Bin/.
I did the root and copy, but it still cannot find the adhoc hotspot for me.
So anyone have any idea?
Solution 1: solving it with the magic "wpa_supplicant"
Solution 2: changing the configuration of hotspot in my mobile to a normal wifi.
I'm waiting for anyone who can solve this.
Cheers
Winston
Click to expand...
Click to collapse
Solution 2 depends on your specific phone and its implementation. My Droid for instance doesn't support infrastructure hotspot (outbound), so I had to use the "magic wpa_supplicant" approach. Other phones may support infrastructure mode, either directly or through a 3rd-party wifi tether app.
In terms of solution 1 - if you get the wpa_supplicant (apparently a new version has been posted for those of us w/ 3.1 update) you also need to reset the permissions on the file to match that on the original file (which I know you backed up, right? ); easiest way would be through Root Explorer and set Read: (Owner/Group/Others), Write (Owner only) and Execute (Owner/Group). I'm too lazy to remember what the Terminal Emulator chmod command would be
As a reminder to all who do choose to replace wpa_supplicant, keep a copy of the original file, you never know when Acer's going to require a specific original file for any future updates (wpa_supp wasn't needed for the 3.0.1 update but was for 3.1)

Yes I would say do not delete or move the old file just rename by adding old to end of file name. Its how I done it renamed did the update changed back. And now all is well again.I used the same replacement file from before. No need for a new. Version

Hi Vereyn,
Thanks a lot.
Could you please provide the link to download?
Frankly, I have tried all wpa_supplicant in this forume.
None of them works for me.
My version is Android 3.0.1
Acer ICONIA A5011, rather than A500.
Cheers

franva said:
Hi guys,
Since the mobile hot spot is an adhoc networks, so tablet cannot recognise it
directly.
So I found a instruction which is called can solve this problem.
We simply replace the original wpa_supplicant with the new one.
And put it in /System/Bin/.
I did the root and copy, but it still cannot find the adhoc hotspot for me.
So anyone have any idea?
Solution 1: solving it with the magic "wpa_supplicant"
Solution 2: changing the configuration of hotspot in my mobile to a normal wifi.
I'm waiting for anyone who can solve this.
Cheers
Winston
Click to expand...
Click to collapse
Soo... Which rock have you been hiding under exactly? This is pretty old news, and there are already a few threads detailing exactly what you need to do... Hell, there's one on the first page of this forum section!

Dear Floating,
Could you please send the link to me? or at least give me the title of that article which
you are talking about?
Because it disappeared again now >_<;

Again,
yes there are many ad hoc articles, but none of them work for me....

franva said:
Again,
yes there are many ad hoc articles, but none of them work for me....
Click to expand...
Click to collapse
The links are in the forum, just scroll down a bit.
As for the articles not working... If they're not working for you, maybe you're doing something wrong or missing one of the steps?

[Q] Wifi Problems [Solved]

Phone: Samsung S4 mini SGH-I257m (Canada Rogers)
Android 4.2.2 I257MVLUAMK5
I used an app called "Wifi Pass Recovery & Backup" and it killed my wifi. It tries to turn on and fails. I could redo my phone completely but I would rather fix it.
I have tried many things:
I made a backup with the app before doing anything and restoring that did nothing. Using the in app "reset wifi settings" button also did nothing but remove my saved networks.
Using ES File Explorer I have looked at the /system/bin/wps_supplicant, /data/misc/wifi/wps_supplicant.conf, /system/etc/wifi/wps_supplicant.conf. Played around with permissions, owner and checked MD5 with backed up versions. One thing I noticed was that the permissions seemed to reset when I would reboot.....
I used logcat and couldn't gain any ground there.
Some post I saw said something about replacing /system/bin/wps_supplicant with the one from the stock firmware, but i couldn't figure out how to find the files in the firmware I downloaded. I did find a factory image from google and was able to extract the files I was looking for, but they didn't work either. No surprise there.
I would love some help this as you guys are the experts!
Thanks!

Are there any other files that have to do with wifi? They might be worth checking out.

Solved
Ok....So, I was able to fix the problem by going back to the stock ROM. Not what I was wanting but whatever.
In an effort to try to figure out what happened, I cross-checked the stock files with the the ones I had before.
- the MD5 checksum of /system/bin/wpa_supplicant was identical
- /system/etc/wifi/wps_supplicant.conf was identical
- /data/misc/wifi/wps_supplicant.conf had a difference with config_methods. Stock was 'physical_display', old was 'physical_display virtual_push_button keypad'
So as far as I can tell.....that one entry was the problem.

[Problem identified] CM 12.1 - Wifi connectivity VS mobile data priority problem

[Solution HERE: disable AFWall+-2.0-alpha2]
Hey there,
I installed the optimized CM12.1 20150602 with Xposed and Xprivacy and now I got a connectivity problem:
When I come back from flight mode or enter a known wifi, wlan0 connects to my local wifi but Internet still gets routed through mobile data (LTE).
ping rounter not possible
Wifi icon has a "!"
netcfg shows:
Code:
rmnet_usb0 UP 10.175.104.107/29 0x00000041
wlan0 UP 192.168.2.126/24 0x00001043
on turning off mobile data, wifi data starts working and keeps working when I turn mobile data back on
I tried with a clean system: no problem, added Xposed/Xprivacy: no problem. So I guess one of my apps with root access must have caused that bug.
Possible candidates: AFWall, AdAway, droid VNC, OpenVPN, OS Monitor, SSHDroid, Tasker, TB.
Anyone knows how to fix this? I guess it must be a problem of how and what gets prioritized.
The setup took me quite some time and it would be great if I could fix this without starting from scratch. Plus I'd like to know the source of the problem.
Log attached.

I run none of the apps you mention and have the same issue and it happens on all wireless networks. I know of two workarounds, if they can be called that.
First is to cycle WiFi from within settings. When I do that it normally works right for a few days after.
Second is to power cycle my wireless router. That normally only works for a day or so as well.
I personally feel this is a flaw in CM as I have also seen the exact same issue on CM and any ROM built from it.

FIX
I found a fix for my problem by trial and error:
First I dirtyflashed the system again which didn't help, so I thought the problem must be in /data... thats where wpa_supplicant.conf is located so I had a look at it and strangest thing was:
The priority numbers for high eventhough it had only three entries. I changed them to 1/2/3 and rebooted. After that automatic connection to wifi worked again. BUT:
I rechecked the
Code:
/data/misc/wifi/wpa_supplicant.conf
again and the priority was back to the old state: 41/47/38 - in this order for the only three networks.
So the fix for me was: Change priority and save. Reboot afterwards.
Can someone elaborate on how this could fix the problem?

Oh and I must revoke my solution. Didn't work on the other network. :/

OK next trial and fail: deleting wpa_supplicant so it gets renewed. No difference.
Maybe I just try to install a fresh install and just restore /data.

I tried deleting the whole /data/misc/wifi folder. Didnt fix it!
And now I even installed from scratch and restored /data only from backup. Didn't help either!
What do I have to remove to fix this???

Rule number 1 of the Optimized ROM: do not use Xposed if you want support. So, uninstall Xposed, make a logcat of your issue if uninstalling Xposed doesn't fix it, then send that to AntaresOne.
He doesn't read the threads in Q&A, and wouldn't reply to this one anyway because of Xposed.

Strephon Alkhalikoi said:
Rule number 1 of the Optimized ROM: do not use Xposed if you want support. So, uninstall Xposed, make a logcat of your issue if uninstalling Xposed doesn't fix it, then send that to AntaresOne.
He doesn't read the threads in Q&A, and wouldn't reply to this one anyway because of Xposed.
Click to expand...
Click to collapse
Yes, thank you, I know that.
I didn't report a bug, I'm just trying to understand the problem, so I won't run into it again.
I tried tried a clean system and a clean system with Xposed and Xprivacy installed and did not have that problem, so I ruled that out.
Lucky for me: I did mention that in my OP.

My point is that you're presenting your information to the wrong audience. You need to post the logcat, without Xposed, on the Optimized CM12.1 thread, if you haven't already done so. That way the people who can actually do something about it can attempt to fix it.
I do apologize however for not reading the thread properly. It was late at night for me and I was half asleep. *sigh*

SOLUTION
So I hope it is fixed now.
My last resort was to flash a new modem/non-hlos.
I was on a 4.4.2 modems (DTM-I9505XXUGNG8_I9505DTMGNG3_I9505XXUGNG8_HOME.tar) before and updated to the latest modems for T-Mobile Germany: DTM-I9505XXUHOD5_I9505DTMHOD1_I9505XXUHOD5_HOME.tar.
This seemed to have solved my Wifi problem.
Step-by-step (no data loss but still: make a backup):
Check which is the latest ROM for your country/carrier on sammobile.com
Download ROM on sammobile.com or samsung-updates.com (no account necessary).
Extract ZIP > rename extracted *.tar.md5 to *.tar > extract modem and non-hlos file from *.tar with WinRAR or the likes.
Shutdown mobile and start into Download mode (Vol-Down)
Run Odin, disable Auto-restart and flash modem and reboot back into Download mode (I did that twice because people were hinting that but I doubt it's necessary).
Flash non-hlos in case you have a S4-LTE version.
Reboot and test.
/edit: didn't fix it.

Solved this time?
I think I finally found the problem: AFWall v2.0-alpha2 seems to cause the connectivity problem.
As soon as I deactivate the Firewall connection won't have any problems. I can't believe I needed so much time to find the bad boy.
Guess I didn't want to reduce security on my system, so I tried to avoid disabling/deleting my firewall.

Android O Wi-Fi password file location

Hi All,
I've noticed in android O wifi passwords are not stored in /data/misc/wifi/wpa_supplicant.conf anymore. It's handy to back them up or recover long back saved networks.
Anyone have a clue where are them now?
Thanks a lot.

lalontra said:
Hi All,
I've noticed in android O wifi passwords are not stored in /data/misc/wifi/wpa_supplicant.conf anymore. It's handy to back them up or recover long back saved networks.
Anyone have a clue where are them now?
Thanks a lot.
Click to expand...
Click to collapse
Try searching with a file explorer for the name of one of those folders or files and see if anything shows up. Other than that, I don't know as I'm still on nougat.

DEVILOPS 007 said:
Try searching with a file explorer for the name of one of those folders or files and see if anything shows up. Other than that, I don't know as I'm still on nougat.
Click to expand...
Click to collapse
Nougat is still as it was from ics or even before I think.
Also in O the file is there at the same path, and it contains the same header as it does in android 7.* and before (some configuration stuff). What is not in the file is the list of all known networks and their password.

lalontra said:
Nougat is still as it was from ics or even before I think.
Also in O the file is there at the same path, and it contains the same header as it does in android 7.* and before (some configuration stuff). What is not in the file is the list of all known networks and their password.
Click to expand...
Click to collapse
Have you tried forgetting your WiFi network and connecting again with the psk?

DEVILOPS 007 said:
Have you tried forgetting your WiFi network and connecting again with the psk?
Click to expand...
Click to collapse
If I hit known network in android wifi options I can see all my previously stored wifi. Everything works perfectly. If I add new networks they will be added with no issues and remembered for ever and ever. (and obviously will not be added to the file). It is like this list is just somewhere else now on the phone.

I am waiting to see any apps that use the new location but I haven't found any. I have notified the developer of the app I use of the change but he has yet to release an update.
Essentially if you upgrade your phone to Android Oreo it will migrate the wpa_supplicant.conf to /data/misc/wifi/WifiConfigStore.xml.
That is the new file. The Wifi Password apps read the wpa_supplicant.conf which will still exist, however, any new connections made will be stored in the WifiConfigStore.xml file meaning that the Wifi Password apps won't "see" the new connections.
Worse yet, If you did a reset of your phone and you are starting from scratch you will only be able to get that information from the WifiConfigStore.xml file.
All is not lost, since you most likely have root for the apps to get that data in a nice gui, it means that you access that file directly (via a root explorer file manager) to see your connections and passwords.

Hey guys,
so I created an app that should help.
Please try it out at this thread, and leave feedback...
https://forum.xda-developers.com/android/apps-games/app-oreo-wifi-passwords-t3708043

dechronic said:
I am waiting to see any apps that use the new location but I haven't found any. I have notified the developer of the app I use of the change but he has yet to release an update.
Essentially if you upgrade your phone to Android Oreo it will migrate the wpa_supplicant.conf to /data/misc/wifi/WifiConfigStore.xml.
That is the new file. The Wifi Password apps read the wpa_supplicant.conf which will still exist, however, any new connections made will be stored in the WifiConfigStore.xml file meaning that the Wifi Password apps won't "see" the new connections.
Worse yet, If you did a reset of your phone and you are starting from scratch you will only be able to get that information from the WifiConfigStore.xml file.
All is not lost, since you most likely have root for the apps to get that data in a nice gui, it means that you access that file directly (via a root explorer file manager) to see your connections and passwords.
Click to expand...
Click to collapse
I have created an app that supports both devices below and over the android Orio, give it a try from this thread -
https://forum.xda-developers.com/android/apps-games/app-wifi-password-view-saved-wifi-t3852668

Hotfingers said:
Hey guys,
so I created an app that should help.
Please try it out at this thread, and leave feedback...
https://forum.xda-developers.com/android/apps-games/app-oreo-wifi-passwords-t3708043
Click to expand...
Click to collapse
Great App!
They are now stored in:
/data/misc/wifi/WifiConfigStore.xml