yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] gokhanmoral:
I tried to make system.img a directory in sdcard but I forgot one thing: system should be readonly :)

it caused lots of problems and I stashed 2 days of tests/changes because they were very intrusive, I didn't like that much of hack just to make it working.

so, we are back to system.img mode.

rlorange has successfully shrunk the size of the system.img file and I guess he will write a doc or it because I will not have too much time to add an option for it to 2ndROM utils soon.

cardock mode, backup/restore fixes for 2ndrom utils and ums fix are the main changes in rc1. there are some other changes which are not worth mentioning...

I will release it tonight.
[Galaxy S III Original Android Development] alienmind:
Gm, just to let you know that wlan_rx_wake wakelock has make his way back on b6 w/ cm10, sorry to not post further details now on my commute but will investigate later tonight.

Cheers

Sent with my cold hands from the grave
[Galaxy S III Original Android Development] edgarf28:
Any progress on fixing the color difference with a cm10 based rom when using your kernel, Gokhan?
[Galaxy S III Original Android Development] bariz143:
Hi. One small problem here. I use cm10 as primary rom and omega as 2nd and i full wiped my 2nd rom today and i noticed that all my game data where gone on my cm10 rom to. Why is that?
[Galaxy S III Original Android Development] webup:
Can this kernel be used with the stock Polish JB release????
[Galaxy S III Original Android Development] FadeFx:
yep...
[Galaxy S III Original Android Development] gokhanmoral:
no, I still have that in my todo list, there is no need to remind it or repeat the request.

there is no easy way of doing it. cyanogenmod added a new scenario to mdnie values and it shifted the available scenarios.

I don't want to break anything on samsung part to fix that.

so it will not be in the current release.

you can try to set the cm10 values using /sys/class/misc/mdnie interface

use this: https://github.com/CyanogenMod/andr...n/drivers/video/samsung/mdnie_table_c1m0.h#L7
[Galaxy S III Original Android Development] sachs:
Image is "erased " with rc1...cm10-4.1.2

does not see anything...only blur
[Galaxy S III Original Android Development] corgar:
with latest version with wanamlite rom 3.9 i can't see anything. Some mdnie bug?
[Galaxy S III Original Android Development] Gliedfried:
Deleted.
[Galaxy S III Original Android Development] amirsardari:
after flashing 1.7rc1 on my revolution HD 11 rom my phone boots in a wierd situation . screen just shows blue and red and black colors . its like inverted color in black and red so i shifted back to 1.6 B4 and its all ok again . this color issue just hapenning 1 seceond after showing boot animation
[Galaxy S III Original Android Development] kkk-sgs2:
On rootbox too, all the time

Tapatalk 2 // GT-I9300 // RootBox
[Galaxy S III Original Android Development] gokhanmoral:
oops.. it was exactly what I meant by "dont want to break anything on samsung side" :)

I will reupload it...

I forgot to revert some mdnie related change before recompilation

links will be updated in 10 mins
[Galaxy S III Original Android Development] FRLinux:
Same problem here, reverting to b6 fixed it.
[Galaxy S III Original Android Development] Craxx:
New version works fine after reupload. :)

Craxx;)

Send from my S3 with Tapatalk :)
[Galaxy S III Original Android Development] Techniques:
Same problem but I'm using Dark ParanoidAndroid.

I typed this by hand.
[Galaxy S III Original Android Development] afcp:
Just on image blue and red on reboot, back to beta6

Checkrom v5.5
[Galaxy S III Original Android Development] Striatum_bdr:
Yes,

unusable here too with Paranoid or Revolution HD, colors are completely messed only dark blue, dark reds, will come back to previous version.

EDIT: fixed (sorry for the noise)
[Galaxy S III Original Android Development] gokhanmoral:
I have updated the links. sorry for that.

I did not change the version number as everybody has to redownload it anyway..
[Galaxy S III Original Android Development] Mirciulikkk:
Learn to read, guys!
[Galaxy S III Original Android Development] gokhanmoral:
it would be nice if people do not repeat the report after I have acknowledged it...

now people won't see the links are updated because of 10s of posts...

anyway...

it is fixed now. flashed and tested...

please edit your posts after testing it.
[Galaxy S III Original Android Development] afcp:
OK blue screen fixed on Checkrom v5.5 :):D
[Galaxy S III Original Android Development] bariz143:
But i did fullwipe in 2nd rom utilites and all my apps on 1st was untouched beside game data
[Galaxy S III Original Android Development] genius.lizard2:
1 issue:

kernel: 1.7b6

flashed 2ndRom (foxhound v0.8a)

can't install theme (so vrtheme way in aroma installer won't work)

when i choose for example aosp dialer blacked in aroma installer nothing will be change!
[Galaxy S III Original Android Development] SignalX:
Edit: found it!

sorry for post,
[Galaxy S III Original Android Development] Erahgon:
I haven't tried this, but from your experience I gather that the sdcard was indeed wiped.

Both the 1st ROM and the 2nd ROM have the sdcard (also mounted too data/media) and extSdCard in common with each other. Sdcard is also where the game data files are stored for some games (usually older games).

A full wipe from 2nd ROM utilities probably wiped data/media (i.e. the internal sdcard) as well.

CWM 5 (from Chainfire) and CWM 6 do not touch the sdcard nor the extSdCard during a full data wipe (unless you use a script such as the super wipe script from ARHD, which would be out of CWM's control).

So, provided you did not use a script, then maybe Gokhan's CWM acts like the stock recovery: a full data wipe results in the sdcard being formatted.

Sorry for the long winded post. Just wanted to clarify a few things.
[Galaxy S III Original Android Development] NewAussiefromCanada:
1.7rc1 All Black Problem

I Appologize if this has been answered. I am running into a odd problem

Just tried flashing 1.7rc1 on my S3 i9300, Installation went perfect, however upon reboot half way through the boot animation all white turned black, and the phone went very dark. As if it did not have the ability to produce the color white or something along those lines. Even with brightness at max I could barley make anything. out All yellows were replaced with an odd redish color and the only color i could see was blue.

Thankfully I was able to flash back to 1.6.8, which resolved the problem.

Tried re-downloading and reflashing 1.7rc1 with no luck.

Running Omega v28 Rom.

Anyone else experiance a problem like this, and if so find a solution? or am I just lucky! :confused:

EDIT: Resolved!
[Galaxy S III Original Android Development] brunodmjr:
Issue:

Having problem with battery stats logger with Siyah 1.7rc1. Screen seems to be consuming a lot of energy. I believes it is more a log problem than a real problem. Someone having that?

With Siyah:

With stock insecure LIB downloaded from Omega files:

No extra mods, only JB domination theme.
[Galaxy S III Original Android Development] Maesedroid:
Wipe cache and battery stats, had same issue after that its fixed! :thumbup:
[Galaxy S III Original Android Development] brunodmjr:
Have tried. It didn't work :(
[Galaxy S III Original Android Development] Rambooka:
I am using ASOP Omega V2.0 as primary ROM with Omega 27.2 as the 2nd ROM with Siyah 1.7b4 and everything is awesome, smooth and working without ANY problems.

The problems start when I program Siyah 1.7b5 or 1.7b6 or 1.7rc1

=> I have setup "Screen Lock" to use a pattern to unlock the phone...

when the screen turns off and I press the power or menu button to wake the phone up, I am prompted to enter a pattern, which I enter...

the phone the keeps showing the unlock pattern and now the screen freezes...

Android is still running in the background (The Music player still plays music)

Siyah is still running as I can press the menu button 4 times to invert the display

Tapping the power button can still turn on and off the LCD

The only solution is to hold the power button in until the phone reboots....

one I program back in Siyah V1.7b4 everything is working OK

- the Omega V27.2 2nd ROM does NOT have this problems with pattern unlock on any version of Siyah kernal

This problem of freezing is also present with Resurrection remix V3.0.9

- I thought is was resurrection remix at fault, so I programmed Omega V2.0 and the problem is back

- I have not tried programming Siyah V1.7b4 with resurrection remix, and I don't run it anymore, Omega AOKP is much better

Hope this problem can be fixed soon... I you need some logs, let me know and i can send them

_ have about 500 apps installed on the S3 and run Nova launcher
[Galaxy S III Original Android Development] webup:
Wish there was added reboot options from power button on this kernel:p
[Galaxy S III Original Android Development] K Rich:
I'm pretty sure that's built into the ROM and not kernel.
[Galaxy S III Original Android Development] sachinaik:
Can u pls send 1.7 B4 cwm zip to me ? I'm using RR3.0.9.
[Galaxy S III Original Android Development] chrismast:
you can use this mod, works great
[Galaxy S III Original Android Development] osator:
So I ask again...

JB stock kernels (and Siyah kernel too) doesn't support car mode and audio out. I found solution in this thread:

http://xdaforums.com/showpost.php?p=32688111&postcount=175

It works very well. Could you add this to siyah?
[Galaxy S III Original Android Development] yhrn:
Please have a look at the latest change log or read a couple of pages back.
[Galaxy S III Original Android Development] osator:
Sorry, I was blind...
[Galaxy S III Original Android Development] kachrukamble:
Device Temp. getting high with 1.7rc1, don't know why..It was all fine with beta 6
[Galaxy S III Original Android Development] Rob2222:
Hello Gokhanmoral,

first of all, thank you for that nice kernel. I hope you did not abandon the S3 soon, even you have got your Xperia T.

In a post from Entropy512 I read, that you know the Broadcom 0x886c packet bug.

This bug is still present on SGS3. ICS/JB and stock/siyah/perseus kernel, all have them. Even a 100% stock ICS S3 with newest firmware has the bug.

It just triggers only at some wifi networks. I think it depends on the wifi chipset on the access point. As soon as you switch the access point, it stops.

I have a wireless router (Speedport W303V) that triggers the bug. And I have a wifi range extender connected to that router. As soon as the S3 switches over from the router to the wifi extender/repeater, the bug is gone. And it's the same network, same ssid. So the access point chipset must be the cause that triggers the problem. That W303V should have a Broadcom chipset. But it triggers also on some Fritzbox routers, that did not have a Broadcom chipset as far as I know.

When it triggers, it creates 6 packets and with this wakups per minute. You can see the wlan_wake kernel wakelock wake cound (wc) in BetterBatteryStats increasing bis 6 counts per minute.

You can prove it by capturing with "shark for root" 10 minutes and analyze it on cloudshark.org or with wireshark app, when you see sixty 0x886c protocol packets.

On my good network I have 50 wakeups caused by wifi over night, on the bad network I have 2000. This is not as bad as the 1Hz wakeup, but the 10Hz wakeup is still not very nice.

The device seems to send wifi configuration information to itself with this packets. It uses it's own mac address, flips one bit and uses this address as source and then sends packets to its own mac address. (See this) So like a loopback / local tunnel. This seems OK, but I think it should not fire / wake the phone each 10 seconds. (It's not exact each 10 seconds, its a little unregular but its around 6 packets per minute)

Could you maybe check if you can fix this anyhow? But, as I said, this bug is also existent on full stock devices.

I have a router that triggers it, if you need a tester, just feel free to PM me.

If you want, I can also send you a wireshark log.

Best Regards

Robert
[Galaxy S III Original Android Development] ajvulcan:
I have some problems with siyah rc1 and light manager(app for the led's control) . The microprocessor is always at 1,4 ghz when it's active (lightmanager), if I disable it the processor goes to 200 mhz aprox, so it backs to a normal state. With previous versions it didn't happen.... Might some problems the people report about more power consumption are related with that.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] Mumin:
One problem, not sure if this can be fixed with siyah or a ROM bug...

I have stock jb as 1st ROM with my Google account and 2nd with cm10 but I can't log in with the same Google account, do I have to make a gmail account and buy all my apps again or is there a way around this? Thanks
[Galaxy S III Original Android Development] brunodmjr:
Agreed with the guy a little back. Adding to my battery stats being a bit crazy with 1.7rc1 (wipe battery stats does not fix the issue), the phone is getting hotter than beta 6.
[Galaxy S III Original Android Development] kilabdg:
Hi!

Can I install MIUI as a 2nd ROM?

Wysyłane z mojego GT-I9300 za pomocą Tapatalk 2
[Galaxy S III Original Android Development] EViollet:
Wrong thread. Please post here : http://xdaforums.com/showthread.php?t=1709860

And the answer is yes if your MIUI is Jelly Bean based. Otherwise it's no.

Regards,
[Galaxy S III Original Android Development] kilabdg:
Thanks for an answer, and sorry for wrong topic ;)
[Galaxy S III Original Android Development] AndroidGX:
1.7rc1 looks pretty good on my device. No problem detected so far.

It finally brings back stock kernel experience in term of 3D while using high-end games like GT3 : no more lags, no more stutters, even with full settings and resolution to max, it's fully playable like stock, now we are only limited by the GS3 hardware again, no more by the kernel :D

I had a "Media" wakelock in battery stats this night in pure idle deep sleep, which drained 16% from 100%, but after wiping cache+dalvik cache, the problem looks solved for now.

Very good job gokhan :good:

PS : for people who still meets slow AC charging problems, as gokhan stated : simply plug to AC only once device is fully booted (once at homescreen). I confirm it worked like a charm.
[Galaxy S III Original Android Development] alias_neo:
Mirror

Download from Dev-Host keeps failing for me after about 1MB, are there any mirrors to RC1?
[Galaxy S III Original Android Development] Tungstwenty:
So I read a bit more and now see that bind is precisely meant for sharing the same fs (or a part of it) under different mount points.

There are some issues mentioned with regards to "mount --bind -r " in one go. Our version fails to set it ro silently, whereas on my Ubuntu running 3.2.0-32 it does warn that it's mounting it rw instead of ro as requested.

But on 3.2.0-32, doing the "mount -o remount,ro" after the bind works fine. I even double checked if it was indeed read-only on one m-point and rw on the root one, or merely reported that way when running plain "mount" (also reported as a problem by some folks). It works!

If only someone :D would, say, find the change applied upstream and apply it on the *kernel*, perhaps this would be feasible after all.

Still puzzled about the sdcard holding ext4 attributes, though :confused:
[Galaxy S III Original Android Development] :
Hi,

Works fine for me, Maybe change the browser?

In any case:

1.7rc1 in .tar: http://www.multiupload.nl/V7DLGI764B

1.7rc1 in .zip: http://www.multiupload.nl/3GZP8ZPEAS

:)
[Galaxy S III Original Android Development] Tungstwenty:
:victory:

[COLOR="DarkRed"]~ # touch /data/local/tmp/_hidden_dir_/system/xpto[/COLOR]
touch /data/local/tmp/_hidden_dir_/system/xpto
[COLOR="DarkRed"]~ # mount --bind /data/local/tmp/_hidden_dir_/system /tmp[/COLOR]
mount --bind /data/local/tmp/_hidden_dir_/system /tmp
[COLOR="DarkRed"]~ # mount -o remount,suid,ro[U],bind[/U] /tmp[/COLOR]
mount -o remount,suid,ro,bind /tmp
[COLOR="DarkRed"]~ # mount | grep /data[/COLOR]
mount | grep /data
/res/dev/data on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc)
/res/dev/data on /tmp type ext4 ([COLOR="Green"]ro,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc[/COLOR])

Ok, now I'll leave the petty implementation work on your hands :laugh:
[Galaxy S III Original Android Development] Ognjen123:
I have problem when i flash 1.7RC on omega v28 rom , the problem is with display of colours , it start on the midle of bot animation colours become dark and wierd ?

---------- Post added at 06:29 PM ---------- Previous post was at 06:22 PM ----------

Ignore that , flashing it from odin seems to work fine
[Galaxy S III Original Android Development] betovanbuuren:
If i want to flash as 2nd rom a stock based rom JB, but my primary is AOKP based will i have NFC, Wifi Errors?
[Galaxy S III Original Android Development] Thomas.:
Do not works external SD card in recovery for me. I have Samsung JB and 1.7rc1 (but with new touch recovery not works before to)
[Galaxy S III Original Android Development] gokhanmoral:
we have /sdcard using /data/media but it uses FUSE to simulate case insensitivity and permissionless sdcard-like behavior.

I am using /data/media/.secondrom/data to keep data and was planning to use /data/media/.secondrom/system to keep system files so that we can save some space by not using 1.5GB system image for 200+MB ROMs.

we were lucky to have hidden partition size to be the same as system partition on S2.

hidden partition is being used as 2ndROM cache on S3.
[Galaxy S III Original Android Development] gurbuza:
I'm running Sammy jb rrom as a 1st from and as a second rom im runnung cm10 but my wifi is not working cm10. I know that you have to flash ics before you flash cm10but i can"t boot into ics as this kernel doesn't support ics. How can i make wifi work on cm10 thanks
[Galaxy S III Original Android Development] betovanbuuren:
Did you flash 2nd rom after having sammy JB based?

I've a similar question: I've never flashed Sammy JB, went direct from sammy ICS to CM10 without wifi issues, but now i've flash sammy jb based to 2nd rom. Does that will bring me wifi errors on 1st rom with aokp?
[Galaxy S III Original Android Development] Geo1997:
Thx for your kernel and dual booting :victory:
[Galaxy S III Original Android Development] alienmind:
Apologies if it has already discussed, but could it be possible to implement vol-up during boot to go directly to 2nd rom utils / integrated recovery? Thanks

Sent with my cold hands from the grave
[Galaxy S III Original Android Development] UrbanDesigns:
When I select the .tar file for the "Recovery" option in Mobile ODIN it just states "Partition could not be found in file."

but when opening mobile ODIN it says I need an odd-on which redirects me to the place I downloaded the .apk in the first place, I even downloaded again from the exact place it directed me to but to no prevail... does anybody know what's going on?
[Galaxy S III Original Android Development] bclark:
You should be asking this in that thread but you need the flash kernel apk. There are 2 to install, the regular app and the device specific flash kernel. I'd advise you read a whole hell of a lot before you use something that you clearly didn't read the OP about though. Also you don't need the Siyah recovery so I don't know why you're using that option.
[Galaxy S III Original Android Development] UrbanDesigns:
I was following the instructions on the main post :(
[Galaxy S III Original Android Development] bclark:
These?
[Galaxy S III Original Android Development] Striatum_bdr:
You are flashing a kernel, not a recovery. You selected the wrong partition type.

The embedded recovery can't be considered as a recovery as it's inside the kernel. Recovery partition isn't touched.

So select kernel in mobile Odin for flashing.
[Galaxy S III Original Android Development] keizero:
You're about to flash a kernel--Siyah--not a recovery. If you're not sure, just try "Open File" and select the .tar file.
[Galaxy S III Original Android Development] dev-host.eu:
It's fully understandable why UrbanDesigns had troubles with it.

For once, the user actually did as OP stated in page 1, but then just forgot to look at the file b4 flashing it - common mistake ;)

So perhaps OP needs to review his installation instructions,as they could be misunderstood ;)
[Galaxy S III Original Android Development] Rambooka:
Any thoughts on this
[Galaxy S III Original Android Development] droidphile:
I have clearly stated not to bother selecting a "recovery" in MobileOdin, if kernel.tar filesize is less than 8 MB; just selecting "kernel" will do. If that's ambiguous, already edited that answer in faq.

Let's continue this kind of discussions to this thread.

It's easy:-

1. Quote or Multi Quote the post(s) you want to reply from this dev thread.

2. Type in your reply, DO NOT HIT Post button.

3. Select the entire text. (Ctrl+A).

4. Head over to discussion thread, hit Post Reply at the bottom left.

5. Paste (Ctrl+v) copied text. Hit "Submit Reply"

That's how we continue discussions there without interrupting what we discussed here when it was forgotten this is a dev thread. :)
[Galaxy S III Original Android Development] MiG123:
im getting really slow data speeds/connectively on rc1. flashing to another kernel or reverting to earlier siyah solves it.

edit: my bad, clearing dalvik+cache solves e issue...
[Galaxy S III Original Android Development] Tungstwenty:
Interesting.

So if /data is actually the entire flash usable space (after subtracting kernel, recovery, efs, etc.) and sdcard is merely a FUSE'd subtree of that, does that mean that your approach of using /data/media/.secondrom/system instead of a fixed-sized ext4 image file will work with that mount --bind followed by a remount? Or are the kind of problems you encountered not only related with the RO vs RW and therefore still not a viable solution?
[Galaxy S III Original Android Development] gokhanmoral:
mount --bind followed by a remount did not work in my case. it also mounted other bind mounts (such as data) on the same volume ro.

and I did not want to patch some parts of the kernel or spend another 2 days just to fix that.

yes, we have /data/media content same as sdcard content. that is why we can create the 1.5GB sized image file in less than a second.
[Galaxy S III Original Android Development] Tungstwenty:
Did you remount with "-o remount,ro,...,bind"? Stating again the "bind" option made the difference in my case, without it the RO would be propagated to the parent mount (hence the "device busy" error).

I didn't have a ready strace command to confirm the mount command behavior, but it might be a busybox-related behavior. When not issuing again a -o bind, it could be assuming you want to say "nobind" instead of maintaining the previous flag.

PS: I think i'll fetch an androing strace implementation, it looks interesting :)

I tried the one that ships with aosp but it segfaults, probably I need to recompile the kernel with the FTRACE options enabled.
[Galaxy S III Original Android Development] johho:
Small question for my understanding, if I set under volting in stweaks to -100mv, does this work only during boot time or in normal use-mode too?

If I use setcpu too, if there's a voltage shown for a step of 800mv, is the "real" actual voltage than 900mv (because of -100 setting in stweaks)?

I'm a little bit confused

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] gokhanmoral:
hmm, actually no, I don't think I have given the bind option to -o again.. I will try it tonight.

if it works it will be great as there will be no need to shrink or expand...

and maybe I will use the same method for s2 and have a single image for both data and system
[Galaxy S III Original Android Development] gurbuza:
Is there any chance to run cm10 and Sammy jelly bean dual boot without any WiFi errors. No matter what I do I can't get WiFi to work on the cm10 ROM. I went to ICS but still no luck as soon as I flash Sammy jb I lose WiFi on cm10 please help thanks