I've been reading / hearing about the home key lag. Anybody else experiencing this issue?
Sent from my XT1058 using XDA Free mobile app
Solved by turning off the home button double tap to open recent apps. Its basically waiting for a second tap.
Sent from my XT1032 using XDA Premium 4 mobile app
CM has fixed this issue already. It was merged in gerrit a few days ago.
EDIT: Source here: http://review.cyanogenmod.org/#/c/64352/
Also the above will work until the fix is pushed in an OTA since the issue is related to the home key listening for hard key as well as nav bar responses.
Related
Almost every time I hit the home button from within an app and it goes to my home screen. It has to completely redraw the touchwiz interface. I'm running 100% stock firmware.
I was curious if anyone else was experiencing this problem. I find it very annoying and i feel that since this phone has 2GB of ram it shouldn't be having a problem keeping the home screen loaded while in another app.
Any help would be greatly appreciated. Thanks!
Sent from my SCH-I535 using xda premium
I'm confused on what exactly your asking. If course if you hit the home button it's going to go to your home screen. If you're talking about your recent apps, hold the home button then you have plenty of apps to choose from.
Sent from my Cocaine White S3.
Op. For s voice, do you have it set to activate with a double tap of the home key? If you do then that is y get the redraw. S voice is waiting for a second tap to see if it need to activate or just go home. Turn that feature off and it will be snappier
Edit. OK. I see what u mean. Do u have forced 2d hardware acceleration enabled in the development setting?
Sent from my SCH-I535 using xda app-developers app
justin94 said:
Op. For s voice, do you have it set to activate with a double tap of the home key? If you do then that is y get the redraw. S voice is waiting for a second tap to see if it need to activate or just go home. Turn that feature off and it will be snappier
Edit. OK. I see what u mean. Do u have forced 2d hardware acceleration enabled in the development setting?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yes I do, i thought that may be the culprit but i wanted to see input from elsewhere. Should I disable that?
Sent from my SCH-I535 using xda premium
Yes. At the least the 2d thing. The home key to go back to the home screen is a personal preference. I use s voice alot so I like to be able to access it right away
Sent from my SCH-I535 using xda app-developers app
I know what he is talking about. It is the amount of time it takes to get to the home screen when you are in a app. It does take a sec to long to get to the home screen.
Sent from my SCH-I535 using xda premium
I know exactly what you're talking about OP, I have the same issue for a while now, and coincidentally I did some research on this just yesterday and found a couple solutions you might be interested in trying:
Solution #1
Solution #2
Solution #3
Solution #4
I skimmed through the solutions and i didn't see the one i believed i helped a friend with. He has the same issue and he had power saving turned on. Once he disabled it, i want to say it was resolved along with other issues. Try this and maybe activate it again and try running one off at a time to see what one it is. Its been a few weeks at least since i talked with the person. Not sure if you have it on or off.
If none of these other solutions work...are you really tied to using the touchwiz launcher? I know launchers like nova and apex give you the option to force the launcher to remain in memory to prevent excessive redraws.
Personally, changing the double tap S memo option made everything a little faster for me.
I keep getting a maps not responding error if I am using the navigation app and while I'm in it, change my destination or hit the start button. I know the obvious answer is well don't change your destination but if I accidentally hit back I have to select the start button again. It also only seems to happen when I'm traveling. FYI I'm on carbon ROM but I don't think that is the issue. Any suggestions?
Sent from my SCH-I535 using xda app-developers app
macmachine87 said:
I keep getting a maps not responding error if I am using the navigation app and while I'm in it, change my destination or hit the start button. I know the obvious answer is well don't change your destination but if I accidentally hit back I have to select the start button again. It also only seems to happen when I'm traveling. FYI I'm on carbon ROM but I don't think that is the issue. Any suggestions?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Have you tried accessing the application settings and clearing it. Maybe uninstalling and then installing it back. If you use waze or another navigation app does it do the same thing. I myself have switched to copilot as my main navigation app now. Yes it costs but well worth it.
Sent from my GT-P5113 using xda premium
I've only ever noticed this on Liquid, but torch turns on instantly, but only when I'm running LiquidSmooth. Is it possible to get the torch to be instant on other ROMs such as slimBean?
What do you mean instant? Open the app and turn it on, that's Instant? Ha
Sent from my SCH-I535 using xda app-developers app
DubleJayJ said:
I've only ever noticed this on Liquid, but torch turns on instantly, but only when I'm running LiquidSmooth. Is it possible to get the torch to be instant on other ROMs such as slimBean?
Click to expand...
Click to collapse
No, in ROMs there is a slight delay when you turn it on(second or two) but on Liquid as soon as you hit the button it's on.
Sent from my SCH-I535 using xda app-developers app
DubleJayJ said:
No, in ROMs there is a slight delay when you turn it on(second or two) but on Liquid as soon as you hit the button it's on.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So that's his question? To save 1-2 seconds ha
Sent from my SCH-I535 using XDA Premium 4 mobile app
As a developer on a couple simple apps, I know that when the code accesses the camera, it takes that split second extra. Once it has access to the camera (before it releases the camera) you can turn on and off the torch, and it is "instant".
One way to code the torch app is to either have the camera be accessed in the onCreate method, or when the app first starts, then release the camera in onPause or onDestroy. This will allow you to turn the flash off and on instantly when you are in the app, but the second you leave the app, it will release the camera. If you only release the camera when the app is killed, then if you switch apps to anything else requiring the camera, it will give an error (even if the torch is off), because its already in use with torch, which is one potential downside to this method.
What it sounds like is in the on create method, nothing really happens with the camera. Only if you press the button for the torch will it access the camera, and when you press the button again to turn it off, it will release the camera. Each access of the camera will create a delay, therefore this will be noticeably laggy. However you shouldn't have to worry about other apps accessing the camera, which is nice.
sent from my GS3 running CM10.2
Hey guys just swiped my screen to the left and nothing happened my Google now seems to have disappeared is there something I'm missing is there a way to turn it on and off ?
Sent from my Nexus 5 using xda app-developers app
Go to the app drawer and open the Google search app?
Sent from my Nexus 5
offwiththeface said:
Hey guys just swiped my screen to the left and nothing happened my Google now seems to have disappeared is there something I'm missing is there a way to turn it on and off ?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Long press the home screen --> settings --> there is a switch to activate or not Google Now
Nice find with the long press on homescreen. Hadn't seen that. I just logged out and logged in again.
BTW if you clear the data from search it just reverts all home screens to default and you lose Google Now.
Sent from my Nexus 5 using xda app-developers app
It works some times but recently I'm trying to say OK GOOGLE and it just shows a blank microphone in the search bar. I have to reset my phone and it will work for a short time before stopping.
I would like to not have to factory reset since I have some very important documents photos and other items.
I don't have a computer to back it up to so that's out of the question.
Any ideas ?
Sent from my Nexus 5 using XDA Free mobile app
Bumpo
Sent from my Nexus 5 using XDA Free mobile app
Bumpity bumpo
Sent from my Nexus 5 using XDA Free mobile app
If it crashes you will see a "so and so has stopped working" message on your screen. If the icon is hollowed then Hotword detection is not currently activated. This can happen most commonly when the speaker is outputting any sound so that it doesn't take the speaker output as the microphone input.