yashsingh1/xdaforums huggingface dataset:
[Defy Q&A, Help & Troubleshooting] mauroaraujo:
You must to desactivate the BT...

I saw at many brazillian forums that is it...

This is a kernel insue with BT...

:o:o:o
[Defy Q&A, Help & Troubleshooting] masoudzc:
i cant receive calls

Sorry what is ur meaning of BT and how can i deactivate it?

thnx for u help
[Defy Q&A, Help & Troubleshooting] mauroaraujo:
BT is Bluetooth :laugh:

Some persons has this problems...

If it doesn't yourk, you must to change the baseband...

And if the problem still continue, you must to do a "wipe data", "wipe dalvik cache" and a "wipe cache"; after this, you must to repass the ROM...

Is it...

:laugh::laugh::laugh:
[Defy Q&A, Help & Troubleshooting] hotdog125:
This bug is present for everyone:(
[Galaxy S III Q&A, Help & Troubleshooting] Wankface:
No matter what ROM I install now I get lots of lag sometimes I try type a webpage and it can take up to 15 seconds for it to input and scrolling home screens its laggy not always but enough to annoy the **** out of me. Maybe I just install too many ROMs and now my phone is screwed I don't know I tried lagfix and for few minutes I thought it worked I was so happy but then it came back any ideas what could be? P.s if your wondering yes I am typical noob that installs things without having a clue what they really do
[Galaxy S III Q&A, Help & Troubleshooting] boomboomer:
Lag is usually either a user perception or memory shortage. Go back to stock and de-bloat, geenify anything left and test, sometimes it is a hardware fault with bad memory blocks.

You might be better off with an iphone, it won't let you break it.
[Galaxy S III Q&A, Help & Troubleshooting] coolhof:
Stop installing and flashing things if you have no clue what you are doing.

You will brick your phone.

Verzonden vanuit Nederland naar de rest van de wereld met de xda premium app.
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
Start at the beginning and understand the Basics

http://xdaforums.com/showthread.php?t=2344125

Critical you read the first two posts .
[Galaxy S III Q&A, Help & Troubleshooting] Wankface:
I currently have miui note 2edition ROM. I didn't have any lag when I installed then it started lagging after few days but I remember I flashed the fly in animation from the settings menu in the ROM so I flashed the stock animation back and now it seems to be lag free for now maybe that was the problem?
[One (M7) Q&A, Help & Troubleshooting] unque1:
Why have they disable this option

You could click this off in the app manager before and now it's greyed out

Anyone able to get rid of this row?
[One (M7) Q&A, Help & Troubleshooting] UCFour:
May be we need a seperate mod to disable it from notification list

No idea why they have disabled in 4.3
[One (M7) Q&A, Help & Troubleshooting] unque1:
Annoying that this has to be hacked out
[One (M7) Q&A, Help & Troubleshooting] Thrashlord:
Try using Jmz Power Saver from the Play Store
[One (M7) Q&A, Help & Troubleshooting] unque1:
I doubt that app will be able to control the CPU as the built in version

They just need to allow the user to get rid of the icon notification
[One (M7) Q&A, Help & Troubleshooting] Thrashlord:
The apps only use is to simply hide the power saver notification icon.
[One (M7) Q&A, Help & Troubleshooting] unque1:
This app needs a rooted device

I'd rather not
[General Topics] Vesselin Nerdeff:
Arvale II promises an expansive RPG experience complete with time travel, combat galore, and all the humor you've come to expect from a PDAMill game. It certainly delivers, but is more of the same good enough?

The graphics are just as good as the first time. Every corridor is rife with details, and little animated touches throughout the landscape breathe life into the world of Arvale. Once again the NPC portraits during conversations exude a colorful anime style, and they appear to be even more detailed than before. We're treated to the same overhead perspective as part one, and for a low resolution portable game that's just fine with me. The combat is still the highlight of the graphical features, with dazzling spells and wonderfully animated characters to help you visualize the foray. I was slightly disappointed in that there didn't seem to be too much of an upgrade in the graphics engine from part one, but a good thing often doesn't need to be changed.

This game is available for order here !
[G2 Q&A, Help & Troubleshooting] lattiboy:
Hi all,

EDIT2:

MAIN PROBLEM FIXED!

I was incredibly frustrated last night, so I figured I'd just re-root as I have a copy of the stock flash tools and a TOT file sitting on my PC should I need to return.

I rooted (again), installed binaries, uninstalled Superuser, installed Super SU, and (just for fun) installed Greenify.

Lo and behold, I rebooted three times now and NO KNOCK LOOP!

I'm still having issues with knock-on not waking the phone sometimes, but once I hit the power button everything works fine.

As I posted above, the proximity sensor app seems to have a huge delay when uncovered. 3-15 seconds at totally random intervals. This might explain my still present knock-on delay issues.... ?

EDIT: Not Greenify causing this, but some other combo of rooting and system file changes. Could also be the proximity sensor misbehaving or just a bad copy of the phone.

Just a friendly PSA, but Greenify (the popular hibernation app that is really awesome) will gimp your knock-on feature for good. As in: returning to stock does not fix it. Myself and at least one other user have had this problem. I'm now having to swap out my phone after just getting it how I like it, which is infuriating.

I'd rather wait until somebody gets a fix up, but I'm within 14-days so I'm not risking it.

Note: This is CLEARLY not the fault of Greenify. It's some bizarre file system/sensor error. Greenify is great.

Related thread where the problem was thought to be fixed... but is not for people who installed Greenify.

I'm using the Verizon variant, so I don't know if this applies to GSM models.
[G2 Q&A, Help & Troubleshooting] burningembers:
From a dev standpoint this makes zero sense to me, so I'm kind of curious if anybody has better insight. Greenify, for the most part, is just leveraging system-level features to disallow the start-up of a particular program when the screen is off.

I am personally using Greenify on a number of apps with success and no ill side-effects. There are a number of code dependencies involved in its use, but mainly it is the knock-on related apk/odex in /system/app - so is it possible these people are Greenifying the wrong things?

Also, I would question their return to stock, Greenify doesn't work on a hardware level. If they didn't return the right files and/or kernel to stock, yeah, it might have lingering ill-effects. I would say that merely flashing a stock ROM is not returning to stock. It isn't clean enough.

tl;dr: There is no logical reason in my mind that Greenify would permanently break knock-on. I need more proof.
[G2 Q&A, Help & Troubleshooting] jayochs:
I've been using greenify since the day after I got the phone and rooted it, so 2 weeks now, and knock on works perfectly every single time.

---------- Post added at 12:14 PM ---------- Previous post was at 12:14 PM ----------

and I'm on the Verizon version. what app are you guys hibernating that's causing this?
[G2 Q&A, Help & Troubleshooting] DaveHTC200:
I'd have to agree with this!!
[G2 Q&A, Help & Troubleshooting] Semantics:
Knock on seems to work on mine (most of the time anyway) while using Greenify for a couple of weeks now. If it was going to gimp it, I'm thinking it would have by now. I have the T-Mobile variant. Its basically just hibernating apps from the market, not any system apps so I guess I don't see the correlation.
[G2 Q&A, Help & Troubleshooting] Ampularity:
Greenify works for me

I'm stock rooted and I heavily use Greenify with my Verizon G2. No problems with Knock On at all!

Edit: Stock rooted (not the chinese way), no OTA, auto-hibernation feature works perfectly too.
[G2 Q&A, Help & Troubleshooting] jayochs:
um question... did you guys who have the problem use the Chinese root method? someone brought it up and now I'm curious....

i did but then flashed back to stock to reroot the good way. you guys who aren't having the issue with me, you use Chinese or regular?
[G2 Q&A, Help & Troubleshooting] lattiboy:
I only froze Facebook and Twitter. Have completely Re flashed stock and BlackHole ROM to no avail. Read the thread, it seems to be vexing even advanced users. The fix of changing screen effect does not resolve it.

YMMV
[G2 Q&A, Help & Troubleshooting] burningembers:
When you say re-flashed stock, what does that mean?

Are all affected users on Verizon and using BlackHole ROM?

I'm just trying to narrow this scope down, because this still makes no sense to me.
[G2 Q&A, Help & Troubleshooting] lattiboy:
1) I rooted

2) installed Greenify

3) bug happens the next morning.

4) went back to stock, using these instructions.

5) bug happens again

6) re-rooted and installed BlackHole ROM.

Everything was (seemingly) cool for a bit, but last night it happened again. Twice this morning I've had the weird behavior sited in the original thread and I'm going to take it into VZW and leave stock in until this gets figured out.

Again, not trying to cause alarm or panic. I'll update my post to reflect the YMMV nature of this issue.
[G2 Q&A, Help & Troubleshooting] SysAdmNj:
You should really rename this thread. I have not experienced any knock issues and I've installed this app since I bought the phone. False psa :)

---------- Post added at 12:44 PM ---------- Previous post was at 12:40 PM ----------

Are you using a custom launcher or does the rom install a custom launcher? That would surely affect the knock on feature.
[G2 Q&A, Help & Troubleshooting] lattiboy:
Nope, using stock home, never even installed Nova or anything else.

I added a big YMMV to it, but because the outcome seems quite dire on such an expensive device, I feel this is warranted.
[G2 Q&A, Help & Troubleshooting] SysAdmNj:
You went back to stock, rooted, installed greenify and still the same issue? Which root method did you use, the chinese one?
[G2 Q&A, Help & Troubleshooting] oasisfeng:
The issue might be caused by misuse of Greenify. Have you greenified any system apps related to the Knock-on feature?

Greenify should never "damage" your device in a non-recoverable way since it never touches any system files. Just simply de-greenify the app and manually relaunch it once to restore everything to normal.

Hope one of you G2 users could find out that key greenified app which caused this terrible issue, thus we could warn others in a more effective way.
[G2 Q&A, Help & Troubleshooting] burningembers:
Yeah, it is an expensive device, but when you go rooting it and mucking around with system files, it is kind of a risk you take. My real issue is two-fold 1) Bad publicity for Greenify when I still don't believe it to be a problem with Greenify and 2) That LG/Verizon are taking a loss on time/cost because users are essentially breaking their own device. I put this on-par with you putting your phone in a bucket of water and then going back to Verizon and getting a new one because it doesn't work.

Now, that said, maybe this truly is a HARDWARE bug/issue with the Verizon model. On AT&T I have Facebook, Humble Bundle, Keep, OfficeSuite, Reddit News, Series Guide, and Google Search greenified. I've modified system APKs. I've flashed some ROMs. I've toggled Knockon off/on in settings. And my phone is fine.

Someone needs to start data collecting. What model phone do these users have, did they take the OTA, did they at some-point use Chinese root method, are they in a dark room, did they toggle Knockon on/off, does toggling knockon on/off on an in-store device result in a similar issue, are they all on Verizon, etc. etc.

One thing someone mentioned the other day was that the latest Verizon OTA changed the scheduler from CFQ to ROW. Is it possible that this is borking the knockon application from staying in the queue properly to register the knockon events?
[G2 Q&A, Help & Troubleshooting] lattiboy:
I did take the OTA, but before flashing the current version of TWRP.

I feel bad about it and I should've waited until these kinds of things were worked out.

I'm trying one last flash back to stock to make sure it isn't a user generated problem with flashing incorrectly.
[G2 Q&A, Help & Troubleshooting] burningembers:
So flashing back to pre-OTA doesn't clear the problem at all?
[G2 Q&A, Help & Troubleshooting] lattiboy:
No, I just flashed to stock (yet again) and I got the weird wake-lock freeze thing within 30 minutes.

Super annoying.
[G2 Q&A, Help & Troubleshooting] burningembers:
What's your Baseband and Kernel version in Software Information?

I know for a *fact* that the OTA changed the cpu scheduler. What I'm curious is if their scheduler changes have somehow caused service-level applications like the KnockOn APK to die/hibernate during a lengthy deep sleep. This makes way more sense to me than merely using Greenify causing a permanent breaking of software/kernel interactions.
[G2 Q&A, Help & Troubleshooting] lattiboy:
This is it. No root, fresh stock 15 minutes ago.
[G2 Q&A, Help & Troubleshooting] lattiboy:
OTA update not applied.
[G2 Q&A, Help & Troubleshooting] timsterzzz:
He's not crazy. It's a real bug. It's not Greenify specifically causing the bug, it just can retrigger the knock on issue. If your not having the issue and rather be pr police for an application, you are mucking the thread up. Unfortunately some people have experienced the problem, some haven't. Greenify is not the only thing I found that triggered it, flashing the stock LG browser did the same thing. Covering the ambient light sensor gives the symptoms. Maybe it's a glitchy sensor / buggy driver combination. Just because you don't have the issue, don't add useless words to thread, which make you sound like a paid rep for the Greenify dev. Btw Greenify works fine for me, luckily the work around the bug is working for me, not everyone.
[G2 Q&A, Help & Troubleshooting] usefulidiot127:
Been using greenify on VZW since day one. I'm rooted on latest OTA. Zero issues.
[G2 Q&A, Help & Troubleshooting] jayochs:
hmm, i flashed the stock browser and use greenify and i never had this issue.

are you guys on the stock rom still? it shouldn't make much of a diff, but i'm running cleanrom.

there must be some common factor in the things those wiht the bug are doing and those without are doing...but it would be such a ***** to even begin to figure out what.
[G2 Q&A, Help & Troubleshooting] lattiboy:
I flashed back to stock, unrooted using the LG tool. I then made sure the problem was happening (it was), and proceeded with the OTA. The problem persists. Even when the particular bug isn't happening (non-deep sleep periods) I'm having to do triple and quadruple taps to get the screen to turn on. It's like the sensor is somehow hosed. I'm on stock EVERYTHING at the moment. Unrooted.

It's astonishingly annoying and probably not widespread enough to warrant dev attention, so I'll probably be forced to do an exchange.

I posted screens of my post-stock flash baseband info a few posts back. That's all I can offer as I'm only a semi-competent end user and not at all helpful in these matters.

Ugh, wish I would've been patient....
[G2 Q&A, Help & Troubleshooting] timsterzzz:
I tested originally by restoring my working nandroid. After that LG tool flashed back to stock. Took the ota. It works occur after each one, without re-rooting the phone. Glitchy ambient light sensor and the software interaction with it would be my wild guess. Who knows what triggers it, definitely not LG. I still love the phone.
[G2 Q&A, Help & Troubleshooting] jayochs:
hold on. triple/quadrouple taps is the problem? everyone has that problem. it's not coming on at 2 taps when the phone enters a deep sleep for ANYONE. i always do 3 and it comes on for the most part..half the time it doesn't come on for 2 after it's asleep.
[G2 Q&A, Help & Troubleshooting] lattiboy:
No, the problem is a weird loop that happens from deep sleep. Won't respond to ANY number of taps and the screen shuts off immediately after waking with the power button, then it keeps shutting the screen off for about 15 seconds.

I'm talking about normal knock on, just moments after knock off. Before greenify it was quite responsive in those scenarios.

Again,not trying to blame greenify. This is clearly a deep system problem.
[G2 Q&A, Help & Troubleshooting] jmilacek:
So I had this exact same problem when I first got the phone. It would especially show up after calls - the screen would turn off and I couldn't get it back on, and thus could never hang up if I got stuck calling a help desk or something. I had to turn the phone off by holding down the power button for a while. It would reboot, be fine for a bit, then stop responding to taps/screen would turn off randomly after unlocking/screen off when I was on a phone call.

The main point is was that the phone was fine for two days, then started doing this, and I hadn't even rooted or installed any particular app like Greenify or the stock LG browser or whatever. It just happened on its own. I exchanged the phone at the VZW store and haven't had the problem yet with my new device (had it for about ten days now).

I think the overall conclusion is that no particular app causes this problem. It is likely a hardware defect or a bug in the stock ROM.
[G2 Q&A, Help & Troubleshooting] dinotheo:
My rooted VZW phone has started doing this as well. I've not used greenify.

It can get into a situation where I can tap it 5-10-15 times and it will not come up. I will then use the power button. The screen comes up, I unlock with a swipe and then the screen powers off. It is REALLY annoying.

Since I've seen so many people talk about the same issue, I am willing to wait until the next OTA to see if it is addressed.

This issue started for me after the OTA. (I don't know that the OTA had anything to do with it, but it started after the OTA nonetheless)
[G2 Q&A, Help & Troubleshooting] y0brando:
That's what I thought when I saw THAT was the problem. I have to triple tap80% of the time...evev before i rooted. :rolleyes:
[G2 Q&A, Help & Troubleshooting] joshuadjohnson22:
I received a G2 at work to set up for a user and right out of the box we had this issue. I wouldn't be too quick to blame a specific app. It was the verizon version and if the phone went to sleep for a few minutes I had no choice but to press the power button to wake. After that 2-5 taps would wake it. No root, no mods no apps installed (besides the preloaded ones)

LG issue?
[G2 Q&A, Help & Troubleshooting] dinotheo:
Another thing I've noticed.

The problem also became worse after I installed a screen protector. (Steinheil).

I just had this problem happen. I noticed that my screen protector was full of fingerprints. I wiped it down and then it worked. Now, I will pay attention and try the screen cleaning to see if it works. I'd be curious to know if the OP also has a screen protector.

UPDATE: Ok more testing.

After wiping down my screen. Knock on worked flawlessly.

I then purposely filled it with fingerprints. Lo and behold, I could not get it to come on. I've done this 3 times. This isn't a large enough scientific sample, but it seemed to be consistent.
[G2 Q&A, Help & Troubleshooting] lattiboy:
Phone is bare naked. Also my fiance is now getting less than twelve hours battery life with two hours screen time and no obvious apps to blame . Jesus LG , ever heard of quality control?!?!

Sucks because this phone is awesome ...when it works .
[G2 Q&A, Help & Troubleshooting] heffzilla:
I was going to ask if the affected have a screen protector installed.
[G2 Q&A, Help & Troubleshooting] lattiboy:
Double
[G2 Q&A, Help & Troubleshooting] dinotheo:
I've been continuing to test. My results now are that now with fingerprints on my protector, it is less likely to work. A clean screen protector almost always works.

Also, covering the camera seems to make the phone not register any touches. The includes swipe to unlock. Odd.
[G2 Q&A, Help & Troubleshooting] lattiboy:
I am not using a screen protector. Also, the big problem I'm having is with the "knock lock", I could live with triple tap.
[G2 Q&A, Help & Troubleshooting] usefulidiot127:
I'm not at all skeptical that you're having the issue but I'm extremely skeptical it has anything to do with Greenify. What exactly led you to that conclusion versus any other multitude of causes?
[G2 Q&A, Help & Troubleshooting] lattiboy:
The thread in my original post which I linked to. Another user had an identical issue after installing Greenify. I had literally just come on to see if it was effecting anybody else.
[G2 Q&A, Help & Troubleshooting] usefulidiot127:
Correlation does not equal causation. This sounds like a very weak correlation. Basically just a handful of data points with people having the problem who also happened to have Greenify installed? And on a whole, I think Greenify is a very common app installed by Xda users in general.

That being said, I hope we can get to the bottom of what the issue actually is so that knock on works correctly for everyone.
[G2 Q&A, Help & Troubleshooting] srps:
That really looks like a proximity sensor problem, either by dirt / fingerprints / screen protector or by calibration problems.

If possible try the proximity sensor check app. If the sensor is registering 0 it the screen will behave like that when you try to wake it.
[G2 Q&A, Help & Troubleshooting] dinotheo:
Ok I tried a proximity sensor app. I am noticing that if I cover the sensor and then uncover it, the sensor will still read 0. This can go on for a second or two up to 15 seconds. This happens about 30-50% of the time.

I don't know exactly how this sensor should work. But something else I've noticed is that placing my hand 2-3 inches above the sensor (with the phone laying flat) will cause the sensor to go to 0.
[G2 Q&A, Help & Troubleshooting] lattiboy:
I'm having the exact same results when using that app. Usually it's 3-7 seconds, but sometimes it will go up to 15 seconds. Totally random. I took a microfiber cloth to the proximity sensor area and the results are the same.
[G2 Q&A, Help & Troubleshooting] arie001:
For what it's worth, my phone hasn't been rooted yet and knock on became completely unresponsive to touch. I toggled the knock on feature off then closed all tasks from the built-in taskman and then toggled knock on back to on and it fixed mine.

Edit: I first tried pressing the power button on mine and it didn't correct my problem.
[G2 Q&A, Help & Troubleshooting] lattiboy:
MAIN PROBLEM FIXED!

I was incredibly frustrated last night, so I figured I'd just re-root as I have a copy of the stock flash tools and a TOT file sitting on my PC should I need to return.

I rooted (again), installed binaries, uninstalled Superuser, installed Super SU, and (just for fun) installed Greenify.

Lo and behold, I rebooted three times now and NO KNOCK LOOP!

I'm still having issues with knock-on not waking the phone sometimes, but once I hit the power button everything works fine.

As I posted above, the proximity sensor app seems to have a huge delay when uncovered. 3-15 seconds at totally random intervals. This might explain my still present knock-on delay issues.... ?

Should also note that if I leave the phone flat on the table for 5-15 seconds knock-on works fine. Can't tell if it's the bottom sensor or the main proximity sensor or both.
[G2 Q&A, Help & Troubleshooting] calirage2k:
That is good news. This is something to keep in mind in case LG G2 vzn owners keep gettings same problem.
[G2 Q&A, Help & Troubleshooting] burningembers:
You do all know that the proximity sensor will disable knock on, right?

It is to keep it from firing when in your pocket.

Example: Cover the sensor then hit the power button, your screen should turn off immediately.

My protector doesn't cover my sensor...so maybe that's why I haven't experienced it yet.