Leaderboard

I reseated all 3. Thing is though, none of them felt loose or anything. I'm actually kinda surprised it worked.

Just a small update... The ghost touching got to a point where the phone was unusable and I couldn't even enter my pattern at boot without a lot of retries. Also got a bit dangerous yesterday when I was using my phone as GPS and it kept randomly switching out of Waze. @Hook posted some troubleshooting steps done with F(x)tec so I thought I give it a try (specifically checking if any flex cables were loose), and it SEEMED to have helped. I followed gelraen's teardown instructions and took the screen apart. Cables seemed tight, but I went ahead and reseated both the LCD/Camera to main

Yes, I've done it twice already. It's not that hard as it seems. Now if you look at my phone, even very close, you can't say the screen was swaped. Also I've installed small difusor for the notification led so now light is in one solid color.

I recently migrated to LineageOS from stock, where I was a happy FinQWERTY user. After seeing it was broken and finding out in the forums that FinQWERTY is expected not to work, I've been crawling all threads related to keyboard layouts and adjustments and nothing I did worked. (In my case -- I'd like to type Portuguese, so I want combining ` ' ~ ^ and ç; none of the built-in options really seem to be comfortable for typing. There's a few alt combinations that are really hard to reach for a couple of them, but not all...) I tried tweaking a KCM as described in but the changes d

I have been looking for a phone for some time now, but it seems that the phone market is not geared towards people with my preferences. Clearly i am not the only one since the Fx pro1 was created. It has a lot of what i want, including improved privacy and control in the OS, and a keyboard. One of my favorite phones i owned was the Microsoft Kin Two which had a great slide out keyboard. But it still is missing something that i really want, which is a compact phone option. At 154x73.6 with 6" display, the pro1 has a big foot print (by my standards). Id really prefer something with a 5" sc

Announcement: https://www.xda-developers.com/lineageos-18-1/ Upgrade: https://wiki.lineageos.org/devices/pro1/upgrade Get it here: https://download.lineageos.org/pro1

Setting up the ssh server seems a bit tricky in UBports indeed. The official docs -- which your certainly know already -- list several ways of transferring the key. I am no UbuntuTouch user, but basically, one encounters the same problems when setting up the SSH server in LineageOS. There, the easiest way (for me) was to grab the required public keys from the PC to the phone using Lineage's built-in SSH client (as opposed to pushing the files to the phone, which requires a working SSH server in the first place). Not sure if Ubuntu includes an SSH client out-of-the box, but if not, I would

You need the ubports tweak tool to put the file system into read write mode. Then you have to edit the file /usr/lib/python3/dist-packages/libertine/ChrootContainer.py (best done with vi) and add "self.run_in_container('apt remove -y makedev') " to line 86 of the file. Before you do the following make sure all libertine containers are deletded. The way to do the edit is like this: download the ut tweak tool open the app and select system change the file system to read/write this time only open terminal sudo -i Then type vi +86 /usr/lib/python3/dist

Please also post your later foundings about this issue. It has not helped in my case, but it may happen you only had this connection issue. It may also happen it will start the same problem again. That is the connector of the screen itself anyway.

Yeah, that is a pity. I have been talking about this earlier. Currently I cannot write @ symbol with QWERTZ using Finnish layout. It is possible to modify KCM file with root but it is a quite hassle. Anyway I upgraded from official LOS 17.1 to 18.1 without issues (dirty flash). Just downloaded the files to my se card and flashed them vie LOS recovery. No need for PC and ADB access. Recovery will be updated automatically when you flash LOS 18.1. Place the files to sd card Reboot to LOS recovery Click Apply Update, then Apply from sd card and select LOS zip Wait unti

Smart move, remind me to do that too if I ever need to change the display panel 😁

I really hope mine doesn't end up in a full phone RMA, especially not with how Google handles backups where it has to be 45 days active. Also paying for the duties and taxes when importing my current one really sucked.

Make sure you are looking at the display only option for those Elephone screens. The frame won't work on the Pro1 because those are different (The more expensive screens sold by FxTex include the frame with the display already mounted). With the cheap replacement display, you have to remove the old display on the pro1, which is glued, from the frame and then glue (it comes with adhesive strips) the new display into the frame.

Maybe you're right... Displays from ebay look slightly different inside than the original one.

After second screen replacement I'm beginning to think that it is not phone memory need to be flashed but the display's chip itself...

If I understood all the past information correctly, Fxtec is in fact supportive of repairs with those cheap parts. Also, I believe their own screen replacements (the added value of which is the easier replacement as they include the screen casing with all that's inside) needed the changed driver, too, from some point in time onwards, and someone who's using LineageOS, which Fxtec also officially supports, would need the driver package, too, even if they got the screen replacement from Fxtec...

I think it is because the ebay displays are lot cheaper than the one that fxtec are selling so maybe there is a conflict of interest...

From what I've heard in the meantime, there must have been some confidentiality restriction on those files, whatever the reason for that may be. Perhaps EvilDragon has become aware of that, too, and maybe that's why he doesn't react on further requests here, either. If communicating with Fxtec would work as we would like it to work, we could get into a discussion with them about it, but as it doesn't, I wouldn't get my hopes up. Still it wouldn't hurt to try...

I went form unofficial to official and used NikGapps Omni instead of MtG. adb reboot bootloader fastboot flash boot lineage-18.1-20210401-recovery-pro1.img reboot to recovery adb sideload lineage-18.1-20210401-nightly-pro1-signed.zip reboot to recovery adb sideload NikGapps-omni-arm64-11-20210324-signed.zip And if you get stuck in a bootloop, try flashing the OS to slot_b and NG/ MtG again to slot_a. Mind you, I went from official 17.1 to unofficial 18.1 without any problems. So the above should also work for 17.1 to 18.1 official.

This didn't quite work for me. I've had my Pro 1 on the stock firmware up until today, where I installed LineageOS 18.1 20210401. I followed this guide, did the magisk hideprops config, and cleared the google play settings, but afterwards the safetynet would still not pass (even in magisk's own check). I googled a bit, and installed https://github.com/kdrag0n/safetynet-fix (downloaded + installed via magisk), then hid magisk and did the clear data/cache/reboot dance again, and afterwards safetynet passes. I also installed Google Pay and was able to set up NFC and everything seem

A quick rundown of my dirty flash: Had LOS 17.1 with OpenGapps Nano installed. Download LOS_18.1.zip and MindTheGapps_11_arm64 to PC Connect phone to PC Reboot to recovery (the recovery from LOS 17.1 will do - no need to fastboot flash the recovery.img) Install via ADB sideload run from command line: adb sideload lineage-18.1-20210401-nightly-pro1-signed.zip Select Advanced -> Reboot to Recovery run from command line: adb sideload MindTheGapps-11.0.0-arm64-20210220_140101.zip Reboot Have my Pro1 running for 4 hours now without issues.

I emailed them on the 23th and received a reply on the 29th. It was a ridiculous reply btw.

It's hard to tell. I was dealing with this in November and December, which was when they were full-speed on the IGG campaign. Sometimes I got an answer in 48 hours, sometimes two weeks. Their answers were always useful and good, so I just became rather zen about when the answers came. I felt strongly I would be taken care of if I was patient. And I was right. The actual warranty screen replacement was excellent. They did have me go through several stages. They had me video the problem, then they had me open up the screen assembly and check that the cable was properly seated.

Updated the link in my first post due to old one having died. So if someone wants the rough 3d scan and the model for a case I made: https://www.dropbox.com/sh/uee2exvq1k9l0g8/AADEZnXLLar2HUjdHvcaj3O1a?dl=0 ping: @ubuntuscofield

Switch the keyboard to type FULL. Get an adb root shell and run: mkdir -p /data/system/devices/keychars cp /vendor/usr/keychars/Builtin_Keyboard.kcm /data/system/devices/keychars/Vendor_181d_Product_5018.kcm sed -i 's/type ALPHA/type FULL/' /data/system/devices/keychars/Vendor_181d_Product_5018.kcm You can also edit the keymap to your liking. @3zet recently did this.

Hi! I've had this problem before with other phones. Even Netflix themselfe share an .apk . You can find it here. Have fun with it