yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] comradesven:
Hrm, in-call reboots is troubling. Might do a version with nothing but the essentials to see if that helps. I personally am not experiencing it though.

As for sixaxis support, after talking to the dev for that he pointed me to a beta sixaxis support checker app for an upcoming release. We have a Broadcom bcm4329 which is an incredibly popular WiFi/Bluetooth chip, and it might be working right now on CM7, but Samsung sources don't expose L2CAP support in the Bluetooth driver. It looks like he found a way to get around that. If one of these http://xdaforums.com/attachment.php?attachmentid=741536&d=1317890455 http://xdaforums.com/attachment.php?attachmentid=741052&d=1317845758 say that they will work that means there's a good chance it will be fixed soon anyway.
[Fascinate Android Development] AtropineNa:
can you guys send text picture messages? I am unable to for some reason...
[Fascinate Android Development] skiddingus:
It normally works for me. If you are on Verizon...it could be the network tonight. They are supposed to be having some data issues. Front page news on Android Central.
[Fascinate Android Development] AtropineNa:
Hasn't been working for me times 2 days now boo don't know the source, what controls multimedia messages? I can send and receive normal texts np
[Fascinate Android Development] darkmage1991:
yea my ps3 controller was working just fine on cm7 but doesn't work on samsung and when i seen he said newer htc's and samsung's don't support the protocol i figured i would ask about adding it into samsung roms, but if he found a way around it thats good too :)

as for the in call reboots, its very scarce it may happen once every 2 days or so, its not often. so im not really worried about it.
[Fascinate Android Development] AtropineNa:
*Problem solved:

Not kernel / rom related, but app related. I really liked the AOSP Messaging app so I took the one from comm romm and just pasted it over in /system/app, messages sent/received fine, but MMS had issues. Just removed MMS.apk from /system/app and installed handcent => rebooted and voila! yay... night not completely ruined

Anyways, thats my rant; hope someone finds that useful
[Fascinate Android Development] darkmage1991:
ok, so i need to check the sixaxis dev's thread before i start asking for support in a kernel devs thread. i tried his new compatibility checker and it finds my ps3 controller just fine. looks like he is really close to getting it working on samsung.
[Fascinate Android Development] laureanop:
You replaced a system app integral to the Rom for one from a froyo Rom and it never occurred to you that that could be the problem?/me shaking head in amused disbelief

PWGB,TKSGB10-15, adren shot xix honeycomb2.03, ec09 radio.
[Fascinate Android Development] AtropineNa:
yes, thats how i found out after some trial and error... so yes, it has occurred to me
[Fascinate Android Development] laureanop:
My apologies sir, wasn't trying to offend you

PWGB,TKSGB10-15, adren shot xix honeycomb2.03, ec09 radio.
[Fascinate Android Development] davwman:
where did you get 10-15 tksgb
[Fascinate Android Development] Hypnosis4U2NV:
http://xdaforums.com/showthread.php?p=18460420

Sent by way of the GB delivery truck..
[Fascinate Android Development] dhouston10:
Lmao. Sorry to get off topic, but that's been the story of my life lately. Who would've thought?

Device info:

PWGB 2.3.4

TSKGB kernel v1012

Adrenaline XIX
[Fascinate Android Development] AtropineNa:
Kernel + ROM Combo is working well, just wanted to say thanks
[Fascinate Android Development] tulalhyt:
hmmm a little question

10 15 have a file for the zram configuration in init.d folder

while adrenaline shoot request a delete all files in init.d folder before installing

so how to use both of them ?
[Fascinate Android Development] comradesven:
zram should be considered an experimental feature for now and probably for always so just to be safe delete it and re-run zram enable after you've installed Adrenaline Shot if you want to take the risk.
[Fascinate Android Development] Skrazz:
Randomly rebooted 3x in 30 minutes after flashing the new kernel. Reverted back to 1015 without issue. This was on my way out to work (and I sit at Mac all day) so i'm unable to grab a logcat. Anyone have the means? The best I can do right now is export a log file out of my Android System Info app. That log doesn't seem to timestamp the events anymore so you'd have to trace back from 2 boots ago. One thing i noticed is quite a lot more battery tests run than i remember previously...
[Fascinate Android Development] dhouston10:
I do not know if this is the case for you, but mine did the same thing. Come to find out the voltage settings were deleted. When I reverted to what they were, it's fixed my reboot issue, as I was only running like 100mgz lol.

OP: So far this update is really solid. I am a little leary about trying zram, so I will wait until I see some more results. I have noticed a little more zip.

[Edit] possible bug: sometimes screen not wanting to come back on after manually turning off. Will update.

Device info:

PWGB 2.3.4

TSKGB kernel v1012

Adrenaline XIX
[Fascinate Android Development] dhouston10:
[EDIT 2] Yeah had problems still. Reverted to v1012 for now

Device info:

PWGB 2.3.4

TSKGB kernel v1012

Adrenaline XIX

OC'd: 1.44 gHz, deadline/ondemand
[Fascinate Android Development] comradesven:
Yea, my kernel is built with a different toolchain. This is when you format the cache and clean dalvik-cache - you can even do it with the recovery I posted.
[Fascinate Android Development] comradesven:
Back off on low UVs at lower MHz (give it a +25mV or two) especially on 100MHz and/or get rid of the 100MHz step
[Fascinate Android Development] comradesven:
Removed 1018 links for more investigation. I'll put out a release later.
[Fascinate Android Development] sarkozy:
10/12 is running great here on top of TSM1.0.

Oh, and it's been so long since I've flashed a voodoo kernel, take delight in the fact I'd forgotten about the "voice," which scared the absolute bejeezus out of me in my office at lunch. O.o
[Fascinate Android Development] thad2b:
Im running TKS 10/12, but was wondering if I should be running the cwm recovery from the op (blue recovery). Currently im still running the red 2.5.x recovery
[Fascinate Android Development] darkmage1991:
im using the red 2.5 recovery. it works great with no issues.
[Fascinate Android Development] droidstyle:
red 2.5.x is fine...
[Fascinate Android Development] skiddingus:
I'm running the same red 2.5.x. I wondered the same thing about the blue one mentioned here. I have had no problems with the red. What are the "minor bugs" that comradesven is talking about?
[Fascinate Android Development] comradesven:
I've updated the OP with links to a build that should hopefully not be quite as disappointing as what I released at 2AM today. So far so good on my end. My phone is flying on EH12 TSM Resurrection. I've not noticed any need for Supercharger or Adrenaline Shot at all, nor any memory manager apps. Let's hope this build is a keeper.

For me, the blue CWM appears to have a bug that prevents it from setting the time correctly. Every time it boots it thinks it's midnight on 1/1/2000 and keeps the time from that reference point, so if you make a backup it'll be labeled accordingly as being made at 12:02 AM on that day or whatever. I just rename the directory in /sdcard/clockworkmod/backup when I get a chance.

Other than that it has all the features I like, such as a Voodoo menu and working adb and sdcard mount. The main advantage of that version of CWM 2.5 is that it supports both Edify and Amend scripting, IIRC, but the thing is, nobody has been using Amend scripting in their CWM zip packages for *ages* now.
[Fascinate Android Development] darkmage1991:
your kernels have been great, but here lately you up the volume of the earpiece, and now its always too loud for me even when i turn it all the way down. is there anyway to remove the enhanced earpiece volume? i got great hearing so i have no need for the earpiece being so amped. i have to hold my phone away from my ear even when its turned all the way down =\
[Fascinate Android Development] comradesven:
I've had dock audio and making the earpiece volume boost level user-adjustible (like Efpophis's kernel) on the back burner for some time now, so just hang on a bit.
[Fascinate Android Development] jezze:
The Killer Stuff Gingerbread Kernel

just a pitch
[Fascinate Android Development] droidstyle:
FIXED!! :D
[Fascinate Android Development] skiddingus:
The red CWM does the same thing to me with the time stamps. No biggie for me. I'm putting the 1018 through the paces now. So far it seems great. Thanks.
[Fascinate Android Development] dhouston10:
Been running 1018 for about an hour now and so far no problems

Device info:

PWGB 2.3.4

TSKGB kernel v1012

Adrenaline XIX

OC'd: 1.44 gHz, deadline/ondemand
[Fascinate Android Development] laureanop:
The red CWR 2.5.x is simply the most reliable recovery for the fassy . It will nandroid restore back ups that others won't.

@comradesven just installed 1018 without a glitch and so far my phone is purring like a kitten with no memory killer.

TSM Resurrection 1.0,TKSGB10-18,XIX,ec09 radio.
[Fascinate Android Development] ekowanz:
Whats the best? InteractiveX or ondemandX?

Sent from my SCH-I500
[Fascinate Android Development] comradesven:
I did not know that about that particular CWM recovery. One of these days I really have to look into the recovery code in-depth.

According to the posts here 1018 try 2 looks like a winner. Also, now that I have a mediafire account it looks like a lot more people are downloading my kernels than I thought. It looks like I'm going to keep adding new features although I've already transitioned to mostly bugfixes and behind-the-scenes work until this thing is feature-complete, even if it takes some time. Thanks for your support, everyone.
[Fascinate Android Development] skiddingus:
Hmmm.... 1018 is working flawlessly for me but my wife just e-mailed me from work and said her phone keeps rebooting. They are configured exactly the same. both running 1200mhz with voodoo disabled for now. Anyone else having any trouble? It was fine all night last night. I don't understand what happened. I may just need to reflash hers tonight.
[Fascinate Android Development] AtropineNa:
Gonna have to agree on this one, volume in the ear piece is loud and has a buzzing sound at the lowest volume, going back to 10/12 but great work on your kernels nonetheless, love your kernels
[Fascinate Android Development] ssignature:
Well maybe for some of you, it's too loud, but for those of us that don't have the best hearing, it's great!

Maybe the answer is a volume boost check box.
[Fascinate Android Development] AtropineNa:
Nvm after some use the sound got better its perfect nownot sure what I did
[Fascinate Android Development] AtropineNa:
Anyone notice that thethe phone runs a constant 100 mhz when being charged or plugged?
[Fascinate Android Development] the entity:
When using deadline and ondemand, it's jumping around like normal for me.
[Fascinate Android Development] AtropineNa:
Yeah im running ondemandx and conservative, both run at 10

0 mhz when charging and the p hone is left alone screen off
[Fascinate Android Development] ibrubeer:
What is the story concerning deadline vs. ondemand? When would you use either?
[Fascinate Android Development] laureanop:
Dead line and on demand are two separate things

TSM Resurrection 1.0,TKSGB10-18,XIX,ec09 radio.
[Fascinate Android Development] dhouston10:
Well the 1018 kernel has been running good on my PWGB, but one thing I've noticed is it has been lagging more than it should. Any ideas?

Device info:

PWGB 2.0b3

TSKGB kernel v1018

Adrenaline XIX

OC'd: 1.44 gHz, deadline/ondemand
[Fascinate Android Development] ibrubeer:
Maybe I have been thinking about this wrong. Can you/do you go into all/multiple I/O settings and change them? Or do you just choose one, and the one you see is what your are using?
[Fascinate Android Development] comradesven:
I'm not too happy about people having instability and reboot problems. This is what happens when you don't have any beta testers yea? And personally I've had only like 3 or 4 reboots total spread out over a few weeks except for the first 1018 I released without doing any testing after switching toolchains and promptly rereleased, which is low enough that I have no idea whether it's my kernel.

For now I whipped up a test build using the old Tree RCU to see if that fixes reboot problems for those of you who are having them and you can find it here: (URL REMOVED. TRY 1021 PLEASE)

So if you had stability problems I'd appreciate it if you tried out this test build and let me know if that was the problem. Depending on how things go I might do a couple more test builds.

Either way I've started a code rebase which should be done sometime this weekend and go from there. Thanks for bearing with me.

Edit:

I/O scheduler and CPU scheduler are not the same thing. CPU scheduler controls how the CPU switches between available clock frequencies. I/O scheduler controls how Linux accesses the available storage space. For example, one of the old I/O schedulers Linux used to have even tries to compensate for the rotational latency of hard drives and deadline (before the tweak I put in for flash, which is not a spinning hard drive) maintains a queue of unfulfilled read requests and inserts new ones where they would be fulfilled more quickly.

Voltage Control allows you to choose which CPU scheduler and which I/O scheduler you use, and also allows you to choose which CPU speed steps are available and how much voltage will be supplied to the CPU at each of those speed settings. Then it saves the settings so that they are automatically applied every time the phone boots. Hope this clears up some confusion.
[Fascinate Android Development] dhouston10:
^this is one of the reasons I use your kernels. Not only do you have a great product, when things go haywire on devices you don't sit back and do nothing. Thanks for all your hard work dude.

Device info:

PWGB 2.0b3

TSKGB kernel v1018

Adrenaline XIX

OC'd: 1.44 gHz, deadline/ondemand
[Fascinate Android Development] comradesven:
Well, sure. I'm just one random dude on the internet with a bit more knowledge than most about how computers work. I may not have a clue about "grammar" and "spelling" of the C programming language and I can't write a damn thing from scratch but I can look at some code and work out what it's trying to do and apply other people's git commits and make a few modifications of my own if it comes to that. Basically what's happened is I've integrated too many things that I'm not sure what they do because they fix this thing or the other at a really low level (to satisfy the computer scientists, if you will) and aren't features that I'm adding in that I've had experience with before in previous Froyo TW and AOSP kernels and somewhere some instability got introduced. My rebase will only have things I understand in there so no features will be lost and hopefully in the process of doing that I can find out which commits are the ones that do break things for people.

No beta testers, this kinda thing happens. That's why it's alpha ;) But I can't just watch when 100-150 people have tried out my kernel just once and a good number of them are still using it. As much as I started with the best of intentions (hey guys, how about some real developer use these hax as the base for a real kernel) I've been doing that work anyway and not completely failing so I feel an obligation by this point to myself and others.
[Fascinate Android Development] s44:
No issues (lag or stability) on 10/18 for me. But I've been on less than a day... I did switch to ondemand from ondemandx right away.
[Fascinate Android Development] dhouston10:
^well I would be willing to beta test, but the only feedback I would really be able to give would be real world performance, I wouldn't have any recommendations of.coding or scripting or anything.

Device info:

PWGB 2.0b3

TSKGB kernel v1012

Adrenaline XIX

OC'd: 1.44 gHz, deadline/ondemand
[Fascinate Android Development] skiddingus:
I just want to give an update on this. Both phones have been running fine since the one hiccup that my wife had. I couldn't figure out what happened so I reflashed it to be same. Both phones are running fine. They do seem to have an occasional hesitation when making a selection. The benchmarks don't show the lag but the real world use does.
[Fascinate Android Development] QuattroMechanic:
Updated to 10/18 and reboots on every call but only after a minute or so. No other issues and gallery is a little quicker

Gonna try the 10/19.
[Fascinate Android Development] the entity:
I've been getting the in call reboots on the last 3 releases, now on 10/18 . Once I get home I'll test 10/19. can't flash with cwm.

*Did a test call, and did not have a reboot. So far so good!
[Fascinate Android Development] icemanwbs:
Where is link for 1019 ?...I don't seam to have any issues with 1018 so far. Disabled voodoo lagfix, maybe that has something to do with problems?
[Fascinate Android Development] icemanwbs:
Check that. Maps freeze up now. :(
[Fascinate Android Development] AtropineNa:
Anyone know what CPU governor the older 10/10 or 10/12 kernels are supposed to be run in? OnDemandX? Conservative? Looking for just reliable use and great battery life
[Fascinate Android Development] comradesven:
The older kernels should probably just use ondemand.
[Fascinate Android Development] dhouston10:
comradesven, i haven't seen this suggestion on here, forgive me if it is. But have you considered the soft key backlight time out? Like when you press one of the buttons it will stay on for only a couple of seconds and go out instead of being on all the time?
[Fascinate Android Development] s44:
Actually, you currently don't even have to press a button... it goes and stays on with the screen. Ack.

Ooh... smartass. (But I've just calibrated my battery! :/ ) What are the two speed targets you're using?
[Fascinate Android Development] sendan:
I prefer that they stay on the all time. Not saying it shouldn't be implemented, but if it is it would be nice if people had an option.
[Fascinate Android Development] comradesven:
#define DEFAULT_AWAKE_IDEAL_FREQ 800000
[...]
#define DEFAULT_SLEEP_IDEAL_FREQ 400000
[Fascinate Android Development] jcurley:
Trying 10/19 now. Have has the random reboot when the system gets bogged down.

Does 10/19 have the memory killer adjustment?

Pwgb

Tks 1015

Adrenaline XIX

mem optimizer

Vm heap 48
[Fascinate Android Development] shag_on_e:
Seriously, there isn't much better than someone who releases something and backs it up with great support. I'm flashing this out of shear principle. Thanks man.

~~~~There is no spoon~~~~
[Fascinate Android Development] jcurley:
No doubt, flashing as soon as I get to my computer.

tsm 1.0

Tks 1015

Adrenaline XIX

mem optimizer
[Fascinate Android Development] AtropineNa:
Love the new OP, especially the enthusiam, thanks comrade
[Fascinate Android Development] FDro:
Can't help but applaud the ambitious attitude you took with this. What an awesome thing to see such concern and humility from a developer, glad to see your ego isn't bloated.
[Fascinate Android Development] jcurley:
Not sure if this helps, BUT, I Odin'd 10/19 about 2 hours ago.

I was deleting emails from the email client and jumped out to my home screen and got a reboot. I will let you know if it happens again. Unfortunately, I was not able to grab any logcat.

Other than that, This thing is flying fast!!! GREAT WORK!
[Fascinate Android Development] comradesven:
Haha, it's hard to have a bloated ego when I don't even know C and devbuild 1019 has at least one very serious problem in that it breaks speakerphone, proving once again that I am not a developer really. I am going to need to upload a new build tonight.

The main thing I want to know is if in-call reboots are fixed. Anyone? There's been a lot of downloads already, surely there is some preliminary news by now.

Either way I'm doing a complete rebase ASAP.
[Fascinate Android Development] Sorvisa:
I know nothing of how kernels work within the roms, but I'm wondering if maybe the different roms are causing some of the reboot problems?

I'm running the latest EH09 PWGB rom and your 1018, have had no problems. Of course I don't oc/uv either. It's the best combo I've ever used as far as battery life and overall snappiness goes. I came from the CM7 rom and have been using this setup for 3 days now.
[Fascinate Android Development] Skrazz:
Still waiting on a call back to give 1019 a test. I'll edit this post with my results. As for the questionnaire:

1. TKSGB 1018 TSM Res 1.0

2. reboots via earpiece and bluetoof

3. in-call only.

4. no other probs i've spotted.

5. Adrenaline Shot XIX only. (kept it simple)

6. 1019 seems a little snappier to be honest

7. touch-light timeout options.

8. Call me a Comradesven fanboy. As long as you're working on this kernel, it'll be my kernel of choice.
[Fascinate Android Development] laureanop:
@comradesven 1006 runs flawless. No re boots of any kind

TSM Resurrection 1.0,TKSGB10-06, XIX,ec09 radio.
[Fascinate Android Development] comradesven:
Well I've finished the rebase of all changes I made since 1006. Now that I have evaluated this new build it looks like I introduced some major, embarrassing bugs and broke Android's memory management by trying to improve Linux's in the older builds. Thankfully the kernel doesn't appear to have slowed down much after removing the questionable code and it retains all of the useful functionality, though it seems to take longer to settle down after booting. Bottom line is that everyone should switch off devbuild 1019 and pretend that the last week and a half never happened.
[Fascinate Android Development] mezster:
Yea it can be annoying when using a dock... is it possible to include a toggle for backlight key duration?
[Fascinate Android Development] Nemeth27:
I've been posting my.info on rootzwiki. Should I do it here instead. I just got my first reboot using 1019. Happened when could bogged down. Is the memory management you said was broken fixed in 1021 build? Thanks for all you hard work!
[Fascinate Android Development] comradesven:
Possible, yes. But I seem to recall touchkey backlights are controlled by the ROM.

Yes, Linux isn't killing Android apps when it's been running for a while and needs more RAM anymore but letting Android handle it as it's supposed to. People should really switch to 1021 whether or not they're having problems.

Personally I'm pretty sure things are fixed and that the occasional hot reboot I have isn't my fault but TSM's. I'm growing more cautiously optimistic.

That said if someone proves me wrong I will of course look into it some more.
[Fascinate Android Development] icemanwbs:
So where is 1021??? Can't find it
[Fascinate Android Development] jcurley:
Does the new 10/21 have the memory optimization or do I need to download that from the market?
[Fascinate Android Development] comradesven:
It has lowmemkiller values that work OK for now. If you want to get a memory management app from the market that's on you.
[Fascinate Android Development] comradesven:
Read in the announcement.
[Fascinate Android Development] jcurley:
Just finished booting up. Thank you for all your help with this Kernel. It has been a really snappy kernel.

DAMN! this kernel is really responsive. With work like this, I don't think I will go back to MTD.
[Fascinate Android Development] kleffman:
Damn I might have to go to this. I really miss BLN, sound, etc. Can't wait to hear if it's working out as a daily driver. Thanks for all the work on this!
[Fascinate Android Development] icemanwbs:
Just flashed it. Thanks Comrad
[Fascinate Android Development] laureanop:
Just installed 1021. I will report how it went later on tonight

TSM Resurrection 1.0,TKSGB10-06, XIX,ec09 radio.
[Fascinate Android Development] briguyy:
Do you mean 1021 kernel? Because on the op there is only up to 10/18..unless im not seeing something.

Thanks
[Fascinate Android Development] the entity:
It's in the op, under the section that says 10/21 announcement.