yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] garyd9:
I just put about 16GB of music on my external microSD card (lexar class 10 32GB card), and obviously "Media Scanning" takes a while now. Are there any suggestions for speeding up that media scanning? (other than removing some of the music.)

Currently, I'm using the same I/O scheduler settings (bfq) that were set pre-set into the 12/1 and earlier DD's. I'm not really familiar enough with the characteristics of these microSD cards to make an educated guess as to if this scheduler would be the best for this read-intensive application, or if some other kernel tweak would be a good thing.

If I remember correctly, most of the schedulers in the kernel were designed with spinning platters and seeking heads in mind, as well as a certain percentage of writes (which I expect to have very little of on the microSD card.) Perhaps the NOOP scheduler would work out well for this application?

Take care

Gary
[AT&T Samsung Galaxy S II SGH-I777] Rockliveson123:
flashed the 12/08 kernel and now the lock screen wake lag is gone.
[AT&T Samsung Galaxy S II SGH-I777] iRide113:
The market has a few pretty good apps to help your SD cache and help speeding up the media scan. Search for something like "SD Booster."
[AT&T Samsung Galaxy S II SGH-I777] autonomous-inc:
I really don't understand what any of you were talkin about concerning a lock screen lag. I played around with the 12/12 kernel, and it was perfect. I'm testing siyah's kernel now, and to be honest, the touchscreen is a bit off. 12/12 kernel made my phone's touchscreen damn near perfect.

I gotta say, siyah's kernel versus entropy's, I don't see much of a difference at all, aside from getting a cwm app for my phone, courtesy of siyah I'm guessing. Anyway, goin back to entropy's solid kernel on Unnamed 2.1.1 tonight.
[AT&T Samsung Galaxy S II SGH-I777] Jonnyredcorn:
I had this happen to me as well. In running unnamed 2.1.1 & 12/8 I reset my pattern and I haven't been able to reproduce since, however I do have a slight wait for the lock screen to pop up. Its kinda annoying
[AT&T Samsung Galaxy S II SGH-I777] Peaster111:
I couldn't agree more regarding the touchscreen. The updated makes a subtle but noteworthy change. The very minor issue (in my opinion) effects only the lock screen and not everyone has been effected by it. Overall Entropy's kernel is and has been a keeper. Good stuff! It's all about making it better. I'm still using it of course.
[AT&T Samsung Galaxy S II SGH-I777] bigblue95z:
This happens when a pattern is set and a new ROM is flashed. Just taping a dot gets you in. If you set the pattern again it will again require the correct pattern. Pretty much have to do this after each ROM flash. Ran into this on UnNamed a while back. Lock screen pops up like its set but its really not.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Well that's just normal behavior for our phone - it takes 650 msec just for the CPU to wake up from suspend.

At this point, the touchscreen failure to register the first touch on wakeup is so subtle and rare compared to the responsiveness improvements I'm going to be going ahead and will revisit the calibration lag once I've fully updated to update3 if I have time. It's one of those things that happen so rarely and are so minor they're almost impossible to debug.

One thing I've noticed is sometimes my swipes fail to unlock if I press too hard - I see that the touch is being registered and the screen begins to move with the swipe, but it doesn't follow the touch all the way. So maybe try a lighter touch.

I'm going to try and put out an update with a few new patches from update3 - it'll likely be the last release before the new year, I'm getting busy with packing then I'll be visiting family for a week.
[AT&T Samsung Galaxy S II SGH-I777] Peaster111:
I wouldn't lose any sleep over the "wakeup touch issue". It is such a nit. If that is all we can find "wrong" with the kernel, your sitting pretty damn good! I'm going to go with a lighter touch. :p Maybe we should take a poll? Guys versus gals and see who has the heavier hand. :D

Have a Merry Christmas with the family and we'll pick up next year. Thanks for all the efforts.
[AT&T Samsung Galaxy S II SGH-I777] EGBTMagus:
Would there be any reason that my device is no longer stable at 1.4ghz after trying out the Siyah kernel and then switching back to Entropy kernel? I made sure to wipe the device prior to reflashing and even changed the rom (Running the newest Unnamed).

I was perfectly stable at 1.4 but now I can OC to it but it randomly reboots my device.
[AT&T Samsung Galaxy S II SGH-I777] Alucardis666:
Can't wait for the next release. This kernel just keeps on getting better and better.
[AT&T Samsung Galaxy S II SGH-I777] Jonnyredcorn:
What exactly is update3?
[AT&T Samsung Galaxy S II SGH-I777] Peaster111:
It could be due to a couple of reasons. OC Stability varies phone-to-phone and kernel-to-kernel. Stability at 1.4 using one kernel doesn't necessarily translate into stability using another kernel, even on the same phone. My phone works fine OC'd up to 1.6, but I keep it at 1.4. The difference at 1.6 is negligible and it eats a lot more battery. 1.6 is just not worth the battery loss.

Two things I would try:

1 - Don't OC for about a day and see if the stabilizes. You may not notice much if any difference between 1.2 and 1.4

2 - The Siyah kernel leaves remnants on the phone despite your uninstall/wipe efforts. The only way i know to clean it out entirely is using this script: samsung ultimate kernel cleaning script The script seems to work well.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Samsung's latest kernel source code drop for the I9100.

I9100 has had four source drops so far - initial, updates 1/2/3.

We've had only one so far. I9100 update3 seems a bit newer than our source code.
[AT&T Samsung Galaxy S II SGH-I777] EnemyOfGlaDOS:
thanks for all your hard work and time spent developing your kernel. It's appreciated, as well as all the helpful info you provide. Glad your around

confirmation# 5RP9753793520400G

merry christmas too!
[AT&T Samsung Galaxy S II SGH-I777] pinoymutt:
Since KK6 was "officially" launched just this week by the Death Star, do you anticipate seeing Samsung dropping the source for the kernel anytime soon (not sure if the kernel was really updated in the KK6 release over stock)...
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
No clue - Very often a kernel does not appear to have any changes other than initramfs, so source drops don't always happen.

It's not like the Infuse where there are CLEAR driver incompatibilities beyond just the initramfs.
[AT&T Samsung Galaxy S II SGH-I777] NJGSII:
Entropy, been using your 12/12 exp release again over a day now and I have been unable to produce the problems that have been occurring with the unlock screen.

I'm probably going to stick with this kernal from now on as it has give me the best of everything.
[AT&T Samsung Galaxy S II SGH-I777] :
Will we be seeing a Christmas kernal present here? Sure would go nice with my shinny new UnNamed 2.2.0. :D
[AT&T Samsung Galaxy S II SGH-I777] :
Entropy, I noticed since I started using your kernel that bluetooth HID devices (like my keyboard) will pair but not connect. Is the stock kernel the only way to connect HID devices?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
No clue - this is the first report I have seen of this. More details (which ROM, etc)? dmesg/logcat of some connection attempts please?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Just uploaded 12/21 Experimental. Standard will come later tonight - I've gotta run out for some errands.

It has some initramfs updates from the UCKK6 kernel image that might fix wifi for people running straight UCKK6. This is not tested.

Also contains the following from I9100 Update3:

Wifi drivers (Tested, both client and tethering, with VillainROM 3.0)

Bluetooth drivers (minimal testing, sorry, been busy)

USB Host drivers (Untested, I don't have an OTG adapter)

Touchkey drivers (Basic functionality fully tested, BLN only tested using the basic BLN Control test function.)
[AT&T Samsung Galaxy S II SGH-I777] gtg465x:
Oh boy. KK6 based ROMs may need updates to work correctly with 12/21. So much to test. Headaches.
[AT&T Samsung Galaxy S II SGH-I777] :
Be happy to help out. I am running Unnamed 2.1.1 right now. How would you like me send the logs? via email?
[AT&T Samsung Galaxy S II SGH-I777] gtg465x:
Might want to see if bluetooth HID was fixed in his 12/21 kernel before going through the trouble of getting logs.
[AT&T Samsung Galaxy S II SGH-I777] eep2378:
Thanks Entropy! Just flashed 12/21 exp. Will report back if any issues. I'm running crysis 2.0.
[AT&T Samsung Galaxy S II SGH-I777] Peaster111:
I thought you were going to chill for the holiday's. You just can't stop...You're as bad as the rest of us. ;-)

EDIT: btw I'll check out the USB otg after I get back from the movies.
[AT&T Samsung Galaxy S II SGH-I777] gtg465x:
See if flashing this fixes bt hid: http://www.multiupload.com/HNATJGIMRI

edit: Seems like this may be working with the 1208 and 1212 kernels, but causing problems with the 1221 kernel
[AT&T Samsung Galaxy S II SGH-I777] Nizda1:
I've been having same problem with hid Bluetooth. My logcat has some pretty similar errors as his.

Sent from my SAMSUNG-SGH-I777
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Oh, do you think the KK6 workarounds in custom ROMs will break with the updated initramfs?

It hasn't broken XXKI3, I need to test UCKH7. I won't get a chance to play with KK6 until next week at least.
[AT&T Samsung Galaxy S II SGH-I777] Nizda1:
Gtg is very close with that fix. It connects but bluetooth goes crazy and turns on and off on a loop

Sent from my SAMSUNG-SGH-I777
[AT&T Samsung Galaxy S II SGH-I777] :
Actually worked with the version of the kernel that was packaged in unknown 2.1.1. With 1221 Bluetooth does keep cycling.
[AT&T Samsung Galaxy S II SGH-I777] Simba501:
Could you make a semi-transparent notification pull down mod (compatible with Cognition Beta 1) that retains the stock look provided by Cognition?
[AT&T Samsung Galaxy S II SGH-I777] eep2378:
Entropy, this is a rock solid release(10/07 build, no doom). been running it since last night with no issues at all. Also running the cpu governor on demand init.d script with some nice results.

Battery standby times have been great(unplugged for 5hrs still at 100% :)) Also when looking in Setcpu, the processor seems to be sleeping well, at 200mhz 92% of the time. Only change I made in Setcpu was set Ignore Nice load to 1.
[AT&T Samsung Galaxy S II SGH-I777] manbeer:
Looks like I got one of the crappy phones that can't handle overlooking. Going to reflash non doom cause I'm stuck in boot loop.
[AT&T Samsung Galaxy S II SGH-I777] xx_bluedev_xx:
New to OC/UV

Hey can someone that has done this provide me a little assistance on good numbers to OC/UV, I have never actually put the numbers in myself always used a preset governor where it was already OC'd/UV'd thanks in advance!
[AT&T Samsung Galaxy S II SGH-I777] eep2378:
This phone is fast enough for every task without overclocking. If its really that important, you may have to deal with some inconsistencies.
[AT&T Samsung Galaxy S II SGH-I777] manbeer:
I know, I I just see everyone else doing it and I'm jealous

I'm usually underclocked to 1.0 most of the time
[AT&T Samsung Galaxy S II SGH-I777] eep2378:
You can start here:http://xdaforums.com/showthread.php?t=1036020

This is from the captivate forum, but many of the basic principles apply :)
[AT&T Samsung Galaxy S II SGH-I777] mrRobinson:
so if i install the doom how do i access the overclock /uv settings? didn't see that anywhere.

and if i install non-doom i just need to create the /etc/init.d folder myself?
[AT&T Samsung Galaxy S II SGH-I777] shishir95:
The overclocking works! I overclocked to 1.6 GHz, got over 115MFLOPS in Linpack and then the phone promptly crashed lol.

I don't plan to use overclocking, but nice to see that it's there.
[AT&T Samsung Galaxy S II SGH-I777] xx_bluedev_xx:
Thanks a lot for your help!
[AT&T Samsung Galaxy S II SGH-I777] eep2378:
OC/UV settings can be accessed with SetCpu.

Yes init.d folder needs to be created by you, as stated in OP. Put it in system/etc
[AT&T Samsung Galaxy S II SGH-I777] shep211:
My sgs II loves these OC settings. I locked the max & min mhz in setcpu at 1600, 1400 & 1200 & tested each OC & voltage setting for over 1 hr. Every cpu is different so this may not work for you.

1600

1450

1400

1300

1200

1275
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Damn - task650 is here. Running KME 7.1 on my 10.1, love it!

SetCPU doesn't actually give you sleep statistics. CPUSpy does. For me, I get around 95% deep sleep when the phone is idle on my shelf.

I wish it were lower, but I'm in a small town with moderate signal, AT&T doesn't support Fast Dormancy, and the big US providers are known for doing wacky things with their data networks that are bad for battery life: http://www.eecs.umich.edu/~qiangxu/paper/sigcomm11_wang.pdf

Advice: If you set overclock or undervolt settings in SetCPU, do NOT set "set on boot" until you're stable.

The "doom" version SHOULD be stable at the default settings.

init.d doesn't NEED to be created - it only does if you want to run scripts from it. If you don't create it, it'll do nothing, just like before.

However I think some overclocking programs (such as Xan's Voltage Control) use init.d to set OC parameters earlier in the boot process. IMO this is a bad idea as it's a lot hard to clean out/undo/disable those settings. A bunch of people who used VC had problems when they came from the Infusion overclock kernel to my Daily Driver on the Infuse due to different VC approaches.
[AT&T Samsung Galaxy S II SGH-I777] TheTodFather:
The DoOm kernel is rock solid!

Are you going to try and uncap the FPS? With the phones specs it would eat through the extra "work".

Thanks!
[AT&T Samsung Galaxy S II SGH-I777] mjgspr95:
+1 I did have to go back to ondemand for stability at 1.6ghz.

i777 stock

Entropy512 Doom

onepointsixingit
[AT&T Samsung Galaxy S II SGH-I777] mjgspr95:
Yes, that's a good look

i777 stock

Entropy512 Doom

Onepointsixingit
[AT&T Samsung Galaxy S II SGH-I777] TheTodFather:
Go back to from what? Performance? Ondemand is pretty aggressive, so you had me wonder what you had it at? Hadn't had one problem yet, phone is cool as an ice cube!
[AT&T Samsung Galaxy S II SGH-I777] mjgspr95:
I used voltage control (market) I didn't change uv (for now) settiings I just moved scaling range to max and chaneged govenor for stability.

i777 stock

Entropy512 Doom

Onepointsixingit
[AT&T Samsung Galaxy S II SGH-I777] eep2378:
Sorry, I should have been more clear, its NEEDED, if you're gonna use it :p
[AT&T Samsung Galaxy S II SGH-I777] dayv:
Running 10/20/11 doom cwm kernel for a few hours now - slight uv no oc. Early results seem very promising, stable smooth good battery results.

On a less important note, can anyone tell me if it is possible to change the initial boot screen back to SGH-I777 from I9100 and s still run this kernel, again not important but if anyone knows it would be nice
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Bluetooth HID is working fine on UCKH7 and XXKI3.

So it's a 2.3.6 problem in general, or a UCKK6 problem specifically.

Odd question - does BTHID work with the stock UCKK6 kernel?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
I just realized - that's a logcat, not a dmesg...
[AT&T Samsung Galaxy S II SGH-I777] highaltitude:
Just installed the newest 12.21.11DD and it seems to have fixed the broken wifi on the UCKK6 2.3.6 update. So far so good.

edit: wifi definitely works! I hit over 18mbps dl, and 3mbps ul. Thanks Entropy512!
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Just uploaded Standard.
[AT&T Samsung Galaxy S II SGH-I777] gtg465x:
Wait, so the fix I posted works with 1208 and 1212 kernels?
[AT&T Samsung Galaxy S II SGH-I777] Peaster111:
I played with USB OTG a bit. It seems to work fine. The only issue is that I can't get it to unmount now. I have to pull it. I previously was able to unmount. No biggie though. The important thing it that is mounts! :)
[AT&T Samsung Galaxy S II SGH-I777] :
When I restored to nandroid of your 2.1.1 rom, the fix worked (that version of the rom used 1208, correct?). When I flashed the 1221 kernel, it appeared that the bluetooth would connect

briefly, but then very quickly Bluetooth would shut off and on and continue to cycle off and on.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Grab both a dmesg and logcat of that please.

I may be able to do a test build in a few days to see if it's the initramfs or the update3 changes...
[AT&T Samsung Galaxy S II SGH-I777] :
Will do. . . I just have to learn how to capture dmesg. . . I will hunt around for directions and post once I have learned how to capture the dmesg.
[AT&T Samsung Galaxy S II SGH-I777] madquack:
adb shell dmesg > dmesg.txt
[AT&T Samsung Galaxy S II SGH-I777] LGSilva:
Hey Entropy, can you add the new voodoo audio driver to the next kernel release?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Until I see a post from Supercurio that the driver is ready for integration and not just some experiment, no.

I recall talking to him and mentioning that a kernel dev had released a kernel with Voodoo Sound for the Tab 10.1 - he was NOT happy because he said that Tab 10.1 VS support was experimental. (Started a rant about patch-o-matic kernel developers from him... :) )
[AT&T Samsung Galaxy S II SGH-I777] AtlanM87:
Anybody running Entropy's 1221 with UnNamed 2.2.x? Thanks.
[AT&T Samsung Galaxy S II SGH-I777] :
Bluetooth HID

Holy Crap!!! Just when I go to get the logs everything works perfectly!!!!

Resotred my unkown 2.1.1 vanilla from a nandroid

Flashed the 1221 experimental kernel

Flashed GTGs fix

Booted up and connected bluetooth no problem.

Just to confirm, in the "about" section it says I have Kernel 2.6.35.14 and baseband I777UCKK6. I assume that I got the right kernel installed . . .

I'll mess a little to see if I can break it. The only thing different from my last attempt was that I flashed GTG's fix on to unnamed 2.1.1 and tested. and then flashed the 1221 kernel, rebooted, and had the cycling bluetooth. So maybe flashing a kernel after GTG's fix caused the problem?

EDIT: Flashing the Kernel after GTG's fix returns the bluetooth cycling problem. I have attached the dmesg and logcat files.
[AT&T Samsung Galaxy S II SGH-I777] hurley81388:
hi all, stupid noob question here.

i'm running stock, rooted android and have been reading the guide (plus others) here:

http://xdaforums.com/showthread.php?t=1311081

where it tells me to flash a kernel with CWM enabled. i want to go from stock, rooted OTA 2.3.6 which i have now to unnamed.

i read in the release notes from the first page of this thread that the 12/21 release is untested on the baseband i currently have from toe OTA 2.3.6 (UCKK6) so i'm unsure if i should install the latest kernel or use the 12/8 one that is mentioned in the first post of the unnamed thread:

"Features:

-Based on UCKK6, Android 2.3.6

-Entropy's Daily Driver kernel (12082011) (governor set to on demand via init.d script)"

not exactly sure what that means.... thanks for your help in advance and sorry for being a noob. i searched as much as i could but couldn't find an answer so please don't flame me

EDIT: oh and i plan on installing the kernel using mobile odin and extracing the zImage as referenced as the preferred method in the guide
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
If your goal is to install UnNamed rom, then it doesn't really matter which version of the kernel you choose. Either will play well enough with UCKK6 for the short time you'll have them together.

When you install UnNamed full, it will install, I believe, the 12/08 version of the kernel, and then you'll have to decide if you want to update the kernel to a later version.
[AT&T Samsung Galaxy S II SGH-I777] Enzopreme:
hey man, sorry if this has been answered already, but i checked the changelog and didnt see the difference in the latest DD exp. version and the regular version. Whats the difference?
[AT&T Samsung Galaxy S II SGH-I777] hurley81388:
Oh OK so when you flash the unnamed ROM it automatically installs a different kernel? From what I read I was under the impression that kernels and ROMs were two separate things but I guess I was mistaken.

So when I flash the most recent version of Unnamed it will install the 12/08 kernel and change the baseband away from the UCKK6 I currently have to the previous version? So there are no wi-fi issues I need to worry about then if flashing the ROM will change the baseband away from UCKK6 and the kernel to 12/8?
[AT&T Samsung Galaxy S II SGH-I777] dalavar:
I have a question regarding this in the changelog: Bring in a few updates from UCKK6

I am running unnamed 2.2.1 and ever since the introduction of the KK6 modem my K9 mail has been locking up on me. Tried wipe install all apps from market no TiBu and still locks up. So I switched back to the KH7 modem and am currently testing that out and so far no locks. But if I use this Kernel with KH7 will those tweaks effect that?
[AT&T Samsung Galaxy S II SGH-I777] :
Kernels and roms are two different things, but UnNamed is a complete package that installs a kernal and a rom together (think of a combo deal). Since Entropy has a newer kernel available than what UnNamed is bundeled with, you can update and flash the kernal since a kernal is separate from the rom.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
I'm pretty sure it still has the 12/08 kernel. I only use the updates which don't include the kernel.

Baseband is the modem. This will be UCKK6 unless you change it yourself.

UnNamed 2.2.1 will show in About Phone:

Baseband Version: I777UCKK6

Kernel Version: 2.6.35.7

Build number: UnNamed v2.2.1
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Please repost these as attachments (just editing your post will do) - the dmesg is cut off early, plus it's hard to review them as small code tag blocks. :)

What may be going on is that a certain combo of kernel/btld binary causes Settings to get hosed up and unhappy.

I'm going to mess with it after Christmas probably. Which reminds me - need to download Unnamed to my laptop. :)
[AT&T Samsung Galaxy S II SGH-I777] AtlanM87:
UnNamed 2.2.1 works fine with Entropy 1221 after first round of tests by your's truly. Can't tell anything about battery life so far (of course).
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Read down through the Changelog to the first of the dual-release entries.

Main thing is 2.6.35.7 vs. .14 - .14 is a newer base but has at least one known regression in battery stats reporting. So far I've never noticed any significant difference between them.

ROMs and kernels are two separate things - However, many ROM developers include a kernel with their ROM to ensure that users are running a kernel they have tested as compatible. (e.g. they don't want to have "I'm running this with PoopyKernel 9001.0, your ROM sucks with it!" comments)

Not all ROM developers include modems - in fact Pulser (maintainer of VillainROM) rants about people who do it. This matters more in I9100 land though where there is much more variance in modem performance from region to region.

So if you want a different kernel than what a ROM comes with, flash the kernel after the ROM.

It's only a few small wifi changes - and I've tested backwards compatibility with UCKH7 and XXKI3 builds. There's rarely a significant dependency between modems and ROMs/kernels - you can run the KH7 modem with KK6, KK6 modem with KH7, etc.
[AT&T Samsung Galaxy S II SGH-I777] smknutson:
Really quick, the only wakelock I seem to have is a show keyguard wakelock. What does this involve?
[AT&T Samsung Galaxy S II SGH-I777] :
Done!!! Thanks for pointing out a "better way" Merry Christmas! :D
[AT&T Samsung Galaxy S II SGH-I777] Lord_Micron:
Mounts fine! Unmounting, on the other hand... :p

BTW - Running UnNamed 2.2.1 w/ DD_12212011_exp
[AT&T Samsung Galaxy S II SGH-I777] LGSilva:
I got this reply when I asked him about the i777 support: