ASUS Eee Pad transformer

I think you confused on the issue.

Android could never connect to Ad-Hoc networks because of security issues(Unless you root). It could how ever creat hot-spots but ones that worked properly with the security layer intact. As for your wi-fi tether app, it simply has not been updated to deal with the new Linux kernel changes in regaurd to WiFi, to be more to the point it has no support for WiFi Direct and probibly needs the developer to play catch up.
I am really confused about the Ad-Hoc issue with Andriod. The above app is running from my phone (rooted; stock froyo) and is still operational. From the app page in the market:
Wifi-tethering creates a so called adhoc (peer-to-peer) network on most devices.

Sine upgrading to ICS I can no longer connect to the hotspot from my TF101.

Some other users indicate that ICS broke ad-hoc: http://www.transformerforums.com/fo...ns/16366-tf101-ics-adhoc-phone-tethering.html

Can anyone recommend a good Wireless Tether app for my Android phone?

The reason I preferred "Wireless Tether" was that it showed how much bandwidth you used and had good access control.
 
Last edited:
I am really confused about the Ad-Hoc issue with Andriod. The above app is running from my phone (rooted; stock froyo) and is still operational. From the app page in the market:

Sine upgrading to ICS I can no longer connect to the hotspot from my TF101.

Some other users indicate that ICS broke ad-hoc: http://www.transformerforums.com/fo...ns/16366-tf101-ics-adhoc-phone-tethering.html

Can anyone recommend a good Wireless Tether app for my Android phone?

The reason I preferred "Wireless Tether" was that it showed how much bandwidth you used and had good access control.

Ok 1st off what are you using to connect to the Internet?
Internet -> phone -> tablet?

Where is the tether app installed?
On the phone?
 
Yes phone.
Internet -> phone -> tablet
(app installed on phone, app creates wifi hotspot, connect to hotspot from Tab)

The tablet could always connect to the hotspot created by this app, it has some pretty cool features ( you can set the IP range; alert you when a user connects, had the battery temp, etc.)

BTW I remember reading that someone said that a firmware update (honeycomb) allowed one to connect to a ad-hoc wifi: http://forum.xda-developers.com/showthread.php?t=1053752&page=8

Also I remember that a Archos G9 (Honeycomb) tablet would not connect to the App's hotspot but the Transformer could. I figured this was to do with ad-hoc wifi support in the different firmwares.
 
Last edited:
I have installed the 'CWM package for ASUS TF101 FOTA 9.2.1.11 WW' ROM over my RevolutionHD.
Everything is fine.

However.

I was under the impression that I would be able to use my 3G dongle with Android 4.
But my USB stick doesn't even get recognized!

All my memory sticks work fine. Tested a number of 1080p movies from it.

Is there any way for me to get my CellC stick to work?
 
Yes phone.
Internet -> phone -> tablet

The tablet could always connect to the hotspot created by this app, it has some pretty cool features ( you can set the IP range; alert you when a user connects, had the batter temp, etc.)

Ok then tell the app creater he needs to fix the app.

Wi-Fi Direct

Android now supports Wi-Fi Direct for peer-to-peer (P2P) connections between Android-powered devices and other device types without a hotspot or Internet connection. The Android framework provides a set of Wi-Fi P2P APIs that allow you to discover and connect to other devices when each device supports Wi-Fi Direct, then communicate over a speedy connection across distances much longer than a Bluetooth connection.

A new package, android.net.wifi.p2p, contains all the APIs for performing peer-to-peer connections with Wi-Fi. The primary class you need to work with is WifiP2pManager, which you can acquire by calling getSystemService(WIFI_P2P_SERVICE). The WifiP2pManager includes APIs that allow you to:

  • Initialize your application for P2P connections by calling initialize()
  • Discover nearby devices by calling discoverPeers()
  • Start a P2P connection by calling connect()
  • And more

Several other interfaces and classes are necessary as well, such as:

  • The WifiP2pManager.ActionListener interface allows you to receive callbacks when an operation such as discovering peers or connecting to them succeeds or fails.
  • WifiP2pManager.PeerListListener interface allows you to receive information about discovered peers. The callback provides a WifiP2pDeviceList, from which you can retrieve a WifiP2pDevice object for each device within range and get information such as the device name, address, device type, the WPS configurations the device supports, and more.
  • The WifiP2pManager.GroupInfoListener interface allows you to receive information about a P2P group. The callback provides a WifiP2pGroup object, which provides group information such as the owner, the network name, and passphrase.
  • WifiP2pManager.ConnectionInfoListener interface allows you to receive information about the current connection. The callback provides a WifiP2pInfo object, which has information such as whether a group has been formed and who is the group owner.

In order to use the Wi-Fi P2P APIs, your app must request the following user permissions:

  • ACCESS_WIFI_STATE
  • CHANGE_WIFI_STATE
  • INTERNET (although your app doesn’t technically connect to the Internet, communicating to Wi-Fi Direct peers with standard java sockets requires Internet permission).

The Android system also broadcasts several different actions during certain Wi-Fi P2P events:

  • WIFI_P2P_CONNECTION_CHANGED_ACTION: The P2P connection state has changed. This carries EXTRA_WIFI_P2P_INFO with a WifiP2pInfo object and EXTRA_NETWORK_INFO with a NetworkInfo object.
  • WIFI_P2P_STATE_CHANGED_ACTION: The P2P state has changed between enabled and disabled. It carries EXTRA_WIFI_STATE with either WIFI_P2P_STATE_DISABLED or WIFI_P2P_STATE_ENABLED
  • WIFI_P2P_PEERS_CHANGED_ACTION: The list of peer devices has changed.
  • WIFI_P2P_THIS_DEVICE_CHANGED_ACTION: The details for this device have changed.

Source http://developer.android.com/sdk/android-4.0.html
More info about the new API can be found here and info about WIFI direct is over here

The reason for the new standard support is because of the lack of security in Ad-Hoc mode. More info http://en.wikipedia.org/wiki/Wireless_security#Ad-hoc_networks
And network problems http://en.wikipedia.org/wiki/Wireless_ad-hoc_network#Medium-access_control

Its the reason it was dumped, not only by Android but Linux and other systems as well. We just used a work around to bypass and ignore the issues at hand.
 
... to be more to the point it has no support for WiFi Direct and probibly needs the developer to play catch up.

Seems that my phone does support wi-fi direct (upgraded to gingerbread and it is now on the wifi settings). Are you perhaps aware of any tether apps that can make use of this functionality?
 
Seems that my phone does support wi-fi direct (upgraded to gingerbread and it is now on the wifi settings). Are you perhaps aware of any tether apps that can make use of this functionality?

Unfortunately not, I use MIUI on my phone that does everything I need with ease so I don't go hunting for crappy applications based on core functionality.

Sorry.
 
I just placed an order with Expansys for the 16gb Transformer (wifi only) with Kb dock for R5500!

Can't wait as the ETA is 5 working days.

It's coming from the UK so do you guys have any idea as to whether the local Asus agents will cover the guarantee? i did call Asus locally and they said that they will but u can never be too sure

I have heard something about an international guarantee. can anyone elaborate?
 
I just placed an order with Expansys for the 16gb Transformer (wifi only) with Kb dock for R5500!

Can't wait as the ETA is 5 working days.

It's coming from the UK so do you guys have any idea as to whether the local Asus agents will cover the guarantee? i did call Asus locally and they said that they will but u can never be too sure

I have heard something about an international guarantee. can anyone elaborate?

I am almost sure you can source it at a better price locally. I bought mine for that price. Only thing is its the 32 gig model.

Sent from my Transformer TF101 using Tapatalk
 
I have looked locally for a long time - the best locally sourced prices came from the notebook company (who claim that they will beat any price provided it is sourced locally and stock is available) and their price was R6300 (R4000 + R 1800) for the tablet and the dock

If anybody can help with better pricing I will be more than happy to buy from SA but i will need to move quite quickly.
 
hmm seems price have gone up. Wootware used to be around R4k IIRC.
Got mine in store for R4200 (16GB)
And R1500 for the dock.
 
how many of you guys who've got the TF101 with the ICS update from 2 weeks ago have issues? I'm experiencing the reboots, crashes and powerdowns randomly as described by quite a few people on various forums, as is a coworker. When looking at another coworker's tablet we noticed she couldn't get the update - so I assume it's been pulled while they fix it.

I'm quite aware of the issues I mentioned above being aware to ASUS, I'm just wondering how many of you guys are in the same boat as me?
 
I've seen mine reboot once or twice, usually when is has been sitting idling. Did you do a factory reset after the update?
 
Did try factory resetting but not much help - apparently ASUS is aware of it and 'is working' on a fix - apparently though the bugs only affect 5% of users - I'm one of the lucky few apparently!
 
Check out the XDA forums and you will find quite a few people having the random reboot problem. Mine rebooted once after the update and not again. I updated mine the week the update became available. Apparently there is another update that people said they were hoping would solve this problem but hasn't seem to have been the solution.

Anyone have face unlock on the tab since the update?
 
Top
Sign up to the MyBroadband newsletter
X