lots of people ask... how do you port roms... so here you go... I hope now the thread is started the people posting can help each other as I have other projects working on... Maybe someone learning will help me later with my other roms
lot of chatter of people saying that the structure of my rom is from other x10 so for you all to see I give you basic instructions (that I ported and posted first with almost everything working) so here is all the basics on getting a bootable miui rom for beginners.. first download the formels newest release.
then download a stable gingerbread 2.3.3 version that is compatible with the files. ( I always use the great z and j for sources).
the next step is to get the formels rom ready by deleting the boot image and the data folder. Next step is to go to the etc folder and delete firmware folder... also delete ap2sd init script from the init folder)
then go to lib folder and delete hw and modules.
now it is time to add files. I know the miui files pretty good now so the list has shortened greatly.
now use your stable gb rom source to replace the folders I had you delet above
you may have to change other files depending on the rom i.e. bluetooth/dhcpd and others.
to start in the etc folder you need to add
apns-conf
dbus
dualmic
gps
hosts
hw-config
init.bt
init.gold
init.local
mediaprofiles
mke2fs
profile
resolve
sensors
sysctl
vold
now to the lib folder all files start with lib
cm
dll
dsm
dss
gsl
miscta
oem-rapi
pbmilb
qmi
diag
mmgsdilib
nv
onrpc
queue
ril-qc-1
wms
auth
sdi-exp
wmsts
mmipl
oemcamera
mmjpeg
there are other files but I think that is enough to get bootscreen... if not let me know and I will list the other misc ones.
now the bin files
akmd2
am
bmgr
bmiloader
chargemon
charger
compache
eeprom
fixpermisions
gdbserver
handlecompache
hciqcomminit
ime
input
monkey
pm
port-bridge
qmuxd
recevent
svc
sysinit
updatemiscta
wlanmac
wlantool
wmiconfig
Any dev, or semi-dev can start work this.
COURTESY: http://android.modaco.com/content/s...aco-com/341986/how-to-port-miui/#entry1737792
manju991 said:
lots of people ask... how do you port roms... so here you go... I hope now the thread is started the people posting can help each other as I have other projects working on... Maybe someone learning will help me later with my other roms
lot of chatter of people saying that the structure of my rom is from other x10 so for you all to see I give you basic instructions (that I ported and posted first with almost everything working) so here is all the basics on getting a bootable miui rom for beginners.. first download the formels newest release.
then download a stable gingerbread 2.3.3 version that is compatible with the files. ( I always use the great z and j for sources).
the next step is to get the formels rom ready by deleting the boot image and the data folder. Next step is to go to the etc folder and delete firmware folder... also delete ap2sd init script from the init folder)
then go to lib folder and delete hw and modules.
now it is time to add files. I know the miui files pretty good now so the list has shortened greatly.
now use your stable gb rom source to replace the folders I had you delet above
you may have to change other files depending on the rom i.e. bluetooth/dhcpd and others.
to start in the etc folder you need to add
apns-conf
dbus
dualmic
gps
hosts
hw-config
init.bt
init.gold
init.local
mediaprofiles
mke2fs
profile
resolve
sensors
sysctl
vold
now to the lib folder all files start with lib
cm
dll
dsm
dss
gsl
miscta
oem-rapi
pbmilb
qmi
diag
mmgsdilib
nv
onrpc
queue
ril-qc-1
wms
auth
sdi-exp
wmsts
mmipl
oemcamera
mmjpeg
there are other files but I think that is enough to get bootscreen... if not let me know and I will list the other misc ones.
now the bin files
akmd2
am
bmgr
bmiloader
chargemon
charger
compache
eeprom
fixpermisions
gdbserver
handlecompache
hciqcomminit
ime
input
monkey
pm
port-bridge
qmuxd
recevent
svc
sysinit
updatemiscta
wlanmac
wlantool
wmiconfig
Any dev, or semi-dev can start work this.
COURTESY: http://android.modaco.com/content/s...aco-com/341986/how-to-port-miui/#entry1737792
Click to expand...
Click to collapse
nice dude,some 1 start with it?
Could this guide still be used for porting nowadays?
Anyway, thanks for this usefull information
so it's works ?
This is a very useful guide , thank you.
I've found that a lot of us doesn't satisfied with our current custom ROM. Please don't bully the dev to make a rom with our personal preference. You may follow this guide instead to modify the custom rom to suit with your personal taste. I hope I could make it as simple as possible so all of us so even a new android user could understand. Please make sure you've read this guide throughly before make any modification.
tools:
1. a custom rom (to be customized) or stock rom.
2. 7zip or another similar program
3. apk files
4. dsixda kitchen (not mandatory)
5. apktools (not mandatory)
6. titanium backup (not mandatory)
7. CWM.
First of all, extract your custom rom. You'll see that the custom rom's zip file contain several files and folders. Some of them are common and could be find in almost all custom rom. The files and folders are:
1. meta-inf : contain the script needed to install the rom (don't touch it if you don't understand about scripting nor dsixdia kitchen).
2. system : contain the system files and folder of the custom rom
3. boot.img : the kernel used in the custom rom
4. additional file : (eg:install-busybox, check-data and bmlunlock) additional file contain scripts needed to install additional feature (eg: busybox, additional app in data/app, and install custom kernel) in the custom rom.
If you don't know much about them, don't touch anything but system folder. now, open the the system folder. You'll see a lot of folders and some common files. Leave CSC files and SWconfiguration intact if you don't know about them. You can edit build.prop to insert more build.prop setting or modify the content if you understand how to do it. To change the rom's name, edit the value for 'ro.build.display.id'. You may also change the value for 'ro.build.version.release' to any number like 9.9.9 if you want to show off your modified custom rom
I'll give a quick explanation about the folders in /system.
1. app : contain all the system's app
2. bin : contain the command and bin files for the rom (don't touch it)
3. cameradata : camera files
4. csc : csc files. contain dictionary for the keyboard
5. etc : additional setting and files for the rom
6. font : the fonts
7. framework : system's framework
8. lib : drivers, modules, kernel related files for the rom
9. media : media files-ringtones, notification
10. sd : folder created by a2sd darktremor. (don't touch it)
11. usr : files needed for keyboard, bluetooth, etc.
12. xbin : additional command and bin files (busybox is normally installed here)(don't touch it)
13. T9DB: dictionary and language database for swype and stock keyboard
now, you're ready to customize the rom. I'll divide the guide into several section. pass the section if you don't want to modify it.
DEODEX VS ODEXED ROM. Most of custom rom available is deodexed rom while our stock rom is half deodexed rom. I'll try to explain it in most simple way. First of all, we should understand that mostly every app in android consist of three part, *apk files, *dex/odex files, and lib files.
ODEXED rom means that *dex file needed to run the app is extracted from the apk file and placed in same folder with the apk files (/system/app). the positive side, it consume less internal memory and a execute faster. the negative side, it makes the app uncostumizable (cannot apply custom themes) and need more space in system partition.
DEODEXED rom means that *dex file needed to run the app is extracted from the apk file and placed in /data/dalvik-cache. the positive side, the app can be themed (full customizable) and consume less system partition. we could put more app in /system/app in deodexed rom. the negative side, it consume a lot of internal memory. please be cautious with the internal memory space if you use deodexed rom. (NOTE: if you start from stock rom, you may use dsixdia to convert odexed to deodexed rom).
system app customization is easy. you can add or remove any app in /system/app folder as long as it fit with the space in sistem partition (220MB). if you start from stock rom, please be cautious to not remove essential app from the folder. you may see the app in hybrid rom v.2.1 to see which app is safe to remove or not (the spreadsheet document in this forum is gone. sorry). having ~20mb free space in system partition is a good thing if you want to make the rom more customizable.
Basicly, theme is easily changed by replacing systemUI.apk in /system/app and framework-res.apk in /system/framework. You may put theme from another custom rom or make for yourself from uot kitchen or make it by yourself with apktool. A high modified theme like dysmenorrhea is also modify some part in setting.apk and jobmanager.apk. and another app. Don't forget to delete the *odex file (for all changed app only)from /system/app if you start from stock rom.
NOTE: please be aware with the base firmware of the rom. make sure that systemUI.apk and framework-res.apk files are from exact firmware version. I've found that theme for DXLA, DXLB, DXLC are exchangeable but you can't put theme from DXKL2 to DXLA or the reverse. to minimize any risk, please use themes only from exact same firmware.
Performance tuning could be done in several ways. the easiest (proven works but risky) method is by edit build.prop file. I won't give you all the script. Feel free to search and apply the script with your personal preference. you can found in this forum or just copy from another rom. these script below is used to increase gprs/hsxdpa speed. this script is a common script and proven to be works in a lot of device. (I forgot the original source. sorry)
Code:
ro.ril.enable.dtm=1
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.3g.prefix=1
ro.ril.hsdpa.category=8
ro.ril.hsupa.category=6
ro.ril.hsxpa=2
ro.ril.enable.a53=1
there are also some common tweaks for build.prop file. these are the one I always using in my rom.
Code:
#mod battery kats
debug.performance.tuning=1
pm.sleep_mode=1
video.accelerate.hw=1
windowsmgr.max_events_per_sec=150
ro.ril.disable.power.collapse=1
wifi.supplicant_scan_interval=150
#mod performance
dalvik.vm.execution-mode=int:jit
persist.sys.purgeable_assets=1
dalvik.vm.dexopt-flags=m=y
ro.media.enc.jpeg.quality=100
ro.telephony.call_ring.delay=0
video.accelerate.hw=1
ro.kernel.android.checkjni=0
ro.HOME_APP_ADJ=1
======
the second way, (little bit harder, but its still proven works) by create or modify some file in /system/etc. I'll give you some of them.
1. sysctl script-to increase internet speed.
make a new file in system/etc, name it 'sysctl.conf' (or edit if it already exist). put this script inside.
Code:
net.ipv4.tcp_wmem = 4096 39000 187000
net.ipv4.tcp_rmem = 4096 39000 187000
net.ipv4.tcp_mem = 187000 187000 187000
net.ipv4.tcp_rfc1337 = 1
net.ipv4.tcp_sack = 1
net.ipv4.tcp_fack = 1
net.ipv4.tcp_window_scaling = 1
net.ipv4.tcp_timestamps = 1
net.ipv4.tcp_ecn = 0
net.ipv4.tcp_no_metrics_save = 1
net.ipv4.tcp_moderate_rcvbuf = 1
net.ipv4.route.flush = 1
net.ipv4.ip_no_pmtu_disc = 0
net.core.rmem_default = 524288
net.core.rmem_max = 524288
net.core.wmem_default = 524288
net.core.wmem_max = 524288
its a common sysctl mod for linux based OS (I found it in another mod for another device but I forgot the source). you'll need busybox, and terminal emulator. to run it, type:
'su
'sysctl -p
in your terminal emulator (without ' symbol).
2. GPS mod-to make the GPS lock faster
this mod is based on zeusseuz's guide. please see this page for further information (the script is quite long) http://forum.xda-developers.com/showthread.php?t=1552076
======
the last way...by init.d script. it only works in custom kernel. I won't put any script here. you should find by yourself. you can use make a file in init.d with there script to check if your kernel support init.d script.
Code:
#!system/bin/sh
touch data/kurotsugi_test.txt
set the both init.d folder and the file's permission to rwxrwxrwx (777)
if the script work, you'll find kurotsugi_test.txt in /data.
======
I'll only put the one I've tested and proven to be works.
1. beats audio
this is the old version but doesn't have FC issue. get the file from here http://forum.xda-developers.com/showthread.php?t=1526643
unzip. copy all the files into their respective folder
2. bravia engine
put be_photo and be_movie in system/etc folder then edit the build.prop file doesn't seems work. The real bravia engine mod is consist of
- be_photo, be_movie in /system/etc
- com.sonyericsson.android.SwIqiBmp.xml in /system/etc/permission
- com.sonyericsson.android.SwIqiBmp.jar in /system/framework
my megabassbeat mod contain these files. you can get it from there.
3. boot animation
download or get custom boot animation file from another custom rom or another source. rename it to bootanimation.zip, put it on /system/media.
you may check this out http://forum.xda-developers.com/showthread.php?t=1548479
please note that DXLB rom doesn't support bootanimation. you need to put bootanimation and samsungani files from another rom (like hybrid) in /system/bin and replace all file in /system/lib with lib files from older firmware (DXLA or older)
4. boot sound
make or download boot sound. please make sure the format is *ogg. rename it to poweron.ogg then put it in /system/etc.
5. custom ringtones, notification,
make or download the sound file (in ogg format). put it in /system/media/audio/(respective folder)
6. disable boot animation (for quick boot)
put 'debug.sf.nobootanimation=1' in build.prop.
7. megabassbeats (better than beat bass)
you can get the file from this link http://forum.xda-developers.com/showthread.php?t=1646406. you'll need to copy the files into its respective folder.
If you've done with the customization, enter the custom rom folder. select all the files then create zip file. to install the rom, copy to your sdcard, flash it either by stock recovery or CWM after wipe /data. PLEASE MAKE SURE THAT ALL THE FILES DOESN'T EXCEED THE LIMIT 220MB BEFORE ZIPPED.
This guide can be used if you want to make your own rom. if you start from stock rom, you may use this script (its from myss v.3.4) to install the rom. please make note that it will only install the rom, not the kernel. you'll still need the bin and xbin folder from custom roms in order to make it work.
http://www.mediafire.com/download.php?skw1ytt37mklb4o
All credits for the dev who make the rom, the one I've used the guide here, and all XDA member. no need to say thanks or press it for me. give that to the real dev. I'm just a noob here. Feel free to correct me if I'm wrong.
1. dualboot
this mod actual intent is to make developing a rom a lot more easier without risking our native rom. I was using it a lot when customizing my rom. you can get the original link for dualboot here: http://forum.xda-developers.com/showthread.php?t=1598803 and for a little more detailed step how to use it http://forum.xda-developers.com/showthread.php?t=1600973.
you can find another dualboot kernel here. http://www.mediafire.com/download.php?gkb33aktyf7wbbh
this one have init.d support. all credits goes to irfanbagus
2. data2sd
this mod is used to increase data partition size. you can find the complete guide here http://forum.xda-developers.com/showthread.php?t=1622052[/QUOTE]
I guess you wanted to post this on Galaxy Y Forum But Posted It Here
Nice Guide , but, it's not actually complete.
You have concentrated more on tweaks, and not actually shown how to use the kitchen to create the rom.
masterex567 said:
Nice Guide , but, it's not actually complete.
You have concentrated more on tweaks, and not actually shown how to use the kitchen to create the rom.
Click to expand...
Click to collapse
Why would you want to use a tool that wasn't even meant for Samsung devices in the first place?True,we can use it.But not to a full extent.New users could get bricked phones :silly:
SmOuuK said:
I guess you wanted to post this on Galaxy Y Forum But Posted It Here
Click to expand...
Click to collapse
So will the performance tweaks mentioned here work for Ace too?
Sent from my GT-S5830 using xda app-developers app
Yup..I know that but it's looking at rom cooking..and the kitchen is the only way to easily extract and build roms...well ofcourse you have to change the Meta inf
Sent from my GT-S5830 using xda app-developers app
masterex567 said:
Yup..I know that but it's looking at rom cooking..and the kitchen is the only way to easily extract and build roms...well ofcourse you have to change the Meta inf
Sent from my GT-S5830 using xda app-developers app
Click to expand...
Click to collapse
Yep.But most likely you run into errors.
---------- Post added at 12:12 AM ---------- Previous post was at 12:09 AM ----------
Koogly said:
So will the performance tweaks mentioned here work for Ace too?
Sent from my GT-S5830 using xda app-developers app
Click to expand...
Click to collapse
Most of them.But not all,like DualBoot.
Hmm..yes but that's like the only way available for users to create Roms ryt?
Sent from my GT-S5830 using xda app-developers app
masterex567 said:
Hmm..yes but that's like the only way available for users to create Roms ryt?
Sent from my GT-S5830 using xda app-developers app
Click to expand...
Click to collapse
No...You can do all those things manually...More easily,you can also learn faster if you do it manually
Prawesome said:
No...You can do all those things manually...More easily,you can also learn faster if you do it manually
Click to expand...
Click to collapse
Okkk. I'm actuallly a newbie so i don't know a lot. So forgive me for all those silly questions.
So, you're saying, that a ROM can be built without the kitchen, by using 7zip to extract, and then compile it to a .zip format using this application??
I thought that only the kitchen could successfully compile a rom.
Please correct me if i'm wrong. It will make life a lot easier for me.
Thanks.
masterex567 said:
Okkk. I'm actuallly a newbie so i don't know a lot. So forgive me for all those silly questions.
So, you're saying, that a ROM can be built without the kitchen, by using 7zip to extract, and then compile it to a .zip format using this application??
I thought that only the kitchen could successfully compile a rom.
Please correct me if i'm wrong. It will make life a lot easier for me.
Thanks.
Click to expand...
Click to collapse
original link ?
http://forum.xda-developers.com/showthread.php?t=1590330
masterex567 said:
Okkk. I'm actuallly a newbie so i don't know a lot. So forgive me for all those silly questions.
So, you're saying, that a ROM can be built without the kitchen, by using 7zip to extract, and then compile it to a .zip format using this application??
I thought that only the kitchen could successfully compile a rom.
Please correct me if i'm wrong. It will make life a lot easier for me.
Thanks.
Click to expand...
Click to collapse
Yep...Just zip it
Prawesome said:
Yep...Just zip it
Click to expand...
Click to collapse
Thanks. Saved me alot of work!! I surely owe you big time. Unfortunately I'm still a teenager, so can't buy you a beer or something... But, when I publish my first ROM. You're gonna surely be there in credits.
Moved to General. Please provide link to the original thread or I'll close this one.
Original thread @ galaxy y development section.
Sent from my GT-S5360 using xda premium
Prawesome said:
Yep...Just zip it
Click to expand...
Click to collapse
Ok. Prawesome, I need your help once again. I did as you said..but now i get errors again...
Its a dalvik vm error again:
This time, I didn't touch META-INF. Just modified system and extracted. Modded, then compressed to .zip file and flashed.
Logcat gives me errors:
Unable to find decl for native Landroid/content/res/AssetManager;.splitThemePackageLjava/lang/String;Ljava/lang/String;[Ljava/lang/StringI
Its a W\dalvikvm error. I guess that means that there is a .so file in the lib that needs to be replaced. I extracted the libs from base rom, and copied and replaced them with mine..then added kernel libs..but that doesn't erase the problem.
This particular problem has been bugging me every time i compile. I don't understand what i've done wrong.
Plus, i want to intergrate adrenaline engine. so I just copy data and system to the working folder right? And...The data folder in adrenaline engine has a system \etc..Am I supposed to copy or delete and copy init.d files there?
Thanks.
masterex567 said:
Ok. Prawesome, I need your help once again. I did as you said..but now i get errors again...
Its a dalvik vm error again:
This time, I didn't touch META-INF. Just modified system and extracted. Modded, then compressed to .zip file and flashed.
Logcat gives me errors:
Unable to find decl for native Landroid/content/res/AssetManager;.splitThemePackageLjava/lang/String;Ljava/lang/String;[Ljava/lang/StringI
Its a W\dalvikvm error. I guess that means that there is a .so file in the lib that needs to be replaced. I extracted the libs from base rom, and copied and replaced them with mine..then added kernel libs..but that doesn't erase the problem.
This particular problem has been bugging me every time i compile. I don't understand what i've done wrong.
Plus, i want to intergrate adrenaline engine. so I just copy data and system to the working folder right? And...The data folder in adrenaline engine has a system \etc..Am I supposed to copy or delete and copy init.d files there?
Thanks.
Click to expand...
Click to collapse
To integrate Adrenaline Engine,you should just copy over the required files to their respective directories.I don't have any idea where those errors are coming from,someone else maybe able to help you out with that.My suggestion is,you get a stock rom,don't mod anything,test it first.Then,add mods one by one,testing each of them.This way,you can know where you have caused errors and you can solve it
---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------
masterex567 said:
Thanks. Saved me alot of work!! I surely owe you big time. Unfortunately I'm still a teenager, so can't buy you a beer or something... But, when I publish my first ROM. You're gonna surely be there in credits.
Click to expand...
Click to collapse
lol..I am just 15,just trying to help out where i can
Prawesome said:
To integrate Adrenaline Engine,you should just copy over the required files to their respective directories.I don't have any idea where those errors are coming from,someone else maybe able to help you out with that.My suggestion is,you get a stock rom,don't mod anything,test it first.Then,add mods one by one,testing each of them.This way,you can know where you have caused errors and you can solve it
---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------
lol..I am just 15,just trying to help out where i can
Click to expand...
Click to collapse
Okkk! Will try that. I tried doing all tests on this custom ROM. but none of them seems to fix it. The problem is that all stock roms are uploaded on hotfile. And, downloading from hotfile never succeeds. One more test, is that it definetely not a problem in the kernel, but in something i'm modding. First, i was using miracle v4 as base rom. Same error....after that I used cm7 nightly. Error. and now i'm using cm7 rc1, and Errors. This might sound noobish, but in the dalvik vm error log, what does the splitThemePackage actually mean? Because, i deleted the original default theme, added another one, and set it default in build.prop..could that be the problem?
This is the full error log:
W/dalvikvm( 191): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.splitThemePackageLjava/lang/String;Ljava/lang/String;[Ljava/lang/StringI
W/dalvikvm( 191): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.detachThemePathLjava/lang/String;I)Z
W/dalvikvm( 191): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.attachThemePathLjava/lang/StringI
W/dalvikvm( 191): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.getBasePackageCount)I
W/dalvikvm( 191): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.getBasePackageNameI)Ljava/lang/String;
W/dalvikvm( 191): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.getBasePackageIdI)I
W/dalvikvm( 191): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.addRedirectionsNativeI)V
W/dalvikvm( 191): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.clearRedirectionsNative)V
W/dalvikvm( 191): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.generateStyleRedirectionsIII)Z
E/JNIHelp ( 191): RegisterNatives failed for 'android/content/res/AssetManager'
E/AndroidRuntime( 191): Unable to register all android natives
Thanks for the help.
masterex567 said:
Okkk! Will try that. I tried doing all tests on this custom ROM. but none of them seems to fix it. The problem is that all stock roms are uploaded on hotfile. And, downloading from hotfile never succeeds. One more test, is that it definetely not a problem in the kernel, but in something i'm modding. First, i was using miracle v4 as base rom. Same error....after that I used cm7 nightly. Error. and now i'm using cm7 rc1, and Errors. This might sound noobish, but in the dalvik vm error log, what does the splitThemePackage actually mean? Because, i deleted the original default theme, added another one, and set it default in build.prop..could that be the problem?
This is the full error log:
W/dalvikvm( 191): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.splitThemePackageLjava/lang/String;Ljava/lang/String;[Ljava/lang/StringI
W/dalvikvm( 191): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.detachThemePathLjava/lang/String;I)Z
W/dalvikvm( 191): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.attachThemePathLjava/lang/StringI
W/dalvikvm( 191): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.getBasePackageCount)I
W/dalvikvm( 191): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.getBasePackageNameI)Ljava/lang/String;
W/dalvikvm( 191): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.getBasePackageIdI)I
W/dalvikvm( 191): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.addRedirectionsNativeI)V
W/dalvikvm( 191): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.clearRedirectionsNative)V
W/dalvikvm( 191): ERROR: Unable to find decl for native Landroid/content/res/AssetManager;.generateStyleRedirectionsIII)Z
E/JNIHelp ( 191): RegisterNatives failed for 'android/content/res/AssetManager'
E/AndroidRuntime( 191): Unable to register all android natives
Thanks for the help.
Click to expand...
Click to collapse
No idea....Double check the name of the apk in build.prop, they are case sensitive
Sent from the year 3000 using a SGA where sheep's are not present.
So in build.prop...how am I supposed to set the default theme. I'm using acheps ics theme..so is it supposed to be com.achep.theme.ICSandwich?
Sent from my GT-S5830 using xda app-developers app
I have multiple errors like this
frameworks/av/media/libstagefright/ACodec.cpp:39:24: fatal error: QCMetaData.h: No such file or directory
this file located in hardware/qcom/media/mm-core/inc/ directory
how i can add this directory to include_paths?
if it is to a linux computer, you would add this to your /home/user/.bashrc file <- notice the dot.
export PATH=$PATH:/path/to/whatever/file/you/need
you can add this line below the same line, if you have one like this already.
to test, youc an also type it on the CLI, if it works, and you needed it permanent, then add it to the file mentioned.
no. it not about PATH variable
on UT compilation i have multiple errors like this
frameworks/av/media/libstagefright/ACodec.cpp:39:24: fatal error: QCMetaData.h: No such file or directory
becouce including header file QCMetaData.h locating in hardware/qcom/media/mm-core/inc/ directory that was not in <<includes_directories>>
how i can add this includes directory to each project which include files from it?
i dont want to catch all dependencies. how get it automatics?
ah I see. that's beyond my sys admin knowledge. someone with programming (gcc) skills can help you. Sorry
Hi Maybe this can help http://stackoverflow.com/questions/...odec-cpp-in-android-sources-in-libstagefright
gazhead said:
Hi Maybe this can help http://stackoverflow.com/questions/...odec-cpp-in-android-sources-in-libstagefright
Click to expand...
Click to collapse
nope
I am working on building from aosp 4.4.2. I have built it with the pre-built kernel without any problems. Then, I managed to get a custom kernel code in place and it builds. Now the only thing left to do is the initramfs/ramdisk for the custom kernel I have in place. Currenlty my build will not boot. I suspect it is using the initramfs/ramdisk from aosp.
Can someone point me to the source files or files that handle the initramfs/ramdisk? I have found bits and pieces strewn throughout the source code but cannot pinpoint the indivitual files or the script/mk file that produces the ramdisk found in the out folder after my system finishes building.
I kinow I can change the initramfs/ramdisk manually by repacking the boot.img, but I would prefer everything be completed in the updatpackage.
what device do you have?
Anyways, just decompile the working boot.img with dsixda's kitchen, and replace the zImage, build it again and done
broodplank1337 said:
what device do you have?
Anyways, just decompile the working boot.img with dsixda's kitchen, and replace the zImage, build it again and done
Click to expand...
Click to collapse
I have a Nexus 5. I'm trying to avoid the, "build it again."
I would like to envsetup, lunch, make clean, make updatepackage, flash and done.
So, I'm still trying to figure out, how make knows where to get all the files and create the ramdisk in the out directory.
AOSP radisk
I am no expert but I think this is how ramdisk is built and it worked for me al the time. ramdisk is composed from the directory 'root' in the product build output folder. the contents are coming from different part of the build tree, mostly from the device source, vendor source. for eg:- check hammer head tree for omni https://github.com/omnirom/android_device_lge_hammerhead in the device.mk you can see PRODUCT_COPY entries to the root similar thing goes with vendor makefiles. If you are looking for executable built from source you can set
LOCAL_MODULE_PATH := $(TARGET_ROOT_OUT) so that they will end up in initrd
related to this: I can see using PRODUCT_COPY_FILES to stage files to the root directory. but where is the directory structure created? Such as /firmware ... etc? I am trying to add a directory to the root fs. When I just create a new directory such as /foo the build fails. I want the new directory to be permanent part of the build process so solutions like unpack - modify - repack is less than satisfactory. Thanks