Support Wi-fi GuiException login message

Discussion in 'Android Devices' started by Groid, May 2, 2013.

  1. Groid

    Groid Well-Known Member
    53

    Dec 1, 2009
    358
    88
    53
    Anyone seeing this message?

    Guiexception detected: Abnormal situation Code wifi_login_screen_required/ null

    It started after the 4.1.2 update, a factory data reset, and the Ubuntu exploit to get root back. It doesn't seem to cause a problem, but is annoying. I've tried various combinations of the wi-fi options to eliminate the message, but still get it daily.
     

    Advertisement
  2. wyzird

    wyzird Well-Known Member
    46

    Jan 21, 2010
    106
    5
    46
    Auto Repair Office Manager, Retail Shop Owner, Wed
    Ohio
    I am getting the same message. I did a FDR after I updated to JB. I was thinking about doing another reset, but now I'm not sure if it will help.(Really dont want to). I will wait and see if anyone has an answer to this problem.
     
  3. wyzird

    wyzird Well-Known Member
    46

    Jan 21, 2010
    106
    5
    46
    Auto Repair Office Manager, Retail Shop Owner, Wed
    Ohio
    I just realized that this is under "All Things Root" . I am not rooted.
     
  4. OutOfPhase

    OutOfPhase Premium Member
    523

    Dec 7, 2010
    4,023
    2,122
    523
    Retired Lineman
    Tampa, FL
    Moved it for you.
     
  5. rdsok

    rdsok Well-Known Member
    53

    Feb 24, 2010
    235
    59
    53
    The original poster is Groid and not wiyzird... Groid IS Rooted though didn't seem to think that having root caused the issue.
     
  6. Thom

    Thom •••
    Guide
    6,143

    Feb 16, 2011
    11,183
    4,557
    6,143
    Male
    Software Developer
    Keene, NH USA
    Since it was root-ed it opened the doors to many issues that are otherwise closed.

    You really have to think of it as two separate devices "bionic" and "rooted bionic". They may exhibit the same error behavior and the cause may (or may not) be entirely different.

    ... Thom
     
  7. rdsok

    rdsok Well-Known Member
    53

    Feb 24, 2010
    235
    59
    53
    I agree but for other reasons... even two devices setup the same... I don't assume the cause of the original poster's issue to always be caused by the same cause even when it may very well be...

    Said another way... The thread is about finding the cause of the issue that the OP stated and other posts should only be made to either support of or help fix the OP's issue. Another person experiencing the same error can be of use in saying what they've tried to fix their own problem... but the thread should be about helping the OP and not the other person since there may be more than one possible cause of an error.

    So my last post was just to point out that there are two people posting about having the error... I suspect that OutOfPhase hadn't noticed that and had moved the post based on the second persons post and not the OP's.
     
  8. Groid

    Groid Well-Known Member
    53

    Dec 1, 2009
    358
    88
    53
    Regardless of which thread we're in, I think I fixed the issue. After clearing cache in stock recovery and cleaning up the Dalvik cache in Titanium Backup (root), I haven't gotten the message again. Since it has happened to people rooted or not, I don't think root has anything to do with it. With all respect to Thom, I don't think simply rooting makes it really a different device.
     
    wyzird likes this.
  9. Thom

    Thom •••
    Guide
    6,143

    Feb 16, 2011
    11,183
    4,557
    6,143
    Male
    Software Developer
    Keene, NH USA
    Thanks for the information ... so clearing the cache might be a good step for him to try on his un-root-ed Bionic taht will not disrupt anything.

    ... Thom
     
    Groid likes this.
  10. jwest06

    jwest06 Member
    16

    Sep 13, 2011
    18
    7
    16
    Constultant
    Atlanta
    Non-rooted. Cleared cache 2 days ago and haven't seen this since. Seems to have cleared it up.
     
    Duckster, Groid, wyzird and 1 other person like this.
  11. wyzird

    wyzird Well-Known Member
    46

    Jan 21, 2010
    106
    5
    46
    Auto Repair Office Manager, Retail Shop Owner, Wed
    Ohio
    I cleared the cache and no more message! Thank You!!!
     
  12. biker128pedal

    biker128pedal Well-Known Member
    16

    Aug 11, 2011
    86
    3
    16
    Engineer
    Eastern VA
    I get the message. My Bionic is not rooted and I did not do a FDR when I updated to JB. Isis FDR for ICS. Not to see how to clear the Cache.
     
  13. Thom

    Thom •••
    Guide
    6,143

    Feb 16, 2011
    11,183
    4,557
    6,143
    Male
    Software Developer
    Keene, NH USA
    See ... Clear Bionic Cache ... for instructions on how to do it.

    I think there is a very high probability that almost everyone will also for a Factory Data Reset after updating to Jelly Bean.

    ... Thom
     
  14. Joshua999

    Joshua999 New Member
    5

    Jan 20, 2014
    2
    0
    5
    I would not recommend nor clearing deleting or whatever whom ever tells you before you actually know what that error means to you. It is a very important error/meaning. It is letting you know that the wifi network your on has an abnormal gui. Hence code wifi login/null. So what then does warning abnormal guest user id on wifi login code wifi/null which null means no value or validity. So string it together. Your network is not safe someone has bypassed your wireless and is now roaming your phone as you do. Chances are not for your nudes either.
     
  15. Joshua999

    Joshua999 New Member
    5

    Jan 20, 2014
    2
    0
    5
    As well it is not entirely noted a security breach. If you are using a laptop/home computer to view such things as a site that has new feeds updates or notifications, and your mobile device is also on that site. You will achieve the error the same way. E.I Google+ Facebook.
     

Share This Page

Loading...