Related
Hello, i'm a web developer and have no experience in developing android roms. Anyways, i'm planning to develop a free website which will let any developer create an online kitchen for his rom, where users like me can come and bake rom according to their needs. Now as i don't have any experience with cooking roms, i would like a little help from the developers. Help i am seeking in is, what features a fully customizable kitchen has, how to change the update.zip for the changes, and adding applications to the zip. I have a little bit idea, but want a clear process.
you will get flamed for this
shararti said:
Hello, i'm a web developer and have no experience in developing android roms. Anyways, i'm planning to develop a free website which will let any developer create an online kitchen for his rom, where users like me can come and bake rom according to their needs. Now as i don't have any experience with cooking roms, i would like a little help from the developers. Help i am seeking in is, what features a fully customizable kitchen has, how to change the update.zip for the changes, and adding applications to the zip. I have a little bit idea, but want a clear process.
Click to expand...
Click to collapse
This really is an admirable goal, but you're attempting to bite & chew WAY more than your mouth can handle!!!
You're a web developer, good.
You have no experience in developing android roms, bad.
You want to develop a free kitchen, good.
You have no experience with cooking roms, bad.
You want developers to help you in exchange for a free kitchen for their rom, bad & good.
You don't know how to update the "update.zip" file and re-sign it, bad.
You don't know how to add an APK to the above mentioned "update.zip" file and re-sign it, bad.
You have a little bit of an idea, but want a clearer process, bad.
All of the above noted BAD points, have been discussed, referenced, and linked on these forums countless times shararti.
You really need to search, read, search some more, and apply what you've learned.
I too am a Web Developer/Designer. I've been in the business of creating websites since 1999 (off & on). And the above mentioned project it something I WON'T EVEN DARE ATTEMPT.
Good luck!
I did search, countless times, everywhere. But as lack of my experience with rom development, it was quite confusing. Well I do know signing and adding apk part, and the rest, i agree, i need some help. I'm willing to give my summer to this project and develop this kitchen for the xda community (i'm also willing to give it away to xda). Now if anyone is willing to help me, please pm me.
Actually, it isn't that difficult.
There are quite a few scripts and programs that you could simply employ on your website. I'm sure those developers wouldn't mind
You would have to tier your ROM baking based on the major ROM cores, and the features swappable between flavors of those cores.
It's simply letting the user choose what he wants in his base ROM, pushing the files into the zip, and running the script to sign them.
I'd be glad to guide you in the structure of ROMs, and showing you what can be mixed and matched.
PM me. We'll get started.
Sounds like a very cool idea and I wish you all the best and hope you find some programmers willing to teach you about roms, and you can do the web coding and make your idea a reality.
I'd use it for sure, would be wicked. Imagine going to this web page on your N1 customizing a ROM, building it and then flashing it. All without going near a computer. Sounds unreal!
APrinceAmongMen said:
I'd be glad to guide you in the structure of ROMs, and showing you what can be mixed and matched.
PM me. We'll get started.
Click to expand...
Click to collapse
Perhaps, share the information here once you two have things worked out?!
shararti said:
I did search, countless times, everywhere. But as lack of my experience with rom development, it was quite confusing ...
... I'm willing to give my summer to this project and develop this kitchen for the xda community ...
Click to expand...
Click to collapse
XDA is such a huge resource, full of solutions, bricked devices and lost newbs LOL.
After trolling for a few months, I was ready to flash my first WinMo SmartPhone a few years ago. I haven't used a 'regular phone' ever since.
This would be an ideal summer project. As I said, I'm also a Web Developer.
Hit me up for some theme/template ideas. I do most of my work with Notepad++ and Adobe Fireworks CS4.
Goonish said:
I'd use it for sure, would be wicked. Imagine going to this web page on your N1 customizing a ROM, building it and then flashing it. All without going near a computer. Sounds unreal!
Click to expand...
Click to collapse
hhmm, never thought of that!
You're right ... sounds unreal!
Something the iFans would never be able to attain.
Even better, how about, instead of flashing some large file, only the ones affected by an update are flashed, resulting in a much SMALLER file (thus saving on data usage) and a FASTER flashing (saying on battery life).
shararti said:
Hello, i'm a web developer and have no experience in developing android roms. Anyways, i'm planning to develop a free website which will let any developer create an online kitchen for his rom, where users like me can come and bake rom according to their needs. Now as i don't have any experience with cooking roms, i would like a little help from the developers. Help i am seeking in is, what features a fully customizable kitchen has, how to change the update.zip for the changes, and adding applications to the zip. I have a little bit idea, but want a clear process.
Click to expand...
Click to collapse
Well it all depends on what you want. I would suggest you have a base rom without the boot.img stored with minimal capability in a folder. then allow the user to choose what type of kernel and capabilities they would like with it. That will be the minimum amount for a rom. Then you can follow it up with additions such as extra scripts and applications that can be added and moved to the appropriate directories. at the end, you would zip up the selection and sign it, with the appropriate update-script (which should be the same as the stock rom's unless the additions require something drastic)
So the folder tree should look something like this for one specific ROM:
ROM/ROM Core Files (this is the base rom without boot.img)
ROM/ROM Core Files/META-INF (this is for the update zip)
ROM/ROM Core Files/system (this is where the system apps go)
ROM/ROM Core Files/data (this is where certain apps go)
ROM/ROM Kernels (this is where kernels are/boot.img)
ROM/ROM Kernels/boot.img.1 etc
ROM/Modifications (this is where apps and other mods go)
ROM/Custom Build (this is where the baked rom should go)
Then all you need to figure out is how to move everything to the custom build directory
Move the core to custom directory and a boot.img (rename it from whatever it is to boot.img) and then move and modifications to the appropriate directory inside the custom build folder. Then zip the custom build folder and sign it
That should be about right. its 3 am here lol so i may be missing something. pm me if you need more help or post here
Exactly.
The great thing about it. The ROM core files can be optional. You can bake a kernel or you can bake CM w/ custom kernel and custom mods, i.e. modded phone.apk. You can bake anything and everything.
Mmm baking never sounded so good.
Check this website out:
http://theunlockr.com/2010/03/26/ho...om-for-android-part-1-setting-up-the-kitchen/
My small contribution to this project
The basic kitchen:
forum.xda-developers.com/showthread.php?t=633246
Sorry it's not a link, apperantly new users cannot post links
flybyme said:
So the folder tree should look something like this for one specific ROM:
ROM/ROM Core Files (this is the base rom without boot.img)
ROM/ROM Core Files/META-INF (this is for the update zip)
ROM/ROM Core Files/system (this is where the system apps go)
ROM/ROM Core Files/data (this is where certain apps go)
ROM/ROM Kernels (this is where kernels are/boot.img)
ROM/ROM Kernels/boot.img.1 etc
ROM/Modifications (this is where apps and other mods go)
ROM/Custom Build (this is where the baked rom should go)
Then all you need to figure out is how to move everything to the custom build directory
Move the core to custom directory and a boot.img (rename it from whatever it is to boot.img) and then move and modifications to the appropriate directory inside the custom build folder. Then zip the custom build folder and sign it
Click to expand...
Click to collapse
Ok so after reading it 3 times carefully, this is what i got to:
All roms have same common files, which are:
1. the META-INF folder.
2. the system folder.
3. the data folder.
This is a basic skeleton of any rom, and every rom has these exact files.
Now what i have to do is, when a user cooks a rom, i have to pick the required boot.img and put it into the basic skeleton, in addition to any apps/modifications user want. Then zip the whole package and sign it.
Is that it?
PS: you also said that i may need to change update-script, in what cases that would be required?
PPS: Do i have to make changes to some other files too? cause it sounds too easy to be true =p
shararti said:
Ok so after reading it 3 times carefully, this is what i got to:
All roms have same common files, which are:
1. the META-INF folder.
2. the system folder.
3. the data folder.
This is a basic skeleton of any rom, and every rom has these exact files.
Click to expand...
Click to collapse
They usually have the same folders, not files
the META-INF has the signature files but most importantly the update-script which tells the phone what to do when your flashing the update.
shararti said:
Now what i have to do is, when a user cooks a rom, i have to pick the required boot.img and put it into the basic skeleton, in addition to any apps/modifications user want. Then zip the whole package and sign it.
Is that it?
PS: you also said that i may need to change update-script, in what cases that would be required?
PPS: Do i have to make changes to some other files too? cause it sounds too easy to be true =p
Click to expand...
Click to collapse
that SHOULD be it but remember that you may have to remove some apps from the core files of the rom such as amazon mp3 that people may not want, so you will have to see what apps can be removed and decide whether you want users to be able to remove it or not.
You MAY have to change the update-script if for example you want to put some things in the data partition and symlink them or change the data partition to include the ext partition instead of just for apps. Changes like that are usually for ROMs that are too big to fit properly on the nexus ( youll also have to check the size of the system and data folders to make sure they fit on the phone without modification)
Most of this stuff will be figured out in testing haha but ya at the very basicee its what you have here. You really have to know what you actually want users to be able to cook and then build the kitchen to that effect
flybyme said:
They usually have the same folders, not files
the META-INF has the signature files but most importantly the update-script which tells the phone what to do when your flashing the update.
Click to expand...
Click to collapse
So does that mean i can use same core for all custom baked roms? Except for the update-script, which in rare cases, may need to be altered.
flybyme said:
that SHOULD be it but remember that you may have to remove some apps from the core files of the rom such as amazon mp3 that people may not want, so you will have to see what apps can be removed and decide whether you want users to be able to remove it or not.
Click to expand...
Click to collapse
I took a look at system folder and it's quite populated. Can you tell me what are the basic files that are common for all roms? For the rest of the files, i guess i'll give the user choice to include them or not.
Also can you tell me what is zipalign? Will that be required in baking process?
And to let everyone know, I have already started the working on the kitchen =]
shararti said:
So does that mean i can use same core for all custom baked roms? Except for the update-script, which in rare cases, may need to be altered.
I took a look at system folder and it's quite populated. Can you tell me what are the basic files that are common for all roms? For the rest of the files, i guess i'll give the user choice to include them or not.
Also can you tell me what is zipalign? Will that be required in baking process?
And to let everyone know, I have already started the working on the kitchen =]
Click to expand...
Click to collapse
Well it really depends on what ROM's your looking at. Some devs change the apps to their liking. For example, CyanogenMod has a modified Settings.apk that has features specific to his rom. However, all ROMs have Settings.apk. As such, you will probably have to have a Core ROM folder for each specific rom.
I would suggest looking at other online kitchens and see what features they offer, come up with a specific feature set and then decide what direction that you want to take.
zipalign is a compression technique that optimizes how .apk files are accessed in android. it makes things faster and is not required but would be nice to have. you lose the benefits if you open and modify any files from a zipaligned apk
Let's clear some things up here.
First, core files are not interchangeable between main roms but only flavors of those main roms.
As of now, we have 3 main roms for the nexus one.
CyanogenMod, Modaco Custom ROM, and Desire/Sense Roms.
Each of these roms have their own unique cores amd features and are not interchangeable.
There are flavors of each of these roms.
Flavors of CM has parts that are interchangeable with other flavors but use Cyans core.
Say there is one CM flavor that has some themieing and a few other changes you don't want. You can take the themed files and put them into your CM base and leave the rest out.
You can't put that themeing into a Modaco Custom ROM though.
Kernels I believe are the only things can be put into any ROM base. Most apps are as well.
Now that I look at it. Doing a Nexus One kitchen isn't that difficult but making a full featured HTC kitchen would be a mountainous task. There are so many mods, roms and themes to keep track of. We'd have to designate people from each device forum to feed us the ROMs and parts that are active and functional.
P. S. Lectures are over at 7 today. ill be able to crack down on it with you then
Kitchens are for the Food Network...
well thanks flybyme and APrinceAmongMen, these 2 posts really cleared up somethings. I'm in the process and will keep you guys updated.
QUESTION: how do i change the radio and boot animations in a rom?
PS: the good news is, i'm done with all the hard part, and just few small things remaining. Probably if anything else doesn't comes up, you guys should have a n1 kitchen within few days =D
shararti said:
QUESTION: how do i change the radio and boot animations in a rom?
PS: the good news is, i'm done with all the hard part, and just few small things remaining. Probably if anything else doesn't comes up, you guys should have a n1 kitchen within few days =D
Click to expand...
Click to collapse
boot animations are located either in /data/local or /system/media
radio flash will require you to change the update-script
you can look at the FRF50 update with the radio to figure it out ( or pm me if thats too difficult, its a little late else id do it myself)
Just make sure the radio is excluded by default.
Another thing about radios, the newest radio usually works on older roms, but old radios don't work on the roms released with and after the newest radio.
Has anybody heard if perhaps we could see something from unrevoked?
I love ROM MRG, use it on several of my phones.
Would love to have it on this thing too.
Dennis
If anybody is up for the challenge, they can compile Clockwork recovery for the Galaxy Tab by following these steps:
*EDIT* - seeing as how I'm not permitted to post links yet, you can find the steps by simply Googling 'porting clockwork recovery'
It's written by Koush on his website.
I don't think the SGT uses MTD though, so you'll have to use dd to dump the boot image.
I'm not up for that. I would happily do it with some help, but not on my own.
I know there are plenty of people here capable of doing this much quicker than I would. Considering I would be learning as I go.
I'm pretty good at figuring things out, but I don't have a build environment set up and really would only use it for this.
No takers?
D
Yeah,there are plenty of people capable, but weneed to wait for them to get a Tab :/
Sent from my GT-P1000
I'm happy to supply whatever is needed off mine. For some reason (maybe that I play too much) I never feel safe without a NAND backup.
What I needed to start this I am willing to help. I got the TMobile Samsung Galaxy Tab?
Sent from my Samsung Galaxy Tab
dsb9938 said:
I love ROM MRG, use it on several of my phones.
Click to expand...
Click to collapse
So does Clockwork Recovery have a lower level recovery than Titanium Backup? I am just curious because I am new to all of this and am looking for a backup solution myself.
Looking through Titanium Backup help files, it seems that you are left on your own with recovering the ROM. The ROM MRG function you mention seems it would take care of even that.
Thanks for any further light you can shed on this topic for me
bml8
/10char
I was looking into building clockwork,
But my ubuntu is being stupid and will not install java-5jdk
It will only install java6 and java 6 is incompatible.
I will look into this a little bit more.
amoamare said:
I was looking into building clockwork,
But my ubuntu is being stupid and will not install java-5jdk
It will only install java6 and java 6 is incompatible.
I will look into this a little bit more.
Click to expand...
Click to collapse
I built the entire Android Open Source Project (AOSP Git/Repo code from the master Froyo 2.2 branch) on Ubuntu 32bits from inside a virtual machine running on Mac OS X 64 bits, using Open-JDK/SDK Java6 (v1.6). The official Android documentation says it's impossible, but there's a workaround, maybe that can help:
./core/main.mk
=> comment the "error" statement that makes the build fail when testing for: ifneq (64,$(findstring 64,$(build_arch)))
./external/clearsilver/cgi/Android.mk
./external/clearsilver/java-jni/Android.mk
./external/clearsilver/util/Android.mk
./external/clearsilver/cs/Android.mk
=> change from 64 to 32 in "LOCAL_CFLAGS += -m64" and "LOCAL_LDFLAGS += -m64"
Easy
That looks like a fix for 64-bit to 32-bit.
I have been using aosp's rom v13, within it there are the googleemail and googleexchange apk's
within rom v21 those have been replaced with email and exchange apks
i have ran CRC checksums on those two versions and they're both the email and exchange apks are different between them. The v21 file sizes are substantially bigger but nothing in the change log tells us why.
the gapps from koushes ics thread has different crc's for those apks than aosp's v13 or v21; they don't match either of aosp's included apks.
This could all be nothing but I think we need an answer here.
Can someone talk about what's going on here? Since these are GAPPS they are the most sensitive apps, I'm sure people will get mad for me making a thread about this but I'm honestly surprised no one has questioned this earlier. I trust the dev's, otherwise I wouldn't be here flashing their roms, but that doesn't mean I shouldn't be able to question something like this openly either. I just want to understand why the email apk and exchange apk are so different from rom to rom within the same dev as well as why they're different from dev to dev when they share the same version.
Thanks
You have my support. I would like to know what the explanation is. I don't assume any I'll intent but it is a valid concern.
I looked at each apk content and there are some extra images in aosp version and the manifest file also but I don't think it was him putting it there. My best guess would be that he compiled it using different options.
If I'm not mistaken, email.apk is part of android os and therefore source is available. When compiling from source, not all files will come through the same.
I would still prefer that Jim stops by this thread and explain why his version is different. I'm sure he has a reason.
...and still no reply? Can anyone reach out?
I'd suggest going to the dev's thread, asking the question and linking to this thread.
Did that to no avail. I'm back to gingerbread.
Will someone get access to my emails, etc.? Some fill me up on this? Please.
You can set different levels of compression when making the APK files. Some devs remove stuff and others add, no two will be exactly the same.
Use apktool to decompile the packages and then beyond compare to compare to see the difference.
Most devs deodex the packages so they will be larger when compared to a Nexus dump from Google that has the odex files.
I have checked out most ICS ROMs in this forum and nothing fishy like that is going on. I always look at the ROMs before installing just to be safe.
AndroidUser00110001 said:
You can set different levels of compression when making the APK files. Some devs remove stuff and others add, no two will be exactly the same.
Use apktool to decompile the packages and then beyond compare to compare to see the difference.
Most devs deodex the packages so they will be larger when compared to a Nexus dump from Google that has the odex files.
I have checked out most ICS ROMs in this forum and nothing fishy like that is going on. I always look at the ROMs before installing just to be safe.
Click to expand...
Click to collapse
Thank you! I don't know how to use apktools so I just want to be clear...you've looked at the apk for email and exchange for both the v13 and v19 vs what's included in the gapps from koush and you've determined that they're all actually the same?
For what it's worth, if the dev uses a different system key to sign everything, it will cause the checksums to be off. ODex vs DeODex (Optimized vs nonoptimized) can very easily double things in size. Nothing creepy about that.
In addition, Mail and Exchange are not part of GAPPs, they're part of system apps, meaning the source for them are released (as opposed to GAPPs). This means they go through the compilation steps just the same as the rest of ICS.
Hi,
I have just bought a new Xperia Pro and Here is My first Contribution.Hope you guys like it.
I have tested it personally on the Unoffical MIUI port for PRO.But it should work on other Kernels and Xperia Devices as well.
I am posting a few Screens for you guys and as you can see lxde is already pre-installed for you guys.
Feel Free to comment
Disclaimer:-
I am Not responsible if anything Happens to your Phone.You do it at your own Risk and Responsibilty,
If you Screw Up then dont Blame Me.
I am not responsible for Anything.
What is chroot?
A chroot image is like a Virtual Machine where you are running an O.S within an O.S.The point of this is that you have a whole Linux System running on a phone where you can ofcourse access all the utilities available in Linux.and as it runs inside of android you dont need to flash anything and can use both the chrooted O.S and Android together.
Things required:-
1)Terminal
2)Root
3)Sdcard with atleast 2GB of free space
4)A Brain
Please Consider Donating to add to my late night coffee and Books Fund.
Link:-
https://www.dropbox.com/s/4k1f5l9jxy2nr9n/debian.7z
Mirror:-
http://www.4shared.com/archive/uNEXsuNS/debian.html?refurl=d1url
Note:
Please read the ReadMe.txt file attached to this post first for instructions.
A special request to all those who are donatinglease send me a P.M so that i know who you guys are.
Donators:-
None So Far
Thank you.
Posting Ubuntu over Here
Remember to Read the Read Me File First.
Link:-
https://www.dropbox.com/s/z7ekya7u7zo19p8/ubuntu.7z
Mirror:
http://www.4shared.com/archive/Qv0u_lWN/ubuntu.html
Mirror:
http://min.us/mZVpflpS5
Posting Back Track 5 Linux
Remember to Read the Read Me
Back Track linux Temp mirror(From My O2x Thread)
https://www.dropbox.com/s/ccf7lhfazl7li7u/btl.7z
Mirror:-
http://www.4shared.com/archive/EoGkvPD9/btl.html?refurl=d1url
NOTElease Download the file btl attached to this post and extract it on your computer and copy the btl file within and paste it in the btl directory downloaded from the above hosts replacing the old one.Now the chroot should run.
added a new Script and deleted the old one.Please use that now.I tested it personally on Stock and it is working perfectly.
As soon as it boots it asks if you wanna start VNC server?Press N and then follow the readme file.
Incase of any probs please let me know
and another
One More
Final Reserve
Nice Run..! First..
Nice work:good:
And im gonna donate [if you make mods I need]
But what is so usefull to have this??
xperiap said:
Nice work:good:
And im gonna donate [if you make mods I need]
But what is so usefull to have this??
Click to expand...
Click to collapse
A chroot image is like a Virtual Machine where you are running an O.S within an O.S.The point of this is that you have a whole Linux System running on a phone where you can ofcourse access all the utilities available in Linux.and as it runs inside of android you dont need to flash anything and can use both the chrooted O.S and Android together.check the Screenshots.
GO ahead:Try Ubuntu...it will give you a better Idea.
Hi! Have you tried this on stock kernel? I believe stock kernel doesn't have loop devices enabled and MIUI is a rebase of CM? Not sure though that's why I'm asking.
Riyal said:
Hi! Have you tried this on stock kernel? I believe stock kernel doesn't have loop devices enabled and MIUI is a rebase of CM? Not sure though that's why I'm asking.
Click to expand...
Click to collapse
The Miui i used was on Stock Kernel.The Kernel Does Support Loop devices.Miui is a Rebase of CM but the loop functionality is related to Kernel.So,Yes it Works on Stock Kernel on Locked/Unlocked Bootloaders Both as we are not flashing anything.
Anyway Give Ubuntu a go.
manasgirdhar said:
The Miui i used was on Stock Kernel.The Kernel Does Support Loop devices.Miui is a Rebase of CM but the loop functionality is related to Kernel.So,Yes it Works on Stock Kernel on Locked/Unlocked Bootloaders Both as we are not flashing anything.
Anyway Give Ubuntu a go.
Click to expand...
Click to collapse
Thanks! Just clarifying things out I haven't meddled with stock kernel that much that's why I am asking. Well the kernel sources sony provided has loop devices disabled by default glad that it's enabled on the official precompiled one.
Anyways! Try packing backtrack that should be alot useful than debian w/ lxde or a classic ubuntu image.
I got backtrack to run on Pro sometime ago when I was still using gingerbread.
Riyal said:
Thanks! Just clarifying things out I haven't meddled with stock kernel that much that's why I am asking. Well the kernel sources sony provided has loop devices disabled by default glad that it's enabled on the official precompiled one.
Anyways! Try packing backtrack that should be alot useful than debian w/ lxde or a classic ubuntu image.
I got backtrack to run on Pro sometime ago when I was still using gingerbread.
Click to expand...
Click to collapse
Already Did.Will upload it sometime Later today or tomorrow.
Debian and Ubuntu both have lxde pre-installed.
Edit:-BT5 UP.
Hi! seeing that you're a fanatic of these perhaps it would be useful if I give you these.
http://50.56.186.177/filez/
Those are packed and reduced sizes of debian & fedora arm images made to fit for chrooting on mobile devices. I made those for my previous device and is very stable already with 256mb RAM
the debian image is a squeeze version. Plus included is the fix for pulse audio. I'm not sure if it would work out of the box for android but with just a little bit knowledge with basic linux stuffs you could get it running perfectly
Riyal said:
Hi! seeing that you're a fanatic of these perhaps it would be useful if I give you these.
http://50.56.186.177/filez/
Those are packed and reduced sizes of debian & fedora arm images made to fit for chrooting on mobile devices. I made those for my previous device and is very stable already with 256mb RAM
the debian image is a squeeze version. Plus included is the fix for pulse audio. I'm not sure if it would work out of the box for android but with just a little bit knowledge with basic linux stuffs you could get it running perfectly
Click to expand...
Click to collapse
THANKS for the link...Meego wont chroot..tried it on the optimus a few months ago and failed..problem with zephyr..will give it a go later.fedora I had as well..but the thing is ...Does anyone except me even use these here????
I do but not that much. Like I said I just only tried backtrack and obviously I use it only when needed
Say do you think it would be possible to include a custom kernel on a chrooted image? It would be cool if we have backtrack here with monitor mode enabled. I think the wlan drivers/hardware of Xperia devices have the capability.
Or also try posting this thread to some other Xperia Sub forums. Arc/Pro users seem to be not very open to these kind of works. They just care on custom ROMs
In short they aren't geeky enough They aren't even that interested in dual booting.
Riyal said:
I do but not that much. Like I said I just only tried backtrack and obviously I use it only when needed
Say do you think it would be possible to include a custom kernel on a chrooted image? It would be cool if we have backtrack here with monitor mode enabled. I think the wlan drivers/hardware of Xperia devices have the capability.
Or also try posting this thread to some other Xperia Sub forums. Arc/Pro users seem to be not very open to these kind of works. They just care on custom ROMs
In short they aren't geeky enough They aren't even that interested in dual booting.
Click to expand...
Click to collapse
In theory yes its possible.but changes will have to be made to the arm kernel to chroot.when u type uname in terminal the output inside the chroot is different than the android kernel.but I think native booting will be better than chrooting..not being interested is just odd....its so much fun having linux on the go
manasgirdhar said:
A chroot image is like a Virtual Machine where you are running an O.S within an O.S.The point of this is that you have a whole Linux System running on a phone where you can ofcourse access all the utilities available in Linux.and as it runs inside of android you dont need to flash anything and can use both the chrooted O.S and Android together.check the Screenshots.
GO ahead:Try Ubuntu...it will give you a better Idea.
Click to expand...
Click to collapse
It would help a lot of people if you would put this description in the first post, or even a better description. Great work!
ameer1234567890 said:
It would help a lot of people if you would put this description in the first post, or even a better description. Great work!
Click to expand...
Click to collapse
Thanks for the advice.added to first post...not good with explanations
Riyal said:
I do but not that much. Like I said I just only tried backtrack and obviously I use it only when needed
Say do you think it would be possible to include a custom kernel on a chrooted image? It would be cool if we have backtrack here with monitor mode enabled. I think the wlan drivers/hardware of Xperia devices have the capability.
Or also try posting this thread to some other Xperia Sub forums. Arc/Pro users seem to be not very open to these kind of works. They just care on custom ROMs
In short they aren't geeky enough They aren't even that interested in dual booting.
Click to expand...
Click to collapse
Actually I know I am going to say something Off-Topic
1) People on XDA are now the people who have got a smartphone just because they can afford one and wanna make their phone look "kewl" than the others with the same device
2) People do dumb things like cross flashing kernels.. They dont even read carefully what the OP says..
3) Running linux on a phone would be the best thing.. specially on an xperia pro where you get a harware keyboard..
I would like all noobs to see this - http://forum.xda-developers.com/showpost.php?p=16682226&postcount=2441
and this - http://forum.xda-developers.com/showpost.php?p=15826094&postcount=45
Would like to know the best way to compare two roms, I am currently seeing crc32 manually, but I want to know if you have a program that does this automatically.
This is a problem..you cant this is a problem
You can check it with several methods. The best way to check it, use any binary file comparison tool, for example free apps: WinMerge (win), kDiff3 (win/linux), and compare the java classes in the framework. Not need to decompile the files, just compare the classes.dex files (the .jar files is compressed, if you want to be 100% sure, extract the classes.dex files manually). This is easy and fast way. Comparing the file sizes/dates is also a solution, but this method is not safe to identify the two rom is same or not. You can compare the binaries (/system/bin, /system/lib folders) too. If the main java classes (classes.dex in framework.jar, core.jar and services.jar) is same, and the most shared binaries (the .so files in /system/lib) also same, the two rom is 99% based on same rom or one of these rom based on the other rom. Do not compare the .apk files (framework-res.apk, and any app in /system/app) because modify these files is easy work, if these files different it means nothing.
fps_fan said:
Would like to know the best way to compare two roms, I am currently seeing crc32 manually, but I want to know if you have a program that does this automatically.
Click to expand...
Click to collapse
Most important is performance of two roms to be compared .....
I recommened atutu benchmark ,,,its an app on playstore...download and check the score of the two...
Hit thanks if helped..
:good:
I think the OP want to compare the roms origin (he/she want to know the examined rom is a copied or soft modded/themed version of another rom or not), not the performance. But you are right, for performance comparison antutu is a good choice because millions of results available, easy to compare with another rom on same device.
But don't forget: all benchmark is based on synthetic tests, the highest benchmark result not equal with the best usability.
Sent from my E15i using xda app-developers app
i usually comparing ROM by installing one by one then i use it for a week
That's my way
alund said:
i usually comparing ROM by installing one by one then i use it for a week
That's my way
Click to expand...
Click to collapse
This
pilu1978 said:
I think the OP want to compare the roms origin (he/she want to know the examined rom is a copied or soft modded/themed version of another rom or not), not the performance. But you are right, for performance comparison antutu is a good choice because millions of results available, easy to compare with another rom on same device.
But don't forget: all benchmark is based on synthetic tests, the highest benchmark result not equal with the best usability.
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse