Leaderboard

I'm going to be pushing for official Lineage support over the next few days. That means fixing all the known bugs (not necessarily enhancement requests, but of course I'll get to those also). So if anybody is experiencing any issues that aren't in the github tracker, please add them ASAP. Otherwise, I'm going to assume FM radio and selinux rules are the last release blocking issues. Also FYI... as soon as Lineage 16.0 goes official, I'll start working on 17.1. That should be a breeze compared to initial bringup. Oh and I'll probably be making an AOKP build this week. 😄

test10 is up. Changes: * Fix audio crackling. * Update fingerprint mitigations.

Got the FM radio fixed (listening to it now). Will push that up and do a new build soon. If anyone is interested in details... The first problem is that the AOSP "FMRadio" package is broken and not used, there is a QCOM "FM2" package that is used instead. I've noted this before. Second, there are some libraries that must be specified to be built which I was missing. Thirdly, there is a library that seems to be in the open source code but explicitly set to not build without the BSP for some reason so that needs to go into the proprietary blob list. Fourthly, was mis

As usual, TDM is Tom Da MAN!!! 🙂 In all seriousness though, there really aren't enough nice things to say about what you've done here. You've almost singlehandedly made a great piece of hardware with terrible software a great piece of hardware with great software to match! I certainly hope that the IdioticLTE people take some hints from your work, for the sake of the device's reputation. Bravo, sir! We salute you!

The advantage of official lineage is that you get automated nightly builds with the current code. That's not such a big deal for 16.0 since it's in de-facto maintenance mode, but it will be really nice for 17.1. It also means that more people will see it and use it, since not everyone reads this forum. The big advantage to AOKP has always been more options over Lineage. And there's also unicorns and swagger, naturally. 🙂 Yes, AOKP is probably past its prime, but I've a particular fondness for it. I've been using it for about 8 years and developing it for about 6. I worked with its

@puppymang the software fixes are slowly trickling into the stock ROM. But things are moving rather slow for stock due to various reasons. @FlyingAntero is correct, LineageOS is moving much faster and will surely provide a better experience for you at the moment. In particular, there is a setting for edge margins on the screen and the audio crackling has been fixed.

Maybe you should try Lineage OS since community has done great progress with the software. Audio issues are fixed in the latest test10 build and official Lineage OS build should be just around the corner. F(x)tec can also use the fixes provided by community (like keyboard driver) in official firmware. https://community.fxtec.com/topic/2509-lineageos-current-status-160-test-builds/

Thanks again! Tested the sound on several games that had always done it before, and yep, sound fixed!

Sorry to hear you had to buy another phone.. As you may or may not know, our factory in China, including their supply chain, has pretty much been off for the past 2 months. We are told they are back operating at some capacity but it's still nowhere near the efficiency and speed before the Coronavirus outbreak. Although very slowly, devices are being produced, but what can we do about that? We don't have 5+ factories like Canon, and we don't have the comfort of moving manufacturing to Taiwan like Apple did. We would be happy to replace your device, but how do you do that when half of

I just want to say that I laugh every time I see the title of this thread. The struggle is real but we are the chosen, poised to inherit the physical keyboard and carry the torch into the new millenium of VR and smartwatches.

His Pro1 is with us, so I can justify why he needed another phone. We're aiming to replace his device ASAP, as it will be quicker than waiting for new parts.

My preferred method is to try to slide my thumbs between the screen and the bottom half, leading with my thumbnails. Nudging the two halves apart this way will lift up on the screen, while pushing it forward, which will cause it to pop open. It also seems like it puts less stress on the hinge mechanism than trying to force it open by pushing down and forward.

Virus? What virus? [/sarcasm]

Which means we'll lose the SU binary as soon as we migrate to 17.x, right? If so not interested, I'll hang with 16 for a long time, lol. AOKP build: Very cool, I'm completely into AOKP and am ready for it! Thanks again for all your hard work and serious dedication!! 👍

I've gotten VLC with OpenSL ES initially working by taking audio_policy_configuration.xml from 1+5/5t. There are quite a few diffs, so I'm narrowing it down now. If you want to try this out yourself and report back, do the following: 1. Remove or rename the directory /vendor/etc/audio. This contains the currently used audio_policy_configuration.xml file. 2. Update /vendor/etc/audio_policy_configuration.xml with this one. I am particularly interested to see if this fixes audio issues in other apps. Note: audio_policy_configuration.xml is search fo

We are very sorry for the issues caused. After some investigation we have found the reason, it was due to the upgrade of security patch to October which needs to be approved from the authority before it was released, which caused CTS to fail. Also there is no way to downgrade security patch via OTA (the user data will be wiped if doing this way.) Therefore the current workaround / work is: - We are acquiring the latest security patch (Feb 2020) and will submit for approval before the next OTA. Therefore once the next OTA with latest security patch applied, and appro

test11 is up. The only change is fixing FM radio.

I realized that today, too. If wifi is on and I try to turn on hotspot, it will turn itself off again with said "error". However, when I turn off wifi first and then turn on hotspot it works. I tried connecting with my laptop, no problem, had internet access. Then when I turn on wifi again, the hotspot will turn off. I am still running Test 9 at this moment I will flash test10 and report back again. EDIT: also works for me in test10 A few days ago I reported issues with my earspeaker, I was able to resolve that problem. A few days before I dropped my phone (not from hi

Glad you like it. It was doing that before already, well except that before it was only cancelling the lock timeout 😁

Wow! As a former Dirty Unicorns user, I am excited by the possibility of AOKP. Sheesh, now I'll have to start sending you even more beers! 😉

When we request a device for service, we typically expect it to be sent within a week. In this scenario, we waited 1+ months for it to be sent in for service alone as far as I know.

@tdm I've done that on mine. All the apps I normally have an issue with are working with this fix as well. I'll let you know if it holds. I didn't even notice that there was a second audio_policy_configuration.xml in that folder there. Definitely confusing.

Just released v0.4.0 : Screen goes off as soon as you close the case whatever is your lock timeout. Seamless brightness adjustments using ALT+UP/DOWN if you are using Fx Qwerty or other keyboard layout providing brightness control. Settings look better and screen brightness is easier to access from there. Remember long press on the Fx quick settings tile take you to the settings.

Neither seems to have Nikon, or if they do, it didn't help, either, as their new D6 flagship camera has now been announced to be introduced no earlier than May, instead of March...

Not really important, but just asking: Did you buy a new phone to replace your Pro1 just because of broken fingerprint sensor? I mean, if the phone is otherwise perfectly usable, why didn't you use for example a lock code instead? I don't even use my fingerprint sensor (or any lock actually), so I could have swapped devices with you.

I just implemented that. It should be part of the next release.

Fx Service is an Android application notably enabling Pro1 smart case support. It also provides various solutions to common Pro1 problems or simply new features including: Smart case support: configurable lock and wake functionalities. Screen filter overlay to lower display brightness beyond system settings. Configurable vibration upon keyboard key action. Alternative auto-rotate solution to bypass system auto-rotate which tends to get stuck. Filter out unwanted system key input. Feel free to post here to discuss bugs and feature requests.

I can confirm crackling audio is gone on dialpad tones :)

And the FM works too. Thanks. 😎

Item is Sold!

As a last resort, if all other methods fails, I suggest a small piece of high friction tape. see e.g. here for various suggestions on how to open.

It took me some getting used to the keyboard, since it is (a) bigger than I'm used to, and (b) has an extra column between A and Caps, so I would initially always hit \ when I meant A. I've mostly gotten used to those, and can now type pretty quickly on the keyboard. The thing that I have not figured out a good solution for is opening the keyboard with the curved screen. It is extremely difficult to both lift up top (when landscape) of the screen (because the curved screen is slippery and significantly reduces the amount of area to grip) and push the bottom without triggering items on the

It would be if the software development were based in a place without COVID19, but unfortunately idealte is in China (AFAIK), and china have not had a tradition for even IT-people to work from home. So most likely things are not set up allowing that. It would require a VPN setup, and a company sponsored computer per person, and if they not already got that, it will be hard to get that too now, even if the budget for that was accceptable.

@Erik I think everybody should unterstand, that the delay because of corona isn't the fault of fxtec and unswayable. BUT isn't this a good possibility for solving all these software problems during home office while waiting for china and the restart of production? So that the rest of the pre-order customers will receive a device whithout or much less software bugs? I am sure this will be a good strategy to sell more devices ...

For what its worth, substratum works on stock pie for dark theme, as reported by @elvissteinjr It seems to me I'm already pretty dark under Lineage tho, where are you seeing all this white? Lineage settings menu backgrounds all dark... you can set your own launcher backgrounds (I use nova and set both the wallpaper and app drawer pure black, and changed the search background from white to charcoal)... I used dark theme youtube vanced... discord has dark theme... riot is dark by default... even play store black background... edit: there's even a setting for Dark Mode that

Possibly this commit? I got it from another device while I was trying to get things working, and then I deleted it when I saw that 1+5/5t does not have it. I am not sure if it should be present or not.

Hello tdm, greeting from Italy! First, many many thanks for you hard work with the device, with a particular effort to the physical keyboard software. For us, with so many words and accents, with the stock it was terrible and now it is comparable with the asanti keyboard (that it is my favourite). Then, I deeply tested your build 9 these days and I just want to report small issues to not be tracked in the Github repository: 1. The hotspot does not start if the Wi-Fi is on. When I try to power on it it self power offs and it does not start, it concludes a generic "error"; 2.

Thanks, works like a charm AND you forgot to advertise that it nicely re-awakes the screen by the magnet only, if re-opened before the Lock-time-out. 😎

Thank you for the update @Erik. Too bad these people don't understand the problems related to the worldwide virus.

New review from Pocket-lint (updated 3 March 2020) https://www.pocket-lint.com/phones/reviews/147291-fxtec-pro1-review-details

@kraynyan Yes, original box and all accessories are included. I would guess shipping would be somewhere between $10-30 depending upon the carrier and options. Let me know your zip code and I can get an estimate for you. Phone has been factory reset and is ready to go.

To me that would be a show stopper too. Can't live without fingerprint reader anymore 😁. Luckily mine has been working flawlessly and I even like its placement.

@tdm Finally had some success with the audio. Since the problem appears only when deep buffering is being used, disabling it from the audio config policy seems to resolve it. Here's the changes: diff --git a/audio/audio_output_policy.conf b/audio/audio_output_policy.conf index 4719b66..eb932be 100644 --- a/audio/audio_output_policy.conf +++ b/audio/audio_output_policy.conf @@ -26,7 +26,7 @@ outputs { app_type 69943 } deep_buffer { - flags AUDIO_OUTPUT_FLAG_DEEP_BUFFER + flags AUDIO_OUTPUT_FLAG_NONE formats AUDIO_FORMAT_PCM_16_BIT sampling_rates 48000 bit_w

... Or the more realistic 3) , they don't have anything they can send currently. If you should have missed out on it, they still have not got neither all the phones nor alle the parts they need.

Maybe you were matched with other people on smartphone but the keyboard gave you an edge over them?

I just tried PUBG first Time and won. There must be some magic on Pro1.

Currently playing the waiting game. :'( Stupid virus...... Hoping the keyboard will work well for SNES controller emulation when the waiting game is finished.

Thanks to @Raksura for posting this in another thread, but let me put it here too, for more to see the progress.

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.

My fingerprint sensor broke just two weeks after I got the phone. I've sent them an email asking when they would have replacement parts and devices and waited until 20.01.2020 before I sent it in for repairs. The phone arrived a couple of days before the 29. Since then I've gotten no updates, but a couple of replies after asking about it. I've been waiting for six weeks now and had to buy another phone.