Database Info

Galaxy S3 - Jelly Bean Update - Home Button Bug

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,

Lock mode bug!

I have tested the following problem on several Samsung galaxy phones including J7, J5, A7 2016 edition all running marshmallow 6.0.1. In all of them the following problem persists:
While watching video with screen lock turned on, touching the back button doesn't do anything which is fine as it is not supposed to respond while in locked mode. But the other two buttons which are home button and the right side button for open apps will respond even on screen lock mode. pressing them in locked mode will unlock the locked mode in mx player. touching the recent apps button will open recent apps even in locked mode and pressing the home button in locked mode goes to home. it is in an annoying bug as in locked mode no key should respond. Does anyone else have the same problem? i tested in lollipop and it is fine there. the problem only exists in marshmallow - at least on the above model phones.
Basically the problem is the lock mode doesn't work for home button and left soft key while it works for right soft key which is back key. Any solutions guys, or anyone working on bug fix.? Please respond.

cosmos4all said:
I have tested the following problem on several Samsung galaxy phones including J7, J5, A7 2016 edition all running marshmallow 6.0.1. In all of them the following problem persists:
While watching video with screen lock turned on, touching the back button doesn't do anything which is fine as it is not supposed to respond while in locked mode. But the other two buttons which are home button and the right side button for open apps will respond even on screen lock mode. pressing them in locked mode will unlock the locked mode in mx player. touching the recent apps button will open recent apps even in locked mode and pressing the home button in locked mode goes to home. it is in an annoying bug as in locked mode no key should respond. Does anyone else have the same problem? i tested in lollipop and it is fine there. the problem only exists in marshmallow - at least on the above model phones.
Basically the problem is the lock mode doesn't work for home button and left soft key while it works for right soft key which is back key. Any solutions guys, or anyone working on bug fix.? Please respond.
Click to expand...
Click to collapse
Yes same problem have tried all lock mode

cosmos4all said:
I have tested the following problem on several Samsung galaxy phones including J7, J5, A7 2016 edition all running marshmallow 6.0.1. In all of them the following problem persists:
While watching video with screen lock turned on, touching the back button doesn't do anything which is fine as it is not supposed to respond while in locked mode. But the other two buttons which are home button and the right side button for open apps will respond even on screen lock mode. pressing them in locked mode will unlock the locked mode in mx player. touching the recent apps button will open recent apps even in locked mode and pressing the home button in locked mode goes to home. it is in an annoying bug as in locked mode no key should respond. Does anyone else have the same problem? i tested in lollipop and it is fine there. the problem only exists in marshmallow - at least on the above model phones.
Basically the problem is the lock mode doesn't work for home button and left soft key while it works for right soft key which is back key. Any solutions guys, or anyone working on bug fix.? Please respond.
Click to expand...
Click to collapse
dhruvdave said:
Yes same problem have tried all lock mode
Click to expand...
Click to collapse
It's not a bug actually. Android doesn't allow to lock everything until or unless device administrator permission is granted. As far as I know, it will be dangerous when MX keeps on crash. There won't be a way to unlock the device.
In MX Player, it's using android loopholes to lock the device & inputs. But, third party application can't lock all hardware keys.In recent android versions, google has restricted furthermore. So, it will also affect the efficiency of the locking. I have already discussed with the MX Player developer. But, it's less likely to be fixed since it's an android restriction.
Sent from my Samsung Galaxy S5 using XDA Labs

ktsamy said:
It's not a bug actually. Android doesn't allow to lock everything until or unless device administrator permission is granted. As far as I know, it will be dangerous when MX keeps on crash. There won't be a way to unlock the device.
In MX Player, it's using android loopholes to lock the device & inputs. But, third party application can't lock all hardware keys.In recent android versions, google has restricted furthermore. So, it will also affect the efficiency of the locking. I have already discussed with the MX Player developer. But, it's less likely to be fixed since it's an android restriction.
Sent from my Samsung Galaxy S5 using XDA Labs
Click to expand...
Click to collapse
Thanks I understand

Good to know...
Too bad there will probably be no fix as it is android restriction. many thanks to ktsamy for prompt reply. the problem is specifically annoying with kids around. I still hope there is some way out...!
QUOTE=ktsamy;67880658]It's not a bug actually. Android doesn't allow to lock everything until or unless device administrator permission is granted. As far as I know, it will be dangerous when MX keeps on crash. There won't be a way to unlock the device.
In MX Player, it's using android loopholes to lock the device & inputs. But, third party application can't lock all hardware keys.In recent android versions, google has restricted furthermore. So, it will also affect the efficiency of the locking. I have already discussed with the MX Player developer. But, it's less likely to be fixed since it's an android restriction.
Sent from my Samsung Galaxy S5 using XDA Labs[/QUOTE]

Bixby hardware button not working

So far we have established one thing.. Bixby is not ready for the prime time.
However, I have completely different but relevant issue with it.
Trying to launch Bixby with the dedicated hardware button doesn't work at times. It's hit or miss.. Sometimes it works.. Sometimes it doesn't!
Anyone has this problem??
PS: I tried the earlier remap workaround and facing this ever since.

Same here. Did you do the update. After I did the update for verizon it seemed to start doing it.

I think it was after the update.. Not sure what causes this but it is annoying for sure..
Take it as a gods sign.. Bixby not working even if you want it to. Lol

Mine was not working at all, then it worked occasionally and now it's working 100%. It seems you just have to warm it up a little

UK version here and I hate the flippin Bixby but the button works every time i accidentally press it lol

rohit.sadhwani said:
So far we have established one thing.. Bixby is not ready for the prime time.
However, I have completely different but relevant issue with it.
Trying to launch Bixby with the dedicated hardware button doesn't work at times. It's hit or miss.. Sometimes it works.. Sometimes it doesn't!
Anyone has this problem??
PS: I tried the earlier remap workaround and facing this ever since.
Click to expand...
Click to collapse
I have another thread going on this, but a lot of us are facing the same issue after the update. I've reset my phone entirely and set it up with a clean install, but it still happens. Samsungs fix for stopping the remap is probably the cause of this issue.

just updated mine on sprint and now I have to double press the button for it to work.. single press or long press doesn't work but everytime a quick double press works.

Oawi said:
just updated mine on sprint and now I have to double press the button for it to work.. single press or long press doesn't work but everytime a quick double press works.
Click to expand...
Click to collapse
Exact same issue I have after Verizon ota
Sent from my SM-G955U using Tapatalk

I have noticed that it always works if i press it really really quick. If i leave the button pressed for half a second it wont work. Either click it really fast or just double click.

Same issue here after the update
Sent from my SM-G955U using Tapatalk

Don't know whose all aware of out but bxactions is back up and running with an updated version for the update. It only lets you remap it to one thing instead of 3 now, but still better than Bixby

bagged00 said:
Don't know whose all aware of out but bxactions is back up and running with an updated version for the update. It only lets you remap it to one thing instead of 3 now, but still better than Bixby
Click to expand...
Click to collapse
Does it open Bixby then launch the app you choose? Nope it does not but the like a 5 sec delay for me to Launch google now
Sent from my SM-G955U using Tapatalk

dogredwing1 said:
Does it open Bixby then launch the app you choose? Nope it does not but the like a 5 sec delay for me to Launch google now
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
I got mine set to messages cause I dont use any assistants. I have to double tap and it opens my messages right up

bagged00 said:
Don't know whose all aware of out but bxactions is back up and running with an updated version for the update. It only lets you remap it to one thing instead of 3 now, but still better than Bixby
Click to expand...
Click to collapse
But it is still a double tap after the update ugh this is weird
Sent from my SM-G955U using Tapatalk

I'm wondering if the update did this on purpose to keep people from accidently hitting the Bixby buttin in stead of volume button and then would pull up Bixby when all you wanted to do was mess with the volume. I know I've done that a few times.

Try too double press the button...

Same here, what a joke.

I had to double tap all the time to get it out. I like it that way as it stops accidental presses for me lol
Sent from my SM-G955U using Tapatalk

It's just that the button time is like 0.00005 of a sec before it thinks it's a long press and does nothing.
Fix is just a very quick tap of the button makes it function every time ... All the time ?

The new T-Mobile fixed the tapping for me.
Sent from my SM-G955U using Tapatalk

Screen Wake Issue

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.

Camera bypasses security

when you activate the camera on a locked phone and hit the back button it takes you to the home screen without asking for pin or fingerprint. Anyone can reproduce the issue?

elfodd said:
when you activate the camera on a locked phone and hit the back button it takes you to the home screen without asking for pin or fingerprint. Anyone can reproduce the issue?
Click to expand...
Click to collapse
Not mine, back to lockscreen.
Using full screen gestures, no physical buttons.

I also get sent back to the lockscreen

Have you updated to the latest firmware? I'm also running Nova launcher if it changes anything. It takes me back to the last used screen not to the home screen.

Also not working for me
EDIT: I'm using stock launcher with google feed. Might be nova launcher then

elfodd said:
when you activate the camera on a locked phone and hit the back button it takes you to the home screen without asking for pin or fingerprint. Anyone can reproduce the issue?
Click to expand...
Click to collapse
do u use smart lock?

On body detection and voice. No location or devices.

I've just disabled the body detection and it solved the issue.