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

Yes. With my first device. It was, sadly, unfixable. It just kept dropping even though it showed that it was there. Second phone just worked instantly.

all that apk is doing is echoing 1 to /sys/module/snd_soc_wcd934x/parameters/high_performance (as the majority APKs that "enable" things. My quick glance over the state of WCD943x in Linux says that it is still in early stages of support (there are numerous patches across the board), but the chip is indeed quite powerful hardware wise.

Magisk isn't required to make something work in the Pixel camera app though? You are saying you recommend doing those two things separately?

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

Vienna, Austria

Geneva, Switzerland, here. Will install LineageOS soon + root it.

Yeah with up to date specs TBH I'm tempted to get one, mainly as a phone to use when going out drinking beer 😄

Is there actually a concise list of bugs being kept somewhere or are we just using this enormous thread? I am experiencing the issue with all learned fingerprints being forgotten. On build QX1000_EEA_20200106110245 .

Usually when I am working at a PC keyboard, I am not even look at the keyboard itself. The phone is a bit different story as it is much smaller and not something which I use the whole day but when a PC is not available. ...and I feel Pro1's QWERTZ keyboard is comfortable especially because it has the same layout as a PC.

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:

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.

Unfortunately I haven't been able to build abl yet. I know it's possible, as an fxtec developer said he was able to build it. He was using a different like Linux distro than me, which may be the issue. One of these days after lineage and the factory restore tool are both humming along without issues I'll try again.

Any chance of this modifying the system and breaking OTAs?

Just to follow up on my previous post: Phone pairs just fine with my car over Bluetooth, and Android Auto works via USB cable Android Wear works, but it took a couple of tries to pair correctly with the watch Regarding wi-fi calling, it is working after going to the Phone app (NOT "Network & Internet" in the phone settings) > Settings (three dots in top right) > Calling accounts > tap the SIM card at the top with <your carrier> (in my case, "T-Mobile") > Wi-Fi calling > Set to On with "Wi-Fi preferred" (thanks again to @SirBaconIII for pointing me in

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 use Google Voice as my main number, and I hardly use my T-Mo number so it's not a huge issue. GV supports VVM in the app and on the web. But coming from a Pixel, it kinda sucks to lose the native VVM and spam filtering for my T-Mo number. I do have the T-Mo VVM app, primarily to clear out the spam

Auto-brightness doesn't work well. Tends to be too bright on many occasions

First, I'd like to apologize for my laziness. I'm just copying and pasting a part of my post from another thread, and I accidently cleared this the first time I was working on it. Hope this helps.

Can you shoot us a link to where you got it from?

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.

@skrilax I've put a userdebug zip in the server. It's not linked, just replace user with userdebug to get it.

Oh right, this thread! I can say it now, my favorite HW keyboard phone is the F(x)tec Pro1 :).