Database Develop

Call volume very low - fixes?

Current info:
N1 from Jan 2010.
2.3.4
kernel 2.6.37.6-cyanogenmod-01505-g81b03a8 [email protected]#1
CyanogenMod-7.1.0-RC1-N1
I'm not sure if I've uninstalled something but the in call volume has got so low I can barely make out people in conversations. The volume up/down is maxed but its still not loud enough.
Do you experienced people think this is caused by a physical fault, me removing/stopping some previous volume boosting service integrated to the ROM, or is there any form of fix? I've tried the basic applications on the market but they crash as soon as a call starts.
Thanks!

dogiedogie said:
Current info:
N1 from Jan 2010.
2.3.4
kernel 2.6.37.6-cyanogenmod-01505-g81b03a8 [email protected]#1
CyanogenMod-7.1.0-RC1-N1
I'm not sure if I've uninstalled something but the in call volume has got so low I can barely make out people in conversations. The volume up/down is maxed but its still not loud enough.
Do you experienced people think this is caused by a physical fault, me removing/stopping some previous volume boosting service integrated to the ROM, or is there any form of fix? I've tried the basic applications on the market but they crash as soon as a call starts.
Thanks!
Click to expand...
Click to collapse
Try to flash a standalone kernel. Look for it in the development thread.

Thanks.
I flashed to 7.2.0 which gave me a fresh kernel. Call volume seems a bit louder but not much and could still do with more :/

I had identical issue with my N1 running CM7.2 RC2, in-call volume just way too low. Resolved by flashing the latest Tiamat N1 kernel. The one I tried was Tiamat_N1-v4.1.0 and you can download from tiamat-dev.com
Do a nandroid backup first so you can backout if something isn't right.

try to flash this kernel http://forum.xda-developers.com/showthread.php?t=653598
i flashed it with cm 7.2 and works great

Akram-aat said:
try to flash this kernel http://forum.xda-developers.com/showthread.php?t=653598
i flashed it with cm 7.2 and works great
Click to expand...
Click to collapse
Solved, thanks ^_^
Wish I'd found it before my 3 phone interviews at Google, luckily I got the job anyway

After messing around with the millions of apps claiming to boost volume, finally found this forum post and updated my kernel to fix the issue. Even Volume+ app support section admits they can't make any changes to in call volume because of kernel limitations.
I was confused with kernel to use from intersectRaven but had great success with the Tiamat kernel posted above.
N1 running 7.2 Cyanogenmod
Thanks guys!

[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] Problems with Touchpad CM

Have been using Touchpad CM9 for a long time, and 2 months ago reflashed it due to the '50 apps in sd card' issue. I reflashed it to the most recent CM9 nightly and it was stable with camera working and all. However what I realised was that there was this space at the top of the screen, about 2cm long, that does not detect any touch at all. This give problems as certain apps have tabs at the top and I can't access those tabs (for e.g. Browsers). On landscape the back button can't detect my touch (on landscape and with the "space" on my left). I wasn't really using my Touchpad much during this period but have recently been more active on it, thus its problematic for daily use.
I have just flashed CM10 over CM9 and this problem persists. I have went into developer options and enabled "Show Touches" and when I reach that "space" it stops detecting my touch and disappears. I would really appreciate it if someone could give me some help :/

iamatechnoob said:
Have been using Touchpad CM9 for a long time, and 2 months ago reflashed it due to the '50 apps in sd card' issue. I reflashed it to the most recent CM9 nightly and it was stable with camera working and all. However what I realised was that there was this space at the top of the screen, about 2cm long, that does not detect any touch at all. This give problems as certain apps have tabs at the top and I can't access those tabs (for e.g. Browsers). On landscape the back button can't detect my touch (on landscape and with the "space" on my left). I wasn't really using my Touchpad much during this period but have recently been more active on it, thus its problematic for daily use.
I have just flashed CM10 over CM9 and this problem persists. I have went into developer options and enabled "Show Touches" and when I reach that "space" it stops detecting my touch and disappears. I would really appreciate it if someone could give me some help :/
Click to expand...
Click to collapse
Do you have the same problem in webos? If so, it's probably hardware, if not I'm sure someone will jump in and help.

chicle_11 said:
Do you have the same problem in webos? If so, it's probably hardware, if not I'm sure someone will jump in and help.
Click to expand...
Click to collapse
Wow, you are right, webos has the same problem. I guess I was just in denial that it was a hardware issue and didn't think of checking it in webos. Damn, I don't think HP would want this back right
Sigh guess I should look into the chinapads my friend was recommending just this morning

Just wondering, is it possible to have android ruin the "hardware" aspect of the tablet? I am thinking of removing android and seeing if it exists still on my Touchpad.. Hmm..

iamatechnoob said:
Just wondering, is it possible to have android ruin the "hardware" aspect of the tablet? I am thinking of removing android and seeing if it exists still on my Touchpad.. Hmm..
Click to expand...
Click to collapse
No, android does not cause a hardware problem, AFAIK.
Use acmeuninstaller then follow this guide : http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
If after this you still have the problem, then you know that it's hardware.
Read the whole thing, it's very informative.
Edit : use cm10.1, it should give you access to the back button in landscape mode.

chicle_11 said:
No, android does not cause a hardware problem, AFAIK.
Use acmeuninstaller then follow this guide : http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
If after this you still have the problem, then you know that it's hardware.
Read the whole thing, it's very informative.
Edit : use cm10.1, it should give you access to the back button in landscape mode.
Click to expand...
Click to collapse
Thanks for the help! Will try this after backing up my stuff via Helium.
I have the impression that 10.1 isn't that stable, but I am likely wrong. Dont seem to see any cm10.1 with low deep sleep drain + working camera & mic + most other functions, or I could be looking at the wrong places.

I use milaq's nightlies, and for my needs, it's more than adequate.

[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

Invisiblek's 4.4 12-30-13 Nightly Impression

I can't post this on the Milaq thread (where most of the invisiblek discussion is) so I thought I would post it here to give anyone else a heads up.
The Good:
It's a fairly stable kernel and all my apps run seemingly just fine. I mean I've only been running it about 5 hours but not a single FC. I did have a weird bootup glitch that locked it up right away after install but after that I loaded all the apps just fine. Super exciting to see it so far!
The Bad:
Screen pixelation/tearing from left to right, especailly on grey backgrounds. Something is up with the video driver/gpu voltage. Certain icons like the Settings sprocket will have a few pixels that will flash and other times you'll see lines all the way across the screen. It might be color specific. I was playing Quadropus Rampage and never noticed it but then went back to the home screen or typing an e-mail and it's very much there.
Pandora plays music fine. If you turn off the screen while playing, horrific things happen like ZZZZZZZZZZZZ and then hard lock. I didn't like that station anyway..
The "OK Google" voice command doesn't seem to work though voice typing does. I'm pretty sure this worked on the Milaq build of the same date.
It's a bit slow and CPU is stuck to 1188. There is a bit of a lag switching apps but I don't notice any core functions slow.
The Different:
The home button doesn't wake up the TP. Only the power button.
Can't say anything about battery life quite yet but I'll keep a gander on it. Battery hasn't been a super concern of mine because I plug it in ever night

The Different:
The typical 15 second reset switch mult-button key is more like 3 seconds now. I like this a lot better.

Positive:
--backup and restore work
--it is getting much better.
Negatives:
--Microphone does not work, so I could not use any vioce search or voice dialer/sound recorder.
--Free game "F.S. Xtreme" has black box issue.
--Youtube still has reboot issue.
--TV streams app "syncbak" has similar reboot issue.

My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.

Switched to milaq's 3.0 kernel.
The CPU is pre-configured to run at much higher 1.5Ghz, yet the 3.0 rom is still able to run very stable.
I am waiting for camera fix to enable video calls.
Since both 3.0/3.4 rom are using the same CWM, it makes 3.0/3.4 rom switch very easy.

Waiting on Flintmans as it is the only non data media rom. Not a big fan of all the repartitioning. For several reasons. Good to see choices still available. God bless the developers for all their time and effort. Wish I could do what they do.

goog888 said:
Switched to milaq's 3.0 kernel.
The CPU is pre-configured to run at much higher 1.5Ghz, yet the 3.0 rom is still able to run very stable.
I am waiting for camera fix to enable video calls.
Since both 3.0/3.4 rom are using the same CWM, it makes 3.0/3.4 rom switch very easy.
Click to expand...
Click to collapse
I flashed 3.4 rom (0103) over 3.0, and tried briefly.
--3.4 rom seems running OK, except it runs relatively slower at 1.1Ghz.
--camera is not working on both 3.0/3.4 rom.
--Free game "F.S. Xtreme" seems not compatible with 3.x kernel. It also cannot run on Samsung S3.

Moody66 said:
My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.
Click to expand...
Click to collapse
Turn off WiFi Optimization in settings.

EbolaCola said:
Turn off WiFi Optimization in settings.
Click to expand...
Click to collapse
Still does it. Did that soon as rom booted as per the Op.

Moody66 said:
My wifi keeps shutting off and won't restart without reboot. Not even sleeping. Other than that it runs nicely.
Click to expand...
Click to collapse
Same here. Also double check that the setting took. I swear I unchecked it and it went back or didn't take the first time. Perhaps give it a toggle or two. I also noticed that if wifi turns off, it won't turn back on.

Anyone else having a problem with rebooting from within CM and it just goes to a blank screen?

Dirty flashed to the 1/5 nigthly. Reboot issues seems gone now, or just that a reflash has fixed mine specifically.

Just noticed that there is an official thread over at http://forum.xda-developers.com/showthread.php?t=2592909
Hopefully I can post there too!

sokratz said:
Just noticed that there is an official thread over at http://forum.xda-developers.com/showthread.php?t=2592909
Hopefully I can post there too!
Click to expand...
Click to collapse
Negative on the posting. I'm still seeing the bzzzz when the screen shuts off while playing music. Have disabled the mic (I think). Curious that nobody on that thread has reported that quite yet.

I'm very excited to see all of this development on our old TPs! I'm currently running Milaq's latest 3.0 kernel test build. It is running almost perfectly for me! I cannot wait for 3.4 to finish getting smoothed out. I've tried Invisiblek's builds out, and they currently seem a little laggy compared to Milaq's 3.0 test build. Great work all around though! Thanks to Invisiblek, Flintman, Milaq, JCSullins, Dorregary, and all of the others that I haven't mentioned who have contributed so much of their time and skill toward keeping our Touchpads relevant, even competitive with the current crop of tablets on the market!
Sent from my TouchPad using Tapatalk 4