https://help.nanominer.org/article/168-gpu-and-cpu-control
By default Nanominer sets the memTweak option to 1. This slightly improves memory timings. However it introduces a little bit of UI lag. This can be a problem if you are trying to use your computer for other tasks. The simple resolution is to change/add the memTweak setting to 0.
memTweak=0
Example config
wallet = WALLET_ADDRESS ; Coin to mine. coin = ETH ; (Optional) Rig (worker) name. rigName = EthMiner memTweak=0
The idea behind this post is to explore some of the differences between both File Explorer and Finder and bring out some of the Pros and Cons of each. They both accomplish the task they need to, so which one is “better” is largely going to be up to your personal preference.
Deleting multiple files results in a list of files waiting to be deleted till the first task gets completed. Can cause issues if the first folder you are trying to delete has some file that is not available or something and holds up the rest of the deletes till you confirm, skip etc.
I personally really like being able to see the speed the file(s) are transferring at.
Both file browsers sort files and folders differently by default. Note, it looks like recent versions of Windows have changed this to be similar to like it is in Finder.
Finder – List folders and files together
Explorer – Generally folders are at the top, files underneath
I have mixed feelings on this. At times I do like that all my folders are at the top so when I am navigating somewhere I don’t have to go scrolling down to locate them. However it is nice to have them together alphabetically so if you comparing if you have a zipped and unzip file, they are right next to each other.
I do like in Finder how you can view the hierarchy side by side in columns. Makes navigating the filesystem easy.
CMD + Shift + G is super handy and nice that it has tab completion.
Zipping and unzipping files is awesome and simple in Finder. Don’t have to go through any “complicated process” of unzip file, pick location, unzip and open that location and now you have two windows open etc.
Doesn’t give you a warning when you are about to open up a ton of files that will slow your computer down.
I seem to have random issues with Finder when working with external drives. Seems like using the command line to run a rm command can be faster then deleting in Finder. Not sure if it is a Finder issue or my extra drives.
Generally very powerful. Lots of options.
I like how the properties option is at the bottom of the menu when you right click on a file.
Gives you a warning or just doesn’t open the files when you select a ton of files and hit enter
Can be slow when there are tons of files in a folder which can be extremely frustrating.
It is interesting the differences between MacOS and Windows. Apple it seems limits what they work on and do a good job what they do work on. However there are those cases where it appears that they didn’t try programming any safe guards in (i.e. No warning about opening up a ton of files at once).
At the end of the day both Windows Explorer and macOS Finder work well and get the job done.
Looks like the problem is caused by the Windows Hypervisor Platform. Work around is to disable it.
In the Start menu search for “turn Windows features on or off”
Once open, disable “Virtual Machine Platform” and “Windows Hypervisor Platform”
You will need to reboot after it finishes.
If you want the Negative button to not execute any command when clicked, you can specify null
.setNegativeButton("Cancel", null)
or if we want to run stuff when Cancel is clicked
.setNegativeButton("Cancel") { dialog, which ->
variable = true
Toast.makeText(this, "Cancel hit!", Toast.LENGTH_SHORT).show()}
.create()?.show()By default the U Installer redirects you to a page asking you to download the app. You can get to the actual U Installer web page by going to https://169.254.169.169
It has the same interface as a regular Airmax M equipment.
Which start up program is this? Did I install it???
Enabling the Command line view will show us the location of the executable. Right click on the Top Row and Check “Command line”
From the Command line column we see that the program is Tomboy
OLED screens have had issues on Linux. Main problem is unable to control the screen brightness. It looks like there are some ways to do it now
Looks like icc-brightness should help. Install instructions are from here
sudo apt install -y liblcms2-dev git clone https://github.com/udifuchs/icc-brightness.git cd icc-brightness make
You can run the utility with
./icc-brightness
Installing it will set it up to automatically run on log in.
sudo make install
Log out and back in and it should work.
https://appaper.com/oled-laptop-screen-brightness-control-linux/
https://www.reddit.com/r/linux/comments/cmf0vi/the_state_of_oled_brightness_on_linux/
We can remove the border and shadows from a button by adding the following style code in your activity_main.xml file. Or what ever your XML file is.
style="?android:attr/borderlessButtonStyle"
Code for button. We are setting an image as the background.
<Button
android:id="@+id/button"
style="?android:attr/borderlessButtonStyle"
android:layout_width="48dp"
android:layout_height="48dp"
android:background="@drawable/gear"
android:onClick="launchSettings"
android:textSize="12sp"/>
Comparison of buttons. One on the left still has the shadow on it
More info here
https://stackoverflow.com/questions/28756035/how-to-remove-button-shadow-android
https://stackoverflow.com/questions/27867284/remove-shadow-effect-on-android-button/30856094
https://askubuntu.com/questions/6995/how-to-enable-ufw-firewall-to-allow-icmp-response
Open up the UFW before.rules config file
vi /etc/ufw/before.rules
And make sure you have these rules in it
# ok icmp codes for INPUT -A ufw-before-input -p icmp --icmp-type destination-unreachable -j ACCEPT -A ufw-before-input -p icmp --icmp-type time-exceeded -j ACCEPT -A ufw-before-input -p icmp --icmp-type parameter-problem -j ACCEPT -A ufw-before-input -p icmp --icmp-type echo-request -j ACCEPT # ok icmp code for FORWARD -A ufw-before-forward -p icmp --icmp-type destination-unreachable -j ACCEPT -A ufw-before-forward -p icmp --icmp-type time-exceeded -j ACCEPT -A ufw-before-forward -p icmp --icmp-type parameter-problem -j ACCEPT -A ufw-before-forward -p icmp --icmp-type echo-request -j ACCEPT
In Kotlin you can request if the WiFi adapter is on or off with the following code
This changes the text on a textbox, replace with your textbox.
wifiManager = this.applicationContext.getSystemService(Context.WIFI_SERVICE) as WifiManager
textBox.text = "WiFi State = ${wifiManager.wifiState}"
The important part is
wifiManager.wifiState
It will return a number from 0-4 which indicates if it is on or off.
0 = WiFi is being disabled
1 = WiFi Disabled
2 = WiFi is being enabled
3 = WiFi is Enabled
4 = Error