Hi!
Since I brought my Galaxy Nexus I have it rooted and I was always aware of the existance of Kernels and Roms but because stock android was always very satisfatory I've never tried to install anything more than stock roms and some themes in the phone.
Now that Google closed the doors for Galaxy Nexus and we're not getting 4.4 officially I decided to study more about those custom modifications so I need some advices and lessons
What are the best rated kernels? (I only know the name of franco kernel)
What exactly do the custom kernels do to the phone?
How can I install a custom kernel?
What are the AOSP builds? Are they different from the official 4.3 JWR66Y? In what aspects?
Odexed and Deodexed... What is the meaning of that?
How can I decompile & compile apps and/or .jar files?
What is the SMALI code?
Well, I hope you can help me with the basis of Galaxy Nexus "Tunning" :laugh:
Rayaxe said:
What are the best rated kernels? (I only know the name of franco kernel)
Click to expand...
Click to collapse
There is no best. Each one has it's fans. Just make sure the kernel fits the ROM you are planning on running, and that it covers your needs and wants.
What exactly do the custom kernels do to the phone?
How can I install a custom kernel?
What are the AOSP builds? Are they different from the official 4.3 JWR66Y? In what aspects?
Odexed and Deodexed... What is the meaning of that?
Click to expand...
Click to collapse
Not trying to sound like a prick, but all of that should be very well documented at this point. By this I mean, don't be lazy and use search. Some of that is probably in the stickies above this post. Kernels, AOSP, odex vs deodex are all covered super well at this point. If you can't find information on it, you are doing it wrong.
How can I decompile & compile apps and/or .jar files?
Click to expand...
Click to collapse
Those are probably covered as well, but perhaps not as well as the others. Decompiling and recompiling there are tools out there, probably found in theming sections. I am unsure of what options are the best, apktool was what I used a year or so ago. Generally I don't ever have a need to decompile or recompile things.
What is the SMALI code?
Click to expand...
Click to collapse
smali
Related
is this possible?
thank's
piero79 said:
is this possible?
thank's
Click to expand...
Click to collapse
it is possible, someone would need to modify the phone.apk and Contacts.Apk to Skin it, as Far as getting the Miui dialler Functionality. not enturely sure.. MIUI is coming for SGS2 soon though, there is a thread on the development Pages
Edit : heres the link to the ROM in development. http://forum.xda-developers.com/showthread.php?t=1130951
Greenie-UK said:
it is possible, someone would need to modify the phone.apk and Contacts.Apk to Skin it, MIUI is coming for SGS2 soon though, there is a thread on the development Pages
Click to expand...
Click to collapse
Maybe you could even extract the phone.apk from that rom and insert it into your current. Don't know if it is actually possible, but i gues in theory it is...
mbroeders said:
Maybe you could even extract the phone.apk from that rom and insert it into your current. Don't know if it is actually possible, but i gues in theory it is...
Click to expand...
Click to collapse
Doubt that would work, MIUI is based on AOSP firmware and not Samsungs android firmware. As a result doubt the Apks would work, not 100% sure though
Greenie-UK said:
Doubt that would work, MIUI is based on AOSP firmware and not Samsungs android firmware. As a result doubt the Apks would work, not 100% sure though
Click to expand...
Click to collapse
Yeah, that's true, good point. I was thinking of the old Desire days where it was possible to use the MIUI dialer on other (AOSP) roms. I didn't consider differences in the frameworks...
Applications Go Contacts, Go Dialer and Go SMS are very, very similar (some might say too similar). I'm using them till we get MIUI on our beloved sgs2.
Well I was going to create a ROM for the Nitro HD but my phone decided it wanted to hardware brick when I battery pulled, so that plans out the window for a while. While my ROM did work for half of the beta testers without issue, I can't say its safe enough for everyone to flash.
Anyways, this is NOT for flashing. This is for devs to create ROMs from. Its the /system of the Nitro HD on AT&T fully de-odexed. All I ask for anyone using this to please credit me.
This includes all stock applications and bloat, except Google Maps, and Polaris Office. You can pull Maps from Market or another ROM, its universal. I didn't try too hard to de-odex Polaris, theres better office apps anyways.
Download:
http://d-h.st/Zu0
AGAIN, DO NOT FLASH ON YOUR PHONE. ITS ONLY FOR DEVS TO CREATE ROMS
Wonderful. Now devs and themers can do their thing. Nice job.
kernelpan1c said:
Well I was going to create a ROM for the Nitro HD but my phone decided it wanted to hardware brick when I battery pulled, so that plans out the window for a while. While my ROM did work for half of the beta testers without issue, I can't say its safe enough for everyone to flash.
Anyways, this is NOT for flashing. This is for devs to create ROMs from. Its the /system of the Nitro HD on AT&T fully de-odexed. All I ask for anyone using this to please credit me.
This includes all stock applications and bloat, except Google Maps, and Polaris Office. You can pull Maps from Market or another ROM, its universal. I didn't try too hard to de-odex Polaris, theres better office apps anyways.
Download:
http://69.197.181.66/kernelpan1c-nitro-hd-system-deodexed.zip
AGAIN, DO NOT FLASH ON YOUR PHONE. ITS ONLY FOR DEVS TO CREATE ROMS
Click to expand...
Click to collapse
Also want to thank you for the effort... You should see about getting one of those donate buttons put up - I am sure there are some of us who would be happy to help defray any repair costs that you may incur as you forge ahead.
Thank you for this i'll be working with this base.
schwin97 said:
Also want to thank you for the effort... You should see about getting one of those donate buttons put up - I am sure there are some of us who would be happy to help defray any repair costs that you may incur as you forge ahead.
Click to expand...
Click to collapse
Done. Thanks for the thought
kernelpan1c said:
Anyways, this is NOT for flashing. This is for devs to create ROMs from. Its the /system of the Nitro HD on AT&T fully de-odexed. All I ask for anyone using this to please credit me.
Click to expand...
Click to collapse
Revolution said:
Thank you for this i'll be working with this base.
Click to expand...
Click to collapse
How did it work out for you?
red_solo_cup said:
How did it work out for you?
Click to expand...
Click to collapse
He made a ROM, its here:
http://forum.xda-developers.com/showthread.php?t=1464921
kernelpan1c said:
He made a ROM, its here:
http://forum.xda-developers.com/showthread.php?t=1464921
Click to expand...
Click to collapse
Hi man, i'm triying to compile the framework but apktool give me so me errors, can help me telling me how you compile this system files?
jamm513 said:
Hi man, i'm triying to compile the framework but apktool give me so me errors, can help me telling me how you compile this system files?
Click to expand...
Click to collapse
I don't have have a straightforward (simple) answer to that. Some of the frameworks have dependencies, you just need to make sure they are included. I spent time figuring out what dependencies were needed.
If your building a ROM for the LG Nitro HD on AT&T, your welcome to use the files from the first post. All I ask for is a one line credit.
How one deoxed a rom?
I've tried xUltimate, but it chokes on qcnvitems.jar and qcrilhook.jar
[email protected] said:
How one deoxed a rom?
I've tried xUltimate, but it chokes on qcnvitems.jar and qcrilhook.jar
Click to expand...
Click to collapse
http://code.google.com/p/smali/
Yes, those I manually de-odexed.
guys i already read thread about "How to Re-Odex ROMs" but none work for me, maybe i was wrong or else i don't know but i can't Re-Odex custom ROMs
can you guys help me in Re-Odex custom ROMs in windows7? (Noob friendly guide please) thanks
Syfer_Fever said:
guys i already read thread about "How to Re-Odex ROMs" but none work for me, maybe i was wrong or else i don't know but i can't Re-Odex custom ROMs
can you guys help me in Re-Odex custom ROMs in windows7? (Noob friendly guide please) thanks
Click to expand...
Click to collapse
There is something app like Odex-Me by someone Android.modaco dev??? Try that app..
or use some Android kitchens that have odex option...
Why do you want to odex your rom?
Sent from my Galaxy Nexus using Tapatalk 2
manumanfred said:
There is something app like Odex-Me by someone Android.modaco dev??? Try that app..
or use some Android kitchens that have odex option...
Click to expand...
Click to collapse
i tried Odex-Me app from modaco but not work
you mean dsixda kitchen? i saw on his thread only Deodex option, no re-odex option
geoffcorey said:
Why do you want to odex your rom?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
because i prefer perfomance, odexed ROMs is faster than Deodexed
Syfer_Fever said:
because i prefer perfomance, odexed ROMs is faster than Deodexed
Click to expand...
Click to collapse
False. The only benefit of bring codex is first boot or a clearing of dalvik-cache, and that's only for apps that are odexed. Other than those two situations, you literally cannot tell the difference between odexed and deodexed.
Sent from my Galaxy Nexus using Tapatalk 2
you guys wanna help me? tried this method http://forum.xda-developers.com/showthread.php?t=1500475 i change the BOOTCLASSPATH in odex file and run the script and an error comes, my friend said the CWM can't access ADB. my friend try that method only change BOOTCLASSPATH and run the script and he has Success 100% with his Ace Plus or Ace Duo (i forgot his device)
i use CWM Touch 6.0.1.9
geoffcorey said:
False. The only benefit of bring codex is first boot or a clearing of dalvik-cache, and that's only for apps that are odexed. Other than those two situations, you literally cannot tell the difference between odexed and deodexed.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
sorry for my mistake sir
i just curious how to odex custom ROMs
Hello,
I am learning about rom development, and want some information about porting a rom from one version of the Nexus to another. There are a couple roms that are on the GSM Nexus that I would like to see on the Verizon Nexus. Where can I find documentation on what the differences are between the same rom running on both versions of the phone? Is this just the binaries found on the Google Developer page, or is there more that would be required for porting from maguro to toro?
There's more to it. There's some lib files that might be needed in order for some stuff to work properly. But its real easy tho. Make sure the ROM u want to port is the same android version. So for example u want to port a 4.2.1 ROM make sure your base ROM is also a 4.2.1 like cm 10.1. Then u just copy some files from one ROM to another. So u go into your ROM that u want to port and u open it with 7zip go to system folder and copy app fonts framework and media folder and copy them to your base ROM. Then u go into the lib folder and copy libandroid_runtime.so and paste that into system lib folder of your base. Then it should work. That would be the basic way of doing it. As far as building from source I can't help u there lol. Good luck.
Sent from my Galaxy Nexus using xda premium
Ok, how do I know which lib files I need? Is there somewhere I can go that says this file does this, this file does that? For example if the camera doesnt work, or if sound doesnt work, how do I know which files are needed for those?
Also, why copy the app fonts framework and the media folder?
Wingdom said:
Ok, how do I know which lib files I need? Is there somewhere I can go that says this file does this, this file does that? For example if the camera doesnt work, or if sound doesnt work, how do I know which files are needed for those?
Also, why copy the app fonts framework and the media folder?
Click to expand...
Click to collapse
Because the framework folder has all the mods from the ROM. As far as camera u don't have to worry about that since they are both the same phone. The only lib file u need to change is the one I mentioned. That's the one that usually will give u a problem booting up. But that's what I was told u need to change and it works.
Sent from my Galaxy Nexus using xda premium
Is there a place that documents what all of these files do? I am trying to go a couple levels deeper than just "Do it because it works". I am hoping to find a place that will explain why, so I can track down bugs when they pop up.
Wingdom said:
Is there a place that documents what all of these files do? I am trying to go a couple levels deeper than just "Do it because it works". I am hoping to find a place that will explain why, so I can track down bugs when they pop up.
Click to expand...
Click to collapse
I see. I'm not to that level yet. Try Google search or maybe even YouTube see if u find something. I do know u will need knowledge on how to use adb so u can do logcats when errors occur. Good luck man.
Sent from my Galaxy Nexus using xda premium
Alright, I got the rom to boot, but I am not getting any signal or wifi. What files do I need to get these working? I want specifics, not copy over all files in a single folder, because I dont want to lose any of the customization already in the rom.
I once ported a version of minco to Toro before there was an official version. I figured out which files to swap by comparing file by file two roms - one maguro one Toro. Any file that was divergent file size got swapped except systemui.apk and frameworkres.apk. I used two bugless beast roms as a base. It worked perfectly.
Wingdom said:
Hello,
I am learning about rom development, and want some information about porting a rom from one version of the Nexus to another. There are a couple roms that are on the GSM Nexus that I would like to see on the Verizon Nexus. Where can I find documentation on what the differences are between the same rom running on both versions of the phone? Is this just the binaries found on the Google Developer page, or is there more that would be required for porting from maguro to toro?
Click to expand...
Click to collapse
There are hardly any differences. I looked at it a lot when the jelly bean developer preview was released for gsm devices and I 'ported' it for toro. I had a list of the differences, but apparently lost it. I want to say that there are only 10-15 differences. The way I found out what the main differences were was by comparing the same build of CM for toro and maguro using Beyond Compare using a binary comparison. Some files may be different, but if you compare the bits directly...you can sometimes see it's only a build date/time and not a real difference.
edit 1 - To try to answer some of your questions, try libsec-ril_lte.so and libsecril-client.so (and the apn stuff listed below) for signal AND bcmdhd.cal and bcm4330.hcd for wifi. For camera, I think I remember fRom being needed. For GPS, you'll want sirfgps.conf, gps.omap4.so, gps.conf, and lib_gsd4t.so from toro.
edit 2 - Ahhh, I found a post where I listed the difference between maguro and toro that I found (it may not be all inclusive, but it should give you a good start!). These were from the CM roms, so toro factory images have a couple more things like MyVerizon.apk, VerizonSSO.apk, VZWBackupAssistant.apk, and libmotricity.so (needed for VerizonSSO.apk).
Code:
\system\app\BIP.apk
\system\app\RTN.apk
\system\app\VZWAPNLib.apk
\system\app\VZWAPNService.apk
\system\etc\gps.conf
\system\etc\permissions\android.hardware.telephony.cdma.xml
\system\etc\permissions\com.vzw.vzwapnlib.xml
\system\etc\permissions\com.vzw.hardware.lte.xml
\system\etc\permissions\com.vzw.hardware.ehrpd.xml
\system\etc\wifi\bcmdhd.cal
\system\etc\apns-conf.xml
\system\etc\NOTICE.html.gz
\system\lib\hw\gps.omap4.so
\system\lib\lib_gsd4t.so
\system\vendor\etc\sirfgps.conf
\system\vendor\firmware\bcm4330.hcd
\system\vendor\lib\libsec-ril_lte.so
Thank you! That is exactly what I was looking for. I do have one more question. How is a power menu (hold power button to get reboot, recovery, hotboot, etc..) added to a rom?
Wingdom said:
Thank you! That is exactly what I was looking for. I do have one more question. How is a power menu (hold power button to get reboot, recovery, hotboot, etc..) added to a rom?
Click to expand...
Click to collapse
You have to modify the android policy jar in framework from code. There is a modded jar in the apps and themes forum, or you could try and lift the file or of your favorite custom ROM, like cyanogenmod.
Wingdom said:
Thank you! That is exactly what I was looking for. I do have one more question. How is a power menu (hold power button to get reboot, recovery, hotboot, etc..) added to a rom?
Click to expand...
Click to collapse
Glad to see you have some initiative! If you want the .smali edits for the advanced power menu, I have attached a .zip containing the comparison of the mod for my 4.2.1 stock AOSP rom. You need to add the 3 GlobalActions$11xx.smali files (in the attached .zip) to \smali\com\android\internal\policy\impl when you decompile your android.policy.jar with apktool. The 2 .pdf's show the smali edits to the 2 files that need modified. There are just a few lines added/changed. The changes for GlobalActions.smali are on page 19 of the .pdf. If you need a working apktool for 4.2.1, you can get one the I compiled using paulobrein's patch HERE.
I'm glad to see people helping a fellow who whats to turn user-to-dev.
Sent from my Galaxy Nexus using Tapatalk 2
Wingdom said:
Alright, I got the rom to boot, but I am not getting any signal or wifi. What files do I need to get these working? I want specifics, not copy over all files in a single folder, because I dont want to lose any of the customization already in the rom.
Click to expand...
Click to collapse
Try flashing the radios. Here is a link: http://forum.xda-developers.com/showthread.php?t=1890585
Wingdom said:
Alright, I got the rom to boot, but I am not getting any signal or wifi. What files do I need to get these working? I want specifics, not copy over all files in a single folder, because I dont want to lose any of the customization already in the rom.
Click to expand...
Click to collapse
I know this is old but... How did it go?
I was trying to port cm-Resurrection_Remix_LP_v5.3.9-20150319-maguro to toro by comparing Resurrection_Remix_KK_v5.1.5-20140609-toro with that maguro but CM12 structure and format is completely different than KK...
Hi there!
I've been looking at this for some time now. Would it be possible to transfer the messaging and contacts apk's from 4.1.2 JB Samsung rom to a CM10.1 based rom?
The two files that I would like, are SecMMS.apk and SecContacts.apk
I've tried to get them on my phone, to no avail. Currently running JellyBam 6.5.0 with CWM kernel.
I could not find any threads about this, or atleast none that worked for me.
Thanks very much.
Bumping to the top, still searching.
Very interesting, I'm eyeing the topic
Looking forward
cometti said:
Very interesting, I'm eyeing the topic
Looking forward
Click to expand...
Click to collapse
Thanks. So am I.
I've tried flashing many things, to no avail.
xxshabsxx said:
Hi there!
I've been looking at this for some time now. Would it be possible to transfer the messaging and contacts apk's from 4.1.2 JB Samsung rom to a CM10.1 based rom?
The two files that I would like, are SecMMS.apk and SecContacts.apk
I've tried to get them on my phone, to no avail. Currently running JellyBam 6.5.0 with CWM kernel.
I could not find any threads about this, or atleast none that worked for me.
Thanks very much.
Click to expand...
Click to collapse
You'll need phone.apk as well...
And don't think no one will ever do this, because Tw code is VERY embedded in this apk's....but if someone port it wlil be my hero...
ruicc said:
You'll need phone.apk as well...
And don't think no one will ever do this, because Tw code is VERY embedded in this apk's....but if someone port it wlil be my hero...
Click to expand...
Click to collapse
Yes I know it won't be an easy task, but they look so nice!
Hopefully...one day it will happen.