yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] guerouig:
you'vr answered my question too, thanks
[Galaxy S III Original Android Development] davtse:
To be clear, it doesnt support samsung 4.2.1. It does, however support AOSP/CM10.1 4.22. One of the kernel developers mentioned that unless samsung releases it's source, it's way too much trouble to have to reverse engineer the leak to create a custom kernel.
[Galaxy S III Original Android Development] EJ98:
Sorry mate, I really am not experienced. My bad for not reading the changelog

Sent from Lightning Fast SIII using PARANOID ANDROID!
[Galaxy S III Original Android Development] last-home:
Hi...

Can i install siyah v1.9.1 on FoxHound 2.0 (zip file for cwm)?
[Galaxy S III Original Android Development] guerouig:
well thanks! and it is also made clear by a previous post from anthrax; although the thread mentions support for JB. So If I were to revert to XXEMC2 which is sammy jb 4.1.2, it'll be supported by Siyah; is that correct?
[Galaxy S III Original Android Development] xanthrax:
correct ! it will work with siyah !
[Galaxy S III Original Android Development] davtse:
^ what he said. 4.1.2 samsung base and cm10.1 base supported. CM10/9/ICS support dropped.
[Galaxy S III Original Android Development] Stephen88:
yes, foxhound it's based on sammy rom

pay attention the next time, zip cwm file is better
[Galaxy S III Original Android Development] Seicer:
Ok, I must admit this is the best kernel I've ever tested. I can control oc with setcpu, incredible audio (mixed with acid audio the result is orgasmical), incredible options, etc. It has everything!!! :)

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] Sigray:
Yeah but need to update to Sammy 10 ;)
[Galaxy S III Original Android Development] grzesdroid:
I have a question. revovery siyah have any problems with vrtheme? and the second question, I can install two ROMs Samsung?

SGS III / Grisza Monster Beam v7.0 / Boeffla 2.10 beta 2 / JKay deluxe framework 14.93.1 / JB Domination (edit by me) / Tapatalk 2 / Swype
[Galaxy S III Original Android Development] martiros:
is there anybody that wants to answer to this question?

i want to ask you if is it possible to implement in s3 kernel NTFS WRITE FUNCTION IN EXTERNAL USB HOST. thanks.
[Galaxy S III Original Android Development] HassanM:
I believe not after Feb 22's release....
[Galaxy S III Original Android Development] beardymarrow:
1.9.0 and higher do support more recent cm10.1 nightlies.

"There are only 10 types of people in the world, those who understand binary, and those who don't."
[Galaxy S III Original Android Development] pippoaacc:
Anyone about my previous post? (Page 1118)?
[Galaxy S III Original Android Development] FeyoMx:
excellent work simply sublime. definitely the best kernel but someone know that in recent versions both causes overheating in some devices?:what:
[Galaxy S III Original Android Development] rlorange:
Yes it is SiyahMODs bug from my app with the timeout/rotation issue... Will be fixed in the next version coming soon
[Galaxy S III Original Android Development] last-home:
I don't think. no problem.

yes, you can install two samsung roms.

use STweaks, Go to DUALBOOT then select Hijack Recovery...

dual - boot options will come in your recovery.
[Galaxy S III Original Android Development] Pusheka:
How disable zram.Gone option.
[Galaxy S III Original Android Development] zodiaxe66:
Flash v.190.zram disabled in this version
[Galaxy S III Original Android Development] invinciblecc:
Use zRAM control app from rlprange or my scripts a few pages back whichever u like
[Galaxy S III Original Android Development] fabzbear:
Can't get it to boot on the Sprint variant. Keeps getting failed error. Flashed using twrp, I'm on jellybam 7.2. I flashed the 1.9.1 version.
[Galaxy S III Original Android Development] Macchinista:
But this version didn't play video.
[Galaxy S III Original Android Development] Kyle07:
Dude, seriously. This is for I9300 (International Version) only. You could end up bricking your device.
[Galaxy S III Original Android Development] fabzbear:
My bad. Thanks for the reply. I'll try and find one for the Sprint variant
[Galaxy S III Original Android Development] guerouig:
First let me join in praising such an amazing kernel; hats down. I finally duabooted using latest siyah, sammy 4.1.2 as primary and cm10.1 as secondary rom. all went well untill i updated cm10.1 with latest nightly, using BBQTools. But upon flashing, the device gets stuck in the cyanogen logo, indefinitelt rotating. what to do? I can boot into recovery, but every time, same result. any way out? with my limited capabilities, I can only odin flash, but then, have to do everything again from scratch.

help would be much appreciated as to Why this? and how to get past it. thx folks.
[Galaxy S III Original Android Development] W@r10ck:
Has anyone tried CM10.1 latest nightly + siyah kernel combination? How was it? :)
[Galaxy S III Original Android Development] m0cha5hake:
Try booting into recovery and fixing permissions.
[Galaxy S III Original Android Development] mitchpunk:
I have something similar to this happening to me.

I had my 4.1.2 stock ROM and I flashed

Rootbox nightly as second ROM then swapped them so that rootbox is my primary ROM.

The thing is when I boot my rootbox ROM, it will stay stuck on boot animation so I have to restart again for it to start normally but it still takes longer

And sometimes I have to reboot twice for it to get past the bootanimation

I'll try that fix permission thing and I'll tell you how it goes :)

--------- Edit ---------

Nope, just tried it and it still stays stuck at boot animation unless I reboot it at least once or twice...

Sent from my GT-I9300
[Galaxy S III Original Android Development] Seicer:
Similar problem here. I swap my Sammy ROM as the second, then flashed CM 10.1 to the first but it it gets stuck on the cm logo... and the worst thing is that it doesn't ask me to boot the first or the second ROM it boots the first as default... although it says second detected on recovery please help :(

Enviado desde mi GT-I9000B usando Tapatalk 2
[Galaxy S III Original Android Development] m0cha5hake:
CM wont boot up as a second ROM with Siyah. You will have to use the Sammy ROM as your second ROM and CM as your first.

---------- Post added at 03:42 AM ---------- Previous post was at 03:40 AM ----------

Here is some more info about the problem.
[Galaxy S III Original Android Development] guerouig:
It is the first thing I tried, but it did not work

---------- Post added at 09:06 AM ---------- Previous post was at 08:56 AM ----------

One last thing : fixing permissions does not help either. Common folks, any hint is highly appreciated. I can't abandon cm10.1 and I need sammy for photo/video.
[Galaxy S III Original Android Development] Seicer:
OK fixing permitions was my solution to make cm boot... now the problem is that it says I don't have space for a sheet (I can't even receive an SMS) and also my apps are corrupted in both ROMs including Google services, Stweaks was deleted with some other apps and I can't install it again because there's not enough space.

It looks like I'll have to make a complete and clean flash and start again, this is the first and the last time I play with dual booting, I just wanted to try cm without deleting my Sammy ROM.. :'(

Enviado desde mi GT-I9000B usando Tapatalk 2
[Galaxy S III Original Android Development] m0cha5hake:
Use CM as your primary ROM. It will not work secondary. So basically do a clean wipe, format system and sdcard, and then flash your 4.1.2 Sammy ROM. After that clone ROM 1(Sammy) to ROM 2. Next boot into recovery wipe data, flash CM, flash Siyah, and you should be good.
[Galaxy S III Original Android Development] guerouig:
thx for your help. I thought that issue of cm10.1 being necessasrily primary was dealt with long go. so before trying this, I must tell you that it worked perfectly as secondary, untill I updated to the next nightly via BBQTools. Does it mean that if I were to dual boot with cm10.1 as primary, I'll be able to update normally afterwards?
[Galaxy S III Original Android Development] m0cha5hake:
OK. If it was working fine before as a secondary ROM, then the problem was probably trying to update it using BBQTools. I am not really familar with app but it might conflict with the way that Siyah sets up the 2nd ROM.
[Galaxy S III Original Android Development] guerouig:
I thought so too, thx a lot for taking time to help; hope someone will pop in and feed some thoughts too.

is there another thread of relevance to this matter?
[Galaxy S III Original Android Development] m0cha5hake:
There's a Siyah discussions thread in the general threads and you may also be able to find some help in the S2 threads for Siyah
[Galaxy S III Original Android Development] guerouig:
thx again bro, I'd hate to have to drop cm10.1
[Galaxy S III Original Android Development] m0cha5hake:
no prob :)
[Galaxy S III Original Android Development] invinciblecc:
But cyanogen mod and cyabogen mod based ROMs are booting up fine as secondary for me

But I have this problem

http://xdaforums.com/showthread.php?p=40065927
[Galaxy S III Original Android Development] SilentStrider:
Can someone tell me wich of this three custom recoveries (CWM, TWRP, Philz) is best suited to use with this kernel and why?
[Galaxy S III Original Android Development] STAticKY:
Personally i use philz because its soo feature packed. Except when i want to swap to siyah kernel then i use that as recovery (its a modded cwm) so i can dual boot.
[Galaxy S III Original Android Development] SilentStrider:
Can you elaborate bit more to that how does one boot to two different recoveries to start with? I mean if I press the 3 button combo or by using for instance the reboot to recovery from RomToolbox(JRammy's) app wich recovery loads? And finally do you know if this kernel is compatible with SGS3-I9305? Sorry if I sound like I am lost in the woods but I want to clear the basics before attempting to use this kernel!
[Galaxy S III Original Android Development] invinciblecc:
If u have not hijacked Ur recovery then Ur primary recovery say phills boots with the 3 button combo

To boot Siyah special recovery which comes with the kernel

U can either use swteaks app which has options in dual boot tab named reboot 2nd ROM utils (which means recovery )

Or u cab use stweaks all to hijack Ur recovery (option under dual boot tab again) which turns siyah recovery into Ur primary recovery....so if after hijacking u press 3 button combo it will boot u into siyah recovery only and phills recovery will be lost
[Galaxy S III Original Android Development] Seicer:
Any help to make CM boot as the second ROM?

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] SilentStrider:
So pretty much you have to go through hoops to have dual boot in simple words how come the developer of this kernel hasn't given the other recovery developers the necessary info to incorporate his kernels needs in to their own recoveries I mean a true dual boot should at least upon the start of the boot sequence you should be prompted to choose were you want to boot in and only after few seconds passed with out choosing which one to boot it would boot to the default rom because let's say you want to flash an other kernel later on you have to flash a recovery all over again as well to much hassle I think pretty much it limits you to have freedom of choice. All that said I don't doubt how good this kernel is and after all dual booting is really cool thing just a kernel that gives you a dual dooting shouldn't restriction you to a certain recovery, just a thought.
[Galaxy S III Original Android Development] guerouig:
the thing is, that it does not restrict you to a particular recovery. on the contrary, it does leave the recovery of your choice as default (three button combo), and allow you the option of hijacking only if YOU decide so. Otherwise the siyah embedded recovery is only necessary when it comes to the process of dualbooting itself.
[Galaxy S III Original Android Development] invinciblecc:
No u don't have to go through boot loops it is working for me and siyah recovery is option

This is true dual booting it restricts u to siyah kernel not to siyah recovery u can use phills recovery all the time but only when u need to change hr second rpm or flash a zip to Ur second Rom u will need siyah recovery

Besides if u have siyah kernel installed and after setting up dual boot it will ask ubwhether u want to boot to ROM 1 or two okay...butbu need to have siyah kernel to install for it to ask u this

Recovery u may use any

So just to make sure u got me right

Siyah recovery is needed only to set up second ROM and after that u may use any recovery it doesn't matter dual booting screen will come as long as Ur on siyah kernel whether or not u have hijacked Ur recovery

But when u need to flash zips to Ur second ROM or change second ROM then u will need siyah recovery the maker of this kernel was thoughtful about people being tired of switching recoveries when they wish to manage their primary and secondary Rom so he included an option to hijackbur recovery wherein siyah is Ur only recovery and u r able to manage both Roms and dualbooting from one recovery but this an option for comfort not for necessity... Even if u don't do it and use Phil's recovery (say) dual booting will work fine

Ya it such working and i am using cm as my second rom

Instead of flashing directly do this

Detailed explanation :: first do all the steps mentioned in op to install any second ROM from siyah recovery (that is format ROM system data cache then install the zip of cm flash kernel again and then fix permissions )

(Don't forget to format /data and /data/media from siyah recovery )

now don't boot Ur second ROM instead make a backup of Ur second ROM to external sd

Finally do these step again format cache system data data media from mount and storage and wipe second rpm dalvik cache cache data and format second ROK system now click restore as second ROM from external sd and choose the backup u made that's it don't fix permissions and reboot into second ROM it should work fine

In one line:: don't flash second ROM. Via siyah recovery directly instead restore a cwm backup of Ur second ROM using option restore as 2nd ROM from external sd (once uvhave made the cwm backup with permission fixed kernel reflashed that is)
[Galaxy S III Original Android Development] SilentStrider:
So how do you access the kernels recovery?
[Galaxy S III Original Android Development] invinciblecc:
Read op mate

Still answering download siyah and see dual boot tab there should be an option to reboot 2nd ROM utils that will lead u to kernels embedded recovery
[Galaxy S III Original Android Development] cmd512:
A bit of a puzzler:

v1.9.1 is absolutely flying, zero issues... until about 24-48 hours of steady usage. That's when things start to get really laggy and choppy, I mean Maps would freeze for nearly 15 seconds when trying to pull down the search bar. A reboot usually clears this right up, so I don't think it's anything hardware based.

Based on the zram feedback under various other kernel threads, I'm wondering if that may be the culprit? If it is, would it be a setting I need to adjust?

(My apologies in advance if this had been discussed to death already, just point me to the right thread if that's the case.)
[Galaxy S III Original Android Development] guerouig:
through STweaks, under dual boot tab
[Galaxy S III Original Android Development] TheMrcool212:
Any way to make the battery life lasts longer? because i want to dual boot roms
[Galaxy S III Original Android Development] SilentStrider:
Thanks! I assume Stweaks can be found in the market?
[Galaxy S III Original Android Development] invinciblecc:
Yup if u search for it that is

Please can we follow Ur questions in siyah discussion thread if !!!!!!

---------- Post added at 08:00 PM ---------- Previous post was at 07:59 PM ----------

Dual booting has no effect OK battery life still do one there is a thread around here somewhere which has various steaks profile there lies the and to Ur question

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

When j get lags open terminal emulator and check Ur used zram value this is most probably not related to zram ....

If when Ur getting lags Ur value of zram is very high above 400 lets say then maybe zram is causing lags

(P S. I haven't faced lags with zram and i have set it to 2gb

Max i ever saw it used is around 800mb still no lags so its very unlikely Ur lags are due to Zram

(Check Ur pm)
[Galaxy S III Original Android Development] cmd512:
I don't know, I just checked the Perseus thread, and it's dev is looking to disable zram because he also experienced some sort of memory choke / recovery issue. Sounds suspiciously similar to the situation I'm experiencing, so I have it disabled for now and will see if the sudden onset of support lag disappears. Well report back, thanks!
[Galaxy S III Original Android Development] invinciblecc:
Yup i read his post too but i encountered that only on Perseus zram is giving lags with yanks and siyah zram is not giving lag no matter at what value i set it too

Anyways go find out what works for u ..

P.S. if lags are in 24 hrs I'll rather live with it bcos of multitasking

Regarding thanks there is a button for it :D:D
[Galaxy S III Original Android Development] guerouig:
green power and quiet hours (cm10.1) or the equivalent (blocking) in stock rom, work fine for me as far as battery saving is concerned (I dual booted cm10.1 and XXEMC).
[Galaxy S III Original Android Development] SilentStrider:
Point me to the direction of that thread if want of course! Thanks
[Galaxy S III Original Android Development] invinciblecc:
Here u go

http://xdaforums.com/showthread.php?t=1709860
[Galaxy S III Original Android Development] Seicer:
The steps from mount and storage won't delete the data from my first ROM? Cause I don't want to lose it. Also, I tried doing everything you said except the steps from mount and storage and it won't boot from cm as the secondary ROM, the screen is black and nothing happens. No problem with the primary ROM.

Enviado desde mi GT-I9000B usando Tapatalk 2
[Galaxy S III Original Android Development] guerouig:
quite simply follow instructions from the OP, you don't need to worry about anything else. CM10.1 can be booted as primary or secondary ROM, it's not an issue anymore. As for CM, don't forget to flash GApps and to flash Siyah again afterwards, and you should be good.
[Galaxy S III Original Android Development] EgyMan:
hello Sir i have install Rom Stock Rom i9300XXELLA with kernel Siyah 1.9.1+ i checked info for this kernal it's can install 2 Rom on my Device i9300 and this kernal only supported for jelly been and CM10.1

question here is ?

this rom " [CM10.1][4.2.2][UNOFFICIAL][APR09] temasek's UNOFFICIAL BUILD - V89" supported with double boot for kernel Siyah

and how i can install it ?

and this rom have file boot.img

thank you

sorry for my bad english
[Galaxy S III Original Android Development] guerouig:
all you need to know is in the OP, only afterwards - if you still have questions - can people help you effectively
[Galaxy S III Original Android Development] rlorange:
Update: V2.4

Big improvements!

>> faster load new style

>> info popups and swap active data info button

>> swap priority settings (not yet configurable)

>> auto rotate bug fixed

Download: http://db.tt/DeM84E2H V2.4
[Galaxy S III Original Android Development] FadeFx:
rlorange, can we habe an option to enter swap/zram sizes manually?

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] SilentStrider:
Thanks
[Galaxy S III Original Android Development] Seicer:
Still the same, I tried to install CM directly to the 2nd ROM but it won't boot, it just gets stuck in a black screen and I can't do anything, just take the battery out and then start again.

It seems that dual booting isn't for me. :'(

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] Erahgon:
FYI, Andrei just reported that the zRam implementation on his kernel seems to be having a problem (memory leak) where pages aren't evicted from zRam although the application is closed (or the memory isn't marked free after a page is evicted). Either way, over time the device gets laggy and the zRam is unusable by the system.

@Gok: whether or not your zRam implementation is the same as Andrei's, just give it a check. Seems to be a problem with the system itself.

Sent from the present, which is now in the past.
[Galaxy S III Original Android Development] invinciblecc:
Hmmmmmmm i i don't think their are any different ways of implementing zram be it in siyah or somewhere else or Perseus or stock

The thing is maybe in andreis kernel something is stopping zram from working right

Trust me i tried it

Perseus on zram has far more lags than any other kernel on zram so i don't think its zram that's the issue maybe something in his kernel is conflicting with zram implementation or something different entirely say entropy or min free values

Maybe minfrees is causing lags try higher value of minfrees

Also zram coupled with zcache or clean cache support has no lags and i mean it absolutely no lqgs

---------- Post added at 09:20 AM ---------- Previous post was at 09:13 AM ----------

Guys somebody here knowledgeable enough to set this right

My both ROMs chaos and pacman are noting fine and working fine except after the first boot of the primary boot and subsequent boots of secondary boot after that

The second ROM seems to loose the permissions over its own file system that is storage/emulated/0 ....

After first boot of primary ROM the secondary ROM now requires su access for accessing this folder storage/emulated/0 .(where the entire file system of secondary ROM is located)

Naturally those appa which don't ask for su access like the play store keep on force closing and those appa which are provided su like titanium backup run fine.....

This is strange bug in dual booting

Just after one boot the primary ROM seems to set the entire internal memory as a system file which on subsequent boot of secondary rom it(sec ROM) required su access to use.......

So no installing Apps on play store normal apps wont run as their data is stored in this place storage/emulated/0 . and they cant access it without su

The problem is solved via fixing permissions on recovery but reappears after a single boot of primary ROM

Now just cant keep on booting to recovery and fixing permissions every time i need to use secondary ROM

Please anyone help????

And don't be idiotic i have read op and done exactly as said also have tried all possible combinations of instructions from op but in vain ....

So reply if u know .
[Galaxy S III Original Android Development] RedDevils88:
i am currently using Perseus Kernel. I want to flash siyah 1.9.1. the phone freezes after doing so and restarts itself.

What happened? :(
[Galaxy S III Original Android Development] MrMastodon:
Perhaps it decided to chill? :D :p

Try reflashing after downloading again.
[Galaxy S III Original Android Development] Bofu:
Is there a way to keep the kernel flashed after updating CM10.1? Tried downloading update and flashing through siyah recovery and it didnt help.

Running TWR with my S3.
[Galaxy S III Original Android Development] Dellair:
No problems here.

Android: 4.2.2

CM: 10.1-20130404-NIGHTLY-i9300

Siyah: 1.9.1
[Galaxy S III Original Android Development] andrewfung888:
I just flash siyah 1.9.1 from Perseus 35. No problem here. I changed zram to 0 and reset everything to default before I flash siyah.
[Galaxy S III Original Android Development] Nichie:
How do you set zram to 2gb when the s3 only has 1gb of ram?

Zram runs off the physical ram on the phone.
[Galaxy S III Original Android Development] cmd512:
Lol, what I thought too.......