-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✏️ [ FEAT REQ ] Outdated MMS Config Database #36
Comments
Will be looking into this for the next release, as this seems important. |
@Retold3202 I'm tackling this now, and after looking over everything, I think I understand what needs to be done, but not quite what needs to change, code-wise. |
@octoshrimpy |
@SkewedZeppelin Hey, great to see you here! Good point on licensing. Do you know where I should start looking into that? maybe grapheneOS license, maybe? |
@octoshrimpy |
Oh is that why QKSMS MMS broke a few years ago? What does this configuration do that the APN on the network doesn't? I tried to go look at them, and on the GrapheneOS page, there's a bunch of stuff about translations, so maybe I missed something. |
@allanonmage |
Well now that the open source community has some code about all this, maybe I can figure out what's what and why MMS has never really worked on my phone whenever I load custom ROMs and stuff to it, for, oh, like 15 years or so. |
About the licensing? Is that really any different from the existing outdated mms config? A assume they were aquired in the same/similar way? I think updating this configs to get MMS working properly should be quite high on the priority list.... |
@snaggen : agreed. Pinning this so when I get some time this is my first priority |
Untested Taken from: https://github.com/GrapheneOS/platform_packages_apps_Messaging/tree/85a1ca48c9c4822325615dead35c215f2e9ec622 Closes octoshrimpy#36 Signed-off-by: Tavi <[email protected]>
Hello, I'm happy to use this app. Thank You. I also have a problem with send eg. photos via MMS. @octoshrimpy I'm sorry for escalating problem, but I wanted to ask you if implementation date is known? (the problem has already been reported some time ago) |
Hopefully this can eventually be implemented, I would love to be able to stop using the stock AOSP Messaging app... |
Is your feature request related to a problem? If so, please describe the problem.
Quik is currently using a very outdated MMS config database from January 2018, that it inherited from QKSMS. It can be found here. This can cause issues with MMS compatibility and reliability.
Describe the feature you'd like
I'd like to see Quik use an updated MMS config database. For instance, GrapheneOS uses the same database as Google Messages for their included Messaging app, see here. This database is much more up to date.
Additional context
See @SkewedZeppelin's comments here and here.
The text was updated successfully, but these errors were encountered: