Database Develop

[Q] Proximity and the ambiant light sensor doesn't work

does anyone experience proximity and ambiant light sensor issues mines wont work. first i thought it was broken and bought a new sensor replaced it and it still wont work. the headphone jack and speaker works ok but not the sensors anyone? I also tried the sensor reading apps to see if its working. proximity wont show anything and the light sensor gives me between 4700-5000 lux but wont change no matter what light condition any help i cant even make a phone call without headphones anymore

What kind of rom are you running?
If you replaced it then its not a hardware issue it software then
Sent from my GT-I9000 using xda app-developers app

well ı've been using pa v2.54 before and flashed lots of roms in this 3 months i even flashed official rom went stock but still no luck :/

Really strange even with a new sensor and stock rom isnt working maybe the socket isnt good maybe a problem with the motherboard i dont know i thought it might have been a rom problem maybe the people here had a similar issue and they might help i wish you luck and i hope you find a fix
Sent from my GT-I9000 using xda app-developers app

thanks if it was due to the socket im guessing that the speaker and the headphone jack would also not respond... but yeah its a minor issue but really annoying

So I realized if I unplug the sensors the reading will still continue bounce between 4500-5000 lux so im guessing its not an issue of the sensor itself there should be something else... Right?.. Please back me up can be it be caused by the drivers of the sensors ?

And i found this (last post) http://forum.xda-developers.com/showthread.php?t=1446005&nocache=1

Yes that picture in the last post could be it it could be a motherboard problem like that just be careful if you dont know what your doing
Sent from my GT-I9000 using xda app-developers app

Barometer and temperature sensors

Hello everyone!
Reading the specifications of this Moto X 2014, I saw that there are sensors of the barometer and temperature. In addition to helping the GPS signal, these sensors are used to monitor a more reliable weather forecasts? The software of the Moto X (more precisely, the stock weather application) also uses these sensors?
Thanks in advance!

There is no app that comes stock that uses these sensors for weather.

Are the sensors actually able to be used by apps for external reading? Sometimes the temperature sensors are just for the inside of the phone. Anyone tested these sensors and can confirm they read external?
Sent from my XT1096 using XDA Premium HD app

[Q] Direction/orientation in Google Maps wrong

Hi all,
I've found that in the Google Maps app, the direction that the app thinks I am facing is almost invariably wrong, and often varies wildly even when I'm not moving. I think it is related to the rotation vector sensor (Sensor.TYPE_ROTATION_VECTOR) but I was wondering if others had experienced similar problems.
I've looked at the various sensors (and compared them to a Nexus 5) and two stand out: the Uncalibrated Gyro (Sensor.TYPE_GYROSCOPE_UNCALIBRATED), and the Rotation Vector (Sensor.TYPE_ROTATION_VECTOR).
The Uncalibrated Gyro seems to sit with a z-axis value of 1.17 rad/s, and the rotation vector *sometimes* seems to stick at a high value too.
Anyway, the question is:
(1) Do other people find that Google Maps tends to detect them pointing in the wrong direction, or turning when they are in fact not turning, and
(2) Do other people find that the rotation vector sometimes sticks at a weirdly high value (if they have the tools to check: I wrote one to check myself, which I can attach if desirable but being unknown I don't know if anyone would trust to install it =)
Cheers.

This may seem a basic question, but did you try calibrating the compass via the service menu?
Enter *#*#7378423#*#* in the dialler.
Service tests
Compass
Follow the on screen guide.
That always seems to correct any "creep" or odd readings with my compass and gyro. You can also check the gyro from the service test menu.
Sent from my C6603 using Tapatalk

kingvortex said:
This may seem a basic question, but did you try calibrating the compass via the service menu?
Click to expand...
Click to collapse
Cheers, I did do that but it didn't seem to make a difference. However, now GMaps seems to be working pretty well so that's good. (It's done that before, but maybe this time it will last). However, the game Ingress is still having problems (which it doesn't have under Stock). Like GMaps, it tries to detect the direction you are facing. On Stock 4.4.4, Ingress does a tolerable job of detecting direction of facing - it mostly gets it right. However, using CM11 the behaviour is really weird: turning the phone has no effect until a tipping point, at which it is detected that I've done a sudden 180, and if I keep turning the phone it eventually happens again. Doing the phone-calibration-twirl has no effect in this case. (Note: that is rotational movement with the phone laying flat on a table, and a metaphorical tipping point. I'm not standing the phone up until it tips over)
Maybe related, but maybe not: Having done some more testing with a few ROMs and kernels, what I've found is that CM11 (both official and _infected builds, with both the included kernel or the multirom-modified kernel) don't provide a TYPE_GYROSCOPE_UNCALIBRATED sensor (where as the stock 4.4.4 ROM does).
That said, Ingress doesn't appear to *use* the TYPE_GYROSCOPE_UNCALIBRATED (instead only using LINEAR_ACCELERATOR, ROTATION_VECTOR and MAGNETIC_FIELD) so I'm a bit confused. (Edit: I believe these are the sensors being used based on the hex values being passed to getDefaultSensor in the smali of Ingress.)
The sensor results for both stock and CM11 look to be about the same, with the exception of the 'Uncalibrated Gyroscope' not being present in CM11 whereas it is present in stock 4.4.4. I think that sensor missing is probably a bug, but I'm not exactly sure where to report what is probably a device-specific bug for CyanogenMod.
tl;dr;
Calibration movements might have fixed it in Google Maps, but Ingress is still having problems in CM11 (but not Stock 4.4.4).
I think there is a sensor missing in CM11 that is in stock, and that's probably a bug. Where should a device-specific yuga bug in CM11 get reported?

This may seem a basic question, but did you try calibrating the compass via the service menu?
Enter *#*#7378423#*#* in the dialler.
Service tests
Compass
Follow the on screen guide.
That always seems to correct any "creep" or odd readings with my compass and gyro. You can also check the gyro from the service test menu.
Sent from my C6603 using Tapatalk
Sent from my C6603 using XDA Free mobile app
---------- Post added at 10:03 AM ---------- Previous post was at 09:19 AM ----------
Sorry guys for this copy paste, my mistake.
I have exactly the same problem.
Calibration do nothing.
Sent from my C6603 using XDA Free mobile app

[Q] problem with compass and gyroscope

Hello,
After replacing the screen of my xperia Z1 in a mobile store,the Z1 doesn’t find the compass hardware and the gyroscope doesn’t work yet. Is their a cable missed or some hardware is breackdown?
Thank you for help

I have also had same problem after my lcd change. I have solved my problem. Can you check and tell all the sensors are not working or only the compass and gyroscope.
Sent from my C6902 using XDA Free mobile app

After having my lcd replaced I noticed my sensors stopped working. Well actually compass has stopped working completely but gyroscope, accelerometer, proximity, and light sensor sometimes stop working, and after a reboot sometimes they work for some time.
Also I noticed that in antutu benchmark app it says not supported for not working sensors, except for once when it showed me the right model for the magnetometer.
It'd be very helpful if you told us what you did so we can try the same

I also had the same problem which you described. In my case compass was the main problem. In my case Compass won't show any reading and other sensors will also stop working once I checked the compass.
The compass was in the main flux cable. Once I have replaced the cable my compass and others sensors also started fine. I suggest you to replace the main flux cable.
Sent from my C6902 using XDA Free mobile app

Hello,
Thank you very much for your answers.
The main cable has dimension of the Xperia Z1 ?
The cable picture in ebay store :
http://i.ebayimg.com/00/s/MTIwMFgxNjAw/z/njcAAOxycgVTjKnW/$_57.JPG
Thanx

Yes that was the cable. Compass present on the opposite side of the keys area. You need to change the cable.
Sent from my C6902 using XDA Free mobile app

[Q] Does anyone know what 'sensors.qcom' is?

Gsam Battery Monitor is reporting something called 'sensors.qcom' as being one of the things that is using up my battery (only 2.1%) but it is the only thing on the list that xda and google hasn't been able to explain to me; aside from some forums linking it to the accelerometer. The thing is, I am not using anything that requires the accelerometer... The battery life on the phone is very good, but this might be kepping it from being great.
Can any of you good people enlighten me as to what sensors.qcom is and how it can be quelled?

sensors.qcom is a process used to activate the sensors on all qualcomm based phones, sounds to me like either you're using an app that is using the sensors often, or an app that is using the sensors doesn't shut down the sensor once it finished using it.

meaniez said:
sensors.qcom is a process used to activate the sensors on all qualcomm based phones, sounds to me like either you're using an app that is using the sensors often, or an app that is using the sensors doesn't shut down the sensor once it finished using it.
Click to expand...
Click to collapse
Thanks for the reply. I don't think I am using any apps that need sensors but I will examine my apps and see what turns up.
Could it be the camera? Aside from the camera the apps I use don't require anything but the touchscreen (tap-to-wake is not on and neither is adaptive brightness).