Jump to content

tdm

Members
  • Content Count

    337
  • Joined

  • Last visited

  • Days Won

    17

tdm last won the day on March 13

tdm had the most liked content!

Community Reputation

1,100 Excellent

3 Followers

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. tdm

    Factory Restore Tool

    Glad you got it to work. Where did you get the idea that the firehose for any of those devices was used? None are, of course. The pro1 firehose is used.
  2. tdm

    Factory Restore Tool

    Several minutes, same as actual writing. Yes, I can give you a debug version. But a packet capture with eg. WinPCAP or wireshark would probably be just as useful. Nope, the edl code knows nothing about led or screen or anything else. That's the thing, USB does not have a programmatically settable speed. So you can set the virtual serial speed to whatever you like and the actual transfer speed will be the same.
  3. tdm

    Factory Restore Tool

    If xbl is functional this should always work. And if you can get to the point where you see a boot logo when turning on the device, xbl (and much more!) is functional. Try putting the cable in the other way (eg. upside down). @Sean McCreary was unable to get his device into EDL mode using a "deep flash" cable, so he disassembled it to fix it. A couple months later, he found that if he flipped the cable upside down, it worked.
  4. tdm

    Factory Restore Tool

    @david you had several posts with several questions so I'll answer them here. Why did I choose to use WinUSB instead of the Qualcomm driver? There are a couple of reasons: The Qualcomm driver exposes the device using a serial port. This is ancient and outdated technology that is difficult to use. At minimum you need to figure out the virtual "com" port number assigned to the device by the Windows device manager. This is unnecessary and confusing. The Qualcomm driver is not installed automatically for all versions of Windows. Finding it and installing it manually is a huge pain. Again, unnecessary and confusing. Why are the WinUSB driver and the Qualcomm driver incompatible? Because programs that are written for the Qualcomm driver use Windows' serial port API and WinUSB does not provide a virtual serial port. Conversely, my program uses the bulk USB protocol and the Qualcomm driver does not provide access to that. Could I modify my program to be compatible with the Qualcomm driver? Sure. But why move backwards just because Qualcomm is stuck in the 1980s? Why does the flash tool show "Unknown error" when it is done flashing? I don't know but if the flashing process completes, it should not affect the operation. If you are concerned about it, I can work with you to try to figure it out. Nobody else has reported this issue, except apparently @VaZso who has replied that he also sees it. WinUSB has no inherent serial speed settings or limitations, nor framing (bits and parity). These are serial port concepts, not USB concepts. USB speed is negotiated below the programming API and, as far as I know, cannot be changed programatically.
  5. Did Sprint ever use TDMA? I thought AT&T was the only one that used TDMA (before they moved to GSM)?
  6. I'm not going to say anyone is lying. Certainly it appears that some CDMA data capabilities exist. But it is not fundamentally a CDMA device. I would say that it is a GSM device that is compatible with modern CDMA networks that implement data-only voice services.
  7. That is all data. And I presume Verizon users can get data. Can you make a CDMA voice call? Can you show me your CDMA MEID? Can you operate the device on the network without a SIM card? The answer is no to all three. Any actual CDMA device would answer yes to all three.
  8. Sorry, no. It is not a CDMA device. GSM and CDMA are fundamentally and technically different protocols. Just because Verizon (and I assume Sprint) has seen the future and is ditching traditional CDMA for VoLTE and they can support random GSM devices does not magically make them CDMA devices. On the other hand, if you can take your SIM card out of the Pro1 and still make a voice call on Verizon, like you can with any real CDMA device, then I will retract my statement.
  9. This isn't a Pixel device and FxTec is no Google. You'll be lucky to just get support equal to other manufacturers. Read the Lineage wiki. I'm sure this is covered in detail. Hint: extract-files.sh. If you need to do a full factory restore (you won't if you are careful), just grab the latest fastboot package and flash it, then "fastboot -w" to erase userdata.
  10. I do not have Verizon, so I cannot really fix it. It would be great if we had a developer that did use Verizon. But if none appear within the next few weeks, I'll probably need to have a Verizon SIM card sent to me. However, as this is a GSM phone and Verizon is a CDMA carrier, I see this as a sort of "extra" functionality -- an enhancement request of sorts. It will take a back seat to getting all the other bugs fixed and official builds running.
  11. Production and software updates are the fault of IdeaLTE. Lack of communication is clearly the fault of FxTec.
  12. Yes, they are available to copy. It's pretty trivial to do this. Oh, and I forgot to mention config files. Those can affect behavior also. But I think I've got all the relevant config files in place and up to date. Also note that Lineage is free to take changes to improve performance that aren't in stock. Particularly with WiFi and GPS. For example, on a previous device I owned, stock only enabled 2.4ghz on WiFi but 5ghz worked perfectly fine. So I enabled it.
  13. In theory Lineage should provide equal performance as stock for all components. If it does not, let me know and I will look into it. Some of the sub-systems that you mention (gps, wifi) have partial open-source components and partial closed-source components. If for some reason the open source components do not work as well as stock, I can look into it. But I am not aware of any such issues at the moment. Some of the sub-systems are pretty much completely closed source (camera, cell radio). These should certainly perform identical to stock. With that said, some behavior is determined at runtime via system properties. It is possible that I may need to tweak some of the system properties to get the components to behave properly. But again, I am not aware of any such issues at the moment.
  14. I haven't heard any complaints. Logs would be a good first step.
  15. I will not comment on whether stock is subpar or not. That is a subjective call. But I will say that stock is pretty much just a basic BSP build with a few changes tossed in here and there (like landscape mode). This is something that a developer team at any other company would use as a starting point for their stock software. It is not a finished product that was meant to be used by consumers. There are reasons for this, as I have mentioned -- IdeaLTE is a hardware company and FxTec cannot afford a software team. But folks who choose to use stock should know about this situation so that their expectations are not set too high.
×
×
  • Create New...

Important Information

Terms