Did you forget some instructions in this post?
Posts made by UniSuperBox
RE: Calendar Synchro with gmail
If you're receiving this error, please try the troubleshooting and logging steps mentioned by mardy here: https://github.com/ubports/ubuntu-touch/issues/1202#issuecomment-572565001
@GizmoChicken, I see, I came off too direct in my message. It's the German heritage, after all.
I'm not trying to say that you shouldn't make suggestions, but rather I'm responding to that single suggestion, saying it may not work out, and giving reasons for why. It's that position that I'm coming from, and only because Pine64 operates so differently from most organizations.
I keep the "if you want it, you build it" motto because, quite frankly, it's true. Maybe someone will make a dual-boot option, maybe someone will make an Android option... until those images are out, we can't promise anything. Making those promises and not delivering on them would make people upset. Meeting suggestions with silence will make people upset. I see now that responding to those suggestions will make people upset. There's no winning.
It is a position of frustration. Frustration that we know these things would make it more likely for your average Joe to buy the phone, but knowing that we can only promise what the device is right now, not what it could be if only we did something different. So maybe it isn't right for the average Joe, but it's right for us. And we'll keep making it better.
I'd rather tell you why things aren't realistic, even if it deflates your excitement, so you know what you're getting into with your purchase.
Also this is the UBports Forum, there is also the Pine64 forum if you'd like to stay up-to-date on all things PinePhone and discuss your suggestions. You might get a more useful response there: https://forum.pine64.org/
If you'd prefer I not respond, I guess that's okay. Sorry for being a bother.
@mirroronthewall, the main problem is the price. For what you're paying for a PinePhone, you can get a far better Android phone (new or used). If you want to run Android, it's just not a good purchase.
For example, a Pixel 1 which can run the newest LineageOS can be had for under $100 (shipping included) in the US. The PinePhone is not a compelling offer as an Android phone with those numbers.
You aren't seriously suggesting that Pine64 relies on "the community" for every aspect of the boot process, are you?
[...] in a post asking about a whether @PINE64 would be providing a script for installing to eMMC, @PINE64 stated: "I'll put together a 'rough' SD->eMMC image in time for when phones are delivered later this month." So @PINE64 seems to have more control over what will ship on the PinePhone than you seem realize.
I'm not suggesting, I'm telling. The Pine64 Store makes hardware, we make software. We are a community. Our community includes PostMarketOS, the KDE Plasma Mobile developers, Manjaro, LuneOS, SailfishOS's community porters, Nemo Mobile... the list goes on and on. The Store itself is a member of our community.
We're on the same side here, man. The @PINE64 account is a collaboration among four long-standing Pine64 community members: TL, Lukasz, 'Gamiee', and 'fire219'. Any one of them could be putting the script together. That does make the "I'm" a bit confusing in this case. We can do better in the future.
I've been involved in the PinePhone project from the first time that Lukasz joined our IRC and asked if we wanted in. Yes, in a group with 2000 people, he implicitly announced the PinePhone before we even knew its specs. From the beginning, it's been clear: The Pine64 Store's staff members are making the hardware they can manage, with the features we request, at a price they believe is fair. They do not hire software engineers.
The Store has, however, allocated no-cost hardware to people that we've requested to receive it. Marius, NotKit, and I have received each revision of the PinePhone hardware. We're able to grow that with the Braveheart batch. It's a (capitalist/existential) win for the Pine64 Store, their hardware is far less expensive than our paid developers' salaries. It's a win for us (the community), we get made-for-us hardware.
Because of this, you are indeed requesting that we create a dual-boot option, not that they create a dual-boot option. You are requesting that we create an Android image.
The Pine64 Store has Veto Power in our community, they need to make the numbers work. I'm telling you now, though, the numbers don't work if they hire developers. Napkin math can tell me that.
RE: Crossbuilder - mk-build-deps
The real error is here:
Removing address-book-app-cross-build-deps:armhf because I can't find dh-translations:armhf
This means that the
dh-translationspackage doesn't exist for
armhf, and it has not specified how it should be installed for cross-building situations.
Looking at the dh-translations package in xenial on the package tracker, it only has a package available for the
allarchitecture. This means that it can run on any architecture.
You can fix this error, therefore, by specifying the architecture you'd like to install in the
dh-translations, under the
Build-Depends:heading. Then try building again.
@AppLee, these comparisons are a little less than useful because not many people have these devices in their hands and not all details about the experience on either is correct. Also we don't need to feed the "us vs. them" mentality, one company getting theirs does not mean that the other company can't.
RE: I'm not sure if messaging is working properly
Sending and receiving MMS is indeed quite broken -- there are a raft of relevant issues at https://github.com/ubports/ubuntu-touch/issues?utf8=✓&q=is%3Aissue+is%3Aopen+mms. It's one of those things that I keep getting pulled away from, and don't make much progress on while I'm working on it.
RE: IRC bridging down since days
I'm not sure we'd like to out-source the bridge's hosting, but I would really love some help with managing it... We need to move all of our Matrix bridges within the next few weeks, and I've seen Matterbridge used successfully in the Pine64 community... the only people who complain are on Matrix.
Help us with the Sony Xperia X
I'm sorry to say that the maintainer for the Sony Xperia X (F5121) port, Alfred, has reached a critical point. He needs to stop his current volunteer positions. That includes his maintainership of the Xperia X port.
Many of you know Alfred. He's been one of the most important drivers of Halium 7.1 for well over a year. Working on the Xperia X port, he's found and fixed a great number of issues. His first ever was fixing the mount of
odmpartitions under Halium 7.1 by pulling in some upstream changes. He's gone on to propose or merge 24 changes to Halium and 25 changes to Ubuntu Touch... in addition to all of his work on the Xperia X-specific repositories.
He's ported multiple apps from Sailfish to Ubuntu Touch, you can find them all on his OpenStore profile
Remember when the MX4 wasn't able to boot edge, and it seemed no one would figure it out? Alfred figured it out with this PR.
Basically, what I'm saying is... He's a cool guy. If you have a development position open in Vienna, accept remote work, or you have a unicorn position working on Ubuntu Touch available, you need to stop reading this and send him to your HR manager.
What he really asked me to write this post for, though, was to call for maintainers for the Xperia X port. The port is close to completion, and relied on by a few in the community, but needs someone to take over.
Now, before you say "I can't do that, I'm not a developer," remember: I wasn't a developer three years ago either. Porting Ubuntu Touch sounds hard - it is hard - but most of the work for either a seasoned developer or a newbie is trying things until they work. Don't let your perceived inexperience stop you.
Alfred is minimally available to help you out, and of course the rest of the community is still here too. If you're interested and have a device, you can find the Halium information for the device at halium/projectmanagement#98, and you can find help via the getting community help section of the UBports Documentation. You can start whenever you like, message us whenever you like, or reply here if you're interested.
Thank you for your time.
On this (US) Thanksgiving...
Thank you, everyone. Thank you for being here, for reading this, for helping us create Ubuntu Touch, and especially for helping others when it breaks. I know that sometimes it seems like the requests for help never end or that people go off into the ether after their threads are solved... but I've watched many stick around, turn around, and help others. It's all thanks to you.
I'd like to open the floor... if you've had anyone that helped you while you were getting started, and you're still here, give them a ping to show them your thanks!
I'd personally like to thank @Flohack and NotKit (who isn't on the forum, bummer!) for greeting me back in September of 2016 and helping me create the ultimately failed Nexus 5X port. Even if my original goals weren't reached, I've had three years of fun and met so many amazing people thanks to your level-headed approach to newcomers. Also, of course I need to thank @mariogrip for the opportunity to dedicate my time to the project.
How about you?