yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] trein91:
Same issue. I was already on xxemc2. Had perseus 34.3. Colors became even more washed out after flashing 35
[Galaxy S III Original Android Development] The Broken:
Back to v 34.1 and all is fine again. So I'm pretty sure it's a kernel problem.
[Galaxy S III Original Android Development] psyntific:
Check the register hook
[Galaxy S III Original Android Development] trein91:
Checked on both versions. I won't make such trivial mistakes -.-
[Galaxy S III Original Android Development] Fienman:
I think the problem these people are having with these colors is because they had never properly activated the calibration.

You are not supposed to tick toggle factory settings. It overrides Andrei's calibration with factory settings if you tick it.

Similarly ticking chroma saturation turns it off.

The only thing that was ON when you ticked it was temperature control.

I think when you guys were on 34.3 you didnt turn all of these calibrations ON properly.

This or there is something wrong with MC2 firmware. I m on MB5 and everything is fine here.
[Galaxy S III Original Android Development] Kyle07:
I'm on MC2 and everything seems fine. Colouration is unchanged according to me.

Excellent update once again, Andrei. Thank you.
[Galaxy S III Original Android Development] habylab:
New version working very well. Any chance in terms of audio for notifications to be muted when on a phone call? Very distracting having them come out of the main speaker, as I always have my phone on vibrate.

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] RedDevils88:
i have an issue here.

i set my phone's screen time-out to 1 minute. but somehow, it will reset itself to 10 minutes. this is so annoying. I don't know what has caused this. any idea? THANKS
[Galaxy S III Original Android Development] www1:
I have a small problem with this kernel and Bluetooth.

The phone can't connect automatic with associated devices.

I have to enter in bluetooth settings and select the device.

I have this trouble only with this kernel.

Anyone have the same problem?
[Galaxy S III Original Android Development] habylab:
I don't have this issue, so try a fresh wipe with backup etc.?

Screen on toggle used, by jkay? I had that a while ago.

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] iridaki:
You are using JKay framework. Reset your Deluxe Settings configuration and see if the problem is still there.

Search and report your issues here.
[Galaxy S III Original Android Development] psyntific:
Backup jkay and reinstall deluxe settings... for the screen on time resetting to 10

I'm in mc2.. the colors are perfect and the kernel just keeps getting incredible... thanks a ton Andrei
[Galaxy S III Original Android Development] RohanAJoshi:
Latest built is excellent...

Realy thanx for that Sir..

.

But on previous build and latest build I found one same bug with audio, also tried with 2 roms..

.

Bug is, force mono downmix is automatically activating some times when headset is connected. Headset giving mono output.

But in stweaks, its remans unchecked..

This means mono is off as per stweaks settings, but actually its on.

.

If I cheked it, headset output becomes stereo..

Its acting opposite to stweaks. .

.

Here debug info from wolfson.

.

Audio version: Perseus 35

WM8994_AIF2_CONTROL_2: 16384

WM8994_LEFT_OUTPUT_VOLUME: 375

WM8994_RIGHT_OUTPUT_VOLUME: 375

WM8994_SPEAKER_VOLUME_LEFT: 377

WM8994_SPEAKER_VOLUME_RIGHT: 377

WM8994_CLASSD: 356

WM8994_AIF1_DAC1_EQ_GAINS_1: 44063

WM8994_AIF1_DAC1_EQ_GAINS_2: 31680

WM8994_AIF1_DRC1_1: 132

WM8994_AIF1_DRC1_2: 647

WM8994_AIF1_DRC1_3: 232

WM8994_AIF1_DRC1_4: 528

WM8994_OUTPUT_MIXER_1: 1

WM8994_OUTPUT_MIXER_2: 256

WM8994_OVERSAMPLING: 3

WM8994_FLL1_CONTROL_4: 229

WM8994_LEFT_LINE_INPUT_1_2_VOLUME: 284

WM8994_RIGHT_LINE_INPUT_1_2_VOLUME: 284

WM8994_INPUT_MIXER_3: 144

WM8994_INPUT_MIXER_4: 16

WM8994_AIF1_DAC1_FILTERS_1: 512

WM8994_AIF1_DAC1_FILTERS_2: 2832

output_type:0

is_fmradio:0 is_eq:1 mic_level:28
[Galaxy S III Original Android Development] BUFUMAN:
i am getting reboots (loop) after a missed call.

Device getting real hot.

Never had this before dude. I am using your kernel since december.

Regards

Gesendet von meinem skz_tenderloin mit Tapatalk 2
[Galaxy S III Original Android Development] psyntific:
did u upgrade from mr2 to mc2?
[Galaxy S III Original Android Development] jimbo77:
I'm experiencing the same issue in latest build (Perseus 35)
[Galaxy S III Original Android Development] AndreiLux:
Just plug the headphones out and back in for now.
[Galaxy S III Original Android Development] alberber:
Hey mates,

is it a good idea using zram and cache swap at the same time?

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] Erahgon:
I think it's a good idea. Overall, when compared to each on their own, you get a performance boost/better multitasking.

The only disadvantages are there due to their individual virtues and don't need consideration wrt your question (I mention it so as to cover all my bases). zRam eats up actual RAM and hard and cache swap is slow wrt actual RAM.

Sent from the present, which is now in the past.
[Galaxy S III Original Android Development] drakester09:
Consider this post before enabling cache swap.

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

Zram is harmless though. Wouldn't be active by default otherwise. :)
[Galaxy S III Original Android Development] trein91:
Oh sweet go on assuming again. I already checked all the proper settings. Everything but the toggle factory settings and chroma is ticked. And please check the latest one yourself, there is no checkbox for chroma anymore, just sliders. I'm gonna say this again. I have exactly the same configuration for both versions and yet they output different results. (Colors being more washed out on 35 than 34.3)
[Galaxy S III Original Android Development] digitalface:
@AndreiLux, would there be a possibility of adding a 'default' button to each tab on STweaks so we can individually default the settings rather than the global default that currently exists?
[Galaxy S III Original Android Development] Fienman:
What part of my post looks like an assumption????

I am on the latest kernel and my colors are normal.

I think i have a special version of the kernel for me as i have a checkbox for chroma.

Right???
[Galaxy S III Original Android Development] tinti93:
This is my favourite kernel, but when i turn on the speaker equalizer in the extweaks and using mic, then the eq for the speakers are turned off. :(

Sorry for my english.
[Galaxy S III Original Android Development] istillmyself:
uik..for me emc2 colouration is unchanged :) perfect like before
[Galaxy S III Original Android Development] woof123:
The colors are fine for me too...the only thing i do is checking the two usual options without tampering with sliders.
[Galaxy S III Original Android Development] dr.ngk:
To sum it up what would be the best settings for the screen..especially regarding white temperature
[Galaxy S III Original Android Development] drakester09:
Master sequence checked and that's it - it's the calibrated profile.

On another topic, I sent a PM to Andrei with my findings about zram and lagging, I'm posting this here as well:

Andrei's reply about this:

I would advise anyone experience lags, to install ZRAM status and check the usage when the lagging ocurrs (it takes patience), so we can verify this more thoroughly.
[Galaxy S III Original Android Development] alberber:
Oh... I don't wanna break my phone... :( But it goes well with zram and cache swap, so I'll think about it. Thanks for the information

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] The Broken:
So..?
[Galaxy S III Original Android Development] AndreiLux:
So there's currently a total of 2801 users of version 35 who don't have this issue. I'm playing a wide variety of codecs including 40mbps FHD streams or Matroska embedded high profile 5.1 with DTS audio, all without issues. On top of that I didn't touch video decoding in the last version.

Just a notice to all users: I'm getting an insane amount of PM traffic every day (See three posts above...), some useless requests or inane questions, which I ignore and don't respond to (I'm not a helpdesk), and some constructive stuff to which I do reply and help out.

I read all your posts and rarely miss a topic or concern , but I'm not going to reply to every single thing out there. So if I'm ignoring a post it's because 1) it's stupid or nothing worth replying to 2) I already know about it and acknowledge it 3) it's not repeatable behavior or an issue of the kernel. 4) I'm sleeping or away/busy.

In case 2, it will be fixed by a hotfix/minor version of the kernel, as has happened many times in previous releases.

So I would please ask people to refrain from repeated reposting of questions. And don't take it personally, I'm doing it for my own sanity.
[Galaxy S III Original Android Development] Pietrone94:
For me all good: play videos in all format (also HD and FHD) with video player, mx player, quickpic....all works well :)

♣♧♣Inviato dal mio ★S3★ con Tapparitappatalk♣♧♣
[Galaxy S III Original Android Development] habylab:
What was it before?

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] BUFUMAN:
No i am @foxhound 2.4 (mb5)

Did a full wipe yesterday everything. I think the problem is zram. My cpu values and co. are nearly stock.

How can I disable zram? My phone doesn't like zram

@andrei good work dude I love your kernels. The features are amazing.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] jeebspawnshop:
You might wanna put this on the first post in BOLD, or something.
[Galaxy S III Original Android Development] cyberspaceguy:
With last update my microphone doesn't work well... Who calling me doesn't hear me good....
[Galaxy S III Original Android Development] nfsmw_gr:
+1
[Galaxy S III Original Android Development] idan1388:
It happens to me as well.

AndreiLux, can you please let us control on the vibration?

or just set the stock values.

I love your kernel! this is the only problem I have.
[Galaxy S III Original Android Development] agusdallalba:
I also have problems with the vibration. But it's totally random, and very hard to reproduce. It never happens to me while the screen is on or there's a partial wake lock held. That might light light up the issue a bit. I don't think we need controls for the vibration, this looks like a bug (and a somewhat critical one, I occasionally miss a message because of this).
[Galaxy S III Original Android Development] KS_Ho:
Yeh this problem has been reported quite a few months ago, happens on my phone too, seems to happen on this kernel only but so far users have just put up with this problem :p
[Galaxy S III Original Android Development] The Broken:
From what I've read after my post about that I know that there are many user with that problem.

But judging from what nfsw_gr said: ''Well,it happens to me times to times but it's not a hardware or a kernel vibration issue,atleast for me...this happens because the device lags this time and the lag cuts the vibration into smaller vibrations...'' So nothing to do about it than keeping your device awake all the time I suppose. Which worked, I did that for a week or so but I had to recharge my battery almost every 5 hours..

And judging by what Andreilux just said, ''it's stupid or nothing worth replying to''.

You'll get used to it trust me lol
[Galaxy S III Original Android Development] sherlock5545:
Is it just me or STweaks takes long to load? Otherwise, the kernel is awesome, loving the Master Sequence calibration. Awesome job.

Sent from my GT-I9300
[Galaxy S III Original Android Development] jimbo77:
To all of you having vibration issues, have you tried to lower the vibration intensity under Settings>sound>Vibration Intensity??

It might just help with your issue
[Galaxy S III Original Android Development] The Broken:
I haven't,I like the string vibration. But I'll try, thank you for the tip!

EDIT: didn't work
[Galaxy S III Original Android Development] Olioaglio:
Stweaks loading time depends on how much tweaking options the kernel offers. And as we all know, Perseus kernel offers a loooooot :D of those and still grows with every new version ;)

That's the reason for loading time.

Cheers, Olioaglio

Sent from my SGS3
[Galaxy S III Original Android Development] presh:
under setting and the battery menu is mediaserver a very active app? i had a similar problem on the same rom. mediaserver was keeping my phone at 100% use.
[Galaxy S III Original Android Development] BUFUMAN:
No dude i disabled that with media scanner disabler.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] grzesdroid:
zram may result in deterioration of the battery stats?

SGS III / Grisza Monster Beam v7.0 / Boeffla 2.10 beta 2 / JKay deluxe framework 14.93.1 / JB Domination (edit by me) / Tapatalk 2 / Swype
[Galaxy S III Original Android Development] BUFUMAN:
I have to correct myself. Its always after the second missed call. I am testing now and will provide a logcat.

EDIT:

no chance to provide it. after second missed call the hole thing messed up!

its something with zram and my phone......

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] habylab:
Because stweaks is a craply compiled app that is the only option really for the amount of settings we have, which we are thank full for. Andrei's words, said it needs a rewrite.

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] alberber:
Is it just me or the new fading led feature wastes more battery than usual? I lost 2% in one hour and I usually lose 1% per 1:30 hour.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] STAticKY:
I believe it because the cpu needs to turn the led on and off. Over and over. Wheras for a solid led the cpu sets its state through the driver then leaves it. Correct me if im wrong
[Galaxy S III Original Android Development] AndreiLux:
The LED is controlled by a separate microcontroller which is programmed to shine/blink in whatever behaviour you tell it to until you tell it to stop. This is completely separate from the CPU or anything else in the phone. There is no raised battery drain except from the power of the LED itself if you make it shine longer, and that's only valid when it's actually on during a notification.

I should add that there are two methods of the notification blinking taking place; one is the stock Samsung controlled behaviour and one is application userspace caused notification. Any third-party app controlling the LED will use the latter. If you turn off the "LED Fading" checkbox it will also relinquish the rest of the controls to complete userspace behaviour, just in case somebody will report such a problem or misunderstanding.
[Galaxy S III Original Android Development] jinosong:
A feature that would be awesome would be the ability to control the vibration. I would be ecstatic if we were able to mimic the haptic feedback vibration from the Nexus 4. The feedback and vibration touch of that device is amazing.
[Galaxy S III Original Android Development] STAticKY:
I see. So my reason for saying that was based on something i read in this thread here.... http://xdaforums.com/showthread.php?t=1714354&page=156

post #1560

I just realised we were talking about blinking one same colour and not alternating colours like i was thinking and read in that thread. Sorry
[Galaxy S III Original Android Development] AndreiLux:
He's talking about things on a higher level than the kernel, that's not my issue.

You can make the LED blink in alternative colours without intervention of the CPU or driver, as you can program each RGB LED with a different pattern and simply make them blink asynchronously from each other with a starting delay.
[Galaxy S III Original Android Development] Obagleyfreer:
Is it just me or has anyone else not noticed any difference when changing the brightness values of the LED?

I can put both sliders right down to 5 or right up to 255 and it is always the same brightness...........

Any ideas?

As always another AWESOME kernel update! Loving it!
[Galaxy S III Original Android Development] tisazalay:
Yes. At first it looked too bright. I lowered the less brightness to 1 and the high brightness to 5. I rebooted and it catched on. Now it looks dim which I want. I tend to leave the phone unattended for periods and as Andreilux stated, Having the led on drains more battery. Hope that less brightness =less energy.
[Galaxy S III Original Android Development] Obagleyfreer:
That's intersting, it makes no difference at all on my phone (i9305).

Could be because I am running Jkay Framework though and that also has LED settings, maybe they're clashing......?

At least it's not a bug though :)
[Galaxy S III Original Android Development] Cy4n1d3:
Great work so far, reminds me of the good old Talon kernel on SGS1 :)

I'm looking forward to the forthcoming developments to this, really like it so far.

On latest JB stock rom (LI8).
[Galaxy S III Original Android Development] Tenacious:
Heaving some weird behavior with touch keys on v21 sometimes they don't respond to touch and other times they are detecting touch even if I'm not touching them. Log http://db.tt/yEgFsVBK Time stamp from 23:30 onevards.

Also heaving some keyboard freezes when typing in opera mobile rom foxhound 1.4.4 LH3
[Galaxy S III Original Android Development] AndreiLux:
Yes, sorry, but it has a bug in it. Maybe I should remove 21. I don't see any reason anymore to support ICS. Update to the new Foxhound and use the JB kernel.

Also: 22.3 up. I couldn't figure out what the hell was wrong in the init sequences, so I just ripped it out and replaced it with the classical one. All the people with ROM problems should now have the kernel working.
[Galaxy S III Original Android Development] EViollet:
Hi.

Version 22.3 now works with Omega 26.1.

Thanks.

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] sak500:
Yep just tried it. Thanks AndreilLux.

Edit: One thing i noticed, Stweaks from siyal kernel still showing and can't delete it.

Edit #2: NVM froze it with TB as it was showing part of system file.
[Galaxy S III Original Android Development] andip71:
You need to delete STweaks by either directly deleting it from /system/app with a root file manager, or you can also delete it with Titanium Backup.

Also, do not forget to delete folder /data/.Syiah if you want to clean it up properly.

Andi
[Galaxy S III Original Android Development] AndreiLux:
You don't really have to clean the Siyah stuff if you don't want to, STweaks just won't do anything that's all. Same with the remnant folders.
[Galaxy S III Original Android Development] mariosraptor:
Great job Andrei. Reinstalled and everything seems to work great.thanks again.
[Galaxy S III Original Android Development] :
flashed and working on official XXDLIB :) as expected (kernel is identical to XXDLI8, thanks to gokhanmoral).
[Galaxy S III Original Android Development] fosseperme:
This kernel support undervolt with SETCPU?
[Galaxy S III Original Android Development] mariosraptor:
Without even making a full charge the kernel is idling very low in battery consumtion. Again great work Andrei.
[Galaxy S III Original Android Development] AndreiLux:
Huh?

Yes.

I also recommend against any scripts besides clock/voltages changes. The governor is set up already to what I think is optimal settings.
[Galaxy S III Original Android Development] :
LOL, sorry.. was replying to 2 threads at the same time so I don't know what I wanted to say :p (what i meant is that XXDLIB kernel is identical to XXDLI8, just compiled at different date) soorry :)
[Galaxy S III Original Android Development] jayden2009:
Question...can i use youre kernel with official JB ?
[Galaxy S III Original Android Development] :
yes (alpha 22 and above)
[Galaxy S III Original Android Development] fosseperme:
What differences in undervolt with Siyah for JB?

actually i use siyah for undervolt my s3 with setcpu.
[Galaxy S III Original Android Development] AndreiLux:
Ah alright :)

There is no differences, both support the "standard" interfaces and are compatible with SetCPU.
[Galaxy S III Original Android Development] jayden2009:
Damn flashed kernel wtf look at this :D

This kernel is sooooooooo fast thank you very much!!!

Btw this is my free ram with kernel

Verstuurd van mijn GT-I9300 met Tapatalk
[Galaxy S III Original Android Development] gee2012:
Can i oc/uv with NSTools?
[Galaxy S III Original Android Development] jayden2009:
I used set cpu :)

Verstuurd van mijn GT-I9300 met Tapatalk
[Galaxy S III Original Android Development] tisazalay:
I also use jkay but on i9300. Even more I enable led with screen on. I do believe that behavior should be more widely noticed. Because of it not seeming to change the brightness, at one point I thought that maybe it was referring to the brightness level where the led shined with more or less intensity but after some time I got it to simply lower the intensity regardless of the surrounding light. It takes a while.

I don't know what is the lux level where the the kernel or led circuit decides to shine with more intensity and maybe im wrong but perhaps the proximity sensor has to do also. Before this kernel if you placed your thumb on the proximity sensor the led intensity varied. Maybe AndreiLux can shed some light on both aspects (the surrounding light to decide shine bright and the proximity sensor roll)... I don't see them on previous posts or the OP.
[Galaxy S III Original Android Development] AndreiLux:
If you are using a user-space app to control the LED then the brightness is controlled by that and the kernel brightness controls are overwritten. Samsung uses separate controls than the usual userspace apps, so as far as those are concerned, everything works as it should. Brightness is also only updated on a new LED event, I'm not refreshing the LED state it's already in (Who the heck keeps the LED on while screen on?).
[Galaxy S III Original Android Development] STAticKY:
I do :) i find it quite useful in certain situations. Like if im playing a game and dont get an event popup i can quickly tell what type if info has just arrived onto my phone.
[Galaxy S III Original Android Development] DirkStorck:
Hi Andreilux. Woould it be possible to add a switch in STweaks that turns the LED on? That way I could test if how I like the behavior that I configure :)

Send from my Omega ROM powered SGS3 :)
[Galaxy S III Original Android Development] morg01:
Think that's a great idea, +1

Sent via courier pigeon
[Galaxy S III Original Android Development] trh1341:
Quick question..im kinda new. And this was linked in an att galaxy s 3 thread..can I use this kernel on a touch wiz 4.1 rom
[Galaxy S III Original Android Development] drakester09:
I don't know who did link you here but this kernel and forum is not for your device.
[Galaxy S III Original Android Development] trh1341:
Thank you. Sorry anout that

Do you know if there is one for the d2att? I tried to search but it seems to be down.
[Galaxy S III Original Android Development] papakaliati:
When i leave the Phone to charge overnight i find it switched off in the morning. Its really annoying cause i lose all alarms :S Anyone knows whats up with that? I didnt really played with the power options on Stweaks screens. Could really use a help there^^

Also its not the charger , ruled this out already.I have to add that i also had the same problem with cm10.1 with Stweaks.
[Galaxy S III Original Android Development] gegode:
thanks for the kernel , Andreilux

works great :)