brunoais

I don't know but the sysfs I currently show there stops energy input. That means the phone starts working powered by the battery, even though it's connected to the cable. What you point out, is the phone just not charging but still taking power to sustain itself (what I'd rather be turning on there). It can have a relation but they are different in that detail I pointed out

Ah ok... It's excused then... I barely have nails and I can open the tray on my PRO¹-X, though... I just tested, a clip also works. I so much prefer no injector tool to use and lose. I disagree... I still prefer the 2SIM/1SIM+SDCard. I just would prefer 2SIM+1SDCard... I see there's space for it but I wonder it would hurt in the structural integrity... Otherwise, the solution for that would be a deeper tray which would take more internal space. However, with 256GB storage... Hopefully, I won't need SD card... Time will tell...

😁 What a piece of work there! I wonder if there's better alternatives... I really dislike hybrid slots... If you put a SIM, seems like a waste. If you put an SD card, then you can't use the SIM card... Always feels like a waste in some way or another... When I want the best of both worlds....

Keeping this post here just in case

Keeping this post here just in case

In this topic, which I'll update every time I find something useful, I will share configurations that are safe and configurations that are risky that you can try yourself on your own PRO¹-X. Everything shown here requires system permissions. The only way for you to get system permissions is by rooting the phone. There's no way around. That's how Android works. Because these are settings using sysfs. By design, they are temporary. Rebooting your phone will reset them to their default values. If you break something and you don't know how or what, one way that usually solves it is shutt

Pff.... Misread 😖

Where did you get the PRO¹-X-compatible LineageOS build (even if not complete and still buggy)?

50<X<200. 😉

Mine is above 7000... 😉 What made you believe that? 😢

To make it clear, the drivers and whatnot of PRO¹-x are still not in mainline linux. That will happen, at the very least (if lucky!), next year. Whatever OS uses mainline linux and its drivers to run won't work until then.

Just noticed. The file on google changed too. It used to be a .gz file and now it's a tar.gz with multiple files. Now I can find the boot.img and others I was looking for.

I've sent an e-mail to f(x)tec about this. Please don't send one too. I'll share the answer with you. I just had this chat on #lineageos IRC (LiberaChat) and I got this interaction Weren't we going to get LineageOS development for the PRO¹? What is going on? The LineageOS management doesn't even know about it. They are claiming it as unsupported! @Waxberry/@Casey , what's going on? Is there development happening outside the LineageOS team but the results not sent to LineageOS team yet? Extra: Doing some research things are not adding up... Can it be I wasn't

LOS guys don't give ETAs and, worse even, they don't give status information. I tried asking for a status update on Discord but I got shot down. Not even a list of what works and what doesn't work...

Try using ddrescue to copy them. See if it works that way.

There's a driver because there's a need to manage the digital-to-analog converter and then manage the amplifier for the speakers. There's a chance they are using a driver that was designed for mono and they are using for stereo and it's failing at some points. If it's software, they can fix with OTA! Edit: Appears like it's a hardware issue. See:

@KingOfTerrible, Mine is nothing like that. It moves with a firm *click* when I press and completely flat when depressed. Same for the volume buttons. All of those have a high pich "TIK" "TUK" sound. The camera button is similar but muffled sound.

How to install Magisk on PRO¹-X? Is it similar to this manual ? Where to find the img files for recovery and such? Are they in the google drive mentioned here?

Would it pass Google's attestation? I don't think it would...

I ran that edl command: edl r persist persist_backup.img but I got 8GB of data in multiple files, inside a directory called "memory". Anything I might have done wrong?

There were interviews. I also remember finding a court case online with f(x)tec as the plaintiff with some company as the defender. I tried to find it again since you asked but the link I had no longer works and I wasn't smart enough to keep the Chinese pdf document. I can only tell that there was (dunno if it wasn't erased) a court procedure and... That's it for outside f(x)tec control.

Interesting... Even without seeing the videos I just do it easily... I do either the lift behind then push open or push slightly down and slide to get it open. (I'm still eager to get a propr OS in this thing and start playing with it!!!)

That's weird... Mine has! It turns on when I try to charge it.

Only suppliers. XDA didn't do anything wrong here.

It's actually XDA that paid the developers. Hence the headline of "XDA made a phone". The deal was XDA would do marketing and paying developers for LOS and ubuntu touch and f(x)tec would take care of the phone. They were screwed in the process. I don't know how much money there is with this but I'm glad I got the thing! Even if I will end up using a generic LOS build instead of one specific for the hardware