Closed lesjaw closed 9 years ago
this is quite common, since the reverse lookup tries to find the name of your location by your coordinates, thus needing both an active connection and GPS fresh coords. If one of these fails/is not available, you got that on log.
What about front-end? Main screen should write out your current position name (town, city, whatever). Does this work?
Oh I see.. Yes it is work... I see my location.. On Aug 26, 2015 6:07 AM, "shineangelic" notifications@github.com wrote:
this is quite common, since the reverse lookup tries to find the name of your location by your coordinates, thus needing both an active connection and GPS fresh coords. If one of these fails/is not available, you got that on log.
What about front-end? Main screen should write out your current position name (town, city, whatever). Does this work?
— Reply to this email directly or view it on GitHub https://github.com/souliss/soulissapp/issues/27#issuecomment-134766439.
this is from SoulissApp logcat
08-25 21:02:51.994 6320-6320/it.angelic.soulissclient:souliss_process E/SoulissApp﹕ Geocoder ERROR java.io.IOException: Timed out waiting for response from server at android.location.Geocoder.getFromLocation(Geocoder.java:136) at it.angelic.soulissclient.LauncherActivity$13.run(LauncherActivity.java:757) at java.lang.Thread.run(Thread.java:841)