yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] sspgoolsby32:
Greatest Of All Time, of course.
[Fascinate Android Development] 123SIT:
Ok, wasn't sure about the flashing and unless the timeout is longer than 15 minutes, not timing out is also confirmed as well.
[Fascinate Android Development] ssewk2x:
Yeah, I checked the code, too, and I see where it won't shut off the lights if they're on because of a notification event. So .. I guess it works as coded, if nothing else ;)
[Fascinate Android Development] shag_on_e:
Yep, BLN patch works like a charm! I've never been one to care much about BLN, but we're one step closer to perfection!

~~~~There is no spoon~~~~
[Fascinate Android Development] Azuma73:
V13.1 is very nice indeed, Thanks fellas!!

Got it all set up, made a nice clean backup, now I believe I'm gonna check out V14 and this ICS business. So if I do full wipe(big 3), flash build #12/Gapps V7 and boot up, then flash V14 I'll safely be able to check out the Hype?

Just as long as I can re-Odin(if necessary) and Flash my backup if things go awry, I'm cool with that!

Is Glitch V14 gonna get it's own thread? Just wonderin'?

--Kudos once again guys!! Can I get a "golf-clap"?:D
[Fascinate Android Development] sixstringsg:
We might end up making ICS and GB threads, but not V14 specific.
[Fascinate Android Development] Azuma73:
Right on!!
[Fascinate Android Development] cesium:
Is 13.1 supposed to have deep idle?
[Fascinate Android Development] sixstringsg:
ten characters
[Fascinate Android Development] AaronCompNetSys:
Well it is so much better than the screen coming on when fully charged, remember that? Thank you for your work, I appreciate it and my BLN works great now.
[Fascinate Android Development] sixstringsg:
Everyone that likes LED notifications, re-download the kernel and re-install. I uploaded a newer one, but didn't change the file name so I wouldn't have to update all the links in the forums. This is the result of ssewk2x's work.
[Fascinate Android Development] ssewk2x:
And credit to tk-glitch for clue-ing me in on where to look.
[Fascinate Android Development] k_nivesout:
What MIUI are you guys running that got BLN working? I'm not getting the LED menu, I tried just redownloading the kernel and flashing it, didn't work, so then I flashed the patch (which probably did nothing) and still nada. Tried reflashing MIUI 1.12.9, then glitch 13.1, and still not getting the menu.

EDIT: I'm an idiot. It doesn't need to be configured, it just works automatically.

Also, I don't want to be a killjoy or anything, but the phantom presses aren't eliminated with 13.1. I was in an area with less than ideal signal earlier today and the phantom presses made the phone essentially unusable. In areas where signal is more stable though, it does seem much improved from where it was on v13, although I'm not sure if it's any better than ssewk2x's test kernels.

Thanks to tk-glitch, sixstringsg, and ssewk2x for all the work on this kernel and the support!
[Fascinate Android Development] GizmoDroid:
I'm pretty sure that there was no more changes done to that part of the kernel after the latest test kernel, so that makes sense.

With that being said, been running since Christmas with only 1 key press.
[Fascinate Android Development] pntballer505:
Haven't seen BLN work in quite some time.

Thanks for the fix!
[Fascinate Android Development] schu9120:
FYI This bln fix works with Pool Party 1.6 . Thanks gang :D
[Fascinate Android Development] droidstyle:
Bln is working! Thanks team glitch, your guys great work is what keeps me content with the fascinate! A+
[Fascinate Android Development] rmtobler:
soooooo happy with BLN working. i am content with my current setup until ICS MIUI gets up and running :D
[Fascinate Android Development] nklenchik:
Holy ****, everything just FLIES on v13.1. If someone told me a year ago I'd be on 2.3.7 and everything would start with no lag whatsoever I'd be like, rightttttt haha.

Is anything happening with glitch for gb after 13.1 or you moving to ics development?
[Fascinate Android Development] sixstringsg:
This might be more detailed than you wanted, but oh well. While there is a demand for it and it doesn't require an unreasonable amount of work, releases will come out for both GB and ICS. That being said, Tk-Glitch runs ICS, as do all of our testers. That means that we are focused on tweaking the performance on that now
[Fascinate Android Development] sageDieu:
Speaking of ICS... Is anyone else having sync issues? Figured I'd ask here before reporting a bug... I'm on the Mesmerize build 3, glitch pre4, gapps v7... my contacts and gmail sync are both broken. I get random gapps force closes, and none of my contacts will download. Every couple of hours my messaging force closes while I'm texting someone, and when I open it again my messages are all deleted. Not really sure what to do to fix it though, idk what the problem is exactly. Just wondering if anyone else has had this issue..

Before you ask, i have tried flashing gapps fixer, newer gapps, reflashing rom and fixing permissions, Nothing worked.

I'm posting this here because I am running the preview 4 of Glitch 14, and nobody has had any answers in the rom threads. It's just such an odd problem.
[Fascinate Android Development] ssewk2x:
Ugh, dammit! I've been running since Christmas, also in very weak signal areas (like my basement) and I haven't had a single sign of phantom keys since I made those fixes. I've been looking for them, too. So I'm not sure what the heck is going on with you guys ...

One thing I did do was to fully power off my phone and pull the battery at some point that day. It's a slim possibility that doing that might help. I think I ended up having to odin something and that's why I did it .. but, if you're one of those people who, like me, leaves their phone on all the time, then doing that might help to reset some flaky internal stuff that I don't know about.

Other things that might help along the same lines:

Just for giggles, Odin the EH03 modem.bin, and be sure to use the power off, batter out method for getting into download mode. Which reminds me, what modem version are you guys using? I've been on EH03 .. maybe that has something to do with it.

Also, a few very minor things changed between 12/15 and V13.1. Here's what I can remember off the top of my head on half a cup of coffee:

1. BLN back to stock CM7, now working with the patch (and I still hate it, BTW).

2. Took out the detailed debug code that was in 12/25 and I warned everyone about.

3. Removed most references to the F word. Added a few references to the S word.

4. Vandalized Glitch's boot logo slightly.

5. A few other minor changes to the touchkey code from upstream - should help eliminate potential race conditions, lockups, things like that.
[Fascinate Android Development] knoxjon:
I had a few phantom popups, too, although yesterday I installed ICS. I don't know why, but I think you are right that resetting the phone once every 24 hours made your fixes "stick." I didn't do the battery pop, tho, and that might be better. FWIW I am on a mez running EH09.
[Fascinate Android Development] sarkozy:
No issues here, but I'm on a Verizon Fascinate.
[Fascinate Android Development] GizmoDroid:
Well for me, the 1 key press I had was on the last test kernel, and it was just a couple phantom back keys. It broke out of the loop really quick. Before your fixes, it wouldn't stop until I toggled the screen or mashed the touchkeys a few times.

As far as I'm concerned, the phantom keypress deal is squashed on my phone. I'm currently running the latest 13.1 release, and I've seen no issues with it, either.

As for people still having issues, would the bootloader in anyway affect anything (my memory is bad, and it's been a while since I knew what the bootloader does)? Anyway, I'm running the GB bootloader. EH03 modem. I average a reset about every 2-3 days.
[Fascinate Android Development] shag_on_e:
I live in the country, so there are a few spots with bad signal, and unfortunately the pop ups are still there. I get a dmesg log every time it freaks out and the whole log is cypress touchkey interruptions. I've followed installation procedure to the "T" and I'm also running the EH03 modem and GB bootloaders. I've been holding out to see if they came back for anyone else to avoid placebo affects. I guess this one is gonna be a tough cookie, but I definitely appreciate the work you guys do. This kernel is a must have for me.

0: recovery_routine: recovery_routine

<3>[ 453.332123] cypress_touchkey_driver 10-0020: touchkey_interrupt_thread: scancode 0xffffffff is out of range

<3>[ 453.428396] cypress_touchkey_driver 10-0020: recovery_routine: recovery_routine

<3>[ 453.430056] cypress_touchkey_driver 10-0020: touchkey_interrupt_thread: scancode 0xffffffff is out of range

<3>[ 453.526043] cypress_touchkey_driver 10-0020: recovery_routine: recovery_routine

<3>[ 453.528429] cypress_touchkey_driver 10-0020: touchkey_interrupt_thread: scancode 0xffffffff is out of range

<3>[ 453.628245] cypress_touchkey_driver 10-0020: i2c read error

<3>[ 453.629394] cypress_touchkey_driver 10-0020: recovery_routine: i2c transfer error retry = 9

~~~~There is no spoon~~~~
[Fascinate Android Development] ssewk2x:
I just noticed something .. you're actually getting an 'i2c read error' message .. I've not seen that in any of my dmesg output, even from when the keypops were relentless on my phone. This leads me to wonder if you might have a different (hardware) problem of some sort. It looks to me like your touchkeypad is actually dying at the hardware level for some reason. That is very odd indeed.
[Fascinate Android Development] shag_on_e:
That's definitely no good! I'm gonna try going back to stock, and go hang out in one of my notorious bad signal spots. I have never tried stock to see if indeed there is hardware defects. Thanks man, I'll report back in a bit.

~~~~There is no spoon~~~~
[Fascinate Android Development] k_nivesout:
While I don't live in the country, my setup is pretty similar. I've been on the EH03 modem since I've been running glitch, and I'm assuming I'm on the GB bootloaders since I odin'd the full EH03 package before flashing AOSP MTD. I reboot fairly often, every day or two, sometimes more, although I rarely pop the cover off and do a battery pull. Rebooting does seem to "fix" some things though when the phone is acting up, I was using GPS the other day and it was all janky, not showing my location accurately, and after a reboot it started working as it should.

Glitch is also a must for me, I can't really imagine not using it even with the occasional issue here and there. If there's anything I can do as far as debugging the phantom presses, let me know. I'll try to grab a dmesg next time it happens. Although I should say I do have to almost go out of my way to get it to really freak out with the phantom presses. When it happened yesterday, it was in an area where signal seemed to be weak and switching from 1x/3g. Fortunately 95% of the time, I'm in areas with decent signal.
[Fascinate Android Development] hazard666:
I tried 13.1 on the latest CM7 Kang nightly and my home and back buttons had the functions reversed, I was unable to get signal, was unable to mount my sdcard in recovery and button functions were discombobulated (in recovery). Is this normal or did my download corrupt and I should retry it? I'm kind of weary because to get my phone back to a working state I had to ODIN the EH03 package.

E: Holy ****.....yeah....I downloaded the wrong device file. It's been a long day.
[Fascinate Android Development] Azuma73:
Alright, which am I supposed to use for ICS build? :confused:

I tried flashing build 2, then build 3 over that(as instructed) and quite frankly, it didn't seem that "special"? So I thought for sure I had flashed the wrong one, kinda freaked out, went to my CM7/Glitch V13.1 backup, And it's all good!

I just wanna make sure I got the right builds and such for Verizon Samsung Fascinate!?!?!

I got-[ROM][ICS][IML74K] teamhacksung's ICS Port for Fascinate (BUILD 3)

and-[ROM][ICS][IML74K] teamhacksung's ICS Port for Galaxy S (BUILD 12)

I'd assume that it's the Build 3 'cuz it's for Fascinate? However in the OP it says use V14 with build 10 or higher? So, could someone please clarify for me? :confused:

And please don't rip my soul out, I ain't got much left????:o
[Fascinate Android Development] sixstringsg:
Build ten is for normal devices, not the Fascinate. Galaxy S and Captivate are in build 12 now. You're using the right one.
[Fascinate Android Development] Azuma73:
Cool, thanks for the clarification!

So I can just flash build #3, boot and flash V14 via updater app or CWM?
[Fascinate Android Development] sageDieu:
right. You will also want to flash gapps and any battery mods as well in that first recovery session. You don't need to boot unless it makes you (if you are on mtd already it shouldn't force a boot) so you can flash all the stuff at once without booting.

Sent from my ICS SCH-i500
[Fascinate Android Development] sageDieu:
been catching log cats and things, fixed everything except Gmail by flashing an older gapps. Gmail force closes still, getting an odd sqlite database IO error. strings/ssewk2x/whoever, would that be a possible kernel issue? if maybe then I can get you a logcat but if not then I'll take this back into ics threads. I'm only here because it started after flashing glitch.

Sent from my ICS SCH-i500
[Fascinate Android Development] shag_on_e:
Well, I flashed back to EH03 yesterday and hung out in my bad signal zone for about 2 hours and didn't have any issues. I opened a bunch of apps and started downloads to put a strain on data and besides going slow everything seemed fine. Who knows... :-\

~~~~There is no spoon~~~~
[Fascinate Android Development] joshkoss:
Yea Google apps issues is rom related. I stopped using build 3 cuz of those issues you mention. I believe it will be fixed in newer releases of ics.
[Fascinate Android Development] BTownTKD:
Running Glitch 13.1 (Fascinate) and CM7 Kang from another thread. My computer will not detect my phone when I plug the phone into USB, and vice-versa; the phone does not recognize that it's been plugged into a computer. It just displays as "charging."

It's not a Windows driver issue, as it doesn't even get far enough to "detect new hardware."

Has anyone else experienced this?
[Fascinate Android Development] nklenchik:
Do you have usb debugging enabled? Usually resets when you flash a new rom
[Fascinate Android Development] droidstyle:
This is not kernel related, better off posting in the q&a section. That being said make sure your usb debugging is turned on and try a different usb cable.
[Fascinate Android Development] sageDieu:
I fixed all of my issues by doing a data wipe and fresh install of everything. Been running everything with no issues all morning.

Sent from my ICS SCH-i500
[Fascinate Android Development] sageDieu:
I know it's off topic and might not even work for you, but what I do in ICS which doesn't have USB mass storage yet is reboot into recovery, go to mounts and storage, then mount USB at the bottom. As long as you're in that screen it should mount to your PC.

Sent from my ICS SCH-i500
[Fascinate Android Development] bigwilly90210:
Just installed over build4. I'm assuming those Universal Mass Storage fixes are at the kernel level and installing glitch v14pre4 just trashed them? I didn't even get a chance to try it out yet, but I will when it reboots. Just curious. Also the build4 buttons mods work with glitch v14pre4 and build 4 too. It's gonna be so hard giving up this phone man... :(
[Fascinate Android Development] sixstringsg:
If you're a web developer and want to help out, shoot me an e-mail. I'm looking for an interface like this here: http://fitsnugly.euroskank.com/skankwich/crespo/ where it gives a landing page to things uploaded via FTP, with download counts, etc.

Thanks,

Six
[Fascinate Android Development] dreamsink98:
I curious if the phantom ring is still showing up in v13.1 . Also wondering how well roaming works. I have a mesmerize through my work and I travel between states so roaming is kind of a big deal for me. Thanks!
[Fascinate Android Development] ssewk2x:
I don't know about roaming, but I have gotten the phantom ring issue once since running the latest kernel.
[Fascinate Android Development] stalls:
I am on the newest US Cell radio Ei20 an will hopefully travel here soon to check it out..

But back to the latest kernel it is great thanks guys.. I have had a few phantom calls as well lately an noticed my batt is dieing alot faster then normal on this recent kernel. Anyone else havin the same issues?

Oh ya Im on CM7 an latest 13.1
[Fascinate Android Development] nklenchik:
What are you guys using for your sleep governors? When the screen's on I'm using smartassv2...kinda wanna save some battery when the screen's off.

Should I do powersave?
[Fascinate Android Development] droidstyle:
I use conservative for screen off.
[Fascinate Android Development] ssewk2x:
I would try, in order, smartass, conservative, and maybe powersave. I bet you will find that conservative saves the most battery.
[Fascinate Android Development] Azuma73:
I found conservative to be most efficient!! But hey, that's just me!!
[Fascinate Android Development] Holliday:
Still having some bad radio issues with v13 on my Fascinate. Just looked at my radio and I am on ED05. Thats pretty old isn't it? :)

Any recommendations on which one I should upgrade to and a download link? Would really appreciate it!

EDIT: Nevermind, I found a newer radio. Going to give this one a shot and see how it works out.
[Fascinate Android Development] nklenchik:
Not odd...radios work depending on location, really. I'm on EC09...gives me the best battery life/download speeds.
[Fascinate Android Development] sageDieu:
Is there any reason the OP shows preview 3 for v14? I've got preview 4... just want to make sure I don't have something that got pulled as it seems to be the cause of a bunch of issues I've been having with sqlite databases and IO errors...

Sent from my ICS SCH-i500
[Fascinate Android Development] sixstringsg:
Because I can't type. Those links point to pre4, just not their displayed text.
[Fascinate Android Development] Holliday:
So I am playing around with EH03. Insta-lock GPS now. Wifi tethering turns on the first try now(used to error out) . Even 3G latency seems much lower and consistent! I feel like I have a new phone.

Navigation was useless for me before.
[Fascinate Android Development] k_nivesout:
Had a random phantom keypress today, it was strange cause it happened at my house with good signal where it's been incredibly rare that I experience the issue. Pulled a dmesg right afterwards, I'm not sure if there's anything helpful in there.

http://pastebin.com/Ek2TyFJi
[Fascinate Android Development] droidstyle:
Dang it!!! Not what I wanted to hear....although I have not had any since the latest 13.1 release. I do wipe cache and dalvik weekly, wonder if that has anything to do with it...probably not?
[Fascinate Android Development] sageDieu:
heh, k. well my major issues with gapps, sync, contacts, apps force closing and everything seem to be glitch... when I run beta 4 I have all of those issues mentioned. I've talked about it before. But right now I'm not using glitch, and not having those issues. It's the only thing I did differently after playing with miui and having to Odin back, I just didn't flash glitch and have had none of those issues...

Sent from my ICS SCH-i500
[Fascinate Android Development] Tk-Glitch:
I have none of your issues flashing 30 different buggy kernels a day so I think this is more complex than that ^^ But well, this is still not even beta stuff.
[Fascinate Android Development] neh4pres:
I also get phantom pops.. Although, if you flash an older glitch kernel. You will see how drastic the fixes for it are. I rarely get them on 13.1.
[Fascinate Android Development] ssewk2x:
Yeah, the end of your pastie has a metric frackload of phantom key interrupts. No indication of what's causing them.

If you want the latest info on this issue, tho, take a look at https://github.com/Efpophis/Glitch/issues/9 ... just to get an idea of how crazy things are getting.

I still have yet to have one incident since Christmas, too. Although, I did briefly switch from using launcher pro to using ADW launcher, which resulted in all sorts of craziness / instability on my device (no phantom pops, but a few random reboots, lockups, wonky colors, etc) .. I have no idea if that has anything to do with anything at all, but I suppose there's a small chance it does.
[Fascinate Android Development] neh4pres:
Did you freeze the stock launcher?
[Fascinate Android Development] Bubbadogg14:
A gut instinct told me to check ftp root for some new ics glitchy goodness and to my excitement there it was!! Haven't flashed it yet but thanks in advance guys. I can't use a stock like kernel anymore u guys spoil us to much.

Sent from my SCH-I500
[Fascinate Android Development] Tk-Glitch:
The new builds are up, just get them from the server til Six updates the op : http://androtransfer.com/tk-glitch/CM9-kernels/Glitch/
[Fascinate Android Development] droidstyle:
preview 5 just bootloops at the samsung logo.
[Fascinate Android Development] jtommyj:
+1:confused:
[Fascinate Android Development] 123SIT:
Same here, had to try so you guys wouldn't be alone lol.
[Fascinate Android Development] sageDieu:
Same for me, odining back.
[Fascinate Android Development] sixstringsg:
I have updated the Changelog, but I am not updating the OP until we get the bootlooping issues fixed.
[Fascinate Android Development] sageDieu:
Cool beans, you know who to call if you need testing on any of it. Couldn't get any logcats obviously since it didn't even get to the second samsung logo.
[Fascinate Android Development] GizmoDroid:
I've found the source of the phantom key press issue, the new boot loop issue, and every other bug we have:

Gremlins.
[Fascinate Android Development] sendan:
So evil...:eek:
[Fascinate Android Development] ssewk2x:
I had not done that, but I did clear defaults, select the desired launcher as the new default, and reboot...wouldn't that keep the other launcher from launching?
[Fascinate Android Development] ssewk2x:
Here I thought it was those gorrham reavers...
[Fascinate Android Development] GizmoDroid:
You never can tell...
[Fascinate Android Development] neh4pres:
Maybe.. I never trust Android to not randomly start apps. But i use adw ex. And don't have any more or less issues than with stock. And 13.1 its almost absent where it was horrible for me for the entire time prior to your fixes no matter the launcher. And i used to run miui. And am now on pool party, and can't stand the stock launcher of boredom it has. Lol. So i use adw
[Fascinate Android Development] nklenchik:
Looking at the changelog, does preview 5 improve colors like voodoo color? (I'll flash when the bootloops are fixed haha)
[Fascinate Android Development] sixstringsg:
No.

10char
[Fascinate Android Development] dallas6672:
I've been noticing a hit to my battery also. CPU Spy was showing a lot of time outside of Deep Sleep and it seemed to do it only with a Wifi connection (don't have service on the Fascinate so I can't say if Data would have the same effect). I tried everything and the only thing that worked was going back to v13 RC1.
[Fascinate Android Development] k_nivesout:
Hm, I would do that but the phantom key press issue is *vastly* reduced in the latest kernels and that's a little bigger priority to me. I'm not sure what sure what would have changed in between v13 RC1 and v13.1 that might have resulted in increased battery drain though? I don't know enough to fully interpret the changes in the source.
[Fascinate Android Development] knoxjon:
I'm on ICS now, but I just switched a few days ago. I am pretty sure the battery drain is connection related, but I couldn't nail it down. I had double the battery life on my phone when I just stayed at home all day within one wifi zone vs going to work and switching wifi and 3g throughout the day. At home, I went probably 6 hours on 25% battery. At work I usually have to charge only because it makes me feel better, but with the test builds I had to charge after 6 or 6 hours just to keep my phone alive.