Leaderboard

@Casey you are my hero! Thank's for the link, it contained finally a solution to the driver issue. In fact I just had to select the driver from a list on my computer manually. I could have come to this on my own, but I was obviously to blindfolded to see this solution... So thank's to all of you for your support!

I'm not sure about this one, I haven't tested it out. Maybe someone more familiar with this can comment here. If installing the USB driver fails, it could indicate that your PC has enabled "Driver Signature Enforcement". You could try to restart your computer to advanced recovery menu and disable this option and try again. More information about this process can be found here. You could also try with a different type-c cable too? In an unlikely case, the cable may not be able to facilitate data transfer. I had an issue once where I was able to boot my Pro1 into bootloader but fast

Noticed THIS difference: And POWER_SUPPLY_INPUT_CURRENT_LIMITED sounds very much like what has been my theory all along..... The big question is how to avoid this state being triggered too soon though....

After rooting and using the 4 setprop commands I can at least see the VoLTE option but it is still grayed out. However, now WiFi calling works, thanks to, wfc_avail_ovr, which was a nice bonus. Edit: VoLTE is working after all. The option is grayed out but enabled and the SIM status shows that it is using LTE for voice.

From the kernel/driver side, that switch is actually controlled manually and not automatically. It's supposed to be controlled by a userland program which sets that value. I was going to jump to that one after constant_charge_current_max but you mentioned you didn't want o continue, so I stopped. the `uevent` file is just providing all data from other files with some extras. In this case, the culprit is: /sys/class/power_supply/battery/charge_control_limit In my phone, there's 7 settings for it (between 0 and 6). Basically, it's a choice of how fast to charge. I think my de

Hello, I got video playback working by creating a file: /etc/gst-droid/gstdroidcodec.conf with the following content (as mentioned as a quirk for the old Pro1x): [decoders] video/hevc=1 [decoder-quirks] video/mp4v-es=use-codec-supplied-height;use-codec-supplied-width video/avc=use-codec-supplied-height;use-codec-supplied-width The directory does not exist. You must create it before creating the file. After creating the file, I ran as root dconf update , deleted /home/defaultuser/.cache/gstreamer-1.0/registry.aarch64.bin and rebooted the device. Aft

Just had delivery of the Pro1x and it is a great phone, however the wifi and cellular data connectivity is appalling! I struggle to connect to a router that is only a few feet away, and my old cheap Nokia G20 connects to the network and cellular data absolutely fine. Little point having an all singing and dancing phone when it can't get the basics right. Any pointers anybody? And don't say it's my provider or wifi router as all other devices in the household connect fine.

Hey everyone, due to the current libsoup3 migration in Debian, `apt dist-upgrade` or the Software app might fail to let you upgrade an existing installation. You can unblock upgrades using the following commands: sudo apt update sudo apt upgrade ..and then proceeding as usual (i.e. doing an upgrade via `sudo apt update && sudo apt dist-upgrade` or using the Software app, which is the recommended way). As a reward, you'll also be able to upgrade to the newest phosh (0.21.0), which finally is available in Droidian 😀 Have fun!

What I found out so far now by evaluating: - any app which crashed before when starting a video still does crash. This includes the sailfish-browser and the ytplayer - any apps which were able to start a video before but performed a software rendering with only one frame each 2-3 seconds now run fluently. This includes the LLS vplayer and any Android video app running in Waydroid. Regarding the crashing apps, I made some experiments a few weeks before with enviroment variables forcing the apps to use different renderers. And the result was that they showed the behavior li

...If you are on a device with AICP or LOS you can (by an option in developer options) allow ADB to do rooted stuff, e.g. ADB root adb shell setprop persist.dbg.ims_volte_enable 1 adb shell setprop persist.dbg.volte_avail_ovr 1 adb shell setprop persist.dbg.vt_avail_ovr 1 adb shell setprop persist.dbg.wfc_avail_ovr 1 ADB unroot (not available on stock android though - neither Pro1X nor Pro1 )

Yes, I mean the Pro1. The same fix makes LLSv Player working on the Pro1X. But any other app I tried so far not.

(lineage-19.1-20220912-nightly-pro1-signed.zip on September 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220605_174313) Still with the keyboard bug introduced that messes accessibility apps (works on AICP R/S based on Android 11/12) see e.g. this.

Yes those commands require root. I've modified my post to note that. The LTE connection stayed up all night long. However, when I just called the phone, I got a "the service has not been implemented" recording, which I've never heard before. Second attempt at a call worked fine. So something is still not quite right.

I would suggest PETG over PLA as it's a tight fit and that's what I've been prototying in. I would hold off on TPU for the moment, the fit isn't strong enough yet.

I got a tip on the Telegram beta channel to force the toggles to show in SIM setup via the following commands (requiring root): setprop persist.dbg.volte_avail_ovr 1 setprop persist.dbg.wfc_avail_ovr 1 After entering those commands, and then enabling VoLTE on my primary SIM, it does appear to have registered properly to use VoLTE, and when I called into the phone, it did ring, did not change to "3G" on the network indicator, and did not lose connectivity. I'll let the phone sit overnight and we'll see in the morning if the problem is solved.

If someone is really interested, I might sell it too. EU. If it remains, I might use it. For now it's in its box and I'm waiting because I have too much content on my current device.

These guys can't catch a break. Us neither, but we know that already. I think this news calls for a pizza.

F(x)tec communication at its best ... 🙂 "Contractual issues" with their partners that lead to a 4-month-delay? With their tradition to underestimate delays by a factor 2 to 3? That's asking for the wildest speculations ... Here are mine: Option 1: The logistics partners suddenly want more money due to prices skyrocketing because of the ongoing crisis. F(x)tec can't pay more so they insist on fulfilment of the existing contract. Parter refuses and stops all activity, witholding the phones. They need to take it to court. Option 2: The entire batches 1 and 2 have "disappeared" fr

One week is a short time. They are a very small shop and are probably getting a high volume of email right now. Hopefully they will get to you. I would guess shipping to Russia from HK won't be too troublesome, but I would imagine if there were specific problems with that, they would contact their Russian backers-- However, I am not knowledgeable on this, just guessing.

So, I sent a message to Nova support, and this is their answer: The Digital Wellbeing app can't be uninstalled, but it can be disabled.

Its the same for me, in general connection strengths for all types of network aren't as good/reliable as my old phone (BB Priv).

Maybe the antennas aren't properly attached? Not sure about the warranty effect of opening it up to check...

For all the issues that I reported on the other thread, wifi isn't one of them. Granted, my home wifi sucks, so I haven't tried to do anything very heavy.

After comparing Pro1x, a Pro1 and a Titan Pocket, they all report similar dBm for my WiFi network, but maybe the Titan is just not great either?

Send an e-mail to info@fxtec.com identifying yourself (including your order (website) or igg backer id) complaining about that. Your unit may be defective. If you bought it, it's under warranty. If you're a backer, you can hope f(x)tec will uphold their voluntary warranty.

I've recently discovered typeracer as well which seems easier since you have full sentences. Best achievement with the Pro1 today were 370cpm which should equal to about 74wpm in german language. In english I get around 65-70 wpm but I have to quit many texts since they have special characters which I don't regularly use (as ' ). On the computer I get to up to 500cpm at max - in best times though.

This is a user-to-user forum, so the chance that your message is spotted by staff here is slim to none. Sorry.