Android L is for Lockdown

Root is, without a doubt, the (un)holy grail of the Android world. Those wonderful permissions that allow you as … more

XDA Xposed Tuesday: XHangouts Will Improve Your Hangouts

Ever since Google started supporting text messaging in Hangouts many people have … more

Shattered Screen? Turn Your Broken Device into a Complete Media Center!

A cracked screen usually means you’ll have to spend a hefty … more

Gmail 5.0: Material Design and Multiple Account Support

Google started to materialize many of its applications right after announcing the … more
Post Reply

Question [Q] Do your i9505 always "wake up" when you receive a call?

OP hotlips69

5th July 2013, 04:03 AM   |  #1  
OP Member
Flag Brighton, Sussex. UK
Thanks Meter: 1
 
95 posts
Join Date:Joined: Jun 2008
More
I've been having issues with my i9505 not always "waking up" when someone tries to ring me, and instead they get sent directly to my voicemail.

It's inconsistent from speaking to people who have tried to ring me and got my voicemail, even though my phone is ALWAYS ON 24/7 with a near maximum H+ signal, and always near full charge.

Is it normal when you press the home key and the lock screen appears that the clock initially shows the last time the phone was "woken" or "unlocked" and then in an instant corrects itself to the correct time??

It feels like the phone is going into a deeper sleep state than I'd like which MAY be causing my issues?
5th July 2013, 06:39 AM   |  #2  
HS™'s Avatar
Recognized Themer
Flag XDA
Thanks Meter: 2,278
 
2,065 posts
Join Date:Joined: Apr 2012
Donate to Me
More
Quote:
Originally Posted by hotlips69

I've been having issues with my i9505 not always "waking up" when someone tries to ring me, and instead they get sent directly to my voicemail.

It's inconsistent from speaking to people who have tried to ring me and got my voicemail, even though my phone is ALWAYS ON 24/7 with a near maximum H+ signal, and always near full charge.

Is it normal when you press the home key and the lock screen appears that the clock initially shows the last time the phone was "woken" or "unlocked" and then in an instant corrects itself to the correct time??

It feels like the phone is going into a deeper sleep state than I'd like which MAY be causing my issues?


have u updated to new version without a complete reset ?

If so do a Reset and try
5th July 2013, 08:20 AM   |  #3  
CP-93's Avatar
Senior Member
Thanks Meter: 55
 
204 posts
Join Date:Joined: Jul 2012
factory reset and you should be all set
5th July 2013, 05:56 PM   |  #4  
OP Member
Flag Brighton, Sussex. UK
Thanks Meter: 1
 
95 posts
Join Date:Joined: Jun 2008
More
Quote:
Originally Posted by CP-93

factory reset and you should be all set

I've not done any updates whatsoever and have only had the phone for 2 weeks, and simply installed several apps.

It took ages to configure the phone settings to my liking, so I really don't want to factory reset it.

Does the "clock not updating on lock screen" that I mentioned happen to you or anyone else?
3rd September 2014, 10:55 AM   |  #5  
Junior Member
Thanks Meter: 1
 
23 posts
Join Date:Joined: Aug 2012
Waking up this question thread. I'm experiencing the exact same issues - with my i9506 (the LTE+ model). Quite annoying actually even though the problem may seem minute.

Interesting to see that you havd/hade the same problems under JB. I'm seeing the same under KK 4.4.2. Just checked the clock-update on lock screen and for a split of a second, the clock showed the "old time" before it updated. I do not know if i had the same problem before updating to KK (I had the phone only for about a month before it was updated to 4.4.2). Maybe it has to do with some deep sleep policy issue for the Snapdragon chipset as both the i9505 and i9506 have Snapragon. I have reported my observations to my local Samsung customer care centre (which is in Sweden).

Rgds
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in Galaxy S 4 Q&A, Help & Troubleshooting by ThreadRank