yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] IRKONIK:
Push! The missing log is still a problem, even after a full wipe and a clean flash. Also no GSM. UMTS, WiFi and Bluetooth work.

EDIT: Nevermind, new version is out. Will try to patch it (both ways, so 200 and 000, if I can call them that way) and upload the zip's to zippyshare again.

URL to gokussjx' version: AOSPA 3.55 Samsung Galaxy S3 Intl GT-i9300

EDIT 2: 200 Method aka normal fails. Let's see if the "000" method works.. fingers are crossed!

EDIT 3: The "000" method "works", but has 2 errors (but there is no log)

Zips here:

pa_i9300-3.55-22MAY2013-062247-openpdroid-20130522-update.zip

MD5: ae8e9b0bd87e2c42d30a4ab826f39b91

pa_i9300-3.55-22MAY2013-062247-20130522-restore.zip

MD5: 19e354c23500c7ed4fc60d05e9f291bb
[Android Software/Hacking General [Developers Only]] denzel09:
Good work for community ;)
[Android Software/Hacking General [Developers Only]] brGabriel:
TabletUI patch still working great! Thanks guys! :highfive: Ça c'est bon!
[Android Software/Hacking General [Developers Only]] r0zj0k3r:
attached is a logcat from my aosp browser crashing if I try to manual set location or use the random feature. I also get crashes using dolphin and the same setup. Reproduced on multiple AOKP AOSP, CM10.1 ROMs. No problems if you just deny location access, so I can't really complain, but I thought you might be interested.

ROM KAOS Droid (based on AOSP Android 4.2.2) using openpdroid

Sent from my Galaxy Nexus
[Android Software/Hacking General [Developers Only]] karamelos:
Hi mateo last cm10 05222013 broken autopatcher so i build it from sauce

I submit diff If you want

See you later
[Android Software/Hacking General [Developers Only]] lastot069:
android app

Let me start by saying this is the best program ever! My suggestion would be to make a app for android that mimics what you are doing here. Thank you so much for this.:highfive:
[Android Software/Hacking General [Developers Only]] mateorod:
Thanks for the backup :)

Anyone who wants to examine the progress or maybe even contribute/review can look here. All branches are active, some are feature specific.

I push my latest commits every couple days or so.

If you already have it built, that would be great. Thanks karamelos.

It is a tricky thing...I would much rater be working on this than the update to OpenPdroid, let me tell you. Someday I hope to get the time to do just this.
[Android Software/Hacking General [Developers Only]] lastot069:
the fact that this can be used on essentially any rom across many devices is what drives me to the best ever conclusion, again thank you for any time you put into it!
[Android Software/Hacking General [Developers Only]] lastot069:
help

Anyone have kobik's files, the site is down and i cant get them.
[Android Software/Hacking General [Developers Only]] sabret00the:
Is there a way to change which branch AutoPatcher builds OpenPDroid from?
[Android Software/Hacking General [Developers Only]] Datastreamx:
Ok so ApG doesn't work anymore. It stopped updating packages so I wanted to do a full reinstall of it. But now it can't even install Java on it. I ran it in administrator and never had these problems last time I used it. Which is 3 months ago or so.
[Android Software/Hacking General [Developers Only]] SimonTS:
It works fine for me, used it a couple of hours ago to patch the latest CM with openDroid.
[Android Software/Hacking General [Developers Only]] mateorod:
Sorry, not that I know. And I really don't have much advice for those of you (the few) who may or may not be having ApG related issues outside of uninstalling completely and reinstalling seems to sometimes make a difference.

Okay, news.

There has been an addition to the Autopatcher which proposes to install a framework allowing us to more easily apply bug/hotfixes to the patches without requiring me to rebuild for every device. It should make the Autopatcher more limber, which will be a requirement for when the merge goes out and we need to fix bugs. This feature was added by phillipberndt and is very welcome.

It has just been pushed to

Autopatcherv2.9.7.

We are testing it with another contribution of phillipberndt's, A fix for the GPS location bug, We hope that this will fix problems with cell tower location and allow apps like Foursquare, Llama and Tasker to work.

You do not need to do anything special, this fix should apply to all roms immediately. You will see it in the output/log as services-gps_fix.patch.

Look for it in ApG or a git pull now. Unfortunately, it looks like techerrata is having a spot of technical trouble, so I have added a temporary download for autopatcher2.9.7 at goo.im. It may take a moment to show up.

I have added the bugfix to ALL 4.2.2 roms, if it seems to work well, I may backport it to the other Android versions as well. Let me know how it works, ok?

Edit: While that new download link may eventually work, even when manually rebuilding the index for all of goo.im the new file has not shown up yet. So the problem may be with the entire goo.im family. I have uploaded the latest autopatcher2.9.7 here.
[Android Software/Hacking General [Developers Only]] Datastreamx:
That's great for you but meanwhile it doesn't work for me. It installed its **** but now it *****es "Failed getting patch list from patch_patches.tgz"

So yea...
[Android Software/Hacking General [Developers Only]] dardragon:
Hi

I tried to use the tabletUI patch on cm-10.1-20130525-NIGHTLY-p1.zip (from get.cm) however I run into an error. Attached are the log files that were returned from ubuntu

Log from Windows:

http://codepad.org/dJJT1Uuw

I have been able to patch the Nexus 7 version of cm 10.1
[Android Software/Hacking General [Developers Only]] Caldair:
When I pulled apart the SystemUI.apk from your rom I found the problem. Below is the way that every CM10.1 rom I have seen (including the 3 I decompiled today from Nexus 4, Galaxy Tab 2, and Kindle Fire 2) looks at /res/values-sw720dp/dimens.xml :

<dimen name="status_bar_recents_app_icon_left_margin">0.0dip</dimen>
<dimen name="status_bar_recents_app_icon_top_margin">8.0dip</dimen>
<dimen name="status_bar_icon_padding">1.0dip</dimen>
<dimen name="notification_panel_width">512.0dip</dimen>
[COLOR="Lime"]<dimen name="system_bar_icon_drawing_size">24.0dip</dimen>[/COLOR]
<item type="dimen" name="system_bar_icon_drawing_alpha">100.0%</item>
<dimen name="system_bar_navigation_key_width">80.0dip</dimen>
<dimen name="system_bar_navigation_menu_key_width">80.0dip</dimen>
<dimen name="notification_ticker_width">360.0dip</dimen>
<dimen name="status_bar_panel_bottom_offset">36.0dip</dimen>
[COLOR="Lime"]<dimen name="notification_panel_min_height">770.0dip</dimen>[/COLOR]
<dimen name="panel_float">56.0dip</dimen>
<dimen name="status_bar_recents_width">600.0dip</dimen>
</resources>

Now this is how the one from your P1 rom looks:

<dimen name="status_bar_recents_app_label_left_margin">16.0dip</dimen>
<dimen name="status_bar_recents_app_icon_left_margin">0.0dip</dimen>
<dimen name="status_bar_recents_app_icon_top_margin">8.0dip</dimen>
<dimen name="status_bar_icon_padding">1.0dip</dimen>
<dimen name="notification_panel_width">512.0dip</dimen>
[COLOR="Red"]<dimen name="notification_panel_min_height">770.0dip</dimen>[/COLOR]
[COLOR="Lime"]<dimen name="system_bar_icon_drawing_size">24.0dip</dimen>[/COLOR]
<item type="dimen" name="system_bar_icon_drawing_alpha">100.0%</item>
<dimen name="system_bar_navigation_key_width">80.0dip</dimen>
<dimen name="system_bar_navigation_menu_key_width">80.0dip</dimen>
<dimen name="notification_ticker_width">360.0dip</dimen>
<dimen name="status_bar_panel_bottom_offset">36.0dip</dimen>
<dimen name="panel_float">56.0dip</dimen>
<dimen name="status_bar_recents_width">600.0dip</dimen>
</resources>

I highlighted the 2 values that are patched. You can see that in your rom the notification_panel_min_height is placed above the first value that is patched.

I don't know why this particular build of CM is this way when every other one I have encountered is the same. But this is what is breaking the patch.

Sorry I guess the P1000 isn't auto-patcher tabletUI patchable after all... out of the box.

I decided while I was writing that last line to rewrite that particular part of the patch specifically for your tablet and try again, and it works!

I have attached a file with the P1000 specific patch for CM10.1 TabletUI. You should have no problem on ubuntu replacing the 20130403 folder in patch_patches.tgz located at /patches/tabletUI/4.2/cm/ with the 20130403 folder contained in the attached zip.

This should allow you to patch CM10.1 for TabletUI on your P1, and should work for future builds too.

All I ask is if(when!) you are successful in patching that you share the fruits of your labour with the P1000 community, and enjoy TabletUI of course!:laugh:
[Android Software/Hacking General [Developers Only]] el_liberator:
Damned :(

the new SlimBean Build 5.8 for Mako isn't compatible with OpenPDroid :(

!!! PATCHING FAILED FOR android/provider/Settings$Secure.smali' !!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed android/provider/Settings$Secure.smali' in framework.jar cannot be remedied
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[Android Software/Hacking General [Developers Only]] dardragon:
Thanks Caldair

I just flashed my P1 and it works as expected.
[Android Software/Hacking General [Developers Only]] mateorod:
I took a look in the p1 device tree, assuming that we would see that section in the device overlay. But I don't see where this is being caused...?

Here is the frameworks/base tree, just as you describe it (and untouched for 8 months).

Here is the overlay directory for the p1, which doesn't touch the values-sw720dp directory, or anything UI-related that I found.

That leaves me thinking that perhaps the p1 is using it's own fork of frameworks_base, although a look at the p1 wiki template didn't tell me much either. The idea was to quicky shoot them a patch rearranging their overlay/fork so as to be in line with upstream. That is best-practice for this stuff regardless of the utility to us with the autopatcher...a merge conflict waiting to happen.

But I don't see a fork, and the p1 maintainer (cdesai) has only private repos. Sorry, I had hoped to lend a hand, inspired by Caldair's efforts.

edit: I will rebuild for SlimRom today.
[Android Software/Hacking General [Developers Only]] el_liberator:
Thanks a lot :good:
[Android Software/Hacking General [Developers Only]] txoof:
Apologies, I realized this is in the wrong thread.
[Android Software/Hacking General [Developers Only]] KingKuno:
Hi, can not syncing autopatcher (http://xdaforums.com/showpost.php?p=31648393&postcount=690) with github changes, why ? Yesterday, it works. And because of this I can not patch my rom. Maybe it will be better when we can patch it whether it is syncing or not (because main files are dowloaded).
[Android Software/Hacking General [Developers Only]] allofusjw:
A quick FYI regarding mms.apk...

*Apologies if this has already been suggested. A quick search of the thread from past few months didn't reveal this exact solution.*

For a while now I've had the issue with the messaging app not appearing in app drawer(even though it is installed in /system/app) after patching jb aokp. It happened again today but I fixed it. I used the ZipSigner app to sign the mms.apk from the patched update.zip, then copied the newly signed mms.apk into /system/app/. The app instantly appeared in my app drawer and is working fine.
[Android Software/Hacking General [Developers Only]] SheridanJohn:
Current nightlies fail on openpdroid?

Hi,

I was about to update to the current nightlies (20130530), however ApG failed:

http://codepad.org/a9uDNc8T

I did the git update, but I am not sure it got something, changelog stops at 2.9.1 from 2012-04-10, however as the first post in this thread also mentions 2.9.1, I assume this is still current. The used openpdroid patch (also the one that failed) was dated in february.

I tried p4 and maguro with the same result.
[Android Software/Hacking General [Developers Only]] Sh0wt1me:
Error

Hi!

I get an error trying to patch this ROM

Here's the code: http://codepad.org/0wbxNIch

Any help? :)

Thx
[Android Software/Hacking General [Developers Only]] mateorod:
What rom did not patch? I just went to test which patch was broken, and the 0524 build of mako patches okay for me...do you have a link and a log?

I do not know much about ROOTBOX or Xenon, but for now there are no plans to expand the supported rom list with the current patching technique. Once the next update of OpenPDroid goes out, I have somewaht large plans for the patching process which I hope will allow support to be much, much wider. But for now we support straight AOSP, AOKP, PACman, PA, CM, SlimRom and EverVolv in addition to whatever else people have found to work (some, but not all kangs of the above list). Somewhere in there we should have support for multiple roms for most devices...if you need another rom because of some killer feature than you will have to choose that feature over Pdroid, for the moment.

As for that Rootbox logs, whatever they have going on with the Mms.apk is breaking the decompile with apktool, so they likely have something there that is incompatible with the patching process as it no matter the rom type.

I am not quite sure what KingKuno means by that last sentence, but I do not know much about what is going on with ApG internally. Something I have seen work is to delete ApG and reinstall. I know that is not evry helpful, sorry. You could also try patching manually with a zip downloaded from our download page...the instructions on the OP will work in a cygwin terminal and it isn't too hard once you figure out how to navigate to the proper directory (where ever you have the download extracted to).

But there are newer CM patches that will patch that nightly up on github and the download page already.

I think I may know why this is happening...I made some changes to the Mms handling last night. I intended to push them out with the new SlimRom patches, but it turns out that they may not be necessary. They will go out soon but if they do not help, I will try signing the apk again...it shouldn't be necessary, but that doesn't mean that isn't actually the problem...

What I found was that the Mms apk is being rebuilt even when we copy over a prepatched file...so it is possible that the apk is being overwritten again. We will see if things change with the next update...if not I will add a signing process. We had that with the very first versions of the Pdroid-Patcher (the project that birthed this one...) so I am familiar with it.

Thanks a bunch for the investigation!
[Android Software/Hacking General [Developers Only]] el_liberator:
Hi

I compile SlimBean from Github's sources (SlimBean Github), since 5.8 build (0528), AutoPatcher doesn't works

log file : log20130530220733.txt
[Android Software/Hacking General [Developers Only]] Datastreamx:
I have this same problem. Or at least I think I do because updating the patches seems to be going too fast and I can't seem to patch any ROMs with opendroid.
[Android Software/Hacking General [Developers Only]] mateorod:
Okay, I confirmed this against my home build. We chase the binary packages here at the autopatcher so we will have to wait for the next SlimROm release before I can update the patches, or else they will wotk for you and no one else. But you can apply the source patches to your build and have a natively patched build in less than twenty minutes. There are pretty simple instructions on the third post of the OpenPDroid thread linked in the OP. Let me know when the next...weekly I guess...slimrom is out and I will upload the new patches.

Okay. thanks. Has anyone try reinstalling? I believe that it isn't updating but I have also been having a bunch (a BUNCH) of trouble with github over the last 48 hours. Even browsing code in the browser is failing often.
[Android Software/Hacking General [Developers Only]] SheridanJohn:
I apologize, I could find the problem: I made a change to the checked out git copy due to the problem with the tabletUI patch missing its "latest" directory. Due to that change, git refused to update the structure. After deleting the checked out structure and getting everything again from git, it worked smoothly! Thanks!
[Android Software/Hacking General [Developers Only]] el_liberator:
Hi

It Work fine when including patches to ROM sources ;)

Thanks so much
[Android Software/Hacking General [Developers Only]] SheridanJohn:
Eventhough patching now works fine, SystemUI closes on opening the notification bar for P4 (Galaxy Tab 10.1) when using the TabletUI (and OpenPDroid) patches against the 2013-05-30 CM 10.1 nightly. I just installed completely clean (full wipe) and cleaned cache/dalvik after applying the patch.
[Android Software/Hacking General [Developers Only]] KingKuno:
Well, now it works again :).
[Android Software/Hacking General [Developers Only]] poo706:
Patching (ApG) Evervolv 4.2.2 nightly from 5/31 for openpdroid failed for the first time for me: http://pastebin.com/hFpJwMcA

I was running the 5/24 nightly before that, which patched just fine. http://evervolv.com/devices/vivow

[poo]
[Android Software/Hacking General [Developers Only]] mateorod:
Hmmmm....could you post a logcat to the TabletUI thread? I have a link to it on the OP. I think that Caldair and I could probably fix this, I will look at it if it is an autopatcher issue, and Caldair is amazing with his efforts on tabletUI. Drop him a line and maybe he will have an idea.

Okay...I can build new patches for this. Everything is breaking lately....luckily I have a build server somewhat up and running which somewhat mitigates the workload for these situations...thanks poo.

Edit: Shoot I forgot the whole reason I came and posted here...I have pushed a new version to github/ApG which changes the Mms.apk handling some. At the very least, users who end up with a prepatched binary getting copied over should have significantly faster autopatching. At best, I hope to have fixed the incredible disappearing Mms.apk problems.

If you are using 2.975 and above, please mention if you have the disappearing apk still or if the problem used to happen and now is fixed. Thanks guys.
[Android Software/Hacking General [Developers Only]] Caldair:
[MENTION=4342828]mateorod[/MENTION]: It appears that this is a TabletUI issue. I can confirm this on a couple of devices now. Hadn't flashed a CM build since the 26th, and all was well then, but some change on or about May 30 seems to be the culprit. I will work on a fix over the weekend.

PS - [MENTION=2779401]SheridanJohn[/MENTION]: Link to Auto-Patcher TabletUI thread, for further discussion and status updates.
[Android Software/Hacking General [Developers Only]] mateorod:
As Caldair just pointed out to me in a PM, actually I am the one who broke the TabletUI mod with a commit the other day. If you read the commit message, I knew that is what an incomplete feature that could negatively impact other mods. I just did not check and see if tabletUI was one of those potential breakages. Oops.

I will fix it this afternoon, thanks for your patience and Caldair for tracking down the issue. The download page 2.9.7 and earlier will still work manually, but that won't help the ApG people who automatically get all of our latest commits. It will be fixed today.

Edit: new Evervolv patches are up...I made the new patches for 0529 and up by estimate. So if it fails to patch for you, grab a rom with that build date or later.
[Android Software/Hacking General [Developers Only]] chainer1:
The new slimbean build 6 is out.

I'm not the original patch requester, but i would also like a openpdroid comp. rom ;)

And thanks for your continous and awesome support mateorod :)
[Android Software/Hacking General [Developers Only]] poo706:
Openpdroid patch was successful on 6/1 Evervolv nightly! Thanks so much for your continued effort, AND the incredibly fast turnaround time!

[poo]
[Android Software/Hacking General [Developers Only]] scutworker:
I too was able to patch the latest Evervolv nightly and am also pleased to see that the MMS.apk problem is also solved.

Thanks.
[Android Software/Hacking General [Developers Only]] mateorod:
Okay, well I tested the build 6 and I guess the patches broke again in between when I built them (4 days ago) and the release. The auto-brightness changes broke them. I am rebuilding (again) and it should be out later tonight.

I also saw some new errors from apktool when I was testing...we may have another issue on hand with that. I will let you guys tell me when I put them up.

That is great news about the disappearing Mms! That has plagued me, for real. I had no real way of finding out what was wrong, since none of my devices come with Mms included. But it finally jumped out at me and I hope it is gone forever. Caldair and I are testing the fix to the trickle down issues with TabletUI from that change...I hope to have it as a stable feature and the SlimRom patches all for 2.98 sometime later tonight.
[Android Software/Hacking General [Developers Only]] mateorod:
Okay...Autopatcherv2.9.8 has been sent to github/ApG and has been uploaded to our download page at techerrata.

Features above 2.9.7 are

new slimRom patches for OpenPdroid (OPD)

new Evervolv OPD patches

Overhauled apk handling decreasing runtime in many cases

FIXED the missing Mms.apk (We hope! Report please!)

Slim users

The SlimRom builds I have tested have Mms.apks that are resisting decompiling by apktool. That means that Slim users will have the premade Mms.apk copied into their rom. That unfortunately compromises any special Mms features from Slim, including the theme for that apk. It isn't an autopatcher problem so much as either a SlimRom error or an apktool deficiency. I looked at the SlimRom Mms repo briefly, but did not see what caused the problem. I will build apktool from source sometime next week and see if the apktool maintainers have prehaps merged anything to the tool that can handle those troublesom resources. ANy enterprising users can take the apktool errors in the code and report to iBotPeaches if they have the time. Hoepfully a solution will present itself soon. I can also maybe post the Mms.apk I made from source...I am not prepared to include it in the autopatcher (it isn't fair to make all other users deal with that extra file) but if you want it, I will upload it to the OP for now.

Thanks (as always) to Caldair for testing and diagnosing issues. He is a full team member here and a great addition.
[Android Software/Hacking General [Developers Only]] SecUpwN:
Cool, thanks! Are you still working on merging the patches to include PDroid 2.0, [MENTION=4342828]mateorod[/MENTION]?

It's gotten pretty quiet around the merge process (at least in this thread) and seems a little like [MENTION=4711230]CollegeDev[/MENTION]s work has been "banned". :o