Related
first off, I'm running stock EC05, rooted
Problem:
yesterday my Epic started jumping to the pause screen while I was playing Collapse! which I had gotten off of the Amazon App market, at first I thought it might be the hardware fault when the back button presses automatically, but it wasn't as it continued to do it without the haptic feedback or blinking, so I ruled that out and tried reinstalling
unfortunately it continued, so I though it might be a bad download that needs an update on the market, so I uninstalled and decided to play Robot Unicorn Attack which I got off the Android Marketplace, however it does the same thing, right in the middle of gameplay, it will jump to the pause screen
so now I thought it might be some other app that I updated that is causing some kind of interference with the system, so I uninstalled all apps that had been updated or installed over the past 2 or 3 days, the problems remains
I tried Fruit Ninja from that Amazon App Store as well, same problem, I'm really not sure what is wrong as there had been no problems with any of the games before yesterday, I also did a scan for malware just for kicks but nothing showed up
when I tired searching for people with similar problems, the closest I found was someone who was having what seemed like an identical problem on a Galaxy S Tab, any help that doesn't require a complete rom flash would be awesome
thanks!
impoc said:
first off, I'm running stock EC05, rooted
Problem:
yesterday my Epic started jumping to the pause screen while I was playing Collapse! which I had gotten off of the Amazon App market, at first I thought it might be the hardware fault when the back button presses automatically, but it wasn't as it continued to do it without the haptic feedback or blinking, so I ruled that out and tried reinstalling
unfortunately it continued, so I though it might be a bad download that needs an update on the market, so I uninstalled and decided to play Robot Unicorn Attack which I got off the Android Marketplace, however it does the same thing, right in the middle of gameplay, it will jump to the pause screen
so now I thought it might be some other app that I updated that is causing some kind of interference with the system, so I uninstalled all apps that had been updated or installed over the past 2 or 3 days, the problems remains
I tried Fruit Ninja from that Amazon App Store as well, same problem, I'm really not sure what is wrong as there had been no problems with any of the games before yesterday, I also did a scan for malware just for kicks but nothing showed up
when I tired searching for people with similar problems, the closest I found was someone who was having what seemed like an identical problem on a Galaxy S Tab, any help that doesn't require a complete rom flash would be awesome
thanks!
Click to expand...
Click to collapse
The only thing I can suggest is going into Clockwork and clearing data and Dalvik cache. Sounds like some data corruption somewhere if you are running stock with no overclocking or undervolting which usually causes this kind of behavior.
Are you running an overclocked kernel? I have a similar problem with Words With Friends whenever I'm running an overclocked kernel. If I disable overclocking and reboot, the problem goes away.
Sent from my SPH-D700 using XDA App
greezestain said:
Are you running an overclocked kernel? I have a similar problem with Words With Friends whenever I'm running an overclocked kernel. If I disable overclocking and reboot, the problem goes away.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
His OP said he was running stock. Switch to Word feud, you can overclock all you want and still run Adfree.
kennyglass123 said:
The only thing I can suggest is going into Clockwork and clearing data and Dalvik cache. Sounds like some data corruption somewhere if you are running stock with no overclocking or undervolting which usually causes this kind of behavior.
Click to expand...
Click to collapse
I will give it a shot and let you know how it goes
question though, can I restore anything from my Titanium Backup? or would that just bring the problem back once it was restored?
impoc said:
I will give it a shot and let you know how it goes
question though, can I restore anything from my Titanium Backup? or would that just bring the problem back once it was restored?
Click to expand...
Click to collapse
Was it OK when you did the backup? If so you can certainly try. Just to clarify you are on full stock, just rooted?
Do you BONSAI?
I'm at sprint right now returning a completely stock refurb they gave me. Apps are randomly opening and backing out of themselves
stir fry a lot said:
I'm at sprint right now returning a completely stock refurb they gave me. Apps are randomly opening and backing out of themselves
Click to expand...
Click to collapse
Nooooo! Something wrong with a Sprint refurb?!! That is unheard of! Rightttt! That is how I got talked into Black Tie insurance...they promise a new phone.
Do you BONSAI?
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.
Hello all... so I'm having a bit of a random issue where my default keyboard selection (Swype) randomly stopped sticking. I'd select it as default and all would be fine. Once I put the phone down then come back to it after a short while, it switches itself back to the stock LG keyboard, which I'm not very fond of. I'm stock rooted on Verizon and using a few xposed modules. Did all that yesterday and things have been fine up until about an hour ago when it started doing this. I changed nothing in xposed since last night. Been using the phone all day without issue. Any thoughts why it would be doing this, and a way to make it stop... preferably one that doesn't involve wiping data?? Any help would be greatly appreciated! Thanks in advance!
Update: So I cleared cache and dalvic in recovery, which somehow I didn't think about doing before, and that seemed to work (for now). However, I'm still quite curious what could have caused this, in case it starts up again. Which is certainly possible. Again, thanks in advance!
Update #2: Yep, that didn't work Lol gahhhhhhhhhh!
Update 3: Ok I think I got it, sheesh ... greenify somehow added Swype to its hibernation list... no idea how. I removed it and it seems to be sticking thus far. So anyone who is having this issue while using xposed modules, such as greenify, double check what apps greenify is hibernating at that time.
Sent from my VS980 4G using Tapatalk
Is anyone else experiencing any performance issues after root? I'm trying to figure out exactly what is happening, so if anyone has suggestions please send them my way.
I haven't done anything crazy after root except install Super Su, freeze some apps with TiB, and remove some bloat (VZW stuff). Now every reboot from my device takes between 3 to 10 minutes to fully come up (using All-in-one toolbox). It used to take under 2 minutes. Scrolling between screens are slow as hell too.
S Health no longer works (I read the threads about fix, but doesn't work for me).
I had to uninstall Xposed framework and Wanam (too laggy) and disabled the Google Now Launcher.
Please, post up any helpful suggestions or anything I should try to improve my performance. Thanks!
BSquaredB2 said:
Is anyone else experiencing any performance issues after root? I'm trying to figure out exactly what is happening, so if anyone has suggestions please send them my way.
I haven't done anything crazy after root except install Super Su, freeze some apps with TiB, and remove some bloat (VZW stuff). Now every reboot from my device takes between 3 to 10 minutes to fully come up (using All-in-one toolbox). It used to take under 2 minutes. Scrolling between screens are slow as hell too.
S Health no longer works (I read the threads about fix, but doesn't work for me).
I had to uninstall Xposed framework and Wanam (too laggy) and disabled the Google Now Launcher.
Please, post up any helpful suggestions or anything I should try to improve my performance. Thanks!
Click to expand...
Click to collapse
Did it start only after root or after installing the xposed framework? If it was the latter have you tried the fixes that have been posted?(disable secure storage, clear shealth cache/davlik cache.)
Rakuu said:
Did it start only after root or after installing the xposed framework? If it was the latter have you tried the fixes that have been posted?(disable secure storage, clear shealth cache/davlik cache.)
Click to expand...
Click to collapse
Thanks for the reply Rakuu and yes, I have tried clearing both caches and secure storage is disabled. The degraded performance started after getting root, but I installed Xposed pretty quickly afterwards. It almost feels like stuff is running in the background, but I can't see any blatant process that could be causing it.
I was actually thinking that the S5 would fly after freezing or removing the bloat. Weird.
You can always Odin back to stock . I had Bluetooth problems and lag after root. I went back to stock and no more problems
Sent from my SM-G900V using XDA Premium 4 mobile app
That's what I'm going to do I think. I hate my phone now.
EDIT: Noticed this morning that notifications are not working properly and something is also draining my battery. Phone died over night (77% battery) at 10:30pm and late for work today.
Question (probably stupid one): Is there a way to redo the root process or do a factory reset without loosing root to try and fix these issues? Otherwise, will be using Odin today. Thanks.
Sent from my SM-G900V using Tapatalk
BSquaredB2 said:
That's what I'm going to do I think. I hate my phone now.
EDIT: Noticed this morning that notifications are not working properly and something is also draining my battery. Phone died over night (77% battery) at 10:30pm and late for work today.
Question (probably stupid one): Is there a way to redo the root process or do a factory reset without loosing root to try and fix these issues? Otherwise, will be using Odin today. Thanks.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
I'm having similar issues, although not quite as bad as yours, after rooting, removing bloat and installing Xposed. I'll be ODIN'ing back to stock and re-rooting tonight.
If I were you, I would do the same: ODIN back to stock and then re-root. Rooting is now a 1 click deal so it's really not hard or time consuming at all. Then just make sure to take your time removing bloat and modifying to try and identify what exactly is causing the performance issues.
So my phone seems to be functioning normally now, but I'm not sure why. Battery is lasting all day, screens seem more responsive, notifications working, and I even got S Health to start working with fix (wasn't editing/saving the build.prop file correctly). I still need to re-install Xposed and Wanam, but I didn't want to push my good luck.
Can anyone guess why performance is better now (like night and day difference)?!
I noticed it with mine too. I put it back to stock and left it
Sent from my SM-G900V using XDA Premium HD app
Same here. I Odin mine back to stock, then rerooted and froze a few apps but didn't touch Xposed or Wanam. It's running so much better now
Sent from my SM-G900V using XDA Free mobile app
I had similar issues after setting up safestrap. It lagged, WiFi never wanted to connect or anything. Factory reset and just used towelroot and xposed and haven't had much issues at all. Some apps lag a bit but I figure its to be expected.
Sent from my SM-G900V using XDA Premium 4 mobile app
Rooting itself does not change performance. Just clarifying because the subject line suggests that it does.
Sent from my Nexus 7 using XDA Free mobile app
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.