Please HELP!!!!
After hours of searching I'm seeing people mentioning the same problem with wireless tether as I have however they are mentioning it in their custom ROM thread thinking its only specific tho their ROM but it seems to be a universal issue. I understand there are still many with it working great, so let's not try to turn this into a "mines working great" thread and instead diagnose why it's working for some and not others.
Problem: Computers cannot connect, transfer freezes at 0.4kb. This is the same exact problem everyone is having (those who have problems) with Wireless Tether.
Things I've done to try to fix it:
1. Wiped Cache
2. Restored a Nandroid that was working great
3. Flashed the new kernal
4. Reinstalled AVA's Froyo Sense
5. uninstalled and reinstalled Wireless Tether
6. Tried the new beta version of wireless tether
Please help guys, this is vital to my business needs. I can live with the bugs in the ROM and things but this one I really need. You guys are great. Thanks.
Im having the same problem...bump?
I have the same problem..even madea thread nobody seems to help...
Things I have tried to fix
Rerun the simple rootwiped cache,dalvik cache ,flashed other roms..
Reran the simpleroot which downgraded me than rerooted to the toast method...
And flashed custom roms...nothing
Seems like its working but only get 4 kb down and 2 kb up ,
If I scan I don't see my wireless teether
Please help...
noscci said:
Im having the same problem...bump?
Click to expand...
Click to collapse
I found a possible fix.... i will try it tomorrow and let you guys know
Sent from my HTC Evo 4G using XDA App
Hopefully it works...will be waiting for update
Tyzing said:
Please HELP!!!!
After hours of searching I'm seeing people mentioning the same problem with wireless tether as I have however they are mentioning it in their custom ROM thread thinking its only specific tho their ROM but it seems to be a universal issue. I understand there are still many with it working great, so let's not try to turn this into a "mines working great" thread and instead diagnose why it's working for some and not others.
Problem: Computers cannot connect, transfer freezes at 0.4kb. This is the same exact problem everyone is having (those who have problems) with Wireless Tether.
Click to expand...
Click to collapse
What versions of wireless tether have you tried?
chocmatic said:
What versions of wireless tether have you tried?
Click to expand...
Click to collapse
The latest one from the market..and its not the app.....
Fix didnt work yet....I just grabbed my buddies phone at work and he has the same issue. Like I mentioned I've tried every Wireless Tether out there including the beta. Hopefully I will have a fix or someone helps soon b/c this isnt good for a lot of people!
I downloaded the 2.05 and 2.02 from market even beta same results 4kb up and 2 kb down.......I heard unrevoked 3 fixes the issue but want to stay fully rooted
Tyzing said:
Fix didnt work yet....I just grabbed my buddies phone at work and he has the same issue. Like I mentioned I've tried every Wireless Tether out there including the beta. Hopefully I will have a fix or someone helps soon b/c this isnt good for a lot of people!
Click to expand...
Click to collapse
Possible workaround
I am not sure if this is going to help but I took a trip this last weekend and thought I would give the tether a try. I think I was having the same problem you guys are seeing. The laptop would connect to the phone just fine but the internet would just simply not work.
After getting pretty pissed I opened the phones web browser while wireless tether was enabled and boom it started working on the laptop and continued to work for a couple of hours.
When I tried it again later the same thing happened I just needed to open the browser on the phone to get it working. Like the phone needed to be forced locally to make an internet connection.
Chris
I'm not sure what the exact prob you guys are having but maybe this could be of help....
The problem is that custom roms "intregrate" our app into their roms. They don't install it but copy it to /system/app or /data/app. By not installing it a shared library is not copied to the right location! It's not the fault of the app!!!
What you could do:
Remove the preinstalled app from /system/app or /data/app and install it manually!
Download: http://android-wifi-tether.googlecode.com/files/wireless_tether_2_0_5-pre2.apk
OR install mentioned shared-library manually:
1) Extract wireless_tether_2_0_5-pre2.apk (using winzip/winrar).
2) in "lib/armeabi" you will find a file named "libnativetask.so"
3) Copy this file to your device:
adb remount
adb push libnativetask.so /system/lib
Did anybody found a fix for this problem yet?
I hope you find a fix, all I can do is tell you what I do each and everytime I load a new ROM, or a new Wireless Tether APP.
I open the app, click tether... allow it to get superusers premissions.
Hit menu, access control, and ENABLE access control
Hit back, stop tethering, allow super users premissions
Close APP
Restart app, click tether and connect
I had your problem once, and this method with the newest version cured it. Hope you find your fix
I had this problem a few weeks ago. I was able to fix it, but i didn't document how i did it.
This is how I think i fixed it.
1. Use Titanium backup to wipe data, and then uninstall it.
2. Go into recovery mode and wipe cache partition.
3. Reboot
4. Then re-install wireless tether app (i installed the pre-9 from code.google.com/p/android-wifi-tether/downloads/list)
I have a feeling I'm forgetting a step, but I hope this works.
I've never been able to get the market version to work. Always thought it was "old" code.
http://code.google.com/p/android-wifi-tether/
I am posting this using wireless tether pre9, on fresh's 3.3 with kingx cfs11 kernel.
Oh to install it. First unistall what ever version you're trying. Then do a fresh install of the download.
ruffytdog said:
I had this problem a few weeks ago. I was able to fix it, but i didn't document how i did it.
This is how I think i fixed it.
1. Use Titanium backup to wipe data, and then uninstall it.
2. Go into recovery mode and wipe cache partition.
3. Reboot
4. Then re-install wireless tether app (i installed the pre-9 from code.google.com/p/android-wifi-tether/downloads/list)
I have a feeling I'm forgetting a step, but I hope this works.
Click to expand...
Click to collapse
I was able to fix by uninstalling and then reinstalling pre10. Just an FYI
At the time I had the problem, the uninstall and re-install method didn't work. I tried re-installing a few of the different "pre" versions. Then I finally tried the clear cache between one of my uninstall/reinstall, and then it finally worked. dunno why, but that was the issue i was having...
Related
ok here goes.......
I've updated to d107, im using noob's new rom, everything is fine EXCEPT I cant for the life of me get rid of the ****ing asphalt demo. I have root manager, root explorer, titanium, everything (licensed versions also if that even matters) and everytime I try to delete/remove and reboot that simple bastard is still there. I mount as r/w in two of the above mentioned programs and still nothing....is there something that im missing or something else that i should be doing? it just figures, I can re-install this that and the other rom,update,removed apps etc without any kind of problem ive seen mentioned on here, but when it comes to that demo (my now arch nemesis) I cant remove it!!! thanks for the help everybody.
specialk0324 said:
ok here goes.......
I've updated to d107, im using noob's new rom, everything is fine EXCEPT I cant for the life of me get rid of the ****ing asphalt demo. I have root manager, root explorer, titanium, everything (licensed versions also if that even matters) and everytime I try to delete/remove and reboot that simple bastard is still there. I mount as r/w in two of the above mentioned programs and still nothing....is there something that im missing or something else that i should be doing? it just figures, I can re-install this that and the other rom,update,removed apps etc without any kind of problem ive seen mentioned on here, but when it comes to that demo (my now arch nemesis) I cant remove it!!! thanks for the help everybody.
Click to expand...
Click to collapse
no need to mount....just use root manager and delete the apk and odex if it is present....cannot remember if it is......should be gone...I have removed it numerous times already...belive me it works...
ok thanks man, I'll give it another try...cant figure out for the life of me why this isnt working....I know that i'm surely missing something so simple.
on another note, flyers huh?.....kidding they had a hell of run last year. being from pittsbugh i love the penguins. hopefully we can win another one
i have no idea!!!
tried exactly what you said and its still there - went into titanium looked at properties of app - said only this: libasphault5.co
looked for it in corresponding folder and no luck.....I may have missed a step or uninstalled it incorrectly? still working on it
wow pretty stupid on my part - over complicating as usual.....all fixed - thanks again!
I was just going through the /system/app directory and found this rather interesting .apk in there, "TetheringManagerRogers1126.apk". Anyone have any idea what Rogers is doing with this? Do you think this is what is causing people with non-tethering enabled accounts (under 1 gig of data) to not be able to use the Mobile AP feature? Would removing it bypass the restriction? Hoping someone with more Android knowledge can shed some light on it.
tbrummell said:
I was just going through the /system/app directory and found this rather interesting .apk in there, "TetheringManagerRogers1126.apk". Anyone have any idea what Rogers is doing with this? Do you think this is what is causing people with non-tethering enabled accounts (under 1 gig of data) to not be able to use the Mobile AP feature? Would removing it bypass the restriction? Hoping someone with more Android knowledge can shed some light on it.
Click to expand...
Click to collapse
Does rooting not allow tethering in the Rogers 2.2?
Regarding your first reply, that has now disappeared:
"Root and tether to your hearts content."
I am rooted, how do you think I was looking through the /system/app directory structure.
Regarding your edited reply, rooting does not disable your ability to tether.
The point of my post was more towards the people that now cannot tether after upgrading to 2.2, there are numerous complaints about it. Mostly from Fido users by the looks of it. The option is disabled for them, if they try to enable Mobile AP it says something about contacting Rogers. I was thinking that possibly this file is the reason, and if they were to remove it, maybe they could enable Mobile AP again.
Tethering does not work for me, when it used on iOS. I never tried on Android 2.1, as I used mobile AP a few times instead. Maybe I just need to set it up again with Rogers since I just renewed my contact...
Mobile AP still works, but just one device at a time it seems? Not sure if thats a limitation or a problem. Now to get VPN to work...
tbrummell said:
Regarding your first reply, that has now disappeared:
"Root and tether to your hearts content."
I am rooted, how do you think I was looking through the /system/app directory structure.
Regarding your edited reply, rooting does not disable your ability to tether.
The point of my post was more towards the people that now cannot tether after upgrading to 2.2, there are numerous complaints about it. Mostly from Fido users by the looks of it. The option is disabled for them, if they try to enable Mobile AP it says something about contacting Rogers. I was thinking that possibly this file is the reason, and if they were to remove it, maybe they could enable Mobile AP again.
Click to expand...
Click to collapse
im on Fido using a Rogers captivate recently updated to froyo 2.2 and mobileAP does not work for me...did you find out of that apk is responsible?
edit: you are a genius tbrummell, that apk was stopping mobileAP from working. i just deleted it and now i can wireless tether. i was almost ready to flash a different rom to get mobileAP up and running...stupid rogers i win haha thanks tbrummell
neotekz said:
im on Fido using a Rogers captivate recently updated to froyo 2.2 and mobileAP does not work for me...did you find out of that apk is responsible?
edit: you are a genius tbrummell, that apk was stopping mobileAP from working. i just deleted it and now i can wireless tether. i was almost ready to flash a different rom to get mobileAP up and running...stupid rogers i win haha thanks tbrummell
Click to expand...
Click to collapse
Good to hear!
How do I delete the file??
I tried Astro Browser and I also tried FTP server, but it would let me delete it.
Thanks!
TOM...
MrLemon said:
How do I delete the file??
I tried Astro Browser and I also tried FTP server, but it would let me delete it.
Thanks!
TOM...
Click to expand...
Click to collapse
Are you rooted?
Yes I am rooted. Used SuperOneClick and I know it worked because Titanium Backup works fine.
TOM...
kegobeer said:
Are you rooted?
Click to expand...
Click to collapse
Ok I got it deleted. Used Terminal Emulator and followed the 'basic' app delete tutorial at this link...
jaxov.com/2010/09/how-to-remove-stock-default-android-apps-easily/
Now it works! Thanks!'
TOM...
Awsome find tbrummell and neotekz. Rogers Fail!
tbrummell said:
I was just going through the /system/app directory and found this rather interesting .apk in there, "TetheringManagerRogers1126.apk". Anyone have any idea what Rogers is doing with this? Do you think this is what is causing people with non-tethering enabled accounts (under 1 gig of data) to not be able to use the Mobile AP feature? Would removing it bypass the restriction? Hoping someone with more Android knowledge can shed some light on it.
Click to expand...
Click to collapse
Its a lame attempt at controlling tethering... just remove it and everything will work as usual.
att does the same thing.
thanks a lot for the trick. I was thinking of roll back to 2.1 to this back. you save me hours of time. great post~
nice find. you guys all use SuperOneClick 1.5.5 to root your phones?
Sent from my SAMSUNG-SGH-I896 using XDA App
weaktight said:
nice find. you guys all use SuperOneClick 1.5.5 to root your phones?
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
Yes.
The message you have entered is too short.
I just found this thread while trying to fix a problem of Mobile AP/USB tethering disconnecting me after about 5 minutes of use. The reason I mention this is that my account should have not have had any tethering restrictions as I'm on the 6gb data plan. Mobile AP worked fine under 2.1, but as mentioned, after about 5 minutes of use on 2.2, both Mobile AP, and tethering would just shut off. I was able to tether fine using Kies though. Removed this file, and now have been connected for over an hour on Mobile AP Thanks!
MrLemon said:
Yes I am rooted. Used SuperOneClick and I know it worked because Titanium Backup works fine.
TOM...
Click to expand...
Click to collapse
Lol just use TiBu to get rid of "Tethering Manager"in the apps list.
@OP: yes, it does what you thought. But you already found that out.
Alternatively,
1. Root your phone
2. Download "Root Explorer"
3. Rename or Delete the file
4. Reset your phone
Ymodem-G
Your alternate solution rocks
hi,
iam using cyanogenmod 7.2 Rc3 working well in my fit....but iam not able to connect to wifi ...please help me
acamogh said:
hi,
iam using cyanogenmod 7.2 Rc3 working well in my fit....but iam not able to connect to wifi ...please help me
Click to expand...
Click to collapse
I guess I'll chime in.
Although I don't have a Samsung or an RC3 I have run into this before on CM7.1 along with many other users.
(Of course, a Data\Cache wipe is always recommended, especially if problems occur after a new ROM install)
Here are my suggestions:
1) Grab the free app Fix-My-Wifi from market and run it. Reboot with it enabled at boot at least once. Toggle Airplane mode on/off before and after rebooting. If this fixes it, Great, you can uninstall the app. If it doesn't fix it, you can uninstall the app and try the next step.
2) Next you'll want to remove any saved/restored APs. You can 'Forget' them one at a time if you'd like, attempting to connect after each removal, but it may be necessary to remove them all. Make sure you attempt to connect from the 'Wireless and Network Settings' too, and not from some other toggle. Reboot and Connect.
3) If that fails, it's been reported that changing the router's password type to WEP only (if I'm remembering correctly) can fix this symptom in some cases, as well as improving the data speeds through the phone. I may have the password type wrong, so try all password types that can be set as 'only'.
If you still cant connect I would redo\retrace your install, ensuring to wipe data/cache and only restoring a minimal amount of DATA with any of your backed up apps. Also, you should avoid restoring any 'System' apps\data (they're the red ones in Titanium Backup).
That's all I've got for ya to try at this point.
If it's still not working, more detail on what you've attempted so far in your troubleshooting and how\when the phone developed the problem might help another XDA'er provide you with a solution.
how about battery back up with cm7.2 mate ??? i asked u question while u r asking ,,by the if u like to say
[Hopefully I didn't miss this being covered somewhere else, as I am much the same as many of you and get beyond irritated with endless repeat questions. I searched using the best keywords I could think of for the issue, but to no avail. Apologies in advance if this has been covered!]
Alrighty. I've got a TF101, rooted it myself (thank you XDA), running 8.6.5.1.9 i believe, stock rom just with root. Used nvflash and Razorclaw. Worked like a charm.
It's been fine for the last 6 months, no issues. However, I decided to update busybox using its internal updater as I have before with no problems. I noticed I accidentally told it to install to /system/bin instead of /system/xbin, and the only reason I even knew about that was due to having to configure an app to find busybox in /xbin instead of /bin.
Now there's a problem. I can still access the internal virtual sd card, but that's about it. The device can't seem to read or write to the main directory (although it can deal with going DIRECTLY to /mnt/sdcard). Ghost commander can't view the main directory, but ESFile explorer _can_, although root browsing in ESFile Explorer is UNchecked. It shouldn't be able to do what it's doing, and it's only doing it in one of two apps.
As a result, I've got no access to any root apps obviousy, but the wifi is having issues as well, it tries connecting but it can't complete the connection.
I'm toying with just wiping and flashing a new rom entirely, but figured I'd ask before I jump in the deep end of things. I keep backups of stuff, but it's still such a pain in the ass reinstalling things.
Any suggestions? I have a feeling it's something "simple", a link file or ... something which linux gurus would know about and I would not, not being a guru or disciple myself.
Thanks in advance!
If only you have working CWM installed. You could just flash this Superuser3.0.7.
Ah, but the plot thickens. I had superuser on there. I even uninstalled and reinstalled it. No dice.
Update: I said fuggit and did a factory reset. However, my wifi is still not fully connecting to my network although it has no problem finding it. I don't have a recovery image on the external SD and unless i get the network working, will have to wait until tomorrow to get a working microsd->usb adapter to put it on there.
I CAN still get into CWM, thank god.
Current rom is stock 8.6.6.19
Razorclaw gives an error when trying to root.
Also, when trying to moust USB from the recovery menu. it fails, saying "E:unable to upen ums lunfile (no such file or directory).
I am hoping this will magically get fixed after re-installing stock from the SD card ... and that my device isn't somehow crippled.
Sorry for the massive details, but more data = better.
It will magically get fixed
I recommend you flash any Totally stock ota. Then upgrade to the latest OTA, then use my tool PERI (or another) to install recovery and root. Then you should be all fixed up.
Well, it looks like I did get things back on track, but oddly enough, neither of the standard OR modified for root stock ROMs would work. One just wouldn't install, another failed halfway through. MD5s checked out and everything. I had put Revolver 4 beta on there sort of as a "just in case", and that one installed fine (and I was pleased when it displayed "installing Busybox symlinks").
Phew. CLose close call. Now to deal with the bull**** of setting stuff back up again.
However, the question remains: I'm assuming this whole thing happened because of the busybox update and me accidentally installing it to /bin instead of /xbin, and I think it "cleaned up" its own symlinks or something.
I'm not saying don't update your busybox, although I'm sticking with what works and **** upgrading anymore, just be careful...
Thanks for the help!
Recently I used the busybox installer to update my busybox version and it went through great... but after reboot it reverted back to the old version.. And I never touch it since.. don't want to take the hassle further..
There are certain 'plague' versions of busybox that simply don't work. I'd find that list of working BBs and STICK with one that's good. I'm still on 1.63 or someat like that.
Mangraa said:
[Hopefully I didn't miss this being covered somewhere else, as I am much the same as many of you and get beyond irritated with endless repeat questions. I searched using the best keywords I could think of for the issue, but to no avail. Apologies in advance if this has been covered!]
Alrighty. I've got a TF101, rooted it myself (thank you XDA), running 8.6.5.1.9 i believe, stock rom just with root. Used nvflash and Razorclaw. Worked like a charm.
It's been fine for the last 6 months, no issues. However, I decided to update busybox using its internal updater as I have before with no problems. I noticed I accidentally told it to install to /system/bin instead of /system/xbin, and the only reason I even knew about that was due to having to configure an app to find busybox in /xbin instead of /bin.
Now there's a problem. I can still access the internal virtual sd card, but that's about it. The device can't seem to read or write to the main directory (although it can deal with going DIRECTLY to /mnt/sdcard). Ghost commander can't view the main directory, but ESFile explorer _can_, although root browsing in ESFile Explorer is UNchecked. It shouldn't be able to do what it's doing, and it's only doing it in one of two apps.
As a result, I've got no access to any root apps obviousy, but the wifi is having issues as well, it tries connecting but it can't complete the connection.
I'm toying with just wiping and flashing a new rom entirely, but figured I'd ask before I jump in the deep end of things. I keep backups of stuff, but it's still such a pain in the ass reinstalling things.
Any suggestions? I have a feeling it's something "simple", a link file or ... something which linux gurus would know about and I would not, not being a guru or disciple myself.
Thanks in advance!
Click to expand...
Click to collapse
You may have been hit with a bug I introduced.
There was a bug with version 8.0 of my application.
There is not an issue with Busybox V1.20.1.
I apologize for this bug, the application symlinked all applets to Busybox and on some devices there are applets which are unique to the device and should not be replaced by those offered by Busybox.
A simple way to fix this is to simply reflash your rom. You do not need to wipe or clear any data. This will fix the issue and you can update Busybox normally with my application as long as it is version 8.1 or higher.
I apologize for the frustration I have caused, please let me know if I can do anything to help you further. I am trying to find people who were affected to see if I can help rectify the situation.
yeah me too
I guess I should have done a more recent backup. I tell you, there is a reason i have 38 updates waiting, everytime I start going through them, boom blows up in my face
I have tried a few custom ICS and JB ROMs for the A700. I could not get it to connect to my ad-hoc wifi network.
Q1: Is there a ROM out there that supports ad-hoc wifi, for the A700?
Q2: If not, is anyone working on it, preferably for JB?!
I really need this feature, or I'll have to replace the tablet.. :crying:
Maybe you can try it with this little piece of software, but make a backup before trying, it doesnt work on every device!
I tried it with my SGS+ years ago and had no problems at all, others had...
For example it could happen that the wifi isnt working properly anymore (as the developer wrote on his description only a hard reset will help in this case or a backup).
Make a backup, give it a try and then you can revert everything if it doesnt work out for you
Wifi Ad Hoc enabler
https:// play.google.com/store/apps/details?id=nl.arendmedia.wifiadhocenabler
Unfortunately I can't post links because I am below 10 posts... try to search for it manually.
shawnboy99 said:
I have tried a few custom ICS and JB ROMs for the A700. I could not get it to connect to my ad-hoc wifi network.
Q1: Is there a ROM out there that supports ad-hoc wifi, for the A700?
Q2: If not, is anyone working on it, preferably for JB?!
I really need this feature, or I'll have to replace the tablet.. :crying:
Click to expand...
Click to collapse
Probably just need to change wpa.supplicant files for one that enables adhoc. At least on older HC and ICS. JB should probably be the same. Here's a link to a wpa.supplicant file that maybe will work, along with instructions. (always keep a backup of your current supplicant file. You can do all necessary things using ES File Explorer. For this method you need root;
http://forum.xda-developers.com/showthread.php?t=1777413
or
http://forum.xda-developers.com/showthread.php?t=2163363 (this seems to have success on tablets)
For non-rooted, you need an app.
Here's a much simplier app you can use on the non-rooted tablet rather than installing client apps on the PC;
http://forum.xda-developers.com/showthread.php?p=32719405
MD
SnoPoX said:
Maybe you can try it with this little piece of software, but make a backup before trying, it doesnt work on every device!
I tried it with my SGS+ years ago and had no problems at all, others had...
For example it could happen that the wifi isnt working properly anymore (as the developer wrote on his description only a hard reset will help in this case or a backup).
Make a backup, give it a try and then you can revert everything if it doesnt work out for you
Wifi Ad Hoc enabler
https:// play.google.com/store/apps/details?id=nl.arendmedia.wifiadhocenabler
Unfortunately I can't post links because I am below 10 posts... try to search for it manually.
Click to expand...
Click to collapse
Thanks for the tip. I found a list of phones/tabs that Wifi Ad Hoc enabler reported working, there was no A500 and A700. There was A100 with ICS that worked, and A200 with JB that did NOT work. I read up on it, and it sounded like it replaces the wpa.supplicant file. I have tried about 4 different wpa.supplicant files that I could find on the web; none of them worked. I have decided to switch to a different tablet. Thanks again for your help!
Moscow Desire said:
Probably just need to change wpa.supplicant files for one that enables adhoc. At least on older HC and ICS. JB should probably be the same. Here's a link to a wpa.supplicant file that maybe will work, along with instructions. (always keep a backup of your current supplicant file. You can do all necessary things using ES File Explorer. For this method you need root;
http://forum.xda-developers.com/showthread.php?t=1777413
or
http://forum.xda-developers.com/showthread.php?t=2163363 (this seems to have success on tablets)
For non-rooted, you need an app.
Here's a much simplier app you can use on the non-rooted tablet rather than installing client apps on the PC;
http://forum.xda-developers.com/showthread.php?p=32719405
MD
Click to expand...
Click to collapse
Thanks for the tip on wpa.supplicant. I have tried a bunch of them, about 4 or 5. None of them worked. (See my previous post also.)
Regarding FoxFi app through the link you have mentioned, it's now part of PdaNet. According to their web description, it turns a tablet into a hotspot, not what I was talking about--connecting tablet to an ad-hoc network.
shawnboy99 said:
Thanks for the tip on wpa.supplicant. I have tried a bunch of them, about 4 or 5. None of them worked. (See my previous post also.)
Regarding FoxFi app through the link you have mentioned, it's now part of PdaNet. According to their web description, it turns a tablet into a hotspot, not what I was talking about--connecting tablet to an ad-hoc network.
Click to expand...
Click to collapse
Try that second supplicant file. Make sure you set the permissions on it after you copy, then reboot the tab. Wipe cache and dalvik also.
If I get some time, I might check it out. Might be able to merge the changes into our own supplicant file.
MD
Hi, I have the same problem with my a500 cm10 v6supercharge, no way to get enable ad hoc connection?!
Please could some body update the wpa supplicant file?
Thank's
Inviato dal mio A500 con Tapatalk 2