Hi all,
I'm having an issue with my vodafone smart prime 6 running a debloated stock rom.
Basically my phone frequently suffers huge lags and crashes where the phone becomes almost totally unresponsive for several minutes. These happen many many times a day, often occuring in batches. Otherwise, the phone can seem quite quick and responsive. I also get alot of apps crashing in the background.
These lags seems to be linked to the process kswapd0, which I believe is linked to move data to and from swap. I previously tried using swap on a different rom installation, but the phone has been totally reinstalled several times since and I haven't turned on swap since.
When I check in the terminal swap is apparently being used. I can't succesfully turn it off through the terminal, so I have used Trickster MOD to turn off zram and this brings swap usage down to zero but the kswapd0 process continues to huge a lot of cpu and cause lagging.
Whats going on?
Is there a way I can permenantly stop swap, or figure out why kswapd0 is causing such huge issues?
Many thanks in advance.:fingers-crossed:
Bump
Bump
Anyone? Bueller...?
One year later, Bueller finds your thread. However, Bueller is no help, because he has the same problem...
Related
Is it possible that rooting the Vibrant causes lag? I finally rooted my phone to install the gps fix from the later firmware, and now my phone suffers horrible lag. Before rooting I had no lag and no delays. Everything was fast. Now menus take seconds to come up, programs take seconds to load. Is it possible rooting has caused this? Or maybe even the GPS fix?
Is it possible for me to keep the GPS fix, but unroot and remove One-Click Root and Clockwork? Thanks.
It's not the root that caused the lag. Try a battery pull and see if that helps. I'm not sure fixes will work without root.
More apps more lag
Sent from my SGH-T959 using Tapatalk
I also felt that way but in a couple of days after a few reboots it will be back to normal. However my average Quadrant score definitely dropped by about 20-30 points (not much but I did notice) after I did the one click root method
I thought it might be more apps, but I've actually taken apps off (none of the stock stuff though). Just extra games and apps I didn't use. It didn't help.
I've rebooted 4 or 5 times since then and nothing's helped. It's just very odd. I would expect root to lag at all unless it's calling super user for access validation everytime or something.
Hello everyone,
Has anybody else who updated to 4.1.57 find that their Atrix is now kinda sluggish? I don't mean all the time, but every now and then I get random stutters or sluggishness when switching between programs. A couple of times, it even screen locks for a few seconds when waking up. This has never happened to me before with the 4.1.26, where programs just run without hesitation. They either run smoothly, or FC in the process. But now, some of them just becomes jittery.
I wonder if it has something to do with Motorola's battery improvement in the update. When it got sluggish on me, I decided to go to into setcpu to see at wat speed the phone was running. I noticed that the phone was throttling severely all the way down to 216 mhz the second the phone is not being used. it fluctuates up and down but it seems to always drop down there once i dont touch the phone. I think this is causing an issue cuz there's a lot of background apps and widgets running and once you try running an active program, it takes a split second to start, and that split second causes it to stutter.
I haven't had the screen lock in a while, so that's a good thing. But it seems setcpu can't seem to force the cpu to constantly stay high, even if i put the minimum to 1000mhz, so I get those stutters every now and then.
Anybody has any suggestions on this matter? Im thinking if this persists, I might just go back to 5.1.26 until they come up with a major update. Really the only reason I updated was cuz the prompt was driving me mad.
p.s. another way I know how the cpu isnt running a constant 1ghz --- my phone isnt as hot as it used to be. it used to be so warm in my hand, my hand would turn red from holding it.
It takes very, very little time for a modern CPU to change its clock speed. Monitor your computer's CPU clock closely sometime, it almost certainly does throttling to a similar degree. I also observed similar levels of throttling via tegrastats on my Atrix prior to the update.
Personally 1.5.7 has been good for me, at least in the sense that nothing appears to be worse after.
Sent from my MB860 using XDA App
Only heard good reviews on 4.1.57. Can't wait for Bell to issue it too
lol, i dont like throttling. All my PCs n laptops run on full speed (throttling disabled) whenever they're on. I expect the same with my phone x) I just don't like any lag but I understand wat you mean. I still wanna hear what other's feel about the update.
note: I'm about to deodex the phone in a bit. Let's see how it ends
Moving stuff around in device memory is an order of magnitude slower than your CPU changing clock speed, and moving stuff between flash and device member is an order of magnitude or two slower than that. CPU throttling isn't the right place to look for this sort of issue.
As for your computers and not allowing them to throttle...enjoy the power bill I suppose. Even in overclocked scenarios modern processors work just fine with throttling enabled.
Sent from my MB860 using XDA App
Atrix 4.1.57 issues
I have had my Atrix for over a month with no issues. After the 4.1.57 update I have the following 3 issues:
1. The phone randomely reboots (never did this before the update)
2. The cell signal is much weaker; no signal in areas where it had signal before
3. Apps seems to start slower.
I called motorola technical support and asked if there is a way to un-install this update; the answer is NO, all they can come up with is a factory RESET which will not remove the update but will remove all my data and Apps.
I finally sent the phone to AT&T and got a replacement with 4.1.26 and it works fine, especially the battery life and the cell signal and no reboots so far.
(summarized below in tl;dr version)
Since my problem I need help with showed up after going back to stock + root, I thought I'd ask in general before filling up the ROM discussion in development about the problem that I found after updating to ICS (leaked).
Had an odd problem crop up on me with scrosler's CleanROM 2.2 SP1 running (will 'splain in a sec, and tl;dr sum-up at the end), so I relocked, flashed back to pre-OTA official firmware and then let the OTA run. All was good, and I was happy. I unlocked again, installed Amon Ra, reinstalled SU, and started putting in my happy-fun root required tools (Oh Titanium, I likes you so). Then, my problem reappeared.
So my problem is occasionally the touchscreen would act "wacky" at times. Specifically, while in my browser, sometimes when I tried to scroll while browsing, the display would act like I was using pinch-zoom. It acted like I was touching the top left corner of the display in portrait mode, and zoom-in/-out according to how I was moving my touch that I intended to scroll. Then I noticed that games which required multi-touch had significant problems reading constant touch on most of the top-half of the display (left half in landscape mode with the carrier name on the left). I like Age of Zombies, and while the game would start off running right, within 20-60 seconds, the movement virtual controller would rapidly turn on and off, leaving me able to fire but not move. Grand Theft Auto was unplayable, as every time I touched a direction key in driving mode, the system would lose track of my holding the gas.
Troubleshooting took a while, as I had installed a lot of apps, and made a few changes at once after everything appeared to run properly. Ultimately, the problem appears to be caused by underclocking, and I can't figure out how to kill that and lock myself at stock speed. Haven't tried an overclocking capable kernel to see if they run any better, and haven't tried checking voltages to see if bumping them on underclocks would fix it.
I have used Antutu CPU master, an old version of SetCPU, and System Tuner Pro (from 3c). I can set the min and max CPU to 1.52, and it seems to stay for a while, but eventually, the setting reverts to allowing underclocking and my touchscreen gets goofy.
tl;dr: My system, even after restoring to RUU/OTA, wants to underclock. When the CPU runs under stock speed, my touch-screen misbehaves, particularly in gaming, but also in browsing. Any help?
Thanks
Can almost definitely confirm it's just bad hardware at this point.
After running 2 days without problem other than the touch-screen issue noted above, the phone entered an persistent bootloop after I loaded Juice Defender today. Phone would reboot, come up to home screen, get a data connection, tell me how many new email and texts I had, then tell me an app (same every reboot) was not responding and reboot 2-3 seconds after I cleared the error. Even when I managed to get to market before a reboot and uninstall the last 2 apps I'd installed, the phone is still in a boot loop.
Appreciate all that took the time to read, and wanted to share that there's a pretty good reason no one could respond with a solution.
Well, it probably is bad hardware but two cardinal rules I have when working on any Rezound is NEVER restore with Titanium BU & don't use Juice Defender (and I have a paid version of it).
I have had both mess up certain phones & I do this stuff all day at work.
I only noticed the underclocking issue with the ICS roms. But, I believe it is due to the Kernels not supporting under/overclocking and scaling options yet.
AtLemacks said:
I only noticed the underclocking issue with the ICS roms. But, I believe it is due to the Kernels not supporting under/overclocking and scaling options yet.
Click to expand...
Click to collapse
I've had the same issue for a while now and nobody answered Me either. After a little research it seems we have bad digitizers. I say this because that was happening to me on gingerbread and I upgraded to ice in part to fix it.
Sent from my HTC Flyer P510e using xda premium
Me 2
aostl said:
I've had the same issue for a while now and nobody answered Me either. After a little research it seems we have bad digitizers. I say this because that was happening to me on gingerbread and I upgraded to ice in part to fix it.
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
Okay so I have a similar problem.
I have hephappy cm9 prefinal installed just started having problems with rom. screen was acting funny so I turned on the touch point developer tool supplied with the rom. I have found that I have multiple touch points when scrolling with one finger.
So I used a apk called touch recalibrate that I got when I was on mik's cm7.
Which I have recalibrated aprox 7 times with no improvements so I set my cpu to min 600 max 600 smartassv2 this did not help either. If anyone has the answer to this problem please let me know.
Hey guys,
I have been running Entropy512's US kernel on my stock, rooted XXKPL YP-G70 for a while now. I have been suffering from random 1-2 second freezes, and capacitive buttons go dark, every once in a while. I noticed others also seem to have experienced it as well from the posts in the kernel's thread (Can't post there yet as I have not gotten 10 posts). I tried changing scheduler to noop, which does lessen the frequency of occurrence of the freezes but they are still there. I am using ext4, checked with mount in adb shell, so I don't think it is rfs lag. The freezes are usually random, but I can reproduce them somewhat consistently by repeatedly scrolling through a list or something (like songs in the music player, or a website, etc.) very fast. Got it to freeze about 4 times within 5 minutes. I tried to see if something showed up in logcat and I saw that every time this freeze happened, it showed:
W/PowerManagerService< 132>: Timer 0x7->0x3:0x0
in the logcat. What is that? It shows up without fail every time I get the freeze. Did anybody ever have any luck with figuring out what is going on? I suppose I can live with it, but it gets a bit annoying sometimes.
Thanks
divergens said:
Hey guys,
I have been running Entropy512's US kernel on my stock, rooted XXKPL YP-G70 for a while now. I have been suffering from random 1-2 second freezes, and capacitive buttons go dark, every once in a while. I noticed others also seem to have experienced it as well from the posts in the kernel's thread (Can't post there yet as I have not gotten 10 posts). I tried changing scheduler to noop, which does lessen the frequency of occurrence of the freezes but they are still there. I am using ext4, checked with mount in adb shell, so I don't think it is rfs lag. The freezes are usually random, but I can reproduce them somewhat consistently by repeatedly scrolling through a list or something (like songs in the music player, or a website, etc.) very fast. Got it to freeze about 4 times within 5 minutes. I tried to see if something showed up in logcat and I saw that every time this freeze happened, it showed:
W/PowerManagerService< 132>: Timer 0x7->0x3:0x0
in the logcat. What is that? It shows up without fail every time I get the freeze. Did anybody ever have any luck with figuring out what is going on? I suppose I can live with it, but it gets a bit annoying sometimes.
Thanks
Click to expand...
Click to collapse
I've never experienced anything like that with EDD. However, it's been a long time since I've used it. I don't recommend posting in that thread. It's an old thread and Entropy512 does not support it anymore. If it were me, I'd wipe everything and start fresh. I bet you don't get any "freezing" on a fresh install. It's most likely an app, combination of apps or too many running apps... Just some thoughts though... Hope it helps.:laugh:
Thanks for the reply Meticulus.
Yeah, I have tried completely wiping my player and starting from stock with Entropy512's kernel. Tried with the original 2.3.5 US firmware, XXKPH, XXKPL, and still get the same freezing. Only happens with his kernel as well. Oh well, I think I am just gonna go back to stock. When I get more time, I think I am gonna try SlimKat, it looks pretty functional and now that the camera is somewhat working (nice job on that by the way:good, I could see myself using it daily . Gingerbread is pretty hard to use now that I have gotten used to using my Nexus 7 and Moto G :laugh:.
Good afternoon-
Great phone, but has anyone else had bad operating system luck? Seems like my phone is freezing and/or locking up daily, and needs to be re-booted. If it were windows I'd call it a BSOD incident. My S3 running Paranoid Android nightlies was even more stable than this.
Tim
I am not having problems like you report at all. The only lockups I had were during the brief period when I ran under ART, and they went away completely after I switched back to Dalvik. Note that under ART my G3 got really hot...
That is what I think is causing most of these phones troubles. I think they were designed in a way that is prone to overheating issues. I also think the designers tried their best to avoid overheating through throttling - which causes some performance degradation, and doesn't always work anyway.
Minor assembly differences could be causing major differences in how different G3s heat-load. This could explain why some owners who have reported lockup issues like yours have gotten much improvement by exchanging their phone, which is what I suggest you do if you can.
moonfarm said:
Good afternoon-
Great phone, but has anyone else had bad operating system luck? Seems like my phone is freezing and/or locking up daily, and needs to be re-booted. If it were windows I'd call it a BSOD incident. My S3 running Paranoid Android nightlies was even more stable than this.
Tim
Click to expand...
Click to collapse
I agree with Trent. Seems some G3s just don't run well. Mine runs great. I have it rooted with xposed and have removed the bloat and no issues at all. I couldn't be happier.
I've even played some games for the first time on my smartphone including Asphalt 8 and I've played it for about an hour non stop the other night while I had time to kill and still no issues, the game played great, phone didn't heat up and get laggy.... Nothing. It just played.
Hard to say really what's causing the issues for some, could be a funky device, maybe a factory reset would help... Maybe people also should take a look at what apps and widgets they have running as well prior to thinking the phone is junk lol not saying that's you, just an idea
- Tapatalked from the G3
moonfarm said:
Good afternoon-
Great phone, but has anyone else had bad operating system luck? Seems like my phone is freezing and/or locking up daily, and needs to be re-booted. If it were windows I'd call it a BSOD incident. My S3 running Paranoid Android nightlies was even more stable than this.
Tim
Click to expand...
Click to collapse
No problems with mine.
What apps and widget are you using?
tech_head said:
No problems with mine.
What apps and widget are you using?
Click to expand...
Click to collapse
It's a pretty random problem, hasn't happened for a couple of days. I run a pretty lean system, not a lot of apps or widgets. Maybe getting rid of some bloat would help. Thanks all, nice to know it's not something everyone is going through. I'm enjoying the phone more than I thought I would, been on the S series since the first Galaxy Fascinate, so this was a bit of a leap. The combo of Knox and Touchwiz did me in...
Tim
I'm wondering if the accessibility service has anything to do with these random shutdowns. I've never turned on ART, but with several xposed mods, tweaksbox, and some debloating, my phone seemed stable for the first few weeks I owned it. One day I had a random reboot. It didn't happen again for a week or so, and then it happened once more. A few days later I noticed one of my tasker scripts (which reroutes gmail notification sounds through the headset iff the headset is connected) wasn't working. I checked the tasker accessibility service and it had turned itself off. After re-enabling it, my random shutdowns soon returned.
Anyone care to try ART with all accessibility services uninstalled? This would include talkback.