yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] Mark376:
Hi [MENTION=4329165]ivanich[/MENTION] [MENTION=4817003]bilal_liberty[/MENTION] [MENTION=4800121]Sultanxda[/MENTION]

Any solution to fix audio speaker distortion at high volume? And in recent nightly it seems lpa causing seeking issue. Everytime i seek a music it play random note and continuously until i change music.
[HTC Sensation] sjknight413:
To fix the speaker distortion - get a new phone. Seriously.

I don't what you're all expecting from the sensations tiny little speaker but I know on my phone there is no distortion at full volume with ringtones or message tones.

The only thing I could see a problem with is music but if you are attempting to listen to music through a phone speaker you need to rethink why you listen to music at all.

I infact use xloud through viper4android to make audio louder and it is still fine.
[HTC Sensation] Mark376:
Try playing any music via Play music or Apollo..

I don't care if it loud or silent as long as it fine

my car has no radio that's why I need it,

and for my post, just forget about it
[HTC Sensation] ivanich:
Try change

1,0,0x00,0x82,0x00,0x07,0x6C,0x56,0x0D,#TPA2051_MODE_PLAYBACK_SPKR

for me it little bit better, default value is 0xCD, need to play with it more. Find value which suitable for your needs and post it here.
[HTC Sensation] sjknight413:
I'm pretty sure the correct value to change is 0x56, next to the one you pointed out. At least it always was in the days of using TPA2051_CFG_XC.csv. it's the value I've been using to make headset volume louder and it's working so I presume it's the right one

Values it can be changed too go from 0x51 which is quieter up to 0x59 then 0x5A to 0x5F for loudest
[HTC Sensation] Mark376:
How about 0x6D?

still need more testing though.

EDIT: I've changed the hex to 0x6D in first attach to all controller, second attachment only speaker is modified.
[HTC Sensation] ivanich:
0x6D is higher, I've started from 0x6D and it seems for me distorted. Now trying 0x64...

Btw, lowering next value doesn't change anything :(

---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------

So if you satisfied with 0x6D I can commit it to repository. :confused:
[HTC Sensation] sjknight413:
Well I didn't think editing TPA2051_CFG would do anything anyway as our device always used TPA2051_CFG_XC but if any value would change speaker and headset volume it would be that one.

Of course I apologise if I'm incorrect, but that's what it has always been
[HTC Sensation] Mark376:
it has no effect lowering it, :crying:

I remembered [MENTION=2212152]SebastianFM[/MENTION] audio fix in revelation 1.0.0 ~ 1.0.2 doesn't accept any TPA config, would you mind take a look @ the dsp calibration Sebastian?

I've lowered up to 0x64 and the volume to 0x54 and... finally no distortion, :D

and I test it with libaudcal and libhtc_acoustic from sultan rom, idk if it affect sound but worth a try.

I attach a flashable fix.

Would you mind commit it to team-senny github?

the TPA are attached.
[HTC Sensation] ivanich:
Have you tried those libaudcal and libhtc_acoustic in senny rom? Because audio libs from sultan rom incompatible with 3.4 kernel audio drivers and VC2 alsa blobs we are now using.
[HTC Sensation] Mark376:
Yes, only audcal and htc_acoustic, sound still working great.

with or without those libs LPA still causing seek issue. fixed by disabling it in build.prop
[HTC Sensation] ivanich:
Could you test TPA changes with original senny libs, because I don't want commit that old libs just for fun :)

Edit: Flashed your zip and can't hear any difference with that libs.
[HTC Sensation] Mark376:
Flashed original libs, still has same output,

Seems only TPA that play the role. Have you test it?
[HTC Sensation] ivanich:
Yes I've tried TPA changes, distortion still present but not so much as before. Can't see any reason to lower volume for other audio outputs.
[HTC Sensation] Mark376:
If I set to 0x52 the sound will be too quiet for everyone

I think 0x54 will only be noticeable in close distant (near ear) but its up to you.
[HTC Sensation] ivanich:
diff --git a/dsp/TPA2051_CFG.csv b/dsp/TPA2051_CFG.csv
index be6df56..69ad03f 100644
--- a/dsp/TPA2051_CFG.csv
+++ b/dsp/TPA2051_CFG.csv
@@ -2,7 +2,7 @@
#mode/kind/i2c_cmds[7],,,,,,,,,
#kind = 0:SPKR, kind = 1:HEADSET, kind = 2:Ring kind = 4:eek:FF,,,,,,,
0,4,0x00,0x90,0x00,0x00,0x00,0x00,0x00,#TPA2051_MODE_OFF
-1,0,0x00,0x82,0x00,0x07,0xCD,0x56,0x0D,#TPA2051_MODE_PLAYBACK_SPKR
+1,0,0x00,0x82,0x00,0x07,0x64,0x54,0x0D,#TPA2051_MODE_PLAYBACK_SPKR
2,1,0x00,0x8C,0x20,0x57,0xCD,0x55,0x0D,#TPA2051_MODE_PLAYBACK_HEADSET
3,2,0x00,0x8E,0x20,0x57,0xCD,0x16,0xCD,#TPA2051_MODE_RING
4,0,0x00,0x82,0x00,0x07,0xCD,0x56,0x0D,#TPA2051_MODE_VOICECALL_SPKR

I think that should be enough
[HTC Sensation] Mark376:
ok,

now one thing left, seek.. in sultan build, I don't have this issue, maybe an upstream causing that?
[HTC Sensation] sjknight413:
So i was right? it is the second to last value that changes volume. Just want to get this straight so i know i'm not doing something wrong with that file.
[HTC Sensation] Mark376:
See here for more info: http://www.ti.com/lit/ds/symlink/tpa2051d3.pdf @ Page 16
[HTC Sensation] sjknight413:
Sorry but i got absolutely nothing from that.

was i correct or not?
[HTC Sensation] ivanich:
Yeah, but problem is not in the max volume level by itself.
[HTC Sensation] sjknight413:
Okay thanks for the clarification
[HTC Sensation] papete:
It always amazes me how people can be so sure about something that is wrong... well, I can't complain, I make a living out of people that think they are sure about something wrong...
[HTC Sensation] Sultanxda:
TPA config is parsed by pyramid audio driver in the kernel. In the stock 3.0 kernel, the pyramid audio driver has a usage scenario for which TPA config to use, based on system revision which is probably provided by some HTC binary: https://github.com/sultanxda/sultan.../arch/arm/mach-msm/board-pyramid-audio.c#L320

In Sebastian's 3.4 kernel, he removed TPA config parsing from the audio driver, so any changes to the TPA config should do nothing (I don't know if any libs are using it).
[HTC Sensation] ivanich:
libhtc_acoustic.so read values from TPA2051_CFG.csv
[HTC Sensation] ivanich:
LPA was enabled in our rom "Jan 26, 2014", if this issue has appeared only in recent builds than it's a upstream cm bug.
[HTC Sensation] SebastianFM:
Not exactly, in HTC Sensation ROM the TPA config is parsed by audio libs and then data is sent to speaker amplifier tpa2051d3 kernel driver.

I didn't remove anything, just Revelation and ViperS uses audio libs from HTC JB for Ville C2. HTC removed support for TPA from these libs, so I created audio fix lib for Sensation, which configures speaker amplifier and sets it to correct mode.
[HTC Sensation] Mark376:
The bug occurred only in recent nightly starting from approx from Feb 18 ~ 21 hopefully cm will fix it soon
[HTC Sensation] mschipperheyn:
You work in politics?
[HTC Sensation] bilal_liberty:
your theory is wrong!

TPA config is still used
[HTC Sensation] Sultanxda:
You're a bit late:

http://xdaforums.com/showpost.php?p=51089097&postcount=1654

http://xdaforums.com/showpost.php?p=51094458&postcount=1656

:p
[HTC Sensation] Hamsterkill:
Here's my logcat of the issue playing music over bluetooth in my car.

http://pastebin.com/DAbQZuS7

The behavior is such that the music player (eg. Apollo or Vanilla) will attempt and fail to play a song and then skip to the next one, fail to play that and skip to the next one, and so on... The music player will also crash after several songs are gone through, which also appears in the log, and may be related to the failing to play.

This is from the March 9th nightly.
[HTC Sensation] ivanich:
Try latest build because I've disabled LPA and it could resolve your issue.

Edit: Also I see that there are a lot of equalizer errors, have you tried disable dspmanager?
[HTC Sensation] Hamsterkill:
You mean disable DSPManager in the App Manager menu? I'll give that a shot.

I'll try the latest build and let you know if it helps, too.
[HTC Sensation] bilal_liberty:
hahahha, just saw :D
[HTC Sensation] papete:
Haha, good guess... I invest in listed stocks... I make money when people is stupid enough to sell them to me too cheaply, or buy them from me for more than what they are worth.
[HTC Sensation] markNOOB:
How is battery life in this rom? Is better then other CM roms?
[HTC Sensation] lovendsuicide:
Interactive governor performance seems to be good, but has some problems, when screen is off for some time it lags pretty bad, seems that maximum frequency gets stuck at 192mhz and then gets back to normal like 15 seconds later... Would be a good alternative to ondemand if this bug gets sorted out.
[HTC Sensation] mschipperheyn:
I also use stocks. I sell them too cheaply and buy them for more than what they are worth. I may be a client :)
[HTC Sensation] lovendsuicide:
I'm having some issues with builds after the 0311. Everything works fine for some hours and then fc's start to happen all over the places. Made a logcat, don't know if can help in this situation.

https://www.dropbox.com/s/59zo0atw6cgusxz/logcat.txt
[HTC Sensation] farazejaz:
is 3.4 kernal the same as used in viper ? asking bcoz i want to know if usb otg without external power is available or not
[HTC Sensation] denis111:
It's forked and modified from the same kernel. Usb otg should work the same way.
[HTC Sensation] ivanich:
At least it enabled:

grep -R OTG .config
CONFIG_USB_OTG_HOST=y
CONFIG_USB_OTG=y
# CONFIG_USB_OTG_WHITELIST is not set
# CONFIG_USB_OTG_BLACKLIST_HUB is not set
# OTG and related infrastructure
CONFIG_USB_OTG_UTILS=y
# CONFIG_USB_OTG_WAKELOCK is not set
# CONFIG_USB_MSM_OTG_72K is not set
CONFIG_USB_MSM_OTG=y
[HTC Sensation] room311:
USB OTG is working in this rom?

what is bugs in this rom?
[HTC Sensation] primekrieger:
Do we have the latest 'Trebuchet Launcher' included in the ROM? Coz I read somewhere that now icon packs are supported by it, but I haven't found any option to change icons/apply icon packs yet :rolleyes:

Edit: Nvm, found it, just have to long press on homescreen :silly:
[HTC Sensation] GizmoTheGreen:
Anyone have any success with Netflix on this rom? image when playing movies is complete garbage! looks like a swap tile puzzle... P:

nightly from 16th march.
[HTC Sensation] ivanich:
- Skype videocall not working

- Front camera wont record video

- Probably HDMI not working
[HTC Sensation] Mark376:
Isn't sultan has fix that? Or just cleanup?
[HTC Sensation] ivanich:
FFC issues is related to HAL and it can't be fixed via configs
[HTC Sensation] denis111:
Is skype doesn't work because of the front camera won't record? If so then this not a bug but consequence of the front camera bug :D
[HTC Sensation] ivanich:
Skype videocall doesnt work because of missing 320x240 preview size, I have disabled it to fix preview dimension. Ffc video recording doesnt work because of some memory issues inside hal.
[HTC Sensation] Sajito:
Since some days I have the Problem that After some hours every app fc's and I have to restart to fix it for some time. Is that related to any upstream changes or to any changes to the Kernel?
[HTC Sensation] Kiranb212:
Very Low Speaker Volume..!!

I'm on latest nightly build cm-11-20140316-UNOFFICIAL-pyramid, audio output from the speaker is very low (looks like audio output has lowered to 50% when compared with cm-11-20140308-UNOFFICIAL-pyramid) i guess in attempt to fix the audio distortion have led to low audio output... can it be fixed ?

BTW... i'm in love with this 3.4 kernel... its fast n fluid no random reboots n FCs, amazing battery life lasts almost 19-24hrs with 2.5hrs of screen on time & 1.5hrs of talk time... what more...?? always have enough RAM memory... my Sensation never felt so young... all thanks to Team-SennyC2 3.4 kernel.. Once again Thank you all for this amazing kernel, appreciate all your hard work..!! :good::highfive:
[HTC Sensation] lovendsuicide:
I'm having the same issue, I posted a logcat a couple pages back, maybe you could do the same if it may help track the problem... for now I reverted to the last build that seems to be stable, the 0311 one.
[HTC Sensation] denis111:
+1, just noticed it today on 16m build but already rebooted(so no logcat).
[HTC Sensation] ivanich:
Try this build, I've increased KGSL_PAGE_TABLE_COUNT to 32 it could help with FC's issues

ftp://ivanich.org.ua/pub/cm11/cm-11-20140317-UNOFFICIAL-pyramid.zip
[HTC Sensation] papete:
Change TPA values, for that you can flash the "Volume boost" mod (it's called something like that), or you can change them yourself. Look for it on the forums.
[HTC Sensation] shantur:
The nightlies is fixed. There is a new build available and will again build tonight
[HTC Sensation] primekrieger:
Sorry, didn't get you. Do you mean both 'Low Volume' and 'Force Close' issues have been fixed?
[HTC Sensation] ivanich:
Shantur mean that nightlies build were fixed.

'Low Volume' and/or distortion probably will be never fixed, because we are using audio from Vc2 and there is the same situation as with camera libs.

'Force Close' issue should be fixed now
[HTC Sensation] primekrieger:
Thanks for clarifying. But the latest changelog states "dd840e1 TPA2051: Increase speaker volume", what does that mean then?
[HTC Sensation] ivanich:
It increases volume a little bit but not as it was before, so no significant changes just to lower speaker distortion.
[HTC Sensation] primekrieger:
Just to confirm, we are talking about the low volume in recent builds and not the low volume in general, right? Coz I was on the 2nd March build and volume was ok, flashed the 16th March build yesterday and suddenly volume was comparatively much much lower.
[HTC Sensation] ivanich:
There is 2 types of complainers, bass distortion at high volume levels and second low volume. Fixing distortion leads us to low volume. Personally I don't care about all that audio bugs, I can just revert all distortion fixes or leave it as is, again I don't care.
[HTC Sensation] primekrieger:
In that case, I think it would be better if distortion fix is reverted because there is no distortion on lower volumes anyways. What say?
[HTC Sensation] Kiranb212:
+1... even i can live with it... its not a big issue... given the great performance offered by 3.4 kernel :good:
[HTC Sensation] lovendsuicide:
Right now I'm using today's nightly, by looking at the changelog I see that fix is already included... in 5 hours of usage I had two times the FC situation. Here's another logcat from where the FC's started to happen.

https://dl.dropboxusercontent.com/u/29396398/log.txt

In the 0311 build there's no problems, so must have been something added or changed from there forward...
[HTC Sensation] papete:
Random Reboot

OK, I'm getting this reboots lately:

Phone soft reboots and then apps start force closing. I'm attaching last_kmsg in case you can find something...

Apart from that.... very smooth, and remaining bugs are being killed quickly, so thanks!!
[HTC Sensation] ivanich:
Your previous log shows that kgsl was out of memory, thats why I've increased kgsl page count because now we using kk kgsl and probably it requires more memory. In this log I can't see why it crashing, log is incomplete. Also I had no such FC, probably because I'm not using sensation as phone, it's only for fun :)

---------- Post added at 09:29 PM ---------- Previous post was at 09:22 PM ----------

Your kmsg log shows that kernel(oom killer) start killing all processes, something ate your ram. First victim was android.vending(Google play).
[HTC Sensation] Sajito:
I'm running latest nightly without any problems anymore...
[HTC Sensation] lovendsuicide:
Sorry for the incomplete log, just pasted from where it seemed to start crashing... here's the rest of it, hope it shows something.

https://dl.dropboxusercontent.com/u/29396398/log2.txt
[HTC Sensation] cclaxx:
Sorry Ivanich probably it's a stupid question but have you thought to rebase your rom on Flemmard's sources to solve stability bugs?
[HTC Sensation] ivanich:
It doesnt make sense, flemm kernel has his own bugs and as a result we will get combination of all that issues. I prefer to wait a little bit until his rom and kernel will be finished. Need to mention that many significant drivers were ported from flemm kernel.
[HTC Sensation] primekrieger:
So I flashed the 18th March build and weirdly the Volume now seems ok (Magically fixed? :confused: or I might need to get my head tested :D)

One issue though, Video Recording in Camera is not working :eek:
[HTC Sensation] ivanich:
cm camera crashes when selecting video mode, it's a cm bug http://review.cyanogenmod.org/#/c/61240/ and it already fixed http://review.cyanogenmod.org/#/c/61261/

---------- Post added at 10:51 PM ---------- Previous post was at 10:31 PM ----------

Unfortunately this log is the same, I will try to reproduce those crashes but not sure if it possible considering that I'm almost not using my sensation for its intended purpose.
[HTC Sensation] lovendsuicide:
Tonight I will do a full wipe and see if this goes away... If not I'll try to do another logcat. There's no pattern to reproduce this error, I just intensively used the phone for an hour or so and it happened the second time.
[HTC Sensation] ivanich:
Don't forget about dmesg log together with logcat if it happens again.
[HTC Sensation] Hamsterkill:
Finally got to try again today with the latest nightly. Music played over bluetooth fine. Didn't even have to disable the DSPManager.
[HTC Sensation] fujanto:
any chances for fixing voip , its seems long outstanding issues such uses for BBM voice, LINE n wechat etc

thank you very much for listening
[HTC Sensation] lovendsuicide:
It didn't take long to happen again after a full wipe... lets see if today's logs are more helpful :fingers-crossed:

https://dl.dropboxusercontent.com/u/29396398/logs.zip

Edit: First app that fc was youtube... This shows in the dmesg:

<4>[ 6977.170684] c0 15771 android.youtube: page allocation failure: order:6, mode:0xd0

maybe you can see the error from there?
[HTC Sensation] ivanich:
The same as before, kernel kill all apps because out of memory but reason not showed in this logs . In my opinion you have too many apps installed(kk.launcher, some sms app etc.) and any of them could cause this issue. Sorry I have no idea why it happens to you.
[HTC Sensation] lovendsuicide:
Not really, I don't have many apps installed, at least not more than the ones I always had since the nightly's began to roll out... and going back to the March 11th build the FC's stop. But indeed is strange that no one else seems to have the same problem so I'll try to figure it out, maybe some app update that went wrong.

Thanks for taking the time to look at the logs.
[HTC Sensation] mn.code:
On last two builds, I think, when you open received SMS by clicking on notification in status bar, notification doesn't dissapear, you have to remove it manually. But when you open that message from app by clicking on that person, the notification dissapears. So is this some CM upstream bug or?
[HTC Sensation] ivanich:
This should fix audio distortion and low volume issues. Please test all possible audio usage cases before it will be merged into repository.

Basically it just libacdbloader.so from mako(nexus4)
[HTC Sensation] Sajito:
I noticed today that I too have still the fc issue but not that often anymore... I'll make a logcat next time
[HTC Sensation] blogodoblogodo:
HI thks for your fix, Is it a Kernel Problem or others thing???

My question is maybe this will work on all new Kernel 3.4 ROMS ??
[HTC Sensation] ivanich:
Audio library issue, and yes it will work on all 3.4 roms
[HTC Sensation] denis111:
Tried some predefined ringtones and some youtube video. For me it sounds fine. I'd try to make it even louder in csv.

UPDATE: tried only loudspeaker...
[HTC Sensation] Mark376:
[MENTION=4329165]ivanich[/MENTION]

I've enabled lpa and tunnel, No seek issue so far I think cm has fix that,

idk if it related but I use this prop

lpa.decode=true
lpa.use-stagefright=true
tunnel.decode=true
[HTC Sensation] ivanich:
Tried it and seek issue is still here.
[HTC Sensation] papete:
No deep sleep

I'm on 18-3 build and had no FC. So for me that's cured (so far). What I still get, or better said, don't get is deep sleep in my phone. Like I said, the issue is random, sometimes it goes to sleep, but sometimes, like last night, it does not. As can be seen on the attached pics, the phone was put to Airplane mode and the juice just kept draining like hell...

Apart from that, excellent job.... The 3.4 kernel is light years away from the 3.0 kernel in terms of stability and performance!!
[HTC Sensation] WnG88:
[MENTION=1792279]ivicask[/MENTION] Should we use this audio fix with Venom 5.1? I get audio distorsion on 5.1 at high volumes.
[HTC Sensation] 3shen:
Hello there,

[MENTION=4329165]ivanich[/MENTION], i'd like to report a minor bug on my end. The volume buttons don't wake the phone up anymore. Yea i've checked that setting in the buttons menu.

Also, may i know which governor is better for battery life, ondemand or interactive ?

To you and the other devs, thank you very much for all your work on this ROM. Truly amazing
[HTC Sensation] ivanich:
Just checked volume buttons and phone wake up sometimes but not every time, anyway I am sure that this is a CM bug.

Interactive have some bugs, so use ondemand for now.

EDIT: Seems like sometimes need to press volume button 2-3 times to wake up phone
[HTC Sensation] 3shen:
alrighty, thanks for the prompt reply Sir !
[HTC Sensation] ivanich:
Install http://xdaforums.com/showthread.php?t=1179809 it will show all wakelocks including kernel related.
[HTC Sensation] 3shen:
[MENTION=4329165]ivanich[/MENTION], noticed another bug. I've set my max CPU frequency to 1188 MHz. When using ONDEMAND governor, the max frequency spikes to 1512 MHz frequently. This doesn't occur when INTERACTIVE is used, it obeys the 1188 MHz ceiling. I'm on the latest 20140320 build btw, full wipe.
[HTC Sensation] ivanich:
Fixed. Will be in the next nightly.

Oops, it's not fixed :(

Reverted to HTC's ondemand governor and removed interactive because it wont work well with htc kernel anyway.

Also updated ondemand governor from HTC One GoogleEdition 4.4.2, it brings new 'multi-phase' power-efficiency ondemand algorithm".
[HTC Sensation] papete:
Ok, betterbatstats is giving me more useful info:

The pics show the device awake all the time while in airplane mode, Kernel wakelocks show PowerManagerService keeping the device awake, and partial wakelocks show GpsLocationProvider keeping the device awake. I added a process pic to show that no process was directly involved in keeping the device awake.

I don't know if it is an issue with the kernel or some badly written app, but it does make sense to me as the "no deep sleep issue" happens usually when I activate my "outdoor" tasker profile, that sets the location profile to high accuracy and I usually use some GPS related app (maps, navigation).

Please let me know if you can solve the issue and if I can help you in any way to do it.

Thanks
[HTC Sensation] cclaxx:
hi [MENTION=4329165]ivanich[/MENTION] , I think there is a problem in reading the battery voltage. I tried it with two different batteries, and both the maximum value read is only 4mv! I also noticed a lot of reboots when it reaches 30% of charging so i yj can you give me a hand? thank you
[HTC Sensation] smint86:
Should be related to your battery(s), besides that battery calibration tools are useless, the stats are wiped after reboot anyway.

Swyped via Tapatalk
[HTC Sensation] cclaxx:
i know i used the app only to check the voltage values. Please can you also download the app to see if your values ​​are correct?