Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 07/05/2021 in all areas

  1. Production does indeed seem to be starting...
    13 points
  2. A few months back me phone just went pitch black in my hand. Nothing triggered any reaction. No button and also no charger. So I contacted support for help. It took a while until they answered me. But they offered me help to repair it myself. Not really keen to try any parcel service during brexit with a phone still holding a decent amount of personal data, I gladly took that offer. They hinted me at the battery and the USB-Board. My skills in electronics and manual labor are... well let's say I am a programmer 😉 But the phone is really really easy to disassemble, I was able to do it w
    11 points
  3. This is now official. Builds are weekly, currently scheduled for Wednesdays. Install instructions are exactly as LineageOS 18.1. Download site: https://dwnld.aicp-rom.com/ Enjoy!
    10 points
  4. Hello, In case of someone would be interested, I try archlinux container in termux with Xfce and it works perfectly for the pro1 with Xserver-XSDL apk. It also works with VNC but without sound. I can now listen music, use Libreoffice and firefox and play with my programming tools. Pro1's keyboard works prefectly (qwerty version here) Very nice discovering a new linux distro. It's not so hard and the documentation is very complete. Source installing archlinux : https://github.com/SDRausty/termux-archlinux When you have done this, $ startarch (in Termux) and you wil
    10 points
  5. Just wanted to provide links to source files that makes our Pro¹ keyboard. That can be used as reference for anyone wanting to understand and customise Pro¹ keyboard experience by building Lineage OS. From low to high level files we have identified the followings key components: Device Tree Structure Include, contains GPIO pin mapping to scan codes: https://github.com/LineageOS/android_kernel_fxtec_msm8998/blob/lineage-18.1/arch/arm/boot/dts/qcom/msm8998-qrd-skuk-t5.dtsi Permalink Driver, brings together GPIO and aw9523b controller input to define the scan codes sent to user space: h
    10 points
  6. Ok, now I do: They're M1.4x2 and any shop that sells small screws should carry them. Also, they're easy to find in black, too, looking good enough for me to not bother with the black stickers anymore. (The black ones I just bought have a slightly thicker head than the original silver screws, but it's still flat enough for the black stickers to perfectly fit on top of them.)
    10 points
  7. This just came in for those who ordered on the web:
    8 points
  8. Next week should be the start of production according to the newest IGG update 🙂
    8 points
  9. They have released another update here.
    8 points
  10. @SlionSadly all too true in general... However... 😃 !!! I FIXED IT !!! 😃 Disassembly was easy with guide referenced above on github. Actually impressed by how repairable this phone is. Removed battery (cell), did the "prick a hole in the cell to release the gas" trick (don't try this at home - see below). Put it back together and my phone is working just fine after 4 hours' careful work. Will be ordering a new battery from Indiegogo. Obviously, the battery is degraded but phone is working 100%. Yay! * * * The full story... Root cause analysis: I now think it
    8 points
  11. For those of you who are self-building, I thought I should provide some info about where to find the monthly ASB patches. Google is currently backporting security patches to all releases since Oreo (Android 8.1), and there is a simple way to cherry-pick these patches from the AOSP source tree. You'll need to have synced the full tree first, following the instructions at https://source.android.com/setup/build/downloading tl;dr repo init -u https://android.googlesource.com/platform/manifest -b master repo sync Once you have the full tree, you can easily display the patches inclu
    8 points
  12. I've put together a guide from knowledge I gathered over the last couple of weeks as I eventually got around trying Lineage OS on my F(x)tec Pro¹: https://slions.net/threads/lineage-os-for-f-x-tec-pro1.90/ It takes you through the installation process from Windows setup to Magisk root and SafetyNet validation to working around prominent issues. It will also take you through the build process from Windows environment setup to development and code contribution. Also taking this opportunity to mention how awesome it is to be able to update, use and customize almost every aspect o
    8 points
  13. It took a while, actually a long while. Seems like the first package got lost, but the second arrived in a week (+1 week customs). I was able to replace the camera and the backplate today in 1-2 hours. It was pain and not fun at all as I'm not used to so small connectors 😄. If you are careful it is possible though. I broke my power button a bit, which is not so clicky anymore and feels so wrong 😄 It was successful though, the camera works again. So it wasn't a software issue. The back is also as new now. And I could learn something new today.
    8 points
  14. Eastern Canada. I've gotten the initial response back from f(x)tec support and they've confirmed that I am still covered, so now just going over some basic troubleshooting with them. Here's hoping!
    8 points
  15. So @tdm Just curious, not trying to bug you. Is this project dead? Any possibility of AICP picking it up officially so it can get regular updates? I obviously would like it to be resurrected, but "no" or "hell, no" are fine. I just would like to know. 🙂 Whatever the answer is, thanks for all you did!
    8 points
  16. It seems that LineageOS 19.1 will be available soon for Pro1: https://www.lineageoslog.com/19.1/pro1 More information: https://lineageos.org/Changelog-26/ (F(x)tec Pro1 mentioned) https://download.lineageos.org/pro1 I hope it'll fix the charging issue I've had with the LOS 18.1 🙂
    7 points
  17. There are so little instructions on the ih8sn in the internet so i thought i could share how to get it to work on pro1 if anyone is interested in that. Fresh install is not needed and you don't need magisk or any SU package to pass safetynet after this. Not sure if this works for other OSes than Lineage but someone can have a shot and tell if it does. Requirements: -ADB on your computer -Debugging and rooted debugging enabled on your phone from developer options. -Latest ih8sn aarch64 release downloadable here, extract the zip, you don't need the .conf file as it is for different phon
    7 points
  18. I think the other thing to look at is their perseverance. Given IGG offers no guarantee of delivery, most, given the obstacles they hit, might have thrown up their hands and walked away. This small group of folks is making sure we get our phones come Hell or high water. I can't believe they are going to have ended up with massive profits. They are doing this for the love of keyboard phones and they will deliver. Thank you Chen and the rest!
    7 points
  19. They have posted another update here:
    7 points
  20. You could be interested on this and to follow it: https://talk.maemo.org/showthread.php?p=1573761#post1573761
    7 points
  21. New manufacturing status info directly from Chen
    7 points
  22. November 2020 backer of the Pro1-X and first-time poster here. F(x)Tec's February update on IGG says they are due to start manufacturing when Shiyan, in the Bao'an district of Shenzhen, "come[s] out of covid lockdown next week." I found this post on Baidu (in Chinese) stating that many restrictions in Shiyan were being lifted on 20 February, now two days ago. I think the speculation that the February update was written in relation to last week is correct. It's also possible that F(x)Tec really was expecting restrictions to be lifted next week, and it turned out they were lifted early
    7 points
  23. To all who still struggle with this issue. People in the fxtec unofficial discord have discovered that flashing ONLY the vendor.img from the stock restore thread will fix the aliex screen issues and won't bork your LOS18.1 installation. For stock and earlier versions of LOS the apk still does the fix. We only have one person done it for now so not 100% guarantee though. Edit: According to feedback from other users this method didn't work. Stock restore thread
    7 points
  24. Personally I hope for e-ink keys like they had on the "Alias 2" a.k.a. "SCH-U750" Samsung made for Verizon. An ingenious solution, fitting 'any' language or gaming...
    7 points
  25. After a very long delay, this feature has finally been merged in LineageOS 18.1. Beginning with tomorrow's build there will be a new option in Settings to make 'fn_r' (the right-hand diagonal yellow arrow key) send ralt/AltGr. This will enable full Windows-style task switching behavior, as well as assist entering accented characters when typing languages other than English. Enabling this feature will disable the use of this key to enter the yellow glyphs printed on each key, but all of them can be generated by chording with 'shift' instead, with the exception of '/' and '?'. Since these two ke
    7 points
  26. During lockdown, we've had repairs go directly to staff addresses, since we all tried to work from home as much as possible. I have hidden the staff address in the first message. I'd advise looking at your tracking, or provide it to us in the original repair request.
    7 points
  27. Sure, its their choice. And I fully understand that Lineage is not in the position to lead Android development and force Google to adapt. Still, I feel like this is the end of the road for me. (Edit: And I am very thankful for the work everyone has done with LineageOS! Lineage is clearly the better Android, and they rescued countless devices from an early obsolescence.) (Warning: Old-man-rant approaching!) Google's choice to develop Android the way they did made sense, back in the olden days. But they quickly gained marked shares, followed by absolute power. Despite that, they contin
    7 points
  28. I'm amazed by their perseverance too. The small group take a lot of beating from angry users, and way too little praise, IMHO I really hope they will continue to both produce PKB phones and support them. If there will not be a successor I hope they will consider crowdfunding extended phone-support as long as possible for the chipset and security update. . I have no idea what a year of support / minor development would cost, but they could come up with a number and see if we are enough that are willing to chip in. As a stretch goal they could offer those that chipped in some special rate
    6 points
  29. I have ordered one - better to have more than having none of a keyboard phone. 😄
    6 points
  30. Sorry, but this is not true. You quoted a post of @VaZso, and then responded with the opening sentence "Don't you think ...". I am ready to believe you did not mean to address your rant at @VaZso, and that the impression of you doing so just resulted from a careless writing style of yours. However, this interpretation is all but "obvious" and, even if true, would still call for an apology. In other news, all-caps are usually considered equivalent to shouting, for which there is also no need here. Even if we all frustrated about manufacturing delays and F(x)tec's communication skills
    6 points
  31. @Dean you accidentially posted in a forum aiming at constructive discussions. The place you are looking for is the IGG comments section. Your useless ranting will blend in nicely over there.
    6 points
  32. Beloved community, here it is: Another up-to-date outdated ROM to satisfy your custom ROM fetish. LineageOS 17.1 JeBB "A noble spirit embiggens the smallest man!" is (so far) a slightly modified build that will be updated in irregular intervals. Future builds may contain additional fixes, or I may attempt to fix things with a Magisk module ... "may" is the important word here 😉 This build can be installed from scratch like any LineageOS build (LineageOS Wiki). Dirty-flashing from the last official LineageOS 17.1 is possible, but the official signature keys have to be exch
    6 points
  33. I uploaded my latest Lineage 16.0 build, dated 20220225. It includes the February 2022 fixes from the 2022-02-05 Android Security Bulletin. These fixes are now backported to Lineage 16.0 by the good people at lineageos.org, as AOSP does not officially support Pie anymore. I bumped the Android security string to reflect this. New local mods since the last release: Backported some CPU and GPU (surfaceflinger) optimizations that, while initially proposed against 16.0, were merged only in 17.1. My full local patchset with respect to the upstream lineage-16.0-branch can be downloa
    6 points
  34. For the sake of fairness and good order, I received an email confirming my refund yesterday and the money has just arrived in my account. I wanted to look at getting Gentoo up and running on the 1-X but that will go on hold until something else comes along.
    6 points
  35. Didn't find this topic which I think is a nice feature on maemo forum. So hello to everyone and happy new year 2022! I am hoping to be a new Pro1X user on february. Hoped I would have got it as a birthday present to myself on last march but didn't happen. I have been hassling with Nokia N900 devices for some years and managed to save 70 pieces of them from three crackheads who were thinking of using them as burner phones! They weren't in good condition (I mean the devices) but I am putting them together to contribute them to Maemo Leste developers. Have been sending working one
    6 points
  36. Considering how people here and on IGG analyse (and maybe over-interpret?) these monthly reports, I think they spend quite some time writing those up. I can imagine they plan very carefully what to publish and how to present it in a way such as to cause least damage to the project. It is easy for us to ask for more honest reports and estimates, but unfortunately it is also a fact that many customers need the harsh reality to be "embellished" for them, or else they jump ship. Some people understand that by supporting Fxtec, they support an interesting enthusiast project: a concept of a sma
    6 points
  37. I finally made a new image (20220129-UNOFFICIAL) with the January 2022 security patch level. Full list of local mods with respect to upstream Lineage-16.0 tree (practically unchanged since December): Modified gps.conf which (for me) enables the Pro1 to get its initial fix much faster. Corrected QoS powerhint signals. Backport from Lineage 18.1. Keyboard driver: Enable high keycodes Backport from Lineage 18.1. Keyboard driver: Fn-Tab acts as Alt-Tab. Cherry-picked from an experimental patch proposed by @Slion against LOS 18.1. Was never merged into any official dist
    6 points
  38. I was on stock and hopeful for the longest time but gave up on it as the chipset "upgrade" of the X clearly meant the original would not get any official support. Moved to Lineage 3 months ago and never looked back. Yes it takes time and effort to set it up but it is well worth it.
    6 points
  39. F(x) Tec has now posted a repair guide with links to the above videos (though hard to notice... the active links are in the section titles, not the graphics). There is a note about further information on the FAQ page which isn't there, so I hope that is something being worked on. https://store.fxtec.com/fix-your-broken-smartphone-screen/ EDIT: I just now noticed the date on this repair blog page-- March 4th 2021. I certainly had no idea it was there (so, as the thread title says new to me 😉). I only discovered it when one of the regulars over on Discord found it.
    6 points
  40. Done with stitching. I love the leather quality, really soft, one of the best I've seen. I need to finish the cutouts on the bumper case and glue it to the leather. Will hopefully get around it tomorrow. The case is 75g that's 25g lighter than the one I've been using so far. Moreover I reckon its lower profile will be more confortable to use, notably when the keyboard is open. The closing latch is on the front panel which is a rarely seen design. As a result when closed it won't lay flat on it's back which should make the phone easier to pick up, not that this was ever a problem considering th
    6 points
  41. Currently working on a new low profile bookcase, I reckon I still have like 12 hours of stitching to go through. I had to remove the stitches to be able to incorporate the smartcase magnet, move the closure magnet to accommodate for the Pro1 thickness and customize the back panel to enable kickstand feature.
    6 points
  42. Maybe you can try this... I just uploaded it and will merge to 18.1 in a few days after I clean it up a bit. https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_msm8998/+/316402
    6 points
  43. 6 points
  44. They stepped up their game again. Since a few weeks support is answering and sending out parts again. I got a new USB-Board a few days ago, which has brought me one step closer to revive my precious pro1.
    6 points
  45. Here is a guide I made for myself, edited from @tdm's original instructions. It is a little simpler because it assumes you have USB working and all the fastboot/adb stuff installed, and that you know where to get everything. It focuses more on just the actual flashing, showing both first time and updates. Since I made these instructions for me, they don't include what to do with Magisk other than flashing the zip, since that is all that is needed for SU. It may be useful for some in combination with @Slion's wonderfully detailed instructions of all the steps with all those many helpful lin
    6 points
  46. Short answer: Why not? 🙂 Long answer: I have set up a quite complex system with LOS 16 and a GNU/Linux (Devuan) running in a chroot, with multiple partitions, automatically starting servers, and shared data folders. To realise that, I use all kinds of tricks to work around Android restrictions. I fear that at least some of these hacks would not work on more recent releases because of changes in the Android security mechanisms. So I would probably have to learn new ways, which is bad because I'm lazy ... 🙂 LOS 16 has a nicely-integrated and low-profile root-management solution
    6 points
  47. 4.1.0.24 should now be available and working. As previously ... 3.4 -> 4.0 -> 4.1 should work fine as far as I know. I havnt done a clean flash of 4.1 (infact, a full image isnt available just yet, so i dont know if that is working)
    6 points
  48. yes yes it is, cpu wise. But the keyboard is timeless. The Question is only, what is the keyboard worth for you? I am currently an owner of a fried prawn, using my old phone (nokia 6.1). I do not miss the faster cpu, I miss the keyboard... every f**king time.
    6 points
  49. You clearly forgot to mention the year 🥴
    6 points
×
×
  • Create New...

Important Information

Terms