Misplaced Pages

TWRP (software)

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.

This is an accepted version of this page

#849150

66-507: Team Win Recovery Project ( TWRP ), pronounced "twerp" , is an open-source software custom recovery image for Android -based devices. It provides a touchscreen -enabled interface that allows users to install third-party firmware and back up the current system, functions usually not supported by stock recovery images. It is, therefore, often installed when flashing, installing, or rooting Android devices, although it does not require

132-406: A Pathways to Enable Open-Source Ecosystems (POSE) program to support open source innovation. The adoption of open-source software by industry is increasing over time. OSS is popular in several industries such as telecommunications , aerospace , healthcare , and media & entertainment due to the benefits it provides. Adoption of OSS is more likely in larger organizations and is dependent on

198-455: A basic file manager and a terminal emulator. It is fully themeable. In January 2017, the TWRP team released an Android application that allows flashing the recovery using root access. However, unlike the recovery, the app is not open source, although free of charge. This app is also shipped via the official TWRP images to rooted and non-rooted devices. It is installed in the system partition, making it

264-541: A bug needs to be fixed in their project. This is established by communicating with the OSS community through avenues such as bug reporting and tracking or mailing lists and project pages. Next, OSS developers select or are assigned to a task and identify a solution. Because there are often many different possible routes for solutions in OSS, the best solution must be chosen with careful consideration and sometimes even peer feedback . The developer then begins to develop and commit

330-507: A copy of the license is provided to recipients with the code. One important legal precedent for open-source software was created in 2008, when the Jacobson v Katzer case enforced terms of the Artistic license , including attribution and identification of modifications. The ruling of this case cemented enforcement under copyright law when the conditions of the license were not followed. Because of

396-439: A device to be rooted before installation. Since February 2016, the first three digits of the version number specify the version, and the fourth digit, separated from the others by a dash, specifies an update for a specific device. This could be a performance improvement, hotfix, bugfix, or just simply an update for a device. The main method of installing (" flashing ") this custom recovery on an Android device requires downloading

462-411: A form of version control in which the complete codebase , including its full history, is mirrored on every developer's computer. Compared to centralized version control (cf. monorepo ), this enables automatic management branching and merging , speeds up most operations (except pushing and fetching), improves the ability to work offline, and does not rely on a single location for backups. Git ,

528-454: A new bug. Early releases : The first version of the software should be released as early as possible so as to increase one's chances of finding co-developers early. Frequent integration: Code changes should be integrated (merged into a shared code base) as often as possible so as to avoid the overhead of fixing a large number of bugs at the end of the project life cycle. Some open-source projects have nightly builds where integration

594-508: A public good as it is available to everyone and does not decrease in value for others when downloaded by one person. Open source software is unique in that it becomes more valuable as it is used and contributed to, instead of diminishing the resource. This is explained by concepts such as investment in reputation and network effects . The economic model of open-source software can be explained as developers contribute work to projects, creating public benefits. Developers choose projects based on

660-415: A pull request to notify maintainers of a new change; a comment thread is associated with each pull request. This allows for focused discussion of code changes . Submitted pull requests are visible to anyone with repository access. A pull request can be accepted or rejected by maintainers. Once the pull request is reviewed and approved, it is merged into the repository. Depending on the established workflow,

726-447: A similar way user scripts and custom style sheets allow for web sites, and eventually publish the modification as a fork for users with similar preferences, and directly submit possible improvements as pull requests . The Open Source Initiative 's (OSI) definition is recognized by several governments internationally as the standard or de facto definition. OSI uses The Open Source Definition to determine whether it considers

SECTION 10

#1733114665850

792-592: A software license open source. The definition was based on the Debian Free Software Guidelines , written and adapted primarily by Perens . Perens did not base his writing on the "four freedoms" from the Free Software Foundation (FSF), which were only widely available later. Under Perens' definition, open source is a broad software license that makes source code available to the general public with relaxed or non-existent restrictions on

858-399: A source code repository that uses a distributed version control system are commonly made by means of a pull request , also known as a merge request . The contributor requests that the project maintainer pull the source code change, hence the name "pull request". The maintainer has to merge the pull request if the contribution should become part of the source base. The developer creates

924-467: A system-level app by default, so that it cannot be uninstalled from within Android without root access. However, TWRP now provides the user the freedom of choice for having the app. This mobile computing related article is a stub . You can help Misplaced Pages by expanding it . Open-source software Open-source software ( OSS ) is computer software that is released under a license in which

990-452: A truly distributed project, such as Linux , every contributor maintains their own version of the project, with different contributors hosting their own respective versions and pulling in changes from other users as needed, resulting in a general consensus emerging from multiple different nodes. This also makes the process of "forking" easy, as all that is required is one contributor stop accepting pull requests from other contributors and letting

1056-452: A version made specifically for the device, and then using a tool such as Fastboot or Odin . Some custom ROMs come with TWRP as the default recovery image. TWRP gives users the option to fully back up their device (including bootloader, system data, private applications, etc.) to revert to at any time, and a built-in file manager to delete files that may be causing problems on the device or add some to fix issues. As of 2019, TWRP supported

1122-422: A victory for OSS supporters. In open-source communities, instead of owning the software produced, the producer owns the development of the evolving software. In this way, the future of the software is open, making ownership or intellectual property difficult within OSS. Licensing and branding can prevent others from stealing it, preserving its status as a public good . Open source software can be considered

1188-404: Is a good or service, what can be considered a modification, governance through contract vs license, ownership and right of use. While there have been developments on these issues, they often lead to even more questions. The existence of these uncertainties in regulation has a negative impact on industries involved in technologies as a whole. Within the legal history of software as a whole, there

1254-539: Is absolutely another terrific way that individuals and organizations choose to contribute to open source projects. Groups like Open Collective provide a means for individuals to contribute monthly to supporting their favorite projects. Organizations like the Sovereign Tech Fund is able to contribute to millions to supporting the tools the German Government uses. The National Science Foundation established

1320-544: Is done automatically . Several versions: There should be at least two versions of the software. There should be a buggier version with more features and a more stable version with fewer features. The buggy version (also called the development version) is for users who want the immediate use of the latest features and are willing to accept the risk of using code that is not yet thoroughly tested. The users can then act as co-developers, reporting bugs and providing bug fixes. High modularization: The general structure of

1386-404: Is innovative since open-source programs are the product of collaboration among a large number of different programmers. The mix of divergent perspectives, corporate objectives, and personal goals speeds up innovation. Moreover, free software can be developed in accordance with purely technical requirements. It does not require thinking about commercial pressure that often degrades the quality of

SECTION 20

#1733114665850

1452-560: Is legal variety in this definition. Some jurisdictions attempt to expand or reduce this conceptualization for their own purposes. For example, The European Court of Justice defines a computer program as not including the functionality of a program, the programing language , or the format of data files. By limiting protections of the different aspects of software, the law favors an open-source approach to software use. The US especially has an open approach to software, with most open-source licenses originating there. However, this has increased

1518-537: Is no single central version of the codebase; instead, each user has a working copy and the full change history. Advantages of DVCS (compared with centralized systems) include: Disadvantages of DVCS (compared with centralized systems) include: Some originally centralized systems now offer some distributed features. Team Foundation Server and Visual Studio Team Services now host centralized and distributed version control repositories via hosting Git. Similarly, some distributed systems now offer features that mitigate

1584-468: Is theoretically challenging in economic models, it is explainable as a sustainable social activity that requires resources. These resources include time, money, technology and contributions. Many developers have used technology funded by organizations such as universities and governments, though these same organizations benefit from the work done by OSS. As OSS grows, hybrid systems containing OSS and proprietary systems are becoming more common. Throughout

1650-447: The copyright holder grants users the rights to use, study, change, and distribute the software and its source code to anyone and for any purpose. Open-source software may be developed in a collaborative, public manner. Open-source software is a prominent example of open collaboration , meaning any capable user is able to participate online in development, making the number of possible contributors indefinite. The ability to examine

1716-889: The distributed version control system (DVCS) are examples of tools, often open source, that help manage the source code files and the changes to those files for a software project in order to foster collaboration. CVCS are centralized with a central repository while DVCS are decentralized and have a local repository for every user. concurrent versions system (CVS) and later Subversion (SVN) and Git are examples of CVCS. The repositories are hosted and published on source-code-hosting facilities such as GitHub . Open-source projects use utilities such as issue trackers to organize open-source software development. Commonly used bug trackers include Bugzilla and Redmine . Tools such as mailing lists and IRC provide means of coordination and discussion of bugs among developers. Project web pages, wiki pages, roadmap lists and newsgroups allow for

1782-458: The Bazaar , open-source influential contributor Eric S. Raymond suggests a model for developing OSS known as the bazaar model. Raymond likens the development of software by traditional methodologies to building a cathedral, with careful isolated work by individuals or small groups. He suggests that all software should be developed using the bazaar style, with differing agendas and approaches. In

1848-630: The Public Interest . Within Europe some notable organizations are Free Software Foundation Europe , open-source projects EU (OSP) and OpenForum Europe (OFE). One Australian organization is Linux Australia while Asia has Open source Asia and FOSSAsia . Free and open source software for Africa (FOSSFA) and OpenAfrica are African organizations and Central and South Asia has such organizations as FLISOL and GRUP de usuarios de software libre Peru . Outside of these, many more organizations dedicated to

1914-569: The United States has focused on national security in regard to open-source software implementation due to the perceived threat of the increase of open-source software activity in countries like China and Russia, with the Department of Defense considering multiple criteria for using OSS. These criteria include: if it comes from and is maintained by trusted sources, whether it will continue to be maintained, if there are dependencies on sub-components in

1980-473: The advancement of open-source software exist. FOSS products are generally licensed under two types of licenses: permissive licensing and copyleft licensing . Both of these types of licenses are different than proprietary licensing in that they can allow more users access to the software and allow for the creation of derivative works as specified by the terms of the specific license, as each license has its own rules. Permissive licenses allow recipients of

2046-402: The bazaar model should exhibit the following patterns: Users should be treated as co-developers: The users are treated like co-developers and so they should have access to the source code of the software. Furthermore, users are encouraged to submit additions to the software, code fixes for the software, bug reports , documentation, etc. Having more co-developers increases the rate at which

TWRP (software) - Misplaced Pages Continue

2112-466: The code facilitates public trust in the software. Open-source software development can bring in diverse perspectives beyond those of a single company. A 2024 estimate of the value of open-source software to firms is $ 8.8 trillion, as firms would need to spend 3.5 times the amount they currently do without the use of open source software. Open-source code can be used for studying and allows capable end users to adapt software to their personal needs in

2178-477: The code may need to be tested before being included into official release. Therefore, some projects contain a special branch for merging untested pull requests. Other projects run an automated test suite on every pull request, using a continuous integration tool, and the reviewer checks that any new code has appropriate test coverage. The first open-source DVCS systems included Arch , Monotone , and Darcs . However, open source DVCSs were never very popular until

2244-414: The code. The code is then tested and reviewed by peers. Developers can edit and evolve their code through feedback from continuous integration . Once the leadership and community are satisfied with the whole project, it can be partially released and user instruction can be documented. If the project is ready to be released, it is frozen, with only serious bug fixes or security repairs occurring. Finally,

2310-403: The codebases gradually grow apart. This arrangement, however, can be difficult to maintain, resulting in many projects choosing to shift to a paradigm in which one contributor is the universal "upstream", a repository from whom changes are almost always pulled. Under this paradigm, development is somewhat recentralized, as every project now has a central repository that is informally considered as

2376-427: The company's IT usage, operating efficiencies, and the productivity of employees. Industries are likely to use OSS due to back-office functionality, sales support, research and development, software features, quick deployment, portability across platforms and avoidance of commercial license management. Additionally, lower cost for hardware and ownership are also important benefits. Organizations that contribute to

2442-554: The creation and adaptation of custom source code branches ( forks ) whose purpose might differ from the original project. In addition, it permits developers to locally clone an existing code repository and work on such from a local environment where changes are tracked and committed to the local repository allowing for better tracking of changes before being committed to the master branch of the repository. Such an approach enables developers to work in local and disconnected branches, making it more convenient for larger distributed teams. In

2508-467: The development and expansions of free and open-source software movements exist all over the world. These organizations are dedicated to goals such as teaching and spreading technology. As listed by a former vice president of the Open Source Initiative , some American organizations include the Free Software Foundation , Software Freedom Conservancy , the Open Source Initiative and Software in

2574-461: The distribution of project information that focuses on end users. The basic roles OSS participants can fall into multiple categories, beginning with leadership at the center of the project who have control over its execution. Next are the core contributors with a great deal of experience and authority in the project who may guide the other contributors. Non-core contributors have less experience and authority, but regularly contribute and are vital to

2640-601: The focus on patent rights within these licenses, which has seen backlash from the OSS community, who prefer other forms of IP protection. Another issue includes technological protection measures (TPM) and digital rights management (DRM) techniques which were internationally legally recognized and protected in the 1996 World Intellectual Property Organization (WIPO) Treaty . Open source software proponents disliked these technologies as they constrained end-users potentially beyond copyright law. Europe responded to such complaints by putting TPM under legal controls, representing

2706-417: The installation of custom ROMs (i.e. custom operating systems such as LineageOS , or the latest Android release), kernels, add-ons (Google Apps, Magisk , themes, etc.), and other various mods. Wiping, backing up, restoring, and mounting various device partitions , such as the system, boot, userdata, cache, and internal storage partitions are also supported. TWRP also supports file transfer via MTP , and has

TWRP (software) - Misplaced Pages Continue

2772-696: The issues of checkout times and storage costs, such as the Virtual File System for Git developed by Microsoft to work with very large codebases, which exposes a virtual file system that downloads files to local storage only as they are needed. A distributed model is generally better suited for large projects with partly independent developers, such as the Linux Kernel . It allows developers to work in independent branches and apply changes that can later be committed, audited and merged (or rejected) by others. This model allows for better flexibility and permits for

2838-455: The local repository, and once the development is done, the change should be integrated into the central repository as soon as possible. Organizations utilizing this centralize pattern often choose to host the central repository on a third party service like GitHub , which offers not only more reliable uptime than self-hosted repositories, but can also add centralized features like issue trackers and continuous integration . Contributions to

2904-480: The many benefits provided, a huge issue to be considered is cybersecurity . While accidental vulnerabilities are possible, so are attacks by outside agents. Because of these fears, governmental interest in contributing to the governance of software has become more prominent. However, these are the broad strokes of the issue, with each country having their own specific politicized interactions with open-source software and their goals for its implementation. For example,

2970-560: The mid 2000s, more and more tech companies have begun to use OSS. For example, Dell's move of selling computers with GNU/Linux already installed. Microsoft itself has launched a Linux-based operating system despite previous animosity with the OSS movement. Despite these developments, these companies tend to only use OSS for certain purposes, leading to worries that OSS is being taken advantage of by corporations and not given anything in return. While many governments are interested in implementing and promoting open-source software due to

3036-505: The number of people employed in the IT sector. OSS can be highly reliable when it has thousands of independent programmers testing and fixing bugs of the software. Open source is not dependent on the company or author that originally created it. Even if the company fails, the code continues to exist and be developed by its users. OSS is flexible because modular systems allow programmers to build custom interfaces, or add new abilities to it and it

3102-419: The official repository, managed by the project maintainers collectively. While distributed version control systems make it easy for new developers to "clone" a copy of any other contributor's repository, in a central model, new developers always clone the central repository to create identical local copies of the code base. Under this system, code changes in the central repository are periodically synchronized with

3168-435: The perceived benefits or costs, such as improved reputation or value of the project. The motivations of developers can come from many different places and reasons, but the important takeaway is that money is not the only or even most important incentivization . Because economic theory mainly focuses on the consumption of scarce resources, the OSS dynamic can be hard to understand. In OSS, producers become consumers by reaping

3234-404: The potential to quicken innovation and create of social value. In France for instance, a policy that incentivized government to favor free open-source software increased to nearly 600,000 OSS contributions per year, generating social value by increasing the quantity and quality of open-source software. This policy also led to an estimated increase of up to 18% of tech startups and a 14% increase in

3300-574: The project is fully released and only changed through minor bug fixes. Open source implementation of a standard can increase adoption of that standard. This creates developer loyalty as developers feel empowered and have a sense of ownership of the end product. Moreover, lower costs of marketing and logistical services are needed for OSS. OSS can be a tool to promote a company's image, including its commercial products. The OSS development approach has helped produce reliable, high quality software quickly and inexpensively. Open source development offers

3366-759: The project's development. New contributors are the least experienced but with mentorship and guidance can become regular contributors. Some possible ways of contributing to open-source software include such roles as programming , user interface design and testing, web design , bug triage , accessibility design and testing, UX design , code testing, and security review and testing. However, there are several ways of contributing to OSS projects even without coding skills. For example, some less technical ways of participating are documentation writing and editing, translation , project management , event organization and coordination, marketing, release management, community management, and public relations and outreach. Funding

SECTION 50

#1733114665850

3432-431: The rewards of contributing to a project. For example, a developer becomes well regarded by their peers for a successful contribution to an OSS project. The social benefits and interactions of OSS are difficult to account for in economic models as well. Furthermore, the innovation of technology creates constantly changing value discussions and outlooks, making economic model unable to predict social behavior. Although OSS

3498-490: The same license while weak copyleft licenses require the use of the same license only under certain conditions. Examples of this type of license include the GNU family of licenses , and the MPL and EPL licenses. The similarities between these two categories of licensing include that they provide a broad grant of copyright rights, require that recipients preserve copyright notices, and that

3564-500: The similarity of the Artistic license to other open-source software licenses, the ruling created a precedent that applied widely. Examples of free-software license / open-source licenses include Apache licenses , BSD licenses , GNU General Public Licenses , GNU Lesser General Public License , MIT License , Eclipse Public License and Mozilla Public License . Several gray areas exist within software regulation that have great impact on open-source software, such as if software

3630-485: The software "in any manner they see fit, without requiring that they pay the author(s) of the software a royalty or fee for engaging in the listed activities." Despite initially accepting it, Richard Stallman of the FSF now flatly opposes the term "Open Source" being applied to what they refer to as "free software". Although he agrees that the two terms describe "almost the same category of software", Stallman considers equating

3696-401: The software evolves. Linus's law states that given enough eyeballs all bugs are shallow. This means that if many users view the source code, they will eventually find all bugs and suggest how to fix them. Some users have advanced programming skills, and furthermore, each user's machine provides an additional testing environment. This new testing environment offers the ability to find and fix

3762-484: The software should be modular allowing for parallel development on independent components. Dynamic decision-making structure: There is a need for a decision-making structure, whether formal or informal, that makes strategic decisions depending on changing user requirements and other factors. Compare with extreme programming . The process of Open source development begins with a requirements elicitation where developers consider if they should add new features or if

3828-453: The software to implement the author's copyright rights without having to use the same license for distribution. Examples of this type of license include the BSD , MIT , and Apache licenses . Copyleft licenses are different in that they require recipients to use the same license for at least some parts of the distribution of their works. Strong copyleft licenses require all derivative works to use

3894-568: The software, component security and integrity, and foreign governmental influence. Another issue for governments in regard to open source is their investments in technologies such as operating systems , semiconductors , cloud , and artificial intelligence . These technologies all have implications for global cooperation, again opening up security issues and political consequences. Many countries have to balance technological innovation with technological dependence in these partnerships. For example, after China's open-source dependent company Huawei

3960-425: The software. Commercial pressures make traditional software developers pay more attention to customers' requirements than to security requirements, since such features are somewhat invisible to the customer. In open-source software development, tools are used to support the development of the product and the development process itself. Version control systems such as Centralized Version control system (CVCS) and

4026-597: The terms incorrect and misleading. Stallman also opposes the professed pragmatism of the Open Source Initiative , as he fears that the free software ideals of freedom and community are threatened by compromising on the FSF's idealistic standards for software freedom. The FSF considers free software to be a subset of open-source software, and Richard Stallman explained that DRM software, for example, can be developed as open source, despite that it does not give its users freedom (it restricts them), and thus does not qualify as free software. In his 1997 essay The Cathedral and

SECTION 60

#1733114665850

4092-514: The traditional model of development, which he called the cathedral model, development takes place in a centralized way. Roles are clearly defined. Roles include people dedicated to designing (the architects), people responsible for managing the project, and people responsible for implementation. Traditional software engineering follows the cathedral model. The bazaar model, however, is different. In this model, roles are not clearly defined. Some proposed characteristics of software developed using

4158-437: The use and modification of the code. It is an explicit "feature" of open source that it puts very few restrictions on the use or distribution by any organization or user, in order to enable the rapid evolution of the software. According to Feller et al. (2005), the terms "free software" and "open-source software" should be applied to any "software products distributed under terms that allow users" to use, modify, and redistribute

4224-555: The world's most popular version control system, is a distributed version control system. In 2010, software development author Joel Spolsky described distributed version control systems as "possibly the biggest advance in software development technology in the [past] ten years". Distributed version control systems (DVCS) use a peer-to-peer approach to version control , as opposed to the client–server approach of centralized systems. Distributed revision control synchronizes repositories by transferring patches from peer to peer. There

4290-404: Was much debate on whether to protect it as intellectual property under patent law , copyright law or establishing a unique regulation. Ultimately, copyright law became the standard with computer programs being considered a form of literary work, with some tweaks of unique regulation. Software is generally considered source code and object code , with both being protectable, though there

4356-400: Was prevented from using Google's Android system in 2019, they began to create their own alternative operating system: Harmony OS . Germany recently established a Sovereign Tech Fund , to help support the governance and maintenance of the software that they use. Pull request In software development , distributed version control (also known as distributed revision control ) is

#849150