Delay problems - Galaxy Note 3 Q&A, Help & Troubleshooting

Hi everyone!
After i rooted and flashed a recovery on my note 3 realized that whenever i reboot or shut down and power on my phone after i unlock the sim (via pin) the phone gets at home screen but is like dead, meaning for about a minute or two i cant lock the screen with the power button, the home and settings buttons dont light up when i push them or do any noise or vibration, wifi remains off, power saving remains off until the phone makes a quick vibe after 2 minutes or so. That quick vibe was quicker before the root and recovery, it was instant after i unlocked the sim. Also after that problem i got a calling delay, after i try to call someone now and then i have to wait for a minute or so until the call starts. The screen stays at dial pad but doesnt do anything, i can dial numbers but no key noise no key vibration. I unrooted my phone, flashed the stock rom again etc but the problem remains. If anyone knows what to do please help me out

I've not done anything to the system at all (Root, flash etc, I'm on full stock) and mine does this too. I boot it up, and for a ful 2-3 minutes it simply remains on and I can't do anything to get it to turn off. I can long-press the power key to bring up the menu, but locking the screen is simply not happening at all. Irritating, but alas.
As for the delay in calling, it usually takes a while between the dialing out and the line to actualy establish, that's probably a network issue.

ShadowLea said:
I've not done anything to the system at all (Root, flash etc, I'm on full stock) and mine does this too. I boot it up, and for a ful 2-3 minutes it simply remains on and I can't do anything to get it to turn off. I can long-press the power key to bring up the menu, but locking the screen is simply not happening at all. Irritating, but alas.
As for the delay in calling, it usually takes a while between the dialing out and the line to actually establish, that's probably a network issue.
Click to expand...
Click to collapse
i don't think that its a network problem because it happens only to me and not always. It takes a while normally but in my case it stuck's on the dial pad not between dial and line. It doesn't even turn the screen off if i put it to my ear...

Have you tried to disable the SIM pin?
I never have a pin code on my SIM and never seen this problem.

SquirtingCherry said:
Have you tried to disable the SIM pin?
I never have a pin code on my SIM and never seen this problem.
Click to expand...
Click to collapse
its not the pin, the phone is like dead for 2 minutes untill it starts, something like it is slow on waking

anything new?

Related

Stop accidental key presses?

Anyone have a solution for this? I have my Wizard go to standby after a short time and always make sure it is in standby when I put in in my case. However, when I receive a call and pull it out of the case, I almost always press one of the buttons. So when I answer the phone I have the camera going, contacts open or the connection manager open. I use all the buttons so I don't want to disable them completly. I wash there was a way to disable all buttons except the answer button for like 5 seconds after a call starts ringing. Or, be able to set buttons to not activate unless pressed for 2 seconds or so. Or, require 2 presses to activate. Anyone have any ideas?
Thanks
Turn on the password (4 digit one is fine) and set to 0 minutes, the phone will "lock" as soon as you go into standby but when it rings you will be able to answer with the red/green buttons but nothing else until you put in your password.
Thanks, I will give that a try. I used a password before but it slowed things down so much that I removed it. I have done quite a bit of optimizing since then and will try it once more.
it does slow the use, and gets annoying (i still use it) but it does work until i find a decent app to do it. All it really needs is 2 touches or 2 buttons to unlock but not found anything yet... \
I have solved this with litle less work .I have Device lock Bar on the top, under date , so you need twice down and middle buton to lock the
device.
device lock doesn't seem to play well with the password application. if you have password activated you can do a device lock but when you put your device on standby and bring it to full power it is unlocked. if you use device lock without password it works.
any solution to lock keyboard during a call ? i always active some functions with my ears(...) when i speak
starseb - switch your phone to stand-by mode... the radio (phone part) should remain on, and you can continue calling. Then just switch it back on when done ( or not %) )
sorry for my english, but i make i make a mistake. i would say how to lock screen during a call.
bostjan said:
I have solved this with litle less work .I have Device lock Bar on the top, under date , so you need twice down and middle buton to lock the
device.
Click to expand...
Click to collapse
Is there a good way to unlock by pressing just keys?
Try christoph's deltaLock map it to a hw button then set it to be unlocked by the same hw button.

Keeping it in standby

Anybody know if there's a way of keeping my Trinity in standby even when a text message comes through - I keep the thing in my pocket and if I don't look at it straight away after a text has come through, all kind of things happen - programs get launched, photos get taken, voice memos are created, just from it moving around in my pocket after un-standbying itself!??
Thanks
Lock the screen and when a text comes no programs will launch!
Nope...
Doesn't work...as soon as a text comes through, everything unlocks - is there anyway to stop this from automatically happening?
Thanks
flight mode
tjw2007 said:
Doesn't work...as soon as a text comes through, everything unlocks - is there anyway to stop this from automatically happening?
Thanks
Click to expand...
Click to collapse
Not so on mine when it is locked it stayes locked! The screen will come on but the machine stays locked.
What mine is doing is when a text comes through, it seems to be causing the device to unlock, because the screen will take touch commands - I need to be able to lock the screen and get it to stay locked even when a text comes through. Any experts out there who might know how to achieve this?
Thanks
What is flight mode anyway?
OK, let me put this another way - is it possible to lock the screen until you press the standby button, so that nothing else unlocks it such as a text message or phonecall?
Thanks
I don't have this problem. My screen is set to go off after 1 minute. When the phone is in standby, all I get is a tone and the orange light flashes. The screen will not come on, unless I press the power button.
No input is accepted when in standby by the screen or any button except the power button - check your settings
I also have it set to auto-lock after 2 hours, so even if I get a text, and turn the screen on, then i need to put the password in before the screen unlocks
i use my m700 the same as you with no problems
RESOLVED!
Managed to put the device lock option on the 'Today' screen and this keeps the whole device locked (screen & all) no matter what happens, until you press the unlock option on the screen. Hooray!

Screen Lock issue with HD2

After i hang up on a call (when the phone is in sleep mode and the screen is locked) the screen unlocks. this is quite contrary to what is mentioned in the phone manual chapter 1 page 45. this becomes an issue since i use a bluetooth headset and the phone remains in its sleeve/case and after every call, a whole bunch of applications will launch since the case is in contact with the screen. have i overlooked some settings or are there other owners who have faced this issue?
ideas and suggestions welcomed
did you check it out if any of the hardware buttons being pressed against the case hence wakening up the phone.?
i had it to only closed al my apps in taskm and it stoped flickering
My HD2 is also behaving in the same way even in controlled test conditions - the phone unlocks when a call comes in (I'm presented with slide to accept or reject call) The phone unlocks during the call, but fails to lock again on disconnect (either by pressing "end call" or hang up via bluetooth).
Can anyone verify this? Is it interacting with something I installed?
I believe I found a (complicated) workaround.
What I want: leave HD2 inside pocket, answer calls with bluetooth headset, hang up and phone will go back to lock.
Problem: After I hang up using bluetooth or press the big red "End Call" button or the other party hangs up, the phone stays unlocked! It stays powered on and all kinds of buttons gets clicked.
Practically all lock sw uses their own lock screen (which I don't want to install). CSDevCtrl does not trigger by phone. TouchLockPro uses its own transparent lock screen but can respond to phone events. Using the !SUSPEND for TAPI\Ended under settings does not seem to work when the screen dims about 50 secs into the call.
Solution: Use TouchLockPro together with LockAndOff. Get TAPI\Ended to run LockAndOff will turn phone off, whether by bluetooth, big red "End Call" button, or the other party hangs up.
BTW: I think there is some confusion on whether the phone locks when you
1. press the big red "End Call" button, or
2. the hard "End call" button
in the forums.
I noticed that HD2 have a light sensor next to the top ear speaker.
During a call, if the phone is put near the ear and cover the light sensor , the screen become non-active which is good.
If anyone can come up with a lock sceen using this light sensor , then the problem with random launch of program when phone inside pocket will be solved.
This lock screen should only activated right after an end of call, beacuse , sometime you may want to use the phone in a dark place.
linivan said:
I noticed that HD2 have a light sensor next to the top ear speaker.
During a call, if the phone is put near the ear and cover the light sensor , the screen become non-active which is good.
If anyone can come up with a lock sceen using this light sensor , then the problem with random launch of program when phone inside pocket will be solved.
This lock screen should only activated right after an end of call, beacuse , sometime you may want to use the phone in a dark place.
Click to expand...
Click to collapse
It's the proximity sensor that turns the screen on and off during a call, not the light sensor. How else would it work in the dark? (which it does)
johncmolyneux said:
It's the proximity sensor that turns the screen on and off during a call, not the light sensor. How else would it work in the dark? (which it does)
Click to expand...
Click to collapse
My proximity sensor does not work, when I am getting a call my screen turn off and when I am taking the phone out from my face it turn on only when I am out side at the sun!! the screen stay off when I am inside room. I tested it with flsh light and it is working also.
I have a T-Mobile US version of the HD2. I am having the same problem when using the bluetooth system in my car. After answering or making a call the phone stay unlocked. And then starts making random calls while I am driving!!!!
There has got to be an easy fix for this!!!
Buy pocketshield, problem solved.
i have this unlock problem with 1.48 rom and i solve it by pressing start button and lock. after that everything works fine unless i change theme in settings. then just repeat first step.
Solved
Same trouble with me until I use the following software. I tried it and it's almost perfect. unzip it and just copy to your HD2, run CallerLoc.exe and click Yes, you'll find:when you hang up, or he/she hang up a call, or a call is established, the screen will turn off.
Why say 'almost perfect', the software is in chinese, but the filename is in english. and it's a call location software but with the function we need.
To stop or before you delete the software, run Callerloc.exe and click Yes again.
Hope this will help you. Sorry I don't find a English version of this software. I esure and I'm using this software perfectlly with my Leo.
theciscokid said:
Buy pocketshield, problem solved.
Click to expand...
Click to collapse
Same for me
Greetings.
I understand this is quite an old thread I'm digging up but I need a little help as well and I didn't want to start a new topic just for that.
I've this silly problem, appeared right out of the blue:
You all know the standard manila behavior, when the phone is idle, the screen first dims and after some more time, depending on your preferences, the screen locks. It also locks if you press the power off button. This all was happening to me till this morning.
I added an event in the calendar (the only change I made today) and after that, my phone dims and then goes in sleep mode after the designated period of time, but DOESN'T lock!!! It doesn't even lock when I press the power off button. I can still lock it by pressing Start and then lock or by press and hold the power button and choose the lock phone option. So one would say that it's still operational, so why bother about it, but I kinda liked the standard function and I have to freaking idea why it changed!!!
I'd be most appreciative if you could offer some help with that.
Oh, I forgot to mention. Soft reset didn't solve the problem. Erasing the calendar event didn't either.
My phone runs the factory ROM (1.66.482.1 ELL), I haven't changed anything other than user settings (yeah, I'm a noob... )
Thanks in advance!
Nasos
Pocketshield could be the end of your problems. You can try it for 10 days and see how it goes...
But why do I need to buy third party software in order to revert my phone to it's original operation?
No, this is not the answer I am looking for. I was wondering if you know of any kind of settings that might have changed by accident and caused this undesired behavior.
Thanks.
The best to return to normal operation would be a hard reset. Or you can spend a while trying.
You can try
HKLM\Software\Microsoft\Shell\Lockscreen\Enable=1
HKLM\Software\Microsoft\Shell\Lockscreen\Active=1
Thank you very much. I opted for the hard reset option... I hope it stays ok this time!
My HD2 also had some strange unlocking and unwanted calling.
I noticed it appeared when using the android style lockscreen.
When I changed back to the original one, problem solved
i had this too. the andriod lockscreen seems to be a bit buggy last time i used it, i accidentially called 7 random numbers

[Q] phone locks during call so I can not hook it

I am using the European Tab, but that probably makes no difference.
For security, I lock the phone automatically after 3 minutes of inaction. This works fine for all apps except phone. Strangely, after dialling (or after picking up a call) the phone first turns off the screen, and briefly thereafter locks the device, within 10 seconds. I can continue the call, but as the screen is off, I can not hang up, unless I first switch it on and enter the password.
I have not found a parameter to influence this behavior. But I know it is not related to the proximity sensor, as the effect happens the same way even when not moving the device from the desk.
Is this a confirmed behavior or does anyone know a cure? It's ok if the screen goes dark, and even if you must turn on via power button, but the password?!
Thanks for any help,
Rolf
rgbigel said:
I am using the European Tab, but that probably makes no difference.
For security, I lock the phone automatically after 3 minutes of inaction. This works fine for all apps except phone. Strangely, after dialling (or after picking up a call) the phone first turns off the screen, and briefly thereafter locks the device, within 10 seconds. I can continue the call, but as the screen is off, I can not hang up, unless I first switch it on and enter the password.
I have not found a parameter to influence this behavior. But I know it is not related to the proximity sensor, as the effect happens the same way even when not moving the device from the desk.
Is this a confirmed behavior or does anyone know a cure? It's ok if the screen goes dark, and even if you must turn on via power button, but the password?!
Thanks for any help,
Rolf
Click to expand...
Click to collapse
It happens to me lately after I flashed a new Rom but I highly doubt that has anything to do with it...it feels like a proximity sensor issue, and a autolock issue as well . I am Clueless sorry

Screen Turning on delay !!!!

Rom: Olyfr sbf upgraded to 4.1.5.7 from 4.1.2.6 via OTA
Not rooted
I have not yet modified the power button.
'Cause I set up the fingerprint unlock,Im used to swiping my finger after press the power button.
after pending or standing by a while(maybe),It vibrates once after my unlocking through scanning fingerprint.But!!!! The screen is still black!!!
Meanwhile,touching the four buttons on the bottom,it still vibrates!
And waiting for seconds,Screen on~~~~~
Symptoms sound a lot like my Bell Vibrant before it died after the Froyo upgrade.
Have you tried resetting your phone yet?...
Okay,I have flash it to 4.157sbf,and temporarily nothing goes wrong
I have the same symptoms. Sometimes when I push the power button it takes 3-5 seconds or more for the screen to light up. I did a power off and on and it works better. Not sure what is causing this but it is annoying.
I've had this on.both my atrixes and it seems to.resolve itself as the phone gets older
Sent From My Gibgerblurred Phone
I have had the same issue on mine. It occurs intermittently. Not always, but sometimes. And when the screen is turned off, I push the power button and nothing happens for about 3-5 seconds. Sometimes longer.
I do also have the fingerprint security feature on, though I am not sure if that that has something to do with it. However there is another problem with the fingerprint security.
Sometimes I want to check the time so I just turn on my screen and quickly turn it back off. But the screen turns right back on cuz it recognized my click as a fingerprint. However since it is too short to be recognized, it just turns my screen back on and says to try again. I try to turn the screen off again and the same thing. This also happens on occasions.
They need to make the power button better so that ways it does not recognize a screen turn off as a fingerprint swipe.
I have had similar problems. Rebooting has usually fixed them, at least for a while

Categories

Resources