yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] MuadDib_II:
Cool.

I was flirting with PDroid for a while now. I think I'm gonna try it, it looks simple after all...

Thanks
[Android Software/Hacking General [Developers Only]] Born2Model3D:
I have been patching ROMs since morning and trying them out to see which one works but have failed to find a single stable ROM, that supports OpenPdroid (when it patched successfully, it didn't worked) and tabletUI and also v6supercharger(not necessary)

I would also prefer a stable ROM even if its a 4.1 or 4.2 or 4.2.1.

Is there any ROM that has openpdroid built-in???

The ROMs I tried:

SlimBean 4.2.1 Stable 1.0

PACman ROM latest one

CM nightly

PA 3 (openpdroid patched but when I blocked es explorer WiFi info and network info, it still checked for an update)

AOKP Milestone JB

Maybe 1- 2 others...
[Android Software/Hacking General [Developers Only]] poo706:
You should get afwall+ for proper wifi/3g blocking.
[Android Software/Hacking General [Developers Only]] mateorod:
Caldair sent in a fix for this error and it is available in Autopatcherv2.9.0 from our download page or from ApG immediately.

Thanks Caldair!

As before, I have not abandoned you guys, I am just trying to put my time into the OpenPDroid update so we can get all the PDroid devs (CollegeDev among them) woorking on one patch set together. That way everyone wins.

Thanks to everyone who has spent some time offering support to new users, that has made this possible!
[Android Software/Hacking General [Developers Only]] Born2Model3D:
I don't just need a network blocker, I just meant to say that pdroid isn't working and have failed to find a single ROM that does.
[Android Software/Hacking General [Developers Only]] rxmd:
I'm having problems patching a couple of 4.2.1 and 4.2.2 ROMs for the Nexus 7. What I'm trying to accomplish is a ROM that is as close to stock/AOSP as possible, but with OpenPDroid. I am using Autopatcher 2.8.8 through ApG 2.6.0.2.

Here is the error message from patching CM 10.1 (20130407 build, failure at AsyncTaskLoader.smali): http://codepad.org/g3oyvhR6

Here is the error message from patching CM 10.1 (latest M-series build, failure at Fragment.smali): http://codepad.org/2QdCtyS6

Here is the error message from patching BAMF 3.1 (AOSP-based, failure at WallpaperService$Engine.smali): http://codepad.org/FHHYyi8v

Here is the error message from patching Purity 5.2.1 (AOSP-based, failure at ServerThread.smali): http://codepad.org/ZBz3RTXQ

Here is the error message from patching Supercharge 2.0 (AOSP-based, failure at BroadcastQueue.smali): http://codepad.org/iqTkKe45

Here is the error message from patching Famigo 4.2 (AOKP-based, failure at Fragment.smali): http://codepad.org/zqtFBD2u

So far the only ROMs that I've succeeded in patching are Slim Bean, and AOSP 2.2 with Franco's kernel. I'll install these later and see what can be done.

For completeness, I know that patching stock ROMs usually isn't very promising, but:

here is the error message from patching a deodexed 4.2.1 stock ROM (failure at Camera.smali and MediaRecorder.smali): http://codepad.org/6VFpOseM, and

here is the error message from patching a deodexed 4.2.2 stock ROM (failure at Camera.smali and MediaRecorder.smali): http://codepad.org/RSAaaus7.

These might well be OpenPDroid issues rather than Autopatcher issues, tell me if it's better to ask these questions over in the OpenPDroid thread.
[Android Software/Hacking General [Developers Only]] mouse@home:
Sorry this my error on attempting to patch the last release of albinoman887 CyanogenMod 10.1 Jellybean 4.2.2 - KANG. here is the log

http://codepad.org/njjgOPTY

Really thanks for your time
[Android Software/Hacking General [Developers Only]] xelra:
We need to put something out there that auto-compiles CM builds with pdroid. So that end users can just grab their cm ROM with pdroid like they do from get.cm.
[Android Software/Hacking General [Developers Only]] SecUpwN:
Any news on why AOKP by heli is not patchable?
[Android Software/Hacking General [Developers Only]] Didgesteve:
Here is a link to Slim patch. If it doesn't work then reflash rom
[Android Software/Hacking General [Developers Only]] nocturnoz:
Would be nice cause it's the only CM 10.1 for the HTC Sensation...and I won't use it without pdroid :silly:
[Android Software/Hacking General [Developers Only]] rufrider:
I get this error:

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!! error: system/media/PDroid.jpeg is missing in the patch. Please upload your logfile to the support thread!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Log.File:

View attachment log20130408144402.txt

Rom:

http://xdaforums.com/showthread.php?t=2130555
[Android Software/Hacking General [Developers Only]] chenrp:
any support for TW based ROM?
[Android Software/Hacking General [Developers Only]] revnu:
I think I give the developelrs here a few more weeks......till now the autopatcher is a good idea, but seems not to work for many ROMs

Again my request to DEVs:

PLZ SUPPORT SUPERNEXUS 2.0 BUILD4 ROM (AOSP 4.2.2)
[Android Software/Hacking General [Developers Only]] mateorod:
Sorry, the dev 'albinoman' has rebased his rom off of something called Team Hydra instead of regular Cm10.1. That has broken the patches. If you look at his changelog, you can see where he rebased this, and the release before that is patchable.

I did some brief testing on a couple of other AOKP nightlies and had breakage as well. I will rebuild some patches tonight and tomorrow and hope that it fixes it for you.

I downloaded your rom and looked into this some. The build query failed for you, and it has resulted in something pretty strange. I have an error-catch that caught one thing, but not another. needs investigating, even if it is a one time thing.

I will add finding an error-catch for this in a future version, but I do not exactly know what is wrong. I just ran your rom through my local copy and the script ran perfectly. Although your ROM did not patch, I guess that HumberOs has gone off of the Official Cm10.1 tree. You might try another CM10.1 build and see if that works.

I will look into why the Autopatcher could not parse your build.prop though. It has something to do with your environment, but I should be able to account for that for you.

Update: The problem slipped past me. The command you ran the autopatcher with is incorrect. You used the whole name of your rom twice, once as a target (the rom to be patched) and once as a ROMTYPE (which is incorrect). Just try adding cm to the end instead of the whole rom name, or better yet, let the autopatcher do the work (it is more reliable) by

./auto_patcher ROM openpdroid

Update2: Fixed the bug that caused this, if I had more time I would run a git blame on this line because I would love to know how long that bug has been lurking. Thanks for the log and the link to the rom, perfect bug report. Sorry that your rom isn't patchable, I would like to have that good news for you.

Sorry, no. Stock roms are not supported because I do not have builders for them, and because source is in many cases not available.
[Android Software/Hacking General [Developers Only]] nocturnoz:
Yeah..I know. I'm running the build before he rebased his rom.

Is there maybe a workaround or could I fix the patch by myself without massive knowledge in programming?:confused:
[Android Software/Hacking General [Developers Only]] mateorod:
Yeah, actually there is and that is probably the best thing to do.

All you need is a computer that can build Android. I don't really want to into the specifics too too much in this thread (it would overwhelm the auto-patcher traffic) but building ROMs is actually pretty simply, and I am pretty sure that albino man has his sources available on github.

Find out if albinoman has sources available for his ROM. If so, start a thread in your device General forum called "Build OpenPdroid for Albino man CM10.1" or something. Once you have successfully built the rom at least once, come back and post the link here and I will get you the rest of the way. It is actually pretty simple and building Android is fulfilling and fun, once you get it done the first time, making updated patches is a snap.

The first place I would go would be the albino man thread. Let them know you are interested in building the ROM for yourself and do they have a manifest available. Good luck!
[Android Software/Hacking General [Developers Only]] Teemoo:
hi,

any news about llama / cell tower bug ?

also you can see a little bit of log here, It might help.

04-03 16:26:12.172 I/LlamaDroid(2115): InitCellListener
04-03 16:26:12.198 I/PrivacyPhoneProxy(2108): package: com.android.phone ALLOWED for getCellLocation()
04-03 16:26:12.202 I/PrivacyGSMPhone(2108): Package: com.android.phone asked for getCellLocation()
04-03 16:26:36.471 I/PrivacyGSMPhone(2108): Package: com.android.phone asked for getCellLocation()
04-03 16:26:36.475 I/PrivacyTelephonyRegistry(1525): package: com.kebab.Llama blocked for CellLocation
04-03 16:26:36.528 E/AndroidRuntime(2115): at com.kebab.Llama.CellsActivity.Update(CellsActivity.java:229)
04-03 16:26:36.528 E/AndroidRuntime(2115): at com.kebab.Llama.LlamaService.cellLocationChanged(LlamaService.java:2346)
04-03 16:26:39.828 I/LlamaDroid(11149): InitCellListener
04-03 16:26:39.844 I/PrivacyPhoneProxy(2108): package: com.android.phone ALLOWED for getCellLocation()
04-03 16:26:39.844 I/PrivacyGSMPhone(2108): Package: com.android.phone asked for
[Android Software/Hacking General [Developers Only]] logicmann:
Hey

got following errors:

http://codepad.org/leqMsGOt

Rom is Supernexus I9000 GalaxyS from faryaab
[Android Software/Hacking General [Developers Only]] dark_ente:
Hello everyone,

I tried to use the Auto-Patcher for Nexus 4, rom Carbon but got the following error.

I tried CM, AOKP, AOSP or PA based but got the same error.

http://codepad.org/JYbfPxtM

Can anybody help me?
[Android Software/Hacking General [Developers Only]] mateorod:
Autopatcher v2.9.1 is up to ApG users and has been uploaded to techerrata (available in maybe 20 mins)

The only change is that I updated the AOKP patches to account for the latest breakage.

If you use AOKP, please test and report. I know that it can patch, but we did have some mysterious phone FCS that I had to work around last time I built patches. I hope that is no longer the case. Keep the restore close by until we get some reports, okay?

Logcats are always helpful. You have not seen me at this thread as much because i am trying to concentrate on the OpenPDroid/Pdroid2.0 merge and update. I can now promise that a test run will be available by the end of next week, if not sooner. That does not mean that it wil be bug free enough to give to everyone, but that we will be testing what we hope to be the update by then.

So, progress,

This update will include CollegeDev's fix for this issue, as well as a bugfix in the LocationManager I have recently found. There are some big improvements over all, and more will be discussed as the time draws near.

Thanks for everyone's patience, I know it has been slow moving, but we have to marshall a bunch of parts to get an update out. Most source code projects just push their changes and are done, we actually have created and support porting to end users. But it makes us kind of slow....

Looks like it is stock based. We do not support stock at this time. If it is based on regular AOSP, then I guess it just isn't patchable. You could try the other rom types, maybe,

I do not know what carbon rom is. But you are trying the 'pa' patches. Is that on purpose? You could try the other rom types. You are using the program correctly, so if they do not work, then we do not support the Carbon rom. We only claim to support the roms on the supported list of the OP. Everything else is just a bonus.
[Android Software/Hacking General [Developers Only]] revnu:
Hallo,

I get errors with my AOSP-ROM :(

can you PLZ try to make a patch for the AOSP Supernexus2.0 build4 ROM ????

I put really much work to this GREAT ROM......many many settings and apps. Now I'm nearly finished, only openPDroid is missing.

Dont want to change ROM now only for PDroid, but it's such a big APP :( :( :(

best regard & THX 4 your work

revnu
[Android Software/Hacking General [Developers Only]] go2net:
I am using CM10.1 AOSP 4.2.2 Jellybean [KANG] [April-11] from this link http://xdaforums.com/showthread.php?t=2115520

from March.9 to now, Auto-Patcher can not be applied on this ROM, following is patch log

$ ./ApGPackages/ap/auto_patcher rom.zip

The Auto-Patcher v2.9.1

### verify tools ###
### verify ROM ###
### unzip patch tools ###
### unzip patch patches ###
inflated: system/build.prop
### probe rom type ###
... result of ROM check: version= 4.2.2 rom= cm ...
... Using results of ROM check ...
No mods selected. Defaulting to openpdroid, since that's what you probably want.
..
... openpdroid patch date has been set to: 20130219 ...
### unzip rom ###
inflated: system/app/Mms.apk
inflated: system/framework/core.jar
inflated: system/framework/framework.jar
inflated: system/framework/services.jar
inflated: system/framework/telephony-common.jar
### create updater script ###
inflated: META-INF/com/google/android/update-binary
inflated: META-INF/com/google/android/updater-script
... using Clockworkmod installer ...
### create restore.zip ###
### decompile system files ###
... decompile framework.jar ...
... extract preloaded-classes ...
... decompile core.jar ...
... decompile services.jar ...
... decompile telephony-common.jar ...
... installing framework files ...
I: Framework installed to: D:\Profiles\shijq\apktool\framework\1.apk
... decompile Mms.apk ...
### copy patch openpdroid/4.2/cm/20130219 ###
... copying system/media/PDroid.jpeg ...
... overwriting ContentResolver.smali ...
### jar patch openpdroid/4.2/cm/20130219 ###
... apply framework.patch ...
1 out of 1 hunk FAILED -- saving rejects to file 'smali/android/app/ContextImpl$
42.smali.rej'
1 out of 1 hunk FAILED -- saving rejects to file 'smali/android/app/ContextImpl$
43.smali.rej'
1 out of 1 hunk FAILED -- saving rejects to file 'smali/android/app/ContextImpl$
44.smali.rej'
2 out of 13 hunks FAILED -- saving rejects to file smali/android/app/ContextImpl
.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file smali/android/app/WallpaperInf
o.smali.rej
... apply preloaded.patch ...
!!! PATCHING FAILED FOR android/app/ContextImpl$42.smali' android/app/ContextImp
l$43.smali' android/app/ContextImpl$44.smali' android/app/ContextImpl.smali !!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed android/app/ContextImpl$42.smali' in framework.jar cannot be r
emedied
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

usage: ./auto_patcher <ROM> <MODS> <ROMTYPE>
example: ./auto_patcher CM10.zip openpdroid cm

Use ./auto_patcher -h for the help menu
[Android Software/Hacking General [Developers Only]] BlackDex:
Also as stated by Albinoman887 him self, that it should work, as that Team Hydra which is revering to is nothing but a collaboration of a few people and not some special ROM. See http://xdaforums.com/showthread.php?p=40178991#post40178991 for his comments. Would be nice if at least OpenPDroid will work with this ROM by useing the Auto-Patcher :).
[Android Software/Hacking General [Developers Only]] Darkman:
Thanks for Feedback!!

But one more question.... what have this with PDroid.jpeg to do?? It is only a Picture? I want to understand this....
[Android Software/Hacking General [Developers Only]] scutworker:
The jpg is a Pdroid banner which is presented to an app if you block the camera and the app tries to take a photo.

So the app takes the photo and it gets the jpg rather than what is in front of the camera.
[Android Software/Hacking General [Developers Only]] logicmann:
@mateorod

I thought that this rom is pure AOSP??? Stock Rom is in my oppinion a samsung original rom ???
[Android Software/Hacking General [Developers Only]] mateorod:
Well, as shown by the ten to 12 logs that have been posted by albinoman users, ever since he changed from the Team Hydra base from straight cyanogen base, it stopped working for the albinoman kang, while still working for all other users of straight CM code base. So we can say with a high sense of certainty that the rebase is the problem.

I responded to albinoman in his thread, it is pretty much all I can do for you guys. I told another of that rom's users, if you want help building OpenPDroid builds of that rom, start a thread in the Sensation device forum and post a link here. Once you have built a straight build of any rom, adding OpenPDroid is simple and easy.

Edit

Believe it or not, Nexus devices do NOT ship with AOSP. They have lots of proprietary Google code that is not the same. That is Nexus stock, not AOSP exactly. An easy example is stuff like gesture keyboard which is proprietary. Another is that AOSP comes deodexed, while stock roms do not.

They are very very close, but just enough to where they don't work with the AOSP patches. We have a team member working on this as he has time, someday soon we hope to support stock for most companies, with Nexus being our first target.
[Android Software/Hacking General [Developers Only]] Rita Muster:
Thank you for OpenPdroid and the AutoPatcher GUI!!!!

I will never again use android without openpdroid.

Thank you!!

But I have a question:

Has someone the knowledge to patch a MIUI build with openpdroid? Miui comes with LBE. But I don´t want to use LBE.

ROM Link: JBMIUI V5

Would do nearly anything for a patch. ;)

THX a lot
[Android Software/Hacking General [Developers Only]] mnjm9b:
Is auto-patcher going to resume pdroid2.0 App support?

according to the OP auto_patcher is supposed to continue supporting the pdroid2.0 app but

as of yet has not been.

according to a recent post from CollegeDev autopatcher won't support Pdroid2.0 anymore...

the Opendroid Manager app that is the only auto-patcher supported app seems to dead. last updated in january.

and from the manager thread itself admits to being horribly full of bugs and not as good as pdroid2.0 yet.

so could you please resume pdroid2.0 support...

why would you stop support for an actively developed app for a stagnate incomplete insufficient app?

(BTW I fully support the opendroid concept however you really left a lot of people hanging...)

I would build and patch my own rom but my laptop can no longer handle compiling android.

auto-patcher has been my savior up until the dropping of pdroid2.0 support...
[Android Software/Hacking General [Developers Only]] kaizokan:
The reason why PDroid2.0 (framework) is not supported is because they are going to merge OpenPdroid and PDroid2.0 into one framework. Making auto-patcher support both frameworks is too much work and some other things. The apps (Pdroid manager and PDroid2.0 app) however will remain different and will both be compatible with the new (yet to come) PDroid. Thats why the latest versions of PDroid2.0 are not inside autopatcher.
[Android Software/Hacking General [Developers Only]] mateorod:
Yep. Also, we didn't "stop" supporting PDroid2.0. The newest PDroid2.0 patches just came out in late february. Before that it was only for 4.1.2. The very next update of OpenPdroid will be the merge with the PDroid2.0 functions. But I can only work with what I have on hand. If we hadn't started OpenPDroid, users wouldn't have 4.2 support at all. CollegeDev uses our porting method to 4.2.2 in PDroid2.0 as well as several other OpenPDroid changes, The exchange has been mutual, we are just working on making it official.

I am sorry that you feel like you got left hanging, I literally cannot imagine a way for me to be spending more time on this than I already am.

Thanks to everyone offering support/help to new users, I cannot do it without you!
[Android Software/Hacking General [Developers Only]] mnjm9b:
Thanks for clarifying...

I never meant to imply that I am ungrateful...I have been following this from the beginning...it was just lately there have been a lot of conflicting comments on the future of pdroid2.0 app. from several threads. And even collegedev himself has made conflicting statements...

I am more than willing to be patient for your hard work. I was only looking for clarification.

BTW Are you still working on the manager app...do you need help?
[Android Software/Hacking General [Developers Only]] mateorod:
Oh yeah, I ain't mad :). And CollegeDev and I are in contact, but many of the details are still getting hammered out. But big progress is currently being made, I am working on the update just about every day. shouldn't be too too long...assuming that everything goes well.

I haven't had anything to do myself with the PDroid Manager app, but I am very in favor of an open-source PDroid app existing, even if just as an alternative. I haven't pulled a fork of the app over to the OpenPDroid github page because they were invisioned to be separate projects, which I am glad we did now that we are merging with PDroid2.0 (the build patches, that is).

So yes, any contributions to PDroid Manager would be very welcome. I know that there is plenty of work to be done with it. If you do any work on a fork, let me know and I will star it to keep my eye on it. It needs an engaged maintainer, I cannot do it personally.
[Android Software/Hacking General [Developers Only]] jpeg725:
"stagnate" isn't the right word. The developers are working hard on merging the two frameworks.
[Android Software/Hacking General [Developers Only]] mnjm9b:
I wasn't talking about framework...
[Android Software/Hacking General [Developers Only]] logicmann:
@mateorod,

hey thanks for your info and the short discription. Now i know what rom i really have ;) So i have to wait for your member until he fixed this fo Stock ROMs.
[Android Software/Hacking General [Developers Only]] CollegeDev:
Btw.. New version v1.55 is out now. Just look at the OP. Feel free to test :)

Or just take a look at OP (topic STOCK-ROMs).
[Android Software/Hacking General [Developers Only]] jpeg725:
autopatcher doesn't support pdroid-manager either. autopatcher only deals with the framework.