yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] hollow1:
I'm kinda new to this. I'm on Omega v. 28 and I flashed with Siyah 1.7rc1 using. tar file with Mobile Odin, no problem at all though not playing with phone a lot. My question is, do I need to make any additional adjustments in STweaks?

If so it will be thankful to you all to give me one good setting as I don't have any idea how to get this done at all :)
[Galaxy S III Original Android Development] gokhanmoral:
I have added KingRamo's video overview of 1.7rc1 introducing dual-boot, 2ndROM utils (custom CWM-based recovery) and some features of stweaks..

it may be helpful for the beginners. thanks to KingRamo for it.
[Galaxy S III Original Android Development] ante0:
deleted
[Galaxy S III Original Android Development] mr. phillip:
Hi.

On the OP (6th post, to be correct) there are some pre-configured settings for different users profiles...

Try one of them...
[Galaxy S III Original Android Development] betovanbuuren:
Anyone?
[Galaxy S III Original Android Development] GrimPivo:
Try to ask in general thread.
[Galaxy S III Original Android Development] habylab:
This is very good, thank you!
[Galaxy S III Original Android Development] sharingan92:
Theres a button for that
[Galaxy S III Original Android Development] gurbuza:
Ok guys I have found out the solution you first flash ics and then flash cm10 your wifi should work now, Then flash siyah and boot into dual boot recover via the stweak app then install a sammy jb followed by siyah kernel. Your wifi on both roms should work this way make sure to wipe in each installation
[Galaxy S III Original Android Development] alysiper:
Hi,

I'm on Omega 28 and Cm10 using Siyah v1.7rc1 and i have serious lags when i browse through apps, all the transint animations are cut off, lag even when scorlling in settings. I don't know why.

Anyone have this problems?
[Galaxy S III Original Android Development] Sandor1:
Please leave non-development related posts to the discussion thread in general section: http://xdaforums.com/show...php?p=27389678

---------- Post added at 07:25 PM ---------- Previous post was at 07:20 PM ----------

Please leave non-development related posts to the discussion thread in general section: http://xdaforums.com/show...php?p=27389678
[Galaxy S III Original Android Development] skodaslx:
Deleted
[Galaxy S III Original Android Development] Tungstwenty:
The problem with strace was that I was using a version compiled from JB sources in an ICS ROM. A matching version must be used due to the shared libraries having different api versions.

Compiled binaries for both ICS and JB are attached, in case it might be useful to anyone.

And here's the relevant bit when running "strace mount -o remount,ro,suid,bind /tmp" (previously mounted with --bind to a .../system placeholder subdir):

stat64("/res/dev/data", {st_mode=S_IFBLK|0600, st_rdev=makedev(259, 2), ...}) = 0
mount("/res/dev/data", "/tmp", 0xd8aa5, MS_RDONLY|MS_NODEV|MS_REMOUNT|MS_NOATIME|MS_BIND|MS_VERBOSE, 0x1b04a8) = 0

Unlike what happens when "-o bind" is not used:

stat64("/res/dev/data", {st_mode=S_IFBLK|0600, st_rdev=makedev(259, 2), ...}) = 0
mount("/res/dev/data", "/tmp", 0xd8aa5, MS_RDONLY|MS_NODEV|MS_REMOUNT|MS_NOATIME|MS_VERBOSE, 0x1b0480) = -1 EBUSY (Device or resource busy)
write(2, "mount: mounting /res/dev/data on"..., 70) = 70

Unlike e.g. MS_NOATIME, the MS_BIND flag is not maintained as it was before and so it must be specified when remounting.
[Galaxy S III Original Android Development] sharingan92:
Ok so lately i myself have have been getting a little annoyed and im sure much of you have also the reason being stupid members not posting in the right section. The most annoying thing is that its always in the development forum and like all devs state in the OP there is a place for Q&A god dammit they even give you a link. Even more frustrating is one of these comments

Love your work thanks man! ￼

Geez there's a button for that thats just more clutter in the dev threads. But do those certain members listen? NO ovcourse not sooner or later the devs are going to get sick of people not listening and posting in the correct section. Even the devs of siyah kernel and Paranoid android are sick of everyone saying thanks and asking quistions then getting annoyed when we direct them to the Q&A or discussion thread. Well guess what noobs THATS WERE ITS MEANT TO BE

Now to all noobs and idiots reading this please start posting in the correct sections or we are all going to lose some amazing devs and do you really want everyone hating you because you didnt listen? Learn your lesson ￼

Sorry for posting here but its not like there going to read the general thread :)
[Galaxy S III Original Android Development] rlorange:
So I finally got a working CWM zip script to shrink your 2nd ROM system partition. 4 sizes available!... check it out here:

http://xdaforums.com/showthread.php?t=1943928
[Galaxy S III Original Android Development] jnr21:
Edit: wrong thread, sorry.
[Galaxy S III Original Android Development] rlorange:
Couldn't have done it without GMs help and script commands :)
[Galaxy S III Original Android Development] habylab:
I'd just like to say that's quite offensive and entirely not needed, as is this. I'm sure you will ignore this post, as it is from a "noob" who has 5x more posts than you (not saying that's justifying my actions) and also posted purely to show appreciation (already hit the thanks button) and to subscribe to the thread under the "participated" heading of the xda app.
[Galaxy S III Original Android Development] iBuzman:
Mod, pls delete (sry)
[Galaxy S III Original Android Development] hollow1:
Thank you for pointing me out. I can see the different. The kernel really does its job well. I try the performance tweak profile and it gives me a good feeling. I have even a nice phone now :good:

Big thank to droidphile for info & the presets and to developer gokhan for this precious kernel :highfive:
[Galaxy S III Original Android Development] bclark:
On latest Pa, using 1.7rc1.

While listening to Google music app, song ended and my phone just died. Black screen, no led, waited a couple minutes and held power to reboot.

Last Kmsg:

http://db.tt/J2y1CpDI

Unfortunately I'm out and I don't have anything to open it to check it myself.
[Galaxy S III Original Android Development] rlorange:
New sizes added to my Shrink 2nd rom CWM zips thread:

450MB -fits cm10 snugly and frees up 1.05GB of internal SD card space.

1.125GB -Safe size for the cautious, using stock deodexed Sammy rom's or those who like having space left for peace of mind :)... frees up 450MB of internal SD space.

1.5GB -designed to restore to default size "un-breaking" dual boot utility features... please test for me :)

http://xdaforums.com/showthread.php?t=1943928
[Galaxy S III Original Android Development] Joshaldo:
Hey guys I want to flash one of the flash able zips for performance but not sure which one I should flash, either the governer one or just the normal one? Thanks
[Galaxy S III Original Android Development] DirkStorck:
Hi. I have a feature request...could it be possible that the backup function for the second rom could make its backup in a different folder or in a sub folder?

Cause it is not possible to give the backup a name it is hard to differ whitch backup is from 1st and which is from 2nd ROM.

Thank you!
[Galaxy S III Original Android Development] danielg90:
setting for life battery?
[Galaxy S III Original Android Development] :
Hi,

6 th post, scroll down to the end of the post and you'll see some flashable zip's in attachments for different settings. There is battery, more battery, etc...

http://xdaforums.com/showthread.php?p=28491201

And for these kinds of questions there is this thread: http://xdaforums.com/showthread.php?p=27389678

:)
[Galaxy S III Original Android Development] elite_gamer04:
With the recent move back to ICS Wifi Drivers in CM10 to rectify Wifi Tethering, will using Siyah in association with Code's latest experimental break things?

http://xdaforums.com/showpost.php?p=33021485&postcount=10446
[Galaxy S III Original Android Development] aegixnova:
I very frequently get freezes that require a hard reboot, as well as repeating 1 second freezes (which occurred even as I began typing this)

Which logs should I post in order to aid in development of a solution?
[Galaxy S III Original Android Development] Hamburgle4:
Out of interest, could this be related to any undervolting you've done? And if so, have you stress tested before enabling any of the undervolt settings through apps like setcpu?

Sywped from my GT-I9300 running Omega v29 & siyah 1.7rc1
[Galaxy S III Original Android Development] aegixnova:
Nothing is undervolted, I've left the CPU settings untouched.

I've experienced similar freezing with Siyah across 1.6, and now with 1.7RC1, across different versions of Omega and Paranoid Android. Perseus kernel had infrequent bursts of freezes, until the latest version, but certainly not the type which required me to hold the power button down to force a reboot.

This was a huge issue across the 1.6s, I think, and it never really got completely resolved. Most of the people complaining never posted logs.
[Galaxy S III Original Android Development] Sukhi:
Try using the lulzactiveq governor inplace of pegasusq. Lulzactive performs way better on JB

Sent from my GT-I9300
[Galaxy S III Original Android Development] Lownita:
+ true, same for me!
[Galaxy S III Original Android Development] danielg90:
ok but what is the profile to save more battery?and the second?
[Galaxy S III Original Android Development] FRLinux:
Download getril from play and check out your modem. Until they matched, I had lookups.
[Galaxy S III Original Android Development] shahzaib.khan:
Cant find a download portion ...can any one give me a link

Edit:Just found it on Google....
[Galaxy S III Original Android Development] dantheman122:
My RIL showed Unknown, what rom/modem are you using and what RIL did you pair with it?
[Galaxy S III Original Android Development] Striatum_bdr:
Think about reporting this unknown ril to the author. The best matching ril is normally auto-selected.
[Galaxy S III Original Android Development] shahzaib.khan:
can I increse the value of charging from 1000 to more ??? To charge fast?....does it is Oki with the device or it is bad for hard ware?
[Galaxy S III Original Android Development] sharingan92:
Yes you can increase it via stweaks and it just means you will need a new battery earlier than normal
[Galaxy S III Original Android Development] shahzaib.khan:
Ohh so u mean it will decrease the life of my bettery?
[Galaxy S III Original Android Development] Lownita:
This phone already charges blazing fast compared to s2! But yes, increase to 1200 and enjoy lightning fast charging :D
[Galaxy S III Original Android Development] shahzaib.khan:
Does it decrease the life of bettery?
[Galaxy S III Original Android Development] sharingan92:
Eventually yes but that wont be for a very long while
[Galaxy S III Original Android Development] shahzaib.khan:
I am confuse I mean I dont know what to do so just give me the answer of this question....is it good and safe to increase from 1000 to 1200 ?....
[Galaxy S III Original Android Development] bradputt:
yes, it's safe to charge @ 1200, I have been charging using this since siyah supports it ( few months already)

and yes, it'll deplete your battery faster. but it won't be gone in days.
[Galaxy S III Original Android Development] andip71:
It is good, as your device will charge faster.

It comes with a slightly reduced battery life time. But so far nobody can tell you how much, there is not yet enough experience. So far we assume it does not significantly decrease battery life time though, there should always be some buffers in the manufacturing process.

Andi
[Galaxy S III Original Android Development] :
Maybe Bug Report?!? Car Mode does not work on Omega v29 DLJ1 and Siyah 1.7rc1 can some confirm this on the same fw and kernel?
[Galaxy S III Original Android Development] Fahimxda:
Battery drains very fast

Hi Guys,

I am using Omega rom yesterday i installed Siyah kernal 1.7rc2 on my samsung galaxy S3 what i noted is the battery drains very fast say like 10mins screen on it drains like 5-6%. I have not made any tweaks on the siyah kernel. I read siyah kernel gives a good battery life is so then how come i am not making of it any suggestions. Thanks in advance.
[Galaxy S III Original Android Development] tolis626:
Kernels that aren't released yet are known to cause battery drainage.Don't worry,it's normal.Now head over to the discussion thread if you want a serious answer.
[Galaxy S III Original Android Development] Fahimxda:
Hi Tolis,

So where is the discussion thread. Which Siayah Kernel version can i install.
[Galaxy S III Original Android Development] jnr21:
Discussion thread: http://xdaforums.com/showthread.php?p=27389678

If you have jelly bean rom, flash 1.7rc1: http://www.gokhanmoral.com/gm/2012/10/06/siyahkernel-s3-v1-7beta1/

---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------

There is no 1.7rc2, latest is 1.7rc1.
[Galaxy S III Original Android Development] shahzaib.khan:
Can any one explain me the tweaks are in first post.....can I install that with rc1?....and are they can be installed together or we can install only one at a time?.....and I need details of every tweak which is in first post
[Galaxy S III Original Android Development] ksameh:
You mean rc1 of course.

Over omega v29 based on xxdlj1 (TW three based rom)

I have noticed the same thing.

Using cpu spy I have noticed that the processor stays a lot at 1400 mhz.

So I tried changing the governor and io to the same as stock. That is pegasusq and cfq.

Same results. Cpu stays at 1.4 ghz for more than 70% of the usage time. It deep sleeps fine. But when used that is the case.

Stock kernel averages more around 1000 and 800 mhz.

I suspect touch boost but am not sure. I have not had more time to test it. I reverted to stock kernel for now.

I tried hunting down a process that made the cpu go that mad with no luck. I tried using bbs and development options with no luck. Nothing showed excessive processing and the phone was not lagging at all.

My tweaked stweaks setting are (other settings are the same as default)

-50 uv cpu (I tried also no under volting with no change in results)

Logging disabled.

Eargasm enabled.

Mdnie invert disabled.

OMEGA V28 worked perfectly.
[Galaxy S III Original Android Development] sizzlers:
Battery drain is huge,ima be with stock kernel till fix.WINAMLITE rom,JKAY DELUXE FRAMEWORK
[Galaxy S III Original Android Development] Net.silb:
WiFi Tethering fixed on CM10, hope this gets implemented soon to Siyah Kernel!

I'm pretty sure it's kernel related.
[Galaxy S III Original Android Development] rlorange:
New version of my second ROM shrinker mod.

You can now select any size you want and adjust the size anytime by running again

The new version is an interactive script run from 1st ROM using script manager or equivalent. Enjoy :)

http://xdaforums.com/showthread.php?t=1943928
[Galaxy S III Original Android Development] andreasy:
I've read the q&a forum that this release of siyah fixes the car dock mode for i-bolt. Can someone confirm that this is true?
[Galaxy S III Original Android Development] jeebspawnshop:
That's nice. All the dev-related information you provided in your post has been IMMENSELY useful to GM. Thank you, sir, really.

Nope, GM was actually lying about it. It's all an elaborate hoax to dupe the unsuspecting public! The joke's on you, haha.

---

---

And while I have all of your attentions, I would like to take this opportunity to thank you all for ONCE AGAIN turning a DEV-ONLY thread in to a discussion thread rife with useless posts and inane comments.

Thank you all for likely peeing off one of xda's greatest devs by DISREGARDING his requests and instructions.

Truly, you all have my undying gratitude.
[Galaxy S III Original Android Development] elite_gamer04:
My question exactly, I'm assuming the Wifi Drivers are related to the Kernel and we have to wait for master Gohn to merge :)?
[Galaxy S III Original Android Development] sharingan92:
It will be merged into rom i think so any cm10 rom will get it i hope
[Galaxy S III Original Android Development] t0n0n:
I've tried to post at the general topic, but no one seems to know the answer(They don't even tried).

I have random freezes while using that Kernel, they mainly happens when I'm using media services.

When the phone freezes, it happens by 2 ways, sometimes it loops the media(Audio) like when a processor fails(I've seen it a lot while overclocking, but I'm not doing OC/DC or UV) or it just freeze and doesn't answer anymore(Like when the processor got stuck).

I've tried do do it with Perseus, Stock and Siyah(The only ones who boots my phone) and only Siyah hangs. Since today, the versions who gave me problems has 1.7+(the ones after DB implementation), but now 1.6.8 started to hang too.

The test conditions was:

Siyah 1.7 RC1 with stock Stweaks + Youtube: Freezes, sometimes just after the video starts, sometimes after 1~2mins, the most error rate is here.

Siyah 1.6.8 with stock Stweaks + Youtube: No freezes on most times, hangs while using Xperia Walkman and lags/lock with PowerAmp).

Tried a lot of configurations for Stweaks, but none appears to increase or decrease the error rate

Perseus: No freezes, but I cannot customize it and none of my ROMs use it(And I trust the developers and most users do not report the same errors).

Stock: No freezes, but it didn't surprised me.

I've tried super wipe.

Sometimes, my Stweaks closes when loading the .xml and when it come back, all my settings are screwed up. I need to close and reopen to see the right configs, but some still appear to have changed.

There's any file I can look for to provide further information? Anyone here reported the same errors(I'm sorry to be lazy, but it's too much to look for)?

I'm trying to understand that last_kmsg file, what I must look for?

I've got my Eclipse and android setup updated, I'll try to provide a logcat, will it help??

I'm sorry if I didn't provided enough information or my post is wrong by anything, just tell me and I'll change or test again.
[Galaxy S III Original Android Development] pswin09:
Seem to be something wrong with your phone hw.
[Galaxy S III Original Android Development] Diaze:
Can some1 give me a direct link fo siyah kernel for wanamlite rom 4.0.1?pls
[Galaxy S III Original Android Development] sharingan92:
Link is in OP
[Galaxy S III Original Android Development] Sukhi:
Here you go....use the lm version.

http://d-h.st/users/siyah/?fld_id=5905#files

Sent from my GT-I9300
[Galaxy S III Original Android Development] madmack:
Thanks for your post Robb.

I'm having the same issues here. If you look at the DATA part of these packets, you'll see the names of the SSIDs of neighboring access points. It is the BT-AMP bug which is some proprietary bluetooth speed enhancement technology from broadcom. This problem started happening in some SGS2 ROMs (Gingerbread) but Entropy512 and from my little testing here and there confirm that these issues are not kernel related but they're userland related. I've played around with the wireless driver; disabled BT-AMP, tried to filter out these 0x886c packets but none of it stopped these packets from appearing on these "dirty" networks while keeping a solid wifi connection on.

If you can find any S3 ROM (or any ROM on any device that uses the BCM4334 chipset) where this problem does not happen, then I'll be very happy to swap around some userland proprietary binaries to see if the problem gets sorted.
[Galaxy S III Original Android Development] Rob2222:
Do you really think/know that it is coming from the userland part?

I would have thought that these packets are generated from the wifi/bluetooth driver (and thats in the kernel, right?) for that chipset or that its generated from the chipset hardware itself, so you maybe must reconfigure the chip to make it stop.

Maybe a workaround would be to add these packet types to the packet filter like the multicast packets?

@Gokhanmoral:

Can you say, what happens when for example one of these blocked multicast packets come in? I know since you have added them to the packet filter, they did not trigger a full wakeup anymore.

But do they still trigger a half wakeup of some kind or are they completely filtered out by the wifi chip in hardware so that the wifi chip doesn't generate a interrupt at all anymore?

BR

Robert
[Galaxy S III Original Android Development] madmack:
I did try to add these 0x886c packets to the filter. My wifi driver refused to connect to any AP when I did that.

Thing is, on the S2 the same kernel when installed on different userland ROMs sometimes exhibited that bug, and other times not. So it's most definitely not a kernel driver issue. I have searched in the sources for that protocol code and it only exists in the BCMDHD driver to indicate incoming control packets from the bluetooth chipset. From what I could gather, it's the way the bluetooth controller sends some control commands to the wifi chipset (HCI control stuff that is beyond my league). So all we have in source code is how to handle incoming data of that protocol type but I haven't found anything that indicates how they're generated which leads me to believe that they're coming from their proprietary binaries. That and the few reports from the S2 forums where users experience this bug happening on some stock ROMs and not others while keeping the kernel a constant confirms it.

I'm not aware of any Android devices that use the BCM4334 chipset other than our phone. I'll keep looking.
[Galaxy S III Original Android Development] Rob2222:
I also think that they are a kind of control packets of the bluetooth or the wifi part. I also just found the receiving parts in the kernel, if I got the code right.

OK, from your text I now understand the problem. We don't have the full source code, right? So we can only use some binaries from broadcom, which already have that bug. And these binaries are in the userland?!

PS: I've just checked on AOKP second rom... same problem.

PSS: If we would know which parameter from some access point makes these binaries go crazy, we could maybe filter that parameter in the kernel/wifi driver so that the binaries think were connected to a good access point?

I mean, as I said, I have a good and a bad access point here, direct next to each other. When connected to the bad AP I have that bug, when connected to the good AP I dont have that bug. So there must be a parameter on the bad AP that makes the broadcom binaries go crazy and make them generate these packets each 10 seconds.

BR

Rob
[Galaxy S III Original Android Development] madmack:
Yeah, that's what I think. It also agrees with Entropy's findings. I came to realize later that he actually made quite an extensive effort to try and solve it. I wish I saw his posts before I fiddled with the driver myself. lol

For the userland blobs, I'm eyeing blobs in /system/etc/wifi (a firmware and nvram file that the kernel module loads on boot up) and the bluetooth blobs in /system/bin/bcm* and a couple of other files like brcm_poke_helper

Now if only I can find a ROM on the S3 that actually works fine, then I can start playing around with these files. I don't want to put in the S2 binaries from BCM4330. Not sure what that will result in. lol

Edit: As to looking at which "parameter" is wrong from the APs, I don't think it's a good route to take given that we have no clue how or where these packets are generated from. If we have access to their sources, it would be easy to debug it and find the culprit.
[Galaxy S III Original Android Development] Tungstwenty:
My guess (not well founded, though) if that the filter is programmed directly into the controller and thus there won't even be an irq fur the cpu to wake up and then decide whether to fully wake up the device or not.

I think I browsed the code before and the filter info was being sent to the controller, but I'm not sure I drew the right conclusions nor if it's still that way.