Leaderboard

Regardless of whether you think this is the right place or not, the latest info from Fx-tec usually is found on IGG and reposted here within days if not hours. In the past "operational delay" has often meant some delay due to a COVID lockdown. As far as your ordering date, reports are that it does not seem to matter if you ordered from the site or participated in the IGG campaign as to when your phone will ship out. As near as we (or at least I) can tell from posts of those whom have received their phone, no one has been able to figure out the shipment order (maybe I missed it). Asking her

That variable has the same value on my Pro1. rostkatze:~ # cat /sys/class/power_supply/battery/constant_charge_current_max -22000 I'm still running LOS 16.0 and never had the charging bug. Whatever that number means, I think it is unlikely that this is the right track ...

I doubt anyone of us has further information about anything happens in the background - we are also waiting for an official information. What @Hook has tried to tell this forum was created for communication between users and official staff may not necessarily reading threads here, however, they wrote in this forum time to time. Basically this thread was initiated independently of official staff as a user to user base of information sharing about production and delivery. What I can say is they have really started delivery (I have already received my Pro1X). I hope they will wri

These numbers are reset if you reboot the phone, though. However, it appears like the issue isn't there. Given so, it might be in the drivers or it can be something I'm missing...

Can you giva a more precise ideab of "bad battery drain?" I get what i consider quite good battery life on 19,1, meaning the Pro1 easily lasts me all day, even with a lot ofuse and screen time. My battery was recently replaced, so I get long life anyway, but I'm not getting unusual drain.

Thanks very much! That's works! I updated my USB Driver via Windows Update Database, make a factory reset on the Pro1X and try to start the fastboot flashing three times... now it's locked! Crazy... maybe one of the problems was the complete data transfer between my old blackberry and the Pro1X, who knows 🤷‍♂ Now I can explore the Pro1X completely 😃🤓

Confirm this with a Pro1. I sometimes stream music (from youtube) to a bluetooth speaker via the Pro1. When the latter uses the 2.4-GHz-wifi band, there can be a ver short hickup in the bt-audio when the player downloads another bit of the youtube stream. Can be prevented by forcing the Pro1 to use the 5-GHz WiFi bands (which sadly have lower range) ... Of course, both, 2.4-GHz-WiFi and bluetooth should be able to handle this kind of interference according to their spec, but reality obviously disagrees. When we bought our house in 2017, everyone was laughing at me when I wired different r

It's specific to the yubikey which is a crypto token, not just a basic nfc tag. I have thousands of nfc tags and can get them all to scan reliably but not any of my 3 yubikeys. Yubikeys are used as 2fa tokens so if you have it set up and the phone doesn't handle it, it makes it very hard to use the phone.

Thank you everyone for your assistance. I am happy to be joining what appears to be a very friendly and supportive community. With the exception of this issue I am extremely happy with the Pro1-X. It is fast, the keyboard is really nice, the hinge is really high quality, and the overall build quality is very impressive. Yes, it is a little heavy but I actually prefer that as I tend to drop lighter objects. Now back to the point: I am using the Pro1-X. I have specifically tried near the camera, the logo, everywhere in-between. I have tried the Yubikey all over the phone. Absolutely no re

some oddities so far, but the most concerning is that the nfc reader does not appear to be working on Android. i have a yubikey for a lot of security items. I cannot get the phone to detect the yubikey. any ideas?

I'm interested in buying this. How can I get in touch with you to arrange shipping?

Install something like GSAM or 3C All-In-One Toolbox, to find what app is the culprit. The LOS by it self is pretty lean on the battery. About 0.5%/h when idle. ADD, And when in Aeroplane mode it falls to about 8%/day (And this is on a preproduction unit from the the spring 2019, with original battery)

My Pro1 can easily last 2 days running LOS. Never changed the battery. Is that phone going to be 3 years old in January? I think I've been running LOS about a year now.

Oh! This is wrong! What happens if you (as root): chmod 644 /sys/class/power_supply/battery/constant_charge_current_max echo 22000 > /sys/class/power_supply/battery/constant_charge_current_max But that may not be enough... If the % doesn't change in about 20 mins, try: chmod 644 /sys/class/power_supply/battery/constant_charge_current_max echo 40000 > /sys/class/power_supply/battery/constant_charge_current_max That should be enough for the phone to start charging significantly. Do execute this from time to time to confirm if it's being overridden by something el

I wish, reset AGPS data and no joy - get "GPS Signal lost" on Android Auto every 20s and still no strong satellite signals when I use a GPS checker app

This is a user to user forum. Any new information will come through updates on IGG, which then gets posted here by one of the folks frequenting this forum. 🙂

My contribution page

QWERTY

13 days ago, fixtec informed, they stopped shipping. And now? Are there any new informations?

Interesting. Maybe try installing the Google USB driver: https://developer.android.com/studio/run/win-usb and try again. I'd suggest only installing the .zip file, no need to go through the whole process via Android Studio. Reboot your Pro1-X to fastbootd by: adb reboot fastboot Then on your Windows PC, go to Windows Start Menu -> Device Manager -> your_device_name, if there is an exclamation mark next to your device, right click and select update driver. Choose the option where you can upload from your local disk rather than Windows searching for an update. Then, locate the

For what it's worth, I have yet to see a really stable Bluetooth connection. Especially in my house, when there also is 2 GHz WiFi in use, Bluetooth and WiFi also interfere with each other because they transmit in the same frequency band. Lately, when I tried walking around the house with headphones on (JVC HA-S30BT) and the Pro1X in my back pocket, I only had very few hiccups and drop-outs, though.

@Slion, in all fairness and understanding: wireless connectivity is the central capability of a mobile phone. It should also be at the center of the design and QA. The Pro1 was not outstanding in this respect, but the Pro1X is obviously failing to be useful at all for some users because of the quality of its radios. While I hope they will be able to improve behaviour in future firmwares, these bugs should have been ironed-out in the prototype phase.

@EskeRahn @eorg The recovery is the dead droid. To activate its menu, press the power button and the volume up button. Still, the limitation is that ADB is not fully available in recovery. We can only sideload patches. In the beta group its used to manual sideload local updates from "OTA" packages that are contained in the releases. We even got an alternate fastbootd that can write logical partitions. You can reach that by either `fastboot reboot fastboot` or from the recovery menu item fastboot. @eorg Don't let yourself confuse too much from the evolving threads here. Most things have be

It would be better to have these issues in separate threads, as others are unlikely to find them in an nfc thread... Thread on the pro1x speakers already exists.

Well it requires Phyton, but apart from that it should be possible to get it working with Windows, I have not experimented with it though....

Danish passports with chips has an antenna like the travellers card above, and has the same issues. Can be read by the Pro1X, but not easily. I would guess it is the same system for all (or at the least many) countries with passports with chips.

I also read a NFC-tag on the late sample Pro1X. I have two other tags that can be read by the Pro1, but NOT the Pro1X. I edited the title slightly. This tag works on Pro1X, Pro1 (and Titan Slim also on stock Android 11) This tag I only managed to get to work once(!) a few times with the Pro1X after maybe once every 100 retry. Else i get "NFC read error. Try again." (Pro1 & Slim OK) Have not been able a really hard time to get this one to work at all on the Pro1X. (Pro1 & Slim OK) But I CAN get it working, holding it exactly right!

Bad news! This ALSO seems to hit stock Android 11 on the Pro1X 😭 ADD: Though it seems that unplugging and re-plugging here several times can suddenly bring it back to normal, so not as bad as what we see on Lineage. and AICP.

Just to be sure, have you tried other nfc-items? That is do we know if it is general or specific to yubikey ? I tried my Titan slim on Android 11, and nfc works out of the box. I will try to install installed AICP-R and AICP S, on my test unit Pro1 to see it it is related to Android 11 / 12 ADD I, just tried AICP-R on a Pro1, and it worked out of the box installing "NFC tools" for test. ADD II, just tried the broken AICP-S on a Pro1, and it worked out of the box (well after the boot-loop) installing "NFC tools" for test. So the issues seems to be related to Pro1X, (or your spe

🙂 Thank you. I thought I saw it was ready, but I was certainly wrong. Ubuntu Touch kind of is, but is in the community channel (not sure how I mixed that up). Appreciated.

There isn't yet a Lineage version for the Pro1x. You'll have to wait for that. The version for the Pro1 will not work. You probably are aware of that, but wanted to make sure, not insult your intelligence. 😉

AFAIK the NFC Antenna is near the camera at the top - are you trying to read it there?

I had this problem. I found I was able to set everything up by doing it with no SD Card and no SIM Card installed. I set it up over wifi, then I installed my SIM Card and SD Card. Everything seemed to work fine after that. I've been using it fine for a few days, now.

This is an official Fxtec-Forum. And here is the production thread. I did not buy my phone via IGG. Therefore I asked here in the right place. Possibly somebody has some new informations about that, what is going on since some weeks. Today is day 14 since Fxtec declared, they stopped shipping. They declared, they finished the production of batch 1 and 2 (what ever this exactly mean). They sent some phones out. The rest is in the "warehouse". And since weeks nothing happend. This situation is very unsatisfactory, I ordered in May 2020 ...