okayphoneme

I put a matte screen protector on my devices these days. I don't care about the protective qualities, but the matte finish stops the screen turning into a smudgy mess and eliminates glare.

This is a very satisfying thread.

I would definitely be interested in this if the stickers are high quality. I like the idea of scraping off the black so the backlight shines through.

He gives the wrong price in the video, and also incorrectly states that you can use two SIMs and expandable storage at the same time.

There's a bit more info here: https://source.android.com/security/verifiedboot/device-state So your co-worker was right (the original key is permanently baked into the hardware), but you can also in theory supply another key to use. It guess this feature isn't widely implemented though (or at least, nobody cares / hasn't tried it) - supposedly OnePlus 5/5T and a Xiaomi phone in addition to Google's own devices.

Maybe it's limited to certain devices, but the Android docs mention this as a possibility (CopperheadOS / GrapheneOS uses it). If you provide a key when the bootloader is unlocked, then it should be possible to install signed updates after relocking.

I'm mostly concerned with the facts. Either the claims are true or not... Verified Boot does concern me. It's not absolutely critical, but I'd like to have it running if possible and didn't, in fact, realise that LineageOS was missing this functionality at first. Ideally I would like to have built and signed releases myself using my own keys. Ok, fair enough, Of course, I completely agree. Are the idealte bits not used at all for Lineage?

There are some concerns raised here, for example - I don't know if they still apply, one year later: https://www.reddit.com/r/CopperheadOS/comments/917yab/can_anyone_technically_explain_why_lineageos_as/

I appreciate the explanation, thank you. I've been reading up on Lineage and I'm not super keen on it now - the project seems to put an emphasis on features over security - which is fine, but I think I'm actually interested in using something like the Ungoogled ROM you've posted here. The thing is, I'd like to make some modifications to it (entirely for my own purposes). I can see the stuff in the Android source that I would change but my knowledge of how the whole thing slots together is rather limited. My question is: is there a way of merging in the proprietary (binary) bits of th

I see. So Lineage in theory does everything that the BSP does, but is an open source implementation?

Is the source available for this so we can build it ourselves?

There are apps that can do this by setting a security policy on the device, e.g.: https://f-droid.org/en/packages/net.zygotelabs.locker/ Unfortunately, there's no mention of any protection against accidental login attempts (like BlackBerry has). So use with caution.

Clove have a review up:

Just because they have always been different doesn't mean they should be. Why does there need to be a learning curve? If the keyboard does something magic that is worth the effort to learn, that's one thing, but moving things around is a totally useless innovation. In the past, phone makers had the valid excuse that there simply wasn't enough room for the standard layout with all the keys -- or it could even be argued that the target audience, mainstream users, didn't need all the symbols. Now we have a full keyboard which even has duplicate keys and yet things aren't in the right place. With

It is different. Unless you're buying a keyboard with some weird layout -- which, I did once, by the way, and the experience was enough ensure I will never make the same mistake again (the change wasn't even as severe as the Pro1). Besides, most of us aren't switching to the Pro1 layout - we have to use it simultaneously with machine(s) with the correct layout. Even if the new layout can be learned well, there has to be a loss of efficiency somewhere.

So what is the notification LED like? Does anyone share OP's concerns about it?

I'm still agonising over whether to buy the Pro1. There are a lot of great things about it, but I just can't get accept the bad keyboard layout. I was considering getting the QWERTZ model and having some vinyl stickers made up to change the remaining keys - but it seems ridiculous to spend so much on a phone and then put some crummy stickers on it. The worst thing is that this hack would hide the backlight on the keys (ultimately why I've given up on the idea). I tolerated the N900's limited layout, but the N900 was a much smaller device and there really wasn't enough room to have everything 1

I'd be interested to know how quickly / easily you adapt to the shifted keyboard - I'm still undecided on whether to follow go with the QWERTZ version myself.

The main problem with BlackBerry for me is that they lock down the phones so they can't run custom software - it's nice from a security perspective but when your two years (or less, depending on where in the release cycle you buy) of software updates is up, you have a slowly ageing phone stuck in an otherwise perfectly usable shell. For me, the appeal of the Pro1 is the combination of the keyboard (+ other stuff) AND the openness in terms of software.

Well, we have Verified Boot for this, which is where each part of the system is checked (with a key stored in the hardware) before it is loaded. This is what happens with an OEM ROM on most(?) phones, but you lose that when you unlock. Google Pixel phones (uniquely, as far as I know) have a way of supplying another key so that you can actually run this process with a custom ROM that you have signed yourself (or a ROM that's signed by the publisher). In addition, I believe you're given a fingerprint of the current OS on boot so you can, if you're paying attention, detect if anything has be

Whenever anyone raises these concerns about security, there are always folks who chime in to say they don't mind the risks, and that is perfectly fine and understandable, and maybe it is a reasonable position to take if you don't put sensitive things on your phone, but I for one care about security and privacy and you need a strong foundation to build these things on. Encryption only covers user data, not the system files, and as I mentioned above, there are attacks which may be able to extract keys from a device with an unlocked bootloader. Most Android users are using PINs / patterns or

The harm is that someone can install stuff on your phone if they have physical access to it. In the past, there have been attacks where crypto keys were recovered from unlocked devices (and locking it would have protected against the attack), for example.

This should work with any custom ROM, right?

Awesome, thanks!

I understand that the Pro1 comes with an unlocked bootloader. This is great for installing other operating systems, but leaving the bootloader unlocked is a massive security liability. Is it possible to lock down the bootloader?