Mobile data usage monitoring (dataMonitor app)

matteo · 10 Oct 2019, 19:19

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.

kristatos · 10 Nov 2019, 07:40

Hey, good idea. What's missing is the labeling of the axes. So for the x-axis it is DOM (day of month) and for the y-axis it's MB, MiB or whatever you're displaying.
I think it's also interesting to see the whole data usage at one sight without to summate the usage of every single day.

matteo · 11 Oct 2019, 11:39

@kristatos thank you for your nice advice: I already planned to implement labels but it is not at the top of my list, speaking for priorities.
In regards to your suggestion about the total data usage, maybe there is a misunderstanding, since the very last column already shows the total usage, you don't have to make a sum of each column, you just have to look at the last one to know how many MBytes you received up to the last day; however, I'm planning to add somewhere a cell with the total MBytes usage written in numbers, to be more clear.

matteo · 24 Jan 2020, 17:53

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:

matteo · 13 Mar 2020, 17:43

I just updated the app on my Gitlab repository (link to this you can find in the first post). The most important feature for me is the introduction of the notifications, which are now triggered in case of exceeding data thresholds. The full change log is below:

-Version 0.1.6-

A new icon has been introduced with the present release (I'm not a great artist so this could be a temporary solution in case somebody else would come up with a better idea);
Added notifications in case of data thresholds exceeding. The code employs the C++ function 'popen' which apparently is the only one I discovered to work seamlessly without killing the daemon ('system' and 'QProcess' were the other two methods tried before);
Added summary at the Main.qml page for SIM and Wi-fi data;
Added the "info" section on the up right corner, close to "settings";
Merged early translation to spanish thanks to @Krakakanov (new additional strings to be translated have been added since then);
Added translation to italian thanks to...me;
Added gestures to interact with the graph:
- Scroll down/up with two fingers to enlarge/narrow the 'MBytes' data range;
- Press and hold with one finger to create a new data threshold object;
Added 'BottomEdge' section to store the list of the created data thresholds. In this section you can:
- Drag the data threshold row towards right, to delete the data threshold;
- Drag the data threshold row towards left, to mute the notification for the concerned threshold;
Added labels for 'Mbytes' and 'Days of Month';
Fixed 'Mbytes' data steps to be consistent between the Vertical and Horizontal view and to fill all the space at its disposal;
Fixed bug occurring when the date passed from one day to the day after, not calculating the received data in a correct way;
Added message on the middle of the page to inform about data unavailability when opening a graph with no data yet;
Added message on the middle of the 'BottomEdge' page to inform about thresholds unavailability when no data thresholds yet.

geekvine · 13 Mar 2020, 20:52

i do pay as you go so this is invaluable for me, thank you.

Giiba · 13 Mar 2020, 21:52

For the life of me I can find no /build/app folder. Am I missing something obvious?

AppLee · 13 Mar 2020, 22:08

@Giiba
You need to install and run clickable to build the app
The /build/app/ is then created

I just tried a clickable build but failed with "install" in Makefile, so I guess installation of the daemon is done whithin the Makefile and the client is installed using clickable.
I'll try tomorrow to plug the phone and see if I can build and install the app on the PinePhone.

matteo · 14 Mar 2020, 08:00

@AppLee and @geekvine and @Giiba you need to build the binary first before to compile the clickable app.
So, once installed the dataMonitor folder into your local directory, you first need to run clickable build-libs to compile the file Actiondaemon.cpp. Only after that, you are ready to run clickable with your phone connected to your PC to compile the whole project.
Thank you for your interest BTW. Any feedback from you on the app behavior is highly appreciated

Matteo

matteo · 14 Mar 2020, 12:08

@AppLee and @Giiba since you are trying to build the app from source, it's worth to inform you I made slight modifications to the two .conf files used for the daemon functionality. Those will be included in the next ver. 0.1.7. The reason is that I'm tring to find the most functional code for the daemon. Just to briefly explain, the mattdaemon-service is only meant to get triggered once at the purpose of switching the first boot code path to the after-boot code path the Actiondaemon binary shall follow. I recommend you to change locally the two .conf files according to the below reported new files. If you already built the app before, then you need to go first to settings and to push the "remove daemon" button; after that, you need to exit from the app and you can rebuild it (this time you only need to build the qml part, since the C++ library remained unchanged) and in the end to reboot the phone. You can find the two .conf file in the dataMonitor/daemon folder.

EDIT: sorry, I needed to remove the previous attached .conf files for the daemon activity, since I find out there is still some improvements to give to those. I will report back as soon as possible, when I'll find the most convenient way to express those. In the meantime, the 0.1.6 version is working for me to test the app.
A recommendation: test this app only on a secondary device, not on a daily driver, since it is still experimental (even if widely tested by me) and in case of any undesirable occurrence you will not lose any data and you can safely recover from scratch. Thank you.

ricardo65 · 15 Mar 2020, 20:10

@matteo Ubuntu Pastebin
Paste from Ubuntu Touch User at Sun, 15 Mar 2020 20:08:13 +0000
Download as text

code_text
```1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
All fired notifications have been reset for the current month.
qml: Received Mbytes: 0 MB
Today updated bytes for "SIM" connection is: 0 MB
file:///opt/click.ubuntu.com/datamonitor.matteobellei/current/qml/StorageThresholds.js:121: Error: no such table: chartYdata Unable to execute statement
Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
Creating a QMirClientScreen now
"20:57:06"
Platform is capable of data statistics for available connections.
"ciudadrealfibra_nkbiw6"
"WLAN"
"/org/freedesktop/NetworkManager/Settings/0"
Session is open!
Session connected!
"Orange Internet Móvil"
"LTE"
"/org/freedesktop/NetworkManager/Settings/1"
Session is open!
Session connected!
qml: Received Mbytes: 21.53868293762207 MB
Today updated bytes for "WIFI" connection is: 1940.21 MB
file:///opt/click.ubuntu.com/datamonitor.matteobellei/current/qml/StorageThresholds.js:121: Error: no such table: chartYdata Unable to execute statement
Today there are no stored bytes yet for "SIM" connection
file:///opt/click.ubuntu.com/datamonitor.matteobellei/current/qml/StorageThresholds.js:121: Error: no such table: chartYdata Unable to execute statement
All fired notifications have been reset for the current month.
qml: Received Mbytes: 0 MB
Today updated bytes for "SIM" connection is: 0 MB
file:///opt/click.ubuntu.com/datamonitor.matteobellei/current/qml/StorageThresholds.js:121: Error: no such table: chartYdata Unable to execute statement
Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
Creating a QMirClientScreen now
"20:58:47"
Platform is capable of data statistics for available connections.
"ciudadrealfibra_nkbiw6"
"WLAN"
"/org/freedesktop/NetworkManager/Settings/0"
Session is open!
Session connected!
"Orange Internet Móvil"
"LTE"
"/org/freedesktop/NetworkManager/Settings/1"
Session is open!
Session connected!
qml: Received Mbytes: 22.031439781188965 MB
Today updated bytes for "WIFI" connection is: 1940.7 MB
file:///opt/click.ubuntu.com/datamonitor.matteobellei/current/qml/StorageThresholds.js:121: Error: no such table: chartYdata Unable to execute statement
Today there are no stored bytes yet for "SIM" connection
file:///opt/click.ubuntu.com/datamonitor.matteobellei/current/qml/StorageThresholds.js:121: Error: no such table: chartYdata Unable to execute statement
All fired notifications have been reset for the current month.
qml: Received Mbytes: 0 MB
Today updated bytes for "SIM" connection is: 0 MB
file:///opt/click.ubuntu.com/datamonitor.matteobellei/current/qml/StorageThresholds.js:121: Error: no such table: chartYdata Unable to execute statement
Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
Creating a QMirClientScreen now
"21:00:28"
Platform is capable of data statistics for available connections.
"ciudadrealfibra_nkbiw6"
"WLAN"
"/org/freedesktop/NetworkManager/Settings/0"
Session is open!
Session connected!
"Orange Internet Móvil"
"LTE"
"/org/freedesktop/NetworkManager/Settings/1"
Session is open!
Session connected!
qml: Received Mbytes: 22.2943115234375 MB
Today updated bytes for "WIFI" connection is: 1940.97 MB
file:///opt/click.ubuntu.com/datamonitor.matteobellei/current/qml/StorageThresholds.js:121: Error: no such table: chartYdata Unable to execute statement
Today there are no stored bytes yet for "SIM" connection
file:///opt/click.ubuntu.com/datamonitor.matteobellei/current/qml/StorageThresholds.js:121: Error: no such table: chartYdata Unable to execute statement
All fired notifications have been reset for the current month.
qml: Received Mbytes: 0 MB
Today updated bytes for "SIM" connection is: 0 MB
file:///opt/click.ubuntu.com/datamonitor.matteobellei/current/qml/StorageThresholds.js:121: Error: no such table: chartYdata Unable to execute statement
Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
Creating a QMirClientScreen now
"21:02:09"
Platform is capable of data statistics for available connections.
"ciudadrealfibra_nkbiw6"
"WLAN"
"/org/freedesktop/NetworkManager/Settings/0"
Session is open!
Session connected!
"Orange Internet Móvil"
"LTE"
"/org/freedesktop/NetworkManager/Settings/1"
Session is open!
Session connected!
qml: Received Mbytes: 22.62652587890625 MB
Today updated bytes for "WIFI" connection is: 1941.3 MB
file:///opt/click.ubuntu.com/datamonitor.matteobellei/current/qml/StorageThresholds.js:121: Error: no such table: chartYdata Unable to execute statement
Today there are no stored bytes yet for "SIM" connection
file:///opt/click.ubuntu.com/datamonitor.matteobellei/current/qml/StorageThresholds.js:121: Error: no such table: chartYdata Unable to execute statement
All fired notifications have been reset for the current month.
qml: Received Mbytes: 0 MB
Today updated bytes for "SIM" connection is: 0 MB
file:///opt/click.ubuntu.com/datamonitor.matteobellei/current/qml/StorageThresholds.js:121: Error: no such table: chartYdata Unable to execute statement
Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
Creating a QMirClientScreen now
"21:03:50"
Platform is capable of data statistics for available connections.
"ciudadrealfibra_nkbiw6"
"WLAN"
"/org/freedesktop/NetworkManager/Settings/0"
Session is open!
Session connected!
"Orange Internet Móvil"
"LTE"
"/org/freedesktop/NetworkManager/Settings/1"
Session is open!
Session connected!
qml: Received Mbytes: 23.010136604309082 MB
Today updated bytes for "WIFI" connection is: 1941.68 MB
file:///opt/click.ubuntu.com/datamonitor.matteobellei/current/qml/StorageThresholds.js:121: Error: no such table: chartYdata Unable to execute statement
Today there are no stored bytes yet for "SIM" connection
file:///opt/click.ubuntu.com/datamonitor.matteobellei/current/qml/StorageThresholds.js:121: Error: no such table: chartYdata Unable to execute statement
All fired notifications have been reset for the current month.
qml: Received Mbytes: 0 MB
Today updated bytes for "SIM" connection is: 0 MB
file:///opt/click.ubuntu.com/datamonitor.matteobellei/current/qml/StorageThresholds.js:121: Error: no such table: chartYdata Unable to execute statement
Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
Creating a QMirClientScreen now
"21:05:31"
Platform is capable of data statistics for available connections.
"Orange Internet Móvil"
"LTE"
"/org/freedesktop/NetworkManager/Settings/1"
Session is open!
Session connected!
Today there are no stored bytes yet for "SIM" connection
file:///opt/click.ubuntu.com/datamonitor.matteobellei/current/qml/StorageThresholds.js:121: Error: no such table: chartYdata Unable to execute statement
All fired notifications have been reset for the current month.
qml: Received Mbytes: 0 MB
Today updated bytes for "SIM" connection is: 0 MB
file:///opt/click.ubuntu.com/datamonitor.matteobellei/current/qml/StorageThresholds.js:121: Error: no such table: chartYdata Unable to execute statement
Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
Creating a QMirClientScreen now
"21:07:12"
Platform is capable of data statistics for available connections.
"Orange Internet Móvil"
"LTE"
"/org/freedesktop/NetworkManager/Settings/1"
Session is open!
Session connected!
Today there are no stored bytes yet for "SIM" connection
file:///opt/click.ubuntu.com/datamonitor.matteobellei/current/qml/StorageThresholds.js:121: Error: no such table: chartYdata Unable to execute statement
All fired notifications have been reset for the current month.
qml: Received Mbytes: 0 MB
Today updated bytes for "SIM" connection is: 0 MB
file:///opt/click.ubuntu.com/datamonitor.matteobellei/current/qml/StorageThresholds.js:121: Error: no such table: chartYdata Unable to execute statement

code_text

Download as text

ricardo65 · 15 Mar 2020, 20:15

@matteo ![alt text]( image url)

Lakotaubp · 15 Mar 2020, 20:30

ricardo65 a day ago

i have installed version 0.1.6 in oneplus one and the data consumption via sim does not appear, you can only see the consumption via wifi

geekvine · 16 Mar 2020, 02:05

@matteo don't worry i tested a REALLY early build, i'll provide some feedback within a few days when i get a chance to compile the latest source.

matteo · 16 Mar 2020, 12:01

@ricardo65 Ricardo, thank you for providing the log. What I noticed is that regardless of the connection type (SIM or Wifi) you got that strange error related to Error: no such table: chartYdata Unable to execute statement. This sometimes happened to me also, but a reboot fixed that without additional troubles. Did you try to reboot?
Also, I need to ask you to type the following command in the terminal, after your SIM connection is fully working: ifconfig -a and report the log here.
Please follow the discussion about this issue reported in my dataMonitor Gitlab page ---->Issue #1
to understand what's going on with your phone and why you don't have apparently SIM data reception.

ricardo65 · 16 Mar 2020, 16:44

@matteo

code_text
```phablet@ubuntu-phablet:~$ ifconfig -a
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:76 errors:0 dropped:0 overruns:0 frame:0
          TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:6269 (6.2 KB)  TX bytes:6269 (6.2 KB)

p2p0      Link encap:Ethernet  HWaddr b2:aa:33:88:88:88  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

rev_rmnet0 Link encap:Ethernet  HWaddr ae:41:1a:3f:35:0f  
          BROADCAST MULTICAST  MTU:2000  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

rev_rmnet1 Link encap:Ethernet  HWaddr d2:50:a2:71:42:7e  
          BROADCAST MULTICAST  MTU:2000  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

rev_rmnet2 Link encap:Ethernet  HWaddr fe:5f:ff:d3:e9:dc  
          BROADCAST MULTICAST  MTU:2000  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

rev_rmnet3 Link encap:Ethernet  HWaddr da:f7:b7:30:9c:79  
          BROADCAST MULTICAST  MTU:2000  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

rev_rmnet4 Link encap:Ethernet  HWaddr ba:40:12:ae:f8:0d  
          BROADCAST MULTICAST  MTU:2000  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

rev_rmnet5 Link encap:Ethernet  HWaddr 92:75:52:cd:48:5a  
          BROADCAST MULTICAST  MTU:2000  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

rev_rmnet6 Link encap:Ethernet  HWaddr 9e:4a:09:99:08:31  
          BROADCAST MULTICAST  MTU:2000  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

rev_rmnet7 Link encap:Ethernet  HWaddr ba:2a:89:e0:66:1e  
          BROADCAST MULTICAST  MTU:2000  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

rev_rmnet8 Link encap:Ethernet  HWaddr c6:86:ce:7a:ca:69  
          BROADCAST MULTICAST  MTU:2000  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

rmnet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          inet addr:10.130.201.17  Mask:255.255.255.0
          UP RUNNING  MTU:1500  Metric:1
          RX packets:3956 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2188 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:4260009 (4.2 MB)  TX bytes:219876 (219.8 KB)

rmnet1    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          [NO FLAGS]  MTU:2000  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

rmnet2    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          [NO FLAGS]  MTU:2000  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

rmnet3    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          [NO FLAGS]  MTU:2000  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

rmnet4    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          [NO FLAGS]  MTU:2000  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

rmnet5    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          [NO FLAGS]  MTU:2000  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

rmnet6    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          [NO FLAGS]  MTU:2000  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

rmnet7    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          [NO FLAGS]  MTU:2000  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

rmnet_usb0 Link encap:Ethernet  HWaddr 7e:bd:10:2b:28:dd  
          BROADCAST MULTICAST  MTU:2000  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

sit0      Link encap:IPv6-in-IPv4  
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0     Link encap:Ethernet  HWaddr b0:aa:33:88:88:88  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

code_text

matteo · 16 Mar 2020, 18:39

@ricardo65 please next time use either an external service to paste such long reports, for instance Pastebin Ubuntu is what we usually prefer to employ, or you could embed your report between code tags (the symbol </> you can find above the text field during message composition). This because it's easier for anyone to read and following these simple rules we avoid too much noise in the present thread.
To come to your output, it seems similar to my Pro5 output....but I don't see any ril_0/ril_1 gsm connections....are you sure you have your SIM card inserted and proved working? Please show me also the output of: nmcli device status both when the SIM is inside and after you pulled it out, if possible. Thank you.

Lakotaubp · 16 Mar 2020, 18:42

@matteo That should help

matteo · 16 Mar 2020, 18:43

@Lakotaubp great! Thank you...much better now

ricardo65 · 16 Mar 2020, 18:49

@matteo said in Mobile data usage monitoring (dataMonitor app):

@Lakotaubp great! Thank you...much better now

I beg your pardon, I don't know how to do as many things as you do, I like this whole world and ubuntu touch but I don't know half as many commands as you all