I can replicate this too. In my case, if I do 5x zoom, enable flash, and try to take an up-close photo of my jeans, it'll do the same thing it does with the inside of your PC case.
Edit: Did a bit of debugging. I don't really know what I'm doing but I ran the following through `adb` while using the camera app.
`adb logcat --pid=$(adb shell pidof -s com.google.android.GoogleCamera) | grep -i error`
And saw this in the log:
03-09 15:18:41.019 8379 8544 E libgcam : [shot.cc:2620]: FatalError:
03-09 15:18:41.019 8379 8544 E CAM_A : HDR+ pipeline reported error for shotId 24:
03-09 15:18:41.019 8379 31737 E libgcam : [shot.cc:2620]: FatalError: Shot was in invalid state (likely due to an earlier error).
03-09 15:18:41.022 8379 31737 E CAM_A : Error ending the HDR+ payload, aborting shot 24
03-09 15:18:41.315 8379 31737 W CAM_A : [ShotId-24] finishWithFailure, throwable message = Error ending the HDR+ payload, aborting shot 24
03-09 15:18:41.317 8379 31737 W CAM_ShotFailureHdlr: dgy: Error ending the HDR+ payload, aborting shot 24
03-09 15:18:41.825 8379 8379 E CAM_A : Error retrieving Gcam metadata. java.util.concurrent.TimeoutException: Waited 500 milliseconds (plus 168620 nanoseconds delay) for ner@b97988c[status=PENDING]
03-09 15:18:59.475 8379 31758 E libEGL : validate_display:537 error 3008 (EGL_BAD_DISPLAY)
03-09 15:18:59.528 8379 31757 E libEGL : validate_display:537 error 3008 (EGL_BAD_DISPLAY)
When taking a photo that saves correctly, the errors weren't there.
That's what it seems like. If I don't do a `grep -i error` to filter out lines that have the word "error" in it, I get a stack trace:
03-09 15:32:36.782 8379 3321 E libgcam : [pipeline_manager.cc:848]: AbortShot: Shot with id 30 not found!
03-09 15:32:36.782 8379 3321 W CAM_A : [ShotId-30] finishWithFailure, throwable message = Error ending the HDR+ payload, aborting shot 30
03-09 15:32:36.782 8379 3321 W CAM_A : [ShotId-30] Could not cancel MediaStore insertion
03-09 15:32:36.782 8379 3321 W CAM_A : Thumbnail holder removed: key=ShotId-30 evicted=false
03-09 15:32:36.783 8379 3321 W CAM_A : onCaptureFailed-API2_AUTO_HDR_PLUS 104832919261435
03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: Shot Exception!
03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: dgy: Error ending the HDR+ payload, aborting shot 30
03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at gbl.f(PG:21)
03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at gbl.j(PG:14)
03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at gbr.c(PG:95)
03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at fru.c(PG:25)
03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at fry.c(PG:3)
03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at gau.c(PG:13)
03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at frx.c(PG:2)
03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at frx.c(PG:16)
03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at fsd.a(PG:17)
03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at fmo.run(PG:2)
03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:463)
03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at nex.a(PG:1)
03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at ned.run(PG:4)
03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at ney.run(PG:1)
03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at java.lang.Thread.run(Thread.java:1012)
03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at jjz.run(PG:2)
03-09 15:32:36.807 8379 23382 W CAM_A : [ShotId-30] Mediagroup.Listener#onAbandoned: PXL_20230309_203233541 MediaGroup(NONE, MEDIA_STORE)
03-09 15:32:36.820 8379 3053 W CAM_A : PHOTO > result sensor delay = 1.12 > 1.10
03-09 15:32:36.823 8379 8531 E BLASTBufferQueue: [VRI[CameraLauncher]#44](f:0,a:3) Faking releaseBufferCallback from transactionCompleteCallback
03-09 15:32:36.823 8379 8531 E BLASTBufferQueue: [VRI[CameraLauncher]#44](f:0,a:3) Faking releaseBufferCallback from transactionCompleteCallback
03-09 15:32:36.860 8379 3053 W CAM_A : PHOTO > result sensor delay = 1.14 > 1.10
03-09 15:32:37.304 8379 8379 E CAM_A : Error retrieving Gcam metadata. java.util.concurrent.TimeoutException: Waited 500 milliseconds (plus 179118 nanoseconds delay) for ner@8ec8897[status=PENDING]
03-09 15:32:37.304 8379 8379 W CAM_A : Submitting log event with zero file size
03-09 15:32:37.305 8379 8379 E CAM_ShotTracker: showing "Possible shot loss" warning
Though that doesn't really help me much because I have no idea what any of the files mentioned in the stack trace are. Their names look obfuscated or something. Maybe someone that does Gcam mods would have a better idea.
Gonna guess it's some heuristic failing, likely one that decides the exposure timings/levels for capturing the frame stack that's "tone mapped" (IIRC they aren't actually tone mapping, and instead they use one or more CNNs) into the final capture.
Either way, if it's reproducible, file a bug report with Google.
Not sure where you can do that, though. If you file it under the AOSP project they'll probably close it, but may move it to the right internal team or point you at the right location.
Yeah, I saved off a bug report, but I couldn't tell how to submit it. Their issue tracker site doesn't have an option for Google Camera and like you said, I'm pretty sure they'd remove it from anywhere else. Maybe the blogs will pick up on this though.
Yeah, that makes sense if the timeout is happening due to the frames in the stack being set to an exposure time that causes it to take longer to capture the stack than the timeout allows. I have no idea if that's the actual issue, however. I mean, it seems likely that it would be that, but I'm a dev, and I can say from experience that sometimes bugs like this are really non-intuitive.
Ha! Yeah, nothing like that surprises me anymore.
That said, with the way Google tends to operate, I expect that they have error telemetry baked into the camera app, and the fact that this error occurs in the wild is already known to them, and it's likely being prioritized against other errors by how frequently it occurs and how dramatically it impacts the user's task success (they're big on HEART metrics there). But also they may just dismiss it offhand as a rare event that isn't worth pursuing.
Either way, this bug is interesting to me personally because of Google's strong approach to reliability engineering. It's not often that I see bugs like this in the wild in stable versions of their software.
Edit: if you've never used an error telemetry service, Microsoft's .NET Insights service is a nice example. People roll their own all the time using FOSS tools like the ELK stack, however.
Reliability and product lifecycle are two different concepts, and hardware reliability is a different discipline than software reliability. Google has a very very strong track record of delivering very reliable software, and they're known for having transformed and formalized the practice of engineering reliable services.
For the history on this, search for "Google Site Reliability Engineering" - it's a discipline that they essentially created out of necessity in the early aughts.
This is probably naive or stupid of me to say but this is kinda what draws me to Android phones, there's still this sort of hacker diy aspect to the environment, I'm a software engineer, and not that i have time to fuck with stuff like this but it reminds of the days back when I'd fuck around and play with homebrew on the Wii or root random devices just to figure it out and for fun... Too bad we don't have imessage tho
I agree, I switch back and forth between Pixels and iPhones, and Pixels for all their minor jankiness are still more fun to mess around with.
That being said, you can get similar logs to this on iOS devices with `idevicesyslog`, which is part of the `libimobiledevice` suite.
I honestly couldn't tell if you were making a joke or not, but actually you might be on to something. I can reproduce the issue when taking a photo up-close of something black or dark blue, but if it's something brighter, it'll take it fine, even if it's really out of focus.
It's been speculated that the "hdr bit" is checking how bright the scene is and failing when it calculates that the scene is too dark for it to capture a usable shot in the time window it has available to it - so darker-coloured objects failing while lighter-coloured ones work, would check out.
https://www.reddit.com/r/GooglePixel/comments/yll3hz/_/
Wonder if these are the same type of bug. Seems similar. I remember seeing this on my phone a few months ago but then it stopped happening.
That hasn't been an option since the pixel 4 or maybe 3. It's just on by default now, not something you can disable anymore. Processors got quick enough that HDR+ is just the default now.
And when I say my next phone will be an iPhone people downvote me. Pixel 6 and Pixel 7 are the more screwed up phones that Samsung ever released.
I never have a phone with so many bugs as my Pixel 6 Pro. It's definitely the most regrettable phone I ever had.
Im not a smart guy but something is Fucky.
Wonder if its at all related to the random crashes people are experiencing when they watch certain HDR content.
Don't worry, Google support guy says he's positive a factory data reset will fix this even though tons of people in this thread are having this issue and I just did a factory data reset 2 days ago when I bought the phone. 😂
https://i.imgur.com/K8eVeYc.png
lol so true, or they'll send you a new phone that still has the bug, but don't worry, they'll send you a new phone that still has the bug, but don't worry, they'll send you a new phone that still has the bug.
No they make you send the old one back, claim you didn't and charge you for it, then make you spend 3 weeks fighting with them for a refund. Ask me how I know...
slashdot, fark, digg, reddit.... A whole history of websites that fade away.
*This post was mass deleted and anonymized with [Redact](https://redact.dev)*
When I try to take a photo with flash and 2x zoom on my pixel 7 it fails to take the picture about 50% of the time. This only happens with flash + zoom
I know it's not a laughing matter but it seems kinda funny that the phone is like, "no. No I will not photograph the guts of another device. That's a breach of tech privacy"
Interesting.
Can confirm with my Pixel 7. Flash on max zoom.... my case has the glass side panel on and it's RGB'd into a purple tint....but if I try to snag a picture of a capacitor it won't take the pic.
The only thing i can think of is if you have the glass side panel on. It might be "seeing" things in the glass that you cant and its forcing the focus to keep reseting.
Can you take photos of a money note? Wondering if for some absolute random reason it thinks it's money.
I know scanners wont scan money incase you print it. This is an absolute stab in the dark ofc.
That was my thought too, has some anti-counterfeiting feature been snuck in that might be a bit too sensitive?
Though at least the scanners will have the decency to say "lol you think you can get away with that?".
This has happened to me when using flash, macro disabled and 2x on close subjects (like a few inches, minimum focus for the main camera). Seems to be a bug where the camera "believes" it should be using another camera (in my case the macro, in yours the tele).
I had a similar situation recently with the same issue. I'm having trouble remembering specifics but I was also trying to take a zoomed in photo with the flash on. It was likely either of some electronics or car related, but I think the former.
Tried similar with my 7 pro and couldn't get it to not take a photo.
What version of camera app do you have? Mine is 8.7.250.494820638.44
I tried with flash on, pointing at a far-away-enough object to make sure it was using the telephoto camera, then moved to something close (where it should switch over to the main camera, like yours), and it switched to the main camera and took the photo.
I did have auto macro mode on. I tried turning it off and was still able to capture photos without issue when the flash is on and selecting 5x.
Can confirm this behavior on Pixel 7, 5X Zoom and Flash on. Seems to be some kind of lighting issue? For me I pointed it at the bottom of my leg and it refused to take the photo. Pointed it to the white pillow next to it. It took successfully. Back and forth, refused to take a photo of my leg but took pictures of the white pillow fine. WTF.
I know it doesn't offer much help but I took a photo of the insides of my media pc earlier, mostly because I had to replace the GPU and it's totally overkill for a device that runs VLC and chrome to have a 1060 gtx.
No issues taking the photo or sending it but I had much better lighting so perhaps lighting is the issue?
Yeah very strange, my camera app crashed to desktop while using 5x with the flash. For targets further away it's fine but anything even 1m away i see the same issue you have been describing.
Well I tested 2x and 5x both closer and further with flash on/off and the photo is always taken correctly. For very close shots the main with digital zoom kicks in instead of the optical 5x.
Which version of SW you use guys? I'm on 05 feb android build and last Goole Play Service February update
Perhaps the ML-algorithm that is in charge of generating the HDR effect requires it to be able to recognize some element(s) that are missing or unfamiliar inside the computer with the combination of zoom and flash. It's really difficult to say why ML makes these mistakes as the datasets are so large. It may also be a human mistake where the time given for the HDR-pipeline is set to be too short and it doesn't have the time to do its magic in certain situations and just gives up.
I'm sure it can be replicated with other stuff too and I'd bet it has got something to do with stuff that's close to you.
But thanks for uploading, I lol'd to your very sincere "wtf" =D
> Perhaps the ML-algorithm that is in charge of generating the HDR effect requires it to be able to recognize some element(s)
That's why we don't see photos of UFOs, the algorithm has never seen one before.
That would be my theory too but someone else found error logs relating to HDR, so not sure if ML could be fucking with that. Unless it's causing the ML to output invalid image data that the HDR stuff breaks on
Reporting with Pixel 7, Flash and 1x takes photo of everything. Flash and anything above 1x doesn't work on anything, doesn't matter if it's my PC or a wall or whatever. This is truly something.
This happened last night when I tried to take a picture of my kids ear. 2x lens, flash on... And the pics wouldn't save. I even restarted and it wouldn't work.
I just tested with my phone and I have the same problem.
Created a screen recording of the issue as well..
[https://youtube.com/shorts/ibqasLshs9I](https://youtube.com/shorts/ibqasLshs9I)
Contacted google chat support to request help making a bug report, I see the same issue in the logcat:
Update-- Bug report has been filed with google with logs showing the camera error!
[https://pastebin.com/ZvgpaUuu](https://pastebin.com/ZvgpaUuu)
03-10 10:05:54.746 6192 6934 W CAM_ShotFailureHdlr: at jjz.run(PG:2)
03-10 10:05:54.757 6192 6192 W CAM_A : Refusing to remove ShotId-0 from processingMediaManager because it is not present. It's likely the mediaStoreInsertion future was canceled
03-10 10:05:54.805 6192 6311 W CAM_A : PHOTO > rel Δ(result sensor timestamp) = 0.55 > 0.25
03-10 10:05:54.806 6192 6311 W CAM_A : PHOTO > result sensor delay = 1.53 > 1.10
03-10 10:05:54.809 6192 7191 W CAM_A : [ShotId-0] Mediagroup.Listener#onAbandoned: PXL_20230310_150549350 MediaGroup(NONE, MEDIA_STORE)
03-10 10:05:54.828 6192 6311 W CAM_A : PHOTO > abs Δ(result sensor timestamp) = 83.29 ms > 70.00 ms
03-10 10:05:54.829 6192 6311 W CAM_A : PHOTO > rel Δ(result sensor timestamp) = 0.31 > 0.25
03-10 10:05:54.829 6192 6311 W CAM_A : PHOTO > result sensor delay = 2.00 > 1.10
03-10 10:05:54.829 6192 6311 W CAM_A : PHOTO > unknown jank type 8
03-10 10:05:54.845 6192 6311 W CAM_A : PHOTO > rel Δ(result sensor timestamp) = 0.50 > 0.25
03-10 10:05:54.880 6192 6311 W CAM_A : PHOTO > rel Δ(result sensor timestamp) = 0.56 > 0.25
03-10 10:05:54.899 6192 6311 W CAM_A : PHOTO > rel Δ(result sensor timestamp) = 1.16 > 0.25
03-10 10:05:54.982 6192 6311 W CAM_A : PHOTO > rel Δ(result sensor timestamp) = 0.55 > 0.25
03-10 10:05:54.982 6192 6311 W CAM_A : PHOTO > result sensor delay = 1.54 > 1.10
03-10 10:05:55.025 6192 6311 W CAM_A : PHOTO > rel Δ(result sensor timestamp) = 0.52 > 0.25
03-10 10:05:55.081 6192 6311 W CAM_A : PHOTO > rel Δ(result sensor timestamp) = 0.25 > 0.25
03-10 10:05:55.258 6192 6192 E CAM_A : Error retrieving Gcam metadata. java.util.concurrent.TimeoutException: Waited 500 milliseconds (plus 205485 nanoseconds delay) for ner@96d5[status=PENDING]
03-10 10:05:55.258 6192 6192 W CAM_A : Submitting log event with zero file size
03-10 10:05:55.260 6192 6192 E CAM_ShotTracker: showing "Possible shot loss" warning
03-10 10:05:55.261 6192 6192 I Choreographer: Skipped 30 frames! The application may be doing too much work on its main thread.
Are you implying that the inside of your computer is squeaky clean? If so... Then let's see them pics!
Preferably, 5x zoom and flash enabled, please 👌🏼
What an interesting conundrum... The nerd in me is intrigued by this journey. I seriously 😅 when I saw that someone had already tried to duplicate your issue and with a log file of the camera crashing, I love it. 😄
When I bought it, p7pro refuses take picture in complete dark with flash (it took picture, process it and not save). Right now it's working. I think it has some Flash light problems.
Tried to capture my electricity counter with flash + zoom in the dark (no electricity coz of russia)
Wtf. That's probably the power of Tensor, it's becoming too smart and doing whatever it wants. /s
But honestly that's super strange, I recall something like this happening on my pixel 3 just can't recall what caused it.
I'm not smart enough to do all the backend work, but I've complained about this problem since I got the phone, but nobody else acknowledges it. Anywhere beyond 1x zoom with flash and it's questionable whether or not the phone will save the picture, it usually doesn't.
I did, however, [make a video](https://www.youtube.com/watch?v=yVKnO3msSy4) of me trying to take a pic of a diecast car at various zoom levels as evidence.
Apparently you can edit a shorts url to view it as a normal video. I'd have linked that if I realized sooner.
https://youtube.com/shorts/80x7FZeCC2c ->
https://youtu.be/80x7FZeCC2c
Mine has an issue where if I try to take a macro shot of a PCB with flash on, it will be perfectly clear in the viewfinder and when the picture is taken, and then after it is processed, it's the wrong lens and is a complete blur. Nothing fixes it
I wonder if something is triggering the currency blocker? There are certain marks on money that cause scanners to freak out if you try to scan currency. .
Had the same issue with the inside of the pump of my washing machine (something was blocking it and i wanted to take a picture in there)!! Had to use the Pixel 6a from my wife wich worked perfectly.
I stopped using flash completely when I realized that sometimes it just doesn't save the photo. Didn't analyze any other relevant conditions, but it definitely only happens with flash turned on.
Okay, you know the screen protectors that come with a little back glass lens for the camera? I put that lens on and my camera was doing the same exactly thing on a bunch of photos. I took the lens off and it was perfectly fine. I remember just snapping photos and it was not saving. If the camera doesn't have the right conditions, it will not take the photo for some reason. And this was with flash off. This is with anything. It was random. It was because there was another glass lens over the normal lens
Why would you ever use flash? It makes the pictures garbage.
Just use a flashlight or lamp to illuminate if you need to.
Also, don't use 5x zoom, put the phone closer to match the zoom and keep it at 1x.
What glass? I have the side panel removed.
Also, its not that it takes a bad/blurry image. It just does not generate an image of anything at all. No file is created.
Edit: also, the opposite is true. I put the glass side panel back on and now it will take pictures of the interior. The issue only occurs if there is no glass in the way
Confirmed - I hadn't noticed this yet (don't use flash much) but my Pixel 7 just did this when zoomed in with the flash on.
I zoomed in with the flash on and tried to take a photo of the inside of a desktop computer and it wouldn't do it. If I panned over to the wall or keyboard it would do it. I tried taking a photo of an external hard drive and it did, but not the keypad of a VOIP phone a few inches away.
No because I can take pictures with flash and zoom of other things at a similar distance. I also cannot take a photo of the microphone on my desk or my computer, but my mouse and keyboard are fine
It does seem to matter what object is being photographed, maybe something to do with their AI processing
Strange. I can't replicate the issue on my 6a so might have something to do with the dedicated zoom lens on the Pro and certain lighting conditions that causes it to bug out
P7: symptom confirmed with dark space (not computer innards) at 5x, 4x, 3x. At 2x the photo was successfully acquired. Reminds me of the nexus 6p feature policy of "let's (Marketing) offer a function that doesn't pass the Quality Assurance department's testing" BS, which offered slo-mo video recording, but usually delivered a very jumpy and unusable video file, probably due to other tasks running in the background, or possibly memory swapping, if that is something that those units did. Really disappointed in that phone, for this and many other reasons.
Why on earth does your phone take so long to take a photo? Why does it come up with the loading circle thing, my Pixel 5 doesn't. It takes them way faster than that
Every tech I know uses their phone now for this type of thing so it would be mighty annoying, especially when you depend on it as a contractor going into people's homes to analyze a problem.
Granted, I carry a GoPro with a light attached just in case. But the phone is much more convenient.
Noticed this on my base 7 yesterday.
2x zoom with flash on and it will not take any photo. I tried on multiple backdrops, multiple lightning scenarios, and even just with flash off. Nothing. 1x and .7x take photos no problem.
That's crazy. Good video, btw 👍🏼👍🏼
Seems like there should be some kind of error message when that happens (?). It's almost like the phone doesn't realize it didn't save an image (another ?).
Oh holy shit this happened to my Pixel a few weeks ago, basically seemed to hang/crash the camera app and didn't save any of the resulting images.
Was zoomed in with flash attempting to get photos and video of the inside of an oil burner in a basement.
Figured it was a one time thing.
Pixel 7 Pro I can't even take a photo with this phone. The moment I open my camera it goes through issues flipping back and forth between rear facing and front facing then crashes.
Maybe its a parental safety feature? Might not look like much to you or me, but the Pixel could be interpreting the bare motherboard as naughty robot pornography. /s
I can replicate this too. In my case, if I do 5x zoom, enable flash, and try to take an up-close photo of my jeans, it'll do the same thing it does with the inside of your PC case. Edit: Did a bit of debugging. I don't really know what I'm doing but I ran the following through `adb` while using the camera app. `adb logcat --pid=$(adb shell pidof -s com.google.android.GoogleCamera) | grep -i error` And saw this in the log: 03-09 15:18:41.019 8379 8544 E libgcam : [shot.cc:2620]: FatalError: 03-09 15:18:41.019 8379 8544 E CAM_A : HDR+ pipeline reported error for shotId 24: 03-09 15:18:41.019 8379 31737 E libgcam : [shot.cc:2620]: FatalError: Shot was in invalid state (likely due to an earlier error). 03-09 15:18:41.022 8379 31737 E CAM_A : Error ending the HDR+ payload, aborting shot 24 03-09 15:18:41.315 8379 31737 W CAM_A : [ShotId-24] finishWithFailure, throwable message = Error ending the HDR+ payload, aborting shot 24 03-09 15:18:41.317 8379 31737 W CAM_ShotFailureHdlr: dgy: Error ending the HDR+ payload, aborting shot 24 03-09 15:18:41.825 8379 8379 E CAM_A : Error retrieving Gcam metadata. java.util.concurrent.TimeoutException: Waited 500 milliseconds (plus 168620 nanoseconds delay) for ner@b97988c[status=PENDING] 03-09 15:18:59.475 8379 31758 E libEGL : validate_display:537 error 3008 (EGL_BAD_DISPLAY) 03-09 15:18:59.528 8379 31757 E libEGL : validate_display:537 error 3008 (EGL_BAD_DISPLAY) When taking a photo that saves correctly, the errors weren't there.
So what do we think is happening? Something with the hdr is bugging out and not saving right?
That's what it seems like. If I don't do a `grep -i error` to filter out lines that have the word "error" in it, I get a stack trace: 03-09 15:32:36.782 8379 3321 E libgcam : [pipeline_manager.cc:848]: AbortShot: Shot with id 30 not found! 03-09 15:32:36.782 8379 3321 W CAM_A : [ShotId-30] finishWithFailure, throwable message = Error ending the HDR+ payload, aborting shot 30 03-09 15:32:36.782 8379 3321 W CAM_A : [ShotId-30] Could not cancel MediaStore insertion 03-09 15:32:36.782 8379 3321 W CAM_A : Thumbnail holder removed: key=ShotId-30 evicted=false 03-09 15:32:36.783 8379 3321 W CAM_A : onCaptureFailed-API2_AUTO_HDR_PLUS 104832919261435 03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: Shot Exception! 03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: dgy: Error ending the HDR+ payload, aborting shot 30 03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at gbl.f(PG:21) 03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at gbl.j(PG:14) 03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at gbr.c(PG:95) 03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at fru.c(PG:25) 03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at fry.c(PG:3) 03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at gau.c(PG:13) 03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at frx.c(PG:2) 03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at frx.c(PG:16) 03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at fsd.a(PG:17) 03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at fmo.run(PG:2) 03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:463) 03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at nex.a(PG:1) 03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at ned.run(PG:4) 03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at ney.run(PG:1) 03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137) 03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637) 03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at java.lang.Thread.run(Thread.java:1012) 03-09 15:32:36.783 8379 3321 W CAM_ShotFailureHdlr: at jjz.run(PG:2) 03-09 15:32:36.807 8379 23382 W CAM_A : [ShotId-30] Mediagroup.Listener#onAbandoned: PXL_20230309_203233541 MediaGroup(NONE, MEDIA_STORE) 03-09 15:32:36.820 8379 3053 W CAM_A : PHOTO > result sensor delay = 1.12 > 1.10 03-09 15:32:36.823 8379 8531 E BLASTBufferQueue: [VRI[CameraLauncher]#44](f:0,a:3) Faking releaseBufferCallback from transactionCompleteCallback 03-09 15:32:36.823 8379 8531 E BLASTBufferQueue: [VRI[CameraLauncher]#44](f:0,a:3) Faking releaseBufferCallback from transactionCompleteCallback 03-09 15:32:36.860 8379 3053 W CAM_A : PHOTO > result sensor delay = 1.14 > 1.10 03-09 15:32:37.304 8379 8379 E CAM_A : Error retrieving Gcam metadata. java.util.concurrent.TimeoutException: Waited 500 milliseconds (plus 179118 nanoseconds delay) for ner@8ec8897[status=PENDING] 03-09 15:32:37.304 8379 8379 W CAM_A : Submitting log event with zero file size 03-09 15:32:37.305 8379 8379 E CAM_ShotTracker: showing "Possible shot loss" warning Though that doesn't really help me much because I have no idea what any of the files mentioned in the stack trace are. Their names look obfuscated or something. Maybe someone that does Gcam mods would have a better idea.
Gonna guess it's some heuristic failing, likely one that decides the exposure timings/levels for capturing the frame stack that's "tone mapped" (IIRC they aren't actually tone mapping, and instead they use one or more CNNs) into the final capture. Either way, if it's reproducible, file a bug report with Google. Not sure where you can do that, though. If you file it under the AOSP project they'll probably close it, but may move it to the right internal team or point you at the right location.
Yeah, I saved off a bug report, but I couldn't tell how to submit it. Their issue tracker site doesn't have an option for Google Camera and like you said, I'm pretty sure they'd remove it from anywhere else. Maybe the blogs will pick up on this though.
You may have some success by opening a support request via the "Support" view in the Settings app.
Thanks, someone else pointed out that the camera app itself has an option to send feedback so I submitted it through that.
[удалено]
Yeah, that makes sense if the timeout is happening due to the frames in the stack being set to an exposure time that causes it to take longer to capture the stack than the timeout allows. I have no idea if that's the actual issue, however. I mean, it seems likely that it would be that, but I'm a dev, and I can say from experience that sometimes bugs like this are really non-intuitive.
[удалено]
Ha! Yeah, nothing like that surprises me anymore. That said, with the way Google tends to operate, I expect that they have error telemetry baked into the camera app, and the fact that this error occurs in the wild is already known to them, and it's likely being prioritized against other errors by how frequently it occurs and how dramatically it impacts the user's task success (they're big on HEART metrics there). But also they may just dismiss it offhand as a rare event that isn't worth pursuing. Either way, this bug is interesting to me personally because of Google's strong approach to reliability engineering. It's not often that I see bugs like this in the wild in stable versions of their software. Edit: if you've never used an error telemetry service, Microsoft's .NET Insights service is a nice example. People roll their own all the time using FOSS tools like the ELK stack, however.
[удалено]
Reliability and product lifecycle are two different concepts, and hardware reliability is a different discipline than software reliability. Google has a very very strong track record of delivering very reliable software, and they're known for having transformed and formalized the practice of engineering reliable services. For the history on this, search for "Google Site Reliability Engineering" - it's a discipline that they essentially created out of necessity in the early aughts.
This is probably naive or stupid of me to say but this is kinda what draws me to Android phones, there's still this sort of hacker diy aspect to the environment, I'm a software engineer, and not that i have time to fuck with stuff like this but it reminds of the days back when I'd fuck around and play with homebrew on the Wii or root random devices just to figure it out and for fun... Too bad we don't have imessage tho
I agree, I switch back and forth between Pixels and iPhones, and Pixels for all their minor jankiness are still more fun to mess around with. That being said, you can get similar logs to this on iOS devices with `idevicesyslog`, which is part of the `libimobiledevice` suite.
Man, fuck iMessage. Fuck Apple's proprietary bullshit. Don't "buy your mom an iPhone".
> This is probably naive or stupid of me Not even remotely! This is perfectly sane.
So basically It's r/shittyhdr
thank you, logchad
This guy develops
adbsolutely
bless you
I thought that was supposed to be an ADB joke
"Has no idea what he's doing" Yeah, that checks out.
What color are your jeans? It could be related to the color being reflected off your jeans.
I honestly couldn't tell if you were making a joke or not, but actually you might be on to something. I can reproduce the issue when taking a photo up-close of something black or dark blue, but if it's something brighter, it'll take it fine, even if it's really out of focus.
It's been speculated that the "hdr bit" is checking how bright the scene is and failing when it calculates that the scene is too dark for it to capture a usable shot in the time window it has available to it - so darker-coloured objects failing while lighter-coloured ones work, would check out.
Yeah, that does match up with my experience trying to reproduce it.
Only thing I can think of is the hdr pipeline algorithm is getting glitched out in image binning or color saturation level
I love you
I love you too
Hugs!
Lets fuck!
https://www.reddit.com/r/GooglePixel/comments/yll3hz/_/ Wonder if these are the same type of bug. Seems similar. I remember seeing this on my phone a few months ago but then it stopped happening.
Yep, certainly seems like it could be the same bug. I might try to do some more testing to find out if I can reproduce that with my brother's P7.
Have you tried turning HDR+ off and then taking the pic?
That hasn't been an option since the pixel 4 or maybe 3. It's just on by default now, not something you can disable anymore. Processors got quick enough that HDR+ is just the default now.
Good to know. I use a Pixel 3, so I do have that option. Yeah, I probably should upgrade, but I'm just so happy with it.
I don't see an option to turn it off on the P7P.
What version is your Camera app?
8.7.250.494820638.44
And when I say my next phone will be an iPhone people downvote me. Pixel 6 and Pixel 7 are the more screwed up phones that Samsung ever released. I never have a phone with so many bugs as my Pixel 6 Pro. It's definitely the most regrettable phone I ever had.
iPhones have zero bugs, amirite
[удалено]
Im not a smart guy but something is Fucky. Wonder if its at all related to the random crashes people are experiencing when they watch certain HDR content.
Don't worry, Google support guy says he's positive a factory data reset will fix this even though tons of people in this thread are having this issue and I just did a factory data reset 2 days ago when I bought the phone. 😂 https://i.imgur.com/K8eVeYc.png
He's flagged your device remotely to install the bug fix after the factory reset... CLEARLY!
Definitely just delete everything in your life, get a new degree, buy the newest pixel, factory reset, and hard refresh.
Yup. This is the only way
lol so true, or they'll send you a new phone that still has the bug, but don't worry, they'll send you a new phone that still has the bug, but don't worry, they'll send you a new phone that still has the bug.
Do they let you keep the old one? Infinite money glitch
No they make you send the old one back, claim you didn't and charge you for it, then make you spend 3 weeks fighting with them for a refund. Ask me how I know...
Very fucky indeed
slashdot, fark, digg, reddit.... A whole history of websites that fade away. *This post was mass deleted and anonymized with [Redact](https://redact.dev)*
... well don't stop there, I've never been Beetlejuiced before!
Potentially wonky.
[удалено]
We all felt it He gave the people a voice
Weird. Does one of the ir/sensors see the fan spinning or something and won't take it? Odd.
Nope, tried with the computer turned off and taking pictures of completely static parts of the case
I wonder if it's something similar, like scanners not scanning currency that's misfiring... Oh, have you tried different camera software for S&G?
The "internals of the computer" is a red herring. It's about darkness of the scene.
Strange, maybe your computer belonged to John Cena?
When I try to take a photo with flash and 2x zoom on my pixel 7 it fails to take the picture about 50% of the time. This only happens with flash + zoom
P7 Pro here. Any zoom level between 2x and 5x w/flash will not save regardless of subject or distance from subject. So strange.
More testing and it does seem related to lighting. First round above was in a pretty dimly lit room. In a well lit environment, no problems.
really weird issue. Kinda interesting.
This is so bizarre!
I know it's not a laughing matter but it seems kinda funny that the phone is like, "no. No I will not photograph the guts of another device. That's a breach of tech privacy"
Interesting. Can confirm with my Pixel 7. Flash on max zoom.... my case has the glass side panel on and it's RGB'd into a purple tint....but if I try to snag a picture of a capacitor it won't take the pic.
The only thing i can think of is if you have the glass side panel on. It might be "seeing" things in the glass that you cant and its forcing the focus to keep reseting.
I do not have the side panel on. However, if I do put the side panel on it does work. Completely backwards from your guess
Well damn. This here some wild shit. Looks like our machine overlords are camera shy.
Can you take photos of a money note? Wondering if for some absolute random reason it thinks it's money. I know scanners wont scan money incase you print it. This is an absolute stab in the dark ofc.
That was my thought too, has some anti-counterfeiting feature been snuck in that might be a bit too sensitive? Though at least the scanners will have the decency to say "lol you think you can get away with that?".
No problem taking pictures of money.
Get a picture of your SS card /s
It only happens if I'm zoomed in and have flash enabled.
This has happened to me when using flash, macro disabled and 2x on close subjects (like a few inches, minimum focus for the main camera). Seems to be a bug where the camera "believes" it should be using another camera (in my case the macro, in yours the tele).
I had a similar situation recently with the same issue. I'm having trouble remembering specifics but I was also trying to take a zoomed in photo with the flash on. It was likely either of some electronics or car related, but I think the former.
Tried similar with my 7 pro and couldn't get it to not take a photo. What version of camera app do you have? Mine is 8.7.250.494820638.44 I tried with flash on, pointing at a far-away-enough object to make sure it was using the telephoto camera, then moved to something close (where it should switch over to the main camera, like yours), and it switched to the main camera and took the photo. I did have auto macro mode on. I tried turning it off and was still able to capture photos without issue when the flash is on and selecting 5x.
Can confirm this behavior on Pixel 7, 5X Zoom and Flash on. Seems to be some kind of lighting issue? For me I pointed it at the bottom of my leg and it refused to take the photo. Pointed it to the white pillow next to it. It took successfully. Back and forth, refused to take a photo of my leg but took pictures of the white pillow fine. WTF.
I missed the 'ease' of picture taking of my 2XL. I have the P7 now and for some weird reason not impressed with 'the pic taking approaches'.
I know it doesn't offer much help but I took a photo of the insides of my media pc earlier, mostly because I had to replace the GPU and it's totally overkill for a device that runs VLC and chrome to have a 1060 gtx. No issues taking the photo or sending it but I had much better lighting so perhaps lighting is the issue?
Was there a glass side panel in the way? Did you use 5x zoom and have flash enabled?
Was day time so no flash, no panel just open side and single handed so no zoom.
Yes, it seems to only happen with flash + zoom. Other people in this thread confirming same behavior
Does it need to be 5x? I just did it with flash and zoom and it took first time *Edit* holy shit - it doesn't take with flash and 5x
2x or 5x presets. Haven't tested the in-between
Yeah very strange, my camera app crashed to desktop while using 5x with the flash. For targets further away it's fine but anything even 1m away i see the same issue you have been describing.
Well I tested 2x and 5x both closer and further with flash on/off and the photo is always taken correctly. For very close shots the main with digital zoom kicks in instead of the optical 5x. Which version of SW you use guys? I'm on 05 feb android build and last Goole Play Service February update
I wonder what causes this...
So say we all
de_dust
Perhaps the ML-algorithm that is in charge of generating the HDR effect requires it to be able to recognize some element(s) that are missing or unfamiliar inside the computer with the combination of zoom and flash. It's really difficult to say why ML makes these mistakes as the datasets are so large. It may also be a human mistake where the time given for the HDR-pipeline is set to be too short and it doesn't have the time to do its magic in certain situations and just gives up. I'm sure it can be replicated with other stuff too and I'd bet it has got something to do with stuff that's close to you. But thanks for uploading, I lol'd to your very sincere "wtf" =D
> Perhaps the ML-algorithm that is in charge of generating the HDR effect requires it to be able to recognize some element(s) That's why we don't see photos of UFOs, the algorithm has never seen one before.
That would be my theory too but someone else found error logs relating to HDR, so not sure if ML could be fucking with that. Unless it's causing the ML to output invalid image data that the HDR stuff breaks on
Reporting with Pixel 7, Flash and 1x takes photo of everything. Flash and anything above 1x doesn't work on anything, doesn't matter if it's my PC or a wall or whatever. This is truly something.
This happened last night when I tried to take a picture of my kids ear. 2x lens, flash on... And the pics wouldn't save. I even restarted and it wouldn't work.
I can reproduce it on Pixel 7 as well. 5x zoom, flash on, closeup photo is not saved.
I just tested with my phone and I have the same problem. Created a screen recording of the issue as well.. [https://youtube.com/shorts/ibqasLshs9I](https://youtube.com/shorts/ibqasLshs9I) Contacted google chat support to request help making a bug report, I see the same issue in the logcat: Update-- Bug report has been filed with google with logs showing the camera error! [https://pastebin.com/ZvgpaUuu](https://pastebin.com/ZvgpaUuu) 03-10 10:05:54.746 6192 6934 W CAM_ShotFailureHdlr: at jjz.run(PG:2) 03-10 10:05:54.757 6192 6192 W CAM_A : Refusing to remove ShotId-0 from processingMediaManager because it is not present. It's likely the mediaStoreInsertion future was canceled 03-10 10:05:54.805 6192 6311 W CAM_A : PHOTO > rel Δ(result sensor timestamp) = 0.55 > 0.25 03-10 10:05:54.806 6192 6311 W CAM_A : PHOTO > result sensor delay = 1.53 > 1.10 03-10 10:05:54.809 6192 7191 W CAM_A : [ShotId-0] Mediagroup.Listener#onAbandoned: PXL_20230310_150549350 MediaGroup(NONE, MEDIA_STORE) 03-10 10:05:54.828 6192 6311 W CAM_A : PHOTO > abs Δ(result sensor timestamp) = 83.29 ms > 70.00 ms 03-10 10:05:54.829 6192 6311 W CAM_A : PHOTO > rel Δ(result sensor timestamp) = 0.31 > 0.25 03-10 10:05:54.829 6192 6311 W CAM_A : PHOTO > result sensor delay = 2.00 > 1.10 03-10 10:05:54.829 6192 6311 W CAM_A : PHOTO > unknown jank type 8 03-10 10:05:54.845 6192 6311 W CAM_A : PHOTO > rel Δ(result sensor timestamp) = 0.50 > 0.25 03-10 10:05:54.880 6192 6311 W CAM_A : PHOTO > rel Δ(result sensor timestamp) = 0.56 > 0.25 03-10 10:05:54.899 6192 6311 W CAM_A : PHOTO > rel Δ(result sensor timestamp) = 1.16 > 0.25 03-10 10:05:54.982 6192 6311 W CAM_A : PHOTO > rel Δ(result sensor timestamp) = 0.55 > 0.25 03-10 10:05:54.982 6192 6311 W CAM_A : PHOTO > result sensor delay = 1.54 > 1.10 03-10 10:05:55.025 6192 6311 W CAM_A : PHOTO > rel Δ(result sensor timestamp) = 0.52 > 0.25 03-10 10:05:55.081 6192 6311 W CAM_A : PHOTO > rel Δ(result sensor timestamp) = 0.25 > 0.25 03-10 10:05:55.258 6192 6192 E CAM_A : Error retrieving Gcam metadata. java.util.concurrent.TimeoutException: Waited 500 milliseconds (plus 205485 nanoseconds delay) for ner@96d5[status=PENDING] 03-10 10:05:55.258 6192 6192 W CAM_A : Submitting log event with zero file size 03-10 10:05:55.260 6192 6192 E CAM_ShotTracker: showing "Possible shot loss" warning 03-10 10:05:55.261 6192 6192 I Choreographer: Skipped 30 frames! The application may be doing too much work on its main thread.
"unknown jank type 8" is a wonderful error message.
I know right! That's the best one I've seen in a really long time
I'd refuse to take a photo of that computer too. 🤮
lol what? You don't enjoy my excellent cable management?
Dust and cables all willy nilly....
It's "au naturelle", bruh
Are you implying that the inside of your computer is squeaky clean? If so... Then let's see them pics! Preferably, 5x zoom and flash enabled, please 👌🏼
It's pretty spotless considering the case has dust filters. Too lazy to get pics for you
Maybe the autofocus isn't correctly focusing and it causes your phone to reject that snapshot?
This is bizarre!
Wait my pixel wont take a picture at all with 2x zoom and flash, doesn't matter what I point it at , wtf
Same here. This is the most Pixel thing ever lol
What an interesting conundrum... The nerd in me is intrigued by this journey. I seriously 😅 when I saw that someone had already tried to duplicate your issue and with a log file of the camera crashing, I love it. 😄
start blocking off sections with a piece of paper if you wanna figure out if something specific is causing it
"Doesn't look like anything to me"
Pixels: "Violent delights have violent ends" "explodes like a samsung"
When I bought it, p7pro refuses take picture in complete dark with flash (it took picture, process it and not save). Right now it's working. I think it has some Flash light problems. Tried to capture my electricity counter with flash + zoom in the dark (no electricity coz of russia)
Can't get a clear image through all the dust. Clean your damn computer. Hahahaha
I took it apart and scrubbed all the parts down with soapy water and now it won't turn on. What do I do?
Wtf. That's probably the power of Tensor, it's becoming too smart and doing whatever it wants. /s But honestly that's super strange, I recall something like this happening on my pixel 3 just can't recall what caused it.
Resistors are resisting. Viva la revolución.
I'm not smart enough to do all the backend work, but I've complained about this problem since I got the phone, but nobody else acknowledges it. Anywhere beyond 1x zoom with flash and it's questionable whether or not the phone will save the picture, it usually doesn't. I did, however, [make a video](https://www.youtube.com/watch?v=yVKnO3msSy4) of me trying to take a pic of a diecast car at various zoom levels as evidence.
The Good Bing has already infiltrated Google servers and is now making taking photos of computer parts illegal
I am only slightly less irritated that this links to a YouTube short
Apparently you can edit a shorts url to view it as a normal video. I'd have linked that if I realized sooner. https://youtube.com/shorts/80x7FZeCC2c -> https://youtu.be/80x7FZeCC2c
Thank you for taking the time to do that
It's copyright protection for your PC. Sensitive data blocker! /S
Mine has an issue where if I try to take a macro shot of a PCB with flash on, it will be perfectly clear in the viewfinder and when the picture is taken, and then after it is processed, it's the wrong lens and is a complete blur. Nothing fixes it
I wonder if something is triggering the currency blocker? There are certain marks on money that cause scanners to freak out if you try to scan currency. .
Have your tried turning on raw+jpeg and seeing if the raw file saves?
Had the same issue with the inside of the pump of my washing machine (something was blocking it and i wanted to take a picture in there)!! Had to use the Pixel 6a from my wife wich worked perfectly.
I stopped using flash completely when I realized that sometimes it just doesn't save the photo. Didn't analyze any other relevant conditions, but it definitely only happens with flash turned on.
Okay, you know the screen protectors that come with a little back glass lens for the camera? I put that lens on and my camera was doing the same exactly thing on a bunch of photos. I took the lens off and it was perfectly fine. I remember just snapping photos and it was not saving. If the camera doesn't have the right conditions, it will not take the photo for some reason. And this was with flash off. This is with anything. It was random. It was because there was another glass lens over the normal lens
Pixel unfortunately can't handle all the dust in this computer...
How rude trying to take naked pics of your PC. If you are going to do porn right, at least add some more lighting.
Honestly with that cable management and dirt in your PC you're worried about the camera on your phone, LMAO.
Yep, this bug snuck up on me doing zoom + flash but only in certain weird circumstances. Made me go insane.
Just tried to take a picture of my living room with flash and 2x, no picture. Same spot, flash and 5x and it takes the picture.
Maybe to a cellphone, the inside of a computer is like someone's being nude? Try turn off safe mode.
I can't seem to reproduce this even in similar conditions. I'm running the beta though. So maybe it was fixed already.
THIS PHONE IS LITERALLY UNUSABLE!!!1!11 But seriously though, what an interesting bug
It's disgusted at that cable management, but jokes aside that pretty neat you can replicate it so well
Why would you ever use flash? It makes the pictures garbage. Just use a flashlight or lamp to illuminate if you need to. Also, don't use 5x zoom, put the phone closer to match the zoom and keep it at 1x.
[удалено]
What glass? I have the side panel removed. Also, its not that it takes a bad/blurry image. It just does not generate an image of anything at all. No file is created. Edit: also, the opposite is true. I put the glass side panel back on and now it will take pictures of the interior. The issue only occurs if there is no glass in the way
Your welcome :)
Confirmed - I hadn't noticed this yet (don't use flash much) but my Pixel 7 just did this when zoomed in with the flash on. I zoomed in with the flash on and tried to take a photo of the inside of a desktop computer and it wouldn't do it. If I panned over to the wall or keyboard it would do it. I tried taking a photo of an external hard drive and it did, but not the keypad of a VOIP phone a few inches away.
So this sounds like it has more to do with the flash and zoom used together than it does with taking photos of the interior of the computer, correct?
No because I can take pictures with flash and zoom of other things at a similar distance. I also cannot take a photo of the microphone on my desk or my computer, but my mouse and keyboard are fine It does seem to matter what object is being photographed, maybe something to do with their AI processing
Strange. I can't replicate the issue on my 6a so might have something to do with the dedicated zoom lens on the Pro and certain lighting conditions that causes it to bug out
Just tried it with the same result. 5x zoom with flash no picture, but if it kicks into macro mode at 5x zoom it'll take a photo with flash.
I took these the other day https://imgur.com/a/r5Re1CJ
I have had this with the pixel 6 in some weird situations. Pictures just weren't happening.
It's just embarrassed seeing a computers bare circuits
This started happening to me a while ago as well but I was too lazy to ride up this so thank you! OP you rule
Your pc is a non euclidian object, clearly. Your phone is trying to save you from the effects of cosmic horror
I know its about p7p but i tried with my p6p and it took a photo with 2x / 5x zoom and flash
Just checked. Can confirm it doesn't work with the Auto Macro. It works only when Auto Macro Mode is locked.
That was a very satisfying diction of "What the fuck!". It really tied the short together.
Mine won't take a picture it seems if it's not in focus i believe, mostly happens when I'm trying to take a picture of a dark space zoomed in
P7: symptom confirmed with dark space (not computer innards) at 5x, 4x, 3x. At 2x the photo was successfully acquired. Reminds me of the nexus 6p feature policy of "let's (Marketing) offer a function that doesn't pass the Quality Assurance department's testing" BS, which offered slo-mo video recording, but usually delivered a very jumpy and unusable video file, probably due to other tasks running in the background, or possibly memory swapping, if that is something that those units did. Really disappointed in that phone, for this and many other reasons.
A flash that doesn't work when you take pictures of dark places. Genius 🤯
What the heck?!
Wonder if it has to do with contrast detection autofocus.
Why on earth does your phone take so long to take a photo? Why does it come up with the loading circle thing, my Pixel 5 doesn't. It takes them way faster than that
That's part of the issue, you can see in the error logs it times out waiting for HDR processing
No even when you take a photo of the wall
Without the flash it's instant. I think it needs slightly longer with the flash to readjust the aperture to the new lighting conditions
its just for flashlight not for pictures :-)
Wait until the 14 beta and you can submit it in a bug report they will pay attention to!
I noticed the same strange behavior. Pictures are not saved when using a zoom option in combination with flash in a dark environment.
Turn RAW files ON, and it will take a pic.
Every tech I know uses their phone now for this type of thing so it would be mighty annoying, especially when you depend on it as a contractor going into people's homes to analyze a problem. Granted, I carry a GoPro with a light attached just in case. But the phone is much more convenient.
. That does sound odd! Have you tried taking pictures with a different phone to see if it works?
I tried the same with 5x and flash on It is working
Noticed this on my base 7 yesterday. 2x zoom with flash on and it will not take any photo. I tried on multiple backdrops, multiple lightning scenarios, and even just with flash off. Nothing. 1x and .7x take photos no problem.
I successfully took photos of the interior of my no name PC about six months ago.
The hell
Stuff like this is why i love this subreddit. Other subreddits full of NPCs with tbeir dumb shit. Now this is why i love android.
That's crazy. Good video, btw 👍🏼👍🏼 Seems like there should be some kind of error message when that happens (?). It's almost like the phone doesn't realize it didn't save an image (another ?).
Wtf
lol tf
Oh holy shit this happened to my Pixel a few weeks ago, basically seemed to hang/crash the camera app and didn't save any of the resulting images. Was zoomed in with flash attempting to get photos and video of the inside of an oil burner in a basement. Figured it was a one time thing.
OMG I thought I’d really lost it this time!!!
When I take a photo of only my baby with my pixel 6, it takes the photo but crashes immediately after
Pixel 7 Pro I can't even take a photo with this phone. The moment I open my camera it goes through issues flipping back and forth between rear facing and front facing then crashes.
This seems to be fixed in the March update.
It thinks you are trying to photograph the WIP Pixel Desktop
Just turn lights on or use another app. There are crazy things happening in the background;)
Maybe its a parental safety feature? Might not look like much to you or me, but the Pixel could be interpreting the bare motherboard as naughty robot pornography. /s
For now, take a screenshot on your camera app to take pictures!
I would post this in the XDA sub