yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] *Luke*:
@ Sixstring

This is a copy of a post I made back in July on the v11 release:

For the life of me, I haven't been able to overclock past 1300 on any of the 3 kernels (not that it needs it, but its like having a corvette and not being able to put the gas to the floor). I'm using voltage control, on the latest CM7, and have tried overvolting, undervolting, and numerous combinations of schedulers and governors to no avail. It reboots on me every time I try to go 1400 or over. I know the phone is capable of higher as I was able to achieve 1500 rock-solid on previous OTB kernels running evil fascination. I've used the kernel cleaning script and everything, but I can't figure out for the life of me what I might be missing, and why I can't get it over 1300... Any suggestions would be appreciated =)

Glitch had replied that my phone was probably far from most and may require some special leakages. Please don't take this as me asking for anything at all, Im just curious if that is something that may still be looked at at some point? Id be happy to test for you if my phone is in fact unique, and some new leakages may be on the table in the future =)
[Fascinate Android Development] Eris _2.1_2010:
Ok I'm on XDA app and there's no way that I know of to search within the thread. And in the browser I click on search thread and the box disappears.

Sent from my Glitched MIUI Fascinate
[Fascinate Android Development] calebv2:
There is a very easy way to search on the xda app but here

- SRB multipliers:

Red ="3415521600"

Green ="3609817920"

Blue ="3773435840"

- Screen v1 gamma hack:

-37 red

-33 green

-36 blue

Give me at least one thanks for being nice
[Fascinate Android Development] Eris _2.1_2010:
What's the way you know, if it's thru the more option that thing is worthless.

Sent from my Glitched MIUI Fascinate
[Fascinate Android Development] calebv2:
Yeah it is worthless most of the time I find my answer 50 percent of the time with it ill agree with you there. I thought you did not know where the search was.
[Fascinate Android Development] iofthestorm:
No, this is what I tried to say in another post I think. On the international sgs it's two different types of memory, but on the Fascinate it's the same so it doesn't matter. Or at least that's what jt told me. Given that, there's no reason to limit the amount of app data space that you have. It's not even that hard to fill it up, apps like Opera Mobile store shared libraries there for some reason, some games store big files there. I can probably go through my apps and pick maybe 15 or 20 that combined will fill up your /datadata partition. It's a very specific problem, but it's a pain in the ass to have to keep clearing it when you start getting everything force closing. I just got fed up with it.
[Fascinate Android Development] rmtobler:
ohhhh that's what happened to my phone today...
[Fascinate Android Development] Eris _2.1_2010:
I'm thinking about asking them to update the app so we can search within threads and to improve the search feature.

Sent from my Glitched MIUI Fascinate
[Fascinate Android Development] nklenchik:
I tried changing the in call volume with the root explorer method and couldn't figure it out.

Has anyone fixed theirs yet?
[Fascinate Android Development] sixstringsg:
Well what issue did you run into?
[Fascinate Android Development] wessiide:
Have you guys considered merging enyo's GPS fixes with this kernel? He said he would post the changes to github. Be great to have fast locking GPS again.
[Fascinate Android Development] PhoenixPath:
As a workaround, I have been using volume+ from the market. Pushed the speaker up to +8 with eq settings set to 'good quality'. Seems to work pretty well.
[Fascinate Android Development] ssewk2x:
As soon as I can see what he did, I'll check it out.
[Fascinate Android Development] scarmon25:
Thanks. This actually worked really well for me. Had to buy pro to get the + 8 but it was like two bucks so not a big deal.
[Fascinate Android Development] CHANGiism:
I can only imagine it to be no more than just a modified gps.conf. This isn't a kernel issue. Enyo himself said he pulled it from Sensation and modified it. To verify this, flash Enyo's rom, examine the gps performance, and flash Glitch kernel. I doubt you will see a performance difference.
[Fascinate Android Development] scarmon25:
Yeah. There is a gps fix somewhere. I can't remember where but all it is a gps.conf and a secgps.conf file. That's it. And it improves gps dramatically. If I can find it ill point ya to it.
[Fascinate Android Development] CHANGiism:
Thanks, I was also having a hard time hearing my ringtone and alarm. It would be great if ssewk2x or sixstringsg can expand upon what they did with the in-call volume and apply it to media playback / incoming call ringtone. :)
[Fascinate Android Development] sixstringsg:
His rom actually has our kernel in it, just modified.
[Fascinate Android Development] CHANGiism:
Ah, just saw Enyo's post about him modifying something in the source for his gps tweak.
[Fascinate Android Development] ssewk2x:
Yeah, that would be nice. Unfortunately, it just doesn't work like that. The way the hardware works is there is an audio chip that handles all the incoming audio from different sources (calls, media, fm radio, etc.) and routes outgoing audio to different destinations (earpiece, BT, speaker, headphones, etc.). Depending on how it's wired, some amplification can take place at the input and/or output phase.

For the call audio fix, I discovered (to my horror) that there was zero amplification taking place at the INPUT stage. So, no matter how high I cranked up the output amplification (which is the same setting that's controlled by adjusting the volume the way you all are used to, btw), it reached a point where it just couldn't get any louder. So the fix for that was to set the INPUT amplification to something other than 0. This is the value that the 90call_vol script modifies.

So, you can see how that same fix does not apply to things like media (ringtones, music player, etc.) since those come from a completely different source and are routed through different hardware. Further, as far as I can tell, all the amplifications for those signals are already cranked up as far as they can go without resulting in god-awful distortion and the (very very slight) possibility of hardware and/or hearing damage.

I suppose at some point, I could look into that and try to expose a similar interface like I did with the call volume boost, but it would take a while for me to reverse-engineer those audio paths .. I'd basically be starting over from scratch, not just taking what I did for call audio and applying it elsewhere. The underlying implementation would end up being completely different.

I hope that makes some sense. I'm going on one cup of coffee today.

As far as media playback and incoming call ringtone, it's been my experience that different media files (which, after all, is what ringtones are) also have their own unique volumes. For example, my 320kbps recording of "Through the Fire and Flames" (be jealous) is a LOT louder than my ???kbps ringtone of GlaDOS informing me of an incoming call, followed by death. The enterprising young hacker would be able to edit both of these files using, say, Audacity (google it), and modify their unique volume properties in order to suit said hacker's preferences .. I haven't yet because I'm old and lazy.
[Fascinate Android Development] PhoenixPath:
Not sure if you're already aware or not:

Any of the CM-based roms, side-by-side with a stock phone (same make/model) will be significantly quieter. I am lucky enough to have 3 Verizon Fascinates, one of which is stock, one switches between stock and CM-based roms (testing), and the other is basically CM-based only.

The Stock phone is *incredibly* loud (ringtones/media) compared to either of the other phones on CM-based roms, and the one that switches is also much louder on stock than on cm-based. I have no idea what's causing it, or if it's a kernel or rom issue, but it is definitely there and the "default" setting for CM-based is in *zero* danger of damaging hardware at this point. ;) (Note that the one that switches has music on it and that music, which doesn't get re-encoded between stock/CM is still much louder on stock)

Not knocking anyone or anything, just trying to explain what we're seeing here as best I can so there is no (less?) confusion. :D

As of now, it seems completely independent of any kernel or rom built from CM7 for MTD. It would be so much easier if there was one rom or kernel it amazingly worked with...but sadly, such does not seem to be the case.

This has not been a problem for many of us over the course of roms/kernels because there have always been much bigger fish to fry, so to say. You guys have done such an amazing job that this niggling little issue is now slowly rising to the top of some folks lists. Not sure if there is anything that can really be done, but there it is.

Hope it helps...someone.
[Fascinate Android Development] jbr05ki:
Question:

Is this kernel the same as the one @ rootzwiki?
[Fascinate Android Development] shag_on_e:
I believe you can still get the volume + app on his website for free. I got one of the first versions a while back and just updated like a week ago. This app definitely is more than enough to compensate for lack of volume in our loved cm roms. This latest Glitch is just amazing, by the way. Can't say thanks enough.

~~~~There is no spoon~~~~
[Fascinate Android Development] ssewk2x:
Ok, that's good to know, and I hit the thanks button for ya :)

With all that said, the audio driver code seems to have been partially re-written from Froyo to the current GB stuff. It looks like someone started to re-write it into something nicer and more structured, then got laid off right in the middle of it. The end result, unfortunately, is that the code is a clusterf*ck.

As far as I know, I'm the only one that's been working on volume issues, so it's entirely plausible that I've missed something since I was concentrating on call audio. I'll get back into it soon and pay attention to the other stuff.

I do stand by my remark that it will take a while, though, since I will still have to learn how those audio subsystems work and are routed and where/if I can bump up some amplification. And I have to learn all that just from looking at the code and some educated trial-and-error - I don't have manuals or schematics for anything :(
[Fascinate Android Development] CHANGiism:
Thanks for the explanations and I would not put more effort than what is worth. Volume+ works great and fiddling around with DSPManager works somewhat also.
[Fascinate Android Development] koszor:
I flashed v11 medium leakage to my fascinate running the latest version of miui.

I like it alot, and I'm still experimenting with UV settings but as of now I'm experiencing great performance and battery life.

I would provide constructive feedback however I have none as of now, great kernel.
[Fascinate Android Development] ssewk2x:
Just so you know, if you find any issues, our first response is probably going to be "flash the V12 beta." In fact, you probably want to do that anyway .. it's a lot nicer in pretty much everyone's opinion. :)
[Fascinate Android Development] scarmon25:
Absolutely. Much much better
[Fascinate Android Development] sixstringsg:
Yes. I actually update here more consistently than there though.
[Fascinate Android Development] jbr05ki:
That's what I thought. Thanks! This kernel flies with TSM Pool Party Rom.
[Fascinate Android Development] PhoenixPath:
lmfao... Sounds about right.

Not an issue, just wanted to hopefully provide some insight, however marginal. As has been stated here by many, we already can't thank you enough...how do you expect us ever to catch up if you don't take a break or slow things down a bit now and then. ;)

For everyone else:Volume+ website (Free download of $3 market version...but donate anyway!) --wish I'd reserved a post under the OP for this stuff...
[Fascinate Android Development] ssewk2x:
Oddly enough, I just found 2 lines of code in the driver that effectively lower the volumes in question by 3db or so. That might be all there is to it. I'll find out soon.

Edit: sadly, I left my build machine at home turned off. So I won't find out for a while yet.
[Fascinate Android Development] mtw4991:
Updated last night to CM7 #61 and Glitch v12-HL with VC app. Got everything set up and working blazing fast. Pushed OC to 1500mhz to run quadrant and got 3400-3600, then backed it down to 1200mhz. VERY NICE WORK guys and thanks for the help and pointers along the way. Nice to see a thread stay on topic for the most part.. getting rarer these days, lol.

I do have a question related to BLN (voted in the poll just now) and Blinky. I downloaded both and left the settings on both at their defaults. However, the lights just seem to stay on whenever the phone is awake and shut off when it goes to sleep. I sent a couple of test SMS's, etc but nothing happens. I tried fix_permissions, reboot, etc but nothing. It seems that this may be a common issue? (hence the poll) Anything I can do?
[Fascinate Android Development] ssewk2x:
I think the default behavior is to disable BLN for both apps. That said, you really only need one. I'm not even sure the two won't fight and cause problems if they're installed together. So I would say pick one (blinky *cough*) and configure it the way you want. It should work just fine then.
[Fascinate Android Development] mtw4991:
Thanks, that makes sense. The way I was reading it (at 1am) was I needed both, but questioned probably conflicts as well. So, I'll go with Blinky, disable BLN on it(?) and then configure it, right?
[Fascinate Android Development] ssewk2x:
Well, if you disable it, it won't work. But yeah, go with blinky and set it up how you want it.
[Fascinate Android Development] nklenchik:
None since I've been using v12...didn't even realize until yesterday lol
[Fascinate Android Development] mtw4991:
Gotcha ssewk, thanks again.
[Fascinate Android Development] Azuma73:
Maybe I'm just dumb, but what is BLN and Blinky?

Go ahead and give me a hard time if you feel you need to!!:eek:
[Fascinate Android Development] scarmon25:
BLN is back light notification. What it does is turn the backlight for the softkeys on when you get a text or message. The BLN and Blinky application is what you use to control it.
[Fascinate Android Development] Jazz848:
Got audio hub schematic and full specs direct from wolfson a while back (bit of an audio junkie). Been skimming for fun, but will see if I can find anything. Happy to zip 'n send if you want. Should also be at wolfson, checking now and will post link...

UPDATE: Ye olde linkage: http://www.wolfsonmicro.com/products/audio_hubs/WM8994/

Frickin' BEAST of a hub. Power amp looks exclusive to headphone out, judging by the charge pump connection. Looks like there's still the pre-DAC DSP suite to work with though. If I'm reading correctly, you may be able to loop via the I2S/PCM section; each one looks to have a bi-directional connection to the DSP. No idea how to do that code-wise, but it looks possible (if messy) hardware-wise...

Git for ASoC: http://opensource.wolfsonmicro.com/...2.6-asoc.git;a=tree;f=sound/soc/codecs;hb=dev

2.6, I know.... still digging...
[Fascinate Android Development] Bubbadogg14:
just checking back in to let you guys (six and ssewk) know my sd card issue turns out to have been unrelated to your kernel. Apparently with OMFGB 9/22 when taking a nandroid backup something happens to your card (with some ppl not sure if it happens to everyone) and forces you to reformat giving you a damaged sd card error. This is what happened to me as I made a backup before I flashed the new glitch kernel which is why it seemed to be your kernel that caused the problem. Also I never did a nandroid backup on jts kernel so I didnt have the problem then. I just thought something with my card didnt like the new kernel until other people on rootzwiki started to have the same problem with OMFGB 9/22. I can confirm it wasnt your kernel because I ran espresso rom with your kernel yesterday with no issues. Thanks for the hardwork you two keep em coming!
[Fascinate Android Development] ssewk2x:
I've seen the stuff you linked, but thanks. What I really need is the datasheet, which they say "please contact us to request." I emailed them a while ago, no response. If you have that, then for sure hook me up!

And for a schematic, I'd need to see how Sammy wired the hub into the phone...
[Fascinate Android Development] sixstringsg:
Thank you for letting us know!
[Fascinate Android Development] Jazz848:
Working on both. May need time, but confident I can obtain...

Edit: I wonder if Supercurio's got this stuff handy.
[Fascinate Android Development] neh4pres:
I'm suddenly having a issue receiving calls. Running glitch hl 9/22 and miui 9/16. I have rebooted, pulled battery. I can make calls fine. But having people call me sitting right next to me and my phone never rings. It does ring on their end until voicemail picks up. I don't know what would cause this (kernel,rom, radio) but the support and knowledge in the glitch thread is phenomenal and I would just like some input from the people here.

Thanks.

Edit: just got one to go through, but made another after and it did not ring. I am using a Wilson (whole house) cell signal booster. It takes my 1 or no bar of signal to 2-4 bars with 3g. My mothers cheap phone gets calls every time I call it so I don't think signal is the issue. I just did the star 228 and it was successful,I then rebooted. the receiving call issue still persists however.

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] 123SIT:
Regarding the data/data partition filling up how can this be rectified?

Sent from my CM7 Mesmerize
[Fascinate Android Development] sageDieu:
I'd bet he does... if anybody has it it would be him.

Sent from my MIUI SCH-i500
[Fascinate Android Development] Jazz848:
Reading through the original i9000 threads, sounds like it may be "privileged info" territory, so he might not be able to share certain things to begin with. Will still ask, but don't wanna cause no trouble. ;)
[Fascinate Android Development] iofthestorm:
Sixstringsg, would you mind putting up instructions on how to set up a build environment for glitch? I tried to build a while back but it was quite different from other android things I've built in the past and ssewk2x said it was hard for him to remember what he had to do to get it building. I probably can't contribute much for lack of time but I just would like to have the ability. Thanks for the best kernel that's graced my phone!
[Fascinate Android Development] tripacer99:
Still experimenting, just realized I could push -200 @ 1.7 GHz and no crashes. Truly awesome stuff
[Fascinate Android Development] kallell:
Six / ssew,

Everything with this new build seems to be 100x better than the previous. However, it seems that occasionally i'll get big delays / lag when trying to exit an app. Furthermore, there still is odd occurances, where i'll be in some app (IE: droidwords) and Randomly ill see system messages (Little gray or black popup box at the bottom) come up saying something with my alarm settings, or whatever else 5-10 minutes after i've done something with them. Also, along the same lines, the volume popup will randomly show up in apps, minutes after I've adjusted it. I'm not sure how well else i can articulate it. It is almost like all that data is being "cached" in a sense then just spews out once the processor load dies down a little.

MIUI 9/16 with glitch 9/22.

Let me know if you'd like any more details.
[Fascinate Android Development] Jeff194:
One thing I have noticed is whenever I use the Glitch kernel,I get a slight buzzing sound in the background when I play back video that I have recorded using the camera . It happened when I used CM7 nightlies,and the first Expresso release,which used Glitch. When I use JT's kernel it doesn't happen.

Currently running Expresso 18
[Fascinate Android Development] jbr05ki:
Didn't notice this til you pointed it out. Thanks brro
[Fascinate Android Development] sixstringsg:
Which version of JT's kernel did you not notice it on?
[Fascinate Android Development] tripacer99:
I can also confirm that this happens on the latest glitch kernel. Running MIUI 1.9.16.
[Fascinate Android Development] PhoenixPath:
BLN. Turns it off. ;-)
[Fascinate Android Development] jbr05ki:
I turned BLN off and I still get a hum after recording video and playing it back.
[Fascinate Android Development] Jeff194:
The 9/19 version. Which was included in the expresso build 18.
[Fascinate Android Development] sixstringsg:
There is nothing I can do about it at this point. It is a little thing, I don't have a fascinate, and I can't run the rom that you are experiencing it on.
[Fascinate Android Development] Jeff194:
No problem,just an fyi. It did it on the CM7 nightlies as well like I said.

Thanks for all your hard work, and time invested in this kernel.
[Fascinate Android Development] Coolsaber57:
I've been using the LL kernel @ 1200mhz, -50mv at each step, CM7 Nightly 55.

I've been experiencing pretty consistent reboots after about a minute of a phone call.

I know there are several factors that could contribute to this (undervolt, leakage, overclock, nightly instability, etc).

I just wanted to report it in case there were others with the same issue.
[Fascinate Android Development] Glocjt:
Have you tried your luck with either the ML or HL kernels? I started off with HL and have gotten pretty solid UVs.
[Fascinate Android Development] thachizzle:
I'm on ML 9.22 v12beta kernel and is there anyway to turn off the bottom backlights? They're way too ****ing bright and they never turn off.
[Fascinate Android Development] fstbusa:
Read back a few pages... I asked that same question. You have to edit the profiles to turn off BLN.
[Fascinate Android Development] Coolsaber57:
I installed the ML yesterday to test it out. It's just odd that up until this point I ran the LL with those settings and had absolutely no problems.

I'll report back if I still find that I'm getting reboots.
[Fascinate Android Development] hejay:
Nothing you can do if you're on MIUI.
[Fascinate Android Development] sixstringsg:
That kind of thing changes on a regular basis between kernels.
[Fascinate Android Development] sixstringsg:
Just a heads up to everyone, we do have a fix for media/ringtone volumes coming. It is merged in, we are just testing it, refining things, then sending it out. It won't be today or tomorrow, so as usual don't ask for ETA's, I might eventually give one.
[Fascinate Android Development] tripacer99:
Will this new build include soft-key light timeouts? Seems that it is winning/won the poll you put in the thread.
[Fascinate Android Development] ssewk2x:
Did he say it would?

That particular feature may not even be a kernel change. Before, it was done via a services.jar edit.
[Fascinate Android Development] schu9120:
Who is going to be Six's 1000th "Thanks"?
[Fascinate Android Development] scarmon25:
I just thanked him. Did that get it.

Edit. Just thanked the last few Pages.
[Fascinate Android Development] shag_on_e:
Nevermind this dude please. I think some folks are getting a little spoiled here. I believe I speak for many of us saying, just do your thing. I honestly couldn't be happier. As long as y'all stick with us at all, life is good. My junk is so smooth, oc'd and uv'd, battery is nice, speed is crazy, life is good. Whatever y'all add...hell yeah. Thanks fellas, y'all are the shiznit.

~~~~There is no spoon~~~~
[Fascinate Android Development] ssewk2x:
It's ok. Thing is, I like new features as much as the next guy. So you can be damn sure that when we/I add one, one or the other of us will trumpet it from the rooftops. So, if we aren't trumpeting about your pet feature, it's safe to assume that it's not included yet.
[Fascinate Android Development] sixstringsg:
Does everybody here have BLN that works well? People in the captivate forum are having issues, so I'm seeing if it's just them with them, or everyone. If it's everyone, I'll probably look into doing LED notifications from upstream.