Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 09/03/2024 in all areas

  1. Soo yess...my phone have stuck on 10% (battery saver) for more than one hour with youtube playing. Final time on battery was approx 34 hours and 6 hours on display. After second charging my phone charges up to 3138mAh but after few seconds after disconnect chager it shows again 2900mAh. It looks like i can be happy with new cell. Question is for how long. BTW cell looks exactly same as original with contacts on exactly same place.
    6 points
  2. I once tried to swap-in the screen assembly of a Pro1-X into a Pro1. They fit mechanically and connector-wise. The result was that the Pro1 was able to boot into a (working) Lineage recovery, but not into the full OS. I thus assumed the selfie camera was different. Of course, the top half of the Pro1(X) includes more than the (touch)screen and camera. There is the indicator LED, the ambient-light photodiode, a speaker and (I guess) a mic for handheld audio. But somehow I had assumed those were analogue devices that could not cause a crash upon boot.
    5 points
  3. HMD Global (used to be known of Nokia Android phones) is now trying similar thing what Motorola did with Moto Mods. https://www.hmd.com/en_int/hmd-fusion https://nokiamob.net/2024/09/05/ifa-2024-introducing-the-modular-hmd-fusion/ Maybe we see keyboard mod as well?
    4 points
  4. I edited my previous post with updated information. Pro1 and Pro1-X are more different than I first thought so you cannot swap parts that easily. I added also the source for the information. Here are few Indiegogo updates: #14 Both the fingerprint sensor and the camera will be redesigned once the samples have been fully tested in the factory. #15 The Fingerprint sensor now has a new module. We’re expecting the performance to be more accurate than the Pro1 and keep you updated once we have a working prototype. #20 Our engineering team in China has had to sta
    4 points
  5. Yeah, the screen with frame does not include front camera module and the board for the connector. So those parts would need to swap anyway from the old screen. But the frame and the panel itself is the same so it makes the change much easier.
    3 points
  6. so with a lot of help and custom made images from TheKit, now i got it running. Basically the persist of mine was corrupt. Some other device persist.img flashed and it worked!
    3 points
  7. A bit of a tangent, but in what universe is August 26th 2 weeks before September 3rd? :D
    3 points
  8. @Aeong – to be fair, the screen is not "defective", it's a minor cosmetic blemish, and all of us had to put up with it who needed to source a replacement screen outside of Fxtec, which was often the case. On the parts market, perfect replacement screens haven't been available at all now for a long time, and it seems that at this point not even Fxtec is capable to source any. Your complaints on some of the other issues you mention are, of course, perfectly valid. When I was still using my Pro1X which also had basic connectivity issues, practically inhibiting calls and text messages a
    3 points
  9. Can't find it back either. But I just checked: If you *carefully* lift the edge of a cap with a pair of tweezers, you can see the transparent mat below. So the keycaps indeed seem to be individual parts. Not something that was meant to be user-customizable, but it does seem possible ...
    3 points
  10. Another thread here made me thinking that what are the chances if Pro1-X mainboard could work on Pro1 (and vice versa). Of course, the phone would change to Pro1 -> Pro1-X (or other way around) since the main board determites software etc. https://community.fxtec.com/topic/4137-shopping-for-a-working-pro1-not-x-mainboard/ The board is definitely different (not the same SoC etc.) but the size could be identical. We know that battery has different connector and camera is different so you probably need to swap those also. But if other connectors are the same could it be just "plug an
    3 points
  11. @claude0001 thanks. I eventually ended up compiling from source then manually flashing via fastboot. Finally in Ubuntu! The documentation / process needs updating. Newer builds. Better device detection. This is not user a friendly process for those unfamilar with the command line.
    2 points
  12. On discord they helped some guy install UBtouch manually after the installer didn't work for him either, basically following this how-to: https://gitlab.com/ubports/porting/community-ports/android11/fxtec-pro1x/fxtec-pro1x To get all the partitions required for flashing, you need a "devel-flashable" zip. Unfortunately, the last successful job of that kind at UBports was 9 months ago, and the resulting artifacts.zip is no longer available for download: https://gitlab.com/ubports/porting/community-ports/android11/fxtec-pro1x/fxtec-pro1x/-/jobs So self-building the system p
    2 points
  13. This is not 100% related to the topic but close enough I think. I found a quite funny mini "BlackBerry" style bluetooth keyboard with a tiny display, named as Lilygo T-Keyboard. There is also a different version Watch-Keyboard-C3 that is intented to use with smartwatch. https://www.lilygo.cc/products/t-keyboard? https://www.lilygo.cc/products/watch-keyboard-c3-v1-0 Would be interesting to dissasembly the keyboard and figure out if it could be bundled with a phone. I found one video where the T-Keyboard is opened. It seems that you can remove display if needed.
    2 points
  14. Lineage-21.0-20240907nightly-pro1-signed.zip on August 5 (2024) security patch, installed smoothly using OTA BUT with these following issues: no camera no flashlight function
    2 points
  15. I wa under the impression that the persist partiton contained unique information so copying it would sort of making the two devices clones. Interesting if that is NOT the case as we could thus have one available somewhere.
    2 points
  16. I had already forgot this picture but the discussion here helped me to remember. Individual keys are indeed possible to swap or even rotate x).
    2 points
  17. I do that on my old pro1 No problem with the key himself, it stills work today. (but doesn't solve my keyboard problem, other story) Sorry the picture is blurry but could be interessant to give an idea from the dark side of the pro1s keyboard...
    2 points
  18. Someone brave should test to flash stock Android 9 firmware of Pro1 to Pro1-X with new screen. I mean the same process that Lineage OS users have done when changing the screen. "You have your current rom installed and try to overwrite it without wiping data. The installation starts and fails after a few minutes, however the display area is reconfigured" It works on Pro1 and you do not lose data. But probably the flashing of Pro1 firmware to Pro1-X does not even start. And if it does, there might be high risk to brick device.
    2 points
  19. 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 below
    2 points
  20. 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 e
    2 points
  21. I like the idea although the layout is very simple. But I fear most of us don't have the knowledge to connect a non-standard keyboard ribbon cable to a phone. With bluetooth, it's obviously much easier.
    1 point
  22. So I ended up building my own phone. Backstory: A few of you know me for my hardware modding adventures. I've replaced the broken USB port with a new port. I've then removed the fingerprint sensor to replace it with a secondary USB port for a more comfortable landscape mode. I filed away some parts of the display mount to make it more durable and I was about to replace the battery while reusing the old BMS. I did all of that to make my Pro1 work as I wouldn't want to live without a keyboard phone. Sadly, the issues didn't stop. The camera quality is bad, it's horr
    1 point
  23. First, off, warning... I have never installed UB Touch. Also, I'm not clear enough on what you have already done to know if I'm just suggesting something you have already tried. Looking at this page (I'm assuming you have the Pro1x): https://devices.ubuntu-touch.io/device/pro1x/ It appears to me you download an installer (links at the bottom of the page) to your computer and it downloads and installs UB Touch (presumably OTA-5, since that is listed as the stable version on that page). Again, I may be making way too many assumptions, but if I were interested in UB Touch, th
    1 point
  24. You are quoting a three year old reply - sorry I have zero recollection "The F(x)tec Pro1 is not supported by the current Ubuntu Touch release."
    1 point
  25. Hoping it's OK to quote my own post in the circumstances: After some uncertainty while I was trying to decide whether I might actually want to keep my Pro1X after all (!!), I can confirm this one IS indeed still (again!) available for offers. My apologies for the delay in getting back to people beforehand, due to the above plus also me having had my site notifications not set properly (facepalm!)... So yes, feel free to contact me [again!] if interested and/or you'd like to make me an offer... And I WILL reply this time!!
    1 point
  26. Hello EskeRahn, thank you for your answer! This morning Francisco confirmed that the flex are different in Pro 1 and Pro 1X I will continue to check if it there are some alternatives.
    1 point
  27. i still did not figure out, so i am not sure if the e.g. phone works. (e.g. IMEI is not shown) So know we know, that the root of my problems was regarding to the corrupted persist but wifi and bluetooth works just fine... So the the keypoints for the fix: having some ~working~ persist i needed to the patched boot.img, which stops early and runs the telnet server, so i was able to format userdata into ext4
    1 point
  28. I would expect that the screen plus frame they are selling, are far from the full top half, and thus not includes the front camera.
    1 point
  29. I was thinking that they are the same. Is the selfie camera different? I thought that only rear camera is different. But anyway, maybe @gusscan confirm? I think guss ordered pro1 screen panel with frame for Pro1-X. Also, some sellers list same screen for both Pro1 and Pro1-X (see attachments).
    1 point
  30. I was under the impression that the frame for the Pro1 is not 100% identical to the frame for the Pro1x (different camera? Other subtle differences?). Anyone know. I can't remember.
    1 point
  31. hello and thanks for the tip. the dealer has the same display for qx1050 and qx1000, so pro1x and pro1 on offer. but he doesn't ship to Germany, well, everything works fine. I just wanted to be on the safe side, burkhard
    1 point
  32. I found a possible correlation between the phone's temperature and whether the touchscreen works or not, as it has sat in sleep mode for a few days now and the touchscreen seems to be working every time I grab it. Phone has consistently been at room temperature every time I've tried. But when I plug the phone in and charge it, after a minute or two it warms up a bit to the touch...and the screen won't receive any touch input. It's wacky. A loose cable does seem possible, especially on the motherboard side. I'm still waiting on that replacement screen. I searched "QX1050" an
    1 point
  33. Lineage-21-20240902-NIGHTLY-pro1x with Aug 5th security patch installed smoothly via OTA. MindTheGapps14, and root was maintained. Notice, Monday's date as expected, but didn't actually show up until today, Tuesday. And, woo hoo, I can dismiss the lock screen with the space bar again! :D I'm probably the only one here who cared about that ;-)
    1 point
  34. I think someone here reported that one of the keycaps came off, and they glued it back in place?
    1 point
  35. That would be my guess too, but strange that that it starts working again though shortly. If you are lucky, it is a cable not locked in the connector and maybe the way holding it can make the cable just get or just loose contact BUT this is a pure guess,
    1 point
  36. To be honest, I'm really pissed now. Since the main display has black marks on the edges, I replaced it with a spare display that I got as a bonus. But this one has the same black marks. I'm really happy that I waited over 2 years for $889 for a device that doesn't make calls, turns itself off, gets hot easily, has a defective screen, a spare screen that is also defective, cheap earphones that I got instead of a spare battery, and 3 pieces of crap screen protector. Sure, the keyboard is pretty cool and works fine. But what can I do with it? I'm a programmer, but I'm not o
    0 points
  37. Hi guys, I have been using this device for about a month and it keeps shutting down on its own and it is really stressing me out. Same thing happens on both stock android and LOS. Right now I am using LOS and when the device shuts down the light starts flashing in different colors. At first I thought it was because the device was overheating but it also turns off when the device is cold. Is there any way I can fix this?
    0 points
  38. already tried installer. does not work:
    0 points
  39. Not sure if this is the place but I screwed up. I was trying to go from Lineage to stock Android and misunderstood the instructions. I thought that it said that you simply have to lock the boot loader by running fastboot flashing lock. However after running this the phone will only boot into into bootloader or lineage recovery it will not boot into an operating system. If you try to run fasboot flashing unlock is says command failed unauthorized or something along those lines. Is there a way to unlock without being able to enable developer options and usb debugging?
    0 points
×
×
  • Create New...

Important Information

Terms