Is there an app to disable Home Wake without root? - Samsung Galaxy S7 Active Themes, Apps, and Mods

I've had issues with my home button waking my phone in my pocket, with and without fingerprint enabled (when disabled, it fully unlocks my phone and wrecks havoc.) I know with root, I can disable it via edits to the key profiles. However, with no root, I have scoured the internet for a fix and can't find anything. Does anyone else have this issue and if so, what have you done to deal with it?

darknessrise1234 said:
I've had issues with my home button waking my phone in my pocket, with and without fingerprint enabled (when disabled, it fully unlocks my phone and wrecks havoc.) I know with root, I can disable it via edits to the key profiles. However, with no root, I have scoured the internet for a fix and can't find anything. Does anyone else have this issue and if so, what have you done to deal with it?
Click to expand...
Click to collapse
I have this issue too. Thinking about rooting the phone.

I have the same issue, if you find any solution without rooting let me know

store/app/flar2.homebutton"]https://labs.xda-developers.com/store/app/flar2.homebutton[/URL][/SIZE]
---------- Post added at 08:00 AM ---------- Previous post was at 07:56 AM ----------
darknessrise1234 said:
I've had issues with my home button waking my phone in my pocket, with and without fingerprint enabled (when disabled, it fully unlocks my phone and wrecks havoc.) I know with root, I can disable it via edits to the key profiles. However, with no root, I have scoured the internet for a fix and can't find anything. Does anyone else have this issue and if so, what have you done to deal with it?
Click to expand...
Click to collapse
https://labs.xda-developers.com/store/app/flar2.homebutton

Related

cannot use headset button after rooting KFHD7

Hi there. My KFHD7 7.4.1 does not regconize headset button after rooted and OTA disabled. Before rooted the headset button worked well. Is there anyone have same issue and know how to fix it ?
leminhngan said:
Hi there. My KFHD7 7.4.1 does not regconize headset button after rooted and OTA disabled. Before rooted the headset button worked well. Is there anyone have same issue and know how to fix it ?
Click to expand...
Click to collapse
I had a similar problem i rooted my kfhd and it became so slow it wouldnt turn on eventully after 30min. it turned on but was so slow when i sided to unlock it took five minutes. I also i tried rerooting without unroot. it worked so i used binary's root like i was unrooted and my kindle was back again. it turned out when i rooted i only had 50% battery and you NEED to have at least 90%. this also fixed any audio issues. Problem solved, it's really simple. Some non-amazon apps put the media volume off, which isn't regulated through the normal settings. I downloaded "Quickmute" from the amazon app store and regulated the media volume that way, so that my speakers started working again.
So don't be afraid of installing non-amazon media apps, just make sure to fix sound problems with quickmute or compareable apps.
---------- Post added at 01:52 PM ---------- Previous post was at 01:46 PM ----------
leminhngan said:
Hi there. My KFHD7 7.4.1 does not regconize headset button after rooted and OTA disabled. Before rooted the headset button worked well. Is there anyone have same issue and know how to fix it ?
Click to expand...
Click to collapse
I can leave an apk if you want?
leminhngan said:
Hi there. My KFHD7 7.4.1 does not regconize headset button after rooted and OTA disabled. Before rooted the headset button worked well. Is there anyone have same issue and know how to fix it ?
Click to expand...
Click to collapse
What third party apps have you installed that allow you to play with system volume (turn the volume up or down onscreen not with the physical buttons). Try to remember all the apps you have installed that you could have changed your sound settings in. If you can think of any app at all (even one you may have uninstalled) reinstall it and change your settings back to normal with whatever app it was and the uninstall the app again. Sounds strange, but I had that happen to me once
CVanB said:
I had a similar problem i rooted my kfhd and it became so slow it wouldnt turn on eventully after 30min. it turned on but was so slow when i sided to unlock it took five minutes. I also i tried rerooting without unroot. it worked so i used binary's root like i was unrooted and my kindle was back again. it turned out when i rooted i only had 50% battery and you NEED to have at least 90%. this also fixed any audio issues. Problem solved, it's really simple. Some non-amazon apps put the media volume off, which isn't regulated through the normal settings. I downloaded "Quickmute" from the amazon app store and regulated the media volume that way, so that my speakers started working again.
So don't be afraid of installing non-amazon media apps, just make sure to fix sound problems with quickmute or compareable apps.
---------- Post added at 01:52 PM ---------- Previous post was at 01:46 PM ----------
I can leave an apk if you want?
Click to expand...
Click to collapse
Thank for your answer! could you send me the apk?
[email protected]
Apk.
leminhngan said:
Thank for your answer! could you send me the apk?
[email protected]
Click to expand...
Click to collapse
I sent you one and I left one hereView attachment com.graycode.quickmute-1.apk
CVanB said:
I sent you one and I left one hereView attachment 2018909
Click to expand...
Click to collapse
Received with thanks, brother!
No prob.
leminhngan said:
Received with thanks, brother!
Click to expand...
Click to collapse
Is your kindle sound working now?

Tap2wake - phone Apk crash

Hi all... I basically have two problems. First of all, I got the Z3C happily rooted... The problems are:
1- Tap2wake simply doesn't work, regardless of how I tap... fast, slow, super fast, thumb, index finger, etc... enable it/ disable it... same issue... refuses to work.
2- I use exDialer for my dialer... It works great (I've been using it for a couple of years)... the problem arises when I miss or reject a call. When this happens, Sony'x Phone apk (forgot the exact name) crashes. I have to acknowledge the notification of the crash and everything continues to work... strange ha?
Any ideas what can be going on? Thanks!
Carlos
Did you uninstall Xperia Home? That will cause the phone app to crash on calls as you describe.
I assume you have the option for tap to wake checked? Possibly you uninstalled something that it needs? Never ran into that particular issue.
Can't comment on issue #2, but T2W works flawless for me in 99.9% of the cases (with firmware .98).
Did you (now it might be too late) check whether both problems were there before you unlocked the BL?
What firmware version are you using?
Thanks.. Yeap. too late... already rooted...
Regarding #1, still doesn't work. Even after unfreezing Xperia home, which indeed fixes #2...
Thanks!!!
Carlos
so I've frozen some apps on the z3c, but I can't quite figure out which one controls the tap2wake function. I've tried the trial and error way (freeze/unfreeze), but can't narrow it down. Any of you have any ideas which apk controls that?
Thanks again!!
Carlos
Chaleman said:
so I've frozen some apps on the z3c, but I can't quite figure out which one controls the tap2wake function. I've tried the trial and error way (freeze/unfreeze), but can't narrow it down. Any of you have any ideas which apk controls that?
Thanks again!!
Carlos
Click to expand...
Click to collapse
You can just turn it off in Display settings.
Kev1000000 said:
You can just turn it off in Display settings.
Click to expand...
Click to collapse
Thanks Kev. What I ment to say is that I want to be able to ENABLE it... I have it ticked on, but since I froze some APKs, it's not working. I wish to know if anyone knows which one is it to unfreeze it (if that's the case). I've tried but I havent been able to figure it out.
Best regards,
Carlos

Superuser issue

So after swapping my phone at AT&T I went home to unlock and root my phone. After I unlocked it and restored it I was able to turn Greenify on under Accessibility. After that I rooted and that's when I started having problems. When the dialog box for Superuser comes up I can't click on anything. I can't accept, I can't deny, I can't change the time. Nothing. I went into Accessibility to turn Lightflow on and I can't do it. I can click on Cancel after hitting the slider to turn it on but it won't let me hit the Ok. This holds true for any app listsed in Accessibility. Has anyone come across this before? I rooted with Wug's NRT
jaysmiff said:
So after swapping my phone at AT&T I went home to unlock and root my phone. After I unlocked it and restored it I was able to turn Greenify on under Accessibility. After that I rooted and that's when I started having problems. When the dialog box for Superuser comes up I can't click on anything. I can't accept, I can't deny, I can't change the time. Nothing. I went into Accessibility to turn Lightflow on and I can't do it. I can click on Cancel after hitting the slider to turn it on but it won't let me hit the Ok. This holds true for any app listsed in Accessibility. Has anyone come across this before? I rooted with Wug's NRT
Click to expand...
Click to collapse
Do you have any apps that alter the display? One I've heard of that causes issues is Lux. The filters cause an issue that prevents being able to make screen selections in some cases.
KB112 said:
Do you have any apps that alter the display? One I've heard of that causes issues is Lux. The filters cause an issue that prevents being able to make screen selections in some cases.
Click to expand...
Click to collapse
Wow uninstalling Lux fixed it. Thanks for the help!
jaysmiff said:
Wow uninstalling Lux fixed it. Thanks for the help!
Click to expand...
Click to collapse
How about clicking a thanks on the app too.
Glad that solved your issue though.

To update to MM or to not

Well the update finally hit and now I'm looking for anybody who is using it to share their experience(s). I'm scarred by the G3 update to Lollipop which basically broke the phone but that's another story. Does anybody know of a known bug list or anything like that which is being compiled?
Cheers
I like it. Haven't ran into any problems yet. I didn't OTA. I downloaded the firmware, factory reset my phone, then flashed via Odin.
Im running it for 2 days now, rooted and viper4android working. I love it. Battery life is good, Deep sleeps like it should. Very snappy and they made some minor changes to the UI. Just waiting on a fully compatible kernel now
---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------
troby86 said:
I like it. Haven't ran into any problems yet. I didn't OTA. I downloaded the firmware, factory reset my phone, then flashed via Odin.
Click to expand...
Click to collapse
I did the same, some say dont but i like change and this one is a good change
I just flashed the stock T-Mobile 6.0 firmware this morning. One change that annoys me is the swipe to unlock screen. I use pattern to unlock my phone. On 6.0 I get this screen before I can input my pattern, so it is an unnecessary extra step to unlock my phone. Very annoying.
I updated about two days ago, so far I like it a lot. My device seems to be running a lot smoother than before. Feels much better to me.
Sent from my SM-G925T using XDA-Developers mobile app
HKSpeed said:
I just flashed the stock T-Mobile 6.0 firmware this morning. One change that annoys me is the swipe to unlock screen. I use pattern to unlock my phone. On 6.0 I get this screen before I can input my pattern, so it is an unnecessary extra step to unlock my phone. Very annoying.
Click to expand...
Click to collapse
Wait till you use fingerprints to unlock the device, they have updated some security policy so they need secondary unlock method along with fingerprint to unlock the phone, that's very very annoying.. thinking of replacing fingerprint lock all together
soumik shah said:
Wait till you use fingerprints to unlock the device, they have updated some security policy so they need secondary unlock method along with fingerprint to unlock the phone, that's very very annoying.. thinking of replacing fingerprint lock all together
Click to expand...
Click to collapse
Ummm...no. The secondary unlock is a backup for the fingerprints. You don't have to do both to unlock the phone. Just verified, turned the screen on, and held my finger in place...boom, unlocked.
Just when you restart the phone you need to put the secondary unlock method.
Phone is very fluid and I love it, best update i had in a phone in a long time.
Just 1 thing and I bet you'll like it.
No more laggy.
Sent from my SM-G920T using XDA-Developers mobile app
Wow first time I've seen a SW push on a phone that everybody seems to be pretty satisfied with lol. I took the plunge this morning and noticed the secondary password for fingerprints as well. However I know that's always been there as a back up and for whatever reason it had to be reset on the first boot but it's gone away now and is only a back up when it doesn't recognize my fingerprint more than three times. So far so good, I'm curious to see if there is any improvement on the battery life or not.
Thanks for the info everybody!
After I updated my phone to 6.0.1, I did a factory reset. I couldn't be happier. I use fingerprint unlock and have my phone encrypted. Since the release (4/11), I haven't had any issues with battery or performance. I did notice that the auto-brightness seems to be more aggressive than Lollipop. One issue I didn't like was that when I used All-In-One-Gesture to enable double-tap to sleep, I had to manually type my password every time to unlock the phone. I think because of my security settings (allowing an app to have permission to lock the screen), I wasn't able to fingerprint unlock unless I manually turned off the screen using the power button. Otherwise, I don't mind entering a long password every time I turn on the phone.
In standby, my phone would drain 15%-20% over 8 hours each night while I slept. With MM, my phone drains less than 5% each night now.
Anyone having problems with LED notifcations not working? It works when I'm charging, but not any other time. It is turned on in settings>display. I also made sure notifications settings for my apps were not blocked. Weird. So far I'm unimpressed by MM. Alot of things don't work right, like LED notifications The battery improvement is negligible. I was getting 5% battery loss overnight anyway. I didn't do a factory reset before/after upgrading. Maybe that will fix my problems.
Update: I fixed the LED notification by doing a factory reset in recovery. Now I have to reinstall everything . My phone is stock by the way.
it works pretty good all around ui is smooth it has a refined feel compared to the older updates
Sent from my SM-G920T using XDA-Developers mobile app
Battery life has been MUCH better for me.
Rooted+ Xposed. I even disabled the location wakelock module I HAD to use in LP, and it's still much better. SOT isn't really effected much, but screen off + listening to streaming music has more than halves battery usage for me, along with idle time.
Tthe phone is much smoother, and I have not experienced any lagging (have animations turned off, though). Plus, finger print unlock is tons faster. LP always lagged hard for me there, now it's almost as fast as the wife's 6s+.
I got a small issue with unlock function.
If I made screen of my hard button, I could use fingerprint to unlock the screen, but if I used 3rd-app to make screen off, I need to use back up method - PIN to unlock the screen.
Does anyone face the same issue?
Received the OTA update. I'm on stock.
Battery life is *slightly* better, but it's nothing to write home about.
The auto-brightness has been updated, and I feel it's not for the better. It seems to dim/brighten aggressively, and/or not work at all. It's been irritating.
trungctu said:
I got a small issue with unlock function.
If I made screen of my hard button, I could use fingerprint to unlock the screen, but if I used 3rd-app to make screen off, I need to use back up method - PIN to unlock the screen.
Does anyone face the same issue?
Click to expand...
Click to collapse
I have that problem too. I forget which security setting it is, but basically it requires you to enter your password whenever an app locks the screen. I don't think there is any way around it. I uninstalled all my apps that lock the screen, except greenify, for that reason.
drbongles44 said:
I have that problem too. I forget which security setting it is, but basically it requires you to enter your password whenever an app locks the screen. I don't think there is any way around it. I uninstalled all my apps that lock the screen, except greenify, for that reason.
Click to expand...
Click to collapse
Me too... back to stock "easy touch" and wait for next update...
Sent from my SM-G920T using Tapatalk
Great update
If you stick with the stock marshmallow update I think you will be happy. You are able to root it also without a problem.
If you make sure NFC and WiFi are turned off (When you're not using them) I personally have seen better battery usage than Lollipop.
I'm running the stock rooted marshmallow and it really is a beautiful update with a bunch of enhanced features. I would recommend.
As a bonus, it also gives your phone a radio update (which allows it to better contact T-mobile's towers).
If you really want a boost in speed, you should lookup changing your APN settings to force your phone into IPv4, because currently your phone will default to IPv6 which (at least for me) is a tad slower than IPv4.
Good luck and have fun messing around with the new update
HKSpeed said:
I just flashed the stock T-Mobile 6.0 firmware this morning. One change that annoys me is the swipe to unlock screen. I use pattern to unlock my phone. On 6.0 I get this screen before I can input my pattern, so it is an unnecessary extra step to unlock my phone. Very annoying.
Click to expand...
Click to collapse
yeah I'm with you on that.
Another thing that is annoying me, and maybe there is a setting to turn this off (if so please tell me as I've not yet found or really looked into it yet)...
It used to be that when I opened a link it would prompt me which browser or or program I wanted it to open with. I actually like being prompted each time because sometimes I want this a bit more secure and so would open with Orweb vs. Google.
Now it seems that once I select and option it becomes the default option until I go in and change it.
Otherwise, I'm enjoying it. I'm rooted running xposed and viper etc.
I really do want my gradient status bar back though...

Frozen screen after waking up screen

At some point after upgrading to Android 9 I started having the following issue where if the screen turns off due to inactivity and I turn it back on by pressing the power button, I see whatever screen I had open before it went to sleep but it's frozen. Scrolling touching etc still perform (invisible) actions but the screen is frozen until I either press the app switch button or perform some action that would change the current application. While the screen is frozen the drawer from the top works just fine. Also when the app that gets frozen is the desktop (I'm using the default launcher), I can see the background scrolling if I swipe left or right but the widgets don't change, they are frozen.
Does anyone else have the same problem? Any ideas what could be causing it?
Tritonio_GR said:
At some point after upgrading to Android 9 I started having the following issue where if the screen turns off due to inactivity and I turn it back on by pressing the power button, I see whatever screen I had open before it went to sleep but it's frozen. Scrolling touching etc still perform (invisible) actions but the screen is frozen until I either press the app switch button or perform some action that would change the current application. While the screen is frozen the drawer from the top works just fine. Also when the app that gets frozen is the desktop (I'm using the default launcher), I can see the background scrolling if I swipe left or right but the widgets don't change, they are frozen.
Does anyone else have the same problem? Any ideas what could be causing it?
Click to expand...
Click to collapse
FWIW I have not really solved the problem but I am circumventing it by having the screen lock immediately instead of waiting 5 minutes. That way I have to unlock with a fingerprint every time the screen is off, and unlocking refreshes the screen which "fixes" the problem.
Tritonio_GR said:
FWIW I have not really solved the problem but I am circumventing it by having the screen lock immediately instead of waiting 5 minutes. That way I have to unlock with a fingerprint every time the screen is off, and unlocking refreshes the screen which "fixes" the problem.
Click to expand...
Click to collapse
There were lot of reports of glitchy phones after the Pie update.
The cure was a factory reset or software repair with Xperia Companion
Use Xperia Transfer to back up your calls/contacts/texts before you reset the phone
Didgesteve said:
There were lot of reports of glitchy phones after the Pie update.
The cure was a factory reset
Click to expand...
Click to collapse
Can you please link a thread, where users told, that problem is solved after reset?
I have the same frozen display (since Android Pie), when turning display off and on again.
Don´t wish to reset and install all again, if that does not help.
bye,
Ralf
thegrobi said:
Can you please link a thread, where users told, that problem is solved after reset?
I have the same frozen display (since Android Pie), when turning display off and on again.
Don´t wish to reset and install all again, if that does not help.
bye,
Ralf
Click to expand...
Click to collapse
Hi Ralf,
the phone will always work better with a reset after a major update, all the Oreo applications are trying to work under Pie. Sometimes it works, sometimes it doesn't. Oreo apps aren't made to work under Pie and they can error.
here, is one example, or another, but I didn't jump to Pie because of all the negative feedback and the scores of people trying to downgrade.
A reset will fix your problem and if you use Xperia transfer then the amount of personal information lost will be minimal.
Thanks for the links.
Didgesteve said:
all the Oreo applications are trying to work under Pie. Sometimes it works, sometimes it doesn't. Oreo apps aren't made to work under Pie and they can error.
Click to expand...
Click to collapse
This sounds to me, the combination of "old" Navi-apps with Pie is the problem. May be only with Pie on some Sonys.
I'm afraid, a reset will not change the frozen display.
All other apps till now do not freeze after display-on except MagicEarth and Osmand+
This 2 apps i deinstalled (+ deleting the data) and installed again.
A reset will fix your problem and if you use Xperia transfer then the amount of personal information lost will be minimal.
Click to expand...
Click to collapse
Xperia transfer shows me only 2 apps for backup.
I'll probably try a reset in the next few days anyway.
bye,
Ralf
thegrobi said:
Thanks for the links.
This sounds to me, the combination of "old" Navi-apps with Pie is the problem. May be only with Pie on some Sonys.
I'm afraid, a reset will not change the frozen display.
All other apps till now do not freeze after display-on except MagicEarth and Osmand+
This 2 apps i deinstalled (+ deleting the data) and installed again.
Xperia transfer shows me only 2 apps for backup.
I'll probably try a reset in the next few days anyway.
bye,
Ralf
Click to expand...
Click to collapse
Looks like there is know issue with the Osmand+, the date of the post is may last year, but it may just be a 'feature'
When backing up with Xperia transfer, make sure you select all the boxes that are optional. It's things like text messages/contacts/phone history that are useful after a reset. Some apps can't be moved and have to be downloaded directly from the playstore, but Google should give you that option, after you log back in to the wiped phone.
Edit: I can recomend Sygic, free maps for one country, works without data.
In the meantime, I found more users with this problem and a little solution that another user describes:
I can confirm I have the exact same issue since Android 9 with my Xperia xz1 compact.
I normally have no lockscreen options set. So when I wakeup the Phone, it sometimes kind of 'locks' the screen. Widgets do not respond, I cannot switch home screens. The time on the status bar remains correct. If I then click on an app and go back, everythning behaves normally.
So I'm quite sure this must be a software issue, as other people have this problem to.
My workaround for now is to have a lockscreen option aktive. But I would rather have not, for conveniance.
I tested this also with safe mode and complete factory reset of the phone. The 'bug' is still there.
Click to expand...
Click to collapse
If I disable lockscreen, then apps stop when it is switched on again. However, I always have to enter pin or use fingerprint sensor, or smart lock.
This often does not work when cycling and is dangerous when cardriving.
On Android 8, the lockscreen did not need to be active.
So the problem is not Osmand and MagicEarth.
It is a Sony 9 bug with Android 9.
bye,
Ralf
Found in an other forum an easy method to reproduce the problem.
disable the screen lock (it must be set to "None");
lock the phone and then unlock it;
lock and unlock it again.
Click to expand...
Click to collapse
bye,
Ralf
---------- Post added at 01:50 PM ---------- Previous post was at 01:20 PM ----------
Because I believe that Sony will not fix the error, I could imagine a solution:
An app (possibly tasker), which puts a selectable running app from foreground while pressing the power button in the background and immediately brings it back to the foreground.
Does anyone know such a tool?
bye,
Ralf
[/COLOR]Because I believe that Sony will not fix the error, I could imagine a solution:
An app (possibly tasker), which puts a selectable running app from foreground while pressing the power button in the background and immediately brings it back to the foreground.
Does anyone know such a tool?
bye,
Ralf[/QUOTE]
So, did you ever find a solution?

Categories

Resources