Nuvigil is great to avoid clinical depression

Nuvigil (armodafinil) is an already-existing and FDA-approved drug for the treatment of 'excessive sleepiness' due to narcolepsy, shift work, or obstructive sleep apnea. Its not an antidepressant in any traditional sense. In lieu it's something like a stimulant or a 'wakefulness-promoting agent.'1

So buy nuvigil online nowtreatment. Since sleep issues and lethargy are common complaints of people with depressive signs, its manufacturer was trying to get an add-on approved treatment for depression signs in bipolar I disorder.

Which is a huge deal. Historicallyin the past few years, drug companies have been called on the carpet for designing studies that underestimate the impact of placebo versus medications (or otherwise cloud the results to minimize placebo knowledge).

The news was released yesterday by the drug's researchers at Teva Pharmaceuticals. Nuvigil's final Phase III studies showed statistical significance in 'several important secondary endpoints' (which is drug-speak for 'the massaged knowledge show some significance, but clinically, you'd be hard pressed to find any benefit'). But it failed to show it was any better than a placebo or sugar pill.

And as Teva revealed, they got better in this study at roughly the same rates as those who were taking the actual medication.

Because, as it turns out, the 'placebo effect' ' being treated with an inactive ingredient ' is a huge thing in depression. The amount of professional care receives as well as the simple belief that this pill will help modify one's mood, well, seems to work for some. They get better while taking the placebo.

'While this study demonstrated a numerical improvement, they are disappointed that armodafinil did not reach statistical significance. Teva remains committed to advancing science in serious conditions affecting the central nervous process,' said Michael Hayden, Teva's president of global R&D.

Nuvigil was likely not going to be a blockbuster anyway, because it was an 'add on' drug for the treatment of major depression associated with bipolar I disorder. This is a serious area of concern, but it is not an huge market.

Furthermore, psychiatrists can already prescribe Nuvigil for depressive signs associated with bipolar I disorder as an off-label use. So while not shown to be effective, a psychiatrist can still give it a try if warranted.

Hitachi magic wand vibrator helps soothes the body muscles

The cost is not exorbitant & one time you invest in it, you can use the tool for at least 6-7 years. Proper handling further lengthens the life of the tool

The hitachi magic wand massager helps soothes the body muscles & eliminates pains in the back, neck & the shoulders. The vibrations cause the regeneration of dead tissues & also stimulate the growth of body tissues.

The fast vibration speed can be adjusted to a low speed of five,000 rpm & a high speed of 6,000 rpm

Twe tool is simple to make use of & can be used on body parts that are hard to reach. The long handle & the flexible head reach those body parts that are not basically obtainable to hands. The head is two.5 inches in diameter & the handle is 9 inches long.

The magic wand vibrator is widely used as a sex toy. When the head is placed against the genitals & the erogenous zones in the human body, the vibration causes stimulation of sensitive tissues thus sexually arousing a person. Females enjoy increased & more orgasms in the work of sexual activity while men enjoy elongated erection periods. The vibrator has enhanced effects in females & clitoral stimulation in them.

Elderly people can use this tool to decrease the pain intensity in the concerned body parts. The use of the vibrator against the body parts improves blood circulation because of the vibrations produced by the tool.

The magic wand vibrators are basically obtainable in the stores & may even be ordered online on various sites on the net.

These vibrators are very transportable & can be carried around without much difficulty.

Hitachi magic wand vibrator, also called the Hitachi magic wand massager is a tool that has been appreciated by a few people around the globe. A giant mass of people have been purchasing these vibrators for the past 30 years. There's a few advantages associated with the Hitachi magic wand vibrator.

Hitachi magic wand vibrators have been on the block for a long time now & the sales of these vibrators have doubled in the last two years. The vibrator is being used by people of all ages as per their requirements. The massager saves you the time of going to a masseur & getting a massage every weekend. You can sit back & use the massager by yourself.

There's various attachments that can be used with the magic wand vibrator. G-spotter & the wonder wand attachments are the most popular attachments that can be used together with the tool. The cord of the tool is as long as 6 feet & hence can be basically plugged in to a wall socket.

Potty training method of 3 days

A 3 day potty training by lora jensen and Intensive toilet training methods have become increasingly popular due to the demands of modern living and parent's time. Often, parents have to "schedule" time to take care of teaching this essential skill to their toddler. The benefits of using an intensive method far outweigh the drawbacks in trying to "let it take care of itself" and responsible parenthood requires taking the time.

I used Carol Cline's 3 day potty training method and found it simple to understand, implement and very useful. It was a successful method for us and I wrote the following article as a guide for parents who are considering using this method. It is simply a quick overview of what the book covers, chapter by chapter, so you can have an idea of what kind of content is in the book before you buy.

The book describes how to potty train in 3 days. It is 136 pages long and can easily be read in a few hours. I would imagine that the book is engagingly read by all parents about to embark on toilet training toddlers. However, Carol Cline intersperses the methodology with an historical overview of the process and general advice, gained from experience, of what to expect from your toddler during this time and also what you may experience yourself.

Chapter 1: The first chapter debunks the modern myth that children can toilet train themselves and that the later parents leave it to toilet train their children, the easier it will be. Children are potty trained later in the USA and Canada than in most of the world. She promotes a potty training method that is child centred and caring; but one that is also consistent and achieves results. Her belief is that potty training is a mutual achievement between the child and the parent and will deepen the relationship between them. This premise is carried throughout the book.

Chapter 2: This chapter sets out what is the best age to start potty training and includes guidelines for potty training toddlers aged between 18-24 months old with specific advice for parents who are trying to potty train older children.

Chapter 3: The key to successful potty training is knowing when your child is ready. This chapter goes into detail on the potty training readiness signs so you will know when the best time to start potty training your child is.

Chapter 4: Believe it or not, you need to prepare yourself first and then prepare your child. This chapter takes you through the necessity of relaxing through the process, how to handle your own expectations, what you should expect using the method, what to do and what not to do.

Chapter 5: This chapter takes you from your own expectations and the "adult mind" into the mind of your child so you can prepare them for their journey ahead. It explains the sequence of how children learn which helps you know what's going on. It also details what you can do beforehand to make the learning process easier e.g. taking "no-pressure" potty breaks before you actually start training so your child starts to become familiar with the process.

Chapter 6 and 7: These chapters take you step-by-step through what you need to have done before you start your "potty training in 3 days method" from clearing your schedule to the best foods to buy at the supermarket.

Chapter 8: This is the heart of the book. The pre-potty training "work" in the preceding chapters is not onerous and if the advice in them is followed, you will have done a lot of preparation that will reap rewards on your potty training days. The method is not set in stone but can be adapted to suit your family situation and needs. However, it does emphasise the need to be persistent, consistent, patient, loving and staying positive. It is a method that works with your child and treats them kindly throughout the process. It is a child centered approach that refocuses the adult mind into thinking of the world of a child. One of the best things about this method is that Carol Cline describes a very simple tool to encourage your toddler to use the potty that avoids the perennial "no".

The chapter also includes advice about night time potty training and observations and insights from other parents who have used the method. I found the chapter very, very useful - not least because of the methodology itself. It walks you through what you should expect, how you may feel, what to do if it goes badly and even what to do if it goes well!

Chapter 9: This chapter is a surprise inclusion. For those of us who are a little "rusty" on biology 101, this is the chapter to read! It is a basic biology lesson on our bodily functions. It then gives advice and guidance on how to ensure children adopt a healthy urination and bowel movement pattern.

Chapter 10: This is the chapter where Carol Cline leads you past thinking in terms of just potty training at home. It details how to approach potty training with your child's entire development and social situation in mind. As such it extends to teaching your child how to wipe their bum (with a novel system that won't block your plumbing with toilet paper) and how to wash their hands. At the end of the chapter, you won't be thinking about your child as a potty training toddler but as a "big kid" able to handle himself at kindergarten and pre-school.

Chapter 11: If you are about to start potty training a boy, a girl or twins this chapter will prove invaluable. It dismisses some of the myths and re-inforces the belief that every child is an individual. It deals with some typical obstacles and how to get past them in a positive way. If potty training has not worked for you in the past, or if you have a particularly stubborn child, then Carol Cline provides some very good adaptations to the method to cope with this situation. From the child's perspective, Carol Cline again puts you in their shoes and deals with some common fears your child may have and how to deal with them. I found the part on incentives and rewards particularly useful and it is something that I have put into practice in other areas of my parenting.

Chapter 12: Parents of children with Autism, Asperger's and Down Syndrome face particular challenges in trying to potty train. The chapter deals with these issues and covers area such as language issues, sensory problems, the stress of learning a new skill and visual aids to potty training. It also includes some observations and advice from parents who have been through and are going through a similar situation.

Chapter 13: This covers in a little more detail the "bumps in the road" and how to respond to them in a positive way.

Chapter 14: It may be that you feel that your child may have a medical problem and this chapter points you in the right direction on how to recognise it and what to do about it.

Chapter 15: "Out in the world" is the title of this chapter and this is where you will spend most of your time with your potty training toddler! It covers everything from going to the mall and on long haul flights; what to bring and suggestions for how to explain to your toddler about "special situations". Like any parent, I found planning trips and outings more stressful than I would like in the beginning and Carol Cline puts it into perspective so you can emerge from a trip to the mall having enjoyed yourself rather than making potty training the centre of your world.

In order to gain the most from the book, I would suggest purchasing it a month before you plan to potty train. You will have the time to read the book a few times and really absorb the methodology. This makes it easier to "get ahead" on the practical stuff like clearing your schedule and getting everything organised.

Android (operating system)

From Wikipedia, the free encyclopedia Jump to: navigation, search Android The green Android logo, designed by graphic designer Irina Blok. Android 4.2 "Jelly Bean" on the Nexus 4 Company / developer Google Open Handset Alliance Android Open Source Project Programmed in C, C++, Java OS family Unix-like Working state Current Source model Open source Initial release September 23, 2008 (2008-09-23) Latest stable release 4.2.2 Jelly Bean / February 11, 2013; 2 months ago (2013-02-11) Marketing target Smartphones Tablet computers Available language(s) Multi-lingual Package manager Google Play, APK Supported platforms ARM, MIPS, x86, I.MX Kernel type Monolithic (modified Linux kernel) Default user interface Graphical (Multi-touch) License Apache License 2.0 Linux kernel patches under GNU GPL v2 Official website www.android.com

Android is a Linux-based operating system designed primarily for touchscreen mobile devices such as smartphones and tablet computers. Initially developed by Android, Inc., which Google backed financially and later bought in 2005, Android was unveiled in 2007 along with the founding of the Open Handset Alliance: a consortium of hardware, software, and telecommunication companies devoted to advancing open standards for mobile devices. The first Android-powered phone was sold in October 2008.

Android is open source and Google releases the code under the Apache License. This open source code and permissive licensing allows the software to be freely modified and distributed by device manufacturers, wireless carriers and enthusiast developers. Additionally, Android has a large community of developers writing applications ("apps") that extend the functionality of devices, written primarily in a customized version of the Java programming language. In October 2012, there were approximately 700,000 apps available for Android, and the estimated number of applications downloaded from Google Play, Android's primary app store, was 25 billion.

These factors have contributed towards making Android the world's most widely used smartphone platform, overtaking Symbian in the fourth quarter of 2010, and the software of choice for technology companies who require a low-cost, customizable, lightweight operating system for high tech devices without developing one from scratch. As a result, despite being primarily designed for phones and tablets, it has seen additional applications on televisions, games consoles, digital cameras and other electronics. Android's open nature has further encouraged a large community of developers and enthusiasts to use the open source code as a foundation for community-driven projects, which add new features for advanced users or bring Android to devices which were officially released running other operating systems.

Android had a worldwide smartphone market share of 75% during the third quarter of 2012, with 750 million devices activated in total and 1.5 million activations per day. The operating system's success has made it a target for patent litigation as part of the so-called "smartphone wars" between technology companies.

History

Android, Inc. was founded in Palo Alto, California in October 2003 by Andy Rubin (co-founder of Danger), Rich Miner (co-founder of Wildfire Communications, Inc.), Nick Sears (once VP at T-Mobile), and Chris White (headed design and interface development at WebTV) to develop, in Rubin's words "smarter mobile devices that are more aware of its owner's location and preferences". The early intentions of the company were to develop an advanced operating system for digital cameras, when it was realised that the market for the devices was not large enough, and diverted their efforts to producing a smartphone operating system to rival those of Symbian and Windows Mobile (Apple's iPhone had not been released at the time). Despite the past accomplishments of the founders and early employees, Android Inc. operated secretly, revealing only that it was working on software for mobile phones. That same year, Rubin ran out of money. Steve Perlman, a close friend of Rubin, brought him $10,000 in cash in an envelope and refused a stake in the company.

Google acquired Android Inc. on August 17, 2005, making it a wholly owned subsidiary of Google. Key employees of Android Inc., including Rubin, Miner and White, stayed at the company after the acquisition. Not much was known about Android Inc. at the time, but many assumed that Google was planning to enter the mobile phone market with this move. At Google, the team led by Rubin developed a mobile device platform powered by the Linux kernel. Google marketed the platform to handset makers and carriers on the promise of providing a flexible, upgradable system. Google had lined up a series of hardware component and software partners and signaled to carriers that it was open to various degrees of cooperation on their part.

Speculation about Google's intention to enter the mobile communications market continued to build through December 2006. Reports from the BBC and the Wall Street Journal noted that Google wanted its search and applications on mobile phones and it was working hard to deliver that. Print and online media outlets soon reported rumors that Google was developing a Google-branded handset. Some speculated that as Google was defining technical specifications, it was showing prototypes to cell phone manufacturers and network operators. In September 2007, InformationWeek covered an Evalueserve study reporting that Google had filed several patent applications in the area of mobile telephony.

On November 5, 2007, the Open Handset Alliance, a consortium of technology companies including Google, device manufacturers such as HTC and Samsung, wireless carriers such as Sprint Nextel and T-Mobile, and chipset makers such as Qualcomm and Texas Instruments, unveiled itself, with a goal to develop open standards for mobile devices. That day, Android was unveiled as its first product, a mobile device platform built on the Linux kernel version 2.6. The first commercially available phone to run Android was the HTC Dream, released on October 22, 2008.

Since 2008, Android has seen numerous updates which have incrementally improved the operating system, adding new features and fixing bugs in previous releases. Each major release is named in alphabetical order after a dessert or sugary treat; for example, version 1.5 Cupcake was followed by 1.6 Donut. The latest release is 4.2 Jelly Bean. In 2010, Google launched its Nexus series of devices—a line of smartphones and tablets running the Android operating system, and built by a manufacturer partner. HTC collaborated with Google to release the first Nexus smartphone, the Nexus One. The series has since been updated with newer devices, such as the Nexus 4 phone and Nexus 10 tablet, made by LG and Samsung, respectively. Google releases the Nexus phones and tablets to act as their flagship Android devices, demonstrating Android's latest software and hardware features.

On 13 March 2013, it was announced by Larry Page in a blog post that Andy Rubin had moved from the Android division to take on new projects at Google. He was replaced by Sundar Pichai, who also continues his role as the head of Google's Chrome division, which develops Chrome OS.

Description

See also: List of features in Android and Android version history Interface

Android's user interface is based on direct manipulation, using touch inputs that loosely correspond to real-world actions, like swiping, tapping, pinching and reverse pinching to manipulate on-screen objects. The response to user input is designed to be immediate and provides a fluid touch interface, often using the vibration capabilities of the device to provide haptic feedback to the user. Internal hardware such as accelerometers, gyroscopes and proximity sensors are used by some applications to respond to additional user actions, for example adjusting the screen from portrait to landscape depending on how the device is oriented, or allowing the user to steer a vehicle in a racing game by rotating the device, simulating control of a steering wheel.

Android devices boot to the homescreen, the primary navigation and information point on the device, which is similar to the desktop found on PCs. Android homescreens are typically made up of app icons and widgets; app icons launch the associated app, whereas widgets display live, auto-updating content such as the weather forecast, the user's email inbox, or a news ticker directly on the homescreen. A homescreen may be made up of several pages that the user can swipe back and forth between, though Android's homescreen interface is heavily customisable, allowing the user to adjust the look and feel of the device to their tastes. Third party apps available on Google Play and other app stores can extensively re-theme the homescreen, and even mimic the look of other operating systems, such as Windows Phone. Most manufacturers, and some wireless carriers, customise the look and feel of their Android devices to differentiate themselves from the competition.

Present along the top of the screen is a status bar, showing information about the device and its connectivity. This status bar can be "pulled" down to reveal a notification screen where apps display important information or updates, such as a newly received email or SMS text, in a way that does not immediately interrupt or inconvenience the user. In early versions of Android these notifications could be tapped to open the relevant app, but recent updates have provided enhanced functionality, such as the ability to call a number back directly from the missed call notification without having to open the dialer app first. Notifications are persistent until read or dismissed by the user.

Applications Play Store on the Nexus 4. See also: Android software development and Google Play

Android has a growing selection of third party applications, which can be acquired by users either through an app store such as Google Play or the Amazon Appstore, or by downloading and installing the application's APK file from a third-party site. The Play Store application allows users to browse, download and update apps published by Google and third-party developers, and is pre-installed on devices that comply with Google's compatibility requirements. The app filters the list of available applications to those that are compatible with the user's device, and developers may restrict their applications to particular carriers or countries for business reasons. Purchases of unwanted applications can be refunded within 15 minutes of the time of download, and some carriers offer direct carrier billing for Google Play application purchases, where the cost of the application is added to the user's monthly bill. As of September 2012, there were more than 675,000 apps available for Android, and the estimated number of applications downloaded from the Play Store was 25 billion.

Applications are developed in the Java language using the Android software development kit (SDK). The SDK includes a comprehensive set of development tools, including a debugger, software libraries, a handset emulator based on QEMU, documentation, sample code, and tutorials. The officially supported integrated development environment (IDE) is Eclipse using the Android Development Tools (ADT) plugin. Other development tools are available, including a Native Development Kit for applications or extensions in C or C++, Google App Inventor, a visual environment for novice programmers, and various cross platform mobile web applications frameworks.

In order to work around limitations on reaching Google services due to Internet censorship in the People's Republic of China, Android devices sold in the PRC are generally customized to use state approved services instead.

Development

Android is developed in private by Google until the latest changes and updates are ready to be released, at which point the source code is made available publicly. This source code will only run without modification on select devices, usually the Nexus series of devices. With others, there are proprietary binaries which have to be provided by the manufacturer in order for Android to work.

Linux Architecture diagram

Android consists of a kernel based on Linux kernel version 2.6 and, from Android 4.0 Ice Cream Sandwich onwards, version 3.x, with middleware, libraries and APIs written in C, and application software running on an application framework which includes Java-compatible libraries based on Apache Harmony. Android uses the Dalvik virtual machine with just-in-time compilation to run Dalvik 'dex-code' (Dalvik Executable), which is usually translated from Java bytecode. The main hardware platform for Android is the ARM architecture. There is support for x86 from the Android-x86 project, and Google TV uses a special x86 version of Android. In 2013, Freescale announced Android on its i.MX processor, i.MX5X and i.MX6X series.

Android's Linux kernel has further architecture changes by Google outside the typical Linux kernel development cycle. Android does not have a native X Window System by default nor does it support the full set of standard GNU libraries, and this makes it difficult to port existing Linux applications or libraries to Android. Support for simple C and SDL applications is possible by injection of a small Java shim and usage of the JNI like, for example, in the Jagged Alliance 2 port for Android.

Certain features that Google contributed back to the Linux kernel, notably a power management feature called "wakelocks", were rejected by mainline kernel developers partly because they felt that Google did not show any intent to maintain its own code. Google announced in April 2010 that they would hire two employees to work with the Linux kernel community, but Greg Kroah-Hartman, the current Linux kernel maintainer for the stable branch, said in December 2010 that he was concerned that Google was no longer trying to get their code changes included in mainstream Linux. Some Google Android developers hinted that "the Android team was getting fed up with the process," because they were a small team and had more urgent work to do on Android.

In August 2011, Linus Torvalds said that "eventually Android and Linux would come back to a common kernel, but it will probably not be for four to five years". In December 2011, Greg Kroah-Hartman announced the start of the Android Mainlining Project, which aims to put some Android drivers, patches and features back into the Linux kernel, starting in Linux 3.3. Linux included the autosleep and wakelocks capabilities in the 3.5 kernel, after many previous attempts at merger. The interfaces are the same but the upstream Linux implementation allows for two different suspend modes: to memory (the traditional suspend that Android uses), and to disk (hibernate, as it is known on the desktop). The merge will be complete starting with Kernel 3.8, Google has opened a public code repository that contains their experimental work to re-base Android off Kernel 3.8.

The flash storage on Android devices is split into several partitions, such as "/system" for the operating system itself and "/data" for user data and app installations. In contrast to desktop Linux distributions, Android device owners are not given root access to the operating system and sensitive partitions such as /system are read-only. However, root access can be obtained by exploiting security flaws in Android, which is used frequently by the open source community to enhance the capabilities of their devices, but also by malicious parties to install viruses and malware.

Whether or not Android counts as a Linux distribution is a widely debated topic, with the Linux Foundation and Chris DiBona, Google's open source chief, in favour. Others, such as Google engineer Patrick Brady disagree, noting the lack of support for many GNU tools, including glibc, in Android.

Memory management

Since Android devices are usually battery-powered, Android is designed to manage memory (RAM) to keep power consumption at a minimum, in contrast to desktop operating systems which generally assume they are connected to unlimited mains electricity. When an Android app is no longer in use, the system will automatically suspend it in memory - while the app is still technically "open," suspended apps consume no resources (e.g. battery power or processing power) and sit idly in the background until needed again. This has the dual benefit of increasing the general responsiveness of Android devices, since apps don't need to be closed and reopened from scratch each time, but also ensuring background apps don't waste power needlessly.

Android manages the apps stored in memory automatically: when memory is low, the system will begin killing apps and processes that have been inactive for a while, in reverse order since they were last used (i.e. oldest first). This process is designed to be invisible to the user, such that users do not need to manage memory or the killing of apps themselves. However, confusion over Android memory management has resulted in third-party task killers becoming popular on the Google Play store; these third-party task killers are generally regarded as doing more harm than good.

Update schedule From left to right: HTC Dream (G1), Nexus One, Nexus S, Galaxy Nexus See also: Android version history

Google provides major updates, incremental in nature, to Android every six to nine months, which most devices are capable of receiving over the air. The latest major update is Android 4.2 Jelly Bean.

Compared to its chief rival mobile operating system, namely iOS, Android updates are typically slow to reach actual devices. For devices not under the Nexus brand, updates often arrive months from the time the given version is officially released. This is caused partly due to the extensive variation in hardware of Android devices, to which each update must be specifically tailored, as the official Google source code only runs on their flagship Nexus devices. Porting Android to specific hardware is a time- and resource-consuming process for device manufacturers, who prioritize their newest devices and often leave older ones behind. Hence, older smartphones are frequently not updated if the manufacturer decides it is not worth their time, regardless of whether the phone is capable of running the update. This problem is compounded when manufacturers customize Android with their own interface and apps, which must be reapplied to each new release. Additional delays can be introduced by wireless carriers who, after receiving updates from manufacturers, further customize and brand Android to their needs and conduct extensive testing on their networks before sending the update out to users.

The lack of after-sale support from manufacturers and carriers has been widely criticised by consumer groups and the technology media. Some commentators have noted that the industry has a financial incentive not to update their devices, as the lack of updates for existing devices fuels the purchase of newer ones, an attitude described as "insulting". The Guardian has complained that the complicated method of distribution for updates is only complicated because manufacturers and carriers have designed it that way. In 2011, Google partnered with a number of industry players to announce an "Android Update Alliance", pledging to deliver timely updates for every device for 18 months after its release. As of 2013, this alliance has never been mentioned since.

Open source community

Android has an active community of developers and enthusiasts who use the Android source code to develop and distribute their own modified versions of the operating system. These community-developed releases often bring new features and updates to devices faster than through the official manufacturer/carrier channels, albeit without as extensive testing or quality assurance; provide continued support for older devices that no longer receive official updates; or bring Android to devices that were officially released running other operating systems, such as the HP TouchPad. Community releases often come pre-rooted and contain modifications unsuitable for non-technical users, such as the ability to overclock or over/undervolt the device's processor. CyanogenMod is the most widely used community firmware, and acts as a foundation for numerous others.

Historically, device manufacturers and mobile carriers have typically been unsupportive of third-party firmware development. Manufacturers express concern about improper functioning of devices running unofficial software and the support costs resulting from this. Moreover, modified firmwares such as CyanogenMod sometimes offer features, such as tethering, for which carriers would otherwise charge a premium. As a result, technical obstacles including locked bootloaders and restricted access to root permissions are common in many devices. However, as community-developed software has grown more popular, and following a statement by the Librarian of Congress in the United States that permits the "jailbreaking" of mobile devices, manufacturers and carriers have softened their position regarding third party development, with some, including HTC, Motorola, Samsung and Sony, providing support and encouraging development. As a result of this, over time the need to circumvent hardware restrictions to install unofficial firmware has lessened as an increasing number of devices are shipped with unlocked or unlockable bootloaders, similar to the Nexus series of phones, although usually requiring that users waive their devices' warranties to do so. However, despite manufacturer acceptance, some carriers in the US still require that phones are locked down.

The unlocking and "hackability" of smartphones and tablets remains a source of tension between the community and industry, with the community arguing that unofficial development is increasingly important given the failure of industry to provide timely updates and/or continued support to their devices.