Database Develop

[Q] Erratic Touchscreen Issues

No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.

have you tried a screen protector? my screen wasnt the best for precise touches but since i put a screen protector on and clean the screen regularly it has since changed my problems to almost non existant.
Sent from my NookColor using Tapatalk

Others may be able to help you more than I can with exactly when the CM7 may be doing this, but returning to stock to find out is actually not hard at all.
In the development thread there is a post that has the 1.2 stock zips (one keeps CW in place, the other returns it completely to stock). Which ever one you pick it's still just as easy to return to stock as to reflash CM7 again. This is especially true if you used a SD card with CW to flash (which is what I do), since when you want to go back to CM7 you won't have to worry about flashing CW to emmc again.

angelic.pariah said:
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
Click to expand...
Click to collapse
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?

dalingrin said:
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
Click to expand...
Click to collapse
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it. At one point I almost purchased an app from the market before I had to power down.
I will return it to 1.2 stock and report back. I was mainly wanting to know if these was a commonly reported issue or not. I guess it's not. Thanks for the help everyone!

angelic.pariah said:
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it.
Click to expand...
Click to collapse
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.

bucketheadmn said:
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
Click to expand...
Click to collapse
So now I have installed nook stock 1.2 and NO PROBLEMS. I have run everything trying to get something to happen, and nothing.
Is it possible that I installed something the wrong way with cm7? Could I have used the wrong CWM version (3.0.0.6)?
Should I try cm7 7.0.2 or something else again?
I would try and return it, but I can't recreate the problem... if I could, I would be in their face right now.
Thanks for the help so far.

I think I solved it!
The newest nooks (in the last week or so) have 1.1.0 factory stock. Apparently there is a glitch that has been reported a lot recently about handling the touchscreen AND the SD card. These were fixed in the 1.2 upgrade. SO...
1. I flashed factory stock back on (in this case I went back to 1.0.1)
2. Then turned it off and "restored factory" settings using "Power+N" to turn it on. Repeated that a second time to get B&N's factory reset screen to come up.
3. Pressed N twice to accept restore prompts.
4. Upgraded to 1.2 (no glitches already by this point with touch or SD)
5. Booted CWM 3.0.0.6+
6. Formatted /system & /data
7. Flashed phiremod 6.1
8. OC'd to 1.1Ghz
...and DONE. No problems so far. I still see the "Read Forever" opening screen, but it still works wonders. WAY better than before.
I am still having issues with Wifi, but I can deal with that.
Now to attempt dalingrin's OC to 1.3!
Thanks guys... hope this helps others.

I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.

I had weird touchscreen issues when using the interactive cpu governor. I later found only performance is supported. Using performance setting, everything works much better.

queseyo said:
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
Click to expand...
Click to collapse
I had the same issue. I exchanged it the other night and now my new one does not have the problem. It probably a hardware issue...i hope you are still under warranty!

Droid4 Stock ICS Bugs

All,
We don't have an ICS Bugs thread going on. I wanted to check with some of the people here on XDA to see if they are experiencing what I am. Currently on .213, but most of these bugs I've seen since the begining. Oh, I'm also in Canada running on 3G HSPA+. I'm stock, but rooted with safestrap installed.
1) When placing a phone call, the phone hangs up immediately (you here the disconnected beep), then retries the phone call a few seconds later (it always succeeds). I have tried this on a freshly wiped phone and found the same experience. I have also tried disabling the Assisted Dialing, but have found ikt's the same thing
2) When using Google Chrome, if there is a input box, most of the time my keyboard won't appear (I'm using Swype as my default keyboard)
3) Phone runs hot sometimes, and when it's running hot it slows down to a halt. Usually happens after a day or two without a restart
4) My photo doesn't appear in the text messaging app (worked in AOKP/CM9 on my D3, as well as it works on my gf's Nexus S)

The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:

podspi said:
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
Click to expand...
Click to collapse
Is your chrome working properly? Specifically the bug I mentioned in the OP...?

I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?

podspi said:
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
Click to expand...
Click to collapse
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS

I'm in the US also running .213
I haven't noticed any bugs, its working fine for me. I do not use chrome beta so I can't comment on that. The stock is not too bad, I don't use it much anyways.
Sent from my DROID4 using xda app-developers app

danifunker said:
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Text entry works fine in both the stock browser and Opera. BTW, Opera also has hardware acceleration, which is why it never worked in any of the Frankbuilds of ICS based off the GB kernel ... So you can have your teh snappy and type with it too :laugh:

I'm on the 212 build and i can't screencap using power + volume down.
Is this fixed in 213 or am i just doing it wrong?
Also on 212 i can't control the default google music app or winamp from my bluetooth headset when the screen is off. I could do this before with the same version of the winamp app when i was back on gingerbread. I tried upgrading winamp, but that did nothing. Is there any change in 213?
Thanks ahead of time
Edit: just tried it and the volume down + power combo worked. Lol

One question, possible thought to ponder.
Are the bugs being described here really bugs of Android 4 or are they bugs in the individual app itself not being fully compatible with Android 4 yet?
Do similar bugs happen on a non-motorola device with android 4?
I'm considering flashing one of the leaks, so I'm trying to understand how you are sure these are ics bugs before I make the leap and run into issues.
Thanks.
Apologies if this constitutes hijacking the thread, if it does let me know and I"ll edit it to delete the question.

I was able to figure out bug #4, I had to login with my Google+ account again, since the update yesterday everything seems to be working fine.
Bugs 1 through 3 still exist, although I've switched off Global mode for now and put it to GSM only, it seems like the phone runs a lot cooler in this mode.
Even after updating Chrome to the final version, I'm still experiencing that text input bug. Maybe it's a Motorola issue... Can't wait for the next version of the leak!

I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.

podspi said:
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
Click to expand...
Click to collapse
for this reason I think there will be other leaks, ICS is supposed to handle killing processes much better than GB, however the settings seem to not be aggressive enough in 213.

Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...

podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.

podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
I don't know, just had a random reboot after watching a youtube video in firefox, most likely memory related, not sure who's fault though, Motorola or Firefox. gotta root and use system tuner to change memory mgmt states.

danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
That is a great idea. Though there hasn't been another leak since 213, so

Notification Bar Sticking/Wont Pull Down
I am on 212 currently, and I have noticed in 208 and 212 something that has happened only twice so far. Today, I just tried to check my notifications, and the bar will not pull down.
After a reboot it works fine, and it has only happened 2 times in the past couple weeks since the leaks first appeared.
Obviously it is a minor glitch, but just thought I'd throw it out there in case anyone else has seen it and overlooked it. :cyclops:

danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
I have heard of a few others using this method successfully. If you are not using safestrap or just don't want to go this route take a look at the post link in my signature. It's a modified version of the original Droid 4 Utility and includes a script to jump from one ICS leak to another without losing data. It also flashes the GB files and the Kernel (boot.img) in one script, thus making it easier to go from one leak to another.
Regarding bugs, my wife got a razr yesterday. It wouldn't pull down the ICS update, so I just sideloaded it. We both run some of the same apps. So this gave me a chance to do side by side comparisons.The issue with some of the icons being small in the left top of the status seems to be a app issue. The chrome issue isn't present on the razr, of course there isn't a physical keyboard. Otherwise my 213 ICS seems to run great.

I found a new bug, it looks like GSM call forwarding doesn't work properly... at least it doesn't with my SIM card, I'm on Rogers in Canada.
Does Verizon support call forwarding? Does it work on there?

I have noticed in Chrome that pressing shift and then one of the symbol keys (like @) will only work if you hold the shift key.
More importantly I don't get notifications of app updates from google play. Check to see if you have any apps that need updating. Superuser had a update on July 1, dropbox yesterday and voodoo rootkeeper on June 28, I think. Anyone else?

[Q] Touchscreen sensitivity issues in CM9/CM10 (but not webOS)... any advice?

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.

[Q] Touchpad Audio Stops work, Lag in all apps CM9, and CM10

As the subject line says, I have tried flashing different builds of CM9, and CM10, AOKP, and the only build that works are the nightlies for CM10.1. What happens is, at some point randomly during use, or more commonly when the screen is off, sound will stop functioning and NO audio will come out of the touchpad. On top of this there is also massive slowdown in every single app. I have tried increasing minimum clock speed, flashing new Kernels, Removing android completely and reinstalling from WebOs, Changing my recovery app, upgrading Moboot, and doing a complete format of system, data, etc before flashing. NOTHING works. Any suggestions?

I'm having the exact same problem. I've tried both CM9 and CM10 along with webos 3.0.0 and 3.0.5. I've also done a full wipe and run webos doctor to start from a completely blank slate. My tablet did suffer from the scratchy sound problem under webos 3.0.5. I haven't tried it yet under 3.0.0.
If I reboot, it works for a little while. I'll get some HW/SW info and post it shortly.
[edit]
The lag only happens when the audio stops working. When audio works, there is no lag and it runs like a dream.
IN WEBOS
Version HP webOS 3.0.0
Product number FB359UA#ABA
Model HSTNH-129C
Android version 4.1.2
Kernel verion 2.6.35 palm tenderloin [email protected] #1 thu apr 18
CPU ARMv7 Processor rev 2 (v7)
Cyanogenmod 10-20130418-EXPERIMENTAL-tenderloin-FOR_LIMITED_TESTING_ONLY_CAM
Build date Thu Apr 1800 04 59 CDT 2013
Build number cm_tenderloin-userdebug-4.1.2 jzo54k eng.jc.20130418.000410 test-keys
MOBOOT 0.3.5
I used CMinstaller3 todo all my CM installs. I couldn't find CMinstaller2. I don't know if that has any bearing on this issue.
I hope this helps. I love this device but I've been fighting with this for almost a month and i'm running out of ideas.
Thanks!

I've since found CMinstaller2 and loaded CM9. Same issue.

Another update: Some may be aware of the scratchy audio issue on the touchpad in webos. I experienced this yesterday under CM9. Since very few people have this problem, I wonder if it is a hardware related issue and only a few touchpads suffer from this.

augoosto said:
As the subject line says, I have tried flashing different builds of CM9, and CM10, AOKP, and the only build that works are the nightlies for CM10.1. What happens is, at some point randomly during use, or more commonly when the screen is off, sound will stop functioning and NO audio will come out of the touchpad. On top of this there is also massive slowdown in every single app. I have tried increasing minimum clock speed, flashing new Kernels, Removing android completely and reinstalling from WebOs, Changing my recovery app, upgrading Moboot, and doing a complete format of system, data, etc before flashing. NOTHING works. Any suggestions?
Click to expand...
Click to collapse
Try the latest CM9 nightly as mentioned here:
http://forum.xda-developers.com/showpost.php?p=43602041&postcount=2740

Issue
As of today I have discovered that Turning on and connecting to Wi-Fi is the source of the problem. Flashed that new build JC and it worked great until I turned Wi-Fi on, at which point the same issues occurred. Why this happens on all builds except CM 10.1 I am still not sure.

augoosto said:
As of today I have discovered that Turning on and connecting to Wi-Fi is the source of the problem. Flashed that new build JC and it worked great until I turned Wi-Fi on, at which point the same issues occurred. Why this happens on all builds except CM 10.1 I am still not sure.
Click to expand...
Click to collapse
Well, that's certainly strange.
Could you try with latest CM9 again and grab output of 'dmesg' after you turn on wifi and get the failed audio?

jcsullins said:
Well, that's certainly strange.
Could you try with latest CM9 again and grab output of 'dmesg' after you turn on wifi and get the failed audio?
Click to expand...
Click to collapse
Certainly can

Issue
dmesg output attached.

I also have flashed 9-20130714-Nightly and I've noticed an improvement in the audio stoppage. I tried to repeat the problem that augoosto has seen by turning the wifi on and off. I was not able to repeat it. I will keep trying to stimulate the failure. I seem to get a lag only when the audio has stopped, and only when the app/program is calling to make a sound. if I mute the app and not the tablet sound (candy crush is a good one to try this), I get normal non-laggy performance.
Overall things are much better with this build. I probably only have to reboot a few times a day. Previously, I had to reboot every time I wanted to do something that involved sound.
Another thought. There may be some correlation to using the power switch. I just now let it fall asleep on its own, and use the home button to wake it up. I'll do more to see if I can find more correlation.
Thanks!

augoosto,
I don't know much about how sound in Android works, but I took a look at your dmesg output anyway. This line stood out to me:
Code:
[ 162.777248] asoc: can't open platform msm-audio
I would assume that this line occurs sometime after CM boots, because I doubt that your TP is taking almost 3 minutes to boot.
Next time that the audio drops out, try running cat /proc/asound/cards and see if anything is listed. My TP lists a single card called msm-audio in CM 10.1.
Sent from my SAMSUNG-SGH-I747

I'm a newbie to Android on my Touchpad and I am also experiencing this intermittent dropout of the audio. I have not been able to narrow down the loss of audio to running any particular application, or sequence of events. In short, audio will be working fine, then, the next thing I know, silence.
For better or worse, I'm running a jcsullins preview build: 10-20130418-EXPERIMENTAL-tenderloin-FOR_LIMITED_TESTING_ONLY_CAM . Everything else has been working fine except for this annoying audio problem. BTW, I first noticed the problem shortly after my initial install and tried to view a YouTube video. The video displayed one frame at a time, obviously very sluggish, and no audio. After rebooting, the same YouTube video played fine, and other sounds were working, too. I didn't think anything of it until I noticed the audio disappearing at random times.
If it helps, I've attached my dmesg and logcat listings captured today as soon as I realized that my sound disappeared. The "Out of memory" errors listed in logcat are certainly suspicious, but could just be a symptom rather than the problem.
-Don

sound card still listed
My sound card is still listed after using that cat line, but I am still no closer to fixing this problem, which I am now experiencing in cm 10.1 as well as of the last 10 builds.

Dmesg
jcsullins said:
Well, that's certainly strange.
Could you try with latest CM9 again and grab output of 'dmesg' after you turn on wifi and get the failed audio?
Click to expand...
Click to collapse
See anything out of the ordinary in my dmesg output JC?

Partial fix
I have found what seems to be the cause of the issue. It appears that the issue is caused by bad blocks in the NAND memory of the device. Last night I did a full format, and before re flashing, I partitioned the SD card in CWM, causing the installation to be written to a different section of the devices flash memory. The audio issues almost completely went away in CM9, now I just need to find a way to identify all of the bad blocks and prevent them from being written to. Hope this is helpful to other users suffering this issue.

augoosto said:
I have found what seems to be the cause of the issue. It appears that the issue is caused by bad blocks in the NAND memory of the device. Last night I did a full format, and before re flashing, I partitioned the SD card in CWM, causing the installation to be written to a different section of the devices flash memory. The audio issues almost completely went away in CM9, now I just need to find a way to identify all of the bad blocks and prevent them from being written to. Hope this is helpful to other users suffering this issue.
Click to expand...
Click to collapse
This is great news as mine has become almost unusable. I'm not 100% sure how to partition the SD card in cwm but I'll take a stab at it and let you know if it fixes mine as well.

augoosto said:
My sound card is still listed after using that cat line, but I am still no closer to fixing this problem, which I am now experiencing in cm 10.1 as well as of the last 10 builds.
Click to expand...
Click to collapse
Try doctor yout TP before installing

augoosto said:
I have found what seems to be the cause of the issue. It appears that the issue is caused by bad blocks in the NAND memory of the device. Last night I did a full format, and before re flashing, I partitioned the SD card in CWM, causing the installation to be written to a different section of the devices flash memory. The audio issues almost completely went away in CM9, now I just need to find a way to identify all of the bad blocks and prevent them from being written to. Hope this is helpful to other users suffering this issue.
Click to expand...
Click to collapse
can you please give us the steps for doing this,, by doing this will we loose webos as well ? i have the touch pad with cm9 and have tried different builds but sound has not worked consistenly. in web os it works well.
with these particular touchpads we have, is it better consider some other OS !!

Any progress with this audio issue? It's the only problem I ever have with my touchpad. Incidentally, it never shows up on my daughter's, which has cm7 installed.

Same thing here. Sounds work fine at the beginning, then lose it (after the screen is off for a couple of seconds).
It was working fine at some point using CM9, but since I tried CM10.2, CM11 and now evervolv 4.4.2... I still have that painful issue. Everything else work fine, except audio. It also prevent youtube from playing videos. Videos work fine while the sound is working, but when we lose the sound, youtube videos doesn't play anymore.
I've been crawling the web since last December on this subject, found a couple of thread like this one with the issue but nobody has found how to fix it (or I didn't find it yet!)
If anyone has an idea... please let us know, thanks!
ps.
Here's a dmesg sample output in attachment (and on pastebin.com/FzsXs7fS )
Suspicious lines:
<3>[ 216.450042] APR: Unable to open handle
<3>[ 216.450073] q6asm_audio_client_alloc Registration with APR failed
<3>[ 216.450103] q6asm_audio_client_free: APR Common Port Already Closed
<3>[ 216.450164] asoc: can't open platform msm-dsp-audio.0

[Q] Looking for a good stable ROM for S3 mini

I have been ROM-hopping for 3-4 months and I have tried many ROMs for my i8190.
I found some I really enjoyed, some did not work well for me.
Without meaning to "compare" the ROMs or find "the best ROM ever" I am just looking for some suggestions on ROMs that I can try.
My requirements are very simple:
-OTG support
-No clock freezing
-No battery drain
What ROMs would you suggest?
Please note, I have no intention of comparing the ROMs with one another, I am just looking for suggesstions in case there is something good that I have not tested yet.
Thanks!

Novafusion CM10.2
sent from Hell with my GT I9100

tobi-19777 said:
Novafusion CM10.2
Click to expand...
Click to collapse
Thank you for your time. This was the ROM I installed last and seems to be a good option.
I have been using it for almost a week, I really like the stability, looks like a solid ROM.
I only have one issue with it (all cyanogenmod ROMs basically).
Even though I have turned the backlight of the hardware buttons off, they keep lighting at random times, I have not found what is causing that or how to fix it, can you suggest something or do I just get used to it?

anpel said:
Thank you for your time. This was the ROM I installed last and seems to be a good option.
I have been using it for almost a week, I really like the stability, looks like a solid ROM.
I only have one issue with it (all cyanogenmod ROMs basically).
Even though I have turned the backlight of the hardware buttons off, they keep lighting at random times, I have not found what is causing that or how to fix it, can you suggest something or do I just get used to it?
Click to expand...
Click to collapse
Download this app, then open it, uncheck "activate bln" then go to system settings-buttons-backlight & uncheck illuminate buttons

mauam said:
Download this app, then open it, uncheck "activate bln" then go to system settings-buttons-backlight & uncheck illuminate buttons
Click to expand...
Click to collapse
I managed to break my phone's screen so I haven't been using it for the past couple of months but I'm back here to say this solution worked 100% for me, just in case anyone is reading. Thank you!
P.S. Sorry I had to remove the url to the app, but I'm a new user and I am not allowed to post external links, obviously even when quoting more experienced users.