yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] veyka:
Just look though the themes/apps section or search google for i9100 bootanimations, there are quite a lot.

Yes boot animations will work with stock roms.
[Galaxy S II Original Android Development] rav4kar:
Okay, I hit with the same issue again this morning, please find the attached last_kmsg.txt that can help the devs to narrow down the issue, thanks!

After double taping the home button, I get the control back and Lock button locks the screen,but once after having locked, it becomes dead, lock button does not wake the lock screen up, then I have to connect the USB cable either to charger or PC for Lock button to work, the screen remains black until then.
[Galaxy S II Original Android Development] ndy4eva:
headset button to play music

I'm using Siyah 2.6.7 with geko95gek's UV/UC cfg right now. I noticed the button on wired headset doesn't really work well. It works to answer or hang up the phone call. But it doesn't response to single/double click to play/skip music.

I don't think I had this issue when I was using the stock kernel.

Thanks for all your hard work. :)

btw, geko95gek's UV/UC cfg works quite well. :D:D
[Galaxy S II Original Android Development] veyka:
confirmed, after running the script it reboots the device, dumping logs now.

See attached, basically the kernel is crapping its pants, all there in the log.
[Galaxy S II Original Android Development] kilian7th:
What to modify when you listen a lot of music with headset ?

Hello,

does anyone has succesfully found settings to apply or change for mass battery drain when you listen a lot of music with headset and screen-off ?

If yess thanks to explain where and how, it should be nice :)

Siyah 2.6.7 is perfect for everything but could maybe optimized for this use ???

Thanks in advance
[Galaxy S II Original Android Development] stylez:
Children get your dummies and chillax no need for these out breaks on XDA.

Any more out breaks on thread infractions will be placed.

XDA IS A DEVELOPMENT FORUM NOT A PLAY GROUND!!

Nuff said.....

Sent from the valley of the shadows....
[Galaxy S II Original Android Development] bclark:
I have a last_kmsg on that thread that looks quite similar if more info is needed
[Galaxy S II Original Android Development] BULL3TPR00F:
Is anyone else experiencing any issues using SiyahKernel v2.6.7 with the phone constantly rebooting after turning it on (or restarting it). The phone boots to the home screen and while everything is loading, it just soft reboots, and it keeps happening over n over until it randomly stops.

It eventually settles down and is fine but while it reboot loops the cpu starts to overheat and the battery drains (cpu being overworked).

I never had this problem on SiyahKernel until after v2.6 i believe.
[Galaxy S II Original Android Development] veyka:
gokhanmoral has logs with debug symbols now, hes working on it :D
[Galaxy S II Original Android Development] stevehkim:
im using siyah 2.6.7 ondemand and today i listened to hour of music while in the gym and lost 2% cpuspy showed it only scaled to 200 mhz. what kind of cpu scaling are you seeing while listening to music? battery shouldnt drain too much at all while listening to music.
[Galaxy S II Original Android Development] kilian7th:
I used siyah 2.6.7 all alone installed by default and I am testing it with thunderbolt script 2.3.2 , I didn t modified any settings see that I don't know how to ...

I have nearly less battery drain with this configuration my phone drain for 8 to 12 % / hour when i listen to music ... in other use maybe 1-2 % / hour ... it s my best configuration followed by siyah 2.6.4 and thunderbolt script 2.3.8 ...
[Galaxy S II Original Android Development] maccawire:
Siyah 2.6.7 is definitely the best kernel yet.

On this charging cycle I've got approx 2 days uptime with 46% still left. (Connected usb for 20 mins but its still pretty decent)

I would be a moderate user and I use tasker to toggle airplane mode every 15mins and back to wifi overnight.

I also use tasker to enable autosync every 30 mins for 2 mins 24 hrs a day. Background data always enabled.
[Galaxy S II Original Android Development] veyka:
If its rebooting to the boot animation, its rom issue, if its to boot logo, its kernel issue, also logs or it didn't happen.

After it boots, if its a kernel issue, in a terminal,

su

cat /proc/last_kmsg > /sdcard lastkmg.log

You can also plug it in and get a logcat via adb as its rebooting, google for guides to getting logs via ADB.
[Galaxy S II Original Android Development] jimmy72:
1) Some kernels files and script may be corrupted, i advice you to dowload again this amazing kernel in TAR version ( odin) on your computer.

Boot your phone in recoverymod, wipe cache partition and wipe dalvik cache . And then flash with Odin. After flashing reboot 3 to 5 times ( for each start let the system completly finish booting sequence).

2) Before your problems begin, do you freeze (with titanium bckup) some apps/syst to avoid theirs starts at booting?

If this not solve your problems, it may come from your rom.

Hope this help you
[Galaxy S II Original Android Development] BULL3TPR00F:
Well ive been using CheckRom with no problems at all until not too long ago after one of these kernel upgrades (Siyah is the only kernel ive ever used). I supplied a logcat so many times but my problem was constantly ignored and never addressed by anyone, which is why i didnt post another log now.

it reboots to the boot animation and the cpu begins overheating at every boot (battery also drained just now from 71% to 14% because of constant reboots). No apps frozen.

Ill give it a shot flashing with the TAR file, but ive reflashed the kernel (and rom with no wipe) several times with no fix.
[Galaxy S II Original Android Development] veyka:
If you are rebooting to boot animation, its more than likely a checkrom issue, backup user app data, but not system app data and do a full wipe and reflash of your rom.

If it was a kernel issue you would be dumped to the logo on a crash.
[Galaxy S II Original Android Development] olifee:
You might also try reducing the Apps on SD (if you use App2SD). I am also on CheckROM and with many App2SD, I got soft reboots about 30 seconds after reboot (i.e. when init-scripts execute and some remounting happens). This is sadly not fixed by disabling media scanning.
[Galaxy S II Original Android Development] omniwolf:
well that's silly, from what i can tell wifi uses less power than 2g/3g, so sleeping the wifi while it's connected will only increase power usage.

i'm not sure what you're saying here. i had 5% drain last night (wifi connected all night), so (for the moment) it seems my phone is back to normal.
[Galaxy S II Original Android Development] BULL3TPR00F:
that sounds like the same problem im having, i have tons of apps installed and have been deleted them recently.

i will try a fresh flash after i backup later.
[Galaxy S II Original Android Development] PhilAd:
Hi,

I can confirm problems with Bluetooth which have been reported by some a lot of pages ago.

I have tested File-Transfer and that worked fine. But pairing with the car of my girlfriend and my car does not work. After pairing he loses connection after a short while. Sometimes my SGS2 also loses his BT Device Name. I have to restart BT or even the Phone to reconnect with my Car. I have tried it with the Navi900 of the Opel/Vauxhall Astra and the MMI-System of the Audi A3. I had the same Issue with very earl versions of CM7 and MIUI and even the Final of CM7.1.

But in the meanwhile it has been fixed in MIUI and CM7.1 (2 or 3 nightly builds after final CM7.1 and MIUI a bit earlier).

- Flashed Siyah 2.6.7 and cleared Cache and Dalvik Cache

I don't think there are any KEX/Modules or something like that that i could maybe load to solve that problem?

- Flashing CM7.1 Stock Kernel again (Cache and Dalvik Cache cleared) solved that problem.
[Galaxy S II Original Android Development] cmd512:
Must be device specific. Syncing to factory Nissan Bluetooth in my GT-R and made/received calls with no issues.
[Galaxy S II Original Android Development] PhilAd:
the problem is kernel specific and not device specific. Might be that there is a difference between nissan and audi and opel but it should work with all devices. there must be a difference between this kernel and other kernels.

EDIT: Or maybe it is caused by the combination of an AOSP ROM with this Kernel?!
[Galaxy S II Original Android Development] gnan10:
yes this is due to Apps2SD only...i am also have been faced that problem of soft bootloops ....after removing sd card its working normal......is there any way to fix this issue.....:confused::confused::confused::confused::confused:

i am using my phone with out memory card now.... so sad by wasting my new 32 gb class 4 card :(:(:(:(:(:(:(:(:(:(:(:(:(
[Galaxy S II Original Android Development] rauschkugl:
Works without problems for me. Maybe your screen off frequency is too low.

I have a question about battery.

When i fully charge my phone, unplug it and put it to sleep i have a battery drain of 2mA according to battery monitor. After about 2 hours it always raises to 20-30mA without receiving a message or getting a call and it is always the same time span. It happens earlier when i use the phone for a while. Then i can't get back under 30-40mA in standby. I already checked wakelocks but i couldn't find something (highest is RILJ with some seconds most of the time) and it is also shown that the phone is in deeplseep almost all the time. Can't upload my screenshots at the moment because i'm browsing with the xda app and can't upload jpeg screencaptures. I also checked if i had any timers set in a programm. I'm monitoring this for several months on all kernel versions now. Does anyone have an idea what the reason for the increase in stanby drain could be?

Sent from my GT-I9100
[Galaxy S II Original Android Development] Rampler:
Maybe a stupid question, how can i enable the logging function ?

I havent files in /dev/log...
[Galaxy S II Original Android Development] Rampler:
I have renamed the /data/.siyah/disable-logger, but where i can find the logs ?
[Galaxy S II Original Android Development] olifee:
Hi Gokhan,

I keep getting corruption of external SD. Easiest way to reproduce is to use "linux installer" to install Debian testing in a 3,9 GB loop device on external SD. My phone just reboots sometime in between, and after that claims SD card is corrupted.

An fsck in a computer fixes this.

As I also got corruption in the filesystem in the chroot before, I guess there is some problem with mmc-driver code? I did not have this in older Siyah-releases, but as it is not that easy to reproduce, I can't give a specific version...

I will try to get a kmsg somehow, but I am not sure when I can reproduce and catch this.

Might be related to the Ubuntu-installation-crashes? And maybe also to App2SD-problems?

EDIT: Can't reproduce right now, because it says the SD card is broken and my µSD-reader is at home...
[Galaxy S II Original Android Development] olifee:
You can get a logcat with the command "logcat", and the kernel log from the ringbuffer with the command "dmesg", or by using "cat /proc/kmsg".

To save those continuously until a crash happens, do

logcat > logcat.txt # for android log
cat /proc/kmsg > kernellog.txt # for kernel log

in a terminal. Beware, those files might become really big if you let them be written for 'ages'!
[Galaxy S II Original Android Development] mc01319:
Hi, has anyone problem with MHL to HDMI adapter with Siyah 2.6.7?

I bought a new adapter and i have black screen in my hdtv.
[Galaxy S II Original Android Development] Simba501:
Working fine here.

Sent from my Galaxy SII
[Galaxy S II Original Android Development] xcarecrow:
Man! this is happening to me too. I don't know what to do, it's happening to me since i installed deodexed XILA2. I installed KI3 modem to test if that's the cause, but keeps drainning the same. If you find a solution, please let me know.

I will try to change rom, maybe the rom causes the loss of battery, don't know.
[Galaxy S II Original Android Development] cbeckstein:
Oh no... flashed already over 1.7.8b3 (actually only the second attempt resulted in an install of the new version)...

and have this sometimes strange behaving superuser 3.0 back on my mobile...

why don't you stay with the stable and reliable superuser 2.3.6.3?

this superuser 3.0 caused lots of unpredictable problems in previous tests

BTW: this time the update to superuser 3 did not force me to reconfirm root rights for all and every app that already was granted root by the previous version; so someting has changed in the setup (apparently to the better)
[Galaxy S II Original Android Development] gokhanmoral:
I did not remove everything, don't worry.

in beta2, I merged every single compiled c file and corresponding headers with 2.6.35.14.

but it caused sd mounting issues.

so, in beta3, I rollbacked some of the files.

and in beta4, I rolledbacked more (the ones which are not in needed)

we still have fixes and memory leak patches...

and we are still on AT&T source base :) (I even thought reverting to update2)
[Galaxy S II Original Android Development] :
Well, update2 has some issues and .13 and .14 are best kernels in a long time as stated by God himself, so.. I sent you PM those mounting issues might have more to do with recovery than with your kernel. The same issues were on my Nexus S before sometimes.

Anyway, prefer to see .14 than .7 :p
[Galaxy S II Original Android Development] GDT:
I came from ninphetamine kernel. Installed beta 3 and now beta 4 but I'm in trouble with superuser and oc daemon and daemon controller. Now I deleted all the guiles above, removed oc daemon and just flashed beta 4 with cwm. Don't have su permissions anymore. What can I start from?
[Galaxy S II Original Android Development] gokhanmoral:
The mounting issue was related with the fs subsystem and I reverted that part and the problem was solved in beta3.

It was really strange that .7 can mount an sd card that .14 cannot.

So I guess newer is not always better.
[Galaxy S II Original Android Development] gokhanmoral:
Let's see if new version fixes root problems for other users. Then if you still have problems with it I will revert back to old su
[Galaxy S II Original Android Development] gokhanmoral:
Please try to download beta 4 again and reflash
[Galaxy S II Original Android Development] sLapshock:
seriously i am on 1.7.7 on CheckRom v3.5 and this kernel is seriously very very buggy.

It HANGS all the time that i have to REBOOT.

Cant even connect to USB at times.

Please look at this.

Battery is good tho. But who cares if its compromise stability?
[Galaxy S II Original Android Development] cbeckstein:
to give you instant feedback:

the new way you install root (in my case su 3.0 over su 2.3.6.3 on KI3, going from Siyah 1.7.8b3 to 1.7.8b4) changed things completely:

- as I wrote: root allowances are correctly carried over to the new superuser

- until now: no sporadic root denials during boot as the previous installs of superuser 3

whatever you changed in the rooting method it really did good

KUDOS!

And now I will make a nandroid backup right away with this seemingly robust root and kernel setup
[Galaxy S II Original Android Development] :
Post of the day. How about checking your init.d for overclocking and undervolting scripts before stating it is kernel fault?
[Galaxy S II Original Android Development] :
You know better of course :D, I am just telling my experience from Nexus S and how it was solved with .13 & .14 :)..
[Galaxy S II Original Android Development] jsompis:
No more superuser issue here, new root script look good.
[Galaxy S II Original Android Development] inferno17x:
I'm on CheckRom 3.5 with 1.77 and

I do not have this problem as you mentioned. Everything works fast and smooth.
[Galaxy S II Original Android Development] ebliss:
beta4 is finally stable. no reboots nor freezes yet.
[Galaxy S II Original Android Development] iamsmallpang:
Just flashed version 1.7.8 beta4

looking for SU upgraded to v3?????????
[Galaxy S II Original Android Development] galanakop:
Friends let me upload a zip in the 1.7.8 beta 4 ... thanks ...
[Galaxy S II Original Android Development] cbeckstein:
did you start the superuser app at least once after flashing the new kernel?
[Galaxy S II Original Android Development] jsompis:
Got new problem in beta4, my phone not go to deep sleep state any more.

In beta3, i got random wakeup.

I never face this issue on 1.7.7 and 1.7.4

Stock rom DCKH2(Thailand) smartass 100-1200, now back to 1.7.7.
[Galaxy S II Original Android Development] iamsmallpang:
SU work fine (LeoMar75 v2.7.1 add SiyahKernel v1.7.8 beta4)

GREAT:eek:D
[Galaxy S II Original Android Development] hausmanis:
what kind of batterylife are you getting with that combo ?
[Galaxy S II Original Android Development] wurzelsepp3:
Do you have the charger plugged in the mhl-adapter?
[Galaxy S II Original Android Development] rauschkugl:
Didn't this happen to you before? I have it since i got my gs2. But i don't know if it happens on a stock device. Rooted and changed rom on the first day.

Tried lots of different roms and it was happening on all for me. The 2mA would really be great. I don't understand why i can only get them for 2 hours. I also don't have to reboot the device to get them back. Only a complete recharge works. So i don't think it can be a programm in the memory...

Sent from my GT-I9100
[Galaxy S II Original Android Development] :
hi guys..downloaded the lulzactive app from the market. trying to play around with the settings and then i save on boot. i have of course in voltage control lulzactive governor and and vr scheduler..those are also saved on boot and that works fine. But everytime i reboot and wait for the phone to load up i go into lulzactive app and it does not save my settings..Any idea why that could be? Thanks in advance

Ps not using any scripts
[Galaxy S II Original Android Development] xuxuzao:
have anyone tried 2.6.7 with and without thunderbolt?

wich were the results on battery and performance?
[Galaxy S II Original Android Development] veyka:
I use it without, and its good here, I had some problems with an older version of thunderbolt! and 2.6.7, but its been updated since then. The kernel comes with part of the thunderbolt! scripts.

Some people are using it happily, so your best bet is to just try it, at worst you will just have to remove it, no harm.
[Galaxy S II Original Android Development] RotesMeerJogger:
you are right. same here. "set on boot" have no effect in lulzactive app. i'm also without any other scripts. only VC with lulzactive governor and lulzactive app to tweak governor a little bit. not really a problem for me only a hint for developer :)
[Galaxy S II Original Android Development] Rampler:
Same here, i went back to ondemand, and its running quite good. The problem is, that the default gouverner is chnaged to ondemandx.

Therefore i was not able to use the lulz app after reboot.
[Galaxy S II Original Android Development] :
Thanks for your replies guys. I am still using lulzactive governor and just deleted the application. Still tweaked about with my settings in voltage control and going to see what battery life is like. Regarding though the app i really do not know why it does not save on boot...Very odd i say but nonetheless not really a major deal..Just would be nice to know why it reverts thats all.:) Still best kernel for me and if i wanna tweak i just flash the thunderbolt script...

But because i am pretty useless making my own script to tweak the governor and i find it alot easier just using the app to tweak the governor it would be nice to know how we can solve it that's all
[Galaxy S II Original Android Development] skribbler86:
Just flashed this kernel and everything seems to be working well. Going to keep a close eye on my battery, although I think the kernel has improved it. After flashing the kernel the market app crashed a few times, but that seems to all been fixed after a couple of reboots
[Galaxy S II Original Android Development] Igor 3:
After some testing, it seems the conservative gov. works the best. With ondemand i had some lags, especially visible when i put on live wallpaper like Christmas HD that scales back and forh on its own. The lags are quite visible. Conservative doesnt have any. Lulzactive is also quite good, better then ondemand but still not as good as conservative.
[Galaxy S II Original Android Development] KcDaRookie:
@Suarez7: You can use the tool in my signature which will give you an easy to use gui for changing governorparameters and many more settings and so far noone complained about not sticking settings.

so i guess you can use this as an alternative until lulzactive app gets an update.
[Galaxy S II Original Android Development] Krendelrus:
I'm using kernel v.2.6.7 (all settings default) with the XILA2 based ROM (made by myself) and getting incredible battery life - 30 hours of moderate usage and still 30% battery left, that's really awesome, thanks gokhanmoral :)
[Galaxy S II Original Android Development] ziroxs:
XILA2 ROM based on Samsung`s sources?
[Galaxy S II Original Android Development] gokhanmoral:
I read all the posts but cannot reply sometimes because of my current workload.

I am aware that there are some problems in the current version which prevents running ubuntu, cause reboots if you move too many apps to sdcard or cause other sdcard problems. I will fix them when I finish my project (or when I cannot sleep which is very unlikely lately)
[Galaxy S II Original Android Development] ndy4eva:
I think the battery drain issue (maybe non-issue), is not related to ROM/Kernel. I believe it's simple science. When you just unplug, it will hold the charge quite well. After while it will go up to 30-40mA range. With UC/UV cfg, mine goes down to 33-21mA (after about an hour).

I didn't change the screen off frequency. Oh well.. It doesn't really matter. I love the current config. :)
[Galaxy S II Original Android Development] DefTaker:
Just trying out Siyah's kernel today - 2.6.7 on unNamed ROM 2.2.1. (Had been running Entropy's 01/02/2012 DD until today.) Wanted to see what the difference (if any) there was. Was ok - didn't notice anything different. Installed SetCPU and OC'ed to 1.6Ghz and left the min at 200Mhz. Set the governer to smartassV2. Did all this today at 7am - noticed that my phone went into SoD (sleep of death) at 12:15pm or so.

Had to hold the power button for ~15 seconds for the phone to power back on. Thought forget it...I'll re-install Entropy's DD Kernel instead. So I did but then decided to give Siyah 2.6.7 another shot. I'm wondering if it was the OC to 1600Mhz that did it...and NO, I didn't have any UV going on. Just the max OC; no underclocking either.

I'll see if Siyah 2.6.7 gives me any more SoD if I run smartassV2 and remove the overclock back to the default 1200Mhz value.

I'll keep everyone posted if I run into SoD again.

Thank you for the kernel. :)
[Galaxy S II Original Android Development] rauschkugl:
Well i don't really understand your science. I know that it's not rom related and it happens on all kernels but it doesn't make sense. The hardware needs the same current directly after unplugging than 5 hours after.

Sent from my GT-I9100
[Galaxy S II Original Android Development] olifee:
Please take your time, and get some sleep sometimes :).

In case I get anything from logs that appears valuable, I will just add it to the thread, but please do not feel forced or pushed to look at it until you really have the time. My life does not depend on Debian / Ubuntu working on the phone ;).

If it does not work, that might even make me my university project finish faster :P.

EDIT: I tried to get some logs, but I am mainly flooded with IO errors and chained clusters after reboot. It reproducibly happens on high sequential or random IO load on external SD, even on a class 10 card. In case you need further information, I can provide anything you want, but I will only give it to you once your project / high workload is over ;).