So Nexus 6 DID HAVE double tap to wake - Google axed it

[Lloydbm41]

Google seems to be sandboxing more features and limiting user options these days. I brought up a few times in other threads that it made no sense why the DT2W feature wasn't added to the Nexus 6, since it is just a few lines of code in the Kernel. And Google already had this feature in the Nexus 9.

Commits now show that the Nexus 6 did have the code and Google axed it in favor of active display a la Moto X. I can understand if Google only went down this one route of using active display, but DT2W is a simple add on that required no additional work. Why not give the user the option to use both or one over the other?

Sometimes I have to wonder why Google does some asinine things?

link: http://www.androidpolice.com/2014/1...-to-wake-functionality-but-google-removed-it/

 

[Dontazemebro]

Google is becoming more and more like Apple with each OS iteration. And on the flip side, Apple is pulling an Android adding features left and right.

The world is definitely coming to an end.

 

[tbayrgs]

Google seems to be sandboxing more features and limiting user options these days. I brought up a few times in other threads that it made no sense why the DT2W feature wasn't added to the Nexus 6, since it is just a few lines of code in the Kernel. And Google already had this feature in the Nexus 9.

Commits now show that the Nexus 6 did have the code and Google axed it in favor of active display a la Moto X. I can understand if Google only went down this one route of using active display, but DT2W is a simple add on that required no additional work. Why not give the user the option to use both or one over the other?

Sometimes I have to wonder why Google does some asinine things?

link: http://www.androidpolice.com/2014/1...-to-wake-functionality-but-google-removed-it/

Maybe to keep some differentiation between its own devices and those of it's partners? Don't want to step on toes by aping the same functionality--just a thought.

 

[Lloydbm41]

Maybe to keep some differentiation between its own devices and those of it's partners? Don't want to step on toes by aping the same functionality--just a thought.

Nokia has DT2W on several of the Lumia's and tons of ROMs use it too.
It would seem to me that Google would want similar functionality between all its Nexus devices, not less? but who knows. Just kinda sucks that they are moving to lessen user options.

 

[jamezr]

Google seems to be sandboxing more features and limiting user options these days. I brought up a few times in other threads that it made no sense why the DT2W feature wasn't added to the Nexus 6, since it is just a few lines of code in the Kernel. And Google already had this feature in the Nexus 9.

Commits now show that the Nexus 6 did have the code and Google axed it in favor of active display a la Moto X. I can understand if Google only went down this one route of using active display, but DT2W is a simple add on that required no additional work. Why not give the user the option to use both or one over the other?

Sometimes I have to wonder why Google does some asinine things?

link: http://www.androidpolice.com/2014/1...-to-wake-functionality-but-google-removed-it/

Mine will be here Thursday so we will find out soon. But this article says it have DT2W but they are older articles from the end of October.


I am curious though. Why do you need DT2W if the N6 has Active Display like the Moto X? So the screen will display the notifications and can be turned on with the same effort? Plus always on voice control......

http://www.wired.com/2014/10/hands-on-with-lollipop-and-nexus/

http://phandroid.com/2014/10/23/the-nexus-6-will-come-with-tap-to-wake-so-you-dont-have-to-reach-for-the-power-button/

This too....

http://www.ubergizmo.com/2014/10/nexus-6-confirmed-to-have-double-tap-to-wake-feature/

 

[TimelessOne]

My guess is it had something to do with battery life and it being hurt on the Nexus 6. Like it pulled to much juice on that device to pull it off.

 

[Lloydbm41]

My guess is it had something to do with battery life and it being hurt on the Nexus 6. Like it pulled to much juice on that device to pull it off.

DT2W more drain than active display? That's a question I wouldn't mind getting answered from Google.

 

[Fireblade]

My guess is it had something to do with battery life and it being hurt on the Nexus 6. Like it pulled to much juice on that device to pull it off.

Don't think so, if it's implemented in the kernel, the battery drainage is absolutely negligible.
Having and using this awesome feature often during the day on my G2, still getting awesome battery life.

 

[mattopotamus]

Not really related to the nexus 6, but I thought the nexus 5 would get the active display style notifications. I thought it was a feature baked into lollipop.

 

[diamond.g]

Not really related to the nexus 6, but I thought the nexus 5 would get the active display style notifications. I thought it was a feature baked into lollipop.

Are you referring to the black and white notifications on the screen when the screen isn't in active use?

 

[SurferMan]

Yeah double tap was the one standout feature I really liked about the N9. I know there are some apps but it's not the same, if I remember it's baked into the kernel hence why us Sammy users are screwed since we can't mess with the kernel anymore as devs on xda tried. I think Sony and others have implemented this too?

 

[mattopotamus]

Are you referring to the black and white notifications on the screen when the screen isn't in active use?

yes, the pulsing of that screen