yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] RoXeon:
Both additional gpu step and new gpu freq table are just great. We all know that unfortunately one (i hope that not both) of those two features is causing problems on some devices. My suggestion is that someone who is able to compile Siyah, could provide two kernels, one with additional gpu step, and one with new gpu freq table.

That would show us, which of those two features is causing problems and maybe then, gokhanmoral could merge at least that one for future releases, which would be really nice.

Sorry for my english. I hope you understood me.
[Galaxy S II Original Android Development] atomic339:
@up what is your voltage on GPU?

Why I can't see different between default profile and performance profile? I always see a lot of changes in ew tweak when I change profile to performance.
[Galaxy S II Original Android Development] RoXeon:
From changelog: "removed battery and performance profile settings during the beta phase (they will be the same as default settings)"
[Galaxy S II Original Android Development] red.hat:
You can make changes via extweaks to your needs.

---------- Post added at 06:05 PM ---------- Previous post was at 06:02 PM ----------

Gk, please could you take a look at this battery.profile and let me know if it is a good combination.

GPUFREQ1=54

GPUFREQ2=108

GPUFREQ3=160

GPUFREQ4=266

GPUVOLT1=850

GPUVOLT2=900

GPUVOLT3=950

GPUVOLT4=1050

GPUTHRESHOLD1UP=85

GPUTHRESHOLD2DOWN=25

GPUTHRESHOLD2UP=85

GPUTHRESHOLD3DOWN=40

GPUTHRESHOLD3UP=85

GPUTHRESHOLD4DOWN=70

min_bl=50

min_gamma=0

max_gamma=12

rate=100

enable_mask=3

sched_mc_power_savings=0

chargecurrent=2

logger=on

secondcore=hotplug

scheduler=deadline

scaling_governor=pegasusq

load_l1=20

load_h0=30

load_rq=20

min_rq=2

freq_min=200000

install_root=on

mov_hysti=5

suspend_freq=500000

vibrator_level=3

user_gamma_adjust=0

blnww=off

cpustepcount=16

notification_enabled=off

notification_timeout=0

led_timeout_ms=-1

bln_effect=0

touchkey_brightness=2700

led_fadeout=on

led_on_touch=on

cpu_undervolting=0

smooth_level0=4

scaling_max_freq=110000

scaling_min_freq=200000

usb_mode=default

GENTLE_FAIR_SLEEPERS=off

ARCH_POWER=on

default_stats=off

mdnie_shortcut_enabled=on

cfs_tweaks=1

zram_size=0

soundgasm_hp=0

Just played around with the default.
[Galaxy S II Original Android Development] robertobsc:
When I turned zram 150 mb on and swappiness automatically to 90 the phone became a hurricane! It's so fast now!!!

Enviado de meu GT-I9100 usando o Tapatalk 2
[Galaxy S II Original Android Development] Hannibal226:
Hey guys,

maybe I'm blind but where I find the options for gestures?

CHEERS ;)

Sent from my Galaxy S2 - Resurrection Remix & Siyah Kernel
[Galaxy S II Original Android Development] atomic339:
Where do you have option to set swappiness?

Can someone post a performance profile?
[Galaxy S II Original Android Development] hawkerpaul:
You need to create your own in init.d/gesture_action

See this thread

---------- Post added at 11:42 PM ---------- Previous post was at 11:39 PM ----------

It gets set automatically when you change ZRam size
[Galaxy S II Original Android Development] Hannibal226:
Just thought this is only the info who it works in background...

Hmm ok, so then maybe if it's build a bit easier I will test :P

Gr8 work guys (for me to much work now) and a big thanks ;)

Sent from my Galaxy S2 - SensatioN Rom & Shun Kernel
[Galaxy S II Original Android Development] mathsmart:
I think your right its a bit faster :)

Envoyé depuis mon GT-I9100 avec Tapatalk
[Galaxy S II Original Android Development] carlos67:
This new gesture feature is very exciting. Great work from Tungstwenty & GM. A nice user interface would make it much more accessible to more people. But maybe that's for later.

However, surely this will create a permanent wakelock, I mean there has to be a service running to continually monitor for gestures?

I hope I'm wrong, but how can a kernel in deep sleep state still be able to "watch out" for the start of swipes.
[Galaxy S II Original Android Development] Tungstwenty:
It doesn't use wakelocks or any extra power, but perhaps this wasn't made clear enough: the detection will not run while the device is sleeping or with the screen off.

The only way to do it would be to keep the touchscreen consuming power and that would mean more battery drain. It simply isn't worth the effort - just press home and draw the gestures you want.
[Galaxy S II Original Android Development] bluefa1con:
Yeah the new frequency are awesome

Its sad we have to miss out on them due to some unlucky people

At least we got lucky enough to get beta5 xD
[Galaxy S II Original Android Development] Crescendo Xenomorph:
I think I've made mistake... I flash this in Bootloader section... But its done and phone is flashed. Should I reflash it in PDA section?

And maybe you could use your own STweaks instead of Extweaks since the ET got a problem in the last betas.... (haven't try beta 5/6 though, still charging and waiting to flash) :good::cowboy::cool::D

UPDATE 1: Reflashed bootloader in PDA and flashed beta6 kernel, its working OK.

Now testing beta6...

UPDATE 2: Beta6 is OK and AWESOME... Now moving to Beta5 and will update if its working properly without reboot/freeze at all...

Minor glitch, since 4.0.1, when I hooked my phone to PC and reboot, it will lost softkey and homekey, after I pull the plug it works OK until I restart it with USB hooked to PC.

Using AC charge got no problem, only when hooked to PC.
[Galaxy S II Original Android Development] CuBG:
When i put gesture_actions in my init.d folder my phone stuck on Siyah LOGO at startup. When i clean the folder from recovery it boots normally. What can be the problem ?
[Galaxy S II Original Android Development] cavaliere06:
confused with bootloader

Maybe the problem it is bootloader related, when I said that I alredy flashed the new bootloader and the problem remained, I flashed it as bootloader, now after reading your post, I reflashed the bootloader as PDA with ODIN and So fare I'm not having the the reboots I had before with beta 3 or 5.

I don't know if my mistake makes any difference or why is it that know I don't have the problems as before.

I will still wait unti tomorrow but so far so good after several hours :confused:
[Galaxy S II Original Android Development] gokhanmoral:
interesting..

if it is the case (I know someone who can confirm it) I will just move to new freq steps and release v4.1.

thank you for the feedback.
[Galaxy S II Original Android Development] cavaliere06:
Hope this leads to the answer since the fourth gpu step is great, Thank you for all of your work, I'm just glad to be helpful:p
[Galaxy S II Original Android Development] egps2:
Thanks GM that would be great but I would strongly recommend explaining the need for the new boot loader in the post as well as posting a link to it on your site to avoid confusion and excessive error reports. Thank you and feel free to delete this since it is not a true dev post, I just didn't want to PM you! Thanks again.
[Galaxy S II Original Android Development] mihaits:
bumpity bump?
[Galaxy S II Original Android Development] hnernes:
Since this is a multi ROM kernel, is it possible to remove the "ICS" mark on the boot animation? Seems a bit wrong to me, using JB, to have ICS bootanimation. ;)
[Galaxy S II Original Android Development] bluefa1con:
I using a gb boot loader and never had a problem
[Galaxy S II Original Android Development] Ryther:
Hi GM!

Gonna try your heart gesture :D my gf surely will love it :D

I have a little tip/request: the possibility to select the number of gpu's steps, like the cpu ones, and more undervolting on gpu itself, cause i'm used to do 133-160 (yes only 2 steps) both at 650mv without problem (in NEAK kernel)! Such a high undervolting save a lot of power, I think!

Doesn't more steps means more work to check the workload = more battery draining?

On my side I have to say that i had no problem with beta 3 and 5! But I've installed b6 'cause i didn't like too much the new gpu steps! If I want to set less steps in beta5, can i put the same freq in 2 or more consecutive steps? Like 108-108-108-160? What this setting will do? And which threshold values it's better to set to prevent the kernel "looping" in a check for the workload?

Sorry for the bad english and the intricate question :p

Keep up the great work!

EDIT: just got a kernel panic on beta 6 :S
[Galaxy S II Original Android Development] RoXeon:
If I would like to have two steps (108 and 160), would use setup like this:

Step #1: 108MHz, treshold up: 1, treshold down: 0

Step #2: 108MHz, treshold up: 1, treshold down: 0

Step #3: 108MHz, treshold up: 70, treshold down: 0

Step #4: 160MHz, treshold down: 50

I think it should work well.
[Galaxy S II Original Android Development] Ryther:
Yeah, that's the same i was going with, but better sure than sorry :D
[Galaxy S II Original Android Development] pangiotis24:
sorry if it has been reported again but crt animation is not working with 4.1 beta and cm10
[Galaxy S II Original Android Development] gokhanmoral:
You cannot set gpu voltage to 650 on neak as I have just checked simone's repo and the lowest limit is set to 700. You probably use stock voltages.

Even with another kernel which has lowered that limit I doubt you can use 650 with 160MHz unless you have a special device built using superconductors.

I recommend you to read about game theory and stop making over optimisations.
[Galaxy S II Original Android Development] salvatore94:
I've flashed gm's bootloader in PDA section, but i still have some freezes/reboot. So I would try to flash directly LPT fw.

The thing that make me "angry" is that I played with DeadTrigger for about 10 min using 4.1beta5 without any problem, but if I lock the screen the phone reboot itself...

Very annoying iussue....
[Galaxy S II Original Android Development] rumen_s:
constant reboots when screen goes off with beta 5, same was with beta 3

last_kmsg attached, if this may help

beta 4 was OK, will test 6

I am on XWLPT
[Galaxy S II Original Android Development] Ryther:
Win!UV values for N.E.A.K.

Well, I have done the same as the OP in the link, with BUS Voltage level set to 4 and latest N.E.A.K. control i can bring the voltage (on the app) all the way down to 600... but my GPU couldn't handle it (@133) so I've set the value to 650 and no more problems. There is a way to verify the voltage set to the gpu? Maybe the app show the value but the kernel is not changed and still have stock values?
[Galaxy S II Original Android Development] baza14:
With old GB bootloader I have got kernel panic after try to wake my phone. With LPT bootloader I have got reboot. Last_kmsg attached.
[Galaxy S II Original Android Development] Tungstwenty:
Please check this post for a discussion on trying to solve that issue.
[Galaxy S II Original Android Development] Josuhu:
CWM BACKUP data image error SOLVED.

I told few pages ago that the Siayh kernel CWM could not make a backup and gave an error. Well the results and solution are below.

- "Backup data image error" seem to have started after I swapped the JB second with the ICS first rom. I USED SIYAH 4.1b4.

- What I could and what not. I could restore and backup the second rom but I could not backup the first rom in CWM.

- This happend also with other Kernels and not just with the latest Siyah betas.

- SOLUTION: Unroot and root again with ODIN.

- RESULT: Backup works again.

- Just a guess why: I have red from xda that the rooting might have been messed.

Frustrated but happy. Now back to flashing JB :)
[Galaxy S II Original Android Development] carlos67:
To get rid of ICS(Siyah logo) on bootup, just create a new empty file called .nobootlogo and put it on the root of the SDcard. Notice the filename begins with a "."

Now you will not see the Siyah logo on bootup.
[Galaxy S II Original Android Development] Christiancs1969:
New boot image will be soon I'm sure just wait dude:D :D

Sent from my GT-I9100 using Xparent Cyan Tapatalk 2
[Galaxy S II Original Android Development] salvatore94:
Flashed stock LPT and 4.1beta5. Still having reboots when I try to resume phone from deep sleep.

Here is last_kmsg
[Galaxy S II Original Android Development] rav4kar:
Did you try 4.1beta6 as beta5 carried forward some frequency changes from beta3/4 by mistake?
[Galaxy S II Original Android Development] Tungstwenty:
Did you flash the ROM through PC Odin, including the PBL and SBL files (primary and secondary bootloader)?
[Galaxy S II Original Android Development] gokhanmoral:
did you flash stock lpt with odin or mobile odin?

and does it have untouched boot.bin and sbl.bin files?
[Galaxy S II Original Android Development] Tungstwenty:
Right, the thing is that beta5 (and previous beta3 also) have the additional GPU steps and frequencies, which should work, but for some people it doesn't.

Hence my previous question as whether the bootloaders were also updated.
[Galaxy S II Original Android Development] hawkerpaul:
Gokhan.

The problem I posted on Tungstwenty's gestures thread is still here for me, but its nothing to do with the gesturing.

I "randomly" seem to lose all my media files on my external sd card. When I go into music player it says "no files" and my default ringtone and notification are lost (as these are also on the external card). The only way to get them back is to clear all cache library folders relating to media app.

First suspicions was a looping gestures script which proved incorrect.

Now I've noticed media scanning takes more time on boot, and if I boot the device with the USB cable plugged into PC, when I open it up it only shows the phone memory. If I disconnect the cable and reconnect then then shows both phone and external sd card.

I put 4.0.1 back on, and the problem is still there along with the USB connection behaviour. This is strange as I have never had any issues whatsoever with 4.0.1 previously.

The only thing I can think of (and I'm clutching at straws here) is that I made a CWM backup in one of the CWM v6 betas, which creates a blobs folder, inside which contains literally thousands of folders and each seems to have a single file inside. Do you think possibly that this huge number of folders in a single folder may be affecting the media scan and perhaps timing out, thereby "removing" all my ringtones/mp3;s etc from the libraries?

I will remove my CWM backup (blobs included) and see what happens.....

Edit: Removed backup+blobs and reboot with USB cable connected to PC. Opened up the device in explorer and I see both phone and external card. Media scanning was as quick as it previously was. It seems this blobs folder was causing the problem for me.

My concern is compatibilty between v5 backups and v6. I would guess a v6 backup cannot be restored by a v5 CWM, but can a v6 CWM restore a v6 backup? If not can CWM5 be bundled in the kernel instead of CWM6?

Can CWMv6 revert back to the CWMv5 style of backing up as this blobs folder seems to be quite dangerous.
[Galaxy S II Original Android Development] rav4kar:
My bad.. I missed the chain and point of discussion :p
[Galaxy S II Original Android Development] salvatore94:
Flashed with odin from my pc. I also tried to flash the bootloader you provide ad PDA after the first reboot with stock LPT.
[Galaxy S II Original Android Development] tuniel:
same here on stock LPG and beta 6. (actually with JKAY mod: the CRT on works and CRT off doesn't).

an additional thing: with stock kernel when i enable the sliding bar for adjusting the auto brightness it refreshes both when going up and down in brightness, but when i use siyah 4.0 or 4.1 it does only refresh when lowering the brightness and not when increasing it. anyone else?
[Galaxy S II Original Android Development] Dampierre:
Same for me. Nothing happens when I'm using the phone but ramdomly freezes and restarts when I try to resume from deep sleep. I returned to 4.01. By the way 440 mhz overheats my phone and it throttles, so the new frequencies are no good for me in summer :) Maybe in winter I can try :)

Add: Forgot to say I used beta 1, beta 3 and beta 5. All have deep sleep freeze issue.
[Galaxy S II Original Android Development] Tungstwenty:
If the problem is with the media scanner, can you try adding a ".nomedia" file in the root folder so it's ignored? Just run this on the shell:

touch /sdcard/clockworkmod/.nomedia

Another option might be that your /sdcard volume can have errors.

For ext4 volumes (/system, /data, etc.) you could run "e2fsck /dev/block/..." from adb while in recovery with the partition unmounted. For vfat partitions (mmcblk0p11) perhaps "fsck" can do the same.

About the files in the new CWM backups.

On my case, inside "blobs" I have a total of 8046 files split in 3516 folders - averaging 2.3 files per directory.

The intermediate directories (the 3 hex digits) are there to avoid 1 single directory with all the files, to prevent a longer time scanning, updating, etc.

But having 3516 folders is still on the same order of magnitude as 8046.

My option would be to only have 2 digits on the sub-folder names and place the remaining digit on the file names:

The square root of 8046 is ~90. If we had a distribution of about 90 distinct directories inside "blobs", the average number of files inside each of those folders (at least for my particular case) would be also 90 files. It would be more balanced.

Using the hex notation of the hash, the most practical way would be to use just 2 digits instead of 3. That would give a max of 256 entries on the top level, and inside there would be on average 31 files (again, in my case). If the total number of files grows to 65536, it would be the perfect balance with 256 entries on each level.

That would be the equivalent of 8 backups where every single file has changed, and where no housekeeping is done due to deletion of old backups.

If there are way more backups, say 100, also with every single file changed every time, there would be 256 top level entries and ~3.150 files in each of them, which is no worse than the current situation.

Changing this would of course have impacts, so I guess neither GM nor Koush will make that change :)
[Galaxy S II Original Android Development] hawkerpaul:
Thanks mate I'll give it a try.

By the way, what is the /dev/block number for external_sd?

Nonetheless, if this is indeed what is causing these issues, its something that everyone needs to be made aware of.
[Galaxy S II Original Android Development] gevans35:
I got an error with Titanium backup (first time ever) using 4.1beta4+. I think it was an xlm file.
[Galaxy S II Original Android Development] lyndonguti:
what kindvof error more details

sent from my lovely phone....hmmm wait its a tablet...waaa i dont really know.....im PARANOID NoW!
[Galaxy S II Original Android Development] Tye:P:
I was having the problem of phone not waking almost every time my phone went to sleep on v3.4.1 beta3. I'm also using GB bootloaders.

In my case it seems to be just a slightly too aggressive GPU undervolt. I was using the exact same UV I've been using for, well, forever and have never had any problems. I think it's the first step, which is 8Mhz above what it used to be, just enough to make my previously stable UV values unstable.

It seems to be fixed now and hasn't happened for about a day.
[Galaxy S II Original Android Development] RoXeon:
/dev/block/vold/179:25 on /mnt/emmc type vfat (external sd)
[Galaxy S II Original Android Development] gevans35:
Sorry, no more details. It flashed up a message that something had failed, couldn't find it logged anywhere and the message only lasted a few seconds so I didn't have time to read it properly. I flashed back to Speedmod kernel and re-ran Titanium full backup with no errors.
[Galaxy S II Original Android Development] m1trand1r:
2nd day now on beta5.....didn't face any random reboots or such...but on beta3...phone rebooted in my pocket:eek:...

btw: is this a bug:

Shouldn't there be "Mhz" instead of khz....on cpu freq?....not anoying...i just noticed....i am on beta 5 now:)

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Sent from my SGS-II powered by CM9

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[Galaxy S II Original Android Development] RoXeon:
1,2 GHz = 1 200 Mhz = 1 200 000 kHz = 1 200 000 000 Hz
[Galaxy S II Original Android Development] Many40:
It is correct now. Our phone's frq default scalling range is 200MHz - 1.2 GHz what is 200 000 kHz - 1 200 000 kHz. Seems that from beta5 GM corrected this (it was reported to him some days ago). I'm using beta4 and it's still in MHz what is incorrect: 200 000 MHz (200 GHz) - 1 200 000 MHz (1 200 GHz). Our phone's CPU for sure can't be so fast :) Regards

Edit: RoXeon was quicker
[Galaxy S II Original Android Development] intronauta:
One random reboot with "4.1beta6" opening an app in my XWLPD 4.0.3 (Stock)

Extweaks resetted with default config except conservative 200-1000Mhz ->BLN: Off->zram: 100MB (no GPU changes, UV, scripts, or apps like SetCPU)

Glad to see swappiness raised to 90 (I still think that 100 is better with zram). I suppose that zram use LZO and I don't know the compress ratio, but, what do you think about this patch?

http://driverdev.linuxdriverproject.org/pipermail/devel/2011-April/015114.html

"Snappy" seems interesting, I would prefer less I/O lag over compression ratio.
[Galaxy S II Original Android Development] m1trand1r:
thanks for clarifying this...i didn't think this way....lol...:p...

Btw: did anyone face this:..i've been listening music today.,i love amp...+6db....but...when in screen off & playin' music there was crackling sounds when changing volume + & -....music stopped playin' for a half a sec....and then again ok....and cracks were loud....i'm using Winamp....:)

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Sent from my SGS-II powered by CM9
[Galaxy S II Original Android Development] RoXeon:
Are you using any screen off profiles? I noticed that too when I used screen off profile with scaling 100-300Mhz (which is soo stupid, don't underclock so low, it's poinless, cpu is jumping to 300Mhz almost all time even on conservative gov.).
[Galaxy S II Original Android Development] m1trand1r:
yes...i have screen off profile at 100-400mhz....ondemand....i'll try disabling it & post back...;)

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Sent from my SGS-II powered by CM9

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[Galaxy S II Original Android Development] confusedmuse:
I had random reboots every few hours on beta 3, 5 and 6. Unfortunately i didn't grab any log cause they happened mostly on work where i didn't had time to do that.

Back on beta 4. No single reboot since the release of this version.

Doesn't make any sense to me at all regarding the changelog. :confused:

EDIT: Forgot to mention: I'm not undervolting since a few days, for testing.
[Galaxy S II Original Android Development] Crescendo Xenomorph:
Same here for me... flashed GM's LPT bootloader via Odin PC in the bootloader section and reflashed in PDA section. Still giving me random reboot on beta5... Beta6 is stable, all working.

In the beta5 last_kmesg got something about "MMC voltage", but in beta6 it isn't any about MMC voltage problem.
[Galaxy S II Original Android Development] m1trand1r:
i just raised max freq. to 500mhz...crackling sounds are gone:D...

thx

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Sent from my SGS-II powered by CM9

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[Galaxy S II Original Android Development] robertobsc:
Got a reboot while phone sleeping :

Beta 6

Xwlpg

Zram 150mb

My standard Undervolt

I/O thunderbolt tweaks

Last_kmsg also seems a binary file... Here it is

Enviado de meu GT-I9100 usando o Tapatalk 2
[Galaxy S II Original Android Development] -earth-:
Owned by low voltage!

No support for undervolted devices.
[Galaxy S II Original Android Development] #illidan:
GM I know you aren't supporting beta5 version but I still tried it out & everything works fine & the 4 steps are smooth when using the phone but I get kernel panics in deep sleep. Anyway attaching the last_kmsg here incase it helps you figure out stuff.