@ZeroPointEnergy said in Librem 5 dev-kit:

@trainailleur Good points. Once I figured out how to create an ubuntu-touch image that at least boots I will definitely look at what's there for the PinePhone.

Maybe even for the route towards a bootable image efforts could be shared with pinephoneporting. Which tooling to use to even create an image, etc. @UniSuperBox is there any public repo for how you guys are kicking around the pinephone?

Another relevant resource is probably the way how librem builds and installs their image, since they have to have a way of getting some kind of linux system without android onto the librem 5. Maybe just building that image yourself will already teach you a lot.

@dtarrant I remember the app. Was it this one

http://www.mardy.it/imaginario/

If it was open source and is just unmaintained, then you might be able to find the source code and maybe take over maintainership yourself, or maybe someone else steps up.

Some old stuff is here https://uappexplorer.com/apps?type=application&category=graphics

@openvanchary the patch is right there in the link you gave...

@PINE64 awesome. Will it be possible to watch the video after the fact? And would you take upfront questions here, like: What's the status of the webcam? And, when will you take our money for it

why do we have it on UT and UBports? Resource limits?

Very definitely to limit resource consumption. On a mobile phone you have very different expectations about battery life. I think UT sigstops the process when the app switches to background.

@Flohack said in Trying to help to improve Dekko2:

@guru Very nice! Welcome to the world of clickablers

Haha. Can we get "clickabler" merchandising?

@guru said in Trying to help to improve Dekko2:

How does clickable know while building what is the target device and what is installed on it? Should the device already be connected before start of clickable?

It defaults to building for an armhf device. It assumes UT is installed and will proceed to install the app. Yes, it's easiest if you connect the device via usb first. Make sure you can adb into the device, that's the same way how clickable will communicate with the device

@RoyD said in Porting to BQ Aquaris U2 soon:

Comparing the specs of the U2 with the E5 could help me build a manifest from the device specs

Not really. I don't think ubports or the halium community are able to build the e5 device specific parts themselves. That was bq's job.

If you want halium on u2, you'd have to start from scratch as any other halium port does. And that means finding a lineage os or similar custom android version. With a quick internet search I couldn't find anything. u2 is yamcha? If there is no lineage os then you are looking at a much bigger task than just the halium port.

One thing that I find a bit surprising is that "convergence conversations" are usually of a either/or mindset. I want convergence, but I do not necessarily want it instead of another device/setup that I have now, I want it in addition.

Sometimes I want to use my phone like a traditional smartphone. Sometimes I want to use my laptop, my smart tv, my cloud computer, my tablet, my car infotainment system, my smart watch or my office desktop. I want them to sync and work smoothly together. But, yes, sometimes I want one of these devices to converge into something else. But that doesn't mean I'm gonna get rid of my laptop.

It reminds me a bit of misunderstandings that I had with people when I was rooting for touch displays. They responded with: "I really can't imagine working without a mouse." Uhh, yeah, sure, neither can I! Of course I use a mouse. I also use a touchpad, and keyboard shortcuts. But, yes, I do also use the touchscreen. It doesn't replace any of the other use cases. It is there in addition.

maybe upstart would be better than cron. at least it doesn't require rw partition. this https://wiki.ubuntuusers.de/Baustelle/Ubuntu_Touch/Snippets/#Skalierung-der-Anzeige uses an upstart job to change the scaling. in a similar way, I'm sure you can write any other job