yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] djp952:
Dude ... not only did this get Facebook-ed as the all-time #1 compliment I've ever received, I think I'm adding it to my resume:

ACCOMPLISHMENTS

- Ensured the continued existence of mankind

Glad to have your back bro. Name the kid "D.J. P. Amante" :cool:

Kidding aside, I'm glad it was a good update so far for everyone. I'm sure something will creep up with BLN that I didn't test, but as always I will do my best to fix it when it does!

OH YEAH BEFORE I FORGET ... My wife, bless her heart, FINALLY let me flash her phone. A complete lack of voicemail and bluetooth no longer pairing with her car were the final straws. Both features work fine again, all her apps have been reinstalled/restored, and I got not one, not two, but THREE "hey, that's kinda cool"s out of her. MISSION = ACCOMPLISHED. I can die a happy man now. :p Specifically she digged the EI20 TouchWiz launcher tray wrap-around, the Samsung keypad and the "Reboot" option.
[Fascinate Android Development] djp952:
I've been screwing with ICS builds for a while now, but haven't been brave enough to pull the trigger on my Galaxy Nexus with a custom ROM yet. Being my primary communication and Angry Birds device, I don't want to mess it up - LOL. I have learned how to do full AOSP builds that work, I even ported GW Recovery kinda/sorta to the GNex using the actual AOSP build process, and that has been successful so far. I even really flashed that to the phone and used it earlier to fix root after applying the newest ICS 4.0.4 leak.

I guess the primary concern I have with ICS on the Fascinate is that I would have to steal a lot of things from other people, far more than I've had to do before. I think the CyanogenMod folks would be my primary kang source to get a working set of device files, but those guys work with the Fascinate as an MTD device, which is not something I've tinkered much with yet.

It's definitely a possibility, but I can't make any promises. Building from actual source code instead of hacking away at java byte code would be such an improvement!
[Fascinate Android Development] mkuehl06:
Lol yeah I understand man. I really do appreciate everything you've done up to this point. Hopefully something will drop that's more of a source. I know they dropped the source for ics and that's what people are basing their roms off of but I didn't know if that's what you were looking for or not.

hi, im Matt and im a flash addict. :)
[Fascinate Android Development] mkuehl06:
Do you recommend using the Odin to flash this or cwm? I've got it on my other fassy and can't remember which method I used. Lol

hi, im Matt and im a flash addict. :)
[Fascinate Android Development] djp952:
I used to swear by ODIN, but I've become a big fan of the CWM/zip method the past few months. ODIN is great, but it's kinda like a lightsaber in that you can very easily lop your own leg off. The end result should be the same, as long as I've done everything right.

The main benefit I see to using ODIN to install this stuff is the "full wipe" TAR. As long as the device is "stock-like", meaning that it's not MTD and has the stock partition table in place, that TAR just nukes everything and provides a nice clean slate to work with. All that can be accomplished with CWM as well, of course, but you have to remember to do so.

The best part about the CWM/zip method is that if something goes horribly awry you can always ODIN your way back!

Short version: CWM if you're not rocking an MTD setup.
[Fascinate Android Development] mkuehl06:
That's what I kind of figured. Thanks again man

hi, im Matt and im a flash addict. :)
[Fascinate Android Development] JJ5150:
Quick question:

In GW 2.6... do we need to apply with BLN patch for 2.5.3? or simply run the bln control app?

I'm on 2.6 now.
[Fascinate Android Development] djp952:
No patches necessary, it's all included in the 2.6 Kernel/ROM. Should just be able to install the BLN Control app, enable it, and be good to go. I think you need the "Pro" version to get missed call notifications to work, but on my phone they worked out of the box. Your mileage may vary!

The only real failure I've seen with BLN has been with android-wifi-tether. if that software is running, I will never get a BLN. Other applications that have a continuous notification don't seem to have the same effect on it. ????
[Fascinate Android Development] JJ5150:
seems to be working so far so good. and I have my charge sound option back. woooo :eek::D
[Fascinate Android Development] rxwookie:
Just a quick note because I know there are users out there wondering...

BLN = Back Light Notification. It's basically a mod that turns your touchkey backlights into a blinking notification led. It must be loaded by a custom kernel (and the GeeWiz kernel now loads it).

The app, BLN Control, just gives you more control over the functionality provided by the kernel. Pro gives more features.

Why is it useful? Your soft key lights will blink (or light up and stay on) when there is a new message, email, etc. This keeps you from having to turn on your phone all the time to see if you've missed something. On the downside, there is no way to differentiate between texts and emails and missed calls that I've seen.

Nice, however, it (BLN) does drain battery a bit faster!

By the way, this Rom and kernel get better each month! I'll be sad when the updates stop. =(

I'm due for an upgrade, but will not do so until this mod stops because I'm so happy with my phone now!

Thanks!
[Fascinate Android Development] JJ5150:
BLN works great. notes me every time. BLN Pro. Great Job once again. :D
[Fascinate Android Development] thisguy23:
Wow this is a first I've seen with these phones to do that! Usually its the opposite!
[Fascinate Android Development] AmanteNJ:
This new update also made my battery usage better than 2.5 ... after 9 hrs and 14 min after charging i still have 85%. wifi on, bluetooth on, data on and minor data usage like facebook, email, market and browsing.
[Fascinate Android Development] rxwookie:
So here's my testimonial...

I love custom boot animations and I have one where the Android dude is built and then turns and destroys an Apple logo.

The only problem is that with the latest version of GeeWiz, my phone boots up so fast I don't get to see the entire animation. I had to switch to a much shorter one & even that one gets clipped a little.

So there... "GeeWiz, it boots so fast you might miss part of your custom boot animation!"
[Fascinate Android Development] ibrubeer:
That's a good one, but doesn't quite measure up to getting laid! Keep working on it!
[Fascinate Android Development] rxwookie:
Yeah, not quite. It's probably the opposite effect because my wife calls me a flash addict now.

=)
[Fascinate Android Development] scarfman4:
I'm not sure if this is the Rom or the market but if I download an app or update one it won't install if the screen is off. It will finish downloading but wait until the screen comes back on before installing. Anybody else seeing this?
[Fascinate Android Development] djp952:
I just tried Netflix with the screen off, and it installed automatically. However, I had the phone plugged in on USB to watch Logcat. So, I tried another app, this time unplugged and it looks like the phone went to sleep once the download completed, which stopped it from installing until it woke back up. Best guess based on the behavior is that this is normal, I think whatever lock the Market has open to download the files is released as soon as it's done which allows the phone to suspend, preventing the installation.

the logs don't help much, I can see where the download completes, then nothing really happens at all until I wake the phone up:

So, you already knew this, but I can confirm that if the phone is suspended it won't install anything. WHY it doesn't, I haven't a clue, but I don't see anything that would point to an error or bad thing, so I'm really thinking this is normal. One of us would probably have to flash back to stock to be 100% sure it's not a ROM issue.

There is something cool we can try, too. What about downloading an app with the screen off and unplugged, then get a BLN? Since BLN uses a wake lock, I think it would be interesting to see if the app will install or not, or if it's being triggered by a screen on type event. Just a text message or GMail BLN, since a phone call would turn on the screen. Science!!
[Fascinate Android Development] rxwookie:
Yea, I'm seeing the same.

Will have to look into it...
[Fascinate Android Development] JJ5150:
I'm happy with it so far. Looks like I finally have the perfect ROM. kapow :D
[Fascinate Android Development] AmanteNJ:
experiencing random reboots for the past 3 days now. it happened twice, wondering if anybody else experienced it with 2.6.
[Fascinate Android Development] scarfman4:
I was getting this when using Super clean M2. I think I was using the 2.5 kernel at the time. It wasn't as frequent as yours though. So far I haven't seen it on full GW 2.6 rom+kernel (knocking on wood).
[Fascinate Android Development] want a droid:
Is it possible to take a screenshot with this rom?
[Fascinate Android Development] JJ5150:
yeah.. seems disabled. I think I remember a post a while back saying it was removed?
[Fascinate Android Development] djp952:
There's an extra to disable it, but out of the box it's enabled and should work. It's a temperamental application in Gingerbread (much improved in Ice Cream Sandwich IMO).

You have to simultaneously press BACK and POWER to take a screen shot. It can be done, the timing of "simultaneously" requires some trial and error. Many applications will respond to the BACK before you can take the screen shot and you miss it. It can be frustrating.

You can practice best at the home screen since there is no BACK functionality. Press and hold BACK and then push POWER. Phone should flash and vibrate and say "Screen captured .." in a toast notification.

Once you get the timing right, screen shots will be saved on the SD card, in a /ScreenCapture folder.
[Fascinate Android Development] JJ5150:
Yep... it works. :p I was holding the power button too long. more than a quick press and it either goes to sleep or gives reboot options. Thanks
[Fascinate Android Development] want a droid:
Thanks for the responses guys.
[Fascinate Android Development] JJ5150:
heh.. I love my phone again... GW ROX!!!
[Fascinate Android Development] scarfman4:
Amen, brotha. I can't believe I strayed by switching to Superclean for a while. Don't know wtf I was thinking! **Hanging my head in shame**
[Fascinate Android Development] djp952:
??? Did you have a question or problem that nobody has responded to? If so, would you mind asking it again? Hard to know if statements are just statements or annoyances sometimes :cool: Happy to help if I can!
[Fascinate Android Development] mkuehl06:
No DJ he got it. He asked a page back about screenshot with this rom. How to do it if its capable. They helped him. Lol.
[Fascinate Android Development] crakedparrot:
DJ, Just wanted to let you know about a minor bug I found. When running GW 2.6 with Kernel 2.6, if you put phone in the Samsung desktop dock with power connected, it causes the captive buttons to remain lit indefinably, unless you press the power button to shut off the screen.

I flashed back to kernel 2.5, left Rom 2.6 as is and the bug was resolved. so I think it has something to do with the BLN that was placed into kernel 2.6.

So to recap... GW Rom 2.6 w/ Kernel 2.6: causes bug. GW Rom 2.6 w/ Kernel 2.5 or below: resolves bug.

Pertinent software: Widget locker, alarm clock plus, bedside mode.
[Fascinate Android Development] djp952:
Confirmed. I'll have a look to see why that's happening. Sorry!
[Fascinate Android Development] djp952:
OK, I have a pretty good idea what's going on, sorry for the delay in a follow-up on this. To get BLN to work, I had to "fix" a couple things in the touchkey driver that were broken. Samsung had intentionally removed the ability to turn the lights on manually for some reason (and there was a bug in it anyway), now perhaps we know why :D

This stuff (bln/liblights/driver) is all somewhat intertwined, I'll have to play around with what I can re-break and what I can't and still have the right functionality present. It may be as simple as messing with liblights so it can't do a straight ON command to the lights (another thing I fixed from the source I had).

We'll see. I'm sure I can figure something out :D
[Fascinate Android Development] rxwookie:
Me too... SuperClean is nice, but GeeWiz it's hands down the best.
[Fascinate Android Development] nitsuj17:
well i wouldnt say it was "shameful" to have used superclean :rolleyes:

everyone has their own preference
[Fascinate Android Development] bobloblaw1:
Fanbois are unable to express their like of something without trashing an alternative. Is it immaturity, confirmation bias, a lack of common respect for work done by all...? Who knows.

Anyway, thank you to both djp and nitsuj for giving me options and making my phone head and shoulders better than the verizon ROMS.
[Fascinate Android Development] AuroEdge:
Yeah I don't get it. I float between the different ROMs. They clearly have different strengths which don't make them better than the other. It's one thing to complain and another to outright trash on a developer
[Fascinate Android Development] Wolfkmann:
I am waiting for the ultimate rom, "superwiz" it should hands down be the best of both worlds.

Imagine if nitsuj and djp built one rom together from the ground up,

I think samsung and verizon would both have strokes.

"I just want the phone to work perfectly, despite all my tinkering. "
[Fascinate Android Development] scarfman4:
Yeah sorry guys. I have no disrespect for nitsuj17's work. I really like a lot of things that are included in Superclean3 that aren't included in GeeWiz which is why I switched for a while. But the frequent hot reboots were starting to really bug me. I never had the problem on earlier versions of GeeWiz so guess I got spoiled, and going back seemed to clear it up.

So I'm not trying to diss any developer. I was just glad that I got my phone back to an enjoyable experience.

So my humble apologies to all offended. After all, without our developers, where would we be? (Oh yeah, still using crappy stock.)

**Still hanging my head in shame**
[Fascinate Android Development] scarfman4:
That would be beyond awesome!
[Fascinate Android Development] lord dredd:
I totally agree !!!

The dev are doing us a favour,

if someone doesn't get along well with one thing then it doesnt mean its trash or shameful.

Thanks DJ and Nitsuj for still hangin in there for us, the ever demanding bunch of perfectionists :P

god bless
[Fascinate Android Development] rxwookie:
No one said SuperClean was horrible... just that GeeWiz is the best right now.

I too switched to SuperClean for a few days, but did not find any benefit over GeeWiz so I switched back. There were a few things I liked better, but I can't pick and choose individual parts. If GeeWiz stops getting updates and SuperClean passes it, I'll switch back.

[RANT] I don't apologize for that. I'm allowed to have my opinion and express it, just as you are. The difference is that I respect your right to your opinion without resulting to name calling or flaming.

I truly appreciate every developer who takes the time, risks their hardware, and furthers the functionality of our phones beyond design regardless if I use their mod or not.

Say what you want in response, just don't expect a reply back. [/RANT]

Sent from my Fascinate running GeeWiz Rom, Kernel, and Recovery
[Fascinate Android Development] nitsuj17:
that wasnt my point....nor was i questioning anyone's particular opinion as to what they like most or feel is best

honestly? people are more than free to use whatever rom/kernel/theme/mod that they like the most or they feel runs best on their phone....i dont take any personal offense if someone likes another developers work better than mine, really i dont

i just happen to not like putting down the work of a developer or their work in the praise of another...i would feel the same way (and in the past have commented on it) if someone posted in one of my threads praising my work inspite of someone else's

reading back through the comments, i realize it wasnt probably meant as an insult more of a tongue in cheek statement...but it rubbed me the wrong way at the time

cm9, cm7, poolparty, the other mtd roms, geewhiz, superclean, resurrection, and even still powerwashed are all fine roms and have their own appeal....ill leave it at that

sorry for cluttering up your thread with unnecessary stuff djp :o
[Fascinate Android Development] dave3588:
You forgot to mention salsa lol XP sorry
[Fascinate Android Development] JJ5150:
I can't help but to keep coming back here and offering my gratitude to this ROM. Not that I"m flattering anyone or insulting anyone. I'm just so happy to get my life back. I mean for like 2 months or more I was a flash-0-holic. Neglecting important things and being simply Phone crazy. Even my girl-friend would say to me, "you play with that phone more than me.". wow... really?

I am very pleased that my phone responds to me as it should. It does everything it's supposed to do, I've gotten my money's worth finally. I've gotten my life back.. and I'm just appreciative to finally have a great ROM.

Thanks again DJ.
[Fascinate Android Development] djp952:
Hey gang. Sorry I kinda disappeared on you for a few days here, I got involved in a couple new projects and pretty much ignored everything else while I was working on them :(

First off, I am still trying to find a good solution to the docked LED always-on issue with GeeWiz 2.6. It's becoming a rather complicated issue to solve, I think the ultimate solution at this point will be to implement a soft-key timeout so they turn off after a while regardless of the reason they were turned on. I apologize for not being able to come up with something quickly for you this time. I would also like to tweak the older "in call volume" hacks a bit since with the EH03 kernel the general consensus is that in-call is too loud now as are the system sound levels.

All I can really say about the "ROM vs. ROM" stuff that happened recently is that I concur with the opinion that once you deviate from stock everything is quite subjective. All of the developers out here do what they do because they want to and it's interesting/exciting for them, and as long as "developers" continues to be a plural word there will always be unique options to choose from. One option is rarely if ever "better" than another, I would prefer to think of them as just "different" :) We're all hacking away at code we didn't write and have different goals in mind, so the end results will always deviate from one another. Each and every implementation has it's goals and challenges to deal with, and the more advanced the author takes things, the more likely unexpected things will occur (and those things become harder to predict!). My stuff takes the easier road in general with less extreme changes, so it's much easier for me to test out and be fairly certain that other people will have the same experience I do :cool:

I don't mean to preach, I think you're all great and I'm

very

appreciative/thankful to you for making me a contributing member of this community :D I'm just a little uncomfortable now and again when these conversations come up. The people we REALLY need to thank are the folks at Samsung for manufacturing these devices to begin with! Yeah, ok, their software leaves a bit to be desired, but the hardware is fantastic and they have ultimately provided enough code for the community to sink it's teeth into and try to correct the software shortcomings :)
[Fascinate Android Development] mkuehl06:
Great post dj, we all do appreciate all you and the rest of the devs do for us. I agree with the rom vs rom bit also. Patience is the most important thing and I'm sure with time everything will come to light.
[Fascinate Android Development] scarfman4:
I still feel bad for starting this whole Rom vs Rom discussion. At the time I didn't realize that such a simple statement would have such a negative impact. And everyone is right; we should let our devs know how much we appreciate their work but not at the expense of another. So after eating a lot of crow I hope we can get back on track and work on making these roms better for all.

In terms of the in call volume, I agree that it's better than stock but is kind of too much. Is there an in-between?
[Fascinate Android Development] djp952:
1) No worries, it happens! If I had a dime for every opinionated discussion I inadvertantly started, I'd have a nicer car - LOL.

2) There should be, I remember when I merged that code in on the EI20 kernel where the levels are set, I also have my "djp952" tag in the code from where I fixed the speakerphone problem it had. I'm almost certain it won't be a big deal to adjust them down a bit.
[Fascinate Android Development] AuroEdge:
So with BLN enabled this generates a wakelock when the buttons are lit? Are you making it through the day on a single charge with this feature turned on?
[Fascinate Android Development] AmanteNJ:
I've had this 2.6 for quite a while now and the battery is better than before with bln on. I would normally see my softkeys on due to email and sometimes will leave it on for a good 2 to 3 hours while sleeping and i will still have enough juice for the whole day. My record for this GW 2.6 is 32 hours and that's awesome compared to the other rom/kernel combination i tried.
[Fascinate Android Development] steve2711:
In Agreement with Dev Support

Yeah, who else puts up with our needs and requests, almost daily if not sooner. In fact I have one. I'm useing the latest KGB kernal with Geewiz, which works very well. However, the boot animation and sounds are stock, and I can't find the boot sound in System/Media, or data/local, and would like to turn the boot sounds off. Any ideas? Thanks
[Fascinate Android Development] scarfman4:
Startup sound is in system/etc and the shutdown sound is in system/media/audio/ui.
[Fascinate Android Development] djp952:
I'm currently listening to my old favorite Internet Radio stream on my old Roku Soundbridge, thanks to ressurecting some old web server code I wrote and hacking up a stream converter app, so I think I'm ready to hit GeeWiz again :) I do love that Euro-pop ... LOL. That's the last of the 3 personal projects I took time off to work on :cool: (3 "old"s in that statement ... "old" in this case means something I did 5 years ago and thankfully did well enough that I was able to update it in just two short evenings!).

Anyway, quick answer to a question: The BLN wakelock I implemented only takes effect while a BLN is actually active. It was necessary to keep the lights on otherwise the phone will go into "deep sleep" and they would turn off. As soon as the device is woken up, the lock is cleared. I'm still getting

at least

5 days of standby battery on the Fascinate, so unless you get a lot of BLNs and don't clear them, there should be no real noticeable impact. If you get a lot of BLNs, chances are good you're checking them often as well, so my thinking is that even though the device is awake and sucking some battery, chances are good it won't last long. Unfortunately, there is no way I could find to avoid the wakelock with EH03, it also turns out that the GS:2 devices have the same dilemma.

I did try adding a timer to the backlights tonight to solve the dock issue, and it failed miserably. I think I'll just look at what others have done and do hope I can deliver a proper fix soon to you guys.
[Fascinate Android Development] steve2711:
Great Thank you-That did it
[Fascinate Android Development] jcurley:
I went on a business trip and had to use a lot of Navi.

When running Navigation for an extended period, I got a lot of lock ups on Geewiz Kernel 2.6 running SC. Not sure if it is a bug or not. I just started using the Autokiller again and seemed to help a little.

Otherwise, just waiting until ICS is running well or I can upgrade to the GNEX and a GNEXWIZ rom :-)