Jump to content

Leaderboard

Popular Content

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

  1. 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
  2. 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
  3. 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
  4. You clearly forgot to mention the year 🥴
    6 points
  5. True, if you don't count the keyboard... Still, my impression – not just from what I myself do (hardly any of which needs more than a low-end SoC) , but also what I read about SoCs and their real-world performance – is that 3 or 4 years old high-end chips like the SD 835 we have in our Pro1 hardly show any lack of real-world performance even today. And the more current, but also more lowly SD 662 shows similar CPU benchmarks, it's just the GPU that comes with a potentially noticeable drop of performance. Any real world applications which don't heavily rely on GPU performance will work jus
    5 points
  6. 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.
    5 points
  7. I'm sure I'm about to hex myself by posting this but, no case, no screen protector, no broken screen (though it was replaced by FxTec in January for Ghost Touches). In use since December 2019. For me, the true lifesaver is the textured Dbrand matte black skin on the back. Best shatter protection is having enough grain on the back to prevent it from sliding easily either out of your hand or off a surface. That, and not being in a blazing hurry when handling it. 😉 I do have 2 AlieExpress replacements waiting in the closet for the day when you all get to point your fingers and laugh
    4 points
  8. The instructions in the LineageOS wiki are really good. Just follow them and make sure not to miss any steps: https://wiki.lineageos.org/devices/pro1/build It is really not that hard. I have been self-building LOS 16.0 without issues for some time now, although I understand next to nothing about the internals of the build system ... Even if you have some Linux running on your main PC already, I strongly suggest to set up a dedicated VM with the latest Ubuntu LTS to stay as close as possible to the recommended environment. Ubuntu Server is sufficient btw. (and much easier on y
    4 points
  9. @tomthegeek, @SCΛRECROW, I suggest you to find a better (but removable) glue which is able to hold the display without allowing it to move. There is a ribbon cable at the bottom of the display (if I remember well) which is better to remain in fixed position. If that ribbon cable breaks, it may lead to ghost touches, display distortion, etc. Sometimes there is another glue comes with a display (maybe B-7000 for example), it seems to hold it good enough. Do not allow the display to move in the frame.
    4 points
  10. I totally agree that the Pro1/Pro1X is not a device for everyone. For those entering a modest amount of texts, a real keyboard might not outweigh the various issues (size, weight, curved display and many others) but for us that uses a keyboard a lot, there are few alternatives. And in my book comparing those ends as an easy win for the Pro1. BUT that is my personal weighing, other might end up prefering one of the few alternatives, or even decide to let do with a fake (=touch) keyboard, to get a device sold in millions or billions, and thus (most likely) a more smooth experience..
    4 points
  11. Users on other devices reported problems with the touchscreen after this change when using certain apps. Consequently, it has been pulled for now :-( If we can fix the problems with the touchscreen, it will be resubmitted and merged again. This means next week's build will have the old bug. If this will cause you problems, please don't update until the August security patches have been merged. With luck we will have a fix by then :-)
    3 points
  12. From what I've read here, the driver does get updated with a stock reflash plus going through all OTA stock updates, as one of them includes the driver update. It would seem that Fxtec needed to apply the changes themselves because from some point on the displays they received (whether in production or for their repair units) were of the variation that needed them...
    3 points
  13. They actually have a pretty good track record in delivery the stuff sometime. It just takes forever.
    3 points
  14. lineage-18.1-20210726-nightly-pro1-signed.zip on July 5 2021 security patch installed smoothly using OTA ....and the input issue is solved!! AMAZING JOB!! https://gitlab.com/LineageOS/issues/android/-/issues/3321 https://review.lineageos.org/c/LineageOS/android_frameworks_native/+/312770/3#message-38cd89dc8bbd979418ae520841df099f05831d8a Special thanks to @EskeRahn and @Sean McCreary
    3 points
  15. Oh, dear... I had multiple broken screens myself until I modified a case... this worked so good that the screen never broke again, even though I regularly throw it on the ground. I don't have a screen protector. This is the case I use: https://www.amazon.de/gp/product/B07BQQ8JCC/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1 You only need to cut out the credit card storage case that's inside the case (then it has the perfect size for the thickness of the phone) and cut a few holes in the silicone so you can access all ports.
    3 points
  16. 3 points
  17. Have uploaded my latest build (20210718), including the 5th July 2021 AOSP security patches, after flashing it to my own Pro1 without issues.
    3 points
  18. (lineage-18.1-20210719-nightly-pro1-signed.zip on July 5 security patch installed smoothly using adb sideload and Open_Gapps-arm64-11-pico-20210712)
    3 points
  19. Sorry, I did say that with a bit too much certainty. I have no official source for that, but now that they are focused on developing for the 662 SOC and, given that they have not provided any updates for over a year, I find it unlikely that they can spread their limited resources to providing updates for the 835 SOC. Would love to be wrong. As @EskeRahnpointed out, Lineage is currently required to keep the Pro1 up to date and I have happily gone there.
    3 points
  20. Maybe it depends on the city, I am in Boston and the device has been fine. When I spoke to AT&T about it they just said as long as it supports 4G they will not take any action to shut the device down. One little trick i found was switching cellular off and then resetting it from the SIM info and then reenabe cellular. Then my connection worked. Maybe that helps. Also I am AT&T contract post-paid account.
    3 points
  21. I no longer have an active AT&T sim to test, but my sim always worked fine with LTE. I think I had the preferred network set to Global. Also, try checking the Access Point names. I forget which one I used, unfortunately. Unless LTE where you are uses a band not included on the Pro1 (like band 71), I have no idea why you would have a problem with LTE.
    3 points
  22. That contractor has been MIA for more than a year now. lol I don't think we will see official stock android 10 anymore. Although a heads up from Fxtec would be well appreciated at this point because everything points to the base Pro1 being left for dead. (save for Lineage and Linux...)
    3 points
  23. (lineage-18.1-20210712-nightly-pro1-signed.zip on June 5 security patch installed smoothly using adb sideload and MindTheGapps-11.0.0-arm64-20210412_124247) Then redid with the new OpenGapps 11, Including a WIPE of the user data! (lineage-18.1-20210712-nightly-pro1-signed.zip on June 5 security patch installed smoothly using adb sideload and Open_Gapps-arm64-11-pico-20210712)
    3 points
  24. Got aliexpress replacement display and replaced the faulty one successfully. Can confirm, no more ghost touches. Such a relief to get the keyboard back.
    3 points
  25. If it arrived on 1st August it would have had to be sent in July which they never suggested was a possibility. Recent monthly updates have always come shortly after the 10th so we should know this week - hopefully they're still confident.
    3 points
  26. Success here with OTA update, too, which kept Magisk and MindThe Gapps as they were.
    3 points
  27. How can it be out of warranty? All Pro1s are still under 2 years since they were shipped. They could decide the initial drop was at fault and say it isn't a covered by the warranty, but the warranty should still be in effect.
    3 points
  28. I had exactly the same, even was looking at the phone while it turned black. Still trying to repair it, but I will have to send it in I think. BUT I MISS THAT DAMN THING EVERYTIME I PICK UP MY PHONE 😪 So please send the thing in for repair and then sell it to someone who is as desperate as me!
    3 points
  29. fastboot oem off-mode-charge 1 I saved it when you first posted it. 🙂
    3 points
  30. Fine so you still got two option, there is magisk hide with props that i use since i have my pro1 for GPay to work. Otherwise there's the uninstall guide here after you're done with the driver update. In both option you won't loose any data. The third option that isn't really easier and isn't guaranteed to work is to flash back to stock so you'll loose everything and isn't sure if it will work or not.
    2 points
  31. Good news! Indeed thanks to @Sean McCreary again. 👍
    2 points
  32. Hi, i can't help for the office thing but I had the same trouble for the phone app. It looks stupid but there is no default phone app selected so it just don't know what to do with calls. Go in apps settings, select default apps and phone is probably empty and it shouldn't be, which was the case for me.
    2 points
  33. Indeed, a flip case is the least bad available, and I have used similar too for over two years. But it is not to everyone's liking. See this (long) thread for various options.
    2 points
  34. It is partly a hardware issue that should be flawlessly corrected with proper software, as I've described. My repeated key issues started about 9 months ago. Same thing with my Photon Q. I'm surprised the backspace key didn't break off and fall right out of the phone. That's very interesting that it's happening on LineageOS as well. But I'd have to guess that the way keyboard input is processed on LineageOS was just "borrowed" from Android. I'm an old-school microcontroller coder, and I have an example of this happening in early 80's tech. I have an old Radio Shack programmable
    2 points
  35. In Denmark it is one year full warranty, and the second year you have to prove it was the manufacturers fault. (That is why planned obsolescence is not uncommon to kick in shortly after the second year)
    2 points
  36. It is certainly not an easy road for a small company being swindled like they were. I'm amazed they got the stamina to push on, and did not just close their business. And indeed if they are so unlucky as to be flooded with warranty requests it might be very hard for them to fulfil what they legally are obliged to. So a big thumbs up from me for their will to fight, And fingers crossed on the road ahead being more smooth,
    2 points
  37. The July 19th update with the July 2021 security patch installed smoothly via OTA. Root retained.
    2 points
  38. What is the source of the info? Did I miss any official communication on this?
    2 points
  39. See you in 5 months then :D
    2 points
  40. This has been a maddening problem since my Photon Q, and I believe there are 2 issues happening, and although I'm a talented engineer, I'm not in a position to confirm my suspicions in the near future. I believe auvo.salmi is right, in that the keyboard is wearing out a bit over time. This causes noise or "bounces" in the keyboard input. In the best-case scenario of keyboard design and OS integration, there is a dedicated microcontroller reading the mechanical buttons which employs advanced debounce algorithms. In my microcontroller programming experience, I require about 60ms of no keypre
    2 points
  41. I don't know what the confidence of a suicidal orange is worth though 😄
    2 points
  42. lineage-18.1-20210712-nightly-pro1-signed.zip on June 5 2021 security patch installed smoothly using OTA
    2 points
  43. UPDATE July 18: Sold I am selling my Pro1. The broken promise of stock Android 10, plus the little idiosyncrasies with it have finally done it for me. I really wanted to like this device. The hardware is great. But the software and lack of support from F(x)tec is not what I signed up for. Details: Original Pro1, QWERTY, fully functional running stock Android 9 Includes original box, cable, power adapter, gray sleeve, manuals Extras: Brown fitBAG Rave sleeve Nite Ize Clip Case Cargo Phone Holster Things to know: It has the "bl
    2 points
  44. In EU, a minimum warranty of 2 years is mandatory, regardless of what the seller or manufacturer says. See here : https://europa.eu/youreurope/business/dealing-with-customers/consumer-contracts-guarantees/consumer-guarantees/index_en.htm
    2 points
  45. Update to lineage-18.1-20210705-nightly-pro1-signed with the June 5th security patch with Magisk 23.0 and MindTheGapps-11.0.0-arm64-20210412_124247 completed successfully via adb sideload
    2 points
  46. That's a known phenomenon. As far I know, there are several ways to fix it, depending on what operating system you run, and whether you are ready to do a full data wipe or not. It's all in this thread: I suggest to contact Dragonbox ( @EvilDragon ), they'll probably know best what to do ... Edit: Dragonbox.de even have note about this on their product page: https://www.dragonbox.de/en/spare-parts-tools/lcds/fx-tec-pro1-replacement-lcd
    2 points
  47. A late update with my device suffering this issue...I fixed it after tightening a loose screw. I dissembled my phone looking for any loose connectors, specifically the flex cable to the USB sub board, but the screw circled in red was loose with maybe 1mm of movement between the screwhead and PCB. (thanks to @gelraen.ua for the photo, I forgot to take photos haha) The FCC teardown photo below shows some contacts on the underside of this PCB. So my theory - without knowledge of the schematics or circuit diagrams - is that a lack of contact against the metal midframe caused the Hal
    2 points
  48. I'm 100% with you. I remember I uttered that same criticism months ago (though I cannot find the thread anymore): The size of the keyboard feels wrong for me. It is too big for thumb-typing while holding the phone in hand, and too small for 10-finger-typing when putting it on a desk. I, too, could thumb-type much faster on my old N900. For sending the quick text message, I actually rarely use the hardware keyboard. That being said, I also never looked back. The big high-res screen is nice (though not very well suited to watching movies due to the green-tint problem), and there are so
    1 point
×
×
  • Create New...

Important Information

Terms