Develop Bugs

[Q] HAVS + CPU Control & [Q] Battery Applications

I have a HAVS kernel (Net's 4.2.2 SBC CFS Aggressive HAVS) and as I understand it any sort of CPU Tweaking application will cause conflict and probably a system crash, correct?
Also, can some recommend me any applications that compliment Juice Defender well. I have Juice Plotter already. I am looking for an aggressive auto task killer that's customizable along with any other suggested applications. Thank you!

A system crash is a possibility but they will basically just counteract each other and either make your battery life worse or give a performance hit.
SetCPU helps dynamically underclock/overclock based on certain scenarios. You can set what scenarios you want. Another option is AutoKiller. It isn't Auto Task Killer. Its a different application. Not quite sure how this works but you can research it. However Froyo does a good job managing most applications.
But if you are looking for customization I would go with SetCPU and AutoKiller

Thank's however since I'm running a HAVS kernel I won't use SetCPU. However I will look into Autokiller. Thanks

Vulf said:
Thank's however since I'm running a HAVS kernel I won't use SetCPU. However I will look into Autokiller. Thanks
Click to expand...
Click to collapse
o.o a ton of people use set cpu with havs... its not setting voltages... its setting the cpu speed...

I just installed setcpu and ran it. My phone crashed about 10 seconds after I allowed root access. Tried twice more with same results.

aimbdd said:
o.o a ton of people use set cpu with havs... its not setting voltages... its setting the cpu speed...
Click to expand...
Click to collapse
Its the governors that conflict. Not sure on the exact technical specifics but think of it like OCing a comp.
Some mobos have dynamic OCing. They adjust voltages based on CPU draw. If SetCPU sets CPU speed but HAVS reduces voltage... it would cause a crash. Its always better to have one thing deal with both CPU and voltage.
I'm not a full blown expert with kernels and how they function. All I know is to not mess around with SetCPU + HAVS kernels. It was always unstable or a massive battery drain for me based on my testing.

sekigah84 said:
Its the governors that conflict. Not sure on the exact technical specifics but think of it like OCing a comp.
Some mobos have dynamic OCing. They adjust voltages based on CPU draw. If SetCPU sets CPU speed but HAVS reduces voltage... it would cause a crash. Its always better to have one thing deal with both CPU and voltage.
I'm not a full blown expert with kernels and how they function. All I know is to not mess around with SetCPU + HAVS kernels. It was always unstable or a massive battery drain for me based on my testing.
Click to expand...
Click to collapse
Setcpu does not do anything that a user with root access and terminal emulator can't. Setcpu does not actively do anything related to cpu speed or voltage in way shape or form. What setcpu does do is set the min and max speed the cpu can scale to and the parameters specific to the governor (up-threshold for one).
The governors also don't conflict with setcpu because setcpu does not do anything that a governor does.
The only things setcpu does is allow you to specify what governors and cpu speeds to use during screen on/off, charging, and battery levels through the use of a gui.
Technically setcpu does not interfere with havs its the settings that cause the issues. Again, what setcpu does any root user with te can do. If you issue the wrong settings in te and your device "crashes" is the user going to blame the settings or te? With the way some people are they would probably claim te interferes with havs instead of realizing that the setting combo they issued is not stable.
Setcpu is a great gui to tweak cpu parameters but don't confuse it with an app that actually controls the dynamic cpu frequency scaling or its voltages.

lovethyEVO said:
Setcpu does not do anything that a user with root access and terminal emulator can't. Setcpu does not actively do anything related to cpu speed or voltage in way shape or form. What setcpu does do is set the min and max speed the cpu can scale to and the parameters specific to the governor (up-threshold for one).
The governors also don't conflict with setcpu because setcpu does not do anything that a governor does.
The only things setcpu does is allow you to specify what governors and cpu speeds to use during screen on/off, charging, and battery levels through the use of a gui.
Technically setcpu does not interfere with havs its the settings that cause the issues. Again, what setcpu does any root user with te can do. If you issue the wrong settings in te and your device "crashes" is the user going to blame the settings or te? With the way some people are they would probably claim te interferes with havs instead of realizing that the setting combo they issued is not stable.
Setcpu is a great gui to tweak cpu parameters but don't confuse it with an app that actually controls the dynamic cpu frequency scaling or its voltages.
Click to expand...
Click to collapse
Ahh there. someone more knowledgable then me explains it perfectly.
I've run set cpu plus haves kernel for the last month... as have almost everyone using savagedzen.. thats what they recommend. If it was causing issues i am sure we would know by now. 100%stable... 0 random reboots! (well... accept for when i didn't follow directions xD)

aimbdd said:
Ahh there. someone more knowledgable then me explains it perfectly.
I've run set cpu plus haves kernel for the last month... as have almost everyone using savagedzen.. thats what they recommend. If it was causing issues i am sure we would know by now. 100%stable... 0 random reboots! (well... accept for when i didn't follow directions xD)
Click to expand...
Click to collapse
I believe you and am not discrediting you but how come when I run SetCPU on a kernel with HAVS, it crashes? (Tried 4.3.1 and 4.2.2.) I moved the maximum value from the default 944 by maybe one or 2 notches up and the device freezes and crashes. Maybe Netarchy's kernels aren't compatible with CPU Tweaking programs? Anyone out there running a Netarchy Kernel w/ HAVS + SetCPU successfully?

Vulf said:
I believe you and am not discrediting you but how come when I run SetCPU on a kernel with HAVS, it crashes? (Tried 4.3.1 and 4.2.2.) I moved the maximum value from the default 944 by maybe one or 2 notches up and the device freezes and crashes. Maybe Netarchy's kernels aren't compatible with CPU Tweaking programs? Anyone out there running a Netarchy Kernel w/ HAVS + SetCPU successfully?
Click to expand...
Click to collapse
Again, it is not setcpu it is your settings. You said you moved the slider "one or two notches up" (overclock) from the default 944? The evos default max is 998. Either way, with what you said you are overclocking and your device cannot handle the overclocked speed.
Like I said, you can do the exact same thing that setcpu does through terminal emulator. Instead of blame setcpu you should observe the speed/governor combo you are using.
I can oc my evo to 1.26 on my personal kernel without it rebooting on certain governors but on others it would reboot randomly and I don't set cpu parameters through setcpu, I use te, init scripts, and tasker.

lovethyEVO said:
Setcpu does not do anything that a user with root access and terminal emulator can't. Setcpu does not actively do anything related to cpu speed or voltage in way shape or form. What setcpu does do is set the min and max speed the cpu can scale to and the parameters specific to the governor (up-threshold for one).
The governors also don't conflict with setcpu because setcpu does not do anything that a governor does.
The only things setcpu does is allow you to specify what governors and cpu speeds to use during screen on/off, charging, and battery levels through the use of a gui.
Technically setcpu does not interfere with havs its the settings that cause the issues. Again, what setcpu does any root user with te can do. If you issue the wrong settings in te and your device "crashes" is the user going to blame the settings or te? With the way some people are they would probably claim te interferes with havs instead of realizing that the setting combo they issued is not stable.
Setcpu is a great gui to tweak cpu parameters but don't confuse it with an app that actually controls the dynamic cpu frequency scaling or its voltages.
Click to expand...
Click to collapse
Couldn't have said it better. The common misconception around these parts is that SetCPU has some negative effect on kernels with HAVS and this is just untrue.

Maybe I'm getting some terrible luck. I've always gotten negative results from using both SetCPU and HAVS. Tried different settings and recommended settings from others. As well as trying to tweak it myself. Not working so I just removed it and HAVS worked better on its own.
Sorry for the misinformation.

sekigah84 said:
Maybe I'm getting some terrible luck. I've always gotten negative results from using both SetCPU and HAVS. Tried different settings and recommended settings from others. As well as trying to tweak it myself. Not working so I just removed it and HAVS worked better on its own.
Sorry for the misinformation.
Click to expand...
Click to collapse
The common practice with setcpu is to use it to underclock when sleeping. Depending on the governor you use (besides powersave) you are actually causing the cpu to struggle when completing tasks if you limit the max to 245 for example. During sleep if it needs to perform a task and that task would normally complete in 1 second at 998 mhz imagine how much longer it would take if it was capped at 245.
I have had better results not underclocking while sleeping. I would suggest using setcpu to specify to use the conservative governor when sleeping, ondemand/interactive/smartass when screen on (depending on which one you want), and interactive/ondemand while charging without under/overclocking at all and using the default freqs (245 - 998). I'm certain you would be surprised at how your evo behaves after that.

I don't know though... if race to idle applied here why would phone manufacturers ever under clock their phone? It kind of confuses me. Rti applies to computers but not phones? doesn't make sense.

aimbdd said:
I don't know though... if race to idle applied here why would phone manufacturers ever under clock their phone? It kind of confuses me. Rti applies to computers but not phones? doesn't make sense.
Click to expand...
Click to collapse
My last post may have been a bit confusing so I will clarify. When I said underclock I was referring to the practice of capping the max freq to 245 which is what most people do. If you cap the freq at 245 you are essentially underclocked all the time and would cause your cpu to work harder.
The evo underclocks automatically when the cpu load is low enough (idle for example) to save on power, reduce temps, and to basically keep the system running. But I would assume that most of us who have used setcpu have seen how lousy the evo runs when it can't scale up (locked at 245) when using the evo. The governors will underclock the cpu on their own if the device reports it does not need the higher freqs and this occurs during sleep/screen off as well.

Ugh this is quite frustrating. Perhaps it's the current kernel I'm using that's the problem?

Vulf said:
Ugh this is quite frustrating. Perhaps it's the current kernel I'm using that's the problem?
Click to expand...
Click to collapse
Have you done testing to make sure your phone plays well with the more aggressive kernel? If using SetCPU is causing your phone to reboot then you may want to adjust your overclock, switch to the less aggressive kernel, or update to the newest netarchy SBC powered kernel; 4.3.2.

freeza said:
Have you done testing to make sure your phone plays well with the more aggressive kernel? If using SetCPU is causing your phone to reboot then it you may want to adjust your overclock, switch to the less aggressive kernel, or update to the newest netarchy SBC powered kernel; 4.3.2.
Click to expand...
Click to collapse
I'm not sure how I would go testing my kernel? I mean I've been using it since yesterday morning and there haven't been any FC's/phone crashes or anything strange so I guess the aggressive HAVS works well with my phone. I'll try upgrading to 4.3.2. I'm assuming it works fine for you?

freeza said:
Have you done testing to make sure your phone plays well with the more aggressive kernel? If using SetCPU is causing your phone to reboot then it you may want to adjust your overclock, switch to the less aggressive kernel, or update to the newest netarchy SBC powered kernel; 4.3.2.
Click to expand...
Click to collapse
This.
Very sound advice and yes some evos can't undervolt as well as others. Always remember too that the stock kernel for the evos use CFS. If you are using a bfs kernel that could also cause issues. Some evos run better with bfs versus cfs but it's really going to come down to the amount of time you want to put into testing and confirming what your evo likes.

Vulf said:
I'm not sure how I would go testing my kernel? I mean I've been using it since yesterday morning and there haven't been any FC's/phone crashes or anything strange so I guess the aggressive HAVS works well with my phone. I'll try upgrading to 4.3.2. I'm assuming it works fine for you?
Click to expand...
Click to collapse
Yeah, it does. How far are you trying to overclock before your phone freezes/reboots?

[Q] Calk's Preset Profiles to save battery question?

Notes about Battery Saver script
Can be used with kernels that have init.d support
It completely eliminates the need for an application to set CPU speeds or profiles
Easily customizable if you use a text editor(scripts located in /system/etc/init.d)
It will set Max CPU speed to 500MHz & Min CPU speed to 200MHz when a sleep
If SetCPU, Overclock Widget, Android Overclock or QuickClock Advanced Overclock are detected, the script is ignored, so it will not affect them
Preset profiles are:
1.2GHz - 100-85%
1.0GHz - 84-36%
800MHz - 35-0%
And just an FYI, even at 800MHz, the phone still operates very well & smooth but the battery saving are the real benefit
Click to expand...
Click to collapse
Does this mean that if I don't use Set CPU or any app that undervolt it, the phone will AUTOMATICALLY drop the CPU speed according to my battery level:
1.2GHz - 100-85%
1.0GHz - 84-36%
800MHz - 35-0%
Another word, it will automatically drop CPU speed to 800 MHZ when my battery level is 35-0% in order to save battery?

It won't "Drop" the CPU speed, it will lower the Maximum speed the CPU is allowed to ramp up to.

Drumrocker said:
It won't "Drop" the CPU speed, it will lower the Maximum speed the CPU is allowed to ramp up to.
Click to expand...
Click to collapse
So if I am not doing CPU intensive stuff and just play simple games, email, web surfing phone call, then I am not going to see battery improvement since my CPU probably don't ramp past 800MHZ anyway when I am just doing simple stuff.?

Calk's ROM undervolts the CPU at all speeds so that in itself should help a little with battery life. But you are correct, if you are not doing CPU intensive tasks the CPU probably isn't spending much time at the higher speeds.
There is an app called CPUSpy which shows how much time the CPU has spent in each frequency state.

Your phone will ramp up to 1200 mhz more than you think. When it loads a webpage, it will ramp up to 1200, when it's loading your "simple" game, it will max out for a bit, etc.
It might not stay there for very long, but still. The nice thing about Calkuins rom is that even at 800 mhz, the phone is super smooth and lag free. In fact I just turn setcpu down to 800 all the time.

Let me research setcpu and play around with it. Thanks again for the quick answers.

clamknuckle said:
Your phone will ramp up to 1200 mhz more than you think. When it loads a webpage, it will ramp up to 1200, when it's loading your "simple" game, it will max out for a bit, etc.
It might not stay there for very long, but still. The nice thing about Calkuins rom is that even at 800 mhz, the phone is super smooth and lag free. In fact I just turn setcpu down to 800 all the time.
Click to expand...
Click to collapse
The way Calkulin's rom scripts are setup, setcpu gets reset on every reboot, even if you have it set to boot settings. The scripts installed will still take priority and the old rules apply, just to let you know. So you would have to set setcpu every boot for it to work, that or remove the scripts.
Sent from my SPH-D710 using xda premium

Team era... Does the same idea apply to the blazer 2.0 battery saving script? or does tegrak break it?
Sent from my SPH-D710 using xda premium

I havnt opened that rom, but Im gonna say the same applies, I remove those scripts, 2 will affect the cpu state.
edit, let me clarify, the scripts take prority, even if the app makes a script for init.d, the original script will take over on a reboot. So the script breaks tegrak, setcpu, and voltage control unless you set the app on every reboot.

I am running Calks 2 and desperado kernel. I notice when using setcpu, if you have it set on boot, it will override calks script.
His script does work well on saving battery life though. I ran oc'd while at 20% and still had 1700mhz blazing on performance gov.
I'd still use Calks script over setcpu or tegrak only due to the fact im too sporatic with my phone use to create optimal profiles to fit the way and when i need to use the device.

mindgrind said:
I am running Calks 2 and desperado kernel. I notice when using setcpu, if you have it set on boot, it will override calks script.
His script does work well on saving battery life though. I ran oc'd while at 20% and still had 1700mhz blazing on performance gov.
I'd still use Calks script over setcpu or tegrak only due to the fact im too sporatic with my phone use to create optimal profiles to fit the way and when i need to use the device.
Click to expand...
Click to collapse
Actually in my own testing setcpu will not override the scripts, the slider may stay the same, but trust me, it goes back to 800 (or 1200 over 86%batt), Ive tested it several times. If you want proof Ill tell you how to figure it out. I know Im not respected yet, but I am someone that is known under another name that is highly respected, so, take it as you will.
Sent from my SPH-D710 using xda premium

Era, what's your suggestion for keeping the battery saving scripts running and getting a 1500 ish over clock when needed... something that can do both without having to physically change setcpu everytime. I basically want to permanently over clock to 1.5 and still save as much battery as possible when i have the screen off or it is charging. Idk if setcpu profiles work on this phone because i know they did not work correctly on the galaxy s. And one final question... what voltages do u run at what speeds on the "desperado" kernel to undervolt efficiently?
Sent from my SPH-D710 using xda premium

TeamERA said:
Actually in my own testing setcpu will not override the scripts, the slider may stay the same, but trust me, it goes back to 800 (or 1200 over 86%batt), Ive tested it several times. If you want proof Ill tell you how to figure it out. I know Im not respected yet, but I am someone that is known under another name that is highly respected, so, take it as you will.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
ERA. I wasn't looking to say that you were wrong in any way shape or form. I would be interested to know how you seen this as I am still in the beginning phases of learning the android system. I do plan on writing my own kernal/roms but I was actually sharing what my logical thought process would have been given the apps and system info I had avail.
I have a little ways to go in understanding the structure and FS of droid. Time is everyones enemy. Thanks for the correction again!

I havnt opened that rom, but Im gonna say the same applies, I remove those scripts, 2 will affect the cpu state.
edit, let me clarify, the scripts take prority, even if the app makes a script for init.d, the original script will take over on a reboot. So the script breaks tegrak, setcpu, and voltage control unless you set the app on every reboot.

I'm currently running Calkulin's rom v2.5, and even at 41% battery I notice the cpu still hits 1.2 Ghz. Is his script activated by default or am I overlooking something? I also have nothing like setcpu installed.

[Q] Dynamically change CPU frequencies + governor based on apps running

Hey!
I'm wondering and looking for a solution to dynamically change my CPU frequency and governor while specific apps are running.
For example:
I like to save as much battery as possible while doing everyday tasks like writing texts, emails, browsing or playing undemanding games like Angry Birds. This i can achieve by keeping my frequencies (and thus voltages) low.
But i also love playing with my Playstation and N64 emulators (among other games like the new Max Payne Mobile etc.). They mostly only run at acceptable speeds when my frequencies are in the upper range of 1.5ghz and above. The Vision is absolutely capable of running these things at pretty good speeds!
So my question is:
Is it possible to have an app or tool that dynamically changes my frequency+governor when launching specific apps and reverting the changes once the apps "close"? Or have Widget-Switches for specific frequency profiles? Or is this an idiotic idea? Is it even safe to do so as long as i keep an eye on the temperature?
(I don't care about battery usage when overclocking that high)

Newest setcpu can set up profile to lower/raise cpu frequency per app.
Its a paid app tho.

an0nym0us_ said:
Newest setcpu can set up profile to lower/raise cpu frequency per app.
Its a paid app tho.
Click to expand...
Click to collapse
This is amazing. Thank you so much. It does exactly what i asked for. Awesome!
Never knew that SetCPU is capable of doing that... :good:

Perseus Kernel

ok. Figured out why perseus kernel ran like poo on my device. I noticed on all my 3d games and sometimes on my browser, there would be be occasional stutter or a slighr but noticeable fps drop leading to a jerky stutter performance. even on the tw launcher I would see it here and there. luckily this awesome device has split screen. So I was able to observe the cpu LIVE as it scales. I ran tons of benchmarks and observed the culprit. While the phone is pushing polygons the cpu down scales to fast and way to much. it would bounce from 1.8ghz to 600mhz constantly. When this aggressive down scale happens then you see the stutter. At least I do. So... Here's the fix. Open Stweaks and on CPU SCALING scroll down to FREQUENCY FOR RESPONSIVENESS. Set that to 1.2ghz or above. Done. enjoy your stuttering free performance. Will this impact your battery? Not much. It just keeps the cpu fast when it needs the power. Once you let go of touching the screen then it scale down to below 1.4ghz.

I think your "fix" may work but I don't think it is optimal. See Andrielux's original N7100 thread and you will see that he recommends keeping this parameter no higher than 600mhz because it causes issues above that. I think there are more direct parameters that can be changed regarding down scaling to fix your issue. You should post this on his thread to get his input as he is quite wise.
Sent from my SPH-L900 using xda app-developers app

yup. I kept an eye on it all day yesterday and with cpuspy I noticed my device was hanging allot of time at 1.2. makes sense. I'll play with it more today.

found a better setting change on stweak! You can leave everything on stweak at default and may change........
under CPU SCALING go to UP THRESHOLD AT FAST-DOWN and set that to 25%. Default is 95. Now using cpuspy I see all the clocks being used healthier compared to before where 1.2ghz was hogging up more. And the studder is gone. This makes the cpu hold 1.8. steady and not down scale when using 3d . try it and you will thank me.

Okay I can confirm it now. This is a good fix for the stuttering. my battery has not taken a hit at all. And it runs smooth. And to boot I'm getting a quadrant score on the 7600. this is the change.
under cpu scaling I changed UP THRESHOLD to 70%. UP THRESHOLD AT FAST DOWN to 20%. Under GPU I changed GPU MAX FREQUENCY to 800mhz. And it's UP THRESHOLD to 80%. Everything else is at stock. Now play with the voltage of the cpu to the lowest possible voltages. And you will be thankful.

Is Redmi note 8 pro locked at 2 GHz normal?

i've been using this phone for about 2 years now and recently moved (about a few months ago) to using a custom rom (crdroid 7.1.2). it was running smooth and cool until day the clockspeed decided to lock itself at 2000 MHz (checked using cpu-z). I do not know if this is normal but the phone's temperature goes up to 36C on idle. i thought the problem was with the Lspeed app (+custom kernel) so i uninstalled it but it didn't work. I also factory resetting it, but still not luck. will updating the firmware resolve my issue? if not, what other available solutions are there?

have you thought about flashing the stock kernel ?

Fytdyh said:
have you thought about flashing the stock kernel ?
Click to expand...
Click to collapse
I have, but it still gets hot

do you use a case ? does your phone goes over 45 degrees celsius when charging ?

Fytdyh said:
do you use a case ? does your phone goes over 45 degrees celsius when charging ?
Click to expand...
Click to collapse
I do use a case, but hasn't been this hot before recently, and it does tend to hit 40C when charging

topsecretasian said:
I do use a case, but hasn't been this hot before recently, and it does tend to hit 40C when charging
Click to expand...
Click to collapse
If you are using Fast Charging, that heating is entirely normal (happens to me too)
But heating during idle is not normal. Try changing CPU governor to something else. (like schedutil or powersave)

Canny1913 said:
If you are using Fast Charging, that heating is entirely normal (happens to me too)
But heating during idle is not normal. Try changing CPU governor to something else. (like schedutil or powersave)
Click to expand...
Click to collapse
Do you know how to change cpu governor? I tried doing it last night but didn't find a whole lot of information. Schedutil seems to just set it all the way to 2ghz, so I want to change it to powersave

topsecretasian said:
Do you know how to change cpu governor? I tried doing it last night but didn't find a whole lot of information. Schedutil seems to just set it all the way to 2ghz, so I want to change it to powersave
Click to expand...
Click to collapse
use Rootify, select the CPU tab located at the top then change it.
The app sometimes gets stuck at Loading screen though.

Canny1913 said:
use Rootify, select the CPU tab located at the top then change it.
The app sometimes gets stuck at Loading screen though.
Click to expand...
Click to collapse
ok so it does work when i change the cpu govenor, but the only option that actually works is 'powersave' (as well as 'userspace'). all the other ones still sets it to 2GHz. 'userspace' seems to have a somewhat of an improvement but it's only setting everything to a constant value. is there a way have it set to balanced mode?

topsecretasian said:
ok so it does work when i change the cpu govenor, but the only option that actually works is 'powersave' (as well as 'userspace'). all the other ones still sets it to 2GHz. 'userspace' seems to have a somewhat of an improvement but it's only setting everything to a constant value. is there a way have it set to balanced mode?
Click to expand...
Click to collapse
powersave forces the processor to work in the lowest frequency availible, thus consuming less power.
userspace allows the app to set the CPU frequency whatever it wants. This isn't supposed to be used in Android since changing CPU speed thorough an app is super uncommon.
Others like ondemand normally keep the power low but starts using the higher frequencies if a processor intensive app is launched.
You can learn which governors do what in this post so you can set the most suitable one for you.
[REF][GUIDE]Saber's guide on CPU governors, I/O schedulers and more!
Collective guide of CPU governors, I/O schedulers and other kernel variables I present to you a wonderful collection of descriptions, comparisons and graphs of common kernel variables. Before continuing on the wonderful journey of Linux kernel...
forum.xda-developers.com

Canny1913 said:
powersave forces the processor to work in the lowest frequency availible, thus consuming less power.
userspace allows the app to set the CPU frequency whatever it wants. This isn't supposed to be used in Android since changing CPU speed thorough an app is super uncommon.
Others like ondemand normally keep the power low but starts using the higher frequencies if a processor intensive app is launched.
You can learn which governors do what in this post so you can set the most suitable one for you.
[REF][GUIDE]Saber's guide on CPU governors, I/O schedulers and more!
Collective guide of CPU governors, I/O schedulers and other kernel variables I present to you a wonderful collection of descriptions, comparisons and graphs of common kernel variables. Before continuing on the wonderful journey of Linux kernel...
forum.xda-developers.com
Click to expand...
Click to collapse
I see. Well I guess it does work as a solution.
Thanks for the help!