Messages

16

Cosmo Communicator - Android / V22 upgrade taskbar/home screen misbehaviour

« on: July 04, 2020, 06:49:11 am »

Great idea! But I've never done that before. How do I do that?

Magisk Modules are installed in /data/adb/modules/[modulename]. Some modules have a service.sh script there which gets executed on startup. Just install a magisk module and add the two lines to the service.sh file afterwards. (requires root) Since I have installed my exfat module anyways (and it has a service.sh file) I just have added the lines there. (If you want to use the module for this,  it can be found on mygnu.de)

I also replaced the default boot image with a magisk image (@see: https://www.oesf.org/forum/index.php?showtopic=35879) so it boots into rooted android by default (so the script gets executed). Anyways it seems, with the newly rooted boot image, the cosmo is far more stable than with planets rooting method. I have not seen a spontaneous reboot since then. Maybe the official kernel image is outdated and does not contain the kernel modifications for V22.

17

Cosmo Communicator - Android / V22 upgrade taskbar/home screen misbehaviour

« on: July 03, 2020, 08:48:54 am »

Sadly, it didn't survive a reboot and I had to reboot about 8 times before it booted up again so that I could run the commands again. Planet better be fixing this with V23, 'cause this way, it's getting hard to use my Cosmo...

I have just added the two comands

settings put global device_provisioned 1
settings put secure user_setup_complete 1

to a service.sh file of a magisk module, so the commands should get run on every startup (when booting rooted). I am curious to see if the issue happens again with that. Maybe this also is an option for you.

18

Cosmo Communicator - Android / V22 upgrade taskbar/home screen misbehaviour

« on: July 01, 2020, 08:03:47 pm »

See? I knew I couldn't be the only one with this issue! I reported it a few days ago in the V22 is out thread.

But I can't use your solution  ADB won't recognize my phone as Developer Options are inaccessible due to this bug, meaning I can't enable USB Debugging for ADB. And I can't access a root shell either since the Play Store won't install apps anymore, APK's won't install anymore either and Planet's TWRP still isn't working. Do you have any suggestion as to how I can get a root shell?

Someone managed using adb by "brute force":
https://forum.xda-developers.com/showpost.p...;postcount=2706
Unfortunately he did not mention the Android version used. Maybe this is also possible on the Cosmo.

You could also try to install the rooted image from sd card as described by Planet Computers: http://support.planetcom.co.uk/index.php/Linux_for_Cosmo
Afterwards install termux from apk (since Play store does not work): https://f-droid.org/packages/com.termux/ and use the settings commands from above.

19

Cosmo Communicator - Android / V22 upgrade taskbar/home screen misbehaviour

« on: July 01, 2020, 10:50:20 am »

After one of the random reboots with V22,  today this happened again. Maybe switching between rooted/non rooted due to reboot is connected? Solution worked, as before.

20

Cosmo Communicator - Android / V22 upgrade taskbar/home screen misbehaviour

« on: June 25, 2020, 05:26:36 pm »

Two days after upgrading from V19 to V22 my Cosmo suddenly started to behave strange. Most functionality of the taskbar has been missing. The home screen suddenly only had one page. Taks switching became impossible.

The reason has been, that due to a bug in/after OTA update the device has been struck in initial setup mode, where most functions are locked.

This can be solved by running the following commands in a root shell or with adb:
settings put global device_provisioned 1
settings put secure user_setup_complete 1

Initially I thought I had to perform a factory reset, but  then I found the issue on: https://www.xda-developers.com/broken-navig...ota-update/amp/

Mith

21

Cosmo Communicator - Hardware / Rooting the Cosmo Communicator

« on: June 22, 2020, 05:02:23 pm »

Anyone already has V22 stock and magisk boot images? Is there an easy way to extract the stock boot image on the unrooted device? I started with spflash tool, but I am unsure about the partition addresses since my scatter file does not match anymore because of reserving space for Linux.

Thanks!

22

Gemini PDA - Linux / apt update frozen on gemian kernel repo

« on: May 08, 2020, 07:36:41 am »

For me apt update froze while processing the http://gemian.thinkglobally.org/stretch/ gemini-linux-kernel-3.18-stretch repository:

root@gemini:/etc/apt/sources.list.d# apt update
Hit:1 http://security.debian.org/debian-security stretch/updates InRelease
Hit:4 http://ftp.debian.org/debian stretch-backports InRelease                                    
Ign:5 http://cdn-fastly.deb.debian.org/debian stretch InRelease                                  
Hit:6 http://cdn-fastly.deb.debian.org/debian stretch Release
0% [Working]^C            

For me this got solved by installing http-transport-https:

  apt install apt-transport-https

Maybe there is some new https redirect on the server.

Mith

23

Cosmo Communicator - Linux / Default Boot Partition

« on: February 26, 2020, 06:32:16 pm »

After completing the Linux install, how do you set the Cosmo default boot partition to DEBIAN_KDE?

I doubt this is possible. However, it should. Do we have the bootloader source somewhere?

24

Cosmo Communicator - Linux / compiling modules

« on: February 19, 2020, 04:23:30 pm »

I've compiled  with clang. But when loading the module I've got the same error.
Maybe in the future I will try to compile the kernel and modules with gcc.
Thank you so much again.

Have you tried to read the running kernels configuration (cat /proc|config.gz|gunzip>.config) and use this as a base for your kernel configuration? Another possible cause could be compiling from git head. Maybe there have been commits relevant for the module layout after the kernel has been built.

25

Cosmo Communicator - Linux / compiling modules

« on: February 18, 2020, 06:35:00 pm »

gemini@cosmopda:~$ cat /proc/version
Linux version 4.4.146 (nekit@supernova) (Android (4691093 based on r316199) clang version 6.0.2 (https://android.googlesource.com/toolchain/clang 183abd29fc496f55536e7d904e0abae47888fc7f) (https://android.googlesource.com/toolchain/llvm 34361f192e41ed6e4e8f9aca80a4ea7e9856f327) (based on LLVM 6.0.2svn)) #28 SMP PREEMPT Sat Jan 18 22:23:37 GMT 2020
gemini@cosmopda:~$


thank you.

OK, that's it. From your output, the kernel has been compiled using clang. So install a clang compiler as near as possible to clang version 6.0.2. Command line should be similar to the one I have been using for the Android modules: https://www.mygnu.de/2020/02/exfat-support-...o-communicator/

First I also have tried with gcc and got the same exec format error on Android.

Another aproach would be to compile kernel and modules with gcc. For the Gemini this involved a mkbootimg step ( @see: https://github.com/gemian/gemini-keyboard-a...rnelCompilation ) to get a bootable image. I don't know if this also  applies to the Cosmo and how to do it, yet.

26

Cosmo Communicator - Linux / compiling modules

« on: February 18, 2020, 04:47:43 pm »

Hi , I am trying to compile some modules from kernel ( available at github ) . But when I did the command : modprobe " some module" it gave me an error something about exec format. ( because the kernel module compiled  doesn't match the boot kernel ). I've also tried the kernel and kernel-headers  from repository ( using apt-get install )  but in this case the Fn key doesn't work and also no  module was loaded ( wifi also didn't work ). So what is the kernel source repository that matches the kernel boot ?
Note : I've tried all branches from the kernel available at github .
Thank you all.

Just guessing, had no time to try out the Linux image, yet.
Maybe the compiler does not match the one used to compile the kernel. Had the same problem when compiling android modules.

Which compiler did you use? gcc? What is the output of cat /proc/version ?
Just to be sure, what is the version of the kernel packages?

If I am right with my guess, either use the matching compiler, probably clang, or create an own boot image. (boot image and modules compiled with same compiler).

27

Cosmo Communicator - General Discussion / Poor battery life

« on: February 13, 2020, 02:21:48 pm »

What about just disabling the Amoledison app. Should solve the problem and it is not useful anyways.

28

Cosmo Communicator - General Discussion / Scam?

« on: February 08, 2020, 07:11:03 am »

hello@planetcom.co.uk has always gotten a fast response for me.

An update. I have been issued automatic refund by PayPal as PC did not respond to my dispute within prescribed time. Now I will be exporing other sources for the vary same cable including eBay.

I don't think there is any other source for the HDMI adapter.

29

Cosmo Communicator - Android / Broken settings search

« on: February 07, 2020, 01:52:00 pm »

I can't search my android settings on my Cosmo?
Whatever I search for yields no search results.
Does anyone else have this problem?

Yes, kill the settings app, i.e. from task switcher screen, long press to the app card then press the cross in the right upper corner. Afterwards the search will work. Already opened a bug with Panet Computers bug report sheet for this.

Unfortunately the reported bugs are not trackable, one not even gets a confirmation mail, so we can just wait what happens. Would be better if they used some real real bug tracker, i.e. bugzilla, where one can discuss the bugs and see if an issue already has been reported...

Thanks--after restart/shutdown the settings search is broken again for me--how about for you?

Right, it is exactly this way.

30

Cosmo Communicator - Android / Broken settings search

« on: February 07, 2020, 08:22:08 am »

I can't search my android settings on my Cosmo?
Whatever I search for yields no search results.
Does anyone else have this problem?

Yes, kill the settings app, i.e. from task switcher screen, long press to the app card then press the cross in the right upper corner. Afterwards the search will work. Already opened a bug with Panet Computers bug report sheet for this.

Unfortunately the reported bugs are not trackable, one not even gets a confirmation mail, so we can just wait what happens. Would be better if they used some real real bug tracker, i.e. bugzilla, where one can discuss the bugs and see if an issue already has been reported...