Leaderboard

Here is the latest update they wrote here:

Hello. It's like threads gravedigging, but just a week ago I finally brought my pro1 to life by replacing a broken display with Ulephone U one bought on ali (and it didn't require any "firmware update for the touch function to work correctly"). But the point is that just a few moments ago I think I managed to solve problems with too loud handset sound volume and distortion. I replaced "/system/vendor/etc/mixer_paths_tavil.xml" with a file from latest Google Pixel 2 LineageOS (it shares the same MSM8998 CPU). I didn't have much time to test it thoroughly, but sound seems to be much better.

I was told by them it's in the order they received the payment. Using that logic, if someone bought online before igg and they got swapped into the PRO¹-X, they receive before all in igg

For some additional detail on the above: I was having a screen issue and I sent my phone in for repair back in April 2021. I received "my phone" back late last month, but it has a different IMEI and the few cosmetic scratches I had on my phone are gone. If I had to guess, I'd say they just gave me a brand new phone instead, but it didn't come in a retail box so I can't say that for certain. So I'll go with "factory refurbished."

See this thread for working install: ---------------------------------------------------------------------------------------- Below is initial attempts where I used a wrong boot image Using this AICP.S mage aicp_pro1_s-17.1-WEEKLY-20220713.zip I was super optimistic and went from 16.1 with OpenGapps to 17.1 and MindTheGapps 12 in one go, without a factory reset (=wipe). ...and that did not go well,,,, I got a boot-loop (I used the recovery-image from Lineage lineage-19.1-20220711-recovery-pro1.img) Then did a factory reset, and it booted - obviously with

I payed at the end of May 2020. If you are right, I can hope. Hopefully we are not getting an update like "fire destroyed first batch" or "bandits robbed first batch" next week.

I hope you are right 😁 Though we never found a way to consistently trigger the bug, so hard to say for sure. Has anyone that updated to 20220711 seen the charging-bug since? Bad news: Just managed to trigger it...... (at 67%) What I did was: In unlocked state, Plugged, unplugged and replugged a few times Locked, waited three minutes (while it was charging on a table). Picked it up and unlocked the device with fingerprint Unplugged and replugged Tried to do exactly the same after a reboot, but it did NOT trigger it again, so not a consistent method, Tried

Since flashing this version, I haven't had a single issue with charging. Up until this version a reboot was required every single time! Bluetooth and GPS still suck though. Unable to get a fix and BT connection is limited in distance and stability)

Any chance they got their hands on a pre-production Pro1x and forgot to label the ROM properly. Lol

I have a factory refurbished QWERTY Pro1 for sale. $650 shipped within the US. edit: SOLD

(on the wiring, the two shifts and the two ctrls are physically wired pairwise. so though we see 66 keys, there are only 64 distinct keys)

I get no response from the keys when using the built-in test software (the one you get when you click the build number multiple times).

I don't seem to have either an advanced option or an option to view recovery.log. Remember that I'm on stock.

At least now I know who has my phone. This phone was used for one week, indoors, by my daughter. She then decided it was time to abandon the physical keyboard. A year later I tried to boot it, it wouldn't. FxTec replaced the screen and battery. Same mark, look at the picture. Pretty annoying you have my phone. But, I wish you and/ or the new owner the best of luck with it. I'm not going through the shipping idiocracy again...