Related
This topic has been floating around the forums for a long time now. For as long as chefs been cooking, they’ve been trying to cook their “perfect rom.” Well…unfortunately they can’t do it by themselves. They need some help from us…so this thread is for any and all feedback we may all have as users, to offer to our chefs in order to achieve our goal.
Keep in mind guys, we’re all different people, we all require different things. Let’s keep our thoughts realistic and respectful. We’re use to 3 types of roms….Full, Medium and Light (lite.) Let’s see if we can offer up a somewhat standard model and set of applications for each type of rom.
But not just apps….lets break this down to CE builds..OS tweaks…radio performance…visual preferences…..EVERYTHING!!!!
also (i know this is gonna cause an outbreak!....) if there are any outstanding issues you've been having with all coked roms across the board...feel free to mention....The more we're all aware of something the better the chance it will be addressed!
======================================================================================
((Results and conclusions))
-For the most part, we can all agree certain apps should not be cooked in because they're updated too often.
======================================================================================
((Topics and issues))
--------------------------------------------------------------------------------------------
*well i can't edit the poll...so we'll have to do this the hard way. So we have the "to be cooked or not" apps figured out. Next is the model in which the roms are produced. Like i said before...theres usually 3. Lite, Medium and full. We need to define the roll and specs of each and what they contain. Sound Off
--------------------------------------------------------------------------------------------
At the request of mr.dutty i've added a poll. Im not sure if i can do this, but i'll try to switch it up everyday with a new subject everyday or so.
* = current topic
almost was going to warn you to get some flame retardant clothing at first glance. However after reading a bit more it does not seem to be a bad idea, assuming it can be kept free from garbage. Ill put some thought and contribute what i can but not a bad idea.
A few things I look for in a cooked ROM -
Hardware keyboard performance: We're talking about a device that features a very nice full hardware keyboard, and roms should take this into account. I've encountered roms that have laggy keyboard entry, other weird keyboard entry problems, and some which work beautifully.
Careful which apps are cooked in: If an app is likely to get updated frequently, it's my opinion that it shouldn't get cooked into a rom (unless, of course, it's a PITA to install in the first place). There'd be no point cooking PointUI's Home into a ROM, as it gets updated a lot. Also, the legality of any cooked in App should be considered. For example, I'd love to see a rom that's got Opera Mini cooked in and ready to go as the default browser, which is a lot of fiddling around and hard work, rather than a rom that uses the NOT FREE Opera Mobile.
Screen Rotation Speed: Some ROMs have managed to achieve near instant screen rotation speeds, others have not. It'd be great to know what settings affect this, and cook them in.
Options: I hate Large Start Menu. I love the fact that you can easily turn it off without any side-effects. I love the fact that Quick Menu gets cooked in, but you have the option to not use it (I'm firmly in the "loving quick menu" camp though, at the moment).
Most important: Speed. I really don't feel like this device is performing quite as well as it could do. I think we could get there - I think there's still some exploring to do, and at some point there'll be a major breakthrough.
Maybe this thread is the start of all of that?
Thank you For starting this as this will alow us to find out from different individuals thier own opinions and also from different chefs as to how we can maximise the best performance out of this baby kaiser.
At the moment Im trying different stuffs
I don't know to much about this stuff, but in my last month of looking at these forums.. I think a lot of people use these
- Pocket Core Media Player
- SOme form of Registry Edit
- Task Manager (Detialed one, WTask i think it's called?)
- Pocket Screen
- Office (obviously)
- Note pad (love it)
- Touch Settings
- Query Analyzer (maybe not for everyone..)
- Slide 2 unlock (better to get that yourself probably now that I think about it)
- Schapps advanced config 1.1
- KaiserTweak
- Total Commander looks pretty usefull
- Some sort of FTP program
- I wish there was some app for linking HTC favorites in the cube to their contact record (give you option of calling,e mailing, etc, instead of a quick call)
Not very advanced stuff, but stuff I hav efound pretty usefull that i never knew about.
swtaltima said:
almost was going to warn you to get some flame retardant clothing at first glance. However after reading a bit more it does not seem to be a bad idea, assuming it can be kept free from garbage. Ill put some thought and contribute what i can but not a bad idea.
Click to expand...
Click to collapse
lol no worries man. i got my suit bag unzipped and waiting!
i guess i'll give it a go....
me myself...I prefer a Full rom. but it seems very unrealistic as to what’s in a full rom or not. I’ve been talking to dutty a bit about this and he wanted me to get some ideas and get back to him….so I guess this is the place to get it all together. For those of us with a tilt…we all know how fat the shipped att rom was. But the funny thing is…it wasn’t slow at all! This is what sparked my thoughts. How about…a full rom = a bloated rom! But not bad bloated….good bloated. I’m talking about any and all those little apps we all know and love. Such as….group sms…call firewall…opermini (files provided to set as main browser…I think that should be left up to the user,) tom tom...quick menu….Live search and all other live apps, all HTC current apps and dialers….ect ect. I wanted to include slide to unlock, point ui and pocket cm…but these apps are updated too often to cook in….but non the less would be great for a full rom. I believe the cooks can find a way to make a rom like this work!
For a media rom….pretty much the rom…plus all the htc goodies we’re all used to. And the the rest of the inessentials….things like flash lite…youtube already cooked in....ect ect. It should be kept clean and nice.
A lite rom?....nothing! lol…lite roms are for those of us who like to tinker ourselves or just don’t use a damn thing on the phone…so I think it should be just the os! And call it a day.
I think we need to add a poll of some sort to vote on what apps should be included in each rom so we can observe, study and compare what individuals use in thier roms and what they dont like.
dan13l said:
A few things I look for in a cooked ROM -
Hardware keyboard performance: We're talking about a device that features a very nice full hardware keyboard, and roms should take this into account. I've encountered roms that have laggy keyboard entry, other weird keyboard entry problems, and some which work beautifully.
Careful which apps are cooked in: If an app is likely to get updated frequently, it's my opinion that it shouldn't get cooked into a rom (unless, of course, it's a PITA to install in the first place). There'd be no point cooking PointUI's Home into a ROM, as it gets updated a lot. Also, the legality of any cooked in App should be considered. For example, I'd love to see a rom that's got Opera Mini cooked in and ready to go as the default browser, which is a lot of fiddling around and hard work, rather than a rom that uses the NOT FREE Opera Mobile.
Screen Rotation Speed: Some ROMs have managed to achieve near instant screen rotation speeds, others have not. It'd be great to know what settings affect this, and cook them in.
Options: I hate Large Start Menu. I love the fact that you can easily turn it off without any side-effects. I love the fact that Quick Menu gets cooked in, but you have the option to not use it (I'm firmly in the "loving quick menu" camp though, at the moment).
Most important: Speed. I really don't feel like this device is performing quite as well as it could do. I think we could get there - I think there's still some exploring to do, and at some point there'll be a major breakthrough.
Maybe this thread is the start of all of that?
Click to expand...
Click to collapse
point ui makes for a good debate....the reason i would cook it in is because it comes with its own update client. so even if an older version is cooked in....or an update is available a day after the rom is cooked....you just need to go into update and that will take care of that. but i do agree with the idea of frequently updated apps should be avoided.
the screen roatation is another one....i agree. i've seen it vary from rom to rom even within dutty's camp. maybe the cooks can unite and nail that one down.
I've been using different ROMs over the last month or so and what I normally go for is the lite ROM with all the performance updates. Then I add my own apps to it. From the ROMs that have applications cooked into it I may use 80-90% of it which I find is not good for me and I think this holds true for most, if not all users. Everyone has different taste/needs.
Maybe a ROM with just the OS and performance/optimization tweaks and leave the rest up to the users. They can find the cabs for everything so why bother to cook it in. The other thing with cooking in the apps if is if the app gets an update a new ROM is needed.
Or just cook your own ROM. There's enough info within the forums to make your own ROM and include whatever apps you want.
Maybe the focus should be on optimizing the OS and leave the apps to the choice of the user.
ecltech said:
I've been using different ROMs over the last month or so and what I normally go for is the lite ROM with all the performance updates. Then I add my own apps to it. From the ROMs that have applications cooked into it I may use 80-90% of it which I find is not good for me and I think this holds true for most, if not all users. Everyone has different taste/needs.
I think make a ROM with just the OS and performance tweaks and leave the rest up to the users. They can find the cabs for everything so why bother to cook it in. The other thing with cooking in the apps if is if the app gets an update a new ROM is needed.
Or just cook your own ROM. There's enough info within the forums to make your own ROM and include whatever apps you want.
Maybe the focus should be on optimizing the OS and leave the apps to the choice of the user.
Click to expand...
Click to collapse
I cooked a lot of roms but always stick with the full rom, Reason is i could take out 50mb of programs out of a rom and This doesnt give me that equvalent space and also performance sometimes are un-stable, thats my own opinion.
I think there is a halfway line with how much goodies you can install in a rom to please most people
ecltech said:
I've been using different ROMs over the last month or so and what I normally go for is the lite ROM with all the performance updates. Then I add my own apps to it. From the ROMs that have applications cooked into it I may use 80-90% of it which I find is not good for me and I think this holds true for most, if not all users. Everyone has different taste/needs.
Maybe a ROM with just the OS and performance/optimization tweaks and leave the rest up to the users. They can find the cabs for everything so why bother to cook it in. The other thing with cooking in the apps if is if the app gets an update a new ROM is needed.
Or just cook your own ROM. There's enough info within the forums to make your own ROM and include whatever apps you want.
Maybe the focus should be on optimizing the OS and leave the apps to the choice of the user.
Click to expand...
Click to collapse
all good points...i tend to agree with you. but lets not forget we're dealing with people who dont know how to hard slp...refuse to read through 30 pages of posts or even use teh search feature. so a full features rom will always be needed.
rzanology said:
all good points...i tend to agree with you. but lets not forget we're dealing with people who dont know how to hard slp...refuse to read through 30 pages of posts or even use teh search feature. so a full features rom will always be needed.
Click to expand...
Click to collapse
This is true. For a full featured ROM I think a based ROM might be better versus cooking in many apps. Here's a list that I think can be a good starting point for a base ROM. Some utilities, tweaks, visuals, etc. The rest can be managed by the user.
- Advanced Config
- GPS Test
- HTC Album
- HTC Camera (new version)
- NotePad
- Registry Editor
- Pocket RAR
- Office w/OneNote
- PDF Viewer
- psShutXP
- QuickGPS
- Total Commander
- NetCF 3.5
- ClearTemp
- KaiserTweak
ecltech said:
This is true. For a full featured ROM I think a based ROM might be better versus cooking in many apps. Here's a list that I think can be a good starting point for a base ROM. Some utilities, tweaks, visuals, etc. The rest can be managed by the user.
- Advanced Config
- GPS Test
- HTC Album
- HTC Camera (new version)
- NotePad
- Registry Editor
- Pocket RAR
- Office w/OneNote
- PDF Viewer
- psShutXP
- QuickGPS
- Total Commander
- NetCF 3.5
- ClearTemp
- KaiserTweak
Click to expand...
Click to collapse
agreed. can we all agree this should be a common app set?
rzanology said:
agreed. can we all agree this should be a common app set?
Click to expand...
Click to collapse
Thats almost what I got apart from pdf viewer which i left out for user preference with adobe reader
the most popular apps don't have to be cooked into a ROM. every ROM can be a light or medium with everything else added as shared backup files using Sprite or SPB Backup. in another thread, some folks expressed reservations about my idea of Backup Install Packs, but i still think it could work. and no one would be forced to use them. it's something at least worth trying.
after flashing a new ROM, the ROM cooker or someone else could install demo versions of the most popular apps (HTC apps, Resco, SPB, SBSH, Opera, Palm Messaging, Kaiser Tweak, TCPMP and the plugins, etc.) onto their devices. They can then make a backup of their devices and make that backup available to other users. Then if someone installs the identical ROM, they could simply install the entire backup of those applications to their own devices. Users can keep the apps they want and register them with their own serials. They could then uninstall the rest.
that would be my idea. keep all ROMs medium and lite and let users customize them to full status with backup install packs.
PointUI drove me nuts, was nice and pretty, but in the way. Then again, I don't like the Cube either. Perhaps if I set up the cube I'd use it more, mainly for the contacts though - I don't use WMP or HTC's, I use TCPMP.'
I love the apps Dutty has, especially WKTask with its launcher and battery bar, quickmenu is awesome (without the large setting).
PocketCM has asked that it NOT be cooked in so...
IMHO a ROM should be usable for as much user as possible.
For one person S2U2 is a must-have application, but others just don't like it.
So a stable, fast and clean ROM should be the best for everyone.
Everyone can add his favorite apps, or don't add apps if you don't like them!
Just my opinion. (Of course I always go for the LITE variant, cause I just don't use a lot of apps)
What I would like to see:
Pretty much the default set of apps and tools in the stock ROM. Some of general use like pocketrar could be integrated but not much more.
Larger page pool.
What I absoltely don't want to see:
Too many UI changes, trial versions, bloated battery status apps and such.
Basically I just want the latest radio, OS and default apps all in one.
Stuff that's not likely to get upgrades for quite some time like the flash player and flash lite could preferebly be integrated but other than that I don't like too much tweaking, I just want the latest versions of the default stuff and then I do my own modifications and tweaks from there.
thanks for setting this up!! But i agree should install from CABs
No, They're updated too often to even think about cooking into the rom!
We need 1 stable EMPTY ROM. And cabs what have been edited for working on the 1 stable empty rom.
Hey all...
So I have been in the Kaiser forums for about a week now and have played around with some of the ROMs out there. My previous device was a PPC-6700. On that device there was a ROM and an Extended ROM. To the best of my experience, I never played with the ROM, but I did unlock the extended ROM and remove many of the bloatware cabs. I also set up some file (I can't remember the name, but it was similar to the UC option) which would allow my own CABs placed in the extended ROM to be auto-installed. In this way we were able to distribute the phones to employees with only the software we wanted (for instance, with our company cert pre-loaded and TCPMP to play back cisco VMs).
While I understand the interest in "cooking" a ROM to get all the latest and greates components (WM version, Radio, etc.) from the various ROMs into one uber-ROM, I'm not sure I see the advantage of adding in all the additional pieces of software.
From my viewpoint, I would think that a ROM should be as clean as possible, this would present a nice base for users to customize. Instead of "cooking" all the files for other components (plugins, menu replacements, voice command, SIPs, etc) into the ROM, why not just provide these as CABs either within the ROM or as a separate download alongside the ROM?
This would allow not only users to choose what to add, but also allow them to remove an installed CAB if they no longer want to use it or if a new one comes along.
I understand part of the allure of a cooked ROM is that the cook has ensured all the components work together... and in my scenario this would still be the case. The ROM would be qualified and shipped with a certain set of applications, but that doesn't mean they all need to be installed.
Another argument I hear for using a cooked ROM is that all the apps are already installed and it doesn't take time to reinstall all the apps. However, with UC, can you not just load all CABs onto an SD and have them all autoinstall? I am pretty sure you can write a file that will install a set of cabs even from local storage. While I understand that this might take a couple minutes more initially, I think the time saved in the long run would be equal or more. For instance, it might take me 10 minutes after I re-flash a base ROM to load another 15 CABs that I want. But, when a new version comes out of my application, or another application I want to install conflicts with something on there, I can easily uninstall the CAB. Small changes to the configurations can also be made without cooking a new ROM.
Now I fully appreciate all the work the cooks on this site have done. I think their work is great. What I am suggesting is an alternative methodology and one that is certainly not new. I am the type of person who likes a very clean build, but also enjoy the many features that are offered with some of the busier ROMs. I feel that having a base build and then simple a suite of approved or offered CABs make the whole process cleaner.
I am trying to understand how the mindset evolved here to make these feature rich ROMs instead of the alternative. The main argument I have heard is that it is quicker to just flash a ROM with all apps rather than load each one. As I have addressed that above, I don't think that the time savings are significant in comparison to the flexibility of modular CABs.
Perhaps there are additional advantages to the current approach that I have overlooked and I would be interested in hearing them.
tell me your thoughts?
wow......all that writing and all you are suggesting that cooks put out some clean roms? arent those already available?
lmfao flash your own clean rom, flash your own choice of radio, tweak on your own, etc...
Do you ever contribute anything worthwhile to threads or do you just prefer to be a sarcastic jerk?
I realize there are some clean ROMs out there...that wasn't the full scope of the post.
The "clean" ROMs are indeed what I would prefer, however that leaves the user going around hunting for all the applications and additions they desire. (And don't use the argument that the user is lazy if they don't spend the time to do this...after all that is what the "cooked" roms allow the user to be...lazy).
The alternative is the loaded ROM which has everything chosen by the cook. The user can't uninstall a component he may not want, or if it causes conflicts with something else.
The middle ground is what I am advocating...a clean ROM but offered with either "built-in" cabs or a separate repository. This would allow the user to install what they wanted (or install it all...then removing what they don't find useful). This would also allow easier updates in between major cooked releases.
I am not stating one way is definitively better, just that at some point someone decided to cook it all in rather then just offer the cab files, and I am looking for the advantage over my alternative.
What would even be nice (and if I knew how to code for PPC I would look to do it!) would be a little menu app that could manage installs from a repository either on your SD card or even online! So you could browse a list of available apps, versions, and descriptions and load it right up. These repositories would then be what the cooks spent time compiling, even offering "Suites" of applications that complement each other well.
As I stated in my original post I am very thankful for the work that others have contributed here and am not belittling their accomplishments in any way. I am just trying to understand how and why things have evolved to their current situation since, if I were to have the time and knowledge I see my framework as more workable (IMHO).
My personal opinion
That's one of the best presented arguments I've seen in a while Bengalih.
Completely agree with all your reasons for preferring a clean ROM over a loaded one - particularly the ability to update applications as and when a new cab is released. While this is the best answer for you (as you state) and in all probability every person with the willingness to go and look for the latest version of everything, I personally still prefer the loaded ROM. I simply prefer the least amount of time between a Hard Reset and being fully back up and running - in my case as long as it takes me to type in my Exchange server details. I try to cook in applications without any bugs that do what I want, so I won't need that newer version (just want it) and if a newer version does come out I can easily bake it into another ROM and be back up and running from start to finish within half an hour (mostly).
While you're completely correct in everything you say - I'm one of the fundamentally lazy people (seriously, check out my ROM's v1.3 intro - that's the word I use to describe why I built it) and so I tend to prefer loaded ROMs.
the way i see it, we cook a rom to have our ideal base. Things where we meet the minimum. The minimum for me must have HTC home, office, tomtom, the games that I always play, which is a whole variety, pim backup, and battery status. When I have my clean base, I just add my packages, which doesn't even take me long at all. If something screws up, we flash our cooked rom, and we don't have to worry about flashing a clean base and adding all our cabs. My roms include a lot of apps, but thats what I expect from my base. Having cabs doesn't seem as clean. I see your point, but cooking your own rom, you don't feel like trying anyone elses roms because the rom is exactly the way you want it.
Thanks for your reply Stu...a perfect example of how one can disagree with an opinion while being completely civil. It seems many other members of this forum can learn from your example.
I'm still not 100% sure I agree with the time you save by having everything cooked in. As you admit, if you want to upgrade an app you would basically cook a fresh ROM with the new package in it and take up to 30 mins. To be honest I would think that you could load ALL your cabs in well under 30 minutes (the first time) and then it takes about 1 minute to upgrade a cab if a new version comes out.
Of course it depends on how often you do each. If you really find yourself reloading your ROM alot...let's say once a week, you might have saved yourself 10-20 mins each time since you don't need to load CABs. However if you instead wanted to upgrade 4 apps, you have saved yourself 30 mins each time from having to recook the ROM.
I guess another thing I don't understand about the argument for the fully loaded ROM is how often are you really re-flashing your ROM? While I understand someone may do this frequently if they are testing ROMs, how often do you really need to re-flash your ROM once it is running with the apps you like (and/or cooked in)?
Also, I believe your opinion is slanted (and not in a bad way) because you obviously cook your own ROMs. Because of this you can customize it the way you want since you have total control. Some of the cooks on here seem to be people like you who then just turn over their ROM for others to use, while other cooks seem to be making ROMs to please the population. Not saying either is a bad thing...just what I notice.
I haven't cooked my own ROM yet (though I have read through the tutorials). I believe however that even after I have decided on everything I want that I won't cook a loaded ROM (if i cook one at all). I would prefer to just put all the CABs i use in a directory and if i ever rebuild just load them all back on, or possibly create a UC script to load them all off my storage card.
Although I still don't really see the advantage of the fully loaded ROM (unless of course you tend to A) reflash your ROM frequently (for what reason?) and B) Tend to not want to upgrade CABs frequently)... to each his own.
thanks!
thomassster said:
Having cabs doesn't seem as clean. I see your point, but cooking your own rom, you don't feel like trying anyone elses roms because the rom is exactly the way you want it.
Click to expand...
Click to collapse
It's funny you say that thomas... because i feel opposite. I feel that with the cooked ROMs it seems that many things just get dumped into the Windows directory instead of being put into individual Program folders. In addition, with no uninstall option it gives me a non-clean feeling
I see your point of course on just building the base the way you want and it makes sense if you don't feel you will want to upgrade an individual component.
I guess I am generally they type that like to go and get the newest version of an app if it is available and would find the process quicker if i could just upgrade the CAB.
Also, as stated above, once I find a config I like I don't know why I would reflash my ROM on any type of frequent basis.
There are additional reasons why certain applications cooked into ROMs aren't always your best alternative.
This is when certain applications (e.g., TomTom, MobiTV & XMRadio) require specific directories for installation. If cooked into the ROM, it will occupy twice the amount of space, since all files are placed in \Windows and through initflashfiles.dat get copied to other locations (e.g., \Program Files\MobiTV). Chefs that know about this avoid cooking these apps into their ROMs.
As for ROMs & which way is better, it's a matter of personal taste. Some folks prefer different levels of clean, and others prefer different levels of full. Some people won't flash unless a cube is included. It's pretty much why I release 8 different versions...
Thanks _Alex_,
Yes that speaks to my point to a degree.
It seems that most cooks don't use INITFLASHFILES.TXT to move applications to a specific directory (under \Program Files) and just let everything sit in \Windows. I was under the impression that INITFLASHFILES could MOVE the files and not just COPY, so thanks for clearing that up. Would it not be possible to execute some sort of script to delete the unnecessary files from Windows and add reg entries to allow programs to be listed in add/remove? Of course this would be additional work for the cook but would really provide the best of both worlds.
I realize you have alot of time and experience invested in your methods (which we all appreciate). But, it would seem to me that instead of cooking 8 ROMs you could cook a base and then offer CAB installation suites as I mention. With either a custom menu install app like I suggest, or UC scripts the process can be automated.
I am not necessarily suggesting that you change how you do things (since you do it so well D), but I just throw this idea out there in case any experienced cooks, or even newcomers agree with my method they are welcome to give it a try.
thanks for your input
bengalih said:
Thanks _Alex_,
Yes that speaks to my point to a degree.
It seems that most cooks don't use INITFLASHFILES.TXT to move applications to a specific directory (under \Program Files) and just let everything sit in \Windows. I was under the impression that INITFLASHFILES could MOVE the files and not just COPY, so thanks for clearing that up. Would it not be possible to execute some sort of script to delete the unnecessary files from Windows and add reg entries to allow programs to be listed in add/remove? Of course this would be additional work for the cook but would really provide the best of both worlds.
I realize you have alot of time and experience invested in your methods (which we all appreciate). But, it would seem to me that instead of cooking 8 ROMs you could cook a base and then offer CAB installation suites as I mention. With either a custom menu install app like I suggest, or UC scripts the process can be automated.
I am not necessarily suggesting that you change how you do things (since you do it so well D), but I just throw this idea out there in case any experienced cooks, or even newcomers agree with my method they are welcome to give it a try.
thanks for your input
Click to expand...
Click to collapse
The method you describe has been mentioned before in other threads and quite possibly in its own thread. (The topic was UC packs, CAB packs or something like that)
There are three cons with that method:
Which cabs to include are subjective, so it's much easier for an individual to gather his/her own cabs
Creating CABs can be a serious pain in the ass, especially if you have 50 OEM packages that need converting and/or fixing for the specific ROM you're building
Cross ROM / device support, which frequently occurs when CABs are released.
On the other hand, with a cooked ROM, you know it works because the chef ( andhis beta tester(s) ) spent the time to test it on the same/similar device and on a specific OS build. ROMs give a better experience overall because of this testing.
FWIW, I've thought about doing what you mention above waaay back with my first UltraClean ROM, but as stated, serious PITA
*SHRUG* Perhaps I'll re-consider it in the future too...
edit: Alltheway used to offer UC packs. Not sure if he still does on his 4shared folder...
I have, personally, always preferred a clean ROM. Yes, it takes some time to set it up the way you want it but, at least, that way, I am not stuck with applications I do not use. If I were to cook a ROM, I would cook it the way I want it and then distribute it. Most cooks here do just that. I would be happy if every cooks released a clean ROM but that is not possible. If cooking ROMs were a full-time job for these cooks, then, I would definitely demand one. So, the way I feel it, if I am lazy or not good enough to cook my own ROMs then I should stick with what has been released and not complain.
@ sherpa:
Perhaps you should go back and re-read my posts. Not once did I "demand" or "complain" about anything that any cook has put out. In fact more than once did I thank and compliment them on all their work. The fact that you state you would "demand" a ROM a certain way if this was the cook's full time job show that it is you more than I who feel that they are, or might be, owed something from these contributors. I fully realize that many cooks are just putting out their own personal ROMs to the masses, but there are plenty of them out there that are also looking to please the community and offer something different. It was to these people that I thought my message might resonate and someone might want to try something like it. As _Alex_ suggested others have thought similarly at somepoint (including himself), so I am not alone in my thoughts. So before you accuse me of complaining, you should re-examine my own words and yours.
@_Alex_
Thanks for the thoughts. I see all the points you are making. However I would argue that point #1 and #3 happen whichever method you choose. A cook is subjective when choosing which CABs to add to a loaded ROM as well. In addition, a single ROM is also device dependent whether it is fully loaded or not. I feel your pain on point #2 about creating CABs... you helped me out in another thread as I created a CAB of the latest Remote Desktop client (with drive mapping support) from the latest AT&T test ROM. I agree that for the cook that would be an extra effort although in many cases most of the CABs are already out there.
Again, I am making a recommendation as to a new (or old?) way to approach this. It sounds like it would be good for the user, but more work for the cook. Of course the current methods are well established, so even if my idea has merits it would most likely encounter some resistance (and as seen already by some, accusations and ignorance.) I still like the idea of an online (or off) repository with a little front-end on the device. The repository can be loaded with approved CABs which can be loaded and unloaded off the device.
In the long run, I don't think it will matter much for me individually, as I will most likely use an available clean build, an RTM ROM, or maybe cook my own. But in any case, I will stick with CABs, and just hope that the ones i need are available or I am able to create them myself (which is exactly what I did for Remote Desktop).
thx!
Dude, I never accused you of complaining. When I wrote "not complain", I meant it to the general population who complain about what's included and what's not included.
No offense meant, no offense taken then. Based on how this thread started out I guess I was just in a defensive mind-set.
We all good
ok bro bengalish
you are just quiet right , i understand your point and i also think that thought cookers make a great work to interduce a room that is useful for everyone but it still better to get a clean room and that's because a simple reason , you will never be able to make everyone happy because simply everyone of us has his owen taste
but i would like to describe what a clean room means ..
i belive it should contain main updates that everyone will need i mean updates like camera , sound and system etc..
i have to thank you for this rich argue and much greeting for you
and i hope really everyone in this forum can show little respect and kindness for the others
cheers
Yes haam,
I would prefer to see more frequent ROMs that have all the base stuff updated (latest BT, VC, etc). And not have the cooks spend as much time with the additional applications as many people will want to do customization here. To the main point, I think there are alot more people out there who can cook an application CAB then cook a ROM with all the latest drivers properly implemented. In my framework the cooks can focus on an up to date clean ROM and the assistant chefs (many in the community) could work on CABs.
Of course I fully acknowledge that there is a segment here (cooks included) that they want everything loaded from the get go and don't really care about additional customization. If that is the majority then things will stay status quo. If not, maybe we will see more people working on UC or CAB packs or something to that effect.
thanks for everyone's thoughts!
Hi Everyone,
I, like many of you, spend way to much time setting phones up over and over again. Since a big part of this is registry edits, I have built a web site that allows you to check off the registry options you want, which it then uses to create a downloadable CAB file to install that will contain all of those registry tweaks. This makes things completely reversible by uninstalling the CAB file.
Notes:
This is Beta. While I have used it, and it's a very basic process, it isn't commercial software by any means.
If you would like to add a new feature, post in this thread.
You may install more than one cab file created with this tool. Just use different names at the bottom of the form.
Without further delay, here's the site:
<edit> The tool has now moved to nowsci.com. If you have any issues, please let me know. </edit>
http://nowsci.com/registry-changer/
Thanks,
Ben
* hold for updates *
Update 1: HTML now renders mobile friendly, so you can use this straight from your device.
Update 2: Edit feature added.
Update 3: Can now manually specify string or integer.
Update 4 [11/17/2008]: Can now specify the app name for install, allowing the user to have more than one Registry Changer cab installed at any point in time.
Update 5 [03/27/2009]: Fixed some character flaws for input. Preparations for move to a new host.
Update 6 [04/22/2009]: Added a filter option.
The site now has the ability for the end user to add registry entries to the database.
Thank you very much. I believe the "Camera Enhancements" entry is mis-titled. Shouldn't it be Rotate Picture 90 degrees, not 180 degress?
Doh! I will fix that.
Also, just added all the registry entries from the Diamond Tweaks post.
What about the Bluetooth DUN profile adding to the list? - Mike
What's the registry entries for that? Happy to add them, or you can add them yourself now through the site.
What happens if you tweak a registry entry that does not exist on your specific device or rom?
Good question. For the most part, I would guess nothing. If there is nothing on your system looking for the registry entry, then it won't effect anything. That being said, that doesn't mean WM doesn't look for registry entries that aren't there. For instance, the following tweak:
Enable Vision Duration/Disconnect Popup
HKLM\ControlPanel\Phone\Flags2=16
Flags2 doesn't exist by default on most any WM6 phone. Adding it in, enables the disconnect.
Who added the "Mighty" tweaks? Is that a phone? Many of those seem like they should go in Misc. I might clean that up if those aren't specific to a phone.
Would it be possible to have a wiki of descriptions for each of these options? I know I could Google them one by one but I'm sure users would appreciate a single source.
Hmm, not a bad idea. I wonder if there was a spot on the xda wiki I could use for it since I don't have my own. I may end up integrating a detailed description field for each item with a question mark next to it. Unfortunatly I won't be able to define them all since people have added one's I've never used.
OK I have a request. I don't' so much mind tweaking the settings when I flash. However what does drive me nuts and keeps me from flashing is knowing I will have to reconfigure all my email accounts. I just use the default mail program, but what a pain going through and adding my 7 yes Seven email accounts every time I flash my phone. Is there a way to make a cab that would auto input all my account settings? The reason for so many accounts, is I have personal accounts, business accounts, email list accounts, car club accounts, and forum subscription accounts.
It would be awesome to be able to go to a site, or run an app where I could plunk in all my account settings, then create a cab store it to my SD card and whenever I flash, just run the cab and POOF all my accounts are setup.
Unfortunately, probably wouldn't be easy to make a cab. However, programs like Sprite Backup will do this for you. You can selectively restore your mail using SB, however I generally back up my phone once I get things the way I like it, then if anything goes sour, I hard reset, then restore.
any1 made an ultimate tweak.cab? maybe make your diamond seem as fast as a custom rom?????????????
then any hardreset.......
dewey1973 said:
Would it be possible to have a wiki of descriptions for each of these options? I know I could Google them one by one but I'm sure users would appreciate a single source.
Click to expand...
Click to collapse
+1 on descriptions of each cab
Wow very nice! Thanks!
I suggest a field to make a *.cab regarding to any registry path/setting the user wishes (if the user is more technical).
without having to actually add to the public entry list.
This will allow the ability to:
1. not have to wait for the admin to add the specific entry
2. allows the author of the new *.cab to distribute their new edit on the fly.
3. give the admin to log & analyze the entries in the custom field to and determine more of the common *custom* entries the ppl may want. Thus not having to depend on explicit user input and emails all the time.
First - thanks for putting this together!
Quick question - I had it "enable" GPS coded photos...but I don't think it did? Shouldn't I have an option somewhere in my camera menu to activate this once I've installed the .cab? Additionally, I don't believe "enable landscape pictures" and "sport mode" worked - how do I know?
Many thanks!
Oh, and I forgot to mention (not that it matters???) that I'm on an HTC Touch Pro with Sprint - stock ROM. I'm new to all this, so I apologize if this is basic stuff.
I'm thinking about creating an application ( based on GScript ) that allows Rom developers to add the ability for rom developers to run shell scripts after the actual rom is flashed and to allow the user to run some rom-specific scripts.
I don't know if there is any need for this by any of the devs, but i have seen TwistedUmbrella used GScript Lite to add some scripts to his build, so that people don't have to ask the same question on how-to run the scripts ( and commands ) over and over.
Although GScript can be easily used for it I think that a special project could offer much more then this and the actual output can be a lot user friendly when its less generic ( i have done the same for the LucidREM script application which can be found in the market ).
And maybe the ability to run some scripts when the actual rom is started the first time after flashing etc.
If you think this could be useful in rom deployment or you have ideas/feature requests etc please drop a post so i know if its worth the work.
like UC
Kinda like UC for windows mobile (I said kinda)? I suppose it could have its uses. First thing that comes to mind is automatic restoration of sms, wep settings, etc.. after a wipe. One thing I like about the g1 is it so easy to build and customize your own builds in comparison to winmo (from a development standpoint). Well, depending on how you look at it I guess.
Curiously, If a function or program like this existed already, what uses would you get from it.
Edit)
I suppose it could be useful afterall. I drew a blank when I initially read your post because everything I run from a script or terminal for that matter is because I'm not behind a computer. If I'm gonna modify something it can be implemented in the update.zip before flash ect.. but if I'm flashing a new rom and I want the dalvikvm updated, louder sound mod, Odex optimized, etc to be done from the first boot I guess it'd be cool. But usuall i'd implement it in an update.zip. I donno I don't think I'm thinkin creatively enough about its uses.
We could create an easy way to backup/restore sms mms bookmarks etc, which can be started before updating and which will run to restore when the image is flashed.
Automatically create the apps2sd settings etc after a flash.
Or even create "smaller"-distributions which asks if the user wants to download extra applications after reflashing...
We could even incorporate google source projects so that users can look for and report issues from within the app for the given distribution.
An easy way to bring out small updates without users having to reflash or have to do manual stuff
Just shooting out some ideas....
I love this idea, I'm a huge supporter for GScript so this only seems natural. Since I use gscript after wipes/loading custom roms ANYWAY it'd be awesome if the process was automated. Chances are people are going to want to restore previous settings and info when they load new roms. I hope more Rom devs see this. So mildly bumping for notice.
Eventually user support will be deciding for developers to use it or not...
I will have a test application finished in a few days.
I will post the first screenshots tomorrow if i will find some time...
This is a little project i've been working on and i thought it was ready enough to be released into the wild. Below is the readme file. I think it covers everything for now. Before posting please read the first 3 posts - especially post 3 - if it is obvious that you haven't done this i will not respond with any form of help and i don't not expect any of the users to do so either.
----------
Included with this zip file are several .cab, .reg and .xml files that will automatically configure your NRGZ28 energy rom when XDA_UC runs upon first boot after flashing.
Included are the following configuration files
activesync.xml
This will configure your MS Exchange settings. Editing with your personal settings is required. Look for the username, server, domain and password tags at the start of the file
aGPS.reg
Enables aGPS
BackLight.reg:
Sets backlight to auto. There are some other settings included for dim and light off times when on battery and AC power aswell
bt_ident.reg
Sets the Bluetooth Identity. Edit the deviceid line to suit
copy.mscr
Copies files from the copy2root folder to the matching location in device storage. A My Documents folder with My Ringtones and My Wallpapers sub folders have been created already. Place you ringtones and wallpapers in these folders. There is also an application data folder which contains a coreplayer config.xml and a program files folder which contains a myPlayer options.ini. Feel free to create more. Thanks to nrfitchett4 for providing this script.
Del.mscr
This file will remove all unwanted ringtones, wallpapers and any other files you decided to add. Edit as you need to. N.B any readonly files will need attributes changed before they can be deleted.
DisableSenseVsync.cab
Disables Vsync in sense increasing the framerate thus making it faster
HD2MemTweaks.cab
Increase's glyphcache size past the bsb tweaks and advanced config defaults, incrases filesystem cache size and a few other bits. This cab file is optional. Delete it if you don't want it. Thanks go out to g.lewarne for documenting the tweaks
HTCAlbumIgnore.reg
Stops the sense music player playing ringtone files from \My Documents\My Ringtones\ and \storage card\ringtones. Copy the examples
if you want to add to it.
M3PH HTC Location Service Enable.cab
Enables HTC location Service and automatically excepts the TOS
ident.reg
Changes the phones identity at first boot. If NRGZ28 won't make it sensible i'll make it so we can customise it . Editing required. this one is pretty obvious
Palringo.reg
Sets up palringo, sorta, change [email protected] to your user name and it should show up at sign in. All you need to do is enter your password
QuickGPS.reg
Enables and configures QuickGPS with the defaults
Ringtones.reg
Configures the ringtone, sms tone and email tone. Needs some editing but you only need to change the file name for each entry, not the
path. The Ringtone2 entry allows for second ringtone to be added to the list of usable ones so you change them with too much fuss.
Also enables flashing light on sms reception for 5 minutes.
wifi_setup.xml
wifi settings. Edit required. This link should help you set it up (see post 3 for details on how to edit)
M3PH Enable Time Auto Update.cab
Enables NTP
Volume.Reg
Sets the volume levels. You can use this one or export your own from HKEY_CURRENT_USER\ControlPanel\Volume
Windows live.reg
Pretty much configures windows live. You do still need to enter your password and you will also need to do atleast one manual sync before Sense will create the mailbox on the email tab but otherwise it works
Opera User Agent String folder
See the readme.txt in that folder
Sense Folder
If you put your wallpaper in this folder it will be installed as the sense default. Just rename it to sense_wallpaper.png.
Start Menu folder
Copy Start Menu shortcuts here
----------
If you like this or any of my other work click the "donate to me" link above my avatar
----------
REMEMBER THIS COLLECTION OF FILES IS PRESENTED AS IS UNDER THE GNU GPLv2. IT IS BETA SOFTWARE AND COMES WITH NO WARRANTY OR ANY FORM OF OFFICIAL SUPPORT. I, M3PH, SHALL NOT TAKE RESPONSIBILITY FOR ANY DAMAGE OR DATA LOSE THAT MAY OR MAY NOT OCCUR TO YOUR DEVICE.
Change Log
Change Log:
1.1.1 Final
Removed Keyboard sensitivity tweaks
Removed opera memory tweaks
Added more palringo settings
Added Quick shutdown settings
1.1 Final
Updated volume.reg to default to seperate system and ring volume controls.
Removed all tweaks now included in Energy roms dated nov30 and newer. I will leave v1.0 posted for a while so people that like to install older versions still get the benefit
1.0 Final
Added Windows_live_settings.reg. You will need to edit it as prescribed on page 16 but it will work.
Added Improved GPS settings.cab. This is untested by me but i trust scabes24 enough to know he's not going to pass on unreliable tweaks
Improved M3PH Location Service enable.cab: Added an extra registry setting that should trigger Manila to showing it's on. This is doubtful but even if it doesn't the file does work
Added alarm_settings.reg: This is only an example file. You will need to export your own settings but this should be a reasonable starting point
Removed readme.txt: It was a habit a picked up from Linux development practices and was pointless for this project
Removed time.reg permanently because there is nothing changed in the registry when it is enabled.
--- Pre Final releases
Tips and Tricks
What follows are some tips and tricks i have found that i'm not going to include for whatever reason but thought some people might find handy or notes on what settings do what and their options.
Q. Can i delete file xyz using xda_uc because i like to have as much space as possible?
Yes you can. i found this link. All you need to do is create a file in the xda_uc folder with the extension .mscr which contains the following:
Code:
delete \test.txt, TRUE
or
Code:
deltree \test, TRUE
Obviously change test to the file or directory you want to delete. For more details check out the provided link above.
Q. The default wifi.xml doesn't match my configuration and i can't find a resource that tells me what are valid values for the options?
A. See this link and this one. As a note if you use WPA2 you need to use <parm name="Authentication" value="6" /> and WPA2-PSK is 7
Q. The exchange settings in activesync.xml aren't how i like them. Can i change them?
A. Sure can! Here's a link to the documentation
Q. I use a [enter service name here] and i want to create an xml file to configure it when i update my rom. Can i do this?
A. Thanks to microsoft developing WAP provisioning to an incredibly encompassing level you can do almost anything. See this link
Q. I want to make a cab file out of all my changes. How do i this?
A. There are many ways but i think this is the best one i've found because it doesn't involve any third party software and is really simple. All you need is the windows mobile sdk, which can be found here. You may also need visual studio but i'm not sure
Making either is very simple. You just pass a normal XML file to makecab and give it the name of the output file you want. The one trick is that the XML file must be named _setup.xml. If you call it something else, makecab will succeed, the CAB or CPF file will be generated fine, and then it will fail with a cryptic error when you try to use it. Beware, the documentation doesn't make this very clear.
The syntax for making a CAB file is:
Code:
makecab _setup.xml config.cab
Click to expand...
Click to collapse
Q. Wow you really do know a lot about this sort of stuff. How can i learn?
A. Well i don't know that much at all really, i just learn fast. Most of the stuff you see here was obtained from or via this MSDN article: http://msdn.microsoft.com/en-us/magazine/cc500581.aspx
Q. Is there a way to boost the performance of Opera in terms of memory/speed?
A. Yes, this cab will force Sense to unload when launching Opera, allowing for better performance while browsing. (When exiting Opera, Sense will then reload) (thanks to Scabes24 for this one)
Code:
[URL="http://www.megaupload.com/?d=O5O1RE97"]Enable Opera Max Memory Tweak.cab[/URL]
Q. I've installed the Opera tweak and everything is working fine, but the page loading seems very slow. Is there a way to improve this?
A. Yes you can, the following registry tweak will enable almost instantaneous web page loading in the web browser. It apparently enables wireless N mode but seems to work with cellular data too. Go to:
HKLM/Comm/BCMSDDHD1/Parms
11nModeDisable = Change from 1 to 0 (thanks to Scabes24 for this one aswell)
Q. My wifi hotspot uses EAP certification and i can't use it because the phone gives me a certificate verification failure error. What can i do?
This was posted in the energy rom thread
NRG, after weeks of not being able to connect to my work wireless network because I was getting a "certificate is from an unknown authority" error, I finally got it working. Can you add this key to your ROMs?
[\HKLM\Comm\EAP\Extension\25\]
"ValidateServerCert"=dword:00000000
This is where I found the answer:
http://social.msdn.microsoft.com/for...-3ebe003aa996/
Click to expand...
Click to collapse
Thanks to oppressa for hunting this one down. The tweak is included as an option in EXCT as M3PH EAP Cert Disable.cab
Here are some locations where 3rd party apps store their values. These were provided by angusc
CodeCity Time settings and Key Code:
[HKEY_CURRENT_USER\Software\CodeCity\CityTime]
Ageye G-Alarm settings and keycode:
[HKEY_CURRENT_USER\Software\ageye\G-Alarm]
Ageye G-Profile settings and keycode:
[HKEY_CURRENT_USER\Software\ageye\G-Profile_v1]
SK Manager settings and Keycode:
[HKEY_CURRENT_USER\Software\sk\smgr]
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Rai\:S KSM]
SlingPlayer Login Details:
[HKEY_LOCAL_MACHINE\Software\Sling Media\SlingPlayer\SlingAccounts]
SPB Language Cards key code:
[HKEY_CLASSES_ROOT\CLSID\{F5C24D33-742A-41BC-BC22-1195BC138ECE}]
SPB Traveller Key Code:
[HKEY_CLASSES_ROOT\CLSID\{7D562A74-A69B-45F5-8D1F-20DABDCE2C76}]
SPB Wallet Key Code:
[HKEY_CLASSES_ROOT\CLSID\{A79D1B0D-2F6A-4E7E-AF94-5EEBC8BFD684}]
Sprite Back-up Key Code:
[HKEY_LOCAL_MACHINE\Software\Sprite Software\Sprite Backup]
RSS Hub Settings and Feed Storage Locations:
[HKEY_CURRENT_USER\Software\Ilium Software\RSS Hub]
SPB Traveller Settings:
[HKEY_CURRENT_USER\Software\Spb Software House\SPB Traveler]
Today Wall Paper Location:
[HKEY_CURRENT_USER\Software\Microsoft\Today]
KeyBoard Config by Tarkim (Settings):
[HKEY_LOCAL_MACHINE\Software\KeyboardConfig]
Resco Explorer Settings:
[HKEY_LOCAL_MACHINE\Software\Resco\Explorer]
Palringo Settings:
[HKEY_CURRENT_USER\Software\Parlingo\Settings]
Click to expand...
Click to collapse
The FAQ
Q. Will you include xyz tweak for me?
A. Only if it's a common one or one that i haven't thought of
Q. I use xyz program and i want to have the config file included in your great collection. What do ya' say?
A. See above but you could always spend 10 minutes tracking it down and then creating a folder in copy2root for it
Q. Why is the bluetooth identity the only tweak for BT you include?
A. Because everyones setup and hardware is far too different for it to be worth it. Also, Although you can export the pairings importing them may not be possible due to the way the bluetooth security protocols work.
(More To Come)
Happy to try this, thank you for cobbling everything together.
wow
this would be so handy, i hate spending time making your phone how you like it. I don't flash as often because i get too comfortable with the current configuration.
thanx M3PH
btw: without NRGZ28 i would have sold my HD2 7 months ago
grumpylad said:
Happy to try this, thank you for cobbling everything together.
Click to expand...
Click to collapse
No worries. I did it because i was getting annoyed with spending ages setting everything up and even more annoyed with people not reading the energy rom FAQ properly (i'm guilty of that too). I used the pre-release version last night after flashing the latest energy rom and it saved me in the region of an hour to an hour and a half. It's not perfect by a long way. Things like the sms led notification is enabled and some people may not like that but is is easily reverted with bsb tweaks.
My plans for the next version is to have all the reg files converted in to cab files for they can be removed and i'll tidy up the readme a bit.
One thing i would like help with though is the FAQ. Can the first few people take notes of any problems or questions they have and things or that nature.
Thanks everybody
Thank you, I'll try it out with the new Energy release. I'd be happy with the reg files to import it doesn't even need to be a cab!
Thanks!
lantern20 said:
Thank you, I'll try it out with the new Energy release. I'd be happy with the reg files to import it doesn't even need to be a cab!
Thanks!
Click to expand...
Click to collapse
Cab files are better because they can be removed and Reg files can't. So if one of these files causes a problem your stuck and that's why it's labeled as alpha software. Also labelling it as that will scare off the less experienced users from trying it and doing themselves a mischief.
V0.2 will be all cab files as far as possible but don't expect a release until 0.1 has had a thorough real world testing.
oh. it is better ,if i find this post eight hour ago.
it drives me nuts ,everytime i get into a new nrg rom.
thank you very much.
Great idea man, thank you so much for this!
Thanks a lot for this! It will definitely save me a lot of time after a rom update. I just have to hope I've set them up correctly and dont break something
Hello
This project is a very good project, I hope is work well
Is it compatible with other language ?
Ex : "Start Menu" folder in WWE Rom is "Menu Démarrer" In FR
Good luck.
@+
diamond_cbr said:
Hello
This project is a very good project, I hope is work well
Is it compatible with other language ?
Ex : "Start Menu" folder in WWE Rom is "Menu Démarrer" In FR
Good luck.
@+
Click to expand...
Click to collapse
no sorry as it stands it's wwe only. If you want to convert it to french and send it over to me i will post it.
yeoldgreat, if you would like to pm me your changes i will look them over.
Overall i'm really pleased with the response so far but i really do need everyones help with composing the faq because for me this works fine (apart from the unteseted bits because i haven't used them yet) so can all of you please, please, please make some notes on your progress and keep posting those questions
M3PH said:
Overall i'm really pleased with the response so far but i really do need everyones help with composing the faq because for me this works fine (apart from the unteseted bits because i haven't used them yet) so can all of you please, please, please make some notes on your progress and keep posting those questions
Click to expand...
Click to collapse
My temptation would be to assume that the FAQ is written for me if I can install and get it working anyone can. For instance in the wifi detailing where the various parm's can be found would make it much easier to install. Very happy to install on what you have and pass back any questions assumptions.
As I frequently flash(ROM's only) I can help with refining the documentation.
grumpylad said:
My temptation would be to assume that the FAQ is written for me if I can install and get it working anyone can. For instance in the wifi detailing where the various parm's can be found would make it much easier to install. Very happy to install on what you have and pass back any questions assumptions.
As I frequently flash(ROM's only) I can help with refining the documentation.
Click to expand...
Click to collapse
Sweet, thanks. That is exactly the sort of thing i'm looking for, because it's been over a year since i did any kind of manual writting i'm pretty rusty. It also doesn't i developed most of the parts in just over 24 hours working on my phone and not my pc everything is a bit scattered in my mind. That's the reason why the readme looks the way it does. It all came out in a bit of a splurge.
The wifi script is one of my older scripts and it took 3 attempts to get right and now i can't for the life of me find the resource on ms technet that i used.
I'll probably have a sitdown over the weekend and have a rerun through the readme and make it a bit more detailed. If i can make it as easy to install as possible then the faq won't be such an important thing
How many people want me to include a coreplayer config.xml in the next version? i've got one that works perfectly with myplayer and turbo3d.
Nice Work
I used a number of these to flash the latest Energy Rom and it worked out great. Very smooth! It will be interesting to see what is added on in the future. Thank you for putting the time in and starting a new thread.
jamesdee said:
I used a number of these to flash the latest Energy Rom and it worked out great. Very smooth! It will be interesting to see what is added on in the future. Thank you for putting the time in and starting a new thread.
Click to expand...
Click to collapse
I'm taking suggestions for additions. So how about one?
Very interesting sir!
I am going to flash the new Energy ROM either tonight or tomorrow and so will chuck this in with it.
I wont use several of them as I dont use those aspects, but those I do will return with feedback.
I have been frustrated with this as well.... fingers crossed.