Jump to content

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Download files attached to the forum.
  • Customize your experience here
  • Share your CyanogenMod experience!
Guest Message by DevFuse
 

Mobile Network Unavailable After Locking Screen


  • Please log in to reply
18 replies to this topic

#1 alperrios

alperrios
  • Members
  • 7 posts
  • Country:
    tr - Turkey
  • Device Model:
    i9505
  • CM Version:
    10.2
  • Recovery Image:
    ClockworkMod

Posted 17 September 2014 - 07:34 AM

Hi,

I am running CM 11-20140916-SNAPSHOT-M10-jflte on my i9505. When I lock screen and then unlock it I see that mobile network is unavailable. But it is not about the network, network is fine. Then if I switch between network modes (2G/3G) it comes back. And when I lock the screen, again it becomes unavailable and I can not get any calls/messages and data is gone aswell.

Any ideas?

Edited by alperrios, 17 September 2014 - 07:35 AM.


#2 AleGhi

AleGhi
  • Members
  • 1 posts
  • Country:
    it - Italy
  • Device Model:
    GT-I9505
  • CM Version:
    11
  • Recovery Image:
    ClockworkMod

Posted 17 September 2014 - 08:04 AM

Hi,
I've the same bug from 13th Aug nightly, for this problem I was flashed the M9.
Yesterday, with update to M10 I've already this bug.

I recorded a video for helping developers!
youtu be/mrR-5Tjap7Y

#3 alperrios

alperrios
  • Members
  • 7 posts
  • Country:
    tr - Turkey
  • Device Model:
    i9505
  • CM Version:
    10.2
  • Recovery Image:
    ClockworkMod

Posted 17 September 2014 - 08:22 AM

View PostAleGhi, on 17 September 2014 - 08:04 AM, said:

Hi,
I've the same bug from 13th Aug nightly, for this problem I was flashed the M9.
Yesterday, with update to M10 I've already this bug.

I recorded a video for helping developers!
youtu be/mrR-5Tjap7Y

Yeah, same here. When I go back to M9 it's fixed.

#4 Fifoxtasy

Fifoxtasy
  • Members
  • 26 posts
  • Country:
    at - Austria
  • Device Model:
    jfltexx
  • CM Version:
    11
  • Recovery Image:
    ClockworkMod

Posted 17 September 2014 - 02:51 PM

This problem affects me as well. This should be a showstopper for a M-release

#5 DonLimo

DonLimo
  • Members
  • 49 posts
  • Country:
    it - Italy
  • Device Model:
    S4 GT-I9505 jfltexx
  • CM Version:
    11-Snapshot-M11
  • Recovery Image:
    ClockworkMod

Posted 17 September 2014 - 04:57 PM

I have same issue on the M10. Back to M9 and waiting news.

#6 Go4a

Go4a
  • Members
  • 2 posts
  • Country:
    il - Israel
  • Device Model:
    Samsung Galaxy S4 (I9505)
  • CM Version:
    CM11 M9
  • Recovery Image:
    ClockworkMod

Posted 17 September 2014 - 10:08 PM

I have the same problem on M10. Came back to M9 until it fixed...

#7 Sulx

Sulx
  • Members
  • 1 posts
  • Country:
    fi - Finland
  • Device Model:
    GT-i9505
  • CM Version:
    11
  • Recovery Image:
    TWRP

Posted 18 September 2014 - 09:35 AM

It seems that you set to 2G only it works but if network is 3G or higher issue occurs...

#8 mikkellund

mikkellund
  • Members
  • 4 posts
  • Country:
    dk - Denmark
  • Device Model:
    Samsung Galaxy S 4 I9505
  • CM Version:
    M10
  • Recovery Image:
    ClockworkMod

Posted 23 September 2014 - 08:27 AM

View PostDonLimo, on 17 September 2014 - 04:57 PM, said:

I have same issue on the M10. Back to M9 and waiting news.

Same for me

#9 smchadwell

smchadwell
  • Members
  • 12 posts
  • Country:
    us - United States
  • Device Model:
    Galaxy S4
  • CM Version:
    11
  • Recovery Image:
    ClockworkMod

Posted 24 September 2014 - 12:26 AM

Me, too. I'm going to run it in 2G -- that definitely is working -- for a few days and see if anything else crops up.

#10 abedecain

abedecain
  • Members
  • 5 posts
  • Twitter:abedecain
  • Country:
    uk - United Kingdom
  • Device Model:
    Galaxy I9505 and I9220
  • CM Version:
    11.0
  • Recovery Image:
    ClockworkMod

Posted 26 September 2014 - 01:24 AM

The bug is reported here, upvote it and follow it for updates: https://jira.cyanoge...rowse/CYAN-5379

#11 abedecain

abedecain
  • Members
  • 5 posts
  • Twitter:abedecain
  • Country:
    uk - United Kingdom
  • Device Model:
    Galaxy I9505 and I9220
  • CM Version:
    11.0
  • Recovery Image:
    ClockworkMod

Posted 26 September 2014 - 01:49 AM

There is a fix,

Follow the guide here: http://forum.xda-dev...&postcount=2549

You can download a baseband update here: http://forum.xda-dev...d.php?t=2192025, XXUGNG2 worked for me

#12 DonLimo

DonLimo
  • Members
  • 49 posts
  • Country:
    it - Italy
  • Device Model:
    S4 GT-I9505 jfltexx
  • CM Version:
    11-Snapshot-M11
  • Recovery Image:
    ClockworkMod

Posted 09 October 2014 - 08:22 PM

This bug is still alive in CM11 M11... I also did a clean install with factory reset. Back once again to M9. I'm gonna try update the baseband too

Edited by DonLimo, 09 October 2014 - 08:45 PM.


#13 LeszekCz

LeszekCz
  • Members
  • 4 posts
  • Country:
    pl - Poland
  • Location:
    silesia
  • Device Model:
    Samsung Galaxy S4 - I9505
  • CM Version:
    CM11 M9
  • Recovery Image:
    ClockworkMod

Posted 10 October 2014 - 06:48 AM

I can also confirm that bug is still active in latest snapshot :(

Could you please advise if changing the baseband really helps?

#14 DonLimo

DonLimo
  • Members
  • 49 posts
  • Country:
    it - Italy
  • Device Model:
    S4 GT-I9505 jfltexx
  • CM Version:
    11-Snapshot-M11
  • Recovery Image:
    ClockworkMod

Posted 10 October 2014 - 05:07 PM

View PostLeszekCz, on 10 October 2014 - 06:48 AM, said:

I can also confirm that bug is still active in latest snapshot :(

Could you please advise if changing the baseband really helps?

I tested my phone all day, all working very well. I updated baseband to XXUGNG2 version as abedecain suggested.
I found another problem, but I think is related to M11. When I'll can reproduce the issue I'll open another thread.

Edited by DonLimo, 10 October 2014 - 05:07 PM.


#15 Fifoxtasy

Fifoxtasy
  • Members
  • 26 posts
  • Country:
    at - Austria
  • Device Model:
    jfltexx
  • CM Version:
    11
  • Recovery Image:
    ClockworkMod

Posted 12 October 2014 - 12:33 AM

I upgraded my modem and bootloader as well and now M11 works fine. I used the latest version from the official update for my country / carrier, in my case XXUGNH7. You can download the packages here.
For flashing I used heimdall. By the way the graphical frontend did not work for me, flashing via commandline worked fine.
On linux copy all the necessary files into the working directory and execute this command
sudo heimdall flash --MDM modem.bin --ABOOT aboot.mbn --SBL1 sbl1.mbn --SBL2 sbl2.mbn --SBL3 sbl3.mbn --RPM rpm.mbn --TZ tz.mbn --APNHLOS NON-HLOS.bin --no-reboot


#16 DonLimo

DonLimo
  • Members
  • 49 posts
  • Country:
    it - Italy
  • Device Model:
    S4 GT-I9505 jfltexx
  • CM Version:
    11-Snapshot-M11
  • Recovery Image:
    ClockworkMod

Posted 12 October 2014 - 07:30 AM

@Fifoxtasy
Network operator scan (Settings -> Mobile networks -> Network operators) works for you? I noticed you flashed WiFi FIX too.

#17 Fifoxtasy

Fifoxtasy
  • Members
  • 26 posts
  • Country:
    at - Austria
  • Device Model:
    jfltexx
  • CM Version:
    11
  • Recovery Image:
    ClockworkMod

Posted 13 October 2014 - 03:31 PM

@DonLimo
actually it doesn't work, after searching i don't get a single result. i didn't even notice because it connected to my home network without a problem.
do you know anything about this?

#18 DonLimo

DonLimo
  • Members
  • 49 posts
  • Country:
    it - Italy
  • Device Model:
    S4 GT-I9505 jfltexx
  • CM Version:
    11-Snapshot-M11
  • Recovery Image:
    ClockworkMod

Posted 13 October 2014 - 07:37 PM

@Fifoxtasy
I just know what I read in the bug's page on Jira and thread on xdadevelopers. It's called WiFi fix but it has nothing to do with "home's wifi". It concern network operator scan function. Wireless connections works properly for what I can say.
I flashed last but one modem version because the latest is known to not work (with network operator scan), at least in my country, but I have the same problem.
Someone that I don't remember the name said that is can be another bug of CM 11 and should be reported, maybe he just did.
Anyway should not be a problem if you don't use roaming in other countries (I think).
I will follow the issue and in case I will update modem version again.

#19 Fifoxtasy

Fifoxtasy
  • Members
  • 26 posts
  • Country:
    at - Austria
  • Device Model:
    jfltexx
  • CM Version:
    11
  • Recovery Image:
    ClockworkMod

Posted 14 October 2014 - 06:17 PM

non-hlos apparently is the LTE modem. details about it, which one to get and why it is called wifi fix here.