Its one of those things which I wasn’t happy about with my Pixel4. Who on earth over looked the fact you could use the face unlock without your eyes open! It doesn’t take a lot to think about the abuses including spouses with trust issues.
It was the first thing I did when I installed the update. Till that point I’ve been enabling lockdown mode when going through sensitive areas like airport security
Why did you create this Eelo or /e/ project in the first place?
Gael: In 2017, I realized that using Android and iPhone, Google and many mobile apps was not compatible with my personal privacy.
A later study by a US University confirmed this: using an iPhone or and Android phone sends between 6 to 12 MB of personal data to Google servers, daily! And this doesn’t count mobile apps.
So I looked for reasonable alternatives to iPhone and Android phones but didn’t find any. Either I found options for hobbyists, like Ubuntu Touch, that were not compatible with existing apps and not fully unGoogled either. Or there were alternative ROMs with all the Google fat inside, and no associated basic online services that could be used without tweaking the system.
Therefore, an idea came to mind: why not fork Android, remove all the Google features, even low level, such as connectivity check, DNS…, replace default apps with more virtuous apps, add basic online services, and integrate all this into a consistent form that could be used by Mum and Dad and any people without tech or expert knowledge?
I’d be interesting in what apps run on the operating system, as Google really have embedded Play services into everything now. When I first got my recent e-reader, it came with its own app store till you enable play services. That store was super small but it doesn’t have to be that way if you look at F-droid for example.
If I still had my Nexus 5x, I would likely give /e/os a try. I could run it on my Nexus 5 I guess but the screen is maybe too broken.
I have been thinking, following my use of Firefox multiple account containers use. Maybe something of a mashup of Blackberry’s Android profiles (anyone remember this?) and Firefox containers.
This certainly feels like a design challenge which could be massively beneficial to many, and showcase the beauty of opensource
Well I liked my energy sistem as it was my very first android eink reader and fore-filled almost everything I was wishing for in a ereader. Its a great device but I found my reading habits changing. I mainly consume longer media content via audio or video rather than textual. I like text for reference, storage, retrieval and share ability. But my consumption was mainly aural. The Enegry sistem has no audio support at all, meaning I would use my phone for audio and occasionally look at the eink screen.
If I could have a ereader with audio too, that would be great for syncing and keep a track of things. Hence when I saw the Likebook (yeah I think its a silly name too) I consider it and bought it a few months later. Of course I’m selling my old ereader on ebay if interested.
After my research I knew I could do everything my previous one could do but also with the updated Android 6 operating system and more power might be able to run some apps which didn’t install or run previously. Its a very good device and the audio is spot on with my bluetooth headphones and a fallback analogue audio jack. At first I had some difficulty getting the google play store working but before I checked out the tutorials, I stumbled on the right settings, logged in and that was that.
The next problem wasn’t to do with the ereader but wallabag, which returned a error every time I synced. Finally after exporting then deleting a lot of archived pieces. This took a long time to diagnose and get sorted hence the long silence during the start of December on this blog.
Finally its all running correctly and I have almost everything on it.
I really like the fact there is now a lock screen because the previous one didn’t and I had to restrict a lot of its operations just incase. For example I disabled Gmail & Gdrive on it just incase. I know some of you will scream its running Android 6, so its game over anyway. But the previous one was running Android 4! I have taken care with the likebook but feel better about drivebys (as such). The amount of internal memory really helps as I can now stick ebooks and audiobooks on the same drive. Theres also a SD slot if more memory is ever needed. I can even put my VPN apps on it which is fantastic news.
Its a good device and now its settling down to its weeks of battery life after all the wallabag syncing.
The only thing I miss really is the size of the device is 7.8 inches instead of 7 inches which makes it too big for my pockets including my jacket pocket. Weirdly enough, it almost fits in my headphones pouch, providing some protection from scratches in my laptop bag.
I like it so far… not quite over the mars about it but its growing on me.
I found this from Android Authority pretty good, I turned off 90hz display on my Google Pixel 4 ages from day one to help with the battery life. Its likely my good eyes would tell the difference but is it worth more than the battery life of the phone?
I think not… of course the comments begs to differ…
When playing Stadia on my Windows PC through the Chrome browser at 720p, Stadia used between 12 and 20Mbps. In contrast, a Netflix stream used about the same amount, but Netflix can buffer content to stop streaming constantly. Because Stadia is always pulling data and can’t buffer, it will use a lot more data.
You could technically use Stadia connected to a mobile hotspot, but I’d strongly advise against it if you have a limited data plan. Playing Stadia at 720p used about 7GB per hour.
Don’t expect to be playing Stadia at your local coffee shop without some comments or a lot of lag. I wonder if most of the cheap routers can sustain bandwidth like that anyway?
What’s the difference between a hybrid smartwatch and a regular smartwatch? In the hybrid category, Fossil’s Hybrid HR mixes physical watch hands with an always-on display that shows information and notifications. It almost feels like an old-school Pebble watch fused with an everyday analog-style watch.
I always swear by eink for these type of things, and I’m happy to hear its using eink too.
Keeping a smartwatch charged is incredibly annoying. Fossil’s newest line of hybrid smartwatches may have found an answer, and it’s E Ink. The Hybrid HR’s added display feels less like a screen and more of an extension of the watch, the sort of basic readouts that you might expect on a digital watch. Or, like what Google’s Wear OS watches offer, but in E Ink. To be clear, though, this isn’t Wear OS. It almost reminds me of what the TicWatch Pro tried for by layering an always-on display on top of a feature-packed smartwatch, but the Hybrid HR looks a lot nicer.
Earlier this year, Google reportedly paid $40 million for Fossil smartwatch technology that could enable hybrid watches. The Hybrid HR looks like it is, indeed, the watch tech that earlier reports thought Google was interested in… and it’s here now.
I will be keeping en eye on this category, because although I like the Hybrid HR, I’m not so keen on round faces and I’d need to get a sense if theres sleep tracking support? Or more so if theres going to be a standard for watch apps like WearOS and the Pebble OS.
What follows was a long painful process trying to pair the Pebble 2 with my Pixel 2 phone. It took forever and ended up with me unpairing both rebooting both and repairing the whole lot again. Nothing was lost in the process but its a real painful process and I thought, once its done, its done forever.
However I was wrong. It seems like this happens every few weeks? Others have suggested it happens when the Pixel doesn’t see the pebble for a little while. Someone started a bug issue with Google, thankfully and I added my own comment to the growing list.
The ring is very good, but the app isn’t the best, its seems to work but isn’t very clear when its not syncing with the ring. Also I knew the 2 day battery was going to be a pain but to date I’ve been charging it every 2 days and never got to the point where its gotten below 44%.
As the app is pretty rubbish, I have sent everything to Google fit. I pretty much have everything synced with Google fit now.
The first time I noticed it was all working, was when I looked at sleep as android which I use with my pebble smartwatch and noticed my heart rate over the top of my sleep data.
I warn you the sleep is a mess due to my flu I currently have… also why I’ve not blogged those great conferences I’ve been to recently.
Likewise I recently hooked up my Withings/Nokia iot scale to Google fit. The scale has its own app which isn’t bad but frankly its not great. It suffers from the similar problems as most of the quantified apps attached to a device or service; they want to be the centre of the world. Reminds me of my Fitbit which import everything but export little.
I understand Google fit is mining the heck out of my quantified data but with Google takeout, I can get the raw numbers in one place. Everyone wants to sync with Google fit and the dashboard view is far better than what everyone else right now.
I’ve also set it up to send me an update every 2 months. Now that’s pretty neat. Would I pay for a service to do this? Yes I would, how much is the question…
I was sure I tooted/tweet a thank you to the Google team in Berlin’s Re:publica conference. But it looks like it never quite happened due to connectivity issues with the wifi at certain points of the day.
Due to a misconfiguration in the Titan Security Keys’ Bluetooth pairing protocols, it is possible for an attacker who is physically close to you at the moment you use your security key — within approximately 30 feet — to (a) communicate with your security key, or (b) communicate with the device to which your key is paired. In order for the misconfiguration to be exploited, an attacker would have to align a series of events in close coordination:
When you’re trying to sign into an account on your device, you are normally asked to press the button on your BLE security key to activate it. An attacker in close physical proximity at that moment in time can potentially connect their own device to your affected security key before your own device connects. In this set of circumstances, the attacker could sign into your account using their own device if the attacker somehow already obtained your username and password and could time these events exactly.
Before you can use your security key, it must be paired to your device. Once paired, an attacker in close physical proximity to you could use their device to masquerade as your affected security key and connect to your device at the moment you are asked to press the button on your key. After that, they could attempt to change their device to appear as a Bluetooth keyboard or mouse and potentially take actions on your device.
This all being a big mistake, Google has offered a replacement key. However because my key hasn’t been added to my account yet, I get a message saying no action is required but a email to override this. However after double checking my key is a type T3 meaning it wasn’t effected.
A security flaw in WhatsApp can be, and has been, exploited to inject spyware into victims’ smartphones: all a snoop needs to do is make a booby-trapped voice call to a target’s number, and they’re in. The victim doesn’t need to do a thing other than leave their phone on.
The Facebook-owned software suffers from a classic buffer overflow weakness. This means a successful hacker can hijack the application to run malicious code that pores over encrypted chats, eavesdrops on calls, turns on the microphone and camera, accesses photos, contacts, and other information on a handheld, and potentially further compromises the device. Call logs can be altered, too, to hide the method of infection.
The issue affects WhatsApp for Android prior to v2.19.134, WhatsApp Business for Android prior to v2.19.44, WhatsApp for iOS prior to v2.19.51, WhatsApp Business for iOS prior to v2.19.51, WhatsApp for Windows Phone prior to v2.18.348, and WhatsApp for Tizen prior to v2.18.15.
