Related
Also, turning on the lock screen hotword detection - will this destroy my battery life, or will it be negligible?
It´s nothingfor the Batterie. You can turn it allways on.
LooksLikeSony said:
It´s nothingfor the Batterie. You can turn it allways on.
Click to expand...
Click to collapse
Erm... If our Z3 is "always listening", it cannot switch to "CPU sleep mode" as it's CPU is constantly busy with analyzing audio streams.
So there MUST be a noticeable impact on battery life.
Chefproll said:
Erm... If our Z3 is "always listening", it cannot switch to "CPU sleep mode" as its CPU is constantly busy with analyzing audio streams.
So there MUST be a noticeable impact on battery life.
Click to expand...
Click to collapse
OK Google does not work when the display is off, so it can go into deep sleep. I use it and have not noticed significant battery drain
'Always' is a little misleading. It's only listening when the screen is on and unlocked.
3Shirts said:
'Always' is a little misleading. It's only listening when the screen is on and unlocked.
Click to expand...
Click to collapse
Not quite true. It is ALWAYS listening when the screen is on. Mine works even from the lockscreen, if you change the language to English US the options are enabled in the "OK Google" detection settings.
gregbradley said:
OK Google does not work when the display is off, so it can go into deep sleep. I use it and have not noticed significant battery drain
Click to expand...
Click to collapse
Ah, I see !
Didn't have the chance of trying out myself, even after using "Ok Google everywhere" and switching the main language to English and activating the feature in the options; just did not work.
But if it doesn't work with the screen off, I don't see too much sense in it: I regard that "always listening" feature as a nice add-on if you're wearing a headset, allowing you to keep the phone in your pocket. As this does not work, I can easily live without it.
Chefproll said:
Ah, I see !
Didn't have the chance of trying out myself, even after using "Ok Google everywhere" and switching the main language to English and activating the feature in the options; just did not work.
But if it doesn't work with the screen off, I don't see too much sense in it: I regard that "always listening" feature as a nice add-on if you're wearing a headset, allowing you to keep the phone in your pocket. As this does not work, I can easily live without it.
Click to expand...
Click to collapse
But how about this, when I have it in my car attached to a Bluetooth speaker and on charge, I can leave the screen on and use OK Google from the lockscreen without having to touch the phone, hence I am not breaking any UK driving laws which basically say you cannot touch the phone to operate it, you need a full handsfree kit (Including when dialing and answering, not just speaking)
Can someone please explain to me whats meant by cdma bug? And also what wifi mac adress is? I mean how will these affect the device.. Not looking for technical info simple and short
Thank you
The CDMA thing is just if your mobile network uses CDMA, and that's just an issue where you have to set preferred network type on first boot.
The MAC address is the address that your device uses on a wifi network (a bit like an IP address). The issue is that it's randomised every time you reboot, so some router things like QOS and whitelisting won't work, but for normal use it doesn't really matter.
Hope this helps ☺
SniperShotgun said:
The CDMA thing is just if your mobile network uses CDMA, and that's just an issue where you have to set preferred network type on first boot.
The MAC address is the address that your device uses on a wifi network (a bit like an IP address). The issue is that it's randomised every time you reboot, so some router things like QOS and whitelisting won't work, but for normal use it doesn't really matter.
Hope this helps
Click to expand...
Click to collapse
THANK YOU I will give CM A try then I thought the CDMA meant no signal lol and the MAC address thing meant no wifi or would limit both the capabilities
b3ava said:
THANK YOU I will give CM A try then I thought the CDMA meant no signal lol and the MAC address thing meant no wifi or would limit both the capabilities
Click to expand...
Click to collapse
Well if you don't set the thing at first boot it is no signal, so remember
I have another thing to report:
The headphones are set to VERY high volume. Even if i turn the volume to the minimum during a call, it is still too loud.
I often have awake and screen on, but i dont actually have screen turned on. How can i see which process is doing this or fix it?
AgiZ10 said:
I have another thing to report:
The headphones are set to VERY high volume. Even if i turn the volume to the minimum during a call, it is still too loud.
I often have awake and screen on, but i dont actually have screen turned on. How can i see which process is doing this or fix it?
Click to expand...
Click to collapse
Does the "double tap to wake" set to on ?
it maybe because of that
tomhtg90 said:
Does the "double tap to wake" set to on ?
it maybe because of that
Click to expand...
Click to collapse
It is, yes. But i was most active on phone that day from 8-16, and in that time you can see that awake and screen-on just kept increasing and didnt "shut off" at all later that day even though not much was going on with the phone. If i remember i even restarted the phone (that sliver missing on the graph).
Right now i have this kind of usage, the way it is supposed to be (ok, not sure whats wrong with the signal, but lets leave that alone for now)
Could it be some app not letting the phone go to sleep or what?
AgiZ10 said:
It is, yes. But i was most active on phone that day from 8-16, and in that time you can see that awake and screen-on just kept increasing and didnt "shut off" at all later that day even though not much was going on with the phone. If i remember i even restarted the phone (that sliver missing on the graph).
Right now i have this kind of usage, the way it is supposed to be (ok, not sure whats wrong with the signal, but lets leave that alone for now)
Could it be some app not letting the phone go to sleep or what?
Click to expand...
Click to collapse
I dont know what happen. But what i saw from your 1st SS, the screen doesn't go to sleep.
U can see what apps that use much battery by simply go back from History details.
On my Battery use stat, Screen always be gonna be the biggest usage (and that's normal). If l lock the phone, the phone does go to sleep (means screen is off and not using the battery until i turn it back on).
On Cyanogen dev thread for our device, some people have bad battery life when double tap to wake is on (me too).
Maybe it's not well implemented yet. So that's why i rather choose not to use that feature for a while until it well implemented.
Ok, thanks for your thoughts. I didnt chech which app used the most power, but perhaps it was Exchange not being able to sign in. I will monitor the behavior (during weekend it should be a lot longer battery life).
Yeah, i think dt2w is not optimised. As long as i have full day of battery it should be enough and for now that is the case.
The volume bug is annoying though.
is it only me that has an issue with Notifications on this phone? It seems that when I am on wifi my internet stops or something.. is there a setting or something I have missed?
No, a lot of users are reporting this bug. I suggest you try the app "Heartbeat fixer for GSM" or "PNF Root" which could fix this. I install one or the other as soon as I get a new phone, and I don't have issues with push notifications that I've noticed so far, but I haven't tested the Mi4C on WiFi yet.
b3ava said:
is it only me that has an issue with Notifications on this phone? It seems that when I am on wifi my internet stops or something.. is there a setting or something I have missed?
Click to expand...
Click to collapse
xdadevet said:
No, a lot of users are reporting this bug. I suggest you try the app "Heartbeat fixer for GSM" or "PNF Root" which could fix this. I install one or the other as soon as I get a new phone, and I don't have issues with push notifications that I've noticed so far, but I haven't tested the Mi4C on WiFi yet.
Click to expand...
Click to collapse
Did you try from scratch?
I put on TWRP, deleted EVERYTHING (system, data, cache...) then put on CM and gapps (opengapps - ARM64 - pico) in one go and for me it works like it should.
About my awake problem: I have left the phone more or less alone during the weekend and it seems it works like expected. I will observe if i find any more strange behaviour like i did a few days ago.
Seems that it sometimes works and sometimes it doesn't the two apps that are mentioned above don't seem to be making a difference.. The funny thing is when I am not connected to WIFI the phone seems to be running fine (notification wise). But when the screen is off and I am on wifi the device seems to be going into some sort of deep sleep most of the times. I think after 2-3 days it hasn't been as bad, but I do get 1 or 2 random hangout notifications not appearing at all..
I've created an app that wakes ambient display when you take the phone out of your pocket or if you have the phone face down and turn it over. The app is in addition to Google's ambient display and does not change your lock screen in anyway. It can also set "pulses" of ambient display. The free version allows you to have it always pulse while charging.
I added a few other paid features for tilt or lift to unlock, wave to unlock, pulsing at an interval, and battery percentage display on the ambient display.
Please let me know if you have any suggestions or run into any problems. Thank you!
Check it out: https://play.google.com/store/apps/details?id=com.compass.ambiturner
Pulse means, as long as i have for exampel a unread whatsapp message, ambi is showing at the set pulse time?
Maybe ill test it on OP3 with CM14.1 running ... will report back!
MultiCulti said:
Pulse means, as long as i have for exampel a unread whatsapp message, ambi is showing at the set pulse time?
Maybe ill test it on OP3 with CM14.1 running ... will report back!
Click to expand...
Click to collapse
Correct. There is a filter for you to choose which apps can trigger a pulse. The pulse timeout is how long do you want the pulses to continue before it stops (to save battery). Pulse will temporarily pause when your phone goes into deep sleep. I could wake it up, but that's a much larger battery hit.
The other features seems to have little to now battery impact. Pulse is fine as long as the interval isn't set crazy low.
So far I've only personally tested it on stock Pixel XL.
ok, so far its working fine here!
Just the pulse isnt working (tried whatsapp and google messenger)
Love the idea off showing the battery, but its not that looking good :silly:
but i think, you just can manage this as "notification", or am i wrong?
anyways, good idea so far, will follow (bought it anyway) :laugh:
MultiCulti said:
ok, so far its working fine here!
Just the pulse isnt working (tried whatsapp and google messenger)
Love the idea off showing the battery, but its not that looking good :silly:
but i think, you just can manage this as "notification", or am i wrong?
anyways, good idea so far, will follow (bought it anyway) :laugh:
Click to expand...
Click to collapse
The battery level is a notification. I'll create a custom layout to improve the look in a future update.
The pulse is the least reliable feature. I'm still working out the kinks, but doze and deep sleep definitely are one problem. I'm testing various ways and will try to get it as consistent as possible.
Alarm Manager would work but it would drain battery.
Looks great! Just to confirm - you need to have a lock screen set up for it to work?
poczynek said:
Looks great! Just to confirm - you need to have a lock screen set up for it to work?
Click to expand...
Click to collapse
Yes, it works with androids Ambient Display. So if you have that and it's turned on it should work.
So I've done some limited testing with the app white listed from doze and so far it improves the responsiveness significantly. I don't know the battery impacts yet, but if it's not noticeable I'll add code to prompt users to white list it.
Other upcoming changes:
Advanced settings to adjust wait times for how long the phone has to be in your pocket or laying flat before a wake can occur.
A pulse option that initially pulses faster when a notification comes in, and progressively shows down until the timeout.
Possibly change in lock screen battery indicator appearance.
Filter on laying flat thresholds. I suspect the accelerometer incorrectly reports the phone tilted while it is laying flat on occasion.
New update posted.
I may have discovered what is causing the intermittent nature of wave to wake. I made some changes in how I'm using the proximity sensor so that should help. I'll have to wait and see after a day or so of use to see how consistent it is.
I also added an option to turn off the wake from pocket.
There's now a help screen with an email developer button and some troubleshooting hints. I've been getting a large number of 1 star reviews, and many of them are people who don't realize you need to have ambient display turned on and a lock screen set, so I included more info on that.
Oh, and the notification is now hidden unless you have the Battery Indicator selected!
If anyone is still having problems with tilt to wake please let me know. On my Pixel XL that has been working every time all day. There is sometimes a delay, but I think that's due to the aggressiveness of Android 7.1 putting the device into sleep.
Awesome app. I bought it mainly because of Wave To Wake, but for some reason it works two times on my Nexus 6 and then stops working until I turn my screen on and off again. Oh, and I've already whitelisted Ambi-Turner from the battery optimisation.
Also I would love if you could make Ambient Display work as soon as I turn the screen off, without having to wait for 10 or 3 seconds.
Thank you a lot for your hard work, I hope this can be fixed. Please contact me if I can help with anything!
Ygor Cortes said:
Awesome app. I bought it mainly because of Wave To Wake, but for some reason it works two times on my Nexus 6 and then stops working until I turn my screen on and off again. Oh, and I've already whitelisted Ambi-Turner from the battery optimisation.
Also I would love if you could make Ambient Display work as soon as I turn the screen off, without having to wait for 10 or 3 seconds.
Thank you a lot for your hard work, I hope this can be fixed. Please contact me if I can help with anything!
Click to expand...
Click to collapse
I'm trying to get wave to wake as consistent as possible. Did you update last night? Let me know if that helps it.
I'm actually working on some advanced settings to let you control those timeouts.
grokus said:
I'm trying to get wave to wake as consistent as possible. Did you update last night? Let me know if that helps it.
I'm actually working on some advanced settings to let you control those timeouts.
Click to expand...
Click to collapse
I'm testing it right now and it's still quite inconsistent. Though I never know if I'm waving too fast or too slow, you know? Maybe if there was a way to make it more sensitive? Thanks for the attention! ;D
Edit: just to be clear, Wave To Wake does only work two times, but I discovered that I don't actually need to turn the screen on for it to work, I can just move the device (then Ambient Display will turn on) and after that the Wave To Wake will work again (though still only two times). I believe it has something to do with the time after it's been awake or something like that.
Android Wear Issue
Ok...I love the app when its working and even bought the Pro. So worth it to me.
This morning I forgot my Android Wear watch (LG Urbane) at home and Ambi Turner was working perfectly. I had to run home at lunch, grabbed my watch, turned it on and now Ambi Turner isn't working.
Any thoughts how to get around this?
mschumacker said:
Ok...I love the app when its working and even bought the Pro. So worth it to me.
This morning I forgot my Android Wear watch (LG Urbane) at home and Ambi Turner was working perfectly. I had to run home at lunch, grabbed my watch, turned it on and now Ambi Turner isn't working.
Any thoughts how to get around this?
Click to expand...
Click to collapse
UPDATE: I turned off the 'Mute' for my watch and Ambi Turner started working again. Hmm...gotta thing this one through. Turning on Mute alerts my watch, but I also see them on Amber Display.
Ygor Cortes said:
I'm testing it right now and it's still quite inconsistent. Though I never know if I'm waving too fast or too slow, you know? Maybe if there was a way to make it more sensitive? Thanks for the attention! ;D
Edit: just to be clear, Wave To Wake does only work two times, but I discovered that I don't actually need to turn the screen on for it to work, I can just move the device (then Ambient Display will turn on) and after that the Wave To Wake will work again (though still only two times). I believe it has something to do with the time after it's been awake or something like that.
Click to expand...
Click to collapse
I'm adding some customization for the wave timeouts. I wish I could measure hand distance from phone but the pixel and nexus sensors don't have that granularity the way moto phones do.
mschumacker said:
UPDATE: I turned off the 'Mute' for my watch and Ambi Turner started working again. Hmm...gotta thing this one through. Turning on Mute alerts my watch, but I also see them on Amber Display.
Click to expand...
Click to collapse
Hmm that's strange. I'm using a garmin fitness watch that has notifications and haven't seen anything like that. Does your watch somehow mute notifications on your phone so that only the watch displays them?
grokus said:
Hmm that's strange. I'm using a garmin fitness watch that has notifications and haven't seen anything like that. Does your watch somehow mute notifications on your phone so that only the watch displays them?
Click to expand...
Click to collapse
Yes...there is a setting in Android Watch (Silence phone while wearing watch ) in the new version. It used to be 'Mute calls and notifications'. Its actually very handy so that when I'm in a meeting, I just get a vibration on my watch instead of my phone making any noise. Add the 'Feel the Wear' app where you can customize the vibration pattern per app...just a great combo.
EDIT: Since I just got a new version of Android Watch, it seems I can turn on the Silence option and the AmbiTurner, wake on wave, is working! Woo HOO!
Made tons of improvements. Tilt to wake should be extremely reliable now. There is also a lift to wake option. I reduced the speed you need to wave, so it should be much easier to trigger now. I also added an option to always pulse while charging.
Let me know how it works!
I had taken a break from updating it because I became a father but I have a little spare time now.
grokus said:
Made tons of improvements. Tilt to wake should be extremely reliable now. There is also a lift to wake option. I reduced the speed you need to wave, so it should be much easier to trigger now. I also added an option to always pulse while charging.
Let me know how it works!
I had taken a break from updating it because I became a father but I have a little spare time now.
Click to expand...
Click to collapse
@grokus is this app still being developed?
Sent from my LG-H990 using XDA Labs
Set voice retrain, set in trusted voice also can't seems to wake the device.
Ok Google can't wake the device. It only works while the phone screen is on.
Beamed in by telepathy.
mine wake up just fine when i say ok google even the screen is off..restart the phone then try again
Wakes up just fine with screen off here too. Trusted voice as I also have a lockscreen with pin.
Thanks for replying guys,let me try.btw, I am using English US as default language.
Solved: Power Saver feature did interfered with the function,off it OK Google can works as normal.
I had this issue today it was pissing me off lol. I think it was the power save feature. Don't even need the power save feature with this beast.
Power saving mode will keep "OK Goggle" from working. If its on, try turning it off.
I almost went crazy thanks for the tip
Thank you as well. My HTC U11 was plagued with the same issue today. I had fat fingered Battery Saver which was on since morning. Now I wonder whether that could be the cause for the non functioning "OK Google" on the new OnePlus 5T.
I finally picked up a U12 after Amazon had a 20% off sale on Warehouse Deals versions. It was basically new and I initially liked it. However, I'm likely returning it because the Motion launch gestures are extremely unreliable, especially when taking it out of my pocket. It seems that the proximity sensor doesn't immediately register that it's not in a pocket anymore. That, or it has to be more forcefully lifted UP, like you must do to activate the Ambient Display. I tried this with the Ambient display in both "always on" mode and "lift to check" mode. Same results. A majority of the time, I take my phone out of my pocket and go to double-tap on the screen and nothing happens. If I keep doing it, it works after a while. If I leave it lying on a table, it will pretty much always work, which is why I think it's a proximity/light sensor issue.
I have experienced this behavior before with other phones with double-tap-to-wake. In fact, LG and OnePlus seem to be the only ones that are 100% reliable for me.
Before anyone suggests it, NO, fingerprint wake-up is not an option. I interact with my lockscreen notifications almost exclusively throughout the day. I just want the screen to turn on when I tap on it twice, like it's supposed to and that's not happening. I also don't use power buttons. At all. I use my phone left-handed anyway, so that's not ideal. I'm not looking for a suggested work-around. I'm just seeing if anyone else experiences this and/or if there's something I'm missing. The phone is great otherwise, but this is a huge deal-breaker for me.