yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] kuronosan:
Interestingly enough I installed jt's newest build and like all the others there are no ics buttons.

Sent in an Ice Cream Sandwich from my SCH-I500.
[Fascinate Android Development] neh4pres:
I don't see v14 link in op. The one based on Linux 3
[Fascinate Android Development] sixstringsg:
That's because its not there.
[Fascinate Android Development] tweakymattman:
Update coming soon since jts new kernel?
[Fascinate Android Development] Tk-Glitch:
The problem is still the same : broken softkeys.

No update until this is fixed.
[Fascinate Android Development] k_nivesout:
I don't know if it's just my setup, some setting or app, but I was curious to see if anyone else has felt like the battery drain is increased on these latest test kernels? I'm still on gingerbread, BTW. Same rom (and apps, more or less) I've been on for a few weeks, but battery life seems to have taken a hit lately. Could be a variety of things, but wanted to see if anyone else had a similar experience?
[Fascinate Android Development] neh4pres:
Calibrate you're battery and see what that does
[Fascinate Android Development] sageDieu:
Well, after fixing all the weird problems I was having, everything runs great. I'm on ICS build 2 and glitch v14 2.x. Will be updating to build 3 of ICS when I get home from vacation. Thanks as usual for making my phone run wonderfully

Sent from my ICS SCH-i500
[Fascinate Android Development] nmalready:
Anyone else's phone intermitantly go into airplane mode after sleeping for awhile?
[Fascinate Android Development] tweakymattman:
Not to argue but I think the problem is more of the radio dying....
[Fascinate Android Development] knoxjon:
I am seeing this, too, and I don't think it's the battery stats. Seems like it's something to do with trying too hard to find a signal, perhaps? I will start with recalibrating the battery, but if there's anything else, let us know.

I'm not complaining, mind you. I am almost always near a charger. Just trying to do my part.
[Fascinate Android Development] big_limits:
Quadrant Question

Are Quadrant scores over 5000 not a norm? Been stable at 1600MHz and consistantly pulling quad scores over 5000. is it safe to leave it at 1600MHz or is there a good range to drive at.
[Fascinate Android Development] Deliquified:
You will severely degrade your battery life, and your phone will die quickly. IMO, it's pretty unnecessary to OC over 1200mhz. I usually do 200-1200mhz, undervolt going up from 200 as follows: 125, 100, 75, 50, 25. Running as deadline/ondemand. I've found that gives the best stability, but every phone is different. Keeping it at 1200mhz will give you a nice performance nudge while keeping your battery from draining fast.
[Fascinate Android Development] Monkeyzzzzz:
Yes, same here... Not even after sleeping, just randomly, but the airplane mode toggle is off, so I have to toggle it on then back off.
[Fascinate Android Development] nklenchik:
I'm on V14 for my kernel. Is voodoo color built into the system with the settings everyone use to recommend?

Also getting that weird color splash screen still on reboots :P not a huge deal, but thought I'd point it out. I'm on CM9 Build 3
[Fascinate Android Development] Tk-Glitch:
Fixed already.

Sent from my GT-I9000
[Fascinate Android Development] tweakymattman:
With the 12/25 build? Because I still have issues
[Fascinate Android Development] Tk-Glitch:
No, in the source of the 3.0.8 based kernel. The one with broken softkeys that won't be released til it's fixed.
[Fascinate Android Development] dave3588:
I actually dont mind soft keys being broke bc I actually like the ics button mod.
[Fascinate Android Development] dave3588:
Alright let's all move on. Can't wait for the v14 when the glitch team is ready to release! :)
[Fascinate Android Development] bigwilly90210:
can't wait for the rock solid stable release. Didn't work so well with my ICS Build 2 install so I'm a little cautious about installing it on Build 3. Might make a nandroid and try it out for fun. We'll see. Happy New Years everybody, btw. :D
[Fascinate Android Development] Tk-Glitch:
Good news for Fascinate users : I was finally able to fix this horrid dead softkeys problem on the 3.0.8 based Glitch kernel. You should get an update in a few hours with all the latest updates in.

Happy new year :)
[Fascinate Android Development] pntballer505:
Awesome, thank you so much!

I'm seeing talk about v14 using cm9.

I feel like a noob asking, but how can I acquire

cm9 for safe flashing of this kernel?!?!
[Fascinate Android Development] ssewk2x:
Oh, sweet! Did you get the 13.1 stuff i sent you?
[Fascinate Android Development] shag_on_e:
http://rootzwiki.com/index.php?/topic/11850-[ROM][ICS][IML74K]-teamhacksung's-ICS-Port-for-Fascinate-(BUILD-3)-[12/29]

~~~~There is no spoon~~~~
[Fascinate Android Development] droidstyle:
Just wanted to let you know that I believe the issue with gps was google maps for some reason... Everytime I flash to a different version of your test kernel, uninstalling/reinstalling google maps is the only way to fix the gps issues or else navigation FC's and keeps my softkeys lit...also no gps lock. Makes me wonder if its a issue with the latest update for gmaps.
[Fascinate Android Development] ssewk2x:
I've experienced the same issue. I reported it to google after learning that other devices and other roms completely different from ours. It looks like it's definitely a google maps issue.
[Fascinate Android Development] pntballer505:
Thank you!

So, does that mean Glitch v14 and further development

will not work on Miui? Don't really understand the CM9 only thing.
[Fascinate Android Development] sixstringsg:
If there is an ICS MIUI that uses the same kernel as CM9, then it is compatible. CM9 just came out first.
[Fascinate Android Development] pntballer505:
Okay okay, that makes sense. Gracias!
[Fascinate Android Development] Stephen.k.spear:
Miui v4 is out for nexus s I played with it but I don't think it is ready to port. Half of Ics features weren't working yet. Maybe in a few Weeks I'll try again.
[Fascinate Android Development] Tk-Glitch:
Glitch V14 Preview 4 for Fascinate :

http://androtransfer.com/tk-glitch/...nate/CM9-fascinatemtd-Glitch-V14-Preview4.zip

3.0.8 based kernel with all the goodies and even more (not yet added to the changelogs).

One detail, DIDLE has been removed on this one for now and will be added back later.

Softkeys are working.

For ICS only ! ;)
[Fascinate Android Development] shag_on_e:
Nice, more goodies!

~~~~There is no spoon~~~~
[Fascinate Android Development] knoxjon:
Glitch - does this build include ssewk2x's softkey popup fixes?
[Fascinate Android Development] ekowanz:
Which one more suitable for this v14... voltage control, setcpu, nofrills?

Sent from my SCH-I500
[Fascinate Android Development] sixstringsg:
Read the changelog.
[Fascinate Android Development] sageDieu:
I know it says in the OP that you guys will have a guide to explain Live OC and things eventually, but could you at least say what settings are good? I really have no idea how it works so idk what to set it at to make it be good.

Also, v14 preview is amazing. So much faster and smoother than the 2.x one.

Sent from my ICS SCH-i500
[Fascinate Android Development] AaronCompNetSys:
Pardon me if I'm jumping the gun while someone is resting, but maybe this is the release I've been waiting for?

Glitch Kernal 13.1 for CM7 http://androtransfer.com/tk-glitch/CM7kernels/Glitch 13.1/

I'm about to jump all over this with some new nightly Skank.
[Fascinate Android Development] ssewk2x:
Quite possible. Stay tuned....
[Fascinate Android Development] joshkoss:
:) ;) can't wait!
[Fascinate Android Development] sixstringsg:
Check i9000 general. Tk posted the link to it already, its been done a few days.

Define waiting for. It isn't a lot different that the last test kernel, but it is 13.1, I will update the thread shortly.
[Fascinate Android Development] stalls:
So this is the newest official kernel? Does this one have the Vol script all fixed again?
[Fascinate Android Development] sixstringsg:
Yes to both.
[Fascinate Android Development] sixstringsg:
Does the DC even have CM7? I don't keep up with it. Even if so, I doubt it will happen any time soon. I don't have time, Glitch is sick, and ssewk2x probably doesn't have time either.
[Fascinate Android Development] sarkozy:
Just FYI bud, you may want to try the kernel on the 1.9.9 MIUI build or sbrissen's TSM 1.3.(both coded with jt's newest compile) I'm not near my PC to confirm exactly what changed, but some people have had sensor issues coming out of their ass mix-matching older kernels with those ROMs and vice-versa.
[Fascinate Android Development] ssewk2x:
Yes, that's exactly what I'm trying to fix. :)

I can now confirm that in my experimental merge, the proximity sensor works as it should during a call. So there is some progress.

Just have to figure out why the accel sensors are still hosed.

Edit: ... And fix bln. Ugh :-p
[Fascinate Android Development] Eris _2.1_2010:
We are pretty close to having cm7, jt and a few others are working on it. I think radios are the only thing left to get working.

Sent from my Droid Charge 4G running Gummy Charged 2.0
[Fascinate Android Development] sageDieu:
yeah ive tried to get debug stuff working before and never had any luck. logcat reads out empty and dmesg would be either blank or not boot.

Sent from my MIUI SCH-i500
[Fascinate Android Development] sixstringsg:
I assume you turned logcat on?
[Fascinate Android Development] jt1134:
I'm not sure what device repo you're using for init/uevent files, but you'll need to make sure to use the latest fascinatemtd tree from cm, as I had to update device permissions for the new sensor drivers.
[Fascinate Android Development] ssewk2x:
Ha! I just thought of the same thing. I haven't synced in a long time. I'll give that a shot asap.
[Fascinate Android Development] sageDieu:
in both recovery and terminal.

Sent from my MIUI SCH-i500
[Fascinate Android Development] sixstringsg:
Well that's odd. It works for me. A limited logcat, but still a logcat.
[Fascinate Android Development] ssewk2x:
Yeah, it works for me, too. It just doesn't actually have much, if any useful info in it. It looks like only a few things realize it's on.

---------- Post added at 01:33 PM ---------- Previous post was at 12:35 PM ----------

<snip>

That was it, JT - you da MAN!

I now have a build with working sensors. Now I just have to figure out why BLN is being weird.

Neldar's BLN works fine on JT's kernel. On mine, with the screen off, the BLN lights only light up if you touch one of them, and not until that. It's like there's an interrupt or event or something that's not firing when it should.

I've been through the change sets and the files effected for the two commits that 1) revert the old BLN, and 2) add Neldar's BLN. All the code there is identical. I'm not sure at this point where else to look.

But, since BLN is fairly minor, and since you can now disable / enable it with the app from the market .. I will be sending Six the builds with the sensor and torch fixes shortly .. unless someone helps me fix BLN within the next hour or so, lol!
[Fascinate Android Development] sageDieu:
that is actually an issue on jt's current kernel that is still outstanding so it isnt a big deal if you don't get it.

Sent from my MIUI SCH-i500
[Fascinate Android Development] neh4pres:
Another thing jt fixed was charging with the power off. Im excited to see if it works. My battery needs a good calibration :)

Sent from a beautiful miui fascinate
[Fascinate Android Development] akellar:
On JT's kernel you have to boot from recovery for BLN to work. Give that a try.
[Fascinate Android Development] sageDieu:
confirmed from me as a fix too

Sent from my MIUI SCH-i500
[Fascinate Android Development] mtw4991:
Ok, this is gonna sound really dumb, but isn't this the Glitch kernel thread and JT's kernel is a whole other beast? The reason I ask is I need to update my daughters' Fascinate which I haven't done in over a month and I'm not sure about whether I should use Glitch v12 HL or JT's kernel? I would appreciate opinions...
[Fascinate Android Development] sixstringsg:
New builds coming soon, stay tuned!
[Fascinate Android Development] sageDieu:
Yeah see the title up there that says glitch? :P

Wait like, a day or two. Right now this kernel doesn't work right due to some sensor update problems but it's just about fixed and should be released soon... this kernel is much better than Jt's in my personal experience so it is worth the wait.

the default kernel is jt's though; I recommend you upgrade her to miui tonight and play with SAS and some supercharger scripts, just look in development and google for those. then when this comes out put it on.

Sent from my MIUI SCH-i500
[Fascinate Android Development] bigwilly90210:
It's a valid question (barring the glaringly obvious title bar) just cause of all the cross over from JT's kernel discussion. Super stoked to see some new builds soon. I love this kernel so much more and can't wait to finally get back on it. Links in the OP? Or down here again? Ha. Thanks guys!
[Fascinate Android Development] ssewk2x:
Ok. I was always booting jt's from recovery, so that explains it, kind of. Our kernel, however, doesn't seem to work when booted from recovery...but maybe that's because we have our own recovery. Might be a good place to look for a fix at some point.
[Fascinate Android Development] stalls:
Awesome thanks guys! But there is goin to be a v14 though correct? :)
[Fascinate Android Development] sixstringsg:
Read the thread title?
[Fascinate Android Development] AaronCompNetSys:
Well I'm guessing V14 for CM7 is actually what I'm waiting (patiently) for. Waiting for return to BLN from CM7, integration of volume script, phantom rings when calls come in (dunno if kernel or ROM). Less SODs, the improved data switching from Wifi/3G.

I ran Glitch for a long time, but I finally decided that I was completely addicted to rock solid BLN notifications. I can't function without it, I know I'm weird.
[Fascinate Android Development] sixstringsg:
It will be here eventually. And most of those are in 13.1. You are UVing too much or you have faulty hardware if you are getting SODs on our kernel. We haven't had SOD issues since before the Fascinate was a supported device.
[Fascinate Android Development] sageDieu:
Six/glitch, v14 pre 4 is running great so far; seems that the "reboot now" button in recovery just shuts down the phone though... i've used it a couple of times for flashing battery mods and when i press it the phone just turns off, when I hit the power button it boots up fine. Just a heads up, no big deal but it scared me the first time :P

edit: Sensors also seem to be broken. Running elixir now to test... the accelerometer reads as working in tests but doesn't work in apps... like a use Screebl to keep my screen on and that isn't working. Light and prox sensors also have no output.
[Fascinate Android Development] bigwilly90210:
pre4? Is this something only testers have... :( ha. since this is still a preview that would explain why I can't get it through the app on my phone? Since its not RC yet?

On the same thread... is the 12/25 build the latest public? I can't even find it on androtransfer... Thanks guys. I'm loving ICS, the only thing missing is that good ol' Glitch.
[Fascinate Android Development] sageDieu:
look back like a page or 2.
[Fascinate Android Development] jfishh:
Sensors are not working for me as well on pre4 :(
[Fascinate Android Development] bigwilly90210:
guess I didn't go back far enough. ha. my bad! installing now, hopefully no random reboots and such like last time. idk what I did but it was rebooting all over the place... i'll find out when I install but will this work with the onscreen soft keys mod from rootzwiki? don't wanna totally bork something. Thanks guys! I don't know if I could ever use another phone, we're so spoiled by y'all. ha.

---------- Post added at 10:57 PM ---------- Previous post was at 10:51 PM ----------

just flashed it over build 3 with onscreen button mod and they're still there and functional. no issues so far. idk if they're included with the 3.0.8 kernel or not so I thought I'd post for anyone looking... now to get a new radio. just realized I was still on ED05 lol
[Fascinate Android Development] ACLakey:
I am running the Mesmerize(Fascinate Kernel) and preview 3 the compass was working and the sensors were not. With Preview 4 neither are working.
[Fascinate Android Development] sixstringsg:
OP updated with current V14 preview, and V13.1. Changes are in the changelog in the second post.
[Fascinate Android Development] ssewk2x:
Minor addition to V13.1 change log:

- vandalized the boot logo a little ;)
[Fascinate Android Development] xain713:
So preview 3 is the same as the one from yesterday right? Cause mine says preview 4.
[Fascinate Android Development] sendan:
13.1 is running great with MIUI so thanks for that. I have a question though, is there any way to get bln working on MIUI?

I was under the impression it should work by default, but since it's not I figured I would ask.

Thanks
[Fascinate Android Development] k_nivesout:
Thanks for the 13.1 update for those of us still on GB! Seems to be working great so far.

Like sendan, I was also wondering about BLN. BLN control tells me that the kernel does not support BLN, whereas with all the previous kernels it doesn't give me that error, but it didn't work either. LED notifications are implemented a little differently in MIUI than CM7, it has it's own menu but it's not showing for me (MIUI 12.9). Now that I think about it, I don't know that I've ever seen it available on the fascinate, it was on the incredible though so I think it must check somewhere to see if LED notifications are supported.
[Fascinate Android Development] sixstringsg:
This is more of a question for efpophis since I've been testing V14 and he's been doing V13.1, but I believe it should be LED notifications in the MIUI settings.
[Fascinate Android Development] sendan:
I seem to remember an option for LED BLNs back when Andmer ported MIUI now that I think about it, and it worked with JT's kernels as well. I'll ask the current MIUI devs about it though, maybe they can help.

Thanks!
[Fascinate Android Development] Tk-Glitch:
Neldar's BLN has been removed in 13.1 so you won't see it available in any app. It's stock CM7 LED Notifications. It's enabled by default and needs either CMParts app (in CM7) or MIUI LED Notifications to tweak it (ask your rom builder for this if you don't have it).

Sent from my GT-I9000
[Fascinate Android Development] ssewk2x:
I would just like to go on record here as saying that I HATE HATE HATE the way CM7 has implemented BLN. I am still trying to make it work with our kernel, and so far nothing I've tried has been able to successfully turn on the LED when I get an email. I can control the LED on/off via sysfs, but the ROM just doesn't seem to want to do it for events / apps that I have configured.

I'm still trying to find a way to make it work - if anyone else has had success with this, please let me know how you set it up. Otherwise, if/when I figure it out, I will post instructions.

Edit:

Have not been able to get it to work, so I might as well post what I've tried:

1. went under settings -> cyanogenmod settings -> interface -> LED notifications

2. created a category named "blndammit"

5. Three, sir!

3. added a bunch of applications under the blndammit category, including gmail, chomp sms, calendar, etc.

4. selected blndammit category -> edit category settings -> LED mode, and tried every option except "force LED off"

5. watched in dismay as I sent myself emails, sms messages, calendar reminders, etc, and not one of them ever turned the LED on.

Anyone have any better ideas?
[Fascinate Android Development] vinal:
May be a stupid question, but do CM7 roms for Fascinate automatically map LED notifications to touch key backlights since some phones do have separate LEDs for notifications? The EUROSKANK rom I have has another setting that mentions 'touch key backlight'.
[Fascinate Android Development] ssewk2x:
That's the idea, yes. The kernel exposes a sysfs device control file that's called "led" and lives under /sys/devices/virtual/misc/notification. Putting a "1" in this file turns on the LED and putting a "0" into it shuts it off. Since our devices don't have an actual notification LED, we have mapped that file to control the touchkey backlights.

The way I think BLN is supposed to work is that the CMParts apk code listens for "notification events," then sees if the event is coming from an application that wants LED notifications. If that is the case, it places a "1" in that file I mentioned. At least that's how I think it's supposed to work. Currently, on the nightly I'm running, at least, nothing of the kind is actually happening. Hence, why everyone is griping about BLN being broke.

I am just about fully convinced it's a ROM / CMParts issue and not a kernel issue at all.
[Fascinate Android Development] Tk-Glitch:
@ ssewk2x

Is the right liblight in ? Or no liblight maybe ? The BLN liblight won't work with CMLed.
[Fascinate Android Development] ssewk2x:
That is a good possibility. I'll check into it.

Edit: Tk-Glitch, you are a fscking genius. That did it.

So, to fix BLN, I've done the following:

0. As always, it's advisable to make a nandroid backup just in case something goes horribly wrong. I did not do this, and I got lucky. You have been warned.

1. removed the offending library from the kernel zips that I put in my drop box. You can use the same links I sent you and Six to grab them and put them on androtransfer.com if you want. They won't over-write the library that's already there anymore, which I think is the behavior we want from now on.

2. I'll also remove them from the codebase in Git and send a pull request (done).

3. Stopped making gratuitous Monty Python references.

4. I'm posting a CWM flashable ZIP that will replace the "broken" lights.aries.so with the one from the CM7 nightly I'm running, which should allow CM7 stock BLN to function normally. At least it is on my phone.

Here's that file: http://dl.dropbox.com/u/28682151/Glitch-kernels/Glitch-V13.1-BLN-patch.zip

What you, our users, can do:

1. Try flashing my patch. Then follow the steps I outlined in my earlier post where I was complaining about BLN. If your BLN starts working, YAY, you're done!

2. If that doesn't work, try re-flashing your ROM, then wait for someone to indicate that the files linked in the OP have been updated. Download and flash the new glitch after re-flashing your rom.

2a. OR, if you're REALLY adventurous, grab the Glitch V13.1 kernel zip and open it in winzip. Delete the system/lib/hw/lights.aries.so file out of it and copy this modified zip to your sdcard. Then, re-flash your ROM and flash the kernel zip you modified.

CAVEAT: BLN timeout behavior is not quite what I expected - it times out only when the screen is on. Is that what was intended? I have no idea, and I'm not inclined to mess with it.
[Fascinate Android Development] 123SIT:
Flashed patch, configured apps and the backlights definitely come on. They don't flash, but this may be how they are supposed to behave not sure. Haven't had enough time to thoroughly test timeouts yet though. Thanks ssewk2x

Sent from my Glitched CM7 Mesmerize
[Fascinate Android Development] sendan:
Thanks, that seems to have fixed BLN on MIUI. It works perfectly without any settings to configure it.

This is how cm7 BLN has always functioned. Also I'm pretty sure they don't time out.
[Fascinate Android Development] sspgoolsby32:
AWESOME! Thank you so much! That was the last touch I needed to call this the GOAT kernel

Working on MIUI, just flashed the patch on V13!
[Fascinate Android Development] ssewk2x:
Ok, good to know. Also slightly annoying to me, lol. I like to leave my phone on all night with the sound (except for calls and alarm) turned off. I don't like when I get spam email in the middle of the night and it leaves my BLN lights on forever. Sigh. Oh well.

---------- Post added at 04:02 PM ---------- Previous post was at 04:01 PM ----------

Do I dare ask wtf you mean by GOAT kernel? ;)