Hey guys! I’m doing a personal review of Ubuntu Touch on the Nexus4 device, and I thought I could share it with you.
It’s kind of a “Pros and cons” thing, but since I tend to get off-topic easily and babble a lot I’ve divided things in sections,
so you don’t have to read everything should you not want to.
Here it goes - Ubuntu Touch on the Google Nexus 4 (mako).
Installing Ubuntu has always been a pleasant experience for me. It feels open. Feels different. Feels fresh. Feels UBUNTU.
Installing any linux distribution on any PC makes mu blood run like crazy and Ubuntu Touch makes no difference.
It’s exciting to see something new and beautiful done for phones. And it’s even more exciting when you see it’s done with taste.
Now just to be clear – when it comes to Pros and Cons I guess the “Cons” section would be obviously much larger,
but hey: it’s a developers preview of what we should be expecting so I’m willing to suck some things up.
Pros:
1. Design.
Ubuntu Touch feels like Ubuntu in your hand. I just have to say this. I’m not sure if it’s the fonts or the wallpapers or the
transitions or the launch pad on the left or something else that I couldn’t quite grasp and understand,
but the fact is UT feels right. Feels Ubuntu.
2. Screen usage
Almost every other mobile OS has some buttons be it hardware or software (eg. Android’s software buttons on the screen + the 3-dot thingy).
Ubuntu gives you the whole screen to have for yourself and your app. It’s amazing how even the “Contacts” app feels bigger and more open.
3. Docking
I haven’t had the chance to go through the UT docking experience yet. I don’t even know if it’s quite baked yet, but what
I’ve seen on videos and ads is pretty awesome. The very idea of it makes it way cool. Chuck Norris cool.
The vision that one can have his PC in his pocket at all times is nothing but genius.
4. Compatibility
Ubuntu aims to be compatible with lots of devices. Which is good, I guess. I just hope compatibility doesn’t come
at the expense of stability or power management or something else that might come along and present itself as an issue.
5. Stability
I am yet to witness an app to crash or force-close or just close or anything like that.
I do get some strange freezes for a few seconds every now and then though.
Cons:
1. Installation
Installation can present itself to be harsh on someone who know nothing about using the terminal. There was a small step
missing in the installation tutorial which can cause some people to get confused. Mainly people with no
prior unlocking/rooting/flashing ROMs experience.
2. Boot
No boot animation. First time the phone booted it needed quite some time and there wasn’t even a splash screen indicating
something was working. The screen had the backlight on and that was it. No shutdown animation as well. And while we’re
still on the subject: there is no shutdown menu, which was kind of strange – I mean when you hold the power button the
phone just shuts down – no questions asked. I guess that might be good in some situations, but I’d rather have the shutdown menu.
3. Overall performance
Overall performance is laggy. The “use-of-edge” design is pretty neatly thought of, but in real life it need polishing. A LOT of polishing.
Swipes act strange, I move from app to app by accident.. My personal guess is that one can get used to it in a couple days
but the swipes should take a step towards being more intuitive as well.
I didn’t like the fact that the music page doesn’t stream anything, but takes you to the browser and when you hit play on some
hit you’re supposed to hear you get a message that flash is not supported or crashed or something like that. It’s kind of frustrating.
I think a native app should be replacing that page on the home screen real soon.
4. Social media
Neither Facebook nor Twitter have native apps. All you get is a mobile version in the browser. I don’t think it needs further explanation.
I hope both Facebook and Twitter do something about this. I don’t think it’s up to Canonical to make apps for those… or up to the
community for that matter. Anyway. I didn’t see a LinkedIn, Pinterest or any other social platform on the suggested apps, so
I guess I’ll just stop here.
5. Graphical glitches
Sometimes things will shift aside or up and down and text would overlap. It’s not something you can’t live with – a simple swipe one
way or another – fixes it, but I think all would agree it’s not an eye-candy feature. There are a few of these throughout the system.
It’s nothing serious in my opinion, but I couldn’t bring myself to put it in the “Pros” section.
The clock disappeared form everywhere except the clock app. I mean it – everywhere. It’s not on the homescreen,
it’s not in the “notification bar”, it’s nowhere. It happened after I rebooted the device for the first time. Also alarms don’t
seem to be working at all.
//* after a second reboot clock reappeared. Alarms still don’t work though.
Another thing is after picking up a call and finishing it – when you put the phone away from your ear the screen won’t turn on by itself.
That’s kind of odd if you ask me. It’s like it knows I’m saying “goodbye” and saves my battery or something. It’s a minor setback,
but still. I noticed that during the dialing process screen lights up if you take the phone away from your ear. I haven’t read a lot of
UT documentation, so it might be on purpose – I’m just stating what I’ve experienced.
6. Navitagion
Navigation is bad right now, I think. It looks like the OS isn’t sure how to respond to your swipe. Transitions are slow in my opinion.
They should be a tad faster. A major setback is the back button. I mean seriously – how many times do you misclick on something
and want to go right back. Think about it. It’s at least a few times a day. I think the back button should be visible the first few seconds
along with the rest of the app menu – should there be one. Or maybe just put it in the top left corner next to the search. If you think there
is no space – the search can always morph into “just a button” ... Other than that I can’t complain about navigation – it’s pretty neat,
actually. Menus are simple and understandable.
7. Hardware glitches
Everytime I wake my device up my Bluetooth is ON and I need to turn it off manually.
I can’t say I like that at all but considering that is all I have to say about hardware glitches I think it's not that bad.
8. 3G
3G is really important. AND it works! There’s just now way to shut it off.
I mean sure – you can turn off the mobile data, but when it comes to choosing whether to use 3G or 2G Networks Only – you don’t really have a choice.
You’re stuck with 3G and all the disadvantages that come with it as well as the advantages.
//* We all know what happens to your battery when using 3G and I’m the kind of guy that doesn’t like to turn his mobile data ON and OFF all the time – it just stays enabled all the time and saves me whole lotta thinking. Not having the choice of switching back to “2G networks only” sends you straight in hell in terms of battery life.
9. Syncing
Since I’m obviously new to Ubuntu Touch I just recently started using Ubuntu One, but my gosh! Syncing contacts with Google is a
real pain in the ass. Since the Gmail app is not a native app, but a HTML5 client instead, syncing appears to be impossible at this point.
Users are forced to hook their devices up to a PC running Ubuntu and write a bunch of commands in the terminal over and over again,
since syncing only works for no more than 50 contacts at a time. That being said I have over 600 so I had to run the damn thing 12 times
in a row. Aside from that should you choose to add a new contact it won’t sync with Google automatically and upload your new contact
into the cloud where you can have access to it at anytime.
//*Note: AFAIK: iOS, WM and Android have pretty easy ways to sync contacts with Google. I think this is one of the things the guys at Canonical should focus on. Slick mail application and neat contacts syncing is vital to a lot of people and is a major reason why they never switch phones.
Final thoughts:
Ubuntu Touch aims to deliver something different and really special to consumers: a PC inside a phone. I think what they are truly
missing here is an app store of some kind. The OS suggests apps but I couldn't see an app for that and I'm guessing that is somewhat of a
setback as well. They’ve been doing really well and while for now the “Cons” section is significantly larger than the “Pros”
I have hope and faith that Canonical will pull this off eventually.
Aside from the hard installation and the lack of an eye-candy boot animation… and maybe some other minor tickles - the OS looks
and feels nice and really pretty in the palm of one’s hand. They still have a lot of work to do if they ever want to catch up with Android or iOS
in terms of usability, syncing, MTP and other stuff that average consumers don’t know and don’t need to worry about but would miss a lot.
If you don’t don't mind the fact it’s a developers preview and the camera doesn’t always start off properly and you have to shut it down and run it again it’s pretty impressive!
Conclusion:
There are a lot of words one can use to describe Ubuntu Touch, but in my opinion the high order bid is “Inspiring”.
Yes, there are some glitches here and there. There is a lot to do. But after seeing it and touching it with my own eyes and fingers well…
I have to say this – I am thrilled and I can’t hardly wait to see what will they make of it.
littlegreen said:
Yes, there are some glitches here and there. There is a lot to do. But after seeing it and touching it with my own eyes and fingers well…
I have to say this – I am thrilled and I can’t hardly wait to see what will they make of it.
[/I]
Click to expand...
Click to collapse
Honestly, i think this is nothing new and nothing special ;/.
UPD: The problem is your article is too generalised, viewing stuff too objectively. Your article must show your personal opinion and vision on stuff, more than boring facts.
And don't use Pros/Cons style, when it's all about cons, not pros. Just don't.
Sent from my Nexus 4 using Tapatalk
reqmon said:
Honestly, i think this is nothing new and nothing special ;/.
UPD: The problem is your article is too generalised, viewing stuff too objectively. Your article must show your personal opinion and vision on stuff, more than boring facts.
And don't use Pros/Cons style, when it's all about cons, not pros. Just don't.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Well since I only have a few hours of experiencing the OS I don't think generalising is an option per say.
Besides - I am an optimist. I try to see the good in everything and that is why I have the "Pros" list. Thanks for the advice though.
well i find your review interesting to learn about the basics of ubuntu
Can you report about the battery performance?
Maybe some things are a lil bit old but everytime gold,lol.
Work in progress.......
------
What is a kernel?
If you spend any time reading Android forums, blogs, how-to posts or online discussion you'll soon hear people talking about the kernel. A kernel isn't something unique to Android -- iOS and MacOS have one, Windows has one, BlackBerry's QNX has one, in fact all high level operating systems have one. The one we're interested in is Linux, as it's the one Android uses. Let's try to break down what it is and what it does.
Android devices use the Linux kernel, but it's not the exact same kernel other Linux-based operating systems use. There's a lot of Android specific code built in, and Google's Android kernel maintainers have their work cut out for them. OEMs have to contribute as well, because they need to develop hardware drivers for the parts they're using for the kernel version they're using. This is why it takes a while for independent Android developers and hackers to port new versions to older devices and get everything working. Drivers written to work with the Gingerbread kernel on a phone won't necessarily work with the Ice Cream Sandwich kernel. And that's important, because one of the kernel's main functions is to control the hardware. It's a whole lot of source code, with more options while building it than you can imagine, but in the end it's just the intermediary between the hardware and the software.
When software needs the hardware to do anything, it sends a request to the kernel. And when we say anything, we mean anything. From the brightness of the screen, to the volume level, to initiating a call through the radio, even what's drawn on the display is ultimately controlled by the kernel. For example -- when you tap the search button on your phone, you tell the software to open the search application. What happens is that you touched a certain point on the digitizer, which tells the software that you've touched the screen at those coordinates. The software knows that when that particular spot is touched, the search dialog is supposed to open. The kernel is what tells the digitizer to look (or listen, events are "listened" for) for touches, helps figure out where you touched, and tells the system you touched it. In turn, when the system receives a touch event at a specific point from the kernel (through the driver) it knows what to draw on your screen. Both the hardware and the software communicate both ways with the kernel, and that's how your phone knows when to do something. Input from one side is sent as output to the other, whether it's you playing Angry Birds, or connecting to your car's Bluetooth.
It sounds complicated, and it is. But it's also pretty standard computer logic -- there's an action of some sort generated for every event. Without the kernel to accept and send information, developers would have to write code for every single event for every single piece of hardware in your device. With the kernel, all they have to do is communicate with it through the Android system API's, and hardware developers only have to make the device hardware communicate with the kernel. The good thing is that you don't need to know exactly how or why the kernel does what it does, just understanding that it's the go-between from software to hardware gives you a pretty good grasp of what's happening under the glass. Sort of gives a whole new outlook towards those fellows who stay up all night to work on kernels for your phone, doesn't it?
-----
What is a Nandroid backup?
If you've read about hacking or rooting your Android phone (or tablet, or media player) you've seen the word Nandroid used. When tinkering with your device, there's always a very good chance you'll be left with firmware that won't boot, leaving you in a bit of a lurch. A Nandroid backup can mean the all the difference here.
What it is, is a full backup of partitions on your device's NAND flash (NAND stands for NOT AND, a type of electronic logic gate -- it's like the hard drive of your Android device) storage. Think of it as a snapshot of the current running system, and it can be used to restore that that point at any time. Both user data and system files are backed up, and it's a far cry from what we think of when talking about a traditional backup from other software. In fact, it's something that many folks wish was part of the stock Android recovery. Yes, to preform a Nandroid backup you'll need a custom recovery on your device so that the executable files and scripts are there. These have been left out of the stock recovery, likely over issues that would arise if users can backup proprietary files.
Getting the custom recovery on your device is the hardest part, thankfully. Once installed backing up and restoring with Nandroid is simple, involving nothing more than choosing the option and verifying -- no wires needed. Even if you never plan to hack your phone, flashing a custom recovery and running a Nandroid backup is always a good idea. You can find more information about custom recoveries, as well as methods to install and use them, in the device-specific section for your device in the Android Central forums. Give it a look, and decide if it's something you're interested in doing.
-------
What is an IMEI?
The IMEI (International Mobile Equipment Identity) number is a unique set of 15 digits used on GSM phones to identify them. Because the SIM card is associated with the user and can be swapped from phone to phone, a method is needed to keep track of the hardware itself, and that's why the IMEI was developed. Math nerds will enjoy the way they are calculated -- the first 14 digits are decided by the GSM association, and the final check digit is computed using what's called the Luhn Formula -- crazy base-8 math that mere mortals like most of us don't understand, nor want to understand. You can see the IMEI of your Android phone by looking in settings > About phone if you're curious. (Or on the box if you still have it. Or under the battery or on the phone itself.
What is this number used for? That's the real question, isn't it. Like the MEID number on CDMA phones (think Sprint and Verizon), the IMEI is used for network control. It's not very common, but your mobile operator can block a phone based on it's IMEI in cases where it's been reported stolen or someone didn't pay the bill. Because it's not easy to change the IMEI of your phone (and maybe even illegal -- check your local laws) it's also used to keep track of phones that were involved in criminal activity, and the UK in particular has a handy database of phones used for these purposes. The IMEI number is also used to specify a phone for wiretapping by federal governments worldwide.
On a lighter note, Android apps can also use your IMEI number. The app will declare that it has access to your personal information, and the IMEI can be used to keep track of the device in a remote database. This sounds pretty scary, but it's an easy way (though not necessarily the best way) for app developers to keep a settings database online for your phone, in their app. Let's say you mark a bunch of favorites in a wallpaper app. Those favorites are kept in a small database file online, and when you reconnect to the app it reads your IMEI number to find your preferences. Not an ideal method, but it's easy.
One last thing -- now that we know a little more about IMEI numbers, they will soon be changing to IMEISV numbers. The use-case scenarios are the same, but the data structure and method of calculation is different. An IMEISV gets rid of the check digit (and its complicated Luhn formulated calculation) in favor of two digits used for software version numbering. Like everything else in the mobile space, network identification changes rapidly.
-------
What is a bootloader?
What is a bootloader? At its most basic level, your Android smartphone is like a hard drive, made of up several partitions. One of those partitions holds the Android system files, another holds all the app data you accumulate (which is how you're usually able to update without losing all your stuff), and others to do more behind-the scenes stuff.
Think of the bootloader as a security checkpoint for all those partitions. Because if you're able to swap out what's on those partitions, you're able to break things if you don't know what you're doing. Or, with a little hackery, you're able to run custom ROMs.
There's a lot of squawking about bootloaders being "locked." Actually, most phones shipped with a "locked" bootloader, including the developer-friendly Nexus devices. (Nexus devices and a couple tablets are easily unlocked with a single command.) No, more accurately, most bootloaders are locked and encrypted, meaning the traditional "fastboot oem unlock" command won't do a thing.
And that's a bone of contention for those who love a manufacturer's hardware and want to tinker with their devices. HTC and Samsung and Motorola -- just about everyone, really -- ships devices with locked and/or encrypted bootloaders. Tinkerers (we really don't like calling 'em "hackers") have to find a way around the encryption, usually with some sort of an engineering bootloader that wasn't supposed to be available to the general public. But in recent months, we've seen HTC provide a free tool that will unlock the bootloaders on a number of its devices, and ASUS just got on board, too. Sony Ericsson recently has provided unlocking tools. Motorola's promised to do so as well, but there's been little movement. LG and Samsung ship with unencrypted bootloaders.
Why keep a bootloader out of reach? Probably the biggest reasons are that the carriers and manufacturers don't want to have to support hacked phones. The other is that a lot of time and money is spent developing these things. HTC Sense ain't cheap. Neither is TouchWiz. But Samsung and HTC both have managed to find a middle ground with the modding community, and pressure is on other companies to do so as well.
-------
What is Dalvik?
What is Dalvik? We hear that word getting thrown around a lot on the Internet when talking about Android and its inner workings. While there's no easy explanation we can give in just a few paragraphs, we can cover the basics and point you in the right direction if you need to feed your nerdly side. In its simplest terms, Dalvik is a virtual machine that runs applications and code written in Java. A standard Java compiler turns source code (written as text files) into Bytecode, then compiled into a .dex file that the Dalvik VM can read and use. In essence, class files are converted into .dex files (much like a jar file if one were using the standard Java VM) and then read and executed by the Dalvik Virtual Machine. Duplicate data used in class files is included only once in the .dex output, which saves space and uses less overhead. The executable files can be modified again when you install an application to make things even more optimized for mobile. Things like byte order swapping and linking data structure and function libraries inline make the files smaller and run better on our devices. The Dalvik VM was written from square one with Android in mind.
Confused yet? Don't feel bad, geeky programming talk usually has that effect. Think of it this way -- when you build a Java application for your computer, a Java Virtual Machine runs the compiled output of the source code. This is why Java runs on just about any operating system. Dalvik is a mobile-optimized version of a Java Virtual Machine, built with code from the Apache Harmony project, which is open-source and runs better than a standard Java VM would on our limited hardware, designed so that you can run more than one instance of the VM at a time -- ie multitasking. Because Dalvik is open-source, it's also been ported to other operating systems, like the one on the BlackBerry PlayBook. It's pretty damn complicated, pretty damn cool, and Oracle (the company that bought Java from Sun) hates it.
Android uses Dalvik because while the license for the standard Java Virtual Machine is GPL2 (free and open-source), when placed in a mobile device and using the Java Micro Edition, it is not. The big dispute between Google and Oracle is all based around Dalvik. Google claims it was written in a "clean-room" environment without using any of Oracle's code, and Oracle disagrees. We claim to have no idea, we're just glad it works as well as it does.
For more on Dalvik, see the Google I/O website.
--------
LG's L-series
They made a big splash earlier this year at Mobile World Congress, and a few carriers in Canada jumped at the chance to sell them, but then they seem to have fallen off the map. I'll admit, even I have to look and see what we're talking about when we have potential news about the L3, L5, or L7. Let's have a refresh.
Imagine LG's Prada phone, but remade for folks who don't buy Prada. The L-series phones are all stylish (and really resemble LG's iconic Prada phones -- check out our look at them in Barcelona) and have an emphasis on good looks. The entry-level L3 competes with phones like HTC's One V and Samsung's entry-level Galaxy phones. It's running Gingerbread on a 3.2-inch display, but it looks nice doing it. Compared to something like the Motorola Defy Mini, you get good looks along with your dirt-cheap pricing. The L5 takes things up a notch to Ice Cream Sandwich and a 4-inch screen, placing it in the middle of the road where most people look first when buying a new smartphone. They'll see the L5, and notice the build materials and design. Finally, the L7 looks to compete with the big dogs of the Android world, with all the bells and whistles you would expect from a high-end smartphone, in a damn fine looking external shell. All three are eye-grabbing, and getting people to notice is the first hurdle. We're really not sure why we don't hear more and see more about them, but we're guessing a saturated market has something to do with it.
Maybe we'll see the L-series phones make their way into the spotlight, maybe we won't. But at least now we all know what we're talking about when we see them mentioned.
-----------
Multitasking
Multitasking is a word you'll hear a lot around here and at other places on the Internet that talk about smartphones or other tech. It doesn't mean what it used to, back when dinosaurs with long beards first dreamed up computers, but it still makes a very big difference for some folks and can be the deciding factor when picking a smartphone operating system. Let's have a look and see what the fuss is all about, and how it relates to Android.
A long time ago, in a laboratory far, far away, some Jedi masters decided that computers should do more than one thing at a time. They really already were doing plenty of things behind the scenes, but to the user it was a case of entering a command, and waiting for it to finish. Using threads and schedulers, and probably a little magic and a lot of luck, engineers were able to work up an operating system that could run more than one user command at a time, and multitasking was born. When you switch to a new VT (virtual terminal) on a Unix box with no GUI, you're multitasking. When you have more than one window open on your Windows or Mac or other computer that does have a GUI, you're multitasking. You're doing more than one thing at a time, and the computer is running more than one user task at a time. You can now read Android Central while your completely legal torrents are downloading in the background.
On a smartphone, multitasking is a bit different. We don't have the luxury of a 20-inch monitor, so showing more than one "thing" running at a time isn't a big deal. Samsung is testing the waters and trying it with the Galaxy S III with the Pop-Up Play feature, but for the most part whatever we're doing takes the whole screen to do it. We also don't have tons of RAM and video memory available and have to watch the power usage. This means smartphone multitasking has to be a bit, well, smarter.
Smartphones have been multitasking for a long time. All the mobile operating systems do it a bit differently -- some suspending all other apps in the background, some saving the state and closing the app itself, and others just letting everything run. The way Android does it is to let threads and processes run depending on their priority. If you're using Google Play Music, the processes that make the sound come out of the speaker have a high enough priority to stay running when you switch away from the app. Not all of it is running in the background, but enough of it is to keep the tunes playing. Other apps can be killed if they aren't being used, and some apps get "frozen" (for lack of a better word) and restore themselves when brought back to the foreground. What's important, and prioritized, is decided when the application is written and compiled so the end user doesn't have to worry about it. It's not perfect, but it follows the very strong multitasking model from Linux and tweaks it for Android. It's all open-source, so manufacturers and ROM builders can (and have) tweaked things to allocate memory the way they want it allocated. Sometimes the tweaks are great, sometimes not so much.
In the end, remember the next time you open an app and start up where you left off that you're seeing multitasking at work.
----------
Haptic feedback
It's one of those little things that can make a big difference, and something we never really think about. Simply put, haptic feedback (commonly referred to as haptics) is the use of touch feedback to the end user. You know how your Android phone vibrates a tiny bit when you tap one of the navigation buttons? That's haptics at work.
Since the screen on your Android phone or tablet is pretty much just a smooth sheet of glass of some sort or another, it's difficult to register any sort of tactile feedback to our fingers. When we type on a computer keyboard, we know when our fingers have pressed a key down. Our mouse (and some trackpads) do the same thing with a healthy click when we press the button. On a smartphone, we just have to trust we've done something, and wait for it to happen. Haptics helps here. The short and light vibration when typing out a message with an on-screen keyboard can make a big difference for many of us, and I can see myself being pretty frustrated if an on-screen button didn't let me know I had pressed it.
Haptics go beyond navigation and the keyboard though. They can be a very important part of mobile gaming. Gunning your way through an enemy horde is much more satisfying when you feel every shot from your rifle, and nothing lets you know you've hit the wall in your favorite racing game like a harsh vibration from your phone or tablet.
Probably the best thing about haptic feedback on Android devices is the way it can be customized. The OS itself is open, meaning OEM and developers can adjust things to get them just the way they like, including leaving the settings wide open to the user like we see in CyanogenMod ROMs. More importantly, application developers have access to the hardware controller to customize haptic feedback for their products. It goes one step further with the addition of things like the Immersion haptic SDK to the mix, where developers have an almost unlimited way to make their applications register with your fingers as well as your eyes and ears. Sometimes, the little things mean a lot.
--------
F is for Factory Reset
A factory reset is the ultimate cleansing of your Android device. It's usually either a last resort to fix a problem, done before you sell it, or because you like to flash ROMs. When you perform a factory reset you're essentially wiping out everything you've ever done to the phone and restoring it back to the basic manufacturer software. As we've mentioned before, it doesn't uninstall any software updates you've received from the folks who made your phone, but it does wipe out any core application updates you've grabbed from the Google Play store. The technical details are as follows:
/system is untouched, because it's normally read-only
/data is erased
/cache is erased
/sdcard is untouched
When your phone or tablet reboots, it's like it was when you opened the box as far as apps and user data goes, except for your data on the SD card partition (either a real, physical microSD card or a partition named sdcard).
Doing a factory reset is easy -- open the settings, do a little digging (different manufacturers put it in different places, but start with privacy or storage), select it and confirm. Your device will reboot into the recovery partition, erase everything, they reboot into the setup again. One thing to note though -- if you've rooted and ROM'd in any way, you should never do a factory reset from settings. Often times it works just fine, but some devices and some ROMs are so different once hacked that you'll end up with a bricked phone. We hate bricked phones around these parts. Follow the instructions from the folks who developed the software you're running instead, and use the reset method they recommend.
-------
End of life
End of life is a term none of us ever want to hear. We envision it means the death of our phone, and we should just throw it away and get a newer model. After all, it's at the end of its life, right? Not really. End of life means something different to carriers and manufacturers than it does to enthusiasts like us. The easy way to look at it is that when the folks in suits get together and decide that a phone isn't going to make enough money so it's worthwhile to keep producing it, it has reached the end of its life. That may mean a refreshed, newer model (like the Droid RAZR MAXX), or a shift to a newer model with new, and arguably better, features like the EVO 3D. We have to remember that the folks who make these phones do it so they can make money, and like any good business they want to maximize their profits.
But what does end of life mean in the real world? First off, it means that once the current stock sitting on the shelves is sold there won't be any more new ones to replace them with. There may be refurbished units floating around, but no more new phones of that model are being made. It doesn't mean that the phone is done getting updates, but don't expect too many new features to come along -- things are in maintenance mode and bug fixes and security patches are the only things that will be addressed. It also doesn't mean your warranty is affected in any way. Even if you were to buy a brand new phone that has already reached the end of life status, you'll still get the full manufacturers warranty.
Most importantly, it doesn't mean that the phone is going to stop doing anything it already does today. The HTC EVO 4G is a great example. It was a huge hit for HTC and Sprint, and actually stayed in production longer than any of us would have thought. Some places are still selling them new (although they're getting harder to find), and those EVO 4G's sold new today are every bit as good, and have the same warranty from HTC, as the ones sold in 2010. Sprint still offers customer service, and it's still one heck of a phone.
Don't be put off by the words end of life. While we wouldn't recommend you search out a new phone that's already been discontinued, they still perform as they should and you'll find lots of folks who still love them.
----------
DLNA
DLNA, or the Digital Living Network Alliance is an organization set up by Sony in 2003 that determines a universal set of rules and guidelines so devices can share digital media. The devices covered include computers, cameras, televisions, network storage devices, and of course cell phones. The guidelines are built from existing standards, but manufacturers have to pay to use them and have their device join the DLNA.
With DLNA devices, you can share video, music and pictures from a Digital Media Server (DMS) to your Android phone or tablet. A DMS could be your computer, a NAS (Network Attached Storage) device, a television or Blu-ray player, or even another Android device. Anything that has a DLNA server, or can have one installed will act as a DMS. Fun factoid: when a DLNA server is installed on a cell phone, tablet, or portable music player it's called a M-DMS -- the M stands for Mobile.
Once a DLNA server is in place, our Android phones usually have two functions -- to act as a Digital Media Player (M-DMP) or a Digital Media Controller (M-DMC). The player is easy enough to figure out, it finds content on a DLNA server and plays it back. A DMC will find content on a DLNA server, and push it to another connected player. For example, my television has a DLNA player, and my laptop has a server. With the right software, I could use my Android phone to find the content on my laptop and play it on my television. DLNA can really be fun if you have all the right equipment.
But chances are Android (and eventually other mobile devices) will be moving away from DLNA. With Ice Cream Sandwich, Wifi Direct is part of the operating system and has the potential to do everything DLNA can do, and more. We already have seen it replace DLNA streaming in the HTC One series with the Media Link HD receiver, which streams content from a Sense 4 device to a monitor with HDMI input. It uses native Wifi Direct, and by all accounts works really nicely. Or Samsung, who is using NFC to kick off a Wifi Direct session for fast data transfer on the Galaxy S III. We'll have to wait and see what manufacturers do with Wifi Direct, because having it built into the OS is a big plus -- even for a company like Samsung who makes millions of DLNA devices each year.
---------
Bloatware
When you think of Android phones, you think of bloatware. We wish it weren't so, and not every phone comes with, but the majority of Android phones out there come from carriers and are chock full of bloatware. We've complained about it, and found ways to remove it, but what exactly is it?
Most folks consider any applications that your carrier (or the folks who built your phone) pre-installed to the system as bloatware. Usually, these applications are a front end to some service or content that you'll have to pay for, and usually it's something you would never download and use on your own. All the carriers, and all the manufacturers, are guilty of including it, and we tend to hate it all equally. When you open the app drawer on your new phone, and see City ID staring back at you, just waiting for you to click it, you can't help but hate it.
But why is it there? It's one down side of Android's open nature. Google gives Android away to anyone and everyone, but realistically only a very few companies can afford to make cell phones. And they don't make them with you and me in mind as their customer. HTC, or Samsung, or LG (you get the picture) makes Android phones for the carriers. They work out deals to decide hardware and software they want to include, and part of those deals are these "value-added applications" we lovingly call bloatware. Verizon and HTC love you, but they still want you to click the app and send in the money. Because Google isn't involved and doesn't make any rules about it, they can include any app they like in your new phone. Nobody likes it, but it is the side effect of being open.
Thankfully, Ice Cream Sandwich brings along the ability to disable (most of) these apps without rooting or tinkering with the system files on your Android device, and that provides the best solution we can think of. Certainly there are some people who found a use for City ID or VZ Navigator, and they should have the opportunity to use those apps if they like. And we can disable and hide them, and forget they exist.
What is the AOSP?
AOSP is a term you'll see used a lot -- here, as well as at other Android-centric sites on the Internet. I'll admit I'm guilty of using it and just expecting everyone to know what I'm talking about, and I shouldn't. To rectify that, at least a little bit, I'll try to explain what the AOSP is now so we're all on the same page.
For some of us -- the nerdly types who build software -- the full name tells us what we need to know. AOSP stands for Android Open Source Project. The AOSP was designed and written by folks who had a vision that the world needed an open-source platform that exists for developers to easily build mobile applications. It wasn't designed to beat any other platform in market share, or to fight for user freedom from tyrannical CEOs -- it exists as a delivery mechanism for mobile apps -- like Google's mobile apps, or any of the 400,000+ in the Google Play store. Luckily, Google realized that using open-source software would ensure that this operating system/mobile application content delivery system is available for all, for free. And by choosing the licensing they did, it's also attractive to device manufacturers who can use it as a base to build their own mobile OS.
The premise plays out rather nicely. Google writes and maintains a tree of all the Android source code -- the AOSP. It's made available for everyone (you, me, manufacturers you've never heard of and not just big players like Samsung or HTC) to download, modify, and take ownership of. This means the folks at CyanogenMod can add cool stuff like audio profiles. It also means folks like HTC can change multitasking in ways that many of us don't like. You can't have one without having the other. The big players then use their modified version of this source to build their own operating system. Some, like Amazon, radically changed everything without a care to use Google's official applications and keep their device in compliance with Android guidelines. Some, like HTC radically changed everything yet followed the Android Compatibility Program (ACP) so they could include Google's core application suite -- including the Google Play store. Some, like the folks at CyanogenMod, enhance the pure AOSP code with additions but don't change the overall look and feel. Again -- that's how this open-source thing works. You can't have it without allowing folks to change it as they see fit, for better or worse.
Any of us can download and build the AOSP. We can even stay compliant with the ACP and contact Google about including their applications. Yes, any of us could build our own device using the AOSP code in our garage or basement with Google's full blessing. That's the beauty of the AOSP, and we wouldn't want it any other way.
--------
What is a widget?
What is a widget? In Android, the word widget is a generic term for a bit of self-contained code that displays a program, or a piece of a program, that is also (usually) a shortcut to a larger application. We see them every day on web pages, on our computer desktop and on our smartphones, but we never give too much thought into how great they are. Widgets first appeared in Android in version 1.5, and really gained traction thanks to HTC's Sense-flavored version of the operating system. Prior to the release of the HTC Hero and our first taste of Sense, widgets were functional, but pretty bland in appearance. Since then, OEMs and independent developers alike have done some marvelous things with widgets, and it's hard to imagine using Android without them.
Android widgets come in all shapes and sizes and range from the utilitarian 1-by-1 shortcut style to full-page widgets that blow us away with the eye-candy. Both types are very useful, and it's pretty common to see a widget or two on the home screen of any Android phone. A full-page widget, like HTC's weather widget for late-model Android phones, tells you everything you need to know about the current conditions, and is also a quick gateway to the weather application where you can see things like forecasts and weather data for other cities. At the other end of the spectrum, the Google Reader 1x1 widget watches a folder in your Google Reader account and tells you how many unread items there are, and opens the full application when pressed. Both are very handy, and add a lot to the Android experience.
Most Android phones come with a handful of built-in widgets. Some manufacturer versions of Android offer more than others, but the basics like a clock, calendar, or bookmarks widget are usually well represented. This is just the tip of the iceberg though. A quick trip into the Android Market will dazzle you with the huge catalog of third-party widgets available, with something that suits almost every taste. With Ice Cream Sandwich supporting things like higher resolution screens and re-sizable widgets, it's going to be an exciting year seeing what developers can come up with.
--------
What is tethering?
What is tethering? Besides the grounds for a giant debate about ethics (the kind that you can only find on the Internet) tethering, in this case, means to share the Internet connection from your phone with other devices. There are several ways to accomplish this -- connecting your phone to your computer via USB, setting up your phone as a wireless hotspot and router, and sharing a data stream over Bluetooth. All these connection types are built into Android, with native Bluetooth tethering new in Ice Cream Sandwich. Of course, different manufacturers can, and have, modified things so that these options are excluded -- at the behest of the carrier, of course. We'll talk more about why in a few minutes.
Tethering itself is pretty easily done. USB tethering involves installing device drivers (Windows only) and plugging in your phone to a high-speed USB port on your computer, then using your computer's built-in connection manager to use the phone or tablet as a USB modem. Bluetooth tethering will need the phone paired with the computer, and the connection type set up correctly in your computer's Bluetooth settings. Wifi is the easiest way -- you just turn it on and connect as you would any other wireless hotspot.
Except that many carriers, especially in the United States, have blocked tethering this way.
You see, your carrier wants to charge you a premium to use your data plan from any device besides your phone. Nobody likes it, but it's in the terms you agreed to when you signed up. They have all sorts of ways to block tethering on their end, and they are pretty diligent about it. Android hackers and developers also have found ways to work around these blocks, and it's a big cat and mouse game. An inside source with one the the biggest cellular carriers in the world has specifically told me that if your usage pattern draws suspicion, there is no current method that can't be detected by you carrier, including the newer VPN methods. If you do it a lot, without paying the extra fees associated with it, you'll get caught.
We're not going to judge anyone, and a few of us here at Android Central think charging extra for tethering is silly -- especially with data caps. Just know what may happen before you start so you don't get caught unaware.
---------
What is sideloading?
What is sideloading? It's a term you see a lot thrown around while talking about Android applications, and it's simple to explain. It means installing applications without using the official Android Market. What's less simple is how it's done and why you would do it. That's where this post comes in. Let's explain it, shall we?
How to do it is easy enough, so let's start there. In the Application settings on your Android phone, you'll find a check box to "Allow installation of non-Market applications." When it's checked, you can sideload. You'll also see a pop-up warning when you check this box letting you know that your phone is now more vulnerable to attacks from applications, and that you accept all the responsibility that comes with doing this. It makes sense -- you can't hold Google responsible for applications you didn't download through their service using their security methods.
Sideloading apps is easy to do as well. You download them to your phone, then use a file manager application to find them and "click" their entry. You'll invoke the app installer program, and it will install your app just as if it had came from the trusted Android Market. It won't be associated with your Android Market account, but it shows in your app drawer just like all the rest. It didn't used to be this easy for everyone. Under the guise of security, AT&T used to block users from sideloading by removing the Unknown sources field in the device settings. Whenever you tried to manually install an app, it would be blocked because it wasn't allowed. This could be circumvented by using adb from the SDK or by using a program like the Sideload Wonder Machine. Luckily, those days are past us and AT&T has re-evaluated their position, and now allows the installation of non-Market apps.
Why would you want to sideload. There are several reasons, one being that Google has allowed carriers to block certain applications based on the model and network your device is running on. We've seen carriers block apps that permit tethering without paying the extra associated fees, and some carriers have exclusives for certain apps and they aren't available for the others. That's a whole other mess that we'll tackle in another post -- just know that it happens. There are other reasons to need to sideload apps, too. Want to use a different appstore like the one from Amazon? You'll need to enable sideloading. The same goes for beta testing apps for developers, or even coding your own apps and testing them on your phone. There are a lot of legitimate reasons for sideloading. Of course, there's always the piracy aspect. If you want to steal from hard working developers you'll need to enable sideloading. You also suck. Sideload, but don't steal from developers.
--------
What is open source?
What is open source? Open-source software is software that makes the source code freely available, for anyone to see and use. There are different open-source licenses that have different use conditions, from the GPL (GNU General Public License) -- which allows "free distribution under the condition that further developments and applications are put under the same license" -- to more liberal licenses like the Apache License, which doesn't require modifications to be open and have the source code available. Android uses both of these licenses, and we'll have a look at them in turn.
The Linux kernel that is used in the OS is covered under the GPL. This means that any changes made to the source code must be made available when a binary (geek-speak for a compiled, executable piece of software) is released to the public. This means manufacturers like HTC, Samsung, Motorola and the rest must release the kernel source-code for any devices they sell at the same time they begin selling them. For the most part, hardware manufacturers are pretty good about doing so, but they often miss the time frame and release the source code a little later than we would like. These are the code releases you see us mention -- the kernel and other open-source "bits" that are covered under the GPL.
The Android OS source code is released mostly under the Apache License. Anybody is allowed to download the source code and change it however they like, but they are not required to make their changes available in source code form to the public. This is why we can't change and recompile things like HTC Sense or MotoBlur -- the changes to the base Android source code aren't available to us. While many folks (myself included) don't like this situation very much, it does make sense from a business standpoint. If manufacturers had to share all of their secrets, there wouldn't be as much monetary incentive to innovate, so the source was offered with a far more liberal license. It certainly worked, as we see devices from many major players in the electronics world.
---------
too,too
aaaaaand too
Good one buddy!
It's good for noobs!
And pro's!!
updated 2+3 post.
Awesome guide bro very informational
Can you emphatize in any way the questions ? Like bold it.
I try to read but i get lost easly x'D
Yeah i know what u mean,i do it with colors.
NERDIFIED TILL DEATH!!!
I like this so far. Please keep up the good work.
Assuming I was an expert user who knew every single Note 9 device option, samsung account setting, and google account setting.... If I were to configure EVERY single one of them to limit the data it collects, set every app permission to be in its most restricted state, disable every usage access setting, and configured my google and samsung accounts to be the most limited data collection accounts as possible, .... it is even possible to get to IOS level privacy on my Note 9? Is Android just sending everything it can back to google's servers as possible, such as when i turn the phone on, when i walk, move, open an app, browse the web, or whatever? I know some have already setup network analyzers to see the traffic going out, but I can never tell what configuration they do that with. I want to know if getting the privacy to IOS levels is impossible, or is it just a matter of very careful configuration....?
It's impossible. I'm not a fan of Apple devices, but I applaud them from a business perspective and that trickles down from the fundamental ideals of Steve Jobs.
Numerous studies show that Google sucks up information 10x as much as Apple which relies in differential data that doesn't exactly pinpoint the person, but more so the general interests of the person. Google identifies the person and their location. Unless you're walking around with your phone off or granting no permissions to every app, you can't match the security of an Apple device. The doesn't only include Google. Remember we have to deal with our specific manufacturers that are collecting data on us as well since Android is open source. So we just have to hope Googles intentions are good or move to an Apple device.
brainysmurf said:
Assuming I was an expert user who knew every single Note 9 device option, samsung account setting, and google account setting.... If I were to configure EVERY single one of them to limit the data it collects, set every app permission to be in its most restricted state, disable every usage access setting, and configured my google and samsung accounts to be the most limited data collection accounts as possible, .... it is even possible to get to IOS level privacy on my Note 9? Is Android just sending everything it can back to google's servers as possible, such as when i turn the phone on, when i walk, move, open an app, browse the web, or whatever? I know some have already setup network analyzers to see the traffic going out, but I can never tell what configuration they do that with. I want to know if getting the privacy to IOS levels is impossible, or is it just a matter of very careful configuration....?
Click to expand...
Click to collapse
No fanboi of any company/mfg/OS,but,they all do virtually the same thing with your personal information/usage habits.
The differences are mere semantics & they collect/sell user information.
The following is a 2yr old article,but,I'm guessing the points they make still hold true:
https://decentralize.today/apple-vs...company-handles-your-data-better-a7022bd452b1
Arguably,Android users can control their sharing of personal data usage,but,that has its caveats,such as limited functionality on some apps/etc...
Best advice I can give is the following:
1) Carefully comb through every setting on the phone,most are self-explanatory.
2) Go to every apps internal settings & the phone's setting under SETTINGS > APPLICATIONS & fine tune as best as possible.
Even after all of that,Google/Samsung (or most other mfgs) have settings that are inaccessible or cannot change (greyed-out),so,you're still not in the clear as far as total control/privacy.
This is one of the major attractions to rooting/ROMs for your Android device.
A rooted &/or ROM'd Samsung device is the ideal for gaining control of privacy/permission control,but,it breaks KNOX & Samsung Pay,no going back once rooted,even if restored to a stock state.
You gain more granular control of such permissions & if you want to go all-in on privacy, a ROM such as Lineage gives you the best you can hope for in personal security/privacy. A brief summary,but,that's the gist.
Outside of root/ROMs,If privacy/security is of utmost importance,I'd dare say a Blackberry would be a decent choice. I myself only briefly owned a Blackberry (Android device),so,I can't attest to how private/secure you personal usage/data is,but,I've rarely,if ever,heard of any major concerns in the matter w/Blackberry.
@brainysmurf
Another step you can take to regain some control of your Samsung device is using a package disabler app & the nice thing about these is no root access is required (AppFreeze/Package Disabler Pro/Adhell3).
https://play.google.com/store/apps/details?id=com.wakasoftware.appfreezer&hl=en_US
https://play.google.com/store/apps/details?id=com.powermanager.batteryaddon&hl=en
https://amp.reddit.com/r/GalaxyS8/comments/8nmrfq/how_to_install_adhell_3_a_video_guide/
Use the XDA site search feature or Google for more info on the above mentioned disabler apps.
You can also use ADB Commands to disable apps as well,but,please read the following link carefully before proceeding:
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
I have never had an apple device, But I would like to say that android as a system is opensource and the google apps that are put on top are non opensource and are probably where you lose your privacy but as a system it is transparent which attracts devs and rooting (i.e. getting access to the system partitions) is what makes android so customizable. Versus apple which you have to blind trust ios and trust that these options are 100% do what they say..
Yes it is more secure because it is closed source but at the same time For actual privacy you never know. Saying that how do you get your privacy with android needs some setup which koliosis did good explaining. But the difference between the two OSs I believe is because of (opensource)ness of android the amout of customizablity with android is really deep. To which I believe if you invest good time researching, you can get a way better state than iOS. Again not an expert but putting my opinion
For the rest
Koliosis said it all.
that_same_guy said:
Yes it is more secure because it is closed source.
Click to expand...
Click to collapse
Have to correct that one. That is a myth spread by some big companies in order try to gain some customers over from the cheaper/free competition. In reality, open vs. closed source has no other effect on how secure the result is than with open source there can be more eyes looking at the code (for both good and bad intentions). As an example, simply compare a decent linux distro (from which only similar applications are installed that would come with corresponding Windows installation) to M$ Windows. Open source (and free at that) wins many times over in overall security (while neither is free from issues).
The biggest effect on the code quality (thus often also how secure it is) is on how many (real) experts work on it, and this in turn depends on popularity (open source) and/or money (company's/organization's income and policies/ideals). For the last part 'policies/ideals' just compare M$ and Apple, both have the money to throw at development if they choose to do so; former makes mostly insecure crap, latter makes half-decent stuff. (And note, I'm not a fanboy of either, or pretty much of any company, except one little local camera shop, so do read the previous with some weight on that "half-" before the "decent".)
As for small input on the privacy squeezing on Samsung devices:
I have so far managed to avoid to use a samsung-account, and that might help a tiny bit, although some features of the phone are then not working, but mostly useless features. Though there are some seemingly useful features that require Samsung-account for some weird reason, but I've manage to live without them. Like the "protected folder" (or whatever it is in English), why on earth would that need an account or anything external for that matter?!?
(Well, technically, I do have a Samsung-account, as that was required to get the phone cheaper, but after that order, I've not used that account anywhere.)
ErebusRaze said:
It's impossible. I'm not a fan of Apple devices, but I applaud them from a business perspective and that trickles down from the fundamental ideals of Steve Jobs.
Numerous studies show that Google sucks up information 10x as much as Apple which relies in differential data that doesn't exactly pinpoint the person, but more so the general interests of the person. Google identifies the person and their location. Unless you're walking around with your phone off or granting no permissions to every app, you can't match the security of an Apple device. The doesn't only include Google. Remember we have to deal with our specific manufacturers that are collecting data on us as well since Android is open source. So we just have to hope Googles intentions are good or move to an Apple device.
Click to expand...
Click to collapse
This actually goes to my point... If indeed I did remove all permissions from all apps, does this mean Android tracking would be completely disabled? Or if I removed google play services, or disabled it, or removed all permissions from it? Technically, would that give it an IOS level of privacy? I'm just wondering if the OS itself is prone to just phoning home and letting it know everything I'm doing, or if it's possible at all to tame it....
Thanks for your repsonse.
ErebusRaze said:
It's impossible. I'm not a fan of Apple devices, but I applaud them from a business perspective and that trickles down from the fundamental ideals of Steve Jobs.
Numerous studies show that Google sucks up information 10x as much as Apple which relies in differential data that doesn't exactly pinpoint the person, but more so the general interests of the person. Google identifies the person and their location. Unless you're walking around with your phone off or granting no permissions to every app, you can't match the security of an Apple device. The doesn't only include Google. Remember we have to deal with our specific manufacturers that are collecting data on us as well since Android is open source. So we just have to hope Googles intentions are good or move to an Apple device.
Click to expand...
Click to collapse
Yeah I saw those same studies. And they never seem to provide specific configuration data. For instance, the study showing that android gathers as much as 10x more data specifically mentioned that Chrome was constantly phoning home sending data. However, what if the user didn't log into their chrome account? I think it's much more limited in that case... Or what if the user disabled chrome, and perhaps all google apps? Is it android doing the privacy damage, or google apps/play services? If I disabled those, or removed all permissions from those, would it be equivalent to IOS? I'm an engineer in the business working at a major silicon valley company, and even with high expertise in the design of these things I'm finding it impossible to get basic understanding of what it actually going on. It is either trying to read through legalize of privacy agreements, or reading blogs and studies with claims such as 10x more data, while not providing specifics...