PineTab
-
@halucigenia I have the same issues with headphones, bluetooth and the microphone on my Pinetab. Morph takes some getting used to and benefits from uAdblock. Morph has hidden reload and close buttons in the adress bar.
-
@matteo that would be nice, but apparently only works on some people's?
Posted from not my pinetab
-
@Yuri I have five ports on my Pinetab; headphone, power, usb, usb 2 Ahost and micro usb OTG. I can't see an sd slot.
-
@Keneda Installing Fench as an addional language changes my screen keyborard when I press the globe.
-
@Yuri
It's not about OSK, but the physical one, with backlight, that makes pinetab a laptop.
Not already availiable as accessory but you can see it here :
https://pine64.com/product/pinetab-10-1-linux-tablet-with-detached-backlit-keyboard/?v=0446c16e2e66 -
Has anyone had any joy with the Bluetooth/Rotation issues
I see they are getting fixed on the other build such as Mobian/Manjaro and Sailfish so would be good to know if those fixes (I know it aint that easy!) are portable from them to us?
-
Is the Pinetab software being worked on or on halt atm? I have a Pinetab Ubports edition, but almost immediately switched to Mobian as Ubports at the time of delivery wasn't very functional. I haven't seen much activity on this forum or elsewhere regarding UBports/Pine64 lately, particularly when it comes to the Pinetab.
-
This has been just discussed in the latest Q&A. Sadly the PinePhone / PineTab seem to have not been the main focus of the core developers in the last few weeks (with personal issues adding on top of that).
And as the PinePhones/Tabs are architecturally quite different from the main bulk of Halium based devices, many changes that are currently made don't benefit those devices.One of the comments on the Q&A where quite interesting though: despite the high number of PinePhones/Tabs sold and the prominent featuring of UT on them, this has apparently resulted in very few additional contributions to UT development. This very strange given the current developer focused nature of these devices, and I fear very many of the initially excited people switched to other software stacks like Mobian shortly after receiving their devices.
While based on comments by the core UT developers this is just seen as an unfortunate fact, without offering further insight, I personally believe this is very much due to the structure of UT itself. As it stands it is just not a very developer friendly environment, with too many hoops to jump through* and architectural differences to more standard Linux distributions.
Thus currently UT seems to be a bit on life support, driven mainly by some very dedicated core contributors (but they show symptoms of developer burnout) and some external developers that are there because they are (for now) stuck with older Android devices.Ultimately this sadly does not bode well for the future of UT, and the current technical debt (old qt and 16.04 base) are further weighting down on it.
I know that some of the core developers are tired of this discussion and wish that it would just "go away", but I truly hope that something good can come out of it, with UT steering away from trying to do too many things differently and those alienating potential contributors.
*noticeable exception being Clickable, which is a really nice way to build release packages, although Click as a package system itself is another case in point.
-
@poVoq I think that all boils down to the fact that mobile OS are lacking developers (compared with desktop Linux) because Android and iOS were more or less closed. Now we have the hardware, but not many are able to play with them. Sadly, this is not something that can be done over night, plus, bringing the device to the latest kernel is not for the faint of heart and not many are able to do it.
-
@andybleaden This worked for me as well. Guess I will have to manually switch back and forth from headphones to Line out until a fix is put out. Thanks!
