yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] evil_moses:
Hi,

Been using your fantastic kernel for a while now without any issues. Unfortunately, today I've found one, and I'm hoping you can help......

I'm using Wanamlite Rom v5.1 that is based upon the latest stable 4.1.2 build and I've just discovered that video recording does not work at all, except for some reason when using the self facing camera (!). It either crashes upon pressing record or when pressing stop. I reflashed the stock kernel that was packed with the Rom and video recording works perfectly, so I'm sure it is kernel related.

I've searched this thread and seen that there have been issues with video recording, but the last post I can find on the matter is from the OP stating it had been fixed, so I'm unsure what to do.

I do not want to use the stock kernel as I need the CIFS module for samba sharing (I cannot find the module for the stock kernel I'm on) and I don't want to use Siyah as for some reason I get awful battery drain using it - saying that though, with two young children I need the video recording function working. My only workaround is to use this kernel day to day, but then flash stock when I want to record video - not an ideal solution!!

Any help or advice? Sorry for the long post, wanted to make myself clear (not very good at doing it in non .NET languages!!)

Thanks in advance for any help you can provide and please let me know if there is more info i can provide.
[Galaxy S III Original Android Development] cmajetic:
for me video recording works fine. Also on best resolution. Stock 4.2.1 rom.

i don't understand why so many use wanam and other roms that say "I am close to stock" but only have more bugs.
[Galaxy S III Original Android Development] Chris_84:
You can try the video recording fix. I got no problems here. But you can give it a shot. Maybe it's working for you.

Throwing out of the window from my flying Ferrari killer S3 driven by a proud omega team member :P
[Galaxy S III Original Android Development] hamer221:
Sound issue happens to me also with this kernel, when i switch listening between radio and media player, sound goes off.

Pease fix it asap.
[Galaxy S III Original Android Development] evil_moses:
I'm sorry my friend, I'm unaware of the fix, could you point me in the right direction??
[Galaxy S III Original Android Development] Chris_84:
Try this and report back if it works please.

http://db.tt/sK9AYvM8

Throwing out of the window from my flying Ferrari killer S3 driven by a proud omega team member :P
[Galaxy S III Original Android Development] cyberspaceguy:
I have problem with yiur last firmware.. With foxhoud 1.6 and tethering.... Tethering is active on my phone but no stuff can access.... How is it possible?

Any tips? Thanks..... Somebody tell me to change kernel with other for my issues... But I like this kernel I would like to understand if there is a fix!
[Galaxy S III Original Android Development] KennyLegend:
It's an issue with this kernel. AndreiLux said this a few pages back and doesn't know the solution yet.

I'm sure it will come.

Sent from my GT-I9300
[Galaxy S III Original Android Development] AndreiLux:
I said I knew about S-Beam not working, I never mentioned anything about tethering or heard about that issue.
[Galaxy S III Original Android Development] cyberspaceguy:
I have problem with tethering..........

Inviato dal mio GT-P3110 con Tapatalk 2
[Galaxy S III Original Android Development] gnam:
But the CRT Off issue with this kernel has been solved or not??
[Galaxy S III Original Android Development] Cy4n1d3:
As CRT-off works fine here, I guess it is.
[Galaxy S III Original Android Development] evil_moses:
That worked perfectly, thank you so much. What did the zip do? What was the problem?
[Galaxy S III Original Android Development] Chris_84:
It just replace the lib files for video with the one from 4.1.1. Glade it worked for you. :)

Throwing out of the window from my flying Ferrari killer S3 driven by a proud omega team member :P
[Galaxy S III Original Android Development] parhelion69:
A workaround has been reported already, go to Stweaks, audio tab and Disable "DAC direct"
[Galaxy S III Original Android Development] Highlander11:
(OT: I take it that you have made quite a generous donation to Andrei to be making demands for fixing things "asap"?? :what: :D END OT)

@Andrei, I have seen the error of my ways :p and am back on the Perseus kernel with ARHD v17.0 :D
[Galaxy S III Original Android Development] ThaiM:
How can I enable logcat with Perseus Alpha 27?

*Edit* nm...
[Galaxy S III Original Android Development] RtN89:
Hi All,

Found a bug (I am using this kernel with Vikingway Rom 2.1) after listening to FM radio... calls will not have any sound and also both PowerAmp and Music Player will not produce any sound even though when I turn the radio on there is sound again.
[Galaxy S III Original Android Development] KS_Ho:
Disable DAC Direct, this problem has been reported already several times :)
[Galaxy S III Original Android Development] RtN89:
Ah woops! Thanks for the help! Should put a "known bugs" list on the OP. I tried that myself before coming onto here and asking but probably didnt work because didnt reboot..
[Galaxy S III Original Android Development] romeo57:
Sorry if this is a noob question, i read around about "UV -50mV" .

Is it the difference between clock voltages or minus 50 for every step, in set cpu's Voltage tab?
[Galaxy S III Original Android Development] erto90:
i think there is the choice there: if you put -50, it will put -50 on every freq, the other method let you choose every voltage for every freq
[Galaxy S III Original Android Development] GrayJack:
Andrei, could you please explain why GPU Max Frequency is 440MHz by default in Perseus? It looks like a little bit underclocked, because almost everybody use 640 Mhz.

At the same time the maximum frequency of CPU looks pretty normal - 1400 MHz.
[Galaxy S III Original Android Development] MuertoKo:
Let me guess but those are the stock values. What do you mean by default? You can OC GPU a lot in STweaks, as well as CPU :S
[Galaxy S III Original Android Development] GrayJack:
Yes, I know that, and "by default" means figures installed by default in STWeaks.

And I was surprised because for instance Siyah uses 640 MHz by default as for GPU.
[Galaxy S III Original Android Development] siavash_Skh:
Hello everyone

I have installed foxhound rom (1.6) + Perseus Kernel (27.2)

the battery status is here : ( the first 10 hours the phone was at sleep status and battery percentage changed from 100 to 96, All the 21 hours the wifi was on and connected)

is my battery status is good ? is it normal ? or not ? Can it be better ?

Is there a tutorial about stweaks setting in this kernel ? for example when we want have a better battery performance what we should do ? what we should change ?
[Galaxy S III Original Android Development] mamba720027:
Battery performance will vary depending on what you're doing with your phone for example reading on the web u use less vs watching a video use more.

I'm running latest Omega rom with Perseus 27.2 kernel and the most effective way to get more out of battery is by UV. Mine CPU is OC 1700mhz an UV -100 and some fquencys -125 while GPU is UV -100 scaleing 106mhz to 266mhz.

These settings might not work for you but that's my setup with a few extra tweaks in setcpu im experimenting with to prevent some of the core from going online too early.

Here's my battery status going and coming home from work,sometimes I got WiFi on dureing brake and sometimes I use the airplane mode in train.

Sent from my GT-I9300
[Galaxy S III Original Android Development] siavash_Skh:
thank you so much

but I afraid of changing the setting randomly, maybe some of my changes will be harmfull for the device, so how can I found how works each part of stweak ?
[Galaxy S III Original Android Development] AndreiLux:
New version. Should fix all the smaller STweaks related bugs and a few new things. Try to break it.
[Galaxy S III Original Android Development] erto90:
Wow new schedulers.. Is the new default one better for battery too?
[Galaxy S III Original Android Development] AndreiLux:
I doubt I/O schedulers have any measurable effect on battery at all. If anything people who might do gaming will see the biggest effect probably in loading times or fluidity when something is being loaded. I don't want to overstate the IO myth as some other developers do; most probably won't notice the differences in a blind test. Apps will load faster though. Use ROW for the best raw speeds.
[Galaxy S III Original Android Development] gundal:
STWEAKS PROFILES! and proper bootloop fix.

Alright! now that Perseus Kernel .28 is out we have a new added feature that lets us implement override profiles!

What does this mean?

Well now this UNCHECK SET ON BOOT zip will actually just update your current default.profile and uncheck the set on boot options.

Which makes it the best fix for a bootloop, because you can then go back in to your old settings that failed and modify them.

EDIT: The s3 chip quality is so different from the n2 that im not going to include any profiles as likely none will work(i dont have an i9000 to test it on), the 2 files ive attached are still safe to use.

Profile 0 is the DEFAULT profile the kernel came with. (it just deletes your profile and rebuilds it so its safe for all versions inlcuding S3-i9000)

I will also have a zip for My custom governor tweaks detailed below:

here is my logic

defaults parameter mine

30000 sampling rate 20000

82 up threshold 90

5 down diff 10

40% thres for response 81

1200 freq for fast down 1600

95 up thres fast down 98

37 up step 18

6 splice amount 4

13 down diff 8

With the default settings when the load is measured if the cpu load is over 82% off current freq step it will scale up.

New logic added in perseus .27 now gives us 3 up steps instead of just a fixed one.

so your cpu will step up more aggressively based on how much above the threshold it is, not just if its over, this is

great.

Right now, if we are coming in with a

load of 83%-88% we increase freq by 300mHz

if we are 89-94% we increase freq by 400 mHz and

if we are 94-100% then we increase freq by 700 mHz.

This is too fast for me.

For a few reasons the main one being that the amount we jump has gone up because our max cpu is 1800 instead of 1600 (at 1600 the jump ups are 200,300,600mhz)

The logic I use on my N2 is as follows:

Load of 90-94 = 100 mhz jump

load of 95-98 = 200 mhz jump

load of 99-100 = 400 mhz jump

The responsiveness of the phone is not compromised at all, the cpu just steps up less and only when it has really high

loads. It still gets to 1800 and does many operations there, but it comes out of 1800 fast and when it jumps down it jumps

down further. The fastdown has been upped from 1200 to 1600 , meaning it now requires 98% or higher load to jump up when above 1600 mhz not 1200 mhz, I found that the phone was always in 1800 or like way lower, never in the 1700 - 1200 range as it used to need 95% load to be in that range. The cores hotplug has been slightly changed to turn off cores quicker when not in use and takes more samples to turn them on so they only turn on if load exists for longer duration of time.

PLEASE NOTE

Flashing any of these zips OTHER THEN THE UNCHECK SET ON BOOT will REMOVE your STWEAKS settings and replace them with the profile. PLEASE back up your profile if you want to save it.

Where is it?

/data/.perseus/default.profile << back this guy up. rename to default.profile2 works. or copy to sdcard.
[Galaxy S III Original Android Development] zappoo:
Awesome but I only see profile 0
[Galaxy S III Original Android Development] GrayJack:
And again strange things :)

According to Stweaks

But default internal storage scheduler is noop by default after kernel installation. SD Card scheduler is FIOPS - it's true.

So why noop?
[Galaxy S III Original Android Development] mamba720027:
If you wanna know what works for u such as UV then do it proportionately like -25 on each cpu frequency and do not check "setonboot" or whatever the option is for saving your settings on bootup. Just let the phone run and try to break it by maybe playing games or watch videos for a few hours, something to push the CPU then if all is stable continue -25 again until u figure the limit. This concept is the basic and can also be applied to UV the GPU. As for how fast the CPU can run,I would recommend seting it to 1600mhz and see how it runs for a few hours,if it reboots then up the volt by +25 etc. If all is good try 1700mhz. This the only tricky part when finding out what works for u,everything else should left default, most of the other settings default is good.

Sent from my GT-I9300
[Galaxy S III Original Android Development] johho:
I can only see profile 0 and the set on boot zip too.

Only these two files for download

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] www1:
Any chance to see kernel for n8000? :)

Inviato dal mio GT-N8000 con Tapatalk 2
[Galaxy S III Original Android Development] AndreiLux:
No.

___

I apparently broke exFat with the new block drivers; I had my card formatted differently and forgot to test that. I will look into it.
[Galaxy S III Original Android Development] Highlander11:
Using v28: This may be a "late night question", but under the STweaks GPU tab->440MHz->the default voltage is given as 1013mV. However, the current value on my phone was displayed as 1014mV. Trying to use the slider to set the value to the default does not work, as the step sizes of the slider are fixed to the nearest multiple of 25mV (giving 1000mV or 1025mV).

How do I set ONLY THIS value to the default? :confused:
[Galaxy S III Original Android Development] cmajetic:
lol this seems to be a typing mistake but 1mV won't matter.

btw row scheduler is really great, contacts and phone open a lot faster. thanks so much.
[Galaxy S III Original Android Development] Highlander11:
I know :D, but I would like to know HOW TO set a single value to the recommended default value? :rolleyes:
[Galaxy S III Original Android Development] qwerty12:
You can edit /data/.perseus/default.profile to your heart's content and then run /res/uci.sh apply. It worked for me anyway, when I was diffing my changes with AndreiLux's fixes to STweaks settings in a newer version of Perseus.
[Galaxy S III Original Android Development] gundal:
can also reboot after making changes there. if set on boot is selected
[Galaxy S III Original Android Development] borjaag:
Can't get into Stweaks, FC's :(
[Galaxy S III Original Android Development] :
STweaks already broken, didn't even try to break it :P
[Galaxy S III Original Android Development] gundal:
edit: wrong forum.
[Galaxy S III Original Android Development] Chillz88:
i get high and aggresive cpu usage on the perseus when checking it on cpu tool.. Anyone else??
[Galaxy S III Original Android Development] Tenacious:
Same here after instaling alfa 28, trayed reflashing deleting perseus folder in data and stweaks from system and then rebooting still fc. Reinstalled 27.2 first time it fc but second time opend fine.

Log for stweak fc http://db.tt/o9wBhjjY
[Galaxy S III Original Android Development] yhrn:
No problems here. Haven't done that much, only applied a few changes, but no obvious issues.
[Galaxy S III Original Android Development] gundal:
yes i noticed this too, which is why im releasing my profiles. one is for custom governor tweaks that greatly reduce the aggressiveness and core uptime

look for it in the longer post a few posts back later tonight
[Galaxy S III Original Android Development] habylab:
My steaks is fine, and I've pushed it as hard as I can.
[Galaxy S III Original Android Development] cgvelmax:
I have problem with my sd 64gb, the phone doesnt recognize.
[Galaxy S III Original Android Development] yhrn:
AndreiLux said a few posts back that the latest update broke exFAT support and he's looking into it so if your SD card is exFAT formatted that's why.
[Galaxy S III Original Android Development] aeroxdefocu:
I've a problem with call audio. When turn on radio FM and try to call someone i haven't call audio and only solution is reboot phone!! :crying::crying:

All work fine if use MP3 player!!:confused::confused:
[Galaxy S III Original Android Development] yhrn:
Search this thread for 'FM' and you'll see that this has been reported many times. Disable 'DAC direct' in STweaks as a workaround.
[Galaxy S III Original Android Development] Tenacious:
This was discussed before disabled dac direct.
[Galaxy S III Original Android Development] KennyLegend:
I don't agree with the above mate. Uv cpu and gpu is NOT the best way to save battery and actually will yield you very little in terms of battery life. Its a lot more effective in keeping ur phone running at lower temperatures.

Sent from my GT-I9300
[Galaxy S III Original Android Development] gundal:
undervolting keeps temperatures down ;)

and it might not be the best way buts its one of the MOST efficient ways

when I say efficient i am reffering to the fact that you dont have to gimp your device.

like turning off auto sync or underclock to 1000 mhz or lower ur screen brighhtness below whats comfortable

gains without any sacrifices
[Galaxy S III Original Android Development] habylab:
What IS the best way then in your opinion?
[Galaxy S III Original Android Development] KennyLegend:
No.. It doesn't save much battery,...

U/v by - 100mV might save u (if ur lucky) approx 10 mins over the cycle. U/c to,.. Say 1200Mhz will save u more than that.

Turning down ur screen brightness will save u more again.

Maximizing efficiency by eliminating ur wakelocks will save u more again.

So u are not correct, it is NOT one of the most efficient ways to save battery.

Sent from my GT-I9300
[Galaxy S III Original Android Development] cyberspaceguy:
New version resolves tethering problem? Thanks!
[Galaxy S III Original Android Development] faithhh:
i wonder too?
[Galaxy S III Original Android Development] faithhh:
Stweaks nit working crash all time with last perseus any1 confirm that?
[Galaxy S III Original Android Development] :
read 1 page before...
[Galaxy S III Original Android Development] mamba720027:
If undervolting is not one of the most efficient ways to save battery then it looks like all these kernel devs have wasted their time into hacking kernels to produce a custom kernel and implementing the feature to UV from the begining of time it seems. Your method in gaining battery by underclocking is correct and if you don't do some UV their you will hardly save anything,this was proven in the old nexus s forum ages ago by UC/UV u save more battery but these quadcores have come a long way since and I must stress that UV does not only keep temp down it does save more battery than setting your screen to the lowest brightness(auto bright is more effective) ,slapping a black wallpaper on your beautifull amoled screen (decreasing the screen MHz+volt may yield better result),using the OS built in powersave feature (this one is a gimmick) and yes tried all of these and does absolutely little or nothing to notice.Furthermore depending on the logic of your governor and various other core settings if u just bring the CPU freq from say 1400mhz to 1000mhz it may actually burn more battery than u think because your kernel is set to handle loads differently and as such u may notice your CPU being on 1000mhz more frequently than staying at say 200mhz-400mhz when u had it set to scale 200mhz-1400mhz before. One of your points in "eliminateing wakelocks" is a sucker for battery performance indeed,esp if you have every account set on sync ever 5mins like fbook (the plague of battery sucker and memory eater). So a combination of all these things have an impact on battery performance and I am too lazy to mention it all like turning off "hepticfeed back" etc. I'm more concern in battery improvements that can be noticed.

Here's a link with a guide explaining indepth on wakelocks from another form for those who likes to read.

xdaforums.com/showthread.php?t=1878828

Edit: On v28 perseus,having same prob as few users pages back getting into stweaks,force closes.

Sent from my GT-I9300
[Galaxy S III Original Android Development] gnam:
With the last version does Crt off effect works again?
[Galaxy S III Original Android Development] svs57:
Great!!!

Does this mean that I can switch also internal SD to ext4?

Before this future I still thinking what kernel use.

Now I choose Perseus.

Thank you.

What version of toolchains do you use to compile kernel?

PS

Does Android 4.1.2 recognize and mount ext4 SD cards while boot or I need write init.d script to mount its?
[Galaxy S III Original Android Development] Chillz88:
Kernel is smooth as hell..thanks andrei.. But i have just one problem.. Whenever i use ext2internalsd swap mod with this kernel i see twice the folders whenever i reboot.. Never happens with other kernels.. If i wipe dalvik and cache and reboot it works.. But goes back to showing double when i reboot again.. Something wrong with implementing init.d scripts at boot??

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

This is the mod... ^
[Galaxy S III Original Android Development] psyntific:
Hi andrei I think there is a slight problem with the values that are being displayed for voltages.. Do I have to uninstall previous stweak before installing this kernel?

Sent from my GT-I9300 on ARHD 17 with perseus 28
[Galaxy S III Original Android Development] eden1988:
For those who have problems with STweaks FC-ing maybe you can try flashing Gundal's PERSEUS_GUNDAL_PROFILE0.zip (reset to default profile, please make a backup first if you want to keep yours) then flash Perseus alpha 28, STweaks works fine for me after I wipe partition cache, dalvik-cache and fix permission.

---------- Post added at 04:09 PM ---------- Previous post was at 04:00 PM ----------

Gundal, mind sharing with us what is your custom governor tweaks changes in your governor tweaks zip?
[Galaxy S III Original Android Development] MuertoKo:
Please, just please, use different paragraphs when u write such a biggie, almost blind after reading O.o

Anyway, back to topic, can you provide any tests that prove that UV saves battery? And I mean using this CPU, because every cpu is a world as you already said

I did some testing long time ago on my Sensation and there proved it to have a null effect (2% more, and that's up to my testing error maybe), but I'd like to read a proper UV review on this CPU as it might be completely different!

Anyway, UC by 50mv when a frequency uses 1000mV for example means just a tiny 5% less voltage in the best case...

Just sharing thoughts anyway, I don't feel like having a risk to a single random reboot for a 2% more juice anyway :P

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] KennyLegend:
You are right, it's not worth trying heavy uv just to end up with instability or bootloop... For what? A few mins extra battery? Pffttt....

That guy has his own theories, but the simple fact is most devs are not providing customers kernels for the sole purpose of uv'ing. That's just a silly comment.

And his essay? tl:dr

Sent from my GT-I9300
[Galaxy S III Original Android Development] mamba720027:
Its not the greatest improvement like everyone would expect (9hours screen + 2days) but 2% is 10mins of usage on extreme use, and could be more depending on what you're doing in my experience.

I find testing a CPU+kernel useless esp those reviews because like I said,it depends on what you use will reflect on how much battery u use. Also since theirs not just one Android device on the market and many phones with many kockamania hardware I doubt many of the apps are fully optimize to support every phone for efficiency (think why Apple apps and phone performs so well with less battery capacity and why their so strict with placeing an app out their).

Sent from my GT-I9300
[Galaxy S III Original Android Development] GrayJack:
I wonder why changing I/O scheduler to either noop or fiops after installing your My cusrom governor tweaks leads to boot loop at my s3-i9300.