Hello everyone,
I recently built the omnirom sources for my Pico and there is still a phenomena I can't understand.
Ths sources includes Email.apk and Exchange.apk.
The pico specific part include Latinime.apk and Dashclock.apk.
I found them, after the build, in the out/target/product/pico/system/app directory.
I also found them in the generated system.img, after extracting it.
But... I don't find them* in the flashable zip! Sound crazy! Could someone explain me what I am doing wrong? ><
Thanks in advance,
edit: I tried cleaning out directory and ccache, but it changed anything.
*them==> Email.apk and Exchange.apk.
Giving up.
I've never seen this on any of our builds so I have no idea what's going on.
System configuration error? Running out of space? Some sort of weird filtering script removing the APK? (I sorta recall that some devices had these as a workaround for tiny /system partitions back in the CM days...)
Related
Searched around a lot, honest.
Looking for the MIUI Camera in an installable format -- tried adb push to system/app of the most recent "MIUI Camera.apk" from the Hyperdroid CM7 thread (this one), but it most definitely did not work. Reboot, etc. Nothing. Wouldn't start -- icon disappeared from the dock, too.
Restored the original Camera.apk via adb push after extracting it from the original HD-CM7 zip. So, it's not the process of installing it, it's something else.
Anyone have advice?
Aloha,
cap
capidamonte said:
Searched around a lot, honest.
Looking for the MIUI Camera in an installable format -- tried adb push to system/app of the most recent "MIUI Camera.apk" from the Hyperdroid CM7 thread (this one), but it most definitely did not work. Reboot, etc. Nothing. Wouldn't start -- icon disappeared from the dock, too.
Restored the original Camera.apk via adb push after extracting it from the original HD-CM7 zip. So, it's not the process of installing it, it's something else.
Anyone have advice?
Aloha,
cap
Click to expand...
Click to collapse
nope you didn't searched a lot...
I bet you didn't do the following before creating this thread:
1. did you check the permissions of the camera apk?
2. if you checked, was it rw-r-r?
3. did you delete the data file that corresponds to the app?
4. lastly, have you tried looking into themes and apps section so that you'll see this on page one of that section???
http://forum.xda-developers.com/showthread.php?t=975196
1) Yes, I did.
2) Yes, it was.
3) No, wasn't aware that I needed to. Thanks for the hint.
4) I searched Themes and Apps, and found no results that suggested success directly concerning Hyperdroid. But searching, of course, is dependent on keywords and search algorithms.
Thanks for the help, and if it works, I'll be sure not to post about it.
Aloha,
cap
I'm in the process of deodexing the stock ROM (4.5.1-134_DFP-82) on my Defy+. I've tried a number of the deodexing tools posted around XDA and elsewhere but nothing would run anything like clean, so I've been building my own script to do it.
I've successfully deodexed everything in /system/framework/ and 151 out of 155 odexes in /system/app/. It has been quite interesting, tracking down the missing classes when something doesn't deodex clean first time with the default BOOTCLASSPATH files. Unfortunately, though, four of the .odexes in /system/app/ have got me beat.
The first one is Settings.odex. This is reporting:class Lcom/motorola/android/mirrorservice/IMirrorService; cannot be resolved.I can't locate that class anywhere. I've tried disassembling everything in both directories and searching the results but it just doesn't seem to be there. Settings seems rather too important to just allow baksmali to ignore the error.
The other three - DLNA.odex, MediaGallery.odex and VideoPlayer.odex - all display the same symptom. Trying to deodex with just the standard BOOTCLASSPATH files gives the error:class Lcom/motorola/android/extdispservice/IExtDispService; cannot be resolved.Adding /system/framework/com.motorola.blur.library.service.odex to the BOOTCLASSPATH files makes that go away, but instead gives the error:Could not find superclass Lcom/google/protobuf/GeneratedMessage$BuildeI've seen that one several times and the way to fix it has always been to add /system/framework/com.motorola.blur.library.utilities.odex to the BOOTCLASSPATH files. But in this case I end up with the error:class Lcom/motorola/android/extdispservice/IExtDispService; cannot be resolved.again. It's taking me round in circles! I've tried reversing the order of utilities and service but that doesn't fix it either.
Anyone able to suggest how I might get rid of these errors? The second one in particular is doing my head in!
OK, so I've done a bit more digging around online and it seems that both those classes are to do with the HDMI interface, which of course the Defy doesn't have. baksmali continues anyway and creates the out folder, so I'm assuming that it should be OK to zip those back in to the relevant apks and try those. Does that sound right?
Hi ejstubbs
thanks for starting this thread...i was wanting to start deodexing roms on my own. can you please help me with the apps needed and/or some link where i can get a thorough knowhow about deodexing roms for my Defy?
Questions go in the Q&A section, not the Dev section.
So I attempted and failed to install the 4.2 keyboard and clock. I am sure I am doing something stupid, but I attempted to take the files that can be found out and about:
DeskClockGoogle.apk and LatinImeGoogle.apk and put them in /system/app, and put libjni_latinimegoogle.so in /system/lib, and nothing happened. I then moved DeskClock.apk to DeskClock.apk.orig and LatinIME.apk to LatinIME.apk.orig, and that did less than nothing...I lost my stock keyboard and clock (as expected), but still no new keyboard or clock.
Please advise....any help appreciated.
Cheers
Rich
I figured it out, silly mistake. If you do this manually, you need to fix permissions (644, make sure it has group and other read permission). Once I did that, a reboot sorted it out.
I got the apks from here: http://www.gnufabio.com/?p=195 btw.
Good day, all!
I've been working on [my first] ROM for Verizon S5 and everything seems to be going great! I've cleaned out as much Samsung/Verizon/Google trash as I can, applied some tweaks to build.prop, changed some default apps to (IMHO) better replacements, and anything that is left (functions correctly) has been moved to /data/app so they can be Uninstalled fully (not just Turned Off). Just a few quick questions:
1) How can I "bake-in" app data? I have replaced the normal, crap launcher with Holo Launcher and cannot seem to get correct permissions when the ROM is installed thru SS. I believe the issue is permissions for /data/data/ get screwed up or not set correctly. I have looked and looked and tried to determine the correct permissions, but still no joy. I've tried to fix /data/data permissions in the updater-script, but it seems like each subfolder/file has different permissions making me think I'll have to go thru them one-by-one.
I have a work-around in place using a OneTimeInit script that does work, but it seems like that's not really the best approach?
2) Kind of ties into question number 1, I patched the framework-res.apk in to allow WiFiHotspot, but without being able to install the system settings data properly, there is not a "Quick Shortcut". Again, I've resolved the problem using the OneTimeInit to update Sqlite DBs after the system is up.
3) How do I de-odex the stock ROM? Using Android Kitchen doesn't seem to do it right. It works mostly but I still seem to get various FCs. I tend to believe that some things just cannot (should not) be De-Odex'd?
I've also discontinued Zip-Aligning because it sometimes produces errors on my ROM. Is it not advised to use Android Kitchen to do these tasks or is there some trick to getting it to work just right?
Bonus Question) I was going to share my ROM on XDA but it says I'm not allowed to post in Development. I assume because of my low post count. Any way I can get an over-ride or should I just make a few more posts and then do it?
Thanks again guys!
I appreciate all the help as always!
Jake
jake5253 said:
Good day, all!
I've been working on [my first] ROM for Verizon S5 and everything seems to be going great! I've cleaned out as much Samsung/Verizon/Google trash as I can, applied some tweaks to build.prop, changed some default apps to (IMHO) better replacements, and anything that is left (functions correctly) has been moved to /data/app so they can be Uninstalled fully (not just Turned Off). Just a few quick questions:
1) How can I "bake-in" app data? I have replaced the normal, crap launcher with Holo Launcher and cannot seem to get correct permissions when the ROM is installed thru SS. I believe the issue is permissions for /data/data/ get screwed up or not set correctly. I have looked and looked and tried to determine the correct permissions, but still no joy. I've tried to fix /data/data permissions in the updater-script, but it seems like each subfolder/file has different permissions making me think I'll have to go thru them one-by-one.
I have a work-around in place using a OneTimeInit script that does work, but it seems like that's not really the best approach?
2) Kind of ties into question number 1, I patched the framework-res.apk in to allow WiFiHotspot, but without being able to install the system settings data properly, there is not a "Quick Shortcut". Again, I've resolved the problem using the OneTimeInit to update Sqlite DBs after the system is up.
3) How do I de-odex the stock ROM? Using Android Kitchen doesn't seem to do it right. It works mostly but I still seem to get various FCs. I tend to believe that some things just cannot (should not) be De-Odex'd?
I've also discontinued Zip-Aligning because it sometimes produces errors on my ROM. Is it not advised to use Android Kitchen to do these tasks or is there some trick to getting it to work just right?
Bonus Question) I was going to share my ROM on XDA but it says I'm not allowed to post in Development. I assume because of my low post count. Any way I can get an over-ride or should I just make a few more posts and then do it?
Thanks again guys!
I appreciate all the help as always!
Jake
Click to expand...
Click to collapse
1: All I had to do was place apk in /system/app or /system/priv-app and thats it. Make sure when you add your apks you dont unzip the archive. basically use kitchen and build your base rom then simply open the archive and make your edits. I also used the updater script from beans base build and only edited the ui print.. Messing with the updater script i wouldnt recommend as it could be causing some of your issues.
2: If using beans base theres no reason for you to edit anything as the hotspot is already baked in.. you must have borked it.. If you are not using beans base then maybe you should copy his files for the native hotspot as its already done properly. I wouldnt mess with framework or settings apks unless you know what your doing. Id work on gettin the fcs n other issues sorted first as you might b doin too much too fast.. work on learning how to make your apks work first before making edits to framework n settings apks.
3: The kitchen is best to deodex and zipalign.. also these two things should not cause fcs or errors if done properly. zipalign should help more than anything.. i just like workin with deodex bcuz its easier and only one set of files instead of .apk and .odex for just bout everything..
Again, if you are not using beans bases id recommend to do so.. his bases are already deodexed have hotspot zipaligned read/write to ext sd etc.. so you wouldnt have to do all from scratch and have so many issues..
Sent from my SM-G900V using XDA Premium HD app
elliwigy said:
1: All I had to do was place apk in /system/app or /system/priv-app and thats it. Make sure when you add your apks you dont unzip the archive. basically use kitchen and build your base rom then simply open the archive and make your edits. I also used the updater script from beans base build and only edited the ui print.. Messing with the updater script i wouldnt recommend as it could be causing some of your issues.
2: If using beans base theres no reason for you to edit anything as the hotspot is already baked in.. you must have borked it.. If you are not using beans base then maybe you should copy his files for the native hotspot as its already done properly. I wouldnt mess with framework or settings apks unless you know what your doing. Id work on gettin the fcs n other issues sorted first as you might b doin too much too fast.. work on learning how to make your apks work first before making edits to framework n settings apks.
3: The kitchen is best to deodex and zipalign.. also these two things should not cause fcs or errors if done properly. zipalign should help more than anything.. i just like workin with deodex bcuz its easier and only one set of files instead of .apk and .odex for just bout everything..
Again, if you are not using beans bases id recommend to do so.. his bases are already deodexed have hotspot zipaligned read/write to ext sd etc.. so you wouldnt have to do all from scratch and have so many issues..
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
Thank you for the response!
It seems perhaps I didn't quite make clear what I've done versus what I'm trying to accomplish.
Firstly, I wouldn't go so far as to say I'm "having so many issues". Everything in my ROM is in perfectly fine working order. I just have these few quirks that I would like to address both so I can learn, and to make this and future projects better.
While I appreciate the recommendation to use bean's base, I have taken a look at his and there seems to be nothing in his which copies data into /data/data/com.whatever.package (or at least there's nothing in his zip in the /data/data folder -- not sure if his ROM has the toggle activated?)
I have the Apps working correctly in my ROM -- they just go in /data/apps, /system/app or /system/priv-app, respectively.
What I need, is to get /data/data/com.whatever.package/ copied With Correct Permissions when the ROM is installed; I do not want a second zip to update things after install, especially for a toggle and a couple shortcuts, seems silly.
For instance, when you boot your phone up with the default [stock] samsung launcher, it has a list of default apps and widgets on the first screen you see such as phone, messages, a clock widget, etc, etc. Since I've replaced the stock launcher with Holo Launcher HD and some other default apps have also been replaced, there's very few shortcuts on the main launcher screen.
** Holo Launcher does have a list of default apps it adds to your main page, but many of those have been removed in my rom.
The solution I've come up with basically waits for the system to boot up to the point that Holo Launcher actually creates the default (mostly blank) /data/data/com.mobint.hololauncher.hd/databases/launcher.db and then my script uses sqlite3 to update the DBs with a list of different shortcuts -- ones to apps that actually exist.
The Hotspot Toggle is the same way as above.. Hotspot works fine in my rom if you go through settings!
I just cannot add the notification panel pull-down toggle to /data/data/com.android.providers.settings/database/settings.db until after the system boots up at least ONE time, and then update the DB to include WiFiHotspot in notification_panel_active_app_list and notification_panel_active_app_list_for_reset
As for the zipalign and deodexing, I will have to try those again now that I have a fairly stable rom.
****EDIT****
I think I figured it out. I can just use busybox to kill the systemui after I update the databases during the first boot. I also figured out how I can add the SetupWizard without it locking up on activation.
Thanks anyways, guys.
Look for my rom, coming soon!
=P
Please add support for more languages
I found a mod for Motorola latest 4.4 please port it
Sent from my SM-G900T using XDA Free mobile app
Hey guys.
Having some difficulty here with modifying system APKs without leaving them 'corrupt'.
Specifically with SecSettings and SamsungCamera6.
Only looking to simply modify the qmg icons for the time being.
Ticklemyandroid didn't really want to know with SecSettings. Tried using apktool manually after installing the framework-res.apk and still doesn't seem quite right. Also tried apk multi took. Even went as far as simply trying to past the qmg files into the existing APK with winrar but that really broke things.
I believe my issue is partly that things aren't decompiling properly, but also that I'm a little unclear of the correct procedure to recompile them afterwards without any errors or corruption if tapping on them to install (I'm not actually trying to install them this way, but I'm looking to get to package conflicts rather than package corrupt).
Edit: NVM. Seems like some kind of protection to prevent you from modifying and installing said APKS