search

MEAM-Ware / android-wifi-tether

Automatically exported from code.google.com/p/android-wifi-tether
0 stars 0 forks source link

Epic touch 4g - no WPA / infrastructure mode support #1161

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
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 commented 9 years ago 
The problem I am experiencing is not the same one as others have described.  I 
am able to get an ad-hoc connection to my laptop (and have in fact used an 
ad-hoc connection to tether my laptop to my older HTC Touch Pro 2 with no 
issues).  Here, even though it says I am connected, and the laptop has a valid 
DHCP address, I am only able to ping websites and do stuff through the command 
prompt, but all HTTP requests through IE result in timeout. I will obviously be 
patient hoping that the devs obtain a platform to test on, but simply adding 
infrastructure support is not the solution to my problem (as again, I have 
previously used an ad-hoc tether, albeit it one with WEP, with this same 
laptop).

Original comment by jatog...@gmail.com on 13 Dec 2011 at 1:46

GoogleCodeExporter commented 9 years ago 
Could you please try today's pre108 build? 
http://android-wifi-tether.googlecode.com/files/wifi_tether_v3_1-pre108.apk ... 
 If it doesn't auto detect...  try Galaxy S2 profile...  Thanks!

Original comment by j...@tekahuna.net on 13 Dec 2011 at 2:03

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Tried the build listed in Comment 52, auto still loads up in AdHoc mode 
(confirmed in log).  Selecting Galaxy S2 profile failed at Configuring softap, 
Starting softap, and Activating Wifi interface.

Any logs that might be helpful? dmesg or logcat?

Original comment by jefba...@gmail.com on 13 Dec 2011 at 1:32

GoogleCodeExporter commented 9 years ago 
For those with internet access issues after adhoc. Please test packet size/mtu. 
Try smaller numbers until you get timeouts/loss in your cmd prmt.

Original comment by DShin...@gmail.com on 13 Dec 2011 at 1:43

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I am using a Sprint/Samsung Epic 4G as well.  I have it working fine using the 
AdHoc mode with multiple laptops.  I've downloaded this pre108 build and tried 
to get it to work with in infrastructure mode with no success.  Tried mult 
device profiles (Auto, Generic, Samsung Epic 4G, Samsung Galaxy S).  Tried both 
Auto and Sotap for Samsung Setup-Methods.  What else should I try?   (I'm 
trying to connect from my Acer ICONIA A500 and a rooted Android HP Touchpad.)

Original comment by clif...@gmail.com on 13 Dec 2011 at 4:49

GoogleCodeExporter commented 9 years ago 
@jefbal99 We definately need logs as we have no device on hand to test with.

pre108 was an attempt at getting SoftAP working...  Samsung Galaxy S2 is the 
profile the changes were made under.  Pretty sure none of the others will 
magically work in Infrastructure mode.

So:

1. go into settings, select the Galaxy S2 Profile, and change the method to 
softap
2. Start tethering from the Application
3. From Terminal or ADB(Charge Only Mode, so you have sdcard access) enter the 
following commands:
$ su
# mkdir /sdcard/tetherlog
# logcat > /sdcard/tetherlog/pre108_sgs2_logcat.log
# dmesg > /sdcard/tetherlog/pre108_sgs2_dmesg.log
# cp /data/data/com.googlecode.android.wifi.tether/conf/tether.conf 
/sdcard/tetherlog/pre108_sgs2_tether.conf
# cp /data/data/com.googlecode.android.wifi.tether/conf/tether.edify 
/sdcard/tetherlog/pre108_sgs2_tether.edify

4. Now go back to the application and Stop tethering

5. Go back to Terminal/ADB and do the following
# cd /data/data/com.googlecode.android.wifi.tether/bin
# ./tether start > /sdcard/tetherlog/pre108_sgs2_tether_start.log

When you're done, upload the files located in /sdcard/tetherlog here.

We also need to verify that "/system/vendor/firmware/bcm4330_aps.bin" exists on 
these phones...

I'm new to the project, and this is the first time I'm poking at SoftAP.  
Harald just turned me on to this situation, so I need to soak up some of the 
background info before I can give real quality input.  Broadcom changed 
something going from the 4329 chipset found in the Galaxy S, to the 4330 found 
in the Galaxy S2/Nexus in how their SoftAP setup works.  What exactly, not 
sure...  I'm optimistic, though..

Aloha

Original comment by j...@tekahuna.net on 13 Dec 2011 at 6:27

GoogleCodeExporter commented 9 years ago 
Great stuff, I have a rooted SGS2 E4GT that replaced my rooted EVO (worked
just fine with wifi tether). i could not connect to my dell precision
laptop w/ adhoc tether from the E4GT. updated the broadcom drivers on the
laptop as suggested somewhere here and it connected and worked! just got an
android Toshiba tablet and it does not see the phone. i will give sprint my
30 bucks a month until i can get that problem figured out. thanks to the
dev guys.

Original comment by jba...@gmail.com on 13 Dec 2011 at 6:55

GoogleCodeExporter commented 9 years ago 
Just to be clear, there is no work being done for the Epic 4G (Galaxy S) to get 
it to work in infrastructure mode?

Original comment by clif...@gmail.com on 13 Dec 2011 at 7:32

GoogleCodeExporter commented 9 years ago 
Only adhoc-mode seems to work currently. Please follow the instruction 
(http://code.google.com/p/android-wifi-tether/issues/detail?id=1161#c58) posted 
by tekahuna.

Thanks.

Original comment by harald....@gmail.com on 13 Dec 2011 at 8:06

GoogleCodeExporter commented 9 years ago 
Yes, I have ad-hoc working perfectly on the Epic 4G.  Of course I cannot tether 
my tablets (without rooting them).  Is there any work being done currently to 
get infrastructure working on the Epic 4G?  If yes, can I help by providing 
logs?  Thanks.

Original comment by clif...@gmail.com on 13 Dec 2011 at 8:14

GoogleCodeExporter commented 9 years ago 
@cliffup

Sorry, I wasn't clear in my previous posts.  SoftAP is the method in which we 
are trying to get SGS2 devices to do Infrastructure/AP mode.

Original comment by j...@tekahuna.net on 13 Dec 2011 at 8:20

GoogleCodeExporter commented 9 years ago 
@ad...@tekahuna.net

Understood.  I'm wondering whether there are any plans to do the same for the 
SGS (Epic 4G)?

Original comment by clif...@gmail.com on 13 Dec 2011 at 8:32

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
BTW, we need someone pull and upload this file from their Epic 4G: 

/system/build.prop

Original comment by j...@tekahuna.net on 13 Dec 2011 at 9:01

GoogleCodeExporter commented 9 years ago 
Here's build.prop for the recent OTA update: http://pastebin.com/NGbankPb

Original comment by r...@nonforma.com on 14 Dec 2011 at 7:32

GoogleCodeExporter commented 9 years ago 
This is the build.prop file from the Samsung EPIC 4G

Original comment by clif...@gmail.com on 14 Dec 2011 at 9:14

Attachments:

GoogleCodeExporter commented 9 years ago 
@cliffup

Thanks for the build.prop...  As I don't have these devices, I was not aware 
that the Epic 4G and Epic Touch 4G are two different devices.    Epic 4G seems 
to be a problem device from what I could find.  Since this thread is addressing 
a different phone with a different chipset, could you please post your finding 
in the thread below that is addressing Infrastructure mode on Epic 4G 
specifically.  I actually believe your should be supported already.  
Regardless, issue 946 is a better place to address this, cause if things get 
difficult for us on the Epic Touch 4G, this place could get messy. Thanks!

http://code.google.com/p/android-wifi-tether/issues/detail?id=946&can=1&q=epic%2
04g%20infrastructure

@ryan

Thanks for the build.prop as well!

Aloha

Original comment by j...@tekahuna.net on 14 Dec 2011 at 10:07

GoogleCodeExporter commented 9 years ago 
@ Message 58

Below are the requested files.

Original comment by MrBurrit...@gmail.com on 15 Dec 2011 at 1:14

Attachments:

GoogleCodeExporter commented 9 years ago 
Awesome project, maybe changes to Galaxy S2 profile can eventually be moved 
into a separate profile for the Epic touch 4g (sprint version) (also a S2 but 
slightly different)  Need the model to be specific to Samsung D710 rather than 
D700.  I'm sure developer is aware of this difference.

Original comment by knibb...@gmail.com on 15 Dec 2011 at 3:54

GoogleCodeExporter commented 9 years ago 
> We also need to verify that "/system/vendor/firmware/bcm4330_aps.bin" exists 
on these phones...

That file is found under /etc/wifi for Epic 4G Touch.

ls -l /etc/wifi/bcm*
-rw-r--r-- root     root       179349 2011-07-30 07:53 bcm4330_aps.bin
-rw-r--r-- root     root       198591 2011-07-30 07:53 bcm4330_mfg.bin
-rw-r--r-- root     root       193482 2011-07-30 07:53 bcm4330_mfg.bin_b0
-rw-r--r-- root     root       213690 2011-07-30 07:53 bcm4330_sta.bin
-rw-r--r-- root     root       213133 2011-07-30 07:53 bcm4330_sta.bin_b0

Original comment by hubs...@gmail.com on 17 Dec 2011 at 8:47

GoogleCodeExporter commented 9 years ago 
All the files are there in the location stated above.

Original comment by andre.si...@gmail.com on 17 Dec 2011 at 8:30

GoogleCodeExporter commented 9 years ago 
I can also confirm that those files are present.

Original comment by MrBurrit...@gmail.com on 18 Dec 2011 at 9:51

GoogleCodeExporter commented 9 years ago 
was excited to see the new release gave epic touch 4g a profile. but log shows, 
still failing to start softap!

Original comment by envy...@gmail.com on 18 Dec 2011 at 8:24

GoogleCodeExporter commented 9 years ago 
ehh... epic touch 4g still not wokring on wep???sigh...

Original comment by Ibeen...@gmail.com on 19 Dec 2011 at 1:55

GoogleCodeExporter commented 9 years ago 
still not working.
same error
hmmmmm??

Original comment by Ibeen...@gmail.com on 19 Dec 2011 at 2:03

GoogleCodeExporter commented 9 years ago 
Great that a 4g touch specific profile was added... But still only works in 
adhoc mode.

Please someone fix this.

Original comment by ch...@barricades.net on 20 Dec 2011 at 3:50

GoogleCodeExporter commented 9 years ago 
beta 9, I too am only able to ad-hoc and can't tether to my hp touchpad. I 
recieve the message "Tethering with errors, Please check 'Show Log'." and in my 
show log three items says failed.

Original comment by michaelm...@gmail.com on 22 Dec 2011 at 1:49

Attachments:

GoogleCodeExporter commented 9 years ago 
I'm going to buy a similiar phone. It's a NO-go here without having a phone for 
testing. (This phone has a new broadcom-wifi-chip).

Please be patient - I do what I can.

Original comment by harald....@gmail.com on 22 Dec 2011 at 8:37

GoogleCodeExporter commented 9 years ago 
Harald.  Your work is much appreciated.

Original comment by frrethym...@gmail.com on 22 Dec 2011 at 1:57

GoogleCodeExporter commented 9 years ago 
Harald, there are a lot more people who haven't been commenting who also really 
appreciate what you are doing.

Original comment by gblinckm...@gmail.com on 22 Dec 2011 at 2:37

GoogleCodeExporter commented 9 years ago 
EPIC 4G Touch with 2.3.6 

New issue with Beta9 - the forced Wifi driver reload seems to cause problems. 
It seems to require a reboot or disabling "Force wifi driver reload", to get 
even adhoc to work.   

Adhoc - works
Softap - fails to configure & start softap, then fails to activate wifi 
interface. 
Netd - fails to activate wifi interface

Original comment by chrisf6...@gmail.com on 22 Dec 2011 at 2:57

Attachments:

GoogleCodeExporter commented 9 years ago 
If you would like any files off of my phone please let me know.

Original comment by chrisf6...@gmail.com on 22 Dec 2011 at 2:59

GoogleCodeExporter commented 9 years ago 
Beta 8 worked for me in ad hoc with NO encryption (couldn't find a way around 
that) using the specific profile for epic 4g touch.  Went to Beta 9 and 
couldn't get adhoc to work at all without errors (with encryption set to off) 
had to go back to Beta 8.  I can use it this way, just would be nice someday to 
have encryption option working.

Original comment by knibb...@gmail.com on 22 Dec 2011 at 5:59

GoogleCodeExporter commented 9 years ago 
Beta 9 really should have been called experimental it broke nearly every  
thing.  In fact even beta 8 seems to be buggier, even after uninstalling the 
beta 9.  

 TIP: dont install Beta 9 on Epic 4G Touch

Original comment by ch...@barricades.net on 23 Dec 2011 at 6:55

GoogleCodeExporter commented 9 years ago 
@chris:  You're right, in beta 8 & 9, support for SGS2/Epic Touch 4G is in a 
sorry state.  They were geared more towards putting a working configuration for 
Galaxy Nexus out.  Folks with that device were chomping at the bit to get 
tether working, and poured out a load of info, and really helped to get things 
going.  We learned a lot from the GNEX port, which hopefully helps out with 
SGS2 & ET4G..  Please try pre111.

http://android-wifi-tether.googlecode.com/files/wifi_tether_v3_1-pre111.apk

If no dice, it would help to get a Screenshot of the tether log like in Comment 
#79, so we can see where we're failing now.  It would also help to have output 
from dmesg, ifconfig, and iwconfig as well.

P.S.  It was me, not Harald who mangled the SGS2/Epic Touch 4G profiles in Beta 
8/9.  Sorry, folks.

Original comment by j...@tekahuna.net on 23 Dec 2011 at 7:24

GoogleCodeExporter commented 9 years ago 
Where are dmesg, ifconfig, and iwconfig located?   

I'll test 111 & post screenshots & files.   

I can tell you that 111 & Beta 9 mess up the wifi.   Where often after shutting 
down the app, wifi completely gets broken and says error when you attempt to 
turn it on.   Reboot seems to be required to get wifi working again at all.

Original comment by chrisf6...@gmail.com on 24 Dec 2011 at 4:32

GoogleCodeExporter commented 9 years ago 
Phone = SGE4GT, Build = 2.3.6
Working, but in ad-hoc mode and unable to change SSID or turn on encryption.  
Let me know if any logs are needed to fix this.  Thanks a million for one 
creating this and your continued work on it.

Original comment by timothyb...@gmail.com on 26 Dec 2011 at 3:50

GoogleCodeExporter commented 9 years ago 
Like tekahuna mentioned in his post ... try version 3.1-pre111 (or pre 112) and 
uncheck "Wifi driver reload" in app-settings.

Original comment by harald....@gmail.com on 26 Dec 2011 at 9:26

GoogleCodeExporter commented 9 years ago 
in v3_1-pre112 version

need correction

at device-profile

samsung epic 4g and samsung epic touch 4g profile are swapped..

if you select samsung epic 4g, you will see the name of epic 4g touch(i710)

any1 having trouble getting wifi encryption!?!?!??

just select profile as epic 4g not epic 4g touch

works like charm!!! :) 

GJ

Original comment by Ibeen...@gmail.com on 27 Dec 2011 at 3:17

GoogleCodeExporter commented 9 years ago 
YES!   pre112 seems to be working for infrastructure!!!

Original comment by ch...@barricades.net on 27 Dec 2011 at 4:43

GoogleCodeExporter commented 9 years ago 
sigh i was wrong. not wokring at all.
in setup mode, only Netd(master) works, not WEXT nor Softap
therefore,wifi encryption does not still work.
no error massages, but not working.
trying to connect my house wifi from phone, and tethering download and upload 
are 0
also don see my tethering in non of my devices.

Original comment by Ibeen...@gmail.com on 27 Dec 2011 at 5:14

GoogleCodeExporter commented 9 years ago 
Darn, I saw that there were no errors in the log, so I assumed it worked.   I 
did not actually have a device at work to test it with.   It did show 0kb for 
up&down, so I guess maybe its not working!! :(

Original comment by ch...@barricades.net on 27 Dec 2011 at 5:26

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Wrong thread!    Epic 4G Touch  information only please.

Original comment by ch...@barricades.net on 27 Dec 2011 at 6:07

GoogleCodeExporter commented 9 years ago 
Using pre112. The issue serbs to  be trouble loading the wifi driver,  even 
when it says it is successful it is not. On my brothers epic 4g d700 as soon as 
you initiate the wifi an icon in the notification bar appears only momentarily 
saying," hotspot activated" if you have a test unit look for a similar icon in 
te the notification bar. I an using the device profile for d710 mistakenly 
called epic 4g while epic touch 4g , d500 which is actually a low end non 
smartphone.tried in all modes except adhoc posting images with names

Original comment by michaelm...@gmail.com on 28 Dec 2011 at 5:14

Attachments:

GoogleCodeExporter commented 9 years ago 
confirmed working. you have to pick the profile samsung galaxy s2 at the 
bottom. works great. GFJ!!!

Original comment by mike61...@gmail.com on 28 Dec 2011 at 6:39

GoogleCodeExporter commented 9 years ago 
Does anyone else notice that the device profile is saying it is set to the 
profile model number if 
the device directly below it.example: the last two are the galaxy sl and the 
last one its the blade.when you click on the galaxy sl it says you have chosen 
the profile for the "blade" and when you click on the blade itself it force 
closes the app

Original comment by michaelm...@gmail.com on 28 Dec 2011 at 3:42

GoogleCodeExporter commented 9 years ago 
Can anyone else confirm that the pre 112 version is working in infrastructure 
mode?

Original comment by joe...@gmail.com on 28 Dec 2011 at 3:58