EskeRahn

Ah of course X-mas, so that is what the X stands for.

(lineage-20.0-20231118-nightly-pro1-signed.zip on Nov 5 security patch installed smoothly (*) using adb sideload and MindTheGapps-13.0.0-arm64-20230808_213316)

Ah yes silly me, I'm so used to qwertZ that I did not look at the layout, so yes clearly original Pro1

I'm not able to tell the difference from the images for sure. I THINK the globe on the space bar is placed a little above the centre line for the original Pro1, and is centred on the Pro1X. It is usually easier spotted from the usb-end, as the usb sits a tad further from the back on the Pro1X (the centre of the plug almost align with the bottom respectively top row of the speaker holes) But yes there are some black Pro1X too, and indeed this one looks pristine from the photos, my Pro1 certainly doesn't look like that any more after four years of wear....

Wauw, an original Pro1, not a Pro1X, right?

As you got it open, I strongly recommend to charge it, as it causes a lot of trouble if it depletes....

We have not heard from Erik in here for months, so let me try to tag @Casey, and hope he and you can find a satisfying solution after this terribly long repair.

(added to the ROMs page, forgot it back then)

I would start with a clean install, and only gradually add the apps you using. In the current installation it is close to impossible to guess what it is. * Some app not working with the Pro1X for what ever reason? * LOS has some issues on the Pro1X? * The Pro1X is faulty? If it works 'clean', then we know it is something with an app. Try to install by 'binary search', that is install half the apps, if they work repeat with half of the rest. If it does not work, uninstall, and install the other half - repeat to you got most of your apps in, in a working state.

Has anyone checked if AICP is actually working again? I see a rather large changelog here a month ago https://dwnld.aicp-rom.com/device/pro1/WEEKLY/aicp_pro1_s-17.1-WEEKLY-20231011.zip.html but see no mention on a going forward on the base android version again Towards the bottom I see 149b0ef Merge "Track our own fork for CVE-2023-4863" into s12.1 So that seems to indicate that it is again on something 12.1 based?? - unless their whole s12.1 is borked and actually is an r11.x.....

(lineage-20.0-20231111-nightly-pro1-signed.zip on Oct 6 security patch installed smoothly (*) using adb sideload and MindTheGapps-13.0.0-arm64-20230808_213316) (Did another one OTA, worked smooth too)

You are right we should not jump to the conclusion but it certinly sounds like a reasonable explanation why it is working for some and not for others. And on this one I wonder what havoc that could make, depending on where it 'lands'?. It does not have to be a 0 to 3.8V short circuit to cause trouble, could be 'anywhere' exposed.

This sounds like a very important find. I marked your post as recommended, and would love to hear some official comment on this. @Casey perhaps? At the least that could explain why some sees this issue and some not, as it thus seems to be related to specimens, and errors in assembly (and QC).

(lineage-20.0-20231104-nightly-pro1-signed.zip on Oct 6 security patch installed smoothly (*) using adb sideload and MindTheGapps-13.0.0-arm64-20230808_213316)

A little foot note I'm not quite sure where to put. Just noticed on a Pro1X (not Pro1), when in OFF state pressing the power/button briefly, will have the led blink briefly, green if full, I do not know if it will use other colours in a lower state. So if a Pro1X will not boot, this might be helpful in telling whether it is a depleted battery or something else....

AFAIK this flag helps the Pro1 better than the Pro1X, but personally have set it on my Pro1X too - I never understood why this flag is not set by deault on ALL phones. I see the Auto-on function as a really odd function that it is hard to imagine a use case for. (Maybe auto-on could be usable for some with a handicap making it hard to use the powerswitch? But if so I guess they are unlikely to want a keyboard phone) But some things in Android are just oddly opposite to what you would expect. E.g we do not get a warning of risking privacy information when enabling location services, o

I beleive they had answered that. The problem is that there needs a minimal amount of charge in the battery to have enough power to boot enough to have the charging activated. AND combined with it not turning it self off early enough it is ALSO a future issue once it gets charged. So make sure it is never allowed to run flat....

Glad you finally got it, but sad that it is in a useless state... Well the only known remedy is to disassemble it and charge the battery directly with a suitable circuitry. That is what FxTec is doing with returned units. So sad that the road from production to delivery has been so long that this happens to several... So the only options I see is to return it/them to get fixed, or to disassemble it and charge. Rather than some fancy circuitry I have seen some suggest to use three 1.5A batteries coupled, as they have a limited power and thus are unlikely to damage the battery.

Necromancing this thread, please note that though this idea works fine on a pc (in a sufficiently large window), it does not work well on a all mobile browser landscape/portrait (*). Here you have to click the avatar and scroll down to "About" and "Rank" to see the info. On some mobile browsers you can select "Show as desktop site" or similar though, and have it appear. (*) ADD using Chrome it works in landscape, with my current "Font size"=Large and "Display size"=Small settings.

(lineage-20.0-20231028-nightly-pro1-signed.zip on Oct 6 security patch installed smoothly (*) using adb sideload and MindTheGapps-13.0.0-arm64-20230808_213316) Updates seem to have changed from Mondays to Saturdays for the Pro1

I think I can answer that part. If I remember correctly then at some point those with pre-orders were promised it would be with tax included (this might have changed for newer web-orders though). But I do not think such a promise were given on IGG. Hence the difference.

I do not know if it will ever be produced to stock. There are those with several years old orders that need to be served first, and they have not said when those will be all served... If you are in a hurry, it might be worth looking on ebay, occasionally some are up for sale. Also keep an eye out on this thread:

Last update 20231016 seems to have thrown the Developer options setting away, but can be reenabled, so adb connection works.. lineage-20.0-20231021-nightly-pro1-signed.zip on Oct 6 security patch installed smoothly (*) using adb sideload and MindTheGapps-13.0.0-arm64-20230808_213316 This update preserved the Developer options setting, as usual. Note the date, Not the usual Monday - not that it matters.

Working with Fastboot tends to be extremely picky on the connection. I have had good experiences with inserting a hub between the computer and the phone. Or to select a USB 2.0 port Fastboot can work with USB 3.0 but is really picky. When I go through my thunderbolt connected docking, and use a USB 3.0 port on that it works smoothly, but not directly connected to the laptop.... ...On windows it can also be quite picky on the driver...

Thanks, but could you give us a rough ball park figure of the fraction of the total covered after the 700+ ? E.g. which of these do you estimate to be the closest : 10% 30% 50% 70% 90% ??? Or the other other way round if you prefer, how large a fraction will be pending afterwards.