yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] SmokeyDP:
You should update the year in the OP, I'm sure some are skipping over your recent work thinking it's an old ROM. Nice work guys.
[Fascinate Android Development] djp952:
Whoops :D I hate January! Thanks for the heads-up!

Oh ... alright ... been avoiding that for far too long, haven't I? ;)
[Fascinate Android Development] gotsflat4love:
BLN wouls be awesome!

Also, when playing fruit ninja the screen becomes unresponsive. Is that a kernal issue, rom or phone issue?

It's been a long time since I have been on a TW rom, but this is pretty stellar. Thank you sir.
[Fascinate Android Development] JJ5150:
I found an issue. Stock music player skips in standby and badly while on a charge. In fact the whole system seems to slow and choke while on a charge. Usb, and ac charge slows system to a craw. No other apps running... I have not tried other music players yet.

---------- Post added at 04:51 PM ---------- Previous post was at 03:51 PM ----------

PlayerPro is the same. The system slows on charge.
[Fascinate Android Development] djp952:
Hmmmm... I'm not seeing anything like that here with charge or the music player application(s). On the surface it sounds like something is spiking the CPU. Do you have any CPU/system monitors or anything like SetCPU installed? Anything that may be going wild trying to monitor something like a charge event/battery level?

The recent change to remove the charge notification tone/vibrate could, in theory, be faulty. All it does is skip the code that causes the notification, but perhaps under some circumstances I never tried it may be looping. I'll review that again and see if I can see any way something like that could happen. I don't think this would be a root cause, and it really should have no bearing on music player in standby off-charge, but you never know!

Do you have ADB access from your PC, and if so would you mind grabbing a logcat for me, ideally from a clean boot? Perhaps boot, start music player, let it suspend and get choppy, then plug in the AC for a bit, then unplug the AC for a bit. The log isn't infinite, so maybe only do each thing for 30 seconds to a couple minutes to make sure we get everything.

PC: adb shell

ADB: logcat -d /sdcard/logcat.txt

ADB: exit

PC: adb pull /sdcard/logcat.txt

You can PM me the log file, or if it's too big I can PM you an e-mail address to use.
[Fascinate Android Development] JJ5150:
alright. I'll have something for you by midnight-ish...
[Fascinate Android Development] AuroEdge:
I have to agree that the addition of BLN would be welcome. So long as there are no negative effects. Would there be any?
[Fascinate Android Development] scarfman4:
Instead of the code trying to skip the sound, why not just make a sound file that has no sound to replace the chirp? Someone had a sound file in this thread that was blank sound that works.
[Fascinate Android Development] ljbrenes:
For the people that have run these other Roms, how does it compare wth TSM 2.x or superclean?

I am interested in stability, battery and performance. Thanks.
[Fascinate Android Development] scarfman4:
I'm running Superclean3 with GeeWiz kernels and to me the transitions are quicker on GeeWiz. Otherwise both are good when paired with the GeeWiz kernels. I have been avoiding TSMRes because of the reports of lag over time and hot reboots. In terms of battery life I can't really say which is better.

I'm always glad GeeWiz is out there. I call it "Old Faithful".
[Fascinate Android Development] djp952:
That would be too easy :p Actually, it was a really easy change and it also gets rid of the vibrate event. I went for the Ice Cream Sandwich approach to both that and the change to recharge at 98% instead of 95%, based on how my Galaxy Nexus behaves.

On the off chance that turns out to have been a problem (I did review it and don't see how, but it is decompiled byte code, so there's always a chance!), I will definitely just put it back the way it was and we can delete/replace the sound file
[Fascinate Android Development] djp952:
Well, I would put this out as an "experimental" thing first so people can try it out to see if there are any unforeseen consequences before just including it and possibly messing things up for those that really don't care about it. As with all changes, the honest answer has to be "maybe", though.

I looked at BLN this afternoon and grabbed the necessary code, but I'm going to approach it a little differently than the implementations for the Fascinate I researched. All the ones I've seen so far use a ported driver (cypress) from the GT-I9000 that seems to be out of date when compared with the latest I9000 driver, possibly even from the Froyo kernel (I'm still comparing it to old I9000 code to see if I can find exactly where it came from for a good diiff). What I would prefer to do is modify the EH03 driver to include the BLN changes rather than use that I9000 driver. That may not work, haven't gotten far enough into it yet to know for sure, but that's my initial approach. I hope by doing it this way there won't be any unintended bad things from using code that is possibly out of date or not quite right for our hardware.
[Fascinate Android Development] AmanteNJ:
u da man .........
[Fascinate Android Development] scarfman4:
Yeah I tried just renaming the soundfile on SC3 and tried plugging and unplugging it and it didn't seem to have any issue. I haven't tried a full charging though.
[Fascinate Android Development] djp952:
New experimental/test package 2.5.1 has been posted. This update attempts to add BLN support to the GeeWiz Kernel/ROM. The update-zip will replace your kernel and add the liblights library to your SYSTEM volume.

This set of modifications were made against the EH03 kernel code, whereas all the other BLN implementations I found used an outdated GT-I9000 driver port to accomplish it. As a result, mistakes may have been made. Just let me know what doesn't work and what you expected it to do and I'll try my best to fix it. The liblights library (/system/lib/hw/lights.s5pc110.so) is also not a copy from anywhere, it's a compiled version of the code from Neldar that I included in my main SCH-I500 build (see github for details)

BLN support is DISABLED by default, and must be enabled with something like BLN Control Free or Blinky (Android Market), or perhaps by using the init.d support built into the GeeWiz kernel to do it via script. I will not be providing a built-in way of enabling/configuring BLN in GeeWiz.

Suggested Apps from Android Market: "BLN test app" - will verify installation worked properly. "BLN control - Free" - will allow you to enable BLN support.

GeeWiz 2.5.1 Experimental - 1.27.2012

Add BLN support to GeeWiz kernel (must be enabled with BLN Control or Blinky or some other application)

Add liblights module (lights.s5pc110.so) to GeeWiz ROM

http://www.mediafire.com/file/lqjnkfc15pe0etk/geewiz-2.5.1-bln.zip

MD5: 90cc65eb5f76d0b7df933cea09e75107
​
[Fascinate Android Development] JJ5150:
Quick n00b question

Edit: already answered my Q. :rolleyes:

Mike, what do you think about this app and is it applicable with your ROM?

http://xdaforums.com/showthread.php?t=1465661
[Fascinate Android Development] djp952:
My BLN doesnt work quite right yet anyway so dont bother.

As for the switcher app sure that might work fine. I can try it out after I fix BLN. Neat idea.
[Fascinate Android Development] JJ5150:
seems to work for me
[Fascinate Android Development] crakedparrot:
Yep working fine here too:)
[Fascinate Android Development] AuroEdge:
Not working here, but it's an experimental after all
[Fascinate Android Development] djp952:
Yeah, it seems to start out working OK and then stops working. Last night it was OK when I had the phone plugged in, but went awry as soon as I packed it in and was on battery. I think it's a matter of time before it stops working for the other guys too :(

I have about an hour tonight to play around with it, from the behavior I saw it has to do with a timeout occurring after an event has been received that's still turning the touchkey device back off again.

Did it do anything at all for you, or is this what you were seeing as well ... works once but then the lights turn off after 5 seconds or so and it's kaput.
[Fascinate Android Development] AuroEdge:
With BLN Control the test worked for a brief moment. With Blinky it wouldn't... blink but it did work for a couple sms or so.
[Fascinate Android Development] JJ5150:
It stopped working for me too.
[Fascinate Android Development] crakedparrot:
That's strange.. because i'm going on 20 hours running and mine is still working as expected, I have not done anything but set it up on install with BLN Pro (I purchased it way back in the early CommRom days) and it has worked ever since
[Fascinate Android Development] djp952:
BLN update:

I've made some additional changes to the touchkey driver now that I understand how it works better and learned how to control it (and BLN) manually from ADB. Not much different end-result than what it was, but cleaner on the inside.

The main issue I have is that when the device suspends it will still kill the lights. Not sure how yet, since I removed that ability from the driver, but I think it may have something to do with the new EH03 "deep sleep" stuff, perhaps it's powering down the device on me in some other driver. I have a couple ideas on how to deal with that, but it will take some time to play with.

edit: fixed by using a wake lock. Yes, it will affect your battery life somewhat, but only while a BLN is active. Sorry, but it's the best I can come up with

The other problem I have is that the notifications won't always trigger through BLN. Could be the liblights, could be BLN, could be something else entirely. Annoying.

For those that it's working for ... 2 questions. 1) Are you using GeeWiz ROM or some other ROM that might have a different liblights module? 2) Do you have anything that might be keeping the phone awake all the time off-charge?

For those that it's not working for ... I'm still trying :(
[Fascinate Android Development] djp952:
Let's see if this makes BLN any better. 2.5.2 attempts to fix BLN a bit, the main difference is that now BLN will take a wake lock when it activates, which seems to solve the problem with the suspend/deep sleep of EH03. This will absolutely have an effect on battery life, but it shouldn't be that bad and it only applies while a BLN is actually active.

GeeWiz 2.5.2 Experimental - 1.29.2012

Add wake lock to GeeWiz Kernel BLN support to solve problems with EH03 deep sleep

Refactor GeeWiz Kernel BLN support to use built-in functionality and clean things up a bit

Modifications to liblights, primarily correcting device paths; none of which seemed to be necessary

http://www.mediafire.com/file/6ohi5fgqaq1quzq/geewiz-2.5.2-bln.zip

MD5: 51174d7b05d81d2952884b4b3c9d9421
​

I'm happy with the kernel now, and I did a lot of testing on it and believe it to be pretty solid. I'm not as sure about the liblights module nor the ability for the Samsung EH03 applications to use it properly.

With the standard EH03 apps, I typically get one BLN that works and then there are no more notifications for new events, so nothing interesting happens. I will continue to research and work on this, but I wanted to post because I think the kernel is solid and maybe using somebody else's ROM/MODs would work right across the board?

I will continue to work on this feature...
[Fascinate Android Development] crakedparrot:
Working fine on mine going on 48 hours now....

#1 I am using GeeWiz 2.5 and GeeWiz Kernel 2.5 with 2.5.1 update.

#2 I am using WidgetLocker for lock screen, and Handcent sms with pop-up service active, not sure if they use a wake lock, but its a start..

I'll keep looking..
[Fascinate Android Development] JJ5150:
mediafire is acting flakey. The download is corrupt 3rd time now...
[Fascinate Android Development] ibrubeer:
Quick question... I am on SuperClean currently with stock EH03 kernel wanting to try this kernel. Do I need to flash the GeeWiz recovery if I flash the kernel? I currently have CWR 2.5. Thanks!
[Fascinate Android Development] djp952:
Any luck? I was able to download it OK, but I'd be happy to re-upload it again if you are still having problems ;)

Nope, you're totally fine keeping ClockworkMod. I try to keep all three things (Kernel/Recovery/ROM) independant of one another as much as possible so everyone is free to use whatever bits and pieces they want :cool:

Be advised that the recent "Experimental" ones posted here (2.5.1, 2.5.2) are for testing BLN and include a library that would overwrite something in SuperClean, so please stick with the main 2.5 kernel-only download from the first post. I don't want to break anything on ya!
[Fascinate Android Development] ibrubeer:
THANKS!! It downloaded perfectly fine!

Noob question...I may have been messing up fundamental kernel flashing in my haste lately. In flashing back and forth between stock EH03 and GeeWiz/KGB, are you supposed to wipe cache and Dalvik every time? Also, does GeeWiz autoconvert lagfix or do I need to select that from CWR after flashing? I'm guessing I would have to disable lagfix if going back to stock EH03. Thanks for all of your work!
[Fascinate Android Development] JJ5150:
Yeah it finally downloaded uncorrupt. I had to disable my Kaspersky. That was weird. and it seems to be working. :D
[Fascinate Android Development] AmanteNJ:
Just my observation and i am not sure if it's the recent kernel/rom (GW 2.5) but my battery life seems to be shorter than the previous version (GW 2.4)

I havent tried the BLN version yet and i dont know if it's my location but it looks like it is eating more than before hmmm
[Fascinate Android Development] scarfman4:
As a test try rolling back to the 2.4 kernel and see if you notice any difference. You can also try rolling back to the 2.4 rom then updating just the kernel to 2.5. That would help you determine if it's the rom or kernel.
[Fascinate Android Development] AmanteNJ:
Will try that one. with regards to the bln update. It only works on the first text message and the following test messages it doesn't work anymore.
[Fascinate Android Development] ejdavis72:
GPS

I am having trouble with GeeWiz and my GPS, it starts, then freezes and it won't do anything at all and requires a battery pull. Not every time though... I am running KGB kernel with the ED05 radio. Any ideas?
[Fascinate Android Development] AmanteNJ:
If you are using google map uninstall and reinstall from android market. Dont pull the battery just press and hold volume up and power for 10 seconds it will reboot the phone. And i have the same experience with KGB kernel, try the stock EH03 Kernel and see if it will still freeze on you.
[Fascinate Android Development] djp952:
Yeah, I have it all figured out and I'm just trying to determine exactly how to deal with it ...

BLN update:

> Kernel (unreleased) looks good across the board now, I corrected a problem I introduced in 2.5.2 where touching the keys would wake up the phone. Now it will stay asleep until you hit power. Adding the wake lock overcame most of the obstacles here.

> liblights (unreleased) looks good across the board now as well. I think I have some pending minor changes that were necessary, but I also have a ton of debugging statements to take out, but either way this will get recompiled.

The problem that still remains is an issue with the ROM/system. Well, maybe not an issue per-se, but a quirk to work around. Once a BLN has been issued, the Notification Manager will no longer send new ones. I've been debugging this last night and today, and determined that what you're "supposed" to do is drop-down the status bar panel, this will reset the state of the Notification Manager and allow new BLNs to work again. I'd like to change this behavior so that if a notification is removed from the status bar (like messaging would do automatically), or on a couple other events, it would also reset the notification state.

So it looks like I'm to the point where the BLN support in and of itself is good, I just need to make the ROM work the way we would expect it to.
[Fascinate Android Development] djp952:
This was/is a common issue with the pre-EH03 kernel code. I don't know exactly what bits of magic EH03 changed since I did a "start over" approach to my kernel, but there were a handful of changes to the drivers, including the touch screen driver. I took the approach of re-adding all the changes I wanted to the base EH03 code rather than trying to merge the other way. You could probably contact comradesven to see if he used all the driver changes in EH03 or if some weren't used because they might mess up some of his other enhancements. It never hurts to ask! :cool:
[Fascinate Android Development] djp952:
Hmmmm... I wonder if the updates to the Google Apps could be a factor here. I always wonder if it's worth it or not to keep those up to date, but in the end I convince myself that pretty much everyone would just blindly update them anyway so there would be little value in leaving old versions in place.

I'm not pointing a finger at the Google Apps, just trying to think of any reason that 2.5 would cause additional battery drain over 2.4.

If you have a way to "freeze" apps installed, may I suggest freezing Google Maps, Google Music and Google+ for a bit just to see if that makes a notable difference? I couldn't live without Google Maps for a single day myself - don't care how much battery it might use! LOL
[Fascinate Android Development] lord dredd:
Hey DJ ,

I am sure you are alreday aware of it,

the shutdown menu options are configured wrongly

the recovery option actually reboots

the download option takes to recovery

regards
[Fascinate Android Development] djp952:
Tzup LD! :D

Methinks you may have flashed a different framework-res.apk, perhaps for a battery mod?
[Fascinate Android Development] JJ5150:
ditto.....
[Fascinate Android Development] ejdavis72:
Yeah thanks, I tried that and it did not help at all. I went a head and installed the whole GeeWiz package and everything works well now. Well, other than the BLN notification but that's experimental right now. Oh, and my music skips sometimes out of nowhere. :D

---------- Post added at 05:45 PM ---------- Previous post was at 05:34 PM ----------

My BLN seems to work for the first notification as stated by someone before but it won't blink, it just stays on and the screen can be activated by touching the lit keys. It does this with Blinky or BLN Notification. I'm using 2.52 you posted at about 1AM yesterday.
[Fascinate Android Development] myersw:
l am running GW 2.5 kernel and TSM 2.1. It seems to me that my battery life is not as good as when I was using the GW 2.4 kernel. Kernel is the only difference. Have not installed any applications since installing the GW 2.5 kernel. Difference has not been enough to get me todrop back to 2.4 kernel. I really like this combination of GW kernel and TSM. Runs the way I would expect this phone to work but never really until now.

--bill
[Fascinate Android Development] AuroEdge:
For the worse battery life, might it be attributed to the voodoo part of the kernel? I don't run voodoo just b/c for me there is no appreciable advantage. Runs great as is
[Fascinate Android Development] scarfman4:
I'm running 2.5 on SC3 Milestone 2, no Ext4 conversion or Voodoo control right now. I can't really say if it's better or worse but so far it seems to work pretty well.
[Fascinate Android Development] djp952:
Sorry for the delay in a response to you :(

> When flashing the Kernel, there is typically no need to wipe any data at all. Wiping the cache doesn't hurt anything, nor does wiping the dalvik-cache, but it will make your first boot take a really long time for no reason :) You really only need to wipe the dalvik-cache when an APK/JAR has changed (and even then it's not always necessary)

> GeeWiz has no auto-conversion feature, I'm very much against that. I provide a way to do it with a couple clicks with GeeWiz Recovery, and existing voodoo-ed devices are supported by the GW kernel. I haven't used ClockworkMod in a while since I've been "rolling my own", but if I recall if you installed a Voodoo version of it, it may auto-convert if you boot into recovery a second time. Don't quote me on that, though. If you really want to auto-convert, install a Voodoo-enabled kernel and boot up, that should convert you with the cool sexy robot voice :) After the device has been converted, you can re-flash any kernel you want that supports EXT4. I suggest the KGB kernel for the best features/performance or mine for a tamer feature set with perhaps a bit more stability.

> If you are going back to stock EH03 with the "full ODIN", you don't need to worry about converting back first, since it will overwrite your entire device and implicitly convert it back to RFS. If you are just going back to the EH03 stock kernel, that doesn't support EXT4 so you would have to convert back to RFS first otherwise your phone won't boot. It won't be broken, but it would just hang on the SAMSUNG logo. Flashing an EXT4-enabled kernel back on it would fix the problem :cool:
[Fascinate Android Development] djp952:
I remember this question, but for some reason I can't find the post to quote ... maybe it was a PM, and if so ... apologies to the sender for allowing it to get lost in the shuffle :(

Q: My Fascinate doesn't show up on my PC when I connect it over USB

A: This is an ages-old issue with the Fascinate, there is some bug in Samsung's USB code that makes it screwy with MTP support available. To fix it, go into Settings/USB Settings and select "Ask on connection" from the available options (the default is "Mass Storage"). Now when you connect USB, you will be asked to "Select USB Mode". Pick whichever one you want (Media Sync = MTP/Windows; Mass storage = flash drive). If you pick Mass Storage, you will see a green android that says "USB Connected", and you have to touch "Connect USB Storage" to actually mount the volume.

I will try to change this default to "Ask on Connection" for GeeWiz 2.6. To be honest, I wanted to do that a long time ago but forgot all about it.
[Fascinate Android Development] lord dredd:
:p indeed i did :) gosh !! u are good :)

sorry mate :P

but then i flashed the aosp lock over it from SC and now ist all fine and i hav got a different lock too.
[Fascinate Android Development] ejdavis72:
GPS issues

I was still having GPS freezing issues and I was able to solve the problem by installing an older Gmaps from Oct 2011. I have tested it many times with no issues. Try it out if you're having issues too.

http://xdaforums.com/showthread.php?t=1451370
[Fascinate Android Development] djp952:
Knocked off a couple more old to-dos from the mental list today for GW 2.6. I changed the default USB mode to "Ask on connection" and actually made good on a very old promise (from GeeWiz Froyo!) to add extended Kernel version info as well as a ROM version item to About Phone. Screeny attached below.

I also found a potential problem with BLN in experimental 2.5.3, but I have to look into it to see what, if anything, can be done about it. I was using android-wifi-tether today on the Fascinate and I didn't get a BLN. It seems that android-wifi-tether, or perhaps more appropriately a constant notification icon in the status bar can stop BLN from working. And here I thought I had this BLN stuff nailed. *sigh*. But hey, I was showing off my changes to a Captivate user and he said that GW BLN support works better than his does, so that's something! lol. (I have no idea what ROM he's using, but I do know that the GSM models have a tremendous development base compared to our little CDMA gang)

No worries on me throwing out a GW 2.6 this soon after 2.5, I remember how annoying that can be from the old Superclean days. Couldn't flash my phone fast enough to keep up with Adrynalyne :D I like the approximately 1 month cycle, but GW 2.6 will probably come in a week or so ... pretty much depends on how the feedback on the BLN stuff goes.