Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No network on 16.04, calls freezes , unable make or receive immediately another call. #860

Closed
Stefano0101 opened this Issue Sep 4, 2018 · 60 comments

Comments

Projects
@Stefano0101
Copy link

commented Sep 4, 2018

Description of the feature

Illustrations

screenshot20180903_090502921

  • Device: Meizu Pro 5
  • Channel: 16.04/stable & rc
  • Build: OTA-4 & 2018 -W35

Steps to reproduce

Initiate a call, finish the call and the screen immediately shows "NO NETWORK" message. No call are possible to make or receive at this time even when network indicator shows network as connected. This situation can last couple of seconds, up to some seriously long time...we're talking minutes here. Switching on and off the Flight mode or a reboot help to solve this issue temporarily, until the next call.

Expected behavior

Make or receive a call and upon hang up, there should be no problem to make or receive another call.

Actual behavior

Initiate a call, finish the call and the screen immediately shows "NO NETWORK" message. No call are possible to make or receive at this time. This situation can last couple of seconds, up to some seriously long time...we're talking minutes here. Switching on and off the Flight mode or a reboot help to solve this issue temporarily, until the next call. This did not happened on 15.04. Only introduced by 16.04/stable/rc

There is an additional issue. While in call, sometimes the menu freezes and it's impossible to close the call. Again, switching Flight mode on and off, helps close the call. This particular issue was fixed previously in 15.04 and it seam it found the way back to 16.04

Logfiles and additional information

@Stefano0101

This comment has been minimized.

Copy link
Author

commented Sep 4, 2018

@Stefano0101

This comment has been minimized.

Copy link
Author

commented Sep 4, 2018

also, the mobile network manager can't remember preferences set on dual sim phones. If selected one particular network for phone calls and texts, upon hang up, the preferred network for call is not selected. It seams to default to SIM1, for whatever reason. This is inconvenient, just in case if I need to make another call to the same No., if it chooses the other SIM, this could be costly call.

@dark-eye

This comment has been minimized.

Copy link

commented Sep 4, 2018

same issue on my pro 5

@mihaelmilea

This comment has been minimized.

Copy link

commented Sep 4, 2018

Same here on my Pro 5 just that rarely it's about 10 seconds, usually more like about two or three seconds.

@Stefano0101

This comment has been minimized.

Copy link
Author

commented Sep 5, 2018

Last time I counted the time, it was 20 seconds, in an area with a full signal.

@thebosbird

This comment has been minimized.

Copy link

commented Sep 6, 2018

@Stefano0101 ... This situation can last couple of seconds, up to some seriously long time ...

The first time, it only takes a few seconds, but repeating making a call and ending the call (make a call by selecting a phonenumber and hit the green phone button, than when it rings hit the red phone button) the time you'll see the 'NO NETWORK' message increases until it won't disappear and you'll have to reboot or try Flight mode on and off.

Besides that you can't make a call or receive a call during the 'NO NETWORK' message, but your cellular data keeps working. So you'll still have your internet connection (I checked but Wifi was selected to off)

Phone OPO with 16.04 dev

@Stefano0101

This comment has been minimized.

Copy link
Author

commented Sep 8, 2018

seems that 16.04 stable is little bit better then the rc... so I'm staying on Stable for the time being.

@yugioh2017

This comment has been minimized.

Copy link

commented Oct 27, 2018

same here, BQ E4.5 16.04 stable

@mgresko8

This comment has been minimized.

Copy link

commented Oct 28, 2018

I confirm both issues on 16.04. But it is not true the second one was fixed in 15.04. I was suffering it also in latest 15.04.

@mgresko8

This comment has been minimized.

Copy link

commented Oct 28, 2018

And moreover huge phone application flickering apperad after upgrade to 16.04. I think it could be related.

@yugioh2017

This comment has been minimized.

Copy link

commented Oct 29, 2018

Also, I'm getting phone calls but it's not ringing when the "No Network" appears!!!!

@yugioh2017

This comment has been minimized.

Copy link

commented Oct 29, 2018

This issue caused some problems to me since people are calling and I'm not answering, downgrading to 15.04 till a fix is released.

@mgresko8

This comment has been minimized.

Copy link

commented Nov 27, 2018

Is there some possibility to rise the priority on this issue? It is quite critical. It is related to the phone's basic function.

@yugioh2017

This comment has been minimized.

Copy link

commented Nov 27, 2018

PLEASE FIX IT ASAP.

@hummlbach

This comment has been minimized.

Copy link
Collaborator

commented Nov 27, 2018

You really don't need the caps here! We can read you well...
Are you guys on current rc?
Me does not see that on his pro 5 @ 2018-W48 rc

@mihaelmilea

This comment has been minimized.

Copy link

commented Nov 27, 2018

I'm on current rc, Pro 5 and still have the issue...

@yugioh2017

This comment has been minimized.

Copy link

commented Nov 27, 2018

I'm on development (16.04 E4.5) and installing all the updates everyday but the issue to stay, I've also tried to downgrade to 15.04 and failed :(

@hummlbach

This comment has been minimized.

Copy link
Collaborator

commented Nov 28, 2018

Now i've seen that too. Doesn't happen always here. Switching mobile data off and on (after each call) seems to resolve it in my case. I didn't have that on 15.04 for sure. I have also updated the radio firmware at the same time...

@mgresko8

This comment has been minimized.

Copy link

commented Dec 12, 2018

Quite critical bug. Is somebody working on it?

@yugioh2017

This comment has been minimized.

Copy link

commented Dec 12, 2018

Any update on this? I've updated to the latest dev update and the issue is not fixed :(

@Stefano0101

This comment has been minimized.

Copy link
Author

commented Dec 12, 2018

OTA-6 and the issue persist. Same as on previous 16.04 OTA-5. Sometimes nothing else (flight mode on/off, data off/on ) only a reboot helps. It's rather a annoying when you trying to call someone, first call is not picked up and then can't make a second call as this is happening. Or the other party tries to call you and it goes straight to voice mail.

@yugioh2017

This comment has been minimized.

Copy link

commented Dec 13, 2018

I'm pretty sure the ubports developers are using Android or iOS as their main phones and don't care if Ubuntu touch users doesn't make or receive calls.

@Stefano0101

This comment has been minimized.

Copy link
Author

commented Dec 13, 2018

yugioh2017 you don't need to be mean, they trying their best, in they free time, don't get paid for it (only a few of them). After all, if you don't like UT, nobody force you to use it. How about help them instead of such a statement?

@yugioh2017

This comment has been minimized.

Copy link

commented Dec 13, 2018

Stefano0101 I'm Ubuntu lover and that's why I'm talking like this, I don't need any features I'm ok with it but they called it a phone for a reason, so you can make and receive calls, I don't want to be forced to move to another OS because I can't make or receive calls it's really disappointing.
I'm ready to help them and even pay to them so they can fix this annoying bug, I hope you understand me.

@mihaelmilea

This comment has been minimized.

Copy link

commented Dec 13, 2018

yugioh2017, I am not a developer but an user. I fell your pain but I strongly disagree with the use of expressions like "really disappointing" or the idea that someone could pay and have things done. Please understand that I don't see myself as someone able to teach people lessons but rather I am learning what an opensource comunity means and that actually all that is part of the UT project, including the rithm at which bugs are solved.

@UniversalSuperBox

This comment has been minimized.

Copy link
Member

commented Dec 13, 2018

A huge majority of the Ubuntu Touch developers are, as noted in this thread, volunteers who do this out of their own passion for the platform. We are supporting a platform we didn't create on hardware devices that we don't have the source code to modify. I personally don't have this device and it's very difficult (read: expensive) to get one into the US.

@yugioh2017, I understand that you're upset but yelling at people is not acceptable or helpful.

Something useful to add to this report would be the contents of /var/log/syslog directly after the issue occurs. That would give us insight into exactly what has happened when "No network" appears. As it is, looking through the logs in this thread is difficult since I'm not able to find the log statements which are relevant to what we're trying to solve.

@Stefano0101

This comment has been minimized.

Copy link
Author

commented Dec 13, 2018

Stefano0101 I'm Ubuntu lover and that's why I'm talking like this, I don't need any features I'm ok with it but they called it a phone for a reason, so you can make and receive calls, I don't want to be forced to move to another OS because I can't make or receive calls it's really disappointing.
I'm ready to help them and even pay to them so they can fix this annoying bug, I hope you understand me.

I understand you perfectly. The other day I was at breaking point, wanted to smash the phone on the wall or floor. Couldn't make or receive a call, when needed, so stressful. Yeah, phone should be able to make a call when needed and you are totally right about that. Just comments like the one you made won't help. But maybe you wanted just stir the water so UBports guys notice this bug?!? Anyway, hoping the fix is on the way.

@yugioh2017

This comment has been minimized.

Copy link

commented Dec 13, 2018

Only who is using UT as a daily and main phone would know why I'm talking like this, I'm really sorry if I hurt you by my words, but also I hope you understand the problem here it been a month without taking any attention although it is really critical issue, I have faith in Ubuntu and UT and in UBPorts guys, I hope you guys help us here.
syslog: https://pastebin.com/jEkwv1Zj

@Stefano0101

This comment has been minimized.

Copy link
Author

commented Dec 14, 2018

This is one of the main reasons why we are moving to gitlab, we are aware that the bug system is not great and we do have a problem here. But gitlab has a much more promising bug reporting system allowing us to better utilize the bug system.

Also please understand, we are a small team with a huge task, we have many moving parts and moving to a newer version of mir and unity8 at the same time is not helping, we are doing our best to make an an awesome operative system. but we are in a really busy period after taking over from canonical, we updated to xenial, we are updating mir and updating unity8 all these are huge since canonical left it far behind the latest releases, this forces us to make major changes. We are also building Halium and following the evolving of android and newer devices to be able to follow the mobile marked. At halium we are also trying to move our sensor, gps, media and camera system over to an active maintained system instead of maintaining our own. And we are also looking at merging our patched in celluar and pulse with an active maintained one. Once we move things to active maintained systems where we can work together to get to the same goal, we will then get more time to focuses on core functions.

About replacing the browser, this is an huge part for us, we are not able to maintain our own fork of chromium (oxide) that why we are forced to move the browser, this move will in fact give more time to focused on the core functions on the phone.

There is also a low amount of pro 5 out there with Ubuntu Touch, this results in out low amount of pro 5's in the qa team. This has resulted in this bug slipped the radar. Please if anyone here wants to help out our qa team let me know.

And i'm deeply sorry that this happened, this should have been fixed before. I'll do my best to get it fixed asap!

I'm ready to help QA team, let me know if and when testing is needed.

@mgresko8

This comment has been minimized.

Copy link

commented Dec 14, 2018

@Stefano0101

This comment has been minimized.

Copy link
Author

commented Dec 16, 2018

syslog attached, right after No network message, after 3 calls, then no network for a long time.
syslog.zip

@yugioh2017

This comment has been minimized.

Copy link

commented Dec 24, 2018

I thought they would give us a christmas gift by fixing this bug, but it seems we have to wait months before they start working on it :(

@advocatux

This comment has been minimized.

Copy link

commented Dec 25, 2018

@yugioh2017 friendly reminder: there is no "they", this volunteer based project is all about "we" ;)

That means too that if you want a specific issue fixed, you need to do it yourself, find a developer, or wait until it gets its turn in the (huge) pending queue :)

@yugioh2017

This comment has been minimized.

Copy link

commented Dec 25, 2018

"they" broke the phone not "we" or "us", it was working perfectly till "they" got involved. I'm no longer waiting the fix.
There's no hope in developing UT since there's not intention in making even the basic phone functions works, for sure I didn't mention the "internet browser" that hangs on most of websites or not able to hang a call, etc....

@yugioh2017

This comment has been minimized.

Copy link

commented Dec 25, 2018

@yugioh2017 friendly reminder: there is no "they", this volunteer based project is all about "we" ;)

That means too that if you want a specific issue fixed, you need to do it yourself, find a developer, or wait until it gets its turn in the (huge) pending queue :)

Then, the UBPorts slogan should be: We broke UT functions and you should find a developer to fix them.

@mariogrip

This comment has been minimized.

Copy link
Member

commented Dec 25, 2018

No useful input here, locked.

As I said before, this bug will be fixed, i will even try right now even although its xmas. we try our best to fix as many bugs as we can, but we don't have apple money and developers. But the fact is that there is a lot of bugs, and the pro5 has little userbase so its not always it will get the highest priority.

I know this is a bad bug, we will get it fixed and i'm sorry it took so long. but this input does not help the matter :)

@ubports ubports locked as too heated and limited conversation to collaborators Dec 25, 2018

mariogrip added a commit to ubports/telepathy-ofono that referenced this issue Dec 25, 2018

@mariogrip

This comment has been minimized.

Copy link
Member

commented Dec 25, 2018

Ok, so got this fixed: ubports/telepathy-ofono#3

Please test, use sudo ubports-qa install xenial_-_fix-end-call install

@ubports ubports unlocked this conversation Dec 25, 2018

@mariogrip

This comment has been minimized.

Copy link
Member

commented Dec 25, 2018

There we go, a fix for it. Merry Christmas everyone!

@mariogrip mariogrip closed this Dec 25, 2018

@yugioh2017

This comment has been minimized.

Copy link

commented Dec 26, 2018

Finally!!! Thank you!!!! Merry Christmas everyone (including Ubports team :P) ! Long live UT!

@mariogrip mariogrip added this to the 16.04 OTA-7 milestone Dec 26, 2018

@mariogrip mariogrip self-assigned this Dec 26, 2018

@mihaelmilea

This comment has been minimized.

Copy link

commented Dec 26, 2018

Beautiful! Wonderful! Fixed! Thank you! Merry Christmas!

@Stefano0101

This comment has been minimized.

Copy link
Author

commented Dec 26, 2018

Thank you Marius, it seems to be fixed, no trouble with it now. If I observe anything else, I'll let you know. Merry Christmas!

@UniversalSuperBox UniversalSuperBox added this to To do in OTA-7 via automation Dec 26, 2018

@UniversalSuperBox UniversalSuperBox removed this from the 16.04 OTA-7 milestone Dec 26, 2018

@UniversalSuperBox UniversalSuperBox moved this from To do to Done in OTA-7 Dec 26, 2018

@thebosbird

This comment has been minimized.

Copy link

commented Dec 27, 2018

Thank you Marius! Tested it in Dev mode (BQ E4.5) and the problem is gone! This bug was, as for many, a very big problem for me.

@advocatux

This comment has been minimized.

Copy link

commented Jan 1, 2019

Device: Nexus 5 (hammerhead)
Channel: RC
Version: 2018-W01 (really 2019-W01)

It seems this issue is fixed but I'll keep an eye on it because it was so random when it happened that I can't be 100% sure for now

@Flohack74

This comment has been minimized.

Copy link
Member

commented Jan 1, 2019

No, 2018-01 was OK. The promote to RC was done still on 31st, but it was week 1 :)

@erik-kueng

This comment has been minimized.

Copy link

commented Jan 2, 2019

Fairphone 2
rc
2018-W01

Fix works. I could not reproduce this issue.

@NeoTheThird NeoTheThird moved this from QA to Done in OTA-7 Jan 3, 2019

@Stefano0101

This comment has been minimized.

Copy link
Author

commented Jan 3, 2019

Tested OTA-7 (rc) and the issue is gone, fixed for good on Meizu Pro 5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.