yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] ssewk2x:
It's not a script you run. You edit the boost and mic gain settings the way you want them, then you save the script file to /etc/init.d. If you don't know what all that entails, you're better off waiting for an app, honestly.
[Fascinate Android Development] fstbusa:
Typically both of these have worked for me and it's not a huge deal in my mind.....love this ROM/kernel combo.... Not going back!!
[Fascinate Android Development] PhoenixPath:
MIUI 1.9.X (anything above 1.8.26) with glitch 915: no sensors or torch... Jt's kernel is the same. Glitch 915 also giving long vibes and random reboots.

HL, ED05 modem, stock speeds/schedulers.

Not sure what help that will be. I can hit someone up on irc if ya let me know when.
[Fascinate Android Development] neh4pres:
Op only told where to place it.. My only knowledge of scripts so far was from v6 supercharger. I don't think using what I know and applying it was a bad idea.. I placed it where the op said, then ran script manager.. It was not until then that I had any hint that I was not doing it right. So I went back to root explorer and opened with a text reader.. It was not until then that I had a glimpse of the scripts instructions.. Sure i'm not as verse in things as a dev or someone with years of Linux experience. But I am able to learn and apply what I have learned in the past. I then also took a minute to try and understand what I was reading.. Which Is instructions guarded by the "#" symbol so the system don't read them followed by lines of code. At the ends of the coding they're is a =% (an equal sign followed by a value) for earpiece I set this between 0 and 3 which is 4 settings and the mic gain from 0 to 31 which is 32 settings.. And each has different modes for adjusting. Such as mic gain speaker mode, or mic gain earpiece.. Pretty sure I figured it out :) thanks for the help.. And you can have your facepalm back now. :p

Sent from a beautiful miui fascinate
[Fascinate Android Development] neh4pres:
I'm running newest miui. And glitch 9/15. My torch works perfect. And sensors have good reading.. However lots of people are having issues with games that use those sensors

Sent from a beautiful miui fascinate
[Fascinate Android Development] sixstringsg:
I'll add directions to the OP that are more detailed, you did it right though.
[Fascinate Android Development] neh4pres:
if you need help let me know. I know your piled with things to do

Thanks for everything that you do

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] sixstringsg:
If you would like to write it up, go for it. Shoot me a pm with it. I've honestly been painting all day, haven't done any kernel work other than maintaining the thread. Today was a break day.
[Fascinate Android Development] neh4pres:
Pm sent. Not showing in my sent folder however.

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] sixstringsg:
I got it, I'll update the OP soon, and the changelog.
[Fascinate Android Development] mesmerbelly:
Anyone have a copy of the 915 release

sent from my glitched cm7 mez with fixed audio
[Fascinate Android Development] neh4pres:
Just keep looking in the previous pages

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] scarmon25:
Go here. It has all the kernels I believe.

http://androtransfer.com/fascinate/
[Fascinate Android Development] davwman:
I read the opening post, but does this work with vanilla gingerbread and would it be worth it to use?
[Fascinate Android Development] scarmon25:
Yeah it should work fine with VGB. I personally think it is worth the time flashing it. ;)
[Fascinate Android Development] shag_on_e:
I live by this kernel, so I definitely think it's with it.

Sent telepathically.
[Fascinate Android Development] davwman:
the kernel that flashes with vgb is crazy fast so, I guess Ill nandroid and give it a go. thanks
[Fascinate Android Development] FettsVett:
A.) The OP is a bit unclear, sorry if I came off as a prick.

B.) The 'facepalm' comment was exasperation, not really directed at you, but at the inability of some people on this site to read and think before they ask a question. Obviously you can think, and you're learning how to read - so don't stop! :)

C.) Any time you have a script and you don't understand how it works, try opening it up and reading the comments. Most (In fact I don't think I've seen a shell script that wasn't) are commented.

D.) Any script that resides in the /etc/init.d directory is executed at boot in the order that it is numbered. (at least for android)

E.) Facepalm. :) Cheers, hope you continue to learn and contribute!
[Fascinate Android Development] sixstringsg:
OP updated, as well as the changelog. I'm aware neither are pretty, I'll fix that later. For now, it conveys the information needed.
[Fascinate Android Development] neh4pres:
Thanks man.. You just taught me something.. I did not know a reboot was needed. I was thinking that the phone.apk referenced the script when making a call. This explains why my called party didn't notice a difference in mic gain.. Now I wish I would have put that in the directions I typed up.

facepalm lol

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] sixstringsg:
I'll fix it the guide. Anything in init.d gets run at boot. You can also run it through script manager.
[Fascinate Android Development] davwman:
what settings do you guys find work best with the script?
[Fascinate Android Development] neh4pres:
Really, if you don't feel there is a issue with your call volume, or your other party hearing you, then you really don't need to change anything imho. I was gonna turn down mic gain in speaker mode because I get complaints about my other party hearing their own echo.

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] davwman:
sounds good thanks
[Fascinate Android Development] davwman:
this kernel with vanilla gb and adrenaline shot v6 and smartass is ridiculous!
[Fascinate Android Development] neh4pres:
I have yet to try adrenalin shot.. Maybe today is the day

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] pntballer505:
What exactly is Adrenalin shot, not a kernel. A mod or something?
[Fascinate Android Development] neh4pres:
Its a mod in the dev section.. I decided not to do it after reading mixed reviews, and the fact I already have a record phone oc at 1.7 ghz.. I just feel content.

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] pntballer505:
Okay, gotcha. Then I don't think i will either. Very content.
[Fascinate Android Development] neh4pres:
Here are the links......... Again...... They were on pg32

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] sixstringsg:
Directs neh4pres to the OP, where they are linked for all to see.
[Fascinate Android Development] neh4pres:
Yes.. But the dates are wrong and don't reflect 9/15... And now I am getting pm's asking if I could give them links to the 9/15 glitch kernels :/ ..

Edit.. ATM it seems the medium and low on the op seem to have broken. However all seem to be working in the quote.. Just trying to help.

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] sixstringsg:
Try again.
[Fascinate Android Development] neh4pres:
Working perfectly..

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] pntballer505:
Cool. Thanks for the work on the kernels. And taking over for glitch.

Besides BLN, what other things are to be worked on/fixed/added in for these

kernels? Just wondering.
[Fascinate Android Development] sixstringsg:
BLN should be working at the moment... We have a lot of cleanup to do, so that's a first priority. After that, who knows.
[Fascinate Android Development] pntballer505:
Interesting. Well cool, thanks for everything.

Oh? I thought BLN was not working atm with the 9/15 kernels?

"Well here is the builds without BLN. I didn't have time to look at BLN, so I decided what the hell."
[Fascinate Android Development] bigjobber69:
as far as 9/15 do u still need to use the in-call volume script or is that in the kernel now?
[Fascinate Android Development] neh4pres:
The kernel Is fine without the script.. The script Is for adjusting if you have the desire to do so.

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] neh4pres:
Don't use the bln app.. Use blinky from the market

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] sixstringsg:
But then after that we had a whole discussion about it working. I'll go edit the post. Most say it works if you use blinky.
[Fascinate Android Development] ssewk2x:
I've been fiddling with it for a while now. I'd say it partially works. As long as you enable the blink feature, its fine. If you leave blinking off, then it's anyone's guess.
[Fascinate Android Development] FJRSport:
Fascinate

ED05

MIUI 1.9.16

Ran cleaning script for MIUI then installed Glitch v12 ML.

Still unable to rotate into landscape. Confirmed that settings has Auto Rotate screen is on.

Suggestions?
[Fascinate Android Development] scarmon25:
I would have to say it works when it wants too. ;)
[Fascinate Android Development] sixstringsg:
Don't run cleaning scripts for starters. The kernel has one built in.
[Fascinate Android Development] sixstringsg:
We are now on ROM manager. I'm not sure what all I'm going to put there other than final releases, so still check here.
[Fascinate Android Development] scarmon25:
Sweet. Is it uploaded for just the fascinate or mesmerize too
[Fascinate Android Development] sixstringsg:
Just fascinate. I forget about the mesmerize a lot.
[Fascinate Android Development] shag_on_e:
I am dead serious, this kernel makes MIUI the fastest I've ever seen on my machine. I haven't tried it on anything else yet, but if it's this crazy on MIUI I can only imagine CM7 or Vanilla.

Sent telepathically.
[Fascinate Android Development] scarmon25:
If you could do the mesmerize at some time it would be much appreciated. I know you've been busy to whenever you can if you choose to is awesome.
[Fascinate Android Development] ssewk2x:
Exactly, lol. Which means the root cause is gonna be a ***** to find. :-P
[Fascinate Android Development] sixstringsg:
I'll do it this evening.
[Fascinate Android Development] akellar:
Any reason it can't just be reverted back to the old BLN that is built in and doesn't require an app? That version at least worked ;)
[Fascinate Android Development] sixstringsg:
It didn't work well either, so no we're not going back.
[Fascinate Android Development] akellar:
Hmm never had any issues with it but whatever you guys decide to go with works for me. Just miss my BLN :)
[Fascinate Android Development] sixstringsg:
It killed the touch keys quite often. Plus blinky is quite nice. It also has the added benefit of being in line with upstream.
[Fascinate Android Development] akellar:
Ahh yeah I guess I did randomly have that issue. Didn't realize it was because of the BLN though. I'm just not a fan of the blinking BLN. Kinda distracting at night :)
[Fascinate Android Development] sixstringsg:
You can set quiet hours in the app.
[Fascinate Android Development] akellar:
In Blinky? Or are you talking about in CM7? I'm on Miui.
[Fascinate Android Development] chopper the dog:
BLN control pro.

good day.
[Fascinate Android Development] akellar:
I was under the impression that BLN Control didn't work, which is why we are using Blinky.
[Fascinate Android Development] sixstringsg:
Works for some, not for others. It works for me.
[Fascinate Android Development] GizmoDroid:
There used to be a short timeout on the lights for the touch keys. Did this get extended as a result of the changes with BLN?

I've always hated the touchkey backlights. I try to read my phone in the dark with the screen dimmed all the way, then I get blinded by the touch keys as soon as I touch a button. Not to mention that they cause the other person to hear a buzzing noise if I have my phone on speakerphone.

Waaay back in the day, (last year, haha) someone worked on this by, I think, tweaking the voltage powering them or something; I can't remember.

Then there are the shortened touch key mods for touchwiz that I worked on before, but that is in the ROM, not kernel.

Heck I'm getting to the point where I almost just want them to never light up if they won't properly turn off in a respectable amount of time.

I have to admit that I like having them for notifications, though I just have them set to stay solid instead of blink.
[Fascinate Android Development] sageDieu:
So for those of you who have played with clocks and voltages and stuff... I have an inquiry.

I run my phone at cfq/conservative, underclocked to 800, undervolted to -125 at 800 down to -200 at 100. I get pretty good performance and battery life and though that seems like it would be unstable I have never had issues.

My question is this: is battery life something that would change a lot depending on clocks? I know it does affect it, but ive seen people that say they have good battery life while overclocked. I am a heavy user of my phone and usually get about 8 hours per charge with the setup detailed above... All I want to know really is if I could/should up it to 1.2 or 1.4ghz with some uv, and how doing so might affect performance and battery life.

Thanks to anyone who replies :)

Sent from my MIUI SCH-i500
[Fascinate Android Development] scarmon25:
I'm of the belief that with the phone overclocked it allows it to complete task quickly therefore it uses less power. I have generally always ran my phone at stock clock or overclocked and honestly I cannot tell a big difference in battery between the two. The only difference is the phone performs better overclocked
[Fascinate Android Development] neh4pres:
Think of it this way. I run 1.4ghz.. That is a 40% overclock.. But the voltage difference is not 40% more. So I believe its more efficient..

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] sixstringsg:
Leakages don't have anything to do with efficiency. They have to do with the differences in different phones. Take for example different phones run better with different OC/UV. The leakages are the same way. They adjust the int voltages, which is something not configureable (yet) in userspace, so we have to configure them that way when we build. That way both the voltages that you are used to (the ones controllable via voltage control) are tailored to your device, as is the int voltages (the ones only we can do). Most people have no idea, but there are dozens of variables that we play with to make so that all of you can OC and UV as much as possible with as much stability as possible. Some aren't device specific, some are. We are trying to make the best experience possible for a wide range in chip quality, therefore we make different leakages, as well as making the kernel configurable via voltage control. From a stability/performance standpoint, and by extension standpoint, there is only one leakage right for your device. Different leakages aren't better in some ways for you and worse in others, there is only one good one for your device. Sorry if that didn't make sense, I tried to make it as informative as possible without it being overwhelming.
[Fascinate Android Development] sixstringsg:
FAQ

I am going to start writing an extensive FAQ for the third post. There is already a small one in the OP, but I want to expand on that. If you have any questions that you've always wondered about, or ones that you see cropping up all the time and would like to have a good thing to reference, shoot me a PM with the ideas. I don't want to clutter up the thread with "sounds like a good idea" and "here's the questions I want" so if it sounds like a good idea, hit the thanks button, and if you want a question included/answered, send me a PM.

Thanks,

Six
[Fascinate Android Development] sixstringsg:
I'll look into setting a timer. Just for the sake of honesty, I've never looked into adding a timer, because personally I like them staying on all the time. Tk-Glitch looked into it earlier, so I know it can be done. If the general consensus is add a timeout, then I'll do it, otherwise I like it so I'll keep it how it is.
[Fascinate Android Development] neh4pres:
Ok. I think I had the chip and the kernels confused. Where a low leakage chip is a efficient chip. But a low leakage kernel is just tailored to a low leakage chip, and in itself has nothing to do with eficiency.. Sorry if I confused anyone with my confusion

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] GizmoDroid:
How about setting it up like the volume gain script (user modifiable)?

Just a suggestion. That way it would be easy to hook into an app to control it like I'm hoping to do with the volume control.
[Fascinate Android Development] sixstringsg:
Because it's not a script. If I remember correctly, it's modifying the touchkey driver to add a timeout to the lights, therefore you can't change it with the system booted.
[Fascinate Android Development] GizmoDroid:
I see. It's been a while since I looked into it. Don't remember a whole lot of details.
[Fascinate Android Development] scarmon25:
Team. Sbrissen had a way to adjust with the system booted through tsm parts. I don't know how he did it but if that's something your interested in Sbrissen may be able to tell ya.
[Fascinate Android Development] GizmoDroid:
In touchwiz roms, the value was set in services.jar. I don't know how that translates to non-tw roms though.

I think Ssbrissen hooked a system variable into a hacked services.jar and then used an app to control this value.
[Fascinate Android Development] scarmon25:
Didn't even think about that.
[Fascinate Android Development] FJRSport:
Sixstringsg,

First,

Thank You! I do appreciate your work.

Just wanted to clarify. I only used cleaning script after installing Glitch v12 ML and noting that auto-rotate was not working. Then cleaning script and reflashed Glitch.

I have read that the cleaning script was not necessary; however, the OP suggested it might cure that problem.

Any suggestions for regaining auto-rotation without removing Glitch?
[Fascinate Android Development] Keithn:
I haven't extensively tested my phone but I am familiar with OCing a chip. You need to realize a couple of things 1 that the higher the clock the more voltage it needs and it becomes increasingly less efficient with voltage, and that lower clocks will use less voltage but do things slower. So I'd test a few different settings, probably a slight oc with uv and a governor that will not stay at higher clocks unless needed. You'll probably have to test your battery life on your own to figure out what works for you.
[Fascinate Android Development] sageDieu:
Thanks for the replies people, I decided to try overclocking and undervolting for battery life. I'm now OC to 1.4 ghz, UV -75 starting there and moving down a step for each clock below that. My phone seems to be really good for undervolting things pretty far.
[Fascinate Android Development] fstbusa:
Everything I've read points to something with the latest version of MIUI and Glitch not playing nice together. I've had the same problem since flashing Glitch and have been unable to remedy with different things I've tried.

Guess you have to just wait and see what the next release brings.
[Fascinate Android Development] neh4pres:
I'm running

newest miui and glitch and all is well with rotation... Try a Web page

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] pospower:
Glitch and new cM7

I get boot loop I clear the develk cach anything else I'm supposed to be doing?
[Fascinate Android Development] akellar:
It's already been stated in the CM7 thread that you can't use a custom kernel with it.
[Fascinate Android Development] pospower:
Sorry mIssed that. So what are you guys doing to get color fix and voltage control?
[Fascinate Android Development] sixstringsg:
Cant use a custom kernel on what?
[Fascinate Android Development] akellar:
The new CM7 nightly build.
[Fascinate Android Development] Bubbadogg14:
yeah only boot loops if u try a custom kernel on the new cm7 nightly. Not sure why they

Aren't compatible but they aren't
[Fascinate Android Development] iofthestorm:
It's generally true that with higher clock rates you need a higher voltage to run stable, but since you're controlling the voltage as well as the clock that statement doesn't mean anything. However, your cpu will burn more power at a higher clock rate with the same voltage over the same time frame but it's possible that if you complete a task faster your cpu can clock itself lower after that and save power. In general, there are too many variables to come up with an authoritative statement from first principles so the best way to determine what gets you the best battery life is to just empirically test different settings and see what happens.
[Fascinate Android Development] sixstringsg:
I'll look into it. I'm working on captivate right now, since I can actually test on one of those.
[Fascinate Android Development] ssewk2x:
You could try a cache (not dalvik) wipe also.
[Fascinate Android Development] sixstringsg:
Heads up to everyone: this kernel will probably not boot on the newest nightly. It broke things for every single SGS device as far as custom kernels, so we're looking into it.
[Fascinate Android Development] Keithn:
Yeah you're agreeing for the most part, which is why I was saying to test different settings(oc uv and cpu governors) and compare battery life. Weither you uv or no higher clocks need higher voltage to remain stable and will consume more power.
[Fascinate Android Development] sixstringsg:
If I read correctly, all it takes is a simple sync/rebuild to fix your problem with the latest nightly. I'll build soon unless someone beats me to it, and post them. Here's what broke it: http://review.cyanogenmod.com/#change,7966
[Fascinate Android Development] sageDieu:
Hey guys, ive been using blinky for BLN, been working fine and no issues there. I just checked battery stats and my display is at a record low of 6% while blinky is at 16%... kind of odd. should I try bln control pro or something else to save battery? bln isnt supposed to use a whole lot of battery but blinky apparently does...

Sent from my MIUI SCH-i500
[Fascinate Android Development] sixstringsg:
Have you noticed an actual hit in battery life? I noticed that about blinky as well, but my battery didn't take a hit, just the stats were skewed.
[Fascinate Android Development] neh4pres:
Yea.. My blinky is second to screen.. :(

Sent from the fascinate that holds the record benchmark on antutu
[Fascinate Android Development] Agenthex:
Because 1600 worked beautifully.

To be fair, 1700 worked pretty well when it was locked in. When it switches in/out of 1700 is when the system freaks out, reboots, and causes problems.
[Fascinate Android Development] sixstringsg:
Honestly, we're not going to help much with problems that arise at 1700. You should stick to 1500, it has best performance and doesn't break everything.
[Fascinate Android Development] brettdacosta:
He straight up roasts 'ems and toasts 'em.
[Fascinate Android Development] scarmon25:
LOL :) that's what happened to mine when I tried the 1.7Ghz
[Fascinate Android Development] ssewk2x:
I'm jealous. I can only get 1400 out of mine. But that's more than sufficient for me.

On an unrelated note, git cherry-pick is neat!
[Fascinate Android Development] sixstringsg:
Since you're doing git stuff, you should send me pull requests :)
[Fascinate Android Development] ssewk2x:
LOL I certainly will .. once I make sure it all actually works. And by "works," I mean "doesn't turn my phone into a very expensive paperweight."

I'm a little scared to flash at the moment, though. ;)