Tizen Developers

Menu
Sites
Language
Getting tons of errors after connecting to my Gear S2 using Device Manager after updating to Tizen Studio 2.0 (log attached)

See the attached log.

12-01 21:02:06.913 : Info / LOCATION ( 1373 : 1373 ) : location-gps.c: __get_availability_use_gps(378) > Check _availability use GPS
12-01 21:02:06.913 : Error / maps ( 1373 : 1373 ) : LocationManager.cpp: callLocationListeners(672) > * Critical * while
12-01 21:02:06.913 : Error / maps ( 1373 : 1373 ) : LocationManager.cpp: callLocationListeners(681) > * Critical * lock
12-01 21:02:06.913 : Error / maps ( 1373 : 1373 ) : MapView.cpp: OnLocationUpdated(337) > [OnLocationUpdated(): 337] (mode_ == ViewMode::LOCATION_OFF) [return]
12-01 21:02:06.913 : Error / maps ( 1373 : 1373 ) : MainView.cpp: OnLocationUpdated(408) > * Critical * geocode_request_state_ : 4, not request reverse geocode

12-02 10:47:44.021 : Error / CAPI_SYSTEM_INFO ( 1221 : 5598 ) : system_info_parse.c: system_info_get_value_from_config_xml(279) > cannot find tizen.org/feature/container field from /etc/config/model-config.xml file!!!
12-02 10:47:44.026 : Error / CAPI_SYSTEM_INFO ( 1221 : 5598 ) : system_info.c: system_info_get_platform_bool(293) > cannot get tizen.org/feature/container
12-02 10:47:51.736 : Error / CAPI_SYSTEM_INFO ( 1221 : 5685 ) : system_info_parse.c: system_info_get_value_from_config_xml(279) > cannot find tizen.org/feature/container field from /etc/config/model-config.xml file!!!
12-02 10:47:51.741 : Error / CAPI_SYSTEM_INFO ( 1221 : 5685 ) : system_info.c: system_info_get_platform_bool(293) > cannot get tizen.org/feature/container

Edited on 03 12, 2017

Responses

2 Replies
Yasin Ali

Hi,

You may try re-installing Tizen Studio at a new directory.

I think its a problem with directory path setup of Tizen Studio.

Thanks.

 

Harry Hyeongseok Heo

Hi .

@parshakov

Is this log is just showing on the Device manager when you connect your Gear S2 ?

I think that the log you attached is tizen platform log on the logview of the Device manager. Right?

If so , it's not a Device manager bug but a tizen platform issue.