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
Related
Hi everyone
I have the phrase set to OK Google Now.
When the phone is locked, screen off or even on moto display, quite a lot of the time saying the launch phrase will do nothing. When I unlock the phone it works perfectly fine. Then when I lock it, it works for a while but then after a bit it stops working until I unlock it again.
Is this some kind of bug that any of you have experienced also?
it kinda happens for me too. Even when it does get it, some commands are almost unusable. it just redirects to google search. is your phone a US one?
Moto XT1097 for the win
No I bought mine from Moto Maker in the UK. Hopefully it should be fixed in the next update.
raze599 said:
Hi everyone
I have the phrase set to OK Google Now.
When the phone is locked, screen off or even on moto display, quite a lot of the time saying the launch phrase will do nothing. When I unlock the phone it works perfectly fine. Then when I lock it, it works for a while but then after a bit it stops working until I unlock it again.
Is this some kind of bug that any of you have experienced also?
Click to expand...
Click to collapse
The Moto X unlike the regular Ok Google which is available on all phones, is not only listening for the words to activate but also processes it to make sure its a close match to the voice used during the initial training setup. Try rerunning the voice training and record your voice without any accent, try speak casually the way you normally do trying to wake up your moto x. This should help
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..
I'm not sure if this is happening on other devices. My Moto X (2013) running 4.4.2 (I am on Republic Wireless) started doing something funny about a week ago. Randomly, I'll unlock my screen to see that any and all text within Google Now Launcher is blurred out. The only way I've been able to fix it is by resetting the device. Clearing cache doesn't work for me. I suppose I could try uninstalling and reinstalling, but I'm not sure if that would really fix an underlying problem if there is one. Does anyone have any ideas?
I had this happen to me one day in an app.. I think it was Reddit Is Fun or Fenix (Twitter). I don't think it happened when I was unlocking the screen, I was already in the app and using it. The screen may have timed out and I unlocked back to it with that app already open, but I distinctly remember the blocky letters on the entire screen, and I could still scroll and stuff. I think I might have pressed Home and my home screen icons had the labels like that too, so I just rebooted and it went away.
I do not use GEL, so I don't think it's related to that. It happened once, I rebooted my phone and it never came back.
I am on stock 4.4.4 XT1060.
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.
Hey guys,
Since upgrading to LP 5.1 I've been not that happy really. Some minor bugs, a lot of RAM consumed by the system and, of course, the lack of the wave to wake option.
Now, I have just discovered another "change" (a bit late, I know) in the Active display behavior. When I had KK and I had AD notifications blinking, they will blink forever (even tho, they started to blink with more gap between as time passed)... Now I noticed that AD notifications with LP 5.1 blinks for a limited period of time (don't know which one yet), and then stops doing it, leaving the screen totally black and without knowin I have a notif pending unless I take my phone.
Anyone noticed this change of behavior too ?
34 views and no one could notice this behavior ? I must assume you guys don't stay more than 5/10 minutes without receiving a new notification.
I think it has to do with what version of Android you were running prior to upgrading to LP. I say this because I flashed to an AOSP 5.1.1 ROM and not only is my wave to wake still working, wrist twists launches the camera app. The OS before was 4.4.4 SU4.21. But the ambient display would flash on and off for a long time when I receive a notification, don't know about forever since I would check the notification with the hand wave gesture oh and I get the green LED after a while also.... Perhaps after it gets sick of flashing the AD notification?
Sent from my DROID MAXX using Tapatalk
Johnny Wong said:
I think it has to do with what version of Android you were running prior to upgrading to LP. I say this because I flashed to an AOSP 5.1.1 ROM and not only is my wave to wake still working, wrist twists launches the camera app. The OS before was 4.4.4 SU4.21. But the ambient display would flash on and off for a long time when I receive a notification, don't know about forever since I would check the notification with the hand wave gesture oh and I get the green LED after a while also.... Perhaps after it gets sick of flashing the AD notification?
Sent from my DROID MAXX using Tapatalk
Click to expand...
Click to collapse
You flashed a 5.1.1 LP to your X 2013 ? How did you do that ? The latest (and only) LP for our X is 5.1
Emiliano55 said:
You flashed a 5.1.1 LP to your X 2013 ? How did you do that ? The latest (and only) LP for our X is 5.1
Click to expand...
Click to collapse
I have a XT1060 DE and got sick of waiting for Verizon so I flashed one of the ROMs in the forum. http://forum.xda-developers.com/showthread.php?t=3116436
Sent from my DROID MAXX using Tapatalk
Johnny Wong said:
I think it has to do with what version of Android you were running prior to upgrading to LP. I say this because I flashed to an AOSP 5.1.1 ROM and not only is my wave to wake still working, wrist twists launches the camera app. The OS before was 4.4.4 SU4.21. But the ambient display would flash on and off for a long time when I receive a notification, don't know about forever since I would check the notification with the hand wave gesture oh and I get the green LED after a while also.... Perhaps after it gets sick of flashing the AD notification?
Sent from my DROID MAXX using Tapatalk
Click to expand...
Click to collapse
Doesn't have anything to do with what version of Android you were running prior to upgrading. Your wave to wake, wrist twist to launch camera, and ambient display (plus the green LED notification) are part of the AOSP rom you installed. Those features work pretty great on the moto x. But he's on stock, which is quite different (ambient display vs active display)
I've tried AOSP roms and now running a stock 5.1 rom. Active display does behave differently than it did on 4.4.4. The notifications stop flashing after a while and the wave to wake doesn't work. But the wave to wake was actually a bug, not an advertised feature, hence why it was removed.
oeusr said:
Doesn't have anything to do with what version of Android you were running prior to upgrading. Your wave to wake, wrist twist to launch camera, and ambient display (plus the green LED notification) are part of the AOSP rom you installed. Those features work pretty great on the moto x. But he's on stock, which is quite different (ambient display vs active display)
I've tried AOSP roms and now running a stock 5.1 rom. Active display does behave differently than it did on 4.4.4. The notifications stop flashing after a while and the wave to wake doesn't work. But the wave to wake was actually a bug, not an advertised feature, hence why it was removed.
Click to expand...
Click to collapse
Understood, however, I was wondering why so many people are having issues with 5.1 and I'm not. So I went outside the box and came up with that theory.
Since you are on stock 5.1, have you tried installing Moto app? https://m.reddit.com/r/MotoX/comments/3anh0n/2013_so_i_figured_out_how_to_get_the_chop_chop/ You'll get hand wave as well as the new chop gesture for flashlight.
Sent from my DROID MAXX using Tapatalk
Johnny Wong said:
Understood, however, I was wondering why so many people are having issues with 5.1 and I'm not. So I went outside the box and came up with that theory.
Since you are on stock 5.1, have you tried installing Moto app? https://m.reddit.com/r/MotoX/comments/3anh0n/2013_so_i_figured_out_how_to_get_the_chop_chop/ You'll get hand wave as well as the new chop gesture for flashlight.
Sent from my DROID MAXX using Tapatalk
Click to expand...
Click to collapse
I have that feature already in the stock rom I use (the only stock 5.1 in the development forum) and it works really well!
Sent from my XT1053 using XDA Free mobile app
oeusr said:
Doesn't have anything to do with what version of Android you were running prior to upgrading. Your wave to wake, wrist twist to launch camera, and ambient display (plus the green LED notification) are part of the AOSP rom you installed. Those features work pretty great on the moto x. But he's on stock, which is quite different (ambient display vs active display)
I've tried AOSP roms and now running a stock 5.1 rom. Active display does behave differently than it did on 4.4.4. The notifications stop flashing after a while and the wave to wake doesn't work. But the wave to wake was actually a bug, not an advertised feature, hence why it was removed.
Click to expand...
Click to collapse
I'm glad someone finally answer my question. So I'm not the only one that noticed this about AD notifications. On 4.4 they blinked forever, now they blink for a short period of time (unless, of course, you get ANOTHER notification and the timer will reset).
It's a shame how Active display behavior has suffered with the Lolli update. First the wave to wake, now this. I'm surprised so few people noticed this also, maybe people get notifications every time, lol
Emiliano55 said:
I'm glad someone finally answer my question. So I'm not the only one that noticed this about AD notifications. On 4.4 they blinked forever, now they blink for a short period of time (unless, of course, you get ANOTHER notification and the timer will reset).
It's a shame how Active display behavior has suffered with the Lolli update. First the wave to wake, now this. I'm surprised so few people noticed this also, maybe people get notifications every time, lol
Click to expand...
Click to collapse
Did you consider that most ppl don't rely on AD and just pick up their phones, unlock them and see all their notifications?
Just imagine
liveroy said:
Did you consider that most ppl don't rely on AD and just pick up their phones, unlock them and see all their notifications?
Just imagine
Click to expand...
Click to collapse
Yeah, I tend to think people really rely on AD, and they use it. Truth is people doesn't notice this features, they just grab their phones and use it, without noticing a lot of things/features/bugs.
Emiliano55 said:
Yeah, I tend to think people really rely on AD, and they use it. Truth is people doesn't notice this features, they just grab their phones and use it, without noticing a lot of things/features/bugs.
Click to expand...
Click to collapse
Yep, exactly.By the way I also didnt notice that bug or if its feature (dunno).Just didn't have notifications that I didn't see for long enough I guess