Jump to content

Hook

Keymaster
 View Profile  See their activity

  • Content Count

    2,007

  • Joined

  • Last visited

  • Days Won

    283

 Content Type 

Everything posted by Hook

  1. Hook
    I don't know anything about the wireless display setup you are using, but the Pro1x is not capable of HDMI out and is only capable of mirroring with one cable setup that uses an apk to do some of the work. Here is the cable that should work on Amazon (although, I have never done this and I don't own the cable myself. https://www.amazon.com/Android-Mirroring-Charging-Smartphones-Projector/dp/B08LN8Z6QX Don't know if this cable connected into your adapter would make wireless mirroring possible.
  2. Hook
    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.
  3. Hook
    So glad it worked out finally. I will say, this stuff is tricky on Windows (and I am mostly a Windows user), However, I have an old Thinkpad that I installed Manjaro on. All the fastboot and adb tools were already installed and doing all this stuff just works smoothly. I now exclusively use that Linux laptop for doing this even though I am not all that skilled with Linux (luckily have a couple of knowledgeable friends that give me support). I don't know why it's such a hassle with Windows, but it always is and I can no longer imagine doing fastboot and adb without Linux. The iron
  4. Hook
    No you need to start with step 4. At the beginning of step 4, you are booted into the bootloader, where you can issue fastboot commands from the PC. You then use the command to flash dtbo.img (step 4) followed by the fastboot command to flash recovery.img (Step 5). As long as you stay connected in fastboot mode, you don't need to reboot to bootloader during these two steps. At the end of step 5, you can use the bootloader menu on the phone to reboot to recovery. Then you are ready for step 6. When you are in the Lineage recovery is when you can use adb commands.
  5. Hook
    This post that @Kilrahlinked you to says what to do at the No Command screen, Doing as instructed should take you to the recovery menu which should have the reboot to bootloader option. EDIT: Would have helped if I had actually included the link. Sorry.
  6. Hook
    Same explanation as here:
  7. Hook
    The backing up of the Persist partition doesn't apply to Lineage. I don't believe Lineage messes with the partition.
  8. Hook
    This and other links are all collected in the "Start Here" thread pinned at the top of the forum. :-)
  9. Hook
    https://discord.gg/F8FeutQX
  10. Hook
    I agree with @EskeRahn. I would wait for the next update and see if that fixes it. The Pro1x seems to have updated without that problem-- I don't know if that means they solved it, or that it was somehow exclusively a Pro1 problem, but they will get it fixed and most everything else still works.
  11. Hook
    Indeed. Lineage-21-20240701-NIGHTLY-pro1x with June 5th security patch installed smoothly via OTA. MindTheGapps14, and root was maintained.
  12. Hook
    Thanks. I didn't have a chance to check back. I was going to go ahead and b the guinea pig, but happy to not have to be. I'll update now. ;-)
  13. Hook
    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
  14. Hook
    Probably, this is the best place to start (hence it being in the pinned "Start Here" thread. :-) Only Stock Android requires you to have Google.
  15. Hook
    I notice we don't have a Monday update (yet). This is probably a good thing. I was worried we might get the same camera problem seen with the Pro1 update. Since we already have the June 5th patch, I hope they will wait and get the camera problem resolved.
  16. Hook
    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.
  17. Hook
    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.
  18. Hook
    Lineage-21-20240629-NIGHTLY-pro1 with June 5th security patch installed smoothly via OTA. MindTheGapps14, and root was maintained. However: The camera problem reported above for the Oddsoulutions version showed up here as well. Neither the AOSP default camera, nor Open Camera work. Open Camera reports "Failed to open camera. Camera may be in use by another application?" For now I will wait and see if this gets fixed in a future update since I don't really use the camera on my Pro1, but this would be mighty inconvenient otherwise. I have even tried a "battery pull" restart wh
  19. Hook
    Ummm... yes. See my post above yours from a month ago. :D
  20. Hook
    From Casey, on Discord: "Yes, we've shipped out the first batch yesterday. Tracking will be updated accordingly via IGG today and tomorrow"
  21. Hook
    Lineage-21-20240624-NIGHTLY-pro1x with June 5th security patch installed smoothly via OTA. MindTheGapps14, and root was maintained.
  22. Hook
    Have you been using Npj's build all along or did you somehow install Npj's build over the official build, because the later might create problems of it's own.
  23. Hook
    I found the problem. It was my end... kind of interesting actually. I discovered a Samsung Galaxy S9 attached to my network. I don't have an S9 (or any Samsung phone) so I immediately disabled it. Turns out, that's what my Modem/router thinks the Pro1x is. Lol. It was over a few days when I hadn't been using the Pro1x much simply because I was wrapped up in someone's medical emergency, so I didn't notice the wifi wasn't working anymore. I wonder why it made that misidentification? Downloaded now and installing.
  24. Hook
    I don't know if this is happening to anyone else. There is a June 24th update listed on the downloads page, but when I try to get it by OTA it tells me it failed to connect, check my internet connection (which is fine, btw). I'll give it 24 hours to resolve whatever it is before trying a sideload install. :)
  25. Hook
    Interestingly, when I check for an OTA update on my Pro1, which currently is on the June 15th update, it says no updates found. And when I check their download page, June 15th is the latest. Maybe they pulled it?
×
×
  • Create New...

Important Information

Terms

  I accept