yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] mateorod:
A known issue, and the thing that I want to solve so we can release the next patches. The two big bugs left (not that there aren't improvements to be made) is the cell tower issue and the MMS failures. I did get a log cat from one person, but a couple more logcats of failed Mms would be helpful.

Yes. I will let you know when I release new patches. It takes hundreds of hours of computer processing to update our full slate of patches, we can't do it all the time. If we can solve the Mms sookn, I would like to have that fix included. But we will begin building the new patches soon.
[Android Software/Hacking General [Developers Only]] wkwkwk:
Excellent, many thanks. Hopefully the Llama bug will be resolved as well.

Thanks.
[Android Software/Hacking General [Developers Only]] :
Direct link to the rom topic:

[AOSPA 4.2.1][22/01] PARANOIDANDROID 2.99 betaNINE

Direct link to download the latest version of the rom:

http://goo.im/devs/bluefa1con/paranoidandroid/pa_i9100-2.99-22JAN2013-091714.zip

Tried to resync and got this error:

http://codepad.org/78u9utSg

Hope you can solve it my friend :highfive::good:
[Android Software/Hacking General [Developers Only]] mateorod:
okay it is fixed. I have checked it myself on your rom. Look for 2.5.4, which is only up for ApG right now. I wll update our download page in the morning, but I am not aware of anyone else with this problem at this time.

Coming tomorrow:

We start building the new openpdroid patches, that fix:

camera lag

Sms/Mms bug

Some patch failures

Still going to have the Llama/Cell Tower bug, but we are working on it and a fix is for sure coming soon. Lots of other new development on the devel branches, check it out sometime.

I have built a bunch of roms with TabletUI, but I had some trouble making the patch this afternoon. But I will look at it again. The hard part is done, I figured out what coding needed to be adjusted and built the roms themselves...so tabletUI should be on it's way.
[Android Software/Hacking General [Developers Only]] SecUpwN:
AW: [Utility][2.5.0][1/13] Auto-Patcher (4.2.1 support)

Is this problem related to the fixes you mentioned?
[Android Software/Hacking General [Developers Only]] mateorod:
That sounds very like the Pdroid2.0 phone bug that has been discussed in the Pdroid2.0 thread since November or so. CollegeDev says he has a fix coming. But I don't think that bug exists with PDroidManager right now.

CollegeDev has been working with us on OpenPDroid, so I would expect that bug to go away when he next updates his app.
[Android Software/Hacking General [Developers Only]] SecUpwN:
AW: [Utility][2.5.0][1/13] Auto-Patcher (4.2.1 support)

The fix or the bug? I'd switch to OpenPDroid to make this go away, but I'd have to know how to migrate permissions first. You know, a wiki about the whole PDroid thing would be trivial. I mean, how is anyone not reading all posts every day supposed to know which app and patch to install? Seems like a mess right now.
[Android Software/Hacking General [Developers Only]] mateorod:
No. I say, clearly and for the record, that these patches have been only tested for Pdroid Manager. I never spoke for Pdroid2.0 because I have no knowledge or control about that.

If you think a wiki is trivial, then write one.
[Android Software/Hacking General [Developers Only]] nsmart:
Will this bugfix Device lags when GPS is active also be included in the new patches ?
[Android Software/Hacking General [Developers Only]] AuSSiELaMbChOpS:
Hi mateorod, thanks again for all your work on this. I successfully patched pa 2.99 tonight it ran through and replaced all files ok and produced the update and restore zips.

Flashed and the phone process was crashing continually tried the patch again just in case but got the same result.

Captured a bit of a logcat, don't know if that will be of any help or not:

http://codepad.org/O5nw6MfV

Log of the patch is below also, but like I said it patched successfully so I doubt there is anything useful in this:

http://codepad.org/tW6eMmgE

I am not much of a Android/Java dev I only really have experience with Windows programming but I am going to have a bit of a play with the smali provisional files that are used in that patch. I am comparing the original with the provisional and seeing if I can fluke anything :)

Thanks again mate and to everybody else your work on the auto-patcher and trying to keep the patches up to date for so many roms and mod is absolutely heroic!! You guys rock!
[Android Software/Hacking General [Developers Only]] karamelos:
Did you wipe cache & dalvik (or fresh install "fullwipe")?

For @moonstruckdrop & if other user want test

Rom: aokp_elf2_unofficial_Jan-16-13.zip

Log, patch & restore: http://d-h.st/Kpr

If not work report attached logs
[Android Software/Hacking General [Developers Only]] AuSSiELaMbChOpS:
Re: [Utility][2.5.0][1/13] Auto-Patcher (4.2.1 support)

Yep I wiped both cache and dalvik cache, I haven't done a full wipe and can't really do that tonight. I will give that a try tomorrow although I have never had to do that before with any of the other roms I have patched with auto-patcher. This is the first time I have ever had an issue after flashing the update zip, had patch errors yes but never any problems with flashing a successful patch.

Sent from my GT-i9100 using Xparent ICS Tapatalk 2
[Android Software/Hacking General [Developers Only]] SecUpwN:
AW: [Utility][2.5.0][1/13] Auto-Patcher (4.2.1 support)

So, seems like I'm not the only guy with a crashing phone service? Must be caused by the patch then.

How to import settings from PDroid to PDroid Manager? Wasn't there some post about it?
[Android Software/Hacking General [Developers Only]] Klaus N.:
OpenDroid & V6 SuperCharger

Hi!

The last few days I tried to patch CM10.1 for OpenDroid and for SuperCharger. But I recognized, when I flash the OpenDroid-patch and after that the patch of SuperCharger, then I get errors, when I try to save the adjustment of the behaviour of an app in OpenDroid. SuperCharger works fine doing this way.

First flashing the SuperCharger patch, and after that the patch of OpenDroid, SuperCharger works only partially.

Therefore my question is, is there an opinion, that both patches work without problems?

Thank you!

Klaus.
[Android Software/Hacking General [Developers Only]] karamelos:
Re: [Utility][2.5.0][1/13] Auto-Patcher (4.2.1 support)

In pdroid2.0 or openpdroid thread you have the solution

Ttb & restore your setting, make it in pdroid2.0 app before & tape reload app in openpdroid

Enjoy
[Android Software/Hacking General [Developers Only]] Klaus N.:
OpenDroid & V6 SuperCharger

Well, I found the solution by myself :D

In the ApG I selected both OpenDroid and SuperCharger by holding "crtl" in the left window, then choosed CM in the right window and "Start". So I got only one update.zip and one restore.zip.

Both OpenDroid and SuperCharger work fine now!

CU
[Android Software/Hacking General [Developers Only]] stealthmouse:
Can't Get OpenPDroid to Patch

Hi. I've attached logs. Still have issue that with AOSP defined by autopatcher, I received a no boot.img error. If I change it up to AOKP, I get a smali error, though no boot.img (in the prior version of autopatcher, I got a similar smali error if I changed the code to bypass the boot.img check). V6supercharger services.jar changes work flawlessly.

BTW, my device is a RAZR, which as you know has a locked bootloader, which could be the issue with the missing boot.img (?), but not really sure. Just giving you a heads up. Thanks for any help!
[Android Software/Hacking General [Developers Only]] noonecanhide:
AW: [Utility][2.5.0][1/13] Auto-Patcher (4.2.1 support)

Maybe completely OT but is it possible to patch rom files directly on an android device ? Usually i download the nightlies to the mobile device itself, and it would be very nice to patch the files there :)
[Android Software/Hacking General [Developers Only]] mateorod:
The two of you with this issue let us know if following the instructions here works. It should.

Well, I did just rearrange all of this in order to make ApG a little more intuitive. Sounds like I made an error. I don't think there is a way to roll back to an earlier version with ApG, but if you are willing to do this manually you could likely get 2.5.2 to work. Could you post a link to your ROM, please? Even though you may have exposed a bug, I am not so confident you are going to have success in any case, that ROM sounds somewhat off of our supported list. But I will check the script and test it if I can find it.

We're working on it. It is asking a LOT from a phone/tablet to handle this processing expense. Some people have given up on it as impossible. It is our very next challenge once 4.2.1 is stable.

Not OT, exactly, but not exactly soon either. What you are suggesting, in a manner of speaking, is for us to build the phone's software on the phone itself. We have ideas, but that is no small thing. :laugh:
[Android Software/Hacking General [Developers Only]] :
Have patched sucessfully the rom:

[AOSPA 4.2.1][22/01] PARANOIDANDROID 2.99 betaNINE

And the log is this one:

http://codepad.org/xA8rsSo8

The patch and restore are in this links:

Patch:

pa_i9100-2.99-22JAN2013-091714-openpdroid-20130125-update.zip - 7.72 MB

Restore:

pa_i9100-2.99-22JAN2013-091714-20130125-restore.zip - 6.68 MB

I keep getting an error of:

We are sorry but the process com.android.phone has been interrupted.

Hope this gets fixed :highfive:

Mine always is :D
[Android Software/Hacking General [Developers Only]] a3955269:
hi,

for those interested, i've ported pdroid 1.32 patches to omega 19.1.

i've used the smali patches found in autopatcher (https://github.com/mateor/auto-patch.../aokp/20121013) as a base.

would be nice if pdroid could be included in omega

http://xdaforums.com/attachment.php?attachmentid=1674201&d=1359085253
[Android Software/Hacking General [Developers Only]] :
Omega? There are lot's of Omega ports! To which one you refer to? :eek::eek:

Edit:

Galaxy SII you mean: http://xdaforums.com/showthread.php?t=1489197
[Android Software/Hacking General [Developers Only]] vitocor:
Slimrom--4.2.1.RC.1-OFFICIAL

Mateorod wrote:

...your eye and butt pain is nearly extinguished.:laugh:

Me write:

Absolutely right...what a nice word. All the pain are gone. :victory:

Thousand thanks to you to bring openpdroid work now with the Slimrom 4.2.1

Creating the patches was like a homerun...no problems with cygwin in Terminal.

The permission settings are working on my girlfriends Samsung Galaxy S3-I9300 and on my Note N7000 full functional!!!

The patches are attached for those who needed.

Thanks again for this great work and for your help.

Best wishes and greetings.

Vito

Ps.: I will now search for your donation link and invite ya a for a beer or two ;)...you really deserve it.
[Android Software/Hacking General [Developers Only]] Sandpapers:
Having an issue with autopatcher 2.5.3 on slimdroid for lg p930. Everything is good up until system/pdroid.jpeg missing. Weird error, was doing openpdroid,v6supercharger. Regular pdroid,v6supercharger works. Any solutions?
[Android Software/Hacking General [Developers Only]] mateorod:
Thanks, as always, for coming in. I have not, by a long shot, forgotten about what went walked about. Me and a couple of the OpenPdroid guys are moving on it once we get this 4.2 update relatively stable.
[Android Software/Hacking General [Developers Only]] mateorod:
Auto-Patcher 2.5.7 is out

Improvements include:

TabletUI for all roms (and I believe all devices, let me know) that are compatible (Cyanogen, AOKP, AOSP and Evervolv)

Improved error checks and patch availability menus

This release brings us back to full complement, as in every mod that was available for 4.1.2 is now available for 4.2.1, with the exception of the original PDroid. (and some compatability questions with the PDroid2.0 app, which we will be fixing with CollegeDev). Once we update OpenPDroid (read below) I am hoping that 2.6.0 can be another LTS release (which for us is measured in months, but still)

OpenPDroid update

The building of the new OpenPDroid patches is going to begin tonight. If it goes without hiccups, then I would estimate that they will be out in a few days. If you have a pet issue with the OpenPDroid patches, you can check out issue dashboard on github. But the major usability bugs have been squashed and will be included. We may even get the Llama/Cell Tower bug kicked, CollegeDev is trying to get it to us.

We are working closely with CollegeDev to increase and hopefully get Official PDroid2.0 support with OpenPDroid. CollegeDev has been very active in the discussions about the improvements, so everyone is benefitting from the teamwork.

Those of you who were asking for tabletUI, tell some friends. This was an even bigger pain in the butt than I thought it would be, and I was pretty sure it was going to suck.
[Android Software/Hacking General [Developers Only]] AuSSiELaMbChOpS:
Hey mateorod, I couldn't really follow the migration instructions as I had not had Pdroid 2.0 or OpenPdroid installed at all on PA 2.99, I did check data/system and confirmed there were no privacy databases, files or the directory present.

Today I did a full wipe and tried again what I tried was - data/factory reset, format /system and cleared cache & dalvik cache.

Installed PA 2.99 betaNINE and flashed the update zip and got the same thing, once I hit the lockscreen I instantly get com.android.phone process has stopped working. That just repeats over and over.

Only thing I can put it down to is that PA 2.99 betaNINE build for the Galaxy SII must be different to the others as you can get it working fine on your grouper.
[Android Software/Hacking General [Developers Only]] nk7:
Seems I got similar results with latest nightly from RootBox and also from v3.5. Opendroid patches are coming soon perhaps wait a bit longer when they begin to add support for such roms. Meanwhile I recommend SlimROM
[Android Software/Hacking General [Developers Only]] haelmchen:
After flashing the zip for OpenDroid on 4.2.1 (AOKP) i can´t send any text message
[Android Software/Hacking General [Developers Only]] :
Re: [Utility][2.5.7][1/25] Auto-Patcher (4.2.1)

Post the log in code sector site -.-

Or a txt and attach it to your post

If you can't do this simple task and avoid posting it and making such a huge post you shouldn't be using this..
[Android Software/Hacking General [Developers Only]] kobik77:
I've uploaded new ApG version with some GitHub sync related fixes and error handling, plus some GUI additions and rearrangement.

What also new is the ability to open ApG and AP log files directly from the GUI (You can set your favorite text editor to open them if it's not associated with *.log files from the INI file)

If you're having GitHub sync problems with this version please share you ApG log.
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
Re: [Utility][2.5.7][1/25] Auto-Patcher (4.2.1)

I'm currently out of town and away from my computer so I cannot check to see if the new ApG is flagged by norton, sorry. If it is than please go back to the work around method.

Injected by my ViperXL using Tapatalk 2
[Android Software/Hacking General [Developers Only]] brGabriel:
First off, I'm really grateful for all the hard work put into this fantastic utility.

I tried running this script for the first time on a stock-based 4.2.1 ROM for Nexus10 (manta) to obtain tabletUI. The script seemingly executed flawlessly; however, upon flashing the update .zip for tabletUI there was no change in the interface. Anyway, I've attached the log file in case there's something I did incorrectly. Seems pretty straight forward, but who knows.

P.S. Here is a link to the ROM I was attempting to patch: http://xdaforums.com/showthread.php?t=2113048
[Android Software/Hacking General [Developers Only]] mateorod:
Sorry, this is a known issue that we have fixed, but not distributed. We are making those patches now. For the moment, you van reinstall the MMs.apk that came with your ROM.

Nothing is wrong, per se. That ROM just isn't supported and isn't on our supported list.

The Nexus10 already displays in tabletUI, so there will not be any change for that device. That mod changes the interface for phablets and (hopefully) phones to display the interface you see every day.

Kobik77, ladies and gentlemen. Thanks!
[Android Software/Hacking General [Developers Only]] brGabriel:
Perhaps we have a misunderstanding in terminology. The way I understand "tabletUI" is a single bar positioned at the bottom of the screen with navigation buttons to the left and clock/notifications on the right. That is not the default UI on the Nexus10. See below:
[Android Software/Hacking General [Developers Only]] mateorod:
Well how about that. If they don't ship 10 inch tablets with tabletUI, then why have it in the code at all?

I don't know what in the code causes the 10 to display PhabletUI. But without a device, I can't really do much. I can poke around, but if the methods that work for the 7 inchers don't work for other devices, then that is as far as I can take it. It is just a little sideline for me, sorry.

I will take a peek at this, but most likely I won't be changing anything. I will add the info the OP, thanks for the report.
[Android Software/Hacking General [Developers Only]] brGabriel:
Don't worry about it. As far as I know, the trigger for tabletUI is the same as the Nexus 7. I can say this with a fair amount of certainty because a fellow member compiled an AOSP rom with tabletUI for the Nexus10 and said he simply made the edits pointed out by barrmulio.

I suspect the issue is more ROM-related than with your script compatibility with Nexus10 devices. To find out for sure, I will try it on another ROM and report back. :good:
[Android Software/Hacking General [Developers Only]] mateorod:
Those are basically the same edits we have here, although with Cyanogen it needed some edits to DateView, Settings/...Util and NavbarEditor classes. But the AOSP, AOKP and Evervolv patches are identical to those original edits, just updated for their 4.2.1 locations. If those edits work for Nexus10 then this mod should work. It certainly ported no problem for 4.1.2.

Let me know what happens, there is a disconnect somewhere. It could always be on this end as well....
[Android Software/Hacking General [Developers Only]] brGabriel:
Sorry, no go on two other AOSP ROMs I tested tabletUI. Its got me scratching my head too.

If its any help, I've attached the patched files from a working Nexus10 AOSP Rom with tabletUI. Maybe you can use it as a basis for comparison. If I knew what I was doing I'd try to look into it as well.
[Android Software/Hacking General [Developers Only]] samsungmario:
Can you show me how you did the patch? Did you build the Omega rom yourself? I am trying to replicate what you did to other similar roms like Neat LS8 but can't do it.

I tried your patches on Omega 19.1 and they work well. Cheers.
[Android Software/Hacking General [Developers Only]] l3ullseye:
I had a problem with SuperXE 4.1.2 build 7

http://codepad.org/MUUgxLQv

I tried Manual Patching, and apparently works. but when I apply the update.zip patch, it keeps FC the phone app :( I used this commands "pd2.0" and "aosp"

And I also tried with 4.2.1 build 2 and it gave me this error http://codepad.org/aWAzuaK5

Thanks

Link to the roms http://xdaforums.com/showthread.php?t=1942239
[Android Software/Hacking General [Developers Only]] mateorod:
Something is screwy...I will need to look into this after all. I just tried patching a buch of roms. The CM patches work as expected, but the aosp only turned the rom into tablet UI on a staright aosp build I made. I tried to other moslty pure aosp sources and they patched fine but the UI stayed the same, exactly as you experienced. I am going to check it out in more detail.

Could you give me a link to that post wth the compiled components? I am going to see if they have a restore.

I don't see why this failed, as they advertise pure aosp, but you areusing the patcher correctly. Maybe the pyramid needs a bunch of modification to run AOSP, but any all devices supported by CM and AOSP are supported here, and almost all of the unofficial. The only device I am aware of that struggles is the defy- maybe the sensation as well. Have you tried a Cyanogen rom?
[Android Software/Hacking General [Developers Only]] brGabriel:
Forgive me, my brain isn't firing on all cylinders at the moment.

Is this what you need: http://xdaforums.com/showthread.php?t=2078315

No one has released a standalone flashable MOD for tabletUI on the Nexus10. Only a couple of ROMs that have been modified from the source.
[Android Software/Hacking General [Developers Only]] gaich:
And I do not use this. You should have known it if you read my post instead of measuring it.:silly:

Thank you! There`s always hope the ROM is included in "...and many others" section...:fingers-crossed:. As my friend said, he tried the patcher with previous versions of the same ROM and it worked... As for Minco - is it supported? The patch works in V6, but when installing the result in the ROM, it shows status 7 error. It would be great if you could give some advice, Thank you.
[Android Software/Hacking General [Developers Only]] regulusv7:
If you delete telephony-common from inside the update zip you won't get that error. Still testing to see how important that file is.
[Android Software/Hacking General [Developers Only]] madyinwhich:
Hi,

first of all a big thank you to all involved here. But I have a problem after flashing the update. I have a Galaxy S2(intl) and I use CM10.1 nightly builds.

After flashing I have trouble as soon I switch to mobile network.

First the process of switching takes some time and if I pull down the status bar it get stuck sometimes and the background image disappears afterwards for a short period of time, as well the status bar infos. The apps which need root don't start properly because they don't get root access instantly. The message 'The app has been granted superuser permissions' appears more then a minute later (or even longer) after closing the app. After some time all gets better almost up to normal. With WIFI I have no problems.

'

I wiped already the cash and dalvik cash and did a 'Wipe data/factory reset' because I thought it could have something to do with some apps but no changes at all.

The patch process runs without problems except this here:

... apply telephony-common.patch ...
1 out of 78 hunks FAILED -- saving rejects to file smali/com/android/internal/telephony/cdma/CdmaServiceStateTracker.smali.rej
1 out of 4 hunks FAILED -- saving rejects to file smali/com/android/internal/telephony/gsm/GsmServiceStateTracker.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
15 out of 15 hunks ignored -- saving rejects to file 'smali/com/android/internal/telephony/RIL$RILSender.smali.rej'
3 out of 20 hunks FAILED -- saving rejects to file smali/com/android/internal/telephony/SMSDispatcher.smali.rej
!!! PATCHING FAILED FOR com/android/internal/telephony/cdma/CdmaServiceStateTracker.smali com/android/internal/telephony/gsm/GsmServiceStateTracker.smali com/android/internal/telephony/SMSDispatcher.smali !!!

File for which patching failed:
---------------------------------------------

CdmaServiceStateTracker.smali

---------------------------------------------

We can try to add a premade copy of those files.
This sometimes works.

You only need to report this if running the program gives you problems!!!

Thank you in advance for any help!
[Android Software/Hacking General [Developers Only]] nachod0g:
I can confirm the same behavior, I'm hoping it will be fixed with the database caching.