I've noticed it ocasionally on my Atrix HD for quite a long time but though it was just my phone. I got my SO the same phone and the same thing has been occurring. It doesn't happen all that often, but when it does, it's very frustrating. It still functions underneath: if it's in a phone call or playing sound, you can adjust the volume. Can take screenshots, or hold power button and it will vibrate (e.g. when the menu pops up).
We are both on CM11 M snapshots and running xposed with nlpunbounced. I believe I remember it occurring before we started using xposed. Also, we've been on CM11 since something like M3. Have run fstrim on all of the partitions (except for my /data partition since I encrypted it, and last I checked the fix for fstrim on dmcrypt wasn't ported to our phone). Anyways, does anyone else have this problem? If not, what could it be? Being an very occasional thing, it's hard to test and capture logcats from.
For anyone curious about this, it's been called the "I/O Stall" in the razr hd thread. They suggest a solution, which I'm trying out:
http://forum.xda-developers.com/showthread.php?p=57605249#post57605249
I have switched to the F2FS and it seems much less common, so we'll see how much the swappiness setting helps.
Related
OG Droid with Liquid Smooth 3.2 (same problem with 3.1). I haven't tried many other roms, so I don't know if this is a problem with my hardware (the phone is refurb and only 1 month old) or if I installed something that is breaking things.
The issue: If I receive a call the phone will allow me to answer (move slider) but then lock so that the call is in speaker phone mode (or at least very loud) and I cannot control anything on the screen. The power button will turn off the screen, but that's it. The other person apparently cannot always hear me, so I don't know if the mic is working at that point. If I let the call end, the phone does not recover. The only way to recover seems to be to pull the battery.
Last time this happened, the caller could hear me so I let the call end. After a minute or two, com.android.phone popped a force close message. A minute later, another app popped a force close. It did not recover even after an hour or so. Battery reset worked.
This issue is not consistent. It occurs maybe 1 out of 20 incoming calls. I had the issue on LS3.1, so I upgraded to LS3.2. Same issue. I can try another rom (CGM7.x), but I really like LS so I'd like to see if there is a resolution.
Is there a log mode I can enable to see if something consistent happens when the phone locks? I have a task killer installed. Could that be an issue? I'm not doing anything that I would have thought could be considered challenging for the phone (answering a phone call), so I'm not sure what to check.
I had this problem often on my droid 1. I ran CM7 nightlies and Prime's kernel at 1.1GHz.
Mostly it happened while I was doing other things with the phone. I think it was due to low RAM.
If you check settings - manage applications - running, how much free RAM do you have?
I usually had 40-50MB free and that wasn't enough.
Ditch whatever you can from your apps and OS to free some up.
TiBU allows you to chuck a lot of system stuff that's not really needed.
I would still be on my OG if it weren't for this problem, so I hope you find a solution that works for you.
A lot of people are on Steeldroid with the droid 1. It's still getting updates. Maybe try that.
-CM7 on DInc2
In general, this happens when the phone is just sitting there (nothing but the regular system stuff running essentially). The last time this happened where the force close messages appeared I had the web browser open. I hadn't considered ram, but that's a good possibility. I do have Advanced Task Killer running as a service, so perhaps that is related.
With ATK non running, it says I have 115MB used/64MB free. 15MB of this used memory is for settings.
With ATK running, it claims 68-79 free (it's set up to kill tasks since I was worried about memory hogs originally).
I'll look into Steeldroid. Like I said, this is a new phone. What I didn't say is that my wife got it for me to see if I would use a smart phone (was on an old lg texting phone before and this thing is physically much larger). She got it for super cheap, so if I have to go with something different, that wouldn't be the end of the world. If that were the path forward, can you recommend a couple good options with full slide out keyboards?
Thanks!
I dunno, I loved the physical keyboard on my old OG, but I left it behind when I jumped moto for HTC.
D2, D3, and D4 are supposed to be great improvements over the D1.
I see the dev for Steeldroid has a D3 version that's up to date. Maybe look for one of those?
I've always been a Motorola fan. Maybe I should have stuck with them, but I figured I'd have to get used to screen keyboards at some point...
I'd say try Steeldroid on your OG first, get a good kernel to go with it, ditch the task killer and let android handle it. See if that helps.
Good luck! B-)
-CM7 on DInc2
Hello, I am having some touchscreen problems with CM9 and 10, but not with webOS. Namely, I think that the tablet is detecting double or even triple taps when none are present.
In CM9, when I execute a longpress (to move an app for example), the tablet just kind of... spazzes out, and in general nothing happens. In CM10 it also does this, and almost everytime, it starts whatever app I was pressing on.
Also, when I try to type in the CM10 keyboard, 2-4 characters are being entered at a time, unless I touch incredibly lightly, and even then, I will often get two.
There are other symptoms along these lines, like trying to pull up the notifications, etc. This does not appear to be isolated to any one portion of the screen, it is happening everywhere I could check it.
This CM9 versions I have tried are the nightly 0715, and whatever the latest nightly was about a week ago. The CM10 version I am using is jcsullins' 12/16.
As stated, I have zero issues in webOS.
Is there any way to change the touch sensitivity? Am I a moron and doing something wrong?
Thank you for your help/advice.
To clarify, I think this might be two separate issues...
I'm not as concerned with the CM9 issue, as it is only a mild annoyance and everything else is outstanding. CM10 is virtually unusable, however, so I'm hoping someone can help me out there.
thatdumbguy said:
Hello, I am having some touchscreen problems with CM9 and 10, but not with webOS. Namely, I think that the tablet is detecting double or even triple taps when none are present.
In CM9, when I execute a longpress (to move an app for example), the tablet just kind of... spazzes out, and in general nothing happens. In CM10 it also does this, and almost everytime, it starts whatever app I was pressing on.
Also, when I try to type in the CM10 keyboard, 2-4 characters are being entered at a time, unless I touch incredibly lightly, and even then, I will often get two.
There are other symptoms along these lines, like trying to pull up the notifications, etc. This does not appear to be isolated to any one portion of the screen, it is happening everywhere I could check it.
This CM9 versions I have tried are the nightly 0715, and whatever the latest nightly was about a week ago. The CM10 version I am using is jcsullins' 12/16.
As stated, I have zero issues in webOS.
Is there any way to change the touch sensitivity? Am I a moron and doing something wrong?
Thank you for your help/advice.
Click to expand...
Click to collapse
I've not had this issue, but this might help. Go here : http://goo.im/devs/jcsullins/cmtouchpad/testing
Download the touch pressure utility (should be the last one) and flash it. Hope it helps.
Good luck.
As an update, after shelving the touchpad for a few months, I have revisited it, and, after doing a clean install of jcsullins' CM10.1 w/BT Fix (20130808), the same issues as above still persist. I've done the following, although I didn't really expect most of them to work:
Switching to stylus mode (no difference)
Changing the accessibility settings for touch & hold delay
Even went so far as to install another launcher (nova) to ensure it wasn't trebuchet (not that I think it was)
Same for the keyboard
This has never been an issue I've seen in webOS... additionally, I don't remember ever having any issues in CM7 either. I did play with webOS for some time today to make sure it wasn't some kind of hardware failure between now and the last time I used it frequently, but I failed to reproduce the problem there.
Is there any light someone can shed on the subject? Thanks!
Thanks for that Chicle_11... I don't know why I failed to mention it, but I did also try the patches with CM9, but it is to my understanding that they were rolled into cm9 nightlies at some point?
I wonder if I could be having a minor hardware issue that just isn't severe enough to display in webOS, because I can't seem to find anything else about this, especially the keyboard problem with CM10. Its bizaar for sure.
Started experiencing the same issues after upgrading from cm9
I recently upgraded from cm9 to cm10.2 and immediately noticed this issue. There were no such issues with cm9. When swyping on the keyboard (any - Google, Swype, etc.), the system registers that I lifted my finger, and so garbage gets typed - you can also see the effect in the trace. When typing instead, letters sometimes double-up for a single press. When playing games like PvZ2, dragging a plant results in a release of the plant before I've lifted my finger, and sometimes the plant gets planted across the screen from where my finger is pressing.
I had a similar problem(but worse) sometimes when using the stock rom.
I've replaced the stock rom and been using CM10.1 on emmc.
Sometimes when playing games the touch screen may become unresponsive but the 3 standard buttons still would work.
(as well as the hardware buttons.)
When this happens I'm not able to click on any of the icons on the home screen. (none of the control buttons work in game, either.)
I wonder if this is a hardware problem, CM10 problem, or a problem with the coding of the game (dungeon hunter 4.)
The problem actually does not last. Nook HD+ recovers by itself after about 1 minute.
Else, I could also click on the power button to turn off display and turn it back on.
Once it's back on everything is working including the in-game controls.
Does anyone have a similar problem?
I doubt this could be a bug in the game (Dungeon Hunter 4). The game is very buggy but when I play it on Nexus 7, I never experienced any control button issues. (Though it does crash "a lot" and sometimes more often than on the Nook HD+)
I had this experience before, just because of the memory going low so it needs time to respond. I advice you exit completely all your current apps and clean ram memory (also cache memory using Clean Master (Cleaner)) before playing games or heavy task. Also remember sometimes turn of completely device for few minutes and turn it back on to use. Hope this help
ndttung8487 said:
I had this experience before, just because of the memory going low so it needs time to respond. I advice you exit completely all your current apps and clean ram memory (also cache memory using Clean Master (Cleaner)) before playing games or heavy task. Also remember sometimes turn of completely device for few minutes and turn it back on to use. Hope this help
Click to expand...
Click to collapse
Thanks. I appreciate your help. I had this problem again today and I noticed the available ram was indeed quite low at the time.
Although it seemed unresponsive, it seemed more like being extremely slow.
Somehow if I turn off the display and turn it backs on it gets a bit better.
I suspect dungeon hunter 4 has a memory leaking problem. (memory not released completely if reload an area many times.)
I tend to have this problem if I load a lot of data in the game several times.
Strangely this does not occur on Nexus 7 based on the latest patch.
I searched in xda and it seemed last year Nexus 7 also had the same problem especially when playing certain games.
So I think this issue may come from rom which is used by nook hd+, with this issue i strongly recommend you post directly to verygreen original topic for him to discover. But if you can attacht catlog file also is better.
Here is his topic: http://forum.xda-developers.com/showthread.php?t=2263553
ndttung8487 said:
So I think this issue may come from rom which is used by nook hd+, with this issue i strongly recommend you post directly to verygreen original topic for him to discover. But if you can attacht catlog file also is better.
Click to expand...
Click to collapse
Thanks. I deleted the game as it is very buggy, crashes often and with many in game bugs. I'm finally done with it.
If I encounter the same issue with other apps I'll definitely upload the log.
I had it on all roms
Hi,
No, you are not alone. The issue occurred on all roms I used so far.
Indeed it mostly shows up in games, though I think I noticed it in other apps too occasionally.
I usually use the power button, but I'll try clearing the memory in the future...
M.
I have been using CM11 for a while now and I am experiencing frequents hangs and hiccups. In particular the systems doesn't seem to be able to handle an installation, what I mean is that whenever I install or update an app the system hangs like if it can't handle a multitasking session, the systems freezes. Also, I ofent have my device frozen and I can't turn it on, the screen stays black for long periods, in the order of 5 minuts or more. I'd say this ROM is not functional. Is there anyone else who is experiencing the same problems? I am not sure whether the ROM is not working properly because of some setting I changed but well... I was thinking about going back to stock or to re-format and start over with a fresh CM11 because it might also be that I did something wrong. Any comment or suggestion, personal experiences? is CM11 working on your xperia sp's?
Cellulario said:
I have been using CM11 for a while now and I am experiencing frequents hangs and hiccups. In particular the systems doesn't seem to be able to handle an installation, what I mean is that whenever I install or update an app the system hangs like if it can't handle a multitasking session, the systems freezes. Also, I ofent have my device frozen and I can't turn it on, the screen stays black for long periods, in the order of 5 minuts or more. I'd say this ROM is not functional. Is there anyone else who is experiencing the same problems? I am not sure whether the ROM is not working properly because of some setting I changed but well... I was thinking about going back to stock or to re-format and start over with a fresh CM11 because it might also be that I did something wrong. Any comment or suggestion, personal experiences? is CM11 working on your xperia sp's?
Click to expand...
Click to collapse
It did start lagging after a few weeks and for me the recent button took forever (3 secs ! thats a lot since it never took that much long) to open recent menu. So I reinstalled it not knowing whether it was my fault or CM and to my surprise after a few weeks it did it again and I switched to PAC rom. Never looked back. IMO pac rom is the best experience of kitkat on sp.
Hi there,
I have a C6903 with 16GB of storage. Baseband 8974-AAAAANAZQ-10270045-39. It ran fine under CM12.1 from last year. I recently updated to a CM12.1 nightly from August of this year. After that I started having problems with random crashes.
The phone would either freeze during operating, not responding to any input. I had to hard reset by holding the power button for a long time. This shuts the phone down. Then I start it and it boots up. Or the crash happens, when I am not using the phone, resulting in a black screen and an unresponsive phone. The fix is the same, shutting the phone down with a long press on the power button and then starting it up.
I switched from CM12.1 to AOSP Jaguar LP 5.1.1 from August (I haven't updated to September yet). I was crash free for three weeks, but now I am back with the same crashes. I found four crash logs in /data/anr, but I can't make much sense of them. I have them attached to the post.
The change in behavior when I install a new rom makes me think this could be software related, but getting the same crashes with two very different roms makes it look like a hardware issue.
What do you guys think? I don't want to go back to stock for testing, because I value privacy a lot and XPrivacy is so much work to set up right, IMHO. I like the privacy managers included with Jaguar or CM12.1 a lot. They are so much easier to use. But if I have to, I will go back to stock. Any other ideas? Can anyone interpret the crash logs? Is there anything useful there? Should I test something else?
Please help. Thank you for reading this post.
SpGG said:
Hi there,
I have a C6903 with 16GB of storage. Baseband 8974-AAAAANAZQ-10270045-39. It ran fine under CM12.1 from last year. I recently updated to a CM12.1 nightly from August of this year. After that I started having problems with random crashes.
The phone would either freeze during operating, not responding to any input. I had to hard reset by holding the power button for a long time. This shuts the phone down. Then I start it and it boots up. Or the crash happens, when I am not using the phone, resulting in a black screen and an unresponsive phone. The fix is the same, shutting the phone down with a long press on the power button and then starting it up.
I switched from CM12.1 to AOSP Jaguar LP 5.1.1 from August (I haven't updated to September yet). I was crash free for three weeks, but now I am back with the same crashes. I found four crash logs in /data/anr, but I can't make much sense of them. I have them attached to the post.
The change in behavior when I install a new rom makes me think this could be software related, but getting the same crashes with two very different roms makes it look like a hardware issue.
What do you guys think? I don't want to go back to stock for testing, because I value privacy a lot and XPrivacy is so much work to set up right, IMHO. I like the privacy managers included with Jaguar or CM12.1 a lot. They are so much easier to use. But if I have to, I will go back to stock. Any other ideas? Can anyone interpret the crash logs? Is there anything useful there? Should I test something else?
Please help. Thank you for reading this post.
Click to expand...
Click to collapse
Your attachments show only general info about OS, but nothing related to freezing/crashes. Based on the fact that you were problem free on Jaguar for about 3 weeks, you might have the following:
You installed an app or mode that's causing this; you might have set up something in Kernel Adiutor (such as cpu voltage or what have you) that's causing problems; you might have restricted something in wakeblocker or an app like Xprivacy or any other Xposed module. Just think of what you did at the end of the 3-week-period. In Kernel Adiutor, untick apply on boot and reboot, so that default values could be loaded. If that doesn't help, disable wakeblocker...
optimumpro said:
Your attachments show only general info about OS, but nothing related to freezing/crashes. Based on the fact that you were problem free on Jaguar for about 3 weeks, you might have the following:
You installed an app or mode that's causing this; you might have set up something in Kernel Adiutor (such as cpu voltage or what have you) that's causing problems; you might have restricted something in wakeblocker or an app like Xprivacy or any other Xposed module. Just think of what you did at the end of the 3-week-period. In Kernel Adiutor, untick apply on boot and reboot, so that default values could be loaded. If that doesn't help, disable wakeblocker...
Click to expand...
Click to collapse
I didn't change anything. Same thing when I went for a new nightly of cm12.1 I did nothing out of the ordinary. Since I did not have new problems since the above mentioned, I didn't delve any further. Today I had another, interesting issue. No one was able to call the phone and I wasn't able to call out, even though the network showed up as fine with full bars. This lasted for several hours. I went into flight mode and back out of flight mode and the issue was fixed. Several SMS arrived about calls missed. And again, I have no idea if this was caused by the hardware, an issue with the software or even the network.
And that is the frustrating thing: How can I find out who the culprit is? Are there good system crash diagnostic tools? Because so far I haven't seen anything.