K, i'm aware there's a old post on this but no one's updated it in seven months. So here's the question again: why is my camera app so slow to launch? And how can I fix it?
I am running rooted stock 2.1-update1.
Baseband 2.1.55.
Kernel 2.6.29 [email protected] #1.
Build 2.1.1.A.0.6
I've turfed much of the bloatware. Does anyone have any (effective, proven) suggestions for speeding up the launching of the stock camera application from the hardware button? Its even slow if the program is running and i've just switched to the homescreen.
Thanks in advance!
Simon
How long? Have you compared it to another camera app? Like a Camera 360 or a Retro Camera or Vignette?
And have you tried installing a Task Manager to see what other apps are running in the background?
Maybe there are a dozen other apps running in the background.
Maybe try clearing cache for the Camera app....go under Settings->Applications and look for the Camera app.
beau420 said:
How long? Have you compared it to another camera app? Like a Camera 360 or a Retro Camera or Vignette?
And have you tried installing a Task Manager to see what other apps are running in the background?
Maybe there are a dozen other apps running in the background.
Maybe try clearing cache for the Camera app....go under Settings->Applications and look for the Camera app.
Click to expand...
Click to collapse
I meant vs opening any other app on the device.
Just task killed - 105m free. pressing hardware button. 10 seconds.
Put camera in the task killer ignore list, cleared the cache, launched went into settings and fixed 'em. out to home screen. hit hardware button. its still almost 10 seconds to launch a native OS app. Conversely, my phone app launches within about 2/3rds of a second from pressing the touchscreen button.
On a whim, i put the camera button on the homescreen. still slightly slow, but faster than the hardware button - does that make any sense? is there some other task i should be ignoring for faster HW button access?
annoyed.
So it is normal when accessed using the Camera app icon in the app list, but the HW camera button on the side is slow.
I think the default Camera app is a lot weaker than Camera360, so I don't use it.
I don't use the camera button.
Anyone else have any suggestions?
There was a stock X10 camera optimization thread a while back.
what he said
you should try installing WolfBreaks rom. for me the native camera launches in 3-4second when i press the hardware button.
Hey guys,
I know next to nothing about modding/dev work, so this may be something completely impossible, and that's cool if it is. Can't know without asking.
I came from the Evo 3D (as I presume a bunch of you did as well), and one of the features I've found myself sorely missing is that blasted search button. I took for granted how convient it was to tap it and look up something really quick, or search through messages/emails/websites for whatever I was looking for.
On Char, using the pkmn tweaks, you can mod the capacitive buttons to open an app, so I had longpress recent apps opening google search, which worked fine for a hacked together solution. But is there anyway to have a mod that would mimic the old dedicated search button function? I.e., when in an application that has a search feature (like Play, Messages, Email, etc.), activation of the button would prompt opening of the search feature. If there's not a search feature, or you're on the home screens, it would prompt standard Google/phone search.
Was also wondering, randomly, if it was possible to have a search box in the pull down notifications? I feel like that'd be harder to implement with the functionality described above, but I think it'd be cool/convient for just quick searches of something if the capacitive buttons are a no go, or people aren't interested in them.
Either way, any of these things possible?
Well, disregard. I found that doing the keylayout remap so that half-pressing the camera button triggers search does the full functionality. Wonder why I couldn't get it to trigger with the capacitive buttons. Oh well!
Sent from my EVO using xda app-developers app
I f*&#ing hate this stock rom! If anyone could tell me how, or if there is a way by disabling a service, to stop the google search popping up when you swipe past the home button or hold it for a second. Aargh!
Install Google Now Launcher or Nova.
Sent from my D5803 using Tapatalk
I have the pro version of nova installed. This has no options to disable this feature
Install Tasker for example. Then if You swipe the home button the popup will show with apps to choose - then choose Tasker (use always) that could do just nothing.
Now if You swipe home button only white circle would appear - that would do nothing.
I should have pointed out that my intention is to stop this circle popping up, so i can use the slimpie controls and disable the navbar completely. I am afraid I am struggling to come to terms with just how limited a stock rom is. Sure I can get root via the sony dev website but at this point I think all the fancy algorithms for camera performance would be removed, as well as throttling for thermal control.
When you Google Search, you find https://play.google.com/store/apps/details?id=hk.sld.SwipeLaunchDisabler
The Irony
I'm using this app to fast lock the screen when I swipe up the home button
https://play.google.com/store/apps/details?id=com.katecca.screenofflock
otherwise you can use this app https://play.google.com/store/apps/details?id=com.dynamicg.homebuttonlauncher
to have more options respect to open google search
Just FYI:
- This is called "Swype up for Google Now" in old Nexus manuals.
- Now in Android 6.0 is replaced for "Google Now on tap".
I don't really know how to disable it.... Maybe trying another Launcher.
Thanks for your input. however the home button launcher will not achieve my goal, and the swipelauncher disabler is comically pointless! It is less a disable function, more so it just doesn't launch my browser, choosing instead to flash the screen at me! It is clear that I will not be sated until custom roms come about with some CM or AOSP goodness. Please hurry devs, I want to love this phone...
I'm a bit late to the party and I'm not sure if this is what you mean, but I've just been disabling some apps on my z5c and one of them was the Google Now app (I think it was called). Because the bubble popping up was from the Google now app, it has stopped appearing ever since. Hope to have helped.
Disable the Google App
Yep remove Google Now or I just tried this and works well (you cannot prevent the animation that will still persists, but the action gets revoked the way you have requested.)
https://play.google.com/store/apps/details?id=com.AdrianCampos.swipeuputility
Button Mapper on the Play Store:
https://play.google.com/store/apps/details?id=flar2.homebutton&hl=en
If your device is rooted, you have complete ability to remap the Bixby Button. You can disable the Bixby assistant, it does not need to be enabled for this to work. There are no compromises with this method. You can get rid of Bixby and program whatever single, double and long press actions you want.
If your device is not rooted, you can still remap Bixby using an experimental method. This method also works with Bixby disabled, and will allow you to map whatever actions you like to a single press or long press. It requires running a command in adb shell once. After this, the Bixby button can be remapped with Button Mapper. A slight inconvenience, but it works.
If you don't like the stuttering that occurs on Samsung devices with certain Accessibility features enabled, got to Advanced Options and select "Remap Bixby only"
Are you using the Accessibility framework to detect keypresses? If so, that does impact scrolling performance. I also am working on a keymapper for BIxby that doesn't use the Accessibility Framework, and it works very well. If you're not using Accessibility, and you don't have any performance impact, I'd be happy to test this out and provide feedback (and probably stop my work)
EDIT: Yep, looks like Accessibility is used here, which kills scrolling performance (lots of stutters) when you listen for keypresses. I shall continue my work.
Kev1000000 said:
Are you using the Accessibility framework to detect keypresses? If so, that does impact scrolling performance. I also am working on a keymapper for BIxby that doesn't use the Accessibility Framework, and it works very well. If you're not using Accessibility, and you don't have any performance impact, I'd be happy to test this out and provide feedback (and probably stop my work)
EDIT: Yep, looks like Accessibility is used here, which kills scrolling performance (lots of stutters) when you listen for keypresses. I shall continue my work.
Click to expand...
Click to collapse
I could do it without accessibility. I'm just piggybacking on accessibility service since the rest of the app uses it.
I wish Samsung would fix that stuttering. It's not even when you listen for key presses, even an empty accessibility service causes that stutter. OnePlus used to have the same issue and they fixed it with a system update.
That's actually not quite true in my testing. The config that causes the slowdown is...
android:canRequestFilterKeyEvents="true"
If you have that enabled, regardless of anything else, it causes stuttering. Setting that to false causes the stuttering to disappear.
Kev1000000 said:
That's actually not quite true in my testing. The config that causes the slowdown is...
android:canRequestFilterKeyEvents="true"
If you have that enabled, regardless of anything else, it causes stuttering. Setting that to false causes the stuttering to disappear.
Click to expand...
Click to collapse
I haven't checked on the latest update, but any accessibility service caused it when I last tested. It was not specific to any setting.
On AQF7 with that flag disabled, all scrolling returns to normal.
does the button remap work when in lockscreen ?
update: Yup, it stutters. even stuttering in Button Mapper setting page.
The stuttering with Accessibility has been there all along. It's not just with the key filter turned on (I am also on AQF7), it's there with bxActions and other accessibility-based apps I've tried that don't filter keys. But you are correct it's not every Accessibility Service. I have an Accessibility service on another app (DevCheck) that does not cause stuttering.
In the end, there's nothing I can do about that stuttering, it will probably be fixed if Samsung updates to Android 7.1.
I would like to focus on the remapping part and how it works. I can make a Bixby remap that doesn't need accessibility, but first I need feedback on how the remap stuff is working. I can't root my S8, so I'm doing this partially blind and I depend on others to test things. The non-root part works perfectly, but is not easy to set up, so I want to see what kinds of problems people run into and fix them before I push this out of beta.
Kev1000000 said:
Are you using the Accessibility framework to detect keypresses? If so, that does impact scrolling performance. I also am working on a keymapper for BIxby that doesn't use the Accessibility Framework, and it works very well. If you're not using Accessibility, and you don't have any performance impact, I'd be happy to test this out and provide feedback (and probably stop my work)
EDIT: Yep, looks like Accessibility is used here, which kills scrolling performance (lots of stutters) when you listen for keypresses. I shall continue my work.
Click to expand...
Click to collapse
Does your method need root?
flar2 said:
Does your method need root?
Click to expand...
Click to collapse
It does, yes. I would prefer your method if you could remove the need for accessibility, for sure.
I tested out as much as I could with your solution. Overall, things seem to work. Single, double, and long press all work. However, it doesn't reliably stay working. After screen off, or launching the camera, etc, it seems to stop working. If I relaunch Button Mapper, it works again.
@OP
Thanks for this.
I signed up so that you can do your work,
but hoping once your testing finished, you'd
remove the "Accessibility"!
samteeee said:
@OP
Thanks for this.
I signed up so that you can do your work,
but hoping once your testing finished, you'd
remove the "Accessibility"!
Click to expand...
Click to collapse
Yes, I'll probably just make a separate app, since everything else in Button Mapper is tied to Accessibility.
That'll be next week though, I'm out of town until next Wednesday.
Kev1000000 said:
It does, yes. I would prefer your method if you could remove the need for accessibility, for sure.
I tested out as much as I could with your solution. Overall, things seem to work. Single, double, and long press all work. However, it doesn't reliably stay working. After screen off, or launching the camera, etc, it seems to stop working. If I relaunch Button Mapper, it works again.
Click to expand...
Click to collapse
Relaunch, as in just opening the app, or do you have to go to the Bixby screen and tap the switch to turn it back on?
Do you have the "Screen off actions" setting enabled or disabled? It's on the Advanced Options screen.
flar2 said:
Yes, I'll probably just make a separate app, since everything else in Button Mapper is tied to Accessibility.
That'll be next week though, I'm out of town until next Wednesday.
Click to expand...
Click to collapse
That'll be awesome, Look forward to beta testing it!
flar2 said:
Relaunch, as in just opening the app, or do you have to go to the Bixby screen and tap the switch to turn it back on?
Do you have the "Screen off actions" setting enabled or disabled? It's on the Advanced Options screen.
Click to expand...
Click to collapse
Just opening the app, and more specifically, a warm launch of the app (the process was still live and not removed from memory).
I didn't adjust the screen off actions, so whatever your defaults are there was what I had set.
Thanks guys, this is the only button mapper which I could use without root, Bixby disabled.
I just pushed version 0.44, with some minor bug fixes and a new option to have smoother scrolling.
This new option can be toggled in Advanced Options->Experimental Options->Remap Bixby only. With this option enabled, you can remap Bixby without suffering from choppy scrolling. However, you will no longer be able to remap the volume buttons (because they require the Accessibility Service settings that cause choppy scrolling on Samsung phones).
Thanks, flar! Working well. Scrolling performance has returned to smooth.
One of the last issues I have is the "open recents" option is fairly slow to execute. I find using Accessibility Service that doesn't capture key events still maintains scrolling performance, but allows super quick "open recents" using Accessibility to call it.
Hmm, with this enabled, my battery life has significantly dropped and the phone is warm to the touch. Have you noticed any increase in battery life with this method? This may have existed before, I just didn't test it long enough to notice.
Hi,
Normally when we press home button of Samsung tab/phone it minimizes all the apps and takes us directly to home screen but for some reason when I press home button on galaxy tab s3 it opens google search and there is no way that I can minimize all apps at once.
can yo help me to change the function of home button.
Thank you.
Did you have any luck finding out how to stop the home button going to goggle assistant instead of home screen? I all of a sudden have the same issue and haven't found a solution on the web
It sounds like your home button might be sticking. Do you feel it snap back immediately after pushing it?
Hope you work it out.
David
Sent from my SM-T827V using Tapatalk
There are several solutions in this thread that seem to have worked.
In order of the easiest:
1. A settings change, changing the delay for the google shortcut.
2. Remove battery (I know, not possible with the S3, but included for any phone users searching)
3. Clear cache
All of these fixes seem to have worked for various users who commented on a given fix. There are a lot of posts on that thread, many of them commenting on the fixes I've listed. I'd try one or more of these first, then read the rest of the thread if no joy.