Database Info

[Q] GPS won't lock if rear camera is in use, otherwise GPS works great

I've searched high and low, but haven't been able to find a solution to this issue, hopefully somebody here has a good answer for this one.
I'm trying to run Waze in the foreground and DailyRoads Voyager in the background while driving, but any time DRV is running, Waze can't get a GPS lock. If I shut down DRV, I get a GPS lock quickly and without issue. The issue doesn't appear to be app related, as I can generate the same symptoms using other camera apps and 'gps status'.
I've seen a few references on other forums where people with S3's are having the same issue, but I haven't found a resolution yet. I'm running the current OTA build, never rooted/tweaked.
Any ideas?

PDXKris said:
I've searched high and low, but haven't been able to find a solution to this issue, hopefully somebody here has a good answer for this one.
I'm trying to run Waze in the foreground and DailyRoads Voyager in the background while driving, but any time DRV is running, Waze can't get a GPS lock. If I shut down DRV, I get a GPS lock quickly and without issue. The issue doesn't appear to be app related, as I can generate the same symptoms using other camera apps and 'gps status'.
I've seen a few references on other forums where people with S3's are having the same issue, but I haven't found a resolution yet. I'm running the current OTA build, never rooted/tweaked.
Any ideas?
Click to expand...
Click to collapse
This is a seriously random suggestion, but did you try turning off geotagging in the main camera app?

aooga said:
This is a seriously random suggestion, but did you try turning off geotagging in the main camera app?
Click to expand...
Click to collapse
I just double-checked, and GPS tagging was already turned off in the stock camera app. Thanks for the idea though!

Can anybody else confirm if they see this behavior as well?
Since my first post I've tried rooted OTA, ran numerous CM10.1 builds (doing full wipes in between), leanKernel, testing along the way all without any real success. It seems a little hit and miss, on occasion (maybe 10% of the time) it seems to work, but in those times GPS still takes 5-10min to get a lock usually has less accuracy than when using GPS apps alone w/o the camera on.
When the camera isn't in use, I typically get a GPS lock in <30 sec (sometimes in just a few seconds).

[Q] May be a BUG in Camera

First of all I must give a big THANKS to Albinoman and all who supported him in producing this ROM.
Recently I found one BUG, I have no idea if it is known issue. I tried to search the same but couldn't find any answer.
What I did was pulling down notification bar and switched on Torch, after the time limit Torch goes OFF but in the notification bar it is shown as ON. So far so good. Now if I switched on Camera it gives Camera Error, Can't connect to Camera. This error comes even if the torch is ON.
Build Date
Thu May 9 17:58:04 PDT 2013.
On BADASS
I will try the May 17th version now and POST the error again. I
I just want you to know that this is what I got. Anyways the ROM is good except for the Battery issue. Someone said ROM has nothing to do with any Battery consumption, but I tried with a different ROM earlier and its Battery life was good.
Also tried upgrading to May 17th, I know change log says nothing about Camera, but still I tried first without upgrading to Camera Sphere 4.2 and than with Camera Sphere 4.2 same issue found.
BTW I am S-ON.
Thanks
Love and regards
Prasad

prasad_m said:
First of all I must give a big THANKS to Albinoman and all who supported him in producing this ROM.
Recently I found one BUG, I have no idea if it is known issue. I tried to search the same but couldn't find any answer.
What I did was pulling down notification bar and switched on Torch, after the time limit Torch goes OFF but in the notification bar it is shown as ON. So far so good. Now if I switched on Camera it gives Camera Error, Can't connect to Camera. This error comes even if the torch is ON.
Build Date
Thu May 9 17:58:04 PDT 2013.
On BADASS
I will try the May 17th version now and POST the error again. I
I just want you to know that this is what I got. Anyways the ROM is good except for the Battery issue. Someone said ROM has nothing to do with any Battery consumption, but I tried with a different ROM earlier and its Battery life was good.
Also tried upgrading to May 17th, I know change log says nothing about Camera, but still I tried first without upgrading to Camera Sphere 4.2 and than with Camera Sphere 4.2 same issue found.
BTW I am S-ON.
Thanks
Love and regards
Prasad
Click to expand...
Click to collapse
First off, just for future refference, there are 2 threads for Albino's rom already.
One is in the development section and one specifically for troubleshooting like this post is in teh Q and A Section. In the future please search for an existing thread rather than create a new one. This helps keep XDA a little more organized.
Now onto your problem...
I agree with everything you said. The torch and the camera don't work at the same time. The camera needs access to the LED to work, and obviously so does the torch. When the torch is already on the camera doesn't have access to it. It's like trying to put 2 keys into the same lock at once.
So since the camera app reads the device to see if the hardware it needs is available, when it finds the LED isn't available it shuts down. Even though the torch itself has timed out and has gone off, the torch app is still running and it controls the LED hardware until the app stops. so even though the light is off, the camera still can't control the LED hardware.
This is an overly simplified explanation, but this is what's going on.
We discussed in the dev thread that the camera app can run the led constantly during video so this isn't being done on purpose to prevent a reboot due to extreme battery drain. Its just a conflict for hardware resources. But since the camera can keep the led on there is no reason to have the torch app keep the led on, so there is no reason to really fix this bug.
Again though, the camera still fc's after the led times out because the torch app is still in control of the led hardware. So you have to remember to turn off the torch. That's also why the notification bar says the torch is on, even though the led is off. The torch app is still running in the background, which is what the notification bar is rally indicating.

Thanks I thought I should mention here if it is a Bug, BTW I was not aware how to start a thread within the Albino's ROM.
I can see only option Reply to someones thread. I found new thread here and hence the confusion.
Anyways thanks.
Love and regards
Prasad

[Q] proximity sensor issue

Hi. I have noticed some problems with proximity sensor on my sensation. When I make phonecall my screen wont shut down at all, i have tried vipers jb and albinos and then android1234567 4.3 so I think problem is with hw, anyone what I should do?

I have the same issue with the roms u mentionned, and in my case dunno if it's HW related because with skype and viber the proximity sensor works fine!

This helped me....sensors seem to work again
Hi,
i also (and a lot of people in fact) have the dreaded proximity and lightsensor problem. And indeed there seems to be no solution... People have been reseting and reflashing the Sensation till it drove them mad, without the problem solved... The problem seem to start when the Sensation was upgraded to ICS, and seems software related...
In my quest to solve the problem I stumbled upon a solution on the htcsensationforum.... and gues what, it seems to work for me, that is, the sensors work more often now.
I quote the solution, since i cannot paste the link;
Hi Tim.
I had the same problem. Phone is now fine after 24 hrs. Here's what I changed:
1. Turned off 'Pocket Mode'. Settings -> Sound -> Pocket Mode. No obvious change by itself
2. Turned off 'Fas tboot'. Settings -> Power -> Fast boot.
3. Turned off, removed battery, waited 30 secs and powered back on.
Simple as that! The proximity sensor was glowing occassionally after the upgrade, and that has gone away too. On the bonus front my battery life has never been so good (using about 60% of what it used to)!!!
Cheers.
Click to expand...
Click to collapse
Don't know how long this solution will hold, but it seems that the pocket mode and / or quickboot option are causing the problems... What i use to check the sensors behavior is the free app android sensor box, found in the playstore.
Maybe one of the devs here can take a look at this solution, and can come up with a permanent solution to have the proximity and lightsensor working normal again...:good:
Just my 2 pence on an old pain in the *ss problem, thanks go to Maestro @ htcsensationforum for his solution...
Cheers:cyclops:

Screen backlight stays on!

Hello!
My oneplus one is having this issue for a while now, When I plug it in and lock the device, there is a 60~70% chance that the display stays on but its just blank, I have to unlock it and lock it again to fix it.
Recently this also started happening when it was not charging and the screen would often stay on causing massive battery drain :/
This happens on every single rom all the way from CM11S up to CM13 and also oxygen os,...
Does anyone know what the problem is?
Thanks,
Noahvt

I have the same problem since I can remember, also looking for an answer.

I have a similar issue. Sometimes the screen stays on, but is dimmed. A simple double press of the power button resolves it (turn on full, turn off screen) but its mildly irritating. I have only noticed it since being on sultanxdas cm12 ROM. I had an issue with a notification LED app not working since a recent ROM update so uninstalled it. Maybe the issue was related to that app as I cant remember the issue occurring since I uninstalled it a few days ago.

Android Auto issues on ColourOS11

Ever since updating to ColourOS11, android auto has been freezing on me when the screen is off however activating the screen will unfreeze it.
Is anyone else experiencing this or if anyone knows a fix besides 30m screen timeout.

The issue's been mentioned on a couple of other threads, from what I've read it seems to be a Android 11 issue in general, not just limited to Oppo / ColorOS. Haven't seen a way to fix this so far, seems like one has to wait for an update to fix it and until then keep the screen on...

Craphead said:
The issue's been mentioned on a couple of other threads, from what I've read it seems to be a Android 11 issue in general, not just limited to Oppo / ColorOS. Haven't seen a way to fix this so far, seems like one has to wait for an update to fix it and until then keep the screen on...
Click to expand...
Click to collapse
Yea I had a look through some other threads. Turning off AOD and Fingerprint while screen off seems to somewhat work abiet still glitchly. Been in contact with Oppo who seems to only want me to send the phone into the service centre but I am waiting for Christmas break to be over and send it then otherwise hopefully a update by then but doubts.

I just had the issue, but by leaving it plugged in and letting the connection time out, it reset and connected. Took about a minute.

I finally got the ColorOS 11 update and now Android Auto is having this issue. Really rather annoying as I've only just got a new car and had Android Auto so was enjoying it!
Basically same issue where the car screen just locks up until you unlock the phone screen (i still get audio prompts for directions in google maps etc so Android Auto is still running). Seems to be a standoff between the OEM's and Google. Looking at other forums some OnePlus phones have the same issue (BBK group thing perhaps!)

Google answer...
[FAQ] Can't connect to Android Auto on Android 11 - Android Auto Community
support.google.com

I solved this issue going into developer options and activating the "keep screen on while charging" mode. The display will remain on, but with a very low brightness level.