I've had my V20 a few weeks now and have enjoyed what it can do for me. I really like the second screen feature, but I do have one complaint about it:
The notifications disappear too fast. They pop up when they come in and by the time I flip my phone over and begin to read the notification, it vanishes. If I want to know what it was, I would need to turn on my phone, thus defeating one of the purposes of the second screen.
Has anyone found that this this something that can be adjusted? Presently, I think the display time is about two seconds. I'd love to bump it up to about five seconds.
Ideas, anyone?
TVThemeGuy said:
I've had my V20 a few weeks now and have enjoyed what it can do for me. I really like the second screen feature, but I do have one complaint about it:
The notifications disappear too fast. They pop up when they come in and by the time I flip my phone over and begin to read the notification, it vanishes. If I want to know what it was, I would need to turn on my phone, thus defeating one of the purposes of the second screen.
Has anyone found that this this something that can be adjusted? Presently, I think the display time is about two seconds. I'd love to bump it up to about five seconds.
Ideas, anyone?
Click to expand...
Click to collapse
So after using this phone for a couple weeks, I’ve gathered the second screen for notifications works the same way as “heads up” notifications work on normal-display phones without the second screen. I don’t think there’s any way to change it on stock, but if you’re rooted I’m sure there’s a prop you can change to make the heads up notification last longer.
I would say like the last post you need root at least
Sent from my VS995 using Tapatalk
Related
i'm new of HTC TD2. my clock time changes all the time when it goes sleep mode and i press the power button and want to make a phone call, i need to adjust the time back. this is really annoying me coz it means i can't use this mobile as my alarm at all.
can anyone help me? I've already read the thread in the forum. but still can't find the solution. Thanks heaps.
Same thing is happening for me. This is the second Pure that I have owned and it seems like the time doesn't "keep up". Sometimes it will be only a few minutes behind; other times, hours. It has caused me to be late for work and I now have to set 2 alarms (I hate using standard alarm clocks and their annoying beeps and prefer to wake up to music that I have set on my phone, but I need a reliable back up). I really like the phone and hate to have to send it back for the second time for the same thing, but HTC seems to think that it is AT&T's network issues (funny how no one else or any other phones in my house have this problem). I'd be interested to know how many other people are experiencing the same problem.
Play with your sync time with network setting and see if that helps.
Thanks for the reply.
i think i've solved the problem. just unticked the automatically time zone changed. and it's running fine now.
What am I doin wrong ? Time out is set at 15 sec.
EDIT: Solved by using different SMS app. Email app works fine
nope.....email works, sms works, not missed call keeps phone awake all the time....
am i the only one ?
I had this problem... Had to reboot the phone.
I have noticed times when my screen was on. When I tried to determine why it seemed that I had received a mms over two minutes prior. My screen timeout is thirty seconds. I have since rebooted and will see if it makes a difference.
Sent from my SGH-T959 using XDA App
I've rebooted numerous times since I've gotten the phone. I prefer the stock messaging app and don't want to *have to* use something else to make it work right.
Any other ideas?
Looks like this is one of the bugs on the phone.....
Thank god all bugs are software related so far. With nexus it wad mostly hardware/software things
I think I figured it out (at least for me)...
I disabled the "puzzle lock" thinking it would be a pain in the neck when trying to unlock the screen. Come to find out, disabling it is what is leaving the display on when receiving a text. Enabled the puzzle lock, and the display comes on for a sec or two and then shuts off when I get a message.
I prefer very few steps to get where I wanna go. I don't like passwords or codes when unlocking my screen so I disabled it. Either way, though, I have swype the screen to unlock it so it's not a big deal to have the puzzle lock on...
I assume it is since it happens for my X10 as well as my girlfriends.
1) While texting it seems to freeze and have a constant vibration, then if your fingers kept texting it would eventually type all those keys or the last key multiple times.
2) Run out of memory. I use ATK and I notice after a day it starts off at something around 136mb of free memory then later in the day it will say "7 apps killed, 119mb remaining" and it has gone down to the 80's before. Where is this memory being used?
3) I seem to pocket dial/text a lot even though I lock the screen every time...
4) When on the phone it hangs up a lot from my cheek lol Is there a way to fix this other than bringing up the dialpad and hearing the keys being hit
Also might as well put this here. Is 'rooting' your phone the same as jailbreaking an iPhone?
C3LL0PHANE said:
2) Run out of memory. I use ATK and I notice after a day it starts off at something around 136mb of free memory then later in the day it will say "7 apps killed, 119mb remaining" and it has gone down to the 80's before. Where is this memory being used?
Click to expand...
Click to collapse
Basic stuff for an android phone. High memory usage is nothing to worry about, it's actually almost the opposite, more the merrier.
Hmm I think I've experienced most of those things. They're odd occurances. But be glad they're software issues, because software can be changed/fixed!
As for rooting vs jailbreaking an iphone... the thing is, since iPhone is locked down so much, jailbreaking an iPhone can make a big difference than a stock iPhone. Rooted android allows access to hidden system files, so can allow for more tweaking, but an unrooted Android phone already does so much, as opposed to an unjailbroken iPhone. Rooted android can by far do way more than a jailbroken iPhone. And even in some ways, an unrooted Android phone can do more than a jailbroken iPhone as well.
PS: can you share the numbers of some of you girlfriends? maybe I can help them out with their technical issues
C3LL0PHANE said:
I assume it is since it happens for my X10 as well as my girlfriends.
1) While texting it seems to freeze and have a constant vibration, then if your fingers kept texting it would eventually type all those keys or the last key multiple times.
2) Run out of memory. I use ATK and I notice after a day it starts off at something around 136mb of free memory then later in the day it will say "7 apps killed, 119mb remaining" and it has gone down to the 80's before. Where is this memory being used?
3) I seem to pocket dial/text a lot even though I lock the screen every time...
4) When on the phone it hangs up a lot from my cheek lol Is there a way to fix this other than bringing up the dialpad and hearing the keys being hit
Also might as well put this here. Is 'rooting' your phone the same as jailbreaking an iPhone?
Click to expand...
Click to collapse
1) I've noticed this. The pattern I notice is that this only happens when you're receiving text and typing. Since in the options for the keyboard you can enable vibration when u type I believe this is the problem. I haven't tested it but the way the phone seems to respond, it seems to be so. It seems to be able to only output one vibration feedback at a time. So in effect it delays those linked to your typing until the vibration for receiving text has ended. I could be wrong though.
2) It is most probably being used by background running processes. Typically you only really close a process by pushing the back button until it closes. If you continually open new tasks after pushing the center button you're essentially putting the current program in the background.
3)What you can do is enable a simple swipe pattern lock to help this, but even so you run the risk of locking your phone if you "guess" the pattern lock too many times. So I would recommend you buying a case for it if you don't have one. I have not had any problem like this and I use a case.
4)It sounds like your proximity sensor isn't working or isn't being properly activated by your cheek. What you can do is go to a mirror and call someone, while speaking to them shift the phone a little bit at a time until you see the screen black. This indicates the proximity sensor has detected your face being close to the phone. While you are at it you can also slide the phone a bit to get peak volume with your phone. From what I can see the in-call speaker is very directional.
EDIT: Yea you can consider rooting to be the android equivalent to jail breaking. Considering you're asking that I am guessing you have not rooted your phone yet. If you don't have the latest firmware it might be a good idea since it fixes some little oddities on the x10 as well as offering battery and speed improvements.
There's an easier way to test the proximity sensor:
While in lockscreen, press: Menu Back Back Menu Back Menu Menu Back
This opens the service menu. Go to Service Tests-Proximity Switch.
Now just move a finger over the sensor to test. It also gives you a sound so you can also try holding it to your cheek!
Hope that helps!
@beno1 cooooolll thanks man.
Sent from my X10a using XDA App
So I went into the testing part and checked the proximity switch and it says it is off. That's not what I want now is it? I couldn't figure out how to get it on.
As for pressing the Home button instead of Back.. wouldn't Advanced Task Killer close those applications anyways?
Put your finger over the proximity sensor and it will go from off to on.. then take it off and it will be off..
Tri3Dent said:
Put your finger over the proximity sensor and it will go from off to on.. then take it off and it will be off..
Click to expand...
Click to collapse
I tried that and it beeps, but goes back to off
C3LL0PHANE said:
I tried that and it beeps, but goes back to off
Click to expand...
Click to collapse
That's what it should do! It will only go to on when it is covered then as soon as you uncover it then it swiches back to off.
This is as it should be in the service test. It is working.
The issue is when i turn the screen off, lets say the time is 2:00PM and i check for notification at 2:20PM. What happens is as soon as the screen turns on the time jumps from 2:00 -> 2:20 PM , shouldn't this be done as a background process so that we shouldn't even see the time jump?
Anyone else facing this issue and any workarounds/fixes?
Thanks
Xxxdevilxxx said:
The issue is when i turn the screen off, lets say the time is 2:00PM and i check for notification at 2:20PM. What happens is as soon as the screen turns on the time jumps from 2:00 -> 2:20 PM , shouldn't this be done as a background process so that we shouldn't even see the time jump?
Anyone else facing this issue and any workarounds/fixes?
Thanks
Click to expand...
Click to collapse
Hi,
Does it always jump to the correct time?
I have seen this on different ROMS on other phones.
Xxxdevilxxx said:
The issue is when i turn the screen off, lets say the time is 2:00PM and i check for notification at 2:20PM. What happens is as soon as the screen turns on the time jumps from 2:00 -> 2:20 PM , shouldn't this be done as a background process so that we shouldn't even see the time jump?
Anyone else facing this issue and any workarounds/fixes?
Thanks
Click to expand...
Click to collapse
Pretty old. Used to happen on my S2 too.
i guess it is an intent that gets activated upon waking of the phone (by turning on the screen)... when you do that, it updates the screen and thats why.
but then again... that is only what i think.. if it should update it while the screen is turned off it would be an active process and use battery
Does it on mine too but only the clock on the main lock screen, the time on the top bar seems to be correct.
Sent from my iPad using Tapatalk (how ironic is that eh)
malybru said:
Hi,
Does it always jump to the correct time?
I have seen this on different ROMS on other phones.
Click to expand...
Click to collapse
Yes it always jump to the correct & exact time....it seems like a battery saving feature...if it is, other people with S4 should also experience it,no?
Tomo1971 said:
Does it on mine too but only the clock on the main lock screen, the time on the top bar seems to be correct.
Sent from my iPad using Tapatalk (how ironic is that eh)
Click to expand...
Click to collapse
For me i have a pattern Lock with time...so the moment i turn it on this is done on the lock screen clock...and yes the timer on the top bar seems to be correct(as in no jump).
Xxxdevilxxx said:
For me i have a pattern Lock with time...so the moment i turn it on this is done on the lock screen clock...and yes the timer on the top bar seems to be correct(as in no jump).
Click to expand...
Click to collapse
Hi,
I ,too, have the pattern lock screen.
But I have the Lightning Launcher.
So, there is no lag or delay on mine.
Maybe ,try a different launcher and see.
malybru said:
Hi,
I ,too, have the pattern lock screen.
But I have the Lightning Launcher.
So, there is no lag or delay on mine.
Maybe ,try a different launcher and see.
Click to expand...
Click to collapse
oh...will do
New to XDA. Hello all!
I am experiencing this clock lag as well. :/
It doesn't matter if I use a custom lock screen or the Samsung lock screen with "swipe to unlock".
It's easily reproducible, let phone sit for 10-15 min and if you press the unlock button you'll see the wrong time for anywhere from a fraction of a second to a few seconds! and then it will update to correct time. Super annoying if I just want to know the time. Also, I've found that the amount the clock is behind is proportionate to the amount of time the phone as been idle....to a point...
I've seen the clock be over an hour off but it doesn't drift much more than than. Like a few folks mentioned, this should be running in the back ground. What is confusing to me is the clock in the top right is correct, so the phone is monitoring the clock...it's just not updating the lock screen clock.
Hopefully we can find a work around.
Not too keen on a new launcher...at least not until others who have seen that lag switch over and confirm it as a fix...but I don't think it will help, because the lock screen is still a Samsung process not controller by the launcher (i don't think)
Any thoughts?
The clock on the main unlock screen is essentially a widget. As a power saving feature, it only updates as necessary, which would be when you turn your phone on to look at the time. The time at the top of the screen in the notification bar is not a widget, it is a built in process that is always active. That is why it is current and the large clock, "the widget", is off until you turn your phone on to look at it.
My phone does the same thing. As does pretty much everyone's. It is not anything wrong with your phone, it is just the way it is set up. It is usually only delayed by a second or two, at best.
If it is an issue, you can always just remove the widget and use the time at the top of the screen to check. Or try a different app and set the update frequency.
It's not that big of a deal to me, I know it's always off until it refreshes, so I just give it a second to update.
For as long as I've owned Smart Watches the number one reason for me has always been being able to see, at a glance, notification information. And I've always thought it really, really odd that watch makers don't give us more ability to tweak this.
In the latest version of Android Wear we now have three settings, which basically boil down too:
1. Never display
2. Display, but really quickly... look now or you'll miss it!!
3. Display forever until manually dismissed.
Obviously never display isn't an option for me as that's my big reason for WANTING a smart watching. But the opposite extreme: Always display until manually dismissed is annoying too. I want to see the notification, then have it go away. I don't need to see the same notification 10, 15, 30+ minutes later.
So that leaves the 5-second option. Now, I'm sure for some people 5 seconds is just the right amount of time and I have no beef with you if that works great for you. But that's too quick for me. I can't always look right away at my watch... if I'm in the middle of changing lanes on the highway or in a meeting talking right at that moment or assisting a customer... I can't always look in that short 5 second window.
I don't understand why this time limit is not customization! Each watch user is going to be different and want/need different things. So why can't we enter a number here? Why can't we pick the seconds for display? And if it's just too complicated to allow a user to enter a number of seconds, why can't we at least get more options then? Why not something like: Never, 5 seconds, 10 seconds, 20 second, or Always?
Isn't Android's motto supposed to be: "Together, not the same?" Why the "one-size fits all" mentality then with notifications on the watch?
I have the same issue. The 1/3 screen peek in 1.5 was perfect for me, I could pull it down today deal with later, tap on it to view, swipe to dismiss or take additional actions, etc. The new notifications are terrible, I've quit wearing my 360 sport until they fix it. I'm half tempted to buy a used one that's still on 1.5.