Ask / Submit
17

Unwanted network traffic (Mobile Data Counter per App missing in Sailfish

Tracked by Jolla

asked 2018-06-01 23:43:56 +0300

neo75 gravatar image

updated 2018-08-18 11:45:23 +0300

Hi Sailors, is there some Sailfish mobile data counter app, which can show me, mobile data consumption/traffic per each running application? I know, there is Settings/Data counters, but it shows only total amounts of data, without any details.

I am asking, because I have some serious data leak (about 50 MB sent data per hour), and I cannot find the app, which is using mobile data extensively. I have uninstalled all android apps, even Android Support, left only standard Jolla apps in the phone, restarted several times, but sending/traffic data remains.

Strange following behaviour I found: When my mobile data limit at local operator is reached and even wi-fi is on, than every exactly 5 minutes a brower window come out and shows redirected page to local operator telling I am out of my mobile data. And this repeats avery 5 minutes. It means that the phone wants to touch the mobile connection even wi-fi is on and working correctly.

Down below this page I have dumped in terminal output of "ps -A" and also "netstat -tupc" as root in developer mode. If anyone understands it, plese take a look at that.

UPDATE 10.6.2018: It seems, that finely doing "Reset device" and update to latest Mouhijoki 2.2.0.29 problem resolved.

UPDATE 18.8.2018: Now the problem is back. The phone is sending about 20 MB per hour, consuming all mobile data very quickly. The android support is stopped. Can anyone help? I can use tcpdump or netstat. I just want to kill the process, which is sending data away.

edit retag flag offensive close delete

Comments

2

Short answer;

no.

Edz ( 2018-06-01 23:51:46 +0300 )edit

Thanks. And what about to use some app from Aptoide Store? I see there some Data counter apps. Will it work?

neo75 ( 2018-06-01 23:57:39 +0300 )edit
1

Good point, I forgot about Android apps, mainly because I don't use them.

Android apps can be very hit and miss when used on SailfishOS, best thing to do is bite the bullet and try them.

I suppose you could try Lighthouse from Openrepos, this may help to show you what is running on your device and consuming your data.

working on 2.2.0.29 https://openrepos.net/content/almindor/lighthouse

Edz ( 2018-06-02 00:57:30 +0300 )edit

Thank you! I am new user of SailfishX and never used Openrepos before. Should I be scared of what is written here by Jolla? https://jolla.zendesk.com/hc/en-us/articles/202398218?mobile_site=true They do not recommend the use.

neo75 ( 2018-06-03 11:26:25 +0300 )edit
4

Jolla are covering their own arses by making such statements and rightly so, as ALL apps on Openrepos are not going through any kind of QA (quality assurance).

Personally, I have no qualms about using Openrepos and I am also a fairly regular contributor and I offer several apps/patches, but as with anything made by human beings, there are occasional problems and what might work for one person/device, may not work for another.

As you can see by my last comment, Lighthouse is working as expected on my device under the latest OS release (2.2.0.29).

Personally, I see more risk crossing the road than I do using Openrepos....oh and any potentially malicious apps soon get ousted. We had one such case where a torch app was collecting use data not personal data, but in no time at all, the developer had pulled it from the Openrepos due to pressure from other users/uploaders.

I recommend using Storeman for browsing Openrepos, but of course, Storeman is found on Openrepos also.

For what it is worth, I spend far more time on and using Openrepos than I ever do on Jolla Store which may be safe due to QA but the store is full of shitty boring useless Android apps and no notifications are given to devs when they have comments on their apps. I have 1 app on Jolla Store and several on Openrepos.

If you rely on Jolla Store for apps/games etc, personally I think your device will be a bit dull and boring after a short while, whereas all the nice/clever/fun/experimental apps are on Openrepos. Use at your own risk like anything else in life - there are no guarantees, even Jolla get it wrong from time to time and cause devices to be bricked; maybe openrepos should issue the same statement about Jolla Store :D

Edz ( 2018-06-03 11:38:38 +0300 )edit

4 Answers

Sort by » oldest newest most voted
5

answered 2018-06-06 12:01:16 +0300

jlaakkonen gravatar image

updated 2018-06-06 13:41:47 +0300

jovirkku gravatar image

Here is one way to find out what applications are connected over network.

If you enable developer mode and gain access to terminal, write devel-su in terminal to become root (which will ask the password set when enabling developer mode via settings) and then write netstat -ntupce in terminal to see the status of your network connections. If you want to display the hostnames instead of IP addresses use netstat -tupce.

netstat will list the programs with their process ids and both local and foreign addresses they are connected to. With the c parameter the list is continuously updated. This will help at least to find out the program that sends data, as send queues and receive queues are also shown. Also, the user identifier is shown, if it is 0 then it is root (system), 100000 is you, the Sailfish OS user (corresponds to user nemo on the device). To exit netstat press Ctrl+C.

If the application is not shown in the listing and traffic still goes out, then it needs to be inspected further.

Edit: the listing usually contains connmand (connectivity daemon) and systemd (system daemon), which are Sailfish OS system services.

edit flag offensive delete publish link more

Comments

Thank you very much! I have successfuly activated developer mode. Instaled ToeTerm from Openrepos. The command 'netstat -tupce' is working correctly, and shows many processes. But I just I cannot enter the root mode. Command 'devel-su' works, I enter the same password (not being shown on term) and it echoes Auth failed. My fault may be. I will experiment a little, but thanks a lot! I like these Linux commands:-)

neo75 ( 2018-06-06 21:23:07 +0300 )edit

Wrong password I entered. Now its OK. In Settings/Developer tools must be activated "Remote connection". Now I can enter the root mode by "devel-su" correctly. I will try to dump "ps -A" and also to dump "netstat -tupc" and publish it here. Hope it helps.

neo75 ( 2018-06-06 23:12:16 +0300 )edit

So here is the dump of command "netstat -ntupe" under root:

Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 1 100.82.125.193:58618 10.144.134.134:http FIN_WAIT1 root 0 -
tcp 0 1 100.82.125.193:42994 10.144.134.142:http FIN_WAIT1 root 0 -
tcp 0 0 100.82.125.193:43012 10.144.134.142:http CLOSE_WAIT root 39244 3011/connmand
tcp 0 1 100.82.125.193:55104 93-153-117-134.tmcz.cz:http FIN_WAIT1 root 0 -
tcp 0 517 100.82.125.193:45496 40.101.9.178:imaps ESTABLISHED nemo 37784 2621/messageserver5 tcp 0 0 100.82.125.193:39727 ec2-52-49-103-21.eu-we:http CLOSE_WAIT root 39233 3011/connmand
tcp 0 0 100.82.125.193:55585 93-153-117-138.tmcz.cz:http ESTABLISHED nemo 39169 5099/sailfish-brows tcp 0 0 100.82.125.193:45682 93-153-117-138.tmcz.c:https TIME_WAIT root 0 -
tcp 0 221 100.82.125.193:48987 ec2-52-30-196-99.eu-w:https ESTABLISHED nemo 39107 5099/sailfish-brows tcp 0 1 100.82.125.193:55103 93-153-117-134.tmcz.cz:http FIN_WAIT1 root 0 -
tcp 0 1 100.82.125.193:55102 93-153-117-134.tmcz.cz:http FIN_WAIT1 root 0 -
tcp 0 1 100.82.125.193:55114 93-153-117-134.tmcz.cz:http FIN_WAIT1 root 0 -
udp 0 0 100.82.125.193:36025 93-153-117-17.tm:domain ESTABLISHED root 25219 3011/connmand
udp 0 0 100.82.125.193:55494 93-153-117-17.tm:domain ESTABLISHED root 25213 3011/connmand
udp 0 0 100.82.125.193:41623 93-153-117-17.tm:domain ESTABLISHED root 39228 3011/connmand
udp 0 0 localhost.localdomain:39795 localhost.locald:domain ESTABLISHED root 25215 3011/connmand
udp 0 0 100.82.125.193:39857 93-153-117-49.tm:domain ESTABLISHED root 25217 3011/connmand
udp 0 0 100.82.125.193:58389 93-153-117-49.tm:domain ESTABLISHED root 25211 3011/connmand
udp 0 0 100.82.125.193:42023 93-153-117-49.tm:domain ESTABLISHED root 39226 3011/connmand
udp 0 0 localhost6.locald:38404 localhost6.local:domain ESTABLISHED root 25216 3011/connmand

neo75 ( 2018-06-06 23:39:24 +0300 )edit

And here is dump of command "ps -A" under root:

PID TTY TIME CMD 1 ? 00:00:02 systemd 2 ? 00:00:00 kthreadd 3 ? 00:00:00 ksoftirqd/0 5 ? 00:00:00 kworker/0:0H 6 ? 00:00:02 kworker/u12:0 7 ? 00:00:00 rcu_preempt 8 ? 00:00:00 rcu_bh 9 ? 00:00:00 rcu_sched 10 ? 00:00:00 migration/0 11 ? 00:00:00 migration/1 12 ? 00:00:00 ksoftirqd/1 14 ? 00:00:00 kworker/1:0H 15 ? 00:00:00 migration/2 16 ? 00:00:00 ksoftirqd/2 18 ? 00:00:00 kworker/2:0H 19 ? 00:00:00 migration/3 20 ? 00:00:00 ksoftirqd/3 21 ? 00:00:00 kworker/3:0 22 ? 00:00:00 kworker/3:0H 23 ? 00:00:00 migration/4 24 ? 00:00:00 ksoftirqd/4 25 ? 00:00:00 kworker/4:0 26 ? 00:00:00 kworker/4:0H 27 ? 00:00:00 migration/5 28 ? 00:00:00 ksoftirqd/5 30 ? 00:00:00 kworker/5:0H 31 ? 00:00:00 khelper 32 ? 00:00:00 kdevtmpfs 33 ? 00:00:00 netns 34 ? 00:00:00 perf 37 ? 00:00:00 kworker/3:1 38 ? 00:00:00 kworker/4:1 40 ? 00:00:00 kworker/0:1 41 ? 00:00:00 kworker/0:1H 42 ? 00:00:00 smd_channel_clo 43 ? 00:00:00 smsm_cb_wq 44 ? 00:00:00 kworker/u12:1 45 ? 00:00:00 deferwq 46 ? 00:00:01 kworker/u13:0 47 ? 00:00:00 rpm-smd 48 ? 00:00:00 kworker/u13:1 49 ? 00:00:00 irq/47-cpr 50 ? 00:00:00 irq/51-cpr 51 ? 00:00:00 mpm 52 ? 00:00:00 kworker/u12:2 53 ? 00:00:00 irq/346-cpr 54 ? 00:00:00 writeback 55 ? 00:00:00 bioset 56 ? 00:00:00 crypto 57 ? 00:00:00 kblockd 58 ? 00:00:00 khubd 59 ? 00:00:00 system 60 ? 00:00:00 ipa_power_mgmt 61 ? 00:00:00 sps_ipa_power_m 62 ? 00:00:00 ipawq14 63 ? 00:00:00 iparepwq14 64 ? 00:00:00 ipawq45 65 ? 00:00:00 iparepwq45 66 ? 00:00:00 ipawq13 67 ? 00:00:00 iparepwq13 68 ? 00:00:00 ipa_power_mgmt 69 ? 00:00:00 ipa_rm_wq 70 ? 00:00:00 ipa_interrupt_w 71 ? 00:00:00 irq/75-msm_iomm 72 ? 00:00:00 irq/73-msm_iomm 73 ? 00:00:00 irq/272-msm_iom 74 ? 00:00:00 irq/273-msm_iom 75 ? 00:00:00 irq/274-msm_iom 76 ? 00:00:00 irq/286-msm_iom 77 ? 00:00:00 irq/287-msm_iom 78 ? 00:00:00 irq/85-msm_iomm 79 ? 00:00:00 irq/86-msm_iomm 80 ? 00:00:00 irq/90-msm_iomm 81 ? 00:00:00 irq/92-msm_iomm 82 ? 00:00:00 irq/93-msm_iomm 83 ? 00:00:00 irq/108-msm_iom 84 ? 00:00:00 irq/109-msm_iom 85 ? 00:00:00 irq/112-msm_iom 86 ? 00:00:00 irq/126-msm_iom 87 ? 00:00:00 irq/133-msm_iom 88 ? 00:00:00 irq/134-msm_iom 89 ? 00:00:00 irq/137-msm_iom 90 ? 00:00:00 irq/138-msm_iom 91 ? 00:00:00 irq/141-msm_iom 92 ? 00:00:00 irq/142-msm_iom 93 ? 00:00:00 irq/143-msm_iom 94 ? 00:00:00 irq/144-msm_iom 95 ? 00:00:00 irq/145-msm_iom 96 ? 00:00:00 irq/146-msm_iom 97 ? 00:00:00 irq/147-msm_iom 98 ? 00:00:00 irq/148-msm_iom 99 ? 00:00:00 irq/149-msm_iom 100 ? 00:00:00 irq/150-msm_iom 101 ? 00:00:00 irq/151-msm_iom 102 ? 00:00:00 irq/152-msm_iom 103 ? 00:00:00 devfreq_wq 104 ? 00:00:00 cfg80211 105 ? 00:00:00 irq/406-bcl_vba 106 ? 00:00:00 irq/405-bcl_iba 129 ? 00:00:00 power_off_alarm 130 ? 00:00:00 kswapd0 131 ? 00:00:00 fsnotify_mark 132 ? 00:00:00 ecryptfs-kthrea 133 ? 00:00:00 bioset 153 ? 00:00:00 rot_commit_work 154 ? 00:00:00 mdss_dsi_event 155 ? 00:00:00 mdss_dsi_dba 156 ? 00:00:00 unblanker 157 ? 00:00:00 apr_driver 158 ? 00:00:00 pil_vote_wq 159 ? 00:00:00 mem_share_svc 160 ? 00:00:00 qmi_hndl0000000 161 ? 00:00:00 msm_ipc_router 162 ? 00:00:00 pacman_qmi_noti 163 ? 00:00:00 pacman_qmi_rx_w 164 ? 00:00:00 qmi_svc_event_w 165 ? 00:00:00 k_hsuart 166 ? 00:00:00 msm_serial_hs_0 167 ? 00:00:00 msm_serial_hs_0 168 ? 00:00:00 hwrng 169 ? 00:00:00 diag_real_time_ 170 ? 00:00:00 diag_wq 171 ? 00:00:00 DIAG_USB_diag 172 ? 00:00:00 DIAG_SMD_MODEM_ 173 ? 00:00:00 DIAG_SMD_MODEM_ 174 ? 00:00:00 DIAG_SMD_MODEM_ 175 ? 00:00:00 DIAG_SMD_MODEM_ 176 ? 00:00:00 DIAG_SMD_MODEM_ 177 ? 00:00:00 DIAG_SMD_LPASS_ 178 ? 00:00:00 DIAG_SMD_LPASS_ 179 ? 00:00:00 DIAG_SMD_LPASS_ 180 ? 00:00:00 DIAG_SMD_LPASS_ 181 ? 00:00:00 DIAG_SMD_LPASS_ 182 ? 00:00:00 DIAG_SMD_WCNSS_ 183 ? 00:00:00 DIAG_SMD_WCNSS_ 184 ? 00:00:00 DIAG_SMD_WCNSS_ 185 ? 00:00:00 DIAG_SMD_WCNSS_ 186 ? 00:00:00 DIAG_SMD_WCNSS_ 187 ? 00:00:00 DIAG_SMD_SENSOR 188 ? 00:00:00 DIAG_SMD_SENSOR 189 ? 00:00:00 DIAG_SMD_SENSOR 190 ? 00:00:00 DIAG_SMD_SENSOR 191 ? 00:00:00 DIAG_SMD_SENSOR 192 ? 00:00:00 DIAG_SOCKMODEM_ 193 ? 00:00:00 DIAG_SOCKMODEM_ 194 ? 00:00:00 DIAG_SOCKMODEM_ 195 ? 00:00:00 kworker/u12:3 196 ? 00:00:00 DIAG_SOCKMODEM_ 197 ? 00:00:01 kworker/u12:4 198 ? 00:00:00 DIAG_SOCKMODEM_ 199 ? 00:00:00 DIAG_SOCKLPASS_ 201 ? 00:00:00 DIAG_SOCKLPASS_ 203 ? 00:00:00 DIAG_SOCKLPASS_ 204 ? 00:00:00 DIAG_SOCKLPASS_ 205 ? 00:00:01 kworker/u12:7 206 ? 00:00:00 DIAG_SOCKLPASS_ 207 ? 00:00:00 DIAG_SOCKWCNSS_ 208 ? 00:00:01 kworker/u12:8 209 ? 00:00:00 DIAG_SOCKWCNSS_ 210 ? 00:00:00 DIAG_SOCKWCNSS_ 211 ? 00:00:00 DIAG_SOCKWCNSS_ 212 ? 00:00:00 DIAG_SOCKWCNSS_ 213 ? 00:00:00 DIAG_SOCKSENSOR 214 ? 00:00:00 DIAG_SOCKSENSOR 215 ? 00:00:00 DIAG_SOCKSENSOR 216 ? 00:00:00 DIAG_SOCKSENSOR 217 ? 00:00:00 DIAG_SOCKSENSOR 218 ? 00:00:00 DIAG_CNTL_SOCKE 219 ? 00:00:00 diag_cntl_wq 220 ? 00:00:00 diag_dci_wq 221 ? 00:00:00 kgsl-3d0 222 ? 00:00:00 kgsl-events 223 ? 00:00:00 governor_msm_ad 224 ? 00:00:00 kgsl_devfreq_wq 225 ? 00:00:00 proximity_als 226 ? 00:00:00 qcrypto_seq_res 247 ? 00:00:00 usbnet 248 ? 00:00:00 sharedmem_qmi_w 249 ? 00:00:00 qmi_hndl0000000 250 ? 00:00:00 k_gserial 251 ? 00:00:00 uether 252 ? 00:00:00 irq/414-fpc1145 255 ? 00:00:00 msm_cci_wq 256 ? 00:00:00 msm_cci_wq 257 ? 00:00:00 msm_cpp_workque 258 ? 00:00:00 kworker/4:2 259 ? 00:00:00 irq/401-batt-mi 260 ? 00:00:00 therm_core:noti 261 ? 00:00:00 chg_apsd 262 ? 00:00:00 kworker/5:2 263 ? 00:00:00 id_poll_q 264 ? 00:00:00 kworker/5:3 265 ? 00:00:00 therm_core:noti 266 ? 00:00:00 irq/365-chg-err 267 ? 00:00:00 irq/371-chg-tap 268 ? 00:00:00 irq/372-chg-tcc 269 ? 00:00:00 irq/370-chg-rec 270 ? 00:00:00 irq/369-chg-p2f 271 ? 00:00:00 irq/375-usbid-c 272 ? 00:00:00 irq/374-otg-oc 273 ? 00:00:00 irq/373-otg-fai 274 ? 00:00:00 irq/376-batt-ho 275 ? 00:00:00 irq/377-batt-wa 276 ? 00:00:00 irq/379-batt-co 277 ? 00:00:00 irq/378-batt-co 278 ? 00:00:00 irq/382-batt-mi 279 ? 00:00:00 irq/381-batt-lo 280 ? 00:00:00 irq/384-usbin-u 281 ? 00:00:00 irq/14-usbin-ov 282 ? 00:00:00 irq/15-usbin-sr 283 ? 00:00:00 irq/385-aicl-do 284 ? 00:00:00 irq/10-dcin-uv 285 ? 00:00:00 irq/386-power-o 286 ? 00:00:00 irq/387-temp-sh 287 ? 00:00:00 irq/6-wdog-time 288 ? 00:00:00 therm_core:noti 289 ? 00:00:00 therm_core:noti 290 ? 00:00:00 therm_core:noti 291 ? 00:00:00 therm_core:noti 292 ? 00:00:00 therm_core:noti 293 ? 00:00:00 therm_core:noti 294 ? 00:00:00 therm_core:noti 295 ? 00:00:00 therm_core:noti 296 ? 00:00:00 therm_core:noti 297 ? 00:00:00 therm_core:noti 298 ? 00:00:00 therm_core:noti 299 ? 00:00:00 therm_core:noti 300 ? 00:00:00 therm_core:noti 301 ? 00:00:00 therm_core:noti 302 ? 00:00:00 therm_core:noti 303 ? 00:00:00 therm_core:noti 304 ? 00:00:00 irq/216-tsens_i 305 ? 00:00:00 therm_core:noti 306 ? 00:00:00 therm_core:noti 307 ? 00:00:00 therm_core:noti 308 ? 00:00:00 dm_bufio_cache 309 ? 00:00:00 bt_drv 310 ? 00:00:00 fm_drv_tx 311 ? 00:00:00 fm_drv_rx 312 ? 00:00:03 cfinteractive 313 ? 00:00:00 irq/170-7824900 314 ? 00:00:00 irq/253-7864900 315 ? 00:00:00 irq/352-7864900 316 ? 00:00:00 irq/329-7a24900 317 ? 00:00:01 mmc-cmdqd/0 318 ? 00:00:00 mmcqd/0rpmb 319 ? 00:00:00 kworker/1:2 320 ? 00:00:00 irq/409-qpnp_wl 321 ? 00:00:00 irq/224-spdm_bw 322 ? 00:00:00 binder 323 ? 00:00:00 krfcommd 324 ? 00:00:00 irq/549-adsp 325 ? 00:00:00 sysmon_wq 326 ? 00:00:00 irq/613-modem 327 ? 00:00:00 msm_vidc_worker 328 ? 00:00:00 pm_workerq_venu 333 ? 00:00:00 rq_stats 334 ? 00:00:00 sb-1 335 ? 00:00:00 ngd_rx_thread1 336 ? 00:00:00 ngd_notify_sl1 337 ? 00:00:00 k_bam_data 338 ? 00:00:00 f_mtp 339 ? 00:00:00 file-storage 340 ? 00:00:00 clearpad_thread 341 ? 00:00:01 irq/416-clearpa 342 ? 00:00:00 kworker/4:1H 343 ? 00:00:00 msm_thermal:hot 344 ? 00:00:00 msm_thermal:fre 345 ? 00:00:00 msm_thermal:the 346 ? 00:00:00 boost_sync/0 347 ? 00:00:00 boost_sync/1 348 ? 00:00:00 boost_sync/2 349 ? 00:00:00 boost_sync/3 350 ? 00:00:00 boost_sync/4 351 ? 00:00:00 boost_sync/5 352 ? 00:00:00 ipa_A7_svc 353 ? 00:00:00 kworker/4:3 354 ? 00:00:00 qmi_hndl0000000 355 ? 00:00:00 clnt_req 356 ? 00:00:00 clnt_resp 357 ? 00:00:00 clnt_req 358 ? 00:00:00 nr_run_avg 359 ? 00:00:00 kworker/2:1H 360 ? 00:00:00 wl_event_handle 361 ? 00:00:00 dhd_watchdog_th 362 ? 00:00:00 dhd_dpc 363 ? 00:00:00 dhd_rxf 474 ? 00:00:00 kworker/1:1H 476 ? 00:00:00 kdmflush 477 ? 00:00:00 bioset 478 ? 00:00:00 kdmflush 479 ? 00:00:00 bioset 486 ? 00:00:00 jbd2/dm-0-8 487 ? 00:00:00 ext4-rsv-conver 488 ? 00:00:00 jbd2/dm-1-8 489 ? 00:00:00 ext4-rsv-conver 533 ? 00:00:00 kworker/0:2 536 ? 00:00:00 systemd-journal 540 ? 00:00:00 kworker/5:1H 545 ? 00:00:00 kworker/3:1H 557 ? 00:00:01 systemd-udevd 967 ? 00:00:00 jbd2/mmcblk0p13 968 ? 00:00:00 ext4-rsv-conver 1121 ? 00:00:00 jbd2/mmcblk0p25 1123 ? 00:00:00 ext4-rsv-conver 1150 ? 00:00:00 jbd2/mmcblk0p28 1160 ? 00:00:00 ext4-rsv-conver 1412 ? 00:00:00 jbd2/mmcblk0p52 1413 ? 00:00:00 ext4-rsv-conver 1427 ? 00:00:02 mce 1440 ? 00:00:01 statefs 1443 ? 00:00:03 dbus-daemon 1446 ? 00:00:01 mdss_fb0 1447 ? 00:00:00 ad_calc_wq 1458 ? 00:00:00 usb_moded 1460 ? 00:00:00 droid-hal-init 1461 ? 00:00:00 ohmd 1463 ? 00:00:00 dsme 1468 ? 00:00:00 dsme-server 1473 ? 00:00:01 kworker/0:3 1481 ? 00:00:00 encsfa 1482 ? 00:00:00 bluetooth_rfkil 1484 ? 00:00:04 sensorfwd 1485 ? 00:00:00 systemd-logind 1487 ? 00:00:00 ofonod 1505 ? 00:00:00 IPCRTR 1507 ? 00:00:00 logd 1509 ? 00:00:00 adsp_IPCRTR 1512 ? 00:00:00 vold 1524 ? 00:00:00 servicemanager 1525 ? 00:00:00 tad_static 1526 ? 00:00:00 ta_qmi_service 1527 ? 00:00:00 sct_service 1528 ? 00:00:00 mlog_qmi_servic 1529 ? 00:00:00 rmt_storage 1530 ? 00:00:00 pm-service 1531 ? 00:00:00 qseecomd 1532 ? 00:00:00 minimediaservic 1533 ? 00:00:00 minisfservice 1534 ? 00:00:00 miniafservice 1535 ? 00:00:00 debuggerd64 1536 ? 00:00:02 rild 1537 ? 00:00:00 drmserver 1538 ? 00:00:00 installd 1540 ? 00:00:02 sensors.qcom 1541 ? 00:00:00 adsprpcd 1542 ? 00:00:00 thermanager 1543 ? 00:00:00 qmi_hndl0000000 1544 ? 00:00:00 msm_slim_qmi_cl 1545 ? 00:00:00 qmi_hndl0000000 1549 ? 00:00:00 qmi_hndl0000000 1552 ? 00:00:00 irq/215-408000. 1567 ? 00:00:00 kworker/3:2 1568 tty1 00:00:00 sh 1569 ? 00:00:00 qmuxd 1570 ? 00:00:00 netmgrd 1571 ? 00:00:00 gatekeeperd 1573 ? 00:00:00 perfprofd 1574 ? 00:00:00 fingerprintd 1575 ? 00:00:00 mm-qcamera-daem 1583 ? 00:00:00 pm-proxy 1587 ? 00:00:00 qseecomd 1592 ? 00:00:00 irq/413-wcd9xxx 1782 ? 00:00:00 kworker/2:2 2215 ? 00:00:00 autologind 2243 ? 00:00:00 therm_core:noti 2289 ? 00:00:00 therm_core:noti 2530 ? 00:00:00 systemd 2531 ? 00:00:00 (sd-pam) 2534 ? 00:00:00 tracker-extract 2535 ? 00:00:01 tracker-miner-f 2536 ? 00:00:00 ohm-session-age 2537 ? 00:00:00 tracker-store 2538 ? 00:00:00 dbus-daemon 2541 ? 00:00:00 timed-qt5 2542 ? 00:00:00 booster-qt5 2543 ? 00:00:00 booster-generic 2568 ? 00:00:00 statefs 2607 ? 00:00:40 lipstick 2608 ? 00:00:00 ngfd 2609 ? 00:00:00 invoker 2613 ? 00:00:00 msyncd 2614 ? 00:00:00 mission-control 2615 ? 00:00:00 invoker 2616 ? 00:00:00 voicecall-manag 2617 ? 00:00:00 invoker 2620 ? 00:00:00 connectionagent 2621 ? 00:00:00 messageserver5 2637 ? 00:00:00 pulseaudio 2645 ? 00:00:00 profiled 2651 ? 00:00:00 invoker 2665 ? 00:00:00 IPCRTR 2667 ? 00:00:00 modem_IPCRTR 2669 ? 00:00:00 qmi_hndl0000000 2715 ? 00:00:00 commhistoryd 2728 ? 00:00:00 qmi_hndl0000000 2846 ? 00:00:00 connman-vpnd 2908 ? 00:00:00 kworker/1:3 2912 ? 00:00:01 kworker/u12:13 2959 ? 00:00:00 dconf-service 2982 ? 00:00:00 obexd 3011 ? 00:00:01 connmand 3043 ? 00:00:00 bluetoothd 3044 ? 00:00:00 kworker/2:3 3045 ? 00:00:00 kworker/2:4 3050 ? 00:00:00 wpa_supplicant 3276 ? 00:00:00 kworker/3:3 3280 ? 00:00:00 ipawq46 3281 ? 00:00:00 iparepwq46 3381 ? 00:00:00 telepathy-ring 3976 ? 00:00:00 invoker 3977 ? 00:00:00 invoker 3978 ? 00:00:00 invoker 3979 ? 00:00:00 booster-silica- 3980 ? 00:00:00 booster-silica- 3981 ? 00:00:00 maliit-server 3982 ? 00:00:00 invoker 3983 ? 00:00:00 ambienced 3984 ? 00:00:00 jolla-signon-ui 3985 ? 00:00:00 contactsd 3998 ? 00:00:01 booster [silica 4003 ? 00:00:03 voicecall-ui 4004 ? 00:00:00 invoker 4039 ? 00:00:00 simkit 4040 ? 00:00:00 booster-browser 4044 ? 00:00:00 invoker 4053 ? 00:00:00 booster [qt5] 4055 ? 00:00:00 (sd-pam) 4204 ? 00:00:00 kworker/1:4 4384 ? 00:00:12 sailfish-browse 4445 ? 00:00:02 store-client 4714 ? 00:00:22 fingerterm 4914 ? 00:00:00 kworker/0:0 4919 ? 00:00:00 invoker 4922 ? 00:00:00 booster [generi 4923 pts/0 00:00:00 bash 4967 ? 00:00:00 kworker/3:4 5070 pts/0 00:00:00 sh 5098 ? 00:00:00 invoker 5099 ? 00:00:01 booster [browse 5154 ? 00:00:00 kworker/1:0 5163 ? 00:00:00 kworker/2:0 5243 ? 00:00:01 booster [silica 5245 ? 00:00:00 packagekitd 5246 ? 00:00:00 kworker/0:2H 5251 ? 00:00:00 polkitd 5266 pts/0 00:00:00 ps

neo75 ( 2018-06-06 23:45:21 +0300 )edit

sorry, but I can't read this log. How could this be helpfull for a new user?

dirksche ( 2018-08-20 13:36:57 +0300 )edit
3

answered 2018-08-18 18:52:44 +0300

dirksche gravatar image

updated 2018-08-18 18:54:33 +0300

image descriptionDo you have Storeman installed? Search and install "Nethogs". You have to activate Developer Mode, if you haven't done already. A Terminal Window will open up and shows you which App/Process sent or receive data.

edit flag offensive delete publish link more

Comments

@dirksche thank you very much! NetHogs works perfect! I will try to find the problematic process sending data out.

neo75 ( 2018-08-18 22:06:32 +0300 )edit

Hope your search will be successfull

dirksche ( 2018-08-19 00:31:25 +0300 )edit
0

answered 2018-06-07 02:30:56 +0300

Raymaen gravatar image

updated 2018-06-25 09:47:46 +0300

Related topics linked below, but nice that it is now "tracked by Jolla". That schould be part of the systemfunctionality. Transparency is everything! ;-)

https://together.jolla.com/question/183914/feature-requestmore-detailed-datatransfer-monitoring/

https://together.jolla.com/question/132942/measuring-monthly-data-volume-more/

Edit: it is the second month in a row that my mobile data is used up, although i did not use my phone mutch. Something is consuming the data without my knowledge.

edit flag offensive delete publish link more

Comments

well, did you try to log network traffic with tcpdump?

  1. as root, install it by "pkcon install tcpdump"
  2. monitor traffic by "tcpdump -i rmnet_data0"
juiceme ( 2018-06-25 10:20:54 +0300 )edit

Sorry i'm not that used to all the comands and programing stuff. I was looking for an app to monitor the trafic but did not find any. I also dont use open repos if this tcpdump is from there...

Raymaen ( 2018-06-25 10:25:11 +0300 )edit

Now I do not understand what you mean by that???

What do you consider "an app"?

Is tcpdump not "an App"? Why not? for something to be "an App" does it need to run in graphical view and have fancy-touchy-feely-UI?

juiceme ( 2018-06-25 10:33:02 +0300 )edit

No just be in the oficial store where i can find it as a "stupid user"

Raymaen ( 2018-06-25 10:53:45 +0300 )edit

OK now this is nitpicking but tcpdump exists in the official repositories.

It can be installed from "mer-tools" which is official jolla repository

It is by all definitions more official than anything you could install from OpenRepos for example!!

juiceme ( 2018-06-25 11:09:03 +0300 )edit
0

answered 2018-08-21 00:41:32 +0300

tao101 gravatar image

This is a shot in the dark, but I had a similar problem once on my Symbian phone. I used Maps during a drive out of town and then back again. When I arrived home, I tossed my phone on the counter and went to sleep without quitting Maps. Little did I know that my memory card was corrupt and because Maps couldn't save what it downloaded, it kept downloading the same data again and again and again and again. My carrier texted me a warning that my data quota was nearing, but not before burning several GB's. Moral: if you have a memory card, check it for errors (perhaps on an actual computer) and maybe even the phone's internal memory with FSCK or whatever it uses. (I don't yet own a Sailfish phone myself...) Even an innocuous program could suck large amounts of MB's if it can't save its data properly.

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools

Follow
4 followers

Stats

Asked: 2018-06-01 23:43:56 +0300

Seen: 1,119 times

Last updated: 4 hours ago