xhajt03

??? If this was supposed to be an answer to my questions, then I don't understand it (actually, I don't understand it in either case, but maybe others would).

I understand that I'm lucky compared to others (since I received my FxTec Pro1x rather long time ago), but although the report states that accessories were shipped as well, I ordered a spare battery through the Indiegogo campaign and received nothing (neither the ordered battery, nor anything else - I believe that someone mentioned a plan to delivery earphones instead of batteries due to unusability of batteries after long time spent in stock, but I received simply nothing). If I receive no battery this way (which I suspect to be the case 😕 ), I wonder if there's any chance to get a new b

Well, that's funny. 😕 If I understand it correctly, you get results confirming supposedly higher level of compliance ("integrity") with an alternative OS than with the standard Android as delivered by the device producer? Do I assume correctly that this "Play Integrity Fix" cannot be installed on regular Android (at least not without rooting the device)?

OK, i.e. the same result I have. 😕 Thus it's indeed likely that I may need to lock it (I didn't unlock it, but it was probably shipped unlocked). Thanks for the links, I'm aware of the manual, but I understand that there may be additional information to this discussed on the forum.

OK, thanks. Still - could you please check the results of the small application from Google Play mentioned above on your device? Regarding "...I forgot to lock it before setting everything up" - do you mean that locking it afterwards couldn't be done / would have the wanted effects any longer?

Hello, Since about 3 weeks ago, I started having an issue with using applications in my "work profile" on my Pro1x device (e.g. using MS Outlook to access my work e-mails - I work in an enterprise environment). This turned out to be due to one of Google APIs used to check "device integrity" apparently started to result in a failure. Unfortunately, no details are available regarding the reasons of that failure. Before proceeding to e.g. FxTec support, I'd like to know if the issue is common on other Pro1x devices as well, or whether it may be e.g. due to some configuration or application

Unfortunately, I don't get any events generated when touching the sensor. 😞 The list of input devices is more or less the same: QX1050:/ $ getevent add device 1: /dev/input/event6 name: "bengal-idp-snd-card Button Jack" add device 2: /dev/input/event5 name: "bengal-idp-snd-card Headset Jack" add device 3: /dev/input/event0 name: "qpnp_pon" add device 4: /dev/input/event1 name: "goodix-ts" add device 5: /dev/input/event4 name: "madev" add device 6: /dev/input/event2 name: "gpio-keys" add device 7: /dev/input/event3 name: "Fxtec Pro1"

Well, "for Tmobile"... 😉 I assume you mean TMUS, right? It's just that my network is also T-Mobile (Czech Republic) - obviously, there's nothing in common between the two from the technology point of view (not more common than any two random mobile network operators anyway), it's just funny that U.S. people believe that "Tmobile" is clear and unique distinction. 😉

I decided to post my fingerprint sensor related issues / findings (Pro1x with standard Android, not rooted): At the beginning, I observed the same behaviour as described above for Pro1 - the fingerprint sensor stopped working after some time and only phone restart helped. After some time it happened to me that restarting didn't help any longer. To my surprise, I found out that my previously registered fingerprints disappeared from the system settings as if I'd never initialized them. After teaching my Pro1x to recognize them again, it continued to work more or less the same way as

No, the VoLTE setting was not off originally, I turned it off explicitly after I discovered that having it enabled led to worse phone call quality. I can enable it again, but I don't want to do that with this firmware version. I'm not attaching a screenshot because the Czech messages wouldn't be useful for majority of forum users - just believe me, please. 😉 Mobile voice network type and Mobile data network type both show "LTE".

I'm sorry, but I don't see the band there, it states "LTE band unknown". It also says "Active connections (0)" and "N/A" for all of "DL EARFCN", "UL EARFCN", "DL Freq" and "UL Freq". The "Cell bandwidth (kilohertz)" value seems to be -1 converted to an unsigned 32-bit number. I don't know if there's anything useful in the Advanced data section, but I doubt it - apart from MNC/MCC, etc., I see only "Channel number" (6200), "Data network type" (13) and "Radio technology type" (14 - apparently meaning LTE).

I'm sorry, but the free version doesn't seem to provide this information. Regardless of what the price of the paid version is, I'm not willing to provide my credit card information to Google (Play/Pay) and I suspect that there's no other way to get the full version even if I'd want to pay for it (feel free to consider me paranoid 😉 ).

I don't see much useful information in Network Monitor either - there is information like Cell Signal Strength and LTE RSRQ, but columns like LTE Cell RF Channel (not even mentioning LTE Cell Id) are empty... Regarding Preferred network type - I allow the last/widest option (NR/LTE/TDSCDMA/CDMA/EvDo/GSM/WCDMA); obviously, some of these technologies are not available here, but that shouldn't matter. Regarding Serial No. - do you mean IMEI (in my case ending 137664 for SIM slot 1 and 168669 for SIM slot 2)?

First of all - as already discussed earlier in this thread, I disable VoLTE in my configuration (and enabled voice over Wifi only as the last resort if not mobile network is available) because it led to lower voice quality. I understand that this option may not be usable for people in locations/carriers not providing other network options for voice calls, but that's what works best for me. As far as LTE Discovery app is concerned - I installed it (the basic free version, i.e. no Pro). Note that my phone is not rooted (and I'm not willing to change that because it would limit usability of

As far as the GSM protocols, etc., are concerned - I may be wrong, but I believe that this area is nowadays covered by the phone chip rather than the phone firmware. The chip isn't specific for Pro1x. In other words, it doesn't seem to be likely that the issue with radio communication observed by some Pro1x users should be related to missing part of a GSM communication protocol. Yes, it may be related to a particular configuration for the device which influences the behaviour of the on-chip implementation, or it may be related to some hardware issues (antenna), or possibly other factors, but i