Trending December 2023 # I Hate Android: Why? – By A Hardcore Android Lover! # Suggested January 2024 # Top 13 Popular

You are reading the article I Hate Android: Why? – By A Hardcore Android Lover! updated in December 2023 on the website We hope that the information we have shared is helpful to you. If you find the content interesting and meaningful, please share it with your friends and continue to follow and support us for the latest updates. Suggested January 2024 I Hate Android: Why? – By A Hardcore Android Lover!

Like millions of people around the world, I am an Android fanboy. Recently I though about sharing some of my  aspects which I don’t like about Android.  Eventhough being Android has gotten better over the years but there are still many things I dont like about it. To put it bluntly, I hate Android, at least some of its features. I have used Linux for a few years since Ubuntu Gutsy Gibbon and fell in love with the open source movement. Ive come to realize that all the hype about being open and portraying Apple and RIM as the evil closed platform was all a deception. . Theres a list(I love lists). Lets go through them. I hate some of the UI. Customization is nice but it allows for more things to break. These include themes and design. At first, the UI was cool and beautiful. I felt like I had a computer in my hands, literally. Icons were nice to touch and scrolling was smooth(at first). After using it for a while, I started to experience the pains of using the touch screen. Mistypes, and mistaps were frequent. The Android experience varied depending on manufacturer. All the different flavors of Android pushed by their respective hardware developers all look different. OneUI, TouchWiz, and MotoBlur are all different. OneUI is probably the best(IMO) out of all these. TouchWiz makes me feel like Im using an iPhone and MotoBlur is a mess with all their social networking widgets. These skins load on top of Android making it slower than its vanilla stock core. When I get my phone, I hate all the bloatware that comes with it. All carriers seem to do it. They push Vcast, SprintTV and other bloatware that I dont want. The Chinese manufacturers Xiaomi,Oppo,Vivo are the notorious ones feeding bloatware just to compnsate for the cheap price they offer in some countries. Not only that, but I hate that I cant delete them. I hate knowing that they are on my phone and the only way for me to get rid of them is by rooting my phone. Why do I have to jump through hoops just to get rid of this crapware? Im not scared of rooting my phone. In fact, Ive done so and install a few custom ROMs but there is always a risk of bricking your phone and leaving it useless. Average users dont want to risk the warranty by rooting their phone. Not only are there crapware on the phone, but there is/was malware on the Market. I hate Andoid memory management, being an old Symbian OS user.Symbian was the most efficient Mobile Os in memory management, followed by iOS. My old Nokia 808 Pureview had just 512MB RAM which was handling the Mammoth Camera, the 41MP beast with Xenon flash. I know that comparing a Symbian Phone with very limited apps and strict developer requirements with Android which has an ocean of apps and simpler developer standards is not fair. But are these crazy RAM of 12GB,16GB etc etc in many high end Android Phones really necessary? Or are they worth the performance they offer compared to iOs? Expanding from the 1st and the 3rd reasons, I hate Androids software fragmentation. I hate that Motorola’s flavor is different from Samsung’s. I hate that the buttons are different in all manufacturer, and even sometimes, within the same manufacturers. And I hate that I cant install certain apps because I my phone doesnt have the latest and greatest version of Android. Notoriously all my Samsung Phones from Galaxy S3 to Galaxy S9 Plus started showing sluggishness after 1 year of usage. The problem being whenever I update an app, the hardware is not able to cope with newest software. Android isВ recognized as the open platform and that unadulterated Android experience does not come standard. It only comes standard on Googles Nexus phones  and Selected flagship phones from other manufacturers. But most people dont own these flagship devices. Most people get their Droids from their carriers. Not only are these phones locked down with carrier bloatware but they are also locked down from performing specific tasks. People have gotten around this issue by a process called rooting. This grants the user superuser status allowing him to do anything he wishes with the phone. The Nexus phones are relatively easy to root but carrier phones are harder. Android phones are great if you want the phone to be your hobby, if you dont mind tinkering with the device, rooting it, or if youre just a techno buff.  

You're reading I Hate Android: Why? – By A Hardcore Android Lover!

Why Android Is Bad For Business

The news seems to be all Android, all the time these days, and various analysts have recently revealed predictions that Android will soon be the leading mobile platform. Despite the popularity of the Android platform, though, there are some critical elements of Android that make it unsuitable for business use.

Open Source

To be fair, open source software has managed to achieve some credibility, but a quick look at market share numbers will show you that even after decades of availability and countless assertions of its technical superiority, Linux has less than one percent of the operating system market, while Microsoft Windows enjoys greater than 90 percent. After only three years, Apple’s iOS mobile platform already leapfrogged the venerable Linux in market share.

Businesses want software vendors they can work with–and point fingers at. Many companies have close relationships with the hardware and software vendors they work with, and those relationships enable more efficient and effective operation. When an issue arises, the IT department knows who to call to address and resolve it as quickly as possible. With open source, the question of “who you gonna call?” gets murky.

Too Much Diversity

The fact that you can choose from a wide variety of smartphone form factors, and select any of the major wireless carriers creates a pool of potential Android users that is significantly larger than say the subset of customers who prefer the iPhone form factor and happen to be AT&T customers. It doesn’t hurt that there are frequently buy-one-get-one-free deals, or that many Android smartphones are available from Amazon for one penny.

The different hardware form factors have unique capabilities, the different Android platforms deliver unique features and functions, and the proprietary interfaces create scenarios unique to the specific device, and the IT admin has to be familiar with them all and find a way to manage and maintain them all. When a new release of Android comes along, the ability to embrace or deploy it is limited by which Android smartphones will even receive the update, and the scattered timing of the releases depending on the vendor and model.

Before the zealots jump in and make this an Android v. iOS debate, the iPhone is not an ideal smartphone platform for business either. Apple takes closed source to a draconian extreme with its dummy proof “walled garden” approach, and the singular iPhone 4 (or dual if you also consider the iPhone 3GS a separate device) smartphone form factor may not be for everyone.

However, RIM has been able to dominate mobile business communications with a proprietary platform, focused on delivering tools IT admins need to monitor and manage devices remotely, and with a diverse collection of BlackBerry handsets. When Windows Phone 7 launches this fall, Microsoft should be in a similar position to deliver a smartphone platform that lies somewhere between too open and diverse, and not open and diverse enough.

All hope is not lost for Android as a business tool, though. For companies that can get past the open source issue, Android offers a powerful mobile platform and is worth consideration. IT admins can remove some of the complexity and make it more manageable by offering a single Android smartphone, or at least narrowing the options to a designated list of supported Android smartphones.

A Button Mapper Is The First App I Install On Any Android Tv

Rita El Khoury / Android Authority

I started using Android TV devices with the 2023 NVIDIA Shield, but I have never found myself with as many options inside my home as I do today. My TV itself — the Xiaomi TV P1 43-inch — as well as my local French TV provider’s set-top box both run the platform. So does the Chromecast with Google TV stick that I had bought before those two, and the Android TV projector I’ve installed in my kitchen. If you think getting used to one remote is bad enough, try four. In the middle of this madness, one app has kept me sane, and it’s the same one I’ve been installing on all of my Android TV devices since 2023: Button Mapper.

Why remap those buttons?

David Imel / Android Authority

Every remote you get is built differently. Some, like the one for the Chromecast with Google TV, are minimalistic enough to only include the essential buttons. Others, like the ones for my TV and set-top box, add dozens of other keys.

The issue that arises, besides the confusing embarrassment of riches that I currently have, is that not every remote will be optimized for you. Your usage, your preferred apps, your favorite layout. Most remotes have hardcoded buttons for apps you’ll never use. For me, this is Netflix; for you, it could be Prime Video or Hulu. Some remotes also put buttons that you can’t use, like that futile (in my region) Mi Patchwall button on my TV’s remote.

Don’t touch these buttons

The omnipresent Google Assistant button is usually not worth touching. You can do it, but on nine devices out of ten, the functionality seems to be hardcoded and no amount of remapping or goodwill works. The remote will start a voice search and there’s nothing you can do about it.

The power button, D-pad, and volume buttons are big no-nos in my book. I don’t dare touch them because they’re crucial to the way Android TV works. I wouldn’t want to have to dig out a USB keyboard and mouse to get myself out of a jam if I messed those up.

Don’t change the power button, D-pad, or volume buttons, because they’re crucial to the way Android TV works.

I also don’t change the Home and Back buttons’ single press purpose — they’re just as essential. But long presses on those are fair game, and I often assign them to go into the TV’s settings or take a screenshot. I’ve never had any problem with this on any device so far, but keep in mind that Google might assign them crucial functionality in future Android TV versions.

Customize these buttons instead

Rita El Khoury / Android Authority

That usually leaves the input, mute, different streaming services, and any extra button your Android TV maker decided to include. Depending on your usage, those could be dispensable, and you can reassign them to any app or functionality without breaking anything. (There’s an exception with the Chromecast with Google TV’s Netflix and YouTube buttons that are less flexible, but otherwise, feel free to play around.)

The input, mute, and different streaming services’ buttons are often fair game, and you can easily reassign them to any app.

My personal go-to tricks are to remap any hardcoded Netflix buttons to Plex, and add a double-press to YouTube that opens Spotify. Long-presses get assigned to whatever streaming app I’m using most at the moment. I also like adding the often missing play/pause role to any unneeded buttons — like that Mi Patchwall launcher button on my TV.

Rita El Khoury / Android Authority

After all of this is set up, I start monitoring my usage of the remote. If I find that I’m getting confused between two buttons, or if there’s one that I often press by mistake, then I’ll fix or reassign the functionality. That keeps me sane and avoids any unnecessary waste of time. You don’t want accidental touches to frequently interrupt your entertainment session.

Do you remap your Android TV’s remote buttons?

687 votes

Besides Android TV, Button Mapper also works on phones. As a matter of fact, it’s one of the apps we recommend Samsung owners use to remap the Bixby button. But since most other Android phones don’t have any superfluous keys, the app is a lot more useful on Android TV. It has quickly become my default set it and forget it utility on the platform.

Root Moto X On Android 4.4.2 Using Pie Root By Jcase

Moto X is one tough shell to crack and the most of the common rooting procedures failed on the Android 4.4.2 upgrade. There are a few rooting techniques where the device should be downgraded to 4.2.2 before performing the rooting process, and then you have to go through a series of tools like SlapMyMoto, Cydia Impactor and Telnet along with a plethora of commands followed by the 4.4 OTA update. This surely will make your rooting experience hectic, especially for those who are new to Android development.

Thanks to JCase, a renowned and recognized developer from XDA community who has finally came up with a solution to root the Moto X on 4.4.2 KitKat without complex operations. The root package is called Pie, and is not an ideal solution to the rooting problem on Moto X on Android 4.4.2 as the root access obtained by the Pie is neither a permanent root nor has complete functionality.

The rooting method used by the Pie root is a tethered root (tethered jailbreak), which means the root permissions will last as long as you don’t reboot your device. So you have to run it each time you reboot in order to have root access. Adding to the miseries, you do not get system write access so no more editing the chúng tôi or writing files to /system partition. The only thing that works correct are the root and busybox.

The Pie is not ideal, but this is the only root method available for the Moto X on locked carrier devices and can come handy for some operations like backup/restore app data using Titanium Backup and granting permissions to some of the apps which don’t need write permissions to System partition. The rooting procedure is quite simple, all you need is the root package and ADB installed on your PC with proper driver installation.

Download the ADB files and root package from the download link provided below.

ADB+Fastboot file → download link.

Pie Root Package → download link.

   Installation Instructions

Connect your device to the PC through a USB cable.

Make sure the PC recognize your device by checking for the device in device manager.

Extract the ADB+Fastboot files to a folder on your computer (avoid extracting to your desktop, there might be problem when you have a

user name

which has space in between like xxx yyy ) and install the

USB drivers

in case you are on Windows PC.

Extract the contents of the root package to the same folder where you have extracted the ADB files.

Now type or copy/paste the following commands in the command prompt one by one to root your device. adb push chúng tôi /data/local/atvc adb push chúng tôi /data/local/atvc adb shell chmod 755 /data/local/atvc/ adb shell /data/local/atvc/

The expected output on the command prompt is: Retina:package jcase$ adb push chúng tôi /data/local/atvc 5288 KB/s (1538203 bytes in 0.284s) Retina:package jcase$ adb push chúng tôi /data/local/atvc 81 KB/s (137 bytes in 0.001s) Retina:package jcase$ adb shell chmod 755 /data/local/atvc/ Retina:package jcase$ adb shell /data/local/atvc/ pie by jcase Retina:package jcase$ adb shell [email protected]:/ $ su [email protected]:/ # id uid=0(root) gid=0(root) context=u:r:kernel:s0

That’s it, with these four commands your Moto X should be rooted on the Android 4.4.2. But bear in mind that the root is lost when the device is rebooted, so avoid rebooting your device frequently.


Why Does My Hotspot Keep Turning Off (Ios, Android, Laptop)

Frequent hotspot disconnection poses a big problem to your work. Whether working from home or outdoors you don’t want constant interruptions to lose your job.

Restarting the hotspot is one way to fix it but it would get frustrating to keep doing it every once in a while. And it’s only going to cost you more to buy a backup internet plan for your hotspot.

There are few features on your mobile device that can turn off hotspot automatically. The power-saving mode is one of the most common causes. To resolve this, simply charge your phone or turn off the feature entirely.

But, it’s not your phone that’s causing the problem or the solution didn’t work, don’t worry. There still are plenty of solutions to the problem.

If the hotspot is from your PC, your network may be set up as metered. Metered networks are configured to restrict network traffic when nearing the limit.

If the hotspot is from your phone, Your phone data may be nearing the limit. Check the data usage on your phone to see if you’ve exceeded your plan. If that’s the case, the phone may shut down internet sharing via hotspot. This information should be visible on your provider’s mobile app too.

Go to Settings and tap on Wi-Fi & Networks.

Select Data usage.

If your Data Usage Exceeds the Plan you have purchased, your data will stop working.

Go to Settings and tap on Cellular.

Scroll down to Cellular Data.

Here too, if your data usage exceeds the plan, the hotspot will turn off automatically.

Wi-Fi hotspot features in new phones are improved to reduce power consumption. When there are no connected devices for a set amount of time, the system turns off the hotspot. Depending on your phone, you may or may not be able to disable it. Check your vendor for details.

Open the Hotspot & tethering options.

Go to the Wi-Fi hotspot.

Check the Turn off hotspot automatically option.

Note that the setting may be slightly different depending on the phone vendor. But the setting is always found under the Mobile hotspot settings page.

iOS does not provide timeout settings.

If your phone or PC is low on battery, your hotspot will turn off automatically. Using a mobile hotspot means you’re using two things at the same time :

Your sim’s cellular connection for data transmission

Your phone’s Wi-Fi feature

Both these tasks consume system resources and drain your battery. If your hotspot is set at 5GHz, the battery drains even faster. Thus, your system may stop one or more of the above tasks to optimize battery life.

Your Wi-Fi may be out of range. Ideally, the range of connectivity with a mobile hotspot on both WIFI and Bluetooth is about 30 ft. You’ll feel a noticeable performance lag outside of this radius.

If it’s not a distance issue, something else is interfering with your wireless hotspot. This could be a different hotspot or a router in your surroundings. Also, laptops may be able to provide a better Wi-Fi range than phones. But no hotspot device will ever work as well as a router.

Use an app like Wifi Analyzer to see if you’re having range problems.

If you’re using an old device set up with a hotspot, it may not be functioning properly. Older devices may have had their wifi antenna damaged. Or they may have stopped receiving software updates altogether.

Thus any system bug resulting in hotspot issues remains unfixed. In any case, these devices are no longer able to deliver hotspots with good performance.

A mobile hotspot device like Orbic Verizon Speed Mobile Hotspot can keep disconnecting for different reasons

The number of connected devices reached its limit. Normally it’s 5 or 10.

Verizon tower reception is poor in your area. You can check tower coverage of Verizon on Official Website.

Your Verizon sim card has failed to work properly or needs replacement.

A Sql Primer For Android App Developers

So, you have your program and you have your database with client details, usernames and passwords, or players and high scores. There are a number of different actions you might wish to perform to get to this point and to make use of the database going forward.

These actions are performed via statements. So, for example, in order to create a new table, we do so by using CREATE TABLE. To add more data, we use INSERT INTO. To delete data, we use DELETE.

There are a great many different SQL statements that you can use to manage your databases. However, most Android developers will find themselves relying on a few key statements.

The first thing you’ll need to do is to create your database. Some databases will let you do this with CREATE DATABASE, but in SQLite3, you use $sqlite, followed by the database name. You’ll probably do this using a Java class, depending on how you want to go about it. But once you’ve done that, you’re good to get started with a whole range of different statements.


A database needs tables. The next step then will be to use CREATE TABLE in order to build one. This is again pretty straightforward, as long as you can imagine the table being built in columns.


CREATE TABLE Clients (     rowid integer PRIMARY KEY,     LastName text,     FirstName text,     Phone text,     Email text INSERT

Now you’ve got a database with an empty table called ‘clients’. The next thing you’ll probably want to do is to put some data in there! To do this we use INSERT INTO. Here, you’ll insert into your specific table and then you’ll list the columns in brackets, followed by the values.


INSERT INTO table_name (column1, column2, columm3) VALUES (value1, value 2, value3);

You’ll be able to insert information into some columns and not others.  We can also insert multiple rows of data using just a single statement, by using lots of brackets separated by commas.

For example, if we wanted to update our clients table, then we would do something like this:


INSERT INTO Clients (LastName, FirstName, Phone, Email) VALUES DELETE

DELETE is for deleting rows from tables. To use delete, the correct syntax is:


DELETE FROM table_name WHERE condition;

So, if we wanted to delete a single record, we could use:


DELETE FROM Clients WHERE FirstName=‘Roy’;

Roy Wood wasn’t in the band for very long, so he doesn’t get to stay on the list. We could also use this to delete anyone over a certain age.

If you just use DELETE FROM table_name; then you’ll end up deleting the entire contents of the table. Be very sure before you do that! If you want to delete the contents of the table and it’s structure, then you’d use DROP TABLE. Be even more careful when doing that.


Adding and removing data is straightforward enough. Occasionally, you’ll just want to update some information. Maybe you just need to change the email address but you don’t want to delete and reinsert the entire record.

In that case, you can use UPDATE in the following manner:


UPDATE Clients



Using these statements will build your database up nice and big. But that’s pretty useless until you can also retrieve that information back.

SELECT is used to return a set of results from one or more tables. If we wanted to retrieve someone’s name or a list of clients aged 21, then we would use SELECT and follow this up with some specific details to define precisely the kind of data we want to retrieve.


SELECT column_name FROM table_name;

This would allow us to select a whole bunch of different columns from our specific table.

FROM is a clause that changes the behavior of the SELECT statement. In this case, it defines which table we want use. FROM is a required clause in any SELECT statement. However others like WHERE are optional. WHERE allows us to filter the rows that have been retrieved by a ‘predicate’ – a true or false statement. Imagine my client contact details table had another column in it for ‘age’ and we wanted to find clients older than 21. In that case we would type:


SELECT FirstName FROM Clients

A quick example

To see how this might work in practice, here’s a project from Gary that puts SQLite into use in the context of an Android app:


import android.database.Cursor; import android.database.sqlite.SQLiteDatabase; import; import android.os.Bundle; import android.widget.TextView; import java.util.Random; public class MainActivity extends AppCompatActivity {     @Override     protected void onCreate(Bundle savedInstanceState) {         super.onCreate(savedInstanceState);         setContentView(R.layout.activity_main);                         SQLiteDatabase db = openOrCreateDatabase("mydb", MODE_PRIVATE, null);         db.execSQL("DROP TABLE IF EXISTS mydata;");         db.execSQL("CREATE TABLE mydata(key text, val integer);");                         Random r = new Random();         int  n = r.nextInt(100);         db.execSQL("INSERT INTO mydata (key, val) VALUES ('random', " + n + ");");                         Cursor results = db.rawQuery("SELECT val from mydata WHERE key='random';", null);         results.moveToFirst();         int myr = results.getInt(0);                 db.close();                 TextView t = (TextView) findViewById(;         t.setText(Integer.toString(myr));     }

More statements, more possibilities

There are many more statements you’ll likely find yourself using frequently. For example, ALTER can allow you to add new columns. AS allows you to rename columns and tables. COUNT lets you count entries. HAVING is similar to WHERE. GROUP BY lets you group your results.

Of course, this is by no means a comprehensive guide. There is a lot to learn here. You can even use extensions in order to perform complex statements like If, Then, and others (though most of this can also be done through Java if you’re using SQLite for building apps).

Update the detailed information about I Hate Android: Why? – By A Hardcore Android Lover! on the website. We hope the article's content will meet your needs, and we will regularly update the information to provide you with the fastest and most accurate information. Have a great day!