hey guys,
I wanted to find out if anyone else is having this issue - when i go into the phone app, and press the keypad button on the bottom. the onscreen keypad doesnt show up - i have to press back and then press keypad button a 2nd time for it to show. But once i do this - it works fine if i go back into it at a later time. I have attached a pic of what the phone looks like when i press the keypad for the first time.
https://www.dropbox.com/s/76cr4p1zmdmtekm/Screenshot_2014-03-06-16-17-41.png
Not sure if this only happens when you restart or load the phone app for the first time.
Any ideas or input will be greatly appreciated
Thanks
R
rhath127 said:
hey guys,
I wanted to find out if anyone else is having this issue - when i go into the phone app, and press the keypad button on the bottom. the onscreen keypad doesnt show up - i have to press back and then press keypad button a 2nd time for it to show. But once i do this - it works fine if i go back into it at a later time. I have attached a pic of what the phone looks like when i press the keypad for the first time.
https://www.dropbox.com/s/76cr4p1zmdmtekm/Screenshot_2014-03-06-16-17-41.png
Not sure if this only happens when you restart or load the phone app for the first time.
Any ideas or input will be greatly appreciated
Thanks
R
Click to expand...
Click to collapse
I had this problem also when I was using Cyanogenmod. To solve this problem, try to disable Developer Mode as test.
I think the problem is caused by Scale Animation option when it is set by 0.
Hi mate thank you for your help. I switched all animation scale to .5 and turned off developers options. This seems to have fixed it
Sent from my AOSP on HammerHead using xda app-developers app
rhath127 said:
Hi mate thank you for your help. I switched all animation scale to .5 and turned off developers options. This seems to have fixed it
Sent from my AOSP on HammerHead using xda app-developers app
Click to expand...
Click to collapse
Good to hear it. :laugh::good:
Related
For those whose proximity censor is not working and they are on MIUI.
you just cant end a call even if u hit power button the screen doesn't turn on.
Here's a solution for that.
If you aren't using launcher pro then install it. Hit home. Now you'll be in a new launcher.
Long press an empty space on the screen. Choose shortcut >activities >settings >accessibility settings. It will prompt you to choose that as the shortcut and it will be placed on the screen.
Then open that and it will ask you if you want to install some accessibility features (because the rom doesn't come with any) but feel free to say no.
And there you go. Power button to end call. Once you're done you can uninstall lp.
I hope u guyz get help from it. I really had a hard time bcoz of this.
thanks! i tried finding it in settings but i couldnt find it then i came across this
Thanks!!!
Sent from my MB525 using xda premium
So I came across this in the EVO 3D forums. How hard do you think it will be to port this to our device?
http://forum.xda-developers.com/showthread.php?t=1346760
It is in development already. See bricked kernel thread for more info.
Sent from my Sensation
Anyway to enable this?
http://forum.xda-developers.com/showthread.php?t=1269247
And gnex has it
Both Bricked and TamCore have this feature.
Bricked: http://forum.xda-developers.com/showthread.php?t=1269247
TamCore: http://files.tamcore.eu/android/?dir=tamcore-kernel
Bricked gives you an option to enable it during installation, while TamCore requires you to flash a zip to enable it, which you can get on the same page, under the name "sweep2wake_enable.zip".
A few kernels already have it.
I am already using it... :angel:
Already using it on bricked!
It's nice because you don't have to constantly use your power button to turn on device ! I really love it! It's so easy.
Sent from my HTC Sensation 4G using xda premium
Is there any way to make it more efficient when locking the device? I find that it closes the current application and goes to the home screen (as you swipe the back and home keys when locking your device).
This is quite annoying when using an app like gmote when I may need to immediately unlock my phone again to pause/play adjust volume etc, as I find that the app has been terminated when putting the device to sleep.
I really like the idea of not having to mash my power button any more than necessary, so using the sweep to lock would be ideal. I also noticed that even in the demo video of sweep to wake, the menu button gets pressed as the phone is locked (you can see the launcher menu appear for a second before the device locks).
Any suggestions would be appreciated, but I wanted to get some guidance before posting any sort of feature requests in the dev forum.
Thanks guys!
Louer Adun said:
Is there any way to make it more efficient when locking the device? I find that it closes the current application and goes to the home screen (as you swipe the back and home keys when locking your device).
This is quite annoying when using an app like gmote when I may need to immediately unlock my phone again to pause/play adjust volume etc, as I find that the app has been terminated when putting the device to sleep.
I really like the idea of not having to mash my power button any more than necessary, so using the sweep to lock would be ideal. I also noticed that even in the demo video of sweep to wake, the menu button gets pressed as the phone is locked (you can see the launcher menu appear for a second before the device locks).
Any suggestions would be appreciated, but I wanted to get some guidance before posting any sort of feature requests in the dev forum.
Thanks guys!
Click to expand...
Click to collapse
Sometimes it will pull up the power window, it will go back, back out of an app...instead of posting here...post in show-p threads.
It's a good feature, the bricked & faux kernels have it as far as I know!
Sent from my HTC Sensation Z710e using xda app-developers app
Louer Adun said:
Is there any way to make it more efficient when locking the device? I find that it closes the current application and goes to the home screen (as you swipe the back and home keys when locking your device).
This is quite annoying when using an app like gmote when I may need to immediately unlock my phone again to pause/play adjust volume etc, as I find that the app has been terminated when putting the device to sleep.
I really like the idea of not having to mash my power button any more than necessary, so using the sweep to lock would be ideal. I also noticed that even in the demo video of sweep to wake, the menu button gets pressed as the phone is locked (you can see the launcher menu appear for a second before the device locks).
Any suggestions would be appreciated, but I wanted to get some guidance before posting any sort of feature requests in the dev forum.
Thanks guys!
Click to expand...
Click to collapse
Skip pressing the back button, just sweep above the back button like that: __--_ (while locking)
kgs1992 said:
Skip pressing the back button, just sweep above the back button like that: __--_ (while locking)
Click to expand...
Click to collapse
Brilliant idea! This actually works as desired, and it doesn't seem to activate the home button in the sweep/swipe either. Now I just need to get in the habit of skipping the back key.
Louer Adun said:
Brilliant idea! This actually works as desired, and it doesn't seem to activate the home button in the sweep/swipe either. Now I just need to get in the habit of skipping the back key.
Click to expand...
Click to collapse
There's a thanks button.
However, I don't see how this is practical much. I only lock using sweep because it's a good shortcut to exit current app, go to home & luck.
I have noticed since yesterday's Jelly Bean update (4.1.1) that if you have an app open (say a browser for example) and you let your screen timeout, when you press the home button it will turn the screen on screen up and take you back to your home screen. Used to with ICS it would just turn the screen on and you could continue in the app. Now it takes you all the way back home and you have to re-open the app to continue in it.
I was wondering if everyone is getting this same result or if it is just me.
Thanks!
I just tried it with Google Now and it returned to the app. I tried the Android browser and it returned the app as well. You might want to power down, pull the battery, then restart. Updates can sometimes act a little wonky at first. Occasionally (and unfortunately) a hard reset can FINALLY make an update work correctly.
Fixed this issue on my phone. The solution for me was to set up S-Voice, then go into it's settings and check the 'open via home key' option. After this, pressing the home key once simply wakes up the screen instead of also taking it to the home screen. Hope it works for you too!
Sent from my SCH-I535 using xda premium
Yea, that fixed it. I don't like S-Voice so I had that option turned off. Apparently it works different with this update then it did with ICS.
I've actually went in there and enabled that option then went into Application Management and disabled S-Voice. Now, if I accidently double tap my home button it just goes to a black screen for a second then back to the home screen. (Better than opening up S-Voice)
Thanks for your help!
I've found if you use a pattern password the home button "feature", to go back home works like how it used to
Sent from my SCH-I535 using xda app-developers app
Nice find! Now my dilemma is, whether the added "lag" when single tapping the home button is not as annoying as being taken to the home screen when pressing the home button after the screen times out. Having the double tap for S-Voice setting disabled speeds up that home button responsiveness.
Sent from my SCH-I535 using xda app-developers app
I find the lag to be to annoying when s-voice is enabled. A fast press of the power button will wake up the phone without closing the app you are using and you can keep s-voice turned off.
SlimSnoopOS said:
Nice find! Now my dilemma is, whether the added "lag" when single tapping the home button is not as annoying as being taken to the home screen when pressing the home button after the screen times out. Having the double tap for S-Voice setting disabled speeds up that home button responsiveness.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
grr, I couldnt agree more. I turned off that feature to reduce home button lag in ICS, now it closes any app open. Hopefully theres a fix
We'll find out. I dislike these small, unnecessary changes that Samsung has implemented. Horizontal pinch to expand notifications is another unnecessary change on VRBLK3.
Sent from my SCH-I535 using xda app-developers app
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
aromig said:
Fixed this issue on my phone. The solution for me was to set up S-Voice, then go into it's settings and check the 'open via home key' option. After this, pressing the home key once simply wakes up the screen instead of also taking it to the home screen. Hope it works for you too!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Ohhhh thank you so much! This was driving me CRAZY! :laugh:
Oh, I spoke to soon. I have tried the S Voice option but it still takes me back to home when I wake with the home button :crying:
lv2bsilly said:
Ohhhh thank you so much! This was driving me CRAZY! :laugh:
Oh, I spoke to soon. I have tried the S Voice option but it still takes me back to home when I wake with the home button :crying:
Click to expand...
Click to collapse
I feel your pain i also suffer from this same problem i had ics stock rom upgraded to hpyer drive rl14 and after that my home button only wakes up to a long press nothing seems to work i even reassigned soft keys functions so home would do back option and same thing,
I am currently using the Galaxy s4 with native keys that are not on screen for home, back, etc. When using navbar / pie and changing home screen the home button on the nav bar / pie does not work if you hit it quickly after you change the screen. Same kind of thing with opening apps if I remember correctly. Is this delay something you see in the OnePlus One as well? Flip a homescreen, hit home on navbar really quick and let me know if you find the phone not responding. It's aa if I need to wait a second for the device to recognize the command although the physical home button works just fine. Just wanna know if this is the case for the 1+1 because I am looking to pick one up shortly, thanks for your time
-Mike
Sent from my GT-I9505G using xda app-developers app
Hi All,
So I have a very odd issue. I have googled and searched the threads, but I cannot find any mention of the same issue from anyone else. Here is my problem:
When the screen is completely off (I have "Always On" turned off), sometimes when I push the power button the lock screen does not come up. Instead, I can barely make out tiny white text at the very bottom of the display that is half cut off. Obviously I cannot take a screenshot to show you. So I push the power button a couple of times and then it works.
Anybody have a clue what is going on?
Thanks in advance!
Dave
dmmoroney said:
Hi All,
So I have a very odd issue. I have googled and searched the threads, but I cannot find any mention of the same issue from anyone else. Here is my problem:
When the screen is completely off (I have "Always On" turned off), sometimes when I push the power button the lock screen does not come up. Instead, I can barely make out tiny white text at the very bottom of the display that is half cut off. Obviously I cannot take a screenshot to show you. So I push the power button a couple of times and then it works.
Anybody have a clue what is going on?
Thanks in advance!
Dave
Click to expand...
Click to collapse
Do u use greenify?
Sent from my Samsung SM-G955U using XDA Labs
I do! What setting can I change to resolve this?
dmmoroney said:
I do! What setting can I change to resolve this?
Click to expand...
Click to collapse
Auto hibernate. Just make a home screen shortcut and tap it B4 u lock your device
Sent from my Samsung SM-G955U using XDA Labs
I must be an idiot. Can you clarify? That sounds like an annoying extra step to have to tap an app prior to each time I lock my phone. Maybe I'm misunderstanding?
that text is greenify is working sign ..
when you press power button when it's working, you won't get screen wake. Need to wait until it's finished,
or press power once (to stop greenify process) then wait a little while until text disappears.
dmmoroney said:
I must be an idiot. Can you clarify? That sounds like an annoying extra step to have to tap an app prior to each time I lock my phone. Maybe I'm misunderstanding?
Click to expand...
Click to collapse
No it's a hibernate shortcut you don't actually open the app. just tap it and it'll put everything to sleep then just lock your phone. I don't use auto hide unless I have root. On nonrooted phones it takes forever to do it when you go to lock your phone and in my case it would take forever for me to be able to unlock my phone so I find it easier to just tap the shortcut then lock
Note the lil icon in the bottom right. It just puts stuff to sleep, doesn't open the app
Sent from my Samsung SM-G955U using XDA Labs
crayonyes said:
that text is greenify is working sign ..
when you press power button when it's working, you won't get screen wake. Need to wait until it's finished,
or press power once (to stop greenify process) then wait a little while until text disappears.
Click to expand...
Click to collapse
Also what he said, it's normal but slow
Sent from my Samsung SM-G955U using XDA Labs
buttsak said:
No it's a hibernate shortcut you don't actually open the app. just tap it and it'll put everything to sleep then just lock your phone. I don't use auto hide unless I have root. On nonrooted phones it takes forever to do it when you go to lock your phone and in my case it would take forever for me to be able to unlock my phone so I find it easier to just tap the shortcut then lock
Note the lil icon in the bottom right. It just puts stuff to sleep, doesn't open the app
Sent from my Samsung SM-G955U using XDA Labs
Click to expand...
Click to collapse
this!
I'm also using the hibernate&sleep shortcut widget,
and disable auto hibernate because of this long wait time.