Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - peter

Pages: [1] 2
Cosmo Communicator - Linux / Re: protonvpn-cli v2.2.4 crashes Debian-KDE
« on: December 24, 2020, 01:34:17 am »
So, I finally resolved the issue by reverting to the very first community cli app, now deprecated.  It's missing some of the features of later releases, notably the killswitch, but other than that I have no complaints. I also discovered that I needed to use a custom DNS server, because the tool overwrites resolv.conf

I realize the short answer is, "If you don't understand what you're doing, don't do it."  That said, I don't know where to start looking for answers. 

I appreciate the automation your solution provides, but I couldn't get it to work for me.  Instead I've been tweaking individual items -- many thanks for the mtrack relative positioning fix!!!

What I'm struggling with now is creating a mount point for the microSD card.  I'd like to access the files I've placed on it from Android.  Is this even possible, or would I have to create a new partition on it to access it from Gemian?

Running "fdisk -l" only shows the partitions on the mmc block device, and the microSD card is also invisible to GParted.  I didn't recognize any unmounted devices when I searched dmesg for "sd."

So, is it even possible to mount the file system on the microSD card created under Android?  And where can I learn how to do it if it is?

Thanks in advance for any help or advice you share!

- peter

Cosmo Communicator - Linux / Re: protonvpn-cli v2.2.4 crashes Debian-KDE
« on: November 28, 2020, 04:44:11 pm »
Thank you, Varti!

I'll do the same with my Gemian which does work, and then compare the two outputs.  That may give a non-techie like myself a little more to work with.

- peter

Cosmo Communicator - Linux / Re: protonvpn-cli v2.2.4 crashes Debian-KDE
« on: November 28, 2020, 09:36:08 am »
Watching the screen closely, an error message about ipv6tables appears right before the system crashed.

Cosmo Communicator - Linux / protonvpn-cli v2.2.4 crashes Debian-KDE
« on: November 27, 2020, 02:41:22 pm »
I hope someone here can help me.  I can follow instructions and use the command line, but I'm not a coder. 

My Gemini runs the (now obsolete) protonvpn-cli v2.2.4 without issue.

I was able to install, init, and configure it on my Cosmo but every time I try to connect, the entire system crashes and reboots.

I submitted a bug report to ProtonVPN and they looked at the logs from ovpn and protonvpn-cli but didn't see anything obviously there.  They don't provide official support for aarch64 devices, so I'm stuck with trying to figure this out on my own.

Can anyone give me a clue where to start poking?

Cosmo Communicator - Linux / Vivaldi Snapshots for Debian ARM64
« on: November 22, 2020, 09:55:35 am »
Although Vivaldi does not offer official support for ARM architecture, they do provide snapshots for DEB ARM64 builds.  You'll have to check for new posts on their blog here and then manually download and install.  The most recent snapshot as of 2020/11/22 was posted on Nov 19.

Two features on Gemian KDE that make this an essential for me are the ability to set default zoom so pages are legible, and sync.  (These are not unique to Vivaldi.)  It would be wonderful to see Vivaldi provide stable builds for the repository, but I'm just grateful to have the snapshots.


-Cannot add new user so the device is very insecure

One of the first things I did after installing v3 was add a new user.

Then I changed the password of the default user "cosmo" (although I'll probably just delete that account once I get CoDi set up on my new user account).

Cosmo Communicator - Hardware / Rooting the Cosmo Communicator
« on: December 14, 2019, 06:41:32 pm »
Quote from: ZimbiX
Edit: Did you retry it? Maybe the download failed somehow. And maybe there's logs somewhere - adb logcat while you do it?

After much faffing about, I did a factory restore.  Following through the steps, I now have root!

Cosmo Communicator - Hardware / Rooting the Cosmo Communicator
« on: November 25, 2019, 12:21:18 pm »
Quote from: ZimbiX
I've attached the scatterfile for anyone else interested in playing around

So, here's a question.  Would it be possible to manually tweak the Cosmo scatter file by comparing it to a Gem file and use the Debian .img provided by Planet for the Gem to set up a dual boot Cosmo? Or is that Debian .img too heavily customized for the Gem to work on our new devices?

I'd just go ahead and try it myself, but I still haven't wrangled Magisk Manager successfully.  I'm aiming to do that so I can use Titanium Backup before moving on to further experiments...

Cosmo Communicator - Hardware / Rooting the Cosmo Communicator
« on: November 22, 2019, 12:06:41 am »
Quote from: v3ritas
peter: Yes, if you have Magisk then you're rooted. If you have any apps that use root you can go ahead & give them a try, or if you already have you can check what has rights in Magisk Manager > Superuser.

I'm getting it flashed now, as soon as my Cosmo finishes charging.

EDIT: I forgot, since we're just flashing the modified boot image, Magisk Manager needs to be installed separately. You can download it from the XDA thread here.

Thanks for your reply, v3ritas.  Unfortunately, what I'm seeing on my Cosmo doesn't match the descriptions I'm reading about.  Magisk Manager was pre-installed.  Even after unlocking the bootloader, flashing the modified .img, and updating Magisk and MM,  I'm left with the following:

 [ Invalid Attachment ]

When I hit Ok, I get a small pop-up saying "Setup failed."  I couldn't find anywhere to toggle superuser permissions.  The info I've read at xda so far seems to assume that the additional setup has been completed successfully.

I'd be grateful for any tips!  Tomorrow when my brains are fresh, I'll try un- and then re-installing, but I'd really rather not.

Cosmo Communicator - Android / Well, I'm bloody annoyed
« on: November 21, 2019, 12:35:49 pm »
Quote from: TallTim
Well, the bloody android "software buttons" insist on being on the right-hand side orientation, and not even NovaLauncher will be able to change that, as far as I can tell.

Also, why the hell the keyboard backlight doesn't stay on when I'd love it to is something else I'd love to know how to change.

The solution for the Android navigation buttons is to be found in Settings.  The second item, right below "Network & internet" is "Cosmo Settings."  There you can choose to move navigation bar to the left side, or hide it entirely.  I've gone with the latter option, since the Fn key + A or D provide "view all" or "desktop" respectively, while Esc functions like the back arrow.

The keyboard backlight can be controlled by Fn + Shift + B (or N) -- basically the same control as for screen brightness, with the Shift modifier for the keyboard.

I'm afraid I don't know any ways around your other annoyances.

Cosmo Communicator - Hardware / Rooting the Cosmo Communicator
« on: November 21, 2019, 10:56:42 am »
Quote from: ZimbiX
Ok, I've extracted the boot image from the partition called 'boot' (using WwR on my full device backup), and patched it in Magisk Manager on the Cosmo. Here are the original and Magisk'd images:


Flashing the Magisk'd image (with Sp Flash Tool v5.1916 using the scatterfile I uploaded), I'm unfortunately seeing this message on top of the splash screen:

Bad State

Your device has failed verification and may not
work properly.
Please download boot image with correct signature
or disable verified boot.
Your device will reboot in 5 seconds.

Flashing the original boot image back at least gets the Cosmo working again.

I'm terribly late for bed, so sadly I'll have to wait until the weekend to continue. We're so close now!

I'm guessing this error is where the bootloader unlocking comes in - @v3ritas: your turn!

Last night I had success unlocking the bootloader using adb and fastboot per the instructions here:

This morning I installed the boot-magisk.img file using fastboot starting at step 12 of Method 2 here:

Successfully booted, and Magisk is now installed, so I've got root?  Maybe?  I've always used SuperSU, so I need to learn how Magisk works.

Cosmo Communicator - General Discussion / Cosmo Screen Protectors?
« on: November 17, 2019, 02:58:58 am »
Quote from: jakfish
Anybody seen any for sale? Or is the Cosmo screen the same size as the Gemini's?


My Cosmo arrived a few days ago, and I intend to buy the same screen protector I have on my Gemini.  As others have noted, the clamshell design means the screen doesn't need protection.  

The selling point for me is that I found a screen protector which de-polarizes the screen.  I have polarized sunglasses, and without this add-on, the screen is only visible when in portrait orientation.  Hardly ideal for using it outdoors.

I bought the "upscreen Reflection Shield Matte Screen Protector for Planet Computers" from Amazon.

Gemini PDA - Linux / Touchscreen as touchpad - relative mouse input
« on: June 17, 2019, 04:35:15 pm »
Quote from: peter
The "Easy Mode" fix worked perfectly for me with TP2, but I cannot get it to work with TP3.  (I haven't tried building from source yet.)  Can anyone confirm if this works with the latest Gemian image?


Never mind.  I feel pretty stupid, but when I went to remove mtrack prior to building from source, I discovered that it wasn't installed.  sudo apt install fixed the PEBCAK.

Gemini PDA - Linux / Touchscreen as touchpad - relative mouse input
« on: June 14, 2019, 02:31:08 am »
The "Easy Mode" fix worked perfectly for me with TP2, but I cannot get it to work with TP3.  (I haven't tried building from source yet.)  Can anyone confirm if this works with the latest Gemian image?


Pages: [1] 2