All Activity

Except that, after maybe the first half of 2020, I have never used it as a phone. Same with my Pro1x although, in fact, my Pro1x actually works pretty well as a phone. They are pocket computers for me. I'm retired and don't do a lot of phoning, Mostly the phoning I do is related to my home health care of Mrs. Hook and I use a Pixel 7 Pro on Verizon for that as I need great coverage and reliability for that. 🙂 Other than that, I don't even give most people my phone number. I prefer asynchronous communication.

You are saying your Pro1 ceased to work as a phone. This is no minor regression for such a device.

I've uploaded the latest build of LineageOS 16.0 (for OG Pro1 / qx1000) to https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 The ROM dated 20250723 contains a WebView updated to chromium 138.0.7204.63. As Google did not publish any ASBs for July 2025, there are no further changes with respect to last month's build. I decided to still bump the security string to "1 July 2025" to reflect the fact that the system browser was updated. As usual, you can get an idea of the full list of changes with respect to the last official LOS16 from the patch tarball also available

Yes, I am able to browse (wifi turned off-- it is actually quite fast) and I was able to take a picture and then text it to my Pixel. The only thing not working at all are calls. It thinks it is calling, says it is calling, but there is no audio feedback for dialing or ringing. The phone part is dead. Don't know why. But, my battery drain is fine, wifi on or off.

The aeroplane mode could be worth a try. I might do it, but it will take a bit as I need to first assure that the problem is still there in normal mode. If I recall correctly I tested with mobile data OFF, so an interesting theory if it is related to the ability to make and receive calls. @Hookcan you use mobile data for say browsing on yours, or is that broken too? I understand SMS works. Does MMS? Just to try to narrow down the parts that do NOT work on yours, as the bug must be related to one of those. PS Note that my provider does NOT offer voice over LTE for this phone model (one of

I still like the theory, suggested by @EskeRahn, that it is related to cell connectivity, and I don't think it matters much what the network preference is. I don't have the battery drain issue with Lineage 22.2 on my Pro 1, but my Pro1 can no longer make or receive calls. It has a SIM, knows it has a SIM and is fine with texting and data, but can't call. If I put in another SIM, the same thing happens. I guess a test might be for someone to put the phone in airplane mode (you can turn on wifi, but leave the cell connectivity in airplane mode). Maybe my lack of cell connectivity (and I mean t

Sorry for the "delayed" answer. I didn't activate notifications. Therefore I did not realize your question earlier. I activated notifications now. My Pro1 was on the June release of Lineage. I just updated to the July release. I will report the effect of the update on the energy consumption in a few days. Just for information: I use the MicroG version of Lineage: lineage-22.2-20250719-microG-pro1 (https://lineage.microg.org/ and https://download.lineage.microg.org/pro1/). There are no GAPPS installed on my Pro1 and I have even removed most of the Google stuff that was in the ROM.

Lineage-22.2-20250721-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

If on stock, use FinQwerty by @Anssi Hannula you can find it in the normal android market. to handle 1 and 7. (It really is not a running app as such, but presents the right configuration files for the wanted layouts to system on boot, so we an choose them side be side with the normal ones) PS Dansk og norsk layout er 99.9% identisk, Æ <-> Ø.

Are you still on stock Android, or have you updated to LineageOS? I recall the problem with Chrome refreshing the page from the fingerprint sensor was present in the stock Android, but fixed in LOS. IIRC, the work around was to switch to Firefox, if you don't switch to LOS. Some of your other issues might work better with LOS, too. No real downside to it, except for the time it takes to set it up.

Just to be sure, you are on newest 22.2? So that means it is still borked?

Hi everybody, I just wanted to mention here, that I am one of the Pro1 users, who is effected by the battery drainage of the Pro1 after the update of the device to Lineage 22.2. For me, this is really a mess, because I used the Pro1 as my so called "daily driver" for the past 2,5 years. 😢 Like TeZtdevice, I also assume, that it will take me too many hours to downgrade the Pro1 to a previous Lineage version. Unfortunately, I will not have the necessary time for this task before September. To "survive" until September, I reactivated an old Samsung A10. ☹️ I cross

forHello My iphone just died and this is my only alternative How do i make the phone usable There are 7 points that make this a completely useless device for me 1 the keyboard does not work with scandinavian layout so the ae oo aa letters are in swedish öä but i am norwegian so i need my norwegian letters not swedish And aa is missing entirely. I just found the comma and dot, great. But there is still no question mark or exclamation mark. 2. There is no working web browser. Chrome reloads the page 24 slash 7 when you hold the phone. It is not possible

Had 3 available updates and started from the oldest. Then figured that could update from the most recent one

Well it is a choice. They COULD have made the update system as a primary version and then a series of deltas. The flipside of that would be that any reinstalls or new installs would require to first load the old full and then maybe scores of updates, installing all in the same partition, and this could be slow. And it would add some extra complexity in generating and applying the deltas. It is much simpler to just have a source that builds a total, and then distribute that, despite the extra traffic, and slower installs than the delta could have given, if it started by making a copy of the run

The point is that the updates are not incremental. The weekly OTAs each time contain the full ROM, even if changes relative to the previous one are minor or non-existing. The idea behind the a/b partitioning scheme is to keep the previous version of the system intact for backup, while flashing a completely new version of the OS to the respective other slot with every update. This is to make sure one of the slots always contains a working OS, even in case of a bad flash or faulty download.

The strange thing to me was having two 22.2 updates of 1Gb each and i was not sure if i should go trough

I've had this [almost] exact problem with my F(×)Tec Pro 1 back since mid November of 2022. After getting the phone brand new and using it for 2 & 1/2 years (yes there were a few accidental phone drops from small heights that produced only miniscule aesthetic scuffs on the corners): it was still in near perfect condition minus only one of the symbol switching keys not working on the keyboard. So that's some context, yet other than that it was in full perfect working order (in a condition of slight use) without any screen cracks nor damage (aside from what's aforementioned).

Remember, the updates are not just what is being added... they are the whole package with the updates integrated. (They don't disturb your settings and data).

Yes, that´s a normal file size for a currently update.

Hi there. I have Lineage 22.2 installed on my Pro 1X and still shows an update to 22.2 about 1Gb. Is it normal? Can i proceed with the update? Thanks

Lineage-22.2-20250714-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

Lineage-22.2-20250707-NIGHTLY-pro1x with June 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

Update on the battery, it seems the radio is to blame, and changing the network type seems to help. This night the phone was on my nightstand and over the course of 6 hours went from 100 to 34%. Network was set to LTE/TDSCDMA/CDMA/EVDO/GSM/WCDMA. Looking at battery usage over system showed the radio as the big culprit. (See image). I've set it before to LTE/TDSCDMA/GSM which seems to work for my local cell network, and battery life seemed to be good, however sometimes the phone would hang while on standby and I changed the network type hoping this would not happen. It didn't happen but th