@PINE64 You mean the SanDisk flash ?

@jamieweb pull it from github, here are my personal notes when I did it :

git clone https://github.com/ubports/ubports-installer.git
cd ubports-installer
npm run-script dist:linux
./setup-dev.sh
npm start

Thanks @dobey once again. I have nothing to modify in it, just trying to save time by copying a portion of existing code to create a new ListView for the VVM messages in the dialer-app, I copy the ListView from the call history and I was looking for the structure of the model.

I added a button (that will be showed only if the service is activated) on the dialer page :

That will display a new page :

I would like to display a play line when we touch the item (like the iphone style).

@jamieweb Of course, no problem at all if that can help other people experiencing this with their Meizu If you need help for your script, please post in your original thread and I will try to help you. Good job.

@Stefano you can do this regarding the fingerprint reader, I did it on 16.04:

https://github.com/ubports/ubuntu-touch/issues/396

@tricky said in Cant receive pictures through mms??:

07918405210077F76404913305000491308291742140790605040B8423F02B06246170706C69636174696F6E2F766E642E7761702E6D6D732D6D65737361676500B487AF848C82986353764D61636E7345484341008D9083687474703A2F2F67656F313A383030322F6353764D61636E73454843410088048102A8BF890B80353038303036393434008A808E03049A42

Well your SMS is arrived, it is the stream above.
you said that you got it into your history db ? Right ?

If yes, in the DB there is a column for the attachment, can you check if it exist in the attachment folder please (./.local/share/history-service/attachments) ?

Hi to all, I'm currently writing an application that will handle the visual voice mail for our favorite OS. The app will allow you to hear your voicemail messages and to see them as a list in the dialer-app.

But at that time, I would like to share with you how I did to configure it in Dekko2.

What is visual voice mail ?
Usually when someone could not reach you, he can leave you a message in your voicemail box, you have then to call your box a listen the message (and delete it using a number on your keypad).

The visual voice mail (vvm service) is a service that need to be activated for your account from your provider interface (call or web). This service require a data connection. When a people will not be able to reach you and leave you a message, your provider will send a hidden sms to your device (SMS CLASS 1 or 0) to inform a local application on your device about the need of download the message from an imap (mail) server. When you activate this service, your provider will send a hidden SMS to your device with your credential's information (imap server address, port, login, password), a dedicated app on your device will store it in a database.

I'm trying to write the app that will handle all of that but for now, I will try to explain to you how you can receive this SMS and try to configure Dekko2 (yes I said try because it was a kind of magic to get it to work) with the imap informations for getting your voicemails inside.

Configuration
First, you will have to active the debug on ofono (the process on our devices that handle sms and other things related to the cellular phone modem), to do that, put your file system in read write :

sudo mount -o remount,rw /

edit the file : /etc/init/ofono.conf

sudo nano /etc/init/ofono.conf

add this lines before the 'exec' line :

env OFONO_RIL_TRACE=y
export OFONO_RIL_TRACE

Restart your phone.

Now run the following command (via adb or terminal) :

tailf /var/log/syslog |grep ofonod

it's time to activate the vvm service from your account.
Once activated, wait and look in this logs for a UNSOLICITED SMS arrival, you should see something like that :

Mar 25 22:33:06 ubuntu-phablet ofonod[2593]: [1,UNSOL]< UNSOL_RESPONSE_NEW_SMS {07913xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxB0D}
Mar 25 22:33:06 ubuntu-phablet ofonod[2593]: SMS
Mar 25 22:33:06 ubuntu-phablet ofonod[2593]: ME Download message ignored

Copie the content located between the {}, it is the binary content of the SMS in PDU format. We will now use an online PDU decoder to have our SMS in clear text.

Go on this site :
https://www.diafaan.com/sms-tutorials/gsm-modem-tutorial/online-sms-deliver-pdu-decoder/

Paste your hexadecimal content in the "SMS DELIVER PDU" box then click on Decode.

In the table under, you will have the clear text message in front of the "Message" item. read this line, inside you will find all the needed information to connect to your imap provider, you will need those information :

• srv or server= your imap mail server !
• ipt or port = the port for the imap connection (ex 993 or 143)
• u or name = your user name
• pw = your personal password.

Now you are ready for configuring Dekko.

You can put your file system again in read/write mode and disable the ofono log by removing the two lines added before, the reboot the phone.

Configuring Dekko

To access the imap server of your provider, you have to switch off your wifi connection, the connection must be done via the cellular modem, so, switch off your WiFi for now.

Open Dekko and go to the settings to add a new account, choose IMAP, name it VVM or whatever you want, enter a description.
Your email address is your username@your_domain_provider ex: 123456@vvm.sfr.net, enter your password then click next. AND then come the magic ...

You have to know that in a normal working way, your device have to send a sms to your provider that tell the service is ready to be used on your phone. I didn't do that. I just try to connect with Dekko and after some hours (maybe the activation time), it downloaded the list of messages. You will have to play in the settings with the kind of crypting (SSL/TLS), the authentification way (I used LOGIN), maybe to manually enter the name of the INBOX in the folders options ... don't put a refresh time to short (I setup a check every 50 minutes or less but not every 5 minutes) normally your provider will expect a connection of your device when somebody leaves you a message, my provider seems to be more tolerant and the server accept my connection all the time.

It works well for me like this way but it is really provider depend. it could not be a success for everyone.

Here some screenshot from my Dekko (in French )

I hope that it will be usefull for some of you at least.

Alain

@Flohack oh I was thinking that only the Meizu Pro5 was missing notifications features ! I will first modify my driver to enable the rgb function then ... I will try to take care of the API for everybody .

@AppLee Hi ! Maybe you can have a look to oFono, it is the app that is controlling the modem. In the documentation there is :

Flight Mode

• Flight Mode support. oFono uses the 'Online' property on the Modem interface
  that controls the state of the radio. When Online state is False, all
  interfaces that depend on the radio being on are removed. Other interfaces
  enter reduced functionality mode where only certain actions are available
  that do not depend on the radio. E.g. setting various settings on the local

You can use D-bus message for putting the radio on or off:

here you have the related d-Bus message :
https://github.com/intgr/ofono/blob/master/doc/modem-api.txt

Properties boolean Powered [readwrite]

		Boolean representing the power state of the modem
		device.

	boolean Online [readwrite]

		Boolean representing the rf state of the modem.

Online is false in flight mode.

@jamieweb Nice article, it is clear and easy to understand. Thanks for your feedback and the mention !

What is currently the status of the sensors on all the devices that are running UT ? You all know that each device came with a lot of sensors (accelerometer, gps, magnetometers, nfc ....) are they working well on all devices ? for my device it is not the case. Do you plan to share some code example for developers who like to used them in some app?This can be very appreciated! For example NFC can be very usefull. I understand that making an OS stable is very difficult when it run on a lot of different devices but actually UT is far away to be unstable, can we imagine to have now more working device's functionalities for the existing one ?

Hi @jamieweb I don't have twitter or a website so you can link my profile if you want. Many thanks to you and of course, I'm curious to read your article

@jamieweb You can also take a look at repowerd, it seems to be the deamon that is handling the power button : launchpad repowerd I see some event of it in syslog when pressing the power button.

With this command you will lock the user screen but not power off the display :

loginctl lock-session c1

@jamieweb The only things I found back from my notes regarding D-BUS is this :

signal time=1544722135.567846 sender=:1.0 -> destination=(null destination) serial=8601 path=/com/ubuntu/Upstart; interface=com.ubuntu.Upstart0_6; member=EventEmitted
   string "dbus"
   array [
      string "SIGNAL=Activity"
      string "BUS=system"
      string "INTERFACE=com.canonical.Unity.UserActivity"
      string "OBJPATH=/com/canonical/Unity/UserActivity"
      string "SENDER=:1.21"
      string "ARG0=0"
   ]

signal time=1544722135.795139 sender=:1.0 -> destination=(null destination) serial=8602 path=/com/ubuntu/Upstart; interface=com.ubuntu.Upstart0_6; member=EventEmitted
   string "dbus"
   array [
      string "SIGNAL=Activity"
      string "BUS=system"
      string "INTERFACE=com.canonical.Unity.UserActivity"
      string "OBJPATH=/com/canonical/Unity/UserActivity"
      string "SENDER=:1.21"
      string "ARG0=1"
   ]

When the home button is pushed. I'm not sure that this will help you a lot...

@jamieweb Hi ! I did not have my notes under the hand for now but one things that you can try to reduce the amount of dbus messages is to switch off gsm/wifi/bluetooth you should have less messages over dbus. Tomorrow I will take a look at my notes to check what can be useful for you.

@jamieweb Awesome ! I'm happy for you.

@jamieweb said in MX4 Ubuntu Edition: FAILED (remote: unknown command):
it seems like ubports-installer is just trying to reboot the phone into recovery, but Meizu phones don't support that in the way it's trying to do it.

Exactly

@jamieweb Good question, I don't know why we have to step first into the installation of Canonical version. If I was you (easy to say), I tried first to flash the ubuntu recovery, then I start the phone on it, and try to use ubports-installer, if that works, you have gain a lot of time, if not.... You will have to reinstall it. During my issue with my IMEI, I played a lot with the phone by switching between Flyme and UT, all the time, the only thing I did was to flash the ubuntu recovery, start on it and run the modified ubports-installer to get UT back (without having to re-install the original Canonical first).

@AlainW94 said in MX4 Ubuntu Edition: FAILED (remote: unknown command):

@jamieweb I perfectly understand, I modified it there is a while ... let me look for the modified file then i will post it there.

Try to replace this part of code in the file src/devices.js :

var instructBootstrap = (fastbootboot, images, bootstrapEvent) => {
    //TODO check bootloader name/version/device
    var flash = (p) => {
        fastboot.flash(images, (err, errM) => {
            if(err)
              handleBootstrapError(err, errM, bootstrapEvent, () => {
                instructBootstrap(fastbootboot, images, bootstrapEvent);
              });
            else {
              if (fastboot) {
                  utils.log.info("Booting into recovery image ALAIN...");
                  // find recovery image
                  var recoveryImg;
                  images.forEach((image) => {
                    if (image.type === "recovery")
                      recoveryImg = image;
                  });
                  // If we can't find it, report error!
                  if (!recoveryImg){
                    bootstrapEvent.emit("error", "Cant find recoveryImg to boot: "+images);
                  }else {
                    fastboot.boot(recoveryImg, p, (err, errM) => {
                      if (err) {
			utils.log.error("Fastboot: AW boot error; ");

			bootstrapEvent.emit("bootstrap:done", fastbootboot); // Ignore the error, ignore the bootstrap, boot into recovery then the installer will did the flash upload, works well on my Pro5, I only had to flash the recovery fisrt with fastboot flash recovery recovery.img, then run the installer. That's not nice I know but that worked for me.

                        //handleBootstrapError(err, errM, bootstrapEvent, () => {
                        //  instructBootstrap(fastbootboot, images, bootstrapEvent);
                        //});
                      }else
                        bootstrapEvent.emit("bootstrap:done", fastbootboot);
                    })
                  }
              } else
                  bootstrapEvent.emit("bootstrap:done", fastbootboot)
            }
        }, p)
    }
    bootstrapEvent.emit("bootstrap:flashing")
    bootstrapEvent.emit("user:write:status", "Flashing images ALAIN")
    if (!utils.needRoot()) {
        flash(false);
    }else {
        requestPassword(bootstrapEvent, (p) => {
            flash(p);
        });
    }
}

You will have to compile and install it or run it from the sources.
Good luck.