[Q] Compiling ROMs for Mini Pro - Sony Ericsson XPERIA X10 Mini

Greetings, as devs seem do abandon this community quite quickly (and yes, I undersnad why), I'd like to ask, how could one compile his own rom. Ow more precisely, what changes are needed after compiling a clean CM for i.e. HTC Hero or ZTE Blade to make it work on Mini Pro?
Thanks in advance for your answers

Take a rom say AOSP, put compatible drivers and some further tweaks, edit framework, delete/put apps in system/app and make compatible hw_config.sh n build.pro do some more deleting/addind and u'll get a custom rom!

Related

[Q] How to create custom xRecovery ROM for X10

Hi there!
I was wondeing how to create my custom ROM using xRecovery for Xperia?
One thing I don't know how to do is to delete my google account so others have to use their own.
I could'n find any tuto arround.
Any sugestion?
Thx
You could start with modifying existing ROMs. For example:
framework-res.apk
All the apps, you can unpack the .apk's, located in /system/app/ and replace the icons.
services.jar
Much, much more.
After that, you can try making a Nexus One or Nexus S kernel from the AOSP, and if you succeed, try looking up some tutorials.
Please note that for building the AOSP source, you need a 64-bit Ubuntu (or another Linux distro) or Mac. Building on Windows is currently not supported. If you don't have a 64-bit machine, you can still build Eclair ROMs, Froyo and above is 64-bit only.
As for a custom rom, even the experienced devs have only just cracked it, sort of. You can however use the Kitchen to modify and theme an S.E rom with Zdzihu's xRecovery which is what I and others are currently doing.

[Q] Ported ROM (Hero CM6 to X8) Stuck at Boot

First, i want to thank cyanogenmod people for their awesome works, then dsixda for his/her Android kitchen, then XDA people who inspired me to learn about cooking ROM, you guys are awesome
Well, as the title says, i want to port CM6 Hero ROM into Sony Ericsson Xperia X8, i'm using libs from some ROM that are meant for my X8, also using ramdisk that already built in X8's Custom ROM.
Here i attach the adb logcat message when my phone boot, from what i see, there is no problem regarding the booting process of the phone in the log, but hey, i'm newbie, maybe you guys know what is the problem.
Please help me, i want to learn more about Android, well my first attempt is to port this ROM
Thanks before, Regards
aldee_s
Progress = I managed to boot the phone, i found that framework is the problem, some pre-installed application doesnt work, like terminal emulator, then the android keyboard.
How do i disable physical keyboard options in setting?

[REQ] TW Launcher 4 Port

Hello all,
So I remember not too long ago a lot of people were asking for touchwiz 4.
Now it's out and I haven't really seen any steps in porting it to other devices (like ours).
BUT, some people over at the Galaxy S I9000 already ported it to their devices.
So, since we can also run android 2.3.4 now, I was wondering if there was a porter around here interested in porting this.
Here's a Link To the original post at the Galaxy S forum.
I don't have much experience porting other apps (unless I can get the whole source I.E. All the Java files and XML files in original format), otherwise I would have tried it.
Dympy
I think Gaby02 try port this.
Hello
I did not try this one yet, but maybe it works:
http://forum.xda-developers.com/showthread.php?t=1061883
I linked to that post in the OP.
Already tried and didn't work :/
Dympy.
Whoops, sorry did not saw that
Try running it through Chainfire? Or am I talking **** now?
Well graphics aren't the problem.
First of all, it just won't install (Maybe because I'm on Froyo (The manifest file requires a minimum SDK version of 8, so if I'm right Froyo is capable of using it)).
If that problem can be overcome, I think the rest of the porting Would be quite easy.
Dympy.
Try pushing it to /system/app and reboot? Maybe it works then?
the current port of Touchwiz 4 on froyo is for arm v7 devices only....... so i suggest wait till marcellusbe port's cm7 and releases gingerbread AOSP.... cause then only the pngs will have to be converted... i guess......
Installed on cm7 but when I select tw it just gives a black screen with the notification bar :/
Touchwiz 4 is for ARMv7 so for the moment I think it's impossible to use it :S
i have tried all on froyo and on cm7 but no one would start i cant install it and only blackscreen
Probably, this would take an another marcellusbe to port the lib files

[Q] Rom porting - where to begin?

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

[Q] what diferences between compile form source & porting?!

can anyone help me to learn a bit more than android!
I heared about compile form source and biuld form source...And I can't understand what diferences between compile from source and port! can U explain easily?
for example should I want to bring superOxygen Rom in my x10 , should I port it with cm as base or compile form source?!
thx
for short:
porting means you are making rom to your device from another device, you will be just moving libs, editing ramdisk, etc.
compiling from source means you make a complete rom from scratch including programming own drivers, libs in some situations.
If source is avaiable fot superOxygen then you can try compiling it yourself, but editing, or adding your drivers is necessary, and anyway its harder than porting, but gives better result in fact because you can program everything to make it work and you aren't dependant on binary files like in porting.
When porting, hardware should be close to one you have in your X10, because most things will not work when processor differs, wifi modules, gsm etc. You take files from any X10 rom and replace ones that are with same name in another rom (oxygen here).
Thanks very much man!
I took your advices...it was good advices but what is your idea about this:
If I port Superoxygen from Nexus1 for my x10 and (use stable AOSP as base) , then can I say I make a superOxygen Rom?
compiling from source is how much difficult?! I'm 17...! , I have a link that teach compile from source... Is it need some Knowledges that is impossible for me?!
heh, im 17 too and I don't have much knowledge, but looking on pcfighter(a gt540 developer) im impressed, hes 17 too and does a great job, so it depends on time spent and interests
when you port oxygen, you can just say that you ported and not made it. credits go to the maker and you for just making it work on x10
I'm looking now how to compile for gt540 but can't find any idea how to make it strict for gt540 compiling from source tutorials are mostly for nexus s and nexus 4g because most of are just remade of what you can find on official android developer page and its easier. For unsupported device its even harder, you have to work with what you already have and add it first to sources then ... more things to do. I'm beginner with that too, just pulled sources yesterday and looking how to make it work :] so don't expect so much help in this way :]. Just telling you overall how this looks
For compiling you need to know Java and C programing language.
Sent from my Xoom using Tapatalk
@mesaj! do you know c and gava programing languge?! ofcourse I worked c++ a little...
Thanks now I also know what the difference is.
In easy terminology. Compiling a ROM is building a ROM from the source code so it means you are building a ROM from the ground up. Porting a ROM to your phones means to take a ROM built for another phone and to get it working on yours. That's the simplest way to think of it. I have in my signature a guide for compiling a ROM. Oh and I'm newly 18
私のEVO 3Dから送信される。
Thanks for this thread
Thanks now I also know what the difference is.
Click to expand...
Click to collapse
Thanks for this thread
Click to expand...
Click to collapse
just press the thanks button if you like this thread

Categories

Resources