Epic touch 4g - no WPA / infrastructure mode support

[GoogleCodeExporter]

Which device (manufacturer, type)? Samsung EPIC Touch 4g 

Which firmware is installed? rooted firmware

What version of wireless tether are you using? 3.1 beta 6

What steps will reproduce the problem?
1.does not support Samsung EPIC touch 4g WPA configuration.. only work in 
generic mode.. and not infrastucture mode and /or WPA configuration.
2.
3.

What is the expected output? What do you see instead?
should have a special profile for Epic touch 4g, or recommend setting to use 
for Epic touch 4g.

Please provide any additional information below.

Original issue reported on code.google.com by louis...@gmail.com on 26 Sep 2011 at 7:58

[GoogleCodeExporter]

@michaelmarcucci23:  Sorry, I had broken things, when I added the Atrix2 
profile.  So in pre112, the profile selection from the Atrix2, to the end of 
the list is one off.  From there to the end, shift one up to be on the right 
profile.  Or you can just use pre111.  I pushed my fix, so the next build 
shouldn't have this issue.  Sorry.

Also, if you continue to have the errors, go into the app settings and uncheck 
"Wifi Driver Reload".

Original comment by j...@tekahuna.net on 28 Dec 2011 at 8:45

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I've uploaded 3.1-pre113 with mentioned fixes.

Original comment by harald....@gmail.com on 28 Dec 2011 at 11:02

[GoogleCodeExporter]

I tried 3.1-pre113.  No luck even with setup on auto to enable any type of 
encryption.  I'm using the epic touch 4g setup profile, I'm still getting the 
wireless driver to freeze with the check in the box by wifi driver reload, I 
have to uncheck that and restart wireless manually.  Anyone getting 3.1-pre113 
to work with any type of encryption?  Any tips?

Original comment by knibb...@gmail.com on 29 Dec 2011 at 4:11

[GoogleCodeExporter]

I tried the pre 113. Too....this time it loads with no errors but still my 
laptop PC doesn't see network.idk if it's the laptop or the tethering.I doubt 
it because it was working fine on the evo 4g .anyway thank u in advance for the 
work u guys put in to resolve this problem.

Original comment by sghi...@gmail.com on 29 Dec 2011 at 5:54

[GoogleCodeExporter]

I tried pre 113, using samsung galaxy s2, uncked wifi driver reload to no 
available.
This app worked great on my other phone. I would love to use it again.
Anyway, thanks guys for all the work you.

Original comment by nypct...@gmail.com on 29 Dec 2011 at 6:38

[GoogleCodeExporter]

pre 113 is working with my epic 4g touch in adhoc mode with no encription.  
Trick is to manually check Setup-Method to WEXT (ad-hoc) instead of Auto. Also, 
if I try it and it fails or if I stop and restart the the tethering service, 
the only way I can get it to start again is to power cycle the phone. Was able 
to connect successfully from my laptop, another android phone, and an iphone.  
THANK YOU to the project members!  Keep up the good work.  I hope the new 
chipset issues get worked out soon.  I will donate some money.

Original comment by ggwashb...@gmail.com on 29 Dec 2011 at 7:35

[GoogleCodeExporter]

I followed the instructions outlined in Comment 107 and it worked as described. 
 Once I do turn off wifi tether I need to reboot before using it again, but 
aside from that adhoc mode seems to work fine with my MacBook, IPad, and IPod 
touch.  Pulled 100MB of data through it at about 687 mbits per sec.  Worked 
great.

Sure it's not perfect, but its enough to convince me to keep the phone and not 
go back to my Evo 4G.

Bravo gentlemen!  Donation on the way!

Original comment by freddec...@gmail.com on 30 Dec 2011 at 5:22

[GoogleCodeExporter]

#107 Works for me, too-- My eventual goal is infrastructure mode, but I donated 
a bit because I had no idea you guys had to buy the phone. (Man, I really hope 
you get enough donations to afford it AND finance the project..)

#107, upon a fresh reboot, doesn't work if you turn on encryption.  Doesn't 
work if you turn on Softap.  This's with "Epic 4G Touch" being the setting, and 
yes, doesn't work if you turn off the Wifi, then turn it back on.

Original comment by soreth...@gmail.com on 31 Dec 2011 at 4:28

[GoogleCodeExporter]

Great work by all, I've been out of the loop for awhile.  I was able to use the 
config in Comment 107 to get AdHoc working again.  Any additional logs needed 
to keep the ball rolling on this or will the same logs requested in comment 58 
still valid?

Original comment by jefba...@gmail.com on 3 Jan 2012 at 8:49

[GoogleCodeExporter]

here's the fix how to get xbox live working with android tether in general..  
http://www.youtube.com/watch?v=2abtSE0SB7g  :)

Original comment by karenchr...@gmail.com on 4 Jan 2012 at 9:59

[GoogleCodeExporter]

I have the Epic Touch 4G on stock ROM rooted version 2.3.6. Just wanted to 
share my input.  I've tried:
wireless_tether_2_0_7.apk 
wifi_tether_v3_1-beta6.apk 
wifi_tether_v3_1-beta7.apk 
wifi_tether_v3_1-beta8.apk 
wifi_tether_v3_1-beta10.apk 
wifi_tether_v3_1-pre115.apk

I have had problems with most of the betas.  Things like the phone will tether 
then when I stop, need to reset phone or simply not working at all.

From what I understand, SoftAP (which I'd guess means Soft Access Point) 
doesn't work and won't until devs get a device to test with.  If it is working, 
please let me know how and if any, what are the problems.

wireless_tether_2_0_7.apk is what I'm currently using.  The only checked boxes 
in settings are 'Vibrate on connect', 'Disable Wake-Lock' and 'Disable 
Screen-Lock'.  I can turn this on and off with out resetting the phone.

NOTE: If you get 'Tether started with errors! Please check 'Show log'.' is all 
you need to do is hit the tether button 2 times and it will start up again 
without any problems.

If anyone else has the latest betas working, could you please share your 
settings?

Thanks harald....@gmail.com and others for all your work, it's much appreciated.

Original comment by stevenb...@gmail.com on 15 Jan 2012 at 1:08

Attachments:

• SC20120114-180010.png

[GoogleCodeExporter]

Steven, 3.1b7 is the last version that worked reasonably well on my Epic 4G 
Touch (SPH-D710).  Obviously, no Infrastructure mode or encryption, but at 
least I can tether my laptop to it.

Also, I second the appreciation for the work done.

Original comment by frank.pi...@gmail.com on 17 Jan 2012 at 3:25

[GoogleCodeExporter]

i was messing around yesterday trying to get my rooted epic with wifi tether to 
allow my xoom to connect to it, and had gotten it connected at some point. both 
are on stock roms. now i cannot get infrastructure mode to work on the epic, 
and cant get the xoom to connect to it. there has to be a simple explanation to 
the issue... im pretty sure infrastructure mode started at least the first time 
after i installed wifi tether

Original comment by jcedward...@gmail.com on 19 Jan 2012 at 4:22

[GoogleCodeExporter]

Some devices have had a lot of trouble getting internet via tethering to the 
Epic Touch.  My MacBook for one, is an example.  I've even seen my Windows 
machine have problems occasionally.  One way that I found to get around these 
problems is to manually configure your devices network settings.

For instance, you can try these settings:
(These settings are while using 2.0.7 but I suspect they will work for 
additional versions.)

IP address:       192.168.2.107 <-- (you can change 107 for additional devices)
Subnet mask:      255.255.255.0 <-- (255.255.0.0 also worked)
Default gateway:  192.168.2.254 <-- (this was the default from the Epic Touch)
DNS server:       8.8.8.8       <-- (8.8.4.4 is an additional one if needed.)

Hope this helps some.

Original comment by stevenb...@gmail.com on 19 Jan 2012 at 10:12

[GoogleCodeExporter]

Betas and experimental versions try to enable infrastructure-mode by default 
(which is obviously not working).

You can still try to change "setup-method" from "auto" to "ad-hoc" in 
app-settings. This should then work like the old 2.0.x versions of the app.

Original comment by harald....@gmail.com on 19 Jan 2012 at 11:43

[GoogleCodeExporter]

Is there any real progress being made on this issue? ?

Original comment by andersen...@gmail.com on 30 Jan 2012 at 4:03

[GoogleCodeExporter]

Harald, have you or any group members managed to acquire one of these phones 
for testing purposes yet?

Original comment by joe...@gmail.com on 2 Feb 2012 at 5:01

[GoogleCodeExporter]

@joen05: Well. The epich touch 4g is (as far as I know) a galaxy s2 derivate. I 
have a galaxy s2 and made the app work on this device. I'm from europe and the 
epic touch 4g is not available here.

Original comment by harald....@gmail.com on 2 Feb 2012 at 10:43

[GoogleCodeExporter]

So does this mean we most likely wont see a fix for the epic 4g touch? My phone 
loads and runs tether with no errors but does nothing else I can start stop 
with no errors just no tehering works at all.  I am able use Barnacle and Open 
Garden fine but get errors on both of them if i try to enable any type of 
encryption.

Original comment by jons...@gmail.com on 2 Feb 2012 at 2:19

[GoogleCodeExporter]

@jonscsl: read my comment #116 ... 

NO 3rd-party-app supports infrastructure-mode for this device! NO ONE!
And ... the opengarden-"app" is a fork of this project.

Original comment by harald....@gmail.com on 2 Feb 2012 at 2:46

[GoogleCodeExporter]

@Harald, if we were able to get one to you, would you be able to run it on any 
of your networks?  I don't know if CDMA phones work in EUR.  Also, do you have 
infrastructure mode on your S2?

Original comment by joe...@gmail.com on 2 Feb 2012 at 2:51

[GoogleCodeExporter]

Yes. Infrastructure works fine on my S2 (and on other derivates but not on the 
epic touch 4g)

As far as I know ... if you chose "device-profile: auto" and "setup-method: 
netd" tethering should be started without visible error (no errors in log). The 
problem is that no wifi-signal is broadcasted - so ... something is wrong.

Well, mmmh. Could you please provide some additional information?
Start tethering (with settings described above - use the latest beta-version), 
connect to your device via adb and execute below command ...

adb shell
/data/data/com.googlecode.android.wifi.tether/bin/iwconfig

Please post the output here.

/data/data/com.googlecode.android.wifi.tether/bin/iwconfig 

Original comment by harald....@gmail.com on 2 Feb 2012 at 9:26

[GoogleCodeExporter]

Is it possible to get a hack for the sprint native hotspot just for the Epic 4g 
Touch as a workaround for this issue?

Original comment by jons...@gmail.com on 3 Feb 2012 at 1:22

[GoogleCodeExporter]

Harald, I'm a little illiterate when it comes to command line prompts... how do 
I start the adb shell in order to execute those commands?

Original comment by joe...@gmail.com on 3 Feb 2012 at 5:05

[GoogleCodeExporter]

Harald, I'm a little illiterate when it comes to command line prompts... how do 
I start the adb shell in order to execute those commands?

Original comment by joe...@gmail.com on 3 Feb 2012 at 5:05

[GoogleCodeExporter]

Harold, here is the output you asked for from joe (though this is not his 
device)

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Nick>adb shell
~ # /data/data/com.googlecode.android.wifi.tether/bin/iwconfig
/data/data/com.googlecode.android.wifi.tether/bin/iwconfig
lo        no wireless extensions.

usb0      no wireless extensions.

sit0      no wireless extensions.

ppp0      no wireless extensions.

eth0      IEEE 802.11-DS  ESSID:""  Nickname:""
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated
          Bit Rate:65 Mb/s   Tx-Power:32 dBm
          Retry min limit:7   RTS thr:off   Fragment thr:off
          Power Managementmode:All packets received
          Link Quality=5/5  Signal level=0 dBm  Noise level=0 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

~ #

Original comment by TheXsecr...@gmail.com on 3 Feb 2012 at 9:01

[GoogleCodeExporter]

Thanks TheXsecr...! I tried that from the command line with no success. :-D

Original comment by joe...@gmail.com on 3 Feb 2012 at 9:04

[GoogleCodeExporter]

Thanks. Well. So it looks like the wifi-interface can't be put into master-mode 
which is needed for infrastructure-mode. Think we are stuck at adhoc.

Original comment by harald....@gmail.com on 5 Feb 2012 at 9:21

[GoogleCodeExporter]

Gah, some of my devices just got really sad :-(

Original comment by joe...@gmail.com on 5 Feb 2012 at 3:41

[GoogleCodeExporter]

OK I have a fix But I hope it wont offend Harald or anyone else but there is a 
Sprint native hotspot hack if you have clockworkmod installed and dont mind 
flashing a hotspot mod to your stock rooted Epic 4G Touch. I did it last night 
and I am 100% happy it uses infrastructure-mode perfectly and stock usb teather 
as well.

 http://forums.acsyndicate.net/showthread.php?2992-ACS-Mod-EK02-EL13-Deodex-Odex-Hotspot-Mod-Now-With-4G

Original comment by jons...@gmail.com on 5 Feb 2012 at 4:01

[GoogleCodeExporter]

I dont want to be the person who restates the overstated obvious here but wifi 
tether isn't working. I figured that ti would be fixed in the next beta but.... 
yeah. I really would prefer to not flash another rom over touchwiz. If there is 
anything I can do to help lt me know. I am not a full blown developer but I 
know my way around android. 

Original comment by cbkoma...@gmail.com on 5 Feb 2012 at 9:32

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

It is definitely possible to have the Epic 4G Touch broadcast an 
infrastructure-mode signal -- Sprint's bundled hotspot application does so 
already, without mods.  However, without modifications, the bundled hotspot app 
will fail if you don't have a tethering SOC on your Sprint plan, or if you're 
using a Sprint MVNO that doesn't even offer tethering, like I am (CREDO, 
anyone?)

But, the only way Sprint knows whether or not you're trying to tether is that 
Sprint-compliant tethering apps use a specific network username/password for 
tethering vs. regular data access.  So, the "fix" in comment 131 is just a mod 
to bypass the tethering-specific network authentication and use the regular 
data authentication instead, thus getting around the "you're not paying for 
tethering" error.

However, I doubt that mod would work if you're not running the stock ROM -- so 
those with custom ROMs still need a fix for this app to broadcast as an 
infrastructure AP.  Again, it's possible for this phone to do it -- one just 
has to figure out how Sprint's app manages it.

Original comment by evend...@gmail.com on 5 Feb 2012 at 10:54

[GoogleCodeExporter]

I would love to use a 3rd party app for tethering as this one but I am guessing 
no one is working on this or just hasnt got this figured out yet. I will keep 
checking in on if any progress has been made.

Original comment by jons...@gmail.com on 5 Feb 2012 at 11:12

[GoogleCodeExporter]

I got it to work on my touch 4g using stock rooted rom. using 2.0.8 pre 1st 
what I did was change the SSID then enable access control. 

Then when you see the connection make sure to hit the access control screen 
select the device by tapping the checkmark. Press apply and make use of it.

Original comment by KTr...@gmail.com on 6 Feb 2012 at 6:02

[GoogleCodeExporter]

Wanted to report beta 11 works properly. Just change the device to epic 4g

Original comment by KTr...@gmail.com on 13 Feb 2012 at 7:38

[GoogleCodeExporter]

Does it only work in adhoc or did you somehow get infrastructure working?

Original comment by GhostSon...@gmail.com on 16 Feb 2012 at 12:14

[GoogleCodeExporter]

I downloaded beta11 after comment #137 and I can report that there is really no 
change. Adhoc works fine without encryption. No infrustructure at all or 
encryption.

Original comment by MrBurrit...@gmail.com on 16 Feb 2012 at 12:16

[GoogleCodeExporter]

Just did a reread of this issue...  So, things aren't looking that great for 
the ET4G.  Something I kind of want to get a clear understanding of, though....

When attempting to tether with netd, and having what appears to be a successful 
startup of tethering..  Does it broadcast an SSID, and are you able to connect 
to the AP, just no data gets passed?  Or is there no SSID or AP broacast?

If you can actually see and connect to the AP, are you able to ping the phone?

If so, try flipping to Airplane Mode, then back out of Airplane mode.  Maybe 
this will make it start passing data.  

Either way, it appears that ET4G is somewhat in the situation of the 
DroidX/Droid2/Droid3.   Where the carrier is using DUN authentication to block 
tethering access.  On DroidX/2/3, they modify the baseband to get around this.  
On ET4G, it seems they patch the system framework to get the stock APK working. 
 Unfortunately, workarounds like these fall outside the scope of this project.  

Sorry folks, looks like we need to call it, and default to adhoc.  

Original comment by j...@tekahuna.net on 17 Feb 2012 at 4:47

[GoogleCodeExporter]

When you try to start up the different modes here is what happens:
NetD= no errors however there is nothing broadcasting. I have even tried to 
sweep the 2.4ghz range and there is nothing there. (encryption on/off does not 
change the outcome).
softap= shows errors. "Config softap", "start softap", "activate wifi int." all 
fail. (encryption on/off dows not change outcome).
adhoc= starts and runs fine without encryption, turn on encryption and 
"Activating Encription" will fail.

From what I have read about the ET4G it seems to have a different network 
chipset than what is typically used in most phones would this matter for the 
software to interface with? It seems that up until a few posts ago some people 
were still under the impression that the ET4G was just a galaxyS2 in disguise 
however it has a completely different network chipset.

Just thought I would throw that out there.

Original comment by MrBurrit...@gmail.com on 18 Feb 2012 at 1:04

[GoogleCodeExporter]

I dont know about ad-hoc mode and all this other stuff but if you install 
wireless_tether_2_0_7 the app works fibe without any setting changes. If it 
says started with errors just hit the off switch wait til it turns back green 
and then turn it back on and from tgere 3g and 4g tether fine. What has changed 
since 2.xx to make it so complicated now?

Original comment by riff@iap-tv.com on 20 Feb 2012 at 2:28

[GoogleCodeExporter]

Maybe read the topic title before commenting on the situation riff

Original comment by envy...@gmail.com on 20 Feb 2012 at 3:32

[GoogleCodeExporter]

I did but maybe I didn't elaborate. Ever since the 3.xx versions I can't get 
this app to tether at all no matter what settings I use. Wext mode or changing 
the device from default to the epic touch or sgs2 none of these settings work 
on my device but the version I mentioned works with the default settings and I 
can set up encryption envy.

Original comment by riff@iap-tv.com on 21 Feb 2012 at 5:28

[GoogleCodeExporter]

I'm running 1.0 kbs if im lucky...what power in mghz should I be set a and what 
channel? Because this sucks

Original comment by ryanfran...@gmail.com on 21 Feb 2012 at 6:30

[GoogleCodeExporter]

I would like to add that version 2.0.7 worked for me Ad Hoc with no security 
whereas the beta 11 absolutely would not broadcast.

Original comment by franklin...@gmail.com on 22 Feb 2012 at 1:48

[GoogleCodeExporter]

Same here. 2.07 works in ad hockey where I couldn't get any other version
to work.

Original comment by michael....@gmail.com on 22 Feb 2012 at 2:14

[GoogleCodeExporter]

Epic Touch 4g - running Android 2.3.6 kernel is 2.6.35.14-rogue_ET-1.5.0+ Build 
is GINGERBREAD.EL29 and Hardware version is D710.10. With the latest beta 
version Wifi does not connect to PC or any other android device.

Original comment by npbeni...@gmail.com on 14 Apr 2012 at 6:07

[GoogleCodeExporter]

Go to the Play Store and download    FoxFi   its a free WiFi Tether app that 
works on rooted and non rooted phones. It works exactly like Sprint native 
Hotspot. Its the best!!!!

Original comment by jons...@gmail.com on 14 Apr 2012 at 6:28

[GoogleCodeExporter]

Correction  Sprint removed it from the Play Store so you will have to go to     
 http://foxfi.com/bin

Original comment by jons...@gmail.com on 14 Apr 2012 at 6:32