claude0001

I fixed similar problems (in Germany) years ago by having the following changes in /system/vendor/etc/gps.conf: [...] XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin [...] XTRA_VERSION_CHECK=1 [...] NTP_SERVER=europe.pool.ntp.org [...] INTERMEDIATE_POS=1 [..] SUPL_HOST=supl.vodafone.com SUPL_PORT=7275 [...] since then, GPS has been working quite OK for me (I have no Gapps on my Pro1). Changing that file in LOS 20 probably involves Magisk scripting, which I unfortunately have no

I confirm that installing Lineage on Pro1-X breaks offline-charging-mode. I had that enabled and working successfully on 2.1.5-GMSless, but never checked after installing LineageOS. I am not on one of the official builds, but on one of the betas from few weeks ago. After reading this, I tried to charge my Pro1-X (shelved for several months) and it seems to be bricked. Upon connecting the charger it briefly blinks red, but then nothing. Previously (with 2.1.5.-GMSless) it would charge (while displaying the "battery screen"). Well ... what to complain about with such a broken device ..

No offence, but, in your report, you are doing precisely that: whitewash a faulty device. Your LTE-router workaround is technically interesting, but it doesn't mitigate the Pro1-X's failure as a mobile phone.

I agree that the Pro1-X's keyboard is better than the Pro1's. But, yes, for me the whole point with the Pro1/Pro1-X is to carry around only the one device I need anyway - my phone. A single device that works as a normal Android slab most of the time but can transform into an UMPC if I urgently need to get some stuff done while away from a real workstation. If I were to settle for carrying two pocket-sized devices all the time, I'd probably choose something else than a Pro1/X as the "computer". I think there are far more capable miniature laptops. But, honestly, I think this discussio

Forget it. People from all over the world have been reporting those network problems for 8 months now. At one point @Casey even acknowledged that this is one of the most reported issues. Still, they haven't come up with even a glimpse of a solution. I think the two most likely explanations are: 1) Something is systematically wrong with the qx1050's RF hardware, causing it to fail in many regions/networks. 2) There are a lot of defective devices around, as @Rob. S. suggests. Either way, f(x)tec will not have the (financial) means to fix all those devices. All they can do is keep affected c

The unofficial builds of LOS have been available for some time. While it is great that they are now to become official, for me, they unfortunately never made any difference with regard to mobile connectivity. Note that does not necessarily mean its hardware issues. LOS has to use the closed-source driver blobs from stock firmware as-is. If the bugs are in there, they couldn't fix them even if they wanted.

Sorry, but this does not make sense to me. For me, this entire discussion started with you trying to fix a broken build of AICP precisely without recompiling its source (as others would have done). Rather, you tried to substitute-in the boot partition from another build in binary form, hoping that would magically fix things. Do you personally know the AICP developers? For the Pro1? I do not think so. You simply trust that project because it's open-source and others trust it. That "toss-salt-over-your-shoulder-and-hope" approach is quite common. And we both use it. Strangely, that seems to

Eske, I usually wouldn't care. But as you are a moderator on this forum, I would really like to know how I deserve this kind of hostile response to (what I intended to be) a helpful post. I linked to the github main pages of those two projects. They provide project descriptions, source-code (as you noticed), how-tos, instructional videos, and official (not "random") downloads of binaries from their release branches. I think that is a pretty transparent and widely accepted way to link to an external open-source project. None of the *.exe's need to be "installed" by the way - they run right

So why then make fun of my proposal and wrongly suggest it requires you to install a GO interpreter? (Something I am not sure even exists, I believe GO is meant to be a compiled language.)

Did you even follow the links I posted?! Both of them give you portable Windows *.exe's (along with builds for other OS) that just run on any random box. No one expects you to compile the code yourself. When I say "no dependencies whatsoever", I mean it. Was actually trying to help ... 🙄

😄 ... as I already hinted above, you could have avoided python and git -- and thus most of those tedious steps -- by using one of the standalone extractor tools I linked to above: I just tested payload-dumper-go. It works well and has no dependencies whatsoever.

True. However, the reports of connectivity failure are so widespread, both in time and location, that I suspect something is just designed too much on-the-edge with the Pro1-X's RF system. Meanwhile, I must admit that I find the "cannot reproduce" attitude of F(x)tec on the topic increasingly hard to believe. As @jakfish suggested, they could just fly a dev with a handful devices (from different batches) to one of the reported areas and test away. As you write, one possible reason they do not do this is money. Then again: if they cannot afford a boarding pass to the US or continental Euro

Dear @Hook and @jakfish, Thanks for sharing the outcome of your investigations. It is intriguing that you get better results with GSM telephony. With my German carrier (O2), I have never been able to place or receive a call on GSM. Only VoLTE will work in the few places where the underlying LTE connection can actually be established. Note that this is not a restriction of my provider: I use and prefer GSM for calls all the time with the Pro1. What is different in our two cases is that US T-Mobile uses the 1.9 GHz band for GSM, while my O2 Germany relies on 900 MHz for that. Also, I o

Your aversion to python is obviously still going strong. 😄 Can't really understand why, but then, I'm into scientific computing where there has hardly been a way around that language for 15 years or so ... That being said, there are standalone payload extractors, like this one or that one. I haven't tested them though, as I have a lineage build environment anyway, which includes the official 'extract.py' tool.

Found my report from a month ago: To repeat: I think I have seen the Pro1-X switch between LTE bands 3 and 1 without dropping dead. Band 20 seems to be the problem for me.

Unfortunately doesn't help. As (I think) I wrote previously, band 20 does not work, even if I enable the modem (or boot the Pro1-X) in that "zone" of my apartment. It will then directly go to the "no service" state.

According to my research, T-Mobile US uses several "long-range" LTE bands (5, 12 and 71), all below 1 GHz (though not identical to my band 20). We'll see what happens ... 👍

This doesn't change anything for me (nor all the other "preferred modes" I have tried). I have a pretty constant behaviour in all the tests I have made: 1) At one end of my apartment, the Pro1-X works acceptably. It uses LTE band 3 (1840 MHz) in that spot. Mobile data is fine. Phone calls go in and out, though only via VoLTE (in principle, my carrier supports GSM calls and I use those exclusively with the Pro1). 2) When I move to the other side of the house (~ 10 m), the Pro1-X switches to LTE band 20 (800 MHz), and all connections stall, even though the signal strength is displ

The latest build of LineageOS 16.0 (for SD835-Pro1 only) is available at https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1. Go for the ROM dated 201230326. It includes backported ASB fixes up to 5 March 2023. As for the last months, there is no upstream code review any more. I can confirm that there are no problems on my own Pro1. Beyond the ASB, there are no changes since last month. My full list of increments with respect to the upstream LOS 16.0 tree can be downloaded for reference. Have fun.

I agree. I am in the lucky position to own an original Pro1 that is unaffected by all these issues. It shows that F(x)tec can make functional phones, just to emphasize that here once more. One thing @Michael074 could do is join their beta testing programme and provide debug-info to them. I haven't done so yet because my Pro1-X is already on LineageOS. Also, I admittedly have too much other fish to fry right now and cannot routinely carry a second smartphone along just to study its field-behaviour. That being said, admittedly, even with all necessary debugging info provided, I no lon

That's a very similar symptom I observe often: Apparently, there is a signal, but calls can't get in or out, and finally the phone "gives up" and you get the "no network" message. Unfortunately I have no solution. For me (German carrier), calls do work in principle, but only with specific cells/bands, and only with VoLTE. Do you have the latter enabled? At this point, no one really knows what is going on. Sadly, if F(x)tec do not come up with a fix for this, be prepared to never be able to use the Pro1X as a (reliable) phone ...

Of course. There is a lot of frustration resonating in that message, wherever it came from.

It does confirm what I wrote above almost to the letter, even including the words "out of control" and "mess". And I have no behind-the-scenes insight. So, yes, I think this is a quite realistic picture of the situation. Maybe it could be classified a pyramid scheme in the sense that IGG earn their income from companies running their campaigns through them, with many of these campaigns failing, backers and/or companies loosing their money, and with only IGG themselves making profit in the end.

Even though they communicate much more openly since a few days ago (which is good), their "careful" phrasing still leaves room for speculation about what is happening, of course. However that post from "Project owner" I quoted already above seems pretty clear to me: "[...] shops have obtained stock from our warehouse without our permission or knowledge. This action was taken by our warehouse in an attempt to recover a some of the outstanding balance that they are due to paid by us." (emphasis mine) and later: "We are told that 300 devices were given(sold) to the Japanese sh

Reading down the IGG comments a bit further, I come to the impression that this is F(x)tec's last stand. They're completely out of money. Their devices sit in Hong Kong with no clearance to ship because F(x)tec are unable to pay the bill. Pro1-Xs "appearing" on the market are due to Expansys acquiring devices as a way to obtain their payment. Probably, F(x)tec are at the point where the few shipments actually taking place are being paid from employees' revenue. What a mess.