yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] sharp87:
Ya thats right people make a furthermore lengthy conversation by quoting my post..People dont know what informations are needed for future DorimanX Kernel :) .. And sadly I forgot to mention at last line of my previous post

"I know what I'm doing... ..NOW stop quoting my post further.. (^_-)..Peace!!!! "

Well 9.43 v37.1 had one screen freeze and never had this before..I will reflash the rom and kernel and making sure its not problem frm rom or too much of my custom scripts i had installed :) guys b cool ;) ..
[Galaxy S II Android Development] nihilista:
If device is absolutely stable over 3 or more days (was with v24,v34 seems to be nearly as stable as...), and the only thing that changes is kernel, then for me its logic, that its not an rom instability.... Btw, one sod in 2 days its nearly acceptable, its the price for using experimental kernel with some good features ;)

The only thing i can say is that we got close to stable, but with every new code line there can be new bugs, maybe i'm wrong, but thats my understanding from what developer does....
[Galaxy S II Android Development] 7HUND3R:
Well I have to say that my device was rock stable with v22 and with upper versions it freezes and get sods, then I rolled back to v22 and everything ok again..then I thought it was kernel related but the majority of people here was doing fine with upper versions and with the same rom as me..so I full wiped my phone and everything is perfect since that time!

I think there are problems that we will never know what cause them but we know the answer: full wipe..

but before try kernel wipe script..maybe it solve your problems without have to full wipe
[Galaxy S II Android Development] jgcaap:
Perhaps you are in fact... Wrong...
[Galaxy S II Android Development] m1trand1r:
9.43v37.1 mv3.....everything is silky smoooooth...I even found time to d/l Clash of puppets game....it's heavy 3d game and runs really smoooooth....thanks devs....you're really breaking the limits all the time....:D:good:

Beam-ed through your pineal gland via//Android 4.3.1:p//
[Galaxy S II Android Development] oL00No:
Master dori: are you still working on zzmanx? Or should the entire beta team maybe force crashes with it and donate more logs? Also, have you considered lowering the amount of freq steps for stability?
[Galaxy S II Android Development] :
Zzmanx stable here? Also 23 hours uptime with v37.1

Sent from a Dorimanx powered I9100p
[Galaxy S II Android Development] oL00No:
I know of more users having problems with it. That's why I ask Dev if he needs extra logs, or If he is tracking it already. But good for you. It's just not helpful.
[Galaxy S II Android Development] jgcaap:
Try get a log . is only way to discover whats wrong
[Galaxy S II Android Development] :
Point is it obviously can be stable so maybe check rom and apps. Full wipe lately? Manual mount and format system and data lately? Also logs are always helpful if there has been a problem. :thumbup:

Sent from a Dorimanx powered I9100p
[Galaxy S II Android Development] cybernetus:
Surprise :)

New build

Maliv3 : Kernel_Dorimanx-V9.43v38-mv3-cybnt-[15-08]-[07-12]-JB-SGII-PWR-CORE.zip

Maliv2 : Kernel_Dorimanx-V9.43v38-mv2-cybnt-[15-23]-[07-12]-JB-SGII-PWR-CORE.zip

8.x : Kernel_Dorimanx-V8.43v38-cybernetus-[15-37]-[07-12]-JB-SGII-PWR-CORE.zip

Commits :

Kernel: Removed Deep sleep function from HYPER,intellidemand,neox,ondemand

Initramfs: Update sbin/ext/post-init.sh, code style fix.
[Galaxy S II Android Development] JulianXhokaxhiu:
This latest commit makes me think something about the Alarm Clock that didn't work either... :)

But unfortunately I'm on CM11 now, and I'll wait patiently when Dorimanx will support it. Until then, I'll continue to follow this topic as always.

Keep up the good work!
[Galaxy S II Android Development] Misk77:
9.43v38 flash and boot up fine. Always Default at this stage at beta. Will reported if any issues.

BBS pic from 1 cycle with 9.43.37.1 uptime total 28 hours.
[Galaxy S II Android Development] AlexVat:
Just got a SoD using the latest version. I'm on SlimSaber with Mali V3. Booted up OK and after 5 minutes, without anything running it went in SoD. All stock, no changes made in STweaks. Hope it helps. Thanks everyone for the time and effort :good:

EDIT: Rebooted now, left it on insert PIN code for 1 minute and another SoD. I just want to point out that it manifests very quickly onmy device. Back on v32 which was stable enough for me. Cheers!
[Galaxy S II Android Development] j1gga84:
Removed Deep Sleep? What does that mean? Can we not use this gov's anymore for DS?

Regards

Sent from my GT-I9100 using german Tapatalk 4
[Galaxy S II Android Development] cybernetus:
This is an information useless to the developer. We need logs.

---------- Post added at 07:43 PM ---------- Previous post was at 07:42 PM ----------

You read the commit ?

Removed Deep sleep function from HYPER,intellidemand,neox,ondemand

Need to check if it's help to wakeup faster. and not effect battery

usage at deep sleep state.

We've talked several times about this ... read the commits. They are your information on what is being tested here.
[Galaxy S II Android Development] AlexVat:
Yeah, I know I should have attached a log to my post, but unfortunately I forgot doing this.

Sorry for giving only half of information :(
[Galaxy S II Android Development] cybernetus:
One doubt. Do you try to use the kernel wipe script ?

Try this :)
[Galaxy S II Android Development] AlexVat:
No, I didn't use the "nuker" but I reverted to the last version now and made a logcat ;)

I will attach it immediatly.

Edit: the catlog txt doesn't get saved :( I will try it via adb and report back. Sorry for taking so long.

Second edit: It gets weirder because I am now logging via adb and it refuses to go into SoD :) This is getting hilarios....

Thirds edit: [MENTION=1670821]cybernetus[/MENTION] This is what is going on in my case: plugged the phone and began logging via adb - all OK. No SoD. Removed the phone from the USB Cable, screen goes off directly into SoD. :( I will attach the log created until I unplugged it. If there is anything more I can do please tell me. I really want to help resolving this issue so others won't run into it. Thank you.
[Galaxy S II Android Development] bronxitas:
SOD SOD SOD with the 38 mv3. Everytime screen turns off, can't turn on again. Tryed reset profiles, wipe cache/dalvik. Didn't help. Back to 37.1 till next ver. Cm10.2

Sent from my ragelis
[Galaxy S II Android Development] cybernetus:
Logs ?

---------- Post added at 08:20 PM ---------- Previous post was at 08:19 PM ----------

Sod Here too, but I'm outside home :(
[Galaxy S II Android Development] bronxitas:
Nope. Just my 2 cents.

Sent from my ragelis
[Galaxy S II Android Development] m1trand1r:
v38 is broken ...I think.....:(

Beam-ed through your pineal gland via//Android 4.3.1:p//
[Galaxy S II Android Development] dorimanx:
hmm, no sods here. i will build and post for all.

Sent from my GT-I9100
[Galaxy S II Android Development] gippy2:
deleted as dori has answered
[Galaxy S II Android Development] dorimanx:
Uploaded V39 all branches to MY BETA storage.

Kernel > https://github.com/dorimanx/Doriman...mmit/c879878765f4b99ce1717135f5da98f828f62b8d

Initramfs > https://github.com/dorimanx/initramfs3/commit/3d80d69206aecb2cdca6835a9f10d00fdecc5385

Please test.

on Maliv3 branch and latest Slim ROM all OK, no sods or any thing else.

All do STweaks Profile RESET from recovery, just in case.

My understanding of a BETA TESTER = Pure STABLE ROM + Gapps + My Kernel + any APPS - ANY SCRIPTS, MODS, JUNK VOODOO MODY CRAP! = STABILITY + GOOD BETA TESTER

I also use the xposed fremework with some mods, so this is OK i guess, i dont have any SODS for mounts.

If you are not in that category, please leave.
[Galaxy S II Android Development] dorimanx:
that means you dont understand the code.

so dont ask.

is it really crossed your mind that i will remove deep sleep and battery will be drained in 4 hours?

NO.
[Galaxy S II Android Development] dorimanx:
not working on it for now.

I am personally using HYPER/ondemand and happy with stable device.

all the rest considered unstable as i dont test them.

read reports from others that do.

and NO i will not change the freq step range. WHO??? told you that this can be more stable?

= Bull Sh#t.
[Galaxy S II Android Development] Misk77:
9.34v38

Sod here too.

didnt notice any problems before i unplugged the charger then after 10 minutes i didnt wake up and cant take logs :/

"error: device not found"

saw new v39 will flash it now.
[Galaxy S II Android Development] dorimanx:
that can be glich in build, some GCC bug.

I have cleaned all temp files with "sh clean_kernel.sh" (for builders)

and loaded config and compiled.

all ok here. so should be for others too.
[Galaxy S II Android Development] Alex-stroev:
Can't flash 9.43 v39 mv3. status 6
[Galaxy S II Android Development] cybernetus:
Same here too.
[Galaxy S II Android Development] gippy2:
Ok same here so I would imagine 3 posters is enough ..Sorry if you didnt need my confirming also v39 no go..
[Galaxy S II Android Development] m1trand1r:
me too....lol...;)

Beam-ed through your pineal gland via//Android 4.3.1:p//
[Galaxy S II Android Development] Misk77:
+1

i cant get adb logcat even then the phone is on...hmmm?

adb dmesg - Android Debug bridge version 1.0.31 and all commands..

But i wait till i see a new beta or something to get going...

watching you...
[Galaxy S II Android Development] Alex-stroev:
All change update-script and flash zip again. take update-script form 9.43 v34

or download zip http://yadi.sk/d/6wteqfoaDw4K6
[Galaxy S II Android Development] evilgod77:
same for v39 mv2 - status 6
[Galaxy S II Android Development] Troubadour666:
Hi,

i take last from [MENTION=2376110]dorimanx[/MENTION] v8 i know, Kernel_Dorimanx-V8.43-v27-[22-30]-[21-11]-JB-SGII-PWR-CORE , replace zImage from Kernel_Dorimanx-V8.43v39-[21-34]-[07-12]-JB-SGII-PWR-CORE.zip (because error status 6 too) and flash.

DualBoot ok here.

thanks.
[Galaxy S II Android Development] dorimanx:
I will fix the install script, all will be OK soon, sorry! :)
[Galaxy S II Android Development] gippy2:
Don't worry we have enough kernels to get by on lol....:D
[Galaxy S II Android Development] cybernetus:
This on the my storage too, if anyone needs to download.
[Galaxy S II Android Development] dorimanx:
Fixed the install script. + Stweaks and Supersu install script.

All branches reuploaded. V39.
[Galaxy S II Android Development] Misk77:
Flashed the new one. :good: flashed and loaded, report i any issues :)

But i cant see my device in adb devices.....
[Galaxy S II Android Development] m1trand1r:
v39 boots fine....:good:.

Thanks;)

Beam-ed through your pineal gland via//Android 4.3.1:p//
[Galaxy S II Android Development] dorimanx:
well its ok here.

try to FC the adb service in windows, and check that phone is loaded in win.

reboot your PC best solution for microsoft.
[Galaxy S II Android Development] j1gga84:
Mainly it was a Joke, I never thought you'd removed DS although it sounds a bit like that :D

And yes I do not understand code very much, like 80% of the users here do not but I think this is not necessary unless you are a developer. So if Dori, cybernetus, computoncio and Co. understand it (and I am sure they do) I am happy and not sad that I don't ;)

Anyway no problems with 9.43v39 :)

Regards

Sent from my GT-I9100 using german Tapatalk 4
[Galaxy S II Android Development] oL00No:
So much fun when you get all wound up :) I still love you, man! And thanks for letting me know it's not a priority. I'll stick to hyper, and help log what you actually want to fix.
[Galaxy S II Android Development] metalgearhathaway:
Update, did anyone who suffered the BT stutter/audio drop notice that from slim build 2.2 based releases that the issue has be alleviated?

I notice on the changelog the note of numerous BT fixes. What I am not so clear about is whether Slim team were resolving their own BT issues or whether it was deeper set issues with base ASOP?

Eitherway, wherever the blame lies, the issue is sorted now, which means that kernels, apps and configuration were never to blame.

So happily back on slimsaber with dorimanx again :) Yipee! :)

9.43 v39 rocking along, blistering stuff :good:
[Galaxy S II Android Development] jpeg725:
For when adb logcat doesn't work, there are apps like CatLog that can almost continuously record your logcat to the sdcard. So if you only get sods when unplugged, you could leave catlog running for a few hours hoping for a sod. Keep a charger on hand though.
[Galaxy S II Android Development] simonsalo:
Dual boot between 4.2 & 4.4?

Hi. Can we or will we be able to to dual boot between PAC 2.2 milestone & alpha builds of 4.4 like Omni? It would be great to keep a stable release for daily use & still be able to play with the new stuff!
[Galaxy S II Android Development] dorimanx:
no.

if 4.4 will use maliv2.

and not soon any way, i not belive in 4.4 as stable and options rich build, so no support for it now.

till its will be usable as 4.3.1 now.

Sent from my GT-I9100
[Galaxy S II Android Development] infatality:
No issues with v39 as usual with fj slimrom, xposed, Viper4Android..

Darkness gov and bfq as awake deem to be real stable on group 2 cpu.. Sleepy and sio as sleep, no issues for quite sometimes.. Wonder when will the released will tag as stable.. :D:sly:
[Galaxy S II Android Development] 089man:
Hi dori, pound Rom kitkat 4.4 based on CM are comes with Mali v3 from begin on. Now are weekly and this rom is much more stable as the most 4.3.1 roms. Also I don't know one 4.3.1 system with released a stable version at this time... Nothing..

This only as info for you.

Since build 1115

kernel/samsung/smdk4412/

mali: bulk import of r3p2-01rel3 drivers from i9300-update12

mali: enable r3p2 build

mali: remove r3p1 drivers

I9100 Tapatalk 4, Rom1 Pound Rom 4.4 Kitkat
[Galaxy S II Android Development] fabiienb:
I think too it's not stable at all! I want u on the s4 just 4 one fing the 4G I believe in u man you are the best the s2 for me it's the best android phone actually I don't think at now a phone working better... But I wait your work on the s4 believe me...

Envoyé depuis mon GT-I9100 en utilisant Tapatalk 4
[Galaxy S II Android Development] cybernetus:
Amazing deepsleep :)

Stable and smooth on v39 :)
[Galaxy S II Android Development] SoLoR1:
That bus freq change in cortex seems to fix random reboots for me as well... before i couldnt use any other gov except hyper/ondemand (got random reboot in matter of minutes) or oc/uv cpu, now everything is back to normal like it was in v22 and before... currently using zzmanx/intelidemand with no reboots over night!
[Galaxy S II Android Development] d_Schizzo:
Haha, good to read that i had the right idea!!:laugh:;)

V39 is rockstable for me aswell. I think its time for a new stable release.:good::cool:

Regards,

Schizzo
[Galaxy S II Android Development] jgcaap:
Wasnt able to record log. But I was updating apps and simply the phone stop responding. Had to reboot. Anyone with similar issue?
[Galaxy S II Android Development] cybernetus:
Record log using logcat or using stweaks ?

When you have problems the best way is use logcat .
[Galaxy S II Android Development] SoLoR1:
Well i was talking to fast :s it was up all night (11h almost), then i unpluged it and got sod/reboot twice in 15 min... back to default cpu settings for me :> im tempted to go revert commit by commit after v22, but since i work 6days/week dont have that much time atm :< main issue is it doesnt produces any last_kmsg or something like that... sometimes it just sods and you need to hold power for 10sec, other time it just reboots by it self...
[Galaxy S II Android Development] cybernetus:
What governor ?
[Galaxy S II Android Development] umair42:
I got 3 SOD's in a row when screen was turned off on neatrom.When connected to pc to get logs,it said "device not found" or "waiting for device".

EDIT:I was using v39
[Galaxy S II Android Development] SoLoR1:
I tryed neonx and zzmanx as awake both same thing. Only hyper (from the ones that i tryed) works as it should. Also other issue is i cant OC/UV even on hyper sods and reboots all the time, only default cpu settings are working for me currently, that means hyper/ondemand govs 200-1200mhz and default cpu voltages. Before i could use zzmanx/intelidemand with 200-1400 and UV -25 on all frequencys, now as soon as i change any of this i get reboots/sods (without last_kmsg)...
[Galaxy S II Android Development] reza2388:
+1.. im too, every screen off my phone SOD.. with default setting not change anything..

Sent from my GT-I9100
[Galaxy S II Android Development] SoLoR1:
maybe its neatrom fault ? :s im using that as well... anyone else problems with neatrom and this kernel? If anyone else can try v22 on neatrom... also thing is why it worked over night for me, if you have it on charger phone doesnt go to sleep....

edit: i was checking commits, between 15th(v22) and 17th(v23) there are only commits to cortex so maybe its that... ill try old cortex script.
[Galaxy S II Android Development] umair42:
How can it be a fault of neatrom?I got sod when screen was turned off and when i unplugged my phone from charger.
[Galaxy S II Android Development] SoLoR1:
it could be some combination of kernel and rom since others are not reporting this... and currently im geting sods even on hyper... so :D lets try old cortex brain script...
[Galaxy S II Android Development] nuraniharun:
+1

Me too...When I turned off screen The phone was dead (SOD). I did everything but unfurnately.
[Galaxy S II Android Development] umair42:
Seems like there is a problem in stock version.I hope dorimanx will fix it soon :)
[Galaxy S II Android Development] jgcaap:
I know but I couldn't I am not at home. Just asked because I do think is ram related. When to many apps are running this happend to me already twice....

On speed is almost perfect. Just think there is needed a small adjustment in memory configurations. I wish I was a dev I would help test better! :)
[Galaxy S II Android Development] m1trand1r:
umm....just a brief report from my side.....9.43v39 mv3 is running fine here doing anything.....using nigr/ondemand along with bfq /bfq and VPLL on at 440mhz -1300mV....it's damn fast n' smooth....good work done [MENTION=2376110]dorimanx[/MENTION] ;)

Beam-ed through your pineal gland via//Android 4.3.1:p//
[Galaxy S II Android Development] SoLoR1:
For sammys roms sods/reboots... its not cortex :(
[Galaxy S II Android Development] xhitm3n:
V39 Working good smooth nothing bad so far.

:D
[Galaxy S II Android Development] toffiko:
8.43 v39 gave me SODs on NeatRom 5.5

Hello everyone, just quick report, 8.43v39 gave me SOD straightaway after installation when have run the system on Neatrom 5.5. the same settings govs nightmare/nightmare schedulers row/cfq. All the same setting as before on 37.1 are giving me SODs on v39. It must be something to do with yesterdays commits. CPU group 3 (4 sometimes). That is on my second S2. Will check also 9.43v39 on SlimSaber on my 1st S2 but as others report ist all good on slimsaber. Will check this. Thanks Dori for awesome job with recent releases.
[Galaxy S II Android Development] dorimanx:
so once again sammy crap cant hande new commits.

i guess end of this branch is now.

users of sammy rom, use stable 8.43 and be happy till you decide to use advanced roms.

Sent from my GT-I9100
[Galaxy S II Android Development] dorimanx:
I have reverted changes to CPU Govs that may be responsible for SODS at SAMMY branch.

and also i have seen reduced performance, but that was the point to save battery.

lets see if that help to restore stability at SAMMY branch, and restore performance,

i will give it some more chance to keep up.
[Galaxy S II Android Development] Alexander1988:
Will these changes be in 9.xx branch too ? If so Will they impact performance ?
[Galaxy S II Android Development] dorimanx:
yes, they are there already, in GIT (for now) and yes performance restored +10% as was.
[Galaxy S II Android Development] fatjoez:
thanks for the extra effort.

a lot of us here prefer sam based roms & enjoy using your kernel.
[Galaxy S II Android Development] cybernetus:
I build but i have a sod ...

I try to build again after the update of my build machine.
[Galaxy S II Android Development] dorimanx:
A lot = / 90% all the rest using 4.2.2 or 4.3.1 :)
[Galaxy S II Android Development] cybernetus:
On my storage i have a max of 4 downloads of the sammy builds ...
[Galaxy S II Android Development] jgcaap:
Agree... once I left Samsung ROM... I could not come back
[Galaxy S II Android Development] cybernetus:
New build

Maliv3 : Kernel_Dorimanx-V9.43v40-mv3-cybnt-[20-34]-[08-12]-JB-SGII-PWR-CORE.zip

Maliv2 : Kernel_Dorimanx-V9.43v40-mv2-cybnt-[20-50]-[08-12]-JB-SGII-PWR-CORE.zip

8.x : Kernel_Dorimanx-V8.43v40-cybernetus-[21-05]-[08-12]-JB-SGII-PWR-CORE.zip

Commit

Kernel : Reverted the Change the calculation of target frequency, seems UNSTABLE.

initramfs : Tune the freq_step after CPU govs stability restore. profiles will reset!

---------- Post added at 12:26 AM ---------- Previous post was at 12:09 AM ----------

Here stable after the update of my build machine ( i believe there is a problem with the gcc compiler ).
[Galaxy S II Android Development] Computoncio:
Just flashed your version [MENTION=1670821]cybernetus[/MENTION] booted fine will report if i find any issue.

Phone: Samsung Galaxy SII - GT-I9100

Kernel: Dorimanx kernel v9.43v40-mv3

1st ROM : SlimSaber Maliv3 by fusionjack build of 20131205 (Online)

2nd ROM :

MODEM: Modem+RIL - XXLS8

MODS: My RR mods, My RB mods, Partition Fix, ASUL v5.1.1 by Kroz :good: and V6 SuperCharger:p
[Galaxy S II Android Development] cybernetus:
Thanks. After the update of the machine the sods gone.

But we need another tests :)

by the way

$ grep 8.43v40 logs/ataliba.eti.br/http/access.log | wc -l

5

$ grep 9.43v40 logs/ataliba.eti.br/http/access.log| wc -l

65

:)

Error, we had more downloads for the 8.x branch :)
[Galaxy S II Android Development] cybernetus:
SOD here but i don't logcat :(

[ataliba@ platform-tools]$ ./adb logcat

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

error: device not found

[ataliba@ platform-tools]$ ./adb logcat

error: device not found

[ataliba@ platform-tools]$ ./adb shell dmesg

error: device not found

[ataliba@ platform-tools]$

here i revert back to v39

Second sod on this version ( on the first build / on the second build )
[Galaxy S II Android Development] gippy2:
I havent a log..Im sorry ..2 sod one off the charger and then straight from reboot.....v39 was fine for the time I was using it and v34 rock stable for sure..
[Galaxy S II Android Development] infatality:
Well.. V40 is no go for me.. Sod on power button press.. Wasn't able to wake up.. Did a clean with kernel script and still same issues.. And twice when I reboot, it booted to a Sod.. Sorry couldn't get logs.. As I'm working.. Hopefully someone else could help to get logs if facing same issue.. Currently reverted to v39..:(
[Galaxy S II Android Development] fatjoez:
Agreed

To be honest 4.2 support should be dropped

4.2 users are all the people who quit sammy base rom to get latest version of android

So they should live with 4.3 roms now
[Galaxy S II Android Development] Fr3d_:
Logs

I can confirm "sleep of death" for v40. Here are some logs, but I can't have last_kmsg (no such file or directory error...).

Hope it helps...