yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] teezle:
While I did not call anyone any names. Your arrogance truly shows. I am not putting anoyne down. If you feel defensive, go right ahead and make yourself feel better. Everyone else may kiss your ass, but you not getting it from me.
[Fascinate Android Development] jt1134:
Blahahaha ya done got trolled and it was too easy xD
[Fascinate Android Development] teezle:
No you did, I just gave you a thanks.......I'll be the bigger man in this.
[Fascinate Android Development] jt1134:
Ah....so big meaning complaining with an annoying sense of entitlement, contributing ZERO, and clicking the thanks button? Updating my dictionary now ;)
[Fascinate Android Development] teezle:
make sure you add "couth"" to the dictionary.
[Fascinate Android Development] teezle:
Thanks a bunch for the update.
[Fascinate Android Development] sageDieu:
Efpophis, not sure if you're still having trouble but if you need any help with git stuff or whatever I'd be glad to assist.
[Fascinate Android Development] sixstringsg:
We're just having a lot of issues merging upstream stuff, there are a lot of merge errors and such.
[Fascinate Android Development] ssewk2x:
Yeah .. What he said. :) Thanks.
[Fascinate Android Development] PhoenixPath:
Not to be a complete downer to all the Drama Queens in here, but the volume issue isn't much of an issue if you stop to think about it for two seconds.

1. That blasting volume? That's the top.

2. That "can't hear it" after one click down? That's one click down from where you had it set *prior* to the blasting. Do it enough times, and you're not going to be able to hear the caller.

3. Solution? Call someone. Set it just right. Next time, hit down once and up once prior to bringing it to your ear.

4. .....?

5. Profit!!!

Also note: SoD requires a battery-pull or hard-reset to get out of. This...is not that. This is a sensor issue (which I believe your good buddy jt *fixed* in his last kernel release...wasn't that *nice* of him???)

I now return you to your usual XDA drama-fest.
[Fascinate Android Development] teezle:
1-3 does not work. Two of us here at work tried every which way. No setting prior or after made any difference.

Also note: You need to read my description of the problem about after being on a call:

"When I mean not waking up after a call, is you can't even see the screen to hit "end". You have to hit volume up or down to wake the screen to see it."
[Fascinate Android Development] scarmon25:
It works for me. What. I do is after each call set the volume to Max. Then when I get a call I hit volume down once. Works perfect. Now I will say that everyone's results may vary. What works for me may not work for you.
[Fascinate Android Development] akellar:
The phone is "awake", your screen is off. Turn the screen on. Is it really that big of a deal to hit an extra button? It's because of the sensors, which JT has fixed and are in his kernel and will be in this one once they can get it merged. You made your point (useless as it was) now move on.
[Fascinate Android Development] teezle:
Actually you have to hit more than one button. Once or twice to the volume to "see the screen after the call". And once to unlock the phone to verify if the call got hung up or not. Add another button push to end the call if it did not hang up. So your info was useless. Unless you were just trying to put your two cents which is what I think you were trying to do.
[Fascinate Android Development] Azuma73:
Just noticed Glitch kernel is now available through Rom Manager! That's pretty cool man.

Are they the latest versions and do they work well downloading through RM?
[Fascinate Android Development] sixstringsg:
They are not the latest versions yet. Will be soon.
[Fascinate Android Development] CHANGiism:
I really appreciate your work sixstrings and ssewk2x! Got an email from Tk that he will start working on things soon so things will pick up really quick in few days and I'm sure what you guys have done will accelerate things up.

I am on CM7 Build #56 and all the random lags are gone, and it runs as smooth as how it used to be! I have noticed that the touchkey gets stuck sometimes and I'm wondering if you can pull what pawitp did to fix the cypress mutex issue. His github is www.github.com/pawitp. Also, he has many other small things like WM8994 extesion and whatnot. I believe he managed to tweak the Voodoo color so that it plays nice with other Aries drivers, and not specific to Nexus S. Sorry to give a request when you guys are doing such a nice job, call me greedy :D Thank you again!
[Fascinate Android Development] Glocjt:
I believe it's 'cause of CM7 (I think the fix came in around nightly 55 or 56), but I haven't been keeping particularly close tabs on the changelogs...so don't quote me on it. ;)
[Fascinate Android Development] djk21108:
The change log says that 9/23 is the latest version, but the download link in the OP reads 9/22.

Are they one in the same? Thanks!
[Fascinate Android Development] ssewk2x:
They should be one and the same. I bet the 9/23 one was a typo.

---------- Post added at 01:44 PM ---------- Previous post was at 01:43 PM ----------

It was both, really. It required a kernel hack and a slight mod to the torch.apk file as far as I can tell. JT did all that, tho, so I'm just giving an educated guess.
[Fascinate Android Development] sixstringsg:
They are the same one. I was uploading and updating threads after midnight, but the builds were from the 22nd. Plus some kernels (for other devices) weren't done building til the 23rd. Sorry about the confusion.
[Fascinate Android Development] sixstringsg:
We'll get to that later. One of those was what was causing all the issues with the lag and such, so we avoided them. As far as voodoo sound, WM8994 extesion, we use supercurio's code, not CMSGS. And same with voodoo color.
[Fascinate Android Development] CHANGiism:
Ah, thanks for the explanation. It was a low priority issue for me anyways, and the touchkey freeze thing is there even for the stock kernel. Keep up the good work guys!
[Fascinate Android Development] sixstringsg:
I know, I merged the touchkey freeze thing already, but we reverted it partially on accident in the latest builds. It'll get done. We mostly put these out because they are stable, and allow people to use the latest nightly. They are by no means perfect, that's why they are still labeled V12 beta.
[Fascinate Android Development] djk21108:
So what does 9/22 version offer over 9/16? The changelog seems to be a comprehensive list of v12 from v11.

Thanks for the work ;)
[Fascinate Android Development] sixstringsg:
It's completely redone since 9/16. Therefore a completely new changelog. All the features of 9/16, none of the annoying bugs and lag.
[Fascinate Android Development] ssewk2x:
Edit: What six said.
[Fascinate Android Development] djk21108:
Sounds good to me!
[Fascinate Android Development] akellar:
I disagree, seems pretty perfect to me! Zero lag issues, crazy good stability even at major UV, and BLN works beautifully again. You are amazing :D
[Fascinate Android Development] djk21108:
Well: I'm looking for a bit of guidance on governor and schedulers.

Right now I'm on deadline and smartass and don't have it configured to conservative when the phone is asleep.

What do you all use six and ssewk?
[Fascinate Android Development] jbr05ki:
Phone's been snappy with this kernel! The only problem I get is random reboots. Using HL with TSM Pool Party.

Before the update i would get lag and a lot of reboots. Anyone else have issues with TSM Pool Party?
[Fascinate Android Development] tripacer99:
High leakage, normal voltage levels. Cfq/smartass. I locked it into state after slowly moving the min. slider all the way up to 1700.
[Fascinate Android Development] sixstringsg:
The defaults have been tested and tweaked extensively. Deadline and Ondemand, with conservative when screen off.
[Fascinate Android Development] Jazz848:
Okay, my dock bar randomly disappeared, preventing me from opening the app drawer. Entering and exiting the settings menu restored it, didn't need a full launcher restart. Only happened once, so I'm writing it off as possible OC/UV/leakage wonkiness unless I can duplicate it on stock clocks and voltage.

Just putting it out there for now...
[Fascinate Android Development] ssewk2x:
I've had good performance and battery life balance with the following on HL:

cfq / conservative, conservative while sleeping

200 - 1400MHz, uv = -50 at each step

Fiddle around tho and find what makes you happy. That's why it's set up so you can control it yourself :)
[Fascinate Android Development] scarmon25:
CFQ-Ondemand here. 1.2 @ -50 all the way down. Runs like a dream

Edit. Powersave when screen is off
[Fascinate Android Development] ssewk2x:
I think I can do that touch-key freeze thing in like 3 lines of code .. I'm not overly thrilled with how pawit did it, lol. Want me to give it a shot?
[Fascinate Android Development] sixstringsg:
Just a heads up, conservative is probably a better idea. Powersave is inefficient, because no matter the load, it runs at 100mhz, therefore taking more time to get things done. Conservative will ramp up, just slowly.
[Fascinate Android Development] akellar:
Since we're sharing -

ML; cfq - conservative; screenstate off (already using conservative so don't see a need)

Step - UV

1200 - 75

1000 - 75

800 - 100

400 - 125

200 - 150

100 - 200
[Fascinate Android Development] ssewk2x:
Actually, give it a try. When the screen shuts off, the screenstate scaling thing modifies the conservative settings to make it *REALLY* conservative. So it will be even more battery friendly with the screen off than your standard conservative settings.

:)
[Fascinate Android Development] akellar:
Ok good to know. I may give it a try then. I was partially basing it off the comments in the script as well that stated better battery was achieved without this. Old comments?
[Fascinate Android Development] ssewk2x:
Yes, old comments. I should probably clean those up at some point.
[Fascinate Android Development] Bubbadogg14:
Not trying to be a **** but there is a thread in q & a section dedicated to ppl sharing their glitch settings. Just giving some guidance don't think I'm being a jerk
[Fascinate Android Development] scarmon25:
I figured that would be a good thing with the screen off. Maybe I'm not understanding the screenstate scaling. I thought when its off it switches to whatever you have set then when it comes on it switches to the other. So like when its off its on powersave and when on it would be on ondemand. I knew that powersave kept it at 100 but didn't think it would cause any issues. I can switch it to conservative no prob just wanna make sure I undertsand it right so I don't cause myself problems. ;)
[Fascinate Android Development] akellar:
You are right but keep in mind that just because the screen is off doesn't mean it's not processing anything. So with powersave on it would be processing everything at the lowest setting which could be extremely inefficient.
[Fascinate Android Development] scarmon25:
Gotcha. Didn't even think about that. Switched it to conservative. Gonna see how that does. Thanks for the info.
[Fascinate Android Development] chrisexv6:
Question - are the leakages still "reversed"?

i.e. high leakage is actually the tighter/cooler running/less tolerant of out of spec hardware?
[Fascinate Android Development] ssewk2x:
We didn't mess with leakages at all. So the are whatever they were before.
[Fascinate Android Development] djk21108:
Hey all. I set my OC to 1400 mhz, saved profile and then saved boot settings.

I restarted my phone and checked CPU spy and it's giving me 1000 mhz max. Does this mean saving boot settings with voltage control is not effective?
[Fascinate Android Development] ssewk2x:
It's working fine for me, tho I've never messed with profiles. Try resetting the timers in CPU spy, then run a benchmark or stability test or something. That should kick it up to 1400 so you can see it.
[Fascinate Android Development] chrisexv6:
One more question - I notice the newest version has BLN ported in....do we need an app for that to work? I didnt get any notifications even though I had an email.

Running on VGB7 if that makes any difference.
[Fascinate Android Development] sageDieu:
Burrito manager is better.

Sent from my MIUI SCH-i500
[Fascinate Android Development] PhoenixPath:
I'd insert the "what is this... I don't even" image here, but I don't even...what is this?

Some inside joke?
[Fascinate Android Development] sixstringsg:
Your example is never how it was. High leakage is samsung default, which requires more volts because it leaks more, hence high leakage. With more volts, comes more heat. The lower leakage chips are actually higher quality silicone, just harder to produce.
[Fascinate Android Development] ssewk2x:
Yeah, the new BLN requires an app to activate. Neldar's BLN control works, but for some reason my phone reboots when I install it. It doesn't seem to matter, but it does make me a little nervous. I've been using Blinky and I like it. No reboots on install with that one, and you can have your lights blink if you want.
[Fascinate Android Development] sixstringsg:
In the changelog is says to use BLN app or Blinky.

Edit: ninjad
[Fascinate Android Development] scarmon25:
I'm using BLN pro without issue.
[Fascinate Android Development] speedingcheetah:
AnTuTu

I know Voltage control and Quadrant is the standard apps around here to use to adjust/test stuff...but anyone try/recommend AnTuTu Benchmark and CPU Master...they seem to offer much more benchmarking stuff and the cpu master seem quite nice...just don't know if it is as good as old faithful Voltage Control and Quadrent...
[Fascinate Android Development] worshipNtribute:
is there any way to compare two kernels directly and accurately or do I have to run each for a couple of days and figure out what I like?

can't figure out if I want jt's 9/12 or this new glitch kernel on MIUI 1.9.16
[Fascinate Android Development] chrisexv6:
Didnt see it, still dont see it.

But it looks like its required anyway so Ill just install Blinky.
[Fascinate Android Development] sixstringsg:
My apologies, I make kernels for 5 devices. It's hard to maintain five threads. Plus the kernel that you are currently running, i don't even run myself since I have a captivate. It was mentioned for the past few pages though.
[Fascinate Android Development] sixstringsg:
Here's are the steps:

1) try Glitch

2) try JTs

3) find glitch is better and go back to Glitch :)
[Fascinate Android Development] neh4pres:
antutu its deff better than quadrant

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] chrisexv6:
Wasnt trying to come off like a do shh. If I could have edited the changelog for you, i would have.

I did notice that Blinky was being talked about, but wasnt sure if it was for the 9/22 (9/23?) build or not.

MY apologies as well.

---------- Post added at 03:57 PM ---------- Previous post was at 03:54 PM ----------

I always keep coming back to Glitch kernels.

Ive tried JTs and his stuff always works well, and without him who knows where our Fascinates would be (maybe in a trash bin somewhere!) but I love the OC/UV capabilities and the extra features in the Glitch kernels.

For me the bigger issue is what ROM I want to play with.
[Fascinate Android Development] Jazz848:
Well, I'm pretty sure neh4pres will vouch for it ;) My curiosity is officially piqued. Personally, though, I haven't trusted a benchmark program since the days of heating my room with an overclocked Prescott. They're often too formulaic to represent average error-free (or filled) daily use for true cross-setup comparative purposes.

That said, I still use them to compare various configs of individual systems. I'd love something more trust-worthy than the yo-yo scores of Quadrant.
[Fascinate Android Development] Jazz848:
OH NO YOU DI'NT!!!
[Fascinate Android Development] scarmon25:
I personally like voltage control better as its easy to use and works very well. As for benchmarking. I very rarely use on but when I do its linpack and antutu
[Fascinate Android Development] djk21108:
I took your suggestion and it doesn't seem to be working. Even when I save my boot settings at 1400, I have to re input them when I restart.

Anything else you could think of that's causing this?
[Fascinate Android Development] sixstringsg:
In all seriousness, jt is wonderful. If it weren't for him, your kernel wouldn't be where it is. Glitch has a lot of modifications on top of that for memory management, battery life, overclocking, et cetera. I wasn't trying to say his was bad, just his is stock.
[Fascinate Android Development] sixstringsg:
What rom are you on?
[Fascinate Android Development] worshipNtribute:
Thanks! I'll try yours out right now.

I couldn't figure out the exact difference in high, medium, low leakage, so I'm thinking about 1200 MHz - GPU@ 200 MHz - 1.350V / -50mV and low leakage. Basically trying to maximize battery life and not too worried about 'snappiness' as the phone is plenty snappy on MIUI.

Would you recommend anything different or does that sound good?
[Fascinate Android Development] speedingcheetah:
O yes ...the Prescott days...I had one of those in my dorm a few years ago...could cook Ramen on that thing...had a jet engine of a fan...could hear it out in the hall...

Anyway, back on topic, AnTuTu Benchmark seem more extensive than Quadrent standard...even test sd card speeds...as far as the CPU Master Free version...don't support UV..so useless to me...
[Fascinate Android Development] neh4pres:
low leakage is the hardest to run.. It is built for those lucky few who got a low leakage chip in their phone.. You need to tinker with all 3 to figure out what kind of chip you have

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] neh4pres:
why is pimp my CPU recommended for miui instead of voltage control? Also I remember a app that would let me pick and choose states. I think it was voltage control back on tw roms. Anyway was wondering if it would benefit being able to disable some middle states. I seem to be stable at high clocks, but when I try to run them naturally with a minimum of 100mhz my phone will lock up.. This seems to happen during a ramp up.

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] akellar:
You can pick and chose states with both voltage control and pmc?
[Fascinate Android Development] neh4pres:
I must be missing something then... I have set as max, and set as min.. Then I can choose voltages.. That is all.. I can't disable middle states

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] scarmon25:
If you hit the green dot on the voltage adjust it disabled that state. Turns red
[Fascinate Android Development] akellar:
Which app? On voltage control you can click the green/red circle next to the step to enable/disable it. Haven't ran PMC for a while so I don't remember its UI.

Edit: DAMN YOU SCARMON!!! :)
[Fascinate Android Development] neh4pres:
I'm using pimp my CPU, and always have on glitch because it is recommended for miui users. Not sure why.. Does anyone disable middle states? I have not seen anyone with a setup with states missing

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] akellar:
I don't know why PMC is recommended either. I'm using VC on MIUI just because that's what I was using on CM7 and I forgot about PMC when I switched. No issues so not sure why it matters but I'll leave that to the experts. As far as middle steps go, I figure I would rather it run at 800 than 1.2 if it doesn't need to so I leave everything alone.
[Fascinate Android Development] scarmon25:
Well I decided to try out PMC. I kinda like it better. Think I'm going to keep it. Its a little pricey. It does have a built if CPU stress test though which I like.
[Fascinate Android Development] djk21108:
I'm on the newest JT vanilla. (This was in reference to voltage settings not saving on boot)

I've also noticed that deep sleep is an unused cpu state in cpu spy. When I have OC set to 1400, all the states between 1400 and 1000 are PRACTICALLY unused. Like 7 seconds for 1200 mhz. I guess that's not a problem...unless you say that's a problem yeah?

Scratch that, deep sleep is working. 1200 and 1300 are getting next to no time. Should I turn em off?
[Fascinate Android Development] neh4pres:
Well.. I'll try vc then.. was gonna disable some steps on the way up to

1.7.. Like that odd 1.44.. And maybe a few others

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] exzacklyright:
Tried flashing the latest version but phone wouldn't boot. Any ideas? It just sat on cm7 boot animation for 15 minutes. This is with the high leak
[Fascinate Android Development] scarmon25:
Question. Since PMC has a built in stress test I decided to go through the leakages again and see which ones did the best. As expected LL crapped out at 1300. But I was able to get both the ML and HL up to 1500 without freezing. Now I run mine constant at 1.2. So if they both seem to do OK then I guess I could go with either one, right? Or no?
[Fascinate Android Development] neh4pres:
Yes.. Or you could push both further either in under voltage or over clock and see which leakage is the fit for your phone

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] neh4pres:
Only the newest cm7 will work

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] sixstringsg:
See my notes at the end of the post.

I can't run that ROM until I get a vibrant, so I can't support it. Everything works as it is supposed to on the latest CM7 and MIUI, and they are what is supported. As far as CPU states, the higher ones won't get much time. Leave them enabled, so that it can go that high when it needs to.

1.44 was added for those people that can't run 1.5, but want more than 1.4. Also, see my general note at the end of the post.

Just work on UV. If you don't care about UV much, then run the ML version.

For everyone talking about states: You can't disable them on this kernel. It isn't fully implemented yet. It will look like it works, but nothing will actually happen. We haven't worked on it yet because we don't feel it is necessary. It doesn't save battery or improve stability, so it's not worth the time. Unless someone has a reason that we have missed. Pimp My CPU was originally reccommended for MIUI because a while back, Voltage Control didn't work for MIUI, just Pimp My CPU. It is now a moot point as both work, so I will update the OP. Although, if you ask questions about Pimp My CPU, I run Voltage Control, therefore I can't help.
[Fascinate Android Development] scarmon25:
Well since I only undervolt -50 and overclock to 1.2. I'm gonna stay on the ML. Seems to run really well. As for PMC. I just like the interface better. I never disable steps other than my Min/Max so that really doesn't apply to me

Thanks for all the info guys. Never to late to learn something new.
[Fascinate Android Development] exzacklyright:
what's the newest.. I thought I was on a new one...

I'm in a boot loop now :[
[Fascinate Android Development] neh4pres:
flash your rom again..

I think you will need to adb reboot recovery to do so

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] Jazz848:
No worries, I didn't assume any bad blood. Just a bad joke. This is my usual reception:
[Fascinate Android Development] wessiide:
Since this was built off jts latest kernel I assume it also suffers from the random keypad punches and keyboard pop ups? It is very sporatic and sometimes happens often but then disappears for a few days.
[Fascinate Android Development] sixstringsg:
It's not technically built off of jt's latest kernel. It has some of jt's fixes merged in, but is all in all not very similar to his. The code from his kernel is only fascinate specific stuff, mostly sensors and drivers. As far as your question, I have not heard complaints of that, but I can't confirm anything.