yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] djsolidsnake86:
also here wifi toggle broken, 8.28
[Galaxy S II Android Development] Georgie9117:
+1
[Galaxy S II Android Development] manan001:
reported... plz dont repeat...
[Galaxy S II Android Development] officiallyme:
wifi toggle working on 9.28 as should

rom = rootbox 4.0
[Galaxy S II Android Development] m1trand1r:
it's all ok on 9.28....on 8.28 is bugger...or like dori said few posts back....it might be ROM related....:)

Sent fom my S-II running >>SlimBean build 6 OFFICIAL<< :D powered with >>DorimanX kernel 9.28<<
[Galaxy S II Android Development] Kai Disobey:
Here on 8.28 must hit wifi toggle twice after deepsleep, but it works.

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II Android Development] Jigen90:
Hello everybody,

probably this problem belongs to discussion thread, however I'm experiencing this issue during music playback since old 9.14 kernel.

I'm currently on 9.24, rom CM10.1 0306.

Whenever I play FLAC files or MP3 320kbps with Apollo and dsp manager activated (I mean DSP and Bass tweaks), when I turn off screen music stutters.

If I leave CPU GOV sleep settings to default, stutter is frequent.

So I thought was a GPU sleep GOV problem and I switched it to HYPER, having same both sleep and awake governor; but that didn't solved the problem.

I tried to switch to performance profile, but no solution.

I tried to transfer all the files to internal memory card (avoiding saving them on external), but no luck.

I tried changing I/O parameters: scheduler and kilobytes_to_read-ahead, again no luck.

I raised up SCALING_MIN_STANDBY_FREQ to 400Mhz, no way.

I tried to copy completely AWAKE and SLEEP governor settings, to reduce the switching overhead, again no way.

The only solution I found is to disable completely cortex background process, in this way I do not hear any stutter during playback with screen off.

I thought was ROM related, I wiped everything and re-installed everything. Wiped kernel with different scripts and flashed from scratch, but no way.. music stutters.

Any suggestion? Am I the only one?

It's frustrating.

BTW Dori keep up the amazing good work! :D
[Galaxy S II Android Development] arjag:
second freeze>auto reboot today. earlier I changed modem and rill, just fyi.

very rare I would get two in a day on any version. hopefully my logs are of some use.

dorimanx_last_kmsg_log-20130606.2

Dorimanx-V9.27 + HyperDroid AOXP 1.11-UO

@VG3

swyped from my i9100 with tapatalk 2
[Galaxy S II Android Development] dorimanx:
thanks, for debug info..

so with cortex off, all ok?

I think it's the

BUS_THRESHOLD()

{

local state="$1";

if [ "${state}" == "awake" ]; then

echo "$busfreq_up_threshold" > /sys/devices/system/cpu/cpufreq/busfreq_up_threshold;

elif [ "${state}" == "sleep" ]; then

echo "50" > /sys/devices/system/cpu/cpufreq/busfreq_up_threshold;

elif [ "${state}" == "wake_boost" ]; then

echo "25" > /sys/devices/system/cpu/cpufreq/busfreq_up_threshold;

fi;

log -p i -t $FILE_NAME "*** BUS_THRESHOLD: ${state} ***";

}

change to 50 on sleep.

when you tested, USB/charger was connected? or not? (important!)

thanks.
[Galaxy S II Android Development] Jigen90:
Stutter occurs without charger plugged in. I'm sure.

I've to try with usb/charger connected. I really don't remember.

Now I'm raising up busfreq_up_threshold to 50% and I'll post here results.
[Galaxy S II Android Development] fractaline:
Just flashed rootbox 4.0, full wipe. Then 9.28. After titanium restore

Got a freeze while changing theme... :( had to hold power to reboot.

Maybe just a one off. But here is the log. I tried to get a logcat on my Linux machine but it stayed at "waiting for device"

http://db.tt/Ufi9LjLj

~PHØN€Ð ÎN~
[Galaxy S II Android Development] pSyCh¤_O_O:
Damn...i unplugged from charger this morning and when i looked at phone in car it was OFF.

I thought i pressed power button by mistake. But it must have switched off because it was quite hot when i grabbed it.

Log:http://db.tt/Qy1f0N7s

-Default profile

-I did change awake and sleep govs to nightmare.

-Oom levels both set to default

-Group 2

-Vpll mode On

-Not UV'd yet

-Fusionjacks v2 (i know Dori said it bugged but i dont want to revert yet because it seemed stable for me)

Testing with stock settings now. Will see how it goes.

RootBOX latest

DorimanX latest

Link to DorimanX Discussion Thread
[Galaxy S II Android Development] dorimanx:
dont set nightmare as SLEEP gov, some bug that alucard still seek how to fix.

BUG == SOD on sleep if Nightmare selected as sleep gov.

Use any other.
[Galaxy S II Android Development] MICa.fighter:
just got a freeze(not the scrolling problem) reading the thread in xda premium app, i had to hold pwr button to reboot

here is a last kmsg hope it can help.

rom: rootbox 4.0 stable

kernel: v9.28

cpu group 4
[Galaxy S II Android Development] jpeg725:
Status report:

Setups:

Ubuntu 13.04 (64bit not in vm)

LinuxMint 13 (ubuntu 12.04 64bit not in vm)

Both distros are fully up to date with all cm-10.1 build dependancies, all linux kernel build dependancies installed (sudo apt-get build-dep linux-image-lowlatency)

Result:

In both cases the same: Everything seems to go absolutely fine, no error messages, and the files created are the right sizes, but it will not boot.

I never doubted you there.

As far as I can tell I have been a good boy and done everything I should have. But still no luck. I suppose I shall have to give up.

Would one of you be willing to send me a list of installed packages so I can compare with what I've got installed?
[Galaxy S II Android Development] dorimanx:
Alert to all Testers of X.28 kernels

Please set OOM on screen ON to Aggressive in STweaks Memory tab.

To fix small lags and delays from low RAM.

I will tune it to be OK on default in next kernel.

Thanks!
[Galaxy S II Android Development] leechseed:
Hi dori,

seems like its still missing + "old" busybox

Attached

Dorimanx 9.28

Slim / CM

Greetz

SlimBean-b6|KangBang-v1|i9100¬Tapa2
[Galaxy S II Android Development] MacDeath:
just type "ifconfig" in terminal, not "busybox ifconfig" and it should work.

ROM: SlimBean 4.2.2 build 6

Kernel: DorimanX 9.28

Baseband: XXLQ6
[Galaxy S II Android Development] gingersandwich16:
Good news: RR3 and Co now work!

Bad news: already got freeze :( carbonROM w/ 9.28

Kmsg attached
[Galaxy S II Android Development] Sun90:
Well the Cortex enable/disable has got something to do with the music stutter when screen turned off.

Checked with inc of Bus_threshold inc to 50 and music still stutters when cortex is enabled with USB/Charger connected or with out.

but once the 'Cortex' is disabled even at Bus_threshold set to 25 the music will not stutter while connected to USB/Charger or with out the same :)

So to concluded for now 'Cortex' turned ON = Music stutter when screen OFF

And 'Cortex' turned oFF = no music Stutter when screen OFF .

But the funny thing is that now with 'cortex' disabled, music stutters when using 'Home' or 'Vol wake' or 'Slide 2 wake' to turn On the screen, with USB/Charger connected or with out it :)

All above as seen with RB V4.0 and Dori v9.28 :)

Hope this helps a bit :)
[Galaxy S II Android Development] MICa.fighter:
hmm v9.28 seems to hate my phone :(

got another freeze while looking around in stweaks, i had to hold power button again.

rom: RB v4.0 stable.

cpu group 4.

i have set oom to agressive as suggested, everything else is default.

here is a > last kmsg <
[Galaxy S II Android Development] Flint2:
Had ROM Soft Reboot while installing Gmail 4.5 from Playstore.

Phone connected to pc by USB

Attached dmesg: View attachment dmesg.txt

Attached profile diff with default: View attachment diff_profile.txt

RootBox 4.0 , DorimanX 9.28, Voltage Group 4
[Galaxy S II Android Development] Thristle:
had an SOD with 9.28

everything is default,CPU is group 3
[Galaxy S II Android Development] MICa.fighter:
wierdest thing happened. i was trying to search in google search app while phone was on charger. suddenly the phone got mega lag. it was still responsive, but it was like a slow motion movie. i managed to open stweaks app and grab logs without rebooting.

dori v9.28, govs: pegasusq/pegasusq , io: sio/sio, everything else is default (oom tuning too)

rootbox v4.0 stable

cpu group 4

dori debug

dori debug logcat
[Galaxy S II Android Development] oL00No:
Use aggressive settings in rom toolbox. I told dori. Don't know if he's taking the advice. My phone did like yours. Cooltool clearly shows that low mem is doing it.

Also, doris oom then panics and releases random memory, including front activity.

Dori: could you add an option to disable your oom?
[Galaxy S II Android Development] Conny84:
[MENTION=4685275]oL00No[/MENTION]
[Galaxy S II Android Development] oL00No:
Yeah, I got that. But I still don't find it as good as manual handling. So I have suggested a "disable" feature from dori the kernel wizard, and stated my reasons for doing so, as per the rules of this thread.
[Galaxy S II Android Development] Crazy-Silver:
Had a SOD while unlocking.

Default profile with nightmare gov on screen on and Scary on screen off .

Rom : JellyBam 7.8.0

LastKmsg on DropBox

http://db.tt/ktMBtHDy

Edit : Sorry but my last kmsg is empty. I don't know why.
[Galaxy S II Android Development] m1trand1r:
change gov from nightmare to hyper or pegasusq....nightmare never worked for me as it should...:eek:

edit: i'd change rom if I were you too...cuz i've heard some bad things about jellybam rom:confused::eek::confused:
[Galaxy S II Android Development] galonpzw:
Got some sod on lock screen, and someusing phone. CM10.1 yesterday nightly, and newest Dori.

CPU Group 1, awake Hyper, sleep ondemand, oom agresive, i/o sio
[Galaxy S II Android Development] cybernetus:
Froze when I'm use uninstall

Dori debug http://pastebin.com/qN0KALeJ

Last kmsg http://pastebin.com/n9Kwdqeb
[Galaxy S II Android Development] jgcaap:
First time that I got a sod.

http://db.tt/xOPiFkMh

Hope it helps

Sent from my GT-I9100
[Galaxy S II Android Development] mofeywalker:
Hi guys,

I had 2 or 3 SOD since upgrading to 9.28.

Here my last_kmsg from just a serveral minutes ago. I hope this will help you.

https://dl.dropboxusercontent.com/u/2354858/dorimanx_last_kmsg_log
[Galaxy S II Android Development] P0tato:
Ok here's my report:

Everything is smooth and fine no SODs or freezes yet, BUT!

-Wifi toggle is buggy (it was ok on v8.24 then after 8.24 it is buggy)

-FM Radio not working (can't switch it on)

-Lockscreen unlocking is laggy (often)

ROM: Omega v23 XWLSN

Kernel: Dorimanx v8.28

Profile: Performance

Changes: Sleep governor is zzmoove (with ondemand lockscreen unlocking is more laggy)

kernel_debug

SORRY 4 MY BAD ENGLISH
[Galaxy S II Android Development] blaex:
Hi Dori,

here my donation (macciato cup) 0K008459FG610883W

thanks for improving the stweaks app and kernel. deep sleep works better for no me with official XWLSN @8.27/8.28.

great point, that you keep an eye on secruity related issues & fixes for our phone, love to see more focus on it, performance wise ::)
[Galaxy S II Android Development] jmarcnms:
Hi

Tried this 8.27 then 8.28.. am also experiencing laggy screen unlock cases (especially when the phone has not been rebooted for very long time like 15hrs or more.. note that when reboot is pretty fresh, system is very responsive and smooth).

Another thing, I happen to use viber quite a lot, and sometimes in call, when screens locks for battery saving, unlocking even if successfull will be a black screen on viber app itself... but bkg isn't dead, i can still get back to the home screen while in call.. just that viber app gui itself has that sod like behavior until hand up.. i don't see that with stock or rooted kernel based on stock.

Another minor issue is that i get every sometime a small crack or noice while listening to music via the music player (mp3).. which i don't normally get. not happening too often.. but still noticable.

Thanks for the hard work, keep it going!

Cheers
[Galaxy S II Android Development] MICa.fighter:
just got a sod. its a first for me in 9.2x

kernel: v9.28

rom: rootbox v4.0

stweaks: agressive screen on oom, everything else is default

> last kmsg <
[Galaxy S II Android Development] jgcaap:
http://db.tt/xOPiFkMh

Happen again. Thanks

Sent from my GT-I9100
[Galaxy S II Android Development] /dev/null/:
i have a sod today

http://db.tt/8rlCf3OR

http://db.tt/xuKPu090

phone is still laggy on lockscreen, even with zzmove sleep governor
[Galaxy S II Android Development] astrogambit78:
Wow Dorimanx you are fast. 2days ago i downloaded v.5.0a then v.5.2 is out. :eek:

You really know how to address/fix issues with your creation.

Amazing mate:good::good:

downloading v.5.2 now:) and will try it.
[Galaxy S II Android Development] xanthrax:
i just flashed dilidroid and then without reboot dorimanx 5.2 .

no issues so far and quickmark (barcodescaner) is ok as well

Ucam doesn`t give FCs on frontcam neither stock camera

i still didn`t get your problem guys with camera ...
[Galaxy S II Android Development] dorimanx:
good, :)

I just ported more stable CPU code from GM kernel, actually just restored many things i have added from other sources, and some that i messed with,

looks like now things getting better and faster! and still with good battery life,

still working and testing, i hope i will share new kernel today / tonight

I found what was missing for HDMI and set it back, so, now it's WORKS, sadly only for SAMMY roms. (kernel 5.2)

thanks for reports and testing :)
[Galaxy S II Android Development] Crazy-Silver:
Dori i asked it to you a lof of times but i hadn't an answer.... Can you improve colors as neak/thoravukk/fluxi/abyss?
[Galaxy S II Android Development] HyperEscape:
Hello,

I have installed Resurrection Remix 2.6 on SGS-II as the primary ROM and then tried RootBox as the secondary ROM.

The kernel is Dorimanx 5.0 , I have been experiencing random shutdown of the phone. This has happened with only the single RR 2.6 as well as with dual RootBox ROM as well. It has happened when the phone is idle as well as during a call.

I am now trying to upgrade to Dorimanx 5.2, but aint got no clue to why it must be happening. All the settings in ExTweaks are left to as-is on default selections.

Can anyone guide me with possible reason or a place to trace any system log to do troubleshooting or how to avoid this annoying problem. I am afraid that can It be due to any hardware fault. I have seen the same behavior with stock battery and an aftermarket Anker battery as well.

Thanks for your input.
[Galaxy S II Android Development] freewind29:
I just found a camera fix from the thread of paranoidandoid, after the fix applied, barcode scanner is working fine now.
[Galaxy S II Android Development] sobirin90:
Dori just simple question..

Is it every time you release a kernel.. It's already been set for optimum in terms of batt life and performance... Coz I just flash 5.1 and average batt life I would get is around 8 to 10 hours with standard battery.. And I didn't touch Extweaks settings except for the BLN. And for me it is good enough :)

And I wondering what is the fuss of camera bug? Haven't have any issues except sometimes not responding but it can be used again when I reopen the camera app..

Last but not least... U are great dev Dori.. I wished I had few extra bucks to donate.. But I will donate to you soon.. And ignore those ungrateful people.. They just gonna be around to entertain us. :p

Sent from my GT-I9100 using Xparent ICS Tapatalk 2 powered by Paranoid v1.6 with Dorimanx 5.1
[Galaxy S II Android Development] sobirin90:
I'm using the same rom with you.. And don't have any problems.. Guess you missed the camera fix zip on the thread eh? Hehe. :)

Sent from my GT-I9100 using Xparent ICS Tapatalk 2
[Galaxy S II Android Development] Jagdish84:
Can't seem to resolve betterbatterystats app not showing kernel wakelocks...

Removed n reinstalled root via extweaks and giving it proper permissions, reinstalling app itself trying earlier releases as well and just when I switched to dream kernel I got it to show...

I just can't think of anything else...

Sent from my GT-I9100
[Galaxy S II Android Development] MDE_86:
Since its mainly based on Siyahs kernel maybe changing to Chainfire SuperSU night help...just an option not sure if it will.

Tapatalk / SGS2 / Cyanogenmod 9 Nightly / DorimanX Kernel.
[Galaxy S II Android Development] muralikrishna72003:
I was having the same issue. I just plugged and unplugged the charger. You can try the same

---------- Post added at 10:20 PM ---------- Previous post was at 10:14 PM ----------

I was having the same issue. I just plugged and unplugged the charger. You can try the same to get the kernel wake locks.
[Galaxy S II Android Development] AndehX:
Interested in trying this kernel. My main focus is battery life though. Does this kernel provide better battery life over Siyah 3.4?
[Galaxy S II Android Development] papazaf:
i have updated to the new version 5.2 since i have spontaneous restarts , and spontaneous turning on of the screen

my rom is NeatRom Lite v3.0.1 Themed, any suggetions?
[Galaxy S II Android Development] aceian:
No one would give you a perfect answer for that..

Try both and decide for yourself.
[Galaxy S II Android Development] chabstyle:
Hey Dori,

why do i have so much Kernel Wakelocktime?

MFG chabstyle
[Galaxy S II Android Development] XPLOSIV10:
Great Kernel! I will use this!
[Galaxy S II Android Development] sd65:
Did you release the battery for a minute to prevent Wakelocks ?

(Better to release when battery charged to 100%)
[Galaxy S II Android Development] Pigmachine:
Yes yes.. I know you all hate me.. now we got that over with :crying:

It's now back to being a dev-thread!

Just a constructive observation. On Kernel_Dorimanx-SGII-ICS-V5.2--T-02-15-D-23-07 the Extweaks saves even for me! It however lose the settings when: Making a backup, changing modem, flashing another MMS.apk.. and most of the stuff that concerns actions in recovery.

But I have found a solution for that one, that works (for me).

When you reboot and notice your ledlights are brighter again (I have mine at 2700mv always) you know that the Extweaks are currently screwed, when you check them, most refer to /data/.siyah/.custom.tmp not existing. Just change a few settings, preferably one that says something about /.custom.tmp and that is don't exist, apply and exit.

Leave it alone a while, go back and see that the ones claiming it didn't exist now are back.. change a few settings at a time, applying as you go along, exiting extweaks in between.. and with some luck you get all the way to the cortexbrain, where if demands a reboot for the settings to take effect, apply, exit and leave it alone a while :fingers-crossed: and with more then 50%+ probability you have the settings saved.

Did that most of the day yesterday too, but it never took.. but now it's on the right track, even for my phone :good: All phones are a bit different, so are all roms!

(Sorry about being a ***** yesterday, but things impossible to fix with reading everything, and trying everything for most of a day really gets to me)

I know I shouldn't even have posted when angry!.. and the public excuse is to Dori.. not the lynch-mob, that were even less constructive then me..
[Galaxy S II Android Development] sd65:
Here my FeedBack fot the 5.2 : :cowboy:

Good Job :

- The Kernel Boot picture is Great ! :D

- So many Tweaks ! I love it ! Keep it that way, I really enjoy the Wifi Scan setting in Extweaks :laugh:

And you find some inovations, out of the blue but also sweet.

- The cycles of the Releases are Fast and you read what people write about their issues in this Thread :good:

Problem :

- The "Boot of the Kernel" (I don't know the real name, like the 'POST' to acess the Bios on a Computer) is really Slow !

When I reboot in Recovery, it takes some time to display the CMW menu...

(And the Progress bar is kind of gadget ^^)
[Galaxy S II Android Development] Crazy-Silver:
Thanks mate..... I did it some weeks ago and I like that you like it :D
[Galaxy S II Android Development] manan001:
hey dori request... can u implement new governors (specially tweaked slp and zzmoove) and symblink fix that u did in 8.27 on 8.14... as its stable version will help with everything working great...
[Galaxy S II Android Development] MICa.fighter:
personally i dont see the pont. the kernel has a lot of changes since 8.14 which are not stable for everybody YET. dori will fix it eventually just be patient. u can follow his git to see progress. thats my personal opinion, and im not part of team dori, im not speaking in their name :)
[Galaxy S II Android Development] eskriminal:
generally governor additions should be okay, as stability is only affected if you use it, however dori said before to me that making governors use the intelli plug hotplugging logic is sometimes difficult (reason why he disabled lulzactivew he was working on I believe)
[Galaxy S II Android Development] Alex-stroev:
Hi, Dory. Can you add UV to Screen controller voltages and Memory voltages like in hirox kernel?
[Galaxy S II Android Development] deepal56:
Still having wifi toggle problems with dori. v8.28.

Rom- Alliance v8
[Galaxy S II Android Development] Kai Disobey:
Then downgrade to 8.14 or 8.16 they are stabel, everything works and by the way more battery friendly :good:
[Galaxy S II Android Development] 089man:
Hi dori, have canched from aosp to stock rom, Specialy biftor rom.

Now I must take the 8.28 kernel.

Will say that it's works fine without issues or freezes since one day with this rom. Much better as with cm rom. Smile.

I9100 Tapatalk 2, Rom1 Biftor / Rom2 , Kernel Dorimanx
[Galaxy S II Android Development] Kyuuba:
I had a little issue with STweaks.

I was playing Dead Trigger with the GPU overclocked and then, I always have backed up the current profile I'm using even after I make any change, after an hour, the OC applied on GPU disappeared making it all default under GPU settings, everything else was ok as I set before.

Had to restore the desired settings again using the profile backup.

ROM: Omega v 23.
[Galaxy S II Android Development] GamingDj:
New update 9.28 is stable.No freezes/lag/SOD for 2 days.
[Galaxy S II Android Development] dorimanx:
no, no time to mess with voltage, that YOU or ME, should not TOUCH EVER!