First, sorry to post here and no in developpement section but I haven t the right
Second, I try the megatron rom and it was fabulous. Everythings work fine and with guevor kernel, it is very fast.
My problem is that very often, i need to go on web without wifi connection. I do it with my phone ( htc tattoo) via wireless tether. It works fine with stock rom ics rooted but none with megatron.
In this case, the tablet can't see my phone
Any idea to resolve my problem ?
No problem for me, tethering from iPhone4 and Free
Thanks for the answer. Now I know it 's possible. I'll try again. Megatron is really amazing and I hope I can utilise it again
I tried again and same issue. The tf can't see my tattoo when I am with megatron rom. No problem with stock ICS or now with revolver RC2 and guevor kernel 17c.
Anybody have idea why ?
Is it a problem of chanel?
I hope there's a solution because I really prefere megatron but I need the possibility to utilise android tethering
Funny enough, I have the same issue. I love megatron (with guevor's 17c), but wifi tethering from my phone isn't visible to my tf101. It's visible to other people around me, but not to the tf101.
That's weird, mine work fine. I'm actually tethering off my CM7 N1 right now.
I'm happy to see that I'm not the only one with this problem. I'm happiest to see that it's possible tethering work and the phone can be see by the tf. But how?
I have the same problem with Megatron v1.0.4, with Revolution 3.2.2 or stock rom I can make tethering from my computer but I can't in Megatron. I think this is a problem with ad-hoc connections (I have the same problem with cyanogenmod in my phone). I hope it works in Megatron v1.1.0 because I like this rom.
This worked for me.
These are the instructions that came with the file:
1. root is required AND make sure you have your file system app (like Root Explorer) set to make files R/W so you can edit/rename/set permissions
2. turn off wifi
3. go into system/bin and rename wpa_supplicant2 to wpa_supplicant2.bak - that's right folks.. it is NOT wpa_supplicant but wpa_supplicant2 that is running the show
3. download the wpa_supplicant file found here post #24 in my other thread
4. unzip it
5. rename it wpa_supplicant2 NOT wpa_supplicant (already renamed)
6. move it to system/bin and paste it
7. set permissions to 755
8. go back and start up wifi
9. turn on wifi analyzer and you will see (*)AndroidTether with no red Ad Hoc notation!!
10. click to connect
11. surf and tether away!!
On my TF101 I did not have a wpa_supplicant2 in system/bin. I just copied the attached wpa_supplicant2 file into system/bin and set permissions to 755. Now I can connect to ad-hoc wifi signals like from my old Droid-1. The new file does not seem to affect infrastructure connections.
I am not sure under what conditions loading a new ROM will wipe out the modified wpa_supplicant2 file so keep a backup handy.
-Rick
Wireless tethering from mb860 running cm9 to tf101 running megatron. No issues at all.
TF101 Megatron 1.0.4 Guevor test 17c
Updated megatron to 1.1.1 and it works now.
Just make sure you use guevor's kernel from megatron's thread!
In v1.1.1 I see the connection but I can't connect. I tried copying the wpa_supplicant2 file to /system/bin and setting 755 permissions but the same problem. I tried with stock kernel and guevor-17c kernel (downloaded from ricardo's thread)
I'm in the same situation. Nice progress, I'm updated to megatron 1.1.1 with guevor kernel 17c. Now, The tf see my phone and say to me that the signal is strong. But impossible to connect. But at the same time, I can connect my pc to my phone and go to the net.
Where is the mistake?
Any solution welcome
Thanks
I also upgraded to Megatron 1.1.1 and the Adhoc tethering stopped working (with the wpa_supplicant2 file in place.) It was working fine in 1.0.4. When it is working properly your adhoc access point signals will have (*) in front of them. I'll so more testing after I flash back to 1.1.1. -Rick
Nice. I wait and hope you'll find a solution
Regards
Pat
Well, I flashed Megatron 1.1.1. This version only installs a single file: system/bin/wpa_supplicant
With 1.1.1 the adhoc wireless access point (my old Droid-1) shows up in the list and tries to connect (obtaining ip address...) but never connects.
With Megatron 1.0.4 if you copy that special wpa_supplicant2 file I previously posted into system/bin then the adhoc signals show up with a (*) in front of the SSID and you can successfully connect.
I tried installing Megatron 1.1.1 but copied wpa_supplicant from v1.0.4 and the special wpa_supplicant2 into the 1.1.1 rom. Adhoc still would not connect.
So at this time the only way I know to use adhoc tethering with Megatron is with 1.0.4 and copy the special wpa_supplicant2 file I previously posted into system/bin using Root Explorer.
I did these tests with Guevor 17c kernel.
For those who have mentioned that their laptops connect to the wireless access point fine, that's because (at least with windows) the OS can connect to both adhoc and infrastructure mode wifi signals. I believe somewhere starting with ICS the adhoc mode was considered insecure and was removed from the code. Some phones like my old Droid-1 can only create an adhoc tether. I think some of the newer phones can create an infrastructure wifi tether so that explains why some of you are having success.
I am not an expert here so I defer to others who are more learned and experienced than I.
-Rick
I don't use ad-hoc connections but you can try replacing wpa_supplicant in megatron 1.1.2 with wpa_supplicant2.
What i mean is you have to rename wpa_supplicant2 to wpa_supplicant and replace in it in the rom
Hi Ricardo,
Thanks for the GREAT ROM and the great work you do.
After version 1.0.4, replacing wpa_supplicant2 no longer works. I tried it in 1.1.1. The connections show up and try to connect but never actually finish connecting. If I flash back to 1.0.4 and copy the adhoc version of wpa_supplicant2 then adhoc tethering will work again. So something probably changed in the wifi driver after 1.0.4.
Are you saying in 1.1.2 I should delete the existing system/bin/wpa_supplicant, replace it with the adhoc version wpa_supplicant2 (renamed as wpa_supplicant)? I think I tried this in 1.1.1 and wifi would not turn on at all. I will try it again.
Can I do the replacement with Root Explorer on the live system or does the file need to be replaced in the ROM zip file before flashing?
Update: With the adhoc version of wpa_supplicant2 (named as wpa_supplicant) installed on 1.1.2 the wifi does not even turn on. With the original 1.1.2 wpa_supplicant plus the adhoc wpa_supplicant2 in system/bin, adhoc still does not work but the rest of wifi works. Using Guevor's 19.3 now.
-Rick
Thanks also Ricardo for your rom and for all the works and the time you give to answers at our problems.
Thanks to Rick for the help. Just after dinner, I wanted to try your solution with the modifications of Ricardo. You do it before.
Well, wait and hope there's a solution
Pat
Edit
@Rick
I come back to 1.0.4 and make all you said. Everything goes well and know I have tethering. It's the more important for me. I hope a solution will be find with the 1.1.2 but i'm very happy like this.
Thanks a lot
And if somebody find something for 1.1.2 please give us
provide me a logcat in 1.1.2 with the original wpa_supplicant
Related
I am thinking of picking up one of these, but I would need to be able to connect to an ad-hoc wifi network. does anyone know if this is possible? Also if anyone can tell me how much faster it appears to run after the stock overlay is removed I would appreciate it. Thanks all
matthewallen72 said:
I am thinking of picking up one of these, but I would need to be able to connect to an ad-hoc wifi network. does anyone know if this is possible? Also if anyone can tell me how much faster it appears to run after the stock overlay is removed I would appreciate it. Thanks all
Click to expand...
Click to collapse
As far as Ad Hoc, yes it can be done. Worked for me when I still had mine. Connected to the wifi from my Droid 1. You have to hack the wifi file a bit but its not hard.
can you tell me what you did to the wifi file? are you using wireless tether on the droid? thanks
this worked for me
http://forum.xda-developers.com/showthread.php?t=754961
this one worked for me
kitzuki said:
http://forum.xda-developers.com/showthread.php?t=754961
this one worked for me
Click to expand...
Click to collapse
Can you just rename the zip as update and run through the stock recovery?
The newer TnT Lite and VEGAn mods have this binary, already.
As for how much faster, not a lot versus adding a Tegra performance pack. If you want speed, you want the performance pack or run one of the mods above (especially VEGAn).
I want to keep it stock until after the next update. I just want to see how it works stock. Testing to see if this will be a good device for my father he isn't going to be flashing ROMS so I want to see what I can do with a stock ROM.
How do I get the Ad Hoc working with Stock ROM?
jasco13 said:
How do I get the Ad Hoc working with Stock ROM?
Click to expand...
Click to collapse
The Adhoc fix is in the wpa_supplicant file. You'll need to replace the stock version of that file from the version in the latest vegan or TnTlite build.
I'm not sure if you can simply connect to computer via USB, find the file, and replace it (I doubt it).
Perhaps you can create a recovery update that only replaces that one file. I don't know if it works, but you could try starting with a Vegan or Tnt build, keep the recovery folder, and delete everything in the update.zip except for the wpa_supplicant file.
I am loving Audiogalaxy, but I have an issue and I was wondering if anyone could help me.
I am running CM7 Nightly 26 with Tiamat 3.3.1 and I can connect to Audiogalaxy just fine.
I updated to CM7 RC3 yesterday and flashed SavagedZen 0.2.0 CFS noSBC and for some reason, Audiogalaxy could not connect to their servers. I tried flashing to the Tiamat kernel and it still wouldn't connect.
So just to experiment, I flashed Kings G2 Gingerbread rom, with the stock kernel and it could connect to Audiogalaxy, but then I tried flashing the SavagedZen 0.2.0 kernel again and it couldn't connect.
I don't get it. Why would a kernel or ROM prevent me from using Audiogalaxy? I'm really scratching my head on this one and I can't figure out how to fix it. I'm using RA 2.3 to do wipes in addition to Calkulin's Format All zip file when I move between roms and always wipe cache and dalvik when flashing kernels. I don't have any other connectivity issues, just with Audiogalaxy.
Has anyone else had issues like this?
Not to sound like a smart ass, but is your pc on.... same thing happen to me. I was going crazy trying to figure it out only to find that my girl turned of my laptop....
I think the host might be blocked you need to remove the host file from your phone internal memory (this is what does the ad blocking) then connenct to audio galaxy then you can install adfree after.
Yes, the computer is on. I was sitting by it last night and trying to get my phone to access it...no luck. But like I said it works fine with Nightly 26 for me for some reason.
Also, I am not running AdFree so there can't be any hosts that are blocked. Or is it possible that there is an AdFree setting saved somewhere on my phone? I have used it before with Sense roms but never with an AOSP build. Ugh.
CM7 Does do adblocking via the hosts file. They implement it themselves. I use audiogalaxy and there are two entries in the hosts file that is defaulted with CM7. If you flash any new nightlies or RC, you will have to delete the entries again.
Also there are two of these host files, if you dont replace them both then it still wont work. One is in (Root) /etc and the other is in /system/etc.
How do I delete the hosts through CM? I haven't had to do this with RC3 or RC4 while flashing a Tiamat kernel.
Allowing ads to work on CM7
MizzouBrent said:
How do I delete the hosts through CM? I haven't had to do this with RC3 or RC4 while flashing a Tiamat kernel.
Click to expand...
Click to collapse
I am on CM7 RC4 and this is how I got Audiogalaxy to work:
1. Back up your rom.
2. First with Root Explorer make a back of host file located in etc/hosts. Doesn't hurt to back it up.
3. With Terminal Emulator, type the following:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblk3 /system
rm /etc/hosts
reboot
The first two steps are not necessary but it never hurts to be safe.
I just got my xoom back after getting the 4G LTE sim installed and the 3.2.2 version of Honeycomb.
I have rooted it again and restored my apps and data, but am stuck on a lot of things work related since there is no kernel that provides tun.ko and keeps 4g working.
Is there a kernel being built that provides tun and 4g or maybe possibly a Moray type rom that has 4g support? (That would be super sweet).
Dude the only one was in the universal root thread. If you changed kernals I think your stuck till we can get the img.
Sent from my Xoom using xda premium
I used the Universal Xoom Root process available in Development. It gave me back root access and superuser, but the kernel is still stock and lacking write access to the microsd card and tun.ko in the kernel so that IPSEC VPN connections work.
Was just searching around to see if a kernel with 4g support was in the works. Was going to use the Rogue kernel, but there is a post about waiting until it can be updated to handle 4g access.
I will just sit back and monitor the forum for an update.
The Tachi kernel is working for a few people so far. I don't live in a 4G area (VZW says it will be here next month), only work in one so I can't test the LTE yet, though the 3G works fine from my home.
I've identified a few minor annoyances and work arounds as compared to running the kernel (and Moray ROM) prior to 3.2.2 HLK75D as listed in this post:
PengLord said:
Interesting... I installed File Manager HD, enabled Root Explorer (in the settings menu) and it prompted for Root permissions. It works great. The next step in resolving this is going to be remounting the external1 device on boot to enable global write support. As I'm not so well versed in Android architecture to do that, I'll use MicroSD Mounter manually on boot.
The final step to getting this all sorted will be for me to figure out how to mount usbOTG devices, If anybody has experience with that on this kernel with a 4G Xoom, I'd very much appreciate it.
I figured out my problem with usbOTG support... I needed to added the "usbOTG" folder in the "mnt" directory using Root Explorer and then install a mount manager such as USB Mass Storage Watcher OTG
Click to expand...
Click to collapse
This will get you set up with R/W support for the external1 folder and usbOTG, VPN support may be in there as well since the kernel supports it, I however haven't tried it nor have I read about it being tested as functional on the HLK75D build.
Sadly solarnz announced he will not be working on a 4G Tiamat ROM due to life getting in the way, this means we will likely need to wait until another dev gets caught up or until ICS gets released to us by Motorola (fingers crossed for next month) before it gets any easier.
EtchG said:
I used the Universal Xoom Root process available in Development. It gave me back root access and superuser, but the kernel is still stock and lacking write access to the microsd card and tun.ko in the kernel so that IPSEC VPN connections work.
Was just searching around to see if a kernel with 4g support was in the works. Was going to use the Rogue kernel, but there is a post about waiting until it can be updated to handle 4g access.
I will just sit back and monitor the forum for an update.
Click to expand...
Click to collapse
See the arcturus kernel thread over on xoomforums... there is now an open beta for a postupgrade kernel if you want to try it
Hi Etchg,
I had a similar issue. I sent my Xoom in for the 4g update. When it came back I rooted it. Trying to vpn into work (ipsec) I found that my new kernel 2.6.36.3-g6963abe has no tun.ko file. I found some instructions online and compiled one myself. Attached is my tun.ko (You will need to unzip and put in the systems/lib/modules directory. If your kernel is exactly the same as mine then it should work. BTW, with the new tun, I have successfully VPN'd into my work.
-Jared
I just came back to this thread and saw the tun.zip you uploaded. I tried to open it, but it tells me it is corrupt.
Can you either upload it again or use dropbox and send me the link?
I was able to extract the module and load it on my Xoom. I have the same kernel, but I keep getting an authorization error when I try to connect. Darnit all to heck!
I fixed the authentication issue I was having. Thanks for the module...works like a charm.
Thanks for compiling the tun.ko. It works correctly with Cisco AnyConnect for Rooted Devices.
Glad to help
Hi Guys,
Been absent for the week. Glad to hear that you got it downloaded and working!
-Jared
This always comes back as corrupt for me. I've tried everything I can think of, but I can't extract the tun.ko out of the zip. I haven't been able to create my own either, so I'd really appreciate someone posting this.
Dear XDA-Community,
I have a lot of trouble with myGT540. At first i tried several ROMS, that didnt worked like I have expected. I found this ROM:
http://forum.xda-developers.com/showthread.php?t=1294516 --> CyanogenMod 7.2 v6 final
I installed it, everything is working but wifi not. If I install the Kernel from zices I cant enable wifi (I tried every stated solution, turn on/off use bluteooth first etc.)
Then I installed it without the kernel, I was able to enable wifi, but with the problem that was descriped in this thread.
My First Question: Is the zice Kernel only for v6?
My Second Question: I tried to fix the "usual" wifi bug (without zice) with the hints given in the thread: I downloaded the wpa_supplicant file and changed Permissions. I also changed Permission on the file located in data/etc/wifi.
I did this with root explorer and it didnt work. (I noticed after a restart the Permissions are resetted) Is root explorer the problem? Do I have to do it with adb shell?(I dont want to do this ), is there any alternative or any other solution? Perhaps some zip file to flash via recovery?
Thanks in advanced,
thecoon
I just installed ICS and it works fine. I never expected it to work as well as it does, but now I can get down to griping about little things that I use that don't yet work
Normally I use CIFS (Common Internet File System, like Samba was before) to access shares on the net. This worked fine on HoneyComb because I built my own kernel modules.
For ICS, I think the source is not yet released for the kernel. I did see that there was a tun.ko and cifs.ko for ICS over in the transformer prime section of XDA, so I tried those out but it appears the tegra 3 kernel is too different for these to work. (although I think the version is the same).
If anyone has seen or has a working cifs.ko module I'd appreciate getting ahold of it (or especially the ICS kernel source code).
Thanks -
I don't know about cifs.ko as I don't use it, but I do use OpenVPN and found out that tun is part of ICS now, you no longer need a separate module.
hachamacha said:
I just installed ICS and it works fine. I never expected it to work as well as it does, but now I can get down to griping about little things that I use that don't yet work
Normally I use CIFS (Common Internet File System, like Samba was before) to access shares on the net. This worked fine on HoneyComb because I built my own kernel modules.
For ICS, I think the source is not yet released for the kernel. I did see that there was a tun.ko and cifs.ko for ICS over in the transformer prime section of XDA, so I tried those out but it appears the tegra 3 kernel is too different for these to work. (although I think the version is the same).
If anyone has seen or has a working cifs.ko module I'd appreciate getting ahold of it (or especially the ICS kernel source code).
Thanks -
Click to expand...
Click to collapse
I didn't have much success with tun and cifs for my purpose which was to wirelessly access the sd card of the phone/tablet vice versa until I used the Samba app fom the market. In combination with Ghost commander and after upgrading to ICS everything was intact. Not sure if this is helpful to you or not. Just throwin it out there.
Thanks both of you -
I realized that tun was there but thanks. As for cifs, I suppose the module isn't really needed except to use certain utils that rely on it, like root explorer.
I found a number of samba/cifs compatible file managers that're fine for me like ES explorer etc.
Those will be fine and I'll look forward to getting kernel source for ICS anyway.
hachamacha said:
Thanks both of you -
I realized that tun was there but thanks. As for cifs, I suppose the module isn't really needed except to use certain utils that rely on it, like root explorer.
Click to expand...
Click to collapse
I've just rooted my TF101 (ICS) so that I could get Junos pulse working with its ssl vpn. Doing a bit of reading I found I needed tun.ko (at least with 3.2). That automatic tun.ko installer from the market reports that tun.ko is installed (compiled into the kernel?)
I can see the tun0 created, with an IP address. But it doesn't work, not a single bit travels the tunnel interface.
I'm officially confused...
Still too few posts under this account name to be able to post links, but have you seen this thread in Dev?
xpad / cifs modules for stock kernel ICS v9.2.1.11
Thanks for that... that confirms tun.ko is built in, which doesn't help me find/fix my problem.
Will keep at it!