Hey! Today I made a phone call and the other person couldnt hear me. Then I tried with another person and the same, then with Whatsapp and same... I can send audios on whatsapp, so the problem is the other microphone.. Even "Ok, Google" isnt working.. I tried restarting and the safe mode too.. Any idea?
Factory reset or RMA are the two things I'd try, neither one is easy.
gariuz said:
Hey! Today I made a phone call and the other person couldnt hear me. Then I tried with another person and the same, then with Whatsapp and same... I can send audios on whatsapp, so the problem is the other microphone.. Even "Ok, Google" isnt working.. I tried restarting and the safe mode too.. Any idea?
Click to expand...
Click to collapse
The only time that has happened to me is after installing an app that required Mic permissions and then had issues releasing the Mic.
maybe revoke all Mic permissions from your apps?
parakleet said:
The only time that has happened to me is after installing an app that required Mic permissions and then had issues releasing the Mic.
maybe revoke all Mic permissions from your apps?
Click to expand...
Click to collapse
I will try both (RMA) is the most difficult because I purchased the phone on December via Amazon and I live in Argentina =(
gariuz said:
I will try both (RMA) is the most difficult because I purchased the phone on December via Amazon and I live in Argentina =(
Click to expand...
Click to collapse
Edit. I tried removing all mic permissions. Didnt work..
Later I will try factory restore... Hope it works
Edit 2. Tried factory restore, didnt work =(
Well, I suppose I will have a phone without mic... Great again Google, first Nexus 6p bootloop, now this....
I have been bitten by this bug. I called google, they had me run in safe mode and do a full wipe and reboot. The tech support person thought it was due to 3rd party software that I had installed. Sigh. I bought my phone from google direct for around $1000 5 months ago. I think I will try again and insist on an RMA unit. I have not seen any official acknowledgement of this bug (which appears to be hardware in nature).
Just went through this myself last week. Same symptoms as @Guriuz. Also had the same support experience as @hawgguy, Support went through safe mode, factory reset, reinstalling factory image, etc. I knew it wasn't an app/software issue as I went through troubleshooting myself already but indulged the support agent. (I had even upgrade to Android P beta, and also back down to a previous version of Oreo just for giggles but nothing helped, same symptom with the mic.) Eventually though, I just stopped him and said what I thought the issue was and requested an RMA. New phone is arriving this week sometime. Hopefully these refurbs are QA'd sufficiently.
Having the same issue. Tried all the tricks I've read on the Google forums (canned air, wipe, etc). After two hours (ugh!!) at the Verizon store they decided to send me a refurb unit. Should be here monday.
Related
I received my Pixel XL 128GB on this past Wednesday and I have been having constant crashing issues with my Camera. I first thought it may have been the app itself so I tried using various camera apps from the playstore which didn't seem to help.
I tried to delete the app data as well as the cache
deleted any app that may use the camera such as facebook and instagram
reset the phone back to factory twice, trying both the stock and stock updated camera app
I even tried various ROMS like PureNexus and AOPK with no fix in sight.
The error message I receieve is "Camera Error - Can't connect to the camera" prior to that error message the screen is black utilizing the forward facing and rear camera.
I called up support and of course got an idiot Google Customer support rep who could barely speak english telling me that it may be hardware related and that I would it would needed to be replaced.
Is there any other options at this point short of sending my phone back and having them send me a replacement? They are telling me they want to do an authorization hold of another $900 for them to ship me a replacement phone first which is absolutely laughable.
ohms139 said:
I received my Pixel XL 128GB on this past Wednesday and I have been having constant crashing issues with my Camera. I first thought it may have been the app itself so I tried using various camera apps from the playstore which didn't seem to help.
I tried to delete the app data as well as the cache
deleted any app that may use the camera such as facebook and instagram
reset the phone back to factory twice, trying both the stock and stock updated camera app
I even tried various ROMS like PureNexus and AOPK with no fix in sight.
The error message I receieve is "Camera Error - Can't connect to the camera" prior to that error message the screen is black utilizing the forward facing and rear camera.
I called up support and of course got an idiot Google Customer support rep who could barely speak english telling me that it may be hardware related and that I would it would needed to be replaced.
Is there any other options at this point short of sending my phone back and having them send me a replacement? They are telling me they want to do an authorization hold of another $900 for them to ship me a replacement phone first which is absolutely laughable.
Click to expand...
Click to collapse
never experienced anything like that. I think a replacement is probably your best option given that you're already done a factory reset. The one remaining option I might suggest is flashing a full factory image downloaded from Google.
IMO, its not all that "laughable" that google would ask to put a authorization hold on your account. Its only a pending charge and is never actually processed unless you don't return the old phone.
mlin said:
never experienced anything like that. I think a replacement is probably your best option given that you're already done a factory reset. The one remaining option I might suggest is flashing a full factory image downloaded from Google.
IMO, its not all that "laughable" that google would ask to put a authorization hold on your account. Its only a pending charge and is never actually processed unless you don't return the old phone.
Click to expand...
Click to collapse
I have actually done a full factory flash from Google.
Well when I had financing from Verizon or T-Mobile and I had an issue with the phone they sent a replacement first and I had a time frame in which to send the phone back or I would get charged, they never held funds first.
Financing devices works a little different and each company has their own policies. I haven't had an RMA with Google ever, but with Moto (after it was bought by Lenovo) they required a hold and there have been a few other places that if they sent a device to me before I sent one to them they would put a hold on my credit card. I always considered it a standard procedure. As for the Pixel's camera, while there have been some issues mentioned here and other places about camera issues yours seems unique, almost like the camera component was DOA. I would RMA if it was my device.
Sent from my BTV-W09 using Tapatalk
I found this on Google's forum: Camera issue seems to be solved with beta 2 update, can anyone else confirm?
Jason70
5 days
Jason70
yep, 7.1.2 seems to have worked... fingers crossed.... not got camera to fail and it always failed at my workplace due to low signal, but this morning its running great!
ThomasBHV
5 days
ThomasBHV
7.1.2 (NPG471) Yes currently it work well
The above post has more to do with phones in low signal areas that have the camera freeze up usually with purple lines across some of the photo. That issue has been on going mostly with European variants since release. This does not give the unable to connect error.
Sent from my BTV-W09 using Tapatalk
Thanks for all the responses but I guess Support was correct when they said it was the hardware. My new phone works without any issues.
The infamous Google Play "download pending" issue - best solution I found so far
I got my Pixel 2 XL on April, and I've already have this annoying issue 3 times.
2 days ago I have the issue again. I've contacted Google many times, and every time their support team ended up advising me to factory rest my phone because all other work around won't work (clearing the cash, Google play service, etc) .
I got so sick of Google ignore this issue, and this issue has been known for a long time.
I literately can't update any app nor installing any new app. I've tried every single work around I found online nothing worked for me.
I almost gave up yesterday and was about to factory rest my phone, however; while playing around I saw rebooting in " safe mode" option.
and guess what, when I reboot my phone in Safe Mode the issue disappears and I smoothly can update all my apps and install new apps.
However, when I boot my phone in the normal mode the issue exists, so I'm living in this stupid work around.
I wanted to share my experience because I'm frustrated and so sick if Google not taking this issue vert seriously even there are multiple posts on their official support website.
Never had such issue.
mataralhawiti said:
I got my Pixel 2 XL on April, and I've already have this annoying issue 3 times. 2 days ago I have the issue again. I've contacted Google many times, and every time their support team ended up advising me to factory rest my phone because all other work around won't work (clearing the cash, Google play service, etc)...
Click to expand...
Click to collapse
Life does not end when you FDR... and who knows, you may even fix your issue. Better yet, fastboot a full factory image wiping all your partitions in the process. Back up your stuff and get to it.
I just use apk mirror, in tired of the issue as well.
I've been having wifi and Bluetooth issues since February update. Bluetooth keeps giving the message "Bluetooth keeps stopping" or something like that and won't connect to anything or stay on for that matter. When this happens wifi also goes. If I go in in clear Bluetooth cache and storage then reset my phone 50% of the time it will work after the reset but fail again shortly after connecting to a Bluetooth device or turning it on. Does anyone have suggestions on what I can do. I am rooted and bootloader unlocked. Is there a way to factory reset without losing all my internal storage. I have way too much stuff on my phone to lose it all. Thanks in advance.
I would use Titanium backup to backup the apps and their content. Then, do the factory reset.
Sent from my Pixel 3 XL
---------- Post added at 10:09 PM ---------- Previous post was at 10:06 PM ----------
You can also connect a USB-c drive and copy to it any important files you may have. I got one with 256 Gb from Amazon some time back for about $50. I regularly copy to it my important files. My pics are automatically uploaded to my Google cloud.
Sent from my Pixel 3 XL
vwood2121 said:
I've been having wifi and Bluetooth issues since February update. Bluetooth keeps giving the message "Bluetooth keeps stopping" or something like that and won't connect to anything or stay on for that matter. When this happens wifi also goes. If I go in in clear Bluetooth cache and storage then reset my phone 50% of the time it will work after the reset but fail again shortly after connecting to a Bluetooth device or turning it on. Does anyone have suggestions on what I can do. I am rooted and bootloader unlocked. Is there a way to factory reset without losing all my internal storage. I have way too much stuff on my phone to lose it all. Thanks in advance.
Click to expand...
Click to collapse
No. By definition, a factory reset is wiping your /data/media folder. Have you tried resetting your network (WiFi,mobile & Bluetooth) under reset options? Often times there is just no substitute for a clean install (flashing a full factory image, not just a factory reset). If you just factory reset, your problem may not be resolved. Since you are rooted there are many backup options. TiBu is one of the best. I think you'd be surprised how quickly you will be back up and running. ADB/Fastboot binaries were updated recently, so make sure you refresh those before starting.
Well completely wiped and reset up after about 15 with Bluetooth on it started again....any other suggestions
vwood2121 said:
Well completely wiped and reset up after about 15 with Bluetooth on it started again....any other suggestions
Click to expand...
Click to collapse
Try starting the phone in safe mode to rule out a conflicting app. If you can confirm it happens in safe mode -and- you have fastboot flashed a full factory image (not just factory reset) and the problem still persists you may have a hardware issue and now have done enough testing for an RMA.
Every thing was great until I connected my pixel buds ....i was playing music for over an hour on a Bluetooth speaker and no problems.....went to mow grass with pixel buds and not even 15 minutes Bluetooth and wifi force closing
Been back and forth with Google and sent in bug reports, they sent me an email asking for all kinds of phone info , my name , address, and such.....they haven't got back to me yet after I sent in that info....what does it usually mean .
They seem to think it is hardware related from the bug report. I've had the phone since November.
They gave me an option to have a replacement sent to me to swap but want to put a credit hold on a debit card. I've been screwed by Google before when I traded a brand new Galaxy s8 plus still in the factory plastic and not used. They told me I sent them an LG with a cracked screen and I was not given any credit towards my pixel 2xl...the trade towards my 3xl went smoothly but I took pics and a long video of it being boxed and mailed. Seems shady with the credit hold...anyone got any input. The only other option they gave me was to send it in for repair and would take 10 business days and I have no backup phone
vwood2121 said:
They gave me an option to have a replacement sent to me to swap but want to put a credit hold on a debit card. I've been screwed by Google before when I traded a brand new Galaxy s8 plus still in the factory plastic and not used. They told me I sent them an LG with a cracked screen and I was not given any credit towards my pixel 2xl...the trade towards my 3xl went smoothly but I took pics and a long video of it being boxed and mailed. Seems shady with the credit hold...anyone got any input. The only other option they gave me was to send it in for repair and would take 10 business days and I have no backup phone
Click to expand...
Click to collapse
A card hold is just that, nothing more. Many companies do it. It disappears as soon as your old phone is received. Wait for the new phone to come, use data transfer feature to setup your new phone, and then return the old one.
Anyone having this problem where call doesn't connect with error of 'Call not sent'? This is doesn't happen when connected to Wi-Fi but happens most of the time otherwise and I have to re-try 2 times (sometimes 10 times) to get the call connected. I have tried clearing data for phone app but it didn't help. I am not seeing any reports on it in any beta discussion so I am guessing its not a beta problem? It never happened before the beta update and I installed the beta update from total reset instead of just updating.
Yes. Only happens when I am on Bluetooth connected to my car. I gave to call from the phone app instead of my driver control.
"Call not sent" error on Samsung Note10
I'm having a similar issue with my Note10, just shows "Call not sent.", whether connected or not to Android Auto or any other dock/bluetooth, it doesn't seem to fix the problem.
I have tried several active sim cards from different carriers which work fine in other phones, but in the Note10 I can only access the web and text. When trying to make a call with full signal bars and LTE next to it, it just shows "Call not sent". I've done all the usual restart, full factory reset from the recovery menu, even reflashed it via Odin with the latest firmware (N970U1_UES2BTA1) three times, then factory reset again, but it's doing the same. It seems to be a hardware problem, not a software glitch.
By the way, my phone is unlocked and I have checked the IMEI to make sure it's not blacklisted. I have also examined the charging port for any liquid damage, but it's completely clean and shiny. When I dial the test code *#0011# to compare the network status screen against a Samsung S9's, I've noticed that the "MIPI TEST SUCCESS" and "ASDiv: PASS THROUGH" at the bottom of the screen are MISSING on the Note10, which might have something to do with the failed calls.
Also, out of curiosity I have installed a couple of different phone dialers (Google Phone and Simpler Dialer), but the outcome is the same "Call not sent.".
Evidently there's a hardware problem with the Note10 series (some or all), because Samsung's own forum full of similar complaints.:=(
Same problem. Getting call not sent
Was not issue in Android 9. Only Android 10.
Galaxy note 10+ unlocked version on tmobile.
I've also had other random Bluetooth issues.
this issue got so bad, i am not able to make calls, unless i make multiple attempts.
so i just upgraded to the S20 Ultra. Same issue!!
Here are other factors and connected devices.
Connected to a Ford vehicle (Sync; 2017 Explorer)
Connected to Samsung Active2 smartwatch (but issues remained even when watch disconnected).
I've also tried to unpair / re-pair. To no avail...
Help!
Also here:
https://us.community.samsung.com/t5...-Android-Auto-after-upgrading-to/td-p/1077007
I am really glad I blocked updates, I am still running on Pie
billa said:
I've noticed that the "MIPI TEST SUCCESS" and "ASDiv: PASS THROUGH" at the bottom of the screen are MISSING on the Note10, which might have something to do with the failed calls.
(
Click to expand...
Click to collapse
I have an Exynos Note 10+ I don't seem to have this problem and when I did the test you did I got "MIPI TEST SUCCESS" but nothing about ASDiv.
Could this be a problem with the Snapdragon chipset?
ultramag69 said:
I have an Exynos Note 10+ I don't seem to have this problem and when I did the test you did I got "MIPI TEST SUCCESS" but nothing about ASDiv.
Could this be a problem with the Snapdragon chipset?
Click to expand...
Click to collapse
It certainly could be, on all other phones I always see the "MIPI TEST SUCCESS" in test mode, but not on the N970U.
It might be fixed with a new update, unfortunately there's still nothing newer available than UES2BTA1 as of right now.
I have the feeling it's a hardware issue rather than software, in which case it's not going to be fixable, short of replacing the main board.
No idea, why this started happening mostly after the last update.
billa said:
It certainly could be, on all other phones I always see the "MIPI TEST SUCCESS" in test mode, but not on the N970U.
It might be fixed with a new update, unfortunately there's still nothing newer available than UES2BTA1 as of right now.
I have the feeling it's a hardware issue rather than software, in which case it's not going to be fixable, short of replacing the main board.
No idea, why this started happening mostly after the last update.
Click to expand...
Click to collapse
Are you able to rollback?
As long as the bootloader is the same you might be able to go back to an update prior to the problem.
Not 100% sure but I believe the 5th number from the right in the build number is the bootloader version. Just need to make sure it is the same and you might be able to fix...
Sorry if I'm rambling, working on 3 hours sleep...
ultramag69 said:
Are you able to rollback?
As long as the bootloader is the same you might be able to go back to an update prior to the problem.
Not 100% sure but I believe the 5th number from the right in the build number is the bootloader version. Just need to make sure it is the same and you might be able to fix...
Sorry if I'm rambling, working on 3 hours sleep...
Click to expand...
Click to collapse
Right, but usually same bootloader version updates are just maintenance or critical security updates only.
Looks like some major changes have happened in the latest update, which could be causing the no call issue.
Just checked, and it's still the same version available.
Version: N970U1UES2BTA1/N970U1OYM2BTA1/N970U1UES2BTA1/N970U1UES2BTA1
OS: Q(Android 10)
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
kingsfan33 said:
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
Click to expand...
Click to collapse
But it's happening for others with or without the Google Voice app installed.
You may have had a different issue.
Chiming in late to the game with a Samsung Galaxy S20. I never had this issue with the new OS on my S10 but it started happening with the S20. It's also intermittent. Sometimes it works. I have tried unpairing and repairing. I have tried deleting the bluetooth device and reconnecting it. All to no avail. At least other folks recognize this issue and hopefully Samsung issue an update soon.
i have regerts (spelled wrong to be funny)
winol said:
I am really glad I blocked updates, I am still running on Pie
Click to expand...
Click to collapse
As nice as this phone is--I am annoyed with myself that I upgraded to Android 10--everything worked so great with 9!!! I wish there was a way to go backwards. I might investigate that, actually. I have a little downtime as of late.
I finally updated to android 10, ui 2.0, and, luckly, all is working fine, only thing I notice is that battery seems to last a little bit less…
i have Android 10 ui 2.1 with infinity rom 6.0 rom N975FD and everything works perfect including goodlock 2020
winol said:
I finally updated to android 10, ui 2.0, and, luckly, all is working fine, only thing I notice is that battery seems to last a little bit less…
Click to expand...
Click to collapse
For me, Android 10, whether UI 2.0 or 2.1
battery.... standby, is exceptional good .!
I am a power user, eg theming etc
so i don't worry or have time to worry,
about SOT ETC....
For me what matters is when , my device is sleeping.....!
/ if anything
is draining my device battery etc.
( Ihave about 200./300 apps.)
Suggestion... factory reset or did you already done that.?
See examples of device overnight
standby etc.
kingsfan33 said:
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
Click to expand...
Click to collapse
THIS WAS THE FIX FOR ME! I'll have to research why Android 10 isn't playing nicely with Google Voice, but I'm glad I can hit call and it goes though, instead of hitting "send" over and over and over again!!!
S10+ Exynos, running Android 10 stock - same problem. Annoying as hell!
I can't uninstall GV because I use it for international calls.
Edit: BTW - it definitely seems to be affected by connected BT headset. As soon as I turn the BT headset off I am able to make the call (using MPOW headset, don't remember the exact model).
billa said:
But it's happening for others with or without the Google Voice app installed.
You may have had a different issue.
Click to expand...
Click to collapse
I have had this issue so many times on my S20+ unlocked. Swipe and touch to call just doesn't work. I saw this thread today when I had multiple call not sent instances. I force stopped Google voice and the problem disappeared. If I have to make an international call, I just to start Google Voice.
dhebi111 said:
I have had this issue so many times on my S20+ unlocked. Swipe and touch to call just doesn't work. I saw this thread today when I had multiple call not sent instances. I force stopped Google voice and the problem disappeared. If I have to make an international call, I just to start Google Voice.
Click to expand...
Click to collapse
Are you (were you at the time) connected to a BT headseat? It happens to me only when my headset is connected, and not just one - two different types of headseats and also happened once or twice when the phone was BT connected to my car. As soon as I disconnect the BT, all calls can be completed without a problem.
I need help identifying what app or setting got me into this mess.
I think the hacker has adb access.
He shuts down apps.. etc
He is messing with the notifications.. i get ony a few. Sometimes they come in late.
I have made reset from samsung setting and the boot menu, AND I INSTALLED A NEW ROM (the one for my phone) WITH ODIN. Still the issue resurfaces.
I think my roomate installed smthg in it. He is on the house wifi and he is got a degree in networking (i think thats what it's called, we study in french in my country)
Please i need help.
If someone needs any further details, please ask.
Avoid the wifi network you suspect your hacker friend is on, reinstall the rom downloaded on another network and stay on 4G and see if it still happens? Also suspect your PC to be hacked...
Thx for replying,
I did format my pc but i have connected it to house wifi.. didn't notice anything out of order though.
I found out about the "Revoke USB debugging authorisations" option in Developer Options. I think it is working.
Today, since i made a new instagram account, i added a mutual friend. Turns out it was an old and lost account, and thats when i got the error from the video.
Fortunately, i fixed it by un.following the account and clearing the app storage.
I need to know what access does he have?
Can't upload the video, here's some shots.
Look no further than yourself for the cause of this... one way or another.
RX: Factory reset, change Google account password.
Stop with the social media crap and go mingle with real people.
This not about social media, it's about getting my phone back.
With my old account, I couldn't even talk to my messenger friend. Today, thats like having your phone number unreachable all the time, frustrating.
Please if you don't want to help don't, but no need for quick unhelpful replies.
Carch921 said:
This not about social media, it's about getting my phone back.
With my old account, I couldn't even talk to my messenger friend. Today, thats like having your phone number unreachable all the time, frustrating.
Please if you don't want to help don't, but no need for quick unhelpful replies.
Click to expand...
Click to collapse
How was it compromised?
Understand if it was compromised it's more than likely because you left yourself vulnerable to attack.
A compromised OS needs to be cleaned or wiped... I gave you the solution(s).
No need to say thanks but don't give me lip about your screw ups.
Thank you.
I tried factory reset more than 10 times, different ways. No luck.
I think he is got access to one of my friends account but i don't know how he is using this connection with me ( message, notification.. i don't know)
@blackhawk what you said is true, and i didn't mean no offense.
Carch921 said:
Thank you.
I tried factory reset more than 10 times, different ways. No luck.
I think he is got access to one of my friends account but i don't know how he is using this connection with me ( message, notification.. i don't know)
@blackhawk what you said is true, and i didn't mean no offense.
Click to expand...
Click to collapse
Reflash the firmware especially if it is Oreo or below.
If it's not embedded in the firmware, it's being added by you albeit inadvertently.
Your Achilles heel is social media... don't be so predictable. Break the link in the chain.
None of the social apps should be running on the device, they are malware. At least keep them in the cloud.
Email must always be kept in the cloud and any attachments downloaded from it scruntinized or preferably not downloaded at all. All downloads are suspect.
At this point your data base is suspect as well.
Insanity is doing the same thing over and over, expecting a different result.
Android 11.
I am trying.
Carch921 said:
Android 11.
I am trying.
Click to expand...
Click to collapse
Unless someone physically got their hands on it, there's no known way the Android 11 stock factory image can be compromised by a rootkit or virus. A factory reset is all that is needed.
The problem happened after the reset.
blackhawk said:
Unless someone physically got their hands on it, there's no known way the Android 11 stock factory image can be compromised by a rootkit or virus. A factory reset is all that is needed.
The problem happened after the reset.
Click to expand...
Click to collapse
That is exactly what i suspect did happen. I often leave my phone home and my pattern is known for him.
How can i undo a modification of that level.
(I intend to go to a phone repair shop and install new soft with the "box". Is this recommended or is it a bad idea)
Carch921 said:
That is exactly what i suspect did happen. I often leave my phone home and my pattern is known for him.
How can i undo a modification of that level.
(I intend to go to a phone repair shop and install new soft with the "box". Is this recommended or is it a bad idea)
Click to expand...
Click to collapse
Never leave a phone physically unsecured as that's the only real security there is.
You need to have the firmware reflashed then be careful what you put back on it.
Change all your passwords and use secure passwords.
I ithink i this is the problem.( in the pic below)
There was an app called android device.. don't know if this is normal. So i deleted it and restarted and things are back to normal.
Sorry i can't upload the image, the app closes automatically.
Scan it online with Virustotal.
Sell the phone Facebook