Guys. Any way to eliminate recent apps delay? After pressing the button it takes like 1 second to see some response. I assume that it can be somehow connected to long press option.
I have gen version d855 and I am rooted.
Thanks in advance
DforDesign said:
Guys. Any way to eliminate recent apps delay? After pressing the button it takes like 1 second to see some response. I assume that it can be somehow connected to long press option.
I have gen version d855 and I am rooted.
Thanks in advance
Click to expand...
Click to collapse
This delay happens on pretty much all android phones, mainly when you haven't opened the recent apps menu in a while. It needs time to cache thumbnails for all your recent apps. If you open it then close it, then open it again you'll notice there's less of a delay.
No way to eliminate that delay that i've seen.
Nit present on my nexus 5 and it happens all the time. Even if I click it again and again.
I think it lags because recent button is also for menu button
Sent from my LG-D850 using XDA Premium 4 mobile app
DforDesign said:
Nit present on my nexus 5 and it happens all the time. Even if I click it again and again.
Click to expand...
Click to collapse
It may be due to the g3 recents menu needing larger thumbnails than on aosp (to allow the resizing funtionality on the g3). Not sure if anything can be done at the moment, but back when i had a sgs3 some dev added an option to 'cache recents automatically' which really sped things up. Maybe we will see it on the g3 if development starts to take off.
Related
Is anyone else getting about 0.5 - 1 second stutter before the recent app menu opens?
When I press the button nothing happens and then I feel a vibrate and the menu opens a second later if the menu has more then 5 apps
More or less, yes.
yeah, I get that.. I think it's a thumbnail caching thing.. if you hit home immediately after and then hit it again, it doesn't appear to lag..
Could be wrong, though.
Yes I get this too. Not a problem in my opinion.
Sent from my Galaxy Nexus using xda premium
I've had the phone for two days now and this has happened 3 times now.
The worst one was I got a phone call but the keyboard was up and the back button wasn't there to get rid of it. So I couldn't answer the phone.
One time I couldn't exit the settings menu because the buttons disappeared.
To remedy I turn off the display, turn it back on and unlock to the camera. I think because the camera has the special hidden buttons it causes the phone to refresh the button display otherwise I couldn't find another way to do it.
Has this happened to others? I haven't seen threads about it.
Sent from my Galaxy Nexus using XDA App
I lost them once but got them back by turning the phone sideways and then back upright once the buttons reappeared.
Sent from my Galaxy Nexus using Tapatalk
Oh wow, yea, that would probably work too. But some apps lock to portrait (dialer).
Sent from my Galaxy Nexus using XDA App
Happened to me while I was playing a game (Reckless Gateway) and received a call at the same time. After the call, soft buttons wouldn't appear anymore, had to restart my phone
I have only lost the buttons when flashing a mod that was not compatible...in that situation I did not have the virtual buttons or the notification bar at all.
Never happened to me on stock or rom. What build/android is your phone? You can find info in settings>about phone
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#6
This has happened to me a couple times while using Google Nav. I just pulled down the notification bar and hit the settings button - that seemed to bring the buttons back. Strange issue.
Just a few kinks that need ironing out.. hopefully Google is aware of minor bugs like this already
ericc191 said:
Just a few kinks that need ironing out.. hopefully Google is aware of minor bugs like this already
Click to expand...
Click to collapse
Yep, exactly. Though I wouldn't call this minor because it made me miss a call.
Another thing I just noticed. Go into an app that has the menu virtual button (the three dots) then turn off the screen. Turn it back on and the menu button will be the only virtual button on the Lock Screen. You can press it and automatically unlock the phone. I'm using slide to unlock and the news and weather app to do this every time.
Edit: Just tried with a different lock (pattern) and the menu button will not unlock. But it is still there and you can press it. It just does nothing. Weird.
Hi,
I've decided it's time to root my phone and install Cyanogenmod 10 to get some JB goodness.
However, I'm currently using a case (Incipio NGP) that makes the side unlock button very difficult to press. Because of this, i only use the side button to LOCK the phone, and instead use the physical home button on the front of the phone to UNLOCK it.
What I want to know is, with CM10, will I still be able to unlock the phone using the front physical home button?
I'm going to ignore that fact that using a case that impedes proper use of the phone is just silly.
Do you mean to wake or unlock? The home and power button both wake the phone on CM10. Home button can be a bit hit and miss at this point, but multiple presses resolves this and it will be fixed in the long run.
Exoplanet25 said:
Hi,
I've decided it's time to root my phone and install Cyanogenmod 10 to get some JB goodness.
However, I'm currently using a case (Incipio NGP) that makes the side unlock button very difficult to press. Because of this, i only use the side button to LOCK the phone, and instead use the physical home button on the front of the phone to UNLOCK it.
What I want to know is, with CM10, will I still be able to unlock the phone using the front physical home button?
Click to expand...
Click to collapse
Idk about cm10 but task650 and ktoonsez ROM you can use both buttons to wake. I'd try out AOKP. It is the best ROM out for the S3 in my opinion.
Sent from my SGH-I747 using xda premium
106168 ryionic
TheFiveDots said:
I'm going to ignore that fact that using a case that impedes proper use of the phone is just silly.
Do you mean to wake or unlock? The home and power button both wake the phone on CM10. Home button can be a bit hit and miss at this point, but multiple presses resolves this and it will be fixed in the long run.
Click to expand...
Click to collapse
Hah yeah, might be a little silly but the case is just amazing in every other aspect so I'll deal with a slightly hard to press wake button.
And yes, what I meant was wake, not unlock. So you are saying that if i press the front home button a few times it will wake up and the screen will turn on?
Exoplanet25 said:
Hah yeah, might be a little silly but the case is just amazing in every other aspect so I'll deal with a slightly hard to press wake button.
And yes, what I meant was wake, not unlock. So you are saying that if i press the front home button a few times it will unlock?
Click to expand...
Click to collapse
I'm saying that both CM10 and AOKP work normally with regards to waking the phone like you'd expect when you press the home button. Just like stock.
However, as of right now some people are reporting that it doesn't always respond to the first press. That's just a bug that will certainly be worked out at some point.
The only way the home button is currently working a bit differently is when you have a delay set between the screen off and screen lock. My screen locks 1 minute after it goes off, but if you use the home button to wake the phone during this time, it will wake, but also close any app you have open.
TheFiveDots said:
The only way the home button is currently working a bit differently is when you have a delay set between the screen off and screen lock. My screen locks 1 minute after it goes off, but if you use the home button to wake the phone during this time, it will wake, but also close any app you have open.
Click to expand...
Click to collapse
That's pretty sketchy - I use a 30minute delay so I guess I'd have to take that off. Why is it that AOKP and CM10 both have the same bug - is it just a bug inherent to AOSP Jellybean with S3 hardware?
Exoplanet25 said:
That's pretty sketchy - I use a 30minute delay so I guess I'd have to take that off. Why is it that AOKP and CM10 both have the same bug - is it just a bug inherent to AOSP Jellybean with S3 hardware?
Click to expand...
Click to collapse
Well, "sketchy" isn't the word I'd use, but it is a bit frustrating.
AOKP is built off CM10 for the most part. CM10 is still in the very initial stages on the S3 and the concentration has been on improving graphic and audio performance as a priority.
TheFiveDots said:
Well, "sketchy" isn't the word I'd use, but it is a bit frustrating.
AOKP is built off CM10 for the most part. CM10 is still in the very initial stages on the S3 and the concentration has been on improving graphic and audio performance as a priority.
Click to expand...
Click to collapse
Good to know, thanks.
The main things I need to work are:
calling
texting
mp3 player
Do the audio performance bug affect the google play music app (or music playback in general)?
Exoplanet25 said:
Good to know, thanks.
The main things I need to work are:
calling
texting
mp3 player
Do the audio performance bug affect the google play music app (or music playback in general)?
Click to expand...
Click to collapse
The audio bugs were related to call audio and have largely been resolved in the latest nightlies.
As for texting, it works. Though there are two outstanding issues that may or may not impact you. 1) Concatenated SMS messages do not work, messages are split at 160 characters. Using an alternative SMS app is not a solution, as messages not split will fail to send. 2) Queueing messages in the stock app is annoying, and if one is attempting to send while you send another, it will fail instead of just getting in line.
Hello,
I've been using my new note 2 for two weeks now.. and I like it so much
I also used sgs2 and 3 before.
I'm not new to android.. I flashed roms, know every single setting in the device, rooted my sgs2 and tried lots of apps to customize them.
Regarding my issue, I like to set my device to none screen security because I always manually lock it with a press on the lock screen button after I do whatever I want to do with it, and to unlock I always press Home button to get back to where I was immediately without the need to swipe the lock screen.
The problem is when I lock it and there is an app running and then press the home button the screen goes to home default screen and do not just unlock the screen and keep it there where I was last, this was not the case with my sgs2 or sgs3.
If I press the lock screen button instead it does what I want but I prefer to use home button because its much easier.
Its not a big issue but its annoying sometimes because sometimes I get popup notification windows while the phone is locked (whatsapp for example) and I press the home button to see it and instead of just turning on the screen to see the window it goes back to home screen and the popup is gone, or in cases where I'am writing an email or reading something and meanwhile talking to somebody, if the screen gets locked, If I press the home button everything is gone. So I have to switch tasks to open my activity again.
I don't know if this is a jellybean issue or hardware (homebutton).
I know its not a big deal but I would appreciate if somebody can help get around this
Sent from my GT-N7100 using xda premium
It seems to be a jellybean feature no way around unless a mod comes out...
All jellybean roms in Note I had this feature and i remember seeing this thing on SGS III jellybean too
Just install the S Voice app , "voicetalk_NLI.apk".
In S Voice, set "double click active S Voice" will fix the issue.
This actually worked! Thanks
But the problem is that i use another app (home2) to control home button which makes me able to control what app runs when double clicking home or even use a combination of home with back or menu.
Its a very good app if you want to try it.
This leaves me with trying to deal with my original issue tho or just return to old factory setting
Sent from my GT-N7100 using xda premium
ghellxh said:
Just install the S Voice app , "voicetalk_NLI.apk".
In S Voice, set "double click active S Voice" will fix the issue.
Click to expand...
Click to collapse
thanks man! used to annoy me so much having to open the app again
edit. There's one slight problem, now it lags a bit to return back to the home screen..
I just got a HTC10 to upgrade from the M9 I had, and so far, I'm liking it, even with the stock ROM (but rooted with Sprint bloatware frozen), but one thing I haven't been able to figure out is the home/fingerprint button behavior. If I'm at the home screen and I press it, I don't have a huge issue with it bringing up all the screens for me to pick which one I want (but long press for it would be better), but I find it annoying that when I am in an app and press it, it takes be to the screen where I have to select which page I want, rather than to the last one I was on. Is there a way that I am overlooking to change this behavior?
SubnetMask said:
I just got a HTC10 to upgrade from the M9 I had, and so far, I'm liking it, even with the stock ROM (but rooted with Sprint bloatware frozen), but one thing I haven't been able to figure out is the home/fingerprint button behavior. If I'm at the home screen and I press it, I don't have a huge issue with it bringing up all the screens for me to pick which one I want (but long press for it would be better), but I find it annoying that when I am in an app and press it, it takes be to the screen where I have to select which page I want, rather than to the last one I was on. Is there a way that I am overlooking to change this behavior?
Click to expand...
Click to collapse
I think you mean the multitask button rather than the home button, and if you double press it it switches back to the previous app.
Tarima said:
I think you mean the multitask button rather than the home button, and if you double press it it switches back to the previous app.
Click to expand...
Click to collapse
I think you are correct... but why why should I have to press the button once to get where I need a few more presses to get where I want or press it once plus still need few more presses to get where I want? Is there any way to change this misbehavior?
I guess you could say my annoyance with this (mis)behavior is related to muscle memory... Every other Android phone I've had would take you to your last 'home' page when you pressed the similar button.. This one is (mis)behaving differently from every other phone I've had... It woudl be really nice to change it.
FWIW, I was finally able to change the behavior of the home/multi-function/fingerprint button - by ditching the HTC ROM for LinageOS 14.1. Better battery life, no sprint junk, seems to run better overall and I can actually assign different ringtones or sounds to different contacts. For whatever reason, that option seemed to be absent on the HTC ROM.
I still don't get what behavior you mean? Or do you mean that when you press the home button you are taken to the standard home screen, instead of for example the app drawer or another home screen page? Quite confusing what you mean
Sent from my HTC 10 using XDA Labs