mmorciegov / android-wifi-tether

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

Semi works #1424

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Which device (manufacturer, type)?
Samsung SGH-i727(Skyrocket)

Which firmware is installed?
Sky-ICS(Android 2.3.5) V7.4 "Stock"

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

What steps will reproduce the problem?
1.Varying the "Device-Profile"

What is the expected output? What do you see instead?

Finally decided to try a different kernel and ROM, had similar issues on stock 
but assumed it was because I was using stock ROM and just didn't worry about 
it. Anyhow here's the results of my testing on a Skyrocket device with 
different ROM:
===Defaults===
Litterally just installed and opened the app(Device-Profile set to "Auto"), 
then tried to start tethering.
Log Shows:
 Loading WiFi driver... [failed]
 Setting ad-hoc mode... [failed]
 Setting essid... [failed]
 Setting channel... [failed]
Computer detects:
 AndroidTether in AP mode, but unable to connect by computer(just says connection fails)

===Device-profile:Samsung Galaxy S2[GT-I9100]===
Log Shows:
 Loading WiFi driver... [failed](On first try, [done] after second, i'll explain below)
Computer detects:
 AndroidTether in AP mode, connects no problem, gets IP.
 Not sure why, but I have to start/stop/start tethering in order for the connection to succeed, it also appears that the 'loading wifi driver' stage doesn't normally work the first time.
 A couple times, despite not having download/upload stats on screen and it saying 'loading wifi driver' has failed, I've still been able to connect to the wifi network and access the internet. But this varies.

Please provide any additional information below.
I mentioned similar issues earlier. When I tried this the first time around on 
stock using beta10, it didn't matter what device-profile i used, i got a 
mixture of wifi driver failing, to not being able to set ad-hoc(seems like the 
most common)

Happy it seems to be working, feel free to email me if you need a tester on the 
Skyrocket device.

Original issue reported on code.google.com by maedond...@gmail.com on 15 Feb 2012 at 3:46

GoogleCodeExporter commented 9 years ago
Additional notes:
 Also noticed my computer is only able to 'connect' at 802.11b(11mbps) speeds, not sure if there's anything out there to help that or not. My computer at the very least supports wifi-g so i'm thinking the driver on the phone is getting stuck in wifi-b mode? just a thought.

Original comment by maedond...@gmail.com on 15 Feb 2012 at 3:48

GoogleCodeExporter commented 9 years ago
Upgraded phone to ICS leak(4.0.3).

Nothing seemed to work this time around with Beta11. Auto/Galaxy S2/Galaxy 
SL/Epic 4G Touch all don't work and report the same failures as I previously 
posted.

Seem to be able to fix the issues when I set the device setting in the menu to 
"Samsung Galaxy Nesus (CDMA/LTE)" or "toro" as the toast notification claims it 
to be.

Original comment by maedond...@gmail.com on 8 Apr 2012 at 7:30