yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] AndreiLux:
Bootanimations on the S3 are supposedly in a proprietary format now, so we'll have to see about it. As said, for now it's baby steps as long as I'm not able to molest the flash counter on the device myself.
[Galaxy S III Original Android Development] Kevinkuensken:
Wifi is not working on this Kernel
[Galaxy S III Original Android Development] xos84292:
Yes, me too...
[Galaxy S III Original Android Development] Mopral:
+1

Same issue with wifi...
[Galaxy S III Original Android Development] AndreiLux:
I guess it boots well then! Reuploaded a new version for Wifi, please test if you want to.
[Galaxy S III Original Android Development] simone201:
Strange, modules not loaded? :)

For me it worked perfectly from first build, using fully stock ramdisk
[Galaxy S III Original Android Development] Mopral:
Still no wifi with Alpha3.1
[Galaxy S III Original Android Development] nickwarn:
Same here
[Galaxy S III Original Android Development] AndreiLux:
Hmmm. I'm reverting to fully untouched ramdisk now, alpha3.2 uploaded.
[Galaxy S III Original Android Development] jonathanyong:
Just because the LF2 kernel might have some improvements not present in the current version of perseus and doing so might actually be a downgrade in some areas. It would be great if there was a changelog. Anyone know of one?

Do we have to wait for Samsung to release the source code for LF2 before we'd get an updated version of perseus?
[Galaxy S III Original Android Development] raubkatze:
Agree but as practice showed we (as users) simply can't see the big difference in these improvements ;) But anyway it's your own choice: wait or test it.
[Galaxy S III Original Android Development] mardon85:
This looks great. After a couple more updates (probably once you have your own phone and include the changes from the latest OTA). I'll be flashing my first Kernal. I'll be sure to send you a donation.

Thanks very much!
[Galaxy S III Original Android Development] AndreiLux:
Generally there is rarely major changes in source code to make noticeable differences. Samsung usually takes several months in-between source drops so it's very likely we'll stay with this base for quite a while and can't do much about it. Does LF2 have some improvements or are you just speculating that it might have improvements? They never provide change-logs.

@shahulvm incredible voltages.

GPU control has been in since the first version I released, you have to use command lines to echo the values to the class device.
[Galaxy S III Original Android Development] jonathanyong:
I was just speculating. I would have waited a week or so for an LF2 based perseus but if we're talking about several months before source is released, and if the changes aren't significant anyway, then forget it! Very happy with your kernel so thanks.
[Galaxy S III Original Android Development] raubkatze:
@AndreiLux a little beer - 46R30401D7451494H
[Galaxy S III Original Android Development] AndreiLux:
Thank you :) My first donation here. I will make it worth your generosity...
[Galaxy S III Original Android Development] raubkatze:
I think it'll be a popular kernel! Thanks a lot for the nice work and waiting for new builds!
[Galaxy S III Original Android Development] jonathanyong:
Nice voltages. I can't go quite as low on mine, but it's hard to tell which frequencies are causing lockups.

Does SetCPU's stress test cycle around all the frequencies testing each one or does it just test the highest? If not, is there an app that can stress test all frequencies to help with pinpointing which frequencies need more volts?
[Galaxy S III Original Android Development] zanzida:
Love your kernel Andrei, hope you get your device soon!

3JD98570EU9735646
[Galaxy S III Original Android Development] Fruktsallad:
Don't know about SetCPU's stress testing, but there's a good "cycling" one called StabilityTest. :-)
[Galaxy S III Original Android Development] jonathanyong:
Perfect, thanks!
[Galaxy S III Original Android Development] KMino:
Feedback, not sure what is wrong but get boot loops here. ALE8, was running .11, flashed .12 with Odin mobile, get boot loops. Luckily did a CWM backup, restoring boot only fixes it. Tried flashing twice just incase, same result. Haven't had any problems before, with flashing kernels etc.
[Galaxy S III Original Android Development] AndreiLux:
Anybody else having the same?
[Galaxy S III Original Android Development] chefaujus:
Me too. Boot loops.
[Galaxy S III Original Android Development] simone201:
They are caused by the module exception to make exfat working...it causes horrible bootloops everytime, with my kernel too :(

I think there is something wrong into it...and also i have tried both siyah-gs3 and latest franco.kernel (that have this patch and are booting) and the exfat modules cannot be loaded anyway

So there should be something else
[Galaxy S III Original Android Development] AndreiLux:
I'm going to freeze releases for a few days until I can test out some things, remove alpha12. I recommend using Siyah in the meantime.
[Galaxy S III Original Android Development] Mopral:
I use Siyah: phone boots and exFAT works...
[Galaxy S III Original Android Development] katestar:
Hi, is there any valid (so there is actually a difference) overclocking gpu frequencies after 440mhz stock. I am not bothered about overclocking cpu as I don't think it will make any noticeable difference, but the gpu is the first thing in this phone that will become outdated, just like every other phone. So I would love to overclock by a bit say to around 500mhz in the future to make it so there is a but of future proofing. I really hope the s3 isn't like the s2 when ocing the gpu, where you can overclock the s2 from 267 to 400mhz, but the heat and power drain makes it not feasible to run it at that high even at 1100mv(lowest stable voltage on my s2 at 400mhz), and the s2 is starting to get dated gpu wise, like for my s2 I would dream of 300-350mhz overclock, as it would be a usable increase (I wish there was a way to port scaling logic that allows the 350mhz step on the s3 to work on the s2, doubt it though). So may I ask what is the lowest frequency above 440mhz you can overclock by which is valid. Any help would be appreciated, I just love games on phones, so the gpu is so important to me.
[Galaxy S III Original Android Development] AndreiLux:
We haven't found that out yet, please ask again in a week's time.
[Galaxy S III Original Android Development] eseregin:
Should give, but time is going on, so things change.

Those time even Stweeks was completely banned 8-) But now - you use it

So this is completely hard work, IF Andrei will have some desire to do it - this appreciate - if not - appreciate as well
[Galaxy S III Original Android Development] Kasmott:
Im not sure if some of you has lost sound after playing FM radio and when trying to play stock music player there was no sound at all?: Had to delete FM.apk:eek:
[Galaxy S III Original Android Development] LaZyDood:
disable DAC direct.should fix your problem.
[Galaxy S III Original Android Development] gundal:
[TOOL] Recover from an stweaks bootloop

deleted
[Galaxy S III Original Android Development] Chillz88:
The overclock zip results in bootloop... And if you restore the stweaks using the bootloop fix zip, it restores back to the default note frequencies which is1600mhz which is ok.. I had previously tweaked my stweaks cpu to 1500.. Undervolted by 100-125mv.. And my gpu to 533 undervolted by 50 at each step... Amd its running fine..

But i have noticed the cpu running aggresively most of the times.. Which costs a little battery loss to me and has generated a little heat too.. If you have worked that out, could share that tweak here? :)
[Galaxy S III Original Android Development] AndreiLux:
I don't advise using the above zips as they are very flawed in their logic in respect how they work, and as stated above, may give boot-loops.
[Galaxy S III Original Android Development] shailraj:
Dear AndreiLux./and other seniors

Guys I have this problem my wifi direct doesn't seem to be working... I am able to connect to my wife's phone fine but when it comes to sending files it just keeps waiting to send files after I select her phone.... I have tried using it with another friend phone also same issue...

I am on omega v34 with latest perseus kernel

I have tried to do a clean flash of rom cleared dalvik cache, fixed permissions... Everything I could think of or guided by omega rom forum... Someone said that it might be kernel related... Though I am sure it's not have been using your kernel for a 3 weeks now and have no problems please help....

Any input, guidance will be very helpful
[Galaxy S III Original Android Development] AndreiLux:
It is caused by the kernel but I don't know the cause of it yet.
[Galaxy S III Original Android Development] shailraj:
Thnx a lot for your quick response...

One last question... Which kernel would you suggest I should try that does not face this problem and is similar in battery life to yours...

I know it's not the right type of question to ask but sorry am asking because this wifi direct issues have been troubling me for a while...

Thank you buddy
[Galaxy S III Original Android Development] shailraj:
Anyone??
[Galaxy S III Original Android Development] DirkStorck:
Hi. I have a small problem...I have copied some files using root explorer into a folder in my sdcard. When I connect the phone to USB I can't see them :(

Thank you!
[Galaxy S III Original Android Development] gundal:
unplug and replug that in it should show. Had that happen to me yesterday
[Galaxy S III Original Android Development] DirkStorck:
Thanks. Tried that but didn't work. :(

Files that I have copied to external sdcard have been showen.

Send from my Omega ROM powered SGS3 :)
[Galaxy S III Original Android Development] DSA:
Just wanted to give thanks to andreilux for these kernels...the latest just blows me away

Ive been testing it in every way possible and im struggling to find a single issue..I dont go looking generally, but this does everything i ask it to without problems

This is true development at work, thank you for using your knowledge for other people's benefit
[Galaxy S III Original Android Development] shailraj:
AndreiLux /Guys please help... Still not got a reply to my last post... Sorry for being pushy but I really need to get the wifi direct working... I am very reluctant shifting from this kernel as I love it! It's the best! Have had no problems other than this so far! Thnx AndreiLux! Really appreciate the hard work you have put in!
[Galaxy S III Original Android Development] eseregin:
Stock kernel?
[Galaxy S III Original Android Development] robogo1982:
Christ.

Download and flash them all, see which one fits you best.
[Galaxy S III Original Android Development] shailraj:
Thnx guys I tried stock and siyah they good, they don't the wifi direct issue but has high battery drain...

Now I am on yank555 kernel it seems to be holding good no wifi issue and better battery life compared to others... Though not as good as perseus....

Hope AndreiLux is able to find and fix the problem that is causing the wifi direct issues in his upcoming releases of the kernel because I really love perseus kernel its been the best so far in all the ones that I have tested!

Cheers keep up the good work AndreiLux
[Galaxy S III Original Android Development] habylab:
If I'm going to be perfectly honest, kernels do not make that much of a difference for me in terms of battery life.

...having said that, this is the best!

Question: I was just going through my settings and found that some of my GPU values for voltage were not set as the default, but I haven't changed them? Is this normal, or not? Thank you.
[Galaxy S III Original Android Development] LaZyDood:
to fix that,set stweaks to default.then reboot,then open stweaks and check if everything is in default config.if it is(except gpu voltages,of course;)),exit stweaks and go to /data/.perseus and delete customconfig.xml then open stweaks again,stweaks should now identify the correct default gpu voltage.
[Galaxy S III Original Android Development] MBurns2:
guys is it a problem if i only uv my cpu without uv also gpu ? i use stweaks for doing it.. thanks a lot
[Galaxy S III Original Android Development] LaZyDood:
its fine.
[Galaxy S III Original Android Development] robogo1982:
Wifi direct is working fine here, tried it with another S3, a Note 2 and a Galaxy Mini 2.
[Galaxy S III Original Android Development] shailraj:
wow! did your fix something??

did you manage to actually transfer files using wifi direct?? if yes thats great news will give it a try again!! :fingers-crossed:

AndreiLux himself said yesterday that wifi direct problem is a kernel one!

i can connect to my wife's s3 phone fine but when it comes to sending files i get waiting to send files notification in notification bar... and it gets stuck there...

yesterday i tried yank kernel i was able to transfer files fine...

but must say our perseus kernel is much much better in terms of performance and battery life!

what version of the perseus kernel have you installed....
[Galaxy S III Original Android Development] robogo1982:
27.2 and all works well here on LJ4. :what:
[Galaxy S III Original Android Development] shailraj:
thnx buddy!

your signature says u r using franco kernel...

i am talking abt perseus kernel on omega v34
[Galaxy S III Original Android Development] robogo1982:
Well I am too lazy to update my signature. :what:
[Galaxy S III Original Android Development] shailraj:
Lol

Thnx buddy again am trying perseus again!
[Galaxy S III Original Android Development] robogo1982:
Just tried it again, sending stuff to and fro my dad's Galaxy Mini 2 works just fine.
[Galaxy S III Original Android Development] Lither:
alpha27 now supports STweaks, will there be profiles uploaded to be used like Siyah?
[Galaxy S III Original Android Development] shailraj:
Thnx buddy.... I have also again installed perseus kernel was missing its battery life this time I again tried to send files via wifi direct....not working.... But I am able to receive files from another device... Don't know where I am goin wrong... With other kernels yank, siyah and stock all I am able to send and receive....

AndreiLux we need ur experience and expertise to know what's going wrong... I simply love your work and am willing to patiently wait for a solution... If there is any help I can be of with regards to logs or performing tests... I would like to volunteer myself

Thnx again guys for being so patient and helpful!

Good luck!
[Galaxy S III Original Android Development] GrayJack:
Talking about WiFi I have to state there is a number of WiFi disconnects with latest Perseus kernel on XXELKC. It looks like it is clearly kernel problem, because the signal is quite high (the router is actually is in 1 meter from me :) ) and teh problem is absent with stock and Siyah.

Hope Andrei will find a source and solution for this!
[Galaxy S III Original Android Development] bamer:
+1
[Galaxy S III Original Android Development] Tenacious:
No wifi issue here with perseus 27.2 and stock elkc rom.
[Galaxy S III Original Android Development] KS_Ho:
+1 my WiFi has been running flawlessly on ELKC
[Galaxy S III Original Android Development] bamer:
I ve got a question.

if i try too use the sound enhancement it's work very well with my headphone.

but absolutely not if a use Bluetooth.

is it just me ? or rom related (use wana lite latest) ? or kernel ?

thx for your great work.
[Galaxy S III Original Android Development] habylab:
Thanks but at the moment I think my lower GPU values are working well.
[Galaxy S III Original Android Development] andip71:
The sound enhancements only influence the WM1811 chip, which is used for analogue audio output.

Bluetooth is not covered by that, as it is a completely different signal path.

That was the same with the original Voodoo sound as well in former Galaxy S1 times.

Andi
[Galaxy S III Original Android Development] abelle_abelle:
Why is that after i install this it takes 3 hours and 15 minutes for me to charge from 0 - 100 %

usually it takes about 2 hours and 15 minutes to charge from 0-100 %
[Galaxy S III Original Android Development] shailraj:
I am getting this in kernel Wakelocks in BBS

What is this deleted_wake_lock?

And battery monitor?
[Galaxy S III Original Android Development] DirkStorck:
Hi... when I am using Perseus - with default settings - I have got the impression that as longer the phone runs the phone gets more and more laggy....not that it totaly freezes or is unusable...not at all...but the apps are stating slower....sometime up to 2-3 sec. Its only a personal impression...

I allthough have the impression that accessing the (external-)sdcard with Perseus is much faster than with Siyah. If I click on the symbol for in ternal storage in the file explorer of my PC the I can seen the file immediately..With Siyah I often seen the binoculars (to moving glasses) till I see the files (3 sec or so..)

EDIT: That long delay with showing the files seems to be only at first time showing the files with Siyah.

Thanks!
[Galaxy S III Original Android Development] MuertoKo:
+1 here, any way we can pull some logs or anything to help on this? I guess it's a usual issue with nearly all kernels though, after a day it gets chopier than after boot (or a few hours after, quite annoying when typing, not bigger issue)

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] yhrn:
deleted_wake_lock are wakelocks that no longer exists. The most common example is probably when you turn off wifi. In this case some wakelock structures that are used by wifi (e.g. wlan_rx_wake) are destroyed permanently and will then be reported as deleted_wake_lock. Next time you enable wifi the same kind of structures will be created but they are new instances so existing deleted_wake_lock will not be converted back to whatever they used to be.

battery_monitor is related to interrupts. Tungstwenty has written a lot of interesting stuff about both of these things in the BBS thread. If you have more questions about any of these things you should probably ask there.
[Galaxy S III Original Android Development] andreasy:
When I push the power button to wake my phone, it sometimes takes up to 7 seconds to wake up. Is this kernel related or Rom?
[Galaxy S III Original Android Development] MuertoKo:
7 seconds looks like just too much to be kernel related, never had this issue in any kernel I've used :S Is your phone laggy? Does it happen at any time, a few hours after boot, just after boot? The more info the best as at least afaik it's not a known issue. Can you try to pull some logs of it?
[Galaxy S III Original Android Development] shailraj:
1+

Just noticed it's taking longer than usual for charging....haven't noticed till now because have been charging my phone all night everyday.... Now after reading ur msg tried and got this It took me 3hrs 25 min to charge from 0% to 100%

Guess some setting has been changed in this new perseus kernel...
[Galaxy S III Original Android Development] andreasy:
It's random and I only have lag on dialer. I'm afraid I don't have any specific pattern at which it happens.
[Galaxy S III Original Android Development] DirkStorck:
Have that sometimes too that it takes "very" long till the phone wakes up.... :(
[Galaxy S III Original Android Development] Lither:
alpha27 now supports STweaks, will there be profiles uploaded to be used?
[Galaxy S III Original Android Development] robogo1982:
Did you undervolt/underclock? If you did, maybe you have overdone it a bit.
[Galaxy S III Original Android Development] andreasy:
no I haven't touch any settings. I use only defaults
[Galaxy S III Original Android Development] sachilleas:
I have a weird problem with alpha26. Sometimes when the phone fully charges i can hear the characteristic sound like i just plugged in the phone and the screen wakes up. It does this randomly, but only after 100% battery level so i suspect a kernel or Rom problem and not a faulty hardware.
[Galaxy S III Original Android Development] szkrable:
Hello,

Super kernel but i have a problem with phone connection. No signal when i make connect.

Wysyłane z mojego GT-I9300 za pomocą Tapatalk 2
[Galaxy S III Original Android Development] habylab:
Google is your friend! These ones are fairly self-explanatory, too.
[Galaxy S III Original Android Development] JethroCl:
When I install Perseus kernel, I'm having trouble with playing music over BT. After 10 to 15min it suddenly stops playing, and have to take my phone and press play again to resume. I mostly use the music player when I'm on my mtb and put my phone in backpack and use BT earpiece, so it is kind of annoying to stop several times, unload my backpack to search for my phone etc...

When installing default kernel (ARHD v17) I have no problems at all, but prefer to use Perseus kernel because of other advantages.
[Galaxy S III Original Android Development] sjh4:
no issues here with Bluetooth and perseus kernel, using mw600 headset, 2-3 hrs a day on commute
[Galaxy S III Original Android Development] andreasy:
I use omega with perseus and listen to music over bt for over an hour and this doesn't happen. Maybe it's your Rom or headset?
[Galaxy S III Original Android Development] mark2222:
When I use Tune in radio pro plugged into my hifi via aux when training this happens as well, unlock screen and have to press play as it has just stopped, bizarre. Never happened before jb, pain in the bum when it stops in the middle of a set though, must be some simple screen off setting we're missing.
[Galaxy S III Original Android Development] LaZyDood:
try checking Music Player>Settings>Music auto off

might have been set to something instead of "Off"
[Galaxy S III Original Android Development] erto90:
is possible to add speedmod sharpness tweak in next release?
[Galaxy S III Original Android Development] henrybravo:
Since this problem isn't happening universally among all Perseus users, it sounds like you guys are having problems with your respective music apps being terminated after a while when they're running in the background. Someone in the JKay thread has noticed the same thing on whatever ROM/kernel he is using:

If you guys are using any of those silly tweaks that mess with Android's native memory management by artificially freeing up RAM (such as V6 SuperCharger), I would suggest disabling it.
[Galaxy S III Original Android Development] mark2222:
Nope that's set to off

It's in foreground and then the screen is just turned off while I train, no memory tweaks, this was the first kernel I installed on JB and only have used stweaks to uv.
[Galaxy S III Original Android Development] henrybravo:
Anytime your screen is off, all running apps (even ones you had in the foreground) are considered background apps at that point. Next time the problem happens, check your Active Applications tab and see if your music app is still running. If it's still running, then the app itself may have stopped the music. If it's not running, well then it got terminated somehow.
[Galaxy S III Original Android Development] JethroCl:
I have no tweaks installed. Just ARHD v17, full wipe. Then the problem occurs. When listening with the wired headset, the problem persist. MP3-player is still in memory, in fact, it shows application when unlocking the screen after music has stopped.

It definitely has something to do with Perseus kernel, because I can reproduce the issue by installing Perseus and reinstall the stock kernel...
[Galaxy S III Original Android Development] henrybravo:
Ok good deal, the music app is definitely not being terminated then. :)
[Galaxy S III Original Android Development] AndreiLux:
You need to test it against (preferably) Siyah or another custom kernel, not the stock one. I personally never touched anything Bluetooth related in the kernel and also can't debug it on my phone since I don't have a headset.