yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] graffixnyc:
Guys, I'm not going to say this again.. Keep the non dev related things out of this thread. Even if you are reporting bugs but don't have anything useful for the OP to use to fix said bugs you SHOULD NOT BE POSTING here.

For example:

"I'm getting really bad battery life" Have a log to provide? no? Then DO NOT POST

"My benchmark scores are awesome on this kernel" DO NOT POST

"What are your settings for.....?" DO NOT POST

"I'm running the kernel with these settings and everything is perfect" DO NOT POST

"Thanks for this great kernel" DO NOT POST, THERE IS A DA*M THANKS BUTTON!

"My phone keeps freezing" DO NOT POST

"My Phone keeps freezing, here is a log cat" OK to post

"I'm having really bad wake locks, here are my logcats and BBS logs" OK to post

I'm already starting to hand out official warnings/infractions. If it continues we will shut down the thread temporally until you guys learn how to post properly

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] bitcasual:
Yes i have and i believe i've fulfilled those requirements. I did not specify what rom i use because i've tried on several roms (omega v27.1, WanamLite, CM10, Android Revolution 11 and many more both sammy and cm based.) and it's still the same problem. Major lags when playing music, in all other apps, and i've also found lags when using two (or more) GPS apps att the same time. For example Zombies, run and Runtastic. It's almost to the point of the lags becoming a freezing issue and this only occurs when two or more GPS using apps are running, if i pause one of them, the lags go away.

If i would've have experienced lags on only one particular rom i've would have wrote so, but as i got lags on all of them...

And for the settings im using all defaults with sTweaks, i have not changed one thing.

Im not using extweaks.
[Galaxy S III Original Android Development] OverRipeBananas:
Again, post log files. Nobody can see what's going on without them.
[Galaxy S III Original Android Development] MuertoKo:
Ok you get that point... but did you attack a Log? Just ONE post above was said that only bugs with logs and battery drain with BBS logs... without them it's useless!

Could be nice it you try to reproduce those lags on both CM10 and Sammy based and attach logs, as both work different but both have the bug, right?
[Galaxy S III Original Android Development] NZDroidDev:
My first question would be can you provide screen shots of your phone showing every running process and how much ram they are currently using when these lags happen? It would seem to me that it is not the kernel but your setup. How much free memory do you have on average, have you done a complete clean install on your phone? As in format internal sdcard? And can you provide logs from when these lags or freezes are happening? Lags can be caused by anything, including rogue apps. Considering that the lags have been solved for pretty much everyone, I would say any remaining would probably be the result of user configuration (not just kernel or Rom, but installed apps etc). I would suggest moving your posts over to the discussion thread as I don't think your issues stem from the kernel.

GM, I have a question though, the mdnie tweaks you have provided an interface for, do they include the interface to alter the brightness curve (more specifically the min_bl value) as I find more often than not the screen is too bright in ambient light inside at night. If it is not already included would it be possible to include that at all? I like you find the stock autobrightness pretty good, I just think the stock min_bl needs to be set at least at 60, if not 80.

Cheers dude.
[Galaxy S III Original Android Development] zappoo:
Just curious, what does this mean:

"change packet filter settings to block multicast (thanks to Entropy512)."

I can find very little info online..

I am getting wlan_rx_wake kernel wakelock and am just doing some research
[Galaxy S III Original Android Development] :
grrr is it so ****ing hard to read????? i guess this thread should really get closed.
[Galaxy S III Original Android Development] droidphile:
flashable zips

OK, here are flashable zips as promised. 4 flashable STweaks Profiles and 5 Governor Tweaks scripts (for pegasusq, lulzactiveq) to go with them. Pick your fav stweaks profile and a governor tweaks script, flash'em. You can flash one governor tweaks over another. It will replace the previous one. Flash remove_governor_tweaks zip to remove governor tweaks script. To remove STweaks Profile, just reset STweaks and configure your own.

Once again please remember - battery and performance are different sides of a coin. You can balance them to a perfect harmony at some point, but expecting 9 hours screen-on time and blazing UI & games at the same time is...........

Normal settings/profiles are the kernel defaults provided by GM. These zips aim to go two levels below normal(battery) or two levels above normal(performance). Zips only indicates my personal preference. It's not the ultimate setup to get the max out of performance or max battery. You can modify as you wish, or don't flash them if you have own idea of tweaks.

I will also post these zips to 6th Post and keep them updated if something changes in newer builds of kernel.

- You can recharge battery, but can not recharge performance.

- If we're likely to find ourselves having no access to charger most of the time, it's better off biasing tweaks towards battery and away from performance.

- If you're more interested in faster loading of apps than animations, set "Windows Animation Scale" to 1x and other two scale to 0.5 x in Settings -> Developer Options.

- Let "Force GPU Rendering" be always ticked under Developer Options.

- Depending on what governor was set in STweaks (pegasusq or lulzactiveq) corresponding tweaks are executed.

- GamersTweaks is also a governor tweaks script - same as ExtremePerformance script with the addition of increased staycount for last GPU step and decreased GPU sampling interval.

Lastly, I may have to write an exclusive FAQ about a special feature soon. Getting the hunch? :)

EDIT: Please download zips from this post instead of here
[Galaxy S III Original Android Development] jothi2lingam:
Can I flash the profile & governor script if different type example ( battery profile & performance governor) or should flash same category
[Galaxy S III Original Android Development] droidphile:
Ofcourse yes. Profile zips are 'default.profile' files for /data/.siyah used by Stweaks app.

Governor tweak zips are init.d scripts. They're mutually exclusive.

Anyway say we're looking for battery, then combination of performance profile+battery governor doesn't sound so good. Does it.
[Galaxy S III Original Android Development] cba1986:
I just was seeing some details of the extremeperfomancedetailprofile. GENTLE_FAIR_SLEEPER should'nt be off to get better permonance? :confused:
[Galaxy S III Original Android Development] bordikun:
^

Good question. But GM made GENTLE_FAIR_SLEEPER "enabled" by DEFAULT on the 1.6.8 update. So really don't know which is which. >.<
[Galaxy S III Original Android Development] xos84292:
Update the baseband to XXDLIB .i had this problem befor,then update the baseband to jb ver . It's fixed. Do not use the ics baseband.

---------- Post added at 04:38 PM ---------- Previous post was at 04:34 PM ----------

Update the baseband to XXDLIB .i had this problem befor,then update the baseband to jb ver . It will fixed. Do not use the ics baseband.
[Galaxy S III Original Android Development] nicesoni_ash:
Post removed.
[Galaxy S III Original Android Development] kilgorcalrizian:
I had Siayh v.1.5rc1 installed on ICS and it worked fine. I just updated to JB and when I try to flash v.1.6.8 my phone wont boot, it just gets stuck on the Siyah logo screen.

Any idea what the problem is?
[Galaxy S III Original Android Development] ilos:
full wipe before update to JB ? did you boot on JB before flashing Siyah ?
[Galaxy S III Original Android Development] kilgorcalrizian:
Thanks for the quick reply,

No, I didn't wipe the phone before flashing JB. Yep, I booted up several times on JB before attempting to flash Siyah (in fact, when my attempt to flash Siyah failed, I re-flashed JB and I've got it up and running right now.).
[Galaxy S III Original Android Development] jeebspawnshop:
I've noticed that if I'm on JB, and if I wipe cache+dalvik, I won't be able to boot in to Android. Dunno why, but it just totally screws everything up.

So if you're doing that before/after installing the kernel, try to NOT do it, and see what happens.
[Galaxy S III Original Android Development] kilgorcalrizian:
Thanks for responding!

Nope, I haven't wiped the dalvik cache.
[Galaxy S III Original Android Development] gokhanmoral:
blocking multicast doesn't mean that you won't receive any wlan_rx wakelocks.

if you continuously ping your phone and turn the screen off, you will have HUGE wlan_rx wakelock.

similarly, if there are some computers/devices on your network that access your phone (may be a trojan or another reason) you will have them a lot.

OR, if you have some apps syncing with an online service (maps, ebay, facebook, gmail...etc) and you may have wlan_rx wakelock when they sync over a wlan connection.

so, that patch doesn't mean that you will never have wlan_rx wakelock. and there is nothing wrong having wlan_rx wakelocks.

you just have to find out why you have them.

that patch will only help not to have it because of multicast packets.

I will try to make more proper change about brightness, it is in my list. the previous brightness modifications was good for low light conditions but had some problems with medium and high.

I am trying to finalize dual booting.

I have wanam and omega roms installed as primary and secondary roms.

it's a little different on s3 and a little harder than I thought.

I will try cm10 and samsung rom combinations and cloning/swapping...

I don't want to release everything at once without testing. so, for now, we will only have clone and swap functionality in the recovery.
[Galaxy S III Original Android Development] graffixnyc:
You people are continuing to post non dev related things in this thread. When I get back to my computer each one of you that posted off topic is going to have a nice warning/infraction sitting for them in their inbox.

I think I'm going to close this thread temporarily. Hey GM if you want to, you can close it that way you can edit the OP. If I close it, I don't think you will be able to edit it. Maybe forcing people to post in general because they have no other option will get them in the habit of posting there instead of here
[Galaxy S III Original Android Development] jody2k:
No offence but closing this thread wont hold the "offtopic people" away as its still a small group. The biggest group: the people that use this thread as it should be, will be punished again because of that.
[Galaxy S III Original Android Development] gokhanmoral:
I agree with this. There are more than 5000 downloads for v1.6.8. but even 1% is a lot of "offtopic people".

so, please do not answer noob questions in this thread and try to answer them in the other one.

some think that they have a better chance of getting an answer here and that causes the cluttering.

if they only get "wrong thread" as an answer, they will learn eventually.

"extrapolation of predicted results combined with humanized responses"

let's implement this feature together :)
[Galaxy S III Original Android Development] abelle_abelle:
Do i still need to set all those settings in op

or if i just run those battery script then its not needed ?
[Galaxy S III Original Android Development] bbeanss:
When I have been using this Kernel on CM10 and AOKP, I've been experiencing serious battery drain issues and when I have been charging my phone it takes a strenuous amount of time to charge up (Around 10 hours to hit 100% from around 20%) I don't know if this is an issue with Siyah or JellyBean but I've had to revert to CM9, is there any possible fix I could use, or is this something that we have to wait for in the future updates in JellyBean?

Thanks in Advance and my apologies if this comment is in the wrong thread.

Beans
[Galaxy S III Original Android Development] danarama:
I know the advice is for freezes and lock ups to try another kernel however I would really like to help contribute, particularly since many cannot reproduce it. What sort if logs / info would actually help troubleshooting this issue? Could someone recommend a minimum data set for reporting this?
[Galaxy S III Original Android Development] MuertoKo:
Ask in general Thread, this is development Thread please. GM said so just ONE post before yours, read, please.

On post 2 OP stated that "battery drain" is not a correct reporting, if u wanna report this like this please, attack logs, more information, BBS screenies, but not like this, this won't help fixing anything as GM can't work with words but yes with logs.

Some pages ago droid and GM said HOW and WHAT could be posted here. Please do some searching on firsts posts about this stuff, at least logcat or BBS (on drain issue) are helpful, but people usually don't attack a single log... imagine how this feels...

On topic again: I was able to reproduce some "lag" or kinda while having 7 - 8 pages open on stock browser, this lag actually was music jumping, not lag. So I guess this can't be solved by general kernel tweaking but with memory sticking the music player. Will try setting on poweramp the setting to keep music alive, and if I'm able to reproduce the hickups again I'll post some logs about it just case (Needed to post something at least a bit on topic after all this OT but worth posts, srry)
[Galaxy S III Original Android Development] danarama:
I'm aware of the posts you mention but they do not answer this question.

My lock ups are for 10 seconds then gone for hours so a logcat will not help since a logcat runs forward from the command, so can only capture AFTER the event. I'm more looking for something like last_kmsg or a similar vein that is retrospective. Hence the question. We need to know what other logs are appropriate when the already mentioned ones are not
[Galaxy S III Original Android Development] MuertoKo:
I know there's one log that you can grab directly from computer, can't remember name or how though so kinda good idea maybe posting a "little" guide on how to report on OP? O.o Just to make it easy for new bug-reporters :)

If you can reproduce the 10sec. lags intentionaly (opening this this and this causes it) it could be easy for you to reproduce it and log it properly if someone tells us how to grab a proper log on a concrete event, is it the case? :)
[Galaxy S III Original Android Development] gokhanmoral:
v1.7b1 is up. ( http://www.gokhanmoral.com/)

please ask questions or help about dual booting in general section thread.

for now, you will have to flash the recovery to use 2ndROM utilities. you can also find the recovery in the same post in my blog.

I now have Samsung JB (as my primary ROM) + CM10 (as secondary) on my device.

the easiest way for now is :

1-) clone 1stROM to 2ndROM in recovery

2-) install new ROM

3-) don't forget to flash SiyahKernel v1.7b1 again if the ROM flashes a kernel

4-) use swap if you want

during boot, you will be asked to press home or volume down to boot the 2ndROM.
[Galaxy S III Original Android Development] danarama:
Yeah thsts another issue. The only commonality I see is that when the lock ups occur, data transfer is taking place (according to the icons) so I can't manually produce it.

Pre edit - actually just had it whilst attempting to look at the last_kmsg.

Symptom, root explorer screen went black, status bar remained visible. Long press home no response, power turns off screen and turn on ok until app relaunched. Also had this with chrome.

Last_kmsg updated so hopefully this dump helps

http://pastebin.com/wARCYPZn
[Galaxy S III Original Android Development] rodrigo_said:
Gokhan Thanks so much you do, just a question, not yet implemented the installation from SD CARD a SECOND ROM?

Greetings!
[Galaxy S III Original Android Development] shay2911:
I tried the new kernel and the new recovery there's seems to have a bug in the recovery : can't mount external sd card ..

I tried to reset recovery and reflash recovery using Mobile Odin

external sd mount not working
[Galaxy S III Original Android Development] gokhanmoral:
thanks for reporting. fixed and reuploaded the recovery.

external_sd works now.
[Galaxy S III Original Android Development] Chris_84:
No. Tried it and it don't work.

Throwing out of the window from my flying Ferrari killer S3 :P
[Galaxy S III Original Android Development] gokhanmoral:
as I have written before (it is also written in the blog post), some features are missing.

for now we have only basic features (clone, swap and delete) which are just enough to get dual ROM setup.

the others will be implemented in the upcoming versions.

I will enable only the ones that I have tested.

I have already implemented most of the other features but I haven't tested them thoroughly.
[Galaxy S III Original Android Development] GaryLiao:
How does it work?

Is there a specific reason as to why we need to install a different recovery (It looks like a modified clockwordmod one) in order to use 1.7.1b1? If dual booting isn't a requirement would it be possible just to flash the kernel using odin and skip flashing the recovery the recovery? Furthermore, how exactly does the dual booting work? Is the new kernel modifying the boot loader in any way?
[Galaxy S III Original Android Development] gokhanmoral:
you don't need to change the recovery if you want to use only the kernel without dual-booting.

and the kernel doesn't change the boot loader or any other partition, other than using some internal sd space.

cloning 1stROM to 2ndROM (available in the custom recovery) creates /sdcard/.secondrom and puts system.img in it.

it is the image of the /dev/block/mmcblk0p9 partition (1.5GB)

and since we have ext4 formatted data folder (/data/media) used as sdcard (fuse-mounted fake case insensitive sdcard), I keep data files in /sdcard/.secondrom/data folder which is bind-mounted to /data during boot if the ROM is 2ndROM.

all modifications are at kernel+ramfs level. no repartitioning or boot loader modification is required.
[Galaxy S III Original Android Development] Chris_84:
Thank you very much for that info! Sorry for this post but i´m outta thanks for today.
[Galaxy S III Original Android Development] rodrigo_said:
Thanks gokhan likewise my idea was to have stock rom first and supernexus second.

Backup, install supernexus in first, clone at second rom to restore the first backup in the first rom and WOW! working!

Thanks and regards!
[Galaxy S III Original Android Development] crazbanditz:
The kernel will contain recovery as well?
[Galaxy S III Original Android Development] gger123:
Thanks dual boot works great just wondering if you have a link to stock Cwm recovery tar?
[Galaxy S III Original Android Development] Chris_84:
No you got to flash recovery separate.

Throwing out of the window from my flying Ferrari killer S3 :P

---------- Post added at 03:16 AM ---------- Previous post was at 03:15 AM ----------

Just look in Android original section. There you will find chainfires thread with original cwm recovery.

Throwing out of the window from my flying Ferrari killer S3 :P
[Galaxy S III Original Android Development] hellsgod:
Dual Boot was the big Thing i was waiting for, thank you Gökhan. 1st ROM CM10 2nd OMEGA 27. But I've a Problem with CM10 (cm-10-20121006-NIGHTLY-i9300), USB connection wont work. android.process.media have a FC when i plug in the USB cable. Made a Full Wipe and flashed again. Problem persists. I've attach a log as soon as my phone have downloaded all my apps.

Anyone else facing the same problem?

edit: log uploaded

hells
[Galaxy S III Original Android Development] Deus_ex11:
Gokhan is a genius

Ok I have cloned the stock Samsung JB on my S3 to the '2ndROM' and its working brilliantly so far. I have yet to try CM10 so this will be the perfect way to try it and keep my current rom ready to use just by rebooting. Its amazing.

Just a couple of reservations in the recovery. The swipe gestures are a bit dangerous. I nearly did a factory wipe and done a unintentional backup by swiping the wrong way. Swiping right usually means back for me but its the other way round in this recovery. You have swipe left for back and swipe right for select. Selecting with a swipe is pretty dangerous too. A feature request, would you be able to compile a Team Win Recovery as a alternative?

I hope to make the most of dual booting to try different custom roms as I want to keep a stock rom handy for compatibility. Thanks Gokhan for this killer feature. Samsung should be paying you for adding better functionality to their mobiles. I will be making a donation as soon as I can.
[Galaxy S III Original Android Development] bala_gamer:
@gokhan

Thanks for bringing back the swipe based recovery again, loved it with my s2.

Gokhan,as the existing hidden partition is used for cache, so in the near future in case if we need an option for third boot is it possible to create both system.img and cache.img in sd card for third boot?

《swagged from aokp》
[Galaxy S III Original Android Development] carlos67:
A question for all those people who wish to dual boot Sammy jb (omega, wanam etc etc) with cm10.

If installing cm10 over sammy JB it breaks NFC, bluetooth and wifi according to the cm10 thread. Their solution is to first install an ICS rom and switch on NFC/wifi/bluetooth then off and then back on and then install cm10 over that and it fixes the problem ( weird, I know but true). Anyway, my question is, bearing this in mind, what is the best way to get a fully working sammy JB dual booting with cm10 without the NFC/wifi/bluetooth being broken on the cm10 Rom?

Btw....wonderful work from the fingers of a genius.

Edit: nevermind, figured it out.

First install new Siyah kernel with new recovery.

1. Backup current Omega v27 (or wanam if that's your thing)

2. Install stock ICS over Omega v27

3. Do the switch on/off/on thing with nfc/wifi/bluetooth

4. Install cm10 over the top (1st rom slot remember)

5. clone 1st Rom to 2nd rom (cm10 now 2nd rom)

6. Restore Omega v27 to 1st Rom

7. Cigar and big grin ;):D
[Galaxy S III Original Android Development] :
Hi gokhanmoral,

About the CFS tweaks.

You removed it from STweaks, so my question is the CFS tweaks you use actually are the Samsung default, Linux kernel default or from the Thunderbolt tweaks?

Depend on your repply, but for example if you use Samsung default, is it possible to have the values for Linux kernel default (and vice versa)?

No need the Thunderbolt tweaks, or at least the tweaks you used in the previous kernel version.

I think you know what I mean, it's for the values for:

Thanks in advance ;)

EDIT: or simplier, the 3 previous values for Samsung, Linux and Thunderbolt tweaks, with each values for each configuration it will be perfect and I'll manage with it ;)

:)
[Galaxy S III Original Android Development] :
Arf, I can't change the values with both inid.d script or SysCtl interface, it remains the "stock" values coded in your kernel...

Any idea, or allow the user to modify these values via init.d script or SysCtl interface? Or re implement these settings in STweaks?

Thanks;)
[Galaxy S III Original Android Development] gokhanmoral:
check /res/customconfig/actions/cfs-tweaks file. I did not remove the action script, it is still in ramfs. you can copy the contents to an init script and apply.
[Galaxy S III Original Android Development] gokhanmoral:
I recommend you to buy an iphone.
[Galaxy S III Original Android Development] NoEnd:
Just did that again with the default governor and the phone went off, I needed to pull the battery out to restart the phone

---------- Post added at 02:04 PM ---------- Previous post was at 02:03 PM ----------

hehehe :D that's funny bro