03-11-2021, 09:32 AM
(This post was last modified: 03-11-2021, 07:37 PM by dsimic.
Edit Reason: Wording improvement
)
I totally agree with your remarks. I'll put up a more detailed proposal for the actual hardware fixes, but please allow me to have some time for that, simply because I want us to start from a couple of viable fixes. Of course, the proposal will need to be discussed before actually testing out anything.
Perhaps we could even end up with someone willing to test the proposed hardware modifications on their own PinePhone, instead of me receiving a hardware donation and using it to test the fixes. I would be very happy if that would be the way to move forward, which will provide exactly what I'm looking for: sharing of the risk. In other words, I am not looking for a free PinePhone; instead, I am looking to us solving the backlight flicker.
I would really appreciate if you would be willing to test out some of the proposed hardware fixes. Of course, we would discuss them in detail before actually doing anything, so the risk of damaging your PinePhone should be as low as possible.
Again, I apologize for the way I came accross, and please allow me to explain further. Asking for a PCBA 1.2b (or testing the hardware fix on it) is necessary because one of the end goals would be to have Pine64 incorporate the actual fix into one of the next PinePhone batches. To do so, a fix needs to be tested on the latest available revision of PCBA, which is the 1.2b revision.
By the way, regarding the support for MMS, I'm afraid that I must be a bearer of bad news...
The internals of the exchange of MMS messages are insanely complicated, involving IIRC connecting to an FTP server etc., meaning that, unfortunately, implementing support for MMS would require a ton of work. Even Maemo, Nokia's variant of Linux that shipped on a couple of old Nokia phones (e.g. N900), initially had no support for MMS. I really cannot recall whether Maemo received the support for MMS in later updates, but if that's true, the related source code (which should be open) could be used to speed up the implementation of MMS support on the PinePhone.
Edit: This page provides more details about MMS on Maemo.
Perhaps we could even end up with someone willing to test the proposed hardware modifications on their own PinePhone, instead of me receiving a hardware donation and using it to test the fixes. I would be very happy if that would be the way to move forward, which will provide exactly what I'm looking for: sharing of the risk. In other words, I am not looking for a free PinePhone; instead, I am looking to us solving the backlight flicker.
I would really appreciate if you would be willing to test out some of the proposed hardware fixes. Of course, we would discuss them in detail before actually doing anything, so the risk of damaging your PinePhone should be as low as possible.
Again, I apologize for the way I came accross, and please allow me to explain further. Asking for a PCBA 1.2b (or testing the hardware fix on it) is necessary because one of the end goals would be to have Pine64 incorporate the actual fix into one of the next PinePhone batches. To do so, a fix needs to be tested on the latest available revision of PCBA, which is the 1.2b revision.
By the way, regarding the support for MMS, I'm afraid that I must be a bearer of bad news...
The internals of the exchange of MMS messages are insanely complicated, involving IIRC connecting to an FTP server etc., meaning that, unfortunately, implementing support for MMS would require a ton of work. Even Maemo, Nokia's variant of Linux that shipped on a couple of old Nokia phones (e.g. N900), initially had no support for MMS. I really cannot recall whether Maemo received the support for MMS in later updates, but if that's true, the related source code (which should be open) could be used to speed up the implementation of MMS support on the PinePhone.Edit: This page provides more details about MMS on Maemo.
