Random cellular network drops on Pro 5

[p-mitana]

The phone tends to drop the entire GSM networks from time to time. It's much less frequent the dropping the data connection, but still it does happen that sometimes I don't have the connection when everyone around does. In most cases the connecition comes back without my actions.

When network drops, I see either "Rejected" or "Unregistered" text instead of carrier name in the network indicator's menu (texts may not be exact, i see them in Polish).

If you need any logs or additional information, please tell me what should I do to gather them.

[NeoTheThird]

Where's the difference to #155 ?

[p-mitana]

155 is about mobile data connection drops - but you still can make calls for example. This one is about the whole cellular network dropping - you have no GSM signal at all and you can neither browse Internet nor call. I think these are different situations.

[NeoTheThird]

I see. Sorry about that.

[mihaelmilea]

I don't have this issue on my Pro 5.

[p-mitana]

I've found a few topics on XDA with different basebands for Pro5: https://forum.xda-developers.com/meizu-pro-5/development

I think that replacing the baseband with the other one might help, but it should be tested. I tried to swap the baseband myself, however it is not possible to just flash it via recovery on Ubuntu (i guess bacause it sits in the android LXC container).

could anyone test these basebands or guide me how to replace a baseband in my phone?

[Flohack74]

No, baseband flashing should be done from fastboot, and its a .img file. You cannot flash it from either recovery or the OS itself. Which file you have got?

[p-mitana]

@Flohack74, Take a look here: https://forum.xda-developers.com/meizu-pro-5/development/meizu-pro5-baseband-25-10-2017-t3699239

I've downloaded the .zip and tried to flash it via recovery as it is seen. I also tried to extract the zip to find out if I can swap the files manually - there is mainly a modem.bin inside and no .img files at all.

On Flyme they definitely have to flash basebands via recovery, so Ubuntu seems to be different here.

[Flohack74]

Ok I can see, they are using an embedded technique, that means we would have stuff it into our system.img - I will talk with the devs and come back to this. Problem is that we are currently not building this system.img for Meizu and BQ, so this can be quite tricky. And yes, you are right, it belongs inside the container. You can however mount the container file probably, and then replace it. But this needs some advanced skills ^^

[p-mitana]

@Flohack74 Could you tell me where to start? Maybe I can find some time sometime and try to look into it.

[Flohack74]

Ask the Halium guys, they are currently more skilled in all this porting stuff. I did not touch it for months, and cannot tell you right now what files to loop-mount, but for sure its system.img or ubuntu.img and then inside there is a folder with the lxc container to be mounted, too ;)

[p-mitana]

I'll add this information here as well, as it's probably important: I wasn't aware that there are two different versions of Pro 5, but mine is TD-LTE.

[lduboeuf]

@the-Mitu is this issue still relevant ?

[p-mitana]

Hello, actually I have no idea - my Pro 5 broke about half a year ago and I have swiched to an Android phone soon after.

pon., 17 gru 2018, 17:23: Lionel Duboeuf notifications@github.com napisał(a):

@the-Mitu https://github.com/the-Mitu is this issue still relevant ?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ubports/ubuntu-touch/issues/156#issuecomment-447905379, or mute the thread https://github.com/notifications/unsubscribe-auth/ADvP7v3WQ5fN2Oqw9_29aLG0Zv-0FNwWks5u58UbgaJpZM4OSDF9 .

[wesertrainer]

The problem still remains for the TD-LTD Version of the Pro 5.