Yea, it's been working alright for me as well. Definitely better than I expected. Not perfect, but absolutely usable.
Apparently there is talk of another driver that will be ready soon. I don't know the details, Oren would be the better person to ask about that in the Telegram. But supposedly we will get a more stable driver soon.
Fast enough for general daily use in my experience. It can be enabled with "sudo systemctl start pinetab2-wifi-enable" in the terminal and a restart (the command only needs to be run once, it will be persistent afterwards and WiFi will remain enabled through future restarts).
The speeds are good enough for Youtube and general web browsing. Downloads are a little slow (around 6mbps or so for me), but luckily most of the apps are fairly small and don't take much time to install. The only issue I've really had with the driver is that WiFi sometimes disconnects itself (maybe once every couple of days or so) and occasionally requires a tablet restart to detect, but this doesn't happen often enough for it to be much more than a minor nuisance for me.
Personally, I don't use a dongle. I've just been using the built in WiFi, and it's worked well enough for me.
The Pinetab devices don't support ADB (at least, not to my knowledge), so SSH must be used instead. I had to use a couple of workarounds to get SSH access working, so I wanted to share the process here for anyone else who may need to get SSH support enabled.
Firstly, you'll need to copy a public key from your computer (the device you will be connecting from). If you don't have one, you will need to run "ssh-keygen" in your computer's terminal. When prompted, type in a name for the key (or just use the default "id_rsa" name if you wish), then go into ~/.ssh and copy the .pub file (it will be called id_rsa.pub if you've used the default names in ssh-keygen).
Next, we will need to get our newly created .pub public key onto the Pinetab, which will require a flash drive. I had some difficulties using the built in file browser to copy/paste, so I had to use the terminal to do this. Open a terminal on your pinetab, and run:
Copy SSH key from flash drive:
Set correct permissions for SSH key and folder:
Optional: Add to authorized keys (prevents password prompts upon login)
(This step is optional, but is recommended if you intend on connecting to your Pine64 device for Clickable projects.)
Finishing up:
Now that we have the SSH key copied and have set the correct permissions, we are almost ready to start the SSH service on the pinetab. However, we must employ one more workaround to create host keys. Otherwise, we will see a "ssh.serviceJob for ssh.service failed because the control process exited with error code."
Create host keys:
Lastly, we must get the IP address on our Pinetab so that we can use this to connect:
(This will spit out several values, each separated by a space. We're only concerned with the first one, which is the iP address of our Pinetab on the network).
Now, we can head over to our computer and connect. Run:
This should be all that you need to get connected to your Pinetab 2 via SSH! 
Just joined after watching some of the live streams from the UBPorts team on YouTube. Installed UBPorts on my Pinetab and loving it so far!
Hello everyone,
I was recently able to overclock my Pinetab 2 on UbPorts, so I figured I'd share a guide here. I was able to get mine to run stably at 2GHZ (some might be able to push it further, but Cortex A55s aren’t known for being able to reach especially high clock speeds, so your mileage may vary). I did overvolt mine slightly just to ensure stability, although it worked without the overvolt as well. I'll provide both configurations here, you may decide which one you are more comfortable with.
Firstly, you'll need something called "device tree compiler" from apt. I’m also assuming that nano is installed, but you can use the text editor of your choice.
Open your terminal and run:
Now, we must convert the DTB files to DTS files so that we can edit them. The Pinetab 2 actually has two DTB files that we will need to edit. Technically, only one of these is loaded by the bootloader, but it can be difficult to tell which one is loaded after bootup (the bootloader takes care of this transparently from the kernel, so Linux itself is unaware of which file was actually loaded). We will edit both just to be sure. (As always, it’s a good idea to create a backup of your /boot folder before editing these. If you botch the overclock, having a backup will make it much easier to restore your old settings. )
Now, we will be able to edit these newly created DTS files to edit the clock speeds with nano (or your favorite text editor of choice). Around line 91, you will see the beginning of an opp table with “opp-table-0” values, which identify valid clock speeds and voltages for the processor. We will add a couple of lines at the end of this block, below the 1800000000 block. We will do the same process for both DTS files.
Note that voltages are provided in hexadecimal here. I will provide two different configurations that you can use, one of which uses default voltages (1.15 volts) and the other of which has a slight overvolt to 1.20 volts. Your mileage may vary. My tablet was stable on both configurations, but some tablets may be more stable with a slight overvolt (do keep in mind that the Pinetab 2 is a passively cooled device, so do this at your own risk).
If you would like to preserve default voltages (without an overvolt), add the following:
opp-2000000000 {
opp-hz = <0x00 0x77359400>;
opp-microvolt = <0x100590 0x100590 0x118c30>;
};
If you would like a modest overvolt to 1.20v (may improve stability, but increases heat dissipation and power consumption) use the following:
opp-2000000000 {
opp-hz = <0x00 0x77359400>;
opp-microvolt = <0x10C8E0 0x10C8E0 0x124F80>;
};
(This is a fairly modest overvolt, which is unlikely to be particularly risky as far as overclocking goes. However, please keep in mind that this is not a risk-free thing! Overvolting can increase the chance of overheating the device. Mine performs fine and hasn’t throttled under load, but make sure you are aware of the risks before attempting to overclock a device with overvolting. Your mileage may vary, and the silicon lottery is real.)
Once you’ve added these settings to your DTS files, we will need to convert them back to DTB files before we can reboot for the new settings to take effect.
This will spit out some warnings, which can safely be ignored (so long as there are no errors. Warning messages are expected).
Now, reboot your pinetab 2. Then monitor the clock speed in the terminal to ensure that the device is reaching 2ghz:
(Note that this only watches core 0. However, this should be enough to ensure that the device is reaching your new clock speed. Make sure to put some load on the device, as the device will downclock during idle periods to save battery life. Ensure that the device reaches 1.99 or 2.00 ghz under load.)
Once you’ve verified that your tablet reaches the desired clock speed, the overclock is complete! You may now use your newly “upgraded" tablet, and enjoy your new ~11% clock speed increase.
Disclaimer: Do this at your own risk! I haven’t shared any settings I have not tried successfully on my own device, but your mileage may vary. Do not overclock your device if you are not completely comfortable with a little bit of risk beforehand!