Related
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.
I installed the G-Tweaks app on my stock rooted LG G2, and once I install the Xposed Framework, every time I try to place or receive a call, I get a phone force close error, and the call drops. Any suggestions?
ki4lhl said:
I installed the G-Tweaks app on my stock rooted LG G2, and once I install the Xposed Framework, every time I try to place or receive a call, I get a phone force close error, and the call drops. Any suggestions?
Click to expand...
Click to collapse
uninstall?
Additional problems with G-Tweaks
ki4lhl said:
I installed the G-Tweaks app on my stock rooted LG G2, and once I install the Xposed Framework, every time I try to place or receive a call, I get a phone force close error, and the call drops. Any suggestions?
Click to expand...
Click to collapse
Also, if I use the mobile hotspot mod, the mobile hotspot force closes, and I cannot tell any difference in the audio from the audio mod.
ki4lhl said:
Also, if I use the mobile hotspot mod, the mobile hotspot force closes, and I cannot tell any difference in the audio from the audio mod.
Click to expand...
Click to collapse
sounds like you're having all kinds of fun
I did the Rooted upgrade to MM via this thread: http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
I'm occasionally getting random softboots for no apparent reason. Anyone else experiencing this?
I'm running xposed with greenify, gravitybox, and amplify as the only system modifying tools.
I had this happening with the first round of 6.0 installs so I factory reset and flashed from that thread I mentioned above, but it's still happening.
I had reboots when I installed mobileradiofix at first I thought my battery was draining but the rom needed to settle, I quickly removed it and all is good eversince.
You might want to check what apps you have/xposed modules.
I had that and removed it. This is a random occurrence. Happened once when opening Photos. Another when opening hangouts. One other time when switching from airplane mode off.
Very syrange, hasn't happened to me on any of the MM roms ive tried. So far I have done Indian, stock, and trueputex 2.1 I use all the same tools as you and I have had no issue with soft reboots. You sure you haven't messed with any kernel parameters or anything like that?
timde9 said:
Very syrange, hasn't happened to me on any of the MM roms ive tried. So far I have done Indian, stock, and trueputex 2.1 I use all the same tools as you and I have had no issue with soft reboots. You sure you haven't messed with any kernel parameters or anything like that?
Click to expand...
Click to collapse
Positive I haven't touched the kernel. I reflashed everything last night minus xposed so we'll see how it goes. Of course, after I did that, I was getting some wonky lag, but I think that's disappeared.
Damn do I miss xposed. If this stays stable for a few days, I'll flash it back. All I really want is GB, Amplify, and No Lock Home.
GCM push notifications in greenify seems to cause reboots at least with some apps. I have had it happen with my fantasy football app regardless of which MM rom I ran. I have since turned GCM push notifications off and no reboots, if you had it soft boot right after a notification I am almost positive that's your problem.
nast203 said:
GCM push notifications in greenify seems to cause reboots at least with some apps. I have had it happen with my fantasy football app regardless of which MM rom I ran. I have since turned GCM push notifications off and no reboots, if you had it soft boot right after a notification I am almost positive that's your problem.
Click to expand...
Click to collapse
Hmm. That's interesting. It wasn't after a notification, but it could still be an issue. I;m going to go xposedless for a bit and see what happens, then go from there.
Like the topic says, I am having major issues with SMS messages. I am not receiving all messages that are being sent to me, and people aren't getting all of mine. It's not an issue I can reliably reproduce, it's just very sporadic. I'm on AT&T and I've called them a few times and every time they tell me they corrected something and the issue should be resolved, but I'm still having problems. Is anyone else having issues like this? I am starting to think it's a problem with the phone and not the network, which would be a damn shame because I REALLY like this thing.
_MetalHead_ said:
Like the topic says, I am having major issues with SMS messages. I am not receiving all messages that are being sent to me, and people aren't getting all of mine. It's not an issue I can reliably reproduce, it's just very sporadic. I'm on AT&T and I've called them a few times and every time they tell me they corrected something and the issue should be resolved, but I'm still having problems. Is anyone else having issues like this? I am starting to think it's a problem with the phone and not the network, which would be a damn shame because I REALLY like this thing.
Click to expand...
Click to collapse
I'm on AT&T as well and was having a similar issue but was when I changed my default SMS app, such as Evolve/Go/etc.. I don't really like the stock app. Found Textra and has been working with no issues.
Are you completely stock... app/rom/etc?
Which APN are you using?
khaos64 said:
I'm on AT&T as well and was having a similar issue but was when I changed my default SMS app, such as Evolve/Go/etc.. I don't really like the stock app. Found Textra and has been working with no issues.
Are you completely stock... app/rom/etc?
Click to expand...
Click to collapse
Stock ROM but not kernel, but that shouldn't affect it I wouldn't think. Still using the stock messenger app, I never liked using 3rd party apps for that stuff. I'm gonna go and get a new SIM card tomorrow I think and try that. If that doesn't work, I might call Oneplus and try to exchange the phone.
Edit: Tried Textra at yours and my friend's recommendation and I am never going back. It is vastly superior to the stock messaging app. It remains to be seen if it solves my problem though.
lilbluemirage said:
Which APN are you using?
Click to expand...
Click to collapse
I set my own based on info I found online because I couldn't get LTE to work otherwise. What do you recommend?
_MetalHead_ said:
Stock ROM but not kernel, but that shouldn't affect it I wouldn't think. Still using the stock messenger app, I never liked using 3rd party apps for that stuff. I'm gonna go and get a new SIM card tomorrow I think and try that. If that doesn't work, I might call Oneplus and try to exchange the phone.
Click to expand...
Click to collapse
I understand the 3rd party stuff.
Kernel shouldnt.
I use ATT Phone APN, I get LTE though I still have an iPhone 6 imei registered with my number, but the settings look pretty much the same.
If haven't already try dirty flashing Oxygen... 2.1.2? Doubt it will change anything as it working sometimes...but never know.
Also a semi last resort maybe factory reset and flash but don't sign into your main Google account to make sure it doesn't pull any settings or anything so it's like a brand new phone. Confirm ATT Phone APN is set and do some testing...
I noticed some xposed stuff, while unlikely maybe there could be something there that could be conflicting with it??
If none of that works, not sure...
I would try a family member/friend's sim first as you know they aren't having issues with it or their service. Then depending on that, a new sim.
I've had similar issues before. I was running on OOS, rooted, with XPOSED installed. I noticed that it had something to do with some XPOSED modules. I believe PowerNap Xposed was behind it. I had to flash back to stock since wiping data, caches, and etc won't fix it for me.
saywhatt said:
I've had similar issues before. I was running on OOS, rooted, with XPOSED installed. I noticed that it had something to do with some XPOSED modules. I believe PowerNap Xposed was behind it. I had to flash back to stock since wiping data, caches, and etc won't fix it for me.
Click to expand...
Click to collapse
Welp, I do have power nap installed. Seeing as though I have noticed absolutely zero improvement in battery life with it I have no problem ditching it. But you don't think uninstalling it will be enough?
_MetalHead_ said:
Welp, I do have power nap installed. Seeing as though I have noticed absolutely zero improvement in battery life with it I have no problem ditching it. But you don't think uninstalling it will be enough?
Click to expand...
Click to collapse
I haven't tried just uninstalling it. Hehe I flashed everything back from a clean slate just to be sure
saywhatt said:
I haven't tried just uninstalling it. Hehe I flashed everything back from a clean slate just to be sure
Click to expand...
Click to collapse
Well I uninstalled it and it is entirely possible my problem is solved, to which I owe you a debt of gratitude. I haven't had an issue with SMS since doing it so keeping the fingers crossed.
Hi
Recently my S6e+ has stopped working during calls. More times than not when someone phones me they cannot hear me but i can hear them perfectly. I will phone them back and then it will work perfectly and they can hear me. It doesn't seem to matter whether it is an incoming or outgoing call.
I thought it was due to root and xposed being installed however i went back to stock and the issue is still there. I have tried using the voice recorder app and it works perfectly every time!
Very strange. Any ideas?
I know there is another thread about call issues but i don't believe it is exactly the same issue.
Any help would be appreciated.
Thank you
rm83855 said:
Hi
Recently my S6e+ has stopped working during calls. More times than not when someone phones me they cannot hear me but i can hear them perfectly. I will phone them back and then it will work perfectly and they can hear me. It doesn't seem to matter whether it is an incoming or outgoing call.
I thought it was due to root and xposed being installed however i went back to stock and the issue is still there. I have tried using the voice recorder app and it works perfectly every time!
Very strange. Any ideas?
I know there is another thread about call issues but i don't believe it is exactly the same issue.
Any help would be appreciated.
Thank you
Click to expand...
Click to collapse
Which kernel do you use? Probably related with kernel, but could be mixer_paths too. Whats been changed or flashed in recents?
Konsstantine34 said:
Which kernel do you use? Probably related with kernel, but could be mixer_paths too. Whats been changed or flashed in recents?
Click to expand...
Click to collapse
Currently on skyhigh 4.0. I have recently installed xposed with the following modules.
Gravity box
Wanam
Amplify
Greenify
Flat style bars
Xblast
Blurred system ui
I have also installed v4a.
I can also vaguely remember installing a ROM which had CSC options, would this affect calls?
rm83855 said:
Currently on skyhigh 4.0. I have recently installed xposed with the following modules.
Gravity box
Wanam
Amplify
Greenify
Flat style bars
Xblast
Blurred system ui
I have also installed v4a.
I can also vaguely remember installing a ROM which had CSC options, would this affect calls?
Click to expand...
Click to collapse
Mind updating kernel to 4.4? And you're not using one of Note 5 roms right?
Konsstantine34 said:
Mind updating kernel to 4.4? And you're not using one of Note 5 roms right?
Click to expand...
Click to collapse
I will try updating the kernel. Do you know anything about CSC? I also cannot send text messages I get the "invalid recipent" error?
Konsstantine34 said:
Mind updating kernel to 4.4? And you're not using one of Note 5 roms right?
Click to expand...
Click to collapse
i have updated the kernel to 4.4 but the problem still persists. I managed to get my hands on stock CSC files (apart from the feature.xml) and now messages work fine. Calls are still intermittent though, its almost like my microphone is turned off and the caller cant hear me, but i can hear them?
rm83855 said:
I will try updating the kernel. Do you know anything about CSC? I also cannot send text messages I get the "invalid recipent" error?
Click to expand...
Click to collapse
Yes I've faced this issue too but which rom I cant remember, I think I reflash the rom cleanly and fixed this. At the other hand I saw this issue in note 5 thread too. Dr. Ketan's has got fix zip to this, but not sure if it works for edge plus or not.
rm83855 said:
i have updated the kernel to 4.4 but the problem still persists. I managed to get my hands on stock CSC files (apart from the feature.xml) and now messages work fine. Calls are still intermittent though, its almost like my microphone is turned off and the caller cant hear me, but i can hear them?
Click to expand...
Click to collapse
I got this issue too when Im using note 5 rom. When I turn the speaker on, mic goes off and had to call again. Did you try talk towards top microphone when in call? It sometimes changes the main mic, you should try it. Which rom do you use btw?
Edit: I just saw you fixed sms issue. Glad to know
Konsstantine34 said:
Yes I've faced this issue too but which rom I cant remember, I think I reflash the rom cleanly and fixed this. At the other hand I saw this issue in note 5 thread too. Dr. Ketan's has got fix zip to this, but not sure if it works for edge plus or not.
I got this issue too when Im using note 5 rom. When I turn the speaker on, mic goes off and had to call again. Did you try talk towards top microphone when in call? It sometimes changes the main mic, you should try it. Which rom do you use btw?
Edit: I just saw you fixed sms issue. Glad to know
Click to expand...
Click to collapse
Yeah its a strange one, have you made any progression towards a fix? I can't live with a phone that can't make calls lol
rm83855 said:
Yeah its a strange one, have you made any professional towards a fix? I can't live with a phone that can't make calls lol
Click to expand...
Click to collapse
I have no problem with calls now. Will this fix or not dont know but I prefer you to try replacing mixer_paths.xml from stock rom or Audax rom to your current rom(/system/etc)(Dont forget to set permissions as rw- r- r). Whichever rom you use still have no idea but maybe you try different kernels like arter97 too(If you havent tried yet)..
Konsstantine34 said:
I have no problem with calls now. Will this fix or not dont know but I prefer you to try replacing mixer_paths.xml from stock rom or Audax rom to your current rom(/system/etc)(Dont forget to set permissions as rw- r- r). Whichever rom you use still have no idea but maybe you try different kernels like arter97 too(If you havent tried yet)..
Click to expand...
Click to collapse
Did your issue just solve itself? i replaced the mixer_path with no luck
rm83855 said:
Did your issue just solve itself? i replaced the mixer_path with no luck
Click to expand...
Click to collapse
When I flash a Tmobile based rom, I use this way to fix it and it works ok. Present days Im using Note 5 rom which is n920G.. based. Havent replaced anything but no problem with calls. If you havent had that issue before the custom rom or something you flash which causes this issue, its probably a software issue. Otherwise Im gonna think your mic has broken down..
Same problem here. Did you manage to fix it by any chance?