I got a new Nook HD+ in June. I kept it on stock, until about October, when I flashed cyanogenmod 10.1.3, then 10.2. The lag slowly became worse and worse until it was almost unuseable. I finally found a thread saying to format data and datmedia, so I did. This fixed the lag, but it started to come back. This is almost certainly a trim bug, but I know almost nothing about that (I am in middle school ). I do not want to format again, so I don't know what to do. Right now, I am on cm11.
If you are on CM11 then trim is enabled so it will run when certain conditions are met. I have found the easiest way is to plug it in overnight. Trim will run if the Nook is charging and has been idle for a period of time. Hope this helps
Thanks!
kokercey said:
If you are on CM11 then trim is enabled so it will run when certain conditions are met. I have found the easiest way is to plug it in overnight. Trim will run if the Nook is charging and has been idle for a period of time. Hope this helps
Click to expand...
Click to collapse
Thanks for responding. I had daydream on, so I don't know if trim ran or not. It seems like the lag is slowly getting better, but that may be the placebo effect. Is there a way to see if trim has run or is there another way to run it? Thanks!
There is a command line that can be run in Terminal that will check the log of the last trim run. I used it once to be sure trim ran BUT i do not remember the command. Do a search of the forum and you will find it.
kokercey said:
There is a command line that can be run in Terminal that will check the log of the last trim run. I used it once to be sure trim ran BUT i do not remember the command. Do a search of the forum and you will find it.
Click to expand...
Click to collapse
I'm sorry, but I can't find it anywhere. Could you find it?
Read this thread carefully and you will find the info you are searching for. You may have to link to another thread. It's the "Teach them to Fish" thing
http://forum.xda-developers.com/showthread.php?t=2528009
kokercey said:
Read this thread carefully and you will find the info you are searching for. You may have to link to another thread. It's the "Teach them to Fish" thing
http://forum.xda-developers.com/showthread.php?t=2528009
Click to expand...
Click to collapse
On that thread, I found instructions to run trim manually from Terminal. I did it and my nook was a little bit faster, but still significantly laggy than it is supposed to. I have started to think that the lag may not just be trim. Could this be true? Also, I ran Androbench and my random write was only .11 mb /s.
Also, I have the MAG2GA chip. Will this affect the speed of my nook?
When I run trim from the command line, it always says that it trimmed the same number of bytes each time, even if it is just a few seconds after. Is it supposed to do this?
Thanks again for all your help!
Related
my nexus one is charging on a regular basis around 106-7 F. I know there is another thread about this issue but the question was not resolved. So does anyone have experience with this issue. Is it a defect or dangerous? I have OSmonitor installed, this si where I am reading my temps. I also notice the CPU usage is pegged around 98-99%..is this normal?
I heard using setCPU with a charging profile can solve this problem if you have root?
No, it is not normal for the cpu to be maxed out while charging. Are you using the car dock or a wall charger?
nexous one
mine does the same thing all the time its not going to damage your phone at all
my phone has got about 120 F on car doc
my phone is perfect just set your set cpu for fail safe and your all good
You probably could use SetCPU to solve this problem, but the fact that your CPU usage is so high in the first place means there is something going wrong - my guess would be a rogue app.
Try downloading a task killer from the Market. Kill each app running one at a time then check your CPU usage. You'll soon find the culprit.
sn95chico said:
my phone has got about 120 F on car doc
Click to expand...
Click to collapse
Yeah I'm starting to see the problem with the phone having a metal casing. Not good when it's summer and you have to place it under direct sunlight for extended amounts of time, while using navigation AND charging
That thing can get burning hot alright.
Are you using froyo 2.2?
I have had the same problem; I also have random periods of high cpu use when not charging as well. This issue is not caused by problem apps either. I must reboot to fix the issue, sometimes I must reboot several times until the cpu load is back to normal.
I am not sure it is a bug or a hardware fault. Maybe a quick call to HTC and/or google is in order.
I will also try to reapply the 2.2 update.
Marine6680 said:
I am not sure it is a bug or a hardware fault. Maybe a quick call to HTC and/or google is in order.
Click to expand...
Click to collapse
Been there, done that. I opened a thread asking other users about the problem, and even mailed HTC's support. In the end I decided to try flashing the stock 2.1 rom again to see if the problem persisted, and it didn't.
I'm pretty sure it's not a hardware problem, but you might want to install eclair too and see if it works for you.
frandavid100 said:
Been there, done that. I opened a thread asking other users about the problem, and even mailed HTC's support. In the end I decided to try flashing the stock 2.1 rom again to see if the problem persisted, and it didn't.
I'm pretty sure it's not a hardware problem, but you might want to install eclair too and see if it works for you.
Click to expand...
Click to collapse
I bet your heat issues are related to cpu loads or staying at high frequencies like mine. Sometimes the phone does not feel like it is really running as hard as the system monitors say, though it may still get hot.
Where can I find the older ROM? I thought the bootloader would not allow going to older ROMs, or maybe I am mistaken.
I am re-flashing the leaked 2.2 update to make sure there was no issue with the original install. I am also using the copy my GF downloaded when I sent her the instructions on the off chance that my download was corrupted in some small way; unlikely but hey. I do think that the original flash may have gone wrong, as mine hung and never rebooted after the flash was complete; I had to manually reboot. Lets hope this fixes it.
This issue may be more widespread than we realize, as many people do not actively monitor their cpu or notice/worry about the heat after charging. I do believe that these leaked ROMs send debug data to google, I remember reading something along those lines; these are internal test ROMs after all. Maybe this is a reason that 2.2 is not out yet, this and other bugs found during real world use.
Marine6680 said:
Where can I find the older ROM? I thought the bootloader would not allow going to older ROMs, or maybe I am mistaken.
Click to expand...
Click to collapse
What I did was follow this guide up to the point where you have a stock eclair rom, then not upgrade to Froyo. Keep using that for some time, see whether the phone gets hot or not, THEN (if you want) move back to Froyo.
I am using the wall charger hat came with the nexus one. I am also running Froyo 2.2... can I set a CPU fail safe without my phone being rooted? Also what is a quick to check if my phone is rooted? I just bought this Nexus One from someone. I know on my G1 it was rooted bc I had Superuser permissions.
Using OSmonitor I can sort the processes by their CPU load and the one process that always has the highest load is " /init" which always has around 85-96% of the load. You can also kill these processes directly inside of OSmonitor and I have tried killing " /init" to no avail.
The fastest way I can think would be installing Lamppu, then trying to use it to light up the camera flash. If it works your phone is flashed, if it doesn't it's not.
As for your other questions... sorry, i don't know. I hope someone else can help you.
foethalove said:
Using OSmonitor I can sort the processes by their CPU load and the one process that always has the highest load is " /init" which always has around 85-96% of the load. You can also kill these processes directly inside of OSmonitor and I have tried killing " /init" to no avail.
Click to expand...
Click to collapse
Thats a system process so you can not kill it.
Going to test my GFs nexus and see if she has these issues as well.
I restored my N1 to the factory image, the updated back through each update to 2.2; so far so good. My GF's N1 has been running fine since I really started watching it, so I figured it would hurt to try to restore and redo the update.
No 100% cpu load during charging any more!
i am using the Motorola charger and my phone is not getting hot at all. with the charger that comes in the box for the N1 it seems to heat up.
Still had the CPU load get stuck at 100% today; though charging is not forcing 100% loads any more.
By the way, how do you measure how busy the processor is? How do you know that it's at 100%?
frandavid100 said:
By the way, how do you measure how busy the processor is? How do you know that it's at 100%?
Click to expand...
Click to collapse
System monitor apps, some will even put a little icon in the notification tray that shows current cpu load.
Hi,
after spending some fruitless hours trying to get better GPS performance from my p990 (cm7 nightly 60-64, baseband 0218, cm7 RIL), trying various tweaks to gps_brcm_conf.xml and even older versions of glgps, I've concluded (tentatively) that
- /data/gps/lto.dat is a file (containing ephemerals?) that's used for A-GPS
- my setup never manages to download this file.
Following this thread of thought, I tried the following (The URL is from a google search while I was digging about in gps_brcm_conf):
Code:
adb shell
cd /data/gps
wget http://gllto.glpals.com/7day/latest/lto.dat
chmod 777 lto.dat
I also did
Code:
rm gldata.sto
to remove (I think) stored orbital data from previous fixes to try to keep the results comparable.
Though measuring GPS performance is difficult due to constantly changing constellations and atmospheric conditions, I think this has made a difference in time-to-fix for me. Admittedly this might just be a placebo, so no guarantees.
If anyone wants to try this and post their results, it'd be great. And, if anyone knows anything about lto.dat, why its needed, and why it never gets downloaded, please post here so I won't be kept awake at night wondering
It might be that the Tegra2 setup doesn't use it, much like gps.conf.
Best bet would be to ask RC I suppose, although he's a bit tied up with some GPL stuff apparently.
Rusty! said:
It might be that the Tegra2 setup doesn't use it, much like gps.conf.
Click to expand...
Click to collapse
It's referred to in gps_brcm_conf.xml (the chip-specific config file), so I've assumed it's relevant to our setup. But yeah, it's possible.
Best bet would be to ask RC I suppose, although he's a bit tied up with some GPL stuff apparently.
Click to expand...
Click to collapse
Yeah, I'll hold off on that a bit.
Would be interesting to know if anyone actually has that file in /data/gps. I'll try to find time for a restore to stock (or at least modaco) to see if it gets downloaded in the standard setup. We'll see.
nrkabul said:
It's referred to in gps_brcm_conf.xml (the chip-specific config file), so I've assumed it's relevant to our setup. But yeah, it's possible.
Yeah, I'll hold off on that a bit.
Would be interesting to know if anyone actually has that file in /data/gps. I'll try to find time for a restore to stock (or at least modaco) to see if it gets downloaded in the standard setup. We'll see.
Click to expand...
Click to collapse
don´t have it on cm .64 either ...
Just created the missing file, and got a lock from stone cold, indoors pretty fast. Did that file help? Dunno lol
Will have to test more.
OK... here is my extremely unscientific test...
GPS Status without lto.dat: 43 seconds to lock.
GPS Status with lto.dat: 19 seconds to lock.
aGPS data was cleared before each test. Interesting, but far from conclusive.
Whooo! This is amazing!
Tried to lock inside without lto.dat, no luck at all after 70+ seconds... Copied the file into /data/gps, tested the same spot and got lock after cca 10 seconds!
This is amazing
nrkabul said:
Hi,
And, if anyone knows anything about lto.dat, why its needed, and why it never gets downloaded, please post here so I won't be kept awake at night wondering
Click to expand...
Click to collapse
This might be of interest then: http://www.broadcom.com/collateral/tb/LTO-TB100-R.pdf
nrkabul said:
Hi,
after spending some fruitless hours trying to get better GPS performance from my p990 (cm7 nightly 60-64, baseband 0218, cm7 RIL), trying various tweaks to gps_brcm_conf.xml and even older versions of glgps, I've concluded (tentatively) that
- /data/gps/lto.dat is a file (containing ephemerals?) that's used for A-GPS
- my setup never manages to download this file.
Click to expand...
Click to collapse
Good find. That file basically holds an analog to XTRA data; It doesn't quite help picking up satellites, but it makes locking onto them a hell of a lot faster once they're found.
TrymHansen said:
This might be of interest then: http://www.broadcom.com/collateral/tb/LTO-TB100-R.pdf
Click to expand...
Click to collapse
Ah. Yes, that explains it nicely. Thanks.
Sent from my Optimus 2X using XDA App
aremcee said:
Good find. That file basically holds an analog to XTRA data; It doesn't quite help picking up satellites, but it makes locking onto them a hell of a lot faster once they're found.
Click to expand...
Click to collapse
Indeed. That matches what I've observed.
Any idea why the download doesn't happen?
Sent from my Optimus 2X using XDA App
Download will happen for the next nightly, this is going to please a lot of people; top bombing.
This is truly awesome, hope it might have some small influence on apps keeping gps alive when screen is turned of too... Maybe a little too much to wish for, but..
Thanks send to nrkabul
It wont, that's just how Android works... my stock N1 was the same.
Endomondo excepted, that should be able to hold a lock, but doesn't. Run Keeper does it fine though.
Rusty! said:
It wont, that's just how Android works... my stock N1 was the same.
Endomondo excepted, that should be able to hold a lock, but doesn't. Run Keeper does it fine though.
Click to expand...
Click to collapse
I had stock rom, Gilgamesh and the first one WGLpoelstra posted, and Endomondo worked flawlesly on those roms, dont know what happened to GPS since then, but on CM7 i have to use My Tracks in the background to make sure that Endo records track.. Havent heard about keeper before, will check it out
Rusty! said:
Download will happen for the next nightly, this is going to please a lot of people; top bombing.
Click to expand...
Click to collapse
Ah, quick work by arcee. I'd already cobbled together an app to do it for me, but this will be a lot better. Fingers crossed for a usable GPS
Sent from my Optimus 2X using XDA App
another workarround: Install this https://market.android.com/details?id=net.canaryx.gpsaids&feature=search_result
and download lto file. open root explorer /data/gps and rename lto2.dat into lto.dat
ionhide said:
I had stock rom, Gilgamesh and the first one WGLpoelstra posted, and Endomondo worked flawlesly on those roms, dont know what happened to GPS since then, but on CM7 i have to use My Tracks in the background to make sure that Endo records track.. Havent heard about keeper before, will check it out
Click to expand...
Click to collapse
It's a pain, and odd the Endomondo can't do it, when others can. If they all couldn't it would be an obvious problem, but when it's just that one (the one I happen to use at that) it's frustrating.
Still, as you've noticed, there is a work around, this might be less hassle than having My Tracks going though: https://market.android.com/details?id=com.kaukovuo.android.trackerbooster
lto.dat works great for me !!
got a fix in my car in about 5 sec, some seconds later got 10 satelites fixed !
GPS works like it did on MCR Rom for me now !
great discovery !
Rusty! said:
It's a pain, and odd the Endomondo can't do it, when others can. If they all couldn't it would be an obvious problem, but when it's just that one (the one I happen to use at that) it's frustrating.
Still, as you've noticed, there is a work around, this might be less hassle than having My Tracks going though: https://market.android.com/details?id=com.kaukovuo.android.trackerbooster
Click to expand...
Click to collapse
I tried that app, and it didnt work for me, thats why i use My Tracks..
Sent from my Optimus 2X using XDA App
I would have posted this in the development forum in the KANG thread, but I cannot because I lack the ability to do so, and yes, I read the thread for this already. I am just having a problem finding 10 things to reply to to get access to post in that forum, and I do not want to run around posting random crap all over the forum that don't add anything. Maybe someone will merge this thread into the development thread for that or something.
I am having issues (on my Nook at least) with the latest build of KANG's 7.2-RC1
I am not posting looking for a fix, or a suggestion. I just want someone running this to try it for a day or two and see if it occurs with you...Mainly wondering if my problem is this release, or my Nook going to crap.
Basically, if i enable "create shortcuts to applications automatically" in the Play Store settings, my Nook Color locks up every now and then while installing apps.
The best way I have found to reproduce this is to start an install of multiple apps from your computer, and just let it run. I did have it also lock up on a manual install of the MyWater APK that was patched up for Nook Color...
Anyway, someone see if you can reproduce this on your end.
Well for the first time in 2 days it has locked up since i turned that feature off while installing something from the Play Store.
I will wipe/reinstall 7.2 and hope for the best. I do not see any replies to this, and I still do not see any similar reports on these forums or forums like it...so cross your fingers please
well since i was obviously faced with a reinstall anyway threw ICS onto my NC and took it for a test drive. for as early as it is it was really pretty impressive. i felt dirty when it was time to do the 7.2-rc1 reinstall... but i finally broke down and did it.
so far the nook has done installs of about 30 apps and has not skipped a beat. something was flaky with emmc so i wiped it and reinstalled clockwork mod, 7.2, did a data/cache wipe, and then installed the market... booted, market updated, and everything has been smooth ever since.
guess i solved my own problem
I've seen some info about Nook HD+ touchscreens having lag and unresponsiveness problems, but that was with an old version of the stock firmware and occasional bad microSD cards.
Has anyone had this problem with the current CM10.1 ROM?
I upgraded to CM10.1 over the weekend and I'm having all kinds of touchscreen problems since changing over. I frequently have to tap two or three times (the last time being very slow and deliberate - and a little more forceful because it is pissing me off) and sometimes have to hold a tap in place so that it will register.
If all else fails, I'm going to go back to stock, but I'd rather not. I'll probably try re-downloading and re-installing CM10.1.
Look at the HD+ native CM10.1 discussion. There has been a lot of talk about that the last few days.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Look at the HD+ native CM10.1 discussion. There has been a lot of talk about that the last few days.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I'm doing this right now. I just got the N+ with the 06/15 emmc build. It certainly does not feel as smooth as the Nexus 7 around the Launcher and apps: it feels like the whole system is running at 20FPS(exception is Boat Browser, Youtube, and other minority apps). I'm still looking at this time hoping that the higher resolution isn't the limiting factor on the OMAP4 hardware.
leapinlar said:
Look at the HD+ native CM10.1 discussion. There has been a lot of talk about that the last few days.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Thanks Leapinlar! :good:
The post that is most meaningful in for this issue in that thread is #834:
http://forum.xda-developers.com/showpost.php?p=42645288&postcount=834
Where it points you to an app that seems to fix the problem - even if that fix is only temporary. Here's the app:
https://play.google.com/store/apps/details?id=com.assid.android.nookrecalibrate&hl=en
Tom2112 said:
Where it points you to an app that seems to fix the problem - even if that fix is only temporary. Here's the app:
https://play.google.com/store/apps/details?id=com.assid.android.nookrecalibrate&hl=en
Click to expand...
Click to collapse
This fix worked great for me as well. Is this a "permanent" fix in the sense that I only have to do it once? or will there be a need to do it again (e.g., after reboot?
Thanks
That's useful to know about the recalibrate app, I may use in the future.
This is a bit obvious but I've found a good clean of the screen helps.
srgibbs99 said:
This fix worked great for me as well. Is this a "permanent" fix in the sense that I only have to do it once? or will there be a need to do it again (e.g., after reboot?
Thanks
Click to expand...
Click to collapse
I think it is something that will need to be repeated. The gurus over in the other thread imply that it is something that degrades over time.
Also, as mdwsmith suggests, it is helpful to keep the screen clean. The Nook HD+ seems very susceptible to greasy fingerprints messing with the touch sensitivity - more so than any other tablet/phone I've used.
Tom2112 said:
I think it is something that will need to be repeated. The gurus over in the other thread imply that it is something that degrades over time.
Also, as mdwsmith suggests, it is helpful to keep the screen clean. The Nook HD+ seems very susceptible to greasy fingerprints messing with the touch sensitivity - more so than any other tablet/phone I've used.
Click to expand...
Click to collapse
Thanks Tom, i have noticed that having fingers/screen very clean helps.
Open up the developer options in settings and enable "Show touches" and "pointed location." Use the device with these options on to see a trace of how the touchscreen registers your touches. You start to get an idea of how sensitive the touchscreen is. You can also clearly see why some touches don't register sometimes. I touched the screen to click a button but it thinks I want to scroll because the trace shows I made the slightest of a line when I pushed down on the screen.
Sent from my Barnes & Noble Nook HD+ using Tapatalk HD
I installed a matte/non-reflective screen protector on my Nook HD+ because I had read elsewhere that it would help the touch sensitivity issues.
It didn't. So I will probably remove it.
verygreen has a thread up with a zip you can flash that did wonders for my touch screen. check it out
bckrupps said:
verygreen has a thread up with a zip you can flash that did wonders for my touch screen. check it out
Click to expand...
Click to collapse
Thanks! I will check it out.
Here's a link for those that find this thread first:
http://forum.xda-developers.com/showthread.php?t=2347003
I found on my Nook HD+ that when the touchscreen starts acting wonky like this it wants to be cleaned. *Especially* ( and sometimes only ) where the glass meets the bezel. I wrap the cleaning cloth around my finger and angle my nail in at about 45 degrees, and gently but firmly 'scrub' around the bezel edge. I can actually feel a buildup there physically from the varying friction of my movement. After that is starts acting like it did ootb.
Tom2112 said:
I've seen some info about Nook HD+ touchscreens having lag and unresponsiveness problems, but that was with an old version of the stock firmware and occasional bad microSD cards.
Has anyone had this problem with the current CM10.1 ROM?
I upgraded to CM10.1 over the weekend and I'm having all kinds of touchscreen problems since changing over. I frequently have to tap two or three times (the last time being very slow and deliberate - and a little more forceful because it is pissing me off) and sometimes have to hold a tap in place so that it will register.
If all else fails, I'm going to go back to stock, but I'd rather not. I'll probably try re-downloading and re-installing CM10.1.
Click to expand...
Click to collapse
I'm on CM10.1 too and faced the same tapping lag - third time is very slow. I lost almost 40 hours of testing, testing and more testing of this nasty lag and there is no result for now, maybe it's some option in the phone that eliminates the lag but I can't find it for 40 hours... But I'm sure for one thing - if the slow tap is ALWAYS the third time, then the reason is some setting. There is nothing in your hardware/performance, be sure about that. Just searching for solution......
Hey guys,
Long time lurker and follower of the site but my first post and I need some advice-
The screen on the kindle fire HD sometimes becomes unresponsive. The buttons like power and volume still work fine, just the touch screen itself seems to be the issue. It only seems to occur when memory/processor load starts to climb (like it's being dumped for space or something) and I can sometimes, SOMETIMES, hit the power button to lock it and unlock it to gain control again then I have to immediately close out of what ever app I'm in and close all running tasks.
While watching the memory available the lowest I've seen it drop to is around 125mbs and still not have an issue, or maybe it's spotty. Not fully out, but getting there.
This is also unrelated to the power issue I've seen posted, that when it's plugged in it can occur as well. Doesn't seem to care too much if plugged in or not.
This started on stock rom so I flashed it and installed cm11 which has definately improved the problem but not solved it.
So, just polling the minds of people here to see if anyone has a suggestion.
Latonya1 said:
i had same problem and what i did is i opened battery from the device and inserted its again and did a factory reset on my device
Click to expand...
Click to collapse
Removing the battery on the kindle isn't an easy feat. Are we talking about the same device, or did you attempt this on a phone? Because if this worked with the kindle, I am more than happy to put the time into trying but I want to make sure.
Thanks for the reply.
dlenoxx said:
Hey guys,
Long time lurker and follower of the site but my first post and I need some advice-
The screen on the kindle fire HD sometimes becomes unresponsive. The buttons like power and volume still work fine, just the touch screen itself seems to be the issue. It only seems to occur when memory/processor load starts to climb (like it's being dumped for space or something) and I can sometimes, SOMETIMES, hit the power button to lock it and unlock it to gain control again then I have to immediately close out of what ever app I'm in and close all running tasks.
While watching the memory available the lowest I've seen it drop to is around 125mbs and still not have an issue, or maybe it's spotty. Not fully out, but getting there.
This is also unrelated to the power issue I've seen posted, that when it's plugged in it can occur as well. Doesn't seem to care too much if plugged in or not.
This started on stock rom so I flashed it and installed cm11 which has definately improved the problem but not solved it.
So, just polling the minds of people here to see if anyone has a suggestion.
Click to expand...
Click to collapse
This happened to me once...however it was solved with me wiping the whole kindle in recovery(dalvick etc) and flashing the kindology rom.....good luck man :thumbup:
sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed
Seems like I have had that problem before, was because I had to many background processes running. I try to keep my ram so only about 60-70% of it is in use when using it, and I also stopped using dolphin web browser, that is a nice browser but man does it use up a lot of resources. On another note I noticed one time my kindle had around a GB left on the internal storage it started getting sluggish so that's another thing to look out for, but I doubt it's the root of your problems. Kinda find it annoying that android uses as much ram as it does, its based on Linux but on a desktop is on my PC with 2gb of ram, it idles at 20% on Ubuntu(which would be like 40% on a kindle because it has half as much ram), whereas android idles at around 60%.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
itouchables said:
This happened to me once...however it was solved with me wiping the whole kindle in recovery(dalvick etc) and flashing the kindology rom.....good luck man :thumbup:
sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed
Click to expand...
Click to collapse
I should have read over what kinology was before flashing it.. I'm sure it's a great rom, but I'm wanting something more android-e. Went great though, as far as the install- and thanks for the tip. Worse case I'll have that file to fall back on.
stunts513 said:
Seems like I have had that problem before, was because I had to many background processes running. I try to keep my ram so only about 60-70% of it is in use when using it, and I also stopped using dolphin web browser, that is a nice browser but man does it use up a lot of resources. On another note I noticed one time my kindle had around a GB left on the internal storage it started getting sluggish so that's another thing to look out for, but I doubt it's the root of your problems. Kinda find it annoying that android uses as much ram as it does, its based on Linux but on a desktop is on my PC with 2gb of ram, it idles at 20% on Ubuntu(which would be like 40% on a kindle because it has half as much ram), whereas android idles at around 60%.
Click to expand...
Click to collapse
As I've been doing a bit more testing trying to figure out what is going on, it does seem to happen more often when under 100~75mg of memory available. Idling now at 550 memory available now, thanks to a few tweaks here and there which has almost erased the problem when doing things like browsing the internet, youtube, netflix, etc. It's just happening now during games. Not as much- but still, in the middle of a game of Kingdom Rush it's a little frustrating to all of sudden have no control. And currently I've still got almost 7 gigs of space available as far as harddrive goes so that doesn't seem to effect it by much (at least for me).
Setting the I/O to noop, overclocking to 1500 (leaving the minimum to 350), and setting the zram compression to 28% were the tweaks. Also having Task Killer by rechild set to kill tasks when screen off has been a great fix when I do lose the touch pad controls as it'll free up some memory when I turn it off, leave it off for a minute, then turn it back on without really interrupting progress in several apps.
Still searching for a true, 100% fix so tips are still welcome and I'll keep everyone posted if I run across anything myself.