yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] alvaretto:
Hi mates. I've been checking the last pages but couldnt find any info. I want to try eric's profile, but i can find the path /data/.perseus . I am using ES file explorer with root options enabled. I get into the /data folder but inside it doesn"t exist the .perseus folder. I already downloaded stweaks and stweaksprofile apks. Excuse me for asking this here but read that other users were happy with the battery life using this profile and wanted to give it a try.

Thanks in advance.
[Galaxy S III Original Android Development] ahac85:
You need to go in to settings and then file settings and tick show hidden files

Sent from my GT-I9300
[Galaxy S III Original Android Development] agusdallalba:
In ES explorer "File Settings" the second checkmark reads “Show files whose name start with a '.'”. Did you tick it?
[Galaxy S III Original Android Development] alvaretto:
Thanks a lot pal. I didnt knew that option. :D thanks a lot!
[Galaxy S III Original Android Development] ManDone.vRs:
Just flashed this kernel , almost 23 hours , with data mobile , just whatsapp and facebook using , every 1 , 2 hours , 15 -20 minutes ... and middle brightness level ... ;)
[Galaxy S III Original Android Development] cba1986:
Sory for the offtopic but i have to comment about the amazing battery life i getting with this kernel + MC2. It last for 1d,5h and 3:45 hours of screen time. Mostly on WIFI with some 3g, browsing, facebook, a couple of hours of music and light gaming.
[Galaxy S III Original Android Development] uggies:
Bump. Please anyone?
[Galaxy S III Original Android Development] STAticKY:
Not sure if it has the screen calibration but its got plenty from this kernel packed into it. Hope it helps dude
[Galaxy S III Original Android Development] Tokarin:
Temasek's kernel on his kang thread does have most of the things Andreilux introduced. It works on most AOSP roms, temasek just doesn't want to make it public cause he's cannot ensure the support for other roms.

Still waiting for that one day Andrei consider AOSP, :(

Sent from my GT-I9300
[Galaxy S III Original Android Development] userguy:
Is there an english description of this somewhere? Or could somebody quickly explain to me how exactly it works?

Thanks in advance!

Edit:

The reason i want to use this is, that with perseus kernel i'm currently actually losing more battery than even with stock kernel. This seems kind off weird. So thats why i wanted to have it clean before installing perseus again!
[Galaxy S III Original Android Development] deom2i:
Its clear kernel lef over files so that it can instal fresh files without a mix.

---------- Post added at 08:38 AM ---------- Previous post was at 08:34 AM ----------

Guys my stuck issue is also with siyah kernel. I still get black screen with lockscreen only responding.:(

Im still searching for the problem cause...
[Galaxy S III Original Android Development] pacman2009:
Hello all

Iv just moved from htc sensation rooted and moded roms. To a s3 i9300 international on rooted stock o2 rom. Iv been reading these

Forums for days now. Trying to take everything thing in, now I'm getting myself all confused.. And have across this kernel. Im i correct in thinking that its safe to use on my stock rom? Iv done a full backup of my rom. ? Any thing more information i can give you just ask. Thanks all
[Galaxy S III Original Android Development] Olioaglio:
Anyone has an idea or can confirm this?

Sorry for bumping this up again...

It really nags me and I'm wondering if I'm the only one who is being affected from this bug.

Cheers, Olioaglio
[Galaxy S III Original Android Development] Tokarin:
I read somewhere that the all share dongle now required you to be on stock bootloader. Check on that.

Sent from my GT-I9300
[Galaxy S III Original Android Development] ManDone.vRs:
Mby witth low brightness level :)
[Galaxy S III Original Android Development] Olioaglio:
Counter is 0 and states offical. No triangle at boot. Concerning official bootloader: After flashing siyah or boeffla kernel (no other changes) the dongle starts working again at once without problems. Flashing perseus again and...baaam...reboot as described some seconds after starting allshare service.

So my conclusion is to blame the kernel on this until anyone confirm it working with perseus.

Olioaglio
[Galaxy S III Original Android Development] cba1986:
25 % brightness actually. Find that is more than enough in my enviroment.
[Galaxy S III Original Android Development] AndreiLux:
Nobody has managed to provide me a viable log on this issue in the last 8 months, and since I don't have the AllCast dongle, the issue won't fix itself anytime soon.
[Galaxy S III Original Android Development] tisazalay:
Welcome back. Hope you enjoyed your trip.
[Galaxy S III Original Android Development] slom33k:
Something bad happened with my s3 with version 25, I mean my phone freezed few times just like that... I downgraded to 24.3 and testing it... anyway great work mate!

Galaxy Suoma SIII
[Galaxy S III Original Android Development] cba1986:
v25 is a little old the current version is v35
[Galaxy S III Original Android Development] papakaliati:
He meant v35 i quess since he mentioned 24.3( being 34.3 i quess)
[Galaxy S III Original Android Development] nfsmw_gr:
@Andreilux

Sorry if it is too much to ask,but is there any possibility you can fix the mono/stereo audio issue?

I don't have a paypal account or anything but it's so anoying that i'd go to a bank and create an acount just to fix this single bug and pay you for it.

Seriously i'd do that,i'm getting desperate about this. :(

I have a very decent headset and the music randomly switches to mono from times to times,and the audio sounds very crappy and sometimes a bit distorted too.

Thanks for your work,hope you can take a look at this.
[Galaxy S III Original Android Development] drakester09:
I grew annoyed at this and that the workaround was within STweaks, which takes several seconds to load.

You might use this crudely made app to change sound settings, it will be faster.

http://db.tt/ZDM8oxa6

No one but you is responsible if you device dies by using this app. ;)

Also all settings are applied immediately.
[Galaxy S III Original Android Development] NeoBlade:
I would suggest upgrading your ROM. I'm currently using the latest Perseus (35) and Omega 43.2 ROM (XXEMC2) and it works fine to a Samsung smart TV and my XBMC media centre. Check to see if the ROM base is updated to EMC2 and that you've applied the AllShare Dongle firmware update too via the Play store.
[Galaxy S III Original Android Development] nfsmw_gr:
Thank you for this. :)

Although the issue is not that STweaks load slow and every time i have to toggle mono/stereo i have to wait some time.

I've locked in memory STweaks with xposed framework so the app never gets killed,unless i kill it myself of course,so i toggle mono/stereo fast.

The issue is the bug itself though,this shouldn't be happening at all...

If it could be completely removed from the sound engine without causing any issues that would be great!

I think many players have mono downmix(software yes,but gets the job done without causing trouble) and also there's a widget/setting that toggles mono/stereo audio output build by samsung (but i don't know if that has anything to do with the sound engine the kernel uses or if it's software downmix though).

EDIT:I read the post again and you mention "that the workaround was within STweaks".

You mean this app you have developed/found/or anything else makes the toggle work like it should and after that everything will be okay?

Or that it'll just load faster than STweaks so i can toggle the mono/stereo setting faster than before?
[Galaxy S III Original Android Development] drakester09:
Nah, it only exposes the interface, it does not detect or fix the state.

I might test that later today.
[Galaxy S III Original Android Development] eric-filth:
Sorry disturb with screenshots showing more battery life, but this screens i really have to show for you guys.

This screens is from user Mutley-BR, he allowed to me publish here.

He using Perseus v35, with my ROM (include this profile what a shared here)

:o

Enviado do meu Nexus 7
[Galaxy S III Original Android Development] bsamardzhiev:
Hi there,

When I try to set personal alarm ring tone, it says ok. But in the morning it plays the default one. Is this aomewfrom the kernel? How should I fix it?

Thanks in advance!
[Galaxy S III Original Android Development] impe90:
Can we use a micro-sd (formatted in linux-swap) for increase ram memory of our sgs3 with this kernel?
[Galaxy S III Original Android Development] STAticKY:
Using yanks hardswap script i think you can. Im pretty sure this kernel supports hardswap...
[Galaxy S III Original Android Development] nfsmw_gr:
Yes,you can do that but i don't know if having the whole card formated as swap would work.

I'd suggest formatting the card in two partitions,one linux-swap and the other as normal fat32 filesystem which works fine. :)
[Galaxy S III Original Android Development] chiupc94:
Eric regarding your profile I have problem after applying it. My phone shut off itself overnight. I have gpu rendering enabled.
[Galaxy S III Original Android Development] Steve_max:
Eric's profile includes voltages. I didn't examine them, but (in the non-undervolted version) those are probably the default voltages for his phone. We know that each CPU is made differently; they are classified in different levels (ASV), and each ASV has its own voltage table. So, if his CPU is a great undervolter (say, ASV8) and yours is not that good (say, ASV2), your CPU has a high chance of not working with his default voltages.

See the default voltages for each ASV level at https://github.com/AndreiLux/Perseus-S3/blob/master/arch/arm/mach-exynos/cpufreq-4x12.c search for asv_voltage_step_12_5. Compare your "default" voltages on STweaks to each column and you will find your ASV level (mine is ASV5, and it seems to handle Eric's undervolted values pretty well).
[Galaxy S III Original Android Development] chiupc94:
So what I should do is increasing the voltage value in his profile??
[Galaxy S III Original Android Development] The Broken:
Mine is asv3 and I even undervolted Eric's settings..

Pretty interesting link!
[Galaxy S III Original Android Development] STAticKY:
Very nice find... had no idea they had diffrent voltage levels accross one model of phones... i guess its like how they bin computer processors...

EDIT: Turns out mine is asv2 :(

[MENTION=4347387]Steve_max[/MENTION]: is the rev_2 voltage table for the note2?
[Galaxy S III Original Android Development] zeljkobo12:
I had problem too, after applying Eric's profile, undervolted one.

EFS partition was lost, after using profile for about one hour.

So I guess everybody should be careful when applying UV profile.
[Galaxy S III Original Android Development] STAticKY:
How could that have happened?
[Galaxy S III Original Android Development] zeljkobo12:
Phone became unresponsive, after that bootloop.

Backup from recovery didn't help. I could enter in CM 10.1 with siyah kernel and IMEI was blank.

Only flashing original samsung rom helped.

After that backup did work, and IMEI is OK.

I really don't know what happened...
[Galaxy S III Original Android Development] sherlock5545:
If efs was lost, unless you had a backup, I don't think it would reappear by magic. Might have been a problem with the modem, though.

Sent from my GT-I9300
[Galaxy S III Original Android Development] offgrey:
I'm not sure if I'm reading what the dude said right but he said that it wasn't by magic that he got his imei back. He was able to restore a backup.

Edit: Read it again. and no, I wasn't reading it right. lol
[Galaxy S III Original Android Development] Olioaglio:
Mine is ASV2 :( according to the default value voltage table

Any suggestions for possible UV values for this ASV level?

ATM I have

1325000 for 1600 Mhz (my phone cannot handle more than 1600 stable)

1300000 for 1500 Mhz

1262500 for 1400 Mhz

1200000 for 1300 Mhz

1175000 for 1200 Mhz

1125000 for 1100 Mhz

1075000 for 1000 Mhz

Rest downwards is stock voltages.

Olioaglio

Sent from my SGS3

---------- Post added at 06:21 PM ---------- Previous post was at 06:15 PM ----------

Thanks for your suggestion. Using Wanam Lite 6.5 (EMC3 base) since yesterday but unfortunately problem stays. NeoBlade, but you are using TV built in Allshare Hardware, not the external dongle, right? It may be a problem with only the dongle.

Olioaglio

Sent from my SGS3
[Galaxy S III Original Android Development] tolis626:
While you cannot expect miracles with ASV2,I think you can achieve a 50mV undervolt across the frequency table.My phone is ASV3,but I wouldn't guess it was because it undervolts more than just fine.It can't run at 1800MHz,but it can run at 1704MHz with 1325mV.Strange stuff these tables...
[Galaxy S III Original Android Development] sherlock5545:
Mine appears to be ASV4, and those undervoltings work just fine.

Sent from my GT-I9300
[Galaxy S III Original Android Development] cba1986:
MIne is also ASV3 and i can run -125mv in all frequencies, (1400 @ 1162500 uV). I think that that UV range is depends on the chip lottery.
[Galaxy S III Original Android Development] psyntific:
I'm on ASV2 n I can take off -100mV on all steps except 1000Mhz which is -75mV
[Galaxy S III Original Android Development] Steve_max:
I don't claim that as "my finding" or anything like that, I remember a discussion on this very thread some time ago about this (AndreiLux wanted to do something about the voltages, and requested information on stable undervolts for each frequency + information on the ASV levels, or something like that). Seems like a very smart move by the CPU manufacturers: since you can't "Celeron" a mobile CPU, you might as bin them per stable voltages. They probably keep a safe margin on the defaults for each ASV, so people can probably undervolt safely by at least 75-100 mV on every frequency, and maybe a bit less on one or two.

I'm not 100% sure, but I believe the rev_2 voltage table is for the 2GB versions, for the Note 2/8/10.1 and the i9305. AndreiLux, or anyone who examined the source better, can give much better answers than me.
[Galaxy S III Original Android Development] STAticKY:
Mine is asv2 but still i can get -100 from all frequencies except 1800 although 1800 works on stock voltage. :)
[Galaxy S III Original Android Development] pistoke:
Looks like undervolting is quite difficult, because Volts don't change linearly between different ASVs.

1400 ASV3=1287500, ASV4=1300000, ASV5=1287500

1300 ASV3=1237500, ASV4=1250000, ASV5=1250000
[Galaxy S III Original Android Development] cba1986:
As i said before use the table as a guide. But UV is more trial and error than a exact science. i have a ASV2 and i have 125mv uV in all the freq(I don't OC) and applied some UV in the internal and the memory bus.
[Galaxy S III Original Android Development] sherlock5545:
So if I undervolt and don't experience any reboots, freezes, etc, does that mean it's fine? Is there something else to consider?

Sent from my GT-I9300
[Galaxy S III Original Android Development] Olioaglio:
Correct. Btw, just did some more tweaks and indeed I'm able to oc to 1704 mhz with 1375000mv. 1800 not possible. Freezes instantly no matter what voltage.

Cheers, Olioaglio
[Galaxy S III Original Android Development] Steve_max:
Set governor to "performance" and put maximum and minimum frequency == the frequency you want to undervolt. Stress test that frequency step as hard as you can (StabilityTest has a good stress test, forcing both CPU and GPU to work as hard as possible). If stable, lower voltage and repeat. If not stable, raise voltage to the lowest stable voltage +25mV (or less, or more: your call, but 25-50mV seem to be a good enough security margin), and move to next frequency.
[Galaxy S III Original Android Development] habylab:
Taking a break from this kernel, but how are the CPU modifications coming along Andrei?

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] pistoke:
I compared my default volts to Eric's undervolted profile.

Here are differences to my default volts and Mhz.

-100 1400Mhz

-100 .

-75 .

-75 .

-75 .

-75 .

-50 .

-50 .

-62,5 .

-75 .

-100 .

-100 .

-100 200MHz

I haven't done any longer stress test. Just Quandrant once and normal use feels like working. No booting etc. But I want to be more sure, mostly because of the earlier posts. What do you think, is it good idea to raise every volts 25 in Eric's profile or should I keep less undervolted ones untouched and rise only volts, which are now -100 to -75? I'm trying to say, is it very possible that 800 Mhz with volts -50 can be more unstable than same cpu at 1400 Mhz and volts -100.

Am I thinking too much? :confused:
[Galaxy S III Original Android Development] AndreiLux:
Hopefully fully working in a day or two,,,
[Galaxy S III Original Android Development] :
Andrei, could you put an option to customise vibration levels and maybe overpower it? My vibrator is quite bugged, it stops sometimes and feels like it's weaker. Thanks.

(btw, by vibrator I meant my phone's vibrator, please)
[Galaxy S III Original Android Development] STAticKY:
:what:
[Galaxy S III Original Android Development] RedDevils88:
we all know what u meant there :p
[Galaxy S III Original Android Development] papakaliati:
My phone keeps closing when i leave it to charge all night long. I quess it has something to do with not closing the supply of power when on 100% and so it force closes or something like that. Any chance you could take it a look AndreiLux?

Thanks for your time.
[Galaxy S III Original Android Development] rankesz:
Audio bug

Small bug in the audio section, when i tick the force mono option in STweaks 1-2 times, the option change itself to reverse mode, so the mono mode will be the stereo, and reverse. I hope somebody understand what i trying to say:D
[Galaxy S III Original Android Development] invinciblecc:
Already been reported

hit thanks if i helped
[Galaxy S III Original Android Development] gkhushal:
I didn't even get close ....

Am using erics stweaks profile with undervoltage
[Galaxy S III Original Android Development] Steve_max:
You ARE overthinking, yes. You could stress test each frequency and see if they are stable; keep the stable ones, raise those that aren't. You can do the whole undervolting process, starting from Eric's values. You can increase each voltage by a constant margin as well. It depends on how much time you have to do this, and how important it is that your phone stays 100% stable under all conditions (or if you can risk a weekly random reset for some percent more battery). It's your phone.

But you are right, the relative and absolute undervolts for each frequency are meaningless*. Your phone could very well handle a 200 mV undervolt in one frequency step, and be barely stable at -25mV in other step. This is why you undervolt frequency step by frequency step, and not all steps at once.

* = the only thing that wouldn't make sense was if your phone was unstable if you used, say, 900mV for 500 MHz and stable with 850mV for 600 MHz. Lower frequencies with higher (absolute) voltages than higher frequencies aren't something you will see in practice.
[Galaxy S III Original Android Development] habylab:
Oh wow seems great!

Sent from my Galaxy S3. Long live the original Galaxy S :)
[Galaxy S III Original Android Development] istillmyself:
noob here.. hmm how to know asv which one my s3 can support. hopefully someone can tech me about it
[Galaxy S III Original Android Development] Steve_max:
If you use Perseus, you can see it in two different places.

1) Open STweaks, look at the "default" voltages provided for each frequency and compare them to those on https://github.com/AndreiLux/Perseus-S3/blob/master/arch/arm/mach-exynos/cpufreq-4x12.c (the table is asv_voltage_step_12_5, each column is a different ASV level, and each line is a frequency step from 1800MHz to 200MHz).

2) Install the application "Terminal Emulator", run it, and type the following line EXACTLY, followed by "enter":

grep Adaptive -A 1 /proc/last_kmsg

(upper/lower case is important). You will see something like:

<6>[ 0.290000] c1 EXYNOS4x12: Adaptive Support Voltage init

<6>[ 0.290000] c1 EXYNOS4x12(SG): ORIG : 5 MOD : 0 RESULT : 5

The "5" means my chip is ASV5.
[Galaxy S III Original Android Development] alberber:
There seems to be issues with the mono and the stereo but... Do you have problems also with the equalizer guys? I do, sometimes it doesn't work (I change the sliders but the sound is exactly the same).

Could anyone confirm this please?

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] jwchips:
Hi, this command is not producing any output on my device (i9300, Perseus 35, rooted, miui, busybox & terminal Emulator), has anyone else had any success?

Edit: my bad, something was wrong on my device (unexpected error in sTweaks). Reinstalled the kernel and the command worked fine. Thanks!
[Galaxy S III Original Android Development] Steve_max:
If it produces absolutely nothing, check your spelling of Adaptive. If it produces a single line (instead of two), check if you used an upper-case "A" on "-A 1". If it produces an error, there may be something weird with your ROM and/or busybox. What's the busybox version? (in the terminal, run just "busybox" without quotes and scroll up).
[Galaxy S III Original Android Development] tolis626:
This happened to me once after updating my busybox.Must be some clash,I don't know.Reboot and the kernel reinstalls its built-in busybox,so all is ok.
[Galaxy S III Original Android Development] coolkakucool:
Support form PGM

hey AndreiLux , can u please add support for PGM as in galaxy nexus?.really need it
[Galaxy S III Original Android Development] omniwolf:
Undervolting

For those interested in a more thorough guide to undervolting your CPU (which can also be applied to RAM and GPU I guess), I wrote one HERE
[Galaxy S III Original Android Development] Olioaglio:
Andrei, could you please enlighten me, what exactly you need and what I have to do to get you this viable log. I would like to help but logwise i'm still noobish.

Btw, atm i have flashed siyah 1.9.1 again in emc3 rom to test again and the dongle works at once. Going to mobile odin and flash perseus again and dongle quits connection again 5 seconds after starting allsharecast. So I would obtain your requested log in both kernels, if you'd guide me how to, please.

Olioaglio
[Galaxy S III Original Android Development] SpideRMaN-17:
After installing this kernel my sdcard permissions became read only. Is there a way to fix the permissions please?

Thanks
[Galaxy S III Original Android Development] The Broken:
I doubt it is kernel related, but to fix it, go into recovery.

When you're there look for an option called "fix permissions", activate that one and wait (could take a minute or so depending on the amount of files I guess)
[Galaxy S III Original Android Development] SpideRMaN-17:
Thanks, but fix permissions from recovery won't touch the sd card (tested it) maybe it,s a coincidence that happened right after I flashed this kernel
[Galaxy S III Original Android Development] Hbohd:
AndreiLux, I have a little sugestion about adding zzmoove governor to your already widely developed kernel. I had great experience with it, increasing my battery life, giving just outstanding smoothness etc.. It also allow us to set screen-off max freq which is undoubtfully usefull ;)

Generally, pegasusq seems to be limited and insufficient in my mind. What others think about that? IMHO, it's worth adding !
[Galaxy S III Original Android Development] habylab:
I would agree, but half of the tweakables in stweaks are governor related, are they not?

Sent from my Galaxy S3. Long live the original Galaxy S :)