Related
I love the phone but I've noticed that while navigating the phone the brightness flickers or pulsates somewhat. It's also noticeable when watching video. Also I've noticed when I swipe from blinkfeed to my main home screen I can tell the screen gets slightly dimmer.
It doesn't seem as pronounced when I disable auto-brightness but it still seems to happen.
Just wondering if anyone else has noticed this.
I also have but I can't consistently recreate the issue so I havent tried to get a replacement yet
Sent from my HTCONE using xda app-developers app
After messing around with the phone more it seems to me like the brightness adjusts depending on what is on the screen, like if I launch an app the brightness might change but once it does it seems consistent until I do something else. I don't know if it's trying to adjust dynamically based on what's being displayed or what.
Not really sure if it bothers me enough to do anything about it.
I had like a wave go through my screen while using the cam odd anyone notice the lines in the screen when its off ?
Sent from my HTC6435LVW using xda premium
I haven't noticed that.
I actually went to Best Buy over the weekend and exchanged my phone to see if a different one would be better about the brightness adjusting constantly. My new phone seems about the same but I think I'm kind of getting used to it, also I just don't feel bad knowing that it seems to be widespread.
I just got a nexus 6, and after installing a few apps I've noticed a faint clicking sound during phone calls.
At first I thought it's coming from the call, but later discovered it's coming from the upper half of the phone itself, and I can only hear it when putting my ear flush against the screen (can't hear anything from the back).
I (accidentally) discovered it's because I'm using a live wallpaper. No idea why, but when I changed the wallpaper the noise was gone. It can also be caused by a few other apps, though I wasn't able to find a common feature or attribute between those apps. The noise starts immediately after opening the app, and stops immediately after exiting.
If It's relevant, I'm on Chroma rom, LP 5.0.2 running franco kernel.
It doesn't actually bother me, but I'm still curious about this, as well as a bit worried the it might be an indicator for a wider issue, so I'd really like to hear your opinion.
If anyone would be willing to try the original "culprit", here it is (It's just a normal live wallpaper): https://play.google.com/store/apps/details?id=com.schulermobile.puddledrops
Thanks
dude1001 said:
I just got a nexus 6, and after installing a few apps I've noticed a faint clicking sound during phone calls.
At first I thought it's coming from the call, but later discovered it's coming from the upper half of the phone itself, and I can only hear it when putting my ear flush against the screen (can't hear anything from the back).
I (accidentally) discovered it's because I'm using a live wallpaper. No idea why, but when I changed the wallpaper the noise was gone. It can also be caused by a few other apps, though I wasn't able to find a common feature or attribute between those apps. The noise starts immediately after opening the app, and stops immediately after exiting.
If It's relevant, I'm on Chroma rom, LP 5.0.2 running franco kernel.
It doesn't actually bother me, but I'm still curious about this, as well as a bit worried the it might be an indicator for a wider issue, so I'd really like to hear your opinion.
If anyone would be willing to try the original "culprit", here it is (It's just a normal live wallpaper): https://play.google.com/store/apps/details?id=com.schulermobile.puddledrops
Thanks
Click to expand...
Click to collapse
Hi, I think you might find some more info here:
http://forum.xda-developers.com/showthread.php?t=2962949
It seems that this is a somewhat common issue.
I actually found the issue you linked to in another place. At the time it didn't seem to be relevant (I thought noise isn't from the speaker), but on second thought, this is probably it.
Thanks.
dude1001 said:
I actually found the issue you linked to in another place. At the time it didn't seem to be relevant (I thought noise isn't from the speaker), but on second thought, this is probably it.
Thanks.
Click to expand...
Click to collapse
No problem at all. I hope that a solution becomes available for this issue.
Hey folks,
Does anyone know of a way to have the watch display in ambient mode (instead of turning fully on) when you tilt it? I find that the ambient mode is plenty bright and don't need or want it to light up fully when I just want to see the time. Any thoughts or ideas?
Nope, there is no setting for that.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Der-Knuffi said:
Nope, there is no setting for that.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
Heh, I'm well aware that there isn't a stock setting for that. The tenor of my question was more along the lines of an-app(or development)-for-that..
What about turning down the screen brightness, turning off the ambient, and have tilt to wake on?
JimF777 said:
What about turning down the screen brightness, turning off the ambient, and have tilt to wake on?
Click to expand...
Click to collapse
Much thanks for replying! That's an excellent thought, though the intent is to keep the auto-brightness enabled (an indispensable feature coming from the ZW2) when I WANT the screen on, but having the wake default to ambient. I've dabbled in frankensteining Android to my needs in the past, and I think I'll get back into 'devving' to make this happen. I really feel that a viable case for tilt to wake is to simply see the time at a glance, similar to the Move gestures in Android where the screen turns on in ambient mode until the screen is touched. I'll look into it (though anyone smarter than me has my money if you make it happen first )
I definitely hear what you're saying. Coming from rooting my first droid, I have a real case of nobatterphobia (great fear of running out of battery) and therefore charging issues.
Right out of the box, I was looking to find a set up that wouldn't stress me for the day with battery life. The tilt to wake, just to see the time, was a bit clumsy. I'd tilt, and wait for it to turn on. Not long, but not natural. No ambient, tilt to wake and 10 seconds for screen on would get me looking for the "ring of power" with 30-20 percent battery at around 6pm.
I thought about how many times that thing is turning on through the day at work (I'm usually at different locations, working with arms over my head, under, on a ladder, etc). Just tried full ambient, tilt off, 10 second on, and though I have to touch for interactive, time is easily seen immediately and now it's 8:15 (last 2.5 hours was pretty heavy use) and have 40% left. That'll get me easily through the night before charging when I get up at 5:30
I think I spun off topic a bit, sorry. This is my first smart watch and haven't even thought about hacking anything since Android started providing those things I was hacking for, right out of the box.
Actually, come to think of it, this is my second smart watch. The first one, also a new ZW3, didn't have any sound. ASUS warrantied it for service and either it, or a new replacement will be on my porch tomorrow.
What the heck am I going to do with two of them?
Like the title says. When the phone is screen off but plugged in, OK Google isn't recognized. Works fine if screen is on. In my Google / Voice settings I have turned on Say Ok Google Anytime and Trusted Voice to unlock.
It worked fine on my LG G3 previously before I came to the 3T.
Any ideas?
Sent from my ONEPLUS A3000 using Tapatalk
For me also not works
This is proving to be very annoying.
I tried the Now Launcher to see if it would fix this problem (I was going to use it anyway since autorotate seems broken with stock Launcher).
Now launcher doesn't change the situation. Does anybody have a work-around? This is the first phone/os that I have had this problem with.
Help!
Sent from my ONEPLUS A3000 using Tapatalk
When i tried, it says there is locked screen (i have fingerprinted lock screen), but when i recognized and accepted, it had no reaction. Do you tried only swiped lock screen?
Tried a bunch of things. When screen is off (but charging)I haven't found any combination of settings that work. I use a fingerprint but noticed problem before setting up the fingerprint. Also have set that my voice can be trusted to unlock; also in my car the phone is unlocked as a trusted Bluetooth device.
Sent from my ONEPLUS A3000 using Tapatalk
For me sometimes it has vibration, sometimes it says that phone are locked. But still not works "ok google" on black screen
I guess what does it means. When you press unlcok button, if there is swipe or something, it unlocks device when you say "ok google"
I have the same problem..ok Google does not work when the screen is off..bt works fine when the screen is on
I've asked this question over in the OnePlus community forum on OnePlus.net. I don't think the readership there is as savvy as here though. I've already gotten some patently wrong answers. I'm still hoping someone can suggest a fix or at least work-around.
Sent from my ONEPLUS A3000 using Tapatalk
gioyocho said:
I guess what does it means. When you press unlcok button, if there is swipe or something, it unlocks device when you say "ok google"
Click to expand...
Click to collapse
I have that option checked and it still stops working for me if I haven't used my device for more than 5 minutes.
Sent from my ONEPLUS A3000 using Tapatalk
I also would like to use OK Google with the screen off.
This has been driving me a bit crazy. I can't imagine what is blocking it from working. Glad to hear it isn't just me experiencing it... At least I am not alone.
I can't imagine it is a technology gap on the phone... That would only apply to screen off / not charging cases. Microphone certainly can work with screen off... For example talking on phone the screen shuts off in proximity to the head. And it's not a power issue, since this use case includes charging.
Somewhere there must be a hidden toggle for some feature set the wrong way.
Anybody have skills to investigate?
Sent from my ONEPLUS A3000 using Tapatalk
you can't.
always listening isn't enabled on our phone (something about licensing with qualcomm).
I don't need always listening... I need listening while charging. Even phones from 5 years ago do this...
Sent from my ONEPLUS A3000 using Tapatalk
again, you can't. IT IS NOT ENABLED ON OUR PHONE.
Yes, my nexus from years ago can do it.
but no, our 3T will NOT do it.
exb0 said:
again, you can't. IT IS NOT ENABLED ON OUR PHONE.
Yes, my nexus from years ago can do it.
but no, our 3T will NOT do it.
Click to expand...
Click to collapse
This kind of makes hands-free driving and home voice actions pointless.
exb0 said:
again, you can't. IT IS NOT ENABLED ON OUR PHONE.
Yes, my nexus from years ago can do it.
but no, our 3T will NOT do it.
Click to expand...
Click to collapse
Thanks for the reply. What exactly isn't enabled... or better asked, at what level is it not enabled? The SnapDragon 821 has support for it. So, perhaps this will come in an update or a custom ROM. Or is there some other layer which needs to be developed that OP currently hasn't?
It's beyond shocking that a major feature ... voice response while driving ... would be crippled in a recent model phone. And, I am ignorant of what exactly needs to work. The microphone works fine when the screen is off, and I have no concerns about battery performance when plugged in and charging, so an app should be able to be told to listen to the microphone under these circumstances.
Any further info about what's missing would be greatly appreciated!
It worked for a short time for me. I could say, "ok google" with the screen off, but I'm guessing the app updated or a rom changed one little thing and now it's a pain in the ass.
Sent from my ONEPLUS 3T using Tapatalk
cbwhat said:
This kind of makes hands-free driving and home voice actions pointless.
Click to expand...
Click to collapse
Uhh, yeah. That's why you keep the screen on.
Frankenscript said:
Thanks for the reply. What exactly isn't enabled... or better asked, at what level is it not enabled? The SnapDragon 821 has support for it. So, perhaps this will come in an update or a custom ROM. Or is there some other layer which needs to be developed that OP currently hasn't?
It's beyond shocking that a major feature ... voice response while driving ... would be crippled in a recent model phone. And, I am ignorant of what exactly needs to work. The microphone works fine when the screen is off, and I have no concerns about battery performance when plugged in and charging, so an app should be able to be told to listen to the microphone under these circumstances.
Any further info about what's missing would be greatly appreciated!
Click to expand...
Click to collapse
Yes, the 821 has support for always listening. However, the phone company (OnePlus) has to pay the SOC company (qualcomm) in order to use always listening (more on always listening later). Is it possible for a developer to somehow enable it? Yes. As seen with the Ok Snapdragon concept with the nexus 4, we can indeed enable it. However due to legal issues, that mod was never released.
Another reason is marketing. Motorola was able to promote their Moto X Pure so much because it had their custom "Ok Google" thingiemajig. If every phone had always listening, why buy a nexus / pixel / moto?
If you want the phone to listen and respond to your voice actions while the screen is off, regardless of whether or not it's plugged in, you need always listening. Unless you're in a call, of course.
I've heard that PA and/or CM managed to make a hackaround this for other OP phones, but I cannot confirm that it actually exists as I have never looked into it.
Great explanation. Thank you
Sent from my ONEPLUS A3000 using Tapatalk
"Approach for Moto Display" doesn't work for me, I know that this device have this feature but doesn't work for me =\, I was wondering if anyone else who has this device also has this problem and has been able to solve
Sorry for my bad English
It works for me, there are two situations where the display activates.
1. I reach for the device, or rather have may hand 3-5 cm above the display.
2. The device is laying on the flat surface, and is picked up.
Does neither of these scenario work for you?
Sent from my moto g(6) plus using Tapatalk
Same problem here XT-1926-6
rufy93 said:
It works for me, there are two situations where the display activates.
1. I reach for the device, or rather have may hand 3-5 cm above the display.
2. The device is laying on the flat surface, and is picked up.
Does neither of these scenario work for you?
Click to expand...
Click to collapse
It doesn't work for me, just when I get the device the Moto Display turns on