yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Erahgon:
A bit of background, and feel free to correct me if I'm wrong:

Say you have a bad adapter/cable which provides fluctuating power to charge the phone. The phone keeps lowering the power supply, until it finds a stable enough current draw. Now, the phone reduces the current draw further by a 100mA, just as a precautionary measure, to be well within the stable zone.

"Ignore safety margin" tells the charger not to reduce the current further by 100mA after finding a stable draw. Thus, it provides a slightly higher charging rate than it would have otherwise.

"Ignore unstable power" tells the charger not to care if the current is unstable, and draws power at full capacity whenever available. This gives a much higher charging rate, usually.

Now, for the risks:

Both these options do not endanger the phone itself, nor the battery, but does pose a threat to the charger, as confirmed by Andrei sometime ago.

I use both these options, as the charger I use at work does not work when I select just the "Ignore safety margin" option. I do suggest that if this option works for you, just use that one, as it is the "safer" of the two options.

Hope this helps clear some confusion. Feel free to correct me if I'm wrong.

Sent from the present, which is now in the past.
[Galaxy S III Original Android Development] nfsmw_gr:
Thanks man. :)

One last thing,sorry if i'm too much trouble...

I've lost my charger and i charge from my pc's usb 3.0 port which is about the same speed as the charger i had...

Will i have any issues with the usb port?

The computer is a high end i7 gaming machine and most of the parts if not all are high quality ones. :)
[Galaxy S III Original Android Development] invinciblecc:
Nope won't be a problem if it is Usb3.0

But still be sure it's 3.0 and then u can set the usb charge current to 1000

Worst case scenario only cord gets damaged but that won't happen
[Galaxy S III Original Android Development] tisazalay:
A possible bug...

Hi I think there might be a bug in the kernel regarding WiFi, if I set it to Only When Plugged In (in advanced) to keep wifi during sleep, it never turns off even with the phone on deep sleep. I've noticed the behavior for a while now but maybe its only me, can someone else confirm if it's working fine or not?

Any suggestion?
[Galaxy S III Original Android Development] iridaki:
I know for a fact that it's not integrated in my country's laws (Greece), so that pretty much makes your argument invalid.

The fact that it should have been, is a whole other discussion. Yes, a consumer could sue the government for not applying the EU directive but, again, this is taking it too far and missing the point, which is to have your phone fixed.

"Lately"? :confused:

Each country has its own law system, the European Union doesn't make or forces laws in such a direct manner, so to speak.

Rest assured, I read a lot and, what is more, I use my brain to criticise what I read. Secondly, I am not a moderator in this section and my post was not intended as a moderating act.

You mean, official "directive" texts.

So yes, indeed you are wrong dear.

Even if I were responsible for this section, and I'm not, I wouldn't mod your post. If you have problems with moderation, take it to the proper channels.

Andrei has stated it's completely safe for the phone and I confirm that I haven't had any issues whatsoever. Phone charges a bit faster now. But it all depends on the charger, the cable and the power source you use.

iR¡D@k!* ? from i9300 via Tapatalk 2
[Galaxy S III Original Android Development] Siberian Tiger:
FTFY :silly:

Sorry for OT ;)
[Galaxy S III Original Android Development] Yank555:
Here are the countries that have implemented the directive in their national law as required by EU :

Belgium

Bulgaria

Czech Republic

Denmark

Germany

Estonia

Ireland

Greece

Spain

France

Italy

Cyprus

Latvia

Lithuania

Luxembourg

Hungary

Malta

Netherlands

Austria

Poland

Portugal

Romania

Slovenia

Slovakia

Finland

Sweden

United Kingdom

Since you read that much, you should have seen that list by clicking on the 3rd link I pointed you to.

"Lately" was pretty ironic, EU directives "must" be implemented, as such they are imposed on each member state, hence those decisions are taken at EU level and not left for each member state to decide, so national power is lowered in favour of EU level.

No I really do mean

national law text references

, here is for your country :

This you would have seen clicking on "Greece" once you were on the page pointed to by my 3rd link.

I'm sorry I can't read greek, but I suppose you should see that it has in fact been integrate in your national law, applicable on 17/06/2010 (pretty late I agree as it's less then 3 years ago, but still, it's implemented in your country as well by now).

If that still is not enough to prove you wrong, I don't see how to help you on this.

But it absolutely is your right to "not claim your rights should your S3 die by SDS".

JP.
[Galaxy S III Original Android Development] xHausx:
And, back on topic please. :)

@Yank555 I don't know what issues you have with AndreiLux, but whenever you post here drama always seems to follow. Do not post in his threads anymore.
[Galaxy S III Original Android Development] Yank555:
I don't see why I can't post in this thread, as long as what I post is correct ?!

But you can maybe point me to some rule that prohibits this ?

JP.
[Galaxy S III Original Android Development] xHausx:
Your posts contribute nothing to the development of this kernel and only serve to stir up discontent. As I said, I don't know what happened between you two in the past but it stops here.

If you wish to continue discussing this please feel free to send me a private message as this is not the appropriate place for it.
[Galaxy S III Original Android Development] nfsmw_gr:
Oops,forgive me!

I didn't know. :)
[Galaxy S III Original Android Development] JustArchi:
@Offtopic

Sorry but as long as users are asking questions (offtopic questions) there is nothing wrong with answering them. Either users should totally don't ask non-related to kernel questions or any other replies to them shouldn't be considered as offtop.

@Ontopic

Great work on LED Andrei. Every next version is even better than the old one :).
[Galaxy S III Original Android Development] xHausx:
This is the correct one. A certain amount of off-topic is overlooked if the OP is okay with it, but when it becomes disruptive or counterproductive then it's gone too far. This forum is for sharing things you've developed or are developing first and foremost. All other conversations should be taken elsewhere.
[Galaxy S III Original Android Development] invinciblecc:
Well

As long as users are asking questions in the wrong thread it mustn't really be a problem replying to then and since I don't think anyone had a problem with Andrei posting in late thread of yank I don't think why it should be the other way around

And regarding usability of discussions as far as I know yabk usually answers questions doesn't start an off topic discussion

Instead of asking him bot to post u should ask the user who actually posted about his sds scenario to post on sds thread

Regarding this subject Andrei is not here now but he too was seemingly interested in discussing this and he's the one who created the post

Regarding yanks posting in this thread causing problems

Please don't mind my saying but is his becoming a personal agenda of xda against yank or something ????

With all due respect Sir if it's not against rules then shouldn't be a problem right ????
[Galaxy S III Original Android Development] tisazalay:
Maybe the law stuff ended and someone can tell me if it's a kernel bug or not.

Thanks.
[Galaxy S III Original Android Development] invinciblecc:
Check the wifi state setting via extended settings by typing in dialer
[Galaxy S III Original Android Development] xHausx:
Users asking questions in the wrong thread is a problem and shouldn't be encouraged by people answering them. A polite reminder to search for the answer or ask in the Q&A section is all that's needed.

For any other questions about policy please PM me and I would be happy to clarify them.
[Galaxy S III Original Android Development] rlorange:
http://xdaforums.com/showthread.php?p=39650148

[APP][12/4/13]Zram & Swap Control [CACHE & PARTITION] V 2.4.1 FIXED 2.4!

Update: V2.4.1

Big improvements!

>> faster load new style

>> info popups and swap active data info button

>> fixed busybox issue... Basically only some versions of busybox support swap priority settings and my detection system was CRAP! So now if you have hard or soft swap already active and set zram to have both active. All active swaps are first switched off so zram can bev switched on first guaranteeing it has the highest priority OTHERWISE IT WON'T BE USED UNTIL YOUR OTHER SWAP IS FULL!!

this is complicated to please use the new "i" button to check swap status and report any problems with this... Remember if zram is active it should always have a priority of -1 or it won't be active until other swaps are full.

I hope I have got all possible combinations accounted for... Argh hurt my brain this one ;)
[Galaxy S III Original Android Development] Erahgon:
Yup, invinciblecc is right. Although, I did hear that the max safe current was 900mA. You may want to check your chipset's documentation on that one.

The USB charging is governed by a separate slider in STweaks (originally set to 475mA I think, which is the USB 2.0 default).

The "Ignore safety margin" and "Ignore unstable power" settings should ideally be irrelevant wrt USB charging, as the computer governs the output voltages to be stable and safe for the computer's chipset. The exceptions are, off of the top of my head, using a powered dock, or a USB extender/multiport with many connected devices.

Sent from the present, which is now in the past.

---------- Post added at 12:14 AM ---------- Previous post was at 12:12 AM ----------

This is some great stuff! Kudos! Thanks a lot!

Sent from the present, which is now in the past.
[Galaxy S III Original Android Development] nfsmw_gr:
Thanks for this,i've already upped the max limit to 900mah for usb. :)

Anyway,i'll give this a go and post back the results.

Thank you all guys! :highfive:

EDIT: P.S. I'm limited to 8 thanks per day,sorry. :(
[Galaxy S III Original Android Development] invinciblecc:
If ur on usb 3.0 u can set the voltage to 3000 but not on usb2.0 it will fry ur cord on 2.0 that too eventually not like bammmmm so u can set it to 1000 I'm quite sure just make sure u don't plug it in usb 2.0 .....

Hit thanks if I helped
[Galaxy S III Original Android Development] c0manche:
Brilliant Kernel only problem I have with it is it can lag with zram activated seems to happen when kernel swaper kicks in to free some memory.

Also getting bitten by the mono downmix bug (mono downmix inverted after seleting it once in stweaks) now have to switch mono downmix to on to get stereo sound

Only slight problems I have found so far
[Galaxy S III Original Android Development] invinciblecc:
Zram doesn't cause lags increase ur minimum frees lags will be gone
[Galaxy S III Original Android Development] offgrey:
Not a dev or knowledgeable on coding or anything like that... But I think Andrei mentioned something about how the Zram feature causes memory leaks which then lead to lags? He actually said a few pages back he's thinking about dropping the feature entirely. Idkkkkk.
[Galaxy S III Original Android Development] nfsmw_gr:
That is correct,but this will only happen when you manage to fill you ram for a long time so that zRam too will get saturated.

If your low memory killer values are decent you'll most likely be fine. :)
[Galaxy S III Original Android Development] danarama:
So you're saying what? You need to set your oom to be the sum of what you actually want oom in RAM + size of ZRAM in order to prevent saturation?
[Galaxy S III Original Android Development] nfsmw_gr:
I don't get what you're saying but in my personal experience i think zram expands like a bubble inside ram.

So the more ram you use the more zram will fill.If you have decent low memory killer values ram you'll have more free ram and less zram i think.

Or at least have some free ram and avoid the lag.

Maybe this is wrong as a theory,but in order to get memory leaks when using zRam,zRam "partition" would have to be filled almost to max and i don't see this happening often(or at all).

Anyway this is what i'm saying.
[Galaxy S III Original Android Development] mattiadj:
Andrei is possible to tweak wireless charger value?? i can charge only at 499 with wireless charger!!
[Galaxy S III Original Android Development] eric-filth:
Andreilux. You are the guy, just it.

Your kernel is absolut amazing, following you since you started here.

Here my battery results, i did a lot modifications using stweaks without loosing a single performace. Quadrant 6028 and Antutu 15780

Enviado do meu GT-I9300
[Galaxy S III Original Android Development] Erahgon:
Wow! That's brilliant! Your phone's sleeping well I see.

Can you share some of your settings?

My phone sleeps well too, however it drains a lot of battery when it's awake and the screen is on. So I'm interested in your CPU (governor and hotplug settings in particular), and GPU scaling.

Sent from the present, which is now in the past.
[Galaxy S III Original Android Development] veteran_troller:
How did you achieve 7 hours screen on time??? More details please

Sent from my GT-I9300
[Galaxy S III Original Android Development] invinciblecc:
Ya actually Andrei did post it and i while posting it i thought i was posting in siyah thread

So sorry for wrong info and as of now yup zram lags on perseus
[Galaxy S III Original Android Development] eric-filth:
Yes, my phone sleep like a lazy :)

Sure i can share, i measure how processor works during 3 days doing basic things in android, results was half usage of processor compared with perseus default and without loose a peerformace and smoothness. But to this works like a charm you need check inside developer options - gpu rendering.

Here the profiles. Just put inside /data/.perseus then load the profiles with app made by droidphile or just edit /data/.perseus/.active.profile and type the correct name of profile you want.

Without undervolt - http://www.mediafire.com/?vjif43auiaahoor

With "universal" undervolt - http://www.mediafire.com/?wb380dd9dr9gtrk

Enviado do meu Nexus 7
[Galaxy S III Original Android Development] Nerobaxxy:
Your kernel is just AWESOME.

After 2 days with too little use:

View attachment 1880060

View attachment 1880061

View attachment 1880062
[Galaxy S III Original Android Development] habylab:
I remember the time I used to get 5 hours of screen time. Those were goooood times! I have no idea why I don't anymore, I just about get 2.5 hours now.

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] veteran_troller:
Same here...:(

Sent from my GT-I9300
[Galaxy S III Original Android Development] sherlock5545:
Same here, I get just about 3 hrs. I'll try some tweaks on STweaks now, hope it helps.

Sent from my GT-I9300
[Galaxy S III Original Android Development] The Broken:
You are kinda aggressive on the memory voltages, especially when compared to gpu and cpu, are you sure that it is safe?

Just to be sure I only lowered it by 50 mV instead of 75- 100 mV
[Galaxy S III Original Android Development] Olioaglio:
()

Thanks mate. Appreciate that you shared. Trying these settings now with additional small uv/oc at higher frequencies and some color tweakings (somewhat colder color temperature).

So far no problems. I see you pushed zram to 400mb? Did you have better experience than with default 200mb or even off like some others?

What effect/function has the gpu rendering setting? Its interesting that this is so important for overall performance.

Edit: achieving 16650 points in antutu with your settings giving me also a really good feeling in performance sight of view. So lets see how it performs battery wise.

Olioaglio
[Galaxy S III Original Android Development] sherlock5545:
You sure you can do that? I tried too, but you can't lower the undervolt of the memory by a bit, you just end up with the default values.

Sent from my GT-I9300
[Galaxy S III Original Android Development] The Broken:
I'm not sure.

I just read his profile and copied the settings I thought would work for me.

In his profile he is undervolting with 75 - 100 mV so I figured that when it is in his profile that way, it is not default anymore.

I must say that the settings are great, didn't have the time to test battery yet, but my phone is so much more responsive!
[Galaxy S III Original Android Development] W@r10ck:
Too bad i cant use this on CM10.1 Unofficial Build. Has anyone tested this on CM10 based ROMs?:confused:
[Galaxy S III Original Android Development] papakaliati:
If you are talking about the stweaks settings obviously they are the same. ALso you shouldn't be posting on a Stock Samsung Kernel thread about using it in Cm10.1 :S
[Galaxy S III Original Android Development] The Broken:
Feel free to test.....

Otherwise, read the op.
[Galaxy S III Original Android Development] W@r10ck:
Ooops my bad :cyclops: i thought i read somewhere that someone might have used this Kernel to CM10 based ROMS( maybe was just hoping someone did tried lol). I did used this from my previous Omega and NeatRom. I can tell that it was awesome :good:
[Galaxy S III Original Android Development] sherlock5545:
No, this kernel isn't compatible. You might want to try Siyah for CM10.1, but we are off topic now.

Sent from my GT-I9300
[Galaxy S III Original Android Development] MBurns2:
do you use stock stweaks values ? i'm unable to have such good battery life..
[Galaxy S III Original Android Development] TheMrcool212:
How can you get such amazing battery life? What ROM/ tweaks / governor are you using?
[Galaxy S III Original Android Development] dr.ngk:
Using erics settings..phone is much more smoother and snappy now.Will post the battery life after a full cycle...
[Galaxy S III Original Android Development] habylab:
Try Temasks build, for his kernel only if you like, essentially the same as this but tweaked differently in terms of CM.

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] eric-filth:
Yes is safe. Undervolt is always good, less hot too :)

I have my S2 undervolted about 2 years.

My Extreme settings is a lot more undervolted, my phone stay cold every time.

I keep 400mb zram because i doesn't have any kind of problem with that, smooth all the time.

I request to check gpu rendering because my modifications are based on that. Looking the difference in test i saw

1- checked gpu redering - less use of processor and more gpu

2- uncheck gpu rendering - more usage of processor

Thanks for sharing, here too, more responsive with excelent battery life.

Enviado do meu GT-I9300

---------- Post added at 01:59 PM ---------- Previous post was at 01:56 PM ----------

No, not stock values, i shared my profiles two post later than this screens.

Using my rom with my tweaks, pegasusQ

Thanks man, good use :o

Enviado do meu GT-I9300
[Galaxy S III Original Android Development] ruffnek786:
Have updated from Perseus-alpha33.3 to latest. I have now lost sound control so unable to increase volume bass etc via other apps like scooby control as modifications do not save. I am using anonorom v25.

I do not no what to do. I have played around with audio via stweaks but am at a loss big time.

Can someone please help as I know this is down to kernal and I had previously gone back to v33.3 to avoid loosing sound settings but I do wish to use the latest version and need to know how to sort out this volume issue and this is a user (me) problem and not kernal issue or bug with kernal.

Please help
[Galaxy S III Original Android Development] Olioaglio:
@eric-filth: after using your settings some time now with perseus 35.0, I can confirm: overall smoothness is AWESOME, indeed! Great work, dude!

Olioaglio
[Galaxy S III Original Android Development] papakaliati:
I agree that smoothness is great, but the settings are like the performance settings, cpu at 1400 almost all the time for no reason and all cores working for easy applications. Battery is bad for me
[Galaxy S III Original Android Development] eric-filth:
You applied gpu rendering inside developer options?

Because in my tests was totally different yours. Maybe is a lot apps in background.

Enviado do meu GT-I9300
[Galaxy S III Original Android Development] gee2012:
Thanks mate, but i wouldn`t advice using profiles for now in SetCpu.
[Galaxy S III Original Android Development] :
where did he say he is using profiles? maybe i'm just blind.. anyway, if something didn't drastically change it will not work with nstools. afaik :)
[Galaxy S III Original Android Development] AndreiLux:
May I ask why?

And NSTools does work for CPU undervolting/overclocking, I don't know why some people think it shouldn't.
[Galaxy S III Original Android Development] jayden2009:
Didn't used anything just overclocked it that's all as this kernel has standard the settings that andreilux has implemented :)

Verstuurd van mijn GT-I9300 met Tapatalk
[Galaxy S III Original Android Development] gee2012:
@tumult i didn`t say he was using profiles, just wanted him to be aware. read on a thread that profiles could cause problems. Not on this thread though but on GM`s, and that was a while ago :)

And for NSTools, not so familiar with this tool as i usualy use voltage control (extreme).

Your kernel is running very well so far, i used it for a few hours now and must say :good:
[Galaxy S III Original Android Development] JSale:
Which I/O scheduler are using to get such good I/O speeds?

if default, could somebody please tell me what the default is ? :P

Regards

Jack
[Galaxy S III Original Android Development] jayden2009:
Left everything as it is... Just oc to 1704 mhz that's all didn't had a freeze or reboot or something like that... I can only say wow this kernel combined with original JB is amazing :)

Verstuurd van mijn GT-I9300 met Tapatalk
[Galaxy S III Original Android Development] :
okey my bad then.. sorry (i though nstools is not using uv_mv_blah interface, whatever - was wrong).
[Galaxy S III Original Android Development] gee2012:
No problem mate, luckily there are no perfect people ;)
[Galaxy S III Original Android Development] :
well i should learn not to talk before i try something :p

thanks and sorry for off topic..
[Galaxy S III Original Android Development] gee2012:
Do 3 hail mary`s and sin no more :laugh:

---------- Post added at 08:48 PM ---------- Previous post was at 08:42 PM ----------

A bit off topic, but do you know how to raise the auto brightness values especialy for dark(er) enviroments?
[Galaxy S III Original Android Development] :
i know only that they talk about it in this thread http://xdaforums.com/showthread.php?p=29199005

as i haven't tried it, i'll stay quite this time.
[Galaxy S III Original Android Development] gee2012:
Thanks mate, but tried that and it didn`t work for me at least :(
[Galaxy S III Original Android Development] sak500:
Confirmed working with V27 Omega JB ROM which is based on official version which was released today.
[Galaxy S III Original Android Development] diego9016:
I have been using this kernel with CheckROM v5.5 for some hours. It has been running good so far
[Galaxy S III Original Android Development] dlads:
I'm presently on ics, looking to make the move to jb, liking the look of this kernel, has anyone tried any heavy games using this kernel on a jb rom? My apologies if this isn't the place to be asking, I play real racing 2 on the way to work every morning so I'd like to be able to play it.

At the moment, I'm on foxhound 1.4.3 using galaxsih, which is a real performance combo.

I know its early days so I'm not expecting too much but any feedback for heavy gaming whilst using this would be great if thats possible.

Many thanks.

Edit: thinking of using foxhound sliver with this.
[Galaxy S III Original Android Development] barondebxl:
:eek::eek::eek::eek::eek::eek::eek:

I usually don't care for benchmarks but WOW!