Craig

I would think they have to applied one after the other, hence incremental....

I imagine you found the same script as me. The reason I think mine not have worked right right as I didn't use the procedure for incremental ota, which I think must be necessary. For anyone else playing with this, here is direct link to OTA file from the source: http://hwfotadown.mayitek.com/ota/root_data02_2/idealte/idealte8998_9.0/QX1000/en-US/other/QX1000_EEA_20200106110245_20200106-1105/2020010614044563241.zip And here is xda thread with tool to extract: https://forum.xda-developers.com/android/development/extract-files-ota-payload-bin-diff-t3959161

I've tried keymapper and lots of those type actions are supported. I'm sure button mapper is similar.

1. Two settings are relevant to this: A. In settings there are slider settings, these are settings specific to the keyboard. One says force landscape when keyboard open. If you turn this on, it'll work for the majority of apps. B. In quick-settings, you can turn on auto-rotation. This works for more apps than the force landscape slider setting, but some apps are still forced portrait no matter how you rotate. C. If you must turn apps landscape that are forced portrait, use split screen to put them on half the screen. 2. I havent played with this but I think it

fastboot devices works?

I had also ssumed this to mean they hope to manufacture the remaining ~60% before the factory shutdown, after 30% are shipped to customers next week (with the assumption 5-10% have been delivered or will be this week (which includes all three batches we know about and the two retailers we know about)).

I think I may end up with LOS in the end too, but I do want stock to be good out of the box. Anyways I've extracted the new boot.img from the ota payload, and just need to patch it with magisk manager. Unfrotunately, I'm running sailfishos right now so need someone else to do that... I've put the unpatched new boot image here: https://www102.zippyshare.com/v/vdReLyxO/file.html Will update this thread with a patched version soon as I can find someone to do it (hint hint Hook). update: magisk wouldn't patch it. unsure why. maybe I extracted wrong.

Exactly. If you take the new OTA (which will require first flashing boot.img from fxtec's flashall), it is suggested not to re-root (with the magisk patched image I shared) until a new patched boot.img is available, because the latest OTA may contain a newer boot.img than fxtec's original flashall. This will become available once FxTec provides an updated flashall, or someone figures out how to interecept it from the OTA, at which time we'll update this thread with new patched boot image. So if root is critical to you, just wait.

Yeah it seems the keymap diagrams are ahead of the release version. For example the sym to wake was committed 9 days ago, after last google play update, someone just pointed out to me. So I'll wait for a new version to try it again. https://github.com/anssih/finqwerty/commit/2505c7e35aa72d19df0ca06a92deb4cb45751843 @Anssi Hannula By the way, why not make SYM into KEYCODE_BACK (as opposed to keycode_wakeup) so it serves dual purposes. (We already have a home key with Fx.)

Different apps behave differently, another thing I noted. Try termux, apostrophe behaves dead in there (with finqwerty-us-intl)

I downloaded and tried the latest versions from the first post, I still get timeout trying to flash.

Yeah, that shows ¡ without shift, like he did in finqwerty. My pc keyboard definatately requires shift for both regular and upside down exlamation, they're opposite of that, weird...

[For those not familiar, a dead key is a key that doesnt advance when you type it, imagine a typewriter and typing é, you type ' first then e and it comes out é. but if you just want ' you have to type ' then space.]

right, but when using finqwerty-us-intl, apostrophe becomes a dead key. So if I use apostrophe normally as in English for contractions or possession, i would have to type an extra space, which I'm not used to and don't want to learn as I don't need dead keys in normal usage.

I decided to give FinQWERTY a try for English. Although I like it, it doesn't work right or solve any issues for me, so this is an opinion of why it isn't useful for me in its current implementation, doesn't mean others won't like it. I downloaded from play store; although described as open source it's not on f-droid (although is on git). First thing is - US International has dead keys by default. One thing this means is I can't use apostrophe normally. So this eliminates this layout for me as I have no need for dead keys, I rarely type accented characters besides é and get that witho

It's not the end users fault fxtec sold to retailers first. The end user did nothing wrong by buying from retailer. Once fxtec sold them to retailers, you think everyone should have boycotted those retailers? Those retailers did nothing wrong either. Anyone who cancelled a preorder to buy from a retailer only hurt fxtec, cuz fxtec presumably sold the retailers at some discount.

This thread got linked elsewhere, and reminded me of this, so I thought why not - New Poll: https://community.fxtec.com/topic/2598-poll-user-age-group/

This was done earlier: https://community.fxtec.com/topic/2357-age-group-of-users-for-pro1/ and ages 40+ won, but the age groups weren't equal sized. So let's try it again. Note usernames are private.

There are USB-C SDcard adapters. That's the only solution I can think of. I was just looking up hubs with sdcard slots myself, here's a couple examples of cheap ones I'm considering: https://www.amazon.com/gp/product/B07L4LW316 https://www.amazon.com/gp/product/B073QNWGLW While browsing, I did see ones that plug straight into phone (without the short attached cable), and I'd imagine sdcard only variant if you want something smaller than multiport hub.

I believe all that means is VZW will no longer activate devices that don't support volte, not that they won't support cdma on devices that do support volte (that they are willing to activate). That's been the case for a while.

This is no better than the way people have done it already, it's still not using the CDMA bands the device supports. Verizon needs to activate Pro¹ with all the radios including 2G/3G, not just 4G.

I'm just an observer, who sees one guy said 99.99% of Czech ppls use qwertz. But one prominent (in the keyboard phone community at least) Czech said he has always used qwerty. So, perhaps if that kinda buy bought a qwertz variant locally but wanted to use qwerty layout on it, that kinda person would be glad it was included in FinQwerty.

I think I posted this before. But I've never used another message board/forum where editing had a time limit. Sure, if someone changes something, it may mess up the other messages, but so what? instead of having 5 irrevelevant posts, it'll have 1 relevant post and 4 perhaps confusing outdated posts, but the relevant post shows it was edited on a certain date and the others have a date anyway, and if they wanted to, they coulda quoted the first message to show what they're replying to at the time they replied to it, to avoid people possibly thinking they posted something irrelevant in the pa

i haven't personally tested as I was waiting for the next ota to test, but in another thread someone reported having to reflash stock boot.img, take ota, then reflash magisk patched img. Slightly inconvenient, but not a showstopper, at this point. The potential problem is when ota includes a new kernel (new boot.img), unless we're provided with a new flashall, or twrp includes decryption by then, we'll be stuck (unless it's possible to intercept the boot.img from the ota).