Friday, 2011-11-25

*** rpierce99 has quit IRC00:11
*** rpierce99 has joined #xdandroid00:58
*** rpierce99 has quit IRC02:10
*** kalemas has joined #xdandroid02:15
*** bzo has quit IRC02:17
*** kalemas has left #xdandroid03:44
*** virsys has joined #xdandroid03:56
*** kalemas has joined #xdandroid04:32
*** hardwalker has quit IRC05:15
*** rpierce99 has joined #xdandroid05:28
*** rpierce99 has quit IRC05:34
*** babijoee has quit IRC05:35
*** SytheZN has joined #xdandroid07:25
SytheZNI dunno what I'm missing here...07:26
SytheZNI'm running ubuntu 10.10 on virtualbox, 64-bit. I've just restored my clean image, re-followed the setup, fetch and build instructions but I'm still getting errors :?07:28
SytheZNTried a clean reinstall as well, to no avail07:29
SytheZNI'm assuming its an id-10-t error again, but I don't know where I'm going wrong07:30
*** helicopter88 has joined #xdandroid07:58
*** kalemas has left #xdandroid08:20
*** kalemas has joined #xdandroid08:21
*** babijoee has joined #xdandroid08:55
*** SytheZN has quit IRC09:09
*** babijoee has quit IRC09:14
*** kalemas has quit IRC09:36
*** rpierce99 has joined #xdandroid09:41
*** emwe has joined #xdandroid10:10
*** |Jeroen| has joined #xdandroid12:17
*** emwe_ has joined #xdandroid12:58
*** emwe has quit IRC13:01
*** |Jeroen| has quit IRC13:02
*** emwe_ is now known as emwe13:05
*** rpierce99 has quit IRC13:38
*** rpierce99 has joined #xdandroid13:39
mgross029Hey emwe,  How goes it?13:40
emwetrying to get ahold of the initially so calm ringer/dialtone/notification volume.13:41
emwei had already burned openSUSE 12.1 for getting this onto another partition here and testing out ... but then i could somehow motivate myself :)13:42
emwedunno for how long.13:42
mgross029Oh so you mean making sure that volume is handled properly when the initial alert/ringer comes in?13:43
mgross029Yeah I do all of my linux on VM here.13:43
mgross029Makes it easier to build and blow up. :)13:44
emweyes, but also normal notifications are too calm imho13:44
emwelike sms or gtalk13:44
emweor mail. whatever.13:44
mgross029Understand.  I know exactly what you are speaking of related to the sound.  I was getting sms and it was garbled at times yesterday.13:44
emwedamnit. i always need to kexecs or killall zygotes to get service back...13:45
emwei mostly miss any notification except calls because there's vibrate :)13:45
emweapart from that, you got no incall mic issues i recap?13:45
mgross029Also, after I said all was working well yesterday I had a kernel panic on a gps app then my ringer and mic reverted back to a problem state.13:46
emwei was looking into acoustic yesterday and then asking myself.. what bugs am i chasing here... got no issues i know off :)13:46
emwehm.13:46
emwegps and getting a call mostly resets here13:46
emwethat's to be resolved on another day.13:46
mgross029I've seen those resets before too.  Tells me that ril and acoustics may still be tied together, which you and detule were talking about the other day.13:47
emwewell, there's still that mute issued to modem processor. perhaps can be dropped.13:48
emwebut in combination with GPS all sorts of stuff might break...13:48
mgross029If anyone were to ask me what the priority of this project would be in order to get it out into public release that would be acoustic, which is sounds like that is what you are working on. :)13:49
emwebecause we are reading out GPS data via rpc, which also the kernel drivers for the mic-bias for example.13:49
emwewell, i can't promise anything.13:49
emwejust that initial notification tone volume and i'd say just push out and be done...13:49
emwewe got no mass tests... nothing to judge from.13:50
mgross029I noticed that when I enabled a boot up sound it seemed to help sometimes with initial notification and ringtones.13:50
emwethat "sometimes" in your sentence sounds undeterministic.13:51
mgross029Yeah it sounds like we are getting a few more folks back into things but until we release an updated beta we may not have enough feedback.  I agree13:52
mgross029Well I only tested it for a short time that way.  Then I went to a fresh data.ext4 with another build and seemed to be working well after the new image13:53
mgross029So, I am not sure of the consistency of my testing with a boot up sound.13:54
emwebah, it's partially not picking up my pushed libs .... yet another restart...13:54
emwelet's see what i can find out by the logs...13:54
emweit always unsets (zeros) the audio device vol when it thinks it's doing an device change.13:55
emwezero volume doesn't mean off, but slightly hearable.13:55
emwesounds what we got here...13:55
emweanyway, back to digging.13:55
mgross029Yep I remember reading that.13:55
mgross029Ok.  Sorry to distract.13:56
*** Jeeva has joined #xdandroid13:56
emwenah, your welcome for a chat. been calm in here anyway ;)13:56
emwemy mac&cheese needs a warm microwave welcome.13:56
mgross029lol13:56
*** Jeeva has left #xdandroid13:56
mgross029Just out of curiosity could we easily build an image so the debuging is cut to a minimum and see if that helps?  I noticed a little better response after you calmed the led debug on one of your latest commits13:58
emwethat's mostly kernel needing to drop debug output. when on wake we so much pollute the kmsg buffer it might also delay stuff13:59
emweuserland isn't the least verbose either ...13:59
emwei dunno if acoustic debugging is on in the last build i did.14:00
emwehm, stupid. it always takes to restarts (hot restarts) in order to get network operational here...14:00
mgross029Yeah that is wierd.  I have issues when booting into WM.  I almost always come up without network and then it causes the phone not to respond at times.14:01
emweoh ;)14:02
mgross029I do notice a lot of acoustic messages in logcat14:02
emwenot to respond in wince or android?14:02
mgross029wince14:02
emweare they prefixed with V/?14:02
emwelike this? 11-25 19:57:22.371 V/AudioHardwareMSM72XX_wince( 7544): setP....14:02
mgross029IIRC yes14:02
emwethen yes, verbose debugging was on then.14:03
mgross029Correct14:03
mgross029Those are the printk statements correct?14:03
emwenope, logcat.14:05
emweprintk is dmesg/kmsg in kernel14:05
emweuserland has logcat.14:05
mgross029Ah ok.14:06
mgross029Thanks for the clarification14:06
emweman, this doesn't really sound like a libaudio/kernel issue with those sounds.14:08
emwebecause all the volume/level adjustments are computed by audiomanager.14:08
mgross029audmgr.c right?14:08
emwewhat bugs me is that qualcomms librarry has a volume range from 0-7 .. we only 5.14:08
emwenope, the kernel land one.14:09
mgross029Hmm that is interesting.14:09
emweand when i slide up, it get's ultra loud and back to the old position it is louder then before14:09
mgross029I noticed in the logs that you saw we were splitting some things out unlike Code Aurora14:09
emwethen after 1-2 secs audio devices are shut off again.14:09
emwe(visible in kernel)14:09
emweand then you start over again....14:10
emweso as soon as audio devices are turned off, it's all reset.14:10
*** ImCoKeMaN has quit IRC14:10
emwebut if you don't let them go off after some idle time the "new/louder" volume will persist.14:10
emwegoing looki looki :)14:11
mgross029Which would solve wake up with no audio right14:11
emwepardon?14:11
emwei am just investigating the "sound is too calm initially" stuff14:11
emwedo you mean that with wake up with no audio?14:12
emwetoo calm ringer vol?14:12
mgross029Yes14:12
mgross029Or even notification volume is too calm14:12
emweyeah ok.14:13
emweso, userland volume bar has 7 (!) steps. that's it, i am sure.14:13
emwewe only support 5 as far is i grasped the whole years.14:14
emwelikely our acoustic csv do the same.14:14
emwenow let me figure where we can tell userland we only support 5 nuances.14:14
mgross029I would agree.  That is all I see is 5 in the code14:14
*** mgross029 has quit IRC14:15
*** mgross has joined #xdandroid14:16
*** mgross is now known as mgross02914:17
mgross029Sorry server rebooted on my. -_-14:18
*** mgross029 has quit IRC14:22
*** mgross029 has joined #xdandroid14:23
rpierce99at least on mine, i can hear the difference between all 7 levels14:23
mgross029rpierce99, how do you determine that you are hearing those additional 2 levels?  Just curious14:25
rpierce99i just hit vol up/down 7 times and listen to each, they are noticably different14:26
rpierce99just the little "beep" when changing volume14:26
mgross029Yeah you are right.14:26
mgross029I notice that here too.  Never realized that before.  Seems to almost go a bit higher.14:27
mgross029Actually if I keep pushing the up volume it just keeps getting louder.14:28
rpierce99agreed, it is capable of getting very loud but the volume slider runs out of room maybe midpoint14:29
mgross029I noticed I really don't hear the beep any longer when I turn it down to mid volume14:29
emwego to tone volume settings ringtone .. change slider to 50% and remmeber/listen how loud it is, then slide to max and then back to 50%. it will be louder on 50% then before.14:29
mgross029ok14:30
rpierce99if i put my ear up right next to the speak i can still make out a beep all the way to the lowest setting, but its a level that is really not practical for a ring14:31
rpierce99s/speak/speaker/14:31
emwebut these lower levels are "leveled" wrong in software /methinks14:32
emwelet me go play a bit...14:32
mgross029Interesting to note there are 7 levels on the volume slider14:32
emwethat's what i said like half an hour ago.14:34
emwe:P14:34
mgross029Sorry didn't not even catch that. lol14:35
mgross029I even just reread it in the logs...  lol14:35
emweperhaps i am chasing a placebo here. I'll see.14:35
emwehaha... or we haven't updated libaudio correctly because it was made for froyo... lol14:36
emwejust looked qualcomms initial gingerbread port of their froyo code...14:37
emwe-    int vol = ceil(v * 5.0);14:37
emwe+    int vol = ceil(v * 7.0);14:37
emwegood morning.14:37
mgross029Wow that could be an issue14:37
rpierce99well i think that implies that they knowingly changed it, so 7 is likely correct14:38
emwesomebody got a froyo setup around running?14:39
rpierce99not running but i can easily reboot into froyo14:39
mgross029rpierce99 beat me to it. :p14:40
emwedon't waste your precious time guys14:41
mgross029http://gitorious.org/liquide/hardware_msm7k/commit/d437fe26e915924f2cc1a44ffa0bc8bd3323543a/diffs14:41
mgross029Interesting.  Looks like CA did it when they went from eclair to froyo14:42
mgross029Made the change from 5 to 7 that is.14:42
emwehm, why did this issue never crop up in froyo then for us?14:44
emweor is it around there too?14:44
mgross029Well we had some audio problems with froyo.  Acoustics always seemed to be a problem14:44
mgross029Static in speaker, etc, etc...14:45
emweand this specific issue?14:45
mgross029Not sure its been so long since I've used froyo14:46
mgross029Checking AudioHardware.cpp I can't even find it in ours.14:48
mgross029Nevermind.  User errors. :p14:49
emwewe got other places though where we skip vol>514:49
*** kalemas has joined #xdandroid15:10
*** kalemas has left #xdandroid15:10
mgross029Found this entry volume = ceil(volume * 7.0); as well at lrint(v * 5.0)15:22
mgross029s/as well at/as well as15:23
*** jonpry is now known as invite15:26
*** invite is now known as jonpry15:26
emwehm, damnit. there a "volume * 6" piece of code for the tpa2016d2 speaker amplifier... which looks bogus, too.16:00
emwethe tpa2016d2 supports -28dB to 30dB, so 59dB steps. then volume * 8 sounds more logical... given the register works like that ;)16:03
mgross029As the rabbit hole gets deeper. :)16:06
emwei see qualcomm pushing that userland volume range (0-7) just off to kernel which then communicates that via rpc call. now what if our CSVs and the acoustic data we upload don't even support 7, or rather 8 settings...16:08
emwei should look at those csv, eh? ...16:08
mgross029Do you have them some where handy?  If not I can get them easily16:09
emwegot them here.16:09
mgross029ok16:09
emwealso on the sd root :)16:09
emweeven got yours here with the xda mods16:11
mgross029Looks like 0-5 in AudioPara3.csv16:12
emweyappediyapp16:14
mgross029So I wonder what will happen when I put this new system.ext2 with volume 7 in. :p  heh  Just experimenting over here.16:17
emwelet me tell you i fooled myself?16:18
emweuserland will report set from 0.0 -> 1.0 ... so there is nothing stopping us from multiypling this by 5 ...16:19
mgross029by 5 or 7?16:20
emweperhaps they updated their csv with 8 (0-7) settings for their devices.16:20
emweby 516:20
mgross029Ok16:20
*** detule has joined #xdandroid16:34
*** helicopter88 has quit IRC16:37
emweok, the tpa2016d2 gain register definitively operates in dB.17:01
mgross029ok so does that mean it will needed stepped up?17:04
mgross029s/needed/need17:06
emwethe volume level (0-5) needs to be transformed into the possible dB range.17:06
emwe0 register value is actually 0dB ...17:06
mgross029Ok.17:07
emweone can set from -28 to +30, but only if compression ratio is off... just checking what we set17:07
emweotherwise if compression ratio is on, only from 0-30dB17:07
mgross029I see.17:07
emweok, compression ratio seems off, so we can distribute the 0-5 among all possible values it seems.17:08
mgross029So those tpa2016d2 settings take place in the kernel not userland, right?17:18
emweuserland sets them in libacoustic via ioctl to the tpa2016d2 driver, which in turn sends them over via i2c to the chip itself.17:21
emwes/sets/sends17:21
mgross029Ok.  Understood.17:21
mgross029emwe, going to get away from this for a bit.  Laters18:17
emweyeah, will likely postpone till tomorrow as well18:19
emwelaters mgross029.18:19
mgross029Yep getting pretty late there. Tomorrow's another day. :)18:20
*** babijoee has joined #xdandroid19:00
*** detule has quit IRC19:13
*** detule has joined #xdandroid19:17
*** detule has quit IRC19:37
*** detule has joined #xdandroid19:48
*** rpierce99 has quit IRC19:53
*** detule has quit IRC19:56
*** emwe has quit IRC20:31
*** babijoee has quit IRC21:08
*** rpierce99 has joined #xdandroid21:43
*** babijoee has joined #xdandroid22:03
*** [7] has quit IRC22:29
*** TheSeven has joined #xdandroid22:29

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!