Jump to content

Leaderboard

  1. EskeRahn

    EskeRahn

    Keymaster


    • Points

      252

    • Content Count

      2,805


  2. tdm

    tdm

    Members


    • Points

      198

    • Content Count

      340


  3. david

    david

    Members


    • Points

      113

    • Content Count

      1,083


  4. Rob. S.

    Rob. S.

    Members


    • Points

      90

    • Content Count

      173



Popular Content

Showing content with the highest reputation since 03/05/2020 in all areas

  1. 19 points
    We are very sorry for the issues caused. After some investigation we have found the reason, it was due to the upgrade of security patch to October which needs to be approved from the authority before it was released, which caused CTS to fail. Also there is no way to downgrade security patch via OTA (the user data will be wiped if doing this way.) Therefore the current workaround / work is: - We are acquiring the latest security patch (Feb 2020) and will submit for approval before the next OTA. Therefore once the next OTA with latest security patch applied, and approved, it should automatically solve the issue. However due to the impact of COVID-19 people are still not fully back to work in China, it might take longer than expected. - If your service is affected, such as the limit of Google Pay etc, there will be a fastboot image uploaded (dated 20200306) with security patch back to September 2019 with the latest keyboard fix. You need to back up all your personal data and perform a fastboot flash and set up the device again. In the future, both 0304 (CTS issue) and 0306 will be updated with the latest security patch together. We are really sorry for the inconvenience (was too excited to share the keyboard fix) and will do our best to get it solved ASAP.
  2. 14 points
    UPDATED: Hi everyone, there is a new OTA update stamped 2020-03-06, offered. This REPLACES the OTA stamped 2020-03-04, that proved to have an error with Safetynet. IF you already updated to the 2020-03-04, you will NOT be offered the 2020-03-06. But both groups will be offered a common OTA, hopefully in the coming week. The two updates contains the same fixes, but the 04 had slightly newer security patches, and that broke Safetynet OLD message on the 2020-03-04 : Hi everyone, @Waxberry has shared a little sneak view of some expected to be in the next OTA Fixed keyboard two keys cannot press together Fixed left and right speaker swapped sound channel EDIT: Now available as OTA update EDIT2: Temporarily suspended, as it had a bug breaking the "SafetyNet", fix should be on it's way quickly. Edit3: Replaced for new users, see above https://drive.google.com/open?id=1iEpVyR5RbOgkbv22Q8ILJcIHDf6241G9 GUIDE for the impatient ones: Fetch file on(/to) phone Settings, System, Advanced, System updates, Settings, SD Card update Point to zip update-20200304204235-20200106110451.zip Follow screen instructions. NOTE that there is a slight display-issue in the updater, after it starts installing a user selected zip it seems that nothing is happening at all, but pressing back once, will bring you to an image with a progress bar. If you do not do that, and just waits, it will install just as fine.
  3. 14 points
    I'm going to be pushing for official Lineage support over the next few days. That means fixing all the known bugs (not necessarily enhancement requests, but of course I'll get to those also). So if anybody is experiencing any issues that aren't in the github tracker, please add them ASAP. Otherwise, I'm going to assume FM radio and selinux rules are the last release blocking issues. Also FYI... as soon as Lineage 16.0 goes official, I'll start working on 17.1. That should be a breeze compared to initial bringup. Oh and I'll probably be making an AOKP build this week. πŸ˜„
  4. 12 points
    Hey all, it's been a while since I've been here so I wanted to pop in and give an update. I live in Seattle, which has been under stay-at-home orders for over two weeks and will continue until at least the end of this month. I have a wife and 4 boys at home, and we are all healthy. But it is difficult to get any work done between the constant interruptions. In addition, I have been given a new project at work that will take a week or two to complete. So I'm afraid that I won't have much of any time to work on the Pro1 until at least the middle of April, but more likely the start of May. But rest assured I will continue to work on it when things get closer to normal again. Stay safe and healthy out there!
  5. 12 points
    test10 is up. Changes: * Fix audio crackling. * Update fingerprint mitigations.
  6. 11 points
    And adapt quite well
  7. 10 points
    Hey guys. Just wanted share the case I printed out for my wife. She wanted a functional opening case that would protect her phone and won't fly off when it opens. After many attempts I was able to get it to work. I'm probably going to modify it some more and tweak my print settings to make it a lot nicer and possible do some post print finishing.
  8. 10 points
    3D Files are here : https://www.thingiverse.com/thing:4236222 (thingiverse is quite slow today)
  9. 9 points
    My preferred wallpaper is attached.... πŸ˜‡ I named it Black_1x2.png
  10. 9 points
    Turns out it was a loose pin. I went in with my basic iFixit tool kit, followed the steps in this PDF took off the screen, unplugged and re-plugged in the section that was marked LCD screen, put everything back as it was, and it works again. Everything is back to normal and good to go (except for sending SMS, but that's a different problem having to do with Verizon).
  11. 9 points
    Got the FM radio fixed (listening to it now). Will push that up and do a new build soon. If anyone is interested in details... The first problem is that the AOSP "FMRadio" package is broken and not used, there is a QCOM "FM2" package that is used instead. I've noted this before. Second, there are some libraries that must be specified to be built which I was missing. Thirdly, there is a library that seems to be in the open source code but explicitly set to not build without the BSP for some reason so that needs to go into the proprietary blob list. Fourthly, was missing a required property, "vendor.bluetooth.soc=cherokee" (I had mistakenly set vendor.qcom.bluetooth.soc). EDIT: both vendor.bluetooth.soc and vendor.qcom.bluetooth.soc appear to be used in various places, so I guess both need to be set. Yay consistency...
  12. 9 points
    Sorry to hear you had to buy another phone.. As you may or may not know, our factory in China, including their supply chain, has pretty much been off for the past 2 months. We are told they are back operating at some capacity but it's still nowhere near the efficiency and speed before the Coronavirus outbreak. Although very slowly, devices are being produced, but what can we do about that? We don't have 5+ factories like Canon, and we don't have the comfort of moving manufacturing to Taiwan like Apple did. We would be happy to replace your device, but how do you do that when half of your workers can't get to work to make the device? It's unfortunate, but the best we can do right now is to patiently wait and help our factory as much as we can. Every startup to medium sized businesses manufacturing in China is affected. As for your messages, I can see a new response to our previous reply was made on Saturday. We know your repair is waiting to be processed, we are not going to forget about it, even if we don't periodically acknowledge it's still with us. Pretty much everything is in hold until the stock is ready, which is what we need to send you a new device :).
  13. 9 points
    Thanks to @Raksura for posting this in another thread, but let me put it here too, for more to see the progress.
  14. 9 points
    today is the day, latest ota fixes all these πŸ™‚
  15. 9 points
  16. 8 points
    On 27-03-2020 12:17 FX Technology Limited wrote: > Hello there! > > We hope you are all well and staying safe at this difficult time. We > just wanted to give you a brief update on the status of your Pro1. > > Over the last week we have really been pushing to try and get remaining > orders completed, however we are still waiting for delivery from our > keyboard supplier which has delayed the process by a few days. We expect > this to arrive at the factory on Saturday 28th March, and from then we > will be able to finalise production units and start preparing for shipping. > > Whilst we appreciate that you were expecting shipping to begin this > week, the travel restrictions in China has slowed everything down so > please bear with us. This has been an extremely difficult couple of > months, not only for us but for many businesses globally which have been > affected by the coronavirus pandemic in one way or another. > > We really do appreciate you sticking by us. Thank you for your ongoing > patience and support. > > Sincerely, > > Team F(x)tec
  17. 8 points
    @sixaxis , you could add a number 8, see mail posted yesterday by @Raksura above. When they say nothing: people are whining When they say something without a when: people are whining When they try to give a vague estimate stating that it is out of their control. people are whining When they tell that the supply lines are working again and production and shipping is expected to be resumed: People are whining too ?!?!? What do you expect them to do in the current situation?
  18. 8 points
    The update is great. The "multiple keys at once" fix has vastly increased my typing speed. Before I couldn't break 40 WPM before I stopped getting dropped keys; now I am 50-60 WPM on a good day. Thank you f(x)tec for fixing this! Before the fix, it was a great phone; now it is stellar.
  19. 8 points
    Not really important, but just asking: Did you buy a new phone to replace your Pro1 just because of broken fingerprint sensor? I mean, if the phone is otherwise perfectly usable, why didn't you use for example a lock code instead? I don't even use my fingerprint sensor (or any lock actually), so I could have swapped devices with you.
  20. 8 points
    A quick update. Received my warranty replacement phone today. It has a different serial number. The stability issues I had before are now gone, so it seems likely that the particular unit I had before was faulty somehow.
  21. 8 points
    Started print this morning, 10h to go still:p
  22. 7 points
    Here goes nothing... https://www.dropbox.com/sh/hffh8qtsljmfa7x/AAAu0ozxcIQ--kZY31nZmA_Ya?dl=0 All photos by me, and I may add more if time permits. That is, if I have anything else that crops okay in portrait and landscape.
  23. 7 points
    Again @Raksura has helped forwarding an update:
  24. 7 points
    Quick update: @EskeRahn I'll add LiveDisplay back for the next build. @auvo.salmi something happened with my DNS and it lost all the IPv6 entries. I have restored them and it should be working again. I asked about gapps persistence in Lineage Slack and the answer was that gapps persistence only works for OTA on A/B devices, not with sideload. This is because nobody has been able to figure out get it working with sideload. So, as you are surely aware by now, gapps needs to be flashed after updating. I'll try to fix this soon. But this won't be a problem after it goes official because updates will be via OTA. I'm currently working on selinux rules. Hopefully it won't take too long to get enforcing mode working. After that is done, there isn't much standing in the way of official builds. Finally, Seattle is in full coronoavirus mode. Kids are out of school for at least two weeks starting today and most people are working remote. I'm not sure how much time I'll have for working on the Pro1 over the next few weeks, so expect my work to slow down for a while.
  25. 7 points
    test11 is up. The only change is fixing FM radio.
  26. 7 points
    I've gotten VLC with OpenSL ES initially working by taking audio_policy_configuration.xml from 1+5/5t. There are quite a few diffs, so I'm narrowing it down now. If you want to try this out yourself and report back, do the following: 1. Remove or rename the directory /vendor/etc/audio. This contains the currently used audio_policy_configuration.xml file. 2. Update /vendor/etc/audio_policy_configuration.xml with this one. I am particularly interested to see if this fixes audio issues in other apps. Note: audio_policy_configuration.xml is search for in /vendor/etc/audio first, then in /vendor/etc. The BSP puts it into /vendor/etc/audio but Lineage (and the Lineage 1+5/5t trees) have it in /vendor/etc. I started by copying the Lineage 1+5/5t and then tossing in the BSP files for the pro1, which is why there are two copies. And this is why it took me forever to figure out a2dp -- I was looking at the wrong file for a couple days. I'll be doing the audio configuration the Lineage way for the next build, hence the instructions above to remove the BSP version. You could also just replace the BSP version instead of deleting it if you wish. But I don't like having two copies of the same file lying around because it's confusing. You know, the old adage about a man with two watches and all. EDIT: The fix is on line 67, removing AUDIO_OUTPUT_FLAG_RAW. This is the only line that needs to change.
  27. 7 points
    Take it apart ASAP and disconnect the battery! First under the stickers on the back of screen there are screws (only under the 5 stickers that are accessible by screwdriver) then take off the screen but careful because you have to disconnect the big ribbon cable while doing that. Then there are 3 screws to take loose the hinge parts, then the whole screen side part of the phone should come off and reveal more stickers under which are screws (also two corners of the keyboard have stickers), after taking thouse out you should be able to remove the top of the keyboard part including the keyboard, then 3 screws and a metal bracket that hold a bunch of the connectors (be careful not to drop these screws on the board) and be able to disconnect the battery. It's also described in this PDF but do not remove the whole key mat like it shows, on production units only the corner stickers of the keyboard should be removed and no need to use heat gun at all with taking off the screen n all. If you are willing take photos of the damage if visible and show us, also if you are within the EU and it isn't totally drowned I may be willing to buy it from you if price is fair. edit: in my haste forgot to say, my sincere condolances 😞 I hope you can get it back alive or replaced edit2: forgot to tell about metal bracket, edited instructions
  28. 7 points
    So now key-chording/rollover works in Sailfish, Lineage, and finally stock with yesterdays OTA! I want my game gripper πŸ˜‰
  29. 7 points
    they pulled my version of the keyboard driver, the issue should be well and truely gone along with randomly missing keys and now multiple simultaneous keys should work too πŸ™‚
  30. 7 points
    test9 is up. Changes: * Fix notification light. * Fix WiFi signal strength indicator. * Add fingerprint mitigations. Notes: The vibrator seems to work but I am seeing errors in the log. Please let me know if it works or not. Either way I will be looking into fixing the errors. The fingerprint backoff defaults to 2 seconds per attempt. This can be controlled via these properties: persist.vendor.fingerprint.auth_delay: the auth delay in seconds, defaults to 2. persist.vendor.fingerprint.auth_backoff: whether to backoff between attempts, defaults to 0 (off). When backoff is enabled, delay is multiplied by the number of failed attempts. eg. 2 seconds for first fail, 4 for second, 6 for third, etc. I'll add these into the settings app for next build.
  31. 6 points
    As an update, I chartered a private jet for my mom. She is back home in the Chicago suburbs, safely tucked into her house 3 blocks away from me, Safe and sound.
  32. 6 points
    Yesterday I had two spontaneous reboots while having a call. I was working on my garage, and had working gloves on. First time I really thought that the device rebooted spontaneously, and the second time I was ready to throw the device towards concrete wall... But then I realized that I had accidentally long-pressed the power button on both of times and this caused the reboot πŸ˜„
  33. 6 points
  34. 6 points
    I used Fusion360: Printed on a Prusa I3 mk3:
  35. 6 points
    My initial AOKP build won't boot. I swear, this device has given me trouble every single step of the way. I've never seen any device cause more trouble in my 6 years of doing custom ROMs.
  36. 6 points
    Today my country (United States) and State (Michigan) have basically cancelled EVERYTHING. International shipping, public events, school....you name it, it's cancelled. First it was masks, and now people are hoarding toilet paper, of all things....you can't find it on store shelves now. Coronavirus. With the panic that this virus has created, you'd think it was like rabies where no one survives, and we were facing mass extinction. Personally, I think that it's becoming increasingly obvious that this will not be remembered as a major medical catastrophe, but as a major PSYCHOLOGICAL catastrophe. THIS IS A COLD. Why are we stopping the world over a COLD? People get colds. People who are feeble occasionally die from themβ€”or more accurately, from complications during them. This is not new, nor is the fact that from time to time a particular strain will be a little more virulent than others and get a little extra attention. However, the mass panic that is being created deliberately by the talking heads is beyond comprehension. I think a lot of people genuinely believe that this is like bubonic plague, and half the population of the known world is going to die. I know I don't want to live on this planet anymore. People have lost their minds.
  37. 6 points
    Lineage does not have gapps, so an official Lineage build could not be used for stock. It would be technically possible to build Lineage with the approved gapps for a stock replacement, but this would violate the contract with Google. Unfortunately, IdeaLTE is a hardware manufacturer and FxTec is too small to have a software team. So the current situation where stock is a basic no-frills system while Lineage is a much nicer alternative will surely persist for quite some time.
  38. 6 points
    I have edit the 3d case that Was made by hka to fit my specs i printed it with pla and made the holes a bit bigger and the outer Walls thicker Here is the stl file pro1-v8-PLA.stl
  39. 6 points
    I just want to say that I laugh every time I see the title of this thread. The struggle is real but we are the chosen, poised to inherit the physical keyboard and carry the torch into the new millenium of VR and smartwatches.
  40. 6 points
    As usual, TDM is Tom Da MAN!!! πŸ™‚ In all seriousness though, there really aren't enough nice things to say about what you've done here. You've almost singlehandedly made a great piece of hardware with terrible software a great piece of hardware with great software to match! I certainly hope that the IdioticLTE people take some hints from your work, for the sake of the device's reputation. Bravo, sir! We salute you!
  41. 6 points
    The advantage of official lineage is that you get automated nightly builds with the current code. That's not such a big deal for 16.0 since it's in de-facto maintenance mode, but it will be really nice for 17.1. It also means that more people will see it and use it, since not everyone reads this forum. The big advantage to AOKP has always been more options over Lineage. And there's also unicorns and swagger, naturally. πŸ™‚ Yes, AOKP is probably past its prime, but I've a particular fondness for it. I've been using it for about 8 years and developing it for about 6. I worked with its creator, Roman Birg, at Cyanogen, and I'm currently the main AOKP admin. And yes it was on Oreo for far too long but Pie is stable and running fine (using it on my 1+6t actually).
  42. 6 points
    @tdm Finally had some success with the audio. Since the problem appears only when deep buffering is being used, disabling it from the audio config policy seems to resolve it. Here's the changes: diff --git a/audio/audio_output_policy.conf b/audio/audio_output_policy.conf index 4719b66..eb932be 100644 --- a/audio/audio_output_policy.conf +++ b/audio/audio_output_policy.conf @@ -26,7 +26,7 @@ outputs { app_type 69943 } deep_buffer { - flags AUDIO_OUTPUT_FLAG_DEEP_BUFFER + flags AUDIO_OUTPUT_FLAG_NONE formats AUDIO_FORMAT_PCM_16_BIT sampling_rates 48000 bit_width 16 diff --git a/audio/audio_policy_configuration.xml b/audio/audio_policy_configuration.xml index 20b00c2..bbf0e0f 100644 --- a/audio/audio_policy_configuration.xml +++ b/audio/audio_policy_configuration.xml @@ -61,7 +61,7 @@ samplingRates="48000" channelMasks="AUDIO_CHANNEL_OUT_STEREO"/> </mixPort> <mixPort name="deep_buffer" role="source" - flags="AUDIO_OUTPUT_FLAG_DEEP_BUFFER"> + flags="AUDIO_OUTPUT_FLAG_NONE"> <profile name="" format="AUDIO_FORMAT_PCM_24_BIT_PACKED" samplingRates="48000" channelMasks="AUDIO_CHANNEL_OUT_STEREO"/> </mixPort> I don't know what other effects this could have but so far seems to be working fine here. If anyone else wants to try it out, here's a new signed Vendor image to flash from fastboot.
  43. 6 points
    Perfect, thanks. Installed VLC and set it to OpenSL ES. mp3 playback is crackling. Will investigate. I haven't used my device much yet. Still need to get my carrier to figure out the voice call issue.
  44. 6 points
    Maybe you were matched with other people on smartphone but the keyboard gave you an edge over them?
  45. 6 points
    I just tried PUBG first Time and won. There must be some magic on Pro1.
  46. 6 points
    THE OTA have been Temporarily suspended, as it had a bug breaking the "SafetyNet", fix should be on it's way quickly.
  47. 6 points
    It worked. OTA info screen: I then went into Magisk Manager and uninstalled it, telling it to restore the previous image. Next, started the download for the OTA: One interesting thing was that it automatically started installing after the download. I thought in the past that it gave you an option tap something to start the install after the download was done, but I could be mistaken about that. This means it is important to uninstall Magisk before even starting the download. It also showed 100% complete immediately after the download was complete and the installation started. However, there was a notification for the install, so I tapped on that and then got this screen: After a while, without any progress bar change, that changed to: Be very careful at this point. You aren't just responding "OK" to the message. If you tap "OK", it will restart the phone. I'm guessing "CANCEL" will not restart the phone, but I didn't test that. At this point, without tapping either button, I went back into Magisk Manager and told it to install Magisk, picking the "Install to Inactive Slot (After OTA)" option. It then did the Magisk install over the top of the OTA, in the inactive slot, backing up the boot image first, so that it is ready to do this whole process again with the next OTA: I then went back into the OTA screen and tapped "OK", causing it to reboot. That could have been done in the Magisk Manager screen with the yellow Reboot button or I could have manually done it with the power button. The method of reboot shouldn't matter at this point. After rebooting: And root was maintained, which is the whole point of this exercise. NOTE: You have to originally achieve root in the proper way for this method to work. And that proper way is for Magisk Manager to be given a non-patched boot image file that is identical to the one you are currently using. It will make a backup of that file (for later use in the OTA process) and will also create a patched version of that file. You then copy that patched file to your PC and use fastboot to flash it. (https://android.gadgethacks.com/how-to/make-ota-updates-easy-by-rooting-your-pixel-3-with-magisks-boot-image-patch-0189139/) If you don't go through the proper steps to acquire root with Magisk Manager, then you won't be able to use the Magisk Manager features to survive the next OTA update. SUB-NOTE: Technically there is a way to hack it and give Magisk Manager a backup boot image that it didn't backup itself, but I haven't tried that. https://forum.xda-developers.com/pixel-4-xl/how-to/guide-alternative-method-applying-ota-t4023175 If you attempt this, there has been a change to where Magisk Manager stores its backup images now. They are now at /data/magisk_backup_(hash)/boot.img.gz instead of having the .gz file right in /data. Also read the comments about changing the recoverymode variable in the config file to false if it is true. If anyone is in a phone state where they don't have root and have the 20200304 firmware on their phone, and they want to root it, let me know and I can upload the boot image for the 20200304 firmware so that you can have Magisk Manager patch it, etc.
  48. 6 points
    THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU!
  49. 6 points
  50. 6 points
    All parts test printed, I will do some adjustments tomorrow and post the design πŸ˜ƒ Then I will try and print it in one piece during the weekend. Th msla I am using is just so slow, to print it in one piece I need to print it standing and it takes about 1h/cm.
×
×
  • Create New...

Important Information

Terms