yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] chx:
I use the kernel with LG8 stock and no uv/oc and the screen on time is normally 6 to 7 hours, so the kernel is very battery friendly, at least more than enough for my normal use.

One question Andrei, with 19.3 I was having some random reboots(after a couple of days of use) that now are gone with version 20. Could those have anything to do with this change: 'Increased mmc timeout for bad quality SD cards.'?
[Galaxy S III Original Android Development] AndreiLux:
I don't think so, it may have been something else, but if you didn't catch the last_kmsg after the reboot, we can speculate endlessly what it could have been.
[Galaxy S III Original Android Development] chx:
I haven't catched it and with the new version the reboots are history... so it's just an anecdote now.
[Galaxy S III Original Android Development] Carphedon:
So is this kernel aosp compatible yet? Can't seem to find it anywhere but since you said a few weeks back that that would be done before you vacation or right after i figured that i should just ask.
[Galaxy S III Original Android Development] :
hint: first post and just few posts about your question.
[Galaxy S III Original Android Development] Carphedon:
Don't give me such a lame answer! I know what's in the first post, and there are numerous posts about it, those numerous posts are there for a reason:

So where is it then? I really appriciate all the hard work, don't get me wrong but i just think you should not promise things you can't be bothered with to finish in the first place.
[Galaxy S III Original Android Development] :
LOL..

because you are such a nice troll look 13 posts above your trolling.
[Galaxy S III Original Android Development] Carphedon:
LOL.. -.- Who is the troll? You can't even reply to a question in a normal way. You are probably referring to this: "I will support AOSP after JB will be released." Why not wait till key lime pie is released... Read my previous post again, there was nothing in there about JB in the first place. CM10 is JB and various kernels support it, i know official source is not yet released but i don't think that is a reason to not make it compatible.
[Galaxy S III Original Android Development] :
when AOSP is suppotred it will be in first post, I am sure. EOD for me.
[Galaxy S III Original Android Development] Carphedon:
Ok thanks, i will keep an eye on it.
[Galaxy S III Original Android Development] AndreiLux:
CM10 right now is not JB because a lot of things are not supported in it, like the hwcomposer for actually smooth rendering; back 7 weeks ago I was working for getting the kernel going for both CM ICS and Samsung ICS, but now seeing that JB is coming out soon which will undoubtedly involve many kernel changes which I don't know if it will cause kernel image incompatibility between ICS and JB or not, so I don't want to bother and waste my time to re-work things again after JB is released if I do the compatibility now solely for ICS and the CM10 ICS/JB hybrid. I worked on it before, it booted, it was half-way working, but it wasn't stable, and I had to leave for a month in the same evening.

Well well, in all due respect but you're just a belligerent imbecile if you think you can be in the position of theorizing on why I do or not do things, and you're welcome to fork off the kernel and implement AOSP your own damn self if it really irritates you that much. I don't get anything for doing this work other than enjoying it and trying to improve my own device, so I don't need people like you coming in *****ing in here like that, and you're welcome to enjoy AOSP on another kernel and not come back.
[Galaxy S III Original Android Development] currydude:
Keep at it AndreiLux! Love your work and hope you continue to the long future! This has most definitely already transformed into a serious kernel and I'm sure everyone believes so too (including other kernel developers), your contribution to other devs and the community has been amazing these past few months.
[Galaxy S III Original Android Development] diego9016:
AndreiLux, thank you for this great kernel.

Is it necesary to wipe cache, dalvik cache and fix permissions everytime i flash a new kernel? I'm asking because when i had my hercules, it was really necessary to do that and i haven't seen that here in any single kernel post. Thanks
[Galaxy S III Original Android Development] Yank555:
Nope, no need to clear any kind of cache, flashing a kernel will just replace the boot image and possibly add some script in init.d (depending on the kernel). Siyah will also push stweaks.apk, but that's rather uncommon for a kernel plus GM clears the dalvik for stweaks when pushing it.

JP.
[Galaxy S III Original Android Development] fastcx:
Though not required, but it is a good practice to do it. Especially after kernel flash you starts getting issue/instability before reporting fault.
[Galaxy S III Original Android Development] diego9016:
Thank you so much! I have no more thanks today but tomorrow I'll thank you both...

Could AndreiLux or someone please make a cwm flashable zip with this kernel?

Thanks in advance.
[Galaxy S III Original Android Development] IOmega666:
Just leaving some feedback.

Got Android Revolution HD 2.3.0, and flashed this Kernel, Alpha20, got a tons of reboots during the day some of them line non stop, gotta remove the battery wait a few minutes so i can use the cellphone again.
[Galaxy S III Original Android Development] Erahgon:
Re: [Kernel][28/02] Perseus

Try disabling DAC direct. It's known to cause such problems in some use cases.
[Galaxy S III Original Android Development] nfsmw_gr:
@OP

Please use search next time,it is located on top right of the thread.

This has been answered multiple times in the past.

@Andreilux

Andrei is this disabled by default or not?i don't remember actually...

If it's not disabled wouldn't it be a good idea to disable it by default so we deal with this permanently?
[Galaxy S III Original Android Development] Erahgon:
Re: [Kernel][28/02] Perseus

I think it's enabled by default. Until someone takes a look at the code and why it isn't working as it should, it wouldn't be a good idea to keep it on, methinks.
[Galaxy S III Original Android Development] Suprash:
I was wondering... Is there a way to enable LED Fading with this kernel ? Thank you. :victory:
[Galaxy S III Original Android Development] orangerot.:
AW: [Kernel][28/02] Perseus

Not yet... Let's wait if it'll be included in the next release :D
[Galaxy S III Original Android Development] Suprash:
Thank you very much for that quick answer. ;)
[Galaxy S III Original Android Development] agusdallalba:
I think the blues are wrong in the calibrated profile. I notice it the most on an app I use all the time, Calculator++. The calibrated profile seems to make the logo too green and desaturated, fact that is easily confirmed by comparing with an iPad 3.

However, I took a picture (with a Canon T3i, daylight white balance, Canon's color-accurate "Faithful" picture style, and the best lens I own, a Canon 50mm f/1.4), and I can hardly make out a difference. ¿Maybe it's something in my eyes? I see these two as _completely_ different, but the camera hardly agrees...

Edit: I found lagom.nl viewing angle tests to be most revealing. While the solid green and blue looked the same (actually, the blue is darker in the iPad, but that's a know limitation of its display) the violet colour was completely different and the red slightly different.

I think that calibrating the primaries is not enough and maybe there still is some work to be done. Can someone please try this out to take my particular devices out of the equation?
[Galaxy S III Original Android Development] jeebspawnshop:
I like that research the guy did on Perseus colors vs an iPad.

Eagle eyes :cool:
[Galaxy S III Original Android Development] agusdallalba:
Use a colour picker, the phone actually is greener, just not as much as I see it. Human eyes are not CMOS sensors, even though both have the same three peak sensitivity points. This discrepancy then may show up if the colorimeter was somewhat similar to the photocapacitors in my camera. Or my eyes are really broken and should have _those_ tested. :p

Edit: Oh, I see you edited your post. Sorry for un-editing it :P but you raised a very good point.
[Galaxy S III Original Android Development] Aijazji:
Re: [Kernel][28/02] Perseus

:thumbup::thumbup::thumbup:

Best kernal..
[Galaxy S III Original Android Development] mdfpido:
Can I install this kernel on top of JKay Framework and nothing will break?

Thanks.
[Galaxy S III Original Android Development] privat75:
AW: [Kernel][28/02] Perseus

yes, i have do it also.
[Galaxy S III Original Android Development] Slimer777:
Don't worry, they are both wrong that is the iPad3 and the phone itself. But both are already at a stage that is as 'correct' as possible by the nature of their panels.
[Galaxy S III Original Android Development] MBQ_:
Re: [Kernel][28/02] Perseus

I know I'm a bit late to post this but

In the rules, it states that you are allowed to give your best try at English if it isn't your main language, or post in your language you speak, and then post a 'translated' version below.
[Galaxy S III Original Android Development] kaynpayn:
Re: [Kernel][28/02] Perseus

Thanks for this man. I did get a class 10 16gb card so i'll give it a shot with hard swap. I did it before with yank's kernel on a class 6 but was unacceptable - phone lagged massively. I belive I should still have his kernel around but since this is a Linux option and perseus supports it I thought I'd want to take the long way and learn about how to do it instead of just flashing a kernel and be done with, learning nothing in the process. Also, I'm not sure if yanks kernel was sds proof.

I can figure out how to do it from your piece of code but you don't think you have something already prepared for hardswap instead of using the internal?

Btw that swapper2 app ended up formating my efs partition instead of the swap one. Nasty, spent the weekend fixing this. So, this time I'd rather not use 3rd party apps im not sure about what they're actually doing, if possible.

Not sure how offtopic was this. We should probably open a thread for discussing swap instead....
[Galaxy S III Original Android Development] nfsmw_gr:
+1

Exactly this!

That's why i switched to scripts from now on and everything goes fine. :)

Also btw i don't think it's off topic.

Perseus supports Swap,we are talking about Swap.Where's the issue? :cool:
[Galaxy S III Original Android Development] tisazalay:
Sure you can. Nice combo. I've been using that for a while,
[Galaxy S III Original Android Development] rlorange:
Re: [Kernel][28/02] Perseus

Andrei. Off-topic and I hope you haven't discussed this and I missed it...

These new Mali drivers CM is using... can Samsung based ROMs be modified to work with them? Assuming its possible to add them into a Samsung compiled kernel such as this?
[Galaxy S III Original Android Development] Erahgon:
I'm using a class 6 external sd as well and it lagged unacceptably! Even if I lowered the swapiness and increased read-ahead, it helped but was still beyond my tolerance. I'm a little apprehensive on trying the swap partition on the internal sd (using the /cache partition and a swap file) cause I can't afford to invest in devices in case of failure.

Please let me know how you fare with a class 10 card. It'll help me, and others like me, a lot!

Maybe you could post your use cases and experiences in a different topic in the general section as a discussion and we could all add to that. It'll be better to consolidate this all into a separate thread rather than load up on Andrei's thread.

On the colour calibration front: on my device, the colours appear a slight bit warmer at lower brightness levels, so I increased the temperature by about (as is displayed) "4 00K", which is just a little bit on the slider. Otherwise, it's an great to experience an accurate colour profile. I do like my device a bit more on the vibrant side, but for sure not as much as Samsung's original calibration. You devs and testers have done wonders! Thanks for helping me look at my device in a new light (pun intended :P )!

Also, using Mamba's profile as a base, and tweaking the setting more to my device, I am managing to get a decent amount of battery life! Coupled with apps like Greenify and so on, it's just great! Now the next BIG upgrade would be Android 5.0!
[Galaxy S III Original Android Development] invinciblecc:
Re: [Kernel][28/02] Perseus

Regarding swap brother

I want to tell u swap will always be slow even on class 10 sd card it will be a bit slow

I am using swap and zram both and I think zram is a lot better

It is fast and it allows seamless multitasking

Right now I am on yanks kernel with swap 512 mb swappiness 100 and zram 650mb my multitasking is awesome it remembers states of 50 apps

And regarding people saying that zram takes away real ran yes it does to be use as swap

But u should know one thing according to my experience zram is not fixed it is dynamic in nature... This means even if u set zram value to 830mb Ur system will still run it will only use that much amount of zram as swap as much as it requires rest will be used for running application I experimented with 830 mb zram and

Was still able to play GTA vc a well as shadow gun deadzone

So zram in my opinion is much better than swap

But still I would suggest a double combo swap +zrqm which most people would advise u against

But my theory is

First say Ur zran value is 260 and swap is 512

So till 10 -15 apps system will use zram (approx no)

After 10-15 apps the lmk will kick in and these apps which were previouslt stored in zRAM will be transferred to hard swap so effectively this combo will remember states of 50 apps (have tried it)

This means 50 apps will open from where u left them if the making of apps support it

I have tried this

U can try yanks kernel for swap +zram support I'll pm u the links

On another note andi can u please add zram support for Ur kernel I would love to try Ur kernel but no zram is a deal breaker for me

Finally enjoying s3

Yanks kernel

Sotmax v13

Zram enabled

Swap enabled
[Galaxy S III Original Android Development] orangerot.:
Just a short question... Is there the possibilty to change the LMK values? That would be really usefull ;)

Thanks in advance!
[Galaxy S III Original Android Development] nfsmw_gr:
Yep,that's the only thing missing from perseus,atleast for me.

Anyway i'm sure Anreilux has seen those discussions before,if he wants he'll add zRam to the kernel,it shouldn't be very hard for a dev like him...
[Galaxy S III Original Android Development] AndreiLux:
Adding zRam is a matter of changing a single option in the kernel - but I won't do it yet as Samsung seems to have enabled it by default on the 4.2.1 kernel and they have some changes regarding page handling on that matter.

I'm a big disbeliever of Swap - it caused too many delays due to the slow I/O speeds, and I was using my internal memory too...
[Galaxy S III Original Android Development] danarama:
Re: [Kernel][28/02] Perseus

Off topic but I can't wait for your 4.2.1 kernel...

Hope this leak becomes official soon
[Galaxy S III Original Android Development] kaynpayn:
I've benchmarked a class 10 16gb kingston card with A1 SD Bench and results were something like:

- Internal SD: read=38.25Mb/s / write=28.42Mb/s

- External SD: read=12.03Mb/s / write=10.51Mb/s

This also allows to bench the "internal memory" which came up with:

read=44Mb/s / write=33.73Mb/s

Also benched the card with sdtools and came up with 10mb/s for write and 17Mb/s for read, maybe it uses a different way of testing, don't know. Didn't allow for testing the internal, so i can't compare.

Haven't tested swapping yet (only later after work) but you're probably right, will probably not be acceptable to hardswap - these figures show the external to be about 3x slower than the internal. Don't think it will ever cut it properly. Will try it anyway, it doesn't hurt (except performance :p )

Didn't bench the 8Gb class 6. No point, wasn't acceptable then and that should exclude the need for actual values (also, i don't have it with me and my UAG case is a b*** to come off :p )

I realise next samsung rom will most likely come with zram enabled but the current kernel version will also not be compatible (i think). I could tell you're going to build a kernel for 4.2 but are you planning in maintaining a kernel for the "old" 4.1.2? In that case, think you can enable zram if it proves effective for people to try it out?

Thanks!
[Galaxy S III Original Android Development] invinciblecc:
Re: [Kernel][28/02] Perseus

Man I know maybe I am pestering u but please if it is not a lot of work and only a matter of changing a single option please add Zram to Ur kernel fast

As I am really really excited to try Ur kernel and all other options which it has specially deep sleep and GPU oc

But I can't leave zram so yank is the only option for me

Please if it is not too much add Ram support cos I know without zram s3s multitasking is close to nil and swap is toooooo slow

Thanks and sorry for pestering again

Yanks kernel

650zram

512swap
[Galaxy S III Original Android Development] TheMasahiro:
So my Galaxy s3 all of a sudden started to have stutters, i have a custom rom Foxhound 2.3, and when i try any custom kernel it lags as hell. (Stock also gives stutters so its not kernel related i think)

For example perseus stutters my phone in app drawer and every time i open an application.

Syah 1.8.9. although its better, still have some stutters...

the only one that can have the phone more stable is the stock one. I dont really mind having the stock kernel its just that it makes the phone more stable but it still stutters when opening apps and in the app drawer.

Its weird because in applications i have no problems, and when im playing games is all good to.. even the more heavy intensive ones. Also my boot and shutdown animation stutter or jitters a little bit.. a thing that dint happened.

Also the benchmarks are good as always +/- 16000 on antutu, no changes... so i don't really understand whats happening...

Steps so far:

-Tested other custom roms including CM10.1 Nightly

-Tested various kernel.

-Flashed stock rom with odin

Every time with megawipe. always...
[Galaxy S III Original Android Development] jeebspawnshop:
You've copied and pasted this exact post in to a bunch of threads... which you probably realize isn't a very nice thing to do.

And why would you post in a kernel development thread about something that has nothing to do with kernel development?

Your copy & paste post belongs in the Q&A section.
[Galaxy S III Original Android Development] nfsmw_gr:
Nice find. :)

Well,i don't like Swap myself either.

The slow i/o occurs only on swap or on zRam as well?

Also something a bit off topic,when do you think we'll have 4.2.1 update from Sammy?
[Galaxy S III Original Android Development] MattBooth:
Can anyone tell me:

If I am getting slow charging from AC (because of a non-official Samsung cable) would increasing the AC charging rate hurt anything?

The AC wall brick is official Samsung, the lead is not (I use it because it's longer).

The default rate is 1000mA. Would 1200mA+ do anything bad?
[Galaxy S III Original Android Development] enigma1981:
Re: [Kernel][28/02] Perseus

The stock Sammy S3 charger can't deliver anything more than 1000mA do there's no point setting it any higher than that as it won't be able to supply it
[Galaxy S III Original Android Development] MattBooth:
So, what's the point to the sliders for charging rate?
[Galaxy S III Original Android Development] orangerot.:
AW: [Kernel][28/02] Perseus

If you're getting slow charging enable "ignore margin" and "disable unstable power detection".
[Galaxy S III Original Android Development] MattBooth:
Those options scare me, though! :p
[Galaxy S III Original Android Development] MuertoKo:
Re: [Kernel][28/02] Perseus

For bigger chargers like n4 one delivering 1200mA

Buy a new wire or tick that option to ignore margins, only options!

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] MattBooth:
What are the dangers of them, though? Is there a possibility of frying the charging chip, my battery or charger?
[Galaxy S III Original Android Development] Steve_max:
If your charger is able to give you a higher current, your phone will accept it. For example, I use a Galaxy Tab charger (up to 2A). I set my phone to charge at 1.4A, which is impossible with the S3 charger (or with the stock kernel); so, my phone charges quicker, and at the optimal rate for the battery size.

---------- Post added at 11:02 AM ---------- Previous post was at 10:53 AM ----------

As far as I can tell, you would endanger the regulator chip and specially the battery. The main problem would be the battery: if you give it too much juice, it might heat up a lot; this could vapourize some components inside a sealed container, and make your battery explode. Explosions and/or leakages and/or other catastrophic failures can happen if you turn on both "ignore margin" and "disable unstable power detection" AND use a highly unsafe charging current, like 2300 mAh AND turn on overcharge).
[Galaxy S III Original Android Development] MattBooth:
So, those should be perfectly safe with the stock, 1000mA charger? Or if I shouldn't use both, which should I use? (I'm using both settings turned off now, the phone is warm, but that's because I'm wi-fi tethering and downloading at 10Mbit/s... but it's now charging much faster than previous. For instnace, before, while tethering it would sill decrease, now it's increased).

And I could set the AC to 1.4A and use my Nexus 10 (2A) charger without worry (the safety stuff on)?
[Galaxy S III Original Android Development] enigma1981:
Re: [Kernel][28/02] Perseus

Yep that's right :)

I use the custom current options to boost my usb charging current as my pc has usb3 which can output at 900mA and not the 475mA stick for usb2
[Galaxy S III Original Android Development] MattBooth:
^ See I'm using a USB2 port and setting it to 900mA and it chargers much quicker. I have USB3, but I'm fairly certain I'm not using that port. It's the same at university too.
[Galaxy S III Original Android Development] AndreiLux:
NO.

I clearly labeled what's dangerous and what's not - enabling the "ignore margin" and "unstable power detection" will have no effect on the phone. The charger chip is rated for amperages and voltages much much higher than we're able to use on a phone.

Those two settings are meant solely for charger protection. ****ty chargers with lowered rated amperage being used at that or above their limit will fail - other phones like the new Sony Xperias charge at a default of 1400mAh and if you connect an old and bad 1A charger with them, they will fail.

Same thing with the charging currents, even the highest I have current set up in the interface is "only" 2300mA, that's 1.1C and still within any reasonable safety margin for the stock battery and extremely safe for bigger third-party batteries.

The only thing that is truly dangerous is the battery voltage controls and I've clearly labelled them as such, anything else is safe.
[Galaxy S III Original Android Development] enigma1981:
Re: [Kernel][28/02] Perseus

Running 900mA through a usb2 port could (potentially) frazzle the usb port as it's putting too much draw on the port. Be careful with that
[Galaxy S III Original Android Development] MrxSiN:
if u got usb port 2.0 (normal usb port) it only give 475mah charging power. Forcing 900 may harm your usb port. But different on usb 3.0 (blue usb hub) if support to 975mah. Using 900mah will never harm your port.
[Galaxy S III Original Android Development] Tectas:
AW: [Kernel][28/02] Perseus

It can't harm the port, the device isn't pulling anything, it just takes less as provided if the margin is set lower otherwise it will simply take what is provided by the port, no matter how high you did set it.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] enigma1981:
Re: [Kernel][28/02] Perseus

So that works the same as the a.c. charger? That's handy to know, cheers