yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] Ahmed:
Looks like I found your profile here: https://www.dropbox.com/sh/2uo5znl1d0j97da/3sZNvZYXX4 -- Do you use this? I will not directly use your profile, rather I will open it in a text-editor and examine, just to be on the safe side.

But anyway you said that that files should be used with 9.43, however can I use it with 10.43 v111? I have also examined profiles with text editor, seems quite same to my custom profiles except those of GPU's.
[Galaxy S II Q&A, Help & Troubleshooting] m1trand1r:
aye....that's a bit outdated but it's nearly the same profile i'm using for ages now.....but wait.....i'll refresh my profiles storage with current profile that i'm using now.....i've been away for some time ......oh.....and just a heads-up ..... [MENTION=1228651]fusionjack[/MENTION] just released fresh new SaberKat build.....so i'm gonna flash it and later i'll post profiles i've promised.....

C'ya....and happy flashing :D

EDIT: [MENTION=5007530]Ahmed[/MENTION] my profile on storage is updated for 10.43v111[emoji106][emoji106]

Grab it....and test.....and see ya in the "other" thread[emoji12]

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Q&A, Help & Troubleshooting] Ahmed:
Thanks I got it. I wanted to tell about a problem in Dorimanx, it used to happen in version 9.43, today it happened in 10.43 too. The problem is, the touch screen doesn't work all on a sudden, otherwise everything works fine. I had to force restart my phone, then, I saw that all the STweaks settings has been reset. It happened several time whiles I was in 9.43, today it happened with 10.43 v109. Is this a BUG? Or my device specific problem?
[Galaxy S II Q&A, Help & Troubleshooting] m1trand1r:
So. ..I assume your device just froze.....and settings of Stweaks had to be reseted because your device may not handle something set In active profile....that's why reset occurs.....could you check your CPU group?...in voltages tab of Stweaks ?

To see what's up with your voltage table.....maybe my voltages are too low for your CPU chip as we have 5 groups of CPU's......

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Q&A, Help & Troubleshooting] GoJo ^^:
Still no answer after 2 more pages..! :(
[Galaxy S II Q&A, Help & Troubleshooting] Ahmed:
No, bro. I never used your profile directly, infact I opened it in a text file, examined it, and set the Stweaks manually with my hands. Most important thing is, the problem started appearing long time ago, (When I didn't even know you :D )
[Galaxy S II Q&A, Help & Troubleshooting] Ahmed:
I will attach a logcat, actually the freezing appears when I reboot the phone. Can you pass the logcat to the developer (or may see that by yourself)?
[Galaxy S II Q&A, Help & Troubleshooting] TheImpossibleEnemy:
When vpll is on and 330mhz is set as a fourth step mali status shows it as 267mhz.Is this a bug of mali status app or a bug of maliv3 branch itself and so it's really running at 267mhz(using v111 of course)?
[Galaxy S II Q&A, Help & Troubleshooting] m1trand1r:
lol...enjoy thanks....:D

.GPU works fine.....it's Malistats.apk with a BUG....not kernel bug AFAIK:)

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Q&A, Help & Troubleshooting] TheImpossibleEnemy:
Thanks man:D

I hoped it was so:angel:
[Galaxy S II Q&A, Help & Troubleshooting] bogser:
Hi,

I'm trying to make the vitalij fix for touchscreen move threshold to this kernel (I use Dorimanx 8.43 with NeatROM 6.0.1). My touch screen model is MX224E, so seems I have to zero the BATT TOUCH THRESHOLD E parameter in STweaks. But the minimum value that I can set for this parameter is 30. Is it possible to set lesser values somehow?
[Galaxy S II Q&A, Help & Troubleshooting] Ahmed:
BUG

[MENTION=3763274]rkoby13[/MENTION] , Hi there. I have figured out my problem. As I told you earlier, the touchscreen freezing appears only a after a reboot. So I started playing with STweaks settings and at last I found that the problem is in 'SlidetoWakeSwitch' :(. As your profile says, you don't use that. So I would recommend you to enable 'SlidetoWakeSwitch' and reboot your phone different times in a day :D. If you face the same problem, it's surely a bug.
[Galaxy S II Q&A, Help & Troubleshooting] m1trand1r:
I will try this right away bro.....but I think i've used S2W feature with no issues..in past though....not on latest betas....but I disabled it because it drains a lil' bit more battery (I have almost dead battery now:( )

and somehow when in-call....it interferes with my status bar brightness feature and brightness gets messed up after ended call coz of my face touching screen at that time.....but I will try what you said anyway :)

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Q&A, Help & Troubleshooting] Spaulding89:
[MENTION=5007530]Ahmed[/MENTION] i use Slide2Wake since a long time and have no issues with it.
[Galaxy S II Q&A, Help & Troubleshooting] m1trand1r:
Confirmed....all works fine here with s2w ON:D

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Q&A, Help & Troubleshooting] Ahmed:
ERROR LOG

So sad it doesn't work for me :crying: But I should mention that a log-errors.html file is generated by the kernel itself after the error appears. Here's the content of that log:

ERRORS IN PARTITIONS DETECTED

Mon May 5 16:32:43 GMT 2014

Version of binaries used:
e2fsck 1.42.8 (20-Jun-2013)
Using EXT2FS Library version 1.42.8, 20-Jun-2013
tune2fs 1.42.8 (20-Jun-2013)

Tunning partitions begins...

Device /res/dev/data already have has_journal in features.
Device /res/dev/data already have dir_index in features.
Device /res/dev/data already have journal_data_writeback in default mount options
Device /res/dev/data already have 256 Inode size

Tunning partitions ends.

Checking if device has errors...

Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (481066, counted=481116).
Fix? no

Free inodes count wrong (129843, counted=129823).
Fix? no

1229 inodes used (0.94%, out of 131072)
25 non-contiguous files (2.0%)
2 non-contiguous directories (0.2%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 1150/1
43222 blocks used (8.24%, out of 524288)
0 bad blocks
0 large files

850 regular files
300 directories
0 character device files
0 block device files
0 fifos
0 links
85 symbolic links (85 fast symbolic links)
5 sockets
------------
1240 files

DEVICE /res/dev/data NEEDS DO BE FIX

Please use Stweaks "FIX DATA ON or OFF" option in the other tab to avoid annoying issues or use "Check and repair file system on every boot" to always check and repair partitions.

It is advised to perform a nandroid or Titanium Backup similar app before fixing corrupt partitions.
Data of app and/or app may be delected if damaged too much!!!

I checked my partition, there was no error though. I also ran DATA FIX, but the problem would appear again in a random time.
[Galaxy S II Q&A, Help & Troubleshooting] m1trand1r:
Did you consider to flash v112 by [MENTION=1670821]cybernetus[/MENTION] ?;)

And in other tab check/tick fix partitions on every boot and browser message will disappear .....as per S2W feature I really don't have idea why it wouldn't work on your side.....but as I'm thinking ....maybe you could try to connect your device to PC via USB when it freezes after booting and run cmd.exe(Windows ) and then do:

adb shell(enter)

logcat(enter and copy output )

kmsg(hit enter and copy output )

paste above logs text into txt file and post here for devs to see the logs.....maybe they could see the reason why freeze occurs ;)

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Q&A, Help & Troubleshooting] Ahmed:
I enabled S2W and rebooted my phone lots of times. But magically, the problem has not re-appeared. As soon as the screen freezes, I will provide you the logs. Until then, don't forget me :D
[Galaxy S II Q&A, Help & Troubleshooting] lovegambler:
Need old Dori kernel v9.14

Hey guys where can i find old dorimanx builds for CM10.1?

Please if anyone can share would be much appreciated, I want v9.14 as my current zip got corrupt
[Galaxy S II Q&A, Help & Troubleshooting] Hopper8:
Hmm that's weird, I can't find them either (have only looked for 30 sec off my phone). But here is a link to download my 9.14 from Dropbox :)

https://www.dropbox.com/s/t54pcjnlc...-[10-49]-[16-04]-JB-CM-AOKP-SGII-PWR-CORE.zip

Sent from a galaxy far, far away
[Galaxy S II Q&A, Help & Troubleshooting] lovegambler:
Thanks a ton buddy, that was a life saver for my device :highfive::angel:
[Galaxy S II Q&A, Help & Troubleshooting] Ahmed:
Don't use 9.14 as a new version is there from a long time, it's 9.43. You can find it from here: http://www.dorimanx.shine.sk/Android-ICS/
[Galaxy S II Q&A, Help & Troubleshooting] Ratheesh143:
Hello Guys i am using Samsung galaxy s2 Resurrection Remix latest rom i had installed Dorimanx-V9.43 kernel after that my phone stuck at dorimanx logo please help me. :fingers-crossed:
[Galaxy S II Q&A, Help & Troubleshooting] sien1996:
Is it the latest versions(KitKat)? Cause those need maliv3 drivers, use the 10.xx branch,:p search around for the dori beta thread and flash the 10.43 v 112 :)
[Galaxy S II Q&A, Help & Troubleshooting] Ratheesh143:
yes i also flashed the 10.43 version also but still it stuck at dormianx logo. what to do now ?
[Galaxy S II Q&A, Help & Troubleshooting] sien1996:
Ok flash core gapps or slim minimal gapps and see if you can boot into the ROM. :good:
[Galaxy S II Q&A, Help & Troubleshooting] Ratheesh143:
can u give me the link please...
[Galaxy S II Q&A, Help & Troubleshooting] sien1996:
I personally like slim gapps,here ya go....

http://slimroms.net/index.php/downl...ons4-4/10813-slim-minimal-gapps-4-4-2-build-5

:p

And search next time please. :)
[Galaxy S II Q&A, Help & Troubleshooting] Ratheesh143:
Thanks for the Link but Still not working bro. :confused:
[Galaxy S II Q&A, Help & Troubleshooting] sien1996:
Can it boot with the stock kernel? Try booting into stock then flash dori and see if it works: D
[Galaxy S II Q&A, Help & Troubleshooting] Ratheesh143:
i am now using slim saber Rom now all is Fine thanks bro.. :laugh:
[Galaxy S II Q&A, Help & Troubleshooting] lovegambler:
9.14 was the bestest Stable and Battery friendly kernel for the ROM I used when Dori released 9.14

my combination was PACMan v23 ROM with the same kernel used to have 3+ hrs of Screen on time 9-10hrs of usage
[Galaxy S II Q&A, Help & Troubleshooting] sien1996:
Haha for me it was 9.13 and rootbox. Man hat battery life was awesome. I mean i could get 6 hours average screen on time with lots of whatsapp or Facebook messenger haha :p But it wasn't as snappy of course. :p
[Galaxy S II Q&A, Help & Troubleshooting] Ahmed:
Can you please provide a pretty good list of supported ROMS by Dorimanx Kernel, maybe in another thread :o
[Galaxy S II Q&A, Help & Troubleshooting] Hopper8:
Click the links in my signature to the ROM indexes, and have a look there. A version of Dorimanx (whether it's 8.xx, 9.xx, or 10.xx) will support the vast majority of the ROMs there. Read the OP & following posts of this thread to find out which dori version you need for your new ROM :)
[Galaxy S II Q&A, Help & Troubleshooting] Ahmed:
Can I use Dori 9.x versions in KitKat AOSP (like Carbon rom)? I somewhere heard that I can use those versions in KitKat roms. I thought that I need to match GPU version.
[Galaxy S II Q&A, Help & Troubleshooting] Hopper8:
I already answered this for you in my above post? In the OP of this thread is explained what version to use for kitkat. I don't know where you heard that you can use 9.xx for kitkat, but that's incorrect. V10.xx for kitkat.

Sent from a galaxy far, far away
[Galaxy S II Q&A, Help & Troubleshooting] Ahmed:
Sorry, I didn't notice that. I also know v 10.xx is for KitKat roms, but I thought if I could find some stable Dorimanx kernel. But actually, there isn't any Dori stable kernel for KitKat. But there will be a stable Dori 10.xx kernel in the future, won't it?
[Galaxy S II Q&A, Help & Troubleshooting] m1trand1r:
Well.....TBH nobody knows when [MENTION=2376110]dorimanx[/MENTION] will release last "STABLE FINAL" version of his masterpiece .[emoji845]....but if you wanna stick with most stable build tested by "US" (testers) you can also follow the Beta thread and read what "WE" wrote backthere about each and every version till date....but coz i'm nice guy..[emoji56].i'll tell ya a secret.....i'm not a nice guy..[emoji35]...flash 10.43v112 by [MENTION=1670821]cybernetus[/MENTION] for KK roms.....and wait.....oh.....don't forget to enjoy The Real Stability by kernel.....[emoji106][emoji106][emoji122][emoji122]

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Q&A, Help & Troubleshooting] officiallyme:
has anybody created a new default and a new battery saving profile for the new beta kernels? taking into account currently stable govs?
[Galaxy S II Q&A, Help & Troubleshooting] m1trand1r:
go to Stweaks profiles thread....I updated my profile for 10.43v112 not so long ago...

I didn't update my reserved post tho[emoji12][emoji12]

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Q&A, Help & Troubleshooting] Ahmed:
Beta versions of Dori kernel automatically installs SuperSU. But I would prefer the Superuser that's embeded in 'Settings' in my rom. I cleaned SuperSU (by using a option given there, something like 'use another superuser app'), disabled the Auto-Root settings in STweaks so that it doesn't install SuperSU every time I reboot. In this way, I finally got SuperSU removed. But everything in vain :eek: The Superuser embeded in Settings didn't work.

Is there any way I can achieve my goal?
[Galaxy S II Q&A, Help & Troubleshooting] Unobtainium:
Did you check that root is enabled under developer settings?
[Galaxy S II Q&A, Help & Troubleshooting] Hopper8:
As Unobtainium says, check that root is enabled in development options. However, the reason that SuperSU was implemented by dorimanx was that Superuser as part of the ROM was causing problems with his kernel. I can't remember what version that SuperSU has been implemented since, however I can say that there have been root related problems when using in-built Superuser with dorimanx in the past, hence the switch to SuperSU.

Sent from a galaxy far, far away
[Galaxy S II Q&A, Help & Troubleshooting] m1trand1r:
Guys....accept it....Rom Built-in Superuser just won't work on [MENTION=2376110]dorimanx[/MENTION] kernel.....so superSU is a must and it's better IMHO;)

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Q&A, Help & Troubleshooting] Ahmed:
While flashing some zips through Dori's CWM recovery, it shows a warning something like: 'E: legacy.....' (Sorry, I can't remember the whole). The zip flashes successfully but with the warning, should I ignore it?
[Galaxy S II Q&A, Help & Troubleshooting] Hopper8:
If you don't tell us what the full message is, how do we tell you to ignore it or not? Sorry but no way of knowing unless you know the message. Personally I've never seen it. What zip are you flashing anyway, a ROM/kernel, or something else?
[Galaxy S II Q&A, Help & Troubleshooting] m1trand1r:
ignore it[emoji33][emoji12]....zip was flashed successfully ...I don't see a problem ...you?...;)

That's why I didn't make a move (I didn't post reply) ;)....I've seen many such posts....--> ignore list [emoji2][emoji122][emoji2][emoji122][emoji482][emoji23][emoji23][emoji23]

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Q&A, Help & Troubleshooting] Ahmed:
For example, if you try to flash v112 kernel, using the cwm of v109 kernel it would show you the warning. You can also try to flash some of the custom SlimSaber bootanimations and see that warning. I have to say that, it doesn't cause any further problem. I just want to be sure :)

---------- Post added at 03:14 PM ---------- Previous post was at 03:12 PM ----------

Me too, ignoring it didn't cause any problem. I just wanted to be sure. I think this warning apperas only when you try to flash some old-type zips with the modern Dori CWM recovery, Dori CWM recovery is too modern for those zips :P And only the Dori CWMs' show this warning message but not the general CWM recoveries :D
[Galaxy S II Q&A, Help & Troubleshooting] 2mecky:
Issue with installing roms and dorimanx

I have a rooted SG2 GTi9100. From several flashes ago I have struck a peculiar problem with the phone in that I can flash any rom I like, currently Carbon but several others before that. The problem is though unless I also flash the latest dorimanx kernel v10 mali v3 (and no other) with it, it just gets stuck in bootloop when restarting the system. Yes I've clean flashed every time and even reverted back to the original stock samsung rom through Odin. Same result, stuck in bootloop. Gave in and flashed Dorimanx again with a custom rom to get the phone going. However that's only half the problem. If I power the phone off overnight or reboot from recovery for whatever reason I have to go through the whole set-up procedure each time, select region, reconnect to wi-fi, re-register my google account and then start from scratch again with apps etc. I don't believe it's a rom issue but can't for the life of me work it out. Any ideas other than wipe data/cache dalvik and format system would be greatly appreciated. ﻿
[Galaxy S II Q&A, Help & Troubleshooting] Hopper8:
Yep that's a weird one... I've never seen anything like that to be honest.

First thing to try, is RomNuke script by hawkerpaul (you can easily find it for S2 on xda). That wipes more than system/data/cache, it's all the hidden files and folders left over from multiple ROM/kernel flashes. Then flash your custom ROM immediately after the nuke script and see if it boots without Dorimanx.

If that doesn't work, what I'd do is to flash a 3-part stock firmware, which wipes your phone as it flashes. It's a clean slate. A 3 part firmware is linked in my signature (it's inside the Odin troubleshooting link). Download that and flash as per instructions in the link. I hope that will boot without Dorimanx.

If it does boot without Dorimanx, I'd leave my phone running stock for a day or two and see if all is good. If it is, then root and flash a custom kernel but not a custom ROM. If that's all good, then flash a custom ROM without kernel and then see. If none of that works, then I'm afraid I have no idea.
[Galaxy S II Q&A, Help & Troubleshooting] 2mecky:
I've done the RomNuke thing without any success so I'll give the 3 part stock firmware a go.......cheers
[Galaxy S II Q&A, Help & Troubleshooting] 2mecky:
Tried the 3 part firmware, followed instructions to the letter but phone stuck at samsung boot animation (looping).......
[Galaxy S II Q&A, Help & Troubleshooting] Hopper8:
And by flashing Dorimanx, you can get past the bootloop?

If so, I honestly have no idea then. Maybe someone else has an idea...?
[Galaxy S II Q&A, Help & Troubleshooting] m1trand1r:
Hmmmm......really.......weird......have you tried wiping internal sdcard and remove extsdcard prior booting ?

Beam-ed through your pineal gland via//Android 4.4.3.:p//
[Galaxy S II Q&A, Help & Troubleshooting] 2mecky:
Yeah the only way to get past the bootloop is to flash dorimanx...............??
[Galaxy S II Q&A, Help & Troubleshooting] Merlin35:
What have I done wrong

Running Omega AOKP V13 using Kernel_Dorimanx-V9.43v98.1-[10-30]-[16-03]-JB-SGII-PWR-CORE. with no problems, tried to upgrade to V10.43v100-[16-51]-[01-04]-JB-SGII-PWR-CORE phone will only show startup screen then shut down. Reflash with V9.43 and phone works fine, help what have I done wrong
[Galaxy S II Q&A, Help & Troubleshooting] m1trand1r:
well...apparently you didn't read as expected by rules here....[emoji12]

And it looks like you can only use 9.xx branch for rom you're using due to Mali video drivers.....so....to sum up....9.xx branch is using Mali v2 whereas 10.xx branch is for Mali v3 video drivers only.....hence you got black screen after dorimanx logo....your rom is using Mali v2 drivers so...you need to upgrade your rom to one that has Maliv3 drivers in order to use 10.xx branch.....and afaik all 4.3.1 roms do have maliv3 built-in as some 4.2.x roms do have maliv3 and some have old maliv2 drivers....but you need to ask this in your rom.thread....

Did I make myself clear?....I hope so;)

Beam-ed through your pineal gland via//Android 4.4.3.:p//
[Galaxy S II Q&A, Help & Troubleshooting] :
Cheers for the answer
[Galaxy S II Q&A, Help & Troubleshooting] shiboby:
[MENTION=272791]rko[/MENTION]by

So is there anything special I need to do to add 4.3.1 as a second ROM?
[Galaxy S II Q&A, Help & Troubleshooting] Hopper8:
Just so he will see your question... [MENTION=3763274]rkoby13[/MENTION] look at the post above mine. I think you replied to this member in the SlimSaber thread about dual boot :) (I don't dual boot so won't answer your question :p )

Sent from a galaxy far, far away
[Galaxy S II Q&A, Help & Troubleshooting] m1trand1r:
Guys......i'm pretty busy lately....so I'll reply a bit later .....sorry [emoji56]

Beam-ed through your pineal gland via//Android 4.4.3.:p//
[Galaxy S II Q&A, Help & Troubleshooting] TheImpossibleEnemy:
Does 8.x branch's v113 still has this "apk parsing error"?
[Galaxy S II Q&A, Help & Troubleshooting] cybernetus:
You need to test

Or anyone using this branch will talk to you about this
[Galaxy S II Q&A, Help & Troubleshooting] TheImpossibleEnemy:
Just did.Still there.
[Galaxy S II Q&A, Help & Troubleshooting] cybernetus:
i will update the 10.x and 9.x branche i believe, but i don't have plans to 8.x
[Galaxy S II Q&A, Help & Troubleshooting] a violinist:
Just to report it for those who want to do this on their own risk: I dirty flashed slimsaber 4.3.1 reborn/v.112 on latest 4.3.1 2013/v.112 and it is running fine and without issues since 23 hours. But dont forget backup, and be aware of possible problems, as it is not recommended to try this.

(I know that this is the wrong thread, but I cant post in development threads, as I have made less than 10 posts so far).

Thanks to [MENTION=1670821]cybernetus[/MENTION] and to all the others for coming kernel updates, and to all who keep our phone alive.
[Galaxy S II Q&A, Help & Troubleshooting] dmagician:
Getting init.d script after setting preferred options in stweaks

Hello.

I'm having a problem with DorimanX kernel (since long ago - never found a solution for it...)

Every once in a while, but almost everyday, the device gets stuck, becomes hot and after a while -- When I'm noticing it -- I'm rebooting the it, where as after the boot completes,

for some unknown reason

, the settings I've done in STweaks are getting lost (and I mean

each and every

one of them...

Even those setting pushed to GOV CORE via the button in "CPU-TUNING (AWAKE)"

which are, as probably guessed, the ones related to over clocking settings.

Is there any way of generating a init.d script AFTER presetting whatever wanted in STweaks which will set anything set under STweaks?

The scenario is as:

Setting whatever preferences as I like.

Using the device (I'm not using it too much over day time)...

At some point over the day, device gets stuck and pretty hot (not extremely hot BUT hot), the storage -- either internal nor external -- becomes unavailable [tested via file explorer of any kind - preffered is X-Plore by lcg]

Booting the device...

...Boot completes.

All settings are gone

!
[Galaxy S II Q&A, Help & Troubleshooting] Biftor:
Hi all

I was out from great dorimanx works,

Now i need to know i want use dorimanx kernel on my slimkat 4.4.4

Is that possible? If yes which version??and where can i download

Thanks

Goodluck

Armin.
[Galaxy S II Q&A, Help & Troubleshooting] Spaulding89:
Read this

http://xdaforums.com/showthread.php?t=2415759

[KERNEL][UNOFFICIAL BUILDS][JB/KK][Vx.43v76]DorimanX Test builds

There is all u need to know