I've gone through all the threads regarding SRS and I'm a little confused as to which one to use - after reading through pages and pages, apparently there were glitches with it and a bundle of patches, so which is the most current, up-to-date and stable version of SRS? Thanks in advance.
Up
Mee to need this info
I believe development has stopped as soon as the WM2003SE arrived.
I don't know which is the latest and how stable it was.
the latest and stable is setup[1][1].ARMV4_9_11_04 & SwitchSR (1[1].4 final).
copy both file to your device with 1.72 rom.
Thanks but where is it?
Related
Does DCD's software work with TCMP; if it does than I'm going to dump the Verizon 6.1 since I'll be able to have MSVC 1.6 and TCMP working on the same device.
Thanks!
I have TCMP working on my ROM so yeah. I think you need a special version tho, as some of the newer builds of Windows were causing issues with TCMP.
thanks - do you know what version of TCMP I'll need? I'm going to start downloading the wiki's so I can attempt to download another ROM this weekend. I don't have to do it now and will need to research this a bit more.
Thanks!
I bet if you searched for TCPMP in this forum, one of the newer threads would list the program compatible with the newer builds of WM 6.1. I have both working on my device.
kdj67f said:
I bet if you searched for TCPMP in this forum, one of the newer threads would list the program compatible with the newer builds of WM 6.1. I have both working on my device.
Click to expand...
Click to collapse
Ah - found it - thanks! I was so frustrated with this update that I didn't run a search for it first.
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
Welcome to an experiment... members only AND FREE online kitchens for CyanogenMod 6.0.0 Release and Nightly builds.
Update: The auto-updating nightly kitchens are now online!
About the MoDaCo Online Kitchen infrastructure
Regular readers will know we've been running an online kitchen for a while, providing ROM building services to AdFree and Plus members. The reason the kitchens have only been available to members is simple - load. The infrastructure required to support kitchens for a large number of users and devices just isn't economically viable.
At the time of writing, the MoDaCo infrastructure consists of four dedicated servers (all running quad core processors with large disks and a large amount of memory). These servers run custom load balancing software designed to ensure that all of the servers are utilised as optimally as possible to provide the best possible build experience.
The experiment
I have set up two free kitchens below to use one of these servers, leaving the other 3 servers load balancing for Ad Free and Plus members. Now, there's a possibility that the free kitchen could become overloaded and collapse in a big heap, but to a certain extent that is the point of this exercise. To get a gauge on the impact of making an online kitchen more widely available. This is a very limited test and won't be extended to all kitchen ROMs.
The kitchen provides both the stable release build and the current unstable 'nightly' build (with update checks hourly).
Is there a difference between the members only and free kitchens?
The biggest difference of course is the allocation of servers in the farm, which equates to speed and availability. The other difference is that the member kitchen can create signed builds, whereas the free kitchen cannot.
Awesome! How do I support future kitchen developments?
Details on how to donate are in the original post at MoDaCo.
Do we post feedback on the CM 6 ROM here?
Only feedback on any issues relating to the kitchen... feedback on the ROM itself should be posted at the CyanogenMod forum.
Anything else?
The kitchens can be found here (unfortunately there's no way for me to embed them into this post) . Enjoy!
P
Very cool, thanks
Cool.
Im an AdFree Modaco Member.
I will really enjoy the nightly kitchen with (maybe?) an old App2sd+ option.
Nice. Oh and have you abandoned sense for nexus? Wanted trackball colours to make it complete
ermacwins said:
Nice. Oh and have you abandoned sense for nexus? Wanted trackball colours to make it complete
Click to expand...
Click to collapse
Not at all, finishing up the new Desire Froyo / Sense port (details) then i'll drop in the bits for N1 support.
P
Thanks for all this information
paulobrien said:
Not at all, finishing up the new Desire Froyo / Sense port (details) then i'll drop in the bits for N1 support.
P
Click to expand...
Click to collapse
thats great, is it possible to get ta support?
ermacwins said:
thats great, is it possible to get ta support?
Click to expand...
Click to collapse
Of course.
P
Update: The auto-updating nightly kitchens are now online!
P
Update: The auto-updating nightly kitchens are now online!
P
paulobrien said:
Update: The auto-updating nightly kitchens are now online!
P
Click to expand...
Click to collapse
Great! (they update same time as the nightly's?) Awesome!
Excellent idea Paul! Suggestion: I've always wondered if it would be possible to save my kitchen selections so I don't have to click all over the place every time I download. Nice work!
Yeah, that feature is coming!
P
AWESOME!
I did a CM Nightly, removed all the stuff I never ever use and now as soon as it downloads I just have to sign it and flash!
I wonder how it'll run.
Or just flash using clockworkmod recovery where signing isn't needed...
P
I am new here, I try to update the Kitchened ROM. But it failed, Error: Status 6.
Pls advise.
Thanks!
Tony
Which options did you bake in / out?
P
Hi Paul... I cooked a (nightly) rom with your "premium" kitchen... but I've got a question: if I try to look for an upgraded version of the rom (through the "Rom update utility") it say that there are no updated version of it.
This happens every night I try.
So... what I have to do to upgrade my nightly "cooked" (clean by all unused stuff ecc...) cyanogen rom? I don't want to upgrade to the stock nightly one, this way the online cooking became useful!
Thanks in advance and... sorry for my bad english, I'm from Italy.
spelverso said:
Hi Paul... I cooked a (nightly) rom with your "premium" kitchen... but I've got a question: if I try to look for an upgraded version of the rom (through the "Rom update utility") it say that there are no updated version of it.
This happens every night I try.
Click to expand...
Click to collapse
Rom manager only checks for the original Nightly zip file. The kitchen adds the selected Gapps into the zip. ( I think )
spelverso said:
So... what I have to do to upgrade my nightly "cooked" (clean by all unused stuff ecc...) cyanogen rom? I don't want to upgrade to the stock nightly one, this way the online cooking became useful!
Click to expand...
Click to collapse
I dont use Rom manager anymore.
Only press: Power> Reboot> Recovery> wipe> install from sd> reboot
Titanium backup for some settings......done
spelverso said:
Thanks in advance and... sorry for my bad english, I'm from Italy.
Click to expand...
Click to collapse
I'm from Sweden....
The kitchen is missing the main ingridient,
the 040411 rom. (001328 rom was ok)
PM sent.
EDIT: Working now.
Hello lads!
Just a quick info thread for the developers of Hermes.
After the installation of 10.08 MIUI 7 Unofficial ROM i occasionally lose contact with Spotify when my phone is locked.
If you'd troubleshoot it, would be nice
Kind regards and thanks for your hard work!
Hey XDA,
i have googled the last days for a solution but found nothing up-to-date.
I'm trying to run a MiUI-Rom on an Android-Emulator for testing purposes. I know that i have to build an AOSP-Rom and patch it for usage with MiUI. But i need a detailed guide how i download and build all components that are required.