Related
I have been having some issues with the torch/flashlight LED programs recently. I didn't used to have problems and prior to this when I used the HTC torch it had the same problem. When I used older versions of MIUI I didn't have this problem with flashlight apps that I had. But now with the most recent versions (since December or so I think when they added the torch button in the notification bar) I am having the problem again.
The problem when using a flashlight app (or the button in the notification bar) the light will turn on for about a second and then turn off. It will still show it off in the app or on the notification bar. If it does not do this it does one of 2 other things. It turns on and then after one second becomes brighter and then after about 1 more second turns off. On rare occasions in an app I can turn it on and it will stay on... but then when I try and turn it off there is usually a delay of a few seconds before it actually turns off. Then it is back to turning on for a second then off.
I had seen this same problem when I used the HTC Torch previously but it went away when using different ROMs and such so it makes me believe it is some kind of software problem. Seeing that the LED does seem to work and if I use the camera it seems to actually work properly with the program I am pretty sure there is nothing actually wrong with the hardware. Has anyone else seen this problem or know what could be causing it? Is there some way or some test program I could use to find what exactly is causing the problem? If someone has had this issue before... do they know how to fix it?
EDIT: I tried manually turning on the flashlight via "echo 1 > /sys/devices/platform/flashlight.0/leds/flashlight/brightness" and it turns the light on but then after about a second gets brighter then after another second turns off. When I did a "cat /sys/devices/platform/flashlight.0/leds/flashlight/brightness" it seems something changed it from the "1" which I wrote to the file to "127". Also, when I tried to "echo 0" to the file... the change did not stay. After doing the echo and then trying to cat the file it was still "127". I then tried to the torch app in the notification bar to turn it on and then off. After I turned it off via the application, I check the file and it was then set back to 0.
EDIT: I have witnessed the issue on 3 seperate Nexus One phones... surely someone else has had the same problem and possibly come up wit a solution.
you have to be careful with the flashlight apps esp with the high brightness setting. the LED is not designed to be on constantly on the nexus one and i have heard of people burning out their LED's from leaving it on too long both in normal and high brightness modes.
i have found out while using mine esp in high brightness if its left on too long it will overheat it and flicker. ever sense i seen mine do that i never use high brightness in fear of burning it out and when i use it in normal mode i try to keep its use as short as possible and i have not had it shut off on me sense. if yours is shutting off in normal mode then i'm afraid you may have already damaged it too much and that is why its turning itself off. thats my opinion anyways.
(if roms matter, i've always ran CM6 and now currently have been running CM7 nightlies and RC's
Frito11 said:
you have to be careful with the flashlight apps esp with the high brightness setting. the LED is not designed to be on constantly on the nexus one and i have heard of people burning out their LED's from leaving it on too long both in normal and high brightness modes.
i have found out while using mine esp in high brightness if its left on too long it will overheat it and flicker. ever sense i seen mine do that i never use high brightness in fear of burning it out and when i use it in normal mode i try to keep its use as short as possible and i have not had it shut off on me sense. if yours is shutting off in normal mode then i'm afraid you may have already damaged it too much and that is why its turning itself off. thats my opinion anyways.
(if roms matter, i've always ran CM6 and now currently have been running CM7 nightlies and RC's
Click to expand...
Click to collapse
Well... I would expect... if the LED was "burned out" then it shouldn't turn on at all. The simple fact that it turns on at all means the LED isn't burnt out. Also, I would suspect that to be the case if I had not witnessed it happen on a brand new Nexus One (Old one of a friends was replaced because it was stolen). Her's had to go in for repair (turns out a cable inside the phone going to the camera was loose) and I had reverted it back to an original ROM. Once it was reverted the LED didn't have problem. Another thing that indicates to me that it is a software problem is I have seen the exact same thing before on previous versions... and it went away when changing to other ROMs. Tonight I am thinking I will wipe and flash CM7 and test it with a light app and make sure... if that has the same symptom I will flash to a shipped ROM and test it. I am pretty sure it is a software issue though. I just don't know... what... is causing the problem.
EDIT: I also forgot to mention... when it was working properly... I never witnessed it overheat and flicker though I never had it on for long periods of time. One last thing, I only saw the symptoms after a flash to a new version. When it was working properly it was always working properly. When it was acting like this on a ROM it always acted like this.
UPDATE: I did flash to CM7 nightly and the torch app works perfectly as do other apps on the market. After being back on CM7 and with the advent of the theming engine for it... I think I may just end up moving back to CM for daily use. I would like to know if anyone else has run into this issue still and/or has a solution just in case I run into the same issue later. For now I think I will just chalk it up as a kernel/ROM problem... though it doesn't explain why others didn't have the same issue =/.
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.
Hey all, i recently flashed the factory image for 5.0.1 and all of a audden auto rotate stopped working. It did fall put of my picket from about 3 feet onto the ground. Nothing externally was harmed . however, i cant remember if i had issues wuth rotating the screen after flashing the factory image and before i dropped it... Im wondering if anyone else has experienced this from either a physical drop or from a bad factory image flash. Thanks...
Similar Issues
spunks3 said:
Hey all, i recently flashed the factory image for 5.0.1 and all of a audden auto rotate stopped working. It did fall put of my picket from about 3 feet onto the ground. Nothing externally was harmed . however, i cant remember if i had issues wuth rotating the screen after flashing the factory image and before i dropped it... Im wondering if anyone else has experienced this from either a physical drop or from a bad factory image flash. Thanks...
Click to expand...
Click to collapse
I am having similar issues, however, my device was not dropped nor was it flashed. The last thing I remember doing was turning the phone to landscape to watch a youtube video, then when exiting the video to select a new one it would not rotate back. I didnt think anything of it at first, but then when I couldnt rotate videos to full screen I became suspicious that there was something wrong. Checked other apps to see if they would rotate, no dice. I have checked the sensors with "Check My Android" and they are all working fine, however, the calibration is way out. I have also rest to factory settings, and the issue persists.
CJsWorld said:
I am having similar issues, however, my device was not dropped nor was it flashed. The last thing I remember doing was turning the phone to landscape to watch a youtube video, then when exiting the video to select a new one it would not rotate back. I didnt think anything of it at first, but then when I couldnt rotate videos to full screen I became suspicious that there was something wrong. Checked other apps to see if they would rotate, no dice. I have checked the sensors with "Check My Android" and they are all working fine, however, the calibration is way out. I have also rest to factory settings, and the issue persists.
Click to expand...
Click to collapse
Is the auto-rotate icon enabled, or greyed out on the quick settings pulldown ?
githyanki said:
Is the auto-rotate icon enabled, or greyed out on the quick settings pulldown ?
Click to expand...
Click to collapse
Yep, it is there, I can toggle between on and off, I can also select it in the accessibility menu too.
CJsWorld said:
I am having similar issues, however, my device was not dropped nor was it flashed. The last thing I remember doing was turning the phone to landscape to watch a youtube video, then when exiting the video to select a new one it would not rotate back. I didnt think anything of it at first, but then when I couldnt rotate videos to full screen I became suspicious that there was something wrong. Checked other apps to see if they would rotate, no dice. I have checked the sensors with "Check My Android" and they are all working fine, however, the calibration is way out. I have also rest to factory settings, and the issue persists.
Click to expand...
Click to collapse
now that you mention it, i also remember this happening after watching a youtube video... strange thing is, ive done everything - factory reset and its still an issue. im going to try and do another factory image instiall and start from scratch. ill post back
---also yes, i toggle between rotate and non-rotate and the issue is still present.
sadly after a factory image install, auto rotate is still not working
EDIT: TRIED AGAIN AND AUTO ROTATE IS WORKING... but now my cell service is not working. I'm chalking it up to a bad factory image download and trying yet again....
EDIT #2: did another factory image install and radio is working. and auto-rotate works... PHEW
spunks3 said:
now that you mention it, i also remember this happening after watching a youtube video... strange thing is, ive done everything - factory reset and its still an issue. im going to try and do another factory image instiall and start from scratch. ill post back
---also yes, i toggle between rotate and non-rotate and the issue is still present.
Click to expand...
Click to collapse
I had a conversation, with Motorola support and they seem to think the only option is repair/replace. I will be speaking to a memeber of the aftercare sales team tomorrow, ill update tomorrow.
Hey I'm having a similar issue, I bought my nexus 6 in mexico no more than a month.. Today it slipped from my pants and felt screen down.. Had a few scratches but nothing to bad.. Well I haven't noticed that after the fall my auto rotate is not working.. Camera, videos, photos etc. Nothing auto rotates, the only thing I can see in landscape is YouTube because of the option to see it on landscape.. I don't know what to do, I have re booted the phone 3 times and nothing.. I'm thinking in installing the firmware or something like that but I need some help with it.. I don't know if someone can help me this???
Having both issues.. No auto-rotate and I've lost all cellular connectivity. Wifi works fine though. The heck is going on?
Has anyone else found a resolution to this?
All of a sudden mine decided to stop rotating earlier today and even though I can toggle it in the quick settings, nothing changes. I've since rebooted a couple of times but no luck so far. I'm on 5.0.1 by the way, non rooted, straight out of the box.
Edit: I've downloaded "Accelerometer Monitor" and confirmed that the accelerometer is responsive in Y,Z axis but the X axis was flat lining. I gave it a gentle slap onto the palm of my hand and all of a sudden the X axis jumped to life. It's as if the axis was stuck or something. It's responding now, though I have still had a few strange issues, like apps going to landscape when the phone was being held in portrait.
So, wondering if anyone else is having this. It definitely seems to be software related, I just can't for the life of me figure out what installed app did this, but hoping someone has the same issue and will chime in here. At random, the top left where the menu button is in Google Play store, for example, will act like it's not taking my touch input. The same goes for where the Edge app/contacts is. I know it to be software because if I rotate the screen in Google Play, the menu button still doesn't work and it's in a different spot while rotated obviously, so not physical from what I can see/determine. I did a factory reset only a few weeks ago, after the last update (as I usually do) and it was fine then (and right after).
Chilinmichael said:
So, wondering if anyone else is having this. It definitely seems to be software related, I just can't for the life of me figure out what installed app did this, but hoping someone has the same issue and will chime in here. At random, the top left where the menu button is in Google Play store, for example, will act like it's not taking my touch input. The same goes for where the Edge app/contacts is. I know it to be software because if I rotate the screen in Google Play, the menu button still doesn't work and it's in a different spot while rotated obviously, so not physical from what I can see/determine. I did a factory reset only a few weeks ago, after the last update (as I usually do) and it was fine then (and right after).
Click to expand...
Click to collapse
Ive had similar issues on OE2 stock.. it seemed the whole top half of the screen wouldnt recognize input and this waseven after reboots and hard resets..
It wasnt til i went back to a fresh install of a custom rom where i got it back.
I havent been able to determine a culprit outside of the software in general.
Yeah, I was sure it was software because if I pull the notification bar down and slide my finger past the "dead" area on the screen, it works fine. Also, the "dead" are moves with whether you are in portrait or landscape mode. What sucks is, my Edge bar seems to not work most of the time. Wish they'd fix this, I'm very certain it's not hardware.
Update: Think I found a fix. It's been a whole day without issues. Believe it or not, change the theme you are using (I was using default, hope you were too?). I switched to the free material theme I found in the store (I like it), and have had 0 touch issues since.
*Edit, well I had 2 good days, but the issue came back. Not as frequent, it seems, but can't nail down why it happened. I did a factory reset after this update, too.
has anyone else noticed (or is there a known issue) with NFC being wonky in general on marshmallow? seems every so often it just stops working for me, and i have to cycle it off and back on in the settings to get it working - i haven't been able to pinpoint when this is happening, but it seems my bluetooth does the same thing when i reboot the phone so i'm wondering if maybe it's related to that. this is far more annoying though, because i have an automagic flow set up to turn bluetooth on when the phone boots...i can't set up a flow to do the same for NFC without being rooted, which i'm trying to avoid.
bump, this is still happening to me. i haven't upgraded to nougat yet, but just this afternoon i had to toggle NFC off and back on to use android pay (nothing happened the first time i tapped to pay, even though NFC was turned on). has anyone else seen this? it does seem to be limited to when the phone reboots...
crackers8199 said:
bump, this is still happening to me. i haven't upgraded to nougat yet, but just this afternoon i had to toggle NFC off and back on to use android pay (nothing happened the first time i tapped to pay, even though NFC was turned on). has anyone else seen this? it does seem to be limited to when the phone reboots...
Click to expand...
Click to collapse
Unless your device is faulty, i havn't seen that happen (havnt seen many posts on the forums either)
Try upgrading to the Latest OOS, it's pretty good now and NFC is working better (as in, i dont have to hold my phone as close) for android pay now.