EskeRahn

It most certainly can! 😄 I have been using it since 2019... See e.g. the slo-mo video where I use one from the 'open' thread here. I have a lot of blah blah in this thread in my blog, and we have a long thread in here as well. Sure it is DIY, but we are talking a few minutes of work that anyone can do (no special skills required at all) YouCut_20200123_155044091.mp4

It is a bit odd that there are no more security updates on AICP-R, since June. And on the other hand the security patch level for AICP-S is March, so I guess they see S as still in development? I would also like to know if it is me that are doing something wrong or they see the same splash screen? Should I e.g. use a different boot-image than I do? I copied the most recent boot-image available at the time of the first AICP-S: lineage-19.1-20220711-recovery-pro1.img should I use an earlier or a newer? (I have saved a few older 0426, 0502, 0530, 0627)

Flashed today's release aicp_pro1_s-17.1-WEEKLY-20220810.zip, Security patch March 5 and MindTheGapps-12.1.0-arm64-20220605_112439.zip (without factory reset) And it is the same error as above. Boot-loop some ten 10 times, , Boots with error screen, and all seems to work, except this splash screen on each boot. (But to make things clear, it is 'only' on the first try after flash that it requires a reset)

Interesting that there should be a difference there, Note that not all camera apps support the half way click. But yes it work, it just takes some getting used to that when the button is pressed slightly and is thus 'free' betweens its in and out position, it is in the 'halfpressed' state. I have seen some compact cameras working in the exact same way.

Correct. IF we could get a fully covering 3D-curved tempered glass protector (as was/is available for e.g. the BB priv and Samsung S8) Then you can be lucky that it takes the impact and scatter, leaving the display intact. But I have not seen those available for the Pro1 or the Elephone U using the same screen. I tried to cut one for a S8+, but it is really hard to cut it without it just scattering, I tried to cut a couple (using a diamond glass-cutter) to no avail, and then tried to make several cuts shortening the remaining to practise - I never succeeded

If there is no OS it find as bootable, you'll need this bootloader screen to fastload a boot image, and EITHER fastload the rest too, OR boot into the recovery mode from the bootloader and "adb sideload" a zip file with the packed images (the zio is how e.g. LineageOS and AICP usually is flashed)

Thanks. Both Google and the fruit company are crooks!! I got an ancient Iphone 6, That I played around with a few days ago, and the funny thing is that if you try to turn it "off", it drains from fully charged to 0% in less than a day. If you keep it "On" and just let it go into the normal standby, it's consumption is roughly 20% per day!!!! So God NSA only knows what they are wasting my battery for when "Off"!!! Maybe it is not NSA, but just aPple that want to completely deplete the battery to better shorten its lifespan?

So you are saying that we actually need to open the phones and add some contacts to disconnect the WiFi and GPS antennas when WE do not use them.... YIKES!! I knew they were crooks, but not that it was THAT bad... 🤬 It is what I would expect from the scrupleless fruit company.

I haven't read it, but guess it in many words says "We will track you, and steal all your data, without asking again, and you have to pay for the data transfer doing so".

As I see what goes on on the screen, the button seems to have two connections and an open state in between. That is unpressed it obvously is in the 'unpressed' state And as soon as your finger press releases it from its 'unpressed' state, you are in the 'half pressed' state. And pressing it fully unsurpringly gives the 'pressed' state, That is, as there is no middle 'point' creating a contact, there is no felt feedback reaching it.

What you see is commonly referred to as Bootloader mode. And from here you can add software with the fastboot command from a pc. Unfortunately we do not yet have a guide on what parts of the supplied file that should be loaded nor in what order. The over all principle is that from the old Pro thread here. The newest version of the needed official adb/fastload software can be fetched here..

Yes a rough draft would do fine for now, it can always be 'polished' later. @Casey, could you help out here? Just a list of the needed files in the correct order would be a great help.

On the Pro1 it got two steps BUT you can not feel the half-pressed, you will have to rely on visual feedback from the photo app. OpenCamera e.g. gives a square frame.

I'm not sure Google allow that for stock Android 11, So you would have to use some AOSP based like LineageOS or AICP when they become available.

If I recollect correctly we had similar reports in here on the Pro1. Though not as bad as @RichC73 reports.

Could be. But before opening I would contact FxTec ( https://www.fxtec.com/support ) and hear their opinion on the subject - as a user to user forum, it is never sure if FxTec sees a post (or even thread) in here.

I hope you are right. We will have to wait and see to we have more units delivered to see if this is for a specific unit, or a general issue. Though at the least for the Astroglide, radio firmware is bit more complex to update, according to the EE section of their update - it might or might not be the same for Pro1X.

I moved your post into this quite large thread, as the same covers and screen protectors should work equally well for both models.

(lineage-19.1-20220808-nightly-pro1-signed.zip on July 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220605_174313) Still with the keyboard bug introduced that messes accessibility apps (works on AICP R/S based on Android 11/12) see e.g. this.

Over at IGG, "Buffer Bear" was charged "UK. Duty of £51.45" so it seems to vary quite a bit...

The Pro1X was PLANNED to be a Pro1 eXtended with more ram, and changed key-layouts.... But after they were swindled, they had to redo the whole thing with a different chipset, and this is why the old code was supposed to have worked (almost) unchanged on the planned Pro1X, but will not work at all on the actual.

Well IF your unit proves to have faults and you have sold it unopened, you could clearly say to be in good faith, and any complaints be between FxTec and the new owner.

It should be fairly easy to sell it for more than the customs amounts to. What key-layout have you requested? The Pro1s have had a high resale value on e.g. ebay used. And if unopened, it should be even easier.

Yes let us hope they found a more serious and honest subcontractor this time.

If the double shift in LOS had activated caps-lock, so Caps key could release it also, it would be a lot less confusing, than release by a single shift. Currently if you click Shift and regret, you have to click TWO more times to cancel it (one to enter pseudo-caps, and another to exit). Had it required the two clicks on shift within say half a second to get pseudo-caps, it would be natural to after a slight hesitation a second click on shift just released the sticky.