Obsolete
Status Update
Comments
an...@gmail.com <an...@gmail.com> #2
Argh....with this bug there is absolutely no way to determine if the user has changed changed the panning of the map....I need a way to determine this so that i can allow the user to reset the map to it's original view. Please fix this ASAP.
tc...@gmail.com <tc...@gmail.com> #3
I have another example regarding the problematic accuracy of moveCamera/animateCamera.
When you use CameraUpdateFactory.newLatLngBounds(), moveCamera and animateCamera result in different values in map.getProjection().getVisibleRegion().latLngBounds.
LatLngBounds bounds = new LatLngBounds(new LatLng(40.70798493778415, -74.01434069136418), new LatLng(40.72072004852845, -73.99760391411343));
if (animate) {
map.animateCamera(CameraUpdateFactory.newLatLngBounds(bounds, 0),
} else {
map.moveCamera(CameraUpdateFactory.newLatLngBounds(bounds, 0));
}
map.getProjection().getVisibleRegion().latLngBounds :
after animateCamera -
LatLngBounds{southwest=lat/lng: (40.70711197865251,-74.01539381593466), northeast=lat/lng: (40.72159253556309,-73.99655096232891)}
after moveCamera -
LatLngBounds{southwest=lat/lng: (40.70798500292429,-74.01539381593466), northeast=lat/lng: (40.72071968970514,-73.99655096232891)}
This is pretty important for my design as im calculating a search radius (Vincenty’s formula) by the bounds of the map. appreciate if you could confirm the accuracy of those 2 APIs.
When you use CameraUpdateFactory.newLatLngBounds(), moveCamera and animateCamera result in different values in map.getProjection().getVisibleRegion().latLngBounds.
LatLngBounds bounds = new LatLngBounds(new LatLng(40.70798493778415, -74.01434069136418), new LatLng(40.72072004852845, -73.99760391411343));
if (animate) {
map.animateCamera(CameraUpdateFactory.newLatLngBounds(bounds, 0),
} else {
map.moveCamera(CameraUpdateFactory.newLatLngBounds(bounds, 0));
}
map.getProjection().getVisibleRegion().latLngBounds :
after animateCamera -
LatLngBounds{southwest=lat/lng: (40.70711197865251,-74.01539381593466), northeast=lat/lng: (40.72159253556309,-73.99655096232891)}
after moveCamera -
LatLngBounds{southwest=lat/lng: (40.70798500292429,-74.01539381593466), northeast=lat/lng: (40.72071968970514,-73.99655096232891)}
This is pretty important for my design as im calculating a search radius (Vincenty’s formula) by the bounds of the map. appreciate if you could confirm the accuracy of those 2 APIs.
gr...@gmail.com <gr...@gmail.com> #5
any news regarding this issue ?
na...@gmail.com <na...@gmail.com> #6
I can share my thoughts about it.
LatLng is keeping doubles, when these are sent via IPC, they are flattened to floats, because there is no writeDouble:http://developer.android.com/reference/android/os/Parcel.html#writeFloat%28float%29 .
When going back, you lose precision and thus errors on 4-5th decimal place.
If I'm correct here, this can be hard (if possible) to fix without breaking compatibility.
LatLng is keeping doubles, when these are sent via IPC, they are flattened to floats, because there is no writeDouble:
When going back, you lose precision and thus errors on 4-5th decimal place.
If I'm correct here, this can be hard (if possible) to fix without breaking compatibility.
gu...@gmail.com <gu...@gmail.com> #7
If you're right then compatibility doesnt have to be broken in order to pass a more accurate LatLng value in many other parcelable types which are not float. This option can be added and not replace the current one.
I any case this issue is really annoying and i hope someone from google can take a look at it. Thanks.
I any case this issue is really annoying and i hope someone from google can take a look at it. Thanks.
mi...@gmail.com <mi...@gmail.com> #8
If I'm right then you are also right. ;)
Double values in LatLng could be sent using writeLong after converting them using Double.doubleToLongBits (http://docs.oracle.com/javase/7/docs/api/java/lang/Double.html#doubleToLongBits%28double%29 ) and converted back to double in Google Play Services app.
Double values in LatLng could be sent using writeLong after converting them using Double.doubleToLongBits (
pu...@gmail.com <pu...@gmail.com> #9
[Comment deleted]
re...@gmail.com <re...@gmail.com> #10
[Comment deleted]
pa...@gmail.com <pa...@gmail.com> #11
Comparing floating-point values for exact equality is rarely a good idea. I'd suggest treating two LatLngs as equal if they're within some small distance of each other.
Not sure what comment #5 is getting at. Parcel#writeDouble exists, and the docs say it's been around since API 1. (Although the docs have been known to lie...)
Not sure what
ro...@gmail.com <ro...@gmail.com> #12
As you are comparing objects, not numerals, unless specifically otherwise documented, you should expect the equals() method of any class derived from Object to implement the same equivalence relation as the parent class [1]:
"The equals method for class Object implements the most discriminating possible equivalence relation on objects; that is, for any non-null reference values x and y, this method returns true if and only if x and y refer to the same object (x == y has the value true)."
Also, regarding numerals, as the previous commenter already mentioned, comparing floating point values for exact equality is generally not a good idea, and doing it right is far from trivial [2].
Issue 4786 had a similar report about the onCameraChange() event not returning the exact same coordinates originally passed to CameraUpdateFactory.newLatLng().
As I commented there, we need to convert between real-world coordinates and pixel coordinates to render anything on the screen, so especially when it comes to cameras and views, you should not assume the coordinates you gave to exactly match those used internally.
The developer on the other issue provided two (longitude) coordinates as an example: 51.9820167 (given by developer) and 51.982016909253694 (returned by the API). However, the maximum real-world distance between these points is actually only 2.3 cm (at the equator).
If you need to check coordinates for approximate equality, I'd recommend using an arbitrary epsilon value of your choice (e.g. 5 or 10 cm, or 0.000001 degrees) to determine if two points are close enough to each other to be considered equal. You just need to choose a suitable distance metric and epsilon that works well for for your use case.
As we know the number ranges ([-90.0, 90.0] and [-180.0, 180.0) degrees), as well as the approximate minimum resolution of the map, absolute error margins are likely sufficient for most use cases (either in degrees or distance). That way you can avoid having to bother with the less intuitive relative errors mentioned in the linked article.
That said, I changed this issue to a type Enhancement request, and created an internal feature request for providing an a convenience method for calculating approximate equality.
[1]https://docs.oracle.com/javase/8/docs/api/java/lang/Object.html#equals-java.lang.Object-
[2]http://floating-point-gui.de/errors/comparison/
"The equals method for class Object implements the most discriminating possible equivalence relation on objects; that is, for any non-null reference values x and y, this method returns true if and only if x and y refer to the same object (x == y has the value true)."
Also, regarding numerals, as the previous commenter already mentioned, comparing floating point values for exact equality is generally not a good idea, and doing it right is far from trivial [2].
As I commented there, we need to convert between real-world coordinates and pixel coordinates to render anything on the screen, so especially when it comes to cameras and views, you should not assume the coordinates you gave to exactly match those used internally.
The developer on the other issue provided two (longitude) coordinates as an example: 51.9820167 (given by developer) and 51.982016909253694 (returned by the API). However, the maximum real-world distance between these points is actually only 2.3 cm (at the equator).
If you need to check coordinates for approximate equality, I'd recommend using an arbitrary epsilon value of your choice (e.g. 5 or 10 cm, or 0.000001 degrees) to determine if two points are close enough to each other to be considered equal. You just need to choose a suitable distance metric and epsilon that works well for for your use case.
As we know the number ranges ([-90.0, 90.0] and [-180.0, 180.0) degrees), as well as the approximate minimum resolution of the map, absolute error margins are likely sufficient for most use cases (either in degrees or distance). That way you can avoid having to bother with the less intuitive relative errors mentioned in the linked article.
That said, I changed this issue to a type Enhancement request, and created an internal feature request for providing an a convenience method for calculating approximate equality.
[1]
[2]
ro...@gmail.com <ro...@gmail.com> #13
Follow-up to comment 11: Mine is an unrooted phone, with relatively few apps (all standard store-downloaded, non-development ones). The below is a fairly extreme example - 7 examples in about 1.5 seconds. Other than this, it's aevery few seconds (as others have noted).
09-14 13:53:34.488 E/NetlinkEvent(1347)NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
09-14 13:53:34.541 D/dalvikvm(5848)GC_CONCURRENT freed 852K, 42% free 4199K/7175K, external 2357K/2773K, paused 1ms+2ms
09-14 13:53:34.571 E/NetlinkEvent(1347)NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
09-14 13:53:34.841 D/dalvikvm(5848)GC_CONCURRENT freed 987K, 42% free 4439K/7559K, external 2357K/2773K, paused 3ms+8ms
09-14 13:53:34.911 E/NetlinkEvent(1347)NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
09-14 13:53:35.058 E/NetlinkEvent(1347)NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
09-14 13:53:35.258 D/dalvikvm(5848)GC_CONCURRENT freed 861K, 39% free 4872K/7879K, external 2357K/2773K, paused 2ms+3ms
09-14 13:53:35.338 E/NetlinkEvent(1347)NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
09-14 13:53:35.378 E/NetlinkEvent(1347)NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
09-14 13:53:35.769 E/NetlinkEvent(1347)NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
09-14 13:53:34.488 E/NetlinkEvent(1347)NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
09-14 13:53:34.541 D/dalvikvm(5848)GC_CONCURRENT freed 852K, 42% free 4199K/7175K, external 2357K/2773K, paused 1ms+2ms
09-14 13:53:34.571 E/NetlinkEvent(1347)NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
09-14 13:53:34.841 D/dalvikvm(5848)GC_CONCURRENT freed 987K, 42% free 4439K/7559K, external 2357K/2773K, paused 3ms+8ms
09-14 13:53:34.911 E/NetlinkEvent(1347)NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
09-14 13:53:35.058 E/NetlinkEvent(1347)NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
09-14 13:53:35.258 D/dalvikvm(5848)GC_CONCURRENT freed 861K, 39% free 4872K/7879K, external 2357K/2773K, paused 2ms+3ms
09-14 13:53:35.338 E/NetlinkEvent(1347)NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
09-14 13:53:35.378 E/NetlinkEvent(1347)NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
09-14 13:53:35.769 E/NetlinkEvent(1347)NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
ro...@gmail.com <ro...@gmail.com> #14
[Deleted User] <[Deleted User]> #15
Unrelated to this issue, but since my unrelated issue was incorrectly closed as a duplicate...
The current implementation of equals() is just plain wrong. This is a case where comparing floating point values using the == operator is exactly what you want. The current implementation compares the values for bitwise equality, which is wrong in at least two ways: it incorrectly returns true when comparing two NaNs, and it incorrectly returns false when comparing 0f and -0f.
The current implementation of equals() is just plain wrong. This is a case where comparing floating point values using the == operator is exactly what you want. The current implementation compares the values for bitwise equality, which is wrong in at least two ways: it incorrectly returns true when comparing two NaNs, and it incorrectly returns false when comparing 0f and -0f.
[Deleted User] <[Deleted User]> #16
[Comment deleted]
[Deleted User] <[Deleted User]> #17
hi i am using samsung galaxy pocket and i have same problem. I have no apps in development on the phone. Only reboot can solve this problem but after a while it occurs again. this phone starts to work very slow while this problem occurs. The information about my phone is below. please help.
Kernel version: 2.6.35.7 official.cori@androide#81
Android Version: 2.3.6
Baseband version: S5300XXLF4
Kernel version: 2.6.35.7 official.cori@androide#81
Android Version: 2.3.6
Baseband version: S5300XXLF4
kg...@gmail.com <kg...@gmail.com> #18
This is also definitely a problem in the US firmware for the MB860.
(I can't store in my pocket screen-out anymore, as it tends to fry any micro-tadpoles in proximity due to the extra heat generation when spinning the processor in this cycle.)
MB860 (Motorola Atrix)
build.fingerprint: MOTO/olyatt/olympus:2.3.6/4.5.141/111212:user/release-keys
My logs blast these messages about 8 times per second for the "ignoring multicast message", 2 different processes.
Log snippet attached for evidence.
It would be nice if Motorola/Google support engineer would either respond to the thread with an "As designed, will not fix", or else provide some hope that I should continue to hold on to a device that now runs slower, eats power and heats up.
(I can't store in my pocket screen-out anymore, as it tends to fry any micro-tadpoles in proximity due to the extra heat generation when spinning the processor in this cycle.)
MB860 (Motorola Atrix)
build.fingerprint: MOTO/olyatt/olympus:2.3.6/4.5.141/111212:user/release-keys
My logs blast these messages about 8 times per second for the "ignoring multicast message", 2 different processes.
Log snippet attached for evidence.
It would be nice if Motorola/Google support engineer would either respond to the thread with an "As designed, will not fix", or else provide some hope that I should continue to hold on to a device that now runs slower, eats power and heats up.
gu...@gmail.com <gu...@gmail.com> #19
me too, even there's nothing installed in my phone
da...@gmail.com <da...@gmail.com> #20
Seeing same issue. Logcat is filled with this error messages. Phone performance has gone down. 100% charges battery drops all the charge in one day.
Build Number: 4.5.1A-129_OLY-145
Baseband Version: N_01.77.38P
Model: Motorola MB860
System Version:4.5.145.MB860.ATT.en.US
Android Version: 2.3.6
Build Number: 4.5.1A-129_OLY-145
Baseband Version: N_01.77.38P
Model: Motorola MB860
System Version:
Android Version: 2.3.6
va...@gmail.com <va...@gmail.com> #21
igot this error:10-28 07:46:10.668: E/NetlinkEvent(1942): NetlinkEvent::FindParam(): Parameter 'TIME_NS' not found
n....@gmail.com <n....@gmail.com> #22
Did anyone figure out this issue? Recently needed to use my DX2 as a backup and am getting exact same errors in the log as OP. I'm wondering if installing CWM 10, which runs on 4.1.2, will solve the issue.
n....@gmail.com <n....@gmail.com> #23
Issue is happening on stock 2.3.4, 2.3.5, and CM10 (4.1.2)
I remember a time when my phone was not doing this. Might have been before 2.3.4
I'm on an MB870 on Verizon
I remember a time when my phone was not doing this. Might have been before 2.3.4
I'm on an MB870 on Verizon
en...@google.com <en...@google.com>
ch...@chrisolin.com <ch...@chrisolin.com> #24
Probably should create a new issues, but I'm seeing this on Marshmallow/6.0.1 on a Sprint Note 4/N910P:
03-05 13:05:58.873 17392 NetlinkEvent E NetlinkEvent::FindParam(): Parameter 'INTERFACE' not found
03-05 13:05:58.873 17392 NetlinkEvent E NetlinkEvent::FindParam(): Parameter 'UID' not found
03-05 13:05:58.875 17924 NetdConnector E Error handling '613 IfaceClass active (null) 4132847086024':
java.lang.NumberFormatException: Invalid int: "(null)"
03-05 13:05:58.873 17392 NetlinkEvent E NetlinkEvent::FindParam(): Parameter 'INTERFACE' not found
03-05 13:05:58.873 17392 NetlinkEvent E NetlinkEvent::FindParam(): Parameter 'UID' not found
03-05 13:05:58.875 17924 NetdConnector E Error handling '613 IfaceClass active (null) 4132847086024':
java.lang.NumberFormatException: Invalid int: "(null)"
ma...@gmail.com <ma...@gmail.com> #25
I'm seeing the below set of messages/errors on a Samsung Galaxy Note 5 (Sprint) running Marshmallow/6.0.1.
They are repeated over and over again. Sorry for the amount of messages but imagine them repeated 100 times as your trying to watch output for something else.
10-07 08:25:17.221 3231-3874/? E/NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'LABEL' not found
10-07 08:25:17.221 3231-3874/? E/NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UID' not found
10-07 08:25:17.221 3668-3753/? D/BatteryStatsImpl: poolsize= 1, curBatteryRealtime= 522796000, mUpdateTime= 522796000, mTimeout= 0, mNesting= 1, mTotalTime= 198480000
10-07 08:25:17.521 3668-4898/? D/BatteryService: !@BatteryListener : batteryPropertiesChanged!
10-07 08:25:17.531 3668-4898/? D/BatteryService: level:100, scale:100, status:5, health:2, present:true, voltage: 4303, temperature: 285, technology: Li-ion, AC powered:false, USB powered:true, POGO powered:false, Wireless powered:false, icon:17303446, invalid charger:0, maxChargingCurrent:0
10-07 08:25:17.531 3668-4898/? D/BatteryService: online:4, current avg:157, charge type:1, power sharing:false, high voltage charger:false, capacity:280000, batterySWSelfDischarging:false, current_now:192
10-07 08:25:17.531 3668-3668/? D/BatteryService: Sending ACTION_BATTERY_CHANGED.
10-07 08:25:17.531 3668-3668/? I/MotionRecognitionService: Plugged
10-07 08:25:17.531 3668-3668/? D/MotionRecognitionService: cableConnection= 1
10-07 08:25:17.531 3668-3668/? D/MotionRecognitionService: setPowerConnected | current backoffstate = 1024 , state =1024
10-07 08:25:17.531 3668-3668/? D/MotionRecognitionService: skip setTransmitPower.
10-07 08:25:17.541 4454-4454/? D/KeyguardUpdateMonitor: received broadcast android.intent.action.BATTERY_CHANGED
10-07 08:25:17.541 4454-4454/? D/KeyguardUpdateMonitor: handleBatteryUpdate
10-07 08:25:17.541 4454-4454/? D/PowerUI: priorPlugType = 2 mPlugType = 2
10-07 08:25:17.551 4454-4454/? D/BatteryMeterView: ACTION_BATTERY_CHANGED : level:100 status:5 health:2
10-07 08:25:17.571 4454-4454/? D/BatteryMeterView: ACTION_BATTERY_CHANGED : level:100 status:5 health:2
10-07 08:25:20.861 4454-4652/? D/NetworkController.MobileSignalController(0/1): onSignalStrengthsChanged signalStrength=SignalStrength: 99 99 -120 -160 -120 -1 -1 18 -104 -8 152 -1 2147483647 0x3000 gsm|lte level=3
10-07 08:25:20.861 4454-4652/? D/NetworkController.MobileSignalController(0/1): getMobileIconGroup(): 13
10-07 08:25:21.191 3668-9995/? D/SSRM:s: SIOP:: AP = 330, PST = 342 (W:20), CP = 258, CUR = 240, LCD = 82
10-07 08:25:21.201 3668-9995/? D/ConnectivityService: returning getNetworkInfo for network type 1 : [type: WIFI[] - WIFI, state: DISCONNECTED/DISCONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true]
10-07 08:25:22.051 4454-4652/? D/NetworkController.MobileSignalController(0/1): onSignalStrengthsChanged signalStrength=SignalStrength: 99 99 -120 -160 -120 -1 -1 18 -104 -8 140 -1 2147483647 0x3000 gsm|lte level=3
10-07 08:25:22.051 4454-4652/? D/NetworkController.MobileSignalController(0/1): getMobileIconGroup(): 13
10-07 08:25:27.591 3668-3687/? D/BatteryService: !@BatteryListener : batteryPropertiesChanged!
10-07 08:25:27.591 3668-3687/? D/BatteryService: level:100, scale:100, status:5, health:2, present:true, voltage: 4305, temperature: 285, technology: Li-ion, AC powered:false, USB powered:true, POGO powered:false, Wireless powered:false, icon:17303446, invalid charger:0, maxChargingCurrent:0
10-07 08:25:27.591 3668-3687/? D/BatteryService: online:4, current avg:170, charge type:1, power sharing:false, high voltage charger:false, capacity:280000, batterySWSelfDischarging:false, current_now:178
10-07 08:25:27.591 3668-3668/? D/BatteryService: Sending ACTION_BATTERY_CHANGED.
10-07 08:25:27.601 3668-3668/? I/MotionRecognitionService: Plugged
10-07 08:25:27.601 3668-3668/? D/MotionRecognitionService: cableConnection= 1
10-07 08:25:27.601 3668-3668/? D/MotionRecognitionService: setPowerConnected | current backoffstate = 1024 , state =1024
10-07 08:25:27.601 3668-3668/? D/MotionRecognitionService: skip setTransmitPower.
10-07 08:25:27.611 4454-4454/? D/KeyguardUpdateMonitor: received broadcast android.intent.action.BATTERY_CHANGED
10-07 08:25:27.611 4454-4454/? D/KeyguardUpdateMonitor: handleBatteryUpdate
10-07 08:25:27.611 4454-4454/? D/PowerUI: priorPlugType = 2 mPlugType = 2
10-07 08:25:27.641 4454-4454/? D/BatteryMeterView: ACTION_BATTERY_CHANGED : level:100 status:5 health:2
10-07 08:25:27.641 4454-4454/? D/BatteryMeterView: ACTION_BATTERY_CHANGED : level:100 status:5 health:2
10-07 08:25:28.541 4454-4652/? D/NetworkController.MobileSignalController(0/1): onSignalStrengthsChanged signalStrength=SignalStrength: 99 99 -120 -160 -120 -1 -1 18 -104 -9 152 -1 2147483647 0x3000 gsm|lte level=3
10-07 08:25:28.541 4454-4652/? D/NetworkController.MobileSignalController(0/1): getMobileIconGroup(): 13
10-07 08:25:31.101 4454-4652/? D/NetworkController.MobileSignalController(0/1): onSignalStrengthsChanged signalStrength=SignalStrength: 99 99 -120 -160 -120 -1 -1 19 -104 -9 116 -1 2147483647 0x3000 gsm|lte level=3
10-07 08:25:31.101 4454-4652/? D/NetworkController.MobileSignalController(0/1): getMobileIconGroup(): 13
10-07 08:25:31.231 3668-9995/? D/SSRM:s: SIOP:: AP = 310, PST = 342 (W:24), CP = 252, CUR = 180, LCD = 82
10-07 08:25:31.241 3668-9995/? D/ConnectivityService: returning getNetworkInfo for network type 1 : [type: WIFI[] - WIFI, state: DISCONNECTED/DISCONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true]
10-07 08:25:32.281 4454-4652/? D/NetworkController.MobileSignalController(0/1): onSignalStrengthsChanged signalStrength=SignalStrength: 99 99 -120 -160 -120 -1 -1 19 -104 -9 144 -1 2147483647 0x3000 gsm|lte level=3
10-07 08:25:32.291 4454-4652/? D/NetworkController.MobileSignalController(0/1): getMobileIconGroup(): 13
They are repeated over and over again. Sorry for the amount of messages but imagine them repeated 100 times as your trying to watch output for something else.
10-07 08:25:17.221 3231-3874/? E/NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'LABEL' not found
10-07 08:25:17.221 3231-3874/? E/NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UID' not found
10-07 08:25:17.221 3668-3753/? D/BatteryStatsImpl: poolsize= 1, curBatteryRealtime= 522796000, mUpdateTime= 522796000, mTimeout= 0, mNesting= 1, mTotalTime= 198480000
10-07 08:25:17.521 3668-4898/? D/BatteryService: !@BatteryListener : batteryPropertiesChanged!
10-07 08:25:17.531 3668-4898/? D/BatteryService: level:100, scale:100, status:5, health:2, present:true, voltage: 4303, temperature: 285, technology: Li-ion, AC powered:false, USB powered:true, POGO powered:false, Wireless powered:false, icon:17303446, invalid charger:0, maxChargingCurrent:0
10-07 08:25:17.531 3668-4898/? D/BatteryService: online:4, current avg:157, charge type:1, power sharing:false, high voltage charger:false, capacity:280000, batterySWSelfDischarging:false, current_now:192
10-07 08:25:17.531 3668-3668/? D/BatteryService: Sending ACTION_BATTERY_CHANGED.
10-07 08:25:17.531 3668-3668/? I/MotionRecognitionService: Plugged
10-07 08:25:17.531 3668-3668/? D/MotionRecognitionService: cableConnection= 1
10-07 08:25:17.531 3668-3668/? D/MotionRecognitionService: setPowerConnected | current backoffstate = 1024 , state =1024
10-07 08:25:17.531 3668-3668/? D/MotionRecognitionService: skip setTransmitPower.
10-07 08:25:17.541 4454-4454/? D/KeyguardUpdateMonitor: received broadcast android.intent.action.BATTERY_CHANGED
10-07 08:25:17.541 4454-4454/? D/KeyguardUpdateMonitor: handleBatteryUpdate
10-07 08:25:17.541 4454-4454/? D/PowerUI: priorPlugType = 2 mPlugType = 2
10-07 08:25:17.551 4454-4454/? D/BatteryMeterView: ACTION_BATTERY_CHANGED : level:100 status:5 health:2
10-07 08:25:17.571 4454-4454/? D/BatteryMeterView: ACTION_BATTERY_CHANGED : level:100 status:5 health:2
10-07 08:25:20.861 4454-4652/? D/NetworkController.MobileSignalController(0/1): onSignalStrengthsChanged signalStrength=SignalStrength: 99 99 -120 -160 -120 -1 -1 18 -104 -8 152 -1 2147483647 0x3000 gsm|lte level=3
10-07 08:25:20.861 4454-4652/? D/NetworkController.MobileSignalController(0/1): getMobileIconGroup(): 13
10-07 08:25:21.191 3668-9995/? D/SSRM:s: SIOP:: AP = 330, PST = 342 (W:20), CP = 258, CUR = 240, LCD = 82
10-07 08:25:21.201 3668-9995/? D/ConnectivityService: returning getNetworkInfo for network type 1 : [type: WIFI[] - WIFI, state: DISCONNECTED/DISCONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true]
10-07 08:25:22.051 4454-4652/? D/NetworkController.MobileSignalController(0/1): onSignalStrengthsChanged signalStrength=SignalStrength: 99 99 -120 -160 -120 -1 -1 18 -104 -8 140 -1 2147483647 0x3000 gsm|lte level=3
10-07 08:25:22.051 4454-4652/? D/NetworkController.MobileSignalController(0/1): getMobileIconGroup(): 13
10-07 08:25:27.591 3668-3687/? D/BatteryService: !@BatteryListener : batteryPropertiesChanged!
10-07 08:25:27.591 3668-3687/? D/BatteryService: level:100, scale:100, status:5, health:2, present:true, voltage: 4305, temperature: 285, technology: Li-ion, AC powered:false, USB powered:true, POGO powered:false, Wireless powered:false, icon:17303446, invalid charger:0, maxChargingCurrent:0
10-07 08:25:27.591 3668-3687/? D/BatteryService: online:4, current avg:170, charge type:1, power sharing:false, high voltage charger:false, capacity:280000, batterySWSelfDischarging:false, current_now:178
10-07 08:25:27.591 3668-3668/? D/BatteryService: Sending ACTION_BATTERY_CHANGED.
10-07 08:25:27.601 3668-3668/? I/MotionRecognitionService: Plugged
10-07 08:25:27.601 3668-3668/? D/MotionRecognitionService: cableConnection= 1
10-07 08:25:27.601 3668-3668/? D/MotionRecognitionService: setPowerConnected | current backoffstate = 1024 , state =1024
10-07 08:25:27.601 3668-3668/? D/MotionRecognitionService: skip setTransmitPower.
10-07 08:25:27.611 4454-4454/? D/KeyguardUpdateMonitor: received broadcast android.intent.action.BATTERY_CHANGED
10-07 08:25:27.611 4454-4454/? D/KeyguardUpdateMonitor: handleBatteryUpdate
10-07 08:25:27.611 4454-4454/? D/PowerUI: priorPlugType = 2 mPlugType = 2
10-07 08:25:27.641 4454-4454/? D/BatteryMeterView: ACTION_BATTERY_CHANGED : level:100 status:5 health:2
10-07 08:25:27.641 4454-4454/? D/BatteryMeterView: ACTION_BATTERY_CHANGED : level:100 status:5 health:2
10-07 08:25:28.541 4454-4652/? D/NetworkController.MobileSignalController(0/1): onSignalStrengthsChanged signalStrength=SignalStrength: 99 99 -120 -160 -120 -1 -1 18 -104 -9 152 -1 2147483647 0x3000 gsm|lte level=3
10-07 08:25:28.541 4454-4652/? D/NetworkController.MobileSignalController(0/1): getMobileIconGroup(): 13
10-07 08:25:31.101 4454-4652/? D/NetworkController.MobileSignalController(0/1): onSignalStrengthsChanged signalStrength=SignalStrength: 99 99 -120 -160 -120 -1 -1 19 -104 -9 116 -1 2147483647 0x3000 gsm|lte level=3
10-07 08:25:31.101 4454-4652/? D/NetworkController.MobileSignalController(0/1): getMobileIconGroup(): 13
10-07 08:25:31.231 3668-9995/? D/SSRM:s: SIOP:: AP = 310, PST = 342 (W:24), CP = 252, CUR = 180, LCD = 82
10-07 08:25:31.241 3668-9995/? D/ConnectivityService: returning getNetworkInfo for network type 1 : [type: WIFI[] - WIFI, state: DISCONNECTED/DISCONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true]
10-07 08:25:32.281 4454-4652/? D/NetworkController.MobileSignalController(0/1): onSignalStrengthsChanged signalStrength=SignalStrength: 99 99 -120 -160 -120 -1 -1 19 -104 -9 144 -1 2147483647 0x3000 gsm|lte level=3
10-07 08:25:32.291 4454-4652/? D/NetworkController.MobileSignalController(0/1): getMobileIconGroup(): 13
em...@gmail.com <em...@gmail.com> #26
Also happens in Moto E Gen 2 Android 6.0 provider Personal Argentina.
ed...@gmail.com <ed...@gmail.com> #27
Seen on many different devices with Android 5 and Android 6: all of them spam system messages crap like "E/NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UID' not found" or "E/NetdConnector: RMV <- {200 14196 Remove success}".
I think it is pretty impertinent to close this issue and call it "obsolete" if nobody does anything about it. Logcat sometimes is almost unusable.
I think it is pretty impertinent to close this issue and call it "obsolete" if nobody does anything about it. Logcat sometimes is almost unusable.
cl...@gmail.com <cl...@gmail.com> #28
Same issue on LG G3. Really pissing off.
d....@gmail.com <d....@gmail.com> #29
The "NetlinkEvent::FindParam(): Parameter 'UID' not found", happens about 3 times per minute even on Vodafone Smart Prime 7 (ZTE VFD.600), stock rom, unrooted, Android 6.0.1
[Deleted User] <[Deleted User]> #30
"NetlinkEvent::FindParam(): Parameter 'UID' not found" found in Samsung note 4.
pa...@gmail.com <pa...@gmail.com> #31
I have the same problem on Huawei Honor 5x, Android 6.0: "NetlinkEvent::FindParam(): Parameter 'UID' not found"
jv...@gmail.com <jv...@gmail.com> #32
Same problem in LG G3
ma...@gmail.com <ma...@gmail.com> #33
I have the same problem too, also on LG G3
ha...@optus.com.au <ha...@optus.com.au> #34
Same on Nokia 6 OS 9
Description
attached is a catlog of the error and a screenshot of the output of the command *#*#4636#*#* that shows the errors on the gsm and netlink connection.
Please assing this issue as high priority as it's getting common on gingerbread.
a link to a verizonwireless report
a link to an androidforums report
a link to a xdadevelopers report
Thanks