NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Chris0404's avatar
Mar 22, 2018

Mobile hotspot LTE MR1100 won’t stay on when connected

This device will not stay on when connected to anything. It auto shuts off and the only way to get it back on is to remove and reinsert the battery. I have already swapped it out with another brand new one from ATT and the same issues are arising.

19 Replies

  • JasonN's avatar
    JasonN
    NETGEAR Employee Retired

    Hi Chris0404,

    I wanted to confirm if your MR1100 device's firmware is up-to-date with the most current firmware? If not, proceed with the update. After the update, perform a factory reset on the device and let it boot all the way up.

    Please let me know if this works. :]

     

     

    - Jason N

  • If you're using the MR1100 as a static 24/7 modem/router, you'll probably find that running on an upgraded QC 2.0 mains charger without the battery installed will cure the problem. I used this charger and took these actions to keep the temperature down. Other providers of QC chargers are available :smileywink:

    • Chris0404's avatar
      Chris0404
      Guide
      Yeah I wasn’t trying to use it as a static or stand alone 24/7 router. I couldn’t even use the device on battery power for 15 minutes without the device powering down and NOT able to turn back on. I have fiber home internet. I need a portable device. 2 of these devices didn’t solve that for me.
      • UK-based's avatar
        UK-based
        Luminary

        Chris0404: I know this isn't by any means ideal but perhaps you could try reducing the current draw to a minimum by doing things like switching off the 2.4GHz Wifi and just relying on the 5GHz, reducing the WiFi Range to Short, enabling WiFi Standby, etc. This might indicate whether or not the problem is a power or perhaps temperature issue.

  • I have the exact same issue and even replaced mine 3 times through att. Turns off and won’t turn back on until battery is pulled. Running it on the ac power only works fine even with 2.4 amp source. I have already contacted support and opened up a case 2 weeks ago. Still waiting to heard back from second level tech support. Apparently they have never heard of this issue.

    Att is aware of a “ battery drain” issue and is taking notes on it to send over to NETGEAR. I bet it’s the same issue however reps seems to be notating the issue incorrectly. It can seem like a dead battery issue because if I plug in the power cord, after it’s shuts off, A battery symbol comes up asking me to wait. It is almoat as if the battery has been dead and left that way for a while and it usually does take a few minutes to get some charge in it before it will start up. But, I know my battery is full and never will unless battery is pulled. Hope this all makes sense and helps
  • That issue sounds similar with mine. I have random shutoffs, according the crashdump, caused by fatal error in SMS service of the device. I have sent error report to Netgear and I hope they will fix it to the next patch. I have MR-1100 EUS .

     

    This is what is in crash report:

     

    Src: FatalError
    Dat: 0000011D
    Str: sys_m_smsm_mpss.c
    Fmt: APPS force stop
    00000000 00000000 00000000 00000000
    Task: AMSS0
    Time: 000FE58D
    R0: 00000000 R1: 00000000 R2: 00000000 R3: 00000000 R4: 00000000
    R5: 00000000 R6: 00000000 R7: 00000000 R8: 00000000 R9: 00000000
    R10: 00000000 R11: 00000000 R12: 00000000 R13: 00000000 R14: 00000000
    PC: 00000000
    CPSR: 00000000
    Mod: Unknown
    Ctr: ARM, IRQ en,FIQ en
    TOS
    00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000
    BOS
    App ver:NTG9X50C_12.02.07.00

    Src: FatalError
    Dat: 00000000
    Str: Recursive fault!

    Task:
    Time: 00000000
    R0: 00000000 R1: 00000000 R2: 00000000 R3: 00000000 R4: 00000000
    R5: 00000000 R6: 00000000 R7: 00000000 R8: 00000000 R9: 00000000
    R10: 00000000 R11: 00000000 R12: 00000000 R13: 00000000 R14: 00000000
    PC: 00000000
    CPSR: 00000000
    Mod: Unknown
    Ctr: ARM, IRQ en,FIQ en
    TOS
    00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000000 00000000 00000000 00000000
    BOS

    • JSchnee21's avatar
      JSchnee21
      Virtuoso

      Hi AoC,

       

      How did you capture that crashdump?  Can you get to it through an AT command?

       

      Thanks,

      Jonathan

      • AoC's avatar
        AoC
        Guide
        Hi JSchnee21
        Yep, I got it through Telnet console. Command AT!GCDUMP prints details of the last crash event.