Is my "hal_process_report_ind: Poor product quality: 11" what to worry about?

Question

I get this error in LogCat while dev is running. It looks like a hardware malfunction. It? What is the reason for this? I tried to find, but only found people talking about cameras. This is on Motorola Razr M. My device is very bizarre (feedback often lingers when unlocking and freezing during the game), and I wonder if this is due to this. Thanks!

PID TID Application Tag Text 698 710 qcom_sensors_hal hal_process_report_ind: Bad item quality: 11 

(with some context)

 06-30 09:32:52.693: D/PowerManagerService(698): acquireWakeLock flags=0x1 tag=AlarmManager 06-30 09:32:52.703: D/PowerManagerService(698): acquireWakeLock flags=0x1 tag=NlpWakeLock 06-30 09:32:52.703: D/PowerManagerService(698): releaseWakeLock flags=0x1 tag=AlarmManager 06-30 09:32:52.713: D/PowerManagerService(698): acquireWakeLock flags=0x1 tag=NlpCollectorWakeLock 06-30 09:32:52.723: D/PowerManagerService(698): acquireWakeLock flags=0x1 tag=NlpCollectorWakeLock 06-30 09:32:52.723: D/SensorManager(19005): caller of registerListener:19005,sensor type:1 06-30 09:32:52.723: I/Sensors(507): sns_pwr.c(383):sns_pwr_set_cpu_latency: hz 50 06-30 09:32:52.723: I/Sensors(507): sns_pwr.c(245):acquiring wakelock 06-30 09:32:52.723: D/PowerManagerService(698): acquireWakeLock flags=0x1 tag=NlpCollectorWakeLock 06-30 09:32:52.733: D/PowerManagerService(698): acquireWakeLock flags=0x1 tag=NlpCollectorWakeLock 06-30 09:32:52.733: D/PowerManagerService(698): releaseWakeLock flags=0x1 tag=NlpWakeLock 06-30 09:32:52.733: D/PowerManagerService(698): releaseWakeLock flags=0x1 tag=NlpCollectorWakeLock 06-30 09:32:52.743: E/qcom_sensors_hal(698): hal_process_report_ind: Bad item quality: 11 06-30 09:32:52.763: E/qcom_sensors_hal(698): hal_process_report_ind: Bad item quality: 11 06-30 09:32:54.595: D/ModemStatsService(1120): onSignalStrengthsChanged 06-30 09:32:54.595: D/ModemStatsService(1120): CDMA, mRssi=-93, mEcio=-140 06-30 09:32:54.595: D/StatusBar.NetworkController(919): onSignalStrengthsChanged signalStrength=SignalStrength: 99 0 -93 -140 -120 -1 -1 16 -117 -19 -70 2147483647 cdma 0 0 0 false 0 0 2 0 1 1 99 0 5 5 5 5 5 5 5 0 level=1 06-30 09:32:54.595: D/ConnectivityService(698): getMobileDataEnabled returning true 

Answer 1

You are right, this is due to sensors. Unfortunately, I can’t pinpoint the exact problem, but it’s most likely a data accuracy problem with your accelerometer.

Android is a very complex operating system, and it is unlikely that every piece of embedded code will function exactly as intended. I would not worry about this error.

Also, it is almost certainly not related to freezing your phone and has feedback delays. This is more like a problem with low RAM and processing power, with too many background applications opening up. Try uninstalling applications that you are not using.

Answer 2

It seems I don’t have the network location where I am, and this message appeared in my log, so I suspect this is part of my problem:

 12-16 09:07:19.739 1117 1500 V GmsNetworkLocationProvi: onSetRequest: ProviderRequestUnbundled, reportLocation is true and interval is 0 12-16 09:07:19.739 1117 1117 V GmsNetworkLocationProvi: SET-REQUEST 12-16 09:07:19.739 1117 1117 V GmsNetworkLocationProvi: in Handler: ProviderRequestUnbundled, reportLocation is true and interval is 0 12-16 09:07:19.849 594 607 E qcom_sensors_hal: hal_process_report_ind: Bad item quality: 11 

This sequence appears twice when you open Maps, so I’m sure that the message about the message quality refers to the location anyway, probably dropping the network location.

Answer 3

This seems to be a location error: http://www.reddit.com/r/Nexus5/comments/20g0vj/150_linessec_qcom_sensors_hal_logcat_spam_causing/ and it seems that this only works if you chose not to enable the report on location. And as soon as this happens, it stops only after rebooting the device.

Answer 4

Try clearing data for Google Play Services.

Go to Settings> Services> Google Play Service> Space Management> Clear All Data.
On my device, which stopped these messages for a while (and so far, even when they appeared, they are much less common).