claude0001
-
Content Count
784 -
Joined
-
Last visited
-
Days Won
116
Posts posted by claude0001
-
-
On 4/12/2025 at 1:33 PM, EskeRahn said:
22.2 is the newest on the Pro1, and most likely on Pro1X on next release in a few days
Thanks. Yes I know that. But the doc linked above lists almost nothing for the new 22.2 branch (yet?), while there are quite specific instructions for 22.1, that's why I asked about that one.
As I am routinely self-building, I feel confident to compile any of the officially-supported branches and thus think I do not depend on the pre-made ROMs from the LOS build farm. However, I hesitate to ditch one of my working installs just to find out that AVF has simply not been ported (or may not be possible at all) for the Pro1 ...
-
Has anyone tried running a GNU/Linux distro through AVF in recent versions of LineageOS?
As can be seen from my signature, I am running old(er) versions of LOS on my Pro1(X)'s. The main reason for this is that I have relatively complex Linux-in-rooted-chroot setups in place, that are notoriously difficult to migrate to different Android releases.
AVF introduced in Android 14 and 15 could be a game-changer for me as it - theoretically - enables official support of Linux-Distros in containers, potentially making my hand-made solutions obsolete.
However, it is not clear to me if AVF is enabled in all LOS releases. In official Android, it seems to be limited to specific devices/SoCs. So what about the LineageOS 22.1 ports for the Pro1 and Pro1X? Do they include AVF or not?
-
Here's another one. The ROM dated '20250326', available at
https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1
gives you my latest unofficial build of LineageOS 16.0 for Pro1 (qx1000).
To make the thread more accessible, I'll recapitulate the full list of enhancements with respect to official every few months. So here it comes:
- Backported AOSP fixes up to the "1 March 2025" ASB (official LOS 16.0 stopped updating in January 2022).
- Improved keyboard behaviour, partly backported from later LOS releases (code changes can be found in my local patch tarball).
- Several more improvements with respect to the upstream LOS 16 tree (GPS fix, touchscreen margin control, ...) as documented in that same patch tarball.
- Updated graphics driver stack (using the same blobs as LOS21 & 22).
- Updated bundled WebView to Chromium 134.0.6998.95 (important for those running without Gapps).
Have a lot of fun.
-
3
-
I've just uploaded build '20250309' of LineageOS 16.0 for OG Pro1 (qx1000) to
https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1
Changes since last release:
- Backported fixes up to the "February 2025" Android Security Bulletin.
- Updated system WebView and browser to Chromium 133.0.6943.137.
Have fun.
-
2
-
2
-
Thanks for the feedback.
With my Pro1 still on LineageOS 16.0, this works. I can select multiple layouts under "Keyboard & input methods > Physical keyboard" and then cycle through them on the fly. Pretty cool, actually. I didn't know about this feature.
However, on the Pro1 with LOS16, the hotkey for layout switching is Ctrl + Spacebar. Yellow arrow + Spacebar is equivalent to pressing the power button in my case, which is another pretty cool feature introduced by @tdm with his initial port of LOS.
-
On 2/10/2025 at 4:15 PM, EskeRahn said:
Indeed, it was broken long ago, then fixed and later broken again, but you are right the chances of a fix seems slim.
OK. I just think: this sounds like a general regression in AOSP, as keyboard support in Android is generally nothing specific to the Pro1 (hence my question whether this is also observed in the Pro1-X port). I just wonder if it could be worthwhile to open a bug against LineageOS because of this.
-
10 hours ago, EskeRahn said:
And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage.
I probably missed why you have been including this warning every week for quite some time. Is this problem unique to the Pro1 (as the corresponding qx1050 thread does not mention it)?
Anyway, it seems I can find no open bug reported against LOS about this. So, whatever your issue is, I doubt it will ever be resolved "automatically" by an OTA.
-
Another unofficial build of LineageOS 16.0 (for qx1000) is here, celebrating 3 years of support beyond its AOSP EOL. 🥳
At
https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1
Go for the ROM dated 20250203. Changes since last release:
- Backported fixes up to the "1 January 2025" Android Security Bulletin.
- Updated system WebView and browser engine to Chromium 132.0.6834.122.
Have fun.
-
5
-
1
-
11 hours ago, CornholioGSM said:
Passport have on lineage same problem as was on FX (first custom roms) - multipressing keys.
Can anyone help me fix it? Will be needed to add something like key press deelay.
The respective fix for the Pro1 is here:
https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_msm8998/+/318274
Note that this is specific to the qx1000.c keyboard driver in android_kernel_fxtec_msm8998, it won't be directly applicable to another device.
-
1
-
-
The only way of "upgrading" is installing LineageOS 22, which will give you the equivalent of Android 15.
Since LIneageOS re-uses most of the device drivers from stock Android 9, it is unlikely that audio or camera quality will be improved. At least I do not know of any such updates.
That being said, a recent LineageOS will give you all those Android security patches since 2020, which is of quite some value in itself ...
-
2
-
-
7 hours ago, cash said:
TL;DR: I ended up getting the battery to charge after disassembly.
Congrats. 👍
I once documented my very similar procedure here:
This was before the rubber-band trick was discovered, so I hadn't tested if that would have worked in my case.
At the time, I also measured 0 V between the pins, but you are probably right, that the internal protection disconnects the cell below some critical value. My Pro1-X has been working fine since (though I do not use it much anymore).
-
2
-
-
This is ridiculous. I understand that F(x)tec are low on resources, but Let's Encrypt certificates are available for free! They literally would only need to run the 'certbot renew' command.
I can only hope they will pass on the contents of this forum to the community in some way before the server goes down, otherwise all the (mostly unofficial) info on the Pro1/Pro1-X we have collected here will be lost ...
-
2
-
-
Slightly off-topic: My browser has been flagging this site as insecure for weeks. Could someone please just run 'certbot -renew' once? 🙄
-
3
-
2
-
-
The latest unofficial LineageOS 16.0 (for qx1000) is available at
https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1
Go for the build dated 20250108. Changes since last month:
- Backported fixes up to the "1 December 2024" Android Security Bulletin.
- Updated system WebView and browser to Chromium 131.0.6778.200.
Have fun.
-
2
-
6 hours ago, diejuse said:
I'm having issues with the physical keyboard since I tried installing new versions of LineageOS. I recently reinstalled stock rom but the problems persist (key repetition or no response sometimes). I'm sure it's a hardware issue.
Do you notice any issues with the physical keyboard with this modified version of LineageOS?Those are hardware issues, unfortunately.
All recent releases of Lineage (including mine) have a workaround implemented in the keyboard driver that suppresses unwanted multiple keystrokes (https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_msm8998/+/318274).
For the undetected keypresses, there is unfortunately no software fix. I have three Pro1s. One (the oldest) has that issue to the point where the keyboard is almost unusable, the second has one or two keys that sometimes need two presses to react. Only my most recent device has a flawless keyboard.
All three run the same version of my LOS16 ROM. So it must be hardware issues, I think.
-
3
-
-
On 12/13/2024 at 5:56 PM, QuestionMark said:
Per the specs, this is a 5-G capable phone
Nope, it isn't.
On 12/13/2024 at 5:56 PM, QuestionMark said:The signal icon in the upper right corner of the screen has always shown 4G LTE -- until recently. Now it simply shows 4G
My Pro1s (still on LineageOS 16 and located in Germany) generally indicate "LTE" or "LTE+", which are different variants of the LTE protocol. In areas where network coverage is bad, my phones drop to "EDGE" (2G, still available in Germany). You are supposed to be able to somewhat influence the protocol switching behaviour using the "Preferred network type" system setting, but I've never seen much effect while playing with this. For practical purposes, "4G", "LTE", and "LTE+" are pretty much equivalent, and indicate the Pro1 is operating at the fastest protocol family it is capable of.
Note that even while being connected via a (theoretically) fast protocol, your effective data transfer speed may still be reduced for other reasons (weak or noisy signal, too many other users on the same tower, throttling by provider).
On 12/13/2024 at 5:56 PM, QuestionMark said:It's as if the device is not connecting on the LTE bands, and has fallen back to EVDO - the older 4G protocol.
Note that pretty much any network protocol may be transmitted over any physical radio-frequency band. As older protocols are phased-out, their frequency bands become free for carrying new ones. Also, usage of frequency bands differs from country to country, as this is governed by national authorities. The same band that may be used for LTE in the US may still be occupied by 2G in Germany, or 3G in Scandinavia.
EVDO is part of the 3G family of network protocols. I believe it was shortly (and deceptively?) marketed as "4G" by some US networks ages ago, but not in the rest of the world as far as I know.
On 12/13/2024 at 5:56 PM, QuestionMark said:Now it simply shows 4G and the signal seems to fluctuate from 1 bar to 4, sometimes dropping to no bars. Same physical location
The RF hardware of even a fully functional Pro1 is far from stellar. Using any App able to display the actual signal power of the radios, you'll see that the latter is rarely above -100 dBm, even if all bars are displayed in the screen corner. If your data transfer speeds are OK and your VoLTE works without interruptions, be happy and done with it. Sadly, there just isn't much safety margin in the radios for f(x)tec phones. When I'm on the move (Germany) LTE network interruptions are common with all three of my Pro1s.
If your connection used to be better at the same location, I'd just assume they changed something on the antenna towers. As @EskeRahn suggests, they might have fully or partly (via DSS) repurposed some RF bands from LTE to 5G. As a result, your Pro1 effectively would not be able to use those frequencies any more, and be forced to revert to one of the remaining LTE ones (which might have lower signal-to-noise). Not much you can do about that.
On 12/13/2024 at 5:56 PM, QuestionMark said:Is there just 1 antenna for multiple frequencies/protocols, or a separate antenna for each protocol?
The actual antenna is the (segmented!) metal back of the phone itself. Depending on the carrier frequency, RF signals are picked-up from (or injected into) it at various locations via spring connector electrodes. The latter are distributed over three so-called "antenna" PCBs, named "main", "diversity" and "wifi/gps". The first two work in tandem to provide mobile-network connectivity. See the corresponding patent https://patents.google.com/patent/US20170117614A1/en for technical details.
-
2
-
-
4 hours ago, Rob. S. said:
[...] a bit of a roulette game [...]
@Rob. S. is absolutely right. QA with F(x)tec phones - especially with the Pro1X - is practically non-existent and you may always end up with a device that has issues in core functionality. And even the "best" specimens come with shortcomings you would never accept from a major manufacturer. Unless you really want that hardware keyboard, you should avoid the Pro1 and even more the Pro1X.
-
1
-
-
Hi @drcp,
@Hook has written down all the essential information already.
I just want to add that, while the black spots in the corners are standard for these screens, they do not worsen over time. I own three Pro1 and one Pro1-X: All have the black corners to some degree, but even for the oldest device they have been stable over time.
Concerning QWERTZ vs. QWERTY: F(x)tec lost many QWERTY devices to unauthorized grey marketing by their Chinese logistics partner company, which is likely the reason they ran out while shipping to backers. If you are really unhappy with the keyboard layout: Even practically unused QWERTY devices are quite commonly available on eBay et al., while QWERTZ ones are pretty rare. Maybe you'll be able to sell yours at a good price and get a QWERTY one instead.
-
3
-
3
-
-
1 hour ago, suicidal_orange said:
Without knowing what your expectations are [...]
Camera functionality seems to be important to @mangled. The device pages for Pro1 and Pro1X still state camera stack to be unstable and video recording not to work at all. So I guess the question is whether this information is up to date.
Beyond that, here as well as on discord, users reported many more issues related to things fundamental to daily phone use, like mobile connectivity, battery life, and stability of core apps. Those problems are not mentioned at all on the project page, which lists the Pro1 and Pro1X as "officially supported".
A brief, but honest, report about how usable Droidian is as daily driver on the Pro1/Pro1X would be very interesting, indeed.
-
1
-
-
On 12/1/2024 at 9:53 AM, Dr.Colossos said:
Termux X11 on Android there, and that works surprisingly well, without me being forced to jump thru hoops getting, e.g., 2FA banking apps to work, which simply run on main Android.
This.
That's precisely why I gave up on all those alternative OSes that are said to be more "Linux-like" than Android but, actually, are just AOSP piggybacking another UI via libhybris.
Like you, I settled early for a combination of (Google-free) LineageOS and a chrooted Debian Linux install, giving me native access to the huge Android ecosystem of apps. Unfortunately, the latter is just necessary nowadays. On the bright side, I can cover almost all my needs with FLOSS Android apps.
Installing some alt OS that claims to be "real Linux" but, actually, runs on a containerized version of Android (Hybris/Halium) hidden beneath? That still has me run my desktop Linux software in another container -- just like native Android? All that to end up using Android's Firefox or Chromium Apps nonetheless (because the alt-OS's "native" browsers don't cut it) -- using even more container tech (Anbox/Waydroid) for that? Technically interesting, maybe. Makes practical sense? Not to me. 🙂
-
2
-
-
On 11/29/2024 at 10:06 PM, Dr.Colossos said:
while Ubuntu on a phone is nice, it really is far less powerful then I have imagined. No Firefox, no Thunderbird, ages away from running docker ...
Back in the days, Canonical wanted people to believe Ubuntu Touch was the Ubuntu GNU/Linux distribution for PCs, just repackaged for their mobile phones.
Of course UBTouch is nothing even close to that. Fun fact, it does not even use a Ubuntu Linux kernel! It runs on the same Android kernel and proprietary drivers than Stock, interfacing them using middleware layers. The latter, however, can be used only by specific "native" UBTouch apps, not by your random favourite software from the full Ubuntu distribution.
You can run Linux Firefox or Thunderbird on UBTouch just like you can on Android: Using some Unix container technology and without any hardware acceleration. This leaves you with no real advantage over a Termux setup on Android, and is of course not what the "Real-Linux-in-your-Pocket"-promise of Ubuntu Touch once made people expect ...
At the end of the day, Ubuntu Touch is just another phone OS, based on Android technology and copying Android concepts. Imho that's why it never really succeeded even in the Linux community and was abandoned by Canonical.
-
3 minutes ago, Dr.Colossos said:
I think I only need to ...
Yep, think so too, see above.
-
Have you performed the steps listed in section "Repair sensors/ folder in persist.img" of this post:
I understand those steps are necessary after flashing back to stock from UBTouch. Note that you need to root the device.
Also, please note that I never tried Ubuntu on the Pro1X, so I never had to do this procedure myself. Just trying to point you into what I think is the right direction ...
-
1
-
-
Newest unofficial LineageOS16.0 (for SD835 Pro1) is available. At
https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1
get the ROM dated 20241116.
Changes since last month:
- Backported security fixes up to the "1 November 2024" ASB.
- Update system webview and browser to Chromium 130.0.6723.73.
Have fun.
-
4
PRO1, LineageOS 16.0 Official Builds: Discussion
in General Discussion
Posted
An updated build of LineageOS 16.0 for OG Pro1 (qx1000) is available for download at:
https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1
The build dated '20250504' gives you backported security fixes from the Android Security Bulletin up to the "1 April 2025" patchlevel, and updates the bundled WebView to Chromium 135.0.7049.100. Otherwise no changes with respect to last month's upload.
Have fun.