david

The clock app is not black. It is gray.

If anyone wants to do it in stock, you can use @elvissteinjr's tasker profile (https://community.fxtec.com/topic/2283-tasker/?do=findComment&comment=45359) and create a quick settings item for the task used in that profile. That will turn on the keyboard backlight. You can create a similar task that sends keyevent 135 to turn off the physical keyboard and add that as a quick settings item too. It could be made a toggle, with some use of variables and if/then logic in the task.

I don't know if it is only happening on my phone, but when I take a video with the BSG GCam port, after I hit stop and it acts like it is writing it, I can't get to it through the thumbnail. When I tap on that, I get a blank view with a camera icon over it. When I go into the gallery or google photos, it isn't there. However, if I take a still picture and then go into one of the grid views, it is somehow found by the system and it shows up in the grid. If I go into a file explorer program after taking a video, the file is there. Once opening it that way, it again will show up in the

@Adrienspawn, or anyone else who is using the BSG GCam port, can you take and save videos? Mine records, but then doesn't save it anywhere. 😞

Are you in CA? If so, I had no idea. Lol

Yep. Not ragging on the Pro1, necessarily, but it really is crazy, that as an industry, we worked our way up to these fabulous flat screens and square corners and then took a step backwards with rounded screens and rounded corners! LOL There is *no* video content, that I'm aware of, that is shot with rounded corners! LOL To the point about the short edges being different than the long edges, it would be nice if we could specify each of the 4 edges independently and have it know that we mean the same physical edges when it is rotated (or not, if one wants to have options). I'm speaking

I should mention that this may have been @EskeRahn's idea originally. I don't remember. I do remember discussing it with him. And @Craig may have come up with it even before then for all I know. 🙂

It didn't in my experiences. But, in general, the magic in GCam does seem to revolve around taking many pictures in the background and doing some magical processing on them to come up with a good looking composite picture, so it can be slower, depending on the mode used. If you use regular HDR+, that's faster than HDR+ Enhanced, for instance, but the output isn't as good in difficult situations. Of course, I'm speaking in nitpicky terms. All of this is much better than the camera sensors and software of several years ago, which is what I am transitioning from. 🙂 This is the GCam p

Yeah, as you said, and others as well, I'm just drawing a distinction in the world of landscape keyboard phones between those that slide and those that have hinge mechanisms. My Relay 4G was a slider. The two halves slide on rails. The Pro1 has its hinge mechanism, where the top part pivots up and away from the bottom part. My T-Mobile G2 (HTC Desire Z) has hinges too, but it lies flat after it pivots up, instead of the angle of the Pro1. As I was playing with it just now, I realized that it is like a mini-Pro1 in that the sound is similar. It isn't quiet like the slider. It is easi

Still slower for me than a slider. It isn't a deal breaker. It is just different. Sliders are just quieter.

I've never done it, since I have been on older androids. I thought it was something unique to the Pro1. Although, now that I mention it, I might have seen it on a Samsung tablet once. I have no idea what The Square is, so I'll have to Google it. EDIT: Oh, *that* square. The overview/task switcher virtual button.

So *that* is why it didn't work for me. I first tried it *after* installing SwiftKey. Related to this, how do you do split screen?

I will say that it is easier to open a slider quickly and *quietly* than the Pro1. It can be opened quietly, but it takes more time. The sliders I have used are relatively quiet when opened.

I believe this is a known issue -- with T-mobile, anyway. I Googled it, but a not clear if Ting still uses Tmobile or has switched to Verizon.

The other reason is for aesthetics, so someone who doesn't want to see content on a curved display can have a flat display. Related to that, would be square corners, not rounded. Aesthetics are probably way down on the priority list, but just mentioning for the future. I have no idea if you have control over things like this, but the pull down menu that has all the system shortcuts in it does not fit the screen when in landscape mode with the default settings for screen size and font size. The edit and settings buttons are off screen and can barely be accessed by tapping the

This post from @Ilrilan has the link: If you do one OTA after your 20191203 image, then you would use the 20191210 image to do the special root process. Then you could test the process to get the final OTA. Alternatively, you can do 2 OTAs and then do the special root process with the 20200106 image file. But you won't be able to test if it allows OTAs until fxtec releases the next one.

😁 I didn't mean you doing it. I was curious if the published tool could do it. Then, someone who has stock and no OTAs could extract it. But, in reality, I don't think it buys much. Someone who has rooted on 20191203 with Magisk, has to unroot temporarily anyway, so they might as well just do the next OTA and use the boot image available online for that one or for the final one, and then reroot using the method that is OTA safe. For those who are on 20191203 stock, and who have not rooted, then they can just do one OTA first. @Kranchan, if you want the boot images needed

Unrooting shouldn't wipe the data partition, which is where your apps and data reside. If you do the "start from scratch" approach that @EskeRahn mentioned, then you will lose it all. Regardless of the method, would recommend backing up data/apps first, just in case. UPDATE: I *think* there is a way to modify the flash all script to not wipe /data. So there might be a way to start over and not lose data. But since you aren't stuck in a boot loop or something, I don't think that path is needed.

I think that one came from the factory, not from an OTA, hence why it is missing. Is there a reason you can't unroot temporarily? @tdm, does your EDL tool allow for extracting the images from a stock phone?

I don't use LOS yet, but just contributing ideas. With the dead zones, an option to change the physical resolution that is reported to apps would also be nice. That way, edge UI elements that a null solution would make inactive can be solved for. Another to add to the list is double tap on screen to wake it. I can't remember if that is already available.

I could not find 20191203 anywhere when I did this, so I had to do one OTA first and then use the boot image from that, from what someone shared, to give magisk something to patch that matched the current image. The trick, @Kranchan, is that you have to let Magisk manager patch the boot image, so it has a backup copy. Then, later, when you want to do an OTA, use the MM feature to disable Magisk, which will put the backed up image back. Don't reboot. Do the OTA. Again, don't reboot. Have MM copy the patched version back. Now reboot. I am not positive, but if you can get a 201912

A step in the right direction: https://www.google.com/amp/s/www.howtogeek.com/659300/windows-10s-new-start-menu-may-kill-live-tiles-forever/amp/

Ah, ninja. I'll go look. Lol

EDIT: Sorry, thought you were asking about how the phone should work, not asking previous posters about how their phones are working.

How did you get unbricked?