Bounty for Pixel 3a/Halium 9 stability
-
I'm not a developer, but I can offer to do testing when needed. I'm on T-Mobile. I'm curious to see if there could be any difference activating this phone on Android first and then installing UT (doubt it considering everything gets wiped, but this is science. I'm not sure if you all are sim-swapping or if the phone is actually tied to an account). I'll also need to be sure I have a viable backup phone to swap to so I can actually call and text.
I want this to work as much as all of you. I'm ready to daily drive UT in the US. I'll do everything I can to assist.
-
@manchee1017 I believe that the IMEI/MEID are sent to your phone company associated with the SIM card. I don't think they change based on the OS but the phone companies definitely associate them to your activated SIM cards/your account. I think they're built into the hardware or something.
-
Is there a method to formalize such a bounty or is it done ad-hoc on the forum like we already have here? I might be able to chip something in, with a formal process but can not do so for a forum setup.
-
@freefrog you could use bountysource as kind of a "notary" to handle it in a more formal way. UBports itself does not manage such transactions for the community, due to legal reasons.
-
Count me in, I'm happy to do testing. I'm on Mint mobile with SMS and Talk working, tho MMS does not work, I can throw In $10 maybe it can give a dev enough coffee to get through a long night coding. :hot_beverage:
-
MMS feature is important for me. I'm willing to donate some money towards this bounty, maybe 20-50 USD.
-
I wonder if someone should build a cloud-based spreadheet with all bounty commitments so a dev could quickly see how much is available to tackle this issue. Might help convince someone to take this on. I could build the sheet but wasnt sure if someone else was in a better position to do so. Or maybe we can pin a running total to the top of the thread if that is possible?
-
@grhmhome said in Bounty for Pixel 3a/Halium 9 stability:
MMS feature is important for me. I'm willing to donate some money towards this bounty, maybe 20-50 USD.
I got MMS working (send and receive) on US Mobile (T-Mobile network) in the USA but only after booting the phone with wifi disabled. Once wifi is enabled, then SMS receive and all of MMS breaks. Here is where I wrote up a bit more detail: https://forums.ubports.com/topic/6369/tmobile-issues/17
Note that with the same SIM on a N5 I don't have any SMS or MMS issues, so it seems specific to the Pixel 3a
-
@rik said in Bounty for Pixel 3a/Halium 9 stability:
I got MMS working (send and receive) on US Mobile (T-Mobile network) in the USA but only after booting the phone with wifi disabled. Once wifi is enabled, then SMS receive and all of MMS breaks. Here is where I wrote up a bit more detail: https://forums.ubports.com/topic/6369/tmobile-issues/17
Note that with the same SIM on a N5 I don't have any SMS or MMS issues, so it seems specific to the Pixel 3aWell, I still have SMS receive and MMS send / receive not working reliably. Sometimes / often the messages will come after a reboot, and I still don't think I have ever gotten messages when wifi is active, but since there are other unreliable pieces here it may be coincidence that I got it working only with wifi off before. In short, I am still confused and more testing / debugging needed. Any pointers on where to find logs about what may be going on? Power saving maybe killing messaging service???
Can anyone NOT in the USA confirm that the Pixel 3a can receive SMS when wifi is on, or that can send / receive MMS? Trying to understand if this is a US carrier thing (see above link to Tmobile thread) or if it is this phone across the board regardless of carrier? Maybe @fredldotme could comment on the state of SMS receive and MMS s/r?
-
@rik
I may be a bit late but just got a pixel 3a working with UT. I am in the UK and CAN send / receive SMS and MMS with the wifi on. -
@irnbru yeah I am in Canada as well and I can receive 100% sms and about 50-65% mms. A reboot often gets mms working again. I think this is affecting US users more for some reason...
-
Bought a refurbished Pixel 3a XL and successfully installed Ubuntu Touch on the device.
UK based - standard phone calls seem to be working
I've documented my steps here: https://forums.ubports.com/topic/6396/pixel-3a-xl-experience
But we should converge all documentation in one central section. It's not been easy for me to install it at all. I worried I irreversibly crashed it at some point.
I'd be keen to help with any sort of development, so will see if I can find some resources or maybe join the Telegram group.
The state of art is "huuuuuge potential, lack of everything" at the moment. If you consider I rarely use the phone to make audio only calls, there is a lot of work to do.
-
Good news! Over the last few days we enabled initial support for SMS & MMS on the Pixel 3a & 3a XL on US carriers. A bunch of other fixes made it into the current release candidate to perfect it but this is the big one.
SMS work reliably on 4G now and MMS partially work (lacking proper Group MMS support right now). The phone doesn't trip off the carrier with its incomplete IMS support too.
If you want to make sure you can reliably receive MMS please make sure your APN settings are compatible, either by changing the settings or, if the system-settings GUI doesn't work, by editing the
/var/lib/ofono/<number>/gprsfile manually, or by disabling the Internet APN completely. Staying off WIFI is also reported to work reliably. -
@fredldotme Wait, do you mean better stability for the AT&T and T Mobile support we've already had for a while, or do you mean VoLTE support for UT to work on Verizon?
My main plan is with Verizon so I got a cheap pre-paid to mess around with on AT&T, but does Verizon now work on Pixel 3a with UT?
-
@heyspencerb sorry to disappoint, but I don't think anything has changed regarding Verizon (lack of) compatibility. The AT&T and T-Mobile support, up until the fixes @fredldotme mentions, are for US users who would not get incoming SMS reliably (ONE would come per boot, but then it turns out once the phone advertized it could handle "IMS" then the carrier switched over to delivering SMS via IMS, which in UT meant they went into a black hole: disabling IMS on the phone means the carriers still send SMS the "old school way" and they reliably come).
Also, at least for several of us, we would not be able to receive or send MMS. Part of this was confusion on setting up APN entries, and some bugginess in the APN gui etc. But with a bit of tinkering with APN entries it is working reliably for us now (but NOT with wifi enabled, only when on cellular data). There is a separate bug about MMS not working when wifi is on, this is not just for the Pixel 3a.
-
@rik Totally, makes sense, I've been following the progress of VoLTE and I was thinking this was a pretty big step forward all of a sudden. Still, good to hear! I'll try out my new AT&T sim when I get home and see how it goes!
Was a bounty ever set up for the VoLTE? If so I'd like to contribute if I can
-
@heyspencerb See last weeks UBPorts Blog Q&A. UBPorts is asking for steady contributions to pay for the work regarding VoLTE
-
@rocket2nfinity Thanks, I just set up a 10 euro per month donation like they asked for.
-
Pixel 3a XL here on development channel. Cricket wireless. After mixing and matching multiple apn solutions to get mms working, I figured I'd share my fix. Hopefully it'll save someone the heartache I just went through, haha.
WIFI off
2g/3g/4g connection type
APN stuff. Modify existing two and save
-Cricket Internet-
Used for
Internet
Name
Cricket Internet
APN
Endo (think this was the main fix from default ndo)-Cricket MMS-
Used for
MMS
Name
Cricket MMS
APN
ndo
MMSC
http://mmsc.aiowireless.net
Proxy
192.168.196.78I believe changing the Cricket Internet to Endo helped with a conflict of both mms and internet being stock set to ndo? Not sure, but that was the last thing I tried before giving up, and it started working.
Hope that helps -
Update. Everything worked. Everything. Now it appears to be denied access. Sigh.
