yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] Deliquified:
Just making sure I'm reading this correctly, but you're trying to use smooth ass as your sleep governor? If so, you're actually wasting a good bit of battery as smooth ass runs with a fairly high clock speed. I'd go with conservative or lazy. I actually turned off screen state scaling and sleep governors myself awhile ago due to my phone being jumpy while scrolling and it'd hang and sleep of death 2-3 times a day. Haven't had an issue since turning it off.
[Fascinate Android Development] droidstyle:
I havent seen uch of a difference either way...1500mhz seems to run the fastest but eats up more battery... I have yet to see any benifits of live OC on my device.

But in regards to my last post, I was just stating that the last ns tools update was automatically maxing out the clock speed and causing folks devices to lock up on boot. Shags post of the ns tools settings reset.zip will cure that problem.
[Fascinate Android Development] bobloblaw1:
I personally find a decent liveOC (10-20%) gives a better general experience since the GPU renders the UI in ICS. That said, certain apps that aren't GPU accelerated will run better with higher clocks. I've been on both side...I've tried really high clock speeds and really high GPU overclocks and, as has been said before, it is best to find a balance and what works best for you and the apps you use.

The one thing I'm wondering about is if there's anything I can do to reduce battery drain while the phone is idle. On Gingerbread (1500maH battery)on imsoyen's leankernel I'd lose maybe 4-6% overnight. On glitched ICS (1800maH battery) I'll drop nearly 20% overnight. I'm already running conservative governor all the time. I don't see and out of the ordinary wakelocks or other usage.... Any other tips?
[Fascinate Android Development] droidstyle:
Im running lag free and only see around a 4-6% drop overnight on build 32. However occasionally I have seen the 20% drop in the past...It seems that it never goes into sleep when this happens. Im not sure what the solution is...
[Fascinate Android Development] bobloblaw1:
The weird thing is that cpuspy shows my phone sleeping for about 95-99% of the night. I don't think I've ever achieve 4-6% drain over 7-8 hours on any ics build/kernel but I know the drain isn't always this bad. It's just weird that the stats even report okay. I'd wipe and low level format but I don't think that would really help since the problem is sporadic.

Just weird.
[Fascinate Android Development] kyleco:
I've been 1500 mhz oc with a 120% live oc for voltages 800 to 1200. Glitchass. My phone flies. Better than red bull! Ymmv. This also kills battery. Haha

Sent from my SCH-I500 using Xparent Blue Tapatalk 2
[Fascinate Android Development] bobloblaw1:
So last night only had a drain of about 8% over 8 hours. Yay!!

Now the weird part. I was only in idle for 78% of the time with most of the remainder on the 100mhz step. So I idled less last night but had better battery life. :what:

Could something be not quite right with idle? My battery stats seem to give fairly accurate readings.... I'm just really confused though I'm quite glad I didn't have another big drain night :-)
[Fascinate Android Development] Deliquified:
Try setting your min clock to 200 mhz instead.. I'm fairly certain that through testing they've found that 200mhz is better battery wise.
[Fascinate Android Development] joshkoss:
@Six! Congrats on the promotion :cool:

welcome to the team!
[Fascinate Android Development] neh4pres:
Huh. Is this Android related?
[Fascinate Android Development] bobloblaw1:
He actually was just signed by the Chicago cubs and josh is also on the team so he is welcoming him.

:p:p:p

Congrats dude lol
[Fascinate Android Development] sixstringsg:
You can't see on the XDA app. I'm a moderator now. Not for fascinate though.
[Fascinate Android Development] neh4pres:
Congrats

I just found out that some governors have settings that you can tinker with in nstools. Does this kernel support that? If so, is there a guide to some of those settings. Ex. "ignore nice load" in conservative gov.
[Fascinate Android Development] sageDieu:
interactive settings show up but I have no idea what they do. lol
[Fascinate Android Development] ssewk2x:
I'm pretty sure those settings only display if the kernel / governor does, in fact, support them. So yes.

Neither do I - fiddle at your own risk, lol
[Fascinate Android Development] ssewk2x:
So, you know how we have been seeing the awesome boot audio file drop dramatically in volume during the bootup process? Yeah?

Yeah .. I fixed that. Turns out there was a "jack_mic_bias" variable that was being used to determine the value of a gpio pin before being initialized. Note to aspiring programmers: always initialize your variables, especially if they're global.

Anyway .. please flash this test kernel and let me know how it goes:

http://efpophis.glitchteam.com/CM9-fascinatemtd-Glitch-20120424.1717.zip

This may also fix a bunch of other audio related stuff - so please try a few things out and let me know if you notice any changes in volume and quality, for better or worse.

Thanks!
[Fascinate Android Development] Deliquified:
Could be placebo effect, but my music sounds less distorted/louder.. Btw, was anything changed related to signal strength? I'm suddenly getting 3 bars in a place where I've never got more than 2..

Awesome work guys.. You have my gratitude
[Fascinate Android Development] ssewk2x:
Nothing that i know of related to signal strength. This has also opened up a whole new area for me to investigate audio-wise. could be interesting :)
[Fascinate Android Development] Deliquified:
Sounds promising.. I forgot to add my setup I'm using.. I have musicfx deleted, the cm9 dspmanager zip installed (I read somewhere cm9 was missing a certain file related to eq settings.. this fixed it), deleted the dspmanager app, and am using Voodoo sound app and Volume+ to manage my hardware/software sound eq. Sounds like an audiophiles wet dream.. ;)
[Fascinate Android Development] sageDieu:
nop, boot audio is ultra gay
[Fascinate Android Development] shag_on_e:
^^^ too cool for school

~~~~There is no spoon~~~~
[Fascinate Android Development] ssewk2x:
hahaha well, to each his own. But nonetheless, boot audio is what uncovered it. And I still don't know how far down that rabbit hole goes - it could affect everything from speaker phone echo to in call volume to media /notification volumes and quality.

And who are you calling gay? You're running a ROM who's mascot is a rainbow-pooping pink unicorn...

... Not that there's anything wrong with that ...
[Fascinate Android Development] sixstringsg:
So, TWRP officially works for ICS now as well :)
[Fascinate Android Development] shag_on_e:
I had a feeling you were keeping super high security stuff quiet when I asked about it a while ago. You da man!

~~~~There is no spoon~~~~
[Fascinate Android Development] sageDieu:
you guys should check out that one recovery project... it's like all touch and stuff and it has lots of cool options and you can turn the screen on and off and junk... it's totally wicked on the nexus.

steve, you know what I'm talking about. make it happennnn
[Fascinate Android Development] Stephen.k.spear:
Thats what he's talking about goof ball.

This is awesome BTW way better than that touch recovery fiasco you did with me six. I guess Smashers recovery skills > mine... :-)
[Fascinate Android Development] shelby04861:
Dang...there is always something to keep you guys busy. I was liking the touch recovery. The regular recovery reminds me how lucky we are to have these fancy thumbs on our hands!
[Fascinate Android Development] sageDieu:
disregard, I was confus
[Fascinate Android Development] nothingblooms:
I would love to , do they have a fascinate/mes version? If so please point me in the correct direction.

Thanks,

nothingblooms
[Fascinate Android Development] sixstringsg:
TWRP is coming very very soon.
[Fascinate Android Development] sageDieu:
I was referring to twrp, I was confused between it and something else. we're now getting the thing I was saying to check out.
[Fascinate Android Development] kallell:
FYI - if anyone wants to see what this rom is capable of check out this post. Battery lasted me 4 days 18 hours and 25 mins on one charge.

http://xdaforums.com/showpost.php?p=25342518&postcount=1690
[Fascinate Android Development] bobloblaw1:
I might be extremely lat with this, but I know at certain points folks have been asking what each governor does and "why x governor should be used over y governor".

I finally found the threads I had been looking for that answers a lot of these questions. It even has some tweaks people can try if they are so inclined:

General stuff about governors: http://xdaforums.com/showthread.php?t=1369817

More Technical stuff about the ICS kernel: http://xdaforums.com/showthread.php?t=1572937

Edit: some of the stuff, such as dual booting in 2nd link, is GS2 specific but there's still a ton of good info here
[Fascinate Android Development] thisguy23:
Is it a bad thing if I've checked this almost every hour since a possible update word was put out?... Nah I don't have a problem!
[Fascinate Android Development] shag_on_e:
Right there wit cha man.

~~~~There is no spoon~~~~
[Fascinate Android Development] sixstringsg:
Oh, I should probably make a fassy TWRP, huh?
[Fascinate Android Development] shag_on_e:
Please!

~~~~There is no spoon~~~~
[Fascinate Android Development] Eris _2.1_2010:
Or this cute kitty gets it.

Sent from my Glitched AOKP Mez
[Fascinate Android Development] bobloblaw1:
Holding out on us, huh?:D
[Fascinate Android Development] sageDieu:
it may have issues so you guys will have to wait a little longer... they're working hard as usual. maybe a few donations would encourage them to get it out faster? ;)
[Fascinate Android Development] ssewk2x:
Well...i think we/you need to be able to:

1. Build twrp from source.

2. Modify the twrp source to support our mtd partition layout.

5. Three, sir!

3. Test the ever-loving sh!t out of it.

I say this because yesterday I used my twrp glitch build to try a data wipe. It didn't go so well. I suspect that, among other things, it didn't do anything to datadata, so the wipe was incomplete. This lead to BadThings(tm).

Then I tried re-flashing build 34 with glitch and normal blue recovery. This lead to boot loops with no recovery. So, I Odined the old cwm for cm7 fix and tried to flash ths2 with that. At that point, my phone became a clusterfuck of boot loops and other very strange behavior (like seeing both ths and glitch kernel logo screens in one boot, which then looped).

So, I don't think twrp flashes roms or kernels or recoveries correctly, either.

To make a long story short, I ended up spending the evening with Odin while my smoking hot wife went to bed without me :'( Not quite what I had planned....

On a positive note, the fresh install is even snappier than the dirty-flash I had before. But I won't be messing with twrp unless I can also mess with the source and try to fix it ... Cuz it is not ready for prime time on our devices yet. At all.
[Fascinate Android Development] shag_on_e:
Damn!

~~~~There is no spoon~~~~
[Fascinate Android Development] sageDieu:
pics or it didn't happen.
[Fascinate Android Development] thisguy23:
Well Damn looks like the glitch devs will have to go to back to tweaking the kernel and making it better :(
[Fascinate Android Development] ssewk2x:
We'll get there. I posted that huge rant / account in order to hopefully give the guys working on the twrp recovery an idea of what was going on. Plus, I still want to test more things related to this audio stuff. I still see some potential for that "make things really quiet" gpio pin to get set when it shouldn't, and I need to investigate that further...

Also, something noteworthy - after my Evening With Odin, stuff seems even louder on my phone now. I didn't change any of the settings .. but holy crap!

Of course, it could just be that things are quieter here in the office...

In your dreams ;)
[Fascinate Android Development] Dees_Troy:
You can build TWRP from source. All of the source code is public. There's guides here and here.

TWRP doesn't have support for datadata yet. Some might consider this a huge oversight, but to put things in perspective, there's only a handful of devices that use that kind of setup and none of the main TWRP developers have owned a device with that setup. If I had such a device I could probably add support for it in a day or so. If you want to attempt it yourself, the changes would lay mostly in ddftw.c and backstore.c If you get it working, please submit a pull request so we can add it to the main code base.

At some point I want to re-do the nandroid engine to be more flexible so that it can more easily handle stuff like datadata, but there's so many things on my to-do list like adding an on-screen keyboard and improving and adding GUI elements, moving to CM9 etc. It's just going to take a little while and won't happen overnight.

As for flashing boot, it's really hard to say. If you were flashing zips and left the TWRP injection on then that might explain some of the weirdness. I've flashed CM7 over my existing TWRP install with and without injection and it worked as expected in both cases. Zip install is mostly handled by the zip itself via the update-binary and update-script so the recovery doesn't have much control. On MTD devices we use flash_image/dump_image but that's only for backup and restore. I did find an odd issue with flash_image though that affects these kinds of Samsung devices. I think flash_image checks the existing boot image and compares the first 2KB of data. If it's the same, flash_image refuses to flash. This method works fine on "normal" Android kernels, but not with the way that custom kernels in CM are packed, so we may have to force an erase_image or update flash_image to ensure that restores get flashed. I only found this issue yesterday. We avoid using erase_image normally because that's extra wear and tear on your memory chips as a normal flash is sufficient.

FWIW, the only Samsung device that I have to work with right now is a Sprint Epic 4G (SGS1 in the USA, CDMA and it doesn't have any emmc so no datadata). I also have a VZW GNex but that's more "Google" than it is "Samsung" as Google doesn't do things the way Samsung does which makes recovery *much* easier.
[Fascinate Android Development] ssewk2x:
Excellent! Thank you.

Sure, I will be happy to check it out at some point, unless someone beats me to it. Meanwhile, though, unless there's been a fork that has added it, I'd suggest either taking down the Samsung images or marking them with a big warning. No one likes a surprise like that, lol.

Yeah, I'm not really sure what happened there. To be honest, I was a little distracted while trying to figure it all out - I may very well have done something dumb, too. Thankfully, Odin was around to save the day.

Yeah .. leave it to Sammy to complicate things. But they're still the only ones I know of that ship with an open bootloader still, so I guess I'll be stuck with them for a while. I'm not about to buy a motorola or HTC that I either can't unlock at all, or have to wait for them to decide when I get to....

Anyway . thanks for all the information, and please know that I did not intend to bash twrp at all .. just to point out that it is not ready for our devices yet and show a little bit about why.
[Fascinate Android Development] thisguy23:
Looks like the latest test kernel breaks YouTube playback on latest AOKP and MIUI. Anyone else have this issue.
[Fascinate Android Development] xain713:
I usually don't use the YouTube app I use the mobile site ( and videos from the app are really slow to load for me most of the time)
[Fascinate Android Development] ssewk2x:
Im not sure where you're getting the kernel you're talking about, but you're best bet is to use the aokp glitched builds. They have newer kernels with them than any of the stand alone kernels out now.
[Fascinate Android Development] thisguy23:
I'm using the test kernel released a few days ago by six that had audio fixes. The mobile YouTube videos won't play either. Will try another and see if it fixes it.
[Fascinate Android Development] sixstringsg:
I don't remember posting a kernel recently. I could he crazy though...
[Fascinate Android Development] Deliquified:
It's this kernel newer than the one included with the latest Glitched build?
[Fascinate Android Development] ssewk2x:
No. That one doesn't have Steve's stability fixes in it, as far as i know.
[Fascinate Android Development] thisguy23:
That's right ssewk2x posted it. That's the one I was using that YouTube wasn't working.
[Fascinate Android Development] Deliquified:
What stability fixes were added? I've never had issues with the kernel since flashing. Also, were your audio fixes added to the newest rom kernel? I guess what I'm asking is, what kernel has the latest features and fixes?
[Fascinate Android Development] sageDieu:
go to nightlies.exynos.com and download the glitched build 34 for whichever phone you have.
[Fascinate Android Development] mezster:
It seems to me that with all this ics kernel and rom development things can get a little confusing. I mean with how fast aokp is releasing builds and Steve's glitchy builds, then you have the glitch kernel itself along with all the test builds being released, it can be difficult to keep up with if you're not checking forum threads daily (even hourly it seems).

Don't get me wrong I'm not by any means complaining, it's just that I can understand how some can be so confused. I myself love all the options, even if I do have to check xda every few hours. :D
[Fascinate Android Development] ssewk2x:
Yeah, i get it. Like I said before, your best bet is to just flash the glitched up build 34 and leave it at that. Don't flash a different kernel - the one in the ROM itself is better.

That's what i have done, and my youtube videos play perfectly. For now, there is really no advantage to flashing a glitch kernel separately, and in fact, doing so might break stuff. At least until we figure out the recovery situation...
[Fascinate Android Development] Deliquified:
I have b34 installed, I just wondered if the ssewk2x audio test kernel fixes made it into the b34 kernel since the rom build date was so close to the test kernel date.
[Fascinate Android Development] ssewk2x:
Yes, they did. It also says so in the OP.
[Fascinate Android Development] 94SupraTT:
Do callboost settings require a reboot to go into effect?

Sent from Samsung Fascinate running ICS.
[Fascinate Android Development] adamklo:
Shouldn't.
[Fascinate Android Development] shag_on_e:
Curious on how things are going with the TWRP? I saw where it doesn't support datadata just hoping the beast squad figured something out...

~~~~There is no spoon~~~~
[Fascinate Android Development] ssewk2x:
I don't think anyone of actively looking at it right now...maybe six or Smasher, but i really don't know. I was going to, but I've gotten really busy at work and with family stuff again. And my development environment got all buggered up, so i will have to figure something out before i can continue working on anything android-related...which is going to take time that i can't seem to find right now :(
[Fascinate Android Development] .Ejekt:
These are ROMs though, yes? What about just the kernel? Where can we non-AOKPers get our most-recent-glitch-build on?
[Fascinate Android Development] sageDieu:
the roms have glitch built in. I'm sure you could find some separate versions of glitch floating around but they will be older than the most recent rom on exynos.
[Fascinate Android Development] .Ejekt:
So, there isn't a place where the updated kernels are being posted? They're exclusive to the AOKP roms?
[Fascinate Android Development] sixstringsg:
I just got back from school for the summer, I'll work on it.
[Fascinate Android Development] .Ejekt:
Awesome! I'm on MIUI and hate to be missing out on fresh Glitch-ness.
[Fascinate Android Development] ssewk2x:
I've got a "skunk works" project in the works, too. Stay tuned ;)
[Fascinate Android Development] shag_on_e:
Tuned...as usual.

~~~~There is no spoon~~~~
[Fascinate Android Development] ssewk2x:
Ok, so, you all know how I'd been posting test kernels left and right, often with a bunch of new stuff for you all to try, but they weren't really Official Glitch releases? I got the idea that what I'm doing is basically a SkunkWorks project. I'm working with minimal accountability and lots of leeway on the Bleeding Edge of the Glitch kernel.

Unfortunately, this has also had its down-side - people tend to confuse "latest official glitch" with whatever I've thrown over the wall, and the two are distinct. So, I've gone ahead and started my own fork of the Glitch source on Github, and done some re-branding in the kernel so that you won't be confused about that. I'm going to call these builds "Skunkworks builds," and it will be obvious that you're using one when you see it. You'll be able to tell the build date and time from both the ZIP file and from the information in your About Phone area. They will also both have the name SkunkWorks in them. I'm not going to give them version numbers - just track them by the timestamps. Generally, you'll want the most recent one.

I want to make it clear that these are subject to the same conditions as my test kernels of old. They are not guaranteed to be stable, nor are they official Glitch. They may contain things that don't make it into Official Glitch, and official Glitch may have stuff that's not in these. I will do my best to keep the two lines synchronized, and this is still primarily an effort on my part to contribute to the Official Glitch kernel. Doing things this way allows me to use willing flashers as guinea pigs, and allows you guinea pigs to try out new stuff whenever I feel like making it. Consider this the shady R&D department of Team Glitch, much like Boeing's "Skunk Works" division was / is the shady R&D department of the military-industrial complex.

For further reading on the inspiration for the name "Skunk Works," read this:

http://en.wikipedia.org/wiki/Skunk_Works

To find all of my SkunkWorks builds, bookmark this page:

http://efpophis.glitchteam.com/SkunkWorks

Hint: There's one there now. Go get it if you want to give it a try. It is the latest bleeding edge glitch code plus a few SkunkWorks cosmetic easter-eggs. Enjoy!

OH!

Source is on my Github. When I post one, I will git tag it with the same time stamp as the zip file. That way if you care, you'll be able to match the source with the stuff you're downloading. And, more importantly, I'll be able to match the version you're complaining about with the source I used to build it! My github is at https://github.com/Efpophis
[Fascinate Android Development] thisguy23:
Amazing news. Downloading now. I checked github and the only thing I saw was 3.1.10. The current glitched aokp has that..

Is there anything other than that new?

Thanks for this btw
[Fascinate Android Development] ssewk2x:
That's my bad. I forgot to set up my fork to default to my skunk works branch. I'll fix that tomorrow.

Look under the "branches" pull-down and you'll see it. You can also look at the tags to see new versions.

I do not mess with the linux version number. Tags, commit history, and zip file names will tell you what you're getting.
[Fascinate Android Development] shag_on_e:
Awe sooky sooky!

~~~~There is no spoon~~~~
[Fascinate Android Development] shelby04861:
So what new changes are you trying out in this skunk works kernel of yours? I see the obvious of course :D
[Fascinate Android Development] DrkGhst87:
Digging the skunk tail :thumbup: (pointing out the obvious :rolleyes: lol)

Sent from my Glitched MIUI v4 Fascinate using the XDA Premium app.
[Fascinate Android Development] thisguy23:
Flashed. Booted up perfect. No problems so far. Not sure if I should be looking for anything special ;)
[Fascinate Android Development] sageDieu:
hm, ill probably inject twrp into this and try it out tomorrow. is there any sort of changelog so we can see what it offers over, say, glitched aokp m5's kernel?