CSV-teksti asetamine Androidi installitud tabelarvutusprogrammis

See oli redditi-lõngas äppide välja lülitamisest Androidis (Android 14 ja varasemate näitel).

Disable-võimalus tuleb ainult sisse-ehitatud äppidele, ning ka mitte kõigile.

Osad äpid, kui nende uuendused on maha installitud, muutuvad süsteemiäppideks, seega tuleb äpilistis näidata ära ka süsteemiäpid.

Kahjuks pole siis ka äpilistis (lausa Android 14-s) kirjas, et kumb äpp on eraldi installitud ja kumb on süsteemiäpp.

Seda muret on võimalik leevendada:

Ostsin endale hiljuti uue nutitelefoni ja siis tuli vajadus automaatselt genereerida nimekirja äppidest ja nende versioonidest, mis telefonis on.

Abiks tuli AppList, mis on saadaval F-Droid äpipoest või samanimeliselt veebisaidilt. AppList genereerib nimekirja automaatselt, kuid tuleb kolme-nupu menüüst valida "System apps", et saaks täielikuma ülevaate.

Siis eksportida nimekiri, mis sisaldab ka infot selle kohta, kas äpp on süsteemiäpp.

Installisin eelnevalt Markor äpi, kuhu AppListi andmed sain eksportida CSV kujul.

See on üks väheseid tekstitoimetamise äppe, mille ma olin uuele telefonile installinud, mis võttis eksporditud nimekirja vastu (õieti, mis oli eksporditava teksti sihtrakenduste nimekirjas).

Mis puutub failihaldusse, siis Markorit esialgu väga lihtne kasutada ei ole.

Markoris saab CSV-andmed kõik valida ja kopeerida puhvrisse. Siis asetada mõnda tabelarvutusäppi, nagu Google Sheets, kuigi mul oli lihtsam see asetada AndrOpen Office'isse.

AndrOpen Office on omanduslik port ja haruarendus Apache OpenOffice'ist (varasem OpenOffice.org, millele eelnes StarOffice). Eelis on selles, et mobiili jaoks mõeldud liidese asemel on sellel pigem desktopi-programmiga sarnane liides, mis on tuttav.

AndrOpen Office'is on reklaamid, aga need ei ole mul nähtavad, sest mul on installitud ja enam-vähem okeilt seadistatud DNS66, mis süsteemiüleselt blokeerib äpireklaamid (v.a. YouTube'is ja mõnes suuremas äpis).

AndrOpen Office Calc-is tuleb kõigepealt valida kogu tööleht ja Format > Cells. Seal tuleb valida "text" (valikuid tuleb kerida), siis ok.

Edasi asetada puhvrisse kopeeritud tekst Edit > Paste Special käsuga, kus CSV-teksti eraldajana tuleb märkida koma, välistada tühikud ja tabeldusmärk (tab), ning siis tee linnuke "format quoted field as text" juurde ja siis lülita välja "detect special numbers". Vajuta OK.

Tulemus:

The modern wonders of smartphone tech

So I watched footy yesterday between Wales and Denmark (Denmark won :), and the football pitch showed ads for some large South-East Asian brands — in non-Latin characters.

So thanks to Firefox, Android 9.0 (which is the latest version of Android that I have right now), and Google Lens, I was able to do several things.

Unlike the default ETV* apps of the Estonian national broadcaster ERR that do not allow making screenshots (in modern Android, apparently), Firefox did permit screenshots when using the browser in Android to watch the official ETV livestream.

I could then make screenshots of the ads flicking on the edges of the green pitch, and use Google Lens in Google Photos to find out what some of the ads were.

So, one was for a SE Asian brand of air conditioners with a non-Latin slogan, and the other displayed a slogan for some kind of SE Asian blockchain technology/solution.

— Google Lens offered a button to Google Translate, and another to play that text back in the original language.

Wow, I say.

My BunsenLabs story

Posted as a reply in the BunsenLabs user forum.

I have an hp Pavilion dv5000 (dv5204ea), with Intel Celeron M 410 running at 1.46 GHz and 1 Gb of RAM memory, and a BIOS date from 13.06.2006., so the computer is 13 years old.

I use the CD version of BunsenLabs Helium as a LiveCD, and due to limited RAM memory, prefer that over the DVD variant.

NoScript is a huge amount of help when browsing the web, but YouTube is impossible to use with 1 Gb of RAM when BL is run from a LiveCD. In my experience, the LiveCD experience of YouTube is good with at least 2 Gb RAM and a dual-core CPU.

BunsenLabs (BL) meets several requirements:

• LiveCD (not DVD), so uses less memory;
• Small memory footprint;
• Based on Debian, so is also compatible with Ubuntu;
• Can run X, with only a window manager;
• Touchpad and pointer drivers must work reliably;
• Has modern Firefox.
• Bonus point: SystemD allows me to limit the memory Firefox can use.

BunsenLabs is one of the few that offers all that. I have a Knoppix 7.2 liveCD, but it's from 2013, is very old, has unreliable pointer drivers, and installing ID card software was cumbersome, and worked partially; I was only able to login and check my bank balance, but not make any transfers.

Ubuntu compatibility and modern Firefox are required for the latest supported software that uses the Estonian ID card. Upon tweaking the installation script, it installs the ID card software and a Firefox extension (both meant for Ubuntu Xenial) that helps with authentication and making electronic signatures online.

The Estonian ID card is a smart card and an identification document that's used for electronic authentication and electronic signing; it's used to access banks and make money transfers; to sign official documents (incl. contracts); to access government services, to conduct business and communications with the government; to vote online in local, general, and EU elections (expat or traveling Estonians can vote anywhere in the world, if they have the kit); to encrypt files, usually for transfer, to ensure high message secrecy; to remove oneself from party membership, and lots more. The ID card is a valid travel document within the European Union.

Estonia adopted the ID card system in 2002, but I got my first ID card in 2009, seven years after adoption. Until then, I used a passport, mostly to identify my person during elections, and when taking cash to the bank.

So, a year ago, after my bank stopped using non-electronic code cards (those with written numerical codes) for two-factor authentication, I finally got an ID card reader — nine years after I got my first ID card (I'm on a second one), and sixteen years after ID card readers became a thing in Estonia.

With some effort, it's possible to install Estonian ID card software meant for Ubuntu, so I could login into my bank and make transfers. Unfortunately, the ID card management software does not yet work properly. But I could vote! — Because the voting program is a separate package.

I'm not a luddite when it comes to technology, but am one of those who gets personal access to interesting stuff and technology much later than my reference group. Because reasons, but that's life, I guess.

So, in Autumn and Winter of 2018, BunsenLabs was essential just so I could check my bank balance at home, and make transfers.

The day-to-day need to use BunsenLabs waned in January 2019. On Christmas 2018, a relative got a new smartphone, and I asked for their old smartphone, explaining, that I could upgrade that old smartphone from Android 4.0.3 to Android 4.1.2, and install Smart-ID — so I could easily access my bank when in transit. Android 4.1 is the oldest version still supported by the Smart-ID app. The relative was convinced, and I got their old smartphone.

My earlier smartphone runs Android 2.3.6, and does not have any more upgrades available. Furthermore, in December 2018, the YouTube app also stopped working on Gingerbread. (There, the default browser would render the mobile YouTube page and thus allow playback in an external player until September 2019.)

Smart-ID is a new two-factor authentication system and app in Estonia and Latvia.

There is also Mobile ID (Mobiil-ID). It's equivalent to the ID card, and supports absolutely all kinds of phones, even featurephones dating back to early 2000s and even a bit before. One can vote with Mobile ID, but not with Smart ID. But — Mobile ID requires a phone contract and a specialized and more expensive SIM card, and is not exactly free, as it requires a small and regular fee.

Whereas Smart-ID is completely free, but has support for less services.

The newer device I got, is LG Optimus L5, which series was released in June 2012, a few months later than my Gingerbread phone.

I really didn't know if I could upgrade the LG phone from ICS to Jelly Bean. While information about upgrade possibility was up, off-the-air upgrades stayed within Android 4.0.3. This meant that I had to check if there was a computer-based upgrade possible.

At first sight, LG's official site had software available that would run on Windows 7 or greater, while I have Windows XP. Fortunately, LG's Australian section offered packages compatible with Windows XP, enabling me to make a backup of device data, and perform the upgrade to Android 4.1.2. Yay!

Getting Smart-ID registered still required use of the ID card, so BunsenLabs came in handy again.

I could login into my bank again. Yay!

As a result of installing registering Smart-ID, I could download my bank's app that just happens to also have Android 4.1 as the earliest supported Android, so with some effort (because this phone's RAM is only 512 Mb), I used Smart-ID to register my bank's app. My bank's app is crashy for most things, but at least allows me to check the balance quickly.

LG Optimus L5 has the same CPU and RAM specs as the phone with Gingerbread (Samsung Galaxy Mini 2), but sports a 5-megapixel camera with auto-focus and flash, while the Samsung smartphone has only a 3.15 Mpix sensor with just fixed-focus and without flash. This is really an upgrade to me, as the LG phone is able to scan more detailed QR codes, which has come in very handy.

Coincidentally, Android 4.1 is also the earliest/oldest Android supported by the Estonian online vote verification app, which scans a QR code displayed by the voting app in the computer after a user has finished voting. For some technical reason, the app wouldn't work as intended during the Estonian Parliament elections in March 2019. It's very possible, that the QR code to verify a person's vote has a very short lifetime. The app worked flawlessly during European Parliament elections in May 2019.

Looking back on an advert: Samsung Galaxy Mini II vs Nokia Asha 311

Five years ago (as of February 2019), this photo comparing Samsung Galaxy Mini II and Nokia Asha 311 caught my eye. On the surface, both had comparable specifications to what I wanted, but I'd preferred a Nokia phone simply on the strength of the Nokia brand. What follows, is a comment that I recently posted.

When my primary phone was a flip-phone with just a 2 Mpix camera, then I dreamed of getting that Nokia Asha 311 one day, as it had all of the new features that I thought I could want.

A young relative got that one for his birthday, but lost it soon after under a tree in the countryside (it was found a year later in a bit disheveled state, but it still worked).

In late 2013, I got the Galaxy Mini II as a hand-me-down (used). It's got a better camera than the flip phone (3.15 Mpix), and comes with Android 2.3 Gingerbread, ended up with a longer useable lifetime and with more functionality and apps than I would have had with Asha 311.

For instance, I could install Firefox on Android, and that extended the Mini II's useable lifetime for quite a bit longer than it would with just the default Android browser.

If equipped with NoScript, and configured properly, then Firefox is the browser that can prevent the planned obsolescence of many old Androids.

When several apps stopped working on Android 2.3, I could use their mobile web equivalents in Firefox. Even Skype for Web, which needed specific work to function in Firefox on Gingerbread.

Five years after I got the Mini II, by Christmas 2018, I finally got an upgrade, which is a hand-me-down from an elder relative, who got a substantial phone upgrade themselves, and had no need for the old phone.

The 'newer' phone has almost the same specs, but a 5 Mpix camera, and had Android 4.0.3 Ice Cream Sandwich (ICS), which I'd upgraded it to Android 4.1.2 Jelly Bean through the phone's official connectivity software.

I would have stayed with Android 4.0.3, but I needed the upgrade, as 4.1 Jelly Bean is the earliest version supported by the Smart ID app, without which I wouldn't be able to do online banking on my phone, should the need arise. I don't have the SmartID app yet, but now I have the possibility to eventually find out, if I can run it there.

The official YouTube app no longer works on Android Gingerbread (2018). Remedies.

This is meant to be a reply in a thread at Google Product Forums. I've posted it here first. The official YouTube app stopped functioning in Android 2.3 in late-late October 2018.

Just an update: Logging out in the non-functional YouTube app in Gingerbread made it impossible to log in again. The error message (roughly translated) reads:

A problem occurred during launch. Check the network connection and system time.

It seems to me, that Error 410 probably appeared when an account is set as logged-in in the YouTube app, though I cannot claim this for certain. The error cited above now appears when attempting to log in, or when trying to play videos.

On the other hand, I got yet another opportunity to check out a device with Android 4.0 Ice Cream Sandwich (ICS), and the YouTube app does work there, provided, that some of the software components are kept up-to-date.

The example ICS setup with a working YouTube app has the following component versions:

* Android 4.0.3
* Google Play Store 8.0.76.R-all [0] [PR] 163912422
* Google Play Services 14.5.74 (000302-219897028)
* YouTube app version 11.01.70

People with Android 2.3 Gingerbread and a non-functioning YouTube app can do the following:

• Continue using the mobile YouTube site in the default browser that would launch videos in an external player.

The reason I suggest using the default browser ("Internet"), is, that while older versions of Mozilla Firefox and derivatives can run on Android 2.3, and while they do also support HTML5 video, then Firefox is resource-intensive on low-end devices. Such devices do not have enough RAM memory, and/or cannot run anything greater than Gingerbread. With these, video playback might work in Firefox, but not satisfactorily, or might not work at all.

• Or they can upgrade to at least Android 4.0 — either by updating the software, if a device manufacturer and/or mobile operator has an update on offer; or by obtaining a device installed with at least ICS.

---

This I left out of the reply:

It appears, that this time, the YouTube app not working on Android Gingerbread is final, hence 'no longer' in the title of this post. I don't think it will be fixed, and it would be a miracle, if it were. If someone has Android 2.3 with a working YouTube app, while most others don't have that, then the most likely explanation could be expired certificates in the app and Gingerbread itself, and updated certificates on the YouTube end. Such is life.

In this case, I follow a personal policy of not suggesting alternative apps. Therefore, if the official app doesn't work, use the browser.

A snippet on using Android 2.3 in 2018.

The text below was written in reply to a comment under one video about using Android 2.3 in 2018.
Pinch-to-zoom can and does work, but several things need to be done beforehand to implement this feature.

If I heard correctly, then the phone in question is a Huawei M865C, aka Ascend II (or Ascend 2). Its 600 MHz CPU is Qualcomm Snapdragon S1, specifically MSM7627, and is based on the ARMv6 architecture.

There is 160 Mb of internal storage available to the user. That's a very small amount, but storage is expandable with a microSD card, and PhoneScoop has it, that a 2 Gb card is included (either in the package, or as installed). I recommend using the incuded 2 Gb card, if it's already been installed and set to act as extended storage for the operating system.

One must update the device's system clock to make sure that some of the certificates are (correctly) rendered invalid, and that others still remain valid. This resolves only some of the certificate issues with the native browser component.

Then, one must let the operating system auto-update Google Play Store and Google Play Services. This happens in the background, and without notifications. These two services have several update cycles each to go through, as one depends on a version of another to update.

The version numbers below are based on what they are in Android 2.3.6.

AFAIK, the most recent Gingerbread version of Google Play Store is version 6.2.0.2, and the latest Google Play Services is v. 10.0.84.

The latest or most modern installable version of Google Play Services may take well over 100 MB of local storage, so a microSD card may be in order for long-term use, if it's not already present. Some Gingerbread devices support formatting a microSD card into an extended system volume, and a bundled card — albeit relatively small at just 2 Gb — may already do just that.

While it would be possible to move the microSD card around to other devices, the phone's operating system will still depend on that card for apps and updates, and in the absence of that card, the operating system might either cease working, or not work as one would expect. If the Android system supports graceful degradation, then only some updates and apps stop working and will appear as unavailable.

Once Google Play Store is accessible, update Google Maps. The most recent version is 6.14.5.

The most recent version of YouTube is 5.5.30. Watching videos and most other activities are possible, except uploading — there, you'll get a 410 error.

If all that doesn't work, install Firefox. Since the example phone, Huawei Ascend II, has a CPU based on the ARMv6 architecture, choose Firefox 31.3esr.

If Firefox is not available at the Play Store, you can download it from the Mozilla archive here. Note, that en-US is for a U.S.-English only package, and multi is for a multilingual package.

Devices with CPUs based on the ARMv7 architecture can have a version of Firefox up to and including v. 47.0.

Firefox has its own certificate store, which is quite a bit more up-to-date.

While these versions are not the latest versions of Firefox, they are still comparably more modern than the default Internet Browser, and so, Firefox will work in Android 2.3.

Note, that while Firefox will work and render modern websites, it's slow to start up as it loads settings and extensions. Since Huawei Ascend II only has 256 Mb of RAM, then Firefox is likely to take up all available RAM memory. You will need an ad-blocker, and you will need NoScript to prevent sites from hogging system resources. Most sites will load nicely and better than the aged default browser.

Use Firefox to login to the the web-based Google Play Store, where one can also download/install the official Google Maps.

I also recommend updating to Android 2.3.6, as it has some improvements, and slightly newer security certificates. The Android version in the video was certainly v2.3.4 or less.

---

If there is not enough storage to update Google Play Services:

Back up all your photos and videos, then use the built-in file manager.

In file manager settings, set it to show hidden files, and to show file extensions. Go to approximately where the photos are typically saved to: /sdcard/DCIM/.thumbnails . Files and folders with a leading dot are hidden.

Go into the .thumbnails folder, select all files, and delete them. This should save plenty of space, but note, that the system may re-create the thumbnail database at any time; especially when you view the gallery. Do not delete the DCIM folder, as it's the default folder where photos are saved to. The Camera app can be configured to save to a microSD card, if one is available.

Note, that if one or more thumbnails contain a small-scale image of a valuable deleted photo, you can connect the phone to the computer as a mass storage device, if the computer has access to relevant drivers. You'll need to download and install the phone's drivers from the manufacturer's website.

To reiterate:
You might need a separate microSD card on that phone, and if your particular phone model supports it, you can format or set the microSD card as an extension of system storage. Keep in mind, that that card is then tied to the phone.

What causes user interface lag (yank) in Android, and remedies to that

This was meant as a reply in /. about lag in Android durin gaming.

The lags are there, because there are processes in the background doing something.

• Switch off all other running tasks.
• Check the services running in the background, and all the currently running processes to find out, what's going on.
• Switch off the animated main screen background image, and replace it with a still one.

The two things always causing mayhem during normal phone operations, were and are Google Play Services and Google Play Store apps automatically updating in the background at the expense of everything else. There is no notification or wait-until-idle-and-then-some period. On many occasions, I just had to wait until the phone was responsive again, and when checking in settings for apps, the version numbers of these two apps had been bumped up.

Another culprit is synchronisation — of all your data, and especially the sync of all your photos. Switch off sync in almost all the apps you have. Except maybe Google Play, because without sync for that turned on, the Google Play app won't be able to access the store under you account.

A small ARM primer

Android devices' CPUs are by and large ARM microprocessors, as these were chosen for their low-power features.

The ARM family consists of different architectures, each of which is named ARMvX, where v stands for 'version', and X is the architecture version number.

CPU architectures can be incompatible with one another, as each have different instruction sets, and programs made for one architecture won't run on the other (or there's a heavy performance penalty).

Most Android device CPUs are based on ARMv7-A (usually shortened to ARMv7) or greater, but a bevy of older devices have ARMv6.

Consequently, not all Android device CPUs are based on ARMv7 or greater, and that's why it's important to pay attention to which architecture an app was compiled for.

ARMv7 is subdivided into a series of architecture profiles, of which Android devices use ARMv7-A (Application profile). The ARMv7-A grouping is also known as Cortex-A.

A deeper subdivision in each architecture is a core, and these are named differently. Cores within the same architecture are mostly compatible between one another, but differ in performance.

Each device manufacturer or maintainer of a compatible Android fork makes their own compilation of the operating system; first for a particular architecture, and then optimised for each processor type, graphics adapter (GPU), and other hardware features.

I'm specifically pointing cores out because of naming similarities between cores and architectures; for example, ARMv7 should not be confused with ARM Cortex-A7, since the former is an architecture, and the latter a core that uses said architecture.

Respectively, ARM11 is the microprocessor core using the ARMv6 architecture; as ARM Cortex-A5 and ARM Cortex-A7 are under ARMv7.

Postimees ja vana Android

See on (algselt kiirena kirjutatud) täiendus varasemale postitusele, mis kritiseeris Postimees Online (edaspidi PMO) uue mobiiliversiooni kasutatavust, kus peamiseid kriitikanooli sai sisu liigtihe automaatne uuestilaadimine.

Üldse, kui sinu hallata on suure levikuga veebileht, siis üks suuremaid vigu on [kogu] lehekülje sisu automaatne uuestilaadimine, sest kasutaja pole seda ise soovinud, ning mobiiliseadmetes kulutab see akut.

Antud blogipostitus on mõeldud kõigile neile inimestele, kelle mobiiliseade (telefon või tahvelarvuti) on varustatud Android 2.3 "Gingerbread" opsüsteemiga, mida pole võimalik uuendada, ning mille vaikimisi lehitseja on liiga vana ja aegunud, et oleks võimalik Postimehe veebilehelt mugavalt uudiseid lugeda. Või üldse.

Ehkki seesinase fookus on Postimehe koduleht, võimaldavad allpool pakutud lahendused laiemalt külastada teisigi kaasaegseid Interneti-lehekülgi, mis Androidi (2.3 ja vanemate) vaikimisi lehitsejas ei näita või pole enam toetatud.

Juhised nõuavad mõnetist tehnika-alast oskust, kuid leian, et instruktsioonides ei tohiks midagi väga keerulist olla.

Probleemid:
* Android 2.3 on vana ja Postimehe enda äpp võib-olla näitab, võib-olla mitte, aga tegemist on äpiümbrisega (wrapperiga), mis põhimõtteliselt näitab Postimehe kodulehte sisseehitatud vaikimisi veebimootoriga. Postimehe äppi pole tegelikult vaja.
* Android 2.3-s vaikimisi lehitseja on liiga vana, et kogu seda sisu adekvaatselt näidata, sest selle lehitseja umbes viis aastat vana veebimootor on lootusetult aegunud.

Mida teha:
* Tõmmata peale Firefox Androidile.

ARMv7l protsessoriarhitektuuril käiatava Android 2.3 jaoks on kõige uuem Firefoxi versioon 47.0; selle eestikeelse variandi saab tõmmata Mozilla FTP lehelt või Google Play Poest.

Mozilla enam ei arenda Android 2.3 jaoks Firefox-i, nii et Google Play Poes võib Firefox olla vabalt märgitud kui ühildumatu. Siis tuleb tõmmata Firefoxi APK-installer eraldi Mozilla FTP-lehelt ja enne selle installimist lubada ajutiseks Androidi seadetes kolmandatest allikatest installimise võimalus ehk mitte-Marketist/Play Poest.

Asja parem külg on see, et vanale mobiili-opsüsteemile siiski on saadaval modernne lehitseja, millega saab vaadata kaasaegseid veebilehti.

* Et PMO mobiiliversiooni sisu laeb liiga tihti, tuleb kasutada PMO töölaua-versiooni. Viimases töötab siis ka artiklite kommentaaride hindamise funktsioon. Ehkki Firefoxi äpi-menüüst on võimalik valida "Töölaua-versioon", tekib ikkagi kaks probleemi:
** PMO lehtede jaoks tuleb Firefoxi töölaua-vaadet valida menüüst iga kord peale Firefoxi käivitamist või peale lehitsejas uue vahekaardi avamist.
** Teiseks on PMO töölaua-versiooni küljendus mõeldud töölauale, aga kunagi töötas see väga ilusti mobiiliversioonina. Vaadet on võimalik näppudega suurendada. Need liigutused on tüütud ja ajakulukad.

Lahendused:
1. Oletades, et sinu Firefoxi versioon on 47.0 (nagu üleval kirjas, Android 2.3-le kõige hiljutisem), jäta allolev vahele ja mine edasi järgmisele punktile.

Kui sa oma Firefoxi versiooni ei tea, otsi see üles: Lähed Firefoxis about: lehele, kus see kribukirjas näha on. Jäta see versioon meelde; tähtis on see kujul 47.0 (täisarv-punkt-null).

Ise kasutan Firefoxil põhinevat IseCat lehitsejat; Android 2.3-le on IceCat-i uusim versioon 38.8.0.

2. Edasi tuleb minna aadressiriba kaudu lehele about:config — seal on kõik Firefoxi tähtsamad seaded, mis on käsitsi seatavad;
1.1 puutuda seal suurt pluss-märki ja kirjutada nimelahtrisse

general.useragent.override.postimees.ee

1.2 Puutuda nuppu "tõeväärtus", vali "string"
1.3 "Sisesta string" lahtris lisa järgmine user-agent string (lehitseja versioon, mille lehitseja saadab seatud leheküljele, antud juhul postimees.ee) —

Mozilla/5.0 (X11; Linux armv7l; rv:47.0) Gecko/47.0 Firefox 47.0

Kui telefonis on Android 2.2, või kui telefonis ka on Android 2.3, aga protsessoriarhitektuur ARMv6, siis nende jaoks on uusim Firefox hoopis versioon 31.3.0esr. Siis peaks kasutajastring olema selline:

Mozilla/5.0 (X11; Linux armv6; rv:31.0) Gecko/31.0 Firefox 31.0

1.4 Olles sobiva kasutajastringi sisestanud, vajuta nupule "Loo".

Antud string kehtib ainult Firefox 47.0 kohta. Kui sinu Firefoxi versioon on erinev, peaksid lisama selle, mis sul on.

Kogu see tegevus seab postimees.ee domeenile töölaua-põhise lehitsejastringi (i.k. user-agent string) nii, et Postimehe koduleht saadab Firefoxi-mobiililehitsejale töölaua-versiooni.

Ülal väljatoodud kasutajastringis tähendab näiteks X11 Unix-põhiste opsüsteemide graafilist keskkonda, Linux tähistab opsüsteemi nime (sh samanimelist kernelit, mis on Androidis sees), armv7l mobiiliseadme keskprotsessori tüüpi, rv: ja Gecko tähistavad Gecko veebimootori (mida kasutavad Firefox, IceCat jt lehitsejad) versiooni, selle järel lehitseja enda nimi (siin vastavalt Firefox) ja versioon.

3. Aga see pole veel kõik, sest Postimehe töölaua-versioon mobiilis ju päris korralikult ei näita, sest pisikesel ekraanil on töölauaversioon liiga lai, tekst liiga väike, ning tuleks liiga palju suurendada.

Et vähemalt enda jaoks probleemi kiiresti lahendada, tegin järgmist:

Installisin Firefoxile laienduse nimega Stylish. Sellega on võimalik muuta lehitsejas näidatavate lehekülgede välimust läbi mobiiliseadmesse tõmmatud kasutajastiilide (i.k. userstyles).

Stylish laiendus töötab nii, et lehitseja tõmbab mõne lehekülje kasutaja seadmesse ja seejärel rakendab Stylish leheküljele seatud kasutajastiilis oleva küljenduse. Lehekülje originaalvälimus jääb lähtekohas ikka samaks, st. kogu see välimuse muutmise protsess toimub ainult kasutaja seadmes, kui kasutaja on mõnele lehekülje mugavama kasutamise tarvis tõmmanud kasutajastiili.

Edasi veetsin selle aasta kevadel mitu ööd ja päeva uurides töölaua-Firefoxi arendajatööriistade abil Postimehe lähtekoodi ja kirjutasin oma stiililehe, et nö tagasi saada mobiilide jaoks mõeldud klassikaline välimus.

Et kõik teisedki inimesed saaksid seda stiililehte kasutada, panin kasutajastiili üles GitHubi:

https://github.com/juneyourtech/GM_PM/raw/master/PM_mobile_classic.css

1. Kopeerida ülalolev aadress.
2. Firefoxis minna läbi Lisade lehekülje Stylish alamlehele: Menüü [> Veel >] Lisad > Stylish;
3. Vajuta "Halda stiile" nupule;
4. Vajuta nupule "Install from URLs", aseta tekstiväljale ülalolev kopeeritud aadress. Vajuta Sobib/OK, kirjuta lisaks stiili nimi.
5. Postimehe töölaua-versioon peaks sestpeale olema nähtav mobiilidele sobilikul kujul.
6. Edaspidi tuleks eelistada Postimehe www-aadressi kujul www.postimees.ee

Ei garanteeri, et see kasutajastiil töötab kõigi peamiste Postimehe alamlehtedega (eriti Ilmajaam).

Reklaame see kasutajastiil otseselt ei blokeeri, kuid üldiselt olen lähtunud sellest, et Firefoxile Androidil on peale installitud skripte blokeeriv NoScript Anywhere laiendus, milles on antud postituse teemat silmas pidades lubatud peamiselt postimees.ee ja pmo.ee domeenid.

Tavalisest reklaamiblokeerijast, nagu Adblock Plus vms., on NoScript mitu korda efektiivsem ja vähem ressursinõudlik; leheküljed laevad kiiremini, ning selles oleva valge nimekirja abil on lubatud ainult need domeenid/võrgulehed, mida vaja.

Inimestele läheb korda telefoni või tahvelarvuti akutarve. Skriptide blokeerimine lehitsejas säästab nii aega, akut, ning mobiil-Interneti kasutajatel ka raha.

Läbides kõik need sammud ongi võimalik Android 2.3 opsüsteemis saada endale võimalus normaalselt lugeda Postimehe uudiseid ja hinnata artiklite kommentaare.

---

Veidi ajaloost:

Valmistehtud stiililehe esialgne tulemus oli rahuldav, kuid alguses ei olnud mul veel õiget lahendust, mille abil olnuks võimalik PMO töölauaversiooni probleemivabalt kätte saada, isegi kui teatud olukordades paistis disain töötavat.

Hiliskevadel või suvel tõmbasin eksperimenteerimise käigus peale Firefoxil põhineva GNU IceCat lehitseja, millel pooljuhuslikult avastasin kasutajastringi muutmise võimaluse, ning ka selle, et erinevat kasutajastringi on võimalik seadistada erinevatele saitidele.

Sügisel avastasin lõpuks, et ka Firefox toetab sama funktsionaalsust; lihtsalt on see about:config lehel iseenesest mitteeksisteeriv ja user-agent string tuleb ise lisada.

Useful apps exclusive to Android

This is a copy of a comment I wrote in a YouTube discussion to someone who recommended that "[I] get an iPhone".

I've formatted and edited the comment with some additions into this blogpost. While it does harken back to a previous post I wrote about reducing one's Android's resource usage, then this one is more about some of the useful apps I use that are exclusive to Android.

An iPhone or any new smartphone is beyond my means, and I wouldn't be able to run some specific apps only available on Android, such as:

• Adblock Plus for Android. Works only on Wi-Fi, but blocks in-app ads;
   
• Firefox for Android. It's got Reader Mode, which saves an article, only keeps relevant article content, and allows white-on-black reading.
  
  Firefox extensions, which only run on Firefox-based mobile browsers:
  • NoScript Anywhere — blocks scripts and trackers run by scripts, and thus reduces browser resource usage. Its whitelist allows running scripts on sites I whitelist through the NoScript menu in Firefox;
  • Privacy Settings — allows users to switch off a number of default Firefox settings to make the browser less resource-hungry and more secure;
  • Stylish — allows users to locally change the appearance of webpages displayed in a browser (make them dark, etc. to save battery life). People can download or make their own userstyles.
  • Save Link Menus — allows saving links or webpages from Firefox to the local file system.
  
  
• Vim Touch — a very advanced text editor. This adds to productivity (I can create and edit content);
• Hacker's Keyboard — I need this to use VimTouch, to easily navigate in text, and to quickly switch between languages without going to settings every time. This keyboard app is very lightweight compared to most native virtual keyboards;
• Unicode Map — to search for, view, and copy Unicode characters;
• VLC Media Player. 'Nuff said;
• Arity — a scientific calculator, but I sometimes use it to calculate expenses when shopping for multiple things with a limited budget.
  

There some other apps with functionality not particularly unique to any mobile ecosystem:

• Sparse RSS — to subscribe to podcasts;
• Units — a very nice unit converter;
• MuPDF — a lightweight viewer for PDF, OpenXPS and CBZ files;

The above apps are all Free / Open Source Software (FOSS), and available at the F-Droid app repository.

Stock app —
• FM Radio. I can listen to plain FM radio and listen to great music for free and without ads. Estonia's public broadcaster ERR is just that awesome. They even provide small "what's playing" pages, so I can check out the artist and song.
  
  FM radio functionality is not on most iPhone models, and not on most Windows phones either. My phone even supports RDS.
  
  
Some proprietary apps:
• TeamViewer — I sometimes do computer support for friends and relatives;
• The local weather widget.

---

This post is licensed under CC-BY-SA-3.0.

File attachments in Android 2.3 and GMail

This post is about how to add attachments in GMail in Android 2.3.x from the file system.

Granted, many people are stuck with Android 2.3.x, so the post is specific to that branch of Android.

GMail app

This happened to me with the GMail app version 2.3.6 in Android 2.3.6 on a lower-end Samsung phone.

A few days ago (that was around 17.05.2015) I was trying to send two crash log files of a different app to its developer via Android's GMail app, and for some reason, sending the e-mail didn't work. I don't quite know why, and I lost the e-mail. One attachment was relatively small, and another was around 860 Kb (a bit large in some respects). I haven't investigated this issue online.

A day later, putting attachments in an e-mail in the Android GMail app and seeing that same letter as a draft in GMail on the web did work:
• If you insert attachments first in the GMail app, then do write some text into the message area, which unblocks the save-as-draft button; save the letter as draft and sync.

I haven't investigated how to do that in a browser in GMail, given that the GMail app method worked out for me.

Android telefoniga mobiil-Interneti jagamine läbi Wi-Fi

Seadmete opsüsteemid:
• Samsungi telefonis Android 2.3.6 (eestikeelse kasutajaliidesega);
• arvutil Windows XP SP3, mis on ingliskeelse kasutajaliidese ja Windowsi enda Wi-Fi tööriistadega ühendumiseks.
• Mida teha, kui arvutil on ThinkVantage Access Connections

Artikkel eeldab juba nii Androidi-nutitelefoni kui ka Windowsi kasutamise oskust teataval tasemel.

Niisiis selgus kõige alguses, et nutitelefonis peab Wi-Fi ise samal ajal välja lülitatud olema.

Kõigepealt tuleb kindlaks teha, et mobiil-Interneti võrguseaded on enam-vähem korras:

Seaded  
• Juhtmevaba võrk ja võrk >
  • Mobiilsidevõrgud >
    Pääsupunktide nimed >
    • Elisa:
      (•) internet.elisa.ee
      wap.elisa.ee või mms.elisa.ee vms asemel.
       
    • EMT:
      (•) internet.emt.ee
      wap.emt.ee või wap2.emt.ee või mms.emt.ee asemel.
      Android nutitelefon võimaldab kasutada nii tavalisi Interneti-lehekülgi kui ka lehitseda wap-lehtedel. Nendel juhtudel, kus mobiiliteenuse paketis on mobiil-Internetile mahupiirangud, mille ületamisel tuleb oluliselt rohkem maksta, on wap-lehtedel lehitsemine odavam. Soodsa paketita kõnekaardi omanikele Android-nutitelefonis mobiil-andmeside ei soovita, kuna paljud teenused ja programmid soovivad automaatselt ühenduda ja kohe andmeid vahetada. Niisugused kõnekaardid sobivad rohkem WAP-lehitsejatega funktsioonitelefonidesse (sh Nokia mitte-Windows nutitelefonid), millega on oluliselt kergem oma Internetiliiklust reguleerida.

Edasi tuleb seadistada Wi-Fi hotspoti (Android 2.3.6-s värdsõna "kuumkoht") juurdepääsupunkt (AP ehk access point) —

Seaded  
• Juhtmevaba võrk ja võrk >
  • Modem ja kaasaskantav kuumkoht >
    • Konfig. kaasask. Wifi kuumkohta >
      Võrgu SSID (nimi, mille järgi leiad võrgu üles)
      [Kirjuta oma võrgu nimi. Lubatud on numbrid 0-9 ja tähed A-Z, a-z, sidekriips - ja allkriips _]
      Turvalisus
      Vali [WPA2-PSK]
      Parool
      [Kirjuta tühikuteta vähemalt 8 tähemärki, lubatud on numbrid 0-9 ja tähed a-z (küll mitte suurtähed)]
      [\/] Näita parooli
      — on valik näidata võrguparooli, mille võib Windowsi Notepadis üles kirjutada ja kohe mällu kopeerida (Ctrl+C).
      Vajuta [Salv.] nupule
       

Siiski otsustasin, et enne hotspoti aktiveerimist oleks kasulik mobiilivõrk (pakettandmeside) enne sisse lülitada (võib ka tagurpidi) —

Seaded  
• Juhtmevaba võrk ja võrk >
  • Mobiilsidevõrgud >
    • Kasuta pakettandmeside [\/]
      — Kui seda parasjagu vaja pole, ei pea see sees olema.

Nüüd aktiveeri hotspot:

Seaded  
• Juhtmevaba võrk ja võrk >
  • Modem ja kaasaskantav kuumkoht >
    • Kaasaskantav Wi-Fi kuumkoht [\/]
      Windowsis otsi Wi-fi võrk ja leia oma võrgu SSID. Vali see ja ühendu.
      Võrguga Ühendumiseks küsib Windows võrguparooli, tihtipeale kahe sisestusväljaga samas dialoogiaknas.
      Sisesta seesama võrguparool, mille oma Wi-Fi võrgu tarvis. Kui tuleb teine väli, siis sinna sama parool uuesti.
      Üleskirjutatud parooli saab kopeerida ja asetada (kleepida) võrguparooli väljale (Ctrl+V).

Ühendumine siis, kui Wi-Fi tööriistaks on ThinkVantage Access Connections

Tingimusteks Windows XP SP3 ja ThinkVantage Access Connections 6.01 (2013, ingliskeelne).

ThinkVantage Access Connections on suurepärane võrguühenduste haldamise programm, mille algselt arendas välja IBM, ning mille arendamist jätkab Lenovo. Access Connectionsi eelis on põhjalik seadistatavus, võimalus luua ja hallata asukohaprofiile ning neid eksportida ja importida ühest arvutist teise. Lisaks kergendab see võrguühenduste haldamist, eriti kui kasutusel on erinevad Windowsi opsüsteemid (XP, Vista, 7, 8, 8.1).

Niisiis järgnev eeldab, et arvuti peamiseks võrguühenduste haldajaks on Windowsi enda asemel ThinkVantage Access Connections (tavaliselt ingliskeelne), mis tuleb kaasa peamiselt ThinkPad sülearvutitega, aga võib-olla ka teiste Lenovo sülearvutitega. Teine eeldus on see, et näiteks kui on Inteli Wi-Fi adapter, siis Inteli Wi-Fi tarkvara ei ole aktiivne ja on maha installitud, kuid adapteri draiverid alles.

Kui hotspotiga nutitelefonil on kõik muud tingimused edukalt täidetud, siis üldine probleem on see, et ThinkVantage Access Connections programmiga ei ole võimalik peale võrguparooli sisestamist Interneti-ühendust saada.

Access Connections on küll palju funktsionaalsem, kuid teatud olukordades mitte nii paindlik kui Windowsi enda võrguhaldustööriistad.

Et kui juba läbi Access Connectionsi oli alguses püütud ühendust võtta, siis Access Connections on juba salvestanud asukohaprofiili, mis kannab mobiiltelefoni AP (access point-i) nimetust. Antud Access Connectionsi versiooniga (6.01) miskipärast ei õnnestunud toimetada äsjaloodud asukohaprofiili, millega ei saanud ühendust (selle ühenduse valiku puhul oli Edit-nupp tuhm). Seega äsjaloodud edutu asukohaprofiil tuli kustutada; Access Connectionsis on sellisel juhul efektiivsem käsitsi uue asukohaprofiili tegemine.

Lahendus seisneb selles, et Wi-Fi seadetes peab konkreetse ühenduse krüpteerimine olema AES ja mitte TKIP.

Kui avada Access Connections põhiaken (tegumiriba märkuste alal must arvuti, mille all juhtmed), siis minna Location Profiles (asukohaprofiilid) vahekaardile, millel ilmub asukohaprofiilide nimekiri.

Eeldusel, et vana ja mittetoimetatav asukohaprofiil on juba kustutatud ning käsitsi uuesti loodud, tuleb seadetes suhteliselt hoolikalt näpuga järge ajada.

Kui Location Profiles vahekaardi nimistus on leitud telefoni AP, valida asukohaprofiil ja klikkida Edit nupule. See kehtib siis asukohaprofiili kohta, mis on saanud eduka ühenduse ja mida saab toimetada.

Aknas Edit Profile: (asukohaprofiili nimi) valida "Wireless Settings" vahekaart.

Et kõik oleks kindel, siis ühenduse tüüp (Connection type) peab olema infrastruktuur (Infrastructure), "Wireless mode" on tavaliselt "Auto". Teisi seadeid (v.a. allolevad) tavaliselt muuta pole vaja.

Kui AP juhtmevabaks turvastandardiks on telefonis valitud WPA2-PSK (Android 2.3.6-s ainuke turvaline valik), siis Access Connections telefoni-wifi asukohaprofiili Wireless Settings vahekaardil on allatulev menüü "Wireless Security Type", kus valida
"Use Wi-Fi Protected Access - Pre Shared Key (WPA-PSK)". Lisaks klikkida Properties nupule, mille järel tuleb ette "Wi-Fi Settings" aken. Seal on järgmised võimalused:
• Access point authentication, kus valitud peab olema WPA2-PSK
• Data encryption: — Valitud peab saama AES ja mitte TKIP.
• Pre-shared key on "Use 8-63 alphanumeric characters (0-9, a-z)"
• Edasi vajadusel sisestada uuesti võrguparool ja vajutada OK.

"Edit Profile" akna "Additional Settings" (täiendavad seaded) vahekaardil on tavaliselt linnuke
\/ Network security juures. Kui vajutada [Settings...] nupule, siis vastutustundlikul kasutajal on tavaliselt välja lülitatud failide ja printerite jagamine, Interneti-ühenduse jagamine, ning sisse on lülitatud Windowsi tulemüür.

Tablet history reflecting early personal computer history

The situation with tablets that I currently observe somehow resembles the personal computer history throughout 1980's and early 1990's, when there were many often mutually incompatible solutions, of which only a few really survived into the current era (I know the word 'survive' can be inaccurate and maybe even corny). Here what I had in mind were the IBM PC & compatibles, the Apple and Mac series, Power-based computers with OS/2, Amigas, Ataris, BeOS and a few others, even Next. Each tried with their own ecosystem and I see the same happening with iOS, Android, WinMo, WebOS, and MeeGo (other ecosystem names for tablets escape me right now).

The 1980's species that did not survive or only got a niche footing, were Amigas and Ataris, and OS/2 to some extent, as these computer ecosystems either failed to have enough popular application software to garner widespread appreciation and acceptance going forward or their development was stopped. NeXT was downright expensive, but it became the first-ever web server (working at CERN must have its perks :-).

I have been trying draw the same parallels with today's tablet platforms, whereby:

• From the developer standpoint, the iOS is a bit like OS/2, as software development APIs for OS/2 were not free of charge, if memory serves me right (this was SOP for some other manufacturers' developer kits, too. Most ironically, OS/2 outlived Windows 9x in terms of available free software), and so iOS also has restrictions on developing for it;
• Android, therefore, offers more latitude, like Windows did at the time, and is just as well plagued by viruses.
  Furthermore, Android, being half-open, sees itself right now in waters similar to BSDi.
• WebOS... The most similarities with an older system that strike me wrt WebOS are with Atari ST, because Atari released their ST series computers to much acclaim and then suddenly stopped developing them.