[APP+MOD][4.1.2+ | STOCK][IRC-CHANNEL][GPL] PDroid 2.0 [2013-05-16 v1.57.1]

Do you want to see PDroid2.0 at Google Play?


  • Total voters
    171
  • Poll closed .
Search This thread

CollegeDev

Senior Member
Jun 28, 2012
270
778
0
Disclaimer:

Code:
/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. 
 * Please do some research if you have any concerns about features 
 * included in this Patch and application before flashing it! YOU are 
 * choosing to make these modifications, and if you point the finger 
 * at me for messing up your device, I will laugh at you.
 *
 */

General & Credits:

First of all, many many thanks to svyat who developed the main application PDroid, thank you!! Before I describe some new features (and old too) I want to say that the Application PDroid2.0.apk is written completely by my own. I just took some styles from svyat to give users the "old PDroid" feeling :) It is a stand alone application and does not need PDroid itself anymore. You just have to apply my patches, install the application and have fun :)

App description:

PDroid 2.0 allows blocking access for any installed application to the following data separately:

  • Device ID (IMEI/MEID/ESN)
  • Subscriber ID (IMSI)
  • SIM serial (ICCID)
  • Phone and mailbox number
  • Incoming call number
  • Outgoing call number
  • GPS location
  • Network location
  • List of accounts (including your google e-mail address)
  • Account auth tokens
  • Contacts
  • Call logs
  • Calendar
  • SMS
  • MMS
  • Browser bookmarks and history
  • System logs
  • SIM info (operator, country)
  • Network info (operator, country)
  • IP Tables(until now only for Java process)
  • Android ID
  • Call Phone
  • Send SMS
  • Send MMS
  • Record Audio
  • Access Camera
  • Force online state (fake online state to permanent online)
  • Wifi Info
  • ICC Access (integrated circuit-card access, for reading/writing sms on ICC)
  • Switch network state (e.g. mobile network)
  • Switch Wifi State
  • Start on Boot (prevents that application gets the INTENT_BOOT_COMPLETE Broadcast)


Donators:

  • Big credits to ce4. He is the first donator. Many thanks :)
  • Another thankful guy: schertling. Thank you for your donation :)
  • Thanks to MacDog_AU, who also donated a beer :)
 
Last edited:

CollegeDev

Senior Member
Jun 28, 2012
270
778
0
Translators:
Big thanks to following translators of PDroid2.0, who made the app available in their native language:


PDroid2.0 Flash-Repo:
@ all guys who ever build a ROM with PDroid2.0, please upload the ROM here and post it in this thread or send me the link via pn. I need following additional information:
  • What ROM is it?
  • When do you build it (optional)
  • Which version of PDroid is included (Framework)
  • For which device is the ROM
You will get full credits in the OP and the link for the REPO will also be present inside the description for the app in googleplay.

How does it work? Just download the ROM for your device and flash it. Then you're able to use PDroid2.0!
Side-Note related the devices:
Nexus 4 = mako
Nexus 7 Wi-Fi = grouper
Nexus 7 GSM = tilapia
Nexus 10 = manta
THX to Koetermann!

Galaxy S2 (I9100):

  • ROM: PACMAN
    Date: 02.15.2013
    MD5: c810f45732bf1f3fd82eccd7bfda2ca0
    PD-Version: 1.57
    Contributor: AuSSiELaMbChOpS
    Download: here
    ----------------------------------------------
  • ROM: CM10.1
    Date: 18.05.2013
    MD5: unknown
    PD-Version: 1.57
    Side-Note: Also includes kernel patches needed for DriveDroid to let you boot your computer from an iso image on your phone.
    Contributor: jpeg725
    Download: here

Galaxy Note 2 (N7100):

  • ROM: CM10.1
    Date: 15.05.2013
    MD5: db79e0530214299120409be241063a1e
    PD-Version: 1.57
    Contributor: biglsd
    Download: here
    ----------------------------------------------
  • ROM: PACMAN
    Date: 15.05.2013
    MD5: daa60cde908b43addc8be9e711cb6c2e
    PD-Version: 1.57
    Contributor: biglsd
    Download: here

Galaxy S 3 (I9300):

  • ROM: PACMAN
    Date: 15.05.2013
    MD5: bcdfee8a5b18b31871cc992ee875810d
    PD-Version: 1.57
    Contributor: optx
    Download: here
    ----------------------------------------------
  • ROM: CM10.1
    Date: 12.05.2013
    MD5: 7d3baba799c4b65ee2aeabf8d56d9839
    PD-Version: 1.57
    Contributor: Koetermann
    Download: here
    ----------------------------------------------
  • ROM: CM10.1
    Date: 19.05.2013
    MD5: b5d07c91c12c913cf6aa06f3f45ef56f
    PD-Version: 1.57
    Contributor: optx
    Download: here
    ----------------------------------------------
  • ROM: CM10.1
    Date: 23.05.2013
    MD5: 9d147c00d863723f801c1e434e51b77f
    PD-Version: 1.57
    Contributor: Koetermann
    Download: here
    ----------------------------------------------
  • ROM: JellyBeer
    Date: 16.05.2013
    MD5: b5d07c91c12c913cf6aa06f3f45ef56f
    PD-Version: 1.57
    Contributor: optx
    Download: here


Note 10.1 (n8000)

  • ROM: CM10.1
    Date: 15.05.2013
    MD5: baa6445ae4162666010509bdcce8ad7c
    PD-Version: 1.57
    Contributor: biglsd
    Download: here

Samsung tab 2 7" (p3100)

  • ROM: CM10.1
    Date: 15.05.2013
    MD5: 93de5d7866b1cee7bc224fb4411380f1
    PD-Version: 1.57
    Contributor: biglsd
    Download: here

Google Nexus 10 (manta)

  • ROM: CM10.1
    Date: 11.05.2013
    MD5: bf19181df5d4b76e4b218ee5a31a58cf
    PD-Version: 1.57
    Contributor: Koetermann
    Download: here

LG Nexus 4 (manta)

  • ROM: CM10.1
    Date: 10.05.2013
    MD5: unknown
    PD-Version: 1.57
    Contributor: Hired Geek
    Download: here

Samsung Galaxy Note (n7000)

  • ROM: CM10.1
    Date: 19.05.2013
    MD5: 16bb075282405af00ce9eb47b7e6eee5
    PD-Version: 1.57
    Contributor: I900-Nutzer
    Download: here

ZTE Blade / Orange San Francisco

  • ROM: CM10.1 by KonstaT
    Date: 19.05.2013
    MD5: 5ab4126a095ddb9329c831e0a10e7e2d
    PD-Version: 1.57
    Contributor: I900-Nutzer
    Download: here

Galaxy Nexus GSM (Maguro) (i9250)

  • ROM: CM10.1
    Date: 19.05.2013
    MD5: da95b698cbdeb9da4285e1629047b9be
    PD-Version: 1.57
    Contributor: Teemoo
    Download: here

Samsung Nexus S (crespo)

  • ROM: CM10.1
    Date: 21.05.2013
    MD5: 3c98c8056a65b4f0709e61bc736d9100
    PD-Version: 1.57
    Contributor: En0id
    Download: here

Samsung Galaxy S (i9000)

  • ROM: CM10.1
    Date: 24.05.2013
    MD5: d5e8a8ccf40aa8f4a239479a73b94ff2
    PD-Version: 1.57
    Contributor: Koetermann
    Download: here

galaxy note 1 (n7000)

  • ROM: CM10.1
    Date: 24.05.2013
    MD5: b790483b2d17627c7e5cb55fd31b64ab
    PD-Version: 1.57
    Contributor: karamelos
    Download: here
    ----------------------------------------------
  • ROM: SlimRom v5.6
    Date: 23.05.2013
    MD5: b46740fcbf0e8688707863be88704d86
    PD-Version: 1.57
    Contributor: I900-Nutzer
    Download: here
    ----------------------------------------------
  • ROM: JellyBeer v4.20
    Date: 22.05.2013
    MD5: 0703f5730b8e90b83cca980f83f801e5
    PD-Version: 1.57
    Contributor: I900-Nutzer
    Download: here
    ----------------------------------------------
  • ROM: PACman v22.3.0
    Date: 23.05.2013
    MD5: c84cfaeda5fb9fb651030f740353a9fd
    PD-Version: 1.57
    Contributor: I900-Nutzer
    Download: here
 
Last edited:

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
143
New Orleans
www.gigmasters.com
Looks good, man. Looking forward to making the package.

Edit: tried to patch on my way out the door, two problems. I haven;t had much time to diagnose, I was hoping to start a build and look at it when I got done with work.

libcore patch- I tried to strip a couple other levels, but no dice. I see that you have CM9 in your path which may not be significant. But since I had a failed hunk in framework I thought I would just report.

Code:
$ patch -p1 < ~/android/pdroidwork/pdroid_ext/patches/JB_libcore.patch
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -rupN '--exclude=.svn' '--exclude=.git*' '--exclude=*.java~' '--exclude=*.mk~' '--exclude=*.orig~' '--exclude=*.txt' '--exclude=*.orig' /root/CM9/libcore/luni/src/main/java/java/lang/PrivacyProcessManager.java pang/libcore/luni/src/main/java/java/lang/PrivacyProcessManager.java
|--- /root/CM9/libcore/luni/src/main/java/java/lang/PrivacyProcessManager.java	2012-07-18 16:10:00.479998383 +0545
|+++ pang/libcore/luni/src/main/java/java/lang/PrivacyProcessManager.java	2012-09-19 20:06:31.467808140 +0545
--------------------------

JB_framework:

Code:
patching file frameworks/base/telephony/java/com/android/internal/telephony/SMSDispatcher.java
Hunk #1 FAILED at 37.
Hunk #2 succeeded at 179 (offset 9 lines).
Hunk #3 succeeded at 319 with fuzz 1 (offset 13 lines).
Hunk #4 succeeded at 926 (offset 30 lines).
Hunk #5 succeeded at 944 (offset 30 lines).
Hunk #6 succeeded at 1030 (offset 30 lines).
1 out of 6 hunks FAILED -- saving rejects to file frameworks/base/telephony/java/com/android/internal/telephony/SMSDispatcher.java.rej
patching file frameworks/base/TelephonyRegistry.java

Everything else patches fine. The failed framework hunk could be because my source is maybe 2-3 days old, I will try a fresh repo sync when I get home from being out.
 
Last edited:
  • Like
Reactions: usamamalik555

bonanza123

Senior Member
Nov 11, 2007
206
35
0
'schland
Hey,

thank you very much for your efforts!
I am using your ready built for SGS 2 but i have problems applying new rules, because they are not saved. Logcat is attached, there are a lot of sqlite errors.
 
Last edited:

CollegeDev

Senior Member
Jun 28, 2012
270
778
0
Looks good, man. Looking forward to making the package.

Edit: tried to patch on my way out the door, two problems. I haven;t had much time to diagnose, I was hoping to start a build and look at it when I got done with work.

libcore patch- I tried to strip a couple other levels, but no dice. I see that you have CM9 in your path which may not be significant. But since I had a failed hunk in framework I thought I would just report.

Code:
$ patch -p1 < ~/android/pdroidwork/pdroid_ext/patches/JB_libcore.patch
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -rupN '--exclude=.svn' '--exclude=.git*' '--exclude=*.java~' '--exclude=*.mk~' '--exclude=*.orig~' '--exclude=*.txt' '--exclude=*.orig' /root/CM9/libcore/luni/src/main/java/java/lang/PrivacyProcessManager.java pang/libcore/luni/src/main/java/java/lang/PrivacyProcessManager.java
|--- /root/CM9/libcore/luni/src/main/java/java/lang/PrivacyProcessManager.java	2012-07-18 16:10:00.479998383 +0545
|+++ pang/libcore/luni/src/main/java/java/lang/PrivacyProcessManager.java	2012-09-19 20:06:31.467808140 +0545
--------------------------

JB_framework:

Code:
patching file frameworks/base/telephony/java/com/android/internal/telephony/SMSDispatcher.java
Hunk #1 FAILED at 37.
Hunk #2 succeeded at 179 (offset 9 lines).
Hunk #3 succeeded at 319 with fuzz 1 (offset 13 lines).
Hunk #4 succeeded at 926 (offset 30 lines).
Hunk #5 succeeded at 944 (offset 30 lines).
Hunk #6 succeeded at 1030 (offset 30 lines).
1 out of 6 hunks FAILED -- saving rejects to file frameworks/base/telephony/java/com/android/internal/telephony/SMSDispatcher.java.rej
patching file frameworks/base/TelephonyRegistry.java

Everything else patches fine. The failed framework hunk could be because my source is maybe 2-3 days old, I will try a fresh repo sync when I get home from being out.

Did you patched the PrivacyProcessManager.java successful? Yes, it based on CM9, because I havn't the source of the original files anymore. But it doesn't matter. I made these patches, updated my source code and used these patches by my own to verify that they work. Can you upload the SMSDispatcher.java.rej? I would like to see wat is going wrong.

Hey,

thank you very much for your efforts!
I am using your ready built for SGS 2 but i have problems applying new rules, because they are not saved. Logcat is attached, there are a lot of sqlite errors.

Yes, I believe I know whats going wrong. You used PDroid before and just flashed my zip, right? If so and you don't want to wipe your device, go to:

/data/system/

and delete the files: privacy.db, privacy.db-journal, privacy.db.bak. Then restart your device and all should work.

CollegeDev, why can't you compile an ALL-IN-ONE-APP ("PDroid-Suite") and just give credits to all developers? Would be so awesome if PDroid itself was included..

Why? I think it is unnecessary to do this, because you have now just one big and powerful applicaton. No addons or something like this. So why you want to use the old pdroid?
 
Last edited:

SecUpwN

Senior Member
Jun 12, 2012
2,086
645
0
DEUTSCHLAND!
secupwn.github.io
Why? I think it is unnecessary to do this, because you have now just one big and powerful applicaton. No addons or something like this. So why you want to use the old pdroid?
I am confused. In the initial post you're stating that PDroid itself is still needed. That's why I figured we'd still have to install 2 applications. Is it the case that this one is actually 2 in one? Would be soo awesome! :)
 
  • Like
Reactions: zuiqingshan1019

CollegeDev

Senior Member
Jun 28, 2012
270
778
0
I am confused. In the initial post you're stating that PDroid itself is still needed. That's why I figured we'd still have to install 2 applications. Is it the case that this one is actually 2 in one? Would be soo awesome! :)

I wrote this in first post:

It is a stand alone application and does not need PDroid itself anymore. You just have to apply my patches, install the application and have fun

It means, that you only need this application, to get it work. You don't need PDroid itself anymore:cowboy:
 
  • Like
Reactions: SecUpwN

measel

Senior Member
Jan 13, 2011
984
541
113
I think there was some irony involved in the FAQ. wasn't it?

But still: Would be great to have a PDroid Version (Suite) working for JB AND GB. It's a pity I can't use your version (yet! :D ).

Thanks for your work. It's good to see that developement is ongoing.
 

curtisf08

Senior Member
Aug 15, 2011
145
39
48
Hi im currently using the old pdroid patch and apk on AOKP-JB 4

Im not near my pc and wont be for awhile. "Is there anything i can do to manually aply your patch over the old one"

Sent from my GT-I9100 using xda app-developers app
 

yhrn

Senior Member
Mar 25, 2011
527
339
0
Stockholm
Hi,
Great work!
Is there any chance that there will be patches for non-CM ROMs in the future? Like Samsung (or other manufacturer) stock based, non-AOSP ROMs?
 

TamCore

Senior Member
Jul 8, 2010
665
649
0
28
Düsseldorf
tamcore.eu
Currently I have the 1.32 patches from pastime1971 in my repos. Can you please compare your and his patches and release an incremental version? That would make it much easier to update to your patch.
The hardest thing is the frameworks patch.

Sent from my Nexus 7 using Tapatalk 2
 

CollegeDev

Senior Member
Jun 28, 2012
270
778
0
I think there was some irony involved in the FAQ. wasn't it?

But still: Would be great to have a PDroid Version (Suite) working for JB AND GB. It's a pity I can't use your version (yet! :D ).

Thanks for your work. It's good to see that developement is ongoing.

I first developed this application for JB, because lot of users asked me if my addon will support JB in future. So I decided to release the patches for JB first. If I have more spare time, I will have a look on other roms e.g. Stock ROMs and ICS too. I don't know if I should support GB, because it is very outdated?

Hi im currently using the old pdroid patch and apk on AOKP-JB 4

Im not near my pc and wont be for awhile. "Is there anything i can do to manually aply your patch over the old one"

Sent from my GT-I9100 using xda app-developers app

Do you compile by your own?
You can flash my patched ROM if you want to test, but it is CM10 based.

What about this part then?
Maybe you should remove it..

Yes, I confess it is a little bit confuse, but it should mean that you can't use my new PDroid application on the old framework patches (v1.32 etc).

Hi,
Great work!
Is there any chance that there will be patches for non-CM ROMs in the future? Like Samsung (or other manufacturer) stock based, non-AOSP ROMs?

Yes, I think so. If I have some spare-time I will port it to other ROMs.

Currently I have the 1.32 patches from pastime1971 in my repos. Can you please compare your and his patches and release an incremental version? That would make it much easier to update to your patch.
The hardest thing is the frameworks patch.

Sent from my Nexus 7 using Tapatalk 2

I don't know if I have time for that, but why you need it? Just update with repo sync and apply the patches. If that not work, use the git hard reset command.
 
Last edited:
  • Like
Reactions: KMino and yhrn

CollegeDev

Senior Member
Jun 28, 2012
270
778
0
Patches updated!
I've made a mistake in JB_libcore.patch, now you have one incremental and basic patch for libcore. Incremental patch is for patch v1.32!
 
  • Like
Reactions: SecUpwN

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
143
New Orleans
www.gigmasters.com
SMSDispatcher.java.rej
Code:
--- root/frameworks_JB_orig/base/telephony/java/com/android/internal/telephony/SMSDispatcher.java	2012-08-07 16:04:22.000000000 +0545
+++ frameworks/base/telephony/java/com/android/internal/telephony/SMSDispatcher.java	2012-09-30 19:50:49.000000000 +0545
@@ -37,7 +37,11 @@
 import android.os.Handler;
 import android.os.Message;
 import android.os.PowerManager;
+import android.os.ServiceManager;
 import android.os.SystemProperties;
+import android.privacy.IPrivacySettingsManager;
+import android.privacy.PrivacySettings;
+import android.privacy.PrivacySettingsManager;
 import android.provider.Telephony;
 import android.provider.Telephony.Sms.Intents;
 import android.telephony.PhoneNumberUtils;

You can see what happened there.

I haven't had a chance to test your incremental libcore.patch update. I am using the source right now. And I haven't looked at it since, really. But the build patch worked, libcore didn't patch at all, due to the above error finding the file it was looking for, and framework had the rejected hunk you see synopsized above.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 169
    Disclaimer:

    Code:
    /*
     * Your warranty is now void.
     *
     * I am not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. 
     * Please do some research if you have any concerns about features 
     * included in this Patch and application before flashing it! YOU are 
     * choosing to make these modifications, and if you point the finger 
     * at me for messing up your device, I will laugh at you.
     *
     */

    General & Credits:

    First of all, many many thanks to svyat who developed the main application PDroid, thank you!! Before I describe some new features (and old too) I want to say that the Application PDroid2.0.apk is written completely by my own. I just took some styles from svyat to give users the "old PDroid" feeling :) It is a stand alone application and does not need PDroid itself anymore. You just have to apply my patches, install the application and have fun :)

    App description:

    PDroid 2.0 allows blocking access for any installed application to the following data separately:

    • Device ID (IMEI/MEID/ESN)
    • Subscriber ID (IMSI)
    • SIM serial (ICCID)
    • Phone and mailbox number
    • Incoming call number
    • Outgoing call number
    • GPS location
    • Network location
    • List of accounts (including your google e-mail address)
    • Account auth tokens
    • Contacts
    • Call logs
    • Calendar
    • SMS
    • MMS
    • Browser bookmarks and history
    • System logs
    • SIM info (operator, country)
    • Network info (operator, country)
    • IP Tables(until now only for Java process)
    • Android ID
    • Call Phone
    • Send SMS
    • Send MMS
    • Record Audio
    • Access Camera
    • Force online state (fake online state to permanent online)
    • Wifi Info
    • ICC Access (integrated circuit-card access, for reading/writing sms on ICC)
    • Switch network state (e.g. mobile network)
    • Switch Wifi State
    • Start on Boot (prevents that application gets the INTENT_BOOT_COMPLETE Broadcast)


    Donators:

    • Big credits to ce4. He is the first donator. Many thanks :)
    • Another thankful guy: schertling. Thank you for your donation :)
    • Thanks to MacDog_AU, who also donated a beer :)
    31
    Translators:
    Big thanks to following translators of PDroid2.0, who made the app available in their native language:


    PDroid2.0 Flash-Repo:
    @ all guys who ever build a ROM with PDroid2.0, please upload the ROM here and post it in this thread or send me the link via pn. I need following additional information:
    • What ROM is it?
    • When do you build it (optional)
    • Which version of PDroid is included (Framework)
    • For which device is the ROM
    You will get full credits in the OP and the link for the REPO will also be present inside the description for the app in googleplay.

    How does it work? Just download the ROM for your device and flash it. Then you're able to use PDroid2.0!
    Side-Note related the devices:
    Nexus 4 = mako
    Nexus 7 Wi-Fi = grouper
    Nexus 7 GSM = tilapia
    Nexus 10 = manta
    THX to Koetermann!

    Galaxy S2 (I9100):

    • ROM: PACMAN
      Date: 02.15.2013
      MD5: c810f45732bf1f3fd82eccd7bfda2ca0
      PD-Version: 1.57
      Contributor: AuSSiELaMbChOpS
      Download: here
      ----------------------------------------------
    • ROM: CM10.1
      Date: 18.05.2013
      MD5: unknown
      PD-Version: 1.57
      Side-Note: Also includes kernel patches needed for DriveDroid to let you boot your computer from an iso image on your phone.
      Contributor: jpeg725
      Download: here

    Galaxy Note 2 (N7100):

    • ROM: CM10.1
      Date: 15.05.2013
      MD5: db79e0530214299120409be241063a1e
      PD-Version: 1.57
      Contributor: biglsd
      Download: here
      ----------------------------------------------
    • ROM: PACMAN
      Date: 15.05.2013
      MD5: daa60cde908b43addc8be9e711cb6c2e
      PD-Version: 1.57
      Contributor: biglsd
      Download: here

    Galaxy S 3 (I9300):

    • ROM: PACMAN
      Date: 15.05.2013
      MD5: bcdfee8a5b18b31871cc992ee875810d
      PD-Version: 1.57
      Contributor: optx
      Download: here
      ----------------------------------------------
    • ROM: CM10.1
      Date: 12.05.2013
      MD5: 7d3baba799c4b65ee2aeabf8d56d9839
      PD-Version: 1.57
      Contributor: Koetermann
      Download: here
      ----------------------------------------------
    • ROM: CM10.1
      Date: 19.05.2013
      MD5: b5d07c91c12c913cf6aa06f3f45ef56f
      PD-Version: 1.57
      Contributor: optx
      Download: here
      ----------------------------------------------
    • ROM: CM10.1
      Date: 23.05.2013
      MD5: 9d147c00d863723f801c1e434e51b77f
      PD-Version: 1.57
      Contributor: Koetermann
      Download: here
      ----------------------------------------------
    • ROM: JellyBeer
      Date: 16.05.2013
      MD5: b5d07c91c12c913cf6aa06f3f45ef56f
      PD-Version: 1.57
      Contributor: optx
      Download: here


    Note 10.1 (n8000)

    • ROM: CM10.1
      Date: 15.05.2013
      MD5: baa6445ae4162666010509bdcce8ad7c
      PD-Version: 1.57
      Contributor: biglsd
      Download: here

    Samsung tab 2 7" (p3100)

    • ROM: CM10.1
      Date: 15.05.2013
      MD5: 93de5d7866b1cee7bc224fb4411380f1
      PD-Version: 1.57
      Contributor: biglsd
      Download: here

    Google Nexus 10 (manta)

    • ROM: CM10.1
      Date: 11.05.2013
      MD5: bf19181df5d4b76e4b218ee5a31a58cf
      PD-Version: 1.57
      Contributor: Koetermann
      Download: here

    LG Nexus 4 (manta)

    • ROM: CM10.1
      Date: 10.05.2013
      MD5: unknown
      PD-Version: 1.57
      Contributor: Hired Geek
      Download: here

    Samsung Galaxy Note (n7000)

    • ROM: CM10.1
      Date: 19.05.2013
      MD5: 16bb075282405af00ce9eb47b7e6eee5
      PD-Version: 1.57
      Contributor: I900-Nutzer
      Download: here

    ZTE Blade / Orange San Francisco

    • ROM: CM10.1 by KonstaT
      Date: 19.05.2013
      MD5: 5ab4126a095ddb9329c831e0a10e7e2d
      PD-Version: 1.57
      Contributor: I900-Nutzer
      Download: here

    Galaxy Nexus GSM (Maguro) (i9250)

    • ROM: CM10.1
      Date: 19.05.2013
      MD5: da95b698cbdeb9da4285e1629047b9be
      PD-Version: 1.57
      Contributor: Teemoo
      Download: here

    Samsung Nexus S (crespo)

    • ROM: CM10.1
      Date: 21.05.2013
      MD5: 3c98c8056a65b4f0709e61bc736d9100
      PD-Version: 1.57
      Contributor: En0id
      Download: here

    Samsung Galaxy S (i9000)

    • ROM: CM10.1
      Date: 24.05.2013
      MD5: d5e8a8ccf40aa8f4a239479a73b94ff2
      PD-Version: 1.57
      Contributor: Koetermann
      Download: here

    galaxy note 1 (n7000)

    • ROM: CM10.1
      Date: 24.05.2013
      MD5: b790483b2d17627c7e5cb55fd31b64ab
      PD-Version: 1.57
      Contributor: karamelos
      Download: here
      ----------------------------------------------
    • ROM: SlimRom v5.6
      Date: 23.05.2013
      MD5: b46740fcbf0e8688707863be88704d86
      PD-Version: 1.57
      Contributor: I900-Nutzer
      Download: here
      ----------------------------------------------
    • ROM: JellyBeer v4.20
      Date: 22.05.2013
      MD5: 0703f5730b8e90b83cca980f83f801e5
      PD-Version: 1.57
      Contributor: I900-Nutzer
      Download: here
      ----------------------------------------------
    • ROM: PACman v22.3.0
      Date: 23.05.2013
      MD5: c84cfaeda5fb9fb651030f740353a9fd
      PD-Version: 1.57
      Contributor: I900-Nutzer
      Download: here
    19
    this release is a prerelease
    I'm ready now and want to pull out a pre-release of PDroid2.0 v1.54. Please feel free to test it and report bugs if there are any :).
    The patches are not tested so please report if anything fails! I'm now going to host all this stuff on github asap.


    News related to the Manager Application:

    • fixed angry birds bugs (multiple apps with same name can't access the privacy settings)
    • Fixed bug in batch profile mode where also system apps gets the profile instead of user only
    • Minor GUI improvements -> new dialog layout, fixed layout for devices which have no hard-keyboard, fixed layout for tablets (ou, that was ugly), a lot of more gui improvements
    • Added Random button in batch profile mode
    • Added random and clear button in the settings dialog if you want to add custom values
    • Added installed notification preference, now you can disable instant notification
    • Changed the update notification to smartmode -> same function as discussed in thread. Only if permissions changed you will get instant notification
    • Fixed the search bar
    • Fixed the keyboard bug if you leave pdroid with home button
    • Added failSafeMode handler(description look at core feature)
    • Added persistence notification in notificationbar which is showing current protection state(logging state, failsafeMode state, current PermissionMode, Database Connection Error Count or Manager Connection Error Count). You're also able to quick access settings, preferences, and logs
    • Switch Debug mode for core logging feature
    • Disable applications handling (description look at core feature)
    • Additional information in "Core and App Information" to see which current hardcoded default deny mode is active
    • many more...


    News related to Core:

    • Fixed llam bug
    • fixed google listen crashed
    • fixed camera bug (thx to MB66)
    • a lot of more fixes. I can't listen them all here, if you want to know some specific fixes, just ask for :)
    • Fixed the announced security bugs (thx to FFuy5)
    • Fixed bug where users have to delete the privacyDatabases to upgrade to PDroid2.0 or OpenPDroid
    • Fixed more security related bugs (every app was able to create its own data access log and a lot of more)
    • Implemented FailSafeMode with self recovery: Until the latest versions every root application was able to delete your privacy database which causes that all "doors" are open and PDroid decided to give the applications the real value. It also was able to modify entries inside of the database for ALL applications and change the settings. But what is the FailSafeMode? This mode is permament watching for unauthorized database accesses. That means if anyone tries to make changes in your privacy database or delete it to get your personal information PDroid triggers the FailSafeMode. The database and all current settings will be deleted and the return values of all settings will be empty, so all accesses will be blocked while you're in FailSafeMode. If PDroid detects a possible attack you will get an instant notification which informs you about the attack and that your system is now in FailSafeMode. After that PDroid tries to handle this case itself, that means it will try to recover the latest privacySettings and set up PDroid from scratch. It will take some seconds and you will receive another notification if the recovery was successful or not. Than you can go to preferences and deactivate the failSafeMode. Now your system is safe again! Once again, if you're currently in FailSafeMode, no application is able to get your personal information.
    • Implemented a core Privacy Debugging Bridge (PDB): A lot of developers wrote me emails and asked for such a feature. Here it is. With the latest version I wasn't able to detect a bug directly because of missing framework logs. But if you logging the whole time the problem is that your system logs will blow out, that's bad. Now you can enable and disable the core logging by enable/disable the preference in PDroid2.0. It alos has the advantage that you can now provide PDroid2.0 logs in a very effective way. You just have to open CatLog or other LogCat readers and type in the tag field "PDroid2.0". Now only core logs which are related to PDroid2.0 will appear and I can have a look at it.
    • enhanced core logging -> Added additional core logging information for EVERY class, now I'm able to give better support.
    • Restructured - partial or complete rewritten PDroid related framework classes. I did it because I implemented also a hardcoded default deny mode
    • Enhanced complete database threading (in a similar way ffuy5 did it, but not the same)
    • Added complete privacyCaching: I've added a complete privacy Cache handling system which allows very effectiv privacy settings access. Why you did that? If you open the Database in android it will cost a lot of CPU and that causes more battery consumption. PDroid open and closes the database a lot of times and that will cause a lot of battery and cpu consumption of your device. Harmful applications can hammer on the settings and your system will lag, that's not good at all! Now you can say: "ok, then i just leave the db connection open". Yes you can, but if you read the developers guide on android you will see that it is not a good way to do it. Summary: The cache will save battery, preserves your cpu. The only disadvantage of this is that it needs more memory, but you will never notice that :)
    • Fixed horrible service connection bug: Until now the problem is that the connection to the privacy service often fails. This causes some privacy information leaked. How did you implemented it? I was able to implement a central reconnection management. Now, on every dataaccess the system tries to connect to the service 5 times, if that fails the hardcoded default deny mode will trigger (description below). I'm running this bugFix now 3-5 weeks and never noticed (I have implemented a counter which is watching this error) a connection failure anymore.
    • Implemented a hardcoded default deny mode: This mode is the last and deepest "surface" which prevents PDroid2.0 from leaking data. What will happen if ever security mechanism fails? The answer is the default deny mode. The default deny mode is hardcoded and cannot be changed dynamically. People who compiling by their own can easily change this hardcoded mode. They have just to change one variable. You can decide between 3 modes: EMPTY, REAL, RANDOM. Just adjust this setting before you compile. You can easily check the current default deny mode of your framework in the manager application at "Core and App information". If you have notification enabled, you will get a special notification which indicates that the default deny mode was active. Btw: since I've fixed this bug I've never noticed that this hardcoded surface was active. So now PDroid works really really stable.
    • Implement disabling apps feature: The disabling apps feature allows you to automatically disable (freeze) the application until you've commit and saved the settings of the new installed application. There are some additional features (like freeze also system apps or freeze on update ....) which allows you to fine tune your settings. This feature will not disable the application like TitaniumBackup does. It search for every provider, receiver, activity or service and deactivates them. So the application cannot receive broadcast's or whatever until you enabled it.
    • Implemented/enhanced task Killing feature: First: the task killing feature is NOT similar to other task-killer you've ever seen on android. It does not showing you current running processes or whatever. With this feature you're able to FORCE CLOSE an application, similar to the force-close-button in the detailed app screen on android. Why should I need this feature? Sometimes you don't want that applications like face-book or google-play running in background. Normal taskkiller are not able to kill background service so task-killing won't work. With PDroid2.0 you can just kill them and they won't restart anymore until you opened the application by yourself.
    • many more.....

    For people who compile by their own, you can change the dafault deny mode in the package android.privacy [class PrivacySettings.java].
    Just change this line:
    Code:
    public static final int CURRENT_DEFAULT_DENY_MODE = DEFAULT_DENY_EMPTY;
    to your demanded mode. Examples:
    Empty
    Code:
    public static final int CURRENT_DEFAULT_DENY_MODE = DEFAULT_DENY_EMPTY;
    Real
    Code:
    public static final int CURRENT_DEFAULT_DENY_MODE = DEFAULT_DENY_REAL;
    Random
    Code:
    public static final int CURRENT_DEFAULT_DENY_MODE = DEFAULT_DENY_RANDOM;

    Ready Build for SGS2:
    I'm not sure if this build contains the latest changes. If it doesn't work for you please get in touch with me.

    Preview:
    screenshot20130128211633B5V5A.png
    screenshot20130128211703G76OC.png
    screenshot201302081534243LNRN.png
    screenshot20130208153447SJ73G.png
    screenshot20130208153457ABJ5T.png
    screenshot20130208153522B39QZ.png
    screenshot201302081537554HJUP.png
    screenshot20130208154959FJKC9.png
    17
    Hey,

    here I am. Hopefully back in business with PDroid2.0 :D I know a lot of people sitting on needles and can't wait until the new version released. I can understand you :) So, I would like to answer some questions:

    Why you need so much time for the next release?
    First: I have a real life and had a lot to do last time so I wasn't able to work on PDroid2.0 the whole time.
    Second: I've restructured a lot in the framework and the core is now partial rewritten by me, more detailed description will follow below.

    What the state of the current development?
    I'm now running Android 4.2.1 for 2-3 Weeks and it is working really stable now. I've finished my work at the last night and it need just a little bit of testing, but there is one BIG problem. The "upload electronic" (in german it calls "ladeelektronik", hopefully it is the right word in english...) of my device is damaged. I have to save some money to get a new device :( Now I only can test my work with the device of my girlfriend if she allows that :laugh: I just need to update the CM10.1 version and check if my code fits with the newest updates (I'm currently developing with a nightly which is older than 1 month) and then I will build the patches and release them.

    It took a long time until you released your new version. Can I except a bunch of "changings"?
    Yes, you can. There are a lot of changings in the new version at the CORE and Application itself. The only disadvantage of this is that it is not compatible with OpenPDroid or older version of PDroid2.0. I will looking forward to make a compatible version, but you all sitting on needles to get it and I will release the "pre-version" of it.

    News related to the Manager Application:

    • fixed angry birds bugs (multiple apps with same name can't access the privacy settings)
    • Fixed bug in batch profile mode where also system apps gets the profile instead of user only
    • Minor GUI improvements -> new dialog layout, fixed layout for devices which have no hard-keyboard, fixed layout for tablets (ou, that was ugly), a lot of more gui improvements
    • Added Random button in batch profile mode
    • Added random and clear button in the settings dialog if you want to add custom values
    • Added installed notification preference, now you can disable instant notification
    • Changed the update notification to smartmode -> same function as discussed in thread. Only if permissions changed you will get instant notification
    • Fixed the search bar
    • Fixed the keyboard bug if you leave pdroid with home button
    • Added failSafeMode handler(description look at core feature)
    • Added persistence notification in notificationbar which is showing current protection state(logging state, failsafeMode state, current PermissionMode, Database Connection Error Count or Manager Connection Error Count). You're also able to quick access settings, preferences, and logs
    • Switch Debug mode for core logging feature
    • Disable applications handling (description look at core feature)
    • Additional information in "Core and App Information" to see which current hardcoded default deny mode is active
    • many more...


    News related to Core:

    • Fixed llam bug
    • fixed google listen crashed
    • fixed camera bug (thx to MB66)
    • a lot of more fixes. I can't listen them all here, if you want to know some specific fixes, just ask for :)
    • Fixed the announced security bugs (thx to FFuy5)
    • Fixed more security related bugs (every app was able to create its own data access log and a lot of more)
    • Implemented FailSafeMode with self recovery: Until the latest versions every root application was able to delete your privacy database which causes that all "doors" are open and PDroid decided to give the applications the real value. It also was able to modify entries inside of the database for ALL applications and change the settings. But what is the FailSafeMode? This mode is permament watching for unauthorized database accesses. That means if anyone tries to make changes in your privacy database or delete it to get your personal information PDroid triggers the FailSafeMode. The database and all current settings will be deleted and the return values of all settings will be empty, so all accesses will be blocked while you're in FailSafeMode. If PDroid detects a possible attack you will get an instant notification which informs you about the attack and that your system is now in FailSafeMode. After that PDroid tries to handle this case itself, that means it will try to recover the latest privacySettings and set up PDroid from scratch. It will take some seconds and you will receive another notification if the recovery was successful or not. Than you can go to preferences and deactivate the failSafeMode. Now your system is safe again! Once again, if you're currently in FailSafeMode, no application is able to get your personal information.
    • Implemented a core Privacy Debugging Bridge (PDB): A lot of developers wrote me emails and asked for such a feature. Here it is. With the latest version I wasn't able to detect a bug directly because of missing framework logs. But if you logging the whole time the problem is that your system logs will blow out, that's bad. Now you can enable and disable the core logging by enable/disable the preference in PDroid2.0. It alos has the advantage that you can now provide PDroid2.0 logs in a very effective way. You just have to open CatLog or other LogCat readers and type in the tag field "PDroid2.0". Now only core logs which are related to PDroid2.0 will appear and I can have a look at it.
    • enhanced core logging -> Added additional core logging information for EVERY class, now I'm able to give better support.
    • Restructured - partial or complete rewritten PDroid related framework classes. I did it because I implemented also a hardcoded default deny mode
    • Enhanced complete database threading (in a similar way ffuy5 did it, but not the same)
    • Added complete privacyCaching: I've added a complete privacy Cache handling system which allows very effectiv privacy settings access. Why you did that? If you open the Database in android it will cost a lot of CPU and that causes more battery consumption. PDroid open and closes the database a lot of times and that will cause a lot of battery and cpu consumption of your device. Harmful applications can hammer on the settings and your system will lag, that's not good at all! Now you can say: "ok, then i just leave the db connection open". Yes you can, but if you read the developers guide on android you will see that it is not a good way to do it. Summary: The cache will save battery, preserves your cpu. The only disadvantage of this is that it needs more memory, but you will never notice that :)
    • Fixed horrible service connection bug: Until now the problem is that the connection to the privacy service often fails. This causes some privacy information leaked. How did you implemented it? I was able to implement a central reconnection management. Now, on every dataaccess the system tries to connect to the service 5 times, if that fails the hardcoded default deny mode will trigger (description below). I'm running this bugFix now 3-5 weeks and never noticed (I have implemented a counter which is watching this error) a connection failure anymore.
    • Implemented a hardcoded default deny mode: This mode is the last and deepest "surface" which prevents PDroid2.0 from leaking data. What will happen if ever security mechanism fails? The answer is the default deny mode. The default deny mode is hardcoded and cannot be changed dynamically. People who compiling by their own can easily change this hardcoded mode. They have just to change one variable. You can decide between 3 modes: EMPTY, REAL, RANDOM. Just adjust this setting before you compile. You can easily check the current default deny mode of your framework in the manager application at "Core and App information". If you have notification enabled, you will get a special notification which indicates that the default deny mode was active. Btw: since I've fixed this bug I've never noticed that this hardcoded surface was active. So now PDroid works really really stable.
    • Implement disabling apps feature: The disabling apps feature allows you to automatically disable (freeze) the application until you've commit and saved the settings of the new installed application. There are some additional features (like freeze also system apps or freeze on update ....) which allows you to fine tune your settings. This feature will not disable the application like TitaniumBackup does. It search for every provider, receiver, activity or service and deactivates them. So the application cannot receive broadcast's or whatever until you enabled it.
    • Implemented/enhanced task Killing feature: First: the task killing feature is NOT similar to other task-killer you've ever seen on android. It does not showing you current running processes or whatever. With this feature you're able to FORCE CLOSE an application, similar to the force-close-button in the detailed app screen on android. Why should I need this feature? Sometimes you don't want that applications like face-book or google-play running in background. Normal taskkiller are not able to kill background service so task-killing won't work. With PDroid2.0 you can just kill them and they won't restart anymore until you opened the application by yourself.
    • many more.....

    Now I have no more time to write and hopefully I will edit this post soon.
    @All people who tries to get in touch with me via PM or email (flooded :eek:) I will answer as fast as I can. But the highest priority now is to release the new Version of PDroid2.0 ASAP.
    Thanks for reading this post and hopefully you can understand my text. If not, just ask, because I wrote this text very fast....
    16
    It also works with TWRP. Tested it on my i9300.

    @CollegeDev: Could you edit the OP concerning to TWRP?


    Regards

    Koetermann

    Yes, I will do it.

    News:
    PDroid2.0 goes now to Github. :good::good:

    I'm currently learning how to handle sources with github and if anyone has a good solution how I can sync my sources with Github -> please get in touch with me, thanks

    You can find me on GitHub for this application under following link:
    https://github.com/CollegeDev/PDroid2.0_Manager
    Other repos:
    https://github.com/CollegeDev/PDroid2.0_Manager_Compiled -> here you can download the newest builds under the "devil" branch
    https://github.com/CollegeDev/PDroid2.0_Framework_Patches -> patches

    You can now open issues and enhancements if you like :)
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone