Database Develop

[Q] Phone 'dies' after using touch to wake feature after a period of time

Hey guy,
I love this phone and the ability to touch the screen to wake it via the app eXperience Pro.
The only issue is that with the framework / module loaded , when I receive or make a call, the phone would be close to my ears which means that the proximity sensor will shut the screen off. However, when the conversation ends, I wouldn't be able to turn the screen on, either by tapping the screen or pressing the power button.
There are times that when I am not in a call, and my phone is just sitting idle, and when it comes to waking it up, it wouldn't do so. I have to manually restart it just like the issue above. What I noticed yesterday was that my led notification light was on indicating that I had a message. I didn't look at it until after awhile which I realize that I couldn't turn on the phone. The led notification was still working.
Then I decided to call up my phone and I could hear the dial tone from my other phone, however, my xperia Z was sitting idle with its screen off without any ringtone and so on.
I would really like to feature to work flawlessly. Tried it on about 4 ROMs, and the issue persist. Is there any way for me to show the log so someone could figure out whats causing the phone to behave this way?
Without the module loaded, the phone works just fine. I have sent a PM to the developer but have not received any replies since.

not all apps are made for every android phones out there. If its causing issues to your Z, just stop using it or contact the app developer (which you did) and hope for the best.
I dont think there is anyone willing to just make a rom or tweak just for a specific app to function flawlessly on an Z. Especially when its not a super popular app.

LitoNi said:
not all apps are made for every android phones out there. If its causing issues to your Z, just stop using it or contact the app developer (which you did) and hope for the best.
I dont think there is anyone willing to just make a rom or tweak just for a specific app to function flawlessly on an Z. Especially when its not a super popular app.
Click to expand...
Click to collapse
My main concern is what is causing this to happen and to see if other xperia Z users are facing the same issue.

I'm using this app.. For me until now no problem..

List of bugs on Note 3

I love this device but it has a couple of issues. I thought it would be helpful to list bugs in this first release of the software. I'm not rooted. These are mine:
Haptic feedback on menu keys sometimes stops
Air Command has stopped working. Its intermittent.
Sound controls sometimes don't allow me to make changes (right now I can't change notification sound level)
Sent from my SAMSUNG-SM-N900A using xda app-developers app

I myself have not encountered the haptic-feedback, air-command, or sound-control problems.
The one problem I've found is that Google Hangouts won't do video calls via LTE. It pops up a message saying a WiFi connection is required instead. (The Note 2 used to have the same problem on ATT, but it was fixed about a month ago.)

Another annoying bug is that AVRCP 1.3 does not seem to be implemented properly.
Song/Media metadata does not get properly sent via bluetooth to receiving devices. This has been seen as not working at all to song information getting stuck on display and not changing when tracks change.
I'm definitely looking forward to a big fix for this one.
This has been seen on ATT, Tmobile, and Sprint variants.
Sent from my SAMSUNG-SM-N900A using Tapatalk

Gary02468 said:
I myself have not encountered the haptic-feedback, air-command, or sound-control problems.
The one problem I've found is that Google Hangouts won't do video calls via LTE. It pops up a message saying a WiFi connection is required instead. (The Note 2 used to have the same problem on ATT, but it was fixed about a month ago.)
Click to expand...
Click to collapse
You have to edit some code to allow video call on LTE. changing a 0 to a 1. Google to learn how. Can be fixed

wdkingery said:
You have to edit some code to allow video call on LTE. changing a 0 to a 1. Google to learn how. Can be fixed
Click to expand...
Click to collapse
But the workaround requires rooting, doesn't it? (For me, the disadvantages of rooting at this point outweigh the benefit of Hangouts via LTE.)

Gary02468 said:
I myself have not encountered the haptic-feedback, air-command, or sound-control problems.
The one problem I've found is that Google Hangouts won't do video calls via LTE. It pops up a message saying a WiFi connection is required instead. (The Note 2 used to have the same problem on ATT, but it was fixed about a month ago.)
Click to expand...
Click to collapse
Edit. Just saw you dont wanna root
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Gary02468 said:
But the workaround requires rooting, doesn't it? (For me, the disadvantages of rooting at this point outweigh the benefit of Hangouts via LTE.)
Click to expand...
Click to collapse
Whats the disadvantages to rooting?

The only bug that I have noticed is sometimes when I get an email notification from the stock email app, it appears in the status bar and then disappears within a couple of seconds. I've seen this a couple of times.
I guess we have to expect some issues since this is the first device out of the box with 4.3.
I really wish they would allow the widgets on the lock screen while having a pin for security. At least read only.

Unhived__Mind said:
What['re] the disadvantages to rooting?
Click to expand...
Click to collapse
Some of the disadvantages are:
* If I screw it up, I could brick the phone, or at least make the phone unavailable while I have to spend a lot of time fixing it.
* Rooting will wipe my existing setup, requiring more time than I want to spend to re-initialize my phone.
* There may be security, stability, or performance problems that have not been discovered yet.
* If my phone exhibits any subsequent problems, even if they're not actually due to rooting, I won't have any easy way of knowing whether that's the case.
* I don't know whether rooting may interfere with subsequent OTA updates (unless I go to the trouble of flashing back to stock first).
* No one can rule out the possibility that rooting will void the phone's warranty.

screen and sound
has anyone noticed occasional brightness flickering? I thought it might be adaptive display or something like that, and i disabled it all, but I still see it.
also, I'm not sure what in the world happened, but my phone started randomly playing music. the music player didn't open, I had air gestures, off, and it wasn't ringing. I turned off wifi and the music stopped. In fact, i don't even think I have the song that was playing saved to my phone.

nespid said:
has anyone noticed occasional brightness flickering? I thought it might be adaptive display or something like that, and i disabled it all, but I still see it.
also, I'm not sure what in the world happened, but my phone started randomly playing music. the music player didn't open, I had air gestures, off, and it wasn't ringing. I turned off wifi and the music stopped. In fact, i don't even think I have the song that was playing saved to my phone.
Click to expand...
Click to collapse
Ghost in the machine....
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Gary02468 said:
Some of the disadvantages are:
* If I screw it up, I could brick the phone, or at least make the phone unavailable while I have to spend a lot of time fixing it.
* Rooting will wipe my existing setup, requiring more time than I want to spend to re-initialize my phone.
* There may be security, stability, or performance problems that have not been discovered yet.
* If my phone exhibits any subsequent problems, even if they're not actually due to rooting, I won't have any easy way of knowing whether that's the case.
* I don't know whether rooting may interfere with subsequent OTA updates (unless I go to the trouble of flashing back to stock first).
* No one can rule out the possibility that rooting will void the phone's warranty.
Click to expand...
Click to collapse
Rooting any device voids warranty. It does not trip the flash counter or Knox. Just flash back to stock or supersu unroot.
As for the other stuff, no issues here. Phone is as stable as it was on stock. Runs even better because debloated it myself.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Gary02468 said:
Some of the disadvantages are:
* If I screw it up, I could brick the phone, or at least make the phone unavailable while I have to spend a lot of time fixing it.
* Rooting will wipe my existing setup, requiring more time than I want to spend to re-initialize my phone.
* There may be security, stability, or performance problems that have not been discovered yet.
* If my phone exhibits any subsequent problems, even if they're not actually due to rooting, I won't have any easy way of knowing whether that's the case.
* I don't know whether rooting may interfere with subsequent OTA updates (unless I go to the trouble of flashing back to stock first).
* No one can rule out the possibility that rooting will void the phone's warranty.
Click to expand...
Click to collapse
Good summary!
Sent from my SAMSUNG-SGH-I317

Using Google Music over headphone aux cable, setup eq the way you want, listen for a sec and slide the track knob to another part of the song. The eq turns off. If you go in to the eq settings, it is showing on. Toggle off and on and you will hear the difference.
Sent from my SAMSUNG-SM-N900A using Tapatalk

I don't have any of the bugs being list here. However, when I have S Voice on for wake up when the screen is off, it will sometimes turn on randomly even when nothing is said. Happened in a movie theater for me and it was embarrasing. That feature is now off.
Sent from my SAMSUNG-SM-N900A using Tapatalk

Anyone else having problems using whatsapp with pen window?
It seems that when I minimise it from a conversation I then can't open it again or move the icon around on the screen.
Works normally if I press back to the conversation window first though

S voice gets weird with me too. Had it in hands free mode and it kept telling me something about my safety while it simultaneously read my text out loud. it kept getting stuck in that loop for any new messages.

lax_22 said:
Anyone else having problems using whatsapp with pen window?
It seems that when I minimise it from a conversation I then can't open it again or move the icon around on the screen.
Works normally if I press back to the conversation window first though
Click to expand...
Click to collapse
Same here

Screen brightness and
Screen brightness issue: occasionally, when brightness is set low (not auto), when phone is turned on, screen turns on at full brightness for a split second then go to low setting level. Happens about 25% times.
Haptic feed back when screen off: after I turn screen off, if I move phone, I get a haptic feed back once. Doesn't repeat until I turn screen on and off again.
Edit: this is caused by 'smart alert'. Under Controls -> Motions. It vibrates when you pick up the phone and you have a notification and the screen is off to let you know there is something you missed.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

Anyone having internet problems? When I'm on wife or 4G lte, the stock browser will get halfway through loading a Web page, then it will just hang there for a little.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Delayed or not receiving Notifications?

Hi everyone,
I have had the Moto G 2nd Gen for about 10 days now and I have noticed that notifications from several apps (Exchange email, Gmail, Whatspp, Facebook...) are either delayed by a few hours or don't come at all. This happens on both Wifi or my network. Has anyone else experienced this ?
I have tried the following with no success:
1- disable Wifi optimization
2- factory reset phone
3- Installed PNF No-Root and set hearbeat to 5min
4- Cleared data & cache of apps
My phone is not rooted running 4.4.4
Thanks

Yes I am having the same problem this is my thread on the subject:http://forum.xda-developers.com/moto-g-2014/help/notification-problems-t2875216
I have tried 1, 2 and 4 of your attempts to fix it to no avail.
Before I reset the phone all notifications showed the correct time that they should have come, for example if I slept the phone at 10:40 and a notification came at 10:44, I then woke the phone at 10:50 the phone would immediately buzz and sound but it would say the notification came at 10:44 in the notification draw.
However after the factory reset of the device in the same situation the notification draw would show 10:50 but I know that is wrong because WhatsApp for instance will say the correct 10:44 timestamp on the message in the app.
Notifications when the phone is awake come through perfectly every time.
The problem is actually not limited to just notifications, I play music from my phone, when the the phone is awake it plays perfectly, when you sleep the phone, the music will carry on playing but occasionally it will have a hiccup where it will stop playing for a split second then carry on, and sometimes at the end of a song you expect the next song to start but it never will, if you then wake the device the song will start playing like nothing was wrong (exactly how the notification problem is).
I don't know what the problem is I suspect something to do with bad software or faulty hardware if there is a specific part of the hardware that only comes into play when sleeping (I don't know if there is or not).
What are the specifics of your phone? Mine is a XT1068 8GB Dual SIM Retail GB completely stock 4.4.4, the system version is: 21.11.14.titan_retgb.retbgall.en.GB retgb, will be good to know if this affects specific versions of the phone or any version, to narrow down the problem.
The problem is also completely random I cannot 'make' the problem happen it just does.

Mine is the same as yours XT1068 8GB Dual SIM Retail GB 21.11.14.titan_retgb.retbgall.en.GB retgb.
I also have the same problem with music, I also noticed this with chromecast, it seems to loose connection after playing one track.
I contacted Motorola assist and they said replace the phone. I'm not sure if replacing it will solve the problem, I'm guessing this is a software issue. I
I got it from Amazon UK, I'm thinking of returning this and going back to my Galaxy Nexus and wait for the new Nexus phone.

Because we have the same software version I more strongly suspect this is a software issue now, I'm not sure what to do, I don't really want to return the phone as I will be left phoneless and a replacement would just come with the same software.
Another option would be to re flash to a different software version (an international version) but that will invalidate the warranty.
Not really sure what to do, would be good hearing if any retGB people are not having any problems, if any are reading this thread? or if any non retGB are having this problem.

jay2the1 said:
Yes I am having the same problem this is my thread on the subject:http://forum.xda-developers.com/moto-g-2014/help/notification-problems-t2875216
[...]
The problem is actually not limited to just notifications, I play music from my phone, when the the phone is awake it plays perfectly, when you sleep the phone, the music will carry on playing but occasionally it will have a hiccup where it will stop playing for a split second then carry on, and sometimes at the end of a song you expect the next song to start but it never will, if you then wake the device the song will start playing like nothing was wrong (exactly how the notification problem is).
I don't know what the problem is I suspect something to do with bad software or faulty hardware if there is a specific part of the hardware that only comes into play when sleeping (I don't know if there is or not).
What are the specifics of your phone? Mine is a XT1068 8GB Dual SIM Retail GB completely stock 4.4.4, the system version is: 21.11.14.titan_retgb.retbgall.en.GB retgb, will be good to know if this affects specific versions of the phone or any version, to narrow down the problem.
The problem is also completely random I cannot 'make' the problem happen it just does.
Click to expand...
Click to collapse
For notification problem read description of https://play.google.com/store/apps/details?id=com.andqlimax.pushfixer.noroot&hl=en
and yes I also have same problem for play music my phone is XT1068 16gb retaildsdsall.en.03.retin
I think you should create new thread for play music problem, seems like we all have that

bhavin192 said:
For notification problem read description of https://play.google.com/store/apps/details?id=com.andqlimax.pushfixer.noroot&hl=en
and yes I also have same problem for play music my phone is XT1068 16gb retaildsdsall.en.03.retin
I think you should create new thread for play music problem, seems like we all have that
Click to expand...
Click to collapse
:\ it doesn't look like that app fixes it even when changing the interval to 1min.
I've sort of found a way to at least make it happen to test stuff, using 2 devices I have installed Telegram on both and set each device up with different numbers so I can message from one device to the other, using the other device to the Moto G if I send messages sometimes the notification is instant, sometimes it is a minute later, there is no pattern on whether it will receive it instantly or delayed, however waking the device will always make the phone buzz if it is delayed.
If I add my tablet into the mix (tablet and Moto G on the same number) the difference is very stark, sending 5 quick fire messages the tablet buzzes for every message, the Moto G may buzz for the first and maybe the 2nd but then nothing for the other 3, or none at all, or none and then double beep on the last message or a little time after the last message. (all this is on WiFi)
The best news is that it has eventually beeped within a couple of minutes for every message, but in a conversation on WhatsApp a couple of minutes is a long time.
Again if the phone is awake or playing music while sleeping it works perfect a beep for every message every time (WiFi Again). (I know PNF is only a partial fix for WhatsApp and Telegram but I can't test it easily with Gmail and the main concern is WhatsApp as I want those messages without delay)
It's definitely something to do with keeping the phone 'active', if it's playing the music it works, if it's doing nothing it is literally like it's sleeping on the job.
I'm going to test on 3G but seems to work almost perfect so far (I haven't really used my phone on 3G much as I'm normally on WiFi)
@katkat911 can you tell me about your WiFi setup it isn't TP-Link is it? because I'm wondering if it could be a WiFi setup issue as my phone originally couldn't even detect my router until I changed some settings. (I know you have the problem on 3G too)
Apologies if this is a bit rambly I want to put my casual findings out there in order to let others have the information.

Been testing on 3G, after the phone is slept all notifications work perfectly for 10 minutes with the phone buzzing a second or 2 after my tablet, if you sleep the phone and send a message after 10 minutes the phone will only buzz after 30 minutes from being slept (ie the heartbeat).
I've reinstalled PNF app and will experiment more tomorrow, still not sure how I will fix WiFi but I think a little more experimentation is required (yet doesn't make sense why my tablet always works 100% and the phone doesn't when using the same router)

jay2the1 said:
:\ it doesn't look like that app fixes it even when changing the interval to 1min.
I've sort of found a way to at least make it happen to test stuff, using 2 devices I have installed Telegram on both and set each device up with different numbers so I can message from one device to the other, using the other device to the Moto G if I send messages sometimes the notification is instant, sometimes it is a minute later, there is no pattern on whether it will receive it instantly or delayed, however waking the device will always make the phone buzz if it is delayed.
If I add my tablet into the mix (tablet and Moto G on the same number) the difference is very stark, sending 5 quick fire messages the tablet buzzes for every message, the Moto G may buzz for the first and maybe the 2nd but then nothing for the other 3, or none at all, or none and then double beep on the last message or a little time after the last message. (all this is on WiFi)
The best news is that it has eventually beeped within a couple of minutes for every message, but in a conversation on WhatsApp a couple of minutes is a long time.
Again if the phone is awake or playing music while sleeping it works perfect a beep for every message every time (WiFi Again). (I know PNF is only a partial fix for WhatsApp and Telegram but I can't test it easily with Gmail and the main concern is WhatsApp as I want those messages without delay)
It's definitely something to do with keeping the phone 'active', if it's playing the music it works, if it's doing nothing it is literally like it's sleeping on the job.
I'm going to test on 3G but seems to work almost perfect so far (I haven't really used my phone on 3G much as I'm normally on WiFi)
@katkat911 can you tell me about your WiFi setup it isn't TP-Link is it? because I'm wondering if it could be a WiFi setup issue as my phone originally couldn't even detect my router until I changed some settings. (I know you have the problem on 3G too)
Apologies if this is a bit rambly I want to put my casual findings out there in order to let others have the information.
Click to expand...
Click to collapse
I agree with you that it has something to do with phone going to sleep. My WiFi router is Netgear. I have they same problem with every other WiFi network and also on 3G. I didnt have this problem on my previous phone Galaxy Nexus.
PNF doesnt seem to work at all.

Notification problem is proved. I also have the issue. that 10 mins theory is absolutely right. as both of you have done good research, I would suggest one of you create a question at https://forums.motorola.com/hives/e3ec93b1d7/summary and summarize all your findings. Some one from Motorola will respond definitely. I see this as a deep sleep issue with the kernel. Once submitted, you can share the link of your thread here. I and others will comment confirming this as a common problem.
You may have to first register with your moto id or may be google id.

anshumandash said:
Notification problem is proved. I also have the issue. that 10 mins theory is absolutely right. as both of you have done good research, I would suggest one of you create a question at https://forums.motorola.com/hives/e3ec93b1d7/summary and summarize all your findings. Some one from Motorola will respond definitely. I see this as a deep sleep issue with the kernel. Once submitted, you can share the link of your thread here. I and others will comment confirming this as a common problem.
You may have to first register with your moto id or may be google id.
Click to expand...
Click to collapse
I have posted this on the Motoral forums here https://forums.motorola.com/posts/dbb4806484

I have been experimenting again today, the problem is significantly worse on WiFi notifications are much slower than on 3G, the problem seems completely unreplicable, sometimes notifications come though aOK even after I have left the device sleeping for an hour (using WiFi) or sometimes the notification will be delayed for several minutes even if it has only just been slept (again using WiFi), 3G on the other hand there is a definite 10 minute cut off from sleeping the device.
I've had PNF installed since last night and it doesn't help WiFi at all, but 3G it might, I say might because sometimes after 10 minutes (even an hour later) if I send a notification I do receive it straight away (something that never happened before I installed PNF) but then sometimes it doesn't and it's delayed for several minutes again.
I will join the Moto forum and add my weight to that when I get back to my computer as you need to sign in with a Google account.

I've also noticed that if the phone is sleeping whilst charging notifications work flawlessly in much the same way playing music while the device is sleeping they do. I've posted this finding in the Moto forums as well.
Fingers crossed we get a solution :fingers-crossed:

jay2the1 said:
I've also noticed that if the phone is sleeping whilst charging notifications work flawlessly in much the same way playing music while the device is sleeping they do. I've posted this finding in the Moto forums as well.
Fingers crossed we get a solution :fingers-crossed:
Click to expand...
Click to collapse
I have also noticed that. It seems that many are having this issue, so far no reply from Motorola

Motorola might be investigating about it. Yesterday i went back to dalvik from art. I tested the notifications the while day. On Wi-Fi, i didn't see the delays any more. In 3g many tests were successful even after 1hr of deep sleep. Only at 4pm India time i found a delay of 22 mins for whatsapp notification. There i also realized that it had switched to 2g due to bad signal in that room. I was definitely having problem when i was on art. Last night i also got the ota for build 23. I see that the kernel is updated. I will monitor one more day and report here.

Motorola has at least seen the post even with no reply, I just hope they are busy behind the scenes working out what is wrong so they can fix it.
I've never used ART (I'm completely stock), and all the problems are still happening today, unfortunately Telegram is being DDoS'd today so haven't been able to test anything out.
It will be interesting to hear if the update you received helps in any way, esp with the updated kernel, since your retGB device received it hopefully ours may do soon too.
As far as I can tell it doesn't affect calls and SMS, but I simply don't use SMS or calls at all (WhatsApp ftw) so my testing has been the odd 'prank' phone call from my 2nd phone and it rings every time, but it's not enough to confirm if it's a fluke or if in fact it does not affect phone calls/SMS.

SMS and calls won't be impacted due to this. It's mostly related to deep sleep state of the phone. It will impact data connectivity mostly.
I have been testing as and when possible after the update. On Wi-Fi, I didn't see any delays for WhatsApp, Facebook notification, exchange mails through nine app even if the phone was in sleep mode fur an hour or so. I saw 1 min delay in Viber twice.

anshumandash said:
SMS and calls won't be impacted due to this. It's mostly related to deep sleep state of the phone. It will impact data connectivity mostly.
I have been testing as and when possible after the update. On Wi-Fi, I didn't see any delays for WhatsApp, Facebook notification, exchange mails through nine app even if the phone was in sleep mode fur an hour or so. I saw 1 min delay in Viber twice.
Click to expand...
Click to collapse
That's good news, hopefully the update has indeed fixed it, there's no indication when the update will hit the UK but if it does fix it then ASAP I hope.

anshumandash said:
SMS and calls won't be impacted due to this. It's mostly related to deep sleep state of the phone. It will impact data connectivity mostly.
I have been testing as and when possible after the update. On Wi-Fi, I didn't see any delays for WhatsApp, Facebook notification, exchange mails through nine app even if the phone was in sleep mode fur an hour or so. I saw 1 min delay in Viber twice.
Click to expand...
Click to collapse
How is the phone with the new OTA update ? are notifications still delayed?
There's still no word from Motorola

katkat911 said:
How is the phone with the new OTA update ? are notifications still delayed?
There's still no word from Motorola
Click to expand...
Click to collapse
In a different thread Motorola amin had mentioned that they are investigating the notification delay issue. I don't see much delays after the update. There are few mins here and there, but mostly good. If you haven't received the update yet, check the ota thread and update manually. It's the same update. Then see if you find any improvement.

I got the OTA update yesterday and I'm still having the same issues

How much lag is too much?

I'm curious if anyone else is finding the phone a bit too laggy, or if it's just my setup. I tap an icon or a soft key and there's a 1-2 second delay while the phone thinks about it. I move the phone away from my face when finishing a call and the screen takes 2-3 seconds to reactivate so I can actually tap end to end the call. Is this normal in your experience?
I seem to recall there was not this much lag when I first got the phone, but the odd thing is that I haven't really installed any more apps. I do use Nova, but I don't have any social apps running in the background or GPS enabled or bluetooth enabled. Just WiFi and 3G. I also turned off nearly all the Google services.

pipspeak said:
I'm curious if anyone else is finding the phone a bit too laggy, or if it's just my setup. I tap an icon or a soft key and there's a 1-2 second delay while the phone thinks about it. I move the phone away from my face when finishing a call and the screen takes 2-3 seconds to reactivate so I can actually tap end to end the call. Is this normal in your experience?
I seem to recall there was not this much lag when I first got the phone, but the odd thing is that I haven't really installed any more apps. I do use Nova, but I don't have any social apps running in the background or GPS enabled or bluetooth enabled. Just WiFi and 3G. I also turned off nearly all the Google services.
Click to expand...
Click to collapse
I have quite the opposite opinion of yours. My phone flies
Sent from my D5833 using XDA Free mobile app

The phone is fast for me as well, even recent apps have no delay (there was LAG when GravityBox was installed).
However, I notice the phone call issue you having, selecting the contact and press call, takes 1-2 seconds to get through (no visible UI lag) and after finishing the call, it takes the same amount of time while the CallUI goes away.

davebugyi said:
The phone is fast for me as well, even recent apps have no delay (there was LAG when GravityBox was installed).
However, I notice the phone call issue you having, selecting the contact and press call, takes 1-2 seconds to get through (no visible UI lag) and after finishing the call, it takes the same amount of time while the CallUI goes away.
Click to expand...
Click to collapse
The "after the call" thing you mentioned isn't a bug. It's there so you can "Call back".
Sent from my D5833 using XDA Free mobile app

pipspeak said:
I'm curious if anyone else is finding the phone a bit too laggy, or if it's just my setup. I tap an icon or a soft key and there's a 1-2 second delay while the phone thinks about it. I move the phone away from my face when finishing a call and the screen takes 2-3 seconds to reactivate so I can actually tap end to end the call. Is this normal in your experience?
I seem to recall there was not this much lag when I first got the phone, but the odd thing is that I haven't really installed any more apps. I do use Nova, but I don't have any social apps running in the background or GPS enabled or bluetooth enabled. Just WiFi and 3G. I also turned off nearly all the Google services.
Click to expand...
Click to collapse
no lag here, phone flies. have been stock from day one, it's been four months now. recent apps, transitions, opening and closing apps = all fast. there is the noted lag when starting the camera from the shutter button, and not consistently responsive Tap2Wake, but once the screen is lit up and i'm doing things, i'm happy.
re: finishing a call. just got off the phone a little while ago, and didn't notice any slow behaviour -- certainly nothing like a 2-3 second delay to come on.

OK, so I guess I might have a problem. The weird thing is that sometimes there's a lag launching an app and other times there's not. Must be something running in the background messing with it, not that I normally have much running.
The phone call thing is really annoying though, and has become worse since the firmware update. Often I will have to push the button to get the screen to light up when I want to end a call. It's like the proximity sensor just refuses to do its thing. Guess I'll wait for Lollipop to see if that changes anything.

(Q) Wi-Fi switches off automatically when screen turns off

So I'm on 5.1 stock and this is really annoying me now. Wi-Fi switches off randomly when screen is off. Wi-Fi always on is checked. Any suggestions?
Sent from my XT1095 using XDA Free mobile app

Is the battery saver option turned on? If so is it starting up to save your battery and killing wifi?

I'm also having this problem. My wifi is configured to aways on, I'm not using any battery saver and even initialized my device in security mode, but the problem continued, so it is not a 3rd party program problem. I even posted on official Motorola forums (and on a lot forums through the internet), but no one could help. I guess it is a bug on 5.1 because I didn't have this problem on 5.0.
I installed a program to solve this problem, but it needs to keep running:
https://play.google.com/store/apps/details?id=com.roamingsoft.manager
Use the wifi repair option. This is the only way that I find to solve this problem. I hope they fix it on the next version.
Sorry for my english.

muiriddin said:
Is the battery saver option turned on? If so is it starting up to save your battery and killing wifi?
Click to expand...
Click to collapse
Nope. No battery saver mode.
Sent from my XT1095 using XDA Free mobile app

pulley06 said:
Nope. No battery saver mode.
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
I tried a few things to investigate this and without root on my device I'm potentially unable to get to logs that we could then compare. So since that approach didn't work, I have some environmental questions. Does the problem occur when you are carrying the phone in your pocket, or when it sits on a table unused for a period of time (or both). I'm trying to eliminate shaking causing the issue. You also mention that it happens with the screen off are you sure that it only occurs in that situation (that is a strange detail).

I can confirm this. It is as if the Wifi Always On setting did not work. When screen sleeps, 3G/LTE kicks in. When you wake the phone up, it'll go from 3G/LTE to Wifi. This has indeed arrived with 5.1, as 5.0 did not have the issue.

muiriddin said:
I tried a few things to investigate this and without root on my device I'm potentially unable to get to logs that we could then compare. So since that approach didn't work, I have some environmental questions. Does the problem occur when you are carrying the phone in your pocket, or when it sits on a table unused for a period of time (or both). I'm trying to eliminate shaking causing the issue. You also mention that it happens with the screen off are you sure that it only occurs in that situation (that is a strange detail).
Click to expand...
Click to collapse
Yeah it only occurs when the screen is off. The minute I switch on the screen I can see that it goes from mobile data to Wi-Fi even if Wi-Fi is on. Also, it is irrespective of where my phone is pocket or on a table top.
Sent from my XT1095 using XDA Free mobile app

I have a XT1094 (Moto X 2014) and have not noticed this. Based upon a post above you have the XT1095. We have the same Android version, just a different carrier version of the hardware. It sounds like when your device is going into one of the lower power states (the screen going off etc), the wireless is erroneously included in that transition. On my tablet I had a similar issue in that going to a lower power state would kill the sdcard which would then not properly reconnect when coming out of that lower power mode. If you prevented the tablet from going into that lower power state, the sdcard problem would not occur. Unfortunately the side effect was worse battery life in that case.
Do you have root on the device? If you do you might be able to do do a test similar to what I did on the tablet, however it would only prove the theory not solve the problem since worse battery life is an ugly trade off for a phone and the only way to actually change the sleep state transitions was to build a modified kernel that changed the sleep state itself (for my LG tablet one of the developers solved the issue and I just used the custom kernel provided)
Info on the "Sleep State" C-State is here https://plus.google.com/+PaulReioux/posts/9R8fjQdHDXD
For the tablet I had to disable the C3 (power collapse) sleep state, my post over there: http://forum.xda-developers.com/showpost.php?p=57719782&postcount=138
No idea if this will help...

I have an XT1095 stock 5.1 un-rooted, and I do not have this issue. I remember reading a similar thread here when 5.0 came out, so this is not a problem specific to 5.1. I don't know what is causing it, but it is clearly not a universal problem.

muiriddin said:
I have a XT1094 (Moto X 2014) and have not noticed this. Based upon a post above you have the XT1095. We have the same Android version, just a different carrier version of the hardware. It sounds like when your device is going into one of the lower power states (the screen going off etc), the wireless is erroneously included in that transition. On my tablet I had a similar issue in that going to a lower power state would kill the sdcard which would then not properly reconnect when coming out of that lower power mode. If you prevented the tablet from going into that lower power state, the sdcard problem would not occur. Unfortunately the side effect was worse battery life in that case.
Do you have root on the device? If you do you might be able to do do a test similar to what I did on the tablet, however it would only prove the theory not solve the problem since worse battery life is an ugly trade off for a phone and the only way to actually change the sleep state transitions was to build a modified kernel that changed the sleep state itself (for my LG tablet one of the developers solved the issue and I just used the custom kernel provided)
Info on the "Sleep State" C-State is here https://plus.google.com/+PaulReioux/posts/9R8fjQdHDXD
For the tablet I had to disable the C3 (power collapse) sleep state, my post over there: http://forum.xda-developers.com/showpost.php?p=57719782&postcount=138
No idea if this will help...
Click to expand...
Click to collapse
Don't have root. And have never rooted the device either. Somehow I'm just massively dissapointed with 5.1
Doesn't seem like a finished product at all. Battery life has plummeted from 3.5-4 hours sot easily to barely making it 3 hours
Sent from my XT1095 using XDA Free mobile app

Had this problem suddenly in 5.0 and continued in 5.1, the only fix was back to 4.4.4.
This has been posted before.
http://forum.xda-developers.com/mot...d-5-1-bugs-t3075232/post61724472#post61724472
http://forum.xda-developers.com/moto-x-2014/help/wifi-off-phone-idle-sleeping-t3053603

Here is the link to Motorola Forums that I've posted:
forums.motorola.com/posts/791e7e30c7
Hopefully this bug gets fixed in Android M.

Same problem that I'm getting. I'm sending mine back to Motorola and you guys can try that too to see if they can fix it. Apparently there's a speical dedicated team working on Moto X faults in Germany.

Anybody have any news?
Is there a way to fix this problem without going back to 4.4.4?