EskeRahn

Ah well 'proved' was a very hard word. 'suggested' might be better 😉 Just to be sure, did you restore on top of a freshly reflashed stock image (following casey's guide) - before booting it? Or did you do something else?

So we better tag @Casey here as this means some extra tests are needed, that only sensibly can be made by someone that can easily add new key-attestation when lost, and I guess that means internally at FxTec.

So does this mean that you have proved that restoring a saved persist image is NOT enough to keep key-attestation, as we thought?

If you are talking the Pro1X, then yes. 😉

We got it on LineageOS for the Pro1, I do not know if it can easily be added to stock android though.

Thanks for the warning!

I made three 'polls' so we can see the progress of the deliveries of the Pro1X. So please 'vote' so others can see how things progress. It is divided into three individual polls for technical reasons: 1/3 Shipping Info 2/3 Surcharges 3/3 Delivered Open discussion on this in this thread:

You have already been pointed to the long thread, but the tl:dr version is: Any soft cases fitting a Huawei P20 Pro can easily be modified in minutes No special skills required. (Do not take stiff cases though, as the slight slant of the Pro1X's back towards the edges makes them a poor fit). For a number of my DIY experiments see here.

Flashed aicp_pro1_s-17.1-WEEKLY-20220817.zip on security update 2022-03-05 Seems much the same. Still initial boot-loop after flash, Issues with using the keyboard for other than US, no matter if I select one or more (It does respect the qwerty/qwertz layout selection though). Ctrl+space for swapping languages is (also) ignored. ADD: This proved to be related to an app. Accesibility requirement by "Android Assistant" messes with the keyboard-functionality - had exactly the same on the Pro1X (on stock android 11) But that aside things seem to work.

Also check if Caps changes. And if you are in E.g.Settings search (at the top), does the fake keyboard disappear when you slide open the real one. (Trying to find out if it is the light in it self that is the issue, or it does not detect the keyboard being opened)

Nice. I wonder why, I could be wrong, but tapping on the backplates, I suspect the Pro1 back to be more massive than the Pro1X?

Have not even tried the build in camera app. Open camera works fine with landscape

(I took the liberty to move some posts comparing the two devices over from the Pro1X LineageOS thread)

I moved the comparisons over to separate thread here

Nope. There were early unit as early as spring 2019. So some half year after that for the first test build an another half year for release bulid of 16 AND that was for a chipset where there were other devices... I do not know how early they have had test units for developers on the Pro1X. At the earliest this spring would be my guess. Does anyone know if there are any 662 powered phones with LineageOS currently

Tried to do them on a Pro1 and Pro1X single core Pro1: 394 Pro1X: 307 multi-core Pro1: 1604 Pro1X: 1294 compute (opencl) Pro1: 1943 Pro1X: 383 compute (vulkan): pro1: Fails, 408 (0 on Horizon detection) pro1X: Crashes the entire app And the big difference is in the GPU parts only

If I recall right @tdm and a few other did the LineageOS 16 for the Pro1 before going public, though they at some point showed some test-versions, see this

on the geekbench, take their results with a truckload of salt. look here for the Pro1 https://browser.geekbench.com/search?utf8=✓&q=fxtec Results vary from 152 to 394 for single core, and from 513 to 1754 on multi. Both Vulcan and OpenCL results vary with a factor of two. I'm trying to running it on the Pro1 and Pro1X. The Pro1 failed on the Vulcan, something with horizon.

Not ALL on git is public... You could easily have a closed channel for developing something, and later either move it to an open channel or make the channel public

To me it make sense that they have taken a principal decision not to tell what is going on. If they did, they would have endless questions on how far they have come, and if it would be possible to get an early version for testing et cetera. It make a lot of sense waiting to they have something fairly close to an acceptable version. But that said I'm (also) impatient and would love to have an idea on when we will get it. It is like the Pro1X it self, worth waiting despite felling that the waiting time is killing us....

More ram, new camera-chip, an over three years newer chipset that will get security updates, and a two major versions newer Android too.... For many that alone says update. My daily driver has since 2019 been a retail Pro1 on stock android. And when I get the retail Pro1X as I perked for, I expect it to take over, and demote the Pro1 to tests (and as a backup device) But sure for some power hungry tasks the Pro1X is slower. But for a lot of tasks the difference is minor. Not unusual that an older flagship is close to a newer midrange chip. Have a look at e.g. this https://nanoreview.

For the most part yes. The Pro1X got the newer supported snapdragon 662, the Pro1 got the 835, that is no longer supported with security updates. It is not easy to get a Pro1, and as a consequence those sold are not cheap. But If you are lucky and find a user that plan to only use stock Android, the Pro1X is an update, you might be able to arrange some swap.

Indeed as not all reports it, it could well be limited to certain bands. And this goes for both cellular and WiFi. Sometimes bugs are really elusive I got two sims in my daily Pro1. Around August first I suddenly rarely could do data, mms or calls on my primary sim in slot 1. SMS worked just fine, and swapping the sims both works fine. Another sim from same provider in slot 1 works fine too, and the sim inserted in another Pro1 does too... Now how is that for an elusive bug for you! (And no the contacts are not worn through or anything like that), so after accepting slot 2 to be my new primar

Just a wild guess. Could it be that the Nova process is stopped (or perhaps even crashes?) and the system fall backs to using another launcher? It could be the battery optimiser or other software that 'cleans up' background bloat, that tears your nova down too? Next time you see, before reselecting, try to go to apps, and see if the Nova is stoppable, or already is stopped. You might need to make sure it can not be optimised, if it does not support Doze properly. (Under the apps, and the app, advanced, and battery, see battery restriction and battery optimisation).

If they are using the hardware drivers from stock android, the issues are unlikely to be limited to one OS.