Database Develop

N5 getting Moto X always listening feature in future update?

from this article by the verge, it seems like n5 will get an update that will add always listening feature in mid november? or am i understanding this article incorrectly given that it's true?
LINK

envizion58 said:
from this article by the verge, it seems like n5 will get an update that will add always listening feature in mid november? or am i understanding this article incorrectly given that it's true?
[URL="
Click to expand...
Click to collapse
I was under the impression that the N5 had this out of the box...

Reading the comments, opinion seems divided. I thought it wouldn't be able to cos of different processor.
Also, I think the update he's referring to is the update that happened last week with launch of 4.4.

That does seem to be what the article is saying:
Speech recognition is receiving some upgrades as well. With the update you'll be able to wake up your Nexus 5 and search just by saying "OK, Google," like on the Moto X.
Click to expand...
Click to collapse
I would take it with a grain of salt, however.

n5's listening mode currently only works in homescreen unlike the moto x. it doesn't work through sleep or lockscreen.

SkuzeeII said:
I was under the impression that the N5 had this out of the box...
Click to expand...
Click to collapse
Nope. If you're on the homescreen you can "OK Google" to start a search but it won't do it if the screen is off like the Moto X.

the verge has a pretty good track record and honestly with the hardware ability to do this function its a no brainer that it will be altered in the future

MaxCarnage said:
That does seem to be what the article is saying:
I would take it with a grain of salt, however.
Click to expand...
Click to collapse
Me too, because the article is about Android Kitkat, not the Nexus 5 specifically. And we know that a dedicated chip is required to have this wakup by voice function (otherwise the phone will not be able to enter deep sleep). So if it were true, the article would have mentioned that the chip is present.
Therefore the article quote should be read this way in my opinion:
With the update you'll be able to (manually) wake up your Nexus 5 and (then) search just by saying "OK, Google," like on the Moto X.
Click to expand...
Click to collapse

i read conflicting info on n5's hardware capability to imitate moto x's always listening feature. i know the snapdragon 800 has a mini coprocessor of some sort that allows always listening, but i also read somewhere that its a bit different from the dedicated low power core moto x has. regardless , i hope it's true. i was swaying toward moto x for a bit before committing to n5 cause of this feature.

envizion58 said:
i read conflicting info on n5's hardware capability to imitate moto x's always listening feature. i know the snapdragon 800 has a mini coprocessor of some sort that allows always listening, but i also read somewhere that its a bit different from the dedicated low power core moto x has. regardless , i hope it's true. i was swaying toward moto x for a bit before committing to n5 cause of this feature.
Click to expand...
Click to collapse
It is different because it's backed into Snapdragon here, but it's exactly the needed thing. Samsung took advantage of it in Note 3. You can wake it up by saying "Hi Galaxy".

All qualcomm s800 cpu has this chip built in
Sent from my LG-D802 using Tapatalk

The Snapdragon 800 is indeed complatible with Always-on recognition. It's even on their site.
http://www.qualcomm.com/snapdragon/processors/800

rokfor2000 said:
It is different because it's backed into Snapdragon here, but it's exactly the needed thing. Samsung took advantage of it in Note 3. You can wake it up by saying "Hi Galaxy".
Click to expand...
Click to collapse
This.
Technically it's not a separate core, but rather one of the cores runs at a low speed when doing mundane tasks. This *does* work with the screen powered off, which is how the Note 3 can be awoken with voice.

I would imagine it will get added with an option to control whether it's on or off in settings.

I'm hoping that it gets added with an update as well. I read the verge's comment the same way as a lot of people that an update to the google search coming in the next few weeks would add the wake by voice feature; but it could just be poor phrasing.

youareme7 said:
I'm hoping that it gets added with an update as well. I read the verge's comment the same way as a lot of people that an update to the google search coming in the next few weeks would add the wake by voice feature; but it could just be poor phrasing.
Click to expand...
Click to collapse
are there any definitive sources for these rumors?
i ordered a n5 (to lock in my inventory) but i might return it for a motox because touch-less controls (and active notifications) are just too useful...

altus said:
Me too, because the article is about Android Kitkat, not the Nexus 5 specifically. And we know that a dedicated chip is required to have this wakup by voice function (otherwise the phone will not be able to enter deep sleep). So if it were true, the article would have mentioned that the chip is present.
Therefore the article quote should be read this way in my opinion:
Click to expand...
Click to collapse
The s-800 chip does have a dedicated component to do similar things such as motion sensing and always on listening, so perhaps this can be repurposed. i do believe qualcomm demoed this, it just may not be as power friendly as the moto x

AndreaCristiano said:
the verge has a pretty good track record and honestly with the hardware ability to do this function its a no brainer that it will be altered in the future
Click to expand...
Click to collapse
Sorry but The Verge article is misleading. They are talking about the KitKat update that is already available. And we already know it can't be done while the screen is off. If this was truly coming, Google would be singing it from the hilltops. I think the article needs to be updated to clear up that obvious error.

envizion58 said:
from this article by the verge, it seems like n5 will get an update that will add always listening feature in mid november? or am i understanding this article incorrectly given that it's true?
Click to expand...
Click to collapse
Would not be surprising

Read somewhere the low power core stuff is being used for other sensors like pedometer instead. So not likely to be in a future update as it would kill other features. May be possible via custom rom/kernel.
M.

Replacement = Even more problems.

Had a n6 with half purple screen and had it exchanged.
This new one is horrible ..
It seems to get really warm compared to the other and when it does, boy does it lag. Just typing this out, it's lagging.
I also noticed that my Bluetooth has "silence" spots while listening to music. Every 2-3 minutes, it will stop for a split second like it can't buffer, even if the music is on the device.
Another thing that may just be me, it seems the keyboard doesn't predict as well, like it's not even touching the keys I'm swiping.
Lastly, half the screen is white and half is a really yellow color. Very irritated by this device. Makes me want to throw it against a wall.

Your first problem can be resolved by using a custom kernel that does not use mpdecision. Mpdecision is known to be power inefficient and sends your CPU to be sitting in wasteful frequencies causing your phone to generate additional heat. My phone became really warm with mpdecision on.
Secondly, I don't use bluetooth so I can't comment.
Third. That isn't a N6 problem, its a problem with the software of the keyboard application that you're using. SwiftKey works great for me.
Fourth, can't really comment on that. My screen looks good, your phone should be uniformly the same color, you can try changing RGB and see if it would do anything. I recommend turning off adaptive brightness.

Good suggestions I suppose.
Only problem with those, I'm not gonna root or use a custom kernel. The last n6 only had a faulty screen and no other problems. That one didn't need any custom root activities.

20degrees said:
Good suggestions I suppose.
Only problem with those, I'm not gonna root or use a custom kernel. The last n6 only had a faulty screen and no other problems. That one didn't need any custom root activities.
Click to expand...
Click to collapse
If you don't root, or use ROM's then why post about it on a developer forum? I'm not trying to be rude just wondering why here. If it has more issue call moto and have them send a new one. My RMA phone is fine 0 issues so far and I'm happy with it.

This is a user forum as well as a developer forum.
I'm posting here to show there is problems with these phones.
Why does it matter to you?

If you are having those problems on stock, and don't want to root/etc, then your only option is to return it again. Pretty simple.
If you are looking for confirmation that your experience isn't 'normal' on the stock phone, I can confirm it is not.

20degrees said:
This is a user forum as well as a developer forum.
I'm posting here to show there is problems with these phones.
Why does it matter to you?
Click to expand...
Click to collapse
I'm not trying to argue at all I was just curious. I would have the phone replaced if you want to gave those issues fixed without modifying the phone. Best of luck with the issues because it's not fun when you can't fix them.

Pilz said:
If you don't root, or use ROM's then why post about it on a developer forum? I'm not trying to be rude just wondering why here. If it has more issue call moto and have them send a new one. My RMA phone is fine 0 issues so far and I'm happy with it.
Click to expand...
Click to collapse
I scratch my head also. XDA is a developer's forum. There are tons of other sites more suitable to those not wanting to root/ROM it up.

Sounds good. Let's discuss dbrand skins and the such.
I doubt this has anything to do with memory leaks or anything that's been discussed on lollipop.

I'd say you have a faulty SOC and I would replace it. My wife had similar issues on an S5 where it would stutter and fall behind almost and get warm. The icing on the cake was while taking video, normal 1080p video, and it would drop frames like crazy. Maybe 22fps or so was al, it was getting.

I actually agree with 20degrees on this one... There are tons of non development/customization threads on here, and XDA has a pretty knowledgeable user base so it is a convenient one stop shop for info.
People just need to ignore/keep their comments to themselves in the Q&A and general sections if they have nothing constructive to add to the topic of the thread.

Moto X Pro

Now that Moto is making a version of the Nexus 6 but with their software for China will it be possible to port moto assist/moto voice and display? It would be great if we could get these feature on the Nexus 6 and since this is identical in every way except for it not saying Nexus and having motos software tweaks.
Sources:
http://www.motorola.com.cn/moto-x-pro-cn.html
http://motorola-blog.blogspot.com/2...ns-to-china-moto-x-moto-g-moto-x-pro.html?m=1

Crossing my fingers

garyHal said:
Crossing my fingers
Click to expand...
Click to collapse
Maybe once its released we could get our hands on the ROM and flash if like some devices did to make the regular one a GPE.

I am hoping for better accessories also.

Pilz said:
...be possible to port moto assist/moto voice and display? It would be great if we could get these feature on the Nexus 6 and since this is identical in every way except for it not saying Nexus and having motos software tweaks.
Click to expand...
Click to collapse
Aren't those basically the same as google now, google voice dictation, and ambient display?
I.e., Nexus 6 already has them...

doitright said:
Aren't those basically the same as google now, google voice dictation, and ambient display?
I.e., Nexus 6 already has them...
Click to expand...
Click to collapse
No, the Moto ones are much better. Goto a carrier store and try Moto voice and display and then let me know if you still think they are the same. Ambient display isn't as good as the Moto one, and google now is nice (and used with moto voice) but you can't use custom commands with it.

My favorite thing about my wife's moto x is to be able to twist the phone twice to activate the camera. Theres some other cool features she has that I don't but that is by far my favorite

n3k said:
My favorite thing about my wife's moto x is to be able to twist the phone twice to activate the camera. Theres some other cool features she has that I don't but that is by far my favorite
Click to expand...
Click to collapse
The twist to activate camera is cool, I really like the moto display because its a better version of the ambient display on the Nexus even though the Moto has both. I wouldn't trade my Nexus for the Moto, I just want the Moto tweaks. I do like the voice commands and how you can make up any phrase to activate it (which can be funny sometimes depending on what you use)

Pilz said:
No, the Moto ones are much better. Goto a carrier store and try Moto voice and display and then let me know if you still think they are the same. Ambient display isn't as good as the Moto one, and google now is nice (and used with moto voice) but you can't use custom commands with it.
Click to expand...
Click to collapse
Most of the internet agrees that ambient display is far nicer than motorola, actually showing you the notification instead of just the fact that there is one.
http://www.droid-life.com/2014/11/0...-display-is-a-very-cool-take-on-moto-display/
What they say about not being able to use sensors (proximity/IR/motion) to refresh the ambient display is.... not entirely true. AOSP 5 does have ALL of this provision in the source code, but it has to be activated with an appropriate sensor (if available).
As for custom commands with google now... you really should look into this more, since there *are* ways to do that with google now. For example, tasker with autovoice.
As far as the quality of voice dictation goes, the google implementation (which probably uses the same backend) is pretty solid... as far as voice recognition goes.

doitright said:
Most of the internet agrees that ambient display is far nicer than motorola, actually showing you the notification instead of just the fact that there is one.
http://www.droid-life.com/2014/11/0...-display-is-a-very-cool-take-on-moto-display/
What they say about not being able to use sensors (proximity/IR/motion) to refresh the ambient display is.... not entirely true. AOSP 5 does have ALL of this provision in the source code, but it has to be activated with an appropriate sensor (if available).
As for custom commands with google now... you really should look into this more, since there *are* ways to do that with google now. For example, tasker with autovoice.
As far as the quality of voice dictation goes, the google implementation (which probably uses the same backend) is pretty solid... as far as voice recognition goes.
Click to expand...
Click to collapse
I understand where you are coming from but some people including myself prefer the Moto display. I don't care if I can't gesture over it, I just like the way the Moto Display looks compared to the ambient one. If it could work without the added sensors (which it will since the X Pro will likely have this) then I'm fine with that.
I know there are ways to implement the custom voice commands, however its more natural the way that its done on the X. I have tried some other alternatives but I wasn't a fan of them. The Nexus 6 has a low power chip for active listening if I recall correctly so this shouldn't be a issue if and when we can port those features over.
I also wouldn't say that the "majority of people prefer the ambient display" we can't generalize things like that because after all statistics can be very bias and wrong if they are not collected correctly. I have seen reviews including AP (android police) who stated they liked the Moto version better, but again its user preference.
I'm not saying you are wrong at all, I would just prefer the Moto tweaks on my Nexus phone because I like them.

Pilz said:
I understand where you are coming from but some people including myself prefer the Moto display. I don't care if I can't gesture over it, I just like the way the Moto Display looks compared to the ambient one. If it could work without the added sensors (which it will since the X Pro will likely have this) then I'm fine with that.
I know there are ways to implement the custom voice commands, however its more natural the way that its done on the X. I have tried some other alternatives but I wasn't a fan of them. The Nexus 6 has a low power chip for active listening if I recall correctly so this shouldn't be a issue if and when we can port those features over.
I also wouldn't say that the "majority of people prefer the ambient display" we can't generalize things like that because after all statistics can be very bias and wrong if they are not collected correctly. I have seen reviews including AP (android police) who stated they liked the Moto version better, but again its user preference.
I'm not saying you are wrong at all, I would just prefer the Moto tweaks on my Nexus phone because I like them.
Click to expand...
Click to collapse
I'm mostly on board with you. I like the ambient display looks vs moto display but I wish the screen wouldn't light up fully when interacting with the notification. In my opinion it totally defeats the purpose of having it black and white. Ambient display is inconsistent in which sometimes it doesn't come up. Moto display is the better functioning of the two.

biggiestuff said:
I'm mostly on board with you. I like the ambient display looks vs moto display but I wish the screen wouldn't light up fully when interacting with the notification. In my opinion it totally defeats the purpose of having it black and white. Ambient display is inconsistent in which sometimes it doesn't come up. Moto display is the better functioning of the two.
Click to expand...
Click to collapse
Don't forget moto display with moto assist has a night mode which went light up the screen when you're sleeping or in a movie. Of course you could use priority notifications but this is more convenient in my opinion.

I'd love to see APT-X ported to N6 ...

nilezon said:
I'd love to see APT-X ported to N6 ...
Click to expand...
Click to collapse
I thought you needed the chip to support it?

n3k said:
My favorite thing about my wife's moto x is to be able to twist the phone twice to activate the camera. Theres some other cool features she has that I don't but that is by far my favorite
Click to expand...
Click to collapse
I am using an app that is still in beta called "QuickCamera". I have been using it since the Nexus 5, and it seems to work pretty well on the Nexus 6. As a matter of fact, the camera opens up much faster on the N6 than the N5 did.
Here is the link to the G+ community for this beta:
https://plus.google.com/u/0/communities/102812968500461027770
EDIT: I just found the XDA thread on this app also:
http://forum.xda-developers.com/showthread.php?t=2732021

PaisanNYC said:
I am using an app that is still in beta called "QuickCamera". I have been using it since the Nexus 5, and it seems to work pretty well on the Nexus 6. As a matter of fact, the camera opens up much faster on the N6 than the N5 did.
Here is the link to the G+ community for this beta:
https://plus.google.com/u/0/communities/102812968500461027770
EDIT: I just found the XDA thread on this app also:
http://forum.xda-developers.com/showthread.php?t=2732021
Click to expand...
Click to collapse
Looks like the either the developer or Google has removed this app from the play store. Can anybody post a link to the .apk please.

Mayze23 said:
Looks like the either the developer or Google has removed this app from the play store. Can anybody post a link to the .apk please.
Click to expand...
Click to collapse
Neither removed it. You have to sign up with the community, then click on the link to join the beta, and wait for it to show up for you in the Play Store (some show up in minutes, one or two took over an hour to show up after joining both). This is how pretty much all of betas through the Play Store are handled. I just checked and put screenshots attached to this post.

nilezon said:
I'd love to see APT-X ported to N6 ...
Click to expand...
Click to collapse
Has aptX been confirmed for the Moto X Pro?

Is this phone available yet? I was hoping the some devs could get the Motorola stuff working on the Nexus 6

biggiestuff said:
Is this phone available yet? I was hoping the some devs could get the Motorola stuff working on the Nexus 6
Click to expand...
Click to collapse
No I just checked their Chinese webpage and it's not available yet

About to go for a nexus 6 but some issues are keeping me from doing it

I've had pretty much every nexus device, but last year I decided to get myself an Iphone 6, but I really missed android, so I'm about to get the nexus 6 but some issues are keeping me from doing it, I've read quite a few reviews and I'm concerned about the following issues:
1. Why is the camera so slow to take pictures? You think it could improve in the future? That's probably the thing I like the most about the iphone 6, how good the pictures come and how the camera is blazing fast
2. Is it true that the device is slower than the nexus 5? Have updates improved this situation? My nexus 5 already stuttered with Lollipop, Ive read quite a few reports about the phone slowing down and lagging for no apparent reason (except for maybe the quadHD killing the cpu/gpu)
3. How true are the reports of screen burn in?
4. How do non google apps and icons look? I imagine pretty bad since facebook or instagram's icons haven't even been updated to take advantage of a 1080p screen
5. Is it true that the device has slow storage a step down from the nexus reading and writing speeds?
Thanks for your help

Chad_Petree said:
I've had pretty much every nexus device, but last year I decided to get myself an Iphone 6, but I really missed android, so I'm about to get the nexus 6 but some issues are keeping me from doing it, I've read quite a few reviews and I'm concerned about the following issues:
1. Why is the camera so slow to take pictures? You think it could improve in the future? That's probably the thing I like the most about the iphone 6, how good the pictures come and how the camera is blazing fast
Click to expand...
Click to collapse
The actual act of taking a picture is fast, its just focusing that is slow. If you focus manually or fixed, it will take pictures amazingly fast.
2. Is it true that the device is slower than the nexus 5? Have updates improved this situation? My nexus 5 already stuttered with Lollipop, Ive read quite a few reports about the phone slowing down and lagging for no apparent reason (except for maybe the quadHD killing the cpu/gpu)
Click to expand...
Click to collapse
Not at all true.
3. How true are the reports of screen burn in?
Click to expand...
Click to collapse
Completely imaginary.
4. How do non google apps and icons look? I imagine pretty bad since facebook or instagram's icons haven't even been updated to take advantage of a 1080p screen
Click to expand...
Click to collapse
Where are you coming up with these questions? The only icon I've seen that actually looks bad, is the one for my bank... and it looks bad on ANY screen. Screen resolution is not so tightly tied to "icons" -- bigger screen = more icons. Also, Nexus 5 was already a 1080p display. I also hardly consider this question to be meaningful. Who really cares what icons look like? The objective is to maximize USEFULNESS.
5. Is it true that the device has slow storage a step down from the nexus reading and writing speeds?
Click to expand...
Click to collapse
No. Flash storage is blazingly fast on this device, HOWEVER, the "default configuration" enables data partition encryption by force, which reduces the EFFECTIVE flash performance to nexus 5 level (which is still very good). Simple adjustment to a text file on the boot partition allows this to be disabled. It is also probable/possible that Google will be enabling hardware crypto on the next update.

doitright said:
The actual act of taking a picture is fast, its just focusing that is slow. If you focus manually or fixed, it will take pictures amazingly fast.
Click to expand...
Click to collapse
I see, we will see if it changes with the 5.1" update, I remember the first big update for the nexus 5 did wonders for the camera
doitright said:
Completely imaginary.
Click to expand...
Click to collapse
http://nexus5.wonderhowto.com/how-to/fix-screen-burns-your-nexus-6-other-amoled-device-0159397/
http://forum.xda-developers.com/nexus-6/general/burn-t2955765
doitright said:
Where are you coming up with these questions? The only icon I've seen that actually looks bad, is the one for my bank... and it looks bad on ANY screen. Screen resolution is not so tightly tied to "icons" -- bigger screen = more icons. Also, Nexus 5 was already a 1080p display. I also hardly consider this question to be meaningful. Who really cares what icons look like? The objective is to maximize USEFULNESS.
Click to expand...
Click to collapse
I'm sorry, I know it sounds ridiculous but I'm studying to become a designer and that kind of things really bother me , as far as I know if you don't update the resolution for the icons and increase the resolution of the display you end up with fuzzy icons
doitright said:
No. Flash storage is blazingly fast on this device, HOWEVER, the "default configuration" enables data partition encryption by force, which reduces the EFFECTIVE flash performance to nexus 5 level (which is still very good). Simple adjustment to a text file on the boot partition allows this to be disabled. It is also probable/possible that Google will be enabling hardware crypto on the next update.
Click to expand...
Click to collapse

I'm in agreement with @doitright. I can say nothing but good about this device. I do not have any of those issues nor know of any that do. As with any device though there are always some bad ones that an unlucky few receive. It does not make all of them bad just those. My phone is a beast. It outperforms the N5 by miles. Screen looks amazing. Icons to me look great I haven't come across a bad looking icon except that of my bank.... I guess banks hire poor developers idk. Storage is incredibly fast. Camera is fantastic. Fastest signal acquisition I've seen on any phone including GPS.
Eh. Entirely up to you what you want to do. I don't trust any reviews. I rather go with my own opinions/feelings on anything. You should too.

Chad_Petree said:
I'm sorry, I know it sounds ridiculous but I'm studying to become a designer and that kind of things really bother me , as far as I know if you don't update the resolution for the icons and increase the resolution of the display you end up with fuzzy icons
Click to expand...
Click to collapse
App icons are controlled by the dev. I've never seen a fuzzy one.

doitright said:
No. Flash storage is blazingly fast on this device, HOWEVER, the "default configuration" enables data partition encryption by force, which reduces the EFFECTIVE flash performance to nexus 5 level (which is still very good). Simple adjustment to a text file on the boot partition allows this to be disabled. It is also probable/possible that Google will be enabling hardware crypto on the next update.
Click to expand...
Click to collapse
I'm awaiting this Thursday to grab one on VZ, coming from a Galaxy Nexus, anything I could get now would be a major update hardware wise, however the only exception I take is the last part of this, not trying so start anything, your other parts are spot on.
The current speculation is that 5.1 may go backwards on forcing software encryption, but nothing is confirmed there, see last paragraph:
http://www.slashgear.com/android-5-1-in-march-heres-what-may-be-coming-18369666/
If the Nexus 6 had the HW encryption on it, and I cant confirm it does, we're left with these options:
1 - they do enable it, which begs why it wasn't in the first place. Current rumor is that the qualcomm drivers for that engine are not open source, therefore it is a no no on android:
http://androidheadlines.com/2014/11...ency-likely-due-missing-qualcomm-drivers.html
2 - they tweak the software encryption, which if you check the threads, opinions really vary here. if you need to irk the absolute most out if it for read write, then undo it. But plenty of others have chimed in saying it wasn't that big an increase, i believe it to be what you may be using on the device that makes the difference, more intensive apps may cause the SW process to bog down, but in all, it is still fast.
3 - they disable it by default, which I wonder how that would be accomplished in an OTA, it would need to wipe the device I'm sure, but ...
4 - Lastly, if in fact they cant use the engine, or it wasn't included (doubtful, it has qualcomm in it) then you cant enable it by an OTA, end of that story.
Personally, if I grab the N6 this week, I plan on unlocking/rooting/removing VZ oem partition, but for the moment leaving encryption on, because 5.1 may drop in March, and then see how things are at that juncture.
It would be great if they could enable HW encryption, because we get that security and maintain read write offloaded from the CPU.
Lastly, I plan on trying to enjoy the thing, playing with it for at least an hour in store before taking it (you never know) because as most of us here are OC hehe, reading all the threads of issues before buying it is kinda a downer. I know I'm going to love it, having waited three years to update myself.

RW-1 said:
The current speculation is that 5.1 may go backwards on forcing software encryption, but nothing is confirmed there, see last paragraph:
http://www.slashgear.com/android-5-1-in-march-heres-what-may-be-coming-18369666/
If the Nexus 6 had the HW encryption on it, and I cant confirm it does, we're left with these options:
1 - they do enable it, which begs why it wasn't in the first place. Current rumor is that the qualcomm drivers for that engine are not open source, therefore it is a no no on android:
http://androidheadlines.com/2014/11...ency-likely-due-missing-qualcomm-drivers.html.
3 - they disable it by default, which I wonder how that would be accomplished in an OTA, it would need to wipe the device I'm sure, but ...
4 - Lastly, if in fact they cant use the engine, or it wasn't included (doubtful, it has qualcomm in it) then you cant enable it by an OTA, end of that story.
Click to expand...
Click to collapse
That's what I was thinking about, would it be possible for them to get rid of the encryption with an OTA , I would think that one needs to factory reset your device

Chad_Petree said:
I see, we will see if it changes with the 5.1" update, I remember the first big update for the nexus 5 did wonders for the camera
Click to expand...
Click to collapse
Focus is a PHYSICAL MOVEMENT of the lens. No update will change the amount of time it takes to move the lens.
http://nexus5.wonderhowto.com/how-to/fix-screen-burns-your-nexus-6-other-amoled-device-0159397/
http://forum.xda-developers.com/nexus-6/general/burn-t2955765
Click to expand...
Click to collapse
I congratulate you on finding a thread about an imaginary problem, and a "fix" for an imaginary problem.
There is a certain subset of people who will do anything, IMAGINE anything, to find a problem. Don't ask me why they are like that. Sucks to be them.
I'm sorry, I know it sounds ridiculous but I'm studying to become a designer and that kind of things really bother me , as far as I know if you don't update the resolution for the icons and increase the resolution of the display you end up with fuzzy icons
Click to expand...
Click to collapse
You can't do anything to increase the fuzzyness of an image, unless you actually stretch it larger. I.e., if it takes the same physical space on the screen, then increasing the DPI on the screen won't cause it to become more fuzzy -- it just won't increase in SHARPNESS with the display. Google has specifications regarding the dimensions of the icons, and these specifications have always included a "much larger" image than what will actually display on the screen. The icons actually get scaled down to fit. So really, don't worry about it. If you find an application with a ugly/fuzzy icon, complain to the application vendor, because they're the ones who made an ugly icon, not the platform.
I just can't stress enough, that this is a silly point to use to avoid a device.
---------- Post added at 06:03 PM ---------- Previous post was at 05:49 PM ----------
RW-1 said:
I'm awaiting this Thursday to grab one on VZ, coming from a Galaxy Nexus, anything I could get now would be a major update hardware wise, however the only exception I take is the last part of this, not trying so start anything, your other parts are spot on.
The current speculation is that 5.1 may go backwards on forcing software encryption, but nothing is confirmed there, see last paragraph:
http://www.slashgear.com/android-5-1-in-march-heres-what-may-be-coming-18369666/
Click to expand...
Click to collapse
I *absolutely promise you* that they WILL NOT eliminate the encryption requirement. Those "android one" devices are... really really cheap. It is likely that they don't force encryption simply because they are not up to the task.
If the Nexus 6 had the HW encryption on it, and I cant confirm it does, we're left with these options:
Click to expand...
Click to collapse
I CAN confirm that it does. There is no question at all. It is part of all snapdragon SoC's since about S4.
1 - they do enable it, which begs why it wasn't in the first place. Current rumor is that the qualcomm drivers for that engine are not open source, therefore it is a no no on android:
http://androidheadlines.com/2014/11...ency-likely-due-missing-qualcomm-drivers.html
Click to expand...
Click to collapse
There are two sides to the use of encryption hardware with qualcomm SoC's; the first is the "blobs", and the second is the integration with Android and the Linux kernel. Specifically, qualcomm's hardware crypto requires changes both to the kernel (which is under GPL), as well as VOLD (which is under APL).
Obviously, to include the kernel part, that kernel part MUST be provided as source. There is absolutely no option here.
VOLD is the part of Android responsible for mounting and managing disks. It is under the Apache license, which means that technically speaking, it can be distributed without including source, HOWEVER, this is a Nexus from Google, which means that they really can't ship a blob in place of VOLD. It has to be possible to build VOLD from AOSP.
So here is what was going on; at the time that Nexus 6 first shipped, Qualcomm HAD NOT made the source for Kernel or Vold available on CAF. That made it *impossible* for Google to include, since they would have to provide kernel code on request, and require that AOSP VOLD actually build and work.
QUALCOMM HAS SINCE MADE THE SOURCE AVAILABLE!!!!
And, in fact, there are a number of devices for which CM actually builds and includes hwcrypto *right now*.
2 - they tweak the software encryption, which if you check the threads, opinions really vary here. if you need to irk the absolute most out if it for read write, then undo it. But plenty of others have chimed in saying it wasn't that big an increase, i believe it to be what you may be using on the device that makes the difference, more intensive apps may cause the SW process to bog down, but in all, it is still fast.
Click to expand...
Click to collapse
This isn't even a half solution, because even though it may seem to improve storage performance to an acceptable level, it has to nail the CPU while doing so.
3 - they disable it by default, which I wonder how that would be accomplished in an OTA, it would need to wipe the device I'm sure, but ...
Click to expand...
Click to collapse
Technically possible, but I *promise* you, it won't happen.
4 - Lastly, if in fact they cant use the engine, or it wasn't included (doubtful, it has qualcomm in it) then you cant enable it by an OTA, end of that story.
Click to expand...
Click to collapse
Most definitely CAN be used. No question about it.
Personally, if I grab the N6 this week, I plan on unlocking/rooting/removing VZ oem partition, but for the moment leaving encryption on, because 5.1 may drop in March, and then see how things are at that juncture.
It would be great if they could enable HW encryption, because we get that security and maintain read write offloaded from the CPU.
Click to expand...
Click to collapse
You could disable crypto now, and let it encrypt when the update rolls around. Disabling forced-crypto does not prevent you from using crypto now or later.
Lastly, I plan on trying to enjoy the thing, playing with it for at least an hour in store before taking it (you never know) because as most of us here are OC hehe, reading all the threads of issues before buying it is kinda a downer. I know I'm going to love it, having waited three years to update myself.
Click to expand...
Click to collapse
Keep in mind that the test unit in the store gets abused.

DIR,
Looked forward to your responses on my last post, and was not dissapointed, nice info there, especially "QUALCOMM HAS SINCE MADE THE SOURCE AVAILABLE!!!!"
so has anyone done a comparison between the hwcrypto'd CM versions and unencrypted yet?
Yeah, I know the store ones get abused, in the end it would be a N6 or a GS6 for me, and I just cannot go to touchwiz, no matter how toned down, I want pure android, and unlocking ability, etc. Kinda makes the choice or me hehehe.
Dammit VZ, if you just announce online ordering tomorrow ... grrr .....

doitright said:
Focus is a PHYSICAL MOVEMENT of the lens. No update will change the amount of time it takes to move the lens.
Click to expand...
Click to collapse
Oh oh well, nothing is perfect
doitright said:
You could disable crypto now, and let it encrypt when the update rolls around. Disabling forced-crypto does not prevent you from using crypto now or later.
Click to expand...
Click to collapse
What would be the point of deactivating to reactivate later?

Chad_Petree said:
Oh oh well, nothing is perfect
What would be the point of deactivating to reactivate later?
Click to expand...
Click to collapse
I would guess deactivate to gain read/write speed increase now, if the update enables HW encryption then you would let it.
Oh, and that is the point - nothing is perfect, not the N6, nor the units that will come after it hehehe....

RW-1 said:
DIR,
Looked forward to your responses on my last post, and was not dissapointed, nice info there, especially "QUALCOMM HAS SINCE MADE THE SOURCE AVAILABLE!!!!"
so has anyone done a comparison between the hwcrypto'd CM versions and unencrypted yet?
Click to expand...
Click to collapse
I said on *some* devices. I did not say that they were enabling it on Nexus 6.
Yeah, I know the store ones get abused, in the end it would be a N6 or a GS6 for me, and I just cannot go to touchwiz, no matter how toned down, I want pure android, and unlocking ability, etc. Kinda makes the choice or me hehehe.
Click to expand...
Click to collapse
Yep, I'm totally with you on that. My last phone was a samsuck.... NEVER again. I spent WAY too many hundreds of hours on kernel and device tree maintenance to get and keep that thing working adequately on CM... then Omnirom (omni is waaaaaay nicer than CM). After a year of ownership of that thing, got the wife a Hammerhead (nexus 5), and its been just so easy to maintain. Literally all I ever did with her phone was add root, busybox, and xposed (to kill a couple of the google services wakelocks). This time around, I wanted the thing to just freaking work already!!!! Only downside is that its a bit *larger* than I would have liked.
Dammit VZ, if you just announce online ordering tomorrow ... grrr .....
Click to expand...
Click to collapse
I don't think that you should buy from verizon, even if/when they sell it directly. It will likely be crippled and branded, at least to some extent. Buy it from tmobile or google play store, and all you need to do is throw your verizon sim card into it. I think I heard that sprint also does not molest it. Oh, it could also be purchased directly from motorola.
Just whatever you do, do NOT buy it from ATT. They DO molest and cripple it.
---------- Post added at 03:34 PM ---------- Previous post was at 03:33 PM ----------
Chad_Petree said:
What would be the point of deactivating to reactivate later?
Click to expand...
Click to collapse
To gain RW performance NOW... DUH.

I'll be getting it from VZ, because I just don't have the spare $$$ to buy direct and place it on VZ.
ATT taught us that VZ will have to toss its bloat on the oem partition just like anyone else, so ... as far as branding, I think that may rub off like ATT's, but if not I plan on putting in a case anyway.
Now we have to wait another two weeks if the newest rumor is true ...

Moto X features on Nexus 6

This has probably been asked before but a search didn't yield any satisfying responses either way.
The Moto X has a handful of features unique to itself that are very nice to have. I had the first generation and fell in love with it. With my Nexus 6 I love having the Nexus feel, but I want some of the features.
Have any ROMs ported over some of the software features of the Moto X? Some features are in Lollipop, but I'm wondering if anyone has ever tried to port over the gesture to launch the camera, or try to port over the breathing active display (Google's variant is very underwhelming and not very responsive to light changes). Since Motorola made the hardware, I wasn't sure if there was some cross compatibility, or if any attempt had been made.

helios.z3r0 said:
This has probably been asked before but a search didn't yield any satisfying responses either way.
The Moto X has a handful of features unique to itself that are very nice to have. I had the first generation and fell in love with it. With my Nexus 6 I love having the Nexus feel, but I want some of the features.
Have any ROMs ported over some of the software features of the Moto X? Some features are in Lollipop, but I'm wondering if anyone has ever tried to port over the gesture to launch the camera, or try to port over the breathing active display (Google's variant is very underwhelming and not very responsive to light changes). Since Motorola made the hardware, I wasn't sure if there was some cross compatibility, or if any attempt had been made.
Click to expand...
Click to collapse
very simple answer for you, no.

Nope.

rootSU said:
Nope.
Click to expand...
Click to collapse
you turned my very simple no, into a complicated nope
oh, but your profile photo got a giggle out of me, so, this time ill let you pass :silly:

simms22 said:
you turned my very simple no, into a complicated nope
oh, but your profile photo got a giggle out of me, so, this time ill let you pass :silly:
Click to expand...
Click to collapse
Your post wasn't there when I stared typing out my epic response

rootSU said:
Your post wasn't there when I stared typing out my epic response
Click to expand...
Click to collapse
i know. your post came literally 3 seconds after mine