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.
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.
I have a Note 4 fully updated, fully stock, not rooted.
I have Google Now set to wake up on any screen including while asleep.
It usually works great, but occasionally it will stop responding as if it was disabled. It will do this in the sleep mode as well as after I wake it up by hand and swipe to unlock. I have yet to determine what conditions create this problem as it seems to be a randomly occurring issue.
Once Google Now decides to ignore me, it seems the only way to get it to pay attention again is to navigate to the Google Now search bar (which resides on one of my side screens) and wait for the microphone to become solid again. There were even a few instances where I had to actually press the microphone icon to get Google's attention.
Normally I would not care so much about this, but I am wanting to use this feature to help a quadriplegic who cannot physically interact with the phone. He could use it to answer calls, and all the other voice features that Google offers. But if the listening service is unstable it will not be a practical solution.
Is anyone else experiencing intermittent "listening" from Google Now even though you have all the full listening options turned on?
Like I said, it does work...just not always.
Thanks!
Hi,
I've had my M9 for a couple of weeks now, and slowly getting it to work how I want it to. One thing nagging me is this weird issue I have with waking the device from sleep.
I have tried to disable all the gesture/smart wake features (double tap the screen, etc). The issue I'm having seems to relate to the light and/or proximity sensor. It seems (and I haven't been able to find any info on this, online or on the phone) that there is a feature which will enable the device to wake up when being picked up or taken out of my pocket. This doesn't always work, but sometimes it does. When I pull my phone from my pocket, it will sometimes wake up. When I glide my finger over the front camera & light sensor, it will sometimes wake up. This is a minor annoyance, as I would like to only be able to wake my device by hitting the power button.
It gets really annoying when these 'gesture' wakes start to interfere with the power button wake. For example (and this is happening more often than not), when I pull my phone out of my pocket, the phone is off, then I hit the power button once, and the phone still doesn't wake. Hitting the power button a second time will wake the device. It seems to me that the smart waking is some how interfering with the manual waking.
Is anyone else seeing this behavior?
Any suggestions for a solution?
Thanks a lot for any help.
This is really odd considering the M9 doesn't support air gestures. Sorry, I have no solution, but is it possible you may have installed an app that may be causing this?
I would think two button push would be the normal, otherwise you could accidentally hit it once and turn the screen on. Do you have Ambient display and pocket detection all turned off ?
Gravity Screen in the play store gives you total control of all that stuff
That for the replies guys.
Clsa, there is no way to disable ambient display & pocket detect because those features do not exist on the M9 (at least... Not that I have found). That's what is bugging me.
I don't think the 2 button press is normal. I've never had to do it on previous phones.
Fernand - not sure if it is another app causing it. I think I have no extra apps installed compared to my last phone.
I just tried Gravity Screen, and it seems to just give me the ability to enable all the features I want to disable.
Any other suggestions?
[email protected] said:
That for the replies guys.
Clsa, there is no way to disable ambient display & pocket detect because those features do not exist on the M9 (at least... Not that I have found). That's what is bugging me.
I don't think the 2 button press is normal. I've never had to do it on previous phones.
Fernand - not sure if it is another app causing it. I think I have no extra apps installed compared to my last phone.
I just tried Gravity Screen, and it seems to just give me the ability to enable all the features I want to disable.
Any other suggestions?
Click to expand...
Click to collapse
Settings / Display & Gestures / Ambient display (Wake screen when device is picked up or notifications arrive)
Pocket Detection is part of some Rom Tweaks (insertcoin & viperOne if i remember right)
Hi again, that option is not available on my phone. Do you see it on your M9?
I don't have a custom ROM. Not rooted either.
[email protected] said:
Hi again, that option is not available on my phone. Do you see it on your M9?
I don't have a custom ROM. Not rooted either.
Click to expand...
Click to collapse
Yes I have it, but I'm on LeeDroid right now. He adds so much stuff i forget whats "custom" and whats stock
Got the same issue
The power button will ignore the first push while standing by for a long time. Thought it might be caused by apps like greentify?
Hi Ducati, is that a fact or is that just how you understand it? Seems strange that that would be intentional. But it definitely seems to be the case.
I do not have greenify installed either.
Do you get similar behaviour on your One?
After a bit more testing. I can confirm that there are some sort of air gestures on this device. I can wave my finger in front of the front light sensor/camera, and the device will wake.
This doesn't happen all the time, I am not always able to reproduce this. But right now, it is happening. Can anyone else reproduce this?
http://somevid.com/N1OnU8JS
I have the same issue on my M9. Glad I found this thread. Thought my power button was defective.
I can't activate any gestures by waving my hand.
I think it's happening mostly when waking from deep sleep.
I know it's an old thread, but I just installed CyanogenMod 12.1 and I guess my google-fu is rusty. I find that if I hit the power button in quick succession (double click) it turns off the phone. Anyone know how I can stop this?
By quick succession I mean multiple times within 20 seconds
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.
Hi Guys!
So I've been facing this annoying issue with the OP7T since I bought it at its launch. The screen Freezes.
So basically, if I'm reading an article on Chrome or browsing some website, the screen will become totally non responsive. Gesturing the back button, or using the Volume rocker shows no changes on the screen, unless you switch the screen off via the power button and turn it back on, after which, the positioning of the page will be where it should intentionally be, ie for example, If I'm on a website, and I used the back button/ previous button on the screen nothing changes as it freezes, but once I turn the screen on and off, its on the previous Page. Like the changes and scrolling is happening behind, but the screen has just frozen
So the changes happen in the background, but the screen Freezes. It is super annoying and has been happening since the beginning.
Any help would be appreciated! Never faced this with the OP.
Yes, I too have this issue!! The same thing happens with the Chrome and Lynket (which also uses Chrome). But I didn't get any workaround. Most times I just swipe-up for the recents and back to Chrome.
Sent from my OnePlus7T using XDA Labs
Also experiencing this in Chrome occasionally. Doesn't happen anywhere else.
This has been reported on.
https://www.androidpolice.com/2020/...ng-and-crashing-on-oneplus-phones-for-months/
Some people commented that it happens on their non OnePlus phone as well so it's possibly a Chrome issue and not our device.