yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] ssewk2x:
For right now, there's not much new except a bunch of changes Tk pushed to the V14 branch and that I'd like to see tested for stability. I'm pretty sure they're just the kind of changes that you don't really notice unless something is wrong. Plus the artwork and a skunkworks string here and there..

For future reference, you can look at the commit log on the "skunkworks" branch on my github for a sort-of change log, or I will post here when new stuff is added, or maybe even both. I'll do my best to keep the commit log on the skunkworks branch clean and organized so that it'll suffice as a changelog.
[Fascinate Android Development] sageDieu:
sweet. not like there's a whole lot you can add any more... lol let us know when you get the mod to give us a 1080p screen
[Fascinate Android Development] ssewk2x:
I still have a few projects on the burner. For one, i'm still not completely satisfied with call audio...and maybe someday cfq will come back .. And there's torch, which might need a kernel change .. plus whatever i feel like experimenting with, lol.
[Fascinate Android Development] vlucchetti:
Will this run fine with Icy Glitch milestone 5?
[Fascinate Android Development] scarfman4:
I'm running it right now. So far I haven't noticed any issues.
[Fascinate Android Development] shelby04861:
No issues here
[Fascinate Android Development] vlucchetti:
Thanks, just loaded it on. Expected to see something different in graphics (like a skunk or something) but nada. Checked

about phone

and it shows it loaded. All seems good.
[Fascinate Android Development] ssewk2x:
You should have seen a boot logo featuring a skunk tail. If not, then you may not have the GB bootloaders. Find them here and install with odin in PDA:

http://dl.dropbox.com/u/28682151/GBBootloaders.tar

And yes, do install them if you don't have them - some of the other features of Glitch Official (and therefore the skunkworks builds) require them also.
[Fascinate Android Development] shelby04861:
Don't go advising too much, as people might actually do it. Then things might actually work. Then there would be no posts. Then there would be nothing to read....and well, you get the point. It all ends with the world blowing up.
[Fascinate Android Development] vlucchetti:
Thanks. Just did. Saw the red glitch with the skunk tail, then the kang glitch unicorn.

LOL, and I thought the little puppy was running fine before and did not even notice I did not have that feature loaded!
[Fascinate Android Development] sageDieu:
Hey, if you're looking for stuff to add you should do me a favor and figure out how to fix my camera hardware even though I'm 4 months out of warranty.
[Fascinate Android Development] ssewk2x:
Some camera stuff is on the list, tho I'm not sure if it's a ROM or Kernel or Library issue, or some Frankensteinian combination all 3.
[Fascinate Android Development] sendan:
I'm testing some new settings but I've run into a bug, apparently you automatically get bumped to 1500 MHz as your max frequency after a reboot if your "OC Target High" setting is less than your Max CPU frequency. Also it seems to lock you at 1500 MHz, according to CPU spy.

I've been running these settings and they have been more impressive (and stable) then anything has ever been on this phone:

Active scheduler: noop

Governor: conservative

Min CPU frequency: 200 MHz

Max CPU frequency: 1400 MHz

-------------------------------

OC Value: 110%

OC Target Low: 200 MHz

OC Target High 1000 MHz

-------------------------------

Default voltages

-------------------------------

Oddly enough it runs perfectly stable at 1500 MHz, this just seems a bit excessive for my taste. Could you guys shed some light on why this is happening?

Also I would definitely recommend these settings, I've been running them for about a week and there is zero lag or stutters. (I can finally mack on my keyboard while a flash heavy site is loading in the browser with zero lag) :D

Thanks team Glitch!
[Fascinate Android Development] sixstringsg:
That sounds like more of an NSTools issue to me than a kernel issue.
[Fascinate Android Development] sendan:
Okay, I'll take a look around in the NSTools thread. In the meantime I found a temp-fix by checking "Set at boot" under the SET CPU tab within ROM Control, in conjunction with NSTools.
[Fascinate Android Development] droidstyle:
like six said,thats a issue with nstools....sounds like you found the fix. thats what i did, when i used nstools ...my device shows no real gains from live oc. 200 min, 1200max, with -50uv across the board works really well along with deadline/lagfree.
[Fascinate Android Development] sageDieu:
ha I'm kidding, it's my hardware and it broke 2 days after my warranty ended. unless you want to take apart my phone and put in a new camera then... yeah.
[Fascinate Android Development] xsc0rchx:
Has anyone had an issue on the new SkunkWorks rebooting into Glitch CW? I have tried reflashing and each time I boot into recovery I got into CW 5 not Glitch CW.

I am running CM9 Nightly BTW.
[Fascinate Android Development] ssewk2x:
That's intentional. Glitch cw has not yet been fixed for nandroid restore as far as I know.
[Fascinate Android Development] xsc0rchx:
If that is the case then how can I modify my sleep governor and other Glitchy settings? I have the Glitch app but that does not allow me to select smoothass as the sleep governor which historically has been available from Glitch CW.

thanks
[Fascinate Android Development] ssewk2x:
Yeah, sorry about that. You can set the governor by hand this way:

1. become root

2. re-mount /system as read+write: mount -o rw,remount /system

3. edit /system/etc/glitch-config/screenstate_scaling and change it to active. avoid typos.

4. edit /system/etc/glitch-config/sleep_governor and change it to show your favorite governor. Avoid typos.

5. re-mount /system as read-only: mount -o ro,remount /system

6. Reboot for the changes to take effect.

You can do 3 and 4 using echo if you like, ie: echo "active" > /system/etc/glitch-config/screenstate_scaling

Maybe my next skunkworks project should be a script similar to callboost to configure this...

Edit: Ok, I went ahead and did it. New skunkworks kernel is up at:

http://efpophis.glitchteam.com/SkunkWorks

Grab the latest one. There's a new script called glitch-config.

Usage:

glitch-config show # shows current configuration

glitch-config set # lets you modify the configuration

Note that if you pick "inactive" for screenstate scaling, it doesn't bother asking you for a sleep governor since that setting is irrelevant.

Also in this build - some audio experiments that don't appear to have made much difference to me, but do let me know if you notice anything different call-audio-wise.

Have fun!
[Fascinate Android Development] bobthesalesclerk:
I have officially given up on nstools. Hello voltage control again :)

sent from my ice cream sandwiched Samsung fascinate
[Fascinate Android Development] bobthesalesclerk:
sent from my ice cream sandwiched Samsung fascinate
[Fascinate Android Development] droidstyle:
you dont need v control just use rom control/ performance settings.
[Fascinate Android Development] ssewk2x:
So, I had a random reboot this morning while driving to work.

I managed to get a fairly helpful /proc/last_kmsg out of it and have collected some data to begin tracking it down. Meanwhile, if any of you guys get random reboots, please do the following as soon as possible afterwards:

1. do NOT reboot the phone again.

2. save the contents of /proc/last_kmsg. To do this:

a. adb pull /proc/last_kmsg reboot_log.txt

b. or from a terminal, become root and cp /proc/last_kmsg /mnt/sdcard/reboot_log.txt

3. PM me that file, or email it to me: efpophis at efpophis dot net.

Yes, I have my own domain now. Neat, huh?
[Fascinate Android Development] Aali1011:
So I hate to be a bother but would like to get a better understanding. Since Stevespear426 is no longer doing the CM9 nightly kang with the glitch goodness V14 Beta 6 IS NOT the newest version of the Kernel correct? We have (Blank) and ssewk2x's skunkworks build. I ask because with V14 B6 on THS build 10 my sensors are broke. Flashing the skunkworks build currently and going to see how that turns out for me. So besides the skunkworks build what is there and where can it be found. I seem to have the wrong efpophis based url.
[Fascinate Android Development] remicks:
You can get the efpophis skunkworks builds from his site @ http://efpophis.glitchteam.com/SkunkWorks/ or you can get the latest mainline glitch builds from http://aokpcb.boomm.net/nightlies/kernels when I build them.

Sent from AOKPCB & Xparent ICS Tapatalk 2
[Fascinate Android Development] 94SupraTT:
Can not having the bootloaders possible cause soft reboot issues? I've ran the glitch kernel on AOKP and always had soft reboot issues. I've never ran GB Bootloaders.
[Fascinate Android Development] droidstyle:
no I doubt it...I have run glitch both ways with no reboots. Although It is advised to flash teh gb bootloaders if your running glitch. My guess is you need to turn off the 100mhz step and get your mhz/ voltages set correctly.

also follow this post.
[Fascinate Android Development] 94SupraTT:
I flashed the GB bootloader via Odin and now my phone will only boot to recovery. Am I missing a step?
[Fascinate Android Development] ssewk2x:
Shouldn't be. Try flashing the latest skunkworks build in the recovery and see if that helps.
[Fascinate Android Development] neh4pres:
i have noticed something strange going in with 3g speeds. I am a heavy user of tether and have 2 fascinates running aokp. And this issue has been on just about every rom i have run in the past year. What I'm getting is slow data speeds over time. Tonight using speed test i was getting around 200kbps download on both devices. I verify using network meter windows gadget tethering and downloading. However if i take 1 phone and wipe both caches in recovery and reboot, I'll get over 500 kbps download. While the other still gets 200kbps. This is nothing to do with location or signal. I have retested this 50 + times in the last few months. Also While generally speeds go up and down at different times of day, and different days altogether. My best 3g speeds always come after a data wipe and install of a new ROM. I then generally see 1000kbps + download speeds. I can sometimes see speeds close to this at other times but very rarely. Basically the longer it's been sense a ROM flash, cache wipe, or a reboot. The worse data speeds and pings get. I'm just looking for others input as to why this happens and possible steps to take to prevent them.
[Fascinate Android Development] 94SupraTT:
I had to Odin.

Sent from Samsung Fascinate running ICS.
[Fascinate Android Development] ssewk2x:
Crap.

Tho now that i think of it, i remember something like that going on. Here's how i got the gb loaders to stay:

1. Odin stock eh03. Reboot, let it do it's thing.

2. Odin gb bootloaders. Reboot. Let it do it's thing.

3. Odin the cwm recovery and 3 finger into it.

4. Proceed as normal (ths2, aokp, gapps, etc)
[Fascinate Android Development] 94SupraTT:
I'm going to give AOKP a go again. Hopefully doing the following resolves my issues.
[Fascinate Android Development] sageDieu:
definitely do use gb boot loaders, personally I experienced major issues with force closing and like SQL database errors and other assorted things, and gb boot loaders seemed to fix everything.
[Fascinate Android Development] shag_on_e:
With the GB bootloaders, an easy way to always have them is, extract the full EH03 and the GB bootloaders, then replace the two bootloaders in the EH03 package with the two extracted from the GB bootloaders package, then you can just use that package in Heimdall instead of having to flash both separately when doing a back to stock flash

~~~~There is no spoon~~~~
[Fascinate Android Development] 94SupraTT:
Dangit. I'll try to load them tonight sometime.
[Fascinate Android Development] shelby04861:
I use this tar version for Odin and have no issues.

http://ubuntuone.com/77uvqWQlGyroFnfgOlkw2b
[Fascinate Android Development] 94SupraTT:
Wifi tether does not work for me on the Skunkworks build. Can anyone else confirm this?
[Fascinate Android Development] sarkozy:
Nope, no tether here either.
[Fascinate Android Development] gt43aw:
six,

have a few on me. thanks for the hard work.
[Fascinate Android Development] Eris _2.1_2010:
No wifi tether here with skunkworks, USB tether works fine though.

Sent from my Glitched AOKP Mez
[Fascinate Android Development] shorttripp86:
Has anyone tried the old Wifi Tether app that we had to use back on the earlier THS builds, before they had it natively working yet? If anyone can remember which settings had to be switched around within the app, it might work as a band aid until the Glitch guys get it functioning again. $0.02

Sent from my Touchpad
[Fascinate Android Development] shelby04861:
It is wifi tether for root users. Change the phone to nexus and you are all set.
[Fascinate Android Development] sarkozy:
Doesn't work. I've used the app exclusively even though native tethering works.
[Fascinate Android Development] sageDieu:
yeah I just tried, both wifi tether and the built in hotspot start with no errors, but then they don't even show up for my computer at all. weird. I will upload a logcat of me starting first the hotspot, then wifi tether, I doubt there will be anything useful but you never know.
[Fascinate Android Development] sageDieu:
I don't thunk I could have been any more wrong, this has some very specific errors in starting network interfaces and kernel drivers and such.

http://pastebin.com/RwdiBvja

ssewk2x you should definitely check this out, it is a logcat of me starting native tethering twice (and it dying shortly after both times) and then switching to the Wifi Tether app from google code, and trying to start it. I think this will help you know what the problem is if you didn't already.
[Fascinate Android Development] ssewk2x:
Thanks. Please leave that there in your pastebin for a while. I am aware that tether is broken, and it's first on my list of stuff to work on as soon as i can. Please bear with me for a little bit, and I'll get there.

Actually, could you do me a favor? Capture the output of dmesg as well. You can do this in a terminal:

# dmesg > /mnt/sdcard/wifidmesg.txt

Do this right after you have tried to turn tether on and watched it fail.

That should tell me what's going on in the kernel itself that's keeping the system from setting up the interface.

Thankee

Edit: Never mind. I got it myself. I think I have the problem solved - stay tuned.
[Fascinate Android Development] ssewk2x:
Ok, Got it :)

New skunkworks build is up. Pick the file with the latest timestamp on it:

http://efpophis.glitchteam.com/SkunkWorks

I tested this a little bit on my own phone. Here's what I was able to do:

- Turn on tethering. Note the absence of key errors in logcat / dmesg.

- My configured network shows up in my laptop's network list.

- I'm able to connect to my network using the password I configured.

- My configured network goes away a while after I shut tethering off. It takes longer than I'd like, but oh well.

I was not able to test actual data throughput through the connection since my 3g service here sucks the sweat off a dead camel's cojones. I will leave that up to all you tether-goons to try out.

Feedback is appreciated :)
[Fascinate Android Development] 94SupraTT:
Thanks! I'll be trying this out shortly.

Sent from Samsung Fascinate running ICS.
[Fascinate Android Development] shelby04861:
Has anyone flashed this with twrp yet? I will be later. Not sure if I need to leave the "re-inject" box checked.
[Fascinate Android Development] sixstringsg:
You will need to re-inject, as it doesn't have TWRP built-in yet.
[Fascinate Android Development] sageDieu:
thanks, sorry I couldn't get the dmesg for you as I was in school but I'm glad you got it figured out. I will try your latest build soon and report back if it works.
[Fascinate Android Development] shelby04861:
I had to Odin back to stock and then flash and restore. I was also told that if I tried flashing cm7 to fix it i was supposed to flash it twice for some reason. i am going to screw the phone up again on monday and try that and report back. it would just be nice to know how to fix it without odin. thanks again to all
[Fascinate Android Development] Nemeth27:
Sixstrings, thanks!

It was the screen scaling. Is it suppose to be like that or is it a bug? I would love to be able to use screen scaling for when I'm not using music.
[Fascinate Android Development] droidstyle:
this is not some mythical fix...it's posted in the op of sbrissen's THS thread.

"Note: The upgrade process from CM7 to ICS is automatic, but downgrading from ICS to CM7 (or restoring Nandroid) requires flashing twice. Once from ICS and again from CM7's recovery."

http://rootzwiki.com/topic/16630-romicsiml74k-teamhacksungs-ics-port-for-fascinate-build-61-0201/
[Fascinate Android Development] bobloblaw1:
Honestly screen scaling shouldn't be a big deal. In fact, screen scaling may actually hurt the battery life in kernels which have deep idle implemented (like this one). I'm unsure of the idle method glitch uses however if you Google "deep idle" and "ezeekel" (ugh I may have spelled that incorrectly) you will find a thread which shows and explains that a high clock will allow the phone to "race to idle" and enter the low power state earlier.

Feel free to correct me if this is inaccurate based on the method glitch uses.

Edit: link wasn't as easy to Google as I had thought so here it is: xdaforums.com/showthread.php?t=1297535
[Fascinate Android Development] sixstringsg:
Theoretically, you are correct. Unfortunately, android is not perfect, and its apps certainly aren't. Screen state scaling hasn't proven to save any realistic amount of battery, nor has race-to-idle.
[Fascinate Android Development] bobloblaw1:
Hehehe, well, I did say it "may" hurt it ;-).

While this is anecdotal and subjective, (yikes, talk about a modifier abdicating all levels of accountability) I find ROMS with deep idle do in fact give better battery life... in most circumstances (there goes that modifier again).

Bad apps will kill your battery life regardless but in that instance screen state scaling actually would probably help. But then again the rogue app is gonna make your battery life suck ; Its just the magnitude of suckage would be reduced lol.

I guess this is pretty much a question of preferences at this point since there are so so many variables.
[Fascinate Android Development] k_nivesout:
While not everything applies to our devices, I've found that this thread (from the Nexus S forums) has a lot of useful info regarding deep idle, battery life, and much more.
[Fascinate Android Development] Glocjt:
I see that you've figured out your issues, but here's what I'm currently running:

Defaulting with fiops/GlitchOndemand

LOC 110% at 1320 max, default voltages

Screen state scaling on, gov set to lazy

I've only been trying SSC on with lazy since last night, and thus far it hasn't been giving me any issues.
[Fascinate Android Development] Nemeth27:
Thanks for your info!
[Fascinate Android Development] sageDieu:
I must say, in the small amount of time I have used each ics version of glitch before it corrupts my SQL databases and bootloops, I have not noticed any increased battery life with it over the stock ics kernel. The stock one runs well enough that I haven't really bothered to try and fix the issues with glitch, I probably will once they get the fixes in for the softkey presses on low signal like in glitch 13.

Sent from my ICS SCH-i500
[Fascinate Android Development] shelby04861:
Thanks a ton. I looked all over the place and never saw that. I mostly searched my exact problem. I am still gonna try it on Monday and see if that helps me to get out of the recovery in that situation.
[Fascinate Android Development] bobloblaw1:
At least to me, that would mean that deep idle is beneficial when playing music.
[Fascinate Android Development] sixstringsg:
Thats really the only time deep idle is useful is screen off music. I can't think of anything else that is heavily used when the screen is off.
[Fascinate Android Development] k_nivesout:
There were a couple other situations where it would be beneficial. While using GPS and/or bluetooth IIRC. In that thread, it unfortunately seems that there are no battery life improvements with eugene's deep idle implementation (the one in v14), while reports seem to indicate that ezekeel's version is effective.
[Fascinate Android Development] pntballer505:
Question, when using NStools, what is the difference between

Arm Voltage and Int(internal??)voltage? I have default settings checked,

but I'm not really sure what the default voltage settings for this kernel

are already?

Edit: ohhh, just read the OP again. So i guess what is the big difference b/w arm and int voltages?
[Fascinate Android Development] neh4pres:
Also should be in op or a link in op
[Fascinate Android Development] pntballer505:
ahh, yeah. My mistake. Thanks.

Edit: Oh, bit of a problem. I've tried to delete the NStools voltage settings from

Glitch recovery. But when i reboot, it keep going back to recovery?
[Fascinate Android Development] xsc0rchx:
Sorry to mention this if it is already known, but the phantom key press issue seems to be very relevant in v14B3 for 6.1. I was running v14B3 with AOSP and migrated to THS 6.1 with v14B3 for 6.1 and now I get a lot of phantom presses. I am not complaining about this just wanted to bring it to attention if it has not been already.

I know a lot of work was done by ssewk2x on this issue, just not sure if that was planned to get migrated into v14.

thanks,
[Fascinate Android Development] Enyo.:
Keep in mind to Never use the 3-finger way to get into recovery at the moment.
[Fascinate Android Development] pmjr0987:
crap, i messed up and i cant find what i did wrong, because i think i did it really stupid

First off im running Verizon Fascinate with Glitch v13 . Im getting horrible back outs and random keyboard pop ups that make the phone a living hell. I read on here and rootzwiki about the new release fixing this sooo...

I downloaded the "CM9-fascinatemtd-Glitch-V14-B3-ForBuild6" that came up when i clicked on what i though was the update file. it was 5 mb and i transferred it to my phones sd card

i went into recovery and clicked update apply update and it took about 10 seconds and was done said it was successful. i went to reboot and now no matter what i do its stuck at the very first boot screen that says just Samsung in white with a black background wont do anything else

ANY HELP APPRECIATED! the soooner the better :)
[Fascinate Android Development] shelby04861:
Thanks six. Just flashed and all was fine. So bleeding edge dude! What a rush....let's do it again!
[Fascinate Android Development] ssewk2x:
Yeah, I guess I missed that.

No worries - I just got twrp into a new build:

http://efpophis.glitchteam.com/SkunkWorks/Glitch-fascinatemtd-SkunkWorks-20120518.2110.zip

Yes, this also has the tether fix from earlier.

If you flashed the tether fix kernel with TWRP and did the re-inject thing, then flashing this one won't do anything for you, btw.

Enjoy! :)
[Fascinate Android Development] 94SupraTT:
Thanks. Just flashed this and it looks like tether is working.

Sent from Samsung Fascinate running ICS.
[Fascinate Android Development] Stephen.k.spear:
BTW TWRP had the option to reinject it self after flashing. So if your new ROM or kernel doesn't come with it make sure the box is checked and it will persist through flashing.

Sent from my Glitched AOKP Unicorn.
[Fascinate Android Development] Eris _2.1_2010:
Tether working great here. Thnx

Sent from my Glitched AOKP Mez
[Fascinate Android Development] k_nivesout:
Tether working again here, both with "wifi tether" and built-in hotspot. Also, TWRP is awesome, I like it a lot! Excellent work sswek2x, thanks a bunch.