yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Entropy512:
Hmm, that's a maybe on deleted_wakelocks being wlan_rx wakelocks after wifi is turned off - I should try experimenting with that - GM added a feature from my kernel to allow deleted_wakelocks debugging.

Also, while .12 fixes some issues with spurious wlan_rx_wake wakelocks that don't have incoming data associated with them - nothing can fix situations where incoming traffic from the chip is waking up the phone.

These situations can include:

1) Misbehaving apps

2) ARP traffic on your local LAN combined with a faulty ROM that inhibits the earlysuspend handler of the wifi driver (XXKI3 is confirmed to do this)

3) Broadcast traffic on your local LAN combined with the faulty ROM described above

4) The "BT-AMP" bug - This is confirmed to affect UCKK6, XWKK5, and XWKL1 at the very least - see http://xdaforums.com/showthread.php?t=1409513&page=4 for details on this bug, and http://xdaforums.com/showthread.php?t=1308030 for how to confirm

#4 is the first confirmed instance of an "Android OS bug" that is actually 100% a ROM bug, and it is ROM-dependent.

Edit: To clarify, on XWKL1 I could have caused the bug with some experimental wifi power management patches - I had no problems for 3-4 days until I tried an experimental patch - but I've seen plenty of confirmation for UCKK6 and XWKK5 with less "experimental" kernels.
[Galaxy S II Original Android Development] omniwolf:
ok thanks for the reply, i'll keep an eye on it tonight, maybe it's just a once off.

i am running a KK5 ROM. hm
[Galaxy S II Original Android Development] shawnaye:
wifi is really a tad weak on release 12.
[Galaxy S II Original Android Development] droid_1989:
Any news on whether Siyah Kernel will support ClockworkMod Touch?
[Galaxy S II Original Android Development] Crescendo Xenomorph:
Because Siyah got 8 step CPU freq instead of 7 (I was using Lulz Kernel) and I don't wanna overclock my CPU, so I set my max freq to 1204Mhz and since it got extra step, yeah... It become so close (1100, 1152, 1204).

I also tried to chmod to 444 and even 777, but those values still kernel default.

FYI: 1204Mhz@1200mV made my S2 warm for light use (imagine if I use it for gaming, it can jump to 40C in no time). That's why I want to kept my freq to stock and UV it.

Ah, I see... ^^ I tought it was for downloading or something for analyzing the script, since it become color-coded instantly... :p

No, it doesn't work, even with Siyah ver .11.

I was using Lulz Kernel, version latest, and it paired with Tegrak Overclock Ultimate, so I never use this kind of script before.

I tried to reflash the kernel (v .11 and now v .12) twice and cleaned dalvik and cache. Even tried to reboot after the first boot. Still the script (only for the CPUfreq) doesn't stick. :confused:

I already disabled Tegrak Overclock Ultimate before I flashed this kernel. :confused:

That's why I'm sooooo confused why only this value is kept reverting to standard value.... :confused:
[Galaxy S II Original Android Development] mekhonte:
I have a wake up issue. The phone it's on but screen won't turns on. Which log should I generate?
[Galaxy S II Original Android Development] veyka:
You could try to connect to it with adb and get a logcat and kmsg, otherwise reboot it using the power button (dont take the battery out) and once it boots up get a last_kmsg using the info i posted a few posts ago.

Edit: The first thing you should do it to remove any undervolting or overclocking or any custom scripts eg thunderbolt! etc and see if you still get the problem.
[Galaxy S II Original Android Development] networkn:
I put 2.6.11 into my phone (CheckROM v4) and now I can't get a GPS Lock. Anyone have any ideas what could be causing this issue?
[Galaxy S II Original Android Development] mekhonte:
I will generate logs next time.and I did clear vc and uv. But I've been using geko configs and thunderbolt with no issue from 2.6.7!
[Galaxy S II Original Android Development] UpInTheAir:
Normal stuff first, update agps data with gps status app, ensure options selected in settings/location and security, and or Try reflash your modem. Kernel flash shouldn't have changed anything.
[Galaxy S II Original Android Development] CamoGeko:
Set your lowest frequency step to 200Mhz. If it still happens, raise voltage on that step by +25 mV.

Sent from origin unknown.......CM9 Galaxy
[Galaxy S II Original Android Development] mekhonte:
good advise and will post how it went.
[Galaxy S II Original Android Development] kevin2210:
i install kernel KOR version 2.6.12 with XXKW8 original rom , plug in ear headset and run FM radio but when i turn this app on the device sudden reset , pl tell me why
[Galaxy S II Original Android Development] :
For some reason, I'm having a android system battery usage of 40%.

Where's my power doesn't show anything unusual and better battery stats doesn't either. I'm having 98% deep sleep.

Is there any way to find out whats exactly causing this high usage?
[Galaxy S II Original Android Development] caiston:
Can confirm the wlan_rx and wlan wakelocks changing to combined total for deleted_wakelocks when you turn wifi off and refresh BBS.

Have had this drain since .5/.7 and experienced it on wifi networks in two countries where phone was only common denominator.

Not had the massive drop of 10% an hour for a couple of releases now but the wakelock still shows for a few minutes whenever I turn wifi on.

Will try .12 today and see if it disappears!

Regarding the CPU sticking permanently at 800Mhz that I experienced after flashing .11, simple reboot fixed this and got 48 hrs with over 4 1/2 hrs screen on time (no wifi) so overall very happy :)

CheckROM RevoHD V4

Sio/ondemand 200-1200 UV 50mV

No scripts
[Galaxy S II Original Android Development] vazovskiiii:
does this kernel support voodoo louder? because it says it is not supported
[Galaxy S II Original Android Development] qureyoon:
Where did you read that?

Read again first post.
[Galaxy S II Original Android Development] MistahBungle:
Voodoo Louder works fine with Siyah 2.6.12, used it for a couple of hrs today.
[Galaxy S II Original Android Development] Moskiller:
When this great kernel support new touch recovery?
[Galaxy S II Original Android Development] vazovskiiii:
i read this in app name voodoo louder

it say's kernel version not supported
[Galaxy S II Original Android Development] vazovskiiii:
Here is the screen
[Galaxy S II Original Android Development] inferno17x:
Hi Gokhan,

I am currently on 2.6.6 and I have tried flashing to 2.6.12 and it stuck at boot at the Samsung screen. When I tried flashing it back to 2.6.6 it boots up normally.

I tried to remove the below script profile from init.d and flash to 2.6.12 it boots up fine. When I tried to insert the script back it stuck at Samsung screen.

Not too sure why it has cause the boot up problem when either flashing to 2.6.11 and 2.6.12.

#!/system/bin/sh

#CPU Frequencies

AWAKE_MIN="100000"

AWAKE_MAX="1200000"

AWAKE_GOV="conservative"

SLEEP_MIN="100000"

SLEEP_MAX="500000"

SLEEP_GOV="conservative"

#CPU Frequency

FREQ_MANUAL="true"

FREQ_STEP_1="1600"

FREQ_STEP_2="1400"

FREQ_STEP_3="1200"

FREQ_STEP_4="1000"

FREQ_STEP_5="800"

FREQ_STEP_6="500"

FREQ_STEP_7="200"

FREQ_STEP_8="100"

#Misc

PROFILE="true"

LOGFILE="/sdcard/external_sd/sysvalues.log"

LOGMODE="1" # Logmode 0=Console only | 1=Startup | 2=Every Change #

#================================================= ===============================================#

if [ -f $LOGFILE ] ; then

rm -f $LOGFILE

fi

if [ "$LOGMODE" = "1" ] || [ "$LOGMODE" = "2" ] ; then

touch $LOGFILE

fi

###########################

# Setting CPU Frequencies #

###########################

if [ "$FREQ_MANUAL" = "true" ] ; then

if [ "$LOGMODE" = "1" ] || [ "$LOGMODE" = "2" ] ; then

echo "Set Frequency Table" | tee -a $LOG_FILE;

fi

echo "Set Frequency Table"

echo $FREQ_STEP_1" "$FREQ_STEP_2" "$FREQ_STEP_3" "$FREQ_STEP_4" "$FREQ_STEP_5" "$FREQ_STEP_6" "$FREQ_STEP_7" "$FREQ_STEP_8 > /sys/devices/system/cpu/cpu0/cpufreq/freq_table

fi

echo "Setting CPU to "$AWAKE_MIN"-"$AWAKE_MAX

echo $AWAKE_MIN > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

echo $AWAKE_MAX > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

####################

# Setting Governor #

####################

echo $AWAKE_GOV > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

####################

# Starting Profile #

####################

if [ "$PROFILE" = "true" ]; then

if [ "$LOGMODE" = "1" ] || [ "$LOGMODE" = "2" ] ; then

echo `date +%X`" - Profile activated" | tee -a $LOGFILE

fi

echo "Profile activated"

(while [ 1 ] ; do

AWAKE=`cat /sys/power/wait_for_fb_wake`

if [ "$AWAKE" = "awake" ]; then

chmod 644 /sys/devices/system/cpu/cpu1/online

echo "1" > /sys/devices/system/cpu/cpu1/online

chmod 444 /sys/devices/system/cpu/cpu1/online

echo $AWAKE_MIN > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

echo $AWAKE_MAX > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

echo $AWAKE_GOV > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

fi

SLEEPING=`cat /sys/power/wait_for_fb_sleep`

if [ "$SLEEPING" = "sleeping" ]; then

chmod 644 /sys/devices/system/cpu/cpu1/online

echo "0" > /sys/devices/system/cpu/cpu1/online

chmod 444 /sys/devices/system/cpu/cpu1/online

echo $SLEEP_MIN > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

echo $SLEEP_MAX > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

echo $SLEEP_GOV > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

fi

done &)

fi
[Galaxy S II Original Android Development] mekhonte:
Voodoo louder gave me this message too!
[Galaxy S II Original Android Development] gokhanmoral:
update your app or find a newer version.

I have already checked the latest version and I guess last 4 or 5 versions already support the kernel.

it is not the kernel's fault if you use an older version.

download it from the market.
[Galaxy S II Original Android Development] luxm4n:
siyah kernel is not stable kernel releases to the user,,, Can you make the first beta version to stable?

daily release of new versions and new bugs, new problems again,,,

siyah kernel is not recommended for your sgs2, save your sgs2 now,,,
[Galaxy S II Original Android Development] xsycox:
Seriously, guys and gokhan, something is wrong with the video playback in .12.

I flashed it again today and the problems with local video files returned.

With .09 and .11 the videos are running fine for hours. With .12 they stop after some seconds to one minute and give out the message: Incorrect data.

I tried it several times with reflashing and different video files.

Greetings
[Galaxy S II Original Android Development] MistahBungle:
WTF ??!! I've been using Siyah pretty much the whole time I've had my phone save for the first week after I bought it. And I've never found it to be anything but stable. It is easily the best SGS2 kernel available, hands down.

And frankly, I'm grateful as hell Gokhan (and the other devs out there) do what they do & bring us fantastic kernels/roms/apps & themes either for free or for piddling amounts of money.

Your comment "siyah kernel is not recommended for your sgs2, save your sgs2 now" is way out of line and insulting to the person who creates/maintains it.

You need to STFU & go troll somewhere else :mad:

Edit to add - I'm running 2.6.12 & was watching a video via USB OTG earlier & it worked flawlessly with both MX & my rom's native video player.
[Galaxy S II Original Android Development] rauschkugl:
This forum should be saved from people like you. If you don't have something to prove your point go and use another kernel. You know how to report a problem the correct way? In your case the problem is in front of the screen. Something i can say without a proper bug report.

Sent from my GT-I9100
[Galaxy S II Original Android Development] xcarecrow:
This is happening to me too.
[Galaxy S II Original Android Development] antt00:
WTH is your problem. Siyah kernel is one of the most stable kernel around. Never had any problems with it (kinda disappointed with this btw). I always go around trying new and different kernel but always come back to this one. This is the smoothest kernel for me.

If u have a problem report it otherwise go flash some other kernel. We won't be missing u. Bye. Seriously don't come back here.
[Galaxy S II Original Android Development] xsycox:
Guys, can you all ignore that moron and stay focused to the video playback issue?

First rule: Do not feed the troll!
[Galaxy S II Original Android Development] vassalle:
Happening to me too. Back to. 11 for now. Cheers
[Galaxy S II Original Android Development] xsycox:
Alright, that is good. It proves I am not the only one. ^^

---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------

... and another one.
[Galaxy S II Original Android Development] pay.c:
BT HID (mouse & keyboard) working like a charm now (since 6.12)! THANKS GOKHAN!
[Galaxy S II Original Android Development] AndreiLux:
After 3 days, I again got the wlan_rx_wake freeze. .12 with update3 wifi drivers.
[Galaxy S II Original Android Development] kasica-76:
Siyah 2.6.11 support Voodoo.
[Galaxy S II Original Android Development] AJ.Rockwell:
Sorry to burst your bubble, but for me it works all right... :)
[Galaxy S II Original Android Development] desean:
No problem with videos here. I have already watched over 4 hours of videos of different formats (rmvb, mp4 & mkv) with SiyahKernel v2.6.12 without any problem. However it should be noted that I am using MX Video Player to watch them.
[Galaxy S II Original Android Development] blaex:
No problens so far... Self made videos or youtube/avi-file?
[Galaxy S II Original Android Development] sierrafox:
i can confirm that local videos (variety of containers and codecs) with mx player only play with SW decoding. HW decoding does not seem to work any more. this may be due to my GPU UC scripts. i'll try and test that when i have free moment!
[Galaxy S II Original Android Development] ozzyita:
For the second day since I've installed v12 once I reboot the phone my battery dropped from 60% to 22%, what is causing this?
[Galaxy S II Original Android Development] droidphile:
Are you on CM7? CM7 had this problem where "cat /sys/power/wait_for_fb_wake" cause a freeze. Two options:

1) Deactivate profile in the script by changing the value of the variable PROFILE or by removing the part of the script that corresponds to screen-off profile.

Flash 2.6.12 and check now.

2) Add a line in script to set stock voltages, flash latest siyah and see if it's ok.

I don't know why is it working with 2.6.6.
[Galaxy S II Original Android Development] CamoGeko:
It's just the battery sensor needs time to readjust. Just like Entropy has explained before in this thread, could help if you search instead of asking again..... :)

Sent from origin unknown.......CM9 Galaxy
[Galaxy S II Original Android Development] Januwar:
DTMF not working

Hi all,

don't know if I'm the only one facing following problem with 2.6.12:

If I want to use DTMF to enter a PIN while in a call (mailbox for example), I hear the sound of the buttons, but they are not correctly recognized by the other side.

Any idea?

Thanks
[Galaxy S II Original Android Development] droidphile:
@Gokhan

Even i have this weird issue where after about 8 seconds of video playback, video pauses sort of 'restart' with message "Incorrect data" and decoding will be switched to software mode from hardware mode.

Using Moboplayer. Problem arises mainly with FLVs and MP4s from Youtube. Also with some low resolution AVIs. (Problematic video was a 480p MP4 from youtube).

There's no issue with 1080p captured using GS2 cam. It's playing smooth.

Below is the part of logcat which i stripped so that only 'suspected' lines and lines corresponding to start of playback remain. You can see decodec threads exiting at the end.

E/CMPlayer( 8321): beginTime=0;filePath=/sdcard/external_sd/Videos/Best of just for laughs 2011 part 13_(480p).mp4;params=

E/MediaPlayer( 8321): Attempt to call getDuration without a valid mediaplayer

D/SurfaceFlinger( 2819): remove count:1 destroying com.clov4r.android.nil/com.clov4r.android.nil.SystemPlayer

W/ActivityManager( 2819): Trying to launch com.clov4r.android.nil/.CMPlayer
W/MediaPlayer( 8321): mediaplayer went away with unhandled events
E/ScrollLayout( 8321): onMeasure

D/player ( 8321): mobo open file setting audio_stream_index = 0,subtitle index = 0
I/player ( 8321): NativeRenderer_nativePlay file
D/player ( 8321): cmp begin loading ffmpeg lib
D/PowerManagerService( 2819): acquireWakeLock flags=0x2000000a tag=MainPlayer uid=10092 pid=8321 myUID=1000 myPID=2819 myTID=3015

I/SurfaceFlinger( 2819): renderScreen: 1219710516, 1.000000, 1.000000
V/item ( 8321): write success!

D/PowerManagerService( 2819): releaseWakeLockLocked flags=0x0 tag=KEEP_SCREEN_ON_FLAG myUID=1000 myPID=2819 myTID=2891

I/AudioFlinger( 2607): stop output streamType (0, 3) for 1
D/player ( 8321): onPause

W/InputManagerService( 2819): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@40b04120

D/dalvikvm( 8303): GC_EXTERNAL_ALLOC freed 607K, 55% free 3120K/6919K, external 519K/520K, paused 40ms
I/SurfaceFlinger( 2819): renderScreen: 1219710516, 1.000000, 1.000000
D/alogcat ( 8303): stopping ...
D/alogcat ( 8303): canceling periodic saves
V/alogcat ( 8303): resumed
D/alogcat ( 8303): starting ...
D/player ( 8321): onStop
D/player ( 8321): onDestroy
W/ActivityManager( 2819): Duplicate finish request for HistoryRecord{4078d210 com.clov4r.android.nil/.CMPlayer}
D/PowerManagerService( 2819): releaseWakeLockLocked flags=0x0 tag=MainPlayer myUID=1000 myPID=2819 myTID=2826
D/player ( 8321): video_decodec_thread exit!
D/player ( 8321): read_packet_thread EXIT!
D/player ( 8321): audio_decodec_thread EXIT!
D/player ( 8321): ===========CMPlayer_nativeClose===========
[Galaxy S II Original Android Development] pikachu01:
This might be the infamous CM7 didle patch problem >.<

CM7/MIUI seemed to have a problem parsing the wait_for_fb_wake for some reason after a certain patch was included (didle maybe?)
[Galaxy S II Original Android Development] inferno17x:
Hi Droidphile,

I am usiing MIUI 2.2.3 ROM when I delete the screen-off profile it works if I put it back it stuck at boot screen for with 2.6.12.

When I flash back 2.6.6 it works just fine.
[Galaxy S II Original Android Development] droidphile:
There is the culprit!!

cat /sys/power/wait_for_fb_wake is causing problems since your aosp MIUI is not able to parse this file/function. Stay away from screen-off profiles or use some governor that has one inbuilt like the 'new' ondemand in Siyah which has a screen-off cap of 500mhz.
[Galaxy S II Original Android Development] pikachu01:
I wonder which commit broke this for AOSP. This was happening for ages in the SGS forum for CM7/MIUI users where their screenstate_scaling capability got robbed by a commit to AOSP :(
[Galaxy S II Original Android Development] gokhanmoral:
Entropy512 has told about video playback problems when using AFTR with new cpuidle driver.

if you have that problem you can disable AFTR by using the following line in an init.d script:

echo 2 > /sys/module/cpuidle/parameters/enable_mask

I will increase the time to enable AFTR in the next release.

you can also try to use 2ndcore app from the market to enable the second core before watching videos.

it will prevent AFTR (second core must be switched off to use AFTR) thus prevent the problem.
[Galaxy S II Original Android Development] droidphile:
Forgot about that. But he said only i777 users had the issue. Ok Nvm, his kernel is only for at&t gs2.

I don't know why is the problem only for low quality videos and not for full HDs.

So you will be increasing target residency for normal idle from 4,000 in next release.
[Galaxy S II Original Android Development] Honusnap:
I've seen that you've "tweaked" the ondemand governor on the 2.6.12, i don't know if it is the reason but while trying "Sentinel 3, a superb game ... :p i saw that the small monsters where walking fast ... slow... fast ... slow.... i suppose that the freuqency was jumping up/down or the processor was running on single ... dual .. single .. etc.

I've changed to "Conservative" and everything run perfect.

Ps : Perhaps it would be good to swap the names of these governors... conservative is now a better performer than ondemand...
[Galaxy S II Original Android Development] cmd512:
Gokhan, noticed a tiny bug on the way to work this morning:

When I fired up the car this morning, Bluetooth synced instantly with no problems. But, while I was driving, I received a text message, which resulted in the Bluetooth disconnecting. Forcing the car to reconnect remedied the issue, but it shouldn't be disconnecting in the first place.

Not ruling out the new ROM I'm using, but this did not happen with previous Siyah kernels. Will try a stock kernel later to test.
[Galaxy S II Original Android Development] remorema:
hey gokhan. excelent job on the bthid fix. now I can connect my mighty mouse with no issues at all.

can we expect a touch based recovery on next build ? and please revert the recovery color back to mystic blue. please please please ;)

edit: btw since this recovery is very well organized. you could remove the duplicated actions in anvanced menu. im talking about reboot recovery(found also on reboot menu);wipe dalvik and wipe batt stats(also found on the wipe menu)
[Galaxy S II Original Android Development] mekhonte:
If you notice the recovery is from af974
[Galaxy S II Original Android Development] vazovskiiii:
yes you was right now it has passed but now i have problem with purchasing this app my country is not in list i have tryed it from google acc from pc but same problem i'm already f...ed up with this app i whant it but i can't buy it i have been charged already 4 times 4 EUR but it's not giving me chance to buy it f..........ck

sorry
[Galaxy S II Original Android Development] veyka:
Use market enabler, also try emailing the dev if you have been charged multiple times and he should be able to help you out.
[Galaxy S II Original Android Development] xsycox:
With which app can I edit the init.d script "on the fly"? Or is it not possible with an app? Do I have to copy the file to the computer and put it back? I guess, a normal text editor will not work, because the file is somehow coded.
[Galaxy S II Original Android Development] tolis626:
I thanked you instead of quoting your post but anyway...Consider it on the house! :p

It's in no way specially coded.It's only a simple text files.The shell will "read" the commands in the file and execute them.That's the simplest explanation I can give.

To edit init.d scripts,a simple text editor is sufficient.All it needs is superuser permission.The built-in editor of Script Manager is perfect for the job as you can actually remount /system as rw and modify your script from within Script manager.As simple as it gets me thinks. ;)
[Galaxy S II Original Android Development] gorillaCF:
hi all. not sure if anyone encountered SoD on 2.6.12.

i got it this morning, on foxy 3.0 and 2.6.12 and also geko's config on VC.

any idea how should i prevent this? increase the voltages of geko's config slightly?
[Galaxy S II Original Android Development] CamoGeko:
Hi mate, yeah it seems to be happening to a few people on the latest Siyah. Try, upping the lowest frequency voltage by +25mV. Also I'd advise to use 200Mhz as your lowest setting.

Sent from origin unknown.......CM9 Galaxy
[Galaxy S II Original Android Development] gorillaCF:
hey man. great to hear from you again :)

anyway, my settings in VC are:

noop/conservative 200-1200, and all the default numbers that you have suggested for your config.

i've upped everything by 25, lets see if this happens again.

not sure if this might help, but on normal daily usage everything is fine. but once i go to sleep, and the phone is left untouched for more than 5 hrs, seems like waking it up is abit of problem.

there's some sort of short lag in the phone waking up lol.