Leaderboard

@Hook has walked me through a weird workaround, so far effective in Maryland, USA/TMobile. As follows: Caller couldn't hear me. Put caller on speaker. Caller could hear me. Took caller off speaker. Caller could hear me. Called caller back, not on speaker. Caller could hear me. Hook also advised, in Preferred Network settings, to use: LTE/TDSCDMA/CDMA/EvDo/GSM/WCDMA This success is all LTE; wifi calling has been disabled. Data, anecdotally, seems fine. Haven't tried gps. But I'm going to try Pro1x as daily driver for next few days to see what I can see.

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

As far as I can tell, my Pro1x is constantly using Band 4 throughout my house and anywhere in my yard. It doesn't seem to switch. Your theory would predict that I'd be fine if that's really the case (I am basing this on LTE Discovery, assuming I understand what it is telling me, which is not guaranteed). I'm going to take it with me shortly to a place I know gets terrible T-Mobile reception on my Pro1 and see if it a)switches and b) if it does, does it have trouble recovering later.

According to the buildkite logs, the scheduled build simply crashed and wasn't re-scheduled. This weeks 20230327 update has finished though. Already have it running on my Pro1. OTA went through without issues.

Yeah, this was really weird... I accidentally did this early on but I didn't believe it was what fixed things. But when @jakfishwas telling me about his problems in discord, I just, on a whim, made the suggestion to see what would happen. I keep thinking it has to be a mistaking correlation for causation error, but the question is, what is the real variable.

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.

Well, I am out in the wild with my Pro1x. T-Mobile seems to have gotten better here. I seem to still be using band 4. Call was fine. Using internet on data now, no wifi. It's slow but steady. Even downloaded Firefox. As I said, slow but steady... no balking and quiting. I am wondering if US problems on T-Mobile have to do with which bands T-Mobile is relying on where. Or if there are defective units, as @EskeRahnraised, is it many or just a few? Any are too mmany for those that have them, I understand, but if weren't hanging out at this forum, I wouldn't see any reason for testing.

Seems a little overkill... I move the phone away and just tap the speaker button. 😄 No additional software needed.

An app like "Auto Speaker" (com.hanan.android.ramkol) can be really handy here, using the proximity sensor to detect if it should be handsfree or not. With this app the workaround could be triggered simply by moving the Pro1X away from and back to your ear.

Casey has been made aware on Discord. I will be joining the beta group in the next day or two.

Let is tag @Casey on this one. If this shows to be a working workaround for that bug -crazy as it is- it MIGHT help in tracking the bug down. If I were doing he testing, I would be likely to do either hands-free or with headphones, as you during test is likely want to see the screen. So who knows that MIGHT be why they could not reproduce the bug - I for one would never had guessed that hands-free or not could have any affect on this... Add: I almost NEVER use a phablet held to my ear. 99.9% of calls are handfree on my desk or with earphones, and THAT could be why I have not had the

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.