Same probably applies to miui rom.
I want to port Lewa OS to Xperia U, and I have chosen patchrom. Things are going good, but I'm stuck at editing smali. Since I'm not good with smali, I was wondering if someone could help me on that. Basically, I have "reject" smalis, files in which are lines which couldn't be implemented by patchrom. I need to manually implement those corrections, but as I said I'm not very good with smali. I get the general idea, but I'm unable to do it.
In attachment I provided "reject" smalis and smalis in which corrections from rejects needs to be implemented.
Here is an explanation of what needs to be done:
http://forum.xda-developers.com/showthread.php?t=1483332&page=18
I would appreciate any help!
Related
Hello XDA community!
I'm interested in rom porting / developing, but don't know where to begin, and how. I have some C, C++ and Java knowledge (cause I learned to be a software designer and developer), and got some free time, so I want to help in rom developments, if I can. (for example to get Optimus Net rom woriking on our Optimus One)
Could someone give an advice, where to begin to learn these things?
Thank you for every help! And keep up the good work, developers!
Just some suggested ports
-oxygen
-AOSP
-sense
-miui
do you want to develop or customize? these are different things.
for porting a binary compiled rom, you need most knowledge in decompiling code.
for porting real source code, you need most knowledge of C/C++ and JAVA and hardware.
for the first steps, use a ready and running rom and theme it something.
if you want to do really more and have dreams what to do - start developing on
source code - use direct source code from AOSP, CM7 or CodeAurora. Here you need to read
about how the compile process is working, if you have a working and booting rom you can modify
all the software you have or write new
Take a base ROM from another phone. First thing, delete the boot.img. That boot.img contains the kernel, which will not do good to your phone. Next, add the boot.img from your phone to this rom (use commom sense, if you are porting a vanilla rom, use an AOSP kernel, if porting sense, use HTC kernels, if you are porting other UI’s like blur, use an AOSP kernel.) Next, go into the /system folder. In here, we want to first delete the usr folder. The usr folder has hard button and keypad drivers. Replace the usr folder with the one from your phone. Next, go into the etc folder. delete the vold.fstab andapns-conf.xml and replace with the one from your phone. Next, we want to go into the lib folder. Here, we will want to replace the lights.(device name here) (and the sensors.name if it is an AOSP port) and replace with files from your phone
There is currently a patch for true Tablet UI on the Nexus7 Development that has worked successfully. Link is here. The following is a quote from the original thread:
Intro
Goal of thread is to share details around how the trigger for Phone UI/Phablet UI/Tablet UI works, and provide a dpi independent patch for tablet ui. Hopefully this also eliminates the misinformation that changing lcd density is the only way to get Tablet UI.
What's "true" tablet UI vs what is called tablet UI in many roms? The Tablet UI actually defines how some apps work (e.g. dual-paned settings like in the screenshots below) vs the other solutions that simply draw the standard Nexus UI with tablet navigation/system bars.
The 'Triggers'
In 4.1.x, there are two files that need to be modified:
PhoneWindowManager.java, located in frameworks/base/policy/src/com/android/internal/policy/impl contains the code that determines which UI to present. During compile this is a part of android.policy.jar
WindowManagerService.java, located in frameworks/base/services/java/com/android/server/wm contains code that specifies the lowest DP settings and has the system select from either sw600 or sw720 presentations. It is a part of services.jar
Click to expand...
Click to collapse
Basically, I'd like to modify this to work on a 4.2.1 AOSP ROM on the Nexus10 (flashing the Nexus7 patch on the Nexus 10 leads to a bootloop). The OP shows what modifications can be made in his thread so I'm wondering how I can port this to a Nexus10 ROM. I've used APKTool to break down the "android.policy.jar" file and looked through the smali files hoping to simply edit the corresponding lines but I was unable to locate it. Apparently there's more to it than that. Any thoughts on how to create a flashable zip to patch these files?
brGabriel said:
There is currently a patch for true Tablet UI on the Nexus7 Development that has worked successfully. Link is here. The following is a quote from the original thread:
Basically, I'd like to modify this to work on a 4.2.1 AOSP ROM on the Nexus10 (flashing the Nexus7 patch on the Nexus 10 leads to a bootloop). The OP shows what modifications can be made in his thread so I'm wondering how I can port this to a Nexus10 ROM. I've used APKTool to break down the "android.policy.jar" file and looked through the smali files hoping to simply edit the corresponding lines but I was unable to locate it. Apparently there's more to it than that. Any thoughts on how to create a flashable zip to patch these files?
Click to expand...
Click to collapse
haha i saw your post to my rom thread and this is exactly what i tried to do!
the thing is when you decompile precompiled java code you get the assembly and actually have to edit the opcodes. i tried doing that and failed (bootloop). I was so frustrated because i spent like 6 hours for nothing and decided to learn how to build AOSP from scratch. When i succeeded i posted my rom
schnip said:
haha i saw your post to my rom thread and this is exactly what i tried to do!
the thing is when you decompile precompiled java code you get the assembly and actually have to edit the opcodes. i tried doing that and failed (bootloop). I was so frustrated because i spent like 6 hours for nothing and decided to learn how to build AOSP from scratch. When i succeeded i posted my rom
Click to expand...
Click to collapse
Haha, well it was a noob "shot in the dark" attempt on my part. Going to start looking into building from scratch so I can take care of business on my own instead of having to rely on others. I don't mean that in a negative sense, I'd like to be able to contribute to the community one day.
Anyway, thanks for your work, schnip!
is this even possible ? has anyone succeeded in doing this ?
i'm currently trying to compile gallery2 and camera app from the aosp source (it seems they are intertwined)
but having numerous (3k+) errors in the source code..
must be a proper way to get into this
any help would be appreciated.
You must have jar file with class which you need to compile it(which generated with start compile AOSP). Best way is Compile AOSP and get Camera.apk ( in which temat i read this)
Hi to all!
I am new in the Android world and I have a mutimidia car system with Android 2.3.4.
The problem i have is to install new applications available on the playstore like Viago.
This application requires at least Android. I have the Android 2.3.4 ROM soucecode and my doubt is if can i make a compilation of the ROM, to upgrada to Android 4 just modifying the sourcecode of the ROM i have.
Or if can i use any other V4 stock ROM, and add the kernel i have and cook it together.
Thanks in advance.
c_verri said:
Hi to all!
I am new in the Android world and I have a mutimidia car system with Android 2.3.4.
The problem i have is to install new applications available on the playstore like Viago.
This application requires at least Android. I have the Android 2.3.4 ROM soucecode and my doubt is if can i make a compilation of the ROM, to upgrada to Android 4 just modifying the sourcecode of the ROM i have.
Or if can i use any other V4 stock ROM, and add the kernel i have and cook it together.
Thanks in advance.
Click to expand...
Click to collapse
Well, what you could do is modify the AndroidManifest.xml in the apk file so that the minSdkVersion is set to API 10. so it would look like this:
minSdkVersion="resource_id:0x10"
Make sure that the app does not require any features that are not in Gingerbread. I hope this helps.
rcunningham said:
Well, what you could do is modify the AndroidManifest.xml in the apk file so that the minSdkVersion is set to API 10. so it would look like this:
minSdkVersion="resource_id:0x10"
Make sure that the app does not require any features that are not in Gingerbread. I hope this helps.
Click to expand...
Click to collapse
Thanks for your quick response. I have some trouble. When I decompile the apk, i am having some errors and dont know what to do. The apk is fully functional in my s4 mini With Android 4.2. this apk (garmin viago) and apktool are not good friends. Initially there are some errors with .9.png images, i've made the Changes in the AndroidManifest.xml and then a recompiled the apk. The result: More and more errors. The only i want to do is modify the min sdk to 10. I Dont know where to follow.
c_verri said:
Thanks for your quick response. I have some trouble. When I decompile the apk, i am having some errors and dont know what to do. The apk is fully functional in my s4 mini With Android 4.2. this apk (garmin viago) and apktool are not good friends. Initially there are some errors with .9.png images, i've made the Changes in the AndroidManifest.xml and then a recompiled the apk. The result: More and more errors. The only i want to do is modify the min sdk to 10. I Dont know where to follow.
Click to expand...
Click to collapse
Trying to get a apk file from Android 4.2 to work on Gingerbread is hard. Getting a apk from ICS to work on Gingerbread is much more simple. But if you only make changes to the AndroidManifest.xml everything should work. If you have more issues, message me on XDA and I could help you a bit more. I might get marked as spam if I post on this page to much.
Hello, I would like to customize the phone more to my preferences and I would like to edit the systemui etc, I've tried looking for systemui, but just couldn't find it, I am using aosp extended, and when I looked for the systemui.apk in the system folder, its just not there. I used to work a bit with those things a few years back, but I don't know if its different because miui is maybe built differently or just android changed the way files are compiled or anything. Anyway, if someone could shortly explain to me how to edit miui/any custom rom system files, or give me a guide that fits miui, I would really appreciate it, thanks.
anyone pls? :\