Jump to content

claude0001

Members
  • Content Count

    554
  • Joined

  • Last visited

  • Days Won

    66

Posts posted by claude0001

  1. 15 minutes ago, Feld said:

    I was wondering from where you saw I'm located in Germany

    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. 

  2. @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 countries, there are no plans to disable the GSM/2G networks anytime soon in Germany, as important national infrastructure relies on them. However, you'll have to remember to re-enable VoLTE when e.g. travelling to the US. They are currently shutting down everything <4G.

    • Thanks 1
  3. 15 hours ago, claude0001 said:

    Haven't unboxed yet, so let's see this was worth it ...

    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.

    • Like 1
  4. 7 minutes ago, EskeRahn said:

    though it is seldom that you do not have a rough idea of the direction.

    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 ... 🙂

  5. On 9/29/2022 at 10:22 PM, brunoais said:

    There's finally a build of LOS that works and I got myself a test build with it.

    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.

  6. 2 hours ago, EskeRahn said:

    Add: Sorry, remembered wrong. It is an autorotate-bug.
    IF you open it, with an app supporting landscape THEN the orientation is shown correctly.

    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.

    • Like 1
  7. 59 minutes ago, mv said:

    are we just taking our own stock if we make these orders

    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 and/or payment deadlines in their contracts with Expansys as logistics partner; and Expansys requisitioning devices already in stock based on some fine-print clauses.

    I must admit that I have also ordered a Pro1-X from Expansys. 60%+ off is just too tempting. Yes, this way I might get a device for cheap, while some early IGG backer might never recieve anything. I agree that that is unfair, and I do not feel easy about it. However, what can we possibly do? In the end, I think it is also important that the Pro1-X finally hits the community (this community!) in sufficient numbers for alternative ROM development to lift off. If all the Expansis devices disappear in some shady grey-market environments with no one caring for them, we might loose everything.

    • Like 3
  8. On 10/12/2022 at 3:25 PM, EskeRahn said:

    I have looked too, without finding it. And combining the modifiers seems to have no or strange results.

    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.

    • Like 2
  9. 1 hour ago, Stucadoor2 said:

    While ordering my pro1x at expansys, their site stated 2 in stock, mine being 1 of them. By now roughly 10 hours later their stock of the 8gb 256gb blue is more than 10...

    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. 

    • Like 3
  10. 1 hour ago, Stucadoor2 said:

    Please explain why orders on the site placed in 2019 to 2021 aren't being fulfilled when at the same time the Carrier supposedly in charge of distribution sells the phones one its website for half the price and within a week.

    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 ...

    • Like 1
  11. 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? 

  12. 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

    2 hours ago, Benni said:

    [...] the chipset doesn't support HDMI out, [...]

    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 ...

  13. 5 hours ago, Hook said:

    Lineage 19 allows you to set a default camera app for a long press of the camera button.  Mine is assigned to open camera.  The short press does nothing.

    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 ...

  14. On 8/20/2022 at 8:12 AM, Rob. S. said:

    Problem now is, starting with (stock) Android 11, changing the default camera app is not possible anymore for alleged security reasons.

    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 ...

  15. On 9/10/2022 at 5:08 PM, Tsunero said:

    Nevermind, FAT32 formatting works if I do it with the phone itself.

    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.

  16. 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" from the warehouse. Maybe stolen to be grey-marketed. Now they need to get the money back from some insurance company and re-manufacture all those phones.

    Option 3: The "contractual issues" and the long delay have nothing to do with each other. Rather, they realised the radio problems, discovered when the first devices went into the wild, cannot be resolved by firmware updates after all. So they hold back all devices not yet shipped to apply hardware fixes.

    • Thanks 1
    • Haha 1
    • Sad 2
  17. 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 repeat my advice given several times here: fastboot is really picky about the USB hardware of the PC. I use a Raspberry Pi2 for all my flashing. Over the ears, Its humble USB2 bus proved rock-solid for that purpose, no need to mess with Google drivers, and the sdk tools are just an "apt install" away in Rasbian.

  18. 17 hours ago, eorg said:

    Can't I just flash in fastboot mode? Does it has to be bootloader mode?

     

    18 minutes ago, Casey said:

    What happens after you enter this command under bootloader?

    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 ...

    • Haha 1
  19. 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 ... 

    • Like 1
×
×
  • Create New...

Important Information

Terms