I think I'm gonna write a small app to enable ad-hoc mode as seen for other android models. Anyone interested ?
Must have:
Single button click to enable ad-hoc wifi mode
Restore option, to revert back to previous state
Check if root is enabled, check if device is supported
Anything missing?
-----------------------------
Update:
App is available in the market.
Reported to work on:
Samung Galaxy Tab GT-P7510, GT-P7500
Samsung GT-I9100 * (Samsung Galaxy S2) reported by PAD
Samsung SPH-D710 Galaxy S2 Epic Touch 4G * reported by Scott
Samsung GT-I9000 * (Galaxy S I)
Nexus S * reported by Arpit
BBK vivo v1 * reported by thesunfei
HTC Desire * reported by Jens
Droid * reported by James
* Requires compatibility check to be disabled.
Probably more devices are supported, I will add them when reported.
Market link: https://market.android.com/details?id=nl.arendmedia.wifiadhocenabler
Discussion: http://www.arenddeboer.com/wifi
This would be great...post a link when ur done
make sure to make two apps one that require pershoot kernel and another one without pershoot kernel just a stock one, if so the app will be great, gd luck.
tarekkkkk said:
make sure to make two apps one that require pershoot kernel and another one without pershoot kernel just a stock one, if so the app will be great, gd luck.
Click to expand...
Click to collapse
Why not check inside the app what kernel is used and act accordingly ?
BTW I have used the same procedure to enable ad-hoc for the stock kernel as well as the pershoot kernel, using the same wpa_supplicant file.
I envision the app should:
Check if the device is supported (for now P75XX)
Request/verify root access.
Check if device is already ad-hoc enabled by this app, if not continue.
Verify if wpa_supplicant in /system/bin/wpa_supplicant is in a sain state (verify md5 hash with original) if it doesn't match warn user if he still wants to continue.
Create a copy of the original wpa_supplicant file.
Copy adhoc-enabled wpa_supplicant to /system/bin/wpa_supplicant, overwriting the existing file.
chmod 755 /system/bin/wpa_supplicant
chown system.wifi /data/misc/wifi/wpa_supplicant.conf
Inform user to reboot for the changes to take effect.
I'm not an expert on wpa_supplicant so any help is appreciated.
adeb2 said:
Why not check inside the app what kernel is used and act accordingly ?
BTW I have used the same procedure to enable ad-hoc for the stock kernel as well as the pershoot kernel, using the same wpa_supplicant file.
I envision the app should:
Check if the device is supported (for now P75XX)
Request/verify root access.
Check if device is already ad-hoc enabled by this app, if not continue.
Verify if wpa_supplicant in /system/bin/wpa_supplicant is in a sain state (verify md5 hash with original) if it doesn't match warn user if he still wants to continue.
Create a copy of the original wpa_supplicant file.
Copy adhoc-enabled wpa_supplicant to /system/bin/wpa_supplicant, overwriting the existing file.
chmod 755 /system/bin/wpa_supplicant
chown system.wifi /data/misc/wifi/wpa_supplicant.conf
Inform user to reboot for the changes to take effect.
I'm not an expert on wpa_supplicant so any help is appreciated.
Click to expand...
Click to collapse
fyi, If you want it to work with all Android versions, don't forget that the wpa_supplicant is not always in the same spot(sometimes in in the /etc folder).
I would also like to see this app. Good luck xD
shaolinx said:
fyi, If you want it to work with all Android versions, don't forget that the wpa_supplicant is not always in the same spot(sometimes in in the /etc folder).
I would also like to see this app. Good luck xD
Click to expand...
Click to collapse
Thanks shaolinx,
It would be great to get all the info for the various devices.
I have started the build and completed the initial verifications, has root, md5hash comparison etc. If anyone can provide details about the location and specific wpa_supplicant files I can add it to this app.
check whenever Wifi On or Off, it will error when you change wpa_supplicant when Wifi on
and afaik not need to reboot for changing wpa_supplicant
Correct Me If I Wrong
AnakTeKa said:
check whenever Wifi On or Off, it will error when you change wpa_supplicant when Wifi on
and afaik not need to reboot for changing wpa_supplicant
Correct Me If I Wrong
Click to expand...
Click to collapse
Good to know, I will request flight-mode before proceeding.
I also noted that after switching to the new wpa_supplicant, the signal strength is no longer visible in the wifi icon. Does anyone know whether this is a known issue ?
adeb2 said:
Good to know, I will request flight-mode before proceeding.
I also noted that after switching to the new wpa_supplicant, the signal strength is no longer visible in the wifi icon. Does anyone know whether this is a known issue ?
Click to expand...
Click to collapse
Mine was stable after replacing the original wpa_supplicant file.
Update:
The app is nearing its final stages of completion. I will probably post the link around Sunday. Have to test it first on the stock rom as well as some of the new ICS roms. First version will be raw and unpolished but should be safe and in good working order. I will rewrite it after the initial release to make it easier to add new devices.
Absolutly YES! very interested
The app is ready, I'm currently pushing it into the Market. Will post the link here shortly.
https://market.android.com/details?id=nl.arendmedia.wifiadhocenabler
Request device support or report bugs in the comments on http://www.arenddeboer.com/wifi
Features:
- Enable WiFi Ad Hoc mode (and keep infrastructure)
- Restore original settings
- Fix WiFi permission issues
Requires:
- Root Access (Superuser)
- BusyBox
Issues:
- No WiFi signal strength visible in taskbar
Please be aware this might potentially brick your device (I have tested the app vigorously on several roms and found no problems). I take of course no responsibility for any real or perceived damage...
Let me know if it works for you so I can improve the app.
Regards
FYI.....Task 13.1 works with adhoc wifi, out of the box!
Thank to the TASK team!
Not sure when they did starting this into the Rom, maybe from Pershoot's kernel?
But thanks anyway. Save me time to copy the WPAsupplicantfile over, which I carry with me from Galaxy tab 7 days!
Hehe, at least it was a nice way of learning root lated tasks in app development But it's still handy as the current kang ics roms do not ship with a modified wpa_supplicant.
when i try to connect it says obtaining ip and after that it disconnects
Ad Hoc Wi-Fi can be a bit tricky to setup, can you create a connection with other devices? I also believe you can make only a single connection between ad hoc devices. So be sure the other device is not already connected.
It was fun working on this app, but is has proven to be difficult to make something that enables Ad Hoc on a wide spectrum of Android devices. Therefor I will no longer be updating the application and will remove the "report to developer" option. My next project: running Linux native on my Galaxy Tab P7510.
Starting point will be this thread by poitee -> http://forum.xda-developers.com/showthread.php?t=1189251
Thanks for the feedback.
Nice! Thanks for the app.
I deleted my apk :-( and it doesn't look like you have a stable version up for download. You think you could hook me up with a link? Thanks man!
Related
Great news everyone! </farnsworth>
ADHOC Wifi Support for Nook Color (stock)!
[EDIT] There appears to be an issue reconnecting when wifi sleeps and comes back on. Researching a permanent fix, in the meantime go to settings -> Wireless and toggle wifi off/on to correct it
This fix will allow you to connect to ADHOC wireless networks ( such as to a laptop or with wifi-tether on an android phone )
Like most other fixes, this requires your nook to be rooted and usb adb working, please follow the guides here and/or at the nook dev wiki first!:
Rooting: http://nookdevs.com/NookColor_Rooting
USB-ADB: http://nookdevs.com/NookColor_USB_ADB
HOWTO enable ADHOC tethering:
1. Download and unzip the attached zip file below, this should give you a wpa_supplicant-adhocfix file
2. *DISABLE WIFI ON YOUR NC*
3. Make a backup of your current wpa_supplicant:
Code:
adb pull /system/bin/wpa_supplicant wpa_supplicant.backup
4. Remount the /system partition RW:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
5. Push the new wpa_supplicant:
Code:
adb push wpa_supplicant.adhocfix /system/bin/wpa_supplicant
6. Fix permissions:
Code:
adb shell chmod 755 /system/bin/wpa_supplicant
7. Remount the /system partition RO:
Code:
adb shell mount -o remount,ro /dev/block/mmcblk0p5 /system
8. Enable WIFI on your NC, you should now be able to see ADHOC networks in the list! ( they'll be displayed with a (*) prefix )
[edit] Credit where credit's due, this was taken from a wpa_supplicant IBSS patch I found via a Google search, if anyone knows the party responsible, let me know so I can credit them properly!
http://szym.net/android/
This is compiled against TI's Omapedia Eclair sources ( http://omappedia.org ) - since this is a different framework than the B&N stock build, I can't guarantee this will work, won't brick your device, etc. Use at your own risk!
If you encounter any problems, please use this thread to let us all know.
That's all there is to it, enjoy!
I can confirm that this will allow you to connect you Nook Color to an adhoc network created by a Jailbroken iPhone 4 and MyWi.
Works great! Thanks!
WHOEVER made this fix....THANK YOU! This was the biggest thing I was missing on my NC! Works great!
Cool you figured this out! For some reason, I've been able to use the adhoc network on my Androidized HTC Leo (HD2) since the first time I tried, even before rooting.
Sent from my Rooted Nook Color using XDA App and iPhone MyWi adhoc connection.
You guys ROCK!!!!!!!!!!
Works great with my Droid now. Thanks!
Confirmed working with Mobile Wi-Fi Router on my VZW Touch Pro2.
Many thanks! Another big step!
Work perfectly on my motorola droid 1 using Wireless tether or Barnacle. Thanks for sharing this with us
Works great with AT&T Samsung Captivate and android-wifi-tether ver. 2.0.5-pre15.
Thank you very much!
My NC is stuck at trying to obtain an IP address from my Droid 1. I'm using Barnacle.
Any ideas?
*edit*
It took several attempts but it finally connected. Being able to get connected anywhere is awesome. Thanks for posting this!
Working great from my epic 4g.
Pro Tip: If you want a quick way to toggle wifi (and a few other settings) tap the clock in the nook's notification bar for a quick settings dialog.
Thanks for this. I can now use my nook at work tethered to my phone. You may want to edit the typo in step 7 as we all caught it but someone may not.
Philosophy757 said:
Thanks for this. I can now use my nook at work tethered to my phone. You may want to edit the typo in step 7 as we all caught it but someone may not.
Click to expand...
Click to collapse
Thanks for noticing, corrected the extra 'o'
As noted in the OP, this is based on TI's omap eclair reference sources, and there *is* a pretty glaring bug.
Basically, if your screen goes to sleep, waking it back up triggers a wifi-reconnect which fails to reinitialize the network properly. Your wifi settings will show 'Connected, no internet' when this happens.
Toggle Wifi off/on to fix this, I'm working on a permanent fix right now and will update when it's working.
Thanks everyone for testing and boosting the ol' ego a little
Some random tips so folks don't repeat the same mistakes I made while doing installing the ad hoc feature.
Don't choose to "forget" a wireless access point because then it doesn't appear again even if the device sees it. You'll have to manually enter the SSID, encryption type, and password to get it to work properly.
While mounting and remounting using adb, if you get a device busy error, disconnect the nook from the computer and come back to it later. Then reconnect and try again. For good measure I also powered down the nook. Not sure what happens if you leave the system folder mounted as RW, but I suspect bad things could happen.
Oh and the fix works like a charm. This is one really nice device.
Works perfect on my NC tethered to my MyTouch 3G ( rooted with CyanogenMod-6.1 )
Many many thanks to the dev. !!
Nice work, and thank you. Working fine with another rooted droid (running CM6.1).
I had the "device busy" error and went ahead and unplugged, then reset to ro with Root Explorer- no problems.
This reminds me of when the Droid first got rooted- took a little while to make progress but every few days that would be another BIG, popular advance.
Thanks so much!!!! Droid1 still has life! Yeah.
Thanks. This works great. One question. Does anyone know where I can get the original wpa_supplicant file? I misspelled it so I don't have a good backup. Thanks.
Original nook wpa_supplicant
Here ya go...
OK. Maybe I can't upload files.
I have been having trouble connecting to my work VPN with the G-Tablet. I have since tried going to ZPad 3.0 in hopes this would fix the issue. However, no luck. The VPN server is reporting an event error of 20209.
After a few hours of looking on other forums it turns out this have been an issue since Android 2.1. They have either intentionally left out the encryption module from PPPD or it was forgotten in the build. The 'fix' is to copy the PPPD file from a version prior to 2.1 (Android 1.5?) and save it to the System/xbin directory. However there is an argument over if should go into system/bin for 2.2.
Does anyone have more information on this - or better yet a fix/update? Any help on this would be appreciated.
which ROm are you using
stock ROM doesn't have VPN at all.
justauser said:
stock ROM doesn't have VPN at all.
Click to expand...
Click to collapse
I'm using ZPAD 3.0 ROM at the moment.
I have narrowed it down to a problem with the MPPE 128 encryption. I have found a PPPD that is supposed to fix the problem (see link below), but I don't now how to get it to the system directory. How do you mount system as R/W?
Alternate PPPD:
H***://melko.hiljanen.com/~qvr/android/ppp/
Root explorer will allow you to mount it that way
Sent from my DROIDX using Tapatalk
Let me know how it goes... I have been trying to connect my gtab but I thought I was the only person interested!
Sent from my DROIDX using XDA App
vectorcharlie said:
Let me know how it goes... I have been trying to connect my gtab but I thought I was the only person interested!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Ditto!!!!!!!!
Tried your link, getting the same error I've seen in the past:
Code:
pppd: This system lacks kernel support for PPP. This could be because
the PPP kernel module could not be loaded, or because PPP was not
included in the kernel configuration. If PPP was included as a
module, try `/sbin/modprobe -v ppp'. If that fails, check that
ppp.o exists in /lib/modules/`uname -r`/net.
See README.linux file in the ppp distribution for more details.
I think(?) we need a customized kernel with ppp. So far, we have NTFS and CIFS support that's been added by some of the devs, here.
vectorcharlie said:
Let me know how it goes... I have been trying to connect my gtab but I thought I was the only person interested!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
No luck. The PPPD file didn't make a difference. I guess I should not have been surprised. The L2TP connections are supposed to work so I may try that tomorrow - if I can convince the network admin to make the changes on the vpn server.
The lastest info I have been able to collect on this issue is that it has been known at google since 2.0 was released. They were having a problem keeping a connection using MPPE 128 over PPTP so instead of releasing something that did not work right, they removed support for it until a later date. Said date has not been determined.
I will keep you posted as I find out more.
roebeet said:
Tried your link, getting the same error I've seen in the past:
Code:
pppd: This system lacks kernel support for PPP. This could be because
the PPP kernel module could not be loaded, or because PPP was not
included in the kernel configuration. If PPP was included as a
module, try `/sbin/modprobe -v ppp'. If that fails, check that
ppp.o exists in /lib/modules/`uname -r`/net.
See README.linux file in the ppp distribution for more details.
I think(?) we need a customized kernel with ppp. So far, we have NTFS and CIFS support that's been added by some of the devs, here.
Click to expand...
Click to collapse
I came across this too. Since the ppp directory exists under system/etc I have made the assumption that there is support for it (at least under ztab 3.0). In order to check using the method above we would need a terminal app or some other way to run the commands. If there is a way to do it natively I am too new to know.
Any devs willing to tackle this issue?
Newanzer said:
No luck. The PPPD file didn't make a difference. I guess I should not have been surprised. The L2TP connections are supposed to work so I may try that tomorrow - if I can convince the network admin to make the changes on the vpn server.
...
I will keep you posted as I find out more.
Click to expand...
Click to collapse
No luck. The Net Admin decided it would be too much work just for a tablet test (and his iPAD VPN work just fine thank you). Anyone willing to try a L2TP test?
I have tried L2TP in Vegan with no success. used my android phone to verify settings and it works fine from there.
nephelim said:
I have tried L2TP in Vegan with no success. used my android phone to verify settings and it works fine from there.
Click to expand...
Click to collapse
Ok so that is 2 ROMs down:
TNT Stock - No option
Vegan - Not functional
Just need TNT light and Zpad Clean v3.0 tested. I'm suspecting that it will be no for both. This is starting to creep higher on my list of needs. Does anyone know of a ROM VPN works in?
I confirm that the advent vega rom has the same problem.
Unable to use vpn.
Newanzer said:
Ok so that is 2 ROMs down:
TNT Stock - No option
Vegan - Not functional
Just need TNT light and Zpad Clean v3.0 tested. I'm suspecting that it will be no for both. This is starting to creep higher on my list of needs. Does anyone know of a ROM VPN works in?
Click to expand...
Click to collapse
Do you need tun.ko/kernel support for this stuff? Clemsyn compiled that into one of his kernels - check his thread in the Development forum out, and give that kernel a try with the Vegan ROM, that might get you closer.
rcgabriel said:
Do you need tun.ko/kernel support for this stuff? Clemsyn compiled that into one of his kernels - check his thread in the Development forum out, and give that kernel a try with the Vegan ROM, that might get you closer.
Click to expand...
Click to collapse
That could be worth the check. I would like to see a list of exactly what his kernel supports before I try though.
[EDIT]: Checked change log. VPN module in kernel not mentioned.
Looking over the list of known issues at Google, this problem has been known for a while. The fact that Google hasn't addressed it worries me a bit. It is possible that since phones are the largest part of their OS client, VPN isn't a high priority. They may be waiting for the open source community to solve their problem for them.
Was able to get VPN working
YOU WILL NEED TO HAVE ROOT AND BUSYBOX INSTALLED. PLEASE MAKE A BACKUP IN CASE SOMETHING GOES WRONG.
1st you will need the new kernel found at the below address.
http://forum.xda-developers.com/showthread.php?t=903505
2nd you will need to insert the tun.ko included in with the kernel into /system/lib/modules/2.6.32.27-cyanogenmod folder on the tablet using root explorer.
3rd you will need to install the latest version of vpn from
http://code.google.com/p/get-a-robot-vpnc/downloads/list
4th install a terminal emulator and then you will need type the following commands
su (press enter)
cd /system/lib/modules/2.6.32.27-cyanogenmod (press enter)
insmod tun.ko (press enter)
You should now be able to connect on VPN.
there is very easy installation get and run vpn frome purevpn........
brainyjd said:
YOU WILL NEED TO HAVE ROOT AND BUSYBOX INSTALLED. PLEASE MAKE A BACKUP IN CASE SOMETHING GOES WRONG.
1st you will need the new kernel found at the below address.
http://forum.xda-developers.com/showthread.php?t=903505
2nd you will need to insert the tun.ko included in with the kernel into /system/lib/modules/2.6.32.27-cyanogenmod folder on the tablet using root explorer.
3rd you will need to install the latest version of vpn from
http://code.google.com/p/get-a-robot-vpnc/downloads/list
4th install a terminal emulator and then you will need type the following commands
su (press enter)
cd /system/lib/modules/2.6.32.27-cyanogenmod (press enter)
insmod tun.ko (press enter)
You should now be able to connect on VPN.
Click to expand...
Click to collapse
Sorry for asking this noob question, but is this VPN fix only for Cyanogenmod, or will work with others, such as TnT Lite?
I'm running TnT lite and there no's VPN setup option.
tnt is missing the vpn shortcut
use VPN Show
Kazuyuki Eguchi/Tools
found in android market to access the vpn menu
i have used with sucess on most roms open vpn and open vpn settings
with out problems just by install them and setting it to auto run at start
with install to xbin and create a folder on internal sd "openvpn"
then place a vpn.conf file there
then connect this cause an error but causes super user to give it root rights
after that all my vpn,s work with out going near openvpn
purevpn said:
there is very easy installation get and run vpn frome purevpn........
Click to expand...
Click to collapse
Please elaborate...
Thanks!
Update: See saturn_de's thread for more modules:
http://forum.xda-developers.com/showthread.php?t=1455382
---
Asus failed big time with their ICS kernel. Not only did they leave out the tun module, they also left out several other required options.
After a lot of trial and error, I've found all the modules necessary to connect to VPN, at least using IPSec XAuth PSK mode with my employer's setup. It may or may not work for you.
Root is required. You can find the compiled modules attached. There is a _readme.txt file inside with instructions. Let me know your results!
Thanks to sklid for his initial tun.ko. If you're looking for cifs.ko, you can find it here:
CIFS kernel module for ICS.
Reserved, or something. Although I can hardly imagine actually needing this.
They also left out the ability to properly use the Battery setting for anything other than system processes - can you fix that in your kernel
Oh & can you fix the ad hoc network issue while your at it
Edited: I wished init.goldfish.sh would work. Anyone knows which script got called at startup?
I modified your instruction a bit as my shell script. It does not work if I tried with the ICS VPN - IPSec Xauth PSK. It works using VPN Widget from market.
You can copy the attached file into /etc and set executed permission for it via Root Explorer. When you need vpn, open terminal then execute it after becoming root. Then setup your vpn widget to connect.
huytrang90 said:
Edited: I wished init.goldfish.sh would work. Anyone knows which script got called at startup?
I modified your instruction a bit as my shell script. It does not work if I tried with the ICS VPN - IPSec Xauth PSK. It works using VPN Widget from market.
You can copy the attached file into /etc and set executed permission for it via Root Explorer. When you need vpn, open terminal then execute it after becoming root. Then setup your vpn widget to connect.
Click to expand...
Click to collapse
Is this the app you're talking about? VPNC Widget
If so, it may be something that vpnc supports but the built-in racoon doesn't. I wonder how your VPN is set up differently from mine. Could you post the logcat output (filtered by racoon) from when you're trying to connect using the built-in VPN tool?
I Thanked you for your effort and excellent documentation, but unfortunately my Prime reboots as soon as it completes Phase 2 negotiation. Can post gory details tomorrow if you're interested. Hopefully your work gets the attention of the devs at Asus!
Noxious Ninja said:
Is this the app you're talking about? VPNC Widget
If so, it may be something that vpnc supports but the built-in racoon doesn't. I wonder how your VPN is set up differently from mine. Could you post the logcat output (filtered by racoon) from when you're trying to connect using the built-in VPN tool?
Click to expand...
Click to collapse
That is correct program. I will get that logcat once I have access to PC.
Sent from my Transformer Prime TF201 using Tapatalk
Hey OP or anyone that knows, do you think this works with VPNsecure?
Tairen said:
Hey OP or anyone that knows, do you think this works with VPNsecure?
Click to expand...
Click to collapse
This VPNSecure? Maybe. I've used a PPTP VPN in Gingerbread on my phone before. I don't think ICS has built-in OpenVPN support, though, so you would have to use these kernel modules with the third-party OpenVPN Installer - assuming it still works with ICS.
If you decide to give it a try, let us know if/how it works.
Noxious Ninja said:
This VPNSecure? Maybe. I've used a PPTP VPN in Gingerbread on my phone before. I don't think ICS has built-in OpenVPN support, though, so you would have to use these kernel modules with the third-party OpenVPN Installer - assuming it still works with ICS.
If you decide to give it a try, let us know if/how it works.
Click to expand...
Click to collapse
Damnit so close. Just tried, got all the way through but when I tried to connect after typing in the passphrase this is what I got:
Wait..
Auth..
Get config..
FATAL: Cannot allocate TUN/TAP dev dynamically
My prime appears to connect fine but when I try to access any data over the connection it restarts.
Connection via the widget above works perfect tho!
Tairen said:
Damnit so close. Just tried, got all the way through but when I tried to connect after typing in the passphrase this is what I got:
Wait..
Auth..
Get config..
FATAL: Cannot allocate TUN/TAP dev dynamically
Click to expand...
Click to collapse
Is this from OpenVPN or PPTP? Are there any more detailed logs?
ssjgesus said:
My prime appears to connect fine but when I try to access any data over the connection it restarts.
Connection via the widget above works perfect tho!
Click to expand...
Click to collapse
Strange that multiple people are having restarts. I wonder if there's something in the vanilla Android kernel that doesn't match up with the Asus kernel, or something missing in my modules. It might just be a bug in Android, though. The VPNC Widget totally bypasses a lot of the built-in ICS VPN pieces and uses its own stuff instead.
Noxious Ninja said:
Is this from OpenVPN or PPTP? Are there any more detailed logs?
Strange that multiple people are having restarts. I wonder if there's something in the vanilla Android kernel that doesn't match up with the Asus kernel, or something missing in my modules. It might just be a bug in Android, though. The VPNC Widget totally bypasses a lot of the built-in ICS VPN pieces and uses its own stuff instead.
Click to expand...
Click to collapse
That program works well. It does complain about missing advance routing capability, but works nonetheless.
Sent from my Transformer Prime TF201 using Tapatalk
Noxious Ninja said:
Is this from OpenVPN or PPTP? Are there any more detailed logs?
Strange that multiple people are having restarts. I wonder if there's something in the vanilla Android kernel that doesn't match up with the Asus kernel, or something missing in my modules. It might just be a bug in Android, though. The VPNC Widget totally bypasses a lot of the built-in ICS VPN pieces and uses its own stuff instead.
Click to expand...
Click to collapse
It's what i get when using openvpn settings and following their instructions. I also directed the filepath to tun.ko as well. And yes i was trying to connect to one of their PPTP servers.
i am having restarts as well. how can i see the log of the vpn trying to connect?
ASUS released the kernel source today on their page, so can we get custom kernels now?
DroidHam said:
ASUS released the kernel source today on their page, so can we get custom kernels now?[/QUOT
Need unlocked bootloader & Recovery to flash.
Click to expand...
Click to collapse
When I issue "insmod tun.ko", I get
"insmod: init_module fail 'tun.ko' failed (Exec format error)"
I'm running the virtuous rom 9.4.2.15v2
Pls help
bklm1234 said:
When I issue "insmod tun.ko", I get
"insmod: init_module fail 'tun.ko' failed (Exec format error)"
I'm running the virtuous rom 9.4.2.15v2
Pls help
Click to expand...
Click to collapse
TUN is already enabled in the stock kernel that comes with Asus 9.4.2.15. It may not have been in earlier Samsung kernels before that. So, you shouldn't need to load that module.
you're right _motley. Thx so much.
I have a Netgear WNDR3700v3 as my main router at my apartment. With it, I connect my Galaxy Nexus as well as my Galaxy Tab 10.1 to the Internet. I've been using CyanogenMod for a few years. So I was really excited when my SGT10.1 got on the CM9 train. When the nightlies started in April, everything was fine. But since May, I've been having horrible trouble with my SGT10.1: I haven't been able to connect to the router. When I use a build from mid-April, everything works. When I use any builds from May I can't connect at all. I CAN connect to my SGN as a hotspot. I just can't connect to my router.
Here is the list of what I've tried:
- Changed router to use WPA (and not WPA2)
- Enabled SSID broadcast on the router
- Switched channels on the router
- Turned the 5GHz radio off (as the device has both a 2.4GHz and a 5GHz radio)
- I've tried Pershoots builds and kernels with no luck.
- I've tried both static and dynamic IP addresses for the SGT10.1
I can still work if I stay on the April builds - but I really do want to keep current on CM9. Any other ideas or thoughts?
if your tab p7500 then try this. search in xda how to use it
real77055 said:
if your tab p7500 then try this. search in xda how to use it
Click to expand...
Click to collapse
I have a P7510. And the issue does not appear to be related to WiFi and country codes. I am able to connect to other WiFi access points (like my hotspot). I just can't connect to the WNDR3700.
is your router on a channel greater than 11?
time_shock said:
is your router on a channel greater than 11?
Click to expand...
Click to collapse
I have run it on Auto as well as on channel 8. I've never used a higher channel.
Questions go in the Q&A section
Step666 said:
Questions go in the Q&A section
Click to expand...
Click to collapse
The distinction between "questions" and issues is certainly murky. This is an issue with recent changes in CM9. It worked in April builds and then didn't work in May builds. Can it be phrased as a question? Well, if you follow "Jeopardy" then anything can be phrased as a question. Are you suggesting that I cross-post this?
select 5GHZ from advanced settings, and you should be able to see it and connect (a current bug that needs to be investigated, if you cant see 5GHZ when on auto). make sure your AP/router is on the latest firmware.
this is what you do:
make sure your AP/router is on latest firmware
flash 0514 from droidbasement
while in recovery after flash, clear out /data/misc/wifi/* folder like so:
adb shell mount /data (after you flash this willl be mounted, so no need to mount it)
adb shell rm -r /data/misc/wifi/*
now reboot.
once in, select advanced in wifi settings, select 5GHZ, select your AP manually, and you should be good to go.
april and may builds are completly different in wifi versions. this was required to get wifi 99% stable for the masses. things will get better once new firmware is released from samsung to be used (currently stock firmware from AOSP is being used).
i myself use an e4200 (dual band) with dd-wrt currently. no issue at all with 5GHZ (except for the aforementioned bug in wifi settings).
pershoot said:
select 5GHZ from advanced settings, and you should be able to see it and connect (a current bug that needs to be investigated, if you cant see 5GHZ when on auto). make sure your AP/router is on the latest firmware.
this is what you do:
make sure your AP/router is on latest firmware
flash 0514 from droidbasement
while in recovery after flash, clear out /data/misc/wifi/* folder like so:
adb shell mount /data (after you flash this willl be mounted, so no need to mount it)
adb shell rm -r /data/misc/wifi/*
now reboot.
once in, select advanced in wifi settings, select 5GHZ, select your AP manually, and you should be good to go.
april and may builds are completly different in wifi versions. this was required to get wifi 99% stable for the masses. things will get better once new firmware is released from samsung to be used (currently stock firmware from AOSP is being used).
i myself use an e4200 (dual band) with dd-wrt currently. no issue at all with 5GHZ (except for the aforementioned bug in wifi settings).
Click to expand...
Click to collapse
my advice is to set this up in stages so you can troubleshoot.
leave the 5GHZ (N only; use auto 20MHZ) open, then try to connect to it. after doing so, then implement security if you like (WPA2), then reauth to it on the tab.
ive found 136 and below channels (this is upper) to work ok, but your mileage may vary. auto should be ok to use (this is what i use currently).
pershoot said:
my advice is to set this up in stages so you can troubleshoot.
leave the 5GHZ (N only; use auto 20MHZ) open, then try to connect to it. after doing so, then implement security if you like (WPA2), then reauth to it on the tab.
ive found 136 and below channels (this is upper) to work ok, but your mileage may vary. auto should be ok to use (this is what i use currently).
Click to expand...
Click to collapse
Thanks for the hints. I've tried the recommended WiFi settings for the router, the recommended build (and kernel) as well as erasing the /data/misc/wifi directory. I even wiped /data altogether. Yet I still can't connect to the WNDR3700v3. I can connect to my SGN CM9 phone (as a hotspots). Obviously its a problem with the new WiFi drivers and the router/build.
The tab sees the network. It even determines whether it is protected or not. But even when open, it doesn't seem to connect - or it can't get an IP address.
BTW, where do I set 20MHz? I can't find this in CM9 WiFi settings or Advanced.
Well, I solved the problem by factory resetting the router. All I can figure is that my previous config exposed a bug in the router or CM9. The config that failed used a different base subnet. When I revert to default 192.168.1.0/24, things began to work.
First, the current "MF9" OSRC source release actually contains the MDL kernel sources. While we wait for that to get corrected, I'm using (at noobnl's suggestion) the SCH-R970X MFA sources. I've confirmed that kernels generated from the MFA source tree closely approximate (in as much as any souce-built kernels do) the MF9 kernel shipped in the update. Folks may wish to take a look at the repository I have on GitHub, otherwise there's nothing fundamentally different from MDL in regard to compiling the kernel sources.
Second, wpa_supplicant has been enhanced in MF9 to store network credentials (e.g., WPA-PSK keys) in secure storage now. As secure storage is incompatible with custom kernels (I believe it depends on a TIMA-enabled, signed kernel for TrustZone support), wpa_supplicant can no longer read or store credentials, requiring keys to be reentered everytime WiFi is toggled.
Fortunately wpa_supplicant can be coerced into its old behavior of storing credentials in plaintext (/data/misc/wifi/wpa_supplicant.conf) by disabling the secure_storage service. Attached is a patch against boot's initramfs to do that.
Otherwise the only other things needed to have usable root-capable custom kernels is the usual disable of CONFIG_SEC_RESTRICT_ROOTING and friends, and removing "/system/app/KNOXAgent.*". Elsewhere folks have suggested to also remove "/system/app/KNOXStore.*", but I have yet to find a need to do so. Plus, I think disabling secure_storage neuters it anyways.
So, I'm a little confused on how this works. What all does the wpa_supplicant rely on?
Let me explain my issue right now. The ROM I have built (MF9 based), works with a custom kernel no problems with Wi-Fi.
If I go back to a stock kernel, it stops working properly. Wi-Fi just doesn't turn on. So, I delete (rename) /data/misc/wpa_supplicant.conf, which allows the Wi-Fi to then turn on. (It's extremely slow to do so) But it's got major lag in the menus and logcat spits out the following errors repeatedly.
Code:
[ 07-17 21:55:42.438 5506: 5506 E/secure_storage_api_full.c, ln. 747 ] Client SS library: connect: Connection refused
[ 07-17 21:55:42.438 5506: 5506 E/secure_storage_api_full.c, ln. 384 ] SS_ConnectToDmnSndCmnData error
How exactly are these WPA requests routed through this new system of apks/libraries? In my ROM Base, I've removed most (if not all) of the KNOX stuff, so I figured I'd put all that back (ContainerAgent.apk, the containers folder along with those apks, EnterprisePermissions.apk, KNOXStore.apk and KNOXAgent.apk) but that still doesn't get it to function as expected.
I'm just trying to figure out what I need to put back in so that it will work with the stock kernel as well, or what to include in the stock kernel flashable package to ensure it functions.
Unknownforce said:
What all does the wpa_supplicant rely on?
Click to expand...
Click to collapse
wpa_supplicant requires libsecure_storage.so, which communicates with secure_storage_daemon through /dev/.secure_storage/ssd_socket.
On the other side, where it looks like you're having trouble, secure_storage_daemon runs after the propery ro.securestorage.ready is set true. The property is set at the end of ss-presetup.sh. So you'll need all those items at least.
Otherwise I don't think the apks are necessary, as this operates below the framework level anyways.
Unknownforce said:
I'm just trying to figure out what I need to put back in so that it will work with the stock kernel as well, or what to include in the stock kernel flashable package to ensure it functions.
Click to expand...
Click to collapse
What I'd probably do is remove ss-presetup.sh. This will disable the use of secure storage, much as the initramfs patch does, but without having to modify the stock initramfs. This should force wpa_supplicant to fall-back to the behavior of storing credentials in wpa_supplicant.conf, which is probably what folks would prefer, so that WiFi passwords don't have to be reentered when switching between kernels.
Of course, that breaks secure storage, but I'm not aware of a compelling purpose for it at this point.
mkasick said:
wpa_supplicant requires libsecure_storage.so, which communicates with secure_storage_daemon through /dev/.secure_storage/ssd_socket.
On the other side, where it looks like you're having trouble, secure_storage_daemon runs after the propery ro.securestorage.ready is set true. The property is set at the end of ss-presetup.sh. So you'll need all those items at least.
Otherwise I don't think the apks are necessary, as this operates below the framework level anyways.
What I'd probably do is remove ss-presetup.sh. This will disable the use of secure storage, much as the initramfs patch does, but without having to modify the stock initramfs. This should force wpa_supplicant to fall-back to the behavior of storing credentials in wpa_supplicant.conf, which is probably what folks would prefer, so that WiFi passwords don't have to be reentered when switching between kernels.
Of course, that breaks secure storage, but I'm not aware of a compelling purpose for it at this point.
Click to expand...
Click to collapse
I figured out the problem. It was the mobicore scripts in /system/bin. I renamed them because in custom kernels they aren't used and they continuously error in logcat, so naturally renaming them gets rid of that spam. After re-setting them it works again. Thanks for the reply.