I tried asking this in the big question thread, but since no one reads that one I'll ask it here.
When I recive text messages the vibrator goes of and stays on for like 10 sec. That is fine for phone calls, but om SMS I'd like a short burst instead.
I see no reson to waste battery time having the phone vibrate for so long.
In the setting I only find the option to enable or disable the vibrator.
I have also looked for some 3rd party software, but I have only found software where I can make the phone vibrate when touching the touch screen.
Same
I have the same issue. It was not a problem in Windows 6.1, so I'm guessing it's just something we have to deal with for now? From what I remember, the extended vibrate is only when the screen is locked... and currently it seems that the new Windows lock has been giving a lot of problems.
Is this the case for you?
any suggestions? ive already turned vibrate off on the keyboard and that fixed alot of the issues with the phone.
I know it's not a standard option. Whether or not it can be achieved with root access, maybe someone else can answer.
seems to have been added with the 156 update.... if you find out please let us all know. maybe with the kernel out it can be addressed
Ive been wondering the same thing.
im amazed that this isnt an option already. that vibrate function slows the phone phone down bad!
I was going to get rid of my phone for this reason and the keypad choppiness
This would be so big if someone can come up with a way to disable this...
i dont think you can without modifying the dialer
boosted125 said:
i dont think you can without modifying the dialer
Click to expand...
Click to collapse
That doesn't turn of the vibrate for the initial time you open up the phone and dial a number.
Ok, this is probably going to be a complete noob type solution, but it's got me stumped.
My screen locks during calls. Can still see all the buttons (End, Keypad, Speaker etc) but they are all disabled. Not a huge problem on a normal call as I can use the hard button to end the call but makes it impossible to use voicemail etc which need the keypad.
I'm using S2U2 along with NRG CHT ROM but nothing else I can think of which may be affecting the screen.
Been right through the settings in S2U2 but the best I could manage was switching the "Lock On Talk" to "BT Only" which made it work for one call and I was able to use my voicemail but then tried again and it's all locked up again.
Anyone else had this or know what might be causing it.
Hi there, not to sure what could be causing that... I had the same problem months ago, a Hard Reset sorted out the problem. Think it was something i installed, not sure what
I have a Samsung Galaxy S2. It recently was warrantied with an identical unit -- the previous one was rooted and ROMed; this one is stock ICS.
Like most android phones, when any form of screen lock is enabled, my phone presents an "Emergency Call" option there on the lock screen. I realize this is present by law, bla bla bla..... I also have read through around 2-dozen threads on the subject... This is apparently a hot topic, please excuse this addition to the discussion.
While I have never butt-dialed 911, I have a very tenacious toddler who had developed the super power of finding my hidden phone (regardless of where it is), who then proceeds to fiddle with it until 911 is called. This has now happened on several occasions. I am unable to find any way to disable the call 911 feature when the phone is locked. Reading today, it was suggested that ~20% of all 911 calls in US and Canada are accidentally dialed from the "Emergency Call" button from the locked screen.
It would seem my only options are to leave my phone unlocked, allowing my kids to screw everything up, or lock the phone, allowing my toddler to place emergency calls.
Today a third option occurred to me. If there was an app that provided a Second Lock Screen, I could leave my phone 'unlocked', never revealing the dreaded Emergency Call button. The phone could be configured to have NO LOCK, or just SWIPE, but then the second lock screen would pop up, offering the standard security options, but with no possibility of placing an emergency call. I would hope for an option that required either no extra actions/swipes, or only one to access the locked phone.
This would be different from the plethora of app locks that are readily available -- I do NOT want to have to unlock individual apps.
Is anyone familiar with an app that would provide this functionality, or of another work-around that would allow me to secure my phone without the 911 hassles? If I need to place an emergency call, I would simply dial it manually, and if there is no SIM card, the emergency call functions remain present, which sounds like a good idea to me.
As a final thought, I do not remember having this problem with my previously ROMed phone. I can't recollect if it had the same emergency call options from the locked screen.
Thank you!
-Steve
Hi, I searched the forum but had no luck:
Completely new Nexus 5, White 16GB, and I have this issue:
When i receive and miss a call, as soon as the ringer stops the phone automatically shows the unlocked homescreen and it just stays there, instead of locking itself normally. This is really weird, and happens even if the phone is in my pocket (so it's not sensor-related like whatsapp pop-ups for example). Also not really safe i'd say. If I select another lockscreen method, it behaves normally (showing, for example, unlock pattern for a certain amount of time before turning the monitor off again.)
Anyone experiencing the same issue?
http://www.reddit.com/r/Nexus5/comments/1q04f7/nexus_5_unlocks_itself_after_a_missed_call/
This is the only other reporting I found on the web. Can anyone test this? It's really fast and easy, and I think this could be a pretty serious issue.
My phone (pin locked) doesn't do that. Phone stays locked. Is your phone kept unlocked?
jj14 said:
My phone (pin locked) doesn't do that. Phone stays locked. Is your phone kept unlocked?
Click to expand...
Click to collapse
Yes. I don't really like the pin/passcode unlock (also don't really need it). Classic slide is simple and fast enough, but it's crazy that it stays unlocked after a missed call.
Also, I noticed that it automatically enters the last application that was open the last time you locked it, creating even more concerns (last online on messaging applications, online status in facebook, ecc.)
Just imagine you boss calling you, with no luck, and founding out a second later you're online in Facebook. Just because you were ignoring your phone, while driving for example.
themcfly said:
Yes. I don't really like the pin/passcode unlock (also don't really need it). Classic slide is simple and fast enough, but it's crazy that it stays unlocked after a missed call.
Also, I noticed that it automatically enters the last application that was open the last time you locked it, creating even more concerns (last online on messaging applications, online status in facebook, ecc.)
Just imagine you boss calling you, with no luck, and founding out a second later you're online in Facebook. Just because you were ignoring your phone, while driving for example.
Click to expand...
Click to collapse
I agree - that should not be the expected behavior
nexus5 32gb here, exactly the same behavior.. I had to enable a pin/password unlock method because every missed call would unlock my phone, even in my pocket..
I have the same issue.
Maybe it is because of the app Light Flow Lite ?
mr_smith1 said:
I have the same issue.
Maybe it is because of the app Light Flow Lite ?
Click to expand...
Click to collapse
I thought this as well, but then I tried it on my friends N5 and had the same behavior, without light flow. I think many of us actually discovered this trying notifications in Light Flow (i bought the pro version) but it's not related to that.
kowloon12 said:
nexus5 32gb here, exactly the same behavior.. I had to enable a pin/password unlock method because every missed call would unlock my phone, even in my pocket..
Click to expand...
Click to collapse
Me too, but I hate it because I can't swipe down from the top to quickly see my notification without unlocking the device first.
Let me know if you guys have any advice on this issue, also report it in this thread to keep it bumped and see if anyone is reporting any solution.
themcfly said:
Me too, but I hate it because I can't swipe down from the top to quickly see my notification without unlocking the device first.
Click to expand...
Click to collapse
exactly this, it was so useful to just throw a glance to the notifications to decide if open them or simply clean them away
Yes same here, this looks to be a bug surely?
Sent from my Nexus 5 using xda app-developers app
OK thanks,
I reported the problem on google discussion (I copy/paste our first topic because you explained the problem very well ^^).
the URL:
"https://productforums.google.com/forum/#!category-topic/nexus/nexus-5/KML5nWW9q6o"
mr_smith1 said:
OK thanks,
I reported the problem on google discussion (I copy/paste our first topic because you explained the problem very well ^^).
the URL:
"https://productforums.google.com/forum/#!category-topic/nexus/nexus-5/KML5nWW9q6o"
Click to expand...
Click to collapse
Nice one, I have posted in that discussion as well. Hopefully we will get a response.
Others have the same problem, do you know how to report a problem to google ?
I just tried it on my phone, called from my desk number, missed call. It did open the phone all the way, but the screen turned back off in 5 seconds, per my settings.
My phones is currently stock, have not rooted or unlocked the bootloader yet. Only UI modification apps are Widgetzoid and Dashclock, I wanted to stay stock for a bit.
Sorry, that you are having issues. Unfortunately sometimes the easiest way to figure out what is causing the problems is to do a factory reset, and re-dowload your apps one by one, to see what is causing the problem.
Ok, but a several people have the same issue ...
Anyway, I think I will tri not to miss a call whenever the phone is in my pocket !
Zandeer said:
I just tried it on my phone, called from my desk number, missed call. It did open the phone all the way, but the screen turned back off in 5 seconds, per my settings.
Click to expand...
Click to collapse
I don't like setting the screen timeout so short, many thimes i just place the phone on my desk while messaging and I want the screen to stay on, for at least 2 minutes.
And when I lock my phone to keep it in my pocket, it's supposed to stay locked and ignore any unintended touches as soon as i slide to unlock, which was originally introduced to prevent an unlock by accident. Yes, I could lower my screen timeout to 5 seconds, but that does not solve the problem because still unintended touches can occur in that time frame.
themcfly said:
I don't like setting the screen timeout so short, many thimes i just place the phone on my desk while messaging and I want the screen to stay on, for at least 2 minutes.
And when I lock my phone to keep it in my pocket, it's supposed to stay locked and ignore any unintended touches as soon as i slide to unlock, which was originally introduced to prevent an unlock by accident. Yes, I could lower my screen timeout to 5 seconds, but that does not solve the problem because still unintended touches can occur in that time frame.
Click to expand...
Click to collapse
I wasn't sing o set your screen lock time to what I have it set at, I was just saying that it did re-lock. However, you are right, IMO it should not completely unlock the screen when the phone is ringing.
Though I have never not had a passcode on my phone, so not sure if that is how it always behaves. Was just trying to test and be helpful.
I sent a message to the google team, let's wait and see.
here is a link to see the bug :"http://www.youtube.com/watch?v=SSTq8Xhe6Kc&"
Zandeer said:
I wasn't sing o set your screen lock time to what I have it set at, I was just saying that it did re-lock. However, you are right, IMO it should not completely unlock the screen when the phone is ringing.
Though I have never not had a passcode on my phone, so not sure if that is how it always behaves. Was just trying to test and be helpful.
Click to expand...
Click to collapse
Thanks for testing, I was wondering if this could have been related to root / unlocked bootloader somehow but you have confirmed this is not the case as it happens on a totally stock phone.
good catch there. same issue here.
at least a Google employee has responded to the topic created HERE. Maybe that will expedite then pushing out an update ASAP.