Jump to content

EvilDragon

Members
 View Profile  See their activity

  • Content Count

    63

  • Joined

  • Last visited

  • Days Won

    3

 Content Type 

Posts posted by EvilDragon

    Having problems contacting Fxtec support

    in Support

    Posted

    On 7/18/2021 at 9:22 PM, Rob. S. said:

    I can't believe it, another screen broken – I just tried to swipe a fly from the display, and what I did was swiping the phone from the table, because the EFFING SCREEN PROTECTOR I'm now using since my last accident is sticky to the touch!

    So it's back to @EvilDragon's repair service...

    Oh, dear... I had multiple broken screens myself until I modified a case... this worked so good that the screen never broke again, even though I regularly throw it on the ground.
    I don't have a screen protector.

    This is the case I use:
    https://www.amazon.de/gp/product/B07BQQ8JCC/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1

    You only need to cut out the credit card storage case that's inside the case (then it has the perfect size for the thickness of the phone) and cut a few holes in the silicone so you can access all ports.

     

    • Like 2
    • Thanks 2

    AICP Q: Discussion

    in General Discussion

    Posted

    On 3/15/2021 at 3:38 AM, VaZso said:

    Instead of slow appearing of incoming call screen I had, incoming call screen does not come up, but if I press power button, lock screen appears together with a message of continue call, and after clicking on it, incoming call screen appears and I can pick it up

    I am having that issue as well - and it drives me insane. On lineage OS, the call screen appeared, I could see who's calling and pick up the phone without any issues.

    On AICP, most of the times the screen stays black and I need to press the power button to make it appear. If I press the power button too long, the camera comes up without any way going back to the call screen... I missed quite a few calls because of that even though I had the phone right in front of me...

    Does anyone know how to fix that? Maybe it's a setting? 

    Otherwise, I hope AICP R won't be too far away and maybe fix that issue.

    AICP Q: Discussion

    in General Discussion

    Posted

    I noticed one issue, but I'm not sure if that's an easy one to fix as it seems to be common with other Android versions as well:

    The microphone of a Bluetooth headset only works for phone calls.
    Whenever you use some other app (audio recorder, WhatsApp, Skype, etc.), the microphone is not available - it only works with normal phone calls.

    There's an app called "Lesser AudioSwitch" which can force the apps to use the bluetooth microphone - but it's a bit flakey (doesn't work all the time) and it seems to switch back to internal speakers as soon as the microphone is enabled.

    It's a mess, as you can't use bluetooth headsets for audio conferencing...

    Does anyone know more about this and is this fixing in Android?

    It sounds like it needs some different routings / settings in the audio manager... so maybe can be fixed with an update 🙂

     

    Display units with large tap-insensitive margin

    in General Discussion

    Posted

    Just now, VaZso said:

    So, if I understand well, it is really a modified touchscreen driver.

    That means they may also include it in newer systems (like when they upgrade to Android 10) and also Lineage OS may use the other driver as well.

    Anyway, does this modified touch screen driver backwards compatible with "old" displays?
    That would be mandatory for the above.

    Also, do these instructions break SafetyNet or such things in (stock) Android?

    I'm not sure if it's for newer systems, as the driver is dated from 2019. Maybe it was too sensitive for the screens they got while it works fine with the ones that have a bit more insensitive edges?

    I don't have an older display here so I can't test right now if it still works. It probably works but might react even more to edge taps than the current one.
    Probably not a problem if you're using LineageOS or AICP, as there you can set you own margin, but that's just my guess.

    I'm not using stock, but I don't think it will break SafetyNet. To me it sounds like it's installed inside the touchscreen driver firmware - it's not related to any OS.
    Because once the firmware has been flashed, you can install or reinstall any OS and the driver won't change.

    • Like 1
    • Thanks 1

    Display units with large tap-insensitive margin

    in General Discussion

    Posted

    On 11/12/2020 at 7:17 PM, dt.white said:

    @EvilDragon take a look at this comment and the video I uploaded in the comment after it - I think it may be similar to what you say you're experiencing? This was purely a hardware issue with that particular screen replacement - the next one I got was much better.

    Thanks - the screen was fine. I had 20 of those, so I could test a few 😉

    But an update:
    A fellow member sent me the instructions and files he received from F(X)Tec - and it worked fine!

    And the best thing is:
    It's really painless if you have a rooted OS. No debug firmware needed, no reflash, no wiping of data.

    Just one single APK, a firmware file and access via adb to change some permissions for the touchscreen driver files.

    So if anyone has the same issues: With a rooted OS, it takes 2 minutes to fix it 😄

    • Like 3
    • Thanks 2

    Cracked screen ticket #6975

    in Support

    Posted

    6 hours ago, benoitjeffrey said:

    I had a 24h wait for a complete reply on how to do it at mid september, I don't think it got much worst actually.

    I don't think you'll be able to do the driver update without a full reflash because they use a debug OS for this to work.

    Well, I did send them my email over a week ago 😄

    So yeah... not that fast 😕

    But thanks, I'll try the support section as well.

    • Confused 1

    Cracked screen ticket #6975

    in Support

    Posted

    6 hours ago, _DW_ said:

    does the screen have any model or revision numbers on it? (its sometime on the circuit board)

    Unfortunately not. They look exactly the same, the silk on the PCBs is also the same.

    They have different batch codes on them, but that's pretty normal.

    Display units with large tap-insensitive margin

    in General Discussion

    Posted

    1 hour ago, EskeRahn said:

    I know they changed 'something' at a deep level to add a small margin at a very early stage, so I guess what you describe is that newer displays comes with a much wider default tap-insensitive edge (that still allows sliding so not touch insensitive).

    I have no idea if this can be changed without wiping everything. But as it seems to follow the hardware I guess it ought to be possible - though I got no idea on the how we can flash individual hardware components.

    I don't have a problem wiping everything, though it would be weird, as the driver should sit on one of the internal partitions and you should be able to reflash that one without touching the others.

    The bigger problem seems to be to find out what's wrong and how to get the fix 🙂

    Display units with large tap-insensitive margin

    in General Discussion

    Posted

    7 hours ago, tdm said:

     

    Sorry I am not familiar with the hardware on this level.  It is possible that the new screen is different in some subtle way.  Or perhaps it is possible you got a defective screen.  I know others have changed screens without any apparent issues.

     

    Well, it's not a single screen, it would be a batch of screens. The ones I bought in March worked fine - but the new batch I recently bought has that issue. All of them, so it's not just one that is defective.

    Seems like this is a new revision - and the distributor told me it works fine on the Elephone U Pro.

    1 hour ago, fxtec-preorder-47xx said:

    I have exactly the same issue. I changed the screen before and everything was fine. Then, after the next drop, I changed the screen again and got the described behavior.

     

    (I am thinking about a big rubber protector around the edge to protect the screen from cracking, now that I cannot use touch in the edge anyway. 😉)

    That seems to confirm that more recent batches have that behaviour. Maybe the screen was updated as it was oversensitive at the edges and that's now on top of the Pro1 own driver code to make it less sensitive.

    About dropping: I'm using a slightly modified leather case from Mulbess. fits perfectly, you can pull out and use the keyboard without removing the phone and all, ports as well as the fingerprint reader work fine.

    Hasn't cracked since then, and I'm regularly dropping it.

    • Haha 1

    Display units with large tap-insensitive margin

    in General Discussion

    Posted

    1 minute ago, EskeRahn said:

    Is this not a deliberate fix for people to avoid unwanted edge interaction? If I do not remember wrong the lineage implementation have a setting for the size of this....

    I would be happy if it would be just that 😄

    However, the edge is way too far in here. I can't even press the record button on What's App anymore.

    With the old screen, I had margin set to the middle setting which was perfect. Here, even on setting 0 it still does not react on about 7 - 8mm at the edge of the screen.

    I can make a video to show this.
    As soon as I connect an original screen, the issue is gone. So I do know that it's a hardware change in the new screens I have, though they look identical (even the electronic parts and silk on the FPCs are the same).

    • Thanks 3
×
×
  • Create New...

Important Information

Terms

  I accept