Jump to content

VaZso

Members
 View Profile  See their activity

  • Content Count

    1,633

  • Joined

  • Last visited

  • Days Won

    105

 Content Type 

Everything posted by VaZso

  1. VaZso
    I think this is about the "bare metal" screen alone vs. complete screen assembly. F(x)tec sends a full display assembly including the camera and proximity sensor while we may purchase the display alone and swap the faulty and new displays on the frame which contains the camera and proximity sensors. Anyway, it also contains a black sticky grid in front of the speaker which should be removed from old display and installed to the new one. As of the non-functioning proximity sensor, it can be a sensor fault but if I remember well, there is also a rubber cover installed on that sens
  2. VaZso
    I am completely gave up using stock OS, going for LineageOS is a better option instead. Also, it has Android 11 support...
  3. VaZso

    Duplicated keys

    VaZso replied to ivoanjo's topic in Support

    Right, the new driver should has less issue. Anyway, I also experience this under LineageOS 18.1, maybe mostly 'n' key what appears for me as "ghost" key on my QWERTZ layout, I think that is 'b' on shifted QWERTY.
  4. VaZso
    About call quality... one of my friends told me the in-call quality is worse since I am using LineageOS after stock. I may try it later using another phone under LineageOS and stock again but he showed me it is very noisy (background noise "hiss?") even if we are speaking on my primary and secondary phone number. It is very significant together with his latest phone while it feels better on his older phone but it can be heard on both phones while these phones can call each other without any similar noises. It would be good to find out if microphone issue can be solved somehow...
  5. VaZso
    ...as far as I know, theoretically Pro1 supports PD but I don't know if it really supports it. Anyway, SD835 supports QC4 which has PD support and also F(x)tec shows PD under technical details of Pro1. So it may happen also power limit works if it does not have a fallback option for QC which allows higher power.
  6. VaZso
    Confirmed on LOS 18.1 I usually disable NFC when not in use anyway.
  7. VaZso
    @AngledLuffa and @saygi, You may want to look in the following thread: ...or most likely in this thread: I think the latter (Factory Restore Tool) would be interesting for you, but I have a feeling it will not help. My friend had a similar problem of his Pro1 maybe a year ago (or more) which has started the same way and ended up with a factory replacement device. Flash tool could reach the device, but it has failed reaching its internal flash storage, most likely UFS flash IC became dead in his case. (So, it was either a soldering problem or IC fault but the result
  8. VaZso
    Right, it would be good to have an option to put images in native resolution at least in this specific thread as it would show the full potential of Pro1's camera. Even more, if Pro1-X will arrive, it will produce even larger photos and it's quality will be really interesting, so it would be good to find a solution for that. Anyway, we don't know what amount of free space does the server have or if they want to extend it or what options they have for storage extension. ...basically the problem is the limits of storage itself and that is why owner's decision is necessary...
  9. VaZso
    Same here. Anyway, e-mail is generally not the most reliable form of communication, so anything may happen with it... Fortunately, this forum has also warns the user from another user. 😄
  10. VaZso
    You may also want look at the latest update of their IGG campaign sent out almost an hour ago. It seems they have some working units (potentially good for development even if its mainboard has an earlier version), a potential last iteration of V3 main board, then an ongoing CE/FCC certification (it should be done using the final mainboard iteration) and mass production then. They currently estimate shipping in November which is potentially the end of the month and that will mean if they are right, they will serve their pending orders first near the beginning of December. So I would
  11. VaZso
    I think "\" it is the AltGr section of "-" as per US keyboard and "|" is the AltGr section of the key left to "ZXC". Also, the key "\|" exists on that layout (left to ZXC) but there is a different print on it (<,>,|) - also, the potential right position of "\|" key has the text of (*,'). So yes, these two keys have different scancodes (like what I have remembered) but US layout produces "\" and international layouts may use them for their own purposes - but those keys are definitively not "` and ~".
  12. VaZso
    The places where I saw "\" character are: The right of a small backspace above big enter The right of "right shift" below big enter in a place where turbo was placed in later keyboard models (to reach power / sleep / wake functions) Above right shift but left of big enter Above small enter and below backspace (between them) The left of ZXC keys Maybe there was also a layout where "\" was placed between CTRL and ALT keys or a similar position So its placement is not constant at all. However, if there is a button between left shift and ZXC keys, it is de
  13. VaZso
    +1, that would be a much better key placement. I will definitively use backslash at the bottom-left corner regardless of the print but that is a right place for it and none of the positions of back- apostrophe key is perfect (that would be the position of ESC), so placing it below backspace is a valid option. I would also live without that key but in my national layout, that button is "0" anyway, so it is definitively used by at least one international layout.
  14. VaZso
    Yes, with F(x) + A but it is not the latest LineageOS (but an official one).
  15. VaZso
    Right, that is what I wanted to write here. Anyway, it could open calculator for me although it is not in that list.
  16. VaZso
    Anyway, I had a problem with Button Mapper on stock Android of Pro1 as it caused lag on my hardware keyboard and a feeling it is not fluent which was solved by removing it...
  17. VaZso
    Yes, that is why I would put "\" to the lower-left position and I am also currently using it there. I never thought they would move ~ key to that position. 😞
  18. VaZso
    Oops, I haven't looked this deeply but you are right. I am agree with that, "\" is at a very wrong position. It may be an option, but another right position for that key is the "`/~" button which should be on the left of '1'. So, I would put "\" key on the "`~" key. That key is absolutely a nonsense being there. I am absolutely and definitively against it - apart that key is handled a bit differently, it is very important for custom layouts, so should not be eliminated.
  19. VaZso
    Right - anyway, for the keyboard itself, the most convenient way of working would be for me: Two slant arrows could be used freely for my custom layout (defined in .kcm file) Original AltGr function of the selected international layout could be reachable for example by "Alt" button Additional yellow characters would be accessible by another modifier like the "Sym" button. Maybe another modifier would be usable to quick-launch applications like the "F(x)" button For the functions above, an additional modifier like FN or Meta would be needed. Quick launch may be pos
  20. VaZso
    Yes, this is a 2-in-1 problem. The first one is the different keymap of shifted (QWERTY) and normal (QWERTZ) variants of keyboards we have. It is a bit strange that F(x)tec itself has generated this issue as otherwise these layouts would work exactly the same way deep inside. So the problem is the shifting itself which made default layout of Pro1 to be unusual while QWERTZ variant is a perfectly usual layout. So @tdm's keyboard driver solved this issue by allowing to map appropriate keycodes to shifted keys respective to its written functions while also maps appropriate keycod
  21. VaZso
    I haven't noticed this issue on my phone either. I also have GSM battery manager and 3C all-in-one Toolbox installed and this is an early Pro1 if that matters.
  22. VaZso
    I have also connected a 3.5mm headset which has both speakers and microphone. Anyway, I also have this clicking noise, so that is also not perfect. I don't know where this problem comes from and what does noise filtering under Android. I would think it should not be placed in low-level driver but it may happen it is a 3rd-party thing... however, it is very annoying. Practically the inability to record a video as one would expect from any phones is a really big fault from day 1.
  23. VaZso
    Right, recording music has a result of really bad sound and also I have experienced the same using basically any casual video recordings - sound is practically unusable, the worst I have ever heard on any phones for sound recording. 😄 I have also tried it and although selecting "unprocessed input" worked for me using my Moto G6 phone, it seemed worth nothing on my Pro1. Anyway, currently OpenCamera can't even record any videos even on SDCard or local storage, always an empty video file is created. I don't know if it has something to do with Android 11 or I have something
  24. VaZso
    It may happen as it was sold by Telekom Hungary which belongs to Deutche Telekom, so it is possible this software upgrade may be related to Telekom, however, I find it strange that retail units did not get it...
  25. VaZso
    That is also the same for me anyway (35) which should be Comreg / Ireland. Anyway, Pro1 is 99 which is GHA / For multi RAT 3GPP2/3GPP So we are not closer to the reason... Anyway, my phone for software variant / software channel (they may have other names) displays "dteu". Also, it's software version is PPSS29.55-37-7-10 from 2020. April 1. (perfect date 🙂)
×
×
  • Create New...

Important Information

Terms

  I accept