yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] ssewk2x:
Nice! I still have yet to see one, though I have seen the "scancode out of range" message in dmesg output. The difference is it didn't get translated to a keypop later on. So I guess that was a fairly effective strategy. I just wish I knew what the root cause of it was .. this feels more like a band-aid solution.

Just out of curiousity, what is your max clock speed / voltage set to? I wonder if it's happening when it stays at higher clock (and therefore higher voltage) for a while? Something it would probably need to do when working extra hard to find a spotty data connection or something...actually, this information would be helpful from everyone who's been getting these phantom keypops.
[Fascinate Android Development] shag_on_e:
I mostly keep my clock at 1.4 with-100 all around on LL and get the pop ups at two or less signal bars. But on the latest, it hasn't happened once. Fingers are crossed!

~~~~There is no spoon~~~~
[Fascinate Android Development] neh4pres:
1300mhz at -75 is my max for daily use. Never turn it up unless I'm doing something like restoring all apps or something from tibu.
[Fascinate Android Development] ssewk2x:
Ok, good. I've been running 200 - 1500mhz with -50mv across the board for a while, and it's been pretty good. However, I switched to your same scheme of -100 at 1000mhz and down, -75 above 1000mhz, and I seem to be running stable for the last couple hours at medium leakage. So thank you!

Still no phantom keypops, so hopefully I've at least masked the problem pretty well with this latest test kernel. Digging through the code, I can barely tell wtf is actually supposed to be going on, let alone finding something obviously wrong beyond what I've already patched up. So .. I think if everyone is happy, I will leave it like it is and see about getting it into the next revision. The team and I will need to figure out what exactly that entails.
[Fascinate Android Development] CHANGiism:
I'm afraid to tell you that the phantom presses are coming back to me stronger than ever. Well, I shouldn't say stronger than ever... it's acting the same way as the stock v13 release I should say. Menus popping up and apps exiting like no other. Happened with high leakage and happening still with medium leakage. I removed all the uv for the moment so let's see how that affects it.

Running CM7 kang, latest test kernel. I'm not in the worst signal area either. JFYI.
[Fascinate Android Development] ssewk2x:
Crap. Ok, back to the drawing board, i guess. At this point, i wonder if it's a buffer overflow or something, and I'm just moving stuff around a little bit and getting lucky now and then with where it all lands...
[Fascinate Android Development] droidstyle:
I switched to high leakage from medium leakage today and still have not had any phantom keyboard popups... no overclock running -50uv acroos the board w/ 100mhz step disabled.
[Fascinate Android Development] k_nivesout:
Unfortunately the problem has cropped back up for me too, seems to be effecting back, home and menu. It was doing it right before I started this post, it was strange, I hit menu then it kept long pressing home by itself. I would hit back to back out of the recent apps and it would do the same home long-press again, did this like 3-4 times. I don't know that I've seen it have that repetitive behavior before, it seems to usually be more random.

I'm on RickS 12.9 MIUI, running default frequencies (and everything else) with a -100 UV. For whatever reason though, the latest kernel is much better with the phantom presses than the 12/14 kernel.
[Fascinate Android Development] droidstyle:
Started getting the keyboard popup shortly after the last post. Had to turn the screen off and back on... This is on high leakage. Going to try low leakage now and see what happens.
[Fascinate Android Development] Jazz848:
Testing different voltages, will post any results. Just a thought in the meantime though: while rare, I only seem to get the phantom keys while running XDA. Just puttin it out there...
[Fascinate Android Development] xain713:
I recently flashed back from ics and have not had any phonying presses, of to 1300 UV 100 and set min to 200 UV by 150, I'm also useing kick ass kernelizer, and v6 supercharger if that effects anything. Also at work on break so can't reply xD. Just thought I say something it might help perhapes lol, uh and on latest test kernel and on miui also on HL
[Fascinate Android Development] stalls:
I have been having a few pop UPS for back an menu button as well.. Had it on 3 - 1 bars of signal. Also the screen would sometimes stop coming on but u can feel the phone still operating an hear it. Had to do a reset. I was also in MN while roaming.

I'm on the latest test kernel an running CM7 stable on a mesmerize.

low leakage

no OC

UV is -200 at 100 mhz an a step up for each other.

ondemand an deadline.
[Fascinate Android Development] GizmoDroid:
I know you are getting lots of reports from people about the touchkey issue, but I thought I would throw in my 2 cents as well:

I live in a decent reception area, so the few times I have the issue, it is almost always when I am sitting beside something that is blocking signal. When it happens when I'm running Opera, it manifests itself as me suddenly having all my browsing screens closed and I'm sitting at the opening page. It doesn't exit the program, but if I click on anything on screen or try to type, it immediately un-does whatever I'm trying to do. Weird part: it doesn't exit out of Opera.

If I'm in the XDA app when it happens, it will actually close the app. If I launch into another app, it will exit out of it as well. Weird part: Unless I open Gmail. It functions just fine.

Now if I push any touchkey or cycle the screen on and off, then it breaks out of the loop and allows me to resume my previous activities.

That all being said: the latest test kernel has been running for nearly two days and I've not had this happen. I've had a few cases of what felt like random touchkey events, but unlike before, they did not continue indefinitely (which in my book is a huge improvement!)

Anyway, I just thought I'd get super descriptive since there is a lot of people throwing around words that might mean different things than want I mean when I say "touchkey issue" :D
[Fascinate Android Development] millwood:
Not exactly sure that this will offer any insight, but I will out it in hers anyhow. My wife and I both have Fascinates. Until Tuesday she had been running stock Touchwiz on her phone ans has had non-stop phantom key touches. She has even had the phone replaced 4 tines because Verizon cannot get them to stop. I put RickS 11.25 MIUI on it Tuesday and it is running with "less" phantom touches, but is not completely resolved. I am running the same exact setup with the same exact apps and I might get one or two phantom touches a week. She easily gets multiple a day, but it has improved. Sadly she will be getting g a new phone Monday. Verizon finally is sending her something different as she is frustrated and missing calls and text messages.

So in a nutshell, two phones same exact setup very different outcomes. Her phone has always done it even when stock.
[Fascinate Android Development] neh4pres:
Hmm. Wonder if it is a gingerbread issue with the phone. when i was on dj05 which i ran for months because it was perfect, phantom issues were not even in the vocabulary.
[Fascinate Android Development] ssewk2x:
Just out of curiosity, has anyone experienced the phantom key presses on jt's kernel that comes with cm7? If I can find a source tree that we know doesn't do it, then that would be a good place to start looking for differences...
[Fascinate Android Development] droidstyle:
I can flash it and test it for a day. Also I have not had a phantom key on med leakage or low leakage, but had it happen twice on high leakage. On the home screen the keyboard started popping up. If I hit the back key it would go away then pop back up until I powered the screen off/on.
[Fascinate Android Development] ssewk2x:
That would be great, thanks. I'll see about comparing internal voltages between the two.

Does anyone remember getting the phantom keys on a version that didn't have configurable leakage?
[Fascinate Android Development] sixstringsg:
Yes, the issue was still present.
[Fascinate Android Development] k_nivesout:
Hm, something weird happened over the night: my fully charged phone was just sitting there while I was sleeping, I woke up and discovered it had turned itself off somehow, and it refused to turn back on until I pulled the battery and put it back in. Not an ideal thing to have happening since I use my phone as an alarm clock... I have no idea why something like that would happen and I'm not insinuating that it's a kernel issue, but the people in this thread tend to be knowledgeable so I thought maybe someone would have an idea as to why that would happen?

Regarding the phantom presses, I'm wondering if it might be more helpful to test out different leakage settings or to flash jt's kernel to see if it also has similar issues?
[Fascinate Android Development] sixstringsg:
ICS update: we are working hard toward an ICS kernel. Right now, the issue is that Team Hacksung still is keeping the aries-common repository to themselves, so we dont have some of the things that we need. Also, we will put out a V13.1 here soon with all of the screenstate patches and the phantom keypress work.
[Fascinate Android Development] fstbusa:
I've had this happen also. Running CM7 nightly and a test glitch kernel. I just hold volume up and power until it reboots.

Sent from my SCH-I500
[Fascinate Android Development] shag_on_e:
I do believe I still have just about every kernel jt has put out, but since I live in a low signal spot this happens to me often, and even jt's have done it since way back. I'll see what I can dig up.

~~~~There is no spoon~~~~
[Fascinate Android Development] neh4pres:
Yes. This had been a issue long before v13
[Fascinate Android Development] droidstyle:
I jusg flashed jt's 3 finger fix kernel. Ill report back!
[Fascinate Android Development] androidmichael:
what is everyone's I/O scheduler and governor choice on these latest builds?

Ive got deadline and smartassV2 going and its great!

Only dislike with this kernel is the instability of bln! I love bln a lot and it sucks having em sketchy and not consistent
[Fascinate Android Development] Tk-Glitch:
@ androidmichael

The upcoming tiny update will get rid of it to get back the CM7 stock implementation. It'll be stabler for everyone this way.
[Fascinate Android Development] sol_671:
i got a question that I've been meaning to ask, why does this kernel drain slower when in use compared to touch wiz kernel like KGB, but drains alot faster when on sleep (nothing is waking it up) no wake locks. No sleep governor active. Would the sleep governor active help it, tried it out but see no difference.
[Fascinate Android Development] sixstringsg:
That's how anything Cyanogenmod for Galaxy S is, and it's due to proprietary software that Samsung does not give us.
[Fascinate Android Development] ssewk2x:
I'm sort of hoping that will change soon, now that cyanogen works for samsung, but I'm also not holding my breath.
[Fascinate Android Development] sixstringsg:
Anyone in here with apache experience that would be willing to help?
[Fascinate Android Development] ssewk2x:
Six, with the thread-kill, lol!

What are you wanting to do with apache?
[Fascinate Android Development] sixstringsg:
Virtual hosts to host two sites through one dedicated server with a single IP.
[Fascinate Android Development] thatbenc:
Try this:

Listen 80

# This is the "main" server running on 172.20.30.40
ServerName server.domain.com
DocumentRoot /www/mainserver

# This is the other address
NameVirtualHost 172.20.30.50

<VirtualHost 172.20.30.50>
DocumentRoot /www/example1
ServerName www.example1.com

# Other directives here ...

</VirtualHost>

<VirtualHost 172.20.30.50>
DocumentRoot /www/example2
ServerName www.example2.org

# Other directives here ...

</VirtualHost>
[Fascinate Android Development] sixstringsg:
Doesn't that only work for if you have two IP address's though? I only have one.
[Fascinate Android Development] thatbenc:
It works with one IP. You don't even need to necessarily specify the IP address:

NameVirtualHost *:80

<VirtualHost *:80>
DocumentRoot /www/example1
ServerName www.example1.com

# Other directives here

</VirtualHost>

<VirtualHost *:80>
DocumentRoot /www/example2
ServerName www.example2.org

# Other directives here

</VirtualHost>
[Fascinate Android Development] sixstringsg:
And I'm putting this in sites-available, then enabling it?
[Fascinate Android Development] thatbenc:
That should work on a Debian based server. I normally put it directly in httpd.conf or in an include file. Run the command below to validate the syntax before you restart:

httpd -S
[Fascinate Android Development] skynet11:
Well, thanks to thatbenc, IT'S ALIIIIIIIIIVE! I wouldn't be surprised if he's the only one in the forum that knows enough about it to help six :D

Has anyone seen John Connor?
[Fascinate Android Development] ssewk2x:
Indeed. Mad props, sir. I'm going to file that away for future use myself. :)
[Fascinate Android Development] droidstyle:
Running jt's 3 finger fix kernel for almost a day now with no phantom keys.
[Fascinate Android Development] GizmoDroid:
Just for the record: approaching 3 days with the last test kernel, with only 1 home key long-press loop @ 1.3OC/-50UV/HL
[Fascinate Android Development] neh4pres:
I almost never get phantoms anymore
[Fascinate Android Development] sspgoolsby32:
I miss my BLN :(
[Fascinate Android Development] sageDieu:
ssewk2, I'm on ICS now... phantom pops are worse than ever. on glitch if it happened at all it would just be the keyboard or menu popping up once or twice. Nothing bad. On this (no glitch of course) it is like it presses the back and menu buttons a hundred times; the phone vibrates over and over, everything backs out, the menus pop up and down... it's awful. You've spoiled me. . can't wait for glitch to support ics.

Sent from my ICS SCH-i500
[Fascinate Android Development] droidstyle:
I never had any phantom keyboard on ics... Your phone must be having a seizure lol.
[Fascinate Android Development] neh4pres:
Quick! Someone get his phone something to bite down on.
[Fascinate Android Development] sageDieu:
it only has happened so far in the office of my school, which is surrounded on all sides with foot-thick concrete blocks and steel. I get no bars, I was trying to browse xda and my phone freaked out on me. :P

Sent from my ICS SCH-i500
[Fascinate Android Development] neh4pres:
Will glitch be playing with the galaxy nexus in the future?
[Fascinate Android Development] sixstringsg:
Neither me nor Tk-Glitch are planning on getting the Galaxy Nexus. I do not know about ssewk2x, but I haven't heard him talk about it.
[Fascinate Android Development] k_nivesout:
This really eases the sting of not being able to upgrade til July. I'd love to have the latest and greatest, but when I think about it realistically, I don't have any valid reasons to shell out hundreds of dollars for a new phone yet. It's just good to know that (hopefully) this phone will be supported a bit longer.
[Fascinate Android Development] ssewk2x:
I don't plan on upgrading until one of the following happens:

1. I win several million dollars in the lottery. I never buy tickets, i figure my chances are about the same.

2. Verizon gets their heads out of their assess and brings back unlimited data.

5. Three, sir!

3. Sprint's network gets a heck of a lot better / comparable to Verizon's, AND they still offer unlimited data.

4. My Fascinate explodes or becomes otherwise permanently incapacitated, forcing me to buy a new phone. Me getting frustrated and using the thing as a very expensive clay pigeon is not entirely out of the question at some point. I have a really nice shotgun, too...

Tl;dr - I'm not going anywhere any time soon.
[Fascinate Android Development] nmalready:
So what phone would you guys switch to? I'm a developer stalker. I can't help myself this kernel is sooo hot :D
[Fascinate Android Development] k_nivesout:
Awesome. This is some good news. :)

Also, sixstringsg - gave you your 2000th thanks.
[Fascinate Android Development] shag_on_e:
This eases my mind too...I'm so hopelessly addicted to Glitch it ain't funny. I refuse to rock anything but Samsung, but I played with the Nexus and was shocked to see no HDMI out support. Anyway, my unit will remain Glitch powered till it melts down or Samsung pumps out something else.

~~~~There is no spoon~~~~
[Fascinate Android Development] Tk-Glitch:
These days I'm thinking about asking the community when I'll be done with the SGS. Note that I won't buy anything Nvidia and Qualcomm SoCs aren't that fun to play with in there actual state. I'll jump the dual core ship as well. So all in all, don't expect me to move before an OMAP or Exynos quadcore chip is available in a well built phone. That should keep the SGS Glitch alive for some time still. And there's obviously room for improvement :)
[Fascinate Android Development] ssewk2x:
Yeah, I'd also like to add that I will flat-out refuse to buy a phone that comes with a locked/encrypted bootloader, or anything else (beyond the threat of a voided warranty) that would prevent me from doing pretty much whatever the hell I want with it. Mind you, I don't mind having to jump through some technical hoops to unlock a phone like we all have to - I'm saying I won't buy one that isn't un-lock-able, or that I have to rely on the manufacturer/carrier to decide to "allow" me to unlock my own device (or decide, on a whim, not to, i/e: HTC).

Are you listening, pretty much everyone except Samsung?
[Fascinate Android Development] sageDieu:
this, my friend does development for his Droid x and it's so frustrating to him all the hoops they have to jump through for roms and stuff. It's so much more complicated to dev for and to fix if you mess it up.

Sent from my ICS SCH-i500
[Fascinate Android Development] neh4pres:
Yea. Don't think i need a new phone. But when i play with something like the gnex at a store i get all excited. But I'm also disappointed that its not as bleeding edge as our phone was. It should have the best of the best. supercurio's tweets tell me they messed up the headphone amp. And no hdmi out? Wtf.. Does anyone know if it supports video out through the 3.5 jack? Still waiting for a phone i can mirror on my dvd deck in my car.

Idk. All in all. You guys, jt, andmer, sbrissen, have made this phone so good that I'm not sure I'll move
[Fascinate Android Development] sendan:
I'm pretty sure all newer Samsung devices support 1080p video out through the micro USB port. I remember reading all manufactures would be using this technology eventually, but I can't find the article.
[Fascinate Android Development] j00manji:
does this kernel support third party batteries? (like the one from the Epictouch 4g)
[Fascinate Android Development] neh4pres:
What about the headphone jack though? I have composite inputs on my dvd player in my car. Would be great to mirror navigation to it while playing Pandora
[Fascinate Android Development] sixstringsg:
The kernel really shouldn't care what battery you put in your phone as long as it provides the same voltage.
[Fascinate Android Development] k_nivesout:
The nexus supports MHL through the USB port, not through the headphone jack. That said, this isn't a nexus thread and isn't glitch-related whatsoever, so would probably be better discussed in the proper forum/thread.
[Fascinate Android Development] CHANGiism:
Ssewk2x and others, about the data losing connection after being exposed to low signal and never connecting back. I have a friend who has a HTC DHD with CM7 and he has an exact same issue. He would lose connection and would have to turn the airplane mode on and off like us. I honestly thought this issue was only on our phones but it's not. It may be an issue with all aosp roms. Just throwing it out there.
[Fascinate Android Development] neh4pres:
New information on that issue.. I'll try to find the article again. But its probably on verizons end because of their implementation of 4g. It seems Verizons towers are failing to verify our devices, then our devices are failing to attempt to retry.

Edit http://www.androidpolice.com/2011/1...other-4g-lte-vzw-phone-is-losing-data-signal/

Realize the article is about 4g. But seems very familiar.
[Fascinate Android Development] ssewk2x:
Well, now .. that IS interesting. Guess what I'm going to be looking at for the next hour and a half .. :-p

Edit: Oh .. GAWD .. my BRAIN! Owwww
[Fascinate Android Development] neh4pres:
Did jt's gps fix get removed somehow? I'm back to the Old days crap gps again.. Running newest ephosis test.
[Fascinate Android Development] sixstringsg:
It's CM7 based in believe, so you're fine.
[Fascinate Android Development] cyonsinn:
Awesome so I'd use voltage control to oc / UV?
[Fascinate Android Development] sixstringsg:
That is correct.
[Fascinate Android Development] Bubbadogg14:
Yeah u r ok I used glitch with omfgb for awhile but I went with tsm pool party once they updated it 2 v1.3 n now I'm hesitant to try out the new Omfgb build cuz I like pool party a lot at the moment
[Fascinate Android Development] Eris _2.1_2010:
What's this tsm pool party you speak of?

N/M I found it on rootzwiki.
[Fascinate Android Development] jbr05ki:
Pool Party is great. TSM Parts ftw.
[Fascinate Android Development] ssewk2x:
So I finally got around to doing my build. Fixed a few oopsies and got things ready.

And the fscking sensors STILL don't work. ARGH. I flashed JT's 9/12 kernel, swiped the libraries out of it, put them so they end up in the exact same places .. and nothing. I have an app called Elixir that lets me read the values coming from the sensors, and the accelerometer ones don't give back any values at all. Well, here's a summary of what seems to be working and what doesn't:

Torch works!

accel, linear accel, gravity, rotation, orientation are all borken. All but orientation give no reading at all. Orientation gives all zeros.

Light sensor reads either 6 lux or 5000 lux. It does not seem to work with auto-brightness, though .. I'm not sure if it should or not. I'll have to flash JT's kernel and see if it looks any different.

Proximity sensor works. At least it reads correctly. Unknown if it "works" while in a call or not.

Neldar's BLN seems to be successfully integrated. Woot!

Colors look pretty snazzy. Of course, I've fiddled with my voodoo color settings, so ..

I'm going to get lunch now, then do another build with printk enabled so I can get some dmesg output on things. Maybe I can figure out what's going on and fix it by hand...

Also, the logcat I took on a fresh reboot was just about empty and useless. I did turn it on in recovery, too.

The ROM I'm using is the last CM7 nightly that was successfully built before all the **** hit the fan with kernel.org

Anyone who might be able to point me in the right direction, please feel free to do so. I feel like I'm soooo close, yet so far away.
[Fascinate Android Development] akellar:
I've never been able to get a valid logcat on Glitch either, FYI. And yes, I enabled it.
[Fascinate Android Development] sixstringsg:
I'm probably going to start building (once the repo is fixed) kernels with debug stuff enabled, because there are a couple of you that have been asking for it. Those of you that need it can PM me, so that I can know what leakage you want, that way I don't have to do 30 kernels each release.
[Fascinate Android Development] akellar:
No worries on my side for this. I don't even remember why I was trying to get one, just know that it never worked. I'm sure it's important for someone though. :)
[Fascinate Android Development] ssewk2x:
Just found something from jt's sensor commit that got nuked from mine. What is BMA023? It is enabled in jt's build, but got shut off in mine.

When I get back from lunch, I'll get another build with it on, then we'll see...