Goodereader has an editoral saying ereader manufactures should be using Android Go for readers.
Google shaves half a gig off Android Poundland Edition
Google's "Poundland" Edition of Android – Go – has received an update to 9.0 Pie. Google leaps on the platform formerly known as Firefox with $22m splurge for KaiOS READ MORE Not to be confused with Android One, which is really a marketing program for full fat Android, Go Edition is a small footprint version of Android …
COMMENTS
-
-
-
-
Thursday 16th August 2018 10:50 GMT Dave 126
I can see some of both sides here:
I can see the benefit of a an E-Ink tablet for reviewing and annotating text. From there, being to use Android apps and services to share the results with collaborators would seem to be a reasonable use-case. More niche are paragliders who like their GPS on E-Ink, for visibility in bright sunlight.
For just reading some fiction on the beach, Android is likely overkill.
-
-
-
Thursday 16th August 2018 16:55 GMT Mage
Re: Where are the missing e-ink tablets?
Android is pointless on eInk Readers and maybe only to make vendor "spying" easier.
The eInk is inherently only suited to reading and annotation, yet most are useless for actually getting the notes back to PC. Yet they put things like share note/higlight to Facebook, but not email nor ability to easily read back on per book basis.
I've an Android tablet and phone. The phone is convenient for reading eBooks, yet I've not found a single really good (i.e. actually better than Kobo H20, Sony PRS350 or Kindle eInk) ereader app.
The ability to search, organise, categorise, import the books is terrible. New eReaders in some cases worse than early ones. Homescreens almost dedicated to marketing. Worse than 1980s document management systems.
No point in Android apps in general on an eInk screen. They are best for reading. They could do with better reading apps and book management. This has not improved in 12+ years.
I've used maybe nine models of eReaders (one oddly was LCD not a tablet like Fire) and tried loads of Android apps. Aldiko not too bad.
I should not need Calibre to manage my "library" and eReaders.
-
-
-
-
Thursday 16th August 2018 10:16 GMT Anonymous Coward
May sound obvious but is there any way to get Android Go for regular devices?
After all, if Maps Go is 50% smaller than regular Maps, but only removes features a small percentage of users need....it could be pleasant.
Like how I run Lubuntu even though I don't have a low-powered machine, simply because I don't want or need the cruft the full-fat versions comes with...
-
-
Thursday 16th August 2018 10:29 GMT Dave 126
Maps Go is little more than a link to a browser, something called Progressive Web Apps. So apparently yes, you can 'install' on normal Android, and you don't even need an APK file. It doesn't have navigation or offline maps though - the latter being well worthwhile if you have ample storage on your handset. Still, suck it and see:
https://www.digitbin.com/install-google-maps-go-incompatible/
-
-
-
Thursday 16th August 2018 10:40 GMT Dave 126
Re: 2.5 Gig footprint for a fucking phone OS
Oh yeah, Symbian, the OS that wasn't well suited to lots of memory and graphics acceleration, causing its caretaker to be late to market with a Linux-based successor. It wasn't just Symbian that hit this bottle neck; the likes of Sony pushed PalmOS as far as it could go. Like Palm OS, Symbian didn't start out on telephones.
As a telephony OS Symbian was fine (though I remember one Nokia taking two minutes to open an standard SMS message) but most of here have mobile internet devices and general purpose computers that we merely call phones.
-
-
-
This post has been deleted by its author
-
Thursday 16th August 2018 13:04 GMT Robert Helpmann??
New El Reg UoM?
I wonder what that equates to in terms of height of a stack of punch cards....
Wonder no more! A punch card can hold about 80 characters or 10 bytes. This means 500MB would take about 5e7 cards. There are about 143 cards to the inch. Stacking them in a continuous column climbs up 349,650 inches or around five and a half miles. YMMV (literally) depending on data storage format on the cards, rounding errors and other assumptions made above, and the amount of caffeine consumed immediately prior to digging this up.
-
-
Thursday 16th August 2018 16:53 GMT Robert Helpmann??
Re: New El Reg UoM?
Inches? Miles? Might I suggest you have a look here
I was aware of the page, but it would not run properly on my work machine. This theoretical stack of cards would soar into the skies a whopping 403 Brontosaurus lengths. Just picture 403 of these late Jurassic giants end to end and then imagine them floating snout to tail tip straight up* and you will be rewarded with a dubiously accurate image of this posited assemblage.
* You might want to imagine a sturdy umbrella or similar protection (see icon) because at least one of the beasts is going to go and from that height... well, let's leave it there.
-
-
Thursday 16th August 2018 20:17 GMT Richard Plinston
Re: New El Reg UoM?
> A punch card can hold about 80 characters or 10 bytes.
A punch card can hold 80 bytes. 'characters' is not 'bits'.
Some punch cards were smaller and 132 column, such as on System 3.
I could hold the operating system on punch cards for an ICL 1901 in one hand. It was about 3inch stack.
-
-
-
Thursday 16th August 2018 10:56 GMT Dave 126
It's an OS for a device that does everything Windows XP can, more or less, so why expect huge difference? Its a 64bit OS designed with the internet, more than half a gig of RAM, video and hardware acceleration in mind. The only reason I would expect an XP install to be bigger is if it hadn't been shorn of drivers for a thousand printers and other hardware configurations.
-
Thursday 16th August 2018 17:01 GMT Mage
It's an OS for a device that does everything Windows XP
Really?
Crap and erratic support on apps for copy/paste, printing, external storage, non-USA keyboards, custom key layouts, network resources etc.
It's more like Win 3.0. Barely, at least you didn't have to BUY a file manager for win 3.x.
Android is a work in progress that has been crawling in terms of developing useful to user rather than useful to Google features.
-
Wednesday 2nd January 2019 16:46 GMT captain veg
Re: It's an OS for a device that does everything Windows XP
I switched to LineageOS a couple of years ago when our BOFHs tweaked Exchange in some diabolical way that the email app on my N9 didn't understand. Have to say that I was shocked at how user-hostile it is. My first ever smartphone (also my first ever mobile phone of any kind) was far and away the easiest to use. A Handspring Treo, it ran PalmOS.
-A.
-
-
-
-
Thursday 16th August 2018 11:47 GMT Charlie Clark
Re: Small footprint OS
I think the plan is indeed to ditch Java for the OS at some point, though I don't think that it will be replaced by FASM, not least because of the huge variety of SoC's that are expected to run. KolibirOS looks nice but I think I'd rather investigate QNX or RiscOS as possibile altermatives.
In any case, while shrinking the footprint is indeed desirable, the mere fact that 8GB ROMs are pretty much standard for the lower end and can still lead to devices with sale prices < $ 30 tells you that this isn't the bottleneck it once was.
-
-
Thursday 16th August 2018 18:17 GMT Charlie Clark
Re: Small footprint OS
If yuou're going to go to QNX, why not just bring back BB10?
I guess that Google (could easily afford to buy BB) and others looked at that and decided against it. After all, BlackBerry did the same after a couple of years. I suspect that mixing so much virtualisation with direct access to the hardware where required isn't easy.
-
Thursday 16th August 2018 21:32 GMT Anonymous Coward
Re: Small footprint OS
I suspect that mixing so much virtualisation with direct access to the hardware where required isn't easy.
OTOH, I suspect that Google don't give a shit, and Android is now very, very mature, and the business plan is to milk it dry, doing diddly squat beyond the minimum, and that minimum includes periodic "new releases" with increasingly token improvements, and squashing sufficient security bugs to give the appearance of doing something about security.
This is of course the norm for all software businesses.
-
-
-
-
Monday 20th August 2018 04:53 GMT Anonymous Coward
Re: Small footprint OS
Java apps are extremely small as long as the developer can resist the urge to link to every open source library on Earth.
Google stuff is enormous because Google absolutely sucks at dependency management and they don't believe in dynamic library linking. Imagine tens of thousands of code monkeys each writing to and for APIs that are an opaque mix of local code and RPCs. You give up figuring out where anything is. The Googly version of "Hello World" that I learned in training took 15 minutes to compile, produced a 120MB executable, and took 5 seconds to launch. I told the teacher that I wasn't impressed. He recommend I turn on the "optimize" flag so it would only be 75 MB.
Not even Google can solve Googly problems. Rumor is that Google created Golang to ditch all the baggage around their C++ and Java codebases. Unfortunately, Go's crude data structures can not model the protobuf spec. At the time of my escape, the Go codebase was bloating out of control as maintainers of API code generators attempted to produce more correct protobuf models using complex trees of interfaces. Again, all of that bloat is statically linked into every single executable.
-
-
-
-
Thursday 16th August 2018 15:06 GMT Norman Nescio
Re: Old Linux ?
1K?
(You attempted to end too early, which puts you in Nid.)
You were lucky. I 'ad 256 bytes and a 20 key keyboard. Being sliced in two wit' bread knife was optional.
-
-
Thursday 16th August 2018 22:39 GMT nagyeger
Re: Old Linux ?
32K? Thirty two? What luxury! You could play acorn invaders and rat race in 3K, as long as you could get the volume right on the tape player.
3K of RAM really taught you how to watch your code for bloat.
The first Linux distro I used fited on 2 floppies, if I remember right that was including including gcc.
-
-
Thursday 16th August 2018 20:27 GMT Richard Plinston
Re: Old Linux ?
> Oh yes, a 386sx33 with a math co-processor & a then massive 4GB IDE drive. I had slackware running on it
I did run Freesco Linux (cf Cisco) as a network hub and server*. No HD, booted off a 1.44 FD on a 386x20 with 16Mb RAM.
* it allowed the 56Kb modem and the printer to be shared, ran NTP and a small web server plus some other stuff.
-
Friday 17th August 2018 09:08 GMT bpfh
Re: Old Linux ?
486 DX2 66 with 4 meg ram, running OS/2 Warp 3 presentation manager, and running Word 6 in its integrated Windows 3.1 interface. And running what could be called “virtualised” today an ms-dos 1.1 image in a command shell. And MS-DOS 6.11 image in another command shell, and a Slackware image in a 3rd image in a command shell, though it did end up pulling a trap D when trying to boot a QNX image into the OS2 presentation manager...
-
-
Sunday 19th August 2018 06:52 GMT Christian Berger
Linux actually is much more than what you'd need on such a device
Essentially Android used a fully featured OS and cut it down PDA style. From a users point of view there is not even a filesystem left, and users are expected to "sync" their devices to cloud services, just like traditional PDAs had to be synced via special software.
All the security mechanisms protect business models, not actual user security, so once we get rid of the malware store (and have something like Linux distributions have) we can get rid of that, essentially allowing users to become root on the devices they paid for.
-
Sunday 19th August 2018 19:10 GMT Richard Plinston
Re: Linux actually is much more than what you'd need on such a device
> From a users point of view there is not even a filesystem left,
Not true. just run one of the many file managers, such as 'Total Commander'.
> users are expected to "sync" their devices to cloud services,
They can if they wish, or they can connect to almost any desktop or laptop computer and backup to that.
Have you actually used one of these devices or are you just using 'alternate facts' ?
-
-
-
Thursday 16th August 2018 13:45 GMT T. F. M. Reader
Count me in!
A <$100 device with a half-decent screen, phone, contacts, calendar, and maps, and maybe even a light-weight browser and an email client, and without all the storage-hogging stupid apps, from FB to Drive to Office to whatever, that I never use but can't remove without rooting / voiding warrantly / etc.?
Hell, I'll pay cash! A camera is nice to have, but not mandatory.
-
-
Friday 17th August 2018 17:29 GMT Oh Homer
Re: Android garbage
Short answer: money.
In fact I've found that the answer to most questions is money.
The long answer would take several volumes, but without going into too much detail:
- Android's obscene bloat is primarily due to Java, which is typically chosen so that people who aren't really software engineers can use point 'n drool toys to produce large volumes of crap very quickly, then sell it equally quickly (i.e. money)
- Android has been deliberately designed with a "read only" mentality, for lots of reasons (all bad), but mostly to prevent you removing highly lucrative bundleware (i.e. money)
- Memory management isn't poor on Android per se, it's just that it's such a bloated pig (including the apps) that you might just as well be running Windows. Moreover, Android apps are explicitly designed not to be closed. Ever. Everything on Android is a "service", mostly so it can spy on your every move and send "telemetry" back to the mothership for resale to spammers (i.e. money)
-
-
-
Thursday 16th August 2018 18:02 GMT Anonymous Coward
"Response to stripping Google" in favor of AOSP
Does Google really believe OEMs selling low end phones are doing that due to the size of Android? They are doing because the margins on low end phones are zero (at best) and they can sell placement to others.
China will never adopt Android Go, they will continue with AOSP Android phones with Google replaced by Baidu, Wechat, etc. who pay the OEMs for their inclusion.
Even if the idea "Android is too big" was their issue, trimming it from 3 GB to 2.5 GB is hardly worthy of crowing about.