yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Hbohd:
That's true, we have good management of each tunable in stweaks, but 3 governors on one kernel don't see to me as 'too much choice'. Moreover, these 2 govs (pegasusq and zzmoove) differs (from easy-notice usage experience i can say that), pity that i don't have enough knowledge to analyse whole source code.

I think that it is still worth considering by Andrei, because it simply gave me best results in both battery and performance :p
[Galaxy S III Original Android Development] JustArchi:
+1 for adding zzmove.
[Galaxy S III Original Android Development] Olioaglio:
Logcats allshare cast

Andrei, attached to this post you will find a zip with two logcats, done with System Tuner. One is made with Perseus kernel alpha35 and failed Allshare Cast Dongle start, the other one was made some minutes later with recent siyah kernel 1.9.1 and successful dongle start. Rom was both times Wanam Lite 6.5 aka JB XXEMC3. Hope the logs contain some helpful information to find the culprit of the allshare cast dongle problem with perseus kernel.

Cheers, Olioaglio
[Galaxy S III Original Android Development] AndreiLux:
First of all, that's a kernel log, not a logcat. Fine however, though having both would be useful.

Secondly, there's nothing in it that identifies a failure of the dongle. I see the hardware decoder is firing up and then the Wifi driver is changing into access point mode for the dongle. Still doesn't advance me on the matter.
[Galaxy S III Original Android Development] Olioaglio:
Ok, thanks. but... could you advise me what to do to get the correct data youd need. I'd be very glad to help

Olioaglio
[Galaxy S III Original Android Development] Scarface1991:
[MENTION=4167023]AndreiLux[/MENTION]

I use your great Kernel with the Zero Wake Lag mod

http://xdaforums.com/showthread.php?t=2208267

This mod removes the lag of 1-2 seconds when you power on the screen by adding a permanent wakelock.

I was wondering how the Pegasusq governor is configured. How does the CPU behave if the screen is off? Does the governor reduce the CPU clock? and if yes to what amount? Also at how many cores does the CPU run if the screen is off? Does it still use all 4 cores?
[Galaxy S III Original Android Development] kazoum:
Can anyone tell me please what do I have to do in Stweaks (Power tab) in order to make my battery charge faster? Of course, without overheating or damaging the battery.
[Galaxy S III Original Android Development] STAticKY:
Have you tryed doing a full nandroid and then replicating your setup on a diffrent rom?
[Galaxy S III Original Android Development] neferym:
I have a boot loop : with working miui v5 Samsung base and boeffla kernel, I flashed perseus kernel. Wipe cache and Calvin cache.

I revert, it's OK.

Any idea?

Ty :)
[Galaxy S III Original Android Development] Lctwisk:
Miui v5 is 4.1.1 based. I guess perseus is for 4.1.2 only ;)
[Galaxy S III Original Android Development] neferym:
Ty.

But it worked before.

Default kernel => perseus OK

Perseus => boeffla OK

Boeffla => perseus ko :-\

I think that I had same problem with samy rom
[Galaxy S III Original Android Development] STAticKY:
Try cleaning up the bits the kernel leaves behind. Like config scripts ect... there are a few cleaning scripts around or you could do it manually...
[Galaxy S III Original Android Development] AndreiLux:
Boeffla leaves some trash scripts behind in init.d which don't seem to agree with this kernel, I don't know what exactly is causing it. Just delete everything prior to flashing.
[Galaxy S III Original Android Development] neferym:
ok ty !!
[Galaxy S III Original Android Development] Anakha56:
Install this app: https://play.google.com/store/apps/details?id=com.nolanlawson.logcat

Launch it and press record. Then go back and launch whatever it is that is failing, count to 5, go back to logcat and stop recording. Rinse & repeat with Siyah kernel. You can do this from a PC I am just providing a "easy" way without a PC and without installing a console app and typing in the command manually. The reason why I say count to 5 is because the log file could get fill with a lot of other information but its your call as to how long you want to leave it running. Hope this helps you in getting the info Andrei requires...
[Galaxy S III Original Android Development] AndreiLux:
Well that was a very long changelog to write. New update.

I hope people enjoy the brightness reduction feature, it was something which plagued me personally until I had sort of an enlightenment a few days ago.
[Galaxy S III Original Android Development] Hbohd:
Just one thing: That's new changelog for probably next alpha36 from 22/04, but you have just copied alpha35(06/04) ;p

Apart from that, have you even considered zzmoove? :>
[Galaxy S III Original Android Development] AndreiLux:
Forgot to edit that, fixed now.

I've considered zzmoove, yes. I won't implement it. You can mimic the scaling logic by yourself by changing the configurables to your liking. I will rewrite some Pegasusq parts in the next version so people stop crying about the smoothness.
[Galaxy S III Original Android Development] borjaag:
WOW, incredible changelog!!!

Thanx u so much AndreiLux :fingers-crossed:
[Galaxy S III Original Android Development] www1:
Fantastic.

Only a simple question Andrei. Do you plan to buy and develop for s4? It's very important for my next phone choice.

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] AndreiLux:
https://github.com/AndreiLux/Perseus-UNIVERSAL5410

Once it's available to buy at "reasonable" price. I'm going to have to have to break the donation piggy-bank from the last 8 months to partially finance it, if it weren't for that I wouldn't find it worthwhile to buy a new high-end phone this early.
[Galaxy S III Original Android Development] Steve_max:
Yes, that 5410 sounds amazing. If you're going that way, looks like the choice on the S4 will be great CM support (Cyanogen on I9505) or great development on stock (AndreiLux on I9500).

I'm assuming your development should be adaptable to a future Exynos 54xx-based Note 3, right? Would you consider developing in parallel for different devices again?
[Galaxy S III Original Android Development] Anakha56:
I won't even pretend to understand some of the new features we have with this new kernel. I honestly thought that there was nothing new to bring to the table and I am extremely happy to see just how wrong I am :D. Thank you for the continued updates Andrei, much appreciated...
[Galaxy S III Original Android Development] JustArchi:
Great work Andrei, I can't imagine how much work you've already put into this kernel. This is AMAZING. Keep up awesome work.
[Galaxy S III Original Android Development] Kyle07:
Here's hoping the S4 upgrade is a way off so that the incredible S3 updates keep coming:p

Thanks for the update, Andrei. I will give a small donation once I am in a position to do so.
[Galaxy S III Original Android Development] psyntific:
Thank you Andrei.. Awesome work once again..
[Galaxy S III Original Android Development] habylab:
I'm on CM10.1 as of today and I am gutted. Linaro!

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] alberber:
Everytime an update comes it is very difficult to me to understand every new feature hahaha

Anyway this kernel is awesome, thanks AndreiLux
[Galaxy S III Original Android Development] Olioaglio:
Thanks Andrei. I have attached a new attempt to log allshare cast dongle start with catlog as advised.

Hope this time it meets your needs to debug. Made on perseus36 kernel. To me it seems it have something to do with wfdbroker...?!

Let me know if there is something usable in the log.

Cheers, Olioaglio
[Galaxy S III Original Android Development] nfsmw_gr:
Nice changelog man.

I'll give it a go tomorrow,thank you for fixing the headset issue. :)
[Galaxy S III Original Android Development] MuertoKo:
Regarding ZRam using stock configuration I still have those well known massive lags of over a minute of blocked screen somehow...

What log could be helpful for this? Can we consider it a known issue? For now must switch it off, the Linaro chain... Well, pure placebo for now as it's not easy to test, we'll see with daily usage.

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] habylab:
Linaro has proven to be a placebo, but there is also evidence to suggest otherwise. Regardless, the zRam issue if still there is annoying! Try changing to a lower size and also cfq.

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] MuertoKo:
Will try the commented fix to set cfq and same buffer for both memories, but looks like settings the readahead buffers won't work properly (only checking on system tuner after using Stweaks, might be app issue, if you can share commands to check terminal great, if not I'll search for them tomorrow).

But happened to me just now, was almost RAM full and plop, major lag!

Using 50 background apps allowed by using JKay framework btw, this may have helped to fulfill my ram causing the issue?

Anything we can do Andrei, to solve or help debugging?

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] nfsmw_gr:
Just tried the new version.

Can't tell if it's placebo or not but i feel my phone kinda smoother now...

About zRam,i've set mine to 512mb,512kb read ahead and row(sometimes good ol' deadline too) as scheduler for both internal and external storage.

Never had any lag with this combo so i'm keeping it this way. :)

EDIT:50 apps?for real now..?

Man that's way beyond 1gb ram excpectations...:(

No wonder why you get lags.

I don't think Andreilux can do something about it,he's a great dev and he has unlocked so much potential for our S3's but he can't magically add/unlock physical ram or something similar to make the lag go away...i mean 50 apps is way too much for 1gb,dont you think?

Anyway,that's only my opinion.Anyone can have theirs i suppose. :)
[Galaxy S III Original Android Development] AndreiLux:
Thank you, I'll try to fix it. Edit: try a6.1

We'll eventually get exFat working and then you won't need NTFS.
[Galaxy S III Original Android Development] tvhak:
sorry bro still no voltage in setcpu and in voltage control
[Galaxy S III Original Android Development] AndreiLux:
...

Can you output the contents of /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table ? (And make sure it's even there, I don't see what could be wrong)

Sorry for bothering that much.
[Galaxy S III Original Android Development] tvhak:
no bother. glad i can help.

you talk about uv_mv_table. i don't have that. i do have uv_uv_table
[Galaxy S III Original Android Development] tvhak:
just flashed 6.4 and i can change and save voltage.

i use voltage controle

thanks
[Galaxy S III Original Android Development] Warm_ice:
Can somebody provide a link for the stock kernel (XXLE9) just in case?

TIA

Edit: found it
[Galaxy S III Original Android Development] 9Lukas5:
Hm, with incredicontrol it didn't work, but voltagecontrol did. I have set all -50, but how can I check if the new values are really beeing used?

L

Gesendet von meinem GT-I9300 Galaxy SIII
[Galaxy S III Original Android Development] mp3geek:
Would it be hard to push the S3 to 1.6G instead of 1.5G?
[Galaxy S III Original Android Development] tvhak:
as for now 1,5 isn't working either. he's working on that.

when he has found the problem. i think we even can get 1,8ghz
[Galaxy S III Original Android Development] kickassdave:
Also set all frequencies to -50mV.

No freezes or anything so far, looks good.

I don't really think there is any need to overclock other than to get some crazy benchmark scores. Undervolting and battery saving I would say are the main goals with any SGS3 kernels.
[Galaxy S III Original Android Development] 9Lukas5:
I'n using it with 1Ghz only and it's running great with that. :D

L

Gesendet von meinem GT-I9300 Galaxy SIII
[Galaxy S III Original Android Development] AndreiLux:
Incredicontrol is using different voltage interfaces, I will have a look at them later on. But usually we use SetCPU / VoltageControl on Galaxy phones.
[Galaxy S III Original Android Development] 9Lukas5:
Yes, with voltagecontrol it works, but can I check if the values are really applied other than setting a value which is surely to low?

Edit: I have tested it right now, it works really, with 850mV@1Ghz it freezed :D But with -100mV on each frequency I haven't got problems up to now.

L

Gesendet von meinem GT-I9300 Galaxy SIII
[Galaxy S III Original Android Development] AndreiLux:
Changed minimum available voltage to 600mV, lower frequencies should reach low 700's. Enjoy playing around with it.

I also added version a7.1, if Wifi does not work on this then I think I have cornered the cause of it.
[Galaxy S III Original Android Development] 9Lukas5:
Hm, I can't go under 850mV with alpha7 or 7.1

On 7.0 wifi is working, on 7.1 not.

L

Gesendet von meinem GT-I9300 Galaxy SIII
[Galaxy S III Original Android Development] AndreiLux:
Can't go under how? Does it crash under that frequency? Or doesn't save that voltage in the app? Also what frequency? Try running lower voltage at 200MHz, greater frequencies obviously won't support such low voltages.

Thank you for the Wifi confirmation.
[Galaxy S III Original Android Development] 9Lukas5:
No I meant that the app only shows down to 850mV, less isn't there. Or do I need to do anything special in voltagecontrol after I flashed a new kernel?

L

Gesendet von meinem GT-I9300 Galaxy SIII
[Galaxy S III Original Android Development] AndreiLux:
Are you using the free version? It has a limitation of -100mV.
[Galaxy S III Original Android Development] 9Lukas5:
yes, I'm using the free version.

L
[Galaxy S III Original Android Development] AndreiLux:
You need to buy it (I strongly recommend SetCPU though), or find a older free version of SetCPU. I'll try to implement other interfaces for other apps later on.
[Galaxy S III Original Android Development] AndreiLux:
The minor versions were just some initramfs re-packs to fix the issues some people had with some ROMs, and I replaced the way init.d works with the "classical" method. Nobody ever used the advanced method anyway. Also I sneaked in default sched_mc_power_savings to be set to 2 by default. If there's any kernel functionality change I will post that of course as a new version with change-log.

You didn't mention the overclock before. Then it sorts out, but still that I/O score seems weird. Anyway stay away from Quadrant.
[Galaxy S III Original Android Development] jayden2009:
I will... But when I used it and saw the results I thought wow that's a high score.... I overclocked it to 1704 mhz... And no problems at all... So again thanks for the kernel :)

Verstuurd van mijn GT-I9300 met Tapatalk
[Galaxy S III Original Android Development] stfudude:
I believe many people need CWM version of this kernel. My reason for wanting it is due to the fact that extsd2internalsd mod by mattiadj requires the script to be flashed

after

flashing custom kernel

before

booting. Will OP please make it? Hopefully it's not as hard as compiling a kernel from scratch.
[Galaxy S III Original Android Development] beaver2233:
its really not that difficult to flash via cwm... download a flashable custom kernel(doesn't matter which), delete that boot.img inside the zip file and move the boot.img of this kernel into the flashable zip... then flash through cwm...
[Galaxy S III Original Android Development] dlads:
Well i answered my own question by installing this kernel anyway and i can report that it runs real racing 2 very well indeed so hat off to you for developing this kernel so early on and i'll be keeping an eye out for updates.

Many thanks.
[Galaxy S III Original Android Development] fosseperme:
With same settings of UV, Siyah for JB is most battery friend than Perseus, do you confirm?

I have also recalibrate my battery after flash of Perseus.
[Galaxy S III Original Android Development] edpham:
Is battery okay with this kernel? The stock jellybean is bad :(
[Galaxy S III Original Android Development] tvhak:
siyah is more battery friendly on my phone to . but then agian perseus is faster then siyah on my phone.

so i guess that could be the reason why its not as friendly as siyah???
[Galaxy S III Original Android Development] gee2012:
Runs perfect on ARHD 11.0.0 (LIB). good job :good: Why only 4 stars, should be 5 imo ;)
[Galaxy S III Original Android Development] EViollet:
Actually, why not dump the "extsd2internalsd mod" completely?

I currently use an app to redirect selected folders to the SD card. Suits my needs perfectly and without the hassle of having to flash yet another zip file.

Try http://xdaforums.com/showthread.php?t=1410262

I believe you won't regret it.
[Galaxy S III Original Android Development] stfudude:
Is that directory bind (sorry I'm using tapatalk app)? I already tried it a few weeks ago and I don't like the fact that it constantly using memory all the time. Ram is really precious to me, so I won't use that app again.

Sent by my Galaxy S III
[Galaxy S III Original Android Development] EViollet:
OK. Your choice. Fair enough. FYI it takes up 2.7Mb of RAM on my phone. You can also disable the service. But quite frankly, 3Mb is OK for me, especially given what it does.
[Galaxy S III Original Android Development] renmo:
same here +10
[Galaxy S III Original Android Development] aydc:
Great kernel, but I miss USB charging speed increase. Any chances of that being implemeted?
[Galaxy S III Original Android Development] jayden2009:
Is there a way to do a donation?

Verstuurd van mijn GT-I9300 met Tapatalk
[Galaxy S III Original Android Development] mariosraptor:
https://www.paypal.com/lu/cgi-bin/w...63663d3faee8db02a037e263542f58098410815cf7df7
[Galaxy S III Original Android Development] AndreiLux:
Will do in next release.

@stfudude: I don't get why you need a CWM for that; you can just flash the kernel and then flash that mod afterwards. In fact I don't see the relation between the two. Also people tend to screw things up with CWM .zips sometimes by flashing it on other devices. Mobile Odin / Odin is a much better way of doing it. The only kernel you should have in CWM form is a stable, stock backup of the default kernel in case things go wrong.

<--- There's a button for it in the user info. It would be appreciated a *lot*. :)
[Galaxy S III Original Android Development] jayden2009:
Done 8T1158322R932450G thanks for you're work :)

Verstuurd van mijn GT-I9300 met Tapatalk
[Galaxy S III Original Android Development] aegeuss:
A beer from me

51A23170D38581115

A small beer for your efforts then ;)

Thanks.
[Galaxy S III Original Android Development] nodstuff:
getting a visa debit card on Friday so expect a donation.

Serious kudos to you, doing some serious dev work for us here.
[Galaxy S III Original Android Development] STAticKY:
Well considering zram compresses data into ram at a ratio of 3:1 you can fit alot of data in there. Although the new compression algo (SNAPPY) gives up a bit of its compression in favour of speed so ratios are around 2-2.5:1... so you can theroretically set zram up to about 1.5gb with this kernel and a bit higher on the last release. Mind you the data that gets compressed are pages that arent needed at that time. So you wouldnt want all ram to be used for this as u need some ram for the system that isnt compressed... you just get rediculous multitasking compared to wothoit zram at the cost of a few lags upon swapping data in/out when you swith to an app that has parts of itsself in the zram. 50 apps works ok with this but i think this limit is too high. Would be good if jkay could make it configurable. I think his reason for that setting is that he finds when u have quitw a few background processes going on they count towards this limit and so when you run apps on top of that things start getting killed off...

EDIT: I find with a higher zram value it rarly gets saturated and that is when i find the lags start to happen...upon nearing saturation...
[Galaxy S III Original Android Development] tolis626:
I know this post doesn't contribute to anything,but hats off to you Andrei.You outdid yourself again.This release focusing on speed and overclocking/undervolting has made me quite happy.I'll see if I find anything unexpected about ABB and I'll let you know!

PS:Guys,50 open apps are too much for even 4GB of RAM.Get over it.It's not a server,it's a phone.
[Galaxy S III Original Android Development] STAticKY:
I would have to say it completly depends on what the apps are. But yea. 50 is a bit much hence why i think jkay should make that option configurable...

PS: these s3's have much more power than a couple of my servers :eek:
[Galaxy S III Original Android Development] Infy_AsiX:
Some nice new useful fixes and improvements. Shame I'm stuck on v34 because if zram is enabled for me none of my apps will load half a minute after boot. As a result I can't get into tweaks to turn it off.

I think it's because I have a number of tasks in background at boot.

?????? Galaxy S3 ??????
[Galaxy S III Original Android Development] AndreiLux:
For what it matters: it's not placebo as far as I can see.

But it has rather less to do with Linaro but with some other smaller patches I also applied. The decompressor patch together with GCC 4.7 and turning off alignment trapping in the kernel is what I guess provides the boost.

I didn't fix the zRam lag because I don't know what causes it, as far as I'm concerned, don't use the hacked framework to artificially increase the app limit and you won't have issues. That or increase zRam size (or disable it).
[Galaxy S III Original Android Development] Infy_AsiX:
I'm using jkay framework but not the 50 app option. I vote for zram to be disabled by default but accessible via stweaks. With unexplained issues shouldn't it be off my default but optional as experimental?

?????? Galaxy S3 ??????
[Galaxy S III Original Android Development] jinosong:
I refuse to buy the new S4 until my favorite dev supports it.

It's true though I won't buy it until Andrei releases a kernel for it.

A Perseus supported S3 is far more appealing than a non-Perseus S4 to me.
[Galaxy S III Original Android Development] nfsmw_gr:
Very complete answer,thank you for mentioning those things.
[Galaxy S III Original Android Development] Fienman:
Thank you so much for the new features Andrei.

Bcoz of ABB, I was finally able to run my Cpu at 1800 mhz with it rebooting on me. First time ever since I got the phone.

Now if you would just let us go beyond 1800......pls
[Galaxy S III Original Android Development] MuertoKo:
Glad to hear I wasn't going crazy :P By increasing the zRam to 1.5Gb I might be able to keep my app limit? Will give it a try today, thanks!

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] Yazan76:
ZRAM

ZRAM is one of the amazing features implemented in this kernel and I vote to keep it. I never had a lag with ZRAM on 400MB except when I intentionally tried to fill it when testing file swap with ZRAM. I opened so many apps including Nenamrk2, and then tried to load the Nenamrk2 results web page which is HUGE. My phone literally stopped responding for like 10 seconds or so while ZRAM got completely filled. The phone went back to normal status after paging most of the ZRAM contents to the file swap.

If there is a way to let ZRAM page its oldest pages to the file swap before it gets completely filled, then I think ( and hope ) that the lag issue will be somehow resolved.

Thank you AndreiLux for your hard work !!