I have a constant reoccurring problem where the mic stops working. At first, I thought it was a hardware problem, but every time it has happened, it has been temporarily remedied by a reboot. After rebooting, it works fine, but then it will stop working again at an unexpected time. It is clear to me that this is a software issue. This makes taking calls and using Assistant virtually impossible.
I was planning on flashing a custom ROM on the device to see if it fixes the issue, but I found out that I have the Verizon boot-loader locked model. I did go onto Google's developer site and flashed the latest OTA but to no avail.
I need help. I have seen not a single other person with the same problem as me. This makes the phone completely useless AS A PHONE. I have been recently using a Galaxy Note 8 as a replacement, but TouchWiz doesn't cut it for me, as well as being a version behind.
It is a hardware issue, all pixels made before 02/2017 might develop that issue.
Related
So I've had a VZW Nexus for about 5 months, flashed all kinds of custom ICS stuff on it, never had problems.
When Jelly Bean ROMs come out I flash one built from AOSP, works great, after a while an updated version of the ROM hits Goo.IM, I dirty flash+GApps, and suddenly after a few days my phone seems to be stuck in headset mode, not allowing me to use the mic or make calls without using speakerphone mode.
Do full system wipe, factory reset of radios/system/bootloader back to IMM76K, the issue is still there at first boot, hmm, must not be a software issue then.
I Google, this seems like a known hardware issue with the headphone jack, get a replacement from Verizon, it works fine, no problem.
Until I flash an AOSP JB ROM on this working phone, then, just like before, after dirty flashing a JB AOSP ROM upgrade, a day or so later I get the exact same issue, and again full wipes/factory resets don't fix it.
Verizon sends me a new one. This time, I'm staying on IMM76K.
This seems fishy to me, the odds of getting this kind of hardware failure on two different phones after the same sequence of events and there being no relation is astronomically high.
Again, not running any OC's or anything weird. Never dropped the phone. Don't use it in humid environments. Don't even use actual headsets. Used the first phone for months with no issues. Tried SIM/battery pulls. The AOSP JB ROM in question is used by many without this issue, though I have found what seems to be a few more instances of this that have happened after JB upgrades via Google.
Any explanations? Is there a weird bug in AOSP that's frying stuff? Doesn't seem likely or even possible, but then why?
Well before deciding to root, my phone was freezing when making a call. Sometimes the system would allow a conversation, then all of a sudden I would get a ringing sound followed by frozen software, I read, researched and tried not to bug any of you. I found possible issue with the proximity and light sensor. Also read on a reputable Android website, that Sprint had follied some of the PRLs OTA. So I decided to change the possible hardware flaws and Root. Low and behold it resolved the ringing that followed the freezing, but not the freezing. Was going good with Wicked Sensation 5.0, but could not stand the constant update request. That beloved Rom eventually did the same. So changed to 5 different roms and went from TWRP to Phils recovery since then. I am currently on Static 4.3, all roms worked great until I sent/recieved a call. As soon as I hit talk phone freezes and all audio ceases to function. Sometimes itll tease me after a dalvik wipe, but always after hitting "Talk," everything regarding S3 audio or sound, stops functioning.
Does anybody know about the issue I am describing? I switched the audio components so can this Handset Issue MB related? It is hard for me to rule out software due to the audio coming back after each newly installed rom. Before its demise, Audio sounds great. The audio disappears after a call. Just concerned about going to a Sprint repair center for the wait. If this is software related it highly likely my issues will come back. Not a pro, but well versed in the rooting process. As a ExSprint employee I went through all of Sam's rooted and never been stumped on a "Hardware vs Software" problem like this. If I find out its Knox Im taking a Google Nexus to record me throwin my S3 on the wall and sending it to Samsung....jk lol. (For reals though, the increasing challenges to root for every update pisses me off cause the Samsung always got better hardware then the others, but WTF Sammy?)
These are the two setups I have used thus far (besides full stock), and this issue has occurred on both:
http://imgur.com/EgzxWFI
http://imgur.com/FZWrdwZ
The first is on ktoonsez kernel on stock rom. The second is Slimroms Kitkat. I have been using the first much longer than the second (which I moved over to just a few weeks ago).
Basically this soft reset tends to happen when I'm driving and using the GPS most often (and I notice that's also when the phone is usually the warmest). What happens is the phone just freezes up and sits there for a bit before finally doing a vibration and starting back up to the unlock screen. Kind of like I was restarting, but not quite. If it happened in the middle of calls, somehow it would keep the call going (at least on the stock kernel, I'm not sure about the new one yet). The other person just wouldn't hear what I was saying during the "soft reset"
On the stock kernel it used to happen even when not using the GPS. It was infrequent, but occurred I would say usually when I was using the phone more heavily... mostly just random though. Sometimes it would also not happen while using the GPS. That is to say it's a sporadic issue.
On this new Kitkat kernel it happened while I was navigating recently, but has not occurred when during any other operations (yet) that I can think of. Considering that was one of the first times I tried navigating with the kernel this worries me.
Does anyone know how I could approach this problem? Perhaps some logging I could do to get to the root issue? Some firmware I should perhaps try out?
Thanks.
Sounds hardware related to me. Especially if its happening on different roms.
Then again... I just looked at you image and you are still running 4.0.4 on one. But the other you are running 4.4.4. On one or tge other you most likely have a rather large gap between your firmware build and the rom. Id try flashing full stock firmware with Odin and test for a day or two. Up to you what build you want to use, but if it were me id update to 4.3. If you go to 4.3, keep in mind there is no going back.
I'm running stock rooted 5.0 on the ASUS_Z008D model of the zenphone 2.
This was originally my girlfriends phone, and she used it about 2 months before I started using it. At the end of those months before I took it, the camera completely stopped working. I looked up the few ways to fix it on google but none of the fixes I found worked. I think it's a hardware problem, but I have no idea truthfully. It always says it's running under another app. I have tried disabling and reenabling it, but nope. Nothing.
That isn't as important as the updates caused. I'm stock rooted, but I've had no problems at all updating the OTA updates ASUS sent out. After the latest one a few weeks ago, the phone finally started having problems that annoy me. Often at times, I send or get sent messages from other people, but the phone never receives or sends them. I've tested this using my siblings or freinds' phones right next to me, textng myself, and I never receive them at all. No delays, just never receive them.
Next, the update caused the phone to have a bunch of random reboots, and constant signal deaths. The phone will constantly completely lose signal, and take a few seconds, maybe a minute or two to reconnect. This usually comes with one to three reboots everyday.
Anyone else experience this or am I alone here? I'm thankful for this phone being awesome for budget price, and the fact it's not mine. (I'll be upgrading to the N 5X on release) But I still wanna know if I can fix this phone to save as a backup.
Taco_Human said:
I'm running stock rooted 5.0 on the ASUS_Z008D model of the zenphone 2.
This was originally my girlfriends phone, and she used it about 2 months before I started using it. At the end of those months before I took it, the camera completely stopped working. I looked up the few ways to fix it on google but none of the fixes I found worked. I think it's a hardware problem, but I have no idea truthfully. It always says it's running under another app. I have tried disabling and reenabling it, but nope. Nothing.
That isn't as important as the updates caused. I'm stock rooted, but I've had no problems at all updating the OTA updates ASUS sent out. After the latest one a few weeks ago, the phone finally started having problems that annoy me. Often at times, I send or get sent messages from other people, but the phone never receives or sends them. I've tested this using my siblings or freinds' phones right next to me, textng myself, and I never receive them at all. No delays, just never receive them.
Next, the update caused the phone to have a bunch of random reboots, and constant signal deaths. The phone will constantly completely lose signal, and take a few seconds, maybe a minute or two to reconnect. This usually comes with one to three reboots everyday.
Anyone else experience this or am I alone here? I'm thankful for this phone being awesome for budget price, and the fact it's not mine. (I'll be upgrading to the N 5X on release) But I still wanna know if I can fix this phone to save as a backup.
Click to expand...
Click to collapse
Mate, if there is a problem, unroot the phone and RMA it with the warranty... That warranty is there for a reason...
Nexus 5X 32GB - stock Android 7.1.2
Fact 1: The device presented the usual bootloop issue a couple months ago. I sent it to LG support for repair, where they replaced the entire PCB. For about a week after the repair the device behaved normally, then the freezing issue started.
Fact 2: After some factory resets and experimentation with installing/uninstalling apps I suspected might cause the issue, I unlocked the bootloader, flashed the latest stock Android 7.1.2 image (wiped user data/cache etc.), relocked the bootloader and kept using it normally.
Fact 3: A few days later from the flashing, the freezing issue came back.
Behavior: What happens is that the device randomly freezes when interacting with it (be it texting on a messaging app, scrolling through Chrome, expanding the notification bar etc.). When this happens, most of the times the device will stay frozen for a couple of minutes and then take me back to the lockscreen where I need to enter my PIN again to unlock it. Sometimes it will just reboot. And less frequently, it will give me an error message that "Google App has crashed". All of the times, when the device remains frozen, the back of the phone will get hot (but not extremely hot).
As you understand, I haven't yet managed to find the root cause of this issue, whether software or hardware induced. Nevertheless, the phone is rendered unusable that way and I want to investigate my options.
Any ideas? Your help is much appreciated.
I would see if your are still covered under the warranty and get it replaced with a unit that doesn't have the hardware issue.
Sent from my Nexus 5X using Tapatalk
I'm noticing similar behaviors on mine too. I have the latest Android 6 room installed instead of 7.
It started happening about 2 weeks ago. Was there an update on Google apps or the core platform recently that could be affecting the ROMs?
I have exactly the same problem! Except I haven't flashed anything. Mine has been stock all the time. So I don't think it is because of flashing.
They also replaced my phone's motherboard after bootloop. And now I have this random freezing at least once a day. Also I haven't been rooted or unlocked bootloader.
Mine is still under warranty.
Does anyone have an update?
I also saw this start happening on a stock 5x with no bootloop issues and no replacement hardware, roughly mid-May. Usually multiple freezes per day. Have not observed freezing for the last 5 days or so, though -- operating like normal again.
Just an update: Lately the issue happens a lot less frequently, but it's still there.
I suspect it has nothing to do with the ubiquitous bootloop issue (as mine has been repaired before the freezing issue appears, while @biff-torkington experiences freezes without having the bootloop issue).
Still no idea what can be done to remedy this situation.
No freezing at all in my 16 month old bullhead currently on stock rooted 7.1.2 with phasma kernel, no previous bootloops or hardware repair. I have never updated ota however and have run a custom ROM the majority of the time since I've had it, no idea if that would make a difference or not
The answer is simple:
2GB Ram + badly written ram hungry apps like messenger.
Best solution is to get another phone.Oh well...