<Request to devs> please write a tutorial - Optimus One, P500, V General

Hi
I have been on this forum for over a year just browsing,installing new roms and things like that.I never even bothered to make an account.
Recently things have taken a steep,turn on this forum with the devs being disrespected and things like that.
Now that you devs who are really awesome at what you are up to are leaveing the forum to new devices,
I am requesting you as a last favour, please write a tutorial on how you did this awesome work ie porting cm and writing drivers, compiling code and other amazing stuff you did for our phones.
Yours respectfully

abhijay.jagini said:
Hi
I have been on this forum for over a year just browsing,installing new roms and things like that.I never even bothered to make an account.
Recently things have taken a steep,turn on this forum with the devs being disrespected and things like that.
Now that you devs who are really awesome at what you are up to are leaveing the forum to new devices,
I am requesting you as a last favour, please write a tutorial on how you did this awesome work ie porting cm and writing drivers, compiling code and other amazing stuff you did for our phones.
Yours respectfully
Click to expand...
Click to collapse
There are many resources on the internet that already describe how to build the source, port ROM's etc. You can always follow the sage advice
http://www.xda-developers.com/android/sage-advice-from-cyanogen-still-valid-today/

abhijay.jagini said:
Hi
I have been on this forum for over a year just browsing,installing new roms and things like that.I never even bothered to make an account.
Recently things have taken a steep,turn on this forum with the devs being disrespected and things like that.
Now that you devs who are really awesome at what you are up to are leaveing the forum to new devices,
I am requesting you as a last favour, please write a tutorial on how you did this awesome work ie porting cm and writing drivers, compiling code and other amazing stuff you did for our phones.
Yours respectfully
Click to expand...
Click to collapse
You can't just make or follow a tutorial on this things... It's not a move mouse here and click this type of thing.
To understand what the code does and where things are supposed to be and why other things don't work you need years or hardcore programming experience
If you want to start coding you might as well start learning C++, C#, java. But the fact is by the time you'll be ready to code anything for a phone you'll change at least one device

Google has everything. Every tutorial is available.
It will take a few days to write all this.
And this ain't copy paste too
Learn programming languages like C, C++, Java etc and explore the android possibilties.

Related

[Q] Kitchen for Samsung Epic

Will someone please help me in getting a kitchen set up for the Samsung Epic and at least have the paitence to teach me the basic skills of developing for Android and building ROMs for Android. (Like what is the stuff I need to know, and stuff that is essential to having a working Android ROM)
Please and thank you,
Korey
Whosdaman said:
Will someone please help me in getting a kitchen set up for the Samsung Epic and at least have the paitence to teach me the basic skills of developing for Android and building ROMs for Android. (Like what is the stuff I need to know, and stuff that is essential to having a working Android ROM)
Please and thank you,
Korey
Click to expand...
Click to collapse
Here are some links to get you started. There's a lot of stuff to learn, so my best advice is to be patience and lurk, read, and learn. I know nothing about your particular device, but much of this will apply.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://forum.androidcentral.com/hacking/6037-general-rom-faq.html
http://forum.xda-developers.com/showthread.php?t=633246
http://blog.coralic.nl/2010/01/28/build-eclair-aka-android-2-1-for-hero-from-source/
http://forum.xda-developers.com/showthread.php?t=622916
http://forum.androidcentral.com/htc...how-build-your-own-kernel-package-source.html
http://forum.xda-developers.com/showpost.php?p=6738713&postcount=1
http://www.kandroid.org/android_pdk/index.html
http://android-dls.com/wiki/index.php?title=Main_Page
https://docs.google.com/Doc?docid=0AcdxIJRSH9ypZGZzc2pxNDlfMjdnazk4OHNxZA&hl=en
http://forum.xda-developers.com/showthread.php?t=641223
http://adrianvintu.com/blogengine/post/Colored-Logcat-Script-for-Windows.aspx
http://www.androidenea.com/2009/08/init-process-and-initrc.html
http://forum.xda-developers.com/showthread.php?t=623976
http://lukasz.szmit.eu/2009/12/making-your-own-rooted-android-rom.html
http://groups.google.com/group/android-kernel
http://groups.google.com/group/android-building
http://groups.google.com/group/android-porting
http://groups.google.com/group/android-developers
http://groups.google.com/group/android-ndk
http://groups.google.com/group/android-platform
Look for the sticky thread by Cyanogen in this forum called "some advice". Are you looking to build roms from source, or just modify existing roms?
Do you know any Java or C?
Building roms may seem fun, but it takes research and patience. Lurking github commits, textbooks, and the forums is a great start. The community is very eager to help, and that's one of my favorite parts about android. But deving shouldn't be as simple as copy paste. Where's the fun in that?
I understand where you're coming from though, I was the same way a few months ago. Built a rom from source, posted it, then realized how uninformed I was.
I am now improving my skillz by reading textbooks on Java ("Head First Java") and C ("The C Programming Language"), both available as pdf documents. I'm mucking around in kernels and am going to start writing apps as well. Its a good place to learn the framework. You could also get into theming, but that requires a little graphic design know-how.
Good luck man, and have fun with it
Sent from my Nexus One using XDA App
Me too would like to learn more about creating ROMs for android (Galaxy S I9000 here)
I do have java experience (quite a lot, actually) but I really have no idea where to start when creating a ROM
thanks
Did you ever get a kitchen going?

[Q] To: MODS - Guide to the Hacking your Android?

Hi Mods, i am a Android user who has been playing around with Android devices for almost a year now, putting ROM's and Kernels, etc on my devices. I had a Mytouch, Galaxy S 4G, and Asus Transformer. Unfortunately, i don't have time to read through all the threads and develop ROMs etc, and i do appreciate all the time and effort that the developers put into it. I am just a normal user who would like to utilize the full potential of my devices (and like to show Apple users how we can kick their A$$e$. I had a thought recently. It would be so useful to all the regular users to have a BIBLE, that gives us the general steps of rooting, installing roms, definitions of terms and abbreviations, and different mods. It doesn't need to be device specific (or maybe it does). I believe it would help everyone out a lot and help bring some uniformity to the world that is Android.
I hope someone would consider this wholeheartedly. And again, BIG THANKS to all the developers!
Yes, I too think that this sounds like an awesome idea. Something like a wiki from xda-developers. With real noob tutorials and introductions. That way, people who are interested in diving deeper into that have a starting point and xda has a recruiting effect. For example I myself would love to learn about developing from scratch because weeks ago i started my studies where I learn java and c++. Having to search for every tiny bit of information is just annoying...
theres already tutorials out there on some basic things...
Yes sure there are some tuts but nothing like a compendium..
Sent from my HTC Sensation Z710e using XDA App

Wanna start developing ROMS but don't know how/where to begin...

Hey!
A while ago I got the idea of learning how to cook roms.. I made some research on it and I found some helpful stuff on xda. Well, I tried but quiet didn't understand and manage to be successful in doing what was told there..
I've read lots of stuff like "The hardest part of developing roms is getting started". So I guess this is the part where I need the most help
Whatever, the reason why I opened this thread is that I wanna hear some developers. Their ideas on developing; How to get started, their short story on how they started developing...
Basically I wanna learn where/how to start from those people who experienced and managed to become a developer..
I mean, I wanna know your stories as I really think they will help me, they will be examples to me...
Well, not only me, to anyone who reads them.. I'm hoping that this thread will help other newbies like me...
Thanks!
My first android phone was the g1, didn't install CM until the myTouch on t-mobile. I started writing scripts for android phones. Little ones, like LCD Density script or apk removal. Then worked on a theme. Didn't really go anywhere. Fixed a bug for Salvagemod for the Evo, then started working on SalvageMod. Evo needed a kernel after support was said and done, I figured out how to compile it, looking at other commits, I was able to make changes successfully to the Freedom Kernel for the Evo. Then decided that I wanted to work on some gui application. Cmcompiler came about.
While there are many many more details from start to finish. Point is really, that no one is going to teach this to you. You have to want to learn, and you simply have to do it. Its hard work. I have spent hours and hours of messing with things to get them to work correctly. Trial and error is a great way to learn android. Sadly "Android" isn't the only thing you have to learn when it comes to development. You need to learn the tools that come with the development, like packaging or install script if you have a local gui application, or git/svn/bzr for version control systems. Most importantly, you need to have fun learning. If you are not having fun. Quit.
I do not feel attracted when you ask devs to answer, but still.
I started with XDAs kitchen.
No development ofcourse, but a good place to start.
I felt XDA kitchen was not enough, so I started to learn BASH - the scripting language in wich Kitchen is written.
I started with opening the "menu" file out of the kitchen.
After a while, I neede batch-resize, as I wanted to become a themer.
I made it together with my dad.
After I saw that some themes contain more items then another, I made CopyFrom.
AndroidCentral was my next idea - a combination of all home-made tools.
Just like lithid, I felt a GUI was needed.
But I started to work on it for cross-platform usage.
Conclusion: writing scripts is a good way to start. Google is my best friend, as I am new to scripting also.
Good luck
Sent from my Galaxy Nexus using Tapatalk 2
To echo the sentiments of the two previous posts by lithid and mdroid, I also started by writing simple scripts and small projects. Android Utility was my start up project.
My first real projects involved Rosie (HTC Sense launcher) and theming it. Then it become modding the apk to do other things (remapped, 4x5, 5 column app drawer, transparency, etc). The process of learning how to theme and mod one apk really helps you learn.
My recommendation is to pick one particular aspect of your device/Rom and learn as much as you can about it. You will find quickly that by doing so you inevitably have to learn how to use the Android tools, scripting, BASIC programming fundamentals, and a general idea of how everything works.
And yes, Google is your friend. Also stackoverflow
Sent from my PG86100 using Tapatalk 2
I also wanna to start developing. Thanks the infos. Can you write a few standard dev-tools name?
Sent from my ZTE Blade using XDA app
After creating this thread and reading the opinions of developers I followed this tut and tried this kitchen.. Helps in modifying a ROM.
And as I already had Cygwin installed using the way shown in the above tutorial I tried this tool for modifying the boot.img..
And if you want to modify apps you can give a shot to this tool...
These tools are basically really easy to use and efficient. Especially for a newbie like me.
oh, and these words of cyanogen would be really helpful..
start developing is not easy...but if you really want it and can dedicatebtime and patience all will just be fine... it's not recommended that u try to do all at first...maybe just a mod can be ok for you or anyone starting here...try modding a rom,changing stuff,adding tweaka and playing with build.prop as well...then if all goes right u can think on modding more stuff like apjs,themes,including simo comex apks...those who needs extra settings,etc... you'll gain xperience as long as time goes on and will fibd lot of interesting stuff u'd like to invlude on builds...so don't rush...good roms need time and patience
Sent from my MB860 using XDA
Thanks! when I read your ideas, telling me to play around with a rom and all that. I feel that Im really lucky. I've already been playing around with the ROMs I've used so far.. like editing build.prop, basic theming, editing apks, I once edited framework-res.apk to enable the navigation bar, etc...
Yesterday I tried porting MIUIv4 on the cm9 for for my device following some tuts on xda.. I did everything right, but no luck I get stuck in boot logo... Whatever I'll not give up!
I'm planning to study those kitchen stuff more for now, I'll give a shot to the tutorial mentioned on the portal today..
Whats your device?
My next plan to modding a ROM. I read also the MIUI porting thread, that's not hard. A long time ago, with my previously phone, the Xperia X8 (miss you...), i tuned up the stock ROM and modified a cooked ROM for myself - without XDA. I registered after here.
Sent from my ZTE Blade using XDA app
LG GT-540 optimus
I know. Its really easy. Plus I tried to port MIUI by mikegapinski on cm9 by miroslav_mm.. both roms are developed for GT-540.. I do everything right but I get stuck...
I don't what to mod, I mean I don't have any ideas... so Ill try porting MIUI
Hey bro. My advice? Do some heavy softmodding first (Take lets say tejas rom and add themes, adjust framework, add tweaks, add custom animations.custom this custom that basically add what you think is nice and yeah after long you will get more and more weird ideas )

[Q] Helping a dev with rom

Hi,
I've been using XDA for a while now, and with the help of many amazing devs I've managed to flash custom roms to all my older devices no problem! Recently I've been waiting for a dev to make changes to an existing kitkat rom, to fix a bug and I'm becoming a little impatient. I know everyone has their own lives to attend so I'm not complaining, rather I'd like to try and help this dev with the problem as I have quite a lot of experience with Android apps. I've read up on the CM wiki the sort of things that are involved in debugging roms etc. so I know that I'll only be able to help with the framework (as I know no C/C++).
So my question is, are there any ways I can help them, and will my help be appreciated considering the skills I have? I also have a decently fast computer too so I have a feeling I could help with building the rom.
Thanks.
Roarster31 said:
Hi,
I've been using XDA for a while now, and with the help of many amazing devs I've managed to flash custom roms to all my older devices no problem! Recently I've been waiting for a dev to make changes to an existing kitkat rom, to fix a bug and I'm becoming a little impatient. I know everyone has their own lives to attend so I'm not complaining, rather I'd like to try and help this dev with the problem as I have quite a lot of experience with Android apps. I've read up on the CM wiki the sort of things that are involved in debugging roms etc. so I know that I'll only be able to help with the framework (as I know no C/C++).
So my question is, are there any ways I can help them, and will my help be appreciated considering the skills I have? I also have a decently fast computer too so I have a feeling I could help with building the rom.
Thanks.
Click to expand...
Click to collapse
Ask them. Or ask their permission to use their ROM as a base, make some actually meaningful modifications, and release it. But as too your "skills" I didn't see you state what they were, and if you have to ask then probably not. Don't stop reading/learning though, you'll only get more knowledgeable.
thewadegeek said:
Ask them. Or ask their permission to use their ROM as a base, make some actually meaningful modifications, and release it. But as too your "skills" I didn't see you state what they were, and if you have to ask then probably not. Don't stop reading/learning though, you'll only get more knowledgeable.
Click to expand...
Click to collapse
Ok, I was thinking along the lines of making modifications and then pushing them to a git repo. Maybe they don't have one, I'll go ahead and ask. As for my skills, I was saying in my last post that I have quiet a lot of experience developing Android apps. Do you know what % of rom editing is Java based vs C/C++?
Roarster31 said:
Ok, I was thinking along the lines of making modifications and then pushing them to a git repo. Maybe they don't have one, I'll go ahead and ask. As for my skills, I was saying in my last post that I have quiet a lot of experience developing Android apps. Do you know what % of rom editing is Java based vs C/C++?
Click to expand...
Click to collapse
There is no hard/fast guide on what "rom-editing" is. Are you wanting to contribute to kernel development? Better know a lot of C. Wanna roll a cool application for a ROMs special settings? Java is what you want. What I'm getting is you know more Java, so why don't you write and application that you think will solve a problem, then talk to a developer about including it in their ROM?

Rom development stranger way

can someone tell me why the developers have 2.3.4 rom in development, with bugs and little support ??? when it is better to devote time to a single good and seriously attended !!!!
Sent from my Redmi 3S using XDA-Developers Legacy app
Same question. There are a few devs who would work on one build then abandon the project completely, and make another build of a different ROM.
Because most of that So called Development is just copy paste job. those guys don't actually develop anything by themselves. otherwise they could have fixed it, instead they wait for actual developers to fix it and just copy from them. :silly:
kraatus90 said:
Because most of that So called Development is just copy paste job. those guys don't actually develop anything by themselves. otherwise they could have fixed it, instead they wait for actual developers to fix it and just copy from them. :silly:
Click to expand...
Click to collapse
agreed
[email protected] said:
can someone tell me why the developers have 2.3.4 rom in development, with bugs and little support ??? when it is better to devote time to a single good and seriously attended !!!!
Sent from my Redmi 3S using XDA-Developers Legacy app
Click to expand...
Click to collapse
kraatus90 said:
Because most of that So called Development is just copy paste job. those guys don't actually develop anything by themselves. otherwise they could have fixed it, instead they wait for actual developers to fix it and just copy from them. :silly:
Click to expand...
Click to collapse
1. You will know then answer when you try to compile one ROM (Not developing).
2. Compiling a ROM is not just a Copy & Paste work. If it's so... Do yourself.... (its just copy & paste nah..?)
So here is a answer. I'm also started Android Development just 2 weeks ago. And i compiled 4 different ROMs : Lineage, Candy, Slim, Glaze. I'm not doing it for you. But for me. I wanted to learn, no one can start from "Coding Everything from Scratch" especially legacy softwares like kernel and other things. So we start from compiling.... When we successfully compiled a ROM by facing and fixing many Errors. We move on to a new ROM, Coz New ROM will give new errors and we can learn to fix them. You may ask "Why you cant learn from Improving a rom...?" and my answer is "NO ONE IS GONNA TEACH ME HOW TO IMPROVE A ROM". Self learning needs lots of trial and error. So we building many ROMs. If you don't like that or you are a cry baby who cries for "XXXXX is not working" or "Poor XXXX". Just stick with STOCK ROM. XDA is for Learning and Not Only for SERVING YOU A BUG FREE, FULLY OPTIMIZED, FULLY FEATURED CUSTOM ROM for FREE.
Sorry.... if anything hurts anyone... I mean it.
dineshthangavel47 said:
1. You will know then answer when you try to compile one ROM (Not developing).
2. Compiling a ROM is not just a Copy & Paste work. If it's so... Do yourself.... (its just copy & paste nah..?)
So here is a answer. I'm also started Android Development just 2 weeks ago. And i compiled 4 different ROMs : Lineage, Candy, Slim, Glaze. I'm not doing it for you. But for me. I wanted to learn, no one can start from "Coding Everything from Scratch" especially legacy softwares like kernel and other things. So we start from compiling.... When we successfully compiled a ROM by facing and fixing many Errors. We move on to a new ROM, Coz New ROM will give new errors and we can learn to fix them. You may ask "Why you cant learn from Improving a rom...?" and my answer is "NO ONE IS GONNA TEACH ME HOW TO IMPROVE A ROM". Self learning needs lots of trial and error. So we building many ROMs. If you don't like that or you are a cry baby who cries for "XXXXX is not working" or "Poor XXXX". Just stick with STOCK ROM. XDA is for Learning and Not Only for SERVING YOU A BUG FREE, FULLY OPTIMIZED, FULLY FEATURED CUSTOM ROM for FREE.
Sorry.... if anything hurts anyone... I mean it.
Click to expand...
Click to collapse
Why did you took it personally lol? it was just an observation. yes there are people who want to learn and they have to start somewhere. nothing wrong in that. but when you see same people doing exactly same thing for a long time and not improving upon that. it becomes clear what they are doing.
and i never ask for fix this fix that, cuz i know who are actually developing and who are just waiting for fix to be developed by someone else. so no point asking. you sound like someone who wants to learn. but that doesn't mean everyone else is like you. there are people who as i said haven't learn anything but just copy paste cherry-pick for donation money. i rarely see anyone with their own piece of code. happens even more with kernel btw.
and yes i have compiled cm13 2 year ago that's the reason why i know this, and currently using my own (copy-paste haha) kernel for both MG5/nexus 5x. although i haven't released it. nor i'll. (source is on my git if you don't believe).
Anyway, best of luck for your learning, i hope you will learn a lot and will be able to fix problems by yourself instead of waiting for others. it's a long road ahead :good:
First of all, people always mistake ROM/Kernel etc development (not talking about app and other development which are indeed) as profession of devs, they do it in their FREE time because they like it, for example you play basketball because you like it.
Secondly, when there is shortage of ROMs, you yourself would complain about it, please correct me if I'm wrong. Different ROMs have different flavours, and everyone of us likes tasting different flavours. If you're worried about why a thread owner isn't updating it, you can migrate to other one instead of complaining about it.
Some guys have enough skills to compile ROMs, but not the ability to work on source code. So they wait for fixes by those who work on source, and update their ROMs as soon as bug is fixed. Also, compiling can be the start of learning development for guys.
Although I agree with @kraatus90 on some points, there are some things that I don't. First of all, there's no point of redoing the whole kernel, vendor, tree source stuff when you can use the available code with some modifications, obviously the one who uses it have to give proper credits to the bringup dev and other contributors. Also it should be moral duty of the forker to improve the forked code, be it in small or big ways. Simply forking, compiling and PUBLISHING is certainly disheartening and condemnable.

Categories

Resources