@ultrasonicnoise

Hmm ... so if that APN is no longer in the file, then maybe it is not matching the "3" in the name field and so it defaults to what the provider or sim card sets? (I am assuming that is what it uses to match ... ) Sorry, not sure what to suggest from here ... ??

  <provider primary="true">
                <name>3</name>
                <gsm>
                        <network-id mcc="234" mnc="20"/>
                        <apn value="three.co.uk">
                                <usage type="internet"/>
                                <name>3 Internet</name>
                        </apn>
                        <apn value="3internet">
                                <plan type="postpaid"/>
                                <usage type="internet"/>
                                <name>Internet</name>
                        </apn>
                        <apn value="three.co.uk">
                                <usage type="mms"/>
                                <name>3 MMS</name>
                                <mmsc>http://mms.um.three.co.uk:10021/mmsc</mmsc>
                                <mmsproxy>217.171.129.2:8799</mmsproxy> <!-- mms.three.co.uk -->
                        </apn>
                </gsm>
        </provider>

In my past experience (and more recently on a fresh 20.04 install), sometimes the UI is glitchy to accept and remember changes (you did reboot, right?) ... To overcome this, I had luck changing the file that feeds the default APN settings when you reset / delete them then reboot. The file is:

/usr/share/mobile-broadband-provider-info/serviceproviders.xml

To edit it, you will need to remount the / file system r/w ...

I found my carrier ... then edited the section to reflect the proper APN entries ... then delete APN entries & reset (they were hard to get rid of) then reboot ... and it should pull in the new values from that file. Hope this helps!

Thanks for the write up!

I have been running with this setup for a while. Couple of other things to point out (maybe there are solutions I've missed?):

I can not get images/pictures in encrypted chats: Just shows a cloud with an exclamation point in it. On UN-encrypted chats, the images come in fine.

"Spaces" are not handled properly - they show up as chats/rooms with no real content in them.

Perhaps obvious, but worth to point out that calls don't work (voice nor video) ... although I think it rings.

@3t_ed To elaborate a bit further: First, Alfred applied those changes to the port. One OR 2 did not stick properly and rather than chasing down the issue further, he remove zram completely. So the dev version of p3a is no longer using any swap. There are no more lockups, but (IMHO) there is a little less bandwidth for multitasking, especially after a few days of uptime (where presumably software memory leaks have chewed into the avail 4GB of ram. All in all a big improvement ... would be good if some other could test and chime in their thoughts.

https://github.com/fredldotme/android_device_google_bonito/commit/cea569eb00838ad9cb6e16471b69510b0f0e0e47

https://github.com/fredldotme/android_device_google_bonito/commit/f4df3991231cf4f7aab62584a9289a7642b88e9c

@rik @Fizz @jezek
Sorry guys ... don't check in here often. Yes, I am also experiencing the "Invalid URL" ...
I believe this is a nuntium bug and raised an issue here
The issue was also experienced by @notkit and there was a hint on where to look for the issue here
Since it is not happening to everyone, my current guess is that the parsing of the URL for those with a PROXY is breaking something: @fizz and I have proxy, don't think you or others do @rik? Either that or the port? (although since its :80 ... I have tried without it and had same results).

TLDR: try pda2.bell.ca for one of the APN's (Internet).

Full version:

On Bell Canada. WITHOUT the patch that allows merged apn entries, this should work (Although I have a bug in nuntium that prevents me from receiving ... I CAN wget the files so hopefully some version of these will help out):

[context1]
Name=Internet
AccessPointName=pda2.bell.ca
Username=
Password=
AuthenticationMethod=none
Type=internet
Protocol=ip
Preferred=true
MessageProxy=
MessageCenter=

[context2]
Name=bell mms
AccessPointName=pda.bell.ca
Username=
Password=
AuthenticationMethod=none
Type=mms
Protocol=ip
Preferred=true
MessageProxy=web.wireless.bell.ca:80
MessageCenter=http://mms.bell.ca/mms/wapenc

To make this stick through APN resets I changed the bell section of my /usr/share/mobile-broadband-provider-info/serviceproviders.xml

        <provider>
                <name>Bell Mobility</name>
                <gsm>
                        <network-id mcc="302" mnc="610"/>
                        <network-id mcc="302" mnc="640"/>
                        <network-id mcc="302" mnc="651"/>
                        <network-id mcc="302" mnc="880"/>
                        <apn value="pda2.bell.ca">
                                <plan type="postpaid"/>
                                <usage type="internet"/>
                                <name>Internet</name>
                        </apn>
                        <apn value="pda.bell.ca">
                                <plan type="postpaid"/>
                                <usage type="internet"/>
                                <name>Mobile Web</name>
                        </apn>
                        <apn value="pda.bell.ca">
                                <usage type="mms"/>
                                <name>bell mms</name>
                                <username></username>
                                <password></password>
                                <mmsc>http://mms.bell.ca/mms/wapenc</mmsc>
                                <mmsproxy>web.wireless.bell.ca:80</mmsproxy>
                        </apn>
                        <apn value="pda2.bell.ca">
                                <plan type="postpaid"/>
                                <usage type="internet"/>
                                <name>Mobile Fast Web</name>
                        </apn>
                </gsm>

So I built a routine that allowed me to reproduce the lockups (where the swap use shown in top (zram) hits 100%, and memory is 95+% used) - it basically involves opening a bunch of webapps / apps that I use; but all at once in fast sequence. The camera is one app that needs a bunch of memory ... and can easily push the device over the edge).

I then tweaked memory control parameters as per various suggestions found online and repeated the test. I was able to get a lot further before lockup with the settings below. (The phone uses less zram as I progress through my test, I guess ultimately pushing back the time to lockup). I haven't noticed any performance hit (purely subjective), and I can run many days now without lockup. On the one occasion where I did lockup, recovery was faster (rather than 1-3 mins, it was ~10 seconds)l; however I did notice one of my open apps was killed (white page with green triangle saying refresh). Haven't figured out how to set this across boots - although my reboots are a lot less frequent!

Disclaimer: This is for the pixel3a - that has 4GB of RAM and ~ 1.6GB zram setup. Based on my reading, I think some of these settings are very specific towards hardware (memory, cpu, swap vs. zram) on the device... also, I am a hack wrt linux and have NO other experience with these settings:)

sudo sysctl vm.min_free_kbytes=29620 &&
sudo sysctl vm.vfs_cache_pressure=200 &&
sudo sysctl vm.dirty_background_ratio=3 &&
sudo sysctl vm.dirty_ratio=40 &&
sudo sysctl vm.admin_reserve_kbytes=16384 &&
sudo sysctl vm.swappiness=80

Hope this helps ...

So turns out the swap showing on our Pixel3's is ZRam (Fake swap on memory that is compressed). The 100 setting is appropriate for this setup. Will keep digging around for some way to prevent 100% use ... (which is the source of my lockups).

A bit too quick to declare success ... I locked up with 100% swap usage again today while my swappiness was set to 20. Still think it is a beneficial change for the life of the emmc ... however, issue persists.
@domubpkm ... Not sure yet how to persist this across reboots ... going to reach out to porters to see where this setting is established.

One further update:

sudo cat /proc/sys/vm/swappiness returns 100 ...

Is this parameter used in UT? If so, that doesn't make sense.

The default value of vm.swappiness is 60 and represents the percentage of the free memory before activating swap. The lower the value, the less swapping is used and the more memory pages are kept in physical memory.

I set mine to 20 ... and my test of opening a ton of webapps starts using swap much later.... and I haven't hit lockup yet. Not sure how to persist it though...

sudo mount -o remount,rw /
sudo sysctl vm.swappiness=20

@3t_ed If you enable USB debugging, next time it happens, you can plug into a computer (with adb tools) and run adb shell. This will bring up a terminal: run "Top" then hit "m" twice to see memory and swap % use.

Thanks @flohack and @kugiigi ...

I use a lot of webapps created with Webber (News sites) ... Quick test shows they jump memory/swap up in increments by 4-8% (just opening them) ... From a fresh boot, opening 5 news webapps, Morph, Telegram and Axotl brought it up to ~ 85% Swap; ... then I switched to closing them (upswipe) to see if swap and memory got freed up, which it did - but not all the way back down. I suspect (and will test) that if I had left them open and come back to them later to keep reading, I would max out and lockup.

None of my apps get closed at any point due to the lack of memory ... The phone just becomes very slow (eg: swipe responds after 30 seconds) ... If I leave it for 5 minutes, It resolves itself (at least for a little while), but I typical reboot to get back to the snappy smooth 3a experience.

I would happily rid it of the swap partition if you felt it would be better ... I gather the installer just set it up that way as a standard.

Let me know if I can test out and report anything to help ID and pin down what might be the cause!

The QA update did not solve the problem. I backed out from Dev to RC ... hoping maybe OTA 19 might have fixed something, but it does not. I confirmed that the lockup/slowdown happens once SWAP hits 100% usage (and obviously, since we are using swap, memory use is already very high around ~95%). Shouldn't the system be freeing up swap/memory before it hits 100%?

Could we change the "swappiness" parameter ... or adjust the amount of SWAP (on my pixel 3a) SWAP is set to 1.57GB ... about 40% of system memory. I remember rule of thumb on servers back in the day is to give them the same amount of swap as they have memory. Could this be the issue?

... so this is still happening for me (dev). Seems I'm using all swap space and kswapd is consuming a ton of resources. If I list memory usage with

ps -o pid,user,%mem,command ax | sort -b -k3 -r

... a lot of QT-WebEngine processes lead the usage ... so I will try this and see if anything improves:

sudo ubports-qa install PR_qtwebengine_5

Hi Folks!

Wondering if any of you are experiencing the same? On a regular basis (on average once a day) ... my 3a grinds to an unusable state: swipes respond after delays of many seconds or even minutes. I usually just reboot rather than wait the 5 to 10 minutes or so it might take to resolve itself. Once when it happened, I had ssh running and was able to see loads of 45 in top. wa was really high ... kswapd was at the top of the list of processes. I recall seeing something about qtwebengine memory leak ... which would build up with my Morph use and its webapps...
Are you other daily users seeing the same?
Thanks!

@damiam

Confirmed same behaviour here ... I just discovered that outbound mms works for me on 4G. But nothing (no SMS, nor MMS) inbound (having said that, only tested when receiving MMS from Iphone... which might be an issue) Interestingly, other notifications break for me as well on 4G - eg: Teleports will not show notifications either. Is this your case as well?

PS: Interesting issue here with a cause pointing to missing timestamp in SMS from certain carriers ... although I can't see why 3G and 4G would be different, nor why Teleports notifications would break.... I am currently wondering if IPV6 has something to do with it...

@haimeh

So I never actually had to add the route ... it seems the OTA17 fixed my issue (but no all issues). One other thing I did around the time, although don't think this has anything to do with was something I stumbled on while troubleshooting:

/usr/share/ofono/scripts/set-context-property 0 Protocol IP

Here are the route tables for 3G & 4G with WIFI on: (hope the formatting holds!):

3G & Wireless

default         10.x.1.1        0.0.0.0         UG    600    0        0 wlan0
default         10.xx.xx.20x    0.0.0.0         UG    700    0        0 rmnet_data1
10.x.1.1         *               255.255.255.0   U     600    0        0 wlan0
10.xx.xx.20x    *               255.255.255.255 UH    700    0        0 rmnet_data1
192.168.250.0   *               255.255.255.0   U     0      0        0 anbox0

4G & Wireless

default         10.x.1.1        0.0.0.0         UG    600    0        0 wlan0
default         10.2xx.x6.2x5   0.0.0.0         UG    700    0        0 rmnet_data2
10.x.1.0        *               255.255.255.0   U     600    0        0 wlan0
10.2xx.x6.2x5   *               255.255.255.255 UH    700    0        0 rmnet_data2
192.168.250.0   *               255.255.255.0   U     0      0        0 anbox0

Not sure if rmnet_data1 and 2 are standard across all phones /connections. If not, you should be able to spot yours by tailing the logfile...

Hope this helps!

PS: to check if you are on OTA17: SystemSettings> About OS should have Ubuntu 16.04(OTA-17)

@rdl85

Sorry, not much to add here ... but I've had similar inconsistent behaviour depending on how I land on 3G or 4G ... eg: Fresh reboot with 4G enabled vs switch from 3G to 4G, vs cycling cell data and or wifi on off. A lot of variables and tough to debug. Not aware of anyone with 3a and working mms in NA ... but then again, maybe they are not coming here since its working! Sorry to be of no help. On my side, Bell APN on the site you mentioned was the same as what I had; ... and my file is same as yours except you have an IP where I have a domain (no difference when I switch). I would also add that my SMS breaks when on 4G.

@rdl85

That is awesome! ... A few questions:

Are you on 4G or 3G?
Running OTA17 or ??
Could you post your APN config file? (I think they are in in /var/lib/ofono/somelongnumber/gprs )

I tried the suggested settings for Bell with no luck ...

Same on Pixel3a ...

Regular wifi drops and ...
futify (Spotify media player) won't hand off from WIFI to Cell Data without flushing the app (swipe away) and restarting it.