Related
Ok so i am trying to determine what my problem is.. here are the symptoms. When i try and end a call i sometimes have to press multiple times or deliberately press and hold the end button and sometimes it doesn't respond pretty much at all. Also i am using go launcher and when i press icons that are in the dock bar they have the same issues. I also have similar issues when i text it's really annoying so is anyone else have similar issues?
Sent from my VS910 4G using XDA App
Same here. I've noticed that to hang up it takes a deliberate double tap. Also, the screen will sometimes become inoperable requiring a reboot. This has happened three times since first getting it. One note if that out happened twice stock, and once with decrapped 1.1
Any body else seen this?
Sent from my VS910 4G using XDA Premium App
I haven't seen it anywhere else, but I have seen the double tap on the end button to end a call. Seems to happen frequently. A "feature?"
Either way, it's annoying.
Running Go Launcher as well.
To me, it seems like it takes the screen a really long time to wake up from being off, in all cases - for example, dial voicemail and put the phone to your ear. When you get the prompt to put in your PIN, take it away and the screen comes on, try to punch the dialpad button immediately and it just won't work. I tried it as I was writing this and had to triple tap the button.
Same thing with the lockscreen (still on the stock lockscreen for now). The screen will wake up and it takes a second or two to even start to register finger swipes. It's really annoying...
Speaking of phone lockup, I received a call a few days ago and the phone froze - I couldn't answer the call, or do anything, all the while the phone just kept ringing. Had to pull the battery. I'm still on the stock ROM.
Me too! I had a call and it froze. Battery pull as well. Also, forgot to mention I am using open home launcher.
Sent from my VS910 4G using XDA Premium App
Yep it's a bug either in LG's function to turn on and off the screen in Android, or the kernel drivers that enable/disable the touchscreen. There is about a 1 second delay to it.
I discovered this lovely bug while porting the AOSP lockscreen mod.
I'll run some more tests to see whether it's an android bug or a kernel bug. I'm betting it's android (something like the screen being turned on before the touch controller has had time to reinitialize itself, or something more complicated like a race condition of some kind...)
Either way, with cm7 around the corner, I don't think it's that big of a bug
thecubed said:
Either way, with cm7 around the corner, I don't think it's that big of a bug
Click to expand...
Click to collapse
Errrr Are you sure the Revo is getting CyanogenMod 7? Where did you hear this and more importantly when will we get it?
AndroidCraig said:
Errrr Are you sure the Revo is getting CyanogenMod 7? Where did you hear this and more importantly when will we get it?
Click to expand...
Click to collapse
Since he is the one working on getting it ported over, I think he has the best idea, and the only rule of cm is no asking for etas ;-)
Sent from my VS910 4G using XDA Premium App
This is apparently a common enough thing from what I've seen on line, but every solution I find involves the person having used a profile switcher or their calender to signify being unavailable. I do not use either type of program. I almost never silence my phone. (in the movie theater or similar, yes, but otherwise never) Does anyone have any idea what it could be? It;s only been happening since the OTA update to .217 ICS. It's getting thoroughly aggravating missing calls and texts, as I'm sure you can imagine... Thank you to anyone with ideas/suggestions.
Check your settings in both the system settings as well as each individual app. I think after the update the messaging app is set to silent by default, or at least the vibrate is turned off.
If the system is messed up I recommend that everyone install the ota factory reset. Clearing out your old GB data and letting the ICS run "fresh" solves a lot of problems.
Sent from my DROID4 using Tapatalk 2
Could it be a Smart Actions setting?
Settings are all fine yet it does randomly put itself on silent mode no vibration and you have to turn it back to vibration via settings volume rocker just puts it back on silent....
Sent from my DROID4 using xda app-developers app
The Magician Type 0 said:
Check your settings in both the system settings as well as each individual app. I think after the update the messaging app is set to silent by default, or at least the vibrate is turned off.
If the system is messed up I recommend that everyone install the ota factory reset. Clearing out your old GB data and letting the ICS run "fresh" solves a lot of problems.
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
The Kraken! said:
Could it be a Smart Actions setting?
Click to expand...
Click to collapse
If it keeps happening tomorrow, I will do a full factory reset. Hoping I won't have to though. It's a pain in the rear to restore everything... It isn't a smart action thing because I have that app frozen, good thought though. Thank you all for the responses.
I tried a fr from recovery menu never froze apps nor rooted this d4 didn't help...
Sent from my DROID4 using xda app-developers app
Update
I've found that it is only doing it with phone calls now. I cannot find a setting in the phone app or the system settings that is set to mute, but it keeps happening. Also, after using the lock screen to unmute it, I have to turn up the volume manually. The lock screen thing only bumps it up to the minimum volume level... Anything else come to mind before i do a full FR? I'd really rather avoid it if I can... Thanks again.
Now I've got one worse. Did a FR, no go. Tried to update to Eclipse, and messed it up. Had to .sbf back to factory. EVEN AFTER the .sbf, still having the same issue with it muting while recieving a call.... (i.e. goes on vibrate instead of ringing....) Any ideas ANYONE???!!?!?!?
Honestly, this sounds like a hardware issue to me. If I understand correctly, it sounds like the phone keeps going to silent (or vibrate after ICS)?
My guess after all your software troubleshooting is that your volume down key is either physically or electronically damaged, and periodically decreases itself. You might want to try remapping the volume button or something to see if that solves the problem. Of course, after that you don't have any volume buttons, which stink.
Aside, the physical buttons (power, volume) on the D4 really stink. They are very mushy and almost flush with the case, poor design if you ask me.
That thought crossed my mind also, but it only happens on an incoming call, and I can adjust the volume up and down in every app. If I don't receive a call all day, there is no problem, texts & emails work fine. I've even had a friend sit with me and text me (sound worked) then call me (muted as it received the call) and all it did was vibrate, no ringtone. I have who is it and thought it might be that, but un-installed it and no change... I'm totally out of ideas...
Thank you for the ideas, unfortunately nothing has worked so far. Any further ideas will be much appreciated. Thanks again.
Finally figured it out. Apparently it had to do with some stetting that Who Is It made. I had it set to announce the caller, which apparently doesn't work now. When I un-installed who is it nothing changed, so I re-installed it and on a whim disabled the announce feature, and it's been ringing fine since. I believe it was some sort of setting because after disabling the announcement, I un-installed who is it again, and the phone would ring without a problem. No Idea what setting it was. Thanks to veryone for the help.
My wife's S5 fails to wake up after multiple home button or side button presses. Sometimes takes a lot of tries!
Anyone else ?
HTC UltimEight ??
Not experiencing anything like that here. Wakes up the first click every time.
I have this problem too. Are you running ART?
Had the same issue this morning. Took a minute for it to come on.
Sent from my SAMSUNG-SM-G900A using xda app-developers app
I did notice a HUGE decrease in wake-up performance while messing with the lockscreen "effects". It seems either using no effect to unlock it, or the watercooler is the fastest (which I like the best anyway).
Also, try turning off the help information and the additional information (such as the weather). The lockscreen weather will effect wake-up time due to it trying to refresh when you wake-up the phone.
I experienced this issue running ART. Been on dalvik since last night and haven't noticed it yet, but it hasn't been long enough to be definitive.
Wow you guys are onto something.
I indeed switched to ART.
Well going back to dalvik to see if it stops.
Thanks guys
HTC UltimEight ??
Jooosty said:
My wife's S5 fails to wake up after multiple home button or side button presses. Sometimes takes a lot of tries!
Anyone else ?
HTC UltimEight ??
Click to expand...
Click to collapse
2 days with mine and I have noticed this several times, some KK custom ROMs had a similar issue so it didn't really faze me but it shouldn't be there on a factory ROM. It has always come on after 2-3 pushes but again this is a brand new totally stock device so WTF?
It seems like there is a slight delay between button push and screen light up so pushing it the 2nd time actually turns it off. If I wait a very long second it lights up without multiple pushes.
The other day I switched my runtime to ART from Dalvik, which I much prefer. Everything was running fine until I picked up my phone and realized that the Active Display didn't come to life. Then the power button wouldn't make the phone respond (battery was at 75%) either. So I did a 3-button reset of the phone.
After the phone boots up I go to the home screen, then all of a sudden the screen stops responding to my touch and the screen fades to black. Again, Active Display doesn't appear and the power button doesn't wake the screen up. Holding the power button down by itself does nothing... only a 3-button reset will reboot the phone. This continues for an hour or so until my phone finally stays awake and stops misbehaving.
The following day my phone seems fine. Played a couple games, used Maps to navigate, and a half dozen other apps for an hour or two. Then after taking my phone out of my pocket a little later, there's no Active Display and the power button doesn't work. [emoji35]
The only app I have had any problems with is Hangouts... where the app would randomly force close. Thinking this might be the culprit, i uninstalled the updates for Hangouts and took it back to it's stock state (since I can't uninstall it outright). But alas, the issue happens maybe twice more, seemingly at random throughout the rest of the day.
This morning I switched back to Dalvik and have yet to have a weird shutdown. I would really like to switch back to ART though because there are several apps that seem to run more smoothly with less stuttering during scrolling with ART enabled rather than Dalvik. I used ART with my 2013 Moto X with never an issue for nearly a year. Any words of advice or suggestions? I really don't want to have to get a replacement device... but I guess I will if I absolutely have to.
I had similar activity happen to me when switching to ART. Staying on Dalvik has eliminated any weird behavior except for the Hangouts force closing. I guess we have to wait on Google for an update.
What version do you have ? I have a XT1097 and its been 2 days with ART, 0 freeze or feboots
Faruko said:
What version do you have ? I have a XT1097 and its been 2 days with ART, 0 freeze or feboots
Click to expand...
Click to collapse
I have a 32GB Moto Maker variant on Verizon. XT1096.
I posted that I was getting shutdowns as well, with very few responses other than people telling me that they were not experiencing the same problem. I did however leave out that I was experiencing the problems while running on ART, and as some of you others have posted, after switching back to dalvik I have had no such issue. I also prefer ART but I will have to wait for an update I guess, which probably will not be until we get the upcoming Android L.
I should also mention that it seemed as though I was only getting the freezes/shutdowns while at work, where I have poor cell reception, yet I have wifi. Also, my phone is in my pocket all day and it does sway around a bit in my pocket. I am thinking this might make the IR sensors go a little crazy. Maybe the lack of cell reception and the IR sensors going crazy has something to do with it, if indeed having the phone in my pocket is messing with the sensors. You're not alone though. Stick with dalvik until we get an update.
stastnysnipes26 said:
I posted that I was getting shutdowns as well, with very few responses other than people telling me that they were not experiencing the same problem. I did however leave out that I was experiencing the problems while running on ART, and as some of you others have posted, after switching back to dalvik I have had no such issue. I also prefer ART but I will have to wait for an update I guess, which probably will not be until we get the upcoming Android L.
I should also mention that it seemed as though I was only getting the freezes/shutdowns while at work, where I have poor cell reception, yet I have wifi. Also, my phone is in my pocket all day and it does sway around a bit in my pocket. I am thinking this might make the IR sensors go a little crazy. Maybe the lack of cell reception and the IR sensors going crazy has something to do with it, if indeed having the phone in my pocket is messing with the sensors. You're not alone though. Stick with dalvik until we get an update.
Click to expand...
Click to collapse
Well that's disappointing... hopefully history will repeat itself and we'll see Android L sooner rather than later. I'd really like to be able to use ART again.
I'm willing to bet the 2014 moto x will be the first device after nexus devices to get android l.
Sent from my XT1096 using Tapatalk
Hey guys,
I am using my Moto X (XT1052) for almost 2 years now. It is/was the best android phone I've had so far. It was smooth, had no hangs and just did what it was supposed to do. Since I received the Update to 5.1 I keep on having real strange issues and it really bothers me because it really renders the phone useless at times. And since I couldnt find another thread with all bugs collected in one place, I am going to start my own thread.
So which bugs did I find so far?
1.Youtube and other video services don't work all the time
(They work sometimes, but the the video stops, tries to resume and ends up in a loop trying to load the video. Often only a reboot helps.)
2. Battery consumption in general has become way worse (cell-standby)
3. Random "Optimizing apps" after a reboot
4. No Active Display with handsover (I know this isn't a feature anymore, but to me this is a bug as well)
5. Missing energy widget
6. Wifi range has reduced significantly and seems to be buggy at times (can't always tell if it's my router or the phone, but mostly it's the phone)
7. Sometimes the phone uses mobile data instead of wifi, even if connected
8. Vibration mode (important notifications only) doesnt always end properly and the phone doesn't start vibrating again after the set time or alarm
I think that's it for now. But this clearly is enough for me.
So please Moto guys do something! If you need logcats or anything else, let me know and I ll help out as good as I can. I was one of those who patiently waited for an update instead of crying for one, because I wanted a stable one rather than a fast and unstable one. So either fix it, or I ll have to return my Moto X. The phone in its' current state is useless for me. Especially as I can't even downgrade without having to risk a full brick. So please do something and push an update to either allow downgrading, or fix the existing bugs!
Sent from my XT1052 using XDA Free mobile app
N00BY0815 said:
Hey guys,
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
I miss this very badly
"No Active Display with handsover"
Now I have to tap or take my phone to see notifications... :crying:
I switched over to CM and all is going great of course at a small cost of losing Moto voice feature but I can most certainly live without it. I've got very decent battery life of 5-6hours of screen time over a span of 13hours. No over heating issues and usually cell standby sits at 2% usage which is absolutely fine for me.. Even the hand wave gesture works with active display. I'm so happy with how stable it is with CM. Living with a bug free phone for now.
Sent from my Moto X
Random Crashes followed by optimization boot
I have been getting random crashes that lead to the phone shutting off. When I turn it back on, it takes FOREVER to optimize 92 apps. I don't have even 30 apps on the phone!
I did a factory reset and still have this problem. It's happening every couple of days. It's making my experience with this phone very frustrating!
Some more issues I've found:
Soundproblem, sometimes when I switch e.g. from twitch to spotify and then try to increase or decrease the volume, I get a crackling sound every time I push the button. Sometimes it disappears after a certain time of not playing anything, but mostly again only a reboot helps.
The phone unlocks itself more often in my pockets for no obvious reason.
The unlock on the ActiveDisplay unlockscreen often only leads to the normal unlocking screen instead of the homescreen. Same thing when I try to open notifications. Mostly those apps run, but I get to see the normal lockscreen, instead of the app with the notification.
Sent from my XT1052 using XDA Free mobile app
I think I found a fix for the YouTube problem.
Press the power button and keep it pressed till you feel another vibrate ie. After the power menu pops up.
That seems to solve it
Sent from my XT1052 using Tapatalk
adity said:
I think I found a fix for the YouTube problem.
Press the power button and keep it pressed till you feel another vibrate ie. After the power menu pops up.
That seems to solve it
Sent from my XT1052 using Tapatalk
Click to expand...
Click to collapse
Well that's not exactly what I would call a fix it appears to work sometimes though. I also noticed that simply changing the video quality from let's say 720p to 480p often resolves the issues. I mostly get the video bug, when I am trying to watch things in 720p or above. Maybe it is a codec problem? A broken lib?
Sent from my XT1052 using XDA Free mobile app
For YouTube, you could get another app. I stopped the cell standby issue by turning off carrier internet when not needed. Install greenify, servicely, battery saver, and power nap. 1 I too have random optimizing of apps. 2 pocket dials have increased, 3 if I tap on the phone icon from messaging app to make call to that person, I have to exit out of the SMS app before I see the call screen. 4 sometimes when I'm multi tasking I go back to another app but the app reloads and doesn't take me to where I was. 5 Google now voice only responds 30% of the time when i say hello google. Some other problems I have noticed but can't think of right now
---------- Post added at 12:41 PM ---------- Previous post was at 12:38 PM ----------
Good thing I waited for a version that I could go back to kit kat because it didn't update the bootloader to lollipop. This is the thread if anyone is interested. I flashed this rom for xt1053 on my Rogers xt 1058, with only speaker phone not working away from WiFi for some reason, but that's if you flash on another moto x besides xt1053. http://forum.xda-developers.com/showthread.php?t=3155843
1. Battery drain (cell standby) makes the phone unusable.
2. WiFi does not connect or only works rarely now.
- download two times on whatsapp
- dialler doesnt dial a call
Sent from my XT1052
Cell Standby Battery drain is the worst..
Randomly restarting and optimizing apps has been a huge problem as well.
I miss the wave to wake for active notifications...
But what I really hate about 5.1, is that when using wifi my mobile radio keeps active all the time...
This drains the battery while being on wifi...
Funny enough, when I'm on mobile data, everything is ok and mobile radio is active only when needed by the apps...
On wifi on the other hand, oh man... it's active all the time...