david

That doesn't appear to work on my version of Cyanogenmod on my Relay 4G.

What are some of the key features LOS has that stock does not that you like? I've been running Cyanogenmod (KitKat equivalent) on my Relay 4G for years, so I'm not up on specific additional features in LOS and how those differ from modern Android versions.

I have to say, I'm really surprised they didn't send a single phone to all remote warehouses many months ago, to work out the bugs in the shipping process (such as customs issues). Good lesson for the next version of the phone and for other start-ups.

Jerk. 😉 Sorry, couldn't resist!

Live in Minnesota long enough, and you can wear short sleeves any time of year. 😉

I suppose that is possible. And I agree with Grandma. 😉

Interesting that it didn't seem to affect the first batch. If it did, you would think the second batch wouldn't have been assembled until the problem was resolved. If it didn't affect the first batch, then there is a question of why it didn't. Unless they didn't notice the issue at all, and some people have screen bleed on 1st batch phones. It might be such a minor issue that it isn't noticeable, but fxtec felt the need to correct it when they found it in the second batch. (all this is speculation)

My email did not say how big the second batch was. I'm just speculating that it wasn't nearly as big as they had communicated it to be in the weeks before it was shipped. Although I'd really like to have my phone and I'm not happy with how things have gone and how they have been communicated, what I'm really concerned about is the financial impact it will have to fxtec to miss Christmas for general availability. Getting someone a phone that won't be there by Christmas is infinitely different than one that will be. I can see them losing a lot of sales by not reaching general availabili

I am curious what you see as the main benefits of using file based encryption instead of full disk encryption? And any idea why fxtec went with FDE?

My email said that all assignment emails have already been sent out. I guess there could be a *lot* of people who received the assignment emails and just didn't share them. But the number of people who shared them on here seems extra small. And some of those people were 1st batch people, which if we are to understand one of the recent updates correctly, did not affect the true batch 2 size, other than adding to it.

I received the same email from support, about me not being in the second batch, despite having a 7xxx order number and paying July 31st (no coupon). It sure doesn't seem like they are assigning phones to people based only on payment date and coupons. And it sure doesn't seem like many people are in the 2nd batch. It makes me wonder if the screen issues shrunk the 2nd batch size to a very small number, and those are what were sent out.

Yeah having the recovery partition separate makes changing recoveries a lot easier.

The data partition is still shared, so you need operating systems that don't have any conflicting information in the data partition, which generally means it needs to be the same OS. I don't know if LOS and Android would be close enough to allow for this. I haven't researched if anyone out there has done it. As for how to manually switch partitions, you do it with fastboot: fastboot --set-active=a or fastboot --set-active=b As for knowing which partition is currently active, so that you know which one to switch to, that is done with: fastboot getvar all Look

Yes, that is a big benefit of the A/B design. Another is that you can fully use the phone while the update is happening, without rebooting, since the files aren't in use on the other partition. When you are ready to switch to the new version, you can reboot at a time that makes sense for you, and come back up on the other partition.

We are talking about how to test new screens that we buy in order to have them available to us for if/when our original screens fail or break.

I will probably wait until the warranty period is over and then test any replacement screens I have, without sealing it back up completely. Light bleed on other phones/TVs looks like uneven brightness at the edges of the display and can be large or small in the area where they occur. Think of a black screen, but where it is not black in a semi-circle at various spots along the edge. That is what I have seen other people report with other devices/TVs. I just don't know if it was from day 1 or after extended use.

Posting a link here regarding a discussion on screen issues in the production assembly line, which relates to repairability for our home assembly lines of the future:

Does anyone have first hand experience with an OLED screen having light bleed? If so, I am curious about the following: - Does the screen have light bleed only after being used for some period of time, or from the time it is born? - Is it not possible to plug a screen into a test machine before installing it in a phone and needing to go through a lengthy and costly process of disassembling the phone to replace it with another untested screen? It seems to me that testing each screen, outside of a phone (or at least outside of a locked down, fully assembled phone...maybe the test

Wow! You just hit another one of my pet peeves. https://youtu.be/dechvhb0Meo

That type of thing drives me crazy.

Yeah, I just meant whether you could tell from feeling the plastic whether it looks better or worse for protection and for clarity.

Have you tried plugging it in when the battery is at 0%? Does it allow it to start, or does it use so much power on starting that it sucks the battery down and you get stuck in a loop? This could be exacerbated by plugging it into a slower charger (like a USB port on a computer).

Ah, okay. Thanks for the clarification. Just looking at it, does it seem like it is better or worse than the ones you (and I) bought from China?

Really? It looks completely flat in the pictures. Is it formed in a curve, or does it just wrap around the curves of the screen?