My Moto X 2014 XT1097 wont play any sound coming from calls and videos (youtube/viral) it doesn’t even play sound from recorded videos.
But notifications, volume changes and built in ringtones are played without any problem.
The sound stopped to work as soon I unlocked the phone via "fastboot oem unlock". I have done 3 factory reset with no luck yet. Any idea?
Lollipop btw
I've ran across this issue with my Moto X 2013 and my Moto X 2014. I fixed the issue by using an app called Root Cleaner. It cleans useless file, cache, clears memory, restarts the UI, and fixes permissions. Unfortunately it is a paid app, but is worth it. You will need to be rooted to use it.
Related
I ordered a Moto X for my 93 year old father. This will be his first smartphone. He currently has an old flip phone, and it is getting too hard from him to see the tiny screen. So I have been trying the demo of Big Launcher on my moto x, and I think it will work perfectly for him. Everything thing on the screen is HUGE. But there is a bug with text messages on 4.4, that they stated is not present on 4.2.2.
So, I am hoping the phone we ordered from Amazon comes with 4.2.2, and I just won't install the 4.4 update until Big Launcher is fixed. Question is, I seem to recall the 4.3 update on my GS4 popping up from time to time, which was annoying, because I did not want to install it at the time.
Will the moto x do the same thing? I installed it on my Moto X the first time I got the notification so I don't what the behavior will be, and I would rather he not keep getting the popup on his screen if it can be avoided. If so, is there a way to keep the popup notifications from happening? Thanks all.
I believe if you go to Settings->Apps->All->Updater and just disable it, you'll never have that problem. I haven't tested this, but it should do the trick.
Sent from my XT1060
Hi all!
I've had a problem with my Motorola Moto G 16gb XT1032 ever since talkback was mysteriously activated.
What happened was is that I got a black screen for less than a second before talkback came on, not knowing then how to disable talkback I did a factory reset to discover it hadn't got rid of talkback.
However I have since been able to correctly disable talkback, but I have found myself with a different problem.
My Moto G XT1032 now randomly reboots itself and some times takes an age doing so going through a mini bootloop.
I've had this Moto G from new, and this phone has never been rooted.
Any ideas on what to do as I'm just about ready to launch this phone??
Househeadrory said:
Hi all!
I've had a problem with my Motorola Moto G 16gb XT1032 ever since talkback was mysteriously activated.
What happened was is that I got a black screen for less than a second before talkback came on, not knowing then how to disable talkback I did a factory reset to discover it hadn't got rid of talkback.
However I have since been able to correctly disable talkback, but I have found myself with a different problem.
My Moto G XT1032 now randomly reboots itself and some times takes an age doing so going through a mini bootloop.
I've had this Moto G from new, and this phone has never been rooted.
Any ideas on what to do as I'm just about ready to launch this phone??
Click to expand...
Click to collapse
Wrong place bro,check Moto G - http://forum.xda-developers.com/moto-g thread this is Moto G(2014)
Quick background, I took the official lollipop update on the 2014 moto x pure edition, performed a factory reset to make sure i would have any fc
question:
ever since the update, whenever i select a a ringtone, the volume starts off really low the first time, and then gets louder. anybody else having this issue?
update: looks like when the phone rings, the ringtone volume starts of low, and then ramps up. is this a setting that i can turn off? or is it a bug? or a feature?
i'm experiencing the same behavior, however, it was happening on my device with KK as well. been exploring for an increasing ringtone option but haven't found it. also trying to figure out why i'm not seeing heads-up notifications for new email, text msgs, etc.
Basically it is a "feature" I believe, Samsung S3 had the same thing. There maybe an app available to change this or if you are rooted there might be a way to change the setting via exposed (although I don't know if it has been updated yet for lollipop or possibly look at the build.prop file though if you don't know what your doing with that, I wouldn't touch it as you can foobar your phone messing around with it.... If it was me, I would post it in the dev thread and see if one of the dev's have the answer. Or check Google, in the short search I did, apparently Moto G 2013 had this "feature" also.....
^^^ahhhh.... the 'ole "undocumented feature" (that's not a bug)...
if the rest of you are experiencing it, then i guess its a feature.... i guess i wanted to see if i set something up incorrectly or it was indeed a feature... .
It does this on kk. Didn't you notice it then?
bmwh0r3 said:
It does this on kk. Didn't you notice it then?
Click to expand...
Click to collapse
I don't recall this on kk. I'm sure that this was not happening in kk for me.
Definitely doesn't / didn't do it on kit Kat for me either. Does it now though..
A few days ago, I started having an issue with my Moto X's audio. I noticed after waking up my alarm hadn't gone off. After that, I realized that my phone wouldn't play any audio at all, through the speaker or headphones. However, I'm not entirely sure whether this is a software or hardware problem. When I attempt to play any video or audio I tend to get a general error from the app I'm using. For example, trying to play a song through Play Music results in a "Couldn't play the stream you requested." error. Attempting to play a Youtube video through the app gives me "There was a problem while playing." error. Trying to play a video through Chrome will actually make Chrome close. So, my audio problem doesn't seem to just be a speaker problem, because if it were I would expect videos to play without a problem, there would simply be no sound, unless I'm misunderstanding how that would work. I'm also not sure whether or not it's hardware related, because, as I said, the issue occurs with both the speaker and when I plug in earbuds or headphones.
I've already attempted some general solutions I had hoped would fix my problem. I've checked the sound setting and ensured the three volume sliders are set correctly. The next thing I tried was the general turn it off, and on again approach. I've also cleared the cache (multiple times), and even resorted to a factory reset, none of which has helped. I also uninstalled any recently installed apps, just in case. The fact that a factory reset did not help makes me assume it has to be a hardware problem. However, I'm not certain, because of the aforementioned errors I get from apps, as opposed to the behavior I would expect if there was a problem with the speaker. Again, please correct me if this is, in fact, what a speaker problem would be like.
Note: I'm running stock 4.4.4 Android and the phone was indeed bought used. I had a problem with my old phone and was not eligible for an upgrade yet, so I bought this phone. I got the phone about a week ago and, until yesterday, it worked perfectly. Unfortunately, I'm still not able to get an upgrade so that's not an option.
I'd really appreciate any guidance with this problem. Unfortunately, after the factory reset, I kind of ran out of things to try to hopefully fix it. Also, I apologize if this post has any formatting issues. This is the first time I've posted. If there's anything I could have done to make my question more clear, please alert me to it.
Tl;dr No audio from stock Moto X running current update. Apps give error or close when attempting to play video or audio. Already tried clearing cache partition and factory reset with no results.
I'm using a stock, rooted, manually debloated 5.1 system image that has incorporated some audio mods. Every once in a while, I'll notice that after waking my phone up, I'll get a redraw. I'm using the stock launcher. Here's what I've tried to get rid of them:
1. Just about everything you can think of involving the Google App (clear data, clear cache, uninstall and reinstall, etc.)
2. Switching to the Google Now launcher and back again.
3. Booting into safe mode and back again.
4. Reverting to the rom that doesn't have the audio mods that I implemented (at least I think I implemented them. I'm not sure how or if I can tell the difference).
5. Clearing cache from recovery about a million times.
Has anyone run into this problem and solved it?
The same behavior occurs on the Moto Maxx with 5.0.2. I was really hoping that it would have been fixed in 5.1.x.
I just flashed 5.1 the other day (using CF's image). I do get frequent redraws of the home screen and icons. I just installed Nova launcher thinking it was an issue with GNL.
I am seeing this on my Turbo since going to the OTA 5.1. with Nova. I don't seem to see it with Action Launcher 3 on the Turbo though. I also see it on my Nexus 7 2013 with 5.1.1 with Nova. Again I don't seem to see it with Action Launcher 3 on the Nexus.
I've noticed that it happens less and less frequently the longer I've been running this rom. Maybe it's just an android thing.
I did notice one thing.... I have turned off the google search bar that shows at the top of each screen by default. However every time I unlock the screen, it flashes the Google search box momentarily, then it disappears.
Also during phone calls, sometimes the bottom right part of the screen will flicker
I turned off Moto Display and the issue is completely gone. But I'm so used to unlocking my phone without having to use the power button that I really want it back
It is a Moto Display issue for sure. I have been experimenting lately and have discovered if I use only swipe for locking that once in a while when unlocking the phone I will have to do the android unlock after the Moto Display unlock. If I use smart lock associated with my Moto 360 watch those same times I'd get the second unlock I get a home screen redraw instead.
So come on Motorola - fix the problem! It is not just the Turbo/Maxx that has the problem. It is the Moto X etc as well.