[DISCONTINUED] OMJ's HTC Sense Kitchen v2.1 | WM 6.x / WM 6.5.x | 21895 / 235xx

[KBZL]

Originally Posted by omnicronx

How are you viewing it? From the about page in manila? Because I am using the device info from the latest LEO dump and it doesnt seem distorted or anything and I'm pretty sure I get all the values.. (or does OMJ not use this and just lets the stock device info run?)

edit: ahhh nvm I see now..

Yeah, only my dialer looks crapped out. The device info just isnt coming up fully.

Still searching for a dialer replacement. I found one but keeps saying it couldnt install successfully.

[Trident]

Originally Posted by kbussen

Yeah, only my dialer looks crapped out. The device info just isnt coming up fully.

Still searching for a dialer replacement. I found one but keeps saying it couldnt install successfully.

I think you're going to have a problem until you can flash.
Replacing a dialer is not something that be done with a cab.
We used to be able to skin them on the fly, but I haven't even been able to do that since WM6.0.

[KBZL]

Originally Posted by Trident

I think you're going to have a problem until you can flash.
Replacing a dialer is not something that be done with a cab.
We used to be able to skin them on the fly, but I haven't even been able to do that since WM6.0.

Ok, thanks. I found the reg to set the dialer back to default so atleast i can dial out.

[KBZL]

Just out of curiosity, I didnt have the dialer issue i described until this build. There can only be two things that could have caused this A) I cooked in the new Manila Unlocker over at XDA Rc2. B) It has something to do with 6.1. Those are the only 2 things i changed in my recent build. Anyone think it could be more one or the other that could have caused this? Thanks.

[MrObvious]

You could just not cook in a phone canvas then skin the dialer that way.

[KBZL]

Originally Posted by MrObvious

You could just not cook in a phone canvas then skin the dialer that way.

Skin to look what way? Like the Rhodium Dialer? Is there such a thing?

[MrObvious]

Originally Posted by kbussen

Skin to look what way? Like the Rhodium Dialer? Is there such a thing?

IDK someone said skinning the WM dialer and I just was pointing out how to bring it back.

[OMJ]

Originally Posted by scout7

Hey OMJ, saw where you were messing with a 28014. can you put that on the FTP!?

theres really nothing better about it....still seeing intermittent freezing in email. Gonna try 28011.

Originally Posted by mucky

Yes, I am using the Sprint pkg. I have even named my file Mighty.jpg and replaced the other one,and it won't load. Here is what I have

[HKEY_CURRENT_USER\Software\HTC\Manila]
"HomeBackgroundPath"=\\Windows\\Mighty.jpg

found this @ XDA, give it a try...

http://forum.xda-developers.com/show...&postcount=790

Originally Posted by CRACING

How to cook custom background wallpaper for Manila 3D 2.5 ( Home Screen )

1. First rename your image file ( PNG or JPG, Not sure about other formats ) to HomeBackground.img*.
2. Create a CAB file ( Using any of your fav SW, i.e WinCE CAB Manager ).
3. Place this .img file into the CAB. Location should be \Windows.
4. Open Notepad and copy the reg entries written below :

REGEDIT4
[HKEY_CURRENT_USER\Software\HTC\Manila]
"CachedBackgroundPath"="\\My Documents\\My Pictures\\Pic01.png"
"HomeBackgroundPath"="\\My Documents\\My Pictures\\Pic01.png"
"Home.WallpaperMode"=dword:00000002

[HKEY_LOCAL_MACHINE\Software\HTC\HTCPhotoPicker\Manila\ReturnValue]
"Status"=dword:00000001
"FilePath"="\\My Documents\\My Pictures\\Pic01.png

[HKEY_LOCAL_MACHINE\Software\HTC\HTCPhotoPicker\Manila\Setting]
"Enable_DRM"=dword:00000000

5. Paste into the Notepad file.
6. Edit the image paths to your image located. I.e CachedBackgroundPath, HomeBackgroundPath and FilePath. The HomeBackground.img and this image should be same.
7. Save the Notepad file to 1.reg.
8. Import the 1.reg file into the CAB file and save it. ( If your CAB manager doesn't support importing reg file(s), try adding the reg entries manually )
9. At last use this cab file to your auto run or etc inwhich the cab should be installed while Manila 3D is running.

This big process is coz, these things should be changed/written while Manila 3D is running. If you do this into rgu and run Manila 3D later on, it doesn't read/change the background wallpaper. However, I have tried few hours playing with this and found the working way. If any of you can find still more simple way, that would be more then a great.

Note #1: The file extension should be correct. i.e reg.txt or img.png is wrong. Make sure about it!
Note #2: The Manila 3D should be loaded fully before the CAB ( via autorun ) installs. If it a lil difference, Manila 3D won't load the image. It is hard to setup but this is the only way!

Sorry for writing too lengthy and not so good language but I hope you can understand better

Thanks a lot to Amarullz!
Best Regards

[mwalt2]

Originally Posted by kbussen

Just out of curiosity, I didnt have the dialer issue i described until this build. There can only be two things that could have caused this A) I cooked in the new Manila Unlocker over at XDA Rc2. B) It has something to do with 6.1. Those are the only 2 things i changed in my recent build. Anyone think it could be more one or the other that could have caused this? Thanks.

It's probably from wm 6.1. Most of the new stuff from HTC is using 6.5 now. You can cab install dialers as long as you kill some processes first (cprog.exe or something else...can't remember, but I'm sure you can find it in the xda vga tachi dialer thread).

[KBZL]

Originally Posted by mwalt2

It's probably from wm 6.1. Most of the new stuff from HTC is using 6.5 now. You can cab install dialers as long as you kill some processes first (cprog.exe or something else...can't remember, but I'm sure you can find it in the xda vga tachi dialer thread).

Hey thanks for the response. I figured it out. Somewhere along the way, i guess while i was making haste, i selected two phone canvases. They were overlapping. Recooked this morning and everything is great.