yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] + Que PPC:
i use this:

and can set 10 chars in signature version... select the os-new.nb from temp folder and compile it. dunno if it works for your device hehehe but maybe you have enter an invalid char in th ervius kitchen
[Windows Mobile] dddrko:
Thank you for the images, but I have one problem: why isn't toolbar text bubble buttons transparent but gray? Is there any registry key?
[Windows Mobile] yardi4life:
I cannot seem to change the ****_pivot_background.png that shows on the setting pages. Even though I replace the files for their respective themes. Any ideas? I'm using 240x400 res (omnia i910).

Also is the windows flag for the start menu still stored in shellres.*.dll?
[Windows Mobile] OndraSter:
no, it is <your theme name>_bubble_flag.png, it means like rockandrepublicblack_bubble_flag.png
[Windows Mobile] torankusu:
skinning tutorial

Hi all,

Wow guys you've really become geniuses when it comes to skin down WM6.5.x, you should, all (involved in the skinning) ,create a thread or a post with steps on which files and what to do on how to skinning wm6.5 because your skinnings are awesome.
[Windows Mobile] wonsanim:
I realy like this layout.I this rom Compatible with my device I have an HTC X7510 WM 6.1 HTC Original ROM.
[Windows Mobile] Shady313:
Sorry, It's only for HTC Artemis :(
[Windows Mobile] wonsanim:
Thanks Shady is realy a great ROM,the skin looks amazing.Some of You Guys can Point me to find a 6.5 Rom for an HTC X7510.
[Windows Mobile] ace10134:
http://xdaforums.com/forumdisplay.php?f=455

We aren't your slaves for finding things!
[Windows Mobile] Cal-El:
Ok, I just built a 23034 ROM on my Rhodium and the softkey bar shows white and the phone and camera softkeys are jammed into the left corner and the start text is still in the top left corner but doesnt open the start menu just the titlebar! What could be causing this do dyou think? :)
[Windows Mobile] + Que PPC:
Hey hey hey calm down, calm down...

We are here to help others... the guy is new here and has two beautyfull devices (envy in its highest level!)

First help with a link... if new, if not invite him to use the search tool, if not read the wiki, if not you can start to Blame but discret... hahaha my mouth is bleeding :p

fair play guys... ace... it seems that you becomes his slave buddy "BY YOURSELF"... :p calm your horses man.

HEY CAL-EL

The satrt menu in the upperbar is not an issue is the name of the windows currently seeing... if you change to the folder connections it changes to connections... :) the camera.... mmmm you need a new camera skin or app. my old camera do the same thing so i switch to the moded (For someone long time ago) :p
[Windows Mobile] Cal-El:
The camera is fine, its the softkeybar that is messed up, I cant get into the start menu at all and the the two softkeys that are there are in the far left corner! lol! thanks for answering though! JAJAJA! ;)
[Windows Mobile] WoZZeR999:
For those that had problems with ezinput 2.1, were you using the Mega packages (Da_G's rom dump), or pcarvalho's version?

After switching to pcarvalho's and making it an OEM (I deleted out the stuff that was in Framework), I can switch between numbers and letters again.
[Windows Mobile] Cal-El:
Cant take one my mobiler sucks, I may have figured it out though! I will let you know! :)
[Windows Mobile] Cal-El:
Got it fixed! there were some left over files in my OEM folder that were over writing the new 23034 SYS folders so I took them out! Its so nice! lol! Thanks everyone! :)
[Windows Mobile] torankusu:
Hi Guys,

dude i so envy you every time you post you are having issues or trying to cook a Rom for the beautiful, almighty, Touch Pro 2 (Rhodium). I can't wait for the Sprint Touch Pro 2...... :D
[Windows Mobile] Captain_Throwback:
Magnifier Exclusions

Since I was having issues trying to zoom in Opera with Magnifier enabled, I poked around the Registry, and noticed this key:

[HKEY_LOCAL_MACHINE\System\GWE\MAGNIFIER\EXCLUDE]

Under that key, there are sub keys for CPROG & IEXPLORE. I added one for OPERA, and then under it added the key for "PROCESS"="OPERA9.EXE", and Magnifier no longer bothers me in Opera :).

[HKEY_LOCAL_MACHINE\System\GWE\MAGNIFIER\EXCLUDE\OPERA]
"PROCESS"="OPERA9.EXE"

So I'd imagine you can exclude any progams that you don't want Magnifier to mess with. Perhaps others can try it and see if it works.

EDIT: Is anyone else having issues with the Sensor SDK 4? Nothing is rotating for me at all.
[Windows Mobile] blazingwolf:
Hmm. Seems better but still not as good as I would like. Thanks. :)
[Windows Mobile] supps2:
Just check, no rotation with SDK 4
[Windows Mobile] NotATreoFan:
If I read correctly, the Gen.Y Manila thread says our devices are not compatible with SensorSDK 4.
[Windows Mobile] jmckeejr:
Been using SDK 4 for months now :eek: Cant check rotation now, but it was working in previous builds.
[Windows Mobile] chriscsh:
i have this issue before (and i'm not using the VC), maybe too many modules, try recMod some (eg. all modules inside "browsingie" folder)
[Windows Mobile] m.carroll:
i've never been able to build it successfully for the fuze... maybe i'm missing something, but i just tried to grab the latest package from the leo...
[Windows Mobile] aruppenthal:
What is the name of the logo file being used for start and what folder is it in. Im guessing its not getting pulled from shellress now lol since i changed that one.
[Windows Mobile] dan-htc-touch:
hey buddy, care to share where you got that xmlgui from? been googling for a while since I saw your post
[Windows Mobile] blazingwolf:
Base_DPI_96 or 192 if VGA. classicblue_bubble_flag.png and classicblue_bubble_flag_disabled.png.
[Windows Mobile] Cal-El:
How do I get the custimazation screen? mine never does that! Is it located in the OEM folder? :)
[Windows Mobile] + Que PPC:
Touch pro 2 HUH? it must be on oem\<device>\Common\Operatorpkg\
[Windows Mobile] wmserver:
Put this in initflashfiles.dat in OEM\Raphael\0409\OEM_Lang_0409:

;++++++++++++++++++++++++ Files for AutoRun +++++++++++++++++++++++++

Directory("\Windows\StartUp"):-File("CheckAutoRun.lnk","\Windows\CheckAutoRun.lnk")

;------------------------ Files for AutoRun -------------------------

;++++++++++++++++++++++++ Files for AutoShortcut +++++++++++++++++++++++++

Directory("\Windows\StartUp"):-File("AutoShortcut.lnk","\Windows\AutoShortcut.lnk")

;------------------------ Files for AutoShortcut -------------------------

;++++++++++++++++++++++++ Files for HTCStartUp +++++++++++++++++++++++++

Directory("\Windows\StartUp"):-File("HTCStartUp.lnk","\Windows\HTCStartUp.lnk")

;------------------------ Files for HTCStartUp -------------------------
[Windows Mobile] Cal-El:
Hwo do I get it into initial flashes dat? I have a TP2 BTW! I think it may be different! :)
[Windows Mobile] dan-htc-touch:
oem_lang_xxxx edit with ms word(heard it works without hex editing), or notepad(will require hex edit removal of the first two bytes FF FE)
[Windows Mobile] NotATreoFan:
I'm going by this:
[Windows Mobile] NotATreoFan:
So are there any other free options for a SIP since EzInput is misbehaving with the latest builds?
[Windows Mobile] Cal-El:
Where in the Initialflashes do I put it, in the begining? Sorry I am just learning this stuff! Thank you for your help! :)
[Windows Mobile] abc001:
It seems to me that there is still no proper solution for correcting the picture distortion on ATContact. Am I right? Is there anyone has got a solution? thank you.
[Windows Mobile] WoZZeR999:
I cooked pcarvalho's version in, instead of the raw mega package, and that fixed it with 23034. Mega worked fine in 23016.
[Windows Mobile] dan-htc-touch:
near the end is where it usually is, but should not matter much, might have to come after the stuff at the beginning, not sure though, never really looked into it
[Windows Mobile] Cal-El:
Cool. Thanks man! Working with a new kitchen and fresh dumped and ported 6.5 OEM so I have to start from scratch on everything! I am used to being spoiled with Da_G! :)
[Windows Mobile] jakdillard:
you have a tp2 so instead of autorun you would be using runcc which should start on its on via registry in the package so make sure that you are including the runcc package
[Windows Mobile] drkfngthdragnlrd:
No, it needs to be Visible="False" It is only supposed to show when your have Active Appointments & the whole section (Clock/Appointments) moves upward to make room for it. This is why there's an OnInitComplete="Binding:LockScreen,LS_Appointments". This tells CHome to only show the Visible="False" items if there's an active Appointment. Same as how Titanium aka CHome has Visible="False" on pretty much everything. This way they only show when called to show & you don't see every Condensed & Expanded Plugin Layout all the time. It is how CHome works.
[Windows Mobile] drkfngthdragnlrd:
I answered this a while Back. Write the Contact Image registry manually to your original images. ATFavPeople is taking that image & resaving it to \AppData\ATContact(?!?!? Don't remember exact directory). In doing this it's causing a formating error CHome no longer likes. So, just use CHome Editor & edit the Contact Images to the original image on your storage card or where ever. Keep in mind anytime you update your contact you'll have to reapply the fix.
[Windows Mobile] abc001:
Thank you. But your method is still not working for me. Some pictures have been distorted but not all. I have tried in my own way again and again, and this time it works!

I just copy all *.jpg from \application data\atcontacts on my mobile to my pc. Then edit those distorted pictures using an undistorted one as template, copy and paste, with Paint Shop Pro. Recopy all of them back to my mobile.
[Windows Mobile] drkfngthdragnlrd:
Yeah, maybe it's the fact we have to use old GAC's to make ATFavPeople work that's currupting those images. I just noticed if I used the Pictures on my Storage Card it was fine, but if any pictures came from that directory, they'd be screwed up. The App copies your images there & reformats them to JPG. Something in that process is screwing them up in these newer builds.
[Windows Mobile] rgb-rgb:
Tried setting the Appontment icon to false, but it did not show up even when I did have an appointment showing. The section does move up and the text for the appontment shows, but the icon itself did not show once I set it to False. Could have just been somethig that I didn't do correctly though. I did have to make some changes to the LockScene.cpr files because of the narrower Top TaskBar.

In the LS_LockScene_480x640.cpr file I ended up changing the following line to Top="400". It was Top="380".

<LockScreenPaneView ID="PaneView" Top="400">

Also, in the LS_Global_480x640.cpr file, I had to change the following line to Top="-32". It was Top="-52"

<Image ID="Background" Left="0" Top="-32" Width="480" Height="640" Visible="True" Opacity="1.0" ScalingAlgorithm = "TriLinear" Source="ConfettiPlus::WallpaperBitmap"/>

There are some changes that need to be made in other .cpr's as well like LS_AlarmScene_480x640.cpr to account for the Top Taskbar being narrower as well.
[Windows Mobile] furb3t:
Hi .... i've tried to read all post to found if someone already had my same problem, but I have found nothing. So...this is my problem: i have ported successfully on my kaiser tytnII the build 23034, but when I press start menu and then scroll up and down I see all icon with a motion effect, and than if I tap on a submenu like Setting, I can see in background the previous icons, after same taps, all screen is full of icons. Some suggestions ?!
[Windows Mobile] kidoucorp:
Anyone is having troubles with SIP menu & Build 23034 ?

I haven't anymore the SIP Menu in Settigns --> Personnal --> Input Settings

EZInput is working fine, but I can't switch to any other keyboard :(
[Windows Mobile] Lokatho:
Did you read post 3???
[Windows Mobile] Piter1225:
Go to SYS\Shell, find

1f1aca24-d942-464a-9281-10567741499c.rgu

Find line "[HKEY_LOCAL_MACHINE\ControlPanel\Buttons]" and delete redirect line.
[Windows Mobile] kane159:
hay dude , that's ezinput's issue not ROM's ;)

by the way whitch ezinput pack you use???

i use mega's PACKAGE_MEGA_IME_Engine_Western and PACKAGE_MEGA_IME_EzInput_Western but i cant switch to symble.....
[Windows Mobile] kidoucorp:
Oups, my bad, read it a long time ago, and didn't noticed the trick :D

It's working fine now, Thanks :D

Can't remember what version i'm using (2.1, but don't know which build exactly), but will check it when I get back to home ;)

Anyway, I don't have any problem with symbols or anything else, all my keyboards are working fine (Full QWERTY, Compact, PhoneKeypad)
[Windows Mobile] Slv:
In the LS_Global_[...].cpr file, change Source field to Source="ConfettiPlus::WallpaperBitmap"

for example:

<Image ID="Background" Left="0" Top="-32" Width="480" Height="640" Visible="True" Opacity="1.0" ScalingAlgorithm = "TriLinear" Source="ConfettiPlus::WallpaperBitmap"/>
[Windows Mobile] furb3t:
I don't think this is the solution....this is my Ls_global_....:
[Windows Mobile] rgb-rgb:
LS_Global .cpr's are for the LockScreen

You would probably need to look at something in the StartMenu .cpr's instead.

Maybe try StartMenu_Global_XXX_XXX.cpr instead
[Windows Mobile] furb3t:
This is my starmenu_global.....

to be continued :)
[Windows Mobile] NotATreoFan:
I found a QVGA package from him. Is there a VGA or autoscaling version available?
[Windows Mobile] qtotter:
screen alignment mui

The 0411 (Japanese) MUI for 23034 is lacking of the translation of the screen alignment...

It shows "Using a stylus, tap the target...." in English not in Japanese. Does anyone know which *.dll or *.exe shows this message so that I can fix it myself?

P.S. I found it myself. It was gwes.exe. Looking at the other *.mui files, it looks like language files are not complete and mixed with old ones...

Thanks.

qt
[Windows Mobile] ahmedfikry:
try changing it to:

<Form Width="240" Height="320">

<Image ID="Background" Left="0" Top="-27" Visible="True" Opacity="1.0" ScalingAlgorithm = "TriLinear" Source="ConfettiPlus::WallpaperBitmap"/>

</Form>
[Windows Mobile] jmckeejr:
The version I have is an older version when sdk 4 was first released(if it aint broke dont fix it). Capn, my rotation is working, dont have version # offhand, will look when I get home if you want.
[Windows Mobile] schreda:
how can we get the good old softkey bar?
[Windows Mobile] empds:
Hi guys

With 23034 build Gen.Y Manila 2.1 (TF2D2.1) does not start up. Does anyone have a fix for this?

Thanks in advance
[Windows Mobile] blazingwolf:
Go back to an older build.
[Windows Mobile] Captain_Throwback:
Rotation is working in build 23034? I had it working fine in previous builds. Maybe I just need to re-flash. I think the missing Start Menu link on the top bar may be breaking Sensor SDK 4. Manila Start Menu has no way of launching without the icon at the top. That could be causing an issue. I'm going to re-flash 23034 & see if it works or not.

@NATF

That reference in the GenY thread is just stating that the Auto-Rotation toggle in the Manila interface doesn't work to enable/disable auto-rotation with the older version of Sensor SDK 4 (1911.2326). But that version of the Sensor SDK 4 works fine with Manila. Also, my issue with lack of rotation isn't just with the Manila interface - nothing is rotating for me at all.
[Windows Mobile] GTx-M.M:
Is this work on VGA Resolution Thanks a billion
[Windows Mobile] programatix:
I've posted it here. http://xdaforums.com/showthread.php?t=551813
[Windows Mobile] schreda:
sure, but is it stable as like as the newer build?

there must be a way to midify some files..
[Windows Mobile] kane159:
share it share it please :D

then my first release rom can be done gigigi

i call it TriKI

(i have Trinity and my name is wai kie :Pa Chinese name gigi)
[Windows Mobile] jmckeejr:
Maybe thats it then, because I dont like/use manila start menu at all. I use the program tab instead and 6.5 start menu which looks pretty sweet now that I have high res icons throughout :)

I do have one issue I am not sure if build related or mod related. I am using new BG4all tabs and I get remnants of some screens on very top portion where top bar used to be. I ask because it may also be related to the smaller top bar, does anyone have a similar issue?
[Windows Mobile] ahmedfikry:
QVGA only lockscreen fix for appointment icon bug

I have a QVGA device running 23034.... & here is my fix for the appointment showing in lock screen page

Basically the top bar is now smaller & things have to be shifted up by 8 pixels:

change the following in:

LS_Global_240x320.cpr

<Image ID="Background" Left="0" Top="-18" Width="240" Height="320" Visible="True" Opacity="1.0" ScalingAlgorithm = "TriLinear" Source="ConfettiPlus::WallpaperBitmap" />

LS_Global_320x240.cpr

<Image ID="Background" Left="0" Top="-18" Width="320" Height="240" Visible="True" Opacity="1.0" ScalingAlgorithm = "TriLinear" Source="ConfettiPlus::WallpaperBitmap" />

then in:

LS_LockScene_240x320.cpr

<LockScreenPaneView ID="PaneView" Top="198">

LS_LockScene_320x240.cpr

<LockScreenPaneView ID="PaneView" Top="118">

in the last 2 files...leave appointment as "True" to be able to see the icon when you have an appointment...no need to change false (old fix) as things are shifted now & it will not show when you have no appointments

PLEASE DONATE by clicking the link below
[Windows Mobile] Captain_Throwback:
ok, good, that gives me somewhere to start looking. And yes, I also have that issue because of the smaller top bar. The small sliver between where the new top bar ends and where the top of Manila begins. That's something that would need to be adjusted in the Manila interface, I guess. Though it would make more sense that M$ should have the OS adjust windows to fit the screen properly.
[Windows Mobile] empds:
I Captain_Throwback. I have notice that you are very "active" in this threat and also in Gen.Y Manila R1.1 among others, so you must be a very busy man now that you are a moderator too.

I have a problem and I just wonder if you could be so kind to help me.

I am trying to build my custom Rom with 23034 build and Gen.Y Manila R1.1 OEM files. I am using lobsterdave Diamond-GSM-Kitchen and I am able to cook the ROM with success but when I start my device I receive a message "unable to start manila press here" (or something like that) and when I press in this message nothing happens.

The thing is that if I use Gen.Y Manila R1.1 OEM files but this time with 23017 build I have no problems at all.

Did you manage to run Gen.Y Manila R1.1 with 23034 build, I am missing something?

Thanks in advance
[Windows Mobile] torankusu:
i use the wm default dialer so it's not that. my battery icon looks normal, i just don't get it, i think it is something with my OEM folder or oemdrivers or maybe registry related.
[Windows Mobile] + Que PPC:
The registry dont change icons in the taskbar

you must to have a shellres dll somewhere in your oem packages. check every folder man.
[Windows Mobile] BesFen:
Are you sure there isn't shellres.192.dl in EXT or OEM folder?, that folder will be process after SYS, so the default shellres.192.dll will be replaced.
[Windows Mobile] torankusu:
ok, here is the thing; i have a vista orb skin for wm6 folder with a shellres.192.dll.0409.mui, i'm almost sure this is the issue BUT i never check that option on buildos so why is this shellres from this folder included into my custom rom when i am not even selecting that to be cooked into the rom?
[Windows Mobile] indagroove:
Delete CDMA_RSSI_PPC.dll from your OEMdrivers folder, and the reg entry that points to it in the .rgu of the OEMdrivers.
[Windows Mobile] indagroove:
Nice guide. It does have a couple of unecessary steps, but will work nonetheless. I did notice that you caught my error from this post: http://www.everythingdiamond.info/showpost.php?p=2879&postcount=2 (thanks for linking btw). I did accidentally delete the names of the six modules that you noticed were excluded from my post. The post is fixed, but you may (or may not) want to edit the tutorial to eliminate any confusion as to the process.
[Windows Mobile] BesFen:
So you still use old kitchen, buildOS will report error if you have file with same name, and if you are not encounter error during BuildOS process it mean there is only one shellres.192.dll and one shellres.192.dll.0409.mui in your kitchen. :rolleyes:

Since you don't use vista orb skin, How if you get shellres.192.dll.0409.mui out from your kitchen?? but i don't sure about it.
[Windows Mobile] ace10134:
Hey, can someone upload their entire XIP folder for this build? (Hopefully an XIP folder fresh from the build, not modified much.)

Could someone do that? I can't get the xip.bin to dump properly, but I do know how to port the XIP folder.
[Windows Mobile] BesFen:
http://xdaforums.com/showpost.php?p=4283250&postcount=161
[Windows Mobile] indagroove:
Already done, right here:

http://xdaforums.com/showpost.php?p=4283250&postcount=161
[Windows Mobile] ace10134:
I knew someone would have done that! Wait, I read through this whole thread yesterday, must have glanced over that.

Whatever, that was my one free-pass token. lol. Thanks guys.
[Windows Mobile] twopumpchump:
look in my kitchens folder of my sig you will find most of them there ;)
[Windows Mobile] stouph52:
hi every body

good work DA G i love this version:):D:p

i have just a bug of graphism

when i enter the start menu the taskbar doesn't hide?

what i do for solved it?

edit

i don't have option of input and button

what i do for have it?

edit

i find for problem input button and owner

i just change in rgu of shell

remove the value "redirect" of input,button and owner

thanks in advance for your answer
[Windows Mobile] sheennick123456:
is it possible to get native nk.exe for older devices?

hermes has got that

can it be done for artemis?
[Windows Mobile] stouph52:
it's possible show me i ported xip on asus p535:)
[Windows Mobile] benko286:
can somebody tell me how to add .exe files into kitchhen?
[Windows Mobile] stouph52:
create a folder and make in your exe and with package creator create a package:);)
[Windows Mobile] krazy_about_technology:
Wow! That will be great :) Can you do it for Gene also?? I am attaching the xip.bin for my latest rom. Its not ported fully, its from my platformrebuilder kitchen, it does the porting itself.
[Windows Mobile] X1iser:
For this problem check StartMenu_Global_XXXxXXX.cpr

<Form Width="XXX" Height="XXX">
<Image ID="Background" Left="0" Top="-[SIZE="5"][B]XX[/B][/SIZE]"/>
</Form>

Change "Top" 0 with XX in StartMenu_GridScene_XXXxXXX.cpr

<GridView ID="Start Menu Items List" Top="[SIZE="5"][B]0[/B][/SIZE]" Left="0" Width="YYY" Height="ZZZ" Columns="3" Scrollable="TRUE" HexagonGrid="TRUE" HorizontalWrapAround="TRUE" PaginatedScrolling="TRUE">

It work for 480x800 for me :)
[Windows Mobile] benko286:
and where to find package creator?
[Windows Mobile] blazingwolf:
By the time you have changed the files you are back to the older builds.

Yes, there are stable older builds.
[Windows Mobile] kidoucorp:
I'm @ work right now, but I'll upload it once I get back to home ;)

Ps : It's an older build than in the EzInput thread, the Tutorial is not working.
[Windows Mobile] schreda:
sorry but i think i'm missunderstandung you!

why change all files? ther must be one file that is responsible for that!

are now the newer or the older build more stable?
[Windows Mobile] GTx-M.M:
excuse me a said VGA

i think VGA is diffrent from QVGA can you guide how can i change it on VGA

sorry for my bad english
[Windows Mobile] dcd1182:
your request makes no sense. you are clearly concerned with stability, yet you obviously prefer to experimentally modify 2302X+ to emulate older builds. this is quite ironic.

i've been trying to tell you guys for some time now that mixing files from old builds into new builds does nothing productive, has unknown side effects, and causes problems that people then post about for page after page.

if you want 23016, run 23016. everyone needs to stop asking how to turn one build into another build, there is no point, it accomplishes nothing positive.