EskeRahn

Unfortunately not.... 😞 merged your question in here.

Thanks for the quick fix. And all your work in general. No pain at all, just shared here so others could skip this update.

Does the destination of the tracking look correct?

Francisco is not a bot - but most likely over-burdened with tasks, But I do agree, that their communication-skills are sub-optimal, to put it mildly.

...Flashing the boot.img from 20230427 gave touch back to recovery, and optimistically went for a dirty flash downgrade without a wipe. Surprisingly it worked 😄

Yup lineage-20.0-20230501-nightly-pro1-signed.zip is severely broken, no touch! The bug is in the boot.img too. I had to navigate with the side keys to even flash. Using the Tab-key and side keys, it can be operated somewhat, and all seems well - except touch....

Indeed it looks bad, but the thing was users can do from within here is tag them, We can only hope that the lag of response is because they are digging to find out what on earth went wrong, but it really looks bad....

I think Hook got the most likely explanation, that they gave you the wrong tracking number - obviously that does not change that things are messed up. I doubt very much that it is a deliberate action against you. But I do understand your frustration and felling of them adding insult to injury....

Yeah, I was way to optimistic putting the polls up late summer....

Indeed. I guess it would need to do more various shapes to have a broader interest. But if it can be done with out creases I think there is a market, as you would get a 'real' keyboard without sacrificing screen estate. Especially for fold-devices it would make a lot of sense to have one half with dual usage... Sort of like the Cosmo. But obviously a matter of how the feeling of a 'key' is, But with a little development there could be flat plates at the centre of each bubble , So you had a feeling of pressing a more firm surface and not a jelly-feeling.

Yes I know that as a moderator I should show a good example and not post off topic stuff. But this IS on keyboard phones, so not completely off topic. A flexible display with physically pop-up buttons https://www.gsmarena.com/researchers_create_an_oled_panel_with_inflatable_keyboard-news-58402.php (tldr: go to 3:38 in the youtube video linked)

Let us hope @Casey can get the parcel stopped, and rerouted to the correct address.... But the tracking already looks weird that it GB-to-GB should take a whole week... That date would be more what we would expect if sent GB-to-US

And sending it GB to GB at that price seems excessive! I wonder if there somewhere in Blyton is an address that looks somewhat like your US one?

Interesting! But the leading text for ACCURACY_THRES seems to indicate that you now include some that were previously thought to poor quality signal to use. Obviously what you got is much better than nothing 😁, but the really interesting question is why the receptions of these are so poor that they go under the default threshold? 🤔

Just to be sure, @ghosttouchscreenguy, Try to press the top part 'together' all way round, we have a while back had reports of odd thing in here if things get loose. If you can feel it move pressing, there might be a screw that need to be tightened. Or if you can hear a 'click', that might be enough.

(lineage-20.0-20230424-nightly-pro1-signed.zip on April 5 security patch installed smoothly using adb sideload and MindTheGapps-13.0.0-arm64-20221025_100653)

Same here, I only know that it is charging, because I have inserted a small usb-meter between the charger and the phone. ADD: Same on stack android.... Though here pressing power briefly gives an icon

...And it decreases slowly, just passed 0.4A, downwards. (Still Off)

Just wore down a Pro1 with LOS 20 to 89%, powered off, and attached to charger, and it pulled about 0.95A, and then went to 0.6A (assumably crossing the 90%)

Now that is interesting, it works fine on my Pro1, though slow. And with no indication - I can see on the amp-meter that it pulls. Unfortunately (for this) the battery is almost full (99%) so will need to discharge it a bit, to see if I get a pull above the 300mA I currently see.

That close to full, the charging-circuit ought to reduce the charging current significantly (any device), to protect the health and overall lifespan battery, so makes sense that it in this almost-full end, predicts times not hugely apart

(now available https://download.lineageos.org/devices/pro1x/builds ) Rather surprised to see that the boot image is NOT the usual 64Mb but 96Mb

At that raises the question if it is more interesting to know that there are issue, or to hear about possible workarounds? And that is NOT saying that a workaround is a solution. But I will claim that what ever workaround that make things useful for a user, is better than just storing it in a drawer. Waiting for a fix. Our complaining about things not working in a user-to-user forum, are hardly speeding any solution at all. At best it can tell others with similar issues, that it is not a fault specific to their device alone.

Unfortunately I have to agree, and as some suggested it might be needed for FxTec to send someone abroad to (try to?) reproduce it, if either they do not get useful logs, or these do not give any clues they can use. In some odd way it would have been nice If I had had the problems here, and could try all kind of weird stuff.

I think this is spot on. But just like we don really know how large a portion that are affected (could be anywhere from almost everyone to almost no-one), similar we do not know who the 'average buyer is', we are just guessing. I have the same guess as you here though. But Hook might be a typical user... I really do not know. On the issues of this thread we know that it is seen it multiple environments, but as said earlier as some do not see them, the big question is if they are just lucky, or the one reporting just unlucky. Since FxTec said previously that they were unable to reproduce