VaZso

I hope so. They already have experience how these manufacturing-related things are going and they seems to have chosen a relatively wide timeframe. They currently have close to 1000 backers which is a number what can be clearly seen, so there is a chance a manufacturer takes them seriously enough to fulfill their needs, maybe the very same manufacturer is willing to do the process for them which is very likely. They know the background (remaining Pro1 orders, expected speed and potential problems) and they should not make the very same mistakes. I hope COVID will not cause a s

Right, but there is a borderline between normal Pro1 orders and Pro1-X campaign start at 27th October. So I assume all Pro1 orders taken before 27th October should be fulfilled before Pro1-X starting to ship. However, I am unsure if later orders of normal Pro1 may or may not be included in the last batch before Pro1-X starts to ship.

You are right, however, they expect delivery of Pro1-X by March 2021, so I think that is a good starting point to expect delivery of recent orders...

You may find it in FAQ section at their IGG page.

The first part of my message was related to this question. Unfortunately it does not work with GCam (as their hardware do not have such button), but it starts Snapgragon Camera instead. So I am in GCam, pressing the button (fully), then default camera app launches. Half-pressing does nothing.

Unfortunately, no. It starts Snapdragon Camera. Yes, that button is a good to have, however, the similar button of N900 was better (at least the feel of 1st stage). However, any phone is not really comparaple with a correct DSLR, but still camera button is a plus.

Right, unfortunately it is very likely because of the manufacturer of "Google Camera". 😞

Right, there are GCam mods which are much better than stock camera and also better than other solutions. That way it can take really good photos.

@MickH- if you try again the process, please be sure to also restart the phone by holding power button more than 15 seconds, then wait for the device to come up. That is because in EDL mode, it will only work once, so an interrupted process will result in a fault next time. Basically that is a very simple protocol, so the restore tool will upload and run an own code first on the phone, then it tries to process the required commands through that own code.

Wow, I have not seen the post above where @MickH showed the device under Windows - that is why I have asked it again. ...perhaps I have clicked on this thread by mistake and it showed the newer messages next time... Sorry for that. Edit: I have only missed that specific message, read the one before and read the one after... but I am not even remember of an existence of the screenshot itself, hmm. This new page starts at that specific message which is also interesting.

Right, but it should come up as an EDL device when it is connected to a cable, that is why I have asked him to check it.

Thanks, it sounds very good.

Does it mean users will be able to install it on the official LineageOS build for Pro1? So the solution may not be included when one installs LineageOS but can be added by this add-on mechanism and still receive security/other updates for the base OS? If it may work like this, then it will be a very good solution. I hate I can not save / restore my phone correctly.

Does it mean it will also work on stock LineageOS or it should be a customer compiled code base?

What is the chance it will work using an Android other than AICP? Is there any chance LineageOS team will also import required code base?

There is a Qualcomm EDL cable which, in theory, can be used to put the phone to EDL state. However, I have tried it using my home-made cable and also using a pre-built cable without any luck even with my own working phone. So I could not put my Pro1 to EDL mode using that method but my friend's phone which I have tried to flash fell back to EDL mode around 15 minutes after "restart". Have you checked if there are any USB devices appear after waiting more than 15 minutes? Linux may be better to identify if it is alive but Windows should also display it as an unknown hardware at first

It is a factory restore tool, not reset. It can be used to write stock data to flash. If it works, then your phone should work again. If your flash is faulty, then it can not write this data.

Hmm, does it have a Mic input at that jack? I don't know the answer but I thought it doesn't.

I have tried it earlier and it worked for me. However, "quick charge" feature did not work through it, but the phone has gained charge so it is clearly not depleted (battery percent was increasing) while I was playing Youtube videos on it. Currently it is not easy for me to take a photo, but I feel it is visible well and there is no problem with angle. In a dark room, it could have been much darker anyway. One thing to mention, when there is an indication which transforms from on to off state of the LED and back (so tries to change its brightness), it behaves like if it tries

The LED is switched on by software, so for charging indication, some part(s) of the software should boot up. My friend's phone which had flash (UFS) problem also did not have charging indicator, but it was charging anyway.

When you press the power button for maybe around 15 seconds, it should restart the phone. I mean restart by hardware, so even if the software stuck somewhere. What happened with your phone before you found the issue? So have you used it? What charge should it have by that time? I have not heard of similar issues but when my friend's phone produced a similar issue, I could switch off that phone by holding power button and it turned on, but it only appeared as a USB device after around 15 minutes. That was some kind of fallback to EDL mode (that is how it has identified by) and th

I use Firefox on my Pro1 but I have not experienced autorotate problems using stock system.

They have definitively done something regarding crackle issue as I have often experienced it earlier but I don't notice it now using the very same applications. However, it can be still a problem with Pro1 somewhere or the emulator itself.

Anyway, the 8/256GB upgrade could be solved regardless of the other parts like the black colour. The question is if they have the PCBs already manufactured or they are still pending as if they were manufactured then this upgrade will not be possible.

So that should be part of the initial flash image(s) which they shared here in a place which is not OS related. If it is only about sensitivity and there is no other information can be obtained from the display, then a general solution (which work with all of these displays) is not easy. Maybe this was one of the reasons they starting to use another display (manufacturer?) in the past.