I have been having this issue for some time now with my N4.
Ever since I had been playing Ingress I have been submitting portals with every chance I get. Some have been already submitted but in the recent month I have been geotagging potential portals left and right.
The issue I am having (I use CM10.1 nightlies with F.K now, but this persisted back in pure stock) is that the geotagging feature of the stock camera is very flaky.
It will work the first time with out an issue, but if I were to use it again soon on another area I wish to geotag I get an error when sending it to the NIA-OPs saying that the image has no geotagging data. I had to turn off the GPS, the geotag option, REBOOT THE PHONE, TURN ALL OF THEM BACK ON to get the ability to geotag a SINGLE image. Before having to repeat the process if I were to get another geotagged picture.
I went to custom roms thinking that it would solve my issues thinking that this was some sort of stock 4.2.2 issue that was resolved in the custom roms. It seems not to be the case unfortunately.
Is there some sort of fix out there that will allow proper geotagging without this persistent issue I keep having? I do not want to keep doing this whole cycle over and over again to make this work. Nor do I want to constantly manually geotag everything using software on my computer (Its very inconvenient.) every time I have an image to send in.
Has anyone had this problem? Is there a way to resolve it?
Related
For no reason my camera flash sometimes doesn't work. When it doesn't work neither will other camera app flashes nor apps to use flash as a flashlight. A phone restart fixes it but by then of course the scene you wanted to photograph is gone.
I am stock VZW 4.4.4 never rooted in a month old Asurian replacement phone. I seldom use flash so I don't know how often this issue occurs. I never happened on my original note 3 however again I seldom used flash. Also I have read this happens to many other people but no measure to cure or prevent it other than the slow restart process.
Anybody know a real fix? Thanks!
When taking pictures with the stock Motorola xamera app, I have a miserable time finding the shot. First I try to swipe to the left so the last image photographed comes onto the screen. THAT works, but then the screen freezes and I can't get out of it until I use the capacitive button to go back to the home screen. Then, when I go into the gallery to see the picture I just took, it is gone-like it was never there. However, occasionally some (not all) of these disappeared pix show up in the gallery hours later. I've tried deleting the app and then re-installing it, but it just doesnt seem to work correctly. Its the only thing about the Turbo which makes me want to throw it onto a nearby set of traintracks. Anyone else have the same issues or know what to do about it?
First off, I assume you mean camera (not xamera. correct me if I'm wrong). Second off, you shouldn't be able to uninstall it. If you installed updates for it via Google play then it might be a hardware problem. I would do a factory reset, and if it still doesn't work get it replaced. I don't know the details of the warranty, but from what I have heard it's quite extensive.
Thanks very much. And yes I meant camera....I guess I am mistaken-I didnt uninstall the entire camera app, just the updates to it. Still happening, but perhaps any bugs in the app might be fixed by the Lollipop update?
Lollipop isn't coming before February, and knowing Verizon I wouldn't bet on 2016 coming second
Got a new Note 4 SM-N910C after I replaced my old, as it had display issues (same model). Old and new phone are running 5.0.1., both are rooted. I restored all apps and data from the old phone on the new via Titanium-Backup.
When I open the carema app, or ANY other camera app on the new phone, it won't focus for approximateli 10-15 seconds - afterwards autofocus works snappy and accurately. When I close the camera app and reopen it, sometimes the autofocus reacts immediately, sometimes I have to wait again. After a longer period in which i did not use the camera, the initial lag always occurs.
Same issue when I use the test mode (#0# - Mega cam). In compairison the old model always works perfectly!
Resetting the camera app does not fix the issue. "Shaking" the phone does not fix the issue.
Does anyone know that issue, does anyone hab a suggestion how to solve the problem. I don't know whether this is a hardware (stuck af-motor??) or a software problem.
I thank you for every answer and suggestion in advance.
Are you on the stock ROM now?
Yes, everythin is stock.. just rooted via CF autoroot..
Did you have this problem before you rooted the device?
pimpl said:
Got a new Note 4 SM-N910C after I replaced my old, as it had display issues (same model). Old and new phone are running 5.0.1., both are rooted. I restored all apps and data from the old phone on the new via Titanium-Backup.
When I open the carema app, or ANY other camera app on the new phone, it won't focus for approximateli 10-15 seconds - afterwards autofocus works snappy and accurately. When I close the camera app and reopen it, sometimes the autofocus reacts immediately, sometimes I have to wait again. After a longer period in which i did not use the camera, the initial lag always occurs.
Same issue when I use the test mode (#0# - Mega cam). In compairison the old model always works perfectly!
Resetting the camera app does not fix the issue. "Shaking" the phone does not fix the issue.
Does anyone know that issue, does anyone hab a suggestion how to solve the problem. I don't know whether this is a hardware (stuck af-motor??) or a software problem.
I thank you for every answer and suggestion in advance.
Click to expand...
Click to collapse
It's a hardware problem, the camera lens abit loose. Some tried shaking it but only a temporary fix. Bring it to Samsung Service Centre for repair (if still have warranty). Mine had that problem and was fixed by Samsung.
Update:
I restored the device's factory settings, i.e. Recovery - Full Wipe, and flashed the Lollipop 5.0.1. stock rom via Odin. I did not not restore the camera app usting Titanium Backup.
The error still exists. Shaking the device causes no improvement at all and there are no strange noises during focusing detectable. I suspect that it is therefore definitely not a hardware failure.
.. Once again the error description:
If I do not use the camera for some minutes and open any camera app (e.g. native app, instagram, PS-express, whatsapp, Google Kamera, camera pro and also in the test mode (# 0 # - Mega Cam)) the picture is totally blurry and the focus seems to stay in the macro focus. When I try to set the focus point by touching the screen, the focus indicator appears but the focus does not change for approximately 10 seconds (again, in all camera modes and camera apps). After this "initial lag" the camera works perfectly fine. When I close my camera and open it after a short time, it focuses immediately. When I close my camera and open it after a longer time, initial lag occurs again.
This is extremely annoying.
I suspect that the system deactivates the camera ("deep sleep") so when opening the camera a full "initialization" (i.e. error checking, etc.??) is done every time. According to the Application Manager however, the camera app is active and uses the system's Ram when the lag occurs!
Can anyone - under 5.0.1. - confirm this behavior?
Again, I am very grateful for any kind of help and suggestions!
How difficult is replacing the camera? Is it simple?
Hi folks
I received my OP2 in July 2016, and this issue has been a mild periodic annoyance. As I approach the end of my warranty, I want to be 100% confident that this issue is software rather than hardware... (so rather than a fix, my highest priority is confirming that I do not have a hardware defect)
The issue is that the screen rotation will stop working for most, but not all apps (OnePlus Camera is the sole exception, it seems). It will rotate normally for a couple weeks and then I'll notice in some app, usually YouTube or Facebook first, that the screen orientation won't rotate anymore. Once I notice it in any app, no other app rotates either except the stock camera. I have been experiencing this symptom on-and-off for most of the time I've had the device, spanning multiple OOS releases (currently 3.5.8 and still happening).
A reboot fixes the condition, then it works fine for a week or two and comes back. OnePlus support suggested a factory reset, which I've done pursuing this issue before, and it didn't help (it immediately helped, obviously, but the issue did return on the same schedule as before).
I had my OP2 rooted, but still using the stock ROM otherwise, for several months (to be able to use Adblock). I reverted to 100% stock configuration pursuing this issue, it happened the same before/during/after the time it was rooted.
I have checked out the accelerometer with the app "Test Your Android" and watched the graph in the "gravity sensor" test. When the phone is in its non-rotating state and I rotate the phone, the graph lines cross but the app stays in portrait. This makes me think the phone knows it has rotated. I reboot the phone, redo the same test, and the graph looks similar except the app now rotates as well (ironic, really).
Is there a background service for "screen orientation" similar to how Play Services provides GPS information to other apps? If so, am I right in suspecting that the service responsible for answering the question, "what way is the device oriented currently?" is either not answering, or answering incorrectly?
I would prefer not to go to a third party ROM just to test this as I'm very happy with the current config of my device, other than this issue popping up from time to time. Any input is appreciated.
Thanks!
OOS has a tonne of services running under android system continuously. Screen orientation feedback might be one of them. I haven't used OOS in months. It doesn't seem like a hardware issue since a reboot solves it. If it is too frustrating then try testing it on a custom rom. You can switch back to stock once you are sure it was a problem in OOS or not.
utkarsh102 said:
OOS has a tonne of services running under android system continuously. Screen orientation feedback might be one of them. I haven't used OOS in months. It doesn't seem like a hardware issue since a reboot solves it. If it is too frustrating then try testing it on a custom rom. You can switch back to stock once you are sure it was a problem in OOS or not.
Click to expand...
Click to collapse
The more I think about it, the more stupid it seems to have a device that is rather well-supported by custom ROM devs and to not try some out.
I'll shop around for a ROM and give it a shot. I'm thinking and hoping this is strictly a software issue.
k1shy said:
The more I think about it, the more stupid it seems to have a device that is rather well-supported by custom ROM devs and to not try some out.
I'll shop around for a ROM and give it a shot. I'm thinking and hoping this is strictly a software issue.
Click to expand...
Click to collapse
In case you want suggestions, try these:
Bliss
Halogen
Validus
Lineage 13
Well, I have the same issue on my OP2 intermittently and it does not matter which rom I am using. In addition to OOS, I have had this issue on Marshmallow Cyanogenmod / Nougat Lineage based roms. Sooner or later it always returns. It seems to happen after longer uptime periods. E.g. with OOS3 I had an uptime stretch of 40+ days (without a reboot), so during this time I experienced the autorotation issue multiple times. It seems to get fixed by itself, but then comes back again. A reboot fixes it usually for longer period of time. As I am now on a custom rom, which is updated quite often, at least once of twice a week, the uptime stretches are not that long and I do not experience this issue often. I have noticed that the step counting sensors also stop working intermittently.
On rooted lineage based rom you can manually restart the sensors with following terminal commands:
su
stop sensors
start sensors
Don't know if this works on OOS. I made a tasker task shortcut for this on my homescreen.
Interesting...I have had the problem on-and-off I'd say, sometimes it follows this ~2 week pattern, sometimes it'll go longer than a month with no issues that I've noticed. Of course, it's also fairly rare that I watch videos on my phone and this is the main time that I realize it won't rotate.
Of course, with the current trend being to make all videos square with unnecessary obnoxious text in the letterbox black space, I suppose I'll never need to rotate my phone again </sarcasm>.
Prior to utkarsh102's suggestions I had already flashed AOSPExtended so I'm going to try rolling with this for a short time, if any issues surface (unrelated to my rotation issue) I'll try another ROM. Given that I'm trying to diagnose this issue before my warranty runs out (yeah, shoulda done it sooner, I know) I'll need to have a usable solution that can run stable for weeks uninterrupted to catch this again, if it's going to happen again.
FYI OnePlus support was entirely unhelpful about this issue. They completely disregarded the fact that it is intermittent and was not currently happening when I reported it to them. They were not able to suggest any diagnostic effort I could take to narrow down the issue further. Viewing the accelerometer readings was my own idea, not theirs. That suggestion absolutely should have come from them.
I do know I'm/we're not isolated in having this issue as there are other forum posts on various sites complaining of it.
I'll keep this thread updated with my findings, in the meantime anyone who has experienced this issue please chime in. It would be helpful to present to OnePlus, though I get the impression they won't care as they seem to have classified the 2 as a legacy product at this point. It's not like we're trying to get parts for a dot-matrix printer here.
Edit, October 2017, to provide an update without bumping the thread:
I've been using AOSPExtended on a constant basis since my last update to this thread and while I have experienced a variety of other issues, this particular one with the screen rotation has not affected me. My uptime has never been super long, but long enough at times that I should have seen this issue if it were going to happen following the same pattern as before.
Ever since my update to 9.0.5 my camera hasn't been working, as well as phone has been blacking out, system freezing up, the LED Light turning to a sort of baby blue color until I force reboot it (this bug has been with my phone since my first boot upon a full charge from 0% after unpacking it). I have scoured the forums of here at XDA and official One Plus forums. All other people have similar camera bugs but those are features of the camera bugging out and easily fixed with a cache clearing. My issue is with the system itself, and no amount of clean (Very) flashes results in a fix. If I go into recovery, select all partitions and format those, even repeatedly has this annoying system bug persist. The camera does come back if I revert to 8.1 OTA and custom ROMs, but the security patches are too far behind for me to keep using them. I am posting here to find out if anyone has had this issue and successfully fixed it as it has been over 2 months since I received my OP5 but I cannot use it for any intensive task as it worsens the freezeups and reboots. Further I live in a remote Alaskan village and there isn't even a OP Center close to the state to send it in. No amount of stock flashing fixes it at all and I am about to curse Oneplus for not being able to push out a stable device.:crying: :edit: I forgot to add that the gyroscope no longer functions as well. Not even in the factory testing menu by entering *#808# in the dialer with the stock roms.
arcticphoenix said:
Ever since my update to 9.0.5 my camera hasn't been working, as well as phone has been blacking out, system freezing up, the LED Light turning to a sort of baby blue color until I force reboot it (this bug has been with my phone since my first boot upon a full charge from 0% after unpacking it). I have scoured the forums of here at XDA and official One Plus forums. All other people have similar camera bugs but those are features of the camera bugging out and easily fixed with a cache clearing. My issue is with the system itself, and no amount of clean (Very) flashes results in a fix. If I go into recovery, select all partitions and format those, even repeatedly has this annoying system bug persist. The camera does come back if I revert to 8.1 OTA and custom ROMs, but the security patches are too far behind for me to keep using them. I am posting here to find out if anyone has had this issue and successfully fixed it as it has been over 2 months since I received my OP5 but I cannot use it for any intensive task as it worsens the freezeups and reboots. Further I live in a remote Alaskan village and there isn't even a OP Center close to the state to send it in. No amount of stock flashing fixes it at all and I am about to curse Oneplus for not being able to push out a stable device.:crying: :edit: I forgot to add that the gyroscope no longer functions as well. Not even in the factory testing menu by entering *#808# in the dialer with the stock roms.
Click to expand...
Click to collapse
It's more likely that you have an hardware issue according to your detailed description of the issue. Cause the gyroscope is also needed for proper camera functionality, camera app may crash.
strongst said:
It's more likely that you have an hardware issue according to your detailed description of the issue. Cause the gyroscope is also needed for proper camera functionality, camera app may crash.
Click to expand...
Click to collapse
Yeah it is part hardware and part software. A couple of months ago I used the cracked unbrick tool found here at XDA and I regained most functionality which was lost after upgrading from 9.0.4 - 9.0.5, though I do still get system freeze ups and reboots. But that is from a faulty unit not any of the ROMs.
I apologize for reviving an old post so any mods may close this thread.
arcticphoenix said:
...
I apologize for reviving an old post so any mods may close this thread.
Click to expand...
Click to collapse
THREAD CLOSED on request of OP.