Setok
|
2012-07-10
, 08:43
|
Posts: 46 |
Thanked: 116 times |
Joined on Jan 2012
|
#291
|
|
2012-07-10
, 08:52
|
Moderator |
Posts: 6,215 |
Thanked: 6,400 times |
Joined on Nov 2011
|
#292
|
|
2012-07-10
, 09:40
|
Moderator |
Posts: 5,320 |
Thanked: 4,464 times |
Joined on Oct 2009
|
#293
|
|
2012-07-10
, 09:51
|
Posts: 1,313 |
Thanked: 2,977 times |
Joined on Jun 2011
@ Finland
|
#294
|
|
2012-07-10
, 13:30
|
Moderator |
Posts: 6,215 |
Thanked: 6,400 times |
Joined on Nov 2011
|
#295
|
You know this because you actually compared two N9's? [1x PR1.2 & 1x PR1.3]* TY.
*ideally clean flashed
|
2012-07-10
, 14:46
|
Moderator |
Posts: 5,320 |
Thanked: 4,464 times |
Joined on Oct 2009
|
#296
|
|
2012-07-10
, 18:37
|
|
Posts: 197 |
Thanked: 198 times |
Joined on Feb 2012
@ Helsinki, Finland
|
#297
|
The Following User Says Thank You to late88 For This Useful Post: | ||
|
2012-07-10
, 22:29
|
Posts: 16 |
Thanked: 50 times |
Joined on Jul 2012
|
#298
|
Well this is not one hallelujah discovery but yesterday I noticed a different error message when trying to connect to my local WiFi network. Instead of just network error it also reported that it was unable to get a DHCP address from the server. I'm almost certain I have never seen the DHCP message before.
This is not an error caused by the phone. It is just in the limit of my routers range so signal is pretty weak at that spot in my house.
The Following User Says Thank You to Sthocs For This Useful Post: | ||
|
2012-07-11
, 10:42
|
Posts: 78 |
Thanked: 135 times |
Joined on Jul 2012
|
#299
|
|
2012-07-11
, 14:03
|
|
Posts: 418 |
Thanked: 506 times |
Joined on Jan 2012
@ Argentina
|
#300
|
The Following User Says Thank You to flotron For This Useful Post: | ||