We have moved support away from this thread and into the main thread at Android General. The info in the second post is accurate as of 12/3/12.
Development on the Auto-Patcher continues, I have just stopped adding Nexus 7 specific features as this device's users didn't express any interest.
If I could close the thread, I would. But if something tickles your fancy, come see us at the above link.
The Auto-Patcher 2.4.7 (Bismuth)
by pastime1971 and mateorod.Trouble with Android 4.2? See here.
Current version and changes: Auto-Patcher 2.4.7 is out
Improvements include:
Pdroid for CM7, after a long battle, should finally be working
Internal script improvements.
Pdroid and Pdroid2.0 are incompatible and cannot be applied to the same rom!. If you are switching from one Pdroid to another, go to data/system and delete everything with privacy in the name.
The Auto-Patcher
The Auto-Patcher is a smali patching utilty that can be used to port mods, framework changes, themes and more across ROMs and devices by patching files and outputting a flashable zip.
We hope that this tool can help developers get their work to a wider audience and help users easily try programs that may call for skills or time they don't have. In one command, you can have all the power and utility of the mods/programs listed below, with no specialized knowledge.
Supports
ClockworkMod and Aroma installers
Cyanogen [CM7, CM9, CM10] (cm)
AOKP (aokp)
AOSP (aosp)
ParanoidAndroid (pa)
Evervolv (aosp)
...and many others.
We do not support system.img, Odexed roms or Sense, TouchWiz or other OEM-skinned AOSP at this time.
If you have a build environment and build for TW or Sense, consider joining the team. Additionally, Quarx's CyanogenMod roms are not currently supported. A maintainer would be welcomed for that as well.
Supported PlatformsThe Auto-Patcher runs on Linux and MacOSX terminals. Project contributors kobik77 and wbedard have helped us add Windows support as well.
Kobik77 has developed a stand-alone GUI for Windows called ApG. The most current version of ApG can be downloaded here. Note: ApG has some trouble with some virus software. It has no elevated permissions and is demonstrably safe. Here are some anti-virus tips from long-time user Grayfoxmg1
The Available Mods
Unless there are hardcoded reasons they conflict, all of the mods below can be combined, so you could get all of the programs and tweaks in one shot. If you use other premade patches or zips, you would have to choose between them.
The Auto-Patcher is the only non-destructive way to get these enhancements, short of building your own ROM and/or applying your own changes to the code.
The name is paranthesis is the MODS for use on the command-line. See usage below if that confuses you. It isn't hard, really.
PDroid (pdroid):
The one where we make our bones, PDroid is an advanced privacy app, one that allows you to deny system and user apps permissions they usually need to function. PDroid changes the information passed by permission requests instead of denying it like other apps. That means no FC's or misbehaving apps. PDroid allows you to set custom phone numbers or IMEIs as well. PDroid is only officially supported through GB. The Auto-Patcher makes it an option for ICS and Jellybean ROMs as well.
PDroid is available in the Google Play Store, although you may have trouble installing it from there. It is available from its release thread by svyat, PDroid's sole developer. Discussion about PDroid efficacy and operation for ICS/JB is usually best at pastime1971's port/build patch thread.
PDroid 2.0 (pd2.0): NEW!
CollegeDev's update of the core PDroid app and framework. There is a separate app you will need as well. You can get the app and read about PDroid2.0 and get the .apk here. This mod is only for Android 4.1.2+
V6 Supercharger (v6supercharger):
Most likely needs no introduction to any regular XDA member. The Auto-Patcher will edit your services.jar for you. Our patches contain zeppelinrox's most recent edits. You will still need the script, which you can get at his OP. Only for Android 4.0.0+!
Insecure Boot.img (insecure):
This should work for just about every ROM, giving you true root shell access, enabling adb push of system files and adb remount commands. It can truly save your bacon if you are the type to play with system files and flashing. Some ROMs come with this feature already, so if this patch fails, it just means you already have one.
Secure boot.img (secure):
The opposite of the above. There are advantages to both, and what you want depends on what you do. I haven't seen any other way to secure a boot.img, with so many roms now having insecure by default.
Swap internal and external storage (external_internal):NEW!
This swaps your app storage from an sdcard to internal storage. This allows you to use all apps, even w/o an sdcard!
TabletUI (tabletUI):
Based on findings by barmullio, this allows users of the "Phablets" UI to switch from the stock phone or phablet layout to Tablet user interface. I personally like the tab interface because it allows me more regular access to the status bar. Lockscreen rotation has been enabled as well. Confirmed working on all devices!.
NEW
Mods for Wifi-only Tablets.
3G Dongle (3gdongle):
This allows users of Wifi tabs to use their 3G dongles on their tablets, allowing them to have data on the go. This is a pretty involved mod, and the development is still on-going. We would like to stress that you read up at developer trevd's thread for best practices and troubleshooting. A growing list of confirmed supported dongles can be found there as well.
Google Voice (voice):
As popularized by bongostl, this allows users to use Google Voice to make outgoing calls. It changes your framework-res to recognize that the tablet is voice capable. This allows you to recieve calls as well and has other call quality advantages over things like GrooveIP.
OTG support- Coming SOON.
Usage
Designed to run on Linux, OSX and Windows (using Cygwin)
The Auto-Patcher has become completely open-source, and no one has gotten more out of that than our Windows users. kobik77 and wbedard have come aboard and brought Windows support to our formerly *nix-only utility.
Kobik has also crafted the first Auto-Patcher GUI! Here is his post with download link and features description (including auto-update from Github!)
Requirements for execution: Java (JDK), cpio, patch
Help
For usage and patch availability, place a rom.zip into this directory and try
Code:
$./auto_patcher <ROMNAME>.zip -h
This will check our various dependancies and provide some useful information. It is not the prettiest thing in the world yet, we're working on it...
To patch a ROM
Code:
./auto_patcher <[FONT="Courier New"]ROMNAME[/FONT]>.zip <[FONT="Courier New"]MODS[/FONT]>
example:
Code:
./auto_patcher cm10-encore-fat-tire.zip pdroid,tabletUI
You can have any number of mods applied at the same time, just separate them with a comma and NO SPACES!
The only thing you may need will be a romtype. The patcher will detect and display the ROMTYPE it thinks you have. If the patches fail, just append your ROMTYPE to the end of the command. The only available ROM types are:
pa
cm
aosp
aokp
Don't worry if your rom doesn't have a type; most roms in XDA are derivatives of one of the above, and tell you which one in their release threads.
Code:
./auto_patcher pa-2.23-mateorod.zip pdroid pa
98% of the time, that is all you need to know!
If you would like to see some of our more advanced usage, please see the third post.
Debugging
There is never any need for any wiping or restoring of a backup! If you encounter any problems, simply reflash the generated restore.zip or your ROM over the install, preserving all data and settings!
In the Auto-Patcher directory you will see a logfile that is generated with each run of the program. Please attach the entire logfile in order to get the best support we can offer.
Current and past versions available at our download page on techerrata
Download
You can also clone from our github. See the README because there is actualy a lot extra there.
Contributors
pastime1971
mateorod
kobik77 (ApG developer/cygwin maintainer)
wbedard (cygwin/AOSP pd2.0 maintainer)
Maintainers
FFU5y (Maintains pd2.0 AOKP)
KickNGuitar (OSX testing)
poncik (Evervolv maintainer)
Thanks
eyeballer and kevank with Team Win for web hosting
Svyat
CollegeDev
tonyp
krylon360
inportb
chainfire (for faapt)
zeppelinrox
trevd
rathian, and TheMatrix2000 (for OSX testing)
romracer and greenblue for 4.1.2 fixes
ninno_mx
The Auto-Patcher is a fully open-source utility, and we welcome new contributors.
If you are a developer, themer or script writer who has code-level edits you walk your users through, let us know and we can get together and create a package for you. A message to developers is here, which also touches on our donation policy.
changelog
12.05.00. (v0.1)
# ...........
# 2012.05.12. (v0.2) allows user to specify a different version of patches
# 2012.05.13. (v0.3.0) force "patch -N", remove temp upon failure, generate log output
# 2012.05.13. (v0.3.1) revised the generation of updater-script (SGS2)
# 2012.05.15. added AOSP patches
# 2012.05.15. added crespo-aosp patches, added device-specific patching if patch exists
# 2012.05.15. remove restore.zip upon failure
# 2012.05.15. (v0.4.1) added CM7 (GB) patches
# 2012.05.18. (v0.4.2) added checking for tool commands
# 2012.05.21. (v0.4.3) apply device-specific patche only when it is specified
# 2012.05.26. added task title to log
# 2012.05.31. (v0.4.4) CM9 patches updated, crespo-aosp added
# 2012.06.04. (v0.4.5) added checking tools and rom, added aroma installer support, add patch outputs reroute
# 2012.06.15. CM9 patches updated
# 2012.06.16. (v0.4.6) AOKP patches updated, patch versions restructured
# 2012.06.17. (v0.5.0) patcher script reorganized, removed build.prop
# 2012.06.17. (v0.6.0) auto patcher script for pdroid and v6 patches
# 2012.06.19. (v0.6.1) add patches for CM7.2 Final
# 2012.06.20. (v0.6.2) updated CM 7.2 patches
# 2012.06.23. (v0.6.3) fix symlinks
# 2012.06.26. (v0.6.4) add CM7 nightly patches (0618 or latest). Removed faulty 7.2 patches (0619)
# 2012.06.27. (v0.6.5) added new CM9 patches (20120626)
# 2012.06.27. (v0.6.6) added CM7 nightly patches (20120625) (finally!)
# 2012.07.02. (v0.7.0) Redid AOSP/AOKP; add Windows support (using Cygwin). Thanks kobik77!
# 2012.07.06. (v0.7.1) updated CM9 patches (20120706)
# 2012.07.08. (v0.7.2) updated AOKP (20120707) and CM9 (20120708) pdroid patches
# 2012.07.11. (v1.0.0) reworked script works on Linux, Mac OSX, and Windows (on Cygwin);
# " " added new ICS/JellyBean support for the new V6-Supercharger
# 2012.07.18. (v1.0.1) updated pdroid patches for CM7/CM9 (20120718)
# 2012.08.06 (v1.5.0) updated smali/baksmali binaries to 1.33
# 2012.08.06 Added Pdroid/V6supercharger support for CM10 Jellybean!
# 2012.08.06. (v1.6.0) added aokp-jb patches for pdroid/v6supercharger, script update
# 2012.08.17. (v1.9.5) Added support for pdroid_addon, by CollegeDev.
# Added insecure boot.img mod
# Added support for aosp-jb (This needs testing, and may not be a wide patch due to large variation between AOSP roms.)
# -Please report all experiences!
# Updated all v6supercharger patches w/new edits to ProcessList
# Major script overhaul in preparation for additional mods!
# 2012.08.20. (1.9.6) Conditional support for Official cm10 and aokp-jb builds
# 2012.08.23. (1.9.7) Final/confirmed pdroid support for Official CM10 and AOKP-JB
# 2012.09.04 (1.9.8) Bundled cygwin-compatible tools (original was corrupt).
# For Cygwin, replaced h2b function with simple bash math
# conversion (req'd for compat w/ Cygwin tools).
# 2012.08.26. (2.0.0) Added .apk patching
# Added 3G Dongle support for Nexus 7
# TabletUI support for Nexus 7 (maybe more)
# Google Voice support for Nexus 7
# mods are 3gdongle, tabletUI, voice, or Nexus7 (for all)
# Added provisional file copy menu to widen patching base
# 2012.09.11. (2.0.1) Cygwin support fixes
# 2012.09.11. (2.0.2) Bugfix for 3gdongle (all)
# 2012.09.16. (2.1.0) Significant restructuring of core operations; added edit text file
# Fix for "method-cap" errors in pdroid.
reserved
Nice to see you and pastimes and your work here as well - and I absolutely love the new Nexus 7 additions as i finally got mine as well
Btw: Are there any news on decompiling the jars and applying these fixes on an android device, without having to use the PC?
It's not important, I'm just interested.
I will try this patcher for getting 3g dongle (ZTE K3565-Z) support.
My config is ParanoidAndroid with franco kernel.
What is my first step?
How do I get my whole rom with kernel into my mac os system? Can I take the nandroid (I dont think so, because I cannot flash zip back again)?
Cetin said:
I will try this patcher for getting 3g dongle (ZTE K3565-Z) support.
My config is ParanoidAndroid with franco kernel.
What is my first step?
How do I get my whole rom with kernel into my mac os system? Can I take the nandroid (I dont think so, because I cannot flash zip back again)?
Click to expand...
Click to collapse
Well, that is interesting, actually. There are a bunch of ways that you could get the update.zip on your tablet, but there isn't support for custom kernels yet. You can patch any rom, but if the patch needs to change the boot.img, flashing a new kernel will remove that part of the patch.
I think I know a way to add it though. I will try to add custom kernel integration to the next update.
But you CAN get the 3gdongle working on your rom, just put it through the patcher and transfer it through adb or email or dropbox.
Code:
./auto_patcher paranoidandroid2.2.1.zip 3gdongle
replacing paranoidandroid2.2.1 with the actual name of the zip.
The stock kernel is pretty awesome, bttw. But I think I can add this to the autopatcher. It is needed anyway.
Edit: I must be really tired. You can do this. The kernels are distributed as boot.imgs. Just open up the kernel installer zip, take out the boot.img. Then replace the boot.img in whatever rom you are using.
Then run it through the Auto-Patcher, using any options you like.
You will ONLY need to replace the boot.img of your rom if you are applying the 3gdongle, insecure,secure, or pdroid-aosp-jb modtypes and would like to use a custom kernel that doesn't come bundled with your rom.
I will add some version of this to the autopatcher's next update though, so it is easy to do from the command-line/GUI.
Cetin said:
I will try this patcher for getting 3g dongle (ZTE K3565-Z) support.
My config is ParanoidAndroid with franco kernel.
What is my first step?
How do I get my whole rom with kernel into my mac os system? Can I take the nandroid (I dont think so, because I cannot flash zip back again)?
Click to expand...
Click to collapse
If you need more info than that, you can ask and I will be more specific, I just reread your post and realized maybe I wasn't thorough enough...
Update Because this seemed so vital to the Nexus 7 community (because we have everyone and their mother with a custom kernel here...) I went and looked through the installers.
It looks most people: faux,_motley, clemsyn et.al. use the AnyKernel updater. Those updaters use some of the same binaries we do to preserve ramdisk edits. They don't want to overwrite mods of this sort any more than we want them to.
A couple devs, franco and some new one from today, Thoravuuk or somethin', just package a boot.img. In those cases you will need to place the custom boot.img (and title it boot.img) in the ROM you would like to patch with the Auto-Patcher.
In all cases, there is existing methods to preserve all support and features with nothing more than winzip or any other archive manager. Drag and drop.
So we will see how we end up handling this in the Auto-Patcher in the future. There are a bunch of methods to distributing kernels which make it tricky, but the more responsible Android devs already are prepared for the fact that you may have modified your ramdisk and want to keep it that way. Using Koush's AnyKernel is a great way to accomplish that.
For franco you will habe to briefly drag and drop for now.
tonyp said:
reserved
Click to expand...
Click to collapse
Just saw this part, tonyp. I hope this means you might have something planned for us...
Hey man, thanks for your big support!
I will try like you said.
As I understand correctly the boot.img keeps untouched by your patch. So I can patch my Rom flash the zip and use any custom kernel by flashing it with fastboot flash boot command?!
NEXUS 7
I tried patching but there´s is a problem:
How to choose the right file and which one is it?
Code:
### applying boot.img patch ###
... applying init.dongle.rc patch ...
... applying init.rc patch ...
The text leading up to this was:
--------------------------
|diff -Npru ramdisk/init.rc 3g-ramdisk/init.rc
|--- ramdisk/init.rc 2012-08-27 00:25:58.749201521 -0500
|+++ 3g-ramdisk/init.rc 2012-08-27 00:24:51.012865613 -0500
--------------------------
File to patch: 3g-ramdisk
3g-ramdisk: No such file or directory
Skip this patch? [y] n
File to patch: 3g-ramdisk/init.rc
3g-ramdisk/init.rc: No such file or directory
Skip this patch? [y] n
File to patch: init.dongle.rc
1 out of 1 hunk FAILED -- saving rejects to file init.dongle.rc.rej
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed patching init.rc
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Cetin said:
I tried patching but there´s is a problem:
How to choose the right file and which one is it?
Click to expand...
Click to collapse
You're using a Mac correct? That is probably the least tested upon platform, although it should be fine. In your autopatcher folder, there is a logfile. Would you attach it please? I can know a bunch more with that file.
Thanks for reporting back.!
tonyp said:
Btw: Are there any news on decompiling the jars and applying these fixes on an android device, without having to use the PC?
It's not important, I'm just interested.
Click to expand...
Click to collapse
Oh yeah, once 2.0 gets stable (and I solve this new pdroid problem, that is soooo irritating. I predicted this was coming waay back in pastime's port thread, when we first ran into trouble with the build patches) that is the next thing I am going to work on.
I think pastime is going to lead the charge getting a linux GUI and I am going to work on getting the Android front-end. That is going to be wild, most people have just accepted it can't be done.
noob here! i just want to apply 3g dongle patch on my nexus 7 stock rom (rooted ofcourse) help please
thanks
rufh_s said:
noob here! i just want to apply 3g dongle patch on my nexus 7 stock rom (rooted ofcourse) help please
thanks
Click to expand...
Click to collapse
Well, we don;t support system.img modding here yet, mostly because it is so device specific. This tool works on all roms and devices, so adding something for each device would be a real pain. I am going to keep looking at perhaps adding the Nexus 7 system.img, though.
What you can do is look for a deodexed stock rom in the rom page. There are several available, I believe scrosler has one, and maybe a couple more. These are basically stock roms, but with deodexing and unpacking of the system.img already done.
The main advantage to using custom roms is their customizability, (if that is even a word...). All the other stuff is a result of that.
If you want the 3gdongle support, you will probably have to try one of the flashable stock roms.
Very useful mod. Thanks for bringing this here.
Quick question to clear up something:
The tablet mode or 3g dongle, can I just flash them through twrp and be done? Or does the untethered way need your manual method you described above for untethered installation?
I'm running stock rom with trinity kernel(anykernel i believe) BTW. I alternate between motleys and trinity. Sometimes Faux one also.
Edit: I see the above post basically answers my question. Won't work on stock rom. Needs a deodexed stock base rom. Will wait till you hopefully add img. Support. My nexus 7 runs great on stock rom with custom kernel. Waiting for custom roms to mature more before I go flashing.
mateorod said:
Well, we don;t support system.img modding here yet, mostly because it is so device specific. This tool works on all roms and devices, so adding something for each device would be a real pain. I am going to keep looking at perhaps adding the Nexus 7 system.img, though.
What you can do is look for a deodexed stock rom in the rom page. There are several available, I believe scrosler has one, and maybe a couple more. These are basically stock roms, but with deodexing and unpacking of the system.img already done.
The main advantage to using custom roms is their customizability, (if that is even a word...). All the other stuff is a result of that.
If you want the 3gdongle support, you will probably have to try one of the flashable stock roms.
Click to expand...
Click to collapse
Well I have downloaded the rom deodex by scrosler,but I am getting the error,have attached log cat.text
Thanks
rufh_s said:
Well I have downloaded the rom deodex by scrosler,but I am getting the error,have attached log cat.text
Thanks
Click to expand...
Click to collapse
I should make a note of this in the top post, the only way to combine the 3gdongle and the Voice hack is to substitute the list of all the mods separately with
Code:
Nexus7
The voice and 3gdongle have separate edits to the bools.xml that are right next to each other. So applying one makes it so the next patch cannot find its context.
I made the Nexus7 patches by hand, so you get all three mods that way. The good news is that going by your log, that's the only problem. So you are basically done!
Edit: And as for the above stock system.img issue, well I may try and add system.img support. But it is a huge pain in the butt, requiring all sorts of manufacturer-specific stuff. I also like stock, though, and alternate between that and straight CM10. But I deodexed the stock.img as well, strictly to make use of all of the cool development that goes down around here.
You can manually deodex, then redex and all that, but I didn't really see a performance drop personally. I am pretty sure all the kernels you listed use koush's anykernel method, which is compatible with the Auto-Patcher and its methods.
mateorod said:
I should make a note of this in the top post, the only way to combine the 3gdongle and the Voice hack is to substitute the list of all the mods separately with
Code:
Nexus7
The voice and 3gdongle have separate edits to the bools.xml that are right next to each other. So applying one makes it so the next patch cannot find its context.
I made the Nexus7 patches by hand, so you get all three mods that way. The good news is that going by your log, that's the only problem. So you are basically done!
Edit: And as for the above stock system.img issue, well I may try and add system.img support. But it is a huge pain in the butt, requiring all sorts of manufacturer-specific stuff. I also like stock, though, and alternate between that and straight CM10. But I deodexed the stock.img as well, strictly to make use of all of the cool development that goes down around here.
You can manually deodex, then redex and all that, but I didn't really see a performance drop personally. I am pretty sure all the kernels you listed use koush's anykernel method, which is compatible with the Auto-Patcher and its methods.
Click to expand...
Click to collapse
Alright I am off to sleep now... will just patch 3g dongles and see...
Well I got to know this is not just n7 specific in your earlier post itself
This is for all devices that's really great,also I just got my n7 so wanted to be stock as much I can,yep I also prefer it..
Let's see, I ll keep you posted
Thanks again for the great work, will also test it on my phone if it works (droid 3) it would give me lot choices to use my data plan
and yeah I also see otg coming soon,all the best for the concept its perfect for noobs like me
Sent from my Nexus 7 using xda app-developers app
apparantly patching only "3gdongles" patch didn't worked either attached log, may be i ll try this with some rom or try to find some other "stock" similar, can you suggest some?
thanks
rufh_s said:
apparantly patching only "3gdongles" patch didn't worked either attached log, may be i ll try this with some rom or try to find some other "stock" similar, can you suggest some?
thanks
Click to expand...
Click to collapse
Okay, this isn't the fault of your rom. Your log shows that it is failing rebuilding your ramdisk. A user reported a corrupted .exe binary, but when I tried to investigate further I haven't heard back.
But since everything else appears to be working for you that may indeed be the case. Give me a minute to look and then I will put out a hotfix.
This will only affect WIndows users who are patching 3gdongle, insecire/secure and aosp-pdroid. I happen to know for a fact that the program runs fine on Cygwin, so I will checkout some new binaries and you should be okay.
Update: We have fixed the final issues with Cygwin and those selct mods. Thanks for your report, 1000+ downloads of 2.0 in the 24 hours or so and you were the one that aimed me towards the fix.
Thanks! Should be up later tonight, after I put my son to bed.
Okay, update is ftp'ing its way up to techerrata as we speak. Maybe 20 mins or so.
I went and got my hands on a Cygwin terminal, and as far a I can tell, everything works as it should. We were having a hell of a time with the binaries, they just seemed to check out fine right up until we uploaded the package and then they crapped out on us.
But the new update has all working pieces. If you were using cygwin and had an issue, give it another shot. Writing a program to run on all three major platforms has been a major learning experience for me, let me tell you.
I am probably going to add the 720p video shooting next update, so if there is anything else you know and want, let me know. It doesn't have to be limited to this forum, there isn't much we can't tackle at this point.
Oh, and we strengthened the voice and 3gdongle patches, now you should be able to apply them both anyway you want, including the Nexus7 command.
Related
The first thing I want to say is that my English is not really good. I hope you understand my questions.
I have an idea for a new Android rom, but I'm faced with a dilemma. I want to have as much as possible supported devices, so I also can just build a launcher apk which can be installed through Google Play. In this way all mobile devices with the minimal platform version can use it. The biggest problem is that I don't only want a replacement for the application launcher but also the notification drawer and everything else. Is it possible to replace them also? I don't think so, so I think I'll work on a custom rom.
The next problem is which base rom I would use if I really build a custom rom. It's most likely to use AOSP as base because it's clean. The question is which version of AOSP: Gingerbread, Ice Cream Sandwich, or the newest version Jelly Bean. You would probably say Jelly Bean because this is the newest version. The problem is the phone support. Gingerbread is supported on most phones. If I build ICS or JB the phones which are supported by Cyanogenmod are easy to support, because I can use their device files. The only problem is that my phone, the Samsung Galaxy Gio is not officially supported and the unofficial port is not really stable. I don't think it's a big problem to use this device files and just wait till the developer makes it more stable, but I don't know for sure.
The last thing I want to know is if it's really that simple to support multiple devices. If I read tutorials about porting existing roms to your device they all say you just have to add your device files to the source and compile it. But they never say something about the kernel. Most devices need another kernel because their hardware is different isn't it? Please explain me how this works.
I'm sorry about this hazy story, but please help me before I make wrong choices. Thanks on purpose.
Wietse
WietsedeVries said:
The biggest problem is that I don't only want a replacement for the application launcher but also the notification drawer and everything else. Is it possible to replace them also? I don't think so, so I think I'll work on a custom rom.
Click to expand...
Click to collapse
These changes you are talking about can be done. They are system changes so not supported by the android app installer.
Eg: Your notification drawer, status bar are part of SystemUI.apk. The source for this is can be found in the AOSP source code under android/frameworks/base/...
You can make your modifications, compile it into an apk and then make a flashable zip to replace the current one (or push it via a rooted adb console).
or you can compile the entire source code into a flashable zip (eg CM7,9 etc..) and use it a replacement ROM with your modifications.
This is the line between an application under the android runtime and the android runtime itself.
these files, under framework are part of the OS. so to provide a customized version of the operating itself is what people like to call ROMs.
Now ROMs (like any OS) are device dependant. Windows has the code to run in a lot of different hardware configs, but android aims to be small. It should have only the minimum required code to efficiently run itself on a device.
Thats the kernel. The kernel communicates with the hardware and so the rest of the hardware can happily talk to a working kernel and expect the hardware to function as advertised. Kernel is a simple program which goes into the RAM on system start and sits there directing the operation of the phone.
Kernel devs work on making sure the hardware and the android runtime work perfectly together. Now, in this imperfect world, not all sources are open, even though they should be. and therein the issue lies.
If you want to compile android from source and make sure it works on your phone, first you need to make sure you have the kernel with all the changes(patches) to it made by the vendor (chap who made the phone and bullied you into buying it) to get it working on your hardware.
If you dont have that, you have to do it yourself. Or wait for someone else to do it.
once you can compile android and get it working on your phone with all the itty bitty hardware working A-OK.. then you can browse through the source, make changes as per your individual requirements and compile it into a ROM.
see the changes to the OS are separate from the changes to the kernel. The kernel changes are for hardware-software interaction so they are phone SPECIFIC.
but changes to your custom android OS (ROM) can be "cherry-picked" from other ROM/gerrit/AOSP/CM/AOKP sources and put inside your own source tree to get included in your build.
so if you have all the device / kernel stuff from a working android distribution, you can take the source of another android distribution and swap the device stuff into it and see if it works.
hope this helps.
wingie6200 said:
These changes you are talking about can be done. They are system changes so not supported by the android app installer.
Eg: Your notification drawer, status bar are part of SystemUI.apk. The source for this is can be found in the AOSP source code under android/frameworks/base/...
You can make your modifications, compile it into an apk and then make a flashable zip to replace the current one (or push it via a rooted adb console).
or you can compile the entire source code into a flashable zip (eg CM7,9 etc..) and use it a replacement ROM with your modifications.
This is the line between an application under the android runtime and the android runtime itself.
these files, under framework are part of the OS. so to provide a customized version of the operating itself is what people like to call ROMs.
Now ROMs (like any OS) are device dependant. Windows has the code to run in a lot of different hardware configs, but android aims to be small. It should have only the minimum required code to efficiently run itself on a device.
Thats the kernel. The kernel communicates with the hardware and so the rest of the hardware can happily talk to a working kernel and expect the hardware to function as advertised. Kernel is a simple program which goes into the RAM on system start and sits there directing the operation of the phone.
Kernel devs work on making sure the hardware and the android runtime work perfectly together. Now, in this imperfect world, not all sources are open, even though they should be. and therein the issue lies.
If you want to compile android from source and make sure it works on your phone, first you need to make sure you have the kernel with all the changes(patches) to it made by the vendor (chap who made the phone and bullied you into buying it) to get it working on your hardware.
If you dont have that, you have to do it yourself. Or wait for someone else to do it.
once you can compile android and get it working on your phone with all the itty bitty hardware working A-OK.. then you can browse through the source, make changes as per your individual requirements and compile it into a ROM.
see the changes to the OS are separate from the changes to the kernel. The kernel changes are for hardware-software interaction so they are phone SPECIFIC.
but changes to your custom android OS (ROM) can be "cherry-picked" from other ROM/gerrit/AOSP/CM/AOKP sources and put inside your own source tree to get included in your build.
so if you have all the device / kernel stuff from a working android distribution, you can take the source of another android distribution and swap the device stuff into it and see if it works.
hope this helps.
Click to expand...
Click to collapse
Thank you very very much for your explanation! It's a pity it's impossible to hit multiple times "Thanks".
I think I'm going to make a modified SystemUI.apk but you didn't tell the application launcher is also in this file. Did you just forget this or is this stored in another file/folder? And the lock screen? And I want also to replace the boot animation if it's possible.
If I take the source files of the SystemUI.apk of AOSP ICS, does this work on every phone running ICS? Included CM, AOKP and other (smaller) custom roms? And my last question: Since SystemUI.apk a apk file is, is it possible to edit these files through Eclipse and build it in Eclipse? Or do I get errors?
//Edit:
Still another question: How much work is it to, as example, port a modified Gingerbread SystemUI.apk to ICS? (Or vice versa)
WietsedeVries said:
Thank you very very much for your explanation! It's a pity it's impossible to hit multiple times "Thanks".
I think I'm going to make a modified SystemUI.apk but you didn't tell the application launcher is also in this file. Did you just forget this or is this stored in another file/folder? And the lock screen? And I want also to replace the boot animation if it's possible.
If I take the source files of the SystemUI.apk of AOSP ICS, does this work on every phone running ICS? Included CM, AOKP and other (smaller) custom roms? And my last question: Since SystemUI.apk a apk file is, is it possible to edit these files through Eclipse and build it in Eclipse? Or do I get errors?
//Edit:
Still another question: How much work is it to, as example, port a modified Gingerbread SystemUI.apk to ICS? (Or vice versa)
Click to expand...
Click to collapse
Only way is through exchanging the png files since porting the whole .apk is impossible.
Sent from my Jelly Beaned Ace
Thanks for the answer. And do you also know the answers of the other questions?
Sent from my GT-S5660 using xda app-developers app
WietsedeVries said:
If I take the source files of the SystemUI.apk of AOSP ICS, does this work on every phone running ICS? Included CM, AOKP and other (smaller) custom roms? And my last question: Since SystemUI.apk a apk file is, is it possible to edit these files through Eclipse and build it in Eclipse? Or do I get errors?
//Edit:
Still another question: How much work is it to, as example, port a modified Gingerbread SystemUI.apk to ICS? (Or vice versa)
Click to expand...
Click to collapse
There are two roads you can go now - one is use apktool to *decompile* apk the apk file that you've taken from your phone, it doesnt convert the app to java source code but java bytecode in .smali files (like an assembly version of the source) but you will have access to the resource files (xml, images etc..) so you can replace them and create some new themes.
http://forum.xda-developers.com/showthread.php?t=1814441
http://forum.xda-developers.com/showthread.php?t=1760133
And no - a GB systemUI.apk will *NOT* work on ICS. It is very probable that any changes you make through any of these methods can brick you phone. So make sure you have CWM and a nandroid backup.
If you want to add/edit functionality within the source code of systemUI.apk, you need to learn how to compile Android from Source. i would suggest getting hold of the CyanogenMod source tree for your device and playing around with it.
Ginger bread is CM7 and ICS is CM9.
http://forum.xda-developers.com/showthread.php?t=1552090
once you have the full source tree, you'll find a folder called android/frameworks/base/core/...something../systemui/..
this will contain the javasource code for your application. Here you can edit stuff to your hearts content!
Note that this cannot be compiled standalone by eclipse. The Android build system must be used to compile this (cuz its a system app).
a nice resource i used when i was doing the same thing :laugh:
http://iserveandroid.blogspot.in/2011/01/how-to-implement-your-own-status-bar.html
cheers and have fun.
Guardian Rom by x942Thanks to:
The Guardian Project
Cyanogen Mod
Android
Open-Pdroid Project
Any one else I am missing
Click to expand...
Click to collapse
What is Guardian Rom?
Guardian ROM is a custom android ROM multiple devices. The ROM is completely Open Source and based off of the CM10.1. While this build is stable because it's based on CM10.1 it is a preview so please expect some bugs, & missing features (i.e updater).
What Features does Guardian Rom have?
Kernel is hardened with SecDroid Tweaks.
ROM is patched with and includes OpenPdoird for
permissions management.
Guardian Project apps are pre-installed – These include Orbot (Tor), Gibberbot (Secure IM),
and more.
CSSimple and OStel (https://guardianproject.info/wiki/Ostel) are included as replacements to the
built calling apps. providing encrypted communications.
If encryption is enabled and password is entered wrong 10 times the phone wipes user data.
Click to expand...
Click to collapse
Coming Soon:
Including support for Deniable Encryption (similar to Truecrypt hidden volumes).
Including GRSecurity for exploit mitigation and more secure phone.
Including SQLCipher to ensure all data is encrypted whenever possible
Including a customer “app store” for our repos.
Different lockscreen pin and Pre-Boot authentication password.
Auto-Prompt for encryption setup on first boot.
Click to expand...
Click to collapse
How to use:
Simply flash the flashable zip through your favorite custom recovery. (TWRP is recommended as it supports encrypted devices). Once flashed you should enable Full Disk Encryption by doing the following (may very depending on device):
Code:
Settings --> Security ---> Password [enter a strong 8-16 char password]
Than
Code:
Settings --> Security ---> Encryption --> Enable Encryption
Downloads:Downloads are over here.
Please verify the downloaded file with the attached GPG signature to ensure is is a legit copy.
GAPPS
Google Apps are NOT included and before you flash them you may want to read this article.
UPDATES:
Since this is a preview I have not had a chance to remove or modify the CM Updater. Please do NOT use it as you will be flashing a stock CM10.1 build and not Guardian Rom. This will be fixed shortly.
thanks for taking the time to build this! how does your ROM compare with SE for Android [ http://selinuxproject.org/page/SEAndroid ]? it sounds like similar features. ive been planning on doing an htc one android SE build for a long time now but havent had the time or the skill to do so. anyways, i appreciate you building this.
lfwake08 said:
thanks for taking the time to build this! how does your ROM compare with SE for Android [ http://selinuxproject.org/page/SEAndroid ]? it sounds like similar features. ive been planning on doing an htc one android SE build for a long time now but havent had the time or the skill to do so. anyways, i appreciate you building this.
Click to expand...
Click to collapse
The build focuses more on the Encryption side and Exploit mitigation (GRSecurity) side of things. SEAndroid is great for containment of malicious payloads AFTER a successful exploit. We want to prevent the exploit to begin with. GRSecurity isn't included yet due to stability issues but it will be eventually. Since we can use SeLinux as the MAC with GRSec. We may do so. Or we may choose to go with RBAC instead. We haven't got that far just yet.
Another note:
Most of the features work well on AOSP but not on CM. It will take more work to either port these enhancements to CM or port stock AOSP to non-nexus devices such as the HTC One.
Dear All
Ever heard or read of/about PDroid? Ever thought about securing your data, addresses, locations and SIM information from being (mis-) used by downloaded apps, games and other things?
Time to read about...
PDroid is a ROM-hooked privacy protection of your personal information & data. It let's you set per-app access rights to your private informations. No more hidden address ore phone-book misuse or GPS-based advertisement "enhancement".
Read more about PDroid/OpenPDroid: http://forum.xda-developers.com/showthread.php?t=2098156
What is this thread about?
This shall be a pure SERVICE thread to all users and friends of Android that care about their privacy.
We (users & friends of xda-developers, PDroid & AutoPatcher) help you patching your ROM so that you can use your apps and games under privacy protection.
Patching these ROMs provides some hurdles and hooks - some of us are very experienced and built & installed an environment to enable "simple patching". Many users stand back from this effort and have few experience with command-based or GUI-based patching - these are the addressees that we want to enable to have ALSO privacy protection on their tablets and smartphones.
Especially when you're not a very frequent "ROM-hopper"
What IS this service?
You drop us a link & we patch & upload this patch - that's it.
Please grant us some time, the response time depends on the supporters - and they all spend their free time for this.
(Please thank the helpers and providers by hitting the Thanks button!) ... maybe also rating the thread?
How to USE the service?
You install your ROM and post us the download link. You'll get back an upload with the patch. Usually you can simply flash it to your device, you should not have any problem, installing it "over" your installation. Even no data loss.
To set the rights for each app and get a warning if rights are changed, install "PDroid Manager" from App Store and launch it.
Nevertheless - make sure to have a backup
- of your (unpatched) ROM install
- of your data & installation
before your first trial.
Further Information:
OpenPDroid / PDroid information: http://forum.xda-developers.com/showthread.php?t=2098156
PDroid Manager - the access rights managing software: https://play.google.com/store/apps/details?id=net.digitalfeed.pdroidalternative
AutoPatcher - the tool if you also want to start patching...: http://forum.xda-developers.com/showthread.php?t=1719408
We'll elaborate this thread and post more and more and add links and further information - subscribe it to get familiar with PDroid!
One last notice: these patches do NOT induct any backdoor, trojan nor any other virus ar any advertisement to your device - rather enable you to set rights to achieve the opposite.
Special thanks to all contributors here, to the PDroid and OpenPDroid Team and especially to mateorod and his AutoPatcher's team.
With kind regards from Switzerland - Chris
Please thank the helpers and providers of patches by hitting the Thanks button!
How to install / proceed with my patch?
Flashing ROMs or ROM updates is unfortunately quite device-dependent.
Please make sure you have a copy of your flashed (unpatched) ROM to restore
Please make sure you backed up all of your data
A GENERIC guidance could be the following steps: How to update your installation to the PDroid-enabled one:
Download [yourROM] (unpatched version)
Download the attached patch-update from the appropriate post - the answer of one of the "helpers" (hit THANKS! )
Put both on your SD-Card
Enter Recovery of your device
(If not yet installed) Install (ZIP from SD-Card) the full fletched non-patched [yourROM] (usually no need to re-boot after that, simply go on with...)
Make sure you installed the appropriate GApps
Install (ZIP from SD-Card) the patched update from this thread's answer post "over it"
IF you changed a major Android version (e.g. 4.2.2 -> 4.3), perform a full wipe
Reboot the device
Go to Play Store and download "PDroid Manager" and start it to configure your privacy settings per every single App - You're done.
After you set up the permissions, you don't need the Android's (very limited; since 4.2.2) privacy protection anymore - deactivate it
Greetz - Chris
#3 - reserved
Req: Patch for cm-10.2-20130918-NIGHTLY-p3100.zip
EXAMPLE of a Request:
Hi
can you patch CM 10.2. Nightly as per 2013-09-18 for P3100 device for me?
Device details:
Manufacturer: Samsung
Device: GT 2 7.0 P3100
ROM's download link: http://www.get.cm/get/jenkins/41935/cm-10.2-20130918-NIGHTLY-p3100.zip
Christoph21x said:
EXAMPLE of a Request:
Hi
can you patch CM 10.2. Nightly as per 2013-09-18 for P3100 device for me?
Device details:
Manufacturer: Samsung
Device: GT 2 7.0 P3100
ROM's download link: http://www.get.cm/get/jenkins/41935/cm-10.2-20130918-NIGHTLY-p3100.zip
Click to expand...
Click to collapse
EXAMPLE Answer:
Hi pls find attached the patch
Nice idea, hopefully it'll get approved and added to the development threads op.
I might join in by writing a short explanation about VM's and how to use the patcher there (since I was doing it this way until a few weeks back, where I got (nearly) rid of win)
Being on Linux actually makes the whole thing a hell of a lot easier.
Cheers!
Via Tapatalk 4 BETA, that, surprisingly, is free.
Here it is!
IRKONIK said:
Nice idea, hopefully it'll get approved and added to the development threads op.
I might join in by writing a short explanation about VM's and how to use the patcher there (since I was doing it this way until a few weeks back, where I got (nearly) rid of win)
Being on Linux actually makes the whole thing a hell of a lot easier.
Cheers!
Via Tapatalk 4 BETA, that, surprisingly, is free.
Click to expand...
Click to collapse
THANKS, IRKONIK!
You know, PDroid is a great service protecting us, the work of the developers is great - including mateorod and others who're working all day and night, as it seems.
And if we can, we should try to make this protection available also (and especially!?) to all non- or semi-enthousiastic users that do not neededly flash ROMs frequently..
Thanks for your support - highly appreciated!
Greetz - Chris
GT-N7000, Krueger CM10.2
Hi, could you add support for GT-N7000 Krueger CM10.2?
ROM link:
http://forum.xda-developers.com/showthread.php?t=2406975
http://www.unionrom.com/galaxyrom/K...00/Rom/Krueger-10.2-20130918-Build3-n7000.zip
Log:
http://codepad.org/OWlwMBie
Thanks!
ralphm2004 said:
Hi, could you add support for GT-N7000 Krueger CM10.2?
ROM link:
http://forum.xda-developers.com/showthread.php?t=2406975
http://www.unionrom.com/galaxyrom/K...00/Rom/Krueger-10.2-20130918-Build3-n7000.zip
Log:
http://codepad.org/OWlwMBie
Thanks!
Click to expand...
Click to collapse
Hi ralph
You posted in the wrong thread - patch DEVELOPMENT is under http://forum.xda-developers.com/showthread.php?t=1719408 who add support for non-patchable ROMs, we just build it for users...
greetz - Chris
Christoph21x said:
Hi ralph
You posted in the wrong thread - patch DEVELOPMENT is under http://forum.xda-developers.com/showthread.php?t=1719408 who add support for non-patchable ROMs, we just build it for users...
greetz - Chris
Click to expand...
Click to collapse
Hi Chris,
thanks for the information, i misunderstood the sense of this thread.
As a junior member i can't post in development-threads. Can someone please post it there?
I posted a link, so you'll be fine (hopefully)
Cheers!
Via Tapatalk 4 BETA, that, surprisingly, is free.
ralphm2004 said:
Hi, could you add support for GT-N7000 Krueger CM10.2?
ROM link:
http://forum.xda-developers.com/showthread.php?t=2406975
http://www.unionrom.com/galaxyrom/K...00/Rom/Krueger-10.2-20130918-Build3-n7000.zip
Log:
http://codepad.org/OWlwMBie
Thanks!
Click to expand...
Click to collapse
Thanks for the thread, Christophe!
I can add support, but I need the rom's source code. You will have to ask the dev for a link to their github page. But then I can add support.
mateorod said:
Thanks for the thread, Christophe!
I can add support, but I need the rom's source code. You will have to ask the dev for a link to their github page. But then I can add support.
Click to expand...
Click to collapse
hi mateorod,
i cant post to that thread to. there doesn't seem to be a link to the right source.
but with v3.1.78 the patch has worked.
i try to contact bangsti and ask for the source, maybe it is helpful for the future.
ralphm2004
--- edit ---
got the information from bangsti:
Is the CM10.2 Source and crdroid Source.
github.com/cristianomatos
github.com/CyanogenMod
Krueger is a Mix from this Sourcen.
Well, I said it, so here it is (yeah, I deliver )
How to use the Auto-Patcher on Linux (debian based (!!)) in a virtual machine.
This "tutorial" does not take you by your hand. No, I DEMAND :silly: that you do stuff by yourself. It helps you! (Trust me. The easy way is not always the best)
First of all: You need a virtual machine with your favorite distro. (I like Mint Cinnamon)
How this step works? Well, google/youtube it. There is so much info about it, there is no need in writing another tutorial. Especially when other people have done it waaaay better
So, you have linux running. What now?
Second step: Getting all the stuff the patcher relies on.
Code:
sudo apt-get update
Code:
sudo apt-get install git git-core cpio patch unzip tar openjdk-7-jdk openjdk-7-jre
Third step: Getting all the files from github and build the patcher
Code:
git clone https://github.com/mateor/auto-patcher
Code:
cd auto-patcher
Code:
./batch.sh
Fourth step: Copy the rom you want to have patched into the auto-patcher folder.
Code:
./auto_patcher rom.zip
!! With this method, the patcher will use the rom detector and will build OpenPDroid patches. If you DO NOT want them, read the first page of the dev-thread. !!
Fifth step: Getting the files "out of" the VM.
- Easy way: Upload it into the/your cloud.
- Nearly as easy way: Use some filehost. (Since the files are about 6MB big, it's not even a hassle). Fast filehost: zippyshare
When your files finished the uploading, just use the link to the file in a qr-code generator, scan it with your device and download it. Easy!
Sixth step: BEFORE you flash the file, check the md5sum (in the VM and on your device!) how-to
If they match, you are good to go. Don't forget to make a nandroid backup! It's not needed, but hey, better safe than sorry!
I hope this helps If something is missing, tell me!
Cheers! :highfive:
PS: Due to lack of time, this "tutorial" is as short as possible and might lack a few explanations. (Hopefully not steps)
PPS: The only "tip" I have: use the tab-key for auto-complete So instead of writing "auto-patcher" just type "au" and then press tab. Saves you lots of time.
Edit1: Props to Mateorod and everybody over at the dev thread!
PDroid Patches for Samsung Galaxy Tab, HTC Desire & Desire S
Dear All
please find below some already PDroid-patched ROM links
Samsung Galaxy Tab 2 7.0 P3100, P3110 & P3113 (JB 4.3 Nightly & JB 4.2.2 CM 10.1.3 RELEASE)
[PDROID][GT-P31XX][2013-09-21][JB][4.3/4.2.2]PDroid: CM 10.2 Nightly & CM10.1.3 Rel. - see http://forum.xda-developers.com/showthread.php?t=2357514
HTC Desire
[ROM][Sept03][CM10.1] Chromium ROM | Build 10 | bravo - see http://forum.xda-developers.com/showthread.php?p=45441296#post45441296
[ROM/4.2.2] [June 03 2013] VJ CM10.1 | Jelly Bean 4.2.2 - v6.3 Stock/Sense/Data++ - see http://forum.xda-developers.com/showthread.php?p=43710438#post43710438
HTC Desire S
[ROM][08 AUG 13][4.2.2][UNOFFICIAL] CyanogenMod 10.1 - see http://forum.xda-developers.com/showthread.php?p=45441957#post45441957
With kind regards - Chris
http://pio-masaki.com/?dir=DroidDNA/Carbon
I'm in need of the 2nd from the bottom
9/22 for CDMA.
Awesome
Æaa°\,,/
takota6 said:
http://pio-masaki.com/?dir=DroidDNA/Carbon
I'm in need of the 2nd from the bottom
9/22 for CDMA.
Awesome
Æaa°\,,/
Click to expand...
Click to collapse
Since you did not specify which patch you want, you get OpenPDroid. All zip's are zipped with md5sum-files and the patch log.
Download link
Yeah I know, MEGA is pretty ****ty (down- and upstreams are crap) BUT it's more stable than other services.
Cheers!
PS: Please report back, if it works, and if it does, hit the thanks button, so a) I know and b) the thread doesn't get spammed. If something does not work as expected, please post a logcat in the dev thread, so it can get fixed.
Thank you
Well it didn't work, not with your doing but rather the Dev that built didn't put some vendor tree and so everyone is not able to boot that build.. I'll post back when I'm sure there a good build up.. Thanks
Æaa°\,,/
I'm back.. Heres a stable crAosp/ Cyanogen open pdroid please
http://forum.xda-developers.com/showthread.php?t=2417275
Direct Iink
http://www.mediafire.com/?6hblh4leblfc0lh
Thanks
Æaa°\,,/
Here's your patch takota6
takota6 said:
I'm back.. Heres a stable crAosp/ Cyanogen open pdroid please
http://forum.xda-developers.com/showthread.php?t=2417275
Direct Iink
http://www.mediafire.com/?6hblh4leblfc0lh
Thanks
Æaa°\,,/
Click to expand...
Click to collapse
Hi takota6!
Thanks for this clarification.
Please find attached the update file (patch) you need.
To restore to original (if you want to) you may use the attached "restore" file.
Kind regards from Switzerland - Chris
Okay so,
A there isn't much going on with tab 3 10.1 [p5210-specific] meaning extra-ROMular activity
I'm going to add this thread in the hopes it will spark some further creativity/participation.
As a scolding to the gimme gimme crowd - instead of demanding/expecting, try inquiring/learning/contributing.
This is my current boot/kernel image. Modified as follows;
Contains busybox [x86] in /sbin and set to --install -s /system/xbin via /sbin/antwerp.sh
This is NOT a flashable zip for a reason. dd is an incredibly kick-ass tool provided you respect it's authoritah.
I've been making changes by way of .rc,.prop files to make my experimenting easier, meaning less remount,rw
Read the info in zip for better description. I'm not certain I will actually be able to answer intensive questions.
I wiil do my best. When i succeed with a new test I will post. The ramdisk.gz is included.
Link DevHost - http://d-h.st/users/moonbutt74/?fld_id=37381#files
GT-P5210 stock recovery
Link DevHost - http://d-h.st/SLp
---------------------------
This is a transparented Modification of MultiWindowSidebar_v1.3_060614.apk from Thread by @zst123
Note- this modded apk must be dropped into /system/app perm-644
Thread http://forum.xda-developers.com/showthread.php?t=2729450
Link to modded apk DevHost - http://d-h.st/users/moonbutt74/?fld_id=37382#files
When I have more I will add.
note - i am attempting to sort out issues with cwm as it was abandoned by a very rude person.
as far as i can figure the problems seem to be maybe in init binary which is out of my league BUT,
i did manage to reduce my back up time to about 45 min on a moderately heavy rom by swapping
zImage with stock and striking kernel cmdline. any meaningful help/direction would be of benefit
to everyone.
m
----------------------------------------------------------------------
Update-Succeded building stock kernel
Will be posting useful device info for quick reference as I encounter need for it/them.
---------------------------------------------------------------------
UPDATE jULY 10 2014: this is what i hope to be a mostly correct device tree for
the samsung galaxy tab 3 10.1 GT-P5210 santos10wifi CM11
github - https://github.com/moonbutt74?tab=repositories
Thanks to @Angel_666 for his device tree for santos103g
---------------------------------------------------------------------
Useful Reading;
http://www.linux.org/threads/the-linux-kernel-android.5459/
Kernel Source KK 4.4.2
Kernel Source KK 4..4.2
Kernel source is up GT-P5210_EUR_KK_Opensource.zip
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=gt-p5210
UPDATE jULY 10 2014
hey,
so i've posted what i hope is a mostly correct device tree for samsung galaxy tab 3 10.1 GT-P5210 santos10wifi http://forum.xda-developers.com/showthread.php?t=2787136
as I encounter errors or omissions i wil attempt to resolve them in as timely a fashion as permissible.
any updates will be posted as extract and overwrite .tar.gz or .zip files unless there is a reason to diff/patch something.
either way, the updates if any will be labled clearly and contain readme.
thank you to @Angel_666 for his santos103g device tree which was my guide.
thank you for reading
m
NOTE- conversation/q&a related content have been relocated to split thread in q&a
http://forum.xda-developers.com/showthread.php?t=2812791
as to keep this thread focused. i apologize for any inconvenience and intend no slight
in anyway. thank you for your patience and understanding.
m
On booting Android 4.4
This comes by way of @Angel_666,
To boot Android 4.4
enable selinux in your kernel source - make menuconfig, goto security options, yes @ app-armor, yes @ nsa selinux, and set
Default Security Module to- Unix Discretionary Access Controls
Use modules that accompany this build.
adjust your init.*.rc's in accordance with Android 4.4, and at that basic level, you should be good.
add salt to taste.:good:
Something to play with GT-P5210
okay so here is a moderately succesful build through of cm11
i am just posting it for play value. there is no support or requests being accepted.
issues- no sound, no wifi, no video playback, some games will work - [gltron from fdroid is fun], external storage does not register, no bluetooth, you must move terminal.apk from system to sdcard and install as normal app. get a copy of total commander on your sdcard as well, trust me, much more manageable file manager. To poweroff or reboot you must type in terminal;
poweroff -f
or
reboot -f
make backup first. DUH.
will flash no problems with my philz recovery build.
Do not hassle me because of your user error. [no noobs]
Remember this is just to play with. However, a note to experienced people, if you resolve any of the issues
please share the solution with the community.
devhost link - http://d-h.st/01Q
please do not post questions in this thread. Goto q&a and post in the odds & ends thread there.
http://forum.xda-developers.com/showthread.php?t=2812791
have fun
m
and p5200 no hope ?
5200
khaledreno said:
and p5200 no hope ?
Click to expand...
Click to collapse
hi,
it's a variant so yes, hope, just work. :good:
m
Hey guys, anybody doing anything on this device at all? I would love to pick up development if someone can point me in the right direction as far as device tree and any needed files go, please let me know asap as I'm a decent Dev and just picked this device up
soupysoup said:
Hey guys, anybody doing anything on this device at all? I would love to pick up development if someone can point me in the right direction as far as device tree and any needed files go, please let me know asap as I'm a decent Dev and just picked this device up
Click to expand...
Click to collapse
soupy,
meant in the best way.
dude, search, read, especially the OP for this [my] thread.
c'mon.
m
We are closing this at the OP's request, and may be reopened when ready.
Hey guys, I was recently installing a new ROM and kernel on my Nexus 6 when I happened upon something interesting. Franco makes an AMAZING kernel for Nexus devices, and he has an awesome app called FKUpdater which checks his server for new updates to the kernel, provides the user with the changelog for that update, then allows the user to either a) download the zip file for the kernel, or b) download and auto-flash the kernel zip.
I thought this was especially smart because it works regardless of what ROM you're on, since we all know how difficult it can be to stay up to date on both the ROM and the kernel, not to mention any other mods that we like for your phones (thinking back to the pre-Lollipop mods like Xposed, etc).
So, what if there was a way to make a ROM OTA manager, which could check for new versions of your ROM using something as simple as an RSS feed that developers could reference using the build.prop.
Here's the way I imagine this working:
A ROM developer doesn't want to go through all of the unnecessary hassle and costs associated with implementing the OTA features (it's not as easy as it might sound), so instead the developer simply adds a line to the build.prop:
ro.customROMversion.rss=http://www.example.com/rss
This build.prop line would be universal for all ROMs, with the actual RSS link being associated with each specific ROM (so if a development team builds ROMs for multiple devices, they would have one feed per device).
Then the app would check the build.prop for that line, and regularly check the RSS feed for updates. The RSS feed would have a standardized format. It would include the necessary information for the app to detect a new version (version number, build date, etc) as well as including the changelog for the new version (if the ROM developer includes this).
In reality, this wouldn't be difficult at all, and the best part is that the feature could be added in a heartbeat to practically every ROM out there. The ONLY issue I could see running into would be that the download links for the ROMs would (potentially) need to be direct downloads, with no redirects. I don't know how important that would be to implementation, though.
Does anyone see this as being something particularly difficult to do? I would love to build/release this (I REALLY wish I could contribute more to the Android community at large), but I don't know how to program something like this. If anyone thinks they could do this, I would really love to help put this in motion!