I noticed the other day that even with all volume sliders at 100%, my tf701t is significantly quieter than it used to be. I've restored a nandroid, wiped data, even accidentally wiped EVERTHING including all of my files (turns out that the bootloader's wipe option kills your internal SD card contents, too... argh!). Nothing at all seems to increase the sound volume.
I have this feeling I might have caused this with a bit of (perhaps unwise) tinkering. I have ubuntu running in a chroot, and I was poking around and seeing if I could get sound working from the ubuntu side. I saw that with root (or with my user added to the right group) I can run alsamixer and get at all sorts of interesting little sliders. I experimented a fair bit, seeing if raising various sliders and unmuting various channels would let me get sound to play using alsa's aplay command. None of that panned out and I abandoned my effort.
Fast forward to yesterday, days and several reboots after I did the above tinkering, and I noticed that the speaker output was barely audible. I've poked around in alsamixer, and I can get it a BIT louder by unmuting a couple of the channels, but it's nowhere near actually useful volume. I'm not at all sure I caused this by tinkering with alsamixer, but I'm also not at all sure I didn't. I wouldn't have expected any changes I made to survive a reboot, but maybe the tegra chip does things weirdly.
Anyone have any ideas?
If anyone's feeling especially helpful, it would be incredibly useful to me if you could get me the normal alsa mixer channel values. Here's how you can do it with the least amount of fuss (root required of course):
grab "Complete Linux Installer" from the market -- I swear this isn't a plug
Follow the tutorial to grab the "core" version of ubuntu 13.10.
get it all set up and boot it up
when it asks, don't run vnc or sshd
open a second terminal, and run these commands:
su
umount /data/local/mnt/dev/pts
mount -t bind /dev /data/local/mnt/dev
mount -t devpts devpts /data/local/mnt/dev/pts
Now, back in the first terminal, do this:
apt-get install alsa-utils
amixer contents > useful_data_for_lexelby.txt
Grab that file and post it here
I realize that's a lot of effort to ask of you folks -- just hoping someone will have pity on a poor amateur android tinkerer Some linux knowledge would probably be useful, as I've glossed over a few of the setup details. Thanks in advance to any brave souls willing to give this a try.
lexelby said:
I noticed the other day that even with all volume sliders at 100%, my tf701t is significantly quieter than it used to be. I've restored a nandroid, wiped data, even accidentally wiped EVERTHING including all of my files (turns out that the bootloader's wipe option kills your internal SD card contents, too... argh!). Nothing at all seems to increase the sound volume.
I have this feeling I might have caused this with a bit of (perhaps unwise) tinkering. I have ubuntu running in a chroot, and I was poking around and seeing if I could get sound working from the ubuntu side. I saw that with root (or with my user added to the right group) I can run alsamixer and get at all sorts of interesting little sliders. I experimented a fair bit, seeing if raising various sliders and unmuting various channels would let me get sound to play using alsa's aplay command. None of that panned out and I abandoned my effort.
Fast forward to yesterday, days and several reboots after I did the above tinkering, and I noticed that the speaker output was barely audible. I've poked around in alsamixer, and I can get it a BIT louder by unmuting a couple of the channels, but it's nowhere near actually useful volume. I'm not at all sure I caused this by tinkering with alsamixer, but I'm also not at all sure I didn't. I wouldn't have expected any changes I made to survive a reboot, but maybe the tegra chip does things weirdly.
Anyone have any ideas?
If anyone's feeling especially helpful, it would be incredibly useful to me if you could get me the normal alsa mixer channel values. Here's how you can do it with the least amount of fuss (root required of course):
grab "Complete Linux Installer" from the market -- I swear this isn't a plug
Follow the tutorial to grab the "core" version of ubuntu 13.10.
get it all set up and boot it up
when it asks, don't run vnc or sshd
open a second terminal, and run these commands:
su
umount /data/local/mnt/dev/pts
mount -t bind /dev /data/local/mnt/dev
mount -t devpts devpts /data/local/mnt/dev/pts
Now, back in the first terminal, do this:
apt-get install alsa-utils
amixer contents > useful_data_for_lexelby.txt
Grab that file and post it here
I realize that's a lot of effort to ask of you folks -- just hoping someone will have pity on a poor amateur android tinkerer Some linux knowledge would probably be useful, as I've glossed over a few of the setup details. Thanks in advance to any brave souls willing to give this a try.
Click to expand...
Click to collapse
I dont know if this is helpful without mounting things. Ill do the mounts later. I used Linux deploy as well.
numid=1,iface=CARD,name='HDMI/DP,pcm=3 Jack'
; type=BOOLEAN,access=r-------,values=1
: values=off
numid=2,iface=MIXER,name='IEC958 Playback Con Mask'
; type=IEC958,access=r-------,values=1
: values=[AES0=0x0f AES1=0xff AES2=0x00 AES3=0x00]
numid=3,iface=MIXER,name='IEC958 Playback Pro Mask'
; type=IEC958,access=r-------,values=1
: values=[AES0=0x0f AES1=0x00 AES2=0x00 AES3=0x00]
numid=4,iface=MIXER,name='IEC958 Playback Default'
; type=IEC958,access=rw------,values=1
: values=[AES0=0x00 AES1=0x00 AES2=0x00 AES3=0x00]
numid=5,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw------,values=1
: values=on
numid=6,iface=MIXER,name='HDA Decode Capability'
; type=INTEGER,access=rw------,values=1,min=0,max=-1,step=0
: values=0
numid=7,iface=MIXER,name='HDA Maximum PCM Channels'
; type=INTEGER,access=rw------,values=1,min=0,max=-1,step=0
: values=0
numid=8,iface=PCM,name='ELD',device=3
; type=BYTES,access=r-------,values=0
---------- Post added at 08:32 AM ---------- Previous post was at 08:18 AM ----------
Doesnt linux deploy mount all these things anyway? Running the mixer from linux deploy doesnt let me changed volume levels as far as I know. It does show the sound devices. Might it be that some things are read only. Try installing it possibly with Archlinux which im using. Maybe itll fix it for you in some magical way
Oh! That's almost exactly what I need. They only thing is that I forgot to mention that I need the mixer values for card 1 -- it defaults to sound card 0, which is the hdmi output. It looks like your Linux installer did the bind mount of /dev just fine. Not sure why Compete Linux Installer doesn't, but it should. I ended up hacking the startup script to mount /dev properly.
Thanks so much for your help!
lexelby said:
Oh! That's almost exactly what I need. They only thing is that I forgot to mention that I need the mixer values for card 1 -- it defaults to sound card 0, which is the hdmi output. It looks like your Linux installer did the bind mount of /dev just fine. Not sure why Compete Linux Installer doesn't, but it should. I ended up hacking the startup script to mount /dev properly.
Thanks so much for your help!
Click to expand...
Click to collapse
Oh right. Lots more information here.
And with linuxdeploy you can VNC into as if it were some kind of RASPBERRY PI OR BEAGLEBOARD advertised to you for all of eternity!!
Thanks so much for providing that amixer output!
YayYouFixedIt said:
And with linuxdeploy you can VNC into as if it were some kind of RASPBERRY PI OR BEAGLEBOARD advertised to you for all of eternity!!
Click to expand...
Click to collapse
Yeah, the one I used does vnc, but performance is pretty pitiful. I use XSDL from the market, a direct x11 server. Supports more apps (chrome crashes on vnc for me) and it's much faster -- almost like a real Linux box.
lexelby said:
Thanks so much for providing that amixer output!
Yeah, the one I used does vnc, but performance is pretty pitiful. I use XSDL from the market, a direct x11 server. Supports more apps (chrome crashes on vnc for me) and it's much faster -- almost like a real Linux box.
Click to expand...
Click to collapse
Very cool, I see with XSDL you can stream a Linux app directly to the tablet Like intelliJ/android studio for example looks exactly the same. Only thing is I couldnt see the on screen keyboard it mentions in the settings.
EDIT: Oh it looks like you have to use the default keyboard.
How did you fix it?
So, did you ever solve the problem with the internal speaker volume? I'm having a similar issue after rooting and installing a custom ROM. I ended up going back to Jellybean to solve a battery drain issue I was having.
Actually, no, I never did find a fix. I tried various other ROMs, but none fixed it. I think my initial theories that I broke it by tinkering with alsamixer were unfounded, and this is just some weird hardware flaw. I bought a little battery-powered speaker which helps a bit.
I have same problem
Hi, I have same problem with quiet speaker. Today I did my first root of android device by these instructions. Root was successful and then during using my tablet I realized the speaker is very quiet. After root I did only one thing - removed file /system/vendor/lib/mediadrm/libwvdrmengine.so which was the part of solution of battery drain problem described here. Sound via external speakers connected by jack into tablet is ok.
I tried fastboot recovery, wipe data and cold start, but still same problem. Even loading removed file back wasn't helpful.
If you anybody has resolved same problem, thank you for advice, how to repair it. I hope this problem has a solution.
babusek said:
Hi, I have same problem with quiet speaker. Today I did my first root of android device by these instructions. Root was successful and then during using my tablet I realized the speaker is very quiet. After root I did only one thing - removed file /system/vendor/lib/mediadrm/libwvdrmengine.so which was the part of solution of battery drain problem described here. Sound via external speakers connected by jack into tablet is ok.
I tried fastboot recovery, wipe data and cold start, but still same problem. Even loading removed file back wasn't helpful.
If you anybody has resolved same problem, thank you for advice, how to repair it. I hope this problem has a solution.
Click to expand...
Click to collapse
You install the touch recovery?
Related
Hey, I stumbled upon this site after having owned my qtek for a week now. First WM based phone that I have had that ive added various software to and basically had a bit of fun with. But without going on too much here I will list what questions/problems I have and hope someone can help. I’ll lst them here instead of creating multiple threads to save on clutter
My list
My phone often freezes up or switches off, is there a fault with the OS/device? The freezing up was happening before I ever installed a thing so I cant put it down to it being my fault for once =] ive checked for updates or posts about it but haven’t been able to find much that has helped. It ran a bit slow the first day i got it after having two prgrams running. i often check to make sure if i have fully closed down apps after using them
Is there any way to stop the Echo the receiver hears when I make or receive calls? This also occurs when using skype.
I brought an i-mate Pocket PC Headset Adaptor (2.5mm to 3.5mm headphone jack) so I could use my phone as an mp3 player when im out and about. The only problem is that the headphones I used (sony in ear bud things) only played sound out of the left speaker. I haven’t used the hands free headphones that came with the phone but they have a left and right speaker, so I need to install a driver or something as so I can hear sound out of both headphone speakers? if not thats 13notes down the trálét
What are the key procedures you should follow to optimise your pocket pc? Including regedits =]
ive seen that you can adjust the CPU speed, is it wise and if so, whats the best processing speed? Or is the “turbo speed” function any good? Does it cause freezing up or shorter hardware life span?
Setting profiles, do I really need to install something in order to customise
and change profiles?
If I wanted to develop my own programs, what software would I need and where can I get it for cheap/free?
Sorry for the long list, ive tried hunting for the info as best I can but obviously not done too well
Cheers for any responses with assistance/answers :thumbsup:
rapturas said:
My phone often freezes up or switches off, is there a fault with the OS/device? The freezing up was happening before I ever installed a thing so I cant put it down to it being my fault for once =] ive checked for updates or posts about it but haven’t been able to find much that has helped. It ran a bit slow the first day i got it after having two prgrams running. i often check to make sure if i have fully closed down apps after using them
Click to expand...
Click to collapse
If you received the device and it was still running, chances are it's been operational a while and had numerous programs added & removed, will have fragmented memory etc. The best thing is to start with a cold hard reset (leave the main battery out for at least an hour to drain the backup battery) then start from scratch & set the device up. This cures about 75% if these kiind of ills. I'll assume you have it connected with activesync by now, so will have a backup of contacts & numbers etc.
Is there any way to stop the Echo the receiver hears when I make or receive calls? This also occurs when using skype.
Click to expand...
Click to collapse
I dont use mine for skype so couldnt comment. when doing a normal soft reset note down the numbers that come up on the starting screen: these are the update numbers of the various ROMS in the device - you may have an early 'buggy' rom and may wish to consider a flash upgrade - many of us have & it;s worth it for improved signal quality/reception & stability. you'll find all the answers you seek using the search tool
I brought an i-mate Pocket PC Headset Adaptor (2.5mm to 3.5mm headphone jack) so I could use my phone as an mp3 player when im out and about. The only problem is that the headphones I used (sony in ear bud things) only played sound out of the left speaker. I haven’t used the hands free headphones that came with the phone but they have a left and right speaker, so I need to install a driver or something as so I can hear sound out of both headphone speakers? if not thats 13notes down the trálét
Click to expand...
Click to collapse
The adaptor I brought had the same problem at first. You will find the socket is slightly recessed, so a normal fat adaptor cant push in far enough into the socket to engage the contacts properly, hence the music in one ear only. Try out the built-in ones, and you should be able to see how the plug pushes in further because of it's slim dimensions. Either cut your adaptor down if possible or find a slimmer adaptor!
what are the key procedures you should follow to optimise your pocket pc? Including regedits =]
Click to expand...
Click to collapse
My personal favourites are pocket mechanic and resco today/registry plugins, you will find countless opnions on this, and many posts! again, search and you will find all the answer you seek, and a lot of clues as to what you should look for: each user uses their PDA for different things.
ive seen that you can adjust the CPU speed, is it wise and if so, whats the best processing speed? Or is the “turbo speed” function any good? Does it cause freezing up or shorter hardware life span?
Click to expand...
Click to collapse
Turbo mode is slightly more responsive, and so should shorten battery life a small amount, but the screen chews up far more battery than running the CPU faster: try running a week on each setting and see if you notice a performace/quality difference. There are utilities to alter the CPU speed using registry tweaks: some of the settings will cause the PDA to lock requiring soft or sometimes hard resets. My personal take is to leave things be & run on turbo, ymmv.
Setting profiles, do I really need to install something in order to customise and change profiles?
Click to expand...
Click to collapse
profiles for what? ring settings? internet connections?
If I wanted to develop my own programs, what software would I need and where can I get it for cheap/free?
Click to expand...
Click to collapse
Your best bet here is to go and look at some of the other forums on this site! Development & Hacking is where you need to go lurk, and then post: that's exactly the place where people far better qualified than I can answer this one
Joe
Hey all,
Sorry if i sound dumb, but i can't quite figure out what these lag fixes do, or if i should try to put one on my device. I've tried to read the threads pertaining to the lag fixes but all the ext2 ext4 stuff confuses me haha. In my mind i picture it fixing the delay on the 4 buttons (menu, home, back, search).
If anyone could break it down for me i'd very much appreciate it
Thanks
One of things it does is makes those button 2-3x faster. Also i think it makes the general experience of the phone a lot more smoother from what i have noticed.
ViniD said:
One of things it does is makes those button 2-3x faster. Also i think it makes the general experience of the phone a lot more smoother from what i have noticed.
Click to expand...
Click to collapse
Ahh i guess i shoulda followed my gut, or just tired it haha. Thanks for the heads up, i think i'm gonna try it right now
Ok so i just ran the one click lag fix. I can't say i notice a difference in pressing the bottom buttons but to make myself feel better i downloaded that quadrant thing, ran it and it gave me a score of 2264. Now i have no idea what that proves but at least i don't feel bad now about applying the lag fix lol
Sometimes the phone seems to lag or hesitate at times if you press a button, open an application, etc. These are the "lags" the fixes are addressing. It's literally taking the phone longer than it could to read and write files on the device.
The lag fixes move your system files into a different file system (sort of like a virtual drive on PC's, all done in software.) Samsung uses a file system called rfs, which is running very slowly on these phones. Lag fixes use different file systems from Linux, such as ext2 or ext4, which perform better.
The risk in using a lag fix (albeit small) is that your data might become corrupted if you don't shut down your phone properly; for example, say if you pulled the battery while the phone is running.
I hope that helps you understand what they do better.
Sent from my SAMSUNG-SGH-I897 using XDA App
ag4vr said:
Sometimes the phone seems to lag or hesitate at times if you press a button, open an application, etc. These are the "lags" the fixes are addressing. It's literally taking the phone longer than it could to read and write files on the device.
The lag fixes move your system files into a different file system (sort of like a virtual drive on PC's, all done in software.) Samsung uses a file system called rfs, which is running very slowly on these phones. Lag fixes use different file systems from Linux, such as ext2 or ext4, which perform better.
The risk in using a lag fix (albeit small) is that your data might become corrupted if you don't shut down your phone properly; for example, say if you pulled the battery while the phone is running.
I hope that helps you understand what they do better.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
This was a perfect explanation. I saw someone who was wanting to make a new guide, i suggest you send that exact post to him. If i can understand it anyone can haha.
This does raise some questions now though,
1. I know it can now be corrupted but is this on the internal or external sd card? 2. Once corrupt what exactly is stored in this location (if i remember right i had to chose a size to apply this lag fix to)?
3. Is this a corruption like i can just reflash a rom and everything is back to stock, or is that piece completely broken?
Thanks again =)
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.
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
Hello,
I'm using my N7000 with CM 10.2-20131214 for about third month and it got pretty slow and laggy. This is becouse of leftovers from previous data.
Using AndroBench random write score is 0.28 MB/s 73.3 IOPS which is dramatically slow.
There is an app for cleaning this mess called LagFix but N7000 is not supported.
I was also trying to TRIM using Terminal Emulator with no resault.
Code:
[email protected]:/ $ su
[email protected]:/ # fstrim -v /system
fstrim -v /system
fstrim:FITRIM: Operation not supported on transport endpoint
Is there any kind of solution for this issue, or I just need to do formatting internal storage from time to time?
No, there is no way to enable trim on the device.
It could cause a superbrick if you did manage to activate it.
Azeazezar said:
No, there is no way to enable trim on the device.
It could cause a superbrick if you did manage to activate it.
Click to expand...
Click to collapse
Thanks for reply
Good that i didn't :<
Can formatting may be threat also?
Is it possible that this will be fixed in future?
Well, the fix is to disable what would cause a superbrick. (Which is why it failed in your case)
Completely fixing it, as far as i understand it, would requiring updating the EMMC firmware, which is risky, if not impossible.
You will just have to use the old garbage collection the chip has been using quite successfully. It seems to be doing fine.
No need for trim, or any special action on your part.
P.S.
Your random write speed is normal and identical to my own note.
Now, how often do you think random writing is bottle-necking your note?
It is likely something else that is the bottleneck.
My guess is that those guys at cyanogen are still using gpu clock speeds from the S2. I have not used that rom in a while, but i remember overclocking my lowest gpu step to 160 (from 100(CM), or 130(Stock) still nowhere near the top step that is 266) to give it a little boost.
I am not a developer, And i have not messed with that stuff for a while. So do your own research to what the problem is.
Azeazezar said:
My guess is that those guys at cyanogen are still using gpu clock speeds from the S2. I have not used that rom in a while, but i remember overclocking my lowest gpu step to 160 (from 100(CM), or 130(Stock) still nowhere near the top step that is 266) to give it a little boost.
I am not a developer, And i have not messed with that stuff for a while. So do your own research to what the problem is.
Click to expand...
Click to collapse
CyanogenMod uses 133MHz as the first GPU step for our note
yes, you can trim the n7000...
http://forum.xda-developers.com/gal...kernel-trim-speed-cyanogenmod-galaxy-t2875730