Not sure whats going on with PayPal, but the problems appear only when we get sent a amount in a different currency then whats currently on the account. PayPal does not give any email of some sort that there is a new payment, so most of the times we we no idea that a new currency has to be accepted to be able to receive in that currency. I will try to follow up with PayPal, but please try sending it with EUR or USD.
Posts made by mariogrip
RE: PayPal donation returned
RE: Oneplus 3/3T
Could all of you with flashing problems please do the following...
You will need a computer with the
- Boot to bootloader
- Run the command
fastboot format:ext4 cache && fastboot format:ext4 data
- Attempt installation again
It appears the problem is ADB trying to read a file from the data partition, failing, and simply blocking all connections.
Please note this will DELETE all data on the device.
RE: What's this Edge merge anyway?
so in the stable channel OTA 12 there will be no the upgrade to mir1.0 and unity8 from 2017?
edge ( Mir 1.x and Unity8 from 2017) | devel ( Mir 0.24 and Unity8 from 2015) | rc ( Mir 0.24 and Unity8 from 2015) | stable ( Mir 0.24 and Unity8 from 2015)
edge ( something newer) | devel ( Mir 1.x and Unity8 from 2017) | rc ( Mir 0.24 and Unity8 from 2015) | stable ( Mir 0.24 and Unity8 from 2015)
I would say unity8 from 2019, there has been so much work put into it from us after canonical dropped it.
RE: Librem 5 dev-kit
@david-boddie aaand we got some freshly baked images https://ci.ubports.com/job/rootfs/job/rootfs-librem5/
I have not tried them, so may be broken
RE: Librem 5 dev-kit
@david-boddie for the development board we do have most parts that is working on pureos and the images should be even better after an apt update since we got lots of mainline and wayland fixes in since last image was built
but i'll update jenkins now to build the new ones now since should be quick to get going
RE: Librem 5 dev-kit
@david-boddie right now there is no "good" way of installing on the librem5, we have some basic images working on it, but we have not put too much time into it, and we have halted the development on it as purism wont send us final devices until last. Purism has also failed to meet anything they said on their "partnership" blog post we had with them a while back. We really want to have Ubuntu touch running, but at this point it seems like purism don't want us.
We have some images built by our ci server: https://ci.ubports.com/job/rootfs/job/rootfs-librem5/
but this has not been tested in a while so the state of the images are unknown. You can flash this using purism's uuu tool
Read before posting!
This category is only for ongoing ports, any other post will be remove or moved.
How the ports should look like
Title: "Device name (codename)"
Posts here needs to include the current status of the device, sources and how to install the device. Try to structure the post to be easy to get the information. Also add some info on how to help or contribute to improve the device.
Title: "Oneplus one (bacon)"
Port for Oneplus one,
Kernel: link to kernel
Device: link to device configs
Halium: Link to halium-devices manifest
- Wifi: works
How to install
RE: Continuation of rpi effort and how to test
@jezek We have images here that are designed for the pinebook https://ci.ubports.com/job/rootfs/job/rootfs-pinebook/ but please note that these are really early images, so they are not stable at all, and there is some bugs
RE: Continuation of rpi effort and how to test
Also will leave this here: https://github.com/anholt/mesa/wiki/VC4-Performance-Tricks might be an idea to look into. (that's the mesa driver)
Continuation of rpi effort and how to test
So, I have done the "heavy lifting" so far, but there are still some work needed. Like getting wifi and bluetooth to work (I suspect just adding firmware will help, see example for pine: https://gitlab.com/ubports/core/rootfs-builder-debos/blob/master/pine64-common.yaml#L15). On the graphical side of things, there is still a host of bugs using the wayland session, but this will be worked on in parallel with pinephone and librem5, so this is not a raspberry specific issue. In short, when it gets fixed on pine it gets fixed on rpi too
The build "scripts" can be found here: https://gitlab.com/ubports/core/rootfs-builder-debos/blob/master/raspberrypi.yaml please send pr's here to improve the images.
Images will be built daily by the ci, they can be found here: https://ci.ubports.com/job/rootfs/job/rootfs-rpi/. flashing is really easy using etcher (https://www.balena.io/etcher/) to flash the sdcard.
This has been tested on rpi3, but should work on anything newer then 3 (as it needs arm64)
Some bugs that i saw:
- Won't start without keyboard or mouse connected
- Once unity8 has started, you need to reconnect the mouse/keyboard to make it work
- Performance using the opensource mesa drivers is still not "great"
- Needs swap
- A host of wayland session bugs
RE: Running Wayland apps on edge?
If this is an android device, wayland currently will not work on stock edge, as some changes to the android graphic plugin is needed for wayland to work.
I have setup an experimental branch that you can try:
sudo ubports-qa install xenial_-_edge_-_wayland
but yeah, this is highly experimental
Please note that the "startup screen might just be black, but unity8 should come up after some time"
To start any applications you need to set:
RE: Anbox development
So the easiest way to get started is using our crossbuilder tool, https://github.com/ubports/crossbuilder this will setup an lxc container that you can with all the tools to do the cross compiling of the binaries.
To start with, install anbox on you device and make sure it's working before starting, this way we know that it works before you start
First clone https://github.com/ubports/anbox and cd into it.
Then to setup container i do:
Then i just do
crossbuilder shell cd anbox mkdir build-armhf cd build-armhf cmake .. -DCMAKE_BUILD_TYPE=Debug -DENABLE_WAYLAND=OFF -DENABLE_MIR=ON -DENABLE_TOUCH_INPUT=ON make -j10
crossbuilder will bind mount to you current working folder
Then with another shell (thats outside of crossbuilder) i push the binaries from the folder to the phone using adb.
Now you have two options, use upstart or start the binaries manually,
For upstart do:
Then adb shell into you device and replace it with the binary you just make
sudo mount -o rw,remount / sudo mv anbox /usr/bin stop anbox-session sudo stop anbox-container sudo start anbox-container start anbox-session
For raw binary start:
First stop the upstart session
stop anbox-session sudo stop anbox-container
Then to start anbox you need two services: container (root) and session (user)
So you need to open two adb shells since there are blocking
sudo ./anbox container-manager --data-path=/home/phablet/anbox-data --privileged
export ANBOX_NO_SDL_WINDOW_HIT_TEST=1 export ANBOX_NO_DESKTOP_SUBDIR=1 ./anbox session-manager --desktop_file_hint=/usr/share/applications/anbox.desktop --mir-rootless
Please not these where mostly written from memory, so might be a bit rusty
RE: Proposal for a Telegram Stickers Project
One point i want to add, is that we might want to remove the "Ubuntu logo" since for this exact reason we are limited. Things that we want to include yumi on might be approved each time, like if we want to have it on the pinephone for example. We also want to move into debian and other distros, so a removal of the logo would be a good move in my opinion.
Yumi itself can be used by anyone, that was one of the main point when it was made, but i see now adding the ubuntu logo was a mistake.
2 Being a privacy oriented phone, it would be cool a physical switch to turn off the module, and maybe the cameras, microphone. I dont trust very much the module stand-by state.
It will have physical switched for all those
- 3 The display manager should be i3 or lxde (kde or gnome would be f00l(no offence ubports)) and the OS arch or debian. All the always-running apps should be gtk2.
gtk on phones is a bad idea. It's not designed for low end hardware nor is it designed to work on a phone form factor. Why do you want gtk?
Qt has superior performance on embedded, ARM based devices. Also LXDE is moving to LXQT which is qt based.
UBports does not use kde or gnome, we use unity8 that's crafted specifically to work on phones and desktop alike, based on qt.
i3 would be hard to use? no keyboard?
But you can run whatever you want there is debian builds already for it, and i know other project are working on it as well, like arch, plasma mobile, etc.
4 I hope that the pinephone 2 will use a mediatek or qualcomm soc. Not a surprise a battery of 3000 mAh.
It will use the allwinner a64
RE: Issue priorities - basic phones features shouldn't be the first ?
Little the same as i wrote on github https://github.com/ubports/ubuntu-touch/issues/860,
Also please understand, we are a small team with a huge task, we have many moving parts and moving to a newer version of mir and unity8 at the same time is not helping, we are doing our best to make an an awesome operative system. but we are in a really busy period after taking over from canonical, we updated to xenial, we are updating mir and updating unity8 all these are huge since canonical left it all the current version far behind the latest releases, this forces us to make major changes. We are also building Halium and following the evolving of android and newer devices to be able to follow the mobile marked. At halium we are also trying to move our sensor, gps, media and camera system over to an active maintained system instead of maintaining our own. And we are also looking at merging our patched in celluar and pulse with an active maintained one. Once we move things to active maintained systems where we can work together to get to the same goal, we will then get more time to focuses on core functions.
About replacing the browser, this is an huge part for us, we are not able to maintain our own fork of chromium (oxide) that why we are forced to move the browser, this move will in fact give more time to focused on the core functions on the phone.
We are moving to newer version of pretty much every part of the system, this is a major work. Once we have done the major upgrade we will get a lot more time. And in fact we are really close go get to this point, we now are super close to finish all the mir/unity8/libhybris upgrades. And we don't have a big enough team to focus on all the bugs right now as the code may have merge errors to be able to merge with never version and to risk spending lots of time on bugs that might be fixed in newer version. that's why we are upgrading, getting our source aligned with newer sources to then focus on fixing and improving.
In fact most of these bugs comes from the canonical days, they was a much bigger team then we are right now, so we don't work at the same speed.
We are doing our best with the small team we have.
OTA 8 will include new mir and unity8 (and many other updated parts), we hope these have many of these issues fixed, but we have to expect some bugs to be included also since the upgrade is so major.
Thanks for understanding
RE: for device-tarball question
@kuailexs Sorry that it took a little, i had to setup eveything, but Its mostly ready now
Do you have an gitlab account? If so whats your username? That way i can add you to the repo.
I have setup an repo on gitlab where you can push your files, those will then get automatically pushed to our infrastructure and pushed to the system image server.
The format inside this is same as device tarball with, partition images in
partitionsfolder and rootfs files in
Required files are:
partitions / boot.img
partitions / recovery.img
Files should not be compressed, our infrastructure will do this
RE: Morph Browser is exellently trackable
This is defiantly something we should resolve within the browser (at least have an option to block ads and trackers) But the browser is quite new and still is under heavy development, i do expect something like this to be added in newer versions.
Right now using https://open-store.io/app/uadblock.mariogrip blocks most ads and trackers.