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
Given some of the issues I've seen listed regarding 4.4 on the Moto X, I've decided to wait until a point kitkat release comes out before going there (also if I decide to unlock/root, 4.2.2 is a better place to be). The only issue with waiting is the nag screen which comes up asking to update, and if you say no, you have to input a time for the next nag to appear. This is a T-Mobile version. Is there any simple way to have it stop asking to update?
larry62 said:
Given some of the issues I've seen listed regarding 4.4 on the Moto X, I've decided to wait until a point kitkat release comes out before going there (also if I decide to unlock/root, 4.2.2 is a better place to be). The only issue with waiting is the nag screen which comes up asking to update, and if you say no, you have to input a time for the next nag to appear. This is a T-Mobile version. Is there any simple way to have it stop asking to update?
Click to expand...
Click to collapse
Try disabling Moto OTA under apps.
larry62 said:
Given some of the issues I've seen listed regarding 4.4 on the Moto X
Click to expand...
Click to collapse
What issues?
Disabling the OTA doesn't seem to prevent the nag for me. Is it done by force stop or some other method?
Sent from my XT1053 using Tapatalk
elijahah said:
Try disabling Moto OTA under apps.
Click to expand...
Click to collapse
Same here. You can force stop it, but it restarts on it's own even without a reboot. Just gotta live with it as a daily nuisance.
What problems with 4.4? Some of the bugs are talked about across this forum. Things like USB OTG (at least file viewing; haven't tested other functions yet), and some issues supporting the ATT NVMO AIO come to mind. I'd just assume wait for 4.4.x where x>=2 and see if some of the bugs get worked out.
Would there be something that can be uninstalled or freezed with Titanium Backup to stop the nag?
I froze it with TB and it stopped the messages.
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've noticed it takes my N6 a few seconds after the phone buzz/sound alerts me I have a new notification before the ambient display comes on. This has been happening since I got the 5.1 update a week or so ago. Previously, it came on very quickly. Almost simultaneously with the sound/buzz notification. Anyone else experience this?
Update to 5.1.1 this has been fixed
stas333 said:
Update to 5.1.1 this has been fixed
Click to expand...
Click to collapse
Thanks, that's good to know. I'm completely locked and not rooted so will just wait for 5.1.1 to get pushed to Verizon phones.
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