According to some sources,
Nexus 6 will feature "Ambient Display" which is supposed to be the Lollipop equivalent of Active Display / Moto Display.
According to this website though (bgr.com/2014/10/21/android-5-0-features-ambient-display-moto-x/) this will be a feature not exclusive to the Nexus 6, but rather Lollipop itself.
Given that most Moto X users (me included) do not switch to AOSP or CM-based ROMs because of the Active Display, does this mean we can now use the Active Display feature directly from vanilla Android? Or will we still be limited to the proprietary Motorola software?
I don't know much about how Active Display works, and how much is software and how much is hardware dependent. I was hoping somebody more "dev-like" can clarify if the Moto X (2013) have any chance of using Ambient Display natively.
Thanks!
It's early, but at a minimum, it looks like the following Moto X features are coming to stock Android as of 5.0 (and some of these aren't on the Moto X 2014 due to the expected quick update):
Active Display/Moto Display (called Ambient Display)
Always on hotword detection (without the word customization of the 2014 Moto X)
Bluetooth Trusted Devices
Battery Saving Mode (it's implemented the same exact way)
Moto Assist (so far, only the quiet hours for notifications has been shown)
So my guess is that if you use an AOSP-based ROM, you'll get the feature. However, it is likely going to be a little different than the Motorola implementation. So, I'm curious, will Motorola now remove some of these features, or will they leave them in as alternatives (and thus, do what Samsung is doing)? If The AOSP versions are good enough, I may seek to entirely disable Motorola's implementations.
Also, keep in mind that Google's Ambient Display does supposedly offer a knock-code option, which the Moto X currently lacks.
Let's see how all those features are on battery life tho... Something that's not much of an issue with those features on the X.
Even just OK Google everywhere on other devices is fairly battery hungry. Specifically witnessed it on the N5.
Just cause they add a generic any phone feature, doesn't mean it will be very thought out.
KJ said:
Let's see how all those features are on battery life tho... Something that's not much of an issue with those features on the X.
Even just OK Google everywhere on other devices is fairly battery hungry. Specifically witnessed it on the N5.
Just cause they add a generic any phone feature, doesn't mean it will be very thought out.
Click to expand...
Click to collapse
I think that Google has accounted for this as best they can. They've stated that certain features either won't work or aren't recommended for specific types of devices. It seems their Ambient Display, for example, is intended to function like the Moto X on OLED displays, while using the more genetic "knock to turn on" gesture for LCD displays (though configurable for a user who doesn't mind destroying battery life).
They've also come out and said that the always-on Google Now requires a specific co-processor and will not function without it. Whereas most ugly implementations keep the phone's CPU in "wake," The Motorola implementation does not, and it seems that Google intends to mirror this.
Now that we know that Google's own Ambient Display is in some way better than Moto's, although some will question if there any advantages at all, I wonder if Moto will revamp their version in 5.0 to display the entire lock screen in black and white. The downside of Google's version is that as soon as you interact with the screen, the screen resorts to all colors consuming more battery.
It would be great to get the best of worlds - being able to see the entire lock screen AND be able to read the contents of the notification without in effect turning on the device.
Does Google's ambient display light up when we pick up the phone as in Moto X? If yes then bye bye stock :fingers-crossed:
DaRkRhiNe said:
Does Googles ambient display light up when we pick up the phone as in Moto X? If yes then bye bye stock :fingers-crossed:
Click to expand...
Click to collapse
Yes. It lights up when you pick it up and also apparently flashes every 10 secs when still. What do you mean be bye bye stock.
floepie said:
Yes. It lights up when you pick it up and also apparently flashes every 10 secs when still. What do you mean be bye bye stock.
Click to expand...
Click to collapse
The only thing stopping me from flashing a Rom is AC display of Moto X.
DaRkRhiNe said:
The only thing stopping me from flashing a Rom is AC display of Moto X.
Click to expand...
Click to collapse
This was in a moto changelog for 2014 moto x, unfortunately the post has been pulled but it shows how they will be dealing with ambient display.
While your phone’s display is off, Moto Display will continue to surface relevant notifications to
you using the low-
power Contextual Computing Processor. It will also intelligently react when you use the Approach
gesture under Moto Actions.
Android Lollipop now includes a similar feature, called Ambient Display, that displays
notifications like those shown on the lockscreen. If you prefer to try the new Ambient Display
feature, you can uncheck the Moto Display setting in the Moto app. Note: Ambient Display does not
use Motorola’s low-power core and will turn on more of the
display, so battery life may be impacted. The Moto Actions Approach gesture will not wake Ambient
Display.
adm1jtg said:
This was in a moto changelog for 2014 moto x, unfortunately the post has been pulled but it shows how they will be dealing with ambient display.
While your phone’s display is off, Moto Display will continue to surface relevant notifications to
you using the low-
power Contextual Computing Processor. It will also intelligently react when you use the Approach
gesture under Moto Actions.
Android Lollipop now includes a similar feature, called Ambient Display, that displays
notifications like those shown on the lockscreen. If you prefer to try the new Ambient Display
feature, you can uncheck the Moto Display setting in the Moto app. Note: Ambient Display does not
use Motorola’s low-power core and will turn on more of the
display, so battery life may be impacted. The Moto Actions Approach gesture will not wake Ambient
Display.
Click to expand...
Click to collapse
Interesting. Does the rest of this log still live somewhere? I wonder if Ambient Display does in fact use some sort of low-power core on the Nexus 6. I can also imagine that if you choose to use A.D., that simply flashing of pixels on such an amoled wouldn't result in much of a perceived battery hit compared to Moto Display.
All of the Snapdragon 800s have the low-power core built into the SoC which is why Moto didn't go with a custom SoC in the new Moto X.
nhizzat said:
All of the Snapdragon 800s have the low-power core built into the SoC which is why Moto didn't go with a custom SoC in the new Moto X.
Click to expand...
Click to collapse
This is actually incorrect (no offense).
The Snapdragon 800 SOC does support always on listening, but it doesn't do so with the main SOC asleep. This means that the battery consumption isn't as low as the method employed by the Moto X. Motorola's own spec sheets reveal that the two specialized lower-power chips used in the Moto X 2013 are still used in the 2014.
Motorola link: https://www.motorola.com/us/motomaker?pid=FLEXR2
Motorola Mobile Computing System including 2.5GHz Qualcomm® SnapdragonTM 801 with quad-core CPU (MSM 8974-AC), Adreno 330 @ 578 MHz GPU, Natural Language Processor, Contextual Computing Processor
Click to expand...
Click to collapse
Although it is for 2014 version but still since some of the h/w is same. I think, this will help answer some of the lollipop questions for our X.
Lollipop Release notes for Moto X(2014)
Ambient Display doesn't make use of the dedicated low-power sensor Moto Display uses in the Moto X 2013 and 2014. It is also a lot less reliable.
Related
Will the nexus 6 have wave-to-wake feature like the Moto X 2014?
If not by default then is it possible that it can have this feature in future by any means??
No, it does not have it by default.
There are apps that can use the proximity sensor with older phones to wake it up, so I imagine that at some point, yes, it will be possible to replicate the Moto X wave-to-wake feature via app.
jt3 said:
No, it does not have it by default.
There are apps that can use the proximity sensor with older phones to wake it up, so I imagine that at some point, yes, it will be possible to replicate the Moto X wave-to-wake feature via app.
Click to expand...
Click to collapse
Ok.. I hope it does happen...
I use this this feature frequently on my Moto X 2014. I will definitely miss it if I get a N6.
Here's the app I use on my Nexus 5. Assuming there aren't any issues running it under Lollipop, it has a setting that wake the phone with a wave. However, I'm not sure whether it will FULLY wake the phone, or let you just activate Ambient Screen. Maybe contacting the dev, and requesting an Ambient Screen setting would help.
Gravity Screen - On/Off
It wont by default - it is a moto specific software feature.
Begging or hoping it is added will do nothing, as the nexus is from google OS wise, and moto hasn't added that specific software (or hardware, see below) to it like the moto X.
Your best hope is 3rd party app that can give that capability, however that said, the phone would have to have the IR sensors like the X in order to detect the handwaving, which AFAIK it doesn't have.
Is this the same feature found in the note 2?
RW-1 said:
...the phone would have to have the IR sensors like the X in order to detect the handwaving, which AFAIK it doesn't have.
Click to expand...
Click to collapse
All modern smart phones have proximity sensors though, and third-party developers have tapped into those. The trick isn't the detection, it's the activation of Ambient Screen without fully waking the phone.
For instance, the Gravity Screen app I posted earlier will wake my N5 with a wave over the screen just perfectly, but it FULLY wakes the device. If they can alter that to give the option of waking the device, or only activating Ambient Screen, then it would almost perfectly emulate the Moto function.
Deciding between the Moto X 2014 and the Nexus 6. I have a preference for the larger screen of the Nexus 6, but also like the idea of the Motorola Value Added Software (Touchless, Car Mode, Moto Voice, etc). Nexus 6 doesn't run this software. Looking for current Moto X 2014 owners to give me their impression of how important/useful the Motorola Suite of Value Added Software is, and how much weight I should give to this in my comparison/decision.
I know we will be a little biased, but you will get a near nexus/stock android experience on the moto X plus the extra useful features that are exclusive to moto devices. The active display notifications and touchless commands really make this a stellar device along with more than sufficient hardware.
The Active Display is great, I use it all the time. Even after the L update I disabled Google's new lock screen to use it instead. It's not as nice looking but the battery savings and ability to see notifications without touching the screen are great, plus it pretty much negates the entire need for the power button to wake it which is really convenient.
Not all of the features are quite as useful as that but I'm glad they're there. The car mode is cool if I get a text while driving as it reads it aloud without me needing to touch it.
moto display is just simply awesome, it's basically life changing from previous 2 phones past couple years:
iphone 4: had to press home button every time just to see if any notification(even jb and put on notification bar app with cydia)
moto g: light was on but i didn't know if it was email or actual text etc, so i still had to click the rocker or pick it up(gravity screen/xposed mod to get these, otherwise pressing power button again)(get like 20 email/day i just simply ignore most and just check once a day at the most)
now Moto x: just wave it or move my phone and see any messaging/call i miss
moto voice: i drive 10+hrs a week routinely and too lazy to put on music sometimes and just listen to musics on radio. I would call on the phone and just ask what music it is and pick it up later when i get back home etc. Without reaching my hand to phone feels alot safer. Send message with whatsapp needs a little simplified as reply or something to get it a little more useful
moto assist: text reading is not bad but i wish they do the same to fb messenger and whatsapp as well, that would be awesome
Active Display its godlike, i love that i just need to pass my hand over my phone to see notifications.
As first i didnt think i would use Voice Controls that much, but there are some situations when its just soo good. Driving, setting up alarms when on bed, etc...
Not to mention the hardware its pretty much top of the line, and the build quality too
But its the extra features that are the highlight of the phone, and what mskes it stand out of the oh so typical high end device
I bought the moto x for it voice control eventhough it isn't available in my language but it is very useful driving
Moto suite is the only reason I'm going to keep my Moto X and pass on the N6. It's that important to me. It changes how I use a phone now and I know I would miss it if I didn't have it. The first time you're in the shower and a phone call or a text comes in and you can have a full conversation with either without having to touch your phone. It's incredible.
Looks like most (so far) find these features more useful than I first thought. Special thanks to those who are putting in detailed impressions (I just pressed the "Thanks Button" for you ). Any further impressions are deeply appreciated!
If the moto specific features are the only thing holding you back from getting a Nexus 6, then go for the nexus 6 you won't miss them all that much as the nexus 6 now has some sort of replacement features via ambient display and always on google now.
I got the moto x considering its price, size and the extra features, fast updates. But in your case I'd recommend the N6 if the price and size aren't a problem
Hi!
Our hammerhead currently lacks full support for ambient display in Android L. One+1 has the kernel changes we need already merged(https://github.com/CyanogenMod/andr...mmit/735f665d2f5dd350b92cffae26517ed494760b5f). I checked this patch before - it's not a match to our source, it needs some more merges in video drivers. I was just wondering if anyone on XDA tried to get this working and wanted to share progress and experiences with doze mode on 3.4 msm kernel?
Mike
mikegapinski said:
Hi!
Our hammerhead currently lacks full support for ambient display in Android L. One+1 has the kernel changes we need already merged(https://github.com/CyanogenMod/andr...mmit/735f665d2f5dd350b92cffae26517ed494760b5f). I checked this patch before - it's not a match to our source, it needs some more merges in video drivers. I was just wondering if anyone on XDA tried to get this working and wanted to share progress and experiences with doze mode on 3.4 msm kernel?
Mike
Click to expand...
Click to collapse
but does our panel really supports that mode?, i remember people thinkering with the digitizer to get the double tap to wake like on the g2 (Without bat drain) and they got nowhere
The panel itself works fine, we are missing one feature only - enabling ambient display afer device is picked up, it needs to be ported to our kernel and sensors hal I guess.
We have a IPS LCD display, using Ambient display will suck a lot of battery juice :/
DJBhardwaj said:
We have a IPS LCD display, using Ambient display will suck a lot of battery juice :/
Click to expand...
Click to collapse
IPS doesn't mean its gonna suck battery. Nokia did it on IPS before.
http://allaboutwindowsphone.com/features/item/18191_Nokia_works_a_LCD_miracle-Glan.php
The topic to be discussed here anyway isn't the screen type or its flaws. It is to get sensors to be able to wake the device with ambient display enabled.
akash3656 said:
IPS doesn't mean its gonna suck battery. Nokia did it on IPS before.
http://allaboutwindowsphone.com/features/item/18191_Nokia_works_a_LCD_miracle-Glan.php
The topic to be discussed here anyway isn't the screen type or its flaws. It is to get sensors to be able to wake the device with ambient display enabled.
Click to expand...
Click to collapse
Everyone's got their choice. I had my opinion laid.
how about applying the patch to cm kernel instead of stock, since it uses updated video drivers and such? is a no-go still?
opssemnik said:
how about applying the patch to cm kernel instead of stock, since it uses updated video drivers and such? is a no-go still?
Click to expand...
Click to collapse
It's included in CM12-CAF build, however we still don't have support for waking the screen after the device is picked up.
mikegapinski said:
It's included in CM12-CAF build, however we still don't have support for waking the screen after the device is picked up.
Click to expand...
Click to collapse
If I recall we had the option on some custom roms (4.4.4) to wake the screen when the device was picked up. I think it used the proximity sensor to detect when the device was picked up.
edit- I apologize, I just realized that this was for developers only.
@mikegapinski Any progress on this or is it abandoned? I'm really looking forward to using full ambient display on hammerhead if it's even possible.
Thanks!
You'd need over 750 patches in the graphics subsystem of the kernel before you can start applying relevant doze patches. Plus updated gpu kernel drivers etc etc
We'll have this on an additional nightly CM12 build eventually and it works pretty good. The only drawbacks at the moment are the situation where sometimes the pick-up sensor is triggered and enables the short wake-up effect; this is because we use a sensor blob from bacon. Then, in order to have a reliable pick-up, that always works, I abused the tilt sensor with some fixed parameters, which is wakeup capable. This however leads to a tad too long timespan from actual pick-up to showing the message on the display.
Whatever, take it or leave it.
myfluxi said:
You'd need over 750 patches in the graphics subsystem of the kernel before you can start applying relevant doze patches. Plus updated gpu kernel drivers etc etc
We'll have this on an additional nightly CM12 build eventually and it works pretty good. The only drawbacks at the moment are the situation where sometimes the pick-up sensor is triggered and enables the short wake-up effect; this is because we use a sensor blob from bacon. Then, in order to have a reliable pick-up, that always works, I abused the tilt sensor with some fixed parameters, which is wakeup capable. This however leads to a tad too long timespan from actual pick-up to showing the message on the display.
Whatever, take it or leave it.
Click to expand...
Click to collapse
Is this available fully implemented in any build?
Sent from my Nexus 5 using Tapatalk
akash3656 said:
IPS doesn't mean its gonna suck battery. Nokia did it on IPS before.
http://allaboutwindowsphone.com/features/item/18191_Nokia_works_a_LCD_miracle-Glan.php
The topic to be discussed here anyway isn't the screen type or its flaws. It is to get sensors to be able to wake the device with ambient display enabled.
Click to expand...
Click to collapse
Sorry for reviving this thread, but it IS about the display type. Not the AMOLED vs. LCD part, but if the display module actually incorporates Display Memory - which is a key in low-power Ambient Display options.
What Nokia/MS did is basically using DM with a simple script that moves the content around. It is low power, and as the phone does not need to be awake, power drainage is lowered even further.
Updates are ran by a background service that collects relevant notifications (the 6 lock screen notifications, the big lock screen info + current date/time), and on the exact minute, updates the DM. It results in a less than 1000ms wakelock, and does not keep the device awake.
I highly doubt that many Android phones would come with Display Memory enabled displays - it is simply not worth it financially, and would be mainly useless. So we cannot really reach the whole Nokia-level low power usage, though we can try.
MemoryController said:
Is this available fully implemented in any build?
Click to expand...
Click to collapse
CM 12.x hammerheadcaf
Looking on youtube I found this video about the hand over function on moto x being disabled on lollipop. Is that true? There are english captions on the video.
It was changed so that now you have to hold your hand over it for a few seconds.
It can be returned.. But not the same as on 444
Or you can just import profile and task to Tasker from attachments.
Also i write instruction for it (but on Russian lang)
The entire reason it was changed was because the device was supposed to know when it was being turned over, or removed from your pocket, with he Nudge To Wake feature being used for when it's on a tabletop.
It never was a feature to begin with, it was a bug due to an overly sensitive proximity sensor that began when they released 4.4.4. (It did not exist in 4.2, or 4.4)
The original intent was to detect when the phone is removed from your pocket or flipped over (when laying face down) Nowhere did Motorola list this as a feature on the original Moto X.
This was a feature added to the Moto X2, because the Moto X2 has IR sensors on the front that the original Moto X does not have.
It now works as intended.
Just curious why someone hasn't been able to rip the Active Display or Moto Actions software/code and reproduce it as an xposed module that can be used on other phones. I get that battery drain might be an issue on phones that don't have a secondary processor for handling gestures/movement/etc... but at least to have the option to try it out would be nice?
Is there some reason this hasn't been done successfully?
I'm also very interested in this. AC Display is a good enough replacement for Moto Display, but what about Moto Voice? Only Samsung, LG, Moto, and Nexus seem to have an always on OK Google function (meaning that it works even with the screen off). I would pay for an Xposed module that enabled this on other phones.