Develop Bugs

[Q] How do you make flashable zips?

I've looked around and can't seem to find a proper guide of how to make flashables I know newer cwm's use an amend script as opposed to the older edify what ever that may mean xD .... anyways I want to start creating my own shiz I don't want to give details but I think it might be kind of special and could interest some nerds anyways if someone can point me in the direction of a proper guide/ tutorial I will much appreciate it.
Sent from my OG Epic

Someone recently asked a similiar questioon. Maybe their thread will help?
http://forum.xda-developers.com/showthread.php?t=1394328
sent from a phone using an app

Figured it was as easy as modifying someone elses zip but wanted to make sure
Sent from my OG Epic

Biggoron said:
Figured it was as easy as modifying someone elses zip but wanted to make sure
Click to expand...
Click to collapse
Often it's as easy as gutting another flashable .zip that you know works, then replacing the directory structure and files with what you want to install. If you want a neater solution with more customization, adamdelozier found benzyniarz1's UpdateZipCreator utility, which provides much more customization possibilities. It currently has a bug that causes scripts to fail, thus causing the entire flashable .zip to fail, but I've let the developer know what's up so hopefully a fix will be out soon. If you want to learn about the bug and the workaround, see pages 5 and 6 and pay close attention to the "Error 6" and "EOL" related posts.

Customization kind of like what the script shows ex: after flashing rc it says your phone is now legendary?
Sent from my OG Epic

Biggoron said:
Customization kind of like what the script shows ex: after flashing rc it says your phone is now legendary?
Click to expand...
Click to collapse
Yes, you can create a custom script from scratch within the utility, and it has the most used commands available to drop into your script, along with a very brief description of syntax for each. Read the OP for the utility to get an idea of its range of features.

AmericanJedi001 said:
Yes, you can create a custom script from scratch within the utility, and it has the most used commands available to drop into your script, along with a very brief description of syntax for each. Read the OP for the utility to get an idea of its range of features.
Click to expand...
Click to collapse
You are the man jedi. Thanks for updating the op also
sent from a phone using an app

Djinn23 said:
You are the man jedi. Thanks for updating the op also
Click to expand...
Click to collapse
Word! Umm, which OP are you refering to? I've updated a couple different OPs this evening, that's why I'm confused!

Thanks as well this is what I did with the knowlegde gained here.
http://forum.xda-developers.com/showthread.php?t=1404886
Sent from my OG Epic

AmericanJedi001 said:
Word! Umm, which OP are you refering to? I've updated a couple different OPs this evening, that's why I'm confused!
Click to expand...
Click to collapse
Yea I typed that knowing it was misuse n abuse. Sorry. I meant the link above I provided to this thread where the people were struggling to find out why it was broken and you explained the bug you linked to here. Jedi's always pop in, save, then boogie. Not choad chomping or anything but I also read your proposal for documentation formatting and lmmfao at your example.
sent from a phone using an app

Biggoron said:
Thanks as well this is what I did with the knowlegde gained here.
http://forum.xda-developers.com/showthread.php?t=1404886
Sent from my OG Epic
Click to expand...
Click to collapse
Awesome. Not my personal cup of tea but I am sure someone somewhere is thinking you are the motts! Well done.
sent from a phone using an app

Most people aren't picky about their cwm zips, basicly it consists of the items you want to flash, the stuff to flash it with, and an updater-script and updater-binary. I usually just take someones updater-binary and write my script from scratch
sent from my always aosp epic

Biggoron said:
Thanks as well this is what I did with the knowlegde gained here.
http://forum.xda-developers.com/showthread.php?t=1404886
Click to expand...
Click to collapse
Interesting... I'm glad you found what you needed!
Djinn23 said:
Yea I typed that knowing it was misuse n abuse. Sorry. I meant the link above I provided to this thread where the people were struggling to find out why it was broken and you explained the bug you linked to here. Jedi's always pop in, save, then boogie. Not choad chomping or anything but I also read your proposal for documentation formatting and lmmfao at your example.
Click to expand...
Click to collapse
Ah, now I understand, my young padawan. Awww, no choad chomping? But seriously, I'm glad I got a laugh out of you! Unfortunately, I'll have to clean parts of it up to get the Mods to sticky it.
Back on topic, the dev of UpdateZipCreator hit me back and said he'll release a fixed version of his utility soon.

UpdateZipCreator has been updated to use UNIX newline / end-of-line / EOL characters in the script generator / editor, which should eliminate "Error 6" when flashing .zips in CWM Recovery.
UpdateZipCreator

AmericanJedi001 said:
UpdateZipCreator has been updated to use UNIX newline / end-of-line / EOL characters in the script generator / editor, which should eliminate "Error 6" when flashing .zips in CWM Recovery.
UpdateZipCreator
Click to expand...
Click to collapse
Awesome too bad I'm headed to bed thanks ill try it out tomorrow. Is this complex or does this generate script or do I have to? That's over my head but yeah...
Edit nevermind took a look at. Any way to change what the binary script displays ie. What it shows in the script when flashing..." your phone is now legendary"
Sent From My Cyan Samurai

Biggoron said:
Awesome too bad I'm headed to bed thanks ill try it out tomorrow. Is this complex or does this generate script or do I have to? That's over my head but yeah...
Edit nevermind took a look at. Any way to change what the binary script displays ie. What it shows in the script when flashing..." your phone is now legendary"
Click to expand...
Click to collapse
This has example scripts, but I don't remember it dynamically generating scripts based on what you install. You must customize the scripts yourself, to include mounting the partition you wish to install to, install package, and screen output. FYI, IIRC the screen is 48 fixed-width characters wide in CWM Recovery. That should help make pretty output screens!

[NS4G-D720][ROM] Stock 4.0.4/IMM76D DEODEX (Error-Free Decompiling)

Contents:
Android 4.0.4/IMM76D deodexed ROM in flashable ZIP format. Will not produce errors when decompiling APK/JAR files.
Includes Superuser and boot.img root-level access. Does not include radio or recovery.
Changelog:
[R1/02APR2012]: ROM base changed from 4.0.4/IMM26 to 4.0.4/IMM76D. Files updated from stock IMM76D listed below.
Updated File List:
system/app/GoogleEarth.apk (v.6.2.1.6363 :: Earth)
system/app/googlevoice.apk (v.0.4.2.54 :: Voice)
system/app/Maps.apk (v.6.5.0 :: Maps)
system/app/Phonesky.apk (v.3.5.15 :: Play Store)
system/app/Wallet.apk (v.1.1-R57v4 :: Wallet)
system/lib/libearthmobile.so
Notes:
The need to wipe data beforehand is dependent on which ROM you're already using, but is advisable when possible for the sake of simplicity.
[R1] http://www.mediafire.com/file/48w84r8v3qbb8bw/NS4G-4.0.4-IMM76D-DEODEX-R1.zip

So does this mean the SystemUI in this version is able to decompile without errors? If so how exactly did you do this?
Thanks.

ssconceptz said:
So does this mean the SystemUI in this version is able to decompile without errors? If so how exactly did you do this?
Thanks.
Click to expand...
Click to collapse
I used smali and allowed each APK to reference all of the .odex files in the framework, added the classes.dex files to their respective APKs, and zipaligned. I don't know if it matters, but I did those steps through the command line, although I'm sure the process would be a lot faster with a script. If you would like the exact line-by-line process that I used, let me know.

So how is this Rom & all I have to do is download & flash it or is there another step to do?
Sent from my Nexus S 4G using xda premium

Killasmoke said:
So how is this Rom & all I have to do is download & flash it or is there another step to do?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
The procedures are the same as for other ZIP-based ROMs: download, transfer to phone, and flash through recovery. You may or may not need to erase your data (depending on which ROM you're coming from), but backing up your data beforehand is advisable and never hurts.
I haven't received any feedback regarding this specific ROM yet (I don't know if that's a good or bad sign). The main difference is that it's deodexed and will decompile without errors. I'm sure there are other threads with more in-depth information on IMM26 changes/improvements/issues.

SuperUser
I was impressed with this rom for the first few minutes I used it. But then I found out that my SuperUser app wasn't working. I tried updating the binaries through the app itself but it couldn't gain root access. I downloaded the file again and flashed it again but SuperUser still didn't work. It was the same problem with not gaining root access. So I flash the SuperUser zip file from zedomax's tutorial on rooting the Nexus S 4G and I was able to gain root access. Just thought I'd tell you.

mvilla, how did you fix the superuser root access problem? i am having the same problem when i try to update binary, and im getting permission error when i try to flash recovery in rom manager, i think is because of superuser not working.

I went to nexusshacks.com and downloaded the nexussrootICS.zip file (I think that's what its called). There's a SuperUser.zip file within that zip file. I moved the file to my phone and flashed it in recovery (wipe cache and dalvik cache of course). And its working well.
Sent from my Nexus S 4G using XDA App

mvilla8 said:
I was impressed with this rom for the first few minutes I used it. But then I found out that my SuperUser app wasn't working. I tried updating the binaries through the app itself but it couldn't gain root access. I downloaded the file again and flashed it again but SuperUser still didn't work. It was the same problem with not gaining root access. So I flash the SuperUser zip file from zedomax's tutorial on rooting the Nexus S 4G and I was able to gain root access. Just thought I'd tell you.
Click to expand...
Click to collapse
Thanks for bringing that to my attention. Uploaded an updated version in the OP that addresses the Superuser issue. Sorry for the inconvenience.
satuday said:
mvilla, how did you fix the superuser root access problem? i am having the same problem when i try to update binary, and im getting permission error when i try to flash recovery in rom manager, i think is because of superuser not working.
Click to expand...
Click to collapse
This update is from ChainsDD's site and has the latest Superuser app and binary. Should accomplish the same thing.

XK72 said:
I used smali and allowed each APK to reference all of the .odex files in the framework, added the classes.dex files to their respective APKs, and zipaligned. I don't know if it matters, but I did those steps through the command line, although I'm sure the process would be a lot faster with a script. If you would like the exact line-by-line process that I used, let me know.
Click to expand...
Click to collapse
Hey buddy, I'd LOVE to have the step-by-step, or line-by-line on the process you used to decompile. If you could PM me, or post it up here for everyone to use, that would be great!! I'm kinda new to the decompiling and compiling scene so any help would be great! Also, you said that most devs that use ICS probably use a kitchen to decompile and compile their .jar and .apk files, where is this kitchen? Or are you talking about Android SDK?

sniperkill said:
Hey buddy, I'd LOVE to have the step-by-step, or line-by-line on the process you used to decompile. If you could PM me, or post it up here for everyone to use, that would be great!! I'm kinda new to the decompiling and compiling scene so any help would be great! Also, you said that most devs that use ICS probably use a kitchen to decompile and compile their .jar and .apk files, where is this kitchen? Or are you talking about Android SDK?
Click to expand...
Click to collapse
Did you ever get that step-by-step process for deodexing ICS from the OP? If so, can you send it to me?

I guess the Google Apps are included?

Will there be any further updates to this in the near future, or has this reached the end of the line so-to-speak? Just curious because I like having the natural AOSP of this.

Been using this since the 9th and I have to say it's very smooth. Very stock too, which obviously is what it's supposed to be. Just saying that for anyone who comes in looking for something customized. This is basically pure vanilla ICS.

Sorry for the delayed replies. I've been hammered by other obligations lately.
sniperkill said:
Hey buddy, I'd LOVE to have the step-by-step, or line-by-line on the process you used to decompile. If you could PM me, or post it up here for everyone to use, that would be great!! I'm kinda new to the decompiling and compiling scene so any help would be great! Also, you said that most devs that use ICS probably use a kitchen to decompile and compile their .jar and .apk files, where is this kitchen? Or are you talking about Android SDK?
Click to expand...
Click to collapse
mabry said:
Did you ever get that step-by-step process for deodexing ICS from the OP? If so, can you send it to me?
Click to expand...
Click to collapse
I'll try my best to post the steps later today or tomorrow. Sorry to keep you waiting.
akabadnews said:
I guess the Google Apps are included?
Click to expand...
Click to collapse
The stock Google apps are included. There are now two choices: One has the apps that were included in the IMM26 release (R3) and I have also included the latest app updates and related binary files as (R4).
The Batman said:
Will there be any further updates to this in the near future, or has this reached the end of the line so-to-speak? Just curious because I like having the natural AOSP of this.
Click to expand...
Click to collapse
I have replaced the Google apps that have been updated since the IMM26 release. There are rumblings that the official ICS ROM should be released sometime soon. I'm not holding my breath, but I'll offer the same thing to that release once it comes out.
If you're asking about adding functionality or features, I don't think I'd have anything unique to offer since there are so many other ROMs and customizable updates out already. I have considered including FaceLock functionality, but it adds quite a bit of size to the ROM and honestly, it hasn't worked very well for me. If there is enough interest, I'll include it as a separate revision in the future.

I'm getting a error for the media fire links. New link please?
Sent from my Nexus S 4G using xda premium

xamadeix said:
I'm getting a error for the media fire links. New link please?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Sorry about that. I don't know what happened there. Link fixed.

XK72 said:
Sorry about that. I don't know what happened there. Link fixed.
Click to expand...
Click to collapse
Thank you
Sent from my Nexus S 4G using xda premium

Does anyone have problems turning Bluetooth on?
Sent from my Nexus S 4G using Tapatalk

XK72 said:
I have replaced the Google apps that have been updated since the IMM26 release. There are rumblings that the official ICS ROM should be released sometime soon. I'm not holding my breath, but I'll offer the same thing to that release once it comes out.
If you're asking about adding functionality or features, I don't think I'd have anything unique to offer since there are so many other ROMs and customizable updates out already. I have considered including FaceLock functionality, but it adds quite a bit of size to the ROM and honestly, it hasn't worked very well for me. If there is enough interest, I'll include it as a separate revision in the future.
Click to expand...
Click to collapse
I would rather have the straight vanilla experience. Thanks for responding.
Edit: Also, touch to focus would be nice for the camera if at all possible. Thanks.

[ROM][.45][OC]PowerXperia

Ok, I really should contribute to the community somehow So I decided to fix any little problem in my rom i'm currently using and release it, so people like me, that means people who like clean and tidy ROMs with some extra horsepower under the hood and few tweaks that increases usefulness of their device a bit will have their life a little bit easier because I'll try to implement as much awesomeness without unnecessary bloatware to this ROM and learn a bit about modding in the process
And I proudly present you PowerXperia ROM for Xperia S
It's based on official .45 ROM, with following changes:
StatusBar toggles
Percentage battery mod
^ these two were one mod, p3001ee's statusbarmod with quickpanelsettings.
krabappel2548's XperiaSSpeed Kernel V6 with stock bootlogo and "Xperia" background in recovery
serajr's xperia s customizable home launcher
ROM is debloated and some handy apps are included
Click to expand...
Click to collapse
Known issues & TODO:
- When lockscreen disabled and waking up phone with camera button, blank form appear that is canceled by any action. This is caused by Camera app.
- AROMA installer - honestly, i am aware that apps I use aren't apps that everyone want to use
Click to expand...
Click to collapse
Feel free to post suggestions/critic/bug reports/giving thanks etc.
Feel free to mirror, just let me know, ok?
DISCLAIMER: I am not responsible for any damage caused to your phone. You are using this at your own risk, and if you are not willing to take it, do not proceed. Please read carefully all the information below, It's wise to prevent problems...
Installation process:
This is currently standard recovery flashable ZIP file. If you do not have access to recovery you may want to read this thread: http://forum.xda-developers.com/showthread.php?t=1793272 there are several ways how to boot into recovery, you may use any method, the recovery will be reflashed anyway. This rom also requires unlocked bootloader.
1) Place installation package anywhere on your internal card.
2) Boot into recovery (usually with pressing vol up button when prompted by kernel)
3) Select install zip from sdcard.
4) Select choose zip from sdcard
5) Find installation package on SD Card and confirm installation
6) Wait until updater finishes his job and wipe cache partition or (optional) perform hard reset.
7) Profit
Click to expand...
Click to collapse
First boot takes a lil bit longer, don't be scared
DOWNLOAD:
Uloz.to
uploaded.to
(will add some more mirrors soon)

reserved

ladynaamah said:
Ok, I really should contribute to the community somehow So I decided to fix any little problem in my rom i'm currently using and release it, so people like me, that means people who like clean and tidy ROMs with some extra horsepower under the hood and few tweaks that increases usefulness of their device a bit will have their life a little bit easier because I'll try to implement as much awesomeness without unnecessary bloatware to this ROM and learn a bit about modding in the process
And I proudly present you PowerXperia ROM for Xperia S
It's based on official .45 ROM, with following changes:
Known issues & TODO:
Feel free to post suggestions/critic/bug reports/giving thanks etc.
Feel free to mirror, just let me know, ok?
DISCLAIMER: I am not responsible for any damage caused to your phone. You are using this at your own risk, and if you are not willing to take it, do not proceed. Please read carefully all the information below, It's wise to prevent problems...
Installation process:
First boot takes a lil bit longer, don't be scared
DOWNLOAD:
Uploading in progress... stay tuned
Click to expand...
Click to collapse
Good to have another rom... But this is more like a combination of some mods that you have done on your stock rom with krabe's kernel and made it a power rom...
Anyways one new rom for us.. Cheers
Edit : you already told these in the beginning.. My bad
Use the thank button, it's there for a reason
Sent from my LT26i using xda premium

exciting stuff!! Btw, is it overclocked by default??

Harsh7689: The point of this ROM is to ease the effort patching it up to others with similar requirements from their device. I've not said that I have done something special, I don't know java and I know very little from bash and other scripting... only thing I've learned up to today is to find a mod, test it and if it works well use it until i find better. This is my little I can do for the community... Maybe I'll learn from this baby-in-sandbox project something that will allow me to do a bit more for community than this... I agree, it's nothing much fancy, but it might help someone, that's why I posted it here.
imrock: It's kernel is krabappel2548's XperiaSSpeed Kernel V6, so yes, it is overclocked by default and can be overclocked up to 1899 MHz, which me personally finds quite hazardous Anyway default overclock is somewhere around 1,7 GHz which is safe value The package also contains Voltage Control free edition, which will allow you to alter those values to your taste

ladynaamah said:
Harsh7689: The point of this ROM is to ease the effort patching it up to others with similar requirements from their device. I've not said that I have done something special, I don't know java and I know very little from bash and other scripting... only thing I've learned up to today is to find a mod, test it and if it works well use it until i find better. This is my little I can do for the community... Maybe I'll learn from this baby-in-sandbox project something that will allow me to do a bit more for community than this... I agree, it's nothing much fancy, but it might help someone, that's why I posted it here.
imrock: It's kernel is krabappel2548's XperiaSSpeed Kernel V6, so yes, it is overclocked by default and can be overclocked up to 1899 MHz, which me personally finds quite hazardous Anyway default overclock is somewhere around 1,7 GHz which is safe value The package also contains Voltage Control free edition, which will allow you to alter those values to your taste
Click to expand...
Click to collapse
Truly said +1
I know this that's why I thanked you first thank of the rom
Use the thank button, it's there for a reason
Sent from my LT26i using xda premium

Glad you agree uploaded.to mirror nearly ready. Will add it to first post By the way, thanks for thanks

after desperate messing with aroma installer i have another idea how to contribute to community tool that generates aroma scripts

What is the difference between this "ROM"and the other ones like Eratcher and DualCore "ROMS"

It is supposed to be as much stock as possible, while getting some extra functionality, to be honest, i'm not keen using AOSP - themed rom, if i would want to, i'd bought galaxy nexus... i've bought xperia cause i like it's design... by the way, being arrogant and rude is not the best way how to support someone trying to learn something...

Could you send me the kernel only, if possible?
Sent from my LT26i with Tapatalk 2

Felimenta97 said:
Could you send me the kernel only, if possible?
Sent from my LT26i with Tapatalk 2
Click to expand...
Click to collapse
Try the search function...you will also see the kernel dev does not want people mirroring his work...
http://forum.xda-developers.com/showthread.php?t=1761778
Sent from my Xperia S using Tapatalk 2

geekygrl said:
Try the search function...you will also see the kernel dev does not want people mirroring his work...
http://forum.xda-developers.com/showthread.php?t=1761778
Sent from my Xperia S using Tapatalk 2
Click to expand...
Click to collapse
i think he(Felimenta97) is asking for the kernel because ladynaamah has the ka kernel with default sony logo.

You may extract zImage file from archive and flash it via fastboot using command
Code:
fastboot flash boot zImage
provided you have connected your device in fastboot mode
geekygrl: I'm aware of that, but what shall i do? Type here guide how to extract it, modify it, repack it and flash it separately? That's not making much sense, would excessively complicate process that is supposed to be simple...

mharckk said:
i think he(Felimenta97) is asking for the kernel because ladynaamah has the ka kernel with default sony logo.
Click to expand...
Click to collapse
Yeah, exactly. Im using SSpeed v6 right now, but those small customizations seems nice.
ladynaamah said:
You may extract zImage file from archive and flash it via fastboot using command
Code:
fastboot flash boot zImage
provided you have connected your device in fastboot mode
geekygrl: I'm aware of that, but what shall i do? Type here guide how to extract it, modify it, repack it and flash it separately? That's not making much sense, would excessively complicate process that is supposed to be simple...
Click to expand...
Click to collapse
Thanks. I asked for it only as I didn't wanted to download the entire Rom, but I will do it. Thanks
Sent from my LT26i with Tapatalk 2

sorry i can't be of more help currently, I'm at the work right now

Does anyone have the same problem ?
Icon position seems wrong

KennyCHF said:
Does anyone have the same problem ?
Icon position seems wrong
Click to expand...
Click to collapse
Lol funny screen
Use the thank button, it's there for a reason
Sent from my LT26i using xda premium

KennyCHF: It appears on my device too, I'll look into it...

ladynaamah said:
KennyCHF: It appears on my device too, I'll look into it...
Click to expand...
Click to collapse
Thanks ~ wait for your good news ~~~

[Q] Difference Between Toro/Maguro 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...

Oxed vs deoxed.

I try to do a lot of reading and very little talking. However, I have not been able to find an answer to this one question.
What is the difference in an oxed vs a deoxed rom?
I appologize if the has been discussed and explained before, but when I do a search I find a lot of discussions that reference them and nothing that explains their meaning.
Eagles1181
Sent with Tapatalk and my Galaxy S3
Please excuse any tpyos.

Oops. Thought I was putting this in th Q&A section. Can a mod move this for me please? Thanks
Eagle
Sent with Tapatalk and my Galaxy S3
Please excuse any tpyos.

Eagles1181 said:
I try to do a lot of reading and very little talking. However, I have not been able to find an answer to this one question.
What is the difference in an oxed vs a deoxed rom?
I appologize if the has been discussed and explained before, but when I do a search I find a lot of discussions that reference them and nothing that explains their meaning.
Eagles1181
Sent with Tapatalk and my Galaxy S3
Please excuse any tpyos.
Click to expand...
Click to collapse
If you read this thread in the q&a freeza explains it very well.... http://forum.xda-developers.com/showthread.php?p=6 again its about halfway down in the op.
Sent from my SPH-L710 using xda app-developers app

Getting a page that says that is not a valid link. Would tou mind double checking it for me? Thanks
Eagle
Sent with Tapatalk and my Galaxy S3
Please excuse any tpyos.

http://forum.xda-developers.com/showthread.php?t=1910947
Sorry try that one.
Sent from my SPH-L710 using xda app-developers app

Q: Odex and DeOdex. HELP!
A: Well, Odex is what your phone ships with. This is a way to optimize the Dalvik so that it doesn't need to create and/or optimize your system apps/framework. Since it will already be done for you. This does not apply to any apps you install yourself. Those will be optimized by the Dalvik VM automatically. This is generally the best way to go, but is a bit more cumbersome to theme and modify. You can mix and match Odex with DeOdex, but you will need to make sure that you delete any relevant .odex files for anything you install that is tagged only for "deodex" ROMs. For instance, if someone created a battery mod that changes the colors and/or icons of the battery, you will need to delete "SystemUI.odex" before installing it, or it won't work properly, and could even cause FCs (Force Closes) and system instability. Basically, if you are going to go the Odex route, you should stick with Odex mods. This usually is the case for folks who only want a stock rooted ROM and nothing more. DeOdex is what the majority of mods here on XDA and custom ROMs are based on. It makes decompiling, modifying, and changing things much more simpler. This comes with a small performance hit on "first boot" because the Dalvik has to now build entries for system apps. In every day usage you should see no difference between the two after the first boot. You can flash between Odex and DeOdex full ROM versions anytime, and most of the time Android can recognize when a Dalvik wipe is necessary so wiping it yourself isn't necessary, but if you notice any strange issues, wiping it won't hurt.
Courtesy of Freeza from his Q&A
Sent from the future via Tapatalk 4

http://www.talkandroid.com/guides/misc/what-do-odex-and-deodex-mean-the-all-inclusive-explanation/
Basically, the Dalvik Virtual Machine (DVM) is the software that runs the executable applications in the Android operating system. The ".dex" files contain the critical lines of code that are required to run the app. If it was explained to me correclty, the DVM, when running an app, looks for the ".apk" file along with the Dalvik Executeable file, or ".dex" file. The "dex" file goes first since it contains the critical command lines, and then if the app requires, the DVM looks into the "apk" file for the rest of the commands or code.
In a "deodexed" rom, the developer has deleted the "dex" file and instead compiles the "apk" file with the critical commands on top; this process is called "zipalign'. The "zipaligned" configuration replaces the "dex" file with an "apk" file that is optimized by design for the DVM to read. Thus, the modificaiton of the rom by use of mods or themes is easier with a deodexed rom since there is no second "dex" file that also needs to be themed.
The answer as to which version is better is like asking someone if Chevy is better than Ford; you will get as many opinions as you get answers.
If I am mistaken or have misspoken anything, please; someone who is smart (like a developer) please chime in and edumacate all of us! I only repeat what I hear (kind of like my teenage daughter).

orlzzt said:
...
If I am mistaken or have missp... the purpose of why it was introduced.[/hide]
Click to expand...
Click to collapse

Thanks for the info.
Eagle
Sent with Tapatalk and my Galaxy S3
Please excuse any tpyos.

Thread moved
And a simple Google would get you the answer a lot quicker. There is lots of info on the net. And it is Odexed vs. Deodexed

CNexus said:
Just a correction, it's an ".odex" file that matches up with each apk. Odexed apks contain a classes.dex inside the app, and an odex file that pairs up with them. Deodexed apks contain a single classes.dex file that is basically a conglomerate of the original classes.dex and <appName>.odex.
As for my take on this, I will simply say that some believe odexed roms to be hundreds of times faster...but this is not really true. Deodexed roms get optimized on the first boot, so the majority of that difference is made up already made up for. Yes, it odexing an app CAN make your system a little faster, but not by very much or a whole lot.
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.
Click to expand...
Click to collapse
Thank you, C-Nex! I think 99.9% of people polled have said that the difference in speed is negligible. Nevertheless, Android is about choices and we Android users can choose for ourselves whether we want to use an Odexed versus a Deodexed rom. And we have brilliant developers like @strongsteve, who have spent literally hundreds of hours of their lives theming and creating roms in the Odex platform so that we users can continue to exercise our "Freedom of Choice" in this matter (and many others...)
:good::good::good::good::good::good::good: