yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] the entity:
Dock audio has always worked fine for me.... Didn't even realize the sentence till now.
[Fascinate Android Development] JJHunterx:
Has anyone had an issue with the phone randomly waking itself up and turning the screen on? No notifications, phone calls, voice mails or texts. Not sure if it's a kernel or Rom problem.
[Fascinate Android Development] Skrazz:
Yes. I get excited like it's a hot babe sending me a text only to see nothing. The log does not seem to provide any clues. Polling could be causing a wake, as it only seems to happen when I have data or wifi enabled.
[Fascinate Android Development] skiddingus:
Yes, I get this occasionally on by mine and my wife's Fascinate. It has done it on several different kernels. Could be a PWGB issue but it doesn't seem to hurt anything. One clue on what may be causing it: both of our phone woke at exactly the same moment once tonight. This couldn't possibly be a coincidence. Thier only possible connection was the verizon time and the wifi in the house. One of the two had to cause the synchronized waking.

---------- Post added at 08:23 PM ---------- Previous post was at 08:20 PM ----------

The kernel is AWESOME but I have to say the volume is a little too loud on my phone. The speakerphone on minimum could wake the neighbors. Thanks for the hard work!
[Fascinate Android Development] JJHunterx:
I went out of town last weekend and it woke several times without WiFi on. Not sure what the issue is.
[Fascinate Android Development] comradesven:
I think I've noticed this once or twice but never thought anything of it. When did it start?

The best way to track it down would be to have the phone connected to a computer with logcat running constantly, and looking at what woke it up, and also looking at the last few dmesg lines. This is difficult to do in practice, of course. Skrazz, if you're reading this, are you saying you already tried this and nothing showed up?

Yes, I changed the default amp gain to 0dB as one of the first things I did with this kernel. The default is a little too low with my headphones, and I got tired of using an init.d script to set it so I didn't have to do it manually. This kernel is primarily about what I want, after all :) Which is to say, I'd be doing most of this tweaking anyway.

And yes, I am going to look into playing around with zram.

I agree it's even a bit distorted at maximum volume, and I expected that there'd be a period of ironing out the settings.

Any of you guys have any thoughts on the mic boost values I baked in? The mic boost changes depending on situation, as I said, and that is what I'm most iffy on at the moment.
[Fascinate Android Development] droidstyle:
I have to agree, the volume is almost distorting the speaker when its on the lowest setting. Went back to 10/05 build for now. Still a great kernal. If I turn the volume down then up it gets plenty loud on the older version anyway.
[Fascinate Android Development] comradesven:
By system click, just so there's no confusion, I'm assuming you mean the little click that you can enable to sound when you choose on-screen menu items and such. From what I understand of the drivers the only way I could make that go down is if I reduced the loudness of the speaker altogether, which was the situation in Eclair anyway, except while using the speakerphone, because that is a separate codec mode in the drivers. So I'm thinking that editing the sound files is probably your best bet.

The sound code is a mess anyway and they added what appears to be TTY support (for deaf people, though truth be told I have no idea what it really is) into it so I've got that to deal with as well if I commit myself to cleaning up the drivers by porting some AOSP code. And the AOSP code is pretty messy to begin with.

Are you saying that dock audio works for you right now? Because that would be interesting.
[Fascinate Android Development] laureanop:
Analog gain is at the optimal level, anything higher creates a lot of distortion. That was my voodoo setting anyways, so now I don't have to adjust every re boot.

The in call volume can comfortably he adjusted by the rocker
[Fascinate Android Development] comradesven:
I somehow skipped over this but good job noticing that two phones did this at the same time. That points to something like a carrier-initiated update check. At the very least I think that it's now pretty unlikely that it's a kernel issue :)
[Fascinate Android Development] comradesven:
Would you say that the call volume setting preserved from one call to the next or is it going straight to max boost with every new call? I can't make up my mind as to which.
[Fascinate Android Development] laureanop:
It preserves every time. Meaning whatever volume level I had on the previous call it's the level of the next call

PWGB,TKSGB10-10, adren shot xix, honeycomb2.03, ec09 radio.
[Fascinate Android Development] skiddingus:
The Verizon update check probably makes the most sense. Maybe it's Verizon collecting their "mobile usage data". :) Did everyone get their e-mail a few minutes ago telling you how they are collecting data about everything you do on your phone for marketing purposes unless you opt out?
[Fascinate Android Development] laureanop:
Mine does the same thing everyday around midnight

PWGB,TKSGB10-10, adren shot xix, honeycomb2.03, ec09 radio.
[Fascinate Android Development] Skrazz:
I used the log in the "Android Info" app. I can try to quickly export the log next time i catch this bugger in the act.
[Fascinate Android Development] QuattroMechanic:
I'm on geewiz 2.0 with its kernel and I'm gonna try this kernel but is there any other steps to flashing this in cwr? Like cache or dalvik clearing. And do I have to enable voodoo from recovery before boot like usual?
[Fascinate Android Development] laureanop:
Clear your dalvik and battery stats. It should do the conversion on first boot. You should hear a female robotic voice. Don't freak out, the process takes like 5-7 minutes.

PWGB,TKSGB10-10, adren shot xix, honeycomb2.03, ec09 radio.
[Fascinate Android Development] QuattroMechanic:
Ok cool, I won't freak.... I promise.
[Fascinate Android Development] the entity:
I've never had a problem w/ dock audio since the initial release of the kernel. Maybe people don't know that you have to tick the little speaker icon to get it working? Or on a rom without the car/desk dock app you need galaxy sound redirector.

Also I'm loving the new volume.
[Fascinate Android Development] QuattroMechanic:
I tried watching a netflix movie and no differ. In volume seems as loud as it used to. Wish it was louder.

Oh and I was just using the speaker not headphones. I'm using geewiz2.0 this 10/10 tksgb kernel
[Fascinate Android Development] s44:
Well, I thought there was a translation table somewhere that linked the user-settable volume levels (0-7) to actual volume levels (0-100) for each category of sound. The problem with Eclair was that volume 7 for "system" was too low (so voice nav was inaudible!); the problem with Froyo+ has been that volume 1 is too high (so clicks are massively loud when on at all).

In Eclair, you could adjust the table values yourself with a hidden menu like this. I figured the actual/original values were in the kernel somewhere so each of the steps could be hard-altered there just by tweaking a few numbers. But maybe I'm wrong, and that's why it's been so hard to raise the top levels of call volume.

In any case, you're right that I could alter a bunch of the oggs in /system/media/audio/ui, and that's almost certainly easier than bugging you in this thread. :D
[Fascinate Android Development] skiddingus:
Well after playing for another day, I can say two things. This kernel is awesome and the speakerphone is definitely too loud. Depending on the call origin, I had calls that were distorting on the minimum setting. The phone earpiece volume is a little too loud but not as distorted as my speakerphone. I look forward to the next update.
[Fascinate Android Development] laureanop:
After using the phone for a couple of days I have to agree with you.

@comradesven is there a way to lower these ear piece,speaker and Bluetooth gains?
[Fascinate Android Development] kwinders:
+1, I really appreciate your work. I for one feel the volume is too loud, I turn it to the lowest setting so it's not so loud. Thanks though, really.
[Fascinate Android Development] comradesven:
Thanks for your feedback about volumes. I'll put out a new build with some changes in a bit. More feedback is appreciated as they might still be on the side of being too loud, due to the way the fix was implemented, and I'm trying to find out which changes do what.

I even tracked down the bug someone earlier was having with Bluetooth pegging the phone at 1440MHz. (Although it looks like the default behavior was to peg it at something like 200MHz, but oh well.)
[Fascinate Android Development] AtropineNa:
is the mobileap the built in wifi tether for this kernel? or do we have to find our own wifi tether app? its not monitored right? thanks!
[Fascinate Android Development] InPocket:
Barnacle Wifi Tether - free in the market
[Fascinate Android Development] kwinders:
It is possible to use Mobile AP, if you first make the id change with qpst. There is a thread on how in the general section. I've using it for a couple weeks now with no issues.

Yes, there are several apps that you can use but I prefer the built in AP.
[Fascinate Android Development] ssewk2x:
Just out of curiosity, are you getting the call volume stuff from the glitch kernel? You're welcome to Kang whatever you want from it, btw...well, maybe I shouldn't say that, but as far as audio stuff, since that is my own work, I say go for it if it will help you out. For other stuff, it would be polite to ask sixstringsg first, probably :)

I'm also going to have a look at your stuff and see how it compares. Maybe I can find a solution to the speakerphone echo problem there.

Other than that, we seem to have taken care of the "too loud" issue in our kernel, so it may be worth looking at.

http://github.com/Efpophis/Glitch
[Fascinate Android Development] jcurley:
GREAT! I will love this now. I am downloading now and will let you know how it works.

Thank you!!!

Edit: WOW that speaker is loud!!! If I turn it up, it is too loud though. Will use it for a couple days and let you know.
[Fascinate Android Development] mgrimmenator:
i tried this kernel out and can't get to work. i get random crashes and reboots. when i switch back to my other kernel all is good. i wipe dalvik and other cache during install. do i have to do full wipe for this?
[Fascinate Android Development] laureanop:
I installed 10-12 last night and here are my observations. The low memory killer tweaks have allowed me to get rid of the memory optimizer :great job.

In call volumes:the phone has eight volume levels.

. Ear piece: on 1010 volume was very distorted at the fourth level, on 1012 at the sixth.

. Speaker: 1010 at the third, 1012 at the fourth

. Bluetooth: 1010 at the second, 1012 at the fourth.

Very close to achieving perfection imo. Thank you very much for your hard work

PWGB,TKSGB10-12, adren shot xix, honeycomb2.03, ec09 radio.
[Fascinate Android Development] ssewk2x:
So I just had a look at your source, and answered a few of my own questions, lol.

Instead of hard-coding the values for the incall audio and mic gain boosts, you can have a look and kang the changes I made to wm8994_voodoo.c, which allows them to be adjusted via sysfs, just like the other voodoo parameters. That way, users can use an init.d script or (as soon as someone writes one) an app to adjust those values.

I also noticed the driver code is almost completely different from the stuff used in AOSP roms, so I have a few questions to ask the people using this kernel related to call audio:

1. do people you are talking to on speakerphone hear an echo of themselves?

2. do you find that the call volume drops off sharply as you turn it down, or is it nice and linear down to silence?

3. how is media playback volume through the speaker?

4. for all of these, what is your overall impression compared with an older kernel from before all the call audio issues surfaced?

What I'm getting at here is that if this EH09 based kernel has over-all better audio drivers than the AOSP kernels out there, I might have to consider porting *cough* kanging *cough* them. Or at least using them as a guide to do a serious overhaul.

Thanks!
[Fascinate Android Development] laureanop:
1- no echo whatsoever

2- linear up or down. It preserves the last call volume

3-excellent quality with no distortion at all

4- although the volume was lower than in froyo, I never found it to be an issue (as opposed to aosp volume which was insanely low). But it helps to have that higher level in loud environments.

Thank you for your help

PWGB,TKSGB10-12, adren shot xix, honeycomb2.03, ec09 radio.
[Fascinate Android Development] ssewk2x:
Thank you very much. It sounds like you've got a good thing going here. As long as you don't mind, I'm going to see if I can get some / all of these fixes into the Glitch kernel, and hopefully the other AOSP/MTD kernels.
[Fascinate Android Development] laureanop:
I'm sure comradesven doesn't mind. Whatever helps the community.

PWGB,TKSGB10-12, adren shot xix, honeycomb2.03, ec09 radio.
[Fascinate Android Development] jcurley:
Try clearing your voltage setting first. You may have a conflict in Voltage when you flash the new kernel.

Not sure if this will help, but it might.
[Fascinate Android Development] comradesven:
Hi Efpophis/ssewk2x.

As you have no doubt already discovered, my in-call audio patch is pretty much an earlier version of your code, as, by his own admission, was jt1134's. And yes, I had been intent on kanging your changes to Voodoo Sound for just that reason. The difficulty is that I am by no means a real developer. I don't know any useful programming languages besides some very small experience with *snicker* Visual Basic long ago, certainly not C, and although I've picked up some by digging through kernel changes I can't do a damn thing without having someone else's working code as a reference to kang from. I was holding off while I got a better understanding of the AOSP code, for which the dock audio patches out there I've seen are written, so that I wouldn't be going into it completely blind.

Anyway, you can see that the EH09 code does all the codec pathway definition stuff the AOSP code does, just hard-coded instead of using the constants in wm8994-def.h and bitwise operations, so adapting the AOSP code to the EH09 driver wouldn't be too difficult, even for me, just time-consuming. If you do end up doing a driver overhaul I would certainly not be averse to using those results.

And yes, Glitch and Talon are the two main sources from which I've kanged enhancements. Carefully. As for your questions:

1. Yes, sometimes. More prominent on higher volumes, of course.

2. It's linear enough, I think, but however many % according to the ROM is still boosted by however many dB is hardcoded into the sauce.

(I could be wrong in the details about 1 and 2, not much testing done)

3. Better than it was on previous ROMs. Probably the best of any release so far, maybe still not loud enough.

4. If it weren't for the in-call values I think the audio code is as good as it gets. Still isn't very good, I know. :)
[Fascinate Android Development] comradesven:
I released work on this kernel to encourage more development on TW GB for i500 although it looks like as far as the features I wanted go I ended up implementing them myself more often than not. Damn straight I don't mind. I don't have any idea what I'm doing.
[Fascinate Android Development] laureanop:
For somebody who has no idea of what he's doing you churn out some pretty good work man . Thanks.

What changes did you make to the low memory killer?. With this and the vm heap size at 32 no need for the optimizer

PWGB,TKSGB10-12, adren shot xix, honeycomb2.03, ec09 radio.
[Fascinate Android Development] ssewk2x:
Ok, good to know, thank you.

For the voodoo sound stuff, I'd be glad to help out however I can. I think you can just copy-paste my stuff in and it should all just work. If you like, tho, I can fork your repo, do it myself, and shoot you a pull request. It shouldn't take too long at all if you're interested..
[Fascinate Android Development] droidstyle:
I agree 100% wit laurenop last post! The 10/12 kernal is by far the best kernal for eh09 to date. the low memory killer changes did wonders. Not to shabby for not being a "real developer":p Comradesven, you sure have provided some great work for the fascinate community!:)
[Fascinate Android Development] comradesven:
https://github.com/kangtastic/sch-i500-gingerbread/commit/a74905f733b8cb7003dd39967f222b81178cb947

For that, refer to Git. It's not too hard to understand conceptually. Ignore the changes to /ref/ramdisk/init.rc, it gets replaced by /src/ramdisk/init.rc in the ramdisk at buildtime. init.rc is like the old DOS autoexec.bat. It sets up the environment and as part of that sets lowmemkiller values upon boot. The line that says write to /sys/blahblahblah is configuring the lowmemkiller driver and the values there are apparently supposed to match the ones set by setprop slightly further up. Allowing for the driver only having 6 steps, as you can see, is handled by making some of the setprop lines set the same number of memory pages as other setprop lines. Apparently the mismatch crept in somewhere and Android didn't like it. I noticed V6 Supercharger modified these values to match and then discovered that the defaults were incorrectly set.

Most of the changes I made are easy enough to figure out like this once you look at them, and read documentation if necessary.

No need for that, I can do things like that easily enough myself (what do you think I've been doing? ;)), and I don't want to impose.

Thanks for the work you already did.
[Fascinate Android Development] laureanop:
@comradesven I just checked the new memory values and those are pretty much like the optimal settings in autokiller memory optimizer that I was using. No wonder the phone responded to the new kernel so well.

Was it Samsung coding not matching android memory management coding?.

Btw, what's your take on vm heap size for this phone. Without a doubt, my phone runs way better at 32 than at 64 and even 48.

PWGB,TKSGB10-12, adren shot xix, honeycomb2.03, ec09 radio.
[Fascinate Android Development] comradesven:
You can find that out for yourself. If you refer to the init.rc in the stock ramdisk I put in the tree for reference purposes at https://github.com/kangtastic/sch-i500-gingerbread/blob/master/ref/ramdisk-stock/init.rc you can see that the error was added downstream somewhere, so no, Samsung isn't at fault. Somebody was careless.

I'm not sure about heap size but I intended to change that to 32 by default if I could anyway so yeah. Like I said, this is all still very much alpha, and there aren't very many tweaks in it yet.

We shouldn't forget that Samsung et al. are major manufacturers and they have money and lawyers and carrier reps liaising with them to make sure that after QA testing certain minimum standards will be met. Expect that an official release probably won't have anything much outright broken. We might look upon RFS and cringe but in the big picture it's part of a greater whole, an up-to-spec kernel/ROM firmware package that passed those QA tests and allows them to quote ridiculous-sounding numbers like 200 hours standby time or whatever it is. A rooted custom kernel/ROM combo is never going to fly with corporate customers when the phones are going to be storing trade secrets when they sync to Exchange and executives' personal info and so on. It's all very fascinating (l0l) if you think about it.
[Fascinate Android Development] s44:
Stray question... I should probably just look at the repo, but does the color driver fix and all that include the Voodoo Sharpness mod?
[Fascinate Android Development] laureanop:
No need really. The app Vm heap tool will do it for you, if you don't wanna go into the build.prop

PWGB,TKSGB10-12, adren shot xix, honeycomb2.03, ec09 radio.
[Fascinate Android Development] comradesven:
If you mean mDNIe values and such, no. I tried some and didn't like the colors and the video output. It's on my list.
[Fascinate Android Development] ssewk2x:
Well, shoot. Porting the audio driver over to the aosp kernel I'm using wasn't as easy as I'd hoped :(

I'm beginning to wonder if there's some horsecrap going on in the framework that's causing incompatibilities somewhere. I made one call and heard the audio well enough, but subsequent calls were dead silent - no audio at all.

Oh well .. back to the drawing board.
[Fascinate Android Development] djblu:
Verizon Access Point Tracking question

This was asked way back in the first couple pages of the thread, but the answer wasn't exactly clear. Reason I bring it up is because today I ran into the problem with trying to use the AP software from the PWGB Rom. Everything connected but all redirected to VZW hot spot subscription page.

Is their ability to track that embedded in the ROM, or in the Kernel? and if it's in the kernel, can we ditch that? If it's something else all together, would someone be interested in coaching me on how to locate, identify, and rectify that situation, and return that resolution to the devs here in for future use?

Thanks
[Fascinate Android Development] AtropineNa:
10/12 kernel = speakerphone fix?

Edit, no speakerphone fix, but volumes are better yay! thanks!
[Fascinate Android Development] SotYPL:
Just installed latest version on PWGB rom and everything beside incall volume is fine. Incall is way too loud. Even at lowest level my ear is bleeding and other person has echo. Is there a way to make it lower like in Glitch kernel scripts?
[Fascinate Android Development] s44:
Call volume IS too loud, but whatever you tweaked on the performance side since 10/06 has really gotten rid of the irritating (and previously unfixable, no matter the governor/OC/scheduler) sporadic lag -- particularly in Dolphin HD -- that had me considering going back to EB01. Great work!
[Fascinate Android Development] thedoman:
Had fluctuation of screen brightness on the latest tks and it went away when I switched to a different kernel. Any thoughts? Any one else experience this?
[Fascinate Android Development] kwinders:
There is a guide in the general section, if I find it then I'll put up a link.

http://xdaforums.com/showthread.php?t=792585

Check the last couple posts, will tell you how to change from pda to modem mode on the usb when you connect to pc.

PM me if you have questions about it so this thread doesn't get cluttered or highjacked.
[Fascinate Android Development] icemanwbs:
Just flashed the 1012. So far so good. GREAT JOB!
[Fascinate Android Development] skiddingus:
I've been running this all day and it works flawlessly! The volume is still just a little on the loud side. I am at the minimum on both speakerphone and earpiece and it is still pushing it a little. One more touch down would be perfect. Everything runs really smooth though!
[Fascinate Android Development] droidstyle:
I disabled lag fix on this kernal and everything seems to run smoother...especially boat browser. Anybody else notice this or maybe its just me? I got the idea in another thread post from skrazz
[Fascinate Android Development] AtropineNa:
Trying Autokiller Memory Optimizer from this post http://xdaforums.com/showpost.php?p=18408869&postcount=1106 to reduce the lag

Literally just installed it hope it works...