Is there a reason I can't seem to get logcat to work with this kernel?
EDIT: Nevermind, found AndroidLogging in the tweak options.
EDIT: Nevermind, found AndroidLogging in the tweak options.
Last edited:
I've been using this by installing the Serendipity ROM. Works great, except that BLN should NOT be baked into a kernel. If somebody wants to add it as an app, fine, but some tertiary functionality shouldn't be at the kernel level.
Also, as a side note, NoLED is a MUCH better way of getting over the notification issues of the Galaxy S hardware. I've been using it since I got my Captivate, and it works great.
EDIT: Typo.
I've been using this by installing the Serendipity ROM. Works great, except that BLN should NOT be baked into a kernel. If somebody wants to add it as an app, fine, but some tertiary functionality shouldn't be at the kernel level.
Also, as a side note, NoLED is a MUCH better way of getting over the notification issues of the Galaxy S hardware. I've been using it since I got my Captivate, and it works great.
EDIT: Typo.
Using Samsung Car Dock -audio from phone is stopped, but there is no output from the dock. Should this be working yet in K13E?
I've been using this by installing the Serendipity ROM. Works great, except that BLN should NOT be baked into a kernel. If somebody wants to add it as an app, fine, but some tertiary functionality shouldn't be at the kernel level.
Also, as a side note, NoLED is a MUCH better way of getting over the notification issues of the Galaxy S hardware. I've been using it since I got my Captivate, and it works great.
EDIT: Typo.
Well, at least he's whining about it in the right thread now. He is the only person using Serendipity who seems to feel this way, and trust me, he won't let it go.There are 2304 posts in this thread. Yours is the only one whining about bln being in the kernel. I'm sure hardcore will get right on it for you. Unreal.
Sent from my Samsung Captivate using Tapatalk
Well, at least he's whining about it in the right thread now. He is the only person using Serendipity who seems to feel this way, and trust me, he won't let it go.
You're right, I've never set anyone to 'ignore' before, he's become the first.Yeah, just ignore him from here on out. It's really the best option at this point. You will never cease his complainin, we've tried.
You're right, I've never set anyone to 'ignore' before, he's become the first.
Back to the subject - I hope Hardcore is working on a GB kernel for whatever GB ROM Mike is cooking up!
Adam and Zel of the Team Phoenix crew said they've been using a beta GB speedmod for the Gingerbread Phoenix ROM. I'm sure we'll be seeing the kernels and ROMs very soon.
Awesome!Adam and Zel of the Team Phoenix crew said they've been using a beta GB speedmod for the Gingerbread Phoenix ROM. I'm sure we'll be seeing the kernels and ROMs very soon.
Adam and Zel of the Team Phoenix crew said they've been using a beta GB speedmod for the Gingerbread Phoenix ROM. I'm sure we'll be seeing the kernels and ROMs very soon.
Since you're so against people "adding garbage" to the rom/kernel... then do yourself (and everyone else around here) a favor and just load the AT&T KB1 rom/kernel and stop harassing the devs here.Then don't do it. It's just bad practice to be adding garbage to the kernel. Also, since the Galaxy S has the AMOLED screen, it's not needed in the first place. As much as AMOLED still isn't ready for prime time, that is one nice part of it.
Then don't do it. It's just bad practice to be adding garbage to the kernel. Also, since the Galaxy S has the AMOLED screen, it's not needed in the first place. As much as AMOLED still isn't ready for prime time, that is one nice part of it.
No, normal posts are saying, "hey I've found a problem when I try to do this. I tried this to fix it and it did/didn't work. Suggest adding that to the next release. or does anyone else have this problem"
Saying the work that the developers do and include is "garbage" is not normal posting and goes against all of the rules about flaming that are included in XDA. If you don't like BLN, that's fine. Go into recovery mode and turn it off. That's what I do because I don't use BLN either. If you like NoLED, that is your opinion. However, adding the functionality to the kernel is actually faster and better suited than an app that is constantly running and uses memory and power. You are entitled to your own opinion, just be respectful and don't harass people when they tell you the feature is very easy to turn off.
If you really have such a problem with this kernel. Just find a new one. There are plenty of options but a bunch of them do include BLN or an equivalent. Check out the kernel thread for more options.
The thread's for discussion of the kernel, and that's discussion of the kernel. I don't doubt that it's more efficient to bake something into the kernel, that doesn't mean it should be done. It's fundamentally bad practice to put tertiary functionality into the kernel where it clearly doesn't belong.