claude0001

Off topic: @Casey, what's the advantage of this QFIL business as opposed to traditional flashing via fastboot/adb as you reported here and which is essentially a two-liner (if one has the Android debug tools installed anyway)?

So I seem to have the exact same issue with the right speaker as reported by @spam71. The speaker just makes a popping sound at low volume and works reliably only at highest gain. After operating for a while at high amplitude (warming up? vibration from speaker itself?) the volume can be decreased to lower values. After some time (cooling down?) the popping noise comes back, though. The problem can sometimes be cured by applying high pressure to the case near the speaker, and is much worse with USB plugged in, similarly to what spam71 observed. This indeed looks like a hardware issue

As I said, I had this on an 835-Pro1. Mostly, when using the phone on the move. The problem with bad VoLTE calls is definitely not specific to the Pro1-X. It is generally not just a problem on the side of the phone, but also caused by shitty LTE coverage and bad handling on the side of the network operator. E.g., when in the midst of a VoLTE call you roam to a cell with no or poor LTE connectivity, the call should seamlessly transition to GSM - however for me this never (or rarely) worked: the call just stalled (German O2, cannot recommend ...). By forcing GSM/2G from the start, you

It was your naming the App "Schlichtes Diktiergerät" (aka "Simple Voice Recorder"). 😄 I do not know about (the future of) 2G/GSM availability in Spain. Disabling VoLTE is a safe solution for Germany and Austria for now, but not for the entire world: If you are in a network which has disabled those old protocols, VoLTE is now mandatory for phone calls. But just trying will not break anything.

@Feld: As your phone seems to be set to German UI language, I will assume you are located in Germany or Austria. If so, you should try to disable VoLTE (sometimes called "Enhanced 4G LTE Mode" in the settings), which will force phone call audio to use the traditional GSM protocols rather than VoIP. For me this was a day/night difference with the Pro1(noX) regarding call availability and connection stability. You will lose native video calling in the process, but I think it is well worth it - and most people prefer using seperate apps for video conferencing anyway. Unlike in some other co

Mine looks fine too. Only issue I found so far is the known problem with the right speaker making just clicking noise at lower amplitudes ... let's see how that will evolve in my case ... Expansys even included a separate travel adapter for German AC wall sockets -- probably not knowing that the bundled charger from F(x)tec already includes a euro-type adapter plug (among others). Funny, but it also shows that they are somewhat serious about customer experience.

307 € (2249 HK$) for the device (6/128 GB) + 62 € (450 HK$) for rest-of-world shipping via DHL + 87 € german customs and VAT = 456 € total. Haven't unboxed yet, so let's see this was worth it ...

Not true in a big city at night. You see no stars, no moon, no nothing. The Pro1 compass is actively disorienting me in such cirumstances. But OK, I like the phone nonetheless ... 🙂

Found this thread following your suggestion: https://community.fxtec.com/topic/3670-pro1x-stock-android-non-gms-build/?do=findComment&comment=63768 Pretty cool. Sounds like a good interim solution before we get official LineageOS support. Thanks for the heads-up.

Is there a publicly accessible development branch? Or is that test-ROM you mentioned available for download somewhere? My Pro1-X should arrive soon and I do not intend to get engaged with Google-infested stock-Android.

I have a similar bug with the 835-Pro1 (in OsmAnd~ and SatStat). Often, the compass is 90° off with the keyboard either flipped in or out. Rotating the phone in all directions often helps to re-calibrate it to the right direction. But, obviously, if you have to know from other sources which direction of "north" is correct, the "compass" is essentially useless.

I guess there is a risk of that, yes. While it is not completely excluded that Expansys indeed legitimately bought a large stock from F(x)tec for re-selling, their very low price tag and the deafening silence from F(x)tec on the matter rather suggest the batch in question is being grey-marketed. I do not think this is the result of plain theft, as Expansys is a very large business and I see no reason for them engaging in what would qualify as all-out petty crime by their standards. Rather, I think the situation has resulted from F(x)tec somehow (unknowingly?) failing to meet supply a

Too bad. Then the Unihertz series is no option for me it seems. Ages ago, the N900 also suffered from its small keyboard and too few (coding-relevant) symbols pre-printed on the keys. However its creators -- programmers themselves -- knew this and included facilities for extensive key-remapping into the OS. The good old times ... One point for the Pro1 here, I guess.

Slightly off topic: Faking low "in-stock" numbers is a common technique to sell goods (of any kind, both online and offline) by creating a feeling of "it's-now-or-never" among potential buyers. I would guess this is just common practice for expansys (as it is for many of their competitors) and has nothing to do with the Pro1-X specifically.

That is a good question indeed, and the silence from F(x)tec on this is strange even by their standards of communication skills. I can imagine they are engaged in legal procedure against Expansys and their lawyers are recommending them to not publicly comment for the time being. As I read, they did promise the regular IGG update before end of the month. Let's see what will be in there ...

Besides the apparent lack of free ROMs, my biggest concern is that the keyboard -- unlike the Pro1(X)'s -- seems to lack many of the special symbols important for shell work or coding. Like "~", "|", ">" "\", or the sqare ("[]") and curly ("{}") brackets. Is there a way to enter these characters using the hw keyboard, e.g. via customisation?

Thanks @Casey. But what does this mean regarding native HDMI-support in Android/LineageOS. Will it ever work? What about the convergence mode of UbuntuTouch? Any hope for that?

With the original Pro1, HDMI works for me in LineageOS using this all-in-one hub: https://www.amazon.de/-/en/gp/product/B093FKT9BF/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 Wait, what? Does that mean that things like this [iggcdn.com] will never actually work with the Pro1-X? I think that was a major feature for those who ordered with UbuntuTouch ...

Nice thanks. On LOS 16.0, a half-press (i.e. the first stage of the shutter button) can be used for "Screen peek", i.e. shortly activate the (lock) screen only while the button is held. Does that no longer exist in LOS 18.1+? I find that quite useful for e.g. checking the time. Of course, as Pro1X has no double-action shutter button anymore, it wouldn't work there anway ...

Bummer. I have also used OpenCamera with my Pro1 since day one. Do you have any information on how not allowing users to set another camera app as default is supposed to be more secure? Did LineageOS 18.1 and 19.1 adopt that "improvement" or can Lineage users still pick whatever camera they want? Might be one more reason for me to camp on 16.0 a little longer ...

The Pro1's kernel supports vfat ("FAT32"), msdos ("FAT16"), ext2/3/4, and f2fs. At least for FAT32, ext3 and ext4, cards can be read also when partitioned and formatted on my (Linux) PC. Even with multiple partitions on the card, Android (Lineage) can access them all. I never tested f2fs. Of course, you should understand the implications of a UID-aware filesystem, before using something like ext. The same would hold for NTFS, where Unix-UIDs would need to be mapped to NT-UIDs in some way.

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

Odd, that looks like two different graphical layouts of the bootloader. Never seen that. I did everything fastboot (on Pro1, no X!) from the bootloader screen like on your first picture. That is the one I get when selecting "restart to bootloader" from LineageOS. You are right that a bad fastboot flash may mess up your data. However you should always be able to reach the bootloader for a full reinstall by holding "volume down" while powering the device. Make sure you have a full battery before any flashing experiments! If you have a bad feeling about your fastboot connections, I

I think @eorg is mistaking recovery for bootloader. He/she wrote that fastboot does work in "fastboot-mode" but not in "bootloader-mode", which makes no sense because the two are the same ...

Also for the Pro1, the Lineage driver was completely rewritten with respect to Stock. I have always only used Lineage and that one indeed supported sticky shift. As far as I am being told, that is a high level Android feature though, and has nothing to do with the actual device driver ("qx1000.c"). I am pretty confident all those things can be changed once we get a Lineage port ...