yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] ssewk2x:
Hey JT, I don't think anyone here disagrees with the indisputable fact that you are the f**kin MAN when it comes to making this phone work. I think what Six was talking about was THS's perceived unwillingness to accept most of the changes that have been made to improve this particular kernel into their own. We all are certainly grateful to the team and especially you for all the work you've put into the Fassy and let the rest of the community blatantly kang. If you or the team ever feels like we haven't given enough props in one of our releases, please let us know and we'll fix it.

Is the perception of THS's attitude towards "outside" contributions the reality? I don't know. I'm more likely to believe you all are busy doing your thing and probably have hundreds garbage pull requests (maybe even some from Enyo *shudder*) come in that really don't deserve consideration, and so it's understandable if some good ones get lost in the noise. Even if, for some reason, THS just doesn't like what we're doing here, then well .. that's why we have open source kernels and our own forks, and that's what makes this platform and community great. We can all do our own thing, and as long as we don't let our egos get in the way and cause drama, we can all co-exist and do our own things to help make things better.

I'm pretty sure that ship has already sailed, lol. Personally, I can hardly wait to dig through it and see what you did. I usually learn quite a bit from reading your code. Also, thanks!

TL;DR version: JT and THS are awesome, we know and acknowledge that every time we kang their stuff. Some were just wondering y u no want our helps. Also, thanks for fixing our radios. kthxbai
[Fascinate Android Development] Tk-Glitch:
For anyone who want to use the 3.0.8 kernel, one of the Glitch testers did make some patches for you to enable ICS onscreen buttons. The downside is that it'll also disable LED notifications.

IT'LL ONLY WORK ON JT'S/TeamHacksung's BUILD 2 !

Here is the patch to enable the onscreen buttons.

Here is the patch to disable the onscreen buttons.

For anyone who get a garbled screen instead of the bootlogo, you are running Froyo bootloader !

Please update to Gingerbread bootloader, available HERE as Odin flashable tar. It's a risky process, don't flash it if you don't know what you are doing.

EDIT : Build 11 are the Cappy/i9000 ones. Sorry for the confusion guys.
[Fascinate Android Development] sixstringsg:
This ^^ that day I was mostly frustrated about they whole device tree thing. I wasn't trying to talk bad about any developer that makes this phone better.
[Fascinate Android Development] sageDieu:
Six, what i meant last night by "first one" was just that I flashed it before anybody else had reported issues, and it screwed my phone up really bad so that I couldn't report them because I was away from a computer. :P

Glitch, with the GB Bootloader, what are the risks? I used to be on that, but I must've been put back on froyo at some point with all this odining yesterday.

Also, who made the button mods you posted? It would be awesome if they could take a look at this thread: http://rootzwiki.com/topic/12573-mods-ics-button-barlauncher-mod-for-encounterics-beta2/

It has a Trebuchet launcher mod to make it fit better with the buttons, plus another mod for the button mod to make it so it has a search button and menu buttons always there instead of just sometimes.
[Fascinate Android Development] tripacer99:
Looks good, but it looks like v14 (3.0.8) is nowhere to be found in the OP, or the thread! :(
[Fascinate Android Development] sixstringsg:
I tool the link down, due to no soft keys. But if Glitch still wants it, here it is. http://goo.gl/lz7pQ
[Fascinate Android Development] djk21108:
v14 with 2.x. kernel is running smoothly on my phone. No issues to report yet. Seems snappy and has no soft key issues.
[Fascinate Android Development] droidstyle:
Thanks TK, Odining GBbootloaders fixed my splash screen isssue!!

---------- Post added at 01:07 PM ---------- Previous post was at 01:05 PM ----------

There does not seem to be any risk...just flash the GBbootloaders like you did before and all is well!
[Fascinate Android Development] Azuma73:
ODIN in PDA section as well?
[Fascinate Android Development] droidstyle:
Correct!!!
[Fascinate Android Development] fstbusa:
I have had just the opposite experience compared to CM7/V13. Menus seem to lag(1-2 sec) before opening. Sometimes adding widgets lags slightly.

My main gripe about the combo was it seemed the browser was super laggy. It didn't matter which I used, stock, dolphin, opera, ect.

I'm not complaining about the kernel as its awesome to see it develop. I'm just not sure our phones can run ICS efficiently enough.... :confused:
[Fascinate Android Development] Aali1011:
Indeed u did, but I thank you for the clarification nonetheless. Better safe then sorry in my eyes.
[Fascinate Android Development] yonith:
@fstbusa I too am experiencing this lag. There also is frequent lag when using the keyboard. Don't agree with the last part of your post as build 2 was much smoother and more responsive for me. BTW I'm OC @ 1.4 with all of the voltages untouched.
[Fascinate Android Development] allcity187:
I've notice when I'm listening to music and when I unlock my phone the music skips and the sensors seems like it's not working. What governor are every one using?
[Fascinate Android Development] sageDieu:
Was playing with NSTools last night, enabled deep idle and live OC and things. It seemed to be all working well. I went to sleep and when I woke up the phone was off (showed the battery thing or whatever) and when I turned it on, all of my preferences were deleted and a bunch of apps were force closing (google+, tapatalk, gallery, etc) and that has been happening all day. Trying to avoid a data wipe and having to start over as it reminds me of the issues with /datadata being full. It's just annoying... has anyone else had anything like this/knows how to fix it?
[Fascinate Android Development] kuronosan:
Funny enough, my BLN works even when using the ICS buttons fix.

edit: You also may want to consider the ICS bar at the bottom... it looks cool and everything but at the lockscreen it blocks the EMERGENCY CALL BUTTON.

Stable and good thus far.
[Fascinate Android Development] nmalready:
http://xdaforums.com/showthread.php?t=991276

For anyone experiencing lag I would highly recommend installing v6supercharger script. I'm using the update 9 rc4 version and super-unleaded setting and it really, really helps. For one thing I rarely have anymore launcher redraws and the browser is significantly faster/smoother now.

It seems to me in ICS the browser caches much more ram than any previous version of android and this script helps optimize ram management thus freeing more available memory for the browser and home launcher ect. You can test this by installing an app that shows available ram in the status bar and watch it really drop to almost nothing when you open a large page (like theverge.com) in the browser. Unfortunately ICS was designed for phones with more ram than the fascinate has, so adjustments to multitasking need to be made and this where v6supercharger seems to help.

Someone smarter than than me can please correct me if I'm wrong about this. Just observation.
[Fascinate Android Development] tripacer99:
Lost modem functionality on 3.0.8 kernel. Not sure why, just randomly lost it while browsing reddit and it hasn't come back. Tried a cache/dalvik wipe, reflashing modem, battery pull...nothing. A flash back to v14 2.x fixed it.

EDIT: Also, when flashing the GB bootloader, do we check the "Phone bootloader update" box or not? Always best to be a bit paranoid when it comes to things like this.

EDIT 2: Seems the v14 2.x kernel only temporarily fixed it; had the modem die again. It went from full 3g, to 0-1 bars, to 1x, and then died completely. How strange. A reboot fixes it, but who knows for how long.
[Fascinate Android Development] allcity187:
No, don't check "phone bootloader ".
[Fascinate Android Development] jmac9:
Too much christmas cheer last night and not having bricked my phone in a long time.....I went ahead and dl'd this and flashed without really looking at what I was flashing (like I said, still drinking last night). I was on MIUI 12.23.11 with glitch v13. Got stuck at the samsung logo. Tried a battery pull and the three finger salute......couldn't get to recovery. tried Odin.....couldn't get past kernel, (Froyo ED05 and pit file in proper places) then it would either go green screen or just sit and sit and sit. Long story short, I quickly got the old BB storm activated for my line and can't try anything until I get home tonight. Any suggestions? Oh and the first ODIN I was scrambling a bit and ODINd just a modem with the pit file......it succeeded but I realized what I had done and didn't boot. So I'm confident the phone is being recognized....just can't get it to complete the froyo dwnload.
[Fascinate Android Development] ssewk2x:
Lesson #1: don't drink and flash.

If you can get to download mode and odin recognizes your device, you can recover.

1. Take out your battery. Yes, do this.

2. Plug your usb cable into the computer, but not your phone yet.

5. Three, sir.

3. With your phone battery out, hold the volume down key on your phone, and with it held down, plug the USB cable into the phone. Phone should come alive and straight to download mode. If it doesn't, go back to step 2 and try a different usb port. I know this sounds odd, but your phone must be able to power up with only the USB and no battery in order for the odin flash to actually work.

4. Odin a stock, fully bloated, official ROM. Let odin do its thing until your phone powers off on it's own.

5. with your phone off, unplug the usb cable from the phone and pop the battery back in. Boot your phone. It will take a while and you might see done scary things. Let it do its thing, it'll be ok. You might have to reboot it and let stock recovery do some stuff, too. Just play along.

6. It will eventually come up with your bloated stock ROM. It will probably take a long time, especially at the Samsung logo. This is normal.

7. Lucky 7. Do the stuff you have to to get your aosp install back. Also, don't forget to re-activate your phone. Blackberry sucks.

Good luck.
[Fascinate Android Development] jmac9:
Yeah....lesson one is the key! Been using ODIN for long time but this time it just didn't want to download the ROM. I'm good on all up to #4. Hoping when I get home, I see what I was missing last night. Will try a fresh stock rom and see if that helps. I tried about 4-5 times last night and just couldn't get past the kernel stage of the dwnload. Thanks for the response.....and can't beleive I used to think the Storm was a great phone!
[Fascinate Android Development] ssewk2x:
I've found a few times that there's just something magical about a full stock ROM. Maybe it's the stock recovery that I've seen come up and do something with the partition table...but it seems to always work when nothing else will.

Again, good luck.
[Fascinate Android Development] sarkozy:
Six, I know you guys are debating adding the voodoo color module back into the kernel pending a better understanding of the color values. I've been using this on my nexus s and it's dead on. Side by side with an actual GN there's no perception of a color difference.

http://xdaforums.com/showthread.php?t=1401759

NEW Voodoo Color Settings! Looks great on ICS or GB
[Fascinate Android Development] sixstringsg:
I agree with you, I want to keep the Voodoo Color in. We've had Voodoo Color values in the FAQ for months, and still for months, nobody even reads the FAQ, and complains about it. The biggest issue is people aren't smart enough to raise their minimum brightness to get over the green flash when it gets too dim, or to change their gamma values. The issue is not a lack of information, but a lack of will to find the information. Also, each device has a different quality screen. At one point I had two Fascinates, two Captivates, and a Nexus S side by side, all set at the same Voodoo Color settings and brightness. Only one of them looked good at that preset, I had to tweak the others' values to get them to look good.
[Fascinate Android Development] ssewk2x:
Hey everyone.

So I've been running my latest test kernel (12/25) for a few days now, and I think I'm ready to cautiously claim victory over the phantom key pop issue.

Not only have I seen zero phantom key pops, but also haven't seen any indications of then in my dmesg output. I'm fact, no activity at all has shown up there that wasn't directly related to either bln events or actual key presses. I have not even once seen output from my band-aid code intended to filter them out.

My 12/25 Christmas Test kernel is the first and only one to exhibit this degree of .. fixedness? So could some of you maybe give it a shot yourselves and hopefully confirm my results? Or if you have been running it, please post and let us know.

Thanks :)
[Fascinate Android Development] GizmoDroid:
Haven't been in a low signal area much, but I can confirm that I have had zero phantom keyboards, or touchkey loops since you posted it.

Congrats!
[Fascinate Android Development] knoxjon:
I've been running it. I did have some phantom backpresses at one point, but I rebooted it and haven't seen it since. Can't recall if I cleared any caches. I've found that the last few of your test kernels did a lot better after an extra reboot. I don't know why, but I wonder if it somehow clears some sort of cache or setting.

On the last test kernel, I had no phantom popups, but when I hit a really bad spot (same grocery store as usual), I could tell that the phone was struggling. Instead of popping up, it kept freezing as if it was using all of it's strength not to mess up.
[Fascinate Android Development] millwood:
Will run the 13. 1 for a few days and see how it does. The true test will be the GPS on the way home from vacation. That is where I really noticed it.
[Fascinate Android Development] k_nivesout:
Same here, haven't been able to test it out in a low signal area where the phantom presses really seem to manifest, but I haven't had any issues so far. I was wondering if there were maybe 1 or 2 individual phantom presses, but I can't say for certain that it wasn't just my finger brushing against one of the keys. Haven't yet run into the issue where it repeatedly hits or long-presses back/menu.
[Fascinate Android Development] Deliquified:
Will this code be merged into V14 for the ICS kernels? I still get phantom pops occasionally on ICS
[Fascinate Android Development] ssewk2x:
That is the plan, as long as it actually does the trick.

---------- Post added at 03:43 PM ---------- Previous post was at 03:35 PM ----------

Ok, good. At this point, I'm really only interested in reports from the latest test kernel, since I know already that the previous ones still had the issue in some form. But, I do appreciate your information nonetheless :)

As far as the "struggling" you mentioned, that might be (at least sort of) what it's actually supposed to do. I can see that happening if you have things like background data going on and the signal is in and out. In that situation, it will naturally use more CPU because of having to retry the transmissions more often and stuff. As long as it doesn't dump you out of your app or pop up your keyboard / menu / search / home screen and stuff like that, then I think its safe to say it's no longer interfering with the touch-keys. Does that make sense?

FWIW, one of the mis-configured GPIO pins I found and hopefully fixed for the latest test kernel was named "PHONE_RESET" something or other .. I don't know if that's a line to reset the radio (as in "phone" vs "pda") or reboot the whole system, but .. I'm sure the way it was before wasn't helping the device's stability any, LOL.
[Fascinate Android Development] neh4pres:
unfortunately hthe tower near my home is broken. there is signal but there's no data traveling on the carrier waves. No phone. No text. No data. therefore I cannot test for popups in the "golden zone" where i always get them..
[Fascinate Android Development] GizmoDroid:
Ssewk2x:

Did the latest test kernel lose in call volume adjustments?
[Fascinate Android Development] ssewk2x:
Crap .. No, but I did move them. You'll need to download the latest call volume script from my drop box and replace yours with it.

Here's the link: http://db.tt/5ObITpV

Look for the files under /sys/devices/virtual/misc/wm8994_call_audio (i think)
[Fascinate Android Development] jmac9:
All good again. Will hold tight with v13 for awhile.
[Fascinate Android Development] GizmoDroid:
Thanks! Knew something was up when i tried to order food for delivery unsuccessfully.
[Fascinate Android Development] Bubbadogg14:
Been running v14 2.x version for about a day and a half now solid as a rock for ICS. live OC and deep idle are activated. I have no seemingly no lag (it does happen sometimes) and I have noticed battery life to be better thus far. I used nstools to OC to 1400 and -50 uv across the board with no random reboots so far (knock on wood). Thanx glitch team ICS glitch was def my best xmas present this year (next to my earthkeepers lol)

Sent from my SCH-I500
[Fascinate Android Development] shag_on_e:
I've been testing the hell outta this one...so far no popping or backing out since Christmas. This is truly great man, this along with new features to play with on V14 is super cool. Thanks fellas!

~~~~There is no spoon~~~~
[Fascinate Android Development] stalls:
Sorry I might be stupid but can we get a better explanation of this? :p
[Fascinate Android Development] droidstyle:
The 12/25 v13.1 test kernel borked my gps...flashed back to your 12/12 and gps is great. I did notice the data handoff is improved on the 12/25 tho, also no phantom pop ups.
[Fascinate Android Development] beray5:
The DEV will correct me where I am wrong.

It was inter-related, the "fix" was originally for call volume problem - Pre-ADC incoming processing signal too weak, incall signal boost compensation/normalization required (pre-amp level).

incall signal boost also lessen final output amplification levels, reducing excess spurious interferences causing false keys/touch-sensitivity.
[Fascinate Android Development] AaronCompNetSys:
All I want for Christmas is some BLN...

I as well noticed the data was much improved, as well as the volume script being changed. But I'm also getting SODs.

I appreciate all the hard work, thanks guys.
[Fascinate Android Development] neh4pres:
I did also, only thing that would fix for me is reverting to v13
[Fascinate Android Development] millwood:
Been running this now to about 18 hours or so. So far everything seems to be running better, no SOD, no GPS problems, No Data issues. I have not checked the Volume issue and I do not know how to update the script so if anyone can help in that manner it would be great. Thanks to everyone.
[Fascinate Android Development] knoxjon:
I have been seeing more SODs, too, but they mostly went away after I turned off screenstate scaling.

The biggest issue I'm having is that my battery life has gone way down. I'm not sure if that's kernel related (or related to turning off screenstate scaling?) or if I've done something else stupid. Anybody else seeing poor battery life?
[Fascinate Android Development] ssewk2x:
I just tested gps on my phone with the 12/25 kernel, and i got insta-lock and great accuracy. Things to try:

1. Re-flash the kernel.

2. Toggle gps off and on under the settings menu. Do the same for network location services and accept the agreement thing that pops up.

5. Three, sir!

3. Cut down the tallest tree in the forest with a herring.

4. Bring me a shrubbery.

Good luck. ;)
[Fascinate Android Development] ssewk2x:
Yes.

It really didn't have anything to do with the key pad. The keypad issue was, i think, due to some gpio pins that are also used by the radio and were not configured properly.
[Fascinate Android Development] ssewk2x:
I had made the call audio and Mic gain boosts configurable by sysfs files. I had originally made that a part of the interface for voodoo sound, thinking the voodoo doing guys would want to incorporate it into their stuff. But .. That was months ago, and they've shown zero interest. So, since i don't want to corrupt their interface, i moved it out of voodoo sound into its own place.

does that help?
[Fascinate Android Development] GizmoDroid:
I'd love to see it integrated into the Glitch app given that it already has a gui set up for adding it in easily.

If no one else is up for coding it, I am.
[Fascinate Android Development] neh4pres:
After flashing v13 to rid myself of sod problems, its greatly apparent just how good ssew's fixes are I'm riddled with radio and pop up problems now.. Thanks for everything
[Fascinate Android Development] ssewk2x:
See, this is where I fall on my face and fail as a dev. I have never written an app before, and I'm not even really sure where to start - it's a whole new world for me. I'm much more comfortable screwing around in the kernel, lol!

I'd sure like to learn, though .. time just hasn't permitted that lately. Maybe someday.
[Fascinate Android Development] sixstringsg:
It'll take smasher less that five minutes to add it to the Glitch app, since we have almost identical stuff already unless you want it as a separate app as well.
[Fascinate Android Development] GizmoDroid:
My thoughts exactly. I'd love to see it in there.
[Fascinate Android Development] k_nivesout:
FWIW, the only SOD problems I've run into seem to be due to too much undervolting at 100mhz. Bumped up the voltage and haven't had an issue with it since. I'm on the latest (12/25) kernel, but I've been using all the test kernels and this has held true for all of them. In other words, I don't see where the latest kernel has a SOD issue.
[Fascinate Android Development] knoxjon:
Still on the test kernel, and I just had a SOD a few minutes ago. Not using 100mhz at all.
[Fascinate Android Development] GizmoDroid:
This link is dead, btw.
[Fascinate Android Development] ssewk2x:
Yeah, I'm in the process of making it part of the kernel, so you won't need to download it separately.
[Fascinate Android Development] GizmoDroid:
Awesome. :cool:
[Fascinate Android Development] fstbusa:
Yes I went from getting 1-2% loss per hour to over 3% per hr on the test kernel.
[Fascinate Android Development] joon82:
This rom have asian language installed?
[Fascinate Android Development] sixstringsg:
This isn't a ROM.
[Fascinate Android Development] kuronosan:
Six, any plans on reformatting the screen so that the emergency dial button isn't covered by the ICS buttons?

Also, on ICS, I seem to be randomly losing data and I wonder if it has something to do with roaming or not... modem is acting kind of funny (using the 2.x kernel).

All in all I'm quite satisfied with what you guys have churned out thus far. :)
[Fascinate Android Development] sixstringsg:
The ICS button thing is ROM, not kernel.
[Fascinate Android Development] kuronosan:
Odd. It wasn't there until I installed glitch. Wonder how to make it go away....

Sent in an Ice Cream Sandwich from my SCH-I500.
[Fascinate Android Development] tripacer99:
Can this (v14) be flashed over jt's and teamhacksung's new ICS build?
[Fascinate Android Development] xain713:
yes i was using it on build 3 seemed to be ok, well the 2.x v14 that is
[Fascinate Android Development] sarkozy:
Generic question. Has anyone with a Fascinate successfully gotten Deep Idle to work without the phone spontaneously rebooting when the screen turns off?
[Fascinate Android Development] Tk-Glitch:
Yes. I know at least two.
[Fascinate Android Development] sarkozy:
You didn't mention that earlier. ;)

(lol, i kid. nice to know i'm not beating my head against a brick wall though)
[Fascinate Android Development] droidstyle:
It works for any ics build for the fascinate...
[Fascinate Android Development] sixstringsg:
But we only support Team Hacksung ROMs.
[Fascinate Android Development] sarkozy:
Well after further review, it seems to be working now. It actually went into Deep Idle mode for a bit according to NS Tools. Maybe I need to stick to ROMs JT compiles himself instead of using my own. :rolleyes: