Database Info

Widgetlocker problem

Hi,
Since two days I'm a happy and proud Note owner, but there's one thing, that makes me really go crazy:
I installed the program "Widgetlocker", because the standard lockscreen is quite broing. It actually works quite good, but sometimes the standard lockscreen still apears. Not instead of the widgetlocker, but additional. So I always have to unlock two lockscreens.
Does anybody else has got this problem? And how can I fix it?
I tried to find a solution in different forums and in the program configuration, without sucess!
Thanks for help!
Edit: The error apears mostly when there's a pop-up (gtalk e.g.) or when I plug in the charger....

I turned on root helper and home helper in settings, that fixed it for me. I'm on Stock Rooted XXKK9 if that helps.
Sent from my GT-N7000 using xda premium

I presume you have set the lock screen to "none" in the actual phone settings too?

NZtechfreak said:
I presume you have set the lock screen to "none" in the actual phone settings too?
Click to expand...
Click to collapse
Where? Can't find any option like that....
Thanks for help

Hi, chrcad,
Finally, the someone else who's been having the same problem.
It IS really irritating. Sometimes it's OK, but other times it just comes on.
Have turned off the lock screen option, but same thing happens. Someone please help!
Sent from my GT-N7000 using XDA App

NZtechfreak said:
I presume you have set the lock screen to "none" in the actual phone settings too?
Click to expand...
Click to collapse
Lol, i accidentaly hit the thanks button. You're welcome!
Sent from my HTC Desire HD using xda premium

drjp77 said:
Hi, chrcad,
Finally, the someone else who's been having the same problem.
It IS really irritating. Sometimes it's OK, but other times it just comes on.
Have turned off the lock screen option, but same thing happens. Someone please help!
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
My widgetlocker works fine. Been using it since day 1. Hmm.. Sorry. Not sure how to help.

chrcad,
Your problem seems related to the fact that Android is not having enough memory left ans simply closes "useless" apps and considers that WL is part of them. To prevent that to happen, simply check in advanced settings the "refuse to suspend WL" box and Android will look another application than WL to close

The_Steph said:
chrcad,
Your problem seems related to the fact that Android is not having enough memory left ans simply closes "useless" apps and considers that WL is part of them. To prevent that to happen, simply check in advanced settings the "refuse to suspend WL" box and Android will look another application than WL to close
Click to expand...
Click to collapse
Thanks @ everybody for the help, but unhappily it's still not working properly.
The problem always apperas, when the phone's sleeping and a gTalk message comes in.... but ONLY, when the gTalk ppop-up is activated......
Any (more) idea?

you are leaving it running all the time aren't you?

I use to have the same problem, very rarely but it was still annoying. I have put a lock on widgetlocker so if I ever close all programs, widgetlocker is still running. It's not happened since but it's only been a few days so I'll see.

chrcad said:
Edit: The error apears mostly when there's a pop-up (gtalk e.g.) or when I plug in the charger....
Click to expand...
Click to collapse
Some pop-ups cause this if they're designed to appear underneath the stock lockscreen rather than dismiss it.
For now:
1) Easy Wake Mode disables the system lockscreen
2) WL Settings > Long-press volume down for Experimental > Aggressive Dismiss stock lockscreen. This should work, but it's not well tested yet so it's off by default.

[Q] Screen Turns off on Vonage Mobile App

Hi,
I use At&T Atrix 2.3.6 with Rooted. When I use Vonage mobile app, after I dialed number, screen turn off (same behavior as normal calls) but problem is it never turns on until Call get disconnected. When I press Powerbutton all I see in bank screen (on Normal call this gives back screen, so we can choose dialpad or speaked). If I repress again phone get locked. Home button gives me home screen but i couldn't find a way to get the dialpad on vonage call screen. This causes almost ununsable vonage for customer care call.
I already contacted the Vonage app developer and suggested method is reinstall and restart which isn't working.
Is anybody else use Vongae successfully without this issue on Atrix-2? Any suggestions?
Thanks as always.
-Nambi

sazhagianambi said:
Hi,
I use At&T Atrix 2.3.6 with Rooted. When I use Vonage mobile app, after I dialed number, screen turn off (same behavior as normal calls) but problem is it never turns on until Call get disconnected. When I press Powerbutton all I see in bank screen (on Normal call this gives back screen, so we can choose dialpad or speaked). If I repress again phone get locked. Home button gives me home screen but i couldn't find a way to get the dialpad on vonage call screen. This causes almost ununsable vonage for customer care call.
I already contacted the Vonage app developer and suggested method is reinstall and restart which isn't working.
Is anybody else use Vongae successfully without this issue on Atrix-2? Any suggestions?
Thanks as always.
-Nambi
Click to expand...
Click to collapse
Hi Nambi,
My name is Tzahi Efrati and I'm from VonageApps, Vonage's mobile development center.
We had an issue with the proximity sensor several versions ago. However, we couldn't recreate it using any of our devices today.
Can you please make sure you're using the latest version (1.5.1)?
Thanks,
Tzahi

Hi,
Thank you for your reply. Its indeed 1.51 version I am using. My friend who uses HTC One V where its working fine. In Atrix2, we have default option of screen goes blank when initiate call and same happens in Vonga app, but pressing power screen won't get the screen as native Dialer does.. I tried deactivate --> uninstall --> Restart --Install already which also not helping.
Let me know if you need any more information....
Any body else using Vonage app in A2, please comment..

check your build.prop. there is some stuff there about the proximity sensor. you can try tweaking the values. I just saw a post on which they are in one of the rom threads in the dev section (romulus I think). check that out.
What rom are you on anyways?

lkrasner said:
check your build.prop. there is some stuff there about the proximity sensor. you can try tweaking the values. I just saw a post on which they are in one of the rom threads in the dev section (romulus I think). check that out.
What rom are you on anyways?
Click to expand...
Click to collapse
Yep, I also stumbled across same info on Romulus Rom thread and verified my build.prop which is same as stock.
I am on Stock 2.3.6 , Rooted though. I also installed the Bootstrapper to flash 1% Mod done by alteredlikeness.

sazhagianambi said:
Yep, I also stumbled across same info on Romulus Rom thread and verified my build.prop which is same as stock.
I am on Stock 2.3.6 , Rooted though. I also installed the Bootstrapper to flash 1% Mod done by alteredlikeness.
Click to expand...
Click to collapse
that shouldn't affect it, it is probably just a glitch with our device.

lkrasner said:
that shouldn't affect it, it is probably just a glitch with our device.
Click to expand...
Click to collapse
I am having the exact same problem - Atrix 2, latest stock rom (2.3.6), the screen goes blank the second I hit the call button and does not come back on until the call gets disconnected.
Tzahi, Any suggestions?

reCAPTCHA
sazhagianambi said:
Hi,
I use At&T Atrix 2.3.6 with Rooted. When I use Vonage mobile app, after I dialed number, screen turn off (same behavior as normal calls) but problem is it never turns on until Call get disconnected. When I press Powerbutton all I see in bank screen (on Normal call this gives back screen, so we can choose dialpad or speaked). If I repress again phone get locked. Home button gives me home screen but i couldn't find a way to get the dialpad on vonage call screen. This causes almost ununsable vonage for customer care call.
I already contacted the Vonage app developer and suggested method is reinstall and restart which isn't working.
Is anybody else use Vongae successfully without this issue on Atrix-2? Any suggestions?
Thanks as always.
-Nambi
Click to expand...
Click to collapse
I have a similar issue on my Samsung Note 3 when I use placing the call using WiFi/3G/4G setting. I have to restart the phone to disconnect from the call. The phone goes complete blank after I place the call using Vonage extensions app. I am very much frustrated as I travel a lot and thought this app would allow me to be in touch with others. Any help will be appreciated.

ijsethi said:
I have a similar issue on my Samsung Note 3 when I use placing the call using WiFi/3G/4G setting. I have to restart the phone to disconnect from the call. The phone goes complete blank after I place the call using Vonage extensions app. I am very much frustrated as I travel a lot and thought this app would allow me to be in touch with others. Any help will be appreciated.
Click to expand...
Click to collapse
Since this is an issue with the app you should email the developer.
[email protected]

Nexus 5 Dialer

Is anyone else experiencing issues with the Nexus 5 dialer?
Whenever I launch the dialer and hit the bottom bar to bring up the buttons, I just got a frozen screen with a white bar at the bottom.
If I hit back and try again, then the dialer numbers come up.
Anyone else seeing this?

phonepersonality said:
Is anyone else experiencing issues with the Nexus 5 dialer?
Whenever I launch the dialer and hit the bottom bar to bring up the buttons, I just got a frozen screen with a white bar at the bottom.
If I hit back and try again, then the dialer numbers come up.
Anyone else seeing this?
Click to expand...
Click to collapse
I too have this problem. It is really annoying.

I don't have this use?
Sent from my Nexus 5 using xda app-developers app

nope

I can reproduce this every time I hit the dialer button after clearing the app data for Google Dialer. Although this happens to me randomly too.

Another dialer problem.
Deleted

SOLVED!
Issue occurs when 'Animation Duration Scale' under Developer Options, is set to zero (x0).
Anything over zero makes the problem go away.

SOLVED!
Issue occurs when 'Animation Duration Scale' under Developer Options, is set to zero (x0).
Anything over zero makes the problem go away.

Good that you solved it but at least let people know that you've done all these mods

Black screen on incoming calls

I have a very strange problem on my Nexus 5.
Some times when i receive an incoming call, i hear the ringtone, the device vibrates but i dont see anything on my display. Just a black screen, Also pressing the power button, i see the lock screen, unlocking the phone will not show the call either. if i select the dialer application i get the screen in the dialer with 3 options:
1) use touch tone keypad
2)return to call in process
3)add call
By pressing "return to call in process" nothing happens.
The problem is gone after restarting the device.
I read somewhere that this may be a proximity sensor problem due to screen protectors. I removed mine, and it continued having the problem.
Is there anything i can do to fix it [reseting the phone will be the last resort].
Thanks

I encountered this problem too, and now a new problem is my phone dead, cant turn it on.
any advice?
tsangaris said:
I have a very strange problem on my Nexus 5.
Some times when i receive an incoming call, i hear the ringtone, the device vibrates but i dont see anything on my display. Just a black screen, Also pressing the power button, i see the lock screen, unlocking the phone will not show the call either. if i select the dialer application i get the screen in the dialer with 3 options:
1) use touch tone keypad
2)return to call in process
3)add call
By pressing "return to call in process" nothing happens.
The problem is gone after restarting the device.
I read somewhere that this may be a proximity sensor problem due to screen protectors. I removed mine, and it continued having the problem.
Is there anything i can do to fix it [reseting the phone will be the last resort].
Thanks
Click to expand...
Click to collapse

danheng said:
I encountered this problem too, and now a new problem is my phone dead, cant turn it on.
any advice?
Click to expand...
Click to collapse
Can you get into bootloader so you can flash the factory image? Did you press the power button for about 10-15 seconds to force boot first.

Mine boots up as supposed to. Today i didn't have the incident.
Is this not a common problem?
Sent from my Nexus 5 using xda app-developers app

Are you running stock or a custom ROM and if so what rom. Also if you could pull a logcat it could be easier to diagnose.
P.S. have you tried clearing data for the dialer app.

i am suffering from this issu haswell.

After a week of no incidents today i had the same problem again.
I am running vanilla android 4.2.2 by Google. No root no custom rom...
Sent from my Nexus 5 using xda app-developers app

How can i have the logcat?
Also clearing dialer data will impact my call log history?
Sent from my Nexus 5 using xda app-developers app

tsangaris said:
How can i have the logcat?
Also clearing dialer data will impact my call log history?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
If you are worried about losing your call logs, they can be backed up a ton of different ways. When I don't have root, I use this:
https://play.google.com/store/apps/details?id=com.riteshsahu.CallLogBackupRestore&hl=en
Very lightweight and easy to use.

es0tericcha0s said:
If you are worried about losing your call logs, they can be backed up a ton of different ways. When I don't have root, I use this:
https://play.google.com/store/apps/details?id=com.riteshsahu.CallLogBackupRestore&hl=en
Very lightweight and easy to use.
Click to expand...
Click to collapse
Thanks for the tip!
I was talking to my brother today (he is a Nexus 4 owner) and he told me that after updating from 4.3 to 4.4 he had the same problem. He could only solve it by restarting his device. So i guess, this is a dialer bug. Clearing dialer data i dont think will help..

@op do you got Truecaller installed or any other app like that?

Z3US911 said:
@op do you got Truecaller installed or any other app like that?
Click to expand...
Click to collapse
No nothing!
Especially on my Nexus 5, i dont mess things up. Everthing is running as the day i bought it, just installed some common applications (Ex. Facebook, weather prediction,etc.).

tsangaris said:
No nothing!
Especially on my Nexus 5, i dont mess things up. Everthing is running as the day i bought it, just installed some common applications (Ex. Facebook, weather prediction,etc.).
Click to expand...
Click to collapse
mate i also faced this issue.So i tried uninstalling Truecaller and it worked for me.No more black screen.

Thanks for the suggestion but no application like this is installed on my device.
Maybe i will go throughout my apps once again..
My brother's N4 running 4.3 never had a problem. As soon as it updated to 4.4 he is having the problem.. Rarely but the problem is still there.
Sent from my Nexus 5 using xda app-developers app

This problem is getting on my nerves!!
I hope 4.4.3 solves a lot of bugs of N5! Its a shame that an excellent device like this causes such problems.
Also another problem my friends are reporting, is that, they call me, it rings 3 times and then it hangs like if the device is powered off or i canceled the call. And i dont even hear it ring, or find an answered call.
Is there a chance all these problems to be linked on my provider?

tsangaris said:
Thanks for the tip!
I was talking to my brother today (he is a Nexus 4 owner) and he told me that after updating from 4.3 to 4.4 he had the same problem. He could only solve it by restarting his device. So i guess, this is a dialer bug. Clearing dialer data i dont think will help..
Click to expand...
Click to collapse
Same problem here, 4.4.2 original from Google.

SiteDispatch said:
Same problem here, 4.4.2 original from Google.
Click to expand...
Click to collapse
I started thinking that maybe its caused by a 3rd-party application, but it seems that other Nexus 5 owners experiencing the same problem as well..

After some thinking i used factory reset on my device yesterday evening just to rule out the possibility below:
As soon as i have purchased the device Google Now wasn't available. So i read in a forum that in order to fix this you have to somehow trick the device that you are situated in a country where Google Now is available. So i downloaded an app (GPS fixing??) and positioned my device to UK, remove something and then install it again(Google services). That fixed the problem and Google Now was available.
Maybe something went wrong there and i was experiencing these problems..
So far so good. Then again to be sure if that was the problem i have to give it at least 2 weeks.
I will get back to you for the results.
Sent from my Nexus 5 using xda app-developers app

Facebook Messenger Quick Emoticon Button Failure

I saw this issue posted on another forum by someone else with no responses. I know many of you here probably don't have the Facebook messenger app installed/enabled because of the the reports of battery drain but I figured I would try my luck and ask anyway as I have this issue as well now. If you do have the app installed, or are familiar with how it works, there is a quick reply emoticon button (default is thumbs up) to the right of the chat box which you can press once to send the emoticon (or hold the button to make it bigger). Several months ago this stopped working for me on my lollop Sprint Note 5. One day I just noticed the thumbs up icon stopped working. Pressing it makes the button depress action but then does nothing. Holding it to make the thumb bigger does nothing. Changing the emoticon default to something other than a thumb does nothing. Since the app is baked into the OS I can't completely get rid of it without root (to my knowledge). I tried deleting the cache, then the data, then "uninstalling updates," then reinstalling the updates, but the problem remains. I have submitted many feedback reports to Facebook through the app but have received no response. I don't know what else I can do at this point. Is there a way to contact Facebook and actually get a response?Any other suggestions on how I can get this to work?

Yea it doesnt work for me either
Sent from my SM-G928P using XDA-Developers mobile app

infamouzwt said:
Yea it doesnt work for me either
Sent from my SM-G928P using XDA-Developers mobile app
Click to expand...
Click to collapse
Looks like this other guy is using AT&T and has the problem as well.... I really wish I could get a response from Facebook. Is there any way to roll back the app to see which version broke it? http://forums.androidcentral.com/fa...cebook-messenger-quick-emoji-reply-error.html

In case anyone has been following this (doubtful) it looks like the issue was caused by something I did in developer options. I don't know which specific option it was that broke that function but when I turned it off and restarted the phone thumb button is now working. I will have to go through the options to see exactly what the problem one was.