EskeRahn

I'm in the same boat... As far as I know you can only move forward without clearing. But have a bit more patience, I do believe a certified version is not that far out in the future.

If I remember correctly @tdm swapped them in LineageOS, so if that is it, it should be fixed there - i have not tested that.

When I use a headset calls are just fine. And recording a small video, also records the sound fine, so not hardware issues. I too have the problem, especially as a speaker phone. IF I talk a bit loud and clear (like to a meeting) it works, but if I talk at a normal voice, people have problem hearing. It is described in other threads, and my guess is that it is the noise-cancellation that is a bit too aggressive regarding my normal voice as just background noise. There also seems to be a problem speaking immediately after picking up a call, that somehow seems to (often?) be lost too.

🤣

Yes that is beacause you have chosen German, that swaps Y/Z. I was talking the shifted and non shifted

Hardware-wise the models are 100% identical internally, it is only the print on top of the keys that are different. So the software need to be able to handle the back-shift from the shifted qwerty to normal qwertz. (And you have to somehow tell the system what keyboard-print you got)

I think the error message is inaccurate. I get the same on a LineageOS 16.0 Test15 that has NOT got the root addon installed. Maybe it is trying to say that the device is not certified or that it does not pass the SafetyNet test. ADD: Checked that It opens without this on Certified Stock even with an OTA not passing SafetyNet. (So the important part of the message is the next that it expects an "official Android")

Updated the previously posted script for somewhat automated updates with the above root patch as an option. Assuming you have downloaded the @tdm images mentioned here and for root also the addonsu-16.0-arm64-signed.zip image linked to here Use as either LineageFLASH 15 or LineageFLASH 15 ROOT (assuming you called hte file LineageFLASH .BAT obviously) The paths are hardcoded, you might want to change those if you are storing the images in a different subdir to the ADB and batch @ECHO off if %1.==. goto :EOF ECHO * Wait for boot to bootloader to finish (or do manu

To my knowledge there are no available firmware layer deeper than what we flash, so it should not matter if you update on stock before going to lineage, it will be wiped. And the process uses both the A & B partition. Flashing the recovery to A, and this then flashes the main image to B (and sets B active) AFAIK the only problem in stepping backwards is that you USUALLY will have to wipe the user data (some updates are so small that you can step back without wiping though). As I read it there are very few differences between 12, 13 and 14, so here i think stepping backwards will

Same here. BTW @tdm "Horizontal" is perhaps not the most clear term, for a phone being used in both directions. 😉

It usually reads my fingers a few mm above. Have you got a screen-protector on? (I see the hoovering-read with and saw it without before). But could be a matter of the material of the protector how bad it is?

That one is new to me 😥 What are the other defaults you need to reset?

We have had other reports that people have better luck connecting to a 2.0 than a 3.0 port.

Did you check if Caps still goes on/off?. I mean if it does not we know that it is frozen. (If it works we are not any wiser, unless someone can tell us at what level the LED is handled)

Me too, I bet the Corona has at the least part of the blame. 😥

Well in theory they could offer the uncertified software, but I bet a lot of users would be quite angry if Fxtec deliberately prevented people from using their banking app and the like requiring the certification.

Spam filter/folder? Also remember that when they get a follow-up mail, the case is moved to the back of the queue, so If someone send say daily mails, that can delay them ever getting to the original mail. But let me mention @Erik here so he can have a look.

Well if that was their reasoning they would just love people rooting, as they could use that as an excuse for refusing support and repair under warranty, and thus save money....

Tried this flip case for Nova 5T and Honor 20 https://www.ebay.co.uk/itm/352897154905?var=622151625395 The shell fits fine, but the flip is too tight to close around the Pro1. 😥

Yes, this is a nice example of the dillema a manufacturer has here. A user complaining about a product being 'faulty' is bad PR even if the fault is actually in the (mis)use and not the product - the last part seldom reaches all those that heard there was a problem... So I do understand that many manufacturers keep things locked being scared of this. I'm glad that F(x)tec give us the options. 🙂

I would say that "encourage" is pushing it a bit. I would rather say that they in no way are opposed to it, And openly tell people of the options, But I doubt that they will encourage the 'ordinary' users to do so, as it might limit them from running apps they would want, and increases the security risk, especially for the 'ordinary' users.

In short: No. It is a bit like saying that a car manufacturer limits your freedom by offering seat belts. If a govermental agency requires you to use the seat belts to drive on public roads, they are the ones doing the limiting, not the car manufacturer.

Not quite. It is not Android that prevents you from rooting, it is some phone manufacturers. But sure rooting could be made easier, and a more advanced security level system could have been implemented in Android. I guess this could be a matter of history, that Android worked on hardware much more limited than today's devices, and have not been thoroughly reimagined/rewritten. And on the bank thing, I repeat my self here: it is an APP thing not an OS thing. At the least in Denmark web-banking requires much more authentication than opening a bank app on your Android device.

Well it is possible to work from a third state between what we have as un-rooted and fully rooted. Giving us the flexibilities of rooting temporarily, without the permanent risk of working rooted. But seen from an app-perspective it is still an insecure platform, as they (obviously) have no idea what we did while we worked with high privileges. It is the old story of where we want to be in the spectrum of in the safety in jail in one end and total anarchy without restrictions in the other. I doubt that there will be any place in that spectrum that fits all. Quite a lot of

I agree in principle that rooting should not block OTA updates - I was unaware that it did. But my GUESS for the reason behind that is that for a non-rooted device it is much easier to know the state of things, and this simplify updates quite a bit. For the other root-related issues, I still say that it is an app-thing not an OS-thing, so they are not to blame as such. Though they by certification and SafetyNet offers a frame for the apps to check the base they are working on. If an app has nothing to loose by you being rooted I doubt that many will require that your device is non-roote