Database Users

Undervolting Thread

This thread has been created to share Undervolting Settings (UV).
Undervolting makes CPU/GPU/Modem to consume less power, thus extend battery life. This is allowed by flashing modified kernels that allow UV (Thanks to raspdeep's work). One can use Voltage Control to change settings (Thanks to xan).
Setting format is -x mV for a given CPU clock as used in xan's app: [1200Mhz] [1000Mhz] [800Mhz] [400Mhz] [200Mhz] [100Mhz]
What are your settings?
PS: Please edit your very first post with settings instead of reposting. Thank you!

Stable: 50 50 75 100 100 100
1200 max: 50
1000 max: 50
800 max: 75

I am currently running 50 50 50 75 100 100 with no stability problems. It has made 4 back-to-back quadrant runs and a couple days of general usage without any crashes so far.

Undervolting doesn't work well with my phone the same with overclocking. I can't undervolt 1000Mhz and above because it causes much stability issues here. I can only undervolt 100-800Mhz with settings < 100mV.

TheVisitorX said:
Undervolting doesn't work well with my phone the same with overclocking. I can't undervolt 1000Mhz and above because it causes much stability issues here. I can only undervolt 100-800Mhz with settings < 100mV.
Click to expand...
Click to collapse
My system hangs in sleep mode when I have setCPU or Superpower with sidekick on.

I have the max cpu capped at 800mhz using SetCpu.
Undervolted -50 for 800mhz 600 400 200 and 100 each.Phone was at 50% last night and 6 hours later it's dead.Battery was completely discharged.All i did was set everything at 50Mvs less.Correct ? i think i'm missing something.Do help.thanks.

hey guys
im new to oc and uv
im currenlty using ramads gb jvh with hardcores speedmod kernel
ive got tegraks ultimate app and have oc'd it to 1100 as anything above reboots my phone
everything else is the same as standard
i was wondering if anyone else can help me with what i should change
i have no clue,
so far
frequency 1100
core 1275mv
internel 1100
cpu level 1
frequency 800
core 1200
internel 1100
cpu level 2
frequency 400
core 1050
internal 1100
cpu level 3
frequency 200
core 950
internal 1100
cpu level 4
frequency 100
core 950
internal 1000
these values are all stock, i havent touched them
im wanting to know what i should change them to
thanks
forgot to add, my battery life is really bad, i use hsdpa and wifi frequently

i have cm7 #19 with the (latest) glitch v10b-VC kernel..no oc, bu uv
100mhz -50,200mhz -50,400mhz -50, 800mhz -25 and 1000mhz @stock

What is the negative effects of UV?
My current values starting at 1000mhz is:
-75
-100
-100
-125
-175

hackeron said:
What is the negative effects of UV?
My current values starting at 1000mhz is:
-75
-100
-100
-125
-175
Click to expand...
Click to collapse
Negative effects come in the form of stability issues and random reboots. Is doesn't physically damage the processor. By lowering the core voltage supplied to the CPU, you also decrease the noise margin for the CPU to properly differentiate between logic 1 and logic 0. This is why -75, for example, works for some and not for others because processors are not 100% identical. The obvious benefit UV is lower power consumption.

gtda said:
hey guys
im new to oc and uv
im currenlty using ramads gb jvh with hardcores speedmod kernel
ive got tegraks ultimate app and have oc'd it to 1100 as anything above reboots my phone
everything else is the same as standard
i was wondering if anyone else can help me with what i should change
i have no clue,
so far
frequency 1100
core 1275mv
internel 1100
cpu level 1
frequency 800
core 1200
internel 1100
cpu level 2
frequency 400
core 1050
internal 1100
cpu level 3
frequency 200
core 950
internal 1100
cpu level 4
frequency 100
core 950
internal 1000
these values are all stock, i havent touched them
im wanting to know what i should change them to
thanks
forgot to add, my battery life is really bad, i use hsdpa and wifi frequently
Click to expand...
Click to collapse
I'm also using Tegrak's overclock apk for some time now (from beginning) and it's really good!
Just lower the core voltage (start with cpu level 0) until it's unstable (random reboots), then add a few mv (+5) to make it stable again (no reboots). do this for every core frequency (only one at the time, so you know witch one is making the system unstable). I never touch the internal frequency... Undervolting will NOT damage your CPU (overclocking can if you're not carefull)
Don't be stupid testing just a few hours, test (stress test) for days. Only then you are sure it's stable
These are my settings:
(rock stable after a few weeks => playing asphalt6, running quadrant and smartbench hours a day for a few weeks,...)
cpu level 0
frequency 1000
core 1205mv (-70) => could get it stable at 1200 but had one reboot after one week, so I added +5
internel 1100
cpu level 1
frequency 800
core 1105 (-95) => could get it stable at 1100 but had one reboot after one week, so I added +5
internel 1100
cpu level 2
frequency 400
core 950 (-100)
internal 1100
cpu level 3
frequency 200
core 825 (-125)
internal 1100
cpu level 4
frequency 100
core 825 (-125)
internal 1100
Now I know what my lowest core voltage is, I can start overclocking (not for now).
I'm on stock deodexed JVP 2.3.4 with Hardcore (latest) Speedmod (partition EXT4), Tegrack Overclock Ultimate and Voodoo Control Plus (holy combo => Quadrant 2400+ (no OC, just UV) and wow, what a great battery life!
edit: yes, I need to update my signature

SamHaLeKe said:
cpu level 4
frequency 100
core 825 (-125)
internal 1100
Click to expand...
Click to collapse
^ Typo??????????
internal voltage @ 100Mhz is 1000mV by default, so you are overvolting.

kiwijunglist said:
^ Typo??????????
internal voltage @ 100Mhz is 1000mV by default, so you are overvolting.
Click to expand...
Click to collapse
Default value is 950mV on my phone according to pimpmycpu. According to SamHaLeKe's post, he's reducing his by -125 so 825mV is correct
I'm new to UV, and just experimenting. My current values are
1200 = -50mV
800 = -50mV
400 = -100mV
200 = -100mV
100 = -150mV
Seems ok so far, more aggressive cutting gave me reboots

$$$

The most i could get from my phone w/o stability issues
1500 - 50
1400 - 50
1300 - 50
1200 - 50
1000 - 50
800 - 75
400 - 100
200 - 125
100 - 150

Starting from 1000MHz, I'm using these values :
-50 [1000]
-75 [800]
-100 [400]
-125 [200]
-150 [100]
No stability issues since then !

Mine are;
1000 : 50
800 : 50
400 : 75
200 : 75
100 : 100
Works great for me
Sent from my GT-I9000 using Tapatalk

swaakx said:
Starting from 1000MHz, I'm using these values :
-50 [1000]
-75 [800]
-100 [400]
-125 [200]
-150 [100]
No stability issues since then !
Click to expand...
Click to collapse
i have the same!
my phone now cold as ice. and greatly stable

I'm a noob at this UV stuff but I'm quite interesting about that.
I tried with Control Freak, should I set first a low voltage on 100Mhz and try to stress the cpu only with this change on 100MHZ? or should I set all voltages and test?
thx for help

i'm on jvq darkyrom
using tegrak overclock ultimate
1200mhz 1255 (-20)
800mhz 1105 (-95)
400mhz 950 (-100)
200mhz 850 (-100)
100mhz 810 (-140)

Live Overclock Voltages -Community Support

Ezekeel has created the ability for user control of cpu overclock and bus/gpu overclock. He has also made it possible to change the cpu and internal voltages, so that this can be done without sacrificing stability. Several awesome kernel developers have implemented his work. Thanks to all of you.
I have seen kernel development threads degenerate into "help me with my voltages" threads. No more!
Please post:
- Your kernel and version/date.
- Your live_oc value.
- Your dvsarm (cpu voltage) values.
- Your dvsint (internal voltage) values.
You can vote for settings you have found to be stable by thanking that post.

Default cpu / bus clock speeds
Trinity teuv:
5 steps:
100 200 400 800 880 MHz;
bus: 220 MHz
Trinity T144:
5 steps:
100 400 800 1000 1440 MHz;
bus: 240 MHz
franco:
5 steps:
100 200 400 800 1000 MHz
bus: 200 MHz
Please post the frequencies for your kernel of choice, so we can make this list complete.

Reserved for bacon.
PM simms if you want chocolate on it.

good idea!
btw, reserved for chocolate covered bacon. Mmm..

Reserved for:
Spank me Ezekeel!

I'll start:
Kernel: Always my latest kernels
live_oc: 110
dsvarm (cpu voltage): 1250, 1155, 1000, 900, 900
dsvint (internal voltage): stock

is it possible that my nexus dislike liveoc.
no matter which kernel (matrix/franco) + rom (markvis/superosr) combo i am on, 110% and 20 - 30ov
will freeze the phone
currently on
kernel: franco.kernel 0611
live_oc: 100
voltage: stock

Kernel: Franco 06november bfs
live_oc: 120
dsvarm (cpu voltage): 1285, 1190, 960, 835, 800
dsvint (internal voltage): stock
Sent from my Nexus S using Tapatalk

Go Go
250~1G freq with 250 bus/GPU speed! Cool~
- kernel and version/date : franco.Kernel 11/6
- live_oc value :125
(max freq :800 / min freq : 200)
- dsvarm (cpu voltage) values : 1250 1250 1080 950 950
- dsvint (internal voltage) values : 1100 1130 1130 1130 1000
#!/system/bin/sh
echo "1250 1250 1080 950 950" > /sys/class/misc/customvoltage/arm_volt
echo "1100 1130 1130 1130 1000" > /sys/class/misc/customvoltage/int_volt
echo "800000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "200000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "125" > /sys/class/misc/liveoc/oc_value
Click to expand...
Click to collapse

Kernel: Franco 06november bfs
live_oc: 110
Min_freq: 440
Max_freq:1100
dsvarm (cpu voltage): 1210, 1160, 1010, 900, 900
dsvint (internal voltage): stock

What's a good max arm volt to liveoc 110 on franco's 06
Ill go with stock on the ones I can control with set cpu
Cool update on nstools! Now can adjust voltages,that's why I ask lol...
Sent from my I9020T NSCOLLAB + FRANCO'S 06 BEAST LIVEOC 105

Kernel:Franco 6NOV CFS
LiveOC:110
dsvarm:1275 1200 925 800 775
The above settings seems to be stable on my phone but
may someone please teach me what to do when OC failure?
(I know how to clear CMOS on computers but don't know much on phones)
I use both NSTools and SetCPU to get LiveOC value of 120 and hang, after restart, the NSTools autoload 120 and hang again, it hang before I get access into the NSTools to change the value, what should I do?
---------- Post added at 03:12 PM ---------- Previous post was at 02:58 PM ----------
LKNim said:
Kernel:Franco 6NOV CFS
LiveOC:110
dsvarm:1275 1200 925 800 775
The above settings seems to be stable on my phone but
may someone please teach me what to do when OC failure?
(I know how to clear CMOS on computers but don't know much on phones)
I use both NSTools and SetCPU to get LiveOC value of 120 and hang, after restart, the NSTools autoload 120 and hang again, it hang before I get access into the NSTools to change the value, what should I do?
Click to expand...
Click to collapse
I got it solved by a brainless method
1.Flash TEUV kernel which doesn't support liveOC
2.Clear the data of NSTools
3.Back to franco kernel
4.Done
It's useful for those don't know much about command and init.d such as me

franciscofranco said:
I'll start:
Kernel: Always my latest kernels
live_oc: 110
dsvarm (cpu voltage): 1250, 1155, 1000, 900, 900
dsvint (internal voltage): stock
Click to expand...
Click to collapse
get reboot with this settings..
strange...

al_madd said:
get reboot with this settings..
strange...
Click to expand...
Click to collapse
It's not strange, you may understand this if you have overclocked your PC.
Different CPUs need different voltages to maintain stability.
You may try this
1275 1200 or even higher
There is no best voltage for every CPUs, you need to find it out yourself.
In my case
1100MHz need 1275mV
1000MHz need 1200mV
880MHz still need 1200mV...
800MHz need 1125mV

LKNim said:
It's not strange, you may understand this if you have overclocked your PC.
Different CPUs need different voltages to maintain stability.
You may try this
1275 1200 or even higher
There is no best voltage for every CPUs, you need to find it out yourself.
In my case
1100MHz need 1275mV
1000MHz need 1200mV
880MHz still need 1200mV...
800MHz need 1125mV
Click to expand...
Click to collapse
I think I am confused with stock voltage for internal voltage...
this one??
Nexus S stock voltages
1000mhz: 1250 mV
800mhz: 1200 mV
400mhz: 1050 mV
200mhz: 950 mV
100mhz: 950 mV
Or this one??
1000mhz : 1100mV
800mhz :1100mV
400mhz :1100mV
200mhz :1100mV
because when change my intenal voltage with stock voltage....immediately hang and after that reboot
100mhz :1000mV

al_madd said:
get reboot with this settings..
strange...
Click to expand...
Click to collapse
with this settings i have no reboot

al_madd said:
with this internal voltage right???
Nexus S stock voltages
1000mhz: 1250 mV
800mhz: 1200 mV
400mhz: 1050 mV
200mhz: 950 mV
100mhz: 950 mV
Click to expand...
Click to collapse
Isn't it 1250 1200 1050 950 950 the arm voltage
Stock int voltages are 1100 1100 1100 1100 1000
(I got these via NSTools before any changes)
With stock int voltages my phone works well
My settings for reference, NOW(STOCK)
Freq 1100(1000) 880(800) 440(400) 220(200) 110(100)
Arm 1275(1250) 1200(1200) 925(1050) 800(950) 775(950)
Int 1050(1100) 1050(1100) 1050(1100) 1050(1100) 900(1000)
It's better try it yourself, values copied from the others may not suit for you

LKNim said:
Isn't it 1250 1200 1050 950 950 the arm voltage
Stock int voltages are 1100 1100 1100 1100 1000
(I got these via NSTools before any changes)
With stock int voltages my phone works well
My settings for reference, NOW(STOCK)
Freq 1100(1000) 880(800) 440(400) 220(200) 110(100)
Arm 1275(1250) 1200(1200) 925(1050) 800(950) 775(950)
Int 1050(1100) 1050(1100) 1050(1100) 1050(1100) 900(1000)
It's better try it yourself, values copied from the others may not suit for you
Click to expand...
Click to collapse
Oh...sorry..because everyone says internal voltage using stock..I thought these value 1250 1200 1050 950 950...sorry..
yes..with 1100 1100 1100 1100 1000...My phone have no problems at all..thanx...

when i change the voltages in terminal emulator:
echo "1250 1200 1000 950 950" > /sys/class/misc/customvoltage/arm_volt
does the voltage change take place instantly or do i need to reboot?

Changes are instant. Rebooting will only reset you to stock values, if you don't have an init.d script for them.
You can check your changes after an echo by typing the following in Terminal:
Code:
cat /sys/class/misc/customvoltage/arm_volt

Perfect Setup for NS4G

Just thought I should share this info.. I've literally tried every combination of everything and after a few days I've settled for this combination..
Best of performance and battery life Ive ever used.
I've searched everything everywhere and this beats everything recommended.
rom: slimics 4.0
lcd density: 200
theme: cobalt
launcher: apex launcher pro
kernel: matr1x cfs 20.0
nstools settings
-----------------
io scheduler: sio
governor: smartassv2
min cpu: 100MHz
max cpu: 1300MHz
deep idle: on
default voltage
smartassv2 settings:
awake ideal freq: 400000 Hz
sleep ideal freq: 100000 Hz
sleep wakeup freq: 400000 Hz
min cpu load: 50 %
max cpu load: 85 %
ramp down step: 200000 Hz
ramp up step: 200000 Hz
down rate: 49000 us
up rate: 48000 us

well good for you, but every phone is different sooooooo dont hurt yourself patting your own back

Lots of people really digging slimics at the moment.
If I was to root I would try that rom for sure.
Sent from my Nexus S using XDA

ozkoidz said:
Just thought I should share this info.. I've literally tried every combination of everything and after a few days I've settled for this combination..
Best of performance and battery life Ive ever used.
I've searched everything everywhere and this beats everything recommended.
rom: slimics 4.0
lcd density: 200
theme: cobalt
launcher: apex launcher pro
kernel: matr1x cfs 20.0
nstools settings
-----------------
io scheduler: sio
governor: smartassv2
min cpu: 100MHz
max cpu: 1300MHz
deep idle: on
default voltage
smartassv2 settings:
awake ideal freq: 400000 Hz
sleep ideal freq: 100000 Hz
sleep wakeup freq: 400000 Hz
min cpu load: 50 %
max cpu load: 85 %
ramp down step: 200000 Hz
ramp up step: 200000 Hz
down rate: 49000 us
up rate: 48000 us
Click to expand...
Click to collapse
Cool story.
But smartassv2 != battery saving. It's a performance governor, not one meant to save battery.

So far I haven't found a ROM that's smoother or more responsive than... STOCK. I have to say this is the first time I am using the Stock ROM for sooo long. It's fast, responsive and it doesn't randomly reboot (uptime 1100+ hours).

+1 for Slim ROM!
It just keeps getting better and better.
Vs Nexus S 4G

polobunny said:
Cool story.
But smartassv2 != battery saving. It's a performance governor, not one meant to save battery.
Click to expand...
Click to collapse
Its battery saving with the smartassv2 settings I provided

ozkoidz said:
Its battery saving with the smartassv2 settings I provided
Click to expand...
Click to collapse
There's definitely better governors suited for battery savings though. Ondemand or conservative, for instance.

Lol. Just lol.
Sent from my Nexus S 4G using XDA

if youre only getting 8-9 hours with your setup - i dont think thats good at all....
ozkoidz said:
Just thought I should share this info.. I've literally tried every combination of everything and after a few days I've settled for this combination..
Best of performance and battery life Ive ever used.
I've searched everything everywhere and this beats everything recommended.
rom: slimics 4.0
lcd density: 200
theme: cobalt
launcher: apex launcher pro
kernel: matr1x cfs 20.0
nstools settings
-----------------
io scheduler: sio
governor: smartassv2
min cpu: 100MHz
max cpu: 1300MHz
deep idle: on
default voltage
smartassv2 settings:
awake ideal freq: 400000 Hz
sleep ideal freq: 100000 Hz
sleep wakeup freq: 400000 Hz
min cpu load: 50 %
max cpu load: 85 %
ramp down step: 200000 Hz
ramp up step: 200000 Hz
down rate: 49000 us
up rate: 48000 us
Click to expand...
Click to collapse

NOOP any better!!

Finally: Underclocked and much cooler GPAD

At first... sorry for my english.
Standard disclaimer.
I am not responsible for any damage or problems you may have!
Use at your own risk.​
Any try to underclock in the past with many apps get failed for Qualcomm mpdecision control of cpu frequency... ONLY 1st core are underclockable, disabling mpdecision with trickster mod give some results... randomly.
Running antutu many times we get worst results when cpu is hot. It's the Thermald that scale the frequency according to a table in respect of the temperature...
A simple idea... a simple trick... edit thermald!
edit the file:
/system/etc/thermald-8064.conf
and reboot.
original:
Code:
[pa_therm0]
sampling 5000
thresholds 44 47 50 53 57 60 70
thresholds_clr 40 45 48 51 55 58 61
actions cpu+gpu+battery+hotplugcpu+lcd+fps cpu+gpu+battery+hotplugcpu+lcd+fps cpu+gpu+battery+hotplugcpu+lcd+fps cpu+gpu+battery+hotplugcpu+lcd cpu+gpu+battery+hotplugcpu+lcd cpu+gpu+battery+hotplugcpu+lcd cpu+gpu+battery+hotplugcpu+lcd
action_info 1728000+400000000+1+0+255+60 1512000+400000000+2+2+231+60 1242000+400000000+3+2+219+54 1242000+320000000+3+2+200 1134000+320000000+3+2+185 1134000+200000000+4+2+185 1134000+128000000+4+3+145
[batt_therm]
sampling 5000
thresholds 350 380 410 440 470
thresholds_clr 340 370 400 430 460
actions cpu+lcd+gpu+battery+hotplugcpu cpu+lcd+gpu+battery+hotplugcpu cpu+lcd+gpu+battery+hotplugcpu cpu+lcd+gpu+battery+hotplugcpu cpu+lcd+gpu+battery+hotplugcpu
action_info 1728000+218+400000000+0+0 1728000+180+320000000+0+0 1134000+180+320000000+1+0 1134000+180+200000000+2+0 1134000+128+200000000+2+2
modified: (you can edit the values according to your needs, for me this is the best performance/cooling)
Code:
[pa_therm0]
sampling 5000
thresholds 14 44 47 50 53 57 60 70
thresholds_clr 10 40 45 48 51 55 58 61
actions cpu+gpu cpu+gpu+battery+hotplugcpu+lcd+fps cpu+gpu+battery+hotplugcpu+lcd+fps cpu+gpu+battery+hotplugcpu+lcd+fps cpu+gpu+battery+hotplugcpu+lcd cpu+gpu+battery+hotplugcpu+lcd cpu+gpu+battery+hotplugcpu+lcd cpu+gpu+battery+hotplugcpu+lcd
action_info 1350000+320000000 1350000+320000000+1+0+255+60 1350000+320000000+2+2+231+60 1242000+320000000+3+2+219+54 1242000+320000000+3+2+200 1134000+320000000+3+2+185 1134000+200000000+4+2+185 1134000+128000000+4+3+145
[batt_therm]
sampling 5000
thresholds 350 380 410 440 470
thresholds_clr 340 370 400 430 460
actions cpu+lcd+gpu+battery+hotplugcpu cpu+lcd+gpu+battery+hotplugcpu cpu+lcd+gpu+battery+hotplugcpu cpu+lcd+gpu+battery+hotplugcpu cpu+lcd+gpu+battery+hotplugcpu
action_info 1350000+218+320000000+0+0 1350000+180+320000000+0+0 1134000+180+320000000+1+0 1134000+180+200000000+2+0 1134000+128+200000000+2+2

Very nice, will have to give this a go!

So to convert this to human, both stock and mod throttles down to cpu 1.13ghz cpu and 128mhz gpu at 70c and act about the same till 50c.
below 50c the mod throttles down to 1.35ghz, while stock goes to 1.7ghz. That seem about right?

you can check CPU states with perfmon http://forum.xda-developers.com/showthread.php?t=1933284
CPU temp with xposed module
gpu with trickster mod

nightanole said:
So to convert this to human, both stock and mod throttles down to cpu 1.13ghz cpu and 128mhz gpu at 70c and act about the same till 50c.
below 50c the mod throttles down to 1.35ghz, while stock goes to 1.7ghz. That seem about right?
Click to expand...
Click to collapse
they throttle also lcd, fps, battery
i've introduced a step at 14 to lock the freq at a cooler temp.
throttle are commanded by thresholds and thresholds_clr value.
in original at first step:
"thresholds" 44 when temp raise 44 then throttle by "actions" value
"thresholds_clr" when temp below 40 then reset value (clear).
and so on 44 -> 47 -> 50 ->
and 40 <- 45 <- 48 <-

First, great finding dude!
But, you have to change the "holes" in your temps, the temperatures are a range, like 10-14 and 44-10, you have a hole in 15 to 43, you have to change to 10-43 for it to work like you want. And not leave any hole in the other temps too.
And not forget that the file need to be rw-r-r.

Power Profiles for FrancoKernel and Kernel Manager FK app

So I wanted a different thread to make a list of different Power Profiles from users of my custom Kernel. My threads are usually pretty big so it gets hard to manage and this is also a safe place for me to post the defaults I'm using.
I'll review each profile and include your Power Profiles in the app if they seem to make sense.
Please follow the template below when posting. Keep off-topic, requests, etas and useless conversations out of here.
FrancoKernel defaults:
Low Power Cluster
Max CPU freq: 1440000
Min CPU freq: 384000
Governor: interactive
Governor parameters:
above_hispeed_delay 0
go_hispeed_load 100
hispeed_freq 0
target_loads 85 600000:45 787200:50 960000:60 1248000:80
timer_rate 20000
min_sample_time 60000
ignore_hispeed_on_notif 1
max_freq_hysteresis 80000
timer_slack 30000
Max Power Cluster
Max CPU freq: 1824000
Min CPU freq: 633600
Governor: interactive
Governor parameters:
above_hispeed_delay 20000 960000:40000 1248000:20000
go_hispeed_load 90
hispeed_freq 960000
target_loads 90 1248000:95
timer_rate 30000
min_sample_time 20000
ignore_hispeed_on_notif 1
max_freq_hysteresis 80000
timer_slack 30000
Input boost frequency
Low power cluster: 1248000
Performance cluster: 768000
Input boost duration
1500
Join the beta here http://beta.franciscofranco.xyz and starting with the next beta8 profiles will be included and be available to apply in a single tap.
FrancoKernel thread: http://n5x.franciscofranco.xyz

Saved to post profiles from users.

Saved to post profiles from users.

What's your opinion on these?
I'm using the Glassfish 1.2 profile since 2 days with your latest kernel, seems to be working great, cannot give an elaborate opinion yet though, obviously.

sigurd_LU said:
What's your opinion on these?
I'm using the Glassfish 1.2 profile since 2 days with your latest kernel, seems to be working great, cannot give an elaborate opinion yet though, obviously.
Click to expand...
Click to collapse
I think there's a lot overcomplication in all of those, but I'll include one or other because users like to play with 'em.