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 - Dickon Hood

Pages: [1] 2 3 4
1
I've been off this site since 23rd March (apparently) because I had no idea what the trouble was.

May I suggest amending the error message to at least mention IPv6?  It's pretty hopeless.

2
OESF Announcements / [SOLVED] OESF SSL certificates now expired
« on: April 27, 2020, 06:13:58 am »
Perhaps, whilst you're at it, you could get them to fix your IPv6 problems.

Attempting to access this thing via IPv6 results in a single 'Cannot determine your IP address' string, and nothing else.  I've had to stick the IPv4 address in /etc/hosts just to post this.  It's been like this for well over a month now.

3
Yes, it's utterly insane that we have to use a toy filesystem (which can't even cope with my mp3 collection, due to 'invalid' characters in some of the filenames -- WTF?) on the uSD card.  But it's a batshit decision by Google, and I doubt it's something Planet can fix.

4
Given Planet's track record on timing promises, even in normal conditions, I wouldn't expect to see the firmware updates particularly soon.  Now, it's software, and people can write that from home (I've been home-working doing just that for >15 years now, and thoroughly love it), but it takes some getting used to, and if you haven't got a sensible setup -- desk, office chair with gas pump, two or three monitors, docking station if you've only got a laptop, etc. -- you simply won't be as productive as you would in an office with all of those things.  Given we've all been told to work from home where possible, it's likely Planet's teams are doing just that, possibly sub-optimally.

5
Cosmo Communicator - CoDi / Tap Payment
« on: February 23, 2020, 09:26:46 am »
Nope.  And the weird thing about that is that the NFC is clearly working when the lid is closed: holding a creditcard anywhere near the thing -- such as when in a wallet in the same coat pocket -- causes it to chirp quietly to itself once every few seconds.  I thought I was going mad...

6
The board is running on some very badly configured kit.  Check the timestamps.

7
Cosmo Communicator - General Discussion / Is this the only Cosmo forum?
« on: February 13, 2020, 04:34:02 am »
I'd hope so, because this this is utterly hateful: the date format is much harder to parse than most -- you need to put some effort into it -- and cannot be changed, and whoever ibilio are, they're bloody useless at managing servers (didn't they host Groklaw, back in the day?).  It is currently 0923 in the UK, but the time at the bottom of this page is showing 0930.  Various machines in the cluster serving this forum have various offsets from real time, and one of them has what looks to be an utterly bogus timezone configured.  This isn't rocket science, and it really doesn't give me confidence that things like passwords are being handled correctly.

8
Cosmo Communicator - Android / Flash drive + Cosmo cable + adapter problem
« on: February 10, 2020, 02:51:49 pm »
That's interesting.  I hadn't checked mine.

I'm not entirely sure which cable I've just looked at is -- might well be the Gemini one, rather than the Cosmo -- but it looks to be a power cable only, rather than a proper, full USB3 thing.  There don't appear to be the second set of conductors in the A end, and the C end is missing quite a lot of (what I seem to remember are) data pins.

Try again with a proper USB-C data cable?

9
Cosmo Communicator - General Discussion / Firmware update
« on: February 09, 2020, 03:49:58 pm »
I installed that version when it was first offered over wireless the first time.  It works, and is a marked improvement to the V15 image.

I've not attempted to root the thing, and haven't done anything the average Android user wouldn't do, other than, perhaps, install Wireguard and an ssh client.  And SSHelper.  None of which should have any impact on the thing.

10
Cosmo Communicator - General Discussion / Poor battery life
« on: February 07, 2020, 11:40:21 am »
I removed mine, and it seem to have had some impact, but not a lot.

I'm more worried about the seemingly endless chatting requests for DNS entries for Google's ad and analytics servers, both of which I have blocked at the DNS level via a VPN and Pi-hole.  I'm getting worrying entries every minute or so, which can't be doing the battery any good whatsoever.

11
I'll add mobile networks to banking on the list of things the US is way, way behind the rest of the world on, then...

That's just perverse.

12
Hang on, how does roaming work?  I assume they do actually support foreign users?

13
Quote from: VAMM
It is indeed monumentally stupid. It appears that the only way to get the phone to work right on AT&Ts network is to fool the system into thinking it is a different phone. If you just give them the Cosmo's IMEI, they will say the phone is incompatible.

That's ludicrous.

I can walk into any random mobile phone shop / order off Amazon / eBay / Alibaba / whatnot and buy a handset, then buy a SIM card from any one of the networks by walking into one of their shops / online / over the phone, plug one into the other, and get on with my life.  Which, AIUI, was what the GSMA was aiming for.

I'd complain if I were you, then change networks.  Or are they all this bad?

14
This seems monumentally stupid to me.  The whole *point* of the SIM card -- the Subscriber Identity Module, after all -- was to enable users to pick networks and handsets independently.  You're saying that you can't (reliably) do that in the US?

15
Cosmo Communicator - General Discussion / Poor battery life
« on: February 06, 2020, 09:20:16 am »
When I first got my Cosmo, the right port wouldn't charge it.  Since upgrading both the Android and CoDi firmware, it now does.

Pages: [1] 2 3 4