EskeRahn

Interesting menu! Another way to get there is executing adb reboot bootloader (When adb is available only obviously)

I have fiddled with this on other phones, but so long back that I do not recall which ones. But glad to hear if some do not have this silly default. Thank

The Pro1X i got my hands on is not retail, but would be interesting if some that got retail version of both, could post some sample images.

This is not a solution, but just saying that if you use a shell or flip-case, a bonus is that it practically eliminate the inadvertent touches. We have had discussion on this on the pro1 as well in here years back BTW, and without sounding like an apple echo of "You are holding it wrong", it is also a matter of getting used to how to hold it. If used primarily in landscape it is the perfect placement for reaching with the right index finger. Maybe a simpler solution would be to have the fingerprint-reader only active in landscape, when the device is unlocked? Personally I would not min

…To those that are blaming FxTec for the shipping delays, see e.g. Astroglide https://www.indiegogo.com/projects/astro-slide-5g-transformer/x/16576339#/updates/73 “There are still limitations on courier shipping from the warehouse in Hong Kong.”

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

New August update, sadly delays at warehouse...

It would be nice with an official AOSP build, with updates, that LineageOS, AICP and others could build from.

@Spargeltim Just a wild idea if you have not sent it in. Have you tried with a FAST charger? (QC 3.0) It just MIGHT be able to provide it with that little extra needed (I do not know if the system handles fast charges that early, but could be worth a try)

PS And we NEVER want the battery to go deeper than when the OS do an Auto-shutdown, that is when it detects the voltage drop point is reached. Trying to charge a phone in this state will likely fail, if people did NOT set fastboot oem off-mode-charge enable Apart from the battery health, deep discharge can -if the above is not set- cause the phone to get in a state where you can not charge it. See e.g. the thread by @Spargeltim here. It is really annoying that phones usually come with this switch set in a way that might render it in need of service, if it depletes.

Deep discharge should indeed generally be avoided, though the system should do an auto-shutdown before the voltage drop starts. The only benefit is calibration, so perhaps once a year. Similar the system ought to take care of not overcharging too (it charges slower towards the end), and in daily life it is hard to stop the charging below full. Some software exists allowing more control, but AFAIK only for rooted devices. So my general advise is to use a slow charger, when the device is idle, e.g. at night. (More hints see e.g. this )

One of the most important things is to avoid charging the phone when it is hot. LiIon battery do not like being charged while above roughly 30°C. They prefer around room temperature. So better to charge a device before doing some heavy work, than after, when it is still hot. Moderate charging is best, I would suggest 30-80% BUT you need to occasionally do full charge as well as discharge, to keep the system calibrated. I have numerous entries on various aspect of the subject in this category on my blog. (the most basic of them at the bottom from ten years ago)

For an AOSP based version like LineageOS or AICP we will have to wait, and no, I have no idea how long, unfortunately.

There is an official guide on rooting (see this) . So I guess from there you can uninstall about anything. If you do not want to root, you can using ADB from a pc disable most. See this on how.

Have any of you having the issue tried another launcher than Nova? I'm experimenting with "Action Launcher", and I do NOT see the issue. Neither after a restart nor after a power down and up, nor a long power press. I DID notice that I get a 'black' launcher screen (notification and navigation icons only) for about 4s after a boot. I then tried power off and on and waiting a long time before entering password. And when entered it STILL took 4s until I got the 'desktop'. So 'something' strange is going on, that just MIGHT get Nova to time-out and crash. ADD: If you add the

Could be interesting with the test performed on the same (type of) SD in a/the PC. And perhaps another phone, to see if the limit is on the device, the card or the OS doing a poor job.

Expansys/FedEx have not even sent out the Batch 1 they got from FxTec yet.... Really annoying, but not much FxTec can do I guess. I'm in the first dozen on IGG, yet I still have not got a shipping mail, despite FxTec told me that Expansys has processed it a fortnight ago... They are as frustrated as we are on the situation.

Great, lucky you that it was not zx browser.... 🤣

That they worked initially is a good sign, so most likely you can avoid the full reset. I agree with @Hook's suggestion, but start with any app that is mentioned as active under Accessibility - or just switch its rights off under accessibility. And if that does not do it, focus on anything keyboard-related, or 'fancy', the more complex the larger the risk of it trying to be clever and mess of stuff. You could try to just STOP rather than uninstall stuff first, with the risk of them being brought back to live, making tests harder. A reboot often restarts a lot of junk you may have stopped

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

Yes, that is about the same functionality. The great thing about the other solution, was that it was impossible for the systems to (even inadvertently) mess up each other, as the production disk was simply not mounted while running something else. (I copied what ever data that needed to be shared to some usb-storage or SD with a RO-switch) ...For the most paranoid stuff, I had a disk with an OS with net removed, and unplugged the network cable....

Sad that it is not for you, hope you get a good price. 🙂

That could be a way to do it, yes, thanks. I miss the feature of my old Lenovo x300 and its easy way to swap SSDs/disks where I would just have used a separate disk

(Have a look at the reasonably pocketable Sony RX100 III, I think they are at VII, but photos on IV were marginally worse than III, and have not seen anything that persuaded me that V, VI or VII should give better images in poor light, in the wide end)

An ugly hack/workaround but something like py2exe, encapsulating all the junk might do the trick. It is not that I see it as malware. I'm pretty picky on what I install on my PC, and let us say that Puketon is not on my wish-list... And the "without a trace" would -unfortunately- be a first for stuff under Windows. Sure I could do backup and restore points, but that would be a bit excessive... I had Docker and Python 3.9 on a previous machine installed about a year ago, never got fully rid of it. Though the culprit for the issues could have been Docker,