Related
I tried to run pngopt on the latest froyo release and after flashing the ROM, the HTC_IME.apk continually force closes.
I ran the pngopt on the entire /system/app dir before flashing and now I recall reading from Fresh's release notes that through experience he knew what apk's did not pngopt well.
Can anyone give me a list of apk's I shouldn't touch with pngopt?
Since I'm sure not a lot of people know the answer to this I will just post my findings so far.
It looks like HTC_IME.apk is the only apk that doesn't like png optimization. I have been running my ROM for several hours and no problems so far after replacing HTC_IME with the original untouched version.
I removed all of the Sprintware first, so there may be problems with those apk's and pngopt, I have no dersire to install those and find out
I've been searching this forum and google. What is pngopt?
ioos said:
I've been searching this forum and google. What is pngopt?
Click to expand...
Click to collapse
I'm an idiot. You guys are just talking about generic png optimization aren't you? So you just unzip the apk, optimize it and re-zip? Is there a "favorite" optimizer for linux?
Hey Guys,
This is a port from an Xperia X8 MIUI Port, which is EXTREMELY buggy, if you are not very experienced in flashing then i urge you not to flash this ROM. I am not responsible if you brick your phone when flashing this ROM, so don't complain to me if you do
Okay the current release's are very very very buggy , we have only just managed to get adb working in the last hour. If you are interested in helping to develop this rom then feel free to download it. If you are looking for a fully functioning rom then they're are plenty others throughout the forum not here
Link to Current ROM ( really not ready for anything atm, unless you want to help dev, don't bother flashing )
http://www.mediafire.com/?reco2eej12a1w Use current version stated in OP. (Build0007 up tonight.. hopefully)
Installation.
1. Wipe of all (even if coming from previous installation)
2. Select Hero-MIUI_Alpha..
3. Flash
4. Wait, may take a while due to re-build of dalvik.
Thanks to:
Erasmux
Ybinnenweg
Pulser
Dsixda
The guys on the VR IRC
Feel free to pm me to offer your support, please do not ask for an ETA however.
Alpha0007 will NOT be released, major problems with egl. Changelog is for dev's mainly.
Initial Build
Changelog
Alpha0007 (5+6 not released.)
removed themed adw launcher and put original back
switched to cm6 launcher
added AudioFilter to system/etc
added AudioPara4 to system/etc
added AudioPreProcess to system/etc
switched apns-conf for cm6 one (system/etc)
switched 01_qcomm_omx.cfg for hero one(system/etc)
removed HTC_imel01 from system/app
removed suquashi inputmethod from system/app
removed semcsfmfm from system/framework
added su from cm6 to system/xbin
added wlan_cu from cm6 to system/xbin
added egl libs from hero to system/lib/egl
removed original egl files from system/lib/egl
added original hero nanorc files to system/etc/nano
added 04module from cm6 to system/etc/init.d
added 30cpumem from cm6 to system/etc/init.d
added 99complete from cm6 to system/etc/init.d
removed yamato_pm4.fw from system/etc/firmware
removed yamato_pfp.fw from system/etc/firmware
removed TIInit_7.2.31.bts from system/etc/firmware
added tiinit_5.3.53 to system/etc/firmware
removed fmc_init_1273.1.bts from system/etc/firmware
removed fm_rx_init1273.1.bts from system/etc/firmware
removed fm_tx_init1273.1.bts from system/etc/firmware
added avpr.bts from cm6 to system/etc/firmware
added brf6300.bin from cm6 to system/etc/firmware
added brf6350.bin from cm6 to system/etc/firmware
added vac_config from cm6 to system/etc/firmware
kept original fm_tx_init_1273.2.bts
Alpha0004
changed launcher2 to a themed adw launcher from a g1 rom
changed framework-res and mot-framework-res to resized versions from mdpi pack
used ele's update script
switched system/bin/.. files for cm6 ones (except those which have miui app dependencies)
updated ramdisk with hero lib's
removed com.sonyericsson.smfmf from system/etc/permissions
removed com.sonyericsson.suquashi from system/etc/permissions
removed com.ti.fm.fmrecieverif from system/etc/permissions
added Fw12551r1c.binto system/etc/wifi
deleted bootanimation.zip from system/media
switched all .kl files for keychars for hero-cm6 ones
switched all .kl files for keylayout for hero-cm6 ones
removed com.sonyericsson.suquashi from system/framework
removed radio.apk from system/app
Alpha0003
framework-res fixed (hopefully)
system/libs updated
busybox problems solved (hopefully)
Build.prop fixed
Alpha0002
Removed App2SD (Not removed yet, kept it for now..)
Switched to a different framework-res ( causes apps to f/c, i know )
Small changes
I just want to say good on you for giving this a go. It's nice to see some new people having a go at developing. So good luck!
I have adb working.. will post a logcat within 10 minutes
EDIT:
Here is the logcat of the boot.
http://pastebin.com/MZFgwhUX
Rom is booting!
Use alpha 003 then follow this steps:
in the folder "data" make a folder called "local"
now copy "bootanimation.zip" from "/system/media/" to "/data/local"
it should boot now it doesn't work, only shows the setup guide, after that it fc's on the launcher.
logcat:
http://pastebin.com/t8My7y1K
i love you <3
if there's any way any of us users can help you, please do not hesitate to ask for anything!
bro im newbie, after i move the "bootanimation.zip" to following step above but when i flash the rom it was failed ..? thanks for helping
fksuperstar said:
bro im newbie, after i move the "bootanimation.zip" to following step above but when i flash the rom it was failed ..? thanks for helping
Click to expand...
Click to collapse
what recovery are you using?, if you don't resign the file, it wont work with amon_Ra. We will we be working on a new build today (although it may not be released today) which you wont need to go through these steps to use. Can i also suggest if you're new to this that you flash another rom, as this one is completely unusable and is only meant to show the communitt the stage we are at.
Sent from my HTC Hero using XDA App
JieeHD - The apk's image-files might be mdpi, but they are all located in hdpi-folders, it could be a reason for fc'ing always.. if you install launcherpro through adb you can use that as launcher until other stuff is fixed.. Phone.apk never launches as it is now
EDIT: FC's seems more serious than that...
The problem with the current framework-res and mot-framework-res is that they are not miui , they are from a different rom. Using the original framework the rom will just not boot, which is why the apps f/c, as they are dependent on the miui framework.
JieeHD said:
The problem with the current framework-res and mot-framework-res is that they are not miui , they are from a different rom. Using the original framework the rom will just not boot, which is why the apps f/c, as they are dependent on the miui framework.
Click to expand...
Click to collapse
So what you have used are CM-framework-files?
And which version of Android is it?
mljjlm said:
So what you have used are CM-framework-files?
And which version of Android is it?
Click to expand...
Click to collapse
In the next build (which is being compiled atm) , the framework's are miui ones, check changelog
Android OS: 2.2.1
Hmm.. Are you sure that you have enabled /data/app-functionality in the latest (0004)?
I couldn't boot, and the logcat said that /data/local/bootanimation.zip wasn't found, when I looked through the updater-script I didn't find the command for extracting the data-folder to the data-partition?
i think you may be right because i switched scripts from a cm6 rom which stores the boot anim in system/media
Also, I'm wondering why the bootanimation.zip can't be in that location.. In the same logcat as before it logged that it was searching both in the /data/local- and in the /system/media-folders..
mljjlm said:
Also, I'm wondering why the bootanimation.zip can't be in that location.. In the same logcat as before it logged that it was searching both in the /data/local- and in the /system/media-folders..
Click to expand...
Click to collapse
i just removed it for organisation
JieeHD said:
i just removed it for organisation
Click to expand...
Click to collapse
Well.. I just mean in the previous version? Was it because of the other framework-files?
And should there be a ramdisk.tar-file in the /system/bin-directory?
mljjlm said:
Well.. I just mean in the previous version? Was it because of the other framework-files?
And should there be a ramdisk.tar-file in the /system/bin-directory?
Click to expand...
Click to collapse
I think the original update-script looked in data/local and then when we switched scripts it looked in both places, for some reason lol
The ramdisk-tar was in the original rom, so i updated it with our .rc files and left it, it shouldn't cause any problems..
Can you give us a quick guide as to whats working and whats not? Thanks
Imperticus said:
Can you give us a quick guide as to whats working and whats not? Thanks
Click to expand...
Click to collapse
I couldn't get the 0004 to boot, but in 0003, you could run through the setup, and then start over
I am a little confused about the odex and deodex terminology. I am looking at various mods or hacks and I'm afraid I could mess something up because I don't know if I am deodexed or not.
I am on the stock ROM, I flashed chris41's stock kernel repacked with CWM and I rooted by installing zip of su and bb from the market. That is all I have done so far.
With that being said, am I deodexed or odexed?
Thanks in advance
P.S. I did search for the answer but did not find one.
Stolen from matlock and akazabam, rooting guide for dummies
Odexed - 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 applications difficult because a part of the coding has already been extracted to another location before execution.
DeOdexed - 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 the worry 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."
this is an excerpt from the rooting guide for dummies. thanx to matlock and akazabam. its their words and not mine.
I think most stock roms are odexed...
Thanks for the info, that helps me not make a big mistake installing the hotspot hack and AIO mod.
What you will need:
Basic tools
- Notepad++
- ZIP manager tool like 7zip
Advanced tools
- Cygwin
- smali (assembler/disassembler)
- APKTool/APK Multi-tool
Lets Begin:
Download a ROM (we use CM in this guide) of your choice (don’t forget to get the permissions for it modding from the developer) and extract it. When you extract it, you will see at least two folders and one file
Folders
- system
- META-INF
Files
- boot.img [this is not present in defy/defy+ ROMs so don't worry about it ]
NOTE THAT I AM ONLY GIVING DETAILS ABOUT THOSE FOLDER WHICH YOU CAN REMOVE/EDIT
THE \system\bootmenu\2nd-boot\ FOLDER
In this folder you'll find the kernel [zImage] file of the ROM here you can change it with the one you compiled or by others.
The Tts folder
The ‘TTS folder’ is all about Text-To-Speech. It contains all the files needed by the Android system to get Text-To-Speech working. If you are removing the TTS feature from your ROM, make sure you remove this entire folder and the TTS related apps from the ‘system folder’, as this will save a lot of space.
The WiFi and Usr folders
The WiFi folder contains the drivers required by the WiFi module to function. So i strongly recommend NOT to touch this folder. If you delete any file from this folder, you will mess up the WiFi functionality.
The usr folder contains some miscellaneous but very important stuff. It may contain anything and everything needed by the Android operating system. For instance, this folder contains all the key-mapping. If such files are messed with, your device will be non-functional although it will boot.
The Build.prop
The build.prop file is pretty self-explanatory. Here, you can change the most basic things, like the android version that setting shows. Wondered how people are making 2.3.4 look like 4.0.3 in settings? Its build.prop. Also,you can change what ‘About phone’ shows here.
Other things,you can change things like,how long your wifi scans,how much battery your phone saves while in sleep, Dalvik VM heapsize and default ringtones. If you are wondering what # stands for, it signifies that, the particular line is commented out, and the system does not read it. You can use it add comments to the build.prop. This helps others understand, what is the function of a particular tweak.
A guide for some basic build.prop tweaks can be found here.
Please be aware that, these build.prop modifications are not universal. So, you will have to experiment with the tweaks and their values.
The META-INF folder
This folder contains instructions for the Android Recovery about how to work with the files present in the zip. This folder contains many folders, but the only one we need to edit is the update-script file.
Making Flashable ZIP
In order to create a flashable zip, first zip the ‘system, META-INF’ folder and the ‘boot.img’. Let’s name this zip as ‘update.zip’. Next we need to sign the zip. Get a signer here. Put your update zip in the same folder as the signer. Then run the ‘signer.bat’ file. This will sign your zip file. After the signing process is complete, you can change the name of the zip to your liking.
confused
hi,,,i'm new here,,,,
after reading ur post, actually i can't do this,,,
and i installed miui v5 rom and always find crashing about "android process stopped."
and i can't edit the rom or make update of it because of no jnderstanding it, but i like miui so far.
so, can u give me the link of miui v5 rom that not crash, in order to me just to instal it without editting.
thx so much.
gwesal said:
hi,,,i'm new here,,,,
after reading ur post, actually i can't do this,,,
and i installed miui v5 rom and always find crashing about "android process stopped."
and i can't edit the rom or make update of it because of no jnderstanding it, but i like miui so far.
so, can u give me the link of miui v5 rom that not crash, in order to me just to instal it without editting.
thx so much.
Click to expand...
Click to collapse
Checkout my miui thread I have already posted the original link there
D5+/cm11/1.2GHz.
Sent from Tapatalk app
coolshahabaz said:
Checkout my miui thread I have already posted the original link there
D5+/cm11/1.2GHz.
Sent from Tapatalk app
Click to expand...
Click to collapse
which one???
is it the official rom from miui site or edited rom you created??
actually its take too long doenloading from official site. but rom i doawnloaded is always crashing android.process.stopped.
gwesal said:
which one???
is it the official rom from miui site or edited rom you created??
actually its take too long doenloading from official site. but rom i doawnloaded is always crashing android.process.stopped.
Click to expand...
Click to collapse
The one I edited had that prob of crashing, n the one on official site is about 240mb ty its taking time
D5+/cm11/1.2GHz.
Sent from Tapatalk app
This is deodexed system part of G900FXXU1BNL2 ROM.
It's for chiefs and devs only and cannot be flashed directly.
Because i don't have S5 device, i cannot test it by myself. So, i'm asking qualified devs with S5 to try to make ROM based on this package and make a report if it can boot or even work.
Some important notes:
1) Because almost all APKs were originally odexed, all of them were required deodexing and then signing. So, original signatures are lost. I've used standard android development test certificate. Usually it's ok for system APK which never update from Play Store (only through ROM updates).
Thus, probably some APKs won't work correctly. You can delete such APK and replace it with one from Google Play store. Btw, Play Store is also resigned and may be won't work with Google servers (need to check).
Also, all resigned APKs won't be able to update in Play Store - so you need to replace such APKs with those from Play Store as well.
2) Following APKs i wasn't able to deodex without errors and not include in package:
Maps.apk
Music2.apk
DocumentService.apk
3) In Android 5.0 APKs having library, they are placed in lib folder of APK sub-folder. While deodexing, i've put these libs inside APKs. Probably, you need to extract these libs and put them all into /system/lib (same as all pre-5.0 ROMs).
4) I've placed APKs similar to pre-5.0 way (not every apk in its own folder). I hope it will work this way. If device won't be able to boot, then place them as in original system structure.
Those, who can build the ROM, please test it and tell me about result.
https://mega.co.nz/#!A4kynJpR!pobkpLuFBAUnhtnUwgJSa2KfT6S8apqWwYD5Asb83DU
Update 1:
- contains only modified parts of system, i.e.: only framework, app, priv-app dirs.
- app and priv-app dirs now have correct structure: each apk in its own dir and lib sub-dir.
- not re-signed, i.e. all apks contain original Samsung or Google certificate
- oops, i've forgot to delete Maps.apk, Music2.apk and DocumetService.apk - they were deodexed with errors and most likely won't work.
https://mega.co.nz/#!1l1BlSza!QN1fNyrU7qtwBu6xqkBRH85h3rL81Rvlc-JZv1OtMeE
Nice build
Sadly im just a normal rom builder with knowledge on v4.4 and below, idunno on v5.0 have to learn it to make good roms out of it
Procedures with 5.0 should be the same. The only difference i've found is placing apks in separate subfolder. I think, it required only for pre-odexed ROMs. So, just need to make an usual ROM, same as 4.4 and then check if it work.
sorg said:
Procedures with 5.0 should be the same. The only difference i've found is placing apks in separate subfolder. I think, it required only for pre-odexed ROMs. So, just need to make an usual ROM, same as 4.4 and then check if it work.
Click to expand...
Click to collapse
Very good than ill give it a try when home
But im not an advanced dev sadly dont expect much [emoji14]
I've tested it out, by putting all your deodexed apk's in their folders of my odexed XtreStoLite 2.0 TW Lollipop BETA ROM (and removed the 'arm' folders), also extracted out the lib files from your apk files, and put them in the 'lib' folder.
And replaced mine framework folder with your deodexed one...
But the phone doesn't boot up then.
So your deodexed files are probably not working.
edgarf28 said:
I've tested it out, by putting all your deodexed apk's in their folders of my odexed XtreStoLite 2.0 TW Lollipop BETA ROM (and removed the 'arm' folders), also extracted out the lib files from your apk files, and put them in the 'lib' folder.
And replaced mine framework folder with your deodexed one...
But the phone doesn't boot up then.
So your deodexed files are probably not working.
Click to expand...
Click to collapse
No log?
edgarf28 said:
I've tested it out, by putting all your deodexed apk's in their folders of my odexed XtreStoLite 2.0 TW Lollipop BETA ROM (and removed the 'arm' folders), also extracted out the lib files from your apk files, and put them in the 'lib' folder.
And replaced mine framework folder with your deodexed one...
But the phone doesn't boot up then.
So your deodexed files are probably not working.
Click to expand...
Click to collapse
logcat would be helpful.
Also you can try it step by step. At first, use odexed framework, and my deodexed APKs in subfolders (use my framework.apk and twframework.apk for certificate match).
Then try to put deodexed APKs into common folder (like 4.4 ROM).
If either of above will work, then try to replace the framework jar files.
It's not exactly because of wrong deodexing. May be you need to keep /arm/boot.* files in order to pass initial boot. And then may be OS will re-create new boot.
So, need to try different combination and look what you get in logcat. May be 5.0 requires some additional steps for deodexed ROMs.
Btw, after extracting libs, don't delete them from APKs.
Just checked CM12 ROM structure:
1) copy each APK in its separate folder (same as stock 5.0 ROM).
2) extract lib to separate lib folder (same as stock 5.0 ROM)
3) all arm folders should be deleted (including framework/arm)
http://www.xda-developers.com/android/deodex-lollipop-system-apps-with-ease/ ???
I've tried to replace some apps by deodexed singly (e.g. SamsungCamera3, SecMms_Candy, TeleService), of course with deleted corresponding arm folder
Unfortunately, none of them work (even completely unmodified), only FC ...
_alexndr said:
I've tried to replace some apps by deodexed singly (e.g. SamsungCamera3, SecMms_Candy, TeleService), of course with deleted corresponding arm folder
Unfortunately, none of them work (even completely unmodified), only FC ...
Click to expand...
Click to collapse
can you provide logcat? FC may be related to incompatible certificate.
sorg said:
can you provide logcat? FC may be related to incompatible certificate.
Click to expand...
Click to collapse
See attachment... logcat while I'm trying to run deodexed SamsungCamera3
_alexndr said:
See attachment... logcat while I'm trying to run deodexed SamsungCamera3
Click to expand...
Click to collapse
I don't see anything about SamsungCamera3 in logcat... If you get FC, then at least FC reason should be shown in logcat.
If it fc post the dumpstate_app_error.txt.gz from data/log rather than taking a log. Guaranteed to include all info
sorg said:
I don't see anything about SamsungCamera3 in logcat... If you get FC, then at least FC reason should be shown in logcat.
Click to expand...
Click to collapse
My mistake. I have not looked at sending and uploaded incomplete file. Now it should be ok
Goldie said:
If it fc post the dumpstate_app_error.txt.gz from data/log rather than taking a log. Guaranteed to include all info
Click to expand...
Click to collapse
This file is also attached
Assuming this permission is in manifest to start with it looks like some issue with actually reading the manifest?
12-12 09:09:30.688 6530 6530 E AndroidRuntime: Caused by: java.lang.SecurityException: Requires SET_ANIMATION_SCALE permission
Goldie said:
Assuming this permission is in manifest to start with it looks like some issue with actually reading the manifest?
12-12 09:09:30.688 6530 6530 E AndroidRuntime: Caused by: java.lang.SecurityException: Requires SET_ANIMATION_SCALE permission
Click to expand...
Click to collapse
While deodexing i didn't touch neither resources nor manifest, only injected dex then signed and then aligned. Probably, because re-signed apk uses different certificate (obviously, i don't have Samsung's private key), OS denies some system level access.
Usually, when i create custom ROM i resign all APKs which use Samsung certificate - thus all system APKs share the same signature and everything works.
Why do you resign all samsung apks? System apps do not require signing unless manifest is changed. Is this something you have always done?
Disabling signature checking may fix this then I guess or not resigning in the first place
Goldie said:
Why do you resign all samsung apks? System apps do not require signing unless manifest is changed. Is this something you have always done?
Disabling signature checking may fix this then I guess or not resigning in the first place
Click to expand...
Click to collapse
No problem, i will update pack with updated structure without resigning.
In my custom ROM i do many changes, sometimes including manifest change and adding additional system APKs imported from other devices or written by myself.
sorg said:
While deodexing i didn't touch neither resources nor manifest, only injected dex then signed and then aligned. Probably, because re-signed apk uses different certificate (obviously, i don't have Samsung's private key), OS denies some system level access.
Click to expand...
Click to collapse
Goldie said:
Why do you resign all samsung apks? System apps do not require signing unless manifest is changed. Is this something you have always done?
Disabling signature checking may fix this then I guess or not resigning in the first place
Click to expand...
Click to collapse
And... this was the cause :laugh:
I've put classes.dex from @sorg 's apk to original SamsungCamera3.apk and it works as deodexed !!!!!!
I will try to baksmali, then modify the code and smali again