My question is basically the same as this question from 4 years ago, but the only answer to the question did not work. So I am asking this again.
My configuration is the followings.
implementation 'com.google.android.gms:play-services-maps:11.8.0'
compile 'com.google.maps.android:android-maps-utils:0.5'
targetSdkVersion 27
compileSdkVersion 27
buildToolsVersion "27.0.3"
The main activity has tabs which of which is a fragment. One of the fragments contain Google Maps, which itself is a fragment.
<fragment
android:id="@+id/mapView"
android:name="com.google.android.gms.maps.SupportMapFragment"
It works fine, but when I see the log with "No Filters" there are strange red logs flooding.
system_process E/LocSvc_eng_nmea: I/<=== nmea_cb line 62 [some hex value]
system_process E/LocSvc_eng_nmea: I/<=== nmea_cb line 62 [some hex value]
I have tried the answer in the question aforementioned, and changed the 'fragment' to a 'FrameLayout' and replaced it with SupportMapView at runtime, but the logs did not disappear.
var mapFragment = SupportMapFragment.newInstance();
this.childFragmentManager.beginTransaction()
.replace(R.id.mapView, mapFragment)
.commit();
How to prevent the error logs?
PS: When I created a sample application and added a support map fragment directly to the main activity, the error messages did not happen. So I think it has something to do with fragments.
PS2: It may not be related to fragments, because I changed the sample app and placed the map fragment inside another fragment, but the logs did not happen. I have tried some things but failed to reproduce the problem in the sample app.
PS3: Removing isMyLocationEnabled = true; solved the problem, but I need this feature.