yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] k_nivesout:
Thanks, I'll have to give that a shot. And the thing with the settings was weird to me because the exact numbers you had actually weren't available to me. I've tried out other peoples settings and have been able to dial it in exactly with some patience, it's just that those numbers weren't an option in my settings.

Other than that, the screen settings look pretty good to me, I'm gonna have to dial it in a little bit to get it to my tastes but it's good. And with changing that setting in advanced display options, I've been able to avoid the green screen when dimming. It does crop up occasionally, it'll flash green for a second when turning the screen on, but since it's so quick, it's something that I can deal with. Plus I just can't get over how god damn smooth the phone is with this kernel, even underclocked to 800mhz! Just awesome awesome work by the glitch crew, I love it, and the prospect of glitch ICS is exciting to say the least.
[Fascinate Android Development] neh4pres:
Welcome to my world. :p
[Fascinate Android Development] ssewk2x:
I saw the phantom-keyboard bug this morning, but by the time I thought to take a logcat, the relevant data was gone. I guess I'm going to have to just sit with my phone hooked up to adb all day and see if I can catch it live. Stupid bug.

Meanwhile, if anyone else is quicker on their feet than I am, please feel free to PM me a logcat of the event. I'll see if I can at least find where it's coming from.
[Fascinate Android Development] neh4pres:
cool.. You will probably need to get the start of the event. After that whatever variable changed in usually constant until a screen lock/unlock. I have had a multiple (one after the other) repeated bug. But it is less common and usually involves the "back" button instead of the long press "menu" button
[Fascinate Android Development] GizmoDroid:
You need to grab one of those debugging programs that you can dump the logcat to the sd card with the push of a button.
[Fascinate Android Development] ssewk2x:
So I just took a look at the driver code again, and compared it to the stuff Samsung released with their Gingerbread kernel. I noticed that, in particular, the interrupt handler code was way different, and possibly in a way that would cause ours to allow static or something to trigger false key-presses. Very interesting. So, without attempting to understand a whole lot about ever single line, I've just copy-pasted (that's pronounced "kanged") the relevant samsung code into our driver.

Now I just have to figure out a way to build and test since I left my computer off at home.
[Fascinate Android Development] sixstringsg:
The famous "will it boot" moment. I would build for you, but mine's off as well. I need to figure out how to do wake on LAN in Ubuntu...
[Fascinate Android Development] neh4pres:
if you would like me to test it ( sense I'm plagued with it at home) shoot a pm at me.
[Fascinate Android Development] sageDieu:
I've used this guide for my ubuntu-based minecraft and web server.

https://help.ubuntu.com/community/WakeOnLan

Sent from my MIUI SCH-i500
[Fascinate Android Development] stalls:
Ya i can as well i get it ALL the time. Thanks guys ur help is better then most peoples customer service!
[Fascinate Android Development] ssewk2x:
I'm building a fascinate version in an ubuntu vmware session right now.

Six, I did have to update the manifest again. Upstream added some stuff and broke it.

Heh, I could possibly make a VMware appliance for building glitch .. that would be fun.

EDIT:

Ok, I have it built. I'm running it now and first impressions are that the keypad seems a little more stable. Everything still works (i/e: all the touchkeys do what they're supposed to when you hit them) the same way it did before, including BLN (which I did not touch).

I think I'll just go ahead and post a link here: http://dl.dropbox.com/u/28682151/Glitch-kernels/CM7Fascinate-Glitch-DEV-20111206_1359.zip

This is a build from my latest experimental branch. If you're afraid of what that entails, then don't flash it. It's Glitch V13 (Verizon Fascinate and compatible only) released version with the following changes:

1. Experimental new cypress touchkey / touchscreen driver hacked together moments ago.

2. The same stuff I released Waaaaay back when in the screenstate scaling patch file. If you flash this kernel, you won't need to re-flash that patch.

5. Three, sir!

3. Some recovery fixes and enhancements:

a. backing your voltage settings up to the SD card should work

b. compatible with new VC file names

c. screenstate sleep governor lets you pick any governor available

4. You might get a slightly different glitch logo - the release may have been built with the wrong one. This is for sure the right one straight from Tk-Glitch himself. Personally, I didn't see a difference visually, but the source files are definitely different, lol!

I only want to hear reports about items 1, 2, and 5 (Three, sir!) 3 .. and really only item 1. This is a build that's for helping me test and debug, it is not an official release or release candidate or beta or alpha or anything even remotely like that.

Happy testing :)

EDIT again: realized I had screwed up the change list, so fixed that and added gratuitous Monty Python references.
[Fascinate Android Development] shag_on_e:
I love you man

~~~~There is no spoon~~~~
[Fascinate Android Development] Dj-Dubster_TN:
3 sir! lol luv'd that, but everything seems to be smooth sailing so far with this :) no keyboard popups and whatnot, keep it up
[Fascinate Android Development] neh4pres:
I will do what i can tonight.. If i need to turn my directional antenna so its not directly at the Verizon tower i will. If i can't produce messed up things with the touch keys then i don't believe anyone will.. I Crosses fingers. Let you know tomorrow.
[Fascinate Android Development] PhoenixPath:
...and again, not 24 hours can go by without me flashing *something* on my phone.

I'm amazed this thing still works*.

*Using a variable definition of "works".

EDIT: I always get the phantom button presses on the way home from work...not today after installing your experimental.

Could be coincidence, but I honestly don't recall the last time I made that trip without the button presses annoying the crap outta me...
[Fascinate Android Development] GizmoDroid:
The v13 release logo had a different shade of black on the top then the bottom. It was the first thing I noticed :D. Tk-glitch confirmed that it was accidental in the IRC.

The new logo is definitely the one you want to go with, and it looks much nicer. Thanks!
[Fascinate Android Development] shag_on_e:
Bummer :-(. As soon as I got in a low signal area apps started backing out like crazy. I wasn't able to get a logcat-bummer #2, but I'm ready now, as soon as I can get to a low signal zone, I'm on it. Y'all rock.

~~~~There is no spoon~~~~
[Fascinate Android Development] neh4pres:
Having a bad signal night because of fog. Had to go outside and wipe water off the antenna because a text would not send.. But not a single soft key glitch. If i don't get one at all tonight, it will be a huge coincidence or this fix worked for me.. Time will tell
[Fascinate Android Development] sageDieu:
I usually get them while driving, I just drove for about 15 minutes to my girlfriends house with no problems.

Sent from my MIUI SCH-i500
[Fascinate Android Development] shag_on_e:
Two is enough for me to completely reflash/wipe/start fresh. What sucks is I won't see a low signal zone until tomorrow. No problamo, it's worth the effort!

~~~~There is no spoon~~~~
[Fascinate Android Development] stalls:
So far it is not near as bad.. Honestly the phone operates a lil different an lol I'm so used to the back button goin back so far it kills the app. Now I'm like what, this thing is normal lol :)

yes it still happens to have the back an menu button still go off every once an awhile.. :( but not near as bad. I think ur on to something here
[Fascinate Android Development] stalls:
Also 2 other things every once an awhile the 4 bottom buttons will jus stop working all together.. So I'll jus hit the power button an cycle the lock screen 1-2 times an it works fine..

Other thing is I'll be doin something an the phone will jus go black screen an not do anything at all.. have to pull the batt every time.

Sorry an this was on official release of v13 an the latest button fix test release
[Fascinate Android Development] Dj-Dubster_TN:
Awww, well on poolparty 1.6 everything was great with the devbuild,but now on miui its running rampant again,can barely use my phone
[Fascinate Android Development] neh4pres:
Well. Had some pop ups and back outs with the fix. Didn't seem nearly as bad. But that could be a placebo effect. Thanks for the effort. And the soft keys do seem more responsive.
[Fascinate Android Development] ssewk2x:
Yeah .. I think I'll keep the changes, but also keep working on it.

My phone just went positively bonkers, and I was able to view some of the events live in logcat and in dmesg. Sadly, there was no useful information there. Something is causing the hardware itself to register events when it shouldn't. So I don't think the problem lies in the software that listens to the hardware. Rather, I think it's an issue with the software that configures the hardware in the first place. Maybe something like what Six suggested - a bad voltage or bad GPIO pin configuration somewhere.

I did notice that the stock samsung code uses a completely different driver for the touchscreen (not the cypress keypad) than we do. Since the two interact, it's entirely possible that something is going on there.

I'll keep looking as I get time.
[Fascinate Android Development] sageDieu:
It's happened to me when my phone got moist around the buttons before. Obviously physical there, but that could be why you aren't getting anything from logcat.

Sent from my MIUI SCH-i500
[Fascinate Android Development] Jazz848:
That sounds... dirty.
[Fascinate Android Development] ssewk2x:
Bow-chika-bow-wow
[Fascinate Android Development] sixstringsg:
Hey ssewk2x, did you know that the script writer of the screenstate scaling said that it doesn't help battery? People are funny.

http://xdaforums.com/showpost.php?p=20088871&postcount=2160
[Fascinate Android Development] ssewk2x:
Hahaha I'm pretty sure i wrote that comment. Since i fixed the code, tho, it actually seems to save me some battery.

I'll have to clean up the comments in there, i guess ;)
[Fascinate Android Development] stalls:
What do u guys run for a screen scaling setting.. I have tried conservative an lazy.. Anyways seems like my phone is dying a lil fatter then normal.. Not gonna lie though I'm on it non stop prolly :)
[Fascinate Android Development] sixstringsg:
I know you wrote the comment, that's why it's funny :p
[Fascinate Android Development] sixstringsg:
Conservative is really the only practical screen off governor.
[Fascinate Android Development] stalls:
Now does that have problems when it has been setting for awhile in deep sleep an lets say u get a phone call an it takes awhile to wake up? Like it will ring but takes a bit for the screen to pop up..
[Fascinate Android Development] sixstringsg:
It shouldn't, no.
[Fascinate Android Development] stalls:
Hmm mine seems to every so often..
[Fascinate Android Development] ssewk2x:
I think that might have something to do with the wonky touchscreen / keypad driver, actually. But do try some other governors and see if any of them do any better.

Has anyone else been having problems with google navigation locking up and then haptic feedback getting stuck on? It's pretty consistent for me, so I'm going to see if i can figure wtf that's all about. I suspect it might also be related to the phantom keypad popups, so maybe tracking it down will give me some insight into that, too. One can hope.
[Fascinate Android Development] stalls:
Yes I did every time at first... Now its all good an stats right up without problems fore some reason. But yes the last 2 updates have been that way.
[Fascinate Android Development] shag_on_e:
I have been having problems with navigation. It only happens occasionally, especially if it's the first time opening navigation. It will let me close the app but haptic feedback keeps going. It happens on MIUI and CM7 for me, but since I only use Glitch I couldn't say if the packaged jt kernel does this. Team Glitch Rules

~~~~There is no spoon~~~~
[Fascinate Android Development] rmtobler:
Yes!! I even had that problem with JT's rom, so I figured it was a problem with MIUI rom only. It started with a miui update about 3 weeks ago before glitch was included in most versions. (it will be 4 weeks ago on Friday).
[Fascinate Android Development] neh4pres:
.i don't think so. I made a thread about that in q&a a few Weeks ago. If you revert to a earlier version of maps it will work again.

Edit: http://xdaforums.com/showthread.php?t=1352285

Google maps and nav.
[Fascinate Android Development] rmtobler:
Oh yea a newer version of maps did come out that same time frame I started getting the problems.
[Fascinate Android Development] fstbusa:
I have it almost everytime I use navigation. The only way to stop the haptic that I have found is to reboot the device.
[Fascinate Android Development] ssewk2x:
True dat. I grabbed a logcat this morning. It does look like an application issue. The app is trying to access some virtual methods that don't exist (anymore?). I have posted a detailed description to the google code forum related to apps and navigation, including my logcat.

Sadly, this doesn't help with the wonky keypad issue like I hoped it would.

A work-around I discovered yesterday, tho, is to start maps first, select your destination there, then launch navigation from within maps.
[Fascinate Android Development] stalls:
Maybe that's how I get it to work all the time meow
[Fascinate Android Development] neh4pres:
Meow? What the hell are you a cat?
[Fascinate Android Development] sixstringsg:
I got frustrated with merging for a minute, so I spent time to update the OP and changelog. Everything is now current.
[Fascinate Android Development] pntballer505:
With the excellence, speed, and battery life etc. of the Glitch kernel

combined with the perfected features in J'ts Kernel, I don't know if a kernel

could get much better than that!
[Fascinate Android Development] speedingcheetah:
I actually prefer not to have voodoo color since it seriously messes with the look of things. I am using JT's kernel the moment and the color looks perfect, but definitely miis the performance boost of the Glitch kernel. Anyway to get the Voodoo Color defaults set to the stock look or to what a non-voodoo color kernel looks like..
[Fascinate Android Development] sageDieu:
Play with voodoo color for a while and you will change your mind; it may look bad on its own but when you lower gamma settings and mess with colors you can get a much better look out of the phone.
[Fascinate Android Development] speedingcheetah:
There is nothing wrong with the stock settings. Samsung set them the way there were designed to look. But, then again, on a tv set, everyone can tweak the settings to adjust the picture to their liking.

I do agree that it is nice to be able to adjust the gamma and color settings, but it makes much more sense to have them start at the stock settings and let people tweak them from there.

I have spent many hours over many days tweaking the settings, but can never get back to the non-voodoo color look...like JT's kernel or just plain stock kernel.

It would also be made a bit easier if u could set profiles that u could switch back and forth to..like one I could set a boost in gamma for bright sunny days and one with lower settings for inside, dark rooms...

I would rather not have to fuss with the settings altogether since stock(non-voodoo color) kernels look perfect to me, but I have to deal with it if I want the other tweaks in the Glitch kernel. It would be nice if the settings would be set at stock values to start with or if there were a version of Glitch that did not have voodoo color. But that is just me and I'm not the one doing the work....so, yea.

I love the performance of Glitch and can deal with the color thing..not that big of a deal..much more important things to worry about.
[Fascinate Android Development] sixstringsg:
To be honest, we're not going to spend the time to make a non voodoo color kernel. Right now, for each release, we already make and upload 15 builds. That would take the number to 30. Voodoo color is also tweaked for accurate color, whereas samsung isn't. If "samsung set the way they were to designed to work" on everything, then you should be on stock froyo.
[Fascinate Android Development] calebv2:
I don't know why you want to go back to stock Samsung colors. Samsung colors have a blue tint to them. In JT kernel colors settings whites are whites and blacks are blacks etc. But to really fine tune it you use voodoo colors if you know what your doing custom voodoo colors look amazing compared to stock or even JT color settings. If you want to try my settings I'll post them.
[Fascinate Android Development] scarmon25:
Please do. I have had a time in a half finding settings tthat really work for me. Im.open to all suggestions
[Fascinate Android Development] calebv2:
- SRB multipliers:

Red ="3415521600"

Green ="3609817920"

Blue ="3773435840"

- Screen v1 gamma hack:

-37 red

-33 green

-36 blue
[Fascinate Android Development] scarmon25:
One.last thing. What do.you normally keep your brightness level at.
[Fascinate Android Development] calebv2:
i keep it in the middle
[Fascinate Android Development] scarmon25:
Thanks. Gonna try this in the AM.
[Fascinate Android Development] gawbage:
Alright, hopefully this will be the last time I have to explain this... What I want you to do is, with your current voodoo color settings, to go to your home screen right now.. Now click menu, click wallpaper and choose live wallpaper. Then I want you to select the galaxy live wallpaper and set it. Looks really freakin' crappy doesn't it? Well this because you are basically screwing over the contrast ratio of your Super AMOLED display. With the gamma hack, and your phone loses the ability to display colors as vibrant as before, and displays blacks (not perfect blacks, but off-blacks) with a slight greenish or orangish tint to them. This is because you've set your phone to emulate the contrast ratio of an LCD screen, which our Fassy don't have! What you should do, is reduce the gamma settings to the lowest possible settings to bring back the vibrancy and contrast that your display should be displaying. Not to mention battery savings due to the Leds being less strained. Here are my settings(you'll find that I compensated for the slight decrease in brightness by scaling my RGB settings):

SCREEN RGB MULTIPLIERS :

R:3947279360

G: 3834792320

B: 4131349440

GAMMA HACK:

R: -59

G: -58

B: -59

Now go look at the galaxy!!!
[Fascinate Android Development] sageDieu:
you realize everybodys phone is different with this... I do agree that the lower gamma settings look better but scarmon you should do your own RGB multipliers to get the best result for your specific device.

Sent from my MIUI SCH-i500
[Fascinate Android Development] scarmon25:
I planned on it. ;) I really just wanted a starting point.
[Fascinate Android Development] calebv2:
Very valid point
[Fascinate Android Development] sageDieu:
as an example, anybody else's rgb settings I try have too much red, when I do it I have to have like 100 less red and 50 less yellow than blue whereas most peoples' colors are relatively close together. My phone looks terrible on the default kernel; a lot of people swear by it and dislike voodoo color but everything is super washed out for me.

Sent from my MIUI SCH-i500
[Fascinate Android Development] cyonsinn:
sorry for the noob question but is voodoo control on a certain rom? cause i have glitch and no voodoo control or anything like that.
[Fascinate Android Development] sageDieu:
https://market.android.com/details?id=org.projectvoodoo.controlapp

the support for it is in the kernel, not the rom. you just have to install it from the market.

Sent from my MIUI SCH-i500
[Fascinate Android Development] cyonsinn:
Thank you. And is it ok to be using glitch with OMFGB rom? I know post #1 only says cm7/miui but it seems to be working and i was wondering if there was anything I should look out for
[Fascinate Android Development] ssewk2x:
Damn you, autocorrect!

Am I right?
[Fascinate Android Development] sageDieu:
I too have had the issue with the screen taking a bit to wake up during a phone call. Did some testing and it is for about 2-3 seconds, which equals about 1.5 rings on the default miui like old style ringtone. Then it wakes up fine. It's no big deal, haven't missed calls or anything because of it, just a minor annoyance.

Sent from my MIUI SCH-i500
[Fascinate Android Development] stalls:
do I look like a cat to you boy?! Am I jumping around all nimbly bimbly from tree to tree!? Am I drinking milk from a saucer?
[Fascinate Android Development] Jazz848:
CHICKENFUCKER!

/Bearfucker needs assistance
[Fascinate Android Development] Dj-Dubster_TN:
Or maybe he was watching supertroopers:)
[Fascinate Android Development] skynet11:
Alright, no need to start a catfight!

http://www.youtube.com/watch?v=vEtbfzMLVWU&feature=youtube_gdata_player

Has anyone seen John Connor?
[Fascinate Android Development] ssewk2x:
Hey everyone,

So I'm still working on that wonky touchkey issue. I would like to put out another unofficial "might drink all your beer" test kernel. I made a one-line code change since the last one, but it might be a Big Deal(tm) - it fixes an uninitialized variable that was being used to set the power-off configuration on the touch-screen. If you're a programmer, especially a C programmer, that should make you cringe, lol.

I've loaded this on my phone and it should be stable enough. I haven't been running it long enough to know for sure if it still has the phantom craziness problems, and I probably won't be in any weak signal areas to try it, so I'm relying on you guys, the awesome Glitch/Fascinate community, to help me test once again! Yay!

Here's the link to the Verizon Fascinate build:

http://db.tt/UMeXldLe

Thanks everyone!

Edit: fixed the link, I hope.
[Fascinate Android Development] GizmoDroid:
Thanks man, I'll give it a shot.
[Fascinate Android Development] sixstringsg:
And a mirror so we don't rape your dropbox: http://goo.gl/RBWf4
[Fascinate Android Development] neh4pres:
Was having bad popup and back out just before flashing.. Sitting in the same chair after flashing and nothing yet. Will know more with time.. Thanks for putting in the work. Much heterosexual man love for all of you.
[Fascinate Android Development] neh4pres:
Just had 3 haptic feedbacks followed by a keyboard popup. :(

Anyway. I would like to report another issue I have had for a long time in low signal areas.

When making a download or loading a webpage. It seems that if my signal gets interrupted for a instant my 3g will stall.. The arrows up top will not light up and usually unless i hit the home button and open up another app that uses internet (like news and weather and hit refresh) it will remain stalled. It happens all the time to me at home. And sometimes i have to invoke the internet in such a way several times just to get a Web page loaded. Any ideas what that's about?

I was doing that when my keyboard popped up.
[Fascinate Android Development] pntballer505:
I know this has been adressed before, but I'm curious.....

Am using v13 and the rgb and gamma settings from the op, but I still get the yellow screen when the backlight dims. Was that fixed in v13? Thanks.
[Fascinate Android Development] shag_on_e:
Go into settings/cyanogenmod settings/display/automatic backlight/screen dim level and change it to 20. 16 works for me, but I know for sure 20 does the trick'

~~~~There is no spoon~~~~
[Fascinate Android Development] pntballer505:
Thanks for the tip, but I think I forgot to mention

I'm on Miui.
[Fascinate Android Development] k_nivesout:
The menu is still there, go to your display settings, make sure it's set to auto, and you should see "advanced options", it's in there.