Hello all,
For some time now I have been having issues with the phone.
Exhibit A) When using e.g. facebook messenger app it will freeze randomly for random amount of time, in some cases if I try to reboot the phone (hold power button for few seconds) the screen would just go blank and wouldn't turn on again, after several seconds in this case phone will reboot by itself. This can happen up to several times a day and is a really tough annoyance to handle. I have tried clearing the cache - situation got better, however issue still persists from time to time. Random "in pocket" reboots also do happen.
Exhibit B) When casting my screen the general video will get laggy and pixelated on movement, audio would break up as well. Tried this with several devices (nVidia SHIELD TV, Panasonic TV, BMW G30)
Phone is completely stock and up to date (OOS 4.1.3)
Any suggestions fellow forum members?
Cheers,
Greq
Is there a solution to this problem? Happens to my wife and me.
Actually, uninstalling Facebook messenger fixed the issue - I switched to messenger lite and device hangs no more
However miracast is still an issue
Related
I'm noticing Chromecast is freezing and crashing quite often. Seems to happen at random, sometimes it freezes with a series of lines on the screen, sometimes it's just black. It has happened with both YouTube and Netflix casting. Two days ago I had to power cycle it to reboot and it kept freezing at the small Chromecast logo. After doing a factory reset everything seemed good until a short time later when the freezing happened again (but it would at least boot up properly).
This didn't happen at first mind you, this has only been since Chromecast auto-updated to a new version(s).
I'm on build 12940.
Anybody else noticing this or similar issues?
Has anyone else noticed problems with CM crashing on their Atrix HD? I have been running CM on mine since September and have noticed the same problems in both CM 10.2 (epinter) and CM 11 (official). I never noticed any problems with the stock software. I have identified at least two different types of crashes.
Type 1 typically happens overnight when plugged into a charger (though less so with more recent builds) or when the phone is idle in my pocket. There is no notice the phone has crashed though sometimes if it happens in my pocket the phone seems to warm up somewhat. When I pull out the phone and press the power button I get nothing at all. This requires holding down the power and volume buttons for an extended period to force the phone off and then restarting it.
Type 2 typically happens when on an active phone call, though it can happen other times when using the phone as well. This involves the phone crashing and immediately going into a reboot (red M on the display as soon as I pull the phone away from my head).
I also have a less serious issue where when I press the power button to turn on the screen it will occasionally display the lock screen but refuse to take any touch input. I can usually get things to work by pressing the power button a few more times to turn the screen off and on again.
Just yesterday I switched to the new unified builds and have not seen all of these happen yet but I have definitely seen a type 2 already. Just wondering if these problems are widespread as I don't see them discussed a lot and if there's anything I can do about them.
Nothing? Am I really the only one having these problems? For the record I have now seen both types of crashes on the unified build.
May be you can try to flash stock rom:silly:
Try flashing the latest Validus ROM. I have been using version 4.3, which is based on KOT49H and it's been very stable with no crashes.
Is there a crash log that I can capture and review after a crash?
BenFranske said:
Is there a crash log that I can capture and review after a crash?
Click to expand...
Click to collapse
/proc/last_kmsg - kernel log from before the last reboot
/data/dontpanic/apanic_console - last kernel crash log
If the kernel crashed and the crash caused the last reboot, the content of both will be the same.
Regarding the non-responsive touchscreen after pulling the phone out of your pocket - it is usually caused by static electricity build-up. Subsequent turning off/on of the screen usually invokes ESD recovery procedure in the touchscreen circuit and the touchscreen starts to respond again.
It's very common on wide variety of phones (including e.g. iPhone). Change your trousers or use a belt case .
kabaldan said:
/proc/last_kmsg - kernel log from before the last reboot
/data/dontpanic/apanic_console - last kernel crash log
If the kernel crashed and the crash caused the last reboot, the content of both will be the same.
Click to expand...
Click to collapse
Great, I'll check those out the next time I have a crash. I am thinking there will almost certainly be some useful information for the second type of crash where the phone actually reboots itself. I am less optimistic that there will be any information when it simply locks up and I'm forced to reboot it by holding power and volume down buttons.
kabaldan said:
Regarding the non-responsive touchscreen after pulling the phone out of your pocket - it is usually caused by static electricity build-up. Subsequent turning off/on of the screen usually invokes ESD recovery procedure in the touchscreen circuit and the touchscreen starts to respond again.
It's very common on wide variety of phones (including e.g. iPhone). Change your trousers or use a belt case .
Click to expand...
Click to collapse
Thanks for the helpful information there too. My sister has forbidden me from wearing belt cases for at least the last 10 years but it's at least nice to understand what the problem is!
Crash Logs
Sorry it took me a while to get back to this. I've attached a few crash logs that I captured last month. I have updated the OS several times since then but I'm still experiencing both of the types of crashes I originally mentioned. Any assistance in interpreting the logs is appreciated!
Any ideas about what might be causing these crashes and reboots?
Am I really the only person with these issues? How can that be?
I have a pair of bluetooth earbuds that I use when I'm on the go, and ever since I got my new turbo, they have been constantly skipping and stuttering when I try to listen to music. It's totally ridiculous, the devices are only two feet away from each other, at most! Is anyone else having similar issues?
Rixanu said:
I have a pair of bluetooth earbuds that I use when I'm on the go, and ever since I got my new turbo, they have been constantly skipping and stuttering when I try to listen to music. It's totally ridiculous, the devices are only two feet away from each other, at most! Is anyone else having similar issues?
Click to expand...
Click to collapse
Nope. Mine is mint in the car with calls and music. Streams to a kitchen speaker perfect too.
civiksi said:
Nope. Mine is mint in the car with calls and music. Streams to a kitchen speaker perfect too.
Click to expand...
Click to collapse
Hmmm, I wonder if it's motion based. I'm sitting in my room listening to it now and it's a lot better. Unfortunately that doesn't really solve my problem, though.
Rixanu said:
Hmmm, I wonder if it's motion based. I'm sitting in my room listening to it now and it's a lot better. Unfortunately that doesn't really solve my problem, though.
Click to expand...
Click to collapse
Rixanu - I think you're on to something... I'll give my "story" and hopefully someone a little more savvy than us can help figure it out.
I switched over from the good ole Galaxy Nexus about a month ago. No major complaints on the Turbo yet as we await Lollipop, with the exception of this Bluetooth issue. I have the Bluetooth paired in the car, and a set of headphones - music and everything worked perfectly on the GNex through the Bluetooth. Now, primarily, it's often choppy (mustic anyway) - for reference, when listening to music I listen via Google Play (all access or whatever they call it now). I figured the choppiness was related to the fact that the music was being streamed since most wasn't downloaded yet, but after very limited experimenting, I believe it must have to do with the physical Bluetooth radio. I had noticed in the past that when the music streams perfectly, a lot of times if I pick it up to check an email, text, etc., it becomes choppy, but thought that was strange since the RAM should be more than sufficient to multitask without choppiness. On my way home from a friend's, I played around and stuck my hand over various parts of the back of the phone, and would press the phone against my pant, etc., and could effectively interfere completely with the connection such that it would be only silent, and not even choppy. Yet, while the music wasn't playing, the track continued to playback on the device and when the music would pick up after I moved the phone, it would be 10 seconds or whatever later as if it had been playing straight through the whole time.
I haven't tested this theory too much yet, but I think combined with your issue, there's certainly something there. Unfortunately, I frequent these parts in order to find answers to these types of issues and don't have the solutions myself.
Do we have lemons, or is this issue prevalent?
I'm happy to provide more info to anyone that can help.
Thanks in advance!
I was having the same problem. It was so bad Bluetooth was completely unusable. I contacted Motorola and they sent me the following steps to try. I worked perfectly. Good luck.
Dear Michael
Thank you for contact Motorola tech support, i send to you the steps you have to follow up to clear the cache for you Driod turbo
Before you do the Wipe cache, please un pair the Blue tooth devices and forget it for the phone, after you do that follow the steps and do the wipe cache.
This will remove any temporary files that may be causing the problem, but will not delete your files or settings.
1. With the phone powered off, press the VOL DOWN KEY for 2-3 seconds then POWER key then release.
2. The device will display different BOOT OPTIONS
3. Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select (I think he meant POWER to select)
Tip: If the device reboots, you may have waited to long to make a selection, you will need to begin the process again.
4. The device will display the Motorola logo and then the Android in distress ( logo with Exclamation mark)
5. Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key
Tip: You can try this step, holding the phone in landscape. If you are stuck on step 6, try a force reboot by pressing the Power key and Vol Down key, and start the process again.
6. The device will display additional menu options (Text will appear in BLUE)
7. Use the VOL DOWN Key to scroll to wipe cache partition and the POWER Key to select this option
8. The device will then perform the partition wipe
9. The device will reboot and start the normal power up sequence
Answer Title: Clear Cache Partition
Answer Link: https://motorola-global-en-usa.custhelp.com/app/answers/detail/a_id/102367
Thank you for choosing Motorola products
Regards.
Richard.
I think Bluetooth stinks. Poorly implemented, stupid pairing issues, and poor quality. I have had very little success with Bluetooth on any device I have had.
Sent from my XT1254 using XDA Free mobile app
Found a Fix for the Stuttering BT issue. It's the dumb kernel on 5.02 that stutters the playback as soon as screen is off. I used a partial wakelock so the cpu stays active after screen off with this app. It works. No more stuttering. As for speakers that require high sample rate I just switched the cpu governor to performance. It's a workaround but the partial wakelock should work especially on bluetooth headphones. Here's the app's link https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
Every time I drive away from my house and the phone loses wifi signal, the bluetooth skips really bad during the transition. Once I get far enough away, it usually clears up again. For my situation, it seems the wifi radio is somehow interfering with the bluetooth signal.
So I've had three Turbos and all of them hang then restart. (first was for the crashing, second was for a screen default + crashing and I've got the third and it crashes)
I'll just be in the middle of watching a Youtube video via the app and it'll just hang and restart. Or I can be opening a new app, closing out of an old one, waking the device up. Basically it just crashes for no reason, same thing with all three I've had. And this isn't an occasional thing we're talking 10+ crashes a day, usually within every 5-10 minutes of use.
I've tried factory resets and not installing any 3rd party apps, still crashes. Tried not using WiFi, still crashes.
Getting ready to throw this thing through a wall, basically it's unusable and I have no idea what to do besides get a different phone.
I have had a few random reboots, seems like mostly when it's connected to my bluetooth in the car.
I just don't understand why three of these phones all do exactly the same thing. I'm certain it's nothing I've done as I get the same results even immediately after factory resetting.
Was there, perhaps, a case which you used with all three phones?
A random reboot is oftentimes a result of overheating.
Im Saint said:
Was there, perhaps, a case which you used with all three phones?
A random reboot is oftentimes a result of overheating.
Click to expand...
Click to collapse
Never overheated, I monitor battery temps constantly. Usually it was in the low 30c range.
Are you getting them directly from Moto? I've had two thanks to a faulty sim tray/volume rocker and neither has ever done this.
My girlfriend's Droid Mini did the random reboot thing. It seems some Moto phones are just lemons, though three in a row seems to defy the odds.
Sent from my SM-T337V using Tapatalk
App issue
I've had three as well (a broken screen and a charging port that I ruined myself.) All three have been flawless, and I also sell Verizon for a living with basically zero complaints or returns on them. Either you are the most unlucky guy alive, or you have an app that is jacking something up.
Anyone else with this phone using Android Auto? I've been having issues with my Kenwood DDX9207S head unit where it sometimes doesn't initialize AA properly, is more often than not very laggy, etc. Sometimes it runs smoothly, as I would expect for a phone of this class with these specs, but it's getting pretty frustrating. I've tried clearing Android Auto's data/cache and uninstalling and reinstalling it, but nothing seems to help. I'm not sure if it's an AA issue, phone issue, or possibly the head unit (very doubtful, but the screen sometimes stays stuck on AA after disconnecting the phone). I can sometimes resolve the issue simply by unplugging and replugging the phone in, sometimes I have to kill all app processes, and sometimes I have to flat out reboot the phone.
EDIT:
Did some testing last night and this morning during my commute (I sit in a lot of traffic, don't worry) and found a possible culprit: Settings. I looked at the memory usage for apps, and without fail, everything was using very little memory except Settings, which was eating 100-300mbs. Killing the process instantly made AA responsive again, but within 5-10 minutes, I was seeing lag again, and Settings was building up memory usage. I'm going to perform a factory reset on the phone today to see if that alleviates the issue.
EDIT II:
After factory resetting the phone, I'm not seeing issues, SO FAR, with AA. The settings thing wasn't the right target. I still get high RAM numbers with it regardless, and I see the same thing on my Tab S2, so that's obviously not what was causing the issue. The difference *might* be that I disabled a lot of AT&T bloatware before, and in doing so might have messed something up. I'm leaving everything enabled right now, so we'll see how this goes. I only have one car ride under my belt so far, so it's not a very scientific comparison.
EDIT III:
Ran into the exact same issues earlier this afternoon. Plugged the phone in, got the "Accept" screen on my head unit, and then blank. I looked at my phone and realized that AA didn't actually launch, so I unplugged it and plugged it back in. It launched that time, but the lag was there. I can take up to 10 seconds for AA to register a touch, and Maps freezes up constantly for 10 seconds or so before trying to catch up (it usually doesn't catch all the way up before it freezes again). This makes AA more or less unusable for me. I can't find anyone else out there that has had these issues with AA and this phone, so I'm unsure of what the issue actually is. The only difference between last night and today is that last night I was listening to podcasts through Pocket Casts, and today I used Audible. I'll do a bit more testing with/without Audible to see if that's the culprit; I know AA support is relatively new on Audible (though it was in the beta for a while). Again, I haven't seen anyone complain of poor AA performance while using Audible, so I don't know if that's the issue. I wish I had a Nexus to test this against to see if its the phone...
Having the same issue it does not connect all the time