Leaderboard

Alright qwertz folks, here's another test boot image. Please try and let me know how the keyboard works. Most keys should be correct, but I may have made a mistake or two... http://files.nwwn.com/android/pro1/boot-qwertz-test2.img Note that I have added a flag for AltGr = 0x1000. So we have: 0x8000 = shift (left shift) 0x4000 = ctrl (left ctrl) 0x2000 = alt (left alt) 0x1000 = altgr (right alt) Note there is only space for one more flag. If more flags are needed, I will probably expand the codes from 16 bits to 32 bits.

Okay I see what's going on with QWERTZ now. All of the incorrect keys (except possibly apostrophe) are accessed via AltGr. So I'll add that as a modifier in my driver and redo the layout for these keys. I should have a new boot image later today.

Thanks a lot! Seems to be mostly correct. I guess the yellow-key pluss l should give ' (apostrophe), at moment it gives ' (acute accent) if my eyes see them correctly Also yellow-key pluss ü gives ~ but for it to be really usefull should give dead_tilde... Thanks again for a great progress!

Since about February I decided to close the tab on my browser session that was permanently open on this topic. I stopped using the forum altogether. Today another "wait a little longer" email came through. Decided to check things out here. Good to know some of us (not me yet) got a stock assigned email. So we're still moving along. Power to the keyboard!

The Dux Ducis Universal case arrived (this is the 5.5-6" version of course). Overall not great, not terrible. The Pro 1 is just way too thick of a phone lol. In size it's almost identical to my Priv case which is very good because the previous Puro case was considerably bigger to the point it was almost very pocket unfriendly, just like that pre-order pouch. I put the Huawei P20 Pro silicone on the glue, it holds alright. (sorry about my horrible cutouts..sadly I don't have precision tools and this was done with small scissors) Sadly the case can't close na

I am from Austria. I think there is no logic behind who gets their phone in what batch. But on the flip side support already wrote me that the refund is in progess.

Yes, but 8th of June is definitively Monday, so I am optimistic. 🙂 It seems to be only a small "typo".

Audio issues in cars can be difficult, both because it is more challenging to get logs (most folks don't carry their laptops with them in the car) and because each car manufacturer seems to have their own unique BT implementation. First question, how does stock behave? Second question, are you able to get a logcat of this happening? EDIT: Also, please file an issue on github. Issues get lost easily on the forum.

I am not very familiar with international keyboards. It is only through this project that I even learned the basics about how non-US keyboards worked. But I'm learning. 🙂 Unfortunately, keyboards are hard. There are multiple layers of translation involved from the physical key press to what you see on the screen. The kernel keymap is the lowest level, which makes it difficult to choose the correct values that generate the symbol you wish to see. I've downloaded your attached file and each line has three symbols on the left and a comment on the right. I presume th

In the meantime I am doing another case experiment. This time it's the Dux Ducis Universal case. This one really doesn't seem it needs any tinkering since you can fold it to access the camera. Although directly gluing the phone inside seems a bit sketchy...so I also ordered a Huawei P20 Pro soft case based on @EskeRahn's experiments. So in case the adhesive lets go there will be still some bumper protection. So the idea is, pop the phone in the silicone and insert it in the flip case like that. Hopefully there will be enough space for it to fit comfortably so I ca

I honestly think you are jumping the gun—not that they shouldn't be faster, but they have a limited staff still working from home and it takes them a while to get through all the email that comes in. You can try invoking @Erik here and see if he can elevate it. I believe from others' experience that you will get the refund.

Is Pro1's signal strength similar or weaker than on the other phones? This question was motivated by a user selling his phone because of weak 4G antenna and Pro1 being unusable indoors as a phone where other phones worked. There are many websites explaining how to check signal strength on an Android phone. This one is from 2010 but later articles have similar instructions. How To Measure Cell Signal Strength on Android Phones "If you want to check out just where you are at in raw numbers, you can check the status screen in Android's menu. Just pull up the menu, scroll down and s

This looks interesting: 06-04 13:52:08.223 731 1420 D voice : voice_start_usecase: enter usecase:voicemmode1-call 06-04 13:52:08.224 731 1420 D audio_hw_primary: select_devices for use case (voicemmode1-call) 06-04 13:52:08.224 731 1420 D audio_hw_extn: audio_extn_should_use_handset_anc: AANC enabled in the property 06-04 13:52:08.224 731 1420 D audio_hw_extn: audio_extn_should_use_handset_anc: AANC enabled in the property 06-04 13:52:08.224 731 1420 D audio_hw_primary: select_devices: out_snd_device(15: voice-handset) in_snd_device(72: handset-mic) I

Nice to see you here @CornholioGSM. I would have delivered you first. My whole family and friends (and myself) owe you a lot. I cancelled my order a long time ago because I was not satisfied with the communication from FxTec and the price for the device is now too high. Sadly I now have a more modern mobile phone for 200€ - unfortunately without keyboard. Greeting Dany

I'm from Germany with order #36xxx for a QWERTZ device, though mine wasn't in this batch yet. But I got this new message: Hello! We hope you are well and keeping safe. With the factory returning to normal production speeds, we are making steady progress working through remaining orders. The factory has confirmed a small batch of Pro1’s is ready to leave the factory, and those that have been allocated stock should now have received a shipping update. We are currently negotiating shipment releases on a 2-3 week basis with the factory, and will be in touch when the next shipment is ready.

Okay, I did a logcat with the pro1 connecting to my car (BT name is "Audi A1"). From what I can tell the call starts at 06-04 13:52:06.897 I did cut several hours of stuff from this morning - still very verbose. Hope this helps for now. I'll see if I can set up a proper strategy for doing a full backup and restore, so I can test with stock. logcat_BT.txt

Well this might be a reason, BUT!! I am from Czech Republic. And that is not the opposit side of the globe - we even have quite long borders with Germany 😄 😄 We are neighbors 😄 😄

I am from Germany, and nothing was sent to me. Order 542XX QWERTZ. Otherwise, I ordered in February 20. So not a long wait yet... 🤭

Unfortunately not. 😞 This generates qQ" eg yellow-arrow + q generates ". If you look at the current keymap (/sys/bus/i2c/drivers/aw9523b/6-0058/keymap), then you can find a line "60:0003:8003" - it is for key 2 and 8003 generates " as it should do. Actually that kind of problem restricted the keys I was able to adjust to these I posted in issue35 😉 However @ can be generated with the help of Sym key. Sym + q generates @. 😉 And all other these still missing yellow keys which should be mapped to "yellow-arrow"... Created a file symkey.txt which describes the current Sym key mappin

I am part of the batch and in France, so it's not just for Germans (it is however possible that they send it to France through Germany, that's not uncommon). I am however getting slightly worried that I have the only QWERTY in that batch. I'll trust them not to have sent the wrong layout, but I can't help wondering. 😄

In another thread they tried a igniter against it to help revive the screen maybe that will help? Loads of videos on you tube

Please note that the QWERTZ and QWERTY version of the Prpo1 are COMPLETELY identical internally, the ONLY difference is what is printed on the keys. So you can test qwertZ on a qwertY Pro1 (or vice versa). (Obviously testing like this is slightly confusing as the qwertY letter print is shifted compared to the qwertZ)

Would you please tell me, where are you from, @ChopSuey133? Just gessing whether the whole batch could have been sent to Germany.. Otherwise I can not understand, why some orders were skipped - e.g. mine or yours.. My only explanation for now is, that the whole batch went to Germany. I am not German.. How about you?

Basically international layouts were based on US keyboard map but some of the keys, mostly non-alphanumeric ones were changed (as we have more alphanumeric letters than in English). They kept CTRL + ALT, in Hungarian layout, their name are the same, in German layout, they were renamed (but still the same). The "Alt Gr" key is an additional modifier, which is technically the right Alt button on US keyboard. For example, in Hungarian layout, "[" and "]" can be reached by pressing AltGr+F,G and "{" and "}" by pressing AltGr+B,N and also Z / Y are interchanged and 0 moved to the right of

Order #292xx, qwertz ordered and paid on August 2nd 2019. Still nothing after 10 months. I will ask for a refund now, fed up with it.

Got the Mail too for a QWERTZ order #38XXXX bought and paid 12. October 2019

Likely. I just spent an hour or two setting up my new Nokia 7.2, so I expect fxtec stock assignment any second now.

I discovered this the hard way....Got a P20 Pro stiff case thinking it would fit but nope. I was lucky it was cheap at least so not a big loss.

finally I got to testing, after getting some adapters and time first. The failure really comes from the screen, with a mouse it's working fine. With some testing I found out, that there is just a horizontal stripe where the touchscreen isn't working anymore, that's also why the input of the pattern failed, because if you get into this part, the phone will think your finger left the screen. Long story short, I need to get a new screen, at least there is no other major damage