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.
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.
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.
Sent from my VS980 4G using Tapatalk 4
---------- 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?
Sent from my VS980 4G using Tapatalk 4
burningembers said:
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.
Click to expand...
Click to collapse
I'd have to agree with this!!
Sent from my GT-N7100 using xda app-developers app
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.
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.
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?
Sent from my VS980 4G using Tapatalk 4
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
Sent from my VS980 4G using XDA Premium 4 mobile app
lattiboy said:
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
Click to expand...
Click to collapse
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.
burningembers said:
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.
Click to expand...
Click to collapse
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.
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 ----------
lattiboy said:
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.
Click to expand...
Click to collapse
Are you using a custom launcher or does the rom install a custom launcher? That would surely affect the knock on feature.
SysAdmNj said:
Are you using a custom launcher or does the rom install a custom launcher? That would surely affect the knock on feature.
Click to expand...
Click to collapse
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.
lattiboy said:
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.
Click to expand...
Click to collapse
You went back to stock, rooted, installed greenify and still the same issue? Which root method did you use, the chinese one?
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.
lattiboy said:
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.
Click to expand...
Click to collapse
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?
burningembers said:
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?
Click to expand...
Click to collapse
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.
lattiboy said:
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.
Click to expand...
Click to collapse
So flashing back to pre-OTA doesn't clear the problem at all?
burningembers said:
So flashing back to pre-OTA doesn't clear the problem at all?
Click to expand...
Click to collapse
No, I just flashed to stock (yet again) and I got the weird wake-lock freeze thing within 30 minutes.
Super annoying.
lattiboy said:
No, I just flashed to stock (yet again) and I got the weird wake-lock freeze thing within 30 minutes.
Super annoying.
Click to expand...
Click to collapse
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.
burningembers said:
What's your Baseband and Kernel version in Software Information?.
Click to expand...
Click to collapse
This is it. No root, fresh stock 15 minutes ago.
Hi all,
I'm running stock 6.0.1 rooted with Xposed (only using gravitybox). When I do the double tap on power to launch the camera, nothing happens other than the power button functioning normally. It did work at one point but I'm not sure if it was an app, Xposed or a system setting which stopped this feature from working. Has anybody else run into this or have a few ideas to try? I tried disabling Gravitybox but left Xposed itself still installed. I've also tried changing the "Power buttons locks instantly" setting under Security but that didn't make any difference either.
Thanks
Try reflashing the vendor.img.
I'm rooted with stock rom, camera would start but not show any picture and you couldn't do anything with the app. I reflashed vendor.img now the camera will work ONCE after a reboot. Also check to see if your flashlight works.
ttillman2177 said:
Try reflashing the vendor.img.
I'm rooted with stock rom, camera would start but not show any picture and you couldn't do anything with the app. I reflashed vendor.img now the camera will work ONCE after a reboot. Also check to see if your flashlight works.
Click to expand...
Click to collapse
If you used traditional root and flashed the boot.img from an older version, it breaks camera for all apps. I had to switch to systemless root to fix the camera.
Also, just verifying that you are using a 6p not a Nexus 6, as your signature states. This is the 6p forum.
See if that setting is checked under the Display settings
pipnmike said:
See if that setting is checked under the Display settings
Click to expand...
Click to collapse
Gosh darn it. I feel dumb now but I swear I spent 30 minutes going through the settings menus trying to find if there was a setting for this. Needless to say, it was turned off somehow (probably by me accidentally) and turning it back on makes it work perfectly fine.
Thanks!
mbazdell said:
Gosh darn it. I feel dumb now but I swear I spent 30 minutes going through the settings menus trying to find if there was a setting for this. Needless to say, it was turned off somehow (probably by me accidentally) and turning it back on makes it work perfectly fine.
Thanks!
Click to expand...
Click to collapse
After updating to Nougat, double click stopped and the setting was off for me as well. But I don't feel dumb. I think whoever in Google thought this was a good place to put this setting should get that privilege. I don't know how I found that setting when I got the phone originally, but I can pretty much guarantee that I read that somewhere and enabled it. No way I went to Display Setting to find how to quickly start the camera app.
Sent from my Nexus 6P using XDA-Developers mobile app
My nexus 6p has worked fine for months however I woke up yesterday morning to find it would not play a video on YouTube. Continuing to use it I noticed the following symptoms:
Wont play videos of any kind (youtube, Facebook etc)
Speakers do not work at all
phone hangs and will not connect during incoming or outgoing calls. The call may connect after several minutes of the screen hanging on the blue calling screen however speakers don't work anyway.
Phone restarts itself randomly
I have tried a hard reset from recovery, wiped cache, booted to safe mode etc with no change.
The phone is bone stock and has not been rooted.
Any suggestions?
At this point I'd try rooting and just flashing stock ROM, don't install anything and see where it goes. If it survives, then maybe it was a rogue app, but that's a lot for an app to do - so it could be a hardware issue.
Same problem here.
teh roxxorz said:
At this point I'd try rooting and just flashing stock ROM, don't install anything and see where it goes. If it survives, then maybe it was a rogue app, but that's a lot for an app to do - so it could be a hardware issue.
Click to expand...
Click to collapse
I've got the same problem, but it happens only on stock, when I've got Chroma installed, everything is fine. One time it happened under Chroma. I don't know what causes it. Reinstalling factory images or even 7.0 doesn't help. Custom kernels didn't bring any improvement either.
Maybe there are some music drivers or something.
Yakksiek said:
I've got the same problem, but it happens only on stock, when I've got Chroma installed, everything is fine. One time it happened under Chroma. I don't know what causes it. Reinstalling factory images or even 7.0 doesn't help. Custom kernels didn't bring any improvement either.
Maybe there are some music drivers or something.
Click to expand...
Click to collapse
It could be a driver thing. Didn't look like a device issue, as it'd be constant. I would go back to stock and note when it happens and then flash a custom ROM and repeat the steps, to perform a controlled test. While doing so, take logcats so Beans / others can review them.
Gone to the service becuase even on a custom ROM I couldn't get any sound. They said that it was a hardware problem (I don't agree but we will see).
Hey forum peeps,
I've got an issue with my Moto G4 Plus (XT1643). Using any custom ROM available (official or unofficial) causes the flashlight to basically disappear. Only by using the stock ROM can I get the flashlight to work. The odd thing is, I can still use it while taking pictures, just not for usage as a tool. I can't find its Quick Settings tile, nor can I get the chop-chop gesture to work (it always says "CMActions stopped working." Since only CM-based ROMs have actions, I use them. Non-CM ROMs like Slim6 don't have gestures.)
Any known way to fix this? It's pretty annoying not having the ability to use the flashlight when I actually need it.
I'm also having Bluetooth issues (stock or non-stock). I can't connect to media devices ONLY (I can connect to my Moto 360 just fine, but I can't connect to say JBL Bluetooth speakers.) I have no idea what's causing this. I've tried everything (flashing modem files through fastboot/recovery ZIP; reverting back to stock; ****ting myself from sheer force of anger), but nothing seems to fix it (it really pisses me off not being able to use a Bluetooth headset.)
Any suggestions for this as well?
Any help on either would be much appreciated.
I'm just ruling out simple things.
Did you try rebooting on the ROMs you installed to see if chop-chop works?
For the latter, I believe you shall need a log for a developer to comment. I have no problems connecting to media devices on the XT1643.
I've noticed this issue as well.
A workaround:
Go to Gestures (or depending on the ROM you're using, wherever the Chop Chop feature can be turned on/off) and switch it off.
Reboot your device. After its rebooted, check your quick settings and verify the flashlight toggle is back.
Then go back into Gestures and Enable the Chop Chop feature..
:ROFIT::
zeomal said:
I'm just ruling out simple things.
Did you try rebooting on the ROMs you installed to see if chop-chop works?
For the latter, I believe you shall need a log for a developer to comment. I have no problems connecting to media devices on the XT1643.
Click to expand...
Click to collapse
Yeah it's like an instruction on all posts to reboot after installing a new ROM, even with stock I have to do that.
For the Bluetooth thing, I'm not really sure on that or really who to contact about it so...
Jleeblanch said:
I've noticed this issue as well.
A workaround:
Go to Gestures (or depending on the ROM you're using, wherever the Chop Chop feature can be turned on/off) and switch it off.
Reboot your device. After its rebooted, check your quick settings and verify the flashlight toggle is back.
Then go back into Gestures and Enable the Chop Chop feature..
:ROFIT::
Click to expand...
Click to collapse
Well I tried that too and it didn't work, still not there -___-
I've had Bluetooth issues with this phone, as well as my previous Moto G 2015. Something that's been working for me is an app called Quick Fix. Not sure what files it actually cleans up as it doesn't require root to run.
themajod said:
Yeah it's like an instruction on all posts to reboot after installing a new ROM, even with stock I have to do that.
For the Bluetooth thing, I'm not really sure on that or really who to contact about it so...
Click to expand...
Click to collapse
I don't remember which custom ROMs have it but in some, there's an option to put flashlight as an option in your power menu.
After that, toggling it on from there triggers a soft reboot. After that both the QS tile and gesture work fine for me.
I don't know why you are having issues in stock ROM though...
Sent from my Moto G4 Plus using Tapatalk
GuruBuilt said:
I've had Bluetooth issues with this phone, as well as my previous Moto G 2015. Something that's been working for me is an app called Quick Fix. Not sure what files it actually cleans up as it doesn't require root to run.
Click to expand...
Click to collapse
Well idk how that fixes anything for you given the fact that this disclaimer was in the app's description:
***Disclaimer: This is a placebo app. It only asks for a reboot. Regularly rebooting your device can have many positive effects***
Anyway I tried it for the hell of it, and nothing; same stupid ****.
1chrome said:
I don't remember which custom ROMs have it but in some, there's an option to put flashlight as an option in your power menu.
After that, toggling it on from there triggers a soft reboot. After that both the QS tile and gesture work fine for me.
I don't know why you are having issues in stock ROM though...
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Actually, I tried that earlier, but it ended up the same. Apparently, I bought a new phone just for some stupid but oddly important things not to work on it -_-
Also, what I meant with stock is that I also have to reboot to get the flashlight to work, after that it's 100% fine. Thing is, I'm not a fan of OEM ROMs, all of them have a certain feature on it that just ruins it for me,so I use RR or CM mostly.
Anyone? Any help?
Okay so this is really starting to piss me off. I've had YouTube disabled since I got my S8 because I use Vanced, auto update is off, Google partner setup is disabled. I've cleared just about everything and YouTube keeps enabling itself and auto updating and it's driving me mad. Any one else having this issue?
KyleBryant said:
Okay so this is really starting to piss me off. I've had YouTube disabled since I got my S8 because I use Vanced, auto update is off, Google partner setup is disabled. I've cleared just about everything and YouTube keeps enabling itself and auto updating and it's driving me mad. Any one else having this issue?
Click to expand...
Click to collapse
Are you rooted or rooted with xposed
([emoji813]9/[emoji725]/9[emoji813])
Not rooted, otherwise I would have just debloated already.
I had this issue.
I have multiple phones with same google (play) account. I've disabled youtube only on one device and it came back every time. After I disabled it on BOTH devices it gone away.
You don't need to be rooted to debloat, just use adb
Ended up switching to a pixel 2 so my s8 gets the shelf for now. Android Q is awesome.
@mrbright25 please share the command, I have the same issue and my device is not rooted
protheusDK said:
@mrbright25 please share the command, I have the same issue and my device is not rooted
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s8/how-to/s8-debloat-bloatware-thread-t3669009
protheusDK said:
@mrbright25 please share the command, I have the same issue and my device is not rooted
Click to expand...
Click to collapse
https://www.google.com/amp/s/www.xd...arrier-oem-bloatware-without-root-access/amp/ here's a guide from xda that'll help you depending on what you want to do. You just need adb and a package viewer on your phone. It's a simple but slightly tedious process, but trust me It'll do wonders to your phone. My s8 used to stutter constantly when switching between apps, now I can even run on battery saving without a single stutter.
Do be careful with what you disable as you need to be sure disabling a package won't cause problems. The safest way to disable packages is by disabling what you are familiar with! Worst case scenario, you can just format your phone, so don't worry too much!
Don't hesitate to contact me if you need any more help!