Adjusting Screen Resolution:
Isn't there a way to adjust screen size or resolution, I feel the default image on the desktop gets cut at the bottom and was curious to see if I can play with resolution like we used to do on a windows desktop where we also adjust the icon sizes!!?
I used the DPI= kernel option for Remix OS. Without it I couldn't see my screen because it is 4k resolution, needed a magnifying glass. Think there are some apps in the play store that will allow you to adjust this. Not sure if they require root though. Now I am curious..........
Checked the Play Store and the DPI changer apps do require root.
erickh said:
I used the DPI= kernel option for Remix OS. Without it I couldn't see my screen because it is 4k resolution, needed a magnifying glass. Think there are some apps in the play store that will allow you to adjust this. Not sure if they require root though. Now I am curious..........
Checked the Play Store and the DPI changer apps do require root.
Click to expand...
Click to collapse
thanks very useful insight!
Hi Sany,
If you want a little more information on the subject you can go here http://technicalcultivation.weebly.com/android . I wrote a short article on the subject of changing your DPI on Android.
erickh said:
Hi Sany,
If you want a little more information on the subject you can go here http://technicalcultivation.weebly.com/android . I wrote a short article on the subject of changing your DPI on Android.
Click to expand...
Click to collapse
Your article is wrong you can set the resolution on android; via wm ie wm size 1204x768 and you can set dpi with wm density 140; and these don't require root afaik.
Thanks for the info, i'll look into it and update.
Alt+F1 to open the command console
wm density (dpi here), then enter
wm size (resolution here), then enter
Alt+F7 to close command window
(Note : This is very experimental. Be very cautious doing it inside open applications as well, and it does persist through reboots. You can easily muck up your display settings, and be forced into reinstalling a new data partition/full install, and it DOES have bearing on open applications, often leading into boot loops per few minutes).
HypoTurtle said:
Your article is wrong you can set the resolution on android; via wm ie wm size 1204x768 and you can set dpi with wm density 140; and these don't require root afaik.
Click to expand...
Click to collapse
How can I access those commands, wm size or wm density ??
chapa_9 said:
How can I access those commands, wm size or wm density ??
Click to expand...
Click to collapse
See post above.
Zeronomous said:
Alt+F1 to open the command console
wm density (dpi here), then enter
wm size (resolution here), then enter
Alt+F7 to close command window
(Note : This is very experimental. Be very cautious doing it inside open applications as well, and it does persist through reboots. You can easily muck up your display settings, and be forced into reinstalling a new data partition/full install, and it DOES have bearing on open applications, often leading into boot loops per few minutes).
Click to expand...
Click to collapse
Hello,
I get a permission error (java.lang.SecurityExcpetion: must hold permission android.permission.WRITE_SECURE_SETTINGS) if i use this command.
Do I have to root Remix OS for it?
G-DaX said:
Hello,
I get a permission error (java.lang.SecurityExcpetion: must hold permission android.permission.WRITE_SECURE_SETTINGS) if i use this command.
Do I have to root Remix OS for it?
Click to expand...
Click to collapse
I have the same error.
what should be done?
If you have installed GRUB, you can edit the start line (first tab, then follow the instructions so you can 'e' edit)
For an interactive choice you can add vga=ask, that will give an overview of the available modes.
If you want to add it permanently, you'll have to modify grub/menu.lst (using a live linux CD or so) and add vga=<your mode in decimal>
Only caveat is that vga=ask shows the mode in hex and you have to add it in decimal to menu.lst
flemlion13 said:
If you have installed GRUB, you can edit the start line (first tab, then follow the instructions so you can 'e' edit)
For an interactive choice you can add vga=ask, that will give an overview of the available modes.
If you want to add it permanently, you'll have to modify grub/menu.lst (using a live linux CD or so) and add vga=<your mode in decimal>
Only caveat is that vga=ask shows the mode in hex and you have to add it in decimal to menu.lst
Click to expand...
Click to collapse
and there is some or team to flip the image from portrait to landscape?
Related
https://i.imgur.com/qfuKKFQ.jpg <- Here's what I get.
I downloaded release_Remix_OS_for_PC_64_B2016020201_Alpha_EFI.zip from the Official Website. Opened the tool inside, and copied the files into my USB 3.0 flash drive using it. Write speeds are higher than 20MB/s. I have a UEFI BIOS. I get the same thing on both Resilient mode and Guest mode. I selected Resilient mode on first launch and the system went through the first launch steps.
When you get to the boot choice of RemixOS remove 'quiet' from the line when TAB and then 'e' for editing it, to show what's going on @ boot time.
most time we solve this by deleting recreating data.img
I hope that helps you
ecksdeeay said:
When you get to the boot choice of RemixOS remove 'quiet' from the line when TAB and then 'e' for editing it, to show what's going on @ boot time.
Click to expand...
Click to collapse
I did that. But this is all I could take a picture of. http://i.imgur.com/7rseNNe.jpg I have no clue what any of it means.
I opened it in guest mode.
imadlatch said:
most time we solve this by deleting recreating data.img
I hope that helps you
Click to expand...
Click to collapse
I dont know how to do that. I cant seem to be able to open the ISO that was in the zip file I downloaded. However, I formatted my flashdrive and used the included tool to reinstall Remix OS. It didnt help.
on the edit line you removed 'quiet' from, put 'DEBUG=1' or just put the '1' on the DEBUG= if it's showing ? I forget if it is but it will go through like before but this time will stop twice where you have to type 'exit' for it to proceed (twice-I repeat!) maybe that'll help? or @imadlatch is more than likely correct?
ecksdeeay said:
on the edit line you removed 'quiet' from, put 'DEBUG=1' or just put the '1' on the DEBUG= if it's showing ? I forget if it is but it will go through like before but this time will stop twice where you have to type 'exit' for it to proceed (twice-I repeat!) maybe that'll help? or @imadlatch is more than likely correct?
Click to expand...
Click to collapse
Here's what I got doing that. http://imgur.com/a/SL1rQ
I never got the second exit prompt. I just got the errors in this https://i.imgur.com/sGo2EQ5.jpg image over and over.
SELinux error. When installing on hardrive the selinux command is passed to the boot line (I'm only guessing here but if you could maybe add this) 'androidboot.selinux=permissive' worth a try?...what are you using as your machine? send feedback from here http://goo.gl/kt1bwC using the Google form https://goo.gl/pcRswT
ecksdeeay said:
SELinux error. When installing on hardrive the selinux command is passed to the boot line (I'm only guessing here but if you could maybe add this) 'androidboot.selinux=permissive' worth a try?...what are you using as your machine? send feedback from here http://goo.gl/kt1bwC using the Google form https://goo.gl/pcRswT
Click to expand...
Click to collapse
androidboot.selinux=permissive is present there by default. Im using a lenovo ideapad y510P with core i7 4700MQ, 8 Gigs of RAM and dual Nvidia GT 755M.
incognitonk said:
Nvidia GT 755M.
Click to expand...
Click to collapse
Nvidia is the problem then. ...
ecksdeeay said:
Nvidia is the problem then. ...
Click to expand...
Click to collapse
Really? Oh well, guess Im gonna be playing the waiting game then.
Thanks for everything up until now.
Search as I think there are work arounds @incognitonk
incognitonk said:
https://i.imgur.com/qfuKKFQ.jpg <- Here's what I get.
I downloaded release_Remix_OS_for_PC_64_B2016020201_Alpha_EFI.zip from the Official Website. Opened the tool inside, and copied the files into my USB 3.0 flash drive using it. Write speeds are higher than 20MB/s. I have a UEFI BIOS. I get the same thing on both Resilient mode and Guest mode. I selected Resilient mode on first launch and the system went through the first launch steps.
Click to expand...
Click to collapse
Its look like its because of your nvdia GPU isssue , don't worry we have solution for this
Select resident mode , don't press enter , press tab you will get into edit mode.
At the end after space write this line - " nomodeset vga = 0x34C "
Without the quote .
Press enter , enjoy remix ☺☺
Hit thanks if it help
mdezazrock said:
Its look like its because of your nvdia GPU isssue , don't worry we have solution for this
Select resident mode , don't press enter , press tab you will get into edit mode.
At the end after space write this line - " nomodeset vga = 0x34C "
Without the quote .
Press enter , enjoy remix ☺☺
Click to expand...
Click to collapse
Thank you, It definitely did help. However the resolution is all wonky now. I have a 1080p screen. The images are all grainy and stretched out. Also, i can see the linux prompt blinking in the background. Anything I type on the keyboard will be entered there. Hence, if i type "reboot" and hit enter, the system will reboot.
I also tried the workarounds in this reddit post: https://www.reddit.com/r/RemixOS/comments/42wylw/any_way_to_run_with_nvidia_gpu/czenutg
But none of them helped either. I get the same issues; the poor resolution and the blinking prompt.
incognitonk said:
Thank you, It definitely did help. However the resolution is all wonky now. I have a 1080p screen. The images are all grainy and stretched out. Also, i can see the linux prompt blinking in the background. Anything I type on the keyboard will be entered there. Hence, if i type "reboot" and hit enter, the system will reboot.
I also tried the workarounds in this reddit post: https://www.reddit.com/r/RemixOS/comments/42wylw/any_way_to_run_with_nvidia_gpu/czenutg
But none of them helped either. I get the same issues; the poor resolution and the blinking prompt.
Click to expand...
Click to collapse
I don't know the blinking error solution , my friend also have that same problem , but there is a easy solution for resolution -
Root remix os , open any rooted browser , go to system folder , then open build.prop , edit the file , just add a line at the end
"ro.sf.lcd_density=150"
Write that line without quote , save build.prop , and change the number between 140 to 210 , see which one looks better on your monitor , have fun exploring remix ☺
I have install and fought (and it has been a fight), to get Remix 2.0.205 installs in VMware and rooted , I actually wrote a script see the rooting thread to mount system rw to allow SuperSU to be updated. However when all is said and done yes it boots, but once rooted and if you update SuperSU as needed, the product is worthless as I'm unable to do anything without rebooting, for instance close chrome (reboot), install apk (reboot, also the app it is not installed), close settings, and click on some icons on the UI such as O.
So basically while you can configure and setup Remix in VMware and even root it, you can not use the OS once rooted, so it is basically useless, if you need root (who don't need root).
Tricks to getting it to work in VMware (that I've discovered):
Use a 32 freebsd as a base (not sure why that matters but it seems to)
use SATA drives, do not use GPT partitions.
Disable advanced graphics
I never could get Remix in VMWARE to run at anything other than 800x600 resolution, no matter what I tried changing DPI only changes text size did not for the display size used, I did not spend time fixing this as I can not used the rooted Image without it rebooting.
Can anyone explain why after updating SuperSU Remix OS fails to function, before updating SuperSU it had no issues, so it has something to do with updating the su binary (normal update as there is no recovery).
Thanks,
ERIC
did you replaced initrd.img with the modified one ?
looks like your system.img still has read-only
imadlatch said:
did you replaced initrd.img with the modified one ?
looks like your system.img still has read-only
Click to expand...
Click to collapse
Yes, I actually wrote a script to adjust the mounting of system.img, when read-only you can not even update SuperSU (fails), Also based on the use of the root prompt (F1) system is mounted read-write.
Actually it is not the OS that restarts, based on uptime but the Remix GUI.
Thanks,
ERIC
The firt U need Root your deives
The Su does not matter what happens
How to adjust the DPI screens
This index higher DPI interface will more loudly and more smooth, but not too big just as well as too large, then everything will be transferred to the interface of the phone should not be spending delectable . DPI is also to small too much content is displayed but text and icons are too small, so we can not see clearly, have pressed themselves into very uncomfortable eyes. Ideally for the middle in a bit tasty.
To change the DPI, the request must be root Remix OS, then you install the app on the Play Store TexdroidDPI about to reset. Extremely simple way of correction, simply enter your desired DPI on, then restart the operating system is finished.
1. there's no option in the settings for updating
2. i can't change the resolutions
i'm not sure how to edit the grub config, i know you can temporarily change it on boot, but even adding UVESA to it, it didnt do anything for me (maybe i did it wrong)
i also tried this http://forum.xda-developers.com/showpost.php?p=67845695&postcount=13
i managed to change the resolution, but the 'physical size' is still 800x600
so right now, no matter what i change it to, it scales it down into 800x600 window
any help would be appreciated
-edit-
well, i took the dumb way approach and just downloaded the .104 iso and did another install
still trying to figure out the resolution situation
does rooting the os cause ota to be disabled? superuser is preinstalled, so i'm confused if this is the case
Using VirtualBox I was able to change the physical size by adding this to the boot options (example):
. . . video=-16 UVESA_MODE=1200x900 INSTALL=1 DEBUG=
(see link).
I do not know whether this works for VMWare, too. Perhaps you can try or use VirtualBox in place of VMWare.
The update is a separate app
I assume that you installed Remix OS in VMWare using the "INSTALL=1" boot option. An OTA update is not possible; it works for pendrive installations only. The update of an "INSTALL=1" installation is described here .
In order to perform the update you need to start a Linux operating system using a pendrive (e.g. PartedMagic), in order to rename the basic directory from the old value (e.g. /android-2016-08-03/) to the value of the current version (e.g. /android-2016-08-11/) and in order to delete all directories within the basic directory other than /data.
After this step you can perform a normal installation (INSTALL=1), but you must not format your partition sda2 because you want to keep your data.
yes, the only way to install it was through install=1
anyways, that's not my problem anymore, the screen resolution is
i need to somehow access the grub file to add vga=xxx, it seems to be the only way i can change resolution
its easy to find the grub install, i can change it to 342 to get near 1200x800 but its terrible still, would be best if someone wrote openvmware-tools udpate for android
I'm Back on XDA!
So, are you tired of the small amount of informations that you can have on your HUGE screen? You are in the right place.
WHAT DO I NEED?
First things first, you need to enable Debug usb under Developer Options (if you don't know how to enable Dev. Options this isn't your place)
After that, you need ADB installed on your computer (Windows/Linux/Mac), you can find it here [url]https://forum.xda-developers.com/showthread.php?t=2588979[/URL]
HOW TO
With Developer Options ENABLED, connect your phone to your pc and launch adb. In ADB type this command
Code:
adb shell wm density xxx
where xxx is your custom DPI value. I found that values BELOW 527 will bug your quick toggles*
*It could depend by your installed theme, Thanks to @SPIDER-7 for reporting that.
HOW DO I RETURN TO THE DEFAULTS VALUES?
Cave_diver said:
To return to the defaults just use the sliders in settings-display-display size
Click to expand...
Click to collapse
SCREENSHOTS
http://i.imgur.com/JyodBYe.png
http://i.imgur.com/fsW1Qtd.png
DISCLAIMER
I'M NOT RESPONSABLE IF THIS PROCESS CREATED A THERMAL NUCLEAR DEVICE
AND / OR TURN YOU INTO FIRESTORM.
NOT RESPONSABLE IF SOMETHING HAPPEN DURING THIS MOD OR IF
YOU DO A MISTAKE DURING THIS PROCESS
I'm Italian so don't blame me for my english.
it works just fine! Thanks, @gsadv . keep it up!
Btw, I'm on value '500 and didn't notice any bugs . will challenge my G6 with lower values .
SPIDER-7 said:
it works just fine! Thanks, @gsadv . keep it up!
Btw, I'm on value '500 and didn't notice any bugs . will challenge my G6 with lower values .
Click to expand...
Click to collapse
Bugs on quick setting may depend by themes. For me 527 is fine, next step is try to get a smaller navbar
i'm going to try 527, but what is the default value if i decided to go back?
To return to the defaults just use the sliders in settings-display-display size
Sent from my LG-H870 using Tapatalk
Cave_diver said:
To return to the defaults just use the sliders in settings-display-display size
Sent from my LG-H870 using Tapatalk
Click to expand...
Click to collapse
original size 640
Hi i have stratos with English firmware.
Is there a way to install APK directly from watch? Without usb connected to PC.
I transferred apk but i am unable to install, the installer crashes everytime.
Is there an easier way to install apk from Android mobile?
Or is there an android adb?
Thanks in advance.
Also my battery is 1 day with GPS always OFF and heartrate always ON. Is this normal?
I have the Pace not the Stratos but I don't think that you can install apps from the watch. It is possible on the Pace to use ADB to enable "unknown sources" and then attempt to install apks from the internal memory, but due to the screen size the installer does not show correctly and it is impossible to finish installing the app.
I would think that results on the Stratos would be very similar even if you found an apk that is compatible it.
I dont have screen size issues, it says installation protected and asks to press ok to install and continue (something similar) then intaller crashes.
Sounds like you got a permission issue.
Have you tried one of these?
adb shell settings put global install_non_market_apps 1
or
adb shell settings put secure install_non_market_apps 1
If you still get a similar error, then you may need root.
anox said:
Sounds like you got a permission issue.
Have you tried one of these?
adb shell settings put global install_non_market_apps 1
or
adb shell settings put secure install_non_market_apps 1
If you still get a similar error, then you may need root.
Click to expand...
Click to collapse
Ok, so after setting both settings menrioned by you i can see the install screen. And unfortunately as you mentioned i cannot see the install button
My watch has 3 buttons and none of them do the CLICK action.
Thank you for the adb commands
Is ther a shell command see all the supported settings?
firoz3321 said:
Ok, so after setting both settings menrioned by you i can see the install screen. And unfortunately as you mentioned i cannot see the install button
My watch has 3 buttons and none of them do the CLICK action.
Thank you for the adb commands
Click to expand...
Click to collapse
I know this is so late but I came across this in my journey to update watch droid assistant.
type the commands they gave you to enable unknown sources, then type adb shell wm density 150, this makes the screen show enough to hit install.
then type adb shell wm density 238 to return to the normal resolution. I know this still requires a computer to keep normal density but there is technically a way.
sonicscrewup said:
I know this is so late but I came across this in my journey to update watch droid assistant.
type the commands they gave you to enable unknown sources, then type adb shell wm density 150, this makes the screen show enough to hit install.
then type adb shell wm density 238 to return to the normal resolution. I know this still requires a computer to keep normal density but there is technically a way.
Click to expand...
Click to collapse
If we have access to PC then there are easier methods to install apk isn't it?
firoz3321 said:
If we have access to PC then there are easier methods to install apk isn't it?
Click to expand...
Click to collapse
In most cases yes, in my case no. I had updated the companion app on my phone, so my watch version was incompatible, instead of revert the phone app, I decided to force the watch to allow me to install. Changing the resolution worked like a charm.
APK installer is easier if you can get the latest apk to your computer, but i could only get it via the app pushing it to the watch.
sonicscrewup said:
In most cases yes, in my case no. I had updated the companion app on my phone, so my watch version was incompatible, instead of revert the phone app, I decided to force the watch to allow me to install. Changing the resolution worked like a charm.
APK installer is easier if you can get the latest apk to your computer, but i could only get it via the app pushing it to the watch.
Click to expand...
Click to collapse
Here is an easy way to install an app on the watch without any screen size issue:
- install the wear part of this-> https://play.google.com/store/apps/details?id=com.sssemil.advancedsettings&hl=en
When installing an apk on the watch using any file manager, just select Advanced Settings instead of the default Package Installer.
anox said:
Here is an easy way to install an app on the watch without any screen size issue:
- install the wear part of this-> https://play.google.com/store/apps/details?id=com.sssemil.advancedsettings&hl=en
When installing an apk on the watch using any file manager, just select Advanced Settings instead of the default Package Installer.
Click to expand...
Click to collapse
Works, but root on watch is required. So it's clear that people with stock firmware (or even common custom ROM with just adb root) cannot use this.
By the way, it seems that if you get adb root and add the permission to install 3rd party apps on watch then it works... I haven't tested this yet tho.
lfom said:
Works, but root on watch is required. So it's clear that people with stock firmware (or even common custom ROM with just adb root) cannot use this.
By the way, it seems that if you get adb root and add the permission to install 3rd party apps on watch then it works... I haven't tested this yet tho.
Click to expand...
Click to collapse
Apparently, sonicscrewup already has all what is required
hi,
anox suggested to install the wear part of this https://play.google.com/store/apps/d...settings&hl=en (
Advanced Settings for Watch) in order to install apk in the watch without pc
but where to find the apk intended to install on the watch (because the
"Advanced Settings for Watch" usually installs on the phone, and then transfers the wear part to the watch)?
I figured it out, probably is not the easier way to do it.
you decompile the phone apk (using apk easy tool), then you will find the wear apk inside the res/raw folder.
you can install it on the watch directly, or probably better, convert it first using this tutorial (https://forum.xda-developers.com/smartwatch/amazfit/android-wear-apps-to-android-read-apk-t3726835)
the "Advanced Settings for Watch" works well in the amazfit to install apks, and to do other things, but of course, there are many features making the app to crash.
cheers
carloscolhao said:
hi,
anox suggested to install the wear part of this https://play.google.com/store/apps/d...settings&hl=en (
Advanced Settings for Watch) in order to install apk in the watch without pc
but where to find the apk intended to install on the watch (because the
"Advanced Settings for Watch" usually installs on the phone, and then transfers the wear part to the watch)?
I figured it out, probably is not the easier way to do it.
you decompile the phone apk (using apk easy tool), then you will find the wear apk inside the res/raw folder.
you can install it on the watch directly, or probably better, convert it first using this tutorial (https://forum.xda-developers.com/smartwatch/amazfit/android-wear-apps-to-android-read-apk-t3726835)
the "Advanced Settings for Watch" works well in the amazfit to install apks, and to do other things, but of course, there are many features making the app to crash.
cheers
Click to expand...
Click to collapse
Yah, I sometimes leave something out. There are already several threads talking about how to install Android Wear app on this watch.
Anyway, an APK file is just a normal compressed ZIP file. So, the quick & easy way to install the wear part of Android Wear app is to:
- Change the file extension from "apk" to "zip"
- Extract the zip file and get the wear APK file inside the res/raw folder to install on the watch
Personally, I don't use any tool or recompile any Android Wear app in order to just install on the watch. I don't see any real world result difference.
Thanks.
I did not realise an apk could be decompressed as a simple zip. Good to know
anox said:
Sounds like you got a permission issue.
Have you tried one of these?
adb shell settings put global install_non_market_apps 1
or
adb shell settings put secure install_non_market_apps 1
If you still get a similar error, then you may need root.
Click to expand...
Click to collapse
Wanted to understand if this setting is maintained across firmware updates. I have a very poor data connection with my charger and this setting is a savior, along with File Manager+. So was wondering if I'm going to lose this at every update.
adityavaidya said:
Wanted to understand if this setting is maintained across firmware updates. I have a very poor data connection with my charger and this setting is a savior, along with File Manager+. So was wondering if I'm going to lose this at every update.
Click to expand...
Click to collapse
Just found this thread tucked away and it works perfectly. No fiddling with any poor USB connections anymore. It's by XDA user zmad2000
https://forum.xda-developers.com/smartwatch/amazfit/amazfit-pace-enable-app-list-install-t3639617
Here's the solution just to ensure that it's archived.
Background
I was have trouble getting my Amazfit Pace to be recognized by the adb program or the ADK installer. When it was in the dock it i could look at the files but not have it recognized by the other apps. I have the Amazfit Pace US version with ROM 1.3.3a
Here are the steps i took.
Enable the "developers mode" by tapping on the legal notice.
Plug in the Amazfit to the computer and put a blank file called "launcher_config.ini" in the main directory
Restart the watch. Once it has booted up connect it via the wifi to the same network your computer is on.
Open and cmd prompt and got to "C:\Users\Rich\AppData\Local\Android\sdk\platf orm-tools" directory (this will differ based on you user name)
Type adb connect (ip address of watch)
Then type adb install (whatever app you want)
Not sure if this is the 100% but it worked for me and my watch was right out of the box. Hope this helps some people.
Click to expand...
Click to collapse
Edit: What I've found is that once you enable developer mode, adb over WiFi is automatically enabled. You don't seem to need that file to be present. Only problem is that adb is now enabled over WiFi at all times when the watch is connected. So there is a security risk, albeit a small one because I'd only connect my watch to my home WiFi.
So all that's required is:
Go to Settings->About
Tap on the Serial number 7 times
Ensure the watch is connected to the same WiFi as your computer
Type adb connect (ip address of watch)
but are you able to install applications directly from the watch?
I did everything but when I try to install using "advanced settings" I always see the word "working" but the installation process never ends
apgeo said:
but are you able to install applications directly from the watch?
I did everything but when I try to install using "advanced settings" I always see the word "working" but the installation process never ends
Click to expand...
Click to collapse
It only works with root, or if you use a modded PackageManager, used in some custom ROMs, after allowing 3rd party APKs installations (non-Market security check).
sonicscrewup said:
I know this is so late but I came across this in my journey to update watch droid assistant.
type the commands they gave you to enable unknown sources, then type adb shell wm density 150, this makes the screen show enough to hit install.
then type adb shell wm density 238 to return to the normal resolution. I know this still requires a computer to keep normal density but there is technically a way.
Click to expand...
Click to collapse
Thanks a lot! That actually worked for me! :highfive: