Leaderboard

I have updated LineageOS 16.0 to include backported security fixes up to ASB patchlevel "5 November 2022". At http://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 grab the ROM dated 20221117. Remember that this is for the original SD835 Pro1 only. The note about lacking upstream code-review from previous months still applies. All I can say is that the build seems to run without issues on my own prawn. Note that, with this release, I have added a compile-time option that disables most of the kernel messages generated by the keyboard driver. I always disliked how e

There's no consistent relation between purchasing/backing date and delivery date; Fxtec told me there would have been some problems on the Chinese side with regard to the shipping order. I already have my October 2020 Indiegogo early bird order, but I still haven't received my September 2019 (!) Pro1 order (later changed to Pro1X)...

Wait, I don't know how to edit post titles lol. Need your help here @EskeRahn😄 EDIT: Managed to change the post title 😛

Assuming this field will now be shown/requested when you first sign in is there perhaps an option for a default that could say "write your device info here" @Casey?

I was so close 😅! My content count was 458. But I think that it is good feature for all. No matter what the content count is. Now we just need to figure out how new members know add details 😅

Don't know why I didn't notice this before. I always liked signatures in forums so that folks could see, whether asking or answering, what devices you had. However, we do have a "member title" field in our profile. So I'm using it to let everyone know I only have a Pro 1 so that people can regard any answers I have about a Pro1X with suspicion. 😄 It's still a good idea to specify what model you are talking about in thread titles and posts as things can get confusing with the two different yet similar phones, especially if people have not listed under their names, but it is still usefu

I installed the utility AccA from F-Droid that @brunoais has already commented on in this thread, it seems to work well. There are settings for limiting charge level, charge rate, high temperature cut off, and low charge level shut down. As already stated, your Pro1(X) needs to be rooted, so this tool may not be for you, I took instructions from here: Note: This procedure works on Pro1X, I'm not sure about Pro1 at the moment. I'll amend if I work it out or somebody with a Pro1 can clarify. I also took the advice of ensuring 'offline charging' was enabled on my Pro1X, (guid

Maybe just pin this thread to the top of the forum? Change the title to: Please Enter Your FxTec Device Information in Member Title slot under "Edit Profile."

Good suggestion, but it's not possible to change the "members title" name to anything else on my side 😕

Haha, nice one!

Now we're talkin' 🙂 !

So, the speaker issue is definitely improving. With the battery fully charged (and /sys/class/power_supply/battery/voltage_now >~ 4100000 µV), the tapping sound reappeared sometimes while changing the volume of a playing youtube video, though not to the extend to make the video unwatchable. Now, with the battery charge at 72% (/sys/class/power_supply/battery/voltage_now ~ 4000000 µV), I'm back to "cannot reproduce" ... I am now quite confident that this problem will quickly go away with ageing of the battery, as others have observed, and I regret opening the Pro1-X for this (

This update looks correct in my opinion. Community is sharing high knowledge, some powerful users/developpers are working in alternative OS, fxtec work hard on debugging issues with components manufacturer...what else ? Delays aren't really a problem according to backing such of niche hardware. Most important is the follow-up here. (one more time : in my opinion 😄)

They have published another update here:

Sent

Could you go to your dial pad and enter *#*#4636#*#*, then take a screenshot of the Phone info? Feel free to send it via DM. I am curious what it says..

I don't know about the firmware fix, but there are two issues here. One is connectivity on different bands--- that is what the firmware fix will address. The other is that Verizon is only allowing white listed phones on their network and the Pro1X isn't one of them. It will connect unofficially with a muled SIM, but it may stop working at any time. That is out of FxTec's hands. There is a whole thread here about Verizon on the Pro 1 and Pro 1x, Some claim to get it working, but rarely come back to periodically verify that it keeps working. I got 3 months with Verizon on the Pro1 before SMS

So I started playing around with my Pro1-X again. After the device being shelved for ~1.5 weeks, the battery is now at 61% and /sys/class/power_supply/battery/voltage_now never exceeds 3870000 µV. In this state, I cannot reproduce the speaker issue! So, maybe, it indeed occurs only on brand-new devices (and batteries) where the voltage exceeds 4.1 V significantly after charge ... ? This might explain why the problem goes away after some time of using the Pro1-X. edit: Re-charging the Pro1-X now, to check whether the problem comes back with battery full.

Finally, this issue has been fixed by restoring backup files. I need pass '--memory=ufs' for each command $ ./edl w persist ./persist_backup.img --memory=ufs $ sleep 3 $ ./edl w modemst2 ./modemst2_backup.img --memory=ufs $ sleep 3 $ ./edl w modemst1 ./modemst1_backup.img --memory=ufs $ sleep 3 $ ./edl w fsc ./fsc_backup.img --memory=ufs $ sleep 3 $ ./edl w fsg ./fsg_backup.img --memory=ufs $ sleep 3 Here is link for my backup files if you need them: https://github.com/steward-fu/pro1x/releases/tag/v1.0 Thanks

Thank you everyone! I'm deeply in love with my phone and want it to last forever 😄

Well I was all wrong.

Yeah I've been down that road with Verizon before - using a working SIM from another phone. This time with the ProX1 it just didn't really work at all...so, hoping the firmware (if and when it ever happens) will let it work.

For the last several weeks I've had serious problems with the display of my Pro¹ X. Right now the display only works when the keyboard is slightly ajar, which makes the phone almost useless. The problems started about a month ago and I think that they were triggered by the interaction between Android Auto and whatever customized software the Pro¹ X has to force landscape mode when the keyboard slides out. Initially, all I noticed is that when the keyboard slides out, the display on Android Auto switches to portrait mode. Later I noticed that after disconnecting from Android Auto, the phon

2.1.5-GMS-less also here. And the problem is definitely there. So whatever fix they prepare, it's not in that ROM.