Develop Bugs

Vibrate Only Mode?

Hi,
So I've had the phone for a couple days now, and I love it. But today I received the nougat update and I have one little (major) issue:
When in any of the none-silent notification modes, it's set to ringer only. I used to have it on vibrate only, mostly in priority mode with vibrate, so it wouldn't ring. How do I get this back? Putting the volume all the way down doesn't change it to vibrate anymore, and nor does tapping on the actual bell icon.
Thanks

I have the same problem. After update I accidentally turned volume up and now I can't turn it back to vibrate. My level of sound stops at 14% and I can't make it vibrate-only. Any ideas?
Sent from Oneplus 3

Put the alert slider to the top position

RedGoblinz said:
Put the alert slider to the top position
Click to expand...
Click to collapse
This doesn't solve the issue. You still can't have the phone vibrate to only priority notifications.
With the slider on the top position (with vibration enabled in the settings) the phone will vibrate for every notification. And if you want to switch to a "drop dead" mode with no notifications at all you would always need to go in the settings to change the vibration option of the silent profile.
Major step back by oneplus.

I want that exact same thing too. So:
Silent - silence all except alarm (with option to vibrate)
Do not disturb - all the current options + option to vibrate for the ones enabled and no sound
Ring - standard mode. Sound for all + option to vibrate.
It's strange that they've missed such a common feature.

The functionality is moved to slider now. Turn the slider all the way up to silent mode and press the grear icon to select the vibration option.
Easy. Love it much more now.
Sent from my ONEPLUS A3003 using Tapatalk

Such a glaring omission by OnePlus.
I have solved the problem by installing Ringer Modes. This app allows you to put a tile in your quick settings that will change ring modes, including Vibrate mode!
https://play.google.com/store/apps/details?id=com.cgollner.quicktiles

Dekz said:
Such a glaring omission by OnePlus.
I have solved the problem by installing Ringer Modes. This app allows you to put a tile in your quick settings that will change ring modes, including Vibrate mode!
https://play.google.com/store/apps/details?id=com.cgollner.quicktiles
Click to expand...
Click to collapse
That's not an omission. That's how it's meant to be in Nougat update. Now people will actually use the Alert Slider more often.
Personally, I love this implementation much more than before.
Sent from my ONEPLUS A3003 using Tapatalk

abobobilly said:
The functionality is moved to slider now. Turn the slider all the way up to silent mode and press the grear icon to select the vibration option.
Easy. Love it much more now.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
This seems to be terrible functionality to me. With my old Nexus phone all I needed to do was 1) Hold the Volume Down button and it would go into vibrate only mode. All it took was one button click. Now you are saying I need to: 1) Move the Alert Slider 2) Click the gear 3) Enable vibration 4) Exit out of settings page to continue what I was doing.
Four steps whereas before it only took one. That is a enormous step back in functionality in my mind.

fstbck6706 said:
This seems to be terrible functionality to me. With my old Nexus phone all I needed to do was 1) Hold the Volume Down button and it would go into vibrate only mode. All it took was one button click. Now you are saying I need to: 1) Move the Alert Slider 2) Click the gear 3) Enable vibration 4) Exit out of settings page to continue what I was doing.
Four steps whereas before it only took one. That is a enormous step back in functionality in my mind.
Click to expand...
Click to collapse
You only have to do it once, brother Once the slider is set to vibrate on silent mode, you only have to touch the slider. It's quicker than 'holding' the volume button.
Cheers.
Sent from my ONEPLUS A3003 using Tapatalk

Actually, you're right. I just tried that and it works. Now that I think about it I'm not sure why I originally assumed I'd need to select vibrate every single time.
Not bad at all just a little different than I'm used to.

I don't understand the functionality, can you explain again?
When i have vibration enabled in silent mode, how do i quickly enable and disable vibration? (before all I had to do was move the slider)

I think LOS roms still have the feature that you need

Always on Display goes blank - Double Tap to check phone not responding

So, while I have my phone on my desk the Always on Display will occasionally disappear leaving me with a blank screen. The only thing that gets the phone to wake is any type of alert/notification or physical push of the power button. I have Double Tap to check phone enabled, and when the AOD is active it will work, but when AOD does its little disappearing act, it wont.
Anyone else having this problem?
I know that the AOD is set to turn off when the phone is in my pocket and I determined that the sensor is in the top left part of the screen, but there is nothing blocking the sensor when AOS decides to turn off. I'm almost certain the issue is tied to that feature... unless I just have a defective phone.

EyeBeeNY said:
So, while I have my phone on my desk the Always on Display will occasionally disappear leaving me with a blank screen. The only thing that gets the phone to wake is any type of alert/notification or physical push of the power button. I have Double Tap to check phone enabled, and when the AOD is active it will work, but when AOD does its little disappearing act, it wont.
Anyone else having this problem?
I know that the AOD is set to turn off when the phone is in my pocket and I determined that the sensor is in the top left part of the screen, but there is nothing blocking the sensor when AOS decides to turn off. I'm almost certain the issue is tied to that feature... unless I just have a defective phone.
Click to expand...
Click to collapse
Have you been messing with Immersive Mode where you hide the nav/status bars?

mine does this occasionally too. not sure why. i assumed it was an unfortunate side effect of setting my phone to immersive mode.

Did you install Greenify? I experienced a similar issue with Greenify installed.

byproxy said:
mine does this occasionally too. not sure why. i assumed it was an unfortunate side effect of setting my phone to immersive mode.
Click to expand...
Click to collapse
You can fix the immersive mode causing hangups by running this command.
adb shell settings put global policy_control immersive.full=apps,-com.google.android.googlequicksearchbox
can use .full for full immersive, .navigation to hide nav bar, and .status to hide status bar

Thanks for the tips, all. I am not running any third party apps to alter anything stock on the phone. I'm not exactly sure what immersive mode is or how to activate it, but I haven't changed any settings in the phone other than your typical changes like font size, wallpapers and notification tones.
I do have an app called Calls Blacklist to block unknown and private calls, which Ive been getting a lot of lately. Perhaps that app's not playing nice with the AOD?

henderjr said:
You can fix the immersive mode causing hangups by running this command.
adb shell settings put global policy_control immersive.full=apps,-com.google.android.googlequicksearchbox
can use .full for full immersive, .navigation to hide nav bar, and .status to hide status bar
Click to expand...
Click to collapse
do i need to undo the adb command i used originally?

byproxy said:
do i need to undo the adb command i used originally?
Click to expand...
Click to collapse
No should just be able to run the command I posted above

I narrowed it down to the Call Blocker app. Just applied the November security patch and now it happens everytime the app blocks an incoming call. I haven't uninstalled the app yet, but when I do I will update the thread to confirm my theory.
Thanks to everyone for their input.

Deep Sleep Wont Wake

Anybody else having issues with the pixel screen not turning on? I get haptic feedback when I touch the screen but the screen doesn't come on. I have to hold down the power button to reboot. It only does it every now and then, I think it's the immersive mode that's causing it.

I am using double tap to lock (Nova Prime) and double tap to wake (settings > system > languages, inputs and gestures),
and once in a while, my double tap to wake (I presume during deep sleep) takes several taps to register.

I'm having the same issue too. Haven't found a solution yet.
Sent from my Pixel 2 XL using Tapatalk

Az Biker said:
I am using double tap to lock (Nova Prime) and double tap to wake (settings > system > languages, inputs and gestures), and once in a while, my double tap to wake (I presume during deep sleep) takes several taps to register.
Click to expand...
Click to collapse
mirwolf said:
I'm having the same issue too. Haven't found a solution yet.
Click to expand...
Click to collapse
I'm using Nova Prime too, but not the DTTL feature, and I'm not seeing this issue. I am using the DTTW in Settings (8.1). Have you tried toggling off DTTL in Nova for a while? Stranger things have happened.

v12xke said:
I'm using Nova Prime too, but not the DTTL feature, and I'm not seeing this issue. I am using the DTTW in Settings (8.1). Have you tried toggling off DTTL in Nova for a while? Stranger things have happened.
Click to expand...
Click to collapse
I'm not using Nova' DTTL, just DTTW in settings. Also using immersive move with system tuner. Not quite sure why i can't get it to wake when it happens. Ambient display turns off and its just a dark screen. Fingerprint reader registers because you can feel the vibration, but the display remains off. I tried flashing 8.1 again and reinstalled magisk, but the issue is still there. happens randomly.

mirwolf said:
I'm not using Nova' DTTL, just DTTW in settings. Also using immersive move with system tuner. Not quite sure why i can't get it to wake when it happens. Ambient display turns off and its just a dark screen. Fingerprint reader registers because you can feel the vibration, but the display remains off. I tried flashing 8.1 again and reinstalled magisk, but the issue is still there. happens randomly.
Click to expand...
Click to collapse
I believe there is a problem with Oreo and immersive mode. I had the same thing happen to me. Screen would go black if I pushed the power button but finger print scanner worked as you could feel the vibration. Also if you press lock again you get the screen lock sound.
Sent from my Pixel 2 XL using XDA Labs

Anyone found a solution to this issue. I'm having the same problem. Exactly as described.

Zetanator said:
Anyone found a solution to this issue. I'm having the same problem. Exactly as described.
Click to expand...
Click to collapse
Remove Magisk manager and remove Root entirely. Rooting is what caused it for me, I guess I had an older version of Magisk manager installed so I went to the official Magisk thread and downloaded and installed the latest Magisk manager app then flash the Magisk zip file via twrp and I haven't had a problem since

mackentosh said:
Remove Magisk manager and remove Root entirely. Rooting is what caused it for me, I guess I had an older version of Magisk manager installed so I went to the official Magisk thread and downloaded and installed the latest Magisk manager app then flash the Magisk zip file via twrp and I haven't had a problem since
Click to expand...
Click to collapse
Thanks I appreciate the help. I ended up going back to stock. The issue got progressively worse.

I too have this issue, I'm almost positive the phone does this when when the screen times out. If I press power button to turn it off I never have the issue. I only think that's what causes it but i think there's more to it, like having magisk and being rooted. Just assumptions. I also noticed that when this happens Android thinks the screens on, I have an app that lets me use active edge to turn on flashlight and it turns light on even though the screen isn't actually on. Even in battery settings it shows my sot being higher than it should.

I experienced the issue. I did have the immersive mode, rooted with magisk, edge sense, and was using substratum. After I installed an up to date module for edge sense in Magisk manager, I haven't seen it since. I think it's the previous outdated Magisk module that's doing it. Could be the base Magisk module as well.

Same issue here... very frustrating. I dropped $6 on this launcher primarily for just the tap to sleep / wake feature on my Pixel 2 XL and can't wake it. It's locked in a deep sleep. I'm forced to press the power button once and then it just wakes to ambient screen on double tap afterwards. THEN...double tap again to wake. Did I just waste my money? Anyone get a solution to this yet?

I just want to add that I have the same issue but I'm not rooted. Using an immersive mode app. Really hoping this isn't an issue on P.

robnhl said:
I just want to add that I have the same issue but I'm not rooted. Using an immersive mode app. Really hoping this isn't an issue on P.
Click to expand...
Click to collapse
I've solved this issue for me. I'm using Navigation Bar Hider from the Play Store to force immersive mode. I had to deselect the system UI-type apps from the NBH settings. Since I did that I haven't had any issues waking up the phone. I basically deselected all of the system apps then went back and selected things like Chrome, Calendar, etc.

Me too... With inmersive mode but only when have less of 10-15% of battery .....
Enviado desde mi Pixel 2 XL mediante Tapatalk

Any way to enable power button long-press torch, on stock 9.0?

Just got my new (refurb) 2 XL. I would like to try to go stock android on this for a while.
Is there any way to achieve the one feature I cannot live without: long-press power button for flashlight?

I don't think so. You can quickly access it via the notification shade of course. You can set a swipe down gesture on the fingerprint sensor to call the notification shade. You should also be able to turn the flashlight on with voice commands, even with the screen off.
The above are only suggestions for workarounds, but I may have missed something.

I have a sloppy way I do it on 8.1 that uses Automagic and the volume key shortcut in Accessibility Settings. Tasker probably works too.
Turn the shortcut on, select a service. I selected a launcher I don't use. Note that this toggles the accessibility features of an app, so don't use something that needs this. Click to enable it on lockscreen.
Now when you hold both volume buttons for 3 seconds, the system notifies you the service has been toggled. Finally I have a flow in Automagic that triggers when this pops up and from there toggle the flashlight. It even works when locked IF the screen is on.
I use a similar method to customize the Active Edge thing.
Locked on Verizon. Have to be creative

https://forum.xda-developers.com/android/apps-games/app-power-button-flashlight-t3839323
This is probably the best option a double tap

Torchie app
Torchie (no root) is another alternative: https://forum.xda-developers.com/an...torchie-torch-volume-buttons-anytime-t3270230

Full screen gestures and full screen apps

Hi,
I've configured my S4 to use full screen gestures instead of navigation buttons. This used to work fine.
Recently I noticed that the gestures not always work. When an app is in full screen mode, the first time I try such a gesture, the notification bar becomes visible for a short time, and usually the app responds to the gesture. When I do it again the gesture is acted upon by the system as intended.
Does anyone recognize this behaviour? Did I miss a new setting?

sciurius said:
Hi,
I've configured my S4 to use full screen gestures instead of navigation buttons. This used to work fine.
Recently I noticed that the gestures not always work. When an app is in full screen mode, the first time I try such a gesture, the notification bar becomes visible for a short time, and usually the app responds to the gesture. When I do it again the gesture is acted upon by the system as intended.
Does anyone recognize this behaviour? Did I miss a new setting?
Click to expand...
Click to collapse
I'll have to check. I know mine does this in-game, but that's expected. I'll check in other apps.

sciurius said:
Hi,
I've configured my S4 to use full screen gestures instead of navigation buttons. This used to work fine.
Recently I noticed that the gestures not always work. When an app is in full screen mode, the first time I try such a gesture, the notification bar becomes visible for a short time, and usually the app responds to the gesture. When I do it again the gesture is acted upon by the system as intended.
Does anyone recognize this behaviour? Did I miss a new setting?
Click to expand...
Click to collapse
So mine is the same way, when in a full screen app the first swipe only shows the bar, then the second swipe does the action. My guess is it's so you don't accidentally close a full screen app? Not sure. I think mine has done this since I switched to gestures.