yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] :
keep it as is for few days and see if you are happy with performance and battery life..

then you can start playing if you want.

well as long as yoi don't select apply on boot a simple reboot will solve it..

from setcpu tabs, voltages is what you want..

start with lowering voltages - 25mV and hit apply.. play with phone.. if stable, lower for another 25mV.. (all together 50mV).. all bellow that is trial and error.. and if you get stuck just reboot your phone..

that's my opinion anyway..
[Galaxy S III Original Android Development] AndreiLux:
Just trying to troubleshoot something, is anybody having issues with connecting to EAP authenticated networks? Please also supply ROM version.
[Galaxy S III Original Android Development] silvio82:
I dont know if kernel related. ...but medium-heavy lags during games like asphalt. Maibe something with graphics drivers/voltages?

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] :
It's my opinion, and you should respect that.

1. yeah it will, one simple change can: drain all the battery/make the phone super laggy and may even not boot.

2. Ask gokhanmoral, he will tell you the same thing. Or I can just post here his PM he sent me. In some words: 1 second at 1,2GHz drains less then 6 seconds at 200MHz.

3. I don't know what he asked, so I tried to tell the most common stuff to do on SetCPU, including limiting screen on freqs.

4. You need to test very carefully for each voltage. It can work for 1 day, but freeze the whole phone after 1 week. Isn't safe to say that testing and stressing for 5 minutes will make this voltage stable. Patience is what I need and don't have to test for each freq.

Cheers
[Galaxy S III Original Android Development] silvio82:
To restore the stock condition....can we have original voltages table? :)

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] gokhanmoral:
I want to make something clear. I remember the pm that I sent you and there were no strict conclusion in that. Although AndreiLux's tests also shows that 1200 mhz doesn't consume six times more than 200 that 1 to 6 ratio in time may change depending on the process type (checking email may take the same whereas computing pi may take 1/6 or decoding a huge data may differ depending on the bus load) . So i will be glad if my name is not used in a discussion that nobody can prove which I don't want to be a side and my pm not as a reference.
[Galaxy S III Original Android Development] :
Yeah, I should have said that, I think I just forgot the "no strict conclusion" part :)

Sorry, didn't meant to get you involved.
[Galaxy S III Original Android Development] AndreiLux:
That's the theoretical dynamic leakage.

Screen off frequencies are bad up until somewhere around 800MHz. To be honest we should be using a screen-off min frequency rather than a screen-off max frequency. But this is all silly discussions because there's simply no work done during screen off. Music play maybe but eh...
[Galaxy S III Original Android Development] :
Wakelocks?
[Galaxy S III Original Android Development] AndreiLux:
What about them?
[Galaxy S III Original Android Development] :
Screen-off activities/work. Increasing min_freq increases efficiency, so wakelocks stay less time working, so they are released faster. Correct?
[Galaxy S III Original Android Development] AndreiLux:
Just what exactly do you think the type of computations are being done during screen-off? The phone does relatively nothing and most time is spent on waiting for time-outs, and even those don't matter that much since we're power-gated during screen off idle. It may bring something in theory but practically I don't think it means much.
[Galaxy S III Original Android Development] ctrlaltdel:
I fixed this issue by flashing the stock kernel then flash back this kernel.
[Galaxy S III Original Android Development] Fienman:
Was anybody able to hit 1800 Mhz with this kernel? I tried all the voltages between 1400 mv to 1500 mv. But it reboots as soon as I start any benchmark.I am able to do 1704 though.

I am using Set CPU.
[Galaxy S III Original Android Development] Ausboy 2011:
noticed a big freeze when using music player and ram usage was rather high. cleared ram and I had to restart phone it was like the phone was stuck on 200 mhz couldn't do a thing. if it happens again I'll get a log and post it :)

Sent from my omega jellybean powered sgs 3 :)
[Galaxy S III Original Android Development] gee2012:
The latest Perseus is running great wit ARHD 11.0.0, settings 200 min. and 1600 Mhz max. frequency with all freqs undervolted by -75mV. No lags or hickups whatsoever and fast as a bullet. Also batterylife is quite descent :)
[Galaxy S III Original Android Development] AbuYahya:
I can run at 1.8Ghz at 1400mv but temps are high in 70c. throttles at 75c and turns the other cores off so only a single core at 1.8Ghz and rest idle. Thus no performance benefit as throttle kicks in after 20s.

Edit

Even 1.6Ghz at 1250mV throttles at 68C switching 3 cores off and only CPU0 is running at 1.6Ghz. So I dont see the performance benefit.

I have just tested 1.3 and 1.4 Ghz both of them throttle at stock voltages when exceeding 63-64C.

1.4Ghz @ 1175mV eventually throttles too.

1.3Ghz @ 1125mV and 1150mV were ok but raising voltage made it hit 64C at which point in throttles.

My mobile is in a case will re-run tests without.

But throttling at stock voltage and frequency is ridiculous.

Without case eventually at 1.4Ghz @ 1275mV which is less than stock, throttles at 68C.

on stock kernal. Throttles when exceeds 64C but throttling behaviour is different it keeps all four cores online but cuts freq of all to 800Mhz. Also the throttle is much shorter in duration.

Can anyone confirm this.

Throttling at stock is ridiculous.

Might retry ICS.
[Galaxy S III Original Android Development] DroidRevenge:
Yeah mate!

Running absolutely great!

Outstanding smoothness and yet stable.

One question: why sammy devs have not done this kind of job earlier?
[Galaxy S III Original Android Development] nicregi:
I am curious. Does this kernel works well with Thunderbolt tweaks?
[Galaxy S III Original Android Development] aegeuss:
Thanks for this great kernel; I have a wish though, can you update OP in compliance with thread title and update information? It's hard to keep up after a while.

Regards

GT-I9300 cihazımdan Tapatalk 2 ile gönderildi
[Galaxy S III Original Android Development] invisiblebm:
Hi. I have Anker extended battery. This kernel is recognizing it like usb and charging is very very slow. The battery has one output from 700 mah and is working well with stock kernel. Please can you look at this in your next realise. This is the best kernel I had ever used on phone. Thanks for your efforts.
[Galaxy S III Original Android Development] JYJY:
Don't know how you manage to get that high temperature man. My phone is running at 1.5Ghz and getting temp between 41-50c.
[Galaxy S III Original Android Development] angelnaina:
I guess i am the only person who is getting FC in front camera in full resolution..::(

Stock JB offical rom...
[Galaxy S III Original Android Development] qwerty12:
Nope :) Though it's not a FC in the traditional sense, as the Camera app throws up the message Warning: Camera Failed [OK]. Though the front camera does continue to work while it's saying this, even if it does close itself after about a minute

I attached the relevant dmesg output, which helps when reporting issues

Not what you asked for, but since nobody answered... my university's EAP authenticated network works fine: PEAP, MSCHAPV2 and no certificate specified (otherwise I have to do that bollocks of unlocking the keystore - at least from what I can remember with my Gingerbread phone).
[Galaxy S III Original Android Development] BaGRoS:
Works software CifsManager anyone?

What should I do to work?

Wysłane z mojego GT-I9300
[Galaxy S III Original Android Development] joe_donkor:
No issues on Cisco EAP wirless where I work. Omega 27.1/Perseus Alpha 23
[Galaxy S III Original Android Development] AndreiLux:
The CIFS module is included, should work.

Thanks for the reports but I found out the issue, it's a bug in Jellybean breaking TLS compatibility due to some softwares not adhering to the standard. Will try to fix in through a different approach (It's not kernel related).
[Galaxy S III Original Android Development] silvio82:
A quick report based on my experience :

Tried a different kernel (Phenomenal 4) for a while with this undervolts from stock:

cpu arm : -125mv to all freq

cpu internal: -50mv to all freq

bus: -100mv to all freq

gpu: -100mv to all freq

Running Asphalt 7 no lags or freeze.

Using perseus with -100mV on all frequencies (arm) i got medium/heavy lags. So i think there's something with gpu drivers or voltages that is causing these lags.

It's not a criticism against perseus kernel but a point to investigate to increase this great kernel. ;)

Sorry for my English also! :D
[Galaxy S III Original Android Development] tsubus:
finally, a kernel done properly. thank you!
[Galaxy S III Original Android Development] AbuYahya:
What do you use to monitor temp's.

System tuner screenshots. Throttled 6 times in 5 minutes
[Galaxy S III Original Android Development] AbuYahya:
Need to stress cpu high load for 5 mins with app "Stability test"
[Galaxy S III Original Android Development] duowing:
I just tried this and noticed that I indeed get the FC error. I barely use the Front Facing Camera, so it's not really a problem. Is this an error related to this kernel or to the LIB rom? I'd have to flash back the stock kernel and check.

I've had some intermittent issues with WiFi with 23.4, but I can't tell if it's related to updating from 23.3 or if it's just the wireless at home. Twice yesterday I'd have an issue where WiFi really wasn't doing anything until I disconnected and reconnected it. Later when I came home from work same issue. I was upstairs which doesn't always get the best wifi signal, but then I disconnected/reconnected it and it worked fine. Shortly later I was using it and noticed wifi had disconnected and dropped back to mobile data then shortly reconnected. Anyone else encountering these issues?
[Galaxy S III Original Android Development] unholygid:
The root cause is usually modem not the kernel. I have this problem once in a while on stock or on other custom kernel and then realized it has nothing to do with rom or kernel. Best is to flash other modems to test if the problem still persist and see which works best.
[Galaxy S III Original Android Development] trueno84:
No issue with 23.3 thanks a million
[Galaxy S III Original Android Development] yoyosamsam:
Is Perseus kernel compatible with Omega v27.1 ??
[Galaxy S III Original Android Development] AbuYahya:
The earlier SS was stock ICS. When it throttles speed is cut to 800Mhz of all 4 cores and temp quickly drops to 50C throttle ceases and all cores return to Max set freq.

On Jb LIB with stock kernal it is similar to above. However with Perseus kernel when the throttle temp is reached (usually 1-2 max load) the first core remains at max temp (so most apps will record max freq as current freq) but other three cores are switched off.

Temp drops but stays around 56C (for stock voltages and clock) so throttle doesnt switch off (threshold is 50C) and we essentially have a single core processor.

SS below. Compare to previous ICS SS.

Edit

It does recover but takes about 100s then quickly throtles again.

And back at 56C and most apps will read freq at 1.4 (or maximum OC freq) but it is practically single core.

Does any one else get these or is mine a ovrr heated phone?
[Galaxy S III Original Android Development] kenzolo:
yes
[Galaxy S III Original Android Development] BaGRoS:
You test it? Because for me it does not work.

Wysłane z mojego GT-I9300
[Galaxy S III Original Android Development] niknase:
Yes, it works great for me with omega 27.1

sent from my S3 powered by Omega Rom
[Galaxy S III Original Android Development] time_shock:
yea this works way better than Siyah 1.6.7 for me... i still get occasional lockups on Siyah 1.6.7
[Galaxy S III Original Android Development] nodstuff:
First question, do you know what hotplugging is?

If you think the cores being switched off is what throttling is then you are mistaken.

The cores switch off when not in use and the temperature limit for throttling stage one is like 70 or 80c, not 50.

56c CPU core temp is not really hot at all.
[Galaxy S III Original Android Development] AbuYahya:
During these tests CPU load is 90-100 percent as stressed with 'stability test v2.5'. They are being switched off 63-69C then do not kick back in until temp drops to 50-56C. @1.4Ghz

But at 1.8 ghz it occurs at 75C.

Look at the SS

Look at load and temps.

Try the stress tests yourself.

This may be hotpluging but that AFAIK is used to switch hardware on & off when needed or not (without rebooting). But here load is maximum at cores are needed.
[Galaxy S III Original Android Development] AndreiLux:
All throttling stops below 76°. And I haven't touched the TMU values. Throttling also doesn't turn off cores. Use the performance governor if you want full power dissipation.
[Galaxy S III Original Android Development] yoyosamsam:
What apps should i use for changing setting like uv, gpu??

Does ExTweaks works for it??
[Galaxy S III Original Android Development] joe_donkor:
I'm using the old free version of SetCPU. Waiting to see the Perseus config tool. ;)
[Galaxy S III Original Android Development] Galaid:
I'm unable to mount USB stick via OTG adapter. Anyone?
[Galaxy S III Original Android Development] qwerty12:
Worksforme:
[Galaxy S III Original Android Development] AbuYahya:
Thanks. Your correct its is the pegasusq governer causing that phenomenon which disappears on performance governer. True Throttling is taking affect at 80C and reduces freq to 800Mhz of all 4 cores.

Performance governer is at maximum set freq irrespect of load. This will kill the battery probably with in the hour.

Can you provide some alternative governers e.g. on-demand, smartass V2, etc

or an amended Pegasusq without previously mentioned phenomenon.
[Galaxy S III Original Android Development] AndreiLux:
Why? You're triggering this problem in a synthetic situation. It is not an issue of every-day use, and I won't include some other useless governors (Which will need modding due to hotplugging) for our device because of it. You have all the configurables free at hand in pegasusq to set this up however you want.
[Galaxy S III Original Android Development] kenzolo:
I'm in love with perseus 6180 quadrant!!

Wooooooooooow

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] nodstuff:
Andrei, any plans to make this to support aosp ROMs?

Flashed liquid smooth after a love/hate relationship with sammy ROMs, would love to be able to use this kernel with it.
[Galaxy S III Original Android Development] AbuYahya:
The negative hotpluging is ocurring at times within 90secs (see SS) on full load (at 68C @1400Mhz and doest deactivate until 56C - i.e. they are not realy that hot temps and it affects performance).

Do you not think apps or games would stress the CPU this much?

IMHO it is not a hypothetical situation but practically feasible esp for games or heavy duty apps.

it maybe the cause of some ppl's occasional lag for those on stock voltages, obviously if we undervolt, then that may also over come it.

I think if the pegasusq negative hot-pluging occurred at 75C and then brought the cores back on line at 65C, then that would be a better balance.

I don't know how that would be done or whether it be too complicated or arduous for a kernel-guru like yourself. Any pointers would be appreciated.

But thanks all the same.
[Galaxy S III Original Android Development] Fienman:
While we are on the topic of OC,can someone please explain why my phone reboots at 1800 mhz no matter what the voltage.If it would throttle down then i would get it,but why reboot?

I tried all the voltages between 1400 mv to 1500 mv.
[Galaxy S III Original Android Development] SirCanealot:
It means you haven't sacrificed 4 chickens to the overclocking gods. Or that your silicone simply can't handle 1.8ghz. All silicone is not created equal. Read up on desktop pc overclocking - you'll see a massive variance on voltages and clock speeds. Your options are: don't OC to 1.8 or buy another phone and you might get more lucky. Which is it gonna be? :D

And don't worry, you're never as unlucky as me with silicone! :p

Edit! I meant to say I tried to get my cpu to throttle at 1.7 ghz and I couldn't do it! System tool reported all cores online and I had trouble even getting the Cpu to 80c! 1.7 ghz at 1325mv here. Am I doing it wrong?

Edit again: I'm running siyah... Getting lags anyway, do gonna flash back. Will re-test...
[Galaxy S III Original Android Development] AbuYahya:
AFAIK Not all CPU's have the same ability to overclock it depends upon the quality of the internal element (quartz crystals I think). so if it doesn't have the ability to go that fast, but your system is telling it to go, no matter how much fuel you give it, it can't do it, so the system fails..

some other guru will be able to explain it better!
[Galaxy S III Original Android Development] Fienman:
Okay. Thanks for the explanation guys.
[Galaxy S III Original Android Development] zykic:
By the meaning of 'overclock', it's 'try' to get better than what you already get. There is no guarantee to it.

If your overclock isn't stable enough, it will give wrong calculations or will not calculate at all, hence the reboots.

As your CPU seems to not be stable at 1800MHz, you should lower it. And you should not go for voltage higher than 1400mv as it's 32nm safe-limit. Also going that high(1800MHz) may not benefit you as it will produce much higher temp and get throttled after a short time.
[Galaxy S III Original Android Development] AndreiLux:
Great and all but you're not hearing me: the governor has nothing to do with the temperatures of the CPU. Turn on dvfs_debug in the configurables and run the stability test while monitoring /proc/kmsg with live core statistics. For me it gives me all cores online way beyond 90 seconds for all the time, with even ****ty load values for cores 1-3 and core 0 at 100%. This is a problem of the stability test not dispatching its threads correctly and is not a problem of the kernel or governor or temperature units.
[Galaxy S III Original Android Development] Falamo:
Please someone can tell me a script to undervolt the gpu?

Sorry for the noob question

Sent by me & my s3
[Galaxy S III Original Android Development] eric-filth:
Andrei, i used this patch to undervolt cpu and didn't work, what im doing wrong?

/sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

Enviado do meu GT-I9300
[Galaxy S III Original Android Development] sak500:
@ 1700 antutu reboots my phone.
[Galaxy S III Original Android Development] tvhak:
what governer you use
[Galaxy S III Original Android Development] Le Rat Noir:
Hi :)

Nstools, voltage control or other ?
[Galaxy S III Original Android Development] tvhak:
setcpu or voltage controle
[Galaxy S III Original Android Development] sak500:
SetCPU : pegasusq and ondemand tried both
[Galaxy S III Original Android Development] KennyLegend:
Hey Andrei nice work.

Any plans to analyse the adjustable charging currents ?...ala Siyah
[Galaxy S III Original Android Development] Le Rat Noir:
Thanks :)
[Galaxy S III Original Android Development] sak500:
ok somehow working now and @ 1800/400 @1425mV the score of antutu dropped from 13+k of 1.6/1.7 to 8k ?
[Galaxy S III Original Android Development] jamuk2004:
exFAT

Great work AndreiLux!

Can I ask if there has been a fix for exFAT on external sd?

Thank you.
[Galaxy S III Original Android Development] jackymuta:
Great work

one problem, SIO performance slow in CFQ and....

1704MHz + sio + pegasusq run Quadrant can be showdown :(

1704MHz + cfq + pegasusq run Quadrant is OK :D
[Galaxy S III Original Android Development] silitek:
Use NOOP and NStools...stable here;)
[Galaxy S III Original Android Development] tvhak:
the phone has a security build that when phone gets hot it will underclock.

so you wont get to the 1800. but maby 600. so the hotter you phone the lower you bench

let him cool down for a while and try it again
[Galaxy S III Original Android Development] simone201:
Managing the charging currents on the GS3 is totally different...

As example, by default it uses 1A for AC Charging and 475mA for USB

I dont think it's safe to stay above 1A (even if the GS3 regulator allows over 2A of max current)

Anyway, also the kernel interface is totally different and should be reworked a lot
[Galaxy S III Original Android Development] sak500:
Thanks, using your tips @ 1.8ghz 1425mv

EDIT: Hit 30k

[/url][/IMG]
[Galaxy S III Original Android Development] silitek:
You welcome;)
[Galaxy S III Original Android Development] bala_gamer:
guys , regarding overclocking the following details would be nice

1. stock voltages of the clock.

2. stable adjusted voltage of the clocks.

3. stability apps used and avg stable time with each clocks.

these details can be updated regularly in a post whenever there is a change. so who is up for it?( i dont have enough time to do this).
[Galaxy S III Original Android Development] F1tty:
Fastcharge would bei a nice feature :thumbup:
[Galaxy S III Original Android Development] bala_gamer:
here are the stock voltage for each steppings, posting this because it might be useful for some people

1600mhz-------1400mv

1500mhz-------1350mv

1400mhz-------1288mv

1300mhz-------1238mv

1200mhz-------1188mv

1100mhz-------1138mv

1000mhz-------1088mv

900mhz--------1050mv

800mhz--------1000mv

700mhz--------975mv

600mhz--------963mv

500mhz--------938mv

400mhz--------925mv

300mhz--------900mv

200mhz--------900mv
[Galaxy S III Original Android Development] sak500:
Mines below using NStools

1800mhz-------1425mv

1704mhz-------1400mv

1600mhz-------1375mv

1500mhz-------1313mv

1400mhz-------1275mv

1300mhz-------1238mv

1200mhz-------1175mv

1100mhz-------1125mv

1000mhz-------1075mv

900mhz--------1025mv

800mhz---------975mv

700mhz---------963mv

600mhz---------950mv

500mhz---------938mv

400mhz---------925mv

300mhz---------900mv

200mhz---------900mv
[Galaxy S III Original Android Development] walda:
general question ... is it possible to UV the deepsleep?

... tapat*lked
[Galaxy S III Original Android Development] :
How are you using? If by init.d steps

1. Set permissions to rwxrwxrwx

2. put an S and a number like S99undervolt

3. Set ownership to 0 - root / 0 - root.

4. Put #!/system/bin/sh at the first line of the script

Even if they are useless, worth a try.
[Galaxy S III Original Android Development] Net.silb:
CyanogenMod 10 Compatibility?

Hi,

I used this kernel with a Samsung based ROM and I really liked it. I'm now using CM and I want to know when and if this kernel will be compatible with AOSP based ROMs?

Thanks in advance!
[Galaxy S III Original Android Development] Ausboy 2011:
not at the moment only Sammy based roms :)

Sent from my checkrom jellybean powered sgs 3 :)
[Galaxy S III Original Android Development] Rikul:
Does the camera quality degrades a bit on this kernel coz of huge ram??
[Galaxy S III Original Android Development] Highlander11:
@Andrei,

thank you for the excellent kernel! :thumbup: IMHO, apart from other suggestions made by far more knowledgeable contributors, what I miss is the faster recharging rate of the stock kernel. Or am I mistaken? :rolleyes: I am using ARHD v11.0.0 with Perseus v23.4 kernel, OC to 1600 MHz and UV to -75mV.
[Galaxy S III Original Android Development] StijnTehMan:
Sorry for the noob question, but this is the first time i flashed a custom kernel.. How can i acces the options?
[Galaxy S III Original Android Development] JYJY:
try setcpu. :)