Dialpad glitch with latest OS (for example 23108) - HD2 Windows Mobile 6.5 ROM Development

I built my own ROM with Phone_Canvas_Enhancement_2G 4_2_62120113626_0 from 2.10 ship rom and dialpad fix in the forum was also applied. The dialpad worked smoothly but I noticed a problem when somebody called me - the incoming call screen was totally blank! No numbers were shown. How to solve this problem? Thank you very much.

BoomerCE said:
I built my own ROM with Phone_Canvas_Enhancement_2G 4_2_62120113626_0 from 2.10 ship rom and dialpad fix in the forum was also applied. The dialpad worked smoothly but I noticed a problem when somebody called me - the incoming call screen was totally blank! No numbers were shown. How to solve this problem? Thank you very much.
Click to expand...
Click to collapse
Which dialpad fix? Fards' fix. Unfortunately that doesn't work on 2310x builds. There are more problems on this builds with the dialpad. Like for example the one you mention.
There a two (actually 3) options you can try, install the ported mini dialer from Smaberg (look in his sticky thread in the app forum) or you can use pimstore.dll, cprog.exe and tpcutil.dll from a 23544 (or newer) build. A third option is to try cprog.exe and maybe pimstore.dll and tpcutil.dll from the tmous 2.10 rom.
Don't use these workarounds with fards' dll because that will cause some severe problems. (unfortunately)

Thank you for you help I will try it out today and report the results.

appleflap that's absolute drivel !
I've used my file on all the 23xxx builds..
I'm currently using it on 23108 right know without issues..
the callerID issue is another problem altogether to what My file fixed, at least you are correct in suggesting the correct files to fix that..

fards said:
appleflap that's absolute drivel !
I've used my file on all the 23xxx builds..
I'm currently using it on 23108 right know without issues..
the callerID issue is another problem altogether to what My file fixed, at least you are correct in suggesting the correct files to fix that..
Click to expand...
Click to collapse
Your fix is so great Workaround for 23108 is to use your fix and use pimstore.dll, cprog.exe and tpcutil.dll from 23545, is that right?

fards said:
appleflap that's absolute drivel !
I've used my file on all the 23xxx builds..
I'm currently using it on 23108 right know without issues..
the callerID issue is another problem altogether to what My file fixed, at least you are correct in suggesting the correct files to fix that..
Click to expand...
Click to collapse
Yeah, great
From experience with the 23105 and 23106 build, I can tell you that your fix caused severe problems with the substitution of the pimstore.dll, cprog.exe and tpcutil.dll files from a 23544 build. (Lockups, a non working windows softkeys etc) Be my guest try it.
The same is true for the combination of the ported Mini dialer and the aforementioned susbtituted files. Be my guest, try that also.
I had to rebuild my roms too often to not stay 100% behind after what i'm saying here. So don't you drivel me.
And ****, at least i'm trying here. Now please give the guy an answer you genius.

Related

Anti - Fix_on-screen slide

a lot of guys want it...
so here it is:
install:
1.) uninstall the "Fix_on-screen slide"
2.) install my "Anti-Fix_on-screen slide"
3.) -> "only optional" install my black dialer once again - if you have the black dialer installed - you can find it under HTC - Blackstone - Applications...
If you are not happy, uninstall my version - then it use your original ROM files insteed and no hard reset is necc.
(language -> my version is i german, but this should also work for all other - let me know if there is a problem).
cu camel
camro said:
a lot of guys want it...
so here it is:
Click to expand...
Click to collapse
... but what is it? You don't describe what you're offering here.
SiliconS said:
... but what is it? You don't describe what you're offering here.
Click to expand...
Click to collapse
sorry - for guys which installed the official fix for "fix on-screen slide" which some guys installed and then they had some problems and don't want to do a hard reset
ex: http://forum.xda-developers.com/showthread.php?t=468478
cu camel
can anyone else confirm this fixes the problem with the video calling?
Psygnosis84 said:
can anyone else confirm this fixes the problem with the video calling?
Click to expand...
Click to collapse
yes - me on my image it has this bug
Thanks so much, Camro !
Your uninstall cab worked. Videocalls are now accessible again
Shame and blame on HTC for this useless "Bugfix" !
Sticky this thread
Thank you Camro.
This also got rid of the problem for me too, which was caused by the slider "hot fix". For reference I'm using WWE 1.19.25581 from the official HTC Hong Kong site.
I suspect this thread/tool will become a lifesaver for many users!
THANKS!!
I ran it and it fixed the problem
Thanks! Worked
Thank you very much.
You will be quite popular I think
Shame on HTC.
This slide fix + the Painting problems on the HD are not acceptable.
So as Camro's ROM is German (and mine btw too), I was not absolutely sure whether I was inadvertantly shooting down the videocall feature, because this Hotfix might have been meant for WWE only.
Although it nowhere says so on HTC's homepage or in the instructions given.
But now as one friend here said he has a WWE firmware and experienced the same problem (and Camro's Anti-Hotfix could save him) we can be sure that this "official HTC Hotfix" has a serious bug !
I only wonder how things like this can happen to a big company like HTC !
Fix a minor bug (I did not really complain about the "slider", which was not working), while at the same time create a major other one.
(btw: Did anyone check, whether their hotfix at least really fixed the "slider problem" ? As I applied the Hotfix around midnight, when I did not receive incoming calls, I couldn't even check that.)
Ain't there no QC at all ?
While a few minutes ago HTC still had the Hotfix available at http://www.htc.com/europe/supportdownloadlist.aspx?p_id=179&act=sd&cat=all
(but no longer linked to the Support menu) it seems they have just now deleted it !
Apparently they now noticed their mistake.
So let's see what kind of "genuine final" Hotfix they will provide us now.
thank you very much!
that bug realy annoyed me.
but where are we now? the slider is still laggy (i installed your cab without removing the slider fix) or it is ok and you just made the cosmetic rearrangements?
Thanks for the fix. Was annoying to see it on screen. Now looking lovely again
Thanks camro,good work!
After your anti-fix is installed and everything is working again can it be unistalled?
HugoTouchHD said:
After your anti-fix is installed and everything is working again can it be unistalled?
Click to expand...
Click to collapse
YES,
on uninstall - will delete the "new" ROM files and after that your system will copy the hidden (your original) ROM files from your basic image.
the related files are:
Windows\18c460d8_manila
Windows\HTCLTB.png
Windows\Incall_02_B.bmp
Windows\phcanhtc.dll
Windows\rilphone.dll
(BUT - only the cab-install/uninstall can delete the "new" ROM files
cu camel
ghl10000 said:
http://www.htc.com/europe/supportdownloadlist.aspx?p_id=179&act=sd&cat=all
Click to expand...
Click to collapse
Strange...
Seems it's online again and available for d/l via this link - with the same timestamp and no additional comment.
So apparently the same faulty package.
I was almost about to think that HTC might read xda-developers.com and maybe adopt some advice from here. Seems I'm mistaken.
camro said:
YES,
on uninstall - will delete the "new" ROM files and after that your system will copy the hidden (your original) ROM files from your basic image.
the related files are:
Windows\18c460d8_manila
Windows\HTCLTB.png
Windows\Incall_02_B.bmp
Windows\phcanhtc.dll
Windows\rilphone.dll
(BUT - only the cab-install/uninstall can delete the "new" ROM files
cu camel
Click to expand...
Click to collapse
This is about the hotfix itself I suppose (which per instruction I uninstalled first), I meant can I uninstall the "Camel Anti-Fix on screen slider"?
so camro, can you please tell me if your cab do justr cosmetic correction or uninstal completeley the slider fix?
in other words, after installing your cab the slider will be laggy or not?
thank you!
noris08 said:
so camro, can you please tell me if your cab do justr cosmetic correction or uninstal completeley the slider fix?
in other words, after installing your cab the slider will be laggy or not?
thank you!
Click to expand...
Click to collapse
1.) what do my fix for fix ?
my cab overwrite (on install) all "HTC fixed files"
my cab delete (on uninstall) all "files"
the related files are:
Windows\18c460d8_manila
Windows\HTCLTB.png
Windows\Incall_02_B.bmp
Windows\phcanhtc.dll
Windows\rilphone.dll
2.) what do my fix for fix ?
cab the slider will be laggy - as it was before install the HTC (buggy) fix.
if someone wants to play with only installing one of the fixed files ... - let me know.
for me - i haven't feel a laggy problem - i only tested the install to help some users whcih had problems with the HTC fix and unstalling the HTC fix without a hardreset.
br camel
EDIT: if somebody wants to play with single files from official (buggy) fix - here attached all flies from the install.
(not necc. to make reg entries.)

Notification Enhancement 3.5 Prevents Boot-up

On my Fuze, Notification Enhancement 3.5 will not allow my device to boot past the orange screen in WM 6.5 21887. I'm cooking a clone ROM of the Rhodium S2 (Sense 2.5) with EVK and I have everything BUT Notification Enhancement 3.5 working. 2.0 works fine BTW. In addition, the volume control is not working except for through the manila settings tab with either one. I'm thinking this is a hardware-software incompatibility issue. However, I'm not giving up yet. There are some other issues through which I think I can work but any help here would be greatly appreciated.
This is a known issue with EVK. You need to recmod NTFConfig.dll. This issue doesn't persist with Barin's OSBuilder.
indagroove said:
This is a known issue with EVK. You need to recmod NTFConfig.dll. This issue doesn't persist with Barin's OSBuilder.
Click to expand...
Click to collapse
I was also having the same problem And never knew about the EVK Issue. Shall have to give it a try..
thanks..
Thanks for the heads up, indagroove. It worked. BTW, I still haven't got around to using OSBuilder yet. I'll be reporting as I get a chance.
Yes I confirm that recmodding the module did work... thanks a lot...
Actually, it's not an issue with EVK, it's an issue with PRB. EVK uses PRB as the building tool. PRB lacks the ability to handle some modules. But PRB is the easiest to use building tool I have ever used, so I don't want to switch to OSBuilder yet.

[SOLVED] Dialer Scroll problem

I have had issues with 23569 & 23127 builds where I get this (please see pictures) I can't duplicate it all the time it just shows up whenever it want's too. As soon as I see the bar on the right the dialer disappears and it takes a soft reset to make it come back. Sometimes the soft reset works and sometimes it doesn't. If you have seen this before and know how to fix this please let me (us) know.
I have tried searching the forums and can't find an exact match to this.
Thanks!
This is a known issue.... please read the stickies in CC before asking.... You can find most solved issues there
Here's a helping hand...
http://forum.xda-developers.com/showthread.php?p=6584182#post6584182
Nibbley15 said:
I have had issues with 23569 & 23127 builds where I get this (please see pictures) I can't duplicate it all the time it just shows up whenever it want's too. As soon as I see the bar on the right the dialer disappears and it takes a soft reset to make it come back. Sometimes the soft reset works and sometimes it doesn't. If you have seen this before and know how to fix this please let me (us) know.
I have tried searching the forums and can't find an exact match to this.
Thanks!
Click to expand...
Click to collapse
Hello bro it is a well known issue with 6.5.5 build and it is already solved problem please see the first post " solved issues in chef central" and take a look at wm 6.5.5 index of fixes and u Will get ur solution.....
kurniawan77 said:
This is a known issue.... please read the stickies in CC before asking.... You can find most solved issues there
Here's a helping hand...
http://forum.xda-developers.com/showthread.php?p=6584182#post6584182
Click to expand...
Click to collapse
Thanks for the quick reply, I read all of those and none of them seemed to have matched the description.
Can you please tell me which one is the correct one to choose?
I tried the "Remove Phonecanvas scrollbar" by Alexx~~
Those files are not listed (8121) in my .dll files I have numbers 8124-8137 And they all have the EXSTYLE = 0x02000000 for the 800X480 and 480X800
I solved this simply using 23128 and dialer from Huashan (0.90 TEST ROM) .
OndraSter said:
I solved this simply using 23128 and dialer from Huashan (0.90 TEST ROM) .
Click to expand...
Click to collapse
great idea...
OndraSter said:
I solved this simply using 23128 and dialer from Huashan (0.90 TEST ROM) .
Click to expand...
Click to collapse
I'll give it a try, thanks!
With the 23127 I tried the fix for the button, then that caused the pink spot, then I fixed the pink spot, then that misaligned the caller ID screen; good grief.....
EDIT: Will the Phone_Canvas_Enhancement_5_0_61220163232_0 file work with the mui file from Phone_Canvas_Enhancement_2G_4_2_62520142921_0 ? Or do you suggest a different MUI file?
EDIT: Decided to try it anyway; after importing 23128 into kitchen & new canvas from .90 test ROM and cooking I got a common\persistance\internal\winmfile.cpp:56 error on boot up (phone). Tracking down where the error arrived from canvas or 23128 SYS
It was the 23128 causing the crash; the new dialer (Phone_Canvas_Enhancement_5_0_61220163232_0) is working in the 23127 build but well the picture says it all.....(first pic)
This dialer/fix worked, crazy all the fixes in one location http://forum.xda-developers.com/showthread.php?t=715498 , needs to be added to the solved list, here is a pic. This fixed the scrolling issue, pink spot, and callerID placement. (Seal Team 6 fix)
This fix labeled
Nibbley15 said:
I have had issues with 23569 & 23127 builds where I get this (please see pictures) I can't duplicate it all the time it just shows up whenever it want's too. As soon as I see the bar on the right the dialer disappears and it takes a soft reset to make it come back. Sometimes the soft reset works and sometimes it doesn't. If you have seen this before and know how to fix this please let me (us) know.
I have tried searching the forums and can't find an exact match to this.
Thanks!
Click to expand...
Click to collapse
In the kitchen @ ..\EXT\LEO\COMMON\WM_6.5.x\pdqhd2_fix_overlap_icon

[Q] How can make HTC Album get work?

I'm making ROM for my Acer S200...
Much things run correctly, except HTC Album. There is no any error pop up.
However, manila Photo tab "seems" work. I could not set wallpaper in setting tab and could not select pic in contact tab.
I have these packages got from
RUU_Leo_S_HTC_Asia_TW_3.04.709.1_Radio_Signed_15.40.50.07U_2.12.50.02_2_Ship.exe
Code:
PACKAGE_LEO_S_Album
PACKAGE_LEO_S_Album_0404
PACKAGE_LEO_S_AppointmentEditor
PACKAGE_LEO_S_AppointmentEditor_0404
PACKAGE_LEO_S_App_Service
PACKAGE_LEO_S_App_Service_0404
PACKAGE_LEO_S_Audio_Manager_Engine
PACKAGE_LEO_S_Audio_Manager_Engine_0404
PACKAGE_LEO_S_Boot_Launcher
PACKAGE_LEO_S_Boot_Launcher_0404
PACKAGE_LEO_S_BrowserSnapshot
PACKAGE_LEO_S_BrowserSnapshot_0404
PACKAGE_LEO_S_CommManager_HTC_ALL
PACKAGE_LEO_S_CommManager_HTC_ALL_0404
PACKAGE_LEO_S_Contact_Picker
PACKAGE_LEO_S_Contact_Picker_0404
PACKAGE_LEO_S_Contact_Utility_Engine
PACKAGE_LEO_S_Contact_Utility_Engine_0404
PACKAGE_LEO_S_DataDisconnect
PACKAGE_LEO_S_DataDisconnect_0404
PACKAGE_LEO_S_DeviceInfo
PACKAGE_LEO_S_DeviceInfo_0404
PACKAGE_LEO_S_DRM_Middleware
PACKAGE_LEO_S_DRM_Middleware_0404
PACKAGE_LEO_S_Dshow
PACKAGE_LEO_S_Dshow_0404
PACKAGE_LEO_S_Facebook_Engine
PACKAGE_LEO_S_Facebook_Engine_0404
PACKAGE_LEO_S_GoogleLocationService
PACKAGE_LEO_S_GoogleLocationService_0404
PACKAGE_LEO_S_GroupEditor
PACKAGE_LEO_S_GroupEditor_0404
PACKAGE_LEO_S_HTCAnimation
PACKAGE_LEO_S_HTCAnimation_0404
PACKAGE_LEO_S_HTCApplication
PACKAGE_LEO_S_HTCApplication_0404
PACKAGE_LEO_S_HTCBookmark
PACKAGE_LEO_S_HTCBookmark_0404
PACKAGE_LEO_S_HTCFramework
PACKAGE_LEO_S_HTCFramework_0404
PACKAGE_LEO_S_HTCGeoService
PACKAGE_LEO_S_HTCGeoService_0404
PACKAGE_LEO_S_HTCScroll
PACKAGE_LEO_S_HTCScroll_0404
PACKAGE_LEO_S_HTCStartUp
PACKAGE_LEO_S_HTCStartUp_0404
PACKAGE_LEO_S_HTCUtil
PACKAGE_LEO_S_HTCUtil_0404
PACKAGE_LEO_S_Manila_Calendar
PACKAGE_LEO_S_Manila_Calendar_0404
PACKAGE_LEO_S_Manila_Core
PACKAGE_LEO_S_Manila_Core_0404
PACKAGE_LEO_S_Manila_Home
PACKAGE_LEO_S_Manila_Home_0404
PACKAGE_LEO_S_Manila_Internet
PACKAGE_LEO_S_Manila_Internet_0404
PACKAGE_LEO_S_Manila_Mail
PACKAGE_LEO_S_Manila_Mail_0404
PACKAGE_LEO_S_Manila_Message
PACKAGE_LEO_S_Manila_Message_0404
PACKAGE_LEO_S_Manila_Music
PACKAGE_LEO_S_Manila_Music_0404
PACKAGE_LEO_S_Manila_People
PACKAGE_LEO_S_Manila_People_0404
PACKAGE_LEO_S_Manila_Photo
PACKAGE_LEO_S_Manila_Photo_0404
PACKAGE_LEO_S_Manila_Settings
PACKAGE_LEO_S_Manila_Settings_0404
PACKAGE_LEO_S_Manila_Stock
PACKAGE_LEO_S_Manila_Stock_0404
PACKAGE_LEO_S_Manila_Twitter
PACKAGE_LEO_S_Manila_Twitter_0404
PACKAGE_LEO_S_Manila_Weather
PACKAGE_LEO_S_Manila_Weather_0404
PACKAGE_LEO_S_Media_Tool_kit
PACKAGE_LEO_S_Media_Tool_kit_0404
PACKAGE_LEO_S_Menu_Enhancement
PACKAGE_LEO_S_Menu_Enhancement_0404
PACKAGE_LEO_S_mHub_VO
PACKAGE_LEO_S_mHub_VO_0404
PACKAGE_LEO_S_MyCPL
PACKAGE_LEO_S_MyCPL_0404
PACKAGE_LEO_S_New_Contact_Card
PACKAGE_LEO_S_New_Contact_Card_0404
PACKAGE_LEO_S_Phone_Canvas_Enhancement_2G
PACKAGE_LEO_S_Phone_Canvas_Enhancement_2G_0404
PACKAGE_LEO_S_Power
PACKAGE_LEO_S_Power_0404
PACKAGE_LEO_S_Resource_Proxy
PACKAGE_LEO_S_Resource_Proxy_0404
PACKAGE_LEO_S_Sensor_SDK
PACKAGE_LEO_S_Sensor_SDK_0404
PACKAGE_LEO_S_Settings_Improvement
PACKAGE_LEO_S_Settings_Improvement_0404
PACKAGE_LEO_S_SharedResource
PACKAGE_LEO_S_SharedResource_0404
PACKAGE_LEO_S_Shared_Modules
PACKAGE_LEO_S_Shared_Modules_0404
PACKAGE_LEO_S_Social_Networks_Engine
PACKAGE_LEO_S_Social_Networks_Engine_0404
PACKAGE_LEO_S_StartIconLoader
PACKAGE_LEO_S_StartIconLoader_0404
PACKAGE_LEO_S_Text_Selection
PACKAGE_LEO_S_Text_Selection_0404
PACKAGE_LEO_S_TimeZoneAutoFix
PACKAGE_LEO_S_TimeZoneAutoFix_0404
PACKAGE_LEO_S_VBookmarkMgr
PACKAGE_LEO_S_VBookmarkMgr_0404
PACKAGE_LEO_S_zlibce_m
PACKAGE_LEO_S_zlibce_m_0404
Nagato Yuki said:
I'm making ROM for my Acer S200...
Much things run correctly, except HTC Album. There is no any error pop up.
However, manila Photo tab "seems" work. I could not set wallpaper in setting tab and could not select pic in contact tab.
I have these packages got from
RUU_Leo_S_HTC_Asia_TW_3.04.709.1_Radio_Signed_15.40.50.07U_2.12.50.02_2_Ship.exe
Code:
PACKAGE_LEO_S_Album
PACKAGE_LEO_S_Album_0404
PACKAGE_LEO_S_AppointmentEditor
PACKAGE_LEO_S_AppointmentEditor_0404
PACKAGE_LEO_S_App_Service
PACKAGE_LEO_S_App_Service_0404
PACKAGE_LEO_S_Audio_Manager_Engine
PACKAGE_LEO_S_Audio_Manager_Engine_0404
PACKAGE_LEO_S_Boot_Launcher
PACKAGE_LEO_S_Boot_Launcher_0404
PACKAGE_LEO_S_BrowserSnapshot
PACKAGE_LEO_S_BrowserSnapshot_0404
PACKAGE_LEO_S_CommManager_HTC_ALL
PACKAGE_LEO_S_CommManager_HTC_ALL_0404
PACKAGE_LEO_S_Contact_Picker
PACKAGE_LEO_S_Contact_Picker_0404
PACKAGE_LEO_S_Contact_Utility_Engine
PACKAGE_LEO_S_Contact_Utility_Engine_0404
PACKAGE_LEO_S_DataDisconnect
PACKAGE_LEO_S_DataDisconnect_0404
PACKAGE_LEO_S_DeviceInfo
PACKAGE_LEO_S_DeviceInfo_0404
PACKAGE_LEO_S_DRM_Middleware
PACKAGE_LEO_S_DRM_Middleware_0404
PACKAGE_LEO_S_Dshow
PACKAGE_LEO_S_Dshow_0404
PACKAGE_LEO_S_Facebook_Engine
PACKAGE_LEO_S_Facebook_Engine_0404
PACKAGE_LEO_S_GoogleLocationService
PACKAGE_LEO_S_GoogleLocationService_0404
PACKAGE_LEO_S_GroupEditor
PACKAGE_LEO_S_GroupEditor_0404
PACKAGE_LEO_S_HTCAnimation
PACKAGE_LEO_S_HTCAnimation_0404
PACKAGE_LEO_S_HTCApplication
PACKAGE_LEO_S_HTCApplication_0404
PACKAGE_LEO_S_HTCBookmark
PACKAGE_LEO_S_HTCBookmark_0404
PACKAGE_LEO_S_HTCFramework
PACKAGE_LEO_S_HTCFramework_0404
PACKAGE_LEO_S_HTCGeoService
PACKAGE_LEO_S_HTCGeoService_0404
PACKAGE_LEO_S_HTCScroll
PACKAGE_LEO_S_HTCScroll_0404
PACKAGE_LEO_S_HTCStartUp
PACKAGE_LEO_S_HTCStartUp_0404
PACKAGE_LEO_S_HTCUtil
PACKAGE_LEO_S_HTCUtil_0404
PACKAGE_LEO_S_Manila_Calendar
PACKAGE_LEO_S_Manila_Calendar_0404
PACKAGE_LEO_S_Manila_Core
PACKAGE_LEO_S_Manila_Core_0404
PACKAGE_LEO_S_Manila_Home
PACKAGE_LEO_S_Manila_Home_0404
PACKAGE_LEO_S_Manila_Internet
PACKAGE_LEO_S_Manila_Internet_0404
PACKAGE_LEO_S_Manila_Mail
PACKAGE_LEO_S_Manila_Mail_0404
PACKAGE_LEO_S_Manila_Message
PACKAGE_LEO_S_Manila_Message_0404
PACKAGE_LEO_S_Manila_Music
PACKAGE_LEO_S_Manila_Music_0404
PACKAGE_LEO_S_Manila_People
PACKAGE_LEO_S_Manila_People_0404
PACKAGE_LEO_S_Manila_Photo
PACKAGE_LEO_S_Manila_Photo_0404
PACKAGE_LEO_S_Manila_Settings
PACKAGE_LEO_S_Manila_Settings_0404
PACKAGE_LEO_S_Manila_Stock
PACKAGE_LEO_S_Manila_Stock_0404
PACKAGE_LEO_S_Manila_Twitter
PACKAGE_LEO_S_Manila_Twitter_0404
PACKAGE_LEO_S_Manila_Weather
PACKAGE_LEO_S_Manila_Weather_0404
PACKAGE_LEO_S_Media_Tool_kit
PACKAGE_LEO_S_Media_Tool_kit_0404
PACKAGE_LEO_S_Menu_Enhancement
PACKAGE_LEO_S_Menu_Enhancement_0404
PACKAGE_LEO_S_mHub_VO
PACKAGE_LEO_S_mHub_VO_0404
PACKAGE_LEO_S_MyCPL
PACKAGE_LEO_S_MyCPL_0404
PACKAGE_LEO_S_New_Contact_Card
PACKAGE_LEO_S_New_Contact_Card_0404
PACKAGE_LEO_S_Phone_Canvas_Enhancement_2G
PACKAGE_LEO_S_Phone_Canvas_Enhancement_2G_0404
PACKAGE_LEO_S_Power
PACKAGE_LEO_S_Power_0404
PACKAGE_LEO_S_Resource_Proxy
PACKAGE_LEO_S_Resource_Proxy_0404
PACKAGE_LEO_S_Sensor_SDK
PACKAGE_LEO_S_Sensor_SDK_0404
PACKAGE_LEO_S_Settings_Improvement
PACKAGE_LEO_S_Settings_Improvement_0404
PACKAGE_LEO_S_SharedResource
PACKAGE_LEO_S_SharedResource_0404
PACKAGE_LEO_S_Shared_Modules
PACKAGE_LEO_S_Shared_Modules_0404
PACKAGE_LEO_S_Social_Networks_Engine
PACKAGE_LEO_S_Social_Networks_Engine_0404
PACKAGE_LEO_S_StartIconLoader
PACKAGE_LEO_S_StartIconLoader_0404
PACKAGE_LEO_S_Text_Selection
PACKAGE_LEO_S_Text_Selection_0404
PACKAGE_LEO_S_TimeZoneAutoFix
PACKAGE_LEO_S_TimeZoneAutoFix_0404
PACKAGE_LEO_S_VBookmarkMgr
PACKAGE_LEO_S_VBookmarkMgr_0404
PACKAGE_LEO_S_zlibce_m
PACKAGE_LEO_S_zlibce_m_0404
Click to expand...
Click to collapse
I`m guessing you're using latest Media_Tool_kit? I faced the same problem when cooking com2 with latest Media_Tool_kit.
patensas said:
I`m guessing you're using latest Media_Tool_kit? I faced the same problem when cooking com2 with latest Media_Tool_kit.
Click to expand...
Click to collapse
Yes, I'm cooking COM2 build 21911... Sorry for not mention at first post.
Maybe Media_Tool_kit from Leo S 3.04 could be the latest one, but I'm not sure that Official Leo one (with Sense 2.5.1921) could be used or not, as I'm at work now, much thanks for your information.
Edit: But I thinks that I'm lack something instead of package version, seems that Arto could use the Official Leo one (1_2_19203325_0)...
Nagato Yuki said:
Yes, I'm cooking COM2 build 21911... Sorry for not mention at first post.
Maybe Media_Tool_kit from Leo S 3.04 could be the latest one, but I'm not sure that Official Leo one (with Sense 2.5.1921) could be used or not, as I'm at work now, much thanks for your information.
Edit: But I thinks that I'm lack something instead of package version, seems that Arto could use the Official Leo one (1_2_19203325_0)...
Click to expand...
Click to collapse
Well who knows, let me know
patensas said:
Well who knows, let me know
Click to expand...
Click to collapse
I found the strange problem, even the version of HTCAlbum was the same, but the size of them are different !
The usable HTCAlbum.exe could be 483,288 Bytes, but one I get form Leo could be 1,293,824 Bytes !
I don't know the different of them...
Try adding the picture_enhancement package
When I found the size of these files change, I know I'm fail to recognize these files are UPX compressed.
I'm flashing my rom to test whether this cause the problem...
I could report it later
BTW, could any one know what's the maximum executable file size?
Media Toolkit is the one responsible to perform 'Photo picker' .
But finally I could not use either HTC Album and Media Tool kit from Leo HK or Leo S TW ROM, but from Arto's Acer ROM
It seems the problem could not be solve until reason found...
Then, I put these two file here, to let someone help me
The non-working one is from
RUU_Leo_HTC_WWE_1.66.405.2_Radio_Signed_15.30.50.07U_2.06.51.07_Ship.exe
and The working one is from Arto's Acer ROM
http://forum.xda-developers.com/showthread.php?t=642654
Bump for visible
The diffrent between your two exe's is, that the file in your HTCAlbum_workone.zip is upx-comressed. That's all.
icke said:
The diffrent between your two exe's is, that the file in your HTCAlbum_workone.zip is upx-compressed. That's all.
Click to expand...
Click to collapse
Yes, one is upx-compressed. However, even both uncompressed, it seems I have to patch it from official ROM to be used on non-HTC phone...
rafyvitto said:
HI, im sorry to say but i was not the one who patched these packages to skip device id check, it was dimice from acerclub.ru il try to contact him and get back to you.
rafyvitto
Click to expand...
Click to collapse
Since I could not understand Russian, then I still have no idea to patch them...

[Q] Problem with Phone Canvas Enhancement 2G v4.0.52619223128.0 in com2 build.

Problem with Phone Canvas Enhancement 2G v4.0.52619223128.0 in com2 build.
Hi all, just have an issue and I can't point the finger on the right place to get this one solved
So I'm asking for some help, I'm using the Phone Canvas Enhancement mentioned above, and it works perfect on a com3 build but
for some reason when I cooked this one in a com2 build the options for the dialer are not working.
I'm using the same kitchen, for com3 and com2 with the same pkg's and everything is working the way it should work.
Only in the com2 build I'm not able to setup the call-specific options.
Already changed the mui files, used another dummy_sqm but still no difference.
The com2 build I'm using is 21916, also tried 21914 but no difference.
Someone else have any idea ?
Thanks,
Ok, just want to give it one more try so BUMP
Hi,
Did you dump the rom yourself or are you using predumped packages?
Phonecanvas in com 3 needs some fixes like the softkeypad.
Also did you look in operatorpkg?
Have a look there which phcanOverbmp.
Is it HTC or T-Mous?
That's all I can think of.
Laurentius26 said:
Hi,
Did you dump the rom yourself or are you using predumped packages?
Phonecanvas in com 3 needs some fixes like the softkeypad.
Also did you look in operatorpkg?
Have a look there which phcanOverbmp.
Is it HTC or T-Mous?
That's all I can think of.
Click to expand...
Click to collapse
I dumped the rom myself, import the 23569 build and import the 21916 build, made a small change on the 21916 build (changed office mobile to office mobile 2010) and edit the file phcanrc, build rom in 23569 no problem, and in 21916 issue with the options.
There is not much left in my operatorpkg only the animated.gif and the Mega_phcanOverbmp, so I have to see if that causes the issue, but I still think it's strange that I don't have it with the 23569 build.
For now really thanks for the info, I'm gonna work on it and keep you informed if this will solve it.
Btw nice site you have
Greetz,
Try to use the phonecanvas as it's (if possible) and use the correspondending phcan in operatorpkg.
Another thing you need to check is the reg in operatorpkg, if it directs to the phcan you are using.
In my case:
[HKEY_LOCAL_MACHINE\Security\ResOver\Bitmaps]
"Basedll"="leo_phcanOverbmp.dll"
"BaseId"=dword:00000000
"BatteryIconIdStart"=dword:000003E9
"BatteryIconLevels"=dword:00000015
Click to expand...
Click to collapse
Thanks for the compliment about the site.
Rataplan said:
and edit the file phcanrc, build rom in 23569 no problem, and in 21916 issue with the options.
There is not much left in my operatorpkg only the animated.gif and the Mega_phcanOverbmp, so I have to see if that causes the issue, but I still think it's strange that I don't have it with the 23569 build.
Greetz,
Click to expand...
Click to collapse
What do you mean with "call specific options"?
pkoper said:
What do you mean with "call specific options"?
Click to expand...
Click to collapse
I mean the advanced options, sounds, network, gsm/umts, headset it's a submenu from the dialer, I think that Laurentius26 is right because I miss the registry key for phcan, I'm gonna check it this evening.
Still wondering why I don't have a problem with a com3 build.
Keep you all informed
Somewhere in sys, maybe Phone or Phoneredist I can't remember, it is set to not display.
Check your reg for
[HKEY_LOCAL_MACHINE\ControlPanel\Phone]
remove
redirect=""
if its there.
pkoper said:
Somewhere in sys, maybe Phone or Phoneredist I can't remember, it is set to not display.
Check your reg for
[HKEY_LOCAL_MACHINE\ControlPanel\Phone]
remove
redirect=""
if its there.
Click to expand...
Click to collapse
Okay thanks gonna try that, because changing the reg. made my kitchen crash.
Greetz,
Ok, I give up, I build 12 roms with 21916 (all different languages) until I noticed the issue, went back to 21914, same issue.
Tried what you both suggested, kitchen start crashing, went back to the original 21854 with the same pkg everything working normal also the options menu in the dialer.
So the problem must be in the changing the office pkg or a kitchen-update because thats are the only things I've changed.
And I'm not even sure about the kitchen-update.
For now I'm not sure what I've changed to give an honest answer if I get this solved.
Just want to say thanks the both of you, together is power
Regards,
I went through some unmodified builds.
The reg key is in the rgu in SYS\Phone....
[HKEY_LOCAL_MACHINE\ControlPanel\Phone]
"Redirect"=-
Sorry, made a mistake in the previous post
pkoper said:
I went through some unmodified builds.
The reg key is in the rgu in SYS\Phone....
[HKEY_LOCAL_MACHINE\ControlPanel\Phone]
"Redirect"=-
Sorry, made a mistake in the previous post
Click to expand...
Click to collapse
Yes, I know, I already found that reg key, but for some reason my kitchen keeps on crashing when I use the 21916 build, so I can not tell you if the trick you told me is working.
In short what I tried:
1. Edit the reg key for the phcan.
2. Deleting the reg key in the Phone pkg.
3. Changing the Phone pkg and use the one from 21854.
4. Building without ext-pkg
5. Make a switch to 21914 and repeated the 4 steps mentioned above.
But for now the kitchen keeps on crashing when I'm using the 21914 or 21916 build, which is very strange because I cooked several roms with it also cooked without the office pkg but still no change.
For now I'm gonna download another com2 build and see if that will do the trick.
In Dutch: Schiet mij maar lek.
In English: Shoot me.
And again really thanks for trying to help me.
Greetz,
Sorry forget my post.
Ok downloading and importing the 21916 again did the trick, download the build from mobileunderground, normally I used the builds from ppckitchen not sure if they are different.
The only thing I can think about for now is that when I'm upgrading my kitchen, went from 1.25 to 133.3 (oskitchen) always in small steps but the only thing I changed was the exe file and the resource folder, and maybe there it went wrong.
I know it is not a real solution but for me this one is solved.
Thanks,

Categories

Resources