My daughter was all excited today to get the Android 12 update on her 4a 5G. Once she installed it, the speakers all quit working. No sound from the phone at all, and I've check every single setting. When you make OR receive a phone call, it is stuck on speaker phone, but the no sound comes out of the speaker. The speaker phone button stays lit up and you can't turn it off.
We have rebooted it and I finally did a full factory reset, and the problem persists. I didn't reinstall any apps. Didn't even add her account. Just a clean FDR and reboot and still now sound.
Tried to flash back to Android 11, but the bootloader is locked, and it the OEM Unlock button is greyed out, and says its not available on carrier-locked phones. This is from T-Mobile, and Its financed, so I doubt they will unlock the device, so I won't be able to unlock the bootloader. I feel very stuck right now.
I've been flashing Nexus, Pixel, and Samsung for years now, going back to the original Moto DROID, adn I can NOT figure out how to fix this. I'm guessing I'm going to have to get a replacement from T-Mo.
Just had issues myself with a locked bootloader. Call a representative and describe the issue. They unlocked my pixel after saying I was using development tools.
Just solved this issue, I didn't have app auto updates on, there was an update waiting for Speech Services from Google. Once that had been installed (there might have been 2 separate updates) microphone and speakers started working instantly again.
D
Related
My last phone was a OnePlus and it was/is a great phone, however I like the Nexus line and the pure android experience. I thought I would try the N6 and see what I thought. I was not able to find it on Motorola or Google, so being I have a bunch of upgrades figured I would grab a ATT one, de-ATT it and done.
So I boot unlocked, rooted , TWRP and got rid of any ATT taint. But something was calling me back to the OPO. So, day 14 of the 14 day return policy comes and I put in a return. I cleaned up the phone, re-installed stock, unrooted and last locked my bootloader. However, and I would reboot and check after each step, when I re-locked the bootloader, it would go to status = 2, say its locked, but would basically boot-loop no matter how many times or what I did. I would unlock and it worked just fine. I tried everything and nothing worked. If anything, it would flash to the Google screen 2x then hit the recovery (android with the blue star belly). I could power/up-volumn and it would show clear data sometimes, but still nothing.
Any ideas why? Is there any way to change that status 2, which I think shows it was unlocked once, to just 0 or 1? Think this had anything at all to do with ATT?
And just FYI, I cancelled the return and love my N6. I didn't realize how attached I grew to the real estate.
The title speaks for it self.
At the time of the original problem I was using...
OS: Android N Preview 5 (stock, rooted)
kernel: Elementalx 4.07 (default settings)
My N6 is about a year and a half old. It all started when I was punching an address in to google maps, and the screen goes dark out of the blue. No back light, nothing. Through process of elimination I am able to tell that the phone works, but the screen doesn't. Later on I'm in a phone conversation (was able to call using moto 360) and once the call is disconnected, the screen powers back up. Now everything is fine and dandy for about another week. The other day I am browsing and again out of no where the screen goes dark.
Failed troubleshooting attempts include:
Blindly rebooting into recovery and wiping cache/dalvik
Blindly rebooting into bootloader and re-flashing boot.img
Blindly doing a hard factory reset
Blindly re-flashing 6.0.1 (mob30w) and Elementalx 4.07
Disassembling phone and verifying connections on display assembly
I'm 90% sure I was able to correctly execute all the failed attempts above with a non-working screen - albeit it was not easy.
Any how, I'm still stuck. Someone help me
I have Project Fi so I almost NEED a nexus device. I ordered a 5x, but I'd hopefully like to return my N6 to it's working condition so I can return the 5x to the factory. I really wanted to use that money for one of the new nexuses (nexi?) when they come out in a month or so.
The one thing I stupidly didn't do was call motorola (whom I purchased the phone through) before dis-assembling the phone and I imagine voiding any sort of warranty claim I could take.
nioletmc said:
The title speaks for it self.
At the time of the original problem I was using...
OS: Android N Preview 5 (stock, rooted)
kernel: Elementalx 4.07 (default settings)
My N6 is about a year and a half old. It all started when I was punching an address in to google maps, and the screen goes dark out of the blue. No back light, nothing. Through process of elimination I am able to tell that the phone works, but the screen doesn't. Later on I'm in a phone conversation (was able to call using moto 360) and once the call is disconnected, the screen powers back up. Now everything is fine and dandy for about another week. The other day I am browsing and again out of no where the screen goes dark.
Failed troubleshooting attempts include:
Blindly rebooting into recovery and wiping cache/dalvik
Blindly rebooting into bootloader and re-flashing boot.img
Blindly doing a hard factory reset
Blindly re-flashing 6.0.1 (mob30w) and Elementalx 4.07
Disassembling phone and verifying connections on display assembly
I'm 90% sure I was able to correctly execute all the failed attempts above with a non-working screen - albeit it was not easy.
Any how, I'm still stuck. Someone help me
I have Project Fi so I almost NEED a nexus device. I ordered a 5x, but I'd hopefully like to return my N6 to it's working condition so I can return the 5x to the factory. I really wanted to use that money for one of the new nexuses (nexi?) when they come out in a month or so.
The one thing I stupidly didn't do was call motorola (whom I purchased the phone through) before dis-assembling the phone and I imagine voiding any sort of warranty claim I could take.
Click to expand...
Click to collapse
I have had the same problem quite a few times. I thought it was the layers that i had installed. I eventually had to reboot to recovery, clear cache and dalvik. Then the phone booted in to Android with screen active. I have now disabled my lock screen pattern. Hopefully that stops it.
This problem started on her unrooted Amazon Prime version. What I did was I went ahead and unlocked the bootloader and installed the 7.4.2 OTA without ads as well as rooting it. That actually worked for a few days, but whenever she gets a phone call, the ringing started to be mute once again. She has claimed that she's tried restarting it, but to no avail did this work. How do I fix this infuriating software bug?
DragonfireEX402 said:
This problem started on her unrooted Amazon Prime version. What I did was I went ahead and unlocked the bootloader and installed the 7.4.2 OTA without ads as well as rooting it. That actually worked for a few days, but whenever she gets a phone call, the ringing started to be mute once again. She has claimed that she's tried restarting it, but to no avail did this work. How do I fix this infuriating software bug?
Click to expand...
Click to collapse
Did you try changing changing the ringtone. Blu usually is fussy when it come to ringtones,. Just reset phone and stick to default ringtone for while to see if it helps
At the time we had tried this, it did not resolve the issue at all.
Hi,
I have started to get this weired issue after the 8.1 update.
Whenever I receive a call, after picking up the speaker phone turns on automatically. I have to manually turn off the speakerphone, also it does not indicate that the speakerphone is turned on.
shashankkp12 said:
Hi,
I have started to get this weired issue after the 8.1 update.
Whenever I receive a call, after picking up the speaker phone turns on automatically. I have to manually turn off the speakerphone, also it does not indicate that the speakerphone is turned on.
Click to expand...
Click to collapse
Solution is mostly the same for all of the problems.
Do full factory reset.
Setup Google account
Don't install any apps just yet.
Try if problem still exists
In most cases this will help.
What I've learned since my first android device, all of the custom ROMs etc, is that the updates are causing loads of problems.
Once in a while, especially after version upgrade, is worth doing full reset just after updating.
This doesn't apply not only to android, but pretty much every single device on the market.
TeddyBeers said:
Solution is mostly the same for all of the problems.
Do full factory reset.
Setup Google account
Don't install any apps just yet.
Try if problem still exists
In most cases this will help.
What I've learned since my first android device, all of the custom ROMs etc, is that the updates are causing loads of problems.
Once in a while, especially after version upgrade, is worth doing full reset just after updating.
This doesn't apply not only to android, but pretty much every single device on the market.
Click to expand...
Click to collapse
Thanks for the suggestion, But by full factory reset do you mean the hard reset from the recovery menu or just the factory reset from settings menu -> factory reset..?
facing same issue please help
i am facign the same issue please help me out
Still no solution for the problem...I have made an habit to turn speaker phone on and off immediately after calling .
Try Macrodroid app to set an automatic task, to turn speaker off 1 or to seconds after receiving call.
I am also facing Same issue, can any one give suggestions
Somehow that happened to me when I just got the phone a few months ago. I think that was still on 8.0.
But tapping the speaker phone button 2 times everytime I have a call became nature for me and eventually after a few days, I no longer have that issue.
Are you still having that speaker phone issue now?
Yes...but while it was consistent on 8.0 it has become a random occurrence after 8.1 update
same issue
factory reset solution is not acceptable.
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
Click to expand...
Click to collapse
I would try flashing the latest factory image via fastboot.
[Guide] Root Pixel 4 XL with Magisk Android 13
[Guide] Root Pixel 4 XL With Magisk Android 13 Android Security Bulletin—Feburary 2023 Pixel Update Bulletin—Feburary 2023 Introduction This Guide is for Pixel 4 XL owners that want to Root their phone, and enjoy the benefits of rooting it. The...
forum.xda-developers.com
https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/ (This is for a Pixel 2 XL but the process is the same. It's basically a condensed version of the one above.)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Click to expand...
Click to collapse
You did not provide the most important information we need- whether your phone is bootloader unlocked. Probably not, otherwise you would have already flashed it with a full Google image, which returns the phone to "out of the box" condition. You need to determine whether you can unlock your bootloader. If you cannot unlock (allow oem unlock is off and or greyed out in Dev options) then you will not be able to fastboot flash ANYTHING. If that is your case, the next best thing is flashing a full OTA image (sometimes called a rescue OTA) from recovery mode using the OTA via ADB option. This means you need fastboot/adb installed and working on your PC. Instructions on how are on the same Google dev page for OTA's.
So, my phone's bootloader is not unlocked. But I have an update for the crowd that may one day find this. I know your frustration and I can report that my phone is once again fixed.
A day (or two) after I sent this, a set of updates came down to my phone. And WebView was updated. That restored all of my sensors and also restored most of my crashing applications. It was an incredibly odd experience.
My phone once again functions. And the nightmare of owning a Google phone and talking to Google support has ended.