Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/11/2020 in all areas

  1. I have finally received a (used) Pro 1 too, so I was able to try and play with it a bit today. The ideas in this thread sounded very interesting but I looked for a completely silent method that also reduces the risk of dropping the phone because of the spring mechanism. What I do is I lift up the back slightly and then push the top forwards. That way I can open the phone completely silent as you probably (can't) hear in this video. Also you do need less force to open it. Don't forget to rate my camera setup...
    5 points
  2. What did you do to end up in this state? Attempt a ROM flash? We need some context to help you out first.
    4 points
  3. I've seen it reported that the Pro1 doesn't come with its own recovery. There is a standard recovery included with the phone's firmware. I think there may have been some confusion due to the way you need to access recovery mode. To access recovery mode, you have to either: A) Hold down the volume up when you boot the phone (before the logo screen comes up) or B) Use "adb reboot recovery" from a connected computer or C) Boot into the bootloader (by holding down the volume down when you boot the phone (before the logo screen comes up) O
    1 point
  4. That's what I love about Lineage vs Stock... most of the workarounds are no longer needed and instead integrated into the OS. 😉
    1 point
  5. 1 point
  6. I am at 62 days but thinking it could use a reboot. The rotation is being funny, I have to launch the camera app at least 3 times a day to fix it. Ho well that was a good run.
    1 point
  7. So I tried flashing the test13 image of Lineage onto my new Pro1. I am certain that I followed all the instructions to the point where possible and used a USB2 port (as USB3 wasn't working). While flashing the recovery worked fine, the first issue I encountered was sideloading the image to the recovery: This always failed. adb sideload lineage-16.0-pro1-test13.zip serving: 'lineage-16.0-pro1-test13.zip' (~30%) adb: failed to read command: Success As a workaround, I put the zip onto an SD card. Then flashing was successful, but the resulting LineageOS installation just t
    1 point
  8. @EskeRahn Sadly I'm no longer in that boat, I'm in this one. -https://community.fxtec.com/topic/2951-screwed-up-i-locked-the-bootloader-wont-boot-and-cant-unlock-it/ I've been working with FxTec support to try and fix it without having to send back to them and have them re-flash it. I made such a noob mistake not to backup all the files/images before trying this. I've emailed @tdm to try and see if I can get some help from him as well. If I do find a workaround I'll let you all know. I would like to help with the development of the LOS version.
    1 point
  9. As far as I know, it has been already resolved in LineageOS and maybe the actual (unreleased) version of stock firmware has related bugfix. So yes, it is up to F(x)tec (their partner) but they will definitively solve it sooner or later as the cause should has been already known.
    1 point
  10. Yeah that seems accurate. The time on the "alarm" now changed to 7:45PM tomorrow, so I tried setting an alarm at 5:30AM tomorrow, and indeed it updated.
    1 point
  11. That's an alarm (and so is the icon in the status bar when you collapse it. Something has an an alarm set for 6:01 pm-- you can check alarm. It might not produce an actual alarm, depending on what's doing it. I used to use a calendar app called Pimlical and I would see an alarm for 2:00am jin that position (if there wasn't an actual alarm scheduled sooner) just because that was when the calendar app performed a daily housekeeping. Something on your phone thinks it has an alarm scheduled.
    1 point
  12. Looking at how your update is named "userdebug 9", I think you got a unit with a pre-production flag enabled of some sort, so yours came shipped with an unreleased firmware. Maybe you can help test to see if the extensive list of bugs are fixed...
    1 point
  13. You can use Whatsapp Business for second sim, it's basically same app with few additional features.
    1 point
  14. Just published release v0.9.3.
    1 point
  15. Sounds like you could be right. Looks like an odd scam. The account created a few days ago using a "spamdecoy" mail-address. It all have an ooze of fake... But I could be wrong of course.
    1 point
  16. Seems an awful waste since a) I have no idea why you think you are entitled to a refund for a smashed phone and b) unsmashed, you probably could have sold it. But if the therapy was worth $700+, glad it was cathartic. By the way, very little of the above has been my experience.
    1 point
  17. I would prefer not to do that, as it could introduce a security risk. Simply run "adb root" and then make your change. Afterward, you can "adb unroot" or reboot the device. I don't think Android lets you deselect the qwerty/qwertz setting. But yes, the setting is directly tied to that file. Note: In an ideal world, the factory would provide some sort of way to find out the physical keyboard layout. The only difference I can see between a QWERTY stock image and a QWERTZ stock image is in the Android keylayout files in /system. These get over-written with t
    1 point
  18. I honestly think you are jumping the gun—not that they shouldn't be faster, but they have a limited staff still working from home and it takes them a while to get through all the email that comes in. You can try invoking @Erik here and see if he can elevate it. I believe from others' experience that you will get the refund.
    1 point
  19. Just published release v0.8.5. It enables search suggestion list item selection using keyboard.
    1 point
  20. Just published release v0.8.1. @hermite This version notably adds auto-update checks much like F-Droid does. Whenever there is a new version available it will notify you.
    1 point
  21. You are only able lock if you unlocked it. The first couple batches shipped with it unlocked. https://community.fxtec.com/topic/2521-notice-regarding-getting-google-safetynet-certified-software/
    1 point
  22. Below 45% the dragon starts to appear even brighter than at 55% as the black becomes green-grey instead. I would definitely expect this to be remedied by an update or screen replacement but will let them deal with the factory production and shipment first while it gets figured out.
    1 point
  23. I took a slow motion video of opening the Pro1. You don't need to pay attention to the technique I used because I had to use my other hand to shooting the video.
    1 point
  24. UPDATE: Link to my comment with working root access for anyone who's looking for a quick answer: I got my device yesterday delivered by UPS. I'm very happy with it, the only thing I don't know how to do is get root access. Has someone got root access working in the stock software?
    1 point
  25. My order #53*** (qwerty) has been received two days ago 🥰
    0 points
  26. Today was the best moment I've had with the pro1. I bent it with my hands, threw it across the room into a wall, I retrieved it and the thing was still on even though the screen was cracked, and the keyboard dislodged from the body! I pulled my sim and sdcard from the phone so I could finish the job. I took it out to my workbench and smashed it to pieces with a hammer. It was truly the most satisfying moment I had with the pro1. The spontaneous reboots for days on end and then stability for a couple weeks, only to start rebooting again. The ability of the camera to take one
    0 points
×
×
  • Create New...

Important Information

Terms