I recently rooted my phone (Galaxy S7 Edge (AT&T) or G-SM935A), which has been great, getting to use all these new apps and all the additional functionality. However, ever since rooting, my phone borders on unusable for day to day activity (Gaming is near impossible). I have managed to fix the poor battery life I was getting, but the lag is unbearable, and I don,t know how to fix it. In the middle of typing a sentence, it'll suddenly stop and take a couple seconds to respond and catch up. opening an app (any app) usually takes a couple seconds for it to respond. And while scrolling it'll tweak out and think I've long pressed something if I scroll too slowly. Also streaming stuff like youtube videos, the video often just freezes while the audio keeps playing. These are the most notable reoccurring issues I am facing.
I followed this root guide exactly as its worded:
http://forum.xda-developers.com/att-galaxy-s7/how-to/root-s7-att-g930a-g935a-t3410538
Its been slow ever since rooting. I have factory reset a few times, cleared partition cache as well as dalvik cache, tried re-flashing the kernel, tried build.prop tweaks (helped with the battery but that's all). No custom ROMs or recoveries or anything else. Just barebones config.
Also the only two root apps I have installed right now are: ES File Explorer, Seeder, and Packet Disabler Pro (only bloatware disabled though). I previously had Root Booster, and Ad Block Plus, but uninstalled them since I found them unhelpful..
It sometimes gets better for maybe half a day if I reset or clear cache or something else mentioned above that I tried, but then goes right back downhill.
I try to regularly close background tasks, not through a task manager (i.e. advanced task killer) or RAM cleaner, as I have heard that this can actually make things worse.
Any suggestions will be greatly appreciated, as I am at a total loss, and cannot find anything helpful online.
I have tried to provide as much info as possible to make any sort of debugging easier. Please feel free to tell me anything at all I might've missed.
Thank you all for your help..
Have you looked at this:
GUIDE: ROOT, install XPOSED, and UNROOT/returning to stock a Galaxy S7 or S7 Edge
http://forum.xda-developers.com/ver...tes-root-install-xposed-unroot-t3411039/page1
It might be helpful.
Use the debloater zip mentioned in the post above mine then check this thread: http://forum.xda-developers.com/ver...uide-fine-tuning-performance-battery-t3417804
This is due to using the engineering kernel needed to achieve root. It causes some phones to lag quite a bit.
Related
I've been having crash events on my Galaxy Nexus, which creates bugreport text files and screen shots on a regular basis, not to mention popping up an Intent dialog asking me how I want to send crash info. It's an annoyance I'd like to correct, so I'm looking for ways to figure out and fix whatever is causing the problem.
Is there a good methodology I can run through to at least narrow down what software is throwing the errors and triggering bug reports? Failing that, is there a decent way to suppress them?
The crashes aren't predicable and seem to occur regardless of what app I'm currently using. Some (I think) occur when I'm not using the phone, and produce a screenshot of my lockscreen as debug info. I've done a fair amount of tinkering, including basic programming in Eclipse, so I'm wondering if I can use LogCat or some other debug tool to observe a crash. Or if I can look for a specific line of the 4 meg bugreport.txt to find what process is freaking. I just don't have enough experience with analyzing when things go wrong to know where to look.
Some simple facts about my case if you're interested in offering opinions:
-Been rooted on the Nexus for ages, but crashes only started fairly recently.
-Started roughly when (give or take a few days) I flashed to stock 4.0.4 and latest Verizon radios, because my collection of mods (maybe Clockwork Recovery) was preventing an OTA update from succeeding. Interestingly, it continued after doing a SuperWipe (of absolutely everything) and flashing in Jelly Bean with stock kernel.
-The radios were reflashed, but are the same between 4.0.4 and 4.1
-All the apps I use are all installed on both OS's. I don't particularly want to go through the time required to remove apps, wait for crashes, and reload them, particularly if there is a quicker solution.
I'm having the same issue. It has persisted through multiple re-images and wipes so It has to be something that I reload on the system, but I cannot figure out what it is...
I've tried digging through the crash reports and watching logcat but i haven't been able to reproduce the crashes on demand...
Update: Actually I have a theory that these crashes may actually be related to Google Wallet. My Secure Element is locked, but i don't have a need for wallet anyhow so I never got my device replaced. I don't remember having this issue before I switched my GNex to the Takju ROM (which included Wallet). This would also explain why the issue seems to persist between wipes (Each ROM I've loaded has always had Wallet pre-installed). I'm going to try using Titanium Backup to freeze Wallet and see if I get anymore crashes. I'll keep you posted.
Resolution:
The bug reports are being generated when USB Debugging is on and Volume Up, Volume Down, and Power are all hit. For me, this was happening frequently because my TPU case is fairly tight and it depresses the volume keys inadvertently.
Thread where I found the problem: http://forum.xda-developers.com/showthread.php?t=1451521
I just bought a Samsung Galaxy S5 from T-Mobile about 2 weeks ago and everything is great but for one thing, my phone lags really badly in games like Dead Trigger 2 and Real Racing 3. It's not just some lag too it makes Dead Trigger 2 almost completely unplayable, I don't think the phone is thermal throttling because my phone does not get hot and the lag occurs instantly when just starting the game. I've also watched a few videos on YouTube showing the S5(Snapdragon 801) lagging on these games too while the Note 3(Snapdragon 800) was flawless without any lags so I'm really confused, does anyone else have this problem?
First make sure you don't have power save on or something obvious like that.
Then check memory, If memory is low, reboot the phone, go into settings /application manager, click on every program you can recognize and don't use ATM and force stop. Things like games and programs you installed etc. After you're done check memory again for comparison and run the game. If it's better, then look for more permanent solution, like Clean Master or something, if not, I don't know. Just reboot the phone after a game again, to make sure programs you killed are restarted, so you don't loose any functions.
pete4k said:
First make sure you don't have power save on or something obvious like that.
Then check memory, If memory is low, reboot the phone, go into settings /application manager, click on every program you can recognize and don't use ATM and force stop. Things like games and programs you installed etc. After you're done check memory again for comparison and run the game. If it's better, then look for more permanent solution, like Clean Master or something, if not, I don't know. Just reboot the phone after a game again, to make sure programs you killed are restarted, so you don't loose any functions.
Click to expand...
Click to collapse
Thanks for the suggestions! The phone didn't have that many apps since I just got it at the time but power saving mode was off and I also disabled a ton of Samsung apps and bloatware to try to save memory as well but it still lagged so I ended up swapping the S5 for a HTC One M8 and the M8 has been smooth so far. Thanks anyways!
I have been experiencing a series of force closes. I am posting this to see if anyone else has experienced this, and whether anyone can suggest a fix. I'm pretty sure it was something I did, but I'm not sure what. I'm hoping that this can maybe narrow it down.
Device: SM-N900P
Firmware: OC5, stock, rooted, with several tweaks and modifications(detailed below).
The problem: I am getting several force closes. They only occur when I am trying to open certain settings. So, they aren't just popping up at random. They are slightly troubling, but not really problematic. Which is to say, aside from the actual force closes themselves, I don't really seem to be experiencing any major problems. Here are the FC's I am experiencing:
-Menu> Settings> General> Battery: This one results in a "Unfortunately, Settings has stopped" dialog box, and an immediate return to my home screen. So, I can't check out my battery usage. I'm not seeing any crazy battery drain. By opening Root Explorer and navigating to data> system> batterystats.bin, and deleting batterystats.bin, the problem is kind of fixed- I can open battery from the settings menu after that. But there is only battery level and state displayed, no usage information(just a message saying it is not available).
-Menu> Settings> General> Developer options> Process Stats: Results in the same dialog box, and the background turns black if I don't press "OK". I'm not even sure what this does, but after my Battery started force closing, I started checking the rest of the settings out.
-Menu> Settings> Connections> Data usage: Dialog box, immediate return to home screen.
The probable cause: hard to say, I've done a few things to it. Like I said, I was hoping that someone would be able to figure out what I've done from the following information about what I have done so far. So, here goes.
I was on NK4, running Priest Punch ROM. I reverted to stock and took the OTA about a week or so ago. I immediately rooted and installed TWRP using the method in this thread: http://forum.xda-developers.com/note-3-sprint/general/how-to-root-note-3-lollipop-t3089382 .
After rooting, I didn't see a whole lot of OC5 development, so I started poking around to see what kinds of mods I could use. First thing I wanted to do was remove bloat. I started off using Root Explorer, then I happened upon this thread featuring a bloatware removal tool for the T-Mobile variant: http://forum.xda-developers.com/note-3-tmobile/development/tool-utility-sgn3-sm-n900x-bloat-t2813036 . It worked. I removed a bunch of apps, but nothing I wasn't sure I could safely remove(I had to check Google a few times). I did not notice any problems at this time.
Then I installed this mod to pump sound out of both speakers: http://forum.xda-developers.com/note-3-sprint/development/mod-sm-n900p-surround-sound-t2966042 . I did not notice any problems at this time.
Next, I decided I wanted more fonts, so uninstalled the preloaded fonts and pushed the apk from this thread: http://forum.xda-developers.com/showthread.php?t=2752379 . Again, no problems.
I decided that a working hotspot would be nice, so I used the method in this thread to get one: http://forum.xda-developers.com/note-4-sprint/general/lollipop-hotspot-root-flashing-t3048163 . I tested it and it worked. No problems.
I really wanted to silence my shutter sound, and I happened upon this Galaxy S4 thread: http://forum.xda-developers.com/showthread.php?t=2261789 . It worked, and there were no issues. This was my first exposure to csc codes. I found a similar thread for the s6( http://forum.xda-developers.com/galaxy-s6-edge/general/quick-guide-enabling-hidden-features-t3087506 ), and followed the instructions. I was able to enable the camera during calls and enable call recording. No problems here. I tried a keyboard mod from the same thread, which had no effect at all(good or bad), so I reverted the code for that one back.
This is when I think I started to go off the rails a bit. I saw a thread for the Polish variant of the Note 3, N9005. http://forum.xda-developers.com/gal...camera-mod-note-3-n9005-lollipop-5-0-t3067827 -it had a neat sounding mod designed to improve camera quality, remove recording time and snapshot restrictions, and make 60fps HD the default camcorder mode. It took a little trial and error to get it installed, but I was making backups of files I was messing with, and was able to quickly and easily reverse any missteps. Again, the mod works fine, and I have noticed no issues. So, I started looking at the dev's other work. Which led me to this thread: http://forum.xda-developers.com/galaxy-note-3/themes-apps/secsettings-mod-17-swipe-charging-t3046032 . I wanted some different unlock effects, and I wasn't really finding them, so I tried his mod out. It was a 3 step process: replace a SecSettings app, copy paste some .ogg files, and finally, copy paste a SustemUI .apk. The first two steps went fine, but the third resulted in a persisitent, repetitive dialog box. I forget what this dialog box said, but it popped up almost as soon as I could press "OK", and I had to restore the backup of SystemUI to make it usable again. Oddly enough, about half of the new unlock animations still worked fine, and I wasn't seeing any problems after that, so I left everything else there. I liked the unlock animations, and they didn't seem to be causing any problems after I restored the original systemUi .apk.
Let's see, what else might be relevant? I was using the built-in task killer quite a bit. I'm also using SetCPU. I have 2 profiles: Screen on, 1728 MHz max, 300 MHz min, governor ondemand. And Screen off, 1036 MHz max, 300 MHz min, governor interactive. And I have installed the Material Power Menu from this thread: http://forum.xda-developers.com/android/apps-games/app-materialpowermenu-reveal-animations-t3059169 .
I started to notice the battery FC last bight. So, I wiped the battery stats as outlined above. Noticed it again today, wiped stats again, and kept checking it. After about an hour, it was force closing again. That's when I started poking around and found the others.
I dunno if anything can be done about this, or if anyone might know what's wrong. And, like I said, Aside from these FC's I'm not experiencing any real problems. I'm a little worried that they may get worse, or turn into something more serious, but I can always restore a backup if that happens. But if there is some kind of fix for these issues, I would use it. Thanks in advance to anyone who takes the time to read this wall of text, and tale of irresponsible phonery.
These are all settings that monitor usage.... should that tell me anything? I have tried wiping cache and dalvik, but that only seems to fix battery usage and data usage very temporarily(like, for a minute or less). And it doesn't seem to have effect on Process Stats.
My thoughts:
Seeing as you have flashed a lot of mods, it could be anything. If it were me, I'd start the rom from scratch. Then for the first step, instead of removing apps, I'd freeze them with titanium backup and give that a day or two to check the stability.
If that works, I'd continue with the mods one by one, giving a day or so for stability checks.
If you'd rather not do all that, you could use a logcat to find the origin of the problems.
Sent from my SM-N900P using XDA Free mobile app
jlechner said:
My thoughts:
Seeing as you have flashed a lot of mods, it could be anything. If it were me, I'd start the rom from scratch. Then for the first step, instead of removing apps, I'd freeze them with titanium backup and give that a day or two to check the stability.
If that works, I'd continue with the mods one by one, giving a day or so for stability checks.
If you'd rather not do all that, you could use a logcat to find the origin of the problems.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
I'd probably try the logcat first. One, because I hate doing stuff over, and two, Ive neber done it before and it should be a learning experience. Is it complicated? I'm assuming there is a thread here on xda about it...
GAPO said:
I'd probably try the logcat first. One, because I hate doing stuff over, and two, Ive neber done it before and it should be a learning experience. Is it complicated? I'm assuming there is a thread here on xda about it...
Click to expand...
Click to collapse
It's fairly straight forward. I did one to see why an app wasn't loading, didn't need instructions. But that was a fairly simple check, yours sounds more complicated. I'd do a bit of reading on it.
Sent from my SM-N900P using XDA Free mobile app
jlechner said:
It's fairly straight forward. I did one to see why an app wasn't loading, didn't need instructions. But that was a fairly simple check, yours sounds more complicated. I'd do a bit of reading on it.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Will do. Thanks for your help!
Okay well I decided to re flash OC5 and start from scratch.
I took it back to stock and re rooted. Am now debloating....no isssues yet.
I have flashed everything except the Polish camera mod and the wallpapers. Having zero issues of any kind. I know it can take difficulties some time to manifest themselves, but I'm betting it is either the lock screen animations or the camera mod. Leaning towards the lock screen animations because it involves messing with system.ui...
Okay, made a new backup and flashed the camera mod. No issues. After every mod, I have been going back and checking for issues. This is all stil pretty new, but if everything is still fine after a couple of days, well, I will be convinced that it was the lock rings. Not surprising obviously that flashing stuff meant for foreign variants can wreck your sh*t, lol.
Hello, guys,
I have had Redmi Note 3 for 6 months now and I have been struggling with an annoying issue.
Whatsapp gets killed after a little time of idleness and unless I kill it in the task manager and restart it, I cannot either receive or send messages. When I check in the running apps section, it is not there so the OS certainly kills it. And just clicking its icon on the desktop, opens the GUI but it does not work unless I force close it and re-open it.
I have had issues with Whatsapp on previous devices - more of the common stuff - delayed notifications, messy push service. This is something else.
MIUI 8 is notorious, it seems, for its RAM and Battery management killing apps and I often struggle with that, too. For example: I minimize VLC to open Firefox. I switch back to VLC - ok, the movie starts over, the app has been killed. This is really annoying and I have turned off all kinds of optimization to prevent it, with no success. I am not sure, though, that it is connected to the Whatsapp issue. Because Whatsapp seems to get killed when the phone is idle for a moment but not when switching between apps.
I rarely use Viber but I think the situation there is the same. I sent a message to a friend and I got no response. I opened the app 5 days later and the response came However, it had tried to arrive 2 minutes after my original message. But I had not opened Viber for 5 days, so...that happened.
Let me know if you need details about my settings. I would be really grateful if someone can share some insight on what might the issue be. I guess if I root the phone I can try and locate the culprit module that kills apps. Maybe edit a config file to disable the killing functionality. It is clear this ROM does not like running apps....
Thanks,
Kiril Ekblad
P.S. I have been on Google multiple times: nobody seems to have that issue.
Disable battery saver
developer options -> disalbe MIUI optimization
MIUI is way to aggressive in killing apps ....
maybe go for a custom rom?
You can follow this https://forum.xda-developers.com/re...de-redmi-note-3-sd-mtk-multi-tasking-t3358433 and see how it`s going with push up notification.
When i`ve used miui 8, i`ve done this things and it seems to work good, but anyway push up notification came with a small delay..
For this reason i left miui 8 (very bad ram management) and flashed nougat custom rom and everything working good
Thank you, all
I have actually tried all of these and all steps in the quoted topic. No difference whatsoever. I would gladly go for a custom ROM bit things have gotten really complicated lately. A coupke of yeara aho I would easily grab and flash a custom ROM. Now when I browse through the ROMs topics here I get frustrates.
Something about firmwares, stuck bootloaders I have no idea where to start.
Oh and I don't want to lose slow motoon and time lapse videos. Do you know of a custom ROM that supports them ans the stock one does?
Ekblad said:
Thank you, all
I have actually tried all of these and all steps in the quoted topic. No difference whatsoever. I would gladly go for a custom ROM bit things have gotten really complicated lately. A coupke of yeara aho I would easily grab and flash a custom ROM. Now when I browse through the ROMs topics here I get frustrates.
Something about firmwares, stuck bootloaders I have no idea where to start.
Oh and I don't want to lose slow motoon and time lapse videos. Do you know of a custom ROM that supports them ans the stock one does?
Click to expand...
Click to collapse
.
Try clean flash of MIUI ROM or flash Epic / Xiaomi.eu ROM
Thanks, I will have to research on the EPIC/EU ROM.
I am all for changing the ROM as long as I can cope with the flashing and I do not lose any of the significant features of the stock ROM.
By the way, recently - the last several days - I have noticed that on multiple occasions Whatsapp seems to be running - it is showing in the Running apps and still the program cannot either receive or send until I force close it and re-start. Whatsapp web also says Phone not connected.
Okay, so as of yesterday, march 27, I have been having severe issues with my display becoming an extremely low resolution and pixelated to the point where nothing is legible or recognizable.
I've included a link to two two screenshots and their descriptions are as follows...
Picture 1, final Fantasy brave exvius main loading screen
Picture 2, Vainglory mode select screen
Picture 3, clash of clans loading screen.
I've done a factory reset, wiped all data under the sun from my phone. Installed and reinstalled games repeatedly but no fix. Can't seem to find a solution anywhere.
I've tried optimizing graphics apps but no bueno. Even tried battery optimization off for all apps. No fix. Only on game apps. Everything else runs as it should.
Please assist if a solution has been found for an issue as this.
Edit okay so I can't post links so message me if interested and I can send you the photos.
My post here helped me.
https://forum.xda-developers.com/an...y-graphics-t3769995/post76046555#post76046555
I tried Game Tuner just for the sake of it, but it blurs me again somehow. So no, I won't use Game Tuner (I never did, anyway.)
ekrezem said:
My post here helped me.
https://forum.xda-developers.com/an...y-graphics-t3769995/post76046555#post76046555
I tried Game Tuner just for the sake of it, but it blurs me again somehow. So no, I won't use Game Tuner (I never did, anyway.)
Click to expand...
Click to collapse
I tried reverting the game optimization back to its original version by uninstalling updates, clearing the factory default gameservice cache. It causes occasional flashing on game restarts and I have to repatriation the process, but resolves the the lower resolution issue.
I very much appreciate the call out on the other thread!
However I run into the slight annoyance of having to do this several times during a normal day of usage. It never actually saves the setting. I do not have root access as this is the factory Verizon build for marshmallow. (I wouldn't be able to do that on this worn thing).
Caveat: along with the "ghost" reapplying the game optimization services update and causing it all to happen again, what would be a good recommendate on for keeping the service at a factory setting?
Edit: skipped that infernal game Tuner altogether. It proved trivial to what the issue actually is...and was useless in the entire process.
Sybreed said:
I tried reverting the game optimization back to its original version by uninstalling updates, clearing the factory default gameservice cache. It causes occasional flashing on game restarts and I have to repatriation the process, but resolves the the lower resolution issue.
I very much appreciate the call out on the other thread!
However I run into the slight annoyance of having to do this several times during a normal day of usage. It never actually saves the setting. I do not have root access as this is the factory Verizon build for marshmallow. (I wouldn't be able to do that on this worn thing).
Caveat: along with the "ghost" reapplying the game optimization services update and causing it all to happen again, what would be a good recommendate on for keeping the service at a factory setting?
Edit: skipped that infernal game Tuner altogether. It proved trivial to what the issue actually is...and was useless in the entire process.
Click to expand...
Click to collapse
Hmm, someone have another solution. You can test it here https://forum.xda-developers.com/an...y-graphics-t3769995/post76046555#post76046555