Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 06/15/2024 in Posts

  1. Thomas Bonde Pedersen has at IGG posted a fix for the not charging Pro1! ADD: This has been confirmed to work by other users! Please try it, before disassembly (or send in for service)
    13 points
  2. Today a Pro1-X arrived at my place. IGG-Contribution around #4000, July 2022. (Enthusiast Pro1-X bundle) Pro1-X 8GB + 256G, Keyboard Layout: QWERTZ , Pre-Installed OS: LineageOS. IIRC no engraving, black. A sapphire blue QWERTZ-device was shipped (the color looks great, btw). S/N < 7000. XDA-engraving on the back. Seals of the packing where already broken. The battery was approx 1/3 full at arrival. it was no problem to recharge it. The device was shipped with stock android. Screen protectors, spare batteries and screens where not included. Importtax to Germany was 28,50 EUR,
    8 points
  3. Ok, so, good news! After some pondering, I decided to open the thing up. It was actually not that hard to take apart, the official Fxtec instructions for disassembling Pro1/Pro1 X (https://vimeo.com/483552998) were easy to follow. Note: I did not use a prying tool, as I found it easier to do with my fingers (as the plastic frame is fitted to the metal quite snuggly, I found it hard to get a prying tool in there). And a word of caution: the black paint on the back of the display chips really easily when removing the 5 screw covers. Once I had the display frame removed and the ribbon
    7 points
  4. You are lucky, mine doesn't boot, with a battery at 3,2 V, and a dumb red light who said to me : Not charging, you will have to completely dismont your brand new pro1x ...😑 Edit Ok works in LOS21 now, but what a sh... it's tricky to apply a bit more voltage directly on the battery connector, and also dismounting the whole thing.... What's a very big surprise, is to find a typical french AZERTY keyboard with é è ç , wich I had mailed fxtec for more as two years to switch in a standard qwerty but well... I'm going to try this beautiful-blue-things, at least the keyboard works good, and th
    7 points
  5. Sure do hope it works... Edit: it works - i just used a couple of rubber bands and paper towel to protect the screen.
    5 points
  6. This actually works. Thanks for this hint. Took me some hours to realize the screen was already turning on and off again. 😅 Well, now I'm stuck with starting it (link). Anyway, helped a lot to fight first resignation after opening a package I waited for more than 2 years, facing it seems broken.
    5 points
  7. Hey a new distro is out for this phone. Looks like a fork of lineage with desktop convergence and Linux os options coming forked from Droidian. https://lmo.framer.website/
    4 points
  8. My phone is working again! Well, the battery is charged, and it boots. I'm thrilled because I thought I was stuck with a poorly engineered brick. Now, I'm the proud owner of a poorly engineered phone. If we can just solve the issues around wireless connectivity, I can use this as a phone—one step at a time...
    4 points
  9. Just my personal opinion: I wouldn't bother with any derivative distributions and just use upstream official LineageOS. If you use that without GApps, it's pretty close to /e/-OS. The main thing they might have added is disabling AGPS (you decide whether that is a good thing.) The main security (and thus privacy) concerns with the Pro1-X are the ageing Qualcomm binary blobs, taken from Stock Android and stuck in 2022. No open-source project can change anything about that anyway ...
    4 points
  10. Have the same issue. Hoping it will work. It's really frustrating waiti g for so long and then finally you receive the phone and it's not charging/turning on Update: After leaving the phone in the battery loop over night it turned on this morning. THX for this post
    4 points
  11. We seem to have confirmation from someone else in Discord. The Pro1x is just kinky and needs to be tied up to get it's juices flowing.
    4 points
  12. I ckecked it too, with these results on my Pro1: (LOS 21, Magisk v.27.002, module: Play Integrity Fix v.16.3)
    4 points
  13. I have opened bug report on lineageos gitlab. https://gitlab.com/LineageOS/issues/android/-/issues/7410
    3 points
  14. I'm sure you could ask way more for an OG Pro1 in such good condition. I'd be very much tempted, but i've got a spare prawn already. Would be a pity if yours had to spend its remaining life in a drawer. Hope it will find another loving owner...
    3 points
  15. Thanks guys for your support. Those last days were exhausting. Wouldn't make it without you.
    3 points
  16. What worked for me now: - Installing adb and fastboot (partially as no FxTec USB Drivers available) https://wiki.lineageos.org/adb_fastboot_guide - ADB driver install (probably no effect) https://adb.clockworkmod.com/ - Reboot into bootloader mode With the device powered off, hold Volume Down + Power Enter recovera with Volume Up + Power - Enable offline charging fastboot oem enable-charger-screen fastboot oem off-mode-charge 1 fastboot reboot - Unlocking the bootloader (skipped as already by default) fastboot flashing unlock - Flashing additional
    3 points
  17. Hello, one more confirmation that this method is working! I received my long-waited Pro1X a couple of days ago. After unpacking, I noticed that the device didn't boot up or take charge. I was wondering whether to disassemble the phone to access the battery, or perhaps try to kick some charge in by plugging/unplugging a magnetic cable (probably a thousand times...) But luckily I found this thread. I wrapped the phone in its original packaging bag, squeezed its body (and the power button) with a long twist tie, and left it plugged to its own charger for the night. I can say
    3 points
  18. This and other links are all collected in the "Start Here" thread pinned at the top of the forum. :-)
    3 points
  19. @clueless - Holy sh*t it worked 😃 Thanks so much. I might actually be able to daily drive this thing now. Thanks alot! I had to do a pretty firm press and it made a quite audible click
    3 points
  20. I can confirm (at least for my unit). Distinctly pressing at the marked spot (front and back of slot for earpiece) created a squeaking noise, such as plastic parts being clicked into place. After that, phone audio is working fine through the earpiece on my unit. Only question being, how permanent this "fix" will be...
    3 points
  21. I received my device today (contribution 34xx, August 2, 2021, Scandinavian layout, delivered to Sweden). Faulty earpiece (can only hear phone audio through speakerphone or headset). Delivery took less than three years, which is definitely quicker than the wait for the Astro Slide (which I doubt I'll ever receive). So, I don't quite understand all the complaints. 😏 On a more serious note, they are finally providing detailed updates with real figures on the number of units shipped. That's good. However, I can't find any information about the total number of units still in stock. As an
    3 points
  22. quite easy...too late for me but good to know 😄 I measured 3,20V on the battery connector at red flashing state, is this voltage the very low battery state ? I thought it was more around 3V, but probably depend on battery model/technology Also I inject 4,1V direct on the battery connector, and in about 30s I had 5% battery, so this trick is very good !
    3 points
  23. Indeed. Lineage-21-20240701-NIGHTLY-pro1x with June 5th security patch installed smoothly via OTA. MindTheGapps14, and root was maintained.
    3 points
  24. lineage-21.0-20240701-nightly-pro1x OTA installed okay, 'Camera' and 'Open Camera' still working, root maintained :)
    3 points
  25. It's a long story, if you care to read through the updates on IGG. The 25 cent recap is: 1. The Pro1x was intended to be simply a Pro1 with a different color and more memory with your choice of OS. The OS images already existed for flashing the phones during manufacturing. 2. The company that was supplying their SD 835 chips took their money, but never provided the chips. 3. FxTec had to redesign the phone with a different chip, given their financial constraints. 4. Although prototypes and source code were provided to developers, there was insufficient time for images fo
    3 points
  26. 3 points
  27. From Casey, on Discord: "Yes, we've shipped out the first batch yesterday. Tracking will be updated accordingly via IGG today and tomorrow"
    3 points
  28. I've uploaded my latest build of LineageOS 16.0 for Pro1 (SD835) at: http://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 Go for the ROM dated "20240620". Changes since last month: Include backported Android security patches up to the June 2024 ASB. Update bundled version of WebView to Chromium 125.0.6422.165. As usual, the full patchlog with respect to the unmodified, official LOS 16.0 tree is available at the link above. Have fun.
    3 points
  29. Lineage-21-20240617-NIGHTLY-pro1x with May 5th security patch installed smoothly via OTA. MindTheGapps14, and root was maintained.
    3 points
  30. I just found the problematic app : Force Stop App (Boot Studio) If it can be useful Christophe
    2 points
  31. Supporting what @Hook wrote, and quoting the official LineageOS wiki: Alternative ROMs cannot magically fix problems that reside in the hardware or the binary blobs of the Pro1X. Are you sure WiFi, LTE and GPS worked fine with stock Android?
    2 points
  32. Lineage-21-20240708-NIGHTLY-pro1x with July 5th security patch installed smoothly via OTA. MindTheGapps14, and root was maintained. Very timely on the security patch for July.
    2 points
  33. Used a Win 10 tablet now. Pluging in the device shows the Qx1050 in device manager instantly, no need for driver updates. Copied files and linked path, run "adb devices" command and everything seem working. Sideload passed on the second attempt as on the first one it told me the recovery file is corrupted and system cannot reboot anymore. But I just redid the wipe and install. Gonna test now.
    2 points
  34. Lineage-21.0-20240707nightly-pro1-signed.zip on July 5 (2024) security patch, installed smoothly using OTA BUT with these following issues: no camera no accelerometer + proximity sensors no flashlight function
    2 points
  35. As far as remember, you do have to "accept" the Google terms, even if you skip connecting the device to a Google account. That's probably because the Google Services are already installed in the Stock ROM, whether you want to use them or not. It's been a long time for me though ... That being said, the only point with enabling USB debugging in Stock Android is to trigger that initial reboot to the bootloader, which you can indeed also just do manually with the "Volume Dn + Power" combo. While there really is no special trick about it, let me try a step-by-step: Power off the de
    2 points
  36. Android USB driver is generic, no need for a specific one. https://androidmtk.com/download-minimal-adb-and-fastboot-tool Just boot in bootloader manually, hold volume down while powering up. Nothing different from any other android phone really.
    2 points
  37. @chrissvI second your hesitation to send it back for repair.I haven't opened up mine yet -- but probably will rather soon. I don't really trust that simply pressing will provide a solid and permanent solution. AFAIK, the hardware of the Pro1 and the Pro1X seem to be pretty much identical in regards to the screen assembly. There are quite a few instruction videos on how to replace the entire screen of the Pro1 in just a few minutes. All it seems to take is removing five screws (after peeling of their adhesive covers) and carefully prying four plastic notches. An example is here:
    2 points
  38. The point with this step is to assure that everything hardware wise is working in your specimen, not to waste time on troubleshooting on Lineage, if it is a faulty specimen, that slipped through their QC. Or a connector managed to pop out during transportation, perhaps before you even got it. But it is not a MUST, seen in the sense that things wont work if you did not do it. It is just a fairly simple step, that might ease debugging any trouble.
    2 points
  39. I have been terrified of the battery accidentally running out while in use but this surprise solution makes using the phone a bit less stressful!
    2 points
  40. Have the same issue. Hoping it will work. It's really frustrating waiting for so long and then finally you receive the phone and it's not charging/turning on
    2 points
  41. Building on @Hook's answer: I believe the Pro1-X still always comes with official (i.e. googlified) Android, no matter what OS you ordered. You have to flash a Google-free variant yourself. Take a minute to read about the procedures and options, following the various links on that entry point he posted. You will probably want to flash LineageOS 21. Choose between the official version without GApps or substitutes, or the derivative LineageOS-MicroG. I have always only used the former myself. For guidance, follow the very good instructions on the LineageOS wiki. Once booted, install F-Droid
    2 points
  42. Interesting. He is basically causing a looping "Battery pull" reboot, so it seems that there is some low level part of that which briefly draws power without needing the usual processes that require being able to fully boot. I've always said the "battery pull" reboot was very useful for a wonky behavior on a phone, but I had no idea. ;-) Hope we can get a record of this working for someone else for verification.
    2 points
  43. Awakening an old thread. A user reported a way to fix the issue on IGG:
    2 points
  44. Lineage-21.0-20240615nightly-pro1-signed.zip on May 5 (2024) security patch, installed smoothly using OTA
    2 points
  45. (lineage-21.0-20240615-nightly-pro1-signed.zip on May 5 security patch installed smoothly (*) using adb sideload and MindTheGapps-14.0.0-arm64-20231025_234300) And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage.
    2 points
  46. They seems to finally be sending out the form-request for IGG. Got this
    2 points
×
×
  • Create New...

Important Information

Terms