draft0 - a shared blog by just some people

Go To Navigation
Show/Hide Navigation

Entries tagged 'cat:Computer'

F(x)tex Pro¹ X

First of all: Look at the title. That's how the name of this device is spelled. I've never, and probably will never, be able to spell that correctly without looking it up.

I've contributed to the crowdfunding campagne in 2020. Various pandamic-related issues, a partly re-design, Chinese lock-down delays, devious shipping-issues and, during the last few years, suspected additional, unexplaned issues caused the delivery date to be postponed uncounted times. More than three years later, I've received my Pro¹ X arrived. That means that I guessed right about the makers not being the worst scum of the earth because the ran off with the money without sendind out the devices that we knew had already been produced. I don't know how this scam should have worked unless they sold the devices again to other people. But that was the general tone to which the comments on Indiegogo had goaded each other over the years.

I wanted a keyboard phone for years. I've had My experience with the Planet Computers devices, which some see as the competition. I've had more hopes for the Pro¹ X being the device I was whishing, searching and waiting for becasue it's keyboard is closer to those of the later slide-out qwerty smartphones, like Nokias N900 and because the Pro¹ X's predecessor, the Pro 1, has been reviewd positively by people with the same preferences as me.

So, the phone finally arrived. And, it didn't work. The battery hasn't been charged in years. It didn't charge. It did nothing electronic. But luckily some other campagne contributor has figured out a way to persuade the phone to charge. Interesting that they decided to send out the devices without knowing how the receipients could use them. Of course, the battery's capacity isn't what it was advertised as. In airplane mode with the display turned off and no app running the battery lasts for just over 24 hours. When used, the battery gets drained respectively quickly. But it works. Enough for a few sentences about my first experience.

The keyboard is not the theoretical ideal my brain has developed in the last 10 years. But I don't think that ideal exists. There probably are keys with a nicer preassure point and a click that feels nicer and is even more reliable. There have been in 2O02. But I didn't honestly expect that in a sub-1000-€ phone. The slide-lout mechanism is as snappy and firm as I've seen it described by users od the previous F(x)tec phone. I hope it lasts at least a few hundret times as long as the one on the Astro Slide.

The camera is fine. Much better than the alibi camera of the Titan Pocket that I'm currently using as my main phone. As it happens, I the week after I received the phone I stayed in the same hotel I was in when I tried out the Astro Slide. So I was able to make the same pointless test photos that I've posted in the Anstro Slide entry back then. (See below.) Okay resolution, mediocre sensore, unreliable auto white balance, usable but not enjoyable under artificial light (of normal brightness).

The screen is nice, which is the absolute minimum one expects in the cheapest of phones nowadays. It's bright enough, has a higher resolution than I need, has noticable colour-shift when viewed at an extreme angle. One edge is rounded, which is a first in my personal phone, but not really something I'll expect to use. It's more than fine. I don't need a display as great as what's common nowadays.

It's the best phone I had in my hands in years. The best for my preferences. If only the battery hadn't been killed by it's years-long storage period, the software would be the only thing I'd have to concern myself with in order to make this my primary phone. The pre-installed Android is very very Google-y. Not to my taste anymore. It works well, as one would expect. Not as buggy as with the Astro Slide and previous Planet Computers' Mediathek-based PDAs. Once I've installed LineageOS and replaced the battery, this may become my favourite smartphone ever. It might finally be the one to beat the Nokia 9300 for practical reasons.

File Attachments (4 files)
Comment via email
SBWG 0.12.8

I've recently published a new version of SBWG, my web site generating bash script. The time that I'm able to allocate to working on SBWG fluctuated a lot in the last year and when I do work on it, I often just feel like doing one type of thing. So, when that is starting a new feature, all the other types of tasks can take on a pile that takes months to resolve. But eventually I managed to test and stabilise the features that I've added and changed, edited the README file and tried out the new version with real web sites. Well, testing could be more professionel, but it's okay for a hobby project, I think.

It's been well over a year since I wrote a blog entry about what's new in SBWG. This entry goes through the main new things since version 0.11.1.

A big new thing, at least from the view of the author/me, is that certain options where that makes sense now support multiple arguments. For example if you've edited three entries and want to re-generate just those three, you don't have to run the script three times but rather define the entries like this: sbwg -e ENTRYNAME_1 ENTRYNAME_2 ENTRYNAME_3. The same goes for pages, tagpages, entry attachments and galleries. This doesn't just make it easier and quicker to generate just some changed pieces of content. It also allows the usage of shell globbing (like *, ? and […]) and brace expansion ({…}). For example you can now regenerate all entries that are stored in one subdirectory or all entries whose names start with a vertain string of characters. Another practicle use case is to add external entries and/or to the site that are not stored in the respective directories in the web site's input directory. Using option -E/-P on the contents of an entire directory creates HTML files in the web site's output directory that look like any other of the web site's pages, but without integrating them in the structure of categories and other tags.

There is now a way to create a custom menu in the navigation bar without writing any code in the settings file of a web site. By using the new 'menu:' tag type in the header of a page or entry source file, the page or entry will get added to the menu. This allows for a list of pages you want to link to from the site's navbar, or a nested tree of interesting blog entries. The tag can be used similarly to the 'topic:' tag with the main difference that it doesn't add the entry or page to a list of entries with that topic, but rather directly in the navigation bar. In the default style set that is a drop down menu like the list of categories, authors, languages and topics. But it is just an unordered list, so it can be styled like any web site menu.

The default style set has changed a bit over the year. It basically looks the same but it's a bit cleaner now and is split into more file more logically. It will become even cleaner in the future though. It now also makes use of the new possibility to present the list of categories in the navigation bar in the form of a tag cloud. Audio attachments are better to look at now, especially when there are several audio files attached to an entry. Image attachments are can now be previewed in a modal without loading the (large) original file and without leaving the page. This almost gallery-like display is about as far as I'd like to go without starting to use JavaScript in the default styleset. Some parts of a web site generated with SBWG are now collapsible/expandable. The parts with this new feature are: entry attachments, entire entries on tagpages, entire entries on their own pages, the custom menu, the category list, topic list, language list and author list in the navbar and the entire navbar. By default all of those things are extanded upon page lead and collapsible by clicking/tapping on their titles. But you can add a setting in your settings file for each of those types of things to be collapsed upon page load and expandable by cliking/tapping on them.

Another thing that behaves similarly is content warnings. Hiding the content of an entry, or parts of it, could always be done by hand, e.g. by adding a <details> and <summary> tag pair to the body of the entry. But it is now easily possible by adding a warn: tag to the header of an entry. For example adding warn:This entry contains spoilers. to an entry header results in the entire content being hidden behind a collapsed <details> tag. Initially visible is only the summary "This entry contains spoilers. (click to open)". The default style set makes this warning line very visible but dunking it into a strong red. If the entry has attachments, those will be collapsed and their title marked in red, too. Both the entry content and its attachments will be collapsed by default if the entry has a warn: tag, independently of what your settings for those parts is in the settins file.

New special tagpages: If there are entries that have a language tag and others don't have one, 'nolang.html' will be created that lists all entries that don't have a language tags. Similarly, if at least one entry on the blog has an author tag, but other entries don't, 'noauthor.html' is created and linked to from the navigation bar.

RSS feeds are now created for every tagpage. That means visitors can now subscribe to individual topics or categories or authors or languages. It also means a longer generation time for a complete regeneration process. But permanent caching reduces that to an acceptable amount. Other feed formats are still not created because I reckon that writing those will be particularly fun and satisfying. So I want to get to that when more of the less interesting todo bullet points are done.

Many small changes make web sites with different structures than mine cleaner. Empty directories or menu entries aren't created. There are new hooks for the various different new functions and loops which a user might want to hook into. Various changes around the default language being used for RSS feeds and HTML documents in order to abide by the standards. Many bugs around all sorts of things have been fixed. The logging option works pretty reliable now. It may still be completely removed one day because it's a large chunk in the code, makes the script slower when enabled and can now be entirely replaced by redirecting output from the script on the shell level. The new flags 'hideinfeeds', 'noshow', 'nogal', 'noatts' and 'noheader' control how and where entries are presented and which parts are visible. See the README for descriptions of those flags.

Reading these update blog posts shouldn't be seen as a replacement for reading the CHANGELOG file. If you have a SBWG web site and consider updating SBWG, at least check the CHANGELOG for lines marked with ! since your current version. That makes it much much less likely that you miss something that you should change upon updating SBWG. I mean, I don't think anybody except me uses any version of SBWG. But I've always approached this project working as if it would be used by others in order to produce something that is practically usable without reading and understanding the codebase first.

The list of things that I'd like to do with SBWG is still long and includes heavy changes on how content is placed in the website's input directory. I reckon that it would take me something like 10 - 16 years to get there is I would continue advancing through the todo list at the pace at which I have in the last year. But if I would loose interest at any point along this path, I could feel okay for at least have gotton as far as testing and publishing version 0.12.8 because it's getting closer to looking how I want it to look in regards to the results it produces.

Comment via email

As a child I used to play with old PCs, take them apart, assemble different parts to new PCs, etc. One day when I was 12 I was carrying a 486 Desktop PC to a friend's house, who lived in a different part of the town. On my way there a man stopped me and asked me if I'm interested in computers. He told me he has lots of computers and computer parts at home and I could look at them, pick anything I wanted and take it home to keep. I just had to come home with him and I'd get all the computer parts I wanted. Sadly I couldn't, because my freidn was waiting for me and expected me to bring the 486. So the man gave me his phone number and told me to definitely call because he would soon have to through away good comuter parts if I wouldn't take them.

Back at home I told my mother about the man. For some reason she thought that it was a strange thing to stop a child in the street for and that I shouldn't call him. I replied "He's liek 80 or 90 or something and he said he has to throw the stuff away if I don't take it." I'm not entirely sure whether it was more the age esitmation or my fear of good tech getting thrown away that let her give him a chance to explain himself. So, I called him, took a train to his house and you may guess what happened there, or continue reading, or both.

He lead me to his basement. It was huge. It seemed larger than the already large house. And every single room of it, including the hall in the center, was filled with PCBs, monitors, PCs, racks, more PCBs and cards, software packages (those thick ring binders with manual, diskettes and sometimes printed source code or other notes ticked in an even thicker cardboard box), ICs and other small parts in transparent boxes, empty boards and all the chemicals needed to make your own PCBs, some unfinished projects, home-grown microcomouters, printers, cables, and so on. A retro computer fan's paradise! He was in my home town because he visited a medical specialist. I'm guessing that he knew or suspected that he didn't have much time to get his hobby stuff into the hands of somebody who'd appreciate it. The latter was certainly his goal and did appreciate the tech, which seemed to make him very happy. But I only realised many years later how much more there would have been to appreciate. Back then I wasn't interested in ISA memory extension cards. They were slow and small compared to even SIMM modules. I didn't care for his software collection at all. And I didn't see what I couldn't have done with a custom build computer for which no software existed except what you write yourself. I had no use for his chemical laboratory, hard disks with less than 100 MB of space or electronic parts like logic gates. An 8086 PC was just a worthless piece of too slow hardware to get any fun out of it. I used an MFM drive solely to open it up and take it apart to see how they built these things.

Recently I was thinking, that old man met me too early. My interest in computers was not developed enough at the time. But he did die soon after I visited his house. So for getting some of his computer stuff to somebody who'll at least do something with it before it gets thrown out it was just the right time. I didn't know him, just met him once after his suspicious chat-up. But his wife actually thanked me after he had died. So maybe I didn't come across as greedy or too selfish.

Comment via email
My Further Experience With (Trying To) Use Astro Slide As My Main Phone
This entry is referencing the entry 'Planet Computers' Astro Slide'.

After having owened and used both previous PDAs by Planet Computers (the Gemini PDA and the Cosmo Communicator), I partly knew what to expect from their new modal, the Astro Slide. I knew it wouldn't be a robust, top-notch state-of-the-art smartphone. Planet Computers makes devices for a pretty small niche and needs to sell these devices for a reasonable price despite their low quantity. After having used it as my main phone, I've come to the comclusion that there are reasosn to be disappointed by the outcome of the device anyway.

I've written about my initial impressions of the device. This entry just adds what further experiences I made while using the device as my main phone for ~42 days. tl;dr: I'm still disappointed.

The build quality is relatively low. But I underestimated and/or misremembered how annoying those buttons with no pressure point whatsoever are. Thy aren't even protuding, nor do they have a different color or texture from their surrounding. That means every times I want to turn on the screen of the phone without opening it, I have to either stumble around the edge of the device with my finger for a while, or I need to have a close-up look at the side of the device to locate the button, then fumble around with my finger for just a little while. That turns of the touch-screen. But unlocking it by using the touch-screen doesn't always work. Sometimes the touch-screen just doesn't seem to be in the mood to respiond to being touched in certain places. I also forgot how annoying it is to have a phone without working adaptive sc reen brightness. I have to turn of the brightness way up, above a sensible poiunt, to make sure it's readable in sun-light. Sometimes, adaptive screen brightness just turns it to 0 for a while, which effectively means it turns off the screen. I guess there's a reason why automatic screen brightness is turned off by default.

The screen is okay, but not very bright, hardly readable in direct sunlight. Colors aren't very accurate. And sometimes contrast and colors shift as if some filtwer was applied, for no reason. The speakers are small and not very loud, lack low frequencies completely (no bass). The headphone output is prone to CPU noise while the screen is turned on. The fingerprint reader is so unreliable it's best treated as if it didn't exist. It's useless. The sliding mechanism feels surprisingly sturdy. I didn't break it yet. But I'm sure something will break or come apart soon, as it was the case with my previous Planet Computer PDAs. The software isn't much better. Ecven though there are security updates available and a notification makes sure to permanently inform me of that fact, no updates can be loaded. The OTA update is fundamentally broken. Apparently Planet Computers didn't think it would be a necessary feature to be able to update Android!

I don't know if it's the Mediatek chipset that the device uses (Maybe Android support for that chipset really is that bad.) but using Android on the Astro Slide is just as buggy on the Astro Slide as it was on previous Planet Computers PDAs. Some apps aren't available for the platform. After every time Android boots some internal app whose function isn't clear to me crashes. Sometimes notifications disappear for no reason. Sometimes a notification sound plays for no reason. Sometimes the screen turns off and locks for no reason. Sometimes the device reboots for no apparent reason. It can be said that Android does run on it. But it's not the experience one expects from a system that is supposed to be native to and ships with a device.

The camera quality is just beyond embarassing. The sensor was obviously chosen by number of megapixels and price only. It's been a long time since I've seen such smushy and noisy pictures even from a <100€ phone. Battery life isn't as good as you might expect from a clunky devoce like this. My Google Pixel 4a with not even half of the battery capacity, despite being over four years old and in daily use, lasts longer than the Astro Slide with (very roghty and estimated) similar use.

When backing the Indiegogo project, my intention was to use the Astro Slide as a small Debian laptop for my packet. A mobile machine for SSH, FTP, some web stuff and for texting. It would have replaced its predecessor, the Cosmo Communicator, in that role. But Planet Computers stopped supporting any OS other than Google Android. Not only is there no official buld of any Linux distribution, the package mirror that used to provide DEBs for the Cosmo Communicator also quietly diasppeared. There doesn't seem enough interest in the device in the Sailfish community. Maybe some Linux support will come from users at some point. But I don't see any on the horizon.

With the previous Planet Computers PDA, the Cosmo Communicator, I had a fallback use case: an occasional PDA for SSH stuff while travelling, sometimes a tiny fileserver at events. But lacking availability of any non-googley OS, I feel compelled to ask: What is the Astro Slide for? I, personally, don't seem to have a suitable use case for it.

Comment via email
SBWG 0.11.1

I'm glad to have this version done and published. Even though it has new features compared to the last published version, I've used it enough to feel relatively comfortable saying it is also more stable and has fewer bugs than the last version. There are known bugs still left. But those aren't new.

Caching options and settings are slowly getting a bit elaborate, but also close to what I imagined them being able to do. There are new cachegroups and parts of entries can now be chosed as individual cachegroups, giving the user more control over what is cached and what caches are used. The lifetime of caches can now be set to make sure that no matter how the caching options are used, no outdated content, tags, attachments, etc. will stay on the web site for too long because cache files have been forgotten to be purges. The cache lifetime can be chosen from 1 second to unfinite. The directory used for persistant caches can now be chosen via command line option. I think the caching options are now in a state in which they can seriously be used reliably. Changes to existing cachegroups, like in previous versions, will probably not be made anymore. Just more cachegroups will be added.

The README file has grown a lot. Not only from new features and options. It's now also more complete. A lot of bugs have been fixed. And some general little code quality improvements took place. The stylesheets of the example web site have been improved a bit.

The messaging and logging system has been completely rewritten. It's not really an important part of the script and strictly doesn't matter for its functionality at all. But I decided to have a messaging system and a logging option that doesn't rely on shell redirects. So I did want to redo it properly. Different message types can now be redirected using file descriptors. The option parser has also been party re-written. It's approaching a state in which it's close to what I think personally a complete option parser for Bash should be like.

Alternate styles can now be defined in a web site's settings file. That way alternate style sheets will be offered to the web browser. If the browser supports alternate style sheets, the visitor can select from them to view the page in a different style. There is now an option to change the tagstyle, enabling a web site to have tags of the same type grouped for a more readable look of the entries' headers. Tags now show in parenthesis the number of entries that carry that tag. The number of file attachments is also displayed below entries.

The options for generating a single entry, page or gallery that is not located in the input directory/isn't actually part of the web site can now be used. They were very buggy or nonexistant before. Entries (and other items) with duplicate names are handled in defined ways now. Text files can now be used as file attachments to entries. But if the script determines one to look like a SBWG source file, it is omitted/not displayed/not linked to.

There are still big plans for future versions. Small and big features as well as a complete re-thinking of how the input directory is structured. Nicer looking web sites, more flexible command line options, more options for speeding up the script in cases where a complete website is updated/re-built. A pause like the one before this release will probably occur more often in the future.

Comment via email
Planet Computers' Astro Slide

I've finally received my Astro Slide. A smartphone with a physical keyboard that came out of a crowdfunding campaign that I've backed a few years ago. This entry contains my first impressions of the device, in the context of having used and having been disappointed by both its predecessors.

Specifications

Display6.53 inches, 2340 x 1080 pixels
ProcessorMediaTek Dimensity 800 (4 x Cortex-A76 + 4 X Cortex-A55)
GPUARM Mali-G57 MC4
RAM8 GB LPDDR4x
Storage128 GB
Cameras48 MP rear, 13 MP front
SpeakersStereo
Ports2 x USB-C, 3.5 mm audio, microSD card slot
Wireless5G, WiFi 5, Bluetooth 5.1, NFC, FM radio, GPS, GLONASS
Battery3.500 mAh
Charging10W Wireless + wired fast charging
BiometricsFingerprint sensor in power button
Keyboard53 keys, slide-out, backlit
Dimensions164 mm x 76.6 mm x 15 mm
Weight300 g

Planet Computers

Planet Computers has created/produced and is selling three PDAs/smartphones with keyboards (Gemini PDA, Cosmo Communicator, Astro Slide). That's their legacy - smartphones of the clamshell kind (or slide-out in case of the new model, the Astro Slide) similar to the Psion Series 5. The form factor and keyboard of all three those devices is remarkably similar to this 1997 PDA. The opening mechanisms aren't. But enough about previous devices. Maybe I'll write about those two, since they are relatively unique devices.

Crowdfunding period

You can skip this and the next paragraph if you just want to know about the device and not my experience of getting it and my opinion on the crowdfunding process. The Indiegogo campaign ended in May 2020. Mass shipping of the produced devices was delayed until the end of December 2022 for various reasons. There was an availability/alleged scamming issue with important parts, forcing a redesign of the board including a switch to a different SoC. There were the usual discrepancies between time planned and actual time needed to finish steps. And there was a long series of problems caused directly or indirectly by the COVID19 pandemic. There was (and continues to be) a fucking huge pile of negativity and hostility towards the maker of the device. Maybe you know the sort of comments delayed crowdfunding campaigns tend to get. My impression is that people regret giving their money to a company as an investment with no security, lose hope to receive the device as expected, and then start to badmouth everything about the project and insult people who continue to support the company behind the project. I don't read much of the comments on campaigns that I'm not supporting. But I've never seen so much hate and unnecessary negativity for a fucking tech gadget. I'll refrain from repeating any details or telling any stories that don't have a point. But I wanted to mention it.

My personal take on the long waiting period: The stated delivery date at the time of backing was never realistic. Even the date to which it was later changed, or the one after that weren't to be expected to be the actual dates at which any devices would be delivered. Every tech gadget crowdfunding I've ever seen missed their delivery target date. But of course people will expect or pretend to expect to receive it before the stated date because that is precisely the purpose of stating that date. Anyway, most of the announced delays were sort of understandable in the current situation; even though Planet Computers surely didn't tell the (whole) truth all the time and their often denounced lack of communication skills is undeniable although not as big as purported by some. Instead of checking and filling the comments page weekly for two years, myself and other people who also didn't channel all their hatred into that page just didn't complain in the comments and still received the same device at the same time as the others. Although one good thing came of the complaining of some on the comments page: When a picture of a prototype or render or something (I don't remember) was shown in an update and people complained about the space between the feet not being filled with battery, Planet Computers made a poll that ended up showing that most backers want an even thicker device than it would have already become, and the design was changed to fill the last gaps with a bigger battery. Communication as a customer with them never feels great. They try to evade warranty claims, ignore questions and arguably lie if they feel that the response sounds better that way. My contribution through Indiegogo was locked for many weeks without an update. I moved house before shipping actually started. So I couldn't update my address on my own but had to send Planet Computers a message instead. They claimed to have updated it (ignoring other questions), but over a week later it was sent to the old address. Gladly UPS really tries to fulfil their task to the utmost satisfaction of the recipient.

Unpacking

At first I wasn't sure whether I even wanted to open the package. Because by I'm already waiting for another device that I discovered after backing the Astro Slide campaign but expect to like better than the Astro Slide. I shortly considered selling it unopened. But whatever, I wanted a treat now, not wait a few weeks for a better one. The packaging is of the sort that we have to come to expect from electronics gear that's not of the lowest price and quality. Nice, thick cardboard and not the simplest box design imaginable. I don't really appreciate this packaging the way others do. When getting everything out of the box, the bottom tray came out too. It obviously used to be glued in but ripped out with force. Also the holder for the SIM tray opening tool was damaged. If the box hadn't been sealed by a thick round transparent sticker, I'd say this box was opened before. Anyway, the device looked fine. When I turned it on I was surprised to find that it was already set up and the language was set to Japanese. Not the most obvious choice for a device with a EU charger and a German keyboard. It really seems to me like somebody else has received and tried out this device before.

Hands-On, Keyboard

My first impression is: It's thick and heavy, as we wished for in the poll. I don't mind that. It's supposed to be a tool, a PDA, not competition for the iPhone or not something to impress people with. The sliding mechanism is new. Both folding mechanisms of Planet Computers' previous devices didn't last long in my hands (or pocket). So I'm curious to find out whether this new approach works better. In the videos it looked more awkward to open than it really it. It's hardly possible to open with only one hand, but it's possible if you absolutely have to. And I think it would become even quite easy and less awkward as long as your hands are at least of average size. It's less fumbly to close with one hand though. After only a few tries of opening it with two hands I got the hang of it and I can do it quickly, without the edge getting stuck in the keys and looking really cool. Maybe that success is due to me using it too violently. But it doesn't feel like I'm straining or pressing anything in a way I shouldn't. So before I've actually used it for a while I'd say the new mechanism feels better than the old one. The keyboard layout is the same as with their previous devices: very much inspired by the Psion Series 5 PDAs from 1997 (and other similar PDAs from that time). For some unapparent reason they've changed the size of some keys though (Left Shift, Left Ctrl, Up, Down). The keys feel more firm than on my Cosmo Communicator, except those on the edges of the keyboard. During my first few tries typing text on it this feels better than with the Cosmo or the Gemini. But my main issue persists: Keys often to very often get stuck. Not in their pressed-down state. Rather they refuse to move down if hit in the wrong angle. When touch-typing on a too small keyboard, one hits the keys in all sorts of angles though. But beyond that I don't want to judge the typing experience. I find it too small for two-handed typing and it's too big and not made for thumb-typing. It takes quite some getting used to or training to type fast and reliably on it. But that's not the fault of the device. I'm sure it must have been the same with the Psion 5. Compared to most high-quality laptop keyboards the Astro's feels a bit cheap in that the keys don't travel consistently straight downwards depending on the angle from which they are pressed. When typing quickly and carelessly, keys sometimes can feel like the got stuck on their way down. But the key press usually gets registered, so that might not matter after getting used to typing on this keyboard. The experience is very similar, if not the same, to typing on a brand new Cosmo Communicator. The space key for some reason feels like it has hardly any travel. But it works well when actually typing text. The bugs that were there in the previous devices haven't been addressed. There's still ghosting when pressing more than two keys, caps lock still sometimes gets enabled accidentally and the caps lock light still sometimes is off when caps lock is on and vice versa.

First few minutestimes trying it out

A certain standard for features, form factor and quality has became standard for smartphones. The form factor of the Astro Slide is obviously different. The technical features can be looked up in the table above. For the perceived quality and experience I'll just list things that I found noteworthy during the first few times using the device. When the device is close, the screen flashes to maximum brightness every time it turns on. The display can not be turned off while the device is opened. It turns off after the set time of inactivity. There is now automatic screen rotation based on the device orientation, like in any other smart phone since the iPhone. But more prominently placed, there is also a setting in the pull-down menu that lets the user switch between landscape and portrait mode as long as the device is closed. When it is opened, the setting is ignored and the screen is set to landscape mode. When the device is closed again, the setting gets changed to portrait mode regardless of what it was before opening or while open. The lock screen is always in portrait mode when closed and always in landscape mode when opened. That mess needs to get sorted out. But, as long as you only ever want to use the Astro Slide in portrait mode when closed and only ever use it in landscape mode when opened, it should be fine. Except when booting the device while it's opened. Then the screen is in portrait mode and can only be changed by closing and opening it again. This could be done properly. But since it's not, having two separate automatic screen rotations (based on opening/closing the device and based on orientation) plus a manual setting may have been the wrong choice.

There is a notification from "System Update" with the title "System Update" and the message "System Update" that's almost always present. Sometimes it disappears for a short while, then it comes back. It can't be dismissed, opened, turned off or blocked. I bet there are system updates because the OS is pretty old by now and I've never done an update. But I also don't see a way to do an over-the-air update. The check in the settings says there is no update even though the security check says there has been a security patches available for over a year. Too bad those update problems weren't fixed after causing me so much frustration with the Cosmo Communicator. I'll have to research doing the update manually if I want to keep using Android. (I probably won't though.)

The keyboard backlight still doesn't turn off automatically even though there is an "Auto Keyboard Backlight" setting that seems to affect nothing. Same as with the predecessor. Maybe the setting does something less obvious. But since questions like this are almost never answered and have been ignored for years, it feels pointless to try and find out. While browsing the settings I came across an empty sub-menu. No idea what I'm missing out on and why it's empty/there.

I got the Astro with only Android pre-installed. That option was supposed to become available sooner than the others. I don't intend to use it with Android. But since that's what it has right now, I'm only writing about Android in this entry. There is a Debian variant available from Planet Computers and probably also some mobile OS other than Android, but not officially supported by Planet Computers this time. The Android comes with Planet Computers' own apps and with the Vivaldi browser pre-installed. It's also heavily bloated with Google apps. I assume Google requires this to allow Google Play Store access. Very many permissions are already given to Google apps. As with other Google Androids using Google apps and sending Google all your data feels optional but isn't. The setup after a factory reset was quick and easy. I was basically just asked for a language, that's all. The user is not forced or even asked to sign in to or create a Google account unless one of their apps is opened.

I like the display. It has no high frame rate, no resolution beyond what can be detected with perfect eyesight but also not less. It doesn't have extremely thin borders. The viewing angle is as good as it gets (better than with my recent Google Pixel). Nothing noteworthy about colours. It's a very good display. The pictures that the cameras produce are very bad though. I didn't test it in bright sunlight. I'm sure there's no major problem there. But in normally lit rooms and on a cloudy winter day outside the picture quality is really crappy. Pictures are almost always blurred unless you try really hard not to move at all. And even then all pictures are a collection of blobs created by a noise removal algorithm. Every picture makes it obvious how cheap the camera sensor is. That's what happens when you put 48 megapixels in an area where 8 megapixels could have done a very good job. The front camera actually seems to make better pictures, but not by much. I had to take a picture of the lightbulb in a lamp in order to get a picture that's not a blobby mess. The speakers aren't quite as bad. But they absolutely lack bass. It's like cheap phone speakers from 10 years ago. Not nice for listening to music. But at least you understand what people say if you're in a small and quiet room.

There is a finger print sensor integrated in the power button. But it fails more often than it works and it is delayed. I've regretted trying to use it almost every time I did. It's much less annoying to completely ignore it. That may be the fault of my fingers though. I've trained several of them. But I also have had difficulties with the finger print sensor on my Google Pixel recently. (It says to clean it, but cleaning it doesn't help much/long.) All hardware buttons aside from the keyboard are very soft, leaving the user wondering whether the button press has been recognised when the device's reaction is delayed. It's unpleasant to turn it on with a button press. But I can imagine getting used to the button positioning and feeling.

Buggedibug

There there quite a few things that I noticed that don't work smoothly. Things that might be attributed to the apps that I'm using. But I found it conspicuous how many of bugs I noticed in the first few days of using the device. My guess is that the MediaTek chipset in the Astro Slide is just not supported as well and tested as much as more widely used chipsets. Here are a few things that keep annoying me: Sometimes while playing media, the entire system becomes incredibly slow, reacting very delayed, playing video with less than 1 fps, until rebooted. Sometimes (often) it's just slow, not being able to play an H264 video in 1080p. Sometimes part of the touchscreen isn't working. Sometimes the PIN touch keyboard isn't displayed on the lock screen. Sometimes the notification light lights up or blinks shortly without any reason. F-Droid crashed several times when trying to install some apps. Overall one should expect hiccups like that, sometimes having to use workarounds like rotating the screen when the area of the touchscreen that you want to use isn't working.

This text was not written on the Astro Slide. The keyboard is just too small for long texts for my opinion. But the more I use the device the more I get used to and over its shortcomings. I'll probably try Debian on it and possibly write about that too. Debian worked pretty well on its predecessor.

File Attachments (6 files)
Comment via email
Project Idea: Accessible Alternative Mouse Ideas (Reusing Old Ball Mice)

I think it was shortly after the first time I had taken apart a computer mouse that I had this idea. I must have been about 13 years old, or somewhere around that. For some reason this is one of those project ideas that I can't forget about. I usually don't pick up on these ideas. But other ideas don't pop back in front of other project ideas ever other year. And this one isn't even one that would be useful to me or anybody I know. Maybe I can get closure by posting the idea here.

So, you know how ball mice worked? The ball would rotate two separate wheels (one horizontal, one vertical) when the mouse is moved. So there are sensors that pick up horizontal and vertical movement independently. One could attach the drum/wheel to anything else that can be rotated. So one could, for example, connect one of the wheels to a crank, or a rollerblade wheel, or whatever. So then, instead of a small plastic mouse on the table, you could handle a different object, that suits you better. Specifically, my idea was to connect both wheels to wooden foot rollers. So one could move the right foot up and down to move the mouse pointer vertically and the left foot to move it horizontally. pressing down on each roller would produce a left or right mouse click respecively. The intention, besides having a cool new way of sending input to a compuer while sitting at a desk, was to remove the possibility to move a hand from the keyboard to the mouse and back. But I suppose it could possibly also be useful to people who don't have hands or can't manipulate a regular computer mouse with one of them comfortably.

I even got myself a pair of these foot rollers. I have enough cheap ball mice to sacrifice one or two to such a project. But here's the two problems, who's combined result is that I never started to build even a proof-of-concept prototype: It wouldn't be incredibly simple to create (orientation of the rollers, reliable connection to the sendors, additional complications for scrolling wheel) and I don't actually need a device like that. I don't have to switch to the mouse that often if I know the software that I'm using well and/or have it configured to my liking. Maybe it would be cool to train using this device so much that I could use it effortlessly and navigate a GUI fast with it, maybe even to be able to use it for graphics work. But what then? Even if I'd use it enough for it to become actually practically usable by me, I would at the absolute best end up where I've started: Using a convenient graphical input device, only this would would be less portable and I would expect one to be available at any desktop computer. It would just complicate things more than it could help make things easier for me.

So, here, take these pictures of the components that I could but won't use to build a mouse alternative and, well, probably forget about them immediately.

File Attachments (6 files)
Comment via email
Fred - Part 3 - Power Supplies
This entry is a reply to or continuation of the entry 'Fred - Part 2 - The Case Lid And Cooling'.

After getting rid of the fan wall, the power supply was the main source of noise. The original PSU was a 3U redundant (2+1) server power supply. Noise does not matter with machines like that. I wanted to be able to have it running in my living room though, so the noise had to drop a fucking lot. Seriously, that's said so many times for people who don't work with servers like this. But people are still surprised when they hear a server fan for the first time. One of original 60 mm fans in the back is louder than my vaccum cleaner. And there were two of those, four 80 mm fans and five 40 mm fans. Three of the latter in the power supplies. Because I have no means to control the fans in software and don't need all the power the power supply can supply, I tried how much I can lower the noise by adding resistors in series to the fans. That did reduce noise a lot. But not only aren't these fans optimated for quiet operation, they are 40 mm fans. They will nver be quiet enough.

So I looked online for a power supply that

  1. fits in the case (it's not completely an ATX case)
  2. can supply enough current for everything and
  3. is trustworthy/doesn't appear to be too cheaply built

I found a Newton Power Model NPS-300AB B, which doesn't meat points 2 and 3 but fits so perfectly into the case that it was a weird feeling to accept that it is mostly coincidence. I got it for a couple of euros on ebay. Most sellers seem to think it's some piece of premium equipment because it's used in some Fujitsu servers or something. But it's really just a cheap ATX power supply in a non-standard case. But because of that non-standard case fitted so well into my non-standard server case, I got it anyway. I only had to drill the screw holes and that was it. It's hardly enough for 14 HDDs and the internet says it's really cheap and not trustworthy. But I went with it anyway in order to pay tribute to r/thingsfittinginthings.

Not a year later the PSU died. Probably overstressed it for too long. I replaced it with a better SFX unit. I had a nice and thick plate of stainless steel lying around, from which I cut an adapter plate.

I'll attach some photos below. Maybe I'll continue this series of entries on Fred some other day with experiences of dust and heat and such over time.

File Attachments (5 files)
The old power supply after it died_ (The unplugged fan and the missing screws do not resemble how it looked while it was in use_)
The old power supply after it died. (The unplugged fan and the missing screws do not resemble how it looked while it was in use.)
Maybe it would have lived longer if I had cooled it better_ It wasn't efficient_ It would have been too loud_
Maybe it would have lived longer if I had cooled it better. It wasn't efficient. It would have been too loud.
The new power supply_ Fits well in height and leaves more than enough room for its modular cables (even for the ones that aren't used) and airflow_
The new power supply. Fits well in height and leaves more than enough room for its modular cables (even for the ones that aren't used) and airflow.
I'm happy with the adapter plate and how it turned out, even though I originally made it for a different SFX unit and the fan cutout now seems redundant_ But it actually looks kind of professional_ That's rare enough with me_ I bet you can't tell which part I made myself_ (Or is this because the photo is so bad?)
I'm happy with the adapter plate and how it turned out, even though I originally made it for a different SFX unit and the fan cutout now seems redundant. But it actually looks kind of professional. That's rare enough with me. I bet you can't tell which part I made myself. (Or is this because the photo is so bad?)
I made my own modular cables with old molex connectors for the HDD backplane_ The unused cables in the plastic bag has its place at the back of the PSU_
I made my own modular cables with old molex connectors for the HDD backplane. The unused cables in the plastic bag has its place at the back of the PSU.
Comment via email
Mastodon