Database Users

Lock screen and Knock On Solution

Strangely, my phone stopped responding to knock on to wake the screen. When you pressed the hardware power button to wake the screen would immediately close. It would take about 10-15 tries to unlock the screen in that split second before it closed. To troubleshoot I flashed back to factory and I still had the same issue after the phone was allowed to sleep just a few minutes. I took the OTA, same problem.
I was ready to box it up and swap out, but decided to try one other thing. I went to the screen off effect and changed it to Simple. Everything worked fine after that. I switched it back to retro tv and it would take many more tries to wake the screen. apparently its some kind of software bug. Thought I'd pass the info on to anyone else having similar issues.
Apparently root apps that play with system files trigger the bug too, like greenify. So the bug isn't tied to one screen effect, just switching to another fixes it until you play with system files via flashing or root apps. Hopefully it's something they fix in the next update.

It seems if you flash or change any system files, it reverts back to the retro tv effect and the issue repeats until change to another transition.

So the knock on feature is supposed to be more reliable if I do this?

in_dmand said:
So the knock on feature is supposed to be more reliable if I do this?
Click to expand...
Click to collapse
If you are suffering from the same software bug, it works. If you flash a mod or do anything that does a "updating android" on reboot, it reverts back to the default screen effect and the knock on becomes unreliable. After a deep sleep you can't wake it with a knock most of the time. Strange but saved me a trip verizon hell for a swap.

Wow!!! I can totally confirm that this is working! Thank you so much... I was getting to the point that I didn't really use the knock on feature due to the flakiness of it... Now it works flawlessly!

in_dmand said:
Wow!!! I can totally confirm that this is working! Thank you so much... I was getting to the point that I didn't really use the knock on feature due to the flakiness of it... Now it works flawlessly!
Click to expand...
Click to collapse
Glad it helped man. I restored my recovery,reflashed stock and took the ota before i found the bug. lol Works as advertised now.

Im getting the same problem with mine, but the retro screen switch to simple isnt solving the problem. Tsking so many tries and not being able to knock on is making the phone unusable.
Any other suggestions or off to Verizon? Im within the 14 days...
Sent from my GT-N5110 using xda app-developers app

dpaul01 said:
Im getting the same problem with mine, but the retro screen switch to simple isnt solving the problem. Tsking so many tries and not being able to knock on is making the phone unusable.
Any other suggestions or off to Verizon? Im within the 14 days...
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
Make sure the sensor area to the right of the FF camera is clean. If you have a screen protector over it, you might want to pull it off and clean the area really good. If that sensor is blocked or not working, it will do the same thing whether or not you change the screen off settings. Could be a bad sensor and you may need to swap it out.

Tried cleaning it, no luck. Seems like its hw related. Off to vzw I go.
Sent from my GT-N5110 using xda app-developers app

Can confirm this. Disabling retro worked originally, but after rooting and Greenify it's back.
Do I have to flash to stock to fix now? Or will Greenify uninstall do the trick?
Sent from my VS980 4G using XDA Premium 4 mobile app
---------- Post added at 08:28 AM ---------- Previous post was at 08:10 AM ----------
Well, I tested it myself. Uninstalling Greenify does indeed fix the knock-on issue.
A shame, as I really liked that app. Boo Verizon/LG. Boo.....

Damn! I was wrong.
Still having this bug, but only from deep sleep.
Incredibly annoying, but I really don't want to Re flash. Any ideas.
I'm dying here....
Sent from my VS980 4G using XDA Premium 4 mobile app

Greenify or any root program that modifys system files has the possibility of triggering the bug. In my personal testing, after you change the screen off to something different after installing Greenify, it stops. I'm guessing the core issue is with the front sensor that disables knock on. A hardware software combination. Strangely even after flashing back to stock doesn't fix the bug. First deep sleep and it will return until you change that setting in screen off.
Sent from my VS980 4G using XDA Premium 4 mobile app

Flashed back to stock myself and the problem continued. I returned the phone for a new one yesterday (14 days) and for the moment I'm going to keep this one stock until the issue fleshes itself out.
Sent from my GT-N5110 using xda app-developers app

timsterzzz said:
Greenify or any root program that modifys system files has the possibility of triggering the bug. In my personal testing, after you change the screen off to something different after installing Greenify, it stops. I'm guessing the core issue is with the front sensor that disables knock on. A hardware software combination. Strangely even after flashing back to stock doesn't fix the bug. First deep sleep and it will return until you change that setting in screen off.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nothing seems to fully resolve this. Super annoyed I ever installed Greenify. Ugh.
I'm within my 14 days (I got it on Monday), but I purchased from letstalk (the $26 price mistake deal that lasted a few minutes). Does anybody know if I can just walk into Verizon to switch it out, or do I have to do the mail back, wait 5 days with no phone thing?
thanks

I've only replaced the phones I directly received from Verizon in person. Call Verizon and tell them you needed to swap a phone under the 14 days. They can look at your account and tell you if you can just swap it in person or if you need to return through the reseller.
Sent from my VS980 4G using XDA Premium 4 mobile app

I've used greenify for two weeks without this issue ever happening.. maybe I'll freeze it now lol
Sent from my VS980 4G using Tapatalk 4

Maybe it was when we removed the Chinese SU. Secret payload to punish us. Lol
Sent from my VS980 4G using XDA Premium 4 mobile app

wait did you guys all use Chinese superuser?? I flashed back to unrooted stock to get rid of that, then rooted the new way so I wouldn't have any trace of it.
Sent from my VS980 4G using Tapatalk 4

timsterzzz said:
Greenify or any root program that modifys system files has the possibility of triggering the bug. In my personal testing, after you change the screen off to something different after installing Greenify, it stops. I'm guessing the core issue is with the front sensor that disables knock on. A hardware software combination. Strangely even after flashing back to stock doesn't fix the bug. First deep sleep and it will return until you change that setting in screen off.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In theory, Greenify may break such a feature like Knock-on, but its always recoverable. Simply de-greenify the app and manually launch it to restore everything to normal.
Please avoid greenifying any app with background functionality.
PS: Greenify actually never touch any system files.

jayochs said:
wait did you guys all use Chinese superuser?? I flashed back to unrooted stock to get rid of that, then rooted the new way so I wouldn't have any trace of it.
Sent from my VS980 4G using Tapatalk 4
Click to expand...
Click to collapse
No, that was just humor.

Is it just an unstable device?

I've had my note 3 for a few weeks now and having come from an s1, s2, s3 and s4 I'm finding I get fc's and freezes in pretty basic android features.
1. My settings > volume controls froze yesterday
2. the flip board widget wouldn't open the flip board page then hung the phone this morning.
3. just now ending a call froze instead of hanging up, then gave an error procees com.android.phone (or similar) is not responding.
Is this knox messing with stuff or just a buggy stock rom (mj7)?
Obviously a factory reset is the next step but I'm interested to know if anyone else finding their's is doing weird stuff that never happened on previous devices?
Thanks
Sent from my SM-N9005 using XDA Premium 4 mobile app

skibadee said:
I've had my note 3 for a few weeks now and having come from an s1, s2, s3 and s4 I'm finding I get fc's and freezes in pretty basic android features.
1. My settings > volume controls froze yesterday
2. the flip board widget wouldn't open the flip board page then hung the phone this morning.
3. just now ending a call froze instead of hanging up, then gave an error procees com.android.phone (or similar) is not responding.
Is this knox messing with stuff or just a buggy stock rom (mj7)?
Obviously a factory reset is the next step but I'm interested to know if anyone else finding their's is doing weird stuff that never happened on previous devices?
Thanks
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have not had such a bad problem like that with my device, A few crashes here and there (1 a week) but that's to be expected from android..I can from an S2.

Hi,
I've had my N3 since release and no issues even following a few updates. However following a patch I believe it's always good to perform a full wipe and restore, and I think patch 3 or 6 was big! I had no issues with my S2 yet my Father took it on but had to factory wipe even though I'd done the same before handing it over (now works fine).
Hope this helps.
Jonty.
Sent from my SM-N9005 using XDA Premium 4 mobile app

OK thanks, so maybe needs a reset. Never had issues like this after updates on other devices before. Hope its not going to be on a regular basis.
Sent from my SM-N9005 using XDA Premium 4 mobile app

Hopefully just a one-off. I've never had to factory reset yet after an update but the awareness is always there just in case.
Keep us posted?
Jonty.
Sent from my SM-N9005 using XDA Premium 4 mobile app

skibadee said:
I've had my note 3 for a few weeks now and having come from an s1, s2, s3 and s4 I'm finding I get fc's and freezes in pretty basic android features.
1. My settings > volume controls froze yesterday
2. the flip board widget wouldn't open the flip board page then hung the phone this morning.
3. just now ending a call froze instead of hanging up, then gave an error procees com.android.phone (or similar) is not responding.
Is this knox messing with stuff or just a buggy stock rom (mj7)?
Obviously a factory reset is the next step but I'm interested to know if anyone else finding their's is doing weird stuff that never happened on previous devices?
Thanks
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you install Wanam Xposed framework and use Center Clock at Status Bar? If yes, return back to original right side will solved the problem.
The center clock no longer work properly since MJ6, most obvious is FC your phone after end call.

No its stock and unrooted. My a alarm clock crashed last night and just now I had to reboot to get my phone signal to be seen. Will do a factory reset tonight. I'm hoping that due to no one else commenting with issues, that will fix it.
Sent from my SM-N9005 using XDA Premium 4 mobile app

episodes of screen unresponsiveness after updating to kitkat

Hi everyone
So I update my N9005 to the official polish kitkat firmware and I've been experiencing episodes of screen unresponsiveness very often. Anybody else has this problem? Anybody managed to fix it?
P.S I'm aware of the counterfeit/unoriginal s-view flip covers issue which I'm having as well but the thread isn't about it.
Hope someone has a solution.

nader9999 said:
Hi everyone
So I update my N9005 to the official polish kitkat firmware and I've been experiencing episodes of screen unresponsiveness very often. Anybody else has this problem? Anybody managed to fix it?
P.S I'm aware of the counterfeit/unoriginal s-view flip covers issue which I'm having as well but the thread isn't about it.
Hope someone has a solution.
Click to expand...
Click to collapse
Hello, I have been experiencing moments of "freezing" or unresponsiveness as well.
For me, it seemed to be due to chrome or using power saving mode. (People in another forum were blaming their droid maxxs freezing problem on chrome) I disabled chrome and disabled power saving mode.
Then I started using opera. I experienced another moment of unresponsiveness using opera without the power saving mode.
I was thinking back to the first times that it happened and it seemed to be paired to the wifi download and upload symbol being active in upload and download activity.
I know that correlation does not mean causation, but I think it is worth exploring if the network activity is causing it to somehow hang.
This bizzar occurance made me perform a factory wipe leading to another round of issues involving processing err_0000, but that is another story; sadly, it didn't even fix the issue.
OP, are you still experiencing the moments of unresponsiveness? If you are, have you noticed the events that are correlated with the event?
Has anybody else experienced this or found a remedy?
It could be one of the apps from the play store that is not playing nice with kitkat, but due to the multitude of other issues, I'd say it is a kitkat or touchwiz flaw.
Thanks for any help.
Lago

nader9999 said:
Hi everyone
So I update my N9005 to the official polish kitkat firmware and I've been experiencing episodes of screen unresponsiveness very often. Anybody else has this problem? Anybody managed to fix it?
P.S I'm aware of the counterfeit/unoriginal s-view flip covers issue which I'm having as well but the thread isn't about it.
Hope someone has a solution.
Click to expand...
Click to collapse
I had an issue with screen not responding sometimes .....I figured out it was due to the flip case (original by Samsung). Although lately I haven't experienced that either.
Try using the original non flip case and see if you still have the issue.
Sent from my SM-N9005 using XDA Premium 4 mobile app

pac-mannan said:
Try using the original non flip case and see if you still have the issue.
Click to expand...
Click to collapse
I have never had a s-view flip case on mine. I use holster iblason case that has no interaction with the screen.
This only started for me once I upgraded to kitkat.
Sent from my SM-N900 using xda app-developers app

lagoboss said:
I have never had a s-view flip case on mine. I use holster iblason case that has no interaction with the screen.
This only started for me once I upgraded to kitkat.
Sent from my SM-N900 using xda app-developers app
Click to expand...
Click to collapse
Hmmm...no idea then...try flashing it again?
Maybe that will help
Sent from my SM-N9005 using XDA Premium 4 mobile app

pac-mannan said:
Hmmm...no idea then...try flashing it again?
Maybe that will help
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If your phone isnt hanging up and freezing, that gives me hope. I'll gsm reset, clear the cache and then flash.
Thanks
Sent from my SM-N900 using xda app-developers app

pac-mannan said:
Hmmm...no idea then...try flashing it again?
Maybe that will help
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just cleared the cache, factory wiped, and installed the Russian update N900XXUDNC4 and so far, the phone is a lot smoother. No hangups in the browser yet, but time will tell lol.
It is annoying setting up the phone like new lol. I'll update the post as to if I have moments of freezing or the screen becoming unresponsive.
Sent from my SM-N900 using xda app-developers app

Cheers mate..do tell me how the battery is..if its good I might flash Russian as well ,currently have but flashed
Sent from my SM-N9005 using XDA Premium 4 mobile app

Had this problem too, as well as lots of lag. Reflashed and did a factory reset. Took care of both.
Sent from my SM-N900W8 using xda app-developers app

Battery life is looking good. Power Saving off, bluetooth on and connected to my smart watch.
I made one short call. I don't talk on the phone that much. I mostly use it for Internet browsing, music, and instant messaging/texting. I'll update on Tuesday when I have a full day at school.
Keep in mind though that the n9005 is the lte version. I have a n900, the non lte international variant; our battery life may be different.
Edit: 4/20/2014 same charge 70% 1 day 6 hours bluetooth, wifi, gps, and 1 Gmail account in sync.
Sent from my SM-N900 using xda app-developers app

Even I experienced the same. My phone came with Kitkat installed. Freezing happens when a webpage is loading or the time i turn on Sync etc. strange thing is phone seems smooter when power save mode turned on.

I think it may be a problem that was not fixed until the March 31st 2014 KitKat build. I have been using Chrome heavily since I installed the most recent official rom; I have not experienced any lag or hanging system wide or in the browser. It reminds me of 4.3.
When I wiped and reinstalled the previous rom, I noticed the lag and unresponsiveness right away.
I'm going to use the browser heavily next week. If I have no issues, I think it may be safe to say that the bug was fixed in the latest kitkat with March 31st 2014 build date.
People with lag, do you have the lte variant or the regular SM-N900? I'm starting to think only the SM-N900 are being impacted by sour Sammy updates.
And if you guys wipe your phones, make sure to turn reactivation lock off because it could cause an error that will not recognize your real Sammy account and password. This phone has become stressful; I'm not updating it again lol
Sent from my SM-N900 using xda app-developers app

I just experienced another moment of unresponsiveness using the google search box within the chrome app running DNC4 :/ Going to try the latest Russian KitKat
Sent from my SM-N900 using XDA Free mobile app

Camera failed on SM-G900H

Hi, yesterday my camera stopped working. I've seen this googling it, but I always come up with Verizon phones. Mine is factory unlocked. Also all information I came up with, was from April. Any ideas on these? I'm not home, I'm on vacations and these really sucks as I can not take anymore pictures.
Sent from my SM-G900H using XDA Premium 4 mobile app

Not only you, Sometime me and other users also faced this problem..
When I heavily used my phone and too many application running in background, on that time I faced this issue..
But after restart the device, problem gone.

I have hard reset it and still have same problem. I think tomorrow I will go to samsung and see what they tell me. I will post it
Sent from my SM-G900H using XDA Premium 4 mobile app

I like you, my s5 when updating 6.0 will be camera error

chimas16 said:
Hi, yesterday my camera stopped working. I've seen this googling it, but I always come up with Verizon phones. Mine is factory unlocked. Also all information I came up with, was from April. Any ideas on these? I'm not home, I'm on vacations and these really sucks as I can not take anymore pictures.
Sent from my SM-G900H using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm experiencing the same here

Sprint S7 & S7 Edge Nougat 7.0 beta program is Open

Hurry up before they close sign ups.
If you don't know how to register, simply download the Samsung beta program from the galaxy apps store (not play store) and then follow the prompts.
I hope you guys find this helpful

Finally!

FYI-You have to wipe data or get constant reboots
Sent from my SM-G935P using XDA-Developers mobile app

aburns7487 said:
FYI-You have to wipe data or get constant reboots
Click to expand...
Click to collapse
Mine works fine without the wipe.

I was just sharing my experience as I just got the phone the day before. I had the phone all set up it was working fine on Android 6.0.1. I upgraded to the beta for nougat Android 7.0 and immediately my phone kept rebooting every 30 seconds or little bit longer. Once I realized the data I have not had any issues at all.
Sent from my SM-G935P using Tapatalk
---------- Post added at 06:52 PM ---------- Previous post was at 06:51 PM ----------
I previously had the Note 7
Sent from my SM-G935P using Tapatalk

I had massive restart loop every 30 seconds yesterday. Have been troubleshooting. Ultimately had to rewipe again, to get it to work.
Sent from my SM-G935P using Tapatalk

I downloaded the app this afternoon, did the registration, went into my setting and checked for an update and it downloaded nougat. The one thing I have found is that Bluetooth sucks! Seriously my music breaks up with it just in my pocket and I'm wearing Bluetooth headphones. Then I took it out of my pocket and put it on the counter and I can't get 5 feet away from the phone and the music breaks up again. Prior to the update I could go to the gym, put my phone down and be a good 40 feet away and it would still work fine.
Sent from my SM-G935P using XDA-Developers mobile app

Is there a way to keep the phone's screen from coming on when a text message comes in?
Sent from my SM-G935P using XDA-Developers mobile app

Thanks to this thread I installed the beta Nougat OS.
Nothing bad so far. I did NOT wipe or remove data.
So far, I really like it. The SoTP meter says it's faster. Only thing that doesn't work so far is my Agenda Widget. Love the improved AOD. Battery seems to last a little longer, but not enough experience to say definitively. I did notice that the phone was warm when at 100% this morning. Haven't seen that since the update that stopped us charging to 100% (even though the display said it was).
The options in Settings are better- much better control of notifications.
I'll post more as I discover it.

Is anybody having the issue where the speaker volume is really quiet? Like unusable when watching YouTube.
Sent from my SM-G935P using Tapatalk

sgtmedeiros said:
Is anybody having the issue where the speaker volume is really quiet? Like unusable when watching YouTube.
Sent from my SM-G935P using Tapatalk
Click to expand...
Click to collapse
I just pulled up a random video on YouTube. Sound is working fine.

Is the registration still open?

DubSolo said:
Is the registration still open?
Click to expand...
Click to collapse
i registered but im afraid to lose my hotspot. i here they fixed the "turn it on after reboot" thing. im still on OG firmware and get 2 and 1/2 days battery life so can someone confirm hotspot still works if turned on real quick after reboot?
being on the OG firmware I can still set my apns. Thanks

Robalboa said:
i registered but im afraid to lose my hotspot. i here they fixed the "turn it on after reboot" thing. im still on OG firmware and get 2 and 1/2 days battery life so can someone confirm hotspot still works if turned on real quick after reboot?
being on the OG firmware I can still set my apns. Thanks
Click to expand...
Click to collapse
I was trying to run the Sprint software on my g935a but that damn annoying Sprint activations wouldn't allow me to get anywhere. Want Nougat bad and Verizon stopped at beta 2...booo

DubSolo said:
I was trying to run the Sprint software on my g935a but that damn annoying Sprint activations wouldn't allow me to get anywhere. Want Nougat bad and Verizon stopped at beta 2...booo
Click to expand...
Click to collapse
Nougat is closed again
Sent from my SM-G935P using XDA Free mobile app

The Beta Program is over today.
https://www.sammobile.com/2016/12/3...ogram-ends-today-official-release-in-january/

Goat1378 said:
The Beta Program is over today.
https://www.sammobile.com/2016/12/3...ogram-ends-today-official-release-in-january/
Click to expand...
Click to collapse
So it releases in January. Just a few days awayyy
Sent from my SM-G935P using XDA Free mobile app

Son Rise said:
So it releases in January. Just a few days awayyy
Sent from my SM-G935P using XDA Free mobile app
Click to expand...
Click to collapse
Lol if only! Thats when Sammy will release it to the carriers. And then they will do their thing and probably take their time draging feet.

Goat1378 said:
Lol if only! Thats when Sammy will release it to the carriers. And then they will do their thing and probably take their time draging feet.
Click to expand...
Click to collapse
Sprint users were part of the beta too, so it shouldn't be like rollouts in the past. Although I don't understand why we've been testing 7.0 and the final is supposed to be 7.1.1, unless Sprint stays on 7.0.

Ramer said:
Sprint users were part of the beta too, so it shouldn't be like rollouts in the past. Although I don't understand why we've been testing 7.0 and the final is supposed to be 7.1.1, unless Sprint stays on 7.0.
Click to expand...
Click to collapse
If sammy sends them 7.1.1 them that's what we will get. 7.1.1 isn't that much different from 7.0 just a few features added like app menu short cuts which wouldnt take much for them to add in the final release .I really dnt get how beta is over with all bugs not fixed. I personality still have an issue with Youtube videos not working after some time. Notification tones stop working after some time. No factory reset or caches clear has fixed this in the whole beta process.