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).
Related
MOD EDIT: links removed
Turn off your screen by shutting the case or auto-shutdown
Power Switch is a tool for devices with cases - somewhat like the SmartCover, it will turn off the screen when you shut the case. If you have a device with poor battery life, Power Switch can save tons of juice by switching it off entirely after a given amount of time asleep.
The app works best on phones using the proximity sensor. On tablets, the light sensor is the most efficient method of knowing that the case has been closed.
Features:
- Sleep seconds after shutting case
- Automatic shutdown (rooted devices only)
- Set up a schedule using Night Mode
- Configure sensor sensitivity
- Facedown to turn screen off
- Persistent notification
- Plays sound to let you know that the screen has turned off
The app has gone through an extensive testing process here at XDA under another name. Thanks to everyone who helped make it happen, you're the best!
However, this testing showed that some features of that app were not all that useful, and some were conspicuously absent. To save both you and us a lot of grief, we made the second-generation Killswitch.
Remember to adjust the light sensor sensitivity settings in a light environment for best performance, and use Night Mode if you are on a tablet with a poor ambient light sensor.
If you have any comments or suggestions, please use this thread or the in-app feedback tool. Please be aware that we ignore logs without descriptions.
Power Switch Lite
The Lite version of the app is exactly the same as the Pro, only the timers are restricted to a minimum of twelve seconds across all sensors.
Screens:
1.1.4
Added option to disable in landscape
Fixed issue with switching Night mode
Fixed many device specific bugs (Tab 7.7, 8.9, 10.1)
good luck
Another thread on this app? Good luck! I love all of your apps.
Sent from my SPH-D710 using xda premium
Thanks, enjoy!
Bump bump
App is on sale - only a dollar?
Going to try this on my ASUS Transformer Prime, hopefully it works
Should work fine... light sensor only though i think. Does the prime have a proximity sensor?
ftgg99 said:
Turn off your screen by shutting the case or auto-shutdown
Power Switch is a tool for devices with cases - somewhat like the SmartCover, it will turn off the screen when you shut the case. If you have a device with poor battery life, Power Switch can save tons of juice by switching it off entirely after a given amount of time asleep.
The app works best on phones using the proximity sensor. On tablets, the light sensor is the most efficient method of knowing that the case has been closed.
Features:
- Sleep seconds after shutting case
- Automatic shutdown (rooted devices only)
- Set up a schedule using Night Mode
- Configure sensor sensitivity
- Facedown to turn screen off
- Persistent notification
- Plays sound to let you know that the screen has turned off
The app has gone through an extensive testing process here at XDA under another name. Thanks to everyone who helped make it happen, you're the best!
However, this testing showed that some features of that app were not all that useful, and some were conspicuously absent. To save both you and us a lot of grief, we made the second-generation Killswitch.
Remember to adjust the light sensor sensitivity settings in a light environment for best performance, and use Night Mode if you are on a tablet with a poor ambient light sensor.
If you have any comments or suggestions, please use this thread or the in-app feedback tool. Please be aware that we ignore logs without descriptions.
Power Switch Lite
https://market.android.com/details?id=fahrbot.apps.powerswitch.demo
The Lite version of the app is exactly the same as the Pro, only the timers are restricted to a minimum of twelve seconds across all sensors.
Screens:
Click to expand...
Click to collapse
wow exactly as described on tab 7.7
thank you!!!
why does Power Switch Pro require full internet access permissions?
PhilDX said:
why does Power Switch Pro require full internet access permissions?
Click to expand...
Click to collapse
Its for licensing, flurry and logs. Logs only send if you click "write to us".
Anything to report?
Anything to report?
Any issues or suggestions?
Gonna try this with S3 FlipCover.
Be sure to use the proximity sensor.
Sent from my GT-P7500 using XDA Premium HD app
Downloading for galaxy S. Thanks for good work
OK, enjoy!
Sent from my GT-P7500 using XDA Premium HD app
ftgg99 said:
Be sure to use the proximity sensor.
Sent from my GT-P7500 using XDA Premium HD app
Click to expand...
Click to collapse
I bought the app for my S3 with flip cover.
Would love to see a way to "combine" light and prox sensor, and also to set timers to 0 sec's.
Other than this, great app! Congrats
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
Hi Guys,
I've experienced that Z1 has a very low flash-light when compared to other phones like nexus 4. I've tried many flash-light applications but even though issue isn't resolved. When capturing image using camera app the flash-light is giving much brighter light but if i use it as torch the flas-light is very low. Did anyone experience this issue? Please help.
I am using this flashlight app:
https://play.google.com/store/apps/details?id=ch.smalltech.ledflashlight.free
It goes like this: after i start the app the led is powered on, then i push the power button of the phone so i do not accidentally type anything on the touchscreen (this way the phone is locked).
Here comes the interesting part: when i push the power button in order to wake up the phone (while flashlight is still working - camera led on), for half of a second, the camera led gets brighter than in the normal use of the flashlight app, then it goes back to the initial state (less bright). :-/
What is happening?
Has anyone found a flashlight app for Z1 that provides more light / uses the camera led to its maximum brightness capabilities?
TeslaLED. Same developer as Nova Launcher.
[email protected] said:
Hi Guys,
I've experienced that Z1 has a very low flash-light when compared to other phones like nexus 4. I've tried many flash-light applications but even though issue isn't resolved. When capturing image using camera app the flash-light is giving much brighter light but if i use it as torch the flas-light is very low. Did anyone experience this issue? Please help.
Click to expand...
Click to collapse
Same here. I think they put the flash light to close to the lens of Z1 and that why the pictures capture to much brightness in wrong time.
nbell13 said:
TeslaLED. Same developer as Nova Launcher.
Click to expand...
Click to collapse
The same result. Little brightness from the led.
Sent from my C6903 using XDA Premium 4 mobile app
bogdan wst said:
The same result. Little brightness from the led.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It doesn't use max brightness to avoid overheating. If you want a bright flashlight, buy a Surefire. Relying on a phone's camera flash is silly.
Ok. I'll keep that in mind. Thank you.
Sent from my C6903 using XDA Premium 4 mobile app
Any updates on this? Can I increase the brightness if I'm rooted?
Sent from my C6903 using XDA Free mobile app
npoljak said:
Any updates on this?
Click to expand...
Click to collapse
Bump
When I turn the flashlight on my Z1 I get a very low light and its blinking and going from brighter to lower light until it is gone completly like it is loosing contact or something, when i yry to take a picture the flash is working properly. Can somebody help me pls?
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
Hi
I've just installed cpuz ver 1.11 in my device and to my surprise, the app is showing always changing values at various sensors readings.
Especially, the gyroscope readings are changing randomly EVEN if the device is placed on the table and still.
Could this be a problem with hardware?
I've tested the same app on my friend phone but his phone does not have this problem.
Can someone please confirm whether all Moto G2 devices has this problem?
I've attached a screenshot, in case you don't understand what exactly I'm talking about.
Sent from my XT1068 using XDA Free mobile app