Database Users

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

[GUIDE] Enable ad-hoc tethering on your Transformer (needs root!)

Update: If you are using the official firmware 8.6.5.9 (and obviously above) or any custom ROM based on it, you don't have to do anythink described here, because ad-hoc works natively. Thankfully ASUS fixed Googles unintelligible inability to enable connection to ad-hoc networks.
This renders this thread pretty much obsolete, but I won't delete it, just in case anyone doesn't want to or cannot update his device for whatever reason
Hi!
As there are only [Q]uestion threads about ad-hoc tethering by now, I thought I'd write a little guide how to enable it on our Transformer.
edit: If you are using Prime v1.5 (and above I guess), you don't have to do this. Roach2010 already included the modified wpa_supplicant, so you can already use ad-hoc tethering.
All credits and many thanks go to szym for the edited wpa_supplicant that makes ad-hoc possible for us!
!!! Always make a nandroid backup via recovery first! You can then reflash your backup if something fails !!!
I. Via root explorer (obviously requires root access):
If you bought root explorer from the market, you should be able to easily copy and replace the file.
1.) Go to /system/bin and copy the file „wpa_supplicant“ to your sd card as a backup.
2.) Then copy the „wpa_supplicant“ from the attached zip file and paste it into /system/bin.
3.) Long press the file and set permissions to rwxr-xr-x, like this:
User: read, write, execute
Group: read, execute
Others: read, execute
4.) Reboot
Finally tried it myself and works fine
II. Alternative method via adb (requires root access):
This is a forwarded guide from the Xoom section. I tried it myself and it works like a charm. You can find it here.
All credits for the following guide go to kelvie !
1.) Your Transformer has to be rooted! (you'll find a guide how to root here)
2.) Make a backup of your system/bin/wpa_supplicant first!
3.) Unpack the attached wpa_supplicant_xoom_wifi_adhoc.zip file to your adb folder. (if you don't know how to use adb, google for one of the many guides, or look below for another option via root explorer )
4.) push the file to system/bin/wpa_supplicant:
Code:
adb remount
adb push system/bin/wpa_supplicant /system/bin/wpa_supplicant
5.) Because zipfiles don't store permission, you have to make it executable as well:
Code:
adb shell chmod 755 /system/bin/wpa_supplicant
6.) You also have to change the permissions on /data/misc/wifi/wpa_supplicant.conf for some reason:
Code:
adb shell chown system.wifi /data/misc/wifi/wpa_supplicant.conf
7.) reboot
Again, many thanks to kelvie for the guide!
III. Easiest method (requires ClockWorkMod recovery and root):
1.)Download the attached CWM_adhoc_wpa_supplicant_TF101.zip to your sd-card. Make sure to copy it to /Removable/MicroSD, because /mnt/sdcard cannot be accessed from CWM
2.) Boot into CWM recovery.
3.) Hit "install zip from sdcard" --> "choose zip from sdcard", select the zip and confirm.
4.) Reboot
Done. You should now be able to tether your ad-hoc connection
This method doesn't seem to work because I missed an option and don't know right now how to fix it. So if somebody knows how to do this via edify script, please help me out:
Code:
chown system.wifi /data/misc/wifi/wpa_supplicant.conf
Use one of the methods above in the meantime, they works flawless.
__________________________________________________
Q&A
Q: Which app should I use for tethering on my phone? Do I need root access for tethering apps?
A: If your phone doesn't support native tethering, just search the Android Market for 'Wifi tether'. There are a lot of apps for that . I tested Barnacle Wifi Tether on my Sony Ericsson Xperia X10 with 2.3.4 MIUI ROM, which worked fine, but I guess all/most tether apps should work fine now. And yes, unless you have native tethering, your phone has to be rooted.
Q: Barnacle gives me the following error on the phone: "DHCP could not bind to DHCP port, address already in use", and my TF is stuck at "obtaining IP Address from barnacle". What should I do?
A: rpavich has found a solution for that. Thanks rpavich!
rpavich said:
1. Change SSID to whatever you want
2. Change Channel to 6
3. Custom Wifi Ad-hoc to none
4. Skip wpa_supplicant checked
5. Restart your phone (just to make sure...)
Click to expand...
Click to collapse
__________________________________________________
Regards
qwer23
Edit: I wasn't sure if this belongs in General or Android Dev section, so mods feel free to move it where it fits best.
Edit2: Attached original wpa_supplicant files for 3.0 and 3.1 (don't know if there's a difference, but I doubt it) if someone wants to reset to stock.
If you find this guide helpful, consider pressing the thanks button
Click to expand...
Click to collapse

awesome. a few more working confirmation from the others and i wont have to kiss my nokia e71 goodbye

philsuf said:
awesome. a few more working confirmation from the others and i wont have to kiss my nokia e71 goodbye
Click to expand...
Click to collapse
No need to wait, you could just try it. If you back up your original wpa_supplicant first, you can always undo your changes. I also added an easier way via root explorer that should be easier.

i just tried it, it connected to barnacle wifi but i couldnt get the internet to work. ill try again tomorrow, it may be my phone.

Skeldave said:
i just tried it, it connected to barnacle wifi but i couldnt get the internet to work. ill try again tomorrow, it may be my phone.
Click to expand...
Click to collapse
Did your phone show the barnacle symbol in the notification bar and tell you that a device is connected?
Sent from my rooted X10i using awesome custom roms

I've done this last week and noticed when stopping my hotspot on the phone the connection on the transformer shows it is still connected. So you have to manual disconnect if you want to reconnect again for later use. This is on my Nokia N8 Phone using JoikuSpot.

I tried to do this via the root explorer and it said "you cannot paste here because the file system is read only"

rpavich said:
I tried to do this via the root explorer and it said "you cannot paste here because the file system is read only"
Click to expand...
Click to collapse
On the top of your system directory in root explorer is a button, that says r/w. Push it and you'll get read/write mode.
Sent from my rooted X10i using awesome custom roms

thank you VERY much....I'll let you know how my tethering goes.

qwer23 said:
Did your phone show the barnacle symbol in the notification bar and tell you that a device is connected?
Sent from my rooted X10i using awesome custom roms
Click to expand...
Click to collapse
Yes, the barnacle symbol was in the notification bar and my TF appeared on the 'client' tab, also the TF said that it was connected to barnacle wifi.
I'm going to try again now
EDIT: Worked perfectly this morning, thanks!
I did it via root explorer FYI

This seems like a rather minor change to wpa_suppliant.conf; any clue if google will fix this in honeycomb? Not sure I understand why it isn't enabled by default...

Ok...trouble getting this to work.
1.) On my Xperia X10; message in Barnacle:
"DHCP could not bind to DHCP port, address already in use"
2.) On my TF: it's stuck at "obtaining IP Address from barnacle"

Ok....found the solution (on another XDA forum section)
I did the following and connected just fine!
1. Change SSID to whatever you want
2. Change Channel to 6
3. Custom Wifi Ad-hoc to none
4. Skip wpa_supplicant checked
5. Restart your phone (just to make sure...)

rpavich said:
Ok....found the solution (on another XDA forum section)
I did the following and connected just fine!
1. Change SSID to whatever you want
2. Change Channel to 6
3. Custom Wifi Ad-hoc to none
4. Skip wpa_supplicant checked
5. Restart your phone (just to make sure...)
Click to expand...
Click to collapse
Mind if i add this to the op? There might be others with this issue.
Sent from my rooted X10i using awesome custom roms

jake21 said:
This seems like a rather minor change to wpa_suppliant.conf; any clue if google will fix this in honeycomb? Not sure I understand why it isn't enabled by default...
Click to expand...
Click to collapse
I don't have a clue either why this isn't enabled by default, but I think they'll add this in the 3.1 update. But it's just a suggestion, didn't read anything about it though.
Sent from my rooted X10i using awesome custom roms

qwer23 said:
Mind if i add this to the op? There might be others with this issue.
Sent from my rooted X10i using awesome custom roms
Click to expand...
Click to collapse
Not at all....as i said...I got that from another part of the XDA forum...

I used this method from my rooted OG Droid and the Xoom and it worked perfectly. I have to wait for my son in law to root my TF to try it out. Would I only need to root the TF for this to work?

sanfaz said:
I used this method from my rooted OG Droid and the Xoom and it worked perfectly. I have to wait for my son in law to root my TF to try it out. Would I only need to root the TF for this to work?
Click to expand...
Click to collapse
At the moment you need to root both your TF and your phone. But if you use Clockworkmod, you probably don't need a rooted TF, because I'm preparing an update.zip to flash via CWM
Your phone has definitely to be rooted, ecxept it supports wifi tethering from stock.
edit: darn, amend scripting is no longer supported in Honeycomb. Anyone knows how to change the zip for edify scripting?
edit2: ok, probably got it solved. we'll see...

Ok, I added a zip file for easy install through ClockWorkMod to the OP. It installed fine on my TF101 and tethering works, but please backup your wpa_supplicant before installing this and report any errors. I didn't work with edify scripts before
I also restructured the guide itself, from easiest to most complicate method
Cheers
qwer23

Would this mod work with an old TP2 windows mobile phone? Will the TF then be able to use it's wifi signal?
Also, if the TF is rooted, will we be able to accept the 3.1 HC update?

Tun.KO Kernel [email protected]

Trying to use anyconnect and get an error about Tun/Tap driver. On android 3.2 touchwiz. Have found several but every time i do a insmod tun.ko get a error. Is there a tun.ko driver available, if so can you please point me in the right direction. Thanks!

Anyone
Can anyone point me in the right direction please?

Where did you get Android 3.2 for the Galaxy Tab 10.1?

My bad
my bad, 3.1, fat finger syndrome

This might help:
forum.xda-developers.com/showthread.php?t=1262315

U da MAN
morkli thank a million times over, that was it. I have been searching all day, I knew if i came to this forum, I would get the answer and help. Again thank you!!

Glad I could help

sorry to dig up the dead, but i cant get this working.
I have a LTE tab running liquidspeed beta 6. I am trying to use the Cisco anyconnect client (not the same as used in the link above) I was getting the error that the tun module was missing from /data/local/kernel_modules.
I dled the tun.ko file and placed it in /data/local/modules folder and ran su and then insmod /data/local/modules/tun.ko both commands had no response or errors.
I then said, okay it is looking in /data/local/kernel_modules so i will place it there and run the insmod command to point there.
When i run the anyconnect app, it hangs and reboots my tablet.
Anyone get this working? i need some help as I use VPN for work often.

See my post in http://forum.xda-developers.com/showpost.php?p=19007667&postcount=20

Digging this up...
I'm using liquid speed beta 6. Can get connected with AnyConnect, but it reboots when trying to finishes the connection. I've insmod and tried from data/local/modules... And just copies to kernel_modules with same result.
Had anyone done a full anyconnect with a pershoot kernel yet?

iceshrike said:
Digging this up...
I'm using liquid speed beta 6. Can get connected with AnyConnect, but it reboots when trying to finishes the connection. I've insmod and tried from data/local/modules... And just copies to kernel_modules with same result.
Had anyone done a full anyconnect with a pershoot kernel yet?
Click to expand...
Click to collapse
i never got mine working either

Kindle Fire tun.ko

I managed to compile a tun.ko that loads on the fire. I don't really have to time to test establishing a VPN tunnel right now, nor do I know if there is anything else needed to make a VPN work on this device.
I did install the module and tool around a bit to make sure nothing blew up though. It hasn't yet.
Things seem to be coming along so quickly with the ROMs and whatnot, I don't know that there's much of a need for this right now anyway....
Anyone able to test anything with this? As normally goes for this type of stuff, anything you choose to do with the attached file is at your own risk.
Code:
# insmod tun.ko
# lsmod
tun 12481 0 - Live 0xbf13a000
tiwlan_drv 972959 0 - Live 0xbf000000
#
Cheers.

Hi,
I tried this (noob alert)
I placed it in /sdcard/
Using OpenVPN I set the TUN module settings to load module to insmod and path to /sdcard/
I then set load tun kernel module before starting openvpn
Generally on trying to connect I get, wait - auth - get config - reconnecting (due to tls-error)
This happens twice then I get "Fatal error - unable to assign TUN/TAP dev dynamically.
I have a log file if it's of help.

Wish I was somewhere I could play around with this today, but I probably won't be until tomorrow.

FWIW From a read of other people's experiences with tun.ko for other devices I tried it a few locations, /dev/net/tun /dev/tun but the same result each time.

ajq said:
I managed to compile a tun.ko that loads on the fire. I don't really have to time to test establishing a VPN tunnel right now, nor do I know if there is anything else needed to make a VPN work on this device.
I did install the module and tool around a bit to make sure nothing blew up though. It hasn't yet.
Things seem to be coming along so quickly with the ROMs and whatnot, I don't know that there's much of a need for this right now anyway....
Click to expand...
Click to collapse
There is definitely need for this. I'm rooting and will be romming my Kindle Fire, but my wife's Fire will probably stay fairly vanilla, perhaps just with full market enabled. As we are in Australia VPN is essential to have access to Amazon Prime and other services...
Anyone made any progress to working VPN yet? I'm at work so can't play...

Hi, I tested it and failed. tun.ko crashed and system reboot, just after openvpn try to make tun device ;-)
FYI, I use this openvpn binary for test: https://github.com/fries/android-external-openvpn/downloads

Installed OpenVPN from Android Market and configured VPN config files and this compiled tun.ko caused a reboot during the 'get config' phase of the OpenVPN login.

I'm in China and I tried PUFF SSH apk for Android system and it worked!
You can check my ip is USA in the browser.
https://seapuff.com/puff.apk
I post the screenshot images and tutorial in this Chinese forum:
http://bbs.mydoo.cn/thread-54630-1-1.html
I am looking for VPN app for Kindle Fire as well, if someone knows that please don't hesitate telling me, thanks!

fire tun.ko almost
same result as damianarnold. insmod happens, lsmod shows module. openvpn gets almost done, then fire reboots.

bump. need VPN
just tried to share my PC's VPN (HMA pro) using connectify.me which makes a wireless hotspot rather than an adhoc network, but for some reason connectify drops out when the VPN is active, dammit.
VPN on the Fire itself would be so much easier...

mclad said:
bump. need VPN
just tried to share my PC's VPN (HMA pro) using connectify.me which makes a wireless hotspot rather than an adhoc network, but for some reason connectify drops out when the VPN is active, dammit.
VPN on the Fire itself would be so much easier...
Click to expand...
Click to collapse
If unblock.us isn't working for you, wait for the custom kernels and/or ids/cm9, and it wont be an issue.... waiting stinks, but there are some smart folks working on it.... sorry the module didn't work, but all the rest of the von stuff has been left out of the device. Unblocked.us worked for me a good portion of the week I was in the eu.
Sent from my Kindle Fire using xda premium

try it ,it is working on my kindlie fire openvpn !

I just went to Market and grabbed TUN.ko Installer app. The developer's web site says it works for Kindle Fire. I installed it and now the "Rooted AnyConnect" app works. No muss. No fuss.

Astrobrewer said:
I just went to Market and grabbed TUN.ko Installer app. The developer's web site says it works for Kindle Fire. I installed it and now the "Rooted AnyConnect" app works. No muss. No fuss.
Click to expand...
Click to collapse
Hi Could you please describe a little which VPN service you use or even recommend to use to access Amazon prime service?
many thx
regards
Mjay

Not working
Astrobrewer said:
I just went to Market and grabbed TUN.ko Installer app. The developer's web site says it works for Kindle Fire.
Click to expand...
Click to collapse
Unfortunately, this does not work for me. Neither do other tuns attached to the thread. Is there any other alternative?

Tun.Ko is fantastic! Had some issues getting FeatVPN set up with my Kindle Fire but after installing tun.ko everything's working flawlessly. This is awesome.
Installed Tun.ko > Installed/Ran FeatVPN setup > Connect with HideMyAss VPN.
BTW, running @twa_priv's CM10 Jelly Bean ROM.
Thanks for the tip for tun.ko!

what should I do with this " tun.ko" file to run vpn? how can i install it?

WiFix - Fixes regional Wi-Fi problems in Android 4.0

WiFi Fix for Android 4.0
Description
I recently found out many people in certain countries no matter what kinds of devices they're using, have issues with WiFi when SIM-Card is inserted.
I realized that changing the WiFi Country Code solves the problem and made an application that does this automatically on each boot and on network state changes.
Installation
It's pretty easy; first of all you should root your device.
Then install WiFixManager.apk.
Start WiFix Manager from applications menu and tap Install WiFix (allow SuperUser permission.)
Once installed, you're ready to go. The application will change the country code when needed. You can also invoke it manually by dialing *#94349# (*#WIFIX#) and pressing the call button (don't forget to press call button; it's not a MSL code).
Updates
You can check for updates and install them via WiFix Manager.
Code:
Change Log:
1/14/12 WiFix V1.0, WiFix Manager V1.1:
Initial Release
1/25/12 WiFix 1.1, WiFix Manager V1.2:
Changed minimum SDK version and API Level to 3
Minor layout changes
Minor bug fixes
1/30/12 WiFix 1.2, WiFix Manager V1.3:
Added custom country code support
7/3/12 WiFix V1.2, WiFix Manager V1.31:
Minor layout bug fixes
Compiled with Android SDK 14
12/9/12 WiFix V1.2, WiFix Manager V1.32
Minor bug fixes (Device compatibility improvement.)
Added reboot prompt after installation and removal.
Compiled with Android SDK 16
Known Issues
Sometimes when you reboot your phone with WiFi turned on, you won't have internet access (you can't open webpages, download files etc.) even though it says it's already connected to your AP.
This issue can be fixed by turning WiFi Off and On or dialing *#WIFIX# as described before.
For ROM Cookers
By placing WiFix.apk in /system/app you'll have a WiFix enabled ROM.
If you're publishing that ROM, please include a link to this thread
Newer fix by XDA Member HTCZ715E
As of today, most of the manufacturers (including HTC and Sony) solved this Wi-Fi issue with their ROMs. Fortunately, there's no need for WiFix anymore.
For those who still have issues with custom ROMs and WiFix, try this.

Thanks. Working fine. much simpler to setup than the script.

Not working....
While I have given the app root permissions, when I click "Install WiFix" it replies with:
"Can't get root access. Either your device is not rooted, or SuperUser request has been rejected."
Ironically, it is immediately followed by:
"WiFi Manager has been granted Superuser permissions."
Any suggestions... am I missing something?

jhedfors said:
While I have given the app root permissions, when I click "Install WiFix" it replies with:
"Can't get root access. Either your device is not rooted, or SuperUser request has been rejected."
Ironically, it is immediately followed by:
"WiFi Manager has been granted Superuser permissions."
Any suggestions... am I missing something?
Click to expand...
Click to collapse
It's a little bit strange.
Root access checking routine, basically opens su, and checks the User ID. So either it can't execute su or the id is different when you're root (!!!) or there is a problem with IO streams (I hope not.)
Anyways, you can help me fix this problem by posting the steps (from installation to error message) to reproduce the error.
Please do the following and post the result:
Install a Terminal Emulator app (this one for example) or get into shell with adb (note that installing Terminal Emulator is preferred since you always log-in as root with an insecure kernel.)
Open it and type "su" (without quotes), and press enter.
Allow SuperUser permission request.
Type "id" (without quotes), and press enter.
Post the result here.
Type "exit" (without quotes), and press enter to logout.
It will be useful to post your device and ROM information as well.
Thanks in advance for your help,
I'll fix it as soon as I realize where the problem is

omar302 said:
Thanks. Working fine. much simpler to setup than the script.
Click to expand...
Click to collapse
You're welcome
The main difference between this application and that script is, it sets the wifi_country_code property by interacting with Secure system settings provider, thus it doesn't need to gain root access and execute sqllite for changing the country code. However it should be placed in /system/app to work. (WiFix Manager does this automatically with one time root permission.)

fardjad said:
It's a little bit strange.
Root access checking routine, basically opens su, and checks the User ID. So either it can't execute su or the id is different when you're root (!!!) or there is a problem with output/input streams (I hope not.)
Anyways, if you like, you can help me fix this problem by posting the steps (From installation to error message) to reproduce the error and do the following and posting the result:
Install a Terminal Emulator app (this one for example) or get into shell with adb (note that installing Terminal Emulator is preferred since in rooted devices when you get into shell with adb shell you're already logged in as root.)
Open it and type "su" (without quotes), and press enter.
Allow SuperUser permission request.
Type "id" (without quotes), and press enter.
Post the result here.
Type "exit" (without quotes), and press enter to close the SuperUser session.
It will be useful to post your device and ROM information as well.
Thanks in advance for your help,
I'll fix it as soon as I realize where the problem is
Click to expand...
Click to collapse
My steps were:
1. Install WiFix Manager
-Successfully installed
2. Open WiFix Manager
3. Click "Install WiFix"
4. Click "Allow" on the Superuser Request pop-up
5. I then get the error above.
After entering ID in Terminal Emulator, I get the response "Toolbox!"
I have HTC Vision/G2, running "Virtuous Quattro Beta 9" in Boot Manager.
Thanks!

jhedfors said:
My steps were:
1. Install WiFix Manager
-Successfully installed
2. Open WiFix Manager
3. Click "Install WiFix"
4. Click "Allow" on the Superuser Request pop-up
5. I then get the error above.
After entering ID in Terminal Emulator, I get the response "Toolbox!"
I have HTC Vision/G2, running "Virtuous Quattro Beta 9" in Boot Manager.
Thanks!
Click to expand...
Click to collapse
OK, so the problem is the id command output. normally it should be something like uid=0(root) gid=0(root), most likely it's a rom issue (try fixing your permissions), however I will release another APK (after about 10 hours) that doesn't fail if id does not contain root.

Can I suggest something?
Why not make a flashable zip so "wifix.apk" can be flashed directly to "system/app" without having to use "wifixmanager.apk"

omar302 said:
Can I suggest something?
Why not make a flashable zip so "wifix.apk" can be flashed directly to "system/app" without having to use "wifixmanager.apk"
Click to expand...
Click to collapse
Of course
Here it is.

jhedfors said:
While I have given the app root permissions, when I click "Install WiFix" it replies with:
"Can't get root access. Either your device is not rooted, or SuperUser request has been rejected."
Ironically, it is immediately followed by:
"WiFi Manager has been granted Superuser permissions."
Any suggestions... am I missing something?
Click to expand...
Click to collapse
jhedfors said:
My steps were:
1. Install WiFix Manager
-Successfully installed
2. Open WiFix Manager
3. Click "Install WiFix"
4. Click "Allow" on the Superuser Request pop-up
5. I then get the error above.
After entering ID in Terminal Emulator, I get the response "Toolbox!"
I have HTC Vision/G2, running "Virtuous Quattro Beta 9" in Boot Manager.
Thanks!
Click to expand...
Click to collapse
OK, I updated the first post and uploaded a new APK and a Recovery Flashable Zip.
Please test and report the results

I've these issues with gb on my HTC Desire -_-

I'm not really sure I understand what problem this is fixing. I have a problem with my wifi that I want to check with you first. Mine is basically where the wifi turns itself off when I go out of range of a connected router for a few minutes . When I come back in range of the router I have to manually turn wifi back on before it will connect back to the wifi. This is despite having the sleep policy set to never so I have no idea why wifi won't stay on. I don't want to install this without understanding the issue a bit more first!
Thanks
Shane

jhedfors said:
While I have given the app root permissions, when I click "Install WiFix" it replies with:
"Can't get root access. Either your device is not rooted, or SuperUser request has been rejected."
Ironically, it is immediately followed by:
"WiFi Manager has been granted Superuser permissions."
Any suggestions... am I missing something?
Click to expand...
Click to collapse
Have you tried fixing permission first incase ur Su or binaries are out dated? Or maybe not.
Sent from my PC36100 using xda premium

Which certain countries?

TheBishopOfSoho said:
I'm not really sure I understand what problem this is fixing. I have a problem with my wifi that I want to check with you first. Mine is basically where the wifi turns itself off when I go out of range of a connected router for a few minutes . When I come back in range of the router I have to manually turn wifi back on before it will connect back to the wifi. This is despite having the sleep policy set to never so I have no idea why wifi won't stay on. I don't want to install this without understanding the issue a bit more first!
Thanks
Shane
Click to expand...
Click to collapse
I don't think that this application can solve your problem. Sorry
WiFix simply changes the WiFi country code which might be set incorrectly (?) in IceCream Sandwich builds when SIM-Card is inserted.

qwerty017 said:
Which certain countries?
Click to expand...
Click to collapse
Basically most of the countries located in Middle-east and Africa.

fardjad said:
Basically most of the countries located in Middle-east and Africa.
Click to expand...
Click to collapse
Thanks. Was wondering if it affected me or not.

qwerty017 said:
Thanks. Was wondering if it affected me or not.
Click to expand...
Click to collapse
If your phone can't find WiFi networks or can't connect to them unless you remove the SIM-Card then you're affected.

fardjad said:
Basically most of the countries located in Middle-east and Africa.
Click to expand...
Click to collapse
Very useful for me if I am traveling back home, or visiting family in NZ or AUS. Thank's for posting this.

fardjad said:
If your phone can't find WiFi networks or can't connect to them unless you remove the SIM-Card then you're affected.
Click to expand...
Click to collapse
I would suggest you put in the app introduction to explain in an easier:
"If wifi is working fine in Gingerbread roms, but does not when flashing/upgarding to IceCreamSanwich, then this app will try to fix it!"