Infrastructure Mode on Motorola Triumph

[GoogleCodeExporter]

Which device (manufacturer, type)?
Motorola Triumph

Which firmware is installed?
Android version 2.2.2
Rooted with GingerBreak 1.2

What version of wireless tether are you using?
3.1-beta2

What steps will reproduce the problem?
1. Did not find a profile that would put the Motorola Triumph into 
infrastructure mode.
2. Phone reboots if I try a profile using "Netd (master)"
3. Log shows errors if I try a profile using "Softap (master)"
4. Log shows errors if I try a profile using "Hostapd (master)"

What is the expected output? What do you see instead?
Expect WiFi Tether to start AP in infrastructure. Expect netbook to detect an 
infrastructure AP. Expect Motorola Xoom to see the AP.

Please provide any additional information below.
I posted a message in issue 11 regarding this issue. But now, I'm thinking it 
should be tracked separately for the Motorola Triumph, because infrastructure 
mode is already working on a number of other phones.

I have the Motorola Triumph. Feel free to let me know if I can provide any 
information from the phone that you may need.

Original issue reported on code.google.com by gypsy3...@yahoo.com on 20 Jul 2011 at 8:51

[GoogleCodeExporter]

Does it work at all in ad-hoc mode?

Original comment by legendm...@gmail.com on 22 Jul 2011 at 12:07

[GoogleCodeExporter]

I am able to connect to the phone via ad-hoc mode on my netbook, but my phone 
is not activated, so I can't test the routing/NAT. I've outlined my experience 
in this thread:
http://www.gearhack.com/Forums/DisplayComments.php?file=Electronics/Phone/Wirele
ss_Tether_with_Motorola_Triumph.

However, someone else, who has activated their phone wrote the following 
passage in this thread:
http://www.howardforums.com/showthread.php/1724977-Motorola-Triumph-Wifi-Hotspot
-Tethering/page2

"...................... Just wondering how many people have actually analysed 
the packets? Clearly with android-wifi-tether 3.1beta 2 or 3.0 pre14, DHCP is 
not working so the client cann't automatically configure ip address. Just set 
the client to 192.168.2.200 mask 255.255.255.0 gateway 192.168.2.254 dns 
8.8.8.8 , 4.2.2.4

"I am able to use non-http(like ftp) or Google http services(gmail, reader, 
utube) on my laptop, and even stock weather/stock on iphone but for other 
websites I get so many TCP RST/Tetransmission(because of no/slow TCP respond). 
Not sure what's causing the problem. Probably bug in android tether.

"I don't get why some people blame hardware for this........ Pretty much all 
WiFi devices can "tether"(Just like ICS in Windows)? Sure there can be software 
issues(firmware, driver, application, OS) but hopefully those can be fixed if 
someone decides to do it......."

Original comment by gypsy3...@yahoo.com on 22 Jul 2011 at 1:10

[GoogleCodeExporter]

"...................... Just wondering how many people have actually analysed 
the packets? Clearly with android-wifi-tether 3.1beta 2 or 3.0 pre14, DHCP is 
not working so the client cann't automatically configure ip address. Just set 
the client to 192.168.2.200 mask 255.255.255.0 gateway 192.168.2.254 dns 
8.8.8.8 , 4.2.2.4"

Not true. I test all version with 3 different android-phones (sorry, I'm not 
able to test it on about 200 phone/android-combinations) and it's working for 
me. If it doesn't work for you ... the wifi-interface on your mobile couldn't 
bet set-up correctly.

"I am able to use non-http(like ftp) or Google http services(gmail, reader, 
utube) on my laptop, and even stock weather/stock on iphone but for other 
websites I get so many TCP RST/Tetransmission(because of no/slow TCP respond). 
Not sure what's causing the problem. Probably bug in android tether."

Can't be a bug. Looks like your carrier is detecting NAT and filters all 
non-google sites. You could try to change dns to the one your carrier is using 
in general. But I doubt it will help.

"I don't get why some people blame hardware for this........ Pretty much all 
WiFi devices can "tether"(Just like ICS in Windows)? Sure there can be software 
issues(firmware, driver, application, OS) but hopefully those can be fixed if 
someone decides to do it......."

Some intel-based wifi-cards (especially under win7) have problems with adhoc. 
Check: http://code.google.com/p/android-wifi-tether/issues/detail?id=244

Anyways. With 3.1b2 which device-profiles have you tried?

Original comment by harald....@gmail.com on 22 Jul 2011 at 3:46

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

> Anyways. With 3.1b2 which device-profiles have you tried?

For infrastructure mode, I've tried the following device-profiles:
Google NexusOne
HTC Desire (GSM)
HTC Desire (CDMA)
HTC Evo 4G
HTC Thunderbolt
Samsung Galaxy S
ZTE Blade

Original comment by gypsy3...@yahoo.com on 22 Jul 2011 at 6:00

[GoogleCodeExporter]

There was a change in condition. While I was coming up with the list in the 
comment above, I thought "Samsung Galaxy S" wasn't a familiar profile and I 
didn't see it before.

So I played with it to "Samsung Galaxy S" and set "Netd (master)". On enabling 
tethering, the phone did NOT reboot. Instead, the only error in the log is this 
one:
"Activating WiFi interface..." failed.

I was able to connect my Samsung Intercept Android phone to it. However, it 
could not obtain address automatically. But once I set static IP to 
"192.168.2.23" "192.168.2.254" "255.255.255.0" "4.2.2.4" "4.2.2.5" on the 
Samsung Intercept, it connected to the Motorola Triumph.

Surprised, I disabled tether again. Then I set the profile to "Google NexusOne" 
and "Netd (master)". I enabled tether and was once again successful with the 
same error in the log. The phone again did not reboot.

I don't know what changed. But this is encouraging. I'm going to activate the 
Motorola Triumph on the VM service now and see if it really works.

Original comment by gypsy3...@yahoo.com on 22 Jul 2011 at 6:07

[GoogleCodeExporter]

One other thing before I forget . . . Once the phone sleeps in this mode, I 
can't turn the phone back on again. Only way to resolve it is to remove the 
battery and turn the phone on again.

That was with "Disable Wake-Lock" enabled. I unchecked that item and hasn't 
experienced problems yet.

This may be a separate bug/issue, but it's related to my experiment, so I'll 
leave it here for now.

Original comment by gypsy3...@yahoo.com on 22 Jul 2011 at 6:18

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have now activated the Motorola Triumph on Virgin Mobile's network. Tonight, 
I started the tethering mode. My Motorola Xoom sees the infrastructure AP. 
However, when it attempts to connect, it could not get an address via DHCP.

I manually configured these settings on the Xoom: "192.168.2.25" 
"192.168.2.254" "24" "4.2.2.4" "4.2.2.5". The Xoom connected. Under "Access 
Control", it doesn't show any connected/authorized clients.

I could not get to any web site on the Xoom using this tethered connection.

Original comment by gypsy3...@yahoo.com on 23 Jul 2011 at 5:37

[GoogleCodeExporter]

I'd like to see this work. I had a dreadful experience with vm intercept, but i 
was able to get tethering functionality. I would hate to of had dropped $319.49 
for nothing, it's a beautiful phone, but I do need this convenient 
functionality. I'd hate to give my money to the big bullies ATT or VRZN.

Original comment by sirluism...@gmail.com on 9 Aug 2011 at 10:36

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

For the Devs,

Check this page of out 
http://www.howardforums.com/showthread.php/1724977-Motorola-Triumph-Wifi-Hotspot
-Tethering/page9

Seems folks are finding problems with MTU settings that is causing the Motorala 
Triumph (MT) from tethering properly.  These guys are on a roll over there and 
could be some useful information to help create a MT profile for Wifi Tether.

Original comment by jedgell...@gmail.com on 10 Aug 2011 at 9:17