Messages

1

Cosmo Communicator - Linux / Re: When gemian-buster.thinkglobally.org repository will be available to V3?

« on: May 12, 2021, 09:32:16 am »

Just to say cmst-connman is outside of my scope and so your off playing with dragons again.

I fixed up cmst/connman back on the Gemini, to only find that on the Cosmo we had apparently moved to nm, so now the plan is to fix that up, going forwards I don't want to have to fiddle with every different option, its a one time move to better fit with the plasma desktop hence updating of kscreenlocker shortcuts to work with nm. Given that my test sim has started showing random small amounts of data/month and I've never installed cmst, nm must be randomly attaching when I turn off wifi, even though I'm generally also turning off cellular at the same time.

Bug #9 is the one to follow if you want to track the progress of getting nm up to scratch: https://github.com/gemian/gemian/issues/9

2

Cosmo Communicator - Linux / Re: ALT key not working in v4

« on: May 12, 2021, 09:02:58 am »

I can assure you that I have done nothing to break alt-tab, V4 sets up the keyboard for you at install time and that should be good. So if its not working I must assume that you've done something odd such as restored a backup that messes with the keyboard settings or followed some out of date instructions to self-break the keyboard settings?

Your keyboard settings should be in /etc/default/keyboard (eg XKBLAYOUT=gb)
You should have fn+shift+[b|m] altering your keyboard brightness, alt-tab switching active apps, and other similar shortcuts etc.

3

Cosmo Communicator - Linux / Re: When gemian-buster.thinkglobally.org repository will be available to V3?

« on: May 12, 2021, 04:19:19 am »

Just to clarify it was one of the sponsors-hub 'pre-release' tick-box testers who noticed the calls problem though not till the day after I'd released to planet.

It occurred to me overnight that I might have given the wrong impression of their testing skills. Possibly more to do with my only emailing at the start and end of what ended up being a 17 day preview window, I think the peak was four releases on one of those days as I worked through installer bugs.

4

Cosmo Communicator - Linux / Re: When gemian-buster.thinkglobally.org repository will be available to V3?

« on: May 11, 2021, 08:26:34 am »

We took the decision to rename the repository because any attempts to upgrade ended up in a pickle, so v3 is intentionally a dead end. Best to stick on v3 and wait for v5?, but for the crazy you could rename (s/buster/planet) the line in a few places in your apt sources/pinning files if you want to live off the edge of the map with the dragons.

I think the camera can only work in v4 though haven't tested it as the whole point of the move is to give the same level of HW support as with UBPorts. The breaking change is moving from droid-hal-cosmopda-bin built from a subset of the private sources and installed without lxc containment and so not upgradable neither to itself nor to lxc-android that is built from LineageOS and due to being inside a .img file is upgradable in the future if needed. We did try to put droid-hal back to one from a backup but turned out to be an older one than that in v3 so we just gave up and so we got the one time forced upgrade. As a sweeter for that forced re-install I did the installer work where you can pick the keyboard/timezone at installation.

I do apologise for not testing calls-in, I did test sms-in/out and calls-out, I just assumed if sms-in worked then as calls-out worked so would calls-in. I did offer pre-release testing to four other people though apparently none of them thought to try incoming calls either. I've generally considered the lack of sleep performance would preclude the use as a telephone also the fact that a pocket crash reboot* will drop you out of any chance of calls/sms working until you've logged in again. Its on the list to investigate along with the BT having only ever worked on first boot after fresh v4 install and never again.

Bugs: https://github.com/gemian/gemian/issues
Work prioritisation: https://gemian.thinkglobally.org/sponsor-hub/ (no actual need to be a sponsor despite the name - clearly need more testers)
Chip in: https://github.com/gemian/gemian/wiki/FundingOptions

* I think I was getting about one a month on Gemini when I actually left the house - zero when its sat on the desk all the time in these C19 times.

5

Cosmo Communicator - Linux / Re: Anbox on Cosmo Linux

« on: May 04, 2021, 01:55:22 pm »

mine is a few builds different to yours: 1.8.0_292-8u292-b10-0ubuntu1~20.10-b10

6

Cosmo Communicator - Linux / Re: New Gebian Linux user questions

« on: May 01, 2021, 08:23:01 am »

I have not found a way to keep it set to speaker on reboot yet.

You need to apply this fix to the tail of /etc/pulse/default.pa:
https://github.com/gemian/gemian-debos-recipes/commit/8882e154c7dba6bff458b9a6a0c61a42e0d5f5a0

Note: Only tested after update to v4, ie using lxc-android not droid-hal...

7

Cosmo Communicator - Linux / Re: Anbox on Cosmo Linux

« on: May 01, 2021, 08:19:24 am »

Ok so I've 16G in this machine, so unsurprisingly your suggestion has no impact. Its also perfectly happy building various other android trees.

In my experimenting the 'jack-admin start-server' fails to return to the console so I was running it in the background (&) to get it out of the way, it completes some minutes later with 'Jack server failed to (re)start, try 'jack-diagnose' or see Jack server log' yet there is nothing in the logs beyond the ... Starting js(1.3-a8 '1.3')/sc/ac (3 lines) finishing with a ... Start timer.

The jack-diagnose script (if made executable) reports spurious errors (error: process ID list syntax error - try ps ... indicating that its designed to work against some incompatible with ubuntu version of 'ps') unless the last thing was a kill-server when it reports no errors.

I also tried changing the port numbers in both config files, just in case there is something else using them, unsurprisingly to no avail as there is nothing unusual running on this machine.

8

Cosmo Communicator - Linux / Re: On-device kernel compilation

« on: May 01, 2021, 06:00:38 am »

Sorry I've not looked into the dtc stuff beyond fixing the errors I encounter when trying to get the kernel to build.

9

Cosmo Communicator - Linux / Re: Anbox on Cosmo Linux

« on: April 30, 2021, 06:22:31 pm »

Yea the halium built android images apply a bunch of patches.

Gemian v4 (based on lxc-android - halium 9) now released has your kernel fixes and you can apt install anbox to pull down something that might have a chance of working.

I've still not got your suggested android.img rootfs building though, with your recent fixes it can now build the c++ code but bails on the java code due to the jack-server having a bad day. I tried various suggested fixes to no avail.

I might wait and see how the https://github.com/Anbox-halium/anbox-halium project goes, looks to be getting regular interesting sounding updates and should have better hardware support in the end.

10

Cosmo Communicator - Linux / Re: On-device kernel compilation

« on: April 30, 2021, 05:43:12 pm »

If you check the Gotchas:
 * If the build fails 'scripts/dtc/dtc_overlay: Exec format error' due to wrong cpu arch check your running a kernel dated Dec 2020 or newer (uname -a) and installed the qemu build dependencies (qemu-user-binfmt).

I'd be interested to know if you still need those fixes now you've pulled in a kernel built with this fix: https://github.com/gemian/cosmo-linux-kernel-4.4/commit/fc4253769f854b888b5515b1d316593dbc3d3df9

The date suggested relates to Gemian build server built kernel releases (ie available via apt).

11

Cosmo Communicator - Linux / Re: Anbox on Cosmo Linux

« on: April 27, 2021, 12:26:05 pm »

Thanks for working on this. I've occasionally looked into it in the past but never got it working. The the anbox-halium branches look to be interesting in terms of avoiding the round trips in and out of desktop open-gl and presumably accessing other bits of hardware directly - https://github.com/Anbox-halium

I pulled in your kernel fixes to the packaging branch: https://github.com/gemian/cosmo-linux-kernel-4.4/commit/e4734bcb48084f482caeab46224e8d511eaba59e

I also updated the anbox branch from the upstream and pulled in your iptables-legacy change too.

However I've got stuck with the building of the suggested android-7 image file. On the Debian 10 build server it complains about lacking tools.jar (related to wanting an older version of java). On my desktop which happens to have many versions of java - external/libavc/decoder/arm/ih264d_function_selector.c:67: error: undefined reference to 'ih264d_init_function_ptr_av8' clang++: error: linker command failed with exit code 1 (use -v to see invocation)

I could probably debug them but ideally we'd be using a newer version of android, and given that we already have a full copy of lineage* running in an LXC container to allow us to access the hardware, it seems a bit odd to have to go back to something so old.

* - granted this is pending release by Planet.

12

Cosmo Communicator - Linux / Re: On-device kernel compilation

« on: April 27, 2021, 12:01:08 pm »

We have a branch (packaging) which is now buildable on both a Debian 10 amd64(Desktop) with cross compilation and natively (arm64) on the device (in Gemini days there were two branches for this). Using the Debian configuration files as detailed on the wiki:
https://github.com/gemian/gemian/wiki/KernelCompilation#cosmo

You end up with a regular Debian installable package which gives the advantage of keeping you on the update tracks for upstream improvements. Ideally you'll be making your own kernels to test out new features that everyone wants and so after testing you'll be pushing the fixes up to share with everyone else.

For those that keen on building outside of the Debian packaging system you can review the commands in debian/rules to see what the steps are and pick out the bits you want.

13

Cosmo Communicator - Linux / Additional keyboard layout

« on: March 06, 2020, 02:10:18 pm »

Well... How can I work with only Russian layout enabled? How to type Latin letters?

If your using the gemian layouts and no one changed things since the gemini to break things then they come with two groups, you just press both shift keys to swap groups to quickly change which set of characters are used.

The gemini login screen was changed to allow you to have two drop downs one for the language variant (symbols) and then one for the layout (group) with a test text entry box so you could try it out. This time around Nikita has swapped everything so someone has to do all that work again. You also lose the special keys as they are not supported on letter+modifier key mappings by upstream projects.

I don't have a functioning Cosmo so can't check.

14

Cosmo Communicator - Linux / backlight keyboard

« on: February 28, 2020, 09:28:44 am »

Well it works for me, I'd try the 45 first as that's most noticeable, 40 turns it off...

15

Cosmo Communicator - Linux / backlight keyboard

« on: February 27, 2020, 08:06:59 am »

The wiki has lots of useful info including backlight:
https://github.com/gemian/gemian/wiki/LEDs#cosmo-leds

Its open to all to update and add findings.