iPad : WiFi not always stable, and heat problems witnessed

The first teething problems have started to appear on the iPad tablet. Some users have signalled WiFi connection outages, while others have noticed the system locks up when system temperatures rise too high.

The release of a new product like the iPad tablet is sometimes accompanied by small problems which weren’t detected before the production phase (in principle). Some of the first users have signalled stability problems with the WiFi connection (impossible to connect, continually disconnecting...).

Apple hasn’t denied the existence of these small problems, claiming that the problem comes from certain internet routers in use, rather then a problem existing on their product. The problem, which only affects a small number of users, comes from routers which use two frequency channels, on which two distinct WiFi networks are created, although these may carry the same name or use different security settings.

The resolution steps provided uniquely linked to the router settings, suggesting that the iPad’s components and software are without fault. We will have to wait and see if these problems persist.


It’s lacking an iFan
Another point raised concerns the iPad user profile, with numerous users indicating that messages indicating that their tablet is overheated have appeared, making the device inoperable when outside.

One of the users has stated that their tablet was protected by a darkly coloured case which was exposed to the sun, which in itself isn’t an exceptional situation considering that the product has been designed for mobile use.

Having said this, it appears that the maximum temperature recommended by Apple for the device is 35° C, which appears to be reasonable for inside use but which may be a little low for use outside. The activation of certain functions can also contribute to the devices heat, leaving little room for manoeuvre.

Will iPad users put up with these spontaneous interruptions to their work, waiting long enough for the temperature to drop back into the acceptable range? A lot of uses believe that the next update will correct this small issue.