10-30-2020, 02:53 AM
(10-22-2020, 01:57 PM)andybleaden@gmail.com Wrote:(10-22-2020, 10:04 AM)peperjohnny Wrote:all really helpful, will try all suggestions when I have a mo and happy to help report issues if it helps you all(10-22-2020, 09:54 AM)andybleaden@gmail.com Wrote: I was wondering how the best way would be to update any of the changes you make upstream?You may get some of the updates with a
Also quick question - I am really enjoying using this. Feels good and promising after a few days
Few issues (as we know BT/Keyboard etc) BUT
If I wanted to stick this on the EMMC - would I do this using jumpdrive do you think? (all my own risk etc etc )
Code:
Code:zypper update
Jumpdrive should do fine. The current version doesn't display anything on the tab, but it should be visible on your PC.
Have had a try at compiling this myself from scratch and not sure I am able to.
I use Ubuntu on my desktop and was coming up with all sorts of errors as this is an Arch build I take it. Also tried on my Pinebook pro (Manjaro ) but again similar errors.
So questions:
Should it be possible to do on an Ubuntu pc? ( I have used it for long enough to have built drivers via the command line before using make etc)
Should it be easier on the Manjaro machine
If so I am happy to build a weekly build and host (different Alphas) so we can keep this moving. I am afraid I am not so good at squashing bugs but if I can compile and build an image and then back that up as an .img I am more than willing to do so to ease the burden.
Why?? Because out of the builds I have used so far on the Pinetab this is the nicest - even as it is better for me to use and more enjoyable as it is even with no keyboard (physical) or Bluetooth (pity)
Hopefully not treading on anyones toes but happy to muck in and help if I can