It can be quite confusing trying to get a feeling for how stable a rom is when combining 3-4 different roms in the same thread.
It can be hard to see what rom-version the bug is reported from, is it the premium one, the one with manilla or not, the Xtralight?
I can imagine many people that for example are looking for a stable standard VM 6.5-rom would be turned off by all the reported bugs in a thread, even though the bugs are related to a rom with manilla cooked into it.
A popular rom-thread can turn into a big mess really.
A function like subthreads would be awesome, a small thread-tree if you will.
One mainthread and one separate subthread for every different version of the ROM.
It would make things very easy to follow.
Ok, I read the rules, and there seems nothing about necroposting but at least I'm adhering to "1. Search before posting." xD
And this one was the closest I found.
I think now, we don't have the problem so much with combining 3-4 different roms in the same thread atm
but now single threads become just far too big to have an overview (e.g. the big ones like lineageos, etc).
Now single threads contain the conversation since start of the rom until the current state. So there are probably many bugs and posts, which are solved. Also most posts which could be classified for a FAQ are somewhere in between.
I'd say the forum structure is good for the "high level" stuff, distinguishing between models, different sections, and the individual roms.
But inside the rom threads I'd pick up the subthreads proposal
or some form if stack exchange structure,
or at least an optional tree structure.
Especially like @nizzon said, a separate subthread for every different version of the ROM and I'd propose a separate subthread for "rom-specific" FAQ.
What do you think ?
Not really much of a point as you look, at the date of the rom and then go to the first post around that time. No point in having other threads about the older versions of the rom as the dev no longer supports it and all talks about older versions are left out of the thread.
As far as I know, the only software difference between Dream and Sapphire is kernel and driver stuff, neither of which effect themes at all.
So why not get rid of the Sappire themes forums completely and just provide a link (for convenience) to the Dream ones? The Hero themes might be identical as well?
I'm sure there are a few other discussions that can be shared between the various platforms too.
I only suggest this because this website is fairly slow (at least here) and having to search both the Dream and Sapphire themes topics can be quite frustrating.
All of my Oreo themes work for CM so if you are running that version of CyanogenMod you can use my themes for the G1. The same applies to any theme, they are just built for a specific rom, not hardware.
Thankyou for clarifying that. It's exactly what I'm getting at. Dream? Sapphire? Hero? It doesn't matter regarding themes because they are all interchangeable between these models. The themes forums for all 3 platforms (and any others that are compatible) should be merged so that it's easier to locate them.
Actually some Rom's are not yet for all Sapphire builds yet. Like the Hero's. There getting there just not yet
Because if someone comes here wanting to theme their Sapphire, and theres no dedicated section for it, the average person would probably be confused, then continue their search elsewhere.
I'm sure in this day and age we have the technical capacity to still make it seem like there is a "Sapphire themes and wallpapers" section, can simply link to to the "Dream themes and wallpapers" section transparently. I agree that it would be confusing for users to not find such a section at all.
My problem is that we have parallel discussions happening, which is a waste of time. It's also a waste of time having to search 2 sections in order to prevent parallel discussions happening. Why not simply merge them since we know for a fact that all the content within such a merged forum would apply equally to both for the benefit of all?
I agree. This is confusing. There are a LOT more themes available on here than what you see in this area because themes for Magic and G1 are also compatible.
Why don't we use tags for this?
From the FAQ:
Tags
What are tags?
Tags are a useful way to search for threads with similar subject matter and content. This complements the normal search system, which searches only for certain words or phrases and/or posts by specific users.
To use tags, you add words or phrases to threads to help describe the content. For instance, if the subject matter is 'photography' then you can add the tag 'photography' to the tag list. But you could also add tags like 'digital image', and 'camera' (depending, of course, on the nature of the thread).
This will categorize this thread with all other threads that have matching tags, whether or not they have the word 'photography' in them.
Who adds the tags?
Tags are initially added to threads by the user who started the thread. Other users may also be able to add and remove tags.
How do I use tags?
Tags are displayed in a box near the bottom of a thread page. Clicking on a tag will allow you to view other threads that have the same tag - and which may be related. Clicking on the word 'Tags' in the top of the box will take you to an overview page with a 'tag cloud.'
This cloud allows you to see which tags are the most popular - the larger the word, the more times it has been used on threads within the board. There is also another tag cloud on the advanced search page that shows you the tags that have been searched for (or clicked on) the most.
Click to expand...
Click to collapse
We could post a sticky listing the tags in use to be consistent. When you post a theme, you tag it. Relevant data would be:
Type (#theme
Theme name (#remix)
OS (#android)
Compatible ROM+build (#cyanogen4.0.4)
Compatible devices (#hero #sapphire #dream)
Then search tags instead of threads.
Vallyn: that's not a bad idea really. I've noticed there's already a convention in place for the title of a thread, which is almost as good as some minor tagging. I'm actually just now transitioning my data over to tags and it's actually a really cool way of doing things.
Convincing everyone to start using the tags can be tricky though. That may or may not be easier than possibly having to modify the layout or even backend of these forums to get a simple link in. /shrug
Hi there!
There are members here who have successfully cooked for the Vogue with each one using the kitchen that he prefers, while there are many others who have researched for hours and still have trouble setting up a kitchen.
Anyone who tried to do this without prior knowledge surely remembers how much effort is needed to learn all the steps, since the cooking process is quite complicated and there are many new things to learn. Even if one managed to setup a kitchen he might still have no idea how to port a new build to the kitchen. I have also found it difficult to learn what exactly do you need to keep from the original ROM that was shipped with the device and which of those old files can we get rid of. And the list goes on and on...
Many would love to enjoy the thrill of building their own custom ROM with the programs that they find useful, and to be able to tweak it the way they prefer.
I'm calling here on all of you who have experience cooking for the Vogue to please share your knowledge here.
If you have a kitchen setup that you would like to share, I'm sure that many members would love to make use of it!
See post #18 for a description of ROM XIP SYS OEM and LANG. Thanks to egzthunder1.
UPDATE 02/18/10
From my own personal experience and as others have mentioned in the first few posts of this thread, the easiest kitchen for a new chef is the PPCKitchen.
STEP 1: You can register at ppckitchen.org and download the latest version of the kitchen. After installing the kitchen you will need to run the updater. It will take a few seconds while it connects to the server. After that you will have an option of downloading different files. In order to cook a working ROM you will need to go to ROM Kitchens\Vogue and download the following Vogue Carrier Kitchen files, Vogue Kitchen Core, Vogue Drivers. (I don't believe you need Generic OEM Kitchen files in the above directory). Of course you will also need at least one of the Windows Mobile builds from the same directory (ROM Kitchens\Vogue).
Although the builds that show up in the updater are pretty new, yet the latest builds will not show up. In the future after having successfully cooked a ROM with one of the more stable builds from the updater, you can go get the latest builds from the PPCK website at Windows Mobile Build Discussions\Test SYS Builds. *Advanced PPCk Users only*. For now I would stick to the builds that show up in the updater.
There are also OEM files that you can download with the updater. These files have different programs that you will be able to add to your ROM. You can download PPCKitchen OEM's, PPCKitchen 240x320 OEM's, Non Freeware OEM's (don't get exited it's only a trial!), and User submitted OEM's. You don't need any of these so you can download them and check if you want the programs that's inside, if not you can delete the whole file from your kitchen folder that's in your PPCK folder.
The kitchen is very easy to use and you can now build a basic ROM.
I hope to add more to this mini tutorial within the next few days.
I agree 100%, I think it would be great if some of the experienced chefs could drop some knowledge on the rest of us, if not only so we can keep pumping out new ROMs for our Vogues.
Head over to PPCKitchen.org they have a tutorial and everything you need to cook roms, its also the easiest to use in my opinion.
As you may have noticed over the past few days, I have been trying to keep the forum a little cleaner by asking people who open new threads with questions to simply ask them in a sticked Q&A thread. This request also falls under that same premise. Please do not open new threads asking questions. Threads should only be opened to contribute to the site (roms, kitchens, skins, guides, apps, etc). Thanks.
Barogi44 said:
Head over to PPCKitchen.org they have a tutorial and everything you need to cook roms, its also the easiest to use in my opinion.
Click to expand...
Click to collapse
I also have been using the PPCkitchen and agree that it's the easiest, but I have found that it's also somewhat limiting and think it would be a good idea if those using the Ervius VK or any other kitchen would be able to help others.
egzthunder1 said:
As you may have noticed over the past few days, I have been trying to keep the forum a little cleaner by asking people who open new threads with questions to simply ask them in a sticked Q&A thread. This request also falls under that same premise. Please do not open new threads asking questions. Threads should only be opened to contribute to the site (roms, kitchens, skins, guides, apps, etc). Thanks.
Click to expand...
Click to collapse
Sorry, didn't mean to make a mess while your trying to clear things up. It must be frustrating, sort of like cleaning up the floor and having somebody walk in tracking dirt on the freshly cleaned floor!
I just thought that this would be a Tutorial type of thread where members could come and add their little bits of knowledge until we would have a lot of info gathered in one spot. Personally I still think that it's not another simple Q&A thread, although your welcome to disagree and to remove this thread if you want. I'm still hoping that this thread will become a guide for all newcomers to cooking.
When I get home tonight, I will give you a heads up on how i use PPCKitchen. I cook for personal use only and don't publish roms. In short, all I do is use is a modified version of Vin's Generic_OEM. By modified, I take out things I don't need and insert things I want. When I used to flash manila roms, this was critical as his MANILA folder has every thing needed. Now that I don't use MANILA (I replaced it it SPB Mobile Shell 3.5.3 (I LUV IT!). When a new WM build comes out, I simply pop them files in the appropriate places and run it. I am currently in love with 23529.
If your interested in what I'm doing, you can start by downloading Vin's Generic_OEM from his 28014 Thread. Just search for Generic_OEM in the thread.
Lewy1 said:
Sorry, didn't mean to make a mess while your trying to clear things up. It must be frustrating, sort of like cleaning up the floor and having somebody walk in tracking dirt on the freshly cleaned floor!
I just thought that this would be a Tutorial type of thread where members could come and add their little bits of knowledge until we would have a lot of info gathered in one spot. Personally I still think that it's not another simple Q&A thread, although your welcome to disagree and to remove this thread if you want. I'm still hoping that this thread will become a guide for all newcomers to cooking.
Click to expand...
Click to collapse
I know what your intentions were and I do not disagree with you. But there are a few things that need to be considered for making a "cooking guide" for this particular section of the site...
*There are only 3 (4 at best) active chefs for this section: Nag, Barogi, vin (if he decides to fully return), and myself. I believe that NFS will not return (personal unfounded belief).
*Most of the above chefs use PPCK. I am not saying that they don't use others like VK, but the info on cooking will be pretty much the same that you can find in the PPCK website.
*There are a slew of tutorials floating around the site (not just the Vogue section, but throughout XDA), which have a lot (and I do mean a lot) of information on how to cook.
*Cooking with other kitchens is far more involved than simply dropping build packages into PPCK. You can even get down to the nitty gritty of hex editing your rom to get more stuff out of it (ie, there is a hex change in the BA roms that allow you to have more ram available).
*Lastly, since the Vogue uses newer style roms (nbh, as opposed to older formats like nbf), learning how to cook from scratch would be kinda a waste of time (believe me, I spent the last month learning how to port a newer rom to the Blue Angel and it isn't as simple as you may think).
One of the mods (I can't remember which one right now) has a series of posts with tools, tutorials, and a bunch of other things needed to cook. What we could do is simply make a one or two post sticky with the links to the different tutorials on xda as well as on other sites (ppcgeeks has a 1100+ pages thread that talks about cooking and porting). I will see if I can get my hands on those and get them in here if that is ok with you.
egzthunder1 said:
One of the mods (I can't remember which one right now) has a series of posts with tools, tutorials, and a bunch of other things needed to cook. What we could do is simply make a one or two post sticky with the links to the different tutorials on xda as well as on other sites (ppcgeeks has a 1100+ pages thread that talks about cooking and porting). I will see if I can get my hands on those and get them in here if that is ok with you.
Click to expand...
Click to collapse
Thanks, that's perfectly fine with me. I have seen most of the stuff that you mentioned and was actually thinking along the same lines as you. If I can I will add my own little bit of knowledge like links to the various kitchens and so on. By the way there is a new kitchen, Oskitchen with new UI by airxtreme (original kitchen by Ondraster). It looks like it will be easy to use and has just been modified for the Vogue, and I'm hoping to give it a try tonight.
Lewy1 said:
Thanks, that's perfectly fine with me. I have seen most of the stuff that you mentioned and was actually thinking along the same lines as you. If I can I will add my own little bit of knowledge like links to the various kitchens and so on. By the way there is a new kitchen, Oskitchen with new GUI by airxtreme (original kitchen by Ondraster). It looks like it will be easy to use and has just been modified for the Vogue, and I'm hoping to give it a try tonight.
Click to expand...
Click to collapse
Yes, I did see that one. I had tried oskitchen before and it isn't too bad (still preferred Ervius though). However, this new UI seems a little more user friendly...
Start out with PPCK. It works well, most users will not notice the limitations.
Biggest thing with making your own ROM's is getting all of the Reg edits that need to be included.
Good Luck! PS Start with build 23529 it seems to be really stable and fast!
First post updated with mini tutorial.
Lmiller1708 said:
Biggest thing with making your own ROM's is getting all of the Reg edits that need to be included.
Click to expand...
Click to collapse
Perhaps we can use this thread to gather up those types of regedits in one place. It would also be good to have guides for new cooks on how to add things like EzInput 2.1 (with working vibration) and Long Press End Key, BT Pan and Alarm functionality (while plugged in). Most of the newer roms have old or incomplete implementations of these features. vin was the last person to get many of these features all together in one place. With the age of the Vogue many of the cooks are trading up to newer devices and much of that knowledge is getting lost.
codf4ther said:
Perhaps we can use this thread to gather up those types of regedits in one place. It would also be good to have guides for new cooks on how to add things like EzInput 2.1 (with working vibration) and Long Press End Key, BT Pan and Alarm functionality (while plugged in). Most of the newer roms have old or incomplete implementations of these features. vin was the last person to get many of these features all together in one place. With the age of the Vogue many of the cooks are trading up to newer devices and much of that knowledge is getting lost.
Click to expand...
Click to collapse
Are you talking bout me ?
egzthunder1 said:
Are you talking bout me ?
Click to expand...
Click to collapse
No sir, not trying to single anyone out. I've tried pretty much every rom released here and on PPCGeeks I haven't tried your latest ones labeled MetroPCS. I'll flash you latest tonight and try it out for a few days.
just uploaded 28230. Try that one and let me know if you like it...
btw, I was joking... don't sweat it. I don't get so easily offended
tharris297 said:
When I get home tonight, I will give you a heads up on how i use PPCKitchen. I cook for personal use only and don't publish roms. In short, all I do is use is a modified version of Vin's Generic_OEM. By modified, I take out things I don't need and insert things I want. When I used to flash manila roms, this was critical as his MANILA folder has every thing needed. Now that I don't use MANILA (I replaced it it SPB Mobile Shell 3.5.3 (I LUV IT!). When a new WM build comes out, I simply pop them files in the appropriate places and run it. I am currently in love with 23529.
If your interested in what I'm doing, you can start by downloading Vin's Generic_OEM from his 28014 Thread. Just search for Generic_OEM in the thread.
Click to expand...
Click to collapse
I don't know if you sent this over via PM but I'd be interested in reading it too. I tried replacing the Generic_OEM.rar in the kitchen folder with the one from vin, but the kitchen won't startup after i do that.
codf4ther said:
I don't know if you sent this over via PM but I'd be interested in reading it too. I tried replacing the Generic_OEM.rar in the kitchen folder with the one from vin, but the kitchen won't startup after i do that.
Click to expand...
Click to collapse
The reason is that Vin's packages are not "kitchen ready". What he posted is in essence a dump of the Mega rom. The packages have to be worked on in a one by one basis to get them to work with PPCK. There is a nice guide on how to do that in the forum at PPCKitchen.org.
Hey Lewy1,
You are off to a good start. I have been giving your idea some thought and if you truly want this to be a "learning resource" for new chefs, you may want to start by describing a few basic concepts as well.
[highlight]ROM[/highlight]
In essence the Operating System with all the necessary files and programs that make up for what you have on your device. This contains things that are general to all devices as well as certain files and folders that are specific to each particular device (hence, the reason why you cannot flash a rom from a Blue Angel into a Vogue and vice-versa). Once a rom is obtained by dumping it, the dump will have a bunch of folders and files, which need to be turned into something "cookable". There exist several applications that can (and must be used) in order to accomplish this.
After all the things in the "dump" are sorted out and manipulated, the rom will essentially turn into 4 main parts: XIP, SYS, OEM, and Lang packages.
[highlight]XIP[/highlight]
The XIP is what holds the core of the OS. This is what holds the Native Kernel of the particular device as well. In order to port a rom to a device, one cannot simply replace the XIP with a new one. The XIP of the new OS must be "implanted" into the XIP of the base rom of the device. The reason for this is that there are many files that can simply be replaced in the XIP, but some must remain untouched as they hold key elements for the proper functioning of the device (Native Kernel).
[highlight]SYS[/highlight]
The SYS folder will have packages with software that the device may or may not need to run properly. This holds things such as the Shell (your UI), Office, core applications, etc. A lot of these packages can be removed from the SYS in order to make space for other apps that the chef maybe interested in having. However, great care must be taken when removing/adding packages since some packages are needed for the device to even be able to boot. Likewise, having too many packages will render the rom un-flashable since most devices have a specific size of rom that they cannot go over. In the case of latter devices, the available space for rom has gone up dramatically. For instance, the Vogue has roughly 90 MB of space for the rom. This is more than plenty to cook a lot of apps without too many issues. There are older devices such as the Blue Angel, where the size of the rom is limited to 32 MB, which forces most cooks to remove packages and compress things as much as possible to even have a bootable rom (keep in mind that most of the time, builds are coming with more and more space requirements).
On top of all this, there are the resolution requirements. Most packages will come with a second folder of a similar name with the resolution added. For example, Base will have another folder called Base_96DPI. The chef will have to be careful on what he/she puts to be cooked as having different resolution packages can make the device either not boot, or look weird (out of scale images) if it does boot
[highlight]OEM[/highlight]
The OEM normally holds fixes and programs that the cook could not fit in the SYS. It also hold drivers, sometimes even Language packs among other things.
[highlight]Lang[/highlight]
These are language and location specific modules. The chefs use the location modules to make roms for different languages and locations. It is usually a four character code that determines which country/language the rom is made for. For instance, 0409 is WWE.
There are many other basic concepts (such as Virtual Memory allocation) that could be discussed, but for now, these basic definitions should help the average person understand what they are dealing with when they see a new set of packages coming out on PPCK,
Hope this helps the cause
egzthunder1 said:
Hey Lewy1,
You are off to a good start. I have been giving your idea some thought and if you truly want this to be a "learning resource" for new chefs, you may want to start by describing a few basic concepts as well.
Click to expand...
Click to collapse
Thanks! Great Info I'll add it to the first post.
Greetings people smarter than I, so here's my problem
I have an HTC M8 (Verizon) Windows Phone. I have done research that shows that the M8 (Both the android and windows version) are the exact same phone with the exception of the windows logo on the back of the case.
I'm interested in (after backing up what is on it) wiping the darn thing and making it an Android phone instead because I miss playing similar games with my friends that aren't available on Windows phone and I thought they were (see Clash of Clans). All of the articles I have found on this forum so far, and others, all start from the point of view of switching to a custom Android ROM from a phone that is already running Android and well...that's obviously not going to work for me. That I know of.
My question is: Is it possible to re flash my phone from the windows phone that it is, to an Android phone instead. Research suggest the SIM card should still work and be unaffected by the OS change, but I'm unsure where to even start after going to HTCdev.com. Or if I should.
Any help is appreciated.
This is the list of OSs that I'm interested in (Specifically Viper and CyanogenMod)
((Apparently I cannot post links yet, so go to phonearena.com slash News Slash Outstanding-custom-Android-ROMs-for-the-HTC-One-M8_id63633))
afaik there is no platform conversion possible so i would not try anything if i where you.
Secondary question from the thread I haven't checked in a while, I'm curious if anyone has actually tried this on this specific phone. From what I have read there is no hardware difference between the android version of the M8 and the WP version. The only difference is software.
So If I were to simply unlock it (Through HTC's approved process) and swap ROM files, why wouldn't this work? Would it brick the phone? Am I crazy?
/for reference I'm actually using a Motorola Droid MAXX for my daily phone, this HTC WP is an extra one I have
//because I like messing with things
///slashies come in three
The hardware is the same except we do not have available the software to make the conversation. You're stuck with WP and there won't be anything in the future. Little to no development on the HTC M8 windows platforms proves as much. Enjoy while you have it.
Reasons why it wouldn't work:
Partition layouts - if different then no.
Processor OTP - chip security, one wrong digit in this .... It's a paperweight.
Between the sbl, OTP, RADIO and security - if it doesn't all tally with each other... Paperweight.
Partitions match - even if they do, between the second and third reason .... Paperweight.
Sent from my HTC One_M8 using XDA Free mobile app