Related
Normally I don't have a problem locating this kind of info, but for TP CM9 it eludes me. I found the link with the tech speak generated list. But I need the info to be a bit more plain english. And couldn't find a known issues list. I would like to check this info to see if I would like to try it out on my TP.
Thanks much.
StoneRyno said:
Normally I don't have a problem locating this kind of info, but for TP CM9 it eludes me. I found the link with the tech speak generated list. But I need the info to be a bit more plain english. And couldn't find a known issues list. I would like to check this info to see if I would like to try it out on my TP.
Thanks much.
Click to expand...
Click to collapse
Known issues are basically the camera and mic don't work, some folks have wifi issues and some don't... and some have issues with the audio acting up when waking from sleep... I myself am happy to say I don't have wifi or audio issues... but camera and mic are driver issues that may never get to work. All in all very stable though
Sent from my cm_tenderloin using Tapatalk 2
If camera and mic are the only problems then I see no reason not to give it a shot. I don't know if I would ever use them.I was concerned that it was missing core functionality making it something one wouldn't use as a daily OS and only switch over to it for test scenarios and then switch back. I have cm9 on my Samsung epic (the one with hw kb). Would the current latest nightly be the one to go with?
Just curious, why are the camera and mic drivers so difficult? I would have thought having them running on WebOS was at least some of the work. I guess porting said work to Android is a completely different ballgame.
I wonder if the wifi/audio issues are still being worked on tho? Or are those of us with those stuck with em forever?
The big thing for me was hardware video decoding. Alpha 1 fixed that for YouTube, and alpha 2 finished the fix for Netflix and others.
If you haven't already, check out the thread at rootzwiki.
I was using webOS by choice until CM9 came out. I switched to CM9, and have been using it as my daily driver since the very first Alpha. I never video chat, but if I wanted to I know I can just boot webOS.
Don't let people here tell you CM9 (or the Kangs thereof) are unstable. Some people continue to spew that we don't have a stable version of android purely because its called an alpha. I don't think it will graduate past alpha without camera/mic support, and that may never happen. Right now, without trying, I am sitting at 587 hours of up time on my TouchPad. I can't think of a better word to use than "stable."
Sent from my Galaxy S II (i777)
Known Issues that I can think of. I know some were mentioned above, but all in one place is good.
Broken, NO FIX:
1) No Microphone
2) No Camera
Partial Workarounds:
1) Audio gets noisy with screen off. Kinda workaround: Turn volume down, only happens at higher volume levels. Or set screen timeout longer/always on while playing audio. No complete fix.
2) Wi-Fi dies or doesn't reconnect. Some people never have a problem, others do. Workarounds: First, set WiFi to always on so it doesn't turn off with the screen. Second, try changing the channel on your router, or if you have 2.4ghz/5ghz switchable, try using the other. If Wi-Fi still dies, toggle it off and back on.
3) Some people report that if the TouchPad fully discharges to 0% they have trouble getting Android to charge properly. Others report that if you reboot the device with it plugged in, sometimes it won't charge. I've experienced neither problem, but the best advice is, charge before the device shuts off fully, and unplug the charger/usb while booting.
Broken, but Completely Fixable:
1) Random crashes. Install CPU Master and raise minimum CPU speed to 384 or 416 depending on which works for you, and crashes go away. Also, don't overclock too much.
Setup Issues:
1) DPI is at 160dpi stock. This works for most things, except a few tablet apps and games will not work properly. Setting DPI to 120dpi fixes everything, but the display quality is not ideal. 132dpi is ideal, but breaks the market after a day or two. Most people use 160dpi or 120dpi.
2) The default launcher, Trebuchet, is NOT compatible with the 4:3 aspect ratio of the TouchPad's screen if you use any DPI other than 160. Why something so easily fixable has not been fixed escapes me, but you will quickly find you need a new launcher. Go Launcher HD is one of a few that are very friendly to the TouchPad.
App Issues (not really issues but you probably want to know)
1) A few apps really, really, really are picky about the screen size and just won't scale right. (see Trebuchet notes above). One example is Politico HD - it forces 16:9 aspect ratio and thus gets cut off. Some apps simply refuse to run. Contacting the developers rarely works. This is probably less than 1% of the apps on the market, however.
2) Some developers simply are too strict on app compatibility on the market, and whitelist only select devices. Getting compatibility from these guys is a longshot. Best option is to install on another device, grab the APK or use Titanium Backup to move the app to the TouchPad.
3) Some games (notably Gameloft is the worst) enforce device compatibility checks within the program itself and it will refuse to run unless you masquerade as an approved device by hacking your build.prop... which is not normally recommended.
Did I miss anything anyone?
Hi community! Thanks to all the developers who make this project fly!!!
I fear I have a resistant Touchpad that does not want to output any audio in Android CM9 or CM10.
It has sound in WebOs so I don't think it is a hardware problem.
I've tried CM9 (123012) and heard some soundtap noise after a reflashed gapps, but then the sound went away, I think
when the wifi started (?).
CM9 was extremely slow and the system would be very laggy and freeze when I tried to change the volume by using
the volume buttons. Many times I'd have to do a power+home button shutdown.
CM10 (121612) on the other hand was very responsive, quick and smooth and there was no lag or freeze on pressing the
volume button- but still no audio.
I used ACMEuninstaller to remove CM9 and used:
ACMEInstaller3, CWM6, moot 0.35 for both installs, flashed cache and dalvik, and fixed permissions.
Is there anything else I can try?
Thanks!
Briefly hold the power button to bring up the menu and make sure it isn't set to mute should be the bottom Line with a line under the speaker on the right .
I brought up the screen, and it shows the speaker icon on the right side with the line under it.
It looks like volume is on and not mute, but still no sound.
Thanks for the suggestion.
Thinking it was something to do with WebOS 3.05, I used the thread in this forum to bring back the Touchpad to WebOS 3.00, and
then 3.04 and still the same issue appears in Android.
I'm now thinking that this 32GB Touchpad may not have the same hardware for the audio codecs to work in android?
(Actually, I'm clueless and just guessing, and, hope I'm wrong.) :fingers-crossed:
Well it was worth a try, it shouldn't be anything to do with webos (I'm on 3.05) . Do the headphones work as it has been suggested that the socket my be causing problems .
Otherwise I'm also clueless .
Good to know that it isn't WebOS 3.05 related.
I tried the headphones and no sound either. So I rebooted with the headphones plugged in and no sound.
One other thing I can't figure out is why would CM10 be more stable than CM9 on this device, when the consensus seems to be
that CM9 is much more stable?
No idea , I'm using Oat's at the moment but also have a backup of jcsullins so that I can test out things on both and have stopped using CM9 completely .
I take that you get no sounds when typing and that the volume cursor moves when you use the rocker switch .
Right. No sound when typing except the vibration feedback, and the volume cursor moves with the volume rocker.
This is jcsullins experimental build (121612), and other than the sound issue, it's sweet!
*edit*
I downloaded an app called AndroidSystem and here is part of the log when I try to play an mp3:
W/AudioTrack(349)
obtainBuffer timed out (is the CPU pegged?) 0x34bbe0 name=0x8user=000012c0, server=00000000
W/audio_hw_primary(160)
pcm_open(out) failed: cannot open device '/dev/snd/pcmC0D0p': Out of memory
W/audio_hw_primary(160)
pcm_write: cannot open device '/dev/snd/pcmC0D0p': Out of memory
The other thing I notice is under Build Info it states CPU ABI=armeabi-v7a,
but in WebOs I recall the CPU as ARMv7 Processor rev 2 (v7l).
north777 said:
Right. No sound when typing except the vibration feedback, and the volume cursor moves with the volume rocker.
This is jcsullins experimental build (121612), and other than the sound issue, it's sweet!
*edit*
I downloaded an app called AndroidSystem and here is part of the log when I try to play an mp3:
W/AudioTrack(349)
obtainBuffer timed out (is the CPU pegged?) 0x34bbe0 name=0x8user=000012c0, server=00000000
W/audio_hw_primary(160)
pcm_open(out) failed: cannot open device '/dev/snd/pcmC0D0p': Out of memory
W/audio_hw_primary(160)
pcm_write: cannot open device '/dev/snd/pcmC0D0p': Out of memory
The other thing I notice is under Build Info it states CPU ABI=armeabi-v7a,
but in WebOs I recall the CPU as ARMv7 Processor rev 2 (v7l).
Click to expand...
Click to collapse
Try going to settings > sound > volumes, and see if the settings are correct.
If I think of something else, I'll post it.
I have the exact same problem. Tried all the resolutions mentioned above, no result. Wiped out android and used WebOS doctor for full recovery, then installed the latest nightly (24 Nov 2013) still no sound. Somewhere it was mentioned that it is due to a firmware (A6) problem but I don't know how to downgrade or upgrade the firmware.
Any help is appreciated.
Hp Touchpad on CM9 and CM10
I have also tried for nth times but my touchpad 16GB has no audio output (including 3.5mm jack) on CM9 or CM10......... somebody help
I have the same problem, but can install older CM9 builds and have sound. 6/12/2012 nightly is one that has sound for me.
My problem ended up being the head phone jack. I rapidly inserted/removed the headphones several time and my speakers came back to life.
Still very odd that I had audio in WebOS and older cm9 builds the whole time, but I'll refuse the question that logic and am thankful that I was able to get it working.
north777 said:
Right. No sound when typing except the vibration feedback, and the volume cursor moves with the volume rocker.
This is jcsullins experimental build (121612), and other than the sound issue, it's sweet!
*edit*
I downloaded an app called AndroidSystem and here is part of the log when I try to play an mp3:
W/AudioTrack(349)
obtainBuffer timed out (is the CPU pegged?) 0x34bbe0 name=0x8user=000012c0, server=00000000
W/audio_hw_primary(160)
pcm_open(out) failed: cannot open device '/dev/snd/pcmC0D0p': Out of memory
W/audio_hw_primary(160)
pcm_write: cannot open device '/dev/snd/pcmC0D0p': Out of memory
The other thing I notice is under Build Info it states CPU ABI=armeabi-v7a,
but in WebOs I recall the CPU as ARMv7 Processor rev 2 (v7l).
Click to expand...
Click to collapse
I have the same problem and the same error messages! It happens on CM9 official nightlies as well as on CM10 and 10.1 unofficials that I have tried from this forum. It has not always been the case, seems like it just started at some point in the past, not sure exactly when or how... I wiped Android using ACMEUninstaller, reinstalled everything freshly and it still happens. When I reboot Android, I have sound for a few seconds or up to a few minutes but then it just stops, usually giving me some lag in the app that was using the sound (e.g. spotify or youtube). :crying:
In webOS, sound works perfectly.
CJMax said:
I have the same problem and the same error messages! It happens on CM9 official nightlies as well as on CM10 and 10.1 unofficials that I have tried from this forum. It has not always been the case, seems like it just started at some point in the past, not sure exactly when or how... I wiped Android using ACMEUninstaller, reinstalled everything freshly and it still happens. When I reboot Android, I have sound for a few seconds or up to a few minutes but then it just stops, usually giving me some lag in the app that was using the sound (e.g. spotify or youtube). :crying:
In webOS, sound works perfectly.
Click to expand...
Click to collapse
Have you guys considered submitting alogcat to the developers? It might be more productive than just stating that you have a problem. Submitting a logcat might help to get the problem fixed. I remember hearing issues with 64GB Touchpads not playing sound with CM9 Roms. Flashing the audio libs helped a few of those users.
I created a log on pastebin: MyfU2DDU (not allowed to post full urls yet). Who should I send it to? At the beginning of the log, sound was still working, then (I think line ~1280) sound stopped. Afterwards, I'm getting out of memory errors. Running CM10, same problem in CM9 and CM10.1.
Had the same prob and now back on cm-9-20130512 and disabled system sounds. It works now.
Hello everybody,
I have been waiting a bit until posting this issue to see if future nightly builds of Cyanogenmod solved the problem but to no avail, I already posted on their forums but so far no one has been able to figure out the problem... not that they tried.
I'm using an international Galaxy note (n7000) and these issues have been popping up since last month.
The main problem comes up when using the android keyboard and listening to music at the same time, the phone just seem to struggle a lot, music begins to stutter and usually the phone just becomes unresponsive and I have to force reboot the whole thing. A pain in the neck. Lately the phone just hangs whenever it feels like it and I have to reboot it, it usually happens twice a day.
Sometimes you're able to come back to normal after a few minutes but rarely.
The problem was even worse while using SwiftKey, now I'm back to just using the normal android keyboard but still the issue pops up almost every day. I already did a wipe data/factory reset, no avail.
Any thoughts on this?
Thank you in advance.
Post a log. Which ROM where you on before flashing CM.
sounds like a memory leak, try newer versions or trace down the issue. Check which apps consume most and cpu when it occurs.
Check as previous poster said logfiles
Sent from my GT-N7000 using Tapatalk 2
CM 10.1.3-N7000 bluetooth issues
Hello,
I'm using CM 10.1.3-N7000 and I really love it, but I'm forced to use another ROM, just because of the carkit compatibility via bluetooth. The sound is extremely bad.
Does anyone know if it's fixed in later versions or earlier versions?
Are there other ROM's, ot based on CM without the bluetooth problem?
I'm really searching since two days now to find a bluetoothfix, but can't find it.
Pairing and so on is no problem at all, it's just the soundquality that is terrible. (it was not the case with my stockROM)
thank you for giving me some advice!
I switched to Omnirom and I think the problem has been solved now.
If I see that the same problem is back as it was with CM, I will come back to that.
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
Hi,
I'm new on the forum, but I search for couple of weeks to resolve this problem, and sadly it occurs over and over again.
It occurs on Cyanogenmod 11, 12, now I have LiquidSmooth 4.4.4 and still occurs.
It is good for less than hour (when running) then volume just go down, tracks gets changed etc.
I have also CWM 6.0.4.7.
I use PowerAmp as main music player, but it occurs on any. I have original Samsung headset. But it also occurs on Roccat Skyva heaphones.
Is this software, or hardware thing? This really is annoying, I must know, because if this isn't fixable I must change phone asap. I need to have good working music player. I run alot, and need for it music.
Other info, I use also endomondo in the same time. But much earlier this problem wasn't present.
I don't know what I can do more to fix it. Any type of "super" reset, extra wipe, I don't know, go back to stock rom?
Please help.
Regards,
Kamil.
Going back to stock also doesn't fix anything, on stock it was even worse.
Can please anyone help?