yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Entropy512:
Looks like lack of freq_table isn't it - I added that and it still goes b00m.

It also doesn't seem entirely related to screen-off profiles - If I set a "Charging USB" profile with a low limit - the device hangs as soon as USB is inserted, even if the screen is on.

This only seems to happen with SetCPU profiles. If I manually set scaling_max_freq, it works. If I use SetCPU to set a limit in the main screen (not a profile), it works. This also happens on any current ICS kernel - stock, GM's, or mine. (Mine won't be released for I9100 for a while - I haven't even done an official I777 release as I'm busy fixing it up, I needed to spend all of Saturday reverse engineering libaudio to work around the lack of an I777-specific one. I was going to wait until I fixed this issue to do a release, but I'm just going to dump it into a "known issues" list because it's taking a while.)

Plan for tonight: When in doubt, add printk()s
[Galaxy S II Original Android Development] Karpfenhai:
Just use screenfilter or a similar app, works fine..

Swyped from my GT-I9100 using XDA App.
[Galaxy S II Original Android Development] olegblochin:
OK I will try via script.thx
[Galaxy S II Original Android Development] Schindler33:
I have lock-up problems with setCPU without profiles. Sometimes it hangs when I change the maximum frequency. I am on Wanamlite 9.5 and had the same problems on older CM9 builds.
[Galaxy S II Original Android Development] simone201:
Had the charging issue too on NEAK 2.0x that i am (trying) making....

Seems really a random issue, happens on sammy roms for me, not on AOSP

Also i had some strange issues on sammy roms, the device hangs as soon as USB is inserted at every charge current and in every mode (MTP, Mass....)

I think i should restart clean :(

I have a bit messed up my repo lol :rolleyes:

EDIT: and also have lack of performance on benchs lol
[Galaxy S II Original Android Development] almaalma74:
Dear gokhanmoral

could I have request for your kernel version, it would be good an stock kernel w/ BLN and that's it. thx
[Galaxy S II Original Android Development] tann3r12:
sorry if this has already been asked, but i have searched and cannot find it. what is the best version to use with resurrection remix v.9.7? :)
[Galaxy S II Original Android Development] minidou-77:
Why won't you try the last one ?

Afaik USB connection is buggy on this one so if you need it try the beta 5 :-)
[Galaxy S II Original Android Development] tann3r12:
i will try that! thanks for the quick response!:D
[Galaxy S II Original Android Development] SupraN0va:
Gokhan

Man you saved my day. Got a huge battery problem with stock kernel. A look at CPU spy showed me how. Deep.sleep 50 % and 40% at 1200 mhz. Flashed siyah, and see there stats are fine now. Just recommend everyone who has battery probs with ics, take a look with CPU spy.
[Galaxy S II Original Android Development] ithehappy:
Well with them I'd add CF too.

Supercurio is the most friendly dev/person I've seen in this forum.
[Galaxy S II Original Android Development] gokhanmoral:
the weird part is that it also happens while charging...

first I thought it was related with deepsleep state.

then after noticing that it happens while charging, I thought it had something to do with changing s value only while freq scaling.

none of them was a lucky guess...

then I thought if it was related with ondemand, tried another governor, it happens as well.

I am pretty sure that I was unable to use 800MHz with voltage control app with samsung ICS leaks. I was having SOD while booting.

simone says that he cannot set governor or freq on boot. maybe samsung prevented that just as a workaround...

in any way, we have a strange problem.

I hope your printk()'s will strike their bytes to the heart of the dev_il tonight..
[Galaxy S II Original Android Development] norbi_nw:
posted this by mistake on the GB kernel, so I will paste it here too:

With beta6 (for ICS) I have problems mounting mass storage to PC. When I press mount it tries to mount the mass storage, in simply unmounts my SD card :/

Reverted back to beta 5 and it's working (have to wait a bit longer than usual, but working).
[Galaxy S II Original Android Development] :
Happens to me too :(
[Galaxy S II Original Android Development] Entropy512:
Yup - it is definitely not the classic 800 MHz suspend SoD issue. I can routinely crash the device when it's connected to USB.

I can:

Set max freq to 500 MHz in an ADB shell and have things work perfectly.

Set max freq to 500 MHz in SetCPU's main screen

I cannot:

Set a max of 800 MHz or lower (haven't tried 1000...) in a SetCPU profile - even a "USB charging" profile

As to governors and boot - https://github.com/Entropy512/initramfs_galaxys2_ics/commit/b31e07bc336cd24edb0220b54c544988220f9aeb
[Galaxy S II Original Android Development] kondronaute:
where do I put the script I not fount init.d with ICS files...
[Galaxy S II Original Android Development] Entropy512:
Nothing at all showed in Wireshark, not even the dreaded BT-AMP bug signature? (Protocol 0x886c at around 1 Hz)

Once that bug starts, it never stops until you turn off wifi - even if you're not near any access points. It's phantom traffic that comes out of the BCM4330.

It was really common in AT&T UCKK6, semi-common in XWKK5 based on some reports, and very rare (but I did see it twice) in XWLA4.
[Galaxy S II Original Android Development] rauschkugl:
read 3 pages back and you'll have your answer. is it that hard to read some pages before posting?
[Galaxy S II Original Android Development] rauschkugl:
no you don't have to ask for permission, but if he already posts that he wants to do the github stuff and repository first and fix this issue before releasing the next version it's pretty rude to ask that question some hours later if you already read what he said according to the next release. give him time to work, it's not his job to develop this kernel, he also has other stuff to do.
[Galaxy S II Original Android Development] robertobsc:
Hum, didn't test it. I'll take a look

Enviado de meu GT-I9100 usando o Tapatalk 2
[Galaxy S II Original Android Development] m1trand1r:
i did now...but it says that i don't have lulzactive governor enabled...so i guess it's not working this way....

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

Sent from my SGS-II powered by CM9

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[Galaxy S II Original Android Development] robertobsc:
Yes, it doesn't work. Only for lulzactive.

Enviado de meu GT-I9100 usando o Tapatalk 2
[Galaxy S II Original Android Development] shawnaye:
argh, so i gotta purchase SetCPU app! something deep within me is holding off!
[Galaxy S II Original Android Development] pikachu01:
You can use ThunderBolt! scripts and then edit it from there :)
[Galaxy S II Original Android Development] GoJo ^^:
Doesn't work on paranoid Android
[Galaxy S II Original Android Development] michyprima:
anyone?
[Galaxy S II Original Android Development] enigmatyq:
Sir, and all are facing this issue: "The extweaks settings don't apply after a reboot" Move ExTweaks.apk from data/app in system/app and set permissions to rw-r--r-- , launch ExTweaks - make your settings - REBOOT - ENJOY . In order to set the file permissions all you need is to have Root explorer/Browser or similar type off file manager app been installed on your phone, with Root access.
[Galaxy S II Original Android Development] :
Please delete this post!

- I am asleep and write stupid comments before reading -

Cheers!
[Galaxy S II Original Android Development] switchgott:
Big thanks for best kernel,

But, i have a problem bis cm10 and neweset siyah.

The auto brightness doesnt work!

The display is to bright.

Any idea?

I set it with extweak, but now way.

---------- Post added at 08:03 AM ---------- Previous post was at 07:35 AM ----------

Big thanks for best kernel,

But, i have a problem bis cm10 and neweset siyah.

The auto brightness doesnt work!

The display is to bright.

Any idea?

I set it with extweak, but now way.
[Galaxy S II Original Android Development] snalfio:
Same situation here : cm10 + Siyah 4.1.2 and the auto brightness doesn't works!

Sent from my Samsung I9100 powered by CyanogenMod 10
[Galaxy S II Original Android Development] stopro:
Just installed 4.1.2 cwm and got soft brick had to install tar a Roberto your lulzactive is more bat friendly then pegasus
[Galaxy S II Original Android Development] Sandor1:
Anyone ??????
[Galaxy S II Original Android Development] GoJo ^^:
I also think misc is car charger. And iPad needs 1A, not 2A. ..
[Galaxy S II Original Android Development] Many40:
Hi, sorry for that: if you expect an answer for this kind of (important) but non-dev related questions better read the first sentence of this thread on page 1 (in red colour and big letters). Pls don't feel offended - it applies also to some other guys who don't read OP or don't care what GM decided to post here. Regards
[Galaxy S II Original Android Development] jocaferlo:
You're right, but reading so many threads you forget where you are .... and in this same thread I had seen several comments about this item.

I'll post in the correct thread.
[Galaxy S II Original Android Development] robertobsc:
Hi guys,

Just to tell I had a sod. :eek:

:eek:

It was in deep sleep.

I'll see if was LulzactiveQ or no, but if you have this set the screen_off_min_step to 11 , I think i make to agressive setting to 14.

Enviado de meu GT-I9100 usando o Tapatalk 2
[Galaxy S II Original Android Development] red.hat:
Same here, I had one of those this morning. I also noticed extweaks and lulzactiveq are not working together. I noticed a massive battery drain this morning. Using setcpu for changes and will see how that goes.
[Galaxy S II Original Android Development] gokhanmoral:
my wife has also reported several SODs this morning and I asked her to select pegasusq.

she says everything is fine now.

lulzactiveq may need some fixes. unfortunately she has no idea what last_kmsg is but I am sure there will be some people who will post some logs to help roberto on that.
[Galaxy S II Original Android Development] Many40:
Same here. Changed screen_off_min_step param from 11 (default) to 14 as you recommend. It seems works well now (will observe).

Just for your info you are not aware of this. SetCPU interpretes a few parameters' values in a quite "strange" way: author (text), tuner(text), freq_table(list of frqs) reading default values as "-1". Does it matter for us?
[Galaxy S II Original Android Development] tendan:
Ouch! :(
[Galaxy S II Original Android Development] cop1976:
I also had two SODs today on newest kernel. One with lulzactiveq and another one with on-demand governor. Unfortunately i can't send you a log.

I've back to 4.1.1 kernel because i need a stable phone (I'm going to work soon). Anyway, you doing a great job. Thx

Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
[Galaxy S II Original Android Development] robertobsc:
Yes, I couldn't catch my own last_kmsg. I don't know if kernel generates it with a sod problem does he?

My initial theory is that he can't wake up with this low screen_off_min_step frequency that i set, let's see if it solves...

No doesn't matter. They are just informative parameters. I thought about removing them but I decided to let equal as lulzactive.

Enviado de meu GT-I9100 usando o Tapatalk 2
[Galaxy S II Original Android Development] red.hat:
Changed screen_off_min_step to 13 instead of 11 or 14.
[Galaxy S II Original Android Development] nihilista:
I had my first SOD within some weeks with some new kernel versions. Happens after setting governor to lulzactiveQ, seems like this governor already has some problems. Back to pegasusq, which seems to be stable, and since last changes its good again (turns off second core not only if screen is off...). OK, i set screen_off_min_step to 14, maybe that is a problem, but i didnt test it again and changed back to pegasusq ;)
[Galaxy S II Original Android Development] Mutalisk:
Changed screen_off_min_step to 11, SODs still happen.

Last_kmsg only shows bootloader.

If I get one, I'll post it, but I think it really is a governor bug :)
[Galaxy S II Original Android Development] Many40:
Other way round. You should have changed to higher value. 11 was default - change to 13 or 14. Regards
[Galaxy S II Original Android Development] red.hat:
Change it to 14 not 11.
[Galaxy S II Original Android Development] Mutalisk:
I though 1 is 1200mhz, 2 is 1100 and so on?

But I had 14 since yesterday, more SODs than with 11 ;)

Edit:

Anyway, danger of getting OT, sorry ;)
[Galaxy S II Original Android Development] m1trand1r:
I've woked up this morning and phone was in freeze state:eek:

with lulzactiveq governor from yesterday....but that's not the only issue i got....after a reboot i lost my connectivity....no network at all...i had to set it manually....is it possible that this is kernel related...?

switched back to siyah v4.1rc1 and all is fine again....;)...it happened after i firstly flashed siyah v4.1.2..i also flashed KH3 modem.bin...(way better connectivity & lower temp. than ever before)....

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

Sent from my SGS-II powered by CM9

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[Galaxy S II Original Android Development] Gawis:
with latest version, I had 2 SOD's with pegasusq today, switched to ondemand and seems fine for now..

Sent from my SGSII CM10 with Tapatalk 2
[Galaxy S II Original Android Development] karlesg:
I'm using 4.1.2 with pegasusq on a Sammy XWLPG based rom. No SOD's, no problems so far.
[Galaxy S II Original Android Development] robertobsc:
I just got a sod with last_kmsg on (thanks god)

Now I can investigate what's going on.

Strange thing that this problem didn't happen at all during my tests (3 or 4 days using without problems)

Enviado de meu GT-I9100 usando o Tapatalk 2
[Galaxy S II Original Android Development] pikachu01:
Wait, what?
[Galaxy S II Original Android Development] gaz617:
Read what he highlighted in red..it's a joke
[Galaxy S II Original Android Development] Tungstwenty:
Sorry, I need to be more careful about the subtlety level of my jokes :D
[Galaxy S II Original Android Development] bgx:
*lol* made my day! :laugh::laugh::laugh:
[Galaxy S II Original Android Development] wjchen0:
See this file line 68,it caused by a typo.

Not "mv /sbin/adb.jb /sbin/adb",and "mv /sbin/adbd.jb /sbin/adbd" is right..
[Galaxy S II Original Android Development] Tungstwenty:
Correct.

I don't know where did GM compile this from, but taking into account the fact that there's a specific binary for JB it can well be the root cause. Perhaps renaming the binary by hand and restarting the service will make the permissions work as before and solve the issue on Eclipse.

I'll test it out when I can afford to boot into my 2nd ROM.
[Galaxy S II Original Android Development] Crescendo Xenomorph:
Just hot 2 random reboot with v4.1.2. Couldn't get last_kmsg, but I got this new 3 files (attached) under /data/log after reboot.

Both reboots was occurred during sleep...

Using Linux Script Default while this happened, now changed back to Thunderbolt.

ExTweaks: Max Gamma 12, v(R) sched, BreathingFX, EarGasm +1.5db, ZRAM disabled.

CPU: Default voltage, 200-1200Mhz, PegasusQ, Hotplug Mode, gentle_fair_sleepers, Thunderbolt Script Default.

GPU: All default settings & voltage, Mali Boost 2.
[Galaxy S II Original Android Development] nihilista:
Next SOD here, this time with pegasusQ. Maybe its while using Thunderbolt script? Will try....

Sry, no log here...
[Galaxy S II Original Android Development] Tungstwenty:
I tested moving it with an init.d script:

#!/system/bin/sh
mount -o rw,remount /
mv /sbin/adbd.jb /sbin/adbd

And it now works correctly. It's just a matter of using this until GM fixes that line.

Another thing I noticed is that on the JB adbd there's no root permission. Probably the same source code patch needs to be applied on the JB version.
[Galaxy S II Original Android Development] :
If it's what I'm thinking, ADB root access is disabled on CM10, so you need to enable on Development Tools.
[Galaxy S II Original Android Development] Tungstwenty:
Yes, but that's for the purpose of running "su" inside the shell, or run "adb root" and unplug + plug so that things like "adb push", "adb shell" all run directly as root instead of the shell user. If it's not enabled in Development Tools, it will fail without even a prompt from Superuser. If it's enabled, it's automatically granted.

The patch I mentioned made adbd always run as root, even if ro.secure=1. That way you can immediately run adb commands as root without requiring connecting the cable twice or asking specifically for root permissions.

Of course that given there's a setting for that (at least on JB), ideally the setting could be taken into account and adbd grant either shell or root access depending on that setting. But I'm not sure whether that would be a simple change or not.
[Galaxy S II Original Android Development] arsalanaly:
lulzactiveq doesn't work properly.... i got random reboot ...... stay back with old settings
[Galaxy S II Original Android Development] CamoGeko:
Just use Ondemand.
[Galaxy S II Original Android Development] robertobsc:
Random reboot doesn't make sense to be a LulzactiveQ problem... Some steps for you:

- Post the last_kmsg

- change to pegasusq and keep monitoring.

As soon as I get home I'll focus on lulzactiveq sods.

As more last_kmsg as I get here, the best for me to investigate. If some of you guys can stay in LulzactiveQ and turn debug_mode on, I'll ask you to try to get the sod error and send me the last_kmsg. I would really appreciate this help since I don't have too much time.

Thanks.

Enviado de meu GT-I9100 usando o Tapatalk 2
[Galaxy S II Original Android Development] gaz617:
You got it, this is what xda is for after all!
[Galaxy S II Original Android Development] cybernetus:
One Sod here.

Last_kmsg : http://pastebin.com/TxqL3fWr

Reverting back to 4.1.1

Paranoid Android 1.9.2

Smooth 800 / zram 150 / Mali on / under volt 25

Ondemand governor
[Galaxy S II Original Android Development] Gawis:
Also had an SOD with ondemand so it wasn't pegasusq

Sent from my SGSII CM10 with Tapatalk 2
[Galaxy S II Original Android Development] cybernetus:
Put your last_kmsg here for the developer :)
[Galaxy S II Original Android Development] ROX77:
Hi, I've tried LulzactiveQ with default settings, and after a while (5-10 sec.) CPU was always blocked at 1200 MHz. Even in lockscreen. With charger or not.

When I moved to SmartAssV2 or PegasusQ CPU started again to move in real time (monitored with cool tool and cpuspy).

Now I'm with 4.1.2 and SmartAssV2+NOOP and I've no problem.

Hoping to be useful ;)

PS: ROM 4.0.3 LPG based
[Galaxy S II Original Android Development] red.hat:
No random reboots or sod here since I changed screen_off_min_step to 13.
[Galaxy S II Original Android Development] FadeFx:
This is neither useful nor any help to the dev i guess

------------------------------

tapatalked from Galaxy S
[Galaxy S II Original Android Development] bleuxeon:
No offence hey?! But let me ask... why do you use that "old" ONDEMAND or that realy "immature" LULZACTIVEQ rather than the powerfull and battery friendly PEGASUSQ? :)
[Galaxy S II Original Android Development] :
respect the dev, brother.

ondemand >>> pegasusq in performance.

Don't know much about lulzactiveq, but give the dev some respect, if gokhan put his work on the kernel, should worth something.
[Galaxy S II Original Android Development] red.hat:
I beg to differ, in the last few post I mentioned I had SOD while it was set at 11. The Dev requested Sceen_min be set at 14, I have done that and reporting the effects. Atleast we know it works for some people for now ( I could be wrong come tomorrow morning) Am sure not everyone is having SOD or issues with the new governor.
[Galaxy S II Original Android Development] cybernetus:
bleuxeon here, on my Paranoid Android I have better results with the old ondemand :)
[Galaxy S II Original Android Development] bleuxeon:
Roots of Gok's choice could also be elsewhere...
[Galaxy S II Original Android Development] red.hat:
Roberysc, I noticed something. You wanted the screen_off_min _step to be set to 14 from 11 or is that vice versa ( or am I having problems with the English Language? ). This parameter is set at 14 here (red). Please clearify.

This is only a battery profile suggestion for the 16 steps. Please explore it!!!!!!

-- Parâmetros Lulzactive

echo "90" > /sys/devices/system/cpu/cpufreq/lulzactiveq/inc_cpu_load

echo "40" > /sys/devices/system/cpu/cpufreq/lulzactiveq/dec_cpu_load

echo "1" > /sys/devices/system/cpu/cpufreq/lulzactiveq/pump_up_step

echo "2" > /sys/devices/system/cpu/cpufreq/lulzactiveq/pump_down_step

echo "50000" > /sys/devices/system/cpu/cpufreq/lulzactiveq/up_sample_time

echo "25000" > /sys/devices/system/cpu/cpufreq/lulzactiveq/down_sample_time

echo "14" > /sys/devices/system/cpu/cpufreq/lulzactiveq/screen_off_min_step

-- Lulzactive - Hotplug Queue parameters

echo "50000" > /sys/devices/system/cpu/cpufreq/lulzactiveq/hotplug_sample_rate

echo "13" > /sys/devices/system/cpu/cpufreq/lulzactiveq/cpu_up_rate

echo "13" > /sys/devices/system/cpu/cpufreq/lulzactiveq/cpu_down_rate

echo "600000" > /sys/devices/system/cpu/cpufreq/lulzactiveq/hotplug_freq_1_1

echo "400000" > /sys/devices/system/cpu/cpufreq/lulzactiveq/hotplug_freq_2_0

echo "350" > /sys/devices/system/cpu/cpufreq/lulzactiveq/hotplug_rq_1_1

echo "300" > /sys/devices/system/cpu/cpufreq/lulzactiveq/hotplug_rq_2_0

echo "0" > /sys/devices/system/cpu/cpufreq/lulzactiveq/hotplug_lock

-- debug on/off

echo "0" > /sys/devices/system/cpu/cpufreq/lulzactiveq/debug_mode
[Galaxy S II Original Android Development] cybernetus:
DELETED
[Galaxy S II Original Android Development] Gawis:
I was testing ondemand since I had several SOD's with pegasusq, didn't test lulz yet :)

Sent from my SGSII CM10 with Tapatalk 2
[Galaxy S II Original Android Development] bleuxeon:
ok ok ok...

So I did some bench with the today's update of Antutu (it wasn't properly working anymore under Jelly Bean)

I have made 2 test run @ 100mhz-1400mhz :

ONDEMAND :

1rst : 6799

2nd : 6724

avr : 6761

PEGASUSQ :

1rst : 6746

2nd : 6863

avr : 6804

So PEGASUSQ is at least equal if not supperior to Ondemand with a less creasy jumping frequencies...

Also no need to say that PEGASUSQ is now lag free, stable and so on under any application (Google Earth, GPS tracking, Chrome etc..)
[Galaxy S II Original Android Development] ROX77:
Even Tapatalk lagfree?! I can't use pegasusq with taparalk, it's frustrating. Smartassv2 better.

*Inviato col mio Aifogn rettangolare brevettato :cool:
[Galaxy S II Original Android Development] Scarface1991:
I`m on 4.1.2 and everything is good so far on smartassv2 and noop.

Has anyone tried to use the "Orbot:Tor on Android" App with the Siyah Kernel?

If you enable transparent Proxying (enables single Apps to go through a proxy) it doesn`t work. I just get the Message: WARNING error starting transparent proxying.

I tried this once before with a stock Samsung kernel and it worked but with all custom kernels I tested so far, none has worked with Tor on Android.

Is there something that can be done?

I`m on Resurrection Remix 2.6.1
[Galaxy S II Original Android Development] Sm0L:
Went back to 4.1.1r1 because in 4.1.2 sometimes the phone doesn't comes back to live (black screen)
[Galaxy S II Original Android Development] :
benchmarks: bullshi7. Will never say what a kernel really is. Developers can easily manipulate those benchmarks, to make it better. But it's also possible to lower the benchmark to increase performance. I remember that SpeedMod has schedmc activated, so it decreased drastically benchmark, but no (or almost) performance were sacrified. Sorry to say that, but anyone believing benchmark as a signal of greatness should study a little more about it. Know why? The cake is a Lie!!