Revision history - together.jolla.com

JIO 4G network disabled, and Problem with Connection(working in Android)

I asked a different question(https://together.jolla.com/question/144859/what-is-the-meaning-of-network-denied-in-sailfish-os-intex-aqua-fish-jio/), but the title was different and the problem has since then changed.

Bought a JIO 4G. Activation done. Data is working in Android non-volte 4G phone.
Inserted in Intex Aqua Fish, network registers quickly. Selected Prefer 4G in Mobile networks. Has set Access Point as jionet.
Tried connecting using the connection switch, it tries to connect and (a) says in the notification area "Problem with connection", and under (b) the Connection area "disabled"
Tried restarting the phone, tried restarting using "Restart network connections" (which is available in Sailifsh Utilities that I installed). No luck.
Tried updating to Sailifsh 4.0.4.14, but update is not yet pushed to the Aqua Fish devices. So I updated by enabling developer mode and using version --dup. Update was successful. But the connection issue persists.

On a sidenote: "I think" what was fixed/claimed in 4.0.14 update related to issues in JIO 4G -- are just apn settings for JIO 4G are available by default. So, since I used correct apn even before updating, there is no difference. And also, I actually did click restore to default in Data Access Point so that it populated the JIO related settings in the Data Access Point screen.

To try even this much is because, many people in this forum got it working successfully without much efforts (similar to Android 4G devices). So, I'm not sure where the problem is. Was there something got permanent when we were trying multiple things. (All are from phone screens, not devel-su).

Can a device reset help?

Now, as a next step I accessed logs using journalctcl -r.

[root@Sailfish nemo]# journalctl -r -- Logs begin at Sat 2016-10-29 13:51:22 IST, end at Sat 2016-10-29 13:53:32 IST. -- Oct 29 13:53:32 Sailfish systemd[1]: Time has been changed Oct 29 13:53:32 Sailfish systemd[928]: Time has been changed Oct 29 13:53:33 Sailfish estart[4312]: [D] NetworkService::handleConnectReply:374 - Reply from service.connect(): "Operation aborted" Oct 29 13:53:33 Sailfish connmand[757]: [ofono] ERROR! GDBus.Error:org.ofono.Error.Failed: Operation failed Oct 29 13:53:33 Sailfish ofonod[745]: Unexpected data call status 55 Oct 29 13:53:32 Sailfish ofonod[745]: Activating context: 1 Oct 29 13:53:32 Sailfish connmand[757]: Skipping disconnect of /ril_0, network is connecting. Oct 29 13:53:28 Sailfish kernel: [08:23:28.049654] [000000022A0EA8EA] [VosMC] wlan: [E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan Oct 29 13:53:27 Sailfish statefs[568]: Display: "on" Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0 Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP already resumed. Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0 Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP wakeup sleep. Oct 29 13:53:27 Sailfish kernel: sensors stk3311-light: Invalid value of delay, delay=0 Oct 29 13:53:27 Sailfish lipstick[1037]: [D] HwComposerContext::sleepDisplay:180 - unsleepDisplay Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3819 t=36.0 h=2 st=3 c=177 chg= Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3814 t=36.0 h=2 st=3 c=177 chg= Oct 29 13:53:25 Sailfish kernel: PM: suspend exit 2016-10-29 08:23:25.975706327 UTC Oct 29 13:53:25 Sailfish kernel: Restarting tasks ... done. Oct 29 13:53:25 Sailfish kernel: PM: resume of devices complete after 82.510 msecs Oct 29 13:53:25 Sailfish kernel: PM: early resume of devices complete after 5.054 msecs Oct 29 13:53:25 Sailfish kernel: i2c-msm-v2 78b5000.i2c: Runtime PM-callback was not invoked. Oct 29 13:53:25 Sailfish kernel: PM: noirq resume of devices complete after 1.779 msecs Oct 29 13:53:25 Sailfish kernel: CPU3 is up Oct 29 13:53:25 Sailfish kernel: CPU2 is up Oct 29 13:53:25 Sailfish kernel: CPU1 is up Oct 29 13:53:25 Sailfish kernel: Enabling non-boot CPUs ... Oct 29 13:53:25 Sailfish kernel: CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend Oct 29 13:53:25 Sailfish kernel: Disabling non-boot CPUs ... Oct 29 13:53:25 Sailfish kernel: PM: noirq suspend of devices complete after 3.346 msecs Oct 29 13:53:25 Sailfish kernel: PM: late suspend of devices complete after 2.995 msecs Oct 29 13:53:25 Sailfish kernel: PM: suspend of devices complete after 40.109 msecs Oct 29 13:53:25 Sailfish kernel: Suspending console(s) (use no_console_suspend to debug) Oct 29 13:53:25 Sailfish kernel: Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done. Oct 29 13:53:25 Sailfish systemd[928]: Time has been changed Oct 29 13:53:25 Sailfish systemd[1]: Time has been changed Oct 29 13:53:25 Sailfish kernel: Freezing user space processes ... (elapsed 0.007 seconds) done. Oct 29 13:53:25 Sailfish kernel: PM: Syncing filesystems ... done. Oct 29 13:53:24 Sailfish kernel: PM: suspend entry 2016-10-29 08:23:24.652726583 UTC Oct 29 13:53:24 Sailfish [990]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty" Oct 29 13:53:24 Sailfish lipstick[1037]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty" Oct 29 13:53:24 Sailfish ofonod[745]: data reg changed 0 -> 1 (registered), attached 0

Please help me resolve this issue.

PS: I've tried formatting the log above, but couldn't if some knows how, please update this post. thanks.

JIO 4G network disabled, and Problem with Connection(working in Android)

I asked a different question(https://together.jolla.com/question/144859/what-is-the-meaning-of-network-denied-in-sailfish-os-intex-aqua-fish-jio/), but the title was different and the problem has since then changed.

Bought a JIO 4G. Activation done. Data is working in Android non-volte 4G phone.
Inserted in Intex Aqua Fish, network registers quickly. Selected Prefer 4G in Mobile networks. Has set Access Point as jionet.
Tried connecting using the connection switch, it tries to connect and (a) says in the notification area "Problem with connection", and under (b) the Connection area "disabled"
Tried restarting the phone, tried restarting using "Restart network connections" (which is available in Sailifsh Utilities that I installed). No luck.
Tried updating to Sailifsh 4.0.4.14, but update is not yet pushed to the Aqua Fish devices. So I updated by enabling developer mode and using version --dup. Update was successful. But the connection issue persists.

On a sidenote: "I think" what was fixed/claimed in 4.0.14 update related to issues in JIO 4G -- are just apn settings for JIO 4G are available by default. So, since I used correct apn even before updating, there is no difference. And also, I actually did click restore to default in Data Access Point so that it populated the JIO related settings in the Data Access Point screen.

To try even this much is because, many people in this forum got it working successfully without much efforts (similar to Android 4G devices). So, I'm not sure where the problem is. Was there something got permanent when we were trying multiple things. (All are from phone screens, not devel-su).

Can a device reset help?

Now, as a next step I accessed logs using journalctcl -r.

[root@Sailfish nemo]# journalctl -r -- Logs begin at Sat 2016-10-29 13:51:22 IST, end at Sat 2016-10-29 13:53:32 IST. -- Oct 29 13:53:32 Sailfish systemd[1]: Time has been changed Oct 29 13:53:32 Sailfish systemd[928]: Time has been changed Oct 29 13:53:33 Sailfish estart[4312]: [D] NetworkService::handleConnectReply:374 - Reply from service.connect(): "Operation aborted" Oct 29 13:53:33 Sailfish connmand[757]: [ofono] ERROR! GDBus.Error:org.ofono.Error.Failed: Operation failed Oct 29 13:53:33 Sailfish ofonod[745]: Unexpected data call status 55 Oct 29 13:53:32 Sailfish ofonod[745]: Activating context: 1 Oct 29 13:53:32 Sailfish connmand[757]: Skipping disconnect of /ril_0, network is connecting. Oct 29 13:53:28 Sailfish kernel: [08:23:28.049654] [000000022A0EA8EA] [VosMC] wlan: [E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan Oct 29 13:53:27 Sailfish statefs[568]: Display: "on" Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0 Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP already resumed. Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0 Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP wakeup sleep. Oct 29 13:53:27 Sailfish kernel: sensors stk3311-light: Invalid value of delay, delay=0 Oct 29 13:53:27 Sailfish lipstick[1037]: [D] HwComposerContext::sleepDisplay:180 - unsleepDisplay Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3819 t=36.0 h=2 st=3 c=177 chg= Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3814 t=36.0 h=2 st=3 c=177 chg= Oct 29 13:53:25 Sailfish kernel: PM: suspend exit 2016-10-29 08:23:25.975706327 UTC Oct 29 13:53:25 Sailfish kernel: Restarting tasks ... done. Oct 29 13:53:25 Sailfish kernel: PM: resume of devices complete after 82.510 msecs Oct 29 13:53:25 Sailfish kernel: PM: early resume of devices complete after 5.054 msecs Oct 29 13:53:25 Sailfish kernel: i2c-msm-v2 78b5000.i2c: Runtime PM-callback was not invoked. Oct 29 13:53:25 Sailfish kernel: PM: noirq resume of devices complete after 1.779 msecs Oct 29 13:53:25 Sailfish kernel: CPU3 is up Oct 29 13:53:25 Sailfish kernel: CPU2 is up Oct 29 13:53:25 Sailfish kernel: CPU1 is up Oct 29 13:53:25 Sailfish kernel: Enabling non-boot CPUs ... Oct 29 13:53:25 Sailfish kernel: CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend Oct 29 13:53:25 Sailfish kernel: Disabling non-boot CPUs ... Oct 29 13:53:25 Sailfish kernel: PM: noirq suspend of devices complete after 3.346 msecs Oct 29 13:53:25 Sailfish kernel: PM: late suspend of devices complete after 2.995 msecs Oct 29 13:53:25 Sailfish kernel: PM: suspend of devices complete after 40.109 msecs Oct 29 13:53:25 Sailfish kernel: Suspending console(s) (use no_console_suspend to debug) Oct 29 13:53:25 Sailfish kernel: Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done. Oct 29 13:53:25 Sailfish systemd[928]: Time has been changed Oct 29 13:53:25 Sailfish systemd[1]: Time has been changed Oct 29 13:53:25 Sailfish kernel: Freezing user space processes ... (elapsed 0.007 seconds) done. Oct 29 13:53:25 Sailfish kernel: PM: Syncing filesystems ... done. Oct 29 13:53:24 Sailfish kernel: PM: suspend entry 2016-10-29 08:23:24.652726583 UTC Oct 29 13:53:24 Sailfish [990]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty" Oct 29 13:53:24 Sailfish lipstick[1037]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty" Oct 29 13:53:24 Sailfish ofonod[745]: data reg changed 0 -> 1 (registered), attached 0

Please help me resolve this issue.

PS: I've tried formatting the log above, but couldn't if some knows how, please update this post. thanks.

JIO 4G network disabled, and Problem with Connection(working in Android)

I asked a different question(https://together.jolla.com/question/144859/what-is-the-meaning-of-network-denied-in-sailfish-os-intex-aqua-fish-jio/), but the title was different and the problem has since then changed.

Bought a JIO 4G. Activation done. Data is working in Android non-volte 4G phone.
Inserted in Intex Aqua Fish, network registers quickly. Selected Prefer 4G in Mobile networks. Has set Access Point as jionet.
Tried connecting using the connection switch, it tries to connect and (a) says in the notification area "Problem with connection", and under (b) the Connection area "disabled"
Tried restarting the phone, tried restarting using "Restart network connections" (which is available in Sailifsh Utilities that I installed). No luck.
Tried updating to Sailifsh 4.0.4.14, but update is not yet pushed to the Aqua Fish devices. So I updated by enabling developer mode and using version --dup. Update was successful. But the connection issue persists.

On a sidenote: "I think" what was fixed/claimed in 4.0.14 update related to issues in JIO 4G -- are just apn settings for JIO 4G are available by default. So, since I used correct apn even before updating, there is no difference. And also, I actually did click restore to default in Data Access Point so that it populated the JIO related settings in the Data Access Point screen.

To try even this much is because, many people in this forum got it working successfully without much efforts (similar to Android 4G devices). So, I'm not sure where the problem is. Was there something got permanent when we were trying multiple things. (All are from phone screens, not devel-su).

Can a device reset help?

~~Now, as a next step I accessed logs using journalctcl -r.~~

[root@Sailfish nemo]# journalctl -r -r

-- Logs begin at Sat 2016-10-29 13:51:22 IST, end at Sat 2016-10-29 13:53:32 IST. --
Oct 29 13:53:32 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:32 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:33 Sailfish estart[4312]: [D] NetworkService::handleConnectReply:374 - Reply from service.connect():  "Operation aborted"
Oct 29 13:53:33 Sailfish connmand[757]: [ofono] ERROR! GDBus.Error:org.ofono.Error.Failed: Operation failed
Oct 29 13:53:33 Sailfish ofonod[745]: Unexpected data call status 55
Oct 29 13:53:32 Sailfish ofonod[745]: Activating context: 1
Oct 29 13:53:32 Sailfish connmand[757]: Skipping disconnect of /ril_0, network is connecting.
Oct 29 13:53:28 Sailfish kernel: [08:23:28.049654] [000000022A0EA8EA] [VosMC]  wlan: [E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
Oct 29 13:53:27 Sailfish statefs[568]: Display: "on"
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP already resumed.
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP wakeup sleep.
Oct 29 13:53:27 Sailfish kernel: sensors stk3311-light: Invalid value of delay, delay=0
Oct 29 13:53:27 Sailfish lipstick[1037]: [D] HwComposerContext::sleepDisplay:180 - unsleepDisplay
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3819 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3814 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:25 Sailfish kernel: PM: suspend exit 2016-10-29 08:23:25.975706327 UTC
Oct 29 13:53:25 Sailfish kernel: Restarting tasks ... done.
Oct 29 13:53:25 Sailfish kernel: PM: resume of devices complete after 82.510 msecs
Oct 29 13:53:25 Sailfish kernel: PM: early resume of devices complete after 5.054 msecs
Oct 29 13:53:25 Sailfish kernel: i2c-msm-v2 78b5000.i2c: Runtime PM-callback was not invoked.
Oct 29 13:53:25 Sailfish kernel: PM: noirq resume of devices complete after 1.779 msecs
Oct 29 13:53:25 Sailfish kernel: CPU3 is up
Oct 29 13:53:25 Sailfish kernel: CPU2 is up
Oct 29 13:53:25 Sailfish kernel: CPU1 is up
Oct 29 13:53:25 Sailfish kernel: Enabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
Oct 29 13:53:25 Sailfish kernel: Disabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: PM: noirq suspend of devices complete after 3.346 msecs
Oct 29 13:53:25 Sailfish kernel: PM: late suspend of devices complete after 2.995 msecs
Oct 29 13:53:25 Sailfish kernel: PM: suspend of devices complete after 40.109 msecs
Oct 29 13:53:25 Sailfish kernel: Suspending console(s) (use no_console_suspend to debug)
Oct 29 13:53:25 Sailfish kernel: Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
Oct 29 13:53:25 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:25 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:25 Sailfish kernel: Freezing user space processes ... (elapsed 0.007 seconds) done.
Oct 29 13:53:25 Sailfish kernel: PM: Syncing filesystems ... done.
Oct 29 13:53:24 Sailfish kernel: PM: suspend entry 2016-10-29 08:23:24.652726583 UTC
Oct 29 13:53:24 Sailfish [990]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish lipstick[1037]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish ofonod[745]: data reg changed 0 -> 1 (registered), attached 0
 0

Please help me resolve this issue.

~~PS: I've tried formatting the log above, but couldn't if some knows how, please update this post. thanks.~~

JIO 4G network disabled, and Problem with Connection(working in Android)Android): why is it giving Unexpected data call status 55?

I asked a different question(https://together.jolla.com/question/144859/what-is-the-meaning-of-network-denied-in-sailfish-os-intex-aqua-fish-jio/), but the title was different and the problem has since then changed.

Bought a JIO 4G. Activation done. Data is working in Android non-volte 4G phone.
Inserted in Intex Aqua Fish, network registers quickly. Selected Prefer 4G in Mobile networks. Has set Access Point as jionet.
Tried connecting using the connection switch, it tries to connect and (a) says in the notification area "Problem with connection", and under (b) the Connection area "disabled"
Tried restarting the phone, tried restarting using "Restart network connections" (which is available in Sailifsh Utilities that I installed). No luck.
Tried updating to Sailifsh 4.0.4.14, but update is not yet pushed to the Aqua Fish devices. So I updated by enabling developer mode and using version --dup. Update was successful. But the connection issue persists.

On a sidenote: "I think" what was fixed/claimed in 4.0.14 update related to issues in JIO 4G -- are just apn settings for JIO 4G are available by default. So, since I used correct apn even before updating, there is no difference. And also, I actually did click restore to default in Data Access Point so that it populated the JIO related settings in the Data Access Point screen.

To try even this much is because, many people in this forum got it working successfully without much efforts (similar to Android 4G devices). So, I'm not sure where the problem is. Was there something got permanent when we were trying multiple things. (All are from phone screens, not devel-su).

Can a device reset help?

Now, as a next step I accessed logs using journalctcl -r.

[root@Sailfish nemo]# journalctl -r

-- Logs begin at Sat 2016-10-29 13:51:22 IST, end at Sat 2016-10-29 13:53:32 IST. --
Oct 29 13:53:32 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:32 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:33 Sailfish estart[4312]: [D] NetworkService::handleConnectReply:374 - Reply from service.connect():  "Operation aborted"
Oct 29 13:53:33 Sailfish connmand[757]: [ofono] ERROR! GDBus.Error:org.ofono.Error.Failed: Operation failed
Oct 29 13:53:33 Sailfish ofonod[745]: Unexpected data call status 55
Oct 29 13:53:32 Sailfish ofonod[745]: Activating context: 1
Oct 29 13:53:32 Sailfish connmand[757]: Skipping disconnect of /ril_0, network is connecting.
Oct 29 13:53:28 Sailfish kernel: [08:23:28.049654] [000000022A0EA8EA] [VosMC]  wlan: [E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
Oct 29 13:53:27 Sailfish statefs[568]: Display: "on"
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP already resumed.
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP wakeup sleep.
Oct 29 13:53:27 Sailfish kernel: sensors stk3311-light: Invalid value of delay, delay=0
Oct 29 13:53:27 Sailfish lipstick[1037]: [D] HwComposerContext::sleepDisplay:180 - unsleepDisplay
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3819 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3814 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:25 Sailfish kernel: PM: suspend exit 2016-10-29 08:23:25.975706327 UTC
Oct 29 13:53:25 Sailfish kernel: Restarting tasks ... done.
Oct 29 13:53:25 Sailfish kernel: PM: resume of devices complete after 82.510 msecs
Oct 29 13:53:25 Sailfish kernel: PM: early resume of devices complete after 5.054 msecs
Oct 29 13:53:25 Sailfish kernel: i2c-msm-v2 78b5000.i2c: Runtime PM-callback was not invoked.
Oct 29 13:53:25 Sailfish kernel: PM: noirq resume of devices complete after 1.779 msecs
Oct 29 13:53:25 Sailfish kernel: CPU3 is up
Oct 29 13:53:25 Sailfish kernel: CPU2 is up
Oct 29 13:53:25 Sailfish kernel: CPU1 is up
Oct 29 13:53:25 Sailfish kernel: Enabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
Oct 29 13:53:25 Sailfish kernel: Disabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: PM: noirq suspend of devices complete after 3.346 msecs
Oct 29 13:53:25 Sailfish kernel: PM: late suspend of devices complete after 2.995 msecs
Oct 29 13:53:25 Sailfish kernel: PM: suspend of devices complete after 40.109 msecs
Oct 29 13:53:25 Sailfish kernel: Suspending console(s) (use no_console_suspend to debug)
Oct 29 13:53:25 Sailfish kernel: Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
Oct 29 13:53:25 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:25 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:25 Sailfish kernel: Freezing user space processes ... (elapsed 0.007 seconds) done.
Oct 29 13:53:25 Sailfish kernel: PM: Syncing filesystems ... done.
Oct 29 13:53:24 Sailfish kernel: PM: suspend entry 2016-10-29 08:23:24.652726583 UTC
Oct 29 13:53:24 Sailfish [990]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish lipstick[1037]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish ofonod[745]: data reg changed 0 -> 1 (registered), attached 0

Please help me resolve this issue.

JIO 4G network disabled, and Problem with Connection(working in Android): why is it giving Unexpected data call status 55?

I asked a different question(https://together.jolla.com/question/144859/what-is-the-meaning-of-network-denied-in-sailfish-os-intex-aqua-fish-jio/), but the title was different and the problem has since then changed.

Bought a JIO 4G. Activation done. Data is working in Android non-volte 4G phone.
Inserted in Intex Aqua Fish, network registers quickly. Selected Prefer 4G in Mobile networks. Has set Access Point as jionet.
Tried connecting using the connection switch, it tries to connect and (a) says in the notification area "Problem with connection", and under (b) the Connection area "disabled"
Tried restarting the phone, tried restarting using "Restart network connections" (which is available in Sailifsh Utilities that I installed). No luck.
Tried updating to Sailifsh 4.0.4.14, but update is not yet pushed to the Aqua Fish devices. So I updated by enabling developer mode and using version --dup. Update was successful. But the connection issue persists.

On a sidenote: "I think" what was fixed/claimed in 4.0.14 update related to issues in JIO 4G -- are just apn settings for JIO 4G are available by default. So, since I used correct apn even before updating, there is no difference. And also, I actually did click restore to default in Data Access Point so that it populated the JIO related settings in the Data Access Point screen.

To try even this much is because, many people in this forum got it working successfully without much efforts (similar to Android 4G devices). So, I'm not sure where the problem is. Was there something got permanent when we were trying multiple things. (All are from phone screens, not devel-su).

Can a device reset help?

Now, as a next step I accessed logs using journalctcl -r.

[root@Sailfish nemo]# journalctl -r

-- Logs begin at Sat 2016-10-29 13:51:22 IST, end at Sat 2016-10-29 13:53:32 IST. --
Oct 29 13:53:32 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:32 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:33 Sailfish estart[4312]: [D] NetworkService::handleConnectReply:374 - Reply from service.connect():  "Operation aborted"
Oct 29 13:53:33 Sailfish connmand[757]: [ofono] ERROR! GDBus.Error:org.ofono.Error.Failed: Operation failed
Oct 29 13:53:33 Sailfish ofonod[745]: Unexpected data call status 55
Oct 29 13:53:32 Sailfish ofonod[745]: Activating context: 1
Oct 29 13:53:32 Sailfish connmand[757]: Skipping disconnect of /ril_0, network is connecting.
Oct 29 13:53:28 Sailfish kernel: [08:23:28.049654] [000000022A0EA8EA] [VosMC]  wlan: [E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
Oct 29 13:53:27 Sailfish statefs[568]: Display: "on"
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP already resumed.
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP wakeup sleep.
Oct 29 13:53:27 Sailfish kernel: sensors stk3311-light: Invalid value of delay, delay=0
Oct 29 13:53:27 Sailfish lipstick[1037]: [D] HwComposerContext::sleepDisplay:180 - unsleepDisplay
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3819 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3814 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:25 Sailfish kernel: PM: suspend exit 2016-10-29 08:23:25.975706327 UTC
Oct 29 13:53:25 Sailfish kernel: Restarting tasks ... done.
Oct 29 13:53:25 Sailfish kernel: PM: resume of devices complete after 82.510 msecs
Oct 29 13:53:25 Sailfish kernel: PM: early resume of devices complete after 5.054 msecs
Oct 29 13:53:25 Sailfish kernel: i2c-msm-v2 78b5000.i2c: Runtime PM-callback was not invoked.
Oct 29 13:53:25 Sailfish kernel: PM: noirq resume of devices complete after 1.779 msecs
Oct 29 13:53:25 Sailfish kernel: CPU3 is up
Oct 29 13:53:25 Sailfish kernel: CPU2 is up
Oct 29 13:53:25 Sailfish kernel: CPU1 is up
Oct 29 13:53:25 Sailfish kernel: Enabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
Oct 29 13:53:25 Sailfish kernel: Disabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: PM: noirq suspend of devices complete after 3.346 msecs
Oct 29 13:53:25 Sailfish kernel: PM: late suspend of devices complete after 2.995 msecs
Oct 29 13:53:25 Sailfish kernel: PM: suspend of devices complete after 40.109 msecs
Oct 29 13:53:25 Sailfish kernel: Suspending console(s) (use no_console_suspend to debug)
Oct 29 13:53:25 Sailfish kernel: Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
Oct 29 13:53:25 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:25 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:25 Sailfish kernel: Freezing user space processes ... (elapsed 0.007 seconds) done.
Oct 29 13:53:25 Sailfish kernel: PM: Syncing filesystems ... done.
Oct 29 13:53:24 Sailfish kernel: PM: suspend entry 2016-10-29 08:23:24.652726583 UTC
Oct 29 13:53:24 Sailfish [990]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish lipstick[1037]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish ofonod[745]: data reg changed 0 -> 1 (registered), attached 0

Please help me resolve this issue.

Update:

My cousin also has an Aqua Fish, I've tried the sim in that phone it's working there :). So, I'm not sure what my next step should be, probably reset or return the phone?

JIO 4G network disabled, and Problem with Connection(working in Android): why is it giving Unexpected data call status 55?

I asked a different question(https://together.jolla.com/question/144859/what-is-the-meaning-of-network-denied-in-sailfish-os-intex-aqua-fish-jio/), but the title was different and the problem has since then changed.

Bought a JIO 4G. Activation done. Data is working in Android non-volte 4G phone.
Inserted in Intex Aqua Fish, network registers quickly. Selected Prefer 4G in Mobile networks. Has set Access Point as jionet.
Tried connecting using the connection switch, it tries to connect and (a) says in the notification area "Problem with connection", and under (b) the Connection area "disabled"
Tried restarting the phone, tried restarting using "Restart network connections" (which is available in Sailifsh Utilities that I installed). No luck.
Tried updating to Sailifsh 4.0.4.14, but update is not yet pushed to the Aqua Fish devices. So I updated by enabling developer mode and using version --dup. Update was successful. But the connection issue persists.

On a sidenote: "I think" what was fixed/claimed in 4.0.14 update related to issues in JIO 4G -- are just apn settings for JIO 4G are available by default. So, since I used correct apn even before updating, there is no difference. And also, I actually did click restore to default in Data Access Point so that it populated the JIO related settings in the Data Access Point screen.

To try even this much is because, many people in this forum got it working successfully without much efforts (similar to Android 4G devices). So, I'm not sure where the problem is. Was there something got permanent when we were trying multiple things. (All are from phone screens, not devel-su).

Can a device reset help?

Now, as a next step I accessed logs using journalctcl -r.

[root@Sailfish nemo]# journalctl -r

-- Logs begin at Sat 2016-10-29 13:51:22 IST, end at Sat 2016-10-29 13:53:32 IST. --
Oct 29 13:53:32 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:32 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:33 Sailfish estart[4312]: [D] NetworkService::handleConnectReply:374 - Reply from service.connect():  "Operation aborted"
Oct 29 13:53:33 Sailfish connmand[757]: [ofono] ERROR! GDBus.Error:org.ofono.Error.Failed: Operation failed
Oct 29 13:53:33 Sailfish ofonod[745]: Unexpected data call status 55
Oct 29 13:53:32 Sailfish ofonod[745]: Activating context: 1
Oct 29 13:53:32 Sailfish connmand[757]: Skipping disconnect of /ril_0, network is connecting.
Oct 29 13:53:28 Sailfish kernel: [08:23:28.049654] [000000022A0EA8EA] [VosMC]  wlan: [E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
Oct 29 13:53:27 Sailfish statefs[568]: Display: "on"
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP already resumed.
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP wakeup sleep.
Oct 29 13:53:27 Sailfish kernel: sensors stk3311-light: Invalid value of delay, delay=0
Oct 29 13:53:27 Sailfish lipstick[1037]: [D] HwComposerContext::sleepDisplay:180 - unsleepDisplay
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3819 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3814 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:25 Sailfish kernel: PM: suspend exit 2016-10-29 08:23:25.975706327 UTC
Oct 29 13:53:25 Sailfish kernel: Restarting tasks ... done.
Oct 29 13:53:25 Sailfish kernel: PM: resume of devices complete after 82.510 msecs
Oct 29 13:53:25 Sailfish kernel: PM: early resume of devices complete after 5.054 msecs
Oct 29 13:53:25 Sailfish kernel: i2c-msm-v2 78b5000.i2c: Runtime PM-callback was not invoked.
Oct 29 13:53:25 Sailfish kernel: PM: noirq resume of devices complete after 1.779 msecs
Oct 29 13:53:25 Sailfish kernel: CPU3 is up
Oct 29 13:53:25 Sailfish kernel: CPU2 is up
Oct 29 13:53:25 Sailfish kernel: CPU1 is up
Oct 29 13:53:25 Sailfish kernel: Enabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
Oct 29 13:53:25 Sailfish kernel: Disabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: PM: noirq suspend of devices complete after 3.346 msecs
Oct 29 13:53:25 Sailfish kernel: PM: late suspend of devices complete after 2.995 msecs
Oct 29 13:53:25 Sailfish kernel: PM: suspend of devices complete after 40.109 msecs
Oct 29 13:53:25 Sailfish kernel: Suspending console(s) (use no_console_suspend to debug)
Oct 29 13:53:25 Sailfish kernel: Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
Oct 29 13:53:25 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:25 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:25 Sailfish kernel: Freezing user space processes ... (elapsed 0.007 seconds) done.
Oct 29 13:53:25 Sailfish kernel: PM: Syncing filesystems ... done.
Oct 29 13:53:24 Sailfish kernel: PM: suspend entry 2016-10-29 08:23:24.652726583 UTC
Oct 29 13:53:24 Sailfish [990]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish lipstick[1037]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish ofonod[745]: data reg changed 0 -> 1 (registered), attached 0

Please help me resolve this issue.

Update:

My cousin also has an Aqua Fish, I've tried the sim in that phone it's working there :). So, I'm not sure what my next step should be, probably reset or return the phone?

Update2:

I've reset the device. Still no luck :(

JIO 4G network Network disabled, and Problem with Connection(working in Android): why is it giving Unexpected data call status 55?

I asked a different question(https://together.jolla.com/question/144859/what-is-the-meaning-of-network-denied-in-sailfish-os-intex-aqua-fish-jio/), but the title was different and the problem has since then changed.

Bought a JIO 4G. Activation done. Data is working in Android non-volte 4G phone.
Inserted in Intex Aqua Fish, network registers quickly. Selected Prefer 4G in Mobile networks. Has set Access Point as jionet.
Tried connecting using the connection switch, it tries to connect and (a) says in the notification area "Problem with connection", and under (b) the Connection area "disabled"
Tried restarting the phone, tried restarting using "Restart network connections" (which is available in Sailifsh Utilities that I installed). No luck.
Tried updating to Sailifsh 4.0.4.14, but update is not yet pushed to the Aqua Fish devices. So I updated by enabling developer mode and using version --dup. Update was successful. But the connection issue persists.

On a sidenote: "I think" what was fixed/claimed in 4.0.14 update related to issues in JIO 4G -- are just apn settings for JIO 4G are available by default. So, since I used correct apn even before updating, there is no difference. And also, I actually did click restore to default in Data Access Point so that it populated the JIO related settings in the Data Access Point screen.

To try even this much is because, many people in this forum got it working successfully without much efforts (similar to Android 4G devices). So, I'm not sure where the problem is. Was there something got permanent when we were trying multiple things. (All are from phone screens, not devel-su).

Can a device reset help?

Now, as a next step I accessed logs using journalctcl -r.

[root@Sailfish nemo]# journalctl -r

-- Logs begin at Sat 2016-10-29 13:51:22 IST, end at Sat 2016-10-29 13:53:32 IST. --
Oct 29 13:53:32 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:32 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:33 Sailfish estart[4312]: [D] NetworkService::handleConnectReply:374 - Reply from service.connect():  "Operation aborted"
Oct 29 13:53:33 Sailfish connmand[757]: [ofono] ERROR! GDBus.Error:org.ofono.Error.Failed: Operation failed
Oct 29 13:53:33 Sailfish ofonod[745]: Unexpected data call status 55
Oct 29 13:53:32 Sailfish ofonod[745]: Activating context: 1
Oct 29 13:53:32 Sailfish connmand[757]: Skipping disconnect of /ril_0, network is connecting.
Oct 29 13:53:28 Sailfish kernel: [08:23:28.049654] [000000022A0EA8EA] [VosMC]  wlan: [E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
Oct 29 13:53:27 Sailfish statefs[568]: Display: "on"
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP already resumed.
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP wakeup sleep.
Oct 29 13:53:27 Sailfish kernel: sensors stk3311-light: Invalid value of delay, delay=0
Oct 29 13:53:27 Sailfish lipstick[1037]: [D] HwComposerContext::sleepDisplay:180 - unsleepDisplay
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3819 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3814 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:25 Sailfish kernel: PM: suspend exit 2016-10-29 08:23:25.975706327 UTC
Oct 29 13:53:25 Sailfish kernel: Restarting tasks ... done.
Oct 29 13:53:25 Sailfish kernel: PM: resume of devices complete after 82.510 msecs
Oct 29 13:53:25 Sailfish kernel: PM: early resume of devices complete after 5.054 msecs
Oct 29 13:53:25 Sailfish kernel: i2c-msm-v2 78b5000.i2c: Runtime PM-callback was not invoked.
Oct 29 13:53:25 Sailfish kernel: PM: noirq resume of devices complete after 1.779 msecs
Oct 29 13:53:25 Sailfish kernel: CPU3 is up
Oct 29 13:53:25 Sailfish kernel: CPU2 is up
Oct 29 13:53:25 Sailfish kernel: CPU1 is up
Oct 29 13:53:25 Sailfish kernel: Enabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
Oct 29 13:53:25 Sailfish kernel: Disabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: PM: noirq suspend of devices complete after 3.346 msecs
Oct 29 13:53:25 Sailfish kernel: PM: late suspend of devices complete after 2.995 msecs
Oct 29 13:53:25 Sailfish kernel: PM: suspend of devices complete after 40.109 msecs
Oct 29 13:53:25 Sailfish kernel: Suspending console(s) (use no_console_suspend to debug)
Oct 29 13:53:25 Sailfish kernel: Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
Oct 29 13:53:25 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:25 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:25 Sailfish kernel: Freezing user space processes ... (elapsed 0.007 seconds) done.
Oct 29 13:53:25 Sailfish kernel: PM: Syncing filesystems ... done.
Oct 29 13:53:24 Sailfish kernel: PM: suspend entry 2016-10-29 08:23:24.652726583 UTC
Oct 29 13:53:24 Sailfish [990]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish lipstick[1037]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish ofonod[745]: data reg changed 0 -> 1 (registered), attached 0

Please help me resolve this issue.

Update:

My cousin also has an Aqua Fish, I've tried the sim in that phone it's working there :). So, I'm not sure what my next step should be, probably reset or return the phone?

Update2:

I've reset the device. Still no luck :(

Network disabled, and Problem with Connection(working in Android): why is it giving Unexpected data call status 55?

I asked a different question(https://together.jolla.com/question/144859/what-is-the-meaning-of-network-denied-in-sailfish-os-intex-aqua-fish-jio/), but the title was different and the problem has since then changed.

Bought a JIO 4G. Activation done. Data is working in Android non-volte 4G phone.
Inserted in Intex Aqua Fish, network registers quickly. Selected Prefer 4G in Mobile networks. Has set Access Point as jionet.
Tried connecting using the connection switch, it tries to connect and (a) says in the notification area "Problem with connection", and under (b) the Connection area "disabled"
Tried restarting the phone, tried restarting using "Restart network connections" (which is available in Sailifsh Utilities that I installed). No luck.
Tried updating to Sailifsh 4.0.4.14, but update is not yet pushed to the Aqua Fish devices. So I updated by enabling developer mode and using version --dup. Update was successful. But the connection issue persists.

On a sidenote: "I think" what was fixed/claimed in 4.0.14 update related to issues in JIO 4G -- are just apn settings for JIO 4G are available by default. So, since I used correct apn even before updating, there is no difference. And also, I actually did click restore to default in Data Access Point so that it populated the JIO related settings in the Data Access Point screen.

To try even this much is because, many people in this forum got it working successfully without much efforts (similar to Android 4G devices). So, I'm not sure where the problem is. Was there something got permanent when we were trying multiple things. (All are from phone screens, not devel-su).

Can a device reset help?

Now, as a next step I accessed logs using journalctcl -r.

[root@Sailfish nemo]# journalctl -r

-- Logs begin at Sat 2016-10-29 13:51:22 IST, end at Sat 2016-10-29 13:53:32 IST. --
Oct 29 13:53:32 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:32 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:33 Sailfish estart[4312]: [D] NetworkService::handleConnectReply:374 - Reply from service.connect():  "Operation aborted"
Oct 29 13:53:33 Sailfish connmand[757]: [ofono] ERROR! GDBus.Error:org.ofono.Error.Failed: Operation failed
Oct 29 13:53:33 Sailfish ofonod[745]: Unexpected data call status 55
Oct 29 13:53:32 Sailfish ofonod[745]: Activating context: 1
Oct 29 13:53:32 Sailfish connmand[757]: Skipping disconnect of /ril_0, network is connecting.
Oct 29 13:53:28 Sailfish kernel: [08:23:28.049654] [000000022A0EA8EA] [VosMC]  wlan: [E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
Oct 29 13:53:27 Sailfish statefs[568]: Display: "on"
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP already resumed.
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP wakeup sleep.
Oct 29 13:53:27 Sailfish kernel: sensors stk3311-light: Invalid value of delay, delay=0
Oct 29 13:53:27 Sailfish lipstick[1037]: [D] HwComposerContext::sleepDisplay:180 - unsleepDisplay
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3819 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3814 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:25 Sailfish kernel: PM: suspend exit 2016-10-29 08:23:25.975706327 UTC
Oct 29 13:53:25 Sailfish kernel: Restarting tasks ... done.
Oct 29 13:53:25 Sailfish kernel: PM: resume of devices complete after 82.510 msecs
Oct 29 13:53:25 Sailfish kernel: PM: early resume of devices complete after 5.054 msecs
Oct 29 13:53:25 Sailfish kernel: i2c-msm-v2 78b5000.i2c: Runtime PM-callback was not invoked.
Oct 29 13:53:25 Sailfish kernel: PM: noirq resume of devices complete after 1.779 msecs
Oct 29 13:53:25 Sailfish kernel: CPU3 is up
Oct 29 13:53:25 Sailfish kernel: CPU2 is up
Oct 29 13:53:25 Sailfish kernel: CPU1 is up
Oct 29 13:53:25 Sailfish kernel: Enabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
Oct 29 13:53:25 Sailfish kernel: Disabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: PM: noirq suspend of devices complete after 3.346 msecs
Oct 29 13:53:25 Sailfish kernel: PM: late suspend of devices complete after 2.995 msecs
Oct 29 13:53:25 Sailfish kernel: PM: suspend of devices complete after 40.109 msecs
Oct 29 13:53:25 Sailfish kernel: Suspending console(s) (use no_console_suspend to debug)
Oct 29 13:53:25 Sailfish kernel: Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
Oct 29 13:53:25 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:25 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:25 Sailfish kernel: Freezing user space processes ... (elapsed 0.007 seconds) done.
Oct 29 13:53:25 Sailfish kernel: PM: Syncing filesystems ... done.
Oct 29 13:53:24 Sailfish kernel: PM: suspend entry 2016-10-29 08:23:24.652726583 UTC
Oct 29 13:53:24 Sailfish [990]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish lipstick[1037]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish ofonod[745]: data reg changed 0 -> 1 (registered), attached 0

Please help me resolve this issue.

Update:

My cousin also has an Aqua Fish, I've tried the sim in that phone it's working there :). So, I'm not sure what my next step should be, probably reset or return the phone?

Update2:

I've reset the device. Still no luck :(:(. Tried in both sims.

Network disabled, and Problem with Connection(working in Android): why Why are some aqua fish phones are giving Connection Problem(Data stataus: enabled) while connecting data even when the network is it giving Unexpected connected?(Terminal: Unepexected data call status 55?55)

I asked a different question(https://together.jolla.com/question/144859/what-is-the-meaning-of-network-denied-in-sailfish-os-intex-aqua-fish-jio/), but the title was different and the problem has since then changed.

Bought a JIO 4G. Activation done. Data is working in Android non-volte 4G phone.
Inserted in Intex Aqua Fish, network registers quickly. Selected Prefer 4G in Mobile networks. Has set Access Point as jionet.
Tried connecting using the connection switch, it tries to connect and (a) says in the notification area "Problem with connection", and under (b) the Connection area "disabled"
Tried restarting the phone, tried restarting using "Restart network connections" (which is available in Sailifsh Utilities that I installed). No luck.
Tried updating to Sailifsh 4.0.4.14, but update is not yet pushed to the Aqua Fish devices. So I updated by enabling developer mode and using version --dup. Update was successful. But the connection issue persists.

On a sidenote: "I think" what was fixed/claimed in 4.0.14 update related to issues in JIO 4G -- are just apn settings for JIO 4G are available by default. So, since I used correct apn even before updating, there is no difference. And also, I actually did click restore to default in Data Access Point so that it populated the JIO related settings in the Data Access Point screen.

To try even this much is because, many people in this forum got it working successfully without much efforts (similar to Android 4G devices). So, I'm not sure where the problem is. Was there something got permanent when we were trying multiple things. (All are from phone screens, not devel-su).

Can a device reset help?

Now, as a next step I accessed logs using journalctcl -r.

[root@Sailfish nemo]# journalctl -r

-- Logs begin at Sat 2016-10-29 13:51:22 IST, end at Sat 2016-10-29 13:53:32 IST. --
Oct 29 13:53:32 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:32 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:33 Sailfish estart[4312]: [D] NetworkService::handleConnectReply:374 - Reply from service.connect():  "Operation aborted"
Oct 29 13:53:33 Sailfish connmand[757]: [ofono] ERROR! GDBus.Error:org.ofono.Error.Failed: Operation failed
Oct 29 13:53:33 Sailfish ofonod[745]: Unexpected data call status 55
Oct 29 13:53:32 Sailfish ofonod[745]: Activating context: 1
Oct 29 13:53:32 Sailfish connmand[757]: Skipping disconnect of /ril_0, network is connecting.
Oct 29 13:53:28 Sailfish kernel: [08:23:28.049654] [000000022A0EA8EA] [VosMC]  wlan: [E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
Oct 29 13:53:27 Sailfish statefs[568]: Display: "on"
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP already resumed.
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP wakeup sleep.
Oct 29 13:53:27 Sailfish kernel: sensors stk3311-light: Invalid value of delay, delay=0
Oct 29 13:53:27 Sailfish lipstick[1037]: [D] HwComposerContext::sleepDisplay:180 - unsleepDisplay
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3819 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3814 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:25 Sailfish kernel: PM: suspend exit 2016-10-29 08:23:25.975706327 UTC
Oct 29 13:53:25 Sailfish kernel: Restarting tasks ... done.
Oct 29 13:53:25 Sailfish kernel: PM: resume of devices complete after 82.510 msecs
Oct 29 13:53:25 Sailfish kernel: PM: early resume of devices complete after 5.054 msecs
Oct 29 13:53:25 Sailfish kernel: i2c-msm-v2 78b5000.i2c: Runtime PM-callback was not invoked.
Oct 29 13:53:25 Sailfish kernel: PM: noirq resume of devices complete after 1.779 msecs
Oct 29 13:53:25 Sailfish kernel: CPU3 is up
Oct 29 13:53:25 Sailfish kernel: CPU2 is up
Oct 29 13:53:25 Sailfish kernel: CPU1 is up
Oct 29 13:53:25 Sailfish kernel: Enabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
Oct 29 13:53:25 Sailfish kernel: Disabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: PM: noirq suspend of devices complete after 3.346 msecs
Oct 29 13:53:25 Sailfish kernel: PM: late suspend of devices complete after 2.995 msecs
Oct 29 13:53:25 Sailfish kernel: PM: suspend of devices complete after 40.109 msecs
Oct 29 13:53:25 Sailfish kernel: Suspending console(s) (use no_console_suspend to debug)
Oct 29 13:53:25 Sailfish kernel: Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
Oct 29 13:53:25 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:25 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:25 Sailfish kernel: Freezing user space processes ... (elapsed 0.007 seconds) done.
Oct 29 13:53:25 Sailfish kernel: PM: Syncing filesystems ... done.
Oct 29 13:53:24 Sailfish kernel: PM: suspend entry 2016-10-29 08:23:24.652726583 UTC
Oct 29 13:53:24 Sailfish [990]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish lipstick[1037]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish ofonod[745]: data reg changed 0 -> 1 (registered), attached 0

Please help me resolve this issue.

Update:

My cousin also has an Aqua Fish, I've tried the sim in that phone it's working there :). So, I'm not sure what my next step should be, probably reset or return the phone?

Update2:

I've reset the device. Still no luck :(. Tried in both sims.

Why are some aqua fish phones are giving Connection Problem(Data stataus: enabled) disabled) while connecting data even when the network is connected?(Terminal: Unepexected data call status 55)

I asked a different question(https://together.jolla.com/question/144859/what-is-the-meaning-of-network-denied-in-sailfish-os-intex-aqua-fish-jio/), but the title was different and the problem has since then changed.

Bought a JIO 4G. Activation done. Data is working in Android non-volte 4G phone.
Inserted in Intex Aqua Fish, network registers quickly. Selected Prefer 4G in Mobile networks. Has set Access Point as jionet.
Tried connecting using the connection switch, it tries to connect and (a) says in the notification area "Problem with connection", and under (b) the Connection area "disabled"
Tried restarting the phone, tried restarting using "Restart network connections" (which is available in Sailifsh Utilities that I installed). No luck.
Tried updating to Sailifsh 4.0.4.14, but update is not yet pushed to the Aqua Fish devices. So I updated by enabling developer mode and using version --dup. Update was successful. But the connection issue persists.

On a sidenote: "I think" what was fixed/claimed in 4.0.14 update related to issues in JIO 4G -- are just apn settings for JIO 4G are available by default. So, since I used correct apn even before updating, there is no difference. And also, I actually did click restore to default in Data Access Point so that it populated the JIO related settings in the Data Access Point screen.

To try even this much is because, many people in this forum got it working successfully without much efforts (similar to Android 4G devices). So, I'm not sure where the problem is. Was there something got permanent when we were trying multiple things. (All are from phone screens, not devel-su).

Can a device reset help?

Now, as a next step I accessed logs using journalctcl -r.

[root@Sailfish nemo]# journalctl -r

-- Logs begin at Sat 2016-10-29 13:51:22 IST, end at Sat 2016-10-29 13:53:32 IST. --
Oct 29 13:53:32 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:32 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:33 Sailfish estart[4312]: [D] NetworkService::handleConnectReply:374 - Reply from service.connect():  "Operation aborted"
Oct 29 13:53:33 Sailfish connmand[757]: [ofono] ERROR! GDBus.Error:org.ofono.Error.Failed: Operation failed
Oct 29 13:53:33 Sailfish ofonod[745]: Unexpected data call status 55
Oct 29 13:53:32 Sailfish ofonod[745]: Activating context: 1
Oct 29 13:53:32 Sailfish connmand[757]: Skipping disconnect of /ril_0, network is connecting.
Oct 29 13:53:28 Sailfish kernel: [08:23:28.049654] [000000022A0EA8EA] [VosMC]  wlan: [E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
Oct 29 13:53:27 Sailfish statefs[568]: Display: "on"
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP already resumed.
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP wakeup sleep.
Oct 29 13:53:27 Sailfish kernel: sensors stk3311-light: Invalid value of delay, delay=0
Oct 29 13:53:27 Sailfish lipstick[1037]: [D] HwComposerContext::sleepDisplay:180 - unsleepDisplay
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3819 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3814 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:25 Sailfish kernel: PM: suspend exit 2016-10-29 08:23:25.975706327 UTC
Oct 29 13:53:25 Sailfish kernel: Restarting tasks ... done.
Oct 29 13:53:25 Sailfish kernel: PM: resume of devices complete after 82.510 msecs
Oct 29 13:53:25 Sailfish kernel: PM: early resume of devices complete after 5.054 msecs
Oct 29 13:53:25 Sailfish kernel: i2c-msm-v2 78b5000.i2c: Runtime PM-callback was not invoked.
Oct 29 13:53:25 Sailfish kernel: PM: noirq resume of devices complete after 1.779 msecs
Oct 29 13:53:25 Sailfish kernel: CPU3 is up
Oct 29 13:53:25 Sailfish kernel: CPU2 is up
Oct 29 13:53:25 Sailfish kernel: CPU1 is up
Oct 29 13:53:25 Sailfish kernel: Enabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
Oct 29 13:53:25 Sailfish kernel: Disabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: PM: noirq suspend of devices complete after 3.346 msecs
Oct 29 13:53:25 Sailfish kernel: PM: late suspend of devices complete after 2.995 msecs
Oct 29 13:53:25 Sailfish kernel: PM: suspend of devices complete after 40.109 msecs
Oct 29 13:53:25 Sailfish kernel: Suspending console(s) (use no_console_suspend to debug)
Oct 29 13:53:25 Sailfish kernel: Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
Oct 29 13:53:25 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:25 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:25 Sailfish kernel: Freezing user space processes ... (elapsed 0.007 seconds) done.
Oct 29 13:53:25 Sailfish kernel: PM: Syncing filesystems ... done.
Oct 29 13:53:24 Sailfish kernel: PM: suspend entry 2016-10-29 08:23:24.652726583 UTC
Oct 29 13:53:24 Sailfish [990]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish lipstick[1037]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish ofonod[745]: data reg changed 0 -> 1 (registered), attached 0

Please help me resolve this issue.

Update:

My cousin also has an Aqua Fish, I've tried the sim in that phone it's working there :). So, I'm not sure what my next step should be, probably reset or return the phone?

Update2:

I've reset the device. Still no luck :(. Tried in both sims.

Why are some aqua fish phones are giving Connection Problem(Data stataus: disabled) while connecting data even when the network is connected?(Terminal: Unepexected data call status 55)

I asked a different question(https://together.jolla.com/question/144859/what-is-the-meaning-of-network-denied-in-sailfish-os-intex-aqua-fish-jio/), but the title was different and the problem has since then changed.Update :

The same is working in another Aqua Fish phone.

Update2:

I've reset the device. Still no luck :(. Tried in both sim slots.

Bought a JIO 4G. Activation done. Data is working in Android non-volte 4G phone.
Inserted in Intex Aqua Fish, network registers quickly. Selected Prefer 4G in Mobile networks. Has set Access Point as jionet.
Tried connecting using the connection switch, it tries to connect and (a) says in the notification area "Problem with connection", and under (b) the Connection area "disabled"
Tried restarting the phone, tried restarting using "Restart network connections" (which is available in Sailifsh Utilities that I installed). No luck.
Tried updating to Sailifsh 4.0.4.14, but update is not yet pushed to the Aqua Fish devices. So I updated by enabling developer mode and using version --dup. Update was successful. But the connection issue persists.

On a sidenote: "I think" what was fixed/claimed in 4.0.14 update related to issues in JIO 4G -- are just apn settings for JIO 4G are available by default. So, since I used correct apn even before updating, there is no difference. And also, I actually did click restore to default in Data Access Point so that it populated the JIO related settings in the Data Access Point screen.

To try even this much is because, many people in this forum got it working successfully without much efforts (similar to Android 4G devices). So, I'm not sure where the problem is. Was there something got permanent when we were trying multiple things. (All are from phone screens, not devel-su).

Can a device reset help?

Now, as a next step I accessed logs using journalctcl -r.

[root@Sailfish nemo]# journalctl -r

-- Logs begin at Sat 2016-10-29 13:51:22 IST, end at Sat 2016-10-29 13:53:32 IST. --
Oct 29 13:53:32 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:32 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:33 Sailfish estart[4312]: [D] NetworkService::handleConnectReply:374 - Reply from service.connect():  "Operation aborted"
Oct 29 13:53:33 Sailfish connmand[757]: [ofono] ERROR! GDBus.Error:org.ofono.Error.Failed: Operation failed
Oct 29 13:53:33 Sailfish ofonod[745]: Unexpected data call status 55
Oct 29 13:53:32 Sailfish ofonod[745]: Activating context: 1
Oct 29 13:53:32 Sailfish connmand[757]: Skipping disconnect of /ril_0, network is connecting.
Oct 29 13:53:28 Sailfish kernel: [08:23:28.049654] [000000022A0EA8EA] [VosMC]  wlan: [E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
Oct 29 13:53:27 Sailfish statefs[568]: Display: "on"
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP already resumed.
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP wakeup sleep.
Oct 29 13:53:27 Sailfish kernel: sensors stk3311-light: Invalid value of delay, delay=0
Oct 29 13:53:27 Sailfish lipstick[1037]: [D] HwComposerContext::sleepDisplay:180 - unsleepDisplay
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3819 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3814 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:25 Sailfish kernel: PM: suspend exit 2016-10-29 08:23:25.975706327 UTC
Oct 29 13:53:25 Sailfish kernel: Restarting tasks ... done.
Oct 29 13:53:25 Sailfish kernel: PM: resume of devices complete after 82.510 msecs
Oct 29 13:53:25 Sailfish kernel: PM: early resume of devices complete after 5.054 msecs
Oct 29 13:53:25 Sailfish kernel: i2c-msm-v2 78b5000.i2c: Runtime PM-callback was not invoked.
Oct 29 13:53:25 Sailfish kernel: PM: noirq resume of devices complete after 1.779 msecs
Oct 29 13:53:25 Sailfish kernel: CPU3 is up
Oct 29 13:53:25 Sailfish kernel: CPU2 is up
Oct 29 13:53:25 Sailfish kernel: CPU1 is up
Oct 29 13:53:25 Sailfish kernel: Enabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
Oct 29 13:53:25 Sailfish kernel: Disabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: PM: noirq suspend of devices complete after 3.346 msecs
Oct 29 13:53:25 Sailfish kernel: PM: late suspend of devices complete after 2.995 msecs
Oct 29 13:53:25 Sailfish kernel: PM: suspend of devices complete after 40.109 msecs
Oct 29 13:53:25 Sailfish kernel: Suspending console(s) (use no_console_suspend to debug)
Oct 29 13:53:25 Sailfish kernel: Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
Oct 29 13:53:25 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:25 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:25 Sailfish kernel: Freezing user space processes ... (elapsed 0.007 seconds) done.
Oct 29 13:53:25 Sailfish kernel: PM: Syncing filesystems ... done.
Oct 29 13:53:24 Sailfish kernel: PM: suspend entry 2016-10-29 08:23:24.652726583 UTC
Oct 29 13:53:24 Sailfish [990]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish lipstick[1037]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish ofonod[745]: data reg changed 0 -> 1 (registered), attached 0

Please help me resolve this issue.

Update:

My cousin also has an Aqua Fish, I've tried the sim in that phone it's working there :). So, I'm not sure what my next step should be, probably reset or return the phone?

Update2:

I've reset the device. Still no luck :(. Tried in both sims.

Why are some aqua fish phones are giving Connection Problem(Data stataus: disabled) while connecting is data even when the network is connected?(Terminal: Unepexected enabled with my JIO sim card in an Aqua Fish phone but not mine? (Journalctl: Unexpected call data call status 55)

Update :

The same is working in another Aqua Fish phone.

Update2:

I've reset the device. Still no luck :(. Tried in both sim slots.

Bought a JIO 4G. Activation done. Data is working in Android non-volte 4G phone.
Inserted in Intex Aqua Fish, network registers quickly. Selected Prefer 4G in Mobile networks. Has set Access Point as jionet.
Tried connecting using the connection switch, it tries to connect and (a) says in the notification area "Problem with connection", and under (b) the Connection area "disabled"
Tried restarting the phone, tried restarting using "Restart network connections" (which is available in Sailifsh Utilities that I installed). No luck.
Tried updating to Sailifsh 4.0.4.14, but update is not yet pushed to the Aqua Fish devices. So I updated by enabling developer mode and using version --dup. Update was successful. But the connection issue persists.

On a sidenote: "I think" what was fixed/claimed in 4.0.14 update related to issues in JIO 4G -- are just apn settings for JIO 4G are available by default. So, since I used correct apn even before updating, there is no difference. And also, I actually did click restore to default in Data Access Point so that it populated the JIO related settings in the Data Access Point screen.

To try even this much is because, many people in this forum got it working successfully without much efforts (similar to Android 4G devices). So, I'm not sure where the problem is. Was there something got permanent when we were trying multiple things. (All are from phone screens, not devel-su).

Can a device reset help?

Now, as a next step I accessed logs using journalctcl -r.

[root@Sailfish nemo]# journalctl -r

-- Logs begin at Sat 2016-10-29 13:51:22 IST, end at Sat 2016-10-29 13:53:32 IST. --
Oct 29 13:53:32 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:32 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:33 Sailfish estart[4312]: [D] NetworkService::handleConnectReply:374 - Reply from service.connect():  "Operation aborted"
Oct 29 13:53:33 Sailfish connmand[757]: [ofono] ERROR! GDBus.Error:org.ofono.Error.Failed: Operation failed
Oct 29 13:53:33 Sailfish ofonod[745]: Unexpected data call status 55
Oct 29 13:53:32 Sailfish ofonod[745]: Activating context: 1
Oct 29 13:53:32 Sailfish connmand[757]: Skipping disconnect of /ril_0, network is connecting.
Oct 29 13:53:28 Sailfish kernel: [08:23:28.049654] [000000022A0EA8EA] [VosMC]  wlan: [E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
Oct 29 13:53:27 Sailfish statefs[568]: Display: "on"
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP already resumed.
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP wakeup sleep.
Oct 29 13:53:27 Sailfish kernel: sensors stk3311-light: Invalid value of delay, delay=0
Oct 29 13:53:27 Sailfish lipstick[1037]: [D] HwComposerContext::sleepDisplay:180 - unsleepDisplay
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3819 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3814 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:25 Sailfish kernel: PM: suspend exit 2016-10-29 08:23:25.975706327 UTC
Oct 29 13:53:25 Sailfish kernel: Restarting tasks ... done.
Oct 29 13:53:25 Sailfish kernel: PM: resume of devices complete after 82.510 msecs
Oct 29 13:53:25 Sailfish kernel: PM: early resume of devices complete after 5.054 msecs
Oct 29 13:53:25 Sailfish kernel: i2c-msm-v2 78b5000.i2c: Runtime PM-callback was not invoked.
Oct 29 13:53:25 Sailfish kernel: PM: noirq resume of devices complete after 1.779 msecs
Oct 29 13:53:25 Sailfish kernel: CPU3 is up
Oct 29 13:53:25 Sailfish kernel: CPU2 is up
Oct 29 13:53:25 Sailfish kernel: CPU1 is up
Oct 29 13:53:25 Sailfish kernel: Enabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
Oct 29 13:53:25 Sailfish kernel: Disabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: PM: noirq suspend of devices complete after 3.346 msecs
Oct 29 13:53:25 Sailfish kernel: PM: late suspend of devices complete after 2.995 msecs
Oct 29 13:53:25 Sailfish kernel: PM: suspend of devices complete after 40.109 msecs
Oct 29 13:53:25 Sailfish kernel: Suspending console(s) (use no_console_suspend to debug)
Oct 29 13:53:25 Sailfish kernel: Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
Oct 29 13:53:25 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:25 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:25 Sailfish kernel: Freezing user space processes ... (elapsed 0.007 seconds) done.
Oct 29 13:53:25 Sailfish kernel: PM: Syncing filesystems ... done.
Oct 29 13:53:24 Sailfish kernel: PM: suspend entry 2016-10-29 08:23:24.652726583 UTC
Oct 29 13:53:24 Sailfish [990]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish lipstick[1037]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish ofonod[745]: data reg changed 0 -> 1 (registered), attached 0

Please help me resolve this issue.

Why is LTE/4G data enabled with works on my JIO sim card in an Aqua Fish phone friend's Intex Aquafish but not mine? the same SIM doesn't work on my Aquafish? (Journalctl: Unexpected call data 55)

Update :

The same is working in another Aqua Fish phone.

Update2:

I've reset the device. Still no luck :(. Tried in both sim slots.

Bought a JIO 4G. Activation done. Data is working in Android non-volte 4G phone.
Inserted in Intex Aqua Fish, network registers quickly. Selected Prefer 4G in Mobile networks. Has set Access Point as jionet.
Tried connecting using the connection switch, it tries to connect and (a) says in the notification area "Problem with connection", and under (b) the Connection area "disabled"
Tried restarting the phone, tried restarting using "Restart network connections" (which is available in Sailifsh Utilities that I installed). No luck.
Tried updating to Sailifsh 4.0.4.14, but update is not yet pushed to the Aqua Fish devices. So I updated by enabling developer mode and using version --dup. Update was successful. But the connection issue persists.

On a sidenote: "I think" what was fixed/claimed in 4.0.14 update related to issues in JIO 4G -- are just apn settings for JIO 4G are available by default. So, since I used correct apn even before updating, there is no difference. And also, I actually did click restore to default in Data Access Point so that it populated the JIO related settings in the Data Access Point screen.

To try even this much is because, many people in this forum got it working successfully without much efforts (similar to Android 4G devices). So, I'm not sure where the problem is. Was there something got permanent when we were trying multiple things. (All are from phone screens, not devel-su).

Can a device reset help?

Now, as a next step I accessed logs using journalctcl -r.

[root@Sailfish nemo]# journalctl -r

-- Logs begin at Sat 2016-10-29 13:51:22 IST, end at Sat 2016-10-29 13:53:32 IST. --
Oct 29 13:53:32 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:32 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:33 Sailfish estart[4312]: [D] NetworkService::handleConnectReply:374 - Reply from service.connect():  "Operation aborted"
Oct 29 13:53:33 Sailfish connmand[757]: [ofono] ERROR! GDBus.Error:org.ofono.Error.Failed: Operation failed
Oct 29 13:53:33 Sailfish ofonod[745]: Unexpected data call status 55
Oct 29 13:53:32 Sailfish ofonod[745]: Activating context: 1
Oct 29 13:53:32 Sailfish connmand[757]: Skipping disconnect of /ril_0, network is connecting.
Oct 29 13:53:28 Sailfish kernel: [08:23:28.049654] [000000022A0EA8EA] [VosMC]  wlan: [E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
Oct 29 13:53:27 Sailfish statefs[568]: Display: "on"
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP already resumed.
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP wakeup sleep.
Oct 29 13:53:27 Sailfish kernel: sensors stk3311-light: Invalid value of delay, delay=0
Oct 29 13:53:27 Sailfish lipstick[1037]: [D] HwComposerContext::sleepDisplay:180 - unsleepDisplay
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3819 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3814 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:25 Sailfish kernel: PM: suspend exit 2016-10-29 08:23:25.975706327 UTC
Oct 29 13:53:25 Sailfish kernel: Restarting tasks ... done.
Oct 29 13:53:25 Sailfish kernel: PM: resume of devices complete after 82.510 msecs
Oct 29 13:53:25 Sailfish kernel: PM: early resume of devices complete after 5.054 msecs
Oct 29 13:53:25 Sailfish kernel: i2c-msm-v2 78b5000.i2c: Runtime PM-callback was not invoked.
Oct 29 13:53:25 Sailfish kernel: PM: noirq resume of devices complete after 1.779 msecs
Oct 29 13:53:25 Sailfish kernel: CPU3 is up
Oct 29 13:53:25 Sailfish kernel: CPU2 is up
Oct 29 13:53:25 Sailfish kernel: CPU1 is up
Oct 29 13:53:25 Sailfish kernel: Enabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
Oct 29 13:53:25 Sailfish kernel: Disabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: PM: noirq suspend of devices complete after 3.346 msecs
Oct 29 13:53:25 Sailfish kernel: PM: late suspend of devices complete after 2.995 msecs
Oct 29 13:53:25 Sailfish kernel: PM: suspend of devices complete after 40.109 msecs
Oct 29 13:53:25 Sailfish kernel: Suspending console(s) (use no_console_suspend to debug)
Oct 29 13:53:25 Sailfish kernel: Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
Oct 29 13:53:25 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:25 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:25 Sailfish kernel: Freezing user space processes ... (elapsed 0.007 seconds) done.
Oct 29 13:53:25 Sailfish kernel: PM: Syncing filesystems ... done.
Oct 29 13:53:24 Sailfish kernel: PM: suspend entry 2016-10-29 08:23:24.652726583 UTC
Oct 29 13:53:24 Sailfish [990]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish lipstick[1037]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish ofonod[745]: data reg changed 0 -> 1 (registered), attached 0

Please help me resolve this issue.

LTE/4G data works on my friend's Intex Aquafish but the same SIM doesn't work on my Aquafish? (Journalctl: Unexpected call data 55)

Update :

The same is working in another Aqua Fish phone.

Update2:

I've reset the device. Still no luck :(. Tried in both sim slots.

Bought a JIO 4G. Activation done. Data is working in Android non-volte 4G phone.
Inserted in Intex Aqua Fish, network registers quickly. Selected Prefer 4G in Mobile networks. Has set Access Point as jionet.
Tried connecting using the connection switch, it tries to connect and (a) says in the notification area "Problem with connection", and under (b) the Connection area "disabled"
Tried restarting the phone, tried restarting using "Restart network connections" (which is available in Sailifsh Utilities that I installed). No luck.
Tried updating to Sailifsh 4.0.4.14, but update is not yet pushed to the Aqua Fish devices. So I updated by enabling developer mode and using version --dup. Update was successful. But the connection issue persists.

On a sidenote: "I think" what was fixed/claimed in 4.0.14 update related to issues in JIO 4G -- are just apn settings for JIO 4G are available by default. So, since I used correct apn even before updating, there is no difference. And also, I actually did click restore to default in Data Access Point so that it populated the JIO related settings in the Data Access Point screen.

To try even this much is because, many people in this forum got it working successfully without much efforts (similar to Android 4G devices). So, I'm not sure where the problem is. Was there something got permanent when we were trying multiple things. (All are from phone screens, not devel-su).

Can a device reset help?

Now, as a next step I accessed logs using journalctcl -r.

[root@Sailfish nemo]# journalctl -r

-- Logs begin at Sat 2016-10-29 13:51:22 IST, end at Sat 2016-10-29 13:53:32 IST. --
Oct 29 13:53:32 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:32 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:33 Sailfish estart[4312]: [D] NetworkService::handleConnectReply:374 - Reply from service.connect():  "Operation aborted"
Oct 29 13:53:33 Sailfish connmand[757]: [ofono] ERROR! GDBus.Error:org.ofono.Error.Failed: Operation failed
Oct 29 13:53:33 Sailfish ofonod[745]: Unexpected data call status 55
Oct 29 13:53:32 Sailfish ofonod[745]: Activating context: 1
Oct 29 13:53:32 Sailfish connmand[757]: Skipping disconnect of /ril_0, network is connecting.
Oct 29 13:53:28 Sailfish kernel: [08:23:28.049654] [000000022A0EA8EA] [VosMC]  wlan: [E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
Oct 29 13:53:27 Sailfish statefs[568]: Display: "on"
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP already resumed.
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP wakeup sleep.
Oct 29 13:53:27 Sailfish kernel: sensors stk3311-light: Invalid value of delay, delay=0
Oct 29 13:53:27 Sailfish lipstick[1037]: [D] HwComposerContext::sleepDisplay:180 - unsleepDisplay
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3819 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3814 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:25 Sailfish kernel: PM: suspend exit 2016-10-29 08:23:25.975706327 UTC
Oct 29 13:53:25 Sailfish kernel: Restarting tasks ... done.
Oct 29 13:53:25 Sailfish kernel: PM: resume of devices complete after 82.510 msecs
Oct 29 13:53:25 Sailfish kernel: PM: early resume of devices complete after 5.054 msecs
Oct 29 13:53:25 Sailfish kernel: i2c-msm-v2 78b5000.i2c: Runtime PM-callback was not invoked.
Oct 29 13:53:25 Sailfish kernel: PM: noirq resume of devices complete after 1.779 msecs
Oct 29 13:53:25 Sailfish kernel: CPU3 is up
Oct 29 13:53:25 Sailfish kernel: CPU2 is up
Oct 29 13:53:25 Sailfish kernel: CPU1 is up
Oct 29 13:53:25 Sailfish kernel: Enabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
Oct 29 13:53:25 Sailfish kernel: Disabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: PM: noirq suspend of devices complete after 3.346 msecs
Oct 29 13:53:25 Sailfish kernel: PM: late suspend of devices complete after 2.995 msecs
Oct 29 13:53:25 Sailfish kernel: PM: suspend of devices complete after 40.109 msecs
Oct 29 13:53:25 Sailfish kernel: Suspending console(s) (use no_console_suspend to debug)
Oct 29 13:53:25 Sailfish kernel: Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
Oct 29 13:53:25 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:25 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:25 Sailfish kernel: Freezing user space processes ... (elapsed 0.007 seconds) done.
Oct 29 13:53:25 Sailfish kernel: PM: Syncing filesystems ... done.
Oct 29 13:53:24 Sailfish kernel: PM: suspend entry 2016-10-29 08:23:24.652726583 UTC
Oct 29 13:53:24 Sailfish [990]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish lipstick[1037]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish ofonod[745]: data reg changed 0 -> 1 (registered), attached 0

Please help me resolve this ~~issue.~~issue. I'm sure this is only happening with Jio Sim in some Aqua Fish phones.

LTE/4G data works on my friend's Intex Aquafish but the same SIM doesn't work on my Aquafish? (Journalctl: Unexpected call data 55)

Update :

The same is working in another Aqua Fish phone.

Update2:

I've reset the device. Still no luck :(. Tried in both sim slots.

Bought a JIO 4G. Activation done. Data is working in Android non-volte 4G phone.
Inserted in Intex Aqua Fish, network registers quickly. Selected Prefer 4G in Mobile networks. Has set Access Point as jionet.
Tried connecting using the connection switch, it tries to connect and (a) says in the notification area "Problem with connection", and under (b) the Connection area "disabled"
Tried restarting the phone, tried restarting using "Restart network connections" (which is available in Sailifsh Utilities that I installed). No luck.
Tried updating to Sailifsh 4.0.4.14, but update is not yet pushed to the Aqua Fish devices. So I updated by enabling developer mode and using version --dup. Update was successful. But the connection issue persists.

On a sidenote: "I think" what was fixed/claimed in 4.0.14 update related to issues in JIO 4G -- are just apn settings for JIO 4G are available by default. So, since I used correct apn even before updating, there is no difference. And also, I actually did click restore to default in Data Access Point so that it populated the JIO related settings in the Data Access Point screen.

To try even this much is because, many people in this forum got it working successfully without much efforts (similar to Android 4G devices). So, I'm not sure where the problem is. Was there something got permanent when we were trying multiple things. (All are from phone screens, not devel-su).

Can a device reset help?

Now, as a next step I accessed logs using journalctcl -r.

[root@Sailfish nemo]# journalctl -r

-- Logs begin at Sat 2016-10-29 13:51:22 IST, end at Sat 2016-10-29 13:53:32 IST. --
Oct 29 13:53:32 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:32 Sailfish systemd[928]: Time has been changed
 Oct 29 13:53:33 Sailfish estart[4312]: [D] NetworkService::handleConnectReply:374 - Reply from service.connect():  "Operation aborted"
Oct 29 13:53:33 Sailfish connmand[757]: [ofono] ERROR! GDBus.Error:org.ofono.Error.Failed: Operation failed
Oct 29 13:53:33 Sailfish ofonod[745]: Unexpected data call status 55
Oct 29 13:53:32 Sailfish ofonod[745]: Activating context: 1
Oct 29 13:53:32 Sailfish connmand[757]: Skipping disconnect of /ril_0, network is connecting.
Oct 29 13:53:28 Sailfish kernel: [08:23:28.049654] [000000022A0EA8EA] [VosMC]  wlan: [E :HDP] hdd_tx_rx_pkt_cnt_stat_timer_handler: Disable split scan
Oct 29 13:53:27 Sailfish statefs[568]: Display: "on"
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP already resumed.
Oct 29 13:53:27 Sailfish kernel: hdd_fb_blank_notifier_cb: Got FB BLANK, blank 0
Oct 29 13:53:27 Sailfish kernel: Goodix-TS 5-005d: GTP wakeup sleep.
Oct 29 13:53:27 Sailfish kernel: sensors stk3311-light: Invalid value of delay, delay=0
Oct 29 13:53:27 Sailfish lipstick[1037]: [D] HwComposerContext::sleepDisplay:180 - unsleepDisplay
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3819 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:26 Sailfish healthd: battery l=47 v=3814 t=36.0 h=2 st=3 c=177 chg=
Oct 29 13:53:25 Sailfish kernel: PM: suspend exit 2016-10-29 08:23:25.975706327 UTC
Oct 29 13:53:25 Sailfish kernel: Restarting tasks ... done.
Oct 29 13:53:25 Sailfish kernel: PM: resume of devices complete after 82.510 msecs
Oct 29 13:53:25 Sailfish kernel: PM: early resume of devices complete after 5.054 msecs
Oct 29 13:53:25 Sailfish kernel: i2c-msm-v2 78b5000.i2c: Runtime PM-callback was not invoked.
Oct 29 13:53:25 Sailfish kernel: PM: noirq resume of devices complete after 1.779 msecs
Oct 29 13:53:25 Sailfish kernel: CPU3 is up
Oct 29 13:53:25 Sailfish kernel: CPU2 is up
Oct 29 13:53:25 Sailfish kernel: CPU1 is up
Oct 29 13:53:25 Sailfish kernel: Enabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
Oct 29 13:53:25 Sailfish kernel: Disabling non-boot CPUs ...
Oct 29 13:53:25 Sailfish kernel: PM: noirq suspend of devices complete after 3.346 msecs
Oct 29 13:53:25 Sailfish kernel: PM: late suspend of devices complete after 2.995 msecs
Oct 29 13:53:25 Sailfish kernel: PM: suspend of devices complete after 40.109 msecs
Oct 29 13:53:25 Sailfish kernel: Suspending console(s) (use no_console_suspend to debug)
Oct 29 13:53:25 Sailfish kernel: Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
Oct 29 13:53:25 Sailfish systemd[928]: Time has been changed
Oct 29 13:53:25 Sailfish systemd[1]: Time has been changed
Oct 29 13:53:25 Sailfish kernel: Freezing user space processes ... (elapsed 0.007 seconds) done.
Oct 29 13:53:25 Sailfish kernel: PM: Syncing filesystems ... done.
Oct 29 13:53:24 Sailfish kernel: PM: suspend entry 2016-10-29 08:23:24.652726583 UTC
Oct 29 13:53:24 Sailfish [990]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish lipstick[1037]: [D] QOfonoNetworkRegistrationInterface::getProperties:238 - "Object path cannot be empty"
Oct 29 13:53:24 Sailfish ofonod[745]: data reg changed 0 -> 1 (registered), attached 0

Please help me resolve this issue. I'm sure this is only happening with Jio Sim in some Aqua Fish phones.

Revision history [back]

JIO 4G network disabled, and Problem with Connection(working in Android)

JIO 4G network disabled, and Problem with Connection(working in Android)

JIO 4G network disabled, and Problem with Connection(working in Android)

JIO 4G network disabled, and Problem with Connection(working in Android)Android): why is it giving Unexpected data call status 55?

JIO 4G network disabled, and Problem with Connection(working in Android): why is it giving Unexpected data call status 55?

JIO 4G network disabled, and Problem with Connection(working in Android): why is it giving Unexpected data call status 55?

JIO 4G network Network disabled, and Problem with Connection(working in Android): why is it giving Unexpected data call status 55?

Network disabled, and Problem with Connection(working in Android): why is it giving Unexpected data call status 55?

Network disabled, and Problem with Connection(working in Android): why Why are some aqua fish phones are giving Connection Problem(Data stataus: enabled) while connecting data even when the network is it giving Unexpected connected?(Terminal: Unepexected data call status 55?55)

Why are some aqua fish phones are giving Connection Problem(Data stataus: enabled) disabled) while connecting data even when the network is connected?(Terminal: Unepexected data call status 55)

Why are some aqua fish phones are giving Connection Problem(Data stataus: disabled) while connecting data even when the network is connected?(Terminal: Unepexected data call status 55)

Why are some aqua fish phones are giving Connection Problem(Data stataus: disabled) while connecting is data even when the network is connected?(Terminal: Unepexected enabled with my JIO sim card in an Aqua Fish phone but not mine? (Journalctl: Unexpected call data call status 55)

Why is LTE/4G data enabled with works on my JIO sim card in an Aqua Fish phone friend's Intex Aquafish but not mine? the same SIM doesn't work on my Aquafish? (Journalctl: Unexpected call data 55)

LTE/4G data works on my friend's Intex Aquafish but the same SIM doesn't work on my Aquafish? (Journalctl: Unexpected call data 55)

LTE/4G data works on my friend's Intex Aquafish but the same SIM doesn't work on my Aquafish? (Journalctl: Unexpected call data 55)