Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/23/2020 in Posts

  1. qaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
    4 points
  2. Please don't. Or at least clearly separate the product review from the support communication review. We all want fxtec to get on their feet and produce more phones in the future.
    4 points
  3. If you have your last phone still and it is VoLTE capable, use that phone to get them to enable it and then transfer to the Pro1. That's a trick used with Verizon. Might work for AT&T. On the other hand, they may not care what the phone is-- they don't for Prepay.
    3 points
  4. Apparently, this is an issue on stock as well according to another user, though I don't have log verification at the moment. The symptoms described were the same. ๐Ÿ˜ž I'm going to see if I can get VoLTE working which will hopefully resolve this.
    2 points
  5. I have the same problem as @itsdevilslettuce with test 22, which I'm still on since it's working great and I'm a little hesitant to fix something that isn't broke, given the past. I've deleted all the fingerprints under security settings, then removed /persist/data/fingerprint. I can re-add the fingerprints and the directory is made like it should be. The real problem seems to be that for some reason most apps think the fingerprints have changed whenever you reboot. They are still set correctly and work fine, it's just that for your banking apps and such, you have to set them back up to wo
    2 points
  6. I did the same and have no issues (of course first login doesn't work but thats supposed to happen)
    2 points
  7. I got little bit under 40 WPM with couple tries. I was still able to beat the others. ๐Ÿ’ช
    2 points
  8. I am pleased to announce that the Pro1 has received official support in LineageOS 16.0. You can find the builds and installation instructions on the official LineageOS Downloads page. Please note that LineageOS does not include the proprietary Google apps (aka. "gapps", Play Store, etc.), nor a "su" binary. These are "extras" or "add-ons". You may use any appropriate gapps package for Android Pie. I personally recommend MindTheGapps which can be found here. LineageOS maintains an official su add-on and a couple other extras here. Note the Pro1 is arm64 and be sure
    1 point
  9. I am pleased to announce test builds for LineageOS 16.0. Please note this thread is for test builds. These builds are not necessarily stable or suitable for daily use. You can find the build(s) and detailed installation instructions here: Lineage on FxTec Pro1 Test Builds Please report any issues here and I will do my best to fix them. Thanks!
    1 point
  10. My last phone was an unlocked Moto Z, not purchased through them. I'm calling them anyhow today, I'll let you know how it goes. Thanks. ..or wait, my wife's phone was purchased through them. I wonder if I can pop my SIM in there and ask if they can enable it?
    1 point
  11. Ok, all of those options are enabled. So I guess I'll call AT&T and get the bad news. They are probably NOT going to enable for this thing since it isn't on their list.
    1 point
  12. Again, I'm not really technical on this, However, if you dial on the phone pad *#*#4636 #*#* and tap phone information, down at the bottom of the screen are a series of switches for provisioning of VoLTE and Wifi calling and such. These have already been switched on in the current test and official builds of Lineage, so you really shouldn't need to do anything. However, I think it depends on whether your SIM has been provisioned for these things. If you are using a very old SIM, you may need to talk to yourcarrier about replacing the SIM.
    1 point
  13. I have wifi calling enabled, but I'm pretty sure it's not working. Whenever I call out, it switches to H+ (or doesn't and fails). If I force LTE, the call just ends immediately. So I cannot call with LTE only, VoLTE or not.
    1 point
  14. So, tried the suggestion. I enabled battery saver and flight mode. It charged from 68% to 69% in 15 minutes ๐Ÿ˜’. Looked up further specs, trying to figure out why it worked on in combination with the Sony XZs. The CPU is an 820 with a 2900mAh battery. It does not work on the Sony XZ1 compact, which sports the exact same CPU as the Pro1. I have to say I am surprised that it works acceptabel(y) well on the 820, but not the 835 ๐Ÿค”. And I agree with the thought this may be due to a handshake of some sorts.
    1 point
  15. I just don't understand. If you (the company) don't have exact dates, then take a little heat up front sand say "We're not sure, but once we know we will share that info" instead of constantly reneging on promises. Simply put this is bullsh*t. Yes I'm excited for my phone, and I will keep waiting, and I understand that that's all they care about. But this PR department is either run by people that genuinely do not care about their customers or they're in the second grade. I'm in the group with Stock assigned earlier this month (US). Had they told me back then that my stock was assigned an
    1 point
  16. Without assessing how genuine this proposal is (no insult intended-- it is just possible this is spam), this is a user forum and you won't get an answer here. You should email any inquiry to [email protected]. Nothing will happen from posting here on this matter.
    1 point
  17. I will definitely leave a negative review after the whole story. This is not how you deal with customers. This is partly kidding the customer
    1 point
  18. Yes, you could. But I have the original factory package (from @Waxberry) which was used to make my factory restore package. It is much quicker and easier to make a fastboot package directly using the original factory package. Plus you get the original sparse images which are much smaller than full images. So either I could give you the images from the factory package with Chen's approval, or he could go ahead and make another fastboot zip like he did before. Yes, this does work. You just "dd" the userdata partition. The encryption footer is on the userdat
    1 point
  19. Over at the factory restore tool thread, tdm said: Cool! This means I could "restore" my phone with the restore tool, extract all the necessary firmware partitions and make them available for manual flashing via fastboot. So one step closer to figuring out how to get some images for flashing ready. Currently I don't have a proper way of making a full backup of my phone though. By proper I mean something like a nandroid/full data partition backup. I did some backups with adb, but I don't really trust it. I used to do this with TWRP on my old phones. There is a TWRP, but withou
    1 point
  20. I could definitely be wrong yes, just wanted to share my experience with wireless chargers. In my experience they were also extremely fickle and not consistent at all. Sometimes it would just charge fine, other times I'd return to a hot and nearly empty phone. Again guessing here, but I think it might've been some slight differences in what software was running in the background. This was an LG G3 on a LG charging dock by the way, so even more reason for it to just work.
    1 point
  21. Hmm, thanks, I'll take a look. Note the /persist partition is not wiped when you do a factory reset. I have a script in Lineage that deletes /persist/data/fingerprint at boot when the Android fingerprint data does not exist (eg. after a factory reset) so that Android and the fingerprint HAL can stay reasonably in sync. The fingerprint HAL should be re-creating that directory when you first enroll a fingerprint. EDIT: Also note that the fingerprint HAL is entirely closed source. The only possible changes have been in updating the vendor blobs from the 6/22 OTA and the
    1 point
  22. No way. As I stated, I own a regular wireless charger (Samsung) and three quick chargers (Samsung & BaseUs). Also two car holders with quick chargers (BaseUs). It's the same pad that worked on Priv and XZs. Same meaning exactly that same one (XZs). Just to humor you I just connected it to my Pro1, placed the pad on the quick charger and left it for 15 minutes. Power went down 2% ๐Ÿ˜ฅ No metal interference whatsoever. The BaseUs pad I'm using claims an output of 5V 1A. That was enough to charge my XZs in, if I recall correctly, 3.5 to 4.5 hours. No it wasn't fast, but I wasn't in a
    1 point
  23. jeix.. then my assumption wasnยดt correct ๐Ÿ˜„
    1 point
  24. I have created an official LineageOS discussion topic: https://community.fxtec.com/topic/3037-lineageos-160-official-builds-discussion/ This thread should die down and the new one should take over.
    1 point
  25. New mailing from Fxtec: Hello! We hope you are well and keeping safe. We just wanted to get in touch to give you an update with regards to manufacturing and shipping of remaining customer orders, but also to fill you in on everything that has been going on with the F(x)tec team. We are still currently understaffed as some of the F(x)tec team are on on furlough. This has undoubtedly resulted in our customer service and email responses taking much longer than usual to sort through and respond to, and for this we really do apologise. We are working through queries as quickly as we ca
    1 point
  26. I'm from Germany with order #36xxx for a QWERTZ device, though mine wasn't in this batch yet. But I got this new message: Hello! We hope you are well and keeping safe. With the factory returning to normal production speeds, we are making steady progress working through remaining orders. The factory has confirmed a small batch of Pro1โ€™s is ready to leave the factory, and those that have been allocated stock should now have received a shipping update. We are currently negotiating shipment releases on a 2-3 week basis with the factory, and will be in touch when the next shipment is ready.
    1 point
  27. Guess we'll have to wait for iFixit and JerryRigEverything :)
    1 point
×
×
  • Create New...

Important Information

Terms