[ad_1]
In our opinion, Google Pixels has some of the best cameras, but there is a way to further reduce the performance of a stunning photo: it is sometimes unnecessary to keep this snapshot you remember. And, as far as we can judge, this remains a problem for Google's new Pixels 3 and 3 XL.
I do not have any music apps stopping randomly on my Pixel 2 XL, but whole photos are not saved all the time.
Pixel 3 suffers from the same problem? Absolutely unacceptable. https://t.co/IFpjYEH8nY
– Artem Russakovskii (@ArtemR) October 16, 2018
Over the past few days, the blogosphere reporting information on Android has been the subject of much discussion on Twitter, with impressions and insights from Google's latest phones being quickly exchanged. A point more people seems to agree The problem is that this new batch of pixels continues to suffer the same problem as in previous iterations, where the pictures taken are not always saved.
I have arrived several times. That's the kind of thing that's happening on phones at $ 199. Really ridiculous that Google still has random flaws in its camera application like this. https://t.co/52HRC85Lj7
– Andrew Martonik (@andrewmartonik) October 18, 2018
Artem from the Android Police has released its report to the community / r / Android from Reddit (where it has been gilded twice in the past 24 hours) and to / r / GooglePixel, and comments posted on Twitter seem to indicate that It may not be exclusively a pixel problem, occurred on older Nexus devices as well as on other phones designed to run the Google Camera application. Some reports report similar behavior on third-party hardware and software from manufacturers such as Samsung, Essential, LG, and Nokia. It is therefore possible, if not probable, to be a symptom of an underlying Android problem.
I had several pictures taken on my 3XL review unit not save. I was just thinking about going crazy
– David Imel (@DurvidImel) October 18, 2018
Regardless of the devices involved and the precise cause, this is a problem still present on the latest Google phones. Visitors to the Google Product Forum article on the subject have come up with a method that more systematically triggers the problem: If a phone is locked or exits the device application photo while HDR + processing is in progress, it is unlikely that the photo being processed has been recorded. (I can not reproduce the behavior of my Pixel phones with these instructions, even though I've experienced this problem in the past, so it's not a fully reliable trigger.)
Based on the method of this so-called trigger, some people think that it is because the camera application stops running before it finishes processing the photo in question. According to the chief editor of XDA Developer and the noted tinkerer of the API Mishaal Rahman, the Google Camera app is supposed to be "pinned" in memory, which means that it should not actually quit / kill the application when the focus changes. Some have speculated that Google Photos could be responsible for the problem: it feeds the gallery into the Google Camera app and starts / stops all alone in the background.
I've said it before and I'll say it again: this has been happening since the Nexus 5X / 6P generation. The 5X had the habit of doing CHARGE. I've lost some important photos, it's terrible that it still is not repaired!
– Kieron Quinn ? (@ Quinny898) October 18, 2018
Whatever the real cause, a workaround preventing the loss of photos has been discovered. According to reports on the product forums, disabling the battery optimization and dewatering of the camera application corrects the problem.
We contacted Google about this story a day ago, but at the time of publication we had not received an answer yet. We will update our coverage if it is available. In the meantime, those who have encountered the problem should probably try not to forget to leave the camera application open until the processing of the photos is completed, or consider changing some power optimization settings.
[ad_2]
Source link
