Related
Without the inclusion of proper documentation included with an Android Rom or an Android Build users will start filling up the HD2 Android Development Forum with why this wont work when it does on someone elses Rom. To stop this from happening there will be a requirement when creating a Thread for a Rom with Android included, or an Android Build.
------------------------------------------
------------------------------------------
If you are making a Rom with Android built in or an Android Build that is run from haret then please INCLUDE with your file a readme.txt file in the ROOT of your release archive with the following information:
*What BUILD version?
An internal version # that can be used to identify the authors exact release (e.g. my-rom-v0.5.zip) for easier reference for the users and fellow developers benefiting from the release.
*Which kernel image and kernel modules are used?
Where are zImage and modules.ko originally downloaded (in case the chef didn't compile on their own) and where is the kernel source code for the kernel and modules.
In case the chef did not compile on his own, he should still be able find out where the source code is.
(The license under which the Linux kernel is released requires the distribution of the source code that was used when distributing builds.)
*What rootfilesystems are used?
Where was it taken from, what does it include (android version it's based on etc) and in case of self compilation, where is the source code.
(In case of most windows mobile shipped devices that's often some rootfs file e.g. named android.ext2 and an initial ram filesystem often named initrd.cpio.gz).
*ChangeLog*
A ChangeLog is really an essential addition in every build as it informs the end user what modifications have been made from the last build. This will save you ALOT of questions as to what has been added, deleted or modified and therefore is a requirement for everyones benefit.
*WindowsMobile version your Android Build was tested on*
Please include your WinMo Build version, HTC OemDrivers (if known), XIP (if known) and Radio version so that users know what the Android Build was tested on and can replicate if neccessary for fault finding purposes.
------------------------------------------
------------------------------------------
If you are unable to obtain any of this information and thus can't make it available through an included readme.txt you should not distribute your rom and keep it for personal use only.
If you are using an exact copy of a present release (e.g. in case of a WinCE rom that has an android 'dual boot' option) you must include the readme.txt from the original rom chef.
If you release a Rom and do not have the required information then you will be asked to either create and include a readme.txt file with your Rom or ask for the thread to be deleted.
If you have any comments or questions on this please feel free to post.
Mark.
** reserved **
Thanks a lot for the quick action, Mark. I am glad to see a first positive response.
If this will establish I hope that
*users are informed about what they get
=>less unneeded questions and thus more room for constructive feedback
*developers have an easier time to benefit from present releases
*new developers must try to get an understanding of what they are doing
=>more quality releases
The original post can be found here.
I think it would be nice to hammer out the readme.txt requirements together with chefs so we can get some convention that satisfies everybody.
edit: Think it will really be good to always put readme.txt in root of release archive so everybody knows where to look for it.
dcordes said:
edit: Think it will really be good to always put readme.txt in root of release archive so everybody knows where to look for it.
Click to expand...
Click to collapse
Edited the 1st post to include this
Mark.
Will be following this convention for any future releases
DarkStone1337 said:
Will be following this convention for any future releases
Click to expand...
Click to collapse
Thank you
Future releases soon I hope lol
Mark.
May I suggest that the readme include the date of ROM compilation, as well as the date the kernel and root file systems files. I think this will help users and chefs to easily build there own compilations and keep track of it's validity.
And a title format like: [date]-[name]-[version]-{[kernel]-[kerneldate]}-{[modules]-[modules-date]}-[rootfs] (just like rules for 'regular' roms). Both for the post and the archive preferably?
Personally I switch between versions a lot, to find differences/improvements/bugs.
Clear archive-naming should simplyfy this .
Excellent rules! We need to improve stability of ports and eliminate all unnecessary questions !
P.S. Hope there won't be any "bogus", or "copy-paste-claim" ROM-s.
dcordes an mskip +1
ahbad said:
May I suggest that the readme include the date of ROM compilation, as well as the date the kernel and root file systems files. I think this will help users and chefs to easily build there own compilations and keep track of it's validity.
Click to expand...
Click to collapse
Very good idea. I think we should at least add the rom release date to minimum required readme.txt information.
For the rootfs release date I think we should leave it up to the chefs because I think it will be hard to find out in many cases. Reason is rootfilesystems get passed on 20 times...
In case of the kernel release date it might be a good idea to add it. should be easy to find out. When you grab the kernel e.g. from the two sources I link to in the thread
http://oe.netripper.com/files/htcleo_autobuild/
http://cotulla.pp.ru/leo/Android/
you can just copy paste the date from filename or information on the site. This would be very useful assuming the kernel images will be removed at some point.
On a side note: For both kernel examples the source code repository to add in readme.txt is
git://git.linuxtogo.org/home/groups/mobile-linux/kernel.git htc-msm-2.6.32
gitweb: http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm-2.6.32
So currently in every leo rom readme.txt this must be linked to as kernel source reference. netripper autobuild zImages using this exact source code and cotulla zImages share same codebase (although currently the latest changes are unavailable but will be added in git soon)
shufflez said:
And a title format like: [date]-[name]-[version]-{[kernel]-[kerneldate]}-{[modules]-[modules-date]}-[rootfs] (just like rules for 'regular' roms). Both for the post and the archive preferably?
Personally I switch between versions a lot, to find differences/improvements/bugs.
Clear archive-naming should simplyfy this .
Click to expand...
Click to collapse
To me that seems over exaggerated. Rom version in file name should be enough. Rest can be looked up in readme.txt
So what does everybody think? If we add the release date of kernel and completed rom, do we have an agreement ? In that case we should compile an example and add it in the first post.
best regards
your right dcordes too much information in the title can be a bad thing. Something more like
[Date] [Name] [Version] [Build] [maybe Kernel version]
That should be Enough i think so for Example
[21/07] [Darkstone1337] [v5] [Eclair w/sense] [2.6.32]
Everything else should stay a change log for people to read
David Balfour said:
your right dcordes too much information in the title can be a bad thing. Something more like
[Date] [Name] [Version] [Build] [maybe Kernel version]
That should be Enough i think so for Example
[21/07] [Darkstone1337] [v5] [Eclair w/sense] [2.6.32]
Everything else should stay a change log for people to read
Click to expand...
Click to collapse
I am sticking with my opinion:
*in filename require internal chef rom version
*in readme.txt add:
-rom release date
-kernel release date
Mark what do you think? Any other opinions?
Install to folder
May be a good idea install all files to appropriate folder, not directly root of SDcard as in last darkstone FROYO. Greatly simplify process of testing and changes between several images and don't messy root. Switching between different versions is than as easy as renaming directory.
I think we should also leave directory structure etc to the chef as long as readme.txt with all the required information exists in archive root so users can find it easily.
so do we have some agreement here? Mark ? If so you should update the first post to compile final set of information needed and clarify that it is not a nice extra but a requirement.
dcordes said:
I am sticking with my opinion:
*in filename require internal chef rom version
*in readme.txt add:
-rom release date
-kernel release date
Mark what do you think? Any other opinions?
Click to expand...
Click to collapse
I agree with you on this theres no need to make things more complicated than they need to be. Although there does need to be some sort of standard for the thread title.
And no I cant think of anything else right now that needs to go in.
dcordes said:
I think we should also leave directory structure etc to the chef as long as readme.txt with all the required information exists in archive root so users can find it easily.
so do we have some agreement here? Mark ? If so you should update the first post to compile final set of information needed and clarify that it is not a nice extra but a requirement.
Click to expand...
Click to collapse
Also agree that its upto the chef how they want their files set up as long as its clearly stated in the readme.txt what to do to get it working.
Everything sounds fine What needs adding to the first post to make it complete?
Sorry I have been working on my Loader but its all finished now (I hope).
Mark.
HD2 Android Image & Instructions
Hi All,
Can somebody confirm if there is a working Android image for the HD2 yet? From reading previous threads, it would seem there is still some technical challenges, no image is available yet.
If I am wrong, please could somebody tell me the location of an image and instructions so I can install Android on my HD2? I am struggling with WM6.5 and I much prefer Android. I have used WM for 9-years now but it just doesn't compare - partially because there are limited decent apps available.
All the best,
Youdaler
youdaler said:
Hi All,
Can somebody confirm if there is a working Android image for the HD2 yet? From reading previous threads, it would seem there is still some technical challenges, no image is available yet.
If I am wrong, please could somebody tell me the location of an image and instructions so I can install Android on my HD2? I am struggling with WM6.5 and I much prefer Android. I have used WM for 9-years now but it just doesn't compare - partially because there are limited decent apps available.
All the best,
Youdaler
Click to expand...
Click to collapse
I will just give you a friendly warning this time as it is your first post. This thread is for the discussion of information to be included by Android builders.
If you look in the Android forum then you will see working builds by DarkStone and by Dan1j3l. Look at their threads for how to load Android. to answer your question yes Android does work (95%) on the HD2.
Please confirm you have read this so I can delete these posts and keep the thread clean. In futured please only post in the correct thread and if you arent sure then post in the Q&A thread at the top of the Android forum.
Mark.
Understand. Thanks for clarifying.
I think we should extend the readme.txt items with some section like 'expected issues' or 'known problems' .
And in the readme.txt , could help too:
Tested with:
-WinMo rom x.xx.xx
-Radio rom 2.xx.xx
Sent from my HTC Desire using XDA App
Information:
PLEASE USE THE SEARCH FUNCTION. Your question has already been answered. Use Google or the search function above. The Google link is a template for quicker searching of this site.
NC=Nook Color
stable=latest stable rom from Cyanogemmod. Your go-to ROM if you just want a good daily driver and do not want to worry about things not working.
nightly=the latest and greatest. Please only try if you are able to troubleshoot, understand basic computer concepts, are not a N00b.
N00b=A word I hate and you should never use. Please do not say I'm a noob that needs help. Simply ask can I please have some help.
rooting=This is NOT FLASHING A ROM. It is the act of taking a stock rom and installing super user privileges. Installing CM7 is NOT ROOTING.
CM=Short for Cyanogenmod. The amazing team of developers that make what you're reading and wanting to do possible. Thank them often and donate any way you can (in help, money, coding).
OP=original post (post #1 in a thread)
OC=overclocked
HC=Honeycomb
AOSP=Android Open Source Project
SD=SecureDigital storage (that little card that goes in your NC)
eMMC=internal memory (the "hard drive" of your NC)
ROM=the "operating system"
kernel="Translater" between your ROM and the NC hardware. You need the overclocked one to overclock. Flash after a rom is flashed. THERE WILL BE NO OC KERNEL FOR THE DEFAULT CM ROM, EVER. OVERVOLTAGES OF THE KERNEL WILL NOT BE INCLUDED.
FC=force close, or when an app crashes
SOD=sleep of death. When the NC will not wake from sleep. You need to hard shutdown, then reboot to fix this.
PBD=premature battery death. When the battery shows 3x-20x% battery life left, but shuts down without warning. This has been linked to people who updated their bootloader without first flashing to 1.2 stock and letting the battery drain all the way down. This is being looked into. You need to plug in your NC if you experience this.
Click to expand...
Click to collapse
Kernel Issues with CM7 stable:
Flashing OC kernel results in "ANDROID" hanging/bootloops on boot. You need to change the updater-script to ext4, or use this kernel. Here is information about the filesystems used.
Which OC kernel can I use with stable? The latest test (4/24) can be used. Both need the updater-script to be changed to ext4. Look here for information.
Please ensure you are running the latest Rom Manager and Clockwork Recovery. This will also fix problems with the kernel not loading and being stuck at "_ANDROID". Open market, download Rom Manager, install it, then flash the latest recovery for the NOOK COLOR (not NOOK COLOR (OLD), if that is still there). Now update your kernel/ROM.
I want to install an OC kernel to my SD rom! Head over here, Racks has all the kernels you could want.
Click to expand...
Click to collapse
CM7 Nightly Issues:
What overclocked kernel do I need?? The latest from dalingrin should do. Please read and understand (and use the search function) if you have questions/concerns. You're looking for the 5/23 .32 based kernel. Some may have issues with wifi, however.
I want to run this off of my SD card, not internal (eMMC) memory. Look at Racks for the answer.
Is it worth my time to upgrade to the latest nightly? You can check here. Changes specific to encore (the code name for the nook color) will have a slightly darker background, and if that is an issue you've had, it may be fixed now!
I want to run netflix on the NC! Download the netflix app and follow these instructions to have it run. If you don't know what it's asking to do, ask here!
I need the new uboot everyone is talking about! Get it here.
I want to try out USB Host support (VERY EXPERIMENTAL). Look here, read EVERYTHING, understand what you are doing!
Click to expand...
Click to collapse
Common Misconceptions/Questions:
Removing system apps (phone, mms, etc) will increase battery life! It has no effect. Stop it.
Using a task manager is a good idea in Android! That's not a good idea at all!
What do all these governors do/mean in setcpu/cyanogenmod performance settings? Look here for a great explanation. Also, DO NOT use setcpu PROFILES in CM7.
How do I install all these things? Check out eyeballer's awesome thread!
Click to expand...
Click to collapse
STOCK: NOOTER Distros:
For 1.0.1 ONLY. Look here.
For 1.1 ONLY. Look here.
For 1.2 ONLY. Look Here.
Click to expand...
Click to collapse
Honeycomb (Android 3.0):
Latest SDK (NOT AOSP) based ROM: Look here.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Thanks for the OP's that saved me from retyping all the answers (Nemith, luciferii, and dalingrin, verygreen, and fattire (and others) that have made CM into the amazing piece of work it is.
Click to expand...
Click to collapse
Reserved for future awesomeness.
This is done with great intentions, but it is not going to work.
We know for a fact, that exactly those people who have questions, and post them in all the worst places, don't read any of the thread titles.
They don't read the information threads, they don't see "DON'T POST IN THIS DEVELOPMENT FORUM" warnings, and so on.
ALSO, this thread is just one more thing to rapidly become outdated - like the sticky thread that has months-old information.
All you have to do is go to a movie, go to sleep, or maybe even vacation, and immediately this has no longer correct information.
And it is one more thread pushing other development threads off the front page.
Fine idea, but it won't work in the real world.
ADude said:
This is done with great intentions, but it is not going to work.
We know for a fact, that exactly those people who have questions, and post them in all the worst places, don't read any of the thread titles.
They don't read the information threads, they don't see "DON'T POST IN THIS DEVELOPMENT FORUM" warnings, and so on.
ALSO, this thread is just one more thing to rapidly become outdated - like the sticky thread that has months-old information.
All you have to do is go to a movie, go to sleep, or maybe even vacation, and immediately this has no longer correct information.
And it is one more thread pushing other development threads off the front page.
Fine idea, but it won't work in the real world.
Click to expand...
Click to collapse
Thanks for the feedback.
I'm going to keep it updated as long as I can. Since I'm on here pretty consistantly. When I can't afford the time to do so, I will pull the information.
I know no one reads these types of threads, but I just had 200+ views in under and hour, so hopefully this solved a few issues without added noise to the real threads.
I think what you're looking to do is make a FAQ or guide or something. Maybe a better place where people can all collaborate (and correct any errors you have made, and I see a few minor ones) would be set up a FAQ page on nookdevs.com or something..
Also, it may be a better idea to organize the bits of information by category so people can quickly find it. Use as few words as you can in the first sentence so that people scanning for their issue don't have to read the whole thing...
Finally, it's "dalingrin"
Geez...if I had a dollar everytime I messed up dalingrin's spelling... :S
Yeah, I figured there would be a few half-truths in there from me not totally understanding what is going on as well as you guys, but feel free to PM or post on here where I can change stuff. I'll try to simplify it as well.
I just read over the OP and holy SH*T that is confusing, no offense. Here are some tips for writing helpful FAQs/Guides:
Space it out. Everything all clumped together in one block of text helps no one. Space it out (ie like this list).
Add titles or headers in between sections (this goes along with the first point) to clearly guide people to where they need to read. People want to read what is pertinent to them; not read an entire block of text and then try to figure out which applies to their case. Help others help themselves.
For all this CM7-specific information, add version numbers in front of bullet points (for the same reason as the previous point).
Ironically, none of your "Common Questions" are actually Questions. Questions end with a "?". What you have are "Common Answers". Insert questions before them so people can quickly decide if reading that particular bullet point is pertinent to them.
[5/10] Since this is all changing at such a ridiculously fast pace, add dates in front of bullet points where necessary (like at the beginning of this bullet point), so people can clearly tell what is outdated and what is new. I really wish Dal etc did this for his threads since a TON of the info in his threads are ridiculously out of date.
Learn to use the [ list ] and [ * ] tags -- quote post #10 of this thread to see what I mean.
Just some friendly tips for writing helpful guides
Also the particular answers in the OP are very specific to the Alpha Test Builds of the last few days.
Those builds, like dalingrin's, are accompanied by FAQs right where the download link is.
The problem is that people talk about these things elsewhere, and even worse, put up mirror links without the FAQ - which just happened with the new Beta .32 build - one guy complained about not being able to download it because everyone else was hitting the same site at the same moment - so a mirror was posted later in the thread without dalingrin's FAQ.
Someone made a wise comment recently that people who cannot find the already posted detailed information, should not be installing these test builds in the first place, as they don't know what they are doing (and they never report enough detail in their bug feedback - such as exactly which build they have installed).
ADude said:
This is done with great intentions, but it is not going to work.
We know for a fact, that exactly those people who have questions, and post them in all the worst places, don't read any of the thread titles.
They don't read the information threads, they don't see "DON'T POST IN THIS DEVELOPMENT FORUM" warnings, and so on.
ALSO, this thread is just one more thing to rapidly become outdated - like the sticky thread that has months-old information.
All you have to do is go to a movie, go to sleep, or maybe even vacation, and immediately this has no longer correct information.
And it is one more thread pushing other development threads off the front page.
Fine idea, but it won't work in the real world.
Click to expand...
Click to collapse
Geez, Dude, you're harshing my mellow. At least Ace is trying to be helpful and doing something positive. Your negative attitude isn't helping anyone.
I for one, would like to say "thank you" to Ace. The OP couldn't have come at a better time as I was a little confused about the new 7.1.0 ROM and "2.6.32" thread was not helping at all. Keep up the good work!
Personally, I would love to see something like this:
7.0.2
Date the below info was updated: 5/10
General Info:
Benefits of This Build:
Common Issues:
How to Flash / Download Location:
Supported Kernels / Download Locations:
7.0.3
Date the below info was updated: 5/10
General Info:
Benefits of This Build:
Common Issues:
How to Flash / Download Location:
Supported Kernels / Download Locations:
Nightly ##
Date the below info was updated: 5/10
General Info:
Benefits of This Build:
Common Issues:
How to Flash / Download Location:
Supported Kernels / Download Locations:
Nightly ##
Date the below info was updated: 5/10
General Info:
Benefits of This Build:
Common Issues:
How to Flash / Download Location:
Supported Kernels / Download Locations:
Other Builds etc
Date the below info was updated: 5/10
General Info:
Benefits of This Build:
Common Issues:
How to Flash / Download Location:
Supported Kernels / Download Locations:
Miscellaneous Questions Not Specific to a Particular Build
[5/10] How do I do X?
[5/10] Where do I get Gapps?
[5/10] Additional Questions
[5/10] Additional Questions
Unfortunately, I have a very limited understanding of all the stuff that is currently happening day-to-day. I run only stables (currently on 7.0.2 flashed weeks ago) for fear that I might mess up my NC because I may have missed a key detail in post #1238 in thread X, Y, or Z. A centralized thread with all this information run by someone dedicated to updating it daily would be a great help to everyone. People like Dal and other developers are busy developing, and rightfully so
Wow...
I dig it!
I'll see if I can start up something that in depth in a bit here...
When updating from 7.0.2 to 7.0.3 are you suppose to use rom manager? Or download the file from PC then transfer it over to SD and use recovery mode to update? Also your suppose to use titanium to back up apps and data only correct just incase. But as far as updating wipe cache and dalvik.... I just want to make sure I'm doing it correct that way all my apps stay. Fyi I'm running cm7 of internal
Actually, it occurred to me that a FAQ thread like this should be in "Nook General Forum", but that your OP, with all the information about nightlies and so on, should be posted to the end of the CM7 User General Discussion thread in this Forum.
That thread is where all these questions come up.
jzibit17 said:
When updating from 7.0.2 to 7.0.3 are you suppose to use rom manager? Or download the file from PC then transfer it over to SD and use recovery mode to update? Also your suppose to use titanium to back up apps and data only correct just incase. But as far as updating wipe cache and dalvik.... I just want to make sure I'm doing it correct that way all my apps stay. Fyi I'm running cm7 of internal
Click to expand...
Click to collapse
Personally, I find that ROM manager is another program that can have bugs, so I don't use it.
I just put the file on my SD card wirelessly using "Samba Filesharing App" (free in the market), and then use Clockworkmod Recovery to install it.
It looks like with many recent changes, it helps to first do "wipe system" and "wipe cache" before installing the new file.
Since our personal stuff is in "data", then I do not wipe that.
I also find that the "nandroid backup" on Clockworkmod Recovery is more reliable than Titanium Backup (same comment as for ROM manager). If you do a complete nandroid backup and then a complete recovery, it brings back everything - all the partitions - so it is a great thing to do when everything is working nicely.
I can't seem to find the latest version of Gapps that you list. I checked throughout the site listed and only see for GB up to 03072011. Did it get deleted?
psychoace said:
I can't seem to find the latest version of Gapps that you list. I checked throughout the site listed and only see for GB up to 03072011. Did it get deleted?
Click to expand...
Click to collapse
Looks like it was just deleted. I'll keep tabs on it.
fattire said:
I think what you're looking to do is make a FAQ or guide or something. Maybe a better place where people can all collaborate (and correct any errors you have made, and I see a few minor ones) would be set up a FAQ page on nookdevs.com or something..
Also, it may be a better idea to organize the bits of information by category so people can quickly find it. Use as few words as you can in the first sentence so that people scanning for their issue don't have to read the whole thing...
Finally, it's "dalingrin"
Click to expand...
Click to collapse
Agreed. Forums for information dissemination are just ****ty beyond belief. We, the NC/xda community, need to either start taking the NC wiki seriously, or fenagle the owners of this fine establishment into upgrading to something more collaborative. No offense, but the only thing worse than forums for a large community is an email mailing list. shudder ... lol
Seriously. Forums are areas for discussion. Not Q&A.
ace7196 said:
Looks like it was just deleted. I'll keep tabs on it.
Click to expand...
Click to collapse
You can google the file name to find it hosted elsewhere
I bought my Nook last week and since then i've been trying to learn how to tinker with custom roms and kernels but this subforum is total chaotic and newbie-unfriendly.
We (new users) need a wiki to get some basic knowledge about modding.9
All that stuff is scattered and buried in subtopics, I have took a lot of time just to install CWM on eMMC.
Now I'm running 1.2 rooted on emmc and CM7 nightly on SD, I couldn't get dual boot working on EMMC nor SD.
hirano said:
I bought my Nook last week and since then i've been trying to learn how to tinker with custom roms and kernels but this subforum is total chaotic and newbie-unfriendly.
We (new users) need a wiki to get some basic knowledge about modding.9
All that stuff is scattered and buried in subtopics, I have took a lot of time just to install CWM on eMMC.
Now I'm running 1.2 rooted on emmc and CM7 nightly on SD, I couldn't get dual boot working on EMMC nor SD.
Click to expand...
Click to collapse
There is a Wiki stickied to the 1st page of the general section of the Nook Color Forum......http://forum.xda-developers.com/showthread.php?t=890549.
Ace created this thread in response to a rash of redundant questions.
OK, this is beginning to give me the s**ts. Where are all the sources to the stuff that is being posted up here? I have been trying to build (rebuild) some of the ROMS on here, if for no other reason than to check there is no dodgy code in them, but also to learn from what everyone has done.
This is supposed to be a DEVELOPMENT forum, where source code is shared and discussed. Not a bazaar where the posters do a bit of hocus-pocus putting together roms from binaries of unknown source code. They fall like crumbs from the majestic sages, that do even more unknown hocus-pocus and cast them down to the unwashed masses to oooh and aahh at, as they give homage to the great compilers in the sky. What is this? Job security?
I have no idea what the legals are around this and I don't really care. The point is that the spirit of the GPL is you post sources (or patches against standard sources) along with any binaries. The binaries are only there to save us the bother of recompiling. The source is what is important in this forum. How else are others going to improve on the code if they can't see it?
I have posted on a couple of threads and/or contacted various people on here, most of whose response is "oh I didn't compile the actual source code, I just stuck it together from the binaries". One of them (thanks kevinlekiller) was kind enough to at least give me rundown on what he did (as best as he could remember - bit of a worry!), but even he didn't have access to the source code. Maybe I haven't looked in the right place, but it shouldn't be this frigging hard - it should be front and centre.
If I had my way, I would ban every ROM post that didn't have a clear link back to all the sources. That's what github etc is for!
Please, please, people, post the source first, binaries can be an afterthought. If you don't have access to the source code, then I reckon it shouldn't be here - who knows what in there? One of these days someone is going to innocently distribute some nefarious program with a ROM. It really isn't that hard to compile a ROM - takes about half an hour on my Linux laptop.
This is actually standard xda-developers policy: see http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45 but seems to be widely ignored.
OK, I'll get off my soapbox now.
Edit: I realise this doesn't apply to everyone, some people are great about posting sources.
Wrong section buddy
Sent from my GT-S5830 using xda premium
djsky2011 said:
Wrong section buddy
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
Huh? You're joking right? I'm discussing the sources not being available in this section, the source is a development topic. Hmm maybe this is such a common complaint that there is a separate section created for it. Sorry I'm getting crabby.
What section should it go in?
You take 30mins , mine takes 2h - it's different for everyone......
Furthermore , if they're basing a ROM off a ROM , what sources are there to be published ?
Furthermore , the sources can already be found online if you want CM7/AOSP:
http://github.com/teamhacksung/android_device_samsung_cooper
Herpderp Defy.
ok man make a rom then talk to us. most of roms here are like this u got new app,launcher and theme voila new rom is posted(no offense).so they cant give you source code.they make roms from the prebuilt ones like using stock or cm7 as base .most of the developers which made roms from source code had there github accounts link in there username ok i agree there are one or two developer who dont share but that dose not mean everyone here is just like them.ok
1.i can make a rom.
2.but i will not make a one unless i compiled it from source code.
3.sure i will share its source code.
i agree a little bit with you
EmoBoiix3 said:
You take 30mins , mine takes 2h - it's different for everyone......
Furthermore , if they're basing a ROM off a ROM , what sources are there to be published ?
Furthermore , the sources can already be found online if you want CM7/AOSP:
http://github.com/teamhacksung/android_device_samsung_cooper
Herpderp Defy.
Click to expand...
Click to collapse
Finally. Thank you! A link to the source code (actually the config files is just what I looking for).
So, since I have your attention, I see a couple of roms from people like vo-1, what is he doing just compiling the source (I have asked him, no reply)?
On the ROMS based on ROMS thing, while there is technically no source code you put through a compiler - there is still source - it is a list of all the changes made to that ROM.
I also can't believe people don't seem to use any sort of build environment - as in a build script - how else are we going to document what's been done and/or recreate it?
xdaboy122 said:
ok man make a rom then talk to us. most of roms here are like this u got new app,launcher and theme voila new rom is posted(no offense).so they cant give you source code.they make roms from the prebuilt ones like using stock or cm7 as base .most of the developers which made roms from source code had there github accounts link in there username ok i agree there are one or two developer who dont share but that dose not mean everyone here is just like them.ok
1.i can make a rom.
2.but i will not make a one unless i compiled it from source code.
3.sure i will share its source code.
i agree a little bit with you
Click to expand...
Click to collapse
Yes I agree this does not apply to everyone. Some people do post source. I suppose my frustration was the source seemed to be forgotten and it shouldn't be so hard to track it down. Maybe I have spent too much time in the Linux world, where source code is king.
I will kick off a make on the source that EmoBoiix3 linked to (thanks mate) and see where we go from there!
A lot of roms here are based off other roms. So much they don't build it themselves, just some editing of the zip.
Other developers merely want to save the technobabble since most xda users are blind to programming.
divereigh said:
Huh? You're joking right? I'm discussing the sources not being available in this section, the source is a development topic. Hmm maybe this is such a common complaint that there is a separate section created for it. Sorry I'm getting crabby.
What section should it go in?
Click to expand...
Click to collapse
still wrong section
this aint a source
this is a discusion so its supposed to be in general section
Should be in general section IMO.
But I fully agree with the OP. It is true lots of ROMs here are "cooked" from other ROMs and are not "developed" denovo. They are "theme" packs.
But for example we have two groups actively working on builds of CM 7.2, they each seem to be building from source and tweaking fixes in. It would really help if everyone used github. Pull a source, build, fix and commit to your fork. Anyone else can see what you changed, what revision of the tree you used, and can learn from your work and it could perhaps inspire them to fix something else, to contribute back to make *your* build better.
Sharing your code, even if it is just 5 line hack on teamhacksung / cyanogenmod /AOSP source, honours the GPL and helps our community grow stronger.
The GalaxyICS team is a great example, I can see where they've pulled their sources, what (hard) work they've done in what components. They are contributing all their work and knowledge back. And their fixes can be pulled into other projects easily, speeding up development and sharing that knowledge for everyone.
A phone like the Ace continually loses developers as they migrate to "better" phones, and we really need to share as much knowledge as possible to keep our software
Sometimes , changes just cannot be shown.....like framework-res tweaks!
Herpderp Defy.
EmoBoiix3 said:
Sometimes , changes just cannot be shown.....like framework-res tweaks!
Click to expand...
Click to collapse
What sort of tweaks are you thinking of? If it's a replaced image file, then that can be a separate file copied in with a script. If it's a changed text file, that can be done with patch or sed.
Let me give you an example of what I did with kevinlekiller's The End 2.5o rom. He based it on a vo-1 rom and did a fair number of replacing files, odexing etc. I produced this bash script (attached) along with his extra (binary) sources which I think replicated what he did. Self documenting! Everyone can see what is in there, maybe even change it again.
More details towards the bottom of this page: http://forum.xda-developers.com/showthread.php?t=1440396&page=31
I see where you are coming from and I sympathize. I'm not a developer, because I don't have the time and patience to work on source code , compile , debug etc.
The Rom's we have for the Galaxy Ace are already very good, the developers that have worked on them have/had the time and patience to iron out most the issues. So for me to try to come out with something better would seem futile.
I still like customizing these Rom's to a way that work better for me, and it doesn't involve having to spend lots of time, because like I said they are already very good. So it just ends up that a few files are added or changed.
Is that a bad thing? I think those that think it is should just not use those types of Rom's, everyone has a right to their opinion.
At first when you asked me for sources, I thought you meant the source code, since I already listed everything that was used in the first post. But then I realized you wanted direct sources (links) to those files. This is something I will do in the future, post the links of every file, I agree with you , things should be more documented, it would save everyone time instead of trial and error and possibly even giving up.
Anyways, I should conclude here, it is getting a long read.
divereigh said:
What sort of tweaks are you thinking of? If it's a replaced image file, then that can be a separate file copied in with a script. If it's a changed text file, that can be done with patch or sed.
Let me give you an example of what I did with kevinlekiller's The End 2.5o rom. He based it on a vo-1 rom and did a fair number of replacing files, odexing etc. I produced this bash script (attached) along with his extra (binary) sources which I think replicated what he did. Self documenting! Everyone can see what is in there, maybe even change it again.
More details towards the bottom of this page: http://forum.xda-developers.com/showthread.php?t=1440396&page=31
Click to expand...
Click to collapse
nice script, thats for sure
but u shouldnt expect everyone to be as geeky and provide such build script.
theres a big different between "providing source" that is mandatory by forum rules and "providing howto step by step" like in your script.
hell most of the roms (the one that is based on previous precompiled rom) were created 100% on windows machine without even touching linux, and maybe the rom creator (modder) doesnt have any clue what in the world is linux. maybe they even dont know that their windows machine do have terminal (cmd). so arent u asking for too much?
an0nym0us_ said:
nice script, thats for sure
but u shouldnt expect everyone to be as geeky and provide such build script.
theres a big different between "providing source" that is mandatory by forum rules and "providing howto step by step" like in your script.
hell most of the roms (the one that is based on previous precompiled rom) were created 100% on windows machine without even touching linux, and maybe the rom creator (modder) doesnt have any clue what in the world is linux. maybe they even dont know that their windows machine do have terminal (cmd). so arent u asking for too much?
Click to expand...
Click to collapse
Actually I only have 1 windows pc, all my other PC's are ubuntu / linux mint installed on them. I use windows on the main PC because most of my games work on it.
Edit: And, I didn't take offense to your post , it is valid, most people have no clue about linux.
kevinlekiller said:
Actually I only have 1 windows pc, all my other PC's are ubuntu / linux mint installed on them. I use windows on the main PC because most of my games work on it.
Edit: And, I didn't take offense to your post , it is valid, most people have no clue about linux.
Click to expand...
Click to collapse
and no offence intended and sorry if anyone feels my post abit too offending
my point is a rom created from previous precompiled rom can be created 100% on windows machine.
in that case the rom also doesnt have sourcecode because it were created from already precompiled rom.
so if the modder just give a valid link to what he put/change it still suites the forum rules to provide source.
let say i've modded a cm rom, i've include ketuts oc kernel, i've include a launcher, and a filemanger, and a theme.
so if i just provide a valid link to the original cm rom, a link to ketuts oc kernel thread, a market link to the launcher, the filemanager and the theme, thats a valid source because the rom were modded from binary precompiled rom/kernel/launcher/filemanager/theme.
so the link to those binary precompiled rom/kernel/launcher/filemanager/theme is a valid "source".
divereigh said:
This is supposed to be a DEVELOPMENT forum, where source code is shared and discussed. Not a bazaar where the posters do a bit of hocus-pocus putting together roms from binaries of unknown source code.
Click to expand...
Click to collapse
I agree. There are two groups of devs:
"Real" developers. They provide repo links and detailed changelogs.
Modders. They should provide repo links and detailed changelogs.
A repo has the benefit of allowing peer review. Peer review improves code quality just like user tests and their reports do. Afterall, this is what XDA is about.
What I like about XDA is how people eagerly send in "works" notes. Not much information, but better than just trying out and telling nobody.
Exactly guys......it seems cyanogenmod has become the only alternative and devs here are only editing it and bringing out new firmware versions. Some also edit stock roms..........but no one here gave a thought of creating a new genre of custom rom right from source.
biswatmak said:
Exactly guys......it seems cyanogenmod has become the only alternative and devs here are only editing it and bringing out new firmware versions. Some also edit stock roms..........but no one here gave a thought of creating a new genre of custom rom right from source.
Click to expand...
Click to collapse
its not as easy as it sounds, thats why the two main dogs are miui and cyanogenmod.
an0nym0us_ said:
nice script, thats for sure
but u shouldnt expect everyone to be as geeky and provide such build script.
Click to expand...
Click to collapse
I get that. I essentially built an interpreter and a source file (the build instructions). Way too much for most. However I think it would be great as developers if we provided be packaging tools so that others can use them and provide repeatable builds and automatically documented builds ("read the source luke").
an0nym0us_ said:
theres a big different between "providing source" that is mandatory by forum rules and "providing howto step by step" like in your script.
Click to expand...
Click to collapse
Agreed, it isn't mandatory, however for the purposes of educating and peer-review it would be great. So my challenge is to make this easy for people.
an0nym0us_ said:
hell most of the roms (the one that is based on previous precompiled rom) were created 100% on windows machine without even touching linux, and maybe the rom creator (modder) doesnt have any clue what in the world is linux. maybe they even dont know that their windows machine do have terminal (cmd). so arent u asking for too much?
Click to expand...
Click to collapse
So we need a graphical version for Windows..
OK, so here's the thing... I'm kind of new in the Android acknowledgement, so I hope that here will be the place where I will get my answers. So here's what I know...
At first I didn't know that Android was Java-based, using a modified Linux kernel which we all know it's C-based (entirely). After a while, I found that there were different firmwares (ROMs) from the original ones, called Stock ones and also different kernels. After reading lots of info about how things actually are, I've decided to root my stock and then I moved to a custom MIUI for my SGSII with a JB implementation. At first it was great, but I had some issues which left me disappointed. Then I moved on to the official MIUI (China - English one). Things got better after I got used to it. The major bugs disappeared, only small ones left and a few crashes, but in time most of them got fixed. Later it crossed my mind, "Why are there so many different kernels and which is the best one for my phone or ROM to be precise?" Well this is where I need your help. I've read some topics that siyah kernel is probably the best kernel, which fits the MIUI rom. The pointing of concrete kernels isn't the kind of answer I was actually searching for. To be honest, I need answers to questions like:
How many kernels are there ?
Which ones are safe ? (I've read that there are badly written ones, so yeah, it needs to be asked)
Statistically, which is the best kernel and is it for the MIUI rom ?
How can I tell that it's suitable for the MIUI rom ? (Since I've read that not all are)
What are the risks of changing the kernel?
How can you test the kernel's behaviour, an app which makes statistics in time or some other methods ?
Believe me, as annoying this topic might seem, lots of us (the newbie users) are burning up the google servers, just to find these answers. I'm really hoping for a reply spam with answers (if possible , spare the trolling ones). Thanks for reading my annoying topic, anyway
Since most of the source is available, basically anyone can build their own kernel at home, so it is hard to tell how many kernels are there.
what isn`t available as open source are most of the OEM-specific drivers. Samsung, for one, doesn`t make most of the drivers' source publicly available, so kernel developers have to make a binary kernel around the binary drivers and literally pray their work well together.
Siyah is safe, but I prefer the stock kernel (I like the stock ROM... go figure). The stock kernel is the only one that is sure to work properly with all the hardware in the phone, because it is the only built from sources for the drivers as well (read my previous paragraph).
Which ones are safe (other than stock and Siyah): you gotta try them for yourself, read other users' remarks and feedbacks, and so on.
Risks:
Very low. As long as the bootloader is good, if the kernel totally malfunctions, just reboot in download mode and flash something else.
Some app may work very well in one kernel and bomb in another. It may crash in some kernels. It is very empyrical.
The problem is that custom kernels don't undergo the same type of quality testing as stock kernels. Developers have very limited resources to do that, and some developers are more interested in having a short time-to-market than a quality product (well, many large corporations act like that as well). At the end of the day we - power users - are the beta testing and quality assurance teams for the kernel developers.
There is a script with claims to odex a deodexed rom via a flash able script here for those who are interested
http://forum.xda-developers.com/showthread.php?t=2095922
[Script] Amestris Odexer V3.0 [4.1.2] Optimize your phone!
Is it possible for ROM-Creators who are using Aroma (like NeatRom by sale,where I originally liked to post but have not enough posts yet) to include this script into Aroma installer?
Reason for the question is the constant demand of different modifications for guys like sale, so instead to have time further optimizing their roms, providing custom versions of one rom for special demands could be avoided with a possibility like this.
Do not want to start a discussion about pro&cons of odex/deodex and zipalign as theres plenty to read on that topic online.
So let devs concentrate on optimizing their roms and users decide which color they think they need?
Please forgive me if I got something wrong, overlooked a post somewhere or just used the wrong keywords to search on that special topic
Would be happy with a short, technical answer if it is possible or not and why.
FosCoJ said:
There is a script with claims to odex a deodexed rom via a flash able script here for those who are interested
http://forum.xda-developers.com/showthread.php?t=2095922
[Script] Amestris Odexer V3.0 [4.1.2] Optimize your phone!
Is it possible for ROM-Creators who are using Aroma (like NeatRom by sale,where I originally liked to post but have not enough posts yet) to include this script into Aroma installer?
Reason for the question is the constant demand of different modifications for guys like sale, so instead to have time further optimizing their roms, providing custom versions of one rom for special demands could be avoided with a possibility like this.
Do not want to start a discussion about pro&cons of odex/deodex and zipalign as theres plenty to read on that topic online.
So let devs concentrate on optimizing their roms and users decide which color they think they need?
Please forgive me if I got something wrong, overlooked a post somewhere or just used the wrong keywords to search on that special topic
Would be happy with a short, technical answer if it is possible or not and why.
Click to expand...
Click to collapse
I don't think any dev would be willing to incorporate this due to the number of problems it would cause.
If you read the relevant thread you can see what a hit and miss affair doing this is.
slaphead20 said:
I don't think any dev would be willing to incorporate this due to the number of problems it would cause.
If you read the relevant thread you can see what a hit and miss affair doing this is.
Click to expand...
Click to collapse
Yeah, I tried the script myself on sale's rom and it just never worked. I could never boot back into the home screen. The odex me app at modaco worked a lot better than this script - for me anyway.
Sent from my GT-I9300 using Tapatalk 2
AW: [Q] Integrate Odex script into Aroma
Thanks to pardoned I was able to test the odex me app and it just Workshop fine!
Topic can be closed.