EskeRahn

Interesting. Does the solution you got working require the phone-display to be set to 1920x1080 (see a few posts above), or does it crop the sides on then monitor? Or does it offer two independent screens?

Flashed aicp_pro1_s-17.1-WEEKLY-20220928.zip on security update 2022-03-05 Still initial boot-loop after flash, And still completely confused! Despite the outer file signals aicp-S and 17.1, the inner version is aicp 16.1 and tells it is Android 11???

Until windows started to require signed drivers (that they later relaxed on), I felt the same, super easy plug and play, how hard can it be...? But later I could not get it working at all, and understood what people was on about., To an extend I limited myself to OTA, for the weekly updates. And PTP&MPT still worked just fine, but fastboot was a lot of trouble. but after a lot of experiments i got things working with an ancient cheap $1 usb-hub, that is terribly slow. And when I got a new PC it got even worse, I then optimistically plugged the USB in the docking hub, and it have worked fla

Interesting, I have not done their OTA for ages.

https://nerdschalk.com/change-screen-resolution-adb-android/ Will test.... Thanks for the idea. ADD The resolution change works - but that is not enough to get HDMI working. adb shell wm size 1080x1920

(lineage-19.1-20220926-nightly-pro1-signed.zip on September 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.

Very interesting. If the info I quoted earlier is true, it might 'only' support FHD, so if that is the case, we might also need a way to get the phone to crop the sides from 2160 to 1920, so it can act as FHD to be able to mirror. If we are very lucky that is enough, as you have proven that it already somehow understands what is going on.

Yes, it can be easier to get things working with an old port, or perhaps using some hub. Obviously the usb-driver can also be the issue. Or even cables / can be quite a puzzle... On my Yoga it only works with an unsigned Google driver, and when going through a hub - currently using a thunderbolt 4 docking/hub

Sad story indeed.... I know the feeling of getting into the 'red field', and not wanting to waste any more time/or money to get things right, from dealing with other companies. I'm awaiting a Pro1X, so not in the market for buying one. But hope yours will find a new owner soon.

Looking for other phones with same chipset we got this list on gsmarena I tried googling for hdmi and one of them (the motorola G30) but found nothing. I did find a fairly officially looking answer suggesting using casting instead, so that sort of points toward that the chipset might not support it, and thus the link I first found could be wrong....

Are you sure about that? https://en.wikichip.org/wiki/qualcomm/snapdragon_600/662 I do not know if it is true or not, BUT it would mean that it can not just mirror the standard 2160x1080 resolution of the main display, and that MIGHT be what is preventing it from working when plugged in. So we would have to get the device into a FHD (or less) mode, for it to be able to do the mirroring. (I have no idea if the chipset/os can handle individual images on the two)

I wonder if that was a typo, or you being extremely pessimistic.... 😇

I have had the same thought. Could be nice to have a donor or two at hand if something breaks down in my daily driver. (That was working on the donor)

Would be awesome if FxTec could offer a setting selecting Full and Alpha, would be totally acceptable if a reboot was required after changing. With a switch people can choose what they prefer. IMHO both have their Pros and Cons, so would be great if each user could choose what matches our needs best.

It would be great if we could have an equally simple process to flash it to its stock Android-state (with GMS).

Much can change in peoples live in a couple of years. I see nothing wrong here - there could be a large number of different reasons. Though as being one of the many still waiting, I can envy those that got it, and feel frustrated that it was not those that wants it that got it in the first wave, despite being in the first third of the super early birds.......

Flashed aicp_pro1_s-17.1-WEEKLY-20220921.zip on security update 2022-03-05 Now I'm completely confused. Still initial boot-loop after flash, But despite the outer file signals aicp-S and 17.1, the inner version is aicp 16.1 and tells it is Android 11??? (I downloaded again, did a binary compare, and a re-flash - just to be sure, but....)

Be aware that AICP-R is gone within about a week, so hurry up and download!! See above

Be aware that AICP-R is gone within about a week, so hurry up and download!! See this

I must admit that I'm very close to giving up on AICP-S, since no one seems to be working on fixing the basic issues that has been there for over two months of initial release, and security updates over half a year old. So maybe I should look at sailfish instead....

It is really hard to guess what it could be, and you already know the standard suggestion: Factory reset and no apps installed, to see if that is stable, but not a very useful suggestion IRL, so as @Hook suggests, have a look at what have happened at the time the behaviour started, and peel off any new apps. There is absolutely no guarantee that an app is the culprit and even if it is, that this will find it. If an app it also could be an Android-market triggered update that have caused the problems. At the least you found a consistent way of making it crash, so I would suggest starting to

(lineage-19.1-20220919-nightly-pro1-signed.zip on September 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.

Well though I'm personally happy with my Pro1 (still waiting for the Pro1X), but that does not mean that everybody has to feel the same. So I don't see anything wrong in someone trying to find a new owner for it, that hopefully like it better. Though I had considered moving them into one thread.

Flashed aicp_pro1_s-17.1-WEEKLY-20220914.zip on security update 2022-03-05 Seems much the same. Still initial boot-loop after flash, But that aside things seem to work.

If people want to avoid the camerabutton launching the stock camera app AND they want to use a different app (e.g. open camera), a way to avoid accidental launches would be to simply disable the default camera app