Database Info

SOLVED: I just want working continuous auto focusing video recording.

]Okay, now I understand this phone simply have this problem where the camera constantly tries to refocus during video recording and it affect all OnePlus, this is my third OnePlus.
For some reason the Cyanogen Rom and roms based on it lack some drivers that allows continuous autofocusing to work correctly while video recording. Depends on what camera apps you use, the autofocusing will either not work, or it will continuously tries to re-focus nonstop. ColorOS however does have this function working correctly.
Solution: Use ColorOS + CameraNext or Google Camera.

If it matters that much to you then find the bug report on Jira and up vote it, that's the only real effective way to have an impact. You're not likely to find a fix at the ROM level.
Transmitted via Bacon

See post 1.

eksasol said:
]Okay, now I understand this phone simply have this problem where the camera constantly tries to refocus during video recording and it affect all OnePlus, this is my third OnePlus.
For some reason the Cyanogen Rom and roms based on it lack some drivers that allows continuous autofocusing to work correctly while video recording. Depends on what camera apps you use, the autofocusing will either not work, or it will continuously tries to re-focus nonstop. ColorOS however does have this function working correctly.
Solution: Use ColorOS + CameraNext or Google Camera.
Click to expand...
Click to collapse
Thanks for posting a solution. This problem is driving me crazy enough to sell my phone since I often need to use it to take short videos at work, and it is so embarrassing to have to show the videos to others that I have taken to also carrying around a small point-and-shoot, and this is not acceptable. I have tried many roms and many camera apps, but all of them have the video refocus issue.
However, I don't see Color OS in XDA. Is there a rom thread for it? I will try anything to salvage this phone since I love it except for this problem.

phoneturf said:
Thanks for posting a solution. This problem is driving me crazy enough to sell my phone since I often need to use it to take short videos at work, and it is so embarrassing to have to show the videos to others that I have taken to also carrying around a small point-and-shoot, and this is not acceptable. I have tried many roms and many camera apps, but all of them have the video refocus issue.
However, I don't see Color OS in XDA. Is there a rom thread for it? I will try anything to salvage this phone since I love it except for this problem.
Click to expand...
Click to collapse
You'll find several builds of ColorOS in our General section.
Transmitted via Bacon

This also appears to be a fix
I flashed the v20 mod for the app at http://forum.xda-developers.com/oneplus-one/themes-apps/app-cameranext-modded-t2999275 and it does not continually autofocus. I saw no need to flash the "click fix" since it is does not click when using it. I am on KK Slim.

phoneturf said:
Thanks for posting a solution. This problem is driving me crazy enough to sell my phone since I often need to use it to take short videos at work, and it is so embarrassing to have to show the videos to others that I have taken to also carrying around a small point-and-shoot, and this is not acceptable. I have tried many roms and many camera apps, but all of them have the video refocus issue.
However, I don't see Color OS in XDA. Is there a rom thread for it? I will try anything to salvage this phone since I love it except for this problem.
Click to expand...
Click to collapse
The official ColorOS firmware for some reason I could not get to boot on my phone, but you have to use the official version if you want working OTA updates. And it lack Gapps so you have to manually install it.
You could use other custom version like this one which is what I'm using, it's flashable using TWRP. http://forum.xda-developers.com/oneplus-one/general/rom-4-4-2-coloros-2-0-36beta-t2955853
The official OppoCamera.apk still do not record with continuous focusing, but the CameraNext.apk and Google Camera does.

6.0 Marshmallow: Missing EQ and sound settings are hidden in Play Music

The audio effect settings are now hidden in the Play Music app. I disable the app, since use Amazon for downloads (no device restrictions) and Poweramp for music. None the less, you can still access the audio effect settings, even if Play Music is disabled.
It is the same audio effect settings and appears to still be global. If it were linked to the Play Music app, I should not be able to mess with settings when the Play Music app is disabled, but I can. I created a shortcut to the Audio Effects with QuickShortcut (handy app!).
Audio Effects are accessible with the QuickShortcut app, so no need for the Play Music app.

That's just equalizer it was always there , on 5.0 sound effects was gone and put back. All you do is disable default EQ app.
Sent from my XT1575 using Tapatalk

It only works on supported apps.
Sent from my XT1575 using Tapatalk

shoman94 said:
It only works on supported apps.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Unless you use viper 4 Android under normal mode.
Sent from my XT1575 using Tapatalk

The equalizers came back after the new play music update.

The Audio Effects were located in the sound page of settings (at the top). They are gone now, but can still be accessed as noted above and without Play Music active (I don't use it).
Testing Youtube and other apps. it sounds like the settings are global (for what I checked), as they were prior to the super great amazing fantastic MM update. All of those adjectives are sarcastic, since I see no improvements but do notice the EQ setting missing from where they were and connecting to a PC went from simple fast connection, to a sporadic pain sometimes.

No, it isn't global anymore.. please test further.
Also the left and right channel doesn't switch anymore when rotating in landscape.. check for right/left channel tests in Youtube.

cruzargel said:
No, it isn't global anymore.. please test further.
Also the left and right channel doesn't switch anymore when rotating in landscape.. check for right/left channel tests in Youtube.
Click to expand...
Click to collapse
yes, this. why in the HELL would they remove that? did people seriously complain that they thought this was a glitch? wouldn't surprise me, since most people are dumb lol. this annoys the piss out of me.

jayochs said:
yes, this. why in the HELL would they remove that? did people seriously complain that they thought this was a glitch? wouldn't surprise me, since most people are dumb lol. this annoys the piss out of me.
Click to expand...
Click to collapse
Maybe if they'd done it correctly from the start -- meaning with no gap in playback, or at the very least a crossfade between channels -- no one would have complained and it could've stayed.

Marshmallow seems to have broken eq. I cannot get audio effects or market equalizer to do anything more than placebo eq. Even some apps with built-in eq have their eq break. . Bluetooth, any way. Yet, to test over eat buds.
---------- Post added at 03:01 PM ---------- Previous post was at 02:56 PM ----------
You can also see at a glance the eq of audio effects is pathetic, if it happened to work. . In real world, there is a huge need for huge adjustments in ear buds, speakers, environments. . The variation of sound setup is huge. .
Not to mention BBE or other clarification effects. Which is essential, on top of eq.

Workaround
Now that we know that this doesn't work, (and probably isn't going to be a priority to fix in the next software update, given Lenovo's haphazard nature of releasing broken patches) what's the best workaround? Can Viper4Android be used with the stock, rooted Rom? Or can this blunder only be fixed with a custom Rom?

Bill720 said:
Now that we know that this doesn't work, (and probably isn't going to be a priority to fix in the next software update, given Lenovo's haphazard nature of releasing broken patches) what's the best workaround? Can Viper4Android be used with the stock, rooted Rom? Or can this blunder only be fixed with a custom Rom?
Click to expand...
Click to collapse
Viper works fine on stock. I highly recommend Arise audio (Viper is included).

Success!
ffejy462 said:
Viper works fine on stock. I highly recommend Arise audio (Viper is included).
Click to expand...
Click to collapse
It's interesting that you mention that because I had literally just discovered A.R.I.S.E. and installed it not even two hours before you posted . Thankfully, I can report that it does appear to be working brilliantly on the stock ROM when using the "Leviticus 1.3" version. :fingers-crossed:
I'll report back if I discover any issues, but so far, it looks good!

Bill720 said:
It's interesting that you mention that because I had literally just discovered A.R.I.S.E. and installed it not even two hours before you posted . Thankfully, I can report that it does appear to be working brilliantly on the stock ROM when using the "Leviticus 1.3" version. :fingers-crossed:
I'll report back if I discover any issues, but so far, it looks good!
Click to expand...
Click to collapse
Cool! I've been using Arise since they started. Fantastic group of developers. Super nice and helpful. There are tons of options, but it can be simple as well. I'd recommend the newer Deuteronomy builds, but they're all really good. Any questions, just ask in the arise thread. Fyi there are a few incompatible versions. It'll show itself trying to take video and it'll stop with an error message that says that something else is using the mic.

Lucked out
ffejy462 said:
Cool! I've been using Arise since they started. Fantastic group of developers. Super nice and helpful. There are tons of options, but it can be simple as well. I'd recommend the newer Deuteronomy builds, but they're all really good. Any questions, just ask in the arise thread. Fyi there are a few incompatible versions. It'll show itself trying to take video and it'll stop with an error message that says that something else is using the mic.
Click to expand...
Click to collapse
I do remember seeing something like that when reading through the threads, but let me check this version real quick...
Phew! Video recording is working! Crisis averted. Is there anything else to watch for with these audio tweaks?

Bill720 said:
I do remember seeing something like that when reading through the threads, but let me check this version real quick...
Phew! Video recording is working! Crisis averted. Is there anything else to watch for with these audio tweaks?
Click to expand...
Click to collapse
Obviously with Viper processing, battery drain will be a bit more. Otherwise just enjoy the music.

Power tabulation
ffejy462 said:
Obviously with Viper processing, battery drain will be a bit more. Otherwise just enjoy the music.
Click to expand...
Click to collapse
Will do . I assume the additional processing required would be comparable to what I experience right now with the Note2 and equalizer found inside of S-Tweaks. Hopefully not when it's sleeping and not playing any sound though.

solved.
Go to apps in settings, scroll to default equalizer ( in my case sound alive). Disable that and then go to music app (eg spotify) and then go to the equalizer settings and it will come up with your own equalizer app (eg V4A)

Android P hidden API removal outrage!?

Now that the Android P preview is out and we developers start seeing the consequences of the upcoming hidden API remove, i wonder if everyone is fully aware of the profound paradigm shift this will be!?
Going through my app Automate, i can say it will be painful. A lot of common Android features, excepted by users for years, will likely cease to function, or have to be reverted back to buggy behavior.
I expect and accept (my app users will not) that features requiring a rooted device will no longer be accessible, like toggling tethering, NFC, mobile data, etc.
But a lot of harmless hacks will also stop working, and the Play Store is full of innovative apps using them, like audio routing, BT utilities, whatever.
The more dire consequence is for working around current and future bugs. My app is has implemented a lot of workarounds relying on reflection for Android versions going back to 4.0. Even Google does this, like the PRNGFixes a few years ago.
In the future such workarounds may not be possible! Expecting Google to start fixing bugs is a pipe dream. I've report ~30 issues myself, starred 300+, and the majority of them are ignored, or has been flagged "Assigned" for years, "WontFix" or "Obsolete".
The proper solution for preventing use of the hidden APIs are to protect the "dangerous" ones with permissions, not blocking us from accessing them altogether.
We developers are battling Android fragmentation with every new release, often using reflection, so claiming to do this for "Improving Stability" is an insult.
I was hoping XDA developers, and others with influence, could get Google to listen, like with the Accessibility API usage ban.
I don't think a single article, which seems to overlook the serious consequence, will suffice.
Developers need to revolt, or if you've already conseede, at least report your hidden API usage here.
PS. Please, anyone with a rooted Android P, could you help me with some tests?

ballzak said:
I expect and accept (my app users will not) that features requiring a rooted device will no longer be accessible, like toggling tethering, NFC, mobile data, etc.
Click to expand...
Click to collapse
Not sure this part is true. According to Quinny899:
"I've just noticed when poking around in P that the warning toast for reflection doesn't fire when the code is run as root
They're not blocking root
That's why my apps still work then"
Let me see what joaomgcd has to say. He's still going through the P release IIRC.

MishaalRahman said:
Not sure this part is true. According to Quinny899:
"I've just noticed when poking around in P that the warning toast for reflection doesn't fire when the code is run as root
They're not blocking root
That's why my apps still work then"
Let me see what joaomgcd has to say. He's still going through the P release IIRC.
Click to expand...
Click to collapse
I'm only seeing the warning dialog in debug builds.
Everything still works in my app as well, since Google doesn't enforce the blacklisting yet.
Them excluding root processes gives some encouragement, but the most serious consequence remain.

ballzak said:
I'm only seeing the warning dialog in debug builds.
Everything still works in my app as well, since Google doesn't enforce the blacklisting yet.
Them excluding root processes gives some encouragement, but the most serious consequence remain.
Click to expand...
Click to collapse
Yes, I agree with you that this is a serious change. Our very own One-Handed Mode app will cease functioning in the final P release. There's nothing we can really do about that.

MishaalRahman said:
Yes, I agree with you that this is a serious change. Our very own One-Handed Mode app will cease functioning in the final P release. There's nothing we can really do about that.
Click to expand...
Click to collapse
That's sad. As i said, there's lots of innovative apps that will be affected.
Hence my wonderment for lack of outrage, we must make Google listen!

ballzak said:
That's sad. As i said, there's lots of innovative apps that will be affected.
Hence my wonderment for lack of outrage, we must make Google listen!
Click to expand...
Click to collapse
The problem is that we need developers to be outspoken about what will be broken in their apps because of these changes. If developers are upfront about what will happen, it will encourage users to get involved too. Right now, I only have my own example to share. And you are sharing your example. What are apps will be affected, and how will they be affected? Knowing that is key for getting support on this issue.

MishaalRahman said:
The problem is that we need developers to be outspoken about what will be broken in their apps because of these changes. If developers are upfront about what will happen, it will encourage users to get involved too.
Click to expand...
Click to collapse
Let's hope so, that's why i posted.
I fear developers are underestimating the consequences, once Android P goes live, and the blacklist kicks in, it's too late!

Hi there.
I too have this issue regarding some of my app's functionalities. What I'm doing is reporting any hidden API I use here. They seem to respond pretty quickly, at least they did with my last submission.
Did you try that? Thanks!

joaomgcd said:
Hi there.
I too have this issue regarding some of my app's functionalities. What I'm doing is reporting any hidden API I use here. They seem to respond pretty quickly, at least they did with my last submission.
Did you try that? Thanks!
Click to expand...
Click to collapse
I've reported 9 requests thus far, no response.

ballzak said:
I've reported 9 requests thus far, no response.
Click to expand...
Click to collapse
Interesting. I've reported 2 (one just today) but for the first one I got a response right away. I'm still figuring out how it'll affect my apps exactly.

joaomgcd said:
Interesting. I've reported 2 (one just today) but for the first one I got a response right away. I'm still figuring out how it'll affect my apps exactly.
Click to expand...
Click to collapse
Are you reporting "light graylist", "dark graylist", or both?
I'm currently only reporting the "light graylist" cases, since Google already decided to block the "dark graylist".
What Priority are you reports flagged as, P2 or P3?
I got to contact Google through some other channel if they're ignoring/binning my requests.

ballzak said:
Are you reporting "light gray", "dark gray", or both?
I'm currently only reporting the "light gray" cases, since Google already decided to block the "dark gray".
What Priority are you reports flagged as, P2 or P3?
I got to contact Google through some other channel if they're ignoring/binning my requests.
Click to expand...
Click to collapse
I reported one that isn't in those "gray" lists: RCS support. It's assigned a P3 priority.
I added another one (Bluetooth Tethering) which is light gray and is assigned a P3 priority as well.

joaomgcd said:
I reported one that isn't in those "gray" lists: RCS support. It's assigned a P3 priority.
I added another one (Bluetooth Tethering) which is light gray and is assigned a P3 priority as well.
Click to expand...
Click to collapse
Just added another request, for a bug workaround, all assigned P3.
Probably wont get a response on this one either. :crying:

Let us know if they ever respond and I'll do the same.

They've responded to another one of my requests now!

joaomgcd said:
They've responded to another one of my requests now!
Click to expand...
Click to collapse
Yey, 3 of 10 requests got a response now.
Seems like the intern on bug tracker duty has awaken. :fingers-crossed:

Did any of the bugs change to a "planned" status or something similar?

joaomgcd said:
Did any of the bugs change to a "planned" status or something similar?
Click to expand...
Click to collapse
No, two lesser issue seems to have been added to a "hotlist".
Enable "Full history" in the upper right corner on an issue page.

Check out a reply to one of my bugs
For future planning, I think we may want to consider some 'device automation' permission bucket.
Click to expand...
Click to collapse

All my reported APIs are now "assigned". Seems like good progress.

Best stock Oreo ROM to downgrade to? Giving up on Pie for now.

I'm ready to give up on Pie for now, but not ready to unlock the boot loader and go for custom ROMs. So, I think the last stock Oreo release was 47.1.A.16.20? So I think I want to find G8142_1308-6041_47.1.A.16.20-R4B_Customized_US.ftf and flash that with newflasher but I can't find that FRF anywhere. Any hints or suggestions? Maybe just bite the bullet and backup the DRM, unlock, and flash a custom ROM instead?
Problems in Pie on my G8142:
1. Many apps stop updating the screen if you have the screen lock set to None and turn the screen off/on a few times. Fixes for a while if you switch to another program and back. Doesn't happen if you have a screen lock enabled (even Swipe to unlock) but I don't like that. Seen it happen in Bumble, Tinder, OS Settings, Chrome (except there the web page goes black instead of maintaining the previous screen), Piktures (black screen instead of maintaining the image, like Chrome), Timely (where the countdown timer is still running, just the screen isn\'t updating to show that), Play Store, and Acrobat Reader. Even got it to happen IN THE INITIAL PHONE SETUP APP before connecting to my Google account when I reset to see if that helped.
2. Some apps don't work correctly on wireless data (TextNow and 2nd Line VOIP apps won't dial out or take inbound calls if not on WiFi on Pie, Waze loses connection every time you move from WiFi to wireless so you have to exit and re-open once you are out of WiFi range - though I'm not sure if this is exclusive to Pie or not, Grindr can't send or receive chats outside of WiFi - just shows Disconnected.)
3. Pie disabled call recording apps.

I don't have any of these problems and I'm on pie. I guess if u wanna stay on stock oreo u can. But pie doesn't even require drm keys anymore. I'm on lineage stock of pie and haven't wanted to go back to oreo since

lonewolfbtown said:
I don't have any of these problems and I'm on pie. I guess if u wanna stay on stock oreo u can. But pie doesn't even require drm keys anymore. I'm on lineage stock of pie and haven't wanted to go back to oreo since
Click to expand...
Click to collapse
Interesting! What do you mean by "pie doesn't even require drm keys anymore"? You mean a custom ROM with the DRM fix included? And good to know that lineage stock pie doesn't have these problems, I'm pretty interested in doing that in the smarted way possible.

rlowens said:
Interesting! What do you mean by "pie doesn't even require drm keys anymore"? You mean a custom ROM with the DRM fix included? And good to know that lineage stock pie doesn't have these problems, I'm pretty interested in doing that in the smarted way possible.
Click to expand...
Click to collapse
Sony no longer penalizes you for rooting ur phone.

lonewolfbtown said:
Sony no longer penalizes you for rooting ur phone.
Click to expand...
Click to collapse
Nice! When did that change? I'd like to read more about that.
Also, I'll go look for the current Lineage install steps. Unless you happen to have that link handy?

rlowens said:
Nice! When did that change? I'd like to read more about that.
Also, I'll go look for the current Lineage install steps. Unless you happen to have that link handy?
Click to expand...
Click to collapse
I don't have it handy. Sony decided that before the release of pie. The Los ROM should be In one of the categories below in the forums

lonewolfbtown said:
Sony no longer penalizes you for rooting ur phone.
Click to expand...
Click to collapse
That's not quite correct, the camera now works with or without DRM. There are still a couple of other higher function softwares that are disabled, including the bravia engine (X-Reality, Super Vivid) and HD for Netflix. There might also be some audio extras that don't work as well, like DSEE HX and ClearAudio+, but I'm not sure and would like for somebody to correct me on that.

Didgesteve said:
That's not quite correct, the camera now works with or without DRM. There are still a couple of other higher function softwares that are disabled, including the bravia engine (X-Reality, Super Vivid) and HD for Netflix. There might also be some audio extras that don't work as well, like DSEE HX and ClearAudio+, but I'm not sure and would like for somebody to correct me on that.
Click to expand...
Click to collapse
Yeah your right. Basically what he said is correct.

Question Portrait mode processing takes decades

Hi Guys,
Hope you all doing well.
So, I purchased an unlocked Pixel 7 Pro and got it delivered yesterday.
All seems good except camera which is very, very disappointing so far (obviously, the phone has the latest updates)
For example, no matter what picture I take in portrait mode, it takes 1-1.5 minutes (!!) to process it to add the blur which is insane as my 2 years old Notes 10 Ultra processes blur in 1-2 seconds. How is this even possible?
Do you guys have the same issue with portrait mode? I want to make sure its not my phone.
Also, I was reading that it is possible to add a blur to unprocessed picture from Google Photos but that option is simply missing from the menu no matter what picture I open.
For instance, Samsung Gallery app does add blur to all these unprocessed pictures so its not the picture itself. Google Photos simply doesn't have that option, its missing.
Google Photos also doesn't have any option to unblur a picture as its also missing. The was apparently one of the "perks" of Pixel 7 Pro but that option is not even there.
Do you guys also experience all this?
If the portrait mode processing is faster for you, can any of you kindly extract your camera and google photo apk and post it here? I will install these instead. Thanks a lot!

Try a factory reset. mine takes 4 seconds tops

Didn't help.
I didn't mention that I am using GrapheneOS.
Tried to flash stock Google image - and Portrait mode processing worked as expected.
I pulled out the original Photo and Google Camera apks from stock Google image, then installed Graphene again and installed these - same results.
It seems there are some additional libraries in stock image that are responsible for processing and they need to be installed in Graphene to make it work as expected? I couldn't identify any though - there was one called Pixel Camera Services that I also installed but still no joy.

VirtualWaver said:
Didn't help.
I didn't mention that I am using GrapheneOS.
Tried to flash stock Google image - and Portrait mode processing worked as expected.
I pulled out the original Photo and Google Camera apks from stock Google image, then installed Graphene again and installed these - same results.
It seems there are some additional libraries in stock image that are responsible for processing and they need to be installed in Graphene to make it work as expected? I couldn't identify any though - there was one called Pixel Camera Services that I also installed but still no joy.
Click to expand...
Click to collapse
So you are running a ROM, and or modded your phone and wonder why things don't work? SMH

VirtualWaver said:
Didn't help.
I didn't mention that I am using GrapheneOS.
Tried to flash stock Google image - and Portrait mode processing worked as expected.
I pulled out the original Photo and Google Camera apks from stock Google image, then installed Graphene again and installed these - same results.
It seems there are some additional libraries in stock image that are responsible for processing and they need to be installed in Graphene to make it work as expected? I couldn't identify any though - there was one called Pixel Camera Services that I also installed but still no joy.
Click to expand...
Click to collapse
Good luck with that. Graphene is a poor choice for people who want to use Google anything.

jaseman said:
So you are running a ROM, and or modded your phone and wonder why things don't work? SMH
Click to expand...
Click to collapse
jaseman said:
So you are running a ROM, and or modded your phone and wonder why things don't work? SMH
Click to expand...
Click to collapse
GrapheneOS is an OS not a mod, and Google Camera works on it for a few years now - it only requires GSF to run. There are many people on XDA who are using GrapheneOS on Pixel phones so its not a unique thing. I was hoping someone who is on it can advise if they experience the same issues.

VirtualWaver said:
GrapheneOS is an OS not a mod, and Google Camera works on it for a few years now - it only requires GSF to run. There are many people on XDA who are using GrapheneOS on Pixel phones so its not a unique thing. I was hoping someone who is on it can advise if they experience the same issues.
Click to expand...
Click to collapse
Graphene is a hugely modded OS with everything Google stripped from it. It is normal and expected for things to not work exactly the same as stock.

EtherealRemnant said:
Good luck with that. Graphene is a poor choice for people who want to use Google anything.
Click to expand...
Click to collapse
I agree, its a way out of Google so yes. I don't use any other Google aps so don't really need them. Such a shame the Cam is not working as expected - I might try GCAM instead.

VirtualWaver said:
I agree, its a way out of Google so yes. I don't use any other Google aps so don't really need them. Such a shame the Cam is not working as expected - I might try GCAM instead.
Click to expand...
Click to collapse
So then it looks like I was correct in my assumption...according to other respondents? You are running a heavily modded OS with Google stripped out of it. Of course you will have all sorts of negative issues. lol

VirtualWaver said:
Hi Guys,
Hope you all doing well.
So, I purchased an unlocked Pixel 7 Pro and got it delivered yesterday.
All seems good except camera which is very, very disappointing so far (obviously, the phone has the latest updates)
For example, no matter what picture I take in portrait mode, it takes 1-1.5 minutes (!!) to process it to add the blur which is insane as my 2 years old Notes 10 Ultra processes blur in 1-2 seconds. How is this even possible?
Do you guys have the same issue with portrait mode? I want to make sure its not my phone.
Also, I was reading that it is possible to add a blur to unprocessed picture from Google Photos but that option is simply missing from the menu no matter what picture I open.
For instance, Samsung Gallery app does add blur to all these unprocessed pictures so its not the picture itself. Google Photos simply doesn't have that option, its missing.
Google Photos also doesn't have any option to unblur a picture as its also missing. The was apparently one of the "perks" of Pixel 7 Pro but that option is not even there.
Do you guys also experience all this?
If the portrait mode processing is faster for you, can any of you kindly extract your camera and google photo apk and post it here? I will install these instead. Thanks a lot!
Click to expand...
Click to collapse
You should have mentioned first that you're NOT on the STOCK ROM before getting all "disappointed" about your phone.

ekin_strops said:
You should have mentioned first that you're NOT on the STOCK ROM before getting all "disappointed" about your phone.
Click to expand...
Click to collapse
Honestly, this topic is not about comparing phones - I own both and providing my feedback. Even with stock ROM, Pixel cannot match the capabilities of 2 years old Notes 20 Ultra - for example, Note 20 Ultra has real-time video background blur with different effects whilst Pixel's Cinematic mode doesn't offer many background effects and works much worse. Note 20 Ultra's portrait mode has much more different real-time effects, etc. But as I said this topic is not about comparing but trying to resolve a problem, so its pointless to write comments like this.

I took this one of my daughter just to see and mine did not have that problem. It processed quick quickly

VirtualWaver said:
Honestly, this topic is not about comparing phones - I own both and providing my feedback. Even with stock ROM, Pixel cannot match the capabilities of 2 years old Notes 20 Ultra - for example, Note 20 Ultra has real-time video background blur with different effects whilst Pixel's Cinematic mode doesn't offer many background effects and works much worse. Note 20 Ultra's portrait mode has much more different real-time effects, etc. But as I said this topic is not about comparing but trying to resolve a problem, so its pointless to write comments like this.
Click to expand...
Click to collapse
It's pointless to write something is broken, and then ask people if theirs is broken too, while ignoring completely the fact that you're on a CUSTOM ROM while people are clearly saying "It's working" fine, yes, on stock ROM.
I'm not trying to argue now, but it's important to mention such stuff so people can actually "help" in a more "accurate" way instead of just writing "it works fine for me", while they're not using the same ROM as you do.
Peace

jaseman said:
So then it looks like I was correct in my assumption...according to other respondents? You are running a heavily modded OS with Google stripped out of it. Of course you will have all sorts of negative issues. lol
Click to expand...
Click to collapse
Please do your research before posting - Google Camera does work on GrapheneOS with Google Services installed.
If you know anything about the issue, then please respond.
If not, its pointless making comments like this and flooding the thread - let other people who are running Graphene to read and share their experience.

VirtualWaver said:
Please do your research before posting - Google Camera does work on GrapheneOS with Google Services installed.
If you know anything about the issue, then please respond.
If not, its pointless making comments like this and flooding the thread - let other people who are running Graphene to read and share their experience.
Click to expand...
Click to collapse
The issue you're having is not there in the stock ROM, something you didn't mention in your thread.
But I'll walk away because you're clearly ignoring the fact that you didn't mention here a KEY factor, because it's definitely the issue of your CUSTOM ROM and not stock ROM. So, don't get angry when you get responses like this.

jaseman said:
So you are running a ROM, and or modded your phone and wonder why things don't work? SMH
Click to expand...
Click to collapse
Literally.

VirtualWaver said:
Didn't help.
I didn't mention that I am using GrapheneOS.
Click to expand...
Click to collapse
It's cuz you're running graphene os