Database Info

Need Some Assistance Editing Roms

I hate to make a thread on this but would like to get started soon with learning how to root roms and add the kernel for multitouch and tethering. This is more for my personal use since I just want a stock rom with all the root benefits like jf use to and theses are the questions I have.
1. Will I have to take the update.zip file and extract everything and modify it then resign and I'm done?
2. I read some info on adding busybox and root which seem easy but when I run the chmod command and such everything will be through adb and the files will be on my pc so do I just make sure its all in the right directory and file path?
3. Where are the wallpapers stored in builds along with animations I will be looking into the framwork/framework-res.apk later but still curious
4. The modified kernel for tethering and multitouch is located where along with the market.db file?
5. What is meta.inf and how easy is it to make the cpu 528mhz standard also not sure what BFS and ASOP are haven't been keeping up.
P.S. I would really appreciate some help on this and I don't mind reading if this information is somewhere else so please provide a link and as always gotta show love to those who started this like JF, Hakuro, Cyanogen, Drizzy, and many more like daproy and kornub did a lot of helping.

I hate to make a thread on this
Click to expand...
Click to collapse
You mean you hate starting threads in the correct place?

Thats a fine line here. Although it is a question, it is specifically a development question. Its not a which rom do i choose?
Although android is "open source" these people dont give a **** about people trying to learn how to develop. They will pull the google line or something.

yeah me 2
Trying 2 learn

Im a noob, so I can only answer two of thosew questions
1. Anytime you modify your update.zip you will have to resign before trying to flash it onyour device.
5b. BFS: Brain **** (simple) Scheduler, something to do with the priority of running proccesses or something http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler. AOSP stands for Android Open Software Project, which i believe is just googles standard rom really (but I may be wrong)
I recommend you try out this rom though, kind of like JF but for Donut http://forum.xda-developers.com/showthread.php?t=538456

Very Sorry, double post

Thanks! I'm actually using that rom and its what has me so interested in this cause I hate having to flash another update.zip to get the full root benefits when JF just made everything available in one nice package but looks like I will just have to go through trial an error unless I get some more feedback cause switching between cyan 4.1.11.1 and JF1..51 is killing me and taking up space on my card.

With my little to no knowledge, replacing the boot.img and some files in system/bin with the ones provided in theofficial expansion pack should give you all that you need. With no extra apps.

yeah me 2
Yeah me too

[Q] Various android-related queries

I have managed to compile (from source) and install CM7.2 on my HTC dream, but my questions below are related to Android:
1. Is there a way to find out which packages (.apk) were installed on my system and if so, how do I do that?
2. Is there a way to find out each package dependencies (I need to figure out this as I am bent on removing the vast amount of guff installed on the phone - I won't need 90% of this stuff)?
3. Similarly to 2 above - is there a way to look at dependencies of a package not yet installed on my system (i.e. the .apk file)?
4. How do I actually remove a package for good from the system?
5. Similarly to 3 above, how do I actually install a package from within the root system - I know I can do this via adb, but is there a way to do this inside the, say, command line terminal?
6. Is there a way to alter (understand remove) certain program permissions which I could see "granted" to a particular program/package? I know there are various ways to look at these, but I wish to remove permissions I am not happy being granted to that particular program/package.
And one last a bit more advanced query: I would like to build a single package from the source tree and then install the resulting .apk file on my system.
Basically, I will try to upgrade a package with a new revision and add a few patches to the package source of my own before compiling it and building it again.
I usually build the whole lot (all packages + the rootfs image itself) with "mke bacon", but if I want to alter the source and build a single package how do I do that?
I am not very familiar with the Android make system, so I don't want to go heads-first into something and make a real mess of it.
Thanks a lot for any assistance given.

Small addition as apparently I cannot post a reply (too few posts) in this thread: http://forum.xda-developers.com/showthread.php?p=9055790#post9055790
Question to ezTerry (if he is reading this!): the advice given in that post above was absolutely splendid! I followed it religiously and it worked an absolute treat!
There is one exception though - I've LOST all of my IMEI, IMEI SV and Baseband information after applying these fixes. As soon as I installed the radio updates and then installed my newly-compiled kernel + CM7.2 (successfully!) I then checked the above fields from Settings and they were all gone!
After a while, the baseband, IMEI and IMEI SV appeared, but the IMEI and IMEI SV stuff have now different values than what I've had previously (I've had T-Mobile IMEI, now it appears that I was "assigned" O2 IMEI & IMEI SV values - very bizarre!).
Is this something I need worry about and (I don't yet have a sim card, but I plan to get one soon after I fix my phone), more importantly, how the hell do these IMEI numbers appeared on my phone - where did they came from?!

josh36 said:
Small addition as apparently I cannot post a reply (too few posts) in this thread: http://forum.xda-developers.com/showthread.php?p=9055790#post9055790
Question to ezTerry (if he is reading this!): the advice given in that post above was absolutely splendid! I followed it religiously and it worked an absolute treat!
There is one exception though - I've LOST all of my IMEI, IMEI SV and Baseband information after applying these fixes. As soon as I installed the radio updates and then installed my newly-compiled kernel + CM7.2 (successfully!) I then checked the above fields from Settings and they were all gone!
After a while, the baseband, IMEI and IMEI SV appeared, but the IMEI and IMEI SV stuff have now different values than what I've had previously (I've had T-Mobile IMEI, now it appears that I was "assigned" O2 IMEI & IMEI SV values - very bizarre!).
Is this something I need worry about and (I don't yet have a sim card, but I plan to get one soon after I fix my phone), more importantly, how the hell do these IMEI numbers appeared on my phone - where did they came from?!
Click to expand...
Click to collapse
Any takers?

@1 Check out the respective directories, i.e. for system apps /system/app
@2 Trial and Error, or someone might have made such a list for your device already
@3 No simple way, you would have to look through the decompiled code i guess
@4 Remove the apk from the folder (for example /system/app) and reboot your device, after wards you might have to clean up some extra folders, i.e. settings of that app. (you can use SD Maid from my signature for that)
@5 Some can just be installed the usual way, by opening it. Some .apk files have to be put in the system folders, afterswards reboot and the app should be "installed". To put those apps there use a rootcapable file explorer of your choice. To edit /system you will need to remount it as it is read only by default, you can do that through command line, but most good file explorers have an option for that.
@6 Yes thats possible, there was an app to do that, just not sure what it was called... It is very likely though, that those apps will not work correctly or just FC.
For the make system, if you just change a package, and build again, it will most likely just rebuild the changed files. I'm not so sure either though... damn make system can be pretty messy... and get upset real fast if you change something ;-).

Dark3n said:
@1 Check out the respective directories, i.e. for system apps /system/app
Click to expand...
Click to collapse
Yep, that indeed helped - I didn't realise that the .apk files are "intact" and do not behave in the "standard" (in Linux terms) way a "package" behaves - the app is "installed" as soon as .apk is placed in /data/app or /system/app. The PacketManager does the rest on reboot.
It also cleans up the mess "automagically" if I delete .apk file and reboot, which is nice.
Dark3n said:
@2 Trial and Error, or someone might have made such a list for your device already
Click to expand...
Click to collapse
Yeah, that's a real bugger - I can't see a way of finding the dependencies, but I haven't looked properly at "pm" (the Package Manager command line tool) - maybe I could use something there.
Dark3n said:
@6 Yes thats possible, there was an app to do that, just not sure what it was called... It is very likely though, that those apps will not work correctly or just FC.
Click to expand...
Click to collapse
A very simple example will issustrate my point - my calendar application is installed and needs some sort of GOOGLE_MAIL and access to the internet permissions, neither of which I am happy to grant, because 1) I won't be using online calendars; and 2) I won't use (google) mail.
The truth is, I deliberately did not install any google apps as I won't be using any of them - ever!
Now, every time I boot up and look at my log files with logcat I see a bunch of error messages that this application (the calendar) needs a bunch of permissions which do not exist (naturally, as I haven't installed a single google app on my phone).
So, I wish to wipe out these permissions from the calendar so that logcat is not filled with junk every time I start my phone.
As I already pointed out above, there are also some installed apps who are listed to "need" permissions I am not happy to grant - like the internet access to calendar for example (there are more apps, but I think you get the point).
Dark3n said:
For the make system, if you just change a package, and build again, it will most likely just rebuild the changed files. I'm not so sure either though... damn make system can be pretty messy... and get upset real fast if you change something ;-).
Click to expand...
Click to collapse
Yeah, that was my plan B - there must be another - easier - way though.
I wish to update a lot of stuff (I will be recompiling/refreshing existing packages as well as adding new things I developed for "standard" Linux), but with this Android make system I am blind - it is very different to what I am used to in the Linux world.
To top it all off, I can't post in any of the devs forums yet as I do not have 10 posts!

Further to my previous post - I just found out a superb article about stripping out Android and removing unnecessary packages from it - http://wiki.cyanogenmod.com/wiki/Barebones
It lists various dependencies and shows what could be deleted and what cannot be - what I wanted really.
My only remaining problem - at least for now - is the making of specific packages without building the whole image.

[Q] How to add menu options UPDATED with new ?

I've been trying to figure out how to get NFC working on the stock ROM for a while now. In no way am I a DEV or experienced with Android coding, but I have learned a few things along the way. I know basic NFC functions are available in certain ROMS, but this is about getting it working on the stock ROM. I am also aware that Google Wallet will not work on these phones without a secure elemint (sp?). But with all of the interest in NFC (even though its uses are limited), I would think alot of people would like to have the option to enable it on the stock ROM.
Here is a few things a have discovered:
These phones already have the Nfc.apk and Nfc.Odex files included. They are very similar to the files on the Korean version of this phone that has working NFC.
The framework-res.apk xml already includes code for NFC operations. I have read where people have said that extra framework is needed, but from what I see (again limited knowledge) it already exists.
I also found (I can't remember where) more code for NFC that includes connection instructions and what it is supposed to do when a NFC signal is detected.
So I am thinking, maybe the only thing we need at this point is to have the option for NFC along with the toggle added to the "Wireless and Network" menu on the phone. Maybe it already exists and just needs to be activated.
Oddly enough, it seems very little information exists about trying to activate NFC on the SkyRocket I727 stock ROM. Alot of the information a got was from the regular Galaxy SII forum and it is obvious that phone isn't coded exactly as ours.
So, can any one tell me in which part of the coding is the "Menu options" enabled for the "Wireless and Network" settings? Maybe I am wrong about all of this, but if anyone knows anything more about it (not just guessing but actually knows something), please post it here so we can get the NFC function working on the stock ROM.
On a seperate note, the same place I found the coding about the NFC operations (like I said, I can't remember where it was but I will try to find it again) I also found additional mentioning of an"FM radio chip"???

OOOOKKKKKKK...can someone atleast point me in the right direction to find this out on my own?

You can edit setting.apk and enable nfc. Or just dload a rom that lets u use nfc.
scott14719 said:
I've been trying to figure out how to get NFC working on the stock ROM for a while now. In no way am I a DEV or experienced with Android coding, but I have learned a few things along the way. I know basic NFC functions are available in certain ROMS, but this is about getting it working on the stock ROM. I am also aware that Google Wallet will not work on these phones without a secure elemint (sp?). But with all of the interest in NFC (even though its uses are limited), I would think alot of people would like to have the option to enable it on the stock ROM.
Click to expand...
Click to collapse

appdroid said:
You can edit setting.apk and enable nfc. Or just dload a rom that lets u use nfc.
Click to expand...
Click to collapse
Thanks for the response, but what do I edit in settings.apk? I have read this more than a couple of times, but no one seems to be able to say what edits to make to the settings.apk. As far as the others ROMS go, I realize NFC works in other ROMS, but I'm trying to find an option to enable it in the Stock ROM. Any info you can provide would be great. Thanks.
Edit...I took a look at the setting.apk XML from a T-mobile phone that has NFC enabled and it seems to be the same as the settings.apk XML from the Skyrocket. This is the confusing part. Everyone seems to think the settings.apk app needs editing, but it is the same as ones in the versions of our phones that have working NFC. As a matter of fact, the NFC.apk apps are the same as well. This is why I am thinking it only needs the option added to the "Wireless an Netwok" menu in order for it to work (which is my original question on how to do so). Things just aren't adding up here?

OK, so I've been looking around some more and I found something interesting.
The T-Mobile (T989) version of the Skyrocket has an extra file located in the settings.apk that the I727 AT&T Skyrocket doesn't appear to have in it's settings.apk.
This file is named "smali". Most of the rest of the settings.apk on both phones appear to be very similar. There are about 9 extra lines of code in the "manifest.xml" in the I727 but they do not appear to be related to Nfc operations at all.
This "smali" file in the settings.apk on the T-mobile phone contains a folder called "com" and the "com" folder contains three more folders called "android", "broadcom", and "samsung". The "broadcom" and "samsung" folders appear to contain information (code) about bluetooth operations. The 'android" folder is the interesting one. It contains a "settings" folder that has many other folders in it. Again, most interesting is a file called "Nfc". It contains 5 smali files that all contain code about Nfc functions. I think this may be the actual file(s) that AT&T had Samsung leave off of this phone (I727) so Nfc is not enabled.
So finally, my new question(s) is..........
Can anyone confirm that the exclusion of the "smali" file in the settings.apk on the Skyrocket is the reason we can not use Nfc?
-and-
Would it be safe or even possible to insert the "smali" file contained in the T-mobile settings.apk into the settings.apk of the AT&T Skyrocket phone and see if it would properly activate Nfc on the AT&T Skyrocket? If so, could this be done on the "stock" AT&T 2.3.6 ROM without being DeOdexed?
I realize this is a lot to ask, but this is the only way we can get NFC working on the stock ROM like it should be in the first place. Maybe one of the Devs that works with the skyrocket can help to answer some of these questions. Thanks to anyone that can help.

This doesn't help u in your finally quest of enabling nfc, but the reason u see the smali folder in the decompiled system.apk for the T-Mobile apk is most likely because it is deodexed, and the apk that u are looking at from your skyrocket is not deodex. If u use apktool or something similar to apktool and decompile a non deodexed apk u will not see any smali file. The smali folder is basically the Java code that is in the system.odex file (layman's terms)
This is why most..or most ever apk edit is don't on an odex apk. Because without it being doedex u would have to edit both the apk and the odex file

To add
If can get your hands on a stock doedex sky rocket rom that's what u would want to use to compair the two with
Sent from my Galaxy Nexus using Tapatalk

runandhide05 said:
To add
If can get your hands on a stock doedex sky rocket rom that's what u would want to use to compair the two with
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I have compared the Stock SkyRocket ROM to both T-Mobiles ROM and the Superstock ROM. The SuperStock ROM is a DeOdexed AT&T version of what I have. The Stock ROM (on my phone) and the SuperStock ROM (DeOdexed) seem to be the same. I have not searched and compared every single file and line of code but the settings.apk and framework.apk and framework-res.apk files seem to be the same? The "smali"file folders that were located on the T-mobile ROM are not on the DeOdexed Stock ROM (atleast not that I have found. Unfortunately I have seem to come to the end of my abilities to do anything else. I just don't have the knowledge to go any further. Hopefully one of the DEVs around here could help out if they get the time. I know the effort would be appriciated, but it is up to them.. Most of them seem to be keeping pretty busy with updating their ROMS.
**edit** Ok, I spoke too soon. I found the "smali" files in the DeOdexed Superstock ROM. They are in the ".jar" files. The framework.jar file has the folder that has info about NFC in it. I just have no idea what to do with it from this point. I still think that everything that is needed for NFC to work is already in the Stock ROM, it just needs menu options to get to it.

[Q] Moving dialer/phone app to stock rom (SOLVED)

I've been trying to take the phone apk and dialer from one rom and move it onto a stock rooted rom. I have accomplished this but when someone calls me the phone won't play a ringtone at all. So I have to run a nandroid restore on it. Can anyone tell me how to do this please? thank you in advance

Re: [Q] Moving dialer/phone app to stock rom
Which rom are you moving it from and to which rom?
sent from outer space.

Truckerglenn said:
Which rom are you moving it from and to which rom?
sent from outer space.
Click to expand...
Click to collapse
I am wanting the dialer and phone apk from the Aeon Rom and put it on my stock rooted rom found in xda-developers website thread here....
http://forum.xda-developers.com/showthread.php?t=1613523
************ OPTION C *************
I997UCLB3-CWM-root-deodex-extras.rar
Features in this version
- Entropy's Daily Driver kernel
- Red CWM recovery
- Rooted
- Deodexed
- Zipaligned
- Busybox
- AT&T and other bloatware removed
- Scrolling wallpaper fix
- CRT off animation
- 8 lock screens
- Extended power menu
- Accurate battery mod
- Get lidroid's 14 statusbar toggles HERE
Thank your for your time, effort and help in advance,
(Sorry for the edit) It might help and then again it may not. But I am using an AT&T Samsung Infuse 4g sgh-i997 rooted from gb 2.3.6 no modifications except what is found in option C above. and removing some stock libs.

oreo918 said:
I am wanting the dialer and phone apk from the Aeon Rom and put it on my stock rooted rom found in xda-developers website thread here....
http://forum.xda-developers.com/showthread.php?t=1613523
************ OPTION C *************
I997UCLB3-CWM-root-deodex-extras.rar
Features in this version
- Entropy's Daily Driver kernel
- Red CWM recovery
- Rooted
- Deodexed
- Zipaligned
- Busybox
- AT&T and other bloatware removed
- Scrolling wallpaper fix
- CRT off animation
- 8 lock screens
- Extended power menu
- Accurate battery mod
- Get lidroid's 14 statusbar toggles HERE
Thank your for your time, effort and help in advance,
(Sorry for the edit) It might help and then again it may not. But I am using an AT&T Samsung Infuse 4g sgh-i997 rooted from gb 2.3.6 no modifications except what is found in option C above. and removing some stock libs.
Click to expand...
Click to collapse
you may need dialer.apk, phone.apk and maybe contact.apk.
after you move them, set the correct permissions.
reboot.
if that doesn't work, may need to boot into cwm and wipe cache and dalvik.
alternate: you can try using titanium back up..remove those apk and then install the other apks from the myfiles

qkster said:
you may need dialer.apk, phone.apk and maybe contact.apk.
after you move them, set the correct permissions.
reboot.
if that doesn't work, may need to boot into cwm and wipe cache and dalvik.
alternate: you can try using titanium back up..remove those apk and then install the other apks from the myfiles
Click to expand...
Click to collapse
Ok. cool. But when i move them the phone starts to force close like crazy. I move them directly to /system/app/ and replacing the current apps. I didn't move just those apps tho. I also moved phone_Util.apk and PhoneSetupWizard.apk DialerTabActivity.apk and it worked but when someone would call me it wouldn't ring.
So my question is this. Do I just cut/past the ones you just described above to /system/app/ and then fix permissions ignoring FCs to rw-r-r. And reboot. Is that correct?
Thank you for your time. And quick response.

oreo918 said:
Ok. cool. But when i move them the phone starts to force close like crazy. I move them directly to /system/app/ and replacing the current apps. I didn't move just those apps tho. I also moved phone_Util.apk and PhoneSetupWizard.apk DialerTabActivity.apk and it worked but when someone would call me it wouldn't ring.
So my question is this. Do I just cut/past the ones you just described above to /system/app/ and then fix permissions ignoring FCs to rw-r-r. And reboot. Is that correct?
Thank you for your time. And quick response.
Click to expand...
Click to collapse
yeah..just work thru the FC's.
you can also use abd and have no fc issues.
if you are running a rom, you can make those changes to the rom before flashing...either way.
make sure you have a back up of your current set up...zen tool kit allows for a whole rom back up

qkster said:
yeah..just work thru the FC's.
you can also use abd and have no fc issues.
if you are running a rom, you can make those changes to the rom before flashing...either way.
make sure you have a back up of your current set up...zen tool kit allows for a whole rom back up
Click to expand...
Click to collapse
Well I did it like you said worked thru the force closing and changed the permissions of all 3 apks (Contacts.apk DialerTabActivity.apk, Phone.apk)
to rw- r-- r-- is how each apk's permission were then I rebooted the phone. The volume is up and the ringtone is set. But when I call my phone from a different phone it does not ring, and at the bottom of the screen will blink Unknown between the green and red answering/ignore button on screen., even though above that. The picture for the contact calling the cell phone shows up and so do the Name as inputted into phone contacts. I don't know what i'm doing wrong, please help me out if you know what I am doing wrong. Thank you for your time

oreo918 said:
Well I did it like you said worked thru the force closing and changed the permissions of all 3 apks (Contacts.apk DialerTabActivity.apk, Phone.apk)
to rw- r-- r-- is how each apk's permission were then I rebooted the phone. The volume is up and the ringtone is set. But when I call my phone from a different phone it does not ring, and at the bottom of the screen will blink Unknown between the green and red answering/ignore button on screen., even though above that. The picture for the contact calling the cell phone shows up and so do the Name as inputted into phone contacts. I don't know what i'm doing wrong, please help me out if you know what I am doing wrong. Thank you for your time
Click to expand...
Click to collapse
Explain to me what you are trying to do.
Which ROM are you currently running, kernel, root?, odex or deodex? Voodoo (ext4) or stock partition?
It is likely that if you are running simple root stock, with non-voodoo stock kernel, and adding a deodex apk to the mix, the stock kernel may not be able to use the deodex files. you may need to change kernel, or re-odex the apk you are trying to port. Remember, most apk's on the rooted stock has 2 file components.
You can try using the stock deodex base dman made as a base of work from there.
If you are only interested in the appearance of the rom, use 7zip and extract the png's from the apk you want and just paste it into the odex system files to get the same look.
In essence, I think you are trying to theme the stock rom or cook your own.
check here for themes
http://forum.xda-developers.com/forumdisplay.php?f=527

qkster said:
Explain to me what you are trying to do.
Which ROM are you currently running, kernel, root?, odex or deodex? Voodoo (ext4) or stock partition?
It is likely that if you are running simple root stock, with non-voodoo stock kernel, and adding a deodex apk to the mix, the stock kernel may not be able to use the deodex files. you may need to change kernel, or re-odex the apk you are trying to port. Remember, most apk's on the rooted stock has 2 file components.
You can try using the stock deodex base dman made as a base of work from there.
If you are only interested in the appearance of the rom, use 7zip and extract the png's from the apk you want and just paste it into the odex system files to get the same look.
In essence, I think you are trying to theme the stock rom or cook your own.
check here for themes
http://forum.xda-developers.com/forumdisplay.php?f=527
Click to expand...
Click to collapse
I used Odin to flash Option C found here
http://forum.xda-developers.com/showthread.php?t=1613523
Which is Deodexed / Rooted / With Entropy's Daily Driver Kernel. I don't much about the partition stuff yet. Just started to scratch that surface. But i haven't messed with it. I know I have voodoo lagfix in the RED CWM recovery and it did say something about partition when i flashed the rom I can never understand what the chick says tho. But I have not altered it from the file you can download from that thread above. Except for uninstalling a bunch of stock libs.
I am trying to to get the phone app or the dialer setup i guess you can say from the Aeon Rom 1.4 because I can't figure out how to save the Facebook sharing options. via gallery/share/facebook sharing photos and what not. So I went with the stock rom and flash the Lidroid 14 toggle mod. and removed the logsprovider.apk with the modded one found in the same thread with option c in matter of a fact.
Are you saying though that I can unzip Phone.apk and DialerTabActivity.apk here in my PC and take the png?? and paste them to where exactly? I'm sorry I am trying to learn this stuff and It can be very frustrating at times because I am still super new to putting my own rom together. I just want the AEON rom dialer because it has that convenient message tab next to the call tab in the dialer so I want that and the phone to actually ring when someone calls me too.
Thank you for your patience qkster. I still can't believe that you have replied to my thread yourself. I have followed your posts and threads and advice for a long time. I appreciate all your hard work and what not that make ideas likes this possible. YOU ARE THE MAN!!!! lol.
Thank you for your time I hope this was detailed enough for you to get the idea i'm trying to project.

oreo918 said:
I used Odin to flash Option C found here
http://forum.xda-developers.com/showthread.php?t=1613523
I am trying to to get the phone app or the dialer setup i guess you can say from the Aeon Rom 1.4 because I can't figure out how to save the Facebook sharing options. via gallery/share/facebook sharing photos and what not. So I went with the stock rom and flash the Lidroid 14 toggle mod. and removed the logsprovider.apk with the modded one found in the same thread with option c in matter of a fact.
Are you saying though that I can unzip Phone.apk and DialerTabActivity.apk here in my PC and take the png?? and paste them to where exactly? I'm sorry I am trying to learn this stuff and It can be very frustrating at times because I am still super new to putting my own rom together. I just want the AEON rom dialer because it has that convenient message tab next to the call tab in the dialer so I want that and the phone to actually ring when someone calls me too.
Click to expand...
Click to collapse
you are finding out what I consider theory, execution and practice.
in theory, it should work.
execution may not result as intended
practice makes perfect
Couple of issues:
1. you're running jesse's uclb3 rooted with extras. great. it's in an odin format, not a cwm. unfortunately it's not in cwm flashable zip.
you can create one if you google how to make a cwm flashable rom from stock leak.
if you can follow a complex set of instructions, go can try it here: http://forum.xda-developers.com/showthread.php?t=1484578
(Jesse also made this: http://forum.xda-developers.com/showthread.php?t=1711375
essentially the some odin option c you used. (he made that in odin for flash via download mode for borked phones)
his ethereal is essentially the same, meant to flash in RED cwm. except for his themes and sound options similar to sgs3.
the odin option c is essentially stock uclb3)
2. before you do anything, make a back up of your current desired setup with zen tool kit - so you can restore in event of boot loops.
3. have the apk with the icons you want on your pc desktop. use 7 zip. double click into the apk. go to res. go to drawable-hdpi. copies all the png. make a new temp folder on your desktop. call it what you want. paste the copied png into the temp folder and look at in windows, with thumbnail options. you will see the icons you want as it may appear in the rom.
4. pull out the apk of the rom you are running. put it on your desktop. look in it also. using 7zip, pull out the res/drawable-hdpi/ folder onto desktop. if you look in it, you will see the other png that you may no longer want. there are several ways to replace the ones you want but it's easier just to pull all the pngs you want into the drawable-hdpi on the desktop and bring the folder over into the apk or just paste them into the apk's /res/drawable-hdpi/
then flash the modded apk or push it into system
Use this for adb..it's easier to use
http://androidforums.com/esteem-all-things-root/517688-adb-android-commander.html
alternatively:
attached is a cwm-flashable shell...study it with 7zip. look at the updater-script. see what it does.
then put the modded apps into the /app folder and flash.
this can be use to flash framework apk/jar and/or system/app apk
test jesse's ethereal and aeon or any other. mix and match. with zen tool kit restore rom, you want play around and restore it back to where you left off
you can also try just pull the aeon apk into the shell and flash it again
remember too that each dev may have different setup or framework that may not let each apk interact correctly...until you have the right combo of files

qkster said:
you are finding out what I consider theory, execution and practice.
in theory, it should work.
execution may not result as intended
practice makes perfect
Click to expand...
Click to collapse
Thank you very much qkster. I really appreciate your help on this issue. I will be studying these threads and this Android Commander and getting to learn all I can about it. I have followed your posts for awhile and believe you are a very talented developer. I for one appreciate all of your hard work on the Samsung Infuse 4g and insight and advice that you offer.
I'm not gonna just jump right into it, I like to uderstand it all first. But I will definitely be looking this over and trying to absorb it all.
You have kept me busy for probably the next week with this one. Thank You again kind sir. I will let you know in the next day or so to be more realistic as to my progress and if I encounter any problems. Too Bad You don't have a | +1,000,000 THANKS | Button.

oreo918 said:
Thank you very much qkster. I really appreciate your help on this issue. I will be studying these threads and this Android Commander and getting to learn all I can about it.
I'm not gonna just jump right into it, I like to uderstand it all first. But I will definitely be looking this over and trying to absorb it all.
You have kept me busy for probably the next week with this one. Thank You again kind sir. I will let you know in the next day or so to be more realistic as to my progress and if I encounter any problems. | Button.
Click to expand...
Click to collapse
you're welcome.
(btw, i thank you for the compliment but i'm not a dev in the true sense. i can re-using and re-applying what is already out there.)
android commander is a graphic ui for adb..easier to use. you'll see that you can pull/push apks much easier, reboot, etc..
as far as learning ...read as much as your brain can handle and google what info you need...that's how most of us picked up this stuff..gl

Re: [Q] Moving dialer/phone app to stock rom
qkster said:
you're welcome.
(btw, i thank you for the compliment but i'm not a dev in the true sense. i can re-using and re-applying what is already out there.)
android commander is a graphic ui for adb..easier to use. you'll see that you can pull/push apks much easier, reboot, etc..
as far as learning ...read as much as your brain can handle and google what info you need...that's how most of us picked up this stuff..gl
Click to expand...
Click to collapse
I used that program you posted "android commander" and extracted a custom Rom to my PC and then using Android Commander I pushed phone.apk dialertab.apk and camera.apk over to my phone and everything it's working fine. Although I had to change permissions to rxw-rxw-r-x
Instead of rw,r r. But it's all doing fine so far. Phone will ring. Camera takes pictures with the power button and I got my dialer tab wanted. Thank you again man. I appreciate you for real.
Sent from my SAMSUNG-SGH-I997 using Tapatalk

Hey qkster,
I have one more question if you don't mind. Where would i find the File that contains the png's for the notification bar/toggles? I would like to change that stuff around as well and see if I can change the colors and toggle images? Just need to know where to find the file containing those png's

look in:
systemui
settings
frameworks-res
there are several areas...
check the main xda android theme sections
make a revert or backup..once you start playing with settings, systemui and framework-res, you might experience boot loops
use the cwm-shell i posted. put the original working files in the correct location..call it revert...put the experimental files in another shell copy, and call whatever..

Hey qkster ever since I moved those files. that i posted in my last post my text messaging has been acting up. Every once in awhile. I finally narrowed it down to the problem being if the text is too long it fails to send the text message is there a way to fix this while at the same time keeping my alterations I have made to the rom?

oreo918 said:
Hey qkster ever since I moved those files. that i posted in my last post my text messaging has been acting up. Every once in awhile. I finally narrowed it down to the problem being if the text is too long it fails to send the text message is there a way to fix this while at the same time keeping my alterations I have made to the rom?
Click to expand...
Click to collapse
prolly your modem..not your mods
http://forum.xda-developers.com/showthread.php?t=1342978

Re: [Q] Moving dialer/phone app to stock rom
qkster said:
prolly your modem..not your mods
http://forum.xda-developers.com/showthread.php?t=1342978
Click to expand...
Click to collapse
What do ya know ? You were right again. Lol. Thank bro your awesome.
Flashed uclb3 & that fixed. Thanks again
Sent from my SAMSUNG-SGH-I997 using Tapatalk

[MOD][May 24th]NFC while Screen Off/Locked 1.0[Sammy]

Introduction
Hey guys
Last night I got my new NFC tags and, of course, went ahead and configured one for my car. What it does is irrelevant (turns on Bluetooth and 3G, turns off Wi-Fi when I get into the car, and turns off Bluetooth and GPS when I leave it), but what's important is that I was absolutely sure I could use it when the screen is off or even unlocked.
It was a bit of annoying to turn on the phone and unlock the display to use an NFC tag, when the entire purpose of a tag (in my view) is to let me do stuff without touching the display!
I found a few apks, but all of which were reported to make NFC FC/crash or not work at all. The suggested solution based on the Xposed framework was unavailable due to site problems, so i decided to see how difficult it is to implement one on my own...
What is this mod?
This mod, as you might have guessed already, simply lets you use an NFC tag when the screen is off or locked.
Installation
Very simple indeed:
Download the included Nfc.apk file,
Do a nandroid backup (backuping your current Nfc.apk (located at /system/app/Nfc.apk) to someplace safe should suffice, but a nandroid is still recommended),
Copy the included Nfc.apk to /system/app/Nfc.apk,
Change permissions to 'rw-r--r--' ('chmod g-w', 'chmod 644' or your favorite file explorer),
Reboot.
Changlog
Version 1.0:
First release!
Covering my *** part
I am not responsible for any nuclear wars that may result from downloading and installing this Nfc.apk, nor am I responsible for your device breaking, bricking, rebooting, data loss, etc.
About making this mod (and credits)
It was actually surprisingly easy. Figuring how to decompile the APK into a smali (using APK Multi-Tool), and where to go (Geniusdog254's explanation was simple but excellent) was quite easy, and from there it was the road to success.
Also, looking at the relevant code was very helpful (although Samsung added some extra checks, the original code to delete was still very much there).
I also made sure to delete only NFC-C related code, and not to touch anything else (including NFC-EE and SMX, UICC, CardMode, etc).
Do note I am using a DMB6-based ROM (Phoenix v10), but I compared the decompilation output of DME1 and the entire code is identical, so it should be safe to install on any DMB6-and-newer ROMs.
Also, this should only be used on a deodexed ROM.
Enjoy!

making life easier, a flashable zip.
as always, its never wrong to make backup before flashing
enjoy
thank you OP for providing us this mod.. THANKS~~!!

Freezeil said:
Installation
Very simple indeed:
Download the included Nfc.apk file,
Do a nandroid backup (backuping your current Nfc.apk (located at /system/app/Nfc.apk) to someplace safe should suffice, but a nandroid is still recommended),
Copy the included Nfc.apk to /system/app/Nfc.apk,
Change permissions to 'rw-r--r--' ('chmod g-w', 'chmod 644' or your favorite file explorer),
Reboot.
Enjoy!
Click to expand...
Click to collapse
It doesn't work on stock MC3, am I missing something?
attached stock apk here
xcxa23 said:
making life easier, a flashable zip.
as always, its never wrong to make backup before flashing
enjoy
thank you OP for providing us this mod.. THANKS~~!!
Click to expand...
Click to collapse
Why your script have command to change permission of bootanimation.zip instead of Nfc.apk??

dr.ketan said:
It doesn't work on stock MC3, am I missing something?
attached stock apk here
Click to expand...
Click to collapse
Apologies, I never meant it to run a stock ROMs...
Give me some time to see if I can make it work on stock

No problem, If it is made for deodexed rom only then it would be better if you can edit title/OP
Sent from my GT-N7100 using xda premium

Good idea (didn't even think about it... ), but let me see if I can make it for odexed roms as well beforehand.
It is my first mod ever so bare with me
Sent from my GT-N7100 using Tapatalk 2

Just send me apk with this process
Reodexed your existing rom - deodexed again
Will check it, i have seen sometimes this works.
Sent from my GT-N7100 using xda premium

As you might have known, the APK you sent me doesn't contain the actual code (the dex files).
I downloaded a stock odexed MC3 ROM and saw that the code is pretty much the same (didn't make sure), but it would not be possible to make an MC3-compatible odex file from my ROM (which is ME1).
Also, afaik, the odex file also contain other stuff (like dependencies and such), so I wouldn't try replacing the .odex file without re-odexing the entire ROM. Even after replacing the .odex file, I think matching files in /data also need to be replaced, and I read someplace that doing nasty woodoo like this might cause bootloops...
Is there anyone here who's running MC3 ROMs and willing to re-oxed it to its entirety and try this?

I'm getting ready to give this a try on Beans 17. Will let you know the results and shower you with thanks if it works.
UPDATE: You are officially my hero. Works like a charm.

Just ran it on beans 17 and it also works for me.
I'm curious to know how this will affect battery life.

Thanks for this great mod.
Is there any other chance to wake screen with NFC than tasker since secure settings and simplistic framework won't work with each other?

I tried installing it on my Droid razr maxx HD. No luck though . The NFC option disappears from the system settings.
EDIT: I'm retarded. It's probably because this is only modded for Galaxy Note II.

Just letting everyone this also works for AT&T Galaxy Note II LTE.
Awesome!!!!!!
Sent from my GT-N7105 using xda premium

A bit of shame not working on Akop rom. I liked your idea. Can I post the nfc from Akop if that can help?

Does this work for Verizon note 2?

Has anyone tried this on Galaxy S3 (GT-I9300 international).
Nearly forgot - I'm running OmegaRom 46.1 (4.2.2)
I want it for exactly the same reasons - nfc tag in car to switch on BT, sync with stereo and launch BeyondPod playlist without having to unlock.

This shouldn't work
Though send me framework-res.apk, twframework-res.apk and Nfc.apk (deodexed)
will look to it.

Hi,
what could be for reasons that the modified NFC-Version on my SG Note 2 LTE (German) does not work?
Does anyone have any advice?
regards
Vinz