I use tasker for many things, but what makes problems since leaving Kitkat is displaying scenes right after the phone was woken up, in special during an incoming call.
I programmed gestures to accept an incoming call and show pictures in scenes to show the user what gesture he has to make.
If the display is on and a call comes in it works perfectly; all scenes are shown as desired. If the screen is off and there's an incoming call the scenes are not shown at all. The rest of the task works. I tried to flash toast messages; even that doesn't work during an incoming call after stand-by. In kitkat it worked, not in LP nor MM.
you can somehow reproduce that by a profile like this:
on incoming call -> wait 5 secs -> flash toast: "test" or display a random scene
Running bliss Rom as you can see in my signature. Any ideas, suggestions?
What if you don't wait 5 seconds?
The earlier the less it worked on kitkat. I guess that it's a tasker bug that no-one stumbled upon so far..
Gesendet von meinem LG-D802 mit Tapatalk
Related
There seems to be an issue where my phone takes between 5-10 seconds to wake up and ring (coming from sleep). The person calling me still gets the ringing tone there end, so it looks like there is an issue with my phone/ROM
Has anyone else had issues with this and is there a way to resolve it.
Mine doesn't take that long, but it does have a delay, I watched the display light up upon a call, then the ring is real muted after a second or two, then the ring is normal volume. I haven't noticed if its connected to the custom ringtones being slower or not, I did try moving my custom ringtone folder from the SD card to the phone's memory, that didn't seem to make a difference. Still a pronounced delay. I just did the ICS OTA, but that hasn't changed the delay, GB or ICS, same result.
You aren't alone.
I like the delay
I like the 1- 2 second delay in ringing .... in a meeting or a quiet place i can quickly answer before disturbing others..
with this i don't have to go to silent mode unless absolutely necessary
This is a workaround for getting missed call notifications in addition to SMS notifications whilst using STAMINA mode.
Note this only works for anybody who hasn't upgraded their firmware yet. Upgrading apparently "fixes" this (useful) bug and you don't get notified at all any more.
The notification LEDs only appear to stay flashing in STAMINA mode if the event occurs when screen is off. This is why SMS notification works, as an incoming SMS doesn't wake the phone. Phone calls,on the other hand, cause the screen to come on, so the notification LEDs don't remain flashing after the missed call. It's the nature of the "bug" it seems.
So, missed calls have to be converted to SMS. The free app "Missed Call Messenger Lite" does this. If a call is missed it fires off an SMS. If you put your own number as the SMS destination, you send yourself an SMS which comes back shortly, time depending on how busy your network is, usually 2-5 seconds.
The problem is, if your network returns the SMS too quickly it arrives whilst the screen is still lit from the phone call. Luckily the app has a delay setting ("call log timeout" - under "Advanced Settings") which delays sending the SMS. Default is 5 secs. If you set 15 secs or longer it should work, the SMS being delayed until after the screen goes off. You need to include Missed Call Messenger in your STAMINA mode exception list,or the SMS won't get sent!.
There's one more thing you need to do. There is already an automatic entry in contacts, right at the top, called "Myself", and the bounced back SMS will be from "Me". Unfortunately you can't set the illumination for "Myself", so you have to create another contact with your own number.
You could name it "Missed Call" or similar, and if you begin it with an underscore it will end up out of the way at the bottom of the contact list. Luckily the system picks up your new contact rather than "Myself" when your own number comes in, and the LED bar flashes.
It sounds a complicated workaround but it actually works without any fuss,so you can now have phone and SMS notifications.
Just to repeat, this only works for the original firmware.
I'll be darn if I can figure out what is going on here.
4.1.2, stock except for custom kernel brick bug prevention.
I've had this rom running since it was released (this is a note international, GBT via amazon, used in the states)
Never had an issue, but I've started to notice a couple missed calls. Today, I saw what was happening.
Incoming calls, the ringer only rings for maybe 1/2 second, phone continues to "ring" but you never hear
anything! It's like it has been silenced as if you quickly pressed a button. That's how it acts without bluetooth.
If I have my bluetooth (jawbone ERA) turned on, SOMETIMES, if the screen is off, it NEVER rings, on the speakerphone
I'm using to dial my Note, I hear it ring 2 times, then go directly to voicemail. Sometimes it does that, sometimes it does
not, otherwise, the phone ringtone plays for a split second, headset continues to ring normally. Screen shows the incoming
call, but no ringtone. I haven't tweaked, installed, updated anything to cause this. Just one day it started doing it.
I'm about to do a clear reset, but it's just a PITA to set it up. Device is going on 18 months old, first issue I've really had
with it other than a bad USB port or a worn battery.
Any clues?
edit: Found the issue...I use call control as a phone number blocker. In settings, I had on for blocked calls, "remove partial ring" turned on. Once that was turned off, everything started working.
Currently, my phone will vibrate for certain notifications while I am on a phone call. I don't want any vibration to occur while I am on a phone call (although a discreet beep in the background would be good, but not essential, the main thing is no vibration while on a call).
I've looked extensively in settings and can't find any way to achieve this. Have I missed something?
Phone is unrooted and stock ROM.
I'm looking for the same thing! The vibrator is so darned loud and with phone in my ear, it's crazy!
Hi,
It turned out I had to install a 3rd-party app for messaging (Handcent) to get this feature.
Also, after investigating further it turned out that the stock Messaging app doesn't vibrate when you receive a message while on a call (that is, there is no notification at all during the call). So it must have been some other app that had vibrated in my ear. However, I installed Handcent because I still want a notification (a tone) if I receive a message while I am on a call.
Hope this helps.
Look like the bug has been fixed and will be available in "future build"
Google search: Issue 220951: 7.0 Nougat vibration during call problem
I have been using Pixel 7 for a few months now and am facing this issue since the day I have got this device. I am not sure what is causing this issue. I tried going through all the settings, developer options, custom rules, notification settings for Whatsapp but couldn't find anything.
THE ISSUE - The device works perfectly fine when I get a normal phone call, which means it rings if the phone is on ring mode when I receive a normal call. Where as for a whatsapp call (Audio/Video), even if the phone is on ring mode, it rings for a second and then immediately switches to silent mode. This means if I get a call over WhatsApp, then after that my phone will remain silent until I manually turn it back to ring mode by clicking on volume button and changing the setting. AI have to do this every single time when I get a WhatsApp call so that I don't miss out my next normal call.
I tried uninstalling the beta version, but it behaves the same way for the regular whatsapp as well. I would appreciate if anyone here could help me with this issue which has become a pain now.