(non-T-mobile)
I've been experimenting beyond my abilities, it seems. Successfully got Google Daydream to work. Successfully got Google Dialer/Phone to work. Failed at getting Google Camera to work. Now the photos I take with the OnePlus camera app seem to finalize themselves as a perfectly solid green. They also get tagged with EXIF data for a Pixel XL. Force close the moment I try to do video.
I've removed the Google Camera app.
I've gone into the build.prop file and removed the mod for Daydream which lied to say it was a Pixel.
I've restored the build.prop's permissions.
I've cleared OnePlus Camera data.
Rebooted many times.
Installed a generic app store camera. It takes non-green photos, but EXIF still says Pixel XL.
Ideas?
UPDATE... I never figured it out. Ended up going into settings and doing a reset. Even though backup & restore seems to work, it's still a little frustrating. One of the oddest things... in Settings -> About Phone -> Model... it listed "Pixel XL". In the desktop version of Mint, it suggested my paired device was "Marlin" (the codename of the Pixel XL). I hadn't altered anything to be Pixel XL-based. I had put in "sailfish" (the regular sized 1st gen Pixel) into build.prop, but not "marlin". Not sure which thing I poked to cause that mess.
Make sure you back up your things before changing your things!
I just found your thread, trying to fix this issue for myself. Disabled daydream and Google phone magisk modules then rebooted. Problem seems to have been resolved.
I am on the T-Mobile variant, flashed to international.
spudkinks said:
I just found your thread, trying to fix this issue for myself. Disabled daydream and Google phone magisk modules then rebooted. Problem send to have been resolved.
I am on the T-Mobile variant, flashed to international.
Click to expand...
Click to collapse
It's a shame... the Daydream thing seemed to work fairly well, considering the phone's screen resolution. If that's the cause, it's not really worth it for me to loose camera abilities.
Related
Hello
I have been having some problems with the main camera on the A500. It has different tints to it. Sometimes the picture seems to be divided in 4 and all 4 squares have a different hue to them. Restoring to factory settings seem to take care of it for a while. Initially I thought it was "skype" that messed it up, but it is not.
I just restarted the tablet and the camera is giving me a yellow tint, with a clear horizontal stripe about 3/4 inch wide through the middle.
The tab has stock 3.2 on it.
I was wondering if anyone has experienced similar problems and if there was a solution to the problem.
Thank you
Well, I would think the problem seems to be some app/apps you have installed. Based on when you do a factory reset, it goes away.
I would just do another factory reset. Then verify it went away. Run it for a couple of days WITHOUT installing any apps. This will probably rule out a hardware issue.
Then install apps, 1 at a time. Use the camera, and look for issues.
Thanx. I will give that a try.
I traced it back to Swift Key X keyboard for tablets. How is that even possible?
Also yahoo messenger is another one that ruins the camera. As soon as I install any of those apps and reboot, the camera is back to normal.
Does anyone out there use either of those apps?
mobilebone said:
I traced it back to Swift Key X keyboard for tablets. How is that even possible?
Also yahoo messenger is another one that ruins the camera. As soon as I install any of those apps and reboot, the camera is back to normal.
Does anyone out there use either of those apps?
Click to expand...
Click to collapse
So, everything is ok?
Rule #1,
Stay away from apps meant for phones.
Yes, they "may" have tested it it on "1" tablet, then gave it a clean bill of health. Maybe.
Moscow Desire said:
So, everything is ok?
Rule #1,
Stay away from apps meant for phones.
Yes, they "may" have tested it it on "1" tablet, then gave it a clean bill of health. Maybe.
Click to expand...
Click to collapse
I thought it would be ok. But after restarting a few times, the camera colors are off. I'm going to root and install a custom 3.2 to make sure it is not the hardware.
Spasiba for all your help )
any news about this problems.
it seems that my iconia has the same problem- i never noticed it because i dont use the rear camera.
i sold it it today and the guy who bought has described something like what you folks are talking about
the strange thing is that i had done a clean boot before i sold it, and the buyer hasnt installed anything on it yet.
im waiting to hear back from him after he tries another clean boot.
anyone else have any ideas ?
I'm having the same problem. I don't use it much, but the camera was ok before. When I tried using it this weekend, it showed colored translucent squares on the sides. It is not a config problem, as there are no effects turned on. The front camera works 100%. I will post a sample when I get home.
If I change the "whites" config to Incandescent, it kind of solves the problem. Sometimes, the squares appear, but not for most the time.
I believe this is not a harware issue, unless that whites configuration is made with hardware (highly doubt it). I don't have Swift key, or Yahoo messenger, or any other apps that use the camera (other than Skype, but it was already installed when the camera worked).
Did anybody find a fix to this? It seems it is only a problem on stock 3.2.
Edit: not an exclusive 3.2 stock issue, it appears that custom roms have this problem as well.
I have the same issue after ICS ota upgrade...
Any ideas?
I haven't had the issue since the ICS upgrade. Only tested once or twice, but it is working properly.
What I did to partially fix it was changing the White Balance to "Incandescent".
When taking pictures with the stock Motorola xamera app, I have a miserable time finding the shot. First I try to swipe to the left so the last image photographed comes onto the screen. THAT works, but then the screen freezes and I can't get out of it until I use the capacitive button to go back to the home screen. Then, when I go into the gallery to see the picture I just took, it is gone-like it was never there. However, occasionally some (not all) of these disappeared pix show up in the gallery hours later. I've tried deleting the app and then re-installing it, but it just doesnt seem to work correctly. Its the only thing about the Turbo which makes me want to throw it onto a nearby set of traintracks. Anyone else have the same issues or know what to do about it?
First off, I assume you mean camera (not xamera. correct me if I'm wrong). Second off, you shouldn't be able to uninstall it. If you installed updates for it via Google play then it might be a hardware problem. I would do a factory reset, and if it still doesn't work get it replaced. I don't know the details of the warranty, but from what I have heard it's quite extensive.
Thanks very much. And yes I meant camera....I guess I am mistaken-I didnt uninstall the entire camera app, just the updates to it. Still happening, but perhaps any bugs in the app might be fixed by the Lollipop update?
Lollipop isn't coming before February, and knowing Verizon I wouldn't bet on 2016 coming second
Is anyone else experiencing problems with their front facing camera? I've only had my moto x pure for a month. Last week, the camera was malfunctioning and when the app froze, I restarted my phone and the front facing option button was not there anymore. I tried clearing the cache and disabling it, uninstalling the updates and using a different app but it's still not there. Can anyone help me with this problem?
Full wipe.
lafester said:
Full wipe.
Click to expand...
Click to collapse
I did do a factory reset and it worked for a few hours but then it stopped working once again.
Then what apps did you install when it stopped working?
lafester said:
Then what apps did you install when it stopped working?
Click to expand...
Click to collapse
I didn't install any new apps. I was using the rear facing camera for about 2 hours on and off and sometimes it would lag. After that, the camera app started to freeze up every time I opened it up. Then the front facing camera stopped working.
I just noticed my front camera no longer works. It has been a while but it didn't hit me that there was a problem. Cerberus is set to take a photo after two missed passwords and I did notice it was only taking pictures from the rear camera a few weeks ago. Open Camera app doesn't see the front camera either.
I did a factory reset and that didn't help. I also thought I used to be able to pick the storage location but that doesn't show up in the menu.
I am on a 1575 with the latest patch (February Security). I am rooted (systemless) but I am not sure that comes into play since the factory reset didn't fix it.
I have the moto extended warranty including damage but would like to definitely rule out software issues before going down that path.
I continued troubleshooting by installing AICP (I had been running stock), unrooting and also tried booting into android "safe mode" and the front camera still didn't work. I finally rolled back to 5.1.1 using the return to stock tool and the front camera still did not work. I am now believing that the problem is hardware related so I am sending it in to Moto for repairs. Interestingly their website would not process the repair (it said I was not in the US even though my address clearly said US) so I called and they processed it. I have the FedEx label from them and they said the turn around is around 5 days. Back to my HTC M8 for a week or so.
Moto emailed me today and said that my warranty is void because I unlocked my bootloader. I was under the impression that hardware issues would still be covered not to mention that I bought the moto extended warranty. It looks like this is my last moto.
Sent from my m8wl using Tapatalk
Hello, after losing hope on my Pixel XL, the famous problem of Microphone and Audio sudden shutdown, with all Pixel XL versions (before 2017), some people related it to a hardware issue
and others even went for RMA and motherboard replacement, i found a solution for the problem.
Tested on 3 phones and works perfectly with up time of more than 35 hours,
The solution works only on Android 9 (P).
just follow the steps :
First you need to do a factory reset, without any third party apps
Second go to Apps and permissions bellow settings
Go to permissions, Microphone permissions
Disable all apps except Phone, Google, and Google play Services
Then go back to apps
Search for Device Policy App
Enable the app on the top menu
Then open app permissions and select Phone only, And all will work as a charm.
i am really happy that finally i am able to use my Pixel XL again ,
if my solution helped you and i know it will save a lot of money for you, you can buy me a coffee
Following for future
Sent from my Pixel XL using Tapatalk
It's the regular Pixel with the hardware issue. Have not seen this on xl.
Sent from my Pixel XL using Tapatalk
lafester said:
It's the regular Pixel with the hardware issue. Have not seen this on xl.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
both Pixel and Pixel XL, i had this issue since Oreo and now that's what fixed to problem for me.
i hope if anyone else has this problem tries this solution if it works for him.
Hi, I've tried your solution with no avail, can you specify more clearly your step by step guide?
Do you follow or skip all the prompt by Google (to connect Wi-Fi, Google Account, set password, etc)?
Do you need any restart before downloading Apps?
Can I re-enable Microphone for my other apps (camera, Messages, YouTube, etc)?
"Disable all apps except Phone, Google, and Google play Services"
And, I don't see any "Google play Services" toggle in my Microphone permission.
Google Pixel (1st Gen) user
wisnusewu said:
Hi, I've tried your solution with no avail
Click to expand...
Click to collapse
That's because this is not a real solution. The audio manufacturing defect is a hardware issue, which you can't fix by simply factory resetting and disabling some permissions. I have had it with 3 Pixel's, it sucks
great post. Just providing another data point that this didn't work for me hopefully i can hold out till pixel 4 later this year....
esuuuu09 said:
great post. Just providing another data point that this didn't work for me hopefully i can hold out till pixel 4 later this year....
Click to expand...
Click to collapse
Yeah, I just tried this on my wife's Pixel XL and it didn't work for me either.
I got the solution for Google pixel mic not working There is a problem in Google assistant step 1-disable Google app running in background .
Step 2 off all settings of Google assistant.
Step 3 reboot your phone.
This will work 100%
If it is not working
Try uninstall the every apps which use microphone in background.
Thankyou
I have an Australian bought Pixel 4, build: QQ1B.200205.002, Security patch level 5 Feb 2020, stock factory firmware, not rooted. Bought it on the first week of release, so had it for a while now.
Since about a week ago my phone stopped responding to the "ok-google" hotword in sleep and locked modes. Restarting the phone temporarily fixes it, but it stops again after a while. Especially if I don’t use the phone for an hour or so.
It used to work quite reliably before. Voice match is enabled, also retrained the voice model but that didn’t help. Haven’t installed any new apps recently, nor recall changing any settings. I only have a handful of very popular 3rd party apps like Waze, Tunein, Skype, Outlook, Viber, Whatsapp a couple of banking apps etc., but no games or optimiser apps of any sort.
Any ideas?
Thanks.
I had similar issue. I had to disable battery optimisation for the Google app. Seems to have cure it
Thanks for the reply, I tried changing battery optimizer settings for Google app, failing that I even did a factory reset. Still nothing. Looks like I’m not alone with this particular problem: https://support.google.com/pixelphone/thread/27204195?hl=en
Check your case, small cutouts affected my microphones on my Galaxy Note8 two years ago.
Received the march update, but the problem still exists.
vonDubenshire said:
Check your case, small cutouts affected my microphones on my Galaxy Note8 two years ago.
Click to expand...
Click to collapse
Pretty sure the case has nothing to do with it, because it used to work fine with the same case till a month ago, it works for a while soon after the phone is restarted, and there are many others experiencing the same problem as noted in the above google community thread.