[SOLVED]Phone freeze after a call in 23673 build - Windows Mobile

hello to all i have cooked a rom with 23673 and rhodium s2 as base i have used i used the incoming call fix and i used the cloudy bold font fix, i have encountered a problem after finishing my call whe i click in finish appel the phone is freezing.....
after its return to normal....will anyone please help me if u have any solution.....

Use this fix instead of the Caller ID Fix you're using right now.
EDIT: In case you wanted to know, it contains cprog.exe, lockscreen.dll, pimstore.dll and tpcutil.dll from 23569. I'm not sure if you need lockscreen.dll. Credits go to sorg? I think...

seeM_ZA said:
Use this fix instead of the Caller ID Fix you're using right now.
EDIT: In case you wanted to know, it contains cprog.exe, lockscreen.dll, pimstore.dll and tpcutil.dll from 23569. I'm not sure if you need lockscreen.dll. Credits go to sorg? I think...
Click to expand...
Click to collapse
thanks bro will try this

I tried to build using 23673, but after messing around with the dialer and getting those delays, and also having some call history problems I think (Then I tried the Hashu, I gave up and reverted temporarily to 23569. If this all works could you post up you solutions re the dialler - I would be very interested in another shot at 23673.
Cheers
C.

seeM_ZA said:
Use this fix instead of the Caller ID Fix you're using right now.
EDIT: In case you wanted to know, it contains cprog.exe, lockscreen.dll, pimstore.dll and tpcutil.dll from 23569. I'm not sure if you need lockscreen.dll. Credits go to sorg? I think...
Click to expand...
Click to collapse
Great solution. Thanks a lot.

seeM_ZA said:
Use this fix instead of the Caller ID Fix you're using right now.
EDIT: In case you wanted to know, it contains cprog.exe, lockscreen.dll, pimstore.dll and tpcutil.dll from 23569. I'm not sure if you need lockscreen.dll. Credits go to sorg? I think...
Click to expand...
Click to collapse
thanks bro its works great ....

After applying the patch call history is not updated anymore. Any similar cases? any solution? Thanks.

giorgina351 said:
After applying the patch call history is not updated anymore. Any similar cases? any solution? Thanks.
Click to expand...
Click to collapse
you finded solution? or problem was gone?

seeM_ZA said:
Use this fix instead of the Caller ID Fix you're using right now.
EDIT: In case you wanted to know, it contains cprog.exe, lockscreen.dll, pimstore.dll and tpcutil.dll from 23569. I'm not sure if you need lockscreen.dll. Credits go to sorg? I think...
Click to expand...
Click to collapse
Life saver, was getting so frustrated with the Incoming no avatar problem. With the other fix where the 3 filese were from the Phone Redist package, works when there are no contacts but once I sync with Exchange, it starts to momentarily freeze the keypad. With this set, it solves the problem totally. Thanks.

seeM_ZA said:
Use this fix instead of the Caller ID Fix you're using right now.
EDIT: In case you wanted to know, it contains cprog.exe, lockscreen.dll, pimstore.dll and tpcutil.dll from 23569. I'm not sure if you need lockscreen.dll. Credits go to sorg? I think...
Click to expand...
Click to collapse
Thanks for sharing dud.

The caller id fix from sys 23569 together with Phone_Canvas_Enhancement_2G_4_2_62520161331_0_PdaXpert.zip finally solve my build for 23144, it works perfectly.
Recently I've tried with the new phone canvas from leo 3.14 with fixes and caller id fix, however the phone will hang, but nevermind, I'll just use the older phone canvas.
Thanks for everyone.

seeM_ZA said:
Use this fix instead of the Caller ID Fix you're using right now.
EDIT: In case you wanted to know, it contains cprog.exe, lockscreen.dll, pimstore.dll and tpcutil.dll from 23569. I'm not sure if you need lockscreen.dll. Credits go to sorg? I think...
Click to expand...
Click to collapse
Thank you, with this 4 files replaced in build 28240, all bugs are fixed!!

Can you please tell me how to install this FIX
seeM_ZA said:
Use this fix instead of the Caller ID Fix you're using right now.
EDIT: In case you wanted to know, it contains cprog.exe, lockscreen.dll, pimstore.dll and tpcutil.dll from 23569. I'm not sure if you need lockscreen.dll. Credits go to sorg? I think...
Click to expand...
Click to collapse
Can you please tell me how to install this FIX

Related

[SOLVED]COM5 Expire watermark

How do you disable Beta expiration?
Make an "app.reg" with this key:
Code:
[-HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\DeviceBeta]
then put it in an EXT folder.
Works like a charm. Thank you so much!
No problem...you are wellcome
Anyone help?
I have tried a couple of times now to use mortscript to remove the "BETA" tags from the registry. I obviously am doing it wrong - can someone post what the mortscript should be for me please?
this is what I tried just now and still no go...
Code:
If ( RegKeyExists("HKLM","\Software\Microsoft\Shell\Device Beta"))
RegDeleteKey("HKLM","\Software\Microsoft\Shell\Device Beta",TRUE,TRUE)
EndIf
Thanks
DT
d_train said:
I have tried a couple of times now to use mortscript to remove the "BETA" tags from the registry. I obviously am doing it wrong - can someone post what the mortscript should be for me please?
this is what I tried just now and still no go...
Code:
If ( RegKeyExists("HKLM","\Software\Microsoft\Shell\Device Beta"))
RegDeleteKey("HKLM","\Software\Microsoft\Shell\Device Beta",TRUE,TRUE)
EndIf
Thanks
DT
Click to expand...
Click to collapse
I may be wrong but I don't didn't the os like it if the registry is removed. It'll probably add them back.
I'd just put that in a app.reg in the last package to be processed by the kitchen like this:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\DeviceBeta]
"Today"=""
"Expiry"=""
"Reminder"=dword:00000000
wmserver said:
I may be wrong but I don't didn't the os like it if the registry is removed. It'll probably add them back.
I'd just put that in a app.reg in the last package to be processed by the kitchen like this:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\DeviceBeta]
"Today"=""
"Expiry"=""
"Reminder"=dword:00000000
Click to expand...
Click to collapse
I use old my own style kitchen with OEMs.
and simply include it in a .rgu file:
Code:
[-HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\DeviceBeta]
Don't know if works in app.reg in new style kitchens.
babak00000 said:
I use old my own style kitchen with OEMs.
and simply include it in a .rgu file:
Code:
[-HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\DeviceBeta]
Don't know if works in app.reg in new style kitchens.
Click to expand...
Click to collapse
just delete all instances of DeviceBeta from Shell rgu.
MietasSR said:
just delete all instances of DeviceBeta from Shell rgu.
Click to expand...
Click to collapse
I remove this.... but still have a bug for beta... white screen etc..
Nokser said:
I remove this.... but still have a bug for beta... white screen etc..
Click to expand...
Click to collapse
You need to patch shell32.exe. Da_G posted one in his thread. Use that.
For lazy people like me, use the attached pkg and put in your EXT. It will replace SYS reg..
ai6908 said:
You need to patch shell32.exe. Da_G posted one in his thread. Use that.
For lazy people like me, use the attached pkg and put in your EXT. It will replace SYS reg..
Click to expand...
Click to collapse
I still have bugs...
Nokser said:
I remove this.... but still have a bug for beta... white screen etc..
Click to expand...
Click to collapse
And later:
Nokser said:
I still have bugs...
Click to expand...
Click to collapse
White screen has nothing common with beta watermark or shell32 time-bomb

[QUESTION] automatic reboot at first boot

Hi
My ROM has some tweaks and extras that needs a soft reset after initialization wth 1st boot. How can I make a automatic reboot just the 1st time the phone boots up?
If you're using RunCC, edit your *.rgu/app.reg accordingly:
Code:
[HKEY_LOCAL_MACHINE\Software\HTC\RunCC]
"ResetDevice"=dword:00000001
How can I know if I use runCC?
You don't know which packages you're using for your ROM? Funny thing!
animelover said:
You don't know which packages you're using for your ROM? Funny thing!
Click to expand...
Click to collapse
hehe... just using a dump of official rhodium S2, and spiced it up a bit, and deleted things I don't need
Take a look into EXT -> Rhodium -> Your Build -> Rhodium_External_Packages and search for "RunCC"!
animelover said:
Take a look into EXT -> Rhodium -> Your Build -> Rhodium_External_Packages and search for "RunCC"!
Click to expand...
Click to collapse
yeye... there it is Thanks
animelover said:
You don't know which packages you're using for your ROM? Funny thing!
Click to expand...
Click to collapse
Funny indeed. These are the junior cooks we get these days...
No offense here but ...
I think all of great cooks started as "junior"
Even the big NRGZ28
best regards
fwt
hey hey... fair play ppl... glad to have new chefs CC is for that... new chefs and experienced chefs
fwt said:
No offense here but ...
I think all of great cooks started as "junior"
Even the big NRGZ28
best regards
fwt
Click to expand...
Click to collapse
Very true..
Anyways, I love your sig And it's quite funny how true it is!
if i might stick with the topic
2 - xda_uc also offers a reboot after customization - you could add this to your ext
3 - old method: autorun + checkautorun pkg also reboots your rom (dump blackstone or kovsky)
Problem With add2config Packages?
Hey, I had this problem before where all my packages that I cook in with the add2config method (so they can be removed by the user) aren't installing / aren't being set as default...
These are the following packages that I have the problem with:
BG4All Tabs (add2config) - Doesn't appear in the rom at all
A 6.5.5 Theme (add2config) - Isn't default but is in the list of themes
A 6.5.5 Taskbar (add2config) - Doesn't appear in the rom at all
All this was solved when I changed the runcc rgu file: e110406e-9af4-4cdc-932d-255ac9636f4d like everyone says to "ResetDevice"=dword:00000001
But since rebuilding my kitchen im having the same problem, Ive changed the reset device to 00000001 but still none of the add2config packages are working has anyone got any solutions?
Thanks
[★] said:
Hey, I had this problem before where all my packages that I cook in with the add2config method (so they can be removed by the user) aren't installing / aren't being set as default...
These are the following packages that I have the problem with:
BG4All Tabs (add2config) - Doesn't appear in the rom at all
A 6.5.5 Theme (add2config) - Isn't default but is in the list of themes
A 6.5.5 Taskbar (add2config) - Doesn't appear in the rom at all
All this was solved when I changed the runcc rgu file: e110406e-9af4-4cdc-932d-255ac9636f4d like everyone says to "ResetDevice"=dword:00000001
But since rebuilding my kitchen im having the same problem, Ive changed the reset device to 00000001 but still none of the add2config packages are working has anyone got any solutions?
Thanks
Click to expand...
Click to collapse
I'm not sure anyone will be able to answer that without being totally lucky if you don't post your packages or build-log or at least the add2config text files. Anway, maybe you already do this, but if you don't, then start doing this: after cooking, look in the dump and make sure everything is there. Also, look at config.txt to make sure all the add2config's were compiled properly. This will save you the flash-disappointment.
Ok theres my buildlog, my run cc rgu file and one of my add2config files Thanks.
fwt said:
No offense here but ...
I think all of great cooks started as "junior"
Even the big NRGZ28
best regards
fwt
Click to expand...
Click to collapse
Yeah, but I wasn't cooking ROMs for the public until I knew what the hell I was doing... lol
NRGZ28 said:
Yeah, but I wasn't cooking ROMs for the public until I knew what the hell I was doing... lol
Click to expand...
Click to collapse
lol, also I did this way...
Can't remember where I read something like "PPL: Could you make it in this language?" - " "COOK": I don't know how to!"
LOL
[★] said:
Hey, I had this problem before where all my packages that I cook in with the add2config method (so they can be removed by the user) aren't installing / aren't being set as default...
These are the following packages that I have the problem with:
BG4All Tabs (add2config) - Doesn't appear in the rom at all
A 6.5.5 Theme (add2config) - Isn't default but is in the list of themes
A 6.5.5 Taskbar (add2config) - Doesn't appear in the rom at all
All this was solved when I changed the runcc rgu file: e110406e-9af4-4cdc-932d-255ac9636f4d like everyone says to "ResetDevice"=dword:00000001
But since rebuilding my kitchen im having the same problem, Ive changed the reset device to 00000001 but still none of the add2config packages are working has anyone got any solutions?
Thanks
Click to expand...
Click to collapse
[★] said:
Ok theres my buildlog, my run cc rgu file and one of my add2config files Thanks.
Click to expand...
Click to collapse
Bumping my own question
[★] said:
Ok theres my buildlog, my run cc rgu file and one of my add2config files Thanks.
Click to expand...
Click to collapse
The add2config.txt file is in the wrong folder; it needs to go in the \files sub-folder of the EXT. Put it in there, and you're problems should go away.
Edit: although, I'm seeing this in the build-log:
Found: 1 Extra Info on a Package... Populating config.txt with: CAB: \Windows\B4ALL.cab
Click to expand...
Click to collapse
and this:
Processing "B4ALL.cab" as file
Click to expand...
Click to collapse
So, I guess I don't really understand why the .cab isn't installing. I've never used runcc before, so I can't help you on what may be going on with it. I guess it's ok to put the add2config in the main folder, since it looks like it's compiling correctly.
2nd Edit: all the cab is doing is adding a couple of manila files; you should just dump the two files and put them in an EXT and have them over-write the stock manila files. You don't need to run this as a cab, as far as I can tell.
You need to fix this (minor, but might as well do it):
Failed to parse value name HKEY_LOCAL_MACHINE\Security\Shell\StartInfo\start\Tools\Format SD Card.lnk!!!
Click to expand...
Click to collapse
Farmer Ted said:
The add2config.txt file is in the wrong folder; it needs to go in the \files sub-folder of the EXT. Put it in there, and you're problems should go away.
Edit: although, I'm seeing this in the build-log:
and this:
So, I guess I don't really understand why the .cab isn't installing. I've never used runcc before, so I can't help you on what may be going on with it. I guess it's ok to put the add2config in the main folder, since it looks like it's compiling correctly.
2nd Edit: all the cab is doing is adding a couple of manila files; you should just dump the two files and put them in an EXT and have them over-write the stock manila files. You don't need to run this as a cab, as far as I can tell.
You need to fix this (minor, but might as well do it):
Click to expand...
Click to collapse
(disregard my last post on the other thread, I didnt realise you had replied )
Thanks for the response, yeah the add2config file has worked before in the root of the packages, seems something else it buggy :/
Yeah that cab may be so, but that was an old one just as an example, I really need to get it working for this mortscript thing we discussed on the other thread..
Maybe we could discuss more tomorrow ? Perhaps you could have a nosey in my kitchen or something, I know I should work this stuff out myself, but as a chef still in training, its quite difficult to know what to look for, and help from peopel like you is priceless
Thanks

[Solved] howto Resolve blank space

Can someone tell me howto resolve the blank space as in attached image?
As you can see this happens in a Dutch ROM, issue doesn't appear in WWE version of the same ROM
Here's the solution with thanks to DiegisOn:
Diegis0n said:
I edited the 0413.mui file and it works !!
I'll upload it
http://rapidshare.com/files/392988811/SettingImprovement.exe.0413.mui
Click to expand...
Click to collapse
patensas said:
Can someone tell me howto resolve the blank space as in attached image?
As you can see this happens in a Dutch ROM, issue doesn't appear in WWE version of the same ROM
Click to expand...
Click to collapse
Will check on my NLD rom if this is also happening
Diegis0n said:
Will check on my NLD rom if this is also happening
Click to expand...
Click to collapse
If not i hope you can supply the solution to
patensas said:
If not i hope you can supply the solution to
Click to expand...
Click to collapse
It's also blank in mine
2 ways to fix it:
- Use the latest "SettingImprovement.exe.0409.mui" and rename to 0413 <-- my advise
or
- Use the "Settings_Improvement_1_0_19211330_06" from the stock 1.66 NLD rom
It's probably due to the fact that you're using a 0413.mui that doesn't fit the newer package
(Just like QuickGPS, Voice Recorder and some others ...)
Diegis0n said:
It's also blank in mine
2 ways to fix it:
Click to expand...
Click to collapse
My guess would be there's a manila file that's missing a translation or something since documents tab isn't officially released in Dutch.
Will try your suggestion in a bit.
What other packages suffor the same issues with 0413 problems?
I know about g-sensor calibrator, QuickGPS and Voice recorder and you know about more?
patensas said:
My guess would be there's a manila file that's missing a translation or something since documents tab isn't officially released in Dutch.
Will try your suggestion in a bit.
What other packages suffor the same issues with 0413 problems?
I know about g-sensor calibrator, QuickGPS and Voice recorder and you know about more?
Click to expand...
Click to collapse
Exaclty, but what file Just like the text below the docs icon while scrolling tabs ...
As to other 0413 issues, G-sensor completes the list afaik the other langs is another story ...
Diegis0n said:
Exaclty, but what file Just like the text below the docs icon while scrolling tabs ...
As to other 0413 issues, G-sensor completes the list afaik the other langs is another story ...
Click to expand...
Click to collapse
Oh well the text below the docs icon was of no issue and i found it in a flash, just can't seem to find the file for the blank.
patensas said:
Oh well the text below the docs icon was of no issue and i found it in a flash, just can't seem to find the file for the blank.
Click to expand...
Click to collapse
I think i'm on to something about that blank field
Diegis0n said:
I think i'm on to something about that blank field
Click to expand...
Click to collapse
And you want to share that info?
patensas said:
And you want to share that info?
Click to expand...
Click to collapse
Of course ! If it works
Edit: cooking
Diegis0n said:
Of course ! If it works
Edit: cooking
Click to expand...
Click to collapse
Can't wait to hear if it works since this is the only "issue" i've found in my latest rom
The other options you've mentioned also work but that leaves us without the shortcut for Documents tab settings.
patensas said:
Can't wait to hear if it works since this is the only "issue" i've found in my latest rom
The other options you've mentioned also work but that leaves us without the shortcut for Documents tab settings.
Click to expand...
Click to collapse
I edited the 0413.mui file and it works !!
I'll upload it
http://rapidshare.com/files/392988811/SettingImprovement.exe.0413.mui
Diegis0n said:
I edited the 0413.mui file and it works !!
I'll upload it
http://rapidshare.com/files/392988811/SettingImprovement.exe.0413.mui
Click to expand...
Click to collapse
You're the man, cooking this very moment
What program do you use to edit mui files?
patensas said:
You're the man, cooking this very moment
What program do you use to edit mui files?
Click to expand...
Click to collapse
I use Restorator.
PS: can you show me how to have the text below the icon?
Diegis0n said:
I use Restorator.
PS: can you show me how to have the text below the icon?
Click to expand...
Click to collapse
I've edited the 26948339_manila file in Manila Core folder which was the easiest way to solve it for me since i only cook in Dutch.
patensas said:
I've edited the 26948339_manila file in Manila Core folder which was the easiest way to solve it for me since i only cook in Dutch.
Click to expand...
Click to collapse
So simple Thanks!
Diegis0n said:
So simple Thanks!
Click to expand...
Click to collapse
You're welcome and ofcourse thank you for editing the mui file for me
Happy ending huh? added into the fixes stickie thread
+ Que PPC said:
Happy ending huh? added into the fixes stickie thread
Click to expand...
Click to collapse
And they cooked happily ever after ...

[SOLVED]Incoming call avatar problem

hello to all
i have cooked a rom with 23673 build and i used rhodium phonecanvas ....i have a problem with my incoming call screen avatar please see the screenshot below
i dont have the avatar image and icoming number i have only the blank white square screen::i have the avatar images in project a folder and i have the initflasht entries also
i dont know what provoque this problem will any one please help me if u have any solution...;thanks to all
This has been a known problem for about an yr now!!! Search for something called caller id fix, and you will learn more about it.
Peace.
ai6908 said:
This has been a known problem for about an yr now!!! Search for something called caller id fix, and you will learn more about it.
Peace.
Click to expand...
Click to collapse
oops sorry its already solved issue...solution found in wm 6.5.3 index of fixes
can you provide a link to the index of fixes... using search doenst reveal anything
lllboredlll said:
can you provide a link to the index of fixes... using search doenst reveal anything
Click to expand...
Click to collapse
here it is bro http://forum.xda-developers.com/showthread.php?t=657372
look at here
Build: 23640
FIX: Caller ID phonecanvas
Thanks to: Faria
Replace the files in Phoneredist:
* Cprog.exe
* Cfghost.exe
* Celltsp.dll
Hmm
I have tried cooking in those files to 23673 and had no luck. I added them as a custom ext to overwrite the sys ones - perhaps I need to put them in the sys directly and replace the originals? Will try tonight.
crazyC said:
Hmm
I have tried cooking in those files to 23673 and had no luck. I added them as a custom ext to overwrite the sys ones - perhaps I need to put them in the sys directly and replace the originals? Will try tonight.
Click to expand...
Click to collapse
You have to replace the originals, I'm also working on a rom based on 23673 and it is really a complex build I changed the complete Lockscreen and the Phoneredist, you can find them in the Common folder.
Greetz,
Aha,
Is this why my call history seems a bit messed up? (although the incoming id and scrollbar are now fixed)
Which build did you substitute in from?
crazyC said:
Aha,
Is this why my call history seems a bit messed up? (although the incoming id and scrollbar are now fixed)
Which build did you substitute in from?
Click to expand...
Click to collapse
I'm not sure anymore from which build I take the files from, but my call history is also a little messed up, not fitting in the screen but workable.
Greetz,

[SOLVED] Add Contact in 6.5.3

Hi, I´ve a little trouble with adding contacts´ background. I don´t know why this image is here. Thanks
Judging from the color and shape that image might be related the te custom theme you are using.
Anyway I have never seen such an image in ROM's before so it might be part of some custom tweeks. So disabling them could solf you problem after a few tries.
BTW which Build are you using?
looks like com5 gwes on com3 build.
derliebewolf said:
Judging from the color and shape that image might be related the te custom theme you are using.
Anyway I have never seen such an image in ROM's before so it might be part of some custom tweeks. So disabling them could solf you problem after a few tries.
BTW which Build are you using?
Click to expand...
Click to collapse
29017 but is the same with 21689 and others com 3
I thought that was Huasang PhoneCanvas, but I put out and is the same
ultrashot said:
looks like com5 gwes on com3 build.
Click to expand...
Click to collapse
Perhaps anything in the langpacks or translations? (0C0A) I´m using langpack from 23563 rollup
malatest said:
I´m using langpack from 23563 rollup
Click to expand...
Click to collapse
COM5 mui files do not work for COM3....
AndrewSh said:
COM5 mui files do not work for COM3....
Click to expand...
Click to collapse
Ok, I´ll try other mui
There's no real reason to use a different gwes though, is there? If you're doing it for the bold font fix, there's a much better fix for that.
seeM_ZA said:
There's no real reason to use a different gwes though, is there? If you're doing it for the bold font fix, there's a much better fix for that.
Click to expand...
Click to collapse
Before there was the real fix by ultrashot, only way to fix the bold fonts were to change the gwes...I think it was posted by cloudyfa.
Ok, it´s solved. I forgot I was cloudyfa´s bold font fix active in my kitchen and I´ve also changed mui from 28230 build. Thanks guys for all
malatest said:
Ok, it´s solved. I forgot I was cloudyfa´s bold font fix active in my kitchen and I´ve also changed mui from 28230 build. Thanks guys for all
Click to expand...
Click to collapse
That means that the only correct answer in the topic was form ultrashot
But that's expected

Categories

Resources