[ZTE Axon 7 Guides, News, & Discussion] QuantumFluxx:
I remember reading about Huawei's involvement in this, but not ZTE's. Corporate greed, corporate greed, corporate greed.... I guess we should all be very aware of this and any developments. Please advise us of anything you come across that doesn't look right. :)

---

I'm so sorry to have played a part, but I am very glad that you were able to find all of this out before the end of your return period. At least, I assume that you're going to return it :)

I wrote this piece because I couldn't find something comparable on XDA or the rest of the net. Just a one sentence reference, here or there, that says someone couldn't encrypt. You would think more people would have flipped out about this, but the average 'unlocker'/'flasher' has a very poor opinion of full device encryption.

---

Good luck with your upcoming TWRP update! P.S., From TWRP.me regarding the Bullhead

If you install the recovery image through TWRP and reboot recovery, have you had any luck? Dunno if I'm reading that wrong.

I believe that the Nougat update re-added encryption [for the Axon].

I can help you secure your quick settings while the device is locked. You need Tasker and root.

Go to a shell and do

settings get secure sysui_qs_tiles

and take notice of the output. We will call these your 'default' settings, hereafter.

In Tasker, you would set up an event that triggered whenever the display was switched off. You could create a timer, but that would be substantially more complex than just tying the functions to the screen state of the device. The next command you will need is

settings put secure sysui_qs_tiles xxx

where 'xxx' are the tiles you want to appear on the lock screen/after the command is executed (referred to as 'modified', hereafter.)

So, 1st: Event,ScreenOff->Code,RunShell 'settings put secure sysui_qs_tiles modified', Use Root

2nd: Event,DeviceUnlocked->Code,RunShell 'settings put secure sysui_qs_tiles default', Use Root

3rd: Event,DeviceShutdown->>Code,RunShell 'settings put secure sysui_qs_tiles modified', Use Root

You will end up with 3 profiles and 2 tasks. I have attached a screenshot. This is my configuration of the 'Run Shell' command that would be triggered by the 'DeviceUnlocked' event.

You could set up the two different configurations, i.e. edit the quick settings tiles to one configuration when the device is locked, and one configuration for when the device is unlocked. Retain the output of the aforementioned 'get' shell command for each configuration and use them as the 'default' and 'modified' variables for your shell commands.

I always find it extremely difficult to write about Tasker and maintain any sense of literary professionalism. My apologies for any confusion. I'm looking at what I just wrote, and....yeah.

I have the same thing set up on my device and I would be happy to provide the exported files, if you are interested.

---

Yes!!! I wholeheartedly agree. You are getting speed, reliability, support, and updates with the Pixel.

We got the speed.

We got the reliability.

We have XDA.

We finally got the updates. -- I'm on the January security patch on 7.1.1.

In short, the Pixel can remain on the top shelf. I can see no reason it is so expensive other than the fact that Google knew people would gobble it up. That's how Apple does things. smh. The Pixel (and the iPhones) are just not worth $700-870. I would pay 400$ for the Pixel and $549.99 for the XL. That is still overpriced, but much more acceptable. In my opinion, these companies would have you believe that these phones really are VERY expensive to manufacturer. From what I've heard/read, Apple is making about 200$ on every iPhone they sell. Over the years, with that amount of money coming in, there is ABSOLUTELY no excuse to release a phone with outdated hardware and inferior display technology.

By the way, your Moto sounds sweet :) I miss my XT1575...

---

Thank you all for your kind words!