I used wavedev.dll and rilphone.dll from birkoff's (chuckydroidrom) kitchen, as modules. I'm an EVK guy and I use rstoyguy's kitchen to cook my own rom for my hd2. The only info I could find was about changing those two.. It seems birkoff used 2.10.1 as a base.. Including the 2.13 gps drivers as an ext. Is there anything more specific? I'll try to figure out.. then hopefully I can add a nice [ref] tag to this post. heh
Just tried the ChuckyDroidROM OEMDrivers folder.. Only the modules.. no luck. Its annoying because one 'robocall' is all it takes to break android sound... not to mention all the rom flashing i've done. Any help guys?
1. Hspl
2. Radio 2.12 or 2.10
3. Miri elegancia or chuckydroid
4. Your android version
Did u try any of those combos?
Make sure u have one of those radios. There pretty important.
Yes, I've got that part down. I've tried every radio, and I've confirmed that chuckydroidrom does solve the voice issues. I'm asking what birkoff changed in the kitchen to get chuckydroidrom to work without issues with android. I could port all my stuff over to osKitchen, including sys (I use com2 builds) - but then i'd never really know for sure.
to recap, so far i've got oemdrivers (modules only), rilphone and wavedev (which are part of oemdrivers) from chuckydroidrom.. but that hasn't cured anything. It seems like OEMDriversHigh is identical to the set I have. Other than that, theres the sys build (I have 21915) and the many different exts. I build com2 21915 with 2016 sense and 1.8.5.1 CHT.. The rom is like 190MB tops.
So is something missing.. or is something that I'm including breaking functionality? I'd like to find out here rather than the long trial and error process ahead of me.
Ok, so I was able to actually break sound in winmo by using the OEMDrivers from birkoffs kitchen. I got the robo voice and all that, the whole nine, so to speak. I wonder if this is relevant. There are probably two things that need to match up in winmo that didn't- most of the time, one of these things don't match up in android, causing robo voice. What carries over to android that is not in OEMDrivers. Rilphone and wavedev alone broke nothing in winmo, but retained robo voice in android.
You need to use CAD.dll, dsm.dll, oncrpc.dll, remote_apis_clnt.dll, wavedev.dll, audio_cal.acdb from a 2.10 OEM to get rid of robo voice.
pkoper said:
You need to use CAD.dll, dsm.dll, oncrpc.dll, remote_apis_clnt.dll, wavedev.dll, audio_cal.acdb from a 2.10 OEM to get rid of robo voice.
Click to expand...
Click to collapse
You are the ****ing man.
I changed rom and I got rid of robot voice
My HD2 Kitchen is available here if you want also. it has a saved project to cook a rom android compatible
Thanks for the link to the kitchen, thats a big one! Well, the aforementioned files did not fix incall robo voice but managed to lock up phone when volume was adjusted in winmo.
What sys does the kitchen use for the droid rom? I'm not trying to build a barebones rom - I'm just trying to adjust my build for in-call sound to work in android.
Ok.. so 21911 is the sys..
I included the 2.10 OEMDrivers and OEMDriversHigh - that still did not work.
On the boot screen, it still says 2.13 for "D" - where R would be radio version. With those drivers, winmo also seemed a great bit choppier. Its back to the drawing board for me..
joshkoss said:
My HD2 Kitchen is available here if you want also. it has a saved project to cook a rom android compatible
Click to expand...
Click to collapse
Was able to get your kitchen set up with a couple of my exts, manila folder (a couple tabs removed), cht, and 21915. I flashed the rom, the "D" read 2.10Droid as expected.. and somehow someway I still get the robo voice. I tried 2.08 radio, 2.12, and 2.10. Same thing.
Now I'm confused.. Could it be something like an updated version of audio manager, audio booster, anything like that? Probably not, as there are roms that work with android that have cht, latest version of manila and so on.
I'll try a few more things..
edit: audio seemes to be really screwed. Any sound played in winmo, locks up my phone. This is crazy. What am i screwing up?
Sounds like your kitchen is all over the show.
Make sure you work with clean sources. I have several untouched stock rom dumps to have quick access to original files.
The files posted earlier definately get rid of robo voice. I also took OEMXipkernel from 2.10, but not sure if this is necessary.
Have you flashed the stock 2.10 ?
pkoper said:
Sounds like your kitchen is all over the show.
Make sure you work with clean sources. I have several untouched stock rom dumps to have quick access to original files.
The files posted earlier definately get rid of robo voice. I also took OEMXipkernel from 2.10, but not sure if this is necessary.
Have you flashed the stock 2.10 ?
Click to expand...
Click to collapse
This was from a clean source.. or rather.. one that is proven to work. The only major changes I did was updating the manila/htc related packages. Would it matter if I had the aforementioned files as modules instead? Good tip on the 2.10 oemxipkernel. I wonder if that is in kitchens like birkoffs and josh's.
Bump. According to the troubleshooting thread, there is still very little info about this.
Any tips or guesses? I'll start cooking whatever tonight.
I think this is the path to the answer. Each android build performs flawlessly with stock ROMs. No freezing or non working hardware. Everything works (for me on TMOUS anyway). I am not looking for a solution to robot voice, I am stating that from my point of view when booting any android build from a stock ROM on my TMOUS HD2, every thing works fine except for the robot voice. Bluetooth,good, Wifi,good, no freezes or SOD. Smooth as a babies butt! I personaly believe that crossing this barrier will mark the start of something great for our developer friends.
Sent from my HTC Desire using XDA App
Well, as I might have stated before, I was able to reproduce robot voice in winmo by frankensteining 2.13 and 2.10 together. In winmo, anytime a sound would be played.. it'd lock up. Its not really a developer issue. Its more like a mismatch of versions. The android sound driver could do things the same way as 2.10 sound driver.. I'm being sorta vague.. but its a very strange problem.. Especially when you introduce radio version into the mix.
How could something happen like that? What has to go wrong? Is it the way the hardware is initialized? or is it the way its accessed?
Did you try a clean 2.10.1 base without mixing any drivers...and I mean CLEAN
OEMXIP also from it including nk etc....
Related
1. This is my first custom ROM ever.
2. Adapted for the 91x from same for 61x by keyx (http://forum.xda-developers.com/showthread.php?t=496283)
3. Major props to fellow Canadian keyx for major instruction and ongoing guidance. Indirect props to all his sources at pdaclan.com and xda-devs.
Done:
1. Dumped IMGFS from HP 910c Factory ROM update (using keyx kitchen).
2. Dumped XIP directly from device.
3. Ported keyx 21198 XIP to 91x using XIPKitchen (http://forum.xda-developers.com/showthread.php?t=443383)
4. Used OEM from 910c factory ROM (with Google Search, Google Maps and VoiceCommander removed)
5. Used SYS from keyx 21198 (except phone.dll and ril.dll from HP 910c factory and 61x-specific modules taken out)
6. Manual XIP ported by keyx
7. Functional ROM kitchen tools in place - tested by successfully building customized WM6.1 ROM
Current status:
- device makes it to OS boot screen (not the first "HP" boot screen but the next one), beeps once and just hangs... never goes any further
- WiFi and phone lights operational, suggesting successful XIP porting?
- can't isolate source problem between OEM, SYS or XIP
This will be based off of keyx's 03-27-09 beta 2.2 build. Once a reliable method is in place, we 910/912/914 owners should be able to benefit from his updates to the 610/612/614.
Please be patient; will post here as soon as its done.
I have cooked many rom the htx advantage ... but I could never switch from one machine to another ...
If you can be your tester!
THANKSSSSSS!!!!!!
This is a great news!! I've been waiting on a cust ROM for iPAQ91X : desperately waiting for this!!
Thanks very much!!!!! ))
I was waiting for this one since ages!
I'll be glad to be one of your testers if you need me to :-D
Gunsfan
sorry
Have been building and flashing many test ROMs for days now... none are making it past the first screen.
We may be better off porting from an entirely new source; I suspect whatever causes the 61x keyx first-boot problem (where users wait for second beep and then must reset frozen device) has just turned into a full-blown show stopper.
in the meanwhile may be you can port 6.1 21042 (if the original rom has a older verson) and may be fitting manila 2d in it.
keyx said:
in the meanwhile may be you can port 6.1 21042 (if the original rom has a older verson) and may be fitting manila 2d in it.
Click to expand...
Click to collapse
Yeah I'll give that a shot.
1. Any idea what is causing the first boot issue in your 61x ROM?
2. How exactly did you get your flash.dio file below 80 MB? Mine is 80 MB, and the 20142 for ipaq612 custom ROM I just downloaded is also 80 MB.
1. I have no idea...i will try to do a port from 6.1 to 6.5 when i done exam to see what process involvoed for cross version port
2. I am using pdalcan's rom as template.rom and it is smaller,i think it has to relate to some hex edit to change the mbr
keyx said:
in the meanwhile may be you can port 6.1 21042 (if the original rom has a older verson) and may be fitting manila 2d in it.
Click to expand...
Click to collapse
Well, I just successfully ported a WM6.1 21042 ROM for the ipaq 910c. XIPKitchen worked fine; all that is missing is WiFi (and I'll probably just have to stick the appropriate wrlsmgr.exe back in for that to work). IE6 is kind of a nice improvement, as is the removal of VoiceCommander, GSearch and GMaps.
Will tweak a bit and then post.
benjaminries said:
Well, I just successfully ported a WM6.1 21042 ROM for the ipaq 910c. XIPKitchen worked fine; all that is missing is WiFi (and I'll probably just have to stick the appropriate wrlsmgr.exe back in for that to work). IE6 is kind of a nice improvement, as is the removal of VoiceCommander, GSearch and GMaps.
Will tweak a bit and then post.
Click to expand...
Click to collapse
Great!! If you need testers, count me in!
benjaminries
you need beta testers for 9xx ipaq? for 6.5 firmware???
roman_n1 said:
benjaminries
you need beta testers for 9xx ipaq? for 6.5 firmware???
Click to expand...
Click to collapse
We still need to wait for 6.5, he's working on it, but having an issue loading the ported ROM, gets stuck in first screen...Hopefully he releases the 6.1 cust ROM soon!
tcortinag said:
We still need to wait for 6.5, he's working on it, but having an issue loading the ported ROM, gets stuck in first screen...Hopefully he releases the 6.1 cust ROM soon!
Click to expand...
Click to collapse
Don't need beta testers, thanks - anything that seems to work on my end will be released.
As it stands, the WM6.5 ROM is stalled; I'll keep fidling with it, but we may have to just wait for a new build to be released before it is worth much more time investment.
The WM6.1 build 21042 is a nice update because it contains IE6 Mobile. I've got a test ROM cooked but it at least major two bugs, detailed in next post.
Of course it is rather easy to customize the factory build (number 19xxx) without any XIP porting - I can post a release that has Google Maps, Google Search and VoiceCommander removed, and a few odds and ends added. But other than that there are very few benefits.
If people want to help out, there are two things they can do:
- hunt down (on xda-devs and PPCgeeks discussion threads) new sources of WM6.5 ROMS for me to use for porting
- try to find a device ROM from which we can extract a compatible, yet better, rilgsm.dll ...the Ipaq 61x and 91x has a well-known problem where the GSM radio doesn't expose the Cell Tower ID to the OS (limiting the "My Location" feature in Google Maps to use the standard GPS only without cell tower triangulation and preventing the useful operation of other apps like Navizon). I am convinced that this problem stems to the rilgsm.dll file in which HP has not implemented this feature (but HTC certainly has).
pdadb.net says that the 91x and the 61x are both manufactured by Inventec and use a Qualcomm MSM6280 (2x QDSP4000) phone controller. If somebody can find a device ROM or just the rilgsm.dll from another phone that uses the same cell radio hardware, we should try cooking that file into our ROMs and see if it enables the desired functionality.
Getting the CNAP feature (a.k.a. Rogers Name Display) would be a bonus as well, but it looks like the Rogers HTC phones do not use the same radio (i.e. Touch Diamond and TyTN use "Qualcomm MSM7201A (QDSP4000, QDSP5000)").
benjaminries said:
The WM6.1 build 21042 is a nice update because it contains IE6 Mobile. I've got a test ROM cooked but it at least major two bugs, detailed in next post.
Click to expand...
Click to collapse
Here are the bugs in my 21042 ROM so far:
BUG 1: WiFi disappears
This is weird - the blue WiFi light begins blinking during first boot and continues through the Welcome tutorial. Then once I reach the first screen, it goes out and the device behaves as though it doesn't have built-in WiFi. The Wireless Manager only shows "Bluetooth" and "Phone" options. Strange, because the SDIO wifi driver is definitely in the OS (it comes up as a network device under "Connections") but there's no interface to enable it.
BUG 2: Storage Card isn't recognized
Simply, whenever I put in a microSD card, the device does nothing. File Explorer shows no Storage Card. Memory CPL shows no Storage Card. Just good old useless iPaq File Store and Bluetooth Neighbourhood
I suspect either I've ported the XIP wrong or I've got some lack of reg entries coming from the new base SYS. But these are show-stoppers for me so I'm inclined not to post until I can at least fix one of them. Will learn to manually port the XIP and see if that helps.
benjaminries said:
Of course it is rather easy to customize the factory build (number 19xxx) without any XIP porting - I can post a release that has Google Maps, Google Search and VoiceCommander removed, and a few odds and ends added. But other than that there are very few benefits.
Click to expand...
Click to collapse
Have you tried using this rom with the mods you mentioned but trying to add manila 2d?? That would be a really nice add-on.
Success!
Got the WiFi and Storage Card stuff working in build 21042 by manually porting the XIP (something I've wimped out on until now). Here's the release.
Moving on to another stab at porting keyx's WM6.5!
More success!
I just got a working WM6.5 21198 build for the 91x from keyx - just as I was figuring out the details of my own port of the same (keeping Windows Live modules out of SYS keeps the total modules low enough for G'Reloc to run without integer overflow; on the other hand that might not have been my problem).
I'm merging a dump of keyx's working ROM with my own stuff (some OEM customizations and a few extra SYS packages) to see how that works. But we've at least got something bootable; expect a release today or tomorrow.
Great!
i just tried this. it works great!! thank you. but can you make the X close button even bigger. the problem with the 910c is that the screen is not flused against the corner so it's difficult to hit that buttom sometimes. just nit picking
Thanks for this ROM
benjaminries,
Many thanks for the WM6.5 ROM you worked on. My 910c has been sitting on my desk for several months due to the lack of interest or any ROM updates from HP. (Great little phone with problems HP still has not fixed (datacard issues and POOR battery life). Your update has given me new reasons to begin using the device again. No crashes and no big problems discovered. Again, good work. Only noticed a couple of cosmetic things which are very minior and a lot of "task manager" icons in different folders. The one thing is did do was map "task manager" to the "voice commander" button on the side of the phone. Since this beast is known to suck up juice it's just a way to stay on top of things. Right now just using it on GSM network setting and getting decent battery life. Will start to see what happens when I set it to high-speed network. But again, no problems what-so-ever with your ROM. (Using 910c as limited use phone and heavy Exchange 2007)
SuperJustKitchen v0.7 Released.
Go to my site: http://justkitchen.info to get the updates and the info. It takes to long to update every device's forum that is supported, and I plan to support all devices.
For more information on the kitchen, please read: http://forum.xda-developers.com/showthread.php?p=4288668
Word of warning:
None of the new EXT's have been tested and fixed for the Herald, Opal, Hermes AND Artemis. Please test test and test and then let me know which packages don't work and what YOU've done to fix them. (I don't have time to fix ALL of them by myself.)
(I'm no longer updating each thread separately for each device but just updating my site and posting the release info here.)
ivanmmj said:
Now with Opal support!!
Wait until you see the announcement on my site to know that it's been updated/uploaded.
Word of warning:
SJK v.5 has had some major changes. None of the new EXT's have been tested and fixed for the Herald and Opal. Please test test and test and then let me know which packages don't work and what YOU've done to fix them. (I don't have time to fix ALL of them by myself.)
Take not that there are many versions of certain packages. Let me know if the older ones are close enough to the new ones so that I can delete the old ones.
Go to my site: http://justkitchen.info to get the updates and the info. It takes to long to update every device's forum that is supported, and I plan to support all devices.
At the moment, consider SJK v0.5 to be a test... Don't expect to have THAT many builds when it goes into v0.5.5
Right now it has the following builds available to you:
21054 (wm6.1)
21864 (COM2 - old style gui - wm6.5)
23064 (COM4 - newer gui - wm6.5)
5.5 will only have 21054, 21864, and 23064 unless something new gets released.
Click to expand...
Click to collapse
Thanks for providing us a new kitchen for opal. Can u give me a tutorial on using this kitchen for opal. Full explaination plz
It works exactly the same as your other Ervius based kitchen. You can follow that tutorial as well.
http://forum.xda-developers.com/showpost.php?p=4446173&postcount=3
The real difference is that I do the porting of new builds and the addition of new EXT packages for you.
(Granted, I've added more options under the Extra Buttons section, but you can go in there and figure out what most things are from their names and descriptions.)
Thanks BUT....
Thanks for your work man BUT: When i make my rom everything works Except the HOME settings and COMM manager,it is the same thing with BesFen kitchen,sometimes it works and then sometimes it does not.
I have tried and tried but nothing seems to help,i give up. I hope you guys can figure it out. Thanks.
What Home settings?
As far as the COMM Manager, don't choose the Comm manager in the EXT list. It's meant for older devices (like the Herald). Don't choose a Comm Manager at all. The OEM still has a comm manager built in. It will automatically insert a working comm manager.
Sorry i meant when you go to start/settings/Today does not work and i did not choose the comm manager, the one that comes with the oem does not work. Like i said sometimes they work and then it does not.
theglen35 said:
Sorry i meant when you go to start/settings/Today does not work and i did not choose the comm manager, the one that comes with the oem does not work. Like i said sometimes they work and then it does not.
Click to expand...
Click to collapse
Weird... The Today works fine on the Herald and it's part of the SYS, not the OEM. Are adding or not adding the MyCPL?
So the Comm Manager, even the one that's made FOR the phone has problems?
No i left out MyCpl. What is that BTW. The same thing happens in BesFen kitchen but it works when you put the PP on 12,anything higher it will not work.But i tried it on 12 & 16 PP in your kitchen but it does not work at all.Also when using file explorer and when selecting a theme when Today is working i have to long press or hold down the stylus to select something.
theglen35 said:
No i left out MyCpl. What is that BTW. The same thing happens in BesFen kitchen but it works when you put the PP on 12,anything higher it will not work.But i tried it on 12 & 16 PP in your kitchen but it does not work at all.Also when using file explorer and when selecting a theme when Today is working i have to long press or hold down the stylus to select something.
Click to expand...
Click to collapse
So it happens with BesFen's kitchen as well? The Opal is so strange and different than the other devices when it comes to cooking, I wonder what other changes I must make to the kitchen to get it work properly. At the moment, without an Opal, I can only make a kitchen as good as BesFen can when it comes to proper NB creation. Does anyone have a current WORKING kitchen for the Opal that doesn't have these problems? If so, point me to it and I will study the differences.
As a side note: Doesn't the Opal use myCPL by default? If it does, then you MUST choose it.
If you know PhamQuang you can ask him what kitchen he uses,his roms are usually buggy but i think the last one he made was good and everything works smooth.
You can find more detailed info on the kitchen in the main thread.
http://forum.xda-developers.com/showthread.php?t=545572&highlight=superjustkitchen
theglen35, I'll go ahead and try to contact PhamQuang. Thanks.
ivanmmj said:
As a side note: Doesn't the Opal use myCPL by default? If it does, then you MUST choose it.
Click to expand...
Click to collapse
Official Opal's ROM have MyCPL, it should be include in ROM.
The reason I made opal's kitchen because no one share working kitchen here, some one asked me to make kitchen for Opal.
PhamQuang is from PDAVIET, and as we all know they always don't want to share the kitchen and source. You can try to contact him, maybe they change their mind now.
BesFen said:
Official Opal's ROM have MyCPL, it should be include in ROM.
The reason I made opal's kitchen because no one share working kitchen here, some one asked me to make kitchen for Opal.
PhamQuang is from PDAVIET, and as we all know they always don't want to share the kitchen and source. You can try to contact him, maybe they change their mind now.
Click to expand...
Click to collapse
Hey BesFen THANKS very much for making a kitchen for the Opal,I have made many roms with it and except for a few problems it works good.But i think you should try and get all the bugs and problems worked out so we don't have to rely or wait for PhamQuang or PDAVIET to get any roms.
Because of the problems i am using Opals original WM 6.1 until you guys can figure it out.
theglen35 said:
Hey BesFen THANKS very much for making a kitchen for the Opal,I have made many roms with it and except for a few problems it works good.But i think you should try and get all the bugs and problems worked out so we don't have to rely or wait for PhamQuang or PDAVIET to get any roms.
Because of the problems i am using Opals original WM 6.1 until you guys can figure it out.
Click to expand...
Click to collapse
If your ROM can boot, it mean the kitchen work great.
The problem that you figure is not causes by the kitchen, it's pure something in the ext or OEM or SYS, try to read more reference from others device thread, I can't fix it since I don't have opal for test it, I am sorry about that.
ivanmmj said:
Now with Opal support!!
Wait until you see the announcement on my site to know that it's been updated/uploaded.
Word of warning:
SJK v.5 has had some major changes. None of the new EXT's have been tested and fixed for the Herald and Opal. Please test test and test and then let me know which packages don't work and what YOU've done to fix them. (I don't have time to fix ALL of them by myself.)
Take not that there are many versions of certain packages. Let me know if the older ones are close enough to the new ones so that I can delete the old ones.
Go to my site: http://justkitchen.info to get the updates and the info. It takes to long to update every device's forum that is supported, and I plan to support all devices.
At the moment, consider SJK v0.5 to be a test... Don't expect to have THAT many builds when it goes into v0.5.5
Right now it has the following builds available to you:
21054 (wm6.1)
21864 (COM2 - old style gui - wm6.5)
23064 (COM4 - newer gui - wm6.5)
5.5 will only have 21054, 21864, and 23064 unless something new gets released.
Click to expand...
Click to collapse
thanks ivan u've done great... thanks for having opal too in ur kitchen.. hopfully everything work great like the herald... ur the best... i thought i'll never see u since my phone is not the wing no more its touch viva now.. cuz i like wat u done for herald lots cooks already doing different roms... it is impressive... hopfully i'll start my own too... for here... thanks alot ivan keep it up...
BesFen said:
Official Opal's ROM have MyCPL, it should be include in ROM.
The reason I made opal's kitchen because no one share working kitchen here, some one asked me to make kitchen for Opal.
PhamQuang is from PDAVIET, and as we all know they always don't want to share the kitchen and source. You can try to contact him, maybe they change their mind now.
Click to expand...
Click to collapse
Yea, if the Opal comes with the MyCPL and they don't choose it, then that's part of the problem.
I agree with you, though. Technically, the issue is not with the kitchen but with what you DO with the kitchen as a cook. Since I don't have an Opal either, I won't be able to look around and preemptively fix all the bugs by pre-packaging certain EXT's into the OEM.
I also appreciate you working on that Opal kitchen. It's what I used as an example to get the Opal compatibility on my own kitchen. I appreciate your advise about PDAVIET.
ob_izzy, now it's your turn to be a great cook. ^_^
I agree with you, though. Technically, the issue is not with the kitchen but with what you DO with the kitchen as a cook. Since I don't have an Opal either, I won't be able to look around and preemptively fix all the bugs by pre-packaging certain EXT's into the OEM.
Come on guys, what are you saying? Both of you are making a kitchen for a device that you don't have and can't test and you are saying it's not the kitchen! I beg to differ because believe me i have tried all sorts of ways to get the rom to work including reading alot, re-arranging files, adding, leaving out, different PP. Maybe it still has stuff to add or leave out that i don't know about, so that is where you guys come in. I need PLEH.
theglen35 said:
I agree with you, though. Technically, the issue is not with the kitchen but with what you DO with the kitchen as a cook. Since I don't have an Opal either, I won't be able to look around and preemptively fix all the bugs by pre-packaging certain EXT's into the OEM.
Come on guys, what are you saying? Both of you are making a kitchen for a device that you don't have and can't test and you are saying it's not the kitchen! I beg to differ because believe me i have tried all sorts of ways to get the rom to work including reading alot, re-arranging files, adding, leaving out, different PP. Maybe it still has stuff to add or leave out that i don't know about, so that is where you guys come in. I need PLEH.
Click to expand...
Click to collapse
The kitchen only puts things together. What the stuff does depends on the OEM's and EXT's included. If you took all the EXT's that came with the official Opal ROM, you may not have any bugs because the manufacturer has worked out all those little bugs. If I had an Opal to play with, I'd probably find all the bugs myself and fix them (like I did with the Herald.) Unfortunately, we need the help of a very experienced Opal cook who HAS an Opal. (Or I need an Opal, which isn't happening since I have a G1 as my main phone and wouldn't buy an Opal to replace it (nothing wrong with the Opal, but I love android. )
theglen35 said:
Come on guys, what are you saying? Both of you are making a kitchen for a device that you don't have and can't test and you are saying it's not the kitchen! I beg to differ because believe me i have tried all sorts of ways to get the rom to work including reading alot, re-arranging files, adding, leaving out, different PP. Maybe it still has stuff to add or leave out that i don't know about, so that is where you guys come in. I need PLEH.
Click to expand...
Click to collapse
You can make an experience, dump the official opal's ROM (ruusigned.nbh) with Visual kitchen from mine or ivanmmj, go to the official rom folder, there is a "dump" folder there with Ervius kitchen tools, then run that kitchen and build the rom, it will build ROM same as official that you dump. If it run well, no problem with the kitchen.
BesFen said:
You can make an experience, dump the official opal's ROM (ruusigned.nbh) with Visual kitchen from mine or ivanmmj, go to the official rom folder, there is a "dump" folder there with Ervius kitchen tools, then run that kitchen and build the rom, it will build ROM same as official that you dump. If it run well, no problem with the kitchen.
Click to expand...
Click to collapse
Great suggestion man. I tried it and it did build the 6.1 rom without problems but it builds 6.1 good but not 6.5. When it builds wm 6.5 there are problems.
I am going to give chef'in a try and as I have never done it before I would ask you to be patient with me.
I have the HTC Leo with Radio 2.10.50 and HSPL installed.
Im using oskitchen and so far I have updated a Stock rom to 6.5.5. Nothing difficult there I hear you say ! But hey, its my first working ROM.
Now I have 2 questions that I hope you can help me with.
Q1. When I flashed the ROM to my phone all worked as you would expect apart from the main screen looked like it had dropped down about 10 pixels. Top and bottom bars looked OK but the middle looked wrong (Screen coming if needed)
Q2. Can someone instruct me on how to set the default wallpaper from oskitchen ?
I have an image called HTC_BG.png and I would like to cook it into the ROM as the default wallpaper.
Ive looked on the forums for help with these questions but I am unable to find them.
Any help / links would be helpfull
Once I have this info, I will proceed to cook my ROM and eventually post the results on the forums along with a complete tutorial as I go along, for those who are looking for similar info.
I have any problems with the buttons and the prefrence folders.
I have create a clip how can you see this problem.
h**p://youtube.com/watch?v=qmDQOzCIWu8
I hope i exist a fix, or what are the right kitchen for the Leo??
BoTTeR1337 said:
I have any problems with the buttons and the prefrence folders.
I have create a clip how can you see this problem.
h**p://youtube.com/watch?v=qmDQOzCIWu8
I hope i exist a fix, or what are the right kitchen for the Leo??
Click to expand...
Click to collapse
From what I know dumping and rebuilding a Leo ROM works correctly on both oskitchen 1.30v3 and 1.31beta3 so you probably changed something that broke that stuff. Always try if a clean dumped ROM rebuilds fine before doing changes that may break it.
Okay... I think im not so Stupid to do this.
I go this way:
1. I Install (extract) OS Kitchen on a folder into my Harddrive (C:/OS)
2. Then i Load the original Rom, extract this to get the RUU_Signed_0407.nbh
3.I Start OSKitchen and klick on Import-> Import a new ROM file.
4. I Select my Model, HTC Leo (HD2) and type the pfad of the RUU_Signed_0407.nbh and go to next (Waiting a minute)
5. I klick on start bulding, and os kitchen go throte without errors..
I Flash the Rom...
And the Taps didn't work. I Have a Windows XP OS and the OS Kitchen Version is 1.31.alpha4
BoTTeR1337 said:
Okay... I think im not so Stupid to do this.
I go this way:
1. I Install (extract) OS Kitchen on a folder into my Harddrive (C:/OS)
2. Then i Load the original Rom, extract this to get the RUU_Signed_0407.nbh
3.I Start OSKitchen and klick on Import-> Import a new ROM file.
4. I Select my Model, HTC Leo (HD2) and type the pfad of the RUU_Signed_0407.nbh and go to next (Waiting a minute)
5. I klick on start bulding, and os kitchen go throte without errors..
I Flash the Rom...
And the Taps didn't work. I Have a Windows XP OS and the OS Kitchen Version is 1.31.alpha4
Click to expand...
Click to collapse
Update to 1.31beta3 because anything before the beta1 had issues with HD2
like Shaddex I am looking into creating ROM's from scratch (for HD2 Leo also!), first for personally use and maybe for general if I can get a ROM to look nice.
My question is, is there a kitchen which work's best for the HD2? Or are all basically generic and just "cook" in different ways?
Sorry to hijack your post Shaddex I hope you get an answer soon, wish I could help
And back on topic
Ok. I extracted Oskitch again, added "RUU_Leo_HKCSL_WWE_1.72.831.1_Radio_CRC_Signed_15.32.50.07U_2.07.51.22_2_Ship"
as the base ROM.
Next installed the "24619_MSXIPKernel_SYS_QVGA_WQVGA_HVGA_VGA_WVGA_0409" so I can use the latest build.
Thats all I did.
No extra EXT packages, Just cooked the ROM and below is what I get.
Anyone shed any light ?
5haddex said:
And back on topic
Ok. I extracted Oskitch again, added "RUU_Leo_HKCSL_WWE_1.72.831.1_Radio_CRC_Signed_15.32.50.07U_2.07.51.22_2_Ship"
as the base ROM.
Next installed the "24619_MSXIPKernel_SYS_QVGA_WQVGA_HVGA_VGA_WVGA_0409" so I can use the latest build.
Thats all I did.
No extra EXT packages, Just cooked the ROM and below is what I get.
Anyone shed any light ?
Click to expand...
Click to collapse
The 6.5.3 windows mobile builds have the top and bottom bar of different sizes while Manila is probably calibrated for the WM6.5 bars (indeed there's empty space at the top and overlap at the bottom). There is probably something else you have to do to fix manila after changing the windows mobile build but I'm pretty sure it's not a kitchen problem I've had several people reporting the Leo ROMs dump and build fine with the 1.31 betas.
Is anyone willing to assist me on getting a Stock HD2 rom and upgrading it to 6.5.x without the problems I am seeing ?
5haddex said:
Is anyone willing to assist me on getting a Stock HD2 rom and upgrading it to 6.5.x without the problems I am seeing ?
Click to expand...
Click to collapse
Could you post a screenshot of your problem, and if you upload your background, i will use it to replace the one in HTC Black.TSK (You need OCP CE CAB Manager)
I have posted a screenie of the problem and someone says its because manila is not the correct version for the 6.5.5 im using.
Dont suppose you have a 6.5.5 stock rom ???
So...
Can anyone let me have a oskitchen with 6.5.x + latest manila so I can add to it.
I just updated from the 2.07 to the 2.1 ATT Base, but using the same SYS as before and the same EXt packages as before, and it had some side effects.
Some of this may have been caused my the rusghed way I updated my kitchen.
Cons:
1. Although XDA-UC ran and installed both exes and some xml, it did not import my exchange settings. neither the XDA-UC pack or the XML for that has changed in months.
2. When I restored my CHT quicklinks, I had to manually restore the one for ActiveSync (Linked to the above?)
3. Had a funny moment with manila where it went very flickery. Never had that before.
Pros
I can now activate voice command with the button on my bluetooth headset like I used to. This is a big thing for me.
Also, just realised, I set up a new kitchen so forgot to apply a few tweaks and change the pagepool. D'oh.
Any hints about the above - first time I have used an ATT base - is there anything around activesync in particular that might be impacted?
Cheers
Do you have 2016 Manila working on this base? If so, would you be willing to share your kitchen or some key EXTs? What kitchen SW are you using? Thanks.
And #3, I had Manila be flickery on almost all the ROMs I have tried. Valyrie, Energy, mines. Are you using CFC compression?
using 2012, sorry.
i use oskitchen 1.3.
my recook went better but i think there may be something about ActiveSync.
so far so good..
crazyC said:
using 2012, sorry.
i use oskitchen 1.3.
my recook went better but i think there may be something about ActiveSync.
so far so good..
Click to expand...
Click to collapse
I love it. Its freaking fast.
And I use the same kitchen SW too
I try to cook a WM 6.5.x rom for my Mega. But When I try to install I've noticed that(picture). So Am I did something wrong? I used ROM_Mega_HTC_WWE_EastEurope_1-28-479-4 for this as base and this
29007_XIP_HVGA_QVGA_VGA_WWQVGA_WWVGA_0409 for 6.5.x
Is this normal? Or What?
Whatever. I'm installing rom.
Well, It's sure now there is a problem with that. It stucks at 18% and don't installs.
Well, I guess this:
ROM_Mega_HTC_WWE_EastEurope_1-28-479-4
is a keyword. You have the ROM version in the file name and it's actually lower than you currently have in device.
I think this number is stored in nk.exe (it's a part of XIP -> OEMXipKernel). I have no idea if this file should be changed when porting ROM to 6.5.x. Someone else must answer it.
Normally MSXIPKernel is included in build, so perhaps nk.exe must match it. I don't know.
I figure it out. When installing it says base builds version but when installed its becomes the name I put like Fattur's Rom v1.0
how to upgrade htc touch 3g. thanks