Hi all,
just wanted to start a thread about my first app development job, to inform you I have made the heavy lift (hopefully!) for having most of the fundamental features in place to bring such a functionality to the Ubuntu Touch OS.
The link to my Gitlab repository page is: dataMonitor app, where it is saved the most up to date .click version 0.1.2 (in the folder /build/app).
The very latest commit is important because it is regarding fixing the bug about received bytes from the SIM connection not detected (wi-fi received data monitoring was working since the beginning).
I'd need some help to find out if it is working for you as it is working for me, but please bear in mind the app is UNCONFINED and runs a daemon on the background, so, you never know, better to install it, if you are willing to help, on a test device and not on a daily driver.

I also would like to use this thread to invite the UT community to share ideas and feature requests to improve this app and having it in a better shape to be eventually ready to be published in the OpenStore or integrated in the OS.
I was similarly involved and committed to help with the Linphone app developed by @CiberSheep and Brian and it was a great experience, very exciting and rewarding even if I didn't contribute very much at its development.
I started to work on this app because I felt a modern OS as UT cannot lack in this regard. Also, I read several times on this Forum and on Telegram about people asking for it or complaining for this lack; unfortunately, sometimes the reply to those people was that sure, the data usage monitoring app was missing in the UT OS but they could easily ask their SIM Provider to provide information as a workaround, which I felt a bit unhelpful and insufficient: I don't know your case but in my Country I cannot trust Providers, they are quite nifty so in my humble opinion it is very important to have the ability to monitor the received data on our own, to check on our Providers.

Thank you in advance.

Matteo

P.S. here below some screenshots of the app running on my phone.

@uri even though this is an old revived thread, only to let you know I'm right now working to provide an app bringing such a capability. I'm facing right now some troubles but I'm along the way to solve all those and maybe soon I'll come out with a concept app. Only for your information, the approach in my app is to exploit the API QNetworkConfigurationManager.

Matteo

Hi All,
just to revive this thread, I'd like to inform the Community that the dataMonitor app, object of the present thread, is still in heavy development by me but right now I'm committed in fixing some little glitches and bringing in UI improvements before to update it again on Gitlab to the last version. This version will be a big one, since it will also bring some gestures I worked on during this time I missed from the present thread.
I'd like to share with you some pics of the very latest build:

@rinigus I will try to help you out to package it if none of the most experienced UBports developers will show up....only, this is my last week at work and after I'll have plenty of time next week to dedicate at this scope. I'm not a great developer but I know a little how to package things with clickable even if I didn't manage yet to download and include third party packages in the clickable package, up to now.
Don't worry, somehow we will be your hands and your eyes, in order to have your great app set and working on this platform

@mariogrip All the best wishes to you and your family. The Community needs you in the best shape to move the project further and further but remember that life and family always come first.

I read your post and I felt your pain, which is mine too. I agree with you with the fact that many little bugs ( some of the bugs you reported don't seem to me very little BTW) could have been tackled before. However, we are a small community, and only a bunch of devs among all the community people are active in the development and we cannot expect miracles from them. For this reason, personally I'm struggling to find my way to help the development to improve, with the goal to start from the little bugs. I'm not a dev, I know some coding languages, but never developed for a phone OS. Like me, other people are trying to ride the same route with similar objectives. In the end, in my humble opinion, something is moving in the background, and maybe soon (that's my hope!) there will be self-taught devs who will be able to make this OS always better and better. For all the interested people, we have a discussion group on matrix named Bootcamp, where all the beginners are more than welcome

@Lakota I have BQ Aquaris E5. I installed also Gimp and it seems working good.

@Stefano I also once changed the baseband following the guide on this forum but I didn't notice such an improvement. To be honest I didn't test it so heavily so thank you Stefano to have made us aware of that, I'll certanly flash it back and pay more attention to the behavior. As a final comment, I'd say that if confirmed to be worth the upgrade, it would be great if the latest firmware would be included in the UT image.

@Kanduras Great, it works!! Thank you very much You made my life much easier Now the set Atom/clickable really rocks!

Kind regards to you all @AppLee, @Kanduras and @lduboeuf

Matteo

@wangqinfeng what do you mean by the "Real Machine"? If you mean the UT phone, then probably you'd need to include in your .apparmor file the adequate policy group to grant permission to access the root folder. Have a look at the Apparmor Policy Groups to find out more.

@MadProgrammer hi and welcome here around I'm not a real expert but very recently I started to develop an app for Ubuntu Touch Platform from scratch and without any experience (this app) and what I can tell you is that exploiting the clickable tool we use to compile and deploy the app on the phone is very easy and fast to be soon on track. As an editor you can use whatever you want but I like employing Atom together with clickable, activating a clickable plugin from within the Atom editor, as suggested also by the clickable developer. To learn more about clickable, please visit this link.
If you want to avoid the steep and difficult learning curve I was eager to travel (for my app I needed to learn and employ C++, Qt/QML, bash and javascript), you can develop an app in a pure Qt/QML language which is by far the easiest way to be soon productive; there are some apps you could also use as reference which are only made in Qt/QML (for instance see Palitan). Don't forget to start from a pure QML template, clickable gives at your disposal to be even faster on track, by typing clickable create as your first instance with clickable. Once ready to publish your app, you could as well use clickable and it doesn't even need manual review by third parties if your app is confined.
Enjoy your time with UT.

Cheers.

Matteo

Hi All,
just to revive this thread, I'd like to inform the Community that the dataMonitor app, object of the present thread, is still in heavy development by me but right now I'm committed in fixing some little glitches and bringing in UI improvements before to update it again on Gitlab to the last version. This version will be a big one, since it will also bring some gestures I worked on during this time I missed from the present thread.
I'd like to share with you some pics of the very latest build:

@Stefano does this procedure also work for Pro5 as well? I'm planning to test it, if possible.

@AlainW94 thank you Alain for your attempt anyways...now at least we know it isn't worth to bother anymore with such an issue.

@wdehoog Willem, I started looking around at the references you gave to me. According to an other post in this Forum, it seems the RGB leds are disabled on purpose; see here below the section of the kernel file leds-lp5562.c commented out for this reason:

static struct lp55xx_led_config lp5562_led_config[] = {
	/*{
		.name 		= "R",
		.chan_nr	= 0,
		.led_current	= 20,
		.max_current	= 40,
	},
	{
		.name 		= "G",
		.chan_nr	= 1,
		.led_current	= 20,
		.max_current	= 40,
	},
	{
		.name 		= "B",
		.chan_nr	= 2,
		.led_current	= 20,
		.max_current	= 40,
	},*/
	{
		.name 		= "m86_led",
		.chan_nr	= 0,
		.led_current	= 80,
		.max_current	= 80,
	},
};

I think this is the major culprit for not having any other colors but the white for the RGB led installed on the Meizu Pro5. My question is: how can I flash only this part of the kernel, prior modifying that code to see if it helps to solving that issue?

In regard to the dmesg log, may I ask you what's that for? Only to understand the purpose, generally speaking. I looked for /var/log directory and I found several archived dmesg files but a bit outdated I'd say. However, I'd copied the most up to date dmesg file and in the following link you can find the details: dmesg.log

Please, tell me if you need something else from me. Needless to say, I really appreciate what you are doing

@wdehoog hi Willem, thank you for the suggestions. I searched on the internet and what @UniSuperBox said before about only the white color to be natively available on the Meizu phones seems correct: at least one app does exist on Flyme/Android side able to unleash all the other colors for the Pro5 as well, so maybe also for UT a work-around could be eventually feasible somehow ---------> RGB led notification Flyme

Now, here below the check I made.

phablet@ubuntu-phablet:~$ sudo find /sys -name brightness -ls
     8459      0 -rw-rw----   1 system   system       4096 gen  9 09:06 /sys/devices/virtual/backlight/pwm-backlight.0/brightness
    15318      0 -rw-rw-rw-   1 root     root         4096 gen  9 09:06 /sys/devices/gpioi2c0.14/i2c-12/12-0030/leds/m86_led/brightness
    15238      0 -rw-r--r--   1 root     root         4096 gen  9 09:23 /sys/devices/gpioi2c1.15/i2c-13/13-0063/leds/flash0/brightness
    15252      0 -rw-r--r--   1 root     root         4096 gen  9 09:23 /sys/devices/gpioi2c1.15/i2c-13/13-0063/leds/flash1/brightness
    15266      0 -rw-r--r--   1 root     root         4096 gen  9 09:23 /sys/devices/gpioi2c1.15/i2c-13/13-0063/leds/torch0/brightness
    15280      0 -rw-r--r--   1 root     root         4096 gen  9 09:23 /sys/devices/gpioi2c1.15/i2c-13/13-0063/leds/torch1/brightness

I typed sudo bash -c "echo 1 > /sys/...../brightness" for all of the items listed above but apparently it didn't work; actually, the only consequence I've seen is when I got the usb cable connected powering up the phone with the notification light blinking, just after sending one of those commands the light suddenly disappeared.
The following is what I have got in each of the folders above listed:

phablet@ubuntu-phablet:~$ ls -l /sys/devices/virtual/backlight/pwm-backlight.0/
total 0
-r--r--r-- 1 root   root   4096 gen  9 09:35 actual_brightness
-rw-r--r-- 1 root   root   4096 gen  9 09:35 bl_power
-rw-rw---- 1 system system 4096 gen  9 09:30 brightness
-r--r--r-- 1 root   root   4096 gen  9 09:35 max_brightness
drwxr-xr-x 2 root   root      0 gen  9 09:06 power
lrwxrwxrwx 1 root   root      0 gen  9 09:06 subsystem -> ../../../../class/backlight
-r--r--r-- 1 root   root   4096 gen  9 09:35 type
-rw-r--r-- 1 root   root   4096 gen  9 09:05 uevent

phablet@ubuntu-phablet:~$ ls -l /sys/devices/gpioi2c0.14/i2c-12/12-0030/leds/m86_led/
total 0
-rw-rw-rw- 1 root root 4096 gen  9 09:24 brightness
lrwxrwxrwx 1 root root    0 gen  9 09:37 device -> ../../../12-0030
-rw-r--r-- 1 root root 4096 gen  9 09:37 led_current
-r--r--r-- 1 root root 4096 gen  9 09:37 max_brightness
-r--r--r-- 1 root root 4096 gen  9 09:37 max_current
drwxr-xr-x 2 root root    0 gen  9 09:06 power
lrwxrwxrwx 1 root root    0 gen  9 09:06 subsystem -> ../../../../../../class/leds
-rw-r--r-- 1 root root 4096 gen  9 09:37 trigger
-rw-r--r-- 1 root root 4096 gen  9 09:05 uevent

phablet@ubuntu-phablet:~$ ls -l /sys/devices/gpioi2c1.15/i2c-13/13-0063/leds/flash0/
total 0
-rw-r--r-- 1 root root 4096 gen  9 09:29 brightness
lrwxrwxrwx 1 root root    0 gen  9 09:37 device -> ../../../13-0063
-rw-r--r-- 1 root root 4096 gen  9 09:37 enable
-r--r--r-- 1 root root 4096 gen  9 09:37 max_brightness
-rw-r--r-- 1 root root 4096 gen  9 09:37 onoff
drwxr-xr-x 2 root root    0 gen  9 09:06 power
-rw-r--r-- 1 root root 4096 gen  9 09:37 source
lrwxrwxrwx 1 root root    0 gen  9 09:06 subsystem -> ../../../../../../class/leds
-rw-r--r-- 1 root root 4096 gen  9 09:37 timeout
-rw-r--r-- 1 root root 4096 gen  9 09:37 trigger
-rw-r--r-- 1 root root 4096 gen  9 09:05 uevent

phablet@ubuntu-phablet:~$ ls -l /sys/devices/gpioi2c1.15/i2c-13/13-0063/leds/flash1/
total 0
-rw-r--r-- 1 root root 4096 gen  9 09:29 brightness
lrwxrwxrwx 1 root root    0 gen  9 09:39 device -> ../../../13-0063
-rw-r--r-- 1 root root 4096 gen  9 09:39 enable
-r--r--r-- 1 root root 4096 gen  9 09:39 max_brightness
-rw-r--r-- 1 root root 4096 gen  9 09:39 onoff
drwxr-xr-x 2 root root    0 gen  9 09:06 power
lrwxrwxrwx 1 root root    0 gen  9 09:06 subsystem -> ../../../../../../class/leds
-rw-r--r-- 1 root root 4096 gen  9 09:39 trigger
-rw-r--r-- 1 root root 4096 gen  9 09:05 uevent

phablet@ubuntu-phablet:~$ ls -l /sys/devices/gpioi2c1.15/i2c-13/13-0063/leds/torch0/
total 0
-rw-r--r-- 1 root root 4096 gen  9 09:30 brightness
--w--w---- 1 root root 4096 gen  9 09:40 chip_reg
lrwxrwxrwx 1 root root    0 gen  9 09:40 device -> ../../../13-0063
-rw-r--r-- 1 root root 4096 gen  9 09:40 enable
--w--w---- 1 root root 4096 gen  9 09:40 hwen
-r--r--r-- 1 root root 4096 gen  9 09:40 max_brightness
-rw-r--r-- 1 root root 4096 gen  9 09:40 onoff
drwxr-xr-x 2 root root    0 gen  9 09:06 power
-rw-r--r-- 1 root root 4096 gen  9 09:40 source
lrwxrwxrwx 1 root root    0 gen  9 09:06 subsystem -> ../../../../../../class/leds
-rw-r--r-- 1 root root 4096 gen  9 09:40 trigger
-rw-r--r-- 1 root root 4096 gen  9 09:05 uevent

phablet@ubuntu-phablet:~$ ls -l /sys/devices/gpioi2c1.15/i2c-13/13-0063/leds/torch1/
total 0
-rw-r--r-- 1 root root 4096 gen  9 09:30 brightness
lrwxrwxrwx 1 root root    0 gen  9 09:40 device -> ../../../13-0063
-rw-r--r-- 1 root root 4096 gen  9 09:40 enable
-r--r--r-- 1 root root 4096 gen  9 09:40 max_brightness
-rw-r--r-- 1 root root 4096 gen  9 09:40 onoff
drwxr-xr-x 2 root root    0 gen  9 09:06 power
lrwxrwxrwx 1 root root    0 gen  9 09:06 subsystem -> ../../../../../../class/leds
-rw-r--r-- 1 root root 4096 gen  9 09:40 trigger
-rw-r--r-- 1 root root 4096 gen  9 09:05 uevent

@BlandCorporation Hi, as far as I know, on devel channel you don't need to flash the kernel image anymore because already embedded in the OS image. This step, according to my experience, led to break something (for instance the wifi connection). I didn't try myself yet and I don't know if it will resolve your issue either but I think that the best would be to restart from scratch in the devel channel and skip the part related to flashing the kernel image.

Willem, here below the full unity8 report:

Unity8. log full report

Let me know if you need additional check.

Regards.

Matteo

@wdehoog updated the previous post with the full report. I also saw that 0% charging level....weird indeed. Thank you for your help.