Below is a format that should be used as an example of how a rom thread should look. It doesnt have to be exact. I suggest that you stay creative and use all the features in the advanced panel when creating a thread.
1. Name of rom, team, etc
2. Introduction
3. Changelog in code or php tags
4. What's included in the rom in the (apps, tweaks, scripts, addons, mods) in code of php tags
5. What works/what doesn't work in code or php tags
6. Credits (Users name-with link to (profile/github/or thread u got tweak from embedded), and what they did to help you)
7. Screenshots (2-10 different screenshots of different aspects of rom)
8. Kernel with either link to thread you got it from or github (if stock sense or cm please state that and that is enough)
9. Instructions on how to install the rom (also if special instruction for a2sd or beats audio...etc)
10. Do's and Don'ts of the rom
11. Questions & Answers section (I find this helpful to write out asked questions with solutions at the bottom of the op. I find that it cuts down on the question being asked a million times)
12. Finally the dl link
13. Additional add-ons (this can go into first post or reserved posts after)
I find the embedded link looks and feels better throughout the op if possible.
All sections should have a header with enlarged text and spaced out so people can read it easily.
I am hoping that this helps to make this section a little cleaner and easier. enjoy
The way I look at this is that it takes US weeks/days/hours to make these roms....we can take the time out to make sure that the op looks professional and clean
Also Make sure the op is fully ready before posting. I know we all get excited to release a rom but stating that half the stuff will be updated as time permits just shows that you are lazy and in a hurry which doesnt look good cause if thats the case then how does your rom run....
No posting a a rom thread without a DL link either
Related
Hello, guys!
The forum is super but here is ocmplete disorder. Where are the ROMS?
How can one find a ROM file here?? The forum is huge and the search leads to discontinued results (2008 year)
Can someone point me to ROM file archive here?
BR
I'd demand a full refund of the money you've paid....
Seriously, if you scroll down through this list a few pages, some kind person has compiled a thread with all the links in one place. Search is terrible and you have to spend lots of your own time. Still, it's free.
Man its full of ROMs. Most active topics or most discussed ROMs are showed on first page. U dont need to search, just click on thread one the rom u like. Its noted by Cook, Built, WM version, sense version, and ROM Version.
Its easy as it can be.
But it's a mess here!
No normal instructions. All are outdated.
Well, as it was said - it's free and therefore it's messy.
ROMs here - one file, no Ruupdate.exe , no nothing. Like if any user comming here is a professional HTC developer. I am simple user and i am sick of spending hours of my time by gathring info by tips. Well, like i said -- good forum, but no order.
What are you complainin?
Please just have a look at recent posts as already said.
The threads where you have a lot of activity are the threads with new roms.
There are also plenty of tutorials!
For example this one: http://forum.xda-developers.com/showthread.php?t=416211
For sure you will need some time to compare different roms and find your best fitting one....which comes with the big choise of roms.
And also there will be little problems from time to time which I'm sure you can solve in a short amount of time.
I can recommend the google search, not built in forum search.
Concerning flashing you don't need to use Ruupdate.exe, it's way easier to name your .nbh file DIAMIMG.nbh, move it to the phone's internal storage and flash directly (see tutorial)
Kind regards and have fun with your new roms
Shark_XXL said:
What are you complainin?
Please just have a look at recent posts as already said.
The threads where you have a lot of activity are the threads with new roms.
There are also plenty of tutorials!
For example this one: http://forum.xda-developers.com/showthread.php?t=416211
For sure you will need some time to compare different roms and find your best fitting one....which comes with the big choise of roms.
And also there will be little problems from time to time which I'm sure you can solve in a short amount of time.
I can recommend the google search, not built in forum search.
Concerning flashing you don't need to use Ruupdate.exe, it's way easier to name your .nbh file DIAMIMG.nbh, move it to the phone's internal storage and flash directly (see tutorial)
Kind regards and have fun with your new roms
Click to expand...
Click to collapse
My complain is that forum is full of unimportant trash in topics and no really helpfull info. Like now, i have found a ROM, flashed it and i lost TouchFlo ) Super!
And no original ROMS, only some outdated.
Well, i am a bit tired reading this forum today within 8 hours to find more or less fresh tut, so i can not tell you exactly what is wrong, but i am telling you - i am professional software developer, not a lamer and not a pumpkin head BUT i lost in this forum, jumping from link to link.
I would delete ALL and put all in order:
Flash (ROM) files here:
Radio files here:
Boot loaders (Hard SPL or whatever it's called) here:
Flashers (Software) here:
Tutorials here:
Discussion here:
Instead i see 13248 topics with xxxxx messages inside and 1% of useful info.
Well, if you take donations then make it user friendly.
I will donate 100 USD to make it in order.
And PS - this is a problem that there are Plenty or tutorials!
Like we say in my language - brevity wit! Try to write the less and put sense the more.
Like when i read - hard SPL... then 100 lines text, cheers to authors and then - a patched bootloader..
LOL
Dharam's Kernel Development Tutorials
Since many of the S2 Kernel Developers have moved on or will be moving on to the Galaxy S3, I feel we need more developers for the S2. No offence to those who have moved on, even I would have done the same if I could afford one
Anyways, there will be many people who will have the knowledge of coding and stuff, just wont know how to build kernel's and all...
So here I present the Kernel Development Tutorials for the Galaxy S2. It will be similar for many other devices and so you can refer the same also if you are developing for any other device
The thread will be similar to my previous tutorials for the Galaxy 3, but based on MOD's for the S2.
I do not present myself as an expert of things, there are many great developers for the device including codeworkx, chainfire, gokhanmoral, simone201 and many many others which I am just skipping for the time being. Credits for their work will be provided as and when refered to.
I am also learning stuff myself, and so I maybe wrong at many places. I would request other developer's to keep a look on this thread and help out me and others whenever required. You guys have better knowledge, and it is a great thing to share the knowledge.
I will explain everything Step by Step.
If you got time to learn/develop join in.
If you get some step working and a fellow developer cant get it, please help each other by answering everyone's doubts.I cant reply to each and every query always.
Most of the code is to be run in the terminal. So I wont be mentioning to Open terminal every time.
I would like to thank marcellusbe who was the first one to make a proper custom Kernel for Galaxy 3, who taught me how to build a kernel, and also lot of other help
Note:
Please do not post useless messages.
If you dont know coding, please learn that first.
Do not flood my inbox with PM's. I will not respond to PM's regarding Kernel Development. Please post in the thread, so that everyone can learn.
[*]I AM NOT RESPONSIBLE IF YOU HARDBRICK YOUR PHONE, DOING ANY OF THE FOLLOWING STEPS
A request to all the people, please do not vote down this thread directly. It will take some time to build the tutorials step by step. If you have any doubts, then this thread will be similar to http://forum.xda-developers.com/showthread.php?t=1186409
I have got many requests to do a similar series for the S2, and so I am doing it.
This series will also be posted at www.androidnova.org - Checkout the website for latest Android News, Reviews and other cool stuff
Step 1: Setting Up The Build Environment
Installing Ubuntu.
1. Download Ubuntu x64 from http://www.ubuntu.com/download/desktop
2. Install Ubuntu directly or as a Virtual Machine ( I prefer direct installation)
3. If setup is Virtual Machine, Please dedicate enough RAM and processor for the Kernel to build fast, else it will take ages
Logging In As Root
1. When Ubuntu first boots, login with the username and password you mentioned while installing.
2. Open Terminal
3. Use following command.(Always the code after $/# is the one to be used. The one before that just specifies [email protected]:~)
## Anything after ## is a comment by me.
Code:
[email protected]:~$ sudo passwd
[sudo] password for dharammaniar: ## Enter password which you used to login.
Enter new UNIX password: ## Enter Password for root(it can be same as your prev password)
Retype new UNIX password: ## Re-Enter Password for root
passwd: password updated successfully
[email protected]:~$ su
Password: ## Enter the root password
[email protected]:/home/dharammaniar#
4. Once you get the last line as above means you now have root access.
5. Now logout from this user and login with username as root
6. On starting Terminal now, you should get
Code:
[email protected]:~#
Setting Up Build Environment
1. You should always be running as root.
2. Go To System->Administration->Synaptic Package Manager
3. Search for ncurses-devel
4. Install libncurses5-dev.
5. Download the toolchain. You can find it in the AOSP Source. I will also upload it soon enough.
Downloading Source
Downloading The Source
1. Download the Update4 Source from http://opensource.samsung.com/ or https://github.com/CheckROM/DK_S2_ICS_KERNEL/tree/5ec9752c34cedf3e8df9e887ecad6db9337de927
2. Download the initramfs from https://github.com/CheckROM/DK_S2_ICS_INITRAMFS/tree/d85b2201b79588e70387d3df0ffd2f83d741c4ac or maybe request some developer to post how to extract initramfs from stock samsung kernel. Even I am trying to figure that out...
(If any developer is reading this, and can help out, We would be grateful)
3. Create a folder named S2.
4. Inside that have 2 folders, 1) Kernel 2) initramfs
5. Kernel folder should have the source e.g. arch, drivers and all
6. initramfs folder should have the files init.rc and stuff
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Last Reserved... I will make use of these posts as and when required, so request the MOD's not to delete any of the above posts
Sure thing i got all the time i need. I was waiting for someone explain this xD
Nice to see this post. .Sir,I have send you PM if you don't mind please see it .
Really nice iniciative
Good luck !
Setting Up The Build Environment is done...
Checkout first page...
Awesome mate that is what i was looking for!
I really appreciate this
this will be the hugest tutorial in know.
but very helpfull for some peoples.
rly nice
Can I follow this tutorial (codes and everything) with mint 13?
Cristiano Matos said:
Can I follow this tutorial (codes and everything) with mint 13?
Click to expand...
Click to collapse
I think it should work, but cant guarantee...Try it and let me know
Dude, it's really nice. But one question. After that, are we going to have a brick wave? I think that unexperienced people like me will have some trouble when trying to build. Your tutorial will be brick safe if we follow all steps? If yes, I will try to do something.
Ics opensource update 4. is believed to be safe,so people will be "brick-safe".
This thread will be handy for disscussions when we get ICs successor,and samsung presents us a new "virgin" kernel source.
Also,u can find 6 toolchains in this repository- https://github.com/sakindia123/Android_Toolchains
Below is a format that is a guideline to be used as an example of how a rom thread should look. It doesn't have to be exact. I suggest that you stay creative and use all the features in the advanced panel when creating a thread.
Name of rom, team, etc
Introduction
Changelog in code or list tags
What's included in the rom in the (apps, tweaks, scripts, addons, mods) in code or list tags
What works/what doesn't work in code or php tags
Credits (Users name-with link to (profile/github/or thread u got tweak from embedded), and what they did to help you)
Screenshots (2-10 different screenshots of different aspects of rom)
Kernel with either link to thread you got it from or github (if stock sense or cm please state that and that is enough)
Instructions on how to install the rom (also if special instruction for a2sd or beats audio...etc)
Do's and Don'ts of the rom
Questions & Answers section (I find this helpful to write out asked questions with solutions at the bottom of the op. I find that it cuts down on the question being asked a million times)
Finally the dl link
Additional add-ons (this can go into first post or reserved posts after)
I find the embedded link looks and feels better throughout the op if possible.
All sections should have a header with enlarged text and spaced out so people can read it easily.
I am hoping that this helps to make this section a little cleaner and easier. enjoy
The way I look at this is that it takes you weeks/days/hours to make these roms....we can take the time out to make sure that the op looks professional and clean
Not to toot my own horn but here is a link to one of my own rom threads as an example. Link
Also Make sure the op is fully ready before posting. I know we all get excited to release a rom but stating that half the stuff will be updated as time permits just shows that you are lazy and in a hurry which doesn't look good cause if thats the case then how does your rom run....
No posting a a rom thread without a DL link either. If posted then the thread will be removed
Below is a format that is a guideline to be used as an example of how a rom thread should look. It doesn't have to be exact. I suggest that you stay creative and use all the features in the advanced panel when creating a thread.
Name of rom, team, etc
Introduction
Changelog in code or list tags
What's included in the rom in the (apps, tweaks, scripts, addons, mods) in code or list tags
What works/what doesn't work in code or php tags
Credits (Users name-with link to (profile/github/or thread u got tweak from embedded), and what they did to help you)
Screenshots (2-10 different screenshots of different aspects of rom)
Kernel with either link to thread you got it from or github (if stock sense or cm please state that and that is enough)
Instructions on how to install the rom (also if special instruction for a2sd or beats audio...etc)
Do's and Don'ts of the rom
Questions & Answers section (I find this helpful to write out asked questions with solutions at the bottom of the op. I find that it cuts down on the question being asked a million times)
Finally the dl link
Additional add-ons (this can go into first post or reserved posts after)
I find the embedded link looks and feels better throughout the op if possible.
All sections should have a header with enlarged text and spaced out so people can read it easily.
I am hoping that this helps to make this section a little cleaner and easier. enjoy
The way I look at this is that it takes you weeks/days/hours to make these roms....we can take the time out to make sure that the op looks professional and clean
Not to toot my own horn but here is a link to one of my own rom threads as an example. Link
Also Make sure the op is fully ready before posting. I know we all get excited to release a rom but stating that half the stuff will be updated as time permits just shows that you are lazy and in a hurry which doesn't look good cause if thats the case then how does your rom run....
No posting a a rom thread without a DL link either. If posted then the thread will be removed
Is there any way to add the ability for the developers (topic starters) to create a template for every post for members to respond with on their topics?
For instance, when members post to the topic 90% of the time it is a "this does not work", "this is broken", "I didn't read the install instructions but I still want to complain".
It would be incredibly helpful to everyone (to the members that constantly read that but want to still help anyway, ie. me and especially the actual developer for the ROM).
I've seen some devs post in the OP a "template" that members need to copy and paste into their post for a bug report. It's followed maybe 20% of the time. But many don't read the OP so it's still kinda useless there.
Something like github, most gits have a template when posting a bug report. Or something like this here:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
follow all OP instructions:
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (adb log/observations/frequency of problem/last version it worked on/etc) as needed:
Click to expand...
Click to collapse
I shamelessly copied that from the LOS topic here and added a few extras. But that template there (a template that any topic starter could make specific for their ROM) would be fantastic if it could be a template for every reply, basically forcing every poster to fill it in if they have a bug report. I know if I was developing ROMs that would make me muuuch happier to read replies.
Because as it is now, it's pretty depressing I would think for them (the devs) to constantly not see logs or any info other than "this don't work" and that's it (and guessing if they even followed 20% of the instructions). That is no help whatsoever. It would even help other members with the same problem, they could say to themselves "oh I'm using the same custom kernel and didn't wipe...hmm" then maybe they would be able to solve it without the dev wasting time looking into it when it's not even the ROM's bug (maybe it's the custom kernel, etc.).
Summary: a reply template the topic starters could make for their ROMs would go a long way for everyone involved on here.