Leaderboard
Popular Content
Showing content with the highest reputation on 09/02/2024 in Posts
-
I agree with your criticism of the Pro1-X's remaining hardware and delivery process. But in these lines you essentially state that you backed a keyboard phone even though you have absolutely no use for a keyboard phone. Of course you have every right to do this. But then do not lateron blame F(x)tec when they indeed ship you a keyboard phone as ordered ...4 points
-
Looks like something really screwed up your partitions... This is now beyond what I can think at the moment. I'm currently out of ideas.3 points
-
As previously stated, I can only agree. I have 2 x Pro1 and 1 x Pro1-X and all displays have these black moons in at least some of their corners. The good news is that they haven't worsened over time, which is 4+ years for my initial Pro1.3 points
-
No we can't, it is a mat, sorry, but you can change what the keys actually return. I have for five years used a Pro1 qwertZ setup for qwertY (as I disliked the shifted qwerty) using FINQWERTY the nice open source work by @Anssi Hannula, and selected a Danish layout. ADD: See below2 points
-
When was it released? Was it nearby 2020/1? Was it produced by a company with deep pockets? Those two are VERY important to take into account. You need absurdly deep pockets to handle such kind of market offer.2 points
-
Mine has the marks too. This is an issue with the display manufacturer which seem to have a 70+% failure rate at the screen edges. However, they scam buyers by cherry picking the displays for test units, so none of the test units have these visible issues. F(x)tec is scammed and they are incapable and don't have enough money to fight back.2 points
-
I agree. There's no noticeable errors or warnings in the logs. @trahe I found this almost by chance: Does it help you? It shows that restoring some of the partitions worked to unbrick his phone.2 points
-
I don't know if UBInstaller deletes the persistent partition. Look at this guide: Try to do a backup of the partitions and let us know the outcome of it. If you are willing to, show us the full output from the tools used to backup.2 points
-
right something about the partitioning is my guess as well1 point
-
OK sure, and thanks for helping the edl backup procedure i logged, and for further information i as well included the output of fastboot getvar all the product is *bengal* the last flash attempt has had been UBTouch i can as well have Pro1x or QX1050, depending on which ROM to flash (stock rom / Lineage21 i tried to no bootable avail) As a sidenote, i as well tried to do the : Pro1-X: Flash Stock Firmware in fastbootd Mode from the "official" Gdocs, and as well installed the newest platform-tools, but fastboot create-logical-part1 point
-
Soo yesterday i have madded my battery refurbishment . It was simple process - remove kapton tape, cut old battery cell contacts from pcb, littlebit shorten contacts on new cell, solder new cell to pcb with spot welder, isolate, bend pcb to correct place and then new kapton tape. It looks like original and whole process was for 5 mins 🙂 I am now inside testing - charged to full - lineage batt info shows approx 2900mA after full charge. I have now 66% on battery after 10 hours usage (lineage update, yt music for 2 hours in car, 40 mins on browser, some calls e1 point
-
never. we all start somewhere. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I can't provide much better steps than what is already in the OP. I guess start here: backup persist. try adb method first. requires unlocked and a recovery boot if above doesn't work, install EDL (see readme and OP) edl r persist persist_backup.img edl r modemst2 modemst2_backup.img edl r modemst1 modemst1_backup.img edl r fsc fsc_backup.img edl r fsg fsg_backup.img flash your OS of choice:1 point
-
Not using SFOS myself since many years. But others indeed have reported much better results. As you had similarly devastating experience with Droidian, also (kind of) positively tested by others, I wonder if something is wrong with your device. Did it work correctly with stock Android 11?1 point
-
I've been daily driving Sailfishos for about 4 years on the Pro1 then the X. I haven't experienced these issues.1 point
-
No no no claude0001, I'm not gonna read this! :)) BTW the psychologist appointment has been canceled - fxtec promised me to send new screen!1 point
-
Maybe it is. But not because you dislike the screen. Rather because you do like the rest of the phone! Just joking of course ... 😉1 point
-
Sadly a lot of the Pro1s have this defect, mine included, and on mine it's not even nearly symmetrical like on yours. Definitely not acceptable but if I ever RMA'd in the past there is a good chance I wouldn't have seen the phone for years so I just put up with it.1 point
-
You can use app called Round corners and Hide notch to make the curve of the corner bigger (there are other apps too). It is not a perfect fix since it does not work in the settings or the drop down menu. However, it can help little bit. Maybe with root you are able to make better fix? https://play.google.com/store/apps/details?id=round.screen.corner.hide.notch1 point
-
I have several Pro1 and Pro1X, and they all got it to some degree, sorry. It is the same screen from Boe used on the Elephone U, and you can find complaints on that too. So though annoying, it would be really lucky to find one without the issues...1 point
-
In general, I use dark mode on my Pro 1 and Pro 1x, as well as black wallpaper, and I never see the spots on the corners. ;)1 point
-
I wouldn't worry about those. My Pro1's (got two of them) and my Pro1-X have had these black spots in the corners of the screen since day one. They haven't worsened over time (we're talking years for my initial Pro1)1 point
-
So far I have only had it working for about a day. I haven't done much with Sailfish other than some tinkering around in the terminal. It runs smoothly and once you perform some of the tweaks (mentioned in the first post) it feels like it was very much designed for a device like the Pro1-X. I haven't attempted to run waydroid yet but when I do I'll update how successful (or not) that attempt is. The Pro1-X is not going to be my daily driver. I intend to use it as a small personal laptop (browsing, email, media consumption etc.) rather than a phone.1 point
-
Hi all, I am late to the party. I didn’t expect to receive this device and it showed up at my door late last week. I am really struggling to install Sailfish on the qx1050. I followed the instructions in the first post of this thread and I can’t get past the “Powered by Android” boot screen. I tried both the March 2023 (Sailfish 4.5) and October 2022 (Sailfish 4.4) releases. I booted to the bootloader, ran the flash.sh script. Each time it states the script has completed successfully but no joy. Can anyone advise me as to what to do? UPDATE: I figured out what I did wrong. When I fi1 point
-
Several posts on the IGG comments thread suggest QWERTY variants are out now. Remaining orders seem to be asked to choose between QWERTZ and scandinavian keyboard layout ... 😕 Edit: Has hit the discord channel too, now.0 points
-
No unfortunately it did not help. The backups i have are doubtful i guess... But there is one noticeable difference after running the UBports installer: the recovery starts with: Can't load Android System. Your data may be corrupt. If you continue to get this message, you may need to perofrma a factory data reset and erase all user data stored on this device. Try again Factory data reset So if i choose Factory data reset i get --Wiping data... Formatting /data E:format_volume: fs_type "auto" unsupported Data wipe failed0 points
-
Replacement screen hasn't arrived yet, but after a few days of staying off on the shelf the phone has...somehow got its touchscreen functionality back in stock Android 11. Don't know for how long. I'm going to open it up anyways but this is super weird. Screen firmware updating itself maybe? Edit: it did the same thing it did in LineageOS. Worked for a little bit longer this time, about 5 minutes, and now the screen won't respond to touch again. Gotta be a hardware issue right?0 points
-
Lineage-21.0-20240901nightly-pro1-signed.zip on August 5 (2024) security patch, installed smoothly using OTA BUT with these following issues: no camera no flashlight function0 points
-
Lineage-21.0-20240901-nightly-pro1-signed.zip OTA installed. Sill: No Camera No Flashlight https://review.lineageos.org/q/project:LineageOS/android_device_fxtec_pro10 points
-
Every preinstalled App hangs, including the Cam-App and the generall Settings, the classic Phone Calls are not working, if you recive more then 5 SMS the SMS Services crashes. Sometimes you see infos on the Homescreen, so the apps are woking somehow, but not in fullscreen view Only working thing: The Terminal0 points