Database Users

WiFi issues Unable to turn on/unable to scan for networks

Hello, I'm having an issue, I'm rooted with the nand unlock method. I was on flipz .1d but have now moved to .2. I've had this issue a number of times now specificly the "unable to turn on" which seems to be caused by the owner of the /data/misc/wifi/wpa_supplicant.conf file changing to root. but I am not sure what causes the unable to scan for networks to happen.
Some of the things I have done that seem to be a part of the cause: I ran flipz vanilla lock screen fix and I team douche menu unlock, both seem to make changes to /system/framework/
anyone that might know where to look to fix the scan issue? I've searched the forum and have seen a few people have the problem but no solutions yet.

Was having the same problem (came across your post from a Google search).
I got a hint from code.google.com (can't post the link). I renamed the /data/misc/wifi/wpa_supplicant.conf to /data/misc/wifi/wpa_supplicant.bak (rather than delete it), rebooted and all is well.
Seems you can just delete the file, and it'll be respawned on a reboot.

I am having this problem, but on a vibrant that has not been rooted yet.
I cant seem to find the wpa_supplicant.conf, I have tried browsing for it using the built in file manager and using ASTRO, but the data directory is always empty.
Is there a way to fix this without rooting the phone?

if your phone has not been rooted then that means your phone is f**ked up and might need to be exchanged. but this is the evo forum not vibrant. the only way to mess with system files is to be rooted

Appreciate info*, worked in a heartbeat, saved from reloading everything from scratch, which was my way out last time. Witstech A81E Froyo 2.2
*renamed the /data/misc/wifi/wpa_supplicant.conf to /data/misc/wifi/wpa_supplicant.bak

Good eye there mate!!!!
InstantKarma said:
Was having the same problem (came across your post from a Google search).
I got a hint from code.google.com (can't post the link). I renamed the /data/misc/wifi/wpa_supplicant.conf to /data/misc/wifi/wpa_supplicant.bak (rather than delete it), rebooted and all is well.
Seems you can just delete the file, and it'll be respawned on a reboot.
Click to expand...
Click to collapse
I was experiencing the same issue and read this and it works, good looking out.

same issue on mytouch 4g
i used root explorer renamed tried no good the file stays renamed but the conf. appears under it after i try to enable wifi again help plz?

Who But BilL$ said:
i used root explorer renamed tried no good the file stays renamed but the conf. appears under it after i try to enable wifi again help plz?
Click to expand...
Click to collapse
It just recreates the file when your phone gets rebooted. My Thunderbolt is having the EXACT same issue. Ive tried renaming this and deleting as well and still no luck. Im now kicking over any rocks that I can find to get my wifi working.

I have exactly the same problem.
With Root Explorer deleted the file 'wpa_supplicant.conf' but no changes.
WiFi starts up and closes down again with the famous line: "unable to scan for networks"
anyone?

shoppy said:
I have exactly the same problem.
With Root Explorer deleted the file 'wpa_supplicant.conf' but no changes.
WiFi starts up and closes down again with the famous line: "unable to scan for networks"
anyone?
Click to expand...
Click to collapse
I actually ended up having to get a whole new phone. My insurance company couldnt fix it.

joeavery2 said:
2. I've had this issue a number of times now specificly the "unable to turn on" ......... but I am not sure what causes the unable to scan for networks to happen.
anyone that might know where to look to fix the scan issue? I've searched the forum and have seen a few people have the problem but no solutions yet.
Click to expand...
Click to collapse
I had the same problem. I installed the software from the sony erikcon website to my computer, and then followed the process for updating the phone software. That did not work, since I had the latest software already. So then, I tried to REPAIR my phone software, and after that was done, my phone was functional again, and the wifi works without any problems.
Requirements:
* A PC connected to the Internet (preferably broadband)
* USB phone-to-PC connection. Please see the accessories compatibility list for your phone.
1. Run the software on the computer after it is installed.
2. Follow the procedure for UPDATE or REPAIR (if you already have the latest version).

SOLVED WIYH THIS D12r a33_8723-8703_v11_0312 20141211.IMG
joeavery2 said:
Hello, I'm having an issue, I'm rooted with the nand unlock method. I was on flipz .1d but have now moved to .2. I've had this issue a number of times now specificly the "unable to turn on" which seems to be caused by the owner of the /data/misc/wifi/wpa_supplicant.conf file changing to root. but I am not sure what causes the unable to scan for networks to happen.
Some of the things I have done that seem to be a part of the cause: I ran flipz vanilla lock screen fix and I team douche menu unlock, both seem to make changes to /system/framework/
anyone that might know where to look to fix the scan issue? I've searched the forum and have seen a few people have the problem but no solutions yet.
Click to expand...
Click to collapse
I SOLVED WITH FLASH THIS: D12r a33_8723-8703_v11_0312 20141211.IMG

People still use this phone?

[Mod] Native WiFi Tethering MobileAP port from Galaxy S i9000 - Infrastructure AP!

According to the Vibrant forums, Jr33 has fixed and ported the MobileAP (native Infrastructure Wifi Tethering AP) from the Galaxy S i9000 to the Vibrant:
http://forum.xda-developers.com/showthread.php?t=756804
Why this is important and better than the Wifi tethering apps (Barnacle and android-wifi-tether):
This is REAL infrastructure mode. Not the hacked up ad-hoc mode (which android-wifi-tether and barnacle uses) which A LOT of devices (other android phones, ps3, wii, corporate laptops included) cannot connect to.
Because it being infrastructure mode, it supports WPA, a much more secure protection than WEP.
This is natively built into the Galaxy S i9000 phones. But taken out by AT&T and T-mobile. It just works, and works well - because it was MADE for our phones!
android-wifi-tethering hard crashes a lot on start, forcing you to do a battery pull, and may lose connectivity every so often.
Barnacle requires you to change the MTU of your client device, not possible in a lot of cases (consoles, phones, etc), and may cause conflicts when moving to a different wifi AP.
-------------------------------------------------------------------------------------------------------------------------------
Update 8/22:
Designgears has figured out a way to automatically launch the wlp2pservice on boot, therefore, no more manual entry is needed (but requires kernel flashing). Please see:
http://forum.xda-developers.com/showthread.php?p=7785171
The reason why it requires flashing the kernel (while Vibrant did not) can be explained by Jr33:
i know the stock kernel for the vibrant had the iptables included as well as wlp2pservice. what i have been finding is all these different features have just been commented out in different places. the same source was used for all three phones. you can see this when you start decompiling the odex files and comparing files, it is all the same. just needs a little tweaking here and there to activate certain features
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------
Update 8/20:
With the help of Jr33 (person that did the port to Vibrant), we *kind* of got it working with a few hoops. Jr33 should be given credit as he created and repackaged the captivate MobileAP update.zip; I was merely a test dummy. This thread will be locked when a solution is made and Jr33 will create a new thread with the final version. Go buy him a red bull!
REQUIREMENTS
Update.zip downloaded below
Rom Manager
ClockworkMod Recovery flashed on your phone (using Rom Manager)
Busybox
An Android Terminal App (ex: http://www.appbrain.com/app/jackpal.androidterm)
DOWNLOAD The Captivate mobileAP update.zip:
http://www.mediafire.com/?ownoqzgo6cbtmoj
File is also attached at the end of this post.
INSTRUCTIONS
Rename to update.zip, put it on your INTERNAL SD card root
Boot into ClockworkMod Recovery (using Rom Manager) and reinstall/update packages.
Reboot - note: first time boot after updating this will take a little while.
Now go into an Android terminal app and type the following:
Code:
su
busybox nohup /system/bin/wlp2pservice &
This starts the wlp2pservice. (Props to designgears for finding out this new command)
Old command (just typing in /system/bin/wlp2pservice in terminal (does not require busybox)) works BUT you will need to keep Terminal open during the duration, if force closed, you will have to retype that command in again.
5. Now you can go into Settings -> Wireless and Networks -> Mobile AP Settings to start your Access point.
Note: if you change any of the settings (AP name or WPA password) it may crash wlp2pservice. Use a task manager to force close "MobileAP Settings." Do step 4 again and your settings should be there.
This works until you reboot your phone. If you reboot, you need to go back into terminal and manually start wlp2pservice again (do step 4 again).
If you do not manually launch wlp2pservice, when you open up MobileAP settings, it just sits there on a black screen and if you check logcat, you see the looping message pasted below. We are currently trying to fix the necessity of manually launching wlp2pservice. This is not how it was intended to be.
-----------------
Developers with a Captivate, we need your help:
Upon opening MobileAP settings WITHOUT manually launching wlp2pservice in terminal, yields the following (from logcat):
Code:
I/ServiceManager( 3459): Waiting for service WLP2PService....
It loops until you force close "MobileAP Settings" in your task manager. Something is not calling wlp2pservice to execute.
Also, rebooting the phone or closing/ending terminal (on the pc or phone) requires you to go back into terminal and execute wlp2pservice manually, otherwise opening MobileAP settings yields the same loop above.
I am guessing that wlp2pservice is not launching on boot, or not executing at all when you open up MobileAP settings. I'm not sure which is supposed to happen.
This *seems* like an easy fix, and because Jr33 does not have a Captivate it is hard for him to help troubleshoot this. This is why we need other people to help figure out a way.

According to the front page: Update: This is a mod to add in the Samsung version of Mobile AP intended for the Galaxy S, but was removed by T-Mobile.
It was also removed by ATT, so wonder if it is possible :/

andy2na said:
According to the front page: Update: This is a mod to add in the Samsung version of Mobile AP intended for the Galaxy S, but was removed by T-Mobile.
It was also removed by ATT, so wonder if it is possible :/
Click to expand...
Click to collapse
This would be excellent to be ported over. While the current wireless tether (found in the associated thread) works... it does it in ad-hoc mode. This apparently supports infrastructure mode which would make it even more useful.
Go mods go!

rickgrob said:
This would be excellent to be ported over. While the current wireless tether (found in the associated thread) works... it does it in ad-hoc mode. This apparently supports infrastructure mode which would make it even more useful.
Go mods go!
Click to expand...
Click to collapse
wireless tether and barnacle "work" but still require you to go through hoops.
Wireless tether hard crashes A LOT.
Barnacle requires you to change MTU in your OS.

Please see OP for Update.

andy2na said:
wireless tether and barnacle "work" but still require you to go through hoops.
Wireless tether hard crashes A LOT.
Barnacle requires you to change MTU in your OS.
Click to expand...
Click to collapse
Yeah i changed my mtu (took like 30 seconds) and barnacle works great now. I was able to register for my fall semester from disneyland last weekend

I hope this isn't too far off topic, but would it then be possible to use a similiar techique to restore usb tethering to captivate ROMS in which AT&T has it removed/disabled?

jsmith8858 said:
I hope this isn't too far off topic, but would it then be possible to use a similiar techique to restore usb tethering to captivate ROMS in which AT&T has it removed/disabled?
Click to expand...
Click to collapse
When did it get removed? And i doubt the mobileAP is anywhere near related to the USB tethering samsung includes.

I currently have the stock rom, it has usb tethering. Mobile ap is related since they're both tethering.
Perhaps I can extract the file out of my phone where I to be instructed how.
Sent from my SAMSUNG-SGH-I897 using XDA App

Bowsa2511 said:
I currently have the stock rom, it has usb tethering. Mobile ap is related since they're both tethering.
Perhaps I can extract the file out of my phone where I to be instructed how.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I guess if you want to be completely broad they are both tethering solutions....
But their implementation i would assume is different and dont affect each other.

thanks Andy for bring this to Jr33's notice to get this implemented for Captivate.
was wondering if there is any app which wld start this service on boot or something like Tasker if it can start a system service.
Thnx

when i boot into recovery......theres no update option. I have the reinstall packages but it just says installation aborted.
Does the update.zip need to have lowercase "u"?? i did upercase, maybe ill try lowercase
Nope.......i ran into a problem i guess. I named the file to update and i boot into recovery with rom manager but when i get to recovery, there is no updates buttom (im guessing there never was?) I click reinstall packages and it seems to start installing the update.zip but then it says "Installation aborted"
help??

Edit: removed

pewpewbangbang said:
when i boot into recovery......theres no update option. I have the reinstall packages but it just says installation aborted.
Does the update.zip need to have lowercase "u"?? i did upercase, maybe ill try lowercase
Nope.......i ran into a problem i guess. I named the file to update and i boot into recovery with rom manager but when i get to recovery, there is no updates buttom (im guessing there never was?) I click reinstall packages and it seems to start installing the update.zip but then it says "Installation aborted"
help??
Click to expand...
Click to collapse
It's not a signed .zip bro. You need to download rom manager off the market if you don't have it, then reboot recovery from it and it will put you into clockwork recovery mode and then run the update.zip from that. It also lets you run other .zips even if they aren't named update.zip.
Hope that helps ya!
Sent from my GT-I9000 using Tapatalk

anilkuj said:
thanks Andy for bring this to Jr33's notice to get this implemented for Captivate.
was wondering if there is any app which wld start this service on boot or something like Tasker if it can start a system service.
Thnx
Click to expand...
Click to collapse
I thought about that, but because it has to start your terminal program and execute the wlp2pservice (and leave it running), I'm not sure if it had a large impact on battery life.
I setup Better Terminal Emulator to have a shortcut key to type out "/system/bin/wlp2pservice" for me, so its a few taps and Its ready. The amount of tethering I do right now is not that often that this is a big deal, but would be nice..

pewpewbangbang said:
when i boot into recovery......theres no update option. I have the reinstall packages but it just says installation aborted.
Does the update.zip need to have lowercase "u"?? i did upercase, maybe ill try lowercase
Nope.......i ran into a problem i guess. I named the file to update and i boot into recovery with rom manager but when i get to recovery, there is no updates buttom (im guessing there never was?) I click reinstall packages and it seems to start installing the update.zip but then it says "Installation aborted"
help??
Click to expand...
Click to collapse
My bad, it should be "Reinstall Packages" then after selecting it, it makes you scroll down past all the No's to Yes, install package.
Make sure when you open up when you open up Rom Manager you see:
Current Recovery: ClockworkMod 2.5.0.4, if not tap Flash ClockworkMod Recovery. (maybe reinstall it just incase) Then tap reboot into recovery.

Ahhh yes got it. Thank you, I didn't flash my rom before. Got it to work now. Thanks =)

As a quick note:
Please mod alert the Original Post to get this moved back to the Captivate development forum, so more developers that know what they are doing can see this thread and hopefully chime in.
This *seems* like it would be an easy fix. wlp2pservice just needs to launch at boot.

New problem. When I try to run the command in android terminal is says
/system/bin/wlp2pservice
not found

Ok I ran into the same problem because my clockworkmod was borked, so I had to reflash Clockwormod Recovery. When you tap Flash Clockworkmod recovery, it replaces update.zip in your root of the SDCard, so when you hit reinstall/update packages, it just reinstalled clockworkmod recovery again, no harm done.
So what you need to do is redownload the mobileAP zip and replace the current update.zip with the one found in this thread.
Go back into Rom Manager and reboot into recovery (dont hit flash clockworkmod), then update/reinstall packages, it should work then.

[Q] How do I prevent a B&N OTA update?

OK, I thought I saw this mentioned -somewhere- on this forum, but I've tried searching in vain.... Most likely I just can't put together the correct search phrase.
I'm currently running ManualNootered B&N 1.3. I've read very conflicting info as to whether B&N can or will update a rooted OS, but is there a way that I can prevent it? I vaguely remember someone mentioning that they had a rooted 1.2 and woke up one morning to a screwed up 1.3. My biggest concern, of course, is the upcoming 1.4. Don't want to try that until someone figures out what might be needed to apply ManualNooter.

That happened to me. I had nootered a 1.2 and it was working beautifully!
Then I turned on wifi, checked my email and got force fed the update to 1.3.
I've just found an old text file on my PC that had directions to block the update though so I tried it out, it requires that you buy the SQlite editor from the market.
It is priced a $2.99 but I feel it was worth it if it works!!
You can still side load the updates if and when you choose to also!
So I bought the editor and followed these directions:
*Open SQLite. It will scan your entire Nook and find every SQL database file there. Even the hidden ones. It only takes ~10 seconds. (You may see a message about granting super-user permissions, which is normal.)
*Scroll down to DeviceManagerService, and tap on it. Then tap on devicemanager.db.
*Tap on the "registry" entry. It's easier now if you rotate to landscape, so you can see more of the fields in each entry.
*All the entries in this table start with "com.bn.device....". Look for the one that's labeled '...fota.mode" at the end.
*In the far right Value column, you'll see "Auto". Tap on that to select it. Then go down to the Status Bar at the bottom, and tap the Menu button (3 horizontal lines), and pick Edit Field.
*You'll then see a black screen with one entry, the field editing form. You should see the field name of "value" there, and its contents will be "auto". If it turned out that your selection picked some other field (they are pretty small!), don't panic! :smileywink: Just go back and retry until you get the right one.
*Tap on "auto" and the keyboard will come up. Backspace to delete the current contents, and enter "manual" in its place. Then tap Done. Then tap Save. Until you tap Save, you've changed nothing, so poking about is fairly safe.
*You can now exit out of SQLite if you like (it's not necessary), but you're not quite done yet, so don't enable WiFi immediately. To make sure that the system is using the settings you just modified, you need to force it to reload and "see" them. So just power your Nook off and back on. After it reboots, it will use your new settings from then on. That's it.
This file was signed ~Mark, and unfortunately I didn't add the username or anything, so Thanks go to "Mark"

Another method?
I found this over on the B&N forum. I don't know if it is more or less effective than the method above. Perhaps a belt-and-suspenders approach would be best - do both.
Link:
http://bookclubs.barnesandnoble.com...be-possible/m-p/1220616/highlight/true#M68396
And the complete OP:
Title:
Declining the 1.4 update should be possible
Text:
I am looking at build.prop from the 1.4 OS released with the Nook Tablet, with an eye to testing an edit of a system file, build.prop, to update the file and make a Nook Color look as if it is already on 1.4. So far, I'm not seeing anything which looks like a showstopper in the new build.prop for drawing elements out of it for a modded build.prop.
Once the actual update is out, I think I should be able to create a modified file very quickly that will tell the BN servers a device does not need the update as it is already running 1.4.
This is the technique I've used successfully to keep my device at 1.2, which I prefer to 1.3.
If my experiments work, I'll post both the raw build.prop, for folks with root who know how to mount /system as rw to simply copy in (after backing up their original build.prop) and as a set of Clockwork installable files. These will need to be run from a Clockwork disk but will not require rooting the device. One script will move your current build.prop and put in an edited one; a second script would remove the modified build.prop and restore your original so you can receive the update if you choose.

If you have a custom recovery in place, ie clockworkmod, it will prevent installation of the update. Your device will still download the update, but when it boots into recovery for install, it will fail. Reboot and you are back to normal. This has worked for me twice.

[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.

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