FlyingAntero

Weird issue indeed. I have not faced anything like that with my Pro1. Maybe you could try to reflash stock firmware via fastboot? I have no other ideas but sometimes reflashing can fix weird software issue.

Have you asked replacement board from F(x)tec? I was able to buy a spare part the fix the issue. Also, you could just to reinsert the usb board cable since it might be loose. However, I would not feel comfortable to teardown the phone if spare parts are not available. One option is to resolder only the usb connector but it can be very hard task. In addition to that, I have seen some people to "bypass" usb connector with wireless charging receiver on other phones. It could be easier soldering task and you could at least charge the phone even so that usb connector itself is not working. (As

It is quite complicated system indeed. My initial idea was to use german layout and make only couple changes so that letters would mostly match prints. Instead, I need to select finnish and make several changes under the hood to achieve that (via custom keymap)? Mission can be completed but it is longer route. If I only select finnish, the layout is mostly good. I just keep forgetting where the special characters are since they do not match prints anymore. That is what I want to fix. Actually, I am pretty happy by swapping only Z <-> Y since Å is not that important for me.

Nice start, I managed to swap Y and Z letters. However, I don't understand where the codes come from? I know the decimal hex thing but where I can find the correct code for Å letter? It is not listed in the source page. I found some info from here: - https://community.bistudio.com/wiki/DIK_KeyCodes According to the link above, decimal for Ü is 26. So the hex value is 001a. That matches for the key 28 from stock QWERTZ file. But how I know the correct hex value for Å? 28:001a:101b is Ü and ü Unicode hex value for Ü is U+00DC so it is not the same. I am little bit lost now. I

So, it is possible to make custom keymaps since LOS 18.1 without root? I am planning to make minor modification to stock QWERTZ german layout in order to use it as scandic. - Y <-> Z - Ü -> Å All I need to do is to place my custom keymap to /data/system/keyboard/keymap and then active custom keymap via settings? Is there stock keymap available somewhere in correct format so it would ne easy to make modifications? I am planning to go as close to printed labels as possible.

That is something I was thinking about. China uses mostly different LTE technology (TDD) and FDD B3 band is not that so common there. I don't know if that affects somehow. Maybe devs in China cannot reproduce the issues? One idea is that TDD does not use freq below 1880Mhz in China. B3 (EU) and B4 bands (US) uses 1700-1800Mhz for uplink (as GSM 1800Mhz also). Maybe we can narrow down the issue to 1700-1800 freqs? I am still just guessing... - https://www.phonearena.com/news/Cheat-sheet-which-4G-LTE-bands-do-AT-T-Verizon-T-Mobile-and-Sprint-use-in-the-USA_id77933 There a

BTW, interesting that you mentioned Xiaomi since several people have reported exactly same issues on their Xiaomi devices in my country. Some user sent their phones to the warranty service but no luck even after changing the board. Temporary fix was to reboot device or use air plane mode for a while. But now people are reporting that leaving 5G out of preferred network type selection have fixed the issue for good. (If I have understand correctly 5G NSA uses LTE for sending data) Probably this has nothing to do with Pro1-X but might be still good to leave 5G out of preferred network type s

Yeah, I was too general with my statement. Some countries have shut down 3G in EU but in many countries it is still available. In Finland, 3G is available to the end this year since operators started to shut down 3G just recently. Your situation highlights my theory, since you do not have 3G and maybe LTE band 3 (1800Mhz) is used in your area? So you could have same situation than in the US. I might be wrong though...

I have been reading all reports in this thread and issues seems to be mostly related to LTE network. However, there are also reports that some users cannot make calls in GSM network either (or especially receive calls). If LTE is disabled and 3G is available then there are no issues reported. @Rasvahas reported that Pro1-X has issues with LTE band 3 which is 1800Mhz. 1800Mhz is also very common in a GSM network. There are lot of issues reported from US. 1800Mhz is not used there but band 2 1900Mhz and band 4 1700Mhz are very common in US. Also, 1900Mhz GSM is used in North America. W

We are all waiting fixes for possible issues but it does not mean that developing other things has to be stopped. Probably there are different people working with software updates and case design. Or maybe the case was developed with the help of community? Anyway it is not bad thing that there is case model for Pro1-X. Community option:

It arrived and looks awesome 😎

Definitely F(x)tec is NOT scamming us. They are just struggling with this project and things have not gone as they planned (SoC change etc). Sure, F(x)tec has done mistakes during the journey but I think that they are trying very hard with limited resources. I received my Pro1 after long wait and during this week I am supposed to receive Pro1-X. Let's see how it works compared to Pro1.

I have an old ProBook 6360b laptop running Windows 10 and Ubuntu (dual boot). Mostly I am using Windows for flashing since I am more familiar with that environment. Just need to find correct drivers before you can flash anything. I have not had any issues with Pro1 or other phones. It just works! I guess that I will never throw Probook away. I even upgraded the CPU to quad core. EDIT: And always use the original cables that came with the phone! At least that is what I do.

You might have triggered the "HDMI bug" on the Pro1 because Pro1 is much more faster phone than Pro1-X. When I plug Pro1 to monitor via HDMI performance start to lag after locking and unlocking the screen. For some reason the chip cannot maintain good performance even so that thermals are not an issue. When you turn off and restart the phone it will be fixed. Unplugging HDMI cable does not fix it. There might be some other thing that triggers the bug also but I have only noticed HDMI. Gaming performance on Pro1 without bug Gaming performance on Pro1 with bug As you c

It is now on eBay but feel free to contact me for direct sell. The price is negotiable. Edit: sold

I was so close 😅! My content count was 458. But I think that it is good feature for all. No matter what the content count is. Now we just need to figure out how new members know add details 😅

Still cannot see "member title". I activated desktop mode on browser but I can see only about me and birthday fields.

I may be dumb but I cannot find "member title" field. I have only birthday and about me fields. Am I missing something?

I think that you should be able to make automation to change keyboard app in portrait and landscape position. So then you can use Swiftkey for landscape and other keyboard for portrait if you prefer so. See my previous posts below: https://community.fxtec.com/topic/2557-key-mapper-foss-app-to-bind-keys-buttons-to-other-keys-or-actions/page/2/?tab=comments#comment-45552

Updated to latest version also. I can confirm that the SIM card lock screen bypass vulnerability is now fixed. (But my Zenfone 9 is still vulnerable with stock firmware)

According to user reports, Lineage OS is affected of the bug below. However, vulnerability should be patched in the November security update. - https://9to5google.com/2022/11/10/pixel-lockscreen-unlock-bug/

Just installed LOS 19.1 to my Pro1 also. Everything is good so far.

I was using Pro1 as a daily driver for over a year but since COVID-19 changed everything (and official support for Pro1 ended) I switched to a Asus Zenfone 8 (and later on to 9). Since I was working from home there was not so much need for handheld keyboard phone anymore. I was able to use laptop almost every time I needed. Now situation has settled back to normal so I am planning to start using Pro1 (or Pro1-X) as a daily driver once again. I haven't decided which phone I will grap when I receive Pro1-X. Pro1 offers more performance which is great since I am gaming a little bit. However,

I was actually not aware that Pro1-X has only 1 year warranty. I am so used to 2 year warranty here in Finland. Even iPhones have 2 years "fault liability" by law despite that Apple only provides 1 year. Regarding Lineage OS I am pretty confident that Pro1-X will have official status later on. It can take some time and Pro1 did not have official status right away. It came little bit later after first builds.

You are so close to the warranty period that I would still ask for repair. Maybe they will do with for goodwill. And if you preordered the phone I think that it is reasonable to calculate warranty period from the receiving date and not order date.