Seems to be the same whether or not I have security in place or no locking code.
I normally have no lock code. So when I turn the screen on the phone is simply ready to do things. That is probably considered a bad practice, but it is for this reason why I always have developer mode disabled.
Do you keep a lock code and then developer mode (most of the time)enabled?
When I plug my Ubports phone into my computer, I would like to see a popup on the phone screen with a yes/no in it to allow file transfers via USB, a sort of limited permissions granting. Right now in Dolphin KDE the phone does appear but the window is completely empty.
I do not want to always enable admin developer mode on the phone with maximum permissions just to grab a few photos. Is this currently possible to enable in Ubports settings somewhere?
I was just curious of someone around here had an idea of if support for displaying an attached bluetooth device's battery level was seeing some progress.
Or else, if I completely missed where I can see it then someone set me straight. Being able to see what the battery level of my headphones, or a bluetooth keyboard would be very useful.
I looked in the bluetooth panel, in the slide down battery panel from the top, and the system > battery control panel.
I'm really hoping that an APNDB update that appears to have been backported to Focal 20.04 will fix a long-standing issue I've been experiencing where after a few months, photo messaging just completely stops working.
https://gitlab.com/ubports/development/core/packaging/lineageos-apndb/-/merge_requests/2
I only have one single phone, wish I could actively contribute for RC but also, my issue usually manifests several months later and that isn't going to help an RC window that closes in 1 to 2 weeks anyways. I can't for now use my daily driver for testing.
Looking forward to more VoLTE supported phones!(FairPhone4 here) Thanks to all who have helped with this release.
@wally said in Why does picture messaging stop functioning after a few months?:
@ezst036 Sorry to hear those things haven't worked. I assume that if restarting nuntium didn't fix the problem, it's just a different issue than I was having.
I hope you're able to resolve it somehow without a full backup and re-install. I presume that in the past when this has happened to you, flashing without wiping data didn't fix the issue?
I have only found backing up and using the UBPorts installer to start fresh as a resolution.
It's working again now, wiped and now have OTA-5.
EDIT: (3/10/25):
I marked the discussion as solved, and wanted to make a few notes for reference.
I updated to OTA-8. This is important compared to other OTA-x because there was an update commit made to the apns-conf.xml in the source tree after I made some requests on Gitlab. My cell provider's APN by default was out of date. Now when I do a fresh UBports install I do not have to change the APN information, the default is correct.
Hopefully that prevents the software from getting confused between my "custom" APN setting and the "default" outdated APN contained in the source xml file. I only need the default.
I will create a new discussion or Gitlab bug request should the issue come back.
@wally said in Why does picture messaging stop functioning after a few months?:
@ezst036 Can I ask what device you're using?
I currently have a Fairphone 4. I started out with a Pixel3a though and it happened on that one once too.
I followed the steps you provided as best as I could:
change my MMS APN to something incorrect, disable MMS, restart phone, correct the MMS APN, enable MMS again, restart phone again, and then it works.
This did not work, but I could not follow the steps as typed. It seems that on 20.04 OTA4 when the phone restarts all APNs are enabled, not the disable as I left it. I thought I might get around this by shutting off all mobile data in its place within these steps, but the icon still only spins and spins.
@arubislander said in Why does picture messaging stop functioning after a few months?:
The equivalent command to yours is:
systemctl --user restart nuntium.service
Thanks for helping sort this out!
Sadly though, this did not do anything appearing to resolve the issue. The nuntium logs used to be located at: ~/.cache/upstart/nuntium.log
Do you know where they are located at now due to systemd?
In that case, it is not a combined APN setting. Only works if APN has the same name.
Thank you for clarifying that. I will try resetting the APNs, rebooting and ensuring no wifi, but having done these a few times already I don't expect much of it.
Hopefully I can collect more info on how to actually troubleshoot this instead of doing a re-install, I would need to put in some kind of bug report that amount to more than just "it's broken" as that won't help me nor anybody else.
If you confirmed that you toggled On Cellular Data ( and toggled Off Wifi ) when sending MMS and it still don't work, then 99,9% chance is a APN setting issue. Depending of your provider, but for mine ( La Poste Mobile in France ), even if it is shown that 2 APN need to be set ( one for Internet, the other for MMS) , i had to create a "combined APN setting Internet & MMS", it means removing the current setup and recreate one.
Thanks, is this a semi-common thing that proper APN settings are working and then, just, one day no longer working that they should require this kind of removal procedure?
That's really what I want to wrap my mind around. When OTA5 was announced, I specifically didn't upgrade because I figured the phone worked, and since then I have sent a few more MMS messages and it was working.
How do you deal with combining your APN setting when your web APN is different than your MMS APN and the phone only has one line? Which one do you choose?
@wally said in Why does picture messaging stop functioning after a few months?:
Here's something to try. I can't say whether it will definitely fix things, but it's quick and it won't break anything.
Open Terminal
type "initctl --user restart nuntium"
Thanks, this sounds promising.
Except, when I type in that command or just when I type in initctl I get:
bash: initctl: command not found
Whoops. Best I can tell initctl ought to have been installed already and just be there. So maybe something somehow got damaged. Just so it is asked, wouldn't this nuntium be restarted if I do a phone shutdown or reboot?
I seem to be having this issue where after about six months, sending and receiving picture MMS messages no longer works. The icon just spins in txt messaging but the image never gets sent. If someone sends to me, I'll never know about it unless I'm told.
Is my only option to make a backup of my text messages and photos and do a full/system reinstall? That seems excessive to do every six months.
I've checked my MMS APN, reset the settings, rebooted, but non functionality stays the same.
Just wanted to clarify,
Yes, it was two monitors but they were mirrored, not extended. Makes the second monitor pointless for now.
@thedeafenguy Thank you, but following the steps in this order and doing other order that I can think of does not help.
I'll take a look around and see if I can find out the steps needed to back up and restore my text messages and photos so I can do an absolute re-install leaving nothing behind.
For phone usage (text, limited internet/browser, calls) I found a Pixel 3a to be more than adequate. I don't use WayDroid or other functionality all that much on a phone, the screen is simply too small.
I noticed some performance uptick with a OnePlus 6T but not really a "necessary" upgrade. The main thing moreso is 'does the UBPorts software support the phone or are there missing features because of the port itself'.
My current FairPhone 4 is decidedly snappy during use, but what I thought was most interesting is it works quite well with a docking station, even with dual monitors. I have tried both the Dell WD15 K17A and WD22TB4 docks and found them to be completely compatible. The WD22TB4 is significantly faster.
What I need most is stronger camera performance but Android has certain things on lockdown that prevent some camera potential from being tapped.
@lduboeuf Yes, Wifi is off. I never use Wifi on this device. When I remove the APN altogether, reboot, and let a new one get created on its own, it somehow selects an incorrect proxy and mmsc address.
This is technically "normal behavior" in that when I first started using UBports this address is what would appear. When I inserted the correct APN information as above, MMS would start working though.
Are there no log files or anything in /VAR or any terminal commands that might be of use?
@lduboeuf Hello, thank you for the prompt reply. The settings are:
APN: mms.gci
MMS: http://mmsc.gci.net
MMS Proxy: 24.237.158.34
MMS Port: 9201
No username/password. I did not know about swipe right to delete, but when I did that and then added a new entry and rebooted, I still only have the spinner.
They should not need to be a combined MMS + Int, they were not that yesterday (well two days ago now) when it last worked.
I'm in a situation, I can no longer send and receive picture messages. I don't know what to do, it worked yesterday though. What steps have you taken to resolve getting MMS back to a working state?
Here are the troubleshooting steps I took so far:
1: Confirm with my carrier that there are no wide outages, confirm APN settings with the tech.
2: Put SIM into old phone, send test picture message. Receive test picture. It works with the old android. My problem is clearly local.
3: Use UBPorts installer, which updated from OTA-2 to OTA-4. I saved personal settings.
4: In system settings search for updates, install everything found.
5: Confirm APN settings in UBports one more time, confirm data/MMS is enabled, go to browser and confirm internet is working. It works. Now I try to send MMS picture message. It's still not working. When someone tries sending me something, its like a ghost. Nothing happens, no notification of any kind. When I try sending something the indicator next to the image just spins.
I don't know how to fix this. Is a destructive full wipe the only solution? What do you do to troubleshoot issues like this?
Are there terminal-based commands that can help identify the issue of why MMS is broken? Is there a hidden settings folder I can delete which will force a reset on specific functionality or clear out those messed up preferences?
@Luksus Thank you for the information.
I am curious what other users of the FP4 see when they open the camera app, am I the only one who doesn't seem to be able to get to the full 48 megapixel?
Good morning and afternoon,
I just had a simple question that I think there is probably an answer to, but I'm new to UBports.
I recently purchased a Fairphone 4 in part because because it has a 48 megapixel camera. The problem is, when i go into the vanilla camera app (I have not done much since installing UB on the FP4) and select quality the highest option is only 16:9 8.3MP. (technically 4:3 12MPixel but I do not really want that aspect ratio)
I have not done any quality comparisons on a larger screen, but the images "seem" to look a lot better than they did on the other phones I have been trying. Is there maybe a setting that I missed that will expose the full 48 megapixels or maybe its just mis-reported?
Anybody know where the discrepancy is at? Again, new user here. Thank you.
When I send people an MMS message from UBPorts, the images that are received on the other side are significantly degraded from what is in my photo gallery.
Is this a setting that I can control? So that the images are sent across much closer in resolution/quality?
As an unscientific test, I took an Android that I have which is around the same age and specs of the phone I'm using for UBPorts and when I send using the Android the photo comes out on the other end with decent quality. (albeit it is also degraded. I can see some grainy but it's minor)