[Q] Papago X5 Sensor Bug - Android Software Development

Hi
I discover that PapagoX5 for android causes a sensor to activate and never sleep even after i exited Papago. The problem that I discover is described as follows:
1. I start Papago and run for a few minutes, let say 5 min.
2. I exit properly.
3. Half hour later I check battery usage using battery history (or spare parts).
4. Papago GPS use is 4m 50s, CPU use is 5m 20s, sensor use is 30m 20s.
5. I try run compass, drop game, camera, and every other apps that use sensor.
6. Another 15min pass, check battery history again, Papago GPS use 4m 50s, CPU use 5m 20s, sensor use 46m 35s.
7. Sensor battery use also got records of the compass, drop game, camera, etc. but they don't show increase after I stop those apps.
It appears that Papago activated a sensor and this sensor never shut down, lurking in the background draining battery all the time. I even tried flight mode, but the Papago sensor still active. Not sure how to proceed from here. So I just restart the phone and the problem goes away...
Btw, I recently notice that Asphalt 5 game also got the same problem. A sensor is activated and never go away. Is this the same problem or a different one I am not sure..
More information: I am using samsung galaxy s i9000 international.
Hope some expert here can advise how to fix this bug...

Related

GPS was not closed.

I found that the some GPS tool will not actually close GPS when it was terminated (Google maps seems OK), even when the phone was switched to fly mode. Battery was drained very quickly in this situation. Is there any too can check current status of GPS and also manage it?
How did you found out ?
Normally, I'll put phone to fly mode during night and it will consume about 5% power. But if I used GPS in that day, the power consumption would be ~20%.
flypp said:
Normally, I'll put phone to fly mode during night and it will consume about 5% power. But if I used GPS in that day, the power consumption would be ~20%.
Click to expand...
Click to collapse
I can't provide much more details, but I'd rather tell you to look elsewhere for the solution to that huge battery drain, as from what I know it's very unlikely to be gps's fault.
The gps is turned off by the device whenever you put the hd2 to sleep with the power button, in fact every app that uses it also loses the location (see navicomputer, nonigpsplot, and tomtom) when you turn off the display.
So, even if the app "forgot" to turn off the gps, it would be turned off when you press power button.
Just to make sure, have you checked with a task manager if the gps is really closed? Some apps (GPS or otherwise) dont really close when you close them, they merely move to the background.
The suggestion GPS is always closed when you sleep the device is not correct, some apps prevent real sleep, exactly to prevent loss of fix.
I'm sure that all GPS related software was closed. The answer from HTC customer support was to remove the buggy GPS software.

Battery Use says Camera at 98%

Why? Cuz I turned on to geo tag my photos? Why in the hell is it always running? I assume turning it off will help this. Anyone else see it happening?
Dont see this problem boss... Could it be rom related, Plz post rom details and basic data.
I am seeing this as well on fresh-2.1.2. I do not have geo on though. Only happens once the camera has been used.
-------------------------------------
Sent via the XDA Tapatalk App
That bar indicates approximately how much of the battery capacity that has thus far been used has been because of each app.
If you turn the phone on, take a couple of pictures, and turn it off, the camera will have used almost 100% of the used capacity.
I have this same problem. I've tested the hell out of it and figured this out:
1. This occurs on ALL Sprint 2.1 ROMs when Geotagging is enabled.(This does NOT occur on Legend/MT3G slide roms)
2. When you launch the Camera app with geotagging enabled, you are screwed. When you check the battery stats at first Camera will say like 10% or so, but come back and check it like 30 minutes later and you will see it slowly creeping up to 95-99%.
3. Camera is NOT running. You can't find it in a task killer and it does not show up in top.
4. Even if you launch camera and then turn off gps through the widget or through settings after you are finished camera will still climb to 98%, the only way to get it to stop is to reboot the phone.
5. It's not a glitch in the battery display, camera really IS somehow eating your battery, it will die in like 4 hours.
6. If you launch camera and take ONE photo and then close it out and check it again like 4 hours later even after HEAVY use camera will still be shown as using 98%.
So, since I like the geotagging feature and I do not want to reboot my phone after every use of the camera, I went to zenexp and do not experience this problem anymore.
How do you know its not running? have you used auto killer? And if the service/app is closed out theres no reason why it would be showing 95 percent unless the battery didn't update the statistics immediately thus making you think it is creeping up to 95.
**Edit** you will never used over 100 percent of your battery its basically a pie chart in number form if its using 95 percent of the battery then you only used 5 percent of your phone when the camera was activated and the camera used 95 percent of it at the time.
Powers16 said:
How do you know its not running? have you used auto killer? And if the service/app is closed out theres no reason why it would be showing 95 percent unless the battery didn't update the statistics immediately thus making you think it is creeping up to 95.
**Edit** you will never used over 100 percent of your battery its basically a pie chart in number form if its using 95 percent of the battery then you only used 5 percent of your phone when the camera was activated and the camera used 95 percent of it at the time.
Click to expand...
Click to collapse
Yes, I know it is odd. I do use auto killer, and I can GUARANTEE you that camera was not running. I tried ATK, auto killer, and even running ps and top. It truly is not running and yet is using the battery. I absolutely promise you this. And if I run camera and close it at first it says 10%. Check it 10 mins later it says 22%, check it 20 mins later it says 50%, check it one hour later it says 97%, just tested it. The entire time it is climbing camera does NOT appear in task killer auto killer, ps, or top, and the last two commands will show every PROCESS that are running, not just "services" and "apps".
I even specifically said that I extensively used the phone and camera still said 95-99%. I played 2 hours straight of replica island, and normally(if I don't launch camera) after 30 mins of replica island it is using at least 30%.
Truly there is a bug somewhere. What I think is going on is that camera is initiating a GPS connection, and then when Camera closes it does not disconnect the GPS signal properly so it is in a state where it is still locked to satellites but frozen.
This has occurred, for me, on every Sprint 2.1 based rom when Geotagging is enabled.
I have the same problem, super annoying!
The rom is the official Sprint 2.1 rom. And I don't run any task killers. It is very annoying. Kills the battery fast.

Desire HD Sensor Usage, Battery Drain

Greetings,
Just wondering if anyone has noticed that if you use Spare Parts, go to Sensor Usage, and under "Android System" it seems to use a ton of sensor, without any real explanation as to what it's all about.
I had this problem with my Galaxy Tab and the Gallery3D application (it also happens on the DHD if I'm not careful) and it drained the battery like crazy.
Any explanation, fix, or workaround? Any thoughts would be appreciated
That's really not an issue, you notice that when your sending a SMS and you hold it landscape the orientation changes? That's because a sensor told your DHD to switch the orientation.
Without them being on all the time your smartphone wont be so smart as you'd have to change the brightness of your display every time it gets dark, you'd have to manually change the orientation. You get the picture.
RE: Sensor Usage and Accelerometer
Hi,
I am aware of that but that is not the issue. On all other android phones and devices (I have 2 android tablets and 3 other phones) the Sensor Usage is not like that. It won't be activated even when the phone is "off" or in hibernation mode.
Like I said, I used to have this issue with my Galaxy Tab which caused it to use alot of battery (Gallery 3D App) and I did have a workaround which improved battery life significantly.
Any other suggestions would be kindly appreciated.

**touchless sleep/wake control!! (app - gravity screen)**

Waking up a device involves the hassle of picking up our device, reaching for the power button, and then pressing it to turn the screen on.
However, using the gyrometer and proximity sensors, gravity screen wakes your device up right as you pick it up, or hover your finger over the proximity sensor!! Neat!
Pros :
Small and light-weight
Doesn't hog up on RAM
No appreciable effect on battery life!
Various options to tune the settings to your liking!
Helpful for devices with broken power buttons
Cons :
None. You say?
This app has been around for a while, and it works seamlessly with our device.
All credits to the developer Plexnor. It is his work. Be generous, and buy him a beer if you may.
Play store link :
https://play.google.com/store/apps/details?id=com.plexnor.gravityscreenofffree&hl=en
Here's a video on the same : :laugh::laugh:
https://youtu.be/NJ6kgaDIwCU
[APP][2.2+] Gravity Screen > Turn Screen On/Off Automatically - Keep Screen On
It doesn't seem to show up on the stock battery consumption screen but on BBS and Gsam, GravityScreen was consuming almost 7 to 12% battery per day.
Maybe I'm doing something wrong but I even turned off the wake by motion and all other accelerometer related services and kept only Proximity Screen On and Proximity Screen Off options ON.
Any suggestions?
Sent from my Nexus 5
Achilles. said:
It doesn't seem to show up on the stock battery consumption screen but on BBS and Gsam, GravityScreen was consuming almost 7 to 12% battery per day.
Maybe I'm doing something wrong but I even turned off the wake by motion and all other accelerometer related services and kept only Proximity Screen On and Proximity Screen Off options ON.
Any suggestions?
Sent from my Nexus 5
Click to expand...
Click to collapse
same here...i have done all suggested tips...
[4] Q: I'm experiencing high battery usage, why?
A: The app should use about 6 percent extra energy per day if you are not using too much the Turn Screen On by Motion feature. If you frequently lay your phone face up on a table and the Turn Screen On by Motion Timeout is too long, the battery consumption can be much higher. Because the CPU has to be constantly analyzing the data of to acceleration sensor to catch the movement when you lift up the device. Thus if you want to reduce the battery usage it's recommended to keep your phone often lying face down when it's on a table. Because in this situation the proximity sensor is responsible for turning the screen back on which uses much less energy. Moreover, please, keep in mind that the android en-built battery consumption measurement can show much higher results, because it shows the battery usage relatively to another apps. If the phone was not in use or the measurement period was short, it looks like my app uses too much energy however there was not too much energy used all together.
Yes I frequently lay the phone face up for see the notification led....
ironia. said:
same here...i have done all suggested tips...
[4] Q: I'm experiencing high battery usage, why?
A: The app should use about 6 percent extra energy per day if you are not using too much the Turn Screen On by Motion feature. If you frequently lay your phone face up on a table and the Turn Screen On by Motion Timeout is too long, the battery consumption can be much higher. Because the CPU has to be constantly analyzing the data of to acceleration sensor to catch the movement when you lift up the device. Thus if you want to reduce the battery usage it's recommended to keep your phone often lying face down when it's on a table. Because in this situation the proximity sensor is responsible for turning the screen back on which uses much less energy. Moreover, please, keep in mind that the android en-built battery consumption measurement can show much higher results, because it shows the battery usage relatively to another apps. If the phone was not in use or the measurement period was short, it looks like my app uses too much energy however there was not too much energy used all together.
Yes I frequently lay the phone face up for see the notification led....
Click to expand...
Click to collapse
Update it and try using only the Proximity wake and sleep..
Battery drain is minimal. [emoji16]
Sent from my Nexus 5
Achilles. said:
Update it and try using only the Proximity wake and sleep..
Battery drain is minimal. [emoji16]
Sent from my Nexus 5
Click to expand...
Click to collapse
i will try, but i have already updated app, i can't live without table mode

Usage of proxomity sensor

How come the usage of proximity sensor under Android System is much higher whilst on mobile network than on wifi?
I think that plays a role in sub optimal battery life..
Here is a quick screenshot.
Proximity sensor doesn't have anything to do with your network connection. Other than when you're at home/work and connected to wifi, your phone is probably laying face up somewhere (proximity sensor off) and when you're not connected to wifi (you're out and about in the world) your phone is in your pocket/bag and the sensor is covered (on).
Just guessing.
According to Elixir, somehow it lists 2 proximity sensors?? using 0.1mA each, so 0.2 mA together. It doesn't say at what voltage, but at nominal battery 4 volts, you would use about 0.8 mW of power per hour. After 1000 hours of usage you would end up using 0.8 W of power and battery capacity is about 12-13W. I don't think you should worry about that sensor too much. Also according to Elixir, the biggest power users are rotation and orientation sensors (there are few) at about 1.5mA each. If you compare that to power used by screen and radios, the sensors use meaningless from power usage point of view. IMO the biggest culprit are programs running in the background and communicating with servers and there is no easy way to stop it.
akira888 said:
How come the usage of proximity sensor under Android System is much higher whilst on mobile network than on wifi?
I think that plays a role in sub optimal battery life..
Click to expand...
Click to collapse
because your phone is in your pocket/ purse/backpack more when you're out and about, when at home posted up it's sitting on the counter/couch/table. Why does this matter? Settings>Display>Keep screen turned off
"Prevent the screen from turning on accidentally while the device is in a dark place such as a pocket or bag"
This means the proximity sensor is more active in your pocket. And typically when you're on WiFi, it's not in your pocket.
Just a guess but I believe I'm right.
Sent from my SM-G955U using Tapatalk

Categories

Resources