Database Users

Problem with Fresh2.0d

Hey guys, today I basically re-did the fresh 2.0d rom (Freshly installed), uninstalling some apk from it. Mostly the HTC widgets... I installed Launcher.apk to have a droid like dock.
I am having an issue though, when ever i try and send an mms, I get an error which says "Generic network error". Is the Mms apk not fully supported in this rom?

XxsydenxX said:
Hey guys, today I basically re-did the fresh 2.0d rom (Freshly installed), uninstalling some apk from it. Mostly the HTC widgets... I installed Launcher.apk to have a droid like dock.
I am having an issue though, when ever i try and send an mms, I get an error which says "Generic network error". Is the Mms apk not fully supported in this rom?
Click to expand...
Click to collapse
You are on Sprint, correct? Mms.apk (the one included in fresh) is fully working, no issues at all. Assuming you didn't replace it with something else then it should be fine.
Try updating your profile and prl a couple of times (do profile, then prl, then profile, then prl) and see if it works itself out.

flipzmode said:
You are on Sprint, correct? Mms.apk (the one included in fresh) is fully working, no issues at all. Assuming you didn't replace it with something else then it should be fine.
Try updating your profile and prl a couple of times (do profile, then prl, then profile, then prl) and see if it works itself out.
Click to expand...
Click to collapse
Thanks Flipz, I appreciate the feed back, yes I'm on sprint. Using chompSMS, which to my understanding uses Mms.apk as it's middle man.
Anyways i'll update and get back to you on it. And no i didn't replace it.
EDIT: Also tested it using the default messaging app.

Sorry to double post but apparently that did nothing, I'm beginning to think I should factory reset it.

XxsydenxX said:
Sorry to double post but apparently that did nothing, I'm beginning to think I should factory reset it.
Click to expand...
Click to collapse
You could try flashing fresh on top of itself first without a wipe to see if that helps. If not then go ahead and try doing a data wipe. There haven't been any data issues reported and it's been out for quite some time.

flipzmode said:
You could try flashing fresh on top of itself first without a wipe to see if that helps. If not then go ahead and try doing a data wipe. There haven't been any data issues reported and it's been out for quite some time.
Click to expand...
Click to collapse
Ok it's fixed, I did the profile and pri update a last time just to be sure and it worked.
Ok, now that one bug is down, here is another. When I end a call at times it doesnt make the "BEEP" notifying me the call has ended, (-usually- when i use the end call button on the touch screen) When the beep doesn't sound i instantly know the bug has appeared since I've had it so many times. This bug wont allow me to dial anyone out, or does it? I'm not sure. Why? Because no sound comes out of my speakers. At all, even the tones for adjusting volume.

XxsydenxX said:
Ok it's fixed, I did the profile and pri update a last time just to be sure and it worked.
Ok, now that one bug is down, here is another. When I end a call at times it doesnt make the "BEEP" notifying me the call has ended, (-usually- when i use the end call button on the touch screen) When the beep doesn't sound i instantly know the bug has appeared since I've had it so many times. This bug wont allow me to dial anyone out, or does it? I'm not sure. Why? Because no sound comes out of my speakers. At all, even the tones for adjusting volume.
Click to expand...
Click to collapse
That's actually a known bug with this leak and affects all roms based on it. It's some type of conflict with HTC music. You can check here for a possible fix: http://forum.xda-developers.com/showthread.php?t=657244

Oh great thanks for the help again, In the future i will keep in mind to search the forums better.
Edit: -Odd, I dont even use the music player-

XxsydenxX said:
Oh great thanks for the help again, In the future i will keep in mind to search the forums better.
Edit: -Odd, I dont even use the music player-
Click to expand...
Click to collapse
I've also heard theories that it's related to contacts sync happening. Honestly I've never once had it happen to me, but a lot of people have.

flipzmode said:
I've also heard theories that it's related to contacts sync happening. Honestly I've never once had it happen to me, but a lot of people have.
Click to expand...
Click to collapse
Just like a tootsie-pop.... THE WORLD MAY NEVER KNOW.

[Q] Evo Shift keeps rebooting

Looking for some advice/help. I got my wife the Evo Shift a couple of weeks ago. Her phone has not been rooted and other than a few added apps the phone is completely stock. The phone reboots on her 4 and 5 times a day. She does not have any kind of task killer installed so that's not it. She plays Angry Birds a lot and uses Pandora quite a bit. I have also installed Sound Manager for her. Other than that I can't think of anything that would be helpful for trouble shooting. I have searched here and through Google and have not seen any info of others having this problem. I am not sure if I should root the thing or return it to best buy. I have the Evo and previously the Hero and am no stranger to rooting or custom ROMs. Just really did not see the need to root it since my wife has no idea about any of that. Any help or advice will be appreciated.
Thanks.

root and install nfinitefx's or mik's rom; you'll have less trouble than if it was stock.

danaff37 said:
root and install nfinitefx's or mik's rom; you'll have less trouble than if it was stock.
Click to expand...
Click to collapse
That's what I was thinking. I am a little worried its a hardware problem though. I guess I could always flash back to stock and return it if that doesn't fix it.

hell return it ya got nothing to lose but a headache

Did you try a factory reset?
Sent from my PG06100 using XDA App

JKILO said:
Did you try a factory reset?
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Not yet. I did get some more info from my wife though. It only happens when she is at work. And she says she get some sort of "radio error". I'm starting to think it might have something to do with the building she is in. She had my hero for a couple months before I got her the shift and had no problems. It had CM 6.1 running though.

hauntedchild said:
Not yet. I did get some more info from my wife though. It only happens when she is at work. And she says she get some sort of "radio error". I'm starting to think it might have something to do with the building she is in. She had my hero for a couple months before I got her the shift and had no problems. It had CM 6.1 running though.
Click to expand...
Click to collapse
im running mine stock and rooted and dont have any problems with reboots. sounds like a app is probably screwing something up

i had a similar problem with one of the streaming media apps i used to use a month or so ago i cant remember the name but for some reason if i lost signal it would crash the phone and need to be rebooted
i took it off and installed tuneinradio and it worked better anyways

My shift was rebooting itself 3 to 4 times a day, I just rooted it and it seemed to stop rebooting itself for a day. Now its starting to reboot itself again, but not as often.

I am almost convinced its a hardware problem. Sounds too rare to be anything else. Maybe bad memory or something.
Sent from my PC36100 using Tapatalk

I had a freezing issue with my phone which people suggested possible due to pandora and bluetooth. Perhaps you have the same issue?
Anyway, try to find "bluetooth for automotive" settings for pandora and turn it off.
I wouldn't recommend rooting your phone if you think its broken. You might just end up breaking it further and render your warranty void.
If you can't fix it, get sprint to replace it.
i dont need a signature

This may be resolved by now, but I got my shift previously used. When I first activated it, I was getting some radio errors and I could not make calls or send sms messages, but the email worked fine. I contacted Sprint customer service via chat from the website and they did something from their end to fix it. I had to turn off my phone and she said now wait till I tell you to turn it back on. I waited 5 minutes and when I turned it back on, everything was fine. So I would take it in or contact Sprint and see what they say. As for not sure if you wanna root it for her, I would definitely recommened it, she doesn't have to take advantage of all the advanced tweak that some use but it will just make the phone a lot smoother and easier to use. IMHO.
Sent from my PG06100 using XDA App

Michael61182 said:
This may be resolved by now, but I got my shift previously used. When I first activated it, I was getting some radio errors and I could not make calls or send sms messages, but the email worked fine. I contacted Sprint customer service via chat from the website and they did something from their end to fix it. I had to turn off my phone and she said now wait till I tell you to turn it back on. I waited 5 minutes and when I turned it back on, everything was fine. So I would take it in or contact Sprint and see what they say. As for not sure if you wanna root it for her, I would definitely recommened it, she doesn't have to take advantage of all the advanced tweak that some use but it will just make the phone a lot smoother and easier to use. IMHO.
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Thanks for the input. I think I'm going to go ahead and root it. After keeping an eye on the situation its seems its only happening when she is at work. I can't imagine it will fix it but I think its worth a shot.

I think I fixed mine. I tried to use navigation and it kept force closing, that was strange because I've used it before with no problems. I googled around and found some info that if you had another text to speak engine in your phone then uninstalled it without setting it back to pico as default it would cause nav to FC, which is what I had done. So I set it back and checked "Always use my settings" in the Voice section of settings, nav started working and the reboot issue went away for the past 7 days.
I don't really know crap about phones and most tech stuff for that matter (heck 99% of what is said in these forums goes over my head) but I think why this fixed it is either nav or some app was trying to use pico or something and when it couldn't the phone would get an error and reboot itself. I may be wrong (probably am) but maybe she deleted something or changed a setting some app needs and that is causing her problem. Hope this helps in someway or at least gives you another direction to start checking.

very weird evo problem :(

greetings. about a week ago, I noticed I was missing a lot of calls, and not receiving texts. I can call out and send texts, just cant receive anything. well today I had enough and took it to the sprint store. after 3 hours of them working on it, still nothing they went as far as trying my number on a different phone, and even that phone couldnt receive calls then. (never rings). lastly, they gave me a new phone number for my evo, and still cannot get calls. so, I along with them are super confused. is it my evo or the number that's bad? they ordered me a new phone to pick up on Tuesday, but I'm not convinced it'll work. anybody have any idea what on earth could be wrong? I'm running pure stock. oh yeah, Google voice doesn't work either for getting calls, but it can receive texts. wife's phone on our account works just fine. so weird. thanks guys.
Derek
data over 3g and WiFi is working perfectly.

It's network related. They better pay this months bill for you. Call Sprint and find out.
Sent from my PC36100 using XDA App

I've had a similar problem lately of not getting calls. I'm not missing all of them, but at least once or twice a day, all of a sudden I'll get a nerw Voice Mail, yet the phone never rang. And, I've had people tell me that when they call, it goes straight to Voice Mail
I just attributed it to having WiFi only on, although that is just a longshot guess on my part.

Ive been unable to receive texts girl 3 days now. Anybody find a fix?
Sent from my PC36100 using XDA Premium App

what rom? if it's calkulin's evio 1.8, there's your problem.

Cm7 final
Sent from my PC36100 using XDA Premium App

dkdude36 said:
what rom? if it's calkulin's evio 1.8, there's your problem.
Click to expand...
Click to collapse
what's wrong with that Rom? damn, now that I think about it, I ran that Rom and realize my problems started that day. is there a reason why that Rom caused my no calls/texts issue.

dschoenike said:
what's wrong with that Rom? damn, now that I think about it, I ran that Rom and realize my problems started that day. is there a reason why that Rom caused my no calls/texts issue.
Click to expand...
Click to collapse
yea. when calkulin upgraded from 1.77 (great rom) to 1.8, he added a bunch of ## codes directly in the menu. but somehow the defaults were messed up. i had this problem too. it affects any rom you flash after. just full wipe and reflash calkulin's, then get your msl from msl reader, and go to the dialer. then type ##data# and select edit. make sure mode of operation is on auto. then, DO NOT OPEN SETTINGS. just power off phone, and flash something else (maybe even calkulin's 1.7.7.)

dkdude36 said:
yea. when calkulin upgraded from 1.77 (great rom) to 1.8, he added a bunch of ## codes directly in the menu. but somehow the defaults were messed up. i had this problem too. it affects any rom you flash after. just full wipe and reflash calkulin's, then get your msl from msl reader, and go to the dialer. then type ##data# and select edit. make sure mode of operation is on auto. then, DO NOT OPEN SETTINGS. just power off phone, and flash something else (maybe even calkulin's 1.7.7.)
Click to expand...
Click to collapse
thank you for that. sorry if this is a stupid question, but will getting a new phone solve my problem? thanks
derek

dschoenike said:
thank you for that. sorry if this is a stupid question, but will getting a new phone solve my problem? thanks
derek
Click to expand...
Click to collapse
i have no idea. i'd try this first, and if it doesn't work, a sprint tech might be able to fix it.

dkdude36 said:
i have no idea. i'd try this first, and if it doesn't work, a sprint tech might be able to fix it.
Click to expand...
Click to collapse
wish i woulda asked you guys earlier i unrooted, went back to stock, spent 4 hours in a sprint store, now have a different evo coming in from sprint on tuesday. guess ill try what you said tomorrow before doing the exchange. cant today as im not home. thank you again for all that info. really appreciate it.
derek

@OP
the problem isn't with your phone, it's with your account. i ran into this a few times while i worked for Sprint, and there for all the issues that came up, the only fix was to delete the account from the network in its entirety and start from scratch. sometimes there's just some corrupted code that no level of tech support knows how to do anything with that just needs to be re-written.
i'm surprised that they ordered you a new phone even though using a different device didn't work. i think it was just a move to make you feel like they're doing something for you tbh. make sure that your line is comp'ed until the problem is resolved. you could probably get your whole bill paid, but you're more likely to get half of it (i'm assuming you only have two lines) covered. my recommendation is don't get greedy, just ask for your half.
goodluck!

JoshuaD80 said:
@OP
the problem isn't with your phone, it's with your account. i ran into this a few times while i worked for Sprint, and there for all the issues that came up, the only fix was to delete the account from the network in its entirety and start from scratch. sometimes there's just some corrupted code that no level of tech support knows how to do anything with that just needs to be re-written.
i'm surprised that they ordered you a new phone even though using a different device didn't work. i think it was just a move to make you feel like they're doing something for you tbh. make sure that your line is comp'ed until the problem is resolved. you could probably get your whole bill paid, but you're more likely to get half of it (i'm assuming you only have two lines) covered. my recommendation is don't get greedy, just ask for your half.
goodluck!
Click to expand...
Click to collapse
thanks for the info. yeah, only two lines on our account. I'm not gonna be greedy seeing as I'm the one who caused the problem (flashed the rom) I just want a working phone now I'm real curious to how long that's gonna take. I'm mean if its my account, a new phone won't solve the issue right? could take Sprint awhile to figure this all out. grrrr. and its all my fault.

dschoenike said:
thanks for the info. yeah, only two lines on our account. I'm not gonna be greedy seeing as I'm the one who caused the problem (flashed the rom) I just want a working phone now I'm real curious to how long that's gonna take. I'm mean if its my account, a new phone won't solve the issue right? could take Sprint awhile to figure this all out. grrrr. and its all my fault.
Click to expand...
Click to collapse
i'm not convinced it's your fault at all. sometimes funky things happen in the back end on sprint's side.
best of luck to you!

don't think this is a rom specific issue, it's most likely the network.
I'm having the same problem on savage-zen rom rc2...
What may help is updating your radios, prl, etc. I haven't done that in a while, not too sure that it will make a significant difference though.

dschoenike said:
greetings. about a week ago, I noticed I was missing a lot of calls, and not receiving texts. I can call out and send texts, just cant receive anything. well today I had enough and took it to the sprint store. after 3 hours of them working on it, still nothing they went as far as trying my number on a different phone, and even that phone couldnt receive calls then. (never rings). lastly, they gave me a new phone number for my evo, and still cannot get calls. so, I along with them are super confused. is it my evo or the number that's bad? they ordered me a new phone to pick up on Tuesday, but I'm not convinced it'll work. anybody have any idea what on earth could be wrong? I'm running pure stock. oh yeah, Google voice doesn't work either for getting calls, but it can receive texts. wife's phone on our account works just fine. so weird. thanks guys.
Derek
data over 3g and WiFi is working perfectly.
Click to expand...
Click to collapse
I had the same problem running Evio 1.8. I tried a number of things (including different ROMS) but what seems to have fixed it was to reflash the radio. I reflashed the PRI 1.77_003 from this thread http://forum.xda-developers.com/showthread.php?t=715485&highlight=radios and my phone has worked fine ever since. Once you're in recovery (amon or clockwork) flash the zip (PRI 1.77_003) and reboot. It will flash the radio and reboot. It might solve your problem.

nucher said:
I had the same problem running Evio 1.8. I tried a number of things (including different ROMS) but what seems to have fixed it was to reflash the radio. I reflashed the PRI 1.77_003 from this thread http://forum.xda-developers.com/showthread.php?t=715485&highlight=radios and my phone has worked fine ever since. Once you're in recovery (amon or clockwork) flash the zip (PRI 1.77_003) and reboot. It will flash the radio and reboot. It might solve your problem.
Click to expand...
Click to collapse
just letting you know, the pri is different than the radio, and we are talking about evio 1.8 starting problems like this for many, including me.

nucher said:
I had the same problem running Evio 1.8. I tried a number of things (including different ROMS) but what seems to have fixed it was to reflash the radio. I reflashed the PRI 1.77_003 from this thread http://forum.xda-developers.com/showthread.php?t=715485&highlight=radios and my phone has worked fine ever since. Once you're in recovery (amon or clockwork) flash the zip (PRI 1.77_003) and reboot. It will flash the radio and reboot. It might solve your problem.
Click to expand...
Click to collapse
so do u think its worth rooting again, and trying all that, or wait till I get the different evo and see how that goes? to be honest, I didn't want a different phone. I really liked this one and do you think them giving me a new number affects any of these trouble-shooting efforts? thanks.
Derek

dschoenike said:
so do u think its worth rooting again, and trying all that, or wait till I get the different evo and see how that goes? to be honest, I didn't want a different phone. I really liked this one and do you think them giving me a new number affects any of these trouble-shooting efforts? thanks.
Derek
Click to expand...
Click to collapse
If you have the time I would try my suggestion and or dkdude36 suggestion. He is correct in that the PRi is not the radio. I was in a hurry to type out the message. But I do mean the PRI, and I use the 1.77. You'll have to root the phone again, and nan-unlock. Then install a ROM and a recovery. If it doesn't work you'll have to restore it to stock before you return the phone so it will take some time to do all that. I was running Evio 1.8 for a while then one day I couldn't receive calls. I tried many things but the PRI fixed my phone. It's really up to you and how much time you have.

calkulin's evio 1.8
dkdude36 i think is right, i had the same problem a month ago, had to call *2 for help.
want ah guess what rom i was running....evio 1.8!
now i'm on Eternal Prophecy 5.8 got to read the hole thread, zero bugs!

Stock KF3 dialer freezes/lags?

Is anyone experiencing an issue when using the dialer in stock KF3? It freezes for a few seconds when switching between the tabs (Keypad, Logs, Contacts and Favourites).
This wasn't like this when I first got the phone. But suddenly it started to behave badly. This is the only problem I've experienced.
I'm running stock unrooted KF3.
Please help me.

If it weren't there from the first then you may have installed something which is causing the issue?

ithehappy said:
If it weren't there from the first then you may have installed something which is causing the issue?
Click to expand...
Click to collapse
Wonder what that could be. Maybe Skype influencing with the dialer or something. I'll try uninstalling.
But now I got a FC:
Activity Phone (in process android.process.acore) is not responding

I tried switching back and forth from Keypad to Contacts, everything was fine.
Also I tried switching from Contacts to Favourites, everything fine.
But when I try to switch to/from Logs, everything freezes/lags.

I tried cleaning Logs (call history), everything fine now.
WOW WEIRD!

That shouldn't be a solution, I mean removing Call history, nah. How long was it anyway? I've mine for 2 months since I purchased, never had a prob!

ithehappy said:
That shouldn't be a solution, I mean removing Call history, nah. How long was it anyway? I've mine for 2 months since I purchased, never had a prob!
Click to expand...
Click to collapse
About the same, 2 months.
Maybe I do a factory reset if this occurs again.

Oh well, now I am scared if it will happen to me as well, least both of us on KF3!

ithehappy said:
Oh well, now I am scared if it will happen to me as well, least both of us on KF3!
Click to expand...
Click to collapse
Let me know if it does.

Sure I will

Knock on problems (proximity sensor?)

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.