yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] SyLvEsTeR20007:
Error with Dual Booting.

Hi all,

I am having some issues with getting dual boot to work. I worked for a while but I think I deleted something and now it doesnt work.

Alittle more detail is that when I try to format 2nd ROM it seems to start but then it doesnt compleate and recovery just loads back to the menu without anything being done. I cant seem to find the files that are ment to be stored on the int sd card.

Any advice how to get it back? I have tried reloading the kernel but that has no worked.

Thanks

Syl
[Galaxy S III Original Android Development] Code124Y:
deleted... post at wrong section... sorry
[Galaxy S III Original Android Development] gokhanmoral:
I will check all those items one by one again but until then possible reasons are:

1- you don't have enough space left on your internal sdcard. use diskusage app from google play to see if there is any big files (maybe in lost+found dir) wasting space and clear them.

2- for some reason the size of system.img file is changed and it cannot be formatted. remove it and try to format again

3- if everything fails try to remove /data/media/.secondrom folder and try again.

there may be bugs in 2ndROM utils..

and if none of those 3 works you will have to wait until I reproduce that problem.
[Galaxy S III Original Android Development] jeebspawnshop:
Did you use the 2nd ROM Shrinker script/app from this forum? If so, that might explain your issues.

If not, then I have no idea either.
[Galaxy S III Original Android Development] xanthrax:
actually those scripts has been compiled to an application which i use without problems. :cool:

his issues are not related to kernel nor to developement and better answers he will get from Siyah Kernel Discussion Thread (IRC)
[Galaxy S III Original Android Development] flinkebernt:
I'm having some strange problems when using my favorite two kernels, Siyah and Perseus.

My setup is very simple:

Omega Rom v31 - No themes or mods except HXCamera

No supercharge script or other mods

No UV or OC

I've tried several versions of Siyah and Perseus and it all seems to work very good in the first few hours after a fresh boot, but after a while apps start lagging and a lot of these messages appear in dmesg:

<6>[13782.598809] c1 evict_bh_lru[1467] drop buffer head d8ec5280.
<6>[13782.603878] c3 evict_bh_lru[1467] drop buffer head cf5fc500.
<6>[13782.603939] c2 evict_bh_lru[1467] drop buffer head d5014500.
<6>[13782.603975] c3 evict_bh_lru[1467] drop buffer head d5014d00.
<6>[13782.604016] c3 evict_bh_lru[1467] drop buffer head d8b31d80.
<6>[13782.731694] c0 evict_bh_lru[1467] drop buffer head eb079c40.

Sometimes when this happens, apps start to crash when I launch them

<4>[13789.302433] c0 dumpstate: page allocation failure: order:4, mode:0x40d0
<4>[13789.302517] c0 Backtrace:
<4>[13789.302609] c0 [<c00495b4>] (dump_backtrace+0x0/0x10c) from [<c05c9478>] (dump_stack+0x18/0x1c)
<4>[13789.302718] c0 r7:00000004 r6:00000000 r5:000040d0 r4:00000001
<4>[13789.303082] c0 [<c05c9460>] (dump_stack+0x0/0x1c) from [<c00f94c0>] (warn_alloc_failed+0x9c/0x118)
<4>[13789.303364] c0 [<c00f9424>] (warn_alloc_failed+0x0/0x118) from [<c00fa060>] (__alloc_pages_nodemask+0x494/0x75c)
<4>[13789.303485] c0 r3:0000000f r2:00000000

mmcqd/0 is hogging the CPU at the same time.

Also tried to reset to default settings in STweaks with no luck.

Once I flash back to stock kernel these problems disappear.

I've attached the whole dmesg and dumpstate_app_error.txt from when this happens.

Anyone else seen something like this? I know the same kind of problem was on 1.6x versions but I've tried all the latest versions as well.

If you need more information or other logs, I'll be more than happy to help out!
[Galaxy S III Original Android Development] :
How to get stock boot animation back?

Hi everybody! :D

I really like this kernel on my SGS3, but I also liked the stock boot animation...

By checking the no boot logo flag in STweaks, all I got is the stock animation without sound...

Is there a way to get it back?

Hoping in your help :confused:
[Galaxy S III Original Android Development] skchattha:
Siyahkernel v1.7RC2

on website: http://www.gokhanmoral.com/?p=1489

It says in logs, (updated on 6th Nov, 2012)

■v1.7rc1 -> v1.7rc2: new STweaks (500% faster startup, retouched UI ), applied wifi changes in CM10 repo to fix wifi tethering problem. Based on update6

....

....

....

What does this mean? Has v1.7rc2 been released or cm10 wifi thether issue has been fixed in v1.7rc1?
[Galaxy S III Original Android Development] rickgillyon:
No. You'll know when it's released as it will be downloadable and the title of this thread will change. :rolleyes:
[Galaxy S III Original Android Development] FadeFx:
Gokhan, would you mind to remove general cwm features from 2ndromutils, as they only cause confusion?

_________________________

tapatalked from GalaxyS
[Galaxy S III Original Android Development] gokhanmoral:
I would, but I am planning to make a "hijack recovery" button in stweaks to flash the recovery to the recovery partition.

I will try to make a boot mode dependent cleanup in the interface though.
[Galaxy S III Original Android Development] tolis626:
Hey Gokhan,great to have you back.

I saw in your to-do list that you plan on making AOSP ROMs compatible with exFAT.Do you mind explaining how you intend to do it?The only way I know is modifying the vold,but I think that changing it just like that would cause problems with some ROMs.

If you need testers,I may have a few spare SDs. :)
[Galaxy S III Original Android Development] dantheman122:
How do they cause confusion? They seem to have worked every time I've ever used them for 1st and 2nd rom flashing etc. Or do they fail for some things?
[Galaxy S III Original Android Development] Striatum_bdr:
Better to have 'usual' recovery for working with the primary rom, and kernel built-in one only for secondary rom. Separate roles, less confusion. Even when tnings are straight clear 50% of people don't read instructions and are naturally confused (see hundreds of posts from people that don't evn read OP), so....

And clearly no need to have 'normal' features in this built in recovery. Better to consider it as a tool and not a full featured recovery.
[Galaxy S III Original Android Development] enigma1981:
I disagree, but I think it should be swapped around so that the "dual boot options" page is the first page you see when you enter siyah recovery, then have an option at the bottom for "Main ROM Options" to give you all the regular recovery tools
[Galaxy S III Original Android Development] dantheman122:
Agreed, I like being able to use it to flash both roms, I don't really want to boot into two recoveries if I want to do things to both roms.
[Galaxy S III Original Android Development] j0bro:
On gokhanmoral's website I read:

But... where is it? I cannot find a d/l link for 1.7rc2.
[Galaxy S III Original Android Development] enigma1981:
Probably because there isn't one yet... he's just posting that change log for the upcoming release.

Swyped from my Galaxy S3
[Galaxy S III Original Android Development] DirkStorck:
Gokhan could you please let your recovery use a different directory for making backups and restore...I often get confused if the backup is now the one for my 1st or 2nd ROM in the clockworkmod directory. That would be great! :)

Thank you ! :)
[Galaxy S III Original Android Development] carrd:
i'm sure this has already been covered but the thread is huge and my rubbish work connection will take me hours to search.

I apologise and I dont want to annoy anyone but can people recommend there SIyah settings for better battery and performace without risk of braking my phone.

Currently I undervolt by -100 but is it worth over clocking also? I have read its best to go no higher than 1600 with the over clock. I am basically looking for settings to give amazing battery life compared to stock and performace without harming my phone.
[Galaxy S III Original Android Development] FadeFx:
Yep, think that is a good idea, however, there is a problem with some flashable zip not doing anything if flashed from touch based recovery, that's why i prefere to keep non touch recovery for first rom...

_________________________

tapatalked from GalaxyS
[Galaxy S III Original Android Development] rlorange:
Finally finished it! All major functions now working ;)

>>>SiyahMODs Shrink system image size for 2nd ROM

> Shrink 3rdROM too

> Boot to Util recovery

> boot to 2ndROM

> Boot to 3RD ROM ;)

> and more!...

You need busy box in /system/xbin/ for now.

http://db.tt/sBtudxdc

PLEASE COME HERE FOR DISCUSSION:

http://xdaforums.com/showthread.php?t=1943928
[Galaxy S III Original Android Development] carrd:
Gokhan for some reason upon reboot my modified setting in sTweaks revert back to their defaults.

Have others had this issue? if so is there a fix?
[Galaxy S III Original Android Development] DirkStorck:
@rlorange: Your apps looks really great! But I must say that is a bit slow.....:(

I have tested 2 thing.

1) ROM status

-> it tells me to input the name of 2nd ROM but I can't find a input field.

2) Reboot 3rd ROM

-> it endet um in an boot loop.
[Galaxy S III Original Android Development] mossief1965:
I can find the input field but it doesn't remember the name I put in.
[Galaxy S III Original Android Development] rlorange:
Did you follow the instructions and tap "Save Input" button after?

---------- Post added at 07:58 AM ---------- Previous post was at 07:55 AM ----------

Please come here for SiyahMODs app discussion:

http://xdaforums.com/showthread.php?t=1943928
[Galaxy S III Original Android Development] Drakenfall:
Hello. I have a question. I flashed this kernel. Used Antutu to see default scores. It give me around 12000. I then oc to 1.5 and it go up to 12800. But then every oc I make 1.6 1.7 1.8. It runs the test but with very low result. Like 10000 or under. Is it Antutu problem (it always shows me I am at 1.8) or is my chipset that can't handle more then 1.5?

I also tried to oc the gpu and for that I used step one 266. 2 -350. 3 -440. 4 -533 5- 600. But it doesn't seem to take any effect. At least in Antutu result.

Probably is a noob question but if some can answer I would appreciate.
[Galaxy S III Original Android Development] jblparisi:
Hi, anyone want to take a shot at helping me compile from source?

So far it has stopped on this error:

Kernel: arch/arm/boot/zImage is ready

find: `/tmp/ramfs-source-sgs3/.git': No such file or directory

mv: cannot stat `drivers/media/video/samsung/mali_r3p0_lsi/mali.ko': No such file or directory

`./fs/cifs/cifs.ko' -> `/tmp/ramfs-source-sgs3/lib/modules/cifs.ko'

`./fs/lockd/lockd.ko' -> `/tmp/ramfs-source-sgs3/lib/modules/lockd.ko'

etc..... etc...

And here are my environment paths:

/home/unknown-linux/android/siyahkernel-sgs3 - For kernel source.

/home/unknown-linux/android/ramfs-sgs3 - For RAMFS

/home/unknown-linux/android/android_prebuilt - For tool chain.

I am running the build script off /home/unknown-linux/android/siyahkernel-sgs3 as NON root.

Any ideas? Thanks.
[Galaxy S III Original Android Development] tolis626:
Thermal throttling taking place.Further in the discussion thread.

Although this would be better of in the discussion thread...Have you tried running as root?Have you tried another toolchain?Did you check your config for errors?
[Galaxy S III Original Android Development] Striatum_bdr:
No need to be root to compile, as no write operation in system files is needed. Must be a config problem in one of the makefiles (mali one?). As compilation went to the end it's not a toolchain problem (it would have stop at the beginning).
[Galaxy S III Original Android Development] Yank555:
Toolchain looks fine to me, the kernel compiled fine (zImage is ready).

You need to check the build script, it's obviously expecting things on different place to pack it into the boot image.

JP.

Sent from my custom ARHD 14.0 / Yank555.lu JB kernel v2.4a Aroma (JB-U6 / Linux 3.0.51) powered Galaxy S3 i9300 using Tapatalk 2
[Galaxy S III Original Android Development] gokhanmoral:
v1.7rc2 is up.

there is no change in the 2ndROM utils because I had some problems with my vm and I will have to fix that first...

if you want to use 2ndROM utils as recovery you can use "hijack recovery" option in dual-boot tab.

we have new stweaks which loads way faster than before.

if it is not installed as default you can find it in /res or google play.
[Galaxy S III Original Android Development] optmkleung:
Screen mode cannot change, I love natural rather than standard. How to fix? Thanks.
[Galaxy S III Original Android Development] gokhanmoral:
I have added cyanogenmod mdnie settings to rc2 and it made the indices shift.

I will try to fix it or add an option to stweaks to choose the default using the correct indices..

the startup scripts remove the old stweaks and install the new one.

you may need to update your shortcuts.

I had to rename the package name to publish to google play.

that is why old stweaks shortcuts won't work with the new one.
[Galaxy S III Original Android Development] optmkleung:
Thanks!! I love your work very much!
[Galaxy S III Original Android Development] senses!:
Gokhan great work. Rc2 kernel and new steaks works fine FAST and SMOOTH.

Siyah power!

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] Notor1ouS-:
also ive to add, the sharpness tweak cant be disabled anymore it seems. when i untick the option in stweak, it still remains blurry after a reboot.

using omega v31, it worked on the rc1 release but not on the rc2 now. can any1 reproduce that "bug"?

apart from that, kernel runs supersmooth
[Galaxy S III Original Android Development] kLONkRIEGER90:
RC2 work perfectly on Stock Rom

no laggs now and stweaks works fast

thx waiting for a new version with new functions :)
[Galaxy S III Original Android Development] gokhanmoral:
same reason... cyanogenmod mdnie settings doesn't have sharpness tweak values.

you can change mdnie scenario manually by using init scripts until I fix it.
[Galaxy S III Original Android Development] AndroidGX:
The green led is working but takes a very long time from 100% to full charge.

Had the same problem in rc1 but not in latest SpeedMod kernel (for example).

Will try to bring a log if needed.
[Galaxy S III Original Android Development] ickoicko:
With regards to post number 6 and the release of rc2, are the zips updated accordingly? thanks!
[Galaxy S III Original Android Development] Kroenen66:
Release notes:

single image for kernel and recovery,

if you flash it to boot partition it is a kernel,

if you flash it to recovery it is a CWM-based custom recovery

(hijack-recovery will be available in STweaks to flash a custom recovery).

Can someone please explain what this means?

I've never read anything about that you

can flash a kernel with two different methods.
[Galaxy S III Original Android Development] bbboldy:
thanks now it's working..

just flashed the rc2 and so far so good :D

good job Gokhan :good:
[Galaxy S III Original Android Development] sgs9:
install Kernel in cwm, open new stweak, read in Dualboot option, easy :)
[Galaxy S III Original Android Development] stfudude:
I noticed that the camera app kinda have a bluish hue to it. I can't make a screenshot while using camera app, I tried but can't. But there is definitely something wrong with camera app after flashing rc2. Hopefully this is not a case of user error. Can someone else confirm?

EDIT: Android 4.2 camera is unaffected. This problem only occur in stock samsung camera.

EDIT2: I managed to take a screenshot. Silly me, forgetting the old way of taking a screenshot (Hold Power + Home buttons). :p But to my surprise, the colour seems normal. The white colour of all the buttons in camera app are white in the screenshot but bluish while using the camera app. This is indeed strange!
[Galaxy S III Original Android Development] Mumin:
I can also confirm that there is a blue hue on the stock cam
[Galaxy S III Original Android Development] Striatum_bdr:
Using Odin or Mobile Odin you can use the same tar file either by installing it in kernel partition (it will be a kernel) or in the recovery partitin and then the embedded recovery will overwrite your existing recovery.

It's a dual usage dual boot kernel lol
[Galaxy S III Original Android Development] gokhanmoral:
how many times should I confirm that there is a mdnie related problem in the latest version?

this is the third time and let me be more clear this time:

-you may have sharpness problems in rc2.

-colors may not be accurate in rc2

-screen may be blurry in rc2

-you may have black crush problem in rc2

I hope this will be my last acknowledgement of the same problem and will stop you flooding the thread by reporting the same problem over and over again.
[Galaxy S III Original Android Development] gokhanmoral:
yes, exactly.

my description was not clear...

in tar file we have boot.img.

if you unpack and rename it to recovery.img and flash you will have a CWM-based recovery in your recovery partition.

and "hijack recovery" just duplicates boot partition to recovery partition.

in a way, as Striatum_bdr said, it is dual-usage image now.
[Galaxy S III Original Android Development] tolis626:
Wifi tethering stopped working when I flashed rc2.I'm using FoxHound 1.3.Bluetooth tethering works ok though(And consumes less battery,duh!).Probably because of CM wifi drivers.If it's just me ignore it,but for some it may be a biggie.
[Galaxy S III Original Android Development] gokhanmoral:
you are right.. I tested it on cm but not on Samsung ROMs. the driver change broke wifi tethering on Samsung ROMs.

too bad... it will be hard to make it work on both of them.

EDIT: I forgot that dhd.ko is a module. I will use different bcmdhd modules for cm10 and Samsung ROMs in the next release.
[Galaxy S III Original Android Development] mrmrmrmr:
too bad. I was just going to install rc2 for the cifs solution. But wifi tethering seems more important for now.

:(

waiting for Gökhan's next attack :)
[Galaxy S III Original Android Development] gokhanmoral:
rc3 is up.

I did not test it but I think it will fix wifi tethering problem on both samsung and cm10 roms.

EDIT: I tested it and it did not work on samsung roms. I will reupload it before I sleep.
[Galaxy S III Original Android Development] cba1986:
Wifi stop working on rc3. Doesn't even turn on.

EDIT: You beat me for a split second.
[Galaxy S III Original Android Development] shorty1483:
Erm...gokhan...for me WiFi thethering worked well in rc2 (Ultima ROM DLJ5).
[Galaxy S III Original Android Development] gokhanmoral:
hmm, strange.. it didn't work for me. maybe it's related with wifi firmware in the system partition.

anyway.. uploaded rc3 again. tested it on both samsung and cm10.

wifi worked on both. I hope wifi tethering will work as well..
[Galaxy S III Original Android Development] instinctkiller:
Hi Gokan !

I just installed the last version of your kernel and... Wifi tethering works fine on Samsung rom, not on CM10 (Dual boot).

If i can help you, let me know !
[Galaxy S III Original Android Development] dantheman122:
Edit: It's working now, just rebooted and seems fine, maybe I didn't wait long enough the first time or something, but I'm sending this from my laptop using the phone hotspot so definitely working for me.
[Galaxy S III Original Android Development] makalolo:
Hye gokhanmoral,

After flash RC3 my STtweaks FC ,... any solution?

Edit : I reboot again and its work!!
[Galaxy S III Original Android Development] Maceee:
Are these values added in rc3? Or when will the Developer add them?
[Galaxy S III Original Android Development] mrmrmrmr:
RC3 works for me.

It has cifs fully working. Also wifi tethering works on my stock JB rom.

I don't use dual rom...

thx Gökhan.
[Galaxy S III Original Android Development] MiG123:
Hi any kind soul mind mirroring this on say box or gdrive? Cuz Dev host has been acting up for me lately, connections keep timing out. TIA!
[Galaxy S III Original Android Development] Maceee:
How about changing screen mode with rc3?
[Galaxy S III Original Android Development] Agaranda:
Hi Gokan.

Cause a hearing problem, I need to boost bass only in one channel. I thik that I'm not the only one. Would be possible in the future to get separate channel eq in Siyah?

Thanks in advance

Galaxy S3 DLJ4+Siyah1.7 Earsonics SM3
[Galaxy S III Original Android Development] Mopral:
Works for me on stock DLJ4
[Galaxy S III Original Android Development] unstandardized:
Ok, so i had a bit of a problem with either RC2 or RC3. I tried both and flashed them with MobileOdin.

I first downloaded RC2 on my PC and simply transfered it on my SD card. after i flashed with MobileOdin and rebooted, i get the message on my phone saying it was "unable to find software on your PC that can recognize your device". went into recovery, wiped my cache, booted back but i still get the message. on Windows, it is able to detect my internal/external sd card, but i can't do any file transfers (to or from).

Since I can't transfer files from my PC to my SD card anymore, I downloaded RC3 (just now) from the phone and flashed it again with MobileOdin; same error after I booted back in.

I re-flashed RC1 and it fixed the problem.

Just wanted to know if anyone else has experienced this or if any has a fix for this in RC2 or RC3.

** Note: I'm on XXDLJ4 (stock) I also updated Kies on my PC when I initially got the message after flashing RC2.
[Galaxy S III Original Android Development] adrien_razvan:
I get that message from time to time, not always, transfering files work but at low speeds..... Using DLJ4, sotmax ultimate v5
[Galaxy S III Original Android Development] Musko:
Same here with that message, slow copy speed and Omega v31. Siyah 1.7 RC3

Sent via smoke signals using Samsung Galaxy SIII ...
[Galaxy S III Original Android Development] hisee:
Can any one give rc1 ?
[Galaxy S III Original Android Development] xan:
It appears that profile support has been removed from rc3.

Why?

It breaks extweaks' profiles. Is that a bug or did you do that on purpose?
[Galaxy S III Original Android Development] bradputt:
hello, i press hijack recovery but i don't like it.

anyway to revert to my touch recovery?
[Galaxy S III Original Android Development] cba1986:
Is due to the new version of stweaks.
[Galaxy S III Original Android Development] xan:
I can see no relation.
[Galaxy S III Original Android Development] dantheman122:
Can't you just reflash it?
[Galaxy S III Original Android Development] sgs9:
With Odin I think, for rc3 with cwm here no problem.
[Galaxy S III Original Android Development] Ttblondey:
Here you are rc1
[Galaxy S III Original Android Development] Ttblondey:
Receive this error message.By the way does the server down can't downloadthe rc 2/rc3. Getting both from others.
[Galaxy S III Original Android Development] makalolo:
can any one give new version of STweak?
[Galaxy S III Original Android Development] Ttblondey:
It's automatically install when you flash siyah kernel 1.7rc2/rc3.
[Galaxy S III Original Android Development] :
https://play.google.com/store/apps/details?id=com.gokhanmoral.stweaks.app
[Galaxy S III Original Android Development] sprongebob:
hallo

ich habe ein problem mit dem neuen kernel 1.7rc3

wenn mein s3 ausgeschalten ist und ich es aufladen möchte

dann sehe ich keine led leuchten

die batterie anzeige ist grau und hat einen weissen kreis in der mitte

bei der orginalen samsung rom leuchtet die led und im display sieht

man das battery symbol

und bekommt so eine meldung das aufgeladen wird

leider fehlt das in diesem kernel

bitte um einen fix

danke

translate with google

Hello

I have a problem with the new kernel 1.7rc3

if my s3 is off and I want to charge it

then I see no LED lights

The battery indicator is gray and has a white circle in the middle

the orginal samsung rom the led lights and the display looks

to the battery symbol

and so gets a message which is charged

sadly lacking in this kernel

Please fix a

thank you
[Galaxy S III Original Android Development] schlei:
Hi can anyone tell me where the second Rom is located on my es file explorer from main Rom?

I want to copy game files from rom1 to rom2.

greetings from germany