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.
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
----------------------------------------------------
I don't know if it's appropriate to post this here.
If not, please remove it.
----------------------------------------------------
I just found that Amon_Ra recovery moved to 1.9.0 alpha, and after some search, I saw no thread about it here. I think this post would help those who always like to taste something fresh, just like me. Sorry for no changelog here, since I have nowhere to find it. Just a download link, and that's all. Enjoy.
Version: 1.9.0 alpha
http://files.androidspin.com/downlo...VERY/&file=recovery-RA-nexus-v1.9.0-alpha.img
NOTE: It's still in ALPHA. While no bug is reported till now, flash it at your own risk. I'm not responsible for any damage you may do to your device, or yourself.
@rambolee: Thanks for the info and link. I flashed it and it works fine, only difference I saw was it had PSFreedom and the color was blue with a Care Bear background.
I have reverted back to 1.7.0.1, more of a choice of preference, I dont like the Care Bear graphic and prefer the Nexus background.
Just sharing my experience with it.
Been posted, just doesn't have a dedicated thread (at least not in the title, since Amon_Ra hasn't updated it yet). RinTinTigger has a thread with this, as well as it being posted in Amon_Ra's own thread.
rambolee said:
----------------------------------------------------
I don't know if it's appropriate to post this here.
If not, please remove it.
----------------------------------------------------
I just found that Amon_Ra recovery moved to 1.9.0 alpha, and after some search, I saw no thread about it here. I think this post would help those who always like to taste something fresh, just like me. Sorry for no changelog here, since I have nowhere to find it. Just a download link, and that's all. Enjoy.
Version: 1.9.0 alpha
http://files.androidspin.com/downlo...VERY/&file=recovery-RA-nexus-v1.9.0-alpha.img
NOTE: It's still in ALPHA. While no bug is reported till now, flash it at your own risk. I'm not responsible for any damage you may do to your device, or yourself.
Click to expand...
Click to collapse
Thanks, for getting this out there.
Anyhow, got some flash instructions?
I already know how, but it would just make this a more solid thread to have the basic instructions for flashing the recovery explained.
Trust me people will keep posting this question otherwise.
Already in the Amon_RA thread just wait to be update by amon_ra
Hi,
I've started to download all the listed tools from AOSP and from Chulri's XDA post but wanted to start the discussion on what steps would be needed to create a gingerbread rom for our Gen8 devices.
My initial questions:
1- Would the driver's source from Archos that are currently written for 2.2 be compatible with 2.3? Can they reasonably be updated?
2- Aren't there two approaches we could use? Update the kernel to be compatible with 2.3 or back port 2.3 to be compatible with our existing kernels?
I apologize for probably sounding ignorant but this is all learning for me and any help is greatly appreciated. If nothing else, this thread would be a great place to discus the steps it would take to develop a Gingerbread rom from a high level stand point.
Mr. Clown - I'd appreciate leaving this in the devel forum since it is specific to devel for 2.3 and gen8 and not just an "is it possible" thread.
Thanks!!
-Nate
double post
sry
do you have kernel dev experience for linux/unix?
if yes concentrate on cm a lot of development has been done.
there are phones who have almost identical components ( well the usb attached screen is a problem)
the recovery will be hell of a problem too..
if you never worked with that stuff (at least i hope you are a c crack otherwise look for other stuff to learn c .kernel development is one of the hardest stuff you can pick in softwaredev.) look for another project where somebody could guide you and teach you stuff the first project will be learning the second could be a very specific project like this where you have to work on your own
Sent from my GT-I9000 using Tapatalk
gbohm said:
do you have kernel dev experience for linux/unix?
if yes concentrate on cm a lot of development has been done.
there are phones who have almost identical components ( well the usb attached screen is a problem)
the recovery will be hell of a problem too..
if you never worked with that stuff (at least i hope you are a c crack otherwise look for other stuff to learn c .kernel development is one of the hardest stuff you can pick in softwaredev.) look for another project where somebody could guide you and teach you stuff the first project will be learning the second could be a very specific project like this where you have to work on your own
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Hi, thanks for the reply. I've been reading just about all of Chulri's posts in his thread and I know $aur0n would answer specific questions if I asked. Other than that, I took a few C++ classes a few years ago but never took the OS/Hardware level classes. I stopped at advanced/e intermediate algorithms and data structures. Either way, I was hoping to start a discussion with this thread about steps that would be needed to happen to build a gingerbread ROM.
But if anyone wants to read along with me about kernel devel then you can start here with me - http://forum.xda-developers.com/showthread.php?p=11261995
Archos's git - http://gitorious.org/archos/
Chulri's How to - http://forum.xda-developers.com/showthread.php?t=891056
Chulri's tool and fantastic following discussion (still trying to comprehend all of it) - http://forum.xda-developers.com/showthread.php?p=10033305#post10033305
Really Thank you for start this thread!
And when you've developed a gingerbread rom, i think the best would be if you work together with $aur0n Do think like i do?
And:
If you need a tester or somebody to do some little things, i'll do it
(At the moment i report some bugs at solune/sauron and test the bootscreens)
I want to help you with that cool project
xnatex21 said:
Hi, thanks for the reply. I've been reading just about all of Chulri's posts in his thread and I know $aur0n would answer specific questions if I asked. Other than that, I took a few C++ classes a few years ago but never took the OS/Hardware level classes. I stopped at advanced/e intermediate algorithms and data structures. Either way, I was hoping to start a discussion with this thread about steps that would be needed to happen to build a gingerbread ROM.
But if anyone wants to read along with me about kernel devel then you can start here with me - http://forum.xda-developers.com/showthread.php?p=11261995
Archos's git - http://gitorious.org/archos/
Chulri's How to - http://forum.xda-developers.com/showthread.php?t=891056
Chulri's tool and fantastic following discussion (still trying to comprehend all of it) - http://forum.xda-developers.com/showthread.php?p=10033305#post10033305
Click to expand...
Click to collapse
i am sorry but you will not be able to develop a kernel with some classes you took i am a dev so i am quite avit with it i come from a completly different backgroud (windows software) but i have a unbelievable hard time to find a starting point with cm7 for sgs although there other developers around
Sent from my GT-I9000 using Tapatalk
That's understandable. If development is going to be tough or near impossible, I'd hope to try before I give up. Right now I'm learning about kernel development but would love it if someone could help me focus.
Is the touch display driver the hardest part to upgrade? What changed in 2.3 that makes updating the driver so difficult? Or would it be better to "back port" 2.3 to be compatible with archos's driver?
Sent from my GSBv1.4-ERIS using XDA App
xnatex21 said:
1)Is the touch display driver the hardest part to upgrade?
2)What changed in 2.3 that makes updating the driver so difficult?
3)Would it be better to "back port" 2.3 to be compatible with archos's driver?
Click to expand...
Click to collapse
1) I would say one of the hardest parts
2) I think the archos drivers aren't compatible, so ...
3) ... this would be better because then you've better drivers support (for each hardware)
Again:
I think this project is assomeI'd love to be a helper/tester.
Attention all rom authors:
Dell Streak Custom Rom List - XDA Wiki
I attempt to keep it as up to date as possible, but as I dont download every single rom I can only work off of what's written in the postings.
Please try and keep your own personal roms up to date,
Correct method of doing so:
Make a new entry to place your rom in, use any of the other ones as a template
Do not delete/overwrite old entries, always make a new one
Date format is always in Month-Day-Year since that's how I had originally organized them (and for no other reason)
If you're really unsure how, you can reply to this thread and i'll add it in if i havnt already
Base rom is exactly that, if it's based on SD, list that it is, and which one.
If there's an error or omission feel free to fix it, but preferably only for your own roms unless you're 100% sure that there's a mistake in someone else's rom
If there are multiple versions, only list the primary one, minor varients should remain on the forum post
If a link is broken and not expected to be fixed, go ahead and remove the link
Do not add guides or other links to it, it should only contain info on the rom itself and download links
Thanks for the reminder. I will modify the Wiki page for any of my further releases. I wasn't aware I could add to it.
It's a wiki, anyone with a forum account can use it (they use the same login info)
I'll be keeping an eye on it regardless of who adds to it (for accuracy and formatting),
But it helps everyone if the rom authors add it themselves first, I dont add things immediately, it could be up to a day or 3 late
Lol, I when I checked the title of this post I had to do a double take. I first saw "Add your *mom* to the wiki list" I was like... Nice....
nvm
Hi,
I am new to android. I have finally rooted my device after a lot of time spending (following the instructions I found in the forum). Now that I have a rooted device, how can I install jelly bean OS (please suggest any other stable software without bugs) on my device and can you please help me out with giving step by step instructions to be followed on how to do it....
gmm8877 said:
Hi,
I am new to android. I have finally rooted my device after a lot of time spending (following the instructions I found in the forum). Now that I have a rooted device, can I install jelly bean OS (or any other stable software without bugs) on my device and if yes, can you please help me out with giving step by step instructions to be followed on how to do it....
Click to expand...
Click to collapse
You can't ask in this forum, "What's the best ROM?" as this goes against the rules of the board. There are many good ROMs and it's a matter of taste and preference. In general the ROMs which are based on the last HTC ICS OTA are the most stable and trouble-free. There are many to choose from that are based on this release, so you'll have to read through the threads and try them out for yourself to decide. As far as JellyBean and KitKat are concerned there are fewer to choose from and all have some type of functionality issues mostly involving Bluetooth, WiFi tethering and camera/video. Every ROM will have somewhere in the first thread or two a list of known bugs / issues and potential workarounds if available. Again, you'll need to read through and determine if the known issues are critical enough to prevent you from trying them out.
Finally, there are several extremely helpful threads with links to important, informative posts that are pinned at the top of the various forums. I suggest you read through them as well as checking out the Amaze Wiki page here on XDA (link at the top of the page) and the "Amaze Bible" page. These host incredible bits of useful information that will steer you in the right direction, so you can fully take advantage of your handset.
Good luck
Ciao
Odysseus1962 said:
You can't ask in this forum, "What's the best ROM?" as this goes against the rules of the board. There are many good ROMs and it's a matter of taste and preference. In general the ROMs which are based on the last HTC ICS OTA are the most stable and trouble-free. There are many to choose from that are based on this release, so you'll have to read through the threads and try them out for yourself to decide. As far as JellyBean and KitKat are concerned there are fewer to choose from and all have some type of functionality issues mostly involving Bluetooth, WiFi tethering and camera/video. Every ROM will have somewhere in the first thread or two a list of known bugs / issues and potential workarounds if available. Again, you'll need to read through and determine if the known issues are critical enough to prevent you from trying them out.
Finally, there are several extremely helpful threads with links to important, informative posts that are pinned at the top of the various forums. I suggest you read through them as well as checking out the Amaze Wiki page here on XDA (link at the top of the page) and the "Amaze Bible" page. These host incredible bits of useful information that will steer you in the right direction, so you can fully take advantage of your handset.
Good luck
Ciao
Click to expand...
Click to collapse
Indeed so.
Thread closed, please no more "best ROM threads."