[MOD][4.1.2 or 4.2.1][GPL] OpenPDroid [v1.0, 2013-01-14]

• Two major security issues are fixed, which allow apps to bypass many or all PDroid or PDroid 2.0 settings. (We are in the process of notifying CollegeDev of these issues, and sample code will not be released for at least a week to give him a chance to fix the problems in PDroid 2.0. Fixes have been added to PDroid in auto-patcher, so if you are using PDroid please consider re-patching your ROM).
• It is available for Android 4.2.1
• Database access threading has been rewritten, as the implementation actually caused bottlenecks and didn't protect from simultaneous read-writes (which is generally the goal of this type of code)
• A bug which was causing 'null pointer exceptions' to occur (but not a crash) is fixed.
• Other code tidy-up or restructuring which doesn't change functionality

• The intention of OpenPDroid is to have a PDroid version which is developed in the open, and which welcomes (although doesn't necessarily always adopt) user input - especially code. This means that the source for OpenPDroid versions in progress is on a public repository (Github at the moment), that changes are put into the Github as they are made, and that other people can contribute code to it. We also hope that by having engaging people more in the development process, there will be more eyes trying to understand the code, and so security-related issues will be identified and address more efficiently.
• We also want to make the discussion/decision making processes for what is in and what is out transparent, so that users can understand why some things are included and others are not, and actually influence the decision-making process.

• mateor's auto-patcher (available for OS X, Linux and Windows) is the recommended way if you are not familiar with building from source, and have a supported ROM (CM10, CM10.1, AOKP Jellybean 4.1.2, AOKP Jellybean 4.2.1, AOSP 4.1.2, and AOSP 4.2.1).
• Patch and build a ROM from source (see How do I compile a ROM with OpenPDroid). Patches are provided for: CM10, CM10.1, AOKP jb, AOKP jb-mr1, AOSP 4.1.2, AOSP 4.2.1

• The source-code patches from the OpenPDroidPatches repository: . Note that there are two branches: 4.2.1 and 4.1.2. These source patches presently work against numerous roms (including CM 10/10.1, AOKP 4.1.2/4.2.1, AOSP 4.1.2/4.2.1, and potentially others)
  [*] Complete repositories for the modified sections of the system are likewise located in the [URL=https://github.com/OpenPDroid/]OpenPDroid github. There are several repositories and branches; see the section 'What are all these repos and branches?' for more details about the content of the github.
  
  What is the licence?
  PDroid was under under the GPL v3 licence (as shown on the Google Code page), and as a result all derivative works (e.g. OpenPDroid) are likewise under the GPL v3 (or later) licence. Thus, OpenPDroid is under the GPL v3 licence, with no additional special conditions. The only way a PDroid derivative can be under any other licence is if the author contacts Syvat, gets him to agree provide PDroid under another licence, and then the author extends it.
  
  Who's work is it?
  PDroid was original developed by Syvat (with contributions and ports from others such as Pastime1971 and Mateor), and then CollegeDev extended it to created PDroid 2.0 (previously called PDroid Addon, then PDroid Extension). PDroid 2.0 has been forked by FFU5y, Mateor and wbedard to create OpenPDroid. Thus, OpenPDroid is the product of the work of many.
  The following list includes all the contributors I know of for any of these version of the core (in alphabetical order):
  • CollegeDev (PDroid 2.0)
  • FFU5y (OpenPDroid)
  • Mateor (Porting PDroid to 4.x, porting PDroid 2.0 to 4.1.2, OpenPDroid)
  • Pastime1971 (Porting PDroid to 4.x, porting PDroid 2.0 to 4.1.2)
  • Syvat (PDroid)
  • Wbedard (OpenPDroid)
  
  How do I report issues?
  The best way to report an issue is to lodge it in github, although you may want to also post in this thread to let others know that the issue exists (and has been lodged). Please ensure you provide details of the issue you are experiencing (i.e. under what circumstances does it happen, what do you observe, etc) and please include a logcat: see how to get a logcat.
  If you don't have a Github account, you can post the issue here (and note that you haven't lodged it in Github) so one of the team can add the issue to Github.
  
  I want to contribute
  Great! The whole point of OpenPDroid is to encourage community contribution in the form of ideas, testing, code, etc.
  Presently, there isn't really a lot (read: any) documentation about how OpenPDroid works. However, this will be forthcoming, as will an API specification for the Privacy service, which will allow you to write your own management application (like PDroid Manager or the PDroid 2.0 App) if you so desire.
  Right now, these are the particular areas of the service which would benefit from developer/code contributions.
  • Transient caching of privacy settings read from the database, ideally with destruction of cache entries when they are too old or memory conditions are low
  • Refining the locking code to ensure that reads are not unduly held up by write locks (note: this isn't a problem *yet*, but will be with the inclusion of batch support. More details soon).
  • Other performance optimisations
  • Adding good quality code comments - mainly function descriptions, etc
  • Back-porting of OpenPDroid to pre-4.1.2, so users currently only able to use PDroid can move to OpenPDroid and get the new features.
  There are many other things you can work on, including adding whole new options (i.e. security features). If you are planning on creating new security features, however, please lodge the enhancement in github first so it can be discussed. Not every feature which seems like a good idea will be a good fit for OpenPDroid, and it may save some time if a prospective feature can be refined before it is fully coded.
  
  How do I compile a ROM with OpenPDroid
  To build a ROM with OpenPDroid, you will need to patch the source code using the provided patches, and then build as you normally would.
  To patch the source:
  • Download the most relevant of the source code patch packages attached to this post
  • Extract the patch files from the package
  • On the command line, go to the root of your Android source code: it will contain folders such as 'build', 'frameworks', 'vendor', etc.
  • Patch the source code with each patch file using the following command
    
    Code:

    patch -p1 < <patch_filename>

  You can then build your ROM as you would normally.
  If you have previously built the ROM in the folder you are using, or you have previously built PDroid 2.0, Syvat's original PDroid, etc it can be helpful to delete the following directories:
  • out/target/common/obj/JAVA_LIBRARIES/framework_intermediates
  • out/target/common/obj/JAVA_LIBRARIES/framework2_intermediates
  • out/target/common/obj/JAVA_LIBRARIES/telephony-common_intermediates
  Not all of these directories will exist for all ROMs, so if you try to delete one and it is missing that is not cause for concern.
  
  What (specifically) can I control with OpenPDroid?
  Currently, access to the following data and functions can be controlled (note this list exactly matches PDroid 2.0):
  
  Code:

  [b]Data access:[/b]
  Device ID (IMEI/MEID/ESN)
  Phone/voicemail number
  Sim Card Serial (ICCID)
  Subscriber ID (IMSI)
  Source number of incoming calls
  Destination number of outgoing calls
  Network location
  GPS location
  Authentication credentials
  List of accounts, including identifiers (e.g. gmail e-mail address)
  Contact list and details
  Call log
  Calendar
  Read and send SMS
  Read and send MMS
  Record audio (not phone calls)
  Camera
  Browser bookmarks and history
  System logs
  Wifi Info, such as current access point, IP address
  Network information (detailed network information such as connection state, IP address, etc)
  Android ID (a unique installation ID for your Android installation)
  SIM information (your phone operator and country)
  Restrict access to iptables command
  ICC Access (reading or writing SMS on the SIM or R-UIM)
  
  [b]Actions:[/b]
  Make phone calls
  Start on Boot (or more accurately, get notified when the boot is complete)
  Switch Wifi State (turn wifi on and off, change access points)
  Switch network state (turn off or on mobile data)
  
  [b]Other[/b]
  Force online state (always tell the app that the device is online: only needed if denying Wifi info and/or Network info)

  
  Known Issues
  Thanks to those users who have posted bug details, we now have a list of known issues. I have tried to indicate which will be fixed in the next release, but it is tentative. These issues can also be found (and discussed) on the github issues list
  • 
    Requests for tower location are always blocked (ETA unknown)
    Device lags when GPS is active (ETA: next release; experimental fix in 'devel' branch of 4.2.1-based ROMs: same fix as the below camera lag issue)
    Camera lags when OpenPDroid is installed (ETA: next release; experimental fix in 'devel' branch of 4.2.1-based ROMs)
    
  
  What are all these repos and branches?
  In the github account containing the OpenPDroid repositories, there are numerous repositories. Many of these are OpenPdroid related: but not quite all of them. In addition, not all of them are relevant to each ROM.
  The main repositories to be aware of are:
  platform_frameworks_base
  This contains the framework/base/* code, which constitutes the most important guts of OpenPDroid in 4.1.2 and 4.2.1. Other projects sometimes use the name android_frameworks_base for this.
  platform_frameworks_opt_telephony
  This contains the framework/opt/telephony code, which was split out from framework/base/* in 4.2.1.
  platform_build
  This contains the build code, mostly makefiles, and is present in 4.1.2 and 4.2.1.
  platform_libcore
  This contains core operational code outside of the framework (e.g. executing shell tasks, etc).
  platform_packages_apps_mms
  This contains the code for the Mms app, for 4.1.2 and 4.2.1.
  platform_packages_apps_mms
  This contains the code for the Mms app, which is modified to affect the ability of apps to send and receive MMS.
  platform_packages_apps_videoeditor
  This contais the code for the VideoEditor app. The only change here is including 'framework2', which is only required for AOSP 4.1.2.
  platform_system_core
  This contais a range of important core code, and is modified only for AOSP 4.1.2 to include 'framework2.jar' in the paths included at boot time.
  
  The branches used include two key naming components. First, the rom:
  e.g.
  cm-10.1* = CyanogenMod 10.1
  cm-jellybean* = CyanogenMod 10, cutting edge
  cm-jellybean-stable* = CyanogenMod 10, stable release
  aokp-jb-mr1* = AOKP 4.2.1-based
  aokp-jb* (without the mr1) = AOKP 4.1.2-based
  jb-mr0* = AOSP 4.1.2
  jb-mr1* = AOSP 4.2.1
  pa-jellybean* = ParanoidAndroid (currently buggy)
  
  then the OpenPDroid version:
  -openpdroid = the current stable release of OpenPDroid
  -openpdroid-devel = the current development line of OpenPDroid
  
  For development, the jb-mr1-release-openpdroid-devel is where I do my initial development, and I think expand it to be on the other -devel branches once I've tested it a bit.
  
  FAQ
  How do I include PDroid Manager in the ROM I am building so it can update from Google Play: see here
  How do I include PDroid Manager in the ROM I am building so it is compiled during build: see here: TamCore provided a fix for the problem he mentioned, and it has been merged.
  How do I build using the bleeding-edge (devel) code: see here, although there is a bit more to it than that. I'll provide extra details when time permits, but the important stuff is in this thread.
  
  
  I have a question or issue not covered in this post
  We'll be adding more to this post in the next day or two. Please be patient =)
  
  Note to mods
  I wasn't sure if this belonged in this forum, or in 'Apps and Games' but since it is not trivial to install I figured this was a safer bet.

• 
  
  In the OpenPDroid github page, you can now find build patches for all the iterations of Pdroid/OpenPdroid. The patches go from 2.3 to 4.2.2, and all have been reformatted so as to be applied in the same manner as recommended for the 4.2 patches in the first post.
  • You can see all the build patches here.
    
  • The patches were originally worked on by svyat, but have been contributed to by CollegeDev, FFU5y, pastime1971, me and wbedard among several others.
• I have also finished converting and moving the original PDroid project tree I have from Svyat. I consider this something worth rescuing and representing, the full commit history of the Pdroid project is preserved. I also pushed that to the OpenPDroid page, you can see the PDroidHistory here.

• Build patches are here.
• PDroid project history is here.

cd ~/android/system/build; git checkout -b pdroid; patch -p1 < ~/openpdroid_4.2.1_build.patch
cd ~/android/system/libcore; git checkout -b pdroid; patch -p1 < openpdroid_4.2.1_libcore.patch
cd ~/android/system/packages/apps/Mms; git checkout -b pdroid; patch -p1 < openpdroid_4.2.1_Mms.patch
cd ~/android/system/frameworks/base; git checkout -b pdroid; patch -p1 < openpdroid_4.2.1_frameworks_base.patch
cd ~/android/system/frameworks/opt/telephony; git checkout -b pdroid; patch -p1 < ~/openpdroid_4.2.1_frameworks_opt_telephony.patch
cd ~/android/system; . build/envsetup.sh; brunch <DEVICE_TARGET>

cd ~/android/system
rm -rf out/target/common/obj/JAVA_LIBRARIES/framework_intermediates \
out/host/common/obj/JAVA_LIBRARIES/layoutlib_intermediates \
out/target/common/obj/JAVA_LIBRARIES/telephony-common_intermediates \
out/target/common/obj/APPS/Mms_intermediates

cd ~/android; make clobber

cd ~/android/system/build; git checkout . ; git clean -df
cd ~/android/system/libcore; git checkout . ; git clean -df
cd ~/android/system/frameworks/base; git checkout . ; git clean -df
cd ~/android/system/frameworks/opt/telephony; git checkout . ; git clean -df
cd ~/android/system/packages/apps/Mms; git checkout . ; git clean -df
cd ~/android/system; repo abandon pdroid

dirtyreturn said:

Hey mateorod. How does the issue with GPS/openpdroid look? Would you need a tester of some sort?

Click to expand...

Click to collapse