PPCGeeks Forums HTC Arrive HTC HD2 HTC Thunderbolt HTC Touch Pro 2 HTC Evo 4G HTC Evo 3D Samsung Galaxy S II Motorola Droid X Apple iPhone Blackberry
Go Back   PPCGeeks > Windows Mobile > Windows Mobile Development > ROM/Kitchen Development

Notices



Closed Thread
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 02-24-2007, 10:15 AM
Glossman's Avatar
Regular 'Geeker
Offline
Pocket PC: HTC SuperSonic
Carrier: Sprint
Location: 34 50' 47" North, 119 8' 55" West
 
Join Date: Feb 2007
Posts: 484
Reputation: 800
Glossman knows their stuffGlossman knows their stuffGlossman knows their stuffGlossman knows their stuffGlossman knows their stuffGlossman knows their stuffGlossman knows their stuff
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
PPCGeeks Unified ROM Project: Task 1 (PROJECT TEAM ONLY)

SINCE THIS IS AN OFFICIAL PROJECT "WORK" THREAD, PLEASE DO NOT RESPOND IF YOU ARE NOT A MEMBER OF THE UNIFIED ROM PROJECT TEAM. FEEL FREE TO START A NEW THREAD, OR PM ME IF YOU WANT TO COMMENT ON WORK DONE HERE.

Task 1 involves the selection of the base 3.5 ROM. During the planning phases, two ideas emerged for choosing a ROM: Selecting the "cleanest" ROM from all of those available, or starting with a brand new kitchen.

If an existing ROM is chosen, here is the likely process:

The team, led by the ROM Analysts, would begin looking at every existing 3.5 ROM. A list would be compiled of all known defects for each ROM. The best to way to this is to scour the boards, as well as discuss it with the author. Since many of the ROM authors are team members, it will be helpful if they "share their bugs" with the analysts. Once we have a good picture of all the ROMs in the wild, a choice can be made.

If we start with a brand new ROM, we'll still need to catalog the defects, but we would be in complete control of it's contents and can document every change along the way. This method will likely take longer than the other, but I believe it also ensures the best quality.

The choice is yours. Existing 3.5 ROM or brand new 3.5 ROM?

I will create Project Task 2 once a decision is made on how to proceed.
__________________
How to recover your Diamond from a hang at the boot screen!

Audiovox Thera-Samsung i700-Verizon PPC 6600-Sprint 6700-Sprint Mogul-Sprint Touch-HTC Touch Diamond-HTC Hero-HTC SuperSonic (EVO)
  #2 (permalink)  
Old 02-24-2007, 10:36 AM
sfaure03's Avatar
Regular 'Geeker
Offline
Location: dallas
 
Join Date: Jan 2007
Posts: 344
Reputation: 0
sfaure03 is a n00b
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
as we,re doing 3.5 and its kitchen based, I say its a clean one.

custim roms are, or should be all done in oems the kitchens modularity gives us ease to take the best and most tested..

and, anyway, I have a decent environment to reverse out and diff roms anyway.. indeed that's how I attacked the issues I have up to now. and most o my personal roms tweaks are from tweaks I stole from the custom makers as well.

to me this s/b an easy one. imcokeman and I bboth worked hard to keepthe kitchen bare no tweaks.

the kitchen also enables us to keep work seperated and structured.
  #3 (permalink)  
Old 02-24-2007, 10:50 AM
schettj's Avatar
morsus mihi
Offline
Pocket PC: iPhone 4
Carrier: AT&T
Location: Not from around these parts
 
Join Date: Oct 2006
Posts: 3,017
Reputation: 3616
schettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIP
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
I think the helmi_c/ImCokeMan 1.1 (now 1.2?) is the cleanest base rom we've got - it's what every other 3.5 custom rom is based on, so any bugs in it are in them (unless fixed by those developers already, and if so those fixes should be easy to roll into the base)

But as you say, it's up to them. I'll identify the issues in any rom they tell me to look at
  #4 (permalink)  
Old 02-24-2007, 12:38 PM
luv2chill's Avatar
Retired Staff
Offline
Pocket PC: Apache (PPC6700); Titan (Mogul)
Carrier: Sprint
Location: Lawrence, KS
 
Join Date: Nov 2006
Posts: 1,524
Reputation: 143
luv2chill is keeping up the good workluv2chill is keeping up the good work
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Send a message via ICQ to luv2chill Send a message via AIM to luv2chill Send a message via MSN to luv2chill Send a message via Yahoo to luv2chill Send a message via Skype™ to luv2chill
I say step even further back than 1.1. Let us start with the helmi 3.3 kitchen and completely re-create AKU 3.5, fully documenting every change made along the way. This way we have a complete "cookbook" (sorry) for how that kitchen was created, which folders are affected by which hacks/fixes, and a more standardized process for implementing said hacks/fixes.

For one (and I've said this before), I strongly suggest that nothing goes into/out of the OS and LOC folders unless it won't work as an OEM package. By doing this we make the changes much easier to manage for everyone and easier to keep track of (because they're in one place). If one of our fixes turns out to cause problems down the line it is easy to just remove that folder from OEM as opposed to having to hunt down individual files/modules inside OS or LOC and trying to replace them from an old kitchen. It just makes for a cleaner kitchen (sorry again).

There may very well be some fixes that must go in OS/LOC because they won't work properly in OEM or would take up much too much space otherwise. In those cases so long as we all agree that they're necessary for the base kitchen and are thoroughly tested they can go into OS/LOC.

Anyway those are just some thoughts. Call me an idealist (it's true), but even if it means a bit more work, I think we should truly start from the beginning and properly implement and document each and every change we make to get it to the proper 3.5 base kitchen. Then that info can go into the wiki for all to see.
  #5 (permalink)  
Old 02-24-2007, 01:13 PM
Maxx134's Avatar
VIP Member
Offline
Pocket PC: Epic Touch 4G
Carrier: Spint
Location: NYC
 
Join Date: Jan 2007
Posts: 1,272
Reputation: 4320
Maxx134 should be added to the payroll for their contributionsMaxx134 should be added to the payroll for their contributionsMaxx134 should be added to the payroll for their contributionsMaxx134 should be added to the payroll for their contributionsMaxx134 should be added to the payroll for their contributionsMaxx134 should be added to the payroll for their contributionsMaxx134 should be added to the payroll for their contributionsMaxx134 should be added to the payroll for their contributionsMaxx134 should be added to the payroll for their contributionsMaxx134 should be added to the payroll for their contributionsMaxx134 should be added to the payroll for their contributions
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
When will be the deadline on this decision?
How much time do we have to voice our opinions?


Edit: had some spec info at home, but at work now that's why.
  #6 (permalink)  
Old 02-24-2007, 01:24 PM
finster869's Avatar
Regular 'Geeker
Offline
Pocket PC: Touch Pro
Carrier: Sprint
Location: Pennsylvania
 
Join Date: Nov 2006
Posts: 282
Reputation: 105
finster869 is keeping up the good workfinster869 is keeping up the good work
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
I think that 1.2 kitchen rom that IMCOKEMAN and Sfaure03 just completed is pretty much as vanilla and close to stock as it gets (other than the .net2 folder being in the OEM). IMCOKEMAN can confirm, but if I recall, when he went from 3.3 to 3.5 he didn't do that much modification. I'd vote for using this one as the base, unless for some reason IMCOKEMAN or Sfauer03 feel a need to start totally over again.
  #7 (permalink)  
Old 02-24-2007, 01:28 PM
ImCoKeMaN's Avatar
Retired Staff
Offline
Pocket PC: Touch PRO 2! Touch Pro, Touch, Mogul, 6700
Carrier: Sprint
 
Join Date: Dec 2006
Posts: 918
Reputation: 3178
ImCoKeMaN is still contributing even after becoming a VIPImCoKeMaN is still contributing even after becoming a VIPImCoKeMaN is still contributing even after becoming a VIPImCoKeMaN is still contributing even after becoming a VIPImCoKeMaN is still contributing even after becoming a VIPImCoKeMaN is still contributing even after becoming a VIPImCoKeMaN is still contributing even after becoming a VIPImCoKeMaN is still contributing even after becoming a VIPImCoKeMaN is still contributing even after becoming a VIPImCoKeMaN is still contributing even after becoming a VIPImCoKeMaN is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Well, idealist or not luv2chill you do have a good point. I did try to document most of the changes i did, but it wouldn't hurt to start from scratch again. I started with the helmi BA aku 3.5 R0 (guaranteed no module conflicts) in the beginning and i think i could help guide someone to most of the steps required to get us back to where we are now using the helmi 3.3 apache OEMs and the fixes that have been added by everyone. I hope someone (an advanced developer/analyst etc. preferably) that didn't do this before could work through it and write the instructions from "tips" or a rough guideline and then revise the notes as needed. This really shouldn't set us back very far if i did my notes properly although i can't walk through it to the point of flashing the rom myself at the moment. I have to at least wait til monday for the UTStarcom warranty support office to open before i even know if they'll look at it.

Finster,
I think the v1.2 should be the direction for the base essentially (hopefully fix a few more lurking issues though), but i agree with luv2chill that we should have a cookbook with step by steps to get the recipe right
  #8 (permalink)  
Old 02-24-2007, 01:53 PM
Sogarth's Avatar
PPCGeeks Regular
Offline
 
Join Date: Jan 2007
Posts: 129
Reputation: 0
Sogarth is a n00b
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
I mostly agree with luv2chill, but with a slightly different perspective on some of the ideas here.

Quote:
Originally Posted by luv2chill
I say step even further back than 1.1. Let us start with the helmi 3.3 kitchen and completely re-create AKU 3.5, fully documenting every change made along the way. This way we have a complete "cookbook" (sorry) for how that kitchen was created, which folders are affected by which hacks/fixes, and a more standardized process for implementing said hacks/fixes.
Nothing to comment on here.... Starting with the only package that's completely verifiable as not having had undue modifications from the beginning would probably give us the cleanest start. Besides of which, all of the fixes have happened recently enough that we probably remember what changes we would need to duplicate.

Quote:
Originally Posted by luv2chill
For one (and I've said this before), I strongly suggest that nothing goes into/out of the OS and LOC folders unless it won't work as an OEM package. By doing this we make the changes much easier to manage for everyone and easier to keep track of (because they're in one place). If one of our fixes turns out to cause problems down the line it is easy to just remove that folder from OEM as opposed to having to hunt down individual files/modules inside OS or LOC and trying to replace them from an old kitchen. It just makes for a cleaner kitchen (sorry again).

There may very well be some fixes that must go in OS/LOC because they won't work properly in OEM or would take up much too much space otherwise. In those cases so long as we all agree that they're necessary for the base kitchen and are thoroughly tested they can go into OS/LOC.
This, I don't know if I would agree with in quite this way. I feel that any modifications we make to files in the OS/LOC directories should stay in the OS/LOC directories, since that's where they came from in the first place. Case in point: I would think that any of the changes we're making to the GAC_* .NET CF .dlls should stay in exactly the same directory. Outside of that, I don't think we need to worry about this problem until we hit the customization phase, and the majority of that will happen in OEM anyways. I'll leave aside those customizations that will need to alter OS/LOC for the moment....

Quote:
Originally Posted by luv2chill
Anyway those are just some thoughts. Call me an idealist (it's true), but even if it means a bit more work, I think we should truly start from the beginning and properly implement and document each and every change we make to get it to the proper 3.5 base kitchen. Then that info can go into the wiki for all to see.
Wiki? Bah, wiki.

Honestly? All changes should probably go through a source control system (yes, I'm bringing that up now). That would ensure that we would have a good history, file by file or change by change, and everything would end up being documented in a sense. It would give us the ability to know exactly what happened, who did it, and why.
  #9 (permalink)  
Old 02-24-2007, 02:44 PM
schettj's Avatar
morsus mihi
Offline
Pocket PC: iPhone 4
Carrier: AT&T
Location: Not from around these parts
 
Join Date: Oct 2006
Posts: 3,017
Reputation: 3616
schettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIP
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Re Source Control

How about http://unfuddle.com/home - free, on the web, secure. Sounds like a winner.
  #10 (permalink)  
Old 02-24-2007, 03:10 PM
Glossman's Avatar
Regular 'Geeker
Offline
Pocket PC: HTC SuperSonic
Carrier: Sprint
Threadstarter
Location: 34 50' 47" North, 119 8' 55" West
 
Join Date: Feb 2007
Posts: 484
Reputation: 800
Glossman knows their stuffGlossman knows their stuffGlossman knows their stuffGlossman knows their stuffGlossman knows their stuffGlossman knows their stuffGlossman knows their stuff
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quote:
Originally Posted by Maxx134
When will be the deadline on this decision?
How much time do we have to voice our opinions?


Edit: had some spec info at home, but at work now that's why.
We'll leave this open as long as there is debate. If you have something add that you won't be able to get to until tonight, it will still be open for you.
Closed Thread

  PPCGeeks > Windows Mobile > Windows Mobile Development > ROM/Kitchen Development

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


All times are GMT -4. The time now is 12:49 PM.


Powered by vBulletin® ©2000 - 2019, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.6.0
©2012 - PPCGeeks.com