mindstalk: (Homura)
I've gotten emergency alerts on my phone before, but always at home. Today I'd met Erik-from-Australia at Charlie's Kitchen, and at some point my phone started buzzing. I quickly shushed it, thus discovering that alerts aren't like text messages, you can't find them again after dismissing them, but I did catch "flash flood". What really struck me was that lots of other phones were doing the same thing, a rather surreal experience. Erik says the TV dipped in volume for a few seconds too, though from my own memory I couldn't tell you that there was a TV to have a volume. His phone did not go off, leaving him going "what? what?"; it did report a couple of alerts later, that mine didn't. Neither of us have a Boston area code, though I do have a local billing address; I also have Android vs. his iPhone, which is my leading hypothesis for the different alert behavior. A carrier difference could apply as well.

I fear no flooding personally. But I met him dressed for 24 C, and it's dropped to 12. Even I find more layers desirable when it's 12 and rainy and *windy*.
mindstalk: (robot)
It's been a bad week for the devices of my household. Well, my N900 smartphone has been having growing trouble for the past few months, but recently it pretty much lost all ability to reliably keep a data connection up, especially for SSH. (Web seemed to do better for a while.) Then it was having more and more trouble with even voice; more and more I'd get a message like "General connection error, even emergency calls won't work, try rebooting". I've given up and moved my SIM card to my 2005 $50 Nokia 6110 ("the Indestructible"), so I'm missing 3/4 of my contacts and texting sucks... even the 9 year old battery holds useful charge way longer, though. The N900's wifi still works fine, so it's become my bedside wee hours computer.

This of course leads to "Operation: Buy A New Smartphone", which would be a lot easier if anyone made what I want. Physical keyboard, removable battery, expandable storage, up to date, Android or even freer but reliable and competent OS -- nope, does not exist. Dropping the keyboard seems to mean "Samsung" these days, with new problems of "costs a lot" and "possible Samsung bloatware and slow updates". The Galaxy S4 has a Google Play (pure Android version) which would be good except it's still $649, about as much as a regular Galaxy S5. But you can burn on Android stock ROMs yourself, apparently, or just skip over to Cyanogen, so I'm thinking of an S4. Or going back a generation to the S III, though that's still not trivially cheap. Or else selling out and getting a Nexus 5. The OnePlus One sounds fairly attractive but it's unclear when it'll even come out, let alone how problem free it'll be.

The Oppo N1 comes with a Cyanogen installer, which is cute, but it's a $600+ phone that doesn't even have LTE.

Versus the Nexus, the S4 does seem to have a better screen and camera, plus a few more sensors; I'm waiting for phone to fully turn into tricorders. I'm still not sure if all that plus the batter/storage is worth $2-300. I did note that I'm only using 19G of the 48G on my N900, so fitting into 32G shouldn't be too hard. I am amused that phone are just catching up with the N900's storage options from 2009. (32G internal, 16G microSD card. Actually things with cards go up to 64 or even 128 now.)

***

Right, other electronics. So I'd let my Ubuntu 12.10 laptop fall behind on updates, and finally caught it up. After which the sound wasn't working, the touchpad(!!!) wasn't working, and the wifi wasn't working. I get messages about various sound devices being removed. I tried full system update, that fails with errors. I think I need a clean install. Safest would probably be to revert to 12.04, since I know that works. Conventional would be 14.04. I'm thinking of flipping off Ubuntu and going with Arch and learning more about how my system works, though the Arch installation guide assumes I know a bunch of things I don't, mostly about formatting.

So I'm using my eee 901 again, with its eeebuntu 10.04. Shocking to again have a version of Gnome that doesn't suck. It's slow and small and has almost on no space after downloading the Arch ISO. But lightweight!
mindstalk: (Default)
I have an account, and $8 of credit. I'd try calling someone but I'd probably croak on the phone. Should I bother getting a Skype number? I know at least a couple of you have Skype, how do you tend to use it?

Also, how the hell did western Massachusetts get the 413 area code, when eastern/Boston had 617? I'm sure a jillion more people live in/around Boston.
mindstalk: (angry sky)
Remember all those problems I've had with my Nokia N900? That probably convinced everyone reading not to get one? I think I've found the problem, and it's mostly not Nokia, or even unstable apps, but my own shell aliases.

See, I use the command shell. And use aliases to make things go better. In fact I have a big file I share around all my accounts. It's never had problems before... but after detective work I won't describe, I found that having it automatically loaded (e.g. .profile of "source etc/aliases", me having my own etc subdir) broke boot. And of all those aliases, removing only one prevented the lack of booting:

alias '.'='pwd'

which makes a simple dot act as a "print working directory" command, instead of the "load file" command it naturally is. Not that I've used it in either form, it's a really old legacy. But I have to assume that the oddity of the phone -- which boots you directly into your userspace, no login screen, plus it's using some weird heavily pruned version of the Unix shell, 'ash' only maybe even less so, means that there's some process during boot where my shell gets started and it goes through startup scripts trying to use '.' to read in other files only these are happening after my .profile and therefore they break and the boot never finishes.

Which I can still grumble about; if this thing were presenting itself as a proper handheld Linux machine, there'd be a login screen, and options for safe-boot in case you messed up, and more of an error output. Things shouldn't be this fragile.

I also can't be 100% certain that this was the only culprit; installing in-development apps might still be stupid. I just know it is a reproducible culprit, one likely to have been involved in all prior cases.

So I guess the lesson is the N900 is probably quite usable, unless you re-program key shell functionalities in an overly aggressive login process.

Profile

mindstalk: (Default)
mindstalk

January 2026

S M T W T F S
    1 23
45678910
11121314151617
18192021222324
25262728293031

Most Popular Tags

Expand Cut Tags

No cut tags

Syndicate

RSS Atom

Style Credit

Page generated 2026-01-03 07:47
Powered by Dreamwidth Studios