Craig

There's quite a few variations that are more like hubs than just usb-hdmi. If you want to use it as a video player to a tv, I suggest look for one you can also charge from (they'll have a usb-c input to hook up charger). Some of them will have built in usb hub or sd-card slots, etc.

Wonder what percentage of workers show up on Monday; I think it's the first day they're allowed back, but maybe also the first day they're allowed to travel? Haven't paid attention to current travel restrictions.... I bet they'll be very short-staffed.

Pretty sure that comes along with setting our keyboard to 'alpha' (along with sticky modifiers and suggestions), which hopefully is in the next ota.

wow. didnt no nano came with lineage. live and learn.

When you say tested in nano, what you do mean? Is there nano for android terminal now? Otherwise, you mean termux, and termux uses its own keymap anyway so not good place to test keyboard layouts. Use android terminal.

Actually, it's a known issue that camera button launches the snapdragon camera, not default camera. One can use something like keymapper to change that behavior for now. But, using the button as a shutter doesn't seem to work for any camera app I've tried. The half-press for focus does work on open camera. But no shutter.

I thought some apps could do already do this. Try VLC, see if it can do it on a 16:9 video.

Even if it has been discussed, it hasn't been added to the community buglist yet. I didnt know ring volume and notification volume couldn't be controlled independently; is that standard android pie behavior? Or a bug fxtec somehow introduced? Or user error?

Actually, you will have an issue with that setup. You won't be able to type question mark, slash, or £. The layouts included with our phone don't take advantage of Fn(slant arrow) key. If you install finqwerty, it adds a bunch of layouts designed specifically for our phone that will work. Alternatively, if you select NO layout, then shift wont work, but you can get all the yellow symbols with Fn including slash and question mark, but no pound.

Check the date code in your version, in settings/about somewhere. If its 2020-01-06 I think that's the lastest. You could also check for updates, it'll tell you then if there are any more.

Bummer. Well hopefully the next OTA F(x)tec's programmer fixes at least one of the two things. If they define the keyboard as alpha instead of full, we'll get predictions (and longpress on letters gets us alternative character choices). If they define a key (ideally Fx logo key) as meta, we get global keyboard shortcuts. They could even define the sym key as right-alt, and then we probably even get a pop-up symbol keyboard. My understanding is F(x)tec's contracter who did our firmware didn't even try to take advantage of any of Androids built in keyboard stuff and tried to re-invent the

The launcher shortcuts are activated by longpress of the shortcut key. The built-in android global shortcuts meta+key cannot be used cuz fxtec didn't assign any key to meta by default. For now only launcher shortcuts if you use their launcher.

https://cobalt232.github.io/blackberrymanager/ You can install the blackberry hub email client from there. I havent used it but somebody else on here recommended it... You can disable gestures in the settings menu, that gets you the three traditional android buttons that are more familiar to most than the pie gestures.

voldown+power button for bootloader, or fastboot wont see it

there is a way to enable charging while off, that might help

They apparently didn't implement it (yet)?; they'd have to assign Fxtec key as 'meta' for those to work - if I understand right. There are some keyboard shortcuts you can assign in the stock launcher, that activate on long press of keys.

Earlier today I saw mccreary post elsewhere that he updated the GSI test files (same link as in the first post) and if the changes he's been talking about are working, it should be getting pretty good by now.

We really need stickies in this forum for info like this. I only really learned this here myself. Now, if I'm going to charge overnight, I use an older slow charger (or from a PC i leave on overnight). Quick charger is now reserved for when I'm getting ready to go out and see my phone isn't full enough, as it can add a lot of charge real quick.

I gave it my best effort, but I think I'm stuck. But I really dunno what I'm doing. https://pastecode.xyz/view/240b6214#L340 I even built sdl12-compat successfully, but it in the end, it still manages to complain about sdl - and other things that I don't know how to deal with. But yeah, ask some TMO guy who has done this before, they'll probably get farther than me.

Added and entry to the community buglist. I think now somebody else is supposed to confirm it? Anyway feel free to add details if you want. https://docs.google.com/spreadsheets/d/15uE12Yv5nMvIF42U33cY5FQoF6M66QIn00cC876uf7Y/edit#gid=0

Right, but the only thing that appears to be not working is decryption. Everything else seems to work already. That was the point.

Anyone tried Sprint yet?

I've been anxiously waiting for some in the US to try getting Pro¹ activated on Sprint proper. Even with this latest shipment, I haven't seen any reports of anyone trying. If you've tried US Sprint, please post your results!

I'm dragging this thread off topic. It has to already be decrypted for it to backup. For example it can be used to backup sailfishos. Then, for example,one could use fastboot to flash android,then when done, flash twrp, wipe, and restore sfos backup, exactly the way it was before.

Yes, current version of twrp cannot decrypt Android. It can't help with any Android problems right now.