EskeRahn

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

(split from another thread) I have a hard time finding the logic here. If you want the free access to do as you please, you can just root it. The whole point of NOT rooting is precisely to make sure the user do not have the rights to accidentally make something that messes things up. If you want to be in complete control, then root. Yes there are apps that won't work rooted, for security reason. Typically apps like bank-apps. If you disagree with them requiring the device to be locked&certified, it is a matter to take up with the app-maker, Not Android in it self.

AH! That sounds like the old known bug, that the display and touchpanel is inactive. I have seen it a few times on Lineage - though more seldom that I did on stock, before it was patched, If you open the device, you will see that e.g. Caps is reacting, if this is the bug. When I had it I held Power 1-2 secs, pressed Tab Trice and Enter (To open the power menu, and goto "Restart").

A few guesses. Have you tried a different port and/or cable? Could it be the version of ADB? Have you fetched it directly from Google https://developer.android.com/studio/releases/platform-tools? Have you tried from a different PC with another OS? (I have been using 29.0.5 on Windows 10, and just tried reflashing with newest 30.0.2, that works too)

Indeed. @tdm has modified it for LineageOS with a delay, ignoring repetitious touches. Hopefully this patch will come to stock too.

I have had a unit that had Stock, Lineage, Sailfish and now Lineage, but I clearly booted at the least at the end of each installation. I'm not quite sure how you could avoid the boots?

In your second dump i see ... ANOFFCHECKORUM (and in the first ALARUM) So my guess would be that the second is only active when the device is sleeping / the screen off, that is to wake the device to do something?? See also e.g. this https://groups.google.com/forum/#!topic/tasker/sms3Kt2inzY So these really are questions belonging in the Tasker forum not the Pro1 ;)

It was only after a reboot/power up I have seen it. So unless the device have rebooted during the night, it sounds like a different bug.

There was a bug that if we were too slow in entering password/pin it rebooted. But that ought to be remedied in firmware quite a while back. So a little surprised you see it.

Indeed, I will strongly recommend FinQwerty over stock layouts. (Note that it is not an active app, it is just presenting the system with pre-made layout files)

The Stock maps for US qwertY and German qwertZ can be found here https://android.onse.fi/finqwerty/#pro1

The question/request have been raised before, and I'm no expert on this. The A/B system as I understand it is normally used to apply new updates, so one can be flashed while the other is still active. The LineageOS setup offered use it slightly different with a recovery image in A and the main image in B If I got it right there would also be a certification issue for stock android with multi boot. So some apps would complain. (Typically bank-apps and the like, fearing the potentially compromised security) But in principle it should be possible.

The layouts (currently) offered can be found described here: https://android.onse.fi/finqwerty/#pro1 e.g.

Are you sure you follow TDM's guide to the letter? I made a batch file for it, see this:

You have limited the shipping to Germany. But the qwertZ variant is interesting to a broader audience than that. Any language with national letters usually right of L and P is likely to be better matched with the qwertZ layout than the shifted qwertY. See FinQWERTY