A new problem appeared on my NexusOne FRF91 - when using N1 as a WiFi hotspot for a while my display gets sometime frozen - I can switch phone on via a button, I can see a display but display doesn't react on any touch. I haven't noticed anything like this on FRF83 or FRF50. Anybody else with similar experience? Any idea about workaround, pls?
Thanks, Pavel
Sent from my Nexus One using XDA App
Related
For some reason my nook running CM7 stable off of sdcard becomes unresponsive for what seems no reason. It still functions just fine I see the background moving and still receive email but all buttons and touch screen stop working.
Has anyone else experienced this or know of a fix or anything I can do?
Sent from my Nexus S 4G using Tapatalk
Its called SoD. (Sleep of death) Common problem. Do a search and you will find many fixes. I use tasker to turn wifi on/off when screen is on/off.
---------------------------------
Sent from my LG Optimus V using Tapatalk
I thought SOD was when the device wont wake up. Mine seems to "freeze" while i'm using it but everything continues to function just no button or touchscreen response.
Are you overclocked/undervolted? What are your settings?
Sent from my NookColor using Tapatalk
Its just straight up CM7 have not changed anything.
Sent from my Nexus S 4G using Tapatalk
Well I'm running cm9 0.5 and I got six axis to work and it connects yet none of the controls work and I got profiles from the right place the only buttons that work are the anolog and the up and down left and right buttons anyway to fix this?
Anyone Know???/
I had the same problem would love to know.
Sent from my cm_tenderloin using xda premium
Assuming you're talking about touch profiles, the first thing to check is whether any touches are being sent by the app. The best way to do this is to download 'Touch Test' or similar from the market, connect the controller and activate the touch profile, then run 'Touch Test' and press some buttons on the controller. If any output shows up, it's likely that the profile you're using has been configured for a different control scheme or a device with a different resolution. If no output shows up let me know and I'll see if I can come up with some more possibilities!
^Do what this blessed man says. He is the developer!
Just came in from work I'm going to give this a shot in a few minutes. Will post the results. Thanks for the help.
Sent from my cm_tenderloin using xda premium
Hey, i got an even worse problem.. once i use any button on my sixaxis whilst using the active touch profile my phone stops recognizing any touch input and i have to reboot it in order to use it..
currently running cm9 on sgs2
Tried out the touch test and its working. Thanks a lot bro!
Sent from my cm_tenderloin using xda premium
i got some news to add:
i enabled the touch indicator of the android system and whenever i touched a button or moved a stick, the sixaxis app seamed to permanently simulate a touch on the screen. that must be the reason for the touchscreen freeze. on the newest cm9 (02012012) i managed to unfreeze it by multitouching around that permanent dot.
if anyone has a solution, plz let me know.
though its not that bad for me since i just wanted to test the active touch profile, bc im getting my transformer prime soon (and afaik there are no issues with sixaxis) i think this occurs on many ppl using cm9 on sgs2, asking for help!
Anyone else experiencing device freezes that require a battery pull to resolve while using Google Navigation? Screen mostly goes to black with part of the top status bar still visible - like the blue background in windows when you close a program but the comp just hasn't caught up.
I wouldn't say it happens often but it does happen enough. Anyone else seeing this?
jeff_roey said:
Anyone else experiencing device freezes that require a battery pull to resolve while using Google Navigation? Screen mostly goes to black with part of the top status bar still visible - like the blue background in windows when you close a program but the comp just hasn't caught up.
I wouldn't say it happens often but it does happen enough. Anyone else seeing this?
Click to expand...
Click to collapse
Thinking maybe an app issue. Try wiping app data. If that doesn't do it under clock when using nav if you oced
Sent from my Transformer Prime TF201 using xda premium
Never occurred to me to wipe data. I'll give it a try. Thanks. Not oc'd.
Sent from my VS910 4G using XDA App
Has happened on mine too, think problem is that nav app is a beta release, blame google for this. Try turning of screen rotation this is what fixed my force close issues.
OK say I have paired it with a Sony Xperia Z1 compact.
As soon as the screen turns off it loses connection with the phone. It still thinks it's connected (there is no cloud with a line through it on the watch face screen) and when you say ok google it tries to interpret but then I get the screen that says
disconnected and to the right is a little icon of a cloud with a line through it and underneath there are options for built-in functions like "show my steps", show me my heart rate" , etc
If I manually disconnect and reconnect using the Android Wear app on the phone it works again straight away.
Anyone else seeing this behaviour?
I had that problem right at the start. Can't remember how I fixed it
Restart both devices? Uninstall and reinstall wear app on phone? Update to latest watch firmware?
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
skitty said:
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey that could be it. I do have stamina enabled because the battery in my phone is going down rapidly with the watch connected. I'll turn stamina off and see what happens. Cheers!
EDIT: I think this might be fixed now after turning off stamina mode. I'll need to test furtehr thugh. Thanks skitty
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
shadeofgrey said:
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
Click to expand...
Click to collapse
I'm pretty sure, for me, the answer was to disable stamina mode on my xperia phone. I very very rarely see the disconnected message any more.
Cycling BT also used to help for me but all that was doing was temporarily foxing the stamina setting. It always switched itself off again.
I'm having the same issues, here's my post in the general android wear help forum
"So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?"
I have also tried running stock faces vs custom with no change
hasn't happened since 9:00 this morning.. today... yesterday I missed almost every notification
disconnect
Not sure if this is related or if anyone can give advice but for me (HTC one max) whenever my Samsung gear live is disconnected from phone...phone randomly restarts all by itself. Tried factory reset, was fine until I set it up again. Made sure android wear was off...just tried turning off Google now see if that helps.... Anyone else experiencing the restarts? Sorry on phone so messy post...
Woah sorry i forgot about this post. My issue was the stock kernal for cm11. When i switched to another kernal, my issue vanished.
I am having the issue where if my phone is asleep I cant do any searches. Now I know or at least I'm pretty sure that its not the watch or the app but something on the phone. Phone is a galaxy note 3 sprint version running temasek's unofficial cm12 rom. The watch is stock of course. When I get a notification the watch will happily wake up and tell me about it, but when I try to tell the watch a command with the phone sleeping is where the problem presents itself. The issue appeared after a few of the rom updates (happens even with a clean install) and I know he's a busy guy (temasek) but I would like to see if anyone here could help me figure it out to be able to provide a solution to others that are having my same issue. Any and all help is appreciated.
I updated to the first ota of kitkat when it went live and really didn't like it, so I downgraded to the first firmware, then accepted ota til I was back to 3.05.651.6, and now my Wi-Fi won't stay turned off no matter what settings I have chosen, and it won't respond to BatteryGuru like it used to before the whole mess.
Anyone have any ideas as to what may be causing it or how to fix it?
Sent from my HTC One using XDA Premium 4 mobile app.