So I typically like to tinker when I get new phones/tablets. One of the first mods I always attempt is an extended power menu. That means android.policy.jar and framework-res.apk need to be pulled to my computer for decompiling. Not to mention, deodexing the jar file. But for the life of me, I cannot find the odex component for android.policy.jar. Has anyone else found it? In past OS versions they were there beside their jar/apk mates. And in lollipop, looks like in /system/framework there is an /art folder which has SOME of the odex files but not all.
There are no odex files because they are deodexed by default.
There is no android.policy.jar for Android 6.0 both GPE and Sense.
If you want to add in Advance Power Menu, you need to see services.jar & framework-res.apk
Hint : \services.jar\smali\com\android\server\policy
If you manage to make one, let me know (by PM also ok) because I don't have the time to look further into it.
Related
Hello,
I always got Multiple lockscreen frameworks such as EDT and JKay's Lockscreens. I really want to know, actually where are these files located in framework-res..
I want to port EDT's JVR lockscreens to JVS framework.
Anybody willing to help me?
Regards,
Rahul
I'm quite interested in this too...and I guess that nobody will write us down a list with needed files .....I can tell you what I've found out so far and hope that it will be of any help to you.
The smali files for the lockscreen itself I think they should be in android.policy.jar
Then there also should be some changes in framework.jar which I do not know.
The ressource files like pictures etc are in the framework-res.apk
Then you also need the edt.apk in /system/app
Decompile the files with apkmanager/baksmali
Use a comparision tool like winmerge to see what files are added additionaly compared with the standard stock files. And also too see if there are smali changes in some files.
Good luck
Sent from my GT-I9000 using Tapatalk
why bother, they are not bug free anyways
$omator said:
why bother, they are not bug free anyways
Click to expand...
Click to collapse
You said that more than once now, but I sure as hell don't suffer any bugs while using them on JVQ or JVR.
While we're at it, I thought, hey, what the hell, I can learn and do it myself. Always good to learn this sort of thing. So I got smali/baksmali, winmerge, and Whitehawkx's source files, which I think will work.
But that's not the point.
The point is that baksmali is desassembling the .dex files just fine, but when I want to make a new file after merging the files from the sources with the originals of the .dex... It makes a .dex with the original files.
That is: disassemble -> merge the files -> I make sure the files are there. They are. -> I use smali, it creates the new .dex -> As everytime I do anything, I think, hey, lets disassemble the new file again to make sure the new files are there -> The files are not there.
It's driving me crazy... I mean, how the hell does it create a file from something that isn't there any more?
I can sort of get that the new files and folders don't make it to the new .dex (although, no, I don't get why would that be), but how can the overwritten files go back to be the original ones?
Seriously, driving me crazy.
Edit: Ok, nevermind what I said... The files change frigging places when smali assembles them...?
Edit2: Suprise, surprise, it didn't boot, but now I don't know if it's because I did something wrong or because the source files aren't good for JVS. I'm gonna try to do it on JVP, I'm curious now...
$omator said:
why bother, they are not bug free anyways
Click to expand...
Click to collapse
Well because some of them have features people want to have...and also because people can live with some of the bugs. I don't care if it writes me SIM-Card is locked even if it isn't. The functionality doesn't decrease because of that.
But well these lockscreens give us a music widget that works with other players then the crappy samsung stock one. And I can unlock directly to messages or phone. If it was for me I would only need something like the fourtab(which sadly has a memory leak)...but if the whole package could be ported or whatsoever and people would like to do it why not ?
Code is present in the android-policy.jar and framework.jar (for some lockscreens). You need to copy over the Smali Files fromt he MOD to the JVS framework and android policy. After that you need to copy over the drawables, layouts and other xml files to the framework apk of JVS and assign them each a unique resource ID. These resource IDs need to be substituted with the new values in the Smali files. Since the framework-res.apk changes with Firmwares, the Resource IDs are different for each framework.
It's very complicated stuff for rookies. You need to know which stuff to copy where and what modifications to make for specific lockscreens. And you need to use Logcat and do a lot of trial and error.
And $omator is right. Those lockscreens all together don't work perfectly due to conflicting code. For example, I made a SGS II Lockscreen Port http://forum.xda-developers.com/showthread.php?t=1070564 . The Same Lockscreen that is found along with 9 Lockscreen MOD is incomplete and doesn't work perfectly. I don't mean to say that the 9 lockscreen mod is useless, but It is very handly provided you compromise on what you get.
dhiru1602 said:
Code is present in the android-policy.jar and framework.jar (for some lockscreens). You need to copy over the Smali Files fromt he MOD to the JVS framework and android policy. After that you need to copy over the drawables, layouts and other xml files to the framework apk of JVS and assign them each a unique resource ID. These resource IDs need to be substituted with the new values in the Smali files. Since the framework-res.apk changes with Firmwares, the Resource IDs are different for each framework.
It's very complicated stuff for rookies. You need to know which stuff to copy where and what modifications to make for specific lockscreens. And you need to use Logcat and do a lot of trial and error.
And $omator is right. Those lockscreens all together don't work perfectly due to conflicting code. For example, I made a SGS II Lockscreen Port http://forum.xda-developers.com/showthread.php?t=1070564 . The Same Lockscreen that is found along with 9 Lockscreen MOD is incomplete and doesn't work perfectly. I don't mean to say that the 9 lockscreen mod is useless, but It is very handly provided you compromise on what you get.
Click to expand...
Click to collapse
Very complicated to do something like that from scratch, yes.
If at least one of the persons that have made a 9 lockscreen JVS rom posted the sources... From there I've learned by now that it's fairly easy to just include them into the files.
But no one have.
If you really want to learn how to do it i can only recommend read lots of info and do some investigations by yourself.
If some guy made the stuff for lets say XXJVQ then grab the files and compare them with the stock files. Decompile them with apkmanager. (jar files can also be modded this way, you only need to add .apk to the jar extention, and remove it later after compiling back)
This way you can see what files need to be added and what values need to be changed/added. First try to understand the process and after that make your own mods.
I used Winmerge for comparisation of the files.
Well... I modded the overscroll by myself. It's a start.
Thanks to Team Obssessed, we can already have multiple lockscreens on JVS.
I already made a theme as I like and added the lockscreens thanks to the files of this rom.
Now I can have a proper JVS .
Is just that I'm too used to puzzle and MIUI lockscreens to go back to stock or AOSP. And those two work without bugs, so... And don't know about the rest.
and btw. apkmanager got aapktool with outdated baksmali/smali ...
Does anyone know which files are required for Flashbar/Multiview to work? This includes and apk's or jar files that contain or uniquely manage a part/aspect of the flashbar service.
Obviously, there are 3 flashbar/annodate and 1 multiview apk in the system/app folder and I believe there is a multiview/flash service jar files in the Lib or ETC folder (don't have a sample rom in front of me) but what other files are needed (or need to be altered) in order for the application to run? Specific Touchwiz version/file, framework file, system ui, android ui, additional lib, jar, sh files, etc.......
Please, only respond if you KNOW 100% sure. Thanks and any help would be appreciated!
arshull said:
Does anyone know which files are required for Flashbar/Multiview to work? This includes and apk's or jar files that contain or uniquely manage a part/aspect of the flashbar service.
Obviously, there are 3 flashbar/annodate and 1 multiview apk in the system/app folder and I believe there is a multiview/flash service jar files in the Lib or ETC folder (don't have a sample rom in front of me) but what other files are needed (or need to be altered) in order for the application to run? Specific Touchwiz version/file, framework file, system ui, android ui, additional lib, jar, sh files, etc.......
Please, only respond if you KNOW 100% sure. Thanks and any help would be appreciated!
Click to expand...
Click to collapse
im looking for the answer to this as well, for the GE of the s 4 ROM. surely there is more than flashbarservice.apk
Please help, is there any specific how to or tutorial on how to make Odex cm 12.1 or 12 directly on the phone. On my Xperia m. Using commands line or apk maybe.
I want to Odex :
Code:
/system/app
/system/priv-app
/system/framework
Thanks in advance.
Add explanation
Quote from nexus 5 thread. Link in post 3.
*What is ODEX and DEODEX?
Odex = More speed__Less customization
Deodex = Less speed__More customization
Extensive explenation:
In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These odex files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applicationsdifficult because a part of the coding has already been extracted to another location before execution.
THEN COMES DEODEX
Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files. By doing that, all pieces of an application package are put together back in one place, thus eliminating theworry of a modified APK conflicting with some separate odexed parts.
In summary, Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming. Since no pieces of code are coming from any external location, custom ROMs or APKs are always deodexed to ensure integrity.
I think that you like more speed and less customization (less costumization for dev because is to difficult mod an Odex file)
Another explanation is this:
If you use a odex rom, you'll have also more space in data (this is important because if you don't have partition ext4 in sdcard, you won't have too free space), increase battery life, more stability and increase perfomance( the Rom is more faster to load system and app) but you can't modifie apk after odex (you can't mod program with classes.dex).
Infact ODEX is an OPTIMIZED-DEX and Android load system and app faster than deodexed (DEOPTIMIZED-DEX) app and system.
When you have a deodex file (a lot of roms are deodexed) you have File.apk in system/app and in data/dalvik-cache [email protected]@[email protected], but with odex file you have File.apk in system/app and File.odex in system/app
ndrancs said:
With odexed the rom, you can get more free space in internal memory, about 400mb.
Click to expand...
Click to collapse
It's also more stable and faster... Thought also about but have doubts that it's easy possible in the Art system because of subfolder structure, missing symlinks and so on... Will be hard work
http://forum.xda-developers.com/android/help/odex-deodex-matter-android-lollipop-art-t2944293
But it seems, some did it:
http://forum.xda-developers.com/goo...om-xtraslim-1-0-stock-odex-optimized-t2924150
This tool http://forum.xda-developers.com/showthread.php?p=47462548
Not yet updated to support lollipop / 5.x.x
Hi everyone. I own the Samsung Galaxy J3 2016 carrier Virgin Mobile. I am attempting to decompile android.policy.jar to do some smali editing. And oddly enough a number of the general jars we all edit regularly to add mods such as reboot menu,etc. are pretty much empty files on my J3. The android.policy.jar file is only 309 bytes with nothing in it except a Meta INF folder with MANIFEST file in there but noting else at all. No classes.dex. Now I thought ok maybe its because I am not deodexed. So I looked in the arm folder in framework and there are indeed odex files in there but none for android.policy.jar nor other typical modded jars we tend to mod. Is this normal across the board for newer Samsung devices like the S6/7 models? Also when I decompile an apk like SystemUI.apk there are no smali files included with the decompiled apk. But the apk seems to decompile correctly and I can edit whats there just fine and recompile it and use it successfully. I just added a center clock mod to SystemUI in fact and it works fine. Just confused about what I am missing here. I seem to have all of my tools up to date for decompiling. Can anyone point me in the right direction? Or give me some insight on these new changes. Thanks
All it takes is for you to take a backup and run the deodex wrapper on your device creating classes.dex's files in all you'r apks allowing to edit the smali. I would do it myself but I currently dont own the device.
Pneuma1985 said:
All it takes is for you to take a backup and run the deodex wrapper on your device creating classes.dex's files in all you'r apks allowing to edit the smali. I would do it myself but I currently dont own the device.
Click to expand...
Click to collapse
Here you go i included the app, dex, framework, odex, priv-app you will need 7-zip because i compressed it from 850mb's to 350mb's.
https://www.androidfilehost.com/?fid=24549084345925845
That does not have all the .dex files in the dex folder. Thus I can not access the smali... Which is what I was after a certrain method within the netxbit systemUI smali. Though it did give me the .dex files of several apks just not the exact one I was after. How do I access the systemUI .dex. It's been a long time since I've made roms and deodexed apks especially now with art. I'm really after the UI .dex file so I can gain access to a specific method within in it. If you could post that I'd be ecstatic Something I decompile to track down smali methods I want to recreate in my own custom 6.0 SystemUI.
Nvm Ticklefish's tool did the job http://www.mediafire.com/download/czod7v081w0ravt/TickleMyAndroid+-+v13.3.0.exe
The only tool out of all the deodexing tools that worked!!!!! The only one! Aside from the linux kitchen but I wasnt setting that up... Mess up my linux install no thanks!
FM radio
Is this FM radio apps