on 09-12-2011 10h26
I have a Samsung Galaxy phone (i9000) which was always tempremental when connecting to Home Hub 2 (this is well documented elsewhere in this forum). I am unable to directly connect to the HH but have to use BT Fon. This was usually OK but a bit hit and miss when trying to connect.
I updated the app yesterday and now have a completely different looking app (v3.0.2). Now I am unable to connect at all, getting the error message 'Sorry, we have been unable to identify this hotspot. For your safety please try another hotspot.'
I cannot regress thsi change, have reset the router etc. but am unable to connect. Why would it suggest my own HH is not identifiable??
Any ideas please?
on 09-12-2011 15h09
Hmm, looking at the reviews on the android market a few others are also experiencing the same problem with the new version
Looks like there may be a problem with the app, but as the Samsung Galaxy never could connect 'normally' to the HH2 I now have no means of wi-fi connection apart from a visit to the Golden Arches or similar
on 09-12-2011 15h47
on 09-12-2011 18h12
Thanks for bringing this to our attention.
We have passed this issue to the team responsible for the app and they are going to investigate.
on 09-12-2011 20h18
on 10-12-2011 8h11
on 10-12-2011 10h48
i am also unable to connect with the Btfon update following the upgrade. Samsung galaxy S2 had not connection problems before hand...If you go to the Android review section for the new Btfon app EVERYONE is saying they are now unable to connect
on 10-12-2011 11h06
I spoke too soon. I had already connected manually to my BTFON hotspot (from the web login). When I launch the app the status goes to "checking internet connectivity" immediately and then it identified my hotspot I.e. if you are not already logged in then the checking internet connectivity fails and then you get the message "cannot identify hotspot". (samsung galaxy s i9000)
I am getting exactly the same message. My HTC desire connects to openzone but then try the app and the message same as bashville. does not seem to recognise it is already connected