Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by claude0001

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


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


    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
  2. 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):


    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
  3. I have updated LineageOS 16.0 to include backported security fixes up to ASB patchlevel "5 November 2022". At 


    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
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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
  9. 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
  10. @IMD seems to be absolutely right. The speaker failures occur only when /sys/class/power_supply/battery/voltage_now exceeds approx. 4100000 µV. This explains naturally why the phenomenon is more apparent when connected to a charger.

    The question remains whether F(x)tec will indeed be able to fix this by a firmware update, or not ... 😞

    • Like 1
  11. So I did open the phone yesterday and could not fix the issue using @spam71's recipe. I fiddled a lot with the spring contacts to the speaker, even while playing music through it: The problem seems to be independent of the electrical contact.

    The popping does seem to come and go also in my case. Sometimes the speaker works at all volume levels, sometimes only at highest gain.

    I will test if there is a correlation with the level of the battery charge. Thanks for the hint @IMD.

  12. Consider that, concerning non-working sensors, the recommendation to do a full backup of the original Android system is largely obsoleted by the latest edit of the OP of this thread:

    Concerning your connection troubles, I can only recommend to try different (USB) hardware. I ended up doing all my adb/fastboot business from a Raspberry Pi3 as my Thinkpads are seemingly to "advanced" for the purpose ...

  13. 45 minutes ago, Name_not_avail said:

    the difference between slot a and slot b, and whether I have screwed something up

    I think it is unlikely you damaged anything.

    As you probably know, the A and B slots are a kind of safety net that (among others) allows the device to keep the previously running OS "in reserve" whenever an update is installed. The active slot basically flips between A and B everytime a new ROM is flashed. So whether A or B is the "right" one for installing Magisk simply depends on the number of previous flashings being even or odd.

    • Thanks 1
  14. 21 minutes ago, FlyingAntero said:

    Pro1 supports Qualcomm Quick Charge 3.0 which is not compatible with USB PD

    Well, the OP wonders why, obviously, the PSU and the Pro1 cannot agree on any charging protocol, which is strange indeed. Depending on the power source, my Pro1 seems to distinguish between three different charging modes: "charging slowly", "charging", and "charging rapidly". The last is probably chosen only if the PSU explicitly supports Qualcomm QC.

    Electrically, one of the lower two modes should always be possible. I've been charging my Pro1 with solar panels ... 😎

    • Like 1
  15. 5 hours ago, steff said:

    I am really upset with answers like this. I really do not want to be rude, but did you read my opening thread?

    No I did not make a mistake Claude. Fedex is doing shady things. Please read the whole thread again.

    My post wasn't targetet at you as OP. I should have made that clear in my reply, sorry.

    As @Rob. S.already wrote, I was speculating about Expansys orders, for which the website defaults to "FedEx" (and very low shipping cost) even if you order from a region where DHL (at much higher cost) would be the right option to pick.

  16. I wonder whether some of the complaints here are due to people picking the wrong shipping option with their Expansys order.

    The cheapest option (FedEx, 114 HK$) is for US customers only, while the "rest-of-world" should use DHL (450 HK$). Now, as some of the complaints here clearly come from non-US buyers, I wonder if FedEX in their case just collects an additional fee that would have been included in the DHL option from the start ...

  17. 1 hour ago, VaZso said:

    So basically screen seems to be okay (sensing all of its area) but it is insensitive for touches at the edge of the screen.

    If you look again at the OP of this thread, the behaviour you observe is exactly as described for a screen having not reveived the "Stock-firmware-magic": The outer ~7 mm are insensitive to tapping but still correctly register dragging your finger form the central area outwards.

    I had understood stock Android 9 does its touch-calibration thing only on first boot. So just connecting the screen to an already-installed stock-Pro1 might not be enough. I would try to facory-reset the "calibrating" device first.

    • Thanks 2
  • Create New...

Important Information