Jump to content

claude0001

Members
  • Content Count

    554
  • Joined

  • Last visited

  • Days Won

    66

Posts posted by claude0001

  1. The Pro1 seems really problematic with regard to fastboot. I recently flashed my wife's Fairphone3 using my Thinkpad X250 without any problems. That same PC never succeeded with the Pro1 ...

    There seem to be multiple factors affecting flashing, especially in fastboot mode, and some are not controllable in a daily-driver PC. E.g. many USB-attached peripherals are not "removable" in a laptop.

    Hence my advice to just use a dedicated system for all Pro1 flashing. Using adb/fastboot from a Raspberry 2 or 3 just works(tm)! They're hardly more expensive than a separate USB hub and are useful for so many other projects ... Note that I haven't tested the Raspberry 4 in this respect: "improving" on its predecessors' USB 2.0, it features a USB 3.0 bus that might behave differently for our purpose ...

    • Like 1
    • Thanks 2
  2. Sooo ... I finally got myself an additional SIM for my Pro1-X. And ... things seem to be bad ... Very bad ... So bad, that I now regret relativizing some of the devastating experiences others have posted here before ...  Apologies, guys!

    I got my Pro1-X two months ago (from Expansys) and found its WiFi and GPS functions to be somewhat on par with the - albeit not great - capabilities of my Pro1. Based on that, I extrapolated that telephony could not be much worse, either. I think I've never been that wrong!

    After a few hours of testing, the Pro1-X's GSM/LTE modem seems to be a disaster (I'm on 2.1.5-GMS-less). I have a single point in my flat where I get any service at all. (The 835-Pro1 has LTE everywhere, I'm in the middle of a major German city!) Even in that spot, I was only temporarily able to get some mobile data transfer. Most of the time, the browser would stall with a "no network" error message, even with the statusbar indicating 4G service available. Up to now, I have also not been able to either initiate or recieve even a single phone call! I tried several network settings, "LTE", "Global", etc. I also tried to enable/disable VoLTE (my carrier supports both on the Pro1) or Voice-over-WiFi. To no avail.

    Frankly, this is a nightmare! I have now serious doubts that the Pro1-X will ever be able to replace my (835)Pro1.

    • Sad 1
  3. I too had initially many troubles when trying to use several Linux PCs (both, desktops and laptops) for flashing the Pro1 in fastboot mode. Compared to other phones, it seems to be quite picky about the USB hardware ...

    I ended up configuring one of my Raspberry Pi3 specially for flashing my Pro1 and Pro1X: no problems ever since. The RPi3's are cheap, their simple USB-2.0 ports have proved to be 100% reliable for the purpose, and adb/fastboot is just an "apt install" away in Raspbian.

    • Thanks 1
  4. On 12/30/2022 at 5:51 PM, mattock said:

    Is there really no way to get any charge into a flat battery?

    From this thread, it seems like you already know all there is to know. Still, here is my summary for any newcomers dropping in:

    For unknown reasons, F(x)tec ship their phones configured in a way that allows battery charging only with a running OS. If, by whatever circumstances, the battery charge ever drops to zero in that configuration, re-charging will no longer work, as this would require to first boot the OS which - in turn - would need at least some residual charge to be left in the battery. In that situation, the only way to re-charge is probably to disconnect the battery from the controller circuit and to energize it using a laboratory power supply (I haven't tried this). 

    Imho, the first thing to do when you receive your F(x)tec phone (Pro1 or Pro1X alike!) is to connect to a PC, fire up fastboot, and do

    fastboot oem off-mode-charge 1

     which will enable charging the battery with the device powered-off.

    • Thanks 2
  5. 9 hours ago, xhajt03 said:

    Do you know that you can select LTE network, but disable VoLTE, i.e. enjoy higher data transfer speeds and longer batter life while having no problems with voice quality?

    That's a good option for regions where GSM/2G or 3G still operate concurrently with 4G/5G. I use that solution with my Pro1 in Germany.

    However, @Name_not_avail is located in the US. They recently shut down all pre-4G networks. 4G simply does not implement traditional voice calls outside of VoLTE. Hence, with the modem no longer able to fall back to one of the older, non-IP-based protocols (2G/3G) upon initiating or receiving a call, VoLTE is now mandatory in the US.

    • Like 2
  6. 🎄 Christmas Update 🎄: A new build of LineageOS 16.0 (for SD835-Pro1) is available at

    https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1.

    Go for the ROM dated "20221222". This build enables kernel support for PlayStation DualShock gamepads, inexplicably missing from the standard defconfig.  😉  There are no other changes since last week. As usual, my collection of mods relative to upstream is available.

    Why this is important: Turns out my son enjoys SuperTuxKart as much as I do, and he actually got his own DualShock3 for St. Nicholas Day. So we thought we could use the Pro1 as a mobile game console by connecting our controllers via a USB dock. What a disappointment when they were initially not detected! These are the things that remind you of the benefits of open source:  😎

    IMGP0289.thumb.JPG.f9eeedba05ca7692289e840e7cec3422.JPG

    Merry Christmas!   

    • Like 3
    • Thanks 2
    • Haha 1
  7. 31 minutes ago, Hook said:

    I don't know much about UT, but as I mentioned above, I think Lineage is awaiting the firmware update.  The fact that Droidian ans Sailfish are advancing, I think, shows that  the community is interested in this phone.

    In the end, all those OS's rely on the stock Android 11 core. I do not think UT or LOS are any more dependent on an updated firmware from F(x)tec than SFOS or Droidian. But I can see your point that the latter two indeed show that not all is lost. Probably I'm just overly pessimistic ...

  8. 3 hours ago, Hook said:

    I think  this really does misrepresent what they said.  They said the alternative OSs are community run projects by volunteers and progress depends on their time (true), but that they are working closely with those volunteers to provide as much support as possible.  There was no comment about ask the devs.

    OK, ok, I was probably overshooting a bit. Sorry. 🙂

    However, my point was not about something specific they wrote in this latest update. It's more that I dislike the overall trend: One year ago, F(x)tec had an in-house developer actively working on Pro1/X kernel mainlining and alternate OS porting. At that point they seemed pretty serious about delivering a phone with official, out-of-the box LineageOS and UbuntuTouch support. As I wrote previously, this was a very important aspect of the initial Pro1-X concept.

    During this year, they first abandoned the "out-of-the-box" part (by shipping all phones with Android), then - slowly but steadily - walked away from the "official" aspect (by admitting that the porting was essentially done by independent community devs after all).

    I am ready to believe that, even when not driving the effort themselves, they still want to support community devs -- but they are obviously quite inefficient even at that. I find it worrying that today's most advanced alternative OS's for the Pro1-X (SailfishOS and Droidian) are precisely NOT the ones F(x)tec initially wanted the Pro1-X to ship with (LineageOS and UbuntuTouch). How does that fit? The pessimistic explanation would be that they have alienated their community ... I hope that is not the case.

    • Like 6
  9. OK ... this does not seem to go well.

    According to the past updates, almost all units should have been sitting at "their" warehouse (really Expansys', I understand) already for four (4) months. Given that Expansys are obviously able to ship their own Pro1-X's without any problems, I think F(x)tec should stop blaming "logistical issues" in "China and Hong Kong" for everything ... they must have at least some part in this mess and I think people would appreciate if they admitted that.

    However, the most disappointing part about the last few updates is how alternative OS development is increasingly being framed as "not our problem ... community thing ... ask somewhere else". Guess what? We are asking "the community" and get responses like "we do not know that device, ask at F(x)tec". Seems like everyone is pointing at everyone else. Is anyone actively working on a LOS port for Pro1-X? If one remembers that the Pro1-X was once branded as the "XDA phone", it is quite saddening that alternative OS development is seemingly no longer given any priority at F(x)tec ...

    Sorry for the outburst. Had to vent. Please proceed, nothing to see here ... 🙂

    • Like 3
    • Haha 1
  10. Another month, another update of good-ol' LineageOS 16.0! Head to

    https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1

    and fetch the ROM dated "20221214". It includes backported ASB fixes up to patchlevel "5 December 2022".

    The warning about lack of upstream code-review still applies (see above). All I know is that the ROM seems to work fine on my own device. Also, as I wrote last month, my modded keyboard driver no longer reports every key-press to the kernel log. Send me a PM if you prefer a build with this debugging info enabled.

    As usual, a tarball of all mods with respect to the official LOS-16.0 tree can be downloaded at the link above.

    Newcomers be reminded that this is for the original (SD835) Pro1 only.

    • Like 2
    • Thanks 2
  11. I believe @TechLvr is using my (LOS16) rom. Therein, the respective section under "System > Languages & Input" is indeed called "Input assistance".

    In my case, the spell-checker panel looks like this:

    Screenshot_20221206-020312_Settings.thumb.png.2ea37460b9dace595899141937ebae1f.png

    Where I have several "System languages" selected under "Languages & input":

    Screenshot_20221206-020539_Settings.thumb.png.c098e55ab7513ba03982f5803769d82f.png

    During typing one can then switch between those on-the-fly using the "globe" icon on the on-screen keyboard, or using "FxTec+Space" on the HW keyboard.

    Did you install any alternative keyboard apps?

    • Like 1
    • Thanks 1
  12. All I can say up to now is that the raw GPU performance of the Pro1-X is indeed much lower than the Pro1's. In Super Tux Kart (love that game!) the X reaches somewhat less than half the frame rate, given identical graphics settings (top: Pro1, bottom: Pro1-X):

    SuperTuxKart_Pro1.thumb.jpg.11f7f53295edc30c69110306a1bc485d.jpgSuperTuxKart_Pro1X.thumb.jpg.7e9d1d8c51704226a89cc20d8bc0e185.jpg

    While this is unfortunately quite noticeable in a fast-paced game like that, it of course does not matter much in normal phone use.

    In many cases the Pro1-X actually feels faster than the Pro1, e.g. when launching apps, as if the disk-IO was faster. However, that may also be related to Android 11 (on the Pro1-X) being better optimized than my good-old Lineage 16.0 (on the Pro1); or simply due to the fact that, up to now, I have way less stuff installed and running in the background on the Pro1-X compared to the Pro1 (which is my daily).

    Once Lineage becomes available, I plan to port my Debian-chroot setup to the X, which should provide me with all the low-level Unix benchmarking tools I'm used to, and allow for a more in-depth comparison of the two devices.

    • Like 2
    • Thanks 2
  13. I have updated LineageOS 16.0 to include backported security fixes up to ASB patchlevel "5 November 2022". At 

    http://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1

    grab the ROM dated 20221117. Remember that this is for the original SD835 Pro1 only.

    The note about lacking upstream code-review from previous months still applies. All I can say is that the build seems to run without issues on my own prawn.

    Note that, with this release, I have added a compile-time option that disables most of the kernel messages generated by the keyboard driver. I always disliked how every single keypress was getting reported in dmesg, and those messages never actually helped me debug anything, so ... If you want to use LOS 16 and keyboard driver logging is really important to you, send me a PM, I can then make a customized build for you with the debugging info re-enabled.

    As usual, a tarball of all my mods respective to the official lineage-16.0 branch is available at the link above.

    • Like 2
    • Thanks 1
  14. So, the speaker issue is definitely improving.

    With the battery fully charged (and /sys/class/power_supply/battery/voltage_now >~ 4100000 µV), the tapping sound reappeared sometimes while changing the volume of a playing youtube video, though not to the extend to make the video unwatchable.

    Now, with the battery charge at 72% (/sys/class/power_supply/battery/voltage_now ~ 4000000 µV), I'm back to "cannot reproduce" ...

    I am now quite confident that this problem will quickly go away with ageing of the battery, as others have observed, and I regret opening the Pro1-X for this (breaking a grand total of three of the tiny grounding springs surrounding the board in the process - do not insert your spudger to deep while opening the bottom shell!).

    • Thanks 4
  15. On 9/28/2022 at 12:27 PM, claude0001 said:

    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?

    Replying to my own question: Seems like it doesn't look very good for HDMI-out on the Pro1X, at least when it comes to alternative OS's.

    Unsurprisingly, I can confirm that my all-in-one UGREEN USB-C dock, which works flawlessly with the Pro1, does nothing regarding HDMI when connected to the Pro1X (also Ethernet does not work with the X btw ...).

    After a bit of reading, I wonder whether the solution that was presented during development of the Pro1X is actually using any native "HDMI-out" features of the SoC. Rather, it seems to implement an MHL interface and needs a proprietary APK to send the screen content to the HDMI-end via USB. This might explain why Apps for playing DRM-protected content (Netflix, Amazon Prime, ...) cannot display on the HDMI screen, as admitted in the product descriptions.

    Watching Netflix on a hotel TV was the only practical use I've ever made of my Pro1's HDMI-out. Bummer ...    

    • Thanks 3
  16. On 11/3/2022 at 8:01 AM, IMD said:

    I think it is not related with temp or charging state.

    So I started playing around with my Pro1-X again.

    After the device being shelved for ~1.5 weeks, the battery is now at 61% and /sys/class/power_supply/battery/voltage_now never exceeds 3870000 µV. In this state, I cannot reproduce the speaker issue!

    So, maybe, it indeed occurs only on brand-new devices (and batteries) where the voltage exceeds 4.1 V significantly after charge ... ? This might explain why the problem goes away after some time of using the Pro1-X.

    edit: Re-charging the Pro1-X now, to check whether the problem comes back with battery full.

    • Thanks 3
  17. 5 hours ago, JECE said:

    As in, should I raise my old complaints about the faulty speaker on the device that I mentioned before?

    Without knowing how well they are prepared for handling mixed tickets, my gut feeling is it is probably better not mix.

    The tapping-sound problem with the bottom speaker has been reported by several users (including myself) in another thread and there are hints this may be a firmware/software problem they are working on. @Casey promised to take home our reports and come back to us once more is known.

    • Like 2
  18. 1 hour ago, EskeRahn said:

    Usually that shift is invisble for the user though

    Well, let's say they are not "apparent" during normal usage. But @Rob. S. is specifically using advanced tools to monitor the charging process. I guess, otherwise he would also not notice this.

    Might be somethign else in the end, but especially the fact that the current decreases towards the end of the charge is pretty normal, I think. I see that also when charging my Pro1 using my solar-panel charger (which includes a built-in current gauge).

    • Like 2
  19. I use my Pro1 as daily driver with my self-built LineageOS 16.0 and a Debian 10 (actually Devuan 3) desktop GNU/Linux system running permanently in a chroot. For me this is the optimal combination of an Android(-like) environment with the option to do serious (desktop) work from the GNU chroot.

    Of course, running a more native GNU/Linux system (if we agree on calling libhybris-based hacks "native" 😉 ) like UbuntuTouch, Sailfish, or Droidian is tempting, but -- realistically -- I cannot make it through the day without some Android apps I would not know how to replace (Firefox, Zoom, Öffi, Zoo for Zotero, ...) and I do not want to rely on something like Waydroid or Anbox for my job.

    My Pro1X seems very promising (except for the right-speaker-bug that hopefully will be solved somehow). The keyboard responsiveness is much better than that of my >2 year old Pro1. The graphics performance is much worse, as expected, but I do not use the Pro1 much for gaming either. Currently my Pro1X is more or less shelved, but once LineageOS becomes somewhat stable, I will try to migrate my Pro1 setup to it.

    • Like 3
×
×
  • Create New...

Important Information

Terms