Leaderboard

I'm working on the changes to allow selecting qwertz in the kernel hardware key map. I should have something to test tomorrow.

Hello. If any of you experienced poor sound quality, here comes the solution! Our Pro1 definitely has some problems with sound quality. In particular it couldn't play 24-bit audio sources in more advanced audio players, like PowerAmp (16-bit played quietly on headpones causes a lot of hiss/noise). I also found some annoying clicks on some games (i.e. Talisman). These problems are caused by Snapdragon 835 energy savings, which disable high quality DAC chip and switches it to some limited operation mode. The apk I attached can enable hq sound. After installation 24-bit playback on Powe

You win!

Although its's more of FedEX issue but I will pushing / checking with out logistics partner see if there is anything we could do to speed that up. That seems rediculous to me as well!

Done. Feel free to edit the doc yourself though 😄

Thank you, so much! (Receiving an award) I'd like to thank my manager, my parents, all my colleagues and also folks at F(x)tec for making this possible. (Applause and music) ... Who's next? 😉

Thanks for including the link to the dev page. Installing a "random" APK from a google drive that requires root doesn't seem safe. Not that I particularly trust it now that I have the dev page though, would've preferred to see the source code or something. But thanks.

I got a black carbon fiber skin from Skinomi for the Note 10, and the back piece is a pretty good fit. The camera and sensor holes are in the right place, although quite a bit larger than they need to be. I filled in some of the gap using other pieces from the kit. I also clipped the corners on the skin, much more than I needed to it turns out, but overall I'm pleased with the result. It looks nice, and it definitely makes the device much more "grippy" to hold.

Okay all you qwertz folks, here's a Lineage boot image with my new keyboard driver: files.nwwn.com/android/pro1/boot-newkeyboard.img To use it, flash it to your boot partition, "fastboot flash boot boot-newkeyboard.img". Upon reboot the keyboard will have version 0002 which will make Android ignore the custom keymap file in the vendor partition. You will find the following files: /sys/devices/soc/c17a000.i2c/i2c-6/6-0058/layout This is the layout file. It can contain "qwerty" or "qwertz". So start by setting it to qwertz: echo "qwertz" > /sys/devices/so

I finally got a response today. Whew lads!

@Slion has the same, and added a bunch Jan 28th in this thread

See above pics. 1. Cut finger reader slot. 2. Volume cut little section out, slightly under case but works. 3. Power and Camera buttons are covered and work. 4. USB cut out 5. Top side (left) speaker cut out from existing hole 6. Hole punched with 'belt hole maker' near camera for secondary mic (needed to cancel echo on speaker phone. 7. Cut plastic holder from case and spun 180 degrees, need to open case to use camera. 8. Cut card slips from inner case. 9. Kept headphone hole covered to keep dust out. Don't use headphones. Picked up from lo

Is this the GPlay link? https://play.google.com/store/apps/details?id=androidexpert35.com.audioDACBooster Looks like it. EDIT: 'Contains Ads' 😞 EDIT EDIT: Seems the developer had a thread on XDA, but the account has since been disabled, and the thread closed due to 'piracy'. Sketchy IMO.

I think it "just works" - at least for QWERTY layout if you not select a specific layout. Specific layouts may also work. However, yellow-labeled keys should have some configurations because basically they are not necessarily there where they are written. For QWERTZ layout, keys should be remapped if lower level drivers are unmodified.

Hello all IGG supporter from Canada, just received the pro1 and all things considered it was worth the wait, the only issue I would consider reporting is the tinting effect that has been mentioned elsewhere in the forum. The default colour temperature is already cooler than I prefer, (thankfully this can be adjusted to taste via apps) however about 1/3 down the brightness slider the colours appear to suddenly get pulled even cooler (bluer?). It is noticeable when the auto brightness slides around. Other than that, fantastic device I'm glad Fx team put in the effort to build such a devic

Am from Singapore. Yes, this is a great idea.

Now we just need to find a business that offers padded phone testing rooms. :-)

There's always a way to fix it. Worst case you can restore to stock following Waxberry's thread. If you want real time help, try the discord chatroom https://discord.gg/BFGzMw7

Me: "I am so sick of this damned thing slipping out of my hand every time I pick it up. Hubby: "What do you want? Just something that will give you some grip?" Me: "Yes, but I don't want anything permanent. I want something that will come off cleanly with no residue." Hubby: "Are you looking for practical or pretty?" Me: "Functional. I don't care what it looks like." Hubby: "Let me work..." So I give you generic Ruggies and a perfect tactile grip that comes off clean, low profile, doesn't make the phone heat up.. And I am pretty sure with it looking like this NO ONE will be inte

It is Alt+Sym (it emulates a Keyboard-Open, that for unknown reasons sends F6 key code)

Okay all, I finally found some time to look at this some more. As it turns out, the xbl partitions are not actually being written by the current package due to a bug in the programming instructions. Or, well, a mismatch between what the programming instructions say and what my program expects it to say. Anyway, I'll fix this and have a new package up shortly. This should be able to fix the currently bricked devices (I know there are at least two out there at the moment).

Interesting, let me just tag @Waxberry to make it more likely that he sees it. 🙂

Got mine!, S/N 1018

on 1) I've been quite fond of VLC, and it works on the Pro1 too. on 2) You most likely have selected "US qwerty", the odd thing is that you shouldn't! De-select ALL tick-boxes to use stock F(x)tex qwerty. YES it is odd, but if you do it acts as Erik writes above, and the symbol over the numbers then needs the arrow and not Shift. You might want to have a look at the free open source project FinQWERTY that offers an extended keyboard experience over the stock one, not installing any fancy stuff, 'just' offering improved key-mappings. E.g. both the yellow arrow and shifts give access

[This is a temporary page while we setting up the support page guild and host files on our server.] The Fastboot restoration file can be downloaded in here. ADD: A newer file for 20200825 can be found here Preparation: You need to have a PC and installed universal ADB driver. Completely turn off the phone. Download the firmware and unfold and copy all the files into the adb folder which installed with the driver. Procedures: Hold Volume down + Power key together, when the logo shows up, release both fingers. The phone should boot into bootloade

Randomly the keyboard will continually repeat a letter once pressed. Stops once you hit another key. Same behaviour weather using hardware or on screen keyboard. Also noticed same behaviour on my Asus TX201LA when using hardware keyboard on android. Current GBoard input language is set to English (Australian) Current FxTec Pro1 input language is (Default) I am unsure if the input language is the issue or something else?

Does *not* happen here. Could that be launcher specific? I an using Launch Time. I also do not have auto-rotate on. Don't know what else might be a variable here.

Hi, When I power up the device with keyboard opened, screen orientation is not in landscape. Steps: Lock in landscape is already set on keyboard open. Device is powered off Open keyboard Power up Enter Pin Let boot complete Layout will be in portrait Lifting up the device in landscape will change display orientation, but moving it in as portrait will change display in portrait. Close keyboard, device will continue to change display orientation as expected. Open keyboard again, orientation lock is in effect. Build: QX1000

My phone is not rooted and camera app works well.

comparing influenza vs corona virus is like arguing about black lives matter vs all lives matter. Both are deadly and we shouldn't discount either. Influenza at the least we have yearly vaccines to attempt to get ahead of while also having a better understanding in regards to how it operates. The coronavirus seems to be quite deadly with the global reaction to shut down ports, transit, etc appears to be effectively working to prevent the spread. We don't need any more viral outbreaks beyond influenza so the reaction I'd say is reasonably warranted. Both are bad. Focusing on Coronaviru

Forward looking.

I faced this "one key reapeating" issue again. This was 4th time and it happened during writing a doc so it is not related to Chrome (like other ones have reported also).

Yeah, sounds quite sketch. But, they provided a possible root cause so hey. It may help the devs (and people in the community doing their own fixes).

See some thoughts about the same problem at these places:

Munich, Germany. Not yet received, but will receive before general availability.

Nuremberg, Germany. Please get in touch via this forum first.

I am happy with unshifted QWERTZ, however, I don't like CTRL being Strg and I would much happier with unshifted QWERTY (as I don't think my national layout will ever come up as an option). Otherwise, those extra keys are very good for using international layouts as they may also contain meaningful letters instead of special characters like in intl. US layout.

If you deselect all of the keyboard profiles and hide the, "set your keyboard location" prompt window you'll be able to use the keyboard as it appears. Counterintuitive but I presume it's a bug that will be fixed soon.

It would be nice if the Fxtec key could be mapped to super (meta) instead tho, for use as a modifier. Press&Release could still be home if fxtec insists 😉 And yep, if one or both of the oem keys could be mapped to right-alt, then it'd be sticky w/alpha. (I think) edit: I keep learning more. Apparently, if its made into meta, then we get some automatic key combinations built into android already - that are not launcher dependent. https://github.com/aosp-mirror/platform_frameworks_base/blob/6bebb8418ceecf44d2af40033870f3aabacfe36e/core/res/res/xml/bookmarks.xml 'a': Cal

As of hardware key codes, that should use the same code as "-" key in standard layout. (National layouts have always used the same key codes as standard US layout but included some special characters instead of original function, so like ";", "'" or "=" characters are replaced.) The strange part of F(x)tec keyboard is for example that ";" character of QWERTY is located at the right side of "P" and it should have been at the right side of "L", however, it generates the same code as being the ";" key. So on a QWERTZ device, the same key has "Ö" marking but located at the right side o

So, how much more of a delay would have been acceptable to you, for them to continue slogging through that list? There comes a point where you just need to ship it. Thing is, I give them a ton of room -- they are a startup, it's their first phone, and they had to partner with a bunch of companies to get this done. Other phone companies that were far better funded have churned out some hot garbage. Blackberry or Blackberry/TCL released the PRIV, a mess of a phone with overheating problems, terrible RAM management, and no updates, then the KEYone with displays that fell out, no updates, and

...This is rather absurd. You REALLY honestly believe that there were/are no Quality Control and they have not ironed out a LOT of major and minor bugs before you even saw it? Please get real. I for one have since last spring reported a bunch of bugs that have been fixed, many they already knew. And that was even before the beta-testers got them. And yes it happens that fixing one bug creates a new one, that no one imagined could be related, and hence did not test...

If I'm following this correctly, it would be the same key code that is generated for the hyphen/minus in the QWERTY layout.

I'm using one of these: https://www.amazon.com/Huawei-P20-Pro-Snakehive-Handmade/dp/B07DFM6HX9/ref=sr_1_1?keywords=snakehive%2Bhuawei%2Bp20%2Bpro&qid=1580840514&sr=8-1&th=1 A little work with a hole punch and an X-acto knife on the TPU part made it a perfect fit. Not necessary to cut the leather at all. I did have to shoehorn it on with a non-marking spudger.

Finally got Magisk installed properly. The issue was that I had an SD card in the phone, and Magisk manager automatically installed to the SD card which makes it not work. Hopefully this info saves someone else some trouble.

...Or maybe you confuse a startup with a multi billion company? Please mention me just ONE device principally different from what was on the market, that was released flawless. And yes, do also include if from one of the multi billion giants. If you do not want a device where the software is not polished, you seem to have made a rather naïve choice to pre-order, and not wait to say half a year after general release, to allow for the bugs found to be ironed out.

It was "askin" ? :P

China has shut down all the public transportation at the moment to slow/stop the spread the virus. China has also extent it's national holiday for the Chinese New Year. There are still quite a few days until the official holiday ends, we will see how things goes in the next few days and will react accordingly. Luckily I got myself back a few days before the mass spread of the virus and the lock down of the different areas. (Otherwise I will be locked into somewhere for 14 days lol)

Just a suggestion - could one of the moderators keep a concise list of known issues/bugs in the first post? That's typical approach on xda developer forums, and it really helps get a quick overview. On a related sidenote - is any of the problems found so far a complete dealbreaker for daily use? I'm thinking sensor-poking apps crashing isn't ideal, but it's not something one needs every day. Headset pairing is a bit of a bummer from what I see. Anything else?