Related
Update March 25, 2013:
Solved!! The folks over at Thinktube Inc. have developed a fix and submitted it to CyanogenMod and AOSP for merging into their code:
http://b-real.org/2013/ad-hoc-ibss-m...h-cyanogenmod/
http://www.thinktube.com/android-tech/46-android-wifi-ibss
Essentially the EASIEST solution is to ROOT your phone, and install the CyanogenMod nightly as of March 25 or later (note: you will have to wait until the nightly is actually BUILT, since as of today it is not ready yet).
I have not tested this solution out myself, however others within this thread have confirmed it working.
Please if anyone develops a easier patch or a step-by-step for people who do NOT want to use CyanogenMod, post and I will update the OP
Cheers!
WiKiD24
-------------------------------------------------------
Update Oct 9, 2012:
- Nexus 7 v4.1.2 did not add Wi-Fi Ad-Hoc Support with the stock update from Google.
To do: Check if any WPA-Supplicant changes previously tested in v4.1.1 now work in 4.1.2
- Workaround (Recommended): Bluetooth Tethering to Nexus 7 Tablet (via Bluetooth DUN Profile). "BlueVPN" from Google Play Store.
Tested successfully on many Nokia Symbian phones (N7, E71, E72), and others.
However, many applications on Nexus 7 Tablet do not support it (without fixes from the developers)
Confirmed working applications:
- Pulse
- Google Chrome
- Dolphin Browser
- Facebook
- Ebuddy
- Youtube
- Others (I am too lazy to add them all)
Confirmed NOT working applications:
- Gmail
- Email
- Google Search
- Google Play Store
- Dropbox
- Words with Friends
- Scramble with Friends
- Others (I am too lazy to add them all)
More details can be found here: http://forum.xda-developers.com/showpost.php?p=29763582&postcount=27
Issue: Sometimes the phone/tablet do not connect (randomly), due to issues with either the phone or the tablet.
To resolve: Turn on and off bluetooth on phone, Turn on & off bluetooth on tablet. Try again. If does not work, reboot phone and tablet and try again. Should work.
-Workaround: Android Phone to Nexus 7 Tablet (via "FoxFI" App on Phone, "FoxFi Addon" App on Tablet, or via "PDANet", or via "Wireless Tether App")
http://forum.xda-developers.com/showpost.php?p=29763582&postcount=27
- Workaround: USB Tethering ANY Phone to Nexus 7 Tablet (via "PPP Widget" App on Tablet, requires rooted Nexus 7)
http://forum.xda-developers.com/showpost.php?p=32431103&postcount=51
- Workaround: Windows WiFi Laptop Tethering to Nexus 7 Tablet
http://www.youtube.com/watch?v=klHzMyYFGeQ
-------------------------------------------------------
Hi All,
I've just recently gotten a Nexus 7 and need to be able to enable Ad-Hoc wifi on the tablet.
I also own a Asus TF101 and previously had the same problem however there was a fix for that.
The solution was to replace the wpa_supplicant file in the /system/bin folder, however I do not know the code to change it.
If anyone has the technical know-how, they would be able to reverse-engineer it and apply the same fix.
http://forum.xda-developers.com/showthread.php?t=1370955
http://szym.net/2010/12/adhoc-wifi-in-android/
http://www.slatedroid.com/topic/2752...less-hotspots/
http://www.olsr.org/?q=olsr_on_android
http://hostap.epitest.fi/gitweb/gitw...upplicant.conf
I posted a possible solution in QnA section. Thread title is similar to this one. Check it out. Doesn't involve any coding. Prime had a similar issue on a few firmware updates. This was solved for us(before Asus came around to enabling it themselves) by adding in a wifi supplicant file and renaming an older one. Then setting permissions on the new file. Here is the link to that thread. There's a good chance it will work without the file needing to be modded. It came from a galaxy tab LR something and worked fine on prime. Its worth checking out.
http://forum.xda-developers.com/showthread.php?t=1438297
thanks for the tip and I tried it out, which is essentially the same type of solution but it didn't think work as there is no wpa_supplicant2 file in the nexus 7.
http://forum.xda-developers.com/showthread.php?t=1777413
here's some more useful information for enabling ad hoc:
http://szym.net/2010/12/adhoc-wifi-in-android/
http://www.slatedroid.com/topic/27522-howto-connect-to-ad-hoc-wireless-hotspots/
http://www.olsr.org/?q=olsr_on_android
http://hostap.epitest.fi/gitweb/git...ob_plain;f=wpa_supplicant/wpa_supplicant.conf
I'm doing what I can right now to try and enable it.
Some more experienced android users whom know what they're doing would be better than me trying it out, though!!
Did any of those sources of information get you any closer to enabling ad-hoc?
Just FYI that Nexus S "ad hoc enabling file" doesn't work on NS with Jelly Bean.
nexususer0101 said:
Did any of those sources of information get you any closer to enabling ad-hoc?
Click to expand...
Click to collapse
None yet, I need some help to do so. There is a file called "wpa_cli" that I need copied from another device, because I can't find it on the internet.
If anyone could find it in their "/system/bin" folder and attach it to this tread, I could certainly try it.
I've also requested the same thing in the Q&A forum here: http://forum.xda-developers.com/showthread.php?t=1793437
Bumping; I have the same condition. I'm in Italy and bought an internet package for my laptop--I'm sharing it with all my other devices but the N7 doesn't see the adhoc connection. Like OP said, I had a Transformer TF101 and remember flashing a file to fix it.
Thanks in advance.
Just an FYI: Also checked my GNex for a wpa_cli and came up empty.
Just wanted to give quick update, i have not been able to find anyone to help me and also my life is kinda hectic right now... Hopefully someone will be able to pick up where I left off, in the meantime my nexus 7 is pretty much useless to me until resolved.
One more "me too".
I'm here to share my sympathy to everyone else's pain as I have a nexus 7 that I can't connect to my phone's adhoc Hotspot. I have also posted my query in Android Central, but no one seems to have been able to know a fix as of yet. (topic can be found here: Android Forums at AndroidCentral.com > Google Nexus 7 Tablet Forum > Nexus 7 Rooting ROM's & Hack's > *** CONNECTING TO Adhoc WiFi WITH THE NEXUS 7 ***)
As I said in that thread.. not being able to connect to phones hotspot makes my beautiful nexus 7 feel like a handicapped tablet.
wikid24 said:
Just wanted to give quick update, i have not been able to find anyone to help me and also my life is kinda hectic right now... Hopefully someone will be able to pick up where I left off, in the meantime my nexus 7 is pretty much useless to me until resolved.
Click to expand...
Click to collapse
I haven't seen any reports/posts of people checking out or trying what I mentioned in post #2..lol. on prime we had this exact same problem. Then we found the supplicant file to replace one we had and then adhoc tethering worked after that. You only need to be rooted to do this as you need to rename a file and insert new supplicant in there and set permissions. You can always backup and rename original file. So if it doesn't work, you can easily revert back to stock file. I have a feeling this new file will work. Just haven't tried myself yet as I haven't brought tablet outdoors yet to need tethering. I might eventually see if it works if no one else does.
Look at the thread I linked in second post and you will see prime owners had exact same problem and we solved it. It worked for the transformer 300 also. Will likely work for nexus 7 also. The file is, in a sense, universal.
demandarin said:
I haven't seen any reports/posts of people checking out or trying what I mentioned in post #2..lol. .
Click to expand...
Click to collapse
I have tried. It does not work -- WiFi refuses to turn back on with this new supplicant file. And yes, I made sure to follow your instructions exactly as described in the procedure.
With the N7, there is no such thing as a wpa_supplicant2 file originally in /system/bin (only the one without the '2' exists in the N7 which is the one running the show here, I know this for a fact as when restoring this file, the WiFi in the N7 becomes functional again). So I tried this same file you provide both with and without the '2', with no better results.
I suspect that only a developer that knows what he's doing would be able to come up with a new wpa_supplicant file specifically tweaked for the N7 (as opposed to using one that did the trick for the Prime or for the Xoom or whathaveyou).
Thanks for the suggested idea though... anything else you think we should try?
rdelfin said:
I have tried. It does not work -- WiFi refuses to turn back on with this new supplicant file. And yes, I made sure to follow your instructions exactly as described in the procedure.
With the N7, there is no such thing as a wpa_supplicant2 file originally in /system/bin (only the one without the '2' exists in the N7 which is the one running the show here, I know this for a fact as when restoring this file, the WiFi in the N7 becomes functional again). So I tried this same file you provide both with and without the '2', with no better results.
I suspect that only a developer that knows what he's doing would be able to come up with a new wpa_supplicant file specifically tweaked for the N7 (as opposed to using one that did the trick for the Prime or for the Xoom or whathaveyou).
Thanks for the suggested idea though... anything else you think we should try?
Click to expand...
Click to collapse
They likely will implement it through a future update. Hopefully that's sooner than later. Ill ask motley, kernel developer.
I toyed with this for a while...
If you install Power Controls (Power Controls) you can add a button that turns on the Wifi Hotspot.
Problems:
you cant change any settings in current settings UI
Appears to be default "Android_AP" SSID and whatever the default password is (i dont recall if this is a random code or not)
Its a start!
Demented-Idiot said:
I toyed with this for a while...
If you install Power Controls you can add a button that turns on the Wifi Hotspot.
Problems:
you cant change any settings in current settings UI
Appears to be default "Android_AP" SSID and whatever the default password is (i dont recall if this is a random code or not)
Its a start!
Click to expand...
Click to collapse
Could you explain exactly what this does? I didn't understand what it is being implied with this being a start? with this you can actually connect to adhoc?
idk if anyone has looked...but has anyone looked into editing the Wifi-Direct api to make adhoc networks visible in there? Since wifi-direct is made for p2p connections. it's android.net.wifi.p2p.WifiP2pManager info about it is here http://developer.android.com/guide/topics/connectivity/wifip2p.html like I said...don't know if it's much help
I also wanted to post a quick reply, since I've been an insomniac yesterday.
From my previous posts I posted this link here as well, I edited the wpa_supplicant.conf file from the /system/etc/wifi folder and modified with the following settings, however I don't think that it even reads the wpa_supplicant.conf file either. Can anyone either confirm or deny that the wpa_supplicant.conf file is being used on the N7??
-------------------
update_config=1
ctrl_interface=wlan0
eapol_version=1
ap_scan=2
fast_reauth=1
network={
ssid="Bondphone"
mode=1
frequency=2412
key_mgmt=NONE
wep_key0="1234567890123"
wep_key1=1234567890123
wep_tx_keyidx=1
priority=3
auth_alg=SHARED
}
------------------------
wikid24: I don't know if N7 (or my NS) reads this file but it definitely reads /data/misc/wifi/wpa_supplicant.conf. Only problem is that I can't turn wifi on after ANY change in this file. Sometimes even if I revert my backup file, wifi won't launch and I must delete it to make wifi working again.
I found this thread on XDA
http://forum.xda-developers.com/showthread.php?t=1806937
It is edited wpa_supplicant file for Asus Transformer but it allows me to turn on wifi even on NS. But it doesn't show me any ad hoc networks. Maybe with non-stock kernel...?
And I also found ad hoc patch for source code of older version of wpa_supplicant. But I'm not able to try if it is possible to apply it on JB version too.
http://szym.net/android/wpa_supplicant-ibss.patch
jenda.69 said:
wikid24: I don't know if N7 (or my NS) reads this file but it definitely reads /data/misc/wifi/wpa_supplicant.conf. Only problem is that I can't turn wifi on after ANY change in this file. Sometimes even if I revert my backup file, wifi won't launch and I must delete it to make wifi working again.
I found this thread on XDA
http://forum.xda-developers.com/showthread.php?t=1806937
It is edited wpa_supplicant file for Asus Transformer but it allows me to turn on wifi even on NS. But it doesn't show me any ad hoc networks. Maybe with non-stock kernel...?
And I also found ad hoc patch for source code of older version of wpa_supplicant. But I'm not able to try if it is possible to apply it on JB version too.
http://szym.net/android/wpa_supplicant-ibss.patch
Click to expand...
Click to collapse
jenda, I think you may have solved a big piece to the puzzle!!
You can copy the file to another directory, and THAN you can open the file! I noticed I had all my pre-saved wifi addresses in this file!
If someone can please copy the "/data/misc/wifi/wpa_supplicant.conf" file to another directory, modify it, than overwrite the old file, it should work!! *fingers crossed*
(unfortunately I am busy for a few days, don't know if I'll be able to make the change for a while)
Ever since a software update a few days ago, the web browsers on my Nook HD have been unable to access local HTML files. All URLs of the form <file:///...> or <file://localhost/...> get an error message "Access to the file was denied". It suggests that the file may have been removed or moved, or the file permissions may be getting in the way. None of these is true; I have no trouble accessing these files from other programs (such as adb shell) and the files are world-readable. In fact, the same thing happens even when I try to browse the root directory with <file:///>, which is ridiculous. This happens with both the Chrome and Opera browsers.
Does anybody have any idea of what's going on or how to fix it?
Hello everyone,
I've had a Nexus 6 for about a month now and I'm running into this same problem, whether it be an email link or a link on Twitter:
I keep getting a "This webpage is not available... ERR_CONNECTION_REFUSED" page upon clicking various links.
This seems to be happening more and more lately. I know the odds of every single one of these links being down or broken are slim to none.
At first I thought it could be my AdAware software wreaking havoc on the link itself, and thus shutting me down from viewing it. But after uninstalling the AdAware, I'm still getting these down webpages. So that rules out the AdAware aspect.
I seem to get these A LOT on Twitter. Someone will post a link, whether it be a website, video, picture, etc..... and I click the link and I get this same message.
I should also mention I bought my Mom a 64GB unlocked Nexus 6 from Amazon (same place where I got mine), I unlocked it, rooted it and we're both running stock 5.0.1 for the time being, until I throw 5.1 stock on ours for the voice and data simultaneous capabilities.
Any help with this matter would be appreciated, as I'm at my witts end regarding why these damn links keep saying unavailable.
I should mention, the latest link was from a job site called ziprecruiter.com, care of monster.com job postings. She tried to open one of the job links in her GMail and it gives her the screenshot I posted. I tried every job link and the same result. However, when I open the job links via a web browser on my MacBook, each link works perfectly. I also included the details screenshot of the webpage.
Thanks everyone!
Anyone?
It's your modified hosts file. Reinstall adaware and use the restore hosts file option. If you want to keep using adaware, you can also add the sites being blocked to your white lists in adaware so that it will not add them to your hosts file. It's blocking referral and redirecting links most likely.
mwalt2 said:
It's your modified hosts file. Reinstall adaware and use the restore hosts file option. If you want to keep using adaware, you can also add the sites being blocked to your white lists in adaware so that it will not add them to your hosts file. It's blocking referral and redirecting links most likely.
Click to expand...
Click to collapse
Thanks so much, I'll try this out
try adfree instead http://adfree.bigtincan.com/adfree.apk
mwalt2 said:
It's your modified hosts file. Reinstall adaware and use the restore hosts file option. If you want to keep using adaware, you can also add the sites being blocked to your white lists in adaware so that it will not add them to your hosts file. It's blocking referral and redirecting links most likely.
Click to expand...
Click to collapse
I tried doing what you said, but was unable to get it to work.
Any tips on this?
I'm still getting this same error page on my Nexus 6, as well as my Mom.
I can't for the life of me figure out how to get this to go away.
Her problem is with random emails from websites she shops at, such as fanatics.com
She'll open the email on her phone, click one of the sales items and that damn page shows up every time. I uninstalled Ad Away and rebooted, and it's still having the same problem.
If you or anyone else could PLEASE help me out with this, I'd appreciate it.
Thanks-
MVLJR said:
I tried doing what you said, but was unable to get it to work.
Any tips on this?
I'm still getting this same error page on my Nexus 6, as well as my Mom.
I can't for the life of me figure out how to get this to go away.
Her problem is with random emails from websites she shops at, such as fanatics.com
She'll open the email on her phone, click one of the sales items and that damn page shows up every time. I uninstalled Ad Away and rebooted, and it's still having the same problem.
If you or anyone else could PLEASE help me out with this, I'd appreciate it.
Thanks-
Click to expand...
Click to collapse
Have you tried clearing the browsers cache in /settings/apps/ or clearing the cache in recovery, that may help. No problem for me to open this site, btw stock not rooted.
mwalt2 said:
It's your modified hosts file. Reinstall adaware and use the restore hosts file option. If you want to keep using adaware, you can also add the sites being blocked to your white lists in adaware so that it will not add them to your hosts file. It's blocking referral and redirecting links most likely.
Click to expand...
Click to collapse
gee2012 said:
Have you tried clearing the browsers cache in /settings/apps/ or clearing the cache in recovery, that may help. No problem for me to open this site, btw stock not rooted.
Click to expand...
Click to collapse
Thanks for the reply.
I FINALLY figured it out.
Had to reset the hosts file via the app and then reboot immediately. For some reason I didn't reboot before and the host files didn't go back to stock.
Even if you uninstall Ad Aware, the host files remain unchanged and thus the problem persists.
I reverted back to stock host files for now and the links are working.
I have to learn how to add sites to the whitelist in order to attain full functionality of Ad Aware.
That is very common with Twitter and the ad blocker as mentioned. I get it every time. But it is some safety feature seeing the modified hosts file. For me it isn't that it is blocked...just hitting refresh fixes it, every time for me.
TonikJDK said:
That is very common with Twitter and the ad blocker as mentioned. I get it every time. But it is some safety feature seeing the modified hosts file. For me it isn't that it is blocked...just hitting refresh fixes it, every time for me.
Click to expand...
Click to collapse
Are you talking about refreshing via the Ad Away app itself, or the twitter link itself?
I can't get certain Twitter links to work, unless I shut off my Ad Away and go back to default host files.
Adaway rocks. Have never had a problem.
MVLJR said:
Are you talking about refreshing via the Ad Away app itself, or the twitter link itself?
I can't get certain Twitter links to work, unless I shut off my Ad Away and go back to default host files.
Click to expand...
Click to collapse
I use Tweetcaster, which launches 'Readability' for its external links....It's a scaled down browser that ripps out ads and pics. I hit refresh in it and its good....or I can hit Readability's menu and open in browser and its good.
So that tells me Ad Away is blocking the original Twitter URL, then Readability refreshes using the real target URL. I will dig into this, should be any easy whitelist ro add.
TonikJDK said:
I use Tweetcaster, which launches 'Readability' for its external links....It's a scaled down browser that ripps out ads and pics. I hit refresh in it and its good....or I can hit Readability's menu and open in browser and its good.
So that tells me Ad Away is blocking the original Twitter URL, then Readability refreshes using the real target URL. I will dig into this, should be any easy whitelist ro add.
Click to expand...
Click to collapse
Thanks for the info.
Maybe I'll give Tweetcaster another try, it just wasn't as easy on the eyes for me vs regular Twitter app.
If I could only figure out this whitelist thing, I could put this all behind me.
I have my original host files in tact right now and and everything is working, but I'm not blocking ads.
Hey everyone I'm rooted and everything so I've been trying to find a way to get around paying $30 for a hot spot that should come with the phone. anyways I found a way to disable the "you are not subscribed to hot spot" thing but when I connect anything to the hot spot I keep getting errors saying the DNS couldn't resolve server names. I tried for hours with different DNS servers so I'm guessing it's something vm has done. If anyone could help me with this I would greatly appreciate it I used it a lot before I got this phone and now I'm kinda stuck :/
I know from experience that you can usb tether with pdanet and it'll hide your tethering with metro. It will not however hide hotspot HOW EVER you can use its experimental feature internet sharing which is essence creates a hotspot however I've only ever been able to connect to a phone that was with metro AND the phone that was hotspotting was not with metro. Trying to do so with my metro phone give me dns errors as well.
I haven't tried to use USB tethering yet only because some of my things can't be tethered via USB. I just don't see why I'd be getting DNS errors now and never did before. Oh wel. Surely someone here will have a solution for me soon.
schuylar156 said:
I haven't tried to use USB tethering yet only because some of my things can't be tethered via USB. I just don't see why I'd be getting DNS errors now and never did before. Oh wel. Surely someone here will have a solution for me soon.
Click to expand...
Click to collapse
I don't know if you are rooted, but I'm using Wifi Tether Router (just google an apk file) instead of trying for the native hotspot function.
javierrr13 said:
I don't know if you are rooted, but I'm using Wifi Tether Router (just google an apk file) instead of trying for the native hotspot function.
Click to expand...
Click to collapse
Are you sure? I tried this app before and it wouldn't broadcast the network. And yes I am rooted. I found a way to partially get the native hotspot working but it's a pain in the butt. If I could figure out how to edit the apn settings I'd have it going in 5 seconds but they're locked and htc phones don't have a "hidden menu" like lg phones.
Weird... Well, If you can't get that working, I'll let you know my current configurations for that app.
keep up the good work guys.
I'm looking for a solution for the hotspot on my 626 from Verizon.
native mobile hotspot and tether on cricket
I was able to use the phone as a wifi hotspot by doing the following:
1) install the following apps: MK explorer, Axel (xml editor)
2) phone must be rooted
3) using MK explorer navigate to the following folder (root directory): /system/customize/ACC
4) make a copy of the default.xml file and rename it in case it gets corrupted
5) run Axel and open the default.xml file for editing
6) scroll down about 80% from the top of the file to find the entry (find didn't work for me):
<app
name="Tethering_provision">
^ <item
type="integer"
name="TetheringGuard_Rule">
. 3 (note:dot is in middle)
7) edit the entry to change the 3 to 0
8) use "save as" and save modified file
9) rename the edited file to default.xml
10) reboot
11) go to settings->more->mobile hotspot and tethering, click on Mobile Hotspot, click on OK, change the hotspot name and password to what you want
12) after this step the phone just sat there so I rebooted
13) hotspot now works
I have no idea if this is hidden from the carrier
Hello. I happen to experience something similar to this one here:
"I found any video encoded with ffmpeg color levels filtering crashes my phone! Does this happen to you, too?
It happened both pre- and post-upgrade. (Both versions are 5.1, "stock-ish".) Just put the file in /sdcard and try to view it. Immediate crash for me, every time. Give it a try! It's a small file. This seems like a serious Android bug, but it could just be that something's wrong with my phone. (I had to attach it as a .zip, but the file should be unzipped when you test it.)
Edit: I found out it's a bug in HTC's video drivers. I can't find the link, but someone else here on XDA actually patched the kernel for his m7, but I don't know whether he submitted a bug, and I assume HTC isn't going to fix this unless someone exploits it to gain root or install malware."
Anyone familiar with this? Thanks