I was trying to unlock the possiblity to connect my android device (droid 4, JB) to a wifi hotspot.
To do this I modified the wifi_supplicant.conf file. Since it didn't work I restored the original.
I also put a command in the terminal but now I cannot recall what, I'll look for that guide again to post it.
Now anyway each time I turn off the wifi (or the phone) I loose all the saved network, and I have to put all the password again.
How can I fix it?
Thank you!
I'm having the issue after updating my ROM, from older stock rooted to newer stock rooted.
I notice the AP entries with passwords inside the wifi_supplicant.conf file keeps getting erased, once you turn OFF and ON the WiFi
Why is this?
SOLUTION:
kevg77 said:
I have seen that others are having the same issue that I am having where my phone forgets WiFi settings after every reboot since MJ4 update. What is the fix for this?
Thanks
Click to expand...
Click to collapse
kevg77 said:
WiFi problems?
Try this:
Due to "securestorage" being set to true in build.prop, changes to the ROM or kernel that aren't reflected in the ss_id file in /system/etc/secure_storage/.system.bin.wpa_supplicant/ can cause issues with WiFi among other things. You can set this to false yourself, or simply flash the zip file below.
Download: Set Secure Storage to False
For those that prefer to do it manually, simply change this line ro.securestorage.support=true to false in /system/build.prop.
Click to expand...
Click to collapse
YOU'RE A LIFE SAVER!!!!!!!!!!!!!!!!!!!
:good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good:
Why was [ ro.securestorage.support=true] set to true? --Is this by ROM's default?
What functionality do we lose once it's set to "false"?
klau1 said:
SOLUTION:
YOU'RE A LIFE SAVER!!!!!!!!!!!!!!!!!!!
:good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good:
Why was [ ro.securestorage.support=true] set to true? --Is this by ROM's default?
What functionality do we lose once it's set to "false"?
Click to expand...
Click to collapse
Done, rebooted, but still not working.. I have the same issue when turing off/on WiFi...
AFAIK, it's a bug introduced in MJ4.
Related
Every time I try to use it, it always renames the access point back to "Android AP" and wipes the password as well - anyone come across a fix?
I'm running the official 2.3.5 firmware.
superdx said:
Every time I try to use it, it always renames the access point back to "Android AP" and wipes the password as well - anyone come across a fix?
I'm running the official 2.3.5 firmware.
Click to expand...
Click to collapse
I am not quite sure what your problem is.
Do you mean tethering?
And your phone does not keep the AP name and password for its own WLAN hotspot?
I am sure that there are some tethering apps on the Market.
Maybe one of them can help you to configure a customized AP name and password and saves it for later use.
Yep that's it exactly, tethering. The AP name and password keep resetting!
http://forum.xda-developers.com/showpost.php?p=18711488&postcount=128
clefster said:
This is because the permissions for the wifi settings got messed up so it can't write out your new permissions. The error handling isn't too good so it doesn't tell you about it
To fix, in a rooted terminal run this command:
chmod 770 /data/misc/wifi
Click to expand...
Click to collapse
After struggling with root, I tried your command and it doesn't work, says Operation not permitted
I think I'm gonna write a small app to enable ad-hoc mode as seen for other android models. Anyone interested ?
Must have:
Single button click to enable ad-hoc wifi mode
Restore option, to revert back to previous state
Check if root is enabled, check if device is supported
Anything missing?
-----------------------------
Update:
App is available in the market.
Reported to work on:
Samung Galaxy Tab GT-P7510, GT-P7500
Samsung GT-I9100 * (Samsung Galaxy S2) reported by PAD
Samsung SPH-D710 Galaxy S2 Epic Touch 4G * reported by Scott
Samsung GT-I9000 * (Galaxy S I)
Nexus S * reported by Arpit
BBK vivo v1 * reported by thesunfei
HTC Desire * reported by Jens
Droid * reported by James
* Requires compatibility check to be disabled.
Probably more devices are supported, I will add them when reported.
Market link: https://market.android.com/details?id=nl.arendmedia.wifiadhocenabler
Discussion: http://www.arenddeboer.com/wifi
This would be great...post a link when ur done
make sure to make two apps one that require pershoot kernel and another one without pershoot kernel just a stock one, if so the app will be great, gd luck.
tarekkkkk said:
make sure to make two apps one that require pershoot kernel and another one without pershoot kernel just a stock one, if so the app will be great, gd luck.
Click to expand...
Click to collapse
Why not check inside the app what kernel is used and act accordingly ?
BTW I have used the same procedure to enable ad-hoc for the stock kernel as well as the pershoot kernel, using the same wpa_supplicant file.
I envision the app should:
Check if the device is supported (for now P75XX)
Request/verify root access.
Check if device is already ad-hoc enabled by this app, if not continue.
Verify if wpa_supplicant in /system/bin/wpa_supplicant is in a sain state (verify md5 hash with original) if it doesn't match warn user if he still wants to continue.
Create a copy of the original wpa_supplicant file.
Copy adhoc-enabled wpa_supplicant to /system/bin/wpa_supplicant, overwriting the existing file.
chmod 755 /system/bin/wpa_supplicant
chown system.wifi /data/misc/wifi/wpa_supplicant.conf
Inform user to reboot for the changes to take effect.
I'm not an expert on wpa_supplicant so any help is appreciated.
adeb2 said:
Why not check inside the app what kernel is used and act accordingly ?
BTW I have used the same procedure to enable ad-hoc for the stock kernel as well as the pershoot kernel, using the same wpa_supplicant file.
I envision the app should:
Check if the device is supported (for now P75XX)
Request/verify root access.
Check if device is already ad-hoc enabled by this app, if not continue.
Verify if wpa_supplicant in /system/bin/wpa_supplicant is in a sain state (verify md5 hash with original) if it doesn't match warn user if he still wants to continue.
Create a copy of the original wpa_supplicant file.
Copy adhoc-enabled wpa_supplicant to /system/bin/wpa_supplicant, overwriting the existing file.
chmod 755 /system/bin/wpa_supplicant
chown system.wifi /data/misc/wifi/wpa_supplicant.conf
Inform user to reboot for the changes to take effect.
I'm not an expert on wpa_supplicant so any help is appreciated.
Click to expand...
Click to collapse
fyi, If you want it to work with all Android versions, don't forget that the wpa_supplicant is not always in the same spot(sometimes in in the /etc folder).
I would also like to see this app. Good luck xD
shaolinx said:
fyi, If you want it to work with all Android versions, don't forget that the wpa_supplicant is not always in the same spot(sometimes in in the /etc folder).
I would also like to see this app. Good luck xD
Click to expand...
Click to collapse
Thanks shaolinx,
It would be great to get all the info for the various devices.
I have started the build and completed the initial verifications, has root, md5hash comparison etc. If anyone can provide details about the location and specific wpa_supplicant files I can add it to this app.
check whenever Wifi On or Off, it will error when you change wpa_supplicant when Wifi on
and afaik not need to reboot for changing wpa_supplicant
Correct Me If I Wrong
AnakTeKa said:
check whenever Wifi On or Off, it will error when you change wpa_supplicant when Wifi on
and afaik not need to reboot for changing wpa_supplicant
Correct Me If I Wrong
Click to expand...
Click to collapse
Good to know, I will request flight-mode before proceeding.
I also noted that after switching to the new wpa_supplicant, the signal strength is no longer visible in the wifi icon. Does anyone know whether this is a known issue ?
adeb2 said:
Good to know, I will request flight-mode before proceeding.
I also noted that after switching to the new wpa_supplicant, the signal strength is no longer visible in the wifi icon. Does anyone know whether this is a known issue ?
Click to expand...
Click to collapse
Mine was stable after replacing the original wpa_supplicant file.
Update:
The app is nearing its final stages of completion. I will probably post the link around Sunday. Have to test it first on the stock rom as well as some of the new ICS roms. First version will be raw and unpolished but should be safe and in good working order. I will rewrite it after the initial release to make it easier to add new devices.
Absolutly YES! very interested
The app is ready, I'm currently pushing it into the Market. Will post the link here shortly.
https://market.android.com/details?id=nl.arendmedia.wifiadhocenabler
Request device support or report bugs in the comments on http://www.arenddeboer.com/wifi
Features:
- Enable WiFi Ad Hoc mode (and keep infrastructure)
- Restore original settings
- Fix WiFi permission issues
Requires:
- Root Access (Superuser)
- BusyBox
Issues:
- No WiFi signal strength visible in taskbar
Please be aware this might potentially brick your device (I have tested the app vigorously on several roms and found no problems). I take of course no responsibility for any real or perceived damage...
Let me know if it works for you so I can improve the app.
Regards
FYI.....Task 13.1 works with adhoc wifi, out of the box!
Thank to the TASK team!
Not sure when they did starting this into the Rom, maybe from Pershoot's kernel?
But thanks anyway. Save me time to copy the WPAsupplicantfile over, which I carry with me from Galaxy tab 7 days!
Hehe, at least it was a nice way of learning root lated tasks in app development But it's still handy as the current kang ics roms do not ship with a modified wpa_supplicant.
when i try to connect it says obtaining ip and after that it disconnects
Ad Hoc Wi-Fi can be a bit tricky to setup, can you create a connection with other devices? I also believe you can make only a single connection between ad hoc devices. So be sure the other device is not already connected.
It was fun working on this app, but is has proven to be difficult to make something that enables Ad Hoc on a wide spectrum of Android devices. Therefor I will no longer be updating the application and will remove the "report to developer" option. My next project: running Linux native on my Galaxy Tab P7510.
Starting point will be this thread by poitee -> http://forum.xda-developers.com/showthread.php?t=1189251
Thanks for the feedback.
Nice! Thanks for the app.
I deleted my apk :-( and it doesn't look like you have a stable version up for download. You think you could hook me up with a link? Thanks man!
Is there a mod that allows me disable the Installer from automatically coming up when connecting to a pc through USB?
Tyetiger said:
Is there a mod that allows me disable the Installer from automatically coming up when connecting to a pc through USB?
Click to expand...
Click to collapse
I was able to by deleting autostart.iso file from \system\etc
I use Mac and it no longer mounts the mobile Verizon app. I assume its the same for windows.
Itsmyphoneyo said:
I was able to by deleting autostart.iso file from \system\etc
I use Mac and it no longer mounts the mobile Verizon app. I assume its the same for windows.
Click to expand...
Click to collapse
Ive been trying for days! Haven't been able to find that folder or file. Unfortunately I have a PC
Tyetiger said:
Ive been trying for days! Haven't been able to find that folder or file. Unfortunately I have a PC
Click to expand...
Click to collapse
You need root to do this... I probly should have mentioned that. Sorry. Getting root is easy now, there are a could threads on how to root with very easy step by step instructions. After you gain root, purchase root explorer from PlayStore (yes, you have to spend a couple $ but its worth it) and use that app to navigate and delete the file. You will likely use the app again, unless you switch to an iPhone. So it's worth the little bit of money.
I see autorun.iso, I assume that's what you're referring?
Sent from my SCH-I545 using xda app-developers app
Itsmyphoneyo said:
You need root to do this... I probly should have mentioned that. Sorry. Getting root is easy now, there are a could threads on how to root with very easy step by step instructions. After you gain root, purchase root explorer from PlayStore (yes, you have to spend a couple $ but its worth it) and use that app to navigate and delete the file. You will likely use the app again, unless you switch to an iPhone. So it's worth the little bit of money.
Click to expand...
Click to collapse
Ok. I was able to download a root explorer and remove the autorun.iso. But I notice the phone still says "Installer is connected" and I still can't view the sdcard or drive on the phone unless I'm in Camara(PTP) mode.
Tyetiger said:
Ok. I was able to download a root explorer and remove the autorun.iso. But I notice the phone still says "Installer is connected" and I still can't view the sdcard or drive on the phone unless I'm in Camara(PTP) mode.
Click to expand...
Click to collapse
Check your usb debugging settings. you might need to either check that box or unchecked it. I can't help much more than that if you're using Windows, I'm a mac user. But that sounds like all you would need to do. Hope it helps.
Verizon installer
Okay here is a weird one (or maybe not). Started getting this when I first connected the S4 to PC via USB. Now when I connect my S3 I am getting the same popup. S3 is rooted never had this message.
I am thinking this is somehow embedded into the new Samsung USB drivers. When the phone is plugged in, some form of check reveals a VZW phone which triggers the installer????
Did anyone figure this out? I was able to stop the Verizon Installer Pop up by renaming the autorun.iso, but there is still a 30 second delay before I get access the the phones internal and external memory.
Gam3r 4 Life said:
Did anyone figure this out? I was able to stop the Verizon Installer Pop up by renaming the autorun.iso, but there is still a 30 second delay before I get access the the phones internal and external memory.
Click to expand...
Click to collapse
Bump, I'd like to know the same thing.
ecen92 said:
Bump, I'd like to know the same thing.
Click to expand...
Click to collapse
I'm getting connect/disconnect every 3 seconds.
Gam3r 4 Life said:
Did anyone figure this out? I was able to stop the Verizon Installer Pop up by renaming the autorun.iso, but there is still a 30 second delay before I get access the the phones internal and external memory.
Click to expand...
Click to collapse
Still trying to figure this one out........any ideas......anyone????
Zelmo88 said:
Still trying to figure this one out........any ideas......anyone????
Click to expand...
Click to collapse
Bump! Anyone find a cure for this yet?
I think I figured it out. I'm still on original MDK build. I don't know if that changes anything.
1. autorun.iso removed (may not be necessary, but mine is gone)
2. enable hidden menus (step 2) http://forum.xda-developers.com/showthread.php?t=2303905
3. enter dialer code *#0808#
4. select MTP+ADB
5. reboot (may not be necessary)
My phone originally had nothing selected. I don't know how to go back to that unselected mode. I can't guarantee anything. It's working for me. My phone now connects in MTP mode within a second or two of connection (unless the phone is in the middle of a reboot, then that has to complete first.)
Chris000001 said:
I think I figured it out. I'm still on original MDK build. I don't know if that changes anything.
1. autorun.iso removed (may not be necessary, but mine is gone)
2. enable hidden menus (step 2) http://forum.xda-developers.com/showthread.php?t=2303905
3. enter dialer code *#0808#
4. select MTP+ADB
5. reboot (may not be necessary)
My phone originally had nothing selected. I don't know how to go back to that unselected mode. I can't guarantee anything. It's working for me. My phone now connects in MTP mode within a second or two of connection (unless the phone is in the middle of a reboot, then that has to complete first.)
Click to expand...
Click to collapse
Tried this on Sophisticated 2.5 . It's a 4.3 rom I get this: error: device offlineerror: device offline even though Link Status is Device Connected. My autorun.iso file was in /system/etc I renamed it. Changing the dialer code *#0808# to MTP works until I reboot. Same thing with dialer code *#7284#. I edited a file in /efs/carrier/HiddenMenu "OFF" changed to "ON" all in capital letters This survives a reboot.
But MTP doesn't
desertopal said:
Tried this on Sophisticated 2.5 . It's a 4.3 rom I get this: error: device offlineerror: device offline even though Link Status is Device Connected. My autorun.iso file was in /system/etc I renamed it. Changing the dialer code *#0808# to MTP works until I reboot. Same thing with dialer code *#7284#. I edited a file in /efs/carrier/HiddenMenu "OFF" changed to "ON" all in capital letters This survives a reboot.
But MTP doesn't
Click to expand...
Click to collapse
I'm on MK2 rooted and I have the same problem with the setting not surviving a reboot. Anyone have any other ideas?
Removing the file should work, if it's giving you a delay then my guess is either your computer or the device is trying to find the file. Back on my s3 and dna rom I had only removed the file and vzw installer didn't show up
Sent from my SCH-I545 using XDA Premium 4 mobile app
CovXX said:
Removing the file should work, if it's giving you a delay then my guess is either your computer or the device is trying to find the file. Back on my s3 and dna rom I had only removed the file and vzw installer didn't show up
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Removing the file does not solve the problem, it still connects as installer for a while before connecting as media device. It's not a huge problem, just annoying! I'm curious if everyone has this problem, or if it's just a few of us??
Zelmo88 said:
Removing the file does not solve the problem, it still connects as installer for a while before connecting as media device. It's not a huge problem, just annoying! I'm curious if everyone has this problem, or if it's just a few of us??
Click to expand...
Click to collapse
I have the same issue. I've tried looking through/changing settings in build.prop, default.prop and init.usb.rc with no luck. I need to do a little more searching to better understand init.usb.rc as a lot of the settings are jibberish to me.
Chris000001 said:
I think I figured it out. I'm still on original MDK build. I don't know if that changes anything.
1. autorun.iso removed (may not be necessary, but mine is gone)
2. enable hidden menus (step 2) http://forum.xda-developers.com/showthread.php?t=2303905
3. enter dialer code *#0808#
4. select MTP+ADB
5. reboot (may not be necessary)
My phone originally had nothing selected. I don't know how to go back to that unselected mode. I can't guarantee anything. It's working for me. My phone now connects in MTP mode within a second or two of connection (unless the phone is in the middle of a reboot, then that has to complete first.)
Click to expand...
Click to collapse
Running the Casual-gnote2 I get this: file/ Open Casual Script (go to location, click on the downloaded Casual-gnote2.jar) it opens and gives me this
Description for /home/wade/Downloads/CASUAL-GNOTE2-Hidden Menus.jar
File Not Found Error: /home/wade/Downloads/CASUAL-GNOTE2-Hidden Menus.jar.txt
Delete this debug line in MenuItemOpenScriptActionPerformed()
If I just open Casual-gnote2 and click DO IT I get this: error: device offlineerror: device offline
In both cases the Link Status = Device Connected
Hello,
I have a Dell Venue 8 that is not able to save/remember wifi passwords after a device reboot. I've tried looking into the built.prop file for ro.securestorage.support=true and this line does not exist in that file. I've also read about google backups being potentially the cause, and I've disabled this but the issue remains.
Turning off/on wifi, the wifi is able to immediately reconnect. But the only problem is when the device itself reboots. I've tried looking all over for some sort of "Save" feature when connecting to the wifi network. It does not appear anywhere.
Has anyone else experienced this? Any help is appreciated.
Bump. Can anyone help?
Do you have root? If so, you could see if the networks are being stored in the file:
/data/misc/wifi/wpa_supplicant.conf
If they are, there's no reason they should disappear, I would think, unless as you mentioned, some Google backup process is overwriting it.
xBIGREDDx said:
Do you have root? If so, you could see if the networks are being stored in the file:
/data/misc/wifi/wpa_supplicant.conf
If they are, there's no reason they should disappear, I would think, unless as you mentioned, some Google backup process is overwriting it.
Click to expand...
Click to collapse
No, I do not have root. I am not able to find this file when connecting the tablet via usb to my computer either.
I recommend rooting your device, it took me maybe 10 minutes at most. Backup your data just in case! I didn't loose any files when I rooted, I followed this guide. After you root, download a file explorer and go to /data/misc/wifi and backup then delete wpa_supplicant.conf and do the same with the dhcp folder in /data/misc. I was having the same issues until I did that.
I know this is an old thread, but I just want to let you know my Venue 8 had the same problem and I was able to resolve it by doing a factory reset in the built-in recovery mode.
after I came across many amendments on my phone (j7p)
twrp ,root, xsposed, Nonencrypt kernel,deleting systemapps.....
i found that my phone doesnot remeber my wifi paswword /ssid
after each reboot , also after disconnect & connect to wifi ....
I could not determine the cause of the problem.
I restored my efs via twrp, but the problem still present
so i came to a temporary solution, and i posted here in order to be helpfull to others
or if someone have a better solution... so he can guid us
first off all backup your efs and keep it in safe place
now open your phone buildprop it is in your root/system ( you should have root access,afaik) via (buildprop edditor or totalcommander..or other
then scroll down to that string
ro.securestorage.support=true
change the value into false
ro.securestorage.support=false
save it and enter your wifi info...again
try to reboot your phone.. if the problem Disappeared, then it is secure storage issue
here i donot have a specific solution ,since i use a moded kernel
but maybe you can get ride of it by deleting ss-data in efs folder (via total-commander .apk or es file explorer.apk ...)
this file contains decryption of your wifi passwords..., and other
the problem will disappear untill you flash new thing from recovery
here you can take another backup of your efs beside the original one, and give it ashot from recovery after you make Major modification
at last I hope some of Veteran members give us better idea
Thanks a lot. By the way, can you use your front flash with the modded kernel?
It's not working for me.
I don't use it but i want to know if it's an issue with the kernel or i messed up a step somewhere.
Zhiro90 said:
Thanks a lot. By the way, can you use your front flash with the modded kernel?
It's not working for me.
I don't use it but i want to know if it's an issue with the kernel or i messed up a step somewhere.
Click to expand...
Click to collapse
sorry for my late reply
j7P doesn't have separate front flash (led) ....afaik
the screen only turn into white when you are using front flash cam
as for me I updated my J7p firmware ...so I am using stock kernel at now
BTW there is no need to modded kernel if U use USBotg pendrive
in clear steps from stock firmware u install twrp via odin
then U can root your phone , put supersu *zip in USBotg pendrive
attach it to your phone, mount this USB in twrp then flash any *zip file... such as SuperSU,,, and then you can install xposed ....
so there is no need to modded kernel , unless you need to get backups for your phone
Regards
Bootup password
I cant change ro.securestorage.support value to false... triggers bootup password then it rejects all password, cant get through... I then have to restore my build.prop and give up
nazgul67 said:
I cant change ro.securestorage.support value to true... triggers bootup password then it rejects all password, cant get through... I then have to restore my build.prop and give up
Click to expand...
Click to collapse
you should set it to false
not true
My bad, i mean setting it false. Then some bootup password is required.
nazgul67 said:
My bad, i mean setting it false. Then some bootup password is required.
Click to expand...
Click to collapse
NM
since the problem still presnet , so i think it is not secure storage issue
any how there is a new domed kernel without this issue (remembering wifi password)
give it a shot
https://forum.xda-developers.com/ga...el-theflash-kernel-v1-0-t3616374#post72618392
Regards
xcorona said:
NM
since the problem still presnet , so i think it is not secure storage issue
any how there is a new domed kernel without this issue (remembering wifi password)
give it a shot
https://forum.xda-developers.com/ga...el-theflash-kernel-v1-0-t3616374#post72618392
Regards
Click to expand...
Click to collapse
Im using default ROM and Kernel. I can see wifi passwords now. One of my apps is setting my selinux to permissive I dont know which is it. Maybe its because of my root, im just thankful for it ?