Touchscreen seems to have died after a reboot

[francehopper]

I was playing around with some firewall settings earlier today over OpenWRT and SSH that involved several reboots of my Almond+. After one of them, the touchscreen just simply stopped responding. I know that sounds like a long shot, but that actually happened. Thankfully the web and ssh logins still work, but it was kind of nice having the touchscreen to do quick things.

Any ideas? If it matters, I do have a PIN lock on the screen.

[LGNilsson]

I don't think it has anything to do with you changing settings in the router.
Please email [suspicious]support@securifi.com[/suspicious] and we'll get it replaced as this is a hardware issue.

[coreygator]

I had a similar problem after changing a setting and had to do a hard reset to get the touchscreen working again. Thought it was a one time thing and did the same thing and got the same results. Dead touchscreen. I was trying to get my cell signal booster working.

[LGNilsson]

Can you please describe your exact steps that caused this problem?

[coreygator]

I'll have to go back and find it. I think it was just a general thread, not an Almond Plus specific thread. In addition to the port forwarding, I enabled IPSec VPN and QoS LAN. I think it was the QoS LAN that did it.

[LGNilsson]

I was playing around with some firewall settings earlier today over OpenWRT and SSH that involved several reboots of my Almond+. After one of them, the touchscreen just simply stopped responding. I know that sounds like a long shot, but that actually happened. Thankfully the web and ssh logins still work, but it was kind of nice having the touchscreen to do quick things.

Any ideas? If it matters, I do have a PIN lock on the screen.

Can you try doing a hard reset, since coreygator seemingly got his working again. I just want to make sure that this is a hardware issue and not something software related before we send you a replacement.

[coreygator]

This link is what i followed. Again i think it had to do with the QoS.

http://www.verizonwireless.com/support/information/networkextender-router-configuration.html

[Vito]

Hello everyone,

I experienced this same problem on Saturday.  I thought the router was unusable, but after unplugging it, removing the USB stick and all of the cat5 cables, and probably having it off for a few minutes...  I then plugged it back in without anything attached to it except for power, and it booted up.

So you might want to give that a try if this happens to you.  I didn't do a hard reset or anything, I just left it unplugged for a bit, and when I plugged it back in, I didn't have anything but power connected to it.

I hope that helps someone, as I'm still not sure what caused it - or even what fixed it.

-Vito

[coreygator]

Hello everyone,

I experienced this same problem on Saturday.  I thought the router was unusable, but after unplugging it, removing the USB stick and all of the cat5 cables, and probably having it off for a few minutes...  I then plugged it back in without anything attached to it except for power, and it booted up.

So you might want to give that a try if this happens to you.  I didn't do a hard reset or anything, I just left it unplugged for a bit, and when I plugged it back in, I didn't have anything but power connected to it.

I hope that helps someone, as I'm still not sure what caused it - or even what fixed it.

-Vito

I didnt unplug the cables put pulling power for a few minutes fixed mine again. Upgrade from R068 to R069 firmware did nothing.