Jump to content

Hook

Keymaster
  • Content Count

    1,911
  • Joined

  • Last visited

  • Days Won

    224

Everything posted by Hook

  1. For people considering this, it would be nice if you expanded on what specifically is "much better" in 21 compared to 20. Is it that 21 is much better than 20, or is it that you are finding whatever tweaks Nolen has made in his version so much better than Official 20? Anything you can be specific about will help people. :)
  2. Lineage-20.0-20240129-nightly-pro1x with Jan 5th security patch installed smoothly via OTA. MindTheGapps13, and root was maintained.
  3. This exact version will never quite become the official version. Nolen maintains his own versions, although he also contributes to and uses some of the same work that goes into the official versions. So, yes, if you want to switch to the official version when it comes out, you would have to do a clean install. That said, there is also no guarantee that there will be an official version . Of course, I assume there will be, but Lineage could decide to drop support for the Por1 and Pro1x. We don't know until we know (Lineage never answers questions about future versions or support).
  4. That may confirm an impression I had (but couldn't find any source that I had gotten the impression from) that Nolen includes Gapps actually built into the ROM.
  5. From what I can tell (I don't have inside information), Francisco handles all communications concerning trouble tickets. That doesn't necessarily mean he is working to solve all the trouble tickets or that he makes all the decisions concerning trouble tickets, but he is the one doing the communication. There will tend not to be responses for email inquiries about what is happening as only IGG updates, as infrequent as they are lately, are used for such information. Both Casey and Francisco have communicated on trouble-shooting matters in Discord, but not as often as they used to.
  6. Lineage-20.0-20240122-nightly-pro1x with Jan 5th security patch installed smoothly via OTA. MindTheGapps13, and root was maintained.
  7. That code, using the phone dialer, works on both my Pro1 and Pro1x. Takes me to the phone info page. What's interesting is on both my Pro1 and Pro1x, the VoLTE toggles are grayed out, but grayed out in the "on" position and I know both are using VoLTE. Both are on Lineage. But I should also point out that that code worked fine on stock as well.
  8. Other than the VoLTE toggles, there isn't much. You can look under Settings if any "preferred network type" settings work better than others or if you have the right Access Point names selected (if there is more than one-- sometimes there isn't.
  9. The Pro1 is certainly capable of VoLTE, but it depends on both the carrier's willingness to let it onto their network and whether VoLTE has been provisioned in a way that will work on the Pro1 with their SIM card. In the past few years, more and more carriers have been moving to allow only whitelisted phones. Here in the US, with a Pro1 (or Pro1x) you can no longer use AT&T, You can use Verizon only if you have a SIM that has been activated in a a Verizon approved phone and moved to the Pro1 (and it doesn't always work). Only T-Mobile US and T-Mobile US MVNOs work well at this point. I
  10. Lineage-20.0-20240115-nightly-pro1x with Jan 5th security patch installed smoothly via OTA. MindTheGapps13, and root was maintained.
  11. I'm pretty sure that is Nolen Johnson's version of Lineage. It probably means there will be an official version soon.
  12. Lineage-20.0-20240108-nightly-pro1x with Dec 5th security patch installed smoothly via OTA. MindTheGapps13, and root was maintained.
  13. Don't know if this is the problem, but it sounds like what would happen to me on my Pro1 when I used to try to mule it onto Verizon's network. That is exactly what would break and how it would break. On T-Mobile (USA), which has no problem with the Pro1 or Pro1x being on their network, no problems at all.
  14. Lineage-20.0-20240101-nightly-pro1x with Dec 5th security patch installed smoothly via OTA. MindTheGapps13, and root was maintained. Happy New Year!
  15. Interesting. Nolen said it didn't work in stock either. But looking back at my original Gitlab bug report, I said it did work on stock. It has been so long since I have used stock, I had forgotten. So, strange. I'm staying with Lineage nonetheless. I'm just careful not to let my Pro1x discharge too much. So, if I take Nolan's explanation at face value, maybe stock blobs can interact with the bootloader in a way that Lineage can't? Not that I understand any of this. Curious if we can get @npjohnson to pop in. Or maybe @Sean McCreary has a clue.
  16. Lineage-20.0-20231225-nightly-pro1x with Dec 5th security patch installed smoothly via OTA. MindTheGapps13, and root was maintained. Merry Christmas All!
  17. So, 8 months ago I opened a bug report on the Lineage gitlab concerning the fact the the fastboot commands do not work to prevent booting when charging. Nolen Johnson just officially closed it as unsolvable by the Lineage folks. They would need to be able to control the bootloader and they have no access to do that (that's my paraphrase of what Nolen said on gitlab). So, in fact, probably cant be easily fixed by any alternative OS.
  18. Hmmm, I just tried and uploading a pic worked. I'm on my computer, not my phone.
  19. I found this, but I would be cautious about any case claiming to be for the Pro1 or Pro1x that doesn't show complete pictures. The case may fit, but does it allow the keyboard to open properly? Luckily Amazon allows returns... https://www.amazon.com/Compatible-Qx1050-backplane-Silicone-KA-HEI16/dp/B0B8S3TXGM My skepticism comes from seeing manufacturers in China relabel a case as for the Por1 or Pro1x just because it fits in one way or is a universal case they think might work, but these cases tend not to be actually created for the Pro1x.
  20. I moved your post to this long thread, which covers both the Pro 1 and Pro1X. You will see there is no one perfect solution and mostly you have to take something and hack it up a bit. I really like the clear case I hacked up a couple of pages back in this thread, but there are many alternatives.
  21. Need a bit more information. Are you connecting just to access files from your computer or are you trying to do things with fastboot and ADB commands to flash an alternative OS or root. Have you tried different USB ports on your computer? Have you tried different cables, making sure they are data cables and not just for charging? If just transfering files, have you made sure, once connected to the computer that you change the default "charge only" setting to "file transfer?" There is a notification in the pull down shade that you tap to make this change.
  22. Lineage-20.0-20231218-nightly-pro1x with Dec 5th security patch installed smoothly via OTA. MindTheGapps13, and root was maintained.
  23. I'm not clear on this, but I think the patch to the firmware was intended for the Elephone U Pro and just plain doesn't work in anything higher than Android 10. I don't know what keeps the native Pro1 and Pro1x screens from having this problem... but whatever it is, it is not compatible with Elephone U Pro screens. I wonder if @Casey has any guidance on this matter?
  24. There is one rather insane possibility for anyone who has both a Pro 1 and a Pro1x... install the display first in the Pro1 (probably wouldn't have to even glue it) and flash the firmware of the screen. Then remove it from the Pro1 and install it on the Pro1x. I'm no expert and I'm just guessing, but would that work, I wonder.
  25. The problem is the fix for the Pro1 was a patch from the Screen manufacturer that requires Android 10 or less. FxTec was able to incorporate that patch into their version of Android 9. Since the Pro1x starts with Android 11, there is no way to patch the Elephone U screens for the Pro1x. At this juncture, at least as far as I know, there is no fix until FxTec is able to provide replacement screens.
×
×
  • Create New...

Important Information

Terms