Hey gang,
This has been going on a few months for me now, and can be pretty frustrating. Compounded by the fact that wi-fi in my own apt is occasionally shoddy with any device, (frequent disconnect/reconnect issue) sometimes it can be downright maddening. Thank god I have a dope case, because I have launched this ****er multiple times now as a result of the issue. Two factory resets have not solved the problem.
Every time my phone connects to or disconnects from any wi-fi source the phone freezes up completely and is unresponsive for anywhere from 5-20 seconds, pretty much immediately after the wi-fi toast message pops up (although occasionally the phone will freeze b4 toast message pops up). After it regains consciousness, the device will "catch up" with whatever inputs were made while it was frozen.
For example: Keyboard open, typing comment on reddit. Wi-fi toast message appears, phone becomes unresponsive. While unresponsive, if I tap 5, g, h, q, back button (touch key), home button (touch key); after becoming responsive again phone will swiftly type "5ghq," close keyboard (go back), then go home (home button) along with the associated haptic feedback responses occurring.
This also seems to be occuring occasionally when I receive text messages. Sometimes but not always. Though, if it happens with one txt received, I can safely assume it will continue to occur until after I restart or (maybe) put phone down for a while.
Restarting or not using phone for a while, however, has no effect on wifi issue. Wifi issue is occuring every single time, no matter what.
Its a minor inconvenience but can be quite irritating
Anyone else experiencing this or able to help? Thx.
Blob Blobbed said:
Hey gang,
This has been going on a few months for me now, and can be pretty frustrating. Compounded by the fact that wi-fi in my own apt is occasionally shoddy with any device, (frequent disconnect/reconnect issue) sometimes it can be downright maddening. Thank god I have a dope case, because I have launched this ****er multiple times now as a result of the issue. Two factory resets have not solved the problem.
Every time my phone connects to or disconnects from any wi-fi source the phone freezes up completely and is unresponsive for anywhere from 5-20 seconds, pretty much immediately after the wi-fi toast message pops up (although occasionally the phone will freeze b4 toast message pops up). After it regains consciousness, the device will "catch up" with whatever inputs were made while it was frozen.
For example: Keyboard open, typing comment on reddit. Wi-fi toast message appears, phone becomes unresponsive. While unresponsive, if I tap 5, g, h, q, back button (touch key), home button (touch key); after becoming responsive again phone will swiftly type "5ghq," close keyboard (go back), then go home (home button) along with the associated haptic feedback responses occurring.
This also seems to be occuring occasionally when I receive text messages. Sometimes but not always. Though, if it happens with one txt received, I can safely assume it will continue to occur until after I restart or (maybe) put phone down for a while.
Restarting or not using phone for a while, however, has no effect on wifi issue. Wifi issue is occuring every single time, no matter what.
Its a minor inconvenience but can be quite irritating
Anyone else experiencing this or able to help? Thx.
Click to expand...
Click to collapse
I just updated to the DO17 and I am having the same issues... I come from a long line of rooting and rom flashing. This is the first phone I have had that is so locked down that I can literally do nothing.
After this last update I am experiencing the freezes and app crashes like you. It is very frustrating. This will be the last ATT phone I ever own
i have the same problem. not sure what causes this.
Related
Hi all,
I'm having a few intermittent problems with my phone but before I start asking to have it swapped out, thought I'd check to see if they are just with my phone or if others have the same and if the latter, whether there are any workarounds. All are occasional but have happened enough times that it wasn't just a one-off glitch:
1 - using the physical keyboard when writing a text if I hold delete to get it to delete a sentence rather than pressing it repeatedly it deletes for a bit, then stops updating the display. You can keep pressing delete and it will delete characters, you can even move the cursor and delete characters from elsewhere but you need to close the keyboard and rotate the display before it updates the screen. While writing that it occurred to me I can't remember if other keypresses show up, whether holding any button pressed causes this, or whether it happens in apps other than the SMS app. Will try those later.
2 - wifi sometimes turns itself off for no reason. Not just not connecting or forgetting the password (although it occasionally does both of those too) but just disabling itself. I can pick the phone up to do something and notice no wireless icon and if I go into the communications part of settings, wireless is disabled and I need to reenable it for it to start working.
3 - the rotation sensor sometimes stops working and no screen rotations work. Sometimes restarting the phone doesn't help (but on that occasion shaking it and tapping it seemed to!) I once solved it by recalibrating the sensor (it froze a few days ago while I was using Teeter to demo the motion sensor to a friend) but it's not happened since then for me to try that again.
There are other niggles too, but those are things that I've already seen mention of - these three are things that I've not seen any other reference to but might be too minor or intermittent to be noted. Anyone else seen the same issues on another handset or is it just mine?
Cheers,
Steve.
First, Sorry for my broken english
I want all Issues of the touch pro 2 ( rhodium ) posted in this thread.
Here are as far as i know
- Touch flo 3D isnt starting sometimes
- Sometimes, volume buttons dont work ( you will be returned to home screen when you push on it )
Please add more if known, so other people with same problem, can see if its known or not.
these past few days. my phone is acting weird. The screen keep rotating as if i open the keyboard (I enable the sound when opening the keyboard. that's how i notice it)
crashes if closing apps before they have fully loaded
intermittantly rotates the screen and gets stuck on what ever its rotated to
random crashing if you try and use it with some sort of speed it just cant cope and crashes. i now am wishing i never bothered with htc anymore but i know its not them its microsoft.
But pls also mention the software you all installed.
Especially this screen rotating is fascinating.
As bug I may ad the notitifaction queue which gets corrupted with duplicates.
maybe the push internet is doing that. (Separate post)
Can't dial from Bluetooth device (car handsfree) when device is locked
Had a strange one this morning. The phone received an sms, and it made it's bleep and vibration to let me know. But then it wouldn't stop vibrating. It went on for about 30 seconds. So I powered down with long push of power button, and selecting yes. It still vibrated after shutdown. So I went to take back off to try a soft reset, and then it stopped. Powered up, and no weird things like that. So put it down to a glitch...
My main issue is that reading an SMS doesn't always mark it as read. I will have to get the keyboard out and scroll through the messages with the arrow keys to "read" the messages I have in a thread.
Hi,
I've got the latest FW and am running on DooMLoRD's kernel #8 (now on #9), min/max 256/1209MHz and everything was fine until a couple of days ago when some random Force closes started appearing, and today I experienced SIM lock skips. By that I mean that when my phone boots, it shows SIM lock screen, but after a few seconds it continues to main screen without me entering the code. This second thing started happening after I've installed WidgetLock Lockscreen.
The phone also didn't allow me to connect to my operator. It showed me a toast message Your SIM card can't connect to this operator, or something along that line.
Also, some system apps started FCing, and when I was receiving a call, I saw only the notification bar and black screen, thus could not answer. My phone usually vibrates for a few seconds, then starts ringing, and a bit after that shows the screen with who's calling and the answer/reject slide bar (this whole action is way too slow :/ ).
I went into recovery mode and restored one of the backups, then turned on my phone and everything was alright. After that I restored the newest backup from today and now everything seems to be in its place.
Any ideas what might have been the problem? The call screen delay is still there (it show up after 10 seconds of ringing + a second or two to be able to answer). Is that normal? I also noticed that with WL Locksreen enabled I have to wait SEVENTEEN seconds to be able to see the call screen and answer the call.
My wife's US Cellular version (SM-T807R4, no SIM, running wifi only), seems to regularly freeze since it received the 6.0.1 update. It will un-freeze if she closes the case cover and opens it but it's annoying. It doesn't seem to be application sensitive. As I type this she was reading the NYTimes (via the app) and looking at Facebook and it froze in each app. Any ideas/suggestions?
My Tab S seems to loose input from the display frequently. Oddly I've noticed the volume rocker works while this happens along with the power button to toggle the display. It's almost like the system is lagging at moments of activity. It is frustrating but the system doesn't crash. I have seen other posts which suggest similar but have found no solution. I had the same issue with Lollipop. I'm happy enough with the device and it seems to recover, that I keep it. Maybe it's specific to cellular models because they use a different CPU? Sometimes I toggle the display with a quick tap to the power button, not sure if it recovers more quickly.
I managed to get Debian booting on my Gemini PDA wifi version pretty easily.
Certainly there are rough edges, but it looks like it will be useful...but for one problem. I can't reliably get it to sleep and wake.
I don't mean the "Sleep" and "Hibernate" options from the "Leave" menu--I have never gotten them to work at all. I'm just trying to get the "Off" feature on the Esc key to work. Or the lid close, either would do.
Trying to reproduce the problem I have had lots of theories of what exactly it takes to make it fail, but none seem to verify. The problem is frequent but erratic.
I do have a clue. The world map screen (the one with the various sized circles) where I type my password tends to do a brightness change; it appears bright, then I think adjusts to the ambient light. In the cases where I see it fail I think it does the same thing, but instead of adjusting to a new brightness it goes black. (No, I can't successfully type my password blind.)
When this does happen, I think the computer is still running, I think I have been ssh-ed in and that was still alive.
Any others had problems with the lockscreen and found what's the problem or a workaround?
Thanks,
-kb
More Info: Network Related
More experimenting and the lockscreen seems reliable as long as wifi is on. If wifi is turned off, it is unreliable. Not 100% failure, but significant.
Suggestions welcome.
Thanks,
-kb, the Kent who wants wifi off to save power.
I can confirm this issue. And Wifi-on does not avoid it, as I had WiFi always on when this happened. Genrally Fn-ESC for screen locking works and unlocking (world map) also. But sometimes, always after longer times of inactivity, the device does not wake up at all. Screen stays black, blind-typing the password does not work, at least the screen stays black. Only solution in this case I found so far is Fn-ESC (aka "Off") until the device is powered off and reboot.
Edit:
Just happened quite shortly after a reboot, so the "always after longer period of inactivity" seems not to apply.
And the UI seems not to work/respond at all. Trying to - blindly, via keyboard - login and shutdown via systemmenu does not work too - typing pwd, Enter, Ctrl+Esc, three times cursor up, one time right, four times down and two times Enter
Partial workround
Using ssh
sudo service sddm restart
gets you to the initial login screen.
As I'm not allowed to post links: See my post on oesf.org forum, topic 35528 for further comments/notes