brunoais

In my case, I never parted from my dumb phone, however, I use my Pro¹-X every day. It's my ultra-portable laptop in which I do all sorts of stuff. I believe I open that keyboard a few dozens of times per day on weekdays and a few on weekends. Given claude001's answer, I think I'm lucky that the keyboard still works perfectly. When I reach 1 year, I will certainly write my 1 year review of my experience with my Pro¹-X. My dumb phone is mostly used for calls and SMS. Pro¹-X's call sound quality is fine but for me, my dumb phone is more reliable to not run out of battery when I most wan

I don't use signal and don't want to install it but it works with all other apps I tried.

For rooted devices, ACC appears to be the most noteworthy and best working means. Either as command line or as an app. For unrooted devices: Pester f(x)tec to pester the developer company to add a system app that can do that work.

Tried to reproduce and I still cannot. Battery at 80% (4.108V), both when charging and not charging. Volume ranging from 10% to 60% (in intervals of 10) and for min 1 min in each. I'm using OS V. 2.1.5 non-GMS.

I use my Pro1-x mostly as a PDA. I want to use it as my primary phone but it's still early for my purposes. I'm still not comfortable with calling being an app instead of being the "front and center" of what it is (when it's something I call a phone). For me, it's almost an ultra-portable laptop that happens to run Android which is slower to type and slower to be productive while I can still be productive. For my phone stuff (basically phone and SMS), I still prefer my Nokia Asha. A big difference is that I used to read PDF and e-books on my Nokia Asha but now I do those on my P

@Name_not_avail Were you in the wrong fastbootd screen?

When you're not a millionaire, with limited resources, natively (or close to natively) knowing Chinese, with low bargining choices and (speculation:) the other party not budging on the terms of the contract... You take it and have something or you don't take it and you don't get the idea turned true. Even though IdeaLTE licensed the code for limited parties to see and use for purposes of alternative Android OS (speculation: May have been what F(x)tec guys were able to bargain for) pretty much all the hardware and firmware (of the hardware itself, not the OS) was locked behind closed sourc

Cannot reproduce. I can't answer that well

That one is IdeaLTE too. The contract is that IdeaLTE supplies the chips, IdeaLTE designs the board (within the size constraints) and IdeaLTE makes the drivers and the Android build but in a way it can be shared with partners so other Android-based OS could be made. With IdeaLTE gone, so is EVERYTHING (that is not "self-components") that made the Pro¹-Pro¹. Something sort of similar happens now but this time (this is my speculation based on facts) F(x)tec seem to have done some extra work to make sure they wouldn't end up with nothing if the current contract breaks the same way as it happ

IdeaLTE just ditched them. They took the money and didn't fulfill the contract. What F(x)tec promised was what IdeaLTE was legally contracted to do for F(x)tec. It also included the batch of SD825 SoC for the Pro¹ igg batches. When there's something in court, that's standard practice. F(x)tec is in court with them. Given so, we only get some informal information here and there. Whatever F(x)tec mentions publicly or officially can be used against them.

The catch here is that f(x)tec is NOT the software OEM of the Pro¹. The OEM is a Chinese company which ditched f(x)tec and they are the legal owners of the whole source code of Pro¹ with SD825 SoC. (Such code that had to be rewritten after they were ditched because they didn't have the rights to repurpose it)

Unfortunately, the LineageOS developers hate to give status updates. So we only get glimpses when they appear...

Unfortunately I can't help with that... Mine is very clear at all volume ranges, even when USB-C is connected at just 30% volume. No clicking.

https://www.expansys.com.au/fxtec-pro1-x-4g-dual-sim-8gb-256gb-blue-qwerty-us-keyboard-382117/ WTF? Is this with authorization?

No I'll send to you in a PM because I don't want this to grow out of proportion badly. Many things don't work or are missing (more missing than not working) in that build and I don't want to be pointed at. There's a non-GMS v2.1.5 (beta) build I'm using which is running rather well and no noticeable new issues from my end. You want?

Get off the drink. It's ruining your brain. An english dictionary would be helpful to you too. Read both "subjectivity" and "objectivity". Maybe that can guide you to enlightenment. If not enough, then... You are beyond help and none of us can help you.

There's finally a build of LOS that works and I got myself a test build with it. It's still too early and barely works enough for the hardware but it's a great light at the end of the tunnel for LineageOS on Pro¹-X

True. However, I have good news. On telegram's beta chat, I got myself an LOS build that boots. So I guess there's finally a bootable LOS build. It's still too barebones lots of stuff work but there's no services for the goodies and the useful such as turning keyboard backlight on automatically.

Did you try using logcat? I usually use logcat with the command less so I can more easily scroll through it

From the kernel/driver side, that switch is actually controlled manually and not automatically. It's supposed to be controlled by a userland program which sets that value. I was going to jump to that one after constant_charge_current_max but you mentioned you didn't want o continue, so I stopped. the `uevent` file is just providing all data from other files with some extras. In this case, the culprit is: /sys/class/power_supply/battery/charge_control_limit In my phone, there's 7 settings for it (between 0 and 6). Basically, it's a choice of how fast to charge. I think my de

Wow... They keep being attacked and attacked and things keep not working out for them! Wow... I really really commend their perseverance!

These numbers are reset if you reboot the phone, though. However, it appears like the issue isn't there. Given so, it might be in the drivers or it can be something I'm missing...

In that case, try using a negative number instead: echo "-40000" > /sys/class/power_supply/battery/constant_charge_current_max (FYI: Pro¹-X uses positive numbers here)

Oh! This is wrong! What happens if you (as root): chmod 644 /sys/class/power_supply/battery/constant_charge_current_max echo 22000 > /sys/class/power_supply/battery/constant_charge_current_max But that may not be enough... If the % doesn't change in about 20 mins, try: chmod 644 /sys/class/power_supply/battery/constant_charge_current_max echo 40000 > /sys/class/power_supply/battery/constant_charge_current_max That should be enough for the phone to start charging significantly. Do execute this from time to time to confirm if it's being overridden by something el

That one didn't show me... Let's try everything, then: adb shell "grep '.*' /sys/class/power_supply/battery/*" This can be a change in the capacity. While on it, this can help too understanding if there's changes in "file" permissions there. adb shell "ls -la /sys/class/power_supply/battery/*"