Leaderboard

I was experiencing the 100% battery issue, but never had any sudden power-offs, and I'm using the phone nearly all day at this point. The full-for-too-long issue seems to have vanished since I've flashed the current beta ROM, but I am not certain it would address your primary fault.

Unfortunately, I have no second specimen of this (quite expensive) type. Now, I could insert my Pro1 card into the laptop and test. However, considering that I routinely hurt at least two of my fingernails when extracting the Pro1's <censored> SD/SIM holder, and subsequently always wonder whether I haven't broken the puny little thing for good now, I prefer not to, sorry. 🙂

To add some information: I have a original Pro1 (no X) with LineageOS 18.1 (didn't have time to update to 19 yet) and I have been using Nova Launcher on it for a long time now. A few days ago I experienced the issue you're describing for the first time. I suspect it could be related to the fact, that I recently I updated a bunch of apps via Playstore, including some Google Apps, that work quite deep in the system, e.g. Device Health Services, Google and Digital Wellbeing.

I additionally tried with "launch" from F-Droid and Niagara Launcher from Play Store - and get asked every reboot.

Myself and many others who ordered back in 2019/2020 are put on hold again, it seems like getting the phone I ordered 2,5 years ago has less priority than those who backed on indigogo just 2 or 3 months ago I have received my Oct 2020 IGG contribution # 3xx, but not yet my website order from Sept 2019 (Pro1 later changed to Pro1 X). I was told the latter is definitely in the pipeline, but things were mixed up quite a bit in China with regard to the sequence of shipments. (Personally, I couldn't care less which of the two came first 😉, but I understand that it's different for th

Sorry, but just use a non-Quick-Charge-enabled power supply. No other action requied.

Deep-discharging being a good thing is a popular myth from Ni-Cd-battery times. Li-ion batteries do not like that. @EskeRahn is right in that temperature is a decisive factor. Using QuickCharge (tm) results in my Pro1(not X) becoming so hot it is uncomfortable to touch. I hence avoid quick-charge by using only my PC USB-ports for charging.

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)

@bryan could your random shutoffs be related to this? Not actually a dead battery, but a problem returning from sleep? Doze? I don't quite understand it but it's something to try.

Interesting. I still have a Pro1 with LOS 18.1 running Nova, too, and I'll keep an eye on it whether it starts to misbehave as well...

Also, I can pretty consistently get it to happen after using the camera button while the phone is locked.

I've never been able to find a source that spells it out, but I believe that once a company has had their Android GMS certified, there are road blocks to their providing a non-certfied version without Gapps. But, it's a guess, not fact.

@EskeRahn I've ususally use this: https://github.com/0x192/universal-android-debloater but that's not what I want. @Hook Whaaaat? I don' know anything about that. Please some info is welcome!

I'm not getting it as often as some, but I'm being prompted once every two days or so, using Lawnchair v2. I'm also using gestured-based navigation, if it matters.

If I'm not mistaken, I don't think they can and still release properly certified Android.

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.

I dunno... I'm pretty darn frustrated....🙃

Camera works for still images, calls work, WiFi works (but see potential issue in the FP), texts work, MMS work, F-Droid works in Waydroid but I couldn't add custom repositories because F-Droid would crash, I have not tried Google Play apps. Copy/paste works fine in Sailfish, what's difficult is to transfer the clipboard from native apps to Alien Dalvik or Waydroid ones, or to LXC of course. I remember that copy/pasting from emails was not trivial (we had to go into edit mode to copy text), I don't know if that's still the case because I read my emails in my LXC container now.

I've made this error every single time I re-flash the phone. Normally I realize it just as soon as I'm happy with my config. Wiping userdata will fix it and you can start all over.

@Ivaylo HubanovYou should be able to set the device into EDL mode anytime by: - Hold both volume buttons when device turns on. (There was a suspicion that the pwr-key is needed too, but it works with only both vol rocker buttons held.) - Release them right when the droid logo flashes up for a split second. - If the screens stays black, thats EDL mode. You can confirm this with `lsusb` showing up a qualcomm gobi modem. Thats the Pro¹-X in EDL mode. - When it boots, goes to fastboot or recovery, just try again by holding the pwr-btn for 10 seconds to force reboot. Troubleshooting: -

Screen protectors reduce the likelihood of a shattered display whether or not they are tempered glass, and not by absorbing the impact of a drop. Scratching your screen is scoring the glass, making it significantly more fragile.

Google pay working here with magisk v24.3 for some time already and works on LOS 19.1 too. -Zygisk mode on -Enforce denylist -Put com.google.android.gms and com.google.android.gms.unstable to denylist under google play services. You might need to check show system apps from the denylist donfiguration settings -You manually need to download and install MagiskHidePropsConfig and do the edit device fingerprint, probably no need to do this if you upgrade from v23 and have already done this. -make sure play store says device certified, if not try clearing play store and pla

I finally got my Pro1x and was loving it, even though the wifi and cellular signal is struggling. I was totally on board to push through the issues, but then the phone unexpectedly turned into a paperweight. I put it on the supplied charger and it started a cycle of booting to the splash screen, dying, booting to the splash screen, dying... There was no way to interrupt the cycle because the phone powers on as soon as it's plugged in. I left it for a while, it charged, and was usable again. I'm assuming the software isn't accurately reading the actual battery percentage because i

Hello, I'm having problems with calls too. The phone app doesn't work properly and when it works the microphone works occasionally. Does anyone else have the same problem?

Good morning, the solution for me is: sending the new Pro1-X to the U.K. for exchange/repair/what ever. 😭 After nearly two years of waiting: quite disappointing.

Spoken too soon! Had to choose my launcher again right now ...

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.

Myself and many others who ordered back in 2019/2020 are put on hold again, it seems like getting the phone I ordered 2,5 years ago has less priority than those who backed on indigogo just 2 or 3 months ago.