yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] henrybravo:
Agreed, I avoid all that stuff. Now there's some guy (that doesn't own a Galaxy S3 BTW) in the dev section with a script/mod that has every stupid tweak you can imagine. It contains, among other things, Seeder (he claims it makes the phone 3 times faster, LOL), V6 SuperCharger, ThunderBolt, Adrenaline Engine, Adrenaline Boost, ZRAM script, Loopy smoothness tweak, and the list goes on and on. A nightmare concoction of bullsh**.
[Galaxy S III Original Android Development] habylab:
Re: [Kernel][09/01] Perseus

Back on topic people!
[Galaxy S III Original Android Development] :
We are on topic, but I guess you aren't...

What we are saying is that those kind of crap doesn't make any magic, and Andrei advises everyone to stay the hell out of this. It screws with the kernel, the system and everything, but I'm sorry if you like those things, I guess that the warning to not use those kind of BS is just as useless as most of the posts around this thread. :)

---------- Post added at 08:03 AM ---------- Previous post was at 08:01 AM ----------

Thunderbolt is good, at least there's a lot or some of good parts on it. No wonder why gokhanmoral uses parts of it in Siyah kernel. I used to use it on my i9100, gave some little improvement, but I guess that with Perseus kernel I don't need it, it's already complete.
[Galaxy S III Original Android Development] Tokarin:
Re: [Kernel][09/01] Perseus

I really hope this seeder and entropy discussion stops. It's simple as this, entropy scripts does make your apps more responsive by making the phone use more of its resources at the time. A little more in perseus case since the kernel already worked that out.

The problem is this "boost" stays when you left the app and let it run in the background so the phone will have to utilize more of its cpu workload, making more cores join the process so the phone become hotter and eats into the battery. Like me for example, I don't need 2 cores to work when I'm only flipping pages in Kindle app. This has real affect on the screen on time battery, though not the idle time since Andrei did a wonderful job with hotpluging logic back to 1 core then utilize AFTR idle mode. End on story. Stop using it, doesn't make anything better, a single A9 core can handle a lot of things on your s3, half a second faster doesn't prove anything.

About the other tweaks on development page, zram compress the data so make it appears a lot of ram free, but have you thought about the time and writes it make to decompress? Bullsh** all the way, the only good thing there is the gpu rendering and that is on the rom side, use something like revolution rom, it does the same thing. End of story too

EDIT: if anyone interest in more workload on your phone, look into swap mod by Yank555.lu, and steal the lock app logic from bestMultiTaskingFix by Mattiadj, put them in init.d folder. Also change the minfree value using terminal emulator or adb using the echo command, if you don't know what I'm talking about then you better not involve in the entropy mess.
[Galaxy S III Original Android Development] yimb0:
Another way?

Hi @AndreiLux it would be very appreciated, another way to donate, maybe google? through google play. I have issue with paypal account ...
[Galaxy S III Original Android Development] d8389:
+1

Sometimes discharging with GPS navigator running and charger connected.
[Galaxy S III Original Android Development] EViollet:
Re: [Kernel][09/01] Perseus

Have you tried with another charger?

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] simmer14:
i'm on the last version guys .. 31.1

my rom is XXELLA jb wanam lite 5.3

my headphone buttons are not functioning ... please anybuddy confirm ..
[Galaxy S III Original Android Development] www1:
R: [Kernel][09/01] Perseus

Disable dac direct from stweaks

Inviato dal mio GT-N8000 con Tapatalk 2
[Galaxy S III Original Android Development] simmer14:
done and rebooted .. still not working .. the headphones are working perfect i can talk and listen songs and everything . but the buttons are not responding ... :crying::crying::crying:
[Galaxy S III Original Android Development] xukaisheng:
Re: [Kernel][09/01] Perseus

Hold the mic control button. Give it a try.
[Galaxy S III Original Android Development] gingerneil:
Any thoughts, comments or updates on including ethernet?
[Galaxy S III Original Android Development] TheMasahiro:
Good explanation there.... thanks,, that was really helpful... What do you say about the tweaks on pimp my rom app? do you think they are useful or its better not to install them?
[Galaxy S III Original Android Development] Tokarin:
I would call the work a "compilation" but yeah, wont do you any good on this kernel and s3. Let me break it:

- You don't need the screen mod, mDNIe do the same thing, I suspect it would get any better for this type of OLED screen.

- Touch sensitivity >>> ARE YOU SERIOUS? is your fingernails being able to control the screen not enough already?

- Zipalign >>> rom already did that, look into odexer, better option

- OnDemand logic >>> suspect it would do better than what Andreilux did, not the mention andrei did it for s3 specific and the app did it for all.

- Deeper Sleep >>> Andrei's logic of going to AFTR is the best way, no better, cause there is none ...

- Task killer mods >>> look into minfree from swap http://xdaforums.com/showthread.php?t=1814311, learn how to change it using terminal emulator http://www.androidcentral.com/fine-tuning-minfree-settings-improving-androids-multi-tasking. DONT USE THE APP, wont stick. If you dont mind the lag between switching apps (not the lag of using, I run 7 apps and a game consecutively without lags anyway) then use this minfree value like mine: 4Mb, 5Mb, 8Mb, 12Mb, 16Mb.
[Galaxy S III Original Android Development] Infy_AsiX:
Re: [Kernel][09/01] Perseus

Been getting freezes in a game. Here's the last_kmsg

http://db.tt/fIlwcH22

?????? Galaxy S3 ??????
[Galaxy S III Original Android Development] www1:
R: [Kernel][09/01] Perseus

Can anyone tell me that file I have to delete for restore stweaks to default settings?

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] giajp:
R: [Kernel][09/01] Perseus

Sent from my iPhone5 Fu**er S3 using the Perseus kernel.
[Galaxy S III Original Android Development] tribemac:
Sv: [Kernel][09/01] Perseus

You just have to push the button under extras in STweaks, reset to default :)

Skickat från min GT-I9300 via Tapatalk 2
[Galaxy S III Original Android Development] TheMasahiro:
Thanks mate!! im already giving this a look and im going to try it out....!!
[Galaxy S III Original Android Development] TheMasahiro:
http://xdaforums.com/showthread.php?t=2107935

Hey what you pros think about this :P ? wanted to know opinions since i use perseus kernel and wanted to try it out
[Galaxy S III Original Android Development] hanspampel:
Did you read the last 3-4 sites? Not? Do it!
[Galaxy S III Original Android Development] habylab:
Re: [Kernel][09/01] Perseus

Nope, leave it.
[Galaxy S III Original Android Development] TheMasahiro:
haha straight! like it.. thanks
[Galaxy S III Original Android Development] KennyLegend:
Re: [Kernel][09/01] Perseus

Too much crap going on there altogether. I wouldn't flash this.
[Galaxy S III Original Android Development] AndreiLux:
Don't touch that pile of crap even with a ten foot pole and a hazmat suit. I also don't want to hear again about it.
[Galaxy S III Original Android Development] trein91:
Re: [Kernel][09/01] Perseus

Hey Andrei just wanna ask your opinion on this app on play store LagFix (fstrim)

https://play.google.com/store/apps/details?id=com.grilledmonkey.lagfix

Does that app genuinely work or is it another placebo app?
[Galaxy S III Original Android Development] AndreiLux:
It's a genuine fix but, as it's written in the description, only affects some devices. I think the explanations in the links provided are thorough enough. I don't think we have any of those issues.
[Galaxy S III Original Android Development] nfsmw_gr:
I tried this after i saw your post,thanks for sharing.

I personally don't feel it's a placebo,i think this actually DID do something. :p

I think my phone runs a lil bit less laggy now,haven't seen anything else yet but it sure booted up faster now lol.

Try it,it won't hurt. :)
[Galaxy S III Original Android Development] Eddiemc:
Re: [Kernel][09/01] Perseus

Just wanted to mention that with this kernel yanks swap mod on the external sd works rather well.

I've tried a lot of swap, both on external sd and internal mem, but I've always had these small random freezes/stutters. So I've always reverted back to no swap. We'll, I tried it again with this kernel, and it seems to run nicely. No stutter, and it seems to have improved multitasking slightly. Just a heads up.
[Galaxy S III Original Android Development] Flypwnz:
Re: [Kernel][09/01] Perseus

Andrei. Any news about update or something new? :)
[Galaxy S III Original Android Development] Geoff.Costello:
Have you seen the ZSEMA1 Kernel?

Hi AndreiLux,,

I was hoping you had seen the new I9300ZSEMA1 firmware for the GT9300.. Release in early January its change log is a large jump forward from the XXELLC before. I am using a ROM based on it (Indies) and would love to be able to go back to your Kernel as I get fantastic battery life and no compromise on performance with it. And the 'buzz' seems to be that this has 'the proper' SDS fix code.

Cheers

Geoff Costello
[Galaxy S III Original Android Development] pat357:
You mean access files using ADB (push/pull) doesn't work for you ?

What is " Android File Transfer " ? Accessing your files as USB storage ?

It's unclear for me what is nor working 4 you....
[Galaxy S III Original Android Development] TheMasahiro:
Aye aye captain!!
[Galaxy S III Original Android Development] habylab:
Re: [Kernel][09/01] Perseus

"The buzz" doesn't matter, this has the fix included.
[Galaxy S III Original Android Development] boulek:
Re: [Kernel][09/01] Perseus

Guys i installed perseus in my brothers gs3 with polish samsung rom.He has the problem with headphones.I mean when he removed the headphones he didn't listen anything and had to reset the phone
[Galaxy S III Original Android Development] AndreiLux:
Re: [Kernel][09/01] Perseus

I honestly didn't touch the kernel code since I released the last version. However the plans for the next version are set and will be a major feature increase. Not much else to say than just be patient.

I tried switching to AndiP's sound implementation this morning but it was a mistake and waste of time so I dropped that, and since then only tried to figure out an outstanding bug with the minimum GPU freq limit not sticking correctly. That's all.

I hope I'll have more time/motivation by the end of the week to implement the other stuff.
[Galaxy S III Original Android Development] orangerot.:
AW: [Kernel][09/01] Perseus

Am I allowed to ask why you dropped andis sound engine? I temporary had his kernel installed for some testings with a Rom and the over saturation suppress in the sound engine sounded quiet good..
[Galaxy S III Original Android Development] nfsmw_gr:
Guys,what is andis sound engine?Could someone post a link?

I googled it but i didn't find anything.

Edit: Okay i found it,don't mind me.
[Galaxy S III Original Android Development] jeebspawnshop:
It would be safe to assume that Andrei dropped it for either - or both - of the following reasons:

1 - Didn't play nice with the current kernel/ROM set ups

2 - Didn't offer an appreciable increase in audio quality

:cowboy:
[Galaxy S III Original Android Development] Obagleyfreer:
Just want to make sure that by lowering the internal voltage I will not be causing any damage? I know that Lowering the voltage of CPU and GPU is safe but I don't know enough about internal voltage yet, especially the memory voltage.

Is there a risk of damage to either eMMC or any other internals by lowering te internal voltage too much? I'm worried about maybe corrupting memory from too lower voltage. Or is it pretty safe like CPU and GPU, only get freezes and things?

Thank you :)
[Galaxy S III Original Android Development] AndreiLux:
Re: [Kernel][09/01] Perseus

Mainly because it's still missing proper speaker tuning and some other things, and that I need to change settings because I maintain the kernel also for Note 2's. There's also some annoying bugs like not being able to boot with the sound mod on by default in the kernel. The DRC is currently the only advantage in it, I started to modify his implementation to include everything but it started to seem like a time sink to me when I have other things to work on now, so I left it be until I have nothing better to do.

Lowering internal will not cause any damage in the physical sense, but you might get some data corruption when it crashes.
[Galaxy S III Original Android Development] Infy_AsiX:
Re: [Kernel][09/01] Perseus

Fair enough. It has bonuses such as it's uniquely handy microphone adjust. Also it's DAC direct function doesn't break sound after using FM radio. Hopefully it improves enough and is implementable at a later stage.

?????? Galaxy S3 ??????
[Galaxy S III Original Android Development] andip71:
I have to hook in here to stop spreading wrong information !

a) The "annoying bug" to not boot with the sound mod on by default is

not a bug

, it is intention and by design. This is made to follow my kernel objectives. Hence, it will be always like that.

However, by changing exactly one define from OFF to ON this can be changed (or one echo command in ramfs).

The same applies to all default settings during load.

You could just ask me for information next time before doing wrong statements.

b) Speaker tuning is true, this is not yet implemented but on the roadmap for the next future.

c) Yes, the implementation is genuine for the S3. However, I know about developers that ported it without any issues to Note2 within an hour.

As stated above, I will still be adding features to it, no question.

Rest will stay as it is.

As always in life: Take it, take and modify it to match your requirements, ... or leave it.
[Galaxy S III Original Android Development] rlorange:
Re: [Kernel][09/01] Perseus

Each to their own applies to both developers and users. I'm sure Andrei meant no disrespect.

I love Perseus and your kernel Andi but I use DualBoot all the time and my own (meager) development efforts rely on it so Siyah is for me...
[Galaxy S III Original Android Development] AndreiLux:
The statement is not wrong, as your current implementation is, it is not possible to simply change BOEFFLA_SOUND_DEFAULT to have it enabled on boot without sending the kernel into a bootloop. This is your unchanged 1.4.3 implementation before I started to do my own modifications, by all definitions, this is a bug in the code. I assume it has to do with you having it compiled as a separate module and the drivers getting initialized in the wrong order instead of having an internal kill switch and compiled together with the WM8994 driver as Voodoo does, I didn't investigate further beyond that.

Please don't chime in accusing me of spreading wrong information when you don't know what I'm talking about in the first place.

I asked you to implement speaker tuning back in early December after you released it but you replied with some odd comment about it already being in when it's not. Whatever. I also know Simone uses it in NEAK unchanged but it's also using dead code as the LTE models all don't have an FM radio so that part of the code is unused/unwanted/unoptimal. And I'm also referring to the speaker tuning itself needing different band values as the Note 2 speaker has different characteristics and it causes distortion.

What's your point in coming in here? I was merely updating the people because several have asked me about it and I'm just stating some facts.

Thank you but I already modified your implementation for the most part (Speaker tuning is roughly in and working but some parts are conflicting with your design of the DRC) until I got fed up because I have more important features in the pipeline warranting spending time on.
[Galaxy S III Original Android Development] andip71:
To close this topic now forever (as it should not be the main topic in your thread, eh?), two things always help:

1) Precise information (the first information was useless, the second one helped)

2) Communication (if you had asked me it would have been much easier for you without waste of time, I fixed your reported startup issue within 5 minutes now, Github push on the way - btw your assumption about the reason was wrong, but no worries)

And now back to Perseus topic again please.

Andi
[Galaxy S III Original Android Development] AndreiLux:
Re: [Kernel][09/01] Perseus

I wasted 3 minutes on the startup issue, and that's why I said is an assumption. An hour or so in rewriting for speaker tuning, so don't worry about that indeed.

My point is that you were out of place in coming in accusing me of something which was just wrong. You're welcome to discuss anything else here as long as it's contributing.

Take your own communication advice in this case, I didn't attack you nor your work, the comments here were not directed towards you but just an update for the users. Please grow some damn respect before assuming the other party doesn't know what it's doing or trying to give a lecture on life.
[Galaxy S III Original Android Development] DirkStorck:
Guys...please don't fight with each other....Would love to see you two and gokhanmoral greating THAT monster kernel for our beloved device....

Each of your kernels has a beloved oustanding feature or works in a certain way better for...:D ;) :highfive:
[Galaxy S III Original Android Development] andip71:
Dirk, no worries. All is good.

For me it is only exchanging statements, which is valid practice. Should be via PM and not in thread, agreed, but sometimes it happens.

But as I said, for me the topic is closed and any more discussions I am happy to do via PM and not here.

Will now leave the thread again and only be here in reading mode as previously :)
[Galaxy S III Original Android Development] Agaranda:
Re: [Kernel][09/01] Perseus

With TWRP, I flash Perseus over Boeffla after wiping cache and dalvik and I get bootloop: Any solution?

Thanks in advance

I9300XXELLC, Boeffla 2.7b3, Earsonics SM3
[Galaxy S III Original Android Development] habylab:
Re: [Kernel][09/01] Perseus

Eagerly awaiting this kernels next update, been too long! Note, not a complaint or asking for an ETA.
[Galaxy S III Original Android Development] erto90:
Waiting makes thing better:D

something big is coming.. as samsung says xD
[Galaxy S III Original Android Development] Flypwnz:
Delete init.d folder.
[Galaxy S III Original Android Development] habylab:
Re: [Kernel][09/01] Perseus

I hope so!
[Galaxy S III Original Android Development] Tokarin:
Re: [Kernel][09/01] Perseus

Guys, I have a problem. I really want to use aosp roms, namely paranoid. But their kernels offer much less cutting edge development comparing to Perseus, namely the hotplug and deepsleep magic (the whole going back to single core then apply AFTR make me drool all over :D). So given the similarity, is there a way to port these 2 enhancements to the siyah kernel and use with aosp.

Just an idea, since I love this kernel so much... Cutting edge kernel and rom development together is what I'm suggesting
[Galaxy S III Original Android Development] thething869:
Re: [Kernel][09/01] Perseus

Hey Andrei, great kernel been using it for a while now and had no complaints

Just a suggestion with the setting for the value of sched_mc. By default you've set it to be 2 but I'm finding leaving it at 0 is better for hot plugging.. what seems to happen is that the workload seems to be biased more towards one core (which is what's supposed to happen lol) so under load the hot plug in requirements are met and another core is hot plugged in and frequency is scaled up. The problem is that cores are being hot plugged in but not much load is placed on these cores despite their frequency still being ramped up to be the same as the first core, meaning lots of wasted cpu cycles, taking longer for the load to be processed, thus longer for the extra cores to be hot plugged out. Realised this by monitoring it with perfmon. Correct me if I'm wrong or anything, or if there's something I'm missing..

So if you could give an option the change sched_mc in stweaks that would be great. I change manually in sys/devices/system/cpu but it resets on reboot so yea

cheers
[Galaxy S III Original Android Development] AndreiLux:
Re: [Kernel][09/01] Perseus

Yes and it's working as intended.

Sched_mc 2 merely biases threads onto non idle CPU cores to not wake them up. The CPUPower driver is the one in charge to do frequency based process biasing, and only I can configure that during compile. It will congregate load into CPU 0 until 500 MHz, however because of this we achieve very high residency times in the WFI state on the other cores so there is no dynamic power wastage, and minimal static leakage because the other cores might be on (we'll deal with that in the next version...).

Considering we've been getting a good battery boost because of this, there's no point in removing it.
[Galaxy S III Original Android Development] habylab:
Re: [Kernel][09/01] Perseus

Yes, but you'll probably have to research it yourself!
[Galaxy S III Original Android Development] thething869:
Re: [Kernel][09/01] Perseus

Ahh ok, so if I've understood correctly, sched_mc 2 isnt really the cause of what I'm talking about, it actually helps hot plugging and improve battery usage...

Though its quite odd how when sched_mc is set to 0, the load is more balanced when mulitple cores are active compared to when it is 2, just commenting.

Ok so I'm guessing the CPUPower driver logic is set to balance load post 500Mhz?

And yes I see your point about the high residency times, nice to see that'll be improved in the next version.
[Galaxy S III Original Android Development] Ausboy 2011:
Re: [Kernel][09/01] Perseus

1 core at 400 or so mhz wont drain as much as 3 or 4 cores on 200. :)
[Galaxy S III Original Android Development] AndreiLux:
sched_mc has nothing to do with hotplugging, it just prevents tasks to be scheduled onto cores in idle states. If the load exceeds a core capacity then it will schedule it on an additional core. Yes beyond 500MHz all the cores have equivalent weight distribution.

That's an apple to oranges comparison. Frequency is only part of the story, clock-gating plays a big role.
[Galaxy S III Original Android Development] thething869:
Re: [Kernel][09/01] Perseus

Yea I know that, I'm not arguing against hotplugging out at lower frequencies, I'm talking about load balancing at higher frequencies to process the load faster.

Don't get me wrong, load bias on cpu0 at lower frequencies is better to prevent non-idle cores from waking, which is exactly what Andrei has implemented

---------- Post added at 09:04 PM ---------- Previous post was at 08:32 PM ----------

Yes what I meant was by biasing the load, it prevents early hotplugging in of another core, sorry didn't explain myself properly for that.

Just post 500mhz, at times, say cpu0 may have load 80% running at 1.4ghz and cpu3, may have load of 30% but still running at 1.4ghz and it continues like this for a while.. is what I'm noticing possibly due to delay in updating the load on that CPU core from perfmon? Also is what I'm asking redundant as unless the first core is completely overloaded, balancing the load equally won't process it any faster, e.g. in m scenario if the loads were 100% and 10% they'd be processed in the same time as loads of 80% and 30% ?

EDIT: at this point would scaling down frequency of the core with less load be possible? (Not sure if it possible on mobile SoC's) or just pointless?

Sorry if I'm being a pain, just curious