I apologize if this isn't the correct place to post this, it seemed the most logical group.
I am coming up against some unique issues on a Nexus S. I don't have any mods on this device, it is stock Android 2.3.1 running 2.6.35.7-g7f1638a android-build (at symbol)apa28 #1.
There appears to be a bug on this device which results in the LED torch being disabled when the autofocus callback is called. To reproduce the issue simply:
Set the flash mode to Camera.Parameters.FLASH_MODE_TORCH
Set the focus mode to Camera.Parameters.FOCUS_MODE_AUTO
Start autofocus
This behavior is unique to this device, although I can only admit to having tested on 7 other Android devices. DroidX suffers from a similar bug but rather than the LED turning off, it blinks.
Inspection of the camera parameters inside the callback shows that flash-mode=torch so it is not an issue of the camera parameters being overwritten.
Has anyone seen this issue that might know how to work around it without modifying the device? My attempts at contacting and submitting bug reports to Samsung has failed miserably. It would be appropriate to make the remark that "Samsung is where bug reports go to die".
My primary concern is that the torch feature behaves so differently on every device, yet all of these devices claim to support Camera.Parameters.FLASH_MODE_TORCH. I'm really hoping to find a generic way to work around this issue since I believe there will be a lot more variation in camera driver implementations in the future.
Regards
Are you saying your camera isn't working because mine isn't working it keeps force closing
Sent from my Nexus S using XDA App
Wouldn't you rather submit the bug to Google via their bug tracking forum? I think Samsung is out of the picture.
Related
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?
device: 9505G
issue: audio over bluetooth does not work 2nd time a device is connected. Must toggle BT off/on (works sometimes) or restart device
This issue persists on all AOSP-based 5.0 and 5.1.x ROMs I've installed (mostly CM-based). My question is, where should I report this issue? I could report it on individual ROMs' threads, but I don't think that will fix the source of the issue. I've never reported a bug to AOSP. Upon investigating that option, it looks like that's meant for developers https://source.android.com/source/report-bugs.html
Does anybody have any experience in troubleshooting this sort of bug that can advise on the best course of action to take? Let me know if you need more information on the issue.
If the developers do not know there is an issue, how are they going to fix it?
In addition to mentioning the presence of a bug on the ROM thread you need to provide the developer with a logcat showing the activity as it occurs. If no logcat is provided, your statement will either be brushed aside or outright ignored.
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
I ask this question here, as I’m knew in the forum I can’t write it directly in the ROM post where would be more appropriate.
I have installed the in the phone the CM13.0 ROM built by mparus, I have used the cm-13.0-20161118-UNOFFICIAL-mparus-without_root-g760.zip build, the last one in this moment. The phone works correctly, I only had a pair of minor issues:
-phone app was not working, caused a reboot when trying to use it: it’s a vanilla cyanogenmod problem, it’s solved choosing the phone app as default for making calls
-camera app doesn’t detect the camera device: I have read that is a bug of the official camera app, can be solved installing another app as open camera
I have a serious problem for which I have not found information about. It’s with the notification lights, they are not working except for indicating the charging status of the device, not for mails, missed calls, etc. I tried all the possible combinations for this without luck. I have also tried third party app’s like light manager and they don’t work also, perhaps something is broken in the build but I’m not sure.
Any of you has experienced this problem with the mparus mod in the ascend g7? Can you give me any advice? I’m a bit frustrated about this
Thank you
Do a clean re-install of the ROM I'd say..
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.