yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] pmichaelro:
I've been having some issues since using this kernel. If i want to use USB tethering, i connect the phone to my PC, enable the USB tethering option and my PC starts to move really slow, especially if i try to "Open Network and Sharing Center" or the adapter settings for the USB tethering. Anybody else noticed slow downs on the PC they use USB tethering with? I've got SGS2 ofc and Original Windows 7 Professional SP1, tried it on another Windows 7 Ultimate SP1 and still the same issue...can i solve this issue somehow? Please help. Thanks in advance!
[Galaxy S II Original Android Development] JmPTaz09:
U have to expect some problems if u oc ur chip that far! 1.2 ghz is enough for almost anything on this phone
[Galaxy S II Original Android Development] DefTaker:
:confused: Lots of people are OC'ing it to the max through setCPU (which is 1600Mhz) and they're rock stable on either Entropy's DD or Siyah's kernel. Again, maybe I got a "lemon" that can't OC past the stock 1200Mhz <-- that's why I'm going to give it another shot to see if the OC was the cause for the SoD.

Then again, I've been hearing a lot about ShoStock + Siyah = FTW <-- might give this combo a shot. :p
[Galaxy S II Original Android Development] mazroui:
your mA readings are good, I have seen a couple of times where i unplug and check my phone battery level increase 5-10% before it settles down and starts decreasing, setting up juice-de with -100 on all mhz running 100-1000 mhz, -ondemand and sio- my usage went down from 30-40mA to 2-6mA on an hours standby time.... very happy with todays performance starting from 10am at 85% and now its 1:32am at 60% with very minimal use of a few sms's/ 5-10 calls/ 20 mins of music on lunch break... not much screen on time tho and the highest wakelock is jd @ 2mins...

amazing work with the kernal Really!!!

((its became a habit to check gokhanmoral.com twice on daily basis XD ... cant use anything else ))

---------- Post added at 01:50 AM ---------- Previous post was at 01:41 AM ----------

If I remember correctly, many a SoD happen due to fast changes in freq/ their voltages...

u need to test out different governors first(on default voltages) and then test for stable voltages.

I Uv a lot thinking it will make a big diff, but it dont. now stability is my main concern, testing takes a lot of time but once done correctly u'll be loving ur phone all over again :P

wish you all the best
[Galaxy S II Original Android Development] pmichaelro:
Anyone experienced this issue?

Can somebody help me with an advice or what can i do to fix this issue?
[Galaxy S II Original Android Development] :
Never had any problems overclocking buddy to 1.6GHz no SOD nothing..Phone files:p
[Galaxy S II Original Android Development] veyka:
I have a fast PC (i7 2600k etc) and I find my computer takes some time to open network and connection centre thing on w7 for a while after the phone has been teathered, seems to happen while windows is identifying and setting the network type, this is a windows not phone problem.
[Galaxy S II Original Android Development] DefTaker:
Uh, yeah...that's my point...

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

Since I did NOT undervolt any of the frequencies, I wouldn't think that the phone would go SoD running an OC from 1.2Ghz to 1.6Ghz. Anywhoo...running smartassV2 governer with the STOCK 1.2Ghz to test if it'll go into SoD.

Could've just been a fluke as well...never went into SoD running unNamed (ANY version) with Entropy's DD.

Like I said, gonna give Siyah a few more chances but if I run into any more issues than yeah, back to Entropy DD I go.
[Galaxy S II Original Android Development] The_MutenRoshi:
Can someone help me with this?

My betterbatterystats results, 14h since charged, left 58%, only 1h screen on...

Wifi On (): 9 h 48 m 55 s (35335 s) Ratio: 66,1%

Awake (): 4 h 26 m 18 s (15978 s) Ratio: 29,9%

Screen On (): 1 h 3 m 15 s (3795 s) Ratio: 7,1%

Phone On (): 24 m 40 s (1480 s) Ratio: 2,8%

Then:

Wakelocks

=========

b (com.sec.spp.push.Samsung Push Service): 3 h 3 m 46 s (11026 s) Count:24 20,6%

AlarmManager (Sistema Android): 10 m 28 s (628 s) Count:3224 1,2%

And:

Kernel Wakelocks

================

"PowerManagerService" (): 2 h 59 m 24 s (10764 s) Cnt:(c/wc/ec)1876/0/0 20,1%

"deleted_wake_locks" (): 14 m 57 s (897 s) Cnt:(c/wc/ec)182233/0/1460 1,0%

Now I have freeze the samsung push service with titanium, lets see tomorow (wtf is this app that came with omega rom v10!?). And what about the kernel wakelock? 20% is tooo much!

Sent from my GT-I9100
[Galaxy S II Original Android Development] veyka:
Don't worry about that kernel wakelock, see here.

https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/PowerManagerService

Its the kernel wake lock to show all the user land wake locks. Aka now the push service is frozen it will be okey, try clicking the wakelock names in bbs for more details sometimes.
[Galaxy S II Original Android Development] ap20001:
2.6.7 for m250k cant solve the problem of weak vibration in m250s，cant anyone solve it?

or a new version for m250s?
[Galaxy S II Original Android Development] rajarshi10:
When will the next version be out?
[Galaxy S II Original Android Development] MistahBungle:
Go back a page & read Gokhan's post. He's busy with life stuff at the moment, so you'll have to be patient. Besides, this is probably the best version of Siyah to date, so who needs a new version ? :D
[Galaxy S II Original Android Development] Little Dragon:
Coming from standard miui and finding my battery life isn't as great. Still gonna keep with it as I love BLN that much
[Galaxy S II Original Android Development] poochewer:
I am extremely happy with this latest version. Battery and performance is exellent for me now since using the settings recomended by @geko95gek

Thanks gokh for your continued labours. We all appreciate it.
[Galaxy S II Original Android Development] 11768:
What's the new command to mount NTFS drive now? The previous one doesn't seems to be able to run.
[Galaxy S II Original Android Development] gokhanmoral:
I had some time while my gf was preparing the breakfast. I will upload 2.6.8 in 10 mins.

I hope some of your problems will be fixed.
[Galaxy S II Original Android Development] Little Dragon:
Nice! Will grab and try out shortly

Any quick changelog?
[Galaxy S II Original Android Development] droidphile:
Unmount first (since kernel mounts ntfs in read-only mode automatically), then remount in read-write mode.

umount /mnt/usb
/system/xbin/ntfs-3g -o rw /dev/block/platform/s3c_otghcd/sda1 /mnt/usb

Replace sda1 with name of partition(s) in your NTFS hd/usb stick.
[Galaxy S II Original Android Development] ziroxs:
Let him take his breakfast without stress ;)
[Galaxy S II Original Android Development] hawkerpaul:
I've lost all haptic feedback with 2.6.8
[Galaxy S II Original Android Development] pikachu01:
Hey guys, did anybody else lose their haptic feedback with 2.8.8? :)

Edit: Spoke too soon. Someone else got the same issue.

For now, let me remove all my scripts and try again.

Edit2: Nope, it's due to 2.8.8. Removed all my scripts and haptic feedback is still missing.
[Galaxy S II Original Android Development] crazykamui:
korea version is same

Not vibration , wifi on/off reboot ^^;;
[Galaxy S II Original Android Development] gokhanmoral:
I will compile again. since I don't use haptic feedback I did not notice the problem.

I temporarily removed 2.6.8
[Galaxy S II Original Android Development] droidphile:
I thought it was the problem with the module and tried removing and insmoding vibrator.ko. But didn't work.

Will wait for the modified release.

Btw, using Sourcery Codebench Lite tool chain huh :)

Even after many code cleanups, size is slightly higher as compared to 2.6.7. Is it any better than sourcery g++

EDIT: My bad, previously G++ is now known as codebench lite. I thought it's a new tool chain :o
[Galaxy S II Original Android Development] gokhanmoral:
it was just an experiment :)

just as initramfs cleanups which caused that vibration problems (wrong permissions)

my eyes thought the permissions were the same but obviously they were wrong. I missed shell vs system difference. anyway, I rolled them back and will release the kernel in 20 mins.
[Galaxy S II Original Android Development] gokhanmoral:
guys, I cannot delete the files from my hosting account because of people reposting the links in their forum and the files are locked now. although I have removed the links they are still being downloaded.

I hate to rename the files and post new links.

so, "please" do not post direct links in your forums or in other posts.

that makes my uploading process very hard and I may have to choose uploading the files directly to wordpress which will prevent you downloading files directly from your phone's browser.

EDIT: at last, the locks are removed. I have uploaded 2.6.8 again.
[Galaxy S II Original Android Development] hawkerpaul:
If I ever post a link, I just link it to your site Gokhan so that the end user can choose for himself.

You could either wait until the downloads are complete, or call the version 2.6.8h to create a new file name.
[Galaxy S II Original Android Development] rajarshi10:
Changes in 2.6.8 ? Better battery life?
[Galaxy S II Original Android Development] gmavro:
Thanks man ,

best kernel ever
[Galaxy S II Original Android Development] :
will i be able to use lulzactive app now in the newest version? Thanks again Gokhan so far 2.6.7 works great...
[Galaxy S II Original Android Development] pesho00:
Do You have plans for making it available for 4.0.3?
[Galaxy S II Original Android Development] :
he will release for 4.0.3 when the sources are out..he has stated this many times before my friend. so just be patient:)
[Galaxy S II Original Android Development] hawkerpaul:
I can confirm the haptic issue has been fixed.

Lightning quick response gokhan!

All looks excellent in the early signs.

Thanks mate. Great job as usual.
[Galaxy S II Original Android Development] forumlarabak:
Battery life?

Better battery life in 2.6.8?
[Galaxy S II Original Android Development] MistahBungle:
FFS. The kernel has been out for what, less than an hour...And you're asking about battery life ? Sheesh :rolleyes:

How bout you flash it, test it for a few days then come back & tell us what the battery life is like.

This goes for you too rajarshi10 :-/
[Galaxy S II Original Android Development] ct85msi:
haptic feedback works
[Galaxy S II Original Android Development] rajarshi10:
I tested 2.6.7 & the battery life was excellent.. TILL yesterday when display was eating up 80% of the battery & it drained like anything. So you never know when & how kernels can change the way they work.
[Galaxy S II Original Android Development] Hertz33:
Just flashed the 2.6.8 and everything is running super smooth.

2.6.7 was/is exellent, hoping for more of the same.

Thank you for your work Gokhan, Its very appreciated.
[Galaxy S II Original Android Development] kilian7th:
Sorry for my noob question, is it completly another kernel or a kernel siyah 2.6.7 update ?

It worked so well !

Thanks for everything you do even if you have a lot of things to do in the "true life" !
[Galaxy S II Original Android Development] ka2uki:
maybe 2.6.8 this change:"Modified GPU frequency setting code a bit. if you use voltage control app or a script to set the second GPU step frequency higher than the third, the third frequency is disabled" make something difference?

running Nenamark2 2.2 use voltage control set gpu min clock to 267mhz ,max clock 400mhz..the same setting with 2.6.7..but 2.6.7 get 58.8-58.9 fps..but 2.6.8 only can get 54.1 fps..had running many times..
[Galaxy S II Original Android Development] MistahBungle:
That's right. Kernels can "change the way they work". My point about the kernel only being out for an hour or so stands.

HTF are we going to know anything about battery life after using the kernel for an hour :rolleyes:

The combined IQ of this place has been dropping by 10 pts a day lately, I swear :X
[Galaxy S II Original Android Development] kilian7th:
Thanks, thats a little more clear for me. Just trying now ...
[Galaxy S II Original Android Development] ka2uki:
and then in 2.6.8 lock the gpu clock to 267mhz..or min is 160mhz .max is 267mhz..the Nenamark2 2.2 result is 54.2FPS the same with min gpu clock is 267mhz max is 400mhz..

so i think ..400mhz is unable to use..although you set the max gpu clock is 400mhz?
[Galaxy S II Original Android Development] poochewer:
and this post means something?
[Galaxy S II Original Android Development] :
Guys i have a few questions please if someone can be kind enough to answer them for me thanks:

1) What is wrong with lulzactive app? I can not set anything on boot. When i do it keeps reverting back to the settings it came with. Is anyone else facing this problem? And if so is it something that Tegrak needs to sort out or something else?

2) if i can not use the app to tweak the governor then would thunderbolt scripts already have it tweaked or do i need to create my own one? Which by the way i would not have a clue hence why using the app..

Thank you in advance to whoever replies...By the way not using any scripts. Just flashed the kernel and using my voltage control settings that i always use:)
[Galaxy S II Original Android Development] ka2uki:
no~just a dout~
[Galaxy S II Original Android Development] pikachu01:
Wait a while after boot. Lulzactive app takes some time to get applied.

Yes, ThunderBolt! tweaks the lulzactive settings to have better performance and battery life :)
[Galaxy S II Original Android Development] :
Thank you sir for your replies. But the whole point is to use my own settings and try and play around with it...Would you suggest your scripts instead of the app then? Thank you again

EDIT: just tried the app set my settings rebooted waited for a few minutes and still nothing...settings got reverted back to the ones it came with....yes annoying but not a big deal.
[Galaxy S II Original Android Development] pikachu01:
You can still use the app. The app takes some time to take effect after boot. Just check it 5minutes after boot. It'll be the correct setting.

You can use my script if you want actually, or use my script then modify from there :)
[Galaxy S II Original Android Development] PhilAd:
i'll give 2.6.8 a try on CM7.1 (AOSP) and test if BT is maybe fully working now.
[Galaxy S II Original Android Development] :
thank you..i shall give it a try and report back to you..many thanks for your help:)

EDIT: waited five minutes and still reverted back to stock settings on the application..never mind like i said not a big deal i just use my voltage control settings and learn how to modify a script.:) thanks again for your help...hopefully tegrak can look into it regarding his app
[Galaxy S II Original Android Development] cooldfuzion:
A question Pika, every time that i install a new kernel do i have to install ThunderBolt again?

Thanks
[Galaxy S II Original Android Development] pikachu01:
You should, as there is a chance that the kernel dev wipes the init.d before install.
[Galaxy S II Original Android Development] :
Pika i waited like fifteen minutes and still app did not work...Think i might have a look at your scripts.:)
[Galaxy S II Original Android Development] pikachu01:
Hmmm. Yeah, you can use my scripts and tune it from there too :)
[Galaxy S II Original Android Development] :
will do..question though why app not working though? would it conflict with something?
[Galaxy S II Original Android Development] Gowind:
Guys, I need your help....

My Gs2 screen has lost Its oleophobic coating at some places and today the service center has replaced it with a new screen. As per they have told me, they didn't mess with my system and Rom. But after the replacement i saw that the screen has become noticeably dark.

Now the real issue. My Proximity sensor is acting weird. when i make a call, the screen goes off and wont turn on even after the call is cut. i need to plug my phone to the charger to get my screen on. When i receive a call, the screen will not turn off. It will be lit even when its close to the face. I checked the Self Test mode and noticed that the screen is green and it vibrates when i test sensor. In normal cases, it should do that only when you put your finger above the proximity sensor.

So all my expert friends out there and android Gurus,

1. Is my Proximity sensor broken?

2. or can it be related to software, some thing related to the rom and kernel?

3. Can this be fixed from our end rather than taking it to the service center again because the self test mode was 'Greek and Latin' to the service center guy. He got nervous when i showed him the screen and told me that we don't actually use this kind of stuffs to test the phone :p lol.....

Ps: Guys, please don't flame me for asking this here. I took the liberty because this is one thread where almost all Android Gurus hangout. :D
[Galaxy S II Original Android Development] veyka:
Loop back bug is fixed, Ubuntu runs perfectly, thanks a lot for the new version!
[Galaxy S II Original Android Development] bclark:
I was just about to check, thanks for the update.
[Galaxy S II Original Android Development] gokhanmoral:
I fixed the problem which was preventing gpu frequencies that are higher than 300mhz being used as the second step.

I uploaded tar file, waiting for the lock to be released on CWM.

if you don't use 400MHz as second GPU freq, you don't need to download the new file. there is absolutely no difference other than fixing this problem.
[Galaxy S II Original Android Development] ka2uki:
;) thank you @gok!yes! the problem is fix!
[Galaxy S II Original Android Development] Hertz33:
Hmmm, flashed 2.6.8 about 3 hours ago and left the phone alone.

When i've turned it on it was awake the whole time.
[Galaxy S II Original Android Development] seaweeduk:
yeeeeees :D

great work going to flash this soon will be sending you another donation soon gokhan
[Galaxy S II Original Android Development] MemoryController:
Is 400mhz for gpu dangerous??? Stability? Thx in advance!
[Galaxy S II Original Android Development] ka2uki:
in my point ..NO..i had use this for a long time~:D
[Galaxy S II Original Android Development] CamoGeko:
Deep sleeping here like a polar bear in hibernation. :D

Try wiping cache and dalvik cache (or flashing a kernel cleaning script) then re-flashing the kernel. Oh and don't forget to remove VC settings first.

PS. 2.6.8 working fine with mycfg v0.3 too. :) Although I had to remove VC boot settings before flashing, otherwise got a bootloop with the config in place.
[Galaxy S II Original Android Development] seaweeduk:
Still getting

when trying to connect after running ubuntu.sh

when trying to connect using 2.6.8 even tried both the .zip and the latest .tar is a logcat of any use I couldn't see much in there relating to the issue random reboot has stopped but I must admit I hadn't noticed this in the last few versions anyway...

edit: should say the script itself seems to always fun ok
[Galaxy S II Original Android Development] ka2uki:
@gok! 2.6.8 is really good!it's the best kernel i never use before.the big change is game performance..in 2.6.7..maybe the reason is the 3rd GPU step..in 2.6.7 ,when you play a game called"ban ban racing" (you may download it in sansung app ,it's free)..in the beginning ,the game is smooth..but after..the game running is very lag.the game run like a movie play 2xslow..but in 2.6.8 gok chang that:"Modified GPU frequency setting code a bit. if you use voltage control app or a script to set the second GPU step frequency higher than the third, the third frequency is disabled." and then i run this game again..it's super smooth..no this problem any more!so I think maybe the 3rd step GPU clock cause the problem..i believe that..in the future version..use the Modified GPU frequency setting code like 2.6.8..SiyahKernel no only in daily use, but also in game play is also the best kernel in SGS2!~
[Galaxy S II Original Android Development] lpsi2000:
Exactly what I said previously, it never fails
[Galaxy S II Original Android Development] ercxar:
anyone tried to change charging mA? in v2.6.7 I've tested both under 450mA and over 650mA to take effect and felt no difference between them, the charging time was about 3hour and half while in 450mA it has to take 4hours to charge if I'm not wrong, in new release right now that my phone is charging I feel no difference in 450mA and 650mA, Can someone confirm this? I need two days to make sure they have differences or not.
[Galaxy S II Original Android Development] rajarshi10:
I've wiped both cache & dalvik cache. Do I still need a kernel cleaning script? :p
[Galaxy S II Original Android Development] stevehkim:
you can slide the charging current to max and it wont make a difference. our sgs2 only sees 2 charge currents. wall charger and usb charger. wall being 650 ma i believe and usb being 450 ma.
[Galaxy S II Original Android Development] arch-angel:
For miui rom u need to check mitalk setting because it constantly check your online status except on offline hours
[Galaxy S II Original Android Development] ercxar:
I knew that, expect the one that you told wall charger only have one charging current? and only 650ma? Are you sure? Cause I read few posts a few weeks or maybe month ago about wall charger only can be 450ma or 650ma nothing between, below or above these two. Am I wrong?
[Galaxy S II Original Android Development] stevehkim:
you could be right. not too sure but i know the wall charger max is 650 ma.
[Galaxy S II Original Android Development] gokhanmoral:
you are right. we have 2 (in face 3 but only 2 of them are useful) charging modes: 650 and 450. I removed charging current modification description from the first post because we cannot modify it really, but only set it to 450 or 650.

defaults are 650 450 450 for AC, MISC and USB modes respectively.

siyahkernel defaults are 650 550 450 which is actually 650 650 450. anything above 450mA will set your charging current to 650.

increasing MISC mode current can help charging your phone with some car chargers faster.

if you are using a charger which is detected as USB port you can also increase USB mode charge current but be careful with that, that may cause problems with your computer's USB port.

I did not remove the charge_current interface not to break the compatibility with voltage control app.
[Galaxy S II Original Android Development] ercxar:
yeah max is 650ma, I barely remember that wall charger have both 450 and 650, but the thing that I was saying is in v2.6.7 there is no difference to change between wall charging current 450ma and 650ma, and I feel that it still has no difference in v2.6.8. (Using VC app)
[Galaxy S II Original Android Development] seaweeduk:
Anyone got ubuntu to successfully boot yet?

thread is here: http://xdaforums.com/showthread.php?t=1223128
[Galaxy S II Original Android Development] gokhanmoral:
if it counts, I did :)

I downloaded the bigger image, extracted it to /sdcard/ubuntu

and copied the ubuntu.sh to the same directory.

I modified the script so that the loopback device is mounted with ext4 (but ext2 should work fine too)

I used scriptmanager and I even created a shortcut on my home screen with scriptmanager widget. I run the script (ubuntu.sh) with root permissions using scriptmanager.

and I used RemoteVNC to connect to localhost 5900 with pwd ubuntu.

it runs flawlessly.
[Galaxy S II Original Android Development] veyka:
Yes, any problems you are having are user related or rom related, kernel is fine. I used the lite Ubuntu img and everything works fine.
[Galaxy S II Original Android Development] seaweeduk:
strange that it doesn't work for me same image works fine with the cm kernel, i'll look into it more when I get some time tomorrow might need to redownload the image...

Thanks for your hard work I'm glad people can run this on your awesome kernel now

edit: working for me now I think I had a brainfart earlier and wasn't running the script as root :)