jajrussel
Member
The title should be ( signing in on router as a guest ) I have to quit assuming that the keyboard and I are in agreement.
I don't know if this is an Android problem or a Chrome problem.
When lollipop first came out the one thing I liked about it, and at first it was the only thing I liked about it is that if my connection to the router ended the device would immediately ask if I wanted to sign in through the notification bar. I would tap the notification, a sign in page would pop up, and I could sign in.
Now before lollipop this page would be a page in my browser, and still is on my tablet that is running kit Kat. In 5.0 it is just a full page with no tabs all I can do is close it then open my browser. Until today it has worked perfectly.
Today, the notification bar asked if I wanted to sign in, I tapped it and the page that popped up said congratulations you can now open a browser. No sign in box, just congratulations.
The problem being that I was not signed in, because no page popped up that I could sign in on. Therefore no internet.
So I switched browser's, going with the native one, got the sign in page put in my password and received a log in error. At which point the router being a finicky beast refused to accept the correct password from any of my devices until I reset the router. I actually went through this routine twice with the same result both times.
The third time I went straight to an icon on the home screen that I knew would use the native browser because it came set up that way out of the box on the device. Got a sign in page, signed in and had internet.
Now to conclude the problem. I reset the router one more time, because doing so would force me to sign in and I wanted to test it. I keep getting the success page when I should be getting the sign in page. I wanted to test it because I told chrome to shut down. Assuming chrome actually shut down this would seem to indicate an Android problem. I can still access the net using the native browser, then I can switch to chrome with no problem. But everything was working fine until today. What's so special about today?
I liked it better when I got a page with a tab, because I could actually close the tab. 2nd. Closing chrome should have forced the device to go native, since it is the only other browser on the device. If I had two other browsers on the device. It should have asked me to choose. It did not. There is the possibility that chrome is also native because when I shut it down there was no option to remove it, and I didn't put it on here to begin with. Still, when I shut it down I should have been offered the other browser. I like chrome when it is working right, but I shouldn't have to use a side door to access the net.
Does anybody have any ideas?
I don't know if this is an Android problem or a Chrome problem.
When lollipop first came out the one thing I liked about it, and at first it was the only thing I liked about it is that if my connection to the router ended the device would immediately ask if I wanted to sign in through the notification bar. I would tap the notification, a sign in page would pop up, and I could sign in.
Now before lollipop this page would be a page in my browser, and still is on my tablet that is running kit Kat. In 5.0 it is just a full page with no tabs all I can do is close it then open my browser. Until today it has worked perfectly.
Today, the notification bar asked if I wanted to sign in, I tapped it and the page that popped up said congratulations you can now open a browser. No sign in box, just congratulations.
The problem being that I was not signed in, because no page popped up that I could sign in on. Therefore no internet.
So I switched browser's, going with the native one, got the sign in page put in my password and received a log in error. At which point the router being a finicky beast refused to accept the correct password from any of my devices until I reset the router. I actually went through this routine twice with the same result both times.
The third time I went straight to an icon on the home screen that I knew would use the native browser because it came set up that way out of the box on the device. Got a sign in page, signed in and had internet.
Now to conclude the problem. I reset the router one more time, because doing so would force me to sign in and I wanted to test it. I keep getting the success page when I should be getting the sign in page. I wanted to test it because I told chrome to shut down. Assuming chrome actually shut down this would seem to indicate an Android problem. I can still access the net using the native browser, then I can switch to chrome with no problem. But everything was working fine until today. What's so special about today?
I liked it better when I got a page with a tab, because I could actually close the tab. 2nd. Closing chrome should have forced the device to go native, since it is the only other browser on the device. If I had two other browsers on the device. It should have asked me to choose. It did not. There is the possibility that chrome is also native because when I shut it down there was no option to remove it, and I didn't put it on here to begin with. Still, when I shut it down I should have been offered the other browser. I like chrome when it is working right, but I shouldn't have to use a side door to access the net.
Does anybody have any ideas?
Last edited:
