yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] m1trand1r:
Now before I snap and call you names[emoji35].....go into in-depth reading of OP of this very thread.., and apparently builders "could potentially change" 10.xx branch kernel package as JB/KK(only).zip

but that's not really necessary because on Servers by uploaders/builders you can clearly see what you can flash for KK....only thing is what ya need to know is which mali video drivers version your rom is coming packed with....and that's not the topic imo..,

So to sum up in short.......You should go reading and do your homework before asking F.A.Q(freaking annoying questions) repeated countless times.....over and over and ......over again.....

Now please.....for your own safety....leave this thread....until you will start reading why/where you are....that will help you to understand what you should flash....oh....and you should read 20-30 pages back....to see what's up with later versions....

TBH....you really shouldn't flash this kernel before you understand which one to flash....

Very Good Luck;)

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] TheImpossibleEnemy:
hmm..

if the same kernel works for me why it shouldn't work for others?
[Galaxy S II Android Development] m1trand1r:
because not everyone has the same setup as you or me....that's why....and it happened in past..,

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] jgcaap:
After long time, Computoncio version kernel is working rock stable. Still testing... :) thank you for your help
[Galaxy S II Android Development] jgcaap:
Computoncio I don't know what you changed but I already rebooted like 10 times and am testing the kernel with the same configuration I had before. No sods, no bootloop. Rock stable. Thank you for the fs version. Thanks dorimanx and team for the great development. It's working great. For a very long time I couldn't use this kernel because it wasn't stable, and now seems to be again on the right track. I am happier :D
[Galaxy S II Android Development] Shillopellos9:
http://www.phoronix.com/scan.php?page=news_item&px=MTY1NDE

does this affect our device?
[Galaxy S II Android Development] m1trand1r:
Hey..,you on 10.xx branch, right?

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] jgcaap:
Yes :)
[Galaxy S II Android Development] m1trand1r:
Then...I agree....[emoji481][emoji482][emoji106][emoji122]

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] Twiq:
I think yes, i spotted a couple of exynos4210 stuff in the pull request
[Galaxy S II Android Development] m1trand1r:
hmmmm ... [MENTION=4663860]Computoncio[/MENTION] is lurking around.....so....FS8 will be up soon?:D

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] CheekyLord:
please, someone could explain why I have access via CWM to my 64GB/exFAT EXTERN sdcard but Not after the system started n running..??

i use atm Computoncio's v8.43FS7 but had that with 10FS7 too.

---

always... via cwm everything is fine... via running System "damaged sdcard" reported.

idea's what could be the reason for that..?

SentFrom NeatROM
[Galaxy S II Android Development] m1trand1r:
Reason is that you're NOT following FS releases properly......for now you can only wait for FS8 if [MENTION=4663860]Computoncio[/MENTION] will be able to fix that bug.....and/or you can format your extsdcard to fat32 as it was and it'll work.....exFAT is still broken somewhere and [MENTION=4663860]Computoncio[/MENTION] & Co. are looking for a solution.....that's why it probably works in cwm but not when system boots.........other than this.....FS7 is kinda beast again....like in good ol' times:D

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] CheekyLord:
thx for clearing up.. :)

please, check pm

---

SentFrom NeatROM
[Galaxy S II Android Development] m1trand1r:
Checked and replied:)

No more PM heads-up please..,..unless if it's really PARANOIA [emoji23][emoji23][emoji23][emoji23]

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] glhfggnore:
reboots

Hello.

When I heavy use my notepad app or listen to music or use whatsapp, when I press home button it reboots.

Latest FS by [MENTION=4663860]Computoncio[/MENTION].

This bug is present at v 99, v 100, FS 4 and FS7.

Please, help!!!
[Galaxy S II Android Development] m1trand1r:
Huh.....well that's happening to me.......but....I don't know since when....and I can't reproduce it....it's bloody random....and NOT only on dorimanx kernel.....maybe it has to do something with Xposed on my side,...but i'm still not sure....although I have an idea....but not tested yet.....so... no help for now.....maybe it's just kitkat issue....as Google is trying to fix just that in 4.4.3 release....I've read this today.....and it's not kernel thing IMO.....so....we wait for 4.4.3 if we will get it by out devs who stick with S-2 development ;)

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] glhfggnore:
But in Gustavo kernel I can't reproduce this bug.

On dori it reproduces and,it is random.

I really really dear dori kernel will fix it, because it is so sweet fast awesome. But since music player bug and after exFAT music player fix was found, unfortunately now with this bug disturbs sweetness of dorimanx kernel!

I have thought now, well, 4.4.2 is out already for a while time, and we've not encountered this bug earlier. But with tha exFAT music player fix, I wonder that with a new bug approach which is random, isn't it fuse related thing? Because earlier we didn't change fs to exfat or ext4, now we change it and woilah bug appears.
[Galaxy S II Android Development] Computoncio:
[MENTION=5074262]StanTRC[/MENTION] and [MENTION=2376110]dorimanx[/MENTION]

I found why exfat doesn't works when installing zip from sdcard0, the cause is in sbin/recovery-loader

because of this mount's:

this is for installing, wiping and installing zips to 2nd rom

$BB mount -t vfat /dev/block/mmcblk0p11 /mnt/.secondrom

this is for fixing .android_secure backup and restore

$BB mount -t vfat /dev/block/mmcblk0p11 /emmc-tmp;
$BB mount -t auto /dev/block/mmcblk1p1 /storage/sdcard1;
$BB mount --bind /emmc-tmp/.android_secure /storage/sdcard1/.android_secure;

with vfat we can format and install zip, but with exfat we can't because sdcard0 is mounted in /mnt/.secondrom and doesn't umount like when it's vfat :(

If i change vfat to auto and comment the mounts above, i can format and install zips but secondrom install is broken because sdcard0 isn't mounted on /mnt/.secondrom.

I tested with dorimanx version v99 without my changes and with exfat secondrom is also broken, same issue, /mnt/.secondrom doesn't get mounted.

Resuming the only think that is stopping my commit is this issue, and i think only [MENTION=5074262]StanTRC[/MENTION] is the one that can resolve it :angel:.

I have rollback my commit and replaced it with the lastest changes i did.

Maybe [MENTION=5074262]StanTRC[/MENTION] could see if he can incorporate it on recovery, if you could umount "/mnt/.secondrom" before formating and mount it after or when we use the dual boot menu it will be great, and can you check if the .android/.secure fix is needed or not? maybe you have fixed it already ;)

[MENTION=5074262]StanTRC[/MENTION] if you want to make private tests or more info just pm me ;)

I notice also that recovery is not formatting in ntfs ext2 and ext3, and do we need this !?!? If not remove it from recovery.

EDIT: [MENTION=2376110]dorimanx[/MENTION] sorry for the trouble but you will have to revert or "git reset --hard adc25746a77234b17df54f91b74411b923bb63ba" my commit, and wait till we fix the issue, i will let you know.

I'm uploading FS.8 to here, it's safe to use if you have vfat (default) filesystem in internal sdcard, if you use exfat use v99 from dorimanx or you will not be able to flash zips.

Changes from FS.7 to FS.8 are only one, fixed 2nd rom tuning and checking.
[Galaxy S II Android Development] changlung:
[MENTION=4663860]Computoncio[/MENTION], thanks for the good work.

with FS8 the ext4 sdcard1 still not mount, this problem also related to recovery issue ?
[Galaxy S II Android Development] Computoncio:
Yes it is, the only way i found to fix the mouts of exfat and ext4 is disabling the mounts in the post above, but it will disable 2nd rom creation and flashing.

Phone: Samsung Galaxy SII - GT-I9100

Kernel: Dorimanx kernel v10.43v101-mv3

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

2nd ROM :

MODEM: UHMS1

MODS: Partition Fix, Hue Blue v4.4 by Kroz :good:
[Galaxy S II Android Development] stoneh:
ROM:[ROM][4.4.2][13/03/14][i9100][1.3.2] AOSB Project

With FS6 or v102，i found a strange issue like this：when use app：“SD Maid Pro 3.0.2.8”，check “SystemCleaner” ....after moment，scaning will freeze.

then i flash Gustavo_s‘ kernel，the “systemcleaner” scaning can be done. Anyone else？

another way，zzmanx seemed not as stable as past.
[Galaxy S II Android Development] Twiq:
Weird, i never get freezes when doing system cleaner on SD Maid, what sometimes stuck on my end is sqlite vacuum for big databases on my sdcard. Rarely tho, not always.

But i don't think that's kernel issue, especially when kitkat builds is known for it's existing sdcard fuse daemon bugs..?

Running 0401 Sabered SlimKat | DorimanX 10.43v99.1
[Galaxy S II Android Development] JulianXhokaxhiu:
Thanks for the hard debugging :) In fact I'm not using at all the second rom feature, that's why I've never noticed that.

Of course you can flash zips but only from PC using the sideload feature. But hey, it's not a problem for me, just doing some bug detection here and there :D

Btw, I'm sorry to say that but I think I'm going to leave the GS2 scene since I'm moving to Nexus 5. It's just a matter of days until it will come.

Of course I'll continue to follow you but I think I will not be able anymore to test the Kernel.

I've learned a lot from you. I'll miss you guys for sure. Thanks for everything you've done until today for this device :)
[Galaxy S II Android Development] m1trand1r:
Hmmmm.....i've just got hammered by an SoD on FS7 for the very first time....:eek:Sorry....no logs avaliable as I was away from comp....:(

Flashing v99 or 99.1 in few secs.....

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] MEMOREX2:
Testing fs8 with vfat sdcard:thumbup:
[Galaxy S II Android Development] nuraniharun:
8.43vfs8 working very stable with 1400 mhz and cpu alucard hotplug.(darkness awake and nightmare sleep, row io in dualboot)

But it gives partition error in browser at every boot.

When I tested with 8.43fs4 this bug not appear.

I tried partition fix and log here.
[Galaxy S II Android Development] toffiko:
Mate FS8 is fixed for this problem. in FS7 my /system partition was showing up as broken, all the othere were ok, but in FS8 all is back to normal, my partitions were not broken as I have newly flashed 2 roms in dualboot conf. So my conclusion is that if in FS8 youre still monited about partition errors its probably true. Try do backups with titanium and flash new rom, recover all apps and yourer done. Good luck.
[Galaxy S II Android Development] Rachid.Ala:
Why not v101 by [MENTION=1670821]cybernetus[/MENTION] ? Have you ever tried it ?

It's working good on my side. I had some hot reboots tho but it was rare
[Galaxy S II Android Development] Computoncio:
You had corrupt partitions, you can see it in the log. It should be fixed now, you can use my script or use FIX DATA ON or OFF in stweaks it does the same as my script.

Good to know that in FS8 partitions check and tuning are working ok.

Stantrc have pm me and he will fix the bug, as always no eta ;)

Phone: Samsung Galaxy SII - GT-I9100

Kernel: Dorimanx kernel v10.43v101-mv3

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

2nd ROM :

MODEM: UHMS1

MODS: Partition Fix, Hue Blue v4.4 by Kroz :good:

---------- Post added at 11:05 PM ---------- Previous post was at 11:00 PM ----------

My changes don't cause SODS :P

Maybe it's that time of the month for your "female" phone :P

Thanks for your help testing the kernel, and have fun with your Nexus 5. [emoji106]

Phone: Samsung Galaxy SII - GT-I9100

Kernel: Dorimanx kernel v10.43v101-mv3

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

2nd ROM :

MODEM: UHMS1

MODS: Partition Fix, Hue Blue v4.4 by Kroz :good:
[Galaxy S II Android Development] j1gga84:
[MENTION=4663860]Computoncio[/MENTION]

Thanks for your work on Dorimanx kernel. :good:

After Dori passes his S2 everything is a bit messed up but I think there will be a final release some day ;)

For me, it is not clear what the most up to date beta version is :D

Is it V102 or the FS8 ?

Can I also use FS8 when my sdcard's are not mounted with exfat?

Anyway, I just saw some new commits:

https://github.com/dorimanx/dorimanx-SG2-I9100-Kernel

Regards
[Galaxy S II Android Development] pSyCh¤_O_O:
L.M.A.O

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

Good morning boys & girls

FS.8 working good here on Spirit
[Galaxy S II Android Development] Troubadour666:
Hi,

coming from 8.43v101 , since 6 hours installed i can say 8.43vFS8 is runin fine my dualboot PHD 4.1.2 / SaberPac 4.4.2 (maliv2) the two toms from [MENTION=4343817]phenomarc[/MENTION].

thanks.
[Galaxy S II Android Development] Computoncio:
Uploading v104 with the latest commits from dorimanx.

This kernel is only for users that use fat/vfat partition type in internal sdcard, StanTRC is working to fix the issue with exfat.

Kernel_Dorimanx-V8.43v104-Comp-[15-33]-[08-04]-JB-SGII-PWR-CORE.zip MD5: b35fc4f173f8760def384831c1d988a5

Kernel_Dorimanx-V9.43v104-Comp-mv2-[15-11]-[08-04]-JB-SGII-PWR-CORE.zip MD5: 20e660cc1ff4a509020973959b087544

Kernel_Dorimanx-V10.43v104-Comp-mv3-[14-50]-[08-04]-JB-SGII-PWR-CORE.zip MD5: ebfbc4a1e4047873f916d0025134f77b

Commits:

Kernel V8: Merge branch 'irq-core-for-linus' of git://git.kernel.org/pub/scm/linux/...

Kernel V9-mv2: Merge branch 'irq-core-for-linus' of git://git.kernel.org/pub/scm/linux/...

Kernel V10-mv3: Merge branch 'irq-core-for-linus' of git://git.kernel.org/pub/scm/linux/...

initramfs: Reworked partition check and tuning
[Galaxy S II Android Development] Troubadour666:
Hi,

I switch from FS8 to 8.43v104 , and no problemo booting the dualboot i have.

with FS8, i dirty flashed a 4.4.2 rom over 4.4.2 2nd rom, i wanted to try Beanstalk last, so I made aroma to flash it with FS8, no trouble, aroma works.

OT

i have one reflexion anw, maybe i found a little solution against "error status 7" during flash. With aroma flasher i never encountered 'error status 7' during flash.

example :

i take "pureperformance stock cwm" and try it with 101 or FS8 recovery kernel, on 2nd rom 4.1.2 and i have error status 7 during flash.

i take a little aroma script i usualy use, and i only added updater-script from original pureperformance cwm, and when i flash this little aroma, i havent any error status 7.

i dont care about choice in my aroma , there is no choice in it, it just serve to flash the purperformance script. all commands launched in all script from pureperformance scripts have worked . Maybe META-INF from AROMA is better against error status 7 (against "some permissions have changed" message or something like that)

END OT

now 104 seems to be cool and very reactive. and No SOD :)

thanks again to [MENTION=4663860]Computoncio[/MENTION] , [MENTION=5074262]StanTRC[/MENTION] and [MENTION=2376110]dorimanx[/MENTION]
[Galaxy S II Android Development] Rachid.Ala:
10.43v104 by [MENTION=4663860]Computoncio[/MENTION] booted fine on latest slimSaber by [MENTION=1228651]fusionjack[/MENTION]:good:
[Galaxy S II Android Development] TheImpossibleEnemy:
v104 all good here on my setup.Never had any browser popups so it seems my partitions are all good.

O.T.

Did anyone noticed that the check "partition status" button in stweaks doesn't work anymore?Message only shows the partitions names.

Anyway,you DEVS are awesome!

Thanks!!
[Galaxy S II Android Development] Computoncio:
I have debug that status 7 error in recovery when flashing zip's, on my side it happens when in the updater-script have set_perm of an nonexistence file.

Maybe [MENTION=5074262]StanTRC[/MENTION] could look at that too, if he finds time :angel:

And for the exfat lovers ;) uploading ve04 with the latest commits from dorimanx and without my commit in initramfs, don't forget that 2nd rom is broken when using exfat, but you can use this kernel if you are using exfat.

Kernel_Dorimanx-V8.43ve04-Comp-[17-00]-[08-04]-JB-SGII-PWR-CORE.zip MD5: 4a8496f4ffe2f1d923664a28c2d1794e

Kernel_Dorimanx-V9.43ve04-Comp-mv2-[16-38]-[08-04]-JB-SGII-PWR-CORE.zip MD5: 4a5f8ee3f2fe8fb150bbd1116eba864f

Kernel_Dorimanx-V10.43ve04-Comp-mv3-[16-16]-[08-04]-JB-SGII-PWR-CORE.zip MD5: cbdf0eb3217133124ba7e7a5574bf808

Commits:

Kernel V8: Merge branch 'irq-core-for-linus' of git://git.kernel.org/pub/scm/linux/...

Kernel V9-mv2: Merge branch 'irq-core-for-linus' of git://git.kernel.org/pub/scm/linux/...

Kernel V10-mv3: Merge branch 'irq-core-for-linus' of git://git.kernel.org/pub/scm/linux/...

initramfs: Fix permissions on su in root install scripts

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

hummm i will look at it, thanks for reporting.
[Galaxy S II Android Development] mosespl:
Any chance for synapse support?:)

Lates build runs gr8 on pound rom. No sods or lagzz.

Wysłane z mojego GT-I9100 przy użyciu Tapatalka
[Galaxy S II Android Development] pSyCh¤_O_O:
And change something for something that does exactly the same as the other?

No real use apart from live CPU info.
[Galaxy S II Android Development] Spaulding89:
We dont need synapse. STweaks is great enough. Changes for Synapse are unstable in my eyes
[Galaxy S II Android Development] reamer1992:
I wonder is it bug or its normal that when i flash set it up and then reboot and flash the kerner is diffrent from when i flash the rom then the kernel. For exsemple ive notice when i flash a rom set it up and flash the kernel it apply volteges 25mv bigger from step 6

"Flash rom set up, flash kernel" "Flash rom and flash kernel"

100mhz - 950 same

200mhz - 950 same

300mhz - 975 same

400mhz - 975 same

500mhz - 975 same

600mhz - 1000 same

700mhz - 1000 1025

800mhz - 1050 1075

900mhz - 1100 1125

1000mhz - 1150 1175

1100mhz - 1200 1225

1200mhz - 1250 1275

1300mhz - 1275 1300

1400mhz - 1300 1325

1500mhz - 1350 1375

1600mhz - 1400 1425

I think you get my point. Its strange and i dont know but maybe sometimes it couses more sods with +25mv than when i flash kernel after settingup the rom. :) . Ive found also that in sleep CPU tweaking tab its pressents a zzmanx tweking options but the governor its not presented as a choise for a sleep governor.
[Galaxy S II Android Development] pSyCh¤_O_O:
Interesting if thats the case...will test asap...

Regarding zmanx:

It was removed from sleep tab because it was unstable.
[Galaxy S II Android Development] AlexVat:
Hi, guys! Sorry for the Off-topic and I hope I won't upset anyone with the following lines.

Until yesterday I was the proud owner of a SGS2 with an older Class2 CPU, after switching from an SGS.

But the time has come to say goodbye and move to a newer phone as I got a SGS3 for the same price I got for my phone, so it was a too good to refuse deal.

THANK YOU SO MUCH [MENTION=2376110]dorimanx[/MENTION], [MENTION=1670821]cybernetus[/MENTION], [MENTION=4663860]Computoncio[/MENTION] and all the others on this thread for your HARD WORK and for making me feel like home everyday! Along with FJ's SlimBean you brought me so much joy and a whole new life for my SGS2. I'm already missing my beloved SGS2:crying: but as I said, I believe it's time to move on. I know I haven't left too much posts on this thread, but I read it everyday and I'm still doing it :D I just can't leave this beautiful-beautiful thread full of wonderful people, a REAL COMMUNITY! :highfive:

The dev thread of the SGS3 doesn't seem so alive as the one of the SGS2, but I am only beginning to dig deeper into it :D

I will also leave a best-wish thought on fusionjack's slimbean/slimkat thread:D

So once again thank you all and I hope one day we will get together on the thread of a new beast, just like our SGS2 was and IS !!!:D

Cheers everyone!

EDIT: I forgot to change my signature :D
[Galaxy S II Android Development] m1trand1r:
Hm....really interesting.....i'll look on my side as well.....

Thanks for finding this.....[emoji106][emoji122][emoji122]

hopefully [MENTION=2376110]dorimanx[/MENTION] will update zzmanx one day....in his free time.....:fingers-crossed:

and mate.....could +25 mV on frequencies above 1Ghz kill my device in a shutdown way aka sort of safe mode like on PC to protect CPU chip to not get burned [emoji845][emoji845]

I need to look at my voltage table asap....and test this out....

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] pSyCh¤_O_O:
Yes there is a safe mode.

Afaik it returns to stock setting so you can check if the problem occured is because of a bad app so you can uninstall it without doing a factory reset.

I guess playing with voltages could trigger safe mode but i have no idea.

Ive not seen it very often but when it happend in the past a reboot would take it back to normal.
[Galaxy S II Android Development] m1trand1r:
Hm....i've had same voltages on group 3 like member above.....I wonder which group is he in?.....and lowered all from 700mhz and up for -25mV but my battery is obviously too weak to run Meteo Earth app to see a full week weather cycle.....device shuts down on half....like.2 days can pass....then device is powered off....LOL.....I guess I have no other option than buying new battery pack....OR my GPU/CPU Is really heavily damaged and.........who knows what's next..[emoji29][emoji29][emoji43][emoji44][emoji43][emoji44][emoji58]

Beam-ed through your pineal gland via//Android 4.4.2.:p//
[Galaxy S II Android Development] mosespl:
I checked this and mu cpu group is 3 and my voltages are tha same as this member. I installed v104 comp today before using kernel wipe script. All settings are default i check what will be after reset stweaks profile. But for a whole day i didnt notice any sods or freezzes

Wrong following sorry i want to follow another post.

Wysłane z mojego GT-I9100 przy użyciu Tapatalka
[Galaxy S II Android Development] reamer1992:
Well im not lazy and every time when installing update to rom or kernel i use gsromnuke and then formatting system data preload and cache . so it would not couse problem app or so it appears that it happens when i flash the kernel imidiatly after the rom. And ive notice kernel couses sods but if i install it after setup its pretty stable. Also the voltige is sticking after reboots on my side.

Ps: ive notice that the romnuke script is unmounting my sd cards and unless i reboot recovery im unable to reach internal sd card to install my stuff. Also this voltages +25 is presetted in the battery and extreme battery profiles. You can go and see them.