Develop Bugs

[Not Possible] HTC Hero GSM: MIUI Port Alpha 0004

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

[Q for Theme development] Multiple lockscreens with JVS framework

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 ...

[Q][CM9b1]Live Wallpaper picker.apk for my rom?

Hi, I'm using cm9 beta 1
I noticed that I can't use lwp as I can't find any opt to choose pictures other than from gallery
Then I found out that i dont have livewallpaper picker.apk
So, I found many lwp picker apk but I'm not sure which one is compatible for my rom
Could you help me to give me the compatible one?

eSPeWe said:
Hi, I'm using cm9 beta 1
I noticed that I can't use lwp as I can't find any opt to choose pictures other than from gallery
Then I found out that i dont have livewallpaper picker.apk
So, I found many lwp picker apk but I'm not sure which one is compatible for my rom
Could you help me to give me the compatible one?
Click to expand...
Click to collapse
Download .apk
Move to /system/apps
Set permissions to rw-r--r--
Reboot
This might do the trick

Why not flash the latest version B4 is already out try it i am sure it is better

wow sorry for such a slow response
yeah it works! HOORAAAYY!!!
thank you guys! Now I can use my new cosmic flow lwp for my galaxy wonder

It works
cycloneblast said:
Download .apk
Move to /system/apps
Set permissions to rw-r--r--
Reboot
This might do the trick
Click to expand...
Click to collapse
cycloneblast's method works. Finally happy with custom roms where live wallpapers didnt worked.

Thanks Cycloneblast I was able to fix my LWP error. My alternate process below:
How to fix - unfortunately live wallpaper picker has stopped.
1. Backup and Uninstall the system
-Live Wallaper Picker-
{livewallpaperspicker.apk}
ONLY (NOT livewallpapers.apk) with -Lucky Patcher-(you need to enable system files in Lucky Patcher) or some other App like that (you don't need to uninstall any already installed live wallpapers).
2. Download many livewallpaperspicker.apk you can find all over the internet (including the one in this thread by <cycloneblast>) for different Android versions(doesn't matter even if the version is not specified, download anything you can).
3. Install the livewallpaperspicker.apk for the Android version you are running.
4. If it still says unfortunately live wallpaper picker... then Install other versions and test them(you don't need to restart your device).
5. If stil not working, then remove odex file of the Live Wallpaper Picker with Lucky Patcher and then repeat steps 3 and 4.
6. If STILL not working then remove corpses with -SD Maid-(you need to enable system files in it's settings first which is usually turned off when you install it). WARNING: Use this at your own RISK.

with that livewallpaperpicker don´t woks for me. i put another one the 4.4 (for kitkat) and works really fine. with live wp again.

[NST/NSTG] Multilanguage and modified Settings.apk for 1.2 firmware

For NST/NSTG with 1.2 firmware​
Hi, new NTSG owener here
After reading this thread I've decided to make similar mod for 1.2 firmware.
NOTE: this was tested on rooted 1.2 firmware on NSTG but should work fine also on NST
Modifications in framework-res.apk:
-added languages: the same as in original mod
-replaced some images: by default not-localized ones had ugly "X" painted on top, now they look as for English locale
Modifications in Settings.apk:
-all languages are now visible in language picker ( <extra android:name="hideDevLanguages" android:value="false" /> in xml/settings_locale.xml) removed due to SetupWizard incompatibility (com.bn.oobe doesn't like this)
-added Development Options in main menu (changes in xml/settings_root.xml and xml/settings_root_gossamer.xml- first file is for NSTG, second for NST)
-locale picker is present in Development Options
-added Sync & Settings submenu
If you wish to play further with Settings.apk I can recommend this tutorial (it's for ICS but workflow is the same for Eclair).
Downloads:
All files are CWM flashable zips
NSTG-MULTI-1.2.x-flash.zip -modified framework-res.apk
NSTG-settings-accounts-1.2.x.zip -modified Settings.apk
RESTORE_FRAMEWORK.zip -restore stock framework-res.apk
stock-settings.zip -restore stock Settings.apk
Remember to make a full backup before flashing anything​

Updated Settings.apk- now Accounts & Sync is available
NST owners- please post feedback, I can't test modifications on your hardware.
EDIT:
Removed modded settings.apk due to SetupWizard incompatibility, testing alternate solutions
EDIT EDIT:
Modded Settings.apk back online.
BIG FAT WARNING
Settings.apk is deeply tied to other B&N system apps, Setup Wizard will fail with a modded one.
So if you want to use it keep original one around in case of data wipe

PERFECT! just what I wanted.. hey this DOES have Japanese on it right?
as in.. the list that said..
languages with better support by android:
Click to expand...
Click to collapse
EDIT: nope no Japanese... lemme see if I can add it in myself

MadHatterRyu said:
nope no Japanese... lemme see if I can add it in myself
Click to expand...
Click to collapse
Languages were taken from 2.1 Samsung EU rom.
I've used Android Multitool
If you want to add language:
1.Grab a 2.1 rom which has your language onboard, decompile framework-res.apk,
-copy /res/values-[desired language code]/ folder which includes arrays.xml, plurals.xml and strings.xml
-copy /res/raw-[desired language code] folder
2. Decompile Nook's framework-res.apk
-put both previously extracted folders to /res
-copy any of existing /res/raw-XX to /res/raw-[desired language code] -this folder holds localized images
-compile apk
-there will be warning about missing strings in translation- dont' worry, system will use english ones
-copy AndroidManifest.xml file and /META-INF from original framework-res.apk to newly compiled one (apk is a zip)
3. Replace framework-res.apk in a flashable zip and flash it
I'd advise to wipe dalvik-cache after flashing (just in case)
And better don't use modded Settings.apk, language picker can be accessed in Nook Color Tools.
Sorry, I didn't find a way to make modded Settings work in SetupWizard (oobe.apk in reality)
EDIT:
And better check if fonts support japanese

ahead of that.. I just wanted it to recognize Japanese characters.. only had to add ttf files into the fonts folder.
(oddly the stock reader doesn't do that.. meh, I didn't like it to begin with.. I'm using AIreader) but thanks though : )

This looks great! Thanks, @gen_scheisskopf. Due to this mod's being created, I'm now working on my own modified Settings.apk.

ИΘΘK¡€ said:
Due to this mod's being created, I'm now working on my own modified Settings.apk.
Click to expand...
Click to collapse
I'd suggest to take a look at dependencies, AFAIR settings.apk depends on B&N apks (this is most likely why my modified apk only FC-ed when booting system after a wipe)

gen_scheisskopf said:
I'd suggest to take a look at dependencies, AFAIR settings.apk depends on B&N apks (this is most likely why my modified apk only FC-ed when booting system after a wipe)
Click to expand...
Click to collapse
Check. I've got the beta version of my Settings.apk working famously on my NTG - here's the project thread.

[TEST] Android 5.0 deodexed system G900FXXU1BNL2

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